System Messages for Cisco IOS Release 12.2 SX

System Messages for Cisco IOS Release 12.2 SX March 2012

Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883

Text Part Number:

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental. System Messages for Cisco IOS Release 12.2 SX @2010 Cisco Systems, Inc. All rights reserved.

Cisco IOS System Message Guide, 12.2 SX This publication lists and describes system messages for Cisco IOS Release 12.2 SX, up to and including 12.2(33)SXI. During operation, the system software sends these messages to the console and, optionally, to a logging server on another system. Not all system messages indicate problems with your system. Some messages are purely informational, and others may help diagnose problems with communications lines, internal hardware, or the system software. This guide also includes messages that appear when the system crashes. This guide contains the following topics: •

How The Messages Are Organized, page 1

•

How to Read System Messages, page 2

•

System Message Example, page 39

•

Message Traceback Reports, page 40

•

Message Overrun and Continuation, page 40

•

Using the Error Message Decoder to Search for System Messages, page 41

•

Searching for System Messages in Online Documentation, page 41

•

Obtaining Documentation and Submitting a Service Request, page 42

•

System Messages, page 1

•

GLOSSARY

How The Messages Are Organized The system messages provide descriptions of system messages related to the Cisco IOS software. The messages are organized according to the particular system facility that produces the messages. The facility sections appear in alphabetical order, and within each facility section, messages are listed alphabetically by mnemonic. Each message is followed by an explanation and a recommended action. For alphabetizing purposes, lowercase and uppercase letters are treated the same. The index of messages is alphabetized as follows: 1.

Facility code

2.

Mnemonic

Americas Headquarters: Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA

© 2008 Cisco Systems, Inc. All rights reserved.

Cisco IOS System Message Guide, 12.2 SX How to Read System Messages

3.

Note

Severity level

You can also view online system messages that pertain to Cisco IOS Release 12.2S-based releases. See System Messages for 12.2S.

How to Read System Messages System messages begin with a percent sign (%) and are structured as follows. The text in bold are required elements of the System Message, the text in italics are optional elements of the System Message. %FACILITY-SUBFACILITY-SEVERITY-MNEMONIC: Message-text FACILITY is a code consisting of two or more uppercase letters that indicate the facility to which the message refers. A facility can be a hardware device, a protocol, or a module of the system software. Table 1 lists the system facility codes.

is used only for Cisco Catalyst 6500 series switches that are operating in a distributed system. The subfacility can consist of one code, or two codes that are divided by a hyphen, and describes the part of the distributed system from where the message is coming. For example, the %DIAG-SP-STDBY-6-RUN_MINIMUM system message is the %DIAG-6-RUN_MINIMUM message coming from the switch processor (SP) that is in redundant or standby (STDBY) mode. SUBFACILITY

is a single-digit code from 0 to 7 that reflects the severity of the condition. The lower the number, the more serious the situation. Table 2 lists the severity levels.

SEVERITY

MNEMONIC

is a code that uniquely identifies the system message.

Message-text is a text string describing the condition. This portion of the message sometimes contains detailed information about the event, including terminal port numbers, network addresses, or addresses that correspond to locations in the system memory address space. Because the information in these variable fields changes from message to message, it is represented here by short strings enclosed in square brackets ([ ]). A decimal number, for example, is represented as [dec]. Table 3 lists the representations of variable fields and the type of information in them.

The following is a sample system message: %LINK-2-BADVCALL: Interface [chars], undefined entry point

Some messages also indicate the card and slot reporting the error. These messages begin with a percent sign (%) and are structured as follows: %CARD-SEVERITY-MSG:SLOT %FACILITY-SEVERITY-MNEMONIC: Message-text

is a code that describes the type of card reporting the error. CIP, CIP2, ECPA, ECPA4, FEIP, PCPA, and VIP are possible card types.

CARD

MSG

is a mnemonic that indicates that this is a message. It is always shown as

MSG.

SLOT indicates the slot number of the card reporting the error. It is shown as SLOT followed by a number (for example, SLOT5).

Note

The prepended portion of the message ( %CARD-SEVERITY-MSG:SLOT) is not shown in the system message listings in this manual.

System Messages for Cisco IOS Release 12.2 SX

2


Table 1

Facility Codes

Code

Facility

AAA

Authentication, authorization, and accounting

AAA_CACHE

Authentication, authorization, and accounting cache

AAAA

TACACS+ authentication, authorization, and accounting security

AAL5

ATM Adaptation Layer 5

AC

Attachment circuit

ACCESS_IE

Access information element

ACE

Access control encryption

ACL_ASIC

Access control list ASIC

ACLMERGE

Access control list merge

ACLMGR

Access control list manager

ADAPTER

CMCC adapter task

ADJ

Adjacency subsystem

AESOP_AIM

Service engine advanced interface module

AFLSEC

Accelerated Flow Logging Security

AHDLC_TRINIAN

PPP in HDLC-like framing device driver

AICMGMT

Alarm interface controller management

AIM

Advanced Interface Module (AIM)

AIP

ATM Interface Processor

ALARM

Telco chassis alarm related

ALC

ATM line card (ALC)

ALIGN

Memory optimization in Reduced Instruction Set Computer (RISC) processor

ALPS

Airline Protocol Support

AMD79C971_FE

Am79C971 Fast Ethernet device driver

AMDP2_FE

AMDP2 Ethernet and Fast Ethernet

AP

Authentication Proxy (AP)

APPFW

APPFW for HTTP subsystem

APS

Automatic Protection Switching

ARAP

Apple Remote Access Protocol (ARAP)

ARCHIVE_CONFIG

Archive configuration-related

ARCHIVE_DIFF

Archive Diff and Rollback-related

AS5400

Cisco AS5400 platform

AS5400_ENVM

Cisco AS5400 environmental monitor

ASPP

Asynchronous Security Protocol (ASPP)

AT

AppleTalk (AT)

ATM

Asynchronous Transfer Mode


3


Table 1

Facility Codes (continued)

Code

Facility

ATM_AIM

ATM advanced module

ATMCES

ATM access concentrator PCI port adapter driver

ATMCORE

ATM core

ATMLC

Cisco 7300 ATM line card software

ATMOC3

ATM OC-3 network module

ATMOC3POM

ATM- OC3-POM module

ATMPA

ATM port adapter

ATMSIG

ATM signaling subsystem

ATMSPA

ATM Shared Port Adapter

ATMSSCOP

ATM Service Specific Connection Oriented Protocol (SSCOP)

ATOM_NP_CLIENT

Any Transport over MPLS NP client

ATOM_SEG

Any Transport Over MPLS (AToM) Segment Handler

ATOM_TRANS

Layer 2 Transport over MPLS

AUDIT

Audit feature

AUTORP

PIMv2 AUTORP

AUTOSEC

AutoSecure

AUTOSHUT

Autoshut

AUTOSTATE

Autostate feature

BACKPLANE_BUS_ASI Backplane bus ASIC C BAMBAM

One-port Fast Ethernet with coprocessor assist

BAP

PPP Bandwidth Allocation Protocol (BAP)

BAT

Power supply (BAT)

BCM

Broadcom switch controller

BCM3220

Cable modem MAC controller interface

BCM56XX

BCM56XX control layer

BCM_GEWAN

Messages related to the Cisco 3800 system controller

BERT

Bit error rate tester (BERT)

BFD

Bidirectional Forwarding Detection

BFDFSM

BFD finite state machine

BGP

Border Gateway Protocol

BGP_MPLS

BGP MPLS common

BIT

Dynamic bitlist

BOOMERANG

Boomerang distributed reverse proxy server

BRI

ISDN Basic Rate Interface

BRIMUX

Cisco AS5200 BRIMUX board


4


Table 1


Code

Facility

BSC

Binary Synchronous Communications protocol

BSQ

Buffer status queue processing

BSR

Bootstrap router

BSTUN

Block serial tunneling (BSTUN)

BUNDLES

Bundles

C1400

Cisco 1400 platform

C_GIGE

Dual-port Gigabit Ethernet back card subsystem

C10K

Cisco 10000

C10K_APS

NSP APS

C10KATM

Cisco 10000 ATM

C10KCARDISSU

Cisco 10000 Card ISSU

C10KCHE1T1

Cisco 10000 T1 line card

C10KCHKPT

Cisco 10000 Checkpoint Facility

C10KET

Cisco 10000 ET

C10KEVENTMGR

Event Manager subsystem

C10KGE

Gigabit Ethernet subsystem

C10KHHCT3

Cisco 10000 HH Channelized T3

C10KINT

Cisco 10000 interrupt infrastructure

C10KISSU

Cisco 10000 In Service Software Upgrade

C10K_IEDGE

Cisco 10000 iEdge

C10K_LFI_GENERAL

Cisco 10000 Link Fragmentation and Interleaving

C10K_MULTILINK_ FRAGSIZE_BELOW_ MIN_WARNING

Cisco 10000 PXF Multilink fragment size below minimum warning

C10K_QOS_GENERAL

Cisco 10000 Quality of Service (QoS)

C10K_QUEUE_CFG_ GENERAL

Cisco 10000 PXF queuing configuration

C10K_TOASTER

Cisco 10000 toaster

C1400_PCI

Protocol control information (PCI) bus for Cisco 1400 platform

C1600

Cisco 1600 platform

C1700

Cisco 1700 platform

C1700_EM

Cisco 1700 VPN module hardware accelerator for IP security

C1800

Cisco 1800 platform

C1800_HW_CRYPTO

Cisco 1800, Cisco 1810 Motorola SEC 2.0

C2400_DSX1

Cisco 2400 DSX1 subsystem

C2600

Cisco 2600 platform


5


Table 1


Code

Facility

C2600_MAINBOARD_ ASYNC_PQUICC

MPC860 quad integrated communications controller for the Cisco 2600 platform

C2950

Catalyst 2950 series switch

C29ATM

Catalyst 2900XL ATM module

C2KATM

Catalyst 2820 ATM module

C3200_FE

Cisco 3200 FEC

C3600

Cisco 3600 platform

C3800

Cisco 3800 platform

C3800_ENVM

Environmental

C3825

Cisco 3825 platform

C4GWY_DSPRM

DSP Resource Manager

C4K

Catalyst 4000 platform

C542

Voice driver for modular access routers

C5421

Voice over IP

C54x

VoIP DSP driver

C54X

VoIP driver

C5510

Voice Over IP (VoIP) driver

C5RSP

Cisco Catalyst 5000 platform

C6KENV

Cisco Catalyst 6500 environmental system

C6K_MWAM_ CENTRALIZED_ CONFIG

Multiprocessor WAN Application Module (MWAM) centralized configuration

C6KPWR

Cisco Catalyst 6500 power control system

C6MSFC

C6MSFC (Draco)

C6SUP

C6SUP-specific

C7200

Cisco 7200 platform - deleted for 12.2

C7200_TDM

Cisco 7200 midplane TDM bus

C7600_RSP

Cisco 7600 Route Switch Processor

C7600_SIP200

SPA Interface Processor 200

C7600_SIP200_MP

Cisco 7600, Catalyst 6500 SIP-200 Multiprocessing

C7600_SIP200_SPIRX

Cisco 7600, Catalyst 6500 SIP-200 SPI4.2 bus ingress interface

C7600_SIP200_SPITX

Cisco 7600, Catalyst 6500 SIP-200 SPI4.2 bus egress interface

C7600_SSC600

Services SPA Carrier Card (SSC600)

C830_HW_CRYPTO

C830 Hifn

C870_FE

Cisco 870 Fast Ethernet

C870_HW_CRYPTO

Cisco 850, Cisco 870 Motorola SEC 1.0

C950

Cisco 950


6


Table 1


Code

Facility

CAIM

Compression Advanced Interface Module (CAIM)

CALL_CONTROL

Call control

CALL_HOME

Call Home

CALL_MGMT

Call management subsystem

CALLPROG

Call progress notification subsystem

CALLRECORD

Modem Call Record

CALLTREAT

Call treatment

CALLTREAT_NOSIGN AL

Call Treatment (TREAT)

CALLTRKR

Call Tracker subsystem

CAMP

Cooperative Asymmetric Multiprocessing

CAPI

Card API

CAPI_EC

Card or EtherChannel limitation

CARDMGR

SIP-400 Card Manager (data plane)

CARRIER

DFC carrier

CASA

Cisco Appliance and Services Architecture (CASA)

CBUS

CiscoBus controller

CBUS_ATTN

CMCC CIP for Cisco bus controller statistics routine

CBUS_WRITE

CMCC CIP for Cisco bus controller write support

CCA

CMCC CIP for channel card adapter

CCH323

Call Control for H.323

CCPROXY

H.323 proxy

CDM

Cable Data Modem subsystem

CDMA_PDSN

CDMA PDSN

CDNLD_CLIENT

Client NRP2 configuration download

CDNLD_SERVER

Server NSP configuration download

CDP

Cisco Discovery Protocol (CDP)

CDSX_MODULE

Network module

CE3

CE3 port adapter (CE3)

CEIPNM

Circuit Emulation over IP Network Module

CERF

Cache Error Recovery Function (CERF)

CES

Circuit Emulation Service (CES)

CES_CLIENT

Client circuit emulation service (CESt

CES_CONN

TDM connection

CFG

Invalid Cisco 1840 configuration

CFGMGR

Configuration Manager


7


Table 1


Code

Facility

CFIB

Constellation FIB

CFM

Connectivity Fault Management

CHANNEL_BANK

Channel Bank

CHARLOTTE

Dual OC-3 PoS port adapter

CHKPT

Checkpoint facility

CHOC12

CHOC12 port adapter

CHOPIN

Versatile Interface Processor (VIP) Multi-channel Port Adapter

CHOPIN_ MAINBOARD_ ASYNC_PQII

Chopin Main Board Asynchronous driver

CHSTM1

CHSTM1

CI

Cisco 7500 platform chassis interface

CIOS

CMCC channel adapter Cisco IOS wrapper

CIP and CIP2

Channel Interface Processor (CIP) and enhanced CIP

CIPDUMP

CIP core dump

CIRRUS

CD2430 asynchronous controller

CIRRUS_PM

Slow-speed asynchronous/synchronous port module

CLAW

CMCC CIP for Common Link Access for Workstations (CLAW) facility

CLEAR

Clear facility

CLIENT_CLOCK_SYNC Clock synchronization server CLNS

OSI Connectionless Network Service

CLOCK

Clock and calendar

CLOCKSW

Cisco 6400 network clocking

CLS

Cisco link services (CNS)

CLSDR

Cisco link services (CNS) driver

CM622_CM155

ATM OC12 and QOC3 line card driver

CMAPP

Call Manager application

CMBPKM

Multimedia Cable Network System Partners, Ltd. (MNCNS), baseline privacy key management

CMCC

Cisco Mainframe Channel Connection (CMCC)

CM_DSPRM

Digital Signal Processor Resource Manager (DSPRM)

CM_MONITOR

UBR900 Cable Access Router Personal Monitor

CMP

Cluster Membership Protocol

CMPCTG

CMCC Logical Link Control Transmission Group

CNS

Cisco Networking Services (CNS)

CNS_AGENT_CFGCHG

Cisco Network Service (CNS) Configuration Change Agent

CNSAD_IPSEC_AGENT Cisco Network Service (CNS)/AD IPsec Agent


8


Table 1


Code

Facility

CNSES

Cisco Network Services Event Service client

COBALT

COBALT

COMMON_FIB

CEF address family independent (FIB)

COMP

Point-to-point compression

CONFIG

CMCC Channel Interface Processor (CIP) messages for the configuration processing facility

CONST_BOOT

Constellation boot

CONST_DIAG

On-line diagnostics

CONST_V6

IP version 6

CONTROLLER

Controller

COPTMONMIB

Cisco Optical Monitoring MIB

COT

Continuity test (COT)

COUGAR_EHSA

Pulse amplitude modulation (PAM) port driver

CP

Control plane protection notification

CPAD

Compression service adapter (CSA)

CPE_MMI

Customer Premises Equipment Modem Management Interface

CPM

Combo Port Module (CPM) device driver

CPOS

Packet-over-SONET

CPU_INTF_FPGA

CPU Interface FPGA

CPU_MONITOR

CPU monitor

CRYPTO

Encryption

CRYPTO_HA

Crypto High Availability

CRYPTO_HA_IKE


CRYPTO_HA_IPSEC


CSG

Content Services Gateway

CSM

Call switching module

CSM_TGRM

CSM TGRM interaction

CSM_TRUNK

Call switching trunk manager

CSM_VOICE

Call switching mode (CSM) voice subsystem

CT3

Channelized T3 (CT3) port adapter

CTA

CMCC CIP for the channel transport architecture device task/mapper

CTLPROVIDERSERV

CTL provider service

CTRC

Cisco Transaction Connection

CWAN_ALARM

Constellation WAN alarm

CWAN_ATM

Constellation WAN ATM

CWAN_HA

WAN module High Availability


9


Table 1


Code

Facility

CWAN_QINQ

Constellation CWAN-QINQ linecard

CWAN_RP

Constellation WAN ATM Route Processor driver

CWAN_SP

Constellation WAN ATM Switch Processor driver

CWAN_SPA

Shared Port Adapter on OSR

CWANLC

Constellation WAN line card

CWANLC_ATM

Constellation WAN ATM Route Processor driver

CWAN_POSEIDON

Optical Services Module (OSM) GE-WAN Route Processor (RP) driver

CWPA

Route Processor for Constellation Supervisor router module

CWPABRIDGE

CWPA bridging

CWRMP

Wireless radio point-to-multipoint driver

CWRPSPA

Shared Port Adapter on OSR RP

CWRSU

Wireless radio point-to-multipoint subscriber unit (SU)

CWRTEST

Wireless radio point-to-multipoint test driver

CWSLC

Constellation WAN SiByte module

CWTLC

Constellation Supervisor router module line card

CWTLC_ATM

ATM line card for Constellation Supervisor router module

CWTLC_ATOM

Constellation WAN Toaster linecard – AToM

CWTLC_CHOC

Cyclops Channelized OC48/OC12-related

CWTLC_CHOC_DSX

Optical Services Module (OSM) CHOC DSX LC common

CWTLC_CHOCX

Optical Services Module (OSM) Channelized OC12/OC3 Module

CWTLC_GEWAN

Gigabit Ethernet WAN Module

CWTLC_QOS

Optical Services Module (OSM) Supervisor line card QoS

CWTLC_RP

Catalyst 6500 Series Switch and Cisco 7600 Series Router WAN Toaster-based Module Route Processor

DAS_ENV

RSC environmental monitor subsystem

DBCONN

Database Connection

DBUS

Data bus

DCU

ATM access concentrator PCI port adapter

DEBUGGER

Debug mode

DEC21140

DEC21140 Fast Ethernet controller

DFC

Dial feature card

DFC_CARRIER

Dial feature card carrier

DFP

Dynamic Feedback Protocol

DHCP

Dynamic Host Configuration Protocol

DHCP_SNOOPING

DHCP snooping

DHCPD

Dynamic Host Configuration Protocol (DHCP) server


10


Table 1


Code

Facility

DHCPV6C

DHCPv6 client

DHCPV6S

DHCPv6 server

DIAG

CMCC CIP for diagnostic testing

DIALER

Dial-on-demand routing

DIALPEER_DB

Dial peer configuration

DIALSHELF

Dial shelf

DIRECTOR

Director server

DISKMIRROR

NSP disk mirror

DLC

Data-link control

DLSWC

Data-link switching (DLSw)

DLSWMasterSlave

Data-link switching (DLSw) core

DLSWP

Data-link switching (DLSw) peer module

DM

Diagnostic Monitor or Dispatch Manager

DMA

Direct memory access

DMTDSL

Digital/discrete multitone digital subscriber line (DMTDSL)

DNET

DECnet

DNLD

Auto-config/download

DNSSERVER

Domain Name System (DNS) server

DOSFS

DOS file system

DOS_TRACK

IP source tracker

DOT11

802.11 subsystem

DOT1Q

802.1q

DOT1X

802.1X authorization

DOT1X_MOD

Messages encountered in platform dependent code for 802.1x

DP83815

DP83815 10/100 Mbps Integrated PCI Ethernet Media Access Controller

DPM

AS5200 T1 BRIMUX

DRIP

Duplicate Ring Protocol

DRP

Director Response Protocol

DRVGRP

Interface driver

DS3E3SUNI

DS3E3SUNI driver

DS_MODEM

FB modem card

DS_TDM

Dial shelf time-division multiplexing

DS1337

DS1337 RTC

DSA

Delayed stop accounting

DSC

Dial shelf controller (DSC)

DSC_ENV

Cisco AS5800 environment monitor


11


Table 1


Code

Facility

DSC_ REDUNDANCY

Cisco AS5800 dial shelf controller (DSC) redundancy

DSCC4

DSCC4 driver

DSCCLOCK

Dial shelf controller (DSC) clock

DSCEXTCLK

Dial shelf controller (DSC) clock

DSCREDCLK

Dial shelf controller (DSC) redundancy clock

DSI

Cisco AS5800 dial shelf interconnect board

DSIP

Distributed system interconnect protocol

DSIP_IOSDIAG

DSIP diagnostic test

DSIPPF

Nitro Interconnect Protocol

DSLSAR

DSL segmentation and reassembly

DSM

DSP Stream Manager

DSMP

DSP Stream Manager

DSP_CONN

TDM connection

DSPDD

Digital Signal Processor Device Driver (DSPDD)

DSPDUMP

Digital Signal Processor crash dump facility

DSPFARM

DSP resource management

DSPRM

Digital Signal Processor Device Driver (DSPDD)

DSPU

Downstream physical unit

DSX0

CT1 RBS time slot status

DSX1

Channelized E1 (Europe) and T1(US) telephony standard

DS_TDM

Dial shelf time-division multiplexing (TDM)

DSXPNM

TE3 network module

DTP

Dynamic Trunking Protocol filtering

DUAL

Enhanced Interior Gateway Routing Protocol

DVMRP

Distance Vector Multicast Routing Protocol

E1T1_MODULE

E1T1 module

EAP

Extensible Authentication Protocol

EARL

Enhanced Address Recognition Logic

EARL_ACL_FPGA

Enhanced Address Recognition Logic ACL FPGA

EARL_DRV_API

EARL driver API

EARL_L2_ASIC

Enhanced Address Recognition Logic Layer 2 ASIC

EARL_L3_ASIC

Enhanced Address Recognition Logic Layer 3 ASIC

EARL_NETFLOW

Enhanced Address Recognition Logic NetFlow

EC

EtherChannel, Link Aggregation Control Protocol (LACP), and Port Aggregation Protocol (PAgP)

ECC

Single bit errors in ECC


12


Table 1


Code

Facility

ECPA and ECPA4

Escon Channel Port Adapter and enhanced Escon Channel Port Adapter

EGP

Exterior Gateway Protocol

EHSA

Cisco 6400 Enhanced High System Availability (EHSA)

EM

Event Manager

EM_FPGA

Cisco 1840 FPGA encryption, decryption and hash message authentication codes (HMAC) for IP Security (IPSec)

ENSP

Enhanced Network Services Provider (ENSP)

ENT_API

Entity MIB API

ENT_ALARM

Entity alarm

ENTITY_ALARM

Entity alarm

ENVM

Environmental monitor

ENV_MON

Cisco 12000 environmental monitor

ENVM

Environmental monitor

EOBC

Ethernet out-of-band channel

EOS

Eos ASIC

EOU

Extensible Authentication Protocol (EAP) over User Datagram Protocol (UDP)

EPAD

Encryption port adapter driver (EPAD)

EPLD

EPLD

EPLD_STATUS_OPEN

EPLD Programming Status File Data Processing

EPAMCM

Ethernet Port Adapter Module Configuration Manager

EPIF_PORT

MMC Networks Ethernet Port L3 Processor Port

ESCON

Enterprise Systems Connection

ESF_CRASHINFO

Extended SuperFrame crashinfo

ESF_DRIVER

SIP-400 ESF driver

ESF_IPC

IPX2800 IPC

ESWILP_CFG

Ethernet switch module configuration

ESWILP_FLTMG

ESWILP fault management

ESWITCH

Ethernet switch port adapter

ESWMOD

Ethernet switch module

ESWMRVL_FLTMG

Ethernet switch fault management

ESW_STORM_ CONTROL

Storm control

ESW_WIC_FLTMG

Ethernet Switch WIC fault management

ET2_MODULE

Ernest-T2 network module

ETHERNET

Ethernet for the C1000 series

EVENT

Event MIB


13


Table 1


Code

Facility

EVENT_TRACE

Event trace subsystem

EXFREE

External memory manager

EXPRESSION

Expression MIB

FABRIC

Fabric Interface ASIC (FIA)

FALLBACK

Voice over IP (VoIP) fallback

FAN

Fan

FARM_DSPRM

Farm DSPRM

FASTBLK

Fast Block

FB

Cisco AS5800 feature board

FB_COREDUMP

Feature board core dump

FBINFO

Cisco AS5800 feature board crash information subsystem

FCIP

FCIP driver

FCL

Forward Control Layer (FCL)

FDDI

Fiber Distributed Data Interface (FDDI)

FDM

Firewall Service Module (FWSM) Device Manager

FDM_HA

High availability FWSM Device Manager

FECPM

Fast Ethernet (FE) Combination Port Module (CPM) device driver

FESMIC_FLTMG

FESMIC fault management-related

FF

FF module-specific

FIB

Forwarding Information Base

FIB_HM

FIB health monitor

FIB_HM_MVL

Platform dependent, FIB Health Monitor

FILESYS

File system

FIO_TDM

Messages related to the Cisco 3700XM TDM device

FLASH

Flash nonvolatile memory

FLEX_DNLD

Voice Over IP (VoIP) driver

FLEXDSPRM

Flex DSPRM operation

FM

Feature Manager (FM)

FM

Forwarding Manager (FM)

FMCORE

Core Feature Manager

FM_EARL6

EARL 6 Feature Manager

FM_EARL7

EARL 7 Feature Manager

FPD_MGMT

FPD Management Subsystem

FPGA

LS1010 chip-specific

FR

Frame Relay

FR_ADJ

Frame Relay Adjacency


14


Table 1


Code

Facility

FR_ELMI

Frame Relay enhanced Local Management Interface

FR_FRAG

Frame Relay Fragmentation

FR_LMI

Frame Relay Local Management Interface

FR_RP

Frame Relay RP

FR_VCB

Frame Relay VC bundle

FRATM

Frame Relay ATM

FREEDM

CT3 trunk card Freedm

FS_IPHC

Fast IP Header Compression

FTC_TRUNK

Cisco 3801 platform

FTPSERVER

FTP server processes

FTSP

Fax Telephony Service Provider subsystem

FTTM

Full Ternary TCAM Manager

FW

Inspection subsystem

FW_HA

Firewall High Availability

FX1000

FX1000 Gigabit Ethernet controller

GBIC_SECURITY

GBIC security check

GBIC_SECURITY_CRY PT

GBIC SECURITY serial EEPROM verification

GBIC_SECURITY_UNI QUE

GBIC security uniqueness verification

GDOI

Group Domain of Interpretation

GE

Gigabit Ethernet subsystem

GENERAL

Zenith route processor

GET_DATA

CMCC CIP for allocating transfer elements

GK

GK-H.323 Gatekeeper

GK_OSP

H.323 Gatekeeper OSP

GLBP

Gateway Load Balancing Protocol

GLCFR

Internet router

GPRSFLTMG

Global Packet Radio Service fault management

GPRSMIB

Global Packet Radio Service MIB

GRIP

Xerox Network Systems (XNS) Routing Protocol

GRP

Gigabit Route Processor

GRP_C10K_CH_DS3

Cisco 10000 CH-DS3 RP driver

GRP_OC12_CH_DS3

Gigabit Route Processor (GRP) driver

GRPGE

Gigabit Ethernet Route Processor (RP)

GRPPOS

POS Route Processor

GSHDSL

G.Symetric High DSL


15


Table 1


Code

Facility

GSI

G.Symetric high bit rate DSL

GSR_ENV

Internet router environment monitor

GSRIPC

Internet router IPC service routines

GT64010

GT64010 DMA controller driver

GT64011


GT64120


GT96K_FE

Cisco 3700 series and Cisco 3631 systems controller

GT96K_FEWAN

Cisco 3700 series and Cisco 3631 systems controller for WAN

GT96K_TDM

Cisco 37xx, Cisco 2691, and Cisco 3631 TDM subsystem

GTP

GPRS Tunnel Protocol

GUIDO

GUIDO network module

HA

High availability system

HA_CLIENT

High availability client

HA_EM

Embedded Event Manager

HA_IFINDEX

High Availability system

HAL

Halcyon

HARDWARE

Hardware resources

HA_WD

High Availability system

HAWKEYE

Token Ring PCI port adapter

HD

HD64570 serial controller

HDLC

High-Level Data Link Control

HDLC32

PAS HDLC32

HDV

High Density Voice (HDV) driver

HDV2

HDV2 network module

HDX

Half-duplex (HDX) finite state machines (FSM)

HEALTH_MONITOR

Health Monitor

HEARTBEAT

Heartbeat

HHM

Cisco AS5400 health monitor

HIFN79XX

Hifn 79xx

HLFM

Forwarding Manager

HMM_ASYNC

Hex modem network module asynchronous driver

HOOD

LAN controller 100VG-AnyLAN interface

HP100VG

100VG-AnyLAN port adapter driver

HPI

Host Port Interface

HSRP

Hot Standby Router Protocol (HSRP)

HTSP

Analog voice hardware adaptation layer software


16


Table 1


Code

Facility

HTTP

Hypertext Transfer Protocol (HTTP)

HTTPC

HTTP client

HUB

Cisco Ethernet hub

HW

Hardware

HW_API

Hardware API

HW_VPN

Encryption Advanced Interface Module (EAIM)

HWECAN

HWECAN echo canceller

HWIC_1GE_SFP

Gigabit Ethernet High-speed WAN Interface Card (HWIC)

HWIC_ADSL

HWIC ADSL

HWIC_ADSL_BRI

HWIC ADSL/BRI

HWIC_BRI

HWIC BRI

HWIC_HOST

High-speed WAN Interface Card (HWIC) Host Driver Library

HWIC_SERIAL

High-speed WAN Interface Card (HWIC) Serial Device Driver

HWIF_QOS

HWIF QoS

HYPERION

Hyperion ASIC

I82541

Intel 82541 Ethernet/Fast Ethernet/Gigabit Ethernet controller

I82543

Intel 82543 Ethernet/Fast Ethernet/Gigabit Ethernet controller

I82544

I82544 Fast Ethernet controller

I82559FE

Intel 82559 Fast Ethernet controller

IAD2420_VOICEPORT

IAD2420 Voice Port

IBM2692

IBM Token Ring chipset

ICC

Inter-Card Communication

IDBINDEX_SYNC

Interface Descriptor Block (IDB) index synchronization

IDBMAN

Interface description block manager

IDCONF

Intrusion Detection Configuration

IDMGR

ID manager

IDNLD

NSP IDNLD

IDS

IP datagram subsystem (IDS)

IDTATM25

IDT ATM25 network module

IEDGE

Intelligent Services Gateway (ISG)

IF

Interface

IFINDEX

SNMP IF_MIB persistence

IFMGR

Interface Manager

IFS

Cisco IOS file system

IGRP

Interior Gateway Routing Protocol

ILACC

ILACC driver


17


Table 1


Code

Facility

ILPM_FAULT

Inline Power Management (ILPM)-related

ILPOWER

Inline power

IMA

Inverse multiplexing over ATM (IMA)

IMAGEMGR

Image manager

IMAGE_SIMFS

In-Memory System Image File System

IMAGE_VFS

Image Virtual File System

INBAND

Inband management

INDXOBJ

Index object

INSTANCE_LOG

Instance log

INT

CIP for the interrupt handler interface

INTERFACE_API

Binary API for the interface descriptor block

INTR_MGR

Interrupt manager

IOCARD

I/O card-specific

IOS_RESILIENCE

Cisco IOS software image and configuration resilience

IP

Internet Protocol

IP_DEVICE_ TRACKING

Switch IP Host Tracking

IP_DEVICE_ TRACKING_HA

Switch IP Host Tracking HA

IPA

Intelligent port adapter

IPACCESS

IP security

IPC

Interprocess communication

IPC_DRVR

CMCC interprocess communication driver

IPCGRP

Route Processor (RP) interprocess communication (IPC)

IPCOIR

IPC Online Insertion and Removal (OIR)

IPC_RPM

Interprocess communication (IPC)

IPC_RSP_CBUS

Interprocess communication ciscoBus (CBUS)

IPC_URM

Interprocess communication universal router module

IPCLC

Internet router line card interprocess communication

IPDCAPP

Internet Protocol Device Control application

IPFAST

IP fast switching

IPFLOW

IP flow

IPM_C54X

Voice over IP (VoIP) driver

IPM_DSPRM

Digital Signal Processor (DSP) Resource Manager

IPM_NV_EEPROM

Integrated port module NVRAM driver

IPMCAST

Cisco 12000 series Internet router line card IP multicast

IPMCAST_LIB

IP Multicast library


18


Table 1


Code

Facility

IPMOBILE

IP Mobility

IPNAT

IP Network Address Translation

IPP

CMCC encryption feature

IPPHONE

IP Phone register/unregister

IPRT

IP routing

IPS

Intrusion prevention system

IPSECV6

Encryption feature

IP_SNMP

Simple Network Management Protocol specific to IP

IPV6

IP version 6

IPV6FIB

IP version 6 forwarding-based on destination IP addresses

IPV6_FW

IPv6 Inspection subsystem

IPV6_VFR

IPv6 virtual fragment reassembly subsystem

IPV6_VRF

VRF common

IP_VFR

IP Virtual Fragment Reassembly (VFR) subsystem

IP_VRF

IP VPN routing/forwarding instance common

IPX

Novell Internetwork Packet Exchange Protocol (IPX)

IRECAGENTSERVER

IREC agent server

IRONBUS

Iron bus

ISA

Integrated Services Adapter (ISA)

ISDN

Integrated Services Digital Network (ISDN)

ISRHOG

Interrupt Service Routine Hog

ISSU

In Service Software Upgrade

ISSU_CS

ISSU configuration synchronization

IUA

ISDN User Adaptation Layer

IVR

Interactive Voice Response (IVR)

IVR_MSB

Media Stream module

IVR_NOSIGNALING

Interactive Voice Response (IVR) system messages not related to call signaling

IXP1200_CP

One port Fast Ethernet with coprocessor assist

IXP_MAP

ESF Network Processor Client Mapper

JAGGER

Constellation WAN line card

JETFIRE_SM

NAM Sensor network module

KERBEROS

Voice over IP (VoIP) for Cisco AS5800

KEYMAN

Keystring encryption

KINEPAK

Voice over IP (VoIP) for Cisco AS5800

L2

Layer 2


19


Table 1


Code

Facility

L2_AGING

Layer 2 aging

L2_APPL

Layer 2 application

L2_ASIC

Layer 2 forwarding engine

L2CAC

Layer 2 CAC

L2HW_CM

Layer 2 hardware connection manager

L2R

L2RLY

L3_ASIC

Layer 3 CEF engine

L3MM

Layer 3 Mobility Manager

L3_MGR

Layer 3 manager

L3TCAM

Layer 3 TCAM manager

LANCE

Local Area Network Controller Ethernet

LANE

LAN Emulation

LANMGR

IBM LAN Network Manager

LAPB

X.25 Link Access Procedure, Balanced

LAPP_OFF

Fax offramp calls

LAPP_ON_MSGS

Fax onramp calls

LAT

DEC local-area transport

LC

Line card

LC_10G

Hamptons 10G trunk card

LC_2P5G

Hamptons 2.6G trunk card

LCB

Line Control Block (LCB) event process

LCCEF

ATM Cisco Express Forwarding (CEF) adjacency

LCCOREDUMP

Line card core dump subsystems

LCFE

Fast Ethernet line card (LC) driver

LCGE

Gigabit Ethernet line card (LC) driver

LCINFO

Line card crash information subsystem

LCLOG

Internet router line card logger subsystem

LCMDC

ONS 15540 Extended Services Platform

LCOC12_CH_DS3

Internet router OC-12-channelized-to-D3 line card

LCPLIM

Line card physical layer interface module

LCPOS

Packet over SONET (POS) line card driver

LCR

Line card registry

LCRED

LC and Port redundancy

LDP

Label Distribution Protocol (LDP)

LES_FDDI

LAN Emulation Server/Fiber Distributed Data Interface

LEX

LAN extension


20


Table 1


Code

Facility

LFD

Label Forwarding Database

LFD

MFI Label Switching Database (LFD)

LIBT2F

Text to fax library

LIBTIFF

Tagged Image File Format (TIFF) library

LINECARD

Node Route Processor (NRP) line card

LINEPROTO

Line Protocol

LINK

Data link

LLC

Logical Link Control (LLC), type 2

LLDP

Link Layer Discovery Protocol

LLIST

Linked list facility

LNM

Link noise monitor for the E1T1 module

LNMC

LAN network manager

LOADER

CIP for relocating loader facility

LOGIN

Login

LOVE

Statistics from the CIP to the router

LPD

Line printer daemon

LRE

Long Reach Ethernet for the Catalyst 2950 switch

LSD

MPLS Forwarding Infrastructure (MFI) Label Switching Database

LSPV

MPLS Label-Switched Path Verification

LSS

LS switching message definition

M32X

M32X Basic Rate Interface trunk card

MAC_LIMIT

MAC address table entries

MAC_MOVE

Host activity

MAILBOX

ChipCom mailbox support

MARS_NETCLK

Network clock system

MARVEL_HM

Platform-dependent health monitor rules

MASTER_LED

Master LED

MBRI

Multi-BRI port modules

MBUF

CMCC memory buffer

MBUS

CMCC maintenance bus (MBus)

MBUS_SYS

Maintenance bus (MBus) system

MC3810_DSX1

MC3810 DSX1 subsystem

MCAST

Layer 2 multicast

MCT1E1

CT1/CE1 shared port adapter

MCX

Voice port adapter

MDEBUG

Memory debug


21


Table 1


Code

Facility

MDR_SM

Minimum Disruption Restart State Machine

MDS

Multicast distributed switching

MDT

PIM MDT

MDX MEM_ECC

Memory write parity errors detected by ECC control

MEM_HM

Memory health monitor

MEMD

CMCC CIP related to the memory device facility

MEM_MGR

Memory management

MEMPOOL

Enhanced Memory pool MIB

MEMSCAN

Memory scan

METOPT

ONS 15540 Extended Services Platform

METS

Memory-leak analysis

MFI

MPLS Forwarding Infrastructure

MFIB

Multicast Forwarding Information Base

MFIB_CONST_LC

MFIB-Constellation platform

MFIB_CONST_RP

MFIB Constellation information

MFIB_STATS

MFIB statistics

MGCP

Media Gateway Control Protocol (MGCP)

MGCP_APP

Media Gateway Control Protocol (MGCP) application-specific

MGCP_RF

Media Gateway Control Protocol (MGCP) High Availability

MHA

Marvel high availability

MHA_LINE

Marvel high availability line

MHA_MODE

Marvel high availability

MHA_RF

Marvel high availability redundancy feature

MIC

Port adapter

MICA

Modem ISDN Channel Aggregation (MICA)

MIF68840

PCI MC68840 FDDI port adapter

MIMIC

MCOM integrated modem network modules

MIPC

Marvel IPC

MISA

Multiple Crypto Engine subsystem

MISTRAL

Mistral ASIC

MK5

MK5025 serial controller

MLD_PROT

Multicast Listener Discovery

MLOAD

Module Loader

MLS_ACL_COMMON

Multilayer switching ACL

MLS_RATE

Multilayer Switching Rate Limit


22


Table 1


Code

Facility

MLSCEF

Multilayer Switching Cisco Express Forwarding

MLSM

Multilayer Switching Multicast

MMLS

Multicast Multilayer Switching

MMLS_RATE

Multicast Multilayer Switching Rate Limit

MMODEM

Integrated modem network module

MODEM

Router shelf modem management

MODEM_HIST

Router shelf modem history and tracing

MODEM_NV

Modem NVRAM

MODEM_CALLREC

Modem call record

MODEMCALL RECORD

Modem Call Record

MOHAWK_SM

IDS sensor network module

MONITOR

Cisco IOS software ROM monitor

MOTCR

Hardware accelerator for IPSec

MPA68360

VIP Multi-channel Port Adapter

MPC

Multipath Channel Protocol

MPF

Multi-Processor Forwarding (MPF)

MPLS

Multiprotocol Label Switching

MPLS_ATM_TRANS

ATM Transport over MPLS

MPLS_PACKET

MPLS packet

MPLS_TE

Label Switch Path (LSP) tunnel

MPLS_TE_PCALC

MPLS TE path calculation facility

MPOA

Multiprotocol over ATM (MPOA)

MPLSOAM

MPLS management

MRIB

Multicast Routing Information Base

MRIB_API

MRIB client API

MRIB_PROXY

MRIB proxy

MROUTE

Multicast route

MSACDSPRM

Media Conferencing DSP Resource Manager

MSC100_SPA_CC

Cisco 7304 SPA carrier card

MSDP

Multicast Source Discovery Protocol

MSDSPRM

Media Services DSP Resource Manager

MSFC2

Multilayer Switch Feature Card 2

MSFW

Media Services DSP Firmware Manager

MSG802

CMCC CIP 802 for IEE 802.2cx LLC Protocol

MSPI

Mail Service Provider


23


Table 1


Code

Facility

MTRIE

Mtrie

MUESLIX

Mx serial application-specific integrated circuit (ASIC)

MV64340_ETHERNET

MV64340 Ethernet controller

MVR_RP

Multicast VLAN Registration (MVR) route processor

MWAM

Multiprocessor WAN Application Module (MWAM)

MWAM_FILESYSTEM

Multiprocessor WAN Application Module (MWAM) crashinfo and bootflash file system

MWAM_FLASH

Multiprocessor WAN Application Module (MWAM) flash memory

MWAM_FUR

Multiprocessor WAN Application Module (MWAM) FUR

MWAM_NVRAM

Multiprocessor WAN Application Module (MWAM) NVRAM

MWAM_VRTC

Multiprocessor WAN Application Module (MWAM) VTRC

MWR1900_QOS_ GENERAL

MWR1900 Quality of Service (QoS)

MWR1900_CFG_ GENERAL

MWR1900 PXF queuing configuration

MWR1900_ REDUNDANCY

MWR1900 redundancy

MXT_FREEDM

8PRI/4T board

NATMIB_HELPER

NAT MIB helper

NBAR

Network-based application recognition (NBAR)

NETFLOW_ AGGREGATION

NetFlow aggregation

NETGX_CRYPTO

NETGX CRYPTO hardware accelerator module for IPsec

NET_SERV

Networking Services

NETWORK_CLOCK_ SYNCHRONIZATION

Network clock synchronization

NETWORK_PORT_SAT ELLITE

Network port satellite

NETWORK_RF_API

Network redundancy feature API

NEVADA

CMCC CIP interrupt controller

NHRP

Next Hop Resolution Protocol (NHRP)

NIM

Network interface module

NM_8_16AM_V2_ MODULE

NM-8/16AM-V2 module

NP

NextPort (NP)

NP_BS

NextPort (NP) Bootstrap and Crash Monitor

NP_CLIENT

NextPort (NP) client

NP_DDSM

NextPort (NP) Digital Data Services Manager


24


Table 1


Code

Facility

NP_DSPLIB

NextPort (NP) DSPLIB

NP_EST

NextPort (NP) error, status, and trace

NP_MD

NextPort (NP) modem driver

NP_MM

NextPort (NP) module manager

NP_SIGLIB

NextPort (NP) signaling library

NP_SPE_DS

NextPort (NP) Dial Shelf Service Processing Element (SPE) Manager

NP_SSM

NextPort (NP) Session and Service Manager

NP_UCODE

NextPort (NP) microcode

NP_VPD

NextPort (NP) Voice Packet Driver

NP_VSM

NextPort (NP) Voice Service Manager

NRP

Network Routing Processor (NRP)

NRP2

Network Route Processor, type 2

NRP2_NVMANAGE

Network Route Processor, type 2 NVRAM management

NRP2_SE64

SE64 upper and lower layer device driver

NRP2EHSA

NRP2 EHSA

NSE

Network services engine

NSE100

Network services engine NSE100

NSP

Network Switch Processor (NSP)

NSP_APS

Cisco 6400 node switch processor (NSP)

NSP_DISK

NSP disk

NSP_OIR

Cisco 6400 online insertion and removal (OIR)

NSPINT

Network switch processor (NSP) interrupt infrastructure

NTP

Network Time Protocol (NTP)

OBFL

Onboard Failure Logging

OCE

Output chain elements

ODM

Online diagnostics manager

OER_BR

Optimized Edge Routing (OER) border router

OER_MC

Optimized Edge Routing (OER) master controller

OER_TT_FLOW

Optimized Edge Routing (OER) top talkers flow border router

OIR

Online insertion and removal (OIR)

OLM

Optical Link Management

ON_DIAG

Online diagnostics subsystem

ONLINE

SCP (Switch-module Configuration Protocol) download processor

ONS15530

Cisco ONS 15530 trunk card

OOBP

Out-of-band port (OOBP)

OPTICAL_MONITOR

Optical monitoring


25


Table 1


Code

Facility

OSM_MULTILINK

Optical Services Module (OSM) distributed multilink

OSPF

Open Shortest Path First (OSPF)

OSPFv3

Open Shortest Path First version 3

P2IPC

Fast IPC event

P2IPC_TRACE

Fast IPC trace

PA

Port adapter

PACC

Cisco 7300 port adapter carrier card (PACC)

PACC_IPC

Port Adapter Carrier Card (PACC) interprocess communication (IPC)

PACKET

Packet

PAD

X.25 packet assembler/disassembler

PAGP_DUAL_ACTIVE

Port aggregation protocol (PAgP)

PAMMBOX

Platform-independent PAM mailbox serial interface

PARSE_RC

Parser return code

PARSER

Parser

PBI_OPEN

Programmable Binary File (PBI) Data Processing

PBR

Policy Based Routing

PCI_FE

PCI Fast Ethernet

PCMCIAFS

PCMCIA disk

PCPA

Parallel Channel Port Adapter

PDSN_CLUSTER

PDSN cluster controller or PDSN cluster member

PERUSER

PPP per-user configuration

PF

Protocol filtering

PFINIT

Platform initialization

PF_OBFL

Platform onboard failure logging

PFREDUN

Policy Feature Card Redundancy

PGM

Pragmatic General Multicast (PGM)

PGMHOST

Pragmatic General Multicast (PGM) host module

PHY

Physical layer

PIF

RSC PIF

PIM

Protocol Independent Multicast

PIMP

Process interrupt mask profiler

PIMSN

Protocol Independent Multicast Snooping

PIM_PROT


PIM_REG_TUN

PIM register tunnel

PIMSN

PIM snooping

PINNACLE

Pinnacle ASIC


26


Table 1


Code

Facility

PKI

PKI feature

PLAT_MP

Platform MP support

PLATFORM

Platform-specific

PLATFORM_IMAGE _ PREFIX

Multilayer Switch Feature Card (MSFC)

PM

Port Manager

PM3387

One-port Gigabit Ethernet HWIC-1GE-SFP

PM_DB_HA

Port management database high-availability client

PMIP

WLAN Proxy Mobile IP Subsystem

PM_MODEM_HIST

Modem history and tracing

PM_MODEM_MAINT

Modem maintenance

PM_SCP

Port manager Switch-Module Configuration Protocol

PMSN

Port State Machine

PNNI

Private Network-Network Interface

POLICY_API

Policy API

POLICY_MANAGER

Policy Manager

PORT

Port Management

PORT_SECURITY

Port security

POS

Packet over SONET subsystem

POS_GIGE

Packet over SONET Gigabit Ethernet

POSDW

Packet over SONET double-wide PCI port adapter driver

POSLC

Packet over SONET line card

POT1E1

Versatile Interface Processor (VIP) multichannel port adapter

POTS

Plain old telephone service (POTS)

PPP

Point-to-Point Protocol (PPP)

PQ3_TSEC

PQ3 TSEC

PQII

MPC860 quad integrated communications controller

PQUICC

MPC860 quad integrated communications controller

PQUICC_ASYNC

Asynchronous MPC860 quad integrated communications controller

PQUICC_ASYNC_ NOMEM

Integrated Port Module Asynchronous Driver

PQUICC_ETHER

Ethernet MPC860 quad integrated communications controller

PQUICC_ ETHERNET

Ethernet MPC860 quad integrated communications controller

PQUICC_FE

Fast Ethernet MPC860 quad integrated communications controller

PQUICC_SERIAL

Serial MPC860 quad integrated communications controller

PQUICC3

MPC8500 PowerQUICC3


27


Table 1


Code

Facility

PRBS

Pseudo-random bit sequence

PROCYON

CPU daughter card for the Supervisor Engine 720

PS

Power supply

PTRANSFORM

Protocol transformation

PT

Protocol Translation

PV

Private VLAN

PVDM2

PVDM2 SIMM

PW_WATCHER

Portware Watcher

PXF

Parallel eXpress Forwarding (PXF)

PXF_ACL

Parallel eXpress Forwarding (PXF) ACL-specific

PXFAPI

Parallel eXpress Forwarding (PXF) API-related

PXF_DMA

Parallel eXpress Forwarding (PXF) DMA subsystem

PXF_FIB

Parallel eXpress Forwarding (PXF) FIB select-specific

PXF_FLOW

Parallel eXpress Forwarding (PXF) Netflow-related

PXF_GEC

PXF EtherChannel

PXF_GRE

Parallel eXpress Forwarding (PXF) GRE tunnel-related

PXF_NAT

Parallel eXpress Forwarding (PXF) Network Address Translation (NAT)-related

PXF_QOS

Parallel eXpress Forwarding (PXF) Quality of Service (QoS)-related

PXF_VRFS

Parallel eXpress Forwarding (PXF) VRF selection-specific

QA

Queue and accumulator

QEM

QEM driver

QLLC

Qualified Logical Link Control

QM

Quality of service management

QNQ

Q-in-Q

QOS

Quality of Service

QOSMGR

Quality of Service (QoS) manager

QUICC

MC68360 quad integrated communications controller

QUICC_ASYNC

Asynchronous MC68360 quad integrated communications controller

QUICC_ETHER

Ethernet MC68360 quad integrated communications controller

QUICC_SERIAL

Serial MC68360 quad integrated communications controller

R4K_MP

Central processing unit

RAC

Ring Access Controller

RADIO

Radio driver

RADIO_DRIVER

Radio driver

RADIUS

RADIUS


28


Table 1


Code

Facility

RADIX

Radix

RADSRV

Embedded RADIUS server

RAIKO

RAIKO-based feature board

RANDOM

Random number generator

RASP16

Interface Multiplexer ASIC

RBCP

Router Blade Control Protocol

RCMD

Remote command

RE

RE subsystem

RECONCILIATION_HA

Reconciliation high availability

RED

Redundancy-related

RED_MODE

High-availability redundancy mode

RED_REMOTE

Redundancy remote

REDUNDANCY

High Availability redundancy

REDUNDANCY_UTILS

High Availability redundancy utilities

Regen

Cisco optical regenerator

Regen_MAINBOARD_ ASYNC_PQUICC

Asynchronous MPC860 quad integrated communications controller for the Cisco optical regenerator

REGISTRY

Registry

RESOURCE_MGR

Resource manager

RESOURCE_MON

Resource monitor subsystem

RESYNCH

Route Processor Module (RPM) resynchronization process

RF

Redundancy facility

RF_INTERDEV

Redundancy facility (RF) interdevice

RF_ISSU

Redundancy facility (RF) In Service Software Upgrade

RFS

Remote file system

RIM

Redundant Interface Manager (RIM)

RIP

IP Routing Information Protocol (RIP)

RITE

IP traffic export

RLM

Redundant Link Manager (RLM)

RM

Resource Manager

RMON

Remote Monitoring Protocol

ROUTEMAP

Route map

ROUTEMAP_IPC

Route map interprocess communication (IPC)

RPA

Resource Pool Allocation (RPA)

RPC

Remote Procedure Call (RPC)

RPF

Multicast RPF


29


Table 1


Code

Facility

RPM

Route Processor Module (RPM)

RPB_BKCD

RPM back card

RPM_BULK

RPM-specific bulk file

RPM_CONFIG_COPY

RPM config copy feature

RPM_CONN_MGMT

RPM Connection Management-related

RP_MLP

Distributed Point-to-Point Protocol (PPP) Multilink

RPM_RED

RPM redundancy

RPM_TRAP_CLIENT

RPM trap client

RPM_VIRTUAL

Route Processor Module (RPM) virtual port

RPM_VIRTUAL_ PORT

RPM virtual port

RPMXF

Route Processor Module, express forwarding (RPM-XF) card level

RPMXF_DMLP

Route Processor Module, express forwarding DMLP configuration

RPMXF_QOS_ GENERAL

Route Processor Module, express forwarding (RPM-XF) Quality of Service (QoS)

RPMXF_QUEUE_CFG_ GENERAL

Route Processor Module, express forwarding (RPM-XF) queuing configuration

RPMXF_QUEUE_CFG_ STR

Route Processor Module, express forwarding (RPM-XF) queuing configuration

RPMXF_TOASTER

Route Processor Module, express forwarding (RPM-XF) Toaster

RPMXFEVENTMGR

Route Processor Module, express forwarding (RPM-XF) event manager subsystem

RPS

Redundant power system

RS_TDM

Router shelf time-division multiplexing

RRR_PCALC

Routing with Resource Reservation (RRR) path calculation

RSC

Route Switch Controller (RSC)

RSC_CF

Compact flash error

RSC_FPFE_IOSDIAGS

RSC front panel Fast Ethernet IOS diagnostics

RSC_MBUS

MBus on RSC

RSC_PIF_IOSDIAGS

Cisco IOS diagnostic test

RSCMSM

Resource Measurement

RSCPB

RSC push button

RSP

Route Switch Processor

RSP_ISSU

Cisco 7500 In Service Software Upgrade system

RSRB

Remote source-route bridging

RSVP

RSVP protocol

RSVP_HA

RSVP protocol high availability


30


Table 1


Code

Facility

RTT

Round-trip time monitor

RUDP

Reliable User Datagram Protocol

RUNCFGSYNC

Auto-Running Configuration Synchronization

RVTCVT_INFO

RVT/CVT Runtime Informational messages

RW_TOO_LONG

Windstar MPLS rewrite

S4T68360

Four-port synchronous serial adapter based on the 68360 processor

SASL

Simple Authentication and Security Layer

SARMGR

Segmentation and reassembly (SARMGR)

SATVS

Satellite Switch Virtual Switch (VS)

SBETH

MAC controller (SBETH)

SBFIFO

Packet first-in, first-out (FIFO) MAC controller

SCCP

Signaling connection control part

SCHED

Scheduler

SCP

Downstream physical unit (DSPU)

SDEE

SDEE subsystem

SDLC

Synchronous Data Link Control

SDLLC

Synchronous Data Logical Link Control (SDLLC) Logical Link Control Type 2 (LLC2) translation

SDP

Session Description Protocol

SDLC

GSHDSL

SDM

Security Device Manager

SDSPFARM

SDSP FARM register and unregister

SEC

IP security

SEC_LOGIN

Secure login

SENSOR

Voltage and temperature sensor

SERIAL

WS SERIAL line card

SERVER_CLOCK_ SYNC

Clock synchronization service

SERVICE_MODULE

Service module

SERVICEMODULE

Service module monitor

SFF8472

Floating-point subsystem (SFF8472)

SFP

SFP

SFP_SECURITY

SFP Security

SGBP

Stack Group Bidding Protocol

SGCP

Simple Gateway Control Protocol (SGCP)

SGCP_APP

Simple Gateway Control Protocol (SGCP) application-related

SGPRSWARNING

SGPRS warning


31


Table 1


Code

Facility

SHELF

Router shelf

SHMWIN

Shared memory

SIBYTE

SiByte processor complex

SIGSM

Signaling Service Manager

SIP

Session Initiation Protocol

SIP200


SIP400


SIP600


SIP600_PARSING_ ENGINE

SIP-600 parsing engine

SIP600_QOS

SIP-600 QoS

SIPSPA

Shared Port Adapter on GSR line card

SKINNYSECURE SERVER

Skinny secure server

SKINNYSECURE SERVICE

Skinny secure service

SKINNYSERVER

Skinny server

SLB

Server load balancing

SLB_DFP

Server Load Balancing Dynamic Feedback Protocol agent

SLICE_TOASTER

Slice

SLIP

Serial Line Internet Protocol

SLOT

AS5850 slot state machine and OIR-related events

SLOT_FPD

Common line card FPD

SLOT_HM

RSC slot health monitor

SLOTDUMP

Slot dump

SM

State machine (SM)

SMC

Services Management Channel

SMF

Software MAC Filter

SMIC

2FE2W, 1FE2W, 1FE1R2W, 2W network module-related

SMRP

Simple Multicast Routing Protocol

SMSC_RP

Short message service center route processor

SNAPSHOT

Snapshot dial-on-demand routing

SNASW

Systems Network Architecture (SNA) Switching Services

SNMP

Simple Network Management Protocol (SNMP)

SNMP_BULKSTAT

SNMP bulk-data collection

SNMP_MGR

Simple Network Management Protocol (SNMP) proxy


32


Table 1


Code

Facility

SOI

Simple Network Management Protocol (SNMP) over interprocess communication (IPC)

SONET

Synchronous Optical Network

SONETMIB

Synchronous Optical Network Management Information Base

SONICT

SONIC Ethernet driver

SPA

Shared Port Adapter (SPA)

SPA_CCB

SPA CCB command

SPA_CHOC_DSX

Common Channelized Shared Port Adapter

SPA_CHOCX


SPA_CHOCX_CWRP


SPA_CONSOLE

Shared Port Adapter (SPA) virtual console

SPA_CT3

CT3 Shared Port Adapter

SPA_DATABUS

SPA data bus interface

SPA_EEPROM

Shared Port Adapter (SPA) EEPROM

SPA_ETHER

Ethernet Shared Port Adapter

SPA_FPD

Shared Port Adapter (SPA) field-programmable device (FPD)

SPA_HA

SPA High Availability

SPA_IPSEC

IPsec SPA Card (SPA-IPSEC)

SPA_MIB

SPA MIB

SPA_OIR

Shared Port Adapter (SPA) online insertion and removal (OIR)

SPA_PLIM

Shared Port Adapter (SPA) physical layer interface module

SPA_PLUGIN

Shared Port Adapter (SPA) plugin

SPA_PMB

SPA specific power management bus

SPA_T3E3

Shared Port Adapter (SPA) T3E3

SPACP

SPA CP

SPAN

Spanning Tree Protocol

SPANTREE

Spanning Tree

SPANTREE_FAST

Spanning Tree Fast Convergence

SPANTREE_VLAN_SW

Spanning Tree VLAN switch

SPARC

3800 SPARC coprocessor subsystem

SPE

Service Processing Element (SPE)

SRC

Switch Redundancy Controller

SRCP_APP

Simple Resource Coordination Protocol (SRCP) application

SRP

Spatial Reuse Protocol (SRP)

SRPMIB

Spatial Reuse Protocol (SRP) MIB

SSA

Super Santa Ana ASIC


33


Table 1


Code

Facility

SSE

Silicon switching engine

SSG

Service Selection Gateway

SSH

Secure Shell (SSH) Protocol

SSI

SSI event

SSLVPN

SSL-based VPN

SSP

State Synchronization Protocol Manager

SSRP

SONET/SDH based SRP Double Wide PCI port adapter driver

SSSMGR

Subscriber Service Switching (SSS) Manager

STACKMGR

Stack manager controller

STAPL_OPEN

Standard Test And Programming Language (STAPL) Processing

STANDBY

Hot Standby Router Protocol (HSRP)

STORM_CONTROL

Storm control

STRING

String database

STUN

Serial tunneling

SUBSYS

Software subsystems

SUPERVISOR

Supervisor

SUPQ

Supervisor queue

SUPW_PROCMIB

Supervisor MIB

SVCLC

Service line card (SVCLC) firewall SP

SW56

Switch 56K

SW_DAI

Dynamic ARP Inspection

SWEPA

Software encryption port adapter and key management

SWITCH

Switch interface

SWITCH_IF

Switch interface subsystem

SWITCHOVER

Line card switchover-related

SWITCH_QOS_TB

Quality of Service rusted boundary

SW_MGR

Segment switch manager

SW_VLAN

Virtual LAN (VLAN) manager

SYS

Operating system

SYSCTLR

System controller subsystem

SYSLOGD

System logging

SYSLOG_SERVER

Syslog-server file system routines

SYSMGR

System Manager

SYSMGR_PLATFORM

Cisco Catalyst 6500 system manager process

SYSMGT_RPC

System management

SYSTEM_BUS_ASIC

System Bus Translator ASIC


34


Table 1


Code

Facility

SYSTEM_ CONTROLLER

System controller

SYSTEM_HM

System health monitor

T1E1SUNI

PAM port driver

TAC

Terminal Access Controller Access Control System

TAGCON

Tag distribution and control

TAGCOS

Tag switching class of service

TAR_FS

Tar file system

TBRIDGE

Transparent bridging

TCAM_MGR

TCAM manager

TCAMMGR

TCAM manager

TCATM

ATM tag control

TCMIPC

Toaster-RP IPC-related

TCMSP

Call control for telephony-style hardware interfaces

TCP

Transmission Control Protocol

TDM

Time-division multiplexing (TDM)

TDM_CLOCK_ SYNCHRONIZATION

Time-division multiplexing (TDM) frame clock

TDM_CONN

TDM connections

TDP

Tag Distribution Protocol

TENGIGE_LC

10-Gigabit Ethernet line card

TESTPA

TestPA port adapter

TFIB

Tag Forwarding Information Base

TI1570

PCI/TI1570-based ATM port adapter

TIB

Tag Information Base

TID_HA

Table ID High Availability (HA)

TIDP

Threat Information Distribution Protocol

TIGER

Error-correcting code (ECC) and parity-related

TINY_FRAG_POLICER

Tiny frag policer

TLV

EEPROM

TMS

Threat Management Service

TMQ

Inbound terminal port queuing

TN

Telnet

TN3270

TN3270 protocol

TOASTER_CP

Toaster-based coprocessor assist

TOASTER_IPC

Toaster interprocess communication

TOPN_COUNTERS

Switch TopN report counters


35


Table 1


Code

Facility

TPLUS

TACACS Protocol

TR

Token Ring

TRANSCEIVER

Transceiver module

TRINITY

Trinity System

TRUNK

E1/T1 trunk card

TRUNK_CLOCK

AS5400 clocking

TRUNK_DFC

Trunk dial feature card

TRUNK_SERIAL

Trunk serial device

TSP

Tag-switched path (TSP)

TTFIB_NP_CLIENT

Toaster Tag FIB (TTFIB) NP client

TTY

Tty-related for all platforms

TTYDRIVER

Router shelf asynchronous driver

TUN

Tunnel

TUNSS

Tunnel security

TURBORSC

Platform-specific RSC

TWOBT

WS 2BT protocol driver

TWO_GIGE

Two Gigabit Ethernet subsystem

TXCONN

Cisco Transaction Connection (CTRC)

UBL

Universal Boot Loader

UBR7200

Cable modem termination system

UBR900

Cisco uBR900 Series Cable Access Routers

UCODE

Microcode

UDLD

UniDirectional Link Detection (UDLD) protocol

UNICAST_FLOOD

Unicast flooding

UNIX

UNIX

UNIXRP

UNIX RP

UPS

Uninterruptible power supply

URLF

URL filtering subsystem

USBFLASH

USB flash device

USB_HOST_STACK

USB host stack

USB_TOKEN

USB security token

USB_TOKEN_FILESYS

USB Token File System

UTIL

Utility

VACL

VLAN ACL

VALENCIA

Valencia ASIC on Services SPA Carrier Card (SSC-600)

VFC

Voice over IP (VoIP)


36


Table 1


Code

Facility

VINES

Banyan VINES

VIP

Versatile Interface Processor

VIP_MDR

Versatile Interface Processor Minimum Disruption Restart system

VIPMLP

Multilink PPP

VOA

Hamptons variable optical attenuator (VOA) card

VOICE_ELOG

Voice event logger

VOICE_FSM

MC3810 voice FSM subsystem

VOICE_IEC

Voice internal error code (IEC)

VOICE_RC

MC3810 voice resource subsystem

VOICE_UTIL

Voice call control utilities

VOIPAAA

VoIP AAA

VOIPFIB

VoIP FIB

VOLANT

Content engine NM

VPA

Voice port adapter

VPD

ATM CES (Voice Processor Deck) driver

VPDN

Virtual Private Dialup Networking

VPLS_NP_CLIENT

Virtual Private LAN Service NP client

VPN_HW

VPN hardware accelerator

VPNSM

VPN Services Module

VPNSMIOS

VPNSM crypto connection

VPNSMIOSSP

VPNSM crypto connection SP

VRM

Voice Resource Management

VRRP

Virtual Router Redundancy Protocol

VSAT

Satellite Module

VSEC

VLAN security violation

VS_GENERIC

Virtual switch

VSL

Virtual switch link

VSI_M

Virtual switch interface (VSI) master

VSL_BRINGUP

Virtual switch link bringup

VSLP

Virtual Switch Link Protocol

VS_MOD

Virtual switch module provisioning

VS_PARSE

Virtual switch

VS_QOS_ACL

Virtual switch QoS ACL

VSTATS

Voice statistics push data

VTSP

Voice telephony security parameter index (SPI)

WA_ENGINE

WA engine network module


37


Table 1


Code

Facility

WARMUPGRADE

Warm upgrade feature

WCCP

Web Cache Communication Protocol (WCCP)

WIC_AM

WIC-AM modem initialization

WiSM

WiFi services module

WLAN_CONTROLLER

WLAN controller network module

WLCCP_WDS

Wireless LAN Context Control Protocol (WLCCP) for WDS

WS_ALARM

Windstar alarm

WSHTF

HT_FPGA data plane driver

WSIPC

Windstar IPC

X25

X.25

XCCTSP_VOICE

External Call Control Telephony Service Provider

XCPA

Mainframe Channel Port Adapter

XCVR

Transponder

XDR

eXternal Data Representation

XDSDLWIC

Cisco 2600 series and 3600 series xDSL drivers

XTAGATM

Extended Tag ATM (XTagATM)

Y88E8K

Yukon 88E8000 E/FE/GE controller

ZAM

Zenith Alarm Management

Table 2

System Message Severity Levels

Level

Description

0 – emergency

System unusable

1 – alert

Immediate action needed

2 – critical

Critical condition

3 – error

Error condition

4 – warning

Warning condition

5 – notification

Normal but significant condition

6 – informational

Informational message only

7 – debugging

Appears during debugging only

System message severity levels correspond to the keywords assigned by the logging console and logging monitor global configuration commands that define where and at what level these messages appear. In general, the default is to log messages from level 0 (emergencies) to level 7 (debugging). However, the default level varies by platform. For more information, see the system configuration chapter and descriptions of the logging console and logging monitor commands in the appropriate Cisco IOS configuration guide and command reference publications.


38

Cisco IOS System Message Guide, 12.2 SX System Message Example

Table 3

Representation of Variable Fields in Messages

Representation

Type of Information

[atalk_address]

AppleTalk address

[atalk_net]

AppleTalk network, either 600 or 600-601

[char]

Single character

[chars]

Character string

[dec]

Decimal number

[enet]

Ethernet address (for example, 0000.FEED.00C0)

[hex]

Hexadecimal number

[hex_addr]

Hexadecimal address

[inet]

Internet address (for example, 10.0.2.16)

[int]

Integer

[ipv6_addr]

IP version 6 (IPv6) address

[node]

Address or node name

[p]

IPv6 address

[sci_notation]

Scientific notation

[t-line]

Terminal line number in octal (or decimal if the decimal-TTY service is enabled)

[v-name]

VINES name; or service number (hex or decimal)

System Message Example The following is an example of a system error message: %LINK-2-BADVCALL: Interface [chars], undefined entry point •

LINK is the facility code.

•

2 is the severity level.

•

BADVCALL is the mnemonic code.

•

“Interface [chars], undefined entry point” is the message text.

Some messages also indicate where the system condition occurred. These messages are structured as follows: %FACILITY-SOURCE-SEVERITY-MNEMONIC: Message-text SOURCE indicates the location of the condition. Examples of SOURCE are SP, which indicates that the condition occurred in the switch processor, or DFC5, which indicates that the condition occurred in the Distributed Forwarding Card on the module in slot 5.


39

Cisco IOS System Message Guide, 12.2 SX Message Traceback Reports

Message Traceback Reports Some messages describe internal errors and contain traceback information. This information is very important and should be included when you report a problem to your technical support representative. The following sample message includes traceback information: -Process= ”Exec”, level= 0, pid= 17 -Traceback= 1A82 1AB4 6378 A072 1054 1860

Message Overrun and Continuation When a system message contains lengthy descriptive information, the message text can sometimes exceed the syslog buffer. In releases earlier than Cisco IOS Release 12.2(33)SXF2, the overrun message is truncated to the buffer size and any additional text is lost. When truncation occurs, the following message is sent after the truncated message: %Log packet overrun, PC [hex], format: [chars]

In Cisco IOS Release 12.2(33)SXF2 and later releases, a long message can be split into multiple messages, with truncation and continuation indicators at each section. The end of an incomplete syslog message section will be tagged with the string "**MSG XXXXX TRUNCATED**", where XXXXX is a count of overrun messages since the last system reload. The continuation of the message will begin with "**MSG XXXXX CONTINUATION #YY", where YY represents the part number. A message can be divided into a maximum of 99 parts. This example shows a message split into three sections: %TEST-5-ANY_ERRMSG: This messaage should be split into three 0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789ABCDEFGHIJKLMNOPQR STUVWXYZabcdefghijklmnopqrstuvwxyz0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrst uvwxyz0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789ABCDEFGHIJKL MNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmn opqrstuvwxyz0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789ABCDEF GHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefgh ijklmnopqrstuvwxyz0123456789ABCDEFGHIJKLMNO**MSG 00001 TRUNCATED** **MSG 00001 CONTINUATION #01**PQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijkl mnopqrstuvwxyz0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789ABCD EFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdef ghijklmnopqrstuvwxyz0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz01234567 89ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ abcdefghijklmnopqrstuvwxyz0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz01 23456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789ABCDEFGHIJKLMNOPQRST UVW**MSG 00001 TRUNCATED** **MSG 00001 CONTINUATION #02**XYZabcdefghijklmnopqrstuvwxyz0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrst uvwxyz


40

Cisco IOS System Message Guide, 12.2 SX Using the Error Message Decoder to Search for System Messages

Using the Error Message Decoder to Search for System Messages The Error Message Decoder (EMD) is a tool that will help you to research and resolve error messages for Cisco software. The EMD helps you to understand the meaning of the error messages that display on the console of Cisco routers, switches, and firewalls. To use the EMD, copy the message that appears on the console or in the system log, paste it into the window, and press the Submit button. You will automatically receive an Explanation, Recommended Action, and, if available, any related documentation for that message. The EMD is located here: http://www.cisco.com/cgi-bin/Support/Errordecoder/index.cgi?locale=en

Searching for System Messages in Online Documentation To search for messages in online documentation, use the search function of your browser by copying and pasting the message that appears on the console or in the system log. Some messages that appear on the console or in the system log indicate where the system condition occurred. These messages are structured as follows: %FACILITY-SOURCE-SEVERITY-MNEMONIC: Message-text SOURCE indicates the location of the condition. Examples of SOURCE are SP, which indicates that the condition occurred in the switch processor, or DFC5, which indicates that the condition occurred in the Distributed Forwarding Card on the module in slot 5. If you search for the explanation and recommended action of a message that contains a SOURCE, remove the SOURCE from the text first, and then search for the message in the documentation. For example, instead of searching the documentation for the message C6KPWR-SP-4-DISABLED, remove the SOURCE identifier and search for the message C6KPWR-4-DISABLED.

Related Documentation The following publications are available for the Catalyst 6500 series switches: •

Catalyst 6500 Series Switch Module Installation Guide

•

Catalyst 6500 Series Switch Cisco IOS Command Reference

•

Cisco IOS Configuration Guides and Command References

For information about MIBs, refer to: http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml For Cisco IOS system messages not contained in this publication, refer to the following Cisco IOS documentation: •

System Messages for IOS: http://www.cisco.com/en/US/docs/ios/system/messages/guide/consol_smg.html


41

Cisco IOS System Message Guide, 12.2 SX Obtaining Documentation and Submitting a Service Request

Obtaining Documentation and Submitting a Service Request For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html Subscribe to the What’s New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.


42

System Messages This section lists messages alphabetically by facility and mnemonic.

AAA Messages This section contains authentication, authorization, and accounting messages.

AAA-2 Error Message %AAA-2-AAAMULTILINKERROR: [chars]([hex]): Acct db for Id [hex] absent Explanation A AAA internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %AAA-2-FORKFAIL: Cannot fork process [chars] Explanation Attempted to fork a process and failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at

Americas Headquarters: Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA

System Messages AAA Messages

http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

AAA-3 Error Message %AAA-3-ACCT_IOMEM_LOW: AAA ACCT process suspended : low I/O memory Explanation The authentication, authorization, and accounting (AAA) accounting process has been

suspended due to insufficient memory. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %AAA-3-BADSERVERTYPEERROR: Cannot process [chars] server type [chars] Explanation A method list function encountered a server type that was unknown, or could not be

handled. This may be due to a server misconfiguration. Recommended Action Research the cause of the misconfiguration and attempt to correct it, otherwise

take the following action.

Error Message %AAA-3-ACCT_LOW_MEM_TRASH: AAA unable to handle accounting requests due to insufficient memory. So, we trash all queued accounting reguests, which may worry customer Please upgrade your memory or plan to get more free memory by optimizing your configuration. Explanation An accounting request was dropped because there is not enough processor memory. All

queued accounting requests will be discarded. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support


2


representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %AAA-3-ACCT_LOW_MEM_UID_FAIL: AAA unable to create UID for incoming calls due to insufficient processor memory Explanation The AAA accounting process is unable to create a user ID (UID) due to insufficient

memory. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %AAA-3-ATTRFORMATERR: Attribute with unknown format [dec] Explanation An attribute was found with an invalid format. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %AAA-3-AUTH_LOW_IOMEM: RADIUS process is unable to handle the requests due to insufficient low I/O memory Explanation The RADIUS process is unable to handle requests due to insufficient memory. Recommended Action Copy the message exactly as it appears on the console or in the system log.



3


Error Message %AAA-3-AUTHORMLISTUNDEF: Authorization method list ’[chars]’ is not defined. Please define it. Explanation A given method list was listed in a command without defining it first. The method list

should be defined before use. Recommended Action Define the method list before using it.

Error Message %AAA-3-BADCURSOR: invalid cursor index [dec] max [dec] service [chars] protocol [chars] Explanation A AAA client has provided an invalid attribute cursor to AAA. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %AAA-3-BADHDL: invalid hdl AAA ID [int], hdl [hex], [chars] Explanation A AAA client has provided an invalid attribute list handle to AAA. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %AAA-3-BADLIST: invalid list AAA ID [int] Explanation A AAA client has provided an invalid attribute list to AAA. Recommended Action Copy the message exactly as it appears on the console or in the system log.



4


representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %AAA-3-BADMAGIC: Data structure failed magic number sanity check Explanation A corrupted data structure has been found which was stored internally. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %AAA-3-BADMETHOD: Cannot process [chars] method [int] Explanation A method list function encountered a method list that was unknown or could not be

handled. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %AAA-3-BADMETHODERROR: Cannot process [chars] method [chars] Explanation A method list function encountered a method type that was unknown or could not be

handled. Recommended Action Copy the message exactly as it appears on the console or in the system log.



5


Error Message %AAA-3-BADPROTOCOL: Unknown protocol [int] Explanation The AAA subsystem encountered an unknown protocol type. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %AAA-3-BADSERVICE: Unknown service [int] Explanation The AAA subsystem encountered an unknown service type. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %AAA-3-BUFFER_OVERFLOW: Radius I/O buffer has overflowed Explanation An unusually large number of Radius attributes has caused AAA to overflow its Radius

I/O buffer. Recommended Action This is an internal software error. Copy the message exactly as it appears on

the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


6


Error Message %AAA-3-DROPACCTFAIL: Accounting record dropped, send to server failed: [chars] Explanation An attempt to send an accounting record to a server has failed. Recommended Action Check that the server (TACACS+ or RADIUS) is operational, that the network access server (NAS) is configured properly, and that the NAS can communicate with the server.

Error Message %AAA-3-INVALIDPARM: invalid parameter was used when accessing AAA function Explanation A AAA client tried to use a AAA function with an invalid parameter. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %AAA-3-IPILLEGALMSG: Invalid use of ip_pid([int]) Explanation A process sent an illegal message to IP for which IP has not subscribed. Recommended Action If this message recurs, copy the message exactly as it appears on the console

or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %AAA-3-ISDNINTF: [chars] [chars]: Can not apply configuration to ISDN channel: "[chars]" Explanation The current configuration cannot be applied to individual ISDN channels. You need

virtual-profiles and virtual-access interfaces to apply a configuration to ISDN. Recommended Action Refer to the “Configuring virtual profiles by AAA Configuration” section in

the Cisco IOS Dial Technologies Configuration Guide.


7


Error Message %AAA-3-MLIST_INTERNAL_ERROR: method list ’[chars]’: [chars] Explanation This is an internal software error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %AAA-3-MLIST_TOO_MANY_METHODS: method list ’[chars]’ Explanation A AAA client attempted to add too many methods to a method list. This is an internal

software error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %AAA-3-NOTABLE: AAA ID [int] Explanation There has been a resource failure. Recommended Action Copy the message exactly as it appears on the console or in the system log.



8


Error Message %AAA-3-NULLCURSOR: Null cursor Explanation A AAA client has provided a nonexistant attribute cursor to AAA. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %AAA-3-NULLVRF: Null vrf entry Explanation A NULL virtual routing and forwarding (VRF) entry was found while comparing the

AAA VRF attributes. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %AAA-3-PARSEERR: Error([dec]) parser is unable to parse [chars] per-user command Explanation All attempts to parse this per_user unconfigure command have failed. The specified

unconfigure command was not unconfigured. Recommended Action Copy the message exactly as it appears on the console or in the system log.



9


Error Message %AAA-3-SERVER_INTERNAL_ERROR: Server ’[IP_address]’: [chars] Explanation This is an internal software error in the AAA server group subsystem. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %AAA-3-SG_DEADTIME_FORKFAIL: Failed to fork process for [chars]. Explanation Most likely, the device has run out of memory, though other explanations are possible. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %AAA-3-SG_INTERNAL_ERROR: server group ’[chars]’: [chars] Explanation This is an internal software error in the AAA server group subsystem. Recommended Action Copy the message exactly as it appears on the console or in the system log.



10


Error Message %AAA-3-SG_TESTPROC_FORKFAIL: Failed to fork process for [chars]. Explanation Most likely, the device has run out of memory, though other explanations are possible. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %AAA-3-SORTFAIL: [chars] :Peruser Could not sort the [chars] attributes Explanation Sorting of the attributes received from the AAA server has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


AAA-6 Error Message %AAA-6-ACCTSESSIDWRAP: Accounting-Session-ID [dec] exceeded max value allowed Explanation The Accounting-Session-ID has exceeded the maximum value allowed. Recommended Action This is an informational message only. No action is required.

Error Message %AAA-6-USER_BLOCKED: Enable view requires to be authenticated by non-none methods,Please use the appropriate method with the login authentication Explanation None method authentication is not allowed in CLI Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,


11

System Messages AAAA Messages

open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

AAAA Messages This section contains TACACS+ authentication, authorization, and accounting security messages.

AAAA-3 Error Message %AAAA-3-AAAFORKFAIL: Failed to start AAA process. AAA requests may not be processed. Explanation The device has failed to create the AAA process. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message %AAAA-3-ACCTFORKFAIL: Failed to start accounting process. Accounting records may not be sent. Explanation The device has failed to create the accounting process. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message %AAAA-3-BADSTR: Bad accounting data: [chars] Explanation During AAA accounting operations, the internal database of accounting information for

a user was found to be corrupt. In all cases, this indicates an internal software error, and that accounting information for a particular user session has been lost. Recommended Action Copy the message exactly as it appears on the console or in the system log.



12


Error Message %AAAA-3-DROPACCTFULLQ: Accounting record dropped due to a full aaa accounting queue: [chars]-[chars] [chars] [chars] Explanation An accounting record was dropped because too many accounting packets are enqueued. Recommended Action Disable periodic accounting if it is on. The accounting queue may have grown to be large, which is usually due to a non-responsive AAA server. Enter the show radius statistics or the show tacacs command to see if the number of timeouts is increasing or if the response delay is unusually high.

Error Message %AAAA-3-DROPACCTLOWMEM: Accounting record dropped due to low memory: [chars]-[chars] [chars] [chars] Explanation An accounting record dropped due to low memory. Recommended Action Disable periodic accounting if it is on. Try to reduce the load on the router.

Error Message %AAAA-3-DROPACCTQUEUEEXCEEDED: accounting record dropped, output record queue full: [chars]-[chars] [chars] [chars] Explanation An accounting record was dropped. The record could not be enqueued because the

number of records in the output queue has exceeded the system limit. Recommended Action If periodic accounting is enabled, disable it by entering the no aaa accounting update newinfo periodic command.

Error Message %AAAA-3-DROPACCTSNDFAIL: Accounting record dropped, send to server failed: [chars]-[chars] [chars] [chars] Explanation An attempt to send an accounting record to a server failed. Recommended Action Check that the server (TACACS+ or RADIUS) is operational. Next, check that the NAS is configured properly. Finally, check that the NAS can communicate with the server.

Error Message %AAAA-3-NOADMINSOC: [chars] Explanation The socket setup for the administrative process has failed. The process is exiting. Recommended Action Copy the message exactly as it appears on the console or in the system log.



13


Error Message %AAAA-3-NULPORT: Could not establish port information Explanation This message indicates an internal software error. AAA could not determine a valid port

string based on the information provided to it via a client. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message

%AAAA-3-NULUSR: accounting for null user

Explanation This message indicates an internal software error. During shutdown of a line or interface, the system tried to send accounting information via AAA, but could not find the user to which the accounting information belonged. The most likely reason for this error is trying to do accounting twice for the same event. This error message can occur without any loss of accounting information. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %AAAA-3-RELOGIN: sanity check in re-login [chars] to [chars] Explanation A software or hardware error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



14


Error Message %AAAA-3-SGDUPFREE: Duplicate free of server group [hex] Explanation This is an internal software error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


AAAA-4 Error Message %AAAA-4-BADSGTYPE: Server-group [chars] is not of type [chars]. Explanation The server group name does not match the specified type. Recommended Action Verify that the group exists and has the correct type.

Error Message %AAAA-4-NOCACHEPROC: The aaa cache process is not created. Please configure aaa cache profile first Explanation Cache was listed in a method-list without defining it first. Cache profile should be

defined before use. Recommended Action Define the cache profile before using it.

Error Message %AAAA-4-SERVNOGRP: Warning: Server %i:[dec],[dec] is not part of server group [chars]. Explanation The server does not belong to the specified server group. Recommended Action Check that the server belongs to the correct server group.

Error Message %AAAA-4-SERVNORADIUS: The server-group "[chars]" is not a radius server group. Please define "[chars]" as a radius server group. Explanation The protocol used by the server-group doesn’t support the configured aaa action. Recommended Action Use a radius server-group.


15

System Messages AAA_CACHE Messages

Error Message %AAAA-4-SERVNOTACPLUS: The server-group "[chars]" is not a tacacs+ server group. Please define "[chars]" as a tacacs+ server group. Explanation The protocol used by the server-group does not support the configured AAA action. Recommended Action Use a TACACS+ server-group.

Error Message %AAAA-4-UNSUPWAITSTART: % AAA: Unsupported option wait-start mapped to start-stop. Explanation Wait-start accounting is not supported. It is being mapped to start-stop . Recommended Action This is an informational message only. No action is required.

AAA_CACHE Messages This section contains authentication, authorization, and accounting cache messages.

Error Message %AAA_CACHE-3-NULL_TREE_PERIODIC_PROC: Cache Tree pointer is of null value Explanation The cache tree pointer is of null value. Recommended Action Copy the message exactly as it appears on the console or in the system log.


AC Messages This section contains Attachment Circuit messages.

Error Message %AC-3-AC_PROVISION: [chars] Explanation An error was encountered during Attachment Circuit [un]provisioning. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at


16

System Messages ACCESS_IE Messages

http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message

%AC-3-AC_SUBBLOCK: [chars]

Explanation An error was encountered during Attachment Circuit sub-block creation or removal. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message

%AC-3-AC_VECTOR: [chars]

Explanation An error was encountered during Attachment Circuit configuration which caused

problems in the setting or restoration of the interface vectors. Recommended Action Copy the message exactly as it appears on the console or in the system log.


ACCESS_IE Messages This section contains access information element messages.

Error Message %ACCESS_IE-3-INVALID_HANDLE: Caller passed in invalid handle traceback to follow. Explanation An invalid handle was encountered in the access information element (IE) library. Recommended Action Copy the message exactly as it appears on the console or in the system log.



17

System Messages ACE Messages


ACE Messages This section contains access control encryption messages.

ACE-2 Error Message %ACE-2-CRYPTOENGERR: Crypto engine error: [chars] ([dec]) Explanation A crypto engine operation did not complete. This error condition can indicate that the

crypto engine cannot bind or unbind an interface to a crypto engine. It can also indicate that the crypto engine cannot query an interface ID. Recommended Action Remove the cryptomap set from the interface by enteringthe no crypto map

command. Then reattach the cryptomap set to the interface by entering the crypto map command. Although removing and reattaching the crypto map might fix the cryptographic engine operation failure, report the failure to your Cisco technical support representative along with the sequence of commands that led to the failure.

ACE-3 Error Message %ACE-3-BOOTMSGERR: [chars]: boot error: [chars] Explanation The ACE completed booting, but with an error status code. ACE will not operate and it will not register with the crypto subsystem. Recommended Action Copy the message exactly as it appears on the console or in the system log.



18


Error Message %ACE-3-CEAL_REGISTRATION: ACE [chars] failed to register. Explanation The ACE failed to register with the Crypto Engine Acceleration Layer (CEAL). Recommended Action Reset the module. If this message recurs, copy the message exactly as it

appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %ACE-3-NOENGINESLOT: Interface [chars] has no crypto engine slot Explanation An IKE SA was requested for a given interface, but no crypto engine slot was assigned

to that interface. [chars] is the name of the interface that is missing the crypto engine slot command. Recommended Action Configure the interface in question with the crypto engine [sub]slot command.

Error Message %ACE-3-OUTOFID_RL: Too may [chars] IDs in the system. Cannot allocate a new one Explanation All the IDs of the specified type are in use. Recommended Action Reduce the traffic load, the number of IPSec tunnels, or the frequency of

changing the value of a cryptographic key. If this message was seen under light loading conditions, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

ACE-6 Error Message %ACE-6-BOOTMSGINFO: [chars]: boot info: [chars] Explanation The ACE completed booting, but with a non-zero informational status code. This does

not indicate an error and ACE will run normally. Recommended Action This is an informational message only. No action is required.


19


Error Message %ACE-6-INFO: [chars]: [chars] Explanation This is an informational message from ACE Recommended Action This is informational message only and occurs in normal operation. No action

is required.

Error Message %ACE-6-SWITCHOVER: VPN-SM switchover: [dec]/[dec] has been [chars] [dec]/[dec] Explanation A module-to-module switchover has occurred. System performance is not affected. Recommended Action No action is required.

Error Message %ACE-6-TUNNEL_ACE_CONGESTED: All crypto engines are congested, assigning [chars] to [chars] Explanation The congestion manager has assigned a new tunnel to an already congested crypto

engine. All crypto engines have indicated congestion, so the least congested engine was selected for the tunnel. Packets may be lost on some tunnels. Recommended Action Reduce the bandwidth requirements of existing tunnels or install additional

crypto engines.

Error Message %ACE-6-TUNNEL_MOVE: [chars] has been moved from [chars] to [chars] to relieve congestion Explanation The congestion manager has moved a tunnel from a congested crypto engine to an

uncongested crypto engine. Recommended Action

No action is required.

Error Message %ACE-6-UNEXP_INBOUND_IPSEC: [chars]: received unexpected IPsec packet: src IP: [IP_address]; dst IP: [IP_address]; (count=[dec]) Explanation An IPsec packet was unexpectedly forwarded to the RP. Recommended Action If this message was seen in the context of the router booting, enabling the hardware crypto accelerator, then this message is normal and can be safely ignored. Otherwise, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


20

System Messages ACL_ASIC Messages

Error Message %ACE-6-UNEXP_OUTBOUND_IPSEC: [chars]: received unexpected IPsec packet: src IP: [IP_address]; dst IP: [IP_address]; firsthop/lasthop = [chars]/[chars] (count=[dec]) Explanation An IPsec packet was unexpectedly forwarded to the RP. Recommended Action If this message was seen in the context of the router booting, enabling the hardware crypto accelerator, or with an invalid peer IP address then this message is normal and can be safely ignored. Otherwise, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

ACL_ASIC Messages This section contains Access Control List ASIC messages.

Error Message %ACL_ASIC-4-INTR_THROTTLE: Throttling "[chars]" interrupt exceeded permitted [int]/[dec] interrupts/msec Explanation Excessive interrupts were generated by the EARL ASIC. The system will enforce

interrupt throttling to protect the SP. Recommended Action If this message recurs, copy the message exactly as it appears on the console



21

System Messages ACLMGR Messages

ACLMGR Messages This section contains Access Control List (ACL) manager messages.

ACLMGR-2 Error Message %ACLMGR-2-NOMAP: Cannot create ACL Manager data structures for VLAN Map [chars] Explanation The ACL manager could not allocate the data structures needed to describe a VLAN

map in a form that can be loaded into hardware. This situation was probably caused by a lack of free memory. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message %ACLMGR-2-NOVLB: Cannot create memory block for VLAN [dec] Explanation The ACL manager was unable to save per-VLAN information needed for its correct

operation. Some per-interface features, such as access groups or VLAN maps, will not be configured correctly. Recommended Action Use a less complicated configuration that requires less memory.

Error Message %ACLMGR-2-NOVMR: Cannot create VMR data structures for access list [chars] Explanation The ACL manager could not allocate the data structures needed to describe an ACL in

a form that can be loaded into hardware. There may not be enough available memory. Recommended Action Use a less complicated configuration that requires less memory.

ACLMGR-3 Error Message %ACLMGR-3-ACLTCAMFULL: Acl Tcam Full! Sofware Forwarding packets on [chars] label [dec] on [chars] [chars] Explanation There are too many ACL configurations for the platform-specific ACL TCAM table to

support. Recommended Action Reduce the number IP or MAC access lists to be configured to interfaces.


22

System Messages ACLMGR Messages

Error Message %ACLMGR-3-AUGMENTFAIL: Augmenting of access-map [chars] on [chars] label [dec] failed Explanation The system ran out of CPU DRAM when attempting to merge internally required

elements with the configured access map(s). Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message %ACLMGR-3-INSERTFAIL: Insert of access-map [chars] #[dec] into [chars] label [dec] failed Explanation The system ran out of CPU DRAM when trying to merge sections of an access map. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message %ACLMGR-3-MAXRECURSION: Too many ([dec]) levels of recursion while merging ACLs (code [dec]). Explanation The configuration is too complicated for the platform-specific ACL merge code to

support. This may be caused by including too many separate access lists in a single VLAN map or policy map. Recommended Action Reduce the number of IP or MAC access lists (considered separately) in any

one VLAN or policy map to fewer than the number of levels reported by this log message.

Error Message %ACLMGR-3-MERGEFAIL: [chars] ACL merge error [dec] ([chars]) on [chars] label [dec] Explanation The ACL manager was unable to complete the merge of the configured features into a

form suitable for loading into the hardware. Packets potentially affected by this feature will be sent to the CPU for processing instead. The most likely cause is specifying an ACL that is too large or too complex for the system to handle. Recommended Action Try specifying a smaller and less complicated configuration.

Error Message %ACLMGR-3-NOLABEL: Cannot allocate [chars] label for vlan-id [dec] Explanation The ACL manager was unable to allocate a label for the features on this interface. This

means that the hardware cannot be programmed to implement the features, and packets for this interface will be filtered in software. There is a limit of 256 labels per direction. Recommended Action Allocate more space to the relevant section of the TCAM and reboot, or else

use a simpler configuration. Use the same ACLs on multiple interfaces, if possible.


23

System Messages ADJ Messages

Error Message %ACLMGR-3-RELOADED: Reloading [chars] label [dec] feature Explanation The ACL manager was able to fit more of the configured features on this label into the hardware. One or more features had previously been unloaded because of lack of space. Recommended Action No action is required.

Error Message %ACLMGR-3-UNKNOWNACTION: Unknown VMR access group action [hex] Explanation An internal software error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ACLMGR-3-UNLOADING: Unloading [chars] label [dec] feature Explanation The ACL manager was unable to fit the complete configuration into the hardware, so some features will have to be applied in software. This prevents some or all of the packets in a VLAN from being forwarded in hardware, and requires them to be forwarded by the CPU. Multicast packets may be dropped entirely instead of being forwarded. Recommended Action Allocate more space to the relevant section of the TCAM and reboot, or else

use a simpler configuration. Use the same ACLs on multiple interfaces, if possible.

ADJ Messages This section contains adjacency (ADJ) subsystem messages.

ADJ-3 Error Message %ADJ-3-ADJGENALLOCATEFAIL: Failed to allocate memory [chars] Explanation An internal software error occurred. This error was probably caused by insufficient

available memory. Recommended Action Copy the message exactly as it appears on the console or in the system log.



24


open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message

%ADJ-3-ADJGENDEALLOCATEFAIL: Failed to deallocate memory [chars]

Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ADJ-3-ADJLISTREINSERTING: [chars] adj (addr [chars] int [chars] cid [dec]) in adj list for [chars] while still in adj list for [chars] Explanation An inconsistency was detected when attempting to maintain the list of CEF adjacencies pertaining to an interface. An adjacency was inserted into more than one list. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ADJ-3-ADJMGRDISPATCHFAIL: Failed to enqueue an adjacency summary event block Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



25



Error Message %ADJ-3-ADJMGRREFRESHFAIL: Failed to dispatch a refresh adjacency summary event Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message

%ADJ-3-ADJSTACK2: Adj stack2 error [chars]: [chars]



Error Message

%ADJ-3-ALLOCATEFAIL: Failed to allocate an adjacency

Explanation An internal software error occurred. This error was probably caused by insufficient

available memory. Recommended Action Copy the message exactly as it appears on the console or in the system log.



26


Error Message

%ADJ-3-ALLOCATEONDOWN: Allocating adj when adj subsystem down



Error Message [chars]

%ADJ-3-BADADDRLEN: Zero address length detected distributing adj

Explanation An internal software error occurred. An attempt was made to reference an adjacency

with an unsupported address type. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ADJ-3-BADADDRTYPE: Using an unsupported address type [dec] when trying to add/delete/modify/find an adjacency Explanation An internal software error occurred. An attempt was made to reference an adjacency




27


Error Message %ADJ-3-BADLINKTYPE: Using an unsupported linktype [chars] when trying to add/delete/modify/find an adjacency Explanation An internal software error occurred. An attempt was made to reference an adjacency



Error Message

%ADJ-3-BADMACALIGN: adjacency mac string end [hex] not [chars] aligned



Error Message

%ADJ-3-BADMAGIC: adjacency [chars] is followed by bad magic




28


Error Message failed

%ADJ-3-BOARDENCAP: Generation of encapsulation string for [chars]



Error Message facility

%ADJ-3-BROKERINITFAIL: Failed to initialise adjacency RP broker



Error Message

%ADJ-3-BUNDLES: Adj bundles: [chars]




29


Error Message %ADJ-3-DBGFILTERALLOCATEFAIL: Failed to allocate an adjacency debug filter block Explanation An internal software error occurred. This is probably because not enough memory was

available. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message subblock

%ADJ-3-ILALLOCATEFAIL: Failed to allocate an adjacency interest list

Explanation An internal software error occurred. This is probably because not enough memory was



Error Message %ADJ-3-ILDEALLOCATEFAIL: Failed to deallocate an adjacency interest list subblock Explanation An internal software error occurred. This is probably because not enough memory was




30


Error Message facility

%ADJ-3-ILINITFAIL: Failed to initialise adjacency interest list



Error Message

%ADJ-3-ILLEGALARGS: Illegal arguments - [chars]



Error Message %ADJ-3-IPC: Adj [chars], [chars] [chars] cid [int] - [chars] distributing to [chars] Explanation An internal software error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



31


Error Message %ADJ-3-LCXDRCLIENT: Adjacency distribution client: [chars] Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message

%ADJ-3-NOFIBIDB: CEF Interface not found - [chars]



Error Message %ADJ-3-RESOLVE_REQ: Adj resolve request: [chars] [chars] [chars] Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



32


Error Message %ADJ-3-RPXDRCLIENT: Adjacency distribution client: [chars] Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message

%ADJ-3-SBINITFAIL: Failed to initialise adjacency subblock facility



Error Message [chars]

%ADJ-3-STATETRANSITION: Unexpected state transition from [chars] to




33


Error Message %ADJ-3-TYPENOTISSUAWARE: Bundle type [chars] must be ISSU aware to send to slot(s) [chars] Explanation The bundle type is not ISSU aware, so it cannot be distributed to a slot with which ISSU

negotiation has occurred. This indicates a design problem that requires code changes to fix. Recommended Action Copy the message exactly as it appears on the console or in the system log.


ADJ-5 Error Message %ADJ-5-ADJISSUINCOMPATIBLE: All or part of sdjacency message for [chars] not sent to incompatible CEF instance for [chars] Explanation The adjacency is not distributed in whole to the remote CEF instance. This may impact

traffic forwarding on the remote CEF instance. Recommended Action No action is required.

Error Message %ADJ-5-PARENT: Midchain parent maintenance for [chars] - [chars] Explanation A midchain adjacency failed to stack onto an output chain because a loop was detected.

Traffic through the adjacency will be dropped until the adjacency is restacked. This condition is typically transient and is resolved by the control plane that drives the stacking. For example, if an IP tunnel destination resolves through the tunnel transiently this message will appear. The situation would be resolved either by learning the tunnel destination through an inteface other than the tunnel itself or by bringing the tunnel down. Recommended Action No action is required.


34

System Messages AFLSEC Messages

AFLSEC Messages This section contains Accelerated Flow Logging Security (AFLSEC) messages.

AFLSEC-6 Error Message %AFLSEC-6-OALDP: [chars] icmp [IP_address] -> [IP_address] ([dec]/[dec]), [dec] packet[chars] Explanation Packet(s) matching the optimized ACL log criteria have been detected. Recommended Action No action is required.

Error Message %AFLSEC-6-OALNP: [chars] ip protocol=[dec] [IP_address] -> [IP_address], [dec] packet[chars] Explanation Packet(s) matching the optimized ACL log criteria have been detected. Recommended Action No action is required.

Error Message %AFLSEC-6-OALP: [chars] [chars] [IP_address]([dec]) -> [IP_address]([dec]), [dec] packet[chars] Explanation Packet(s) matching the optimized ACL log criteria have been detected. Recommended Action No action is required.

Error Message %AFLSEC-6-OALRL: Oal logging rate-limited or missed [dec] packet[chars] Explanation Some packet matching logs were missed because the log messages were rate-limited or

the cache table was full, or no log buffers were available. Recommended Action No action is required.

Error Message %AFLSEC-6-OALRP: [chars] igmp [IP_address] -> [IP_address] ([dec]), [dec] packet[chars] Explanation Packet(s) matching the optimized ACL log criteria have been detected. Recommended Action No action is required.


35

System Messages ALIGN Messages

ALIGN Messages This section contains ALIGN messages.

ALIGN-3 Error Message %ALIGN-3-CORRECT_SO: Alignment correction made at [chars] [chars]ing [chars] Explanation A software component within the router needs memory optimization. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message

%ALIGN-3-TRACE_SO: -Traceback= [chars]

Explanation A trace that shows where the previous ALIGN error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message

%ALIGN-3-TRACEX: [chars]

Explanation A trace that shows where the previous ALIGN error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



36

System Messages ALPS Messages


ALPS Messages This section contains Airline Product Set (ALPS) messages.

ALPS-3 Error Message %ALPS-3-ASCU_IF_STUCK: Polling for ASCU [hex] on interface [chars] is stalled. Explanation The polling mechanism for agent set control units (ASCUs) on an ALPS interface has

become stuck. Recommended Action No action is required.

ALPS-5 Error Message %ALPS-5-ASCU_DISABLED_ASCU_STUCK: ASCU [hex] on interface [chars] has been disabled since 4 consecutive messages were received from same SID. Explanation An ALPS agent set control unit (ASCU) has been automatically disabled. Recommended Action No action is required.

Error Message

%ALPS-5-ASCU_DOWN: ASCU [hex] on interface [chars] is down.

Explanation An ALPS agent set control unit (ASCU) has transitioned from up to down. Recommended Action No action is required.

Error Message %ALPS-5-ASCU_UP: ASCU [hex] on interface [chars] is up. Explanation An ALPS agent set control unit (ASCU) has transitioned from down to up. Recommended Action No action is required.

Error Message %ALPS-5-CIRCUIT_CLOSED: Circuit [chars] changed state to closed, rsn = [chars]. Explanation An ALPS circuit has tranistioned from open to closed Recommended Action No action is required.


37


Error Message %ALPS-5-CIRCUIT_OPEN: Circuit [chars] changed state to open. Explanation An ALPS circuit has transitioned from closed to open. Recommended Action No action is required.

Error Message %ALPS-5-PEER_CLOSED_DYNAMIC_INACTIVITY: Peer ([IP_address], [chars]) closed due to inactivity. Explanation An ALPS peer connection is now closed due to inactivity. Recommended Action No action is required.

Error Message %ALPS-5-PEER_CONN_ID_CHANGE: Peer ([IP_address], [chars]) ID modified to ([IP_address], [chars]). Explanation An ALPS peer connection identifier has changed. Recommended Action No action is required.

Error Message %ALPS-5-PEER_OPEN: Peer ([IP_address], [chars]) changed state to open. Explanation An ALPS peer connection is now open. Recommended Action No action is required.

ALPS-6 Error Message %ALPS-6-CIRCUIT_ASCU_REJECT: Circuit [chars] received a Circuit Open Confirm with a list of rejected ascus Explanation An ALPS circuit sent a Circuit Open Request message and received a Circuit Open

Confirm with a list of rejected ascus. Recommended Action No action is required.

Error Message %ALPS-6-CIRCUIT_BUSY_START: Circuit [chars] has entered a congested state. Explanation An ALPS circuit is experiencing congestion. Recommended Action No action is required.


38


Error Message %ALPS-6-CIRCUIT_OPEN_FAILED: Circuit [chars] received a Circuit Open Failed message, rsn = [chars]. Explanation An ALPS circuit sent a Circuit Open Request message and received a Circuit Open

Failed message as a reply. Recommended Action No action is required.

Error Message %ALPS-6-CIRCUIT_UPDATE_FAILED: Circuit [chars] received a Circuit Open Failed message, rsn = [chars]. Explanation An ALPS circuit sent a Circuit Update message and received a Circuit Open Failed

message as a reply. Recommended Action No action is required.

Error Message %ALPS-6-CIRCUIT_X25_VC_STUCK: Host unresponsive on X.25 VC for circuit [chars] Explanation The X.25 or EMTOX host is not advancing the transmit window for extended periods

of time. This may be indicative of a temporary problem with the host application. An X.25 Reset is sent to reset the transmit and receive windows to allow communication to proceed. Recommended Action None

Error Message %ALPS-6-PEER_BUSY_END: Peer ([IP_address], [chars]) has exited a congested state. Explanation An ALPS peer connection is no longer experiencing congestion. Recommended Action No action is required.

Error Message %ALPS-6-PEER_BUSY_START: Peer ([IP_address], [chars]) has entered a congested state. Explanation An ALPS peer connection is experiencing congestion. Recommended Action No action is required.

Error Message %ALPS-6-PEER_OPEN_FAIL: Peer ([IP_address], [chars]) open failed, rsn = [chars] Explanation An ALPS peer connection attempted to open, but failed to open. Recommended Action No action is required.


39


ALPS-7 Error Message %ALPS-7-CIRCUIT_BUSY_END: Circuit [chars] has exited a congested state. Explanation An ALPS circuit is no longer experiencing congestion. Recommended Action No action is required.

Error Message %ALPS-7-CIRCUIT_DROPS_CKT_DISABLED: Threshold exceeded for circuit disabled drops for circuit [chars] Explanation The number of ALPS circuit drops due to circuit disabled exceeds the ALPS circuit

threshold value. Recommended Action No action is required.

Error Message %ALPS-7-CIRCUIT_DROPS_INVALID_ASCU: Threshold exceeded for invalid ASCU drops for circuit [chars] Explanation The number of ALPS circuit drops due to invalid ASCU identifier exceeds the ALPS circuit threshold value. Recommended Action No action is required.

Error Message %ALPS-7-CIRCUIT_DROPS_LIFETIME_EXPIRED: Threshold exceeded for lifetime timer expiration drops for circuit [chars] Explanation The number of ALPS circuit drops due to lifetime timer expiration exceeds the ALPS

circuit threshold value. Recommended Action No action is required.

Error Message %ALPS-7-CIRCUIT_DROPS_QUEUE_OVERFLOW: Threshold exceeded for queue overflow drops for circuit [chars] Explanation The number of ALPS circuit drops due to queue overflow exceeds the ALPS circuit


Error Message %ALPS-7-CIRCUIT_DROPS_VC_RESET: Threshold exceeded for X.25 VC Reset drops for circuit [chars] Explanation The number of ALPS circuit drops due to X.25 VC Reset exceeds the ALPS circuit



40

System Messages AP Messages

Error Message %ALPS-7-PEER_DROPS_MAX_SIZE_EXCEEDED: Threshold exceeded for maximum size exceeded drops for peer ([IP_address], [chars]). Explanation The number of ALPS peer drops due to maximum size exceeded, exceeds the ALPS peer


Error Message %ALPS-7-PEER_DROPS_PEER_UNREACHABLE: Threshold exceeded for peer unreachable peer drops for peer ([IP_address], [chars]). Explanation The number of ALPS peer drops due to a peer unreachable condition exceeds the ALPS

peer threshold value. Recommended Action No action is required.

Error Message %ALPS-7-PEER_DROPS_QUEUE_OVERFLOW: Threshold exceeded for TCP Queue overflow peer drops for peer ([IP_address], [chars]). Explanation The number of ALPS peer drops due to queue overflow exceeds the ALPS peer


Error Message %ALPS-7-PEER_DROPS_VERSION_MISMATCH: Threshold exceeded for version mismatch peer drops for peer ([IP_address], [chars]). Explanation The number of ALPS peer drops due to version mismatch exceeds the ALPS peer


AP Messages This section contains Authentication Proxy (AP) messages.

AP-1 Error Message %AP-1-POSTURE_POLICY_ERROR: POLICY=[chars]| POLICYNAME=[chars]| IP=[IP_address]| ERROR= Explanation The specified policy was not applied for the host IP due to the reason specified as Error. Recommended Action When the “POLICY” character string is “HOST ACL,” verify that an input

access list is defined and configured on the interface. A “URL REDIRECT ACL” policy needs a URL-redirect VSA to have an associated access control list URL-redirect-ACL VSA that can be


41


used to determine HTTP redirect critera. HTTP packets that match the ACL are subject to redirection. When a URL-redirect-ACL access control list is not specified or is not configured, the host will not be set up for HTTP redirection.

AP-4 Error Message %AP-4-AUTH_PROXY_NOMEM: Sufficient memory was not available to [chars] Explanation There was not enough memory to perform the specified operation. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message %AP-4-POSTURE_EXCEED_MAX_INIT: Exceeded maximum limit ([dec]) on entires in authentication proxy posture cache in initializing state Explanation The number of entries that are in the Authentication Proxy posture cache and in an initializing state has exceeded the maximum limit. Recommended Action This condition might indicate a Denial of Service attack. Copy the message

exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

AP-5 Error Message %AP-5-AP_AAA_DOWN: Event=AAA [chars]. HOST=%i| POLICY [chars]=[chars].| AUDITSESSID=[chars] Explanation The AAA servers defined by the method list are unreachable for the host and the policy

being applied. Recommended Action Determine the status and availability of the AAA servers.


42


AP-6 Error Message %AP-6-FALLBACK_REQ: IP=%i| MAC=%u| PROFILE_NAME=[chars]| EVENT=[chars]| AUDITSESSID=[chars] Explanation A fallback to authentication proxy has been initiated or terminated for the host. Recommended Action No action is required.

Error Message %AP-6-POSTURE_DOWNLOAD_ACL: Send AAA request to download ([chars]) named access control list Explanation The system has sent a request to AAA to retrieve the contents of the specified

downloadable ACL. Recommended Action This message is informational. No action is required.

Error Message %AP-6-POSTURE_POLICY: [chars] [chars] ([chars]) policy for host ([IP_address]) Explanation This message specifies the policy that was enforced for or removed from the specified

host. The policy can be either an ACL or a URL to which any intercepted HTTP traffic is redirected. Recommended Action This message is informational. No action is required.

Error Message %AP-6-POSTURE_START_VALIDATION: IP=[IP_address]| Interface=[chars] Explanation The system has created an entry for the host in the Authentication Proxy posture cache

and has initiated the posture validation process. Recommended Action This message is informational. No action is required.

Error Message %AP-6-POSTURE_STATE_CHANGE: IP=[IP_address]| STATE=[chars] Explanation The state of posture validation changed for the specified host in the Authentication

Proxy posture validation cache. Recommended Action This message is informational. No action is required.


43

System Messages APS Messages

APS Messages This section contains Automatic Protection Switching (APS) messages.

APS-2 Error Message %APS-2-INITSYS: [chars] Explanation A software error occurred during initialization of the APS subsystem. Recommended Action Check for sufficient processor memory. Copy the message exactly as it appears

on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %APS-2-NOSOCKET: Failed To Open Socket Explanation This message is posted when the APS subsystem fails to create a UDP socket for exchanging APS channel protocol messages over APS message channel configured for IP. This is usually caused by a low memory condition in the system Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

APS-6 Error Message %APS-6-BIDIRSWCH: Group [chars]: Remote Request - [chars] Explanation This message is posted by the local network element after an APS switchover that is triggered by an APS request from the remote network element. Recommended Action No action is required.

Error Message

%APS-6-CHNLACTIVE: Group [chars] - [chars] channel is now ACTIVE

Explanation This message is posted when a previously standby channel becomes the active channel. Recommended Action No action is required.


44

System Messages ARAP Messages

Error Message

%APS-6-ENAUTFOVR: Enable Auto-Failover On [chars]

Explanation This message is posted when APS software enables hardware to perform APS actions

for failures detected by the hardware. Recommended Action No action is required.

ARAP Messages This section contains Apple Remote Access Protocol messages.

Error Message %ARAP-0-VSERROR: TTY [dec]: VS queued error Explanation An internal software error occured. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ARAP-4-NOEXTTACACS: TTY [dec]: arap TACACS is configured but extended TACACS is not. Explanation Terminal Access Controller Access Control System (TACACS) authentication failed

because extended TACACS is not configured. Recommended Action Configure extended TACACS.


45

System Messages ARCHIVE_CONFIG Messages

ARCHIVE_CONFIG Messages This section contains ARCHIVE_CONFIG messages.

ARCHIVE_CONFIG-4 Error Message %ARCHIVE_CONFIG-4-ARCHIVE_DELETE_FAILED: Delete of a previously saved archive of the router configuration could not be completed. Explanation The router could not delete a file that had previously been written. The file that was

being deleted contains an archive of the router configuration. This condition could occur if the file was manually deleted. Recommended Action No action is required.

Error Message %ARCHIVE_CONFIG-4-ARCHIVE_SKIPPED: Archive of router configuration was skipped due to a previous initiation. Explanation An attempt to create an archive was started while one archive operation had already

been started. Only one archive can be created at a time. Two or more simultaneous archive operations are not allowed. This condition could occur if two users attempt to create an archive simultaneously. Recommended Action Retry the archive creation when the current archive operation has finished

being written.

ARCHIVE_CONFIG-6 Error Message %ARCHIVE_CONFIG-6-ARCHIVE_CREATE_FAILED_STANDBY: Could not create an archive of the router configuration on the standby RP. Explanation The router could not create an archive file on the standby route processor (RP). The file

that was being created contains an archive of the router configuration. This condition can occur if the active RP cannot communicate with the standby RP. Recommended Action No action is required.

Error Message %ARCHIVE_CONFIG-6-ARCHIVE_DELETE_FAILED_STANDBY: Delete of a previously saved archive of the router configuration could not be completed on the standby RP. Explanation The router could not delete a file that was previously written on the standby route

processor (RP). The file that was being deleted contains an archive of the router configuration. This condition might occur if the file was manually deleted or if the active RP cannot communicate with the standby RP. Recommended Action No action is required.


46

System Messages ARCHIVE_DIFF Messages

ARCHIVE_DIFF Messages This section contains ARCHIVE_DIFF messages.

ARCHIVE_DIFF-3 Error Message %ARCHIVE_DIFF-3-DIFF_CMD_INIT_FAILED: Failed to register the special case [chars] command:"[chars]" during initialization. Config Diff and Rollback cannot be used as a result of this error. Explanation An internal software error occurred during initialization of the Archive Diff program.

As a result of this error, checking configuration differences (config diff) and rollback operations cannot be performed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ARCHIVE_DIFF-3-DIFF_INIT_FAILED: Could not initialize the Config Diff and Rollback subsystem Explanation An internal software error occurred during initialization. Config diff and rollback

cannot be used as a result of this error. Recommended Action Copy the message exactly as it appears on the console or in the system log.



47


ARCHIVE_DIFF-5 Error Message %ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_BACKUP: Backing up current running config to [chars] Explanation The current running configuration is saved so that when the timer expires, if no

confirmation has been received from the user to confirm configuration changes, the system will roll back to the saved configuration. Recommended Action This message occurs during normal operation of the rollback confirmed

change. No action is required.

Error Message %ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_CANCEL: User: [chars]: Rollback Confirmed Change is cancelled due to [chars] failure Explanation Rollback confirmed change is normally configured along with other configuration

operations, such as config term or config replace. If those operations failed, rollback confirmed change should not be activated. Recommended Action Remove the error condition and retry.

Error Message %ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_CONFIRM: User: [chars]: Confirm the configuration change Explanation The configuration change is confirmed. The timer for rolling to the previously saved configuration is cancelled. Recommended Action This message occurs in normal operation of the rollback confirmed change. No

action is required.

Error Message %ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_RESET_ABSTIMER: User: [chars]: Reset Rollback Confirmed Change timer(absolute) to %lu minute Explanation The rollback confirmed change timer (absolute) was reset to a new value. Recommended Action This message occurs in normal operation of the rollback confirmed change. No

action is required.

Error Message %ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_RESET_IDLETIMER: User: [chars] Reset Rollback Confirmed Change timer(idle) to %lu minute Explanation The rollback confirmed change timer (idle) was reset to a new value. Recommended Action This message occurs in normal operation of the rollback confirmed change. No

action is required.


48


Error Message %ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_REVERTNOW: User: [chars]: Rollback immediately. Explanation A rollback will happen immediately and the timer will be cancelled. Recommended Action This message occurs in normal operation of the rollback confirmed change. No

action is required.

Error Message %ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_ROLLBACK_RETRY: Failed to acquire configuration lock. Rollback did not start. Schedule to retry in 5 minutes Explanation Because the system was unable to acquire a configuration lock, configuration rollback

did not start. A retry will be scheduled. Recommended Action This message occurs in normal operation of the rollback confirmed change. No

action is required.

Error Message %ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_ROLLBACK_START: Start rolling to: [chars] Explanation The timer for rollback confirmed change has expired. System will roll back to the previously saved configuration. Recommended Action This message occurs in normal operation of the rollback confirmed change. No

action is required.

Error Message %ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_START_ABSTIMER: User: [chars]: Scheduled to rollback to config [chars] in %lu minutes Explanation The system will wait until the timer expires for the user to confirm the configuration changes. If the confirmation is not received before the timer expires, the router will roll back to the previous configuration. Recommended Action To keep your configuration changes, enter the configure confirm command.

Otherwise, no action is required.

Error Message %ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_START_IDLETIMER: User: [chars]: Scheduled to rollback to config [chars] if session has been idle for %lu minutes Explanation The system will wait until the timer expires for the user to confirm the configuration changes. If the confirmation is not received before the timer expires, the router will roll back to the previous configuration. Recommended Action To keep your configuration changes, enter the configure confirm command.



49

System Messages ARCHIVE_ISSU Messages

Error Message %ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_WARNING_ABSTIMER: System will rollback to config [chars] in one minute. Enter Explanation Rollback to the previous configuration will start in one minute unless the user confirms

the configuration changes. Recommended Action To keep your configuration changes, enter the configure confirm command.


Error Message %ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_WARNING_IDLETIMER: User [chars] on tty [dec] has been idle for %lu minutes. System will rollback to config [chars] in oneminute if it continues to be idle. Enter Explanation Rollback to the previous configuration will start in one minute unless the user confirms

the configuration changes. Recommended Action To keep your configuration changes, enter the configure confirm command.


ARCHIVE_ISSU Messages This section contains messge related to the In Service Software Upgrade facility.

ARCHIVE_ISSU-2 Error Message %ARCHIVE_ISSU-2-GET_BUFFER: Archive ISSU client failed to get buffer for message. Error: [dec] ([chars]) Explanation The Archive ISSU client failed to get buffer space for building a negotiation message.

A negotiation message cannot be sent to the standby device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly. Recommended Action Copy the error message exactly as it appears on the console or in the system

log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show logging and show checkpoint client command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.


50


Error Message %ARCHIVE_ISSU-2-INIT: Archive ISSU client initialization failed to [chars]. Error: [dec] ([chars]) Explanation The Archive ISSU client could not be initialized. This initialization failure must be

addressed before in-service software upgrade or downgrade can be performed successfully. If you do not address this failure, there will be downtime during software upgrade or downgrade. Recommended Action Copy the error message exactly as it appears on the console or in the system

log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message %ARCHIVE_ISSU-2-SEND_NEGO_FAILED: Archive ISSU client failed to send negotiation message. Error: [dec] ([chars]) Explanation The Archive ISSU client failed to send a session negotiation message to the peer device.

If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly. Recommended Action Issue the show logging and show checkpoint client command to gather data

that may help identify the nature of the error. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message %ARCHIVE_ISSU-2-SESSION_NEGO_FAIL_START: Failed to start Archive ISSU session negotiation. Error: [dec] ([chars]) Explanation The Archive ISSU client failed to start session negotition.If a problem occurs with the

ISSU session start, the standby device cannot be brought up properly. Recommended Action Issue the show issu session command to gather data that may help identify the

nature of the error. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.


51


Error Message %ARCHIVE_ISSU-2-SESSION_REGISTRY: Archive ISSU client failed to register session information. Error: [dec] ([chars]) Explanation The Archive ISSU client failed to register session information. If a problem occurs with

the ISSU session registration, the standby device cannot be brought up properly. Recommended Action Issue the show issu capability entries and show issu session and show issu negotiated capability command to gather data that may help identify the nature of the error. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

ARCHIVE_ISSU-3 Error Message %ARCHIVE_ISSU-3-INVALID_SESSION: Archive ISSU client does not have a valid registered session. Explanation The Archive ISSU client does not have a valid registered session. Recommended Action Issue the show issu capability entries and show issu session and show issu negotiated capability command to gather data that may help identify the nature of the error. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message %ARCHIVE_ISSU-3-MSG_NOT_OK: Archive ISSU client ’Message Type [dec]’ is not compatible Explanation The Archive ISSU client received an incompatible message from the peer device. The

message cannot be processed. Recommended Action Issue the show issu message group and show issu session and show issu negotiated version command to gather data that may help identify the nature of the error. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.


52


Error Message %ARCHIVE_ISSU-3-MSG_SIZE: Archive ISSU client failed to get the MTU for Message Type [dec].Error: [dec] ([chars]) Explanation The Archive ISSU client failed to calculate the MTU for the specified message. The

Archive ISSU client is not able to send the message to the standby device. Recommended Action Issue the show issu message group and show issu session and show issu negotiated version command to gather data that may help identify the nature of the error. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message %ARCHIVE_ISSU-3-SESSION_UNREGISTRY: Archive ISSU client failed to unregister session information. Error: [dec] ([chars]) Explanation The Archive ISSU client failed to unregister session information. Recommended Action Issue the show issu capability entries and show issu session and show issu negotiated capability command to gather data that may help identify the nature of the error. CCopy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message %ARCHIVE_ISSU-3-TRANSFORM_FAIL: Archive ISSU client [chars] transform failed for ’Message Type [dec]’. Error: [dec] ([chars]) Explanation The Archive ISSU client could not transform the specified message type. If the transmit transformation failed, the checkpoint message was not sent to the standby device. If the receive transformation failed, the checkpoint message was not applied on the standby device. In both cases, the Archive state between the active device and the standby device is not identical. Recommended Action Issue the show issu session and show issu negotiated version command to gather data that may help identify the nature of the error. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.


53

System Messages ATM Messages

ATM Messages This section contains ATM messages.

ATM-1 Error Message %ATM-1-ISSU_NOMEMORY: Unit [dec], no memory for [chars] Explanation The requested operation could not be accomplished because of a low-memory

condition. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

ATM-3 Error Message %ATM-3-ISSU_SENDFAILED: ATM ISSU: send message failed, rc = [dec] Explanation The sending of a message has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


ATM-4 Error Message %ATM-4-ISSU_INCOMPATIBLE: atm-issu-compat: returned FALSE Explanation The compatibility checking has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



54

System Messages ATMPA Messages


Error Message %ATM-4-ISSU_XFORM: [chars]: failed, rc=[chars] Explanation The transform has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


ATMPA Messages Error Message %ATMPA-1-INVALIDCONFIG: VIP2-40 and below only supports one OC-3 ATM PA. The other PA bay needs to be emptied in order for the ATM PA to function. Explanation The bandwidth requirements of the installed port adapters exceed the processor’s rated

capability. Recommended Action Either remove one of the port adapters or upgrade the VIP.

Error Message %ATOM_TRANS-3-INIT_FAIL: Failed to start AToM Manager Explanation Failed to start and initialize AToM Manager. Recommended Action Copy the error message exactly as it appears on the console or in the system



55

System Messages ATMSPA Messages

ATMSPA Messages This section contains ATM Shared Port Adapter (ATMSPA) messages.

ATMSPA-2 Error Message %ATMSPA-2-INITFAIL: [chars] - Init Failed return code: [int] Explanation The shared port adapter (SPA) failed to complete hardware initialization. One of the devices in the SPA failed to initialize successfully. Information about the failed device is specified in the message text on the console or in the system log. Recommended Action Power down and reseat the indicated SPA card. If the condition persists, copy

the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

ATMSPA-3 Error Message %ATMSPA-3-DATA_ERROR: [chars] Error [hex] [chars] Explanation A data path protocol violation or sequence error has been detected. The message text on the console or in the system log provides more information on the specific cause of the error. Recommended Action Copy the message exactly as it appears on the console or in the system log.



56


Error Message %ATMSPA-3-FATAL_ERROR: occurred on [chars]. Resetting SPA Explanation The shared port adapter (SPA) has been reset because of a critical error in one of its

devices. The error could either be a single occurrence of an event or multiple occurrences within a period of time. The message text on the console or in the system log provides more information on the specific cause of the error. Recommended Action If the SPA is reset more than once, copy the message exactly as it appears on

the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %ATMSPA-3-FPD_VER_DEPENDENCY_NOTE: Cannot perform the requested FPD update operation because [chars] in subslot [int]/[int] has incompatible HW version [int].[int] with FPD image version [dec].[dec] for FPD ID [dec]. Only image version greater than [int].[int] can be used in the update operation of [chars] with HW version greater than [int].[int]. Explanation The version of the field-programmable device (FPD) image from the FPD image bundle

or package is not compatible with the hardware (HW) version of the target card. Recommended Action If the SPA is reset more than once, copy the message exactly as it appears on


Error Message %ATMSPA-3-GEN_ERROR: [chars] Error [hex] [chars] Explanation The error that is specified in the message has been detected. Recommended Action Copy the message exactly as it appears on the console or in the system log.



57


Error Message %ATMSPA-3-HW_ERROR: [chars] Error [hex] [chars] Explanation A hardware error has been detected. The message text on the console or in the system

log provides more specific informationabout the error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ATMSPA-3-QOS_ALLOC_FAILED: [chars] [chars] [chars]: [dec] Explanation Traffic-shaping parameters could not be configured because the number of unique shaping parameters that are configured on the PVCs or PVPs in this specified ATM SPA is over the maximum limit. The maximum number of unique shaping parameters that can be configured on the PVCs or PVPs is 4096. Recommended Action Ensure that the total number of unique shaping parameters that are configured on both PVCs and PVPs does not exceed the maximum limit of 4096.

Error Message %ATMSPA-3-SW_ERROR: [chars] Error [hex] [chars] Explanation A software error has been detected. The message text on the console or in the system

log provides more specific information about the error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ATMSPA-3-VCQ_ERROR: [chars]: VC queue configuration failed due to un-initialized queue table(global identifier [dec]) Explanation The software configuration of a virtual circuit (VC) queue failed because of an

uninitialized queue table. Recommended Action Attempt to perform a soft OIR operation by entering the command that is

described in the shared port adapter software configuration guide. If the condition persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve


58


the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

ATMSPA-4 Error Message %ATMSPA-4-VCSETUP: [chars]: VC setup command received on the LC for an existing VC (VCD [dec]) Explanation A command to set up a virtual circuit (VC) has been received for a VC that has already

been set up and configured by a previous setup VC command from the RP. A duplicate setup command may indicate that the RP did not receive a response from the line card for the previous setup command. Recommended Action No action is required.

Error Message %ATMSPA-4-VCTEARDOWN: [chars]: VC tear down command received on the LC for a non-existing VC (VCD [dec]) Explanation The virtual circuit (VC) does not exist on the line card. The VC probably has been torn

down by a previous teardown command from the route processor (RP). A duplicate teardown command may indicate that the RP did not receive a response from the line card for the previous teardown command. Recommended Action No action is required.

Error Message %ATMSPA-4-VPSETUP: [chars]: VP setup command received on the LC for an existing VP (VPI [dec]) Explanation A command to set up a virtual path (VP) has been received for a VP that has already

been set up. The VP has already been configured by a previous setup VP command from the route processor (RP). A duplicate setup command may indicate that the RP did not receive a response from the line card for the previous setup command. Recommended Action No action is required.


59

System Messages ATOM_NP_CLIENT Messages

Error Message %ATMSPA-4-VPTEARDOWN: [chars]: VP tear down command received on the LC for a non-existing VP (VPI [dec]) Explanation The virtual path (VP) does not exist on the line card. The VP probably has been torn

down by a previous teardown command from the route processor (RP). A duplicate teardown command may indicate that the RP did not receive a response from the line card for the previous teardown command. Recommended Action No action is required.

ATOM_NP_CLIENT Messages This section contains Any Transport Over MPLS (AToM) NP client messages.

ATOM_NP_CLIENT-3 Error Message %ATOM_NP_CLIENT-3-INFO: [chars] Explanation The AToM NP client failed to initialize properly, which will result in improper operation

of the Any Transport Over MPLS feature. Recommended Action Attempt to reload the IOS image on the affected card or platform. If this

message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %ATOM_NP_CLIENT-3-NOMEM: [chars] Explanation The AToM NP client failed to initialize properly, which will result in improper operation

of the Any Transport Over MPLS feature. Recommended Action This error may indicate that more memory must be installed on the affected

card or platform to service all the features and related entities enabled by the configuration. Attempt to reload the IOS image on the affected card or platform. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support


60

System Messages ATOM_SEG Messages


ATOM_NP_CLIENT-4 Error Message %ATOM_NP_CLIENT-4-WARN: [chars] [dec] [chars] Explanation An AToM entry could not be added because the entry passed is invalid. Recommended Action Attempt to reload the IOS image on the affected card or platform. If this

message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

ATOM_SEG Messages This section contains Any Transport Over MPLS (AToM) Segment Handler messages.

ATOM_SEG-3 Error Message %ATOM_SEG-3-CHUNKFREE: Error freeing [chars] [hex] Explanation An error has occurred in the AToM segment handler. Recommended Action Copy the message exactly as it appears on the console or in the system log.



61

System Messages ATOM_TRANS Messages

Error Message %ATOM_SEG-3-ILLEGALUPD: Illegal label [dec] update [chars] Explanation An error has occurred in the AToM Segment Handler. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ATOM_SEG-3-NOTSUPP: Unsupported update [chars] Explanation An error has occurred in the AToM segment handler. Recommended Action Copy the message exactly as it appears on the console or in the system log.


ATOM_TRANS Messages This section contains Any Transport Over MPLS (AToM) Layer 2 messages.

ATOM_TRANS-3 Error Message %ATOM_TRANS-3-INIT_FAIL: Failed to start AToM Manager Explanation Failed to start and initialize AToM Manager. Recommended Action Copy the message exactly as it appears on the console or in the system log.



62

System Messages ATOM_TRANS Messages


Error Message %ATOM_TRANS-3-LABEL_ALLOC_FAIL: Failed to allocate local label for peer:%i, vcid:%u Explanation The system was unable to allocate a local label for the specified AToM virtual circuit. Recommended Action Copy the message exactly as it appears on the console or in the system log.


ATOM_TRANS-4 Error Message %ATOM_TRANS-4-CONFIG: [chars] Explanation The AToM pseudowire is using an unacceptable configuration. Recommended Action Copy the message exactly as it appears on the console or in the system log.



63

System Messages AUDIT Messages

AUDIT Messages This section contains audit messages.

AUDIT-1 Error Message %AUDIT-1-FILE_ROLLOVER: Audit File Roll-over: [dec] Explanation The audit circular file has rolled over. Recommended Action Increase the size of the audit file.

AUTHMGR Messages This section contains Auth Manager messages.

AUTHMGR-5 Error Message %AUTHMGR-5-FAIL: Authorization failed for client ([chars]) on Interface [chars] Explanation The client was unable to obtain authorization on the interface. Recommended Action No action is required.

Error Message %AUTHMGR-5-MACMOVE: MAC address ([enet]) moved from Interface [chars] to Interface [chars] Explanation Client has moved to a new interface without logging off of the previous one. Recommended Action No action is required.

Error Message %AUTHMGR-5-MACREPLACE: MAC address ([enet]) on Interface [chars] is replaced by MAC ([enet]) Explanation A new client has triggered a violation causing an existing client to be replaced Recommended Action No action is required.


64

System Messages AUTHMGR Messages

Error Message %AUTHMGR-5-SECURITY_VIOLATION: Security violation on the interface [chars], new MAC address (%e) is seen Explanation A host on the specified interface is attempting to gain access to the network or is trying

to authenticate in a host mode that does not support the number of hosts attached. This incident is treated as a security violation and the port has been error-disabled. Recommended Action Ensure that the port is configured to support the number of hosts attached.

Enter the shutdown command followed by no shutdown command to restart the port.

Error Message %AUTHMGR-5-SECURITY_VIOLATION_VLAN: Security violation on the interface [chars], new MAC address ([enet]) is seen on vlan [dec]. Explanation A host on the specified interface is attempting to gain access into the network or is

trying to authenticate in a host mode that does not support the number of hosts attached. This is treated as a security violation and the port has been error-disabled. This log provides vlaninformation along with the mac. Recommended Action Ensure that the port is configured to support the number of hosts attached.

Enter the shutdown command followed by no shutdown command to restart the port.

Error Message %AUTHMGR-5-START: Starting ’[chars]’ for client ([chars]) on Interface [chars] Explanation The authentication manager is starting an authentication method for the client. Recommended Action No action is required.

Error Message %AUTHMGR-5-SUCCESS: Authorization succeeded for client ([chars]) on Interface [chars] Explanation Authorization was successful for the client. Recommended Action No action is required.

Error Message %AUTHMGR-5-UNAUTHORIZED: Interface [chars] unauthorized Explanation The specified port has become unauthorized. Recommended Action No action is required.

Error Message %AUTHMGR-5-VLANASSIGN: VLAN [dec] assigned to Interface [chars] Explanation A VLAN was assigned to the interface. Recommended Action No action is required.


65

System Messages AUTH_MGR_ISSU Messages

AUTHMGR-7 Error Message %AUTHMGR-7-FAILOVER: Failing over from ’[chars]’ for client ([chars]) on Interface [chars] Explanation The authorization manager will fail over from the current authentication method to another method. Recommended Action No action is required.

Error Message %AUTHMGR-7-NOMOREMETHODS: Exhausted all authentication methods for client ([chars]) on Interface [chars] Explanation All available authentication methods have been tried for the client, but authentication

has failed. Recommended Action No action is required.

Error Message %AUTHMGR-7-RESULT: Authentication result ’[chars]’ from ’[chars]’ for client ([chars]) on Interface [chars] Explanation The authentication result and method are displayed for the client. Recommended Action No action is required.

AUTH_MGR_ISSU Messages This section contains Auth Manager in-service software upgrade (ISSU) messages.

AUTH_MGR_ISSU-2 Error Message %AUTH_MGR_ISSU-2-GET_BUFFER: Auth Mgr ISSU client failed to get buffer for message. Error: [dec] ([chars]) Explanation The authentication manager ISSU client was unable to get buffer space for building a

negotiation message. A negotiation message cannot be sent to the standby device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the


66


following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show checkpoint client commands and your pertinent troubleshooting logs.

Error Message %AUTH_MGR_ISSU-2-INIT: Auth Mgr ISSU client initialization failed to [chars]. Error: [dec] ([chars]) Explanation The authentication manager ISSU client could not be initialized. This initialization

failure must be addressed before an in-service software upgrade or downgrade can be performed successfully. Otherwise, a software upgrade or downgrade will result in downtime. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show checkpoint client commands and your pertinent troubleshooting logs.

Error Message %AUTH_MGR_ISSU-2-SEND_NEGO_FAILED: Auth Mgr ISSU client failed to send negotiation message. Error: [dec] ([chars]) Explanation The authentication manager ISSU client was unable to send a session negotiation

message to the peer device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs.


67


Error Message %AUTH_MGR_ISSU-2-SESSION_NEGO: Auth Mgr ISSU client encountered unexpected client nego_done. Error: [dec] ([chars]) Explanation An ISSU-compliant client transitions through a series of internal states. The

authentication manager ISSU client encountered a client negotiation done state that was unexpected. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs.

Error Message %AUTH_MGR_ISSU-2-SESSION_REGISTRY: Auth Mgr ISSU client failed to register session information. Error: [dec] ([chars]) Explanation The authentication manager ISSU client was unable to register session information. If a problem occurs with the ISSU session registration, the standby device cannot be brought up properly. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs. Recommended Action show tech-support commands and your pertinent troubleshooting logs.


68


AUTH_MGR_ISSU-3 Error Message %AUTH_MGR_ISSU-3-CAP_INVALID_SIZE: Auth Mgr ISSU client capability list is empty. Explanation The authentication manager ISSU client capability exchange list is empty, which is an invalid condition. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show issu capability entries commands and your pertinent troubleshooting logs.

Error Message %AUTH_MGR_ISSU-3-CAP_NOT_COMPATIBLE: Auth Mgr ISSU client capability exchange result incompatible. Explanation Based on the results of the capability exchange, the authentication manager ISSU client

is not compatible with the peer. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show issu capability entries commands and your pertinent troubleshooting logs.

Error Message %AUTH_MGR_ISSU-3-INVALID_SESSION: Auth Mgr ISSU client does not have a valid registered session. Explanation The authentication manager ISSU client does not have a valid registered session. Recommended Action Copy the message exactly as it appears on the console or in the system log.



69


following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs.

Error Message %AUTH_MGR_ISSU-3-MAUTH_VLAN_ASSIGN_NOT_COMPATIBLE: Multi Auth VLAN Assignment is active in one of the ports and the peer does not support Multi Auth VLAN Assignment. Explanation At least one of the ports have Multi Auth host mode and VLAN assignment

simultaneously enabled and ISSU cannot proceed since Standby does not support Multi Auth VLAN assignment. Shut down the ports in which Multi Auth VLAN assignment is enabled and retry ISSU. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs.

Error Message %AUTH_MGR_ISSU-3-MSG_NOT_COMPATIBLE_WITH_PEER: ’Feature Id [dec], Tag [dec]’ is not supported by Auth Mgr ISSU client at peer Explanation The authentication manager ISSU client at the peer supervisor does not support this

message type. The authentication manager client will be marked as incompatible with the peer. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %AUTH_MGR_ISSU-3-MSG_NOT_OK: Auth Mgr ISSU client ’Feature Id [dec], Tag [dec]’ is not compatible Explanation The authentication manager ISSU client received an incompatible message from the

peer device. The message cannot be processed. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying


70


information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs.

Error Message %AUTH_MGR_ISSU-3-MSG_SIZE: Auth Mgr ISSU client failed to get the MTU for Feature Id [dec], Tag [dec]. Error: [dec] ([chars]) Explanation The authentication manager ISSU client was unable to calculate the MTU for the

specified message. The authentication manager ISSU client is not able to send the message to the standby device. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %AUTH_MGR_ISSU-3-SESSION_UNREGISTRY: Auth Mgr ISSU client failed to unregister session information. Error: [dec] ([chars]) Explanation The authentication manager ISSU client was unable to unregister session information. Recommended Action Copy the message exactly as it appears on the console or in the system log.



71

System Messages AUTORP Messages

Error Message %AUTH_MGR_ISSU-3-TRANSFORM_FAIL: Auth Mgr ISSU client [chars] transform failed for ’Feature Id [dec], Tag [dec]’. Error: [dec] ([chars]) Explanation The authentication manager ISSU client could not transform the specified message type.

If the transmit transformation failed, the checkpoint message was not sent to the standby device. If the receive transformation failed, the checkpoint message was not applied on the standby device. In either case, the authentication manager state between the active device and the standby device is not identical. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs.

AUTORP Messages This section contains Protocol Independent Multicast (PIM) version 2 Auto-Rendezvous Point (AUTORP) messages.

AUTORP-2 Error Message %AUTORP-2-RADIXINIT: Error initializing the Auto-RP radix tree Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



72

System Messages AUTORP Messages

AUTORP-4 Error Message %AUTORP-4-OVERLAP: AutoRP [chars] packet, group %i with mask %i removed because of multicast boundary for %i with mask %i Explanation The multicast boundary has a longer network mask than the Auto-Rendezvous Point

encoded group. Recommended Action Use postive permit clauses in the AutoRP access control list.

Error Message %AUTORP-4-PAK_ERR: AutoRP [chars] packet is received on interface [chars] with Source address=[IP_address], Destination address=[IP_address], TTL=[int], IP length=[int] Datagram size/UDP length=[int] Explanation The AutoRP packet was received with wrong packet length. The packet has been

dropped as it may be a malformed packet.

Error Message No action is required.%AUTORP-4-PRM_DEL: Error expiring semi-static RP-mapping entry (%i/[dec], RP:%i) Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %AUTORP-4-RADIXINSERT: Error inserting a new entry into the RP-mapping radix tree Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



73

System Messages AUTOSHUT Messages

AUTORP-5 Error Message %AUTORP-5-CRP_REMOVED: C-RP %i on interface [chars] has been removed Explanation PIM is disabled on the interface or the interface card has been removed. Recommended Action No action is required.

Error Message %AUTORP-5-MAPPING: RP for %i/[dec] is now %i Explanation A new Auto-Rendezvous Point has been elected for the subject group prefix. Recommended Action No action is required.

AUTORP-6 Error Message %AUTORP-6-RP_MAPPING_IDB_DEL: AutoRP RP-MAPPING IDB [chars] is deleted Explanation The configured rp-mapping IDB has been deleted. Recommended Action No action is required.

AUTOSHUT Messages This section contains automatic shutdown (utoshut) messages.

AUTOSHUT-4 Error Message %AUTOSHUT-4-MOD_AUTOSHUT: Module [dec] shutdown automatically, reset [dec] times within [dec] minutes due to [chars]. Explanation This message includes information about the automatic shutdown of a module. Recommended Action If this message recurs, copy the message exactly as it appears on the console

or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


74

System Messages BACKPLANE_BUS_ASIC Messages

AUTOSHUT-5 Error Message %AUTOSHUT-5-MOD_AUTOSHUT_SLOW: Module [dec] reset frequency exceeded threshold but over [dec] minutes. Hence NOT powering down module. Explanation The module’s reset frequency has exceeded the threshold, but over a period more than

the preset period. Recommended Action No action is required.

BACKPLANE_BUS_ASIC Messages This section contains backplane bus ASIC messages.

BACKPLANE_BUS_ASIC-3 Error Message %BACKPLANE_BUS_ASIC-3-FAILURE_INTR_CFG: Failure to setup the Backplane Bus ASIC device interrupts. Explanation The line card internal ASIC could not be initialized. As a result, the device has been

disabled and the datapath will not be operational. Recommended Action Copy the message exactly as it appears on the console or in the system log.


BACKPLANE_BUS_ASIC-4 Error Message %BACKPLANE_BUS_ASIC-4-DEV_RESET: Backplane Bus Asic reset, interrupt [chars] Explanation The backplane bus ASIC in the MSC/FlexWAN-ENH has received a fatal error. The

ASIC will be reset and the MSC/FlexWAN-ENH will attempt to continue normal operation. Recommended Action No action is required if traffic recovers. Otherwise, enter the show platform hardware hyperion all command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at


75


http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %BACKPLANE_BUS_ASIC-4-EARL_BUS_SYNC_ERR: Failed to sync Earl bus, Backplane Bus Asic version [dec] Explanation The backplane bus ASIC in the line card failed to synchronize with the EARL bus. Recommended Action No action is required if traffic recovers. Otherwise, enter the show platform hardware hyperion all command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %BACKPLANE_BUS_ASIC-4-UNEXPECTED_VERSION: Unexpected Backplane Bus ASIC version. Explanation The line card is unable to recognize the version of the Hyperion ASIC. Recommended Action No action is required if traffic passes through the line card. Otherwise, check the Bug Toolkit on Cisco’s web site to determine a version in which the bug is fixed and upgrade accordingly. If traffic does not pass after the upgrade, enter the show platform hardware hyperion all command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


76


BACKPLANE_BUS_ASIC-5 Error Message %BACKPLANE_BUS_ASIC-5-BUS_MODE_CHANGE: The System Switching Bus Mode changed to [chars] mode Explanation The supervisor engine has instructed this line card to change the mode on the switching

bus. Recommended Action No action is required.

Error Message %BACKPLANE_BUS_ASIC-5-BUS_SEQ_ERR: Constellation bus Sequence Error. Resetting Backplane Bus Asic. Explanation The switch processor has detected a sequence error on the backplane bus. A reset

sequence from the EARL has been called to recover from this error. System traffic should recover and continue normally. Recommended Action No action is required if traffic recovers. Otherwise, enter the show platform hardware hyperion all command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %BACKPLANE_BUS_ASIC-5-DEV_INIT_FAILURE: The Backplane Bus Asic initialization failed Explanation The backplane bus ASIC could not be initialized. As a result, this device is not

operational and has been disabled. Recommended Action Copy the message exactly as it appears on the console or in the system log.



77


Error Message %BACKPLANE_BUS_ASIC-5-DEV_INTR_INFO: [chars] Explanation This message provides more information about the interrupts from the backplane bus

ASIC to the line card CPU. Recommended Action No action is required if traffic recovers. Otherwise, enter the show platform hardware hyperion all command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %BACKPLANE_BUS_ASIC-5-DEV_RESET_INFO: [chars] Explanation This message provides more information about the interrupts leading to the reset of the backplane bus ASIC. Recommended Action No action is required if traffic recovers. Otherwise, enter the show platform hardware hyperion all command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %BACKPLANE_BUS_ASIC-5-NULL_DEV_OBJECT: The Backplane Bus Asic device object pointer is set to NULL Explanation The memory location of the backplane bus ASIC device object is invalid. The backplane

bus ASIC operation is disabled and the device interrupt is now masked. Recommended Action Copy the message exactly as it appears on the console or in the system log.



78

System Messages BCM Messages

BCM Messages This section contains Broadcom (BCM) switch messages.

BCM-4 Error Message %BCM-4-ECC_L2CACHE: Corrected ECC from L2 cache Explanation A soft-parity error from the Layer 2 cache has been detected and corrected. Normal

system operation should continue. Recommended Action If there is a regular or sustained occurrence of this message, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %BCM-4-ECC_MEMORY: Corrected ECC from memory Explanation A soft-parity error from the memory has been detected and corrected. Normal system

operation should continue. Recommended Action If there is a regular or sustained occurrence of this message, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

BFD Messages This section contains Bidirectional Forwarding Detection (BFD) messages.


79

System Messages BFD Messages

BFD-3 Error Message %BFD-3-BUFPOOL: Creation of BFD Private Buffer Pool failed Explanation A private buffer pool could not be created in memory. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %BFD-3-CHUNK: Chunk malloc failure - [chars] - [hex] Explanation The system was unable to allocate memory. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %BFD-3-CHUNK_DESTROY: Unable to destroy [chars] Explanation The system was unable to deallocate memory. Recommended Action Copy the message exactly as it appears on the console or in the system log.



80


Error Message %BFD-3-DBSCAN: Session data removed durring scan [dec] Explanation An adjacency database corruption occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %BFD-3-IF_IN_USE: Interface [chars]([dec]) already in use Explanation The specified interface number is already in use. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %BFD-3-IF_NO_CLEAN: Could not free bfd idb array - still in use Explanation The bidirectional forwarding detection (BFD) interface descriptor blocks (IDBs) are

still in use and cannot be freed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



81


Error Message %BFD-3-ILL_IF: Illegal interface [dec][chars] Explanation The interface number is out of range for the platform. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %BFD-3-INVQELEM: Invalid queue element - [chars] Explanation An invalid queue element was detected. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %BFD-3-INVVER: Invalid version type Explanation An invalid version type was detected. Recommended Action Copy the message exactly as it appears on the console or in the system log.



82


Error Message %BFD-3-NBR: bfd_neighbor - client not found Explanation A client does not exist in the client list. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %BFD-3-NOCLIENT: Client not found Explanation No client exists in the BFD client list. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %BFD-3-NOIOUPROC: Failed to create BFD IOU Process Explanation The IOU process failed to start. Recommended Action Copy the message exactly as it appears on the console or in the system log.



83


Error Message %BFD-3-NOKADIS: Failed to start Kadis. Status [dec] Explanation The Kadis timer process failed to start. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %BFD-3-NOPPPROC: Failed to create BFD PP Process Explanation The pseudo-preemptive (PP) process failed to start. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %BFD-3-NO_TYPE: Neighbor address type not specified as ADDR_IP([dec]), [dec] Explanation A BFD client called a BFD neighbor with an uninitialized address type. Recommended Action Copy the message exactly as it appears on the console or in the system log.



84


Error Message %BFD-3-NULLDISC: Invalid Discriminator [hex], state [dec] Explanation An invalid discriminator value was detected. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message

%BFD-3-PACKET: bfd_pak_coalesce - [chars] failed

Explanation The packet buffer could not be obtained or coalesced. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %BFD-3-SWIDB: Failed to create BFD swidb subblock for interface [chars] Explanation An interface descriptor block (IDB) sub-block could not be created. Recommended Action Copy the message exactly as it appears on the console or in the system log.



85


Error Message %BFD-3-VERSION: Version change [chars] Explanation A version change error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %BFD-3-WAVL_DELETE_FAIL: Failed deleting node %x from wavl tree thread [dec] Explanation The BFD process was unable to delete a node from a wrapped AVL (WAVL) tree. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %BFD-3-WAVL_INIT_FAIL: Failed initializing wavl tree. Explanation The BFD process was unable to initialize a wrapped AVL (WAVL) tree. Recommended Action Copy the message exactly as it appears on the console or in the system log.



86


Error Message %BFD-3-WAVL_INSERT_FAIL: Failed inserting node %x to wavl tree thread [dec] Explanation The BFD process was unable to insert a node into a wrapped AVL (WAVL) tree. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %BFD-3-WAVL_TREE: Failed to malloc space for wavl tree. Explanation The BFD process was unable to allocate memory space for a wrapped AVL (WAVL)

tree. Recommended Action Copy the message exactly as it appears on the console or in the system log.


BFD-6 Error Message %BFD-6-MAX_DESCR: BFD discrminators exhausted. No more sessions can be created. Explanation The maximum number of BFD discriminators has been assigned. Recommended Action Copy the message exactly as it appears on the console or in the system log.



87

System Messages BFDFSM Messages

Error Message %BFD-6-MAX_SESSION: Maximum session creation limit [dec] reached. Explanation The maximum number of BFD sessions has been created. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %BFD-6-TX_ON_STANDBY: BFD transmit detected on standby Explanation The standby device attempted to transmit a packet. Recommended Action Copy the message exactly as it appears on the console or in the system log.


BFDFSM Messages This section contains Bidirectional Forwarding Detection (BFD) Finite State Machine (FSM) messages.

BFDFSM-3 Error Message %BFDFSM-3-INVEVENT: Invalid event_id [hex] Explanation An invalid event occurred in the state machine. Recommended Action Copy the message exactly as it appears on the console or in the system log.



88

System Messages BFDFSM Messages


Error Message %BFDFSM-3-INVSTATE: Invalid current state [hex] Explanation An invalid state occurred in the state machine. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %BFDFSM-3-INVTRANS: obj: [[hex]] event_id: [[hex]] er_p: [[hex]] arg: [[hex]] session state [chars] -> [chars] Explanation An invalid transition occurred in the state machine. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message

%BFDFSM-3-NOEVENT: Unable to apply event [hex]

Explanation A transition failure occurred in the state machine. Recommended Action Copy the message exactly as it appears on the console or in the system log.



89

System Messages BFD_HA Messages

Error Message

%BFDFSM-3-NULLMACH: Invalid machine pointer [hex]

Explanation The state machine contains an invalid pointer. Recommended Action Copy the message exactly as it appears on the console or in the system log.


BFD_HA Messages This section contains Bidirectional Forwarding Detection (BFD) high availability (HA) messages.

BFD_HA-2 Error Message %BFD_HA-2-CF: [chars][dec] Explanation An error occurred with the CompactFlash device. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %BFD_HA-2-RESOURCE: [chars] Explanation An error occurred in a system resource. Recommended Action Copy the message exactly as it appears on the console or in the system log.



90

System Messages BFD_HA Messages


Error Message %BFD_HA-2-RF: [chars][dec] Explanation An error occurred in the RF system. Recommended Action Copy the message exactly as it appears on the console or in the system log.


BFD_HA-3 Error Message %BFD_HA-3-DELSESS: [chars][dec] Explanation An error occurred while deleting a session. Recommended Action Copy the message exactly as it appears on the console or in the system log.



91

System Messages BFD_ISSU Messages

BFD_ISSU Messages This section contains Bidirectional Forwarding Detection (BFD) in-service software upgrade (ISSU) messages.

BFD_ISSU-2 Error Message %BFD_ISSU-2-GET_BUFFER: BFD ISSU client failed to get buffer for message. Error: [dec] ([chars]) Explanation The BFD ISSU client was unable to get buffer space for building a negotiation message.

A negotiation message cannot be sent to the standby device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show checkpoint client commands and your pertinent troubleshooting logs.

Error Message %BFD_ISSU-2-INIT: BFD ISSU client initialization failed to [chars]. Error: [dec] ([chars]) Explanation The BFD ISSU client could not be initialized. This initialization failure must be addressed before an in-service software upgrade or downgrade can be performed successfully. Otherwise, a software upgrade or downgrade will result in downtime. Recommended Action Copy the message exactly as it appears on the console or in the system log.



92


Error Message %BFD_ISSU-2-SEND_NEGO_FAILED: BFD ISSU client failed to send negotiation message. Error: [dec] ([chars]) Explanation The BFD ISSU client was unable to send a session negotiation message to the peer device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %BFD_ISSU-2-SESSION_NEGO: BFD ISSU client encountered unexpected client nego_done. Error: [dec] ([chars]) Explanation An ISSU-compliant client transitions through a series of internal states. The BFD ISSU client encountered a client negotiation done state that was unexpected. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %BFD_ISSU-2-SESSION_REGISTRY: BFD ISSU client failed to register session information. Error: [dec] ([chars]) Explanation The BFD ISSU client was unable to register session information. If a problem occurs

with the ISSU session registration, the standby device cannot be brought up properly. Recommended Action Copy the message exactly as it appears on the console or in the system log.



93



BFD_ISSU-3 Error Message %BFD_ISSU-3-INVALID_SESSION: BFD ISSU client does not have a valid registered session. Explanation The BFD ISSU client does not have a valid registered session. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs.

Error Message %BFD_ISSU-3-MSG_SIZE: BFD ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] ([chars]) Explanation The BFD ISSU client was unable to calculate the MTU for the specified message. The

BFD ISSU client is not able to send the message to the standby device. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs.


94


Error Message %BFD_ISSU-3-SESSION_UNREGISTRY: BFD ISSU client failed to unregister session information. Error: [dec] ([chars]) Explanation The BFD ISSU client was unable to unregister session information. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %BFD_ISSU-3-TRANSFORM_FAIL: bfd ISSU client [chars] transform failed for message [dec]’. Error: [dec] ([chars]) Explanation The BFD ISSU client could not transform the specified message type. If the transmit

transformation failed, the checkpoint message was not sent to the standby device. If the receive transformation failed, the checkpoint message was not applied on the standby device. In either case, the BFD state between the active device and the standby device is not identical. Recommended Action Copy the message exactly as it appears on the console or in the system log.



95

System Messages BFD_SCALE Messages

BFD_SCALE Messages This section contains Bidirectional Forwarding Detection (BFD) credit-based workload messages.

BFD_SCALE-6 Error Message %BFD_SCALE-6-INSUFFICIENT_RESOURCES: Configuration not changed, exceeds maximum resource limit. Explanation The configuration could not be changed due to a resource limitation. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %BFD_SCALE-6-RESOURCES_EXHAUSTED: BFD adjacency can not be created due to resource limitation. Explanation A BFD adjacency cannot be created due to a resource limitation. Recommended Action Copy the message exactly as it appears on the console or in the system log.



96

System Messages BFD_TEST Messages

BFD_TEST Messages This section contains Bidirectional Forwarding Detection (BFD) test messages.

BFD_TEST-3 Error Message %BFD_TEST-3-BAD_ADDR_TYPE: Invalid address type [dec] Explanation The BFD test process detected an invalid address type. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %BFD_TEST-3-BAD_TYPE: Invalid session type [dec] Explanation The BFD test process detected an invalid session type. Explanation Copy the message exactly as it appears on the console or in the system log. Research

and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %BFD_TEST-3-WAVL_INIT_FAIL: Failed initializing wavl tree. Explanation The BFD test process was unable to initialize a wrapped AVL (WAVL) tree. Recommended Action Copy the message exactly as it appears on the console or in the system log.



97



Error Message %BFD_TEST-3-WAVL_INSERT_FAIL_IPV4: Failed inserting neighbor address %30i to wavl tree thread [dec] Explanation The BFD test process was unable to insert an IPv4 node in a wrapped AVL (WAVL) tree. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %BFD_TEST-3-WAVL_INSERT_FAIL_IPV6: Failed inserting neighbor address %30P to wavl tree thread [dec] Explanation The BFD test process was unable to insert an IPv6 node in a wrapped AVL (WAVL) tree. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %BFD_TEST-3-WAVL_TREE: Failed to malloc space for wavl tree. Explanation The BFD test process was unable to allocate memory for a wrapped AVL (WAVL) tree. Recommended Action Copy the message exactly as it appears on the console or in the system log.



98


Error Message %BFD_TEST-3-WAVL_WALK_FAIL: wavl_walk failed while walking wavl tree thread [dec] interface [dec] Explanation A thread failed while walking the wrapped AVL (WAVL) tree. Recommended Action Copy the message exactly as it appears on the console or in the system log.


BFD_TEST-7 Error Message %BFD_TEST-7-FSM_STATE: Session [[IP_address],[IP_address],[chars],[int]], event [chars], state [chars] -> [chars] Explanation State information is shown in the message. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %BFD_TEST-7-RECV_START: First packet has come in. Explanation The first packet has been received. Recommended Action This is an informational message only. No action is required.


99

System Messages BGP Messages

BGP Messages This section contains Border Gateway Protocol (BGP) messages.

BGP-2 Error Message %BGP-2-INSUFMEM: Insufficient memory for [chars] entry Explanation The requested operation could not be accomplished because of a low memory condition. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

BGP-3 Error Message %BGP-3-ADDROUTE: Unable to add route for [chars] to radix trie Explanation An addition to the radix trie could not be completed because of an error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %BGP-3-BADMASK: Attempt to install route for %i without valid mask in [chars] Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



100


Error Message %BGP-3-BADROUTEMAP: Bad parameters in the route-map [chars] applied for [chars] Explanation The route map contains incorrect entries. Recommended Action Correct the route map.

Error Message %BGP-3-BGP_INCONSISTENT: [chars] Inconsistent [chars] Explanation An error was detected in a data structure. This is an internal software error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %BGP-3-DELPATH: Attempted to delete path from an empty net for [chars] Explanation A BGP path could not be deleted. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %BGP-3-DELROUTE: Unable to remove route for [chars] from radix trie Explanation The system was unable to delete a route from the radix trie. Recommended Action Copy the message exactly as it appears on the console or in the system log.



101


Error Message %BGP-3-INSUFCHUNKS: Insufficient chunk pools for [chars], requested size [dec] Explanation The static chunk pools size is too small. Recommended Action Collect the chunk and BGP summary. Copy the message exactly as it appears


Error Message %BGP-3-INVALID_MPLS: Invalid MPLS label ([dec]) received in update for prefix [chars] from [chars] Explanation An invalid MPLS label was found in a received BGP message. This indicates that there

is some problem on the remote router. Recommended Action Check the configuration of the remote router.

Error Message %BGP-3-MARTIAN_IP: [chars] Martian prefix [chars] in [chars] Explanation A Martian prefix was found in the BGP message. This indicates that there is some

problem on the remote router. Recommended Action Check the configuration of the remote router.

Error Message %BGP-3-MAXPFXEXCEED: No. of prefix received from [chars][chars][chars] (afi [dec]): [dec] exceed limit [dec] Explanation The number of prefixes received from a neighhor exceeeds the configured limit. The

message displays the session number or VRF identifier, if applicable. Recommended Action Check the number of prefixes received from the neighbor and determine

whether the limit should be increased.

Error Message %BGP-3-NOBITFIELD: Could not allocate bitfield. Cannot open session to [chars] Explanation The allocation of a neighbor index for this neighbor has failed because of a low memory



102


Error Message %BGP-3-NOTIFICATION: [chars] neighbor [chars] [dec]/[dec] ([chars]) [dec] bytes [chars] Explanation An error condition has been detected in the BGP session. A notification message is

being sent or received and the session will be reset. This message appears only if the log-neighbor-changes command is configured for the BGP process. Recommended Action This message represents an error in the session and its origin should be investigated. If the error is reported periodically, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %BGP-3-ORF_PFXLIST: Received misformatted prefixlist ORF from [chars] Explanation The received prefix list outbound route filter (ORF) is misformatted. Recommended Action Check the prefix list ORF implementation on the neighboring router.

Error Message %BGP-3-PER_VRF_AGGR: pervrfaggr label: [chars] Explanation The TFIB asks for a label for a prefix in the VRF routing table. The per-VRF-aggregate

label will be assigned to the connected type or BGP aggregate prefix when BGP runs a best-path calculation. This message might appear when a prefix changes to a connected type or BGP aggregate type. Recommended Action No action is required. If this message recurs, copy the message exactly as it


Error Message %BGP-3-RADIXINIT: Radix trie initialization failed Explanation Initialization of the radix tree could not be accomplished because of a low memory



103


BGP-4 Error Message %BGP-4-AFIMPORT: [chars] prefixes imported to [chars] vrf reached the limit [dec] Explanation The number of prefixes imported from an address family to a VRF has reached the

configured limit Recommended Action Check the number of imported prefixes from the address family and determine whether the limit should be increased or if the ip vrf import route-map command is configured correctly.

Error Message %BGP-4-ATTRNULL: A NULL attribute has been assigned to a path Explanation The path was incorrectly assigned a value of NULL instead of a valid attribute. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %BGP-4-BFD_NOT_ONEHOP: BFD is supported for single hop neighbors. [chars] is not single hop neighbor Explanation Bidirectional forwarding detection (BFD) is not enabled because the configured

neighbor is not a single hop. BFD is supported only for single hop neighbors. Recommended Action Unconfigure BFD from BGP.

Error Message %BGP-4-MAXDYNNBR: BGP:DN: Cannot create new neighbor [chars], for range [chars]: maximum number of [dec] dynamic neighbors limit reached Explanation The number of dynamically created subnet range neighbors has reached a warning limit. Recommended Action Check the number of listen range limit configured for dynamic subnet

neighbors and determine whether the limit should be increased.


104


Error Message %BGP-4-MAXPFX: No. of prefix received from [chars][chars][chars] (afi [dec]) reaches [dec], max [dec] Explanation The number of prefixes received from a neighhor has reached a warning limit. The

message displays the session number or VRF identifier, if applicable. Recommended Action Check the number of prefixes received from the neighbor and determine

whether the limit should be increased.

Error Message %BGP-4-MAX_EXTCOMM_EXCEED: Exceeded limit of [dec] extended communities per advertised prefix Explanation An attempt was made to advertise a prefix with an extended community attribute

containing more extended communities than the allowed limit. Recommended Action Reduce the configured number of route targets or other extended communities that will be added to prefix advertisements.

Error Message %BGP-4-NBRTRACK: Route Tracking failed on memory. Neighbor tracking for route-fall-over will stop Explanation The route tracking system failed to allocate memory. Neighbor route fallover will stop

tracking neighbor routes in order to free some memory. Recommended Action If the system is stable, then reconfigure neighbor route fallover. If this message reappears, neighbor route fallover has been unconfigured.

Error Message %BGP-3-NEGCOUNTER: Prefix-accepted counter negative for peer [chars], prefix [chars] Explanation The counter value for accepted prefixes is less than zero, which is an illegal value. This

indicates an internal software error. Recommended Action Reset the session.

Error Message %BGP-4-NORTRID: BGP could not pick a router-id. Please configure manually. Explanation The BGP router ID has not been manually configured and BGP is unable to allocate a

router ID from the IPv4 address of one of its interfaces. Recommended Action Make sure that at least one interface is up and has a valid IPv4 address, or

configure the router ID manually.


105


Error Message %BGP-4-RIDSYNC: BGP routes are redistributed to OSPF. For synchronization to work, you must manually configure the BGP router-id to be the same as the OSPF router-id. Explanation For synchronization to work, the BGP router ID must be the same as the OSPF router

ID at all times that the router is up. Recommended Action If synchronization is turned on between one instance of OSPF and BGP, make sure to manually configure a BGP router ID that is identical to the router ID of the particular OSPF instance.

Error Message %BGP-4-VPNV4NH_MASK: Nexthop %i may not be reachable from neigbor [chars] - not /32 mask Explanation We are sending to an IBGP neighbor a VPNv4 route whose next hop address is our

loopback, which does not have a 32 bit mask. In addition, we are using OSPF on this loopback, and the OSPF network type of this interface is loopback. OSPF advertises this address as a host route (with mask /32) regardless of what mask is configured. This conflicts with the Tag Distribution Protocol (TDP), which uses configured masks, so our TDP neighbors may not receive a tag for this route. As a result, connectivity could be lost between sites that belong to the same VPN. Recommended Action Configure the loopback used as the next hop with a 32 bit IP host mask (/32),

or configure the ip ospf network point-to-point command on this loopback.

Error Message %BGP-4-VPN_NH_IF: Nexthop [chars] may not be reachable from neigbor [chars] - not a loopback Explanation We are sending to an IBGP neighbor a VPN route whose the next hop is one of our

directly-connected physical interfaces. The label for the next hop address may be removed in the MPLS cloud one hop soon. Since the P routers do not have VPN information, they do not know where to forward packets with the BGP label. As a result, connectivity could be lost between VPN sites. Recommended Action Use loopback interfaces as the next hops for VPN IBGP neighbors.

BGP-5 Error Message %BGP-5-ADJCHANGE: neighbor [chars][chars][chars][chars] [chars] Explanation A BGP neighbor has either come up or gone down, as indicated. This message appears

only if the log-neighbor-changes command is configured for the BGP process. Recommended Action This informational message normally appears as routers and BGP neighbors go

up or down. However, unexpected neighbor loss might indicate high error rates or high packet loss in the network and should be investigated.


106


Error Message %BGP-5-DAMPENING_DECAY_TIME: Decay time from maximum penalty to suppress penalty is [dec] secs. Maximum penalty: [dec], suppress penalty: [dec] Explanation The configured dampening parameters may not be feasible. The time window between

maximum penalty and suppress penalty may be low. Recommended Action If the decay time from maximum penalty to suppress penalty is too low,

increase the half-life time or the maximum penalty values.

Error Message %BGP-5-DAMPENING_HIGH_MAX_PENALTY: Maximum penalty ([dec]) is more than allowed maximum ([dec]). Dampening is OFF Explanation The configured dampening parameters may not be feasible. The maximum penalty is

more than the allowed maximum. As a result, dampening will be off. Recommended Action Depending on the value of the maximum penalty, adjust the maximum suppress

time. Because the maximum penalty is more than the allowed maximum, reduce maximum suppress time. The maximum penalty should be greater than the suppress penalty but less than the maximum allowable penalty.

Error Message %BGP-5-DAMPENING_LOW_MAX_PENALTY: Maximum penalty ([dec]) is less than suppress penalty ([dec]), Dampening is OFF Explanation The configured dampening parameters may not be feasible. The maximum penalty is

less than the configured suppress penalty. As a result, dampening will be off. Recommended Action Depending on the value of the maximum penalty, adjust the maximum suppress

time. Because the maximum penalty is less than the suppress penalty, increase the maximum suppress time. The maximum penalty should be greater than the suppress penalty but less than the maximum allowable penalty.

Error Message %BGP-5-VERSION_WRAP: bgp version wrapped of [chars] Explanation The BGP table version has reached its maximum value and has wrapped around. The

message describes this event. Recommended Action This message is informational. However, frequent occurrences of such an event

might indicate high error rates or high packet loss in the network and should be investigated.

BGP-6 Error Message %BGP-6-ASPATH: [chars] AS path [chars] received from [chars]: [chars] Explanation The remote BGP peer sent an update with an invalid autonomous system (AS) path. Recommended Action Copy the message exactly as it appears on the console or in the system log.



107

System Messages BGP_MPLS Messages


Error Message %BGP-6-BIGCHUNK: Big chunk pool request ([dec]) for [chars]. Replenishing with malloc Explanation This is an informational message describing an internal software operation. If the static chunk pool size can not service the request, it will be serviced with a memory allocation (malloc) process. Recommended Action No action is required.

Error Message %BGP-6-NEXTHOP: Invalid next hop (%i) received from [chars]: [chars] Explanation The remote BGP peer sent a route with an illegal next hop. The route was ignored. Recommended Action No action is required.

BGP_MPLS Messages This section contains BGP MPLS common messages.

BGP_MPLS-3 Error Message %BGP_MPLS-3-GEN_ERROR: [chars] Explanation This message describes a general runtime error related to BGP MPLS. Recommended Action Copy the message exactly as it appears on the console or in the system log.



108


Error Message %BGP_MPLS-3-IPRMCONNECT: [chars] Explanation BGP VPNv4 failed to register to the IP rewrite manager (IPRM) component. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %BGP_MPLS-3-LABELALLOC: [chars] Explanation An MPLS label could not be allocated for a prefix. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %BGP_MPLS-3-LSDCONNECT: [chars] Explanation BGP VPNv4 failed to register to the MPLS forwarding component. Recommended Action Copy the message exactly as it appears on the console or in the system log.



109


Error Message %BGP_MPLS-3-NBR_ROUTE: [chars] Explanation An error occurred in manipulating the BGP neighbor route needed for MPLS

operations. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %BGP_MPLS-3-PERVRF: pervrfaggr label: [chars] Explanation An error occurred related to the per-VRF label feature. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %BGP_MPLS-3-PER_VRF_AGGR: pervrfaggr label: [chars] Explanation An error occurred related to the per-VRF aggregate label feature. Recommended Action Copy the message exactly as it appears on the console or in the system log.



110


Error Message %BGP_MPLS-3-SIZEMISMATCH: Label table size ([dec]) mismatch, checkpt key creation failed Explanation A BGP MPLS label table size mismatch was detected. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %BGP_MPLS-3-VPN_REWRITE: [chars] Explanation An error occurred in installing, updating, or removing a VPN rewrite entry in the MPLS

forwarding tabl.e Recommended Action Copy the message exactly as it appears on the console or in the system log.


BGP_MPLS-4 Error Message %BGP_MPLS-4-LABELALLOC: Label allocation failure Explanation A resource limitation was encountered while allocating a local label on the router. Recommended Action Copy the message exactly as it appears on the console or in the system log.



111

System Messages BSR Messages

BGP_MPLS-7 Error Message %BGP_MPLS-7-IASLABELALLOC: Failed to create rewrite for prefix [chars], reason: [chars] Explanation A BGP MPLS VPN rewrite creation failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %BGP_MPLS-7-IPv4LABELALLOC: Failed to allocate label for IPv4 prefix %i/[dec] Explanation A BGP MPLS IPv4 label allocation failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


BSR Messages This section contains Bootstrap Router (BSR) messages.

BSR-5 Error Message %BSR-5-CBSR_REMOVED: Candidate-BSR on interface [chars] has been removed Explanation The interface card has been removed. Recommended Action No action is required.


112

System Messages BUNDLES Messages

Error Message removed

%BSR-5-CRP_REMOVED: Candidate-RP on interface [chars] has been

Explanation The interface card has been removed. Recommended Action No action is required.

BUNDLES Messages This section contains Bundles messages.

BUNDLES-3 Error Message %BUNDLES-3-ALLOCATION: Bundle allocation error: [chars] Explanation An internal software error occurred. This error is probably caused by a low-memory

condition. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %BUNDLES-3-PLATFORMSPACE: Platform attempted to access unreserved space Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



113

System Messages C2950_MONITOR Messages

Error Message %BUNDLES-3-TYPENOTISSUAWARE: Bundle type [chars] must be ISSU aware to send to slot(s) [chars] Explanation The bundle type is not In Service Software Upgrade (ISSU) aware so cannot be

distributed to a slot with which ISSU negotiation has occurred. This indicates a design problem that requires code changes to fix. Recommended Action Copy the message exactly as it appears on the console or in the system log.


C2950_MONITOR Messages This section contains Catalyst 2950 series switch monitor messages.

C2950_MONITOR-3 Error Message %C2950_MONITOR-3-C2950MONITOR_UNKNOWN_PARAM: Unknown trap type:[dec] received in emt_call function. Explanation An unknown trap type occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



114

System Messages C4K_IOSSYS Messages

C4K_IOSSYS Messages This section contains Catalyst 4000 series switch Cisco IOS system messages.

C4K_IOSSYS-7 Error Message %C4K_IOSSYS-7-INVALIDVALUE: [chars] Type [dec] not handled, returning a default of 0 Explanation This message is for debugging purposes. When you see this message, report it to your

technical support representative. Recommended Action Copy the message exactly as it appears on the console or in the system log.


C4K_REDUNDANCY Messages This section contains Catalyst 4000 series switch redundancy messages.

C4K_REDUNCANCY-2 Error Message

%C4K_REDUNDANCY-2-IOS_VERSION_CHECK_FAIL: [chars]

Explanation For the redundancy utility to operate properly, the system must be configured with

symmetrical hardware and software. A mismatch in versions of Cisco IOS software between the active and standby systems has been detected. Redundancy operations cannot be guaranteed. Recommended Action Configure the system so that the active and standby supervisor engines are

using the same versions of Cisco IOS software.

Error Message

%C4K_REDUNDANCY-2-NON_SYMMETRICAL_REDUNDANT_SYSTEM: [chars]

Explanation For the redundancy utility to operate properly, the system must be configured with

symmetrical hardware and software. A mismatch in hardware has been detected between the active and standby systems. Redundancy operations cannot be guaranteed. Recommended Action Configure the hardware so that the active and standby supervisor engines are

identical.


115

System Messages C6KENV Messages

Error Message detected

%C4K_REDUNDANCY-2-POSTFAIL: POST failure on [chars] supervisor

Explanation An active supervisor engine failed during a POST operation. The standby supervisor

engine will reset the current active supervisor engine, and the standby supervisor engine will attempt to become the active supervisor engine. Recommended Action Perform offline diagnostic operations on the failed supervisor engine to isolate

the failure.

C6KENV Messages This section contains Catalyst 6500 series switch and Cisco 7600 series router environmental (C6KENV) messages.

C6KENV-2 Error Message %C6KENV-2-BADFLOWCTRL: Module [dec] not at an appropriate hardware revision level to support DFC. Power denied Explanation The fabric-capable module in the specified slot is not at an appropriate hardware

revision level and cannot support a DFC. If a DFC is present, the module will not be activated and remains powered down. Recommended Action Remove the DFC to enable the module to operate at its current hardware

revision level. To enable DFC operation, ensure that the module is at an appropriate hardware revision level.

Error Message %C6KENV-2-BADFLOWCTRL_WARN: WARNING: Module [dec] not at an appropriate hardware revision level to support DFC3 Explanation The fabric-capable module in the specified slot is not at an appropriate hardware

revision level to support a DFC3 or higher. Recommended Action When you upgrade the DFC daughter card, also upgrade the module to an

appropriate hardware revision level.

Error Message %C6KENV-2-BADPINN1: Module [dec] not at an appropriate hardware revision level to coexist with PFC3 system. Power denied Explanation The module specified in the error message has a revision of 2.x or below. Modules with

this revision will experience problems when they are used with a supervisor engine with a PFC3 installed and should not be used. Recommended Action Upgrade the module to an appropriate hardware revision level.


116


Error Message %C6KENV-2-BADTRANSCEIVER: Module [dec] will be power disabled because an inappropriate transceiver is inserted at [chars]. Explanation An incompatible transceiver is inserted at the interface specified in the error message.

This transceiver should not be used in this system. Recommended Action Remove the specified transceiver and restore power to the module. If this

transceiver was purchased from Cisco, contact your Cisco technical support representative to get the transceiver replaced.

Error Message %C6KENV-2-C2PLUSWITHNODB: The constellation 2 plus module in slot [dec] has no forwarding daughter board. Power denied Explanation The module in the slot specified has no forwarding daughter card and is expected to

have either a distributed, accelerated, or centralized forwarding card. This module will not be activated and will remain powered down. Recommended Action Enter the show module command to view error message details.

Error Message %C6KENV-2-DFCMISMATCH: Module [dec] DFC incompatible with Supervisor DFC. Power denied Explanation The DFC in the specified module is different from the DFC in the supervisor engine.

The module will not be activated and remains powered down. Recommended Action Enter the show module command to view the difference between the DFC in

the module and the DFC in the supervisor engine.

Error Message %C6KENV-2-DFCMISMATCHMINOR: Module [dec] DFC installed is incompatible with system operating mode. Power denied. To enable Module [dec] DFC, the system must be reset. WARNING: Any system reset will change the system operating mode which can result in degradation of system performance. To eliminate this from occurring, remove Module [dec] DFC or replace with a system compatible DFC. Explanation The DFC in the specified slot does not have the same software operating mode as the rest of the system. The DFC will remain powered down and cannot be activated. Recommended Action Enter the show module and show platform earl-mode commands to view the difference between the DFC in the specified slot and the operating mode of the rest of the system.

Error Message %C6KENV-2-FANUPGREQ: Module [dec] not supported without fan upgrade Explanation The supervisor engine and the DFC in the specified slot require a fan tray upgrade. A

system shutdown is scheduled. Recommended Action Upgrade the system fan tray.


117


Error Message %C6KENV-2-SHUTDOWN_NOT_SCHEDULED: Major sensor alarm for [chars] is ignored, [chars] will not be shutdown. Explanation The system detected that the specified module should be shut down because it exceeded

major sensor thresholds. However, the command that shuts down the module in the event of a major sensor alarm has been overridden, so the specified module will not be shut down. The command used to override the shutdown is no environment-monitor shutdown. Recommended Action Remove the configuration that bypasses the module shutdown due to sensor

thresholds being exceeded. Shut down the module after removing the configuration.

Error Message %C6KENV-2-SHUTDOWN_SCHEDULED: shutdown for [chars] scheduled in [dec] seconds Explanation A major alarm condition will be corrected by shutting down the affected component.

[chars] is the component, and [dec] is the time in seconds before shutdown. Recommended Action Replace the component as soon as possible.

C6KENV-4 Error Message %C6KENV-4-ALARMCLR: [chars] alarm cleared Explanation The specified alarm condition has been cleared. The shutdown has been cancelled. Recommended Action No action is required.

Error Message %C6KENV-4-FANCOUNTFAILED: Required number of fan trays is not present Explanation The system is missing the number of required fan trays to operate properly. Although

this is a minor alarm, system components could overheat and be shut down. Recommended Action Insert the required fan tray as soon as possible.

Error Message %C6KENV-4-FANCOUNTOK: Required number of fan trays is present Explanation The number of required fan trays has been restored. Recommended Action No action is required.

Error Message %C6KENV-4-FANHIOUTPUT: Version [dec] high-output fan-tray is in effect Explanation The system has detected that the fan tray is a high-output (version 2) fan tray. The

system has updated the cooling capacity for the fan tray. Recommended Action No action is required.


118


Error Message %C6KENV-4-FANLOOUTPUT: Version [dec] low-output fan-tray is in effect Explanation The system has detected that the fan tray is a low-output (version 1) fan tray. The system

has updated the cooling capacity for the fan tray. Recommended Action No action is required.

Error Message %C6KENV-4-FANPSINCOMPAT: Fan tray and power supply [dec] are incompatible Explanation An upgrade of the power supply is required to sufficiently operate this fan tray.

Although this is a minor alarm, overcurrent protection on the power supply could start without further warning. Recommended Action Upgrade the power supply.

Error Message %C6KENV-4-FANTRAYFAILED: fan tray failed Explanation One or more fans in the system fan tray have failed. Although this is a minor alarm,

system components could overheat and be shut down. Recommended Action Reseat the fan tray. If the error recurs, replace the system fan tray at the earliest

opportunity.

Error Message %C6KENV-4-FANVERCHK: Power-supply [dec] inserted is only compatible with Version [dec] fan-tray. Please make sure fan is low-output fan-tray Explanation The system has detected that the fan tray is a low-output (version 1) fan tray. If the fan

tray is a low-output tray, no action is required. If the fan tray is actually a high-output (version 2) fan tray, the specified power supply is not able to support the high-output fan tray. Recommended Action If the fan tray is a high-output (version 2) fan tray, enter the hw-module fan-tray version 2 command to update the system with the upgrade information. Replace the 1000 W or 1300 W power supply, as these two power supplies are not compatible in this chassis with the version 2 fan tray.

Error Message %C6KENV-4-INSUFFCOOL: Module [dec] cannot be adequately cooled Explanation The fan tray cannot adequately cool the specified module. Although this is a minor

alarm, system components could overheat and be shut down. Recommended Action Upgrade the system fan tray.


119


Error Message %C6KENV-4-MINORTEMPOKALARM: [chars] all temperature sensor have failed. If the module temperature sensor does not recover by itself, please power cycle the module when it is feasible Explanation All module temperature sensors have failed. Recommended Action If the module temperature sensors do not recover, power cycle the module

when possible.

Error Message %C6KENV-4-MINORTEMPOKALARMRECOVER: [chars]. It has returned to normal operating status. Explanation All module temperature sensors have returned to normal operating status. Recommended Action No action is required.

Error Message %C6KENV-4-MINORTEMPSUPOKALARM: All temperature sensors of Supervisor in slot [dec] have failed. If the temperature sensor does not recover by itself, please power cycle the chassis when it is feasible Explanation All temperature sensors have failed in the supervisor engine. Recommended Action If the temperature sensors do not recover, power cycle the chassis when

possible.

Error Message %C6KENV-4-MINORTEMPSUPOKALARMRECOVER: Supervisor in slot [dec] has returned to normal operating status. Explanation The supervisor engine temperature sensors have returned to normal operating status. Recommended Action No action is required.

Error Message %C6KENV-4-MINORVTTOKALARM: All the backplane vtt temperature sensor have failed. If the backplane vtt temperature sensor does not recover by itself, please power cycle the chasis when it is feasible Explanation All backplane VTT temperature sensors have failed. Recommended Action If the backplane VTT temperature sensors do not recover, power cycle the

chassis when possible.

Error Message %C6KENV-4-MINORVTTOKALARMRECOVER: Backplane VTT has returned to normal operating status. Explanation The backplane VTT has returned to normal operating status. Recommended Action No action is required.


120

System Messages C6KERRDETECT Messages

C6KENV-SP Error Message %C6KENV-SP-4-FANTRAYFAILED: Fan tray failed. Explanation One or more fans in the system fan tray have failed. Although this is a minor alarm,

system components can overheat and be shut down. Recommended Action Replace the system fan tray as soon as possible.

Error Message %C6KENV-SP-4-MINORTEMPALARM: [chars] has exceeded normal operating temperature range. Explanation Message indicates that the normal operating temperature range has been exceeded. This

message can indicate a trend for the module or component, and also a trend for other components in the system. Recommended Action Inspect the indicated module or component closely to determine why it

operates out of normal operating temperature range and determine if it eventually exceeds the allowed operating temperature range. Verify the air flow to the device is not blocked and that the fan is operational. Enter the show environment temperature command to see temperature readings and the show environment alarm threshold command to see the alarm thresholds.

C6KERRDETECT Messages This section contains Catalyst 6500 series switch and Cisco 7600 series router bus error detection (C6KERRDETECT) messages.

C6KERRDETECT-2 Error Message %C6KERRDETECT-2-SWBUSSTALL: The switching bus is experiencing stall for [dec] seconds Explanation During an Online Insertion or Removal (OIR), some switching modules will assert a stall signal on the backplane to pause data transmission for the duration of the OIR. When the OIR is performed smoothly and quickly, traffic is usually interrupted for less than one second. If the OIR is performed slowly or is paused, the longer traffic interruption will result in this error message being reported. Recommended Action Perform the OIR smoothly and quickly. Do not pause with the module partially

inserted.


121

System Messages C6K_IVRF Messages

C6K_IVRF Messages This section contains Catalyst 6500 series switch internal VRF (IVRF) messages.

C6K_IVRF-3 Error Message %C6K_IVRF-3-C6K_IVRF_ERROR: [chars] Explanation A VRF infrastructure failure occurred involving the platform’s internal VRFs (IVRFs). Recommended Action Copy the message exactly as it appears on the console or in the system log.


C6K_MPLS_COMMON Messages This section contains Catalyst 6500 series switch and Cisco 7600 series router LAN and WAN Multiprotocol Label Switching (C6K_MPLS_COMMON) messages.

C6K_MPLS_COMMON-3 Error Message %C6K_MPLS_COMMON-3-L2_CONFIG_NOT_RECOMMENDED: xconnect is configured on interface vlans and WAN interfaces are facing the MPLS Core. Do not configure LAN interfaces facing the MPLS Core. Explanation An attempt was made to configure a LAN interface to face the MPLS core. The current

network configuration has cross-connection services configured on interface VLANs and has WAN interfaces facing the MPLS core. Recommended Action Do not configure MPLS on LAN interfaces facing the MPLS core if the

network has cross-connect services configured on an interface VLAN and WAN interfaces that face the MPLS core.


122

System Messages C6K_MPLS_LC Messages

Error Message %C6K_MPLS_COMMON-3-L3_CONFIG_NOT_RECOMMENDED: LAN interfaces are facing the MPLS Core. Do not configure xconnect on interface vlans. Explanation An attempt was made to configure a cross-connection service on an interface VLAN.

The current network configuration has MPLS configured on a LAN interface that is facing the MPLS core. Recommended Action Do not configure cross-connection services on an interface VLAN if the

network has MPLS configured on a LAN interface.

Error Message %C6K_MPLS_COMMON-3-OSM_BB1_CONFIG_UNSUPPORTED: The maximum label range configured for this system exceeds the [int] limit supported by the module in slot [int]. For proper MPLS functionality on any of the interfaces on this module the maximum label range should be set to [int]. Explanation The OSM cannot support the MPLS label range configured for this system. Recommended Action Change the maximum MPLS label range by using the mpls label range

command.

Error Message %C6K_MPLS_COMMON-3-VPLS_CONFIG_EXCEEDED: The number of EoMPLS/VPLS VCs exceeded the maximum supported on [IP_address]/[int]. Explanation The number of destination routers or the global number of virtual circuits exceeded the

maximum limit supported by the device. Recommended Action Refer to network configuration guidelines for the maximum limits.

C6K_MPLS_LC Messages This section contains Catalyst 6500 series switch and Cisco 7600 series router Multiprotocol Label Switching (MPLS) switch processor or module (C6K_MPLS_LC) messages.

C6K_MPLS_LC-3 Error Message %C6K_MPLS_LC-3-INFINITE_OCE: In label: [dec] Invalid OCE previous oce type: [dec] prev ptr:Unrecognized format ‘ %p’, next oce type: [dec] next oce ptr:Unrecognized format ‘ %p’ Explanation The Output Chain Element(OCE) specified in the system message is invalid because it

has exceeded the maximum depth. One known cause is invalid static route configuration. Traffic for this path will be dropped. Recommended Action Copy the error message exactly as it appears on the console or in the system

log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance,


123


open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message %C6K_MPLS_LC-3-INVALID_TABLEID: Invalid tableid([dec]) for label([dec]) Explanation The system has received an invalid table identifier number. The table identifier should

be in the range from 0 to 4095. This is an internal software error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %C6K_MPLS_LC-3-INVALID_TE_IF_NUMBER: An invalid Traffic Engineering interface number [[int]] was passed to the statistics update routine Explanation The traffic engineering interface number sent to the statistics update routine is invalid. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %C6K_MPLS_LC-3-INVALID_VRFID: Invalid vrf_id(%u) for label([dec]) Explanation An invalid VRF identifier (ID) was received. The VRF ID should be in the range of 0 to

4095. This is an internal software error. Recommended Action Copy the message exactly as it appears on the console or in the system log.



124



Error Message %C6K_MPLS_LC-3-LABEL_STACK_SIZE: Label [[dec]] is not added to label stack. Current label stack is [[dec] [dec] [dec] [dec] [dec]] Explanation The label specified in the system message was not added to the label stack because the

stack already contains the maximum number of allowed labels. The system cannot forward data correctly. This condition is an internal software error. Recommended Action Enter the show mpls forwarding-table labels command, and gather label

information about the label that was not added to the stack and about the labels that are in the stack already. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %C6K_MPLS_LC-3-MALLOCFAIL: failed to create [chars] Explanation The system failed to allocate memory for an MPLS entry for the incoming label. Some

MPLS packets might be forwarded by the software. Recommended Action Reduce other system activity to ease memory demands. If necessary, increase

system memory. When more memory is available, wait for a few minutes and enter the clear ip route command. If sufficient memory has not been made available, this message will display again. If this problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %C6K_MPLS_LC-3-OCE_ERROR: Invalid OCE [[chars]] [hex] Explanation The Output Chain Element (OCE) specified in the system message is invalid because it cannot be processed. This issue can cause problems in data forwarding. This condition is an internal software error. Recommended Action Copy the message exactly as it appears on the console or in the system log.



125


information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %C6K_MPLS_LC-3-REWRITEFAIL: null adj for incoming label [dec] Explanation The specified incoming label has a NULL adjacency entry. The hardware adjacency

entry might not be programmed because the incoming label has the NULL adjacency entry. This condition is an internal software error. Recommended Action Enter the show mpls forwarding-table labels command. Copy the message


Error Message %C6K_MPLS_LC-3-SIX_PE_REW_LBL_ENTRY_MISMATCH: The label entry([hex]) in the 6PE rewrite table for incoming label [dec] does not match the passed in label entry([hex]) Explanation The label entry in the IPv6 on Provider Edge router (6PE) rewrite table does not match the label entry for an incoming label. This is an internal software error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %C6K_MPLS_LC-3-TCAMFAIL: TCAM validation check failed for label [dec] Explanation The validation check on an inserted TCAM entry failed for the specified label. Recommended Action Copy the message exactly as it appears on the console or in the system log.



126



C6K_MPLS_LC-5 Error Message %C6K_MPLS_LC-5-TCAM_EXCEPTION: TCAM exception occured for MPLS, traffic will be software switched Explanation The switch failed to insert an MPLS entry into the hardware FIB TCAM because the

total number of software forwarding entries exceeds the hardware FIB TCAM limit. As a result, some MPLS packets might be forwarded by the software. Recommended Action Reduce the number of routes in the system to free up TCAM space. When

enough free TCAM space is available, the software starts the TCAM recovery mechanism automatically, which will reinstall into TCAM those MPLS label entries that failed before. If the number of labels has been tuned down with the mls cef maximum-routes configuration command, increase the number of labels, save the configuration, and reload the router, bacause this configuration will only be effective on reloading the router. The maximum number of routes currently configured can be observed with the show mls cef maximum-routes command, and the current number of routes in the system can be observed with the show mls cef summary command.

Error Message %C6K_MPLS_LC-5-TCAMEXPRECOVER: TCAM exception recovered for MPLS, traffic will be hardware switched Explanation At some earlier point in time some of the MPLS forwarding table could not fit into the

hardware TCAM. The complete MPLS forwarding table is now in hardware, and forwarding for the incoming MPLS packets will be done in hardware. Recommended Action No action is required.


127

System Messages C6K_MPLS_RP Messages

C6K_MPLS_RP Messages This section contains Catalyst 6500 series switch and Cisco 7600 series router LAN Multiprotocol Label Switching (C6K_MPLS_RP) messages.

C6K_MPLS_RP-2 Error Message %C6K_MPLS_RP-2-INIT: [chars] Explanation The initialization of the Constellation MPLS forwarding infrastructure failed. This

condition causes problems in the MPLS packet forwarding. The router will be forced to reboot to recover from the problem. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %C6K_MPLS_RP-2-NO_IP_ACL_RSVD_VLAN: IP ACL features will not be applied to MPLS->IP packets due to a lack of internal VLAN resources Explanation This error might occur if the total number of VLANs in use exceeds 4096. The VLAN

resources are shared by VLANs used for SVI, VLANS used for subinterfaces, hidden VLANs used for routed ports, and internal VLANs used for some VRFs. An internal VLAN is needed when an IP ACL feature is applied to a VRF interface. If the total number of VLANs in use exceeds 4096, no more internal VLANs can be allocated, so IP ACL features will not be applied to MPLS-to-IP packets. Recommended Action Reduce the total number of VLANs in use by removing SVI interfaces,

subinterfaces, or VRF interfaces.

Error Message %C6K_MPLS_RP-2-NO_IP_QOS_RSVD_VLAN: IP QoS features will not be applied to MPLS->IP packets due to a lack of internal VLAN resources Explanation This message indicates a condition that might occur if the total number of VLANs in

use exceeds 4096. The VLAN resources are shared by VLANs used for SVI, VLANS used for subinterfaces, hidden VLANs used for routed ports, and internal VLANs used for some VRFs. An internal VLAN is needed when an IP QoS feature is applied to a VRF interface. If the total number of VLANs in use exceeds 4096, no more internal VLANs can be allocated, so IP QoS features will not be applied to MPLS-to-IP packets. Recommended Action Reduce the total number of VLANs in use by removing SVI interfaces,

subinterfaces, or VRF interfaces.


128


C6K_MPLS_RP-3 Error Message %C6K_MPLS_RP-3-GET_RSVD_VLAN_TABLEID_MISMATCH: Tableid [int] in reserved VLAN idb [chars] mismatched application tableid [int] Explanation An application provided a table ID for a reserved VLAN, but the table ID does not match the value in the reserved VLAN interface descriptor block (IDB). Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %C6K_MPLS_RP-3-GET_RSVD_VLAN_VRFID_MISMATCH: Tableid %u in reserved VLAN idb [chars] mismatched application tableid %u Explanation An application gave a table identifier (ID) to get a reserved VLAN interface descriptor block (IDB) but the table ID within the IDB does not match the specified value. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %C6K_MPLS_RP-3-INFINITE_OCE: In label: [dec] Invalid OCE previous oce type: [dec] prev ptr:Unrecognized format ‘ %p’, next oce type: [dec] next oce ptr:Unrecognized format ‘ %p’ Explanation The Output Chain Element(OCE) specified in the system message is invalid because it

has exceeded the maximum depth. One known cause is invalid static route configuration. Traffic for this path will be dropped. Recommended Action Copy the message exactly as it appears on the console or in the system log.



129



Error Message %C6K_MPLS_RP-3-INVALID_TABLEID: Invalid tableid([dec]) for label([dec]) Explanation An invalid table ID was received. The table ID should be in the range of 0 to 4095. This

is an internal software error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %C6K_MPLS_RP-3-INVALID_VRFID: Invalid vrfid(%u) for label([dec]) Explanation An invalid VRF identifier (ID) was received. The VRF ID should be in the range of 0 to

4095. This is an internal software error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %C6K_MPLS_RP-3-L2_CONFIG_NOT_RECOMMENDED: xconnect is configured on interface vlans and WAN interfaces are facing the MPLS Core. Do not configure LAN interfaces facing the MPLS Core. Explanation An attempt was made to configure a LAN interface to face the MPLS core. The current

network configuration has cross-connection services configured on interface VLANs and has WAN interfaces facing the MPLS core. Recommended Action Do not configure MPLS on LAN interfaces facing the MPLS core if the

network has cross-connection services configured on an interface VLAN and WAN interfaces that face the MPLS core.


130


Error Message %C6K_MPLS_RP-3-L3_CONFIG_NOT_RECOMMENDED: LAN interfaces are facing the MPLS Core. Do not configure xconnect on interface vlans. Explanation An attempt was made to configure a cross-connection service on an interface VLAN.

The current network configuration has MPLS configured on a LAN interface that is facing the MPLS core. Recommended Action Do not configure cross-connection services on an interface VLAN if the

network has MPLS configured on a LAN interface.

Error Message %C6K_MPLS_RP-3-NO_RSVD_VLAN_ERROR: Failed to allocate reserved VLAN for vrf [int] Explanation The system failed to allocate an MPLS-reserved VLAN. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %C6K_MPLS_RP-3-PKT_DROP_NO_RSVD_VLAN_IDB: Packet dropped, no idb for reserved VLAN [int] Explanation A packet received on a reserved VLAN was dropped because it did not contain an

interface descriptor block (IDB) for the VLAN. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %C6K_MPLS_RP-3-RECIRC_DROP: Re-circulated packet dropped due to error. Possible causes: MTU or TTL fail Total drops = [int] pkts, Last packet size [int] Bytes Top 3 Labels and partial packet dump -


131


{[int](exp:[dec] eos:[dec] ttl:[dec]), [int](exp:[dec] eos:[dec] ttl:[dec]), [int](exp:[dec] eos:[dec] ttl:[dec])} [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] Explanation A recirculated packet was dropped due to an error. This condition might occur if the size

of a recirculated packet exceeds the egress interface MTU. Recommended Action Increase the MTU size on the egress interface to accomodate the incoming

packets. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message 6K_MPLS_RP-3-RSVD_VLAN_CLEAR_ACL_ERROR: Failed to clear ACL default for reserved VLAN [int] for vrf [int] Explanation The system failed to clear the ACL default for an MPLS-reserved VLAN. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %C6K_MPLS_RP-3-RSVD_VLAN_RELEASE_ERROR: Failed to release reserved VLAN [int] from vrf [int] Explanation The system failed to release an MPLS-reserved VLAN from a VRF either because the

VRF was not found or because a failure occurred when dissociating the VLAN from the VRF. Recommended Action Copy the message exactly as it appears on the console or in the system log.



132


Error Message %C6K_MPLS_RP-3-RSVD_VLAN_SET_ACL_ERROR: Failed to set ACL default for reserved VLAN [int] for vrf [int] Explanation The system failed to set an ACL default for an MPLS-reserved VLAN. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %C6K_MPLS_RP-3-RSVD_VLAN_SET_IDB_ERROR: Failed to set idb of reserved VLAN [int] for vrf [int] Explanation The system failed to set the IDB for an MPLS-reserved VLAN. Recommended Action Copy the message exactly as it appears on the console or in the system log.


C6K_MPLS_RP-6 Error Message %C6K_MPLS_RP-6-PKT_DROP_RSVD_VLAN_TABLEID: Packet dropped, reserved VLAN idb [chars] has incorrect tableid [int] Explanation A packet received on a reserved VLAN was dropped due to an incorrect table ID in the

IDB. This situation might occur during VRF removal. The aggregate label will stay in the H state for a few minutes, while the table ID in the reserved VLAN IDB has already cleared. Recommended Action Copy the message exactly as it appears on the console or in the system log.



133

System Messages C6K_PLATFORM Messages

Error Message %C6K_MPLS_RP-6-PKT_DROP_RSVD_VLAN_VRFID: Packet dropped, reserved VLAN idb [chars] has incorrect tableid %u Explanation A packet received on a reserved VLAN was dropped due to an incorrect table identifier

(ID) in the interface descriptor block (IDB). This condition might occur when, during VRF removal, an aggregate label will stay in the H state for a few minutes, while the table ID in the reserved VLAN IDB has already cleared. Recommended Action Copy the message exactly as it appears on the console or in the system log.


C6K_PLATFORM Messages This section contains general Catalyst 6500 series switch and Cisco 7600 series router platform (C6K_PLATFORM) messages.

C6K_PLATFORM-0 Error Message %C6K_PLATFORM-0-UNKNOWN_CHASSIS: The chassis type is not known.([hex]) Explanation The Cisco IOS software installed on the system does not recognize the chassis type

specified in the error message. Recommended Action Ensure that your Cisco IOS software release train supports the chassis type.

Upgrade your system to the latest Cisco IOS software release in your release train.

C6K_PLATFORM-2 Error Message %C6K_PLATFORM-2-PEER_RESET: [chars] is being reset by the [chars] Explanation The local CPU is being reset by the peer CPU when the peer CPU reloads because of

exceptions. Recommended Action Copy the message exactly as it appears on the console or in the system log.



134



C6K_PLATFORM-3 Error Message %C6K_PLATFORM-3-INFO1: [chars]=[hex] [chars]=[hex] Explanation This message provides information regarding the internal state of the SiByte processor. Recommended Action Copy the message exactly as it appears on the console or in the system log.


C6K_PLATFORM-4 Error Message %C6K_PLATFORM-4-CONFREG_BREAK_ENABLED : The default factory setting for config register is 0x2102.It is advisable to retain 1 in 0x2102 as it prevents returning to ROMMON when break is issued. Explanation The SP configuration register has been changed from the default factory setting of

0x2102 to another hexadecimal value. Recommended Action No action is required.

Error Message %C6K_PLATFORM-4-ENVMON: System shutdown due to temperature alarms is [chars]. Explanation The system has a configuration to shut down a module if its operating temperature

exceeds a temperature threshold. This configuration has been bypassed, and a module will still operate in an over-temperature condition. Operating at an over-temperature condition can damage the hardware. Recommended Action Do not override the sensor alarms that act on an over-temperature condition.

Enter the environment-monitor shutdown temperature command to bring the system back to standard temperature detection.


135


Error Message %C6K_PLATFORM-4-RTC_OSCILLATOR: The oscillator in the Real Time Clock is [chars]. Calendar [chars] be maintained during the powered down state of the switch. Explanation A command has been entered that will cause the system calendar not to be maintained

during a power down of the switch. The system date and time will require manual setting when the system is powered up during the next boot time. This command is useful to conserve the battery power of the CMOS, which is used to keep the real-time clock active while the switch is powered down. This condition is useful only if the switch is powered down for a long period of time. Recommended Action If the switch need not be powered down for a long period of time, remove the

configuration by entering the no hw-module rtc-oscillator shutdown command.

C6K_PLATFORM-5 Error Message %C6K_PLATFORM-5-LESS_SPACE : May not have enough space to save the crash info. on flash of [chars] on module: [dec] Explanation The flash memory device does not have enough memory to save the crash information.

The crash information might not be saved on the flash memory device. Recommended Action Remove unnecessary files from the flash memory device, and enter the squeeze

command for the flash memory device.

Error Message %C6K_PLATFORM-5-MISMATCH : '[chars]' device programming algorithm mismatch detected on [chars] (module: [dec]), formatting is recommended. Explanation The flash memory device programming algorithm that was written to the device when

the flash memory was formatted is different from what the current running software has detected. The first [chars] is the device, the second [chars] is where the mismatch was detected, and [dec] is the module number. This conditions occurs when a flash memory is installed into a system with a different Cisco IOS release or when a Cisco IOS upgrade is performed on the switch. Recommended Action Reformat the flash memory device. Otherwise, no action is required.

C6K_PLATFORM-6 Error Message %C6K_PLATFORM-6-PACKET_BUFFER: This setting will cause a packet buffer error to [chars] Explanation This warning message appears when the configuration contains the error-detection

packet-buffer action command. Upon detecting a packet buffer failure on an ASIC, the supervisor engine takes the action specified by the error-detection packet-buffer action command (and shown in [chars]). The choices include error-disabling the ports on a particular ASIC, error-disabling the the module, or automatically power-cycling the module. To view the default and configured actions on all modules, enter the show error-detection packet-buffer command. Recommended Action .This message is informational only. No action is required.


136

System Messages C6K_POWER Messages

C6K_POWER Messages This section contains Catalyst 6500 series switch and Cisco 7600 series router power (C6K_POWER) messages. For more power messages, see the C6KPWR Messages section of this chapter.

C6KPWR Error Message %C6KPWR-SP-2-PSFAIL: power supply [dec] output failed. Explanation Power supply [dec] has failed. Recommended Action Replace the power supply.

Error Message %C6KPWR-SP-4-PSOK: power supply [dec] turned on. Explanation Power supply [dec] is turned on. Recommended Action No action is required.

Error Message %C6KPWR-SP-4-PSREDUNDANTBOTHSUPPLY: in power-redundancy mode, system is operating on both power supplies. Explanation When the system is in power redundancy mode, it operates on both power supplies. Recommended Action No action is required.

C6K_POWER-3 Error Message %C6K_POWER-3-NOTIFY_FAIL: Failed to notify RP of change in operator status for [chars] number [dec] from ’[chars]’ to ’[chars]’ Explanation The SP is unable to acquire the resources needed to notify the RP of the event specified

in the error message. Recommended Action Copy the message exactly as it appears on the console or in the system log.



137

System Messages C6K_PROCMIB Messages

C6K_POWER-4 Error Message %C6K_POWER-4-PD_NOLINKUP: The device connected to [dec]/[dec] is powered up but its link is not up in [dec] seconds. Therefore, power is withdrawn from the port. Explanation The system withdrew the power that was allocated to the specified port because the port

link was not operational in the specified number of seconds. Recommended Action Try to connect the device to a different port or connect a different device to the

port specified in the message.

C6K_POWER-6 Error Message %C6K_POWER-6-NOLPP: Because of lack of system power, devices that require the system to power them on may not come up within one second. Explanation The local power pools have been deallocated. The module firmware cannot power up

the device until it has received authorization for power allocation from the software running on the supervisor engine. Recommended Action No action is required.

C6K_PROCMIB Messages This section contains Catalyst 6500 series switch and Cisco 7600 series router Process MIB SP CPU (C6K_PROCMIB) messages.

C6K_PROCMIB-3 Error Message %C6K_PROCMIB-3-IPC_PORTOPEN_FAIL: Failed to open port while connecting to process statistics: error code = [chars] Explanation An error occurred during an attempt to open a port for an IPC message. Recommended Action Copy the message exactly as it appears on the console or in the system log.



138

System Messages C6KPWR Messages

Error Message %C6K_PROCMIB-3-IPC_TRANSMIT_FAIL: Failed to send process statistics update : error code = [chars] Explanation An error occurred during an attempt to send an IPC message. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %C6K_PROCMIB-3-MALLOC_FAILURE_IPC: Failed to allocate IPC message to contact process Explanation A memory allocation failure occurred during the processing of an IPC message. Recommended Action Copy the message exactly as it appears on the console or in the system log.


C6KPWR Messages This section contains Catalyst 6500 series switch and Cisco 7600 series router power (C6KPWR) messages.

C6KPWR-2 Error Message %C6KPWR-2-INSUFFICIENTPOWER: Powering down all linecards as there is not enough power to operateall critical cards Explanation The switch was operating with two power supplies in combined mode. One of power supplies has failed. Available power is insufficient to support all critical service modules. Critical service modules include modules that support VPNs or IP security. If these critical modules fail, security issues could arise; therefore, all modules have been powered down. Recommended Action Replace the failed power supply.


139


Error Message %C6KPWR-2-MAJORPOWERALARM: In the absence of power supply 1, system power usage exceeds allowed range of [chars]W. Power total will be reduced in [dec] seconds Explanation This message indicates a major power alarm condition. The power supply in slot 2 has

exceeded its allowed range. The range is specified in the error message. Recommended Action Enter the show power command to determine the actual power usage. Insert a

power supply in power supply slot 1, or power down some modules to reduce system power usage. If downtime can be scheduled, move the power supply from slot 2 to slot 1. If this condition persists, the environmental monitor will shut down some modules to prevent a complete power failure.

Error Message %C6KPWR-2-MAJORPOWERALARMRECOVER: System power usage has returned to allowed operating range Explanation This message indicates that system power usage has returned to the permitted operating

range. The scheduled shutdown is cancelled, and the system will continue operating. Recommended Action No action is required.

Error Message %C6KPWR-2-MINORPOWERALARM: In the absence of power supply 1, system power usage exceeds the recommended range of [chars]W Explanation This message indicates a minor power alarm condition. The power supply in slot 2 has

exceeded its allowed range. The range is specified in the error message. Selected modules will be shut down to prevent a complete power failure. Recommended Action Enter the show power command to determine the actual power usage. Insert a

power supply in power supply slot 1, or power down some modules to reduce system power usage. If downtime can be scheduled, move the power supply from slot 2 to slot 1.

C6KPWR-3 Error Message %C6KPWR-3-PSUNKNOWN: Unknown power supply in slot [dec] (idprom read failed). Explanation The IDPROM of the power supply in the specified slot cannot be read. Recommended Action Remove and reinsert the power supply. Fasten the screw and attempt to operate the power supply again. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


140


C6KPWR-4 Error Message %C6KPWR-4-INPUTCHANGE: Power supply [dec] input has changed. Power capacity adjusted to [chars]W Explanation The power supply in the specified slot has detected a change in its input supply. The

power capacity for the power supply has been adjusted accordingly. Recommended Action Enter the show power command to see the current power status. Otherwise, no

action is required.

Error Message %C6KPWR-4-MAJORPOWERALARMRECOVER: System power usage has returned to allowed operating range Explanation This message indicates that system power usage has returned to the allowed operating range, so the scheduled shutdown was cancelled. The system will continue operating. Recommended Action No action is required.

Error Message %C6KPWR-4-MINORPOWERALARM: In the absence of power supply 1, system power usage exceeds the recommended range of [chars]W Explanation This message indicates a minor power alarm condition. The power supply in slot 2 has

exceeded its allowed range. The range is specified in the error message. Selected modules will be shut down to prevent a complete power failure. Recommended Action Enter the show power command to determine the actual power usage. Insert a

power supply in power supply slot 1, or power down some modules to reduce system power usage. If downtime can be scheduled, move the power supply from slot 2 to slot 1.

Error Message %C6KPWR-4-MINORPOWERALARMRECOVER: System power usage has returned to normal operating range Explanation This message indicates that system power usage has returned to the normal operating

range. Recommended Action No action is required.

Error Message %C6KPWR-4-PS1FAILALERT: Do not remove power supply 1 without inserting another supply. In the absence of power supply 1, system power capacity will be reduced to [chars]W after a [dec] second grace period. Explanation The system is experiencing heavy traffic. In this condition, the single power supply

should be used in slot 1 rather than in slot 2. Recommended Action Insert a power supply in slot 1, or move the power supply from slot 2 to slot 1.


141

System Messages C6K_VSD_ROIR Messages

Error Message %C6KPWR-4-PS2ONLY: Single power supply system should utilize power supply slot 1 Explanation The system is experiencing heavy traffic. In this condition, the single power supply

should be used in slot 1 rather than in slot 2. Recommended Action Move the power supply from slot 2 to slot 1.

Error Message %C6KPWR-4-PSINPUTDROP: Power supply [dec] input has dropped Explanation The power supply in the specified slot has detected a drop in its input supply. The power

capacity for the power supply has been adjusted accordingly. Recommended Action Enter the show power command to see the current power status. Otherwise, no

action is required.

Error Message %C6KPWR-4-PSMISMATCH: power supplies rated outputs do not match. Explanation The two power supplies in the system have different output ratings. Recommended Action For more efficient load sharing, use power supplies with the same output

rating.

Error Message %C6KPWR-4-PSNOREDUNDANCY: Power supplies are not in full redundancy, power usage exceeds lower capacity supply Explanation The two power supplies in the system have different output ratings. Current power usage

exceeds the capacity of the lower-rated power supply. If the higher-rated power supply fails, the lower-rated power supply will not be able to support all modules that are currently powered up. Recommended Action To ensure that the system power supplies are optimally redundant, use power

supplies with identical output ratings or reduce system power consumption.

C6K_VSD_ROIR Messages This section contains Catalyst 6500 series switch and Cisco 7600 series router messages.

C6K_VSD_ROIR-2 Error Message %c6k_VSD_ROIR-2-ROIR_INVALID_MODULE_TYPE: Remote switch module type is invalid : slot [dec] Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



142



Error Message %c6k_VSD_ROIR-2-ROIR_INVALID_SYNC_EVENT: ROIR: [chars] receiver process has received an invalid sync event OrIt can’t sync the event to its standby counter part Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %c6k_VSD_ROIR-2-ROIR_NULL_MODULE_DATA_STRUCTURE: [chars] bay(per-module) data structure ptr is NULL Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %c6k_VSD_ROIR-2-ROIR_NULL_MODULE_DATA_STRUCTURE_TYPE: ROIR: [chars] bay(per-module) data structure ptr is not NULLmodule data structure TYPE is NULL Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



143


http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %c6k_VSD_ROIR-2-UNKNOWN_OR_NULL_EVENT_RECEIVED: [chars]: Received [chars] event Explanation The system was unable to create a watched boolean for the ROIR event receiver process,

which is used to recieve ROIR messages. This message could indicate a catastrophic software error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %c6k_VSD_ROIR-2-VECTOR_IS_NULL: [chars] [chars]: Vector is NULLResource or config callbacks couldn’t be called when module hadProblems coming online Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


C6K_VSD_ROIR-3 Error Message %c6k_VSD_ROIR-3-ROIR_HUGE_BAY_SIZE: ROIR: [chars], failed to send bulk sync for bay type [dec] due to its huge unit size [dec] Explanation Remote OIR failed to bulk sync for one bay typebecause of its huge unit size. Recommended Action This is a system error. Please contact Cisco tech-support.


144


Error Message %CDP-3-CHUNK: Chunk_malloc Failure Explanation chunk malloc failure Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %c6k_VSD_ROIR-3-ROIR_ISSU_SESS_INCOMPLETE: ROIR ISSU SESSION INVALID: issu nego session not completed Explanation The remote OIR did not complete the ISSU session negotiation. The system is trying to

transform a message sent or received. This is a system error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %c6k_VSD_ROIR-3-ROIR_LATE_EVENT_RESPONSE: ROIR: sender dropped late response for slot [dec] type [dec] seq [dec] result [dec] Explanation The remote OIR sender received a late processing response. The request timed out while

waiting for a response. This is a system error. Recommended Action Copy the message exactly as it appears on the console or in the system log.



145


Error Message %c6k_VSD_ROIR-3-ROIR_TIMER_WB_FAIL: ROIR Timer Process : Unable to create watched boolean Explanation The system was unable to create a watched boolean for a timer process of ROIR. This

message could indicate an internal software error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


C6K_VSD_ROIR-6 Error Message %c6k_VSD_ROIR-6-BAD_IDPROM: ROIR:idprom error [chars] for index [chars], switch_id [dec]physical_slot [dec] Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %c6k_VSD_ROIR-6-BAY_IS_NULL: [chars], bay is NULL bay_type:[dec], index:[dec] Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



146


Error Message %c6k_VSD_ROIR-6-BULK_SYNC_MSG_SEND_FAILED: [chars] Failure sending Bulk sync msg Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %c6k_VSD_ROIR-6-ERR_GET_SWID: [chars] Error ([dec]) in getting swid and phy_idx for vidx [dec] Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %c6k_VSD_ROIR-6-EVENT_SEND_FAILED: Remote Oir::Sender: Events for for Module Type [dec] Slot [dec] could not be sent to core because [chars] Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



147


Error Message %c6k_VSD_ROIR-6-FAILED_TO_GET_PAK: ROIR:Notify Failed to get pak for [chars] notification Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %c6k_VSD_ROIR-6-FAILED_TO_SEND_NOTIFICATION: ROIR:Notify Failed to send [chars] notification Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %c6k_VSD_ROIR-6-GETBUFFER_FAILED: ROIR: [chars] getbuffer failed. Mod type = [dec], slot# = [dec] Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



148


Error Message %c6k_VSD_ROIR-6-INVALID_SM_INSTANCE: Unable to get remote module State Machine instance forswitch [dec] slot [dec] module_type [dec] Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %c6k_VSD_ROIR-6-MALLOC_FAILURE: Switch Id: [dec] : malloc for [chars] failed Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %c6k_VSD_ROIR-6-NACKED_EVENT: [chars] Remote Oir::CORE NACK’ed event status [dec] Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



149


Error Message %c6k_VSD_ROIR-6-POST_PROCESSING_NOTIFY_FAILED: ROIR:sender [chars] Post processing notifications to local applns failed Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %c6k_VSD_ROIR-6-PROCESSING_FAILED: ROIR::Sender:: For Bay type [dec] slot [dec] - Core unsuccessful in processing event type [dec] status [dec] Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %c6k_VSD_ROIR-6-RECEIVED_NULL_ARG: [chars] received NULL argument Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



150


Error Message %c6k_VSD_ROIR-6-REGISTRY_ADDITION_FAILED: Registry addition failed for [chars] Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %c6k_VSD_ROIR-6-REMOTE_MODULE_SANITY_CHK_FAILED: sanity check failed for remote module virtual slot number [dec] Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %c6k_VSD_ROIR-6-REMOTE_SWITCH_NOT_ONLINE: [chars] remote switch not online [dec] Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



151


Error Message %c6k_VSD_ROIR-6-RF_CLIENT_NOTIFY_TIMER: [chars](): Could not extend notification timer



Error Message %c6k_VSD_ROIR-6-RF_ROIR_MESG_SEND_FAILED: [chars] (): Error sending remote oir rf message Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %c6k_VSD_ROIR-6-RF_SEND_PEER_MSG_FAILED: [chars] - rf_send_peer_msg failed Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



152


Error Message %c6k_VSD_ROIR-6-ROIR_BAD_VSLOT_NUM: [chars] virtual slot [dec] number is invalid for virtual switch module Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %c6k_VSD_ROIR-6-ROIR_EVENT_SEND_NULL_IDPROM: ROIR Event Send failed : fru type [dec] bay type [dec] unit [dec] name [chars] description [chars] - reason: [chars] Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %c6k_VSD_ROIR-6-ROIR_RECV_EVENT_ERROR: ROIR:incoming event error received [chars] event Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



153


Error Message %c6k_VSD_ROIR-6-ROIR_UNABLE_TO_GET_REMOTE_MODULE_DATA_STRUCT: Unable to get remote switch module data structure forswitch [dec] slot [dec] module type [dec] Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %c6k_VSD_ROIR-6-SLOT_IS_ZERO: [chars] slot is ZERO Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %c6k_VSD_ROIR-6-TIMER_EVENT_RECV: ROIR::Receiver::Timer Process got TIMER event Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



154


Error Message %c6k_VSD_ROIR-6-TIMER_EXPIRED: ROIR::Receiver::For Switch:[dec] Type [dec] Phy Slot [dec] - [chars] timer expired Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %c6k_VSD_ROIR-6-UNABLE_TO_COMMUNICATE_THREAD: Remote Oir::Sender:: Cannot communicate thread sub block to type [dec] slot [dec] Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %c6k_VSD_ROIR-2-UNABLE_TO_CREATE_PROCESS: Could not create [chars] Process Explanation The system was unable to create a watched boolean for the timer process of ROIR. This

could indicate an internal software error. Recommended Action Copy the message exactly as it appears on the console or in the system log.



155


Error Message %c6k_VSD_ROIR-6-UNABLE_TO_CREATE_ROIR_PROCESS: ROIR:Core Process creation failedswitch [dec] slot [dec] module_type [dec] Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %c6k_VSD_ROIR-6-UNABLE_TO_CREATE_SWOVER_PROCESS: ROIR:HA error Could not create Remote Swover process!!pid: [dec] for slot [dec] Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %c6k_VSD_ROIR-6-UNABLE_TO_CREATE_THREAD_INSTANCE: Remote Oir::Sender::Unable to create a [chars] for process type [dec] slot [dec] Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



156


Error Message %c6k_VSD_ROIR-6-UNABLE_TO_CREATE_WB: ROIR: [chars] Unable to create [chars] watched boolean Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %c6k_VSD_ROIR-6-UNABLE_TO_GET_THREAD_SUBLOCK: Unable to get thread sub-block. Unable to continue. Remote switch sender thread aborting. Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %c6k_VSD_ROIR-6-UNABLE_TO_INIT: ROIR: Core: Unable to init [chars] Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



157


Error Message %c6k_VSD_ROIR-6-UNABLE_TO_RETRIEVE_MODULE_DATA_STRUCTURE: Unable to get module data structure for remote module Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %c6k_VSD_ROIR-6-WORKER_THREAD_IDENT_FAILED: ROIR::Recvr [chars] Could not get identify worker thread id Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %c6k_VSD_ROIR-6-WORKER_THREAD_INVALID_THREAD: ROIR::Recvr - Bay sw[dec] type[dec] slot[dec] - [chars] Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



158

System Messages C6K_WAN_C2W Messages

Error Message %c6k_VSD_ROIR-6-WORKER_THREAD_PACK_DROPPED: ROIR::Rcvr Worker Thread [dec] dropped packet because data section NULL! Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %c6k_VSD_ROIR-6-WORKER_THREAD_SET_OR_CREATE_WORKER_THREAD: ROIR::Rcvr Worker Unable to [chars] thread [chars] Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


C6K_WAN_C2W Messages This section contains Catalyst 6500 series switch and Cisco 7600 series router WAN C2Wire (C6K_WAN_C2W) messages.

C6K_WAN_C2W-4 Error Message %C6K_WAN_C2W-4-READERROR: C2Wire read failed reg [hex] on device [chars] Explanation The SMbus driver failed to read from the specified C2W device. Recommended Action No action is required if this warning message appears occasionally. If the

message appears often in a short period of time, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at


159

System Messages C7600_ES Messages


Error Message %C6K_WAN_C2W-4-WRITEERROR: C2Wire write failed reg [hex] on device [chars] Explanation The SMbus driver failed to write to the specified C2W device. Recommended Action No action is required if this warning message appears occasionally. If the

message appears often in a short period of time, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

C7600_ES Messages This section contains Ethernet Services linecard messages.

C7600_ES-2 Error Message %C7600_ES-2-CRITICAL_ERR: C7600-ES Line Card Failure: [chars] Explanation A critical error has occured on the C7600-ES Line Card. The message that was

previously received on the console or in the system log and cash dump should provide more information of the problem. Recommended Action If the problem persists, then collect crash dump and File a DDTS. Copy the

message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


160


Error Message %C7600_ES-2-IOFPGA_IO_BUS_ERROR: C7600-ES Line Card IOFPGA IO [chars] Bus Error: Error = [hex] Error Address = [hex], Error Data = [hex] Explanation An unexpected hardware error condition has occured on the C7600-ES Line Card.

SELENE/LINKFPGA/PEFPGA FPGA failed to respond to a read or write access. This message indicates a hardware failure or a malfunction. The linecard will reload to attempt to fix the problem.

Error Message %C7600_ES-2-NMI_RESET: C7600-ES Line Card NMI reset by SUP Explanation The Supervisor detected C7600-ES line card as unresponsive and attempted to recover

line card by issuing an Non Maskable Interrupt. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %C7600_ES-2-NP_FAILURE: C7600-ES Line Card NP [dec] Failure: [chars] Explanation An unexpected fatal condition has occured on the C7600-ES Line Card. The message

that was previously received on the console or in the system log and cash dump should provide more information of the problem. This message indicates a NP failure or malfunction. The LC will reset to attempt to fix the problem. Recommended Action If the problem persists, then collect crash dump and File a DDTS. Copy the


Error Message %C7600_ES-2-NP_WORKAROUND: C7600-ES Line Card NP[[dec]] Workaround [chars] after [[dec]] retries Explanation The NP workaround routine on the C7600-ES Line Card Passed/Fail.If the workaround

failed, it will result in packets not being forwarded. Recommended Action Attempt to reload the line card. If the problem persists, then copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug


161


Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %C7600_ES-2-PEX_INIT_FAILED: C7600-ES Line Card PCI Express Initialization failed at [chars][[dec]] Explanation The C7600-ES Line Card received an error during initialization when attempting to

initialize the PCI Express interface with the forwarding hardware. A hardware problem has prevented the target line card from fully initializing. This will result in packets not being forwarded. Recommended Action Attempt to reload the line card. If the problem persists, then copy the error

message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message %C7600_ES-2-UNRECOVERABLE_FAILURE: C7600-ES Line Card Unrecoverable Failure for Device: [chars] Explanation An unexpected fatal condition has occured on the C7600-ES Line Card. The message

that was previously received on the console or in the system log should provide more information on the specific nature of the problem. This message indicates a hardware failure or malfunction. The system will reload to attempt to fix the problem. Recommended Action If this message recurs, copy the error message exactly as it appears on the

console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.


162


C7600_ES-3 Error Message %C7600_ES_LINK-3-FPGA_NOT_READY: [chars] reports Link FPGA is not ready (ConfigPLD status [hex])! Explanation The Link FPGA configuration is not done properly. This could be caused by an

incompleted Link FPGA update in a previous FPD upgrade process. Recommended Action Restart the FPD upgrade. If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message %C7600_ES-3-KPFPGA_FIFO_INT: C7600-ES Line Card Packet Engine Supertycho KPFPGA Interrupt Explanation An unexpected hardware error condition has occured on the C7600-ES Line Card. Some

data traffic between EARL and the firmware ASIC Metropolis is flow controlled. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %C7600_ES-3-KPFPGA_PARITY_ERR_INT: C7600-ES Line Card Packet Engine Supertycho KPFPGA Parity Error Explanation An unexpected hardware error condition has occured on the C7600-ES Line Card. A

parity error occured during KPFPGA register access. Recommended Action Copy the message exactly as it appears on the console or in the system log.



163


Error Message %C7600_ES-3-PE_INT_BUS_ACL_PARITY: C7600-ES Line Card Packet Engine ACL Counter FPGA Parity ErrorIO Bus Error Address = [hex], IO Bus Error Data = [hex] Explanation An unexpected hardware error condition has occured on the C7600-ES Line Card. A

parity error is detected when reading from the ACL Counter FPGA. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %C7600_ES-3-PE_INT_BUS_INV_ADDR_ERR: C7600-ES Line Card Packet Engine Invalid Address Access on Earl CardIO Bus Error Address = [hex], IO Bus Error Data = [hex] Explanation An unexpected hardware error condition has occured on the C7600-ES Line Card. An

IO Bus transfer from the Baseboard goes to an undefined address on the EARL card. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %C7600_ES-3-PE_INT_BUS_PARITY: C7600-ES Line Card Packet Engine Bus Parity ErrorIO Bus Error Address = [hex], IO Bus Error Data = [hex] Explanation An unexpected hardware error condition has occured on the C7600-ES Line Card. A

parity error is detected on the IO Bus from the Baseboard. Recommended Action Copy the error message exactly as it appears on the console or in the system



164


Error Message %C7600_ES-3-PE_INT_BUS_PROTOCOL_ERR: C7600-ES Line Card Packet Engine IO Bus Protocol ErrorIO Bus Error Address = [hex], IO Bus Error Data = [hex] Explanation An unexpected hardware error condition has occured on the C7600-ES Line Card. A

transfer on the IO Bus between the Baseboard and the Earl FPGA did not follow the bus protocol. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %C7600_ES-3-PE_INT_BUS_ST_PARITY: C7600-ES Line Card Packet Engine Supertycho Parity ErrorIO Bus Error Address = [hex], IO Bus Error Data = [hex] Explanation An unexpected hardware error condition has occured on the C7600-ES Line Card. A

parity error is detected when reading from the Supertycho register. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %C7600_ES-3-PE_INT_BUS_TIMEOUT: C7600-ES Line Card Packet Engine Bus Timeout: IO Bus Error Address = [hex], IO Bus Error Data = [hex] Explanation An unexpected hardware error condition has occured on the C7600-ES Line Card.

Supertycho or the ACL Counter FPGA failed to respond to a read or write access within 1 usec. Recommended Action Copy the error message exactly as it appears on the console or in the system



165


C7600_ES-5 Error Message %C7600_ES-5-BRIDGE_ASIC_INTR: The Bridge-ASIC-[chars][[dec]] interrupt asserted. Addr[[hex]]=[hex] Explanation The Bridge-ASIC on the linecard has experienced an interrupt. The recovery action is

already taken and no further action is needed. Recommended Action No action is required.

Error Message %C7600_ES-5-FPGA_IMAGE_CORRUPTED: [chars] failed to program at power up, presumed corrupted. Explanation One of the FPGAs failed to program at boot. The board will not and cannot forward

traffic in this state. Failure to program presumably caused by corrupted FPGA image. Likely cause of corrupted FPGA image: write failure during FPGA FPD upgrade. Likely cause of FPGA FPD upgrade fauilure: unexpected LC reset during FPD upgrade. Recommended Action If failure occured during a FPGA FPD upgrade, ensure that LC was not or will not be inadvertently reset during upgrade. Some FPGA FPD upgrades might require a longer time to complete, and an inadvertent reset during the programming interval will corrupt the FPGA image. If failure did not occur during an FPD upgrade, the FPGA recovery logic will nevertheless necessitate a FPGA FPD upgrade. As a reminder, this requires an FPD bundle file on the supervisor to complete.

Error Message %C7600_ES-5-FPGA_RECOVERY: [chars] recovery invoked. Explanation FPD is being invoked to recover corrupted FPGA FPD image. Allow a few minutes for

programming to complete. FPD will report results from programming FPGA. If FPD reports success, recovery has completed successfully. Recommended Action Verify that FPD successfully recovered image.

Error Message %C7600_ES-5-MET_TIMEOUT: Rewrite Engine Multicast Expansion Table access timeout recovery action invoked, Address = [hex] Explanation The linecard experienced an IO-BUS timeout while accessing the Multicast Expansion

Table. The recovery action is already taken and no further action is needed. Recommended Action No action is required


166


C7600_ES-LINK-3 Error Message %C7600_ES_LINK-3-FPGA_NOT_READY: [chars] reports Link FPGA is not ready (ConfigPLD status [hex])! Explanation The Link FPGA configuration is not done properly. This could be caused by an

incompleted Link FPGA update in a previous FPD upgrade process. Recommended Action Restart the FPD upgrade. If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message %C7600_ES_LINK-3-INIT_FAILED: Failed to initialize Link Daughtercard. Explanation Link Daughter card initilization process failed caused by a Link FPGA not ready,

memory allocation failure, or a fatal OS kernel error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %C7600_ES_LINK-3-INTR_THROTTLE: Interface [chars] PHY interrupt is throttled. Total throttle count [dec]. Explanation A 10GE PHY interrupt burst has occurred on one of the interfaces on the link daughter card. The error message indicates that a throttling mechanism has been applied to this port to avoid any operational damage that could be provoked by this event. Possible causes of this problem include a bad transceiver, frequently flapping optical signals, or mismatched path signals (that is, receiving a 10GBASE-W signal on 10GE LAN interface). Recommended Action Check the interface configuration and received signal characteristics. Verify

the XFP transceiver and receive signal path to determine the exact root cause. If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical suppor


167


Error Message %C7600_ES_LINK-3-SEND_MSG: Link DC failed to notify driver process about a line state change in the interface port [dec] Explanation A line state change has occurred on one of the interface ports on the link daughter card.

The error message indicates the port number. The state change notification could not be sent to the link daughter card processor. The cause for this problem could be memory exhaustion. Recommended Action Enter the show memory summary command to attempt to determine the cause

of the error. If it is insufficient system memory, Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

C7600_ES-LINK-4 Error Message %C7600_ES_LINK-4-SCPBUF_ERR: Failed to get packet from SCP packet pool for [chars] Explanation The Line Card failed to allocate a packet from the SCP packet pool for the transceiver

control message specified in the error message. Recommended Action No action is required.

C7600_ES-LINK-5 Error Message %C7600_ES_LINK-5-ALS_RESTARTREJ: ALS manual restart command on the Interface [chars] is rejected. Explanation The most recent Automatic Laser Shutdown manual restart command (als restart mode manual) on the given interface was issued when the ALS statemachine was not in the IDLE state and could not be accepted. Recommended Action No action is required.


168

System Messages .C7600_SIP200 Messages

.

C7600_SIP200 Messages This section contains SPA Interface Processor 200 (C7600_SIP200) messages.

C7600_SIP200-3 Error Message %C7600_SIP200-3-BADIFCTRL: Corrupted sip-200 information for interface [chars] [[hex]] Explanation The interface SIP 200 information is not valid. This message indicates an internal software error. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show memory command on the line card. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %C7600_SIP200-3-SONET_CLOCK_FAILED: SPA Sonet clock has failed (status = [hex]) Explanation The SPA SONET clock has failed. SPAs that rely on the SPA SONET clock for proper

operation, such as PoS and ATM, will be affected. Recommended Action If the SPA SONET clock does not recover, perform an OIR.

Error Message %C7600_SIP200-3-SONET_CLOCK_RECOVERED: SPA Sonet clock has recovered (status = [hex]) Explanation The SPA SONET clock has recovered. Recommended Action No action is required.


169

System Messages C7600_SIP200_MP Messages

C7600_SIP200-4 Error Message %C7600_SIP200-4-MEM_MODULE_MISMATCH: Memory modules are not identical Explanation The memory modules do not have identical parameters. This condition might impact

performance. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show memory command on the line card. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

C7600_SIP200_MP Messages This section contains SIP 200 multiprocessing (C7600_SIP200_MP) messages.

C7600_SIP200_MP-1 Error Message %C7600_SIP200_MP-1-UNSAFE: Multiprocessor error on [chars] Explanation The line card CPU contains two CPU cores, one of which is the master CPU. The CPU

specified in the error message attempted to perform an operation that is illegal for multiprocessor operation between the two CPU cores. Recommended Action Copy the message exactly as it appears on the console or in the system log.



170

System Messages C7600_SIP200_MP Messages

C7600_SIP200_MP-3 Error Message %C7600_SIP200_MP-3-INIT_FAILURE: Second CPU initialization failed Explanation The line card CPU unit has two CPU cores in it. The second CPU core is not initialized

successfully, so the line card is operating with one CPU core only. You may also see a SYS-2-MALLOCFAIL warning message. Recommended Action If this message appears when a line card boots up, reload the line card by

entering the hw-module module slot reset command. Also, check the amount of memory on the line card by entering the show controller cwan command.

C7600_SIP200_MP-4 Error Message %C7600_SIP200_MP-4-PAUSE: Non-master CPU is suspended for too long, from [hex]([int]) to [hex] for [int] CPU cycles. [chars] Explanation The line card CPU contains two CPU cores, one of which is the master CPU. The master

CPU caused the second nonmaster CPU to be suspended for too long a time. This condition could cause the nonmaster CPU to drop packets. This warning indicates a transient software problem, and the line card should continue to operate normally. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %C7600_SIP200_MP-4-TIMEOUT: Master CPU request timed out [chars] Explanation The line card CPU contains two CPU cores, one of which is the master CPU. The

nonmaster CPU is not responding in time to the request from the master CPU. This warning indicates a transient software problem. The line card should continue to operate normally. Recommended Action If this message recurs, copy the message exactly as it appears on the console



171

System Messages C7600_SIP200_SPIRX Messages

C7600_SIP200_SPIRX Messages This section contains SIP 200 SPI4.2 bus ingress interface (C7600_SIP200_SPIRX) messages.

C7600_SIP200_SPIRX-3 Error Message %C7600_SIP200_SPIRX-3-INITFAIL: Failed to configure the ingress SPI4.2 device. Error = [hex] Explanation The system cannot program or configure the ingress SPI4.2 device on the line card. This condition indicates an internal hardware error. Recommended Action If this problem recurs, copy the message exactly as it appears on the console or

in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA.

Error Message %C7600_SIP200_SPIRX-3-SPA_INTERRUPT: SPA [int] - [chars], SPA Int status = [hex] Explanation A SPA interrupt from the ingress SPI4.2 device has occurred. Recommended Action If this problem recurs, copy the message exactly as it appears on the console or


Error Message %C7600_SIP200_SPIRX-3-SPI4_LINKERROR: SPA Bay [int], [int] SPI4 Link Failures Explanation Link errors from the ingress SPI4.2 device have occurred. Recommended Action If this problem recurs, copy the message exactly as it appears on the console or

in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,


172

System Messages C7600_SIP200_SPIRX Messages

open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA.

Error Message %C7600_SIP200_SPIRX-3-SRAM_ERROR_DATA: SRAM[dec] Address = [hex][hex] Data = [hex][hex][hex]_[hex][hex][hex]_[hex][hex][hex]_[hex][hex] [hex] Explanation An SRAM address and data dump has occurred. Recommended Action If this problem recurs, copy the message exactly as it appears on the console or


Error Message %C7600_SIP200_SPIRX-3-SRAM_INTERRUPT: [chars], Sram Int status = [hex] Explanation An SRAM interrupt has occurred from the ingress SPI4.2 device. Recommended Action If this problem recurs, copy the message exactly as it appears on the console or


Error Message %C7600_SIP200_SPIRX-3-STATUS_INTERRUPT: [chars], Global Int status = [hex] Explanation A status interrupt has occurred from the ingress SPI4.2 device. Recommended Action If this problem recurs, copy the message exactly as it appears on the console or

in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support


173

System Messages C7600_SIP200_SPITX Messages

representative and provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA.

C7600_SIP200_SPITX Messages This section contains SIP 200 SPI4.2 bus egress interface (C7600_SIP200_SPIRX) messages.

C7600_SIP200_SPITX-3 Error Message %C7600_SIP200_SPITX-3-BADDESC: descriptor [hex], tag [hex], global channel [int] Explanation The egress SPI4.2 device on the line card returns a descriptor entry that is corrupted. Recommended Action If this problem recurs, copy the message exactly as it appears on the console or


Error Message %C7600_SIP200_SPITX-3-BADPAK: corrupted packet to [chars] Explanation The egress SPI4.2 device on the line card is handling a packet that is corrupted. This condition indicates that an internal software error has occurred. The corrupted packet has been dropped. Recommended Action If this problem recurs, copy the message exactly as it appears on the console or



174


Error Message %C7600_SIP200_SPITX-3-CHANNEL_ENABLE_FAIL: SPI4 Channel [int] for Bay [int], [chars] Failed Explanation The specified SPI4 channel could not be enabled or disabled. Recommended Action If this problem recurs, copy the message exactly as it appears on the console or


Error Message %C7600_SIP200_SPITX-3-DESCR_ERR_SPA0: SPAstatus=[hex], syndrome=[hex], RdRspOvf=[int], RdRspTo=[int], OvfVal=[int], OvfCh=[int], OvfDescHi=[hex], OvfDescLo=[hex], DisChk=[int], SeqErrVal=[int], SeqErrCh=[int] Explanation The egress SPI4.2 device on the line card detected a sequence or FIFO overflow error

while processing a TX descriptor. This condition could cause packets to drop. Recommended Action If this problem recurs, copy the message exactly as it appears on the console or






175








Error Message %C7600_SIP200_SPITX-3-DMA_SQERR: Syndrome=[hex], SPA=[int], Ch=[int], RdSz=[int], RdOff=[int][chars] Explanation The egress SPI4.2 device on the line card detected a sequence error while processing a

DMA operation. This condition could cause packets to drop. Recommended Action If this problem recurs, copy the message exactly as it appears on the console or



176


Error Message %C7600_SIP200_SPITX-3-EFC_ERR_SPA0: SPAstatus=[hex][chars] Explanation The egress data path device on the line card detected an error condition with the

extended flow control (EFC) bus interface. This condition could cause packets to drop. Recommended Action If this problem recurs, copy the message exactly as it appears on the console or









177





Error Message %C7600_SIP200_SPITX-3-EFCEVNT_ERR: [chars] Explanation The egress data path device on the line card detected an error while processing internal

extended flow-control events. This condition could cause a reduced packet rate. Recommended Action If this problem recurs, copy the message exactly as it appears on the console or


Error Message %C7600_SIP200_SPITX-3-EFC_QUEUE_STUCK: [chars] Explanation The egress data path device on the line card detected an error condition with the

Extended Flow Control Bus interface. This condition could cause packets to drop. Recommended Action If this problem recurs, copy the message exactly as it appears on the console or



178


Error Message %C7600_SIP200_SPITX-3-EFCSTAT_FAIL_SPA0: [chars] Explanation The egress SPI4.2 device on the line card detected an EFC status clock or

synchronization failure. This condition could cause packets to drop. Recommended Action If this problem recurs, copy the message exactly as it appears on the console or









179





Error Message %C7600_SIP200_SPITX-3-FCSTAT_FAIL_SPA0: [chars] Explanation The egress SPI4.2 device on the line card detected a SPI4.2 status clock or







180








Error Message %C7600_SIP200_SPITX-3-INITFAIL: Failed to configure the egress SPI4.2 device. Error = [hex] Explanation The egress SPI4.2 device on the line card could not be programmed or configured. This

indicates an internal hardware error. Recommended Action If this problem recurs, copy the message exactly as it appears on the console or



181


Error Message %C7600_SIP200_SPITX-3-INT_PERR_SPA0: IntMemPerr=[hex][chars] Explanation The egress SPI4.2 device on the line card detected an internal memory parity error. This

condition could cause packets to drop. Recommended Action If this problem recurs, copy the message exactly as it appears on the console or









182





Error Message %C7600_SIP200_SPITX-3-MISMATCH: Descriptor ring mismatch: expects [int] got [int] Explanation The egress SPI4.2 device on the line card returned a descriptor entry that did not match

what the line card CPU expected. This condition could cause packets to drop. Recommended Action If this problem recurs, copy the message exactly as it appears on the console or


Error Message %C7600_SIP200_SPITX-3-OVERRUN_DROP: SPI4 overrun drops packet for SPA [int], queue [int], count [int] Explanation While the egress SPI4.2 device on the line card sends an packet on the extended flow

controlled channel, it overruns the SPI4 channel but cannot queue it to the internal hold queue. This indicates an internal software error. Recommended Action If this problem recurs, copy the message exactly as it appears on the console or



183


Error Message %C7600_SIP200_SPITX-3-SPI4_ERR_SPA0: SPAstatus=[hex][chars] Explanation The egress SPI4.2 device on the line card detected an error condition with the SPI4.2

bus interface. This condition could cause packets to drop. Recommended Action If this problem recurs, copy the message exactly as it appears on the console or









184





Error Message %C7600_SIP200_SPITX-3-SRAM_ECCERR: EccSynd=[hex], Err1bit=[int], ErrMbit=[int], SecHalf=[int], SPA=[int], Ch=[int], Addr=[hex], DataHi=[hex], DataLo=[hex], DataEcc=[hex] Explanation The egress SPI4.2 device on the line card detected a a parity error in the egress packet

memory. This condition could cause packets to drop. Recommended Action If this problem recurs, copy the message exactly as it appears on the console or



185

System Messages C7600_SSC Messages

C7600_SSC Messages This section contains Services SPA Carrier Card (C7600_SSC) messages.

C7600_SSC-3 Error Message %C7600_SSC-3-BRDTYPE_INDEX_MISMATCH: [chars]: Board type ([dec]) and card index ([dec]) do not match Explanation A mismatch was detected between the card index and board type. The C7600-SSC-400

board type is 4 and the card index is 191. The C7600-SSC-600 board type is 5 and the card index is 224. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %C7600_SSC-3-DCM_FAIL: [chars]: [chars] FPGA module DCM Lock Failure, status:[hex] Explanation One or more of the Digital Clock Managers (DCMs) for the data path FPGAs failed to

lock. This indicates a hardware failure. Recommended Action Copy the message exactly as it appears on the console or in the system log.



186


Error Message %C7600_SSC-3-DP_COUNTERS: [chars]: Failed to create DP counter process. Explanation A process is initiated on bootup to monitor the counters of the data path FPGAs. There

was an error creating this process. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %C7600_SSC-3-DP_ERROR: [chars]: Bus Error initializing [chars] FPGA, addr: [hex]. Explanation This FPGA could not be initialized due to a bus error. This condition indicates a

hardware failure, possibly due to a failed FPD upgrade. Recommended Action Enter the show hw-module slot fpd command. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %C7600_SSC-3-DP_PROGRAMMING: [chars]: [chars] FPGA failed to program. Explanation This FPGA failed to program. This condition indicates a hardware failure, possibly due to a failed FPD upgrade. Recommended Action Enter the show hw-module slot fpd command. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


187


Error Message %C7600_SSC-3-DPRX_ERR: [chars]. [chars] Explanation There was an error receiving data from the SPA, possibly due to data corruption. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %C7600_SSC-3-DPTX_ERR: [chars]: [chars]. Explanation There was an error sending data to the SPA, possibly due to data corruption. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %C7600_SSC-3-DPTX_ERR_MECC: [chars]: [chars]. ERR addr register:[hex]. Explanation There was an error sending data to the SPA, possibly due to data corruption. Recommended Action If this message recurs, copy the message exactly as it appears on the console



188


Error Message %C7600_SSC-3-DPTX_ERR_SECC: [chars]: [chars]. Single bit error count:[hex], ECC ERR addr register:[hex]. Explanation A data corruption error that was automatically fixed was detected while sending data to

the SPA. Recommended Action No action is required if you see this message once. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %C7600_SSC-3-DPTX_QDR: [chars]: Error clearing QDR queue [dec]. Explanation One of the QDR queues did not flush completely. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %C7600_SSC-3-SINGLE_SPA_MODE: [chars]: Module will use only bay [dec]. Bay [dec] is shut. Explanation The 7600-SSC is in single SPA mode. Recommended Action No action is required.

Error Message %C7600_SSC-3-SSC_BAY_SHUT: [chars]: Bay [dec] is shutdown because [chars] is in single-spa-mode Explanation The specified bay is shut down. In single SPA mode, only one bay is active. Recommended Action Refer to the IPsec VPN SPA documentation for information about single SPA

mode.


189


Error Message %C7600_SSC-3-SW_ERROR: [chars]: [chars] Explanation This error is seen when there is a problem in internal software coding; it should not be

seen under normal operation. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %C7600_SSC-3-UNKNOWN_BRDTYPE: [chars]: SSC board type [dec] is not supported Explanation Board type does not belong to either C7600-SSC-600 or C7600-SSC-400. Recommended Action Copy the message exactly as it appears on the console or in the system log.


C7600_SSC-7 Error Message %C7600_SSC-7-DP_DISABLE: [chars]: [chars] FPGA is forced disabled. Explanation This FPGA has been disabled. Forced disabling is a debugging feature. Recommended Action No action is required.


190

System Messages C7600_SSC600 Messages

C7600_SSC600 Messages This section contains Services SPA Carrier Card (C7600_SSC600) messages.

C7600_SSC600-3 Error Message %C7600_SSC600-3-DCM_FAIL: [chars] FPGA module DCM Lock Failure, status:[hex] Explanation One or more of the Digital Clock Managers (DCM) for the data path FPGAs failed to

lock. This condition indicates a hardware failure. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %C7600_SSC600-3-DP_COUNTERS: Failed to create DP counter process. Explanation A process is initialized at bootup to monitor the counters of the data path FPGAs. There

was an error in creating this process. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %C7600_SSC600-3-DP_ERROR: Bus Error initializing [chars] FPGA, addr: [hex]. Explanation This FPGA could not be initialized because of a bus error. This condition indicates a

hardware failure, possibly due to a failed FPD upgrade. Recommended Action Enter the show hw-module slot fpd command to gather more information on

the specific nature of the condition. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will


191


supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %C7600_SSC600-3-DP_PROGRAMMING: [chars] FPGA failed to program. Explanation This FPGA failed to program. This condition indicates a hardware failure, possibly due to a failed FPD upgrade. Recommended Action Enter the show hw-module slot fpd command to gather more information on

the specific nature of the condition. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %C7600_SSC600-3-DPRX_ERR: [chars]. Explanation There was an error receiving data from the SPA, possibly due to data corruption. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %C7600_SSC600-3-DPTX_ERR: [chars]. Explanation There was an error sending data to the SPA, possibly due to data corruption. Recommended Action If this message recurs, copy the message exactly as it appears on the console

or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support


192



Error Message %C7600_SSC600-3-DPTX_QDR: Error clearing QDR queue [dec]. Explanation One of the QDR queues did not clear completely. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %C7600_SSC600-3-SINGLE_SPA_MODE: Module will use only bay [dec]. Bay [dec] is shut. Explanation The 7600-SSC-400 is in single SPA mode. Recommended Action This message is informational. No action is required.

Error Message %C7600_SSC600-3-SSC_BAY_SHUT: Bay [dec] is shutdown because 7600-SSC-400 is in single-spa-mode Explanation The specified bay is shut down. In single SPA mode, only one bay is active. Recommended Action Refer to the IPsec VPN SPA documentation for information about single SPA

mode.

Error Message %C7600_SSC600-3-SW_ERROR: NULL Explanation This condition occurs when there is a problem in internal software coding; it should not occur under normal operation. Recommended Action Copy the message exactly as it appears on the console or in the system log.



193

System Messages CALL_HOME Messages

C7600_SSC600-7 Error Message %C7600_SSC600-7-DP_DISABLE: [chars] FPGA is forced disabled. Explanation This FPGA has been disabled. Forced disabling is a debugging feature. Recommended Action No action is required.

CALL_HOME Messages This section contains Call Home messages.

CALL_HOME-3 Error Message %CALL_HOME-3-CLI_CMD_RUN_FAILED: No VTY connection available to run CLI command for event notification message (ERR [dec]) Explanation Call Home was unable to open a VTY connection to run CLI commands and collect

output for use in notification messages. Recommended Action Increase the number of configured VTY lines or change the Alert Group

subscriptions to make them more restrictive (to reduce the number of simultaneous event triggers).

Error Message [dec])

%CALL_HOME-3-HTTP_REQUEST_FAILED: Call-Home HTTP request failed (ERR

Explanation The Call Home HTTP message failed to send to an HTTPS server. Recommended Action Check whether you have configured a valid trustpoint certificate for secure

HTTP messages.

Error Message %CALL_HOME-3-MESSAGE_SIZE_OVER_LIMIT: XML message size over limit, failed to send call-home message. configured message size limit ([dec]) is less than current message minimum length required ([dec]). Explanation Unable to create the message because the message size exceeds the configured message

size limit. Recommended Action Increase the destination message size limit.

Error Message %CALL_HOME-3-REQUEST_MESSAGE_FAILED: call-home request message failed to send (ERR [dec], [chars]) Explanation An attempt to send a call-home request message has failed. Recommended Action Configure Call Home to send call-home request messages.


194

System Messages CALL_HOME Messages

Error Message %CALL_HOME-6-REQUEST_MESSAGE_SUCCEEDED: call-home request message succeeded Explanation A call-home request message was sent successfully. Recommended Action No action is required.

Error Message %CALL_HOME-3-SMTP_SEND_FAILED: Unable to send notification using all SMTP servers (ERR [dec], [chars]) Explanation Call Home was unable to send notification using any of the configured SMTP servers. Recommended Action Verify the configuration of the Call Home SMTP servers and ports used to

connect to the servers. Verify that the remote SMTP servers are reachable and that they are operating correctly.

CALL_HOME-4 Error Message %CALL_HOME-4-MESSAGE_IS_TRUNCATED: message size over limit, call-home message is truncated. configured message size limit ([dec]) is less than current message total length required ([dec]). Explanation The Call Home message is truncated because it exceeds the configured message size

limit. Recommended Action Increase the destination message size limit.

CALL_HOME-5 Error Message %CALL_HOME-5-HTTPS_NOT_SUPPORTED: This image version does not support HTTPS Explanation The configured message destination is a secure HTTP (HTTPS) URL, but this image does not support secure HTTP. Recommended Action Upgrade your system image to a crypto image, which supports secure HTTP.


195

System Messages CAMP Messages

CAMP Messages This section contains Cooperative Asymmetric Multiprocessing (CAMP) messages.

CAMP-3 Error Message %CAMP-3-MP_INIT_FAILURE: Second CPU initialization failed Explanation The module CPU unit has two CPU cores in it. The second CPU core did not initialize

successfully, so the module is operating with only one CPU core. Recommended Action Copy the message exactly as it appears on the console or in the system log.


CAPI_EC Messages This section contains card and EtherChannel limitation (CAPI_EC) messages.

CAPI_EC-4 Error Message %CAPI_EC-4-GROUP_RATE_LIMITED: Adding interfaces of the same port-group ([dec]-[dec]) on [chars] to an etherchannel will not increase the channel throughput! Explanation Because ports on the specified slot use oversubscription, the total throughput of the port

channel is limited by the port group. Recommended Action If more throughput is required, either use ports from a line card that does not

use oversubscription, or use ports from different line cards or port groupings on oversubscribed line cards. For example, if the line card has 48 ports in groups of 8, you can select ports 1, 9, 17, 25, 33, and 41 for the same port channel.


196

System Messages CARDMGR Messages

Error Message %CAPI_EC-4-RATE_LIMITED: Adding [chars] interfaces to an etherchannel will limit channel throughput to 1 Gbps! Explanation Because ports on the indicated card type use oversubscription, throughput of the port

channel is limited. Recommended Action If more throughput is required, either use ports from a line card that does not

use oversubscription, or use ports from different line cards or port-groupings on oversubscribed line cards. For example, if the line card has 48 ports in groups of eight, you can select ports 1, 9, 17, 25, 33, and 41 for the same port channel.

Error Message %CAPI_EC-4-SLOT_RATE_LIMITED: Adding interfaces on slot [dec] to an etherchannel will limit channel throughput to 1 Gbps! Explanation Because ports on the indicated slot use oversubscription, the total throughput of the port

channel is limited. Recommended Action If more throughput is required, either use ports from a line card that does not

use oversubscription, or use ports from different line cards or port-groupings on oversubscribed line cards. For example, if the line card has 48 ports in groups of eight, you can select ports 1, 9, 17, 25, 33, and 41 for the same port-channel.

CARDMGR Messages This section contains SIP 400 Card Manager (data plane) (CARDMGR) messages.

CARDMGR-2 Error Message %CARDMGR-2-ESF_DEV_ERROR: An error has occurred on [chars]: [chars] Explanation The ESF encountered an error during normal operation. Steps need to be taken to

resolve the problem and allow traffic through the SIP 400 line card. Recommended Action Copy the message exactly as it appears on the console or in the system log.



197


Error Message %CARDMGR-2-ESF_LOAD_FAIL: [chars] failed to load: [chars] Explanation The ESF could not be loaded because one of the steps in the startup sequence failed.

This ESF is now not operational, which stops the traffic through the SIP-400 line card. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CARDMGR-2-SPABUS_ERROR: A [chars] FSM SPA bus error has occurred in subslot [dec] Explanation An FSM SPA bus error occurred during normal operation. Recommended Action Copy the message exactly as it appears on the console or in the system log.


CARDMGR-4 Error Message %CARDMGR-4-ESF_DEV_RELOADED: The ESF microcode has automatically recovered from an internal inconsistency. Explanation An ESF internal inconsistency was detected during normal operation. The ESF

microcode was reloaded to resolve the inconsistency. Recommended Action No action is required unless this message appears multiple times. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


198


Error Message %CARDMGR-4-ESF_LOAD_WARN: [chars] microcode load: [chars] Explanation The ESF was loaded even though a potential problem exists. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CARDMGR-4-ESF_LOOPBACK_FAIL: ESF loopback packet test failed: tried [dec] sent [dec] received [dec] Explanation The ESF loopback packets sent after a microcode reload experienced excessive packet

loss. This condition is usually an indication that data traffic through this line card is impacted as well. Recommended Action Copy the message exactly as it appears on the console or in the system log.


CARDMGR-5 Error Message %CARDMGR-5-ESF_DEV_INFO: ESF internal inconsistency corrected on [chars]: [chars] Explanation An ESF internal inconsistency was detected and corrected during normal operation. Recommended Action No action is required unless this message appears multiple times. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


199

System Messages CAT6000_SSC Messages

Error Message %CARDMGR-5-ESF_UCODE_DONE: Microcode download complete for [chars], time elapsed [time-stamp] Explanation The ESF microcode was successfully downloaded and started. The forwarding engine

is now configured and operational. The time elapsed is measured from the ESF_UCODE_START message. Recommended Action This is a normal activity at Cisco IOS boot time or after a fatal ESF error

occurs. No action is necessary.

Error Message %CARDMGR-5-ESF_UCODE_START: Downloading microcode [chars] for [chars], version=[chars], [chars] Explanation The platform code was starting to download a particular ESF microcode image. Recommended Action This is a normal activity at Cisco IOS boot time or after a fatal ESF error

occurs. No action is necessary.

CAT6000_SSC Messages This section contain Services SPA Carrier Card (SSC) messages.

CAT6000_SSC-3 Error Message %CAT6000_SSC-3-BRDTYPE_INDEX_MISMATCH: [chars]: Board type ([dec]) and card index ([dec]) do not match Explanation A mismatch was detected between the card index and board type. For the

C7600-SSC-400, the board type is 4 and the card index is 191. For the C7600-SSC-600, the board type is 5 and the card index is 224. Recommended Action Copy the message exactly as it appears on the console or in the system log.



200


Error Message %CAT6000_SSC-3-DCM_FAIL: [chars]: [chars] FPGA module DCM Lock Failure, status:%08x Explanation One or more of the digital clock managers (DCM) for the data path FPGAs failed to

lock. This indicates a hardware failure. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CAT6000_SSC-3-DPRX_ERR: [chars]. [chars] Explanation An error occurred while receiving data from the SPA, possibly due to data corruption. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %CAT6000_SSC-3-DPTX_ERR: [chars]: [chars]. Explanation An error occurred while sending data to the SPA, possibly due to data corruption. Recommended Action If this message recurs, copy the message exactly as it appears on the console



201


Error Message %CAT6000_SSC-3-DPTX_ERR_MECC: [chars]: [chars]. ERR addr register:0x%08lx. Explanation An error occurred while sending data to the SPA, possibly due to data corruption. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %CAT6000_SSC-3-DPTX_ERR_SECC: [chars]: [chars]. Single bit error count:0x%08lx, ECC ERR addr register:0x%08lx. Explanation A data corruption error was detected and automatically fixed while sending data to the

SPA. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %CAT6000_SSC-3-DPTX_QDR: [chars]: Error clearing QDR queue [dec]. Explanation One of the QDR queues did not flush completely. Recommended Action If this message recurs, copy the message exactly as it appears on the console



202


Error Message %CAT6000_SSC-3-DP_COUNTERS: [chars]: Failed to create DP counter process. Explanation A process is spawned on bootup to monitor the counters of the data path (DP) FPGAs.

There was an error creating this process. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CAT6000_SSC-3-DP_ERROR: [chars]: Bus Error initializing [chars] FPGA, addr: 0x%08x. Explanation This FPGA could not be initialized due to a bus error. This condition indicates a

hardware failure, possibly due to a failed FPD upgrade. Recommended Action If this message recurs, copy the message exactly as it appears on the console

or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show hw-module slot fpd commands and your pertinent troubleshooting logs.

Error Message %CAT6000_SSC-3-DP_PROGRAMMING: [chars]: [chars] FPGA failed to program. Explanation This FPGA failed to program. This condition indicates a hardware failure, possibly due to a failed FPD upgrade. Recommended Action f this message recurs, copy the message exactly as it appears on the console or

in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show hw-module slot fpd commands and your pertinent troubleshooting logs.


203


Error Message %CAT6000_SSC-3-SINGLE_SPA_MODE: [chars]: Module will use only bay [dec]. Bay [dec] is shut. Explanation The 7600-SSC is in single SPA mode. Recommended Action No action is required.

Error Message %CAT6000_SSC-3-SSC_BAY_SHUT: [chars]: Bay [dec] is shutdown because [chars] is in single-spa-mode Explanation The specified bay is shut down. In single SPA mode, only one bay is active. Recommended Action Refer to the IPsec VPN SPA documentation for information about single SPA

mode.

Error Message %CAT6000_SSC-3-SW_ERROR: [chars]: [chars] Explanation This error indicates a problem in internal software coding. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CAT6000_SSC-3-UNKNOWN_BRDTYPE: [chars]: SSC board type [dec] is not supported Explanation The board type is not supported. Recommended Action Copy the message exactly as it appears on the console or in the system log.



204

System Messages CAT6000_SVC Messages

CAT6000_SSC-7 Error Message %CAT6000_SSC-7-DP_DISABLE: [chars]: [chars] FPGA is forced disabled. Explanation This FPGA has been forced disabled. This is a debugging feature. Recommended Action No action is required.

CAT6000_SVC Messages Error Message %CAT6000_SVC_APP_HW-0-DPFPGAINTFATALERR: [chars], hardware register offset [hex] value [hex] Explanation DPFPGA fatal error Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CAT6000_SVC_APP_HW-2-APP_PROC_ALERT: Service Application Processor alert: [chars] Explanation A hardware problem was detected on the Service Application Processor. Recommended Action Copy the message exactly as it appears on the console or in the system log.



205


Error Message %CAT6000_SVC_APP_HW-2-HW_INTERRUPT: Hardware interrupt for Device: [chars] Explanation A hardware interrupt occured on the Line card. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CAT6000_SVC_APP_HW-2-UNSUPPORTED_HW: Unsupported Hardware: [chars] Explanation Unsupported hardware was found on the Line card. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CAT6000_SVC_APP_HW-3-BAD_IFCOMTYPE: Bad ifcom message type=[int] Explanation A Trifecta module passed down a message that the RP software was not prepared to

handle. Recommended Action lcp-services

Error Message %CAT6000_SVC_APP_HW-3-DPFPGADRVFAIL: DPFPGA object driver [chars] failure Explanation DPFPGA object driver create or pll check or TSE and XAUIs bring-up or check all

blocks except GLOBAL and XAUIs or check global interrupt register or check XAUIs global status or check XAUIs global error status failure Recommended Action Copy the message exactly as it appears on the console or in the system log.



206



Error Message %CAT6000_SVC_APP_HW-3-DPFPGAHWFAIL: Hardware bring-up failure Explanation The DPFPGA manager failed to bring-up the hardware prior to constructing the device

object driver. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CAT6000_SVC_APP_HW-3-DPFPGAIMAGE: DPFPGA image [chars] error, IOFPGA config flash status register [hex] Explanation DPFPGA image download or CRC error, the actual hardware reason is stored in

IOFPGA config flash register Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CAT6000_SVC_APP_HW-3-DPFPGAINTERR: [chars], hardware register offset [hex] value [hex] Explanation DPFPGA error Recommended Action Copy the message exactly as it appears on the console or in the system log.



207



Error Message %CAT6000_SVC_APP_HW-3-DPFPGAMNGRFAIL: DPFPGA manager [chars] failure Explanation The DPFPGA manager create various processes failure or initialization failure Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CAT6000_SVC_APP_HW-3-DPFPGASEUERR: A [chars] occured on the DPFPGA. SEU_EMR_REG = [hex] Explanation DPFPGA error Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CAT6000_SVC_APP_HW-3-DPFPGATIMEOUT: DPFPGA [chars] timeout after [dec]ms Explanation DPFPGA init done or pll lock timeout during bring-up Recommended Action Copy the message exactly as it appears on the console or in the system log.



208


Error Message %CAT6000_SVC_APP_HW-3-IPCALLOCFAIL: Failed to allocate IPC buffer [chars] Explanation The Linecard failed to allocate a buffer for communication with the Route Processor

(Draco). Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CAT6000_SVC_APP_HW-3-IPCPORT: Failed to [chars] IPC port ’[chars]’, error [chars] Explanation The Linecard failed to create a port for communication with the Route Processor

(Draco). Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CAT6000_SVC_APP_HW-3-IPCSENDFAIL: Failed to send IPC message [chars] Explanation The Linecard failed to send a message to the Route Processor (Draco). Recommended Action Copy the message exactly as it appears on the console or in the system log.



209

System Messages CAT6000_TRIFECTA Messages

Error Message %CAT6000_SVC_APP_HW-3-SHMEMFAIL: Shared memory write time out after [dec]ms Explanation The DPFPGA manager failed to get into the critical section for update the statistics counters in the PCI shared memory Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CAT6000_SVC_APP_HW-6-APP_FPGAVER_MISMATCH: Module [dec]: [chars] Explanation Service application FPGA version mismatch. Recommended Action No action is required.

Error Message %CAT6000_SVC_APP_HW-6-APP_RESTART_REASON: [chars] : [chars] Explanation Service application restart reason. Recommended Action No action is required.

Error Message %CAT6000_SVC_APP_HW-6-APPONLINE: Service application in slot [int] is online. Explanation Service application has finished booting up and is online Recommended Action No action is required.

CAT6000_TRIFECTA Messages CAT6000_TRIFECTA-0 Error Message %CAT6000_TRIFECTA-0-DPFPGAINTFATALERR: [chars], hardware register offset [hex] value [hex] Explanation A DPFPGA fatal error has occurred. Recommended Action Copy the error message exactly as it appears on the console or in the system

log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support


210


command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

CAT6000_TRIFECTA-2 Error Message %CAT6000_TRIFECTA-2-APP_PROC_ALERT: Service Application Processor alert: [chars] Explanation A hardware problem was detected on the Service Application Processor. Recommended Action If this message recurs, copy the error message exactly as it appears on the


Error Message %CAT6000_TRIFECTA-2-HW_INTERRUPT: Hardware interrupt for Device: [chars]

Explanation A hardware interrupt occured on the line card. Recommended Action If this message recurs, copy the error message exactly as it appears on the


CAT6000_TRIFECTA-3 Error Message %CAT6000_TRIFECTA-3-BAD_IFCOMTYPE: Bad ifcom message type=[int] Explanation A Trifecta module passed down a message that the RP software was not prepared to

handle. Recommended Action If this message recurs, copy the error message exactly as it appears on the

console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the


211


Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message %CAT6000_TRIFECTA-3-DPFPGADRVFAIL: DPFPGA object driver [chars] failure Explanation DPFPGA object driver create or pll check or TSE and XAUIs bring-up or check all

blocks except GLOBAL and XAUIs or check global interrupt register or check XAUIs global status or check XAUIs global error status failure Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %CAT6000_TRIFECTA-3-DPFPGAHWFAIL: Hardware bring-up failure Explanation The DPFPGA manager failed to bring-up the hardware prior to construct the device

object driver Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %CAT6000_TRIFECTA-3-DPFPGAIMAGE: DPFPGA image [chars] error, IOFPGA config flash status register [hex] Explanation DPFPGA image download or CRC error, the actual hardware reason is stored in

IOFPGA config flash register Recommended Action Copy the error message exactly as it appears on the console or in the system



212


Error Message %CAT6000_TRIFECTA-3-DPFPGAINTERR: [chars], hardware register offset [hex] value [hex] Explanation A DPFPGA error has occurred. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %CAT6000_TRIFECTA-3-DPFPGAMNGRFAIL: DPFPGA manager [chars] failure Explanation The DPFPGA manager has created a processes failure or an initialization failure. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %CAT6000_TRIFECTA-3-DPFPGATIMEOUT: DPFPGA [chars] timeout after [dec]ms Explanation DPFPGA init done or pll lock timeout during bring-up Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %CAT6000_TRIFECTA-3-IPCALLOCFAIL: Failed to allocate IPC buffer [chars] Explanation The linecard failed to allocate a buffer for communication with the Route Processor

(Draco). Recommended Action Copy the error message exactly as it appears on the console or in the system



213



Error Message %CAT6000_TRIFECTA-3-IPCPORT: Failed to [chars] IPC port ’[chars]’, error [chars] Explanation The linecard failed to create a port for communication with the Route Processor

(Draco). Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %CAT6000_TRIFECTA-3-IPCSENDFAIL: Failed to send IPC message [chars] Explanation The linecard failed to send a message to the Route Processor (Draco). Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %CAT6000_TRIFECTA-3-SHMEMFAIL: Shared memory write time out after [dec]ms Explanation The DPFPGA manager failed to get into the critical section for update the statistics counters in the PCI shared memory. Recommended Action Copy the error message exactly as it appears on the console or in the system



214

System Messages CBUS Messages

CBUS Messages This section contain Cisco Bus Controller (CBUS) messages.

CBUS-3 Error Message %CBUS-3-CCBCMDFAIL3: Controller [dec], cmd ([dec] [hex], [hex], [hex]) failed ([hex]) Explanation A command control block (CCB) command sent from the system to an interface

processor failed to complete successfully. Recommended Action The system recovered by generating an error code for the requester. No action

is necessary.

Error Message %CBUS-3-CCBSEMINFO: CCB semaphore [chars] traceback Explanation Displays information about the sending and receiving of command control block (CCB)

semaphores. Recommended Action No action is required if the frequency of the message is not affecting the operation of the switch. Frequent messages may be the result of software bugs (CSCee82681, CSCin54713) in earlier Cisco IOS releases. If conditions warrant, upgrade to a later Cisco IOS release.

Error Message %CBUS-3-SRPRSET: Interface [chars], Error ([hex]) [chars] srp_reset() Explanation A command to reset an SRP interface was issued by the RSP, but the interface did not

respond to the command within the expected time delay. The delay is given for the processor to return the buffers that it has allocated and to perform any necessary cleanup. This condition may be caused by a large number of buffers that have been allocated by the interface due to either heavy traffic or a hardware problem with the interface. Recommended Action Verify that the card is properly seated. If this message recurs, copy the message



215

System Messages CCE_DP Messages

CCE_DP Messages This section contains Common Classification Engine Data Plane (CCE_DP) messages related to the application firewall for HTTP.

CCE_DP-4 Error Message %CCE_DP-4-CCE_DP_DYNAMIC_CLASS: Sig:[dec] Content type does not match the specified type - [chars] [chars] from %i:[dec] to %i:[dec] Explanation The HTTP message violates the content-type-verification application firewall

inspection rule. Recommended Action This message is informational only, but may indicate a security problem.

Error Message %CCE_DP-4-CCE_DP_ICMP: ICMP Classification Result Invalid Explanation The HTTP message violates the request-method application firewall inspection rule. Recommended Action This message is informational only, but may indicate a security problem.

Error Message %CCE_DP-4-CCE_DP_NAMED_DB: Sig:[dec] Content type not found - [chars] [chars] from %i:[dec] to %i:[dec] Explanation The HTTP message violates the content-type-verification application firewall


Error Message %CCE_DP-4-CCE_DP_PACKET_PATH: Sig:[dec] Content type: [chars] does not match the Accept-Type from %i:[dec] to %i:[dec] Explanation The HTTP message violates the content-type-verification application firewall


Error Message %CCE_DP-4-CCE_DP_POLICY: Sig:[dec] HTTP protocol violation detected [chars] [chars] from %i:[dec] to %i:[dec] Explanation The HTTP message violates the strict-http application firewall inspection rule. Recommended Action This message is informational only, but may indicate a security problem.


216

System Messages CCH323 Messages

Error Message %CCE_DP-4-CCE_DP_TARGET: content-length Explanation The HTTP message violates the content-length application firewall inspection rule. Recommended Action This message is informational only, but may indicate a security problem.

Error Message %CCE_DP-4-CCE_DP_TIMERS: Sig:[dec] Content size %lu out of range [chars] [chars] from %i:[dec] to %i:[dec] Explanation The HTTP message violates the content-type-verification application firewall


Error Message %CCE_DP-4-CCE_DP_UDP: UDP Classification Result Invalid Explanation The HTTP message violates the request-method application firewall inspection rule. Recommended Action This message is informational only, but may indicate a security problem.

Error Message %CCE_DP-4-CCE_DP_VFR: Fragment classification result invalid Explanation The HTTP message violates the max-uri-len application firewall inspection rule. Recommended Action This message is informational only, but may indicate a security problem.

Error Message %CCE_DP-4-CCE_DP_VTCP: Virtual VTCP Classification result invalid Explanation The HTTP message violates the max-hdr-len application firewall inspection rule. Recommended Action This message is informational only, but may indicate a security problem.

CCH323 Messages Error Message %CCH323-3-CANNOT_CREATE_CCB: [chars]: cannot create the H.323 ccb Tree Explanation Creation of the H.323 CCB Tree failed. The system memory pool may be exhausted. Recommended Action This can be a catastrophic error.


217

System Messages CE3 Messages

CE3 Messages Error Message %CE3-1-CONFIGURE: Failed to configure [dec] interfaces in bay [dec], shutting down bay Explanation The CE3 hardware failed. Some components on the board failed to initialize. Recommended Action Replace the CE3 port adapter.

CFGMGR Messages This section contains Configuration Manager (CFGMGR) messages.

CFGMGR-1 Error Message %CFGMGR-1-UNABLE_TO_SEND_RUN_CFG: unable to send running-cfg, bits: [hex], retrying... Explanation The system is attempting to push the running configuration to the slaves. Recommended Action No action is required.

Error Message %CFGMGR-1-UNABLE_TO_SEND_STARTUP_CFG: unable to send startup-cfg, bits: [hex], retrying... Explanation The system is attempting to push the startup configuration to the slaves. Recommended Action No action is required.

CFGMGR-3 Error Message %CFGMGR-3-ERROR_APPLYING_STARTUP_CFG: Error Applying Startup Config to Running Config Explanation The system encountered an error while automatically applying the startup configuration

to the running configuration. Recommended Action Copy the message exactly as it appears on the console or in the system log.



218

System Messages CFGMGR Messages


CFGMGR-4 Error Message %CFGMGR-4-SLAVE_WRITING_STARTUP_CFG: only master can do that Explanation An attempt to write to the startup configuration was made on a slave, but is allowed only

on the master. Recommended Action No action is required.

CFGMGR-6 Error Message %CFGMGR-6-APPLYING_RUNNING_CFG: as new master Explanation The new master is applying a backed-up running configuration. Recommended Action No action is required.

Error Message %CFGMGR-6-SPURIOUS_SLAVE_ADD: CFG MGR Recvd Spurious New Slave Notification: [int] Explanation Configuration Manager was notified about a slave that it already knows about. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %CFGMGR-6-UNABLE_TO_NVGEN_BUSY_RUNNING_CFG: config file busy, retrying... Explanation The master is temporarily unable to complete the nonvolatile generation process

(NVGEN) to construct the running configuration. Recommended Action No action is required.


219

System Messages CFIB Messages

Error Message

%CFGMGR-6-UNABLE_TO_NVGEN_RUNNING_CFG: config file too large...

Explanation The master is unable to complete the nonvolatile generation process (NVGEN) to

construct the running configuration because the configuration file is too large. Recommended Action Remove some configuration commands.

CFIB Messages This section contains Constellation Forwarding Information Base (CFIB) messages.

CFIB-3 Error Message %CFIB-3-CFIB_UNEXPECTED_OCE_CHAIN: Unexpected oce length obj:Unrecognized format ‘ %p’ type: [dec] Explanation The Output Chain Element(OCE) specified in the system message is invalid because it

has exceeded the maximum depth. One known cause is invalid static route configuration. Traffic for this path will be dropped. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %CFIB-3-REQ_VPN_MAPPER_IPV4_FAIL: CFIB vpn mapper request fails for ipv4 appid [chars] Explanation All vpn ids for ipv4 app are used Recommended Action Copy the error message exactly as it appears on the console or in the system



220

System Messages CFIB Messages

Error Message %CFIB-3-REQ_VPN_MAPPER_IPV6_FAIL: CFIB vpn mapper request fails for ipv6 appid in [chars] Explanation All vpn ids for ipv6 app are used. Recommended Action Copy the error message exactly as it appears on the console or in the system


CFIB-7 Error Message %CFIB-7-CFIB_ADJBASE: Failed to free adjacency base from hash table (entry not found) Explanation An error has occurred while attmepting to free an adjacency from a hash table. This

condition might be caused by an inconsistent use of hash key during creation of the adjacency hash table. This condition might cause a memory leak Recommended Action Copy the message exactly as it appears on the console or in the system log. To check memory usage over time, enter the show process memory command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %CFIB-7-CFIB_EXCEPTION: FIB TCAM exception, Some entries will be software switched Explanation Because there are no free memory blocks in the FIB TCAM, some switching will be

done in software rather than hardware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



221

System Messages CFIB_TUNNEL_RP Messages

Error Message %CFIB-7-END_CFIB_EXCEPTION: FIB TCAM exception cleared, all CEF entries will be hardware switched Explanation Because free memory blocks have become available in the FIB TCAM, switching will

be done in hardware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


CFIB_TUNNEL_RP Messages This section contains Constellation Forwarding Information Base (CFIB) messages.

CFIB_TUNNEL_RP-4 Error Message %CFIB_TUNNEL_RP-4-TUN_RECIR_FORCED: The current configuration of hardware and software requires MPLS tunnel recirculation to be enabled. ’mls mpls tunnel-recir’ has been added to the running configuration Explanation When the chassis contains a SIP-600 line card, and VRF forwarding is configured on a

tunnel interface, MPLS tunnel recirculation must be enabled to prevent the creation of corrupted packets from EARL. The mls mpls tunnel-recir command has been added to the running configuration automatically. Recommended Action No action is required.

CFM_CONST Messages This section contains Connectivity Fault Management (CFM) messages.

CFM_CONST-3 Error Message %CFM_CONST-3-AEB_ON_EC_UNSUPPORTED: CFM AEB mode is unsupported on etherchannels. Cannot set CFM AEB mode Explanation CFM AEB mode is unsupported on etherchannels. Recommended Action Set CFM AEB mode only on physical (unbundled) ports.


222

System Messages CFM_CONST Messages

Error Message %CFM_CONST-3-CFM_ON_SUPERVISOR_PORTS_DISABLED: CFM is enabled system wide except it’s disabled on supervisor ports due to spanning tree configuration. Explanation Unable to program all port ASIC MAC match registers on supervisor ports for CFM due

to hardware limitations on these ports. Continued with enabling CFM system-wide to allow coexistence with other protocols such such as PVST. Recommended Action System has handled this by disabling CFM on all supervisor ports. If this is

unacceptable configure STP mode to MST and re-enable CFM or disable CFM completely.

Error Message %CFM_CONST-3-CFM_ON_SUPERVISOR_PORTS_DISALLOWED: CFM is enabled system wide except on supervisor ports due to spanning tree configuration. Explanation Unable to program all port ASIC MAC match registers on supervisor ports for CFM due

to hardware limitations on these ports. Continued with enabling CFM system-wide to allow coexistence with other protocols such such as PVST. Recommended Action Administrator action may be required. Ensure no CFM traffic is presented to

any supervisor ports via configuration. If not possible configure STP mode to MST and re-enable CFM or disable CFM completely

Error Message %CFM_CONST-3-MAC_OPERATIONALLY_ERROR: The set MAC operationally action on interface [chars] has encountered an error. Explanation The set MAC operationally action failed and ended abnormally. Recommended Action No action is required.

Error Message %CFM_CONST-3-MATCH_REG_GLOBAL_RESERVE_FAILED: Unable to program port ASIC MAC match register on one or more slots. Cannot run CFM Explanation The Content Flow Monitor (CFM) attempted to reserve and program the port ASIC

MAC match registers, but there are insufficient match registers available. CFM cannot be run. Recommended Action To free MAC match registers, disable protocols that use the MAC match register. Protocols using port ASIC match registers can be viewed with the remote command switch show platform mrm info command.

Error Message %CFM_CONST-3-MATCH_REG_RESERVE_FAILED: Unable to reserve port ASIC MAC match register on slot [dec]. Cannot run CFM Explanation CFM attempted to reserve a port ASIC MAC match register for the slot indicated and

there is no register available. CFM cannot be run without support from all line cards. Recommended Action To free MAC match registers, disable protocols that use the MAC match register. Protocols using port ASIC match registers can be viewed with the remote command switch show platform mrm info command.


223

System Messages CFM_CONST Messages

Error Message %CFM_CONST-3-MATCH_REG_RESERVE_ON_SUPERVISOR_FAILED: Unable to program port ASIC MAC match register on supervisor slot [dec]. Cannot run CFM on supervisor ports Explanation CFM attempted to reserve a port ASIC MAC match register for the indicated

supervisors’ slot and there is no register available. CFM cannot run on supervisors ports. Recommended Action Protocols that use the MAC match register must be disabled to free MAC match registers. Protocols using port ASIC match registers can be can be viewed with remote command switch show platform mrm info.

Error Message %CFM_CONST-3-MST_SIMULATE_PVST_PLAT_ENABLED_FAILED: Unable to enable CFM when spanning tree mode is MST and PVST simulation is enabled on the platform Explanation CFM does not work along with MST plus PVST simulation. Recommended Action Disable PVST simualation on the platform.

Error Message %CFM_CONST-3-STP_MODE_CHANGE_NOT_ALLOWED: Unable to change STP mode while CFM is enabled Explanation STP modes PVST and rapid PVST are not compatible with CFM due to hardware

limitations. Recommended Action Either configure STP mode MST or disable CFM.

CFM_CONST-6 Error Message %CFM_CONST-6-CFM_ON_SUPERVISOR_PORTS_ENABLED: CFM is enabled on supervisor ports also due to spanning tree mode change to mst configuration. Explanation Able to program all port ASIC MAC match registers on supervisor ports for CFM due

to spanning tree mode change to mst configuration. Recommended Action No action is required.

Error Message %CFM_CONST-6-MAC_OPERATIONALLY: Interface [chars] is MAC operationally [chars]. Explanation The specified interface is MAC operationally up or down. Recommended Action No action is required.


224

System Messages CH-1 Messages

CH-1 Messages Error Message %CH-1-RM_STATE: _state_ attribute still available Explanation The _state_ attribute was still available in CH db re_auth recand it should have been

removed by now as part of the re_auth process. Recommended Action No action required.

.

CHARLOTTE Messages This section contains Dual OC-3 PoS port adapter (CHARLOTTE) messages.

CHARLOTTE-1 Error Message %CHARLOTTE-1-INITFAIL: Failed to initialize port [dec]. Explanation The dual OC-3 PoS port adapter failed to complete IDB initialization. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CHARLOTTE-1-PCIINITFAIL: PCI initialization failed. Explanation The dual OC-3 PoS port adapter failed to complete hardware initialization. Recommended Action Copy the message exactly as it appears on the console or in the system log.



225

System Messages CHKPT Messages

CHARLOTTE-3 Error Message %CHARLOTTE-3-INVALIDPCI: Device reported [hex] Explanation The dual OC-3 PoS port adapter hardware failed. The PCI device has an invalid ID. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CHARLOTTE-3-UNSUPPORTED: [chars] Explanation The dual OC-3 PoS port adapter hardware is not supported on the specified platform. Recommended Action Upgrade your system so that it supports the dual OC-3 PoS port adapter.

CHKPT Messages This section contains checkpointing (CHKPT) messages.

CHKPT-3 Error Message %CHKPT-3-INVALID_CALLBACK_ARG: Attempt to add a checkpointing client with an invalid [chars] argument Explanation An invalid argument was supplied to an internal application program interface (API).

As a result, the system state between one or more checkpointing clients might not be properly synchronized. The message output identifies the type of error that occurred. This failure is probably caused by a software error. Recommended Action Copy the message exactly as it appears on the console or in the system log.



226


Error Message %CHKPT-3-ISSU_MSG_NOT_COMPATIBLE: Checkpointing message type not compatible Explanation An error was detected when verifying the checkpointing message type compatibility

between checkpointing client peers. As a result, the system state between one or more checkpointing clients might not be properly synchronized. This failure is probably caused by a software error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CHKPT-3-ISSU_NEGO_FAILED: Checkpointing Facility failed to start ISSU negotiation with the peer ([chars]) Explanation The checkpointing facility was unable to start the ISSU negotiation successfully. The failure to start negotiation is a fatal error condition and is probably caused by a software error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CHKPT-3-ISSU_RCV_TRANSFORM_FAILED: Checkpointing receive message header transformaton failed ([chars]) Explanation An error was detected while performing a receive-level transformation on a

checkpointing message. As a result, the system state between one or more checkpointing clients might not be properly synchronized. The message output identifies the type of error that occurred. This failure is probably caused by a software error. Recommended Action Copy the message exactly as it appears on the console or in the system log.



227



Error Message %CHKPT-3-ISSU_XMIT_TRANSFORM_FAILED: Checkpointing transmit message header transformaton failed ([chars]) Explanation An error was detected while performing a transmit-level transformation on a

checkpointing message. As a result, the system state between one or more checkpointing clients might not be properly synchronized. The message output identifies the type of error that occurred. This failure is probably caused by a software error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CHKPT-3-RMI_CALLBACK: Checkpointing Facility encountered an error while processing a callback from the Resource Manager (RMI), [chars] Explanation The checkpointing facility registers with the Resource Manager (RMI) to receive status

notifications about resources (such as IPC) and uses them to throttle the sending of messages to the peer. The checkpointing facility encountered an error while processing a callback from RMI. This error is probably caused by a software error. Recommended Action Copy the message exactly as it appears on the console or in the system log.



228


Error Message %CHKPT-3-RMI_FAILED: Checkpointing Facility failed to register with the Resource Manager (RMI), [chars] Explanation The checkpointing facility registers with the Resource Manager (RMI) to get status

notifications about resources (such as IPC) and uses them to throttle the sending of messages to the peer. The checkpointing facility was unable to register itself with RMI and cannot throttle the sending of any messages. The system may still operate normally. This error is probably caused by a software error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CHKPT-3-SYSMGR_LOOKUP: Failed to get process Job ID from SysMgr Explanation The checkpointing facility was unable to get a job ID for an ION (run-time Modular

IOS) process from the System Manager. The job ID lookup is done when any ION checkpointing facility client first registers itself with the checkpoint facility. The error does not affect the checkpointing capabilities of the system. The job ID is used by the reset manager for tracking process restarts. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CHKPT-3-TRANSFORMFAILED: Checkpointing msg header transform failed ([dec]) Explanation A transform error related to check pointing occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



229



Error Message %CHKPT-3-TRANSMIT_FAILED: Checkpointing message transmission failure ([chars]) Explanation An error was detected when transmitting a checkpointing message between

checkpointing client peers. As a result, the system state between one or more checkpointing clients might not be properly synchronized. The failure is probably caused by a software error. The message output identifies the type of error that occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


CHKPT-4 Error Message %CHKPT-4-GET_BUFFER: Checkpointing ISSU session ([dec]) failed to get buffer Explanation The checkpointing ISSU session failed to get a buffer. Recommended Action Copy the message exactly as it appears on the console or in the system log.



230


Error Message %CHKPT-4-INIT: Checkpoint [chars] initialization failed in RF state ([chars]) Explanation The checkpointing standby initialization failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CHKPT-4-INVALID_STATE: Checkpoint State ([dec]) is invalid Explanation The checkpointing state is invalid. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CHKPT-4-MSG_SEND: Checkpointing ISSU session ([dec]) failed to send message Explanation The checkpointing ISSU session failed to send a negotiate message to the peer. Recommended Action Copy the message exactly as it appears on the console or in the system log.



231

System Messages CHOPIN Messages

Error Message %CHKPT-4-NOCLIENT: CF client is NULL, ([chars]) Explanation The checkpointing facility cannot send the message because the client is NULL. Recommended Action This is a warning message; no action is required.

Error Message %CHKPT-4-NOIPCPORT: IPC port is NULL, ([chars]) Explanation The checkpointing facility cannot send the message because the IPC port information is

NULL. Recommended Action This is a warning message; no action is required.

Error Message %CHKPT-4-NOMESSAGE: Message is NULL, ([chars]) Explanation The checkpointing facility cannot send the message because the message is NULL. Recommended Action This is a warning message; no action is required.

CHOPIN Messages This section contains Versatile Interface Processor (VIP) multichannel port adapter messages.

CHOPIN-2 Error Message %CHOPIN-2-TXBADVC: [chars], vc [dec] Explanation The VIP multichannel port adapter had a bad transmit VC. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech and show controllers vip slot tech-support commands and your pertinent troubleshooting logs.


232

System Messages CI Messages

CI Messages This section contains chassis interface (CI) messages and temperature alarms.

CI-0 Error Message %CI-0-SHUT_LC_CRITICALTEMP: Line cards shutdown as critical temperature exceeded [chars] Explanation The chassis temperature has exceeded a critical threshold and line cards have been shut

down. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CI-0-SHUT_LC_FANFAIL: Line cards are being shut on fan failure Explanation The chassis fan tray failure timer has expired and line cards have been shut down. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CI-0-SHUT_LC_FANGONE: Line cards are being shut as fan tray is missing Explanation The chassis fan missing timer has expired and line cards have been shut down. Recommended Action Copy the message exactly as it appears on the console or in the system log.



233



CI-1 Error Message %CI-1-CHASSISFAULTYSENSOR: Alarm: Chassis temperature sensor is faulty Explanation This error indicates that the chassis temperature sensor is faulty. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CI-1-CHASSISTEMPCRITICAL: Chassi temperature CRITICAL limit exceeded Explanation The system chassis temperature critical limit has been exceeded. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CI-1-CRITICALTEMP_LC_SHUT: Alarm: [chars], [chars], [chars], [chars], [chars] Explanation This error indicates that line cards have been shut down due to the core temperature

exceeding the critical threshold. Recommended Action Copy the message exactly as it appears on the console or in the system log.



234



Error Message %CI-1-FAN_FAILURE_LC_SHUT: Alarm: [chars], [chars], [chars], [chars], [chars] Explanation This error indicates that line cards have been shut down due to total fan failure or a missing fan tray. Recommended Action Copy the message exactly as it appears on the console or in the system log.


CI-3 Error Message %CI-3-CHASSISTEMPLOW: Chassis temperature too low Explanation The system chassis temperature is below -15 degrees Celsius. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CI-3-CHASSISTEMPMAJOR: Chassis temperature major limit exceeded Explanation The system chassis temperature major limit has been exceeded. Recommended Action Copy the message exactly as it appears on the console or in the system log.



235



Error Message %CI-3-CHASSISTEMPMINOR: Chassis temperature minor limit exceeded Explanation The system chassis temperature minor limit has been exceeded. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CI-3-MIB_ALM_SUBMIT: MIB alarm: [chars], [chars], [chars], [chars], [chars] Explanation An alarm message is contained in the MIB. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CI-3-PS_FAIL: Power supply module [dec] failure Explanation The specified power supply module has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



236


CI-4 Error Message %CI-4-MULTIPLE_FAN_FAILURE: [chars] [dec] [chars] [chars] Explanation When two or more of the fans in the chassis fan tray have failed or the fan try is missing, the line cards will be powered down after the user-configured timer interval. This warning message is generated one minute after the fans have failed or the fan tray is detected to be missing. Recommended Action Copy the message exactly as it appears on the console or in the system log.


CI-6 Error Message %CI-6-CHASSIS_SHUTDOWN: Chassis shutdown. Card/subcard not powered up Explanation The chassis is shut down. Line cards will not be powered up. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CI-6-FANOK: Fan tray module OK Explanation The chassis fan tray is operating normally. Recommended Action No action is required.


237


Error Message

%CI-6-LINECARD_SHUTDOWN: [chars]

Explanation When two or more of the fans in the chassis fan tray have failed or the fan tray is

missing, the line cards will be powered down after a user configured timer interval. This message is generated before shutting down line cards. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CI-6-PS_MISSING: Power supply module [dec] missing Explanation The specified power supply module is not present in the system Recommended Action No action is required.

Error Message

%CI-6-PSNORMAL: Power supply [int] normal

Explanation A failed power supply is working normally now. Recommended Action If the situation does not correspond with a normal operation of the system’s

power supplies, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %CI-6-PS_OK: Power supply module [dec] OK Explanation The specified power supply module is operating normally. Recommended Action No action is required.

Error Message %CI-6-PS_PRESENT: Power supply module [dec] present Explanation The specified power supply module is present in the system . Recommended Action No action is required.


238

System Messages CLNS Messages

CLNS Messages This section contains OSI Connectionless Network Service messages.

CLNS-3 Error Message %CLNS-3-CKSUMERR: [chars]: L[dec] LSP [chars] database checksum error, restarting Explanation A hardware or software error occurred. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %CLNS-3-IPLIST: ISIS: [chars] [hex], [IP_address] [IP_address] Explanation An internal error has occurred in the intermediate system-to-intermediate system (ISIS). Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CLNS-3-LSPLIST: ISIS: [chars] [hex], index [dec] Explanation An internal error has occurred in the intermediate system-to-intermediate system (ISIS). Recommended Action Copy the message exactly as it appears on the console or in the system log.



239

System Messages CLNS Messages

Error Message %CLNS-3-NSF_CP_INIT_ERR: Checkpoint initialization error ([chars]) Explanation An unrecoverable error occurred during initialization of the check point client. Recommended Action At this time there is no workaround. If this message recurs, copy the message

exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

CLNS-4 Error Message %CLNS-4-AUTH_FAIL: [chars]: [chars] authentication failed Explanation An ISIS packet (IIH, CSNP, PSNP, or LSP) was received and did not pass the

authentication check. Recommended Action If the error persists, check the originating router for matching authentication

mode and password.

Error Message CLNS-4-BADINTFCLNSMTU: [chars] Invalid interface clns MTU [dec] Explanation The interface MTU has become unusable while ISIS is running on the interface. This

condition may be temporary and recoverable. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CLNS-4-LSP_MAXSEQ: [chars][chars]: attempt to exceed LSP maximum sequence number for LSP [chars] Explanation An attempt was made to exceed the maximum sequence number for an LSP. Recommended Action Protocol will shut down for a period of (max-lsp-lifetime) + 1 minute. This is

an unprobable natural occurrence. Investigate to find the source of any out-of-order reception, generation, or incrementing of this LSP’s sequence number.


240

System Messages CLUE Messages

CLNS-5 Error Message %CLNS-5-NSF_ISSU_NEGO_FAIL: ISIS NSF cancelled - ISSU negotiation failed for NSF CISCO Explanation ISIS cancelled the nonstop forwarding (NSF) restart because ISSU negotiation failed in

Cisco mode. Recommended Action Enter the show issu negotiated version command and look for additional

information in the output of the command.

CLUE Messages This section contains Compact Local Unit Exchange (CLUE) messages.

CLUE-3 Error Message %CLUE-3-CHECKSUM_ERROR: CLUE record checksum error in record, id [dec], record starting address %#x, new checksum %#x, previous checksum %#x Explanation A Compact Local Unit Exchange (CLUE) record stored in the CLUE memory has a bad

checksum and cannot be accessed. The CLUE record was either modified by a CLUE client but not committed or it was modified by memory corruption. Recommended Action Internal CLUE client software will attempt to automatically correct the error.

If the error persists, reload the unit.

Error Message %CLUE-3-CLIENT_REGISTRY_FULL: Maximum of [dec] CLUE clients registered. Cannot register callback %#x Explanation No more Compact Local Unit Exchange (CLUE) clients can be registered because the

client registry for callback service is full. Unregistered CLUE clients will not be informed about CLUE service events such as CLUE service ready status or CLUE record corruptions. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show clue commands and your pertinent troubleshooting logs.


241


Error Message %CLUE-3-COMMIT_FAILED: CLUE cannot commit record, id [dec] Explanation The specified CLUE record was not committed in the CLUE storage memory, so the

CLUE record cannot be accessed. Either the CLUE record was not allocated by the CLUE client before committing or there was an error in the internal CLUE record index table. Recommended Action The internal CLUE client software will attempt to automatically correct the

error. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %CLUE-3-EOR_CORRUPT: CLUE record corruption in end of record field, record id [dec], record starting address %#x Explanation A CLUE record’s end of record delimiter was corrupted in the CLUE storage memory,

so the CLUE record cannot be accessed. The CLUE record was overwritten by the previous CLUE record or by a memory corruption. Recommended Action Internal CLUE client software will attempt to automatically correct the error.


Error Message %CLUE-3-INDEX_BUILD_FAIL: Failed to build CLUE internal record index due to [chars] Explanation CLUE could not build an internal record index table, so the CLUE service will not be

available and any data in the CLUE storage cannot be accessed. This failure can occur either when CLUE storage does not exist or when any CLUE record within the CLUE storage is corrupted. Recommended Action Internal CLUE client software will attempt to automatically correct the error.


Error Message %CLUE-3-INIT_ERROR: Failed to initialise the reserved memory for new CLUE context due to [chars] Explanation Reserved memory for the Compact Local Unit Exchange (CLUE) storage area was not

initialized due to the reason given. The CLUE storage area will not be available to provide any CLUE service. Recommended Action Copy the message exactly as it appears on the console or in the system log.



242


representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show clue commands and your pertinent troubleshooting logs.

Error Message %CLUE-3-INTERNAL_SW_ERROR: [chars] Explanation An internal Compact Local Unit Exchange (CLUE) software error was reported. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CLUE-3-INVALID_AREA: Either address %#x or size [dec] reserved for CLUE storage area is invalid Explanation An internal Compact Local Unit Exchange (CLUE) software error occurred. In order to

initialize and use the reserved area as a CLUE storage area, CLUE expected a non-zero reserved memory address and a non-zero reserved memory size. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CLUE-3-INVALID_REC_DATA_SIZE: CLUE record size [dec] is invalid to allocate CLUE record [dec] Explanation An internal Compact Local Unit Exchange (CLUE) software error occurred. When the

CLUE client requested to allocate the CLUE record, the record size was zero or was not the same as expected. The CLUE record was not allocated. Recommended Action Copy the message exactly as it appears on the console or in the system log.



243


representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show clue commands and your pertinent troubleshooting logs.

Error Message %CLUE-3-INVALID_REC_ID: Invalid CLUE record id [dec] has been received so CLUE cannot [chars] it Explanation An internal Compact Local Unit Exchange (CLUE) software error occurred. The

indicated action cannot be carried out on the specified CLUE record ID because the record ID is not valid. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CLUE-3-NOT_ENOUGH_CLUE_STORAGE: CLUE storage has not enough space to allocate record, id [dec] and data size [dec] Explanation An internal Compact Local Unit Exchange (CLUE) software error occurred. The CLUE

record was not allocated for the record ID because not enough space for CLUE storage was reserved or the CLUE storage contingency space was full. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CLUE-3-NOT_ENOUGH_MEMORY: [dec]-bytes of local memory has not enough space left to reserve [dec]-bytes of CLUE storage Explanation Insufficient local memory was available to reserve the required Compact Local Unit

Exchange (CLUE) storage space. Recommended Action Add more local memory.


244

System Messages CMP Messages

Error Message %CLUE-3-NO_SIGNATURE: CLUE cannot [chars] record, id [dec] Explanation The specified CLUE record was not serviced because CLUE storage was not available

or because the CLUE storage signature was invalid. Recommended Action The internal CLUE client software will attempt to automatically correct the error. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %CLUE-3-SOR_CORRUPT: CLUE record corruption in start of record field, record id [dec], record starting address %#x Explanation A CLUE record’s start of record delimiter was corrupted in the CLUE storage memory,

so the CLUE record cannot be accessed. The CLUE record was overwritten by the previous CLUE record or by a memory corruption. Recommended Action The internal CLUE client software will attempt to automatically correct the error. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

CMP Messages This section contains Cluster Membership Protocol (CMP) module messages.

CMP-5 Error Message %CMP-5-NBR_UPD_SIZE_TOO_BIG: Number of neighbors in neighbor update is [int], maximum number of neighbors allowed in neighbor update is [int] Explanation The number of cluster neighbors in the clustering neighbor update packet exceeds the

number of neighbors supported by the clustering module design. Recommended Action No action is required.


245

System Messages CNS Messages

CNS Messages This section contains Cisco Networking Services (CNS) messages.

CNS-3 Error Message %CNS-3-MEMORY: [chars] Explanation CNS subsystem has experienced a problem gettting the required memory to complete

this operation. Recommended Action Check system memory for other memory allocation errors and contact

Technical support for problem resolution. In the absence of IOS errors, upgrading the memory in the network device may be required.

Error Message %CNS-3-TRANSPORT: [chars] Explanation The CNS subsystem has experienced a problem contacting an external application. Recommended Action See specific message text for an indication of what the cause might be. Check

the network configuration and cables to make sure that the remote application is running and the address is accessible.

Error Message %CNS-3-WARNING: [chars] Explanation The CNS subsystem has encountered an unexpected condition while executing a set of

commands that did not cause a failure but suggests things did not go totally correctly. Recommended Action Check the error log for additional information. This is an informational

message and does not necessarily indicate that an error occurred.

Error Message %CNS-3-XML_SEMANTIC: [chars] Explanation The CNS subsystem has encountered an error while processing the XML encapsulation

of configuration command. Recommended Action The externally supplied XML has errors in it and connot be processed. See the specific message text for an indication of what the cause might be. This condition could possibly require that the command be checked and reissued from the server.


246

System Messages COLLECTION Messages

CNS-5 Error Message %CNS-5-CONFIG_SUCCESS: SUCCESSFUL_COMPLETION Explanation The configuration download has been applied successfully. Recommended Action No action is required.

CNS-6 Error Message %CNS-6-NO_EVENT_AGENT: CNS EVENT AGENT IS NOT CONFIGURED Explanation The CNS event agent is not configured. The event that was to be sent to it will be

dropped Recommended Action Configure the CNS event agent.

COLLECTION Messages This section contains COLLECTION messages.

COLLECTION-3 Error Message %COLLECTION-3-MODE_PROCESS_MISMATCH: Attempted to start a walk with incompatible mode and process (mode [chars] process [chars]) Explanation An internal error occurred in the collection process. Recommended Action Copy the message exactly as it appears on the console or in the system log.



247

System Messages COMMON_FIB Messages

Error Message %COLLECTION-3-PROC_INIT: Initialization of process [chars] failed, unable to [chars] Explanation An internal error occurred in the collection process. Recommended Action Copy the message exactly as it appears on the console or in the system log.


COMMON_FIB Messages This section contains CEF address Forwarding Information Base (FIB) messages.

COMMON_FIB-3 Error Message %COMMON_FIB-3-ACL_PBR_NAMETOOLONG: IPV6_SWSB_CTRL name length error, [chars] (acl_in [dec] ([dec]), acl_out [dec] ([dec]), pbr [dec] ([dec])) Explanation In an IPC eXternal Data Representation (XDR) message, the name of an IPv6 ACL or

an IPv6 policy-based route (PBR) was too long. To prevent buffer overrun errors, the names will not be used. Either the XDR message or an internal IPv6 FIB structure may be corrupted. Recommended Action Copy the message exactly as it appears on the console or in the system log.



248

System Messages COMMON_FIB Messages

COMMON_FIB-4 Error Message %COMMON_FIB-4-CHAIN_REMOVE_INCONS1: Attempting to remove [hex] but it has no prev [hex] Explanation COMMON_FIB_INTERNAL_ERROR. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %COMMON_FIB-4-CHAIN_REMOVE_INCONS2: Attempting to remove [hex] but prev [hex] points at [hex] instead Explanation COMMON_FIB_INTERNAL_ERROR. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %COMMON_FIB-4-CHAIN_REMOVE_INCONS3: Attempting to remove [hex] with next thinks its prev is [hex] Explanation COMMON_FIB_INTERNAL_ERROR. Recommended Action Copy the message exactly as it appears on the console or in the system log.



249

System Messages COMP_MATRIX Messages

COMMON_FIB-6 Error Message %COMMON_FIB-6-FIB_RECURSION_VIA_SELF: [chars] is found to resolve via itself during [chars] Explanation Cisco Express Forwarding (CEF) discovered that the routing for a prefix has recursive

paths that lead back to itself. CEF was forced to terminate an operation on the entry for that prefix. Recommended Action If the problem persists, use show commands to display the RIB and CEF information for the prefix in question and check its configuration.

COMP_MATRIX Messages This section contains ISSU Compatibility Matrix messages.

COMP_MATRIX-3 Error Message %COMP_MATRIX-3-PRST_VBL_DELETE: ISSU Compatibility Matrix was unable to delete a persistent variable from the [chars] system (rc = [dec]). Explanation The ISSU compatibility matrix was unable to delete a persistent variable. There is no way to determine whether ISSU image version compatibility checking should be enabled or disabled. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show persistent variable commands and your pertinent troubleshooting logs.

Error Message %COMP_MATRIX-3-PRST_VBL_GET: ISSU Compatibility Matrix was unable to read a persistent variable from the local system (rc = [dec]). Explanation The ISSU compatibility matrix was unable to access a persistent variable. There is no way to determine whether ISSU image version compatibility checking should be enabled or disabled. Recommended Action Copy the message exactly as it appears on the console or in the system log.



250

System Messages COMP_MATRIX Messages

open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show persistent variable commands and your pertinent troubleshooting logs.

Error Message %COMP_MATRIX-3-PRST_VBL_WRITE: ISSU Compatibility Matrix was unable to write to persistent variables on the [chars] system (rc = [dec]). Explanation The ISSU compatibility matrix was unable to write a persistent variable. There is no way to determine whether ISSU image version compatibility checking should be enabled or disabled. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show persistent variable commands and your pertinent troubleshooting logs.

COMP_MATRIX-4 Error Message %COMP_MATRIX-4-DISABLED: Compatibility Matrix has been disabled. No image compatibility checking will be done. Explanation The ISSU compatibility matrix check has been disabled by the no service

image-version compatibility configuration command. When the standby comes up, no image compatibility checking will be done. The system will enter SSO redundancy mode even if the active and standby supervisors are running different images. Recommended Action If you require ISSU compatibility matrix checking, enter the service

image-version compatibility command.


251

System Messages CONST_BOOT Messages

CONST_BOOT Messages This section contains Constellation boot messages.

CONST_BOOT-3 Error Message %CONST_BOOT-3-QUEUE_CLEANUP: Could not clean up reload netboot buffer after error Explanation The error processing encountered problems trying to free buffers while attempting to

clean up the allocated buffer for reload netboot. Recommended Action Copy the message exactly as it appears on the console or in the system log.


CONST_DIAG Messages This section contains Online Diagnostics (CONST_DIAG) messages.

CONST_DIAG-2 Error Message %CONST_DIAG-2-DIAG_SW_LPBK_TEST_MAJ: Module [[dec]/[dec]]: TestMgmtPortsLoopback detected a major error for port [dec] Explanation The module failed the loopback test. The module will be power cycled. Recommended Action Re-run the test with the NO RESET option after resetting the module. If it fails

again with the same error message, copy the message exactly as it appears. Include the system configuration along with any other relevant information. Contact your technical support representative for assistance.


252

System Messages CONST_DIAG Messages

Error Message %CONST_DIAG-2-HM_FAB_SWOVER: Fabric card switchover due to unrecoverable errors, Reason: Failed [chars] Explanation The fabric module has switched over because of unrecoverable error. The failure is

specified in the message. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CONST_DIAG-2-HM_LC_CRSH: Module [dec] crashed due to unrecoverable errors, Reason: Failed [chars] Explanation The system detected an unrecoverable error that caused the specified module to fail. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CONST_DIAG-2-HM_MOD_RESET: Resetting Module [dec] for software recovery, Reason: Failed [chars] Explanation The system detected an unrecoverable error that caused the specified module to reset. Recommended Action Copy the message exactly as it appears on the console or in the system log.



253


Error Message %CONST_DIAG-2-HM_SUP_CRSH: Standby supervisor crashed due to unrecoverable errors, Reason: Failed [chars] Explanation The system detected an unrecoverable error that caused the redundant supervisor engine

to fail. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CONST_DIAG-2-HM_SUP_CRSH: Supervisor crashed due to unrecoverable errors, Reason: Failed [chars] Explanation The supervisor engine has halted or restarted due to unrecoverable errors. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CONST_DIAG-2-HM_SUP_SWOVER: Supervisor card switchover due to unrecoverable errors, Reason: Failed [chars] Explanation The system detected an unrecoverable error that caused this supervisor engine

switchover. Recommended Action Copy the message exactly as it appears on the console or in the system log.



254


Error Message %CONST_DIAG-2-HM_TEST_FAIL: Module [dec] [chars] consecutive failure count:[dec] Explanation The system detected an unrecoverable error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CONST_DIAG-2-HM_TEST_WARNING: Sup switchover will occur after [dec] consecutive failures Explanation The system detected an unrecoverable error. A supervisor engine switchover will occur after the specified number of consecutive failures. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CONST_DIAG-2-MOD_PWR_DOWN: [chars] is powering down. Reason: Failed [chars] Explanation The module will power down due to the detection of an unrecoverable error. Recommended Action Copy the message exactly as it appears on the console or in the system log.



255


Error Message %CONST_DIAG-2-MOD_RESET_AFTER_DISRUPTIVE_DIAG: The following action is required after disruptive diagnostic test: ******************************************************************* * WARNING: Please reset [chars] prior to normal use ******************************************************************* Explanation You must reset the module after a disruptive diagnostic test. Recommended Action Copy the message exactly as it appears on the console or in the system log.


CONST_DIAG-3 Error Message %CONST_DIAG-3-BOOTUP_TEST_FAIL: [chars]: [chars] failed [chars] Recommended Action The indicated test failed during bootup diagnostics. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CONST_DIAG-3-DIAG_FIB_TCAM_TEST: Fib Tcam test: Missed at address [hex], device #[dec], HRR = [hex], lookup value = [hex]-[hex] Explanation The FIB TCAM device might not be functional because the test failed to get a response

at the reported address and look-up value. Recommended Action Rerun the test with the NO RESET option after resetting the module. If the test

fails again at the same address, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support


256



Error Message %CONST_DIAG-3-DIAG_FW_TEST_CARD_DOWN: Failed to disable module [dec] Explanation The module could not be powered down after firmware diagnostics failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CONST_DIAG-3-DIAG_FW_TEST_CARD_RESET: Failed to reset module [dec] Explanation The module could not be reset after firmware diagnostics failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CONST_DIAG-3-DIAG_TEST_PORT_SKIP: Module [dec] [chars] skipped multiple ports due to high traffic (Traffic=[dec]%) Explanation Online diagnostics did not take place on multiple ports in the specified module because

of high traffic volume. Recommended Action No action is required.

Error Message %CONST_DIAG-3-DIAG_TEST_SKIP: Module [dec] [chars] skipped due to high traffic (Traffic=[dec]%) Explanation Online diagnostics were not performed on the specified module because of high traffic

volume. Recommended Action No action is required.


257


Error Message %CONST_DIAG-3-HM_ALL_PORT_ERR: All ports on module [dec] failed [chars]. Explanation The data paths that correspond to all ports of the module have failed. Recommended Action Check your network configuration for spanning tree loops, excessive flooding,

and other related conditions. Reset the line card to see if the problem resolves itself. If the condition persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %CONST_DIAG-3-HM_CHAN_ERR: All ports in channel [dec] on module [dec] failed [chars]. Disabled the channel. Explanation The data path that corresponds to the channel has failed. All ports that are part of the

channel are put into errdisable state. Recommended Action Check your network configuration for spanning tree loops, excessive flooding,

and other related conditions. Reset the line card to see if the problem resolves itself. If the condition persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %CONST_DIAG-3-HM_CONFIG_FAIL: [chars] failed in health monitoring configuration (error code [dec]) Explanation The system has detected an unrecoverable error. Recommended Action Contact your Cisco technical support representative.

Error Message %CONST_DIAG-3-HM_FCI_0_STUCK: Flow control stuck at 0 error on module [dec]! Explanation The signal LDBUS_FCI_L0 is stuck on active-low. The line card is powered down. Recommended Action Copy the message exactly as it appears on the console or in the system log.



258



Error Message %CONST_DIAG-3-HM_PORT_ERR: Port [dec] on module [dec] failed [dec] consecutive times. Disabling the port. Explanation The data path that corresponds to the port has failed. The port is put into errdisable state. Recommended Action Reset the line card to see if the problem resolves itself. If the condition persists,

copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %CONST_DIAG-3-HM_PORT_ERR_3X: Port [dec] on module [dec] is not allowed to clear err-disabled state due to 3rd series of [chars] failures. Port will remain in err-disabled state. Explanation The data path that corresponds to the port has failed. The port is put into a disabled state. Recommended Action Reset the line card to see if the problem resolves itself. If the condition persists,


Error Message %CONST_DIAG-3-LTL_PORT_ERR: Port [dec] on module [dec] failed [chars]. Disabling the port. Explanation The datapath corresponding to the port is bad. The port is put into err-disabled state. Recommended Action No action required.


259


Error Message %CONST_DIAG-3-SUP_FAILURE: [chars] supervisor has [chars] online diagnostic failure [hex]: [chars] Explanation The specified supervisor engine has experienced an online diagnostic failure. Recommended Action Depending on whether failure is minor, major, or critical, the supervisor engine

will display a warning message during the boot process, or the supervisor engine will fail and go into ROM monitor mode.

CONST_DIAG-4 Error Message %CONST_DIAG-4-DIAG_DETECT_FABRIC_CHAN_LOW_RATE: Module [dec] fabric channel [dec] [chars] is low ([hex] instead of [hex]). Explanation The diagnostic test has detected a fabric low buffer rate for the fabric channel. Recommended Action Flow control is occurring in the system. Analyze the system traffic, and remove

the traffic source that causes flow control. Enter the show fabric utilization command to determine the overall traffic pattern.

Error Message %CONST_DIAG-4-DIAG_RESET_WARNING: Please reset module [dec] prior to normal use Explanation The specified module must be reset after the diagnostic test. Recommended Action Reset the specified module after the diagnostic test.

Error Message %CONST_DIAG-4-DIAG_SUGGEST_ACTION_DUE_TO_FABRIC_CHAN_FLOW_CONTROL: Flow control is occurring in the system. Analyze the system traffic and remove the traffic source that causes flow control. Explanation This message appears when a diagnostic test has detected a low buffer rate in the switch

fabric. Recommended Action Flow control is occurring in the system. Analyze the system traffic and remove

the traffic source that causes flow control. Enter the show fabric utilization command to check the overall traffic pattern.

Error Message %CONST_DIAG-4-DIAG_SUGGEST_ACTION_DUE_TO_FABRIC_CHAN_LOW_RATE: Flow control is occurring in the system. Analyze the system traffic and remove the traffic source that causes flow control. Explanation The diagnostic test has detected a low buffer rate for the fabric channel. Flow control is

occurring in the system. Recommended Action Analyze the system traffic and remove the traffic source that is causing flow

control. Enter the show fabric utilization command to determine the overall traffic pattern.


260


Error Message %CONST_DIAG-4-ERROR_COUNTER_WARNING: Module [dec] Error counter exceeds threshold, system operation continue. Explanation The TestErrorCounterMonitor has detected that an error counter in the specified module

has exceeded a threshold. Specific data about the error counter will be sent in a separate system message. The TestErrorCounterMonitor is a non-disruptive health-monitoring background process that periodically polls the error counters and interrupt counters of each line card or supervisor module in the system. Recommended Action To determine the cause of the error, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show module, show logging, and show diagnostic events commands, the contents of the CONST_DIAG-4-ERROR_COUNTER_DATA system message, and your pertinent troubleshooting logs.

Error Message %CONST_DIAG-4-ERROR_COUNTER_DATA: ID:[dec] IN:[dec] PO:[dec] RE:[dec] RM:[dec] DV:[dec] EG:[dec] CF:[dec] TF:[dec] Explanation The TestErrorCounterMonitor has detected that an error counter in the specified module

has exceeded a threshold. This message contains specific data about the error counter, including the ASIC and register of the counter, and the error count. Recommended Action To determine the cause of the error, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show module, show logging, and show diagnostic events commands and your pertinent troubleshooting logs.

CONST_DIAG-6 Error Message %CONST_DIAG-6-DIAG_ONDEMAND_NOT_SUPPORTED: [chars] is not supported on-demand for module [dec] Explanation The specified on-demand online diagnostics are not supported on the specified module. Recommended Action This message is informational. No action is required.


261


Error Message %CONST_DIAG-6-DIAG_PORT_SKIPPED: Module [dec] port [dec] is skipped in [chars] due to: [chars]. Explanation The specified diagnostic test was not performed on this port because the port loopback could not be configured at test time. Recommended Action No action is required. Although the test cannot be run at this time, this message

does not indicate a problem.

Error Message %CONST_DIAG-6-DIAG_RERUN_RESET: Resetting Module [dec] to re-run [chars] diagnostic Explanation The system is resetting the module to rerun diagnostics. Recommended Action No action is required. The system is working properly.

Error Message %CONST_DIAG-6-DIAG_SW_LPBK_TEST_INFO: Module [[dec]/[dec]]: TestMgmtPortsLoopback detected a minor error for port [dec] Explanation The module failed the loopback test. The is an informational message.

Error Message Re-run the test with the NO RESET option after resetting the module. If it fails again with the same error message, copy the message exactly as it appears. Include the system configuration along with any other relevant information. Contact your technical support representative for assistance.%CONST_DIAG-6-HM_MESSAGE: High traffic/CPU util seen on Module [dec] [SP=[dec]%,RP=[dec]%,Traffic=[dec]%] Explanation The system bypassed the health-monitoring test on the specified module because of high

utilization of system resources. Recommended Action This message is informational. No action is required.

Error Message %CONST_DIAG-6-HM_TEST_INFO: CPU util(5sec): SP=[dec]% RP=[dec]% Traffic=[dec]% netint_thr_active[[dec]], Tx_Rate[[dec]], Rx_Rate[[dec]] Explanation This message provides system resource information during an event. Recommended Action This message is informational. No action is required.

Error Message %CONST_DIAG-6-HM_TEST_RECOVERED: Module [dec] [chars] recovered after [dec] consecutive failure(s) Explanation The health-monitoring test recovered from transient failure on the specified module. Recommended Action This message is informational. No action is required.


262


Error Message %CONST_DIAG-6-HM_TEST_SP_INFO: [chars][[dec]]: last_busy_percent[[dec]%], Tx_Rate[[dec]], Rx_Rate[[dec]] Explanation This message provides system resource information during an event. Recommended Action This message is informational. No action is required.

Error Message %CONST_DIAG-6-RW_ENGINE_DROP_INFO: Rewrite engine over-subscription detected for module [dec] channel [dec]: At least [int] packets were dropped. Explanation Rewrite engine over-subscription detected. Recommended Action No action required.


263



264

CONST_V6 Messages

CONST_V6 Messages This section contains IP version 6 (CONST_V6) messages.

CONST_V6-5 Error Message %CONST_V6-5-FIB_EXCEP_OFF: Protocol IPv6 recovered from FIB exception Explanation The IPv6 CEF table successfully reloaded to the hardware FIB TCAM. All IPv6 packets

will be switched by the hardware. Recommended Action No action is required.

Error Message %CONST_V6-5-FIB_EXCEP_ON: Failed to insert an IPv6 prefix in hardware FIB TCAM Explanation The switch failed to insert an IPv6 entry into the hardware FIB TCAM because the total number of software-forwarding entries exceeded the hardware FIB TCAM limit. Some IPv6 packets might be switched by the software. Recommended Action Copy the message exactly as it appears on the console or in the system log.


CONTROLLER Messages This section contains controller messages.

Error Message %CONTROLLER-5-DOWNDETAIL: Controller [chars], changed state to [chars] due to [chars] Explanation A configurable controller has changed its state. Recommended Action This is an informational message only. No action is required.


257

CONTROLLER Messages

Error Message %CONTROLLER-3-INBAND_BAD_PAK: Possibly un-encapsulated packet passed to Mistral: int [chars], type [int], stat [hex], flags [hex], size [dec], offset [dec], total [int] Explanation A badly encapsulated packet was received from the process level. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %CONTROLLER-3-INBAND_INVALID_IBL_FILL: Attempting to issue IBL Fill when IBL is void of packet. Explanation The input buffer logic (IBL) did not contain any packets. An IBL fill operation was

attempted. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CONTROLLER-3-MISTRAL_INVALID_OBL_PAGE_REQUEST: Invalid request for free ’Output Buffer Logic’ pages = [dec] Explanation There was an invalid output buffer logic (OBL) page request. The maximum number of

OBL pages has been set to its maximum value of 40 and processing will continue through the normal switching path. Recommended Action Copy the message exactly as it appears on the console or in the system log.



258

CONTROLLER Messages

Error Message %CONTROLLER-3-NO_GIG_SYNC: Inband Gig interface not syncronized, status [hex] Explanation The hardware for transmitting and receiving packets from and to the router is not

functioning properly. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CONTROLLER-3-NO_OBL_TO_INBAND: The System Controller OBL to INBAND semaphore not obtained. Explanation The system controller output buffer logic (OBL) to inband semaphore could not be

properly obtained. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CONTROLLER-3-NO_SYSTEM_CONTROLLER_INIT_STATUS: The System Controller init status of 0xf not obtained, status [hex] Explanation The system controller initialization status could not be properly obtained. Recommended Action Copy the message exactly as it appears on the console or in the system log.



259

CONTROLLER Messages

Error Message %CONTROLLER-3-NOT_IDLE: Receive path not idle after the reset. Explanation The receiving hardware is not idle after it has been reset. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CONTROLLER-3-SYSTEM_CONTROLLER_BUSY: The System Controller could not finish [chars] operation in time. Explanation The system controller failed in completing its operation. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CONTROLLER-3-TOOBIG: An attempt made to send giant packet on [chars] ([dec] bytes from [hex], max allowed [dec]) Explanation An attempt was made to send an oversized packet. Recommended Action Copy the message exactly as it appears on the console or in the system log.



260

COPTMONMIB Messages

Error Message %CONTROLLER-5-UPDOWN_BERT: BERT test [chars] on Controller [chars]. Forced state to [chars] Explanation A configurable controller has changed its state. Recommended Action This is an informational message only. No action is required. Recommended Action Copy the message exactly as it appears on the console or in the system log.


COPTMONMIB Messages This section contains Cisco Optical Monitoring MIB (COPTMINMIB) messages.

COPTMONMIB-3 Error Message %COPTMONMIB-3-ENTRYADDFAILED: Registering of the interface with ifIndex [dec] to local data structure failed Explanation An attempt to make an entry for the registering interface failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %COPTMONMIB-3-ENTRYPRESENT: An entry is already present for the registering interface with ifIndex [dec] Explanation An entry in the OPTICAL MONITORING MIB already exists for the registering

interface. Recommended Action No action is required.


261

Cougar Messages

Cougar Messages This section contains Cougar line card messages.

Error Message %COUGAR_EHSA-3-NCLK_FUNCVER_MISMATCH: Mismatch in the Network Clock Module Functional Version number. The Functional Version of the Network clock module in the Primary = [dec].[dec] Explanation This may lead to loss of Network Clocking functionality if and when a CPU switchover

occurs. The system is now running CONDITIONALLY REDUNDANT - subject to the above mentioned restriction

Error Message No action required. %COUGAR_EHSA-3-TWO_PRIM_DETECT: Other RP has declared PRIMARY, two primaries active in chassis. This RP will now crash to avoid this condition. Explanation N/A Recommended Action No action required.

CPU_INTF_FPGA Messages This section contains CPU interface field programmable gate array (FPGA) messages.

CPU_INTF_FPGA-2 Error Message %CPU_INTF_FPGA-2-DEV_INIT_FAILURE: The CPU Interface FPGA initialization failed due to [chars] Explanation The CPU interface FPGA initialization was not successful due to a hardware problem. This condition will cause packet drops. Recommended Action Copy the message exactly as it appears on the console or in the system log.



262

CPU_INTF_FPGA Messages

Error Message %CPU_INTF_FPGA-2-INT: [chars] Explanation A fatal interrupt has occurred and the device has been reinitialized. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CPU_INTF_FPGA-2-NULL_DEV_OBJECT: The CPU Interface FPGA device object pointer is set to NULL Explanation The memory location of the CPU Interface FPGA device object is invalid. The CPU

interface FPGA operation is disabled and the device interrupt is now masked. Recommended Action Copy the message exactly as it appears on the console or in the system log.


CPU_INTF_FPGA-3 Error Message %CPU_INTF_FPGA-3-DEV_UNPAUSE_FAIL: Status register is [hex] Explanation An attempt to unpause traffic from the CPU interface FPGA to the backplane interface ASIC has timed out. This failure may lead to traffic disruption. Recommended Action If normal traffic processing does not resume, copy the message exactly as it



263

CPU_INTF_FPGA Messages

Error Message %CPU_INTF_FPGA-3-QUEUE_ALLOC_FAILED: Failed to allocate queue in the CPU Interface FPGA for SPA in bay ([dec]) Explanation Failed to allocate a queue for the SPA in the given bay. This failure may lead to traffic

disruption. Recommended Action If normal traffic processing does not resume, copy the message exactly as it


CPU_INTF_FPGA-4 Error Message %CPU_INTF_FPGA-4-DEV_WARN_INT: [chars] Explanation The CPU interface FPGA received a nonfatal interrupt. This event should not affect the normal operation of the device. Recommended Action No action is required.

CPU_INTF_FPGA-5 Error Message %CPU_INTF_FPGA-5-PAUSE_FAIL: FPGA status register is [hex] Explanation An attempt to pause traffic from the CPU interface FPGA to the backplane interface

ASIC has timed out. This event may lead to traffic disruption. Recommended Action If normal traffic processing does not resume, copy the message exactly as it



264

CPU_MONITOR Messages

CPU_MONITOR Messages This section contains CPU monitor (CPU_MONITOR) messages.

CPU_MONITOR-2 Error Message %CPU_MONITOR-2-NOT_RUNNING: CPU_MONITOR messages have not been sent for [dec] seconds [[chars] [dec]%/[dec]% ([time-stamp] [dec]%/[dec]%)] [[chars] [time-stamp]] [[chars] [time-stamp]] [[chars] [time-stamp]] Explanation CPU monitor messages have not been detected for a significant amount of time. A

timeout is likely to occur soon, which will reset the system. Recommended Action No action is required.

Error Message %CPU_MONITOR-2-NOT_RUNNING_TB: CPU_MONITOR traceback: [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] Explanation This message provides additional debugging information for the NOT_RUNNING message. The message displays the traceback of the interrupted functions. Recommended Action No action is required.

CPU_MONITOR-3 Error Message %CPU_MONITOR-3-KERNEL_OPERATION: CPU_MONITOR kernel operation failed: [chars] Explanation A CPU_MONITOR kernel operation required to identify supect threads has failed. Recommended Action This is an informational message only. No action is required.

Error Message %CPU_MONITOR-3-PEER_EXCEPTION: CPU_MONITOR peer has failed due to exception , resetting [[dec]/[dec]] Explanation The CPU monitor messages failed on the peer processor. The system is no longer

operational. Recommended Action No action is required.

Error Message %CPU_MONITOR-3-PEER_FAILED: CPU_MONITOR peer process has failed to receive heartbeats, reset by [%d/%d] Explanation The CPU monitor messages have failed on the peer process and the system is no longer

operational. Recommended Action No action is required.


265

CRYPTO Messages

Error Message %CPU_MONITOR-3-TIMED_OUT: CPU_MONITOR messages have failed, resetting %s [%d/%d] Explanation The CPU monitor messages failed and the system is no longer operational. Recommended Action No action is required.

CPU_MONITOR-6 Error Message %CPU_MONITOR-6-NOT_HEARD: CPU_MONITOR messages have not been heard for %d seconds [%d/%d] Explanation CPU monitor messages have not been detected for a significant amount of time. [dec]

is the number of seconds. A timeout is likely to occur soon, which will reset the system. This error can be caused by a badly seated module or by high traffic in the EOBC channel. Recommended Action Verify that all modules are seated properly in the chassis. Pull out the module

mentioned in the message and inspect the backplane and module for bent pins or hardware damage. If the message persists after reseating all the modules, a hardware problem may exist, such as a defective module or chassis.

CRYPTO Messages This section contains encryption (CRYPTO) messages.

CRYPTO-3 Error Message %CRYPTO-3-CONNID_ALLOC_FAIL: Crypto engine failed to allocate a connection ID for negotiation from [IP_address] to [IP_address] Explanation The crypto engine has exhausted all available connection IDs or is otherwise

malfunctioning. Recommended Action Decrease the number of concurrent connections or inspect the crypto engine.

Error Message %CRYPTO-3-CRYPTO_INV_ACL: Crypto ACL with GT/LT/NEQ operator is not supported. Explanation Crypto map ACL is an invalid map. Recommended Action Remove the invalid ACL .


266

CRYPTO Messages

Error Message %CRYPTO-3-ENGINE_BAD_ID: Crypto Engine id [dec] is invalid Explanation The engine ID of the packet is set to something other than software crypto or hardware crypto. The system cannot determine which encryption (crypto) engine to use. The packet will be sent to the default crypto engine, which is the software crypto engine. Recommended Action No action is required.

Error Message %CRYPTO-3-EZVPN_VINTERFACE_CREATE_ERR: EZVPN([chars]): Virtual-access interface creation failed Explanation The virtual interface feature will not work without a virtual access interface. The

EZVPN configuration is unusable. You can remove the virtual interface configuration from EZVPN as a workaround. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CRYPTO-3-IKMP_QUERY_KEY: Querying key pair failed. Explanation Querying public key and private key usinga subject name failed. Recommended Action Check the subject name in the certificate.

Error Message %CRYPTO-3-MTREE_CMD_BLOCK: Mtree command [dec] was blocked from the the mtree process queue. Explanation An attempt was made to enqueue a command to the crypto mtree manager process even

though IPsec is currently operating in HAPX mode. Recommended Action Copy the message exactly as it appears on the console or in the system log.



267

CRYPTO Messages

Error Message %CRYPTO-3-RSA_SELFTEST_FAILED: Generated RSA key failed self test Explanation An automatic test of the newly generated RSA key pair has failed and the RSA key has been automatically deleted. Recommended Action Retry the operation and attempt to create another RSA key pair. If this message

recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %CRYPTO-3-TOKENADMINLOCKEDOUT: Cryptographic Token [chars] Administrator PIN Locked due to too many unsuccessful login attempts Explanation The cryptographic token has disabled the Admin PIN due to too many login failures . Recommended Action If the user PIN is also locked out, it will be necessary to reinitialize the card.

The data on the card will be lost.

Error Message %CRYPTO-3-TOKENADMINLOGINFAILED: Cryptographic Token [chars] ADMIN Login FAILED Explanation The cryptographic token has rejected the administrator PIN offered by the router. Recommended Action Enter the crypto pki token admin-pin command to enter the correct PIN.

Error Message %CRYPTO-3-TOKENAPIFAILURE: Cryptographic Token [chars] API FAILED, error = [dec] Explanation The cryptographic token returned an unexpected error. Recommended Action Copy the message exactly as it appears on the console or in the system log.



268

CRYPTO Messages

Error Message %CRYPTO-3-TOKENCHANGEPINFAILED: Cryptographic Token [chars] Change PIN FAILED Explanation The cryptographic token has rejected the new PIN offered by the router. Recommended Action Be sure you are logged in to the token as administrator. Try a longer PIN.

Error Message %CRYPTO-3-TOKENLOCKEDOUT: Cryptographic Token [chars] PIN Locked due to too many unsuccessful login attempts Explanation The cryptographic token has disabled the user PIN due to too many login failures. Recommended Action Enter the crypto pki token admin-pin command to enter the correct

administrator PIN.

Error Message %CRYPTO-3-TOKENLOGINFAILED: Cryptographic Token [chars] Login FAILED Explanation The cryptographic token has rejected the PIN offered bythe router. Recommended Action Enter the crypto pki token user-pin command to enter the correct PIN.

Error Message %CRYPTO-3-TOKENSTOREKEYFAILED: Key [chars] store on Cryptographic Token [chars] Failed Explanation An error occurred attempting to write a new key pair out to the cryptographic token. Recommended Action Try logging in to the token. If the error persists, try logging in as administrator.

CRYPTO-4 Error Message %CRYPTO-4-ENC_METHOD_NOT_SUPPORTED: Invalid encryption method for IKE policy [int] Explanation The configured encryption method is not supported Recommended Action Use any of the valid encryption methods for the ISAKMP policy.

Error Message %CRYPTO-4-EZVPN_SA_LIMIT: [chars] Explanation The maximum number of EZVPN tunnels that can be set up on the platform has been

reached. Active SAs will not be terminated, but additional SAs can not be established until the number of existing SAs decreases. Recommended Action No action is required.


269

CRYPTO Messages

Error Message %CRYPTO-4-IA_CLEARTEXT: Unencrypted traffic [chars] [IP_address] because crypto optional is configured Explanation Cleartext traffic is passing through an interface that is configured for encryption. This

traffic is accepted because the router has the CRYPTO IPSEC OPTIONAL ENABLE setting, which allows such traffic. Recommended Action If you did not intend to configure the crypto optional setting, reconfigure the

system to turn it off.

Error Message %CRYPTO-4-IA_ENABLE: Security warning: crypto ipsec optional is configured Explanation The router has the CRYPTO IPSEC OPTIONAL setting enabled. This setting allows

data that would normally be encrypted to be sent without encryption. Recommended Action If you did not intend to configure the crypto optional setting, reconfigure the

system to turn it off.

Error Message %CRYPTO-4-IKE_DENY_SA_REQ: IKE denied an [chars] SA request from [chars] to [chars] due to [chars] Explanation Call Admission Control is configured globally or at the IKE level on this device. As a

result, an IKE SA request was denied due to the reason described in the error message. Recommended Action Depending on the reason that the request was denied, either reduce the load on the system so that it can handle new IKE SA requests, or increase the maximum allowed IKE sessions if more are needed.

Error Message %CRYPTO-4-IKE_QUICKMODE_BAD_CERT: encrypted connection attempted with a peer without the configured certificate attributes Explanation An encrypting peer attempted to establish an IPsec session with an interface for which

it was not authorized. This condition might be considered to be a hostile event. Recommended Action Verify that the peer is authorized to establish an IPsec session with the

interface. If the peer is authorized, this condition might be caused by an incorrect configuration. Contact the administrator of the peer.

Error Message %CRYPTO-4-IKE_SA_LIMIT: IKE active SA count is [int] but SA limit has been set to [int]. Explanation The IKE SA limit that was set is less than the number of active IKE SAs. Active SAs

will not be terminated but no additional IKE SAs can be established unless the limit is increased or the number of active SAs decreases. Recommended Action Increase the IKE SA limit if necessary to establish connectivity.


270

CRYPTO Messages

Error Message %CRYPTO-4-IKE_SA_NEGO_LIMIT: IKE in-negotiation SA count currently is [int] but new limit has been set to [int]. Explanation The IKE in-negotiation SA limit that was set is less than the current number of

in-negotiation IKE SA. As of a result, no more new IKE SAs can be created. However, those already in negotiation are allowed to finish. Recommended Action Increase the IKE SA limit if necessary to establish connectivity.

Error Message %CRYPTO-4-IKMP_ISR_LIMIT_MAX: INV SPI RECOV LIMIT [dec] maxed [IP_address] [IP_address] Explanation The maximum limit of INVALID SPI RECOVERY SAs has been reached. Recommended Action You may need to reload the local system.

Error Message %CRYPTO-4-IPSEC_AAA_START_FAILURE: IPSEC Accounting was unable to send start record Explanation The AAA subsystem was unable to send the accounting start record on behalf of IPsec.

This condition can occur if the AAA server is unreachable. Recommended Action Ensure that the AAA server is reachable and enabled for accounting.

Error Message %CRYPTO-4-IPSEC_AAA_STOP_FAILURE: IPSEC Accounting was unable to send stop record Explanation The AAA subsystem was unable to send the accounting stop record on behalf of IPsec.

This condition can occur if the AAA server is unreachable. Recommended Action Ensure that the AAA server is reachable and enabled for accounting.

Error Message %CRYPTO-4-IPSEC_ENC_METHOD_NOT_SUPPORTED: Transform [chars] not valid under IPSec transform [chars] Explanation The configured encryption algorithm is not supported. Recommended Action Specify a valid encryption algorithm for the IPsec transform.

Error Message %CRYPTO-4-IPSEC_ENC_METHOD_NOT_SUPPORTED_FULL_SPEED: Transform [chars] will run with reduced performance because of IPSec transform [chars] Explanation The configured encryption algorithm will not run on the hardware encryption card. The

transform is still usable but will run with reduced performance. Recommended Action To reach the full performance of the encryption card, specify another

encryption algorithm for the IPsec transform.


271

CRYPTO Messages

Error Message %CRYPTO-4-IPSEC_ENC_METHOD_NOT_SUPPORTED_WITH_IKE: Transform [chars] not usable with IKE because of IPSec transform [chars] Explanation The configured encryption algorithm is not usable with IKE with the current hardware

configuration. Recommended Action If IKE is required, specify a valid encryption algorithm for the IPsec transform.

Error Message %CRYPTO-4-NOAUTOSAVE: Configuration was modified. Issue "write memory" to save new certificate Explanation Auto Enrollment has obtained a new router key pair and certificate. However, the

running configuration was previously modified. Recommended Action Enter the write memory command to save the new certificates and keys.

Error Message %CRYPTO-4-RECVD_PKT_INV_UDP_WRAPPER: Rec’d packet has invalid udp wrapper protocol. cryptoflags = [hex], sa->udp_wrapper_support = [dec],transform = [hex] Explanation Either a UDP or encapsulated packet was received that is not a correct negotiation

transform, or the system expected a UDP-encapsulated packet but received a non-UDP packet. There might be a policy setup error on the peer. This activity could be considered a hostile event. Recommended Action Contact the administrator of the router or host that sent the packet to compare

policy settings.

Error Message %CRYPTO-4-TOKENKEYSDEACTIVATED: RSA keypairs from token [chars] and associated IPSEC sessions being deactivated now Explanation Router RSA key pairs and associated IPsec sessions are being deactivated because the

token containing them was removed. Recommended Action Reinsert the crypto token.

Error Message %CRYPTO-4-TOKENKEYTIMEOUT: RSA keypairs for token [chars] and associated IPSEC sessions will be deactivated in [dec] seconds Explanation Router RSA key pairs and associated IPsec sessions will be deactivated when the

timeout expires. Recommended Action Reinsert the crypto token before the timeout expires.


272

CRYPTO Messages

CRYPTO-5 Error Message %CRYPTO-5-GM_REGSTER: Start registration for group [chars] using address [chars] Explanation Registration for one group has started. Recommended Action No action is required.

Error Message %CRYPTO-5-IKE_SA_HA_STATUS: IKE sa’s if any, for vip [IP_address] will change from [chars] to [chars] Explanation This is a notification message for crypto IKE SAs changing HA status. Recommended Action No action is required.

Error Message %CRYPTO-5-IKMP_AG_MODE_DISABLED: Unable to initiate or respond to Aggressive Mode while disabled Explanation The router is configured to not accept or respond to ISAKMP aggressive mode with any

peer. Recommended Action If you did not intend to disable aggressive mode, remove the command.

Error Message %CRYPTO-5-IPSEC_SA_HA_STATUS: IPSec sa’s if any, for vip [IP_address] will change from [chars] to [chars] Explanation This is a notification message for crypto IPsec SAs changing HA status. Recommended Action No action is required.

Error Message %CRYPTO-5-SESSION_STATUS: Crypto tunnel is [chars]. Peer [IP_address]:[dec] [chars] [chars] [chars] [chars] [chars] [chars] [chars] [chars] Explanation This is a notification message for IPsec tunnel status. Recommended Action This is an informational message only. No action is required.

CRYPTO-6 Error Message %CRYPTO-6-AUTOGEN: Generated new [dec] bit key pair Explanation Auto Enrollment has generated a new router key pair. Recommended Action This is an informational message only. No action is required.


273

CRYPTO Messages

Error Message %CRYPTO-6-AUTOSAVE: Running configuration saved to NVRAM Explanation Auto Enrollment has obtained a new router key pair and certificate, and has done an

automatic write to memory to save them. Recommended Action This is an informational message only. No action is required.

Error Message %CRYPTO-6-CERTIFSRECV: Could not receive router’s Certificate from file system. Explanation The router’s certificate could not be received from the file system. Recommended Action Verify the enrollment URL and verify that the router is able to read from the

file system.

Error Message %CRYPTO-6-CERTIFSSEND: Could not send Certificate enrollment request to file system. Explanation The certificate enrollment request could not be sent to the file system. Recommended Action Verify the enrollment URL and verify that the router is able to write to the file

system.

Error Message %CRYPTO-6-EZVPN_CONNECTION_DOWN: [chars] Explanation The EZVPN connection is being closed. The IPsec and IKE security associations will

also be brought down along with it. Recommended Action No action is required.

Error Message

%CRYPTO-6-EZVPN_CONNECTION_UP: [chars]

Explanation The EZVPN connection is up for the specified client. Both IPsec and IKE security

associations are up now. Recommended Action No action is required.

Error Message %CRYPTO-6-ISAKMP_ON_OFF: ISAKMP is [chars] Explanation The ISAKMP process has been switched on or off either by the CLI or because no crypto

map or EZVPN configuration is applied to any interface. Recommended Action This is an informational message only. No action is required.

Error Message %CRYPTO-6-PKCS12EXPORT_FAIL: PKCS #12 Export Failed. Explanation An attempt to generate and export a PKCS #12 has failed. Recommended Action This is an informational message only. No action is required.


274

CRYPTO Messages

Error Message %CRYPTO-6-PKCS12EXPORT_SUCCESS: PKCS #12 Successfully Exported. Explanation A PKCS #12 has been generated and successfully exported. Recommended Action This is an informational message only. No action is required.

Error Message %CRYPTO-6-PKCS12IMPORT_FAIL: PKCS #12 Import Failed. Explanation An attempt to import a PKCS #12 has failed. Recommended Action This is an informational message only. No action is required.

Error Message %CRYPTO-6-PKCS12IMPORT_SUCCESS: PKCS #12 Successfully Imported. Explanation A PKCS #12 has been successfully imported. Recommended Action This is an informational message only. No action is required.

Error Message %CRYPTO-3-POLICY_CKSUM_ERROR: Crypto policy checksum failure. Crypto access list [chars], crypto map [chars], interface [chars] Explanation A crypto policy checksum failure has been detected in this router, whose traffic is protected by the crypto policy. This event may be caused by memory corruption occurring in crypto policy data or the memory area has been illegally modified. It may also be caused by software defects. As a result of this event, the router has been forced to reload. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CRYPTO-6-PRNG_SEED_KEY_ERROR: Pseudo-random number generator seed and seed key was identical Explanation The X9.17 random number specification requires checking for the same value appearing

as the seed and the seed key. This message indicates that the identical seed and seed key condition was discovered. Recommended Action The X9.17 random number will occasionally produce this condition, and this

is not a problem. If this message occurs frequently, the system should be manually reloaded. If the message is persistent across reloads, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,


275

CRYPTO Messages


Error Message %CRYPTO-6-TOKENADMINCHANGEPIN: Cryptographic Token [chars] ADMIN PIN change Successful Explanation The cryptographic token has accepted the new administrator PIN offered by the router. Recommended Action This is an informational message only. No action is required.

Error Message %CRYPTO-6-TOKENADMINLOGIN: Cryptographic Token [chars] ADMIN Login Successful Explanation The cryptographic token has accepted the administrator PIN offered by the router. Recommended Action This is an informational message only. No action is required.

Error Message %CRYPTO-6-TOKENCHANGEPIN: Cryptographic Token [chars] PIN change Successful Explanation The cryptographic token has accepted the new PIN offered by the router. Recommended Action This is an informational message only. No action is required.

Error Message %CRYPTO-6-TOKENINSERTED: Cryptographic token [chars] inserted in [chars] Explanation A cryptographic token has been detected. Recommended Action This is an informational message only. No action is required.

Error Message %CRYPTO-6-TOKENLOGIN: Cryptographic Token [chars] Login Successful Explanation The cryptographic token has accepted the PIN offered by the router. Recommended Action This is an informational message only. No action is required.

Error Message %CRYPTO-6-TOKENLOGOUT: Cryptographic Token [chars] Logout Successful Explanation The router has logged out from the cryptographic token. Recommended Action This is an informational message only. No action is required.


276

CRYPTO_HA Messages

Error Message %CRYPTO-6-TOKENREMOVED: Cryptographic token [chars] removed from [chars] Explanation A cryptographic token has been detected. Recommended Action This is an informational message only. No action is required.

Error Message %CRYPTO-6-TOKENSTOREKEY: Key [chars] stored on Cryptographic Token [chars] Successfully Explanation A new key pair has been written out to the cryptographic token. Recommended Action This is an informational message only. No action is required.

Error Message %CRYPTO-6-TOKENTIMEOUTCANCELLED: Cryptographic Token [chars] re-inserted. removal timeout cancelled Explanation A cryptographic token containing private keyfiles has been reinserted before the

timeout. Router RSA key pairs and associated IPsec sessions will not be deactivated. Recommended Action This is an informational message only. No action is required.

Error Message %CRYPTO-6-VPN_TUNNEL_STATUS: [chars] Explanation VPN tunnel status. Recommended Action This is an informational message only. No action is required.

CRYPTO_HA Messages This section contains crypto high availability messages.

CRYPTO_HA-3 Error Message %CRYPTO_HA-3-IKEADDENTRYFAIL: (VIP=[IP_address])ISAKMP SA entry insertion on standby device failed for src=[IP_address], dst=[IP_address] Explanation An attempt to insert an SA entry transferred from the active device has failed. The SA

database is no longer synchronized with that on the active device. Recommended Action Initiate a manual resynchronization of the ISAKMP SA table.


277

CRYPTO_HA Messages

Error Message %CRYPTO_HA-3-IKEDELENTRYFAIL: (VIP=[IP_address])ISAKMP SA entry deletion on standby device failed for src=[IP_address], dst=[IP_address] Explanation An attempt to delete an SA entry that was removed on the active device has failed. The

SA database is no longer synchronized with that on the active device. Recommended Action Initiate a manual resynchronization of the ISAKMP SA table.

Error Message %CRYPTO_HA-3-IKEINSERTKEYFAIL: (VIP=[IP_address])ISAKMP SA entry key insertion on standby device failed for src=[IP_address], dst=[IP_address] Explanation An attempt to insert keys for a new SA entry on the standby device has failed. The

standby device will not receive this entry. Recommended Action Initiate a manual resynchronization of the ISAKMP SA table from the standby

device.

Error Message %CRYPTO_HA-3-IKEQUERYKEYFAIL: (VIP=[IP_address])ISAKMP SA entry key query on active device failed for src=[IP_address], dst=[IP_address] Explanation An attempt to query an SA entry for key information to send to the standby device has

failed. The standby device will not receive this entry. Recommended Action Initiate a manual resynchronization of the ISAKMP SA table from the standby

device.

Error Message %CRYPTO_HA-3-IPSECADDENTRYFAIL: (VIP=[IP_address])IPSEC SA entry insertion on standby device failed Explanation An attempt to insert an SA entry transferred from the active device has failed. The SA

database is no longer synchronized with the database on the active device. Recommended Action Initiate a manual resynchronization of the IPsec SA table.

Error Message %CRYPTO_HA-3-IPSECDELENTRYFAIL: (VIP=[IP_address])IPSEC SA entry deletion on standby device failed Explanation An attempt to delete an SA entry that was removed on the active device has failed. The

SA database is no longer synchronized with the database on the active device. Recommended Action Initiate a manual resynchronization of the IPsec SA table.


278

CRYPTO_HA Messages

CRYPTO_HA-6 Error Message %CRYPTO_HA-6-IKEDOWN: (VIP=[IP_address])Disabling High Availability functionality for the ISAKMP failover group. Explanation This is a normal notification message when HA is unconfigured for this failover group, or a tracked interface is shut down. However, it may also be a result of a failure. Recommended Action If the failover was initiated deliberately (for example, by shutting down a

tracked interface), then no action is required. Otherwise, investigate the status of the redundancy protocol (HSRP, for example) that may have lead to the Down state notification to the high availability framework.

Error Message %CRYPTO_HA-6-IKEFAILOVER: (VIP=[IP_address])Taking over as the new Active device for the ISAKMP failover group. Explanation This is a normal notification message when an active device is first elected.

Alternatively, it is triggered when a failover occurs within the high availability group. In that case, the formerly active device within the ISAKMP failover group has gone down and this device is taking over as the new active device for the group. Recommended Action If the failover was initiated deliberately (for example, by shutting down a

tracked interface), then no action is required. Otherwise, investigate the status of the previous active device to troubleshoot the reason for failure and take appropriate action.

Error Message %CRYPTO_HA-6-IKEHAINFINITEMSGLOOP: (VIP=[IP_address])Dropping remainder of this HA IKE SSP message because of suspected infinite message loop. Explanation HA IKE SSP message processing seems to be looping on this message. The processing

of this message will be dropped to prevent an infinite loop. Recommended Action Turning on detailed IKE HA debugs on both HA pairs can help determine what

message may be causing this problem.

Error Message %CRYPTO_HA-6-IKEHANOTENABLE: IKE HA is not enabled. Explanation IKE HA received a state notification or an SSP message for a VIP that does not have

HA enabled. Recommended Action Verify that IKE stateful failover is configured for the interface with this VIP.

Error Message %CRYPTO_HA-6-IKEHASYNCCOMPLETE: (VIP=[IP_address])IKE HA state synchronization with Active device complete. Explanation This is a normal notification message after the standby has received either

REPLY_ENTRY or DELETE_ENTRY messages for all requests during synchroniztion. Recommended Action No action is required.


279

CRYPTO_HA Messages

Error Message %CRYPTO_HA-6-IKESTANDBY: (VIP=[IP_address])Setting up as a Standby device for the ISAKMP failover group. Explanation This is a normal notification message after a standby device comes up. Recommended Action No action is required.

Error Message %CRYPTO_HA-6-IKEUPDATEENTRYFAIL: (VIP=[IP_address])ISAKMP SA entry update on standby device failed for src=[IP_address], dst=[IP_address] Explanation An attempt to update an SA entry as specified by the active device has failed. The SA

entry will be missing the latest packet level update until another update entry is sent by the active device. Recommended Action Normally, a subsequent update entry message will self-correct the problem.

Manual resynchronization of the ISAKMP SA table by the standby device may be necessary if this message appears repeatedly.

Error Message %CRYPTO_HA-6-IPSECDOWN: (VIP=[IP_address])Disabling High Availability functionality for the IPSEC failover group. Explanation This is a normal notification message when HA is unconfigured for this failover group, or a tracked interface is shut down. However, it may also be a result of a failure. Recommended Action If the failover was initiated deliberately (for example, by shutting down a

tracked interface), then no action is required. Otherwise, investigate the status of the redundancy protocol (HSRP, for example) that may have lead to the Down state notification to the high availability framework.

Error Message %CRYPTO_HA-6-IPSECFAILOVER: (VIP=[IP_address])Taking over as the new Active device for the IPSEC failover group. Explanation This is a normal message when a device first becomes active, or when failover occurs

within the high availability group. In the failover case, the former active device within the IPsec failover group has gone down and this device is taking over as the new active device for the group. Recommended Action If the failover was initiated deliberately (for example, by shutting down a

tracked interface), then no action is required. Otherwise, investigate the status of the previous active device to troubleshoot the reason for failure and take appropriate action.

Error Message %CRYPTO_HA-6-IPSECHAMAXINSERTERRORS: IPsec HA has failed inserting SAs for the last [int] seconds, the box is either out of resources or has suffered a hardware failure Explanation The device is normally out of resources for short periods of time, and retries will

automatically occur. In this case, however, the retries have not succeeded and have stopped. Action is required from the administrator. Recommended Action Verify that both devices in the HA pair are identical and that the hardware is

working properly.


280

CRYPTO_HA Messages

Error Message %CRYPTO_HA-6-IPSECHANOTENABLE: (VIP=[IP_address])IPSEC HA is not enabled. Explanation IPsec HA received a state notification or an SSP message for a VIP that does not have

HA enabled. Recommended Action Verify that IPsec stateful failover is configured for the interface with this VIP.

Error Message %CRYPTO_HA-6-IPSECHASYNCCOMPLETE: (VIP=[IP_address])IPSEC HA state synchronization with Active device complete. Explanation This is a normal notification message after the standby has received either a

REPLY_ENTRY or a DELETE_ENTRY message for all requests during synchroniztion. Recommended Action No action is required.

Error Message %CRYPTO_HA-6-IPSECSTANDBY: (VIP=[IP_address])Setting up as a Standby device for the IPSEC failover group. Explanation This is a normal notification message when a standby device comes up. Recommended Action No action is required.

Error Message %CRYPTO_HA-6-IPSECUPDATEENTRYFAIL: (VIP=[IP_address])IPSEC SA entry update on standby device failed Explanation An attempt to update an IPsec SA entry as specified by the active device failed. The SA

entry will be missing the latest packet level update, until another update entry is sent by the active device. Recommended Action Normally, a subsequent update entry message will self-correct the problem. Manual resynchronization of the IPsec SA table by the standby device may be necessary, if this message appears repeatedly.


281

CRYPTO_HA_IKE Messages

CRYPTO_HA_IKE Messages This section contains encryption (CRYPTO) high availability (HA) IKE messages.

CRYPTO_HA_IKE-3 Error Message %CRYPTO_HA_IKE-3-FAILOVER_ERROR: Attempt to failover IKE SA ([IP_address]:[IP_address]) failed due to [chars]. No stateful failover available for this SA. Explanation The HA active device attempted to checkpoint the state of an IKE SA to the standby

device, but the standby device was unable to create the standby IKE SA. Recommended Action Search for other error messages at WARNING log level or turn on debugging

messages to find the specific cause of the failure.

CRYPTO_HA_IKE-4 Error Message %CRYPTO_HA_IKE-4-CRYPTO_HA_NOT_SUPPORTED_BY_HW: Crypto hardware is enabled and it does not support HA operation ’[chars]’ Explanation Crypto hardware is enabled, but the hardware does not support HA operations such as

insertion and extraction of keys. Recommended Action Replace the crypto module with one that supports HA operations, or disable the hardware and use the software crypto engine.

CRYPTO_HA_IPSEC Messages This section contains encryption (CRYPTO) high availability (HA) IPsec messages.

CRYPTO_HA_IPSEC-3 Error Message CRYPTO_HA_IPSEC-3-FAILOVER_ERROR: Attempt to failover IPSec SA ([IP_address]:[IP_address]) failed due to [chars]. No stateful failover available for this SA. Explanation The HA active device attempted to checkpoint the state of an IKE SA to the standby

device, but the standby device was unable to create the standby IKE SA. Recommended Action Search for other error messages at log level WARNING or turn on debugging

messages to find the specific cause of the failure.


282

CRYPTO_RSA_ISSU Messages

Error Message CRYPTO_HA_IPSEC-3-HA_IPSEC_UPDATE_PROC_FAIL: Start of HA IPSec update process failed Explanation The IPsec HA process failed to start. Updates will not be sent from the active device to the standby device. Recommended Action The module may need to be rebooted if this is a part of an IPsec HA setup.

CRYPTO_HA_IPSEC-4 Error Message CRYPTO_HA_IPSEC-4-CRYPTO_HA_NOT_SUPPORTED_BY_HW: Crypto hardware is enabled and it does not support HA operation ’[chars]’ Explanation Crypto Hardware is enabled, but the hardware does not support HA operations such as

insertion and extraction of keys. Recommended Action Replace the crypto module with one that supports HA operations, or disable the hardware and use the software crypto engine.

CRYPTO_RSA_ISSU Messages This section contains encryption (CRYPTO) RSA in-service software upgrade (ISSU) messages.

CRYPTO_RSA_ISSU-3 Error Message %CRYPTO_RSA_ISSU-3-GET_BUFFER: Crypto RSA ISSU client failed to get buffer for message. Error: %d (%s) Explanation The crypto RSA ISSU client was unable to obtain a buffer for building a negotiation

message. As a result, the client cannot send the negotiation message to the standby unit and the standby unit cannot be brought up. Recommended Action Copy the message exactly as it appears on the console or in the system log.



283


Error Message %CRYPTO_RSA_ISSU-3-INIT: Crypto RSA ISSU client initialization failed to %s. Error: %d (%s) Explanation The crypto RSA ISSU client could not be initialized. This condition will cause a

catastrophic failure when an ISSU upgrade or downgrade is performed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CRYPTO_RSA_ISSU-3-INVALID_SESSION: Crypto RSA ISSU client does not have a valid registered session. Explanation The crypto RSA ISSU client does not have a valid registered session. This condition will

prevent the standby unit from coming up. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CRYPTO_RSA_ISSU-3-MSG_NOT_OK: Crypto RSA ISSU client message type %d is not compatible Explanation The crypto RSA ISSU client received an incompatible message from the peer unit.

Because the message is not compatible, it cannot be processed by this unit. Recommended Action Copy the message exactly as it appears on the console or in the system log.



284


Error Message %CRYPTO_RSA_ISSU-3-MSG_SIZE: Crypto RSA ISSU client failed to get the MTU for message type %d. Error: %d (%s) Explanation The crypto RSA ISSU client was unable to calculate the MTU for the message specified.

The 802.1X ISSU client will be unable to send the message to the standby unit. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CRYPTO_RSA_ISSU-3-SEND_NEGO_FAILED: Crypto RSA ISSU client failed to send negotiation message. Error: %d (%s) Explanation The crypto RSA ISSU client failed to send a session negotiation message to the peer.

This condition will prevent the standby unit from coming up. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CRYPTO_RSA_ISSU-3-SESSION_NEGO: Crypto RSA ISSU client encountered unexpected client nego_done. Error: %d (%s) Explanation The crypto RSA ISSU client encountered an unexpected ’client negotiation done’. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly. Recommended Action Copy the message exactly as it appears on the console or in the system log.



285


following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs.

Error Message %CRYPTO_RSA_ISSU-3-SESSION_REGISTRY: Crypto RSA ISSU client failed to register session information. Error: %d (%s) Explanation The crypto RSA ISSU client failed to register session information. This condition will prevent the standby unit from coming up. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CRYPTO_RSA_ISSU-3-SESSION_UNREGISTRY: Crypto RSA ISSU client failed to unregister session information. Error: %d (%s) Explanation The crypto RSA ISSU client failed to unregister session information. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CRYPTO_RSA_ISSU-3-TRANSFORM_FAIL: Crypto RSA ISSU client %s transform failed for message type %d. Error: %d (%s) Explanation The crypto RSA ISSU client could not transform the message. If the transmit transformation failed, the checkpoint message cannot be sent to the standby unit. If the receive transformation failed, the checkpoint message cannot be applied on the standby unit. In either case, the crypto RSA state will not match with the active unit. Recommended Action Copy the message exactly as it appears on the console or in the system log.



286

CSG Messages

http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs.

CSG Messages This section contains Content Services Gateway (CSG) messages.

CSG-3 Error Message %CSG-3-ERROR: Module [dec]: [chars] Explanation An error occurred in a CSG module. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %CSG-3-RELOADNOTOK: CSG ACCOUNTING [chars] reload on module [dec] failed. Explanation This informational message appears whenever a CSG configuration is reloaded as a result of power cycling a CSG card. Recommended Action This is an informational message only. No action is required.

CSG-4 Error Message %CSG-4-WARNING: Module [dec]: [chars] Explanation An undesired event has occurred in a CSG module. Recommended Action If this message recurs, copy the message exactly as it appears on the console

or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at


287

CSM_SLB Messages


CSG-6 Error Message %CSG-6-LIRELOADOK: CSG LI reload on module [dec] successful Explanation The CSG lawful intercept (LI) configuration was reloaded because of the power cycling

of a CSG module. Recommended Action No action is required.

Error Message %CSG-6-RELOADOK: CSG ACCOUNTING [chars] reload on module [dec] successful Explanation This informational message appears whenever a CSG configuration is reloaded as a

result of power cycling a CSG card. Recommended Action This is an informational message only. No action is required.

CSM_SLB Messages This section contains Content Switching Module (CSM) server load balancing (SLB) messages.

CSM_SLB-4 Error Message %CSM_SLB-4-ENV_VARIABLE: Module %d warning: %s %s Explanation There is a mismatch between the configuration and the specified environment variable. Recommended Action Check the documentation for any caveats regarding the use of the specified

environment variable.


288

CT3 Messages

CT3 Messages This section contains CT3 shared port adapter messages.

Error Message %CT3-3-CT3NOACC: [chars] - Accumulator is not available Explanation An invalid TX accumulator is detected. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CT3-3-MBOXRECV: Failed to receive reply [dec] from bay [dec] firmware Explanation A message was not received from CT3 firmware. Recommended Action Copy the error message exactly as it appears, collect the output of the show

tech-support command immediately, and report it to your technical support representative. If possible, try to do an OIR (Online Insertion and Removal). Please refer to the Cisco documentation for information on ’Online Insertion and Removal’ for your platform

Error Message %CARRIER-2-TOOMANY_CT3: Too many CT3 DFC cards, do not power up invalid card in slot [dec] Explanation The user has put too many CT3 DFC cards in the chassis. Recommended Action Remove the extra CT3 DFC card, or 8PRI DFC card causing the problem.


289

CTS Messages

CTS Messages This section contains Cisco TrustSec (CTS) messages.

CTS-0 Error Message %CTS-0-AUTHZ_OUT_OF_MEM: %s failed to create %s due to insufficient memory Explanation A Cisco TrustSec (CTS) process failed due to insufficient system memory. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CTS-0-CTS_EMERG: [chars] Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CTS-0-IFC_OUT_OF_MEM: %s failed to create %s due to insufficient memory Explanation A Cisco TrustSec (CTS) process failed due to insufficient system memory. Recommended Action Copy the message exactly as it appears on the console or in the system log.



290

CTS Messages


CTS-1 Error Message %CTS-1-CTS_ALERT: [chars] Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


CTS-2 Error Message %CTS-2-CTS_CRIT: [chars] Explanation An internal software error occurred. Recommended Action Copy the error message exactly as it appears on the console or in the system


CTS-3 Error Message %CTS-3-AUTHZ_ADD_DATA_FAILED: %s failed to add %s to %s Explanation An error occurred while the Cisco TrustSec (CTS) authorization attempted to build its

database. Recommended Action Copy the message exactly as it appears on the console or in the system log.



291

CTS Messages


Error Message %CTS-3-AUTHZ_DATA_CREATE_FAILED: %s failed to create %s Explanation Cisco TrustSec (CTS) authorization was unable to create an internal data structure. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CTS-3-AUTHZ_DATA_EXCEEDS_LIMIT: %s encountered %s(%d) exceeds max(%d) Explanation Cisco TrustSec (CTS) authorization data exceeded the maximum allowed limit. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CTS-3-AUTHZ_DATA_FAILED: %s failed to obtain %s Explanation Cisco TrustSec (CTS) authorization was unable to get or create a data structure. Recommended Action Copy the message exactly as it appears on the console or in the system log.



292

CTS Messages

Error Message %CTS-3-AUTHZ_DATA_NULL: %s encounters NULL %s Explanation Cisco TrustSec (CTS) authorization encountered an unexpected NULL pointer or data. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CTS-3-AUTHZ_DATA_UNINIT: %s appears uninitialized Explanation Cisco TrustSec (CTS) authorization unexpectedly encountered uninitialized data. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CTS-3-AUTHZ_FAILED_SYNC_RCV: Standby failed receive sync msg(%s) Explanation An error occurred while the standby unit was receiving synchronization data from the

active unit. Recommended Action Copy the message exactly as it appears on the console or in the system log.



293

CTS Messages

Error Message %CTS-3-AUTHZ_GENERIC_FAILURE: %s %s Explanation Cisco TrustSec (CTS) authorization encountered an internal error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CTS-3-AUTHZ_INSTALL_FAILED: %s failed to install %s %s Explanation An error occurred while Cisco TrustSec (CTS) authorization attempted to build its



Error Message %CTS-3-AUTHZ_INVALID_DATA: %s encountered invalid %s Explanation Cisco TrustSec (CTS) authorization encountered an invalid data type. Recommended Action Copy the message exactly as it appears on the console or in the system log.



294

CTS Messages

Error Message %CTS-3-AUTHZ_NOT_SUPPORTED: %s encountered %s not unsupported Explanation Cisco TrustSec (CTS) authorization encountered an unsupported data type or feature,

possibly due to incompatibility. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CTS-3-AUTHZ_POLICY_FALLBACK_FAILED: Failed to %s Fallback policy for %s Explanation Cisco TrustSec (CTS) was unable to install a fallback authorization policy. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CTS-3-AUTHZ_POLICY_INGRESS_FAILED: Failed to %s Ingress policy for %s Explanation Cisco TrustSec (CTS) was unable to acquire or install an ingress policy from the access

control server. Recommended Action Copy the message exactly as it appears on the console or in the system log.



295

CTS Messages

Error Message %CTS-3-AUTHZ_POLICY_INTERNAL_FAILED: Failed to acquire/install policy for %s due to internal error Explanation Cisco TrustSec (CTS) was unable to acquire or install a policy due to an internal

software error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CTS-3-AUTHZ_POLICY_PEER_DOWNLOAD_FAILED: Failed to download peer policy for %s Explanation Cisco TrustSec (CTS) was unable to acquire a peer policy from the access control

server. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CTS-3-AUTHZ_POLICY_RBACL_FAILED: Failed to %s RBACL %s for SGT=%d Explanation Cisco TrustSec (CTS) was unable to acquire a role-based access control list (RBACL)

policy from the access control server. Recommended Action Copy the message exactly as it appears on the console or in the system log.



296

CTS Messages

Error Message %CTS-3-AUTHZ_POLICY_WILDCARD_FAILED: Failed to download wildcard policy Explanation Cisco TrustSec (CTS) was unable to acquire a wildcard policy from the access control

server. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CTS-3-AUTHZ_SYNC_FAILED: Failed to send %s sync msg(%s) to Standby Explanation An error occurred while Cisco TrustSec (CTS) authorization was performing a

synchronization of the standby unit. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CTS-3-CTS_ERR: [chars] Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



297

CTS Messages

Error Message %CTS-3-DOT1X_CONFIG_FAILED: Failed to configure dot1x for int(%s) Explanation Cisco TrustSec (CTS) was unable to configure 802.1X for a CTS link. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CTS-3-DOT1X_FORCE_PORT_AUTHORIZED_FAILED: Failed to force dot1x port authorized for int(%s) Explanation Cisco TrustSec (CTS) authorization was unable to FORCE AUTHORIZED an 802.1X

port on a CTS link. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CTS-3-DOT1X_INIT_FAILED: Failed to initialize dot1x for int(%s) Explanation Cisco TrustSec (CTS) was unable to initialize 802.1X for a CTS link. Recommended Action Copy the message exactly as it appears on the console or in the system log.



298

CTS Messages

Error Message %CTS-3-DOT1X_PAE_FAILED: Failed to %s dot1x PAE(%s) for int(%s) Explanation Cisco TrustSec (CTS) was unable to start or stop an 802.1X Port Access Entity (PAE)

for a CTS link. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CTS-3-GENERIC_FAILURE: %s %s Explanation Cisco TrustSec (CTS) encountered an internal error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CTS-3-GLOBAL_DOT1X_DISABLED: Global dot1x config is currently disabled - CTS will not run Explanation Because global 802.1X is not enabled, Cisco TrustSec (CTS) will not run. Recommended Action Copy the message exactly as it appears on the console or in the system log.



299

CTS Messages

Error Message %CTS-3-IFC_DATA_DESC_DECODE_FAILED: %s failed to decode the data-descriptori - swidb unknown Explanation Cisco TrustSec (CTS) was unable to decode the data descriptor in order to obtain the software interface descriptor block (SWIDB). Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CTS-3-IFC_DATA_DESC_ENCODE_FAILED: %s failed to encode the data-descriptor for int(%s) Explanation Cisco TrustSec (CTS) was unable to encode the software interface descriptor block

(SWIDB) into the data descriptor. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CTS-3-IFC_DATA_NULL: %s encounters NULL %s Explanation Cisco TrustSec (CTS) encountered an unexpected NULL pointer or data. Recommended Action Copy the message exactly as it appears on the console or in the system log.



300

CTS Messages

Error Message %CTS-3-IFC_LINK_OBJ_FAILED: %s failed to get link_obj for int(%s) Explanation Cisco TrustSec (CTS) IFC was unable to access the link object. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CTS-3-IFC_SYNC_FAILED: Failed to send %s sync msg(%s) to Standby Explanation An error occurred while Cisco TrustSec (CTS) IFC was performing a synchronization

of the standby unit. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CTS-3-IFC_SYNC_FAILED_2: %s, Failed to send %s sync msg(%s) to Standby Explanation An error occurred while Cisco TrustSec (CTS) IFC was performing a synchronization

of the standby unit. Recommended Action Copy the message exactly as it appears on the console or in the system log.



301

CTS Messages

Error Message %CTS-3-INVALID_MSGID_RCV: %s received invalid HA/ISSU msgId(%d) Explanation Cisco TrustSec (CTS) encountered an unexpected invalid HA/ISSU message ID. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CTS-3-PORT_AUTHORIZED_FAILED: Failed to authorize Port for int(%s) Explanation A port could not be authorized on a Cisco TrustSec (CTS) link. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CTS-3-PP_CTS_EC_NOT_CTS: Physical port is not configured for CTS, but port-channel is. Explanation A physical port cannot join the channel group (port channel) because its Cisco TrustSec

(CTS) configuration does not match the channel group’s CTS configuration. Recommended Action Copy the message exactly as it appears on the console or in the system log.



302

CTS Messages

Error Message %CTS-3-PP_CTS_MODE_EC_MISMATCH: Physical port CTS mode does not match the port-channel’s CTS mode. Explanation A physical port cannot join the port channel because its Cisco TrustSec (CTS) mode

does not match the port channel’s CTS mode. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CTS-3-PP_CTS_TIMER_REAUTH_EC_MISMATCH: Cannot bundle interface. CTS Reauth Timer mismatch. %s = %d %s = %d Explanation A physical port cannot join the port channel because its Cisco TrustSec (CTS)

reauthentication timer value does not match the port channel’s timer value. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CTS-3-PP_NOT_CTS_EC_CTS: Physical port is configured for CTS, but port-channel is not. Explanation A physical port cannot join the channel group (port channel) because its Cisco TrustSec

(CTS) configuration does not match the channel group’s CTS configuration. Recommended Action Copy the message exactly as it appears on the console or in the system log.



303

CTS Messages

Error Message %CTS-3-SEND_MSG_TO_CORE_FAILED: Failed to send msg([dec]) to core process Explanation An error occcured while CTS attempts to to send a message event to the core process Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CTS-3-SXP_BINDING_ERR: Binding [chars]- [chars] Explanation SXP binding update error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CTS-3-SXP_CONN_STATE_CHG_OFF: Connection [chars]-[dec] state changed from [chars] to Off. Explanation SXP Connection with the specified instance number changed state. Recommended Action No action is required.

Error Message %CTS-3-SXP_LISTENER: Fail to start global listening socket after TCP process restart. Explanation The Security Exchange Protocol (SXP) process could not start after a restart. Recommended Action Copy the message exactly as it appears on the console or in the system log.



304

CTS Messages


Error Message %CTS-3-SXP_MSG_PARSE: Connection [chars] [chars] Explanation An error occurred while parsing SXP message. Recommended Action Copy the message exactly as it appears on the console or in the system log.


CTS-4 Error Message %CTS-4-CTS_WARNING: [chars] Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CTS-4-SXP_INTERNAL: CTS SXP [chars] Explanation The CTS SXP system encountered internal failure. Recommended Action Copy the message exactly as it appears on the console or in the system log.



305

CTS Messages

CTS-5 Error Message %CTS-5-CTS_NOTICE: [chars] Explanation Normal but significant conditions Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CTS-5-SXP_BINDING_ADD: Binding [chars]- added to SXP database. Explanation Binding added to the SXP database. Recommended Action No action is required.

Error Message %CTS-5-SXP_BINDING_CHG: Binding [chars]- changed: old connection instance number:[dec], old sgt:[dec]. Explanation Binding changed in the SXP database. Recommended Action No action is required.

Error Message %CTS-5-SXP_BINDING_DEL: Binding [chars]- deleted in SXP database. Explanation Binding deleted in the SXP database. Recommended Action No action is required.

Error Message %CTS-5-SXP_BINDING_FWD: Binding [chars]- is forwarded to the peer. Explanation SXP forwarded binding to the peer. Recommended Action No action is required.

Error Message %CTS-5-SXP_BINDING_REQ: SXP received binding forwarding request ([chars]) binding [chars]. Explanation SXP received a binding forwarding request. Recommended Action No action is required.


306

CTS Messages

Error Message %CTS-5-SXP_BINDING_UPD: Binding [chars] [chars]. Update binding manager. Explanation SXP updated binding manager with the binding change. Recommended Action No action is required.

Error Message %CTS-5-SXP_DFT_PASSWORD_CHANGE: CTS SXP password changed. Explanation The SXP system password has been changed. Recommended Action No action is required.

Error Message %CTS-5-SXP_DFT_SRCIP_CHG: SXP default source IP is changed [IP_address] -- [IP_address]. Explanation SXP default source IP is changed on this device. Recommended Action No action is required.

Error Message %CTS-5-SXP_VRF_DEL: SXP Connection removed.

configuration in VRF:[chars] is

Explanation A VRF is removed, the connections configured in this VRF should be removed. Recommended Action No action is required.

Error Message %CTS_HA_ISSU-3-CAP_INVALID_SIZE: CTS HA empty tlv size. Explanation Received empty tlv list during capability negotiation. Recommended Action Copy the message exactly as it appears on the console or in the system log.



307

CTS Messages

CTS-6 Error Message %CTS-6-DOT1X_FORCE_PORT_AUTHORIZED_SUCCESS: Successfully forced dot1x port authorized for int(%s) Explanation Cisco TrustSec (CTS) authorization caused FORCE AUTHORIZED on an 802.1X port on a CTS link. Recommended Action No action is required.

Error Message %CTS-6-DOT1X_PAE_CONFIG: %s dot1x PAE(%s) for int(%s) Explanation The specified interface has been configured to be an 802.1X Port Access Entity (PAE). Recommended Action No action is required.

Error Message %CTS-6-IFC_CACHE_APPLIED: Cache data applied for int(%s) Explanation The Cisco TrustSec (CTS) link was brought up using cache data. Recommended Action No action is required.

Error Message %CTS-6-CTS_INFO: [chars] Explanation Informational messages Recommended Action No action is required.

Error Message %CTS-6-PORT_AUTHORIZED_SUCCESS: Port authorized for int(%s) Explanation A port was authorized on a Cisco TrustSec (CTS) link. Recommended Action No action is required.

Error Message %CTS-6-PORT_UNAUTHORIZED: Port unauthorized for int(%s) Explanation A port has become unauthorized on a Cisco TrustSec (CTS) link. Recommended Action No action is required.

Error Message %CTS-6-SXP_CONFIG: Connection [chars] [chars] Explanation A SXP configuration error occurred. The connection can not be setup correctly. Recommended Action Ensure that the connection configure on both ends have the matched mode, IP

addresses.


308

CTS Messages

Error Message %CTS-6-SXP_CONN_STATE_CHG: Connection [chars]-[dec] state changed from [chars] to [chars]. Explanation SXP Connection with the specified instance number changed state. Recommended Action No action is required.

Error Message %CTS-6-SXP_SRC_IP: Source IP address ([chars] [IP_address]) does not belong to this device. Explanation An error occurred while using this source IP address to set up SXP connection. Recommended Action Re-configure SXP connection to have a valid source IP address.

Error Message %CTS-6-SXP_TIMER_START: Connection [chars] [chars] timer started. Explanation The specified SXP timer started. Recommended Action No action is required.

Error Message %CTS-6-SXP_TIMER_STOP: Connection [chars] [chars] timer stopped. Explanation The specified SXP timer stopped. Recommended Action No action is required.

CTS-7 Error Message %CTS-7-CTS_ASSERT: Assertion Failure ( [chars] @[chars]:[dec] ) : [chars] Explanation An internal software error occurred. Recommended Action Copy the error message exactly as it appears on the console or in the system



309

CTS_HA Messages

CTS_HA Messages This section contains Cisco TrustSec (CTS) high availability (HA) messages.

CTS_HA-3 Error Message %CTS_HA-3-CHKPT_REG_FAIL: CTS HA add CTS checkpoint client failure Explanation The Cisco TrustSec (CTS) high availability (HA) process failed to add a checkpoint

client. No CTS data will be synchronized with the standby device. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CTS_HA-3-RECEIVE_FAILED: CTS HA client failed to process message recieved from Active device. Explanation The Cisco TrustSec (CTS) high availability (HA) client on the standby device failed to

process a checkpoint message from the active device. The CTS state between the active device and the standby device is not identical. Recommended Action Copy the message exactly as it appears on the console or in the system log.



310

CTS_HA_ISSU Messages

Error Message %CTS_HA-3-SEND_FAILED: CTS HA client on Active device failed to send checkpoint message. CTS component Id %d, message Id %d Explanation The Cisco TrustSec (CTS) high availability (HA) client on the active device failed to

send a checkpoint message to the standby device. The CTS state between the active device and the standby device is not identical. Recommended Action Copy the message exactly as it appears on the console or in the system log.


CTS_HA_ISSU Messages This section contains Cisco TrustSec (CTS) high availability (HA) in-service software upgrade (ISSU) messages.

CTS_HA_ISSU-3 Error Message %CTS_HA_ISSU-3-CAP_INVALID_SIZE: CTS HA empty tlv size. Explanation Received empty tlv list during capability negotiation. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CTS_HA_ISSU-3-CAP_NOT_COMPATIBLE: CTS HA capability not compatible Explanation CTS HA failed during capability negotiation. Recommended Action Copy the message exactly as it appears on the console or in the system log.



311



Error Message %CTS_HA_ISSU-3-GET_BUFFER: CTS HA ISSU client failed to get buffer for message. Error: %d (%s) Explanation The Cisco TrustSec (CTS) high availability (HA) ISSU client failed to get buffer space

for building a negotiation message. A negotiation message cannot be sent to the standby device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CTS_HA_ISSU-3-INIT: CTS HA ISSU client initialization failed to %s. Error: %d (%s) Explanation The Cisco TrustSec (CTS) high availability (HA) ISSU client could not be initialized.

This initialization failure must be addressed before an in-service software upgrade or downgrade can be performed successfully. Otherwise, a software upgrade or downgrade will result in downtime. Recommended Action Copy the message exactly as it appears on the console or in the system log.



312


Error Message %CTS_HA_ISSU-3-MSG_NOT_COMPATIBLE_WITH_PEER: Message [dec] in component [dec] is not compatible with the peer. Explanation Message not compatible with the peer. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CTS_HA_ISSU-3-SEND_NEGO_FAILED: CTS HA ISSU client failed to send negotiation message. Error: %d (%s) Explanation The Cisco TrustSec (CTS) high availability (HA) ISSU client failed to send a session

negotiation message to the peer device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CTS_HA_ISSU-3-SESSION_REGISTRY: CTS HA ISSU client failed to register session information. Error: %d (%s) Explanation The Cisco TrustSec (CTS) high availability (HA) ISSU client failed to register session

information. If a problem occurs with the ISSU session registration, the standby device cannot be brought up properly. Recommended Action Copy the message exactly as it appears on the console or in the system log.



313



Error Message %CTS_HA_ISSU-3-SESSION_UNREGISTRY: CTS HA ISSU client failed to unregister session information. Error: %d (%s) Explanation The Cisco TrustSec (CTS) high availability (HA) ISSU client failed to unregister

session information. Recommended Action Copy the message exactly as it appears on the console or in the system log.


CTS_HA_ISSU-6 Error Message %CTS_HA_ISSU-6-INCOMPAT: CTS HA ISSU client negotiation results incompatible Explanation The Cisco TrustSec (CTS) high availability (HA) ISSU client message version is not compatible on the active and standby devices. As a result, no CTS data will be synchronized to the standby device. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs.


314

CWAN_ALARM Messages

CWAN_ALARM Messages This section contains Constellation WAN (CWAN) alarm messages.

CWAN_ALARM-6 Error Message %CWAN_ALARM-6-INFO: [chars] [chars] [chars] [chars] [chars] Explanation This message provides alarm assertion or deassertion information. Recommended Action This is an informational message only. No action is required.

Error Message %CWAN_ALARM-6-SONET: [chars] [chars] [chars] [chars] [chars] Explanation This message is generated whenever an alarm is present in the system (and the alarm

status has been reported to the RP) or an alarm has been removed from the system (and the alarm status has been reported to the RP . Recommended Action This is an informational message only. No action is required.

Error Message %CTS-6-SXP_PASSWORD_CHANGE: CTS SXP password changed Explanation The Cisco TrustSec (CTS) Security Exchange Protocol (SXP) system password has been changed. Recommended Action No action is required.

Error Message %CTS-6-SXP_STATE_CHANGE: CTS SXP %s Explanation The Cisco TrustSec (CTS) Security Exchange Protocol (SXP) system component has

changed its operational state. Recommended Action No action is required.


315

CWAN_ATM Messages

CWAN_ATM Messages This section contains Catalyst 6500 series switch and Cisco 7600 series router WAN ATM port (CWAN_ATM) messages.

CWAN_ATM-3 Error Message %CWAN_ATM-3-LOWMEM: Could not allocate memory for RFC 1483 packet cloning. Explanation Memory is running low. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message %CWAN_ATM-3-PORT_ERR: Invalid PORT [dec] Explanation The specified port does not exist. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CWAN_ATM-3-VCD_ERR: Invalid PortVCD [hex] Explanation The specified port VCD does not exist. Recommended Action Copy the message exactly as it appears on the console or in the system log.



316

CWAN_ATM Messages

Error Message %CWAN_ATM-3-VC_ERR: Invalid VC [hex] Explanation The specified VC does not exist on the port. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CWAN_ATM-3-VC_OR_PORT_ERR: Invalid VCD [hex] or Port: [dec] Explanation Either the port or the VCD is invalid. Recommended Action Copy the message exactly as it appears on the console or in the system log.


CWAN_ATM-5 Error Message %CWAN_ATM-5-UNKNOWN_VCD: Unknown port vcd [hex] in egress packet Explanation An unknown VCD has been received in the egress path of the module. This condition is

most likely a transient condition, and it is usually caused by VCs that are being disassembled and reassembled while traffic is being passed. Recommended Action No action is required.


317

CWAN_ATOM-HA Messages

CWAN_ATOM-HA Messages This section contains Any Transport over MPLS (AToM) high availability messages.

CWAN_ATOM-HA-2 Error Message %CWAN_ATOM_HA-2-ISSU_ERROR: [chars] [chars] Explanation Platform ATOM HA ISSU client error. Recommended Action Copy the error message exactly as it appears on the console or in the system


CWAN_ATOM-HA-3 Error Message %CWAN_ATOM_HA-3-CF_ERROR: [chars] [dec] Explanation Platform ATOM HA CF client error. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %CWAN_ATOM_HA-3-RF_ERROR: [chars] [dec] Explanation Platform ATOM HA RF client error. Recommended Action Copy the error message exactly as it appears on the console or in the system



318

CWAN_CHOC Messages

CWAN_CHOC Messages This section contains Catalyst 6500 series switch and Cisco 7600 series router WAN Channelized OC48/OC12-related (CWAN_CHOC) messages.

CWAN_CHOC-4 Error Message %CWAN_CHOC-4-CORRUPT: [chars] information seems to be corrupted, bad value =[int] Explanation Incorrect parameters were detected internally. Recommended Action This is only a debug warning message. The unexpected value is discarded.

CWAN_CHOC_DSX Messages This section contains Catalyst 6500 series switch and Cisco 7600 series router WAN CHOC DSX LC Common (CWAN_CHOC_DSX) messages.

CWAN_CHOC_DSX-3 Error Message %CWAN_CHOC_DSX-3-NODESTROYSUBBLOCK: The [chars] subblock named [chars] was not removed Explanation A software error occurred. This message displays when IDB subblocks cannot be

removed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



319

CWAN_CT3 Messages

CWAN_CT3 Messages This section contains Catalyst 6500 series switch and Cisco 7600 series router WAN module Channelized T3 (CWAN_CT3) messages.

CWAN_CT3-3 Error Message %CWAN_CT3-4-CORRUPT: [chars] information seems to be corrupted, bad value =[int] Explanation Incorrect parameters were detected internally. Recommended Action This is only a debug warning message. The unexpected value is discarded.

CWAN_FWD_TABLES Messages This section contains Catalyst 6500 series switch and Cisco 7600 series router WAN module forwarding tables messages.

CWAN_FWD_TABLES-3 Error Message %CWAN_FWD_TABLES-3-CHUNK_CREATE_FAIL: [chars] Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CWAN_FWD_TABLES-3-CHUNK_DESTROY_FAIL: [chars] Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



320

CWAN_FWD_TABLES Messages


Error Message %CWAN_FWD_TABLES-3-CHUNK_MALLOC_FAIL: [chars] Explanation There is a problem with internal software coding. This message should not appear under

normal operation. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CWAN_FWD_TABLES-3-ENTRY_BUILD_FAIL: [chars] [int] Explanation There is a problem with internal software coding. This message should not appear under



Error Message %CWAN_FWD_TABLES-3-INVALID_DEST_INFO: [chars] [hex] [hex] [hex] Explanation There is a problem with internal software coding. This message should not appear under




321

CWAN_FWD_TABLES Messages


Error Message %CWAN_FWD_TABLES-3-INVALID_INDEX: [chars] [int] Explanation There is a problem with internal software coding. This message should not appear under



Error Message %CWAN_FWD_TABLES-3-INVALID_OPR_TYPE: [chars] [dec] Explanation There is a problem with internal software coding. This message should not appear under



Error Message %CWAN_FWD_TABLES-3-MALLOC_FAILED: [chars] Explanation There is a problem with internal software coding. This message should not appear under




322

CWAN_HA Messages

Error Message %CWAN_FWD_TABLES-3-TABLE_ERROR: [chars] Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


CWAN_HA Messages This section contains Catalyst 6500 series switch and Cisco 7600 series router WAN module high availability (CWAN_HA) messages.

CWAN_HA-2 Error Message %CWAN_HA-2-CCB_PLAYBACK_ERROR: CCB playback failed for slot [dec]. Explanation The high availability component for WAN modules failed to synchronize new state

information for the specified slot. Recommended Action Reload the redundant supervisor engine to force a fresh bulk synchronization. If this error recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. Examine both the active supervisor engine and the redundant supervisor engine for messages.

Error Message %CWAN_HA-2-CCB_RECORD_ERROR: CCB record failed for slot [dec]. Explanation The high availability component for WAN modules failed to record new state

information for the specified slot. The system is falling back to RPR mode for high availability. Recommended Action Examine both the active supervisor engine and the redundant supervisor engine for messages. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved


323

CWAN_HA Messages

software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %CWAN_HA-2-IFCFG_PLAYBACK_ERROR: Interface Configuration command [int] playback failed for slot [int]/[int]. Explanation The high availability component for WAN modules failed to synchronize new state

information for the specified slot. The redundant system is no longer synchronized with the active system. The redundant supervisor engine was reloaded shortly after this error was encountered. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %CWAN_HA-2-IFCFG_RECORD_ERROR: Interface Configuration command [int] record failed for slot [int]/[int]. Explanation The high availability component for WAN modules failed to record some new state

information for the specified slot. The system is falling back to RPR mode for high availability. Recommended Action Copy the message exactly as it appears on the console or in the system log.



324

CWAN_HA Messages

CWAN_HA-3 Error Message %CWAN_HA-3-CCB_INIT_ERROR: Failed to initialize CCB list for slot [dec]. Explanation The high availability component for WAN modules failed to properly initialize state

information for the specified slot. The system is falling back to RPR mode for high availability. Recommended Action Examine both the active supervisor engine and the redundant supervisor engine for messages. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %CWAN_HA-3-IFCFG_CMD_NOT_UNIQUE: More than one command registered for unique-key generator for interface configuration command [int]. Explanation The high availability component for WAN modules is unable to properly synchronize state information for the current configuration due to a conflict in command identifiers. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CWAN_HA-3-IFCFG_INIT_ERROR: Failed to initialize Interface Configuration list for slot [int]/[int]. Explanation The high availability component for WAN modules failed to properly initialize state

information for the specified slot. The system is falling back to RPR mode for high availability. Recommended Action Examine both the active supervisor engine and the redundant supervisor engine for messages. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support


325

CWAN_HA Messages

representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. Examine both the active supervisor engine and the redundant supervisor engine for messages.

Error Message %CWAN_HA-3-IFCFG_NO_UNIQUE_KEY: No unique-key generator registered for interface configuration command [int]. Explanation The high availability component for WAN modules is unable to properly synchronize state information for the current configuration. The system is falling back to RPR mode for high availability. Recommended Action Examine both the active supervisor engine and the redundant supervisor engine for messages. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

CWAN_HA-4 Error Message %CWAN_HA-4-CCB_PLAYBACK_ERROR: CCB playback failed for slot [dec]. Explanation The high availability component for WAN modules failed to synchronize some new

state information for the specified slot. Recommended Action Reload the standby supervisor engine to force a fresh bulk synchronization. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


326

CWAN_HA Messages

Error Message %CWAN_HA-4-CCB_RECORD_ERROR: CCB record failed for slot [dec]. Explanation The high availability component for WAN modules failed to record some new state

information for the specified slot. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CWAN_HA-4-IFCFG_DFLT_LIST_ERROR: For Interface Configuration command %u, default retval list search resulted 0x%x for slot %u/%u Explanation The high availability (HA) component for WAN modules failed to synchronize new

state information for the specified slot. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show platform redundancy if-config default-retvals commands and your pertinent troubleshooting logs.

Error Message %CWAN_HA-4-IFCFG_PLAYBACK_ERROR: Interface Configuration command [int] playback failed for slot [int]/[int]. Explanation The high availability component for WAN modules failed to synchronize some new

state information for the specified slot. Recommended Action Copy the error message exactly as it appears on the console or in the system

log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.


327

CWAN_HA Messages

Error Message %CWAN_HA-4-IFCFG_RECORD_ERROR: Interface Configuration command [int] record failed for slot [int]/[int]. Explanation The high availability component for WAN modules failed to record some new state

information for the specified slot. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CWAN_HA-4-LTLSYNCFAIL: Failed to sync LTL data during [chars] for [chars] [int]: (slot=[dec],slotunit=[dec],if_num=[dec]) to standby (vlan=[int],hash=[int],ltl=[int]) Explanation Some local target logic (LTL) data did not synchronize correctly from the active to the

standby RP. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CWAN_HA-4-NOSRPBULKSYNC: Failed to [chars] srp bulk data (slot=[dec], intf=[dec], type=[dec]), ret code [dec] Explanation The synchronization of RP bulk data and SRP bulk data failed from the active supervisor

engine to the redundant supervisor engine. Recommended Action Copy the message exactly as it appears on the console or in the system log.



328

CWAN_HAL Messages

Error Message %CWAN_HA-4-NOSRPSYNC: Failed to sync srp packet (slot=[dec],intf=[dec]) to standby, HA_SYNC_STATUS=[dec] Explanation The RP dynamic synchronization of SRP packets failed from the active supervisor

engine to the redundant supervisor engine. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CWAN_HA-4-SRPSYNC: Slot [dec]: [chars] Explanation The specified error occurred while synchronizing the SRP states from the active

supervisor engine RP to the redundant supervisor engine RP. Recommended Action Copy the message exactly as it appears on the console or in the system log.


CWAN_HAL Messages This section contains Catalyst 6500 series switch and Cisco 7600 series router WAN module Halcyon (CWAN_HAL) messages.

CWAN_HAL-3 Error Message %CWAN_HAL-3-CHUNK_CREATE_FAIL: [chars] Explanation There is a problem with internal software coding. This message should not appear under




329

CWAN_HAL Messages


Error Message %CWAN_HAL-3-CHUNK_MALLOC_FAIL: [chars] Explanation There is a problem with internal software coding. This message should not appear under



Error Message %CWAN_HAL-3-DELETION_FAILED: [chars] Explanation There is a problem with internal software coding. This message should not appear under



Error Message %CWAN_HAL-3-FILL_OCE_INFO_FAIL: [chars] Explanation There is a problem with internal software coding. This message should not appear under




330

CWAN_HAL Messages


Error Message %CWAN_HAL-3-ILLEGAL_DEAGG_PROT_TYPE: [chars] Explanation There is a problem with internal software coding. This message should not appear under



Error Message %CWAN_HAL-3-ILLEGAL_OBJ_TYPE: [chars] [chars] Explanation There is a problem with internal software coding. This message should not appear under



Error Message %CWAN_HAL-3-INSERTION_OR_UPDATION_FAILED: [chars] Explanation There is a problem with internal software coding. This message should not appear under




331

CWAN_HAL Messages

Error Message %CWAN_HAL-3-LABEL_SPACE_INCONSISTENT: [chars] [chars] Explanation There is a problem with internal software coding. This message should not appear under



Error Message %CWAN_HAL-3-NULL_OBJ_HANDLE: [chars] Explanation There is a problem with internal software coding. This message should not appear under



Error Message %CWAN_HAL-3-NULL_PLT_SPACE: [chars] Explanation There is a problem with internal software coding. This message should not appear under




332

CWAN_HAL Messages

Error Message %CWAN_HAL-3-TABLE_CREATION_FAILED: [chars] [chars] Explanation There is a problem with internal software coding. This message should not appear under



Error Message %CWAN_HAL-3-TABLE_DELETION_FAILED: [chars] [chars] Explanation There is a problem with internal software coding. This message should not appear under



CWAN_HAL-4 Error Message %CWAN_HAL-4-UN_SUPPORTED_CONFIG: %s Explanation The configuration of the WAN module is not supported. A common cause is configuring

TE on a GRE tunnel. Recommended Action Copy the message exactly as it appears on the console or in the system log.



333

CWAN_IFMGR Messages

CWAN_IFMGR Messages This section contains Catalyst 6500 series switch and Cisco 7600 series router WAN module Interface Manager (CWAN_IFMGR) messages.

CWAN_IFMGR-4 Error Message %CWAN_IFMGR-4-CREATEFAIL: IM Driver Creation Failed: Interface [dec]/[dec]: [chars] Explanation Driver failed to create an interface with the interface manager. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message %CWAN_IFMGR-4-DESTROYFAIL: IM Driver Destroy Failed: Interface [dec]/[dec]: [chars] Explanation Driver failed to destroy the interface with the interface manager. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message

%CWAN_IFMGR-4-REGISTERFAIL: IM Registration Failed: [chars]

Explanation Driver failed to register with the interface manager. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.


334

CWANLC Messages

CWANLC Messages This section contains Catalyst 6500 series switch and Cisco 7600 series router WAN module (CWANLC) messages.

CWANLC-3 Error Message %CWANLC-3-FPD_INCOMPATIBLE: FPD ID=[int] image in this FPD package is for revision [int].x boards. It is incompatible with current board revision of [int].[int] Explanation This FPD package does not contain images that are compatible with the current line card

revision. Recommended Action Perform the FPD upgrade operation with a newer version of an FPD image

package that is compatible with the Cisco IOS software that is operating on the switch. Consult with the FPD image package section of the Cisco IOS software release note to confirm that your line card revision is supported for a particular release.

Error Message %CWANLC-3-CWANLC_EARL_VERSION_NOTICE: CWAN receives mismatch Earl version notification. New Earl[int] vs Earl[int] Explanation The RP determined through an SCP find operation that the version of the EARL

switching engine on the module has changed. This message occurs during a switchover operation. The version of the EARL switching engine is specified in the message text. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CWANLC-3-FATAL: [chars] Explanation The OSM encountered a fatal error. Recommended Action Copy the message exactly as it appears on the console or in the system log.



335

CWANLC Messages


Error Message %CWANLC-3-FPD_INCOMPATIBLE: FPD ID=[int] image in this FPD package is for revision [int].x boards. It is incompatible with current board revision of [int].[int] Explanation This FPD package does not contain images that are compatible with the current board

revision. Recommended Action Perform the FPD upgrade operation with a newer version of the FPD image package that is compatible with the running Cisco IOS software. Consult with the FPD image package section of the Cisco IOS software release note to confirm if your board revision is supported for a particular release.

Error Message %CWANLC-3-IPCPORT: Failed to %s IPC port ’%s’, error %s Explanation The line card failed to create a port for communication with the route processor. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CWANLC-3-LTL_NOPPEPORTMAP: Failed to retrieve default port mapping for packet processor [int] Explanation The line card software initialization was not completed correctly. Recommended Action Copy the message exactly as it appears on the console or in the system log.



336

CWANLC_ATM Messages

Error Message %CWANLC-3-TVPN_NOMEM: Failed to start vpn, not enough memory Explanation The OSM could not start VPN due to insufficient memory. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

CWANLC-5 Error Message %CWANLC-5-NOSCPPING: Linecard has not sent SCP PING responses for too long Explanation The SCP ping mechanism is used by the RP and SP processors to monitor whether the

line card that is executing Cisco IOS is in a healthy state. This SCP ping response has not been sent by the line card for a long time; the line card has exported its context information to the RP and may be power cycled. The exported context is available in the output of the show diag command. Recommended Action Save the show diag command output and contact your Cisco technical support representative if the line card is reset.

CWANLC_ATM Messages This section contains Catalyst 6500 series switch and Cisco 7600 series router WAN ATM module (CWANLC_ATM) messages.

CWANLC_ATM-3 Error Message %CWANLC_ATM-3-NOVPSPACE: [chars]: out of VP space for VPI [dec] Explanation Out of virtual paths (VPs) on the segmentation and reassembly (SAR) engine. Recommended Action Copy the message exactly as it appears on the console or in the system log.



337

CWAN_POSEIDON Messages


Error Message %CWANLC_ATM-3-VCCLOSEFAIL: [chars]: Failed to remove VC [dec]/[dec] cause [int] Explanation An attempt to remove a virtual circuit on the module failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


CWAN_POSEIDON Messages This section contains Optical Services Module (OSM) GE-WAN Route Processor (RP) driver messages.

Error Message %CWAN_POSEIDON-6-ALARM_INFO: [chars] [chars] [chars] [chars] [chars] Explanation This message is generated whenever an alarm is present in the system and the alarm

status has been reported to the RP, or an alarm has been removed from the system and the alarm status has been reported to the RP. Recommended Action This is an informational message only. No action is required.


338

CWAN_QINQ Messages

CWAN_QINQ Messages This section contains Catalyst 6500 series switch and Cisco 7600 series router WAN QinQ (CWAN_QINQ) messages.

CWAN_QINQ-3 Error Message %CWAN_QINQ-3-CWAN_POCH_QINQ_NULL_EGRESS: [chars] QinQ Ether VC have received invalid egress assignment on phyport [chars]for trunk encapsulation dot1q [int] Explanation The port channel QinQ Ether VC subinterface being configured contains an invalid

egress port assignment. The egress traffic of the OSM port will be stopped for this EVC. Recommended Action Copy the message exactly as it appears on the console or in the system log. At the line card, enter the show cwan qinq command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %CWAN_QINQ-3-CWAN_QINQ_TRUNK_DATAINCONSISTENCY: QinQ data integrity check failed for bridge-vlan [int] dot1q [int] using trunk encapsulation dot1q [int], existing record shows mapping with encapsulation dot1q [int]. Explanation A data integrity error related to QinQ was detected while a trunk was being configured for the bridge VLAN that is indicated in the message text. The error will be ignored, and the QinQ update will proceed normally. Recommended Action Enter the show cwan qinq command on the module. Copy the message exactly

as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


339

CWAN_RP Messages

CWAN_RP Messages This section contains Catalyst 6500 series switch and Cisco 7600 series router WAN route processor driver (CWAN_RP) messages.

CWAN_RP-0 Error Message %CWAN_RP-0-LCLOG_MSG : slot [dec]/[dec]: [chars] Explanation An error has occurred on a module. The slot and CPU number are indicated after the

CWAN_RP-0-LCLOG_MSG text. The error message that appears after the slot number is the original message from the module. Recommended Action Follow any instructions provided in the error message text. If no instructions

are provided, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.





340

CWAN_RP Messages

Error Message %CWAN_RP-1-OVERRIDE_MAC_INVALID: [chars] has invalid override-mac-address. Explanation The user issued an override MAC address that does not match the MAC address of the

MSFC. This condition can occur if the configuration was moved to new hardware or the MAC address command was used on another interface. While the system automatically corrects this condition, the configuration needs to be adjusted. Recommended Action Modify the override MAC address command in the configuration.




CWAN_RP-3 Error Message %CWAN_RP-3-FAILED_CONFIG: Failed to send line card config message [chars] for slot [int] port [int] Explanation The RP could not send the specified configuration message to the line card. Recommended Action Copy the message exactly as it appears on the console or in the system log.



341

CWAN_RP Messages

Error Message %CWAN_RP-3-IFCFG_CMD_NOT_OWNER: Process ’[chars]’ waiting for interface configuration command ([hex]) to slot [int]/[int] without acquiring lock owned by process ’[chars]’ Explanation A process on the RP sent a configuration command to the slot specified in the message

and a different process waited for the result. This condition could cause incorrect line card configuration states. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CWAN_RP-3-LCLOG_MSG : slot [dec]/[dec]: [chars] Explanation An error has occurred on a module. The slot and CPU number are indicated after the



Error Message %CWAN_RP-3-MODULE_TYPE: cannot find FCI for module type [int] in slot [int] Explanation An internal software error occurred while the system was detecting the module type in the specified slot. The module operation will be affected. Recommended Action Copy the message exactly as it appears on the console or in the system log.



342

CWAN_RP Messages


Error Message %CWAN_RP-3-PROCMSG: Process msg send failed for process[dec] Explanation An attempt to send a process message failed for the specified process. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CWAN_RP-3-UPGRADE_ERROR: Slot [int]: The ROMMON upgrade failed to complete. Explanation An error occurred during the upgrade process. Recommended Action If the module reloads successfully, examine the file and try the upgrade process. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %CWAN_RP-3-WAN_BRIDGING_CONFIG_EXCEEDED: The number of VPLS/EoMPLS/Bridging/QinQ VCs exceeded the maximum supported by the platform Explanation The user attempted to configure more VPLS, EoMPLS, and bridging VCs than the

number that is supported by the platform. Recommended Action Review the configuration guidelines for the features that are being configured, and reduce the number of VPLS, EoMPLS, and bridging VCs to the number that is supported by the platform.


343

CWAN_RP Messages

CWAN_RP-4 Error Message %CWAN_RP-4-CONFIG_MISMATCH: Irreconcilable Configuration difference between Active & Standby Supervisors due to OIR/Config Event -> Reloading Standby Supervisor to synchronize the configuration. Explanation An unexpected configuration difference exists between the active and standby

supervisor engines. Recommended Action The standby supervisor engine is being reloaded. No action is required.

Error Message %CWAN_RP-4-EMPTY_CWANBAYS: FLEXWAN in slot [dec] is empty. Please remove the Flexwan or insert it with atleast one PA Explanation The FlexWAN in the specified slot does not contain any port adapters. Recommended Action The FlexWAN should be removed. This is an unsupported configuration.

Error Message %CWAN_RP-4-IFCFG_CMD_TIMEOUT: Interface configuration command ([hex]) to slot [int]/[int] timed out Explanation The RP sent a configuration command to the slot specified in the message and received

no confirmation for the command. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CWAN_RP-4-INCR_CFG_SYNC_FAIL: 7600 incremental running-config sync for [[dec]/[dec]] failed - [chars]([dec]), Reload Standby Explanation The specified 7600 series router incremental running configuration synchronization has

failed. Recommended Action Power cycle the redundant supervisor engine.

Error Message %CWAN_RP-4-INVALID_UNIT: Invalid 7600 Unit: [[dec]/[dec]]. Explanation The specified 7600 series router slot and CPU are beyond the chassis limit. Recommended Action Power cycle the redundant supervisor engine.


344

CWAN_RP Messages




Error Message %CWAN_RP-4-MODULE_CONFIG_MISSING: configuration missing for slot [int] Explanation Some information is missing regarding the configuration of the module in the specified

slot. Any startup configuration for the interfaces will not be applied. If the module in the specified slot is a FlexWAN, details about the port adapters in the FlexWAN are missing from the configuration information. This information is missing from the SLOTCACHE ROMMON variable. Recommended Action If the module in the slot specified in the error message has not previously been inserted, it has no previous configuration; therefore, no action is required. If the configuration for the specified slot in the startup configuration is suitable for the module in that slot, after the module has loaded, manually apply the configuration by using one of the following two methods. The second method requires a system reload. – Enter the copy nvram:startup-config system:running-config command to reapply your saved

configuration and then enter the no shutdown command on all interfaces whose configuration was rejected. Enter the copy system:running-config nvram:startup-config command to save your configuration and the WAN module slot configuration. – Enter the copy command to copy your startup configuration to a temporary location (for

example, copy nvram:startup-config bootflash:tmp-config), and then enter the copy system:running-config nvram:startup-config command to update the WAN module slot configuration. Enter the copy command to restore the temporary copy of the startup configuration (for example, copy bootflash:tmp-config nvram:startup-config), and then enter the reload command to reload the system. After using the second method, you may want to use the delete command to remove the temporary copy of the startup configuration. To prevent this condition from recurring, ensure that the SLOTCACHE variable is updated whenever modules that require it (FlexWANs, but not OSMs) are moved between slots in the chassis. The SLOTCACHE variable is updated when the running configuration is written to the startup configuration using the copy system:running-config nvram:startup-config command (or the deprecated write memory equivalent). The two methods of restoring the configuration for the module ensure that the SLOTCACHE variable is updated.


345

CWAN_RP Messages




CWAN_RP-6 Error Message %CWAN_RP-6-ADF_FILE: Slot [int]: Using VPN-SM Upgrade File: "[chars]" Explanation The system is booting the specified upgrade image for the VPN Services Module. Recommended Action No action is required.

Error Message %CWAN_RP-6-AUX_FILE: Slot [int]: Found VPN-SM Firmware in File: "[chars]" Explanation The file specified in the message was found and will be loaded instead of the bundled

image by the VPN Services Module. Recommended Action No action is required.



are provided, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,


346

CWAN_RP Messages


Error Message %CWAN_RP-6-LC_RESET: The RP is reloaded, resetting slot [dec] is necessary. Please ignore errors if any, till the linecard comes up. Explanation If the system is running Catalyst operating system software on the supervisor engine and Cisco IOS software on the MSFC, the WAN line cards that power up before the RP powers up will be reset automatically. Recommended Action This is an informational message only. No action is required.

Error Message %CWAN_RP-6-NO_LC_IMAGE: Line card image in slot [dec] for card_id [dec] is not bundled with IOS. Explanation The line card in the specified slot will be powered down to prevent it from running an image that is not supported by the RP. If the line card image is compatible with the image running on the RP, there might be another problem with the software. Recommended Action Follow any instructions provided in the error message text. If no instructions


Error Message %CWAN_RP-6-OUT_OF_RESOURCE: [chars] configuration has exceeded available internal resources. Explanation The resources required for configuration are no longer available. They may have been

acquired by another application. Recommended Action If the requested resources have not been allocated to another application,

contact your Cisco technical support representative for further assistance.

Error Message %CWAN_RP-6-OVERRIDE: Slot [int]: ...Overriding Intrinsic VPN-SM Firmware. Explanation The specified image will be used instead of the bundled image. Recommended Action No action is required.


347

CWAN_SLOT Messages

Error Message %CWAN_RP-6-UPGRADE_COMPLETE: Slot [int]: ROMMON upgrade complete. Reset the card for the changes to take effect. Explanation The ROMMON upgrade has completed successfully. The module must be reloaded for

the changes to take effect. Recommended Action No action is required.




CWAN_SLOT Messages This section contains Catalyst 6500 series switch and Cisco 7600 series router WAN slot (CWAN_SLOT) messages.

CWAN_SLOT-1 Error Message %CWAN_SLOT-1-CF_ADDFAILED: Failed to register chkpt client, client = %d Explanation The checkpoint facility client could not be registered. Recommended Action Copy the message exactly as it appears on the console or in the system log.



348

CWAN_SP Messages


Error Message %CWAN_SLOT-1-CF_NOBUF: Failed to get chkpt buffer, client = %d Explanation The checkpoint facility could not obtain buffer memory. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

CWAN_SP Messages This section contains Catalyst 6500 series switch and Cisco 7600 series router WAN switch processor (CWAN_SP) messages.

CWAN_SP-3 Error Message %CWAN_SP-3-INIT_FAIL: Failed to allocate [dec] bytes memory needed for CWAN SP module initialization Explanation A memory allocation failure has occurred during initialization of WAN SP module. Recommended Action Upgrade to a higher memory size on the switch processor (SP).

CWAN_SP-4 Error Message %CWAN_SP-4-UNKNOWN_PW: Unknown CWAN pseudo wire on vlan [dec], port [dec]/[dec] Explanation An unknown WAN pseudowire is being used. Recommended Action Copy the message exactly as it appears on the console or in the system log.



349

CWAN_SPA Messages

CWAN_SPA Messages This section contains shared port adapter (SPA) on OSR messages.

Error Message %CWAN_SPA-3-CREATION_FAILURE: slot=[dec] subslot=[dec], spa_type=[hex], lc_type=[hex]. Explanation An attempt to create a SPA object has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CWAN_SPA-3-DIAG_CONFIG: [chars] did not complete [dec]/[dec] Explanation An error has occurred during diagnostic test. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CWAN_SPA-3-INVALID_DATA_INSTANCE: interface type [chars], slot [dec] port [dec] vc [dec] : [chars] Explanation The data required to support the specified interface is not available. Recommended Action Copy the message exactly as it appears on the console or in the system log.



350

CWAN_SPA Messages

Error Message %CWAN_SPA-3-INVALID_IF_INDEX: index= [dec], cardType=[hex], spaType=[hex], slot [dec] subSlot [dec] slotunit [dec] vc [dec] Explanation The index for the interface is not valid. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CWAN_SPA-3-INVALID_INDX_RANGE: index1= [dec], index2= [dec], maxIndex= [dec] Explanation Invalid index range. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CWAN_SPA-3-MEM_ALLOC_ERROR: [chars] Explanation A memory allocation error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



351

CWAN_SPA Messages

Error Message %CWAN_SPA-3-NULL_SPA_PTR: Explanation The pointer to a SPA object is null. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CWAN_SPA-3-NULL_VFT: [chars] virtual function table is not initialized. spaType=[hex] Explanation A required function table is not initialized. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CWAN_SPA-3-NULL_VFUNC: [chars] vector is not initialized. spaType=[hex] Explanation A required function vector is not initialized. Recommended Action Copy the message exactly as it appears on the console or in the system log.



352

CWPA Messages

Error Message %CWAN_SPA-3-POWER_CYCLE: [chars] occurred on Shared Port Adapter [int]/[int] Explanation An error has occurred that will cause the shared port adapter to be power cycled. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CWAN_SPA-3-SPA_CREATION_FAILURE: slot=[dec] subslot=[dec], PID=[chars] lc_type=[hex]. Explanation An attempt to create a SPA object has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


CWPA Messages This section contains Catalyst 6500 series switch and Cisco 7600 series router port adapter module (CWPA) messages.

CWPA-2 Error Message %CWPA-2-BAD_HWVERS: Unable to determine board hardware version Explanation The module software cannot read the module hardware version. This condition indicates

a hardware error. Recommended Action Copy the message exactly as it appears on the console or in the system log.



353

CWPA Messages


Error Message %CWPA-2-PAOIR: Port adapter OIR not supported, reloading Explanation An OIR operation occurred on the port adapters of the specified module, but OIR is not

supported on the port adapter. This error has caused the module to fail and reload. Recommended Action Do not attempt OIR on the port adapters of the specified module.

Error Message %CWPA-2-PA_VOLFAIL: Port adapter [dec]V failed, Reloading flexwan Explanation The module encountered an error involving power delivery to the module. Probable

causes for this error are an environmental condition, an overtemperature condition, or inconsistent voltage to the module. Recommended Action Verify that the input voltage and the temperature of the module are within

acceptable ranges.

Error Message %CWPA-2-WHICH_INT: Unexpected [chars] interrupt, INT status = [hex] Explanation The module specified in the error message has encountered an unexpected interrupt. Recommended Action Copy the message exactly as it appears on the console or in the system log.


CWPA-3 Error Message %CWPA-3-DIAGFAIL: Failed to handle diag [chars] [dec] Explanation The module failed to execute a diagnostics command. Recommended Action Copy the message exactly as it appears on the console or in the system log.



354

CWPA Messages


Error Message %CWPA-3-PROCCREATEFAIL: Failed to create [chars] process Explanation A module failed to create a process that is necessary for proper functioning of the

module. Recommended Action If a statistics export process was not created, check the I/O rate and the bytes

that are getting incremented in the show interface command output for the nonchannelized interfaces on the FlexWAN and Enhanced FlexWAN modules. You can also get the statistics from the show interface acc command output or the show interface stats command output. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

CWPA-4 Error Message %CWPA-4-HEADER_TOO_BIG: Needs [dec] bytes, with only [dec] bytes available. Packet size [int], received from [chars], buffer [hex] packet start [hex]: [hex]:[hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]:[hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] Explanation A packet was sent from the port adapter to either the route processor or the line card.

That packet did not have enough available space to append the header. A new particle has been linked to the packet to store the header. Recommended Action No action is required.


355

CWPABRIDGE Messages

CWPABRIDGE Messages This section contains CWPA bridging messages.

Error Message %CWPABRIDGE-3-BADLTL: [chars] got bad LTL index [hex] for vlan [int] ckt_id [int] sent from RP Explanation The RP has provided the line card with an invalid value for the local target logic (LTL)

index value. Recommended Action If the bridging traffic stops going through, copy the message exactly as it

appears on the console or in the system log. At the RP console exec prompt, enter the following commands: show log, show cwan bridge, show atm vlan, show mac-address-table dynamic detail, show cwan ltl The output of these commands will enable the engineer to gather more information about the condition. Contact your Cisco technical support representative, and provide the representative with the gathered information.

Error Message %CWPABRIDGE-3-NOCLONEDPAK: Unable to allocate pak header for cloned pak Explanation A line card is not able to allocate a pak header for a cloned pak that is used for flooding

packets among bridged WAN links. Recommended Action On the Cisco support website, use the online Software Advisor and check the

release notes for the code you are running to determine the minimum amount of memory. If you have sufficient memory and are still seeing this error message, load the previous image on the unit to return the unit to an operational state and retrieve the information needed to report this problem. Copy the contents of the line card’s crashinfo data from the cwan slot/bay bootflash: command, where slot and bay belong to the line card. When you open a TAC case, provide the line card’s crashinfo data and the output of the show tech command from the router.


356

CWRPSPA Messages

CWRPSPA Messages This section contains messages for shared port adapters (SPAs) on the Catalyst 6500 Series Switch and Cisco 7600 Series Router WAN route processor (RP).

CWRPSPA-3 Error Message %CWRPSPA-3-HWIDB_FAILURE: Creation: slot [dec] subSlot [dec] port [dec] vc [dec] Explanation Failed to create a hardware interface descriptor block (HWIDB). Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CWRPSPA-3-INVALID_PORT_NUM: slot=[dec] port=[dec], hwidbType=[hex], max_port_num=[dec], LCtype=[hex] Explanation The port number is out of range. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CWRPSPA-3-MAX_SPA: Power to IPSEC-SPA-2G in [chars] is denied because it has exceeded the number allowed([dec]) Explanation The number of IPSEC-SPA-2G port adapters in a chassis is limited. This message

displays when the number of IPSEC-SPA-2G port adapters in the chassis has exceeded the limit. Recommended Action Use only the number of supported IPSEC-SPA-2G port adapters.


357

CWRPSPA Messages

Error Message %CWRPSPA-3-NO_HOST_INFO: slot [dec] subSlot [dec], spaType [hex] Explanation Failed to get information about the host line card. Recommended Action Copy the message exactly as it appears on the console or in the system log.


CWRPSPA-4 Error Message %CWRPSPA-4-SPA_CMD_NO_RESP: [chars]: No response for interface configuration command [int] Explanation A timeout occurred while the RP was waiting for a response from the line card. This condition may occur when the line card CPU is too busy to respond to the configuration command. Recommended Action Retry the configuration command.

Error Message %CWRPSPA-4-SPA_RESP_CMD_MISMATCH: [chars]: Expecting response to interface configuration command [int] but received response to command [int]. Explanation An internal synchronization error occurred while configuring the interface. The

configuration may not have succeeded. Recommended Action Check that the running configuration for the interface is correct. If this message occurred on the standby, try reloading the standby to ensure that its configuration is in sync. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


358

CWSLC Messages

CWRPSPA-6 Error Message %CWRPSPA-6-CARDRELOAD: Module [int] reload due to SPA insert in [int]/[int]. Explanation When inserting a SPA on the specified module, the module resets. Recommended Action This message is informational. No action is required.

CWSLC Messages This section contains WAN SiByte Module (CWSLC) messages.

CWSLC-3 Error Message %CWSLC-3-DIAGFAIL: Failed to handle diag [chars] [dec] Explanation The module failed to execute a diagnostics command. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CWSLC-3-DIAGSKIP: Skipped diag for port [dec] Explanation The module skipped diagnostics for the specified port. Recommended Action Copy the message exactly as it appears on the console or in the system log.



359

CWSLC Messages

Error Message %CWSLC-3-DIAGWARNING: Backplane DIP switches settings incorrect Explanation The backplane DIP switches need to be set properly. Recommended Action Refer to the 7600 SIP and SPA Hardware Installation Guide for information about how DIP switches must be set.

Error Message %CWSLC-3-IPCALLOCFAIL: Failed to allocate IPC buffer [chars] Explanation An Enhanced FlexWAN module failed to allocate a buffer for communication with the route processor (MSFC). Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CWSLC-3-IPCSENDFAIL: Failed to send IPC message [chars] Explanation An Enhanced FlexWAN module failed to send a message to the route processor

(MSFC). Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CWSLC-3-LC_ENCAP_UPDATEFAIL: Could not update encapsulation on [chars] to [int] Explanation The line card failed to update the new encapsulation that was requested. The interface

data structures could not be temporarily locked to perform the encapsulation change Recommended Action If the interface does not come up with the new encapsulation, remove and

reconfigure the encapsulation on the interface. If the error persists after a few attempts at reconfiguration, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at


360

CWTLC Messages


CWTLC Messages This section contains WAN Optical Services Module (CWTLC) messages.

CWTLC-0 Error Message %CWTLC-0-FATAL_EXCEPTION: [chars] Explanation The OSM encountered a fatal exception. Recommended Action Copy the message exactly as it appears on the console or in the system log.


CWTLC-2 Error Message %CWTLC-2-FATAL_ATM: [chars] Explanation The OSM encountered a fatal line management interrupt. This error is not recoverable and will cause the system to fail. Recommended Action Copy the message exactly as it appears on the console or in the system log.



361

CWTLC Messages

Error Message %CWTLC-2-PCITIMEOUT: Fatal Local I-O Bus [dec] Timeout Addr = [hex] Explanation The OSM encountered a PCI timeout. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CWTLC-2-PLIM_RX: [chars] Explanation The OSM encountered an FPGA error that caused a sequence error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CWTLC-2-SLAVEPCI: [chars] Explanation The OSM encountered a PCI error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CWTLC-2-TESTCRASH: [chars] Explanation The user entered a command that caused the module to fail. Recommended Action No action is required.


362

CWTLC Messages

CWTLC-3 Error Message %CWTLC-3-ATMTXFIFO: [chars] Explanation The OSM encountered an error with the FPGA that has caused the FIFO queue to exceed

the maximum limit. This condition will cause the system to fail. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CWTLC-3-CONST_SWITCHING_BUS_INTERFACE_ASIC_ERR: Constellation Switching Bus Interface Asic [[dec]] error: [chars] Explanation The CWTLC switching bus interface ASIC received an error. Recommended Action If traffic recovers, no action is required. Otherwise, copy the message exactly

as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %CWTLC-3-CONST_SWITCHING_BUS_INTERFACE_ASIC_HWERR: Constellation Switching Bus Interface Asic [[dec]] HW error: [chars] Explanation The CWTLC switching bus interface ASIC received a hardware error and will be reset. Recommended Action If traffic recovers, no action is required. Otherwise, copy the message exactly



363

CWTLC Messages

Error Message %CWTLC-3-DMA_ENGINE_ASIC_ERR: DMA Engine Asic [[dec]] error: [chars] Explanation The CWTLC DMA engine ASIC received an error. Recommended Action If traffic recovers, no action is required. Otherwise, copy the message exactly


Error Message %CWTLC-0-DMA_ENGINE_ASIC_FATAL_ERR: DMA Engine Asic[[dec]] fatal error: [chars] Explanation The CWTLC DMA engine ASIC received a fatal error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CWTLC-3-ERR_DETAIL: [chars] Explanation This message provides additional error details for a previous message, which may be of use to your technical support representative. Recommended Action Follow the instructions for any system messages preceding this one and be sure

to include the text from this error.

Error Message %CWTLC-3-EXCEPTION_ERR: [chars] Explanation The OSM encountered an error exception. Recommended Action Copy the message exactly as it appears on the console or in the system log.



364

CWTLC Messages


Error Message %CWTLC-3-FABRIC_INTERFACE_ASIC_FATAL: OSM Fabric Interface ASIC Fatal Error. ERROR CODE: [chars] Explanation The OSM fabric interface ASIC received a fatal error. Recommended Action If traffic recovers, no action is required. Otherwise, copy the message exactly


Error Message %CWTLC-3-FABRIC_INTERFACE_ASIC_PXF: CWAN PXF Client [[dec]] Not Running Explanation An ASIC device on the OSM has detected that the designated PXF client is not running. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CWTLC-3-FR_BAD_BRIDGING: Frame Relay: old bridge-vlan([int]) or new bridge-vlan([int]) on the bridged interface [chars] is malformed Explanation This is an unexpected update from the route processor and should be ignored. Recommended Action This is an informational message only. No action is required.


365

CWTLC Messages

Error Message %CWTLC-3-FR_INTLEVEL: unexpected interrupt level invocation of frame-relay handler:[chars] if_number([dec]) dlci([dec]) Explanation Some feature code mistakenly invoked the module Frame Relay handler, which is

designed to run at process level. This condition may lead to data corruption and a module failure. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CWTLC-3-LTL_ERR: Inconsistent port selection [hex] assigment for PXF([dec]) Vlan([dec]) on PXF([int]) Explanation The port selection information stored in the database is not valid. Recommended Action Shut down the interface VLAN and restart the interface VLAN.

Error Message %CWTLC-3-MCAST_REPL_ENGINE_FATAL: Multicast Replication Engine Asic Fatal Error. Resetting ASIC. Explanation The OSM multicast replication engine ASIC received a fatal error. Recommended Action If traffic recovers, no action is required. Otherwise, copy the message exactly


Error Message %CWTLC-3-MEDUSA_FATAL: OSM Medusa ASIC Fatal Error. ERROR CODE: [chars] Explanation The OSM Medusa ASIC received the specified fatal error. Recommended Action No action is required if traffic recovers. If traffic does not recover, copy the

message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support


366

CWTLC Messages


Error Message %CWTLC-3-MEDUSAPXF: CWAN PXF Client [[dec]] Not Running Explanation An ASIC device on the OSM has detected that the specified PXF client is not running. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CWTLC-3-NOMEM: [chars] Explanation The OSM could not obtain statistics due to depleted memory. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %CWTLC-3-NO_STATID: PXF([dec]): no stat_id is available for statistics collection Explanation The OSM has used up all resources for statistics collection. No additional resources are

available for further statistics collection. Recommended Action Reduce the number of features configured on the specified PXF. If conditions

warrant, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support


367

CWTLC Messages


Error Message %CWTLC-3-OLDIOFPGA: Upgrade your I/O FPGA Explanation The OSM has an earlier release of the I/O FPGA software. Recommended Action Contact your Cisco technical support representative to upgrade the I/O FPGA

software.

Error Message %CWTLC-3-PLIM_TX: [chars] Explanation The OSM encountered an FPGA error that caused a sequence error. The module will

attempt to recover from the error. Recommended Action If the system recovers, no action is required. If the system does not recover,


Error Message %CWTLC-3-PORTERROR: Port control error, cmd=[chars], port=[dec] Explanation The port control command function has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CWTLC-3-SECPAIRINT: Unexpected VA/Toaster interrupt from second pair Explanation The OSM experienced an unexpected interrupt. Recommended Action Copy the message exactly as it appears on the console or in the system log.



368

CWTLC Messages


Error Message %CWTLC-3-TITANFATAL: Titan Fatal Error. Resetting ASIC. Explanation The OSM Titan ASIC received a fatal error. Recommended Action No action is required if traffic recovers. If traffic does not recover, copy the

message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %CWTLC-3-TMC_STATID_INCONSISTENCY: PXF([dec]):Inconsistent stats id([hex]) [int] packets dropped. Explanation The WAN module received inconsistent statistics from the PXF. The PXF reported that

a packet was dropped, but the PXF did not report the correct packet count. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CWTLC-3-TMTRIE_ALLOC_FAILED: Failed to allocate toaster mtrie nodes. Explanation The system encountered an error while it was attempting to allocate memory from a

WAN OSM component. Recommended Action Reduce the number of routes associated with a VRF identifier or upgrade the

WAN OSM to a higher version.


369

CWTLC Messages

Error Message %CWTLC-3-UNSUPPORTED_LABEL_RANGE: The maximum label range configured for this system exceeds the [int] limit supported by the OSM module. Explanation The MPLS label range configured for this system is not supported. The maximum label

range limit is specified in the message. Recommended Action Change the maximum MPLS label range by entering the mpls label range

command.

Error Message %CWTLC-3-VTMS: [chars] Explanation The OSM could not schedule the wheel entry. The reason for the error is specified in the

error message text. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CWTLC-3-VTMSQ_NOTIDLE: Queue not idle when modifying Q([hex]) Explanation The VTMS queue was in the process of being modified for a change in QoS

configuration, but packets were still going through the queue. When the queue is being modified, there is usually no traffic in the queue. Recommended Action Copy the message exactly as it appears on the console or in the system log.



370

CWTLC Messages

CWTLC-4 Error Message %CWTLC-4-ASIC_RESET: Reset asics - [chars] Explanation The ASICs on the OSM are resetting. System traffic should recover and continue

normally after the module resets. Recommended Action No action is required.

Error Message %CWTLC-4-CONST_SWITCHING_BUS_INTERFACE_ASIC_CONFIG_ERR: Constellation Switching Bus Interface Asic [[dec]] configuration failed after [dec] retries. Explanation The CWTLC switching bus interface ASIC failed to be configured correctly. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CWTLC-4-MEDUSAERROR: Medusa Error. [chars] Explanation The CWTLC Medusa ASIC received a recoverable error. Recommended Action No action is required if traffic recovers. If traffic does not recover, copy the


Error Message %CWTLC-4-PINNACLE_OLDIOFPGA: Link negotiation maybe be affected, upgrade I/O FPGA Explanation The system detected an earlier release of the I/O FPGA software. The I/O FPGA

software needs to be upgraded to the latest release. Recommended Action Upgrade the I/O FPGA software to the newest release. If you require

assistance, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved


371

CWTLC Messages

software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %CWTLC-4-PORT_ASIC_OLDIOFPGA: Link negotiation maybe be affected, upgrade I/O FPGA Explanation An earlier version of the I/O FPGA software has been detected. Recommended Action Upgrade the I/O FPGA software to the latest version. If you require assistance, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %CWTLC-4-TMC_INVALID_STATID: PXF:Invalid-Statid ([dec]) for vc [int] under interface [int] Explanation The OSM has encountered an internal error while setting up the statistics system. Recommended Action Copy the message exactly as it appears on the console or in the system log.



372

CWTLC Messages

CWTLC-5 Error Message %CWTLC-5-BUS_SEQ_ERR: Constellation bus Sequence Error. Resetting port ASICS. Explanation The SP detected a sequence error on the backplane bus of the OSM. The system called

a reset sequence from the EARL to recover from this error. System traffic should recover and continue normally. Recommended Action If traffic recovers, no action is required. If traffic does not recover, copy the


Error Message %CWTLC-5-DATAPATH_RECOVERY_PATCH: EARL reset patch invoked. Explanation The ASICs on the OSM were reset so that the module could recover from a bus sequence

error. This condition usually occurs under heavy traffic with HA-related switchover or a module OIR operation. System traffic should recover and continue normally. Recommended Action If traffic recovers, no action is required. If traffic does not recover, copy the


Error Message %CWTLC-5-FABRIC_INTERFACE_ASIC_RE_INIT: Fabric Interface Asic Re-initialize. Explanation The OSM fabric interface ASIC is being reinitialized because of a system backplane bus sequence error, a fatal ASIC error, or a line card error. Recommended Action If traffic recovers, no action is required. Otherwise, copy the message exactly

as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support


373

CWTLC Messages


Error Message %CWTLC-5-MEDUSA_RE_INIT: Medusa Re-initialize. Explanation The OSM Medusa ASIC is being reinitialized because of a system backplane bus

sequence error or a fatal ASIC error on the module itself. Recommended Action If traffic recovers, no action is required. If traffic does not recover, copy the


Error Message %CWTLC-5-PENDING_PATCH: Invoke pending data recovery patch. Explanation The ASICs on the OSM line card has been reset so that it can recover from backplane

switching bus sequence errors or local hardware ASIC errors. This condition is usually occurs under stress trafficwith HA-related switchover or a line card OIR operation. System traffic should recover and continue normally. Recommended Action If traffic recovers, no action is required. Otherwise, copy the message exactly


CWTLC-6 Error Message %CWTLC-6-FABRIC_INTERFACE_ASIC_MODECHANGE: Fabric Interface Asic switching bus Mode changed to [chars] Explanation The supervisor engine has changed the CWTLC fabric interface ASIC switching bus

mode. Recommended Action No action is required.


374

CWTLC_ATOM Messages

CWTLC_ATOM Messages This section contains Any Transport over MPLS messages for WAN Optical Services Modules (CWTLC_ATOM).

CWTLC_ATOM-3 Error Message %CWTLC_ATOM-3-INTFID_ERR: The internal interface ID [hex] for the AToM interface [chars] is invalid for the connection ID [hex] Explanation The internal interface ID that is required by the OSM to establish an AToM connection

is either invalid or is mismatched with the control plane MPLS data structure for this connection. The current interface ID of the OSM has lost its synchronization with the interface ID of the control plane for this connection. This condition is usually caused by unfavorable network conditions such as a failover operation and can occur during normal system operation. Recommended Action Enter the appropriate AToM commands for either the Frame Relay over MPLS,

Cell Relay over MPLS, AAL5 over MPLS, or Frame Relay local switching to remove the AToM connection, then add the connection again. Performing this action once should successfully reestablish the connection.

Error Message %CWTLC_ATOM-3-OSM_BB1_CONFIG_UNSUPPORTED: Attempt to configure Frame Relay over MPLS or Frame Relay localswitching on a non-enhanced OSM Explanation Frame Relay over MPLS and Frame Relay local switching features are supported only

on enhanced Optical Services Modules. Nonenhanced OSMs do not support these features. Recommended Action Remove the configuration of the unsupported features, or upgrade this module to an enhanced OSM.

CWTLC_CHOC Messages This section contains Cyclops Channelized OC48/OC12 (CWTLC_CHOC) messages.

CWTLC_CHOC-3 Error Message %CWTLC_CHOC-3-HWERROR: [chars] Explanation The module hardware has experienced the specified error. Recommended Action Copy the message exactly as it appears on the console or in the system log.



375

CWTLC_CHOC_DSX Messages


CWTLC_CHOC_DSX Messages This section contains Optical Services Module (OSM) CHOC DSX LC common messages.

Error Message %CWTLC_CHOC_DSX-3-HWERROR: [chars] Explanation A hardware error involving the OSM line card has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


CWTLC_CHOCX Messages This section contains Optical Services Module (OSM) Channelized OC12/OC3 module (CWTLC_CHOCX) messages.

CWTLC_CHOCX-3 Error Message %CWTLC_CHOCX-3-HWERROR: [chars] Explanation The module hardware has experienced the specified error. Recommended Action Copy the message exactly as it appears on the console or in the system log.



376

CWTLC_GEWAN Messages

CWTLC_GEWAN Messages This section contains Gigabit Ethernet WAN module (CWTLC_GEWAN) messages.

CWTLC_GEWAN-3 Error Message %CWTLC_GEWAN-3-FPGA_PROG_FAILED: [chars] FPGA initialization failed due to [chars] Explanation The FPGA could not be initialized. The cause of this condition is specified in the

message text on the console or in the system log. As a result of this condition, the device is not operational and has been disabled. Recommended Action Reload the line card. If the problem persists, copy the message exactly as it

appears on the console or in the system log. Enter the show module command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %CWTLC_GEWAN-3-GEMAC_9K_MODE_FIX_FAILED: Fix for 9k buffer mode failed for GEMAC[[dec]] Explanation An error has occurred while the system was setting the GEMAC component of the Gigabit Ethernet WAN module in 9,000-buffer mode (a buffer mode that supports jumbo frames). This condition occurred on the port specified in the error message. Recommended Action Copy the message exactly as it appears on the console or in the system log.



377


Error Message %CWTLC_GEWAN-3-GEMAC_INIT_FAILED: Device initialization failed for GEMAC[[dec]] Explanation An error occurred during initialization of the GEMAC device. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CWTLC_GEWAN-3-IF2PORT: Cannot determine port from interface [dec] for operation [dec] with [[enet]] Explanation The port number could not be determined from the given interface number. Recommended Action Reload the line card. If the problem persists, copy the message exactly as it


Error Message %CWTLC_GEWAN-3-MAC_OP_BAD: Unknown MAC address operation [dec] with [[enet]] on port [dec] Explanation The specified MAC address operation is unknown and cannot be performed. Recommended Action Reload the line card. If the problem persists, copy the message exactly as it



378


Error Message %CWTLC_GEWAN-3-PORT_AUTONEG_FAIL: Failed to [chars] auto-negotiation [chars] on port [dec] Explanation The enabling/disabling of the auto-negotiation functionality on a GE-WAN port has

failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CWTLC_GEWAN-3-PORT_CMD_FAIL: Port [chars] failed on port [dec] Explanation A GE-WAN port command has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CWTLC_GEWAN-3-TABLE_ADD_REMOVE_FAILED: MAC address table [chars] with [[enet]] failed on port [dec] Explanation The addition or removal of a MAC address from the MAC address table has failed. Recommended Action Reload the line card. If the problem persists, copy the message exactly as it



379

CWTLC_GEWAN-5

Error Message %CWTLC_GEWAN-3-ZICO_INIT_FAILED: Device initialization failed for Zico FPGA[[dec]] Explanation An error occurred during initialization of the protocol converter FPGA. Recommended Action Copy the message exactly as it appears on the console or in the system log.


CWTLC_GEWAN-5 Error Message %CWTLC_GEWAN-5-GEMAC_INTR: [chars]: [chars] Explanation The GEMAC component of the Gigabit Ethernet WAN module caused an error

interruption. Recommended Action Reload the module. If the problem persists, copy the message exactly as it


Error Message %CWTLC_GEWAN-5-LINKFPGA_INTR: Index[[dec]] Cause[[hex]]: [chars] Explanation The link FPGA component of the Gigabit Ethernet WAN module caused an error

interruption to occur. Recommended Action Reload the module. If the problem persists, copy the message exactly as it



380

CWTLC_QOS Messages

CWTLC_QOS Messages This section contains Optical Services Module (OSM) supervisor engine line card QoS messages.

Error Message %CWTLC_QOS-3-CHUNK_INIT_FAIL: [chars]: [chars] allocation failed Explanation The OSM detected a memory allocation failure. The installed amount of memory could

be insufficient for the software features that are configured. Recommended Action If this message appears continuously, a memory upgrade might be required.

Error Message %CWTLC_QOS-3-CHUNK_MALLOC_FAIL: [chars]: chunk_malloc for [chars] failed Explanation The OSM detected a memory allocation failure. The installed amount of memory could

be insufficient for the software features that are configured. Recommended Action If this message appears continuously, a memory upgrade might be required.

Error Message %CWTLC_QOS-3-MISC: [chars]: [chars] [dec] Explanation The OSM detected the software error event that is specified in the message text. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %CWTLC_QOS-4-STATS_CLASS_INFO_INVALID: Stats process found invalid class_info [[hex]], stat_type [[hex]] caller_pc [[hex]] caller_pc1 [[hex]].

Explanation The OSM has detected invalid class data. This condition is transient when the policy map is modified and the update is propagated to the OSM. Recommended Action If this message appears continuously, reset theline card by entering the hw-module module reset command. Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support


381

CWTLC_RP Messages


Error Message %CWTLC_QOS-3-WRED_CLASS_INDEX_NOT_FOUND: sub-class limit has exceeded Explanation The OSM supports only 29 WRED classes: 8 CS, 12 AF, 1 EF, and 8 user-defined DSCP

values. Recommended Action Refer to the technical documentation for more information about WRED

configurations on the OSM.

CWTLC_RP Messages This section contains WAN Toaster-based module route processor (CWTLC_RP) messages.

CWTLC_RP-3 Error Message %CWTLC_RP-3-TMEM_IMPROPER_SEL: Improperly nested PXF [int] memory select/deselect at nested level [int]. Value stored with select ([hex]) does not match the value passed with deselect ([hex]) Explanation The last PXF select operation was not followed by a deselect operation. Recommended Action Copy the message exactly as it appears on the console or in the system log.



382

DBUS Messages

DBUS Messages This section contains data bus (DBUS) messages.

DBUS-3 Error Message %DBUS-3-MSGPABADCONFIG: Slot [dec] has an unsucessfully configured PA in bay [dec] Explanation The port adapter (PA) in the slot is not sucessfully configured, either because the VIP is incompatible with it or because the Cisco IOS has no pertinent drivers. Recommended Action Refer to the documentation of the PA to get a list of compatible VIPs. If the VIP that contains the PA is listed as supported, verify that your Cisco IOS version supports the PA. Otherwise, place the PA in one of the supported VIPs and verify that the Cisco IOS version supports the PA.

Error Message %DBUS-3-MSGPAUNSUP: Slot [dec] has an unsupported PA in bay [dec] Explanation The port adapter (PA) in the slot is not supported, either because the VIP is incompatible

with it or because the Cisco IOS has no pertinent drivers. Recommended Action Refer to the documentation of the PA to get a list of compatible VIPs. If the VIP that contains the PA is listed as supported, verify that your Cisco IOS version supports the PA. Otherwise, place the PA in one of the supported VIPs and verify that the Cisco IOS version supports the PA.

Error Message

%DBUS-3-ORFS_NOTINITIALIZED: ORFS is not initialized

Explanation When the OIR Remove Failing Slot (ORFS) feature is configured, the software attempts

to initialize parameters. This initialization failed and the service will not be available. Recommended Action Try entering the service oir-remove-failing-slot command again. This error message should not cause any functional failures. If the message causes a Cisco IOS performance issue, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


383

DEV_SELENE Messages

DEV_SELENE Messages This section contains messages related to the Selene FPGA device.

DEV-SELENE-3 Error Message %DEV_SELENE-3-DEV_INIT_FAILURE: Selene [dec] initialization failed. Explanation The initailazation of the Selene FPGA device on this linecard failed. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %DEV_SELENE-3-EFIFO_ECC: Selene [dec] Egress [dec] Burst FIFO Read ECC error Explanation A FIFO ECC error condition was detected in a FPGA device on the linecard. This may

be caused by a hardware malfunction. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %DEV_SELENE-3-FIFO_ECC: Selene [dec] Ingress [dec] [chars] Priority FIFO Read ECC Error Explanation An ECC Error was detected while reading from a queue in a FPGA device on the

linecard. This may be caused by a hardware malfunction. Recommended Action Copy the error message exactly as it appears on the console or in the system



384

DEV_SELENE Messages

Error Message %DEV_SELENE-3-FIFO_FULL: Selene [dec] Ingress [dec] [chars] Priority FIFO Full Explanation An ingress packet queue full condition was detected in a FPGA device on the linecard.

This may be caused by a flow-control misconfiguration due to incorrect software. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %DEV_SELENE-3-FIFO_SEQ: Selene [dec] Egress [dec] Burst FIFO Read Sequence error Explanation A FIFO sequence error condition was detected in a FPGA device on the linecard. This

may be caused by a hardware malfunction. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %DEV_SELENE-3-INV_POE: Selene [dec] Egress [dec] Invalid POE error, [hex] Explanation An invalid Port of Exit error condition was detected in a FPGA device on the linecard.

This may be caused by incorrect software. Recommended Action Copy the error message exactly as it appears on the console or in the system



385

DEV_SELENE Messages

Error Message %DEV_SELENE-3-INV_VLAN: Selene [dec] Egress [dec] Invalid Vlan error Explanation An invalid vlan error condition was detected in a FPGA device on the linecard. This may be caused by a software error. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %DEV_SELENE-3-MRX_CRC: Selene [dec] Metropolis Rx [dec] Packet CRC Error Explanation A packet checksum error was detected in a FPGA device on the linecard. This may be

caused by a hardware malfunction. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %DEV_SELENE-3-MRX_FCS: Selene [dec] Metropolis Rx [dec] Packet Header Checksum Error Explanation A packet header checksum error was detected in a FPGA device on the linecard. This




386

DEV_SELENE Messages

Error Message %DEV_SELENE-3-MRX_GNT: Selene [dec] Metropolis Rx [dec] Giant Packet Error Explanation A giant frame was received in a FPGA device on the linecard. This may be due to

incorrect software. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %DEV_SELENE-3-MRX_LEN: Selene [dec] Metropolis Rx [dec] Packet Length Mismatch Explanation An incorrect length was detected for packet received in a FPGA device on the linecard.

This may be caused by a hardware malfunction. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %DEV_SELENE-3-MRX_MIN: Selene [dec] Metropolis Rx [dec] Minimum Packet Length Error Explanation A frame smaller than the minimum size was received in a FPGA device on the linecard.

This may be due to incorrect software. Recommended Action Copy the error message exactly as it appears on the console or in the system



387

DEV_SELENE Messages

Error Message %DEV_SELENE-3-MRX_SEQ: Selene [dec] Metropolis Rx [dec] Sequence Error Explanation A sequence error was detected in a FPGA device on the linecard. This may be caused

by a hardware malfunction. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %DEV_SELENE-3-SRAM_ECC: Selene [dec] SRAM [chars] [chars] ECC error, error status: [hex] Explanation An ECC error was detected in SRAM memory in a FPGA device on the linecard. This



Error Message %DEV_SELENE-3-XAUI_CODE: Selene [dec] XAUI [dec] Coding Error Explanation A XAUI lane coding error was detected in a FPGA device on the linecard. This may be

caused by a hardware malfunction Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %DEV_SELENE-3-XAUI_CRC: Selene [dec] XAUI [dec] Checksum Error Explanation A XAUI interface checksum error was detected in a FPGA device on the linecard. This may be caused by a hardware malfunction Recommended Action Copy the error message exactly as it appears on the console or in the system



388

DEV_SELENE Messages


Error Message %DEV_SELENE-3-XAUI_FRM: Selene [dec] XAUI [dec] Framing error Explanation XAUI interface framing error was detected on a FPGA device on the linecard. This may



Error Message %DEV_SELENE-3-XAUI_GNT: Selene [dec] XAUI [dec] Giant Frame Error Explanation A giant frame was detected in a FPGA device on the linecard. This may be due to

incorrect software. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %DEV_SELENE-3-XAUI_LEN: Selene [dec] XAUI [dec] Packet Length Error Explanation A packet with bad length value was detected in a FPGA device on the linecard. This may

be caused by incorrect Network Processor software. Recommended Action Copy the error message exactly as it appears on the console or in the system



389

DEV_SELENE Messages

Error Message %DEV_SELENE-3-XAUI_MIN: Selene [dec] XAUI [dec] Min Packet Size Error Explanation A frame smaller than the minimum allowed size was detected in a FPGA device on the

linecard. This may be due to incorrect software. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %DEV_SELENE-3-XAUI_RX_RDY: Selene [dec] XAUI [dec] Rx Rdy changed state Explanation XAUI interface on a FPGA device on the linecard changed receive ready state. This may



Error Message %DEV_SELENE-3-XAUI_SEQ: Selene [dec] XAUI [dec] Sequence Error Explanation A XAUI interface sequence error was detected in a FPGA device on the linecard. This

may be caused by a hardware malfunction Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %DEV_SELENE-3-XAUI_TX_ECC: Selene [dec] XAUI [dec] Tx FIFO ECC error Explanation A FIFO queue ECC error was detected in a FPGA device on the linecard. This may be

caused by a hardware malfunction. Recommended Action Copy the error message exactly as it appears on the console or in the system



390

DEV_SELENE Messages


Error Message %DEV_SELENE-3-XAUI_TX_FULL: Selene [dec] XAUI [dec] Tx FIFO Full Explanation A FIFO queue full condition was detected in a FPGA device on the linecard. This may



Error Message %DEV_SELENE-3-XAUI_TX_RDY: Selene [dec] XAUI [dec] Tx Rdy changed state Explanation XAUI interface on a FPGA device on the linecard changed transmit ready state. This



DEV-SELENE-5 Error Message %DEV_SELENE-5-FC_CS: Selene [dec] Channel [int] Egress Flow-control Status change Explanation A flow-control status change was detected between a FPGA device and a network

processor on the linecard. Recommended Action No action is required.


391

DFP Messages

DFP Messages This section contains Dynamic Feedback Protocol messages.

Error Message %DFP-4-ENQUEUE: Process enqueue failed: [chars] Explanation An unexpected error occurred while enqueueing a DFP element. Recommended Action If this message recurs, copy the message exactly as it appears on the console


DHCPD Messages This section contains Dynamic Host Configuration Protocol daemon (DHCPD) messages.

DHCPD-2 Error Message %DHCPD-2-(-1): DHCP could not start its [chars] process. Explanation The DHCP process could not start one of its processes. Recommended Action Upgrade to a larger memory configuration.


392

DHCP_SNOOPING Messages

DHCP_SNOOPING Messages This section contains Dynamic Host Configuration Protocol Snooping (DHCP_SNOOPING) messages.

DHCP_SNOOPING-3 Error Message %DHCP_SNOOPING-3-DHCP_SNOOPING_INTERNAL_ERROR: DHCP Snooping internal error, [chars] Explanation A software verification test failed in the DHCP snooping process. Recommended Action Copy the message exactly as it appears on the console or in the system log.


DHCP_SNOOPING-4 Error Message %DHCP_SNOOPING-4-AGENT_OPERATION_FAILED: DHCP snooping binding transfer failed. [chars] Explanation This message provides the reason for failure when a database transfer has failed. Recommended Action No action is required.

Error Message %DHCP_SNOOPING-4-AGENT_OPERATION_FAILED_N: DHCP snooping binding transfer failed([dec]). [chars] Explanation This message provides the reason for failure when a database transfer has failed. This

log message is rate limited. Recommended Action No action is required.

Error Message %DHCP_SNOOPING-4-DHCP_SNOOPING_ERRDISABLE_WARNING: DHCP Snooping received [dec] DHCP packets on interface [chars] Explanation DHCP Snooping detected a DHCP packet rate limit violation on a particular interface.

The interface will be error disabled. Recommended Action No action is required.


393


Error Message %DHCP_SNOOPING-4-IP_SOURCE_BINDING_PVLAN_WARNING: IP source filter may not take effect on secondary vlan [dec] where IP source binding is configured. [chars] Explanation If the private VLAN feature is enabled, the IP source filter on the primary VLAN will

automatically propagate to all secondary VLANs. Recommended Action No action is required.

Error Message %DHCP_SNOOPING-4-QUEUE_FULL: Fail to enqueue DHCP packet into processing queue: [chars], the queue is most likely full and packet will be dropped. Explanation DHCP packets are coming into the CPU at a much higher rate than the DHCP snooping

process can handle them. These unhandled DHCP packets will be dropped to prevent system from denial of service attack. Recommended Action No action is required.

Error Message %DHCP_SNOOPING-4-SSO_SYNC_ACK_ERROR: Error is encountered in processing acknowledgement for DHCP snooping binding sync, %s. ack message txn id: 0x%x Explanation An error occurred in handling the acknowledgement of DHCP snooping binding

synchronization. This message is usually caused by the ACK message being ignored. Recommended Action No action is required.

Error Message %DHCP_SNOOPING-4-STANDBY_AGENT_OPERATION_FAILED: DHCP snooping binding transfer failed on the Standby Supervisor. %s Explanation This message provides the reason of failure when a database transfer has failed on the standby supervisor. Recommended Action No action is required.

DHCP_SNOOPING-5 Error Message %DHCP_SNOOPING-5-DEST_NOT_FOUND: %s: Could not find destination port. Destination MAC %e Explanation The switch is unable to determine the destination port for a DHCP reply. This message

may be an indication of a malicious user connected to the port. Recommended Action Using debug commands, identify the users that are attached to the port. Enter the debug ip dhcp snooping mac-addr command, where mac-addr is the MAC address shown in the error message. Any subsequent DHCP packet that is received with mac-addr as the source MAC or DHCP CHADDR (client hardware address) will cause a message to appear on the console indicating the port from which the packet originated. If the error message recurs, check the user connected to the port indicated in the debug message.


394


DHCP_SNOOPING-6 Error Message %DHCP_SNOOPING-6-AGENT_OPERATION_SUCCEEDED: DHCP snooping database [chars] succeeded. Explanation The given binding transfer has succeeded. This message is logged only once after some

failure to indicate that the switch has recovered from failures. Recommended Action No action is required.

Error Message %DHCP_SNOOPING-6-BINDING_COLLISION: Binding collision. [dec] bindings ignored Explanation The given number of bindings from the database file have been ignored when the file is

read. The bindings are ignored because the system has a binding for the given MAC address and VLAN combination by the time the switch read the ignored binding from the file. Recommended Action No action is required.

Error Message %DHCP_SNOOPING-6-INTERFACE_NOT_VALID: Interface not valid. [dec] bindings ignored. Explanation The given number of bindings from the database file have been ignored when the file is

read. The bindings are ignored because the interface specified by the ignored binding either does not exist in the system or it’s a router or DHCP snooping trusted port. Recommended Action No action is required.

Error Message %DHCP_SNOOPING-6-LEASE_EXPIRED: Lease Expired. [dec] bindings ignored. Explanation The specified number of bindings from the database file have been ignored when the file

is read. The bindings are ignored because their lease has expired. Recommended Action No action is required.

Error Message %DHCP_SNOOPING-6-PARSE_FAILURE: Parsing failed for [dec] bindings. Explanation The specified number of bindings from the database file have been ignored when the file

is read. The bindings are ignored because of parsing failures. Recommended Action No action is required.


395

DHCP_SNOOPING_CAT3550 Messages

Error Message %DHCP_SNOOPING-6-VLAN_NOT_SUPPORTED: Vlan not supported. [dec] bindings ignored. Explanation The specified number of bindings from the database file have been ignored when the file

is read. The bindings are ignored because the VLAN specified by the ignored binding no longer exists in the system. Recommended Action No action is required.

DHCP_SNOOPING_CAT3550 Messages This section contains Dynamic Host Configuration Protocol Snooping (DHCP_SNOOPING) messages for the Cisco Catalyst 3550.

DHCP_SNOOPING_CAT3550-3 Error Message %DHCP_SNOOPING_CAT3550-3-MVR_INSTALL: Cannot install [chars] ACLs for DHCP Snooping, probably no TCAM space Explanation There is insufficient space in the TCAM to install the specified ACLs for DHCP

snooping. Recommended Action Reduce the number of PACLs or VACLs to make space in the TCAM.

Error Message %DHCP_SNOOPING_CAT3550-3-UNEXPECTED_EVENT: Process received unknown event (major [hex], minor [hex]). Explanation A process can register to be notified when various events occur in the router. This

message indicates that a process received an event it did not know how to handle. Recommended Action Copy the message exactly as it appears on the console or in the system log.



396

DHCP_SNOOPING_ISSU Messages

DHCP_SNOOPING_ISSU Messages This section contains Dynamic Host Configuration Protocol Snooping (DHCP_SNOOPING) in-service software upgrade (ISSU) messages.

DHCP_SNOOPING_ISSU-2 Error Message %DHCP_SNOOPING_ISSU-2-GET_BUFFER: DHCP Snooping ISSU client failed to get buffer for message. Error: %d (%s) Explanation The DHCP snooping ISSU client failed to get buffer space for building a negotiation

message. A negotiation message cannot be sent to the standby device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %DHCP_SNOOPING_ISSU-2-INIT: DHCP Snooping ISSU client initialization failed to %s. Error: %d (%s) Explanation The DHCP snooping ISSU client could not be initialized. This initialization failure must

be addressed before an in-service software upgrade or downgrade can be performed successfully. Otherwise, a software upgrade or downgrade will result in downtime. Recommended Action Copy the message exactly as it appears on the console or in the system log.



397


Error Message %DHCP_SNOOPING_ISSU-2-SEND_NEGO_FAILED: DHCP Snooping ISSU client failed to send negotiation message. Error: %d (%s) Explanation The DHCP snooping ISSU client failed to send a session negotiation message to the peer device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %DHCP_SNOOPING_ISSU-2-SESSION_NEGO: DHCP Snooping ISSU client encountered unexpected client nego_done. Error: %d (%s) Explanation An ISSU-compliant client transitions through a series of internal states. The DHCP

snooping ISSU client encountered a ’client negotiation done’ state that was unexpected. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %DHCP_SNOOPING_ISSU-2-SESSION_REGISTRY: DHCP Snooping ISSU client failed to register session information. Error: %d (%s) Explanation The DHCP snooping ISSU client failed to register session information. If a problem occurs with the ISSU session registration, the standby device cannot be brought up properly. Recommended Action Copy the message exactly as it appears on the console or in the system log.



398



DHCP_SNOOPING_ISSU-3 Error Message %DHCP_SNOOPING_ISSU-3-INVALID_SESSION: DHCP Snooping ISSU client does not have a valid registered session. Explanation The DHCP snooping ISSU client does not have a valid registered session. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %DHCP_SNOOPING_ISSU-3-MSG_NOT_OK: DHCP Snooping ISSU client ’Message Type %d’ is not compatible Explanation The DHCP snooping ISSU client received an incompatible message from the peer

device. The message cannot be processed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %DHCP_SNOOPING_ISSU-3-MSG_SIZE: DHCP Snooping ISSU client failed to get the MTU for Message Type %d. Error: %d (%s) Explanation The DHCP snooping ISSU client was unable to calculate the MTU for the specified

message. The DHCP snooping ISSU client is not able to send the message to the standby device. Recommended Action Copy the message exactly as it appears on the console or in the system log.



399


information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs.

Error Message %DHCP_SNOOPING_ISSU-3-SESSION_UNREGISTRY: DHCP Snooping ISSU client failed to unregister session information. Error: %d (%s) Explanation The DHCP snooping ISSU client failed to unregister session information. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %DHCP_SNOOPING_ISSU-3-TRANSFORM_FAIL: DHCP Snooping ISSU client %s transform failed for ’Message Type %d’. Error: %d (%s) Explanation The DHCP snooping ISSU client could not transform the specified message type. If the

transmit transformation failed, the checkpoint message was not sent to the standby device. If the receive transformation failed, the checkpoint message was not applied on the standby device. In either case, the DHCP snooping state between the active device and the standby device is not identical. Recommended Action Copy the message exactly as it appears on the console or in the system log.



400

DHCPV6C Messages

DHCPV6C Messages This section contains DHCPv6 client messages.

Error Message %DHCPV6C-3-NOPACKET: Cannot setup or duplicate a socket packet Explanation An error occurred that is probably related to a resource problem within the system. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message %DHCPV6C-3-NOSOCKET: Cannot create DHCPv6 client socket Explanation A DHCPv6 socket could not be created. This error is probably the result of either IP not

being enabled on any interface or a resource problem with the system. Recommended Action Enable IP on the interface. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

DHCPV6S Messages This section contains DHCPv6 server messages.

Error Message %DHCPV6S-3-DBNOTLOADED: Binding database not loaded Explanation A DHCPv6 binding database could not be loaded. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %DHCPV6S-3-DBOPEN: Openning [chars]: [chars] Explanation A DHCPv6 binding database file could not be opened. Recommended Action Copy the message exactly as it appears on the console or in the system log.



401

DHCPV6S Messages


Error Message %DHCPV6S-3-DBREAD: Reading file: [chars] Explanation A DHCPv6 binding database file could not be read. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %DHCPV6S-3-DBWRITE: Writing file: [chars] Explanation The system could not write to a DHCPv6 binding database file. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %DHCPV6S-3-NOPACKET: Cannot setup or duplicate a DHCPv6 server socket packet Explanation An error occurred that is probably due to a resource problem within the system. Recommended Action No action is required.


402

DIAG Messages

DIAG Messages This section contains online diagnostics (DIAG) messages.

DIAG-3 Error Message %DIAG-3-ALWAYS_ENABLE_TEST: [chars]: The users are not allow to disable monitoring for Test #[dec] Explanation The specified health monitoring test cannot be disabled. Recommended Action No action is required. The system is working properly.

Error Message %DIAG-3-FIXED_INTERVAL_TEST: [chars]: The users are not allow to change monitoring interval of Test #[dec] Explanation The specified health monitoring test interval cannot be changed. Recommended Action No action is required. The system is working properly.

Error Message %DIAG-3-INVALID_DEVICE: Invalid device number : [chars] Explanation The system made a diagnostics request on a device that does not exist. Recommended Action Ensure that the specified device number exists and is valid.

Error Message %DIAG-3-INVALID_MONITORING_INTERVAL: [chars]: The [chars][ID=[dec]] monitoring interval must be at least [dec] millisec Explanation The specified test monitoring interval is too small. Recommended Action No action is required. The system is working properly.

Error Message %DIAG-3-INVALID_TEST: Invalid test: [chars] Explanation A test that does not exist was requested. [chars] describes the test. Recommended Action Ensure the specified test is supported by the switching module. The list of

available tests and their associated test IDs can be retrieved using the show diagnostic content command.

Error Message %DIAG-3-MONITOR_DISABLE: [chars]: The monitoring test:[dec] is disable since default interval is Zero Explanation The specified test is no longer a health-monitoring test. Recommended Action No action is required. The system is working properly.


403

DIAG Messages

Error Message %DIAG-3-MONITOR_INTERVAL_ZERO: [chars]: Monitoring interval is 0. Cannot enable monitoring for Test #[dec] Explanation The system cannot enable health monitoring for the specified test because the interval is set to zero. Recommended Action Reset the health monitoring interval for the test, and reenable health

monitoring.

Error Message %DIAG-3-NOT_MONITORING_TEST: [chars]: The test:[dec] cannot be used as health monitoring test Explanation The specified test is not a health-monitoring test. Recommended Action No action is required. The system is working properly.

Error Message %DIAG-3-TEST_SKIPPED: [chars]: [chars]{ID=[dec]} is skipped Explanation The diagnostic test cannot be run. Recommended Action No action is required. The system is working properly.

DIAG-4 Error Message %DIAG-4-CONFIG_REAPPLY: Please reapply config command [chars] after the card is online. Explanation This message appears when the specified configuration command cannot be applied.

[chars] is the configuration command that you must reapply. Recommended Action The system is working properly and the specified command cannot be applied.

Reapply the configuration command after the module is online.

DIAG-6 Error Message %DIAG-6-SCHEDULE_IS_REMOVED: [chars]: Schedule Diagnostic for [[chars] [chars] [dec]:[dec].] is removed Explanation The scheduled online diagnostics test was removed because the test is no longer

applicable. Recommended Action No action is required. The system is working properly.


404

DIAG Messages

Error Message %DIAG-6-SIMULATED_TEST_RESULT: [chars]: [chars] test result is simulated. Explanation The result of the specified test is simulated. The message does not indicate a software

or hardware fault. The first [chars] is the message notification and the second [chars] is the test name. Recommended Action No action is required. The test failure is simulated as specified by the user.

Error Message %DIAG-6-SKIP_ONDEMAND_ACTIVE_TO_STANDBY_TEST: [chars]: [chars] cannot be executed. Explanation The diagnostics test is bypassing the specified redundant test because the redundant test

cannot be executed. Recommended Action No action is required. The system is working properly.

Error Message %DIAG-6-TEST_SKIPPED_FROM_ACTIVE: [chars]: [chars] cannot be executed from active supervisor. Explanation The specified test cannot be run from the active supervisor engine. Recommended Action No action is required. The test cannot be run, but the system is working

properly.

DIAG-SP Error Message %DIAG-SP-6-DIAG_OK: %s: Passed %s Explanation The diagnostic tests did not detect any error on the card. Recommended Action This is an informational message stating that the line card passed the diagnostic

tests.

Error Message %OIR-SP-6-DOWNGRADE_EARL: Module %d %s installed is not identical to system PFC and will perform at current system operating mode. Explanation The PFC/DFC module is at a higher hardware revision than the level of the system PFC.

The PFC/DFC module will operate at the same level as that of the system PFC. Recommended Action No action is required.

Error Message %DIAG-SP-6-RUN_MINIMUM: %s: Running Minimal Diagnostics... Explanation Minimum Diagnostic is running on the card Recommended Action This is an informational message and the system is working properly.


405

DLSWC Messages

DLSWC Messages This section contains Data-link Switching System messages.

DLSWC-3 Error Message %DLSWC-3-NOPEER: [chars] Explanation A data-link switching system error occurred. Recommended Action Copy the error message exactly as it appears on the console or in the system


DLSWP Messages Error Message %DLSWP-3-PEERFAILURE: [chars] [chars] Explanation A DLSW peer failed:

- keepalive failure, dlsw between cisco peers is sending a peer keepalive by default every 30 sec. After missing 3 consecutive keepalives the peer is taken down. - We are not promiscuous, Rej conn from peer a.b.c.d The local dlsw peer is not configured for promiscuous and we receive a request to open a dlsw peer for which we have no corresponding dlsw remote peer statement. - received tcp fini, dlsw peer code has received a tcp fini from the underlaying tcp subsystem. To obey the tcp fini dlsw wring bring down the peer connection for which the tcp fini was received. Recommended Action - keepalive failure. Check end to end connectivity between the DLSW peers

-We are not promiscuous, Rej conn from peer a.b.c.d correct your configuration. - received tcp fini, Check the underlaying tcp connection between the two dlsw peers.


406

DM Messages

DM Messages This section contains Dispatch Manager (DM) messages.

Error Message %DM-1-CORRUPT_MLIST: [chars]: attached-message list corrupted -[[dec],[dec]] overlaps [[dec],[dec]] Explanation A Dispatch Manager list of attached messages was found to be corrupt. Recommended Action This is an internal error and should be reported to TAC. A memory dump

should be taken (to assist TAC) and the application should be restarted.

Error Message %DM-4-FATTACH: [chars]: event_file_attach failure for fd [dec], cond [dec]: [chars]. Explanation An ionotify call to request a file-state notification has failed. Recommended Action This is an internal error and should be reported to TAC. The server process for the failed fd has died or there is a connectivity failure. If you can determine which server failed, restart that server and the application with the ionotify error. If that fails, reboot the router.

Error Message %DM-1-HANDLE: [chars]: invalid dispatch danager handle -- [hex] Explanation A Dispatch Manager call was made with an invalid dispatch manager handle. Recommended Action This is an internal error and should be reported to TAC. The application process making the call has corrupted data or some other internal error. Restart the application. If that fails, reboot the router.

Error Message %DM-7-HEAP: [chars]: could not allocate from heap Explanation A Dispatch Manager library function was not able to obtain HEAP memory space. Recommended Action Either some process is using too much memory or there is not enough physical

memory available in the router. Determine if an application is misbehaving by checking the amount of memory allocated to each application and noting whether one is unusually large. If there are no misbehaving applications, memory should be added to the router.

Error Message %DM-4-RMCONTEXT: [chars]: could not allocate memory for Resource Manager context Explanation The Dispatch Manager could not allocate memory to construct a Resource Manager

context when delivering an RM message. Recommended Action Either some process is using too much memory or there is not enough physical



407

DM Messages

Error Message %DM-4-SIGACTION: [chars]: could not install signal handler for signal [dec] [chars] Explanation The Dispatch Manager signal thread must install a signal handler for each signal that it

is watching. Recommended Action This is an internal error. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %DM-4-SIGHEAP: [chars]: could not allocate memory to deliver signal [dec] [attempt [dec] of [dec]] Explanation The Dispatch Manager signal thread could not allocate memory needed to deliver a

signal message to the Dispatch Manager message channel. The Dispatch Manager will try to work around the problem by sending itself the same signal a few times. Recommended Action Either some process is using too much memory or there is not enough physical


Error Message %DM-1-SIGPATCH: [chars]: unexpected signal [dec] received Explanation The Dispatch Manager signal handler should never be invoked directly. Recommended Action This is an internal error. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %DM-1-TIMEOUT: [chars]: timeout call failed, handle [hex] Explanation A Dispatch Manager blocking call was made with an invalid timeout specification. The

application process making the call has corrupted data or some other internal error. Recommended Action Restart the application. If that fails, reboot the router. This is an internal error

and should be reported. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at


408

DMA Messages

http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

DMA Messages This section contains dynamic memory access (DMA) messages.

DMA-3 Error Message %DMA-3-DTQ_DISPATCH_DIRTY_PAK: pak not cleaned up by Egress processing (appId [dec]) Explanation After DTQ dispatched a packet to egress processing, the packet was not cleaned up by

the application. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. If possible, also provide the show log on the reporting VIP.

DMB Messages This section contains Dynamic Message Broker (DMB) messages.

DMB-0 Error Message %DMB-0-DMB_EMERG: %s Explanation An internal error occurred in the Dynamic Message Broker (DMB). Recommended Action Copy the message exactly as it appears on the console or in the system log.



409

DMB Messages


DMB-1 Error Message %DMB-1-DMB_ALERT: %s Explanation An internal error occurred in the Dynamic Message Broker (DMB). Recommended Action Copy the message exactly as it appears on the console or in the system log.


DMB-2 Error Message %DMB-2-DMB_CRIT: %s Explanation An internal error occurred in the Dynamic Message Broker (DMB). Recommended Action Copy the message exactly as it appears on the console or in the system log.



410

DMB Messages

DMB-3 Error Message %DMB-3-DMB_ERR: %s Explanation An internal error occurred in the Dynamic Message Broker (DMB). Recommended Action Copy the message exactly as it appears on the console or in the system log.


DMB-4 Error Message %DMB-4-DMB_WARNING: %s Explanation An internal error occurred in the Dynamic Message Broker (DMB). Recommended Action Copy the message exactly as it appears on the console or in the system log.


DMB-5 Error Message %DMB-5-DMB_NOTICE: %s Explanation An internal error occurred in the Dynamic Message Broker (DMB). Recommended Action Copy the message exactly as it appears on the console or in the system log.



411

DNET Messages


DMB-6 Error Message %DMB-6-DMB_INFO: %s Explanation This message displays information from the Dynamic Message Broker (DMB). Recommended Action No action is required.

DMB-7 Error Message %DMB-7-DMB_ASSERT: Assertion Failure ( %s @%s:%d ) : %s Explanation An internal error occurred in the Dynamic Message Broker (DMB). Recommended Action Copy the message exactly as it appears on the console or in the system log.


DNET Messages Error Message %DNET-3-HEARSELF: Hello type [hex] for my address from [dec].[dec] via [chars] Explanation The system is receiving its own DECnet packets. Either a serial line is looped back or

another host with the same DECnet address is already present on the LAN. Recommended Action Check the serial lines (if present) and the DECnet configuration.


412

DOSFS Messages

DOSFS Messages This section contains DOS file system (DOSFS) messages.

DOSFS-3 Error Message %DOSFS-3-RESETERR: [chars] [chars] Explanation The disk could not be reset while the system has initiated reload. A transient disk error

or disk timeout error will occur when the ROMMON initialization code tries to reads the device information block. This is a transient error and the system will be able to access the disk and continue normal operation. Recommended Action No action is required.

DOSFS-4 Error Message %DOSFS-4-DFS_FSCK_ERR: Error while running fsck on the file [chars]. Explanation The file system consistency check (fsck) program became stuck in a loop while walking

through the cluster chain of a file and has aborted. Recommended Action Copy the message exactly as it appears on the console or in the system log.


DOSFS-5 Error Message %DOSFS-5-DFS_CLOSE_ERR: Error during close of the file [chars]. [chars] Explanation An error occurred during a file-close operation. Recommended Action Enter the fsck filesystem prefix: command to check and attempt to repair the

disk. If this does not fix the problem, format the disk.


413

DOT1AD Messages

Error Message %DOSFS-5-DIBERR: [chars] [chars] Explanation The system cannot boot an image from the flash disk because the device information

block (DIB) is different. The flash disk can be read by the router, but will require formatting by the router before an image can be booted from it. Recommended Action Follow any instructions provided in the error message. Before storing an image to the flash disk and trying to boot from this device, enter the format command to format the flash disk from the router. Copy the desired image to the flash disk and boot from the device.

DOT1AD Messages This section contains 801.1ad messages.

DOT1AD-4 Error Message %DOT1AD-4-DOT1QTUNNEL_PORT: Port %s is a dot1q-tunnel port, it conflicts with Dot1ad configuration Explanation IEEE 802.1ad configuration cannot coexist with 802.1q tunnel ports. Recommended Action Disable the 802.1q tunnel configuration on the ports before enabling 802.1ad.

Error Message %DOT1AD-4-DOT1X_PORT: Port %s is configured for DOT1X, it conflicts with Dot1ad configuration Explanation IEEE 802.1ad configuration cannot coexist with 802.1X enabled ports. Recommended Action Disable the 802.1X configuration on the ports before enabling 802.1ad.

Error Message %DOT1AD-4-ETHERTYPEMISMATCH_PORT: Port %s ethertype cannot be changed to Dot1ad ethertype, it conflicts with Dot1ad configuration Explanation The Ethertype on the port cannot be changed to 802.1ad Ethertype. Recommended Action Replace the module with a unit that supports Ethertype change, or power down

the module before enabling 802.1ad.

Error Message %DOT1AD-4-L2PT_PORT: Port %s is a l2protocol-tunnel port, it conflicts with Dot1ad configuration Explanation IEEE 802.1ad configuration cannot coexist with a Layer 2 protocol tunnel port. Recommended Action Disable the Layer 2 protocol tunnel configuration on the port before enabling

802.1ad.


414

DOT1Q_TUNNELLING Messages

Error Message %DOT1AD-4-LACP_PORT: Port %s is a part of an LACP channel, it conflicts with Dot1ad configuration Explanation IEEE 802.1ad configuration cannot coexist with LACP ports. Recommended Action Disable the LACP configuration on the port before enabling 802.1ad.

Error Message %DOT1AD-4-OAM_PORT: Port %s is configured for OAM, it conflicts with Dot1ad configuration Explanation IEEE 802.1ad configuration cannot coexist with OAM-enabled ports. Recommended Action Disable the OAM configuration on the port before enabling 802.1ad.

Error Message %DOT1AD-4-PLATFORM_RESOURCE_UNAVAILABLE: Platform does not have resouces to support dot1ad configuration Explanation The hardware match registers required by 802.1ad are not available. Recommended Action Unconfigure the features that use the match registers (such as CFM or CGVRP) before enabling 802.1ad.

Error Message %DOT1AD-4-STP_CONFLICT: STP mode conflicts with Dot1ad configuration as it is not in MST mode Explanation The current Spanning Tree Protocol (STP) mode conflicts with the 802.1ad

configuration. Recommended Action Change the STP mode to Multiple Spanning Tree (MST) before enabling

802.1ad.

DOT1Q_TUNNELLING Messages This section contains 801.1Q tunnelling messages.

DOT1Q_TUNNELLING-4 Error Message %DOT1Q_TUNNELLING-4-MTU_WARNING: System MTU of [dec] might be insufficient for 802.1Q tunnelling. 802.1Q tunnelling requires system MTU size of [dec] to handle maximum size ethernet frames. Explanation The system MTU setting might not be a large enough value to support 802.1Q

tunnelling. When 802.1Q tunnelling is being used, the system MTU setting might need to be adjusted to add the 4-byte overhead associated with the additional 802.1Q tag. Recommended Action Enter the system mtu command in global configuration mode to adjust the

system MTU setting to take into account the additional 802.1Q tag.


415

DOT1X Messages

DOT1X Messages This section contains IEEE 802.1X (DOT1X) messages.

DOT1X-4 Error Message %DOT1X-4-UNKN_ERR: An unknown operational error occurred. Explanation The 802.1X process cannot operate due to an internal system error. Recommended Action Reload the device.

DOT1X-5 Error Message %DOT1X-5-DROP_MAC: Disallowed MAC address [enet] trying to authenticate. Explanation Authentication using 802.1X is not allowed for a host whose MAC address is configured

as a drop entry in the MAC address table. Recommended Action Remove the drop entry if this host is to be allowed access.

Error Message %DOT1X-5-ERR_INVALID_AAA_ATTR: Got invalid AAA attribute settings [chars] Explanation The authorization settings that were obtained are either unsupported or are invalid. Recommended Action Change the value so that the correct settings are obtained.

Error Message %DOT1X-5-ERR_INVALID_TUNNEL_MEDIUM_TYPE: Got an invalid value [chars] for TUNNEL_MEDIUM_TYPE [chars] Explanation The provided TUNNEL_MEDIUM_TYPE is either unsupported or invalid. Recommended Action Change the tunnel medium type value to one that is supported.

Error Message %DOT1X-5-ERR_INVALID_TUNNEL_TYPE: Got an invalid value of [chars] for TUNNEL_TYPE [chars] Explanation The provided TUNNEL_TYPE is either unsupported or invalid. Recommended Action Change the tunnel type value to one that is supported.


416

DOT1X Messages

Error Message %DOT1X-5-ERR_PER_USR_IP_ACL: Applied per-user IP ACL was unsuccessful on interface [chars] Explanation The 802.1X process could not successfully apply a per-user IP ACL. A possible reason

for this condition could be an invalid per-user base (or pub) ACL from the RADIUS server. Recommended Action Examine the per-user base configuration for the RADIUS server and configure

a correct one.

Error Message %DOT1X-5-ERR_PER_USR_MAC_ACL: Applied per-user MAC ACL was unsuccessful on interface [chars] Explanation The 802.1X process could not successfully apply a per-user MAC ACL. A possible

reason for this condition could be an invalid per-user base (or pub) ACL from the RADIUS server. Recommended Action Examine the per-user base configuration for the RADIUS server and configure

a correct one.

Error Message %DOT1X-5-ERR_PVLAN: Dot1x cannot be enabled on private vlan port [chars] Explanation 802.1X could not be enabled on the specified private VLAN port. This condition was

caused by trying to set 802.1X port control to automatic mode on a PVLAN port. Recommended Action Change the port to access or routed mode, and retry enabling 802.1X on the

port.

Error Message %DOT1X-5-ERR_PVLAN_EQ_VVLAN: Dot1x can not be enabled on a port with Access VLAN equal to Voice VLAN. Explanation A port could not enable 802.1X because the access VLAN is equal to a voice VLAN.

This condition was caused by trying to set 802.1X port control to automatic or force-unauthorized mode on a voice VLAN that is equal to an access VLAN port. Recommended Action Change the voice VLAN or the access VLAN on the interface, and retry the

802.1X operation.

Error Message %DOT1X-5-ERR_PVLAN_TRUNK: Dot1x can not be enabled on private VLAN trunk ports. Explanation 802.1X cannot coexist with private VLAN trunking on the same port. Recommended Action This is an informational message only. No action is required.


417

DOT1X Messages

Error Message %DOT1X-5-ERR_RADIUSVLAN_EQ_VVLAN: RADIUS attempted to assign a VLAN to Dot1x port [chars] whose Voice VLAN is same as AccessVlan Explanation The RADIUS server attempted to assign a VLAN to a supplicant on a port with a voice

VLAN that is equal to an access VLAN. Recommended Action Either update the RADIUS configuration so that an access VLAN is not equal to voice VLAN or change the voice VLAN on the specified port.

Error Message %DOT1X-5-ERR_STATIC_MAC: Dot1x can not be enabled on a port configured with Static MAC addresses. Explanation A port could not enable 802.1X because the port is configured with static MAC

addresses. This condition was caused by trying to set 802.1X port control to auto or force-unauthorized mode on a port that is configured with static MAC addresses. Recommended Action Remove the static MAC addresses on the port, and retry the 802.1X operation.

Error Message %DOT1X-5-ERR_VLAN_INTERNAL: The VLAN [dec] is being used internally and cannot be assiged for use on the Dot1x port [chars] Vlan Explanation The VLAN is used internally and cannot be assiged for use again on this port Recommended Action Update the configuration to not use this VLAN.

Error Message %DOT1X-5-ERR_VLAN_INVALID: The VLAN [dec] is invalid and cannot be assiged for use on the Dot1x port [chars] Vlan Explanation The VLAN specified is out of range and cannot be assiged for use on this port. Recommended Action Update the configuration to use a valid VLAN.

Error Message %DOT1X-5-ERR_VLAN_RESERVED: The VLAN [dec] is a reserved vlan and cannot be assiged for use on the Dot1x port [chars] Vlan Explanation The VLAN specified is a reserved VLAN and cannot be assiged for use on this port. Recommended Action Update the configuration to not use this VLAN.

Error Message %DOT1X-5-ERR_VVID_NOT_SUPPORTED: Dot1x can not be enabled on this port with Voice VLAN configured. Explanation 802.1X cannot coexist on the same port with Voice VLANs. Recommended Action Remove voice VLANs configuration on this port and retry the 802.1X

operation.


418

DOT1X_SWITCH Messages

Error Message %DOT1X-5-FAIL: Authentication failed for client (%s) on Interface %s Explanation Authentication was unsuccessful for the specified client. Recommended Action No action is required.

Error Message %DOT1X-5-SUCCESS: Authentication successful for client (%s) on Interface %s Explanation Authentication was successful for the specified client. Recommended Action No action is required.

DOT1X_SWITCH Messages This section contains 802.1X switch messages.

DOT1X_SWITCH-4 Error Message %DOT1X_SWITCH-4-PROC_START_ERR: Unable to start dot1x switch process. Explanation The system failed to create the 802.1X switch process. Recommended Action Reload the device.

DOT1X_SWITCH-5 Error Message %DOT1X_SWITCH-5-ERR_ADDING_ADDRESS: Unable to add address %e on %s Explanation The authenticated host’s address could not be added. This is probably because either the

TCAM is full or the address exists as a secure address on another port. Recommended Action If the TCAM is full, clear some dynamic addresses to make room for the host’s

address. If the host’s address is secured on another port, manually remove it from that port.

Error Message %DOT1X_SWITCH-5-ERR_INVALID_PRIMARY_VLAN: Attempt to assign primary VLAN %d to 802.1x port %s Explanation An attempt was made to assign a primary VLAN to an 802.1x port, which is not allowed. Recommended Action Update the configuration to use a different VLAN.


419


Error Message %DOT1X_SWITCH-5-ERR_INVALID_SEC_VLAN: Attempt to assign invalid secondary VLAN %d to PVLAN host 802.1x port %s Explanation An attempt was made to assign a non-secondary VLAN to a PVLAN host 802.1x port. Recommended Action Change the mode of the port so that it is no longer a PVLAN host port or use

a valid secondary VLAN.

Error Message %DOT1X_SWITCH-5-ERR_PRIMARY_VLAN_NOT_FOUND: Primary VLAN for VLAN [dec] does not exist or is shutdown for dot1x port [chars] Explanation An attempt was made to use a private VLAN whose primary VLAN does not exist or is

shut down. Recommended Action Make sure the primary VLAN exists and is not shut down. Also verify that the private VLAN is associated with a primary VLAN.

Error Message %DOT1X_SWITCH-5-ERR_RADIUS_VLAN_NOT_FOUND: Attempt to assign non-existent VLAN %s to dot1x port %s Explanation An attempt was made by RADIUS to assign a VLAN with a particular name or ID to a

supplicant on a port, but the name or ID could not be found on the switch. Recommended Action Make sure a VLAN with the specified name or ID exists on the switch.

Error Message %DOT1X_SWITCH-5-ERR_SEC_VLAN_INVALID: Attempt to assign secondary VLAN %d to non-PVLAN host 802.1x port %s Explanation An attempt was made to assign a secondary VLAN to a port that is not a PVLAN host

port, which is not allowed. Recommended Action Change the mode of the port so that it is configured as a PVLAN host port or

use a different VLAN that is not configured as a secondary VLAN.

Error Message %DOT1X_SWITCH-5-ERR_SPAN_DST_PORT: Attempt to assign VLAN %d to 802.1x port %s, which is configured as a SPAN destination Explanation An attempt was made to assign a VLAN to an 802.1x port that is configured as a SPAN

destination port. Recommended Action Change the SPAN configuration so that the port is no longer a SPAN

destination port or change the configuration so that no VLAN is assigned.

Error Message %DOT1X_SWITCH-5-ERR_VLAN_EQ_MDA_INACTIVE: Multi-Domain Authentication cannot activate because Data and Voice VLANs are the same on port %s Explanation Multi-Domain Authentication (MDA) host mode cannot be activated if the configured

data VLAN on a port is the same as voice VLAN. Recommended Action Change either the voice VLAN or the access (data) VLAN on the interface so

they are not equal.


420


Error Message %DOT1X_SWITCH-5-ERR_VLAN_EQ_VVLAN: Data VLAN [dec] on port [chars] cannot equal to Voice VLAN. Explanation The 802.1x assigned VLAN on a port cannot be the same as the voice VLAN. Recommended Action Change either the voice VLAN or the access 802.1X assigned VLAN on the

interface so they are not equal anymore. This change will cause the authentication to proceed normally on the next retry.

Error Message %DOT1X_SWITCH-5-ERR_VLAN_INTERNAL: The VLAN [dec] is being used internally and cannot be assiged for use on the Dot1x port [chars] Vlan Explanation The VLAN is used internally and cannot be assiged for use again on this port. Recommended Action Update the configuration to not use this VLAN.

Error Message %DOT1X_SWITCH-5-ERR_VLAN_INVALID: The VLAN [dec] is invalid and cannot be assiged for use on the Dot1x port [chars] Vlan Explanation The VLAN specified is out of range and cannot be assiged for use on this port. Recommended Action Update the configuration to use a valid VLAN.

Error Message %DOT1X_SWITCH-5-ERR_VLAN_NOT_FOUND: Attempt to assign non-existent or shutdown VLAN [dec] to dot1x port [chars] Explanation An attempt was made to assign a VLAN to a supplicant on a port, but the VLAN was

not found in the VTP database. Recommended Action Make sure the VLAN exists and is not shutdown or use another VLAN.

Error Message %DOT1X_SWITCH-5-ERR_VLAN_NOT_VALID: Attempt to assign non-existent group or shutdown VLAN to 802.1x port [chars] Explanation An attempt was made to assign a VLAN to an 802.1x port, but the VLAN was not found

in the VTP database. Group not found.

Error Message Make sure the VLAN exists and is not shutdown or use another VLAN.%DOT1X_SWITCH-5-ERR_VLAN_ON_ROUTED_PORT: Attempt to assign VLAN %d to routed 802.1x port %s Explanation An attempt was made to assign a VLAN to a routed 802.1x port, which is not allowed. Recommended Action Change the mode of the port so that it is no longer a routed port or change the configuration so that no VLAN is assigned.


421

DP83815 Messages

Error Message %DOT1X_SWITCH-5-ERR_VLAN_PROMISC_PORT: Attempt to assign VLAN %d to promiscuous 802.1x port %s Explanation An attempt was made to assign a VLAN to a promiscuous 802.1x port, which is not

allowed. Recommended Action Change the mode of the port so that it is no longer a promiscuous port or change the configuration so that no VLAN is assigned.

Error Message %DOT1X_SWITCH-5-ERR_VLAN_RESERVED: The VLAN [dec] is a reserved vlan and cannot be assiged for use on the Dot1x port [chars] Vlan Explanation The VLAN specified is a reserved VLAN and cannot be assiged for use on this port. Recommended Action Update the configuration not to use this VLAN.

Error Message %DOT1X_SWITCH-5-ERR_VLAN_RSPAN: Attempt by 802.1x to assign RSPAN VLAN [dec]. 802.1x is incompatible with RSPAN Explanation Remote SPAN should not be enabled on a VLAN in which ports are configured with

802.1X enabled. Recommended Action Either disable the remote SPAN configuration on the VLAN OR disable

802.1X on all of the ports in this VLAN.

DP83815 Messages This section contains DP83815 10/100 Mbps Integrated PCI Ethernet Media Access Controller messages.

DP83815-1 Error Message %DP83815-1-DISCOVER: Only found [dec] interfaces on bay [dec], shutting down bay Explanation The software could not identify the interface card. Recommended Action Reseat the interface card. If the message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


422

DP83815 Messages

Error Message %DP83815-1-INITFAIL: [chars] failed to initialized Explanation The software failed to initialize or restart an Ethernet or Fast Ethernet interface. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %DP83815-1-MEMERR: [chars] status = [hex] Explanation The interface could not access system resources for a long time. This problem may

occur under very heavy loads. Recommended Action The system should recover. Otherwise, copy the message exactly as it appears


DP83815-3 Error Message %DP83815-3-OWNERR: [chars] packet buffer, pak=[hex] Explanation The software detected an error in descriptor ownership. Recommended Action Clear the interface. If the problem recurs, copy the message exactly as it



423

DP83815 Messages

Error Message

%DP83815-3-UNDERFLO: [chars] transmit error

Explanation While transmitting a frame, the controller chip’s local buffer received insufficient data because data could not be transferred to the chip fast enough to keep pace with its output rate. Normally, such a problem is temporary, depending on transient peak loads within the system. Recommended Action The system should recover. No action is required.

DP83815-5 Error Message %DP83815-5-LATECOLL: [chars] transmit error Explanation Late collisions occurred on the Ethernet or Fast Ethernet interface. Recommended Action If the interface is Fast Ethernet, verify that both peers are in the same duplex

mode. For regular Ethernet, the system should recover. No action is required.

Error Message

%DP83815-5-LOSTCARR: [chars] cable/transceiver problem?

Explanation The cable or transceiver is not connected. Recommended Action Connect the cable or transceiver. No action is required.

DP83815-6 Error Message %DP83815-6-EXCESSCOLL: [chars] Explanation Ethernet or Fast Ethernet is seeing multiple collisions. This condition may occur under

heavy loads. Recommended Action The system should recover. No action is required.

Error Message %DP83815-6-NOTDP83815: Slot [dec] device ID seen as [hex], expected [hex] Explanation The software did not recognize the interface chips. Recommended Action Reseat the interface card. If the message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


424

DTP Messages

DTP Messages This section contains Dynamic Trunking Protocol (DTP) filtering messages.

Error Message %DTP-5-DOMAINMISMATCH: Unable to perform trunk negotiation on port [chars] because of VTP domain mismatch. Explanation The two ports involved in trunk negotiation belong to different VTP domains. Trunking

is possible only when the ports involved belong to the same VTP domain. Recommended Action Ensure that the two ports that are involved in trunk negotiation belong to the

same VTP domain.

DUAL Messages This section contains Distributed Update Algorithm (DUAL) Enhanced Interior Gateway Routing Protocol (EIGRP) messages.

DUAL-3 Error Message %DUAL-3-BADIGRPSAP: Cannot send incremental SAP update to peer on %s. Increasing output-sap-delay may help Explanation An incremental SAP update could not be sent because it might cause a loss of

synchronization of the SAP tables between peers. Recommended Action Increase the output SAP delay on the listed interface to reduce buffer usage. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %DUAL-3-BADIGRPSAPTYPE: Unsupported SAP type for EIGRP being %s - type %x Explanation This message appears when you receive or attempt to send a SAP message with a type

code that is neither a general query nor a general response, or when you receive a general query that is not addressed to the broadcast address. Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative. If possible, also provide the output of the debug ipx sap activity and debug ipx sap event commands for the period during which this message appeared.


425

DUAL_ACTIVE Messages

Error Message %DUAL-3-PFXLIMIT: %s %d: %s prefix limit reached. Explanation The number of prefixes for the Enhanced Interior Gateway Routing Protocol (EIGRP)

has reached the configured or default limit. Recommended Action Take preventive action by identifying the source of the prefixes. Enter the show

ip eigrp accounting command for details.

DUAL-4 Error Message %DUAL-4-PFXLIMITTHR: %s %d: %s threshold prefix level reached. Explanation The number of prefixes in the topology database has reached the configured or default

threshold level. Recommended Action Take preventive action by identifying the source of the prefixes. Enter the show

ip eigrp accounting command for details.

DUAL-5 Error Message %DUAL-5-NBRCHANGE: [chars] [dec]: Neighbor [chars] ([chars]) is [chars]: [chars] Explanation A neighbor has gone up or down. The displayed information is [routing protocol]

[Autonomous System number]: Neighbor [IP address] ([interface]) is [up or down]: [reason]. Recommended Action No action is required.

DUAL_ACTIVE Messages This section contains dual-active chassis (DUAL_ACTIVE) messages.

DUAL_ACTIVE-1 Error Message %DUAL_ACTIVE-1-DETECTION: Dual-active condition detected: shutting down all non-VSL interfaces Explanation A dual-active situation has occurred because VSL went down. The VSL has become

inactive and both virtual switches have taken over the role of the active virtual switch. To fix this condition, the standby virtual switch has become active and taken control of the network. All non-VSL interfaces on the original active virtual switch will be internally shut down in hardware. Recommended Action Attempt to determine the reason why VSL has gone down and correct it. Once VSL has been reestablished, the original active virtual switch will reload. Enter all variations of the commands:


426


show show show show show

switch virtual troubleshooting last vslp lmp status switch virtual dual-active summary switch virtual dual-active pagp switch virtual dual-active bfd

If you cannot determine the cause of the problem from the commands you entered, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %DUAL_ACTIVE-1-RECOVERY: BFD running on [chars] triggered dual-active recovery Explanation Bidirectional Forwarding Detection (BFD) detected a dual-active scenario on the

specified interface and caused the switch to go into recovery mode. Recommended Action No action is required.

Error Message %DUAL_ACTIVE-1-VSL_DOWN: VSL is down - switchover, or possible dual-active situation has occurred Explanation The virtual switch link (VSL) between the active and standby switches has gone offline.

The following are possible reasons for the switchover condition: – -A switchover has occurred and the standby virtual switch has become the active virtual switch. – A dual-active situation has occurred, and the original active virtual switch has gone into

recovery mode, which would bring down all non-VSL interfaces on the original active virtual switch. – A dual-active situation has occurred, but the original active virtual switch did not detect the dual

active state and did not go into recovery mode. This condition may be the result of multiple system failures or an incorrect configuration that caused the dual-active situation to not be detected. Recommended Action Attempt to determine the reason why the VSL has gone offline and correct it if

it is a dual-active situation. Enter all variations of the commands: show show show show show

switch virtual troubleshooting last vslp lmp status switch virtual dual-active summary switch virtual dual-active pagp switch virtual dual-active bfd

If you cannot determine the cause of the problem from the commands you entered, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools


427


and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %DUAL_ACTIVE-1-VSL_RECOVERED: VSL has recovered during dual-active situation: Reloading switch [dec] Explanation The virtual switch link (VSL) between the two active virtual switches in a dual-active situation has gone online. The virtual switch in recovery mode must be reloaded to reenable all non-VSL interfaces that were shut down when the dual-active situation first occurred. Recommended Action No action is required.

DUAL_ACTIVE-3 Error Message %DUAL_ACTIVE-3-PORT_ERR_IN_RECOVERY: Port [chars] [chars] error Explanation Port information could not be extracted or a non-VSL port could not be disabled while

the active virtual switch was going into recovery mode. Recommended Action Attempt to determine why the port information could not be extracted or why

the non-VSL port could not be disabled.

Error Message %DUAL_ACTIVE-3-REGISTRY_ADD_ERR: Failure in adding to [chars] registry Explanation Could not add a function to the registry. Recommended Action No action is required.

DUAL_ACTIVE-4 Error Message %DUAL_ACTIVE-4-CONFIG: [chars] Explanation If VSL goes down due to any reason, standby switch will take over as active

immediately.If the original active chassis is still operational, both chassis are now active. This situation is called a dual-active scenario. A dual-active scenario can have adverse affects on network stability, because both chassis use the same IP addresses, SSH keys, and STP bridge ID.The virtual switching system (VSS) must detect a dual-active scenario and take recovery action for which at least one of the following detection methods should be configured: a/ Ehanced Pagp b/ IP BFD c/ Fast-hello. Please refer to Software configuration guide for more details. Recommended Action Configure one or more dual-active detection methods as per configuration

guide.


428

DVMRP Messages

DVMRP Messages This section contains Dense wavelength division multiplexing messages.

DVMRP-5 Error Message %DVMRP-5-NBRUP: Neighbor [IP_address] is up on [chars] Explanation A DVMRP multicast neighbor is active on the specified interface. This is caused by the

arrival and acceptance of DVMRP probes via that interface. This may indicate that a multicast session has been subscribed via a path passing through this router. Note that DVMRP activity is mutually exclusive of tagswitching, so this will cause tagswitching to be disabled on that interface. Recommended Action No action is required.

DWDM Messages This section contains EDistance Vector Multicast Routing Protocol (DVMRP) messages.

DWDM-3 Error Message %DWDM-3-CLEAR_G709_CTR: 23414.2.c:205:64: backslash and newline separated by spaceUnable to clear g709 counter in slot [dec] rc = [dec] Explanation The SPA driver was unable to clear the G.709 OTN protocol counters for bit errors. Recommended Action Please check the configuration of the interfaces and controllers and correct the configuration if necessary. If the problem persists contact your Cisco technical support representative.

Error Message %DWDM-3-CONFIG_ALARM_REPORT: Failed to config report alarm [chars] slot [dec] rc = [dec] Explanation The SPA driver could not configure one of the reporting status of the alarms. Recommended Action Please check the configuration of the interfaces and controllers and correct the configuration if necessary. If the problem persists contact your Cisco technical support representative.


429

DWDM Messages

Error Message %DWDM-3-CONFIG_ALARM_THRESHOLD: Failed to config threshold alarm [chars] slot [dec] rc = [dec] Explanation The SPA driver could not configure one of the threshold alarms for the optical data or

transport unit. Recommended Action Please check the configuration of the interfaces and controllers and correct the configuration if necessary. If the problem persists contact your Cisco technical support representative

Error Message %DWDM-3-CONFIG_TX_POWER: Failed to config transmit power [dec] on slot [dec] rc = [dec] Explanation The SPA driver detected a error in configuring the Tx power level for the UT2

transponder module Recommended Action Please power down and reseat the indicated SPA card. If the condition persists,

copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message %DWDM-3-DWDM_CONFIG_FAIL: Failed to [chars] [chars] in slot [dec] rc = [dec] Explanation The SPA driver detected failure during configuring one of the DWDM parameters Recommended Action Reload the SPA card and if the problem persists, contact the technical support

representative.

Error Message %DWDM-3-DWDM_GET_INFO_FAIL: Failed receiving [chars] from slot [dec] rc = [dec] Explanation The SPA driver did not receive the necessary optics information from the slot. Recommended Action Please check the configuration of the interfaces and controllers and correct the configuration if necessary. If the problem persists contact your Cisco technical support representative.

Error Message %DWDM-3-DWDM_NULL_INFO: DWDM info is NULL in [dec] Explanation The SPA driver detected NULL information for DWDM. Recommended Action Reload the SPA and if the problem persists contact the technical support

representative.


430

DWDM Messages

Error Message %DWDM-3-IPC_SHIM_INIT: DWDM IPC SHIM init failed Explanation The SPA driver detected failure during DWDM IPC SHIM initialization Recommended Action Please power down and reseat the indicated SPA cardIf the problem persists please contact yourtechnical support representative

Error Message %DWDM-3-LC_ERR_STATS: error sending LC stats to RP Explanation The SPA driver encountered an error while sending the LC stats to the RP. Recommended Action Reload the SPA card and if the problem persistscall the technical support

representative.

Error Message %DWDM-3-MALLOC_FAIL: malloc failure creating G.709 port on slot [dec] Explanation The SPA driver detected a memory error on the SPA card. Recommended Action Reload the card and if the problem persists call TAC.

Error Message %DWDM-3-RPC_FAILED: Application error rc = [dec]: Explanation The system failed to retrieve the information required to execute the command. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %DWDM-3-RPC_INIT_FAIL: DWDM RPC init failure Explanation The system failed to create the resources required to process user interface commands

for transceivers. The error is not fatal but some show commands could fail. Recommended Action Copy the error message exactly as it appears on the console or in the system



431

DWDM Messages

Error Message %DWDM-3-RPC_PROCESSING_ERROR: DWDM RPC error: [chars] Explanation Non Fatal error occurred in processing an RPC messsage. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %DWDM-3-RX_G709_INFO: Failed receiving G709 info from slot [dec] rc = [dec] Explanation The SPA driver did not receive the necessary G.709 OTN protocol information from the

slot. Recommended Action Please check the configuration of the interfaces and controllers and correct the configuration if necessary. If the problem persists contact your Cisco technical support representative.

Error Message %DWDM-3-RX_LOS_THRESHOLD: Failed to config rx los threshold = [dec] on slot [dec] rc = [dec] Explanation The SPA driver detected an error in configuring the transponder receive power

threshold. Recommended Action Reload the SPA card and if the problem persistscall TAC.

Error Message %DWDM-3-TIMER_ERR: Timer error Explanation The Driver did not obtain an expired timer from the timer tree for the DWDM process. Recommended Action The SPA driver has encountered an error event on the SPA card. If the condition persists, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.


432

EAP Messages

DWDM-4 Error Message %DWDM-4-G709ALARM: [chars]: [chars] [chars] Explanation The specified G709 Alarm has been declared or released. Recommended Action Repair the source of the alarm.

EAP Messages This section contains Extensible Authentication Protocol (EAP) messages.

EAP-2 Error Message %EAP-2-PROCESS_ERR: [chars] Explanation A critical condition exists that prevents the system from performing an operation related

to an EAP process. Recommended Action Reload the system.

EAP-4 Error Message %EAP-4-BADPKT: IP=[IP_address]| HOST=[chars] Explanation The system received an invalid or malformed EAP packet from the specified host. Recommended Action Check the specified host for the EAP operation.

EAP-6 Error Message %EAP-6-MPPE_KEY: IP=[chars]| MPPE_RECV_KEY_LENGTH=[dec] Explanation The system received an MPPE key for the specified host. Recommended Action No action is required.


433

EARL Messages

EARL Messages This sections contains Enhanced Address Recognition Logic (EARL) messages.

EARL-0 Error Message %EARL-0-TASK_SPAWN_FAIL: Failed to initialize task “[chars]” Explanation The EARL component failed to start a task required by the system to work properly. The

task name is specified in the error message. Most errors will cause a system reload. However, in some cases, only the feature that failed to start will be affected. Recommended Action Copy the message exactly as it appears on the console or in the system log.


EARL-2 Error Message %EARL-2-PATCH_INVOCATION_LIMIT: [dec] Recovery patch invocations in the last 30 secs have been attempted. Max limit reached Explanation The system attempted the EARL recovery for the maximum number of times that are

permitted in the last 30 seconds. The module has been automatically reset instead of attempting recovery. Recommended Action Copy the message exactly as it appears on the console or in the system log.



434

EARL Messages

Error Message %EARL-2-SWITCH_BUS_IDLE: Switching bus is idle for [dec] seconds Explanation The EARL did not switch any packets on the EARL bus. A module or line card

attempted to access the bus and could not. In most cases, this error appears when a card is not properly seated. A recovery mechanism will attempt to fix the problem. The system reloads if the problem cannot be corrected. Recommended Action Reseat all modules and line cards on the switch. If the error message recurs

after reseating the cards, a hardware problem may exist.

Error Message %EARL-2-SWITCH_BUS_STALL: Switching bus stall detected. Backplane bus stall status: [dec] Explanation The EARL did not switch any packets on the EARL bus. A recovery mechanism will

attempt to fix the problem. The system reloads if the problem cannot be corrected. Recommended Action Copy the message exactly as it appears on the console or in the system log.


EARL-3 Error Message %EARL-3-FABRIC_CONNECTION : Recovering from sequence error detected on fabric connection. Explanation A sequence error was detected by the crossbar and bus fabric interface. This error can

be fatal. Recovery is being attempted. Recommended Action If this message recurs, copy the message exactly as it appears on the console



435

EARL Messages

Error Message %EARL-3-RESET_LC: Resetting module in slot [dec]. (Errorcode [dec]) Explanation The specified module did not respond to a critical message. This condition indicates a

hardware error and might be a transient error only. The system has reset the module to fix the error. Recommended Action If this message recurs, copy the message exactly as it appears on the console


EARL-4 Error Message %EARL-4-BUS_CONNECTION : Interrupt [chars] occurring in EARL bus connection. Explanation An error interrupt is occurring for the switching bus interface. Recommended Action Enter the show earl status command on the consoles of the switch supervisor

engine and any DFC-enabled modules. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %EARL-4-EBUS_SEQ_ERROR: Out of Sync error. Explanation The EARL has detected an out-of-synchronization condition on the bus. A recovery

mechanism will attempt to fix the problem. Recommended Action Reseat and then reset the module. If the error remains, upgrade the software to Cisco IOS Release 12.2(18)SXF or later.

Error Message %EARL-4-NF_USAGE: Current Netflow Table Utilization is [dec]% Explanation The NetFlow table utilization exceeds a preset threshold percentage. Recommended Action No action is required.


436

EARL_ACL_FPGA Messages

EARL_ACL_FPGA Messages This section contains Enhanced Address Recognition Logic ACL field-programmable gate array (EARL_ACL_FPGA) messages.

EARL_ACL_FPGA-2 Error Message %EARL_ACL_FPGA-2-INTR_FATAL: EARL ACL FPGA : Non-fatal interrupt [chars] Explanation The EARL ACL FPGA detected the specified unexpected fatal condition. This message indicates a hardware failure or malfunction. The system will reload to attempt to fix the problem. Recommended Action If this message recurs, copy the message exactly as it appears on the console


EARL_ACL_FPGA-3 Error Message %EARL_ACL_FPGA-3-INTR_WARN: EARL ACL FPGA : Non-fatal interrupt [chars] Explanation The EARL ACL FPGA detected the specified unexpected nonfatal condition. Recommended Action If this message recurs, copy the message exactly as it appears on the console



437

EARL_DRV_API Messages

EARL_ACL_FPGA-4 Error Message %EARL_ACL_FPGA-4-CPU_PAR_ERR: EARL ACL FPGA : CPU Parity error [chars] Explanation The EARL ACL FPGA detected a CPU parity error. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %EARL_ACL_FPGA-4-MEM_PAR_ERR: EARL ACL FPGA: Counter Memory Parity error. Error address [hex] Explanation The EARL ACL FPGA detected a memory parity error. Recommended Action If this message recurs, copy the message exactly as it appears on the console


EARL_DRV_API Messages This section contains Enhanced Address Recognition Logic Driver API (EARL_DRV_API) messages.

EARL_DRV_API -0 Error Message %EARL_DRV_API-0-TASK_SPAWN_FAIL: Failed to spawn task "[chars]" Explanation The system failed to perform the specified task. Recommended Action Copy the message exactly as it appears on the console or in the system log.



438

EARL_DRV_API Messages


EARL_DRV_API-2 Error Message %EARL_DRV_API-2-SIG_INST_FAIL: [chars]: Failed to install signal handler Explanation The system failed to install the process signal handler. Recommended Action Copy the message exactly as it appears on the console or in the system log.


EARL_DRV_API-4 Error Message %EARL_DRV_API-4-NOMEM: Malloc failed: [chars] [dec] Explanation The system is running out of memory. Recommended Action Copy the message exactly as it appears on the console or in the system log.



439

EARL_L2_ASIC Messages

EARL_L2_ASIC Messages This section contains Enhanced Address Recognition Logic Layer 2 ASIC (EARL_L2_ASIC) messages.

EARL_L2_ASIC-0 Error Message %EARL_L2_ASIC-0-EXCESSIVE_FT_TBL_ECC_ERR: EARL L2 ASIC [dec]: Too many bad entries in L2 Forwarding Table Explanation The EARL Layer 2 ASIC detected too many errors in the forwarding table. This

condition indicates hardware malfunction and causes the system to reload. Recommended Action If this problem is seen more than once, it could be a case of faulty hardware.

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %EARL_L2_ASIC-0-FATAL_INTR: L2 Forwarding Engine: fatal interrupt: interrupt status [hex], interrupt mask [hex] Explanation Critical interrupts might have caused system forwarding to cease. Recommended Action Copy the message exactly as it appears on the console or in the system log.



440


EARL_L2_ASIC-2 Error Message %EARL_L2_ASIC-2-PARITY_ERR: L2 Forwarding Engine: parity interrupt #[dec]: address [hex], Data: [hex], [hex], [hex], [hex] Explanation A parity error was detected while accessing the Layer 2 forwarding table. Recommended Action Copy the message exactly as it appears on the console or in the system log.


EARL_L2_ASIC-3 Error Message %EARL_L2_ASIC-3-INTR_FATAL: EARL L2 ASIC [dec]: fatal interrupt [chars] Explanation The EARL Layer 2 ASIC detected an unexpected fatal condition. This message

indicates a hardware failure or malfunction. The system will reload to fix the problem. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %EARL_L2_ASIC-3-INTR_WARN: EARL L2 ASIC [dec]: Non-fatal interrupt [chars] Explanation The EARL Layer 2 ASIC detected an unexpected nonfatal condition. Recommended Action If this message recurs, copy the message exactly as it appears on the console



441



EARL_L2_ASIC-4 Error Message %EARL_L2_ASIC-4-DBUS_HDR_ERR: EARL L2 ASIC #[dec]: Dbus Hdr. Error occurred. Ctrl1 [hex] Explanation The EARL Layer 2 ASIC detected an invalid header in the DBUS. This error is due to hardware that has failed, an incorrect configuration of the module software, or invalid packets that were dropped because of an OIR operation. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %EARL_L2_ASIC-4-DBUS_SEQ_ERR: EARL L2 ASIC #[dec]: Dbus Seq. Error occurred (Ctrl1 [hex]) Explanation The EARL Layer 2 ASIC detected a DBUS sequence mismatch error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %EARL_L2_ASIC-4-FT_ERR: EARL L2 ASIC [dec]: Forwarding table bank [dec] encountered [chars] ecc error at address [hex] Explanation The EARL Layer 2 ASIC detected a nonfatal condition in one of the banks of the

forwarding table. The bank and address of the forwarding table are specified in the error message. Recommended Action This message is informational. The device has detected and corrected the error.


442


Error Message %EARL_L2_ASIC-4-FT_INVLD_ADDR: Forwarding table bank [dec] encountered invalid address [hex] Explanation The EARL Layer 2 ASIC attempted to access an invalid address in the forwarding table.

Because there are only 12 pages (0–11) per line, access to page 12–15 will be invalid. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %EARL_L2_ASIC-4-INTR_THROTTLE: Throttling "[chars]" interrupt exceeded permitted [int]/[dec] interrupts/msec Explanation Excessive interrupts were generated by the EARL ASIC. Interrupt throttling has been

performed to protect the supervisor engine. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %EARL_L2_ASIC-4-INV_REG: EARL L2 ASIC: Attempt to [chars] invalid register Explanation An attempt was made to read or write to an invalid register of the EARL Layer 2 ASIC. Recommended Action Copy the message exactly as it appears on the console or in the system log.



443


Error Message %EARL_L2_ASIC-4-L2L3_SEQ_ERR: EARL L2 ASIC #[dec]: L2L3 Mismatch seq #[hex] Explanation The EARL Layer 2 ASIC detected a Layer 2-Layer 3 sequence mismatch error. A

recovery mechanism will attempt to fix the problem. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %EARL_L2_ASIC-4-SRCH_ENG_FAIL: EARL L2 ASIC Search Engine has failed Explanation The EARL Layer 2 ASIC search engine failed to terminate a search. A recovery

mechanism fixes the unexpected condition. Recommended Action Copy the message exactly as it appears on the console or in the system log.


EARL_L3_ASIC Messages This section contains Enhanced Address Recognition Logic (EARL) Layer 3 ASIC messages.

EARL_L3_ASIC-3 Error Message %EARL_L3_ASIC-3-INTR_FATAL: EARL L3 ASIC: fatal interrupt [chars] Explanation The EARL Layer 3 ASIC detected an unexpected fatal condition. This message

indicates a hardware failure or malfunction. The system will reload to attempt to fix the problem. Recommended Action Copy the message exactly as it appears on the console or in the system log.



444



Error Message %EARL_L3_ASIC-3-INTR_WARN: EARL L3 ASIC: Non-fatal interrupt [chars] Explanation The EARL Layer 3 ASIC detected an unexpected non-fatal condition. This indicates

that a bad packet was received and dropped. Several conditions can cause a packet to be considered bad; for example, the size of an Ethernet frame was reportedto be different than the expected IP packet size. In older Cisco IOS releases, these packets are normally dropped without being logged. Recommended Action This message is informational only, and can occur due to conditions such as

bad NIC cards, bad NIC drivers, or a bad application. Use a network sniffer or configure a SPAN session to identify the source device that is sending the erroneous packets. Also, examine the adjacent Cisco device for errors. The following commands can be configured to stop verifying checksum or length errors: no mls verify ip checksum — Disables checking of packets for checksum errors no mls verify ip length — Disables checking of packets for length errors no mls verify ip same-address — Disables checking of packets for having the same source and destination IP address

EARL_L3_ASIC-4 Error Message %EARL_L3_ASIC-4-CPU_PAR_ERR: EARL L3 ASIC: CPU Parity error. Error data [hex]. Error address [hex] Explanation The EARL Layer 3 ASIC detected a CPU parity error. This condition is caused by an

interprocess communication error between the CPU and Layer 3 ASIC. Recommended Action Copy the message exactly as it appears on the console or in the system log.



445

EARL_NETFLOW Messages

Error Message %EARL_L3_ASIC-4-INTR_THROTTLE: Throttling "[chars]" interrupt exceeded permitted [int]/[dec] interrupts/msec Explanation Excessive interrupts were generated by the EARL ASIC. Interrupt throttling has been

performed to protect the supervisor engine.

EARL_NETFLOW Messages This section contains Enhanced Address Recognition Logic NetFlow (EARL_NETFLOW) messages.

EARL_NETFLOW-0 Error Message %EARL_NETFLOW-0-NF_ECC_MAX: Netflow ECC Error Threshold Reached, Total Ecc Errors [[dec]] Explanation The total number of NetFlow ECC errors has crossed the maximum threshold. The

maximum allowable of NetFlow ECC errors is 2000. The system will perform a crash dump and will be inoperable. The output of the show tech-support command will also be displayed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


EARL_NETFLOW-3 Error Message %EARL_NETFLOW-3-NF_ECC_RSRV: Netflow ECC Error Occured, Reserved NF location [[hex]] Explanation The number of ECC errors per NetFlow TCAM entry has reached the maximum

threshold (three or more ECC errors). The NetFlow TCAM location will now be marked as reserved and can no longer be used. Recommended Action Copy the message exactly as it appears on the console or in the system log.



446



Error Message %EARL_NETFLOW-3-NF_ECC_SOFT_MAX: Too many Netflow ECC errors have occurred, Total Ecc Errors [[dec]] Explanation The total number of NetFlow ECC errors has exceeded the soft limit number. The soft limit of NetFlow ECC errors is 2500. The hard limit is 5000. When the hard limit is reached, the line card will reboot. Recommended Action Copy the message exactly as it appears on the console or in the system log.


EARL_NETFLOW-4 Error Message %EARL_NETFLOW-4-ICAM_THRLD: Netflow ICAM threshold exceeded, ICAM Utilization [[dec]%] Explanation The NetFlow ICAM is almost full. Aggressive aging is temporarily enabled. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %EARL_NETFLOW-4-NF_AGG_CACHE_THR: Netflow [chars] aggregation cache is almost full. Explanation The aggregation cache for NetFlow is almost full. This condition might cause a high

CPU load. Recommended Action Consider increasing the size of the aggregation cache, or remove the

aggregation cache configuration specified in the error message.


447


Error Message %EARL_NETFLOW-4-NF_FULL: Netflow Table Full, ICAM occupancy [[dec]%], TCAM occupancy [[dec]%], Entry creation failures [[dec]] Explanation The NetFlow table is full, possibly because of faulty hashing behavior. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %EARL_NETFLOW-4-NF_TIME_SAMPLING: Time-based sampling requests could not be processed in time. Explanation Time-based sampling requests could not be processed in a timely fashion. This

condition means that the sampling result might not be accurate. Recommended Action Consider using packet-based sampling. Packet-based sampling uses an

algorithm that ensures the sampling results will be accurate, even if they are not processed in the allotted time.

Error Message %EARL_NETFLOW-4-TCAM_THRLD: Netflow TCAM threshold exceeded, TCAM Utilization [[dec]%] Explanation The NetFlow TCAM is almost full. Aggressive aging is temporarily enabled. Recommended Action Copy the message exactly as it appears on the console or in the system log.



448

EC Messages

EARL_NETFLOW-5 Error Message %EARL_NETFLOW-5-NF_ECC_REMOVE: Netflow ECC Error Occured, Deleted NF entry [[hex]] Explanation A NetFlow ECC error occurred. The affected NetFlow entry has been deleted at the

address specified so that a new entry will be created. Recommended Action Copy the message exactly as it appears on the console or in the system log.


EC Messages This section contains EtherChannel, Link Aggregation Control Protocol (LACP), and Port Aggregation Protocol (PAgP) messages.

EC-5 Error Message %EC-5-CANNOT_BUNDLE_QOS1: Removed [chars] from port channel as QoS attributes of port and port-channel are different. Explanation The port specified in the error message cannot join the port channel, because the QoS

attributes of this port are not consistent withthe QoS attributes of the port channel. Recommended Action Match the QoS attributes of the specified port to the QoS attributes of other member ports in the port channel. Use the show queueing interface command to display the QoS attributes of a port.

Error Message %EC-5-COMPATIBLE: [chars] is compatible with port-channel members Explanation The specified port was not operational earlier because its attributes were different from

the attributes of the port channel or the attributes of the ports within the port channel. The system detects that the attributes of the specified port now match the port channel attributes. Recommended Action This is an informational message only. No action is required.


449

EC Messages

Error Message %EC-5-DONTBNDL2: [chars] suspended: port in half-duplex for LACP Explanation For LACP EtherChannel, if the member port is in half-duplex mode, the port will be in a suspended state. Recommended Action Configure port duplex to full duplex.

Error Message %EC-5-MINLINKS_MET: Port-channel [chars] is up as its bundled ports ([dec]) meets min-links Explanation The administrative configuration of minimum links is equal to or less than the number

of bundled ports. As a result, this port channel is operational. Recommended Action No action is required.

Error Message %EC-5-MINLINKS_NOTMET: Port-channel [chars] is down bundled ports ([dec]) doesn’t meet min-links Explanation The administrative configuration of minimum links is greater than the number of

bundled ports. As a result, this port channel is no longer operational. Recommended Action Reduce the number of minimum links for the specified group, or add more

ports to this port channel so that they bundle.

Error Message %EC-5-PROTO_MISMATCH: Port-Channel [dec] has one aggregator with protocol mismatch Explanation EtherChannel software disabled an aggregator under this port-channel and encountered

a protocol mismatch on the aggregator. This means that the ports in the port-channel have not been all configured with the same protocol and this needs to be fixed. Recommended Action Please verify the port-channel members configuration and fix it so that all the

ports use the same protocol.

Error Message %EC-5-SUSPENDED: Port [chars] in port-channel [chars] is being suspended Explanation EtherChannel software is unable to bundle the physical port in the port-channel. As the standalone disable feature is enabled, the port is going in the suspended state. Please check the configuration on the peer side of this port-channel. Recommended Action Please verify the port-channel configuration of the port connected to the port

for which this error messsage appeared.


450

EM Messages

Error Message %EC-5-VSS_MINLINKS_MET: Members of the Port-channel [chars] on switch [dec] is up as its bundled ports ([dec]) meets min-links Explanation The administrative configuration of minimum links is equal or less than the number of

bundled ports from the switch. Therefore all the ports in the port channel from that switch has been brought up. Recommended Action None.

Error Message %EC-5-VSS_MINLINKS_NOTMET: All the members of the Port-channel [chars] is down on switch [dec] as the number of bundled ports ([dec]) doesn’t meet min-links Explanation The administrative configuration of minimum links is greater than the number of

bundled ports from the switch. Therefore all the ports in port-channel from that switch has been brought down. Recommended Action Reduce the min-links configuration for this group or add more ports to this

port-channel from the switch to have them bundle.

EM Messages This section contains Event Manager (EM) messages.

EM-3 Error Message %EM-3-EXCEED: EM exceed maximum open events ([dec]). Explanation The total number of open events exceeded the maximum number of possible open

events. The maximum number that the EM server permits is specified in the error message. EM clients are either opening too many events or not closing events within the permitted time period. Recommended Action Enter the show em state | inc em_type command. Copy the message exactly as

it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


451

EM Messages

Error Message %EM-3-FAIL: The specified EM Function failed ([chars]). Explanation The specified EM function failed. This condition might be caused by incorrect logic or

a memory corruption. Recommended Action Enter the show em state command and the show em status command. Copy


Error Message %EM-3-NOMEM: The EM failed to allocate memory resources for the specified EM function ([chars]). Explanation The EM failed to allocate memory resources for the specified function because memory

is running low. Recommended Action Enter the show memory summary command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %EM-3-NULLPTR: The pointer in a specified EM function ([chars]) is incorrectly NULL. Explanation The pointer in the specified EM function is incorrectly NULL. This condition might be

caused by incorrect logic or a memory corruption. Recommended Action Enter the show em state command and the show em status command. Copy



452

EM Messages

EM-4 Error Message %EM-4-AGED: The specified EM client (type=[dec], id=[dec]) did not close the EM event within the permitted amount of time ([dec] msec). Explanation A timeout occurred. This condition is minor and should not affect the functionality of

the switch. Recommended Action Enter the show em state command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %EM-4-INVALID: The specified EM function ([chars]) received Invalid operands . Explanation The EM client used invalid API parameters. Recommended Action Enter the show em state command and the show em status command. Copy


Error Message %EM-4-LIMIT: EM exceed open events limit ([dec]). Explanation The EM has exceeded the permitted number of open events. The open event limit is

5000. Recommended Action Copy the message exactly as it appears on the console or in the system log.



453

EM Messages

Error Message %EM-4-NOTUP: The EM is not available ([chars]). Explanation The EM is not available because some basic initialization failed. This condition might

be caused by failure of a basic infrastructure functionality or a memory corruption. Recommended Action Enter the show em state command and the show em status command. Copy


Error Message %EM-4-SEARCH: The EM function ([chars]) searched for the specified open event ([dec]), but the search failed. Explanation The specified EM function could not find the specified open event. This condition might

be caused by a memory corruption. Recommended Action Enter the show em state command and the show em status command. Copy


Error Message %EM-4-SENDFAILED: The specified EM client (type=[dec]) failed to send messages to standby. Explanation The redundant supervisor engine is not updated because the specified EM client failed

to send messages to the redundant supervisor engine. Do not attempt to failover to redundant supervisor engine. Recommended Action Enter the show checkpoint clients command. If you cannot determine the

cause of the error from the error message text or from the show checkpoint clients output, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


454

EM_ISSU Messages

EM_ISSU Messages This section contains Event Manager (EM) in-service software upgrade messages.

EM_ISSU-2 Error Message %EM_ISSU-2-GET_BUFFER: Event Manager ISSU client failed to get buffer for message. Error: %d (%s) Explanation The Event Manager ISSU client failed to get buffer space for building a negotiation



Error Message %EM_ISSU-2-INIT: Event Manager ISSU client initialization failed to %s. Error: %d (%s) Explanation The Event Manager ISSU client could not be initialized. This initialization failure must be addressed before an in-service software upgrade or downgrade can be performed successfully. Otherwise, a software upgrade or downgrade will result in downtime. Recommended Action Copy the message exactly as it appears on the console or in the system log.



455

EM_ISSU Messages

Error Message %EM_ISSU-2-SEND_NEGO_FAILED: Event Manager ISSU client failed to send negotiation message. Error: %d (%s) Explanation The Event Manager ISSU client failed to send a session negotiation message to the peer

device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %EM_ISSU-2-SESSION_NEGO: Event Manager ISSU client encountered unexpected client nego_done. Error: %d (%s) Explanation The Event Manager ISSU client encountered a ’client negotiation done’ state that was

unexpected. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %EM_ISSU-2-SESSION_REGISTRY: Event Manager ISSU client failed to register session information. Error: %d (%s) Explanation The Event Manager ISSU client failed to register session information. If a problem

occurs with the ISSU session registration, the standby device cannot be brought up properly. Recommended Action Copy the message exactly as it appears on the console or in the system log.



456

EM_ISSU Messages


EM_ISSU-3 Error Message %EM_ISSU-3-INVALID_SESSION: Event Manager ISSU client does not have a valid registered session. Explanation The Event Manager ISSU client does not have a valid registered session. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %EM_ISSU-3-MSG_NOT_OK: Event Manager ISSU client ’Message Type %d’ is not compatible Explanation The Event Manager ISSU client received an incompatible message from the peer device.

The message cannot be processed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %EM_ISSU-3-MSG_SIZE: Event Manager ISSU client failed to get the MTU for Message Type %d. Error: %d (%s) Explanation The Event Manager ISSU client was unable to calculate the MTU for the specified

message. The Event Manager ISSU client is unable to send the message to the standby device. Recommended Action Copy the message exactly as it appears on the console or in the system log.



457

EM_ISSU Messages

information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, show issu message group, and show issu negotiated version commands and your pertinent troubleshooting logs.

Error Message %EM_ISSU-3-OPAQUE_MSG_NOT_OK: Event Manager ISSU client ’Opaque Message Type %d’ is not compatible Explanation The Event Manager ISSU client received an incompatible (opaque) message from the

peer device. The message cannot be processed. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, show issu message group, and show issu negotiated version commands and your pertinent troubleshooting logs.

Error Message %EM_ISSU-3-SESSION_UNREGISTRY: Event Manager ISSU client failed to unregister session information. Error: %d (%s) Explanation The Event Manager ISSU client failed to unregister session information. Recommended Action Copy the message exactly as it appears on the console or in the system log.



458

ENT_ALARM Messages

Error Message %EM_ISSU-3-TRANSFORM_FAIL: Event Manager ISSU client %s transform failed for ’Message Type %d’. Error: %d (%s) Explanation The Event Manager ISSU client could not transform the specified message type. If the

transmit transformation failed, the checkpoint message was not sent to the standby device. If the receive transformation failed, the checkpoint message was not applied on the standby device. In either case, the Event Manager state between the active device and the standby device is not identical. Recommended Action Copy the message exactly as it appears on the console or in the system log.


ENT_ALARM Messages This section contains entity alarm messages.

ENT_ALARM-3 Error Message %ENT_ALARM-3-NOALARMENT: [chars] Explanation All entities that could have alarm conditions set for them should be registered with the alarm subsystem for the Cisco IOS software. This message indicates that the normal registration of entities in the Cisco IOS software alarm subsystem has failed, and that one or more entities could not be registered. The message text indicates the alarm entity that could not be registered. Any alarm conditions against the entity specified in the message text cannot be reported. This message does not indicate that the entity specified in the message has undergone an error condition. Recommended Action Copy the message exactly as it appears on the console or in the system log.



459

ENT_API Messages

ENT_ALARM-6 Error Message %ENT_ALARM-6-INFO: [chars] [chars] [chars] [chars] [chars] Explanation This message provides alarm assertion or deassertion information. Recommended Action This is an informational message only. No action is required.

ENT_API Messages This section contains Entity MIB API (ENT_MIB) messages.

ENT_API-4 Error Message %ENT_API-4-NOALIAS: Physical entity not found when adding an alias with physical index = [dec] and logical index = [dec] to the Entity MIB Explanation A timing issue was detected when the system or the module is brought up. This issue

has no impact on system performance or management functionality. Recommended Action No action is required.

Error Message %ENT_API-4-NOPORT: Physical entity does not have a Port PhysicalClass when adding an alias with physical index = [int], logical index = [int], phyDescr = [chars], phyName = [chars], phyClass = [int], phyContainedIn = [int], to the Entity MIB Explanation An attempt to add an alias entry to the Entity MIB was made. The physical entity with

the specified index does not have an entPhysicalClass of 10 (Port class) and so the alias entry creation failed. See RFC2737 for the definition of the PhysicalClass textual convention and the aliasMappingEntry object. Recommended Action Copy the message exactly as it appears on the console or in the system log.



460

ENVIRONMENT Messages

ENVIRONMENT Messages This section contains environment messages.

ENVIRONMENT-3 Error Message %ENVIRONMENT-3-OVERTEMP: [chars] [chars] [chars] [chars] Explanation The internal chassis temperature has exceeded the maximum temperature threshold. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ENVIRONMENT-3-RPS_FAILED: [chars] [chars] [chars] [chars] Explanation Only one power supply was detected for the system in dual-power mode, or the power

supply is failing. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ENVIRONMENT-3-UNDERTEMP: [chars] [chars] [chars] [chars] Explanation The internal chassis temperature is below the minimum temperature threshold. Recommended Action No action is required.


461

ENVM Messages

ENVIRONMENT-4 Error Message %ENVIRONMENT-4-CONFIG_OVERTEMP: [chars] [chars] [chars] [chars] Explanation The chassis inside temperature has exceeded the configured threshold, but is less than

or equal to the maximum allowable internal chassis temperature. Recommended Action Copy the message exactly as it appears on the console or in the system log.


ENVM Messages This section contains environmental monitoring (ENVM) messages.

ENVM-2 Error Message %ENVM-2-TEMP_SENSOR_READFAIL: Failed to access the Temperature sensor on the linecard. Resetting the linecard. Explanation The local CPU on the Enhanced FlexWAN module was unable to access the temperature

sensor on the module. The module will attempt to recover by resetting itself. Recommended Action Copy the message exactly as it appears on the console or in the system log.



462

ENVM Messages

ENVM-3 Error Message %ENVM-3-DISABLE: Environmental monitoring for [chars] disabled ([chars]) Explanation Environmental monitoring for the indicated hardware component could not be initiated. This error message is displayed if environmental monitoring for the whole system, or a particular hardware component is disabled. Operating the system with the environmental monitoring disabled can be dangerous. Recommended Action Address the cause for the environmental monitoring being disabled as

indicated in the error message. Depending on whether a particular hardware component is affected or the whole system, either the card should be removed or the entire system taken offline for a power shutdown until the problem is resolved. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %ENVM-3-ENVDATA_MISSING: Environmental monitoring information for card in [chars] is not present in the IDPROM Explanation Environmental threshold data for the card in the specified slot is not present in the board

IDPROM. The system will not monitor the voltage and temperature readings for the specified card. Recommended Action Enter the show diag slot-number command for the specified slot. Copy the



463

ENVM Messages

Error Message %ENVM-3-ENVINFO_MISSING: Voltage threshold information for [chars] is not present in the [chars]IDPROM for the card in [chars] Explanation Environmental threshold data for the specified voltage is missing from the threshold

table in the IDPROM. The system will not monitor the voltage and temperature readings for the specified card. Recommended Action Enter the show diag slot-number command for the specified slot. Copy the


Error Message %ENVM-3-SUBSLOT_SHUTDOWN: Environmental monitor initiated shutdown of the card in subslot [dec]/[dec] ([chars] measured at [chars]) Explanation The environmental monitor initiated a subslot shutdown due to a temperature or voltage

condition. Recommended Action Look at previous environmental messages to determine the cause of the

shutdown and correct if possible. If you think the shutdown was in error, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %ENVM-3-TEMP_SENSOR_DISABLED: Access to Temperature sensor on module in slot [dec] is disabled Explanation During previous reloads, this module experienced a timeout while accessing the

temperature sensor. All further access to the temperature sensor will be disabled. This condition indicates a possible problem with the temperature sensor. Recommended Action Copy the message exactly as it appears on the console or in the system log.



464

ENVM Messages


ENVM-4 Error Message %ENVM-4-LONGBUSYREAD: C2W Interface busy for long time reading temperature sensor [dec] Explanation The Cisco 2 wire (C2W) interface has taken an unusually long time to read the specified

temperature sensor. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ENVM-4-LONGBUSYWRITE: C2W Interface busy for long time writing temperature sensor [dec] Explanation The Cisco 2 wire (C2W) interface has taken an unusually long time to write to the specified temperature sensor. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ENVM-4-RPSFAIL: [chars] may have a failed channel Explanation One of the power supplies in a dual (redundant) power supply

may have failed. Recommended Action Check the inputs to the power supply or replace the faulty power supply as soon as possible to avoid an unplanned outage. If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also


465

ENV_MON Messages

perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support

Error Message %ENVM-4-WRITEERROR: Error writing temperature sensor [dec] Explanation The Cisco 2 wire (C2W) interface has encountered an error while writing to the specified temperature sensor. Recommended Action Copy the message exactly as it appears on the console or in the system log.


ENV_MON Messages This section contains environmental monitor (ENV_MON) messages.

ENV_MON-2 Error Message %ENV_MON-2-BUSBRD_TEMP: [chars] temperature has reached critical levels Explanation The specified temperature sensor has signaled an overtemperature condition. Recommended Action Check the supply. Attempt to resolve the temperature problem. Check to ensure that all router doors are in place and are closed. Check to ensure that the fans are operating. Remove the affected cards, check their temperature and, if required, allow them to cool and reinsert them. Operation of overtemperature equipment is not recommended because the equipment might become damaged. If the condition is not resolved, power the unit off. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


466

ENV_MON Messages

ENV_MON-5 Error Message %ENV_MON-5-CSC_FAIL_SUPPLY_POWER_TO_FANS: CSC in slot [dec] could not supply power to fan tray Explanation The indicated clock and scheduler card (CSC) could not supply power to the fan trays. Recommended Action Turn the router off and then on to attempt to clear the problem. Remove and

reinsert the fan tray, and then the CSC. If the problem persists, contact your Cisco technical support representative to replace the indicated CSC.

ENV_MON-6 Error Message %ENV_MON-6-CANTSHUT: Cannot shut down card in this slot Explanation The attempt to shut down the line card has failed. Recommended Action No action is required.

Error Message %ENV_MON-6-INSALM: ALARMCARD [chars] was inserted in slot [dec] Explanation The OIR facility has detected the insertion of an alarm card from the slot specified in

the message text. Recommended Action No action is required.

Error Message

%ENV_MON-6-INSFAN: The Fan tray has been inserted into slot [dec]

Explanation The OIR facility has detected the insertion of a PEM from the slot specified in the

message text. Recommended Action No action is required.

Error Message

%ENV_MON-6-INSPEM: PEM number [chars] inserted into slot [dec]

Explanation The OIR facility has detected the insertion of a PEM from the slot specified in the


Error Message

%ENV_MON-6-INSPEM_GSR_POWERSHELF: Powersupply [chars] inserted

Explanation The OIR facility detected the insertion of a PEM on the power shelf-basedinternet

router. Recommended Action No action is required.


467

ENV_MON Messages

Error Message %ENV_MON-6-INTERNAL_ERROR: Internal error [dec] in [chars] - contact Cisco technical support Explanation An unexpected internal error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ENV_MON-6-REMALM: ALARMCARD [chars] was removed from slot [dec] Explanation The OIR facility detected the removal of alarm card from the slot specified in the


Error Message

%ENV_MON-6-REMFAN: The Fan tray has been removed from slot [dec]

Explanation The OIR facility has detected that the fan tray has been removed. Recommended Action No action is required.

Error Message

%ENV_MON-6-REMPEM: PEM number [chars] removed from slot [dec]

Explanation The OIR facility has detected the removal of a PEM from the slot specified in the


Error Message

%ENV_MON-6-REMPEM_GSR_POWERSHELF: Powersupply [chars] removed

Explanation The OIR facility has detected the removal of a PEM on a power shelf-based internet

router. Recommended Action No action is required.


468

EOBC Messages

EOBC Messages This section contains Ethernet out-of-band channel (EOBC) messages.

EOBC-0 Error Message %EOBC-0-EOBC_JAM_FATAL: [chars] in slot [dec] is jamming the EOBC channel. It has been disabled. Explanation The primary supervisor engine EOBC hardware is faulty. There is no redundant

supervisor engine to take over, so the switch has been shut down. Recommended Action Immediately replace the supervisor engine in the slot specified in the error

message.

EOBC-2 Error Message %EOBC-2-EOBC_JAM: EOBC channel is jammed. source of the problem and recover if possible.

Attempting to diagnose the

Explanation The SP is unable to communicate with other processors in the system because of a

problem with the EOBC channel. The problem could be due to faulty EOBC hardware on the supervisor engine or due to a module with a faulty connector to the EOBC channel. The SP will attempt to recover automatically. The success of this automatic recovery will be communicated through more messages. Recommended Action No action is required.

Error Message %EOBC-2-EOBC_JAM_RECOVERED: [chars] in slot [dec] is jamming the EOBC channel. It has been disabled. [chars] Explanation The specified module has faulty hardware and is adversely affecting the operation of the

switch. The remaining modules will be power cycled and brought online. Recommended Action Immediately replace the module in the slot specified in the error message.

EOBC-3 Error Message %EOBC-3-NOEOBCBUF: No EOBC buffer available.

Dropping the packet.

Explanation The EOBC receive buffer pool has been exhausted. No further input packets can be

processed until some buffers are returned to the pool. Recommended Action After buffers are returned to the pool, if processing continues normally, no

action is required. Otherwise, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at


469

EOS Messages

http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

EOS Messages This section contains EOS ASIC (EOS) messages.

EOS-2 Error Message %EOS-2-EOS_INIT_FAILURE : The EOS FPGA initialization failed due to [chars] Explanation The EOS FPGA initialization was not successful because of a hardware problem with

the board. This condition will cause packet drops. Recommended Action Contact your Cisco technical support representative to obtain a replacement

board.

Error Message %EOS-2-EOS_INT : [chars] Explanation A fatal interrupt has occurred. As a result, the device has been reinitialized. Recommended Action Copy the message exactly as it appears on the console or in the system log.



470

EOS Messages

Error Message %EOS-2-INT : [chars] Explanation A fatal interrupt has occurred. As a result, the device has been reinitialized. If the reported condition is a CRC or ECC parity error, the device will attempt to correct the error. Infrequent parity errors can usually be ignored, but persistent parity errors may indicate a hardware failure. Recommended Action Reseat and reset the module. If the error persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %EOS-2-NULL_EOS_OBJECT : The EOS device object pointer is set to NULL Explanation The memory location of the EOS device object is invalid. The EOS FPGA operation is

disabled and the device interrupt is now masked. Recommended Action Copy the message exactly as it appears on the console or in the system log.


EOS-3 Error Message %EOS-3-EOS_PAUSE_FAIL: [chars] Explanation An attempt to pause the forwarding of traffic from an EOS ASIC interface FPGA to

another ASIC has timed out. Depending on the status register value of the ASIC interface FPGA, traffic disruption might occur. Recommended Action If normal traffic processing does not resume, copy the message exactly as it

appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support


471

EOS Messages


Error Message %EOS-3-EOS_UNPAUSE_FAIL : EOS status register is 0x[hex] Explanation An attempt to unpause traffic from the EOS FPGA to the Hyperion ASIC timed out. This

condition may lead to traffic disruption. Recommended Action If normal traffic processing does not resume, copy the message exactly as it


Error Message %EOS-3-QUEUE_ALLOC_FAILED: Failed to allocate queue in the EOS FPGA for SPA in bay ([dec]) Explanation The system failed to allocate the EOS ASIC queue for the SPA in the specified bay. This condition might lead to traffic disruption. Recommended Action If normal traffic processing does not resume, copy the message exactly as it


EOS-4 Error Message %EOS-4-EOS_WARN_INT: [chars] Explanation The EOS ASIC interface FPGA received a nonfatal interrupt. This interrupt should not

affect normal operation. Recommended Action No action is required.


472

EOU Messages

EOS-5 Error Message %EOS-5-PAUSE_FAIL: [chars] Explanation An attempt to pause the forwarding of traffic from an EOS ASIC interface FPGA to

another ASIC has timed out. Depending on the status register value of the ASIC interface FPGA, traffic disruption might occur. Recommended Action If normal traffic processing does not resume, copy the message exactly as it


EOU Messages This section contains Extensible Authentication Protocol over UDP (EOU) messages.

EOU-2 Error Message %EOU-2-PROCESS_ERR: Router could not create a EAPoUDP process Explanation The system could not create an Extensible Authentication Protocol over UDP process. Recommended Action Reload the system.

EOU-4 Error Message %EOU-4-BAD_PKT: IP=[IP_address]| Bad Packet=[chars] Explanation The system received an invalid or malformed EAP packet from the specified host. Recommended Action Check the specified host for the EAP operation.

Error Message %EOU-4-MSG_ERR: Unknown message event reveived Explanation The EOU authentication process received an unknown message event. Recommended Action If this message recurs, reload the system.


473

EOU Messages

Error Message %EOU-4-PROCESS_STOP: PROCESS=[chars]| ACTION=[chars]. Explanation The specified process has stopped. Recommended Action Reload the system.

Error Message %EOU-4-SOCKET: EAPoUDP socket binding fails for PORT=[hex]. Check if the interface has valid IP address. Explanation The EOU socket could not bind its port to an valid interface address. Recommended Action This condition is probably caused by a missing IP address on the interface.

Configure a valid IP address for the interface.

Error Message %EOU-4-UNKN_EVENT_ERR: UNKNOWN Event for HOST=[IP_address]| Event=[dec]. Explanation An unknown event for the EOU process has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %EOU-4-UNKN_PROCESS_ERR: An unknown operational error occurred. Explanation The EOU process cannot function due to an internal system error. Recommended Action Reload the system.

Error Message %EOU-4-UNKN_TIMER_ERR: An unknown Timer operational error occurred Explanation The EOU process cannot function due to an internal system error. Recommended Action Reload the system.


474

EOU Messages

Error Message %EOU-4-VALIDATION: Unable to initiate validation for HOST=[IP_address]| INTERFACE=[chars]. Explanation EOU could not start posture validation for the specified host. This condition is probably

caused by a failure to bind the EOU port. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %EOU-4-VERSION_MISMATCH: HOST=[IP_address]| Version=[dec] Explanation The specified host detected a mismatch in EOU versions. Recommended Action Copy the message exactly as it appears on the console or in the system log.


EOU-5 Error Message %EOU-5-AAA_DOWN: AAA unreachable. METHODLIST=[chars]| HOST=[IP_address]| POLICY=[chars]. Explanation AAA servers defined by the method list are unreachable for the given host and the policy

being applied. Recommended Action Check connectivity to the AAA servers.

Error Message %EOU-5-RESPONSE_FAILS: Received an EAP failure response from AAA for host=[IP_address] Explanation The system received an EAP failure response from AAA, which indicates the

unsuccessful validation of host credentials. Recommended Action No action is required.


475

EOU Messages

EOU-6 Error Message %EOU-6-AUTHSTATUS: [chars]|[IP_address] Explanation This message displays the authentication status (Success, Failure) for the specified host. Recommended Action This message is informational. No action is required.

Error Message %EOU-6-AUTHTYPE: IP=[IP_address]| AuthType=[chars] Explanation This message displays the authentication type for the specified host. Recommended Action This message is informational. No action is required.

Error Message %EOU-6-CTA: IP=[IP_address]| CiscoTrustAgent=[chars] Explanation This message indicates whether or not Cisco Trust Agent was detected on the specified

host. Recommended Action Install Cisco Trust Agent on the host if it was not detected.

Error Message %EOU-6-IDENTITY_MATCH: IP=[IP_address]| PROFILE=EAPoUDP| POLICYNAME=[chars] Explanation Because the system found the specifed host in the EOU identity profile, there will be no EOU association with the host and the local policy. Recommended Action If you do not want the specified host to be exempted from authentication,

remove its entry from EOU identity profile.

Error Message %EOU-6-POLICY: IP=[IP_address]| [chars]=[chars] Explanation The system received policy attributes from AAA for the specified host. Recommended Action This message is informational. No action is required.

Error Message %EOU-6-POSTURE: IP=[IP_address]| HOST=[chars]| Interface=[chars] Explanation This message displays the posture validation status for the specified host. Recommended Action This message is informational. No action is required.

Error Message %EOU-6-SESSION: IP=[IP_address]| HOST=[chars]| Interface=[chars] Explanation An entry was created or deleted for the host on the specified interface. Recommended Action This message is informational. No action is required.


476

EPIF Messages

Error Message %EOU-6-SQ: IP=[IP_address]| STATUSQUERY|[chars] Explanation The status query result for the specified host either failed or was invalid. Recommended Action This message is informational. No action is required.

EPIF Messages Error Message %EPIF_PORT-0-INTERNAL_PANIC: [chars] Explanation A Panic Condition.

EPLD_STATUS_OPEN Messages This section contains EPLD programming status file data processing (EPLD_STATUS_OPEN) messages.

EPLD_STATUS_OPEN-4 Error Message %EPLD_STATUS_OPEN-4-ERROR_ALLOC: %Error: Can’t allocate [dec] bytes for epld status data Explanation The system is unable to allocate required memory to access the file. Recommended Action Determine the memory usage of the system, and retry the operation.

Error Message %EPLD_STATUS_OPEN-4-ERROR_OPEN: %Error: Can’t open [chars] Explanation The system is unable to open the specified file. Recommended Action Ensure that the filename is correct. Enter the dir command to verify the

filename.

Error Message %EPLD_STATUS_OPEN-4-ERROR_READ: %Error: status file [chars] read failed Explanation An unknown error occurred while the system was reading the status program file to a

local buffer. Recommended Action Delete and recopy the file. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support


477

EPLD_STATUS_OPEN Messages


Error Message %EPLD_STATUS_OPEN-4-ERROR_REMOVE: %Error: status file [chars] remove failed Explanation An unknown error occurred while the system was removing the status program file from

nonvolatile memory. Recommended Action Delete the file manually. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %EPLD_STATUS_OPEN-4-ERROR_SIZE: %Error: Bad file size [chars] Explanation The file is too small or too large for a programming status file. Recommended Action Enter the dir command, and determine the size of the file. Retry the operation.

Error Message %EPLD_STATUS_OPEN-4-ERROR_WRITE: %Error: status file [chars] write failed Explanation An unknown error occurred while the system was writing the status program file to

nonvolatile memory. Recommended Action Delete and recopy the file. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


478

EPM Messages

EPM Messages This section contains Policy Enforcement Module (EPM) messages.

EPM-4 Error Message %EPM-4-POLICY_APP_FAILURE: IP=%i| MAC=%e| AUDITSESID=%s| AUTHTYPE=%s| POLICY_TYPE=%s| POLICY_NAME=%s| RESULT=FAILURE| REASON=%s Explanation The displayed policy for the client could not be applied by the Policy Enforcement

Module (EPM) for the reason indicated in the message. Recommended Action Take appropriate action based the failure reason indicated in the message.

EPM-6 Error Message %EPM-6-AAA: POLICY=%s | EVENT=%s Explanation A download request has been sent and downloaded successfully for the specified

downloadable ACL (dACL). Recommended Action No action is required.

Error Message %EPM-6-IPEVENT: IP=%i| MAC=%e| AUDITSESID=%s| AUTHTYPE=%s| EVENT=%s Explanation An IP wait, release, or assignment event has occurred with respect to the specified host. Recommended Action No action is required.

Error Message %EPM-6-POLICY_APP_SUCCESS: IP=%i| MAC=%e| AUDITSESID=%s| AUTHTYPE=%s| POLICY_TYPE=%s| POLICY_NAME=%s| RESULT=SUCCESS Explanation The displayed policy for the client has been applied successfully by the EPM. Recommended Action No action is required.

Error Message %EPM-6-POLICY_REQ: IP=%i| MAC=%e| AUDITSESID=%s| AUTHTYPE=%s| EVENT=%s Explanation A policy application or remove request has been received by the EPM. Recommended Action No action is required.


479

ERR_C6K_Stack_MIB Messages

ERR_C6K_Stack_MIB Messages This section contains error messages.

Error Message %ERR_C6K_STACK_MIB-3-ERR_C6K_STACK_MIB_ICC_NO_PROC: [chars]: Failed to create the vs_stack_mib_sp ICC Process Explanation Failed to create the vs_stack_mib_sp ICC Process. Recommended Action No action is required.

Error Message %ERR_C6K_STACK_MIB-3-ERR_C6K_STACK_MIB_ICC_Q_NULL: [chars]: Failed to create the ICC queue for C6K STACK MIB Explanation Failed to create the ICC queue for C6K STACK MIB. Recommended Action No action is required.

ERR_DET Messages This section contains error detection messages.

ERR_DET-5 Error Message %ERR_DET-5-ERR_DET_LOW_MEM: Very low memory, dump debuginfo, local %u, io %u Explanation A low-memory condition was detected. Debugging information will be dumped. Recommended Action No action is required.

Error Message %ERR_DET-5-ERR_DET_NO_EOBC_INPUT: No EOBC input, dump debuginfo, interval %u, times %u Explanation No Ethernet Out-of-Band Channel (EOBC) input was received. Debugging information

will be dumped. Recommended Action No action is required.


480

ESCON Messages

ESCON Messages This section contains Enterprise Systems Connection (ESCON) messages.

ESCON-3 Error Message %ESCON-3-ACCESS_FAIL: LRC access Failed Explanation Line card redundancy controller (LRC) access has failed. Recommended Action Remove and reinsert the ESCON aggregation card. If the problem persists,

power cycle the ESCON aggregation card. If the problem still persists, replace the ESCON aggregation card.

Error Message %ESCON-3-CRC16_ERR_THR_ALM: ESCON CRC-16 Error Threshold [chars] Explanation The threshold of allowable CRC-16 errors has been exceeded. Recommended Action Check the client receive cable and the SFP optics. If the problem persists, copy


Error Message %ESCON-3-CRC32_ERR_THR_ALM: CRC-32 Error Threshold [chars] Explanation The threshold of allowable CRC-32 errors has been exceeded. Recommended Action Check the client receive cable and SFP optics. If the problem persists, copy the



481

ESCON Messages

Error Message %ESCON-3-ESCON_RDWRFAIL: Read/write failed [[chars]] Explanation A read or write error occurred while the hardware was being accessed. Recommended Action Remove and reinsert the ESCON aggregation card. If the problem persists,


Error Message %ESCON-3-HEC_ERR_THR_ALM: CDL-HEC Error Threshold [chars] Explanation The threshold of allowable CDL HEC errors has been exceeded. Recommended Action Check the network cable for sharp bends, and ensure the connectors are clean

and connected properly.

Error Message %ESCON-3-HW_LASER_DOWN_ALM: Remote Loss of Light [chars] Explanation The optics laser has been disabled. Recommended Action Check the remote client receive cable and the SFP optics.

Error Message %ESCON-3-IDPROM_ACCESS_FAIL: Access to IDPROM Failed Explanation The IDPROM could not be accessed. Recommended Action Remove and reinsert the ESCON aggregation card. If the problem persists,


Error Message %ESCON-3-INT_LPBK_FAIL: Internal CardLoopback Failed Explanation An internal card loopback has failed. Recommended Action Remove and reinsert the ESCON aggregation card. If the problem persists,


Error Message %ESCON-3-LASER_TX_FAULT_ALM: Optic Laser Transmit Fault [chars] Explanation An optical laser transmission fails on an ESCON aggregation card. Recommended Action Remove and reinsert the ESCON SFP optics. If the problem persists, replace

the ESCON SFP optics.

Error Message %ESCON-3-LOCAL_FL_LASER_DOWN_ALM: Local Failure [chars] Explanation The optics laser has been disabled. Recommended Action Check the trunk and switch fabric connection.


482

ESCON Messages

Error Message %ESCON-3-LOSS_OF_LIGHT_ALM: Transceiver Loss of Light [chars] Explanation The cable for the transceiver has been cut or removed. Recommended Action Check the client receive cable and the SFP optics.

Error Message %ESCON-3-LOSS_OF_LOCK_ALM: Transceiver CDR Loss of Lock [chars] Explanation The CDR cannot lock onto the signal. Recommended Action Check the client receive cable and the SFP optics.

Error Message %ESCON-3-LOSS_OF_SYNC_ALM: Transceiver Loss of Sync [chars] Explanation The transceiver has lost its synchronization. Recommended Action Check the client receive cable and the SFP optics.

Error Message %ESCON-3-LPBK_THRU_PSC_FAIL: Loopback through PSC Failed Explanation An attempt to loopback through the processor and switch card (PSC) has failed. Recommended Action Remove and reinsert the ESCON aggregation card. If the problem persists,


Error Message %ESCON-3-MIB_HW_LASER_DOWN_ALM: Laser Disabled [chars] [chars] [chars] Explanation The client-side laser has been disabled. Recommended Action Check the remote client receive cable and the SFP optics.

Error Message %ESCON-3-MIB_LASER_TX_FLT_ALM: Laser Transmit Fault [chars] [chars] [chars] Explanation The client laser encountered a fault during transmittal. Recommended Action Remove and reinsert the ESCON SFP optics. If the problem persists, replace

the ESCON SFP optics.

Error Message %ESCON-3-MIB_LOCAL_FL_LASER_DOWN_ALM: Local Failure, Laser Disabled [chars] [chars] [chars] Explanation The client-side laser has been disabled. Recommended Action Check the trunk and switch fabric connection.


483

ESCON Messages

Error Message %ESCON-3-MIB_LOSS_OF_LIGHT_ALM: Loss of Light [chars] [chars] [chars] Explanation The client side transceiver detects a loss of light on an ESCON aggregation card. Recommended Action Check the client receive cable and the SFP optics.

Error Message %ESCON-3-MIB_LOSS_OF_LOCK_ALM: Loss of Lock [chars] [chars] [chars] Explanation The client side transceiver detects a loss of lock on an ESCON aggregation card. Recommended Action Check the client receive cable and the SFP optics.

Error Message %ESCON-3-MIB_LOSS_OF_SYNC_ALM: Loss of Sync [chars] [chars] [chars] Explanation The client side transceiver detects a loss of synchronization on an ESCON aggregation

card. Recommended Action Check the client receive cable and the SFP optics.

Error Message %ESCON-3-SEQ_ERR_THR_ALM: ESCON SEQ Error Threshold [chars] Explanation The threshold of allowable sequence errors has been exceeded. Recommended Action Check the network cable for sharp bends, and ensure that the connectors are

clean and connected properly.

Error Message %ESCON-3-SYM_ERR_THR_ALM: 8b/10b Error Threshold [chars] Explanation The threshold of allowable 8-byte or 10-byte errors has been exceeded. Recommended Action Check the client receive cable and the SFP optics.

Error Message %ESCON-3-UNKNOWN_SFP_INSERTED: Unknown SFP inserted [chars] Explanation An SFP has been inserted. Recommended Action Copy the message exactly as it appears on the console or in the system log.



484

ESF_CRASHINFO Messages

ESF_CRASHINFO Messages This section contains Extended SuperFrame crashinfo data messages.

Error Message %ESF_CRASHINFO-2-CRASHINFO_BAD_REGION: Unable to initialize crashinfo data collection Unknown region type specified: [chars] Explanation Initialization of the crashinfo data collection facility failed. An unknown region type

was specified. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ESF_CRASHINFO-2-CRASHINFO_BAD_VENDOR_ID: Unable to initialize crashinfo data collection - the device vendor ID is invalid: [hex], should be: [hex] Explanation Initialization of the crashinfo data collection facility failed due to an incorrect device

vendor ID. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ESF_CRASHINFO-2-CRASHINFO_COLLECTION_FAILED: Unable to collect ESF crashinfo data Explanation ESF crashinfo data collection has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



485



Error Message %ESF_CRASHINFO-2-CRASHINFO_DEV_IN_RESET: Unable to initialize crashinfo data collection - the device is still in reset: [chars] Explanation Initialization of the crashinfo data collection facility failed due to the device being in

reset state. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ESF_CRASHINFO-2-CRASHINFO_INIT_FAILED: Unable to initialize ESF crashinfo data collection: [chars] Explanation Initialization of the ESF crashinfo data collection facility failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ESF_CRASHINFO-2-CRASHINFO_PCI_CMD_STAT: Unable to initialize crashinfo data collection PCI_CMD_STAT error indication: [hex] Explanation Initialization of the crashinfo data collection facility failed due to a PCI_CMD_STAT

error indication. Recommended Action Copy the message exactly as it appears on the console or in the system log.



486



Error Message %ESF_CRASHINFO-2-CRASHINFO_UNSUPPORTED_START_STR: Unable to initialize crashinfo data collection Start string symbol not supported: [chars] Explanation Initialization of the crashinfo data collection facility failed due to unsupported start

string. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ESF_CRASHINFO-2-INIT_FAILED: Unable to create crashinfo file, subsystem not properly initialized Explanation An attempt to produce a crashinfo prior to successful completion of subsystem

initialization has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ESF_CRASHINFO-2-OPEN_FAILED: Unable to open crashinfo file [chars] ([dec]) Explanation Unable to open the file that was used to gather crashinfo. Recommended Action Copy the message exactly as it appears on the console or in the system log.



487



Error Message %ESF_CRASHINFO-2-WRITE_FAILED: Unable to write to crashinfo file [chars]: [chars] Explanation Unable to open the file that was used to gather crashinfo. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ESF_CRASHINFO-2-WRITING_CRASHINFO: Writing crashinfo to [chars] Explanation Crashinfo data is written to the specified file. Recommended Action Copy the message exactly as it appears on the console or in the system log.



488

ESF_DRIVER Messages

ESF_DRIVER Messages This section contains SIP-400 ESF driver messages.

Error Message %ESF_DRIVER-2-CHECKSUM_FAILURE: Loading of the CPU code on [chars] failed due to checksum error Explanation When code is loaded onto the CPU of the ESF engine, the code is read back and a

checksum is calculated. The checksum that was read before the code was loaded onto the CPU does not match the checksum that was read after the code was loaded. This condition is an indication of a failure of the Rambus RAM for the ESF engine. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ESF_DRIVER-2-FORWARDING_PROCESSOR_READ_FAILURE: Read of register address [hex] failed on [chars]. Explanation The host processor tried to read a forwarding processor register on the ESF engine. The

read failed after several retries because of collisions with other accesses to that register. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ESF_DRIVER-2-FORWARDING_PROCESSOR_WRITE_FAILURE: Write of register address [hex] failed on [chars]. Explanation The host processor attempted to write a register on the forwarding processor for the ESF

engine. The write failed after several retries because of collisions with other messages that were attempting to access that register. Recommended Action Copy the message exactly as it appears on the console or in the system log.



489

ESF_DRIVER Messages


Error Message %ESF_DRIVER-2-PCI_BUS_ERROR: A PCI bus error occurred on [chars]: [chars] (addr=[hex]). Explanation The host processor communicates with the ESF engine by using a PCI interface. While

a PCI transaction was being performed, the transaction failed, which caused a bus error on the host processor. The address specified in the message text is the approximate address of the PCI transaction Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %ESF_DRIVER-2-PROD_ID_FAILURE: Retrieving the product id failed on [chars] Explanation The host processor could not read the product ID register of the ESF engine. This

condition occurs if the ESF engine fails to initialize. Recommended Action Copy the message exactly as it appears on the console or in the system log.



490

ESF_DRIVER Messages

Error Message %ESF_DRIVER-2-RDRAM_INIT_FAILURE: RDRAM failed to init on [chars]: condition = [chars]. Explanation During initialization of the Rambus DRAM, several waiting conditions occur while the

code is polling a register to obtain a lock bit. One of the waiting conditions has exceeded the timeout period. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ESF_DRIVER-2-RDRAM_SETUP_FAILURE: The initialization of the RDRAM failed on the [chars] Explanation The Rambus DRAM could not be initialized. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ESF_DRIVER-2-SRAM_SETUP_FAILURE: The initialization of the SRAM failed on the [chars] Explanation The SRAM could not be initialized. Recommended Action Copy the message exactly as it appears on the console or in the system log.



491

ESF_DRIVER Messages

Error Message %ESF_DRIVER-2-START_FORWARDING_PROCESSOR_FAILURE: The starting of forwarding processor failed on the [chars] Explanation The forwarding processors of the ESF engine have to be started before processing can

begin. The CPU on the ESF engine assists in the starting of the forwarding engines. The CPU reported that an error occurred while the forwarding engines were being started. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ESF_DRIVER-2-UCODE_LOAD_FAILURE: The loading of microcode failed (rc=[dec]) on [chars] Explanation Before processing can begin, microcode has to be loaded on each forwarding processor

of the ESF engine. The CPU on the ESF engine assists in the loading of the microcode. While microcode was being loaded, the CPU reported an error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ESF_DRIVER-2-UNEXPECTED_PCI_DOORBELL_INT: Received an unexpected PCI interrupt ([dec]) from [chars] (mb0=[hex] mb1=[hex] mb2=[hex] mb3=[hex] Explanation The CPU on the ESF engine communicates to the host processor through the PCI

interface using various bits in an interrupt register. This error indicates that the host processor does not know how to interpret one of those bits. Recommended Action Copy the message exactly as it appears on the console or in the system log.



492

ESF_IPC Messages


Error Message %ESF_DRIVER-2-UNKNOWN_VENDOR_ID: The vendor id ([hex]) of [chars] does not match any known vendor id. Explanation The vendor ID on the ESF engine does not match the vendor ID that is supplied by the

manufacturer. Recommended Action Copy the message exactly as it appears on the console or in the system log.


ESF_IPC Messages This section contains IPX2800 IPC messages.

ESF_IPC-2 Error Message %ESF_IPC-2-BAD_HANDLER_ID: An invalid handler ID was specified: [hex] Explanation An invalid handler ID was specified. The handler ID is required to specify which thread

the IPC message is being sent to. Recommended Action Copy the message exactly as it appears on the console or in the system log.



493

ESF_IPC Messages

Error Message %ESF_IPC-2-INVALID_ARGUMENT: An invalid argument was specified: [chars] Explanation An invalid argument was specified to one of the IPC library functions. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ESF_IPC-2-PRINT_DATA_INDICATION_FAILED: An error occurred trying to process a PRINT DATA request: [hex] ([dec]:[dec]:[dec]): [chars] ([hex] [hex] [hex]) Explanation An error occurred in processing the PRINT DATA request from a thread. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ESF_IPC-2-SEND_MSG_TIMEOUT: IPC command timeout: [hex] [hex] [hex] [hex]. Explanation The thread to which an IPC command was issued did not respond in the required time

period. Recommended Action Copy the message exactly as it appears on the console or in the system log.



494

ESF_IPC Messages

Error Message %ESF_IPC-2-START_MSG_TIMEOUT: A timeout occurred waiting for the NP to register to support processing IPC commands. Explanation Each network processor (NP) must register to handle processing an IPC soon after

startup. If it does not register within the required time period, then initialization cannot be completed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ESF_IPC-2-UNABLE_TO_ACCESS_ESF_MEMORY: Unable to access NP memory: [chars] Explanation An error occurred trying to access network processor (NP) memory. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ESF_IPC-2-UNABLE_TO_CREATE_MSG: Unable to create IPC message Explanation Insufficient resources exist to create a message used for processing the requested IPC

command. Recommended Action Copy the message exactly as it appears on the console or in the system log.



495

ESF_IPC Messages

Error Message %ESF_IPC-2-UNABLE_TO_SEND_MSG: Unable to send IPC message Explanation Insufficient resources exist to send a message used for processing the requested IPC

command. Recommended Action Copy the message exactly as it appears on the console or in the system log.


ESF_IPC-3 Error Message %ESF_IPC-3-FATAL_ERROR_MSG: Fatal Error indication from [hex] ([dec]:[dec].[dec]): [chars] Explanation A thread has generated a fatal error indication. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ESF_IPC-3-NON_FATAL_ERROR_MSG: Error indication from [hex] ([dec]:[dec].[dec]): [chars] Explanation A thread has generated a nonfatal error indication. Recommended Action Copy the message exactly as it appears on the console or in the system log.



496

ESF_IPC Messages

Error Message %ESF_IPC-3-NON_FATAL_ERROR_MSG_ERROR: Error indication from [hex] ([dec]:[dec].[dec]): [hex] [hex] [hex] Explanation An error occurred trying to process a nonfatal error indication from a thread running on

a network processor. Recommended Action Copy the message exactly as it appears on the console or in the system log.


ESF_IPC-6 Error Message %ESF_IPC-6-PRINT_DATA_INDICATION: Print Data indication from [chars] - [hex] ([dec]:[dec].[dec]): [chars] Explanation A network processor thread requested the display of a particular section of memory.

This is normally used for debugging. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ESF_IPC-6-STATUS_UPDATE_MSG: Status update from [hex] ([dec]:[dec].[dec]): [hex] Explanation A thread has generated a status update indication. Recommended Action Copy the message exactly as it appears on the console or in the system log.



497

ETHCNTR Messages

ETHCNTR Messages This section contains the Ethernet controller (ETHCNTR) error messages. These messages are a result of a failure of the switch software when trying to program the hardware. Most of these errors lead to incorrect switch behavior, and should be reported to your Cisco technical support representative.

ETHCNTR-2 Error Message %ETHCNTR-2-MOLSENDTIMEOUT: Molecule send timeout, queue [dec], molecule [hex] [hex] Explanation An attempt to read or write one or more of the hardware settings failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


ETHCNTR-3 Error Message %ETHCNTR-3-FLOWCONTROL_DUPLEX_ERROR: Flowcontrol will not take effect until duplex is set to auto. Explanation Flow control cannot take effect until the duplex mode has been set to auto. Recommended Action Set the duplex mode to auto.

Error Message %ETHCNTR-3-HALF_DUX_COLLISION_EXCEED_THRESHOLD: Collisions at [chars] exceed threshold. Considered as loop-back. Explanation The collision at a half-duplex port has exceeded the threshold, and the port is considered to be a loopback port. Recommended Action No action is required.


498

ETHER_CFM Messages

Error Message %ETHCNTR-3-MOLSENDINT: Molecule send from interrupt handler Explanation An interrupt handler is accessing the hardware in a manner that is not permissible for

an interrupt handler. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ETHCNTR-3-NO_HARDWARE_RESOURCES: Not enough hardware resources. Shutting down [chars] Explanation The system currently contains more VLANs and routed ports than the hardware can

support. Recommended Action Reduce the total number of VLANs and routed ports to fewer than 1,023. To

maintain this configuration and connectivity across reboots, save the configuration to NVRAM.

ETHER_CFM Messages This section contains Ethernet Connectivity Fault Manager (ETHER_CFM) messages.

ETHER_CFM-3 Error Message %ETHER_CFM-3-CROSS_CONNECTED_CSI: Service ID of received CC [chars] does not match local Service ID [chars]. Explanation For a specified service within a domain, the service ID in the continuity check (CC)

message should match the locally configured service ID. Recommended Action Verify that the service IDs are configured correctly using the show ethernet cfm domain command.

Error Message %ETHER_CFM-3-LR_FROM_WRONG_FP: received Loopback Reply with correct Transaction IDentifier, but from a Maintenance Point different than Loopback Message’s destination Explanation An unknown destination sent a reply to a loopback message that was intended for

another device. Recommended Action Verify that the correct destination MAC address was specified in the CLI while

sending the loopback message.


499

ETHER_LMI Messages

Error Message %ETHER_CFM-3-MEP_NOT_CONFIGURED: received CC from unconfigured remote MEP. Explanation While performing a crosscheck, a continuity check (CC) message was received from a

remote maintenance endpoint (MEP) that is not configured under the domain submode. Recommended Action Verify whether the remote MEP should be added to the remote MEP list under the domain using the show ethernet cfm domain command.

Error Message %ETHER_CFM-3-RCV_LOCAL_MPID: MPID of CC matches local MPID. Explanation The remote maintenance endpoint identifier (MPID) matches a MPID configured

locally for the service. Recommended Action Either the local MPID or remote MPID should be changed because the MPID

should be unique for each service in a network.

Error Message %ETHER_CFM-3-TM_EGRESS_BOUNDRY: egress path found for TM is at a higher level than the traceroute message. Explanation Traceroute found a domain boundary on egress because the egress port level is higher

than the traceroute message level. Recommended Action Check that the MIP level on the egress port is at an appropriate level.

ETHER_CFM-5 Error Message %ETHER_CFM-5-IGNORED_VLAN: Ignored VLAN %u in ’%s’ Explanation An invalid VLAN was ignored in the configuration. Recommended Action No action is required.

ETHER_LMI Messages This section contains Ethernet Local Management Interface (ETHER_LMI) messages.

ETHER_LMI-6 Error Message %ETHER_LMI-6-MISMATCHED_VLAN_CONFIGURED: VLAN %s configured but not in VLAN mapping for UNI %s Explanation VLANs are configured on the user network interface (UNI) but do not exist according

to VLAN mapping received from the network by the Ethernet local management interface (LMI). Recommended Action Verify that the configuration of VLANs on the UNI match those assigned.


500

ETHERNET_LACP Messages

Error Message %ETHER_LMI-6-MISMATCHED_VLAN_NOT_CONFIGURED: VLAN %s not configured but in VLAN mapping for UNI %s Explanation VLAN mappings received from the network by the Ethernet local management interface

(LMI) do not match those that are configured on the user network interface (UNI). Recommended Action Verify that the configuration of VLANs on the UNI match those assigned.

ETHERNET_LACP Messages This section contains Ethernet Link Aggregation Control Protocol (LACP) messages.

Error Message %ETHERNET_LACP-1-ISSU_NOMEMORY: Unit [dec], no memory for [chars] Explanation The requested operation could not be accomplished because of a low memory condition. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message %ETHERNET_LACP-3-ISSU_SENDFAILED: LACP ISSU: send message failed, rc = [dec] Explanation The sending of a message has failed. This is an informational message only. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %ETHERNET_LACP-4-ISSU_INCOMPATIBLE: lacp-issu-compat: returned FALSE Explanation The ISSU compatibility matrix check has failed. This is an informational message only. Recommended Action Copy the error message exactly as it appears on the console or in the system



501

ETHERNET_LACP Messages

Error Message %ETHERNET_LACP-4-ISSU_XFORM: [chars]: failed, rc=[chars] Explanation The ISSU transform has failed. This is an informational message only. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %ETHERNET_LACP-4-RF_CLIENT_BUNDLE: LACP HA: Unable initiate checkpoint bundle mode. Explanation LACP is unable to initialize checkpoint bundle mode. This is an informational message

only. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %ETHERNET_LACP-4-RF_CLIENT_INIT: LACP HA: Unable to initiate RF client. Explanation LACP is unable to initialize as a RF client. This is an informational message only. Recommended Action Copy the error message exactly as it appears on the console or in the system



502

ETHERNET_MLACP Messages

ETHERNET_MLACP Messages This section contains Ethernet Multichassis Link Aggregation Control Protocol (LACP) messages.

ETHERNET_MLACP-3 Error Message %ETHERNET_MLACP-3-PEER_ICCP_VERSION_INCOMPATIBLE: Peer ICCP version [dec] is incompatible with local ICCP version [dec]. Explanation mLACP peer is running with a different version of ICCP. Incompatible ICCP would

prevent mLACP from working properly. Recommended Action Reboot peer with identical IOS version would correct the issue. Compatible

ICCP version between different IOS images can still be achieved by doing show lacp multichassis group on the both devices to check if ICCP versions are compatible. If ICCP versions are incompatible, repeat IOS image loading and CLI above until a compatible image is loaded.

Error Message %ETHERNET_MLACP-3-SYS_CFG_DUPL_ID: Remote mLACP peer has duplicate mLACP node-id [dec] Explanation A remote mLACP peer is configured with the same mLACP node-id as this device. Recommended Action Reconfigure the mLACP node-id to be unique between the two devices with

the mlacp node-id configuration command. Refer to the mLACP configuration section of the Cisco IOS documentation for more information on configuring mLACP.

Error Message %ETHERNET_MLACP-3-SYS_CFG_INVALID_ID: Received invalid mLACP node-id [dec] from peer Explanation A remote mLACP peer is configured with an invalid mLACP node-id. Recommended Action Reconfigure the peer to send a valid mLACP node-id with the mlacp node-id

configuration command. Refer to the mLACP configuration section of the Cisco IOS documentation for more information on configuring mLACP.

ETHERNET_MLACP-4 Error Message %ETHERNET_MLACP-4-CORE_CONNECTED: mLACP has recovered from a core isolation failure. Attempting to recover [dec] LAGs in redundancy group [int] Explanation mLACP has recovered from core isolation and has attempted to recover the LAGs in the

redundancy group. Recommended Action This message may not require any action. However the show lacp multi-chassis group and show lacp multi-chassis port-channel commands may be used to verify the state of the mLACP port-channels. Reference the mLACP section of the IOS documentation for details on core isolation failures and related configuration commands.


503


Error Message %ETHERNET_MLACP-4-CORE_ISOLATION: mLACP Core isolation failure: Attempting to failover [dec] LAGs in redundancy group [int] Explanation mLACP has detected isolation from the core and has attempted to failover. Recommended Action Use the show redundancy interchassis command to determine which core

facing interface has triggered the isolation failure. Correct the failure for the given interface, this will clear the mLACP core isolation failure. Reference the mLACP section of the IOS documentation for more information on core isolation failures and related configuration commands.

Error Message %ETHERNET_MLACP-4-ICRM_CLIENT_RECV_BAD_LEN: Received an mLACP TLV with bad length [dec], total message length [dec] Explanation The mLACP TLV length is longer than the total message length. Recommended Action Issue the show version command on the local and remote devices to get the

versions of IOS that are running. Reference the mLACP section of the IOS documentation to verify that mLACP is compatible between the IOS versions on the two devices. If the versions are compatible and the message still appears then please contact your Cisco technical support representative. Provide the representative with the exact message being seen as well as the output of the following commands, show version, show run, show lacp multi-chassis group, and show lacp multi-chassis port-channel.

Error Message %ETHERNET_MLACP-4-ICRM_CLIENT_RECV_NO_TYPELEN: Received an mLACP TLV without a type and/or length field ([dec]) Explanation mLACP received an improperly formatted TLV from the peer. As a result the local and peer devices may have mismatched state data. Recommended Action Issue the show version command on the local and remote devices to get the

versions of IOS that are running. Reference the mLACP section of the IOS documentation to verify that mLACP is compatible between the IOS versions on the two devices. If the versions are compatible and the message still appears then please contact your Cisco technical support representative and provide the representative with the exact error message being seen as well as the versions of IOS from both devices.

Error Message %ETHERNET_MLACP-4-ICRM_CLIENT_RECV_REJ: Received rejected mLACP TLV from peer with message ID [dec] Explanation A remote mLACP peer has rejected an mLACP TLV. Recommended Action Issue the show version command on the local and remote devices to get the

versions of IOS that are running. Reference the mLACP section of the IOS documentation to verify that mLACP is compatible between the IOS versions on the two devices. If the versions are compatible and the message still appears then please contact your Cisco technical support representative and provide the representative with the exact error message being seen as well as the versions of IOS from both devices.


504


Error Message %ETHERNET_MLACP-4-PEER_DISCONNECT: An mLACP peer has disconnected from redundancy group [int], attempting to reconnect Explanation mLACP has detected that a peer device from the specified redundancy group has

disconnected. mLACP will attempt to reconnect to the device until successful. Recommended Action This message is typically caused by a configuration event on the peer router,

and so no action may be necessary. However if this message is unexpected then issue the show redundancy interchassis command on both the local and peer mLACP devices to determine which peer member IP has lost communication. Use this information to further debug the network communication issue, and re-enable communication with the peer. Reference the mLACP section of the IOS documentation for more information on peer down failures.

Error Message %ETHERNET_MLACP-4-PEER_DOWN: mLACP Peer down failure: Attempting to make [dec] local LAGs active in redundancy group [int] Explanation mLACP has detected a peer down failure and has attempted to make the local

port-channels become active. Recommended Action The peer down failure should be corrected by re-enabling communication with

the peer mLACP device. Use the show redundancy interchassis command on both the local and peer mLACP devices to determine which peer member IP has lost communication. Use this information to further debug the network communication issue, and re-enable communication with the peer. Reference the mLACP section of the IOS documentation for more information on peer down failures.

Error Message %ETHERNET_MLACP-4-PEER_RECONNECT_FAILED: The attempt to reconnect to the peer in redundancy group [int] has failed Explanation After an mLACP peer device disconnected, an attempt was made to reconnect, however

that attempt has failed. Recommended Action To reinitialize the connection, unconfigure mlacp interchassis group from the port-channel, and then reconfigure it. After doing that, issue show redundancy interchassis to get the peer member IP connection status and the mLACP connection state. If the peer member IP connection status is not CONNECTED then there is a more basic communication issue that needs to be fixed. Otherwise if the peer member IP is CONNECTED but the mLACP state is not CONNECTED, then there could be a software issue. In that case collect the output of show redundancy interchassis, show lacp multi-chassis group, and show lacp multi-chassis port-channel. Then please contact your Cisco technical support representative and provide the collected information.

Error Message %ETHERNET_MLACP-4-PEER_UP: mLACP has recovered from a peer down failure in redundancy group [int] Explanation mLACP is now in communication with the peer device, and has recovered from a

previous peer down failure. Recommended Action This message may not require any action. However the show lacp multi-chassis group and show lacp multi-chassis port-channel commands may be used to verify the state of the mLACP port-channels. Reference the mLACP section of the IOS documentation for details on peer down failures and related configuration commands.


505

ETHERNET_OAM Messages

ETHERNET_MLACP-6 Error Message %ETHERNET_MLACP-6-PEER_CONNECT: mLACP peer is now connected in redundancy group [int] Explanation This message indicates that the local mLACP device is now connected to a peer device

in the specified redundancy group. Recommended Action No action is required. To view the peer information the command show lacp

multi-chassis port-channel or show lacp multi-chassis group may be issued.

ETHERNET_OAM Messages This section contains Ethernet Operation, Administration, and Maintenance (ETHERNET_OAM) messages.

ETHERNET_OAM-2 Error Message %ETHERNET_OAM-2-CRIT_ERR: The Ethernet OAM protocol has encountered the critical error: [chars]. Explanation The protocol has encountered a critical error as specified in the message. Recommended Action Copy the message exactly as it appears on the console or in the system log.


ETHERNET_OAM-3 Error Message %ETHERNET_OAM-3-LOOPBACK_ERROR: Loopback operation on interface [chars] has encountered an error([chars]). Explanation Because of the specified error, the loopback operation has ended abnormally. Recommended Action No action is required.


506


ETHERNET_OAM-5 Error Message %ETHERNET_OAM-5-EVENTTLV: [chars] is received from the remote client on interface [chars]. Explanation An event TLV is received from the remote OAM client, which detected errors in

receiving frames from this local interface. Recommended Action No action is required.

Error Message %ETHERNET_OAM-5-LINK_MONITOR: [chars] detected over the last [chars] on interface [chars]. Explanation A monitored error has been detected to have crossed the user-specified threshold. Recommended Action No action is required.

Error Message %ETHERNET_OAM-5-LINK_MONITOR_HT_CROSS: High threshold was crossed on Port Channel [chars]’s last operational member port [chars]. Interface [chars] is kept online. Explanation A monitored error has been detected to have crossed the user-specified threshold. Recommended Action No action is required.

ETHERNET_OAM-6 Error Message %ETHERNET_OAM-6-ENTER_SESSION: The client on interface [chars] has entered the OAM session. Explanation Ethernet OAM client on the specified interface has detected a remote client and has

entered the OAM session. Recommended Action No action is required.

Error Message %ETHERNET_OAM-6-EXIT_SESSION: The client on interface [chars] has left the OAM session. Explanation Ethernet OAM client on the specified interface has experienced some state change. Recommended Action No action is required.


507


Error Message %ETHERNET_OAM-6-LINK_TIMEOUT: The client on interface [chars] has timed out and exited the OAM session. Explanation The Ethernet OAM client on the specified interface has not received any OAMPDUs in

the number of seconds for timeout that were configured by the user. The client has exited the OAM session. Recommended Action No action is required.

Error Message %ETHERNET_OAM-6-LOOPBACK: Interface [chars] has [chars] the [chars] loopback mode. Explanation The specified interface has entered or exited loopback mode because of protocol control

or an external event, such as the interface link going down. Recommended Action No action is required.

Error Message %ETHERNET_OAM-6-RFI: The client on interface [chars] has received a remote failure indication from its remote peer(failure reason = [chars]) Explanation The remote client indicates a Link Fault, or a Dying Gasp (an unrecoverable local

failure), or a Critical Event in the OAMPDU. In the event of Link Fault, the Fnetwork administrator may consider shutting down the link. Recommended Action In the event of a link fault, consider shutting down the link.

Error Message %ETHERNET_OAM-6-RFI_CLEAR: The client on interface %s has received a clear of remote failure indication from its remote peer(failure reason = %s action = %s) Explanation The remote client received a message to clear a link fault, or a dying gasp (an

unrecoverable local failure), or a critical event in the operations, administration, and maintenance Protocol Data Unit (OAMPDU). The error-disable state can only be cleared by entering the shutdown command followed by the no shutdown command on the interface. Recommended Action Copy the message exactly as it appears on the console or in the system log.



508

ETHER_SERVICE Messages

ETHER_SERVICE Messages This section contains Ethernet service messages.

ETHER_SERVICE-6 Error Message %ETHER_SERVICE-6-EVC_STATUS_CHANGED: status of %s changed to %s Explanation The Ethernet virtual connection (EVC) status has changed. Recommended Action No action is required.

Error Message %ETHER_SERVICE-6-EVC_VLAN_NOT_CONFIGURED: VLANs %s not configured at %s but is in a CEVLAN/EVC map Explanation The specified VLANs are part of the CEVLAN/EVC map for an EVC associated with

the specified interface, but the VLANs are not configured on that interface. Recommended Action Verify the configurations of VLANs on the interface.

ETSEC Messages This section contains messages.

ETSEC-1 Error Message %ETSEC-1-INITFAIL: PQ3/FE([dec]), Init failed, CSR[dec]=[hex] Explanation The software failed to initialize/restart an Ethernet/Fast Ethernet interface. Recommended Action Clear the interface. If the message recurs, call your technical support

representative for assistance.

Error Message %ETSEC-1-INITFAILP: PQ3/FE([dec]), Init failed at [chars] Explanation The FEC could not allocate a I/O buffer pool. Recommended Action Clear the interface. If the message recurs, call your technical support



509

ETSEC Messages

Error Message %ETSEC-1-MEMERR: PQ3/FE([dec]), Memory error, CSR[dec]=[hex] Explanation The interface could not access system resources for a long time. This problem may

occur under very heavy loads. Recommended Action The system should recover. No action is required. If the message recurs, call

your technical support representative for assistance.

Error Message %ETSEC-1-SHOWFAIL: PQ3/FE([dec]), Memory error at [chars] Recommended Action Clear the interface. If the message recurs, call your technical support


ETSEC-2 Error Message %ETSEC-2-EXCEPTION: Fatal Error, Interface [chars] not transmitting Explanation The software detected critical error and recovery failed, resulting in system crash. Recommended Action Collect crashinfo files, syslogs and console dumps.

Error Message %ETSEC-2-NOISL: Interface [chars] does not support ISL Explanation The interface cannot be configured as an ISL trunk. Recommended Action Check the configuration.

ETSEC-3 Error Message %ETSEC-3-CREATE_IBC_FAILED: Creation of etsec ibc idb failed Explanation etsec ibc idb creation has failed Recommended Action Copy the error message exactly as it appears on the console or in the system



510

ETSEC Messages

Error Message %ETSEC-3-INIT_IBC_FAILED: Initialization of etsec ibc failed Explanation etsec ibc initialization has failed Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %ETSEC-3-INIT_ICDM_FAILED: Initialization of icdm driver failed Explanation icdm driver initialized failed for etsec ibc Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %ETSEC-3-INIT_MAC_DRIVER_FAILED: Initialization of ethernet mac driver failed Explanation ethernet mac driver initialized failed for etsec ibc Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %ETSEC-3-MASKED_RCV_INTR: etsec_ibc_rcv_interrupt called while masked: [int] Explanation etsec_ibc_rcv_interrupt called while already masked Recommended Action Copy the error message exactly as it appears on the console or in the system



511

ETSEC Messages


Error Message %ETSEC-3-NO_BUFFER_POOLS: Initialization of private buffer pools failed Explanation Private buffer pools were not created for etsec ibc. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %ETSEC-3-NO_PARTICLE: no particle available to populate the ethernet dma ring Explanation No particle available to populate the ethernet dma ring. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %ETSEC-3-OVERFLO: PQ3/FE([dec]), Receive overflow Explanation While receiving a frame, the controller chip’s local buffer transmitted insufficient data because data could not be transferred to DRAM fast enough to keep pace with its input rate. Normally, such a problem is temporary, depending on transient peak loads within the system. Recommended Action The system should recover. No action is required.

Error Message %ETSEC-3-OWNERR: PQ3/FE([dec]), Buffer ownership error, pak=[hex] Explanation The software detected an error in descriptor ownership. Recommended Action Try a later version of the software. If the message recurs, call your technical

support representative for assistance.


512

ETSEC Messages

Error Message %ETSEC-3-RECOVER_TX: Interface [chars] TX workaround invoked Explanation The software detected the interface was not transmittingpackets. The workaround patch

has been invoked. Recommended Action The system should recover. No action is required.

Error Message %ETSEC-3-RESTART: Interface [chars] Restarted Due to [chars] Error Explanation The software detected critical error and etsec driver was restarted to restore EoBC

traffic flow. Recommended Action The system should recover. No action is required.

Error Message %ETSEC-3-RX_ADD_BUFFER_FAILED: particle not added to the ethernet dma ring Explanation Particle not added to the Ethernet dma ring. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %ETSEC-3-UNDERFLO: PQ3/FE([dec]), Transmit underflow Explanation While transmitting a frame, the controller chip’s local buffer received insufficient data because data could not be transferred to the chip fast enough to keep pace with its output rate. Normally, such a problem is temporary, depending on transient peak loads within the system. Recommended Action The system should recover. No action is required.

ETSEC-4 Error Message %ETSEC-4-BABBLE: PQ3/FE([dec]), Babble error, CSR[dec]=[hex] Explanation The transmitter has been on the channel longer than the time taken to transmit the largest

frame. Recommended Action The system should recover. No action is required.


513

ETSEC Messages

ETSEC-5 Error Message %ETSEC-5-COLL: PQ3/FE([dec]), Excessive collisions, TDR=[dec], TRC=[dec]. Explanation Ethernet/Fast Ethernet is seeing multiple collisions. This may occur under heavy loads. Recommended Action The system should recover. No action is required.

Error Message %ETSEC-5-EXCESSCOLL: PQ3/FE([dec]), Excessive collision Explanation Ethernet/Fast Ethernet is seeing multiple collisions. This may occur under heavy loads. Recommended Action The system should recover. No action is required.

Error Message %ETSEC-5-FIFO_RECOVER: [chars] ([dec]) detected freeze, last([dec]) new([dec]) tx cntr. tx_pending ([dec]). applying patch Explanation The interface is used for IPC/SCP communication between RP and SP. In a rare situation

when fifo tx engine is stuck and requires a toggle there is no data loss when the recovery patch is executed. Patch is applicable to MPC8548 version 2.0 silicons only. Recommended Action None - software patch will be executed.

Error Message %ETSEC-5-LATECOLL: PQ3/FE([dec]), Late collision Explanation Late collisions occurred on the Ethernet/Fast Ethernet interface. Recommended Action If the interface is Fast Ethernet, verify that both peers are in the same duplex


Error Message %ETSEC-5-LOSTCARR: PQ3/FE([dec]), Lost carrier. Transceiver problem? Explanation The cable is not connected to the port. Recommended Action Connect the cable to the port.


514

EVENT_TRACE Messages

EVENT_TRACE Messages This section contains event trace subsystem messages.

EVENT_TRACE-3 Error Message %EVENT_TRACE-3-GROUP_ID: Duplicate registration of group-id [dec] Explanation Software subsystem is trying to register a group ID for an event trace that has already

been used by another subsystem. Recommended Action Copy the message exactly as it appears on the console or in the system log.


EXFREE Messages This section contains external memory manage messages.

EXFREE-2 Error Message %EXFREE-2-EXMEMFREE: Free a non allocated ptr [hex] size [dec]. Explanation The system is trying to free a memory. Not all of it is marked as allocated. Recommended Action Copy the message exactly as it appears on the console or in the system log.



515

EXFREE Messages

Error Message %EXFREE-2-EXMEMINIT: EXMEM [dec]: [chars] Explanation The requested external memory allocator failed to be initialized. The reasons are not

clear. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %EXFREE-2-EXMEMLOCK: [chars] detected error ptr [hex] size [dec]. Explanation The system is attempting to lock or unlock a memory location that was either already

locked or unlocked. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %EXFREE-2-EXMEMPARAM: Bad parameter ([dec]) when calling to the allocator utility Explanation An illegal parameter was used when a call to the allocator utility was made. This

condition may indicate data corruption. Recommended Action Copy the message exactly as it appears on the console or in the system log.



516

EXPRESS_SETUP Messages

Error Message %EXFREE-2-EXMEMRESET: EXMEM [dec]: [chars] Explanation The requested external memory allocator failed to be reset. The reasons are not clear. Recommended Action Copy the message exactly as it appears on the console or in the system log.


EXFREE-4 Error Message %EXFREE-4-EXMALLOCFAIL: External memory allocation of [int] bytes failed from EXMEM [dec] Explanation 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. Recommended Action Copy the message exactly as it appears on the console or in the system log.


EXPRESS_SETUP Messages This section contains Express Setup messages.

EXPRESS_SETUP-3 Error Message %EXPRESS_SETUP-3-UNABLE_TO_RESET_CONFIG: [chars] Explanation The system is unable to reset the configuration. Recommended Action Copy the message exactly as it appears on the console or in the system log.



517

EXPRESS_SETUP Messages


EXPRESS_SETUP-6 Error Message %EXPRESS_SETUP-6-CONFIG_IS_RESET: [chars] Explanation The configuration is reset and the system will now reboot. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %EXPRESS_SETUP-6-MODE_ENTERED: Explanation Express setup mode is now active. Recommended Action No action is required.

Error Message %EXPRESS_SETUP-6-MODE_EXITED: Explanation Express setup mode is no longer active. Recommended Action No action is required.


518

FABRIC Messages

FABRIC Messages This section contains Fabric (FABRIC) messages.

FABRIC-3 Error Message %FABRIC-3-DISABLE_FAB: The fabric manager disabled active fabric in slot [dec] due to the error ([dec]) on this channel (FPOE [dec]) connected to slot [dec] Explanation The firmware detected a severe fabric error and reported the error to the fabric manager.

The manager has disabled the active fabric. Recommended Action The Fabric Manager will automatically resynchronize the fabric channel to recover from the error. The problem may occur when the fabric card or the line card does not have good contact with backplane. You should insert the fabric and line cards firmly into the chassis.

Error Message %FABRIC-3-EM_RECOVERY_ISSU_NEGO_FAILED: Attempting EM recovery for EM type %d, but ISSU negotiation was unsuccessful/incomplete. Explanation On a switchover, the fabric manager is trying to recover for events that were opened on

the peer before the switchover, but not closed. These events are maintained by the event manager (EM). The fabric manager found that ISSU negotiation was either unsuccessful or incomplete. Because the data may not have been synchronized correctly between the active and standby devices, this is an error condition. Recommended Action No action is required.

Error Message %FABRIC-3-ERRORS_DDRSYNC: Line card DDR channels sync error fpoe/slot [dec]/[dec]. Explanation A transmit FIFO overrun or underrun in the DDR channels has occurred. The error

indicates a clock mismatch. If this condition is persistent, the hardware is faulty. Recommended Action The system will attempt to resynchronize the DDR channel and the fabric

channel.

Error Message %FABRIC-3-LOST_SYNC: [chars] endpoint of fpoe:[dec] lost Sync. to [chars] fabric,#[dec] times recovered success, trying to recover now! Explanation The endpoint has lost synchronization with the fabric and is trying to recover. Recommended Action No action is required.


519

FABRIC Messages

FABRIC-4 Error Message %FABRIC-4-DISABLE_FAB: Please disable fabric service: active sup [dec] (error [dec]) Explanation All supervisor engine fabric channels have errors. Recommended Action Disable fabric services for the switch. Disable power for external switch fabric

modules. Disable fabric service for internal switch fabric modules, but keep the supervisor engines powered on.

Error Message %FABRIC-4-LINECARDMODE_CFG_MISMATCH: Service module in the slot [dec] cannot pass traffic to the distributed etherchannel configured. Explanation Because of the hardware limitation of the service module in the slot specified, traffic

from these modules cannot pass through the distributed EtherChannel as configured. Recommended Action Force the service modules switching mode to bus mode by entering the fabric switching-mode force busmode command, or change the channel configuration so that the affected modules do not need to pass traffic through the EtherChannel.

Error Message %FABRIC-4-SERVICEMOD_CHANGE_BUSMODE: The switching mode of service module in slot [dec] can be changed to its default as the distributed etherchannel config is removed. Explanation The switching mode of the service modules can be reverted to the default by entering

the no fabric switching-mode force busmode command. Recommended Action Restore the default by entering the no fabric switching-mode force busmode

command.

Error Message %FABRIC-4-SUP_SWITCHOVER: Supervisor switchover from slot [dec] (error [dec]) Explanation The active supervisor engine fabric channel has errors. Recommended Action A switchover to the redundant supervisor engine occurs automatically.

FABRIC-5 Error Message %FABRIC-5-CANNOT_CLEAR_BLOCK: The fabric in slot [dec] cannot support clear-block feature. Explanation A user enabled the clear-block mechanism, but the fabric in the specified slot cannot

support the feature. Recommended Action No action is required.


520

FABRIC Messages

Error Message %FABRIC-5-CANNOT_SUPPORT_FP_INVERSION: The module you have installed in slot [dec] is running an older revision of firmware/software which may cause inconsistent system behavior. Please refer to the release notes for a minimum recommended software release for mentioned module. Explanation The specified module can not support FP bit inversion with the current software release.

The fabric clear block will disregard the COS setting for this module. Recommended Action No action is required.

Error Message %FABRIC-5-CLEAR_BLOCK: Clear block option is [chars] for the fabric in slot [dec]. Explanation The fabric manager has changed the status of the clear-block mechanism for all fabric

channels. The status (on or off) is indicated in the message. Recommended Action No action is required.

Error Message %FABRIC-5-ERRORS_BUFFER: In fabric slot [dec], memory buffer for fpoe/slot [dec]/[dec] is full. Explanation Either the buffer size is less than the packet size or the uplink buffer cannot respond to

flow control from the fabric. Recommended Action Examine the fabric memory configuration.

Error Message %FABRIC-5-ERRORS_TIMEOUT: Time out for input from fpoe/slot [dec]/[dec] to slot [dec]. Explanation A timeout in the fabric input buffer occurred because of a problem from the destination slot. The transient error is observed when the module is removed. If the error is persistent, the module local bus might be locked. Recommended Action Reset the module in the destination slot if the error is persistent.

Error Message %FABRIC-5-FABRIC_FAILOVER: The fabric in slot [dec] has failed over due to fabric errors on slot [dec]. Fabric in slot [dec] is now the current active fabric. Explanation The Switch Fabric Module in the specified slot failed over and active supervisor switch

to former standby supervisor.

Error Message No action is required.%FABRIC-5-LINECARDMODE_BUS_FORCED: The switching mode of module in slot [dec] is forced to bus-mode. Explanation The fabric switching-mode force busmode command has been applied. Recommended Action No action is required.


521

FABRIC_INTF_ASIC Messages

Error Message %FABRIC-5-NOT_ALLOWED: Power not allowed to module [dec] : [chars] . Explanation Certain types of linecards is not given power for some reaon. Detailed reason is given

in the message body. Recommended Action No action is required.

FABRIC-6 Error Message %FABRIC-6-TIMEOUT_ERR: Fabric in slot [dec] reported timeout error for channel [dec] (Module [dec], fabric connection [dec]) Explanation Firmware code on the fabric detected that the input or output buffer was not moving. To recover from this condition, the system will automatically resynchronize the fabric channel. Recommended Action The system automatically recovers from this condition by doing a fabric

channel resynchronization. If the system experiences this condition persistently, directly connect to the console of the fabric and the module to determine if any errors are being reported by the firmware. Also, reseat and reset the module.

FABRIC_INTF_ASIC Messages This section contains switch fabric interface ASIC (FABRIC_INTF_ASIC) messages.

FABRIC_INTF_ASIC-4 Error Message %FABRIC_INTF_ASIC-4-DEV_CONFIG_FAIL: The Switch Fabric interface ASIC configuration failed Explanation The switch fabric interface ASIC could not be configured. Recommended Action If the switch fabric is inactive (down), this message can be expected. If the

module comes online and traffic processing resumes, ignore this message. Otherwise, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. On the Route Processor, capture the show logging and show version commands.


522


Error Message %FABRIC_INTF_ASIC-4-FABRICCRCERRS: [dec] Fabric CRC error events in 100ms period Explanation The switch fabric interface encountered more CRC error events than the supervisor

engine CRC error threshold allows. Recommended Action The line card has notified the supervisor engine and the error has been logged. No action is required from the user.

FABRIC_INTF_ASIC-5 Error Message %FABRIC_INTF_ASIC-5-CHAN_LINK_SPEED_OOB: Array access bounds violated, channel_num=[int], link_num=[int], speed=[int] Explanation Cisco IOS code has attempted to access an internal array with an invalid index for SSA

channel number or link number or speed. Recommended Action No action is required if there is no system impact. If traffic stops or linecard

fails, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %FABRIC_INTF_ASIC-5-DEV_INIT_FAILURE: The Switch Fabric interface ASIC initialization failed Explanation The switch fabric interface ASIC was not successfully initialized. As a result, this device is not operational and has been disabled. Recommended Action Copy the message exactly as it appears on the console or in the system log.



523


Error Message %FABRIC_INTF_ASIC-5-FABRICDOWN_CRCERRS: [dec] Fabric CRC error events in 100ms period Explanation The switch fabric interface encountered more CRC errors than the maximum configured

threshold. However, the reason for this error is that the switch fabric is inactive (down). The line card has notified the supervisor engine of this condition and the error has been logged. Recommended Action This message indicates normal system operation. No action is required.

Error Message %FABRIC_INTF_ASIC-5-FABRICDOWN_SYNCERRS: [dec] Fabric sync error events in 100ms period Explanation The switch fabric interface encountered more synchronization errors than the maximum

configured threshold. However, the reason for this error is that the switch fabric is inactive (down). Recommended Action This message indicates normal system operation. No action is required.

Error Message %FABRIC_INTF_ASIC-5-FABRICSYNC_DONE: Fabric sync on [chars] channel done. Explanation The switch fabric interface ASIC was resynchronized. Recommended Action No action is required.

Error Message %FABRIC_INTF_ASIC-5-FABRICSYNC_REQ: Fabric sync requested on [chars] channel ([dec]) Explanation The line card has requested that the supervisor engine resynchronize its fabric interface

ASIC. Recommended Action No action is required.

Error Message %FABRIC_INTF_ASIC-5-NOFABRICPROCESS: The Switch Fabric interface fabric process could not be created Explanation The switch fabric interface does not have a link process running: the system failed to

create this process. This module will not support the fabric interface. Recommended Action Copy the message exactly as it appears on the console or in the system log.



524


Error Message %FABRIC_INTF_ASIC-5-NULL_DEV_OBJECT: The Switch Fabric interface device object pointer is set to NULL Explanation The memory location of the switch fabric interface device object is invalid. The switch

fabric interface ASIC operation is disabled and the device interrupt is now masked. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %FABRIC_INTF_ASIC-5-SMB_ACCESSERROR: The Module Switch Fabric interface ASIC cannot be accessed Explanation The switch fabric interface ASIC access (read or write) failed. The serial bus that

connected to the switch fabric interface ASIC on this module is not functioning correctly. Recommended Action Copy the message exactly as it appears on the console or in the system log.


FABRIC_SP Error Message %FABRIC-SP-5-CLEAR_BLOCK: Clear block option is [chars] for the fabric in slot [dec]. Explanation The fabric manager has changed the status of the clear-block mechanism for all fabric

channels. The status (on or off) is indicated in the message. Recommended Action No action is required.

Error Message %FABRIC-SP-5-FABRIC_MODULE_ACTIVE: The Switch Fabric Module in slot [dec] became active Explanation The Switch Fabric Module in the specified slot is active as the switching fabric. Recommended Action No action is required.


525

FIB Messages

FIB Messages This section contains Forwarding Information Base (FIB) messages.

FIB-2 Error Message %FIB-2-FIBFEATSESINIT: Error initializing CEF repop feature session queue Explanation Initialization of a CEF feature session queue could not be accomplished because of a

low-memory condition. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message %FIB-2-FIBRETRY_EXCEEDED: CEF table download to slot [dec] not performed as IPC port did not come up Explanation The FIB could not be fully downloaded. As a result of this condition, hardware

switching might not be functional on the module. Recommended Action Reset the module to overcome this condition.

Error Message %FIB-2-HW_IF_INDEX_ILLEGAL: Attempt to create CEF interface for [chars] with illegal index: [dec] Explanation An internal software error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %FIB-2-IF_NUMBER_ILLEGAL: Attempt to create CEF interface for [chars] with illegal if_number: [dec] Explanation An internal software error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



526

FIB Messages


FIB-3 Error Message %FIB-3-FIBSBNOFN: Missing [chars] subblock [chars] function for [chars] Explanation Functions for distributing this subblock are missing from the image. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %FIB-3-MAC_ACCT: [chars]: [chars] Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %FIB-3-PREC_ACCT: [chars]: [chars] Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



527

FIB Messages


FIB-4 Error Message %FIB-3-FIB_STATS_ERROR: Internal Error - type [dec], slot [dec], total_len [dec], msg_len [dec], seg_len [dec] Explanation An internal software error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %FIB-4-FIBNULLHWIDB: Missing hwidb for fibhwidb [chars] (ifindex [dec]) Explanation An internal software error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %FIB-4-FIBNULLIDB: Missing idb for fibidb [chars] (if_number [dec]). Explanation An internal software error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



528

FIB Messages


Error Message %FIB-4-FIBRETRY_WARNING: IPC port for slot [dec] to become available for CEF table download (retried [dec] times) Explanation The FIB table failed to download for the number of times specified in the message. Recommended Action If the FIB table is successfully downloaded in a subsequent retry, no action is

required. If the operation is not successful, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %FIB-4-FIBXDRINV : Invalid format. [chars] Explanation Because the VLAN interface was deleted while still in the administrative up state, the

HSRP MAC address remains in the adjacency table. This message is not sent if the VLAN interface is first put into an administrative down state before being deleted. Recommended Action No action is required.

FIB-6 Error Message %FIB-6-FIBLCTUNDELSEQ: Update received on a linecard for a deleted tunnel([chars]) - ignored. Explanation An update was received on a line card for a tunnel that has already been deleted. The

update was ignored. Recommended Action No action is required.


529

FILESYS Messages

FILESYS Messages This section contains filesys messages.

FILESYS-3 Error Message %FILESYS-3-RUNNING_SYNC_FAILED: The active is unable to synchronize the running configuration to standby, so standby will be reloaded Explanation The active supervisor engine cannot access its running configuration to synchronize the

configuration to the standby supervisor engine. This can be caused by temporary resource issues such as high CPU. Recommended Action No action is required. This message is for informational purposes only.

FILESYS-4 Error Message %FILESYS-4-CLPDINT: Management interrupts are [chars] for pcmcia device in socket [dec]. [chars] Explanation A faulty PCMCIA flash device might be generating spurious insert or remove interrupts

continuously. The PCMCIA controller’s interrupt generation will be disabled temporarily, and will be reenabled after a few seconds. If an alternate PCMCIA device is inserted while the interrupts are disabled, the alternate device may not be readable. In this case, you must remove and reinsert the PCMCIA device. Recommended Action Replace the PCMCIA flash device.

FILESYS-5 Error Message %FILESYS-5-CFLASH: Compact flash card [chars] [chars] Explanation A file system’s status has changed. Recommended Action Follow any instructions provided with the message.

Error Message %FILESYS-5-IFLASH : Internal Flash [chars] [chars] Explanation A file system’s status has changed. This can occur after the switch is converted from Catalyst OS software to Cisco IOS software. When you enter the dir bootflash: command, an unformatted flash memory returns a "bad device block info" or "invalid magic number" error message. Recommended Action Format the flash memory using the format command and follow any

instructions provided with the message. Otherwise, no action is required.


530

FILESYS Messages

Error Message %FILESYS-5-UNKNDEV : Unknown device [chars] [chars] Explanation A file system's status has changed. The flash device cannot be recognized by the switch.

The 16-MB MEM-C6K-FLC16M and 24 MB MEM-C6K-FLC24M linear flash PC cards are preformatted and are ready to use, but the MEM-C6K-ATA-1-64M and 64 MB MEM-C6K-FLC64M flash PC cards are not preformatted. You must format these cards before using them to store files. In addition, the Supervisor Engine 1 and Supervisor Engine 2 do not support the same flash PC card format. To use a flash PC card with a Supervisor Engine 2, you must format the card with a Supervisor Engine 2. To use a flash PC card with a Supervisor Engine 1, you must format the card with a Supervisor Engine 1. Recommended Action Format the flash memory using the format command and follow any

instructions provided with the message. Otherwise, no action is required.


531

FILESYS Messages


532

FM Messages

FM Messages This section contains Feature Manager (FM) messages.

FM-2 Error Message %FM-2-ACL_MERGE_EXCEPTION: ACL merge internal error due to features configured on interface [chars] in [chars] direction, traffic may be switched in software Explanation The configured features for this interface caused the merge to abort because of an

internal error. The traffic on this interface and the interfaces sharing TCAM label with this interface will be sent to the software. Recommended Action Redefine and reapply or unconfigure one or more features on the interface.

Error Message %FM-2-ACL_MERGE_NUM_ACES: ACL merge aborted due to number of ACEs threshold for features on interface [chars] in [chars] direction, traffic may be switched in software Explanation The configured features for this interface may have caused the merge to abort because

of hitting the 64000 ACE merge threshold. The traffic on this interface and the interfaces sharing the TCAM label with this interface will be sent to the software. Recommended Action Redefine and reapply or unconfigure one or more features on the interface.

Error Message %FM-2-FIE_EXCEPTION: Feature interaction internal error due to features configured on interface [chars] in [chars] direction, traffic may be switched in software Explanation The configured features for this interface caused an internal error in the feature

interaction. The traffic on this interface and the interfaces sharing the TCAM label with this interface will be sent to the software. Recommended Action Redefine and reapply or unconfigure one or more features on the interface.

Error Message %FM-2-FLOWMASK_CONFLICT: Features configured on interface [chars] have conflicting flowmask requirements, traffic may be switched in software Explanation The configured features for this interface have a flow mask conflict. The traffic on this

interface and the interfaces sharing the TCAM label with this interface may not comply with the features under this condition. The traffic on these interfaces will be sent to the software. Recommended Action Redefine and reapply or unconfigure one or more features to avoid the conflict.


541

FM Messages

Error Message %FM-2-TCAM_ERROR: TCAM programming error %d Explanation A software error caused a failure in programming ACLs into the TCAM. Recommended Action Choose the Order Dependent Merge (ODM) algorithm for merging the ACL.

Shut down the VLAN interface and reenable the interface after ten minutes. If the error message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %FM-2-TCAM_MEMORY: ACL merge abandoned when merging Interface [chars] [chars] ACLs due to insufficient memory. Interface traffic handled in Software. Explanation The capacity of the hardware TCAM has been exceeded and the packets will be now

process-switched. The first [chars] value indicates the VLAN interface for which the ACL merge fails, and the second [chars] indicates whether the ACL is ingress or egress. Recommended Action Choose the Order Dependent Merge (ODM) algorithm for merging the ACL.

Shut down the VLAN interface and reenable the interface after ten minutes. If the error message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %FM-2-TCP_FLAG_HW_EXCEPTION: No VLOUs available for TCP FLAGs for interface [chars] in [chars] direction: all features on the interface for the specified direction will be NOT effective Explanation No VLOUs are available for TCP flags. This condition cannot be handled in the software for all the features configured on the interface. A message is printed on the console to notify the user of this error condition. Because there are no features that the software can handle, the system will program an entry to permit all traffic. Recommended Action The hardware TCAM can handle up to 9 logical operations per interface and up to 64 logical operations in total. To recover from this error, recompute the ACLs for the features that cannot be handled in the software (for example, VACLs) to move entries using TCP flags before others entries are moved and to minimize the usage of TCP flags.


542

FM Messages

Error Message %FM-2-TCP_FLAG_SW_EXCEPTION: No VLOUs available for TCP FLAGs on interface [chars] in [chars] direction: traffic will be software switched, features which are NOT processable in software will be NOT effective Explanation No VLOUs are available for TCP flags. This condition cannot be handled in the software for some features configured on the interface. A message is printed on the console to notify the user of this error condition. Because there are some features that can be handled in the software (for example, VACLs and RACLs), an exception entry and traffic on this interface will be sent to the software. Recommended Action The hardware TCAM can handle up to 9 logical operations per interface and up to 64 logical operations in total. To recover from this error, recompute the ACLs for the features that cannot be handled in the software (for example, VACLs) to move entries using TCP flags before others entries are moved and to minimize the usage of TCP flags.

FM-3 Error Message %FM-3-LABELERROR: Incorrect label to [chars] vlan label attribute copy callback srclabel [dec], dstlabel [dec] Explanation The Feature Manager attribute copy callback was called with an incorrect source or

destination label. Recommended Action Enter the show running-config command. Copy the message exactly as it


Error Message %FM-3-NOTEMPTY: Illegal copy of attribute to non empty [chars] vlan label [dec] Explanation The Feature Manager attribute copy callback was called with a destination label already

being used by a VLAN or routed port. Recommended Action Enter the show running-config command. Copy the message exactly as it



543

FM Messages

Error Message %FM-3-UNKNOWNACTION: Unknown VMR access group action [hex] Explanation An internal software error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


FM-4 Error Message %FM-4-EXCESSSECONDARY: More than [dec] secondary IP addresses configured on interface [chars] Explanation When secondary IP addresses are configured on an interface, the hardware is usually

programmed so that the ICMP redirect functionality on the CPU is not notified of packets sent between two subnets configured on the same interface. If many secondary IP addresses are configured on the same interface it becomes impractical to program the hardware in this manner. This message is logged, and the CPU will be notified of every packet sent between two subnets on this interface. No ICMP redirects will be sent in error, but the CPU usage may increase because of the additional notifications. Recommended Action Enter the no ip redirects command on the interface to reduce the CPU load on

the system.

Error Message %FM-4-MPLS_RSVD_VLAN_ERROR: Failed attempt to remove the default feature from MPLS reserved vlan [chars] Explanation MPLS reserved vlan’s have a default ’permit ip any any’ ACL configured. In some

corner cases an event is generated to unconfigure this default feature. Such instances should be blocked. Recommended Action No functional impact. Contact TAC with the traceback and also with the

configuration steps that lead to the error message.

Error Message %FM-4-FLOWMASK_REDUCED: Features configured on interface [chars] have conflicting flowmask requirements, some features may work in software Explanation The configured features for this interface have a flow mask conflict. The traffic on this

interface and the interfaces sharing the TCAM label with this interface will be sent to the software. Recommended Action Redefine and reapply or unconfigure one or more features to avoid the conflict.


544

FM Messages

Error Message %FM-4-IPSG_VACL: VACL Capture & IPSG conflict on i/f [chars] Explanation Because VACL capture and IPSG is not supported on the same VLAN port, VACL

capture will be inactive. To activate VACL capture, reconfigure the feature after removing IPSG. Recommended Action Remove either IPSG or VACL capture on this interface.

Error Message %FM-4-L2_DYN_TCAM_EXCEPTION: Failed to install Dynamic TCAM entry to filter Layer 2 traffic, error status: [dec], host IP address: [IP_address], interface: [chars] Explanation There is an error in installing the per-user policies in the Dynamic TCAM region to filter

Layer 2 traffic. The TCAM might be full. As a result, host ingress traffic will be subjected to the default interface ACL. Recommended Action Attempt to free up TCAM resources.

Error Message %FM-4-L2EOU_INSP: INSPECION & L2EOU conflict on i/f [chars] Explanation The inspection feature and the Layer 2 EAP over UDP (L2EOU) feature are not

supported on the same VLAN. The inspection feature will be inactive. To activate the inspection feature, reconfigure it after removing the L2EOU feature. Recommended Action Remove either the Layer 2 EAP over UDP (L2EOU) feature or the inspection

feature from the interface.

Error Message %FM-4-L2EOU_VACL: VACL Capture & L2EOU conflict on i/f [chars] Explanation Because VACL capture and the Layer 2 EAP over UDP (EOU) feature are not supported

on the same VLAN port, VACL capture will be inactive. To activate VACL capture, reconfigure the feature after removing the L2EOU feature. Recommended Action Remove either the Layer 2 EAP over UDP (EOU) feature or VACL capture on

this interface.

Error Message %FM-4-TCAM_ADJ: Hardware ACL adjacency capacity exceeded Explanation The hardware does not have the capacity to handle all of the configured adjacencies. Recommended Action The configured policies have too many adjacencies to fit in the hardware. Use the mls tcam priority command to prioritize interfaces for hardware switching. Reduce the number of adjacencies in the policies.

Error Message %FM-4-TCAM_DYN_ENTRY_EXCEPTION: Failed to install Dynamic TCAM entry in TCAM for Interface:[chars] Explanation Dynamic installation of an ACE failed because of TCAM resource exhaustion. Layer 3

traffic will be handled by the software. Recommended Action Attempt to free up TCAM resources.


545

FMCORE Messages

Error Message %FM-4-TCAM_MASK: Hardware TCAM MASK entry capacity exceeded Explanation The hardware TCAM has exhausted its available storage and does not have the capacity

to store all configured ACLs. Recommended Action If the ACL merge algorithm is currently binary decision diagrams (BDD), space could be freed by changing the merge algorithm to order dependent merge (ODM). Enter the show fm summary command to determine the current merge algorithm. Enter the mls aclmerge algorithm odm command to change the merge algorithm from BDD to ODM. Enter the mls tcam priority command to prioritize interfaces for hardware switching. Attempt to share the same ACLs across multiple interfaces in order to reduce TCAM resource contention. If server load balancing is configured, enter the mls ip slb search wildcard rp command to reduce the amount of TCAM space used by server load balancing. After you enter the command, server load balancing will increase its utilization of the route processor.

FMCORE Messages This section contains Core Feature Manager (FMCORE) messages.

FMCORE-2 Error Message %FMCORE-2-ACL_FAILURE: Interface [chars] traffic will not comply with ACLs in [chars] direction(s) Explanation ACLs will not be applied on traffic for the specified interface because of a TCAM

resource contention. Recommended Action The configured ACLs are too large for all of them to fit in the hardware TCAM.

Use the mls tcam priority command to prioritize interfaces for hardware switching. Try to share the same ACLs across multiple interfaces to reduce TCAM resource contention.

Error Message %FMCORE-4-RACL_REDUCED: Interface [chars] routed traffic will be software switched in [chars] direction Explanation TCAM resource contention prevents ACLs from being applied in the TCAM for this

interface. The traffic on this interface will be sent to software so that the ACLs can be applied. Recommended Action The configured ACLs are too large to all fit in the hardware TCAM. Enter the

mls tcam priority command to prioritize the interfaces for hardware switching. Try to share the same ACLs across multiple interfaces to reduce TCAM resource contention.


546

FMCORE Messages

Error Message %FMCORE-2-VACL_FAILURE: Interface [chars] traffic will not comply with VACLs in [chars] direction(s) Explanation VACLs will not be applied on traffic for this interface because of a TCAM resource

contention. Recommended Action The configured ACLs are too large for all of them to fit in the hardware TCAM.


FMCORE-4 Error Message %FMCORE-4-RACL_REDUCED: Interface [chars] routed traffic will be software switched in [chars] direction Explanation A TCAM resource contention prevents ACLs from being applied in the TCAM for the

specified interface. The traffic on the interface will be sent to software so that the ACLs can be applied. Recommended Action The configured ACLs are too large for all of them to fit in the hardware TCAM.


FMCORE-6 Error Message %FMCORE-6-RACL_ENABLED: Interface [chars] routed traffic is hardware switched in [chars] direction Explanation Earlier TCAM resource contention may have prevented ACLs from being applied in the

TCAM for this interface. It has been enabled and traffic on this interface is hardware switched. Recommended Action No need to take an action for this as it is an informational message not an error

message.


547

FM_EARL6 Messages

FM_EARL6 Messages This section contains Enhanced Address Recognition Logic 6 Feature Manager (FM_EARL6) messages.

FM_EARL6-4 Error Message %FM_EARL6-4-RACL_REDUCED_MCAST_RATELIM_WARN: Enabling acl [chars] rate-limiter will cause Multicast traffic to be dropped in hardware on interface [chars] in [chars] direction Explanation A TCAM resource contention prevents routed ACLs from being programmed in the

TCAM for the specified interface in the specified direction. All Layer 3 traffic will be sent to CPU to have RACLs enforced in software. Due to a lack of resources, multicast special VMRs cannot be programmed. In this condition, rate limiting for traffic bridged to the CPU by the ACL is incompatible with the status of the multicast interface and will cause multicast traffic to be dropped in the hardware. Recommended Action Do not enter the mls unicast acl {input | output} command.

Error Message %FM_EARL6-4-VACL_PVLAN: Vacl config is NOT supported on secondary Vlan: [chars] and will be removed Explanation Current implementation of the FM does not support the configuration of VACLs on

secondary VLANs. The VACL configuration is removed from the VLAN interface once it becomes a secondary private VLAN. Both the hardware and the software will be updated accordingly. Recommended Action Make the VLAN a primary VLAN or a regular (nonprivate) VLAN. Reapply

the VLAN filter.

FM_EARL7 Messages This section contains Enhanced Address Recognition Logic 7 Feature Manager (FM_EARL7) messages.

FM_EARL7-2 Error Message %FM_EARL7-2-IPV6_PORT_QOS_MCAST_FLOWMASK_CONFLICT: QoS configuration on port [chars] conflicts for flowmask with IPv6 multicast forwarding on SVI interface [chars] Explanation The port-based QoS microflow policing configuration for this interface has a flow mask

conflict with IPv6 multicast forwarding. The traffic on the SVI interface will be sent to the software under this condition. Recommended Action Unconfigure the latest configuration change, modify the conflicting QoS

configuration, and reapply.


548

FM_EARL7 Messages

Error Message %FM_EARL7-2-IPV6_QOS_MCAST_FLOWMASK_CONFLICT: QoS configuration on interface [chars] conflicts for flowmask with IPv6 multicast forwarding, traffic may be switched in software Explanation The QoS microflow policing configuration for this interface has a flow mask conflict

with IPv6 multicast forwarding. The traffic on this interface will be sent to the software under this condition. Recommended Action Unconfigure the latest configuration change, modify the conflicting QoS

configuration, and reapply.

Error Message %FM_EARL7-2-SWITCH_PORT_QOS_FLOWMASK_CONFLICT: QoS configuration on switch port [chars] conflicts for flowmask with feature configuration on SVI interface [chars] Explanation The QoS configuration on the specified port has a conflict with a feature configuration

on an SVI interface. QoS or other features might not function correctly under these circumstances. Recommended Action Unconfigure the latest configuration change, modify the conflicting

configuration, and reapply the features.

FM_EARL7-4 Error Message %FM_EARL7-4-FEAT_CONFLICT_ON_IDB: IP ADMISSSION feature conflicts with other features on interface [chars], feature will work in software Explanation The IP admission feature conflicts with other features on this interface. Recommended Action Unconfigure any conflicting features and reapply the IP admission feature.

Error Message %FM_EARL7-4-FEAT_FLOWMASK_REQ_CONFLICT: Feature [chars] requested flowmask [chars] conflicts with other features on interface [chars], flowmask request Unsuccessful for the feature Explanation The flow mask requested by the specified feature conflicts with other features. The

requested flow mask cannot be programmed for the feature. Recommended Action Redefine and reapply the feature, or unconfigure one or more features and

reapply the specified feature to avoid the conflict.

Error Message %FM_EARL7-4-FEAT_FLOWMASK_REQ_CONFLICT_ON_SP: Flowmask requested on interface [chars] conflicts with other features on interface for Protocol [chars], flowmask request Unsuccessful for the feature Explanation The flow mask requested by the feature conflicts with other features. The requested flow

mask cannot be programmed for the feature. Recommended Action Redefine and reapply the feature, or reconfigure one or more features and

reapply the feature to avoid the conflict.


549

FM_EARL7 Messages

Error Message %FM_EARL7-4-FLOW_FEAT_FLOWMASK_REQ_FAIL: Flowmask request for the flow based feature [chars] for protocol [chars] is unsuccessful, hardware acceleration may be disabled for the feature Explanation The flow mask request for the flow-based feature is unsuccessful. This condition might

occur because of a TCAM resource exception, a flow mask registers resource exception, or an unresolvable flow mask conflict with other NetFlow-based features. The NetFlow shortcut installation and hardware acceleration for the feature might be disabled under this condition, and the feature might be applied in the software. Recommended Action Determine the netflow shortcut installation enable/disable status for the feature

by entering the show fm fie flowmask command. If the NetFlow shortcut installation and hardware acceleration is disabled for the feature, reconfigure or unconfigure some of the other features to remove the TCAM resource exception or the flow mask conflict/flow mask resource exception condition. Reapply the feature for the flow mask request to succeed, and reenable the NetFlow shortcut installation for the feature.

Error Message %FM_EARL7-4-FEAT_QOS_FLOWMASK_CONFLICT:Features configured on interface [chars] conflict for flowmask with QoS configuration on switch port [chars], traffic may be switched in software Explanation The configured features for the specified interface have flow mask conflicts with the

QoS configuration on the switch port. The traffic on this interface will be sent to software. Recommended Action Undo the latest configuration change, modify the conflicting QoS configuration on the switch port, and reapply the features.

Error Message %FM_EARL7-4-FLOW_FEAT_FLOWMASK_REQ_FAIL: Flowmask request for the flow based feature [chars] for protocol [chars] is unsuccessful, hardware acceleration may be disabled for the feature Explanation The flow mask request for the flow-based feature is unsuccessful. This may happen due

to TCAM resource exception or flow mask registers resource exception or due to unresolvable flow mask conflict with other NetFlow-based features. NetFlow shortcut installation and hardware acceleration for the feature may be disabled under this condition and the feature may be applied in software. Recommended Action Check the NetFlow shortcut installation enable/disable status for the feature by

entering the show fm fie flowmask command. If NetFlow shortcut installation/hardware acceleration is disabled for the feature, reconfigure or unconfigure some of the other features to remove the TCAM resource exception or the flow mask conflict/flow mask resource exception condition. Reapply the feature for the flow mask request to succeed and reenable the NetFlow shortcut installation for the feature.

Error Message %FM_EARL7-4-MLS_FLOWMASK_CONFLICT: mls flowmask may not be honored on interface [chars] due to flowmask conflict Explanation The configured MLS flow mask conflicts with other features or with the QoS

configuration. The traffic on the specified interface will be sent to the software. NDE might not function correctly for the specified interface under this condition. Recommended Action Remove the conflicting configuration, and reconfigure the MLS flow mask.


550

FM_EARL7 Messages

Error Message %FM_EARL7-4-MLS_FLOWMASK_NO_TCAM_RESOURCES: mls flowmask may not be honored on interface [chars] due to TCAM resource shortage Explanation The requirements for the configured features exceed the TCAM resources. The flow

mask may not be programmed in the hardware. Under this condition, the traffic on the specified interface is sent to the software. NDE may not function correctly for this interface. Recommended Action Redefine and reapply some of the features, or unconfigure one or more

features.

Error Message %FM_EARL7-4-MLS_IPV6_FORCED_COMPRESS_MODE: Use IPv6 mask values of 88 or lower in forced compress mode for consistent processing of incompressible IPv6 addresses in both hardware and software. Explanation IPv6 compress mode is a hardware feature. If compress mode is force-enabled and IPv6

ACLs are built with mask values 89 or greater, inconsistent behavior in IPv6 ACL processing could result with incompressible addresses. Using IPv6 mask values of 88 and lower while forcing compress mode ensures proper hardware processing of IPv6 ACL entries. Recommended Action Use IPv6 mask values of 88 or lower in forced compress mode for consistent

processing of incompressible IPv6 addresses in both hardware and software.

Error Message %FM_EARL7-4-NO_FLOWMASK_REGISTERS: Feature configuration on interface [chars] could not allocate required flowmask registers, traffic may be switched in software Explanation The flow mask requirements for configured features on the specified interface cannot

be met because there are no available flow mask registers. The traffic on this interface will be sent to software. Recommended Action Remove one or more NetFlow-based features or QoS microflow policing from the configuration, and reapply the features.

Error Message %FM_EARL7-4-RACL_REDUCED_MCAST_RATELIM_WARN: Enabling acl [chars] rate-limiter will cause Multicast traffic to be dropped in hardware on interface [chars] in [chars] direction Explanation A TCAM resource contention prevents routed ACLs from being programmed in TCAM

for the specified interface in the specified direction. All Layer 3 traffic will be sent to CPU to have RACLs enforced in software. Due to a lack of resources, multicast special VMRs cannot be programmed. In this condition, rate limiting for traffic bridged to CPU by the ACL is incompatible with the status of the multicast interface and will cause multicast traffic to be dropped in hardware. Recommended Action Do not enter the mls unicast acl {input | output} command.


551

FPD_MGMT Messages

Error Message %FM_EARL7-4-VACL_PVLAN: Vacl config is NOT supported on secondary Vlan: [chars] and will be removed Explanation The current implementation of the Feature Manager does not support the configuration

of VACLs on secondary VLANs. The VACL configuration is removed from the VLAN interface once it becomes a secondary private VLAN. Both the hardware and the software will then be updated accordingly. Recommended Action Change the VLAN to be a primary VLAN or a regular (nonprivate) VLAN and

reapply the VLAN filter.

FPD_MGMT Messages This section contains FPD Management Subsystem (FPD_MGMT) messages.

FPD_MGMT-2 Error Message %FPD_MGMT-2-CREATE_FAIL: Couldn’t create [chars]. Explanation The system does not have enough free main memory to create the specified resource. Recommended Action Make sure that the system main memory size meets the minimum requirement that is specified in the Cisco IOS software release note. If the system meets the minimum requirement for this Cisco IOS software release, make sure that the amount of free main memory in the system also meets the minimum memory required to use this software feature. Enter the show memory command to find out this information and add more main memory if it is necessary. If the system meets all the memory requirements, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


552

FPD_MGMT Messages

FPD_MGMT-3 Error Message %FPD_MGMT-3-BNDL_CARD_TYPE_MISMATCH: The [chars] file does not contain the card type ([hex]) in the image bundle to indicate the support of the target card. Please make sure that this is a valid FPD image [chars] file for card in [chars]. Explanation The image bundle in the specified file does not contain a correct card type value for the

target card. Recommended Action Ensure that the version of the FPD image package, which is stated in the

package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the correct one from the Cisco Software Center website. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show hw-module subslot fpd, the show upgrade fpd table, and the show upgrade fpd file fpd-pkg-url commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %FPD_MGMT-3-BNDL_CRC_CHECK_FAIL: The [chars] file contains a corrupted image bundle - CRC mismatch: current value [hex], expected value [hex]. Please make sure that this is a valid FPD image [chars] file for card in [chars]. Explanation The file failed the CRC checking process. This failure indicates a corrupt FPD image bundle or package file. Recommended Action Try to download again the required package from the Cisco Software Center

website as the specified one might be corrupted. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the Enter the show hw-module subslot fpd, the show upgrade fpd table, and the show upgrade fpd file fpd-pkg-url commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


553

FPD_MGMT Messages

Error Message %FPD_MGMT-3-BNDL_NAME_PREFIX_MISMATCH: The [chars] file contains a bundle name prefix ([chars]) that does not match with the expected value of "[chars]" for the image bundle. Please make sure that this is a valid FPD image [chars] file for card in [chars]. Explanation The content of the selected FPD image bundle does not match its filename. Recommended Action Ensure that the version of the FPD image package, which is stated in the


Error Message %FPD_MGMT-3-BNDL_WRONG_HDR_LEN: The [chars] file contains wrong header length for the image bundle: [int] bytes (expected [int] bytes). Please make sure that this is a valid FPD image [chars] file for card in [chars]. Explanation The specified file might not be a valid FPD image bundle or package file for the target

card. Recommended Action Ensure that the version of the FPD image package, which is stated in the



554

FPD_MGMT Messages

Error Message %FPD_MGMT-3-BNDL_WRONG_MAGIC_NUM: The [chars] file contains a wrong magic number for the image bundle: [hex] (expected [hex]). Please make sure that this is a valid FPD image [chars] file for card in [chars]. Explanation The specified file might not be a valid FPD image bundle or package file for the target

card or the file could be corrupted. Recommended Action Ensure that the version of the FPD image package, which is stated in the


Error Message %FPD_MGMT-3-BNDL_WRONG_SIZE: The [chars] file contains incorrect image bundle size: [int] bytes (expected [int] bytes). Please make sure that this is a valid FPD image [chars] file for card in [chars]. Explanation The specified file might not be a valid FPD image bundle or package file for the target




555

FPD_MGMT Messages

Error Message %FPD_MGMT-3-BUNDLE_EXTRACT_ERROR: Cannot extract the [chars] bundle from [chars] - [chars] Explanation There has been a bundle file-extraction error. The cause of the failure is specified in the

message. The specified file might not be a valid FPD image package file. Recommended Action Ensure that the version of the FPD image package, which is stated in the


Error Message %FPD_MGMT-3-CLOSE_FAILED: Failed to close [chars] file. Explanation There is a problem in the internal software coding. This message should not be seen

under normal operation. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %FPD_MGMT-3-DUPLICATE_UPGRADE_RESULT: Upgrade result already received for the FPD image upgrade of FPD ID [int] for [chars] card in [chars]. Explanation There is a problem in the internal software coding. This message should not be seen




556

FPD_MGMT Messages


Error Message %FPD_MGMT-3-FPD_UPGRADE_FAILED: [chars] (FPD ID=[int]) image upgrade for [chars] card in [chars] has FAILED. Explanation The FPD image upgrade process has failed for the specified device. Recommended Action Retry the upgrade operation again. If the affected card remains disabled by the system after attempts to retry the upgrade, copy the message exactly as it appears on the console or in the system log. Enter the show hw-module subslot fpd command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %FPD_MGMT-3-IMG_CRC_CHECK_FAILED: The FPD image for [chars] (FPD ID [int]) in [chars] file is corrupted - CRC mismatch: current value [hex], expected value [hex]. Please make sure that this is a valid FPD image bundle or package file for card in [chars]. Explanation The image failed the CRC checking process, this indicates a corrupt FPD image bundle

or package file. Recommended Action Ensure that the version of the FPD image package, which is stated in the



557

FPD_MGMT Messages

Error Message %FPD_MGMT-3-IMG_DATA_UNCOMPRESS_ERROR: Could not uncompress [chars] FPD image for [chars] in [chars]. Explanation An error has been detected during the uncompress operation of the compressed FPD

image data. Recommended Action Ensure that the version of the FPD image package, which is stated in the


Error Message %FPD_MGMT-3-IMG_VER_NOT_FOUND: FPD image version information is not available for [chars] card in [chars]. All the FPD images will be upgraded to recover from this error. Explanation The FPD image version information for the specified card is not available because the

system was not able to extract this information for all the FPDs in the card. This could be the result of a corrupted FPD image from a power failure. Recommended Action If the automatic upgrade feature is not enabled, then the affected card will be

disabled. If this happens, follow the recommended action described for the FPD_MGMT-5-CARD_DISABLED message.

Error Message %FPD_MGMT-3-INCOMP_BNDL_VER: The selected [chars] file contain an image bundle that has a version number that is incompatible for this IOS release - [chars]. Selected version = [int].[int], minimum compatible version = [int].[int]. Please make sure that this is a valid FPD image [chars] file for card in [chars]. Explanation The version of the selected FPD image bundle does not contain a valid version number

that is compatible for the Cisco IOS release. The major version number should be the same and the minor version number should be at least equal to the minimal required version. Recommended Action Ensure that the version of the FPD image package, which is stated in the

package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the correct one from the Cisco Software Center website. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show hw-module subslot fpd, the show upgrade fpd table, and the show upgrade fpd file fpd-pkg-url commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at


558

FPD_MGMT Messages


Error Message %FPD_MGMT-3-INCOMP_IMG_VER: Incompatible [chars] (FPD ID=[int]) image version detected for [chars] card in [chars]. Detected version = [int].[int], minimum required version = [int].[int]. Current HW version = [int].[int]. Explanation An incompatible FPD image version has been detected. The FPD image must be upgraded either automatically or manually to make the card operational. If the automatic upgrade feature is not enabled, or if the system cannot find the necessary FPD image package file, the card will be disabled. Recommended Action If the automatic upgrade feature is not enabled, then the affected card will be


Error Message %FPD_MGMT-3-INVALID_IMAGE_SIZE: The [chars] FPD image from [chars] file does not have a valid image size: expected size = [dec] bytes, actual size = [dec] bytes. Explanation The size of the specified FPD image does not have the expected size. The FPD image

bundle or package might not be a valid file. Recommended Action Ensure that the version of the FPD image package, which is stated in the



559

FPD_MGMT Messages

Error Message %FPD_MGMT-3-INVALID_IMG_VER: Invalid [chars] (FPD ID=[int]) image version detected for [chars] card in [chars]. Explanation The specified field programmable device contains an invalid version for the FPD image,

because the system was not able to extract this information from the specified card. A failed upgrade attempt might have corrupted the FPD image identification on the device. Recommended Action If the automatic upgrade feature is not enabled, the affected card will be


Error Message %FPD_MGMT-3-INVALID_PKG_FILE: The indicated file ([chars]) is not a valid FPD image package file - [chars] Explanation The file format does not appear to be a valid FPD image package. Recommended Action Ensure that the version of the FPD image package, which is stated in the


Error Message %FPD_MGMT-3-INVALID_PKG_FILE_SIZE: The indicated file ([chars]) does not have a valid FPD image package file size, minimum size = [dec] bytes. Explanation The file size of the specified FPD image package does not meet the required minimum

size. The file is too small to be a valid FPD image package file. Recommended Action Ensure that the version of the FPD image package, which is stated in the

package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the correct one from the Cisco Software Center website. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show hw-module subslot fpd, the show upgrade fpd table, and the show upgrade fpd file fpd-pkg-url commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support


560

FPD_MGMT Messages


Error Message %FPD_MGMT-3-INVALID_UPGRADE_RESULT: Invalid upgrade result ’[int]’ received for the FPD image upgrade of [chars] (FPD ID=[int]) for [chars] card in [chars]. Explanation There is a problem in the internal software coding. This message should not be seen



Error Message %FPD_MGMT-3-IPC_FAILED: Failed to send IPC message to [chars] in [chars] - [chars] Explanation The system failed to send a message via IPC to the specified card. The cause of the

specific IPC failure is specified in the message text. Recommended Action Copy the message exactly as it appears on the console or in the system log.



561

FPD_MGMT Messages

Error Message FPD_MGMT-3-MAJOR_VER_MISMATCH: Major image version mismatch detected with [chars] (FPD ID=[int]) for [chars] card in [chars]. Image will need to be [chars] from version [int].[int] to at least a minimum version of [int].[int]. Current HW version = [int].[int]. Explanation A major image version mismatch has been detected. This incompatibility will need to

be resolved by doing an upgrade or downgrade operation, either automatically, or manually, to make the card operational. If the automatic upgrade feature is not enabled, or if the system cannot find the necessary FPD image package file, then the card will be disabled. Recommended Action If the automatic upgrade feature is not enabled, the affected card will be

disabled. If this happens, you can perform the upgrade using the upgrade hw-module privileged EXEC command. For more information about these commands, refer to the FPD image upgrade feature documentation in the software configuration guide for the target card.

Error Message %FPD_MGMT-3-MISSING_BUNDLE_ENTRY: Failed to find a matching entry in the programmable device bundle information table. Explanation There is a problem in the internal software coding. This message should not be seen



Error Message %FPD_MGMT-3-MISSING_DEV_INFO: Could not find [chars] (FPD ID=[int]) information for [chars] card in [chars]. Explanation There is a problem in the internal software coding. This message should not be seen




562

FPD_MGMT Messages

Error Message %FPD_MGMT-3-MISSING_IMAGE: Could not find the required [chars] image (FPD ID=[int] and FPD version=[int].[int] compatible with HW version=[int].[int]) from the [chars]-fpd.bndl bundle in [chars] file. Please make sure that this is a valid FPD image [chars] file for [chars] card in [chars]. Explanation The specified FPD image bundle or package file might not be the correct one. If this is

an FPD image package file, then an incompatible package file might have been renamed with a filename that matched the one that the system is expecting for this Cisco IOS software release. You should never rename an FPD image package file name. Recommended Action Ensure that the version of the FPD image package, which is stated in the


Error Message %FPD_MGMT-3-OPEN_FAILED: Failed to open [chars] ([chars]). Please make sure that the required file is in a valid path. Explanation The system cannot access the required file from the specified URL. Recommended Action Ensure that the specified URL is a valid path and the system has access to the

file system where the file has been placed.

Error Message %FPD_MGMT-3-OUT_OF_MEMORY: Could not allocate the required [dec] bytes of memory. Explanation The system does not have enough free main memory to download the bundle file. Recommended Action Make sure that the system main memory size meets the minimum requirement that is specified in the Cisco IOS software release note. If the system meets the minimum requirement for this Cisco IOS software release, make sure that the amount of free main memory in the system also meets the minimum memory required to use this software feature. Enter the show memory command to find out this information and add more main memory if it is necessary. If the system meets all the memory requirements, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support


563

FPD_MGMT Messages


Error Message FPD_MGMT-3-PKG_VER_MISMATCH_NOTE: The FPD image package being used ([chars]) is not the right version for this IOS version (it appears that a ’[chars]’ package was renamed to ’[chars]’). An attempt to find the required FPD image will still be performed with this package. Explanation The indicated FPD image package that is being used in FPD automatic upgrade does not

contain the correct version information for the Cisco IOS version that is running in the system. This condition can occur if a different version of the FPD image package was renamed to match the filename that the Cisco IOS image is expecting to use. The upgrade operation will still be performed by trying to find the required FPD image from the renamed package file. Recommended Action If the upgrade operation fails because the required FPD image cannot be found

with the renamed FPD image package, replace the wrong package file with a valid one and perform the upgrade operation again.

Error Message %FPD_MGMT-3-PKG_FILE_SEARCH_FAILED: FPD image package ([chars]) cannot be found in system’s flash card or disk to do FPD upgrade. Explanation By default, if the upgrade fpd path fpd-pkg-url global configuration command is not

configured, then the system will try to locate the required FPD image package file from removable flash cards or disks that are accessible by the system for an FPD upgrade. This message indicates that the system could not find the package file. Recommended Action Make sure that the specified FPD image package file is copied into a flash card

or disk that is accessible by the system, then restart the FPD upgrade by reinserting the target card or entering a system command to reload or power-cycle the target card.

Error Message %FPD_MGMT-3-PKG_VER_FILE_EXTRACT_ERROR: Cannot extract the [chars] version file from [chars] - [chars] Explanation There is a package version file extraction error. The cause of the failure is specified in

the message. The specified file might not be a valid FPD image package file. Recommended Action Ensure that the version of the FPD image package, which is stated in the

package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the correct one from the Cisco Software Center website. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show hw-module subslot fpd, the show upgrade fpd table, and the show upgrade fpd file fpd-pkg-url commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support


564

FPD_MGMT Messages


Error Message %FPD_MGMT-3-READ_BNDL_HDR_ERROR: Failed to read the FPD bundle header from [chars] file. Explanation The specified file might not be a valid FPD image bundle or package file. Recommended Action Ensure that the version of the FPD image package, which is stated in the


Error Message %FPD_MGMT-3-READ_ERROR: Could not read the [chars] file. Explanation The system cannot read the required file from the specified URL. Recommended Action Make sure that the specified URL is a valid path and that the system has access

to the file system where the file has been placed.

Error Message %FPD_MGMT-3-SEND_IMG_FAILED: [chars] (FPD ID=[int]) image for [chars] card in [chars] has failed to be sent for upgrade operation - [chars] Explanation The FPD image was not able to be sent for the upgrade operation. The system might be

too busy to handle this operation. The affected card will be disabled by this failure. Recommended Action Wait until the system load is lower to try again with the manual upgrade

procedure by using the upgrade hw-module privileged EXEC command. If the symptom persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


565

FPD_MGMT Messages

Error Message %FPD_MGMT-3-SW_ERROR: NULL Explanation There is a problem in the internal software coding. This message should not be seen



Error Message %FPD_MGMT-3-TOO_MANY_FPD_ENTRIES: Too many FPD entries for the FPD Bundle Info Table. Required number of entries = [int], maximum number of entries allowed = [int]. Explanation There is a problem in the internal software coding. This message should not be seen



Error Message %FPD_MGMT-3-UNKNOWN_BNDL_HDR_FORMAT: Unknown header format version: [hex] Explanation There is a problem in the internal software coding. This message should not be seen




566

FPD_MGMT Messages

Error Message %FPD_MGMT-3-UPGRADE_LIST_FULL: Could not add a new entry in the FPD Management Upgrade List. No upgrade will be performed for the [chars] card in [chars]. Explanation There is a problem in the internal software coding. This message should not be seen



Error Message %FPD_MGMT-3-WRONG_IMG_DATA_LEN: The FPD image for [chars] (FPD ID [int]) in [chars] file contains wrong data length: total data length (with padding) = [int] bytes, data length = [int] bytes. Please make sure that this is a valid FPD image bundle or package file for card in [chars]. Explanation The specified file might not be a valid FPD image bundle or package file for the card. Recommended Action Ensure that the version of the FPD image package, which is stated in the


Error Message %FPD_MGMT-3-WRONG_IMG_HDR_LEN: The FPD image for [chars] (FPD ID [int]) in [chars] file contains wrong header length: [int] bytes (expected [int] bytes). Please make sure that this is a valid FPD image bundle or package file for card in [chars]. Explanation The specified file might not be a valid FPD image bundle or package file for the card. Recommended Action Ensure that the version of the FPD image package, which is stated in the

package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the correct one from the Cisco Software Center website. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show hw-module subslot fpd, the show upgrade fpd table, and the show


567

FPD_MGMT Messages

upgrade fpd file fpd-pkg-url commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %FPD_MGMT-3-WRONG_IMG_MAGIC_NUM: The FPD image for [chars] (FPD ID [int]) in [chars] file contains wrong magic number: [hex] (expected [hex]). Please make sure that this is a valid FPD image bundle or package file for card in [chars]. Explanation The specified file might not be a valid FPD image bundle or package file for the card. Recommended Action Ensure that the version of the FPD image package, which is stated in the


Error Message %FPD_MGMT-3-WRONG_IMG_MAJOR_VER: The selected FPD image for upgrade contains wrong FPD image major version number = ’[int]’ (expected number = ’[int]’) for [chars] (FPD ID [int]). Please make sure that the file being used for upgrade is a valid FPD image [chars] for card in [chars]. Explanation The file used for upgrade might not be a valid FPD image bundle or package file for the


package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the correct one from the Cisco Software Center website. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show hw-module subslot fpd, the show upgrade fpd table, and the show upgrade fpd file fpd-pkg-url commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at


568

FPD_MGMT Messages


FPD_MGMT-4 Error Message %FPD_MGMT-4-BYPASS_AUTO_UPGRADE: The automatic FPD image upgrade feature is not enabled, bypassing the image upgrade for [chars] card in [chars]. Explanation The automatic FPD image upgrade feature is not enabled. The incompatible image will

not be automatically upgraded. The card will be disabled until the image is upgraded to a compatible version. Recommended Action Enable the automatic FPD image upgrade by entering the upgrade fpd auto

global configuration command, or enter the upgrade hw-module privileged EXEC command for a manual upgrade operation. For more information about these commands, refer to the FPD image upgrade feature document for the target card. (This documentation can be found in the software configuration guide for the target card.)

Error Message %FPD_MGMT-4-CFG_NOT_SYNCED: Failed to sync "[chars]" command to standby: [chars] Explanation A FPD configuration command failed to get synced to standby RP due to the indicated

error condition. Usually this can happen if the standby RP hardware doesn’t support the type of filesystem supported on the active one. Recommended Action Configure again the command with a filesystem that is supported on both

standby and active RP. To find out if a specific filesystem is also supported on standby RP, the dir ? command can be used to display a list of filesytem supported on both standby and active RP.

Error Message %FPD_MGMT-4-UPGRADE_EXIT: Unexpected exit of FPD image upgrade operation for [chars] card in [chars]. Explanation The FPD image upgrade operation was interrupted by the physical removal of the card

from the system or by the use of other commands that have interrupted the normal operation of the target card. The partial upgrade operation might have left the card unusable because of corrupted FPD images. Recommended Action If the card does not come up after reinserting into the system, perform the recovery upgrade operation by entering the upgrade hw-module privileged EXEC command. With this command, the system will attempt to reprogram the image to recover from the previous partial upgrade operation. For more information about performing a recovery upgrade operation, refer to the FPD image upgrade feature document for the target card (this documentation can be found in the software configuration guide for the target card).


569

FPD_MGMT Messages

Error Message %FPD_MGMT-4-VERSION_CHECK_ABORTED: FPD image version check operation has been aborted for [chars] card in [chars] because manual upgrade has already being started. Explanation The FPD image version check operation required for the automatic upgrade feature is

not being performed for the specified card because the upgrade hw-module privileged EXEC command has already being executed. These two operations cannot be performed at the same time. Recommended Action If an automatic upgrade operation is required, do not enter the upgrade hw-module privileged EXEC command for the manual upgrade while the target card is initializing. Enter the show hw-module subslot fpd command and ensure that the target card is displayed in the command output before proceeding with the manual upgrade.

FPD_MGMT-5 Error Message %FPD_MGMT-5-CARD_DISABLED: [chars] card in [chars] is being disabled because of an incompatible FPD image version. Note that the [chars] package will be required if you want to perform the upgrade operation. Explanation The specified card contains an incompatible FPD image version, and is being disabled

to avoid operational problems with the existing Cisco IOS software. This can happen if the automatic upgrade feature has not been enabled with the upgrade fpd auto global configuration command, if the automatic upgrade operation failed to perform the required upgrade, or because it could not find the necessary FPD image package file. Upgrade the incompatible image so that the system can enable the card. Recommended Action The FPD image upgrade can be performed automatically by making sure that

the automatic upgrade feature is enabled with the upgrade fpd auto global configuration command and the necessary FPD image package file is located in the system’s default file system (for instance, disk0:) or in a location specified by the upgrade fpd path directory-url global configuration command. When the automatic upgrade feature is enabled, the upgrade is triggered by the reinsertion of the card into the system or the use of a system command to reload or power-cycle the target card. nother way to perform the upgrade is through the use of the upgrade hw-module privileged EXEC command. For more information about these commands, refer to the FPD image upgrade feature document for the target card (this documentation can be found in the software configuration guide for the target card).

Error Message %FPD_MGMT-5-POST_UPGRADE_REMINDER: [chars] card in [chars] will require a [chars] for the FPD image upgrade to take effect. Explanation The indicated card will require manual intervention after the FPD image upgrade. The

specified operation is required for the upgraded FPD image to take effect.

Error Message No action is required. %FPD_MGMT-5-CARD_POWER_CYCLE: [chars] card in [chars] is being power cycled for the FPD image upgrade to take effect. Explanation The specified card is being power cycled after the FPD image upgrade. This action

allows the target card to be operational with the new upgraded FPD image or images. Recommended Action This is an informational message only. No action is required.


570

FPD_MGMT Messages

Error Message %FPD_MGMT-5-UPGRADE_ATTEMPT: Attempting to automatically upgrade the FPD image(s) for [chars] card in [chars]. Use ’show upgrade fpd progress’ command to view the upgrade progress ... Explanation The automatic FPD image upgrade feature is enabled with the upgrade fpd auto global

configuration command. The system is currently upgrading an incompatible image version automatically. Recommended Action The upgrade process can take a long time. The

FPD_MGMT-6-UPGRADE_TIME message gives an estimate of the total upgrade time. No action is required.

FPD_MGMT-6 Error Message %FPD_MGMT-6-BUNDLE_DOWNLOAD: Downloading FPD image bundle for [chars] card in [chars] ... Explanation The system is downloading the field programmable device image bundle to the system main memory. Recommended Action This is an informational message only. No action is required.

Error Message %FPD_MGMT-6-OVERALL_UPGRADE: All the attempts to upgrade the required FPD images have been completed for [chars] card in [chars]. Number of successful/failure upgrade(s): [int]/[int]. Explanation All the FPD image upgrades have completed for the specified card. Recommended Action This is an informational message only. No action is required.

Error Message %FPD_MGMT-6-PENDING_UPGRADE: [int] more FPD image upgrade operation will be required on [chars] in [chars] after additional power-cycle operation on the target card. Explanation All upgrade operations have not completed, and additional power-cycle operations are

required before the upgraded or new FPD image will be applied to the system configuration. The message text specifies the number of pending upgrade operations that will be performed. More than one power-cycle operation might be required to complete the overall upgrade process. Recommended Action This is an informational message only. No action is required.

Error Message %FPD_MGMT-6-UPGRADE_PASSED: [chars] (FPD ID=[int]) image in the [chars] card in [chars] has been successfully updated from version [chars] to version [int].[int]. Upgrading time = [time-stamp] Explanation The FPD image upgrade process has completed successfully for the specified device. Recommended Action This is an informational message only. No action is required.


571

FPOE_DB Messages

Error Message %FPD_MGMT-6-UPGRADE_RETRY: Attempting to recover from the failed upgrades ... Explanation Because of an image upgrade failure, the system will attempt another upgrade operation

for the same FPD image. Recommended Action This is an informational message only. No action is required.

Error Message %FPD_MGMT-6-UPGRADE_START: [chars] (FPD ID=[int]) image upgrade in progress for [chars] card in [chars]. Updating to version [int].[int]. PLEASE DO NOT INTERRUPT DURING THE UPGRADE PROCESS (estimated upgrade completion time = [time-stamp]) ... Explanation The FPD image upgrade process has started. Do not interrupt the upgrade operation

because any interruption could render the target card unusable. Avoid actions such as removing the target card from the system, powering off the system, or using commands that can power-cycle the target card during the upgrade process. Recommended Action This is an informational message only. No action is required.

Error Message %FPD_MGMT-6-UPGRADE_TIME: Estimated total FPD image upgrade time for [chars] card in [chars] = [time-stamp]. Explanation The estimated total time for all FPD images to be upgraded is displayed for the specified

card. Recommended Action This is an informational message only. No action is required.

FPOE_DB Messages This section contains fabric port of exit (FPOE) messages.

FPOE_DB-4 Error Message FPOE_DB-4-ENTRY_USAGE_ABOVE: FPOE DB entry usage is above [dec]% Explanation FPOE database entry usage went above the warning threshold. Recommended Action If this message recurs, copy the message exactly as it appears on the console



572

FPOE_DB Messages

Error Message FPOE_DB-4-ENTRY_USAGE_BELOW: FPOE DB entry usage is below [dec]% Explanation FPOE database entry usage went below the warning threshold. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message [dec]>

FPOE_DB-4-ENTRY_USAGE_FULL: FPOE DB entry usage is full

FPOE_DB-4-ENTRY_USAGE_NOT_FULL: FPOE DB entry usage is not full [chars] Explanation The router has changed state. Recommended Action No action is required.

HTTP Messages This section contains Hypertext Transfer Protocol (HTTP) messages.


649

HTTP Messages

HTTP-3 Error Message %HTTP-3-INIT_FAIL: HTTP Process Init failed. Explanation Initialization of the HTTP subsystem has failed. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message %HTTP-3-OUTOF_MEM: HTTP out of memory. Explanation An error occurred during initialization of the HTTP process. The HTTP process could

not create crucial internal data structures that are required for operation of the HTTP subsystem. The most likely reason for this condition is an exhaustion of system memory. Recommended Action Reduce other system activity to ease memory demands. if conditions warrant,

upgrade to a larger memory configuration.

Error Message %HTTP-3-PROC_NOCREAT: Unable to create HTTP process. Explanation An error occurred during initialization of the HTTP process. The HTTP process that

processes all HTTP requests and responses could not be created. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message %HTTP-3-SERVER_RESTART_FAILED: Server restart failed. Disabling HTTP server. Explanation TCP process was restarted affecting the HTTP server. Attempts to restart HTTP server

failed. Recommended Action Check status of TCP process. Enable the HTTP server after TCP process has

started.

HTTP-6 Error Message %HTTP-6-SERVER_SETUP_FAILED: Server setup failed Explanation Setup of the HTTP or HTTPS server to listen on the specified port number has failed. Recommended Action Disable the server, verify that port number is correct and enable the server.

Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.


650

HW Messages

HW Messages This section contains hardware messages.

HW-2 Error Message %HW-2-OBSOLETE_HW_VER: Module Version in [chars] is obsolete ********************************************************************* * IMPORTANT !!! * * The module in [chars] is obsolete and must be returned * * via RMA to Cisco Manufacturing. If it is a lab unit, * * it must be returned to Proto Services for upgrade. * ********************************************************************* Explanation The specified hardware is obsolete and needs to be replaced. Recommended Action If this message recurs, copy the message exactly as it appears on the console


HW_API Messages This section contains hardware API messages.

HW_API-3 Error Message %HW_API-3-BACKWALK_REQUEST: Backwalk request failed, [chars] Explanation A request to walk internal data structures has failed. Depending on the criticality of the data, the accuracy of forwarding may be affected. Recommended Action Copy the message exactly as it appears on the console or in the system log.



651

HW_API Messages

Error Message %HW_API-3-BACKWALK_REQUEST_VALUE: Backwalk request failed, [chars] ([hex]) Explanation A request to walk internal data structures has failed. Depending on the criticality of the data, the accuracy of forwarding may be affected. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %HW_API-3-INVALID_CONTEXT: Invalid context [hex] Explanation An internal API error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %HW_API-3-INVALID_OBJ: Invalid object [hex] Explanation An internal API error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



652

HW_API Messages

Error Message %HW_API-3-INVALID_TYPE: Invalid type [dec] Explanation An internal API error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %HW_API-3-INVALID_WALK_SPEC: Invalid walk spec [hex] Explanation An internal API error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %HW_API-3-NO_OBJ_TYPE_LIST_ENTRY: Invalid sw_obj_type ([dec]) used with obj_type_list Explanation An internal API error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



653

HW_API Messages

Error Message %HW_API-3-NO_OBJ_TYPE_LIST_ENTRY2: Invalid sw_obj_link_type ([dec]) used with obj_type_list Explanation An internal API error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %HW_API-3-RESILIENCE_NO_HANDLER: No handlers in place for [chars] sw object creation failure. Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message

%HW_API-3-VECTOR: Failed to set [chars] vector for [chars], [chars]

Explanation An internal API error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



654

HWIF_QOS Messages

Error Message %HW_API-3-WALK_MODE_UNSUPPORTED: Walk mode ’[chars]’ unsupported Explanation An internal API error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


HWIF_QOS Messages This section contains HWIF QoS messages.

Error Message %HWIF_QOS-6-EOM_FORCE_TRUSTED: EoMPLS on [chars] caused install of ’trust cos’ state Explanation If EoMPLS is configured on the interface or any of its subinterfaces, the no trust state

is automatically replaced by trust cos. Recommended Action Remove all EoMPLS configurations from the interface to restore the no trust

state.

Error Message %HWIF_QOS-6-EOM_RESTORE_UNTRUSTED: The ’no trust’ state is restored on EoMPLS removal from [chars] Explanation If EoMPLS is unconfigured on the interface and all its subinterfaces, the configured no

trust state is restored. Recommended Action This is an informational message only. No action is required.

Error Message %HWIF_QOS-6-EOM_TRUST_NOT_INSTALLED: ’no trust’ command is not installed on [chars] in presence of EoMPLS Explanation If EoMPLS is configured on the interface or any of its subinterfaces, the no trust command is not installed. Recommended Action Remove all EoMPLS configurations from the interface.


655

HYPERION Messages

HYPERION Messages This section contains Hyperion ASIC (HYPERION) messages.

HYPERION-3 Error Message %HYPERION-3-FAILURE_INTR_CFG: Failure to setup the Hyperion device interrupts. Explanation The internal ASIC on a line card could not be initialized. The device is not operational

and has been disabled. The data path is not operational. Recommended Action Copy the message exactly as it appears on the console or in the system log.


HYPERION-4 Error Message %HYPERION-4-EARL_BUS_SYNC_ERR: Failed to sync Earl bus, Hyperion version [dec] Explanation The HYPERION ASIC in the line card failed to synchronize with the Earl bus. Recommended Action If traffic recovers, no action is required. Otherwise, copy the message exactly

as it appears on the console or in the system log. Enter the show platform hardware hyperion all command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


656

HYPERION Messages

Error Message %HYPERION-4-HYP_RESET: Hyperion Error Interrupt. Resetting ASIC. Explanation The Hyperion ASIC in the SPA or Enhanced FlexWAN module has received a fatal

error. The ASIC is automatically reset, and the SPA or Enhanced FlexWAN module attempts to continue normal operation. Recommended Action No action is required if traffic recovers. If traffic does not recover, copy the

error message exactly as it appears on the console or in the system log. Enter the show platform hardware hyperion all command to gather data that may help identify the cause of the error. If you cannot determine the cause of the error from the error message text or from the show platform hardware hyperion all output, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %HYPERION-4-HYP_RESET: Hyperion ASIC reset, interrupt [chars] Explanation The Hyperion ASIC in the SPA or Enhanced FlexWAN module has received a fatal

error. The ASIC is automatically reset, and the SPA or Enhanced FlexWAN module attempts to continue normal operation. Recommended Action No action is required if traffic recovers. If traffic does not recover, copy the


Error Message %HYPERION-4-UNEXPECTED_VERSION: Unexpected Hyperion version. Explanation The line card is unable to recognize the version of the Hyperion ASIC. Recommended Action No action is required if traffic passes through the line card. If traffic does not

pass through the line card, check the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl to determine in which version this problem is fixed and upgrade accordingly. If traffic does not pass after the upgrade, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


657

HYPERION Messages

HYPERION-5 Error Message %HYPERION-5-BUS_MODE_CHANGE: The System Switching Bus Mode changed to [chars] mode Explanation The system switching bus interface device mode changed switching bus modes. The

mode is specified in the system message. Recommended Action The supervisor engine instructed the module to change the mode on the

switching bus. No action is required.

Error Message %HYPERION-5-BUS_SEQ_ERR: Constellation bus Sequence Error. Resetting Hyperion ASIC. Explanation The switch processor has detected a sequence error on the backplane bus. A reset

sequence from the EARL has been called to recover from this error. System traffic should recover and continue normally. Recommended Action If traffic recovers, no action is required. If traffic does not recover, copy the


Error Message %HYPERION-5-HYP_INIT_FAILURE: The Hyperion ASIC initialization failed Explanation The Hyperion ASIC initialization was not successful. The Hyperion ASIC is not

operational and is disabled. Recommended Action If traffic recovers, no action is required. If traffic does not recover, copy the



658

HYPERION Messages

Error Message %HYPERION-5-HYP_INTR_INFO: [chars] Explanation This message provides more information about the interrupts from the backplane bus

ASIC to the line card CPU. Recommended Action If traffic recovers, no action is required . Otherwise, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %HYPERION-5-HYP_RESET_INFO: [chars] Explanation This message provides more information about the interrupts leading to the reset of the backplane bus ASIC. Recommended Action If traffic recovers, no action is required . Otherwise, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %HYPERION-5-NULL_HYP_OBJECT: The Hyperion device object pointer is set to NULL Explanation The memory location of the Hyperion ASIC device object is invalid. The Hyperion

ASIC operation is disabled, and the device interrupt is now masked. Recommended Action If traffic recovers, no action is required. If traffic does not recover, copy the



659

ICC Messages

ICC Messages This section contains Inter-Card Communication (ICC) messages.

ICC-3 Error Message %ICC-3-MAST_BAD_FREE: ICC multicast memory already freed Explanation One of the ICC multicast request’s memory was found to be free when response arrived Recommended Action Copy the message exactly as it appears on the console or in the system log.


ICC-4 Error Message %ICC-4-BAD_ACCOUNTING: ICC received a bad class %d Explanation The intercard communication (ICC) process received an invalid class and therefore

cannot account for the message. Recommended Action Copy the message exactly as it appears on the console or in the system log.



660

ICC Messages

ICC-5 Error Message %ICC-5-REQ_WATERMARK: [dec] pkts for class [chars] request [dec] are waiting to be processed Explanation The processor has received packets for the class request and the packets are waiting to

be processed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


ICC-6 Error Message %ICC-6-INFO: [chars] [hex] [hex] [hex] Explanation This message provides ICC subsystem generic information or error information. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ICC-6-MCAST_TIMEOUT: ICC multicast request timed out Explanation One of the ICC multicast request timed out without response. Recommended Action Copy the message exactly as it appears on the console or in the system log.



661

ICC_ISSU_NEGO Messages


ICC_ISSU_NEGO Messages This section contains Inter-Card Communication (ICC) in-service software upgrade (ISSU) negotiation messages.

ICC_ISSU_NEGO-3 Error Message %ICC_ISSU_NEGO-3-CLIENT_EVENT_QUEUE_CREATE: Failed to create ICC nego client queue (client %d, endpoint 0x%x) Explanation The intercard communication (ICC) ISSU negotiation process failed to create a client

watched queue. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ICC_ISSU_NEGO-3-CLIENT_FREE_EVENTS_ALLOCATION: Failed to allocate ICC Nego free events (client %d, endpoint 0x%x) Explanation The ICC negotiation process failed to allocate ICC negotiation free events. Recommended Action Copy the message exactly as it appears on the console or in the system log.



662


Error Message %ICC_ISSU_NEGO-3-CLIENT_FREE_EVENT_ENQUEUE: Failed to enqueue event to free event queue (type %d, client %d, endpoint 0x%x) Explanation The ICC negotiation process failed to enqueue an event to the free event queue. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ICC_ISSU_NEGO-3-CLIENT_FREE_EVENT_QUEUE_CREATE: Failed to create ICC nego client queue (client %d, endpoint 0x%x) Explanation The ICC negotiation process failed to create a client free events queue. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ICC_ISSU_NEGO-3-CLIENT_PROCESS_CREATE: Failed to create ICC nego client process (client %d, endpoint 0x%x) Explanation The ICC negotiation process failed to create a client process. Recommended Action Copy the message exactly as it appears on the console or in the system log.



663


Error Message %ICC_ISSU_NEGO-3-DROPPING_MSG: Dropping message (client %d) Explanation The ICC negotiation process dropped a client message. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ICC_ISSU_NEGO-3-ICC_INIT_SEND: Failed to send the ICC Nego Init message (endpoint 0x%x) Explanation The ICC negotiation process failed to send the negotiation initialization message. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ICC_ISSU_NEGO-3-INCONSISTENT_MEDMAN_DATA: Inconsistent MEDMan data (unique key %d) Explanation The ICC negotiation process Multiple Endpoint Data Manager (MEDMan) data is

inconsistent. Recommended Action Copy the message exactly as it appears on the console or in the system log.



664


Error Message %ICC_ISSU_NEGO-3-INTERNAL_ICC_PAK: Failed to get an ICC pak (internal message %d, size %d Explanation The ICC negotiation process failed to get an ICC packet for an internal message. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ICC_ISSU_NEGO-3-INVALID_CLIENT: Invalid client %d Explanation The ICC negotiation client is invalid. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ICC_ISSU_NEGO-3-INVALID_CLIENT_PID_GENERIC: Invalid client process pid, can’t be the generic process (client %d, endpoint 0x%x, pid %d) Explanation An attempt was made to send a client process message to the ICC negotiation generic

process. Recommended Action Copy the message exactly as it appears on the console or in the system log.



665


Error Message %ICC_ISSU_NEGO-3-INVALID_DS: Invalid ICC Nego data structure Explanation The internal ICC negotiation data structure is invalid. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ICC_ISSU_NEGO-3-INVALID_DS_CLIENT: Invalid ICC Nego data structure (client %d) Explanation The internal ICC negotiation data structure is invalid. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ICC_ISSU_NEGO-3-INVALID_MSG: Invalid message (type %d) Explanation The ICC negotiation message is invalid. Recommended Action Copy the message exactly as it appears on the console or in the system log.



666


Error Message %ICC_ISSU_NEGO-3-INVALID_PCOL_DS: Invalid ICC Nego process collector data structure (client %d, endpoint 0x%x) Explanation The ICC negotiation process collector data structure is invalid. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ICC_ISSU_NEGO-3-INVALID_QUEUE: Invalid ICC Nego client queue (client %d) Explanation The internal ICC negotiation watched queue is invalid. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ICC_ISSU_NEGO-3-INVALID_STATUS: Invalid client negotiation status (client %d, status %s) Explanation The ICC negotiation client negotiation status is invalid. Recommended Action Copy the message exactly as it appears on the console or in the system log.



667


Error Message %ICC_ISSU_NEGO-3-MEDMAN_DS_CREATION: Failed to create the client data structure in MEDMan (client %d, endpoint 0x%x, error %s) Explanation The ICC negotiation process could not create the client data structure in the Multiple Endpoint Data Manager (MEDMan). Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ICC_ISSU_NEGO-3-MEDMAN_REGISTRATION: Failed to register with MEDMan Explanation The ICC negotiation process failed to register with the Multiple Endpoint Data Manager

(MEDMan). Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ICC_ISSU_NEGO-3-MSG_ENQUEUING: Failed to enqueue msg to the ICC Nego generic process (client %d) Explanation The ICC negotiation process failed to enqueue a process message to the ICC negotiation

generic process. Recommended Action Copy the message exactly as it appears on the console or in the system log.



668


Error Message %ICC_ISSU_NEGO-3-MSG_ENQUEUING_CLIENT: Failed to enqueue msg to the ICC Nego generic process (client %d, e_id 0x%x, type %d) Explanation The ICC negotiation process failed to enqueue a process message to an ICC negotiation

client process. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ICC_ISSU_NEGO-3-NEGO_CANNOT_COMPLETE: Negotiation cannot complete (endpoint 0x%x) Explanation The ICC negotiation cannot complete. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ICC_ISSU_NEGO-3-NOTIFY_CLIENT: Failed to notify client %d (e_id 0x%x) Explanation The ICC negotiation process failed to notify a client. Recommended Action Copy the message exactly as it appears on the console or in the system log.



669


Error Message %ICC_ISSU_NEGO-3-NO_FREE_EVENT: Couldn’t get a free event (type %d, client %d, e_id 0x%x) Explanation The ICC negotiation process failed to get a free event for a client. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ICC_ISSU_NEGO-3-NO_INTERNAL_CB: No callback for internal message %d Explanation No ICC negotiation callback has been defined for this internal message. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ICC_ISSU_NEGO-3-NO_QUEUE: Couldn’t get an event queue (type %d, client %d, e_id 0x%x) Explanation The ICC negotiation process failed to get an event queue for a client. Recommended Action Copy the message exactly as it appears on the console or in the system log.



670


Error Message %ICC_ISSU_NEGO-3-NO_UK: Couldn’t retreive the unique key Explanation The ICC negotiation process failed to retrieve the unique key for a client endpoint pair. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ICC_ISSU_NEGO-3-NVI_EMPTY_MSG: Received an empty NVI ICC message Explanation The ICC negotiation process received an empty NVI ICC message. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ICC_ISSU_NEGO-3-NVI_ICC_SEND: Failed to send the ICC Nego NVI ICC message (endpoint 0x%x) Explanation The ICC negotiation process failed to send the NVI ICC message. Recommended Action Copy the message exactly as it appears on the console or in the system log.



671


Error Message %ICC_ISSU_NEGO-3-NVI_REQ_PAK: Failed to get an ICC req pak for the ICC Nego NVI message Explanation The ICC negotiation process failed to get an ICC request packet for the NVI internal

message. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ICC_ISSU_NEGO-3-NVI_RESP_PAK: Failed to get an ICC resp pak for the ICC Nego NVI message Explanation The ICC negotiation process failed to get an ICC response packet for the NVI internal

message. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ICC_ISSU_NEGO-3-OPEN_PORT_RELIABLE: Can’t open reliable port (endpoint 0x%x, client %s - %d) Explanation The ICC negotiation process cannot open a reliable port to the endpoint for the ISSU

client. The ISSU client might not be able to negotiate. Recommended Action Copy the message exactly as it appears on the console or in the system log.



672


Error Message %ICC_ISSU_NEGO-3-OPEN_PORT_UNRELIABLE: Can’t open unreliable port (endpoint 0x%x, client %d) Explanation The ICC negotiation process cannot open an unreliable port to the endpoint for the ISSU

client. The ISSU client might not be able to negotiate. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ICC_ISSU_NEGO-3-OUT_OF_MEMORY: System is running out of memory Explanation There is not enough available memory in the system. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ICC_ISSU_NEGO-3-PCOL_INCONSISTENT_PID: Inconsistent ICC Nego process collector process id (client %d, endpoint 0x%x) Explanation The ICC negotiation process collector process ID is inconsistent. Recommended Action Copy the message exactly as it appears on the console or in the system log.



673


Error Message %ICC_ISSU_NEGO-3-PROCESS_CREATE: Failed to create ICC nego process Explanation The ICC negotiation failed to create a process to handle the messages. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ICC_ISSU_NEGO-3-PROCESS_KILL_INTERNAL: Internal process kill failed (pid %d, process collector pid %d) Explanation The ICC negotiation process failed to terminate an internal process due to an

inconsistent process ID. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ICC_ISSU_NEGO-3-PROC_LEVEL_MSG_GENERIC: Invalid process level message in the generic process (client %d, level %d) Explanation The level of messages for the ICC negotiation process is invalid in the generic process. Recommended Action Copy the message exactly as it appears on the console or in the system log.



674


Error Message %ICC_ISSU_NEGO-3-PROC_LEVEL_MSG_INTERRUPT: Invalid process level message in the ICC interrupt (client %d, level %d) Explanation The level of messages for the ICC negotiation process is invalid in the ICC interrupt. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ICC_ISSU_NEGO-3-SEND_UK: Failed to send unique key to process (client %d, endpoint 0x%x Explanation The ICC negotiation process failed to send the unique key to the new client process. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ICC_ISSU_NEGO-3-TIMER_NOT_AWAKE: ICC Nego pcol timer was not awake when getting a timer event Explanation The ICC negotiation process collector timer was not awake when receiving a timer

event. Recommended Action Copy the message exactly as it appears on the console or in the system log.



675

ICC_ISSU_TAGGING Messages

Error Message %ICC_ISSU_NEGO-3-TIMER_NOT_RUNNING: ICC Nego pcol timer was not running when getting a timer event Explanation The ICC negotiation process collector timer was not running when getting a timer event. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ICC_ISSU_NEGO-3-WATCHED_QUEUE_CREATION: Failed to create the watched queue Explanation The ICC negotiation process could not create the watched queue. Recommended Action Copy the message exactly as it appears on the console or in the system log.


ICC_ISSU_TAGGING Messages This section contains Inter-Card Communication (ICC) in-service software upgrade (ISSU) tagging messages.

ICC_ISSU_TAGGING-3 Error Message %ICC_ISSU_TAGGING-3-NOT_XFORM: Untransformed message detected (class:%d, request:%d, sender:%x) Explanation During runtime, the intercard communication (ICC) ISSU tagging process detected an untransformed ICC message. This message must be transformed or suspended to support ISSU. Recommended Action Copy the message exactly as it appears on the console or in the system log.



676

IDBINDEX_SYNC Messages


IDBINDEX_SYNC Messages This section contains Interface Descriptor Block (IDB) index synchronizationmessages.

IDBINDEX_SYNC-3 Error Message %IDBINDEX_SYNC-3-IDBINDEX_ASSIGN: Failed to assign an index to IDB type %d, for interface Explanation An interface index cannot be allocated for this interface due to an internal software error. This is an unrecoverable error that results in this interface not being usable for traffic. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %IDBINDEX_SYNC-3-IDBINDEX_ENTRY_MISMATCH: An interface index mismatched its active table entry: Explanation An interface index was found which did not match the active interface descriptor block

(IDB) index table entry with the corresponding synchronization key. This condition is due to an internal software error. Recommended Action Copy the message exactly as it appears on the console or in the system log.



677


Error Message %IDBINDEX_SYNC-3-IDBINDEX_LINK: Driver for IDB type ’%d’ changed the Identity of interface Explanation The interface index table cannot be updated with the new identity provided for this

interface due to an internal software error. The driver might not have deleted the old identity first, or the driver might have accidentally changed the identity. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %IDBINDEX_SYNC-3-IDBINDEX_RETRIEVE: Cannot retrieve if-index for this interface: Explanation The interface index number was not found in the interface index table for the interface

specified in the error message. This condition might have been caused by the interface index number not being properly synchronized by the primary processor card. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %IDBINDEX_SYNC-3-INIT_ERR: %s Explanation The interface index synchronization ISSU client has an initialization error. Recommended Action Copy the message exactly as it appears on the console or in the system log.



678


Error Message %IDBINDEX_SYNC-3-IPC_ERR: %s: %s. Explanation The interface index synchronization interprocess communication (IPC) session has an

error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %IDBINDEX_SYNC-3-ISSU_ERR: %s%s, rc=%d Explanation The interface index synchronization ISSU client has an error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %IDBINDEX_SYNC-3-RF_ERR: %s %d. Explanation An error occurred in the interface index synchronization of the redundancy facility (RF)

client. Recommended Action Copy the message exactly as it appears on the console or in the system log.



679


Error Message %IDBINDEX_SYNC-3-TRANSFORM: Require IF-Index ISSU transformation function %s %s Explanation The interface index synchronization process has identified a missing ISSU

transformation function. This condition may lead to misoperation. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %IDBINDEX_SYNC-3-VALIDATE: Cannot validate if-index for this interface: Explanation The identity of this interface could not be validated against the stored identity within

the interface descriptor block (IDB) index table. This condition probably occurred due to the identity of the IDB changing without first explicitly unlinking the previous identity. Recommended Action Copy the message exactly as it appears on the console or in the system log.


IDBINDEX_SYNC-4 Error Message %IDBINDEX_SYNC-4-RESERVE: Failed to lookup existing ifindex for an interface on the Standby, allocating a new ifindex from the Active (ifindex=%d, idbtype=%s) Explanation A lookup failure occurred for an interface on the standby unit. An attempt was made to resolve the issue by reserving a new interface index on the active unit. If this failure was caused by a defect in the key encoding, then traffic may stop on this interface if the system switches over. Recommended Action Copy the message exactly as it appears on the console or in the system log.



680

IDBINDEX_SYNC_KEY Messages


Error Message %IDBINDEX_SYNC-4-TRUNCATE: Overflow in %s when encoding interface sync key, got %d maximum is %d Explanation During the creation of a unique synchronization key to represent an interface, one of the

attributes making up the key was truncated to fit in the allocated space in the key. This condition might lead to overlapping key allocations, which would cause an error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


IDBINDEX_SYNC_KEY Messages This section contains Interface Descriptor Block (IDB) key synchronizationmessages.

IDBINDEX_SYNC_KEY-3 Error Message %IDBINDEX_SYNC_KEY-3-UNKNOWN_TYPE: Interface type is unknown and cannot be synced: Explanation An internal software error has occurred related to the interface descriptor block (IDB)

key synchronization. Recommended Action Copy the message exactly as it appears on the console or in the system log.



681

IDBMAN Messages

IDBMAN Messages This section contains Interface Descriptor Block Manager (IDBMAN) messages.

IDBMAN-4 Error Message %IDBMAN-4-CONFIG_WRITE_FAIL: FFailed to generate configuration for interface [chars] Explanation The system failed to generate a configuration for the specified interface because of a

problem with the file system. The active and standby supervisor engines will have configurations that do not match. Recommended Action The standby supervisor engine is reloaded automatically to recover from the problem. If the standby supervisor engine does not recover, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %IDBMAN-4-IDB_LIMIT: Maxinum interface count reached the limit of [dec]([dec]+[dec]). Module is disabled. Explanation The number of interfaces has reached the maximum limit and the module has been

disabled. Recommended Action Copy the message exactly as it appears on the console or in the system log.



682

IDMGR Messages

IDMGR Messages This section contains ID manager messages.

Error Message %IDMGR-3-INVALID_ID_TABLE_SIZE: bad new ID table size Explanation A bad new table request to ID manager has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


IF Messages This section contains interface messages.

IF-2 Error Message %IF-2-IDB_TABLE_INIT: Malloc failed while initializing idb table Explanation A memory allocation failure occurred while an IDB table was being initialized. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

IF-3 Error Message %IF-3-BADMACADDRTYPE: illegal mac address type, [dec] Explanation This is an internal error that was recovered gracefully. Recommended Action Copy the message exactly as it appears on the console or in the system log.



683

IFDAMP Messages


IF-4 Error Message %IF-4-BACKWARD_COUNTERS: Corrected for backward [chars] counters ([int] -> [int]) on [chars] Explanation The interface specified in the message has a packet counter that has decreased in

number. This condition can occur if a packet is counted and then dropped. This event was detected and corrected. Recommended Action If this condition persists, copy the message exactly as it appears on the console


Error Message %IF-4-NOBGPROCESS: Network background process not running. [chars] Explanation A process which manages network interface background processing is not yet running, but another system process has tried to send the process a message. An interface on the router may have missed a request to bring itself up. Recommended Action Reset the interface by entering a shutdown command followed by a no shutdown command.

IFDAMP Messages This section contains interface dampening (IFDAMP) messages.

IFDAMP-5 Error Message %IFDAMP-5-ZERODELAY: dampening reuse timer is updated with 0 delay time Explanation An inconsistency was detected in the dampening reuse timer wheel. Recommended Action No action is required.


684

IFMGR Messages

IFMGR Messages This section contains interface manager messages.

IFMGR-3 Error Message %IFMGR-3-BADIFINDEXTABLE: The file nvram:ifIndex-table is corrupt. Explanation The file is not in the expected format. Recommended Action If possible, delete the file. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %IFMGR-3-DUP_IFINDEX: Duplicate ifIndex (%d) found for ifDescr Explanation Two interfaces have the same interface index in the interface manager assigned list. The

second interface registered with the interface manager will be assigned a new index. Recommended Action If interface index persistence is not required, then no action is required. Otherwise, reload the router with the proper interface index table and image. If the error message only appears from the standby route processor (RP), reload the standby RP.

Error Message %IFMGR-3-IFDB: IF manager interface database [chars] failure- [dec] Explanation An internal software error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



685

IFMGR Messages

Error Message %IFMGR-3-IFINDEX_PERSIST_ENTRY_CORRUPT: [chars] seems to be corrupted. Trying to read [dec] size Explanation The ifIndex table is corrupted. Recommended Action Delete the ifindex table.

Error Message %IFMGR-3-INVALID_PERSISTENT_DATA: Invalid persistent data Explanation An attempt was made to write invalid persistent data. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %IFMGR-3-NOIMACP: IF manager control process failed to start Explanation An internal software error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %IFMGR-3-NOVECTOR: Interface manager failed to allocate IF vector. size %d Explanation The interface vector could not be allocated with the number of elements required, either

initially or by a resize operation. Recommended Action Copy the message exactly as it appears on the console or in the system log.



686

IFMGR Messages


Error Message %IFMGR-3-VECTOREXD: IF manager attempted to use interface [dec] outside vector range. Explanation An internal software error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %IFMGR-3-VECTORIFSUSPECT: IF manager added interface %d which is unexpectedly large. Explanation The ifIndex allocation scheme is trying to add an ifIndex value much larger than the

former greatest ifIndex value in the DB. It should assign sequential ifIndex values. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %IFMGR-3-VECTORPOSUSED: IF manager attempted to add interface [dec] which was already added. Explanation An internal software error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



687

IFMGR Messages


IFMGR-4 Error Message %IFMGR-4-NOIFINDEX: All SNMP if indices are exhausted Explanation All SNMP MIB indexes have been exhausted. Interfaces will not be able to obtain an

interface index that they can use to register with the interface MIB. Recommended Action Attempt a system reload. If the problem persists after the system reload, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %IFMGR-4-NOSYNC: ifIndex not being synced between active and standby Explanation When the standby module comes up, the tuple of ifIndex and ifDescr is synchronized so

that interfaces get the same ifIndex when they come up. This error happens when the interface does not get the ifIndex for the given ifDescr. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %IFMGR-4-STACK_RELATIONSHIP_ADD_ERROR: [chars]: Request for creating invalid stack relationship [dec], [dec] Explanation The IF MGR received the call to add invalid stack relationship. The higher and lower

ifIndex are shown in the message. The module of the IF MGR from which this message is generated is also shown in the message. Recommended Action Copy the message exactly as it appears on the console or in the system log.



688

IFMGR Messages


Error Message %IFMGR-4-VECTORIFSUSPECT: IF manager added interface [dec] which is unexpectedly large. Explanation The ifIndex allocation scheme gives out sequential ifIndex values. This message comes

from the IF-MGR DB when it is trying to add an ifIndex value much larger than the former greatest ifIndex value in the DB. Recommended Action Copy the message exactly as it appears on the console or in the system log.


IFMGR-7 Error Message %IFMGR-7-NO_IFINDEX_FILE: Unable to open [chars] [chars] Explanation This is a informational message. This means system found no saved ifIndex

information, and ifIndex is not persisted across reboots. The ifIndices will be reassigned. Recommended Action 1. No Action, if ’snmp-server ifIndex persist’ is not configured. 2. If

’snmp-server ifindex persist’ is configured then copy the error message exactly as it appears, and report it to your technical support representative.


689

IFS Messages

IFS Messages This section contains Cisco IOS file system messages.

Error Message %IFS-3-FS_STRUCT_ERROR: Data does not match expected internal representation Explanation A mismatch exists between the representation of data extracted from the file system and

the expectation of its formatting. This condition may occur when running in a dual-RP environment, with different Cisco IOS versions running on the two RPs. Recommended Action Ensure that both RPs are running the same Cisco IOS version, if running in a

dual-RP environment. If not, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

IGMP Messages This section contains Internet Group Management Protocol (IGMP) messages.

IGMP-3 Error Message %IGMP-3-NO_DNS_SERVER: No DNS server is configured. DNS-based SSM mapping should be disabled if no DNS server is configured. Explanation No domain name service (DNS) server is present. Processing of Internet Group

Management Protocol (IGMP) packets may be delayed if the DNS lookup is done continuously. Recommended Action Disable DNS-based source specific multicast (SSM) mapping if no DNS server

is present in the network.

Error Message %IGMP-3-QUERY_INT_MISMATCH: Received a non-matching query interval %d, from querier address %i Explanation An IGMP version mismatch was detected between routers. Recommended Action Configure both interfaces with the same IGMP version.


690

ILPOWER Messages

IIGMP-6 Error Message %IGMP-6-IGMP_CHANNEL_LIMIT: IGMP limit exceeded for channel (%i, %i) on %s by host %i Explanation The allowed number of IGMP joiners reached the configured limit. New joiners cannot

be allowed unless the configuration is changed. Recommended Action Enter the global or interface ip igmp limit command to adjust the allowed

number of IGMP joiners. If the exceeding of current limits was unexpected, find the IP address of the denied host in the system log.

Error Message %IGMP-6-IGMP_GROUP_LIMIT: IGMP limit exceeded for group (*, %i) on %s by host %i Explanation The allowed number of IGMP joiners has exceeded the configured limit. New joiners

cannot be allowed unless the configuration is changed. Recommended Action Enter the global or interface ip igmp limit command to adjust the allowed

number of IGMP joiners. If the exceeding of current limits was unexpected, find the IP address of the denied host in the system log.

ILPOWER Messages This section contains inline power messages.

ILPOWER-3 Error Message %ILPOWER-3-CONTROLLER_ERR: Controller error, Controller number [dec]: [chars] Explanation An error involving the inline power controller has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



691

ILPOWER Messages

Error Message %ILPOWER-3-CONTROLLER_IF_ERR: Controller interface error, [chars]: [chars] Explanation An interface error has been detected between the inline power controller and the system. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ILPOWER-3-CONTROLLER_PORT_ERR: Controller port error, Interface [chars]: [chars] Explanation A port error has been reported by the inline power controller. Recommended Action Copy the message exactly as it appears on the console or in the system log.


ILPOWER-5 Error Message %ILPOWER-5-AC_DISCONNECT: Interface [chars]: AC disconnect Explanation The AC power has been disconnected. Recommended Action No action is required.

Error Message %ILPOWER-5-DC_DISCONNECT: Interface [chars]: DC disconnect Explanation The DC power has been disconnected. Recommended Action No action is required.


692

ILPOWER Messages

Error Message %ILPOWER-5-ILPOWER_MISCONFIG: Interface [chars] is denied power as it requires more power than configured maximum wattage([dec]). Explanation The interface is denied power as it requires more power than the configured maximum

wattage. Recommended Action No action is required.

Error Message %ILPOWER-5-ILPOWER_NOPOWER_AVAIL: Interface [chars] is denied power because either the system ran out of power or module limit reached. Explanation There is not enough power left in the system to supply to the interface specified in the

error message. Recommended Action No action is required.

Error Message %ILPOWER-5-ILPOWER_POWEROVERDRAWN: Interface [chars] is shutdown as it is consuming more power ([dec]) than the configured maximum value ([dec]). Explanation The specified interface is shut down because it is consuming more power than the

configured maximum value. Recommended Action No action is required.

Error Message %ILPOWER-5-LINKDOWN_DISCONNECT: Interface [chars]: Link down disconnect Explanation A link has been disconnected. Recommended Action No action is required.

Error Message %ILPOWER-5-POWER_GRANTED: Interface [chars]: Power granted Explanation Power has been granted for the interface specified. Recommended Action No action is required.

ILPOWER-7 Error Message %ILPOWER-7-DETECT: Interface [chars]: Power Device detected: [chars] Explanation A power device has been detected. Recommended Action No action is required.


693

ILPOWER_RF Messages

ILPOWER_RF Messages This section contains inline power redundancy facility (RF) messages.

ILPOWER_RF-3 Error Message %ILPOWER_RF-3-CREATE_PROCESS: Inline power RF client failed to create %s process Explanation The inline power redundancy facility (RF) client could not create a process. This

condition will cause bulk synchronization to fail. Recommended Action Copy the message exactly as it appears on the console or in the system log.


IMAGEMGR Messages This section contains image manager messages.

IMAGEMGR-6 Error Message %IMAGEMGR-6-AUTO_ADVISE_SW: [chars] Explanation A line of output from the auto-advise-software process is being displayed. Recommended Action No action is required.

Error Message %IMAGEMGR-6-AUTO_ADVISE_SW_INITIATED: Auto-advise-software process initiated for switch number(s) [chars] Explanation Systems with incompatible software have been detected in the stack. The stack will now

determine whether or not software is available to be copied to the incompatible systems, and if so, advise the user how to copy it. Otherwise, the system lets the user know that the software on the stack needs to be updated. Recommended Action No action is required.


694

IMAGE_SIMFS Messages

Error Message %IMAGEMGR-6-AUTO_COPY_SW: [chars] Explanation A line of output from the auto-copy-software process is being displayed. Recommended Action No action is required.

Error Message %IMAGEMGR-6-AUTO_COPY_SW_INITIATED: Auto-copy-software process initiated for switch number(s) [chars] Explanation Systems with incompatible software have been detected in the stack. The stack

determines whether or not software is available to be copied to the incompatible systems, and whether or not it is appropriate to copy the software automatically. Recommended Action No action is required.

Error Message %IMAGEMGR-6-AUTO_DOWNLOAD_SW: [chars] Explanation A line of output from the automatic software download process is being displayed. Recommended Action No action is required.

Error Message %IMAGEMGR-6-AUTO_DOWNLOAD_SW_INITIATED: Auto-download-software process initiated for switch number(s) [chars] Explanation Systems with incompatible software have been detected in the stack. The stack attempts

to download software from a previously configured location, and install it to make the systems compatible. Recommended Action No action is required.

IMAGE_SIMFS Messages This section contains In-Memory System Image File System messages.

Error Message %IMAGE_SIMFS-3-NOPROCESS: Failure spawning Memory Reclaim process Explanation The creation of an Cisco IOS process to compact memory previously held by in-memory

image files has failed, probably due to a software defect. Recommended Action Copy the message exactly as it appears on the console or in the system log.



695

IMAGE_VFS Messages

IMAGE_VFS Messages This section contains Image Virtual File System messages.

Error Message %IMAGE_VFS-3-CHECKSUM_FAIL: [chars] image checksum mismatch. Explanation The checksum of the image in memory is different from the expected checksum. Recommended Action Verify that the image file is complete and uncorrupted.

Error Message %IMAGE_VFS-3-LOAD_FAIL: Failed to locate all the Image files,on bootup Explanation The relevant image file is missing or it could not be extracted (due to corruption), or the

router has insufficient memory to load the entire image Recommended Action Copy the message exactly as it appears on the console or in the system log. If

the TAR file is part of a system image, enter the show image contents file archive-name, where archive-name is the name of the archive. Enter the show region and show version commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %IMAGE_VFS-3-LOCATE_FAIL: Failed to open [chars], which was loaded from archive [chars] Explanation The relevant image file is missing or it could not be extracted (due to corruption), or the

archive itself is missing (in the case of flash-based access). Recommended Action Copy the message exactly as it appears on the console or in the system log. If

the file is not in memory, check the archive file. If the file is a TAR archive file and not part of a system software image, enter the archive tar table archive-name command, where archive-name is the name of the TAR archive. If the TAR file is part of a system image, enter the show image contents file archive-name, where archive-name is the name of the archive. Enter the the dir all and show version commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


696

INBAND Messages

Error Message %IMAGE_VFS-3-NOPROCESS: Failure spawning No Cache process Explanation The creation of a Cisco IOS process to delete in-memory image files has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %IMAGE_VFS-3-VERIFY_FAIL: archive verification failed for file [chars] & archive [chars]. Explanation The archive in the local device is different from the version whose image file has been loaded into memory. This condition can happen if the archive was deleted from the local device or replaced by another file of the same name. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Check whether the archive file is complete and uncorrupted. Also check if the size of the archive and the last modification time (if available) is what you expect it to be. Enter the dir all and show version commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

INBAND Messages This section contains inband management messages.

Error Message %INBAND-3-BAD_PAK: Possibly un-encapsulated packet passed to Mistral: int [chars] type [int] stat [hex] flags [hex] size [dec] offset [dec] requeue_token [int] r1 [int] r2 [int] total detected [int] Explanation There is a badly encapsulated packet from the process level. Recommended Action Copy the message exactly as it appears on the console or in the system log.



697

INBAND Messages


Error Message %INBAND-3-INVALID_SEND: Invalid send operation (packet on [chars]) Explanation An internal error caused illegal call to device driver: normal operation continues. Recommended Action If this message recurs, copy the error message exactly as it appears on the


Error Message %INBAND-3-NO_BUFFER_POOLS: Initialization of private buffer pools failed Explanation Private buffer pools were not created for etsec ibc. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %INBAND-3-TOOBIG: An attempt made to send giant packet on [chars] ([dec] bytes from [hex], max allowed [dec]) Explanation An attempt was made to send an oversized packet. Recommended Action Copy the error message exactly as it appears on the console or in the system



698

INTERFACE_API Messages

INTERFACE_API Messages This section contains binary API for the interface descriptor block messages.

INTERFACE_API-1 Error Message %INTERFACE_API-1-NOMOREHWIDBNUMBERS: No more hardware IDB numbers can be issued. The maximum allowed numbers, [dec], has been reached for this platform. Explanation No more hardware IDB numbers can be issued. The maximum allowed number has been

reached for this platform. Recommended Action In addition to the following, copy the information from the show idb command

output. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %INTERFACE_API-1-NOMORESWIDBNUMBERS: No more software IDB numbers can be issued. The maximum allowed numbers, [dec], has been reached for this platform. Explanation No more software IDB numbers can be issued. The maximum allowed number has been

reached for this platform. Recommended Action In addition to the following, copy the information from the show idb command

output. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


699


INTERFACE_API-3 Error Message %INTERFACE_API-3-CANNOTGETMTU: Error [dec] received while getting MTU: [chars]. Using default [int] Explanation A software error has occurred while attempting to retrieve the MTU value from the

interface. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %INTERFACE_API-3-IFNUMTOIDBERROR: Error occurred while using the ifnum to idb table for interface [chars], if number [dec], during [chars] Explanation A software error has occurred. An operation on the interface number to the IDB

mapping table could not be performed successfully. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %INTERFACE_API-3-INVALIDSUBBLOCKPARAMETERS: Invalid subblock parameters for [chars] were supplied. Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



700


Error Message %INTERFACE_API-3-NOADDSUBBLOCK: The [chars] subblock named [chars] was not added to [chars] Explanation A software error has occurred. IDB subblocks could not be added. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %INTERFACE_API-3-SUBNUMDBERR: subnum [hex] error in [chars] Explanation A software error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


INTERFACE_API-4 Error Message %INTERFACE_API-4-TBLERROR: A error occurred while using the Index Table utility for [chars]. Explanation A software error has occurred. This message is displayed when an index table feature

could not be used successfully. Recommended Action Copy the message exactly as it appears on the console or in the system log.



701

INTR_MGR Messages

INTR_MGR Messages This section contains interrupt manager messages.

Error Message %INTR_MGR-3-BURST: [chars] [chars] [[dec]] Explanation A burst of hardware interrupts of the specified type has occurred. Recommended Action The message text on the console or in the system log provides more

information on the specific cause of the error. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %INTR_MGR-3-INTR: [chars] [chars] Explanation The specified interrupt event has been detected. Recommended Action The message text on the console or in the system log provides more

information on the specific cause of the error. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %INTR_MGR-3-MAXBURST: [chars] [chars] [[dec]] Explanation The specified hardware interrupt has exceeded the maximum allowed number of bursts. Recommended Action The message text on the console or in the system log provides more

information on the specific cause of the error. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support


702

IP Messages

representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. Recommended Action Copy the message exactly as it appears on the console or in the system log.


IP Messages This section contains Internet Protocol (IP) messages.

IP-3 Error Message %IP-3-LOOPPAK: Looping packet detected and dropped src=[IP_address], dst=[IP_address],hl=[int], tl=[int], prot=[int], port=[int], dport=[int] in=[chars], nexthop=[IP_address], out=[chars] options=[chars] Explanation A looping packet was detected. A common cause is a misconfiguration of an IP helper

address. The helper address should be the same address as that of the server of the intended service. Putting the address of the router in the helper address causes a routing loop to be created. Recommended Action To resolve this issue, analyze the source and destination address of the looped packets. Verify that the configuration of IP helper addresses in the switch correctly point to the right device (for example the DHCP server, the DNS server, or WINS server).

Error Message %IP-3-MAXIRDP: Attempt to send IRDP to proxies exceeding configurable limit: [dec], interface: [chars], secondary = [dec], proxy = [dec] Explanation The sum of configured secondary addresses and configured proxy addresses exceeds the

number of total addresses that the IRDP can support in its implementation. Recommended Action Reduce the number of either the secondary IP addresses or proxy addresses

configured for the interface.


703

IP Messages

Error Message %IP-3-NOOUTINTF: Output interface not available. source address: [IP_address], destination address: [IP_address], routing type: [int] Explanation The output interface for this packet is not set. Recommended Action Copy the message exactly as it appears on the console or in the system log.


IP-4 Error Message %IP-4-DUPADDR: Duplicate address %i on %s, sourced by %e Explanation Another system is using your IP address. Recommended Action Change the IP address of one of the two systems.

IP-5 Error Message %IP-5-TURBOACL: [chars] Explanation An error occurred while the TurboACL feature was being initialized. Recommended Action Copy the message exactly as it appears on the console or in the system log.



704

IPACCESS Messages

IP-6 Error Message %IP-6-L2MCASTDROP: Layer 2 Multicast packet detected and dropped, src=[IP_address], dst=[IP_address] Explanation Layer 2 Multicast packet with Layer3 Unicast Destination was dropped. Recommended Action No action is required.

Error Message %IP-6-PHYBCASTDROP: Physical broadcast packet detected and dropped, src=[IP_address], dst=[IP_address] Explanation Layer 2 Broadcast packet with Layer3 Unicast Destination was dropped. Recommended Action No action is required.

IPACCESS Messages This section contains IP security messages.

IPACCESS-4 Error Message %IPACCESS-4-INVALIDACL: Invalid ACL field: [chars] is [dec] Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



705

IPC Messages

IPC Messages This section contains InterProcessor Communication (IPC) messages.

IPC-2 Error Message %IPC-2-INVALIDZONE: The IPC Zone is invalid. zone=[hex] Explanation The zone ID entry is not in the zone table. Recommended Action Copy the message exactly as it appears on the console or in the system log.


IPC-3 Error Message %IPC-3-INVALID_PORT_INFO: Invalid port_info in the retry queue message - SRC_PORT = [hex], DEST_PORT = [hex], MSG_TYPE = [hex] Explanation The IPC protocol subsystem detected that the port information is inconsistent. The port

information is probably already freed by the application. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show tech ipc command from the master and the slave, to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


706

IPC Messages

Error Message %IPC-3-ISSU_API_ERR: [chars] failed with error code [dec] Explanation An ISSU API could not perform an operation for the IPC layer. The message text

includes the error code from ISSU library. Recommended Action Enter the show issu client command. Copy the message exactly as it appears


Error Message %IPC-3-ISSU_ERROR: [chars] failed with error code [dec] for seat [hex] Explanation An ISSU API could not perform an operation for the IPC layer. The message text

includes the error code from ISSU library. Recommended Action Enter the show issu fsm command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

IPC-4 Error Message %IPC-4-MSGMAXTIMEOUT: Invalid maximum timeout value [dec] seconds; Period - [dec]; Retries - [dec] Explanation The maximum message timeout for an IPC message exceeds 2 minutes. Recommended Action Enter the show version command. Copy the message exactly as it appears on



707

IPC Messages

Error Message %IPC-4-NOPORT: Port Not Found. [hex] --> [hex], Index:[hex], Seq: [dec], flags: [hex], size: [dec] Explanation IPC received a message which is destined for a port that cannot be found by IPC. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show ipc status, show ipc ports, and debug ipc errors commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

IPC-5 Error Message %IPC-5-INVALIDINPUT: [chars] Explanation An IPC API was called with an invalid argument. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %IPC-5-NULLBPHANDLER: Passed Null backpressure handler Explanation IPC cannot register the application’s null function in the IPC backpressure handler list. Recommended Action Copy the message exactly as it appears on the console or in the system log.



708

IPC Messages

Error Message %IPC-5-QFULL: Q=[hex] [chars] [dec] Explanation The IPC queue is full. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %IPC-5-WATERMARK:[dec] messages pending in [hex] for the port [chars] [hex].[hex] Explanation A particular IPC port is overused. An application is not draining packets quickly, which

suggests that the CPU might be busy. [dec] is the number of messages pending in the IPC to be processed by the application. [chars] is the IPC port name. The first [hex] is the IPC port number, the second [hex] is the IPC seat number, and the third [hex] is the IPC index. Recommended Action Reduce the traffic on this port to a minimal level. If the error message recurs,

upgrade the system software to a release containing a fix for Cisco bug ID CSCdw74873 (watermark messages appear continuously with no traffic).

IPC-6 Error Message %IPC-6-MAXRPCTIMEOUT: Maximum RPC timeout value [dec] seconds set for port [hex] Explanation The maximum RPC timeout for an IPC message exceeds the maximum expected value

of 10 minutes. Recommended Action Enter the show techsupport ipc command. Copy the message exactly as it



709

IP_DEVICE_TRACKING Messages

Error Message %IPC-6-STATEFUL: %s Explanation A stateful interprocess communication (IPC) event occurred. Recommended Action No action is required.

IP_DEVICE_TRACKING Messages This section contains switch IP host tracking HA (IP_DEVICE_TRACKING) messages.

IP_DEVICE_TRACKING-4 Error Message %IP_DEVICE_TRACKING-4-TABLE_LOCK_FAILED: Table already locked by process-id [dec]([chars]) Explanation The IP device tracking table could not be updated because of another process holds a

lock on the table. Recommended Action No action is required.

Error Message %IP_DEVICE_TRACKING_HA-4-ENTRY_OUT_OF_SYNC: Host mac-address [enet] ip-address [IP_address] interface [chars] Explanation An inconsistency has been detected between the active supervisor engine IP device

tracking table and the standby supervisor engine IP device tracking table for this host. Recommended Action No action is required.

IPFAST Messages This section contains IP fast-switching (IPFAST) messages.

IPFAST-2 Error Message %IPFAST-2-FAILOPENIPCPORT: Could not open the IPC ports. [chars] Explanation The IPFAST process could not open the IPC port to communicate to the line card or route processor. Recommended Action Copy the message exactly as it appears on the console or in the system log.



710

IPFAST Messages


Error Message %IPFAST-2-FASTPORTCREATEERR: Attempt to create [chars] failed after [dec] retries (last error:[chars]) Explanation The line card attempted to create a port to the route processor but has failed after a few

retries. This condition might result in the CEF becoming disabled on the line card. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %IPFAST-2-FASTPORTOPEN: Requested to open [chars], id [int] when already open. Attempting to re-open. Explanation The line card is attempting to open a port to the route processor when one is already

open. This behavior could be transient but might result in multiple ports opened for the same purpose. Recommended Action The router should be able to recover from this situation. If CEF problems

develop for this line card, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %IPFAST-2-FASTPORTOPENERR: Attempt to open [chars] failed after [dec] retries (last error:[chars]) Explanation The line card attempted to open a port to the route processor but has failed after a few




711

IPFAST Messages


Error Message %IPFAST-2-FASTPORTREGISTERERR: Attempt to register [chars] failed after [dec] retries (last error:[chars]) Explanation The line card attempted to register a port to the route processor but has failed after a few



Error Message %IPFAST-2-INVALSIZE: The IP fast path received an IPC message with an invalid size(size/type - [dec]/[dec]) Explanation The IP fast path switching module has received an IPC message with an invalid size. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %IPFAST-2-MSGDROP: IPC queue limit is reached and message is dropped. queue limit = [dec] cumulative drops = [dec] Explanation The IPC raw queue limit for IP fast path has been reached. Recommended Action Copy the message exactly as it appears on the console or in the system log.



712

IPFAST Messages


IPFAST-4 Error Message %IPFAST-4-FAILATTEMPTOPENIPCPORT: Attempt to open the IPC ports failed. [chars] Explanation The IPFAST process failed an attempt to open the IPC port to communicate to the line card or route processor. Recommended Action This is an informational message only. No action is required.

Error Message %IPFAST-4-FASTPORTCREATEWARN: Attempt to create [chars] failed. Will be retried [dec] times (last error:[chars]) Explanation The line card is attempting to create a port to the route processor but has failed. This

behavior could be transient. The system will reattempt to create the port. Recommended Action The system should be able to recover from this condition. If CEF becomes

disabled on this line card, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %IPFAST-4-FASTPORTOPENWARN: Attempt to open [chars] failed. Will be retried [dec] times (last error:[chars]) Explanation The line card is attempting to open a port to the route processor

but has failed. This behavior could be transient. The system will reattempt to create the port. Recommended Action The system should be able to recover from this condition. If CEF becomes

disabled on this line card, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


713

IP_HOST_ISSU Messages

Error Message %IPFAST-4-FASTPORTREGISTERWARN: Attempt to register [chars] failed. Will be retried [dec] times (last error:[chars]) Explanation The line card is attempting to register a port to the route processor but has failed. This could be transient behavior so retries will be attempted. Recommended Action The router should be able to recover from this situation. If CEF gets disabled

for this line card, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

IPFAST-5 Error Message %IPFAST-5-SUCCEEDOPENIPCPORT: Attempt to open the IPC ports succeeded. [chars] Explanation The IP fast switching has succeeded in an attempt to open the IPC port to communicate

with the line card or route processor. Recommended Action No action is required.

IP_HOST_ISSU Messages This section contains IP host in-service software upgrade (ISSU) messages.

IP_HOST_ISSU-2 Error Message %IP_HOST_ISSU-2-GET_BUFFER: IP Host ISSU client failed to get buffer for message. Error: %d (%s) Explanation The IP host ISSU client failed to get buffer space for building a negotiation message. A negotiation message cannot be sent to the standby device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly. Recommended Action Copy the message exactly as it appears on the console or in the system log.



714


representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs.

Error Message %IP_HOST_ISSU-2-INIT: IP Host ISSU client initialization failed to %s. Error: %d (%s) Explanation The IP host ISSU client could not be initialized. This initialization failure must be

addressed before an in-service software upgrade or downgrade can be performed successfully. Otherwise, a software upgrade or downgrade will result in downtime. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %IP_HOST_ISSU-2-SEND_NEGO_FAILED: IP Host ISSU client failed to send negotiation message. Error: %d (%s) Explanation The IP host ISSU client failed to send a session negotiation message to the peer device.

If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly. Recommended Action Copy the message exactly as it appears on the console or in the system log.



715


Error Message %IP_HOST_ISSU-2-SESSION_NEGO: IP Host ISSU client encountered unexpected client nego_done. Error: %d (%s) Explanation The IP host ISSU client encountered a client negotiation done state that was unexpected.



Error Message %IP_HOST_ISSU-2-SESSION_REGISTRY: IP Host ISSU client failed to register session information. Error: %d (%s) Explanation The IP host ISSU client failed to register session information. If a problem occurs with

the ISSU session registration, the standby device cannot be brought up properly. Recommended Action Copy the message exactly as it appears on the console or in the system log.


IP_HOST_ISSU-3 Error Message %IP_HOST_ISSU-3-CAP_INVALID_SIZE: IP_HOST ISSU client capability list is empty. Explanation The IP host ISSU client capability exchange list is empty, which is an invalid condition. Recommended Action Copy the message exactly as it appears on the console or in the system log.



716


representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show issu capability entries commands and your pertinent troubleshooting logs.

Error Message %IP_HOST_ISSU-3-CAP_NOT_COMPATIBLE: IP Host ISSU client capability exchange result incompatible. Explanation Based on the results of the capability exchange, the IP host ISSU client is not compatible with the peer. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show issu negotiated capability commands and your pertinent troubleshooting logs.

Error Message %IP_HOST_ISSU-3-INVALID_SESSION: IP Host ISSU client does not have a valid registered session. Explanation The IP host ISSU client does not have a valid registered session. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %IP_HOST_ISSU-3-MSG_NOT_OK: IP Host ISSU client ’Message Type %d’ is not compatible Explanation The IP host ISSU client received an incompatible message from the peer device. The

message cannot be processed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



717


open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, show issu message group, and show issu negotiated version commands and your pertinent troubleshooting logs.

Error Message %IP_HOST_ISSU-3-MSG_SIZE: IP Host ISSU client failed to get the MTU for Message Type %d. Error: %d (%s) Explanation The IP host ISSU client was unable to calculate the MTU for the specified message. As

a result, the client is not able to send the message to the standby device. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, show issu message group, and show issu negotiated version commands and your pertinent troubleshooting logs.

Error Message %IP_HOST_ISSU-3-SESSION_UNREGISTRY: IP Host ISSU client failed to unregister session information. Error: %d (%s) Explanation The IP host ISSU client failed to unregister session information. Recommended Action Copy the message exactly as it appears on the console or in the system log.



718

IPMCAST_LIB Messages

Error Message %IP_HOST_ISSU-3-TRANSFORM_FAIL: IP Host ISSU client %s transform failed for ’Message Type %d’. Error: %d (%s) Explanation The IP host ISSU client could not transform the specified message type. If the transmit

transformation failed, the checkpoint message was not sent to the standby device. If the receive transformation failed, the checkpoint message was not applied on the standby device. In either case, the IP host state between the active device and the standby device is not identical. Recommended Action Copy the message exactly as it appears on the console or in the system log.


IPMCAST_LIB Messages This section contains IP multicast library messages.

IPMCAST_LIB-4 Error Message %IPMCAST_LIB-4-RPF_DEPTH_ERR: Depth for rpf lookup greater than [dec] for [chars] Explanation The number of recursions for resolution of a given route has exceeded the allowed

maximum. This is usually due to misconfiguration. Recommended Action Review and fix the router configuration. If you require further assistance, copy

the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


719

IPNAT Messages

Error Message %IPMCAST_LIB-4-RPF_STATIC_ERR: No match for RIB static route [ipv6_addr]/[dec] in static table for root [ipv6_addr] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


IPMCAST_LIB-6 Error Message %IPMCAST_LIB-6-TIMER_BUSY: Timer drift is accumulating, [dec] msecs Explanation There is large amount of processing load and the timers are accumulating delay. Recommended Action If this message recurs, copy the message exactly as it appears on the console


IPNAT Messages This section contains IP Network Address Translation (IPNAT) messages.

IPNAT-4 Error Message %IPNAT-4-ADDR_ALLOC_FAILURE: Address allocation failed for [IP_address], pool [chars] might be exhausted


720

IPRT Messages

Explanation An address could not be allocated from the IP NAT pool. This condition can cause a

translation failure and might result in packets being dropped. The counter for missed packets will be incremented. Recommended Action Determine if the NAT pool has been exhausted. To reuse any existing addresses

in the NAT pool for new packet flows, clear the current NAT entries using the clear ip nat translation command.

IPNAT-6 Error Message %IPNAT-6-CREATED: [chars] Explanation A NAT flow entry was created. Recommended Action No action is required.

Error Message %IPNAT-6-DELETED: [chars] Explanation A NAT flow entry was deleted. Recommended Action No action is required.

IPRT Messages This section contains IP routing (IPRT) messages.

IPRT-4 Error Message %IPRT-4-TRACKOBJECTNONE: Illegal tracking number 0 on static route %i%m [%d/0] via %i, table %d, client %d Explanation The tracking number 0 was assigned to a static route, but 0 is not a legal value. Recommended Action Copy the message exactly as it appears on the console or in the system log.



721

IPSECV6 Messages

IPSECV6 Messages This section contains encryption feature messages.

IPSECV6-4 Error Message %IPSECV6-4-PKT_PROTOCOL_MISMATCH: IP protocol in packet mismatched with tunnel mode, packet from [chars] to [chars] dropped by [chars] Explanation The system tried to send an IPv4 packet into an IPsec IPv6 tunnel, or an IPv6 packet

into an IPsec IPv4 tunnel. The tunnel cannot handle this type of packet, and so the packet is dropped. Recommended Action Modify the tunnel configuration, either by removing the incorrect IP address type from the tunnel interface, or by changing the tunnel mode to match the IP address type.

Error Message %IPSECV6-4-RECVD_PKT_NOT_IPSECV6: Rec’d packet not an IPSEC packet. (ip) dest_addr=[ipv6_addr], src_addr=[ipv6_addr], prot= [dec] Explanation A received packet matched the crypto map ACL, but is not IPsec-encapsulated. An IPsec peer is sending unencapsulated packets. There may be a policy setup error on the peer. This activity could be considered a hostile event. Recommended Action Contact the administrator of the router or host that sent the packet to compare

policy settings.

Error Message %IPSECV6-4-RECVD_PKT_V6_INV_PROT: decapsulate: packet missing [chars], destadr[ipv6_addr], actual prot=[dec] Explanation A received IPsec packet is missing an expected AH or ESP header The peer is sending

packets that do not match the negotiated security policy. This activity could be considered a hostile event. Recommended Action Contact the administrator of the router or host that sent the packet to compare

policy settings.

Error Message %IPSECV6-4-RECVD_PKT_V6_INV_SPI: decaps: rec’d IPSEC packet has invalid spi for destaddr[ipv6_addr], prot=[dec], spi=[hex]([dec]), srcaddr[ipv6_addr] Explanation A received IPsec packet specifies SPI that does not exist in SADB. This may be a

temporary condition due to slight differences in aging of SAs between the IPsec peers, or it may be because the local SAs have been cleared. It may also be because of invalid packets sent by the IPsec peer. This activity could be considered a hostile event. Recommended Action If the local SAs have been cleared, the peer may not know this. In this case, if a new connection is established from the local router, the two peers may reestablish successfully. Otherwise, if the problem occurs for more than a brief period, either attempt to establish a new connection or contact the peer’s administrator.


722

IP_SNMP Messages

Error Message %IPSECV6-4-RECVD_PKT_V6_MSG_LEN_ERR: decapsulate: packet has bad [chars] length destadr[ipv6_addr], prot=[dec], len=[dec] Explanation A received IPsec packet is malformed, possibly because of an encapsulation error. The

peer is sending malformed packets. It may be due to a decryption error. This activity could be considered a hostile event. Recommended Action Contact the peer’s administrator.

IP_SNMP Messages This section contains IP Simple Network Management Protocol (SNMP) messages.

IP_SNMP-4 Error Message %IP_SNMP-4-NOTRAPIPV6: SNMP trap source %s has no ipv6 address Explanation The user entered an snmp-server trap-source command. The interface requested for use as the source address has no IPv6 address associated with it. The SNMP trap is being sent anyway, but without the source address that the user intended. Recommended Action Enter a no snmp-server trap-source command to disable the request for a specific source IP address, or add an IPv6 address to the interface referenced in the snmp-server trap-source configuration command.

IPV6 Messages This section contains IP version 6 messages.

IPV6-3 Error Message %IPV6-3-(-1): Cannot start the IPv6 process; router will not process IPv6 packets. Explanation The IPv6 process could not be started. This machine will not be able to process any IPv6

packets. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.


723

IPV6 Messages

Error Message %IPV6-3-INTERNAL: Internal error, [chars] Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %IPV6-3-INTERNAL_PAK: Internal error ([chars]): [hex] [hex] [chars] Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %IPV6-3-NO_UNIQUE_IDENTIFIER: Cannot determine an unique IPv6 identifier for the system.IPv6 will not be started. Explanation An unique IPv6 Identifier could not be determined for the system. Therefore the IPv6 process will not be started.This machine will not be able to process any IPv6 packets. Recommended Action Verify that there is at least one interface in this machine that supports

IEEE-style addresses.

Error Message %IPV6-3-RIB: [chars] Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



724

IPV6 Messages


Error Message %IPV6-3-UNFRAGMENTABLE: Cannot fragment packet: unfragmentable part length [dec], MTU of [dec] Explanation An internal software error occurred. A single packet originated by this system could not

be fragmented and has been dropped. Normal system operation continues. Recommended Action This is a transient error. However, this condition indicates other errors in the

software that will require further examination by your Cisco technical support representative. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

IPV6-4 Error Message %IPV6-4-DUPLICATE_OPTIMISTIC: Duplicate address %P on %s Explanation You have elected not to run duplicate address detection (DAD), but another system is

using your IPv6 address. Recommended Action Change the IPv6 address of one of the two systems.

Error Message %IPV6-4-LLA_CONFLICT: LLA conflict for static neighbor on [chars] : [chars] Explanation A neighborhood discovery (ND) message from the specified neighbor carries a

link-layer address (LLA) other than the configured address. Recommended Action Reconfigure the static neighbor with the correct link-layer address.

Error Message %IPV6-4-MAXPDB: Exceeded maximum supported IPv6 Routing Protocol instances Explanation Configuration of a routing protocol has failed because it would exceed the maximum

supported number of routing protocols. Recommended Action Reduce the number of IPv6 routing protocol instances configured.


725

IP_VRF Messages

IPV6-6 Error Message %IPV6-6-ACCESSLOGSP: list [chars]/[dec] [chars] [chars] [chars]->, [dec] packet[chars] Explanation A packet matching the log criteria for the given access list was detected. Recommended Action No action is required.

Error Message %IPV6-4-MULTICAST: Application does not support multicast destination address , packet dropped. Explanation An internal software error occurred. A multicast destination address was used in an

local application which does not yet handle IPv6 multicast. Recommended Action Use a unicast address in commands on the router. If the problem persists, or

you feel the command should support multicast, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

IP_VRF Messages This section contains IP VPN routing/forwarding instance common error (IP_VRF) messages.

IP_VRF-3 Error Message %IP_VRF-3-VRF_CACHE_ADD_ERROR: [chars] Explanation A cached VRF entry could not be created. Recommended Action Copy the message exactly as it appears on the console or in the system log.



726

IP_VRF Messages

Error Message %IP_VRF-3-VRF_CACHE_INIT_ERROR: [chars] Explanation A cached VRF entry could not be initialized. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %IP_VRF-3-VRF_CACHE_UPDATE_IF_LIST_FAIL: [chars] Explanation An update of the cached interface list for VRF failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %IP_VRF-3-VRF_CHKPT_TX_FAIL: [chars] Explanation An attempt to send a VRF table ID checkpoint message has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



727

IP_VRF Messages

Error Message %IP_VRF-3-VRF_CMN_INVALID_PARAM: [chars] Explanation An invalid parameter was used. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %IP_VRF-3-VRF_CREATE_FAIL: [chars] Explanation Creation of an IP VRF has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %IP_VRF-3-VRF_ID_INVALID_ERROR: Invalid VRF id [hex] in [chars] Explanation The VRF ID is invalid. Recommended Action Copy the message exactly as it appears on the console or in the system log.



728

IP_VRF Messages

Error Message %IP_VRF-3-VRF_IFLIST_NOT_EMPTY: VRF [chars] iflist is not empty in [chars] Explanation The VRF interface list is not empty Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %IP_VRF-3-VRF_IVRF_ERROR: [chars] Explanation A VRF infrastructure failure for platform VRFs occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %IP_VRF-3-VRF_MALLOC_FAIL: Memory allocation failure Explanation Memory could not be allocated for a VRF. Recommended Action Copy the message exactly as it appears on the console or in the system log.



729

IP_VRF Messages

Error Message %IP_VRF-3-VRF_MISSING_NAME_REC: VRF [dec] name record is null [chars] Explanation VRF name record is null Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %IP_VRF-3-VRF_TABLEID_INCONSISTENT: [chars] Explanation The VRF table ID is inconsistent between two RPs. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %IP_VRF-3-VRF_TABLEID_INVALID: [chars] Explanation The VRF table ID is invalid. Recommended Action Copy the message exactly as it appears on the console or in the system log.



730

ISA Messages

IP_VRF-4 Error Message %IP_VRF-4-VRF_DELETE_WAIT: The VRF [chars] is getting deleted after a wait Explanation There are routes remaining in the deleted VRF routing table. To ensure reusablity of the

same VRF, the system forcibly clears the routes in the VRF routing table, which causes the VRF to be deleted. Recommended Action Copy the message exactly as it appears on the console or in the system log.


ISA Messages This section contains Integrated Services Adapter (ISA) messages.

Error Message %ISA-1-ALIGN: Alignment failure on packet buffer: [hex] Explanation A software error has occurred. The ISA driver detected that the buffer is not aligned

correctly. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISA-1-ERROR: [chars] Explanation An error occurred in the application using ISA. Recommended Action Copy the message exactly as it appears on the console or in the system log.



731

ISA Messages


Error Message %ISA-6-INFO: [chars] Explanation This is an informational message from ISA. Recommended Action This is an informational message only and occurs in normal operation. No

action is required.

Error Message %ISA-1-INITDESCRING: Slot [dec]: The ISA driver failed to allocate "descriptor offsets" write_offsets: [hex], read_offsets: [hex], stored_offsets: [hex] Explanation The ISA driver failed to initialize at the specified point. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISA-1-INITFAIL: Slot [dec]: [chars] Explanation The ISA driver failed to initialize at the specified point. Recommended Action Copy the message exactly as it appears on the console or in the system log.



732

ISA Messages

Error Message %ISA-1-NOMEMORY: [chars] creation failed for slot [dec] Explanation The ISA driver, in its initialization phase, could not allocate memory for the specified

data structure. Recommended Action Consider adding more shared memory. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %ISA-1-OWNER: [chars] packet buffer, pak=[hex] Explanation A software or hardware error has occurred. The ISA driver detected that the buffer ring

is in an inconsistent and unrecoverable state. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISA-6-SHUTDOWN: [chars] shutting down Explanation The specified ISA is shutting down. It may have been physically removed. Recommended Action This is an informational message only and occurs in normal operation. No

action is required.

Error Message %ISA-1-TOOBIG: [chars] received a packet with size [dec]. Explanation The system has received a packet that is larger than the allowed size. Recommended Action Copy the message exactly as it appears on the console or in the system log.



733

ISSU Messages


ISSU Messages This section contains In-Service Software Upgrade (ISSU) messages.

ISSU-3 Error Message %ISSU-3-BAD_PARAMS: %s Explanation Bad parameters were detected in the ISSU process. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISSU-3-BASE_CLIENT_CHECK_COMPATIBILITY: %s Explanation An error was found during checking of the ISSU base client compatibility. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISSU-3-CLIENT_OR_ENTITY_NOT_REG: Client([dec]) or entity([dec]) is not registered [chars]. Explanation The specified client or entity is not registered. Recommended Action Enter the show issu client | grep client id command. Copy the message exactly

as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and


734

ISSU Messages

utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %ISSU-3-CLIENT_REG_DIST: Failed to %s distributed client %d Explanation A distributed client reservation or unreservation failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISSU-3-DEBUG_ERROR: [chars] Explanation An error occurred when turning on ISSU debug. Recommended Action Enter the show issu client | grep client id command. Copy the message exactly


Error Message %ISSU-3-DUMY_ENTRY_NOT_LAST: Dumy cap entry is not last one for cap group([dec]) registration under client([dec]) and entity([dec]) Explanation The dummy cap entry is not the last one for the cap group registration. Recommended Action Enter the show issu client | grep client id command. Copy the message exactly



735

ISSU Messages


Error Message %ISSU-3-DUMMY_VERSION_OUT_OF_RANGE: Dummy msg version (%d) is out of range for msg(%d) under client %s(%d) and entity(%d). Explanation The dummy message version is out of range. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show issu message type | include commands and your pertinent troubleshooting logs.

Error Message %ISSU-3-DUP_DUMMY_VERSION_REG: %s is already registered under client %s(%d), entity(%d), and msgtype(%d) Explanation The specified item is registered already under that message type. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show issu message type | include commands and your pertinent troubleshooting logs.

Error Message %ISSU-3-DUP_ENTITY_REG: Entity([dec]) is registered already under client([dec]) Explanation The entity is duplicated under the client. Recommended Action Enter the show issu client | grep client id command. Copy the message exactly



736

ISSU Messages


Error Message %ISSU-3-DUP_ITEM_IN_REG_UNDER_ENTITY: [chars] is duplicated [chars] under client([dec]) and entity([dec]) Explanation Item is duplicated under the client and entity. Recommended Action Enter the show issu client | grep client id command. Copy the message exactly


Error Message %ISSU-3-DUP_REG_ENDPOINT: Endpoint is registered already. Explanation The endpoint is already registered. Recommended Action Enter the show issu endpoint command to check if the ISSU subsystem was

initialized twice.

Error Message %ISSU-3-DUP_REG_UNDER_ENDPOINT: [chars]([dec]) is registered already under endpoint. Explanation The item is already registered under the endpoint. Recommended Action Enter the show issu client | grep client id command. Copy the message exactly


Error Message %ISSU-3-DUP_REG_UNDER_ENTITY: [chars]([dec]) is registered already under client([dec]) and entity([dec]) Explanation The item is already registered under the client and entity. Recommended Action Enter the show issu client | grep client id command. Copy the message exactly

as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and


737

ISSU Messages

utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %ISSU-3-EMPTY_DUMMY_VERSION: %s is empty under client %s(%d), entity(%d). Explanation The dummy version is empty. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISSU-3-EMPTY_UNDER_CLIENT: [chars] is empty under client([dec]). Explanation The item is empty in the client. Recommended Action Enter the show issu client | grep client id command. Copy the message exactly


Error Message %ISSU-3-EMPTY_UNDER_ENDPOINT: [chars] is empty under endpoint. Explanation The item is empty under the endpoint. Recommended Action Enter the show issu client | grep client id command. Copy the message exactly



738

ISSU Messages


Error Message %ISSU-3-EMPTY_UNDER_ENTITY: [chars] is empty [chars] under client([dec]) and entity([dec]). Explanation The item is empty in the client and entity. Recommended Action Enter the show issu client | grep client id command. Copy the message exactly


Error Message %ISSU-3-ENDPOINT_NOT_REG: Endpoint is not registered yet. Explanation The endpoint is not registered yet. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISSU-3-ERP_AGENT: [chars] Explanation One of the primary functions for the ERP agent failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



739

ISSU Messages

Error Message %ISSU-3-ERP_AGENT_SEND_MSG: [chars]; error code is [chars] Explanation The send message function call failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISSU-3-ERP_CLIENT: [chars] Explanation One of the primary functions for the ERP client failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISSU-3-ERP_CLIENT_EVENT: Unknown [chars] event - [dec] Explanation An unknown event was received. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISSU-3-EXTERNAL_MATRIX_FILE_ERR: Line %u: %s Explanation An error was found in the external matrix data file. Recommended Action Open a case with TAC, and attach the output of the more ivfs:/matrix_cm_file command, where matrix_cm_file is the output of the dir system:image command.


740

ISSU Messages

Error Message %ISSU-3-FAILED_TO_ALLOC_CHUNK_MEMORY: [chars] type chunk allocation failed. Explanation A memory allocation has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISSU-3-FAILED_TO_ALLOC_DUMMY_VERSION: Can not allocate %s under client %s(%d) and entity(%d) Explanation The ISSU process could not allocate a dummy version under the client and entity. Recommended Action Enter the show proc mem or show buffs command to determine whether the memory or buffer is full, indicating a possible memory leak. To recover, shut down any unused tasks and reset the cards. If these actions do not help, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %ISSU-3-FAILED_TO_ALLOC_ENTITY: Can not allocate entity([dec]) under client([dec]) Explanation Cannot allocate an entity control block under the client. Recommended Action Enter the show proc mem or show buffs command to check if memory or buffer is full. Shuting down unused tasks or resetting cards usually can recover a memory leak problem. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


741

ISSU Messages

Error Message %ISSU-3-FAILED_TO_ALLOC_FUNCT_UNDER_ENDPOINT: Can not allocate [chars]. Explanation Cannot allocate the function callback. Recommended Action Enter the show proc mem or show buffs command to check if memory or buffer is full. Shutingt down unused tasks or resetting cards usually can recover those memory leak problem. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %ISSU-3-FAILED_TO_ALLOC_FUNCT_UNDER_ENTITY: Can not allocate [chars] under client([dec]) and entity([dec]) Explanation Cannot allocate control block under the client and entity. Recommended Action Enter the show proc mem or show buffs command to check if memory or buffer is full. Shuting down unused tasks or resetting cards usually can recover a memory leak problem. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %ISSU-3-FAILED_TO_ALLOC_MEMORY: memory allocation for %s failed. Explanation The ISSU process could not allocate memory. Recommended Action Copy the message exactly as it appears on the console or in the system log.



742

ISSU Messages

Error Message %ISSU-3-FAILED_TO_ALLOC_UNDER_ENDPOINT: Can not allocate [chars]([dec]) control block. Explanation Cannot allocate a control block. Recommended Action Enter the show proc mem or show buffs command to check if memory or buffer is full. Shuting down unused tasks or resetting cards usually can recover a memory leak problem. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %ISSU-3-FAILED_TO_ALLOC_UNDER_ENTITY: Can not allocate [chars]([dec]) under client([dec]) and entity([dec]) Explanation Cannot allocate a control block under the client and entity. Recommended Action Enter the show proc mem or show buffs command to check if memory or buffer is full. Shuting down unused tasks or resetting cards usually can recover a memory leak problem. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %ISSU-3-FAILED_TO_ALLOC_UNDER_GROUP: Can not allocate [chars]([dec]) for [chars]([dec]) registration under client([dec]) and entity([dec]) Explanation Cannot allocate an item for group registration under the client and entity. Recommended Action Enter the show proc mem or show buffs command to check if memory or buffer is full. Shuting down unused tasks or resetting cards usually can recover a memory leak problem. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support


743

ISSU Messages


Error Message %ISSU-3-FAILED_TO_ALLOC_UNDER_MSG: Can not allocate [chars] for msg ([dec]) registration under client([dec]) and entity([dec]) Explanation Cannot allocate a control block for message registration. Recommended Action Enter the show proc mem or show buffs command to check if memory or buffer is full. Shuting down unused tasks or resetting cards usually can recover a memory leak problem. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %ISSU-3-FAILED_TO_ALLOC_UNDER_MSG_SES: Can not allocate [chars] for msg session([dec]) registration under client([dec]) and entity([dec]) Explanation Cannot allocate a control block for message session registration. Recommended Action Enter the show proc mem or show buffs command to check if memory or buffer is full. Shuting down unused tasks or resetting cards usually can recover a memory leak problem. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %ISSU-3-FAILED_TO_CREATE_ID32_SPACE: Failed to create ID32 space. Explanation Failed to create ID32 space. Recommended Action Enter the show proc mem or show buffs command to check if memory or buffer is full. Shuting down unused tasks or resetting cards usually can recover a memory leak problem. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,


744

ISSU Messages


Error Message %ISSU-3-FAILED_TO_INIT_ISSU_PROTO: Failed to initialize ISSU proto. Explanation Failed to initialize the ISSU protocol. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISSU-3-FAILED_TO_UNREG_SES: Failed to unregister [chars] session under client([dec]) and entity([dec]) Explanation Failed to unregister the session. Recommended Action Enter the show proc mem or show buffs command to check if memory or buffer is full. Shuting down unused tasks or resetting cards usually can recover a memory leak problem. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %ISSU-3-FOREIGN_OWNED_FIELDS: %s; err code [%s] Explanation The transformation of a foreign owned field (FOF) has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



745

ISSU Messages


Error Message %ISSU-3-FSM_BADMSG: Session [dec] in received message [chars] is wrong. Explanation Sessions on peers are mismatched or were not found. Recommended Action Enter the show issu session | grep session id command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %ISSU-3-FSM_DUP_UID: Duplicate unique_id on session [dec]: my_uid [dec], peer_uid [dec]. Explanation The requirement that each endpoint must have distinctive identifier has been violated. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISSU-3-FSM_INIT: Fail to create process during FSM init. Explanation Creation of an FSM timer process has failed. Recommended Action Check what system resources are available during bootup.

Error Message %ISSU-3-FSM_MISMATCH_MTU: ISSU nego failed for client %s(%d) entity_id %d session %d due to mismatch of mtu size %d & %d. Explanation The ISSU negotiation failed due to a mismatch in the negotiation version MTU size. Recommended Action Copy the message exactly as it appears on the console or in the system log.



746

ISSU Messages

http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message types, and show issu fsm | include commands and your pertinent troubleshooting logs.

Error Message %ISSU-3-FSM_NEGO_SEND_ERR: Client ’%s’ with ID %d encountered ’%s’ in session %d. Explanation The ISSU negotiation message could not be sent. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session | include, and show issu fsm commands and your pertinent troubleshooting logs.

Error Message %ISSU-3-FSM_RUNTIME_ERR: [chars] occurs during FSM negotiation in session [dec]. Explanation Runtime error occurs during FSM negotiation. Recommended Action Enter the show issu session | grep session id command. Copy the message


Error Message %ISSU-3-HANDLE_SIZE: Handle buffer size is %d, should be %d Explanation A statically defined handle buffer size is incorrect. Recommended Action Copy the message exactly as it appears on the console or in the system log.



747

ISSU Messages


Error Message %ISSU-3-INCOMPATIBLE_BASE_CLIENTS: %s Explanation This message displays a list of ISSU base clients found to be incompatible. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISSU-3-INCOMPATIBLE_PEER_UID: Setting image (%s), version (%s) on peer uid (%d) as incompatible Explanation The peer client is incompatible. Recommended Action Synchronize the configurations and reload the standby supervisor.

Error Message %ISSU-3-INCONSISTENT_MSG_TYPE: %s Explanation A runtime registration error has occurred. Message types passed for foreign owned

fields (FOFs) are inconsistent. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISSU-3-IN_USE_UNDER_ENDPOINT: [chars]([dec]) is in use under endpoint Explanation Item is in use under the endpoint. Recommended Action Enter the show issu session | grep session id command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools


748

ISSU Messages


Error Message %ISSU-3-IN_USE_UNDER_ENTITY: [chars]([dec]) is in use under client([dec]) and entity([dec]) Explanation Item is in use under the client and entity. Recommended Action Enter the show issu session | grep session id command. Copy the message


Error Message %ISSU-3-INVALID_ITEM_UNDER_ENDPOINT: Invalid [chars] under endpoint Explanation Invalid item under the endpoint. Recommended Action Enter the show issu session | grep session id command. Copy the message


Error Message %ISSU-3-INVALID_ITEM_UNDER_ENTITY: Invalid [chars] under client([dec]) and entity([dec]) Explanation Invalid item under the client and entity. Recommended Action Enter the show issu session | grep session id command. Copy the message

exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support


749

ISSU Messages


Error Message %ISSU-3-INVALID_PARAM_UNDER_SES: Invalid params %s under session(%d) Explanation Invalid parameters were detected under the session. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show issu session | include commands and your pertinent troubleshooting logs.

Error Message %ISSU-3-INVALID_VERSION_LOWHIGH: Invalid low([dec]) and high([dec]) value for msg([dec]) under client([dec]) and entity([dec]). Explanation Invalid low and high value for group registration. Recommended Action Enter the show issu session | grep session id command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %ISSU-3-IPC_PORT: Port name ’[chars]’ failure; reason is ’[chars]’. Explanation Creation or removal of the named port failed for IPC. Recommended Action Copy the message exactly as it appears on the console or in the system log.



750

ISSU Messages

Error Message %ISSU-3-ISSU_INIT_NOT_COMPLETE: %s Explanation ISSU initialization has not been completed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISSU-3-JID: Failed to get the local process JID with err %d Explanation The system manager call to collect the job ID has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISSU-3-MISSING_ITEM_IN_REG: [chars]([dec]) is not available [chars] under client([dec]) and entity([dec]) Explanation Item is not available for registration. Recommended Action Enter the show issu session | grep session id command. Copy the message



751

ISSU Messages

Error Message %ISSU-3-MSG_NEGO_RESULT_CHUNK: Failed to %s element %x Explanation The message negotiation result element could not be locked or freed, indicating an

invalid element or corrupted memory. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISSU-3-MSG_SES_IN_MSG_NOT_FOUND: The intended session %d specified in received %s for client %s(%d) is not found. Explanation No session could be found with the session ID specified in the received message. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show issu session | include commands and your pertinent troubleshooting logs.

Error Message %ISSU-3-NON_ISSU_ID_UNDER_ENDPOINT: Non ISSU [chars] Explanation Peer endpoint does not support ISSU. Recommended Action Copy the message exactly as it appears on the console or in the system log.



752

ISSU Messages

Error Message %ISSU-3-NO_PEER_UID: No peer uid found at [chars] Explanation No peer UID with this value was found registered in the ISSU database. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISSU-3-NOT_DUMY_CAP_TYPE: Cap type([dec]) is not dumy one. Explanation Cap type is not dummy. Recommended Action Enter the show issu cap type | grep cap type command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %ISSU-3-NOT_FIND_ENTITY: Can not find entity([dec]) under client([dec]). Explanation Cannot find entity under the client. Recommended Action Enter the show issu session | grep session id command. Copy the message



753

ISSU Messages

Error Message %ISSU-3-NOT_FIND_FUNCT_UNDER_SESSION: Can not find [chars] under [chars] session([dec]). Explanation Cannot find function under the session. Recommended Action Enter the show issu session | grep session id command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %ISSU-3-NOT_FIND_MSG_SES: Can not find message session([dec]) [chars]. Explanation Cannot find message session. Recommended Action Enter the show issu session | grep session id command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %ISSU-3-NOT_FIND_UNDER_ENDPOINT: Can not find [chars]([dec]) control block under endpoint. Explanation Cannot find a control block under the endpoint. Recommended Action Enter the show issu client | grep client id command. Copy the message exactly



754

ISSU Messages

Error Message %ISSU-3-NOT_FIND_UNDER_ENTITY: Can not find [chars]([dec]) control block under client([dec]) and entity([dec]). Explanation Cannot find a control block under the client and entity. Recommended Action Enter the show issu client | grep client id command. Copy the message exactly


Error Message %ISSU-3-NOT_FIND_UNDER_SESSION: Can not find [chars]([dec]) under [chars] session([dec]). Explanation Cannot find item under the session. Recommended Action Enter the show issu session | grep session id command. Copy the message


Error Message %ISSU-3-NOT_REG_UNDER_ENDPOINT: [chars]([dec]) is not registered under endpoint. Explanation Item is not registered under the endpoint. Recommended Action Enter the show issu client | grep client id command. Copy the message exactly



755

ISSU Messages

Error Message %ISSU-3-NOT_REG_UNDER_ENTITY: [chars]([dec]) is not registered under client([dec]) and entity([dec]) Explanation Item is not registered under the client and entity. Recommended Action Enter the show issu client | grep client id command. Copy the message exactly


Error Message %ISSU-3-NO_UID: No uid ([dec]) registered with ISSU at [chars] Explanation No UID with this value was found registered in the ISSU database. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISSU-3-NULL_CALLBACK_UNDER_ENDPOINT: [chars] callback is NULL for registration. Explanation Callback is NULL for registration. Recommended Action Enter the show issu client | grep client id command. Copy the message exactly



756

ISSU Messages

Error Message %ISSU-3-NULL_CALLBACK_UNDER_ENTITY: [chars] callback is NULL for msg session registration under client([dec]) and entity([dec]) Explanation Callback is NULL for message session registration. Recommended Action Enter the show issu client | grep client id command. Copy the message exactly


Error Message %ISSU-3-NULL_CALLBACK_UNDER_SESSION: Can not register null [chars] callback in [chars] session([dec]). Explanation Cannot register NULL callback in the session. Recommended Action Enter the show issu session | grep session id and show issu fsm | grep session id commands. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %ISSU-3-PEER_IMAGE_INCOMPATIBLE: Peer image (%s), version (%s) on peer uid (%d) is incompatible Explanation The peer client is incompatible. Recommended Action Synchronize the configurations and reload the standby supervisor.

Error Message %ISSU-3-PEER_IMAGE_NOT_IN_INCOMP_LIST: Peer image (%s), version (%s) on peer uid (%d) is not in the incompatible images list Explanation The peer client is incompatible. Recommended Action Synchronize the configurations and reload the standby supervisor.


757

ISSU Messages

Error Message %ISSU-3-PEER_IMAGE_REM_FROM_INCOMP_LIST: Peer image (%s), version (%s) on peer uid (%d) being removed from the incompatibility list Explanation The peer client is incompatible. Recommended Action Synchronize the configurations and reload the standby supervisor.

Error Message %ISSU-3-PEER_INCOMP_SET: Peer incompatibility set for image (%s), version (%s) on peer uid (%d) Explanation The peer client is incompatible. Recommended Action Synchronize the configurations and reload the standby supervisor.

Error Message %ISSU-3-PEER_UID_CB_IS_NULL: Peer uid control block is NULL Explanation The peer client is incompatible. Recommended Action Synchronize the configurations and reload the standby supervisor.

Error Message %ISSU-3-PROTO_CLIENT_ENTITY_UNREG: Proto Client entity unreg for [chars] has failed Explanation A protocol client has failed to unregister its entity with ISSU. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISSU-3-PROTO_CLIENT_REG: Proto Client registration for [chars] has failed Explanation Protocol client has failed to register with ISSU. Recommended Action Copy the message exactly as it appears on the console or in the system log.



758

ISSU Messages

Error Message %ISSU-3-REF_TREE: %s reference tree %s failed Explanation The AVL-based ISSU reference tree operation failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISSU-3-SESSION_ID_ERROR: Failed to %s session id %d for %s Explanation A session ID related operation failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISSU-3-SESSION_RENEGOTIATE: Client Attemptiong to renegotiate on session [dec] Explanation A client is attempting to renegotiate a session without unregistering it and doing the negotiation over again. This is not allowed. Recommended Action Unregister the message session first, and then reregister and attempt the

negotiation.

Error Message %ISSU-3-SET_UNKNOWN_UID: Unknown unique_id is set. Explanation Platform team should provide distinctive identifier for the endpoint. Recommended Action Copy the message exactly as it appears on the console or in the system log.



759

ISSU Messages


Error Message %ISSU-3-TRANSPORT_ERP_UID_CB_IS_NULL: Transport ERP uid control block is NULL Explanation The peer client is incompatible. Recommended Action Synchronize the configurations and reload the standby supervisor.

Error Message %ISSU-3-UNKNOWN_ENTITY_ID: Unknown entity id under client([dec]) Explanation There is an unknown entity ID under the specified client. Recommended Action Enter the show issu client | grep client id command. Copy the message exactly


Error Message %ISSU-3-UNKNOWN_ID_UNDER_ENDPOINT: Can not use unknown [chars]. Explanation Cannot use the specified unknown ID. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISSU-3-UNKNOWN_ID_UNDER_ENTITY: Unknown [chars] under client([dec]) and entity([dec]) Explanation Unknown ID under the specified client and entity. Recommended Action Enter the show issu client | grep client id command. Copy the message exactly

as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug


760

ISSU Messages

Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %ISSU-3-VERSION_LOWHIGH_NOT_MATCH_TABLE_SIZE: Version low([dec]) and high([dec]) value for msg([dec]) does not match table size([dec]) under client([dec]) and entity([dec]). Explanation Version low and high values for the specified message do not match the specified table

size. Recommended Action Enter the show issu client | grep client id command. Copy the message exactly


Error Message %ISSU-3-VERSION_OUT_OF_ORDER: Msg version([dec],[dec]) is out of order for msg([dec]) under client([dec]) and entity([dec]). Explanation The specified message version is out of order for the specified group registration. Recommended Action Enter the show issu client | grep client id command. Copy the message exactly


Error Message %ISSU-3-VERSION_OUT_OF_RANGE: Msg version([dec],[dec]) is out of range for msg([dec]) under client([dec]) and entity([dec]). Explanation The specified message version is out of range for the specified group registration. Recommended Action Enter the show issu client | grep client id command. Copy the message exactly

as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require


761

ISSU Messages

assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

ISSU-4 Error Message %ISSU-4-FSM_INCOMP: Version of local ISSU client [dec] in session [dec] is incompatible with remote side. Explanation The protocol versions of the local and remote clients are incompatible. These clients

cannot communicate with each other. Recommended Action Use the show version and show issu clients commands to help verify that the

software images are incompatible. Upgrade the software images on each unit to versions that are compatible. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %ISSU-4-MSG_INCOMP: Message([dec]) is incompatible under msg session([dec]). Explanation The specified message is incompatible under the specified message session. Recommended Action Enter the show issu session | grep session id and show issu fsm | grep session id commands. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


762

ISSU_CS Messages

Error Message %ISSU-4-NEGO_NOT_FINISHED: Negotiation is not finished for client [dec], msg session([dec]). Explanation Negotiation is not finished for the specified client and message session. Recommended Action Enter the show issu session | grep session id and show issu fsm | grep session id commands. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

ISSU_CS Messages This section contains ISSU configuration synchronization messages.

ISSU_CS-3 Error Message %ISSU_CS-3-BULK_CONFIG_TR: [chars] [chars] Explanation ISSU bulk configuration synchronization transformation failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISSU_CS-3-DL: [chars] [chars] Explanation The ISSU configuration synchronization difference list is displayed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



763

ISSU_CS Messages


Error Message %ISSU_CS-3-DL_STATS: [chars][dec][chars] Explanation ISSU configuration synchronization difference list statistics are displayed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISSU_CS-3-LBL_CONFIG_TR: [chars] [chars] Explanation ISSU line-by-line configuration synchronization transformation failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISSU_CS-3-SKL: [chars] [chars] Explanation An ISSU configuration synchronization SKL operation failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



764

ISSU_CS_DL_MESSAGES Messages

ISSU_CS_DL_MESSAGES Messages This section contains ISSU configuration synchronization difference list messages.

ISSU_CS_DL_MESSAGES-3 Error Message %ISSU_CS_DL_MESSAGES-3-DL_CLI_DUMP: [chars][dec][chars][dec][chars] Explanation ISSU configuration synchronization difference list CLI generation statistics are

displayed. Recommended Action No action is required.

ISSU_ERROR Messages This section contains ISSU error messages.

ISSU_ERROR-2 Error Message %ISSU_ERROR-2-CLIENT_INCOMPATIBLE: %s(%d): ISSU Client not compatible Explanation The ISSU client is incompatible with the current version. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISSU_ERROR-2-NEGO_NOT_DONE: %s(%d): ISSU Negotiation not complete Explanation The ISSU client was unable to complete ISSU negotiation. Recommended Action Copy the message exactly as it appears on the console or in the system log.



765

ISSU_ERROR Messages


Error Message %ISSU_ERROR-2-NTI_EP_TYPE_REG: %s(%d): Failed to register EP type (%d) with NTI: %s (%d) Explanation The ISSU client could not register the endpoint (EP) type with the Negotiation Trigger

Infrastructure (NTI). Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISSU_ERROR-2-NTI_EP_TYPE_UNREG: %s(%d): Failed to unregister EP type (%d) with NTI: %s (%d) Explanation The ISSU client could not unregister the endpoint type with NTI. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISSU_ERROR-2-NTI_REG: %s(%d): Failed to register with NTI: %s (%d) Explanation The ISSU client could not register with NTI. Recommended Action Copy the message exactly as it appears on the console or in the system log.



766

ISSU_ERROR Messages

Error Message %ISSU_ERROR-2-NTI_UNREG: %s(%d): Failed to unregister with NTI: %s (%d) Explanation The ISSU client could not be unregistered with NTI. Recommended Action Copy the message exactly as it appears on the console or in the system log.


ISSU_ERROR-3 Error Message %ISSU_ERROR-3-CAPENTRY_REG: %s(%d): failed to register a capability entry (%s) Explanation The ISSU client failed to register a capability entry. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISSU_ERROR-3-CAPGROUP_REG: %s(%d): failed to register a capability group (%s) Explanation The ISSU client failed to register a capability group. Recommended Action Copy the message exactly as it appears on the console or in the system log.



767

ISSU_ERROR Messages

Error Message %ISSU_ERROR-3-CAPTYPE_REG: %s(%d): failed to register capability type (%s) Explanation The ISSU client failed to register a capability type. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISSU_ERROR-3-CAP_EXCHANGE: %s(%d): Capability exchange failed with error (%s) Explanation The capability exchange failed and the ISSU client is unable to process the received

capability. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISSU_ERROR-3-CAP_REG: %s(%d): failed to register its capabilities (%s) Explanation The capabilities of the ISSU client could not be registered. Recommended Action Copy the message exactly as it appears on the console or in the system log.



768

ISSU_ERROR Messages

Error Message %ISSU_ERROR-3-CF_SEND: %s(%d): Client failed to send message (%d) Explanation The ISSU client cannot send a negotiation message to a peer. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISSU_ERROR-3-CLIENT_REG: %s(%d): Client failed to register (%s) Explanation The ISSU client could not be registered. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISSU_ERROR-3-CLIENT_REG_FAILED: %s(%d): Client is not initialized Explanation The ISSU client is not initialized. The negotiation for this client is not yet done. Recommended Action Copy the message exactly as it appears on the console or in the system log.



769

ISSU_ERROR Messages

Error Message %ISSU_ERROR-3-ENTITY_REG: %s(%d): failed to register the entity (%s) Explanation The ISSU entity could not be registered. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISSU_ERROR-3-ENTITY_UNREG: %s(%d): failed to unregister the entity (%s) Explanation The ISSU entity could not be unregistered. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISSU_ERROR-3-ICC_SEND: %s(%d): Client failed to send message Explanation The ISSU client cannot send a negotiation message to a peer. Recommended Action Copy the message exactly as it appears on the console or in the system log.



770

ISSU_ERROR Messages

Error Message %ISSU_ERROR-3-MSGGROUP_REG: %s(%d): failed to register a message group (%s) Explanation The ISSU client cannot register a message group. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISSU_ERROR-3-MSGTYPE_REG: %s(%d): failed to register a message type (%s) Explanation The ISSU client cannot register a message type. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISSU_ERROR-3-MSG_MTU: %s(%d): Client failed to get mtu for message %d (%s) Explanation The ISSU client cannot get the MTU for the message. Recommended Action Copy the message exactly as it appears on the console or in the system log.



771

ISSU_ERROR Messages

Error Message %ISSU_ERROR-3-MSG_NOT_OK: %s(%d): ISSU message type (%d) is not compatible Explanation The ISSU process received a message not compatible with the running version. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show message type commands and your pertinent troubleshooting logs.

Error Message %ISSU_ERROR-3-MSG_POLICY: %s(%d): Client failed to negotiate version for message type (%d), error (%s) Explanation The ISSU client cannot negotiate the message type with a peer. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISSU_ERROR-3-MSG_REG: %s(%d): failed to register its messages (%s) Explanation Messages for the ISSU client could not be registered. Recommended Action Copy the message exactly as it appears on the console or in the system log.



772

ISSU_ERROR Messages

Error Message %ISSU_ERROR-3-MTU_NOT_ENOUGH: %s(%d): Requested buffer size (%d) is greater than the max MTU size (%d) Explanation The checkpoint buffer size requested is greater than the maximum MTU size supported

by the checkpoint feature. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISSU_ERROR-3-NEGO_PROCESS: %s(%d): Cannot create process: %s Explanation The process to negotiate the session for the specified ISSU client cannot be created. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISSU_ERROR-3-REG_ARBITRATE_CALLBACK: %s(%d): Failed to register first speaker arbitration callback - %s) Explanation The ISSU client could not register the first speaker arbitration callback. Recommended Action Copy the message exactly as it appears on the console or in the system log.



773

ISSU_ERROR Messages

Error Message %ISSU_ERROR-3-SESSION_REG: %s(%d): session failed to register (%s) Explanation The client’s ISSU session could not be registered. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISSU_ERROR-3-SESSION_UNREG: %s(%d): session (%d) failed to unregister (%s) Explanation The client’s ISSU session could not be unregistered. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISSU_ERROR-3-START_NEGO_FAILED: %s(%d): failed to start negotiation (%s) Explanation The ISSU client cannot start its negotiation. Recommended Action Copy the message exactly as it appears on the console or in the system log.



774

ISSU_PROCESS Messages

Error Message %ISSU_ERROR-3-TRANSFORM_FAILED: %s(%d): %s transformation failed (%s) Explanation The transformation operation for the ISSU message has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISSU_ERROR-3-TRANSFORM_FAILED_DETAILED: %s(%d): %s transformation failed for message %d, endpoint %d (%s) Explanation The transformation operation for the ISSU message has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


ISSU_PROCESS Messages This section contains ISSU process messages.

ISSU_PROCESS-3 Error Message %ISSU_PROCESS-3-ABORTVERSION: issu loadversion; %s Explanation The ISSU abortversion command can be run only from the LoadVersion or RunVersion

ISSU state. Recommended Action Reinitialize the ISSU process.


775


Error Message %ISSU_PROCESS-3-ACCEPTVERSION: issu acceptversion; %s Explanation The ISSU acceptversion command did not execute because one of the following

conditions was not met: — The active supervisor was not in the RunVersion ISSU state. — The active supervisor’s ROMMON does not contain the current version. — The active supervisor’s ROMMON does not contain the primary version. — The primary and current versions are not the same. — The standby supervisor’s ROMMON does not contain the current version. — The standby supervisor’s current and primary image names are different. — The active supervisor does not have the secondary version. — The active’s secondary version and the standby’s current version are different. Recommended Action Correct the condition and retry the command.

Error Message %ISSU_PROCESS-3-COMMITVERSION: issu commitversion; %s Explanation The ISSU commitversion command did not execute because one of the following conditions was not met: — The current ISSU state is not RunVersion. — The secondary version does not exist on the standby supervisor. — The standby BOOT variable does not exist. — The new image is not the first in BOOT on the standby supervisor. — The active BOOT variable is not set. — The primary version does not exist on the active supervisor. — The new image is not the first in the active BOOT. — The configuration register is not 0x2102. Recommended Action Correct the error condition and retry the command.

Error Message %ISSU_PROCESS-3-CONFIGREG: ISSU process is in progress; Changing configuration register might disrupt the upgrade process Explanation The configuration register value should not be changed while the ISSU process is in

progress. Recommended Action The low-order byte of the configuration register should be 0x02 during the

upgrade process.

Error Message %ISSU_PROCESS-3-FILESYS: ’[chars]’ filesystem does not exist Explanation Verification of the file system failed. Recommended Action Download the file to the flash disk.


776


Error Message %ISSU_PROCESS-3-IMAGE: %s is loading the wrong image [ %s ], expected image [ %s ] Explanation The wrong image is being loaded during the ISSU process. Recommended Action Check the detail state of the ISSU process and make sure that the correct

images are loaded on the active and standby supervisors.

Error Message %ISSU_PROCESS-3-IPC_AGENT: [chars] [ [chars] ] Explanation The ISSU process IPC agent had an error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISSU_PROCESS-3-IPC_MSG: %s Explanation An error occurred in the setup of the interprocess communication (IPC) message queue. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISSU_PROCESS-3-LOADVERSION: %s Explanation The ISSU loadversion command did not execute because one of the following

conditions was not met: — The standby device is not yet in the HOT state. — The active or standby device’s unit ID is wrong. — The ISSU process is not in the INIT state. — The active or standby image does not exist in flash memory. — The active and standby image names are not the same. — The configuration register value is not 0x2102. Recommended Action Correct the error condition and retry the command.


777


Error Message %ISSU_PROCESS-3-NVRAM: [chars] Explanation NVRAM variables are not set properly. Recommended Action The ISSU commands or the hardware module command did not set the

variables properly. Fix the error and retry the command.

Error Message %ISSU_PROCESS-3-PARAMETERS: [chars] ([chars]) parameters are wrong Explanation The system could not be configured for ISSU. Recommended Action Fix the error and retry the command.

Error Message %ISSU_PROCESS-3-PEER: %s Explanation The ISSU process cannot continue with negotiation because it cannot verify the peer’s

state. Recommended Action Make sure the peer is present and try again. If the problem persists, copy the

message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show version, and show issu state commands and your pertinent troubleshooting logs.

Error Message %ISSU_PROCESS-3-PRST: %s Explanation The specified persistent variables are not set properly. Recommended Action Check the ISSU commands and the hw-module command to determine

whether the specified variables are set properly.

Error Message %ISSU_PROCESS-3-RF: [chars] [ [chars] ] Explanation The ISSU process RF client had an error. Recommended Action Copy the message exactly as it appears on the console or in the system log.



778


Error Message %ISSU_PROCESS-3-ROLLBACK_TIMER: [chars] Explanation The rollback timer could not be configured. Recommended Action Fix the error and retry the command.

Error Message %ISSU_PROCESS-3-RUNVERSION: issu runversion; %s Explanation The ISSU runversion command did not execute because one of the following

conditions was not met: — The standby device is not in the RF STANDBY HOT state. — The current ISSU state is not LoadVersion. — The primary version image does not exist in the active supervisor’s ROMMON. — The configuration register value is not 0x2102. — The ISSU state could not be set to RunVersion. Recommended Action Correct the error condition and retry the command.

Error Message %ISSU_PROCESS-3-SYSTEM: [chars] Explanation The system could not be configured for ISSU. Recommended Action Correct the error condition and retry the command.

Error Message %ISSU_PROCESS-3-TRANSFORM: [chars] [ [chars] ] Explanation The ISSU process transform utility had an error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ISSU_PROCESS-3-UAM: %s Explanation An unexpected return code failure was received from the Upgrade Analysis Module

(UAM). Recommended Action Copy the message exactly as it appears on the console or in the system log.



779

ISSU_PROXY Messages


ISSU_PROCESS-7 Error Message %ISSU_PROCESS-7-DEBUG: %s Explanation This message displays debug commands for the ISSU process. The system is attempting

to recover from an unknown error. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show logging commands and your pertinent troubleshooting logs.

ISSU_PROXY Messages This section contains ISSU proxy messages.

ISSU_PROXY-3 Error Message %ISSU_PROXY-3-ISSU_PROXY_TIMEOUT: ICC Timed Out after waiting for %dsecs. Explanation The ISSU proxy on the route processor initiated an asynchronous intercard

communication (ICC) call to the switch processor to perform an ISSU command. This call did not return within the wait period. Recommended Action Copy the message exactly as it appears on the console or in the system log.



780

IXP_MAP Messages

IXP_MAP Messages This section contains ESF network processor client mapper (IXP_MAP) messages.

IXP_MAP-3 Error Message %IXP_MAP-3-ATOM: [chars] error detected: [chars] [chars] [hex] [hex] Explanation A software programming error for the ATOM ESF network processor client mapper was

detected. Recommended Action This software programming error is not considered fatal to the operation of the

ESF network processors. The software is designed to detect and report the error condition. If the error persists, reset the affected device. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %IXP_MAP-3-DROP_BLOCK: [chars] error detected - [hex] [hex] [dec] [dec] Explanation An error was detected during the processing of ESF network processor drop block

allocations. Recommended Action This is a software programming error. Copy the message exactly as it appears

on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %IXP_MAP-3-EXMEM: [chars] [chars] error detected - [chars] ([dec]) Explanation An error was detected managing the external memory of a network processor. Recommended Action This is a software programming error. Copy the message exactly as it appears

on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at


781

IXP_MAP Messages


Error Message %IXP_MAP-3-HQF: [chars] error detected: [chars] [chars] [hex] [hex] Explanation A software programming error for the HQF ESF network processor client mapper was

detected. Recommended Action This software programming error is not considered fatal to the operation of the ESF network processors. The software is designed to detect and report the error condition. If the error persists, reset the affected device. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %IXP_MAP-3-INITFAIL: Initialization Failed - [chars]: [chars] [chars] Explanation Memory needed to service one or more network processors could not be initialized. Recommended Action Try to reload the Cisco IOS image on the affected card or platform. If the error persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %IXP_MAP-3-INTF: [chars] error detected: [chars] [chars] [hex] [hex] Explanation A software programming error for the interface ESF network processor client mapper

was detected. Recommended Action This software programming error is not considered fatal to the operation of the ESF network processors. The software is designed to detect and report the error condition. If the error persists, reset the affected device. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying


782

IXP_MAP Messages

information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %IXP_MAP-3-LOCK_BLOCK: [chars] error detected - [hex] [dec] [dec] [dec] Explanation An error was detected during the processing of ESF network processor lock bit



Error Message %IXP_MAP-3-LOCK_LIST: [chars] error detected - [hex] [dec] [dec] [dec] Explanation An error was detected during the processing of ESF network processor lock bit



Error Message %IXP_MAP-3-MAXEXCEED: ESF NP Mapper Max Services Exceeded - [chars]: [chars] [dec] Recommended Action Change the configuration to reduce the number of services configured. If the

error persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at


783

IXP_MAP Messages


Error Message %IXP_MAP-3-MPLSOGRE: [chars] error detected: [chars] [chars] [hex] [hex] Explanation A software programming error for the MPLSOGRE ESF network processor client

mapper was detected. Recommended Action This software programming error is not considered fatal to the operation of the ESF network processors. The software is designed to detect and report the error condition. If the error persists, reset the affected device. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %IXP_MAP-3-NOMEM: Memory Allocation Failure - [chars] : [chars]([hex]) Explanation Memory required to service one or more network processors could not be allocated. Recommended Action This error may indicate that more memory must be installed on the affected

card or platform to service all the features and related entities enabled by the configuration. Attempt to reload the Cisco IOS image on the affected card or platform. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %IXP_MAP-3-NOMEM_S: Memory Allocation Failure - [chars]: [chars] [chars] Explanation Memory required to service one or more network processors could not be allocated. Recommended Action This error may indicate that more memory must be installed on the affected

card or platform to service all the features and related entities enabled by the configuration. Attempt to reload the Cisco IOS image on the affected card or platform. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages,


784

IXP_MAP Messages

these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %IXP_MAP-3-NOTFOUND: ESF NP Client Mapper - [chars]: [chars] [hex] Explanation The ESF network processor client mapper could not locate a required software element. Recommended Action Try to reload the Cisco IOS image on the affected card or platform. If the error persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %IXP_MAP-3-NPUNKNOWN: Unsupported NP - [chars]: [chars] [chars] Explanation An unsupported network processor has been detected. Recommended Action Verify that the correct Cisco IOS image is loaded on the affected card or

platform for the configured features. If the error persists, Recommended Action Verify that the correct Cisco IOS image is loaded on the affected card or

platform for the configured features. If the error persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %IXP_MAP-3-QOS: [chars] error detected: [chars] [chars] [hex] [hex] Explanation A software programming error for the QOS ESF network processor client mapper was


ESF network processors. The software is designed to detect and report the error condition. If the error persists, reset the affected device. Copy the message exactly as it appears on the console or in


785

IXP_MAP Messages

the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %IXP_MAP-3-QOS_CONFIG: [chars] error detected: [chars] [chars] [hex] [hex] Explanation A configuration error for the QoS ESF network processor client mapper was detected. This configuration error is not considered fatal to the operation of the ESF network processors. The software is designed to detect and report the error condition. Recommended Action Change the configuration to correct the QoS ACL configuration problem. If the

condition persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %IXP_MAP-3-STATS_BLOCK: [chars] error detected - [hex] [hex] [dec] [dec] [dec] Explanation An error was detected during the processing of ESF network processor statistics block




786

IXP_MAP Messages

Error Message %IXP_MAP-4-STUCK: Client ID([hex], [hex]) not ready on [chars] Explanation During reset of the ESF network processor, one or more network processor clients had

not completed stop processing. Recommended Action The system should still operate normally, however, statistics or state collected before the ESF network processor was reset may have been lost. If the error persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %IXP_MAP-3-TTFIB: [chars] error detected: [chars] [chars] [hex] [hex] Explanation A software programming error for the VPLS ESF network processor client mapper was



Error Message %IXP_MAP-3-VPLS: [chars] error detected: [chars] [chars] [hex] [hex] Explanation A software programming error for the VPLS ESF network processor client mapper was




787

IXP_MAP Messages

Error Message %IXP_MAP-3-WRED: [chars] error detected: [chars] [chars] [hex] [hex] Explanation A software programming error for the WRED ESF network processor client mapper was

detected. Recommended Action This software programming error is not considered fatal to the operation of the ESF network processors. The software is designed to detect and report the error condition. If the error persists, reset the affected device. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

IXP_MAP-4 Error Message %IXP_MAP-4-IPC_FAIL: ESF IPC Command failed - [chars] NP=[chars] (cmd=[dec] me=[dec] rc=[dec]) Explanation An IPC command sent to the ESF network processor has failed. Recommended Action This error indicates a possible problem with the network processor hardware

or microcode. Reload the affected hardware to clear the condition. If the error persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %IXP_MAP-4-QUEUE_LIMIT_EXCEED: Warning: Line card default queue-limit exceeds the maximum transmit packet buffers ([dec]). To ensure high priority traffic is not dropped, apply a QOS policy on each interface and adjust the queue-limit so that the total of the queue-limits on this line card is less than the maximum transmit packet buffers. Explanation An error for the HQF ESF network processor client mapper was detected. The total of

the default queue imits exceeds the maximum transmit packet buffers for this line card. Under high-traffic conditions, the line card may run out of packet buffers and drop high-priority traffic. Recommended Action This configuration error is not considered fatal to the operation of the ESF

network processors. The software is designed to detect and report the error condition. Apply the QoS policy configuration in the output direction of each interface. Adjust the queue limit so that the total of the queue limits on this line card is less than the maximum transmit packet buffers. If this message


788

KEYMAN Messages

recurs, copy the message exactly as it appears on the console or in the system log. Enter the show policy-map interface command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

KEYMAN Messages This section contains key string encryption (KEYMAN) messages.

KEYMAN-4 Error Message %KEYMAN-4-KEYSTR_BAD_CRYPTO: Bad encrypted keystring for key id [dec]. Explanation The system could not successfully decrypt an encrypted key string. The key string may

have been corrupted during system configuration. Recommended Action Reenter the key string command, and reconfigure the key string.

Error Message %KEYMAN-4-KEYSTR_CRYPTO_TYPE: Type [dec] encryption unknown. Interpreting keystring as literal Explanation The system does not recognize the format type. A key string format type value of 0

(unencrypted key string) or 7 (hidden key string), followed by a space, can precede the actual key string to indicate its format. An unknown type value will be accepted, but the system will consider the key string as being unencrypted. Recommended Action Use the correct format for the value type or remove the space following the

value type.


789

KEYSTORE_SP Messages

KEYSTORE_SP Messages This section contains keystore (KEYSTORE) messages.

KEYSTORE_SP-3 Error Message %KEYSTORE_SP-3-HW_BAD_EEPROM_ERR: Bad EEPROM cell reported in hardware keystore. Explanation A cell in the keystore EEPROM has failed. Write operations are not producing correct

results. Recommended Action Report this error to your Cisco technical support representative and arrange to have the hardware keystore on the supervisor card replaced.

LANMGR Messages Error Message %LANMGR-4-BADRNGNUM: Ring number mismatch on [chars], shutting down the interface Explanation The router detected a conflict in assigned ring numbers for the specified Token Ring.

The Ring Parameter Server (RPS) function was shut down to prevent potentially incorrect information from being sourced onto the ring. Recommended Action Check all bridges connected to this Token Ring and ensure that they are using the same assigned ring number.

L2 Messages This section contains Layer 2 (L2) messages.

L2-3 Error Message L2-3-DUP_REG: L2 Forwarding Engine: [chars] Attempt to program duplicate MAC address Explanation There was an attempt to program a duplicate MAC address in the match registers.

[chars] indicates the source of the attempt. Recommended Action Copy the message exactly as it appears on the console or in the system log.



790

L2_AGING Messages


L2_AGING Messages This section contains Layer 2 aging (L2_AGING) messages.

L2_AGING-2 Error Message %L2_AGING-2-DEC_EN_FAIL: Failed to initialize Distributed EtherChannel Explanation One or more resources that are required for the distributed EtherChannel operation are

in use. Recommended Action Remove the monitor session reserved for service modules by entering the no

monitor session service module command, and then try to reinitialize the operation.

Error Message %L2_AGING-2-MALLOC_FAIL: [chars]: Failed to allocate memory for bitlist Explanation There was no memory available to create the bit list. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %L2_AGING-2-SIG_INST_FAIL: [chars]: Failed to install signal handler Explanation A signal handler could not be installed for a process that involves Layer 2 aging. Recommended Action Copy the message exactly as it appears on the console or in the system log.



791

L2_APPL Messages


L2_APPL Messages This section contains Layer 2 application (L2_APPL) messages.

L2_APPL-0 Error Message %L2_APPL-0-TASK_SPAWN_FAIL: Failed to spawn task "[chars]" Explanation The specified initializing task failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


L2_APPL-4 Error Message %L2_APPL-4-MAC_MOVE: Host [enet] is flapping between port [chars] and port [chars] Explanation A host is going up and down between ports. Recommended Action Examine the network for possible loops.

Error Message %L2_APPL-4-MAC_USAGE: MAC usage is currently [dec]% Explanation MAC usage is exceeded for the Layer 2 monitoring feature. Recommended Action No action is required.


792

L2_ASIC Messages

Error Message %L2_APPL-4-UNKMESG: Unknown received message [dec] Explanation An internal error occurred. There might be a mismatch between image versions. Recommended Action Copy the message exactly as it appears on the console or in the system log.


L2_ASIC Messages This section contains Layer 2 forwarding engine messages.

L2_ASIC-0 Error Message %L2_ASIC-0-FATAL_INTR: L2 Forwarding Engine: fatal interrupt: int status [hex], int mask [hex] Explanation Critical interrupts indicate that EARL may no longer be functioning. Recommended Action Copy the message exactly as it appears on the console or in the system log.


L2_ASIC-1 Error Message %L2_ASIC-1-SCP_Q_CREATE_FAIL: Failed to create L2 Forwarding Engine SCP queue Explanation SCP queue creation has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



793

L2_ASIC Messages


Error Message %L2_ASIC-1-TASK_CREATE_FAIL: Failed to create L2 Forwarding Engine fatal interrupt patch task Explanation A task creation failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %L2_ASIC-1-THRO_RES_ALLOC_FAIL: Failed to allocate throttle resource Explanation Throttle resource allocation has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


L2_ASIC-2 Error Message %L2_ASIC-2-L2L3_SEQ_ERR: L2 Seq #[hex], L3 Seq #[hex], L2L3 Mismatch seq #[hex] Explanation A Layer 2 forwarding engine Layer 2-to-Layer 3 sequence error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



794

L2_ASIC Messages


Error Message %L2_ASIC-2-PARITY_ERR: L2 Forwarding Engine: parity intr #[dec]: address [hex], Data: [hex], [hex], [hex], [hex] Explanation A parity error was detected while accessing the forwarding table. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %L2_ASIC-2-RESET_LC: Resetting the linecard [dec]. Error code [dec] Explanation Failed to receive an SCP response or received a response with a status of not-ok. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %L2_ASIC-2-SEQ_ERR: [chars] seq. error: Seq #[hex], Intr. status #[hex], Cntrl1 #[hex], Cntrl2 #[hex] Explanation A Layer 2 forwarding engine sequence error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



795

L2_ASIC Messages


L2_ASIC-4 Error Message %L2_ASIC-4-INV_MSG: Received [chars] message from slot [dec] Explanation A message was received from an invalid line card. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %L2_ASIC-4-INV_REG: L2 Forwarding Engine: Attempt to [chars] invalid register Explanation An internal error has occurred. An attempt was made to read or write to an invalid

Layer 2 forwarding engine register. Recommended Action Copy the message exactly as it appears on the console or in the system log.



796

L2TP Messages

L2TP Messages This section contains Layer 2 Tunneling Protocol (L2TP) messages.

L2TP-3 Error Message %L2TP-3-CRITICAL: %s Explanation An critical event was processed by the Layer 2 Tunneling Protocol (L2TP) subsystem. Recommended Action No action is required.

Error Message %L2TP-3-ILLEGAL: %s: %s Explanation An illegal event was processed by the Layer 2 Tunneling Protocol (L2TP) subsystem. Recommended Action No action is required.

L2TP-5 Error Message %L2TP-5-IGNOREICMPMTU: Ignoring received ICMP Type 3 Code 4, due to pmtu min or max setting Explanation An ICMP Type 3 Code 4 packet has been received, indicating that fragmentation is

needed, but the ’don’t fragment’ (DF) bit is set. This packet has specified a next-hop MTU that is smaller or greater than the current minimum or maximum path MTU discovery MTU value. The ICMP packet was ignored and the MTU has not been changed. Recommended Action To allow the ICMP packet to be accepted and used to decrease or increase the

MTU, enter the vpdn pmtu min command to decrease the minimum MTU allowed and enter the vpdn pmtu max command to increase the maximum MTU that is allowed. The minimum value specified is the minimum MTU that is allowed, and the maximum value specified is the maximum MTU that is allowed.


797

L2TUN Messages

L2TUN Messages This section contains Layer 2 Tunneling Protocol (L2TUN) messages.

L2TUN-3 Error Message %L2TUN-3-ILLEGAL: %s Explanation An illegal event was processed by the Layer 2 Tunneling (L2TUN) subsystem. Recommended Action No action is required.

L2_MMC Messages This section contains Layer 2 MAC move counter (L2_MMC) messages.

L2_MMC-3 Error Message %L2_MMC-3-TASK_SPAWN_FAIL: L2 MMC process cannot be created Explanation The Layer 2 MAC move counters (MMC) process cannot be created. Recommended Action Copy the message exactly as it appears on the console or in the system log.


L2_MMC-4 Error Message %L2_MMC-4-MMC_FIRST: MAC Move(s) are detected Explanation The feature is enabled and the first MAC move(s) have been detected. Recommended Action Copy the message exactly as it appears on the console or in the system log.



798

L3_ASIC Messages


Error Message %L2_MMC-4-MMC_MAX: Maximum limit for MAC move counters exceeded for vlan %d Explanation The maximum limit has been exceeded for MAC move counters (MMC) on the specified

VLAN. Recommended Action Copy the message exactly as it appears on the console or in the system log.


L3_ASIC Messages This section contains Layer 3 CEF engine messages.

L3_ASIC-1 Error Message %L3_ASIC-1-ERR_NF_PARITY: Netflow table parity error can’t be fixed by software. Explanation NetFlow table parity errors are too many to be fixed by software. Recommended Action Reload the system. If the messages continue for the same module after a reload, contact your Cisco technical support representative and provide the output of the show module command to obtain a replacement for that module.

L3_ASIC-4 Error Message %L3_ASIC-4-ERR_INTRPT: Interrupt [chars] occurring in L3 CEF Engine. Explanation An error interrupt is occurring for the Layer 3 CEF engine. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show earl status command on the consoles of the switch supervisor and any DFC-enabled line cards to gather data that may help identify the cause of the error. Research and attempt to resolve


799

L3_COMMON Messages

the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

L3_COMMON Messages This section contains Layer 3 common ISSU messages.

L3_COMMON-3 Error Message %L3_COMMON-3-ERROR: %s Explanation An error has occurred in the Layer 3 in-service software upgrade (ISSU) process. Recommended Action Copy the message exactly as it appears on the console or in the system log.


L3_MGR Messages This section contains Layer 3 manager messages.

L3_MGR-3 Error Message %L3_MGR-3-ERROR: %s: %s Explanation An error has occurred in the Layer 3 in-service software upgrade (ISSU) process. Recommended Action Copy the message exactly as it appears on the console or in the system log.



800

L3_MGR_ISSU Messages


L3_MGR_ISSU Messages This section contains Layer 3 in-service software upgrade (ISSU) manager messages.

L3_MGR_ISSU-3 Error Message %L3_MGR_ISSU-3-ERROR: %s: %s Explanation An error has occurred in the Layer 3 ISSU manager process. Recommended Action Copy the message exactly as it appears on the console or in the system log.


L3MM Messages This section contains Layer 3 Mobility Manager (L3MM) messages.

L3MM-4 Error Message %L3MM-4-AP_DB_ADD: Failed to add AP to DB { AP: [enet], [IP_address]} Explanation The L3MM failed to add the entry for the specified access point (AP) into the AP




801

L3MM Messages


Error Message %L3MM-4-AP_DB_DEL: Failed to delete AP from DB { AP: [enet], [IP_address]} Explanation The L3MM failed to delete the entry for the specified AP from the AP database. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %L3MM-4-DUP_AP_IPADDR: AP [enet] is requesting ip [IP_address] which is being used by another AP Explanation The L3MM detected that an access point requested an IP address that is being used by

another access point in the network. Recommended Action Change the IP address of one of the two access points.

Error Message %L3MM-4-DUP_IPADDR: MN [enet] is requesting ip [IP_address] which is being used by MN [enet] Explanation The L3MM detected that a mobile node requested an IP address that is being used by

another mobile node in the network. Recommended Action Change the IP address of one of the two mobile nodes.

Error Message %L3MM-4-INIT_FAIL: Initialization failure; reason: [chars] Explanation The L3MM failed to initialize due to the specified reason. Recommended Action Copy the message exactly as it appears on the console or in the system log.



802

L3MM Messages

Error Message %L3MM-4-MALLOC_FAIL: Memory allocation failure [chars] Explanation The L3MM failed to allocate memory that was needed to perform an operation or to respond to an event. Recommended Action Increase the memory on the router processor of the supervisor engine.

Error Message %L3MM-4-MN_IPDB_ADD: Failed to add MN to MN DB { MN: [enet], [IP_address]} Explanation The L3MM failed to add the entry for the specified mobile node into the mobile node

IP database. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %L3MM-4-MN_IPDB_DEL: Failed to delete MN from IP DB { MN: [enet], [IP_address]} Explanation The L3MM failed to delete the entry for the specified mobile node from the mobile node

IP database. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %L3MM-4-MN_MACDB_ADD: Failed to add MN to MAC DB { MN: [enet], AP: [IP_address] } Explanation The L3MM failed to add the entry for the specified mobile node into the mobile node MAC database. Recommended Action Copy the message exactly as it appears on the console or in the system log.



803

L3MM Messages


Error Message %L3MM-4-MN_MACDB_DEL: Failed to delete MN from MAC DB { MN: [enet], [IP_address], AP: [IP_address], WNID: [dec] } Explanation The L3MM failed to delete the entry for the specified mobile node from the mobile node

MAC database. Recommended Action Copy the message exactly as it appears on the console or in the system log.


L3MM-5 Error Message %L3MM-5-WLAN: Wireless LAN Module in slot [dec] is [chars] Explanation The L3MM detected a change in the state of the wireless LAN module in the specified

slot. If the module is now on line, the L3MM starts accepting access-point and mobile-node registrations from the WDS on the module. If the module is now off line, the L3MM purges all access points and mobile nodes received from the module. Recommended Action No action is required.

Error Message %L3MM-5-WLAN_COMM_ABORT: Communication with Wireless LAN Module in slot [dec] aborted ([chars]) Explanation The L3MM detected a communication failure with the wireless LAN module specified

in the error message above. The L3MM will respond by purging its access point and mobile node databases as if the module went offline. However, the module will not be reset by the L3MM. Recommended Action No action is required.


804

L3TCAM Messages

Error Message %L3MM-5-WLAN_PWR_DN: Wireless LAN Module in slot [dec] will be powered down, another module is already active Explanation The L3MM detected a wireless LAN module trying to come online, while another

module was already functional as the active wireless LAN module. The L3MM does not support more than one wireless LAN module on line in the chassis at a given time, which is why this module will be powered down. Recommended Action No action is required.

L3TCAM Messages This section contains Layer 3 TCAM Manager (L3TCAM) messages.

L3TCAM-3 Error Message %L3TCAM-3-SIZE_CONFLICT: [chars] requires enabling extended routing Explanation The TCAM entry has not been configured to enable extended routing. In order to

support this feature, it is required that the TCAM entry be configured to enable extended routing. Recommended Action Modify the Switch Database Management template so that the switch is enabled to support the 144-bit Layer 3 TCAM. Enter the sdm prefer extended-match, sdm prefer access extended-match, or sdm prefer routing extended-match global configuration command, then reload the switch by entering the reload privileged EXEC command.

Error Message %L3TCAM-3-TOO_MANY_VRF: Exceed the maximum number of VRF allowed Explanation The number of VPNs has exceeded the maximum number of VPNs that are allowed in

the VPN routing and forwarding table on this hardware platform. Recommended Action Reconfigure your switch to limit the number of VRFs. Do not define more than

seven VRFs when you are entering the ip vrf vrf-name command, with vrf-name being the name of the VRF instance, in global configuration mode.


805

LACP Messages

LACP Messages This section contains Link Aggregation Control Protocol (LACP) messages.

LACP-4 Error Message %LACP-4-MULTIPLE_NEIGHBORS: Multiple neighbors detected on %s Explanation The Link Aggregation Control Protocol (LACP) detected multiple neighbors on the

specified interface. Recommended Action Copy the message exactly as it appears on the console or in the system log.


LAPB Messages This section contains line card Link Access Procedure, Balanced (LAPB) messages.

Error Message %LAPB-2-NOBUF: Interface [chars], no buffer available to [chars] Explanation There was insufficient memory for the LAPB protocol engine to send a message. Recommended Action This message is acceptable if it occurs infrequently, because the LAPBprotocol

is designed to handle loss of frames. Frequent occurrences can cause disruption of service. The system can be configured to ease memory demands or, if conditions warrant, the system can be upgraded to a larger memory configuration.


806

LC Messages

LC Messages This section contains line card (LC) messages.

LC-2 Error Message %LC-2-BADSUBSLOT: Out of range Line Card slot [dec] Sub Module slot [dec] Explanation The software specified an out-of-range submodule slot. Recommended Action Copy the message exactly as it appears on the console or in the system log.


LC-3 Error Message %LC-3-LC_CHUNK: Unable to [chars] for Linecard Slot [dec] Explanation A memory shortage may exist. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LC-3-LC_QUEUE: Unable to [chars] for Linecard Slot [dec] Explanation A memory shortage may exist. Recommended Action Copy the message exactly as it appears on the console or in the system log.



807

LC_10G Messages


LC_10G Messages This section contains Hamptons 10G trunk card-related messages.

LC_10G-3 Error Message %LC_10G-3-ACCESS_FAIL: [chars] Access Fail Explanation A read or write operation to the line card redundancy controller (LRC) scratch pad

register has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LC_10G-3-AFOVR_ERR: Autofailover Error [chars] Explanation The optical switch has encountered an error during an autofailover operation. Recommended Action Copy the message exactly as it appears on the console or in the system log.



808

LC_10G Messages

Error Message %LC_10G-3-AFOVR_EVNT: Autofailover event occured [chars] Explanation An autofailover event has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LC_10G-3-CDL_HEC_ERR_THR: CDL HEC Errors threshold [chars] Explanation The threshold of allowable converged data link (CDL) header error control (HEC) errors

has been exceeded. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LC_10G-3-CRC_ERR_THR: CRC Errors threshold [chars] Explanation The threshold of allowable cyclic redundancy check (CRC) errors has been exceeded. Recommended Action Copy the message exactly as it appears on the console or in the system log.



809

LC_10G Messages

Error Message %LC_10G-3-ETH_DCC_LPBK_FAIL: EthernetDcc loopback Fail Explanation A loopback operation through the Ethernet backplane has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LC_10G-3-IDPROM_ACCESS_FAIL: Idprom Access Fail Explanation The IDPROM could not be read or checked. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LC_10G-3-INTERNAL_CRITICAL: [chars] Explanation A critical internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



810

LC_10G Messages

Error Message %LC_10G-3-INTERNAL_ERROR: [chars] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LC_10G-3-INT_LPBK_FAIL: Internal Card loopback Fail Explanation A loopback attempt that was internal to the card has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LC_10G-3-LASER_AUTO_SHUTDOWN: Auto Laser Shutdown [chars] Explanation The laser has been automatically shut down. Recommended Action Copy the message exactly as it appears on the console or in the system log.



811

LC_10G Messages

Error Message %LC_10G-3-LASER_BIAS_ALARM: Optic Laser Bias Alarm [chars] Explanation An error involving laser bias has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LC_10G-3-LASER_TEMP_ALARM: Optic Laser Temperature Alarm [chars] Explanation An error involving the temperature of the optics laser has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LC_10G-3-LASER_TX_FAULT: Optic Laser Transmit Fault [chars] Explanation An error involving optics laser transmission has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



812

LC_10G Messages

Error Message %LC_10G-3-LOSS_OF_LOCK: Transceiver Loss of Lock [chars] Explanation The transceiver has lost the lock onto the incoming signal. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LC_10G-3-LOSS_OF_SYNC: Transceiver Loss of Sync [chars] Explanation The transceiver has lost its frame synchronization. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LC_10G-3-LPBK_THRU_PSC_FAIL: loopback through PSC Fail Explanation A internal card loopback attempt through the processor and switch card (PSC) has




813

LC_10G Messages

Error Message %LC_10G-3-MIB_AFOVR_ERR_ALM: Optical Switch Error [chars] [chars] [chars] Explanation An optical switch error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LC_10G-3-MIB_AFOVR_EVNT_ALM: AutoFailover Event [chars] [chars] [chars] Explanation An autofailover event has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LC_10G-3-MIB_AUTO_LASER_SHUTDOWN: Auto Laser Shutdown [chars] [chars] [chars] Explanation The laser has been shut down. Recommended Action Copy the message exactly as it appears on the console or in the system log.



814

LC_10G Messages

Error Message %LC_10G-3-MIB_LASER_BIAS_ALM: Laser Bias Alarm [chars] [chars] [chars] Explanation An error involving trunk laser bias has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LC_10G-3-MIB_LASER_TEMP_ALM: Laser Temperature Alarm [chars] [chars] [chars] Explanation An error involving the temperature of the trunk laser has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LC_10G-3-MIB_LASER_TX_FLT_ALM: Laser Transmit Fault [chars] [chars] [chars] Explanation An error involving trunk laser transmission has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



815

LC_10G Messages

Error Message %LC_10G-3-MIB_LOSS_OF_LOCK_ALM: Loss of Lock [chars] [chars] [chars] Explanation A loss-of-lock event has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LC_10G-3-MIB_LOSS_OF_SYNC_ALM: Loss of Sync [chars] [chars] [chars] Explanation A loss-of-synchronization event has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LC_10G-3-SYML_ERR_THR: Symbol Errors threshold [chars] Explanation The threshold of allowable symbol errors has been exceeded. Recommended Action Copy the message exactly as it appears on the console or in the system log.



816

LC_2P5G Messages

LC_2P5G Messages This section contains Hamptons 2.6G trunk card-related messages.

LC_2P5G-3 Error Message %LC_2P5G-3-ACCESS_FAIL: Access Fail [chars] Explanation A read or write operation to the LRC scratch pad register has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LC_2P5G-3-AFOVR_ERR: Autofailover Error [chars] Explanation The optical switch failed to perform an autofailover operation. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LC_2P5G-5-AFOVR_EVNT: Autofailover event occured [chars] Explanation An autofailover event has occurred. Recommended Action No action is required.


817

LC_2P5G Messages

Error Message %LC_2P5G-3-CDL_HEC_ERR_THR: CDL HEC Errors threshold [chars] Explanation The threshold of allowable converged data link (CDL) header error control (HEC) errors

has been exceeded. Recommended Action Check that the cables connected to the Rx transciever are plugged in, are not

bent or twisted, and are in good condition. Check the physical state (transmit laser power level) and configuration of the remote end connected to the port associated. If the error message persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %LC_2P5G-3-CRC_ERR_THR: CRC Errors threshold [chars] Explanation The threshold of allowable CRC errors has been exceeded. Recommended Action Check that the cables connected to the Rx transciever are plugged in, are not


Error Message %LC_2P5G-3-ETH_DCC_LPBK_FAIL: EthernetDcc loopback Fail [chars] Explanation A loopback operation through the Ethernet backplane has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



818

LC_2P5G Messages

Error Message %LC_2P5G-3-IDPROM_ACCESS_FAIL: Idprom Access Fail [chars] Explanation The IDPROM could not be read or checked. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LC_2P5G-2-INTERNAL_CRITICAL: [chars] Explanation An internal critical error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LC_2P5G-3-INTERNAL_ERROR: [chars] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



819

LC_2P5G Messages

Error Message %LC_2P5G-3-INT_LPBK_FAIL: Internal Card loopback Fail [chars] Explanation A loopback operation that was internal to the card has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LC_2P5G-5-LASER_AUTO_SHUTDOWN: Auto Laser Shutdown [chars] Explanation The laser has been automatically shut down. Recommended Action No action is required.

Error Message %LC_2P5G-3-LASER_DEGRADATION_ALARM: Optic Laser Degradation Alarm [chars] Explanation The transmission power of the optics laser module is degrading. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LC_2P5G-3-LASER_NO_LIGHT_ALARM: Optic Laser Loss of Light Alarm [chars] Explanation The optics laser has experienced a loss of light. Recommended Action Copy the message exactly as it appears on the console or in the system log.



820

LC_2P5G Messages

Error Message %LC_2P5G-3-LASER_TX_FAULT: Optic Laser Transmit Fault [chars] Explanation An optics laser transmission fault has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LC_2P5G-3-LASER_WAVE_LN_DEV_ALARM: Optic Laser Wavelength Deviation Alarm [chars] Explanation The wavelength of the optics laser module has deviated. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LC_2P5G-3-LOSS_OF_LOCK: Transceiver Loss of Lock [chars] Explanation The receiver has lost the lock on the incoming signal. Recommended Action Check that the cables connected to the Rx transciever are plugged in, are not



821

LC_2P5G Messages

Error Message %LC_2P5G-3-LOSS_OF_SYNC: Transceiver Loss of Sync [chars] Explanation The decoder has lost its frame synchronization. Recommended Action Check that the cables connected to the Rx transciever are plugged in, are not


Error Message %LC_2P5G-3-LPBK_THRU_PSC_FAIL: loopback through PSC Fail [chars] Explanation An internal card loopback operation through the processor and switch card (PSC) has



Error Message %LC_2P5G-3-MIB_AFOVR_ERR_ALM: Optical Switch Error [chars] [chars] [chars] Explanation An autofailover operation for the optical switch has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



822

LC_2P5G Messages

Error Message %LC_2P5G-5-MIB_AFOVR_EVNT_ALM: AutoFailover Event [chars] [chars] [chars] Explanation An autofailover event has occurred. Recommended Action No action is required.

Error Message %LC_2P5G-5-MIB_AUTO_LASER_SHUTDOWN: Auto Laser Shutdown [chars] [chars] [chars] Explanation The laser has been automatically shut down. Recommended Action No action is required.

Error Message %LC_2P5G-3-MIB_CVRD_ERR_THR: CVRD Error Threshold Exceeded [chars] [chars] [chars] Explanation The threshold of allowable symbol errors has been exceeded. Recommended Action Check that the cables connected to the Rx transciever are plugged in, are not


Error Message %LC_2P5G-3-MIB_LASER_DEG_ALM: Laser Degradation Alarm [chars] [chars] [chars] Explanation The transmission power of the optics laser module is degrading. Recommended Action Copy the message exactly as it appears on the console or in the system log.



823

LC_2P5G Messages

Error Message %LC_2P5G-3-MIB_LASER_TX_FLT_ALM: Laser Transmit Fault [chars] [chars] [chars] Explanation An optics laser transmission fault has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LC_2P5G-3-MIB_LASER_WV_DEV_ALM: Laser Wavelength Deviation Alarm [chars] [chars] [chars] Explanation The wavelength of the optics laser module has deviated. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LC_2P5G-3-MIB_LOSS_OF_LOCK_ALM: Loss of Lock [chars] [chars] [chars] Explanation The receiver has lost its lock on the incoming signal. Recommended Action Check that the cables connected to the Rx transciever are plugged in, are not



824

LC_2P5G Messages

Error Message %LC_2P5G-3-MIB_LOSS_OF_SYNC_ALM: Loss of Sync [chars] [chars] [chars] Explanation The decoder has lost its frame synchronization. Recommended Action Check that the cables connected to the Rx transciever are plugged in, are not

bent or twisted, and are in good condition. Check the physical state (transmit laser power level) and configuration of the remote end connected to the port associated. If the error message persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs..

Error Message %LC_2P5G-3-MIB_NO_LIGHT_ALM: Laser Loss of Light Alarm [chars] [chars] [chars] Explanation An error involving a loss of light for the optics laser has occurred. Recommended Action Check that the cables connected to the Rx transciever are plugged in, are not


Error Message %LC_2P5G-3-SYML_ERR_THR: Symbol Errors threshold [chars] Explanation The threshold of allowable symbol errors has been exceeded. Recommended Action Check that the cables connected to the Rx transciever are plugged in, are not



825

LCMDC Messages

LCMDC Messages This section contains Cisco Optical Networking Systems (ONS) 15540 Extended Services Platform (ESP) messages.

LCMDC-3 Error Message %LCMDC-3-FPGA_ACCESS_FAIL: Alarm: [chars], [chars], [chars], [chars], [chars] Explanation An alarm has occurred. The message text provides additional details on the cause of the



LCMDC-6 Error Message %LCMDC-6-TX_ALARM_SOAK: [chars] Explanation An alarm has occurred. The message text provides additional details on the cause of the




826

LCR Messages

LCR Messages This section contains Line Card Registry (LCR) messages.

LCR-6 Error Message %LCR-6-FAILED_MCAST: Failed to send exported registry request %d to mcast group Explanation A communication failure occurred while attempting to send an exported registry request

to a multicast group. Recommended Action No action is required.

Error Message %LCR-6-FAILEDRCV: Failed to process registry request [dec] Explanation A request received on a receiver could not be processed successfully. Recommended Action No action is required.

Error Message %LCR-6-FAILED_RCV_ON_ACTIVE: Failed to process registry request [dec] - on active supervisor SP Explanation A request received on the active supervisor engine could not be processed successfully. Recommended Action No action is required.

LDP Messages This section contains Label Distribution Protocol (LDP) messages.

LDP-3 Error Message %LDP-3-ISSU_XFORM: ISSU [chars] transformation failed for msg type ([dec])[chars]. Explanation The LDP could not upgrade or downgrade a checkpointing message. Recommended Action Copy the message exactly as it appears on the console or in the system log.



827

LDP Messages


Error Message %LDP-3-RECONNECT: [chars] Explanation An error occurred while parsing the incoming LDP initialization message. The FT

reconnect timer value received was greater than the locally-configured forwarding state holding timer value. Recommended Action Reconfigure the forwarding state holding timer value.

LDP-5 Error Message %LDP-5-CLEAR_CHKPT: Clear LDP bindings checkpoint state ([chars]) by [chars] Explanation The checkpoint state for one or more LDP bindings has been reset. Recommended Action No action is required.

Error Message %LDP-5-CLEAR_NBRS: Clear LDP neighbors ([chars]) by [chars] Explanation One or more LDP neighbor sessions has been reset. Recommended Action No action is required.

Error Message %LDP-5-GR: [chars] Explanation An informational LDP notice was generated for a graceful restart event. Recommended Action No action is required.

Error Message %LDP-5-SP: [chars] Explanation An informational LDP notice was generated for a session protection event. Recommended Action No action is required.


828

LFD Messages

LFD Messages This section contains MFI Label Switching Database (LFD) messages.

LFD-2 Error Message %LFD-2-AVL: [chars] [hex] Explanation An error involving an Adelson-Velskii and Landis (AVL) tree operation has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LFD-2-FPIHANDLER3: [chars] [hex] [hex] [hex] Explanation An error has been detected in the forwarding path identifier (FPI) handler. Recommended Action Copy the message exactly as it appears on the console or in the system log.


LFD-3 Error Message %LFD-3-BADEXEC: Unexpected Code Execution: [chars] [dec] Explanation An error involving unexpected execution of code has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



829

LFD Messages


Error Message %LFD-3-BADFRRTYPE: illegal frr type: [dec] Explanation An error involving an Fast ReRoute (FRR) request type has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LFD-3-BADLABELADD: Cannot add label - [chars]. Explanation Unable to create label due to reason given. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LFD-3-BADSHORTLABELADD: Cannot add short label: path_idx [dec], moi_type [dec] Explanation Unable to create MFI feature space in FIB entry, so unable to store short path extension

information there. Recommended Action Copy the error message exactly as it appears on the console or in the system



830

LFD Messages

Error Message %LFD-3-BROKERINITFAIL: Failed to initialise lte RP broker facility Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LFD-3-CHUNKMGR: chunk mgr: [chars] [hex] Explanation An error involving the memory manager has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LFD-3-CHUNKMGRALLOC: failed chunk alloc: [chars] Explanation An error involving memory allocation has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



831

LFD Messages

Error Message %LFD-3-CHUNKMGRDEALLOC: failed chunk dealloc: [chars] Explanation An error involving the freeing of memory has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LFD-3-EVTLOGBADSOURCE: Illegal log event source: [dec] Explanation An illegal event in the log buffer has been detected. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LFD-3-FIB_SRC: Lable [[dec]/[dec]] [chars] [chars] [chars] Explanation The FIB entry could not be sourced for label in question. Recommended Action Enter the show mpls forwarding-table internal and show ip route [vrf name] prefix commands and capture the error message traceback. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


832

LFD Messages

Error Message %LFD-3-FPIHANDLER: LFD SSS Handler: [chars] Explanation An error has been detected in the FPI handler. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LFD-3-FPITYPEWRONG: Require fpi type [chars], get fpi type [chars] Explanation An error involving unmatched FPI types has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LFD-3-INTFDB: intf db: [chars] [hex] Explanation An interface DB error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



833

LFD Messages

Error Message %LFD-3-INTFDB2: intf db: [chars] [hex] [hex] Explanation An interface DB error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LFD-3-INVINSTALLER: Wrong installer [dec] for [chars] [dec]/[dec] update (was [dec]) Explanation The rewrite ID is invalid for non-IP label table entry. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LFD-3-INVIPLABELTYPE: Wrong label type [dec] for IP Label [dec], table [dec] prefix [chars], vrf [chars] Explanation The label type is invalid for the indicated label table entry. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show running-config command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show running-config commands and your pertinent troubleshooting logs.


834

LFD Messages

Error Message %LFD-3-INVLABELTYPE: Wrong label type [dec] for non-ip LTE [dec]/[dec] Explanation The label type is invalid for the non-IP label table entry. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LFD-3-INVLABELUPDTYPE: Wrong label type [dec] for label [dec] table [dec] [chars] [chars] Explanation An invalid label type was encountered during the specified operation. Recommended Action Enter the show mpls forwarding-table label label internal command and

capture the error message traceback. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %LFD-3-INVPATHLBL: [chars] [chars] Explanation An invalid outgoing label is attached to the prefix. Recommended Action Copy the message exactly as it appears on the console or in the system log.



835

LFD Messages

Error Message %LFD-3-INVPLIST: Wrong path list type [dec] for label [dec]/[dec] [chars] Explanation The path list type is set incorrectly for the label in question. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LFD-3-INVRWID: Wrong rwid [dec] for non-ip LTE [dec]/[dec] Explanation The rewrite ID is invalid for non-IP label table entry. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LFD-3-INVXDRLEN: Length [int] for [chars] field in LTE msg for [chars] Explanation An error occurred when encoding the MPLS label information for the FEC in question.

This could result in line cards having stale labels for this FEC. Recommended Action Copy the message exactly as it appears on the console or in the system log.



836

LFD Messages

Error Message %LFD-3-KEY_DB_INSERTFAIL: [chars], entry [hex], existing [hex] Explanation The element could not be inserted into the LFD’s key database. Recommended Action Enter the show mpls forwarding-table label label internal command and

capture the error message traceback. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %LFD-3-LCXDRCLIENT: LTE distribution client: [chars] Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LFD-3-LTABLEMEM: Cannot allocate new mpls table [dec] of size [dec] needed for entry [dec] Explanation There is not enough contiguous memory for the MPLS forwarding table. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message %LFD-3-NONIPINFO: Non-ip info: [chars] Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



837

LFD Messages


Error Message %LFD-3-NOOCE: Attempt to get labels from OCE failed - [chars]. Explanation The calling function has provided insufficient information to get labels. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LFD-3-NORESOURCE: [chars] [dec] Explanation A resource failure occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LFD-3-NULLADJACENCY: NULL Adjacency Explanation A NULL adjacency was encountered. Recommended Action Copy the message exactly as it appears on the console or in the system log.



838

LFD Messages

Error Message %LFD-3-NULLFIBIDB: NULL FIB IDB: [chars] [dec] Explanation A NULL FIB IDB was encountered. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LFD-3-ORPHANLTE: Label [dec]/[dec], plist [dec], LDM: [hex] Explanation The LTE for the label was supposed to be deleted, but is still present. Recommended Action Collect the running configuration and the output of the show mpls

forwarding-table labels label-num command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %LFD-3-REWMGR: Rewrite Manager: [chars] [hex] Explanation An error involving the rewrite manager has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



839

LFD Messages

Error Message %LFD-3-REWMGR2: [chars] [hex] [hex] Explanation A rewrite lookup attempt has failed becuase of an inconsistency in the FPI. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LFD-3-RPXDRCLIENT: Invalid XDR Client: %s Explanation An internal software error occurred. The XDR client is invalid. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LFD-3-RUNNING_TIMER: [chars] [dec] [chars] [dec] Explanation The MPLS forwarding entry for the specified label was deleted prior to the expiry of its

associated timer. Recommended Action Enter the show mpls forwarding-table label label internal command. Copy



840

LFD Messages

Error Message %LFD-3-SM: [chars] [dec] Explanation An error involving the state machine has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LFD-3-SMBADEVENT: Unexpected event [chars] for state [chars] Explanation The LFD received an unexpected event for its state. The state of the LFD, and the

unexpected event, are specified in the message text. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LFD-3-UNSUPPORTED_XDR: [chars] Explanation Decoding of an XDR message revealed data or a format that is unsupported in the

current release. Recommended Action Copy the message exactly as it appears on the console or in the system log.



841

LFD Messages

Error Message %LFD-3-UPDATEHANDLER2: [chars] [hex] [hex] Explanation An error involving the update handler has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LFD-3-UPDATEHANDLER3: [chars] [hex] [hex] [hex] Explanation An error involving the update handler has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LFD-3-UPDATEHANDLERFPI: No handler installed: fpi=[dec] handler type=[chars] Explanation No handler has been installed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



842

LFD Messages

Error Message %LFD-3-XDRBADMAGIC: xdr message for [chars] spilled out of allocated static storage Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


LFD-4 Error Message %LFD-4-NOFIBIDB: [chars] - ifnum [dec] Explanation The FIB IDB is missing on the line card. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %LFD-4-OWNCHANGED: Owner changed for [chars] [dec]/[dec] from [dec] to [dec] Explanation A label was previously installed by a different installer. Recommended Action Copy the message exactly as it appears on the console or in the system log.



843

LINEPROTO Messages

Error Message %LFD-4-UNSUPPORTEDRW: Unexpected rewrites seen where MPLS is not supported by platform for this slot Explanation MPLS is either not needed or not handled by the platform for this card and should not

handle rewrites. Recommended Action No action is required.

LFD-5 Error Message %LFD-5-FRRISSULOG: FRR is not ISSU compatible, notified by %s Explanation The ISSU negotiation results for Fast Reroute (FRR) are not compatible. Recommended Action Copy the message exactly as it appears on the console or in the system log.


LFD-6 Error Message %LFD-6-RESOURCE: [chars] Explanation MPLS is not supported by the platform. Recommended Action No action is required.

LINEPROTO Messages Error Message %LINEPROTO-SP-5-UPDOWN: Line protocol on Interface %s, changed state to %s Explanation The data link level line protocol changed state. Recommended Action Copy the message exactly as it appears on the console or in the system log.



844

LINK Messages


LINK Messages This section contains data link messages.

LINK-3 Error Message %LINK-3-BOGUSENCAP: Interface [chars], bad encapsulation in idb-enctype = [hex] Explanation A serial interface has been configured with an unknown encapsulation. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %LINK-3-FCS_ERROR: [chars] [chars] [chars] [chars] Explanation The FCS error rate exceeds the configured threshold. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LINK-3-LINK_FAULT: [chars] [chars] [chars] [chars] Explanation The link state for the port is down. Recommended Action Copy the message exactly as it appears on the console or in the system log.



845

LINK Messages


Error Message %LINK-3-TOOSMALL: Interface [chars], Output runt packet of [dec] bytes Explanation An output packet was detected that was smaller than the minimum allowable datagram

size. An error in another driver or an error in the system software probably triggered this error message. Recommended Action This is an informational message only. No action is required.

Error Message %LINK-3-UPDOWN: Interface [chars], changed state to [chars] Explanation The interface hardware has gone either up or down. Recommended Action If the state change was unexpected, confirm the configuration settings for the

interface.

LINK-6 Error Message %LINK-6-BERTMSGS: [chars] Explanation This message contains information related to a bit error rate test (BERT). Recommended Action Copy the message exactly as it appears on the console or in the system log.


LINK-SP Error Message %LINK-SP-3-UPDOWN: Interface %s, changed state to %s Explanation The interface hardware went either up or down. Recommended Action If the state change was unexpected, confirm the configuration settings for the

interface.


846

LLDP Messages

LLDP Messages This section contains Link Layer Discovery Protocol (LLDP) messages.

LLDP-4 Error Message %LLDP-4-LLDP_NEW_ENTRY: Neighbor record not committed - malloc failure Explanation An LLDP entry creation failed due to a memory allocation failure. Recommended Action Run memory diagnostics.

LRE_CPE Messages This section contains Long Reach Ethernet (LRE) Customer Premises Equipment (CPE) messages.

LRE_CPE-3 Error Message %LRE_CPE-3-INVALIDMODE: CPE on interface [chars] is in invalid mode [chars]. Explanation The CPE is in an inconsistent mode; for example, the model number may imply a MAC

mode while the CPE is in a PHY mode. Recommended Action Enter the show controllers lre cpe mfg command to verify that the CPE model

number string is correct. Enter the hw-module slot slot lre upgrade remote command to ensure that the CPE has the latest supported firmware. If the CPE’s model number and firmware are correct, enter the interface configuration shutdown command followed by the no shutdown command to force the switch to read the CPE information again. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


847

LRE_CPE Messages

Error Message %LRE_CPE-3-INVALIDPATCH: CPE on interface [chars] has invalid LRE firmware. Explanation The LRE firmware header does not have a valid signature, or the header information on

the specified firmware is inconsistent with the contents of the firmware Recommended Action Upgrade the firmware on the CPE to the latest supported one by using the

hw-module slot slot lre upgrade remote command.

Error Message %LRE_CPE-3-INVALIDPHY: CPE on interface [chars] has an unsupported Ethernet PHY. Explanation The Ethernet PHY device on the CPE attached to the specified interface is not

supported. This error occurs when the switch cannot recognize the PHY identifier of the PHY device(s) on the CPE. The reason could be one of the following: The Cisco IOS version running on the switch is not compatible with this CPE, the CPE is not supported by Cisco, or the switch did not correctly read the PHY identifier from the CPE. Recommended Action Verify that the CPE is supported by Cisco. Enter the command show

controllers lre cpe mfg to verify that the CPE model number string is correctly set. If the Cisco IOS version and CPE model number look correct, enter the interface configuration shutdown command followed by the no shutdown command to force the switch to read the PHY identifer again. As a last resort, power cycle the CPE. If the error persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %LRE_CPE-3-NOVERCKSUM: Could not fetch CPE firmware version and checksum on interface [chars]. Explanation The system could not obtain the CPE firmware version and checksum. If the CPE has

the latest firmware, and the CPE model number is correct, the most likely cause for this error is that the LRE link between the switch and the CPE is of poor quality. Recommended Action Enter the command show controllers lre cpe mfg to verify that the CPE model

number string is correctly set for this CPE. Enter the hw-module slot slot lre upgrade remote command to ensure that the CPE has the latest supported firmware. Enter the interface configuration shutdown command followed by the no shutdown command to force the switch to read the CPE firmware version and checksum. As a last resort, power cycle the CPE. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support


848

LRE_CPE Messages


Error Message %LRE_CPE-3-UNKNOWNMODEL: CPE has unrecognizable model number [chars] on interface [chars] Explanation The model number string in the CPE does not match a known CPE model number. Recommended Action Enter the command show controllers lre cpe mfg to examine the model

number of the CPE. Verify that the model number is supported by Cisco. Enter the interface configuration shutdown command followed by the no shutdown command to force the switch to read the CPE model number again. If the error message persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %LRE_CPE-3-WRONGAPPVER: CPE on interface [chars] reported unsupported version of application firmware [chars]. Minimum application firmware version needed [chars] Explanation Each CPE requires a currently supported application firmware version for it to function

correctly. This CPE has a application firmware version that predates the earliest supported version. Recommended Action Application firmware is not currently used on the CPE. This error message is

for future use.

Error Message %LRE_CPE-3-WRONGBOOTVER: CPE on interface [chars] reported unsupported version of bootloader firmware [chars]. Minimum bootloader firmware version needed [chars] Explanation Each CPE requires a currently supported bootloader firmware version for it to function

correctly. This CPE has a bootloader firmware version that predates the earliest supported version. Recommended Action Enter the hw-module slot slot lre upgrade remote command to upgrade the

bootloader firmware on the CPE to a recent version that supports the current requirements. If the CPE firmware upgrade does not solve the problem, enter the interface configuration shutdown command followed by the no shutdown command to force the switch to read the bootloader firmware version again. As a last resort power cycle the CPE. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support


849

LRE_LINK Messages


Error Message %LRE_CPE-3-WRONGPATCH: CPE on interface [chars] has wrong patch version [hex]. Patch version [hex] or higher is needed for this CPE. Explanation Each CPE requires a currently supported patch version for it to function. This CPE has

a patch version that predates the earliest supported version. This condition might occur because the switch was upgraded with the latest Cisco IOS software image, but the CPE firmware has not been upgraded. Recommended Action Enter the hw-module slot slot lre upgrade remote command to upgrade the

patch on the CPE to the latest supported version.

LRE_CPE-5 Error Message %LRE_CPE-5-SSNCHANGED: CPE unit on interface [chars] changed. Explanation The CPE system serial number has changed. This condition usually means that the CPE

unit on this interface was replaced. Recommended Action No action is required.

LRE_LINK Messages This section contains Long Reach Ethernet (LRE) link for the Catalyst 2950 LRE switch messages.

LRE_LINK-3 Error Message %LRE_LINK-3-PROFILE_FAILURE: Interface [chars], profile [chars] failure Explanation The interface specified in the error message did not achieve link with the attached

profile. Recommended Action If the link failure was unexpected, confirm the profile settings for the interface.

Error Message %LRE_LINK-3-UPDOWN: Interface [chars], changed state to [chars] Explanation The interface hardware has either become active (came up) or become inactive (gone

down). Recommended Action If the state change was unexpected, confirm the configuration settings for the

interface.


850

LRE_LOG Messages

LRE_LINK-4 Error Message %LRE_LINK-4-HEALTH_MON: Interface [chars], had crossed certain monitored thresholds Explanation The link status monitor for the specified interface has detected conditions that have

crossed the configured thresholds. Recommended Action Enter the show controllers lre link monitor command

to obtain more information on this error. If the change in operating conditions was unexpected, confirm the configuration settings for the interface.

LRE_LOG Messages This section contains Long Reach Ethernet (LRE) log messages.

LRE_LOG-7 Error Message %LRE_LOG-7-LRE_LOGGING: LRE Log:Interface [chars]: State: [chars], Event: [chars], Data: [chars]. Explanation The system has changed its state. The error message text provides more information on

the cause of the change. Recommended Action No action is required.

LRE_UPGRADE Messages This section contains LRE upgrade for the Catalyst 2950 LRE switch messages.

LRE_UPGRADE-2 Error Message %LRE_UPGRADE-2-LOCAL_LOAD_FAILURE: The system failed to load the firmware for local PHY controller:[dec] Explanation An internal system error has occurred while loading the firmware for a local PHY

controller. Recommended Action Power cycle the switch. If this message persists, copy the message exactly as

it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at


851

LRE_UPGRADE Messages


LRE_UPGRADE-3 Error Message %LRE_UPGRADE-3-INIT_SYSTEM: Upgrade module failed to initialize Explanation The LRE upgrade module failed to initialize. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LRE_UPGRADE-3-LOCAL_FAILURE: Upgrade of local controller [chars] failed Explanation The LRE upgrade is unable to download firmware to a local controller. Recommended Action Copy the message exactly as it appears on the console or in the system log.


LRE_UPGRADE-4 Error Message %LRE_UPGRADE-4-INIT_RESOURCE: [chars] Explanation The LRE upgrade module cannot locate a required resource. Recommended Action Copy the message exactly as it appears on the console or in the system log.



852

LSD Messages


Error Message %LRE_UPGRADE-4-TERMINATE: Upgrade on [chars] terminated Explanation The customer equipment was disconnected or changed in the middle of an upgrade. Recommended Action No action is required.

LSD Messages This section contains MPLS Forwarding Infrastructure (MFI) Label Switching Database (LSD) messages.

LSD-2 Error Message %LSD-2-APP_NOTSUPP: [chars] interface does not support app [chars] Explanation The interface does not support the application that is specified in the message. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LSD-2-AVL: [chars] [hex] Explanation An error involving an Adelson-Velskii and Landis (AVL) tree operation has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



853

LSD Messages


Error Message %LSD-2-FPIHANDLER: [chars] [hex] Explanation An error involving the FPI handler has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LSD-2-INVALID_VAR: [chars] Explanation The function has received invalid parameters. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LSD-2-INVALID_VAR2: [chars] [hex] [hex] Explanation The function has received invalid parameters. Recommended Action Copy the message exactly as it appears on the console or in the system log.



854

LSD Messages

Error Message %LSD-2-RESOURCE: [chars] Explanation A system resource error has occurred. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message %LSD-2-TESTAPP2: Test app error: [chars]: [hex] [hex] Explanation A test application error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


LSD-3 Error Message %LSD-3-APPMGR: [chars] [hex] Explanation An error involving the application manager has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LSD-3-BADEXEC: Unexpected Code Execution: [chars] [dec] Explanation An error involving unexpected execution of code has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



855

LSD Messages


Error Message %LSD-3-CHUNKMGR: chunk mgr: [chars] [hex] Explanation A memory manager error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LSD-3-CLIENT_CONN: [chars] Explanation A client connection error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LSD-3-CLIENT_CONN2: [chars] [hex] [hex] Explanation A client connection error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



856

LSD Messages

Error Message %LSD-3-EVTLOGBADSOURCE: Illegal log event source: [dec] Explanation An illegal event was found in the log buffer. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LSD-3-INTF_DB: [chars] Explanation An interface database error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LSD-3-INTF_DB2: [chars] [hex] [hex] Explanation An interface database error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



857

LSD Messages

Error Message %LSD-3-INVALID_PROC_EVT: Unexpected process event [dec] for pid [dec] Explanation The LSD component received an unexpected process event notification for the process

with the specified ID. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LSD-3-LABEL: [chars][dec] Explanation A label operation error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LSD-3-LABEL2: [chars] [hex] [hex] Explanation A label operation error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



858

LSD Messages

Error Message %LSD-3-MULTISERVICEREQ: Multiple outstanding service requests: [dec] [dec] Explanation A service request was submitted, but one service request is already outstanding. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LSD-3-OS_NOTIFY: Process id [dec] [chars], error code [dec] Explanation The LSD was unable to notify the operating system about (un)registration of the

specified process. Recommended Action Enter the show version, show running-config, show mpls infrastructure lsd apps commands. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %LSD-3-REWMGR: Rewrite Manager: [chars] [hex] Explanation An error involving the rewrite manager has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



859

LSD Messages

Error Message %LSD-3-REWMGR2: [chars] [hex] [hex] Explanation An attempt to look up a rewrite has failed because of an inconsistency in a forwarding

path identifier. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LSD-3-UPDATELISTMGR2: [chars] [dec] [dec] Explanation A general error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LSD-3-UPDATELISTMGREXEC: Illegal exec: [chars] [hex] Explanation An error involving illegal execution of code has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



860

LSD Messages

LSD-4 Error Message %LSD-4-BADAPI: [chars] from [chars] Explanation The LSD has received a message with invalid parameters. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LSD-4-LABELFREETO: requested free timeout ([int] ms) by [chars] limited to: [int] ms Explanation The timeout period for the MPLS application label has exceeded the maximum

configured time. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LSD-4-LABEL_RESOURCE: label range [dec]-[dec] exhausted Explanation The MPLS application is attempting to allocate more labels than the system

configuration will allow. Recommended Action Copy the message exactly as it appears on the console or in the system log.



861

LSD_CLIENT Messages

LSD_CLIENT Messages This section contains MPLS Forwarding Infrastructure (MFI) Label Switching Database (LSD) client messages.

LSD_CLIENT-2 Error Message %LSD_CLIENT-2-MSGHANDLERERR: Client=[dec] Msg type=[dec] Error=[chars] Explanation An error involving the message handler has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LSD_CLIENT-2-XDREXEC: [chars] [dec] Explanation Illegal code has been executed in the XDR path. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LSD_CLIENT-2-XDREXEC2: [chars] [hex] [hex] Explanation llegal code has been executed in the XDR path. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show running-config command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at


862

LSD_CLIENT Messages

http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show running-config commands and your pertinent troubleshooting logs.

LSD_CLIENT-3 Error Message %LSD_CLIENT-3-CLIENTAPI: Client API error: [chars] [dec] Explanation An unexpected client API error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LSD_CLIENT-3-INVALID_VAR: [chars] Explanation A function has received parameters that are invalid. Recommended Action Copy the message exactly as it appears on the console or in the system log.



863

LSD_CLIENT Messages

Error Message %LSD_CLIENT-3-ISSU_MSG_CONV: [chars] [dec] [dec] Explanation Could not convert received message type to a known message. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LSD_CLIENT-3-PCHUNK2: [chars]: [chars] [hex] [hex] Explanation An error involving memory parameters has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show version, show running-config and show process memory commands and your pertinent troubleshooting logs.

Error Message %LSD_CLIENT-3-UTIL2: [chars]: [hex] [hex] Explanation An error involving utilities has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show version and show running-config commands and your pertinent troubleshooting logs.


864

LSD_HA Messages

LSD_HA Messages This section contains MFI Label Switching Database (LFD) high availability (HA) messages.

LSD_HA-2 Error Message %LSD_HA-2-CF: [chars][dec] Explanation A CF-related error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LSD_HA-2-RESOURCE: [chars] Explanation A system resource error has occurred. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message %LSD_HA-2-RF: [chars][dec] Explanation An RF-related error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



865

LSD_HA Messages

LSD_HA-3 Error Message %LSD_HA-3-GENERAL: [chars] Explanation A function has received invalid parameters. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LSD_HA-3-INVALID_VAR: [chars] Explanation A function has received invalid parameters. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LSD_HA-3-LABEL_RANGE_DB: [chars] Explanation An error has occurred in the label range database. Recommended Action Copy the message exactly as it appears on the console or in the system log.



866

LSPV Messages

Error Message %LSD_HA-3-UNSENT_MSG_DB: [chars] Explanation An error has occurred in the unsent message database. Recommended Action Copy the message exactly as it appears on the console or in the system log.


LSPV Messages This section contains MPLS Label-Switched Path Verification (LSPV) messages.

LSPV-3 Error Message %LSPV-3-COMM: [chars]: [hex] [hex] Explanation An unexpected RP/LC XDR condition has been encountered in the communications

module. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %LSPV-3-COMM_UNKNOWN_RC: Unexpected oce return code Explanation An unexpected OCE return code was encountered in the communications module. Recommended Action Copy the message exactly as it appears on the console or in the system log.



867

LSS Messages


LSS Messages This section contains LS switching (LSS) message definition messages.

LSS-4 Error Message %LSS-4-LSIPC: [chars] [dec] Explanation LSIPC warning - LSIPC is timing out. uCode on that interface may not be responding. Recommended Action Possibly E-PAM is not responding.

LTL Messages This section contains local target logic (LTL) messages.

LTL-2 Error Message %LTL-2-LTL_PARITY_CHECK: LTL parity check request for 0x%x. Explanation The local target logic (LTL) parity check found a parity error on the index. Recommended Action Copy the message exactly as it appears on the console or in the system log.



868

MAB Messages

MAB Messages This section contains MAC authentication bypass (MAB) messages.

MAB-5 Error Message %MAB-5-FAIL: Authentication failed for client (%s) on Interface %s Explanation Authentication was unsuccessful. Recommended Action No action is required.

Error Message %MAB-5-SUCCESS: Authentication successful for client (%s) on Interface %s Explanation Authentication was successful. Recommended Action No action is required.

MAC_LIMIT Messages This section contains MAC limit feature (MAC_LIMIT) messages.

MAC_LIMIT-4 Error Message %MAC_LIMIT-4-DROP: Vlan [dec] with Configured limit = [dec] has currently [dec] Entries Explanation The number of entries for a VLAN has gone below or is equal to the allowed number. Recommended Action Copy the message exactly as it appears on the console or in the system log.



869

MAC_LIMIT Messages

Error Message %MAC_LIMIT-4-ENFORCE: Enforcing limit on Vlan [dec] with Configured limit = [dec] Explanation The number of entries for a VLAN has exceeded the allowed number. The action that

enforces the limit is configured. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MAC_LIMIT-4-EXCEED: Vlan [dec] with Configured limit = [dec] has currently [dec] Entries Explanation The number of entries for a VLAN has exceeded the allowed number. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MAC_LIMIT-4-PORT_DROP: [chars] with Configured limit [dec] has currently [dec] entries Explanation The number of entries for the specified port has gone below or is equal to the permitted

number. Recommended Action This message is for reporting purposes only. No action is required.

Error Message %MAC_LIMIT-4-PORT_ENFORCE: Enforcing limit on [chars] with Configured limit [dec] Explanation The number of entries for the specified port has exceeded the permitted number. The

action to enforce the limit is configured. Recommended Action This message is for reporting purposes only. No action is required.


870

MAC_MOVE

Error Message %MAC_LIMIT-4-PORT_EXCEED: [chars] with configured limit [dec] has currently [dec] entries Explanation The number of entries for the specified port has exceeded the permitted number. Recommended Action This message is for reporting purposes only. No action is required.

Error Message %MAC_LIMIT-4-VLAN_DROP: Vlan [dec] with configured limit [dec] has currently [dec] entries Explanation The number of entries for the specified VLAN has gone below or is equal to the

permitted number. Recommended Action This message is for reporting purposes only. No action is required.

Error Message %MAC_LIMIT-4-VLAN_ENFORCE: Enforcing limit on Vlan [dec] with configured limit [dec] Explanation The number of entries for the specified VLAN has exceeded the permitted number. The

action to enforce the limit is configured. Recommended Action This message is for reporting purposes only. No action is required.

Error Message %MAC_LIMIT-4-VLAN_EXCEED: Vlan [dec] with configured limit [dec] has currently [dec] entries Explanation The number of entries for the specified VLAN has exceeded the permitted number. Recommended Action This message is for reporting purposes only. No action is required.

MAC_MOVE This section contains MAC move notification feature (MAC_MOVE) messages.

MAC_MOVE-4 Error Message %MAC_MOVE-4-NOTIF: Host [enet] in vlan [dec] is flapping between port [chars] and port [chars] Explanation The system found the specified host moving between the specified ports. Recommended Action Examine the network for possible loops.


871

MCAST Messages

MCAST Messages This section contains Layer 2 Multicast log (MCAST) messages.

MCAST-2 Error Message %MCAST-2-IGMP_ADDRAL:IGMP: Address Aliasing for [chars] Explanation The network management processor (NMP) detected a multicast data stream being

directed to a special multicast address. Several special class D addresses are used exclusively for control purposes by the multicast protocols IGMP, DVMRP, MOSPF, and PIM. The sending of noncontrol packets to these addresses is considered address aliasing. Recommended Action From the displayed MAC and IP address information, determine which

device’s IP address is being aliased. Change its IP address to an address outside of the special multicast address group, or do not use it for the multicast data feed.

Error Message %MCAST-2-IGMP_ADDRALDETAILS:IGMP: Multicast address aliasing: From [chars] ([IP_address]) on [dec]/[dec] to [chars] Explanation The network management processor (NMP) detected a multicast data stream being

directed to a special multicast address. Several special class D addresses are used exclusively for control purposes by the multicast protocols IGMP, DVMRP, MOSPF, and PIM. The sending of noncontrol packets to these addresses is considered address aliasing. Recommended Action From the displayed group, port, and IP address information, determine which

device’s IP address is being aliased; [dec]/[dec] is the module number/port number. Change its IP address to an address outside of the special multicast address group, or do not use it for the multicast data feed.

Error Message %MCAST-2-IGMP_FALLBACK:IGMP: Running in FALL BACK mode Explanation The network management processor (NMP) has detected excessive multicast traffic being directed to a special multicast address that should be used exclusively for control purposes. As a result, the NMP has entered fallback mode, in which it stops snooping packets with the specified destination MAC address. After 5 minutes the NMP will attempt to listen to these groups again. If it fails 3 times, the switch will move to fallback mode permanently. In fallback mode, only IGMP-based packets will be directed to the NMP, and router ports will be learned only from IGMP general query messages. Recommended Action From the group and IP address information displayed by related system

messages, determine which device’s IP address is being aliased. Change its IP address to an address outside of the special multicast address group, or do not use it for the multicast data feed.


872

MCAST Messages

Error Message %MCAST-2-IGMP_SNOOP_DISABLE: Explanation IGMP snooping is disabled, but the system is receiving multicast traffic. This situation

will force multicast packets to be directed to the route processor, possibly flooding it. IGMP snooping may have been disabled automatically due to excessive multicast traffic. Recommended Action By capturing packets on the management VLAN (using a sniffer or SPAN),

determine the source of the excessive multicast traffic and remove it.

MCAST-3 Error Message %MCAST-3-GROUP_IP_INVALID: MCAST: Invalid group_ip in SSO sync msg for LTL type=[dec], index [hex] Explanation A system error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MCAST-3-IGMP_PKT_DROPPED:IGMP: IGMP Queue full (high packet rate/CPU busy), dropped [dec] packet(s) in last 5 minutes Explanation The IGMP queue dropped one or more packets during the past five minutes either

because the queue was full due to a high packet rate or because the CPU was too busy. Recommended Action If the packet drops are few and infrequent, the drops may be caused by a

transient condition, and no action is required. If many packets are being dropped, a multicast server might be flooding the switch, or some other process might be using excessive CPU resources.

Error Message %MCAST-3-PIMV2_PTCAM_LTL_ALL: PIMv2 PT_CAM LTL change to %s failed on all %s Explanation While the system was executing an MPLS, router-guard, or PIM rate-limiter

configuration command, communication with all line cards failed. As a result, the PIMv2 protocol redirection feature might not work properly. Recommended Action Enter the MPLS, router-guard, or PIM rate-limiter command ([no] mpls ip or

[no] router-guard ip multicast switchports or [no] mls rate-limit multicast ipv4 pim) again to cause the PIMv2 redirection local target logic (LTL) to be reprogrammed.


873

MCAST Messages

Error Message %MCAST-3-PIMV2_PTCAM_LTL_LC: PIMv2 PT_CAM LTL change to %s failed on linecard %d Explanation While the system was executing an MPLS, router-guard or PIM rate-limiter

configuration command, communication with one of the line cards failed. As a result, the PIMv2 protocol redirection feature might not work properly. Recommended Action Enter the MPLS, router-guard, or PIM rate-limiter command ([no] mpls ip or

[no] router-guard ip multicast switchports or [no] mls rate-limit multicast ipv4 pim) again to cause the PIMv2 redirection local target logic (LTL) to be reprogrammed.

Error Message %MCAST-3-PROT_RED_ALL: %s of %s redirection failed on all %s Explanation While IGMP or PIMv2 snooping was being globally enabled or disabled,

communication with all line cards failed. As a result, the protocol redirection feature might not work properly. Recommended Action Disable and then enable IGMP or PIMv2 snooping globally, or vice versa,

depending on whether the enable or disable form of the [no] ip [igmp | pim] snooping command was executed.

Error Message %MCAST-3-PROT_RED_LC: %s of %s redirection failed on linecard %d Explanation While IGMP or PIMv2 snooping was being globally enabled or disabled,

communication with one of the line cards failed. As a result, the protocol redirection feature might not work properly. Recommended Action Disable and then enable IGMP or PIMv2 snooping globally, or vice versa, %MCASTRED-3-BAD_SYNC_TYPE depending on whether the enable or disable form of the [no] ip

[igmp | pim] snooping command was executed.

Error Message %MCAST-3-QUERY_INT_MISMATCH: Snooping Querier received a non-matching query interval ([dec] msec), from querier address ([IP_address]) on VLAN([dec]).Configured query-interval ([dec] msec) Explanation Mismatch of snooping query interval found between routers which can lead to querier

flapping issues Recommended Action Configure the same snooping query interval across all the active and redundat queriers in the VLAN.


874

MCAST Messages

MCAST-4 Error Message %MCAST-4-LTL_FULL_VDB_CREATE_FAILED: Multicast Multi-Layer Switching: Failed to create VLAN ([dec]), hardware resource unavailable Explanation The number of multicast MAC entries has exceeded the hardware limit. As a result, the

VLAN will be software switched. This error also occurs when a larger number of VLANs are configured on a virtual switch. Recommended Action Check the number of multicast MAC entries using the show

mac-address-table multicast count command. Consider rearranging the network topology to reduce the multicast MAC count. Once multicast MAC entries fall below the hardware limit, unconfigure the VLAN using the no vlan command and reconfigure it.

Error Message %MCAST-4-RX_LVRANGE:IGMP: Rcvd Leave in the range [chars] Explanation The switch received an IGMP leave message from a host for the group address in the

specified range. This range is normally used for control packets and should not be used for general multicast data traffic. Recommended Action No action is required if the frequency of the message is not affecting the operation of the switch. This message may indicate a malfunction of the multicast host device that sent it. To determine the identity of the multicast device, check for related system messages reporting details of the IGMP leave. Using the port information displayed by the related system messages, capture port traffic to determine the source of the IGMP leave message.

MCAST-5 Error Message %MCAST-5-RX_IGMPLV:IGMP: Rcvd IGMP Leave [chars] on [dec]/[dec] Explanation The switch has received an IGMP leave message for the group number on module

number/port number; [chars] is the group number, and [dec]/[dec] is the module number/port number. Recommended Action No action is required.

Error Message %MCAST-5-RX_IGMPREPORT:IGMP: Rcvd IGMP Report [chars] on [dec]/[dec] Explanation The switch has received an IGMP report message for the group number on module

number/port number; [chars] is the group number, and [dec]/[dec] is the module number/port number. Recommended Action No action is required.


875

MCAST Messages

MCAST-6 Error Message %MCAST-6-CGMP_JOININFO: CGMP: GDA %e USA %e Explanation The system has received from the router a Cisco Group Management Protocol (CGMP)

join message for the group destination address (GDA) for the host whose unicast source address (USA) is shown. Recommended Action No action is required.

Error Message %MCAST-6-DELGDA: Deleting a GDA %e in vlan %d Explanation A multicast entry in the specified VLAN is being deleted because an IGMP leave from

the last host for this group destination address (GDA) was received. Recommended Action No action is required.

Error Message %MCAST-6-ETRACK_LIMIT_EXCEEDED: [chars] snooping was trying to allocate more explicit-tracking entries than what allowed ([dec] Explanation The allocation of explicit-tracking entries is limited to avoid the monopolizing of system resources by IGMP and MLD snooping. Recommended Action Reduce the number of (s,g) channels or the number of receivers. When the

explicit-tracking database has gone beyond its limit, new membership for any channels will not be tracked. This condition might cause high-leave latency when those members leave a channel. Another alternative is to increase the limit from configuration mode by entering the ip igmp snooping limit track max-entries command. It is important to note that increasing the value of max-entries could cause the system to fail because of high use of system resources.

Error Message %MCAST-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in %s snooping explicit-tracking statistics has exceeded the %s (%d) Explanation The number of explicit-tracking statistics entries is bounded to avoid monopolizing of

system resources by IGMP/MLD snooping. The explicit-tracking statistics database maximum size is set to the same as that of explicit-tracking limit. The statistics are split into two banks: permanent and volatile. The statistics entries will be stored permanently (volatile) until the permanent entries threshold is reached, after which the statistics will be stored temporarily up to the database maximum size. When the size of the database exceeds the permanent threshold, a group will be removed on receiving an IGMP/MLD leave. Groups can be removed whether they were installed above or below the permanent threshold. If the number of statistics entries grows beyond the maximum size of the database, then no statistics will be stored for any newly formed groups. Recommended Action If the number of groups being used in the network exceeds the recommended

value of the explicit-tracking database, you can increase the size of the database using the ip {igmp | mld} snooping limit track {0-128000} command. If the number of groups being used by hosts exceeds the recommended value of the explicit-tracking database, but the number of groups currently active is less than the database size and you require complete statistics, you can set the explicit-tracking limit to the maximum using the ip {igmp | mld} snooping limit track {0-128000} command. If you are interested only in statistics of the groups currently active in the system, you


876

MCAST Messages

can clear the IGMP/MLD snooping statistics to free up space in the database. The following command can be used to clear snooping statistics: clear ip {igmp | mld} snooping statistics [interface [type slot/port | vlan x]].

Error Message %MCAST-6-GC_LIMIT_EXCEEDED: IGMP snooping was trying to allocate more Layer 2 entries than what allowed ([dec]) Explanation IGMP snooping attempted to allocate more Layer 2 entries than the permitted amount

specified in the message. Recommended Action No action is required.

Error Message %MCAST-6-GLOBAL_CGMP_REDIRECT_NOT_INSTALLED: Global IGMP Snooping CGMP MAC Redirection not Installed, System cannot operate in IGMP_CGMP mode automatically Explanation The global IGMP Snooping feature was unable to install the CGMP-MAC redirection. As a result, the system cannot automatically function in IGMP_CGMP mode when the CGMP-capable devices are in the network. Recommended Action Enter the per-VLAN ip igmp snooping cgmp present command in all the

VLANs that have one or more receivers through a CGMP-capable Layer 2 switch connected to this system.

Error Message %MCAST-6-IGMP_CGMP_MODE: IGMP snooping now is running in IGMP_CGMP mode on vlan [dec] Explanation The specified VLAN is running in IGMP/CGMP mode. Recommended Action No action is required.

Error Message %MCAST-6-IGMP_ONLY_MODE: IGMP snooping now is running in IGMP_ONLY mode on vlan [dec] Explanation The specified VLAN is running in IGMP mode. Recommended Action No action is required.

Error Message %MCAST-6-IGMP_PKT_DROPPED: IGMP: IGMP Queue full (high packet rate/CPU busy), dropped [dec] packet(s) in last 5 minutes Explanation The IGMP packet queue is not able to accommodate additional packets. Any additional

packets will be dropped without processing. Recommended Action Reduce the IGMP packet rate to prevent packets from being dropped.


877

MCAST Messages

Error Message %MCAST-6-IGMP_RATE_LIMIT_DISABLE: IGMP: enabling Snooping on Vlan([dec]), IGMP messages will not be rate limited Explanation After throttling the IGMP messages on the VLAN for a certain period, snooping is

reenabled after the user manually fixes the rate on the offending VLAN and reduces the CPU load. Recommended Action No action is required.

Error Message %MCAST-6-IGMP_RATE_LIMIT_ENABLE: IGMP: Incoming IGMP message rate exceeded max threshold([dec] pps), disabling Snooping on Vlan([dec]) with Rate([dec] pps) Explanation The incoming rate of IGMP messages exceeded the maximum configured threshold.

Snooping will be disabled on all high-rate VLANs to lower the aggregate rate below the threshold on all remaining VLANs. Recommended Action Ease the CPU load by reducing the rate of IGMP messages on all high-rate

VLANs.

Error Message %MCAST-6-IGMPV3_BADPKT: IGMPV3: No of bad packets received (%s) = %d Explanation The switch received the specified number of bad IGMP packets. Recommended Action No action is required.

Error Message %MCAST-6-IGMPV3_EXCLUDE_RECORD: Received %d IGMP-V3 EXCLUDE Group Records with zero sources. Last received from Explanation This message indicates the number of IGMPv3 EXCLUDE 0 reports that were received

for groups in the source specific multicast (SSM) range. Recommended Action No action is required.

Error Message %MCAST-3-IGMPV3_V1V2PKT: No of IGMP (%s) messages received in SSM Range = %d Explanation The specified number of IGMP messages was received for groups in the source specific

multicast (SSM) range. Recommended Action No action is required.

Error Message %MCAST-6-IGMP_BADPKT: IGMP: No of Packets received with %s in last 5 minutes = %d Explanation The switch received the specified number of IGMP packets with bad checksums during

the previous five minutes. Recommended Action No action is required.


878

MCAST Messages

Error Message %MCAST-3-IGMP_VLAN_SNOOP_ALL: %s of protocol redirection for vlan %d failed on all %s Explanation While enabling or disabling IGMP snooping on the VLAN, communication with all line

cards failed. As a result, the protocol redirection feature might not work properly for the VLAN. Recommended Action Disable and then enable IGMP snooping on the VLAN, or vice versa,

depending on whether the enable or disable form of the [no] ip igmp snooping command was executed.

Error Message %MCAST-3-IGMP_VLAN_SNOOP_LC: %s of protocol redirection for vlan %d failed on linecard %d Explanation While enabling or disabling IGMP snooping on the VLAN, communication with one of

the line cards failed. As a result, the protocol redirection feature might not work properly for the VLAN. Recommended Action Disable and then enable IGMP snooping on the VLAN, or vice versa,

depending on whether the enable or disable form of the [no] ip igmp snooping command was executed.

Error Message %MCAST-6-L2_HASH_BUCKET_COLLISION: Failure installing (G,C)->index: ([enet],[dec])->[hex] Protocol :[dec] Error:[dec] Explanation A Layer 2 entry could not be installed in the hardware because there is not enough space in the hash bucket. Multicast packets will be flooded on the incoming VLAN because the Layer 2 entry installation failed. Recommended Action No action is required.

Error Message %MCAST-6-LTL_HIGH_WATER_MARK: Number of free LTL indices in the system has reached above the low threshold ([dec]) Explanation The number of indices available in the system has increased above the low threshold.

Snooping on the VLANs will resume. Recommended Action No action is required.

Error Message %MCAST-6-LTL_LOW_WATER_MARK: Number of free LTL indices in the system has reached below the low threshold ([dec]) Explanation The number of indices available in the system has fallen below the low threshold. As a

result, the multicast traffic on the VLANs will be flooded and snooping will be discontinued. Recommended Action Check whether the system has many source-only entries.


879

MCAST Messages

Error Message %MCAST-6-LTL_WATER_MARK: Number of free LTL indices in the system has reached above the low threshold (%d) Explanation The number of local target logic (LTL) indices available in the system has exceeded the

lower threshold, and snooping on the VLANs will resume. Recommended Action No action is required, but you can enter the remote command switch show mmls mltl command to check multicast LTL resource usage.

Error Message %MCAST-6-MCAST_PROT_STATUS: %s Feature is %sabled Explanation This message displays whether the Layer 2 multicast feature is enabled or disabled. Recommended Action No action is required.

Error Message %MCAST-6-MCAST_RTRADD_PIM: Adding Router Port %d/%d in vlan %d - PIM message Explanation The CGMP/IGMP has learned a new router port through a PIM message. Recommended Action No action is required.

Error Message %MCAST-6-MCAST_RTRADD_PROT: Adding Router Port %d/%d in vlan %d Explanation The CGMP/IGMP/MLD has learned a new router port. Recommended Action No action is required.

Error Message %MCAST-6-MCAST_RTRADD_USERCFG: Adding Router Port %d/%d in vlan %d User Configured Explanation A user-configured multicast router port was added using the CLI. Recommended Action No action is required.

Error Message %MCAST-6-MCAST_TOPOCHG: Recvd Topology Change Notification in vlan %d Explanation The network management processor (NMP) received a topology change notification in

a VLAN. Recommended Action No action is required.


880

MCAST Messages

Error Message %MCAST-6-MLD_ADDRESS_ALIASING_FALLBACK: Address Aliasing detected for [enet] on vlan [dec] from possible src-ip[ipv6_addr] dst-ip[ipv6_addr] src-mac [enet] Explanation Multicast packets with destinations that alias a special Layer 2 entry can indicate a possible denial-of-service attack and overwhelm the CPU. Recommended Action Remove from the Layer 2 table the entry for which address aliasing was

detected.

Error Message %MCAST-6-MLD_ADDRESS_ALIASING_NORMALMODE: Address Aliasing timer expired reinstalling entry for group [enet] on vlan [dec] Explanation After a certain time (dependent on the group for which address aliasing was detected)

the corresponding Layer 2 entry is reinstalled. Recommended Action Reinstall in the Layer 2 table the entry for which address aliasing was detected

Error Message %MCAST-6-MLD_RATE_LIMIT_DISABLE: MLD: enabling Snooping on Vlan([dec]), MLD messages will not be rate limited Explanation After throttling the IGMP messages on the VLAN for a certain period, snooping is

reenabled after the user manually fixes the rate on the offending VLAN and reduces the CPU load. Recommended Action No action is required.

Error Message %MCAST-6-MLD_RATE_LIMIT_ENABLE: MLD: Incoming MLD message rate ([dec] pps) exceeded max threshold([dec] pps), disabling Snooping on Vlan([dec]) for [dec] secs Explanation The incoming rate of MLD messages has exceeded the maximum configured threshold. Snooping will be disabled on all high rate VLANs to reduce the aggregate rate on all remaining VLAN to below the threshold. Recommended Action Ease the CPU load by reducing the rate of MLD messages on all high-rate

VLANs.

Error Message %MCAST-6-RGMP_JOIN: Rcvd RGMP Join Mesg %d/%d vlan %d for Group %i Explanation The router has joined a multicast group. Recommended Action No action is required.

Error Message %MCAST-6-RGMP_JOINRANGE: Rcvd RGMP Join Message in the range 01-00-5e-00-00-xx Explanation The router sent a message for an invalid (reserved) address. The address

01-00-5e-00-00-xx cannot be used by the Router Port Group Management Protocol (RGMP). Recommended Action No action is required.


881

MCAST Messages

Error Message %MCAST-6-RGMP_LEAVE: Rcvd RGMP Leave Mesg %d/%d vlan %d for Group %i Explanation The router has left a multicast group. Recommended Action No action is required.

Error Message %MCAST-6-RGMP_LVRANGE: Rcvd RGMP Leave Mesg in the range 01-00-5e-00-00-xx Explanation The router sent a message for an invalid (reserved) address. The address

01-00-5e-00-00-xx cannot be used by RGMP. Recommended Action No action is required.

Error Message %MCAST-6-RTRDEL_TIMEOUT: Deleting Router Port %d/%d in vlan %d Timeout Explanation The router port timer has timed out and the router port entry has been removed. Recommended Action Determine whether a router is connected to the indicated port, and verify that

IGMP is enabled.

Error Message %MCAST-6-RTRRGMP_BYE: Router Port %d/%d in vlan %d has become nonRGMP-capable Explanation An RGMP router port has changed to a non-RGMP router port. Recommended Action No action is required.

Error Message %MCAST-6-RTRRGMP_HELLO: Router Port %d/%d in vlan %d has become RGMP-capable Explanation A router port has changed to a RGMP-capable port. Recommended Action No action is required.

Error Message %MCAST-6-RTRRGMP_TIMEOUT: Router Port %d/%d in vlan %d has become RGMP-capable Explanation The RGMP router has timed out and the port is no longer RGMP-capable. Recommended Action No action is required.

Error Message %MCAST-6-RX_CGMPJN: Rcvd CGMP Join Mesg in vlan %d Explanation A CGMP join message was received by a VLAN. Recommended Action No action is required.


882

MCAST Messages

Error Message %MCAST-6-RX_CGMPLV: Rcvd CGMP Leave Mesg %d/%d vlan %d Explanation A CGMP leave message was received on a VLAN port. Recommended Action No action is required.

Error Message %MCAST-6-RX_IGMPLV: IGMP: Rcvd IGMP Leave %e on %d/%d Explanation The switch received an IGMP leave message for the group number on module

number/port number. Recommended Action No action is required.

Error Message %MCAST-6-RX_IGMPREPORT: IGMP: Rcvd IGMP Report %e on %d/%d Explanation The switch received an IGMP report message for the group number on module

number/port number. Recommended Action No action is required.

Error Message %MCAST-6-RX_JNRANGE: IGMP: Rcvd Report in the range of 01-00-5e-00-00-xx Explanation The switch received an IGMP report from a host for the group address in the range of

01-00-5e-00-00-xx. This range is reserved for control packets and should not be used for general multicast data traffic. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MCAST-6-RX_LVRANGE: IGMP: Rcvd Leave in the range of 01-00-5e-00-00-xx Explanation The switch received an IGMP leave from a host for the group address in the range of

01-00-5e-00-00-xx. This range is reserved for control packets and should not be used for general multicast data traffic. Recommended Action Copy the message exactly as it appears on the console or in the system log.



883

MCAST_MQC Messages


Error Message %MCAST-6-SOURCE_ONLY_LIMIT_EXCEEDED: [chars] snooping was trying to allocate more source only entries than allowed ([int]) Explanation Attempts by the IGMP snooping module to allocate source-only entries has exceeded

the limit. This limit prevents the IGMP snooping module from consuming all of the system resources. Any IP groups sent in excess of the limit will not be learned by IGMP snooping. Recommended Action Either reduce the number of IP groups sent or increase the limit by entering the

ip igmp snooping source-only-learning limit max-entries command. Increasing the value of max-entries could cause a system failure due to the overuse of system resources.

MCAST_MQC Messages This section contains multicast modular quality of service command-line interface MQC messages.

MCAST_MQC-3 Error Message %MCAST_MQC-3-CMAP_SDB_REGISTER: Error initialising class-map of type multicast-flows. Explanation The system could not register the component related to the class map of type \n multicast-flows to the string database. Recommended Action Copy the message exactly as it appears on the console or in the system log.



884

MCASTRED Messages

MCASTRED Messages This section contains multicast redundancy (MCASTRED) messages.

MCASTRED-3 Error Message %MCASTRED-3-ACKQMSG: Failed attempt to enqueue sync message type %u in confirmation queue Explanation An attempt to link a new synchronization message into the synchronization message

confirmation queue failed. This failure indicates corruption of the linkage within the queue. It is not possible to track message confirmation or to initiate a recovery action if confirmation is not received. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MCASTRED-3-ACKUNQMSG: Failed to remove sync request type %u from pending ACK queue Explanation An attempt failed to unlink a completed synchronization request from the queue for requests awaiting confirmation of receipt from the standby route processor (RP). This failure indicates corruption of the linkage within the pending acknowledgement queue. False timeout error messages and memory leakage are likely. Loss of standby RP synchronization is possible. Recommended Action Copy the message exactly as it appears on the console or in the system log.



885

MCASTRED Messages

Error Message %MCASTRED-3-ALCSYNCTYP: Attempt to allocate sync request for invalid sync type %u Explanation A function attempting to perform a synchronization operation has specified an invalid

synchronization data type. No synchronization operation can be performed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MCASTRED-3-ALLOCMSG: Sync message buffer allocation failed for sync info type %u Explanation An attempt to allocate a buffer for synchronization message transmission failed. Loss of synchronization on the standby route processor (RP) is likely. Recommended Action Attempt standby RP synchronization by reloading the standby RP. If the

problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %MCASTRED-3-ALLOC_CAP_TLV: Failed attempt to allocate memory for %s client capability TLV Explanation The callback function responsible for creating an ISSU capability type length value (TLV) list was unable to allocate memory to hold the TLV list. Capability negotiation cannot proceed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



886

MCASTRED Messages

Error Message %MCASTRED-3-BAD_EVENT_TYPE: Defrd sync event type [dec] is invalid. Explanation An invalid value was specified in a call to handle events which deferred sync elements are waiting for. The value is greater than PIM_SYNC_WAIT_FOR_EVENT_MAX. Recommended Action This is a transient error. However, this condition indicates other errors in the

software that will require further examination by your Cisco technical support representative. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %MCASTRED-3-BAD_SYNC_TYPE: PIM sync type %d is invalid or too large. Explanation In a call to modify an array indexed by the Protocol Independent Multicast (PIM) synchronization type, an out-of-bounds value was specified. The specified value exceeds either PIM_SYNC_TYPE_MAX or the length of the array. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MCASTRED-3-BLKNOBOOL: Failed to create %s watched boolean for bulk sync Explanation An attempt to create a watched boolean to monitor bulk synchronization of state

information to the standby route processor (RP) has failed. It is not possible to verify successful completion of the bulk synchronization operation. Recommended Action Copy the message exactly as it appears on the console or in the system log.



887

MCASTRED Messages

Error Message %MCASTRED-3-BLKNOFUNC: No bulk sync function defined for sync type %u Explanation No function is defined for bulk synchronization of database information of this type.

Some required information might not be synchronized to the standby RP. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MCASTRED-3-BULKRQTIME: Timeout sending bulk sync requests to standby Explanation The maximum wait time has expired for transmission of enqueued bulk synchronization

messages to the standby RP. Some required synchronization messages might not have been sent successfully. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MCASTRED-3-BULK_COMPLETE_INCOMPATIBLE: Skipping sending of bulk sync completion message to peer: Incompatible message type. Explanation The message code designated for peer RP confirmation of bulk synchronization

completion was not recognized by the ISSU infrastructure as a compatible PIM HA message type. Although PIM bulk synchronization may have succeeded, bulk synchronization confirmation is not possible. Recommended Action Copy the message exactly as it appears on the console or in the system log.



888

MCASTRED Messages

Error Message %MCASTRED-3-BULK_COMPLETE_XFORM_FAIL: ISSU xmit transform failed for bulk send complete message. Explanation An ISSU transformation failed on the message used for peer RP confirmation of bulk

synchronization completion. Although PIM bulk synchronization may have succeeded, bulk synchronization confirmation is not possible. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MCASTRED-3-CAP_PROC_NULL_CTX: NULL client context for ISSU capability TLV processing. Explanation The callback function responsible for processing a capability type length value (TLV)

was invoked by the ISSU infrastructure with a NULL client context. Capability negotiation cannot proceed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MCASTRED-3-CAP_PROP_NULL_CTX: NULL client context for ISSU capability TLV setup. Explanation The callback function responsible for creating a capability type TLV was invoked by the

ISSU infrastructure with a NULL client context. Capability negotiation cannot proceed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



889

MCASTRED Messages

Error Message %MCASTRED-3-DDE_REPLAY_FAILSAFE: PIM NSF Data Driven Event failsafe timer expired. First waiting VRF is Explanation Multicast Forwarding Information Base (MFIB) replay of data driven events and subsequent Multicast Routing Information Base (MRIB) update processing has not completed within the maximum allowed time interval. Protocol Independent Multicast (PIM) is forcing termination of the Data Driven Event (DDE) replay monitoring period but some multicast routing information might not have been restored. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MCASTRED-3-DDE_REPLAY_NULL_MVRF: NULL MVRF specified for DDE replay. Explanation An invalid (NULL) value was specified in a call to initiate MFIB data driven event replay following a route processor failover. Some previously existing multicast state might not be preserved through the route processor failover. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MCASTRED-3-DECODEFUNC: No decode function exists for sync data type %u Explanation No function is defined for handling synchronization data of the specified type. No

synchronization action is possible on the standby RP for the synchronization message that specified this data type. Recommended Action Copy the message exactly as it appears on the console or in the system log.



890

MCASTRED Messages


Error Message %MCASTRED-3-DECODENULL: No message buffer specified for standby sync of database type %u Explanation A function was invoked to perform a database synchronization operation on the standby

RP, but the caller did not specify the address of the synchronization message containing the information required for performing the synchronization operation. The synchronization operation for this database entity type cannot proceed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MCASTRED-3-DEFER_SYNC_FAILURE: Sync failure in standby defer sync operation. Explanation An element which was scheduled to be synched later has failed to sync either upon

arrival of the event it was waiting for or it has waited in the deferred sync queue for more than 1 minute. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %MCASTRED-3-DELNULLREQ: No sync request specified in sync request deletion attempt. Explanation In a call to delete a synchronization request entry, the caller failed to specify the location

of the synchronization request to be deleted. A memory leak is likely. Recommended Action Copy the message exactly as it appears on the console or in the system log.



891

MCASTRED Messages


Error Message %MCASTRED-3-DELSYNCTYP: Attempt to delete sync request for invalid sync type %u Explanation A function attempting to delete a synchronization request has specified an invalid

synchronization data type. The synchronization request cannot be deleted. A memory leak is likely. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MCASTRED-3-EMPTY_CAP_GROUP: Empty capability group for %s ISSU client capability TLV setup. Explanation The callback function responsible for creating an ISSU capability type length value (TLV) found that the count of capability entries in its client context table was zero. Capability negotiation cannot proceed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MCASTRED-3-EMPTY_CAP_PROPOSE_TABLE: Empty capability table for ISSU capability TLV setup. Explanation The callback function responsible for creating a capability type TLV was invoked by the

ISSU infrastructure with a capability table containing no capability types. Capability negotiation cannot proceed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



892

MCASTRED Messages


Error Message %MCASTRED-3-EOXBADRC: Invalid completion code %u for sync message transmission type %u Explanation An undefined completion code was specified for end of synchronization message

transmission handling. Memory leakage, false timeouts, and other subsequent errors may result. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MCASTRED-3-EOXNOREQ: End of sync message transmission: no sync request specified Explanation End of synchronization message transmission handling was invoked with no

synchronization request specified. Cleanup for successful transmission cannot proceed. Retry for unsuccessful transmission cannot proceed. Memory leakage is likely and loss of synchronization on the standby RP is possible. Recommended Action Copy the message exactly as it appears on the console or in the system log.



893

MCASTRED Messages

Error Message %MCASTRED-3-FINDNULLENT: No target specified for sync entity search. Explanation In a call to invoke a search for a database entity requiring synchronization to the standby

RP, the caller failed to specify a descriptor for the entity to be synchronized. The synchronization operation entity cannot proceed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MCASTRED-3-FMTFUNC: No sync message format function defined for sync type %u Explanation No function is defined to create a synchronization message for this type of database

information. Loss of synchronization on the standby RP is likely. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MCASTRED-3-FMTGENNOBF: No message buffer specified for generic sync message info Explanation A function was invoked to store generic synchronization message information into an

outgoing message buffer, but the caller did not specify the outgoing message buffer address. The synchronization operation for this database entity type cannot proceed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



894

MCASTRED Messages

Error Message %MCASTRED-3-FMTMSG: Failed to format a sync message for sync type %u Explanation An attempt to format (create) a synchronization message has failed. The

synchronization message cannot be sent. Loss of synchronization on the standby RP is likely. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MCASTRED-3-FMTNULLPRM: Missing parameters in sync message format request for data type %u Explanation A function was invoked to store synchronization message information into an outgoing

message buffer, but the caller failed to specify either the location of the search key for the database entity to be synchronized or the address of the outgoing message buffer. The synchronization operation for this database entity type cannot proceed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MCASTRED-3-HASHNQ: Failed attempt to enqueue sync request type %u in hash table Explanation An attempt to link a new synchronization request into the synchronization request hash

table failed. This failure indicates corruption of the linkage within the hash table. The synchronization operation cannot proceed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



895

MCASTRED Messages

Error Message %MCASTRED-3-HLD_RLS_NO_MVRF: No MVRF for tableid 0x%x specified for multicast NSF holdoff release. Explanation A table ID for which no MVRF exists was specified as an input to a function registered

for releasing of a multicast NSF holdoff lock. If the calling client has a real holdoff extension request pending for some MVRF, the lock will not be released until the holdoff failsafe timer expires. This condition could delay completion of multicast reconvergence following an RP failover. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MCASTRED-3-HOLDOFF_FAILSAFE: PIM NSF failsafe timer expired. Holding client mask = 0x%x Explanation One or more clients requested extension of the PIM NSF holdoff period, but did not

release the holdoff within the maximum allowed time interval. PIM is forcing termination of the NSF holdoff period and resumption of normal flow of multicast routing information, but one or more clients may not be ready to resume normal operation. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MCASTRED-3-INITNOBOOL: Failed to create %s watched boolean during multicast redundancy initialization Explanation An attempt to create a watched boolean during multicast (PIM) redundancy process

initialization has failed. The PIM redundancy process cannot be initialized. Recommended Action Copy the message exactly as it appears on the console or in the system log.



896

MCASTRED Messages


Error Message %MCASTRED-3-INITNOQUEUE: Failed to create %s watched queue during multicast redundancy initialization Explanation An attempt to create a watched queue during multicast (PIM) redundancy process initialization has failed. The PIM redundancy process cannot be initialized. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MCASTRED-3-INVALID_CAP_PROPOSE_TABLE: Invalid capability table for %s client ISSU capability TLV setup. Explanation The callback function responsible for creating a capability type length value (TLV) was

invoked by the ISSU infrastructure with a capability table that did not match any of the registered entries for this client. Capability negotiation cannot proceed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MCASTRED-3-INVSYNCTYP: Attempt to initiate sync request for invalid sync type Explanation The synchronization data type specified by the function attempting to initiate a synchronization operation is not a valid type. No synchronization operation can be performed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



897

MCASTRED Messages


Error Message %MCASTRED-3-INV_CKPT_MSG: Received invalid CF message. client = %u, entity = %u, type = %u Explanation An invalid checkpoint facility (CF) message was received by the PIM HA checkpoint client. The message cannot be processed. This condition might cause a loss of database synchronization between the primary and standby RPs. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MCASTRED-3-INV_PORT_TYPE: Invalid communication port identifier %u specified for ISSU port up/down handling Explanation An undefined communication port identifier was specified for PIM ISSU transport up

or down handling. PIM ISSU communication port up or down handling cannot proceed. PIM ISSU functionality might be impaired or lost. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MCASTRED-3-ISSU_EMPTY_TLV: Empty TLV list received for ISSU %s client capability processing Explanation The callback function responsible for processing an ISSU capability type length value

(TLV) list received an empty TLV list. Capability negotiation cannot proceed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



898

MCASTRED Messages


Error Message %MCASTRED-3-ISSU_PROC_CAP_TYPE: Invalid capability type found in %s client capability entry. Explanation The callback function responsible for processing an ISSU capability type TLV list

encountered a capability type for which no handling is available. Capability negotiation cannot proceed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MCASTRED-3-ISSU_TLV_INSERT: Failed to insert entry in ISSU capability TLV list for %s client Explanation The callback function responsible for creating an ISSU capability type TLV list

encountered a failure when attempting to insert an entry into a TLV list. Capability negotiation cannot proceed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



899

MCASTRED Messages

Error Message %MCASTRED-3-LOCFUNC: No database entity search function defined for sync type %u Explanation A function was invoked to store synchronization message information into an outgoing

message buffer, but no function exists for locating a database entry of the specified type. The synchronization operation for this database entity type cannot proceed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MCASTRED-3-LOCNULLENT: No destination specified in search for sync entity of type %u Explanation A function was invoked to search for a database entity of the specified type, but the caller failed to specify a destination for storing the search result. The synchronization operation for this database entity type cannot proceed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MCASTRED-3-LOCNULLHND: No search handle specified in search for sync entity of type %u Explanation A function was invoked to search for a database entity of the specified type, but the caller failed to specify a search handle (key) for finding the database entity to be synchronized. The synchronization operation for this database entity type cannot proceed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



900

MCASTRED Messages


Error Message %MCASTRED-3-MRIB_UPD_NULL_MVRF: NULL MVRF pointer specified for MRIB update notification. Explanation A NULL MVRF address was specified in a function call to notify the PIM HA process

that all pending updates have been read for a specified MVRF. The process will attempt to continue with RP switchover handling despite this error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MCASTRED-3-MSGNOREQ: Could not find sync request for completed sync message type %u Explanation The synchronization request corresponding to a completed synchronization message

could not be determined. This condition may result in memory leakage, false timeouts, and other subsequent errors. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MCASTRED-3-MSGSEQNUM: Out of order sequence number in received sync message for sync data type %u, received epoch/seq %u/%u, expected %u/%u Explanation The sequence number specified in a synchronization message received by the standby

RP is not the expected sequence number for the next received synchronization message. Some synchronization messages may have been lost. Recommended Action Attempt to synchronize the standby RP by reloading it. If the problem persists,

copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software


901

MCASTRED Messages

issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %MCASTRED-3-MVRF_NAME: MVRF lookup for VRF %s failed. Explanation An MVRF lookup failed for a VRF name known to be associated with an existing

MVRF table, indicating an incorrect setup of search parameters. A PIM data synchronization operation has been aborted. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MCASTRED-3-MVRF_TABLEID: MVRF lookup for tableid %u failed. Explanation An MVRF lookup failed for a table ID known to be associated with an existing MVRF

table, indicating an incorrect setup of search parameters. A PIM data synchronization operation has been aborted. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MCASTRED-3-NEGOMSGINV: Invalid negotiation status for %s client message Explanation The ISSU infrastructure evaluated a message for this client but failed to identify the message as a negotiation message or a user message. The message cannot be processed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



902

MCASTRED Messages


Error Message %MCASTRED-3-NOSYNCARG: NULL argument pointer specified for PIM data sync type %u. Explanation A function was invoked to synchronize PIM information, but the caller did not provide

a valid data pointer. The synchronization operation for this database entity type cannot proceed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MCASTRED-3-PRM_LOOKUP: PIM RP mapping range lookup for VRF %s group %i mask %i failed. Explanation A PIM RP mapping range lookup failed for a range that is known to exist, indicating an

incorrect setup of search parameters. A PIM data synchronization operation has been aborted. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MCASTRED-3-RCVNODATA: No data pointer returned for received checkpoint message Explanation On reception of a checkpoint message at the standby RP, an attempt to obtain the

location of the data for the message returned a NULL pointer. No message contents are available for this message. Recommended Action Attempt to synchronize the standby RP by reloading it. If the problem persists,

copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some


903

MCASTRED Messages

messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %MCASTRED-3-RPDF_NO_IDB: No IDB for if_number %u in Bidir RP DF sync attempt for RP address %i. Explanation In a function call to trigger synchronization of bidirectional RP designated forwarder (DF) information, the interface descriptor block (IDB) if_number specified does not map to any existing IDB. The synchronization operation cannot proceed. The DF information might no longer be correct following an RP failover. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MCASTRED-3-RPDF_NULL_IDB: NULL IDB pointer in Bidir RP DF sync attempt for RP address %i. Explanation In a function call to trigger synchronization of bidirectional RP DF information, a

NULL IDB address was specified. The DF information might no longer be correct following an RP failover. Recommended Action Copy the message exactly as it appears on the console or in the system log.



904

MCASTRED Messages

Error Message %MCASTRED-3-RTRYLIMIT: Retry limit reached for sync type %u Explanation The maximum allowable number of transmission retries has failed for a database entity of this type. No further retries can be executed. The standby RP might no longer be synchronized with the active RP. Recommended Action Attempt to synchronize the standby RP by reloading it. If the problem persists,


Error Message %MCASTRED-3-RTRYNOREQ: Sync retry requested with no sync request specified Explanation A retry was requested for transmission of a synchronization message, but no

synchronization request information was specified. The retry cannot be executed. The standby RP might no longer be synchronized with the active RP. Recommended Action Attempt to synchronize the standby RP by reloading it. If the problem persists,


Error Message %MCASTRED-3-SNDMSG: Failed to send a sync message for sync type %u Explanation An attempt to send a synchronization message has failed. The message transmission will be automatically retried. Recommended Action Copy the message exactly as it appears on the console or in the system log.



905

MCASTRED Messages

Error Message %MCASTRED-3-SNDNODATA: No data pointer provided in checkpoint message to be sent. Explanation After allocation of a checkpoint message buffer in the primary RP, an attempt to obtain the location of the data for the message returned a NULL pointer. The checkpoint message cannot be sent. Loss of standby synchronization is likely. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MCASTRED-3-SPURIOUS_MGD_TIMER_EXP: Managed timer wakeup received by the PIM HA process with no expired timers. Explanation The PIM HA process received a wakeup for managed timer expiration, but no expired

timer was reported. The timer expiration cannot be handled. The standby RP might no longer be synchronized with the active RP. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MCASTRED-3-SYNC_REQ_ORPHAN: Orphaned queue links found in sync request hash table search for sync type %u Explanation An attempt to find a matching entry for a new synchronization request in the

synchronization request hash table failed because of corruption of the linkage within the hash table. The synchronization operation cannot proceed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



906

MCASTRED Messages


Error Message %MCASTRED-3-TABLE_INVALID_CAP_TYPE: Invalid capability type found in %s client capability entry. Explanation The callback function responsible for creating an ISSU capability type length value (TLV) list encountered a capability type for which no handling is available. Capability negotiation cannot proceed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MCASTRED-3-TUNSYNCMSG: Received invalid termination message for mvrf(%u) while waiting for mvrf(%u) mdt tunnel sync Explanation Confirmation has failed for standby RP reception of a multicast distribution tree (MDT)

tunnel message. As a result, the standby RP might not be able to create the MDT tunnel. Recommended Action Attempt to synchronize the standby RP by reloading it. If the problem persists,


Error Message %MCASTRED-3-TUNSYNCRCV: %s failure in reception of MDT tunnel sync information for mvrf %s on the standby RP. Explanation Confirmation has failed for standby RP reception of a multicast distribution tree (MDT)


copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at


907

MCASTRED Messages


Error Message %MCASTRED-3-TUNSYNCTIME: Timeout waiting for confirmation of mdt tunnel sync for mvrf(%u) (%s) Explanation Confirmation has failed for standby RP reception of a multicast distribution tree (MDT)



Error Message %MCASTRED-3-TUNSYNCXMIT: Failed to transmit sync MDT tunnel information for mvrf %s to the standby RP. Explanation An interprocess communication (IPC) transmission attempt has failed to send an IPC message to the standby RP with multicast distribution tree (MDT) tunnel synchronization information. As a result, the standby RP will not be able to create the MDT tunnel. Recommended Action Attempt to synchronize the standby RP by reloading it. If the error recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %MCASTRED-3-UCAST_CONV_STBY: Spurious unicast convergence notification received on standby RP for mvrf %s. Explanation Unicast convergence notification was erroneously signalled on the standby RP for the

specified multicast VRF. This convergence notification is being ignored. Recommended Action Copy the message exactly as it appears on the console or in the system log.



908

MCAST_RP Messages


Error Message %MCASTRED-3-WAITQ_ORPHAN: Orphaned queue links found in the %x MVRF wait queue. Explanation An attempt to perform state transition handling for multicast VRFs (MVRFs) in this queue failed. The failure occurred because the queue was corrupted or because one or more queue link entries did not specify the address of the corresponding MVRF. Multicast route convergence following an RP failover may be delayed or impaired. Recommended Action Copy the message exactly as it appears on the console or in the system log.


MCAST_RP Messages This section contains multicast route processor messages.

MCAST_RP-4 Error Message %MCAST_RP-4-MPLS_PIM_RATE_LIMIT: [chars] when [chars] will reprogram hardware setting for PIM. Please reapply PIM rate-limiter. Explanation The Router Guard or PIM Snooping features require the switch hardware to be

programmed in a manner different from MPLS. These two features are incompatible with MPLS. When either Router Guard or PIM snooping is enabled while MPLS is enabled, the PIM rate limiter will not work properly. Recommended Action Unconfigure and reconfigure the PIM rate limiter using the show mls rate-limit multicast ipv4 pim command. The same solution applies to the situation when both Router Guard and PIM snooping are disabled and MPLS is being enabled.


909

MCM Messages

Error Message %MCAST_RP-4-MPLS_PIM_SNOOPING: The MPLS and PIM Snooping features do not work together. Please disable either one. Explanation The PIM Snooping feature requires the switch hardware to be programmed in such a

way that PIM register messages with MPLS tags might be lost. Recommended Action Disable either MPLS or PIM Snooping.

Error Message %MCAST_RP-4-MPLS_ROUTER_GUARD: The MPLS and Router Guard features do not work together. Please disable either one. Explanation The Router Guard feature requires the switch hardware to be programmed in such a way

that PIM register messages with MPLS tags might be lost. Recommended Action Disable either MPLS or Router Guard.

Error Message %MCAST_RP-4-RGUARD_PIM_RATE_LIMIT: Router Guard feature if enabled or disabled while PIM rate-limiter is ON will not work properly. Please reapply the PIM rate-limiter. Explanation The PIM rate limiter floods the rate-limited PIM control packets to all the ports in the VLAN. Because of this, the Router Guard feature will not work properly if enabled while the PIM rate limiter is enabled. Recommended Action Unconfigure and reconfigure the PIM rate limiter using the show mls rate-limit multicast ipv4 pim command.

MCM Messages This section contains minimum disruption restart (MDR) card manager messages.

MCM-3 Error Message %MCM-3-DEQUEUE_FAIL: Unable to get a free event (%s) from the free event queue (slot: %d, mode %d) Explanation During runtime, the minimal disruption routing (MDR) card manager is unable to

retrieve a free event to communicate between its different processes. MDR operation will probably result in the resetting of all line cards. Recommended Action Copy the message exactly as it appears on the console or in the system log.



910

MCM Messages


Error Message %MCM-3-GET_MTU_FAIL: Unable to get the MTU for message %d to seat %s (%d) (valid:%d) Explanation During runtime, the MDR card manager is unable to get the MTU of a message to be

sent between its different processes. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MCM-3-NEGO_INCOMPATIBLE: MDR Card manager ISSU negotiation with standby is incompatible Explanation An error occurred during MDR card manager initialization. As a result, the MDR card

manager is unable to synchronize its data between the active and standby supervisors. An MDR operation will probably result in the resetting of all line cards. Recommended Action Copy the message exactly as it appears on the console or in the system log.



911

MCT1E1 Messages

MCT1E1 Messages This section contains CT1/CE1 shared port adapter messages.

MCT1E1-2 Error Message %MCT1E1-2-CMD_DROP: [chars], cmd: [dec], arg0: [dec], arg1: [dec] arg2: [dec], arg3: [dec], vc: [dec] reason: [chars] Explanation The SPA driver dropped a configuration command. One or more interfaces or

controllers associated with the SPA might not be configured correctly. Recommended Action Check the configuration of the interfaces and controllers and correct the

configuration if necessary. If the condition persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %MCT1E1-2-EV_DROP: [chars], cmd: [dec], arg0: [dec], arg1: [dec] arg2: [dec] reason [chars] Explanation The SPA driver dropped an event notification command. Counters or line protocols for

one or more interfaces or controllers may be incorrect. Recommended Action Restart any interfaces or controllers that are down. If the condition persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


912

MCT1E1 Messages

MCT1E1-3 Error Message %MCT1E1-3-AUTODNR: %s failed for slot %d bay %d err %d Explanation The Auto-Do-Not-Resequence (AUTODNR)/USNDNR process has failed. The SPA

and line card are out of synchronization. This condition indicates a software error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MCT1E1-3-BAD_SIZE_ERR: SPA [dec]/[dec]: [dec] [chars] events on HDLC Controller were encountered. The SPA is being Restarted. Explanation The SPA driver detected an error event on the HDLC controller. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %MCT1E1-3-BATCH_CMD_INVALID_TAG: SPA [dec]/[dec]: Invalid tag value [dec] at index [dec]. Explanation The SPA driver detected an invalid tag value in a batch command from the RP. Recommended Action If the ports on the SPA are not operating as expected, power down and reseat

the specified SPA card. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


913

MCT1E1 Messages

Error Message %MCT1E1-3-CMD_FAILED: SPA [dec]/[dec]: f/w send command failed err [dec] reason [chars] Explanation The SPA driver could not successfully send a command to the firmware. Recommended Action If the ports on the SPA are not operating as expected, power down and reseat

the specified SPA card. If this message persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %MCT1E1-3-COR_MEM_ERR: SPA [dec]/[dec]: [dec] correctable [chars] memory error(s) encountered. The error has been corrected and normal processing should continue. The memory address of most the recent error is: [hex] Explanation The SPA driver detected a correctable memory error on the SPA card. The error has been

corrected and normal processing should continue. The hexadecimal memory address of the most recent error is specified in the message text on the console or in the system log. Recommended Action If the condition persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %MCT1E1-3-FPGA_CNTR_ERR: [chars]: [dec] [chars] error(s) encountered. Explanation The SPA driver detected an FPGA error condition on the SPA card. Interface packet

error counter corruption may result. Recommended Action The SPA should continue to function normally. If the error condition recurs,

reset the SPA by doing a physical online insertion and removal (OIR). If the condition persists, copy the error message exactly as it appears. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support


914

MCT1E1 Messages


Error Message %MCT1E1-3-FRMR_CLKFAIL: SPA [dec]/[dec]: Framer input clock failure detected, CTCLK = [chars]CTIVE, LREFCLK = [chars]CTIVE, SREFCLK = [chars]CTIVE, ctclk count [int] lrefclk count [int] srefclk count [int] Explanation The SPA driver detected failure of one or more input clocks to the framer chip. The

T1/E1 ports may not operate as expected. Recommended Action If the ports on the SPA are not operating as expected, power down and reseat


Error Message %MCT1E1-3-HDLC_CTRL_ERR: SPA [dec]/[dec]: [dec] [chars] events on HDLC Controller were encountered. Explanation The SPA driver detected an error event on the HDLC controller. Recommended Action If the condition persists, c opy the message exactly as it appears on the console


Error Message %MCT1E1-3-INITFAIL: MCT1E1 (bay [dec]), Init Failed at [chars] - line [dec] arg [hex] Explanation The SPA failed to complete hardware initialization. Recommended Action Copy the message exactly as it appears on the console or in the system log.



915

MCT1E1 Messages


Error Message %MCT1E1-3-PERIODIC_PROCESS: SPA [dec]/[dec]: periodic process error [chars]. Explanation The SPA driver detected an error with the periodic processing routine. Recommended Action If the ports on the SPA are not operating as expected, power down and reseat


Error Message %MCT1E1-3-QUEUE_HALT_FAIL: [chars]: Could not suspend message ([dec]) or command ([dec]) queue Explanation The message or command queue could not be stopped prior to the OIR removal of the

SPA. Recommended Action If the ports on the SPA are not operating as expected, power down and reseat


Error Message %MCT1E1-3-SPI4_HW_ERR: SPA [dec]/[dec]: [chars] Hardware error was encountered. Explanation The SPA driver detected a hardware error condition on the SPA card’s SPI4 bus. This

condition might result in improper operation. Recommended Action Power down and reseat the specified SPA card. If the condition persists, copy

the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at


916

MCT1E1 Messages


Error Message %MCT1E1-3-TIMEOUT: %s: %s failed: %d, state: %d, ml_id: %d progress: %d Explanation Linkrec is stuck at non-ready. This condition indicates a software error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MCT1E1-3-UNCOR_MEM_ERR: SPA [dec]/[dec]: [dec] uncorrectable [chars] memory error(s) encountered. The memory address of the most recent error is: [hex] The SPA is being restarted. Explanation The SPA driver detected an uncorrectable memory error condition on the SPA card.

Packet corruption may result. The hexadecimal memory address of the most recent error is specified in the message text on the console or in the system log. Recommended Action Power down and reseat the specified SPA card. If this message recurs, copy the


Error Message %MCT1E1-3-UNCOR_PARITY_ERR: SPA [dec]/[dec]: [dec] [chars] parity error(s) encountered. Explanation The SPA driver detected an uncorrectable parity error condition on the SPA card. Packet

corruption may result. Recommended Action Power down and reseat the specified SPA card. If this message recurs, copy the

message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at


917

MCX Messages


MCX Messages This section contains Voice port adapter messages.

MCX-3 Error Message %MCX-3-FREEDMFATAL: Bay [dec]: freedm reset, command-status register [hex] Explanation CHOPIN experienced fatal freedm related problem. Recommended Action Copy the message exactly as it appears on the console or in the system log.


MDEBUG Messages This section contains memory debugging messages.

MDEBUG-2 Error Message %MDEBUG-2-ACCESSBEYONDSIZE: [hex] access beyond allocated size; ptr = [hex]; size = [dec]; actual size = [dec]; allocator_pc = [hex]; Traceback - [chars] Explanation The software attempted to access memory beyond the allocated size. Recommended Action Copy the message exactly as it appears on the console or in the system log.



918

MDR_SM Messages


Error Message M%DEBUG-2-ACCESSFREED: [hex] access freed memory; ptr = [hex]; size = [dec]; actual size = [dec]; allocator_pc = [hex]; free_pc = [hex]; Traceback [chars] Explanation The software attempted to access freed memory. Recommended Action Copy the message exactly as it appears on the console or in the system log.


MDR_SM Messages This section contains minimum disruption restart (MDR) state machine (SM) messages.

MDR_SM-3 Error Message %MDR_SM-3-INIT_FAIL: Initialisation error ’%s’ Explanation An error occurred during initialization of the minimum disruption restart (MDR) state

machine (SM). As a result, the MDR SM is inoperable. An MDR operation will probably result in the resetting of all line cards. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show monitor event-trace mdr_sm all commands and your pertinent troubleshooting logs.


919

MDR_SM Messages

Error Message %MDR_SM-3-SLOT_CLIENT_ID_ERROR: Can not find the data associated to client ID (%d) for slot (%d) Explanation The MDR state machine cannot find the data registered for the client ID. The client ID

is invalid. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MDR_SM-3-SLOT_CONTINUE_INVALID: Client (%d) returned an invalid status code on slot %d Explanation The MDR state machine client returned a status code that is invalid when returned on the standby device. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MDR_SM-3-SLOT_EVENT_TIMEOUT: MDR slot state machine %d did not receive the SLOT_UP event from the linecard Explanation The MDR slot state machine (SM) did not receive an expected event from the line card.

As a result, the state machine is inoperable for this slot. Recommended Action Copy the message exactly as it appears on the console or in the system log.



920

MDR_SM Messages

following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show monitor event-trace mdr_sm all commands and your pertinent troubleshooting logs.

Error Message %MDR_SM-3-SLOT_ID_MISMATCH: Client ID mismatch for slot %d during progression %s on client: %d, expecting %d Explanation The MDR state machine client returned a client ID that does not match the current client

ID. As a result, the MDR state machine will abort. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MDR_SM-3-SLOT_INVALID_ARG: Process is unable to get his slot number Explanation The MDR state machine process is unable to get the slot number of a slot supporting

MDR. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MDR_SM-3-SLOT_INVALID_EVENT: Slot (%d) received an unexpected event (%s) in state (%s) Explanation The MDR state machine received an unexpected event for the current state. Recommended Action Copy the message exactly as it appears on the console or in the system log.



921

MDR_SM Messages

representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show monitor event-trace mdr_sm all commands and your pertinent troubleshooting logs.

Error Message %MDR_SM-3-SLOT_NOTIFY_STANDBY_FAILED: Failed to notify Standby for MDR slot state machine (%d) Client %s (%d) in state %s Explanation The MDR state machine failed to notify the standby device. As a result, the MDR state

machine will abort. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MDR_SM-3-SLOT_NOTIFY_TIMEOUT: Notification timeout on MDR slot state machine %d for the local client %s (%d) in state %s Explanation The MDR state machine (SM) did not receive a response from the MDR SM client. As

a result, the state machine is inoperable. An MDR operation will probably result in the resetting of all line cards. Recommended Action Copy the message exactly as it appears on the console or in the system log.



922

MDR_SM Messages

Error Message %MDR_SM-3-SLOT_NO_FREE_EVENT_IN_QUEUE: The event queue is full for MDR Slot SM %d, MDR Slot SM %d will abort Explanation The MDR state machine (SM) was unable to get a free event from the event queue. As

a result, the state machine is inoperable. An MDR operation will probably result in the resetting of all the line cards. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MDR_SM-3-SLOT_STATUS_INVALID: Client %s (%d) on slot %d returned an unexpected status code (%d) Explanation The MDR state machine client returned an unexpected status code. An MDR operation

will probably result in the reset of all line cards. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MDR_SM-3-SYS_CLIENT_ID_ERROR: Can not find the data associated to client ID (%d) Explanation The MDR state machine cannot find the data registered for the client ID. The client ID

is invalid. Recommended Action Copy the message exactly as it appears on the console or in the system log.



923

MDR_SM Messages


Error Message %MDR_SM-3-SYS_CONTINUE_INVALID: Client (%d) returned an invalid status code Explanation The MDR state machine client returned a status code that is invalid when returned on the standby device. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MDR_SM-3-SYS_ID_MISMATCH: Client ID mismatch during progression %s on client: %d, expecting %d Explanation The MDR state machine client returned a client ID that does not match the current client



Error Message %MDR_SM-3-SYS_INVALID_EVENT: Received an unexpected event (%s) in state (%s) Explanation The MDR state machine received an unexpected event for the current state. Recommended Action Copy the message exactly as it appears on the console or in the system log.



924

MDR_SM Messages

http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show monitor event-trace mdr_sm all commands and your pertinent troubleshooting logs.

Error Message %MDR_SM-3-SYS_NOTIFY_STANDBY_FAILED: Failed to notify Standby for MDR system state machine Client %s (%d) in state %s Explanation The MDR state machine failed to notify the standby device. As a result, the MDR state

machine will abort. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MDR_SM-3-SYS_NOTIFY_TIMEOUT: Notification timeout on MDR system state machine for the local client %s (%d) in state %s Explanation The MDR state machine (SM) did not receive a response from the MDR SM client. As

a result, the state machine is inoperable. An MDR operation will probably result in the resetting of all line cards. Recommended Action Copy the message exactly as it appears on the console or in the system log.



925

MDR_SM Messages

Error Message %MDR_SM-3-SYS_NO_FREE_EVENT_IN_QUEUE: The event queue is full for MDR System SM, MDR SM will abort Explanation The MDR state machine (SM) was unable to get a free event from the event queue. As

a result, the MDR SM is inoperable. An MDR operation will probably result in the resetting of all the line cards. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MDR_SM-3-SYS_STATUS_INVALID: Client %s (%d) returned an unexpected status code (%d) Explanation The MDR state machine client returned an unexpected status code. An MDR operation



MDR_SM-4 Error Message %MDR_SM-4-QUIESCE_FAIL: Quiesce watchdog timer expired, continuing with MDR Explanation At the start of a switchover, the minimum disruption restart state machine (MDR SM)

on the old active RP enters the quiesce state. Because this state blocks the reload of the old active, the switchover is blocked during this state. To prevent a loss of service due to a bug in the MDR SM or one of its clients, a watchdog timer limits the duration of this state. Recommended Action Copy the message exactly as it appears on the console or in the system log.



926

MDR_SM Messages

http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show monitor event-trace mdr_sm all commands and your pertinent troubleshooting logs.

Error Message %MDR_SM-4-SLOT_CALLBACK_TOO_MUCH_TIME: MDR SM Slot %d client %s (%d) spent too much time (%d msecs) in state (%s) Explanation The MDR state machine has detected that one of its clients spent too much time in its

callback function. This is a warning message; the MDR state machine will continue. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MDR_SM-4-SYS_CALLBACK_TOO_MUCH_TIME: MDR SM SYS client %s (%d) spent too much time (%d msecs) in state (%s) Explanation The MDR state machine detected that one of its clients spent too much time in its




927

MDR_SM_LC Messages

Error Message %MDR_SM-4-UNBLOCK_RF: MDR SM aborted, continuing RF Progression (%d) Explanation The MDR state machine (SM) aborted due to an error in the MDR state machine or one

of its clients. The redundancy facility (RF) progression was blocked, but it will be unblocked to allow the standby device to boot. Recommended Action Copy the message exactly as it appears on the console or in the system log.


MDR_SM_LC Messages This section contains minimum disruption restart (MDR) state machine (SM) line card (LC) messages.

MDR_SM_LC-3 Error Message %MDR_SM_LC-3-ABORT: MDR state machine is aborted due to ’%s’ Explanation The minimum disruption restart (MDR) state machine (SM) aborted due to an

unrecoverable error. Any MDR operation will probably result in the resetting of this line card. Recommended Action Copy the message exactly as it appears on the console or in the system log.



928

MDR_SM_LC Messages

Error Message %MDR_SM_LC-3-ID_MISMATCH: Client ID mismatch during progression on client: %d, expecting %d Explanation The MDR state machine client returned a client ID that does not match the current client



Error Message %MDR_SM_LC-3-INIT_FAIL: Initialisation error ’%s’ Explanation During the MDR state machine (SM) initialization, an error occurred that has caused the MDR SM to be inoperable. Any MDR operation will probably result in the resetting of this line card. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MDR_SM_LC-3-INVALID_EVENT: MDR SM LC received an unexpected event (%s) in state (%s) Explanation The MDR state machine (SM) received an unexpected event for the current state. Recommended Action Copy the message exactly as it appears on the console or in the system log.



929

MDR_SM_LC Messages

Error Message %MDR_SM_LC-3-NOTIFY_TIMEOUT: Notification timeout for client %s(%d) in state %s Explanation During an MDR state machine (SM) state transition, the notification timer expired for

the client. Any MDR operation will probably result in the resetting of this line card. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MDR_SM_LC-3-NO_FREE_EVENT_IN_QUEUE: The event queue is full for MDR SM, MDR SM will abort Explanation The MDR state machine (SM) was unable to get a free event from the event queue. This

error has rendered the MDR SM inoperable. An MDR operation will probably result in the resetting of all the line cards. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MDR_SM_LC-3-SEMWAIT: MDR state machine waiting for semaphore(%s) acquired by pid(%d) Explanation The MDR state machine encountered a problem in acquiring a semaphore. Any MDR

operation will probably result in the resetting of this line card. Recommended Action Copy the message exactly as it appears on the console or in the system log.



930

MDR_SM_LC Messages


Error Message %MDR_SM_LC-3-STATUS_INVALID: Client %s (%d) returned an unexpected status code (%d) Explanation The MDR state machine client returned an unexpected status code. An MDR operation



MDR_SM_LC-4 Error Message %MDR_SM_LC-4-CALLBACK_TOO_MUCH_TIME: MDR SM LC client %s (%d) spent too much time (%d msecs) in state (%s) Explanation The minimum disruption restart (MDR) state machine (SM) has detected that one of its

clients spent too much time in its callback function. This is a warning message; the MDR state machine will continue. Recommended Action Copy the message exactly as it appears on the console or in the system log.



931

MDR_SM_PROXY Messages

MDR_SM_PROXY Messages This section contains minimum disruption restart (MDR) state machine (SM) proxy messages.

MDR_SM_PROXY-3 Error Message %MDR_SM_PROXY-3-NOTIFY_TIMEOUT: Notification timeout on MDR %s state machine for the remote client ’%s’ Explanation The minimum disruption restart (MDR) state machine (SM) proxy master did not

receive any response to the notification on its slave, and is now unable to communicate with the slave. As a result, the MDR SM is inoperable. An MDR operation will likely result in the resetting of all line cards. Recommended Action Copy the message exactly as it appears on the console or in the system log.


MDR_SM_PROXY-4 Error Message %MDR_SM_PROXY-4-SLOT_CALLBACK_TOO_MUCH_TIME: MDR SM Slot %d client (%d) spent too much time (%d msecs) in state (%s) Explanation The MDR state machine has detected that one of its clients spent too much time in its




932

MDS Messages

Error Message %MDR_SM_PROXY-4-SYS_CALLBACK_TOO_MUCH_TIME: MDR SM SYS client (%d) spent too much time (%d msecs) in state (%s) Explanation The MDR state machine has detected that one of its clients spent too much time in its



MDS Messages This section contains multicast distributed switching messages.

MDS-2 Error Message %MDS-2-LC_INVALID_HWIDB_INDEX: Invalid if_index for HWIDB [chars] Explanation The if_index parameter for the hardware IDB was invalid. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MDS-2-LC_INVALID_HWIDBQ_SIZE: Invalid Q count value Explanation The Q count parameter was invalid. Recommended Action Copy the message exactly as it appears on the console or in the system log.



933

MDS Messages


Error Message %MDS-2-LC_INVALID_SWIDB_IFNUM: Invalid if_num for SWIDB [chars] Explanation The if_index parameter for the software IDB was invalid. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MDS-2-LC_INVALID_SWIDBQ_SIZE: Invalid Q count value Explanation The Q count parameter was invalid. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MDS-2-LC_SWIDB_UPDATE_NULL_MVRF: LC received swidb update for if_number [hex] ([chars]) tableid [hex].mvrf pointer for this tableid is NULL. Explanation The line card received a software IDB update from the route processor specifying a

multicast VRF table ID for which no multicast VRF exists in the linecard. Recommended Action Copy the message exactly as it appears on the console or in the system log.



934

MDT Messages

MDS-4 Error Message %MDS-4-ROUTELIMIT_ATTEMPT: Attempt to exceed multicast route-limit of [dec] Explanation The number of multicast routes equals the configured maximum allowed. New routes

cannot be added unless the configuration is changed. Recommended Action If multicast traffic is of any priority among the traffic carried by this router,

then use the ip multicast route-limit command to increase the number of multicast routes. Otherwise, no action is required.

MDT Messages This section contains Multicast Distribution Tree (MDT) messages.

MDT-4 Error Message %MDT-4-LBSRC: MDT %s uses source address %i from a non-loopback interface Explanation The local peering interface used to set up an MDT tunnel is not a loopback interface. This may cause black holes if the interface is in the outgoing list of the MDT group. Recommended Action Change the configuration of the bgp update-source command and use a loopback interface as the local peering interface.

Error Message %MDT-4-NO_GROUP_LINK: MDT entry [chars]:([IP_address],[IP_address]) linked by source but not linked by group Explanation The entry for the affected MDT group was not properly linked into the MDT database.

The inconsistency has been repaired. [chars] is the MDT entry and the [IP_address],[IP_address] are the linked IP addresses. Recommended Action No action is required.

Error Message %MDT-4-RD_CONFLICT: MDT entry [chars]:([IP_address],[IP_address]) received an update for RD [chars] Explanation A previously existing MDT entry should have been withdrawn by BGP before sending

this conflicting update. [chars] is the MDT entry, the [IP_address],[IP_address] are the linked IP addresses, and the second [chars] is the redirect name. Recommended Action Copy the message exactly as it appears on the console or in the system log.



935

MDT Messages


Error Message %MDT-4-UPDATED_RD_CONFLICT: MDT entry %s:(%i,%i) received an update for RD %s Explanation The previously existing entry should have been withdrawn by BGP before sending this

conflicting update. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MDT-4-VRFSRC: The source interface of the MDT tunnels, %s, is not in the global table Explanation The local peering interface must not be an interface in a VRF. Recommended Action Change the configuration of the bgp update-source command and use a loopback interface in the global table.

MDT-5 Error Message %MDT-5-DATA_MDT_REUSED: Data MDT %i is reused Explanation If all pre-defined data MDT groups are used, a data MDT group can be reused by a

particular host that sources user traffic in an VPN. Recommended Action No action is required.


936

MDX Messages

MDX Messages This section contains MDX messages.

MDX-1 Error Message %MDX-1-DAEMSGSNDFAILED: FAILED to send IPC message of TYPE [chars] to slot [dec] on the DAE, FAIL REASON = [chars] Explanation An IPC message could not be sent. Retries to send the message were attempted and

failed. This condition does not affect system operation. Recommended Action No action is required.

Error Message %MDX-1-DAENODPENTRY: MDX framework could not find an entry for the DP with dp_id = [dec] on slot = [dec], on DAE Explanation IPC messages that were sent to the line card have been lost as the line card buffers were

being reassigned. As a result of this condition, the MDX DP failed to register. This condition does not affect system operation. Recommended Action Disable the SNMP query of the MIBs depending on the value of dp_id as

follows: If the dp_id is 1, disable the CISCO-ENHANCED-MEMPOOL-MIB SNMP query. If the dp_id is 2, disable the CISCO-PROCESS-MIB SNMP query. If the dp_id is 3, disable the CISCO-OPTICAL-MONITORING-MIB SNMP query. If the dp_id is 4, disable the CISCO-FABRIC-C12K-MIB SNMP query. You can replace the SNMP query with the CLI to obtain the same results. Enter one or more of the following CLI commands to obtain the required information: show processes memory, show processes cpu, show controller optics, show controller fia, show controller xbar or show controller sca.

Error Message %MDX-1-DAEPORTCREATEFAIL: Could not create IPC port for MDX framework on DAE, FAIL REASON = [chars] Explanation The IPC port for MDX framework on the Data Aggregator End (DAE) failed for the

reason specified in the message text. This condition does not affect system operation, except that the MDX framework will not be able to obtain the requested data from the MIBs. Recommended Action Enter one or more of the following CLI commands to obtain the required

information: show processes memory, show processes cpu, show controller optics, show controller fia, show controller xbar or show controller sca.


937

MDX Messages

Error Message %MDX-1-DAEPORTOPENFAIL: UNABLE to open port to primary RP FAIL REASON = [chars] Explanation The MDX Data Aggregator End (DAE) IPC port could not be opened, even after three

retry attempts. This condition does not affect system operation, except that the MDX framework will not be able to obtain the requested data from the MIBs. Recommended Action Enter one or more of the following CLI commands to obtain the required


Error Message %MDX-1-DAEPORTOPENFAILRETRY: UNABLE to open port to primary RP try number = [dec], FAIL REASON = [chars], Will retry again Explanation The MDX Data Aggregator End (DAE) IPC port could not be opened. The system will

attempt to retry the operation a maximum of three times. This condition does not affect system operation. Recommended Action No action is required.

Error Message %MDX-1-DPENTRYEXISTS: An entry already exists for the DP with dp_id [dec] on the DPE, could not create a new entry Explanation The DP entry that is attempting to be added already exists on the DPE. The new entry

could not be created. Recommended Action No action is required.

Error Message %MDX-1-DPEPORTOPENFAIL: UNABLE to open port to MDX framework on slot = [dec] from DAE, FAIL REASON = [chars] Explanation The MDX DPE (Data Provider End) IPC port could not be opened because of the reason

specified in the message text. This condition does not affect system operation. Recommended Action No action is required.

Error Message %MDX-1-DPREGFAILED: DP Registration with MDX framework failed on DPE Explanation The DP could not be registered with the MDX framework on the Data Provider End

(DPE). This condition does not affect system operation, except that the MDX framework will not be able to obtain the requested data from the MIBs. Recommended Action Enter one or more of the following CLI commands to obtain the required



938

MDX Messages

Error Message %MDX-1-IPCMSGSNDFAILED: FAILED to send IPC message of TYPE [chars] to DAE, FAIL REASON = [chars] Explanation The MDX component could not send the IPC message because of the reason specified

in the message text. This condition does not affect system operation. Recommended Action No action is required.

Error Message %MDX-1-IPCMSGUNAVAIL: Request for IPC buffer failed for size = [int] Explanation An IPC buffer request returned a null value. The IPC has exhausted its buffer space. This

condition does not affect system operation. Recommended Action Enter the ipc cache size command to increase the IPC buffer size.

Error Message %MDX-1-MSG: [chars] Explanation An internal error regarding the MDX facility has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MDX-1-NODPENTRY: MDX framework could not find an entry for the DP with dp_id = [dec] Explanation The entry for the DP does not exist in the MDX framework. A possible reason for this

error is that the DP has not registered with the framework. This condition does not affect system operation, except that the MDX framework will not be able to obtain the requested data from the MIBs. Recommended Action Enter one or more of the following CLI commands to obtain the required


Error Message %MDX-1-NOMGDTIMERCNTXT: The expired timer does not have a timer context Explanation MDX framework found a managed timer that does not have a context. This condition

does not affect system operation. Recommended Action No action is required.


939

MDX Messages

Error Message %MDX-1-PORTCREATEFAIL: Could not create IPC port for MDX Framework, FAIL REASON = [chars] Explanation An IPC port could not be opened for the MDX framework even after three retry

attempts. This condition does not affect system operation. Recommended Action No action is required.

Error Message %MDX-1-PORTCREATEFAILRETRY: Could not create IPC port for MDX framework try number = [dec], FAIL REASON = [chars], Will retry again Explanation An IPC port could not be created. The system will attempt to retry the operation a maximum of three times. Recommended Action This condition has no effect on system operation. No action is required.

Error Message %MDX-1-PORTREGFAIL: Could not Register IPC port for MDX framework FAIL REASON = [chars] Explanation The IPC port could not be registered with the IPC master, even after three retry attempts. This condition does not affect system operation. Recommended Action No action is required.

Error Message %MDX-1-PORTREGFAILRETRY: Could not Register IPC port for MDX framework try number = [dec], on slot = [dec], FAIL REASON = [chars], Will retry again Explanation The IPC port could not be registered with the IPC master. The system will attempt to

retry the operation a maximum of three times. Recommended Action This condition has no effect on system operation. No action is required.

Error Message %MDX-1-SIZEMISMATCH: Recieved an IPC message with inconsistent size compared to the MDX TU in its data region Explanation The size of the IPC message that was received by the MDX framework is not consistent

when it is compared to the MDX TU. This condition does not affect system operation. Recommended Action No action is required.

Error Message %MDX-1-UNKNOWNMSGTYPE: The rcvd msg-type is not supported, msg-type [chars] Explanation The message type that was received is not supported by the MDX framework. This

condition does not affect system operation. Recommended Action No action is required.


940

MEM_ECC Messages

MEM_ECC Messages This section contains messages about single and multiple bit and CPU write parity errors that have been detected by ECC control.

MEM_ECC-2 Error Message %MEM_ECC-2-MALLOC: Attempt to malloc [dec] bytes for the ECC error log failed. ECC errors will only be reported and not recorded. Explanation Memory could not be allocated for the ECC error log. If the system has only 32 MB of

memory, an upgrade is recommended. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MEM_ECC-2-MBE: Multiple bit error detected at [hex] Explanation A multi-bit error that could not be corrected was detected on a CPU that was read from

DRAM. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MEM_ECC-2-MBE_RMW: Multiple bit error detected at [hex] on a read-modify-write cycle Explanation A multi-bit error that could not be corrected was detected during a read-modify-write

cycle on a CPU that was read from DRAM for a non-8-byte access. Recommended Action Copy the message exactly as it appears on the console or in the system log.



941

MEM_ECC Messages


Error Message %MEM_ECC-2-PARITY: Parity error on CPU write to address: [hex] Explanation A data parity error was detected by the ECC Ctrl facility during a CPU write operation. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MEM_ECC-2-PARITY_INFO: Parity error was detected on the following byte(s) of a double word: [chars] [chars] [chars] Explanation This message specifies the bytes of a 64-bit word that contained invalid parity, and

caused the ECC Ctrl facility to generate an interrupt operation. Recommended Action Copy the message exactly as it appears on the console or in the system log.



942

MEM_ECC Messages

MEM_ECC-3 Error Message %MEM_ECC-3-BADADDR_MBE: Invalid MBE dram address: [hex] latched by ECC Ctrl Explanation The address that was found by the ECC control register while an MBE was being

detected is not a valid DRAM address. This condition probably indicates a malfunctioning ECC control register that requires replacement. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %MEM_ECC-3-BADADDR_MBE_RMW: Invalid MBE dram address: [hex] latched by ECC Ctrl during a RMW cycle Explanation The address that was found by the ECC control register while an MBE was being

detected during a read-modify-write cycle is not a valid DRAM address. This condition probably indicates a malfunctioning ECC control register that requires replacement. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MEM_ECC-3-BADADDR_SBE: Invalid SBE dram address: [hex] latched by ECC Ctrl Explanation The address that was found by the ECC control register while an SBE was being

detected is not a valid DRAM address. This condition probably indicates a malfunctioning ECC control register that requires replacement. Recommended Action Copy the message exactly as it appears on the console or in the system log.



943

MEM_ECC Messages


Error Message %MEM_ECC-3-BADADDR_SBE_RMW: Invalid SBE dram address: [hex] latched by ECC Ctrl during a RMW cycle Explanation The address that was found by the ECC control register while an SBE was being

detected during a read-modify-write cycle is not a valid DRAM address. This condition probably indicates a malfunctioning ECC control register that requires replacement. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MEM_ECC-3-SBE: Single bit error detected and corrected at [hex] Explanation A single-bit correctable error was detected on a read from DRAM. Recommended Action Enter the show ecc command to display the single-bit errors that have been

logged. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %MEM_ECC-3-SBE_HARD: Single bit *hard* error detected at [hex] Explanation A single-bit error that could not be corrected (a hard error) was detected on a CPU that was read from DRAM. Recommended Action Enter the show ecc command to display the single-bit errors that have been

logged and display the hard error address locations. Monitor the system by periodically entering the show ecc command and replace the DRAM if too many errors are encountered.


944

MEM_ECC Messages

Error Message %MEM_ECC-3-SBE_LIMIT: Single bit error detected and corrected at [hex] Explanation A single-bit correctable error was detected on a CPU that was read from DRAM. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MEM_ECC-3-SBE_RMW: Single bit error detected and corrected at [hex] on a read-modify-write cycle Explanation A single-bit correctable error was detected on during a read-modify-write cycle on a

CPU read from DRAM for a non-8-byte access. Recommended Action Enter the show ecc command to display the single-bit errors that have been


Error Message %MEM_ECC-3-SBE_RMW_HARD: Single bit *hard* error detected at [hex] on a read-modify-write cycle Explanation A single-bit uncorrectable hard error was detected during a read-modify-write cycle on

a CPU read from DRAM for a non-8-byte access. The show ecc command can be used to dump single-bit errors currently logged. Recommended Action Enter the show ecc command to display the single-bit errors that have been

logged and display the hard error address locations. Monitor the system by periodically entering the show ecc command and replace the DRAM if too many errors are encountered.


945

MEM_ECC Messages

Error Message %MEM_ECC-3-SBE_RMW_LIMIT: Single bit error detected and corrected at [hex] on a read-modify-write cycle Explanation A single-bit correctable error was detected on during a read-modify-write cycle on a

CPU read from DRAM for a non eight-byte access. Recommended Action Enter the show ecc command to display the single-bit errors that have been


Error Message %MEM_ECC-3-SYNDROME_MBE: 8-bit Syndrome for the detected Multi-bit error: [hex] Explanation A multi-bit error has been detected for the 8-bit syndrome. This value does not indicate

the exact positions of the bits in error, but can be used to approximate their positions. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MEM_ECC-3-SYNDROME_SBE: 8-bit Syndrome for the detected Single-bit error: [hex] Explanation A single-bit error has been detected for the 8-bit syndrome. This value does not indicate




946

MEM_MGR Messages

Error Message %MEM_ECC-3-SYNDROME_SBE_LIMIT: 8-bit Syndrome for the detected Single-bit error: [hex] Explanation A single-bit error has been detected for the 8-bit syndrome. This value does not indicate



MEM_MGR Messages This section contains memory manager (MEM_MGR) messages.

MEM_MGR-3 Error Message %MEM_MGR-3-MEM_MGR_EXCEED_MAX: memory pool exceeds maximum (%d bytes) allowed. Explanation An attempt was made to allocate a buffer from a memory pool that has reached its

maximum limit. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MEM_MGR-3-MEM_MGR_INVALID: The Memory Management code encounters an invalid parameter. Explanation The memory manager has received an invalid parameter from its caller. Recommended Action Copy the message exactly as it appears on the console or in the system log.



947

MEMPOOL Messages


Error Message %MEM_MGR-3-MEM_MGR_NOMEM: Out of memory Explanation The memory manager is out of memory. Recommended Action Copy the message exactly as it appears on the console or in the system log.


MEMPOOL Messages This section contains Enhanced Memory pool MIB messages.

Error Message %MEMPOOL-3-IPC: [chars] [chars] Explanation An IPC error has occurred on polling the Enhanced Mempool MIB. Recommended Action Copy the message exactly as it appears on the console or in the system log.



948

METOPT Messages

METOPT Messages This section contains Cisco Optical Networking Systems (ONS) 15540 Extended Services Platform (ESP) messages.

METOPT-2 Error Message %METOPT-2-NOPAKBUFFER: No packet buffer available for [chars] interface to send this packet to higher layer Explanation An attempt to allocate a packet buffer failed. Recommended Action Perform one or more of the following actions to remedy the problem:

- Reload the system. - Perform a CPU switchover if you have a redundant CPU system.

METOPT-6 Error Message %METOPT-6-DI_ASSERTED: CDL Defect Indication: [chars] Asserted on interface [chars] Explanation Some CDL Defect Indication bits were asserted on this interface. Recommended Action Closely monitor CDL Defect Indication Status if Defect Indication was

asserted.

Error Message %METOPT-6-DI_CLEARED: CDL Defect Indication: [chars] cleared on interface [chars] Explanation CDL Defect Indication Status changed. Recommended Action No action is required.


949

METOPT_DRV Messages

METOPT_DRV Messages This section contains Cisco Optical Networking Systems (ONS) 15540 Extended Services Platform (ESP) driver messages.

METOPT_DRV-3 Error Message %METOPT_DRV-3-REPROGRAM_ERROR: [chars] Explanation The Metro Optical Reprogram driver encountered an error. The error message contains

text useful to identify the cause of the problem. Recommended Action Retry the reprogramming of the card. If the reprogramming fails again, remove

the card and reinsert it. If the card does not come up, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

MFI Messages This section contains MPLS Forwarding Infrastructure (MFI) messages.

MFI-3 Error Message %MFI-3-BADREADUPDATESIZE: Read update reply message from RP has bad size: [dec] Explanation A read update message does not match the parsed result of the read message. Recommended Action Copy the message exactly as it appears on the console or in the system log.



950

MFI Messages

Error Message %MFI-3-EVTLOGCAPTURE: Event Logger Capture Error [dec] [dec] Explanation A failure occurred during an event logger capture operation. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MFI-3-EVTLOGCLIENT: Invalid client [dec] Explanation An invalid client has accessed the event logger. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MFI-3-EVTLOGCONTROL: [chars]: [dec] Explanation A general event logger controller error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



951

MFI Messages

Error Message %MFI-3-EVTLOGREGISTER: Event Logger Registration Error [dec] [dec] [dec] Explanation A failure occurred during an event logger client registration operation. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MFI-3-LCPULSE: LC pulse failed: [chars] [dec] Explanation A line card pulse request operation has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MFI-3-MFICOMM: [chars] Explanation An error involving the communications module has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



952

MFI Messages

Error Message %MFI-3-MFICOMM2: [chars]: [hex] [hex] Explanation An error involving the communications module has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MFI-3-MFICOMM3: [chars]: [hex] [hex] [hex] Explanation An error involving the communications module has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MFI-3-MPLS_MTU_SET: [chars] [dec] [chars] [chars] [chars] [dec][chars] Explanation Most drivers will be able to support baby giants and will gracefully drop packets that

are too large. Certain drivers will have packet forwarding problems including data corruption. Recommended Action Increase the interface MTU on all routers connected to this interface to the

needed MTU size by entering the mtu bytes command.

Error Message %MFI-3-NOCLIENTREQ: [chars] [chars]: [dec] [dec] [dec] Explanation The client reply component could not find an outstanding request. Recommended Action Copy the message exactly as it appears on the console or in the system log.



953

MFI Messages


Error Message %MFI-3-PNDMSGMGR: [chars] [chars] [dec] [dec] [dec] Explanation Only one outstanding request is allowed from a process. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MFI-3-REDISTMGR: Redistribution Manager: [chars] [hex] Explanation An error involving the redistribution manager has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MFI-3-REDISTMGR2: Redistribution Manager: [chars] [hex] [hex] Explanation An error involving the redistribution manager has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



954

MFI Messages

Error Message %MFI-3-REDISTMGR3: Redistribution Manager: [chars] [hex] Explanation An error involving the redistribution manager has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MFI-3-REPLYMSGSIZE: Reply message is too large: [chars]: [dec] Explanation A read update message is too large to fit into the XDR buffer. Recommended Action Copy the message exactly as it appears on the console or in the system log.


MFI-4 Error Message %MFI-4-MFICOMM4: [chars]: [hex] [hex] Explanation An error involving the communications module has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



955

MFIB Messages

MFIB Messages This section contains Multicast Forwarding Information Base (MFIB) messages.

MFIB-3 Error Message %MFIB-3-NETWORK_GET_FAIL: MFIB can not get network offset: datagram [hex]; network [hex] Explanation The MFIB failed to find a suitable packet network offset. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MFIB-3-NETWORK_SET_FAIL: MFIB can not set network offset: datagram [hex]; length [dec]; offset [dec] Explanation The MFIB failed to set the offset within a packet. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MFIB-3-NO_SBCTRLFUNC: A[chars] function is required for the MFIB sub-block, but none was provided Explanation The MFIB could not distribute interface information to a line card due to an internal




956

MFIB_CONST_LC Messages


Error Message %MFIB-3-SWITCHOVER_FAIL: Error creating [chars]. MFIB will not work with switchover Explanation Sufficient memory is not available to create structures needed to enable switchover for

IPv6 multicast. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

MFIB_CONST_LC Messages This section contains MFIB Constellation platform messages.

Error Message %MFIB_CONST_LC-6-ADJ_V6MCAST_ALLOC_FAILURE: Failed to allocate Adjacency for IPv6 multicast entry (S[ipv6_addr], G[ipv6_addr]) Explanation The system was unable to allocate an adjacency for this particular flow. The affected

flow will be retried and will be software switched until it is successfully installed in the hardware. Recommended Action The adjacency table utilization could be very high and need to be brought

down. Removing some hardware switched flows would help solve the problem

Error Message %MFIB_CONST_LC-6-FIB_V6MCAST_INSTALL_FAILURE: Failed to install FIB IPv6 multicast entry (S[ipv6_addr], G[ipv6_addr]) Explanation The FIB entry limit has been exceeded so FIB entries cannot be allocated by the

MFIB_CONST_LC. Recommended Action The FIB table utilization is too high and needs to be reduced. The total number

of multicast shortcuts is too large to fit in the FIB table. As a result, subsequent shortcuts will be software switched. Reducing the FIB utilization by other protocols would help solve the problem.

Error Message %MFIB_CONST_LC-6-MET_V6MCAST_ALLOC_FAILURE: Failed to allocate MET entries for IPv6 multicast entry (S[ipv6_addr], G[ipv6_addr]) Explanation The system is unable to allocate MET entries for this particular flow. The affected flow

will be retried and will be software switched until it is successfully installed in the hardware. Recommended Action The MET utilization could be very high and must be reduced. Removing some hardware switched flows would help solve the problem


957

MFIB_CONST_RP Messages

Error Message %MFIB_CONST_LC-6-NF_V6MCAST_INSTALL_FAILURE: Failed to install Netflow IPv6 multicast entry (S[ipv6_addr], G[ipv6_addr]) Explanation A multicast entry could not be installed due to a NetFlow full condition or a Hash

collision. Recommended Action The NetFlow table utilization is too high and needs to be reduced. The total

number of multicast shortcuts are too large to fit in the NetFlow table. As a result, these shortcuts will be software switched. Removing dynamically created NetFlow IPv6 entries or disabling dynamic NetFlow entry creation would help solve the problem.

Error Message %MFIB_CONST_LC-6-SW_V6MCAST_INSTALL_FAILURE: Failed to install IPv6 multicast entry, due to [chars] (S[ipv6_addr], G[ipv6_addr], C:[dec]) Explanation The system is unable to install an IPv6 multicast entry due to unrecoverable software

failures. Recommended Action Copy the message exactly as it appears on the console or in the system log.


MFIB_CONST_RP Messages This section contains MFIB Constellation information messages.

Error Message %MFIB_CONST_RP-6-REPLICATION_MODE_CHANGE: Replication Mode Change Detected. Current system replication mode is [chars] Explanation When automatic detection of the replication mode is enabled, the system will transition

to ingress mode when an egress-incapable line card is inserted. The system will transition back to egress mode when the last egress-incapable line card is removed. The transition between ingress and egress modes will cause temporary loss of traffic. Recommended Action To prevent traffic loss, enter the ipv6 mfib hardware-switching

replication-mode ingress command.


958

MFIB_STATS Messages

MFIB_STATS Messages This section contains MFIB statistics messages.

Error Message %MFIB_STATS-2-MFIB_STATS_LC_FAILED_GET_COUNTERS: Linecard failed in getting counters due to null table. af = [int], v6 def tbl [hex], v4 def tbl [hex] Explanation The line card has failed to get entry counters due to a null table. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MFIB_STATS-2-MFIB_STATS_LC_FAILED_GET_IPC_MSG: Linecard failed allocating ipc message buffer Explanation The line card failed to allocate a buffer for sending statistics. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MFIB_STATS-2-MFIB_STATS_LC_FAILED_SEND_MSG: Linecard failed in sending msg to the Route Processor error = [chars] Explanation The line card has failed to send a statistics message to the route processor. Recommended Action Copy the message exactly as it appears on the console or in the system log.



959

MFIB_STATS Messages

Error Message %MFIB_STATS-2-MFIB_STATS_LC_MSG_TOO_BIG: Linecard failed to return counters, message buffer too small. Explanation The line card has failed to return counters because the minimum message size exceeds

the maximum IPC buffer size. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MFIB_STATS-2-MFIB_STATS_RP_FAILED_GET_IPC_MSG: RP failed allocating ipc message buffer for linecard, slot = [dec] Explanation The route processor failed to allocate a buffer for getting line card statistics. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MFIB_STATS-2-MFIB_STATS_RP_FAILED_REPLY_MSG: RP received reply with error status from linecard, slot = [dec] Explanation The route processor has received a reply with error in statistics message from a line

card. Recommended Action Copy the message exactly as it appears on the console or in the system log.



960

MISA Messages

Error Message %MFIB_STATS-2-MFIB_STATS_RP_SEQ_ERROR: The RP ignored out of sequence per-interface statistics returned by the linecard in slot [dec]. Explanation A line card returned per-interface statistics in the wrong order and the RP has ignored

them. Recommended Action Copy the message exactly as it appears on the console or in the system log.


MISA Messages This section contains Multiple Crypto Engine subsystem messages.

Error Message %MISA-1-ERROR: [chars] Explanation An error occurred in the application using ISA. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MISA-6-INFO: [chars] Explanation This is an informational message from ISA. Recommended Action This is an informational message only and occurs in normal operation. No

action is required.


961

MISTRAL Messages

MISTRAL Messages This section contains Mistral ASIC (MISTRAL) messages.

MISTRAL-3 Error Message %MISTRAL-3-BAD_PAK: Possibly un-encapsulated packet passed to Mistral: int [chars] type [int] stat [hex] flags [hex] size [dec] encsize [dec] offset [dec] requeue_token [int] r1 [int] r2 [int] total detected [int] Explanation A badly encapsulated packet from the process level was passed to the Mistral ASIC. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MISTRAL-3-NOEOBCBUF: No EOBC buffer available. Dropping the packet. Explanation The Ethernet out-of-band channel pool of receive buffers for the Mistral ASIC has been

exhausted. No additional input packets can be handled until some buffers are returned to the pool. Recommended Action Copy the message exactly as it appears on the console or in the system log.



962

MLD_PROT Messages

MLD_PROT Messages This section contains Multicast Listener Discovery (MLD) protocol messages.

Error Message %MLD_PROT-6-IDB_ENABLE: Interface [chars] does not support multicast, not enabled Explanation IGMP/MLD is not enabled on the specified interface that does not support multicast. Recommended Action This is an informational message only. No action is required.

MLI Messages This section contains Memory Layout Information (MLI) messages.

MLI-3 Error Message %MLI-3-NOT_ENOUGH_SPACE: There is not enough space in Memory Layout Information area to store the tuple Explanation Insufficient memory is reserved in the Memory Layout Information (MLI) area to store

the given MLI tuple data. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show mli commands and your pertinent troubleshooting logs.


963

MLS_ACL_COMMON Messages

MLS_ACL_COMMON Messages This section contains Multilayer Switching ACL (MLS_ACL_COMMON) messages.

MLS_ACL_COMMON-3 Error Message %MLS_ACL_COMMON-3-MLS_ACL_CONSIST_FIX: ACL TCAM inconsistency seen at index [dec] and could not be fixed Explanation The ACL TCAM inconsistency checker found an inconsistency between software and

hardware TCAM entries and could not fix it. [dec] is the index where the inconsistency was found. Recommended Action If this message recurs, copy the message exactly as it appears on the console


MLS_ACL_COMMON-4 Error Message %MLS_ACL_COMMON-4-LOG_UPDATE_NO_RL: ACL TCAM update ([chars] direction) occured on interface [chars]; [chars] action taken [chars] msec Explanation An update of the ACL TCAM occurred on the specified interface. When the ACL

TCAM is updated, the specified security action is taken for the specified time interval. Recommended Action If this message recurs, copy the message exactly as it appears on the console



964

MLSCEF Messages

Error Message %MLS_ACL_COMMON-4-LOG_UPDATE_RL: ACL TCAM update ([chars] direction) occured on interface [chars]; [chars] action taken [chars] msec Explanation An update of the ACL TCAM occurred on the specified interface. When the ACL

TCAM is updated, the specified security action is taken for the specified time interval. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %MLS_ACL_COMMON-4-MLS_ACL_CONSIST: ACL TCAM inconsistency seen at index [dec] Explanation The ACL TCAM inconsistency checker found an inconsistency between software and

hardware TCAM entries and has fixed it. [dec] is the index where the inconsistency was found. Recommended Action If this message recurs, copy the message exactly as it appears on the console


MLSCEF Messages This section contains Multilayer Switching Cisco Express Forwarding (MLSCEF) messages.

MLSCEF-2 Error Message %MLSCEF-2-EXCESSIVE_FIB_CORR_SSRAM_ERRORS: Too many fib correctable ecc error interrupts. Explanation The number of correctable error interrupts has exceeded the threshold of 1000

correctable ECC errors in 30 minutes. All errors were corrected. Recommended Action Copy the message exactly as it appears on the console or in the system log.



965

MLSCEF Messages

information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show mls cef hardware, show mls cef log, and show ver commands and your pertinent troubleshooting logs.

Error Message %MLSCEF-2-EXCESSIVE_FIB_SSRAM_ERRORS: Too many fib ecc error interrupts. Explanation The number of error interruptions exceeded the threshold. As a result of this condition, the system will fail. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MLSCEF-2-FIB_SSRAM_WRITE_INCONSISTENCY: FIB SSRAM Mismatch for Index: [dec] Expected: [hex], Hardware: [hex] Explanation A problem occurred when the system attempted to write the FIB SSRAM. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MLSCEF-2-FIB_TCAM_WRITE_INCONSISTENCY: FIB TCAM Mismatch for [chars]: Index: [dec] Exprected:Entry: [hex]-[hex]-[hex] Hardware: Entry: [hex]-[hex]-[hex] Explanation A problem occurred when the system attempted to write the FIB TCAM. Recommended Action Copy the message exactly as it appears on the console or in the system log.



966

MLSCEF Messages


Error Message %MLSCEF-2-RELOAD: maximum routes config mismatch. Reloading with correct config Explanation The system detected a mismatch between the user configuration route allocation and the

current route allocation. A system reload is required to correct this condition. Recommended Action If the message does not appear continuously and the mls cef maximum-routes

command has been entered, no action is required. If this message appears continuously on the same module and the mls cef maximum-routes command has not been entered, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %MLSCEF-2-SANITY_FAIL: Sanity Check of MLS FIB s/w structures failed Explanation The verification process encountered inconsistent MLS FIB data structures. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MLSCEF-2-UNCORRECTABLE_SSRAM_ERROR: Bank [dec] Index: [dec], Expected: [hex], Hardware: [hex]. Affected TCAM [hex]-[hex]-[hex] Explanation A faulty FIB SSRAM location was detected. Recommended Action Copy the message exactly as it appears on the console or in the system log.



967

MLSCEF Messages


MLSCEF-4 Error Message %MLSCEF-4-FIB_EXCEPTION_THRESHOLD: Hardware CEF entry usage is at 95% capacity for [chars] protocol. Explanation The number of route entries that are installed is about to reach the hardware FIB

capacity, or the maximum routes limit set for the specified protocol. If the limit is reached, some prefixes will be software switched. Recommended Action Enter the mls cef maximum-routes [protocol] global configuration command

to increase the maximum number of routes for the protocol. Refer to the configuration manuals for the differing capacity limitations of XL versus non-XL systems, as well as for impacts to other protocols when changing maximum routes of one protocol. Enter the show mls cef summary command to see the current usage summary.

Error Message %MLSCEF-4-INCORRECT_CONFIG: A max-routes configuration mismatch or an invalid max-routes configuration has been detected. Reverting to default configuration. Explanation The system has detected a configuration mismatch or an invalid configuration for the

mls cef maximum-routes command, and is reverting to the system default configuration. Recommended Action Reconfigure your maximum routes using the mls cef maximum-routes command. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


968

MLS_CEF_ISSU Messages

MLSCEF-7 Error Message %MLSCEF-7-FIB_MASK_MISMATCH: Attempt to delete an entry not matching block mask - class = [dec], [dec]/[dec], mask [dec]/[dec] Explanation The passed mask does not match the stored block mask. Recommended Action This is a debug message only. No action is required.

MLS_CEF_ISSU Messages This section contains Multilayer Switching Cisco Express Forwarding (MLSCEF) in-service software upgrade (ISSU) messages.

MLS_CEF_ISSU-2 Error Message %MLS_CEF_ISSU-2-MLS_CEF_RETRY_FAIL: Unable to get maximum routes config from Active RP. Explanation The ISSU process was unable to get the maximum route configuration from the active

RP. The system will configure to default values. Recommended Action Reload the system. If the problem persists, copy the message exactly as it



969

MLSM Messages

MLSM Messages This section contains Multicast Distributed Shortcut Switching (MDSS)/multilayer switching for multicast (MLSM) messages.

MLSM-4 Error Message %MLSM-4-CC_ERROR: (Type of CC: [chars]): [chars] ([IP_address],[IP_address]), Auto-repair is [chars] Explanation Either the RP-SP or MROUTE-MLSM consistency checker has detected an error. Recommended Action If enabled, the autorepair feature will automatically correct the error.

Error Message %MLSM-4-MLSM_LTL_FULL_VDB_CREATE_FAILED: Multi-Layer Switching for Multicast: Disabling Multicast Hardware Switching for VLAN ([dec]), VLAN not found on Switch Processor Explanation The switch processor is unable to create VLANs due to a Layer 2 hardware limitation.

Because no VLAN information is available, the switch processor is unable to install shortcuts. Multicast hardware switching for this VLAN interface will be disabled to avoid installation of shortcuts. All flows using this VLAN as the outgoing interface will be affected. Recommended Action Modify the network configuration to increase the hardware resources for

creating VLANs on the switch processor.

MLSM-6 Error Message %MLSM-6-BIDIR_SC_INSTALL_FAILURE: Bi-dir multicast flows will not be installed in hardware in the presence of tunnel interfaces for RP [IP_address] Explanation Bidirectional multicast flows will not be installed in hardware in the presence of tunnel

interfaces. The bidirectional flows will be software-switched until the tunnel interfaces are unconfigured. Recommended Action Unconfiguring the tunnel interfaces will allow the bidirectional flows to be

hardware-switched.

Error Message %MLSM-6-MLSM_PMS: MMLS: MLSM is suspending the caller process [chars] Explanation MLSM is suspending the caller process. This message appears when the MLSM

routines are called from the PIM/Mwheel context and MLSM routines suspend a process. When MLSM suspends the caller process, data corruption might occur for the data that is handled by the caller process. Recommended Action This message is informational. No action is required.


970

MLSM Messages

Error Message %MLSM-6-MMLS_EGRESS_INFO: MMLS: Please make sure no multicast traffic is going through egress incapable line cards when system is operating in egress mode Explanation There should be no multicast traffic going through egress-incapable line cards while the

system is operating in egress replication mode. Recommended Action Determine if there are any egress-incapable line cards in the system. If there

are egress-incapable line cards, verify that there is no multicast traffic going through them.

Error Message %MLSM-6-MMLS_LEGACY_INSERTED: MMLS: Legacy Linecard Inserted, Egress Replication Mode will be disabled Explanation Egress replication is not supported with legacy modules. The system will transition to

ingress mode and will cause a temporary loss of traffic. Recommended Action If the system is required to operate in egress replication mode, remove the

legacy module.

Error Message %MLSM-6-MMLS_MDT_TUNNEL_UP: MMLS: MDT tunnel is up, Egress Replication Mode will be disabled Explanation Egress replication is not supported when MDT is configured and an MDT tunnel is up.

The system will transition to ingress mode if required, and the transition will cause a temporary loss of traffic. Recommended Action This message is informational. No action is required.

Error Message %MLSM-6-MMLS_MODE_CHANGE: MMLS: Replication Mode Change Detected Explanation When automatic detection of the replication mode is enabled, the system will transition

to ingress mode when an egress-incapable module is inserted. The system will transition back to egress mode when the last egress-incapable module is removed. Recommended Action Transitioning between ingress and egress mode causes a temporary loss of

traffic. To prevent this temporary loss of traffic, enter the mls ip replication-mode ingress command.

Error Message %MLSM-6-MMLS_NO_EGRESS_LOCAL_IN_INGRESS: MMLS: Egress Local feature is NOT applicable in Ingress mode Explanation When the system transitions from egress replication mode to ingress mode, the egress

local feature will not be applied, even if the egress local feature is enabled. Recommended Action If the egress local feature is required, restore the system replication mode to

egress.


971

MLS_RATE Messages

MLS_RATE Messages This section contains Multilayer Switching Rate Limit (MLS_RATE) messages.

MLS_RATE-4 Error Message %MLS_RATE-4-CPP_DISABLED_IN_HW: Control Plane Policing NOT performed in hardware, due to the presence of egress QoS. Explanation CPP cannot be performed in the hardware when the system is running in PFC3A mode

and egress QoS is configured on any other interface. Under these circumstances, CPP is performed only in the software until egress QoS is removed from the running configuration. Recommended Action Remove any egress QoS from the running configuration, or upgrade to a

PFC3B or PFC3-BXL. We strongly recommend the upgrade.

Error Message %MLS_RATE-4-CPP_RE_ENABLED_IN_HW: Control Plane Policing will now be performed in hardware. Explanation CPP cannot be performed in the hardware when the system is running in PFC3A mode

and egress QoS is configured on any other interface. Egress QoS has been removed from the running configuration. Recommended Action Because egress QoS has been removed, no action is required. To prevent this

condition from occurring again, we strongly recommend that you upgrade to a PFC3B or PFC3BXL.

Error Message %MLS_RATE-4-DISABLING: The Layer2 Rate Limiters have been disabled. Explanation The Layer 2 rate limiters are turned off with the current hardware configuration because

they are not supported with this combination of modules. Recommended Action Refer to the feature usage guidelines for more details.

Error Message %MLS_RATE-4-LIMITING_DOWN: MLS HARDWARE RATE-LIMITING functionality is not active Explanation Memory resources are insufficient to support the rate-limiting functionality. Recommended Action Copy the message exactly as it appears on the console or in the system log.



972

MLS_RATE Messages

Error Message %MLS_RATE-4-NO_DHCP_RESOURCE: DHCP Snooping requires 2 Rate Limiters Explanation There are not enough hardware rate limiters to enable DHCP snooping. Recommended Action DHCP snooping requires two hardware rate limiters. All may be used. To

display the features that use these hardware rate limiters, enter the show mls rate-limit usage command. Unconfigure enough rate limiters to configure DHCP snooping.

Error Message %MLS_RATE-4-NO_RESOURCE: The hardware Rate Limiters are fully used Explanation There are no more hardware rate limiters available. Recommended Action EARL supports a limited number of hardware rate limiters. All may be used.

To display the features that use these hardware rate limiters, enter the show mls rate-limit usage command. To program a rate limiter for the new feature, unconfigure one of the configured rate limiters.

Error Message %MLS_RATE-4-NOT_SUPPORTED: This functionality is not configurable. Explanation The rate limit functionality is not active with the current hardware configuration. Recommended Action Refer to the feature usage guidelines for more details.

Error Message %MLS_RATE-4-OVERWRITING_PORTSEC_DEFAULT: Port security rate limiter was set to non-default value. Explanation Overwriting the default port security rate value. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %MLS_RATE-4-OVERWRITING_VALUE: Overwriting the rate value for: [chars] case Explanation Some rate limiters share the same hardware register. This message appears if

programming a new rate limiter causes a previously configured one to be overwritten. Recommended Action Copy the message exactly as it appears on the console or in the system log.



973

MLS_STAT Messages


MLS_STAT Messages This section contains Multilayer Switching Statistics (MLS_STAT) messages.

MLS_STAT-4 Error Message %MLS_STAT-4-IP_CSUM_ERR: IP checksum errors Explanation Packets with IP checksum errors have been received. Recommended Action No action is necessary. This message is for informational purposes only.

Error Message %MLS_STAT-4-IP_LEN_ERR: MAC/IP length inconsistencies Explanation Packets with an IP length that does not match their physical length have been received. Recommended Action No action is necessary. This message is for informational purposes only.

Error Message %MLS_STAT-4-IP_TOO_SHRT: Too short IP packets received Explanation Packets with IP minimum length check errors have been received. Recommended Action No action is necessary. This message is for informational purposes only.

Error Message %MLS_STAT-4-IPX_LEN_ERR: MAC/IPX length inconsistencies Explanation Packets with an IPX length that does not match their physical length have been received. Recommended Action No action is necessary. This message is for informational purposes only.

Error Message %MLS_STAT-4-IPX_TOO_SHRT: Too short IPX packets received Explanation Packets with IPX minimum length check errors have been received. Recommended Action No action is necessary. This message is for informational purposes only.


974

MMLS Messages

MMLS Messages This section contains Multicast Multilayer Switching (MMLS) messages.

MMLS-3 Error Message %MMLS-3-ICROIF_BLOCK_ALLOC_FAILED: Allocation of %s block of indices for egress distribution over fabric failed Explanation The allocation of the block of indices used for egress distribution over the fabric has

failed. As a result, the system will not be able to work in egress replication mode. This condition could be caused by a shortage of hardware resources during boot up or at the time when the first block of indices is completely consumed. A shortage of hardware resources might be caused by having too many VLANs configured. Recommended Action Reduce the number of VLANs in the system by entering the no vlan {vlan_id} command and reloading the system, or configure ingress replication mode by entering the mls ip multicast replication-mode ingress command. Ingress replication mode does not use egress distribution indices.

MMLS-4 Error Message %MMLS-4-ICROIF_INDICES_EXHAUSTED: Unable to allocate index for egress distribution over fabric Explanation The indices used for egress distribution over the fabric are exhausted and the system is

currently unable to allocate an index. An index is allocated for each unique combination of flow over the fabric and is not freed upon removal of all shortcuts using it. An index-freeing mechanism operates when a threshold for freeing up unused indices is reached. If the number of used indices stays above the threshold after collection of unused indices, another block (up to a maximum of two blocks) of 256 indices is allocated. Recommended Action You may not be required to take any action, as the index-freeing mechanism

should take care of freeing up unused indices. If the problem remains, try reducing the number of unique combination of flows over the fabric created by the presence of multicast sources and receivers on different line cards.

Error Message %MMLS-4-VLAN_2K_SR_TR_INSTALL_FAILED: Multicast Multi-Layer Switching: Failed to install service reflect translation, hardware resource unavailable Explanation The Multicast Service Reflect translation cannot be installed in hardware as a required

hardware resource is unavailable. Recommended Action Removing tunnel interfaces or reducing the number of service reflect

translations would help solve the problem.


975

MMLS Messages

MMLS-6 Error Message %MMLS-6-ADJ_ALLOC_FAILURE: Failed to allocate Adjacency for the multicast flow ([IP_address], [IP_address]) Explanation The system is unable to allocate an adjacency for this particular flow. The affected flow

will be retried and will be software switched until it is successfully installed in the hardware. Recommended Action The adjacency table utilization could be very high and needs to be reduced.

Removing some hardware switched flows would help solve the problem.

Error Message %MMLS-6-BIDIR_ADJ_LIMIT_EXCEEDED: Failed to allocate Adjacency for Bidir Multicast shortcuts, exceeded limit of ([dec]), subsequent flows will be software switched. Explanation The system limit of maximum adjacencies for bidirectional shortcuts has been

exceeded. As a result, any new multicast flows will be switched by the software. Recommended Action The number of bidirectional multicast flows is too large to fit in the hardware. There is no workaround.

Error Message %MMLS-6-FIB_LIMIT_EXCEEDED: Failed to allocate FIB entry, exceeded system limit of ([dec]) entries. Explanation The maximum FIB entry limit has been exceeded, so FIB entries cannot be allocated by

the MMLS. Recommended Action The total number of multicast shortcuts is too large to fit in the FIB table and

as a result subsequent shortcuts will be software switched. There is no workaround.

Error Message %MMLS-6-MCAST_L3FLOW: %s from the Route Processor for Source %i Group %i vlan %d Explanation A multicast flow has been installed or deleted. Recommended Action No action is required.

Error Message %MMLS-6-MCAST_STATUS: IP Multicast Multilayer Switching is %sabled Explanation This message indicates whether the multicast Layer 3 multicast feature is enabled or

disabled. Recommended Action No action is required.


976

MMLS Messages

Error Message %MMLS-6-MET_LIMIT_EXCEEDED: Failed to allocate MET entry, exceeded system limit of ([dec]) entries. Number of times MET limit is exceeded in the last 1 min : [dec] Explanation The maximum MET entry limit has been exceeded, so MET entries cannot be allocated

by the MMLS. Recommended Action The total number of OIFs is too large to fit in the MET table. Subsequent

shortcuts or OIFs will be switched by the software. There is no workaround.

Error Message %MMLS-6-MMLS_EGRESS_INCAPABLE_LC_INSERTED: MMLS: Egress incapable line card ([dec]) inserted in forced egress replication mode Explanation An egress-incapable line card is inserted while the system is operating in forced egress replication mode. The user must not source any multicast traffic on this egress-incapable line card. Recommended Action Verify that there is no multicast traffic going through this egress-incapable line

card.

Error Message %MMLS-6-MMLS_EGRESS_INCAPABLE_LC_PRESENT: MMLS: Egress incapable line card present while forcing replication mode to egress Explanation There is at least one line card that is egress incapable in the system, but forced egress

replication mode is configured on the system. Multicast traffic must not be sourced on the egress-incapable line card. Recommended Action Verify that there is no multicast traffic going through this egress-incapable line

card.

Error Message %MMLS-6-MMLS_FSTATS_MAX_PENDING_MSGS: Flow stats enqueued messages count([dec]) has reached the maximum and would be reset to [dec] Explanation This message indicates that flow stats pending messages count has reached the

maximum. To avoid further flow stats messages from being dropped, the counter would be reset to match the current pending messages count of the ICCQ. Recommended Action This message is provided for information only.

Error Message %MMLS-6-MMLS_HALF_MET: MMLS: IPv6 multicast enabled on supervisor uplinks. Available MET space on supervisors is halved Explanation The MET space is being halved to enable IPv6 on supervisor engine uplinks. Recommended Action No action is required.


977

MMLS Messages

Error Message %MMLS-6-MMLS_LEGACY_LC_PRESENT: MMLS: Legacy line card present, system cannot operate in egress replication mode Explanation There is at least one legacy line card in the system. Therefore, the system cannot operate

in egress replication mode when the system is configured for forced egress replication mode. Recommended Action Remove the legacy line card(s) if you want the system to operate in forced egress replication mode.

Error Message %MMLS-6-RPF_ADJ_LIMIT_EXCEEDED: Failed to allocate Adjacency for multicast shortcuts with RPF-vlan: ([dec]), exceeded limit of ([dec]), subsequent flows will be software switched Explanation The system limit of maximum adjacencies for multicast shortcuts with the same RPF

has been exceeded. As a result, any new multicast flows will be software switched. Recommended Action The number of multicast flows with the same RPF interface are too large to fit

in the hardware. There is no workaround.

Error Message %MMLS-6-RP_LIMIT_EXCEEDED: Failed to allocate DF index for Bidir-RP, exceeded limit of ([dec]) RPs for VPN: ([dec]). Shortcuts for RP: ([IP_address]) will be software switched. Explanation The system limit of four RPs per VPN has been exceeded. As a result, the multicast

flows for the groups served by this RP will be software-switched. Recommended Action The configured RPs are too large to fit in the DF table for one VPN. Attempt

to configure the groups among existing RPs in hardware, or configure the RP in another VPN.

Error Message %MMLS-6-VLAN_ADD_FAILURE_ON_MET_FULL: Error adding vlan [dec] to the MET table of some shortcuts Explanation The MET table is full and the system is unable to add the VLAN to some shortcuts. The affected shortcuts will not switch traffic for that VLAN. Recommended Action The MET utilization is very high and must be reduced. Removing some

VLANs or switching to ingress replication mode will solve the problem.


978

MMLS_RATE Messages

MMLS_RATE Messages This section contains Multicast Multilayer Switching Rate Limiting (MMLS_RATE) messages.

MMLS_RATE-3 Error Message %MMLS_RATE-3-MMLS_PARTIAL_SC_ERROR: Error installing Multicast Partial-sc rate-limiter.Operation failed. Explanation The multicast partial SC rate limiter could not be configured because of an error that

was returned from the switch processor. Recommended Action The LTL index for the partial SC rate limiter might not have initialized yet.

Wait several minutes, and try to configure the rate limiter again.

MPLS_ADJ_SB Messages The following are MPLS Adjacency Subblock messages.

MPLS_ADJ_SB-4 Error Message %MPLS_ADJ_SB-4-NO_BACKUP_INTF: [chars] - ifnum [dec] Explanation Backup interface cannot be programmed. Recommended Action Copy the error message exactly as it appears on the console or in the system



979

MPLS_IPRM Messages

MPLS_IPRM Messages This section contains MPLS IP rewrite manager (IPRM) messages.

MPLS_IPRM-3 Error Message %MPLS_IPRM-3-DB: [chars] Explanation There is an inconsistency in the information required to request labels from or to process

labels received from an IP label distribution module. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MPLS_IPRM-3-DB_PATH: [chars] Explanation There is an inconsistency in the information about a prefix path required to request

labels from or to process labels received from an IP label distribution module. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MPLS_IPRM-3-DB_PNDG_DISC: [chars] Explanation There is an inconsistency in the information about a temporarily deferred action

required to populate MPLS forwarding data structures for a prefix. Recommended Action Copy the message exactly as it appears on the console or in the system log.



980

MPLS_IPRM Messages


Error Message %MPLS_IPRM-3-DB_TABLE: [chars] Explanation There is an inconsistency in the information about a (VRF) table ID required to request labels from or to process labels received from an IP label distribution module. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MPLS_IPRM-3-DB_TRANS: [chars] Explanation There is an inconsistency in the information about an ongoing transaction required to

populate MPLS forwarding data structures for a prefix. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MPLS_IPRM-3-INTERNAL: [chars] Explanation An operation required for proper operation of the IP rewrite manager has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



981

MPLS_IPRM Messages

Error Message %MPLS_IPRM-3-PATH_LABEL_DEL: [chars] Explanation An attempt to delete MPLS forwarding information for the specified prefix has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MPLS_IPRM-3-PATH_LABEL_GET: [chars] Explanation An attempt to access MPLS forwarding information for the specified prefix has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MPLS_IPRM-3-PATH_LABEL_UPD: [chars] Explanation An attempt to update MPLS forwarding information for the specified prefix has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



982

MPLSMFISTATIC Messages

Error Message %MPLS_IPRM-3-WALK: [chars] Explanation A request by an IP label distribution module (for example, LDP, BGP) to walk a CEF

table cannot be handled. Recommended Action Copy the message exactly as it appears on the console or in the system log.


MPLSMFISTATIC Messages This section contains MPLS Forwarding Infrastructure (MFI) static application messages.

MPLSMFISTATIC-3 Error Message MPLSMFISTATIC-3-CHUNKMGR: [chars] [hex] Explanation An MPLS MFI static application chunk manager error has occurred. Recommended Action This problem may be due to a low memory condition on the device. Check

system memory and minimum memory requirements for this release and configuration, and add memory if required. If memory appears to be sufficient and problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show process memory, show version and show running-config commands and your pertinent troubleshooting logs.

Error Message MPLSMFISTATIC-3-FCALLFAILED: [chars] Explanation A static application function call has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



983

MPLSOAM Messages

open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show version and show running-config commands and your pertinent troubleshooting logs.

Error Message MPLSMFISTATIC-3-INVALIDPRAMS: [chars] [dec] Explanation Unexpected parameters have been detected in a static application. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message MPLSMFISTATIC-3-WRONGCODEPATH: [chars] Explanation An error involving an unexpected static application code path has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


MPLSOAM Messages This section contains Multiprotocol Label Switching (MPLS) Operations, Administration, and Maintenance (OAM) messages.


984

MPLS_PACKET Messages

MPLSOAM-3 Error Message %MPLSOAM-3-XDR_COMM: %s:0x%x 0x%x Explanation The XDR communication module reports an unexpected RP/LC XDR condition

encountered in the MPLS OAM software. This condition may result in MPLS OAM FIB subblocks becoming out of synchronization between the RP and the line card. This condition should not affect overall system operation. Recommended Action Copy the message exactly as it appears on the console or in the system log.


MPLS_PACKET Messages This section contains MPLS packet messages.

MPLS_PACKET-3 Error Message %MPLS_PACKET-3-FWDDISABLE: MPLS [chars] forwarding path disabled Explanation The MPLS forwarding plane has been disabled. Recommended Action This log entry is informational only. No action is required.

Error Message %MPLS_PACKET-3-FWDREENABLE: MPLS [chars] forwarding path reenabled Explanation The MPLS forwarding plane has been reenabled. Recommended Action This log entry is informational only. No action is required.

Error Message %MPLS_PACKET-3-LABELCACHE: [chars] [dec]/[dec] Explanation An MPLS label cache error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



985

MPLS_TE Messages


MPLS_PACKET-4 Error Message %MPLS_PACKET-4-NOLFDSB: MPLS packet received on non MPLS enabled interface [chars] L3 type [hex] label {[dec] [dec] [dec] [dec]} Explanation MPLS packets received on an interface are being dropped as the interface is not setup

to handle MPLS. This message may appear when an MPLS application is disabled on a interface, and should disappear when the upstream neighbor has reprogrammed its CEF and MPLS entries. Recommended Action If an MPLS application has just been disabled and traffic is flowing, this

message is expected and should be ignored. If the message recurs in steady state, the operator should monitor the network for attacks and report the occurrence to Cisco.

MPLS_TE Messages This section contains MPLS Label Switch Path (LSP) Tunnel messages.

MPLS_TE-2 Error Message %MPLS_TE-2-ADJ_WALK_ERR: [chars] Explanation An error occurred during a bundle adjacency walk. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MPLS_TE-2-BUNDLE_INSERT: [chars][chars] Explanation A request for inserting a traffic engineering tunnel bundle failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



986

MPLS_TE_AUTOMESH Messages


Error Message %MPLS_TE-2-UNSUPPORTED_LINK_TYPE: [chars] Explanation An unsupported link type was detected. Recommended Action Copy the message exactly as it appears on the console or in the system log.


MPLS_TE-3 Error Message %MPLS_TE-3-LSDERROR: [chars]: [chars] [chars] Explanation A traffic engineering request to the label switching database encountered an unexpected



MPLS_TE_AUTOMESH Messages This section contains MPLS Traffic Engineering (TE) Auto-Tunnel Primary and Backup log and error messages.


987

MPLS_TE_LM Messages

MPLS_TE_AUTOMESH-5 Error Message %MPLS_TE_AUTOMESH-5-AUTOTEMPLATE_HWIDB_DELETE: Failed to delete hwidb for Auto-Template %d index %d Explanation The deletion of a hardware interface descriptor block (HWIDB) for an auto-template

interface failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


MPLS_TE_LM Messages This section contains MPLS TE Link Management messages.

MPLS_TE_LM-3 Error Message %MPLS_TE_LM-3-LSP_BAD_ENCODING_TYPE: LSP [chars] requesting Encoding Type [[chars]] that is unsupported on interface [chars]. Explanation The indicated TE LSP, routed on the indicated interface, requested an encoding type that

is unsupported on the interface. The requested value appears in the Generalized Label Request. Recommended Action Verify that the head end originating the TE LSP has a Generalized Label Request that is specifying an encoding type acceptable to the interface in question. If not, alter the head end configuration to request an LSP with an appropriate value, or cause the LSP to be routed on a different interface. If this problem still persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. Also provide a topology diagram showing the hops in the LSP, marking each hop with the vendor and software, and identify which hop is the Cisco IOS device issuing the error message.


988

MPLS_VPN_HA Messages

Error Message %MPLS_TE_LM-3-LSP_BAD_GPID: LSP [chars] requesting G-PID [[chars]] that is unsupported on interface [chars][chars]. Explanation The indicated TE LSP, routed on the indicated interface, requested a (Generalized)

Payload Identifier unsupported on the interface. The requested value appears in the Label Request and Generalized Label Request. Recommended Action Verify that the head end originating the TE LSP has a Label Request that is specifying a PID acceptable to the interface in question. If not, one possibility is to alter the head end configuration to request an LSP with an appropriate value. Alternatively, if this error is generated at the penultimate hop of an LSP where the endpoint is advertising an implicit-null label (penultimate hop popping is in use), alter the endpoint to advertise an explicit-null label. If this problem still persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. Also provide a topology diagram showing the hops in the LSP, marking each hop with the vendor and software, and identify which hop is the Cisco IOS device issuing the error message.

Error Message %MPLS_TE_LM-3-LSP_BAD_SWITCHING_TYPE: LSP [chars] requesting Switching Type [[chars]] that is unsupported on interface [chars]. Explanation The indicated TE LSP, routed on the indicated interface, requested a Switching Type

that is unsupported on the interface. The requested value appears in the Generalized Label Request. Recommended Action Verify that the head end originating the TE LSP has a Generalized Label

Request that is specifying a Switching Type acceptable to the interface in question. If not, alter the head end configuration to request an LSP with an appropriate value, or cause the LSP to be routed on a different interface. If this problem still persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. Also provide a topology diagram showing the hops in the LSP, marking each hop with the vendor and software, and identify which hop is the Cisco IOS device issuing the error message.

MPLS_VPN_HA Messages This section contains MPLS HA messages for checkpointing label bindings.


989


MPLS_VPN_HA-3 Error Message %MPLS_VPN_HA-3-CF_GEN_ERROR: [chars] Explanation A general error occurred related to the MPLS VPN HA client CF. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MPLS_VPN_HA-3-CLIENTREG: [chars] Explanation The MPLS VPN HA failed to register to CF. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MPLS_VPN_HA-3-DBOPERATION: [chars] RD [chars], [IP_address]/[dec], label [dec] Explanation An error occurred related to an MPLS VPN HA checkpoint database operation. Recommended Action Copy the message exactly as it appears on the console or in the system log.



990


Error Message %MPLS_VPN_HA-3-SIZEMISMATCH: Label table size ([dec]) mismatch, get label tableid failed. Explanation A mismatch has been detected in the table size of the MPLS VPN HA facility. Recommended Action Copy the message exactly as it appears on the console or in the system log.


MPLS_VPN_HA-7 Error Message %MPLS_VPN_HA-7-LABELFREE: [chars] [dec] Explanation The MPLS VPN label manager failed to free a label. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MPLS_VPN_HA-7-MALLOCFAIL: [chars] Explanation The MPLS VPN HA facility failed to allocate memory. Recommended Action Copy the message exactly as it appears on the console or in the system log.



991

MPLS_VPN_ISSU Messages

Error Message %MPLS_VPN_HA-7-XMITFAIL: [chars], message seq no [dec], current seq no [dec] Explanation The MPLS VPN label manager has failed to deliver a message. Recommended Action Copy the message exactly as it appears on the console or in the system log.


MPLS_VPN_ISSU Messages This section contains MPLS VPN ISSU client messages.

MPLS_VPN_ISSU-3 Error Message %MPLS_VPN_ISSU-3-CF_ERR: [chars] [hex] Explanation An error occurred related to the MPLS VPN ISSU client CF. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MPLS_VPN_ISSU-3-GENERR: [chars] Explanation An error occurred related to the MPLS VPN ISSU client. Recommended Action Copy the message exactly as it appears on the console or in the system log.



992

MRIB_PROXY Messages


Error Message %MPLS_VPN_ISSU-3-ISSU_RC_ERR: [chars] [chars] Explanation An error occurred related to the MPLS VPN ISSU client. Recommended Action Copy the message exactly as it appears on the console or in the system log.


MRIB_PROXY Messages This section contains Multicast Routing Information Base proxy (MRIB_PROXY) messages.

MRIB_PROXY-2 Error Message %MRIB_PROXY-2-MRIB_LC_CREPRC_FAILED: LC in slot [dec] failed to create a required process. Explanation The line card could not create a process to perform delayed IPC initialization. The

MFIB will not be started on this line card. Recommended Action Copy the message exactly as it appears on the console or in the system log.



993

MRIB_PROXY Messages

Error Message %MRIB_PROXY-2-MRIB_LC_FAILED_GET_IPC: LC failed allocating IPC buffer which may lead to data loss or inconsistent MFIB states, slot = [dec] Explanation The line card has failed in allocating an interprocessor communication buffer. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message %MRIB_PROXY-2-MRIB_LC_FAILED_IDB_MAP: LC failed in mapping interface number [dec] Explanation The line card failed in mapping an interface from the global representation to the local

one. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MRIB_PROXY-2-MRIB_LC_FAILED_IPC_ACK: RP failed in getting Ack for IPC message of type = [dec], status = [dec], error = [chars] Explanation The route processor has failed to get IPC acknowledgement. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MRIB_PROXY-2-MRIB_LC_FAILED_IPC_OPEN: LC in slot [dec] failed to open IPC port to RP, error = [chars] Explanation The line card has failed to open an IPC port towards the route processor. Recommended Action Copy the message exactly as it appears on the console or in the system log.



994

MRIB_PROXY Messages


Error Message %MRIB_PROXY-2-MRIB_LC_FAILED_SEND_LC_READY: LC in slot [dec] failed to send LC ready to RP, error = [chars] Explanation The line card has failed to send a ready message to the route processor. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MRIB_PROXY-2-MRIB_LC_FETCH_FAIL: LC in slot [dec] failed to send an RPC fetch request to the RP: [chars] Explanation The line card attempted to read mroute updates from the route processor but the RPC

request failed. The line card MFIB state may now be inconsistent or frozen. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MRIB_PROXY-2-MRIB_LC_READY_NOIPC: LC failed allocating IPC buffer to send LC ready, slot = [dec] Explanation The line card has failed to allocate an interprocessor communication buffer to send the

ready message. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.


995

MRIB_PROXY Messages

Error Message %MRIB_PROXY-2-MRIB_LC_UPDATE_IGNORED: LC in slot [dec] ignored one or more mroute updates Explanation The line card ignored one or more mroute updates because the buffer containing them

failed a sanity check. The line card MFIB state may now be inconsistent. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MRIB_PROXY-2-MRIB_RP_FAILED_GET_IPC: RP failed allocating IPC buffer which may lead to data loss or inconsistent MFIB states Explanation The route processor has failed to allocate an interprocessor communication buffer. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MRIB_PROXY-2-MRIB_RP_FAILED_IDB_MAP: RP failed in mapping interface Explanation The route processor failed to map an interface from the global representation to the local

one, or vice versa. Recommended Action Copy the message exactly as it appears on the console or in the system log.



996

MRIB_PROXY Messages

Error Message %MRIB_PROXY-2-MRIB_RP_FAILED_IPC_ACK: LC failed in getting Ack for IPC message of type = [dec], status = [dec], error = [chars] Explanation The line card has failed to get an IPC acknowledgement. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MRIB_PROXY-2-MRIB_RP_FAILED_IPC_CREATE: RP failed in creating IPC port, error = [chars] Explanation The route processor failed to create an MFIB interprocess communications port. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MRIB_PROXY-2-MRIB_RP_FAILED_LC_DIST_MODE_INIT_PROC: RP failed in creating distribute mode init process for a linecard, slot = [dec] Explanation The route processor failed to create a distribute mode initialization process for a line

card. Recommended Action Copy the message exactly as it appears on the console or in the system log.



997

MRIB_PROXY Messages

Error Message %MRIB_PROXY-2-MRIB_RP_FAILED_LC_PORT_INFO: RP failed in creating linecard port info for distributed mode, slot = [dec] Explanation The route processor failed to create line card port information for distributed mode. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MRIB_PROXY-2-MRIB_RP_FAILED_LC_PORT_OPEN: RP failed in opening linecard port info for distributed mode, slot = [dec] Explanation The route processor failed to open line card port information for distributed mode. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MRIB_PROXY-2-MRIB_RP_FAILED_RPC_REPLY: RP failed in sending [chars] reply to a linecard in slot = [dec], IPC error = [chars]. This is normal after linecard removal or reset. At other times, data loss or mroute state inconsistency may result. Explanation The route processor has failed in sending a remote procedure call reply to a line card.

This is normal after line card removal or reset. At other times, data loss or mroute state inconsistency may result. Recommended Action Copy the message exactly as it appears on the console or in the system log.



998

MROUTE Messages

MROUTE Messages This section contains MROUTE messages.

MROUTE-2 Error Message %MROUTE-2-RADIXINIT: Error initializing IP multicast radix for %i Explanation Insufficient memory is available to initialize the IP multicast routing table. Recommended Action Copy the message exactly as it appears on the console or in the system log.


MROUTE-3 Error Message %MROUTE-3-IGMP_NOT_FOUND: IGMP group [IP address] to delete from interface [chars] not found in VRF [chars] Explanation An inconsistency in maintaining the IGMP cache occurred. The group to be deleted

from the interface could not be found in the IGMP cache for the VRF. [IP address] is the IP address in the IGMP group, the first [chars] is the interface, and the second [chars] is the VRF. Recommended Action Copy the message exactly as it appears on the console or in the system log.



999

MROUTE Messages

Error Message %MROUTE-3-IGMP_TWHEEL_INIT_ERR: Error trying to initialize the IGMP timer wheel Explanation An error occurred during the initialization of a timer wheel. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MROUTE-3-IGMP_WAVL_ERROR: IGMP wavl [chars] failed for group [IP_address] in interface [chars] Explanation The addition/deletion of igmp group in wavl tree failed. Recommended Action Collect show tech ipmulticast command output. Copy the error message

exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message %MROUTE-3-MIDB_QUEUE_ERR: Interface %s not in (%i, %i) Explanation The MIDB has the highest expiration timer but was not in the MDB->MIDB. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1000

MROUTE Messages

Error Message %MROUTE-3-NO_PIM_NBR: There is no PIM neighbor on this IDB: [chars] Explanation There is no PIM neighbor on the specified IDB. The most probable cause of this error

is that PIM is not configured correctly on this interface or on interfaces of the next-hop routers. Recommended Action Check PIM configurations on local and neighbor routers. Copy the message


Error Message %MROUTE-3-RECUR_ROUTE_DEPTH_ERR: Recursive route lookup has reached its max depth for: [IP_address] Explanation The recursive route lookup has reached its predefined maximum depth limit. Recommended Action If possible, reduce the number of rounds of next-hop lookup needed for the

network address in question. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %MROUTE-3-ROUTECOUNT_ZERO: Multicast route count reached zero Explanation The running count of multicast routes reached zero when it should be non-zero. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1001

MROUTE Messages

Error Message %MROUTE-3-TWHEEL_DELAY_ERR: Exceeded maximum delay (%d ms) requested: %d Explanation An attempt was made to schedule a function with a higher delay than the maximum

allowed. The function will be scheduled using the maximum delay possible. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MROUTE-3-TWHEEL_ERR: Timer wheel internal error Explanation A timer wheel internal error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MROUTE-3-TWHEEL_INIT_ERR: Trying to re-initialize an already initialized timer wheel Explanation An error occurred while intializing a timer wheel. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1002

MROUTE Messages

Error Message %MROUTE-3-TWHEEL_INSERT_ERR: An error occured after inserting or executing a timer wheel event Explanation An error occurred after inserting or executing a timer wheel event. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MROUTE-3-TWHEEL_INT_ERR: Timer wheel error at interrupt level %d Explanation A timer wheel internal error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MROUTE-3-TWHEEL_SLOT_ERR: Timer wheel event:%x slot:%d func:%x unequal to exec slot: %d Explanation The timer wheel event has an inconsistent slot number. Recommended Action Enter the clear ip mroute command to delete entries from the IP multicast

routing table. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


1003

MROUTE Messages

Error Message %MROUTE-3-WAVLINIT: Could not initialize WAVL tree for (%i,%i) Explanation The WAVL tree could not be initialized, so the system canot search for Multicast

Interface Data Blocks (MIDBs). Recommended Action Copy the message exactly as it appears on the console or in the system log.


MROUTE-4 Error Message %MROUTE-4-INCONSISTENT_IDB_TABLEID: PIM detected inconsistency in table-id information on [chars]. Explanation The PIM has detected that the interface table ID value is not the same as the value

maintained by the multicast code. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MROUTE-4-MROUTELIMIT: Exceeded multicast limit for group %i, source %i on interface %s Explanation The allowed number of multicast routes having the incoming or outgoing interface

reached the limit specified by a configured access list. New routes cannot be added unless the interface configuration is changed. Recommended Action If multicast traffic over the interface is of any priority among the traffic carried

by this router, then enter the ip multicast limit interface command to increase the number of multicast routes. Otherwise, no action is required. Enter the debug ip mroute limit command or the show ip multicast limit command to learn which multicast interface limit was exceeded.


1004

MROUTE Messages

Error Message %MROUTE-4-MTU_MISMATCH: WARNING: With IP multicast enabled, interfaces which transmit traffic from larger to smaller MTU interfaces may not be hardware switched due to fragmentation. A degradation in performance may occur. Explanation With IP multicast enabled, interfaces that transmit traffic from larger to smaller MTU interfaces may not be hardware switched due to fragmentation. A degradation in performance may occur. Recommended Action Set the MTU values on all interfaces to be identical.

Error Message %MROUTE-4-RADIXDELETE: Error trying to delete multicast route entry %i/%d for %i (expected %#x, got %#x) Explanation A route could not be deleted from the routing table. Recommended Action Enter the clear ip mroute command to delete entries from the IP multicast

routing table. Determine whether the router is low on memory. If the problem recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %MROUTE-4-RADIXINSERT: Error trying to add multicast route entry %i/%d for %i (expected %#x, got %#x) Explanation A route could not be inserted into the routing table. Recommended Action Enter the clear ip mroute command to delete entries from the IP multicast

routing table. Determine whether the router is low on memory. If the problem recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %MROUTE-4-REGISTER_SOURCE_CONFIG: Removing pim register source configuration for [chars] Explanation The register source interface was deleted, or its IP address was removed, or its VRF

forwarding was changed. Recommended Action Check the ip pim register-source configuration.


1005

MROUTE Messages

Error Message %MROUTE-4-ROUTELIMIT: Current count of %u exceeds multicast route-limit of %d Explanation The number of multicast routes equals the configured maximum allowed. New routes


then use the ip multicast route-limit command to increase the number of multicast routes. Otherwise, no action is required.

Error Message %MROUTE-4-ROUTELIMIT_ATTEMPT: Attempt to exceed multicast route-limit of [dec] Explanation The number of multicast routes equals the configured maximum allowed. New routes


then enter the ip multicast route-limit command to increase the number of multicast routes. Otherwise, no action is required.

Error Message %MROUTE-4-ROUTELIMITWARNING: multicast route-limit warning (curr %u threshold %u) Explanation The number of multicast routes reached the configured percentage of the multicast

route-limit. Recommended Action Increase the multicast route-limit.

Error Message %MROUTE-4-RPF_LOOKUP_LOOP: RPF route lookup loop for %i, route %i/%d Explanation A routing loop exists, possibly caused by routers reverse path forwarding to different

tables . Recommended Action Check the routing tables used for reverse path forwarding (RPF).

MROUTE-6 Error Message %MROUTE-6-LARGE_TWHEEL_DELAY: Exceeded maximum delay (%d ms) requested: %d Explanation An attempt was made to schedule a function with a higher delay than the maximum

allowed. The function will be scheduled using the maximum delay possible minus a small delay offset. Recommended Action Check whether a large IGMP query-interval is set. Some timers may refresh

periodically to allow for the large delay.


1006

MSC100_SPA_CC Messages

MSC100_SPA_CC Messages This section contains Cisco 7304 SPA carrier card messages.

MSC100_SPA_CC-0 Error Message %MSC100_SPA_CC-0-FPGA_BAY_ERROR_EXCEED_LIMIT: [chars] detected [chars] exceed limit ([dec]) (hardware-status = [hex]) Explanation A critical FPGA error was detected on the SPA or carrier card for the specified subslot.

The SPA in this subslot has been disabled. Recommended Action Try to reactivate the card using the hw-module subslot

slot-number/subslot-number start command. If the error persists, enter the show diag slot-number command to gather data that may help identify the cause of the error. If you cannot determine the cause of the error from the error message text or from the show diag slot-number output, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %MSC100_SPA_CC-0-FPGA_ERROR: [chars] Slot [dec]: Hardware error detected [[chars]] Explanation A critical FPGA error was detected on the carrier card. The carrier card is deactivated

and then an automatic recovery is initiated. If a similar error occurs more than five times within an hour, the carrier card is deactivated. Recommended Action If the line card is no longer automatically reactivating, copy the error message exactly as it appears on the console or in the system log. Enter the show diag slot-number command to gather data that may help identify the cause of the error. If you cannot determine the cause of the error from the error message text or from the show diag slot-number output, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


1007

MSDP Messages

Error Message %MSC100_SPA_CC-0-FPGA_ERROR_EXCEED_LIMIT: [chars] Slot [dec] detected [chars] exceed limit ([dec]) (hardware-status = [hex]) Explanation A critical FPGA error was detected on the carrier card. The carrier card is deactivated

and then an automatic recovery is initiated. If a similar error occurs more than five times within an hour, the carrier card is deactivated. Recommended Action If the line card is no longer automatically reactivating, copy the error message exactly as it appears on the console or in the system log. Enter the show diag slot-number command to gather data that may help identify the cause of the error. If you cannot determine the cause of the error from the error message text or from the show diag slot-number output, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %MSC100_SPA_CC-0-MISSING_RP_FPGA_SUPPORT: The 7304-MSC-100 in slot [int] has been deactivated because the RP FPGA requires an upgrade. Explanation The MSC-100 SPA carrier card in the specified slot requires a particular version of the

RP FPGA. The MSC-100 will be deactivated until this FPGA incompatibility is addressed. Recommended Action Enter the upgrade fpga all command to upgrade the RP FPGA. After

upgrading the RP FPGA, reactivate the MSC-100 by removing and reinserting the MSC-100.

MSDP Messages This section contains Multicast Source Discovery Protocol (MSDP) messages.

MSDP-3 Error Message %MSDP-3-DNS_ERROR: DNS lookup time out. DNS lookup for ssm mapping will be disabled for 60 sec Explanation DNS source lookup timeout. DNS server not respond to the DNS query, this may be due to DNS server is down. DNS lookup will be stopped for next 60 sec. Recommended Action Disbale DNS ssm mapping till the DNS server come up. Copy the error

message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance,


1008

MSDP Messages


Error Message %MSDP-3-NO_RPF_NODE: SA message could not be sent to peer [IP_address]. Expecting RPF node with host address [IP_address] but found node with host [IP_address] in the rpf tree. Explanation The reverse path forwarding (RPF) node could not be found while sending a

Source-Active (SA) message to the peer. The SA will not be sent in this period. Recommended Action Copy the message exactly as it appears on the console or in the system log.


MSDP-4 Error Message %MSDP-4-PKT_TOO_BIG: Message size violation on %u-byte packet from %i, discarded Explanation A message larger than the maximum MSDP message size was received. This message

could also indicate an internal error. Recommended Action Obtain the manufacturer and the version information of the router that sent the oversize packet. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show version commands and your pertinent troubleshooting logs.


1009

MSFC2 Messages

Error Message %MSDP-4-SA_LIMIT: SA from peer %i, RP %i for (%i, %i) exceeded sa-limit of %d Explanation The number of MSDP SAs exceeds the configured maximum number. SA cache entries

cannot be added unless the configuration is changed. Recommended Action If the MSDP SAs come from legitimate sources or RPs, then enter the ip msdp

sa-limit command to increase the number of SA entries allowed from the subject peer. Otherwise, no action is required.

MSDP-5 Error Message %MSDP-5-PEER_IS_SELF: Peering with self (%i) Explanation Multicast Source Discovery Protocol (MSDP) on this device is peering with itself. Recommended Action Check the address of the intended MSDP peer.

Error Message %MSDP-5-PEER_UPDOWN: Session to peer %i going %s Explanation A session to an MSDP peer going up or down. Recommended Action Determine whether the router is low on memory.

Error Message %MSDP-5-PEER_IS_SELF: Peering with self ([IP_address]) Explanation MSDP peering with ourselves Recommended Action Check the address of the MSDP peer

MSFC2 Messages This section contains Multilayer Switch Feature Card 2 (MSFC2) messages.

MSFC2-3 Error Message %MSFC2-3-IDB_INCORRECT_UNTHROTTLE_VECTOR: attempting to throttle idb [hex] ([chars]) with enable vector [hex] Explanation An invalid interface enable vector was detected. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1010


Error Message %MSFC2-3-TOOBIG: Attempt to send giant packet on [chars] ([dec] bytes from [hex], max allowed [dec]) Explanation An attempt was made to send an oversized packet. This message typically appears when

the Layer 3 switch is not fragmenting packets with a message size larger than 1500 bytes. Recommended Action Increase the interface MTU size.

MTRIE Messages This section contains MTRIE messages.

MTRIE-4 Error Message %MTRIE-4-MTRIECORRUPTLEAF: [IP_address]/[dec] - [chars] Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MTRIE-4-MTRIELEAFOPFAIL: [IP_address]/[dec] - [chars] Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1011

MUESLIX Messages


Error Message %MTRIE-4-PLACEALLOC: Failed to allocate place holder Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


MUESLIX Messages This section contains Mx serial ASIC messages.

MUESLIX-3 Error Message %MUESLIX-3-ERROR: [chars] Explanation A general error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


MVRP Messages This section contains Multicast VLAN Registration Protocol (MVRP) messages.


1012

MVRP Messages

MVRP-3 Error Message %MVRP-3-ADD_REGISTRY_FAILED: MVRP subsystem fails to add callback function %s Explanation Another subsystem has mistakenly added its own callback functions. This message is for debugging purposes. Recommended Action No action is required.

Error Message %MVRP-3-ENABLE_FAILED: MVRP can’t be enabled because %s Explanation Multicast VLAN Registration Protocol (MVRP) cannot be enabled for the specified

reason. Recommended Action Take action according to the specified reason. For example, if the failure is due

to insufficient memory, add more memory to the system.

Error Message %MVRP-3-HA_INIT_FAILED: MVRP High Availability subsystem fails to be initialized and hence MVRP won’t support HA stateful switchover. Explanation The MVRP CF client or the MVRP RF client failed to initialize. Recommended Action Enter the show redundancy clients command and the show checkpoint

clients command to learn which client was not initialized.

Error Message %MVRP-3-SUBSYS_INIT_FAILED: MVRP subsystem failed in initialization(%s) and MVRP won’t function properly. Explanation MVRP could not initialize, probably due to insufficient memory. Other accompanying

system messages may provide further information about the failure. Recommended Action Enter the show memory summary command to check the memory usage.

Contact the TAC with the output of the show memory summary, show version, and show run commands and the associated syslog messages from the time of the problem.

MVRP-6 Error Message %MVRP-6-MODECHANGE: The operating mode is changed to %s mode on interface %s. Explanation As a result of protocol negotiation, the operating mode changed to the specified mode

on the specified interface. Recommended Action No action is required.


1013

MVRP_CONST Messages

MVRP_CONST Messages This section contains MVRP messages on Constellation platforms.

MVRP_CONST-3 Error Message %MVRP_CONST-3-MAC_MATCH_REG_FAILED: Unable to reserve needed MAC match register - cannot run MVRP on interfaces of slot %d Explanation Multicast VLAN Registration Protocol (MVRP) attempted to reserve a MAC match

register for the slot indicated, but there is no dedicated register or programmable register available. MVRP cannot be activated on interfaces of this card. Recommended Action Disable conflicting protocols that use the MAC match register or use a different card type that supports MVRP.

MVRP_CONST-6 Error Message %MVRP_CONST-6-FEATURE_CONFLICT: Failed to enable MVRP on %s because conflicting feature %s is enabled on the interface Explanation MVRP could not be enabled on the given interface because of conflicting features. For

example, unknown unicast flood blocking(UUFB) and MVRP cannot be enabled on the same interface. Recommended Action If MVRP is required on the interface, enter the show running-config interface

command to investigate whether incompatible features are enabled on the interface.

Error Message %MVRP_CONST-6-MAC_LEARNING: MAC learning on VLAN %s is %s Explanation If only two MVRP ports are forwarding and not pruned in a VLAN, MVRP will disable MAC learning on that VLAN in order to save room in the MAC table, which is a limited system-wide resource. Recommended Action No action is required.

Error Message %MVRP_CONST-6-MAC_LRN_SETTING_FAILED: Failed to %s MAC learning on VLAN %s Explanation MVRP failed to enable or disable MAC learning on the given VLAN, probably because

MAC learning was already configured on the VLAN by the administrator. Recommended Action To determine the status of MAC learning on the VLAN, enter the show mac-address-table learning command.


1014

MVRP_ISSU Messages

MVRP_ISSU Messages This section contains MVRP in-service software upgrade messages.

MVRP_ISSU-2 Error Message %MVRP_ISSU-2-GET_BUFFER: MVRP ISSU client failed to get buffer for message. Error: %d (%s) Explanation The Multicast VLAN Registration Protocol (MVRP) ISSU client was unable to reserve

buffer space for building a negotiation message. As a result, the negotiation message cannot be sent to the standby device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MVRP_ISSU-2-INIT: MVRP ISSU client initialization failed to %s. Error: %d (%s) Explanation The MVRP ISSU client could not be initialized. This initialization failure must be

addressed before an in-service software upgrade or downgrade can be performed. Otherwise, a software upgrade or downgrade will result in downtime. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1015

MVRP_ISSU Messages

Error Message %MVRP_ISSU-2-SEND_NEGO_FAILED: MVRP ISSU client failed to send negotiation message. Error: %d (%s) Explanation The MVRP ISSU client was unable to send a session negotiation message to the peer

device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MVRP_ISSU-2-SESSION_NEGO: MVRP ISSU client encountered unexpected client nego_done. Error: %d (%s) Explanation The MVRP ISSU client encountered a client negotiation done state that was unexpected.



Error Message %MVRP_ISSU-2-SESSION_REGISTRY: MVRP ISSU client failed to register session information. Error: %d (%s) Explanation The MVRP ISSU client was unable to register session information. If a problem occurs

with the ISSU session registration, the standby device cannot be brought up properly. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1016

MVRP_ISSU Messages


MVRP_ISSU-3 Error Message %MVRP_ISSU-3-INVALID_SESSION: MVRP ISSU client does not have a valid registered session. Explanation The Multicast VLAN Registration Protocol (MVRP) ISSU client does not have a valid

registered session. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MVRP_ISSU-3-MSG_NOT_OK: MVRP ISSU client ’Message Type %d’ is not compatible Explanation The MVRP ISSU client received an incompatible message from the peer device. The

message cannot be processed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1017

MVRP_ISSU Messages

Error Message %MVRP_ISSU-3-MSG_SIZE: MVRP ISSU client failed to get the MTU for Message Type %d. Error: %d (%s) Explanation The MVRP ISSU client was unable to calculate the MTU for the specified message. As

a result, the MVRP ISSU client is not able to send the message to the standby device. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MVRP_ISSU-3-SESSION_UNREGISTRY: MVRP ISSU client failed to unregister session information. Error: %d (%s) Explanation The MVRP ISSU client was unable to unregister session information. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %MVRP_ISSU-3-TRANSFORM_FAIL: MVRP ISSU client %s transform failed for ’Message Type %d’. Error: %d (%s) Explanation The MVRP ISSU client could not transform the specified message type. If the transmit

transformation failed, the checkpoint message was not sent to the standby device. If the receive transformation failed, the checkpoint message was not applied on the standby device. In either case, the MVRP state between the active device and the standby device is not identical. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1018

MVRP_SWITCH Messages

following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs.

MVRP_SWITCH Messages This section contains MVRP messages on switch platforms.

MVRP_SWITCH-6 Error Message %MVRP_SWITCH-6-IGNORE_USER_CONFIG: The user configured list of pruned VLANs on interface %s is ignored as MVRP will prune VLANs dynamically. Explanation The switchport trunk pruning vlan command is used by VTP pruning to prune

VLANs numbered from 1 to 1001 only. This configuration command does not apply to MVRP, which prunes all 4096 VLANs. The command will be ignored. Recommended Action No action is required.

Error Message %MVRP_SWITCH-6-VLAN_CREATED: MVRP created VLANs %s on this device Explanation MVRP has created the specified VLANs. MVRP can create VLANs dynamically if the feature is enabled with the mvrp vlan create command. Recommended Action No action is required.

MVR_RP Messages This section contains Multicast VLAN Registration (MVR) route processor messages.

MVR_RP-3 Error Message %MVR_RP-3-OPER_PORT_SET_FAILED: MVR port operational type setting failed. Reason: [dec] Explanation A failure occurred while setting the MVR source or receiver port operational type on

the switch port. The cause was either a failure on the switch port or an ICC failure. Recommended Action Unconfigure the MVR type from this switch port and reconfigure it.


1019

MVR_RP Messages

MVR_RP-6 Error Message %MVR_RP-6-RCVR_ACCESS_PORTMODECHNG: [chars] MVR type receiver on [chars], this access port [chars] MVR vlan Explanation An MVR type receiver should not be configured on a MVR VLAN port. Because this

port is configured as dynamic auto/desirable, and due to a mode change in the neighboring switch, the operational switchport mode on this switch has become access and the corresponding VLAN is an MVR VLAN. Recommended Action Either unconfigure MVR type receiver from this switch port or change the

access VLAN to a non-MVR VLAN.

Error Message %MVR_RP-6-RCVR_TRUNK_PORTMODECHNG: [chars] MVR type receiver on [chars], MVR type receiver should not be configured on trunk ports Explanation An MVR type receiver should not be configured on a trunk port. Because this port is

configured as dynamic auto/desirable, and due to a mode change in the neighboring switch, the operational switch port mode on this switch has become trunk. MVR type receiver should be disabled. Recommended Action Either unconfigure MVR type receiver from this switch port or change the

mode to access and change the VLAN to a non-MVR VLAN.

Error Message %MVR_RP-6-SRC_ACCESS_PORTMODECHNG: [chars] MVR type source on [chars], this access port [chars] MVR vlan Explanation MVR type source should not be configured on a non-MVR VLAN port. Because this

port is configured as dynamic auto/desirable, and due to mode change in the neighboring switch, the operational switch port mode on this switch has become access and the corresponding VLAN is non-MVR. Recommended Action Either unconfigure MVR type source from this switch port or change the access VLAN to an MVR VLAN.

Error Message %MVR_RP-6-SRC_TRUNK_PORTMODECHNG: [chars] MVR type source on [chars], this trunk port allowed vlans [chars] MVR vlan Explanation MVR type source should not be configured on a non-MVR VLAN port. Because this

port is configured as dynamic auto/desirable, and due to mode change in the neighboring switch, the operational switch port mode on this switch has become trunk and the corresponding VLAN range does not contain the MVR VLAN. Recommended Action Either unconfigure MVR type source from this switch port or change the trunk

allowed VLAN range to include the MVR VLAN.


1020

MWAM Messages

MWAM Messages This section contains Multiprocessor WAN Application Module (MWAM) messages.

Error Message %MWAM-4-FAILED_FILE_SYNC: Failure creating or synchronizing MWAM configuration file to standby: [chars], [chars] Explanation The active supervisor engine has failed to copy an MWAM configuration file from

bootflash: to slavebootflash:. The standby supervisor engine will not be up to date with the MWAM configuration files if a switchover occurs. Recommended Action Verify that there is space available on the bootflash: and slavebootflash: devices. It may be necessary to compress either or both devices to recover space used by deleted or overwritten files. After taking these actions, a new attempt to synchronize files can be started either by resetting the standby supervisor engine or by configuring no mwam bootflash access followed immediately by mwam bootflash access. If these actions do not resolve the issue, obtain the output from the following commands:

- dir bootflash: - dir slavebootflash: - show bootflash: - show slavebootflash: If possible, set debug mwam all on the active supervisor engine, and then reset the standby supervisor engine with the hw-module module slot reset command, capturing the debug information that appears on the active supervisor engine console. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %MWAM-4-FAILED_TASK_INIT: Failed to start a required task: [chars], [chars] Explanation A necessary process failed to be created. Recommended Action If this message recurs, copy the message exactly as it appears on the console



1021

NATMIB_HELPER Messages

NATMIB_HELPER Messages This section contains Network Address Translator (NAT) MIB helper messages.

NATMIB_HELPER-3 Error Message %NATMIB_HELPER-3-NOCREAT: NATMIB Helper Process not created - NAT MIB will not work properly Explanation An attempt to start the NATMIB helper process failed when the NATMIB subsystem was initialized. The NATMIB helper process could not be created. This condition might be caused by a lack of memory. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Reload the system after reconfiguring it.

NBAR Messages This section contains network-based application recognition (NBAR) messages.

Error Message %NBAR-1-NODESIZEMISMATCH: Nodes size mismatch between parsing and sending:[chars] Explanation There was a failure during the distribution of NBAR graph nodes from the route processor to the line cards. The failure is related to node size changes between the parsing and sending phase. Recommended Action Disable the NBAR protocols.

NETCONF Messages This section contains network configuration protocol (NETCONF) messages.

NETCONF-3 Error Message %NETCONF-3-MEMORY: %s Explanation The network configuration protocol (NETCONF) subsystem was unable to reserve the

required memory to complete this operation. Recommended Action Check the system memory for memory allocation errors. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.


1022

NETFLOW_AGGREGATION Messages

NETFLOW_AGGREGATION Messages This section contains NetFlow Aggregation (NETFLOW_AGGREGATION) messages.

NETFLOW_AGGREGATION-3 Error Message %NETFLOW_AGGREGATION-3-FLOWMASK_CONFLICT: Netflow [chars] cannot set the required flowmask Explanation The NetFlow aggregation flow mask conflicts with other features. Recommended Action If NetFlow Data Export is configured, increase the size of the NDE flow mask to VLAN full flow by entering the mls flow ip interface-full command, and then reconfigure the NetFlow aggregation scheme. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

NETFLOW_AGGREGATION-4 Error Message %NETFLOW_AGGREGATION-4-NO_TOS_AGGR: Disable hardware switching to enable [chars] Explanation NetFlow does not currently support ToS-based aggregation schemes for

hardware-switched flows. Recommended Action If ToS-based aggregation is required, disable hardware switching.

Error Message %NETFLOW_AGGREGATION-4-OER_AGG_EXPORT_ERROR: OER Error [chars] Explanation An error occurred in receiving an Optimized Edge Routing (OER) aggregation export

packet. Recommended Action Disable OER monitor prefix aggregation.


1023

NETWORK_PORT_SATELLITE Messages

NETFLOW_AGGREGATION-6 Error Message %NETFLOW_AGGREGATION-6-OER_MLS_LONG_AGING: MLS long aging time modified by OER to [dec] Explanation OER modified the long aging time to a value that may be different from the configured

value. Recommended Action No action is required.

NETWORK_PORT_SATELLITE Messages This section contains network port satellite messages.

NETWORK_PORT_SATELLITE-3 Error Message %NETWORK_PORT_SATELLITE-3-PHY_LOCKUP: Repeated phy lockup seen on [chars]. Interface will be shut down. Explanation The physical interface has locked up an excessive number of times. To avoid the

interface becoming active, and then quickly becoming inactive numerous times (link flapping), the interface has been shut down. Recommended Action To reenable the interface, enter the shutdown command, followed by the no

shutdown command in interface configuration mode, to shut down and restart the interface.

NETWORK_RF_API Messages This section contains network redundancy feature API (NETWORK_RF_API) messages.

NETWORK_RF_API-3 Error Message %NETWORK_RF_API-3-CLIENT_REGISTER_FAIL: Failed to register with [chars], rc =[dec] Explanation A redundancy client could not be registered. An internal failure associated with client

registration occurred in the run-time module specified in the message output. The return code that is specified in the message output identifies the type of failure that was detected. The failure most likely occurred because of a software error. The system state between the active and standby units might not be properly synchronized. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1024

NETWORK_RF_API Messages


Error Message %NETWORK_RF_API-3-FAILDECODEDATADESC: Cannot decode data descriptor for [chars], descriptor type=[dec] Explanation An internal data descriptor could not be decoded for synchronization for the interface

or controller in the run-time module specified in the message output. The failure most likely occurred because of a software error. The descriptor type specified in the message output, if it is a nonzero value, identifies the type of failure. The system state between the active and standby units might not be properly synchronized. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %NETWORK_RF_API-3-FAILDECODEDATADESCINSTDBY: Cannot decode data descriptor in Standby for [chars], descriptor type=[dec] Explanation An internal data descriptor could not be decoded in the standby unit. The message

identifies the interface or controller that caused the decoding failure in the standby unit. This interface was encoded in the active unit but could not be decoded in the standby unit. The failure is probably caused by a software error. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1025


Error Message %NETWORK_RF_API-3-FAILENCODEDATADESC: Cannot encode data descriptor for [chars], descriptor type=[dec] Explanation An internal data descriptor could not be encoded for synchronization for the interface

or controller in the run-time module specified in the message output. The failure most likely occurred because of a software error. The descriptor type specified in the message output identifies the type of failure. The system state between the active and standby units might not be properly synchronized. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %NETWORK_RF_API-3-FAILSENDMSGTOACTIVE: Failed to send [chars] message to active for [chars], [chars] Explanation The specified synchronization message, which is an internal IPC message, could not be

sent to the active unit in the specified run-time module. The failure most likely occurred because of a software error. Additional details on the cause of the error are specified in the message text on the console or in the system log. The system state between the active and standby units might not be properly synchronized. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %NETWORK_RF_API-3-FAILSENDMSGTOSTDBY: Failed to send [chars] message to standby for [chars], rc=[dec] Explanation The specified synchronization message, which is an internal IPC message, could not be

sent to the standby unit in the specified run-time module. The failure most likely occurred because of a software error. The numeric error code in the message output identifies the type of failure. The system state between the active and standby units might not be properly synchronized. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1026



Error Message %NETWORK_RF_API-3-INVALID_CHKPT_STATUS_CODE: Invalid checkpointing status code received, rc=[dec] Explanation An invalid checkpoint status code has been detected. An internal status code that is associated with checkpointing was found to be invalid. The return code that is specified in the message output identifies the invalid code that was detected. The failure most likely occurred because of a software error. The system state between the active and standby units might not be properly synchronized. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %NETWORK_RF_API-3-INVALID_MSG_RECEIVED: Invalid [chars] message received Explanation A message that is used for state synchronization was not received correctly. An internal data structure for a message could not be retrieved. The failure most likely occurred because of a software error. The system state between the active and standby units might not be properly synchronized. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1027


Error Message %NETWORK_RF_API-3-IPC: [chars] [chars] Explanation An interprocess communication (IPC) error has occurred. Additional details on the cause of the error are specified in the message text on the console or in the system log. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show tech-support ipc command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %NETWORK_RF_API-3-ISSU_MSG_MTU_INVALID: The ISSU message MTU is invalid: [chars] Explanation A message buffer size that is used for state synchronization was found to be invalid. An

internal data structure for a message could not be retrieved. The failure most likely occurred because of a software error. Additional details on the cause of the error are specified in the message text on the console or in the system log. The system state between the active and standby units might not be properly synchronized. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %NETWORK_RF_API-3-ISSU_MSG_TYPE_INCOMPAT: The active and standby ISSU message types are incompatible Explanation An incompatible message was used for state synchronization. An internal data structure

for a message could not be retrieved. The failure most likely occurred because of a software error. The system state between the active and standby units might not be properly synchronized. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1028



Error Message %NETWORK_RF_API-3-ISSU_REG_SES_INFO: Failed to register ISSU session information: [chars] Explanation The system failed to register the ISSU session information required to complete version exchange between the active and standby units. The failure most likely occurred because of a software error. Additional details on the cause of the error are specified in the message text on the console or in the system log. The system state between the active and standby units might not be properly synchronized. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %NETWORK_RF_API-3-ISSU_START_NEGO_SES: Failed to start ISSU session: [chars] Explanation The system failed to start the ISSU negotiation session required to complete version

exchange between the active and standby units. The failure most likely occurred because of a software error. Additional details on the cause of the error are specified in the message text on the console or in the system log. The system state between the active and standby units might not be properly synchronized. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1029


Error Message %NETWORK_RF_API-3-ISSU_TRANSFORM_FAIL: The ISSU message [chars] transformation failed: [chars] Explanation A message that is used for state synchronization could not be transformed correctly. An

internal data structure for a message could not be retrieved. The failure most likely occurred because of a software error. Additional details on the cause of the error are specified in the message text on the console or in the system log. The system state between the active and standby units might not be properly synchronized. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %NETWORK_RF_API-3-ISSU_UNREG_SES_INFO: Failed to register ISSU session information: [chars] Explanation The system failed to unregister the ISSU session information required to complete

version exchange between the active and standby units. The failure most likely occurred because of a software error. Additional details on the cause of the error are specified in the message text on the console or in the system log. The system state between the active and standby units might not be properly synchronized. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %NETWORK_RF_API-3-NO_CHKPT_BUFFER: No checkpointing buffer for [chars], rc=[dec] Explanation A message data buffer that is used for state synchronization could not be obtained. An

internal data structure could not be allocated for synchronization in the run-time module specified in the message output. The return code that is specified in the message output identifies the type of failure. The failure most likely occurred because of a software error or a lack of system memory. The system state between the active and standby units might not be properly synchronized. Recommended Action If you determine that this condition was caused by a lack of system memory,

reduce system activity to ease memory demands, or if conditions warrant, upgrade to a larger memory configuration. Otherwise, copy the message exactly as it appears on the console or in the


1030


system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %NETWORK_RF_API-3-NO_MSG_BUFFER: No message buffer for [chars] Explanation A message data buffer that is used for state synchronization could not be obtained. An

internal data structure could not be allocated for synchronization in the run-time module specified in the message output. The failure most likely occurred because of a software error or a lack of system memory. The system state between the active and standby units might not be properly synchronized. Recommended Action If you determine that this condition was caused by a lack of system memory,

reduce system activity to ease memory demands, or if conditions warrant, upgrade to a larger memory configuration. Otherwise, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %NETWORK_RF_API-3-NO_RESOURCES: [chars] Explanation A run-time module could not obtain the resources that are required to complete a task.

The failure most likely occurred because of a software error or a lack of system memory. Additional details on the cause of the error are specified in the message text on the console or in the system log. The system state between the active and standby units might not be properly synchronized. Recommended Action If you determine that this condition was caused by a lack of system memory,

reduce system activity to ease memory demands, or if conditions warrant, upgrade to a larger memory configuration. Otherwise, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


1031

NHRP Messages

NETWORK_RF_API-6 Error Message %NETWORK_RF_API-6-IDB_TRANSITIONS_PENDING: Switchover terminated with [dec] transitions pending after there was no transition activity for [dec] seconds Explanation The system terminated the switchover IDB transitioning phase with a number of IDB

transitions still pending because no switchover-related IDB transitions were logged during the specified time interval. Some connected routes may experience a temporary loss of traffic. Recommended Action No action is required.

NHRP Messages This section contains Next Hop Resolution Protocol (NHRP) messages.

Error Message %NHRP-3-TIMERLOOP: Timer process looping ([dec]/[dec]/[dec]/[dec]/[dec]/[dec]). Explanation The process that handles timer events is looping, possibly on a malfunctioning timer

event. Recommended Action Copy the message exactly as it appears on the console or in the system log.


NP Messages This section contains Network Processor messages.

NP-2 Error Message %NP-2-BADREAD: Read failed for [chars] on NP [dec]. Explanation There was a read error on the file during the microcode image load. Recommended Action Copy the error message exactly as it appears on the console or in the system

log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the


1032

NP Messages

Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message %NP-2-HDRCORRUPT: Microcode header has been corrupted, expected [hex], got [hex]. Explanation Network Processor microcode appears to be corrupted. This could be due to an already

corrupted image or, less likely, a software problem. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %NP-2-INVALID: Corrupted microcode retrieved from the image bundle for NP [dec]. Explanation The retrieved microcode appears to be corrupted. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %NP-2-NONEXIST: Could not open or file does not exist [chars] for NP [dec]. Explanation There is a possibility that the Network Processor microcode may not be bundled into the

image correctly or a software error occurred that prevented locating the microcode. Recommended Action Copy the error message exactly as it appears on the console or in the system



1033

NP Messages

Error Message %NP-2-RESTARTED: NP [dec] restarted. Explanation Network Processor has been restarted, either manually or by a microcode reload, or as

a result of an exception. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %NP-2-WRONGHARD: The microcode type does not match, expected [hex], got [hex]. Explanation There is a possibility the images has been corrupted or, less likely, an incorrect

microcode set is bundled into the image. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %NP-2-WRONGMAGIC: Microcode section contains inalid magic for NP [dec]. Explanation Network Processor microcode appears to mismatch the ucode hdr type. This could be

due to an already corrupted image or a read error on the file during the downloading on the NP. Recommended Action Copy the error message exactly as it appears on the console or in the system



1034

NP_CLIENT Messages

NP-5 Error Message %NP-5-RESTARTEDALL: All NPs have been restarted. Explanation All Network Processors have been restarted, either manually or by a microcode reload,

or as a result of an exception. Recommended Action Copy the error message exactly as it appears on the console or in the system


NP_CLIENT Messages This section contains NextPort (NP) client messages.

Error Message %NP_CLIENT-3-ALLEXISTS: NP Client Previously Defined Software Element - [chars]: [chars] [chars] Explanation The NP client has detected a previously defined software element. Recommended Action Attempt to reload the Cisco IOS image on the affected card or platform. If the error persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %NP_CLIENT-2-FATAL: NP Client [chars] : [chars] ([dec], [dec]) Explanation The NP client software detected a critical programming error. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1035

NP_CLIENT Messages


Error Message %NP_CLIENT-3-INITFAIL: NP Client Initialization Failed - [chars]: [chars] [chars] Explanation The NP client could not initialize memory needed to service one or more network processors. This error may indicate that an incompatibility exists between the NP firmware and the associated Cisco IOS image. Recommended Action Attempt to reload the Cisco IOS image on the affected card or platform. If the error persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %NP_CLIENT-3-INTF: [chars] ([chars]) on [chars] - [chars] if_number=[dec] Explanation The interface NP client detected an error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %NP_CLIENT-3-MAXEXCEED: NP Client Max Services Exceeded - [chars]: [chars] [chars] Explanation The maximum number of NP client services has been exceeded. Recommended Action Change the configuration to reduce the number of services configured. If the

error persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at


1036

NP_CLIENT Messages


Error Message %NP_CLIENT-3-METADATA: [chars] failed: [chars] [[chars]] [chars] Explanation Processing of the metadata for the specified network processor has failed. The specified network processor will fail to operate. Recommended Action Attempt to reload the network processor microcode. If the error persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %NP_CLIENT-3-NOMEM: Memory Allocation Failure - [chars]: [chars] [chars] Explanation The NP client could not allocate the required memory needed to service one or more

network processors. Recommended Action This error may indicate that more memory must be installed on the affected

card or platform in order to service all the features and related entities enabled by the configuration. Try to reload the Cisco IOS image on the affected card or platform. If the error persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %NP_CLIENT-3-NOTFOUND: NP Client Software Element Not Found - [chars]: [chars] [chars] Explanation The NP client could not locate a required software element. Recommended Action Attempt to reload the Cisco IOS image on the affected card or platform. If the error persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,


1037

NP-CRASHINFO Messages


Error Message %NP_CLIENT-3-NOTSUP: NP Client Feature Not Supported - [chars]: [chars] [chars] Explanation The NP client does not support the specified feature. Recommended Action Verify that the correct Cisco IOS image is loaded on the affected card or


Error Message %NP_CLIENT-3-NPUNKNOWN: NP Client Unsupported NP - [chars]: [chars] [chars] Explanation The NP client detected an unsupported NP. Recommended Action Verify that the correct Cisco IOS image is loaded on the affected card or


NP-CRASHINFO Messages This section contains Network Processor messages.


1038

NP-CRASHINFO Messages

Error Message %NP_CRASHINFO-2-OPEN_FAILED: Could not open crashinfo file [[chars]] Explanation The file for writing crashinfo could not be opened. This is usually caused by the file

system problem. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %NP_CRASHINFO-2-WRITE_FAILED: Could not write crashinfo file [[chars]] Explanation Could not write crashinfo to the file. This is usuallycaused by the file system problem. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %NP_CRASHINFO-2-WRITING: Writing crashinfo file [[chars]] Explanation NP detected a watchdog timeout. The crashinfo is collectedfrom problematic NP and

stored in the location. Recommended Action Copy the error message exactly as it appears on the console or in the system



1039

NP-DEV Messages

NP-DEV Messages This section contains Network Processor messages.

NP_DEV-2 Error Message %NP_DEV-2-INVREGINTR: Illegal Write on NP RMA Register: [hex], Data: [hex] Explanation This is an illegal Write to an NP RMA Register. This is to debug NP Parity Error issue. Examine traceback and forward it to development team. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %NP_DEV-2-WATCHDOG: Watchdog detected on NP [dec] Explanation A software exception occured on an NP device. Recommended Action Copy the error message exactly as it appears on the console or in the system


NP_DEV-3 Error Message %NP_DEV-3-ECC_DOUBLE: Double-bit ECC error detected on NP [dec], Mem [dec], SubMem [hex],SingleErr [dec], DoubleErr [dec] Count [dec] Total [dec] Explanation A double-bit ECC error was detected for a Network Processor device component. Recommended Action Copy the error message exactly as it appears on the console or in the system



1040

NP-DEV Messages


Error Message %NP_DEV-3-ERRINTR: Error caused by: [chars] on NP [dec] Explanation An error in Network Processor device operation was detected. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %NP_DEV-3-PERR: Non-recoverable Parity error detected on NP [dec], cause [dec] count [int] uqParityMask [hex], uqSRAMLine [hex], bRecov [dec], bRewr [dec] Total [dec] Explanation A non-recoverable parity error was detected for a Network Processor device component. Recommended Action Copy the error message exactly as it appears on the console or in the system


NP_DEV-5 Error Message %NP_DEV-5-INTRTHR: Interrupt: cause [dec] for NP([int]) throttled Explanation Too many interrupts are being generated from Network Processor device. Recommended Action Copy the error message exactly as it appears on the console or in the system



1041

NSE100 Messages

NP_DEV-6 Error Message %NP_DEV-6-PERR_RECOVERED: Recovered from a Parity error on NP [dec], cause [dec], count [int] uqParityMask [hex], uqSRAMLine [hex], bRecov [dec], bRewr [dec] Total [dec] Explanation Recovered from a Parity error detected for a Network Processor device component. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %NP_DEV-6-ECC_SINGLE: Recovered from a single-bit ECC error detected on NP [dec], Mem [dec], SubMem [hex],SingleErr [dec], DoubleErr [dec] Count [dec] Total [dec] Explanation Recovered from a single-bit ECC error detected for a Network Processor device

component. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

NSE100 Messages This section contains network services engine messages.

NSE100-3 Error Message %NSE100-3-IOBUSTIMEOUT: IO access to the address [hex] timed out (Target: [chars]) Explanation The system controller flagged an I/O access timeout, indicating either a transient/fatal

system component issue or an underlying software initialization issue. The source of the problem can be determined more accurately by decoding the address being accessed. If the I/O address is


1042

NSE100 Messages

valid in the system memory map and if the system has been up and operational for a while, the problem is probably hardware related. If this problem is seen repeatedly, the corresponding component might need to be replaced. Recommended Action If the message is seen repeatedly, copy the message exactly as it appears on the

console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: description of the user activity just before the occurrence of this incident, prevailing system operational conditions like traffic pattern, amount of traffic, system neighbors, system console messages and the output of the following commands: show running-config, show c7300 pxf accounting, show c7300 pxf interfaces all, show diag and show c7300.

Error Message %NSE100-3-PINNACLE_PORT: [chars] - [chars] Explanation A failure occurred while one of the Gigabit Ethernet (GE) ports on the NSE-100 was

being initialized. This condition is probably caused by either a software error or a transient condition before the GE port becomes successfully initialized. Recommended Action If the GE ports either do not initialize or fail to forward traffic as a result of this

condition, enter the shutdown command, followed by the no shutdown command, in interface configuration mode to shut down and restart the affected GE ports to restore the forwarding. If the message is seen repeatedly, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: - The user activity immediately preceding the receipt of this message. - The prevailing system operational conditions such as the traffic patterns, amount of traffic, and system neighbors. - Any additional system console messages. - The output of the following commands: show version, show running-config, show controller gigabitEthernet, show interface gigabitEthernet, show pxf accounting, show c7300, show logging and show tech-support.


1043

NSE100 Messages

Error Message %NSE100-3-UNEXPECTED_TIMEREVENT: The NSE-100 GE port driver couldn’t determine the port associated with the expired internal managed timer.The expired managed timer is pointing to [chars] Explanation The expired managed timer returned a null context. This condition indicates a software

failure in the management of the timer. Recommended Action If the message is seen repeatedly, copy the message exactly as it appears on the

console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: - The user activity immediately preceding the receipt of this message. - The prevailing system operational conditions such as the traffic patterns, amount of traffic, and system neighbors. - Any additional system console messages. - The output of the following commands: show version, show running-config, show platform, show controller gigabitEthernet, show interface gigabitEthernet, show pxf accounting, show c7300, show logging and show tech-support.

Error Message %NSE100-3-VA_ERROR: Vanallen ASIC detected an error condition: [chars] Explanation The Van Allen ASIC has detected an error condition. Either a hardware error or an error

in the packet was detected. Recommended Action Copy the message exactly as it appears on the console or in the system log.


NSE100-5 Error Message %NSE100-5-AUTONEG_ENABLE: Auto negotiation is enabled for interface GigabitEthernet[dec]/[dec] due to [chars] Explanation The auto-negotiation feature has been enabled for the Gigabit Ethernet interface in the

slot and port specified in the message text. The reason why the feature was enabled is specified in the message text. The auto-negotiation feature is required for the interface to work properly. Recommended Action No action is required.


1044

NP_UCODE Messages

NP_UCODE Messages This section contains NextPort (NP) microcode messages.

Error Message %NP_UCODE-3-INVALID_FILE: NP microcode [chars] for device [chars] is invalid ([chars]) Explanation The file containing the microcode for an NP is not specified or not accessible. This could be due to an invalid configuration or because the microcode is missing in this image. Recommended Action Copy the message exactly as it appears on the console or in the system log.


NTI Messages This section contains Negotiation Trigger Infrastructure (NTI) messages.

NTI-3 Error Message %NTI-3-AGENT_ERR: %s Notifying platform about AGENT ERROR %s, AGENT EP ID 0x%x for EP ID 0x%x, EP type %s, EP group %s Explanation A Negotiation Trigger Infrastructure (NTI) AGENT error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1045

NTI Messages

Error Message %NTI-3-CLIENT_NOT_REGSTRD_FOR_EPTYPE: %s Client (#%d - %s) has NOT registered for platform EP type %s Explanation A client has not registered for a platform endpoint (EP) type. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %NTI-3-ISSU_AGENT_LIST_ALLOC: Failed to allocate agent bitlist for endpoint 0x%x Explanation The NTI ISSU process was unable to allocate the agent bitlist for an endpoint. The

endpoint will probably be reset. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %NTI-3-ISSU_DUMMY_MSG_FAILED: Failed to send a dummy nego msg to endpoint 0x%x Explanation The NTI ISSU process was unable to send a dummy negotiation message to trigger

negotiation on the peer. The endpoint will probably be reset. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1046

NTI Messages

Error Message %NTI-3-ISSU_EXISTING_SESSION: Session already exists for ep 0x%x Explanation The NTI ISSU session already exists for this endpoint. The endpoint will probably be

reset. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %NTI-3-ISSU_INVALID_MEDMAN: Invalid MEDMan data Explanation The Multiple Endpoint Data Manager (MEDMan) data is invalid. The endpoint will

probably be reset. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %NTI-3-ISSU_INVALID_MSG_TRANS: NTI ISSU transformation function got an invalid message in argument Explanation The NTI ISSU process transformation function received an invalid message. The

message cannot be transformed and will not be processed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1047

NTI Messages

Error Message %NTI-3-ISSU_INVALID_RC: Invalid ISSU rc argument for endpoint 0x%x Explanation The NTI ISSU process received an invalid ISSU return code argument. ISSU

negotiation will fail and the endpoint will probably be reset. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %NTI-3-ISSU_INVALID_RCVD_MSG: NTI ISSU received an invalid message for transformation from endpoint 0x%x Explanation The NTI ISSU process received an invalid message for transformation. The message

cannot be processed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %NTI-3-ISSU_INVALID_SESSION: Invalid session for ep 0x%x Explanation The NTI ISSU session is invalid for the endpoint. The endpoint will probably be reset. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1048

NTI Messages

Error Message %NTI-3-ISSU_MEDMAN_CREATE: Failed to create MEDMan data for endpoint 0x%x Explanation The NTI ISSU process was unable to create the Multiple Endpoint Data Manager

(MEDMan) data for an endpoint. Negotiation cannot be done, and the endpoint will probably be reset. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %NTI-3-ISSU_MEDMAN_GET: Failed to get MEDMan data for endpoint 0x%x (%s) Explanation The NTI ISSU process was unable to retrieve MEDMan data for an endpoint. ISSU

negotiation will fail for this endpoint, and the endpoint will probably be reset. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %NTI-3-ISSU_MTU_FAILED: NTI ISSU failed to get MTU for message type %d (%s) Explanation The NTI ISSU process was unable to get the message MTU for transformation. The

message cannot be sent. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1049

NTI Messages

Error Message %NTI-3-ISSU_NEGO_ALREADY_STARTED: NTI ISSU negotiation already started, endpoint 0x%x Explanation An attempt was made to start the NTI ISSU negotiation, but it has already been started.

The endpoint will probably be reset. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %NTI-3-ISSU_NEGO_ASYNC_ERROR: Aync error during nego with 0x%x (%s) Explanation The NTI ISSU process received an asynchronous error during negotiation with an

endpoint. The endpoint will probably be reset. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %NTI-3-ISSU_NEGO_INCOMPATIBLE: Negotiation incompatible for endpoint 0x%x Explanation The NTI ISSU negotiation is not compatible for this endpoint. The endpoint will

probably be reset. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1050

NTI Messages

Error Message %NTI-3-ISSU_NOT_INIT: NTI ISSU is not initialized, endpoint 0x%x. Explanation The NTI ISSU process is not initialized. The endpoint will probably be reset. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %NTI-3-ISSU_PLATFORM_TRANSPORT_NEGO_GET_REQ_PAK: NTI ISSU failed to get an platform transport nego message Explanation The NTI ISSU process was unable to receive a platform transport negotiation message.

The endpoint will probably be reset. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %NTI-3-ISSU_PLATFORM_TRANSPORT_NEGO_SEND: NTI ISSU failed to send an platform transport nego message to 0x%x Explanation The NTI ISSU process was unable to send a negotiation message using the platform

transport. The endpoint will probably be reset. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1051

NTI Messages

Error Message %NTI-3-ISSU_RCVD_NEGO_NOT_DONE: NTI ISSU negotiation not done when received a message from 0x%x Explanation The NTI ISSU process received a message before negotiation was done. The message



Error Message %NTI-3-ISSU_RCVD_TRANS_FAILED: NTI ISSU failed to transform received message from 0x%x Explanation The NTI ISSU process was unable to transform a received message. The message cannot



Error Message %NTI-3-ISSU_RCVD_UNKNOWN_MSG: NTI ISSU received an unknown message type %d from 0x%x Explanation The NTI ISSU process received a message whose type is unknown. The message cannot




1052

NTI Messages

Error Message %NTI-3-ISSU_RCV_FAILED: NTI ISSU failed to transform message type %d for receive from 0x%x (%s) Explanation The NTI ISSU process was unable to transform the message for receive. The message



Error Message %NTI-3-ISSU_REG_ADD: NTI ISSU failed to hook to the registry %s Explanation The NTI ISSU process was unable to hook to a registry. This endpoint will probably be



Error Message %NTI-3-ISSU_REG_RECEIVE_NEGO_MSG: NTI ISSU failed call the platform receive nego message registry Explanation The NTI ISSU process was unable to call the platform receive negotiation message

registry. The endpoint will probably be reset. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1053

NTI Messages

Error Message %NTI-3-ISSU_TRIG_NEGO_NOT_DONE: NTI ISSU negotiation not done when getting a trigger from 0x%x Explanation The NTI ISSU process received a trigger from this endpoint before the negotiation was

done. The trigger will be ignored. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %NTI-3-ISSU_UNKNOWN_MSG_TYPE: NTI ISSU got an unknown message type: %d Explanation The NTI ISSU process received an unknown message type while trying to get the

message MTU. The message cannot be sent. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %NTI-3-ISSU_XMIT_FAILED: NTI ISSU failed to transform message type %d for transmit to 0x%x (%s) Explanation The NTI ISSU process was unable to transform the message for transmit. The message

cannot be sent. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1054

NTI Messages

Error Message %NTI-3-TRIG_ABORT_ALL_CLIENTS: %s Aborting trigger processing for all clients as requested by the platform, EP ID 0x%x trigger type %s trigger group %s Explanation Trigger processing has been aborted for all clients due to a platform request. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %NTI-3-TRIG_CLIENT_NOTINLIST: %s Cannot trigger NTI client (%d) for this EP: could not find client in list, EP ID 0x%x Explanation An NTI client could not be triggered for an endpoint because the client could not be

found in the list. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %NTI-3-TRIG_INIT_ALREADY_IN_PROGRESS: %s Cannot initiate NTI trigger for EP ID 0x%x at this time: trigger processing of trigger type %s, trigger group %s already in progress Explanation An NTI trigger could not be initiated because a trigger is already in progress. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1055

NTP Messages

Error Message %NTI-3-TRIG_PROCESSING: %s Trigger processing ERROR for client (#%d %s), EP ID 0x%x trigger type %s trigger group %s : %s Explanation An NTI trigger processing error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


NTP Messages This section contains network time protocol (NTP) messages.

NTP-4 Error Message %NTP-4-PEERUNREACH: Peer [IP_address] is unreachable Explanation The NTP peer is unreachable. Recommended Action Check the network connection to the peer and ensure that NTP is running on

the peer.

Error Message %NTP-4-UNSYNC: NTP sync is lost Explanation NTP synchronization to its peer is lost. Recommended Action Perform the following actions:

- Check the network connection to the peer. - Check to ensure that NTP is running on the peer. - Check that the peer is synchronized to a stable time source. - Check to see if the NTP packets from the peer have passed the validity tests specified in RFC1305.

NTP-5 Error Message %NTP-5-PEERSYNC: NTP synced to peer [IP_address] Explanation NTP has synchronized the local clock to a new peer. Recommended Action No action is required.


1056

OBFL Messages

NTP-6 Error Message %NTP-6-PEERREACH: Peer [IP_address] is reachable Explanation The NTP peer is reachable. Recommended Action No action is required.

Error Message %NTP-6-RESTART: NTP process starts Explanation The NTP process has just started or restarted. Recommended Action No action is required.

Error Message %NTP-6-STOP: NTP process stops Explanation NTP is disabled. Recommended Action Check to see if NTP has been manually disabled by the administrator.

OBFL Messages This section contains Onboard Failure Logging (OBFL) messages.

OBFL-5 Error Message %OBFL-5-DISABLED: Onboard Failure Logging disabled Explanation Onboard Failure Logging has been disabled. Recommended Action No action is required.

OBFL_ERRMSG Messages This section contains Onboard Failure Logging (OBFL) error messages.


1057

OBFL_ERRMSG Messages

OBFL_ERRMSG-5 Error Message %OBFL_ERRMSG-5-FILECREATEFAIL: OBFL [chars] App failed to open/create file [chars] . Errno = [dec] Explanation The file open or creation operation failed. Recommended Action No action is required.

Error Message %OBFL_ERRMSG-5-FILEFSTATFAIL: OBFL [chars] App failed to fstat file [chars] . Errno = [dec] Explanation The file fstat operation failed. Recommended Action No action is required.

Error Message %OBFL_ERRMSG-5-FILELSEEKFAIL: OBFL [chars] App failed to Lseek file [chars] . Errno = [dec] Explanation The file lseek operation failed. Recommended Action No action is required.

Error Message %OBFL_ERRMSG-5-FILEMINFREEFAIL: OBFL [chars] App failed to set coalesce min free Explanation Failed to set the coalesce minimum free value. Recommended Action No action is required.

Error Message %OBFL_ERRMSG-5-FILEOPENFAIL: OBFL [chars] App failed to open file [chars] . Errno = [dec] Explanation The file open operation failed. Recommended Action No action is required.

Error Message %OBFL_ERRMSG-5-FILEREADFAIL: OBFL [chars] App read failure on file [chars] . Errno = [dec] Explanation The file read operation failed. Recommended Action No action is required.


1058

OCE Messages

Error Message %OBFL_ERRMSG-5-HISTFILESMALL: OBFL [chars] App: history file is exceedingly small Explanation The history file for this application has been detected to be very small. Recommended Action No action is required.

OCE Messages This section contains output chain elements (OCE) infrastructure messages.

OCE-3 Error Message %OCE-3-MISSING_HANDLER_FOR_SW_OBJ: Missing handler for ’[chars]’ function Explanation An internal API request has been ignored because it was unexpected. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %OCE-3-MISSING_HANDLER_FOR_SW_OBJ_TYPE: Missing handler for ’[chars]’ function for type [chars] Explanation An internal API request has been ignored because it was unexpected. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1059

OCE Messages

Error Message %OCE-3-OCE_CHANGED_BY_APPLY_FUNCTION: Target OCE[hex_addr] changed to[hex_addr] by apply function[hex_addr] Explanation An internal API request has been ignored because it was unexpected. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %OCE-3-OCEDEPDUMP: [chars] Explanation An error condition triggered display of OCE dependents. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %OCE-3-OCE_FWD_STATE_HANDLE: Limit of oce forward state handle allocation reached; maximum allowable number is [int] Explanation Did not store the reinject forwarding state handle, as the maximum number of handles

are already in use. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1060

OCE Messages

Error Message %OCE-3-OCE_FWD_STATE_HANDLE_INIT: Failed to initialize a stack of reusable forward state handles; at element [int], initial stack size is [int] elements Explanation Could not allocate enough forwarding state handles for initial handle reuse. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %OCE-3-QUEUE_UNLOCK: Failed to [chars] unlock[chars] for [chars] oce [hex] Explanation Failed to enqueue a unlock for an OCE. This condition may lead to a memory leak. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %OCE-3-UNEXPECTED_DISP_TYPE: Unexpected disposition type is encounted; expecting disposition types are [chars], found [chars] Explanation An internal disposition counter measure request has been ignored because it was

unexpected. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1061

ODM Messages

Error Message %OCE-3-UNEXPECTED_SW_OBJ_TYPE: SW_OBJ handle/type mismatch; expecting oce type [chars], found [dec] Explanation An internal API request has been ignored because it was unexpected. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %OCE-3-UNINITIALIZED_VECTOR: Improperly initialized [chars] vector in [chars] OCE bundle [hex], packet dropped Explanation An OCE bundle vector was improperly initialized. Recommended Action Copy the message exactly as it appears on the console or in the system log.


ODM Messages This section contains online diagnostics manager (ODM) subsystem messages.

ODM-3 Error Message %ODM-3-PEER_INCOMPATIBLE: Online Diags Peer Version is different Explanation The version of the peer online diagnostics manager is different from the expected

version. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1062

OER_TT_FLOW Messages


Error Message %ODM-3-SC_TEST_FAIL: Slot [dec], Subcard [dec],[chars] [chars] Failed Explanation The online diagnostic test for the subcard specified in the error message has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


OER_TT_FLOW Messages This section contains Optimized Edge Routing (OER) top talkers flow border router messages.

OER_TT_FLOW-2 Error Message %OER_TT_FLOW-2-OER_TT_FLOW_BR_CACHEINIT: Error initializing OER TT Flow BR cache Explanation The NetFlow top talker cache could not be initialized on the border router because of a

low-memory condition. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message %OER_TT_FLOW-2-OER_TT_FLOW_BR_EXPORTINIT: Error initializing OER TT Flow BR Export queue Explanation The OER NetFlow top talker export queue could not be initialized on the border router because of a low-memory condition. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.


1063

OIR Messages

OER_TT_FLOW-4 Error Message %OER_TT_FLOW-4-OER_TT_FLOW_BR_FLOWEXPORT: Error exporting [chars] Explanation An error involving a flow to the route processor has occurred. Recommended Action This is a debug message only. No action is required.

OIR Messages This section contains online insertion and removal (OIR) messages.

OIR-3 Error Message %OIR-3-HARD_RESET: Module [dec] is being hard reset as a part of switchover error recovery Explanation The specified module is being hard reset as a recovery for failure to respond to a

switchover message. Recommended Action No action is required.

Error Message %OIR-3-ISSU_RESET: Module %d is being hard reset as a part of ISSU upgrade Explanation The specified module is being hard reset as part of a planned ISSU upgrade. Recommended Action No action is required.

Error Message %OIR-3-PSM_SUBCARDDETECT: Slot [dec] [chars] [dec]: subcard [dec] inserted Explanation A protection switch module (PSM) subcard has been detected in the slot specified in the


Error Message %OIR-3-PSM_SUBCARDREMOVE: Slot [dec] [chars] [dec]: subcard [dec] removed Explanation A protection switch module (PSM) subcard has been removed from the specified slot. Recommended Action No action is required.


1064

OIR Messages

Error Message %OIR-3-SOFT_RESET: Module [dec] is being soft reset as a part of switchover error recovery Explanation The specified module is being soft reset as a part of switchover error recovery. Recommended Action No action is required.

Error Message %OIR-3-SOFT_RESET_SSO: Module %d is being soft reset as a part of switchover error recovery Explanation The specified module is being soft reset as a part of a switchover error recovery. Recommended Action No action is required.

Error Message %OIR-3-STDBY_PWRCYCLE: Standby was notified, Card in module [dec] is being power-cycled [chars] Explanation The OIR facility on the redundant supervisor engine was notified that a module on the

active supervisor engine is unresponsive. The module is being power-cycled. Recommended Action No action is required.

Error Message %OIR-3-STDBY_UNKNOWN: Standby was notified, Unknown card in slot [dec] Explanation The OIR facility on the redundant supervisor engine was notified that an undetermined

module was detected on the active supervisor engine. Recommended Action Reseat the module in the specified slot.

Error Message %OIR-3-UCODE_INTERNAL: The image download to card in slot [dec] failed due to internal error: [chars], [chars] Explanation An internal error has occurred in the line card image download code. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the remote command switch dir system:image/ command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


1065

OIR Messages

OIR-4 Error Message %OIR-4-DISABLE: Unsupported service module [chars] in slot [dec] disabled Explanation This service module is not supported in this release of software. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %OIR-4-INSERTION: Possible half inserted module detected in slot [dec] or a slow insertion Explanation This module is either inserted improperly or is not making a full contact to the

backplane or it is being insert very slowly. The user should follow the cisco recommandation on module insertion procedures. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %OIR-4-WARN: [chars] Explanation The OIR facility detected the specified condition. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1066

OIR Messages

OIR-6 Error Message %OIR-6-CWANVSSISSU: CWAN card present in slot [dec] in the slave chassis is powered down because ISSU is in progress Explanation CWAN card already present in the slave chassis of a virtual switch should not be

powered up during ISSU. It will be powered up on switchover or upon completion of ISSU. Recommended Action No action is required.

Error Message %OIR-6-DIAG_OFFLINE: Card inserted in slot [dec], is now ready for offline diagnostics Explanation The OIR facility detected a newly inserted line card. The line card is configured for the

offline diagnostic state by the user. This state can be entered only after the module is in the online diagnostic state. Recommended Action This is an informational message only. No action is required.

Error Message %OIR-6-DIAG_ONLINE: Card inserted in slot [dec], is now ready for online diagnostics Explanation The OIR facility detected a newly inserted line card. The line card is configured for the

online diagnostic state by the user or if diagnostic failure is detected during bootup. Recommended Action This is an informational message only. No action is required.

Error Message %OIR-6-DOWNGRADE: Fabric capable module [dec] not at an appropriate hardware revision level, and can only run in flowthrough mode Explanation This fabric capable module is not at an appropriate hardware revision level, and can run only in flowthrough (bus) mode. Recommended Action Upgrade the line card hardware.

Error Message %OIR-6-DOWNGRADE_EARL: Module [dec] [chars] installed is not identical to system PFC and will perform at current system operating mode. Explanation The PFC/DFC module is at a higher hardware revision than the level of the system PFC.

The PFC/DFC module will operate at the same level as that of the system PFC. Recommended Action This is an informational message only. No action is required.

Error Message %OIR-6-INSFAN: Fan [dec] inserted Explanation The OIR facility detected a newly inserted fan tray. Recommended Action This is an informational message only. No action is required.


1067

OIR Messages

Error Message %OIR-6-NOPWRISSU: Card inserted in slot %d powered down because ISSU is in progress Explanation The online insertion and removal (OIR) facility detected a newly inserted line card during an ISSU upgrade process. The new card will be powered down until completion of the ISSU. Recommended Action No action is required.

Error Message %OIR-6-PWRFAILURE: Module [dec] is being disabled due to power convertor failure [hex] Explanation The DC-DC power converter failed on this module and must be replaced. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %OIR-6-REMFAN: Fan [dec] removed Explanation The OIR facility detected the removal of a fan tray [n]. Recommended Action This is an informational message only. No action is required.

Error Message %OIR-6-SEQ_MISMATCH: SCP seq mismatch for card in slot [dec] : [chars] Explanation The OIR facility detected an SCP sequence mismatch for the card in the specified slot. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %OIR-6-SOFT_RESET_ISSU: Module [dec] is being soft reset as a part of ISSU cycle Explanation The module specified in error message is being soft reset as a part of ISSU cycle. Recommended Action No action is required.


1068

OIR_ISSU Messages

Error Message %OIR-6-STDBY_INSCARD: Standby was notified, card online in slot [dec] Explanation The OIR facility on the standby supervisor engine was notified by the active supervisor engine that a processor was inserted in slot [n] and that all the interfaces are now usable. Recommended Action No action is required.

Error Message %OIR-6-STDBY_REMCARD: Standby was notified, card removed from slot [dec] Explanation The OIR facility on the standby supervisor engine was notified by the active supervisor engine that a processor from the specified slot has been removed. Recommended Action No action is required.

OIR_ISSU Messages This section contains online insertion and removal (OIR) in-service software upgrade (ISSU) messages.

OIR_ISSU-3 Error Message %OIR_ISSU-3-BUFFER: Cat6K OIR ISSU client failed to a buffer for message, error %d Explanation The online insertion and removal (OIR) ISSU client failed to get a buffer for building a negotiation message. As a result, the client cannot send a negotiation message to the standby unit and the standby unit cannot be brought up. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %OIR_ISSU-3-CAPABILITY: Cat6K OIR ISSU client %s Explanation During capability negotiation, the OIR ISSU client detected an error that results in a

mismatch between the client capability of the active and standby units. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1069

OIR_ISSU Messages

information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs.

Error Message %OIR_ISSU-3-INIT: Cat6K OIR ISSU client initialization failed at %s, error %s Explanation The OIR ISSU client could not be initialized. This condition will cause a catastrophic failure when an ISSU upgrade or downgrade is performed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %OIR_ISSU-3-MSG_NOT_OK: Cat6K OIR ISSU client message %d is not compatible Explanation The OIR ISSU client received an incompatible message from the peer unit. The message

cannot be processed by this unit. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1070

OIR_ISSU Messages

Error Message %OIR_ISSU-3-MSG_SIZE: Cat6K OIR ISSU client failed to get the message size for message %d Explanation The OIR ISSU client was unable to calculate the message size for the message specified.

The client will be unable to send the message to the standby unit. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %OIR_ISSU-3-POLICY: Cat6K OIR ISSU client message type %d is %s Explanation The OIR ISSU client received a message type that it does not support. A policy is

applied to make the session compatible. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show issu session commands and your pertinent troubleshooting logs.

Error Message %OIR_ISSU-3-SEND_FAILED: Cat6K OIR ISSU client failed to send a negotiation message, error %d Explanation The OIR ISSU client could not send a session negotiation message to the peer. As a result, the standby unit cannot be brought up. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1071

OIR-SP

Error Message %OIR_ISSU-3-SESSION: Cat6K OIR ISSU client %s Explanation The OIR ISSU client detected an error during a session negotiation with the peer unit.

As a result, the standby unit cannot be brought up. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %OIR_ISSU-3-TRANSFORM: Cat6K OIR ISSU client %s transform failed, error %s Explanation The OIR ISSU client could not transform the message. If the transmit transformation

failed, the checkpoint message cannot be sent to the standby unit. If the receive transformation failed, the checkpoint message cannot be applied on the standby unit. In either case, the OIR state of the bay will not be identical with the active unit. Recommended Action Copy the message exactly as it appears on the console or in the system log.


OIR-SP Error Message %OIR-SP-6-CONSOLE: Changing console ownership to %s processor Explanation The OIR facility has switched the console to the specified processor. Recommended Action No action is required.


1072

OLM Messages

Error Message %OIR-SP-6-DOWNGRADE_EARL: Module %d %s installed is not identical to system PFC and will perform at current system operating mode. Explanation The PFC/DFC module is at a higher hardware revision than the level of the system PFC.

The PFC/DFC module will operate at the same level as that of the system PFC. Recommended Action No action is required.

Error Message %OIR-SP-6-INSCARD: Card inserted in slot [dec], interfaces are now online Explanation The OIR facility detects a newly inserted module. The interfaces associated with that module are operational, but are shut down until they are configured by the user. If any interfaces of that type were previously configured, they are restored to their previous state. Recommended Action No action is required.

Error Message %OIR-SP-6-INSPS: Power supply inserted in slot [dec] Explanation The OIR facility has detected the insertion of a power supply in the specified slot. The

total power adjusts after the power supply is turned on, Recommended Action No action is required.

OLM Messages This section contains Optical Link Management (OLM)) and Link Management Protocol (LMP) messages.

OLM-3 Error Message %OLM-3-LMPSDMISMATCH: Service Discovery: Attribute [chars] incompatible with neighbor [chars] Explanation The specified service attribute does not match that on the neighbor. The neighbor or the local node is not properly configured. Recommended Action Enter the show mpls uni lmp neighbor command on the local as well as the

neighbor node (where applicable), to determine the service attributes. Modify the configuration, if possible, to ensure that the attributes match.


1073

ONLINE Messages

Error Message %OLM-3-LMPSDPORTFAILED: Service Discovery: Attributes for port [chars] incompatible with nbr [chars] Explanation The port-level service attribute does not match with that of the neighbor. The neighbor

or the local node is not properly configured. Recommended Action Enter the show mpls uni lmp neighbor command on the local as well as the

neighbor node (where applicable), to determine the service attributes. Modify the configuration, if possible, to ensure that the port-level service attributes match.

ONLINE Messages This section contains SCP (Switch-module Configuration Protocol) download processor messages.

ONLINE-2 Error Message %ONLINE-2-LCP_BOOT_MISMATCH: The system detected LCP boot version mismatch for module in slot [dec], and will upgrade with new LCP boot image bundled into the system image, and power cycle the module. Explanation The system detected LCP boot version mismatch for module. This condition would

normally occur if the LCP boot version on the legacy modules is old for the modules, which require rapid boot support. The LCP boot version is upgraded automatically and the module will be power-cycled. Recommended Action No action is required.

ONLINE-3 Error Message %ONLINE-3-UNKNOWN_CARD_TYPE: Unknown card type is encountered: card_type = [int] Explanation The card type is unknown or not supported. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1074

ONLINE Messages

ONLINE-6 Error Message %ONLINE-6-BOOT_TIMER: Module %d, Proc. %d. Failed to bring online because of boot timer event Explanation The system was unable to download the runtime image to the module and processor

because the boot did not complete in the allocated time. Recommended Action No action is required.

Error Message %ONLINE-6-DNLD_TIMER: Downloading image to Module [dec], Proc. [dec]. has failed, due to download timer expiry Explanation The system was unable to download the runtime image to the module and processor

because the download did not complete in the allocated time. Recommended Action No action is required.

Error Message %ONLINE-6-DOWNLOAD_TIMER: Module %d, Proc. %d. Failed to bring online because of download timer event Explanation The system was unable to download the runtime image to the module and processor

because the download did not complete in the allocated time. Recommended Action No action is required.

Error Message %ONLINE-6-FIND_MASTER_FAIL: Module %d, Proc. %d. SCP_DNLD failed to find master Explanation The system was unable to find the master to download an image to the module and

processor within the allocated time. Recommended Action No action is required.

Error Message %ONLINE-6-GET_IMAGE_FAIL: Module %d, Proc. %d. SCP_DNLD failed to get image Explanation The system was unable to get the image from the master for downloading to the module and processor. Recommended Action No action is required.


1075

ONLINE Messages

Error Message %ONLINE-6-INVALID_DNLD_REQ: Received an unexpected image download request from Linecard Module [dec], Proc [dec]. Linecard image download request reason was [chars] Explanation The system received an image download request from the module and processor

complex specified in the message text, but that complex has already downloaded the image and should be initialized and operating normally. Recommended Action No action is required.

Error Message %ONLINE-6-LCC_CONFIG_FAIL: Module %d. LCC Client %s failed to configure at %08x Explanation During a Secure Copy (SCP) download, the Linecard Configuration Coordinator (LCC)

client failed to finish configuration of the module. Recommended Action No action is required.

Error Message %ONLINE-6-LCP_DNLD: Error while downloading image to Module [dec], Proc. [dec].: [chars] Explanation An error was encountered while downloading an image to a switching module. The first

[dec] is the module number, the second [dec] is the process number, and [chars] is the message explanation. Recommended Action No action is required.

Error Message %ONLINE-6-ONLINE_TIMER: Module %d, Proc. %d. Failed to bring online because of online timer event Explanation The system was unable to download the runtime image to the module and processor

because the online event did not happen in the allocated time. Recommended Action No action is required.

Error Message %ONLINE-6-READY_TIMER: Module %d, Proc. %d. Failed to bring online because of ready timer event Explanation The system was unable to download the runtime image to the module and processor

because the ASIC initialization did not complete in the allocated time. Recommended Action No action is required.

Error Message %ONLINE-6-REGN_TIMER: Module %d, Proc. %d. Failed to bring online because of registration timer event Explanation The system was unable to download the runtime image to the module and processor

because the registration did not complete in the allocated time. Recommended Action No action is required.


1076

ONLINEDIAG Messages

Error Message %ONLINE-6-RUNNING_TIMER: Module %d, Proc. %d. Failed to bring online because of running timer event Explanation The system was unable to download the runtime image to the module and processor

because the running event did not happen in the allocated time. Recommended Action No action is required.

ONLINEDIAG Messages Error Message %ONLINEDIAG-2-CPU_SWITCH_LB_TST_PKT_THRESH_ERROR: CPU Switch Interface : [dec]/[dec] of online diagnostic packets in error. Explanation The packet loss can be due to congestion. Recommended Action Issue the command show diag online cpu sw to get more details about the

failure. If this error occurs frequently, contact your technical representative for assistance with the output of the command show techsupport.

ONS15530 Messages This section contains Cisco ONS 15530 trunk card messages.

ONS15530-1 Error Message %ONS15530-1-DISCOVER_ENET: Failed to init Ethernet device [dec] Explanation The software could not be initialized. Recommended Action Power down the system, reseat the interface card, and reboot the system. If this

message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


1077

ONS15530 Messages

ONS15530-2 Error Message %ONS15530-2-NOMEMORY: No memory available for [chars] Explanation An attempted memory allocation failed. Recommended Action Try these actions to remedy the problem:

- Add memory. - Disable some features. - Apply filtering to decrease the size of system data structures - the routing table, for example. - Reduce other system activities to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

ONS15530-3 Error Message %ONS15530-3-CHASSIS: Unknown chassis model. Explanation Data stored in midplane is bad or incomplete. Recommended Action Contact your Cisco technical support representative to update your system.

Error Message %ONS15530-3-IONOT0: IO card discover in non-zero slot [dec]/[dec] Explanation Unavailable. Recommended Action Unavailable.

Error Message %ONS15530-3-IPCOPENFAILED: Couldn’t open IPC portfor port id [hex] slot [int]/[int]: [chars] Explanation Unavailable. Recommended Action Unavailable.

Error Message %ONS15530-3-NOMAC: Can’t allocate MAC address for interface [int]/[int] Explanation Unavailable. Recommended Action Unavailable.

Error Message %ONS15530-3-NOMEM: OUT of Memory: [chars] Explanation Unavailable. Recommended Action Unavailable.


1078

ONS15530 Messages

Error Message %ONS15530-3-NOPORTINFO: Port info invalid for port [dec] slot [int]/[int]: [chars] Explanation Unavailable. Recommended Action Unavailable.

Error Message %ONS15530-3-NOPORTINFO_ID: Port info invalid for port id [hex] slot [int]/[int]: [chars] Explanation Unavailable. Recommended Action Unavailable.

ONS15530-4 Error Message %ONS15530-4-COOKIE: Corrupt or missing MAC address cookie using random base [enet] Explanation The MAC address cookie is corrupt or missing. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %ONS15530-4-MACBLKSIZE: Unknown MAC address block size. Explanation Data stored in midplane is bad or incomplete. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1079

OPTICAL_MONITOR Messages

OPTICAL_MONITOR Messages This section contains optical monitoring messages.

OPTICAL_MONITOR-4 Error Message %OPTICAL_MONITOR-4-FAILED: [chars] [chars] Explanation The current hardware version cannot support monitoring for the rate that was specified. Recommended Action Specify a different rate for monitoring, if possible. If you require further

assistance, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

OSM_MULTILINK Messages This section contains Optical Services Module distributed multilink (OSM_MULTILINK) messages.

OSM_MULTILINK-3 Error Message %OSM_MULTILINK-3-PROCESS_FAIL: Process creation failed for [chars] Explanation The system failed to create a process. The probable cause of this condition is that the

system has low memory. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.


1080

OSM_MULTILINK Messages

OSM_MULTILINK-4 Error Message %OSM_MULTILINK-4-BUNDLEERROR: Bundle([chars]) is not distributed Explanation The bundle specified in the message is not associated with the OSM. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %OSM_MULTILINK-4-BUNDLENULL: Unexpected bundle missing in [chars] searching for [chars] Explanation A software error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %OSM_MULTILINK-4-BUNDLEVC: [chars] for vc [dec] and if_index [dec] Explanation A software error has occurred while a bundle was being provisioned. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1081


Error Message %OSM_MULTILINK-4-IDBNULL: Unexpected hwidb missing in [chars] Explanation A software error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %OSM_MULTILINK-4-IPCNOTREADY: Bundle process on the line card is not ready to handle message of type [dec] Explanation Bundle is being deleted on the line card due to an ip cef disable command and is not

ready to process other messages. The most likely cause of this condition is that CEF was disabled and enabled in very quick succession. Recommended Action Reset the line card.

Error Message %OSM_MULTILINK-4-MLPSBNULL: Unexpected subblock missing for [chars] Explanation A software error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %OSM_MULTILINK-4-NUMLINKS: The bundle had an unexpected number of links([dec]) in [chars] Explanation A software error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1082



Error Message %OSM_MULTILINK-4-QUEUE_BUNDLE: Not able to queue the bundle ([chars]), Num. of bundles [dec] Explanation A software error has occurred while a bundle was being inserted in the queue. Recommended Action Copy the message exactly as it appears on the console or in the system log.


OSM_MULTILINK-5 Error Message %OSM_MULTILINK-5-BUNDLEEXCEEDED: Bundle([chars]) cannot be associated with link([chars]), max [dec] Explanation The number of bundles has exceeded the limit for the group belonging to the link. The

bundle specified in the error message will not work in distributed mode. If the module is CT3 (OSM-CT3 module), then ports 1–12 belong to one group. If the module is a CHOC-3 module (OSM-CHOC-DS0 module), then ports 1–4 belong to one group. If the module is a CHOC-12 module (OSM-CHOC-DS0 module), then port 1 belongs to one group, and port 2 belongs to the second group. Only 168 bundles can be supported per group. The new bundle created will cause an extra load on the RP CPU. Recommended Action Remove the multilink interface that is causing this condition.

Error Message %OSM_MULTILINK-5-CFGERROR: Cannot set up this bundle link-- [chars] to bundle [chars] reason:[chars] Explanation The bundle link could not be set up. A configuration or resource limit has been reached.

The bundle may be forced to become inactive (go down). If the line card is a CT3 (OSM-CT3 line card), then ports 1–12 belong to one group. If the line card is a CHOC-3 (OSM-CHOC-DS0 line card), then ports 1–4 belong to one group. If the line card is a CHOC-12 (OSM-CHOC-DS0 line card), then port 1 belongs to one group and port 2 belongs to the second group. Only 168 bundles can be supported per group and each bundle can have a maximum of 12 links. Recommended Action Ensure that all links belong to the same group and slot. Check the number of

links in the bundle and number of bundles in the group. After the configuration has been corrected, enter the shutdown and no shutdown commands on the multilink interface to shut down and restart the interface.


1083

OSPF Messages

OSPF Messages This section contains Open Shortest Path First (OSPF) messages.

OSPF-3 Error Message %OSPF-3-CFG_NBR_ALLOC_FAILED: Could not allocate or find neighbor [IP_address] Explanation An internal error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %OSPF-3-CFG_NBR_FAILED: Neighbor [IP_address] not configured Explanation The configured neighbor options are not valid. Recommended Action Check the configuration options for the neighbor command and correct the

options or the network type for the neighbor’s interface.

Error Message %OSPF-3-INT_ATTACHED_MULTI_AREAS: Interface [chars] is attached to more than one area Explanation The interface is attached on the interface list to an area other than the one that the interface links to. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1084

OSPF Messages

Error Message %OSPF-3-INT_INIT_FAILED: Init failed for interface [chars], [chars]. Explanation The interface initialization failed. The following are possible reasons:

- The area to which the interface is being attached is being deleted. - It was not possible to create a neighbor datablock for the local router. Recommended Action Remove the configuration command that covers the interface and try again. If

this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %OSPF-3-LSA_LEN: Area [chars] router-LSA of length [dec] bytes plus update overhead [dec] bytes is too large to flood. Explanation The router tried to build a router-LSA that is larger than the huge system buffer size or

the OSPF protocol imposed maximum. Recommended Action If the reported total length (LSA size plus overhead) is larger than the huge system buffer size but less than 65535 bytes (the OSPF protocol imposed maximum), you may increase the huge system buffer size. If the reported total length is greater than 65535, you must decrease the number of OSPF interfaces in the reported area.

OSPF-4 Error Message %OSPF-4-AREA_ALLOC_FAIL: Can not allocate memory for area structure Explanation An internal error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1085

OSPF Messages

Error Message %OSPF-4-ASBR_WITHOUT_VALID_AREA: Router is currently an ASBR while having only one area which is a stub area Explanation An ASBR must be attached to an area which can carry AS external or NSSA LSAs. Recommended Action Make the area to which the router is attached into an NSSA or regular area.

Error Message %OSPF-4-CFG_NBR_INVAL_NBMA_OPT: Can not use configured neighbor: cost and database-filter options are allowed only for a point-to-multipoint network Explanation The configured neighbor was found on an NBMA network and either the cost or

database-filter option was configured. These options are only allowed on point-to-multipoint type networks. Recommended Action Check the configuration options for the neighbor command and correct the


Error Message %OSPF-4-CFG_NBR_INVAL_NET_TYPE: Can not use configured neighbor: neighbor command is allowed only on NBMA and point-to-multipoint networks Explanation The configured neighbor was found on a network for which the network type was neither NBMA or point-to-multipoint. Recommended Action No action is required.

Error Message %OSPF-4-CFG_NBR_INVAL_P2MP_OPT: Can not use configured neighbor: poll and priority options are allowed only for a NBMA network Explanation The configured neighbor was found on a point-to-multipoint network and either the poll

or priority option was configured. These options are only allowed on NBMA type networks. Recommended Action Check the configuration options for the neighbor command and correct the


Error Message %OSPF-4-CFG_NBR_P2MP_NEEDS_COST: Can not use configured neighbor: cost or database-filter option is required for point-to-multipoint broadcast network Explanation The configured neighbor was found on a point-to-multipoint broadcast network. Either

the cost or database-filter option needs to be configured. Recommended Action Check the configuration options for the neighbor command and correct the



1086

OSPF Messages

Error Message %OSPF-4-INVALID_METRIC: OSPF-%d Area %s: Router %i originating invalid type %d LSA, ID %i, Metric %d on Link ID %i Link Type %d Explanation The router indicated in this message has originated a Link-State Advertisement (LSA)

with an invalid metric. If this is a router LSA and the link metric is zero, routing loops and traffic loss could occur in the network. Recommended Action On the router that originated the reported LSA, configure a valid metric for the

given LSA type and link type.

Error Message %OSPF-4-INV_LSA_BLD_FLG: Invalid build flag [hex] for LSA [IP_address], type [dec] Explanation An internal error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %OSPF-4-NO_IPADDRESS_ON_INT: No IP address for interface [chars] Explanation The interface is not point-to-point and is unnumbered. Recommended Action Either change the interface type to point-to-point or give the interface an IP

address.

Error Message %OSPF-4-NO_OUTPUTQ: Packet not written to the output queue Explanation An internal error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1087

OSPF Messages

Error Message %OSPF-4-NORTRID: OSPF process [dec] failed to allocate unique router-id and cannot start Explanation OSPF failed while attempting to allocate a unique router ID from the IP addresses of its

interfaces. Recommended Action Ensure that at least one interface is active (up) and has a valid IP address. If multiple OSPF processes are running on the router, each requires a unique router ID. Configure a unique router ID manually by entering the router-id a.b.c.d command, or configure an interface in the same VRF table by entering the ip vrf forwarding word command to which the OSPF process belongs. Configure on that interface an IP address that is not used as a router ID by any other OSPF process.

Error Message %OSPF-4-NULL_LINKAGE: Doubly linked list linkage is NULL Explanation An internal error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %OSPF-4-NULL_PREV_LINKAGE: Doubly linked list prev linkage is NULL [hex] Explanation An internal error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %OSPF-4-OSPF_MAX_LSA: Maximum number of non self-generated LSA has been exceeded "[chars]" - [dec] LSAs Explanation The maximum number of non-self-generated LSAs has been exceeded. Recommended Action Check if some router in the network is generating a large number of LSAs as a result of misconfiguration.


1088

OSPF Messages

Error Message %OSPF-4-OSPF_MAX_LSA_THR: Threshold for maximum number of non self-generated LSA has been reached "[chars]" - [dec] LSAs Explanation The threshold for the maximum number of non-self-generated LSA has been reached. Recommended Action Check if some router in the network is generating a large number of LSAs as a result of misconfiguration.

Error Message %OSPF-4-RTRID_IN_USE: Router-ID [IP_address] is in use by ospf process [dec] Explanation An attempt was made to assign a router ID that is in use by another process. Recommended Action Configure another router ID for one of the processes.

Error Message %OSPF-4-UNREC_TIMER: Unrecognized timer [dec] in OSPF [chars] Explanation An internal error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


OSPF-6 Error Message %OSPF-6-BAD_LSA_COUNT: OSPF-%d Area %s: LSA ID %i, Type %d, Adv-rtr %i, LSA counter %s Explanation An internal error was found and automatically corrected in an OSPF Link-State Advertisement (LSA). This error does not affect operation. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show tech-support ospf commands and your pertinent troubleshooting logs.


1089

OSPFv3 Messages

Error Message %OSPF-6-PROC_REM_FROM_INT: OSPF process [dec] removed from interface [chars] Explanation The OSPF process was removed from the interface due to IP VRF removal. Recommended Action No action is required.

Error Message %OSPF-6-UNREC_VIRT_INT_TYPE: Unrecognized virtual interface [chars]. Treat it as loopback stub route Explanation Because the virtual interface type was not recognized by OSPF, it will be treated as a

loopback interface stub route. Recommended Action No action is required.

OSPFv3 Messages This section contains Open Shortest Path First (OSPF) version 3 messages.

OSPFv3-3 Error Message %OSPFv3-3-CFG_NBR_ALLOC_FAILED: Could not allocate or find the neighbor Explanation An internal error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %OSPFv3-3-INT_ATTACHED_MULTI_AREAS: Interface [chars] is attached to more than one area Explanation The interface is attached on the interface list to an area other than the one that the interface links to. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1090

OSPFv3 Messages


Error Message %OSPFv3-3-INT_INIT_FAILED: Init failed for interface [chars], [chars]. Explanation The interface initialization failed. Possible reasons include:

- The area to which the interface is being attached is being deleted. - It was not possible to create the link scope database. - It was not possible to create a neighbor datablock for the local router. Recommended Action Remove the configuration command that covers the interface and then try it again. If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

OSPFv3-4 Error Message %OSPFv3-4-AREA_MISMATCH: Received packet with incorrect area from[ipv6_addr], [chars], area [IP_address], packet area [IP_address] Explanation An OSPF packet was received with an area ID in its header that does not match the area of this interface. Recommended Action Check the OSPF configuration of the receiver and the sender for inconsistency.

Error Message %OSPFv3-4-ASBR_WITHOUT_VALID_AREA: Router is currently an ASBR while having only one area which is a stub area Explanation An ASBR must be attached to an area which can carry AS external or NSSA LSAs. Recommended Action Make the area to which the router is attached into an NSSA or regular area.

Error Message %OSPFv3-4-CFG_NBR_INVAL_NBMA_OPT: Can not use configured neighbor: cost and database-filter options are allowed only for a point-to-multipoint network Explanation The configured neighbor was found on an NBMA network and either the cost or

database-filter option was configured. These options are only allowed on point-to-multipoint type networks. Recommended Action Check the configuration options for the neighbor command and correct the



1091

OSPFv3 Messages

Error Message %OSPFv3-4-CFG_NBR_INVAL_NET_TYPE: Can not use configured neighbor: neighbor command is allowed only on NBMA and point-to-multipoint networks Explanation The configured neighbor was found on a network for which the network type was neither NBMA or point-to-multipoint. Recommended Action No action is required.

Error Message %OSPFv3-4-CFG_NBR_INVAL_P2MP_OPT: Can not use configured neighbor: poll and priority options are allowed only for a NBMA network Explanation The configured neighbor was found on a point-to-multipoint network and either the poll

or priority option was configured. These options are only allowed on NBMA type networks. Recommended Action Check the configuration options for the neighbor command and correct the


Error Message %OSPFv3-4-CFG_NBR_NOT_NBMA_NET: Neighbor command allowed only on NBMA networks Explanation Neighbor command allowed only on NBMA networks. Recommended Action Check the configuration options for the neighbor command and correct the


Error Message %OSPFv3-4-CFG_NBR_P2MP_NEEDS_COST: Can not use configured neighbor: cost or database-filter option is required for point-to-multipoint broadcast network Explanation The configured neighbor was found on a point-to-multipoint broadcast network. Either

the cost or database-filter option needs to be configured. Recommended Action Check the configuration options for the neighbor command and correct the


Error Message %OSPFv3-4-DBD_ALLOC_FAIL: Could not allocate DBD packet Explanation An internal error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1092

OSPFv3 Messages

Error Message %OSPFv3-4-DB_NOT_FOUND: Can’t find LSA database type [hex], area [hex] , interface [hex] Explanation An internal error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %OSPFv3-4-INVALID_METRIC: OSPFv3-%d Area %s: Router %i originating invalid type 0x%x LSA, ID %u, Metric %d on Link ID %d Link Type %d Explanation The specified router has originated a Link-State Advertisement (LSA) with an invalid

metric. If this is a router LSA and the link metric is zero, routing loops and traffic loss could occur in the network. Recommended Action On the router that originated the reported LSA, configure a valid metric for the

given LSA type and link type.

Error Message %OSPFv3-4-INV_LSA_BLD_FLG: Invalid build flag [hex] for LSA [IP_address], type [hex] Explanation An internal error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %OSPFv3-4-NO_GLOBAL_ADDR: Could not select a global IPv6 address. Virtual links require at least one global IPv6 address. Explanation A virtual link was configured. For the virtual link to function, a global IPv6 address

must be available. However, no global IPv6 address could be found on the router. Recommended Action Configure a global IPv6 address on an interface on this router.


1093

OSPFv3 Messages

Error Message %OSPFv3-4-NO_OUTPUTQ: Packet not written to the output queue Explanation An internal error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %OSPFv3-4-NULL_LINKAGE: Doubly linked list linkage is NULL Explanation An internal error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %OSPFv3-4-NULL_PREV_LINKAGE: Doubly linked list prev linkage is NULL [hex] Explanation An internal error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %OSPFv3-4-RTRID_IN_USE: Router-ID [IP_address] is in use by ospf process [dec] Explanation An attempt was made to assign a router ID that is in use by another process. Recommended Action Configure another router ID for one of the processes.


1094

OSPFv3 Messages

Error Message %OSPFv3-4-TIMER_ERROR: Error for timer [dec] in OSPF process [chars] Explanation An internal error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %OSPFv3-4-TWO_INT_ON_LINK: Multiple interfaces ([chars]/[chars]) on a single link detected. This is not supported Explanation OSPFv3 enabled on multiple interfaces that are on the same link is not supported. Recommended Action OSPFv3 should be disabled or made passive on all but one of the interfaces.

Error Message %OSPFv3-4-UNREC_TIMER: Unrecognized timer [dec] in OSPF [chars] Explanation An internal error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


OSPFv3-6 Error Message %OSPFv3-6-UNREC_VIRT_INT_TYPE: Unrecognized virtual interface [chars]. Treat it as loopback stub route Explanation Because the virtual interface type was not recognized by OSPFv3, it will be treated as a loopback interface stub route. Recommended Action No action is required.


1095

OTNMGR Messages

OTNMGR Messages Error Message %OTNMGR-3-OTN_STATS_CREATE_IF_FAIL: stats for interface index [dec] could not be created with status [dec] Explanation N/A Recommended Action Copy the message exactly as it appears on the console or in the system log.


PACC Messages This section contains Cisco 7300 port adapter carrier card (PACC) messages.

PACC-3 Error Message %PACC-3-RXPAKLEN: PA-CC FPGA detected an ingress packet length error on slot [dec] Explanation The PA carrier card has detected a packet length error during reception of an ingress

packet.This condition could be caused by one of the following: - Faulty hardware (either the Cisco 7300 or the PA carrier card) - A corrupted FPGA image - A software problem (least likely). Recommended Action If this message occurs frequently, remove and reinsert the PA carrier card. If

reseating the card does not fix the problem, a later Cisco IOS image may have an updated FPGA bundle that could solve the problem. If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


1096

PACKET Messages

Error Message %PACC-3-TXPAKLEN: PA-CC FPGA detected an egress packet length error on slot [dec] Explanation The PA carrier card has detected a packet length error during transmission of an egress

packet. This condition could be caused by one of the following: - Faulty hardware (either the Cisco 7300 or the PA carrier card) - A corrupted FPGA image - A software problem (least likely). Recommended Action If this message occurs frequently, remove and reinsert the PA carrier card. If

reseating the card does not fix the problem, a later Cisco IOS image may have an updated FPGA bundle that could solve the problem. If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

PACKET Messages This section contains packet messages.

Error Message %PACKET-3-BLKDUMP: [chars] Explanation This message is for reporting general messages in the memory management code. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PACKET-3-CLNTDISCONN: Handling disconnect for client [dec] ([chars]) Explanation The client ID was not found in the previous client list. Recommended Action Remove the client’s information from the list of all connected clients. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using


1097

PACKET Messages

the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %PACKET-3-CORRUPTPAKHDR: Corruption in packet header [hex], pid [dec], magic [hex], buffer [hex] caller_pc [hex] Explanation The packet header has become corrupted. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PACKET-3-CORRUPTPAKPOOL: [chars] Pool [hex] corrupted, magic [hex]

Explanation The packet pool has become corrupted and has failed a consistency check. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PACKET-3-ERRORPUNT: Intransit flag not set in [dec] Explanation A packet that is being redirected across processes does not have the Intransit flag set. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1098

PACKET Messages


Error Message %PACKET-3-ERRPAKHDR: Not able to fix corruption in packet header [hex], pid = [dec] Explanation There has been a corruption in the packet header memory and it cannot be fixed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PACKET-3-PACKETHDRDUMP: [chars] Explanation This message is used to report general packet header messages. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PACKET-3-PARTICLEPAKDUPFAIL: Particle packet duplication attempted on non-particle packet Explanation Duplication of packet with particles routine is called without the packet containing

particles. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1099

PAGP_DUAL_ACTIVE Messages

Error Message %PACKET-3-RECOVERBLK: BLOCK [hex] IS SUCESSFULLY RECOVERED AFTER CORRUPTION Explanation Corruption was detected in a memory block, and it was possible to recover the block

successfully. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PACKET-3-REINITSHMEM: Restarting [chars] to reinitialize shared memory because of memory corruption Explanation There has been a memory corruption. Recommended Action Restart the client to reinitialize shared memory. Copy the message exactly as

it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

PAGP_DUAL_ACTIVE Messages This section contains Port Aggregation Protocol (PAgP) messages.

PAGP_DUAL_ACTIVE-1 Error Message %PAGP_DUAL_ACTIVE-1-RECOVERY: PAgP running on [chars] triggered dual-active recovery: active id [enet] received, expected [enet] Explanation PAgP detected that the virtual switches were in a dual-active mode on the specified

interface. PAgP caused a switch to go into recovery mode. Recommended Action No action is required.


1100


PAGP_DUAL_ACTIVE-3 Error Message %PAGP_DUAL_ACTIVE-3-ADD_TLV_FAIL: Too few bytes for [chars] TLV in PAgP (reqd. [dec], got [dec]) on port [chars] Explanation The dual-active type-length-value (TLV) could not be added to the PAgP packet due to

too few bytes in the packet. PAgP dual-active detection may be disabled as a result. Recommended Action Enter these commands:

show switch virtual dual-active summary show switch virtual dual-active pagp Retrieve the PAgP packet contents by entering these commands: debug condition interface intfc debug pagp packet Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %PAGP_DUAL_ACTIVE-3-OBJECT_CREATE_FAILED: Unable to create "[chars]" Explanation The specified managed object could not be created. Recommended Action No action is required.

Error Message %PAGP_DUAL_ACTIVE-3-PROC_CREATE_FAILED: Unable to create process "[chars]" Explanation The specified process could not be created. Recommended Action No action is required.

Error Message %PAGP_DUAL_ACTIVE-3-RECOVERY_TRIGGER: PAgP running on [chars] informing virtual switches of dual-active: new active id [enet], old id [enet] Explanation PAgP received a new active ID on the specified interface, indicating that the virtual

switches are in a dual-active mode. When PAgP notifies the virtual switches, one switch will enter recovery mode. Recommended Action No action is required.


1101


Error Message %PAGP_DUAL_ACTIVE-3-REGISTRY_ADD_ERR: Failure in adding to [chars] registry Explanation A function could not be added to the registry. Recommended Action No action is required.

PAGP_DUAL_ACTIVE-4 Error Message %PAGP_DUAL_ACTIVE-4-NO_CHNL_GROUP: Port [chars] channel group not present while [chars] Explanation Although the channel group was expected to be present in a link, it could not be

extracted. This error may affect functionality, depending on where it occurred. This message indicates a software bug, and should not be seen under normal operation Recommended Action Enter these commands:

show switch virtual dual-active summary show switch virtual dual-active pagp Retrieve the PAgP packet contents by entering these commands: debug condition interface intfc debug pagp packet Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


1102

PAGP_SWITCH_ISSU Messages

PAGP_SWITCH_ISSU Messages This section contains Port Aggregation Protocol (PAgP) switch in-service software upgrade (ISSU) messages.

PAGP_SWITCH_ISSU-3 Error Message %PAGP_SWITCH_ISSU-3-BUFFER: PAGP SWITCH ISSU client failed to get buffer for message, error %d Explanation The port aggregation protocol (PAgP) switch ISSU client was unable to get buffer space for building a negotiation message. As a result, it cannot send the negotiation message to the standby unit and the standby unit cannot be brought up. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PAGP_SWITCH_ISSU-3-CAPABILITY: PAGP SWITCH ISSU client %s Explanation During capability negotiation, the PAGP switch ISSU client detected an error that will

result in a mismatch in the client capability between the active and standby unit. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1103


Error Message %PAGP_SWITCH_ISSU-3-INIT: PAGP SWITCH ISSU client initialization failed at %s, error %s Explanation The PAGP switch ISSU client could not be initialized. This condition will cause



Error Message %PAGP_SWITCH_ISSU-3-MSG_NOT_OK: PAGP SWITCH ISSU client message %d is not compatible Explanation The PAGP switch ISSU client received an incompatible message from the peer unit. The

message cannot be processed by this unit. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PAGP_SWITCH_ISSU-3-MSG_SIZE: PAGP SWITCH ISSU client failed to get the message size for message %d Explanation The PAGP switch ISSU client was unable to calculate the message size for the message specified. The client will be unable to send the message to the standby unit. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1104


Error Message %PAGP_SWITCH_ISSU-3-POLICY: PAGP SWITCH ISSU client message type %d is %s Explanation The PAGP switch ISSU client received a message type that it does not support. A policy is applied to make the session compatible. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PAGP_SWITCH_ISSU-3-SEND_FAILED: PAGP SWITCH ISSU client failed to send a negotiation message, error %d Explanation The PAGP switch ISSU client could not send a session negotiation message to the peer.



Error Message %PAGP_SWITCH_ISSU-3-SESSION: PAGP_SWITCH ISSU client %s Explanation The PAGP switch ISSU client detected an error during a session negotiation with the

peer unit. As a result, the standby unit cannot be brought up. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1105

PARSER Messages

Error Message %PAGP_SWITCH_ISSU-3-SESSION_UNREGISTRY: PAGP SWITCH ISSU client failed to unregister session information. Error: %d (%s) Explanation The PAGP switch ISSU client was unable to unregister session information. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PAGP_SWITCH_ISSU-3-TRANSFORM: PAGP SWITCH ISSU client %s transform failed, error %s Explanation The PAGP switch ISSU client could not transform the message. If the transmit

transformation failed, the checkpoint message cannot be sent to the standby unit. If the receive transformation failed, the checkpoint message cannot be applied on the standby unit. In either case, the PAGP_SWITCH state will not be identical with the active unit. Recommended Action Copy the message exactly as it appears on the console or in the system log.


PARSER Messages This section contains parser messages.

PARSER-3 Error Message %PARSER-3-BADUNLOCKREQ: Unlock requested by process ’[dec]’. You are not the lock owner Explanation A configuration unlock has been requested by an alien. Recommended Action Check the code flow for an unwanted configuration unlock request.


1106

PARSER Messages

Error Message %PARSER-3-CFGLOG_CLI_INITFAILED: Initialization of the Config Log CLI failed. Explanation Initialization of the configuration log CLI failed. Configuration logging CLI commands may not be accessible. The configuration logger may not be accessible by using Cisco IOS software CLI commands. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PARSER-3-CFGLOG_EMPTYCMD: User:[chars] Explanation The user specified entered an empty command for which a log attempt was made.

Normally, empty commands will not be logged. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PARSER-3-CFGLOG_INCONSISTENT: User:[chars] command:[chars] Explanation When logging a command entered by CLI, the configuration logger detected an

inconsistency in the log. This inconsistency may result in a failure to log the command. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1107

PARSER Messages

Error Message %PARSER-3-CFGLOG_INITFAILED: Initialization of the Config Log subsystem failed. Explanation During initialization of the configuration logger subsystem, one or more queues or data

structures that are essential to the configuration logger could not be set up. As a result, the configuration logger will not be available for use. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Execute a show version command. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %PARSER-3-CFGLOG_NOMEM: User:[chars] [chars] Explanation The command that was entered could not be logged because of a lack of memory. The

configuration logger will free old entries one by one until the system logger (syslog) has enough memory to log the command so that an NMS can receive notification of it. Recommended Action Attempt to free up memory on the router by stopping nonessential processes or

unused features that may be running. Once sufficient memory is available, this message no longer appears.

Error Message %PARSER-3-CFGLOG_NOUSER: Command:[chars] Explanation The user could not be determined while this command was being logged. The command

could not be saved in the configuration log. Recommended Action Copy the error message exactly as it appears. Enter the show version

command, and copy the displayed information. Determine (if possible) which users are currently logged in to the router, and who was copying configuration files or executing commands in global configuration mode (or via SNMP or HTTP). If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %PARSER-3-CFGLOG_PERSIST_APPLY_CMD_FAILED: Configuration logger persistency: Applying config command ’[chars]’ failed. result ’[dec]’. Explanation When applying the command to the running configuration, the parser returned an error. Recommended Action Verify that no other process locks the configuration mode during this time. The

parser could be locked by the HA or SNMP or by some other process.


1108

PARSER Messages

Error Message %PARSER-3-CFGLOG_PERSIST_DB_OPEN_FAILED: Configuration logger persistency: opening persist db failed. File ’[chars]’. Explanation The file open for writing or reading persisted commands has failed. Recommended Action Check for the file system availability. The file system might have been

corrupted. Try formatting the file system.

Error Message %PARSER-3-CFGLOG_PERSIST_FILESYS_FULL: Configuration logger persistency: Add command to persistent db failed. File system ’[chars]’ full. Explanation When logging a CLI command to the configuration logger persistent database, the

configuration logger persistency detected zero bytes free in the file system. Recommended Action Check the space available in the file system. Enter the dir filesystemname:

command to display the free bytes. Clear some space for the configuration logger persistency feature to continue to store the config commands logged in the persistent database.

Error Message %PARSER-3-CFGLOG_PURGEFAILED: Purge config log failed. Explanation An attempt to purge some of the configuration log entries failed. Recommended Action Copy the error message exactly as it appears. Execute a show version

command, and copy the displayed information. Contact your technical support representative with this information.

Error Message %PARSER-3-CFGLOG_RESIZE_FAILED: Could not resize the config logger to new size:[dec] Explanation Due to an internal error, a request to resize the configuration log was not carried out.

Besides a failure to resize, there should be no change in the behavior of the configuration logger. Recommended Action Copy the error message exactly as it appears. Enter the show version



1109

PARSER Messages

Error Message %PARSER-3-CFGLOG_SESSIONERR: Could not delete config log session:[dec] for user:[chars]. Explanation When a user logged out, the configuration logger was unable to clean up information

about the user’s login session. The result might be a memory leak or an inability to add new commands to the configuration log. Recommended Action Copy the error message exactly as it appears. Enter the show version


Error Message %PARSER-3-CONFIGNOTLOCKED: Unlock requested by process ’[dec]’. Configuration not locked. Explanation A configuration unlock was requested on a free lock. Recommended Action Check the code flow for an excess configuration unlock request.

PARSER-4 Error Message %PARSER-4-INVLDSYNTX: Syntax clean up called while not syntax checking. FuncPtr / Context [chars] Explanation Functions were mistakenly called. There may be more than those listed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1110

PARSER Messages

PARSER-5 Error Message %PARSER-5-CFGLOG_LOGGEDCMD: User:[chars] logged command:[chars] Explanation The configuration logger, which logs every CLI command, has an option to log

messages to system logging (syslog). If this option is enabled, this message will be displayed every time a CLI command is processed. This message does not denote any error condition and is a part of the normal operation of the parser and configuration logger. Recommended Action If you prefer not to see this syslog message, enter the no cfglog send to syslog

command.

Error Message %PARSER-5-CFGLOG_PERSIST_APPLY_ON_RELOAD: Apply persisted config cmds on reload switched off Explanation The switch that controls the persisted commands applied during reload is set to off. Recommended Action From the ROMMON prompt, verify the value of the ROMMON

logpersistreload variable. This variable might have been intentionally set to off.

PARSER-6 Error Message %PARSER-6-CONFIGLOCKCLEARED: Configuration lock cleared by user ’[chars]’ process ’[dec]’ from terminal ’[dec]’ Explanation The configuration lock was cleared using the clear configuration lock command. Recommended Action This is a notification message only. No action is required.

Error Message %PARSER-6-CONFIGLOCKNOTSUPPORTED: Configuration lock not supported for this transport ’[chars]’ Explanation The configuration lock was enabled from a transport other than Telnet or SSH. Recommended Action This is a notification message only. No action is required.

Error Message %PARSER-6-EXPOSEDLOCKACQUIRED: Exclusive configuration lock acquired by user ’[chars]’ from terminal ’[dec]’ Explanation An exclusive configuration lock was acquired by the user. Recommended Action This is a notification message only. No action is required.


1111

PARSER Messages

Error Message %PARSER-6-EXPOSEDLOCKRELEASED: Exclusive configuration lock released from terminal ’[dec]’ Explanation An exclusive configuration lock was released by the user. Recommended Action This is a notification message only. No action is required.

Error Message %PARSER-6-LI_VIEW_INIT: LI-View initialised. Explanation A lawful intercept (LI) view was successfully initialized. Recommended Action No action is required.

Error Message %PARSER-6-SUPER_VIEW_CREATED: super view ’%s’ successfully created. Explanation A super view was successfully created and the system has entered the view

configuration mode. Recommended Action No action is required.

Error Message %PARSER-6-SUPER_VIEW_DELETED: super view ’%s’ successfully deleted. Explanation A super view was successfully deleted. Recommended Action No action is required.

Error Message %PARSER-6-SUPER_VIEW_EDIT_ADD: view %s added to superview %s. Explanation A view was successfully added to the super view. All view related configuration can

now be accessed from the super view. Recommended Action No action is required.

Error Message %PARSER-6-SUPER_VIEW_EDIT_REMOVE: view %s removed from superview %s. Explanation A view was successfully removed from the super view. Recommended Action No action is required.

Error Message %PARSER-6-VIEW_CREATED: view ’%s’ successfully created. Explanation A view was successfully created and the system has entered the view configuration

mode. Recommended Action No action is required.


1112

PARSE_RC Messages

Error Message %PARSER-6-VIEW_DELETED: view ’%s’ successfully deleted. Explanation The required view was successfully deleted. Recommended Action No action is required.

Error Message %PARSER-6-VIEW_SWITCH: successfully set to view ’%s’. Explanation The view was successfully selected. Recommended Action No action is required.

PARSE_RC Messages This section contains PARSE_RC-related error messages.

PARSE_RC-3 Error Message %PARSE_RC-3-PRC_INTERRUPT: [chars] Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PARSE_RC-3-PRC_INVALID_BLOCK_PTR: Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1113

PARSE_RC Messages

Error Message %PARSE_RC-3-PRC_INVALID_CSB: Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PARSE_RC-3-PRC_OUT_OF_RANGE_ENUM: [chars] had value [int] Explanation An out-of-range parameter was passed to an internal API. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PARSE_RC-3-PRC_UNRECOGNIZED_ERROR: error value ‘[dec]’ is not currently mapped Explanation An unrecognized error was caught and remapped. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1114

PBI_OPEN Messages

PARSE_RC-4 Error Message %PARSE_RC-4-PRC_NON_COMPLIANCE: ‘[chars]’ Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


PARSE_RC-6 Error Message %PARSE_RC-6-PRC_DISABLE: Parser PRC Feature Disabled Explanation The parser return code (PRC) feature is disabled. Recommended Action No action is required.

Error Message %PARSE_RC-6-PRC_ENABLE: Parser PRC Feature Enabled. PRC logs are displayed for configration commands alone Explanation The parser return code (PRC) feature is enabled. PRC logs are displayed for

configuration commands alone. Recommended Action No action is required.

PBI_OPEN Messages This section contains programmable binary file data processing (PBI_OPEN) messages.

PBI_OPEN-4 Error Message %PBI_OPEN-4-ERROR_ALLOC: %Error: Can’t allocate [dec] bytes for pbi data Explanation The system is unable to allocate required memory to access the file. Recommended Action Check the memory usage of the system and retry the operation.


1115

PBR Messages

Error Message %PBI_OPEN-4-ERROR_OPEN: %Error: Can’t open [chars] Explanation The system is unable to open the file specified. Recommended Action Ensure that the filename is correct. Enter the dir command to verify the file

name.

Error Message %PBI_OPEN-4-ERROR_READ: %Error: pbi file [chars] read failed Explanation An unknown error has occurred while the system was copying the PBI program file to

a local buffer. Recommended Action The file name is specified in the message by [chars]. Enter the del filename command to remove the file. Use the copy command to recopy the file from a known good source to its desired destination filename. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %PBI_OPEN-4-ERROR_SIZE: %Error: Bad file size [chars] Explanation The file is too small or too large for a PBI program file. Recommended Action Enter the dir command and verify the size of the file. Retry the operation.

PBR Messages This section contains Policy-Based Routing (PBR) messages.

PBR-2 Error Message %PBR-2-NO_RMAP: Cannot create PBR data structures for route-map [chars] Explanation The PBR manager could not allocate the data structures needed to describe a route map

being used for policy routing. This condition is probably caused by lack of available memory. Recommended Action Use a less complicated configuration that requires less memory.


1116

PBR Messages

PBR-3 Error Message %PBR-3-INSTALL_FAIL: Policy route-map [chars] not installed in hardware Explanation The PBR manager was unable to install the complete route map in the hardware, so it will have to be applied in software. This requires the packets to be forwarded by the CPU. Recommended Action Reconfigure the route map to use a simpler configuration. Use the same route

map on multiple interfaces, if possible.

Error Message %PBR-3-MERGE_FAIL: [chars] ACL merge error [dec] on route-map [chars] Explanation The PBR manager could not complete the merge of the configured route map into a form

suitable for loading into the hardware. The most likely cause is specifying an ACL that is too large or too complex for the system to handle. Recommended Action Try specifying a smaller and less complicated configuration.

Error Message %PBR-3-NO_LABEL: Cannot allocate label for route-map [chars] Explanation The PBR manager could not allocate a label for this route map. This means that the

hardware cannot be programmed to implement policy routing. There is a limit of 247 labels for policy routing Recommended Action Use a less complicated configuration that allows label sharing. Use the same

route maps on multiple interfaces, if possible.

Error Message %PBR-3-UNSUPPORTED_RMAP: Route-map [chars] not supported for Policy-Based Routing Explanation The route map attached to an interface for policy routing contains an action that is not

supported on this platform. This is a hardware limitation. Recommended Action Reconfigure the route map. Use only permit entries and set ip next-hop actions in the route map.


1117

PCIELIB Messages

PBR-4 Error Message %PBR-4-CPU_SUPPORTED_ACTION: Set action in sequence [dec] of route-map [chars] supported by forwarding to CPU Explanation The route map attached to an interface for policy routing contains an action that is not

supported in hardware, such as a set interface, set ip default next-hop, set default interface, or set ip df action. Because the action is not supported in hardware, the packets must be forwarded by the CPU. Recommended Action Reconfigure the route map. Use only set ip next-hop in the route map, if

possible.

Error Message %PBR-4-RETRY_INSTALL: Route-map [chars] installed in hardware upon retry Explanation The PBR manager was able to fit the complete configuration into the hardware. One or

more route maps had previously not been loaded because of lack of space. Recommended Action No action is required.

PCIELIB Messages This section contains The PCI library messages.

PCIELIB-1 Error Message %PCIELIB-1-NULL_RC: The pointer to root complex [[dec]] is NULL. Explanation The pointer to the specified root complex is NULL. Recommended Action Copy the error message exactly as it appears on the console or in the system



1118

PCIELIB Messages

PCIELIB-2 Error Message %PCIELIB-2-INSERT_FAILURE: Failed to insert [hex] into [chars] list. Explanation Failed to insert item into the specified list. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %PCIELIB-2-MMAP_FAILURE: Failed to perform mmap for [chars], errno = [chars]. Explanation Failed to perform mmap for the specified memory Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %PCIELIB-2-NO_JID: Could not get my job id. pid [dec] Explanation Could not get my job id Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %PCIELIB-2-PCIELIB_INIT: Could not initialize PCIE library for process [dec] Explanation Could not initialize PCIE library. Recommended Action Copy the error message exactly as it appears on the console or in the system



1119

PCIELIB Messages


Error Message %PCIELIB-2-REMOVE_FAILURE: Failed to remove [hex] from [chars] list. Explanation Failed to remove item from the specified list Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %PCIELIB-3-REUSE_LAWBAR: LAWBAR #[dec] is used. orig value = [hex]. Explanation The specified LAWBAR register was used for other purpose. Recommended Action Copy the error message exactly as it appears on the console or in the system


PCIELIB-3 Error Message %PCIELIB-3-SHM_OPEN_FAIL: Failed to open shm [chars] errno = [chars]. Explanation Failed to open the specified shared memory.

Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.


1120

PCMCIAFS Messages

PCMCIAFS Messages This section contains PCMCIA disk messages.

PCMCIAFS-3 Error Message %PCMCIAFS-3-RESETERR: PCMCIA disk [dec] [chars] Explanation A PCMCIA disk could not be reset while the system was being initialized or reloaded. This condition will cause a transient disk error or disk timeout error when the ROMMON initialization code tries to read the DIB. This is a transient error and the system will be able to access the disk and continue normal operation. Recommended Action This is an informational message only. No action is required.

PCMCIAFS-4 Error Message %PCMCIAFS-4-DFS_FSCK_ERR: Error while running fsck on the file [chars]. Explanation The fsck process was running in a loop while walking through the cluster chain of a file

and has aborted. Recommended Action Copy the message exactly as it appears on the console or in the system log.


PCMCIAFS-5 Error Message %PCMCIAFS-5-DFS_CLOSE_ERR: Error during close of the file [chars]. [chars] Explanation An error occurred during a file close operation. Recommended Action Enter the fsck filesystem prefix: command to check and attempt to repair the

disk. If this does not fix the problem, format the disk.


1121

PF_ASIC Messages

PF_ASIC Messages This section contains protocol filtering messages.

PF_ASIC-3 Error Message %PF_ASIC-3-ASIC_DUMP: [[dec]:[hex]] [chars] = [hex] Explanation This message includes relevant ASIC counters that might help to diagnose the problem

with the switching bus. Recommended Action Copy this message and the SWITCHING_BUS_IDLE message exactly as they

appear on the console or in the system log. Contact your Cisco technical support representative with the output. Include this output along with SWITCHING_BUS_IDLE error message.

PF-ETHERCHANNEL Messages This section contains Policy Feature Card Etherchannel messages.

Error Message %PF_ETHERCHANNEL-3-MLACP_EXTENDED_MISMATCH: An inconstistency was detected between the operational and the configured mlacp-extended mode. Reloading. ([chars]) Explanation This error message is printed if there is an inconsistency between the persistent storage stored mode and the configuration mode. It will be display on the SP on boot-up. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %PF_ETHERCHANNEL-3-MLACP_EXTENDED_MISMATCH: An inconstistency was detected between the operational and the configured mlacp-extended mode. Reloading. ([chars]) Explanation Use of Module [dec] prevents this system from being able to operate at full NEBS

compliance levels. Recommended Action For further information, please refer to Cisco.com technical documentation for

this module.


1122

PFINIT Messages

PFINIT Messages This section contains platform initialization (PFINIT) messages.

PFINIT-1 Error Message %PFINIT-1-CONFIG_SYNC_FAIL: Sync’ing the [chars] configuration to the standby Router FAILED, the file may be already locked by a command like: show config. Explanation The active router could not synchronize its configuration with the redundant router. This

condition might be a transient one that was caused by the configuration file being temporarily used by another process. Recommended Action Retry the synchronization operation.

Error Message %PFINIT-1-CONFIG_SYNC_FAIL_RETRY: Sync’ing the [chars] configuration to the standby Router FAILED, the file may be already locked by a command like: show config. Will attempt to sync [dec] more time[chars] Explanation The active router could not synchronize its configuration with the redundant router. This

condition might be a transient one that was caused by the configuration file being temporarily used by another process. Recommended Action The synchronization operation will be retried the specified number of times.

Error Message %PFINIT-1-CONFIG_SYNC_FAIL_SECONDARY_SYNC_RETRY: Sync’ing the [chars] configuration to the standby Router FAILED with error: [chars] ([dec]).Will attempt to sync [dec] more time[chars] Explanation The active router could not synchronize its configuration with the redundant router. This

condition might be a transient one that was caused by the configuration file being temporarily used by another process. Recommended Action Retry the synchronization operation.

Error Message %PFINIT-1-CONFIG_SYNC_SIZE_NULL: Active config file is empty. No sync of the [chars] configuration file required. Explanation The configuration of the active switch was not synchronized with the standby switch

because the configuration file of the active switch is empty. This condition might have been the result of the user entering a write erase command on the active router prior to synchronization between the active and standby switches. Recommended Action If the empty configuration file was the result of user-entered CLI, no action is required. If this was an unexpected condition, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at


1123

PFINIT Messages


PFINIT-2 Error Message %PFINIT-2-IPCSEAT: Unable to add/remove IPC seats for %s Explanation The platform initialization subsystem could not add or remove interprocess

communication (IPC) elements (seats). Recommended Action Copy the message exactly as it appears on the console or in the system log.


PFINIT- 4 Error Message %PFINIT-4-IPC_ICC_INIT_FAIL: Failed to [chars] Explanation The PF subsystem failed to initialize some IPC/ICC information. Recommended Action Copy the error message exactly as it appears on the console or in the system



1124

PF_ISSU Messages

PFINIT-5 Error Message %PFINIT-5-CONFIG_SYNC_NOT_SUPPORTED: Sync'ing the [chars] configuration to the standby Router is not supported. Explanation The configuration has not been successfully synchronized with the standby router.

[chars] is the configuration name. Recommended Action No action is required.

PFINIT-6 Error Message %PFINIT-6-ACTIVE_NON_VS: Active supervisor is in standalone mode, but SWITCH_NUMBER rommon variable set on the standby or standby having vsl config.Setting SWITCH_NUMBER variable in rommon to 0 and resetting the standby. Explanation The active supervisor is up in standalone mode while standby’srommon has

SWITCH_NUMBER set. Clearing SWITCH_NUMBER rommon variable and resetting the standby Recommended Action This is an informational message. No action is required.

PF_ISSU Messages This section contains high availability platform in-service software upgrade (ISSU) infrastructure messages.

PF_ISSU-3 Error Message %PF_ISSU-3-ISSU_NEGO_LC_RESET: ISSU negotiation failed between endpoint %d and line card %d, for ISSU client %d Explanation ISSU negotiation failed between an endpoint and a line card. The line card must be


Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show issu sessions commands and your pertinent troubleshooting logs.


1125

PF_OBFL Messages

PF_OBFL Messages This section contains platform on-board failure logging (OBFL) messages.

PF_OBFL-5 Error Message %PF_OBFL-5-FEATURE: Platform OBFL [chars] feature initialization fails in slot [dec]. Explanation The PF subsystem could not initialize the on-board failure logging (OBFL) feature

specified by [chars]. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PF_OBFL-5-STORAGE: Platform OBFL storage ([chars]) initialization fails in slot [dec]. Explanation The PF subsystem could not initialize on-board failure logging (OBFL) storage flash. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1126

PF_PRST_VBL Messages

PF_PRST_VBL Messages This section contains platform persistent variable messages.

PF_PRST_VBL-3 Error Message %PF_PRST_VBL-3-MEDIA: PF persistent variable media error: %s Explanation A media error was detected with the persistent variable PF interface. Recommended Action Copy the message exactly as it appears on the console or in the system log.


PFREDUN Messages This section contains Policy Feature Card Redundancy (PFREDUN) messages.

PFREDUN-1 Error Message %PFREDUN-1-VTP_CONFIG_DISLOCATE: VTP config file must be in default location for standby supervisor to come online Explanation The redundant supervisor engine failed to come online because the VTP configuration

file is not in the default location. Recommended Action Reset the redundant supervisor engine, and then configure the VTP

configuration file so that it is in the default location.


1127

PFREDUN Messages

PFREDUN-3 Error Message %PFREDUN-3-ACTIVE_FORCED_TO_RELOAD: Active not able to operate properly. Standby is ready to take over and forced active to reload. Explanation The active supervisor engine is not operating properly. It is failing to respond. The

standby supervisor engine is ready to take over and forces the active supervisor engine to reload. Recommended Action If the active does not reload successfully, copy the message exactly as it


Error Message %PFREDUN-3-CCMODE_MISMATCH: Standby Supervisor cannot support Configured Card Mode [chars]([hex]) due to [chars](enf mask [hex], cap mask [hex], msg ver [hex])! Explanation The active supervisor engine is in user-configured mode (for example, DFC-only

mode). The active supervisor engine attempts to bring the standby supervisor engine on line, but incompatible software on the standby cannot support this mode The active keeps the standby in ROMMON mode. Recommended Action Remove the user-configured mode on the active supervisor engine so that the

active can bring the standby on line.

Error Message %PFREDUN-3-STANDBY_OUT_OF_SYNC: Active and Standby are out of sync. Explanation The active supervisor engine and standby supervisor engine are out of synchronization.

This condition may be due to communication failure, configuration synchronization failure, or another cause. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1128

PFREDUN Messages

Error Message %PFREDUN-3-SUP: [chars] Explanation The supervisor engine failed to boot because it detected that the system might contain

an invalid combination of supervisor engines. Recommended Action Examine all modules in the system, and look for an invalid combination of

supervisor engines.

PFREDUN-4 Error Message %PFREDUN-4-AUTOBOOT: [chars] Explanation The RP experienced a hardware failure or another type of failure. When the redundant

system initializes, the redundant supervisor will wait for the RP to initialize. Because the RP cannot initialize due to the failure, the redundant supervisor engine might never initialize. The default wait time for the RP to initialize (three minutes) has now expired, and the autoboot feature for the supervisor engine has been disabled. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PFREDUN-4-BOOTSTRING_INVALID: The bootfile [chars] is not present in standby Explanation The bootfile that is configured is not present on the redundant supervisor engine. If the

redundant supervisor engine resets, it will not come up because it will not find the image specified in the bootstring. Recommended Action No action is required.

Error Message %PFREDUN-4-EARL_MISMATCH_4SUP: In-Chassis Standby being disabled ([chars]) Explanation This message indicates that there is an Earl mode mismatch between the In-Chassis

Active and the In-Chassis Standby and hence In-Chassis Standby is being disabled. Recommended Action Copy the error message exactly as it appears on the console or in the system



1129

PFREDUN Messages


Error Message %PFREDUN-4-INCOMPATIBLE: Defaulting to RPR mode (%s) Explanation A runtime incompatibility exists between image versions running on the active and

standby supervisors. The redundancy mode will default to route processor redundancy (RPR). Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PFREDUN-4-PFC_MISMATCH: My PFC [chars] and Other’s PCF [chars] mismatch Explanation The active supervisor engine and the redundant supervisor engine have different

versions of the PFC daughter card. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PFREDUN-4-PFC_MISMATCH_4SUP: In-Chassis Active PFC is [chars] In-Chassis Standby PFC is [chars] Explanation This message indicates that the In-Chassis Active and the In-Chassis Standby have

different versions of the PFC. Recommended Action Copy the error message exactly as it appears on the console or in the system



1130

PFREDUN Messages

Error Message %PFREDUN-4-PHYSMEM_MISMATCH: Asymmetrical redundant configuration: Active [chars] has ([int]/[int]K) memory, Standby has ([int]/[int]K). Explanation To support the high availability feature, we recommend that your redundant supervisor

engines have symmetrical memory configurations. Recommended Action Upgrade the memory on the supervisor engine with less memory to match the amount of memory on the other supervisor engine.

Error Message %PFREDUN-4-SUP_FORCE_TO_ROMMON: Supervisor forced to rommon with reason: [chars] Explanation An application forced the supervisor engine to stay in ROMMON mode with the reason

given. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PFREDUN-4-SUP_OS: The peer supervisor is running a different operating system. Explanation The active supervisor engine is in user-configured mode (for example, DFC-only

mode). The active supervisor engine attempts to bring the standby supervisor engine on line, but incompatible software on the standby supervisor engine cannot support this mode. The active supervisor engine keeps the standby supervisor engine in ROMMON mode. Recommended Action Remove the user-configured mode on the active supervisor engine so that the

active supervisor engine can bring the standby supervisor engine on line, or insert a supervisor engine that runs the same operating system as that of the peer supervisor engine.

Error Message %PFREDUN-4-VERSION_MISMATCH: Defaulting to RPR mode ([chars]) Explanation There is a mismatch of image versions running on the active supervisor engine and on

the redundant supervisor engine. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1131

PFREDUN Messages


PFREDUN-6 Error Message %PFREDUN-6-Z_COOKIE: [chars] Explanation Informational messages regarding the presence of z-switchover cookie Recommended Action No action is required.

PFREDUN-7 Error Message %PFREDUN-7-KPA_WARN: RF KPA messages have not been heard for [dec] seconds Explanation The RF KPA messages have not been sent from the peer for the specified numbers of

seconds. This message is printed after every third KPA timer expiry. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1132

PFREDUN_SP Messages

PFREDUN_SP Messages This section contains Policy Feature Card Redundancy (PFREDUN) switch processor (SP) messages.

PFREDUN_SP-3 Error Message %PFREDUN_SP-3-DIVC_MODE_CHANGE: Redundancy mode changed to RPR Explanation The redundancy mode has changed from stateful switchover (SSO) to route processor

redundancy (RPR) because one or more base ISSU clients have failed to successfully negotiate an ISSU session. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PFREDUN_SP-3-DIVC_MODE_CHANGE_RESET: Redundancy mode changed to RPR, standby supervisor being reset Explanation The redundancy mode has changed from SSO to RPR because one or more base ISSU

clients have failed to successfully negotiate an ISSU session. The standby supervisor is being reset and will come up in RPR mode. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1133

PHY Messages

Error Message %PFREDUN_SP-3-STANDBY_NEGO_FAILED: Session not negotiated, resetting the standby sup Explanation Both the active and standby supervisors are ISSU capable but the standby failed to

negotiate its platform redundancy ISSU session. The standby supervisor must be reset. Recommended Action Copy the message exactly as it appears on the console or in the system log.


PHY Messages This section contains physical layer messages.

PHY-4 Error Message %PHY-4-CHECK_SUM_FAILED: SFP EEPROM data check sum failed for SFP interface [chars] Explanation The SFP was identified as a Cisco SFP, but the system was unable to read vendor data information to verify its correctness. Recommended Action Remove and reinsert the SFP. If it fails again in the same way, the SFP may be

defective.

Error Message %PHY-4-EXCESSIVE_ERRORS: Excessive FCS, data, or idle word errors found on interface [chars] Explanation The system has detected excessive FCS, data word, or idle word errors on the specified

interface. Recommended Action Enter the show interface command on the specified interface and check for

CRC and other input errors. If errors are excessive, enter the shut command followed by the no shut command to reset the interface.


1134

PIM Messages

PIM Messages This section contains Protocol Independent Multicast (PIM) messages.

PIM-1 Error Message %PIM-1-INVALID_RP_REG: Received Register from router %i for group %i, %i not willing to be RP Explanation A PIM router received a register message from another PIM router that thinks it is the

rendezvous point. If the router is not configured for another rendezvous point, it will not accept the register message. Recommended Action Configure all leaf routers (first-hop routers to multicast sources) with the IP

address of the valid rendezvous point.

Error Message %PIM-1-SR_INTERVAL_SETTING_ERR: Incompatible SR interval from %i on %s (%d != %d) Explanation A state-refresh capable PIM neighbor on this interface has a different setting for the state-refresh origination interval. Recommended Action Configure all PIM routers connected to this LAN to use the same state-refresh origination interval for their interfaces on the LAN.

PIM-3 Error Message %PIM-3-MVRF_NULL_PRM: Null parameter specified for MVRF lookup. Explanation A function to perform a Multicast Virtual Route Forwarding (MVRF) lookup by name

detected a NULL input parameter. The intended action cannot proceed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1135

PIM Messages

Error Message %PIM-3-RPDF_NULL_PRM: Null parameter specified for Bidir RP DF creation. Explanation A function to create a bidirectional route processor (RP) designated forwarder (DF)

entry detected a NULL input parameter. The RP DF entry cannot be created. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PIM-3-UPD_RPR_NULL_PRM: Null parameter specified for Bidir RP route update. Explanation A function to perform an update of the bidirectional RP route information detected a

NULL input parameter. The update cannot proceed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


PIM-4 Error Message %PIM-4-DEPRECATED_HELLO_TLV: Deprecated PIM Hello Option TLV %d (%s) from %i (%s) Explanation A PIM neighbor is running old software that uses deprecated Hello Option TLVs. Unless the router is upgraded, DR priority and bidirectional groups may not function properly. Recommended Action Upgrade the routers.


1136

PIM Messages

Error Message %PIM-4-INVALID_SRC_REG: Received Register from %i for (%i, %i), not willing to be RP Explanation A PIM router configured as a rendezvous point received a register message from another

PIM router, but the source of the multicast data is disallowed in this RP. Recommended Action No action is required.

PIM-5 Error Message %PIM-5-DRCHG: DR change from neighbor [IP_address] to [IP_address] on interface [chars] (vrf [chars]) Explanation A PIM neighbor is the new DR on an interface. Recommended Action This is an informational message only. No action is required.

Error Message %PIM-5-NBRCHG: neighbor [IP_address] [chars] on interface [chars] (vrf [chars]) [chars] Explanation A PIM neighbor has gone up or down on the specified interface. Recommended Action This is an informational message only. No action is required.

Error Message %PIM-5-PROXY: Deny proxy for ([IP_address], [IP_address]) from neighbor [IP_address] Explanation A PIM proxy from the specified neighbor was denied. Recommended Action No action is required.

PIM-6 Error Message %PIM-6-INVALID_RP_JOIN: Received (*, %i) Join from %i for invalid RP %i Explanation A downstream PIM router sent a join message for the shared tree, which this router does

not want to accept. This behavior indicates that this router will allow only downstream routers join to a specific rendezvous point. Recommended Action Configure all downstream leaf routers to join to the RP that is allowed by

upstream routers toward the validated rendezvous point.


1137

PIM_PROT Messages

Error Message %PIM-6-REG_ENCAP_INVALID: Bad register from %i for (%i, %i); additional info = %x %x %x %x %x %x %x %x Explanation A PIM router configured as a rendezvous point or with network address translation

(NAT) received a PIM register packet from another PIM router. The data encapsulated in this packet is invalid. Recommended Action No action is required.

Error Message %PIM-6-SA_ENCAP_INVALID: Bad SA from RP %i for (%i, %i); additional info = %x %x %x %x %x %x %x %x Explanation A PIM router configured as an MSDP peer received an SA with encapsulated data. The

data encapsulated in this packet is invalid. Recommended Action No action is required.

PIM_PROT Messages This section contains Protocol Independent Multicast (PIM) protocol messages.

PIM_PROT-3 Error Message %PIM_PROT-3-MSG_SEND_ERR: [chars] Explanation An internal error occurred while trying to send a message. Events scheduled to happen

on reception of the message, such as deletion of the PIM tunnel IDB, may not take place. Recommended Action If this message recurs, copy the message exactly as it appears on the console


PIM_PROT-4 Error Message %PIM_PROT-4-PROTOCOL_WARNING: [chars] - [chars] [chars] : [chars] Explanation Internal protocol inconsistency warning Recommended Action No action is required.


1138

PIMSN Messages

PIM_PROT-6 Error Message %PIM_PROT-6-IDB_ENABLE: Interface [chars] does not support multicast, not enabled Explanation PIM is not enabled on an interface that does not support multicast. Recommended Action This is an informational message only. No action is required.

PIM_PROT-7 Error Message %PIM_PROT-7-INTERNAL_ERR: [chars] Explanation An internal error has occurred. Recommended Action If this message recurs, copy the message exactly as it appears on the console


PIMSN Messages This section contains Protocol Independent Multicast (PIM) Snooping (PIMSN) messages.

PIMSN-6 Error Message %PIMSN-6-IGMPSN_GLOBAL: PIM Snooping global runtime mode [chars] due to IGMP Snooping [chars] Explanation PIM snooping requires that IGMP snooping be enabled. When IGMP snooping is

disabled, PIM snooping also becomes disabled. PIM snooping is reenabled when IGMP snooping is reenabled. Recommended Action No action is required. The system is working properly. We recommend that you

leave IGMP snooping enabled.


1139

PKI Messages

Error Message %PIMSN-6-IGMPSN_VLAN: PIM Snooping runtime mode on vlan [dec] [chars] due to IGMP Snooping [chars] Explanation PIM snooping requires that IGMP snooping be enabled. When IGMP snooping is

disabled, PIM snooping also becomes disabled. PIM snooping is reenabled when IGMP snooping is reenabled. Recommended Action No action is required. The system is working properly. We recommend that you

leave IGMP snooping enabled.

PKI Messages This section contains public key infrastructure (PKI) feature messages.

PKI-3 Error Message %PKI-3-CERTIFICATE_INVALID: Certificate chain validation has failed. Explanation The certificate is not valid. Recommended Action Verify that the system clock is set correctly.

Error Message %PKI-3-CERTIFICATE_INVALID_EXPIRED: Certificate chain validation has failed. The certificate (SN: [chars]) has expired. Validity period ended on [chars] Explanation The certificate validity period indicates that this certificate has expired. Recommended Action Verify that the system clock is set correctly.

Error Message %PKI-3-CERTIFICATE_INVALID_NOT_YET_VALID: Certificate chain validation has failed. The certificate (SN: [chars]) is not yet valid Validity period starts on [chars] Explanation The certificate validity period indicates that this certificate is not yet valid Recommended Action Verify that the system clock is set correctly.

Error Message %PKI-3-CERTIFICATE_INVALID_UNAUTHORIZED: Certificate chain validation has failed. Unauthorized Explanation The certificate is valid but not authorized Recommended Action Verify that the system clock is set correctly.


1140

PKI Messages

Error Message %PKI-3-CERTIFICATE_REVOKED: Certificate chain validation has failed. The certificate (SN: [chars]) is revoked Explanation The certificate has been revoked by the CA administrator. Recommended Action Contact the CA administrator to check the status of the certificate.

Error Message %PKI-3-CERTRETFAIL: Certificate enrollment failed. Explanation A certificate enrollment transaction failed due to internal error. Recommended Action Contact the CE or copy the message exactly as it appears on the console or in

the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %PKI-3-CS_CRIT_STORAGE: Critical certificate storage, [chars], is inaccessible, server disabled. Explanation The critical certificate storage location is inaccessible, so the server is disabled. Recommended Action Make the storage location accessible or reconfigure the storage location.

Error Message %PKI-3-GETCARACERT: Failed to receive RA/CA certificates. Explanation A failure was encountered while CA or RA certificates were being parsed or processed. Recommended Action Check the status of the certificate or contact the CA administrator.

Error Message %PKI-3-INVALIDCACERT: Failed to process CA certificate. Explanation The CA certificate that was received from the CA server could not be processed. Recommended Action Enter the parser command.

Error Message %PKI-3-INVALID_INPUT: The input to the parser command is not correct Explanation The arguments supplied to the parser command are not correct. Recommended Action Reenter the command.


1141

PKI Messages

Error Message %PKI-3-POLLCACERT: Polling CA certificate ..... Explanation The CA certificate is being polled. Recommended Action Check to see if the CA server or the LDAP server is on line.

Error Message %PKI-3-POLLRACERT: Polling RA certificate ..... Explanation The RA certificate is being polled. Recommended Action Check to see if the CA server or the LDAP server is on line.

Error Message %PKI-3-POLLROUTERCERT: Polling Router certificate ..... Explanation The router certificate is being polled. Recommended Action Check to see if the CA server or the LDAP server is on line.


1142

PKI Messages

Error Message %PKI-3-QUERYCACERT: Failed to query CA certificate. Explanation A CA certificate from the CA server could not be queried. Explanation Enter the parser command.

Error Message %PKI-3-QUERY_KEY: Querying key pair failed. Explanation A public key or private key query attempt using the subject name has failed. Explanation Resubmit the enrollment request. Check the subject name.

Error Message %PKI-3-SOCKETSELECT: Failed to select the socket. Explanation The socket could not be selected. Explanation Check for a TCP of socket debugging message to attempt to investigate the problem.

Error Message %PKI-3-SOCKETSEND: Failed to send out message to CA server. Explanation A message could not be sent to the CA server. This failure is caused by a problem with

the HTTP transaction. Explanation Check the HTTP connection to the CA server.

PKI-4 Error Message %PKI-4-CRL_LDAP_QUERY: The CRL could not be retrieved from the specified LDAP server Explanation The certificate revocation list (CRL) is located on an LDAP server but the LDAP query

failed. Recommended Action Check that the LDAP server is reachable and online. Verify that the CRL is at

the specified location.

Error Message %PKI-4-CS_PUBLISH_STORAGE: Publish certificate storage, [chars], is inaccessible. Explanation The publish certificate storage location is inaccessible. Recommended Action Make the storage location accessible or reconfigure the storage location.


1143

PKI Messages

Error Message %PKI-4-NOAUTOSAVE: Configuration was modified. Issue "write memory" to save new certificate Explanation Auto-enroll has obtained a new router key pair and certificate. However, the running

configuration was previously modified. Recommended Action Enter the write memory command to save the new certificate(s) and key(s).

Error Message %PKI-4-NOCONFIGAUTOSAVE: Configuration was modified. Issue a "write memory" to save new IOS PKI configuration Explanation The PKI process has generated a new PKI configuration, but the running configuration was previously modified. Recommended Action Enter a write memory command to save the new PKI configuration.

Error Message %PKI-4-NOSHADOWAUTOSAVE: Configuration was modified. Issue "write memory" to save new IOS CA certificate Explanation Cisco IOS CA Rollover has generated a shadow CA key pair and certificate. However,

the running configuration was previously modified. Recommended Action Enter the write memory command to save the new certificates and keys.

PKI-6 Error Message %PKI-6-AUTOENROLL_KEY_LOCKED: Auto-enroll failed - RSA keypair is locked Explanation Auto-enroll could not generate a new RSA key pair because the existing RSA key pair

is locked. Recommended Action Auto-enroll will retry the enrollment request. Make sure that the existing RSA key pair is unlocked before the next retry.

Error Message %PKI-6-AUTOSAVE: Running configuration saved to NVRAM Explanation Auto-enroll has obtained a new router key pair and certificate, and has done an

automatic write to memory to save them. Recommended Action This is an informational message only. No action is required.

Error Message %PKI-6-CERTFAIL: Certificate enrollment failed. Explanation A fatal error was encountered during a certificate enrollment operation. Recommended Action Contact the CA administrator.


1144

PKI Messages

Error Message %PKI-6-CERT_FATAL_ERR: [chars] Explanation A fatal error was encountered during a certificate enrollment operation. The operation

has been terminated. Recommended Action Contact the CA administrator.

Error Message %PKI-6-CERTIFSRECV: Could not receive router’s Certificate from file system. Explanation The certificate for the router could not be received from the file system. Recommended Action Verify the enrollment URL and that the router is able to read from the file

system.

Error Message %PKI-6-CERTIFSSEND: Could not send Certificate enrollment request to file system. Explanation The certificate enrollment request could not be sent to the file system. Recommended Action Verify the enrollment URL and that the router is able to write to the file system.

Error Message %PKI-6-CERTPENDING: Enter manual authentication ... Explanation The CA server is attempting to manually authenticate the router. Recommended Action Follow the manual authentication procedure.

Error Message %PKI-6-CERTREJECT: Certificate enrollment request was rejected by Certificate Authority Explanation A previous certificate enrollment request was received by the Certificate Authority. The CA has rejected the enrollment request. Recommended Action Contact the Certificate Authority administrator.

Error Message %PKI-6-CERTRET: Certificate received from Certificate Authority Explanation A previous certificate enrollment request was received by the Certificate Authority. The CA has issued the certificate and sent back a copy Recommended Action No action is required.

Error Message %PKI-6-CONFIGAUTOSAVE: Running configuration saved to NVRAM Explanation The PKI process has generated and saved to memory a new PKI configuration. Recommended Action No action is required.


1145

PKI Messages

Error Message %PKI-6-CS_DELETE: Certificate Server is deleted. Explanation The certificate server is deleted. Recommended Action No action is required. This is an informational message.

Error Message %PKI-6-CS_DELETE_TP_KEY: Trustpoint and key deleted. Explanation The trustpoint and key used by the certificate server are deleted. Recommended Action No action is required. This is an informational message.

Error Message %PKI-6-CS_GRANT_AUTO: All enrollment requests will be automatically granted. Explanation All enrollment requests will be automatically granted. Recommended Action No action is required. This is an informational message.

Error Message %PKI-6-CS_GRANT_AUTO_CACERT: All rollover subordinate CA cert requests will be automatically granted. Explanation All rollover subordinate CA certificate requests will be automatically granted. Recommended Action No action is required. This is an informational message.

Error Message %PKI-6-CS_GRANT_AUTO_RA: Enrollment requests coming from known RAs will be automatically granted. Explanation Enrollment requests coming from known RAs will be automatically granted. Recommended Action No action is required. This is an informational message.

Error Message %PKI-6-CS_GRANT_AUTO_RACERT: All rollover RA cert requests will be automatically granted. Explanation All rollover RA certificate requests will be automatically granted. Recommended Action No action is required. This is an informational message.

Error Message %PKI-6-CS_REJECT_AUTO: All enrollment requests will be automatically rejected. Explanation All enrollment requests will be automatically rejected. Recommended Action No action is required. This is an informational message.


1146

PLATFORM Messages

Error Message %PKI-6-PKCS12EXPORT_FAIL: PKCS #12 Export Failed. Explanation An attempt to generate and export information conforming to the PKCS #12 format has

failed. Recommended Action This is an informational message only. No action is required.

Error Message %PKI-6-PKCS12EXPORT_SUCCESS: PKCS #12 Successfully Exported. Explanation Information conforming to the PKCS #12 format has been generated and successfully

exported. Recommended Action This is an informational message only. No action is required.

Error Message %PKI-6-PKCS12IMPORT_FAIL: PKCS #12 Import Failed. Explanation An attempt to import information conforming to the PKCS #12 format has failed. Recommended Action This is an informational message only. No action is required.

Error Message %PKI-6-PKCS12IMPORT_SUCCESS: PKCS #12 Successfully Imported. Explanation Information conforming to the PKCS #12 format has been successfully imported. Recommended Action This is an informational message only. No action is required.

Error Message %PKI-6-SHADOWAUTOSAVE: Running configuration saved to NVRAM Explanation Cisco IOS CA Rollover has generated a shadow CA key pair and certificate, and has

executed an automatic write memory command to save them. Recommended Action No action is required. This is an informational message.

PLATFORM Messages This section contains platform-specific messages.

PLATFORM-1 Error Message %PLATFORM-1-CRASHED: [chars] Explanation The system is attempting to display the crash message from the previous crash. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1147

PLATFORM Messages


PLATFORM-3 Error Message %PLATFORM-3-FATALCINNAMON: The FPGA controller has received a fatal interrupt, reg=[hex], mask=[hex], config=[hex] - [chars] Explanation The FPGA controller has received a fatal interrupt. This may be a hardware or a

software problem. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PLATFORM-3-NO_HARDWARE_RESOURCES: Not enough hardware resources. Shutting down [chars] Explanation There are too many VLANs and routed ports on the system. Recommended Action Reduce the total number of VLANs and routed ports to be fewer than 1023. If you require this configuration and connectivity to be maintained across system reboots, save the configuration to NVRAM.

Error Message %PLATFORM-3-PW_REC_HRPC_BAD_LENGTH: Received incompatible length (=[dec]) in set-password-recovery HRPC message from box [dec]. Explanation The system has received an incompatible length parameter in a set-password-recovery

HRPC message. This condition could be caused by a stack that is operating with incompatible software versions on different stack members. Recommended Action Ensure that all stack members are running compatible software images. If the

problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support


1148

PLATFORM Messages


Error Message %PLATFORM-3-PW_REC_HRPC_NOT_ON_MASTER: Set-password-recovery HRPC msg from box [dec] received on master. Explanation The active stack has received a set-password-recovery HRPC message. These types of

messages should only be received on standby systems. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PLATFORM-3-PW_REC_HRPC_ONLY_ON_MASTER: Get-password-recovery HRPC msg from box [dec] received on slave. Explanation A standby switch has received a get-password-recovery HRPC message. These types of

messages should only be received by the active stack. Recommended Action Copy the message exactly as it appears on the console or in the system log.


PLATFORM-4 Error Message %PLATFORM-4-FPGA_MISMATCH: FPGA image in slot [dec] (name = [chars], hardware version = [dec].[dec], current fpga version = [chars]) does not match the FPGA image in Cisco IOS software (version [dec].[dec]). Approximate time to update the FPGA image is [dec] minutes. Explanation The version of the FPGA image on the specified card differs from the Cisco IOS

software bundled FPGA image version. Recommended Action Update the FPGA image by entering the upgrade fpga all command.


1149

PM Messages

Error Message %PLATFORM-4-FPGAUPD_RELOAD_SKIP: After the FPGA update, the card in slot [dec] was not reloaded. The card should be reloaded for the new FPGA image to take effect. Explanation The FPGA image on the specified card is updated. The new FPGA image will not be

operational until the card is reloaded. The FPGA image upgrade will take effect after the next reload of the card. The card was not reloaded due to negative user response to the reload prompt. Recommended Action Reload the card in the specified slot. If the card is a processor, reload the router.

Error Message %PLATFORM-4-FPGA_VER_INVALID: FPGA version information for the hardware in slot [dec] (fpga [dec]) has not been cached. Explanation An attempt to read the current FPGA version from the cache was unsuccessful.

Normally, the FPGA version on the RP and line cards is read from the flash memory device and is cached during the initialization of the card. However, the FPGA image version information for the card in the specified slot has not been cached. This problem is caused by a software error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


PM Messages This section contains port manager (PM) messages.

PM-1 Error Message %PM-1-INCONSISTENT_PORT_STATE: Inconsistent HW/SW port state for [chars]. Please shut/no shut the interface Explanation The hardware and software port state has become inconsistent. [chars] is the interface. Recommended Action No action is necessary. This message is informational only.


1150

PM Messages

PM-3 Error Message %PM-3-ERR_INCOMP_PORT: is set to inactive because is a trunk port Explanation An isolated or community VLAN port or private host port cannot be configured on the

same COIL application-specific integrated circuit (ASIC) when another port is either a trunk, a SPAN destination, or a promiscuous PVLAN port, or if a port is configured as dynamic desirable mode (the default mode on some switches). Recommended Action To reactivate the ports, remove the isolated or community VLAN port

configuration and enter the shutdown command followed by the no shutdown command. Configure the incompatible port on a different ASIC on the module or on a different module. Refer to the module documentation to determine which ports share an ASIC. If ports are configured (manually or by default) as dynamic desirable mode, configure the ports as access mode using the switchport mode access command.

PM-4 Error Message %PM-4-LIMITS: The number of vlan-port instances on [chars] exceeded the recommended limit of [dec]. Explanation The total number of individual VLAN ports on the module or switch,has exceeded the

recommended limit. VLANs can be counted more than once; if VLAN 1 is carried on ten interfaces, it will count as ten VLAN ports. On some platforms, bundling is also ignored for purposes of this count; if eight interfaces on the same module are in one bundle, and the port channel is carrying VLAN 1, it will count as eight VLAN ports. [chars] is the module name (for example, switch or the module number), and [dec] is the recommended limit. In some releases, such as Cisco IOS Release 12.2(33)SXI, the actual limit may be greater than the limit reported in this message. See the Cisco IOS release notes for the latest recommended limits. Recommended Action Reduce the number of trunks and VLANs configured in the module or switch

as recommended in [dec]. Enter the show interfaces trunk privileged EXEC command to see the total number of trunks and VLANs.

Error Message %PM-4-MPLS_MTU_EC_CFG: MPLS MTU size [dec] is not supported by one or more ports in channel [chars]. Explanation The MPLS MTU size that was configured on the Ethernet channel is larger than the

maximum MTU size that can be supported by one or more ports in this channel. Large packets might be dropped. Recommended Action Reduce the MPLS MTU size, or remove these ports from the channel before

increasing the MPLS MTU size.


1151

PM Messages

Error Message %PM-4-MPLS_MTU_PORT_CFG: MPLS MTU size [dec] is not supported by port [chars]. Explanation The MPLS MTU size that was configured on the port is larger than the maximum MTU

size that can be supported by this port. Large packets might be dropped. Recommended Action Reduce the MPLS MTU size.

Error Message %PM-4-NOSB: No PM subblock found for interface [chars] Explanation This syslog, along with T/B, is logged for all type of interfaces where PM subblock is

absent.The interface types include WAN, loopback and tunnel, which do not have associated PM subblock as per the design.This message helps the PM group to identify the offending application. This message indicates that PM module encounters unusual conditions for diagnose purpose. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %PM-4-NOSB: No PM subblock found for interface [WAN|loopback|tunnel]: ios-base : (PID= [number], TID=[number]):[traceback] Explanation This message indicates that the port manager module encountered unusual conditions.

It is logged for interfaces where the port manager subblock is absent. Interface types include WAN, loopback and tunnel which do not have associated port manager subblock by design. The traceback helps the Cisco port manager development group to trace the problematic code path. Recommended Action No action is required.

Error Message %PM-4-PORT_BOUNCED: Port [chars] was bounced by [chars]. Explanation The PM needed to perform a reactivation of a port in the link-down state during a

switchover. A port is only reactivated when the port data structures lack consistency between the active and redundant supervisor engines. Active ports in the link-down state were returned to the link-up state by the reactivation event. Recommended Action No action is required.

Error Message %PM-4-PVLAN_TYPE_CFG_ERR: Failed to set VLAN [dec] to a [chars] VLAN Explanation The platform failed to set the type for the private VLAN. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1152

PM Messages


Error Message %PM-4-SVI_ADD_CORRESPONDING_L2_VLAN: Vlan [dec] must be added to L2 database in order to be used, do from config mode. Explanation When a switch virtual interface (SVI) is created, the corresponding Layer 2 VLAN is

not automatically created in the Layer 2 database. Recommended Action Create a Layer 2 VLAN before the switch virtual interface (SVI) is created.

Error Message %PM-4-TUNNEL_INT_VLAN_NOTAVAIL: Internal VLAN allocation failed for tunnel interface [chars]. Explanation Because the maximum internal VLAN usage has been reached, VLAN allocation for the

tunnel interface has failed. The tunnel interface could not be created. Recommended Action Delete some extended range VLANs created by users or remove some features that require internal VLAN allocation (for example, routed ports).

PM-6 Error Message %PM-6-ACTIVE: Interface [chars] is now active because [chars] Explanation The port manager has detected an interface that was down as up for the VLAN, causing

the port to be in the active state. Recommended Action No action is required.


1153

PMB Messages

PMB Messages This section contains power management bus (PMB) messages.

PMB-4 Error Message %PMB-4-CANTPWROFF: Attempts to power down slot [dec] failed, card will be disabled. Explanation The system could not power down the module in slot [dec], possibly due to a hardware

failure. Recommended Action Copy the message exactly as it appears on the console or in the system log.


PM_ISSU Messages This section contains port manager (PM) in-service software upgrade (ISSU) messages.

PM_ISSU-3 Error Message %PM_ISSU-3-BUFFER: Port Manager ISSU client failed to get buffer for message, error %d Explanation The port manager ISSU client was unable to get buffer space for building a negotiation




1154

PM_ISSU Messages

Error Message %PM_ISSU-3-CAPABILITY: Port Manager ISSU client %s Explanation The port manager ISSU client detected an error during capability negotiation. As a

result, there is a mismatch in the client capability between the active and standby unit. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PM_ISSU-3-INIT: Port Manager ISSU client initialization failed at %s, error %s Explanation The port manager ISSU client could not be initialized. This condition will cause a



Error Message %PM_ISSU-3-MSG_NOT_OK: Port Manager ISSU client message %d is not compatible Explanation The port manager ISSU client received an incompatible message from the peer unit. The message cannot be processed by this unit. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1155

PM_ISSU Messages

Error Message %PM_ISSU-3-MSG_SIZE: Port Manager ISSU client failed to get the message size for message %d Explanation The port manager ISSU client was unable to calculate the message size for the message

specified. The PM ISSU client will be unable to send the message to the standby unit. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PM_ISSU-3-POLICY: Port Manager ISSU client message type %d is %s Explanation The port manager ISSU client received a message type that it does not support. A policy

is applied to make the session compatible. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PM_ISSU-3-SEND_FAILED: Port Manager ISSU client failed to send a negotiation message, error %d Explanation The port manager ISSU client could not send a session negotiation message to the peer.




1156

PM_ISSU Messages

Error Message %PM_ISSU-3-SESSION: Port Manager ISSU client %s Explanation The port manager ISSU client detected an error during a session negotiation with the



Error Message %PM_ISSU-3-SESSION_UNREGISTRY: Port Manager ISSU client failed to unregister session information. Error: %d (%s) Explanation The port manager ISSU client was unable to unregister session information. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PM_ISSU-3-TRANSFORM: Port Manager ISSU client %s transform failed, error %s Explanation The port manager ISSU client could not transform the message. If the transmit

transformation failed, the checkpoint message cannot be sent to the standby unit. If the receive transformation failed, the checkpoint message cannot be applied on the standby unit. In either case, the port manager state will not be identical with the active unit. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1157

PM_PVLAN_ISSU Messages


PM_PVLAN_ISSU Messages This section contains port manager (PM) private VLAN (PVLAN) in-service software upgrade (ISSU) messages.

PM_PVLAN_ISSU-3 Error Message %PM_PVLAN_ISSU-3-BUFFER: Private Vlan ISSU client failed to get buffer for message, error %d Explanation The private VLAN ISSU client was unable to get a buffer for building a negotiation

message. As a result, it cannot send the negotiation message to the standby unit and the standby unit cannot be brought up. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PM_PVLAN_ISSU-3-CAPABILITY: Private Vlan ISSU client %s Explanation The private VLAN ISSU client detected an error during capability negotiation. As a




1158


Error Message %PM_PVLAN_ISSU-3-INIT: pm_pvlan Client Name ISSU client initialization failed at %s, error %s Explanation The private VLAN ISSU client could not be initialized. This condition will cause a



Error Message %PM_PVLAN_ISSU-3-MSG_NOT_OK: Private Vlan ISSU client message %d is not compatible Explanation The private VLAN ISSU client received an incompatible message from the peer unit.

The message cannot be processed by this unit. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PM_PVLAN_ISSU-3-MSG_SIZE: Private Vlan ISSU client failed to get the message size for message %d Explanation The private VLAN ISSU client was unable to calculate the message size for the message

specified. The client will be unable to send the message to the standby unit. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1159


Error Message %PM_PVLAN_ISSU-3-POLICY: Private Vlan ISSU client message type %d is %s Explanation The private VLAN ISSU client received a message type that it does not support. A

policy is applied to make the session compatible. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PM_PVLAN_ISSU-3-SEND_FAILED: Private Vlan ISSU client failed to send a negotiation message, error %d Explanation The private VLAN ISSU client could not send a session negotiation message to the peer.



Error Message %PM_PVLAN_ISSU-3-SESSION: Private Vlan ISSU client %s Explanation The private VLAN ISSU client detected an error during a session negotiation with the




1160

PM_SCP Messages

Error Message %PM_PVLAN_ISSU-3-TRANSFORM: Private Vlan ISSU client %s transform failed, error %s Explanation The private VLAN ISSU client could not transform the message. If the transmit

transformation failed, the checkpoint message cannot be sent to the standby unit. If the receive transformation failed, the checkpoint message cannot be applied on the standby unit. In either case, the private VLAN ISSU state will not be identical with the active unit. Recommended Action Copy the message exactly as it appears on the console or in the system log.


PM_SCP Messages This section contains port manager Switch-Module Configuration Protocol (PM_SCP) messages.

PM_SCP-1 Error Message %PM_SCP-1-LCP_FW_ERR_POWERDOWN: Module [dec] will be powered down due to firmware error: [chars] Explanation A nonrecoverable error was detected by the switching module firmware and the

switching module will be powered down to keep the system functioning. [dec] is the module number and [chars] explains that the system will be powered down. Recommended Action No action is required.

PM_SCP-2 Error Message %PM_SCP-2-LCP_FW_ERR_INFORM: Module [dec] is experiencing the following error: [chars] Explanation The linecard is reporting an error condition, where [dec] is the module number, and

[chars] is the error. This condition is usually caused by an improperly seated linecard or a hardware failure. If the error message is seen on all of the linecards, the cause is an improperly seated module. Recommended Action Reseat and reset the linecard or the module. If the error message persists after the module is reset, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying


1161

PM_SCP Messages


Error Message %PM_SCP-2-SPURIOUS_INTERRUPT: Module [dec] detects [dec] spurious interrupts from asic [chars]. Explanation An error condition was detected by the active supervisor engine firmware. If

error-detection crash-action is configured, the active supervisor engine will switch over to the standby supervisor engine in a redundant setup. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PM_SCP-2-RESET: Module [dec] is resetting - Due to Packet Buffer Error. Explanation An error condition was detected by the line card firmware and the supervisor engine has initiated a reset procedure for the line card. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1162

PM_SCP Messages

Error Message %PM_SCP-2-SHUTDOWN: Module [dec] is shutting down - Due to Packet Buffer Error. Explanation An error condition was detected by the line card firmware and the supervisor engine has

initiated a shutdown procedure for the line card. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PM_SCP-2-STDBY_NOT_SWTCH_OVER: Standby is not ready for switchover for Packet Buffer Error. Active-Sup (Module [dec]) is going down... Explanation An error condition was detected by the active supervisor engine firmware and the

standby supervisor engine is not ready for switchover, so the active supervisor engine is going down. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PM_SCP-2-STDBY_RELOAD: Standby (Module [dec]) is reloading due to Packet Buffer Error... Explanation An error condition was detected by the supervisor engine firmware and the standby

supervisor engine is reloading now. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1163

PM_SCP Messages

Error Message %PM_SCP-2-STDBY_SWTCH_OVER: Supervisor (Module [dec]) is preparing for switch-over - Due to Packet Buffer Error. Explanation An error condition was detected by the supervisor engine firmware and has initiated the switchover action. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PM_SCP-2-TRANSCEIVER_BAD_HW: Module [dec] will be power disabled for safety reasons because a defective transceiver is inserted at [chars]. Explanation An inappropriate transceiver is inserted at the specified interface. This transceiver

should not be used in this system. Recommended Action Remove the specified transceiver and enable power to the module. If this

transceiver was purchased from Cisco, contact Cisco TAC to get the transceiver replaced.

Error Message %PM_SCP-2-TRANSCEIVER_INCOMPATIBLE: Transceiver inserted in [chars] port [dec]/[dec] is not compatible with its interface (transceiver speed is [chars], interface speed is [chars]) Explanation An incompatible transceiver was inserted in the specified module. This transceiver

should not be used with this module. Recommended Action Replace the specified transceiver with another transceiver that is compatible

with this module.

PM_SCP-3 Error Message %PM_SCP-3-LCP_FW_ABLC: Late collision message from module [dec], port:0[dec] Explanation The line card firmware has detected abnormal collisions in port traffic. Recommended Action This is usually a temporary condition. Check for any mismatch in the Duplex

or Speed setting with the remote device. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at


1164

PM_SCP Messages


Error Message %PM_SCP-3-TRANSCEIVER_BAD_EEPROM: Integrity check on transceiver in [chars] port [dec]/[dec] failed: bad key Explanation The transceiver has an incorrectly programmed EEPROM. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PM_SCP-3-TRANSCEIVER_DUPLICATE: Transceiver in [chars] port [dec]/[dec] and in [chars] port [dec]/[dec] have duplicate serial numbers Explanation The transceiver was identified as a Cisco transceiver, but its vendor ID and serial

number match that of another transceiver on the system. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PM_SCP-2-TRANSCEIVER_INCOMPATIBLE: Transceiver inserted in [chars] port [dec]/[dec] is not compatible with its interface (transceiver speed is [chars], interface speed is [chars]) Explanation An incompatible transceiver is inserted in the specified module. This transceiver should

not be used with this module. Recommended Action Replace the specified transceiver with another transceiver that is compatible

with this module.


1165

PM_SCP Messages

PM_SCP-4 Error Message %PM_SCP-4-FPOE_INFO: An unsupported distributed fabric card has been detected Explanation Fabric-capable modules are not supported in this system. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PM_SCP-4-LCP_FW_ABLC: Late collision message from module [dec], port:0[dec] Explanation The line card firmware has detected abnormal collisions in port traffic. This message is

typically an indication of a speed or duplex mismatch, possibly caused by a misconfiguration. Recommended Action This is usually a temporary situation. Check the speed and duplex for the port and make sure that it is correct. For correct operation, both sides of a link should be auto-negotiated or both sides should be manually configured for speed and duplex. Do not configure auto-negotiation on one side and manual setting on the other, because the auto-negotiating side might lock at the wrong duplex setting.

Error Message %PM_SCP-4-TRANSCEIVER_UNSUPP_MODULE: Interface [chars] does not support receive-only transceivers Explanation A receive-only transceiver has been inserted into a module that does not support it. Recommended Action Use the receive-only transceiver with a supported module. Refer to the

documentation for modules that support receive-only transceivers.

Error Message %PM_SCP-4-UNSUPPORTED: Interface [chars] does not support receive-only transceivers Explanation A receive-only transceiver has been inserted into a slot that does not support it. Recommended Action Use the receive-only transceiver with a supported module.


1166

POLARIS Messages

PM_SCP-6 Error Message %PM_SCP-6-LCP_FW_ERR_INFORM: Module [dec] is experiencing the following error: [chars] Explanation The module is reporting an error condition, where [dec] is the module number, and

[chars] is the error. This condition is usually caused by an improperly seated linecard or a hardware failure. If the error message is seen on all of the linecards, the cause is an improperly seated module. Recommended Action Reseat and reset the linecard or the module. If the error message persists after the module is reset, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

POLARIS Messages This section contains Layer 3 CEF engine (POLARIS) messages.

POLARIS-4 Error Message %POLARIS-4-ERR_INTRPT: Interrupt [chars] occurring in Polaris Layer 3 ASIC Explanation An error occurred in the Layer 3 forwarding ASIC. The error description is shown by

[chars]. Recommended Action These errors are transient conditions caused by traffic passing through the

ASIC, and may appear occasionally under normal conditions. If this message recurs, enter the show earl status command on the consoles of the switch supervisor engine and any DFC-enabled modules. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


1167

POLICY_API Messages

POLICY_API Messages This section contains policy API messages.

POLICY_API-4 Error Message %POLICY_API-4-POLICYDYNCLR: Dynamic policy on intf:[chars] cleared. Static policy in use. Explanation A dynamic policy was attempting to override the static policy. The dynamic policy has

been cleared, the static policy is now in effect. Recommended Action No action is required.

Error Message %POLICY_API-4-POLICYOVERIDE: Dynamic policy overriding static on intf:[chars] Explanation Both a static policy and a dynamic policy are configured on the interface. The dynamic

policy will override the static policy. Recommended Action If preferred, remove the static policy configuration.

Error Message %POLICY_API-4-POLICYSTATICCLR: Static policy on intf:[chars] cleared. Dynamic policy in use. Explanation A dynamic policy has overridden the static policy. The static policy has been cleared. Recommended Action No action is required.

POLICY_MANAGER Messages This section contains Policy Manager messages.

POLICY_MANAGER-2 Error Message %POLICY_MANAGER-2-INIT_FAILURE: Init failure: [chars] Explanation A problem occurred during the initialization of the policy manager during system

initialization. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1168

POLICY_MANAGER Messages


Error Message %POLICY_MANAGER-2-NO_FREE_EVENT_BUFFERS: Event pool depleted: [chars] Explanation The event pool has been depleted. There are no free buffers to process the event. Recommended Action Copy the message exactly as it appears on the console or in the system log.


POLICY_MANAGER-3 Error Message %POLICY_MANAGER-3-INVALID_ACTION: Invalid action Explanation An invalid action was performed by the policy manager. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %POLICY_MANAGER-3-INVALID_PARAMETERS: A call to Policy Manager is made with invalid parameters Explanation A call to the policy manager was made with one or more invalid parameters. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1169

POLICY_MANAGER Messages


Error Message %POLICY_MANAGER-3-INVALID_SEVERITY: Invalid event severity [hex] Explanation The event that was received by the policy manager contained an invalid severity and was

not processed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %POLICY_MANAGER-3-NO_FREE_POLICY_IDS: No more Policy IDs available Explanation There are no more policy IDs that can be allocated. Policy manager policies can no

longer be created. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %POLICY_MANAGER-3-NULL_ACTION_ROUTINE: NULL action routine invoked Explanation The policy manager attempted to invoke an action that was of a null value. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1170

PORT_SECURITY Messages

Error Message %POLICY_MANAGER-3-PRE_INIT_CALL: Policy Manager routine called prior to initialization Explanation The policy manager component was called prior to its initialization. This action could

result in vital information being lost. Recommended Action Copy the message exactly as it appears on the console or in the system log.


PORT_SECURITY Messages This section contains port security messages.

PORT_SECURITY-2 Error Message %PORT_SECURITY-2-INELIGIBLE: Port security configuration on [chars] is being made inactive since the port is now not eligible for port security as [chars]. Explanation A port had port security configuration on it, but the port now has a configuration not

supported with port security. Because the port is now not eligible for port security, the port security configuration on it is being made inactive. Recommended Action Check the port’s configuration and remove the offending configuration that is

not compatible with port security.

Error Message %PORT_SECURITY-2-PSECURE_VIOLATION: Security violation occurred, caused by MAC address [enet] on port [chars]. Explanation An unauthorized device attempted to connect on a secure port. The MAC address of the

unauthorized device and the secure port are specified in the message. Recommended Action Determine the device that attempted to connect on the secure port. Notify your

network system administrator of this condition.


1171

PORT_SECURITY Messages

PORT_SECURITY-6 Error Message %PORT_SECURITY-6-ADDR_EXCEEDS_LIMIT: Address can not be allowed on port [chars] because of max address limits. It has been removed Explanation A routed port has changed to a switched port. The addresses stored in the previous

switched-port configuration are now causing the total secure address count to exceed the allowed limit and they have been deleted Recommended Action This is an informational message only. No action is required.

Error Message %PORT_SECURITY-6-ADDR_REMOVED: Address exists on port [chars]. It has been removed from port [chars]. Explanation A routed port has changed to a switched port. An address stored in the previous

switched-port configuration is now in conflict and has been deleted. Recommended Action This is an informational message only. No action is required.

Error Message %PORT_SECURITY-6-INVALID_SESSION: Invalid Port-Security ISSU Session ID Explanation The ISSU session ID is not valid because it has not been negotiated. Recommended Action No action is required.

Error Message %PORT_SECURITY-6-VLAN_REMOVED: VLAN(S) [chars] is/are no longer allowed on port [chars]. Their port security configuration has been removed. Explanation A configured VLAN has been excluded on a trunk port and so is being removed from

the configuration. Recommended Action This is an informational message only. No action is required.


1172

POSLC Messages

POSLC Messages This section contains Packet over SONET line card (POSLC) messages.

POSLC-3 Error Message %POSLC-3-HWERROR: [chars] Explanation The Optical Services Module has encountered a hardware error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %POSLC-3-PROCESS_CREATEFAIL: [chars] Explanation The PoS line card could not create a process required for its operation. This condition

might be caused by a resource being unavailable. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %POSLC-3-PROCESS_TIMEREVENT: [chars] Explanation An unexpected process timer event occurred in the Optical Services Module. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1173

POT1E1 Messages


Error Message %POSLC-3-UNEXPECTED_PROCESSEVENT: [chars] Explanation An unexpected process event occurred in the Optical Services Module. Recommended Action Copy the message exactly as it appears on the console or in the system log.


POT1E1 Messages This section contains Versatile Interface Processor (VIP) Packet over T1 and E1 (POT1E1) port adapter messages.

POT1E1-2 Error Message %POT1E1-2-NOACCPTR: VC=[dec] [chars] Explanation The POT1E1 port adapter could not increment the pointer count. Recommended Action Copy the error message exactly as it appears on the console or in the system

log. Enter the show tech-support and show controllers vip slot-number tech-support commands, with slot-number being the slot number where the POT1E1 port adapter resides. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support and show controllers vip slot-number tech-support commands, with slot-number being the slot number where the POT1E1 port adapter resides, and your pertinent troubleshooting logs.


1174

POT1E1 Messages

Error Message %POT1E1-2-NOINC: [chars] Explanation The POT1E1 port adapter encountered a null access pointer while it was incrementing

the pointer count. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %POT1E1-2-QTAIL: Qhead=[hex] particle_count=[dec] size=[dec] Explanation The POT1E1 port adapter encountered a null queue heading. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %POT1E1-2-TXBADVC: [chars], vc [dec] Explanation The POT1E1 port adapter encountered a null queue heading. Recommended Action Copy the error message exactly as it appears on the console or in the system

log. Enter the show tech-support and show controllers vip slot-number tech-support commands, with slot-number being the slot number where the POT1E1 port adapter resides. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support


1175

PPP Messages

representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support and show controllers vip slot-number tech-support commands, with slot-number being the slot number where the POT1E1 port adapter resides, and your pertinent troubleshooting logs.

POT1E1-3 Error Message %POT1E1-3-FREEDMFATAL: Bay [dec]: freedm reset, command-status register [hex] Explanation The POT1E1 port adapter has experienced a fatal problem related to the Frame Engine

and Data Link Manager (FREEDM) ASIC. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %POT1E1-3-MBOXSEND: Bay [dec]: fail sending mbox msg [dec] Explanation POT1E1 mailbox failed send Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

PPP Messages This section contains Point-to-Point Protocol (PPP) messages.

PPP-3 Error Message %PPP-3-ISSU_ERR: [chars] Explanation An error occurred during an ISSU versioning operation. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1176

PQ3 Messages


PQ3 Messages This section contains Ethernet Phy messages.

PQ3_FE Error Message %PQ3_FE-1-INITFAILP: PQ3/FE([dec]/[dec]), Init failed at [chars] Explanation The FE could not allocate an I/O buffer pool. Recommended Action Clear the interface. If the message recurs, call your technical support


Error Message %PQ3_FE-1-MACADDRFAIL: PQ3/FE([dec]/[dec]), Unable to set the Mac-address for the interface Explanation The FEC could not set the mac address of the interface. Recommended Action Clear the interface. If the message recurs, call your

technical support representative for assistance.

Error Message %PQ3_FE-1-SHOWFAIL: PQ3/FE([dec]/[dec]), Memory error at [chars] Explanation The FEC could not allocate memory to display controller. Recommended Action Clear the interface. If the message recurs, call your technical support


Error Message %PQ3_FE-2-NOISL: Interface [chars] does not support ISL Explanation The interface cannot be configured as an ISL trunk. Recommended Action Check the configuration.

Error Message %PQ3_FE-3-OVERFLO: PQ3/FE([dec]/[dec]), Receive overflow Explanation While receiving a frame, the controller chip’s local buffer transmitted insufficient data because data could not be transferred to DRAM fast enough to keep pace with its input rate. Normally, such a problem is temporary, depending on transient peak loads within the system. Recommended Action The system should recover. No action is required.


1177

PQ3 Messages

Error Message %PQ3_FE-3-UNDERFLO: PQ3/FE([dec]/[dec]), Transmit underflow Explanation While transmitting a frame, the controller chip’s local buffer received insufficient data because data could not be transferred to the chip fast enough to keep pace with its output rate. Normally, such a problem is temporary, depending on transient peak loads within the system. Recommended Action The system should recover. No action is required.

Error Message %PQ3_FE-4-BABBLE: PQ3/FE([dec]/[dec]), Babble error, CSR[dec]=[hex] Explanation The transmitter has been on the channel longer than the time taken to transmit the largest


Error Message %PQ3_FE-5-EXECOLL: PQ3/FE([dec]/[dec]), Excessive collision Explanation Excessive collisions occurred on the Fast Ethernet interface. Recommended Action No action is required. Recommended Action

Error Message %PQ3_FE-5-LATECOLL: PQ3/FE([dec]/[dec]), Late collision Explanation Late collisions occurred on the Fast Ethernet interface. Recommended Action If the interface is Fast Ethernet, verify that both peers are in the same duplex

mode. No action is required.

Error Message %PQ3_FE-5-LOSTCARR: PQ3/FE([dec]/[dec]), Lost carrier. Transceiver problem? Explanation The cable and/or transceiver is not connected. Recommended Action Connect the cable and/or transceiver.

PQ3_TSEC Error Message %PQ3_TSEC-1-INITFAIL: PQ3/FE([dec]), Init failed, CSR[dec]=[hex] Explanation The software failed to initialize/restart an Ethernet/Fast Ethernet interface. Recommended Action Clear the interface. If the message recurs, call your technical support



1178

PQ3 Messages

Error Message %PQ3_TSEC-1-INITFAILP: PQ3/FE([dec]), Init failed at [chars] Explanation The FEC could not allocate a I/O buffer pool. Recommended Action Clear the interface. If the message recurs, call your technical support


Error Message %PQ3_TSEC-1-MEMERR: PQ3/FE([dec]), Memory error, CSR[dec]=[hex] Explanation The interface could not access system resources for a long time. This problem may

occur under very heavy loads. Recommended Action The system should recover. No action is required. If the message recurs, call

your technical support representative for assistance.

Error Message %PQ3_TSEC-1-SHOWFAIL: PQ3/FE([dec]), Memory error at [chars] Explanation The FEC could not allocate memory to display controller. Recommended Action Clear the interface. If the message recurs, call your technical support


Error Message %PQ3_TSEC-2-NOISL: Interface [chars] does not support ISL Explanation The interface cannot be configured as an ISL trunk. Recommended Action Check the configuration.

Error Message %PQ3_TSEC-3-OVERFLO: PQ3/FE([dec]), Receive overflow Explanation While receiving a frame, the controller chip’s local buffer transmitted insufficient data because data could not be transferred to DRAM fast enough to keep pace with its input rate. Normally, such a problem is temporary, depending on transient peak loads within the system. Recommended Action The system should recover. No action is required.

Error Message %PQ3_TSEC-3-OWNERR: PQ3/FE([dec]), Buffer ownership error, pak=[hex] Explanation The software detected an error in descriptor ownership. Recommended Action Try a later version of the software. If the message recurs, call your technical

support representative for assistance.


1179

PQ3 Messages

Error Message %PQ3_TSEC-3-UNDERFLO: PQ3/FE([dec]), Transmit underflow Explanation While transmitting a frame, the controller chip’s local buffer received insufficient data because data could not be transferred to the chip fast enough to keep pace with its output rate. Normally, such a problem is temporary, depending on transient peak loads within the system. Recommended Action The system should recover. No action is required.

Error Message %PQ3_TSEC-4-BABBLE: PQ3/FE([dec]), Babble error, CSR[dec]=[hex] Explanation The transmitter has been on the channel longer than the time taken to transmit the largest


Error Message %PQ3_TSEC-5-COLL: PQ3/FE([dec]), Excessive collisions, TDR=[dec], TRC=[dec]. Explanation Ethernet/Fast Ethernet is seeing multiple collisions. This may occur under heavy loads. Recommended Action The system should recover. No action is required.

Error Message %PQ3_TSEC-5-EXCESSCOLL: PQ3/FE([dec]), Excessive collision Explanation Ethernet/Fast Ethernet is seeing multiple collisions. This may occur under heavy loads. Recommended Action The system should recover. No action is required.

Error Message %PQ3_TSEC-5-LATECOLL: PQ3/FE([dec]), Late collision Explanation Late collisions occurred on the Ethernet/Fast Ethernet interface. Recommended Action If the interface is Fast Ethernet, verify that both peers are in the same duplex


Error Message %PQ3_TSEC-5-LOSTCARR: PQ3/FE([dec]), Lost carrier. Transceiver problem? Explanation The cable is not connected to the port. Recommended Action Connect the cable to the port.


1180

PQUICC3 Messages

PQUICC3 Messages PQUICC3-1 Error Message %PQUICC3-1-BADHDXFSM: PQUICC3([dec]/[dec]), Unexpected HDX state [dec], event [dec] Explanation A bad event was detected in the state machine for half duplex transmission/reception. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %PQUICC3-1-CTSLOST: PQUICC3([dec]/[dec]), Clear to Send Lost Explanation The Clear To Send (CTS) input signal on a data terminal equipment (DTE) serial

interface became inactive while transmitting a frame. This problem is a result of a communication line failure or cable disconnection. Recommended Action Check the serial interface cable and/or communication equipment, such as the channel service unit/data service unit (CSU/DSU).

Error Message %PQUICC3-1-INITFAIL: PQUICC3([dec]/[dec]), SCC[dec] init failed Explanation The software failed to initialize/restart a 1T serial card. Recommended Action Clear the serial interface. If the message recurs, call your technical support


Error Message %PQUICC3-1-LINEFLAP: PQUICC3([dec]/[dec]), Excessive modem control changes Explanation The system received too many modem control signal interrupts. Modem control signals

are hardware handshake signals between data terminal equipment (DTE) and data communications equipment (DCE). The signals include either a data carrier detect (DCD) or a data set ready (DSR), or both DCD and DSR. Recommended Action Check the serial interface cable. The error can occur if the cable is

disconnected or has come loose and is picking up noise. If the cable appears to be connected correctly, check the equipment connected to the cable.


1181

PQUICC3 Messages

Error Message %PQUICC3-1-NOMEMORY: Unit [dec], no memory for [chars] Explanation The MPC8500/PowerQUICC CPU was unable to access the memory it needs to carry

out its functions. Here are some possible causes. – The network is large, requiring a lot of memory for routing tables, etc. – The router configuration has many features enabled, each of which requires memory. – A software error (memory leak) exists. Recommended Action Reduce system activity to ease the memory demand, or upgrade to a larger

memory configuration.

Error Message %PQUICC3-1-QMC_GLOBAL_ERROR: PQUICC3([dec]/[dec]), Global error [hex] in QMC Explanation One or more of the channels served by the QMC instance encountered transmitter

underflow or receiver overflow or the QMC interrupt table overflowed. Normally, such a problem is temporary, depending on transient peak loads within the system. Recommended Action The system should recover. No action is required.

Error Message %PQUICC3-1-TOOBIG: PQUICC3([dec]/[dec]), packet too big, packet size was [dec] bytes Explanation A packet greater than the assigned MTU of this serial interface was queued up for

transmission. Recommended Action The system should recover. No action is required. If the message recurs, it may

indicate an error related to data traffic patterns. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message %PQUICC3-1-TOOSMALL: PQUICC3([dec]/[dec]), packet was less than 2 bytes, packet size was [dec] bytes Explanation A small packet (less than 2 bytes) was queued up for transmission. The interface cannot

handle such small packets for transmission. Recommended Action The system should recover. No action is required. If the message recurs, it may

indicate a hardware error related to data traffic patterns. copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still


1182

PQUICC3 Messages

require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message %PQUICC3-1-UNDERFLO: PQUICC3([dec]/[dec]), Transmit underflow Explanation While transmitting a frame, the serial controller chip’s local buffer received insufficient data because data could not be transferred to the chip fast enough to keep pace with its output rate. Normally, such a problem is temporary, depending on transient peak loads within the system. Recommended Action The system should recover. No action is required.

Error Message %PQUICC3-1-UNEXPECTED_INTERRUPT: PQUICC3([dec]), Unexpected modem-signal interrupt Explanation The software did not expect to see a modem control signal change on this interface. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %PQUICC3-1-WRONG_SLOT: PQUICC3([dec]), BRI card in wrong slot(1) Explanation The BRI card is not supported in WIC slot 0. Recommended Action Power down, move the BRI card to the other WIC slot on the port module and

reboot.

PQUICC3-3 Error Message %PQUICC3-3-OWNERR: Unit [dec], buffer ownership error, pak = [hex] Explanation An internal software error occurred. Recommended Action Call your technical support representative to obtain a software upgrade.


1183

PRBS Messages

Error Message %PQUICC3-3-SPURIOUS_INTERRUPT: Interface card in slot [dec] generated a spurious interrupt Explanation Interface card on the router which is not supported by this image generated a spurious

interrupt that can not be handled. Recommended Action No action is required. To avoid seeing this message in the future, remove the

unsupported card or use an image that supports it.

Error Message %PQUICC3-3-UNKNOWN_SCCS: PQUICC3, Incorrect SCC number Explanation An internal software error occurred. Recommended Action Call your technical support representative to obtain a software

upgrade.

Error Message %PQUICC3-3-UNKNOWN_SCC_TX_VECTOR: PQUICC3, Unknown TX vector on port [dec] Explanation An internal software error occurred. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %PQUICC3-1-UNKNOWN_WIC: PQUICC3([dec]), WIC card has an unknown ID of [hex] Explanation The software does not recognize the type of WIC card plugged into the port module. Recommended Action Check the part number on the WIC card to verify that it is supported in the IOS

release operational on the router or contact your technical support representative.

Error Message %PQUICC3-1-UNSUPPORTED_CONFIG: Slot [dec] has an unsupported combination of ISDN WAN interface cards Explanation It is not possible to support this type of BRI card in slot 1 along with another BRI card

in slot 0. Recommended Action Remove one of the BRI cards from either slot.

PRBS Messages This section contains Manhattan Pseudo-Random Bit Sequence (PRBS) related messages.


1184

PRBS Messages

PRBS-5 Error Message %PRBS-5-DECERR: Slot:[dec],Subcard:[dec],Port:[dec] Decoding error [dec] at time [dec] sec. Explanation A software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PRBS-5-GETARGERR: process_get_arg_num error. Explanation A software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PRBS-5-LOSSLOCK: Slot:[dec],Subcard:[dec],Port:[dec] Loss of Lock at time [dec] sec. Explanation A software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1185

PROCYON Messages

Error Message %PRBS-5-PASSED: Slot:[dec],Subcard:[dec],Port:[dec] [dec] sec PRBS test passed. Explanation A PBRS test was successful. Recommended Action No action is required.

Error Message %PRBS-5-STATUSERR: Slot:[dec],Subcard:[dec],Port:[dec] at [dec] sec status error [dec], quit. Explanation A software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PRBS-5-STOP: Slot:[dec],Subcard:[dec],Port:[dec] PRBS test stop at [dec] sec. Explanation A PBRS test stopped. Recommended Action No action is required.

PROCYON Messages This section contains messages for the CPU daughter card for the Supervisor Engine 720 (PROCYON).

PROCYON-3 Error Message %PROCYON-3-CREATE_IBC_FAILED: Creation of procyon ibc idb failed Explanation The creation of an inband control interface description block for the CPU daughter card has failed. The software or the hardware is faulty. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1186

PROCYON Messages


Error Message %PROCYON-3-INIT_IBC_FAILED: Initialization of procyon ibc failed Explanation Inband control initialization has failed. The software or the hardware is faulty. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PROCYON-3-INIT_ICDM_FAILED: Initialization of icdm driver failed Explanation The ICDM driver initialization failed for the CPU daughter card inband control. The

software or the hardware is faulty. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PROCYON-3-INIT_MAC_DRIVER_FAILED: Initialization of ethernet mac driver failed Explanation The Ethernet MAC driver initialization failed for the CPU daughter card inband control.

The software or the hardware is faulty. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1187

PROCYON Messages

Error Message %PROCYON-3-MASKED_RCV_INTR: procyon_ibc_rcv_interrupt called while masked: [int] Explanation The CPU received an inband interrupt, although the inband interrupt was masked. The

software or the hardware is faulty. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PROCYON-3-NO_BUFFER_POOLS: Initialization of private buffer pools failed Explanation Private buffer pools were not created for the CPU daughter card inband control. This condition can occur during periods of extreme traffic. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PROCYON-3-NO_PARTICLE: no particle available to populate the ethernet dma ring Explanation No particle was available to populate the direct memory access of the Ethernet ring.

This condition can occur during periods of extreme traffic. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1188

PROCYON_ION_INTR Messages

Error Message %PROCYON-3-RX_ADD_BUFFER_FAILED: particle not added to the ethernet dma ring Explanation A particle was not added to the direct memory access of the Ethernet ring. The software or the hardware is faulty. Recommended Action Copy the message exactly as it appears on the console or in the system log.


PROCYON_ION_INTR Messages This section contains messages for the CPU daughter card for the Supervisor Engine 720 (PROCYON).

PROCYON_ION_INTR-3 Error Message %PROCYON_ION_INTR-3-ENABLE_INTR_REGISTER_ACCESS_FAILED: Access to interrupt registers failed Explanation A failure occurred in accessing interrupt registers. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PROCYON_ION_INTR-3-ENABLE_KERNEL_MODE_FAILED: Access to kernel mode failed Explanation A failure occurred in accessing kernel mode. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1189

PRST_IFS Messages


Error Message %PROCYON_ION_INTR-3-INTERRUPT_UNMASK_FAILED: Interrupt unmask failed: interrupt_source [dec] Explanation A failure occurred in unmasking interrupts. Recommended Action Copy the message exactly as it appears on the console or in the system log.


PRST_IFS Messages This section contains persistent media IOS file system (IFS) messages.

PRST_IFS-3 Error Message %PRST_IFS-3-FILE: persistent media IFS file error: %s Explanation An error occurred in a persistent media module (IOS file system) file. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1190

PRST_VBL Messages

Error Message %PRST_IFS-3-FILEMEM: No memory to update %s. Please free some space Explanation There is no file system memory for the system to write an updated version of the

persistent variable file. Recommended Action Free space on the file system shown in the error message as soon as possible.

You must delete existing files or squeeze the file system if the file system requires it (bootflash, for example, may require it).

Error Message %PRST_IFS-3-GENERAL: persistent media IFS general error: %s Explanation An error occurred in the persistent media module (IOS file system). Recommended Action Copy the message exactly as it appears on the console or in the system log.


PRST_VBL Messages This section contains persistent variable messages.

PRST_VBL-3 Error Message %PRST_VBL-3-GENERAL: Persistent general error: %s Explanation A general error related to a persistent variable occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1191

PT Messages

Error Message %PRST_VBL-3-MEDIA: Persistent media error: %s Explanation A media error related to a persistent variable occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


PT Messages This section contains Protocol Translation messages.

Error Message %PT-3-PT_HW_UNAVAIL: Protocol Tunneling hardware resource not available. [chars] Explanation Protocol tunneling could not be enabled because no redirect registers are available. Protocol tunneling requires redirect registers. Recommended Action Disable any applications that use redirect registers and configure the protocol

tunneling again.

Error Message %PT-3-PT_NO_SWSB: Protocol Tunneling software subblock not found. [chars] Explanation The software subblock that is used for protocol tunneling could not be found for the port specified in the message text. Protocol tunneling has been disabled on this port. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1192

PXF Messages

PXF Messages This section contains Parallel eXpress Forwarding (PXF) messages.

Error Message %PXF-2-DWNLOADCOLROW: Could not download the microcode into PXF processor @ column [dec] row [dec]. Explanation A problem occurred that prevented the microcode from being downloaded to PXF. This

could be either a software or hardware abnormality. Recommended Action Copy the message exactly as it appears on the console or in the system log.


PXF_ACL Messages This section contains Parallel eXpress Forwarding (PXF) ACL-specific messages.

PXF_ACL-3 Error Message %PXF_ACL-3-WS_ACL_CONTEXT_EVENT: [chars] [chars] Explanation An invalid turbo ACL context has been used to call a block initialization. This condition

is possibly caused by a process-level watchdog that has timed out. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1193

PXFAPI Messages

Error Message %PXF_ACL-3-WS_ACL_EVENT: [chars] Explanation PXF turbo ACL errors have occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PXF_ACL-3-WS_ACL_PXF_CONTEXT_EVENT: [chars] [chars] Explanation An invalid PXF turbo ACL context has been used to call a block initialization. This

condition is possibly caused by a process-level watchdog that has timed out. Recommended Action Copy the message exactly as it appears on the console or in the system log.


PXFAPI Messages This section contains Parallel eXpress Forwarding (PXF) API-related messages.

PXFAPI-3 Error Message %PXFAPI-3-TIFBAD: TIF [int] is not available or invalid. Explanation The PXF interface instance that was requested is not available or is invalid. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1194

PXF_FIB Messages


Error Message %PXFAPI-3-TIFINUSE: Request for in-use reserved TIF [int] Explanation A PXF interface instance was requested but is currently reserved as it is still in use. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PXFAPI-3-TIFNODETACH: TIF [int] could not be detached. Explanation The PXF interface instance could not be detached. Recommended Action Copy the message exactly as it appears on the console or in the system log.


PXF_FIB Messages This section contains Parallel eXpress Forwarding (PXF) Forwarding Information Base (FIB) messages.

PXF_FIB-3 Error Message %PXF_FIB-3-WS_FIB_RW_EVENT: [chars] [dec] [chars] Explanation The Layer 2 information for this interface is not consistent in PXF. The router may

resume normal operation after this message. Recommended Action If this message recurs, copy the message exactly as it appears on the console

or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying


1195

PXF_FLOW Messages


Error Message %PXF_FIB-3-WS_FIB_TIF_EVENT: [chars] [chars] Explanation The interface does not have a valid PXF handle attached to it. The router may resume

normal operation after this message. Recommended Action If this message recurs, copy the message exactly as it appears on the console


PXF_FLOW Messages This section contains Parallel eXpress Forwarding (PXF) NetFlow messages.

PXF_FLOW-4 Error Message %PXF_FLOW-4-INVLDAGG_SINGLE: The netflow aggregation scheme is not supported in PXF. This interface will be marked as unsupported by the PXF, all incoming traffic to this interface will be processed in the RP. Explanation The only NetFlow aggregation schemes supported in the PXF are AS aggregation, proto port aggregation, source prefix aggregation, and destination aggregation. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1196

PXF_GRE Messages

Error Message %PXF_FLOW-4-NO_INVLDAGG: All previously configured unsupported netflow aggregations have been disabled or removed. Netflow enabled interfaces may however still be marked unsupported due to other unsupported features configured. Explanation Only PXF-supported NetFlow aggregation schemes are configured, or possibly no

NetFlow aggregation schemes are configured. Recommended Action Copy the message exactly as it appears on the console or in the system log.


PXF_GRE Messages This section contains Parallel eXpress Forwarding (PXF) GRE tunnel-related messages.

PXF_GRE-3 Error Message %PXF_GRE-3-PXF_MEM_ERR_CLR_TSTATS: PXF MEM ERROR when clearing PXF tunnel stats (Addr=[hex]) Explanation An error occurred when clearing the tunnel statistics from PXF memory. The tunnel

statistics could not be properly cleared. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1197

PXF_GRE Messages

Error Message %PXF_GRE-3-PXF_MEM_ERR_HINFO: PXF MEM ERROR when downloading tunnel hash info to PXF (Addr=[hex]) Explanation An error occurred when writing into PXF memory. Tunnel hash information could not

be properly downloaded to PXF. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PXF_GRE-3-PXF_MEM_ERR_HTIFS: PXF MEM ERROR when downloading tunnel hashed tifs to PXF (Addr=[hex]) Explanation An error occurred when writing into PXF memory. Hashed tunnel TIFs could not be

properly downloaded to PXF. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PXF_GRE-3-PXF_MEM_ERR_READ_TSTATS: PXF MEM ERROR when reading PXF tunnel stats (Addr=[hex]) Explanation An error occurred when reading the tunnel statistics from PXF memory. The tunnel

statistics could not be properly read. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1198

PXF_GRE Messages

Error Message %PXF_GRE-3-PXF_MEM_ERR_TID: PXF MEM ERROR when downloading tunnel id to PXF (Addr=[hex]) Explanation An error occurred when writing into PXF memory. The tunnel ID could not be properly

downloaded to PXF. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PXF_GRE-3-PXF_MEM_ERR_TVRF: PXF MEM ERROR when downloading tunnel vrf to PXF (Addr=[hex]) Explanation An error occurred when writing into PXF memory. The tunnel VRF could not be

properly downloaded to PXF. Recommended Action Copy the message exactly as it appears on the console or in the system log.


PXF_GRE-4 Error Message %PXF_GRE-4-PXF_MEM_ERR: Memory allocation error while [chars] Explanation An error has occurred while allocating memory. PXF could not process tunneled packets

properly. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1199

PXF_MPLS_TE Messages

PXF_MPLS_TE Messages This section contains Parallel eXpress Forwarding (PXF) MPLS traffic engineering (TE) messages.

PXF_MPLS_TE-3 Error Message %PXF_MPLS_TE-3-PXF_MEM_ERR_CLR_TSTATS: PXF MEM ERROR when clearing PXF tunnel stats (Addr=[hex]) Explanation An error occurred when tunnel statistics were being cleared from PXF memory. The

tunnel statistics could not be properly cleared. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PXF_MPLS_TE-3-PXF_MEM_ERR_LKUP_TABLE: PXF MEM ERROR when downloading TE tunnel look-up table to PXF (Addr=[hex]) Explanation An error occurred while information was being written into PXF memory. The lookup

table could not be properly downloaded to PXF. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %PXF_MPLS_TE-3-PXF_MEM_ERR_READ_TSTATS: PXF MEM ERROR when reading PXF tunnel stats (Addr=[hex]) Explanation An error occurred while tunnel statistics were being read from PXF memory. The tunnel

statistics could not be properly read. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1200

PXF_QOS Messages


PXF_MPLS_TE-4 Error Message %PXF_MPLS_TE-4-PXF_MEM_ERR: Memory allocation error while [chars] Explanation An error has occurred while allocating memory. PXF could not process a tunneled

packet properly. Recommended Action Copy the message exactly as it appears on the console or in the system log.


PXF_QOS Messages This section contains Parallel eXpress Forwarding (PXF) Quality of Service (QoS) messages.

PXF_QOS-3 Error Message %PXF_QOS-3-QOS_STAT_GENERATION_FAIL: Cannot [chars] actual QoS statistics generation in PXF Explanation An error occurred while QoS statistics generation was being enabled or disabled. Recommended Action Enable QoS debugging to obtain more information in case the condition recurs.

Disable and reenable the PXF QoS statistics. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support


1201

QM Messages


Error Message %PXF_QOS-3-SUB_INTF_SRVPOL_FAIL: Error attaching [chars] service-policy PXF data to [chars]: [chars] Explanation The PXF portion of the service policy data could not be assigned to a subinterface. The configuration will show that the service policy is attached to the subinterface; however, the download of the necessary PXF data has not occurred. Because of this condition, the service policy will not be effective on the subinterface. Recommended Action Detach and reattach the service policy to the subinterface. If this message

recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

QM Messages This section contains Quality of Service Management (QM) messages.

QM-2 Error Message %QM-2-CONFORM_ACTION_NE: Different aggregate and microflow conform-action in class [chars][policy [chars]] Explanation Conform actions in the police and police flow commands must be the same for the same

class in a service-policy applied to MLS interfaces. Recommended Action Change the conform-action in the police or police flow command to make both

actions the same, or remove one of the two commands.

Error Message %QM-2-MERGE_ERROR: ACL merge error for Interface [chars] in [chars] direction status [dec] Explanation The ACL merge failed before programming ACLs into the TCAM. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1202

QM Messages


Error Message %QM-2-PLC_ATTACH_REJECT_2_PLCRS: Command rejected: (policy [chars] interface [chars] dir [chars]) police and police aggregate commands present in same traffic class Explanation One of two conditions has occurred: either a policy map that contains a traffic class with

both police and police aggregate commands is attached to an unsupported interface or a policy attached to an interface is being modified in an unsupported manner. Recommended Action Remove the unsupported command combination from the same traffic class. In

the case of a modification to a policy that is already attached to unsupported interfaces, no action is required because the command is automatically rejected.

Error Message %QM-2-PLC_ATTACH_REJECT_ARP_UFLOW: Command rejected: (policy-map [chars] class [chars] interface [chars] dir [chars]) flow policer is not supported for traffic classes matching ARP ACL. Explanation In a policy map, flow policer is not supported if the traffic class is matching ARP ACL. Recommended Action Remove the flow policer from traffic class matching ARP ACL and reattach the

policy or change the traffic class to match non-ARP ACL and configure flow policer.

Error Message %QM-2-PLC_ATTACH_REJECT_IPX_PROTO: Command rejected: (policy-map %s class %s) IPX access-list is not supported in EARL7. Explanation In a class map, an IPX access list is not supported in the match criteria. Recommended Action Remove the IPX access list from the traffic class match criteria and reattach the

policy, or change the traffic class to match a non-IPX ACL.

Error Message %QM-2-PLC_ATTACH_REJECT_SET: Command rejected: (policy [chars] interface [chars] dir [chars]) police/trust and set commands present in same traffic class Explanation One of two conditions has occurred: either a policy map that contains a traffic class with

both set and police/trust commands is attached to an unsupported interface or a policy attached to an interface is being modified in an unsupported manner. Recommended Action Remove the unsupported command combination from the same traffic class. In

the case of a modification to a policy that is already attached to unsupported interfaces, no action is required because the command is automatically rejected.


1203

QM Messages

Error Message %QM-2-SET_IP_AND_MPLS: Hardware does not support ’set mpls exp’ and ’set precedence | dscp’ together Explanation The hardware does not support the set mpls exp and set precedence | dscp commands

together. Recommended Action Use either the set mpls exp or the set precedence | dscp command.

Error Message %QM-2-TCAM_ENTRIES_EXCEEDED: ACL merge failed, ACEs exceed TCAM capacity or 0 ACES, [dec] ACEs for interface [chars] in [chars] direction Explanation The ACL merge was halted. The results of the ACL merge have caused the number of

ACEs to exceed the TCAM capacity, or zero ACEs were present. Recommended Action Copy the message exactly as it appears on the console or in the system log.


QM-4 Error Message %QM-4-AGG_POL_EXCEEDED: QoS Hardware Resources Exceeded : Out of Aggregate policers Explanation The supported number of aggregate policers has been exceeded. On EARL 7-based

switches, this limit is 1023. Recommended Action Attempt to aggregate policers if possible.

Error Message %QM-4-FRAG_INFO: QoS TINY_FRAG : enable ’mls qos vlan based’ on accessports of L3 VLANs for fo1 policing to take effect Explanation Policing of fragment offset == 1 (FO1) packets through switch ports will be supported

only if the port is in VLAN-based mode, because FO1 policing is a Layer 3 feature. Recommended Action Enter the mls qos vlan based command on the switch port.

Error Message %QM-4-MFLOW_POL_EXCEEDED: QoS Hardware Resources Exceeded : Out of Micro flow policers Explanation The supported number of microflow policers has been exceeded. On EARL7-based

switches, this limit is 63. Recommended Action No action is required.


1204

QM Messages

Error Message %QM-4-TCAM_MASK: Hardware TCAM mask entry capacity exceeded Explanation The hardware TCAM does not have the mask capacity to handle all of the configured

ACLs. Recommended Action Because the configured ACLs are too large to all fit in the hardware TCAM, try

to share the same ACLs across multiple interfaces in order to reduce TCAM resource contention.

Error Message %QM-4-UNEXPECTED_INTERNAL_QOS_CONDITION: Unexpected internal QoS condition. Explanation An unexpected internal QoS condition has occurred. QoS debug may be enabled to

obtain more information in case the condition recurs. Recommended Action Copy the message exactly as it appears on the console or in the system log.


QM-6 Error Message %QM-6-EOM_FORCE_TRUSTED: EoMPLS on [chars] caused install of ’trust cos’ state Explanation If EoMPLS is configured on the interface or any of its subinterfaces, the no trust state

is automatically replaced by the trust CoS state. Recommended Action Remove all EoMPLS configurations from the interface to restore the no trust

state.

Error Message %QM-6-EOM_RESTORE_UNTRUSTED: The ’no trust’ state is restored on EoMPLS removal from [chars] Explanation If EoMPLS is unconfigured on the interface and all its subinterfaces, the no trust state

is restored. Recommended Action No action is required.


1205

QM Messages

Error Message %QM-6-EOM_TRUST_NOT_INSTALLED: ’no trust’ command is not installed on [chars] in presence of EoMPLS Explanation If EoMPLS is configured on the interface or any of its subinterfaces, the no trust command is not installed. Recommended Action Remove all EoMPLS configurations from the interface.

Error Message %QM-6-IOS_AND_PS_FEATURE: [chars] action cannot be present in classmap [chars] of policymap [chars] because this service-policy cannot be executed in Cat6K HW due to the presence of filters which require packets to be processed in IOS SW Explanation NBAR is required for the match protocol commands used. NBAR exists only in

software. Hardware-specific actions cannot be supported. Recommended Action Remove either the hardware-specific command(s) or the match protocol

criteria in class map.

Error Message %QM-6-NBAR_DISABLED: Packets will not be software switched. Explanation NBAR is disabled so traffic will not be redirected to the RP. Recommended Action No action is required.

Error Message %QM-6-NBAR_ENABLED: Packets will be software switched. Explanation NBAR is enabled so all the traffic will be redirected to the RP. Recommended Action No action is required.

Error Message %QM-6-SET_AND_POLICE: ’set’ and ’police’ commands cannot co-exist in classmap [chars] of policymap [chars] Explanation The set and police commands cannot coexist in a class map for a QoS manager (QM) supported interface. Recommended Action Choose one of the commands or use the set-dscp-transmit | set-precedence-transmit | set-exp option for the conform action of the police command.

Error Message %QM-6-SET_AND_TRUST: ’set’ and ’trust’ commands cannot co-exist in classmap [chars] of policymap [chars] Explanation The set and trust commands cannot coexist in a class map for a QoS manager (QM) supported interface. Recommended Action Choose one of the commands.


1206

QNQ Messages

Error Message %QM-6-SHAREDAG_AND_POLICE: ’police aggregate’ and regular ’police’ commands cannot co-exist in classmap [chars] of policymap [chars] Explanation The set and police commands cannot coexist in a class map for a QoS manager (QM) supported interface. Recommended Action Choose one of the commands or use the set-dscp-transmit | set-precedence-transmit | set-exp option for the conform action of the police command.

Error Message %QM-6-TRUST_AND_POLICE: ’trust’ and ’police/police aggregate with a set’ cannot co-exist in classmap %s of policymap %s Explanation The trust command and the police (or police aggregate) command with set statements

cannot coexist in a class map for a QoS manager (QM) supported interface. Recommended Action Remove the set statements in the police or police aggregate command.

Error Message %QM-6-UNDEF_SHR_AG: shared aggregate policer [chars] used in classmap [chars] of policymap [chars] is not defined Explanation Shared aggregate policers have to be created first by entering the mls qos aggregate

command before being used in a policy map. Recommended Action Either define the shared aggregate policer or do not use it in the policy map.

QNQ Messages This section contains Q-in-Q (QnQ) messages.

Error Message %QNQ-6-NATIVE_VLAN_TAGGING: Please enable the native VLAN tagging feature for proper functioning of the Q-in-Q service. Explanation QnQ may not function properly for packets in the native VLAN if native VLAN tagging

is not enabled. Recommended Action Enable native VLAN tagging by entering the vlan dot1q tag native command.


1207

QOS Messages

QOS Messages This section contains Quality of Service (QoS) messages.

QOS-3 Error Message %QOS-3-HA_BULK_SYNC: %s Failure in completing bulk sync Explanation The QoS configuration cannot be synchronized to the standby. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %QOS-3-HA_BULK_SYNC_BEFORE_TIMEOUT: %s Failure in completing bulk sync before timeout Explanation The QoS configuration cannot be synchronized to the standby. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %QOS-3-HA_GET_ARG_NUM: %s Failure in getting event identification Explanation The QoS configuration cannot be synchronized to the standby. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1208

QOS Messages


Error Message %QOS-3-HQFPOOLERR: interface [chars]: failed to allocate hqf particle Explanation The HQF particle pool is empty. It cannot process a router generated packet. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show buffer and show policy interface commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %QOS-3-NOCAPID: Failed to allocate QoS capability ID. Explanation No more QoS capability IDs are available. Recommended Action Change the Cisco IOS software image so that it can support more QoS

capability IDs. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

QOS-6 Error Message %QOS-6-EXTENDED_BURST_CHANGED_WARN: Illegal extended burst size; it is increased to [int] Explanation Configured extended burst size is less than the Rate.It is considered to be illegal and has been reset basedon the Rate. Recommended Action This is an informational message only.No action is required.


1209

QOSMGR Messages

Error Message %QOS-6-NORMAL_BURST_CHANGED_WARN: Illegal normal burst size; it is increased to [int] Explanation Configured normal burst size is less than the Rate.It is considered to be illegal and has

been reset basedon the Rate. Recommended Action This is an informational message only. No action is required.

QOSMGR Messages This section contains Quality of Service (QoS) manager messages.

QOSMGR-3 Error Message %QOSMGR-3-FEATURE_NOT_FOUND: Cannot find feature for [chars] Explanation An internal software error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %QOSMGR-3-FILTERTYPE_INVALID: Internal Error Invalid Policy filtertype [dec] Explanation An internal software error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1210

QOSMGR Messages

Error Message %QOSMGR-3-MERGE_RES_COUNT: Internal Error Invalid count Explanation An internal software error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %QOSMGR-3-NO_POLICER_QOSLABEL: Creating port Class Label Failed Explanation An internal software error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %QOSMGR-3-NO_VMR_QOSLABEL: qm_generate_vmrs have no qos label Explanation An internal software error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1211

QOSMGR Messages

Error Message %QOSMGR-3-NULL_POLICER: Internal Error Invalid Policer Explanation An internal software error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %QOSMGR-3-POLICER_RES_COUNT: Internal Error Invalid Policer count Explanation An internal software error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %QOSMGR-3-POLICYMAP_NOT_FOUND: Cannot find policymap for [chars] Explanation An internal software error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1212

QOSMGR Messages

Error Message %QOSMGR-3-QUEUE_PTR_ERROR: queue pointers out of order [hex] [hex] [hex] [hex] Explanation An internal software error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %QOSMGR-3-RESERVE_COUNT_ERROR: Reserved Count Exceeding total [dec] Explanation An internal software error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %QOSMGR-3-RESOURCE_INTERNAL: Internal Error in resource allocation Explanation An internal software error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1213

QOSMGR Messages

Error Message %QOSMGR-3-VMRSEQ_INVALID: Internal Error Invalid VMR sequence Explanation An internal software error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


QOSMGR-4 Error Message %QOSMGR-4-ACTION_NOT_SUPPORTED: Action is not supported in policymap [chars] Explanation An action that cannot be configured by the set, trust, and police commands in policy

map configuration mode was configured in a policy map. This condition indicates a hardware limitation. Recommended Action Configure only the supported actions that can be configured by the set, trust,

and police commands in policy map configuration mode.

Error Message %QOSMGR-4-CLASS_NOT_SUPPORTED: Classification is not supported in classmap [chars] Explanation An unsupported match class-map command was entered in class-map configuration

mode in a policy map and attached to an egress interface, or more than one match command was configured. This condition indicates a hardware limitation. Recommended Action Reconfigure the class map or the policy map. Use only the match dscp

command in class-map configuration mode in a policy map that is attached to an egress interface. Only one match per class map is supported.

Error Message %QOSMGR-4-COMMAND_FAILURE: Execution of [chars] command failed on [chars] Explanation The command to configure a QoS setting failed. This condition possibly indicates a lack of hardware resources. Recommended Action Check to see if any other messages along with this message indicate a resource

failure. If other messages indicate that the hardware resources have been exceeded, retry the command with a smaller configuration. If you require more information, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the


1214

QOSMGR Messages

tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %QOSMGR-4-HARDWARE_NOT_SUPPORTED: Hardware limitation has reached for policymap [chars] Explanation The hardware cannot support the current policy map configuration. More QoS ACL

entries have been configured than the number that is specified in the Switch Database Management template. Recommended Action Reconfigure the class map or the policy map and reduce the number of QoS

ACLs.

Error Message %QOSMGR-4-MATCH_NOT_SUPPORTED: Match type is not supported in classmap [chars] Explanation An unsupported match type was specified. The only match types that are supported are match access-group, match dscp, and match precedence. Recommended Action Reconfigure the class map. Ensure that only the match access-group, match

dscp, and match precedence commands in class-map configuration mode are used within the class map.

Error Message %QOSMGR-4-NOT_SUPPORTED: Action ’[chars]’ is not supported for a policymap attached to output side. Explanation A set or trust command was configured in policy-map class configuration mode in a

policy map and attached to an egress interface. The requested action will not be applied to the configuration. Recommended Action Do not configure a set or trust command in policy-map class configuration mode in a policy map and attach it to an egress interface. These policy map actions are supported only on ingress interfaces.

Error Message %QOSMGR-4-POLICER_PLATFORM_NOT_SUPPORTED: Policer configuration has exceeded hardware limitation for policymap [chars] Explanation The policy map configuration has exceeded the limitation of the hardware. More

policers have been configured in all policy maps by using the police or police aggregate command in policy-map class configuration mode than can be supported by the hardware. Recommended Action Reconfigure the class map or the policy map or delete the policy from some

interfaces.


1215

R4K_MP Messages

Error Message %QOSMGR-4-POLICER_POLICY_NOT_SUPPORTED: Number of policers has exceeded per policy hardware limitation for policymap [chars] Explanation The policy map configuration has exceeded the limitation of the hardware. More

policers have been configured in a policy map by using the police or police aggregate command in policy-map class configuration mode than can be supported by the hardware. Recommended Action Reconfigure the class map or the policy map, and reduce the number of

policers.

R4K_MP Messages This section contains central processing unit (R4K_MP) messages.

R4K_MP-3 Error Message %R4K_MP-3-CRASHED: CPU [dec] has now crashed a total of [dec] times. Explanation The specified CPU failed the specified number of times and has been restarted. Recommended Action Copy the message exactly as it appears on the console or in the system log.


R4K_MP-5 Error Message %R4K_MP-5-DELEGATE_GETBUF: Delegated call to [hex] failed, out of buffers Explanation A remote procedure call (RPC) to the specified function failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1216

R4K_MP Messages


1217

R4K_MP Messages


1218

RADIUS Messages

RADIUS Messages This section contains RADIUS messages.

RADIUS-3 Error Message %RADIUS-3-AIDDEFINEFAILED: a_id definition ignored. Explanation An attempt to store a corrupted authority ID (a_id) failed or memory allocation failed

during authority ID definition. Any existing authority ID will be preserved. Recommended Action Configure a proper authority ID.

Error Message %RADIUS-3-CANNOT_OPEN_SOCKET: Cannot open UDP socket for service %s Explanation The router is unable to open a socket for UDP communications by the indicated service. Recommended Action Check your configuration to make sure that no other services are using the

same port.

Error Message %RADIUS-3-CORRUPTCONTEXT: Bad Magic pattern in [chars]:[hex], magic:[hex]! Explanation The magic pattern imprinted on the internal hash table data structures in the RADIUS

subsystem is missing, which indicates memory corruption. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %RADIUS-3-INVALIDFORMAT: Invalid Nas Port Format: [chars] [char] Explanation The user is attempting to configure an incorrect format string. Recommended Action Enter a 32-character string using supported characters only.


1217

RADIUS Messages

Error Message %RADIUS-3-NOACCOUNTINGRESPONSE: Accounting message [chars] for session [chars] failed to receive Accounting Response. Explanation There was no response from the RADIUS server, and the maximum number of

retransmissions has been exceeded. The network or the RADIUS server may be down. Recommended Action Check the network connectivity to the RADIUS servers and check that the

servers are running.

Error Message %RADIUS-3-NOATTRLIST: No attribute-list passed through parser. Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %RADIUS-3-SERVERTYPEMISMATCH: Servers [IP_address] and [IP_address] in server group ’[chars]’ are of different types. Explanation All the servers in a server group should be of either type: standard or nonstandard. Recommended Action Check the running configuration and verify that all the radius servers in the

specified server group are of the same type: either standard or nonstandard.

Error Message %RADIUS-3-SOURCEPORTALLOCERROR: Warning: Unable to allocate port [dec] Explanation The system was unable to allocate the port specified in the message. The system will

not have the full range of source ports. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1218

RADIUS Messages

Error Message %RADIUS-3-UNKNOWNAPI: Unknown API type %d Explanation The RADIUS process has been invoked using an unknown application program

interface (API) type. This condition is the result of a fault in the RADIUS subsystem. Recommended Action Collect traceback and contact your technical support representative.

Error Message %RADIUS-3-ZEROATTRLEN: Radius attr [dec] len 0 Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


RADIUS-4 Error Message %RADIUS-4-BADATTRLIST: Unable to process attribute list. Explanation The attribute list is syntactically incorrect. Recommended Action Specify the attribute list as a comma-delimited string of integers between 1 and

255.

Error Message %RADIUS-4-NOATTRLISTDEF: Warning: Attribute list [chars] is not defined. Explanation The given attribute list is not defined. Recommended Action Define the attribute list as soon as possible.

Error Message %RADIUS-4-NOPUBLICSERV: Warning: No servers were found in the public server list. Explanation No servers are in the global public servers list. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1219

RANDOM Messages


Error Message %RADIUS-4-RADIUS_ALIVE: RADIUS server [IP_address]:[int],[int] has returned. Explanation A RADIUS server that previously was not responding has responded to a new request. Recommended Action No action is required.

Error Message %RADIUS-4-RADIUS_DEAD: RADIUS server [IP_address]:[int],[int] is not responding. Explanation A RADIUS server has not responded to repeated requests. Recommended Action Check to see if the RADIUS server is still active.

RADIUS-6 Error Message %RADIUS-6-RESETDEADSERVER: Group [chars]: Marked alive as Radius server [IP_address]:[dec],[dec] configured. Explanation The RADIUS server is configured in the server group that was previously marked dead. Recommended Action This is an informational message only. No action is required.

RANDOM Messages This section contains utility messages.

RANDOM-6 Error Message %RANDOM-6-RANDOM: A pseudo-random number was generated twice in succession Explanation A pseudo-random number generator produced the same number twice in succession. Recommended Action Under normal circumstances, a pseudo-random number generator will

occasionally produce the same number twice in succession, which is not a problem. However, if this message occurs frequently, the system should be manually reloaded. If the message is persistent across reloads, copy the error message exactly as it appears, and report it to your Cisco technical support representative.


1220

RASP16 Messages

RASP16 Messages This section contains interface multiplexer ASIC messages.

Error Message %RASP16-5-NULL_RASP16_OBJECT: The Interface Multiplexer device object pointer is set to NULL. Explanation The memory location of the interface multiplexer device object is invalid. The interface

multiplexer ASIC operation is disabled and the device interrupt is now masked. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %RASP16-5-RASP_INIT_FAILURE: The Interface Multiplexer ASIC initialization failed. Explanation The interface multiplexer ASIC could not be initialized. As a result, this device is not

operational and has been disabled. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1221

RBM Messages

RBM Messages This section contains Role-based Access Control Manager (RBM) messages.

RBM-0 Error Message %RBM-0-RBM_EMERG: %s Explanation An error occurred in the Role-based Access Control Manager (RBM). Recommended Action Copy the message exactly as it appears on the console or in the system log.


RBM-1 Error Message %RBM-1-RBM_ALERT: %s Explanation An error occurred in the Role-Based Manager (RBM). Recommended Action Copy the message exactly as it appears on the console or in the system log.



1222

RBM Messages

RBM-2 Error Message %RBM-2-RBM_CRIT: %s Explanation An error occurred in the Role-based Access Control Manager (RBM). Recommended Action Copy the message exactly as it appears on the console or in the system log.


RBM-3 Error Message %RBM-3-RBM_ERR: %s Explanation An error occurred in the Role-based Access Control Manager (RBM). Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %RBM-3-RBM_PARSE_ACE: Could not parse command for adding ACE ’[chars]’ to [chars] Role-Based Access List ’[chars]’ Explanation An error occured while attempting to add an ACE to a Role-Based Access List. The

ACE syntax is most likely incompatible with the type of RBACL. Recommended Action Verify the syntax of the ACEs of the RBACL in ACS and the IP protocol

versions the RBACL applies to. RBACL ACE syntax could be verified by manually configuring IP/IPv6 RBACL on the system within (config-rb-acl)/(config-ipv6rb-acl) configuration mode respectively.


1223

RBM Messages

Error Message %RBM-3-RBM_PARSE_RBACL: Could not parse command for creating [chars] Role-Based Access List ’[chars]’ ’[chars]’ Explanation An error occured while attempting to create Role-Based Access List. Recommended Action This error could occur when TrustSec attempts to install RBACL it has

acquired from ACS while configuration mode is locked exclusively. TrustSec will retry this operation and should eventually succeed once configuration mode is no longer locked. If the error occurs when the configuration mode is not locked or if the RBACL does not get installed after the configuration mode lock is released.

RBM-4 Error Message %RBM-4-RBM_WARNING: %s Explanation An error occurred in the Role-based Access Control Manager (RBM). Recommended Action Copy the message exactly as it appears on the console or in the system log.


RBM-5 Error Message %RBM-5-RBM_NOTICE: %s Explanation This is a notice message from the Role-based Access Control Manager (RBM). Recommended Action Copy the message exactly as it appears on the console or in the system log.



1224

RED_MODE Messages

RBM-6 Error Message %RBM-6-RBM_INFO: %s Explanation This is an informational message from the Role-based Access Control Manager (RBM). Recommended Action No action is required.

RBM-7 Error Message %RBM-7-RBM_ASSERT: Assertion Failure ( %s @%s:%d ) : %s Explanation An error occurred in the Role-based Access Control Manager (RBM). Recommended Action Copy the message exactly as it appears on the console or in the system log.


RED_MODE Messages This section contains high availability redundancy mode messages.

RED_MODE-3 Error Message %RED_MODE-3-CAPENTRY_REG: Red Mode Cap Entry ([dec]) for Entity ([dec]) Registration failed ([chars]) Explanation A capability entry could not be registered for the redundancy mode ISSU. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show issu capability entries command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support


1225

RED_MODE Messages


Error Message %RED_MODE-3-CAPGROUP_REG: Red Mode Cap Group ([dec]) for Entity ([dec]) Registration failed ([chars]) Explanation A capability group could not be registered for the redundancy mode ISSU. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show capability groups command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %RED_MODE-3-CAP_REG: Red Mode cap reg failed: reason [dec] Explanation The capabilities of the redundancy mode ISSU could not be registered. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show issu capability arguments command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %RED_MODE-3-CAPTYPE_REG: Red Mode Cap Type for Entity ([dec]) Registration failed ([chars]) Explanation A capability type could not be registered for the redundancy mode ISSU. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show issu capability types command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support


1226

RED_MODE Messages


Error Message %RED_MODE-3-CLIENT_REG: Red Mode Client ([dec]) Registration failed ([chars]) Explanation The redundancy mode ISSU client could not be registered. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show issu clients command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %RED_MODE-3-CLIENT_REG_FAILED: Red Mode ISSU client ([dec]) Client registration failed. [chars] Explanation The redundancy mode ISSU client could not be registered during system initialization. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %RED_MODE-3-DELAYED_REGISTER: Delayed registration could not be completed succesfully, Operand = [dec] Explanation The delayed registration operation for the RF-proxy clients could not complete

successfully. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1227

RED_MODE Messages


Error Message %RED_MODE-3-ENTITY_REG: Red Mode Entity ([dec]) Registration failed ([chars]) Explanation The redundancy mode ISSU entity could not be registered. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show issu entities command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %RED_MODE-3-GET_BUFFER: Red Mode ISSU session ([dec]) failed to get buffer Explanation The redundancy mode ISSU session was unable to get a buffer. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show issu fsm command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %RED_MODE-3-IPC_AGENT: [chars] [ [chars] ] Explanation There has been a failure in the redundancy mode IPC agent. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1228

RED_MODE Messages


Error Message %RED_MODE-3-ISSU_BASE_CLIENT_INCOMP: One or more ISSU base clients are incompatible, fallback to RPR Explanation An incompatible ISSU base client caused the redundancy mode to revert to route

processor redundancy (RPR) mode. Recommended Action Check the console log for the name and ID of the incompatible ISSU base

clients.

Error Message %RED_MODE-3-ISSU_NEGOTIATION: [chars] [ [chars] ] Explanation There has been a failure in the redundancy mode client. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %RED_MODE-3-ISSU_RESET_PEER_IMAGE_COMP: Failed to reset peer image to be compatible Explanation The redundancy process was unable to reset the peer image to be compatible after the

standby device came back up in RPR mode. This message is usually seen in conjunction with an ISSU module error message. Recommended Action

Examine the associated ISSU message for the cause of the failure and the

recommended action.

Error Message %RED_MODE-3-ISSU_SET_BASE_CLIENT_INCOMP: Failed to set base client incompatibility Explanation The redundancy process was unable to set the base client incompatibility. Recommended Action Check the console log for the name and ID of the incompatible ISSU base

clients.


1229

RED_MODE Messages

Error Message %RED_MODE-3-MSG_DATAPTR: Red Mode Client ([dec]) get msg dataptr failed. Error = [dec] Explanation The redundancy mode ISSU client could not obtain a message data pointer. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %RED_MODE-3-MSGGROUP_REG: Red Mode Msg Group ([dec]) for Entity ([dec]) Registration failed ([chars]) Explanation The message group for the redundancy mode ISSU entity could not be registered. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show issu message groups command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %RED_MODE-3-MSG_MTU: Red Mode Client ([dec]) get msg mtu failed. Error = [dec] Explanation The redundancy mode ISSU client could not obtain the message size. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1230

RED_MODE Messages

Error Message %RED_MODE-3-MSG_REG: Red Mode msg reg failed: reason [dec] Explanation Messages for the redundancy mode ISSU could not be registered. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show issu message arguments command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %RED_MODE-3-MSG_SEND: Red Mode ISSU client for session ([dec]) failed to send message. Error Code = [chars] Explanation The redundancy mode ISSU client could not send a negotiation message to a peer. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %RED_MODE-3-MSGTYPE_REG: Red Mode Msg Type for Entity ([dec]) Registration failed ([chars]) Explanation The message type for the redundancy mode ISSU entity could not be registered. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show issu message types command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


1231

RED_MODE Messages

Error Message %RED_MODE-3-NO_DEREGISTER: Could not deregister plugin for redundancy mode [chars] Explanation At system initialization the plugin that describes the capabilities of this redundancy

mode could not be deregistered with the redundancy mode client. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %RED_MODE-3-RED_MODE_MSG_NOT_OK: Red Mode ISSU msg type ([dec]) is not ok Explanation The redundancy mode ISSU message type has not negotiated correctly. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show issu message types clientID command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %RED_MODE-3-RED_MODE_START_NEGO_FAILED: Red Mode ISSU start nego session failed ([chars]) Explanation The redundancy mode ISSU could not start its negotiation process. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1232

RED_MODE Messages

Error Message %RED_MODE-3-RED_MODE_XFROM_FAIL: Red Mode ISSU [chars] transformation failed ([chars]) Explanation The transformation operation for the redundancy mode ISSU message has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show issu fsm and show issue sessions command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %RED_MODE-3-SELECT_MODE: The mode change to [dec] was unsuccessful rc = [dec], force = [dec], caller = [dec] Explanation The specified mode change operation did not complete successfully. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %RED_MODE-3-SESSION_REG: Red Mode session for Entity ([dec]) Registration failed ([chars]) Explanation The redundancy mode ISSU session could not be registered. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show issu sessions command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


1233

REDUNDANCY Messages

Error Message %RED_MODE-3-SESSION_UNREG: Red Mode session ([dec]) Un-Registration failed ([chars]) Explanation The redundancy mode ISSU session could not be unregistered. Recommended Action Copy the message exactly as it appears on the console or in the system log.


REDUNDANCY Messages This section contains high availability redundancy messages.

REDUNDANCY-3 Error Message %REDUNDANCY-3-EHSAISSU: %s failed with error code [ %s ] Explanation An ISSU-related error occurred in the redundancy process. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %REDUNDANCY-3-EHSAPARSER: parser failure - [chars]: tty=[dec] orig_parse_cli_type=[dec] parse_cli_type=[dec] Explanation An EHSA parser error occurred. The details about the failure will beprinted. Recommended Action Copy the error message exactly as it appears. Copy down the system’s

configuration along with any other relevant information. Contact your technical support representative for assistance.


1234

REDUNDANCY Messages

Error Message %REDUNDANCY-3-MEMORY_DIFF: WARNING, nonsymetrical configuration: Active has [dec]K Standby has [dec]K Explanation The redundant route processors (RPs) have different memory configurations. The

configuration is allowed but is discouraged. Recommended Action Attempt to avoid configuring a system with redundant RPs that have different

memory configurations.

REDUNDANCY-4 Error Message %REDUNDANCY-4-PEER_DID_NOT_RESPOND: Resetting peer [chars] because it did not respond to verification of HA role. Explanation The platform uses high availability (HA) hardware lines to perform HA role negotiation

during the system boot time. The standby controller card verifies its role as the standby with the active controller card through the MBUS. If the active controller card does not respond, it is reset as it is either nonresponsive (hung) or is running an earlier version of Cisco IOS software. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %REDUNDANCY-4-RELOADING_STANDBY: Reloading the Standby [chars] Explanation The active system has sent a reload IPC request to the standby peer. If the reload is not

successful, the standby peer will be power cycled rather than reloaded. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1235

REDUNDANCY_UTILS Messages

REDUNDANCY-6 Error Message %REDUNDANCY-6-STANDBY_HAS_RELOADED: The Standby [chars] has reloaded; reason: [chars] Explanation The standby peer reloaded itself to correct a configuration mismatch between the active

system and the standby peer. The standby peer detected that it is missing the configuration for a line card. This situation probably occurred because the standby peer was reloaded before the new card was inserted. Recommended Action No action is required.

Error Message %REDUNDANCY-6-SWITCHOVERTIME: Time taken to switchover = [dec] milliseconds Explanation This message displays the time elapsed for the standby peer to become active following

a failure of the existing active system. Recommended Action No action is required.

REDUNDANCY_UTILS Messages This section contains high availability redundancy utilities messages.

Error Message %REDUNDANCY_UTILS-3-INVALID_UNIT_DESIGNATION: An invalid redundancy designation ([chars]) has been detected. Explanation The redundancy utility assigns each system a unit designation of either active unit,

standby unit, or other unit. This designation was found to be invalid in the run-time module associated with the system traceback message. This condition most likely occurred because of a software error. The message text provides more information on the specific cause of the error. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1236

REGISTRY Messages

REGISTRY Messages This section contains registry-related (REGISTRY) messages.

REGISTRY-2 Error Message %REGISTRY-2-REG_FLAG_DEADLOCK: Registry call to [chars] timed out due to deadlock Explanation When a remote registry is not serviced within 25 seconds, the remote process (and

presumably the entire system) is deadlocked. This message is printed when the deadlock is broken by a timeout. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %REGISTRY-2-REG_PARSE_ERROR: [chars]: Could not parse notification [chars] : error/no. of items = [dec] Explanation The registry library is unable to parse a notification that was received from a name

server. This condition could exist for several reasons: - There is a bug in the sscanf function. - The notification block is corrupted. - The pathname published to the name server is invalid. This issue is serious and affects interprocess communications. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1237

REGISTRY Messages

REGISTRY-3 Error Message %REGISTRY-3-FASTCASE_OUT_OF_BOUNDS: Attempt made in [chars] to register with out of bounds key. Explanation In FASTCASE registry, the key must be smaller than the size specified when the registry was created. An attempt was made to register with a key that is out of bounds. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %REGISTRY-3-REG_FLAG_ERR: Invalid combination of registry flag and scheduler control : [chars] Explanation Process blocking has been disabled using either the raise_interrupt_level or the

assign_blocking_disabled process. As a result of this action, a remote registry that contains the reg_flag_data_safe or reg_flag_peer flag has been invoked. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %REGISTRY-3-REG_SUSPEND: Registry of type SUSPEND called when suspends are not allowed. Explanation Process blocking has been disabled using either the raise_interrupt_level or the

assign_blocking_disabled process. As a result of this action, a remote registry of the suspend type has been invoked. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1238

REGISTRY Messages


Error Message %REGISTRY-3-REG_XDR: [chars] Explanation An error occurred while processing a parameter to a remote (interprocess) registry call. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %REGISTRY-3-SEQ_LIST_OVERWRITE: Attempt made to overwrite a set sequence function (%s) Explanation A single function can be set as a callback for a specified sequence number for a

sequenced list registry. An attempt to set a new callback failed because a callback function has already been set for this sequence number. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1239

REMOTE_OIR_ISSU Messages

REMOTE_OIR_ISSU Messages This sections contains remote online insertion and removal (OIR) in-service software upgrade (ISSU) messages.

REMOTE_OIR_ISSU-3 Error Message %REMOTE_OIR_ISSU-3-BUFFER: Cat6K Remote OIR ISSU client failed to a buffer for message, error %d Explanation The remote OIR ISSU client failed to get a buffer for building a negotiation message. As a result, the client cannot send a negotiation message and the standby unit cannot be brought up. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %REMOTE_OIR_ISSU-3-CAPABILITY: Cat6K Remote OIR ISSU client %s Explanation The remote OIR ISSU client detected an error during capability negotiation. As a result, there is a mismatch in the client capability between the active and standby unit. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1240


Error Message %REMOTE_OIR_ISSU-3-INIT: Cat6K Remote OIR ISSU client initialization failed at %s, error %s Explanation The remote OIR ISSU client could not be initialized. This condition will cause a



Error Message %REMOTE_OIR_ISSU-3-MSG_NOT_OK: Cat6K Remote OIR ISSU client message %d is not compatible Explanation The remote OIR ISSU client received an incompatible message from the peer unit. The



Error Message %REMOTE_OIR_ISSU-3-MSG_SIZE: Cat6K Remote OIR ISSU client failed to get the message size for message %d Explanation The remote OIR ISSU client was unable to calculate the message size for the message




1241


Error Message %REMOTE_OIR_ISSU-3-POLICY: Cat6K Remote OIR ISSU client message type %d is %s Explanation The remote OIR ISSU client received a message type that it does not support. A policy



Error Message %REMOTE_OIR_ISSU-3-SEND_FAILED: Cat6K Remote OIR ISSU client failed to send a negotiation message, error %d Explanation The remote OIR ISSU client could not send a session negotiation message to the peer.



Error Message %REMOTE_OIR_ISSU-3-SESSION: Cat6K Remote OIR ISSU client %s Explanation The remote OIR ISSU client detected an error during a session negotiation with the peer unit. As a result, the standby unit cannot be brought up. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1242

REP Messages

Error Message %REMOTE_OIR_ISSU-3-TRANSFORM: Cat6K Remote OIR ISSU client %s transform failed, error %s Explanation The remote OIR ISSU client could not transform the message. If the transmit

transformation failed, the checkpoint message cannot be sent to the standby unit. If the receive transformation failed, the checkpoint message cannot be applied on the standby unit. In either case, the OIR state of the bay will not be identical with the active unit. Recommended Action Copy the message exactly as it appears on the console or in the system log.


REP Messages This sections contains Resilient Ethernet Protocol (REP) messages.

REP-4 Error Message %REP-4-LINKSTATUS: %s (segment %d) is %s Explanation The Resilient Ethernet Protocol (REP) link status has changed. If the status changed to nonoperational, a reason is displayed. Recommended Action No action is required.

REP-5 Error Message %REP-5-PREEMPTIONFAIL: can not perform preemption on segment %d due to %s Explanation A Resilient Ethernet Protocol (REP) preempt operation failed. The failure could be

caused by specifying an invalid port ID or neighbor number with the rep preempt block port command or by configuring the rep preempt block port preferred command while no REP port is configured with a preferred flag. Recommended Action Correct the configuration and run REP manual preemption on the primary edge

port by entering the rep preempt segment command.


1243

REP_ISSU Messages

REP_ISSU Messages This sections contains Resilient Ethernet Protocol (REP) in-service software upgrade (ISSU) messages.

REP_ISSU-3 Error Message %REP_ISSU-3-BUFFER: REP ISSU client failed to get buffer for message, error %d Explanation The Resilient Ethernet Protocol (REP) ISSU client was unable to get buffer space for

building a negotiation message. As a result, it cannot send the negotiation message to the standby unit and the standby unit cannot be brought up. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %REP_ISSU-3-CAPABILITY: REP ISSU client %s Explanation The REP ISSU client detected an error during capability negotiation. As a result, there is a mismatch in the client capability between the active and standby unit. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1244

REP_ISSU Messages

Error Message %REP_ISSU-3-INIT: REP ISSU client initialization failed at %s, error %s Explanation The REP ISSU client could not be initialized. This condition will cause a catastrophic

failure when an ISSU upgrade or downgrade is performed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %REP_ISSU-3-MSG_NOT_OK: REP ISSU client message %d is not compatible Explanation The REP ISSU client received an incompatible message from the peer unit. The



Error Message %REP_ISSU-3-MSG_SIZE: REP ISSU client failed to get the message size for message %d Explanation The REP ISSU client was unable to calculate the message size for the message

specified. The REP ISSU client will be unable to send the message to the standby unit. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1245

REP_ISSU Messages

Error Message %REP_ISSU-3-POLICY: REP ISSU client message type %d is %s Explanation The REP ISSU client received a message type that it does not support. A policy is



Error Message %REP_ISSU-3-SEND_FAILED: REP ISSU client failed to send a negotiation message, error %d Explanation The REP ISSU client could not send a session negotiation message to the peer. As a

result, the standby unit cannot be brought up. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %REP_ISSU-3-SESSION: REP ISSU client %s Explanation The REP ISSU client detected an error during a session negotiation with the peer unit.




1246

REP_ISSU Messages

Error Message %REP_ISSU-3-SESSION_UNREGISTRY: REP ISSU client failed to unregister session information. Error: %d (%s) Explanation The REP ISSU client was unable to unregister session information. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %REP_ISSU-3-TRANSFORM: REP ISSU client %s transform failed, error %s Explanation The REP ISSU client could not transform the message. If the transmit transformation

failed, the checkpoint message cannot be sent to the standby unit. If the receive transformation failed, the checkpoint message cannot be applied on the standby unit. In either case, the port manager state will not be identical with the active unit. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1247

RESETMGR Messages

RESETMGR Messages This sections contains reset manager messages.

RESETMGR-3 Error Message %RESETMGR-3-NOMEM: Failed to allocate memory to add ID (%d) to table Explanation The reset manager was unable to allocate memory to add the unique ID and process

name to its table. If this process is restarted on the active system, the standby system might not be reset due to this error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %RESETMGR-3-RESET: Reset Manager has reset the system due to ’%s’ process restart

The standby system is being forced to reset by the reset manager. The reset manager stores a set of IDs, each of which uniquely identifies a process on the system. If one of these monitored processes is restarted, the standby unit will be reset so that the versioning infrastructure can renegotiate. This is not a software fault.

Explanation

Recommended Action No action is required.

Error Message %RESETMGR-3-RESET_UNKNOWN: A restarted process could not be identified by its Job ID, the Reset Manager has reset the Standby system. Explanation The reset manager stores a set of IDs, each of which uniquely identifies a process on the

system. A process was restarted but it could not be uniquely identified by its job ID. Because it cannot be determined whether the restarted process was being monitored by the reset manager, the standby system is being reset. This is probably due to a software fault on the system. Recommended Action No action is required.


1248

RESETMGR Messages

Error Message %RESETMGR-3-SYSMGR_JOBID_LOOKUP: Failed to get the job ID of the Reset Manger (IOS blob) from SysMgr Explanation The reset manager was unable to get its job ID from the system manager. The reset

manager cannot function without this information and will suspend any further initialization. Recommended Action Copy the message exactly as it appears on the console or in the system log.


RESETMGR-4 Error Message %RESETMGR-4-SYSMGR_PROCNAME_LOOKUP: Failed to lookup process name from SysMgr, job ID = %d Explanation The reset manager was unable to get the name of the process with the specified job ID

from the system manager. Although this is a system manager error, the system can continue to operate normally because the process name is used only for reference purposes. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1249

RF Messages

RF Messages This sections contains redundancy facility (RF) messages.

RF-3 Error Message %RF-3-CANNOT_SWITCH: Cannot switchover; the peer Route Processor (RP) is not available Explanation Cannot initiate switchover. The peer RP is not available. Recommended Action This is an informational message only. No action is required.

Error Message %RF-3-CANT_GET_VERSION: Cannot get version info from peer Route Processor (RP); the RP software is incompatable. Explanation The standby RP cannot get version information from the peer RP. The likely cause is incompatible software. Recommended Action Ensure that the same software image is running on both RPs.

Error Message %RF-3-FAILED_SET_RED_MODE: ACTIVE failed to set redundancy mode. STANDBY has selected mode but unable to get confirmation from ACTIVE. Explanation Under normal conditions, the standby RP selects the redundancy mode and sends its

decision to the active RP. The active RP uses it to determine the system mode and returns the final decision on the mode to the standby RP. This system message indicates that the exchange has failed, and the standby RP does not have the right redundancy mode to proceed. Recommended Action Allow the standby RP to reset once. If the problem persists, verify that all

modules are working properly.

Error Message %RF-3-NEGOTIATED_ROLE_MISMATCH: Negotiated Role mismatch; The Route Processor (RP) believes it should be ACTIVE while the System Processor (SP) believes the RP should be STANDBY... or vice versa. Explanation The RP negotiates its role (active or standby) at boot time. If the other RP is running an image that does not contain role negotiation code, then the role that is negotiated may not be valid. When this occurs, the RP detecting a mismatch between the role specified by the SP and the role negotiated will be rebooted. Recommended Action Ensure that the same software image is running on both RPs. Make sure that

neither RP is running the bootloader image.


1250

RF Messages

Error Message %RF-3-NON_HA_SWITCHOVER: The SP switchover was NOT stateful. To support SSO on the RP, the SP must be configured with HA enabled. Explanation The switch processor switchover that occurred was not stateful. Stateful switchover

(SSO) mode on the route processor requires the switch processor to run with high availability enabled to ensure that appropriate state is synchronized between the switch processors and that there is sufficient state information on the new active switch processor to support the switchover of the route processor while in stateful switchover mode. Because there is insufficient state to support a route processor switchover in stateful switchover mode, the recovery is to reset the route processor and reboot it. Recommended Action Configure the SP to enable HA. If HA is enabled, it is possible that resource

exhaustion (such as memory) might have caused this non-HA switchover. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %RF-3-NOTIF_TID: Notification timer extended for the wrong client, cur-client=%d, req-client=%d Explanation The current redundancy facility (RF) client attempted to extend the RF notification timer using a client ID other than its own. This is an internal software error. The message text on the console or in the system log contains error details such as the current client ID number and the requested client ID number. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show redundancy history commands and your pertinent troubleshooting logs.

Error Message %RF-3-PEER_RP_RELOAD: The peer Route Processor (RP) is being reset because [chars] Explanation This message provides the reason that the peer RP reset. The peer RP resets in an attempt to recover from an indeterminate state. Recommended Action If the condition persists after the reset, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will


1251

RF Messages

supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %RF-3-VERSION_MISMATCH: Version Info mismatch; Not running same version of software on each Route Processor (RP). Cannot run in SSO mode; will go to RPR mode instead. Explanation Each RP must be running the same version of software. The version check indicates that

there is a version mismatch. As a result, the RPs cannot run in SSO (hot-standby) mode and operation will regress to RPR mode. Recommended Action Ensure that both RPs are running the same software image.

Error Message %RF-3-WAKEUP_STANDBY_NOT_SEEN: Active-Standby RP Handshake Error. The Standby RP did not receive a WAKEUP_STANDBY message from the Active RP during the early initialization phase on the Standby RP. Explanation As part of the early initialization phase, the standby RP requests that the active RP

notify it when the active RP is ready to support the standby RP. The active RP has failed to wake the standby RP. The active RP may have failed during the standby RP’s early initialization phase or some other error has prevented the active RP from completing this handshake. Recommended Action The standby RP will be restarted. If the problem persists, restart the system.

RF-4 Error Message %RF-4-MEMORY_SIZE_MISMATCH: Memory Size mismatch: The redundant Route Processors have different memory configurations. To support the High Availability feature, it is recommended that both RPs have the same memory configurations. Explanation To support the high availability feature, it is recommended that both redundant route processors have the same memory configuration. Recommended Action Install the same amount of memory on both RPs.


1252

RF Messages

RF-5 Error Message %RF-5-RF_RELOAD: %s. Reason: %s Explanation The current redundancy facility (RF) has invoked a reload. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show redundancy history reload commands and your pertinent troubleshooting logs.

Error Message %RF-5-RF_TERMINAL_STATE: Terminal state reached for (%s) Explanation The current redundancy facility (RF) has reached a terminal state for the operating

mode. Recommended Action This is a notification message only. No action is required.

Error Message %RF-5-SEND_FAIL: RF client progression send failure for reason (%s) Explanation The current redundancy facility (RF) failed to send a client progression to the standby

client. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show redundancy history commands and your pertinent troubleshooting logs.


1253

RF Messages

RF-6 Error Message %RF-6-CONS_MSG: Console Message from [chars] RP: [chars] Explanation This message is a console message from the peer RP. Recommended Action This is an informational message only. No action is required.

Error Message %RF-6-NEGOTIATED_RED_MODE: Negotiated Redundancy MODE is [chars] Explanation The negotiated redundancy mode may be either SSO or RPR. Recommended Action This is an informational message only. No action is required.

Error Message %RF-6-STANDBY_READY: The Standby RP has reached HOT-STANDBY state and is now ready for stateful switchover. Explanation The standby RP has reached the hot-standby state and is now ready to take over operation in the event that the active RP should fail. Recommended Action No action is required.

RF-7 Error Message %RF-7-KPA_WARN: RF KPA messages have not been heard for [dec] seconds Explanation RF keepalive messages have not been sent from the peer. This message is posted after

every third KPA timer expiry. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1254

RF_ISSU Messages

RF_ISSU Messages This sections contains redundancy facility (RF) in-service software upgrade (ISSU) messages.

RF_ISSU-3 Error Message %RF_ISSU-3-CAPENTRY_REG: RF Cap Entry ([dec]) for Entity ([dec]) Registration failed Explanation A capability entry could not be registered for the RF ISSU. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show issu capability entries command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %RF_ISSU-3-CAPGROUP_REG: RF Cap Group ([dec]) for Entity ([dec]) Registration failed Explanation A capability group could not be registered for the RF ISSU. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show capability groups command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %RF_ISSU-3-CAP_REG: RF cap reg failed: reason [dec] Explanation The capabilities of the RF ISSU could not be registered. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show issu capability arguments command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at


1255

RF_ISSU Messages


Error Message %RF_ISSU-3-CAPTYPE_REG: RF Cap Type for Entity ([dec]) Registration failed Explanation A capability type could not be registered for the RF ISSU. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show issu capability types command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %RF_ISSU-3-CLIENT_REG: RF Client ([dec]) Registration failed Explanation The RF ISSU client could not be registered. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %RF_ISSU-3-CLIENT_REG_FAILED: RF ISSU client ([dec]) Client registration failed. [chars] Explanation The RF ISSU client could not be registered during system initialization. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show issu clients command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,


1256

RF_ISSU Messages


Error Message %RF_ISSU-3-ENTITY_REG: RF Entity ([dec]) Registration failed Explanation The RF ISSU entity could not be registered. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show issu entities command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %RF_ISSU-3-GET_BUFFER: RF ISSU session ([dec]) failed to get buffer Explanation The RF ISSU failed to get a buffer. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %RF_ISSU-3-MSG_DATAPTR: RF Client ([dec]) get msg dataptr failed. Error = [dec] Explanation The RF ISSU client could not obtain a message data pointer. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show issu fsm command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support


1257

RF_ISSU Messages


Error Message %RF_ISSU-3-MSGGROUP_REG: RF Msg Group ([dec]) for Entity ([dec]) Registration failed Explanation The message group for the RF ISSU could not be registered. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show issu message groups command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %RF_ISSU-3-MSG_MTU: RF Client ([dec]) get msg mtu failed. Error = [dec] Explanation The RF ISSU client could not obtain message size. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %RF_ISSU-3-MSG_REG: RF msg reg failed: reason [dec] Explanation Messages for the RF ISSU could not be registered. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show issu message arguments command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support


1258

RF_ISSU Messages


Error Message %RF_ISSU-3-MSG_SEND: RF ISSU client for session ([dec]) failed to send message Explanation The RF ISSU client could not send a negotiation message to a peer. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %RF_ISSU-3-MSGTYPE_REG: RF Msg Type for Entity ([dec]) Registration failed Explanation The message type for the RF ISSU could not be registered. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show issu message types command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %RF_ISSU-3-RF_MSG_NOT_OK: RF ISSU msg type ([dec]) is not ok Explanation RF ISSU message type has not negotiated correctly. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show message types Client_ID command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support


1259

RF_ISSU Messages


Error Message %RF_ISSU-3-SESSION_REG: RF session for Entity ([dec]) Registration failed Explanation The RF ISSU session could not be registered. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %RF_ISSU-3-SESSION_UNREG: RF session ([dec]) Un-Registration failed Explanation The RF ISSU session could not be unregistered. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1260

RFS Messages

RFS Messages This section contains remote file system messages.

RFS-3 Error Message %RFS-3-CAPENTRY_REG: RFS Cap Entry ([dec]) for Entity ([dec]) Registration failed Explanation RFS ISSU cap entry registration has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show issu capability entries command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %RFS-3-CAPGROUP_REG: RFS Cap Group ([dec]) for Entity ([dec]) Registration failed Explanation RFS ISSU cap group registration has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show issu capability groups command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %RFS-3-CAPTYPE_REG: RFS Cap Type for Entity ([dec]) Registration failed Explanation RFS ISSU cap type registration has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show issu capability types command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying


1261

RFS Messages


Error Message %RFS-3-CLIENT_REG: RFS Client ([dec]) Registration failed Explanation RFS ISSU client registration has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show issu clients command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %RFS-3-CLIENT_SESSION_REG: RFS ISSU client shared msg session for entity ([dec]) registration failed Explanation RFS ISSU client shared message session registration has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show issu sessions command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %RFS-3-CLIENT_SESSION_UNREG: RFS session ([dec]) Un-Registration failed Explanation RFS ISSU client session unregistration has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show issu sessions command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at


1262

RFS Messages


Error Message %RFS-3-CREATE_ACTIVE_PORT: RFS create active port ([chars]) failed Explanation RFS ISSU active port creation has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show ipc port command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %RFS-3-CREATE_CLIENT_PORT: RFS create client port (%s) failed Explanation The remote file system (RFS) ISSU client was unable to create a client port. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show ipc port commands and your pertinent troubleshooting logs.

Error Message %RFS-3-CREATE_SERVER_PORT: RFS create server port (%s) failed Explanation The RFS ISSU client was unable to create a server port. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1263

RFS Messages

following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show ipc port commands and your pertinent troubleshooting logs.

Error Message %RFS-3-CREATE_STANDBY_PORT: RFS create standby port ([chars]) failed Explanation RFS ISSU standby port creation has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %RFS-3-ENTITY_REG: RFS Entity ([dec]) Registration failed Explanation RFS ISSU entity registration has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show issu entities command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %RFS-3-IPC_GET_BUFFER: RFS issu ipc get buffer failed Explanation RFS ISSU IPC get buffer has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show issu command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


1264

RFS Messages

Error Message %RFS-3-LOCATE_PORT: RFS locates port ([chars]) failed Explanation RFS ISSU port location has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %RFS-3-MSGGROUP_REG: RFS Msg Group ([dec]) for Entity ([dec]) Registration failed Explanation RFS ISSU message group registration has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show issu message groups command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %RFS-3-MSG_MTU: RFS Client ([dec]) get msg mtu failed. Error = [dec] Explanation RFS ISSU client get message MTU has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show issu fsm command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


1265

RFS Messages

Error Message %RFS-3-MSG_RCV: RFS Client ([dec]) receive msg failed. Error = [dec] Explanation RFS ISSU client receive message has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %RFS-3-MSGTYPE_REG: RFS Msg Type for Entity ([dec]) Registration failed Explanation RFS ISSU message type registration has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show issu message types command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %RFS-3-MSG_XMIT: RFS Client ([dec]) send msg failed. Error = [dec] Explanation RFS ISSU client send message has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1266

RFS Messages

Error Message %RFS-3-NEGO_COMP: RFS nego is not compatible ([dec]) Explanation RFS ISSU start shared negotiation session has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %RFS-3-NEGO_SESSION_REG: RFS nego session for Entity ([dec]) Registration failed Explanation RFS ISSU shared negotiation session registration has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %RFS-3-NEGO_SESSION_UNREG: RFS session ([dec]) Un-Registration failed Explanation RFS ISSU shared negotiation session unregistration failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1267

RFS Messages

Error Message %RFS-3-OPEN_ACTIVE_PORT: RFS open active port ([chars]) failed Explanation The RFS ISSU client was unable to open an active port. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %RFS-3-OPEN_CLIENT_PORT: RFS open client port (%s) failed Explanation The RFS ISSU client was unable to open a client port. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %RFS-3-OPEN_SERVER_PORT: RFS open server port (%s) failed Explanation The RFS ISSU client was unable to open a server port. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1268

RFS Messages

Error Message %RFS-3-OPEN_STANDBY_PORT: RFS open standby port ([chars]) failed Explanation The RFS ISSU client was unable to open a standby port. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %RFS-3-RECEIVE_NEGO_FAILED: RFS receive nego message ([dec]) failed Explanation RFS ISSU receive negotiation message has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %RFS-3-RECEIVE_NEGO_NOT_DONE: RFS receive nego message is not done ([dec]) Explanation RFS ISSU receive negotiation message is not done. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1269

RFS Messages

Error Message %RFS-3-REG_PORT: RFS reg port ([dec]) failed Explanation RFS ISSU register port has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %RFS-3-RFS_BOOL_CREATE_ERR: %s. Explanation The RFS redundancy facility (RF) client detected an error when creating a watched

boolean. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %RFS-3-RFS_ISSU_NEGO_PROCESS: RFS create rfs_issu_start_port watch boolean failed Explanation RFS ISSU create negotiation process has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1270

RFS Messages

Error Message %RFS-3-RFS_ISSU_START_PORT: RFS create rfs_issu_start_port watch boolean failed Explanation The RFS ISSU client was unable to create anrfs_issu_start_port watched boolean. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %RFS-3-RFS_ISSU_START_SESSION: RFS create rfs_issu_start_session watch boolean failed Explanation The RFS ISSU client was unable to create anrfs_issu_start_session watched boolean. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %RFS-3-RFS_RF_PROG_ERR: %s %d. Explanation The RFS RF client detected an error. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1271

RFS Messages

Error Message %RFS-3-RFS_RF_PROG_NOT_SENT_ERR: %s. Explanation The RFS RF client detected an error when sending a client progression. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %RFS-3-SEND_NEGO_MESSAGE: RFS send nego message ([dec]) failed Explanation RFS ISSU send negotiation message has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %RFS-3-START_NEGO_SESSION: RFS start shared nego session ([dec]) failed: [dec] Explanation RFS ISSU start shared negotiation session has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1272

RFS_ISSU Messages

Error Message %RFS-3-UNREG_ENTITY: RFS ISSU Client unreg entity failed. Explanation The RFS ISSU client unregister entity has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


RFS_ISSU Messages This section contains remote file system in-service software upgrade (ISSU) messages.

RFS_ISSU-3 Error Message %RF_ISSU-3-INVALID_SESSION: RF ISSU client does not have a valid registered session. Explanation The redundancy facility (RF) ISSU client does not have a valid registered session. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %RF_ISSU-3-RF_CAP_INVALID_SIZE: RF ISSU client capability list is empty. Explanation The RF ISSU capability list is empty, which is an invalid condition. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1273

RITE Messages

open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show issu capability entries commands and your pertinent troubleshooting logs.

Error Message %RF_ISSU-3-RF_CAP_RESULT_INCOMP: RF ISSU client capability exchange result incompatible. Explanation Based on the results of the capability exchange, the RF ISSU client is not compatible with the peer. Recommended Action Copy the message exactly as it appears on the console or in the system log.


RITE Messages This sections contains IP traffic export messages.

RITE-5 Error Message %RITE-5-ACTIVATE: Activated IP traffic export on interface [chars] Explanation IP traffic export has been enabled on the specified interface. Recommended Action No action is required.

Error Message %RITE-5-DEACTIVATE: Deactivated IP traffic export on interface [chars] Explanation IP traffic export has been disabled on the specified interface. Recommended Action No action is required.


1274

RMON Messages

Error Message %RITE-5-MODIFIED: Changed IP traffic export outbound interface from [chars] to [chars] Explanation The outbound interface for IP traffic export has been changed. Recommended Action No action is required.

RMON Messages This section contains Remote Monitoring (RMON) messages.

RMON-5 Error Message %RMON-5-HCFALLINGTRAP: Falling trap is generated because the value of %s has fallen below the falling-threshold hc value %llu Explanation A falling trap was generated. The value of the specified MIB object fell below the falling threshold value as configured by the rmon hc-alarms command for the specified object. Recommended Action Take the appropriate action on the specified MIB object.

Error Message %RMON-5-HCRISINGTRAP: Rising trap is generated because the value of %s exceeded the rising-threshold hc value %llu Explanation A rising trap was generated. The value of the specified MIB object exceeded the rising

threshold value as configured by the rmon hc-alarms command for the specified object. Recommended Action Take the appropriate action on the specified MIB object.

ROllBACK-ISSU Messages ROLLBACK-ISSU-2 Error Message %ROLLBACK_ISSU-2-GET_BUFFER: Rollback ISSU client failed to get buffer for message. Error: [dec] ([chars]) Explanation The Rollback ISSU client failed to get buffer space for building a negotiation message. A negotiation message cannot be sent to the standby device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly. Recommended Action Issue the show logging and show checkpoint client command to gather data

that may help identify the nature of the error. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance,


1275

ROllBACK-ISSU Messages


Error Message %ROLLBACK_ISSU-2-INIT: Rollback ISSU client initialization failed to [chars]. Error: [dec] ([chars]) Explanation The Rollback ISSU client could not be initialized. This initialization failure must be

addressed before in-service software upgrade or downgrade can be performed successfully. If you do not address this failure, there will be downtime during software upgrade or downgrade. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %ROLLBACK_ISSU-2-SEND_NEGO_FAILED: Rollback ISSU client failed to send negotiation message. Error: [dec] ([chars]) Explanation The Rollback ISSU client failed to send a session negotiation message to the peer device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly. Recommended Action Issue the show logging and show checkpoint client command to gather data

that may help identify the nature of the error. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message %ROLLBACK_ISSU-2-SESSION_NEGO_FAIL_START: Failed to start Rollback ISSU session negotiation. Error: [dec] ([chars]) Explanation The Rollback ISSU client failed to start session negotition. If a problem occurs with the

ISSU session start, the standby device cannot be brought up properly. Recommended Action Copy the error message exactly as it appears on the console or in the system



1276

ROllBACK-ISSU Messages

Error Message %ROLLBACK_ISSU-2-SESSION_REGISTRY: Rollback ISSU client failed to register session information. Error: [dec] ([chars]) Explanation The Rollback ISSU client failed to register session information. If a problem occurs with the ISSU session registration, the standby device cannot be brought up properly. Recommended Action Issue the show issu capability entries and show issu session and show issu negotiated capability command to gather data that may help identify the nature of the error. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

ROLLBACK-ISSU-3 Error Message %ROLLBACK_ISSU-3-INVALID_SESSION: Rollback ISSU client does not have a valid registered session. Explanation The Rollback ISSU client does not have a valid registered session. Recommended Action Issue the show issu capability entries and show issu session and show issu negotiated capability command to gather data that may help identify the nature of the error. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message %ROLLBACK_ISSU-3-MSG_NOT_OK: Rollback ISSU client ’Message Type [dec]’ is not compatible Explanation The Rollback ISSU client received an incompatible message from the peer device. The

message cannot be processed. Recommended Action Issue the show issu message group and show issu session and show issu

negotiated version command to gather data that may help identify the nature of the error. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.


1277

ROUTEMAP Messages

Error Message %ROLLBACK_ISSU-3-MSG_SIZE: Rollback ISSU client failed to get the MTU for Message Type [dec].Error: [dec] ([chars]) Explanation The Rollback ISSU client failed to calculate the MTU for the specified message. The

Rollback ISSU client is not able to send the message to the standby device. Recommended Action Issue the show issu message group and show issu session and show issu negotiated version command to gather data that may help identify the nature of the error. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message %ROLLBACK_ISSU-3-SESSION_UNREGISTRY: Rollback ISSU client failed to unregister session information. Error: [dec] ([chars]) Explanation The Rollback ISSU client failed to unregister session information. Recommended Action Issue the show issu capability entries and show issu session and show issu negotiated capability command to gather data that may help identify the nature of the error. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message %ROLLBACK_ISSU-3-TRANSFORM_FAIL: Rollback ISSU client [chars] transform failed for ’Message Type [dec]’. Error: [dec] ([chars]) Explanation The Rollback ISSU client could not transform the specified message type. If the transmit transformation failed, the checkpoint message was not sent to the standby device. If the receive transformation failed, the checkpoint message was not applied on the standby device. In both cases, the Rollback state between the active device and the standby device is not identical. Recommended Action Issue the show issu session and show issu negotiated version command to

gather data that may help identify the nature of the error. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

ROUTEMAP Messages This section contains route map messages.


1278

RPC Messages

ROUTEMAP-4 Error Message %ROUTEMAP-4-BADTRACKOBJECTTYPE: can’t track this type of object Explanation Route maps only support STATE type track objects. This object is not a STATE object. Recommended Action Reconfigure the track object to make it a STATE object.

RPC Messages This section contains Remote Procedure Call (RPC) messages.

RPC-2 Error Message %RPC-2-6: Recovered from RPC send failure for request [chars]. Resending request. Explanation A communication error occurred during an RPC request. RPC will retry. Recommended Action This is an informational message only. No action is required.

Error Message %RPC-2-CORE_SAT_RPC_FAIL: RPC between Core and Remote Switch - [chars] failed (non-fatal)Expected when VSL goes down Explanation A nonfatal communication error occurred during an RPC request between the core and

a remote switch or vice versa. This error message is not considered a failure when the virtual switch link (VSL) goes down. Recommended Action No action is required.

Error Message %RPC-2-FAILED: Failed to send RPC request [chars] (fatal) Explanation A fatal communication error occurred during an RPC request. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1279

RPF Messages

Error Message %RPC-2-FAILED_RETRY: Failed to send RPC request [chars] (will try again) Explanation A communication error occurred during an RPC request. The system will attempt the

RPC request again. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %RPC-2-FAILED_USERHANDLE: Failed to send RPC request [chars] Explanation A communication error occurred during an RPC request. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %RPC-2-RETRY: Recovered from RPC send failure for request [chars]. Resending request. Explanation A communication error occurred during an RPC request. Recommended Action The RPC will retry the request. If the message recurs, copy the message exactly


RPF Messages This section contains multicast Reverse Path Forwarding (RPF) messages.


1280

RPF Messages

RPF-3 Error Message %RPF-3-RTAVLDELETE: Error deleting an rpf entry from the multicast rpf tree Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %RPF-3-RTAVLINSERT: Error inserting a new rpf entry into the multicast rpf tree Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


RPF-4 Error Message %RPF-4-AVLDELETE: Error deleting an rpf entry from the multicast rpf tree Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1281

RP_MLP Messages


Error Message %RPF-4-AVLINSERT: Error inserting a new rpf entry into the multicast rpf tree Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %RPF-4-SNMP_RADIX_ERR: Failed to [chars] snmp node [chars] snmp radix tree for multicast group (*, [IP_address]). Explanation An error occured while adding or deleting snmp node in snmp radix tree when mroute

is created or deleted. Recommended Action Copy the error message exactly as it appears on the console or in the system


RP_MLP Messages This section contains route processor Multilink Point-to-Point Protocol (RP_MLP) messages.

RP_MLP-3 Error Message %RP_MLP-3-ADJ_FAIL: Adjacency walk for [chars] failed Explanation An adjacency update for the specified multilink interface failed. Recommended Action Reset the multilink interface by entering the shutdown command followed by

the no shutdown command on the interface. If traffic does not resume, collect the output of the show adjacency internal and show cef interface internal commands. Copy the message exactly as it


1282

RP_MLP Messages


Error Message %RP_MLP-3-INCOMPATIBLELINK: The current config cannot be supported as link([chars]) [chars] for bundle ([chars]) Explanation When using multilink, the following restrictions must be met:

- All the links should be from the same port. - Non-channelized T3 interfaces are not supported on multilink. - Any added link should be compatible with the existing links in the bundle. - All the links should be distributed. Recommended Action Modify the configuration so that the restrictions are not violated.

Error Message %RP_MLP-3-UNSUPPORTEDCONFIG: The current config cannot be supported as [chars] for [chars] Explanation When using multilink on hardware-assisted SPAs, the maximum number of links in the

bundle and number of bundles should not exceed the maximum permissible by device. Refer to the product documentation for restrictions. Recommended Action Modify the configuration so that it does not violate the restrictions.

RP_MLP-4 Error Message %RP_MLP-4-DLFIONELINKSUPPORT: Only ONE link should be configured for dLFI bundle!! Explanation The system attempted to configure more than one link for the Distributed Link

Fragmentation and Interleaving (dLFI) bundle interface. The dLFIoFR and the dLFIoATM do not support configuring more than one link. Recommended Action No action is required.


1283

RSP Messages

RP_MLP-5 Error Message %RP_MLP-5-SPAWARNING: Feature support switching to LC based software for [chars] as [chars] Explanation A link was added to the bundle, but it is not on the same bay as other member links of the bundle. The specified link that is not on the same bay has become active, and the bundle has been switched to line card-based software support instead of the hardware mode that is supported on FREEDM. Recommended Action When a link is added to a bundle, ensure that it is on the same bay as the other member links of the bundle, in order to have the MLP bundle in hardware mode supported on FREEDM.

RSP Messages This section contains Route Switch Processor (RSP) messages.

RSP-3 Error Message %RSP-3-NORELOAD: reload command not allowed on standby RSP Explanation The reload command in privileged EXEC mode is not allowed on the standby RSP. Recommended Action Enter the slave reload command in privileged EXEC mode to reload the

standby RSP.

Error Message %RSP-3-PA_INIT: Malloc to [chars] failed for slot [dec] bay [dec] Explanation The information structure for the port adapter could not be created. The interfaces on

the specified port adapter might no longer be functional. A possible reason for this is a memory allocation failure involving the port adapter. This can occur as a result of insufficient hardware memory or a memory leak. Recommended Action Confirm that the recommended amount of memory is installed for the platform.

If memory is adequate, obtain the output of the show process memory command over time to determine the process using increased memory. As an immediate possible solution, attempt to reseat the line card. If this condition persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


1284

RSVP Messages

RSP-4 Error Message %RSP-4-CRASHINFO: Error saving crashinfo for slot [dec]. Reason: [chars] Explanation A VIP crash information file has not been saved due to the indicated reason. Recommended Action If the reason indicates Out of space, the bootflash may not have sufficient

memory to save the crashinfo file. Otherwise, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

RSP-6 Error Message %RSP-6-TXSTUCK: Txacc of Interface [chars] is at [dec]% of its txlimit Explanation The specified interface has a low TXACC value. This might be a transient condition and

might be harmless if it occurs during periods of high packet traffic. If this condition is detected more than once during periods of relatively moderate traffic, it could indicate a problem. Distributed packet switching might be disrupted as a result of this condition. Recommended Action If the message recurs during periods of relatively moderate traffic, this might indicate a disruption in distributed packet switching. If such a disruption occurs, enter the microcode reload command to recover. Open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

RSVP Messages This section contains RSVP protocol messages.


1285

RSVP Messages

RSVP-1 Error Message %RSVP-1-RSVP_AUTH_NO_KEYS_LEFT: No valid keys left for [IP_address] Explanation The router attempted to use a key in an RSVP key chain but discovered that all the keys

in the chain have expired and no other per-neighbor or per-interface keys are available for the specified neighbor. The router will continue to use the last key in the chain rather than revert to an unauthenticated condition. However, the specified neighbor router may start discarding RSVP messages as a result, and reservations with that neighbor may eventually time out. Recommended Action Update the key chain by updating the text and expiration times for the expired

keys.

RSVP-2 Error Message %RSVP-2-RSVP_AUTH_KEY_CHAIN_EXPIRED: All the keys in chain [chars] have expired - please update the key chain now Explanation The router attempted to use a key in an RSVP key chain but discovered that all the keys

in the chain have expired. The router will attempt to find another suitable key. If no other suitable per-neighbor key can be found, the router will attempt to use key (chain) configured for the interface over which the authenticated RSVP message is being sent or received. Recommended Action Update the key chain by updating the text and expiration time(s) for the expired

key(s).

RSVP-3 Error Message %RSVP-3-BAD_RSVP_MSG_RCVD_AUTH_COOKIE: [chars] message from [IP_address] discarded - challenge failed for key ID [chars] Explanation The router sent an RSVP message to challenge the untrusted source to compute a secure

hash on a random piece of data and return the hash with the same data, but the source did not return the expected data. RSVP discarded the response because the untrusted source may be (unsuccessfully) attempting an RSVP challenge response replay attack. Recommended Action If you can verify that the source is trusted, it is possible that the source has

malfunctioned; in this case, copy the error message exactly as it appears on the console or in the system log, enter the show tech-support rsvp command to gather data that may help identify the cause of the error, and send this information to your Cisco technical support representative. Otherwise, try to find and disable the untrusted source.


1286

RSVP Messages

Error Message RSVP-3-BAD_RSVP_MSG_RCVD_AUTH_DIGEST: [chars] message from [IP_address] discarded - incorrect message digest Explanation The router received an RSVP message that contained a different secure hash from the

one computed by the router. RSVP discarded the message because the message may have come from an untrusted source. Recommended Action Check the configuration on the router and the sending system to make sure that

they are using the correct security key and secure hash algorithm.

Error Message %RSVP-3-BAD_RSVP_MSG_RCVD_AUTH_DUP: [chars] message from [IP_address] discarded - authentication seq #[int] is a duplicate Explanation The router received an RSVP message with an authentication sequence number that has

already been seen. RSVP discarded the message because an untrusted source may be (unsuccessfully) attempting an RSVP message replay attack. Recommended Action If you can verify that the source is trusted, it is possible that the source has

rebooted and its clock has gone backward in time; in this case, the source should be configured to synchronize its clock with an NTP server. Otherwise, the sender might be an untrusted source (unsuccessfully) attempting an RSVP message replay attack. Try to locate and disable the untrusted source.

Error Message %RSVP-3-BAD_RSVP_MSG_RCVD_AUTH_NO_SA: [chars] message from [IP_address] discarded: no security association for [IP_address] - no RSVP security key configured or no memory left. Explanation The router received an RSVP message that contained a secure hash but dropped the

message because the router was not able to create a security association for the sending system. Recommended Action Check the configuration on the router to make sure that RSVP has access to a

security key for the sending system. If such a key is configured, then check to see if the router has run out of memory.

Error Message %RSVP-3-BAD_RSVP_MSG_RCVD_AUTH_WIN: [chars] message from [IP_address] discarded - seq #[int] outside authentication window Explanation The router received an RSVP message whose authentication sequence number is less

than the lower limit of the out-of-order window. RSVP discarded the message because an untrusted source may be (unsuccessfully) attempting an RSVP message replay attack. Recommended Action It is possible that a trusted source is sending a burst of reordered RSVP

messages that is too large for the authentication window size. If you can verify that the source is trusted and its messages are being sent in large reordered bursts, use the ip rsvp authentication window-size command to increase the window size on the receiving router. It is also possible that a trusted source has rebooted and its clock has gone backward in time; in this case, the source should be configured to synchronize its clock with an NTP server. Otherwise, the sender could be an untrusted source (unsuccessfully) attempting an RSVP message replay attack; try to find and disable the untrusted source.


1287

RSVP Messages

Error Message %RSVP-3-RSVP_MFI_RECOVERY: RSVP calculated Recovery Time is longer than TE Rewrite Hold-Time registered with LSD. Some LSPs may not be be recovered. Explanation Traffic engineering (TE) registered a maximum cutover time with the label switching

database (LSD) that is less than the time it may actually take to recover all LSPs. As a result, more than usual traffic loss may occur on some LSPs during recovery. Recommended Action Make note of the number of checkpointed LSPs in the RSVP HA database by

entering the show ip rsvp high-availability database internal command. This number likely exceeds the hard-defined limit of the number of recoverable LSPs. Provide this information to your Cisco technical support representative.

Error Message %RSVP-3-RSVP_MSG_AUTH_CHALLENGE_TIMEOUT: No response to challenge issued to [IP_address] for key ID [chars] Explanation The router sent an RSVP message to challenge the untrusted source to compute a secure

hash on a random piece of data and return the hash with the same data, but the source did not reply. The source may have crashed or lost its network connection. However, it is also possible that the source was (unsuccessfully) attempting to replay an RSVP message before the challenge and gave up when it saw the challenge from the router. Recommended Action If you can verify that the source is trusted, try to determine if it has crashed or lost its network connection, and then restore network connectivity to it. If the source repeatedly crashes when challenged, a temporary workaround might be to disable challenges on the router by entering the no ip rsvp authentication challenge command until the problem on the source is resolved. Otherwise, assume the source is untrusted. Try to locate and disable it.

Error Message %RSVP-3-RSVP_MSG_AUTH_TYPE_MISMATCH: [chars] message from [IP_address] discarded - authentication algorithm mismatch Explanation The router received an RSVP message from a source that required authentication but the

received message was using the wrong authentication algorithm. Recommended Action Enter the show ip rsvp authentication detail source command on the router

to display the expected algorithm type. Locate the source and change its configuration to match.

RSVP-4 Error Message %RSVP-4-RSVP_AUTH_DUPLICATE_KEY_ID: Key chains [chars] and [chars] contain duplicate key ID [int] Explanation An attempt is being made to add a new key identifier to a key chain in the router

configuration but RSVP detected that this identifier is found in another key chain already assigned to RSVP. Becaue key identifiers must be unique across all the key chains used by RSVP, RSVP will not use the keys with this identifier in all such key chains. This could cause RSVP authentication to fail in some cases. Recommended Action Update the listed key chain(s) so they use different key identifiers.


1288

RSVP_HA Messages

RSVP-5 Error Message %RSVP-5-RSVP_AUTH_KEY_ACL_CHANGE: Key chain [chars] [chars] for [IP_address] because ACL "[chars]" [chars] Explanation The ACL specified in the message text associates the key chain specified in the message

text with a set of RSVP neighbors. RSVP uses the specified key chain to authenticate each RSVP message exchanged with that set of RSVP neighbors after the association is configured. Subsequently, the specified ACL has been reconfigured such that the key chain association is no longer valid for one or more RSVP neighbors in the set. This causes RSVP to search the configuration for another suitable key chain to use with those neighbors. If no such key chain is found, RSVP will no longer be able to provide authentication for messages exchanged with those RSVP neighbors. This causes RSVP to discard RSVP messages from that set of neighbors. Because this may ultimately lead to loss of RSVP functionality with those neighbors, RSVP generates this system message. This system message may also be generated if the ACL is subsequently changed so that it reassociates RSVP neighbors with the specified key chain. If RSVP is not using another key chain for the set of RSVP neighbors specified by the ACL, RSVP will begin using the specified key chain to exchange authenticated RSVP messages with that set of RSVP neighbors, potentially restoring RSVP functionality with those neighbors. Recommended Action If the ACL change unexpectedly caused authentication to be disabled or

enabled for one or more RSVP neighbors, undo the ACL change so that RSVP authentication is not impacted.

Error Message %RSVP-5-RSVP_AUTH_ONE_KEY_EXPIRED: Key (ID) [int] in chain [chars] has expired Explanation The router has detected that one key in a RSVP key chain has expired and that RSVP

has switched to the next unexpired key in that chain. Recommended Action Update the key chain by changing the text and expiration time(s) for the

expired key.

RSVP_HA Messages This section contains RSVP high availability (HA) protocol messages.

RSVP_HA-3 Error Message %RSVP_HA-3-CF_REGISTER_FAILED: Failed to register with CF Explanation The system may be low on memory. Recommended Action Verify system memory availability. Deconfigure graceful restart full mode and

configure it again. This will attempt to restart the RSVP HA process and reregister with compact flash (CF).


1289

RSVP_HA Messages

Error Message %RSVP_HA-3-CLI_ADD_FAILED: Failed to add RSVP HA to CLI Explanation The system may be low on memory. Recommended Action Verify system memory availability. Deconfigure graceful restart full mode and


Error Message %RSVP_HA-3-DB_INIT_FAILED: Database init failed Explanation The system may be low on memory. Recommended Action Verify system memory availability. Deconfigure graceful restart full mode and


Error Message %RSVP_HA-3-ENTRY_MOVE_FAILED: Failed to move a database entry to [chars] tree Explanation An internal error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %RSVP_HA-3-ISSU_INIT_FAILED: In Service Software Upgrade (ISSU) Init failed Explanation The system may be low on memory. Recommended Action Verify system memory availability. Deconfigure graceful restart full mode and


Error Message %RSVP_HA-3-ITEM_SIZE_TOO_BIG: Item size ([int]) bigger than default CF buffer ([int]) Explanation An internal error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1290

RSVP_HA Messages


Error Message %RSVP_HA-3-MAIN_INIT_FAILED: Main init failed Explanation The system may be low on memory. Recommended Action Verify system memory availability. Deconfigure graceful restart full mode and


Error Message %RSVP_HA-3-MSG_MGR_INIT_FAILED: Message Manager init failed Explanation The system may be low on memory. Recommended Action Verify system memory availability. Deconfigure graceful restart full mode and


Error Message %RSVP_HA-3-PROCESS_CREATE_FAILED: Failed to create RSVP HA process Explanation The system may be low on memory. Recommended Action Verify system memory availability. Deconfigure graceful restart full mode and

configure it again. This will attempt to restart the RSVP HA process.

Error Message %RSVP_HA-3-PROCESS_KILL: Killing RSVP HA process Explanation The RSVP HA process is terminating. Recommended Action No action is required.

Error Message %RSVP_HA-3-RF_REGISTER_FAILED: Failed to register with RF Explanation The system may be low on memory. Recommended Action Verify system memory availability. Deconfigure graceful restart full mode and


Error Message %RSVP_HA-3-RF_UNREGISTER_FAILED: Failed to unregister with RF Explanation The RSVP HA client may not have registered with RF. Recommended Action No action is required.


1291

RTT Messages

RTT Messages This section contains round-trip time monitor messages.

RTT-3 Error Message %RTT-3-PathSetupFailed: %RTR Probe [int]: Error in setting current Path. Probe will be stopped Explanation An internal software error has occurred. Recommended Action Reschedule the probe operation that was stopped. Copy the message exactly as

it appears on the console or in the system log. Enter the show rtr configuration command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %RTT-3-SAAMPLS: IP SLA Monitor([dec]): SAA MPLS [chars] Probe [chars] [chars] for destination-address [IP_address] lsp-selector [IP_address] Explanation This informational message logs violations in the Service Assurance Agent probes. This message appears after the rtr logging trap command has been entered. Recommended Action If this message is not necessary, enter the no rtr logging trap command to disable logging. Otherwise, no action is required.

Error Message %RTT-3-SAANEGATIVEVALUE: IP SLA Monitor([dec]): Negative Value for [chars] Explanation The IP SLA monitor statistics generated an error message. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1292

RTT Messages

Error Message %RTT-3-SAANOPROCESS: IP SLA Monitor: Cannot create a new process Explanation The IP SLA monitor is unable to start a new process, and may not be running. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message %RTT-3-SAAPROBENOTFOUND: IP SLA Monitor: Error deleting the probe Explanation A deletion attempt was performed on a probe that does not exist. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %RTT-3-SAARESPTWINITFAIL: IP SLAs responder initialzation failed Explanation The IP Service Level Agreement (IP SLA) responder initialization process was unable

to initialize the timer wheel. As a result, the IP SLA probes on other routers for which this router acts as responder will not work. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %RTT-3-SAATWINITFAIL: IP SLAs: Generic Timer wheel timer functionality failed to initialize Explanation IP SLAs could not initialize the timer wheel. Recommended Action Search for resolved software issues using the Bug Toolkit at Active Explanation This message is generated only when SGBP errors or events debugging is enabled. This

indicates that a link to another SGBP member has completed the interactions to set it up and is now entering the active state. Recommended Action No action is required.


1293

RTT Messages

RTT-4 Error Message %RTT-4-DuplicateEvent: IP SLA Monitor [dec]: Duplicate event received. Event number [dec] Explanation The IP SLA monitor process has received a duplicate event. Recommended Action This is only a warning message. If this message recurs, copy the message

exactly as it appears on the console or in the system log. Enter the show rtr configuration command to gather data that may help identify the cause of the error.Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered along with information about the application that is configuring and polling the Service Assurance Agent probes. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %RTT-4-OPER_CLOSS: condition %s, entry number = %d Explanation This message displays connection loss conditions in the IP Service Level Agreement (IP

SLA) operations. This message is enabled when the ip sla monitor logging trap command is entered. Recommended Action Ensure that the destination for the IP SLA operation is reachable and that the

IP SLA responder operation is configured on the destination. To disable these messages for IP SLA operations, enter the no ip sla monitor logging trap command.

Error Message %RTT-4-OPER_TIMEOUT: condition %s, entry number = %d Explanation The timeout condition is displayed for the IP SLA operations. This message is enabled

when the ip sla monitor logging trap command is entered. Recommended Action Ensure that the destination for the IP SLA operation is reachable. To disable

these messages for IP SLA operations, enter the no ip sla monitor logging trap command.

Error Message %RTT-4-SAACLOCKNOTSET: IP SLA Monitor Probe(s) could not be scheduled because clock is not set. Explanation One or more IP SLA monitor probes could not be scheduled because the system clock

is not set. Recommended Action Ensure that the system clock is functional by using Network Time Protocol or

another mechanism.


1294

RUNCFGSYNC Messages

Error Message %RTT-4-SAAGRPSCHEDCONFIGFAIL: Group Schedule Entry [dec]: [chars] Explanation The probes could not be group scheduled. Either the configured starting time has

already occurred, or the starting time is invalid. Recommended Action Reschedule the group scheduling entry with a valid start time.

Error Message %RTT-4-SAASCHEDCONFIGFAIL: IP SLA Monitor Probe [dec]: [chars] Explanation The IP SLA Monitor probe could not be scheduled. Either the configured starting time

has already occurred, or the starting time is invalid. Recommended Action Reschedule the failed probe with a valid start time.

RTT-6 Error Message %RTT-6-SAATHRESHOLD: IP SLA Monitor([dec]): Threshold [chars] for [chars] Explanation This informational message logs threshold violations in the Service Assurance Agent

probes. This messages appears after the rtr logging trap command has been entered. Recommended Action If this message is not necessary, enter the no rtr logging trap command to disable logging. Otherwise, no action is required.

RUNCFGSYNC Messages This section contains Auto-Running Configuration Synchronization (RUNCFGSYNC) messages.

RUNCFGSYNC-6 Error Message RUNCFGSYNC-6-HASRMSTATE: [chars] Explanation HA single router mode has changed state. Additional details are provided in the error


SASL Messages This section contains Simple Authentication and Security Layer (SASL) messages.


1295

SATVS_DNLD Messages

SASL-2 Error Message %SASL-2-FORKFAIL: Cannot fork process [chars] Explanation An attempt to fork a process has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SASL-2-INITFAIL: Initialization failed - [chars] Explanation SASL component initialization failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


SATVS_DNLD Messages This section contains satellite switch virtual switch (VS) download messages.

SATVS_DNLD-3 Error Message %SATVS_DNLD-3-RS_BOOT_RDY_MEM_FAIL: Unable to allocate space for BOOT_READY msg Explanation The remote switch failed to allocate memory for a BOOT READY message to the virtual

switch. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1296

SATVS_DNLD Messages


Error Message %SATVS_DNLD-3-RS_BOOT_RDY_SEND_FAIL: Unable to send BOOT_READY message Explanation The Remote Switch failed in sending a BOOT READY message to the Virtual Switch. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_DNLD-3-RS_DNLD_BAD_EVENT: Got invalid event [hex]:[hex] Explanation An invalid event was received. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_DNLD-3-RS_DNLD_BAD_QUEUE_EVENT: Event on bad queue [hex] Explanation An unknown message queue event was received. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1297

SATVS_DNLD Messages


Error Message %SATVS_DNLD-3-RS_DNLD_BAD_TIMER_EVENT: Invalid timer [hex] Explanation An invalid event was received or the message queue was unknown. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_DNLD-3-RS_DNLD_CREATE_PROC_FAIL: Failed to create image download process Explanation Failed to create a message queue on the remote switch for downloading related messages from the virtual switch. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_DNLD-3-RS_DNLD_CREATE_QUEUE_FAIL: Failed to created watched queue for download messages Explanation Failed to create a message queue on the remote switch for downloading related messages from the virtual switch. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1298

SATVS_DNLD Messages


Error Message %SATVS_DNLD-3-RS_DNLD_FAILED: Failed to start download from the Virtual Switch ([chars]) Explanation The remote switch was unable to initiate a download from the virtual switch. This could be because of problems in the RSL. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_DNLD-3-RS_DNLD_PROC_FAIL: Download rocess killed. So dropping dnld data Explanation The download process is not running on the remote switch. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_DNLD-3-RS_MSG_ENQUEUE_FAIL: Unable to enqueue message Explanation Failed to enqueue a message. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1299

SATVS_DNLD Messages

Error Message %SATVS_DNLD-3-VS_BOOT_MSG_INVALID_SWITCH: Invalid switch_id (Internal) [dec] (switch number [dec])! Droppping BOOT_READY msg Explanation An invalid BOOT RDY message was received at the virtual switch. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_DNLD-3-VS_BOOT_RDY_RESP_MEM_FAIL: Unable to allocate memory for BOOT_READY response for [chars] [dec] Explanation The virtual switch failed to allocate memory to send a BOOT READY response message to the remote switch. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_DNLD-3-VS_BOOT_RDY_RESP_SEND_FAIL: Unable to send BOOT_READY response to [chars] [dec] Explanation The virtual switch was unable to send a BOOT READY response message to the remote

switch. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1300

SATVS_DNLD Messages

Error Message %SATVS_DNLD-3-VS_BOOT_RDY_SCP_RESP_FAIL: scp_send_pak() returned 0 for BOOT_READY resp for [chars] [dec] Explanation The virtual switch was unable to send a valid BOOT READY response message to the

remote switch. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_DNLD-3-VS_CREATE_DNLD_INSTANCE_FAIL: Failed to create a download instance for [chars] [dec] Explanation An internal error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_DNLD-3-VS_CREATE_DNLD_PROC_FAIL: Failed to create a download process for [chars] [dec] Explanation An internal error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1301

SATVS_DNLD Messages

Error Message %SATVS_DNLD-3-VS_DNLD_IMAGE_INFO_FAIL: Unable to get image info for [chars] [dec] Explanation Failed to get image information for the remote switch from the bundled image. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_DNLD-3-VS_DNLD_IMAGE_VER_INFO_FAIL: Unable to get version for [chars] [dec] Explanation Failed to get image version information for the remote switch from the bundled image. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_DNLD-3-VS_DNLD_UNKNOWN_RS: Unknown RS type [dec] for [chars] sup [dec] Explanation An unknown type of hardware was detected on the remote switch. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1302

SATVS_DNLD Messages

Error Message %SATVS_DNLD-3-VS_GET_DNLD_IMAGE_FAIL: Unable to get image for [chars] [dec] Explanation Failed to get image information to be downloaded to the remote switch from the internal



Error Message %SATVS_DNLD-3-VS_GET_DNLD_INSTANCE_FAIL: Failed to get the download process instance for Remote Switch Explanation An internal error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_DNLD-3-VS_GET_PSLOT_FAIL: Unable to get the physical slot for the Remote Switch in virtual slot [dec] Explanation Failed to get physical slot for the remote switch. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1303

SATVS_DNLD Messages

Error Message %SATVS_DNLD-3-VS_IMAGE_DNLD_FAIL: Image download of size ([dec]) failed for [chars] [dec] Explanation The virtual switch failed to download the image to the remote switch. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_DNLD-3-VS_INVALID_BOOT_MSG: BOOT_READY message in ONLINE state for [chars] [dec]. NAKing Explanation The virtual switch received an invalid BOOT RDY message. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_DNLD-3-VS_RS_REGISTRY_ADD_FAIL: [chars] registry addition failed. Explanation Failed to create registries during initialization. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1304

SATVS_IBC Messages

Error Message %SATVS_DNLD-3-VS_SET_DNLD_INSTANCE_FAIL: Failed to set the download process instance for [chars] [dec] Explanation An internal error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_DNLD-3-VS_VLSOT_ALLOC_FAIL: Unable to allocate vslot for [chars] [dec] slot [dec] Explanation Failed to allocate a virtual slot to the remote switch. Recommended Action Copy the message exactly as it appears on the console or in the system log.


SATVS_IBC Messages This section contains satellite switch virtual switch (VS) interboard communications messages.

SATVS_IBC-3 Error Message %SATVS_IBC-3-VS_IBC_PVTPOOL_PAKALLOC_FAIL: Unable to allocate Pak from VS Inband Private buffer Pool: [chars] Allocating from Public Buffer Pool Explanation Inband packet allocation could not be done from the virtual switch link (VSL) inband

private buffer pool due to the reason stated. Recommended Action No action is required.


1305

SATVS_UL_MGMT Messages

Error Message %SATVS_IBC-3-VSL_DOWN_IP_DROP: VSL inactive - dropping cached IP-over-EoBC packet: (SA/DA:[hex]/[hex], eSA/eDA:[enet]/[enet]) Explanation The VSL is no longer active. The other virtual switch to which the VSL was attached

had one or more IP-over-EoBC packets remaining in the cache after the VSL became inactive (down). The cached IP-over-EoBC packets are being dropped. This condition indicates normal system operation. Recommended Action No action is required.

Error Message %SATVS_IBC-3-VSL_DOWN_SCP_DROP: VSL inactive - dropping cached SCP packet: (SA/DA:[hex]/[hex], SSAP/DSAP:[hex]/[hex], OP/SEQ:[hex]/[hex], SIG/INFO:[hex]/[hex], eSA:[enet]) Explanation The VSL is no longer active. The other virtual switch to which the VSL was attached

had one or more SCP packets remaining in the cache after the VSL became inactive (down). The cached SCP packets are being dropped. Recommended Action No action is required.

SATVS_IBC-5 Error Message %SATVS_IBC-5-VSL_DOWN_IPC_DROP: VSL inactive - dropping cached IPC packet: (SA/DA:[hex]/[hex], SEQ:[hex], Pak_pointer: [hex]) Explanation The VSL is no longer active. The other virtual switch to which the VSL was attached

had one or more IPC packets remaining in the cache after the VSL became inactive (down). The cached IPC packets are being dropped. Recommended Action This condition does not affect normal system processing. No action is required.

Error Message %SATVS_IBC-5-VSL_DOWN_SCP_DROP: VSL inactive - dropping cached SCP packet: (SA/DA:[hex]/[hex], SSAP/DSAP:[hex]/[hex], OP/SEQ:[hex]/[hex], SIG/INFO:[hex]/[hex], eSA:[enet])

Explanation The VSL is no longer active. The other virtual switch to which the VSL was attached

had one or more SCP packets remaining in the cache after the VSL became inactive (down). The cached SCP packets are being dropped. Recommended Action This condition does not affect normal system processing. No action is required.

SATVS_UL_MGMT Messages This section contains satellite switch virtual switch (VS) messages.


1306


SATVS_UL_MGMT-3 Error Message %SATVS_UL_MGMT-3-RS_DNLD_ABORT: Image download aborted because RSL went down Explanation An ongoing remote switch image download was aborted because the remote switch link

(RSL) went down. This condition can be caused by any of the following: - The port channel forming the RSL was shutdown. - All members of the port channel have been shutdown. - The cables hooking to all members have been removed. - The remote switch was deconfigured. - The remote switch detected another virtual switch with a a better priority value. Recommended Action Check for the above conditions and resolve them. Copy the message exactly as


Error Message %SATVS_UL_MGMT-3-RS_HW_PROG_TIMEOUT: H/w programming timed out. Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-RS_INVALID_BNDL_EVENT: Bundle event on already bundled port [chars] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1307



Error Message %SATVS_UL_MGMT-3-RS_INVALID_BOOL_EVENT: Invalid boolean event [hex] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-RS_INVALID_EVENT: [chars]: Invalid event [hex]:[hex] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-RS_INVALID_UNBNDL_EVENT: Unbundle event on already unbundled port [chars] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1308


Error Message %SATVS_UL_MGMT-3-RS_INV_FAILED: Failed to send inventory data to Virtual Switch. Will keep trying Explanation The remote switch failed to send inventory data to the virtual switch even though the

RSL is up. It will keep trying forever. Recommended Action Wait 10 minutes for the system to recover from this condition. If the system

does not recover, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SATVS_UL_MGMT-3-RS_NO_PORT_BNDL_NUMBER: No bundle port number in RSL -- SI set to BIT BUCKET Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-RS_NO_UPLINK: No uplink to master core -- SI set to BIT BUCKET Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1309


Error Message %SATVS_UL_MGMT-3-VS_DEALLOC_VSLOT_MSG_FAIL: [chars] for VS UL dealloc vslot msg [dec] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_DROP_INV_MSG: Dropping Inventory message from unknown Remote Switch number [dec] switch-id(Internal) [dec] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_DUP_INV_MSG: NAKing duplicate inventory from Remote Switch number [dec] switch-id(Internal) [dec] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1310


Error Message %SATVS_UL_MGMT-3-VS_GET_PSLOT_FAIL: Unable to get the physical slot of supervisor for [chars] [dec] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_GET_SWITCH_NUMBER_FAIL: Unable to get switch number for switch-id(internal) [dec] Explanation Failed to get switch number from internal switch ID. An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_ICC_REQ_FAIL: Unable to alloc memory for status update message for [chars] [chars] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1311


Error Message %SATVS_UL_MGMT-3-VS_ICC_RESP_FAIL: icc_get_resp_pak failed Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_ICC_RESP_UPLINK_STATUS_FAIL: icc_req_resp_pak to SP failed for [chars] [chars] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_INVALID_BNDL_EVENT: Bundle event on already bundled port [chars] for switch number [dec] switch-id(Internal) [dec] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1312


Error Message %SATVS_UL_MGMT-3-VS_INVALID_UNBNDL_EVENT: Unbundle event on already unbundled port [chars] for switch number [dec] switch-id(Internal) [dec] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_INV_FAILED: Failed to process inventory data for Remote Switch [dec]. Will remain OFFLINE Explanation The virtual switch is unable to process the inventory data received from the remote switch even though the RSL is up. This switch will be held offline. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_INV_VER_MISMATCH: Versin of INVENTORY message mismatch. Forcing download to switch number [dec] switch-id(internal) [dec] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1313


Error Message %SATVS_UL_MGMT-3-VS_NO_INFO_EM_RECOVERY: No PM info on EM recovery for port [chars] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_NON_INV_MSG: Dropping non-INVENTORY message. Explanation A non-inventory message was received from the remote switch. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_NON_RSL_EM_AGE: EM aging event on non-RSL port [chars] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1314


Error Message %SATVS_UL_MGMT-3-VS_NO_SWIDB_EM_AGE: No swidb for EM aging event (gpid = [dec]) Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_NO_SWIDB_EM_RECOVERY: No swidb for EM recovery event (gpid = [dec]) Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_RS_ADD_PORT_AGPORT_FAIL: Unable to add port [chars] to RSL. Explanation A failure occurred while attempting to add the port to the RSL. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1315


Error Message %SATVS_UL_MGMT-3-VS_RS_ADD_TLV_FAIL: Too few bytes for [chars] TLV in PAgP (reqd. [dec], got [dec]) on port [chars] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_RS_BAD_SUB_OPCODE: Dropping bad sub opcode ([hex]) from [chars] [dec] Explanation An invalid message was received from the remote switch. The message could be

corrupted. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_RS_BAD_VER_STR: Bad version string - inventory failed Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1316


Error Message %SATVS_UL_MGMT-3-VS_RS_CF_CLIENT_ADD_FAIL: CF: Failed to create client (err_code = [hex]) Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_RS_CF_INVALID_SYNC: CF: TLV sync for unconfigured port ([chars]) Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_RS_CHKPT_INVALID_SYNC: CF: Received invalid sync type [hex] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1317


Error Message %SATVS_UL_MGMT-3-VS_RS_CHKPT_MSG_FAIL: CF: Send FAIL status Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_RS_CHKPT_MSG_MEM_FAIL: CF: Unable to get chkpt buffer for sync type [hex] (retval [hex]) Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_RS_CHKPT_MSG_SEND_FAIL: CF: Unable to sync type [hex] to standby (retval [hex]) Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1318


Error Message %SATVS_UL_MGMT-3-VS_RS_CLEAR_LTL_INDEX: Unable to clear LTL index [hex] (retval [hex]) Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_RS_CREATE_BOOL_FAIL: Failed to create watched boolean to monitor uplink comm up Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_RS_CREATE_PROC_FAIL: Failed to create the [chars] process Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1319


Error Message %SATVS_UL_MGMT-3-VS_RS_CREATE_QUEUE_FAIL: Failed to create watched queue for [chars] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_RS_ENQUEUE_FAIL: Unable to enqueue unsolicited message Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_RS_GET_LTL_PORT_INDEX: Unable to get LTL index for port [chars] (retval [hex]) Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1320


Error Message %SATVS_UL_MGMT-3-VS_RS_GET_OID_FAIL: Failed to get OID - inventory failed Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_RS_GET_UPLINK_INFO_FAIL: Failed to get uplink info for port [chars] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_RS_ICC_REQ_FAIL: RP-SP sync: Unable to get memory for RP-SP sync type [hex] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1321


Error Message %SATVS_UL_MGMT-3-VS_RS_IGNORE_ICS_TLV: Ignore ICS TLV on non-uplink port [chars] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_RS_IMAGE_NOT_FOUND: The system failed to find an image to download to Remote Switch [dec]. Will remain OFFLINE Explanation The virtual switch failed to find an image for the remote switch. The remote switch will remain offline. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_RS_IMAGE_NOT_FOUND_INV_RESP: Remote Switch image NOT found in Virtual Switch Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1322


Error Message %SATVS_UL_MGMT-3-VS_RS_INVALID_ARGS: Both [chars] [dec] and idb for port ([chars]) specified Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_RS_INVALID_BOOL_EVENT: Invalid [chars] boolean event [dec] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_RS_INVALID_EVENT: Invalid [chars] event [dec]:[dec] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1323


Error Message %SATVS_UL_MGMT-3-VS_RS_INVALID_ICS_TLV: Invalid ICS TLVs from port [chars] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_RS_INVALID_QUEUE_EVENT: Event on invalid [chars] queue [dec] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_RS_INVALID_SW_ID: Invalid switch-id(Internal) [dec] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1324


Error Message %SATVS_UL_MGMT-3-VS_RS_INVALID_SWITCH_INFO: switch number [dec] has no switch_info Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_RS_INVALID_TIMER_ID: Invalid [chars] timer [dec] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_RS_INVALID_TLV: Received [chars] TLV on non-uplink port [chars] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1325


Error Message %SATVS_UL_MGMT-3-VS_RS_INVALID_TLV_RS: Received Remote Switch side UL mgmt TLV on Remote Switch on port [chars] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_RS_INVALID_TLV_VS: Received Virtual Switch side UL mgmt TLV on Virtual Switch on port [chars] for [chars] [dec] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_RS_INVENTORY_FAIL: Out of memory - inventory failed Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1326


Error Message %SATVS_UL_MGMT-3-VS_RS_INV_RESP_FAIL: Failed sending INVENTORY response [chars]to [chars] [dec] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_RS_INV_RESP_MEM_FAIL: Alloc failure for INVENTORY response to switch number [dec] switch-id(Internal) [dec] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_RS_INV_SEND_FAIL: Inventory:scp send failed session [dec] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1327


Error Message %SATVS_UL_MGMT-3-VS_RSL_BOUNCE: Remote switch [dec] OFFLINE since RSL bounced Explanation The remote switch is now offline because the remote switch link (RSL) was bounced.

This condition can be caused by any of the following: - An SSO switchover resulted in failures on the RSL line cards that required the RSL to be bounced. - The remote switch failed to respond to a sanity check request after an SSO switchover. Recommended Action Check for the above conditions. Note that the first condition can occur when

the switchover happens during a critical operation on the RSL line card. If this is not the case, or if the second condition occurred, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SATVS_UL_MGMT-3-VS_RS_LTL_ALLOC_FAIL: Dynamic allocation also failed for Remote Switch private indices (retval [hex]) Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_RS_MAX_INV_OID_SIZE: OID too long ([dec]) inventory failed Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1328



Error Message %SATVS_UL_MGMT-3-VS_RS_NAK_INV_RESP: Virtual Switch NAKed Inventory. Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_RS_NON_RSL_CONN_INFO_REQ: Dropping non-RSL connect info request message Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_RS_NON_UPLINK_PORT_RM: Attempt to remove port [chars] that is not an uplink of [chars] [dec] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1329


Error Message %SATVS_UL_MGMT-3-VS_RS_NO_RS_INFO_INV_SYNC: CF: No Remote Switch info for inventory sync for [chars] [dec] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_RS_NO_RS_INFO_STATE_SYNC: CF: No Remote Switch info for state sync for [chars] [dec] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_RS_NOT_ENOUGH_PRIVATE_INDICES: Not enough private indices (reqd [dec], got [dec] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1330


Error Message %SATVS_UL_MGMT-3-VS_RS_NULL_RP_SP_SYNC_MSG: RP-SP sync: Received NULL sync msg Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_RS_NULL_SWIDB: Unable to get swidb for port [dec]:[dec]. Explanation The specified port has a null software interface descriptor block. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_RS_PO_AGG_RS_OFFLINE: Port [chars] aggregated but switch-id(InternaL) [dec] OFFLINE Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1331


Error Message %SATVS_UL_MGMT-3-VS_RS_PORT_ADD_REMOVE_ERR: Port ([chars]) add/remove from unconfigured [chars] [dec] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_RS_REGISTRY_ADD_FAIL: [chars] registry addition failed Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_RS_RF_CLIENT_ADD_FAIL: RF: Failed to create client (retcode = [hex]) Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1332


Error Message %SATVS_UL_MGMT-3-VS_RS_RSL_CONN_INFO_RESP_FAIL: No RSL connect info info response received from [chars] [dec] Explanation The RSL connect information response was not heard from the remote switch. This

could be due to an invalid switch number, or the virtual switch may not be actively connected to the remote switch at this time. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_RS_RSL_CONN_INFO_RESP_MSG_FAIL: Unable to alloc memory for RSL connect info response Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_RS_RSL_CONN_REQ_MEM_FAIL: Unable to allocate memory for sending RSL connect info request to [chars] [dec] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1333


Error Message %SATVS_UL_MGMT-3-VS_RS_RSL_CONN_RESP_SEND_FAIL: Sending RSL connect info response failed. Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_RS_RSL_LTL_INDEX_FAIL: Unable to get the local RSL LTL index Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_RS_SET_LTL_INDEX: Unable to [chars] index [hex] on supervisor [chars] [chars] (retval [hex]) Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1334


Error Message %SATVS_UL_MGMT-3-VS_RS_SET_PORT_LTL_INDEX: Unable to set LTL index for port [chars] to [hex] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_RS_SET_RSH_MODE: Unable to set RSH mode on port [chars]. Explanation The system failed to set RSH mode. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_RS_SET_SRC_INDICES_FAIL: Failed to [chars] SCP msg to set src indices. Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1335


Error Message %SATVS_UL_MGMT-3-VS_RS_SSO_EVENT: SSO switchover event in oir_online (slot [dec])-- not supported in Remote Switch Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_RS_TLV_INVALID_METRIC: ICS TLV on [dec] with invalid metric on port [chars] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-3-VS_RS_VSLOT_ALLOC_FAIL: Unable to alloc vslot for switch number [dec] switch-id(Internali) [dec] slot [dec] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1336


Error Message %SATVS_UL_MGMT-3-VS_UNKNOWN_MSG: Unknown message type [dec] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


SATVS_UL_MGMT-4 Error Message %SATVS_UL_MGMT-4-RS_RS_MISMATCH: Virtual switch indicates software mismatch. Requesting download Explanation Because the software running on the remote switch does not match that in the virtual

switch, the proper image will be downloaded. Recommended Action The image download is automatic. If it fails to complete, copy the message


Error Message %SATVS_UL_MGMT-4-RS_RS_OFFLINE: Remote switch OFFLINE since RSL went down Explanation The remote switch is now offline because the remote switch link (RSL) went down. This

condition can be caused by any of the following: - The port channel forming the RSL was shutdown. - All members of the port channel have been shutdown. - The cables hooking to all members have been removed. - The remote switch was deconfigured. - The remote switch detected another virtual switch with a a better priority value. Recommended Action Check for the above conditions and resolve them. Copy the message exactly as

it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require


1337


assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SATVS_UL_MGMT-4-VS_GET_PM_COOKIE_FAIL: RF: Unable to get cookie for port [chars] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-4-VS_RS_MAX_UPLINKS_CONF: Attempt to add port [chars] to [chars] [dec] that already has [dec] uplinks to it Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-4-VS_RS_MISMATCH: Remote switch [dec] software version mismatch. Forcing download Explanation Because the software that is running on the remote switch does not match the software that is running on the virtual switch, matching software will be downloaded to the remote switch. Recommended Action The image download is automatic. If it fails to complete, copy the message



1338



Error Message %SATVS_UL_MGMT-4-VS_RS_OFFLINE: Remote switch [dec] OFFLINE since RSL went down Explanation The remote switch is now offline because the remote switch link (RSL) went down. This

condition can be caused by any of the following: - The port channel forming the RSL was shutdown. - All members of the port channel have been shutdown. - The cables hooking to all members have been removed. - The remote switch was deconfigured. - The remote switch detected another virtual switch with a a better priority value. - The remote switch was powered off. - The remote switch rebooted. Recommended Action Check for the above conditions and resolve them. Copy the message exactly as


Error Message %SATVS_UL_MGMT-4-VS_RS_REG_READ_FAIL: Unable to read register [hex] of port [chars] Explanation The virtual switch failed to read the port adapter registers to verify that RSH is enabled

on them. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1339


Error Message %SATVS_UL_MGMT-4-VS_RS_RS_CONF: Attempt to [chars]-configure [chars] [dec] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-4-VS_RS_VLAN_BLOCK: Unable to [chars] VLANS [hex] [hex] for [chars] Explanation The system could not block or unblock a range of VLANs. Recommended Action Copy the message exactly as it appears on the console or in the system log.


SATVS_UL_MGMT-5 Error Message %SATVS_UL_MGMT-5-RS_ICS_SWITCHOVER: ICS swtichover due to priority change on RSL member [chars] from Virtual Switch [enet] Explanation The remote switch has detected a priority change at the virtual switches and will do an

ICS switchover to a new virtual switch. All RSL members, except the one from which the priority change was detected, will be bounced to allow faster detection of this situation at the virtual switches. Recommended Action This is an informational message. No action is required.

Error Message %SATVS_UL_MGMT-5-RS_RSL_DOWN: RSL is DOWN Explanation The remote switch link is down. Recommended Action This is an informational message. No action is required.


1340


Error Message %SATVS_UL_MGMT-5-RS_RSL_UP: RSL is UP Explanation The remote switch link is up. Recommended Action This is an informational message. No action is required.

Error Message %SATVS_UL_MGMT-5-RS_RSL_UP_INV: RSL is UP. Sending inventory data Explanation The remote switch link is up. The remote switch is sending inventory data to the virtual

switch. Recommended Action This is an informational message. No action is required.

Error Message %SATVS_UL_MGMT-5-RS_RS_ONLINE: Remote switch is ONLINE. Exporting line card data to Virtual Switch Explanation The remote switch is now online. The virtual switch will now look for line cards on the

remote switch and try to bring them online. Recommended Action This is an informational message. No action is required.

Error Message %SATVS_UL_MGMT-5-VS_RSL_UP: RSL to Remote Switch [dec] is UP. Waiting for inventory data Explanation The remote switch link is up and waiting for inventory from the remote switch. Recommended Action This is an informational message. No action is required.

Error Message %SATVS_UL_MGMT-5-VS_RS_ONLINE: Remote switch [dec] ONLINE. Looking for line cards on it Explanation The remote switch is now online. The virtual switch will now look for line cards on the

remote switch and try to bring them online. Recommended Action This is an informational message. No action is required.

SATVS_UL_MGMT-6 Error Message %SATVS_UL_MGMT-6-RS_RSL_MEMBER_BOUNCE: RSL member [chars] bounced due to unbundle action Explanation The RSL member was bounced after it became unbundled. Recommended Action This is an informational message. No action is required.


1341

SATVS_WARM_UPGRADE Messages

Error Message %SATVS_UL_MGMT-6-RS_VS_RSL_BOUNCE: RSL members to the active Virtual Switch bounced as RSL went down Explanation Because the remote switch link (RSL) is down, all members to the same virtual switch

are bounced to allow the virtual switch to recognize the RSL down condition. Recommended Action This is an informational message. No action is required.

Error Message %SATVS_UL_MGMT-6-VS_RS_INVALID_RP_SP_SYNC_TYPE: RP-SP sync: Received invalid sync type [hex] Explanation An internal RP-SP synchronization error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_UL_MGMT-6-VS_RSL_MEMBER_BOUNCE: RSL member [chars] bounced due to unbundle action Explanation The remote switch link (RSL) member was bounced after it became unbundled. Recommended Action This is an informational message. No action is required.

SATVS_WARM_UPGRADE Messages This section contains satellite switch virtual switch (VS) warm upgrade messages.

SATVS_WARM_UPGRADE-3 Error Message %SATVS_WARM_UPGRADE-3-VS_RS_BAD_SUB_OPCODE: (WUG)Dropping bad sub opcode ([hex]) from [chars] [dec] Explanation Received an invalid message from the remote switch. The message could be corrupted. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1342



Error Message %SATVS_WARM_UPGRADE-3-VS_RS_INVALID_EVENT: Invalid [chars] event [dec]:[dec] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_WARM_UPGRADE-3-VS_RS_INVALID_QUEUE_EVENT: Event on invalid [chars] queue [dec] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_WARM_UPGRADE-3-VS_RS_WUG_RESP_FAIL: Failed sending WARM_UPGRADE response [chars]to [chars] [dec] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1343


Error Message %SATVS_WARM_UPGRADE-3-VS_RS_WUG_RESP_MEM_FAIL: Alloc failure for WARM_UPGRADE_RESP to switch-id(Internal) [dec] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_WARM_UPGRADE-3-VS_RS_WUG_SEND_FAIL: WUG start:scp send failed Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SATVS_WARM_UPGRADE-3-VS_RS_WUG_TEST: Test msg_satvs_warm_upgrade Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1344

SBFIFO Messages

SBFIFO Messages This section contains packet first-in, first-out (FIFO) MAC controller messages.

SBFIFO-1 Error Message %SBFIFO-1-BAD_IDB: Invalid Interface Descriptor Block Explanation The driver failed to get the interface descriptor block (IDB). Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %%SBFIFO-1-BAD_PARTICLE: Problem getting particle size Explanation The driver was unable to obtain the particle size for this interface. Recommended Action This is a software bug. Copy the message exactly as it appears on the console


Error Message %SBFIFO-1-BAD_POOL: Could not init buffer pools Explanation The driver failed to obtain a pool of buffers from the Cisco IOS software. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1345

SBFIFO Messages


Error Message %SBFIFO-1-BAD_SB_NOMEM: [chars] - Cannot create IDB subblock due to insufficient memory Explanation There was insufficient system memory to create the subblock. Recommended Action The router requires more main memory. Copy the message exactly as it appears


Error Message %SBFIFO-1-BAD_STRUCT: Could not initialize structure Explanation The driver failed to initialize a structure. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SBFIFO-1-BAD_SUBBLOCK: [chars] - Could not install or use IDB subblock Explanation An internal Cisco IOS error prevented the IDB subblock from being installed or used. Recommended Action This is a software bug. Copy the message exactly as it appears on the console



1346

SBFIFO Messages

Error Message %SBFIFO-1-IDBTYPE_UNK: Unknown IDBTYPE while starting driver Explanation The IDBTYPE in the interface’s instance structure is undefined for this driver. Recommended Action This is a software bug. Copy the message exactly as it appears on the console


Error Message %SBFIFO-1-INITFAIL_NOMEM: [chars], initialization failed, no buffer memory Explanation The Ethernet port initialization failed due to insufficient memory. The router requires

more packet memory. Recommended Action Consider a system upgrade. If this message recurs, copy the message exactly


Error Message %SBFIFO-1-MODE_INVALID: Unknown or invalid chip mode (MII/TBI) Explanation The driver subblock contains an invalid or undefined chip operating mode (MII or TBI

mode). Recommended Action This is a software bug. Copy the message exactly as it appears on the console



1347

SBFIFO Messages

Error Message %SBFIFO-1-RESET: MAC-FIFO Still in Reset Explanation An attempt was made to access the MAC-FIFO while it was in reset. Recommended Action Copy the message exactly as it appears on the console or in the system log.


SBFIFO-3 Error Message %SBFIFO-3-ERRINT: [chars], error interrupt, mac_status = [hex] Explanation The MAC-FIFO controller signalled an error condition. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SBFIFO-3-TOOBIG: [chars], packet too big ([dec]), from [enet] Explanation The interface detects a packet larger than the value that is defined by MTU. Recommended Action Determine the MTU setting of the other station. No action is required.


1348

SCHED Messages

SCHED Messages This section contains scheduler messages.

Error Message %SCHED-3-SEMLOCKED: [chars] attempted to lock a semaphore, already locked by itself Explanation Some sections of code use semaphores to protect critical sections of software. An

attempt was made to lock a semaphore that was already locked. Recommended Action Copy the message exactly as it appears on the console or in the system log.


SCP Messages This section contains Switch Module Configuration Protocol (SCP) messages.

SCP-1 Error Message %SCP-1-TASK_CREATE_FAIL: Failed to create SCP Generic Unsolicited message handler task Explanation The system could not spawn a process that handles certain types of incoming SCP

packets. This could be due to low memory on the switch, in which case other related errors may appear. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1349

SCP Messages

SCP-3 Error Message %SCP-3-ETHERTYPE_FAIL: Ethertype configuration on module [dec], port [dec], failed with return code [hex] Explanation The EtherType configuration failed on the specified port. This usually means that the

module hardware does not support the EtherType configuration. The return error code provides more information. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SCP-3-SCP_HA_FAIL: SCP HA Seq Set - Module: [dec] failed [dec] times Explanation The system did not receive the SCP HA sequence set acknowledgment. Recommended Action Copy the message exactly as it appears on the console or in the system log.


SCP-4 Error Message %SCP-4-UNK_OPCODE: Received unknown unsolicited message from src_addr [hex], dest_addr [hex], length [dec], dsap [dec], ssap [dec], opcode [hex] Explanation An unsupported SCP message was sent to this processor. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1350

SDLC Messages


SCP-5 Error Message %SCP-5-ASYNC_WATERMARK: [dec] messages pending in [chars] Explanation The specified number of SCP messages are waiting in the specified local queue. This

condition might indicate that the SP is generating many messages, that the SP is too busy to send them, or that the module cannot process them at a faster pace. In most cases, this condition occurs when there is heavy control plane activity, such as the formation of Layer 2 trunks, the addition of new VLANs, or the toggling of links. Recommended Action Determine if the SP is busy or if there is interface link toggling. If this condition persists for more than five minutes, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SCP-5-ENABLE: Module enabled [chars] Explanation The supervisor engine sent a message to the router to indicate that a module has been

enabled. Recommended Action No action is required.

SDLC Messages This section contains Synchronous Data Link Control (SDLC) protocol messages.

Error Message %SDLC-4-NOUA: [chars], addr [hex] received command [hex] in response to SNRM, expected UA Explanation The router received a frame other than a UA in response to a SNRM. Recommended Action Check the end station to see if the SNA stack is up and running.


1351

SDM Messages

SDM Messages This section contains Security Device Manager (SDM) template messages.

SDM-6 Error Message %SDM-6-MISMATCH_ADVISE: [chars] Explanation This message provides information regarding an SDM mismatch. Recommended Action No action is required.

SEC_LOGIN Messages This section contains Secure Login messages.

SEC_LOGIN-1 Error Message %SEC_LOGIN-1-QUIET_MODE_ON: Still timeleft for watching failures is [int] secs, [user: [chars]] [Source: [IP_address]] [localport: [int]] [Reason: [chars]] [ACL: [chars]] at [chars] Explanation Quiet mode is now on. No request for connections are now accepted other than those

allowed by the ACL, if the ACL is configured for the blocking period. An implicit deny all of any logins will be in effect. Recommended Action Because all requests from other sources are blocked, check the ACL and add

any source addresses as necessary.

SEC_LOGIN-3 Error Message %SEC_LOGIN-3-INIT_FAILED: Secure Login Initialization failed. [chars] Explanation Initialization of the secure login subsystem has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1352

SFF8472 Messages

SEC_LOGIN-4 Error Message %SEC_LOGIN-4-25: Login failed [user: [chars]] [Source: [IP_address]] [localport: [int]] [Reason: [chars]] at [chars] Explanation A user name or password is invalid. Recommended Action Specify a vaild user name or password.

SEC_LOGIN-5 Error Message %SEC_LOGIN-5-LOGIN_SUCCESS: Login Success [user: [chars]] [Source: [IP_address]] [localport: [int]] at [chars] Explanation Login has succeeded. Recommended Action No action is required.

Error Message %SEC_LOGIN-5-QUIET_MODE_OFF: Quiet Mode is OFF, because [chars] at [chars] Explanation Quiet mode is now off. The router is now operating in normal connection processing

mode. The reason for the change is specified in the message text. Recommended Action No action is required.

SFF8472 Messages This section contains floating-point subsystem (SFF8472) messages.

SFF8472-2 Error Message %SFF8472-2-NOMEM: Not enough memory available for [chars] Explanation The SFF8472 subsystem could not obtain the memory it needed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1353

SFF8472 Messages


SFF8472-3 Error Message %SFF8472-3-INTERNAL_ERROR: [chars] Explanation The SFF8472 subsystem encountered an internal software error. The error message

contains text that can be used to help identify the nature of the problem. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %%SFF8472-3-READ_ERROR: [chars] Explanation There was an error reading digital optical monitoring information from the transceiver

at the specified interface. Recommended Action Try removing and reinserting the transceiver. If the error remains, replace the

transceiver.

Error Message %SFF8472-3-THRESHOLD_VIOLATION: [chars]: [chars]; Operating value: [chars], Threshold value: [chars]. Explanation There has been a threshold violation as specified in the message. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1354

SFP Messages

Error Message %SFF8472-3-UNEXPECTEDEVENT: Process received unknown event (maj [hex], min [hex]). Explanation A process can register to be notified when various events occur in the router. This

message indicates that a process received an event it did not know how to handle. Recommended Action Copy the message exactly as it appears on the console or in the system log.


SFP Messages This section contains Small Form-Factor Pluggable (SFP) module messages.

SFP-3 Error Message %SFP-3-EEPROM_DUP_ERR: SFP on ports [chars] and [chars] have duplicate serial numbers Explanation The GBIC or SFP was identified as a Cisco GBIC, but its vendor ID and serial number

match those of another GBIC on the system. Recommended Action Copy the message exactly as it appears on the console or in the system log.


SFP-4 Error Message %SFP-4-EEPROM_CRC_ERR: EEPROM checksum error for SFP in [chars] Explanation The SFP in the port specified in the message text contains invalid EEPROM data. Recommended Action Remove the SFP from the specified port.


1355

SFP_SECURITY Messages

Error Message %SFP-4-EEPROM_READ_ERR: Error in reading SFP serial ID in [chars] Explanation An error occurred while the SFP type was being read from the EEPROM. Recommended Action Remove the SFP from the port that reported the error.

Error Message %SFP-4-EEPROM_SECURITY_ERR: SFP in [chars] failed security check Explanation The SFP in the port specified in the message text contains invalid EEPROM data. Recommended Action Remove the SFP from the port that reported the error.

SFP_SECURITY Messages This section contains Small Form-Factor Pluggable (SFP) module security check messages.

SFP_SECURITY-4 Error Message %SFP_SECURITY-4-DUPLICATE_SN: SFP interface [chars] has the same serial number as another SFP interface Explanation The SFP was identified as a Cisco SFP, but its serial number matches that of another

interface on the system. Cisco SFPs are assigned unique serial numbers. Recommended Action Verify that the SFP was obtained from Cisco or from a supported vendor.

Error Message %SFP_SECURITY-4-ID_MISMATCH: Identification check failed for SFP interface [chars] Explanation The SFP was identified as a Cisco SFP, but the system was unable to verify its identity. Recommended Action Check the list of supported SFPs for this version of the system software. An

upgrade may be required for newer SFPs. If this does not fix the problem, verify that the SFP was obtained from Cisco or from a supported vendor.

Error Message %SFP_SECURITY-4-SFP_INTERR: Internal error occurred in setup for SFP interface [chars] Explanation The system was unable to allocate resources or encountered some other problem while

attempting to set up the specified SFP interface. Recommended Action Reload the system. If this message recurs, copy the message exactly as it

appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support


1356

SGBP Messages


Error Message %SFP_SECURITY-4-UNRECOGNIZED_VENDOR: SFP interface [chars] manufactured by an unrecognized vendor Explanation The SFP was identified as a Cisco SFP, but the system was unable to match its

manufacturer with one on the known list of Cisco SFP vendors. Recommended Action Check the list of supported SFPs for this version of the system software. A

software upgrade may be required for newer SFPs.

Error Message %SFP_SECURITY-4-VN_DATA_CRC_ERROR: SFP interface [chars] has bad crc Explanation The SFP was identified as a Cisco SFP, but it does not have a valid CRC in the EEPROM

data. Recommended Action Check the list of supported SFPs for this version of the system software. A

software upgrade may be required for newer SFPs. Even if the system could not recognize the SFP, it may still operate properly, but might perform with limited functionality.

SGBP Messages This section contains Stack Group Bidding Protocol (SGBP) messages.

SGBP-1 Error Message %SGBP-1-AUTHFAILED: Member [chars] failed authentication Explanation This message is generated only when SGBP hellos or errors debugging is enabled. This

indicates that an attempted peer connection ended in authentication failure. A peer may be misconfigured, or this could indicate an attempted security breach. Recommended Action Check if the peer is correctly configured. If there is a chance your network is

under attack, obtain knowledgeable assistance. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.


1357

SGBP Messages

Error Message %SGBP-1-DIFFERENT: Rcv [chars]’s addr [IP_address] is different from the hello’s addr [IP_address] Explanation The internally-configured address for an SGBP member does not match the address of

the host that tried to authenticate as that member. The configuration is incorrect on either this system or the other member - they must agree. Recommended Action Determine which configuration is in error and fix it.

Error Message %SGBP-1-DUPLICATE: Rcv Duplicate bundle [chars] is found on member [chars] Explanation This message is generated only when SGBP hellos or errors debugging is enabled. This

indicates that a duplicate bundle was received from the same peer more than once. The duplicate was discarded. Recommended Action If this message recurs, copy the error message exactly as it appears on the

console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support

Error Message %SGBP-1-MISSCONF: Possible misconfigured member [chars] using [IP_address] Explanation This message is generated only when SGBP hellos or error debugging is enabled. This

indicates a configuration error. Either this router has an incorrect IP address listed for the peer or the peer is using an incorrect IP address. Recommended Action Find and correct the configuraton error.

Error Message %SGBP-1-UNKNOWNHELLO: Rcv Hello message from non-group member using [IP_address] Explanation This message is generated only when SGBP hellos or error debugging is enabled. An

SGBP Hello message was received from a host that is not a member of the SGBP group, and discarded. Recommended Action This is a configuration error. Either that host should be listed in this router’s configuration as a member (if that is actually true) or the other host is misconfigured to attempt to join this group.


1358

SGBP Messages

SGBP-3 Error Message %SGBP-3-INVALID: MQ message with [chars] Explanation This message is generated only when SGBP error debugging is enabled. An invalid

message was received and discarded. Recommended Action This probably indicates an error in network media or a peer which is generating

erroneous packets.

Error Message %SGBP-3-INVALIDADDR: Stack group [chars] IP address [IP_address] Explanation The current configuration does not allow a local IP address to be configured using sgbp

member . Any local address is automatically removed fro the SGBP group. Recommended Action Do not configure sgbp member using a local IP address.

Error Message %SGBP-3-INVALIDB: [chars] for bundle ’[chars]’ -- [chars] Explanation An internal software error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SGBP-3-INVFIELD: [chars] field type [hex] has [chars] [dec] (expected [dec]) Explanation This message indicates that an SGBP request from a peer contained invalid or corrupt

data. Recommended Action Check the peer equipment or network media for any problems.

Error Message %SGBP-3-PEERERROR: Peer [IP_address] [chars] during ’PB [chars]’ state for bundle [chars] Explanation An internal software error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1359

SGBP Messages


Error Message %SGBP-3-TIMEOUT: Peer [IP_address] bidding; state ’PB [chars]’ deleted Explanation This message is generated only when SGBP event debugging is enabled. It indicates that

a peer timed out while closing a query. The connection has been dropped. Recommended Action Check the peer equipment and network media for problems.

Error Message %SGBP-3-UNEXP: MQ [chars] from [IP_address] for query [dec]:[dec], bundle [chars], bid [dec], state [chars] Explanation This message is generated only when SGBP error debugging is enabled. The SGBP

connection has entered an unexpected state, possibly due to a software error. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %SGBP-3-UNKNOWN: [IP_address] not known Explanation This message is generated only when SGBP error debugging is enabled. An SGBP

connection was attempted by a host which was not recognized as a peer. The connection was not accepted. Recommended Action Depending on the network topology and firewalling, SGBP connection

attempts from a non-peer host could indicate probing and attempts to breach security. If there is a chance your network is under attack, obtain knowledgeable assistance. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.


1360

SGBP Messages

Error Message %SGBP-3-UNKNOWNEVENT: Event [hex] from peer at [IP_address] Explanation This message is generated only when SGBP error debugging is enabled. An invalid

event occurred, which probably indicates an internal software error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SGBP-3-UNKNOWNPEER: Event [hex] from peer at [IP_address] Explanation This message is generated only when SGBP error debugging is enabled. An SGBP event

came from a network host which was not recognizable as an SGBP peer. The event was discarded. Recommended Action Check if a network media error could have corrupted the address, or if peer

equipment is malfunctioning to generate corrupted packets. Depending on the network topology and firewalling, SGBP packets from a non-peer host could indicate probing and attempts to breach security. If there is a chance your network is under attack, obtain knowledgeable assistance. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

SGBP-5 Error Message %SGBP-5-ARRIVING: New peer event for member [chars] Explanation This message is generated only when SGBP event debugging is enabled. An SGBP peer

joined the group. Recommended Action No action is required.

Error Message %SGBP-5-LEAVING: Member [chars] leaving group [chars] Explanation This message is generated only when SGBP event debugging is enabled. An SGBP peer

has left the group. Recommended Action No action is required.


1361

SGBP Messages

Error Message %SGBP-5-SHUTDOWN: [chars] Explanation This message is generated only when SGBP event debugging is enabled. A process

involved in SGBP was terminated upon completion of its work. Recommended Action No action is required.

Error Message %SGBP-5-STARTUP: [chars] Explanation This message is generated only when SGBP event debugging is enabled. An process

involved in SGBP was started. Recommended Action No action is required.

SGBP-6 SGBP-7 Error Message %SGBP-7-ACTIVE: Member [chars] State - Active Explanation This message is generated only when SGBP errors or events debugging is enabled. This

indicates that a link to another SGBP member has completed the interactions to set it up and is now entering the active state. Recommended Action No action is required.

Error Message %SGBP-7-AUTHOK: Member [chars] State - AuthOK Explanation This message is generated only when SGBP errors or events debugging is enabled. A

message was received from another SGBP member indicating that an authentication attempt to that member succeeded. Recommended Action No action is required.

Error Message %SGBP-7-CANCEL: Local query #[dec]:[dec] for bundle [chars] Explanation This message is generated only when SGBP query debugging is enabled. It provides

information about queries in progress. Recommended Action No action is required.

Error Message %SGBP-7-CHALLENGE: Send Hello Challenge to [chars] group [chars] Explanation This message is generated only when SGBP hellos debugging is enabled. This indicates

that an authentication challenge was sent to a peer. Recommended Action No action is required.


1362

SGBP Messages

Error Message %SGBP-7-CHALLENGED: Rcv Hello Challenge message from member [chars] using [IP_address] Explanation This message is generated only when SGBP hellos debugging is enabled. This indicates

that an authentication challenge was received from a peer. Recommended Action No action is required.

Error Message %SGBP-7-CLOSE: Closing pipe for member [chars] Explanation This message is generated only when SGBP event debugging is enabled. An interprocess communication link was closed. Recommended Action No action is required.

Error Message %SGBP-7-DONE: Query #[dec] for bundle [chars], count [dec], master is [chars] Explanation This message is generated only when SGBP query debugging is enabled. It provides


Error Message %SGBP-7-DUPL: Duplicate local query #[dec] for [chars], count [dec], ourbid [dec] Explanation This message is generated only when SGBP query debugging is enabled. It provides


Error Message %SGBP-7-EQUAL: [dec] equal highest bids, randomly select bid# [dec] Explanation This message is generated only when SGBP query debugging is enabled. It provides


Error Message %SGBP-7-HANGUP: I am a forward-only member, can’t forward bundle [chars], hangup Explanation This message is generated only when SGBP query, event and/or error debugging is

enabled. This indicates a routine change of role for the router in its SGBP interactions with its peers. Recommended Action No action is required.


1363

SGBP Messages

Error Message %SGBP-7-KEEPALIVE: Sending Keepalive to [chars], retry=[dec] Explanation This message is generated only when SGBP hellos debugging is enabled. It indicates

that a keepalive message was send to an SGBP member. Recommended Action No action is required.

Error Message %SGBP-7-KEEPALIVE_TIMEOUT: Keepalive timeout on [chars] Explanation This message is generated only when SGBP hellos debugging is enabled. It indicates

that keepalive messages were not answered so the pipe to an SGBP member has been closed. Recommended Action No action is required.

Error Message %SGBP-7-MQ: [chars] ([hex]) for query [dec]:[dec], bundle [chars], bid [dec], len [dec] Explanation This message is generated only when SGBP error debugging is enabled. This message

indicates that an SGBP query has been received. Recommended Action No action is required.

Error Message %SGBP-7-MQB: Bundle: [chars]State: [chars]OurBid: [dec] Explanation This message is part of a list of debug states displayed at the request of the operator. Recommended Action No action is required.

Error Message %SGBP-7-NEWL: Local query #[dec] for [chars], count [dec], ourbid [dec] Explanation This message is generated only when SGBP query debugging is

enabled. It provides information about queries in progress. Recommended Action No action is required.

Error Message %SGBP-7-NEWP: Peer query #[dec] for [chars], count [dec], peerbid [dec], ourbid [dec] Explanation This message is generated only when SGBP query debugging is enabled. It provides



1364

SGBP Messages

Error Message %SGBP-7-NORESP: Failed to respond to [chars] group [chars], may not have password Explanation An authentication challenge was received but there was no information available to

respond to it. This probably indicates a configuration error, a missing password. Recommended Action Refer to the documentation to configure a username with the same name as the

SGBP group.

Error Message %SGBP-7-PB: [IP_address]State: [chars]Bid: [dec] Retry: [dec] Explanation This message is part of a list of debug states displayed at the request of the operator. Recommended Action No action is required.

Error Message %SGBP-7-RCVD: MQ [chars] from [IP_address] for query [dec]:[dec], bundle [chars], bid [dec], prot[chars] Explanation This message is generated only when SGBP message debugging is enabled. It indicates

that an SGBP packet was received. Recommended Action No action is required.

Error Message %SGBP-7-RCVINFO: Received Info Addr = [IP_address] Reference = [hex] Explanation This message is generated only when SGBP hellos debugging is enabled. It indicates

that data was received by a listener process. Recommended Action No action is required.

Error Message %SGBP-7-RESPONSE: Send Hello Response to [chars] group [chars] Explanation This message is generated only when SGBP hellos debugging is enabled. This indicates

that a response to an authentication challenge was sent to a peer. Recommended Action No action is required.

Error Message %SGBP-7-RESPONSED: Rcv Hello Response message from member [chars] using [IP_address] Explanation This message is generated only when SGBP hellos debugging is enabled. This indicates

that a response to an authentication challenge was received from a peer. Recommended Action No action is required.


1365

SGPM Messages

Error Message %SGBP-7-SENDAUTHOK: Send Hello Authentication OK to member [chars] using [IP_address] Explanation This message is generated only when SGBP hellos debugging is enabled. A message

was send or re-sent to another SGBP member indicating that an authentication attempt from that member succeeded. Recommended Action No action is required.

Error Message %SGBP-7-SENDINFO: Send Info Addr to [chars] Explanation This message is generated only when SGBP hellos debugging is enabled. It indicates

that data was sent by the listener process in response to received data. Recommended Action No action is required.

Error Message %SGBP-7-SENT: MQ [chars] to [IP_address] for query [dec]:[dec], bundle [chars], bid [dec], prot[chars], len [dec] Explanation This message is generated only when SGBP message debugging is enabled. It indicates

that an SGBP packet was sent. Recommended Action No action is required.

SGPM Messages This section contains SG Policy Manager messages.

SGPM-3 Error Message %SGPM-3-POLICY_CTX_POISONED: Policy context %X has bad magic, %X. Explanation The magic number in the policy context is wrong. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1366

SHMWIN Messages

Error Message %SGPM-3-POLICY_INCOMPLETE_RULE: Subscriber policy rule (%s), event (%s) is missing a mandatory action for service (%s); automatically adding. Explanation The subscriber policy rule was missing a mandatory action. The missing action will be

automatically added. Recommended Action Copy the message exactly as it appears on the console or in the system log.


SHMWIN Messages This section contains shared memory messages.

SHMWIN-6 Error Message %SHMWIN-6-ALLOC_FAILURE: Insufficient memory Explanation There was a failure while returning physical memory to the system. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SHMWIN-6-CORE_NOT_ENABLED: In function [chars] The core has not been enabled to get more physical memory Explanation The core has not been enabled. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1367

SHMWIN Messages


Error Message %SHMWIN-6-EXCEEDED_MAX_SIZE: In function [chars] The requested memory size exceeded the window size Explanation The memory requested in this window exceeded the window size. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SHMWIN-6-EXCEEDED_MAX_USERS: In function [chars] The maximum number of users for a shared window has been exceeded Explanation The maximum number of users for a shared window has been exceeded. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SHMWIN-3-FREE_FAILURE: Failure while freeing memory in function [chars] Explanation An attempt was made to free memory that has already been freed or is not within the

address space of the current process. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1368

SHMWIN Messages


Error Message %SHMWIN-6-INCONSISTENCY: Inconsistent state in window Explanation Inconsistent state in window. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SHMWIN-6-INVALID_ARGS: One or more invalid arguments have been passed to the function [chars] Explanation One or more invalid arguments have been passed to the shared memory APIs. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SHMWIN-6-INVALID_PARAM: An invalid parameter has been passed to the function [chars] Explanation One or more invalid parameters have been passed to the shared memory APIs. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1369

SHMWIN Messages

Error Message %SHMWIN-6-MAX_WINDOWS_EXCEEDED: In function [chars] process has exceeded the maximum number of windows that can be opened by it Explanation The process has exceeded the maximum number of windows that can be opened by a



Error Message %SHMWIN-6-MEM_COLLISION: In function [chars] the requested memory space collides with the memory space of other windows Explanation There is a memory space collision. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SHMWIN-6-MUTEX_ERROR: An internal mutex error has occured in the function [chars] Explanation An error has been encountered in the locking or unlocking of the shared memory mutual

exclusivity lock (mutex). Recommended Action Copy the message exactly as it appears on the console or in the system log.



1370

SHMWIN Messages

Error Message %SHMWIN-6-MUTEX_MONITOR_FAILURE: Registration failed with mutex monitor in [chars] Explanation An error occurred while trying to monitor a shared memory mutual exclusivity lock

(mutex). Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SHMWIN-6-NOT_SUPPORTED: The option passed to function [chars] is not supported Explanation This option is not supported. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SHMWIN-7-PHYS_MAP_FAILURE: In function [chars] Failed to map physical memory Explanation Failed to map physical memory in the specified function. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1371

SHMWIN Messages

Error Message %SHMWIN-6-PTHREAD_MUTEX_LOCK_FAILED: An internal mutex error has been encountered in function [chars] Explanation A process that has obtained the access mutex has not released it. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SHMWIN-6-PTHREAD_MUTEX_UNLOCK_FAILED: An internal mutex error has been encountered in function [chars] Explanation An internal mutex error has been encountered. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SHMWIN-6-SHMEM_FAILURE: The function [chars] Could not access shared memory Explanation Could not access shared memory. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1372

SHMWIN Messages

Error Message %SHMWIN-6-SYS_LOCK_CREATE_FAILED: The lock creation for the shared memory failed in function [chars] Explanation Lock creation for the shared memory has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message SHMWIN-6-SYS_LOCK_CREATE_SUCCEEDED: The lock creation for the shared memory succeeded in function [chars] Explanation Lock creation for the shared memory succeeded. Recommended Action No action is required.

Error Message %SHMWIN-6-SYS_LOCK_FAILED: In function [chars] The process was unable to lock the shared memory against other processes Explanation The process was unable to lock the shared memory against other users. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SHMWIN-6-SYS_LOCK_MMAP_FAILED: The mmap for the shared memory lock creation failed in function [chars] Explanation Lock creation for the shared memory has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1373

SHMWIN Messages


Error Message %SHMWIN-6-SYS_UNLOCK_FAILED: In function [chars] The process was unable to unlock the shared memory Explanation The shared memory could not be unlocked due to an internal error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SHMWIN-7-UNLINK_ERROR: An internal error occurred while unlinking in function [chars] Explanation An internal error occurred while unlinking. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SHMWIN-6-VIRT_MAP_FAILURE: In function [chars] Could not reserve virtual memory Explanation Could not reserve virtual memory. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1374

SIBYTE Messages

Error Message %SHMWIN-6-WINDOW_EXCEEDED_MAX_POOLS: The maximum number of pools has been exceeded in function [chars] Explanation The maximum number of pools has been exceeded. Recommended Action Copy the message exactly as it appears on the console or in the system log.


SIBYTE Messages This section contains SiByte processor complex messages.

SIBYTE-0 Error Message %SIBYTE-0-ADDRESS_TRAP: Address trap: [dec] occurred on physical address: [hex] at EPC: [hex], ERR_EPC: [hex] Explanation A previously defined address trap has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SIBYTE-0-MISDIRECTED_INTERRUPT: A misdirected interrupt occurred with int_mask: [hex] Explanation A misdirected interrupt has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1375

SIBYTE Messages


Error Message %SIBYTE-0-UNCORRECTABLE_ECC_ERR: An uncorrectable ECC error has occurred, A_BUS_L2_ERRORS: [hex], A_BUS_MEMIO_ERRORS: [hex], A_SCD_BUS_ERR_STATUS: [hex] Explanation An uncorrectable ECC error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


SIBYTE-3 Error Message %SIBYTE-3-CORRECTABLE_ECC_ERR: A correctable ECC error has occurred, A_BUS_L2_ERRORS: [hex], A_BUS_MEMIO_ERRORS: [hex], A_SCD_BUS_ERR_STATUS: [hex] Explanation The card detected and corrected a single-bit parity error using the error correction code

(ECC) functionality. There was no interruption of service. Transient parity errors are typically caused by RF radiation. Recommended Action No action is necessary if the message occurs infrequently. If errors become

frequent, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


1376

SIBYTE_ION

SIBYTE-6 Error Message %SIBYTE-6-SB_RMON_OVRFL: RMON register [dec] overflow on mac [dec] Explanation The indicated RMON register has overflowed (wrapped around), meaning that the counter reached its maximum value and restarted from zero. The affected register is in the RMON statistical information associated with the specified MAC interface of the Sibyte ethernet controller located on the linecard. Recommended Action This message is informational, and is normal when the service internal

command is enabled. The service internal command should be enabled only for troubleshooting. To disable service internal messages, enter the global configuration command no service internal.

SIBYTE_ION This section contains Sibyte Ion messages.

SIBYTE_ION-3 Error Message %SIBYTE_ION-3-SB_THREAD_CTL_ERR: Call to ThreadCTL() failed: function = [chars], line number = [dec], return_code = [dec], errno = [dec] Explanation A QNX call to ThreadCTL() failed. [chars] is the function, the first [dec] is the line number, the second [dec] is the return code, and the third [dec] is the error number. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1377

SIP10G_QM Messages

SIP10G_QM Messages This section contains 10Gigabit Ethernet SPA Interface Processor (SIP10G) QoS manager (QM) messages.

SIP10G_QM-2 Error Message %SIP10G_QM-2-ACL_MERGE_NO_MEM: Memory low: ACL merge failed for interface %s in %s direction Explanation An ACL merge failed due to insufficient system memory. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SIP10G_QM-2-BAD_TLV: Error in internal messaging - bad tlv %d Explanation A software error occurred during the programming of ACLs into the TCAM. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SIP10G_QM-2-CONFORM_ACTION_NE: Different aggregate and microflow conform-action in class %s[policy %s] Explanation The conform actions must be identical in both the police and police flow commands for

the same class in a service policy applied to MLS interfaces. Recommended Action Change the conform action in the police or the police flow command to make

both actions the same, or remove one of two commands.


1378

SIP10G_QM Messages

Error Message %SIP10G_QM-2-DSCP_NE: Different aggregate and microflow DSCP in class %s[policy %s] Explanation The conform actions must be identical in both the police and police flow commands for

the same class in a service policy applied to MLS interfaces. Recommended Action Change the conform action in the police or the police flow command to make

both actions the same, or remove one of two commands.

Error Message %SIP10G_QM-2-MERGE_ERROR: ACL merge error for Interface %s in %s direction status %d Explanation An ACL merge failed before programming the ACLs into the TCAM. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SIP10G_QM-2-NO_AGGREG_PLC: Hardware aggregate policer resources exceeded Explanation The hardware cannot support the number of aggregate policers required by

configuration. Recommended Action Reduce the total number of aggregate policers required by all service policies

installed in the device. For example, use shared aggregate policers, as defined by the mls qos aggregate-policer command, instead of default per-interface policers.

Error Message %SIP10G_QM-2-NO_FLOW_PLC: Hardware microflow policer resources exceeded Explanation The hardware cannot support the microflow policers required by the policy map. Recommended Action Adjust the microflow policing rate and burst parameters to reduce the total number of different rate and burst combinations in the device.


1379

SIP10G_QM Messages

Error Message %SIP10G_QM-2-P10G_PLC_ATTACH_REJECT_ARP_UFLOW: Command rejected: (policy-map %s class %s interface %s dir %s) flow policer is not supported for traffic classes matching ARP ACL. Explanation In a policy map, a flow policer is not supported if the traffic class matches an ARP ACL. Recommended Action Remove the flow policer from the traffic class matching the ARP ACL and

reattach the policy, or change the traffic class to match a non-ARP ACL and configure the flow policer.

Error Message %SIP10G_QM-2-TCAM_BAD_LOU: Bad TCAM LOU operation in ACL Explanation A software error caused a failure in programming ACLs into the TCAM. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SIP10G_QM-2-TCAM_ENTRIES_EXCEEDED: ACL merge failed, ACEs exceed TCAM capacity or 0 ACES, %d ACEs for interface %s in %s direction Explanation An ACL merge was aborted because the number of ACES exceeded the TCAM capacity

or because the number of ACES was zero. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SIP10G_QM-2-TCAM_ERROR: TCAM programming error %d Explanation A software error caused a failure in programming ACLs into the TCAM. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1380

SIP10G_QM Messages


Error Message %SIP10G_QM-2-TCAM_MEMORY: NMP processor memory low Explanation The programming of ACLs into the TCAM failed due to insufficient memory. Recommended Action Copy the message exactly as it appears on the console or in the system log.


SIP10G_QM-4 Error Message %SIP10G_QM-4-TCAM_CAPMAP: Interface %s hardware TCAM LOU usage capability exceeded Explanation The hardware TCAM cannot support the number of logical operations used with the

configured ACLs on this specific interface. The hardware TCAM can support a maximum of 9 logical operations per interface and a maximum total of 64 logical operations. Recommended Action Reduce the use of logical operations in the ACLs.

Error Message %SIP10G_QM-4-TCAM_ENTRY: Hardware TCAM entry capacity exceeded Explanation The configured ACLs exceed the capacity of the hardware TCAM. Recommended Action To reduce TCAM resource contention, try to share the same ACLs across

multiple interfaces.

Error Message %SIP10G_QM-4-TCAM_LABEL: Hardware TCAM label capacity exceeded Explanation The hardware TCAM cannot support the number of interfaces configured with ACLs.

The hardware TCAM supports 500 interfaces configured with ACLs. Recommended Action Unconfigure ACLs from some of the interfaces.


1381

SIP10G_QM Messages

Error Message %SIP10G_QM-4-TCAM_LOU: Hardware TCAM LOU capacity exceeded Explanation The hardware TCAM cannot support the number of logical operations used with the

configured ACLs. The hardware TCAM can support a maximum of 9 logical operations per interface and a maximum total of 64 logical operations. Recommended Action Reduce the use of logical operations in the ACLs.

Error Message %SIP10G_QM-4-TCAM_MASK: Hardware TCAM mask entry capacity exceeded Explanation The hardware TCAM does not have the mask capacity to handle the number of

configured ACLs. Recommended Action To reduce TCAM resource contention, try to share the same ACLs across

multiple interfaces.

SIP10G_QM-6 Error Message %SIP10G_QM-6-IOS_AND_PS_FEATURE: %s action cannot be present in classmap %s of policymap %s because this service-policy cannot be executed in Cat6K HW due to the presence of filters which require packets to be processed in IOS SW Explanation Network-Based Application Recognition (NBAR) is required for the match protocol

commands used. Because NBAR exists only in software, hardware-specific actions are not supported. Recommended Action Remove the hardware-specific commands or remove the match protocol

criteria in the class map.

Error Message %SIP10G_QM-6-SET_AND_POLICE: ’set’ and ’police’ commands cannot co-exist in classmap %s of policymap %s Explanation The set and police commands cannot coexist in a class map for a QoS manager (QM) supported interface. Recommended Action Remove one of the commands or use the set-dscp-transmit |

set-precedence-transmit | set-exp option for the conform action of the police command.

Error Message %SIP10G_QM-6-SET_AND_TRUST: ’set’ and ’trust’ commands cannot co-exist in classmap %s of policymap %s Explanation The set and trust commands cannot coexist in a class map for a QM supported interface. Recommended Action Remove one of the commands.


1382

SIP200 Messages

Error Message %SIP10G_QM-6-SHAREDAG_AND_POLICE: ’police aggregate’ and regular ’police’ commands cannot co-exist in classmap %s of policymap %s Explanation The police aggregate and police commands cannot coexist in a class map for a QM

supported interface. Recommended Action Remove one of the commands or use the set-dscp-transmit |

set-precedence-transmit | set-exp option for the conform action of the police command.

SIP200 Messages This section contains SPA Interface Processor 200 (SIP200) messages.

SIP200-3 Error Message %SIP200-3-BADIFCTRL: Corrupted sip-200 information for interface [chars] [[hex]] Explanation The interface SIP-200 information is not valid. This is an internal software error. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Collect the output of the show memory command on the line card. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

SIP200-4 Error Message %SIP200-4-MEM_MODULE_MISMATCH: Memory modules are not identical Explanation The memory modules do not have identical parameters. This may impact the

performance. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Collect the output of the show memory command on the line card. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


1383

SIP200_MP Messages

SIP200_MP Messages This section contains SPA Interface Processor 200 (SIP200) multiprocessing messages.

SIP200_MP-1 Error Message %SIP200_MP-1-UNSAFE: Multiprocessor error on [chars] Explanation The line card CPU contains two CPU cores, one of which is the master CPU. The CPU

specified in the error message attempted to perform an operation that is illegal for multiprocessor operation between the two CPU cores. Recommended Action Copy the message exactly as it appears on the console or in the system log.


SIP200_MP-3 Error Message %SIP200_MP-3-INIT_FAILURE: Second CPU initialization failed Explanation The line card CPU unit contains two CPU cores. The second CPU core has not

initialized successfully. The line card is operating with one CPU core only. You may also see a SYS-2-MALLOCFAIL warning message. Recommended Action If this message appears when a line card boots up, reload the line card by

entering the hw-module module slot reset command. Also, check how much memory the line card has by entering the show controller cwan command.


1384

SIP200_SPIRX Messages

SIP200_MP-4 Error Message %SIP200_MP-4-PAUSE: Non-master CPU is suspended for too long, from [hex]([int]) to [hex] for [int] CPU cycles. [chars] Explanation The line card CPU contains two CPU cores, one of which is the master CPU. The master

CPU caused the second, nonmaster CPU to be suspended for too long a time. This condition could cause packet drops on the nonmaster CPU. This warning indicates a transient software problem. The line card should continue to operate normally. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %SIP200_MP-4-TIMEOUT: Master CPU request timed out [chars] Explanation The line card CPU contains two CPU cores, one of which is the master CPU. The

nonmaster CPU is not responding in time to a request from the master CPU. This warning indicates a transient software problem. The line card should continue to operate normally. Recommended Action If this message recurs, copy the message exactly as it appears on the console


SIP200_SPIRX Messages This section contains SPA Interface Processor 200 (SIP200) SPI4.2 bus ingress interface messages.


1385

SIP200_SPIRX Messages

SIP200_SPIRX-3 Error Message %SIP200_SPIRX-3-INITFAIL: Failed to configure the ingress SPI4.2 device. Error = [hex] Explanation The system was unable to program or configure the ingress SPI4.2 device on the line

card. This indicates an internal hardware error. Recommended Action If this message recurs, copy the message exactly as it appears on the console

or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA.

Error Message %SIP200_SPIRX-3-SPA_INTERRUPT: SPA [int] - [chars], SPA Int status = [hex] Explanation A SPA interrupt occurred from the ingress SPI4.2 device. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %SIP200_SPIRX-3-SRAM_ERROR_DATA: SRAM[dec] Address = [hex][hex] Data = [hex][hex][hex]_[hex][hex][hex]_[hex][hex][hex]_[hex][hex][hex] Explanation An SRAM address and data dump is displayed. Recommended Action If this message recurs, copy the message exactly as it appears on the console

or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the


1386

SIP200_SPITX Messages

following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA.

Error Message %SIP200_SPIRX-3-SRAM_INTERRUPT: [chars], Sram Int status = [hex] Explanation An SRAM interrupt occurred from the ingress SPI4.2 device. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %SIP200_SPIRX-3-STATUS_INTERRUPT: [chars], Global Int status = [hex] Explanation A status interrupt occurred from the ingress SPI4.2 device. Recommended Action If this message recurs, copy the message exactly as it appears on the console


SIP200_SPITX Messages This section contains SPA Interface Processor 200 (SIP200) SPI4.2 bus egress interface messages.


1387


SIP200_SPITX-3 Error Message %SIP200_SPITX-3-BADDESC: descriptor [hex], tag [hex], global channel [int] Explanation The egress SPI4.2 device on the line card returns a descriptor entry that is corrupted. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %SIP200_SPITX-3-BADPAK: corrupted packet to [chars] Explanation The egress SPI4.2 device on the line card is handling a packet that is corrupted. This indicates an internal software error. The corrupted packet is dropped. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %SIP200_SPITX-3-CHANNEL_ENABLE_FAIL: SPI4 Channel [int] for Bay [int], [chars] Failed Explanation The system was unable to enable or disable a given SPI4 channel. Recommended Action If this message recurs, copy the message exactly as it appears on the console



1388



Error Message %SIP200_SPITX-3-DESCR_ERR_SPA0: SPAstatus=[hex], syndrome=[hex], RdRspOvf=[int], RdRspTo=[int], OvfVal=[int], OvfCh=[int], OvfDescHi=[hex], OvfDescLo=[hex], DisChk=[int], SeqErrVal=[int], SeqErrCh=[int] Explanation The egress SPI4.2 device on the line card detected a sequence or FIFO overflow error

while processing a transmit descriptor. This condition could cause packet drops. Recommended Action If this message recurs, copy the message exactly as it appears on the console






1389








Error Message %SIP200_SPITX-3-DMA_SQERR: Syndrome=[hex], SPA=[int], Ch=[int], RdSz=[int], RdOff=[int][chars] Explanation The egress SPI4.2 device on the line card detected a sequence error while processing a

DMA operation. This condition could cause packet drops. Recommended Action If this message recurs, copy the message exactly as it appears on the console



1390



Error Message %SIP200_SPITX-3-EFC_ERR_SPA0: SPAstatus=[hex][chars] Explanation The egress data path device on the line card detected an error condition with the

extended flow control bus interface. This condition could cause packet drops. Recommended Action If this message recurs, copy the message exactly as it appears on the console









1391






Error Message %SIP200_SPITX-3-EFCEVNT_ERR: [chars] Explanation The egress data path device on the line card detected an error while processing internal

extended flow-control events. This condition could cause a reduced packet rate. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %SIP200_SPITX-3-EFC_QUEUE_STUCK: [chars] Explanation The egress data path device on the line card detected an error condition with the




1392



Error Message %SIP200_SPITX-3-EFCSTAT_FAIL_SPA0: [chars] Explanation The egress SPI4.2 device on the line card detected an EFC status clock or

synchronization failure. This condition could cause packet drops. Recommended Action If this message recurs, copy the message exactly as it appears on the console









1393






Error Message %SIP200_SPITX-3-FCSTAT_FAIL_SPA0: [chars] Explanation The egress SPI4.2 device on the line card detected an SPI4.2 status clock or







1394









Error Message %SIP200_SPITX-3-INITFAIL: Failed to configure the egress SPI4.2 device. Error = [hex] Explanation The system was unable to program or configure the egress SPI4.2 device on the line

card. This indicates an internal hardware error. Recommended Action If this message recurs, copy the message exactly as it appears on the console



1395


representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA.

Error Message %SIP200_SPITX-3-INT_PERR_SPA0: IntMemPerr=[hex][chars] Explanation The egress SPI4.2 device on the line card detected an internal memory parity error. This

condition could cause packet drops. Recommended Action If this message recurs, copy the message exactly as it appears on the console









1396


representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA.




Error Message %SIP200_SPITX-3-MISMATCH: Descriptor ring mismatch: expects [int] got [int] Explanation The egress SPI4.2 device on the line card returns a descriptor entry that does not match

what the line card CPU expects. This condition could cause packet drops. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %SIP200_SPITX-3-OVERRUN_DROP: SPI4 overrun drops packet for SPA [int], queue [int], count [int] Explanation While the egress SPI4.2 device on the line card sends an packet on the extended flow

controlled channel, it overruns the SPI4 channel but cannot queue it to the internal hold queue. This indicates an internal software error. Recommended Action If this message recurs, copy the message exactly as it appears on the console



1397


http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA.

Error Message %SIP200_SPITX-3-SPI4_ERR_SPA0: SPAstatus=[hex][chars] Explanation The egress SPI4.2 device on the line card detected an error condition with the SPI4.2

bus interface. This condition could cause packet drops. Recommended Action If this message recurs, copy the message exactly as it appears on the console





Error Message SIP200_SPITX-3-SPI4_ERR_SPA2: SPAstatus=[hex][chars] Explanation The egress SPI4.2 device on the line card detected an error condition with the SPI4.2




1398


http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA.




Error Message %SIP200_SPITX-3-SRAM_ECCERR: EccSynd=[hex], Err1bit=[int], ErrMbit=[int], SecHalf=[int], SPA=[int], Ch=[int], Addr=[hex], DataHi=[hex], DataLo=[hex], DataEcc=[hex] Explanation The egress SPI4.2 device on the line card detected a a parity error in the egress packet

memory. This condition could cause packet drops. Recommended Action If this message recurs, copy the message exactly as it appears on the console



1399

SIP400 Messages


SIP400-2 Error Message %SIP400-2-IOBUS_ERROR: IO bus error occurred: [chars] last addr [hex] data [hex] tran [hex] Explanation There was a communication problem with a device on the I/O bus. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %SIP400-2-PCI_BUS_ERROR: A PCI Bus Error occurred while trying to access a device (status reg = [hex], addstatus reg = [hex]) Explanation There was a problem with a PCI read access to a device that caused a bus error on the

host processor. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %SIP400-2-PCI_ERROR_INT: A PCI Error interrupt occurred while trying to access a device (status reg = [hex], addstatus reg = [hex]) Explanation There was a problem with a PCI write access to a device that caused a PCI error

interrupt. Recommended Action If this message recurs, copy the message exactly as it appears on the console



1400

SIP600 Messages



SIP600-2 Error Message %SIP600-2-DEVMGR_ASIC_INIT_FAILED: SIP-600 ASIC Initialization failed at stage-asic_init[dec] Explanation The SIP-600 received an error during initialization when attempting to initialize the

ASICs that make up the forwarding hardware. A hardware problem has prevented the SIP-600 from fully initializing on the target line card. This will result in packets not being forwarded. Recommended Action Attempt to reload the line card. If the problem persists, copy the message


Error Message %SIP600-2-DEVMGR_PROC_CREATE_FAILED: SIP-600 Initialization failed to create a required IOS process[dec] Explanation The SIP-600 received an error during initialization when attempting to create the ASIC

stage2 initialization process. A potential memory or other software resource problem has prevented the SIP-600 from fully initializing on the target line card. This will result in packets not being forwarded. Recommended Action Attempt to reload the line card. If the problem persists, copy the message



1401

SIP600 Messages

Error Message %SIP600-2-INITFAIL: SIP-600 Initialization Failed - [chars]: [chars] [dec] [dec] Explanation The SIP-600 could not initialize the memory that is needed for the feature specified in

the message. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SIP600-2-NULL_OBJECT: Missing device object ([chars]) for pending interrupt Explanation A hardware device asserted an interrupt to report an event, but there is no device object

for this device. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SIP600-2-NULL_SPA_BAY_OBJECT: SPA Bay [dec] is missing Explanation A SPA bay object is missing. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1402

SIP600 Messages

Error Message %SIP600-2-PE_BUS_UNRECOVERABLE_INT: Packet Engine Unrecoverable Bus Interrupt: [chars] = [hex] Explanation A packet engine unrecoverable bus interrupt has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SIP600-2-QUPDATE: SIP-600 Update Queue Hardware Failed - [chars]: [chars] [dec] Cause: [hex] Explanation The SIP-600 received an error on the specified hardware queue when attempting the

specified action. A hardware problem has prevented system queues from being updated on the target line card. This could result in packets not being forwarded. Recommended Action Reload the line card. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SIP600-2-UNRECOVERABLE_FAILURE: SIP-600 Unrecoverable Failure Explanation An unexpected fatal condition has occurred on the SIP-600. The message that was

previously received on the console or in the system log should provide more information on the specific nature of the problem. This message indicates a hardware failure or malfunction. The system will reload to attempt to fix the problem. Recommended Action If this message recurs, copy the message exactly as it appears on the console



1403

SIP600 Messages

SIP600-3 Error Message %SIP600-3-IO_BUS_ERR_INT: IO Bus Error Interrupt: [hex] - Deadman Timer = [hex] Trans Status = [hex] Last Address = [hex] Last Data = [hex] Explanation An I/O bus error interrupt has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SIP600-3-NMI: NMI Reset Status = [hex] Explanation A nonmaskable interrupt has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SIP600-3-NOMEM: [chars] Explanation The SIP-600 card could not obtain statistics due to insufficient memory. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


1404

SIP600 Messages

Error Message %SIP600-3-NO_STATID: PXF([dec]): no stat_id is available for statistics collection Explanation The SIP-600 line card has used up all statistics collection resources. No more resources

are available for further statistics collection. Recommended Action Reduce number of features configured on this PXF. If conditions warrant, copy


Error Message %SIP600-3-NO_STAT_PROCESS: Failed to create statistics process Explanation The SIP-600 card failed to create a statistics process. All statistics counters will be zero. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SIP600-3-PE_BUS_ERR_INT: Packet Engine Bus Error Interrupt: [chars] Explanation A packet engine bus error interrupt has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1405

SIP600 Messages

Error Message %SIP600-3-PE_SPA_BUS_ERR_INT: SPA Bus Error Interrupt: SPA Bus Error Status ([hex]) = [hex], SPA Bus Trans Status ([hex]) = [hex], SPA Bus Last Data ([hex]) = [hex] Explanation A SPA bus error interrupt has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SIP600-3-PE_UNEXPECTED_INT: Unexpected Packet Engine Interrupt: [chars] Explanation An unexpected packet engine interrupt has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SIP600-3-SIP10G_GEN_DEV_ERR: [chars] unexpected error: [chars] Explanation The software driver for the specified SIP-600 device has detected the specified

unexpected condition. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1406

SIP600 Messages

Error Message %SIP600-3-STATID_INCONSISTENCY: PXF([dec]):Inconsistent stats id([hex]) [int] packets dropped. Explanation A WAN line card has received inconsistent statistics from PXF. PXF reported that one

or more packets have been dropped, but no corresponding packet count has been reported. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SIP600-3-UNEXPECTED_GLOBAL_INT: Unexpected Global Interrupt: [chars] Explanation An unexpected global interrupt has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SIP600-3-UNSUPPORTED_LABEL_RANGE: The maximum label range configured for this system exceeds the [int] limit supported by the OSM module. Explanation The MPLS label range that was configured for this system is not supported. The

maximum label range limit is specified in the message. Recommended Action Change the maximum MPLS label range by entering the mpls label range

command.


1407

SIP600 Messages

SIP600-4 Error Message %SIP600-4-INVALID_STATID: PXF:Invalid-Statid ([dec]) for vc [int] under interface [int] Explanation The SIP-600 line card has encountered an internal error while setting up the statistics

report subsystem. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SIP600-4-MR_CFG_ALL_PORTS: CFM configuration is global to sip-600 and applies to all ports Explanation An SCP message to configure match register functionality on the specified port will

apply to all ports on the MSC-600 card as match register configurations are done on the parsing engine. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SIP600-4-SIP10G_PXF_IRAM_PARITY_ERROR: Correcting a PXF instruction error. Explanation This is a Parallel Express Forwarding (PXF) error message that indicates a detection and

correction of a typically rare event. If the error is persistent, it may indicate faulty hardware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1408

SIP600_PARSING_ENGINE Messages


SIP600-6 Error Message %SIP600-6-NULLQID: PXF([dec]):Null-QID ([chars]) [int] packets dropped. Explanation The SIP-600 line card has encountered an invalid queue. The packet has been dropped.

The packet will be counted in the null queue statistics. Packet traffic should continue normally. Recommended Action Copy the message exactly as it appears on the console or in the system log.


SIP600_PARSING_ENGINE Messages This section contains SIP-600 parsing engine messages.

Error Message %SIP600_PARSING_ENGINE-3-DROP_FIFO_OVERFLOW: Parsing Engine Drop Fifo Overflow Explanation The SIP-600 parsing engine has detected that the drop FIFO queue has exceeded the

maximum limit. New updates will be discarded. The parsing engine continues to process data from the interfaces if possible. Recommended Action If traffic has resumed, no action is required. If this message recurs, copy the



1409

SIP600_PARSING_ENGINE Messages

Error Message %SIP600_PARSING_ENGINE-3-INTERRUPT_ERROR: [chars] Explanation The SIP-600 parsing engine has detected the specified interrupt event. The message text

on the console or in the system log provides more information on this error. The parsing engine continues to process data from the interfaces, if possible. Recommended Action If traffic has resumed, no action is required. If this message recurs, copy the


Error Message %SIP600_PARSING_ENGINE-3-MASTER_ABORT: Parsing Engine CPU Master Abort Error Explanation The SIP-600 parsing engine has detected a CPU Master Abort Interrupt. A read to a

write-only register or a write to a read-only register could cause this interrupt. The parsing engine continues to process data from the interfaces, if possible. Recommended Action If traffic has resumed, no action is required. If this message recurs, copy the


Error Message %SIP600_PARSING_ENGINE-3-PARITY_ERROR: Parsing Engine CPU Parity Error Explanation The SIP-600 parsing engine has detected a CPU parity error. A hardware fault is

suspected on the second occurrence only. Otherwise, the parsing engine continues to process data from the interface if possible. Recommended Action If traffic has resumed, no action is required. If this message recurs, copy the



1410

SIP600_QOS Messages

Error Message %SIP600_PARSING_ENGINE-3-RP_INT_WATCHDOG_TIMEOUT: Parsing Engine RP Interface Watchdog Timeout Explanation The SIP-600 parsing engine has detected an RP interface watchdog timeout. The RP

interface process has not relinquished the processor for the watchdog timeout period. The parsing engine continues to process data from the interfaces, if possible. Recommended Action If traffic has resumed, no action is required. If this message recurs, copy the


SIP600_QOS Messages This section contains SPA Interface Processor 600 quality of service (SIP600_QOS) messages.

SIP600_QOS-2 Error Message %SIP600_QOS-2-INITFAIL: SIP-600 Initialization Failed [chars]: [chars] [dec] [dec] Explanation The SIP-600 could not initialize the memory that is needed for the QoS feature. A

hardware problem has occurred on the line card that prevents QoS from functioning. Recommended Action If QoS is a desired feature, try to reload the line card. If the problem persists,

copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


1411

SIP600_QOS Messages

Error Message %SIP600_QOS-2-NOMEM: Memory Allocation Failure - [chars]: [chars] [dec] [dec] Explanation SIP-600 could not allocate the memory that is required for the QoS feature. This

condition might indicate that more memory must be installed on the affected line card or platform to service all features and related entries that are enabled in the configuration. Recommended Action Check available memory and install more if necessary. If sufficient memory is available, reload the Cisco IOS image on the affected line card or platform. If the error persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

SIP600_QOS-3 Error Message %SIP600_QOS-3-CLASSIFYUPDATE: SIP-600 Update QoS Classify Hardware Failed - [chars]: [chars] [dec] Cause: [hex] Explanation SIP-600 received an error on the specified hardware classify entry when attempting the

specified action. Recommended Action If the error occurs on allocating any of the Default Classify Entries, attempt to reload the line card because traffic cannot be forwarded out this line card. If the error occurs in all other cases, remove the QoS action just performed at the user interface, wait a period of time, then reapply the service-policy. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SIP600_QOS-3-EXCEEDEXCESSQRATE: SIP-600 Exceeded system maximum excess queue rates - [chars]: [chars] [dec] Cause: [hex] Explanation The SIP-600 received an error on the specified hardware queue when attempting the

specified action. This condition is the result of attempting to configure a QoS action. The sum of excess bandwidth for all allocated queues has exceeded the system limit. Recommended Action Remove the service policy that failed and try applying the shape command to each of the classes if they are not already configured. Then reapply the service policy. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and


1412

SIP600_QOS Messages

attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SIP600_QOS-3-EXCEEDGUARTQRATE: SIP-600 Exceeded Guaranteed Rates on interface - [chars]: [chars] [dec] Cause: [hex] Explanation The SIP-600 received an error on the specified hardware queue when attempting the

specified action. This condition is the result of attempting to configure a QoS action. The sum of all queue-guaranteed rates has exceeded the maximum that can be configured for the interface to which the queues are applied. This condition could be caused when the priority command is configured without the police command. Recommended Action Add the police command to limit the rate of the priority queue. If this is not the

problem, remove the service policy and reapply it. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SIP600_QOS-3-INSUFFDFLTBW: SIP-600 Insufficient bandwidth for default processing: port [dec] queue id [dec] Cause: [hex] Explanation The SIP-600 reserves 1 percent of the bandwidth of a port for router control packets.

When a service policy is applied, this bandwidth is first deducted from the QoS class default queue. If there is not sufficient bandwidth in the class default queue and the sum of queue-guaranteed bandwidth exceeds the link rate, this message is generated instead of the EXCEEDGUARTQRATE message. Recommended Action Determine if there is any bandwidth available for class default so that space is made available for the port’s queue to handle control packets. Reduce the amount of bandwidth configured on user-defined classes so that more bandwidth is available for class default. If necessary, explicitly configure bandwidth for class default by entering the bandwidth command. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support


1413

SIP600_QOS Messages


Error Message %SIP600_QOS-3-NORESOURCE: SIP-600 Out of Resources- [chars]: [chars] [dec] Cause: [hex] Explanation The specified resource has been depleted from the SIP-600. Recommended Action Change the SIP-600 configuration to conserve the specified resource.

Error Message %SIP600_QOS-3-NOTFOUND: SIP-600 Software Element Not Found - [chars]: [chars] [dec] Explanation SIP-600 client could not locate a required software element. Recommended Action Reload the Cisco IOS image on the affected line card or platform. If the error

persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SIP600_QOS-3-NOTSUP: SIP-600 Feature Not Supported - [chars]: [chars] [chars] Explanation The SIP-600 does not support the specified feature. Recommended Action Change the SIP-600 configuration so that it does not include the specified

feature.

Error Message %SIP600_QOS-3-QEXCEEDWREDGRP: SIP-600 Exceeded WRED limit groups for queue [dec] Explanation The SIP-600 depleted available resources when configuring WRED on the specified

hardware queue. This condition is a result of attempting to configure a QoS action. Recommended Action For each queue, there is a limited number of unique WRED limits sets that can be configured. The user’s configuration action has caused the limits to go beyond the system limit. As a result, WRED is not configured on that queue. The following configuration illustrates three unique sets of WRED min/max limits: random-detect random-detect prec 0 1000 2000 1 random-detect prec 1 1000 2000 1 random-detect prec 2 2000 3000 1


1414

SIP600_QOS Messages

random-detect random-detect random-detect random-detect random-detect

prec prec prec prec prec

3 4 5 6 7

2000 1000 3000 2000 3000

3000 2000 4000 3000 4000

1 1 1 1 1

Update your configuration so that the WRED configuration is within the limits and reapply the service policy.

Error Message %SIP600_QOS-3-QUPDATE: SIP-600 Update Queue Hardware Failed - [chars]: [chars] [dec] Cause: [hex] Explanation The SIP-600 received an error on the specified hardware queue when attempting the

specified action. This condition is the result of attempting to configure a QoS action. Recommended Action There are a variety of reasons that this condition occurs: 1) If the user

configuration action was to remove a service policy and then reapply a service policy to the same interface, it is possible that queues are still draining, which prevents new queues from being allocated. You need to remove the service-policy that failed, wait for a period of time, and then reapply the service policy. 2) It is possible that the number of resources has been depleted. You can consolidate your current QoS configuration to free up resources, and then try reapplying your new configuration. 3) If the error was the result of removing queue hardware, then there is a hardware problem that must be reported. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SIP600_QOS-3-QWREDGTQLIMIT: SIP-600 WRED maximum threshold exceeds queue-limit for queue [dec] Explanation The WRED maximum threshold values should be greater than the assigned queue limit. This condition is the result of the user attempting to configure WRED or changing bandwidth rates, which changes queue-limit values. If this error has occurred, the queue is allocated but WRED is not enabled. Recommended Action Make sure that the queue-limits configured does not exceed any of the WRED max_threshold values. If the queue-limit command is not configured, configure one that is greater than WRED max_threshold values.


1415

SIPSPA Messages

SIP600_QOS-4 Error Message %SIP600_QOS-4-NOTINSHAPE: Warning - Ingress shaping on [chars] not supported on this interface. Explanation Ingress shaping on the specified precedences or DSCP is not supported on this interface

because such packets are control data, which go through a separate high-priority path. Recommended Action Because the specific match statements are ignored, no action is required.

SIPSPA Messages This section contains shared port adapter (SPA) on GSR line card messages.

SIPSPA-3 Error Message %SIPSPA-3-BADCMD: [chars]: Unsupported command [dec], arg0=[hex], arg1=[hex], arg2=[hex] Explanation The route processor issued a command that the software was not able to process. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SIPSPA-3-BAD_IFCOMTYPE: Bad ifcom message type=[int] Explanation The route processor sent a message that the software was not able to process. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1416

SIPSPA Messages

Error Message %SIPSPA-3-BADINT: Attempted to access HWIDB for port [int] Explanation The line card attempted to access the hardware interface descriptor block (IDB)

associated with a nonexistent port. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SIPSPA-3-CMDNOINT: HWIDB Null for command [dec], arg=[hex] Explanation The route processor issued a command that the software was unable to process. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SIPSPA-3-DEVICE_ERROR: subSlot [dec], spatype [hex]. Device error: [chars] Explanation An error related to a device on the SPA has been detected. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1417

SIPSPA Messages

Error Message %SIPSPA-3-EFC_CHAN_ERR: EFC error - interface [chars], vc [dec], anyphy [dec], err_code [dec] : [chars] Explanation There was a failure to configure EFC channel or parameters. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SIPSPA-3-FCI_NOT_SET: Bay [dec]: [chars]: FCI type not set Explanation An FCI type of zero was detected. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SIPSPA-3-HWIDB_FAILURE: Creation: port [dec] vc [dec] Explanation There was a failure to create a hardware interface descriptor block (IDB). Recommended Action Copy the message exactly as it appears on the console or in the system log.



1418

SIPSPA Messages

Error Message %SIPSPA-3-INVALID_ANYPHY: Bay [dec] - Invalid anyphy number [int] for vc [dec] Explanation The specified interface has an invalid anyphy number. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SIPSPA-3-IPCALLOCFAIL: Failed to allocate IPC buffer [chars] Explanation The line card failed to allocate a buffer for communication with the route processor. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SIPSPA-3-IPCSENDFAIL: Failed to send IPC message [chars] Explanation The line card failed to send a message to the route processor. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1419

SIPSPA Messages

Error Message %SIPSPA-3-ISR_RC_ERROR: ISR return code out of range. rc=[dec] Explanation The ISR error return code is out of range. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SIPSPA-3-LINKREC_ERROR: Link record error - Bay [dec] vc [dec], error code [dec] Explanation There was an error during processing of the link record structure. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SIPSPA-3-MESSAGE_ERROR: Bay [dec]: [chars] Explanation An unexpected error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1420

SIPSPA Messages

Error Message %SIPSPA-3-MSGTOOBIG: Message length exceeds max, [int] bytes Explanation The line card attempted to send too large a message to the route processor. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SIPSPA-3-NODISPATCH: Dispatch vector Null, cmd=[dec], dintf=[dec] Explanation No command dispatch vector was found for the specified interface. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SIPSPA-3-POWER: Bay [dec] 12V power is [chars] Explanation The SPA 12 V power fault indicator is displaying the indicated condition. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1421

SIPSPA Messages

Error Message %SIPSPA-3-SONET_CLOCK_FAILED: SPA Sonet clock has failed (status = [hex]) Explanation The SPA SONET clock has failed. SPAs that rely on the SPA SONET clock for proper

operation, such as POS and ATM, will be affected. Recommended Action If the SPA SONET clock does not recover, perform an online insertion and

removal (OIR).

Error Message %SIPSPA-3-SONET_CLOCK_RECOVERED: SPA Sonet clock has recovered (status = [hex]) Explanation The SPA SONET clock has recovered. Recommended Action No action is required.

Error Message %SIPSPA-3-SPI4_CONFIG_FAILURE: Bay [dec], spi4 configuration failure, error [dec] Explanation An attempt to configure the SPI4 interface has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SIPSPA-3-SPI4_INIT_FAILURE: Bay [dec] initialization failure Explanation An attempt to create a SPI4 subblock has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1422

SIPSPA Messages

SIPSPA-4 Error Message %SIPSPA-4-MAX_BANDWIDTH: Total SPA bandwidth exceeds line card capacity of [int] Mbps Explanation The total bandwidth of SPAs exceeds the specified rated capacity of this line card. Recommended Action Refer to the line card guidelines for the maximum allowed aggregated SPA

bandwidth for the line card.

Error Message %SIPSPA-4-MAX_BANDWIDTH_NS: Total SPA bandwidth exceeds line card capacity, full utilization of installed SPA interfaces is not supported Explanation The total bandwidth of SPAs exceeds the rated capacity of this line card. Recommended Action Refer to the line card guidelines for the maximum allowed aggregated SPA

bandwidth for the line card.

Error Message %SIPSPA-4-SPABUS: Bay [dec] [chars] failed. sz=[int] rd_par=[int] noresp=[int] err_l=[int] addr=[hex] data=[hex] parity=[hex] deadman=[int] Explanation The SPA bus has reported an error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SIPSPA-4-SPABUS2: Bay [dec] [chars] failed. sz=[int] rd_par=[int] noresp=[int] absent=[int] err_l=[int] addr=[hex] data=[hex] parity=[hex] deadman=[int] Explanation The SPA bus has reported an error. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1423

SLB Messages

SIPSPA-6 Error Message %SIPSPA-6-ERRORRECOVER: A Hardware or Software error occurred on [chars]. Reason : [chars] Automatic Error recovery initiated. No further intervention required. Explanation An error occurred in one of the devices. Automatic recovery will be attempted. If recovery succeeds, no further messages will be logged and no action will be required. Recommended Action If this message recurs, copy the message exactly as it appears on the console


SLB Messages This section contains server load-balancing messages.

Error Message %SLB-4-CF: Unexpected error: [chars] Explanation An unexpected error occurred in SLB slave replication. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %SLB-4-CF_BULK: [chars] Explanation An unexpected error has occurred in SLB slave replicationand bulk synchronization. Recommended Action If this message recurs, copy the message exactly as it appears on the console

or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at


1424

SLB Messages


Error Message %SLB-4-CF_IPC: Slave replication messages are creating a backlog in IPC. Some SLB objects may not be synchronized. Explanation Due to an IPC resource contention, SLB was unable to replicate all objects. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %SLB-4-CF_NUM: Unexpected error: [chars] [dec] Explanation An unexpected error has occurred in SLB slave replication. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %SLB-4-CF_RATE: Overrun of SLB’s slave replication rate, some SLB objects may not be synchronized. Explanation Due to a high connection rate, SLB was unable to replicate all objects. Recommended Action If this message recurs, copy the message exactly as it appears on the console



1425

SMC Messages

Error Message %SLB-4-IF_REMOVED: Access interface removed: [chars] being set to outofservice. Explanation An interface being referenced in SLB access configuration has been removed. The

virtual server or firewall farms referencing this interface will be brought out of service. Recommended Action If this message recurs, copy the message exactly as it appears on the console


SMC Messages This section contains Services Management Channel (SMC) messages.

SMC-2 Error Message %SMC-2-BAD_ID_HW: Failed Identification Test in [chars] [[dec]/[dec]] 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 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. Explanation The hardware in the specified location could not be identified as a genuine Cisco

product. Recommended Action If this message recurs, copy the message exactly as it appears on the console



1426

SMSC_RP Messages

Error Message %SMC-2-FAILED_ID_HW: Failed Identification Test in [chars] [[dec]/[dec]] Explanation An error occurred while identifying the hardware in the specified location. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %SMC-2-PROTO_HW: Module ([chars]) is a registered proto-type for Cisco Lab use only, and not certified for live network operation. Explanation The hardware in the specified location is a prototype module from Cisco and should not

be used in a live network. Recommended Action If this message recurs, copy the message exactly as it appears on the console


SMSC_RP Messages This section contains short message service center route processor messages.

SMSC_RP-3 Error Message %SMSC_RP-3-GETHWVER_FAILED: Unable to set 7600-SSC-400 in slot [dec] in single-spa-mode because of error in obtaining its hardware revision. Explanation The 7600-SSC-400 could not be set to single-SPA mode. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1427

SMSC_RP Messages


Error Message %SMSC_RP-3-NO_SCP_BUFFER: Unable to set 7600-SSC-400 in slot [dec] in single-spa-mode because of insufficient scp buffers. Explanation The 7600-SSC-400 could not be set to single-SPA mode. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SMSC_RP-3-SSC_SSPA_RETRY: 7600-SSC-400 in slot [dec] is reset as a [dec] try to set it in single-spa-mode. Explanation The specified slot has reset in an attempt to set it to single-SPA mode. A maximum of

three retries are performed. Recommended Action If the third retry is unsuccessful, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SMSC_RP-3-SSC_SSPA_SHUT: 7600-SSC-400 in slot [dec] is shutdown because it cannot be set in single-spa-mode Explanation The specified slot has been shut down because it cannot be set to single-SPA mode. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1428

SNASW Messages


SMSC_RP-6 Error Message %SMSC_RP-6-INVALID_HW_VERSION: Single-spa-mode is not allowed for 7600-SSC-400 hardware version [dec].[dec]. Explanation Only 7600-SSC-400 versions greater than 0.3 can be set in single-SPA mode. Recommended Action To use single-SPA mode, use 7600-SSC-400 versions greater than 0.3.

SNASW Messages This section contains Systems Network Architecture (SNA) Switching Services messages.

SNASW-3 Error Message %SNASW-3-CLS_LOG_0: PROBLEM - [int] - Could not validate process handle [chars] Explanation CLS has passed the SNA switch a DLC packet, but the SNA switch does not have a valid

handle to invoke the correct SNA process. The CLS message has been discarded. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SNASW-3-HPR_LOG_20: PROBLEM - [int] - Remote node supplied a corrupted RSCV: the next hop is the local CP [chars] Explanation A high performance routing (HPR) route setup request or response unit (RU) has been

received with a Route Selection Control Vector (RSCV) that gives the local node as the next ANR hop, which is an invalid vector. The remote node is sending invalid protocol data. Recommended Action Report the error to the remote end administrator.


1429

SNMP Messages

SNASW-4 Error Message %SNASW-4-RTP_LOG_10: EXCEPTION - [int] - LFSID in use, moving on to next one. [chars] Explanation An LFSID was found to be in use. The SNA switch will use another one. Recommended Action If this message recurs, copy the message exactly as it appears on the console


SNMP Messages This section contains Simple Network Management Protocol (SNMP) messages.

SNMP-3 Error Message %SNMP-3-AUTHFAILIPV6: Authentication failure for SNMP request from host %P Explanation An SNMP request sent by this host was not authenticated. Recommended Action Make sure that the community and user name used in the SNMP request has

been configured on the router.

Error Message %SNMP-3-BADIFINDEXTABLE: The file nvram:ifIndex-table is corrupt. Explanation The file is not in the expected format. Recommended Action Delete the file if possible.

Error Message %SNMP-3-DVR_DUP_REGN_ERR: Attempt for dupe regn with SNMP IM by driver having ifIndex [dec] and ifDescr [chars] Explanation A driver is attempting to register an IDB with the interface manager while there is

already an interface with the same ifIndex and ifDescr but different IDB registered. A duplicate registration would cause the interface counters shown by SNMP to not work properly for this particular interface. Recommended Action Fix the duplicate registration in the driver level.


1430

SNMP Messages

Error Message %SNMP-3-DVR_DUP_REGN_WARNING: Attempt for dupe regn with SNMP IM by driver having ifIndex [dec] and ifDescr [chars] Explanation A driver is attempting to register an IDB that is already registered with the interface

manager. This is just a warning message and handled by SNMP. Recommended Action Fix the duplicate registration in the driver level.

Error Message %SNMP-3-DYNSYNCFAIL: Snmp Dynamic Sync Failed for %s %s %s%s Explanation The dynamic synchronization of an SNMP MIB to the standby device failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SNMP-3-INPUT_QFULL_ERR: Packet dropped due to input queue full Explanation An SNMP packet was dropped because the input queue is full. Recommended Action Enter the show snmp command to see the number of packets dropped. Stop any SNMP access to the device until the error condition has recovered.

Error Message %SNMP-3-INTERRUPT_CALL_ERR: [chars] function, cannot be called from interrupt handler Explanation A call has been made to the function from an interrupt handler. This is not permitted.

The function call will fail and the device will reboot down the stack in a memory allocation call. Recommended Action If this message recurs, copy the message exactly as it appears on the console



1431

SNMP Messages

Error Message %SNMP-3-ISSU_ERR: [chars] Explanation An error occurred during an ISSU versioning operation. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SNMP-3-MAX_TRAPS_EXCEED_ERR: Maximum number of traps exceeded the maximum allowed in the current sync-message to STANDBY Explanation This is a software development debug message. The number of SNMP traps defined

exceeded the maximum allowed in a checkpoint synchronization message. Recommended Action (These actions apply only to the developer, and not to the user.) Increase

SNMP_SYNC_BITMASK_MAX to a higher value. Check smci_rf_status_event() for further details.

Error Message %SNMP-3-SYNCFAIL: SNMP MIB Sync Failure: [chars] Explanation An error occurred while synchronizing an SNMP MIB to standby. Recommended Action Copy the message exactly as it appears on the console or in the system log.


SNMP-4 Error Message %SNMP-4-HIGHCPU: Process exceeds %dms threshold (%dms IOS quantum) for %s of %s--result %s Explanation A warning threshold was exceeded when SNMP was processing a variable binding. Recommended Action Enter the debug snmp packet command to determine the contents of the

SNMP request that is causing the message. Some MIB objects require a relatively large amount of time to process. MIB objects in the multi-variable-binding are processed one by one. If possible, do


1432

SNMP_BULKSTAT Messages

not retrieve MIB objects appearing in this messages by using multi-variable-binding SNMP PDUs. Copy the error message exactly as it appears, and report it along with any debug output to your technical support representative.

Error Message %SNMP-4-NOENGINEIDV6: Remote snmpEngineID for %P not found when creating user: %s Explanation An attempt to create a user failed, probably because the engine ID of the remote agent or SNMP manager was not configured. Recommended Action Configure the remote snmpEngineID and reconfigure the user. If this message


SNMP-5 Error Message %SNMP-5-LINK_DOWN: LinkDown:Interface %s changed state to down Explanation The state of the interface is changed to down. Recommended Action No action is required.

Error Message %SNMP-5-LINK_UP: LinkUp:Interface %s changed state to up Explanation The state of the interface is changed to up. Recommended Action No action is required.

Error Message %SNMP-5-MODULERESET: [chars] object has been set to ’reset’ for [chars]=[dec] from IP address [chars]. Explanation The SNMP server has reset a module. Recommended Action No action is required.

SNMP_BULKSTAT Messages This section contains Simple Network Management Protocol (SNMP) bulk data collection messages.


1433

SNMP_BULKSTAT Messages

SNMP_BULKSTAT-3 Error Message %SNMP_BULKSTAT-3-5: Memory not available for [chars] for [chars] Explanation Data collection or transfer could not be successfully carried out because of lack of

memory. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message %SNMP_BULKSTAT-3-REMOTE_FILE_WRITE_ERR: File Write failed for the remote file [chars] Explanation The user name or password specified in the error message might not have the required

privileges to write a file to the network management station specified in the error message, or the destination directory specified in the error message is invalid. Recommended Action Ensure that the user name and password in the network management station

address has the necessary privileges to write to the destination directory.

Error Message %SNMP_BULKSTAT-3-TOOSMALL_BUFFER: Buffer size is insufficient to accommodate even the header part for [chars] Explanation The buffer size is insufficient to accommodate the header for the bulk data file. The header contains the schema definitions of all the configured schemas. Recommended Action Increase the maximum buffer size using the buffer-size size-of-buffer command, where size-of-buffer is the increased buffer size.

SNMP_BULKSTAT-4 Error Message %SNMP_BULKSTAT-4-BUFFER_OVERFLOW: Buffer size too small to accomodate data for one collection interval for [chars] Explanation The bulk data file is too large for the configured buffer size for a single transfer interval.

Data collection will continue in another new buffer of the configured size, and the collected buffer will be transferred to the configured destination. Recommended Action Increase the maximum buffer size using the buffer-size size-of-buffer command, where size-of-buffer is the increased buffer size.

Error Message %SNMP_BULKSTAT-4-PRI_URL_UNREACHABLE: Primary network management station is unreachable for [chars] Explanation The collected bulk data file could not be successfully transferred to the primary network

management station address specified in the error message. This condition can occur because the primary network management address is not configured or the configured primary network


1434

SNMP_MGR Messages

management station address is unreachable. If a secondary network management station address is configured, the collected bulk data file will be sent to the secondary network management station address. Recommended Action Ensure that the primary network management station address is configured. If the primary network management station address is configured, check the connectivity to the destination indicated by the primary network management station address specified in the error message.

Error Message %SNMP_BULKSTAT-4-SEC_URL_UNREACHABLE: Secondary network management station is unreachable for [chars] Explanation The collected bulk data file could not be successfully transferred to the secondary

network management station address destination specified in the error message. This condition can occur because the secondary network management station address is not configured or the configured secondary network management station address is unreachable. If a retention interval is not configured, the bulk data file will be immediately deleted. If a retention interval is configured, retries will be attempted for the configured number of times. Recommended Action Check the connectivity to the destination indicated by the secondary network

management station address shown in the error message.

SNMP_MGR Messages This section contains Simple Network Management Protocol (SNMP) manager messages.

SNMP_MGR-3 Error Message %SNMP_MGR-3-BADINFORMTRANSPORT: Unknown inform transport type: [chars] Explanation This SNMP inform destination uses an unknown transport type. Inform notifications

cannot be sent to this destination. Recommended Action Copy the error message and the output from show techsupport exactly as it

appears, and report it to your technical support representative.

Error Message %SNMP_MGR-3-MISSINGHOSTIPV6: Cannot locate information on SNMP informs host: %P Explanation A table entry cannot be found for the indicated SNMP informs destination. As a result,

inform notifications will not be sent to this destination. Recommended Action Delete and readd the informs destination by entering the snmp-server host

configuration command. If this does not clear the condition, reload the system and copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require


1435

SNMP_MIB_ISSU Messages

assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show snmp host, and show snmp commands and your pertinent troubleshooting logs.

SNMP_MGR-4 Error Message %SNMP_MGR-4-BADRESPONSESTATUS: Unknown response status code: [int] Explanation The SNMP Manager process received an internal response with an unknown status

code. Recommended Action Copy the error message exactly as it appears on the console or in the system


SNMP_MIB_ISSU Messages This section contains Simple Network Management Protocol (SNMP) MIB in-service software upgrade (ISSU) messages.

SNMP_MIB_ISSU-2 Error Message %SNMP_MIB_ISSU-2-GET_BUFFER: SNMP MIB ISSU client failed to get buffer for message. Error: %d (%s) Explanation The SNMP MIB ISSU client was unable to get buffer space for building a negotiation

message. As a result, the negotiation message cannot be sent to the standby device and the standby device cannot be brought up properly. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1436


following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs.

Error Message %SNMP_MIB_ISSU-2-INIT: SNMP MIB ISSU client initialization failed to %s. Error: %d (%s) Explanation The SNMP MIB ISSU client could not be initialized. This initialization failure must be

addressed before an in-service software upgrade or downgrade can be performed successfully. Otherwise, a software upgrade or downgrade will result in downtime. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SNMP_MIB_ISSU-2-SEND_NEGO_FAILED: SNMP MIB ISSU client failed to send negotiation message. Error: %d (%s) Explanation The SNMP MIB ISSU client was unable to send a session negotiation message to the

peer device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SNMP_MIB_ISSU-2-SESSION_NEGO: SNMP MIB ISSU client encountered unexpected client nego_done. Error: %d (%s) Explanation An ISSU-compliant client transitions through a series of internal states. The SNMP

MIB ISSU client encountered a client negotiation done state that was unexpected. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1437


information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs.

Error Message %SNMP_MIB_ISSU-2-SESSION_REGISTRY: SNMP MIB ISSU client failed to register session information. Error: %d (%s) Explanation The SNMP MIB ISSU client was unable to register session information. If a problem



SNMP_MIB_ISSU-3 Error Message %SNMP_MIB_ISSU-3-CAP_INVALID_SIZE: SNMP MIB ISSU client capability list is empty. Explanation The SNMP MIB ISSU client capability exchange list is empty, which is an invalid


Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show issu capability entries commands and your pertinent troubleshooting logs.


1438


Error Message %SNMP_MIB_ISSU-3-CAP_NOT_COMPATIBLE: SNMP MIB ISSU client capability exchange result incompatible. Explanation Based on the results of the capability exchange, the SNMP MIB ISSU client is not compatible with the peer. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SNMP_MIB_ISSU-3-INVALID_SESSION: SNMP MIB ISSU client does not have a valid registered session. Explanation The SNMP MIB ISSU client does not have a valid registered session. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SNMP_MIB_ISSU-3-MSG_NOT_OK: SNMP MIB ISSU client ’Message Type %d’ is not compatible Explanation The SNMP MIB ISSU client received an incompatible message from the peer device.




1439


Error Message %SNMP_MIB_ISSU-3-MSG_SIZE: SNMP MIB ISSU client failed to get the MTU for Message Type %d. Error: %d (%s) Explanation The SNMP MIB ISSU client was unable to calculate the MTU for the specified

message. The SNMP MIB ISSU client is not able to send the message to the standby device. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SNMP_MIB_ISSU-3-SESSION_UNREGISTRY: SNMP MIB ISSU client failed to unregister session information. Error: %d (%s) Explanation The SNMP MIB ISSU client was unable to unregister session information. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SNMP_MIB_ISSU-3-TRANSFORM_FAIL: SNMP MIB ISSU client %s transform failed for ’Message Type %d’. Error: %d (%s) Explanation The SNMP MIB ISSU client could not transform the specified message type. If the

transmit transformation failed, the checkpoint message was not sent to the standby device. If the receive transformation failed, the checkpoint message was not applied on the standby device. In either case, the SNMP MIB state between the active device and the standby device is not identical. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1440

SONET Messages


SONET Messages This section contains Synchronous Optical Network (SONET) messages.

SONET-3 Error Message %SONET-3-APSCOMMCHANGE: [chars]: Link to [chars] channel reverts to PGP protocol version [dec] Explanation APS has reverted to a different version of the PGP protocol between working and

protect routers. Recommended Action This is an informational message only. No action is required.

Error Message %SONET-3-APSEVENT: [chars]: APS event type error: event [dec] undefined Explanation The APS software has malfunctioned. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SONET-3-APSHAHOLDTIME: [chars]: [chars] Explanation The PGP hold time was adjusted. Recommended Action This is an informational message only. No action is required.


1441

SONET Messages

Error Message %SONET-3-APSSYNCSECONDARY: [dec]/[dec]: No hwidb Explanation A new secondary RP was unable to find a device descriptor block corresponding to slot

and unit specified by primary the RP. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SONET-3-DELAYTIMER: [chars] Explanation The system was unable to create a delay timer. Recommended Action Copy the message exactly as it appears on the console or in the system log.


SONET-6 Error Message %SONET-6-APSREFL: [chars]: Remote reflection of APS status now [chars] Explanation The APS software has detected a change in the reflected local APS status. Recommended Action This is an informational message only and occurs in normal operation. No

action is required.

Error Message %SONET-6-APSREMSWI: [chars]: Remote APS status now [chars] Explanation The APS software has detected a change in the APS status of the remote interface. Recommended Action This is an informational message only and occurs in normal operation. No

action is required.


1442

SPA Messages

SPA Messages This section contains shared port adapter (SPA) messages.

SPA-0 Error Message %SPA-0-TEMP_SHUTDOWN: [chars] temperature too high. ([dec]C) SPA has been shut down. Explanation The SPA has been shut down. Recommended Action Ensure that the temperature is normal in the area where the router is located and resolve any conditions, such as malfunctioning fans, that are causing a temperature increase.

Error Message %SPA-0-TEMP_SHUTDOWN_OVR: [chars] temperature too high ([dec]C) but shutdown has been overridden. Explanation SPA shutdown has been overridden by the configuration. Recommended Action Ensure that the temperature is normal in the area where the router is located and resolve any conditions, such as malfunctioning fans, that are causing a temperature increase.

Error Message %SPA-0-VOLT_SHUTDOWN: [chars] voltage out of operating range. Nominal ([dec]mV), value ([dec]mV). The SPA has been shut down. Explanation The SPA has been shut down to prevent component damage. Recommended Action Replace the SPA immediately. Record the associated messages and return the

SPA for service.

SPA-2 Error Message %SPA-2-TEMP_CRITICAL: [chars] temperature too high. ([dec]C) Explanation The SPA temperature is too high. Recommended Action Ensure that the temperature is normal in the area where the router is located and resolve any conditions, such as malfunctioning fans, that are causing a temperature increase.


1443

SPA Messages

Error Message %SPA-2-VOLT_CRITICAL: [chars] voltage outside of nominal range. Nominal ([dec]mV), value([dec]mV) Explanation One of the measured environmental test points exceeded the nominal voltage threshold.

This condition could cause the system to fail to operate properly. Explanation Correct the specified condition, or the system may shut itself down as a preventive

measure. Enter the show environment all command to help determine if this problem is due to a voltage condition.

Error Message %SPA-2-VOLT_SHUTDOWN_OVR: [chars] voltage outside of operating range. Nominal ([dec]mV), value([dec]mV). SPA shutdown has been overridden by configuration. Explanation One of the measured environmental test points exceeded the nominal voltage threshold.

SPA shutdown has been overridden by the configuration. Recommended Action Correct the specified condition. Enter the show environment all command to help determine if this problem is due to a voltage condition.

SPA-3 Error Message %SPA-3-BAD_FCITYPE: [chars]: Illegal FCI type [dec]. Explanation An invalid FCI type was passed to the SPA. This is a software error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA-3-ENVMON_INITFAIL: SPA environmental monitoring initialization error Explanation A failure occurred during the SPA environmental monitoring subsystem startup.

Environmental monitoring is not enabled. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.


1444

SPA Messages

Error Message %SPA-3-ENVMON_NOT_MONITORED: Environmental monitoring is not enabled for [chars] Explanation The specified SPA has not registered any sensors with the environmental monitoring

system. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA-3-RESOURCE_ERROR: [chars] ([hex], [hex], [hex], [hex]) [chars] Explanation A required resource could not be allocated. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA-3-SOFTWARE_ERROR: [chars] ([hex], [hex], [hex], [hex]) [chars] Explanation The specified software error has been detected. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1445

SPA Messages

SPA-4 Error Message %SPA-4-TEMP_WARNING: [chars] temperature too high. ([dec]C) Explanation The SPA temperature is too high. Recommended Action Ensure that the temperature is normal in the area where the router is located and resolve any conditions, such as malfunctioning fans, that are causing a temperature increase.

Error Message %SPA-4-TEMP_WARNLOW: [chars] temperature too low. ([dec]C) Explanation The SPA temperature too low. Component reliability and data integrity may be

compromised. Recommended Action Raise the ambient temperature if it is too low. If there is no issue with the ambient temperature, then the SPA temperature sensor has likely failed. If there are no data errors, this warning can be ignored.


1446

SPA_CCB Messages

SPA_CCB Messages This section contains SPA configuration control block (CCB) command messages.

SPA_CCB-3 Error Message %SPA_CCB-3-CMDFAIL_0ARG: [chars]: host command [dec] error: [chars]. Explanation A command from the host failed to execute for the specified reason. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA_CCB-3-CMDFAIL_1ARG: [chars]: host command [dec](arg0=[dec]) error: [chars]. Explanation A CCB command failed to execute for the specified reason. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA_CCB-3-CMDFAIL_2ARG: [chars]: host command [dec](arg0=[dec], arg1=[dec]) error: [chars]. Explanation A command from the host failed to execute for the specified reason. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1447

SPA_CCB Messages


Error Message %SPA_CCB-3-CMDFAIL_3ARG: [chars]: host command [dec](arg0=[dec], arg1=[dec], arg2=[dec]) error: [chars]. Explanation A command from the host failed to execute for the specified reason. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA_CCB-3-CMD_TOOEARLY: [chars]: host command [dec] received before handler ready. Explanation A host command was received before the handler was initialized. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA_CCB-3-ENQUEUE_FAIL: [chars]: host command [dec] failed to enqueue. Explanation An error occurred while the SPA console was attempting to enqueue a host command to

the command queue. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1448

SPA_CCB Messages


Error Message %SPA_CCB-3-IF_CONFIG: [chars]: IF_CONFIG type [dec] failed. Explanation The specified interface configuration type is not valid for the SPA card. Recommended Action Copy the message exactly as it appears on the console or in the system log.


SPA_CCB-4 Error Message %SPA_CCB-4-BADENCAP: [chars]: Unknown encapsulation command [dec]. Explanation An invalid encapsulation command was received by the SPA. This is a software error. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1449

SPA_CHOC_DSX Messages

SPA_CHOC_DSX Messages This section contains common channelized shared port adapter (SPA_CHOC_DSX) messages.

SPA_CHOC_DSX-3 Error Message %SPA_CHOC_DSX-3-BAD_SIZE_ERR: SPA [dec]/[dec]: [dec] [chars] events on HDLC Controller were encountered.The SPA is being restarted. Explanation The SPA driver detected an error event on the HDLC controller. Recommended Action If the condition persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SPA_CHOC_DSX-3-COR_MEM_ERR: SPA [dec]/[dec]: [dec] correctable [chars] memory error(s) encountered. The error has been corrected and normal processing should continue. The memory address of most the recent error is: [hex] Explanation The SPA driver detected a correctable memory error on the SPA card. The error has been

corrected and normal processing should continue. The hexadecimal memory address of the most recent error is specified in the message text on the console or in the system log. Recommended Action If the condition persists, or other errors are specified for the SPA, copy the


Error Message %SPA_CHOC_DSX-3-EFC_ERROR: EFC ERROR: [chars] - [chars] [int] Explanation The SPA extended flow control (EFC) encountered an error. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1450



Error Message %SPA_CHOC_DSX-3-HDLC_CTRL_ERR: SPA [dec]/[dec]: [dec] [chars] events on HDLC Controller were encountered. Explanation The SPA driver detected an error event on the HDLC controller. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SPA_CHOC_DSX-3-INVALID_IF_TYPE: Invalid SPA type [dec] on [chars]. Port Number = [dec]. Explanation The software cannot recognize the interface type. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA_CHOC_DSX-3-INVLIAD_IF_INDEX: Invalid interface index [dec] on slot/bay:[dec]/[dec]. Min. Index = [dec]. MAx. Index = [dec]. Explanation The index is not valid for the specified interface. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1451



Error Message %SPA_CHOC_DSX-3-LINK_TABLE_ERR: [chars]: Could not create link table, error [dec] Explanation An error occurred during the creation of the link record table. Interfaces may not come

up or pass traffic. Recommended Action If the ports on the SPA are not operating as expected, power down and reseat

the specified SPA card. If the error messages persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SPA_CHOC_DSX-3-NODESTROYSUBBLOCK: The [chars] subblock named [chars] was not removed Explanation IDB subblocks could not be removed during the unprovisioning of a channel. This condition indicates a software error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA_CHOC_DSX-3-NULL_DATA_STRUCTURE: Failed to create [chars] on slot/bay:[dec]/[dec]. Port Number = [dec]. Explanation The specified software resource cannot be allocated for this hardware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1452



Error Message %SPA_CHOC_DSX-3-NULL_SPA_PTR: Explanation The pointer to a SPA value is null. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA_CHOC_DSX-3-SEMAHOG: SPA on [chars]: Semaphore Hog was encountered. Explanation The semaphore used by the IPC communication between host and the SPA was

monopolized by one process. This behavior would cause other processes fail to send commands down to the SPA and might result in improper operation. Recommended Action Stop all the traffic on the SPA, and then reload the configuration by entering

shutdown and no shutdown commands on the controllers. If the problem persists, power cycle the SPA. If the condition persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SPA_CHOC_DSX-3-SPA_CMD_RETURN_ERR: SPA command [chars] return error [int] Explanation The SPA returned an error status for a host command. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1453



Error Message %SPA_CHOC_DSX-3-SPA_CMD_SEND_ERR: Failed to send [chars] command to SPA Explanation The host failed to send a command to the SPA. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA_CHOC_DSX-3-SPA_SW_ERR: SPA on [chars]: [chars] Software error was encountered. Explanation The SPA driver detected a software error condition on the SPA card. This condition

might cause improper operation. Recommended Action Reload the configuration by entering shutdown and no shutdown commands

on the controllers. If the problem persists, power cycle the SPA. If the condition persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SPA_CHOC_DSX-3-SPI4_HW_ERR: SPA on [chars]: [chars] Hardware error was encountered. Explanation The SPA driver detected a hardware error condition on the SPA card’s SPI4 bus. This

condition might cause improper operation. Recommended Action Power down and reseat the specified SPA card. If the condition persists, copy

the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at


1454



Error Message %SPA_CHOC_DSX-3-UNCOR_MEM_ERR: SPA [dec]/[dec]: [dec] uncorrectable [chars] memory error(s) encountered. The memory address of most the recent error is: [hex] The SPA is being restarted. Explanation The SPA driver detected an uncorrectable memory error condition on the SPA card.

Packet corruption may result. The hexadecimal memory address of the most recent error is specified in the message text on the console or in the system log. Recommended Action Power down and reseat the specified SPA card. If the condition persists, copy

the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SPA_CHOC_DSX-3-UNCOR_PARITY_ERR: SPA [dec]/[dec]: [dec] [chars] parity error(s) encountered. Explanation The SPA driver detected an uncorrectable parity error condition on the SPA card. Packet

corruption may result. Recommended Action Power down and reseat the specified SPA card. If the condition persists, copy

the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


1455


Error Message %SPA_CHOC_DSX-3-UNKNOWN_CMD: Unknown [chars] command recieved on slot/bay:[dec]/[dec]. Command Type = [dec] Explanation An unknown command was received by the SPA card carrier. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA_CHOC_DSX-4-UNPROV_FAIL: Interface [chars] unprovisioning failed: [chars] Explanation The system failed to respond to an unprovisioning command. A hidden VLAN could not

be deleted within a 2-second timeout window. This condition may be caused by a system that is too busy or by a FIB IPC failure. The line card driver code will attempt to delete the hidden VLAN. Recommended Action If processing continues normally, no action is required. If system operation is

adversely affected, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SPA_CHOC_DSX-3-VCCFG_ERROR: Interface [chars] config command error (cmd [int], arg [int], retval [int]) Explanation A command sent from the system to a line card has failed. This is an internal software

error. Recommended Action Decode the traceback and get the output of the show logging command on the RP and SIP-1 and check if there are any errors being reported. Try to recreate the problem to see if there is a consistent method to recreate. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs


1456

SPA_CHOCX Messages

SPA_CHOCX Messages This section contains common channelized shared port adapter (SPA) messages.

SPA_CHOCX-3 Error Message %SPA_CHOCX-3-"NULL": NULL [chars] Explanation The NULL pointer was seen when getting the data structure. This is an internal software

error. Recommended Action Decode the traceback. Enter the debug hw-module subslot slot/bay oir plugin command while the problem is happening. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SPA_CHOCX-3-CREATE_FAIL: Failed to create [chars] : slot/bay:[dec]/[dec] Explanation The CHOCX SPA controller descriptor block creation failed. Recommended Action Check the amount of system memory available. Upgrade your system to the

latest version of Cisco IOS software. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SPA_CHOCX-3-FATAL_ERROR: Fatal error for [chars] : slot/bay:[dec]/[dec] Explanation The CHOCX SPA controller encountered a fatal error. Recommended Action Upgrade your system to the latest version of Cisco IOS software. If this

message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at


1457

SPA_CHOCX Messages


Error Message %SPA_CHOCX-3-INVALID_SPA_TYPE: Invalid SPA type : slot/bay:[dec]/[dec], spa_type=[dec]. Explanation The CHOCX SPA type cannot be recognized by the version of Cisco IOS software

currently running on the system. Recommended Action Upgrade your system to the latest version of Cisco IOS software in your release

train. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SPA_CHOCX-3-NULL_INSTANCE: Null [chars] instance for [chars] : slot/bay:[dec]/[dec] Explanation The instance pointer is NULL when getting the data structure. This is an internal

software error. Recommended Action Decode the traceback and get the output of show running-config. Copy the


Error Message %SPA_CHOCX-3-RETURN_ERROR: Return error for [chars]: return_value=[dec] Explanation An error code was received. This is an internal software error. Recommended Action Decode the traceback and get the output of show running-config. Copy the

message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using


1458

SPA_CHOCX_CWRP Messages

the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SPA_CHOCX-3-UNKNOWN_OPTION: Received unknown [chars]: option=[dec] Explanation An unknown option was received. This is an internal software error. Recommended Action Decode the traceback and get the output of show running-config. Copy the


SPA_CHOCX_CWRP Messages This section contains common channelized shared port adapter (SPA) CWRP messages.

SPA_CHOCX_CWRP-1 Error Message %SPA_CHOCX_CWRP-1-ALLOCFAIL: OC3/STM1 [dec]/[dec] [chars] allocation failure Explanation A memory allocation failure occurred in the CHOCX controller or channel. This is an internal software error. Recommended Action Decode the traceback. Enter the debug hw-module subslot slot/bay oir plugin command while the problem is happening. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


1459


SPA_CHOCX_CWRP-3 Error Message %SPA_CHOCX_CWRP-3-APS_CMD_FAIL: Failed to send APS command [hex] to [chars] (retcode [hex]) Explanation An APS command send failed. This is an internal software error. Recommended Action If this error happened while configuring APS, try reconfiguring the interface.

If the error persists or occurred during normal operation, decode the traceback and copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SPA_CHOCX_CWRP-3-CORRUPT: Corrupt configuration, unsupported [chars] ([int]) encountered Explanation The OC3/STM1 RP driver running configuration is corrupt. Recommended Action Decode the traceback and get the output of show running-config. Research


Error Message %SPA_CHOCX_CWRP-3-NULL_SUBBLOCK: Null ssb for [chars] Explanation The hardware IDB subblock is NULL. This is an internal software error. Recommended Action Decode the traceback and get the output of show running-config. Research



1460


Error Message %SPA_CHOCX_CWRP-3-PLUGIN_ERR: [chars] Explanation The RP plugin encountered an error during a plugin call. This is an internal software

error. Recommended Action Decode the traceback. Enter the debug hw-module subslot slot/bay oir plugin command while the problem is happening. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SPA_CHOCX_CWRP-3-TIMEOUT: Interface ([chars]): [chars] Explanation The line card did not reply to a query for SONET information from the CHOCX RP

driver. This is an internal software error. Recommended Action Decode the traceback. Enter the debug hw-module subslot slot/bay oir plugin command while the problem is happening. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

SPA_CHOCX_CWRP-5 Error Message %SPA_CHOCX_CWRP-5-DEF_SUBRATE: [chars] [chars] Explanation The remote subrate configuration has changed. Recommended Action No action is required.

Error Message %SPA_CHOCX_CWRP-5-PATH_UPDOWN: Path [chars], changed state to [chars] Explanation A SONET high-order path changed its state. This is an internal software error. Recommended Action Decode the traceback and get the output of show controller sonet. Look into this output to see if there are any alarms being reported at the path level. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at


1461

SPA_CONSOLE Messages


Error Message %SPA_CHOCX_CWRP-5-T3_UPDOWN: T3 [chars], changed state to [chars] Explanation A T3 within STS1 has changed its state. This is an internal software error. Recommended Action Decode the traceback and get the output of show controller sonet. Look into this output to see if there are any alarms being reported at the path level. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

SPA_CONSOLE Messages This section contains shared port adapter (SPA) virtual console messages.

SPA_CONSOLE-3 Error Message %SPA_CONSOLE-3-BADDETACH: SPA console session detach failed with IPC error [chars]. Explanation A failure occurred when attempting to detach SPA console subsystem. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1462


Error Message %SPA_CONSOLE-3-INITFAIL: [chars]: SPA console initialization error: [chars]. Explanation A failure occurred during initialization of the SPA console subsystem. The SPA console may not be functioning. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA_CONSOLE-3-NOBUF: No packet buffer available for sending SPA console messages Explanation An error occurred while the SPA console was attempting to acquire a packet buffer from

the IPC buffer pool. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show ipc status command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SPA_CONSOLE-3-NO_DRIVER: [chars]: VCON_SPACP: Driver not ready. Explanation The SPA sent a message before the line card was fully initialized. Recommended Action If this message recurs, copy the message exactly as it appears on the console



1463


Error Message %SPA_CONSOLE-3-RX_BUS_PARAM: [chars]: VCON_SPACP: Invalid SPA bus parameters. Explanation There was an error receiving a message from the SPA. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %SPA_CONSOLE-3-TX_BUS_PARAM: [chars]: VCON_SPACP: Invalid SPA bus parameters. Explanation There was an error sending a message to the SPA. Recommended Action If this message recurs, copy the message exactly as it appears on the console


SPA_CONSOLE-5 Error Message %SPA_CONSOLE-5-CANTGET: Cannot get spa client ipc port Explanation The SPA virtual console subblock is not properly initialized. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1464


Error Message %SPA_CONSOLE-5-CANTSEND: Cannot send SPA console messages. Explanation An error occurred while a SPA console message was being sent through the IPC. This

condition might result in a malfunction in the operation of the IPC. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA_CONSOLE-5-CANTSET: Cannot set spa client ipc port Explanation The SPA virtual console subblock is not properly initialized. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA_CONSOLE-5-QUEUEFULL: Queue holding SPA console messages is full current console packet will be dropped Explanation An error occurred while the SPA console was queueing a packet for transmission. Some

console data may be lost. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1465

SPACP Messages

SPACP Messages This section contains SPA bus communications protocol (SPA CP) messages.

Error Message %SPACP-3-BUFFER: [chars]: Failed to allocate buffer for SPACP message. Explanation Cannot allocate memory for an SPACP message. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %SPACP-3-CREATE: [chars]: SPA Bus Device creation failed. Explanation Cannot allocate memory for the SPA bus structure. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %SPACP-3-INIT: [chars]: Failed to initialize SPACP. [chars]. Explanation SPACP messaging could not be initialized for the specified reason. Recommended Action If this message recurs, copy the message exactly as it appears on the console



1466

SPA_CT3 Messages

Error Message %SPACP-3-OPCODE: [chars]: SPACP opcode [hex] unknown. Explanation An unexpected message was received from the SPA. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %SPACP-3-SEND: [chars]: Failed to send SPACP message. Explanation Failed to send a message to the SPA. Recommended Action If this message recurs, copy the message exactly as it appears on the console


SPA_CT3 Messages This section contains CT3 shared port adapter (SPA) messages.

Error Message %SPA_CT3-3-INVALID_SPA_TYPE: Invalid SPA type : slot/bay:[dec]/[dec], SPA_type=[dec]. Explanation The CT3 SPA type cannot be recognized by the version of Cisco IOS software currently

running on the system. Recommended Action Upgrade the system to the latest version of Cisco IOS software in your release train. If you require further assistance, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support


1467

SPA_CT3 Messages


Error Message %SPA_CT3-3-PROCESS_FAIL: process creation failed for [chars] Explanation A command could not be processed because of a process-creation failure. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA_CT3-3-SUBRATE_FPGA_DL_FAILED: [chars]: Failed to download the subrate FPGA image. Explanation The specified SPA was not able to download the subrate FPGA image during a

card-initialization sequence. The image might be corrupted and the system will try to recover from this error by upgrading the image. Recommended Action If the system cannot recover from this error automatically after a few attempts,

it will power off the affected SPA. In that case, copy the message exactly as it appears on the console or in the system log. Enter the show hw-module subslot slot-number/subslot-number fpd and show hw-module subslot slot-number/subslot-number oir commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


1468

SPA_DATABUS Messages

SPA_DATABUS Messages This section contains SPA data bus interface messages.

Error Message %SPA_DATABUS-3-PACKET_GAP_ERROR: [chars] [chars] - A packet gap error has occurred Explanation The data bus interface on this line card is experiencing a hardware-related issue. No loss

of data or data corruption should occur. Packets should continue to be forwarded because this error will occur only with a hardware failure. Recommended Action If this error recurs, verify whether the failed hardware is the SIP or the SPA.

Copy the message exactly as it appears on the console or in the system log. Enter the show hw-module slot-number/subslot-number errors spi4 command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SPA_DATABUS-3-SPI4_BAD_CHAN_NUM: [chars] [chars] - An error condition on the SPA data bus has occurred. Explanation An error condition on the SPA data bus has occurred. This condition can be caused by

a software fault only. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show hw-module slot-number/subslot-number errors spi4 command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


1469


Error Message %SPA_DATABUS-3-SPI4_BAD_CNTR_WORD: [chars] [chars] - An error condition on the data bus between the SPA and the SIP has occurred. Explanation An error condition has occurred on the data bus between the SPA and the SIP. Symptoms

of this error include data corruption or a short duration of data loss. In addition, the interface may lock up. Recommended Action If this error recurs, verify whether the failed hardware is the SIP or the SPA.

Copy the message exactly as it appears on the console or in the system log. Enter the show hw-module slot-number/subslot-number errors spi4 command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SPA_DATABUS-3-SPI4_CALENDAR_LEN: [chars] [chars] - An error condition on the data bus between the SPA and the SIP has occurred. Explanation An error condition on the data bus between the SPA and the SIP has occurred. This

condition results from a software fault. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show hw-module slot-number/subslot-number errors spi4 command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SPA_DATABUS-3-SPI4_CRTL_WD_NO_DIP4: [chars] [chars] - An error condition on the data bus between the SPA and the SIP has occurred. Explanation This message points to an error condition on the SPA data bus. Symptoms of this error include data corruption or a short duration of data loss. Recommended Action If this error recurs, verify whether the failed hardware is the SIP or the SPA.

Copy the message exactly as it appears on the console or in the system log. Enter the show hw-module slot-number/subslot-number errors spi4 command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at


1470



Error Message %SPA_DATABUS-3-SPI4_FIFO_STATUS_BUS: [chars] [chars] - FIFO status bus out of frame condition has occurred. Explanation The data bus interface on this line card is experiencing a hardware-related issue. When

this condition is occurring, the interface will be down or may not forward any traffic. This error will occur only with a hardware failure. Recommended Action If this error recurs, verify whether the failed hardware is the SIP or the SPA. If supported by the platform, try running diagnostics on the suspected hardware. Copy the message exactly as it appears on the console or in the system log. Enter the show hw-module slot-number/subslot-number errors spi4 command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SPA_DATABUS-3-SPI4_OUT_OF_FRAME: [chars] [chars] - A data bus out of frame error condition has occurred Explanation An error has occurred on the data bus between the SPA and the SIP. When this condition

is occurring, the interface will be down or may not forward any traffic. This error will only occur with a hardware failure. Recommended Action Power down and reseat the card. If this error recurs, verify whether the failed

hardware is the SIP or the SPA. If supported by the platform, try running diagnostics on the suspected hardware. Copy the message exactly as it appears on the console or in the system log. Enter the show hw-module slot-number/subslot-number errors spi4 command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


1471


Error Message %SPA_DATABUS-3-SPI4_SEQUENCE: [chars] [chars] - A sequence error has occurred. Explanation A sequence error has occurred on the data bus between the SPA and the SIP. When this

condition is occurring, a short duration of packet loss may be noticed. This condition may indicate a developing hardware failure. This error should occur very infrequently during normal operation and should not occur when no changes are made to the configuration. This error will occur only with a hardware failure. Recommended Action If this error recurs, verify whether the failed hardware is the SIP or the SPA. If supported by the platform, try running diagnostics on the suspected hardware. Copy the message exactly as it appears on the console or in the system log. Enter the show hw-module slot-number/subslot-number errors spi4 command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SPA_DATABUS-3-SPI4_SINGLE_DIP2_PARITY: [chars] [chars] - A single DIP 2 parity error on the FIFO status bus has occurred. Explanation The data bus interface on this line card is experiencing a hardware-related issue. Some

packets may be dropped. This error will occur only with a hardware failure. Recommended Action If this error recurs, verify whether the failed hardware is the SIP or the SPA. If supported by the platform, try running diagnostics on the suspected hardware. Copy the message exactly as it appears on the console or in the system log. Enter the show hw-module slot-number/subslot-number errors spi4 command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


1472


Error Message %SPA_DATABUS-3-SPI4_SINGLE_DIP4_PARITY: [chars] [chars] - A single DIP4 parity error has occurred on the data bus. Explanation A single parity error has occurred on the data bus between the SPA and the SIP. When

this condition is occurring, a short duration of packet loss or symptoms resulting from data corruption may occur. This condition may indicate a developing hardware failure. This error should occur very infrequently during normal operation and should not occur when no changes are made to the configuration. Recommended Action Power down and reseat the card. If this error recurs, verify whether the failed

hardware is the SIP or the SPA. If supported by the platform, try running diagnostics on the suspected hardware. Copy the message exactly as it appears on the console or in the system log. Enter the show hw-module slot-number/subslot-number errors spi4 command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SPA_DATABUS-3-SPI4_SINK_FIFO_OVERFLOW: [chars] [chars] - An error condition on the data bus between the SPA and the SIP has occurred. Explanation An error condition on the data bus between the SPA and the SIP has occurred. Possible

causes include misconfiguration of maxburst parameters, incorrect FIFO sizing, or improper FIFO threshold settings. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show hw-module slot-number/subslot-number errors spi4 command to gather data that may help identify the cause of the error. You may need to load a more recent version of the software. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


1473


Error Message %SPA_DATABUS-3-SPI4_SINK_FIFO_UNDERRUN: [chars] [chars] - An error condition on the data bus between the SPA and the SIP has occurred. Explanation An error condition on the data bus between the SPA and the SIP has occurred. Possible

causes include misconfiguration of maxburst parameters, incorrect FIFO sizing, or improper FIFO threshold settings. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show hw-module slot-number/subslot-number errors spi4 command to gather data that may help identify the cause of the error. You may need to load a more recent version of the software. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SPA_DATABUS-3-SPI4_UNALIGNED_BURST: [chars] [chars] - An error on the data bus has occurred. Explanation Under normal conditions, the transitions from the data burst state to payload control or

idle control are possible only on integer multiples of 8 cycles or upon the end of a packet. This error happens if the modelware (MW) bit flips on the bus with coincidental good 4-bit diagonal interleave parity (dip4) or due to a malfunctioning source. Recommended Action Power down and reseat the card. If this error recurs, verify whether the failed

hardware is the SIP or the SPA, because this error will occur only with a hardware failure. If supported by the platform, try running diagnostics on the suspected hardware. Copy the message exactly as it appears on the console or in the system log. Enter the show hw-module slot-number/subslot-number errors spi4 command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


1474

SPA_EEPROM Messages

SPA_EEPROM Messages This section contains shared port adapter (SPA) EEPROM messages.

SPA_EEPROM-3 Error Message %SPA_EEPROM-3-FIELD_NOT_FOUND: [chars]: Failed to find content of field type [hex] with data size = [dec] bytes. The EEPROM might require an update. Explanation The system failed to find the content of the specified field type from the SPA EEPROM. The format of the EEPROM of the specified SPA might not be up to date. Recommended Action Retry the operation. If the problem persists, copy the message exactly as it

appears on the console or in the system log. Enter the show idprom module slot-number/subslot-number dump command or the show diag subslot slot-number/subslot-number command (depending on the support of the platform) to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SPA_EEPROM-3-FORMAT_ERROR: [chars]: [chars]. The EEPROM might require an update. Explanation A format error has been detected in the EEPROM of the specified SPA. The type of error

is specified in the message. Recommended Action Retry the operation. If the problem persists, copy the message exactly as it



1475

SPA_EEPROM Messages

Error Message %SPA_EEPROM-3-READ_FAILED: Failed to read the EEPROM content of [chars] in [chars] (offset=[hex], num_byte=[int]) Explanation The system failed to read the EEPROM content of the specified SPA with the specified

offset value and number of bytes to read. Recommended Action Retry the operation. If the problem persists, copy the message exactly as it


Error Message %SPA_EEPROM-3-RPC_FAILED: Failed to send RPC message to [chars] EEPROM of [chars] in [chars] - [chars] Explanation The system failed to send an RPC message to read or write the EEPROM of the specified

SPA. The cause of the error condition is shown in the message. Recommended Action Retry the operation. If the problem persists, copy the message exactly as it

appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SPA_EEPROM-3-SET_WR_PROTECT_FAILED: [chars]: Failed to [chars] the EEPROM write protect mode on [chars]. Explanation The system failed to enable or disable the write protect mode for the SPA EEPROM on

the specified device. This might happen if the device were busy performing other tasks. Recommended Action Retry the operation. If the problem persists, copy the message exactly as it

appears on the console or in the system log. Enter the show idprom module slot-number/subslot-number dump command or the show diag subslot slot-number/subslot-number command (depending on the support of the platform) to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at


1476

SPA_EEPROM Messages


Error Message %SPA_EEPROM-3-SW_ERROR: NULL Explanation There is a problem in the internal software coding. This message should not be seen



Error Message %SPA_EEPROM-3-WRITE_FAILED: Failed to write the EEPROM content for [chars] in [chars] (offset=[hex], num_byte=[int]) Explanation The system failed to write data into the EEPROM of the specified SPA with the specified offset value and number of bytes to write. Recommended Action Retry the operation. If the problem persists, copy the message exactly as it



1477

SPA_ETHER Messages

SPA_EEPROM-4 Error Message %SPA_EEPROM-4-CANNOT_UPDATE: [chars]: EEPROM data cannot be updated at this moment because the SPA is not in service. Explanation The EEPROM update operation cannot be performed because the specified SPA could

have been in an out-of-service state, an admin down state, or is trying to get initialized. Recommended Action Retry the operation when the SPA is in service. Check the operational status of

the SPA with the show hw-module subslot slot-number/subslot-number oir command. If the SPA is shown to be in the out-of-service state, correct the specified problem before the retry to update EEPROM. If the state shown is admin down, reenable the SPA by entering the no hw-module subslot slot-number/subslot-number shutdown command.

Error Message %SPA_EEPROM-4-DATA_TRUNCATED: [chars]: Data will be truncated for field type [hex] - size ([int] bytes) too big for this field type ([int] bytes) Explanation The provided data to be written into the specified field type of the SPA EEPROM is too

big. The data will be truncated to fit into the allowed space. Recommended Action Retry the operation with a data size that will fit into the specified size for the

field type.

SPA_ETHER Messages This section contains 4-port 10/100, 2-Port 10/100/1000 Ethernet shared port adapter (SPA) messages.

SPA_ETHER-1 Error Message %SPA_ETHER-1-ALLOCFAIL: Subslot [dec]/[dec], [chars] allocation failure ([chars]) Explanation The router has failed to allocate sufficient memory for a software module on the

Ethernet SPA located in the specified subslot. The error message indicates the modular services card slot, the SPA subslot, the SPA type and the name of the software module. Recommended Action Perform an OIR of the SPA located in the specified subslot. Before removing

the SPA, enter the hw-module subslot stop command. Remove the SPA, wait 5 seconds, and reinsert the SPA into the MSC. Enter the show memory summary command to attempt to determine the cause of the error. Reduce system activity to reduce memory demands. If conditions warrant, upgrade to a larger memory configuration. If you require further assistance, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support


1478

SPA_ETHER Messages


SPA_ETHER-3 Error Message %SPA_ETHER-3-HW_ERROR: Subslot [dec]/[dec], [chars] Hardware device error ([chars]) detected, reactivating the SPA Explanation An internal hardware device error has occurred on the Ethernet SPA. The message text

specifies the modular services card slot, the SPA subslot, the SPA type, and the name of the hardware device. The SPA has been deactivated and reactivated to resolve the problem. If the error occurs more than five times within an hour, no further attempts to reactivate the SPA will be made. This condition is most likely due to an unrecoverable hardware failure. Recommended Action Perform an OIR operation of the SPA located in the specified subslot. Before

removing the SPA, enter the hw-module subslot stop command. Remove the SPA, wait 5 seconds, and reinsert the SPA into the MSC. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show diag command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SPA_ETHER-3-INITFAIL: Subslot [dec]/[dec], [chars] initialization failure ([chars]) Explanation Initialization of an internal device on the Ethernet SPA in the specified subslot has

failed. The message text specifies the modular services card slot, the SPA subslot, the SPA type, and the name of the device that failed to initialize. The message also provides the interface name and other details about the error. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1479

SPA_ETHER Messages

Error Message %SPA_ETHER-3-INVALID_PORT: Subslot [dec]/[dec], [chars] Incorrect port number ([dec]) specified for SPA Explanation An internal error has been encountered by the Ethernet software driver for the SPA. The

message text specifies the modular services card slot, the SPA subslot, the SPA type, and the invalid interface port number. This condition is caused by a software error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA_ETHER-3-SEND_MSG: Subslot [dec]/[dec], [chars] Failed to notify driver process about a line state change in one of the SPA interfaces Explanation A state change has occurred on the line of one of the interface ports on the Ethernet SPA.

The message text specifies the modular services card slot, the SPA subslot, and the SPA type. Information to identify the affected interface port on the SPA is not provided. The affected interface might not function properly. Recommended Action Perform an OIR operation of the SPA located in the specified subslot. Before


Error Message %SPA_ETHER-3-SFP_EEPROM_READ_FAIL: [chars], [chars] initialization failure ([chars]) Explanation The pluggable transceiver module (SFP) on the Ethernet SPA could not be initialized

because the EEPROM on the pluggable transceiver module (SFP) could not be read. The error message specifies the modular services card slot, the SPA subslot, the SPA port, the SPA type and the name of the device that failed to initialize. Recommended Action Ensure that the pluggable transceiver module (SFP) is properly seated in the

SPA port by reseating it. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply


1480

SPA_ETHER Messages

clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SPA_ETHER-3-SFP_SEC_FAIL: [chars], [chars] initialization failure ([chars]) Explanation The pluggable transceiver module (SFP) on the Ethernet SPA could not be initialized

because it could not pass the SFP security check. The error message specifies the modular services card slot, the SPA subslot, the SPA port, the SPA type and the reason for the security check failure. Recommended Action Try replacing the pluggable transceiver module (SFP) with a Cisco approved

pluggable transceiver module (SFP). If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SPA_ETHER-3-SPI4_NOT_IN_SYNC: Subslot [dec]/[dec], [chars] SPI4 internal interface is not synchronized with the modular services card for the SPA located in the specified subslot. Explanation The SPI4 internal path between the modular services card and the SPA is not

synchronized. The message text specifies the modular services card slot, the SPA subslot, and the SPA type. This error indicates that either the SPA is not properly inserted into the MSC or a hardware failure has occurred on the SPA. Recommended Action Perform an OIR operation of the SPA located in the specified subslot. Before



1481

SPA_ETHER Messages

Error Message %SPA_ETHER-3-TCAM_ACCESS_FAILURE: Subslot [dec]/[dec], [chars] Failure in accessing the TCAM device ([chars], status = [hex]) Explanation An attempt to access the TCAM device on the SPA has failed. The message text specifies the modular services card slot, the SPA subslot, and the SPA type. This condition indicates a hardware failure. Recommended Action Perform an OIR operation of the SPA located in the specified subslot. Before


Error Message %SPA_ETHER-3-TCAM_INST_CREATE_FAIL: Subslot [dec]/[dec], [chars] Failed to create the TCAM management instance (status = [hex]) Explanation The SPA failed to create the internal data structures that are required to manage TCAM

entries. The message text specifies the modular services card slot, the SPA subslot, and the SPA type. This condition indicates a software error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA_ETHER-3-TCAM_MAC_DA_TABLE_ACCESS_FAILURE: Subslot [dec]/[dec], [chars] Failure in accessing the TCAM destination MAC address table ([chars]) Explanation The TCAM destination MAC address table for the SPA interface could not be accessed.

The message text specifies the modular services card slot, the SPA subslot, the SPA type, and the affected interface number. This error indicates either a software error or a hardware failure. Recommended Action Perform an OIR operation of the SPA located in the specified subslot. Before

removing the SPA, enter the hw-module subslot stop command. Remove the SPA, wait 5 seconds, and reinsert the SPA into the MSC. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show diag command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply


1482

SPA_ETHER Messages

clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SPA_ETHER-3-TCAM_MAC_DA_TABLE_INVALID: Subslot [dec]/[dec], [chars] Destination MAC address filter table is invalid for interface [dec] Explanation The internal data structure that is used by the SPA to manage the destination MAC address filtering for an interface port is invalid. The message text specifies the modular services card slot, the SPA subslot, the SPA type, and the interface port. This condition indicates a software error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA_ETHER-3-TCAM_VLAN_TABLE_ACCESS_FAILURE: Subslot [dec]/[dec], [chars] Failure in accessing the TCAM VLAN address table ([chars]) Explanation An attempt to access the TCAM VLAN table for the SPA has failed. The message text

specifies the modular services card slot, the SPA subslot, the SPA type, and the affected interface. This condition indicates either a software error or a hardware failure. Recommended Action Perform an OIR operation of the SPA located in the specified subslot. Before



1483

SPA_ETHER Messages

Error Message %SPA_ETHER-3-TCAM_VLAN_TABLE_INVALID: Subslot [dec]/[dec], [chars] VLAN filter table is invalid for interface [dec] Explanation The internal data structure used by the SPA to manage the VLAN filtering is invalid. The SPA supports a separate VLAN table for each interface. The message text specifies the modular services card slot, the SPA subslot, the SPA type, and the affected interface. This condition indicates a software error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


SPA_ETHER-4 Error Message %SPA_ETHER-4-BAY_NOT_FOUND: Subslot [dec]/[dec], [chars] Failed to get the bay information Explanation A software data structure could not be retrieved for the subslot. The message text

specifies the modular services card slot, the affected subslot, and the SPA type. This condition indicates a software error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA_ETHER-4-NOPROCESS: Subslot [dec]/[dec], [chars] creation of [chars] process failed Explanation A software process to manage the SPA could not be created. The message text specifies

the modular services card slot, the SPA subslot, the SPA type, and the name of the process. This error message will be accompanied by a Cisco IOS software error message that gives more information about the cause for this failure. Recommended Action Enter the show memory summary command to attempt to determine the cause

of the error. Reduce system activity to reduce memory demands. If conditions warrant, upgrade to a larger memory configuration. If you require further assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact


1484

SPA_ETHER Messages

your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SPA_ETHER-4-TCAM_MAC_DA_TABLE_FULL: Subslot [dec]/[dec], [chars] Destination MAC address filter table is full for interface [dec], MAC address = [enet], mask = [enet] Explanation The TCAM destination MAC address table for an interface on the SPA is full. The SPA

supports a separate MAC table for each interface. The message text specifies the modular services card slot, the SPA subslot, the SPA type, the affected interface, and the MAC address. The specified MAC address will not be added to the TCAM table. Recommended Action Attempt to remove some of the registered MAC addresses for the interface by

changing the interface configuration. To verify the MAC addresses currently in use by an interface, enter the show controllers command.

Error Message %SPA_ETHER-4-TCAM_VLAN_TABLE_FULL: Subslot [dec]/[dec], [chars] VLAN filter table is full for interface [dec], VLAN identifier = [dec] Explanation The TCAM VLAN filter table for an interface on the SPA is full. The SPA supports a

separate MAC table for each interface. The message text specifies the modular services card slot, the SPA subslot, the SPA type, the affected interface, and the VLAN entry that failed. The specified VLAN identifier will not be added to the TCAM table. Recommended Action Attempt to remove some of the registered VLANs for the interface by changing

the interface configuration. To verify the VLAN IDs currently in use by an interface, enter the show controllers command.

Error Message %SPA_ETHER-4-TEMPERATURE_READ_FAIL: Subslot [dec]/[dec], [chars] Failed to read current temperature from sensor [dec], (status = [hex]) Explanation The current temperature reading on the SPA cannot be determined. The message text

specifies the modular services card slot, the SPA subslot, and the SPA type. This condition indicates a hardware failure. Recommended Action Perform an OIR operation of the SPA located in the specified subslot. Before



1485

SPA_ETHER Messages

Error Message %SPA_ETHER-4-VOLTAGE_READ_FAIL: Subslot [dec]/[dec], [chars] Failed to read the current voltage for [chars] supply Explanation The current voltage reading for the SPA voltage supply cannot be determined. The error

message indicates the modular services card slot, the SPA subslot, the SPA type and the identification of the voltage supply. This error indicates a hardware failure. Recommended Action Perform an OIR operation of the SPA located in the specified subslot. Before


SPA_ETHER-6 Error Message %SPA_ETHER-6-TCAM_VLAN_FILTERING_DISABLED: Subslot [dec]/[dec], [chars] TCAM VLAN filter table is full, disabling VLAN filtering for interface [dec] Explanation VLAN filtering for the specified interface has been disabled because the VLAN table is full. This means that the SPA will transmit frames destined for any VLAN ID to the route processor. The SPA supports a separate VLAN table per interface. The error message indicates the modular services card slot, the SPA subslot, the SPA type, and the affected interface. Recommended Action To verify the VLAN IDs that are currently in use by an interface, enter the show controllers command. You can remove some of the existing VLANs from the interface configuration to reactivate VLAN filtering on the indicated interface.

Error Message %SPA_ETHER-6-TCAM_VLAN_FILTERING_ENABLED: Subslot [dec]/[dec], [chars] Enabling VLAN filtering for interface [dec] Explanation VLAN filtering for the specified interface is enabled. The SPA supports a separate

VLAN table per interface. The error message indicates the modular services card slot, the SPA subslot, the SPA type, and the affected interface. Recommended Action VLAN filtering has been reactivated, and the VLAN table is no longer full.

This means that the SPA will transmit frames to the route processor only for those VLAN IDs configured on the specified interface.To verify the VLAN IDs that are currently in use by an interface, enter the show controllers command.


1486

SPA_FPD Messages

SPA_FPD Messages This section contains shared port adapter (SPA) field-programmable device (FPD) messages.

SPA_FPD-2 Error Message %SPA_FPD-2-PWR_NO_OK: SPA POWER OK signal is not asserted for [chars] in [chars] for FPD upgrade. Explanation A check for the SPA POWER OK signal assertion failed. This might indicate a hardware

problem with the SPA. Recommended Action Contact your Cisco technical support representative to have the SPA replaced.

SPA_FPD-3 Error Message %SPA_FPD-3-GETVER_FAILED: Failed to get FPD version for SPA in subslot [dec]: [chars]. Explanation Failed to get a field-programmable device (FPD) version due to either an IPC problem

or an operation error. The card will be disabled. Recommended Action Check the SPA seating and the SPA status. Ensure compatibility among FPD,

Cisco IOS, and possible SPA firmware by comparing the output of the show hw-module subslot fpd command with Cisco IOS release notes. Obtain the Cisco IOS version by entering the show version command.

Error Message %SPA_FPD-3-JTAG_ERR: [chars]: Failed to program a [chars] FPD image file. Error code [hex]. Explanation An error occurred while attempting to program a SPA FPGA using the JTAG bus. It

could be caused by an outdated carrier card FPGA or SPA connection, or it may also result from an internal software error. Recommended Action Reseat the SPA and retry the upgrade. Verify that the carrier card FPGA is

current. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


1487

SPA_FPD Messages

Error Message %SPA_FPD-3-PWR_OFF_FAILED: Failed to power-off [chars] in [chars] for FPD offline upgrade within [dec] seconds. Explanation The power-off operation of the indicated SPA failed within the number of specified

seconds. This might indicate that the waiting time for the SPA to power off is not long enough, which can happen if the SPA has many interfaces configured. Recommended Action Retry the upgrade operation again later. If the problem persists, remove the

configuration of the SPA before retrying the upgrade operation.

Error Message %SPA_FPD-3-SMM665_CONF_WRITE_ERROR: [chars]: Failed to write new configuration into SMM665 device. Explanation An error occurred while attempting to write to the SMM665 through the Cisco 2-wire

(C2W) serial interface from the SPA carrier card. The C2W serial interface may be busy. Recommended Action Retry the upgrade operation again later. If the problem persists, remove the

configuration of the SPA before retrying the upgrade operation.

Error Message %SPA_FPD-3-SW_ERROR: NULL Explanation This is an internal software error, which should not be seen under normal operation. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA_FPD-3-UPGRADE_FAILED: Failed to upgrade FPD for SPA in subslot [dec], [chars]. Explanation The FPD image upgrade operation has failed. This error is specific to the SPA. The

cause could be a wrong image file, an error in accessing FPGA storage, or a physical interrupt, such as a power failure or card removal. Depending on the SPA type and error cause, the card could be in an unusable status. Normally the system automatically reattempts the upgrade and shuts down the card after repeated failures. Recommended Action Do not interrupt the system while an FPD upgrade is in progress. Obtain the matching FPD package. Refer to the Cisco IOS release notes for more information on obtaining the correct FPD package for the SPA. Review the output of the RP FPD logs.


1488

SPA_HA Messages

SPA_HA Messages This section contains SPA high availability (HA) messages.

Error Message %SPA_HA-3-BADSWITCHOVER: [chars]: Invalid HA event detected: [chars] Explanation An HA switchover event occurred before initialization was finished. Recommended Action Copy the message exactly as it appears on the console or in the system log.


SPA_IPSEC Messages This section contains IPsec VPN SPA (SPA-IPSEC) messages.

Error Message %SPA_IPSEC-3-BOOT_FAIL: [chars]: [chars]. Explanation The SPA failed to boot up for the specified reason. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %SPA_IPSEC-3-BRDTYPE: Incorrect jacket card board type [dec] detected. Explanation The detected SIP/SSC module type is not a C7600-SSC-400 or C7600-SSC-600. Recommended Action Install the module carrier type that supports your SPA.


1489

SPA_IPSEC Messages

Error Message %SPA_IPSEC-3-OVERRIDE: [chars]: Overriding bundled firmware with ssc[int]-[chars]. Explanation The specified file was used instead of a bundled file. This is a debugging feature. Recommended Action This is an informational message only. No action is required.

Error Message %SPA_IPSEC-3-PROC_FAIL: [chars]: [chars] Process creation failed. Explanation Cannot allocate memory for the specified process. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %SPA_IPSEC-3-PWRCYCLE: SPA ([dec]/[dec]) is being power-cycled (Module not responding to keep-alive polling). Explanation The SPA has stopped responding to keepalive polling from the carrier card. The SPA has

been power-cycled. Recommended Action Once the SPA is back on line, retrieve the crash dump data that was saved on the bootflash of the supervisor engine. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SPA_IPSEC-3-QUACK: %s: Skipping quack authentication for hw ver %d.%d. Explanation Quack authentication was not performed for some prototype boards. Recommended Action No action is required.


1490

SPA-IPSEC-2G Messages

Error Message %SPA_IPSEC-3-SKIP_SPI: %s: Skipping SPI Init. Explanation SPI initialization will not be performed. This is a debugging feature. Recommended Action No action is required.

Error Message %SPA_IPSEC-3-SPA_BUS: %s: SPA Bus timeout. Explanation A timeout occurred while trying to access the SPA. Recommended Action Reseat the board and try again. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

SPA-IPSEC-2G Messages This section contains IPsec VPN SPA (SPA-IPSEC-2G) messages.

SPA-IPSEC-2G-2 Error Message %SPA-IPSEC-2G-2-ACE_PKA_KAT_FAILURE: PKA: Known Answer Test failure: [chars] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA_IPSEC_2G-2-ACEIKEADRVPKRM: Decode of RSA Private Key [dec] failed Explanation Data error in PKI certificate. Recommended Action Verify certificate server for proper operation.


1491


Error Message %SPA_IPSEC_2G-2-ACEIKEAPRVCREDRV: Driver refused RSA Private Key Explanation Attempt to create too many PKI sessions on SPA. Recommended Action Reduce system load.

Error Message %SPA_IPSEC_2G-2-ACEIKEAPRVDRV: Driver refused RSA Private Key Explanation Attempt to create too many PKI sessions on SPA. Recommended Action Reduce system load.

Error Message %SPA_IPSEC_2G-2-ACEIKEAPRVRMDRV: Decode of RSA Private Key [dec] failed Explanation Data error in PKI certificate. Recommended Action Verify certificate server for proper operation.

Error Message %SPA_IPSEC_2G-2-ACENVRAMCSUM: NVRAM Checksum failed Explanation Error reported by firmware. Recommended Action Contact TAC.

Error Message %SPA_IPSEC_2G-2-ACENVRAMWR: Write to nvram failed Explanation Error reported by firmware. Recommended Action Contact TAC.

Error Message %SPA-IPSEC-2G-2-ACESCPERROR: Null MAC address pointer in SCP module Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1492


SPA-IPSEC-2G-3 Error Message %SPA_IPSEC_2G-3-ACEI0BADPARAM: PcpManCreateTunn: cannot create tunnel with expiring Sa Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, contact TAC with the

output of show tech-support command .

Error Message %SPA-IPSEC-2G-3-ACEI0TCAMFAILED: SpdSpInstall: cannot install Sp [dec]: TmInsertSp failed Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI1BADPARAM: SpdSpInstall: cannot install generic SP [dec] with non-zero priority Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI1OUTOFSA: PcpQOpCreSaBegin: cannot create new Sa using SpdMan Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message

exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools


1493



Error Message %SPA_IPSEC_2G-3-ACEI10OUTOFCME: PcpManCreateAcl: cannot allocate new Acl for aclId=[int] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA_IPSEC_2G-3-ACEI11NESTOVERFLOW: SpdSaAddTmInsCb: cannot have more than [dec] pending nested callbacks from TcamMan Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI11OUTOFSEL: PcpAclGetSpSelSet: cannot clone SelSet for ACL [dec] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message

exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at


1494



Error Message %SPA-IPSEC-2G-3-ACEI2BADPARAM: PcpManUpdateFlow: cannot update flow [dec] with invalid ID Explanation Configuration not downloaded correctly. Recommended Action Can safely ignore.

Error Message %SPA-IPSEC-2G-3-ACEI12IDNOTINUSE: PcpManRemoveAcl: cannot remove non-existing access list [int] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI12OUTOFSAPAR: SpdSaSetKeys: cannot allocate new SaPar for Sa [dec] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message



1495


Error Message %SPA-IPSEC-2G-3-ACEI13IDINUSE: PcpManRemoveAcl: cannot remove access list [int] while in use Explanation An error has been reported by the firmware. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI3OUTOFSEL: PcpQOpActSaBegin: cannot allocate selector set for outer Sa in flowId [dec] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI14BADCMEID: PcpSpdCreateCme: cannot create Cme with ID=[dec]: too large Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message



1496


Error Message %SPA-IPSEC-2G-3-ACEI14NOLOGA: SpdSaSetParams: cannot allocate SPI with TcamMan for Sa [dec] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI15IDNOTINUSE: PcpManRemoveCme: cannot remove non-existing Cme [int] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI16BADPARAM: PcpManActivateFlowAsync: cannot activate flow [dec]: Sa is in the wrong state Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message



1497


Error Message %SPA-IPSEC-2G-3-ACEI16TCAMFAILED: SpdSaTmInstallIn: cannot install inbound Sa [dec] with TcamMan Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI17BADPARAM: PcpManActivateFlowAsync: cannot activate non-existing flow [dec] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI17TCAMFAILED: SpdSaTmInstallOut: cannot install outbound Sa [dec] with TcamMan Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message



1498


Error Message %SPA-IPSEC-2G-3-ACEI18BADPARAM: PcpManCreateSMap: cannot create outbound SPD Map [int] with ingress access list [int] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI19BADCMEID: PcpManActivateFlowAsync: cannot activate flow [dec] with non-existing Cme [dec] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA_IPSEC_2G-3-ACEI1BADPARAM: SpdSpInstall: cannot install generic SP [dec] with non-zero priority Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message



1499


Error Message %SPA-IPSEC-2G-3-ACEI2BADPARAM: PcpManUpdateFlow: cannot update flow [dec] with invalid ID Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA_IPSEC_2G-3-ACEI1OUTOFSA: PcpQOpCreSaBegin: cannot create new Sa using SpdMan Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA_IPSEC_2G-3-ACEI20OUTOFSEL: PcpUtilSelSetFromPar: cannot allocate new selector set Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message



1500


Error Message %SPA_IPSEC_2G-3-ACEI26OUTOFSP: PcpCmeInstallNext: cannot create a new Sp Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA_IPSEC_2G-3-ACEI27BADPARAM: PcpManSetFlowKeys: cannot set keys for flow [dec]: SA is in the wrong state Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI2NESTOVERFLOW: SpdSaInitTmSaOut: outer outbound Sa [dec] of Sa [dec] is above nesting limit of [dec] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1501


Error Message %SPA-IPSEC-2G-3-ACEI20OUTOFSEL: PcpUtilSelSetFromPar: cannot allocate new selector set Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI21BADPARAM: PcpAclAppend: got too many denys for aclId=[dec], max is [dec] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI22BADPARAM: PcpAclAppend: got out-of-sequence line number [dec] for aclId=[dec] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message



1502


Error Message %SPA-IPSEC-2G-3-ACEI23IDINUSE: PcpSpdCreateCme: cannot create Cme with ID=[int]: already used Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI24BADPARAM: PcpAclAppend: got invalid ranges for selector set at lineNo=[dec], aclId=[dec] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI25IDINUSE: PcpAclAppend: got duplicate line number [dec] for aclId=[dec] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message



1503


Error Message %SPA-IPSEC-2G-3-ACEI26OUTOFSP: PcpCmeInstallNext: cannot create a new Sp Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI27BADPARAM: PcpManSetFlowKeys: cannot set keys for flow [dec]: SA is in the wrong state Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI28IDINUSE: PcpQOpCreSaBegin: cannot create second Sa for flow [dec]: conditions for transport adj. are not met Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message



1504


Error Message %SPA-IPSEC-2G-3-ACEI29SPDFAILED: PcpCmeInstallNext: cannot install Sp [dec] with SpdMan Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI3NESTOVERFLOW: SpdSaGetXformSeq: outer inbound Sa [dec] of Sa [dec] is above nesting limit of [dec] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI3OUTOFSEL: PcpQOpActSaBegin: cannot allocate selector set for outer Sa in flowId [dec] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message



1505


Error Message %SPA-IPSEC-2G-3-ACEI30BADPARAM: PcpSpdUpdateCme: cannot update already queued Cme [int] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI31BADALENUM: PcpQOpActSaBegin: cannot find access list entry number [dec] for cmeId=[dec] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI32BADPARAM: PcpQOpActSaBegin: cannot delete old [chars]bound flow [dec] while activating [chars]bound flow [dec] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message



1506


Error Message %SPA-IPSEC-2G-3-ACEI33BADPARAM: PcpCmeActivateSa: got invalid lifetime values softSecs=[int], hardSecs=[int] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI34BADPARAM: PcpCmeActivateSa: got invalid lifetime values softKBytes=[int], hardKBytes=[int] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI35BADPARAM: PcpCmeIntersectSaWithSp: cannot activate flow [dec] with selector ranges not intersecting parent Sp Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message



1507


Error Message %SPA-IPSEC-2G-3-ACEI36BADSELADDR: PcpQOpActSaBegin: cannot activate per-host flow [dec] with addresses [dec].[dec].[dec].[dec] and [dec].[dec].[dec].[dec] not included in Sp [dec] selector sets Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI37OUTOFSEL: PcpQOpActSaBegin: cannot clone selector set to activate per-host flow [dec] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI38BADSELADDR: PcpQOpActSaBegin: cannot activate transport mode flow [dec] with addresses [dec].[dec].[dec].[dec] and [dec].[dec].[dec].[dec] not included in Sp’s selector sets Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message



1508


Error Message %SPA-IPSEC-2G-3-ACEI39BADPARAM: PcpTrInProcess: got invalid opcode [dec] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI4BADPARAM: PcpQOpCreSaBegin: got invalid addresses [int].[int].[int].[int] and [int].[int].[int].[int] for other Sa of flow [dec]: expected [int].[int].[int].[int] and [int].[int].[int].[int] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI40BADACLID: PcpManCreateCme: cannot create Cme with non-existing access list [int] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message



1509


Error Message %SPA-IPSEC-2G-3-ACEI41SPDFAILED: PcpQOpSaActivated: cannot finish activating Sa [dec] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI42QUEUEFULL: PcpCmeActivateSa: cannot activate Sa [dec]: queue is full Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI43BADPARAM: PcpAclAppend: got invalid line number [dec] for ACL [dec] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message



1510


Error Message %SPA-IPSEC-2G-3-ACEI44QUEUEFULL: PcpSpdCreateCme: cannot create Cme [int] (aclId=[int]): queue is full Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI45IDNOTINUSE: PcpManDestroyFlowAsync: cannot delete already deleted flow [dec] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI46BADPARAM: PcpQOpActSaBegin: cannot activate non-fully-specified Sa for Cme [dec] without Acl Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message



1511


Error Message %SPA-IPSEC-2G-3-ACEI47BADPARAM: PcpQOpActSaBegin: cannot activate Sa for manual Sp (cmeId=[dec],entry=[dec]), Sa already exists Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI48CMEINUSE: PcpManSetInitMode: cannot set fast init-mode in TcamMan: [dec] pending Ops, [dec] Flows and [int] Cmes already exist or TcamMan is busy Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI49BADPARAM: PcpManQueryFlow: cannot query flow [dec]: Sa is not active Explanation Configuration not downloaded correctly. Recommended Action Can safely ignore.

Error Message %SPA-IPSEC-2G-3-ACEI5BADPARAM: SpdSaActivate: cannot activate Sa [dec], old Sa [dec] already has successor Sa [dec] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message



1512



Error Message %SPA-IPSEC-2G-3-ACEI5OUTOFSA: PcpQOpCreSaBegin: cannot create new Sa for flow [dec] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI50CMEINUSE: PcpQOpRemCmeBegin: cannot remove Cme [dec]: TcamMan is in Init mode Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI51BADPARAM: PcpSpdCreateCme: got invalid flags (manual,dynamic,discover,drop,clear) = ([dec],[dec],[dec],[dec],[dec]), cmeId=[dec] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message



1513



Error Message %SPA-IPSEC-2G-3-ACEI52IDINUSE: PcpManCreateAcl: cannot process opcode [int] for Acl [int] in state [int] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI53BADPARAM: PcpManCreateAcl: cannot create Acl with id [int] out of range [0,[int]] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI54CMENOTREADY: PcpSpdCreateCme: cannot create Cme [int] with Acl [int] when Acl state is [int] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message



1514


Error Message %SPA-IPSEC-2G-3-ACEI55SPDFAILED: PcpQOpActSaBegin: cannot begin activating Sa [dec] for flowId [dec] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI56IDNOTINUSE: PcpManDestroyFlowAsync: cannot delete flow [dec] already being deleted Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI57CMEINUSE: PcpManSetInitMode: cannot set normal init-mode in TcamMan: there are pending Flows or Cmes Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message



1515


Error Message %SPA-IPSEC-2G-3-ACEI58IDNOTINUSE: PcpManDestroyFlowAsync: flow [dec] already queued for deletion Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI59BADPARAM: PcpCmeActivateSa: cannot activate flow [dec] as per-host with subset of Sp as a selector set Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI6BADPARAM: PcpTrInProcess: got invalid size [dec] for opcode [dec] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message



1516


Error Message %SPA-IPSEC-2G-3-ACEI6OUTOFSEL: SpdSpInstall: cannot compute SP’s permit-SelSets from mixed SelSet list Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI60SPDFAILED: PcpManSaUpdateError: cannot update Flow [dec] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI61BADPARAM: PcpQOpActSaBegin: cannot activate Sa for cmeId=[dec], entry=[dec] with bad spdId=[dec] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message



1517


Error Message %SPA-IPSEC-2G-3-ACEI62IDINUSE: PcpQOpCreSaBegin: cannot setup Flow [dec] in trans.adj. with outer SA in tunnel mode Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI63CMEINUSE: PcpManActivateFlowAsync: cannot activate flow [dec] while using fast policy mode Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI64BADPARAM: PcpQOpActSaBegin: got invalid ranges for selector set of fully-specified flow [dec] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message



1518


Error Message %SPA-IPSEC-2G-3-ACEI65BADPARAM: PcpManSetInitMode: got invalid flags [hex] for setting fast policy mode Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI66NOTREADY: PcpManUpdateFlow: cannot update flow [dec] when SA is not active Explanation Configuration not downloaded correctly. Recommended Action Can ignore safely.

Error Message %SPA-IPSEC-2G-3-ACEI67BADPARAM: PcpSpdCreateSMap: cannot create SMap [int] with Acl [int] when Acl state is [int] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI68BADPARAM: PcpAclAppend: got invalid flags [hex] at lineNo=[dec], aclId=[dec] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message



1519



Error Message %SPA-IPSEC-2G-3-ACEI69BADPARAM: PcpManCreateCme: cannot create Cme [int] with spdId [int] out of range [0,[int]] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI7BADPARAM: PcpManSetFlowKeys: cannot set keys for flow [dec]: invalid ID Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI7OUTOFSEL: SpdSaTmInstallOut: cannot compute outbound SA’s permit-SelSets from mixed SelSet list Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message



1520


Error Message %SPA-IPSEC-2G-3-ACEI70IDNOTINUSE: PcpManUpdateCme: cannot update non-existing Cme [int] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI71QUEUEFULL: PcpSpdUpdateCme: cannot update Cme [int]: queue is full Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI72QUEUEFULL: PcpSpdCreateSMap: cannot create SPD map with mapId [int]: queue is full Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message



1521


Error Message %SPA-IPSEC-2G-3-ACEI73BADPARAM: PcpSpdCreateSMap: cannot create SPD map with mapId [int] out of range [0,[int]] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI74IDINUSE: PcpSpdCreateSMap: cannot create SPD map with mapId [int] already in use Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI75TMFAILED: PcpSMapInstall: cannot insert SMap [int] with TcamMan Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message



1522


Error Message %SPA-IPSEC-2G-3-ACEI76BADPARAM: PcpSpdCreateSMap: cannot create SPD map [int] with invalid flags [hex] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI77BADPARAM: PcpManCreateSMap: cannot create SPD Map [int] using non-existent access list [int] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI78OUTOFSMAP: PcpSpdCreateSMap: cannot create SPD map [int]: out of memory Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message



1523


Error Message %SPA-IPSEC-2G-3-ACEI79BADPARAM: PcpQOpActSaBegin: cannot activate Sa for cmeId=[dec], entry=[dec] when Cme is not ready Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI80QUEUEFULL: PcpManDestroyFlowAsync: cannot delete flowId [dec]: operation queue is full Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI81IDNOTINUSE: PcpQOpDelSaBegin: cannot delete already deleted flow [dec] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message



1524


Error Message %SPA-IPSEC-2G-3-ACEI82QUEUEFULL: PcpManRemoveCme: cannot remove Cme with cmeId [int]: queue is full Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI83TMFAILED: PcpSpdInitialize: cannot insert SPD [int] with TcamMan Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI84BADPARAM: PcpManCreateSMap: cannot create SPD map [int] with spdId [int] out of range [0,[int]] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message



1525


Error Message %SPA-IPSEC-2G-3-ACEI85OUTOFSMAP: PcpManCreateSpd: cannot create SPD [int]: out of memory Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI86IDINUSE: PcpManActivateFlowAsync: cannot activate already active flow [dec] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI87BADPARAM: PcpManCreateFlow: cannot create Flow with id=[dec], max is [dec] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message



1526


Error Message %SPA-IPSEC-2G-3-ACEI88IDNOTINUSE: PcpManRemoveSMap: cannot remove non-existing SMap [int] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI89OUTOFCME: PcpSpdCreateCme: cannot allocate new Cme for aclId=[int] Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message


Error Message %SPA-IPSEC-2G-3-ACEI92QUEUEFULL: PcpManCreateFlow: cannot create flowId [dec]: operation queue is full Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply crypto map. If the failure persists, copy the message



1527


Error Message %SPA_IPSEC_2G-3-ACEIKEADELCB: [chars]:[dec]: unexpected ([dec]) error on delete callback Explanation Probable software bug. Recommended Action Contact TAC.

Error Message %SPA_IPSEC_2G-3-ACEPKARSAPRVXCR: PKA: PkaRsaPrivXcrypt() invalid input buffer length [dec] Explanation Data error in PKI certificate. Recommended Action Verify certificate server for proper operation.

Error Message %SPA_IPSEC_2G-3-ACEPKARSAPUBXCRBUFLEN: PKA: PkaRsaPubXcrypt() invalid input buffer length [dec] Explanation Data error in PKI certificate. Recommended Action Verify certificate server for proper operation.

Error Message %SPA_IPSEC_2G-3-ACEPKASK0LENCROP2: PKA: 0 length crypto operation Explanation Data error in PKI certificate. Recommended Action Verify certificate server for proper operation.

Error Message %SPA_IPSEC_2G-3-ACEPKASK0LENCRYOP3: PKA: 0 length crypto operation Explanation Data error in PKI certificate. Recommended Action Verify certificate server for proper operation.

Error Message %SPA_IPSEC_2G-3-ACEPKASK0LENOP: PKA: 0 length crypto operation Explanation Data error in PKI certificate. Recommended Action Verify certificate server for proper operation.

Error Message %SPA_IPSEC_2G-3-ACEPKASK1STFRAGSHRT: PKA: 1st frag too short for crypto operation Explanation Data error in PKI certificate. Recommended Action Verify certificate server for proper operation.


1528


Error Message %SPA_IPSEC_2G-3-ACEPKASKDESNOTMUL82: PKA: DES/3DES data length not multiple of 8 Explanation Data error in PKI certificate. Recommended Action Verify certificate server for proper operation.

Error Message %SPA_IPSEC_2G-3-ACEPKASKDESNOTMULT8: PKA: DES/3DES data length not multiple of 8 Explanation Data error in PKI certificate. Recommended Action Verify certificate server for proper operation.

Error Message %SPA_IPSEC_2G-3-ICPUBADGRESA: Invalid GRE SA - can’t find match. saptr:[hex] Explanation Error reported by firmware. Recommended Action Contact TAC with output from the show pcp sas command.

Error Message %SPA_IPSEC_2G-4-ICPUPP3: Illegal pkt dst:[dec].[dec].[dec].[dec] proto:[dec] spi:[hex], no match on SA SPI [hex]. Explanation Auditable event. Recommended Action To see the details, enter the show crypto ipsec sas command.

Error Message %SPA-IPSEC-2G-3-SPI_NOT_AVAIL: SPI [hex] is not available Explanation Crypto connect config could not be programmed correctly. Recommended Action Remove and reapply crypto connect commands. If the failure persists, copy the



1529


SPA-IPSEC-2G-4 Error Message %SPA_IPSEC_2G-4-ACEIPCMPINGPRE: IPC ping ([chars]): premature ping...awaiting response to previous ping Explanation Error reported by firmware. Recommended Action Contact TAC.

Error Message %SPA_IPSEC_2G-4-ACEIPCMPINGSEQ: IPC ping ([char]CPU): seq.# does not match: Expected [dec], got [dec] Explanation Error reported by firmware. Recommended Action Contact TAC.

Error Message %SPA_IPSEC_2G-4-ACEIPCMPINGSKIP: IPC ping ([char]CPU): Skipped [dec] times before receiving reply Explanation Error reported by firmware. Recommended Action Contact TAC.

Error Message %SPA_IPSEC_2G-4-ACEIPCXNOBUF2: ICPU unable to allocate msg buf for Ping Reply: [dec] Explanation Error reported by firmware. Recommended Action Contact TAC.

Error Message %SPA_IPSEC_2G-4-ACEIPCXNOBUF3: OCPU unable to allocate msg buf for Ping Reply: [dec] Explanation Error reported by firmware. Recommended Action Contact TAC.

Error Message %SPA_IPSEC_2G-4-ACEIPCXPINGNOBUF: [dec] srcCPU unable to allocate msg buf for Ping Reply in CB: [dec] Explanation Error reported by firmware. Recommended Action Contact TAC.


1530


Error Message %SPA-IPSEC-2G-4-ACETCAMFULLINSMANSP: Full SA insertion for a manual SP. Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply the crypto map. If failure persists, copy the message


Error Message %SPA-IPSEC-2G-4-ACETCAMPKTNOSA: Packet event for a non-existing SA. Explanation Configuration not downloaded correctly. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA-IPSEC-2G-4-ACETCAMPKTNOSP: Packet event for a non-existing SP. Explanation Configuration not downloaded correctly. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1531


Error Message %SPA_IPSEC_2G-4-ACETCAMPKTNOSP1: EarlyPkt Exit1. Explanation Configuration not downloaded correctly. Recommended Action Remove and reapply the crypto map. If failure persists, contact TAC with the

output of the show tech-support command.





Error Message %SPA-IPSEC-2G-4-ACEXCPUALLOC: IPC: Unable to allocate and send STATFLUSH. Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA_IPSEC_2G-4-ACEXCPUALLOC: IPC: Unable to allocate and send STATFLUSH. Explanation Error reported by firmware. Recommended Action Transient error. No action.

Error Message %SPA_IPSEC_2G-4-ACEXCPUALLOC2: IPC: Unable to allocate IPC to set debug flag. Explanation Error reported by firmware. Recommended Action Transient error. No action.


1532


Error Message %SPA_IPSEC_2G-4-ACEXCPUALLOC3: IPC: Unable to allocate IPC to start 5840 test. Explanation Error reported by firmware. Recommended Action If persistent, restart VPNSPA.

Error Message %SPA-IPSEC-2G-4-ACEXCPUCMMTU2: CFGMON: Failed to set MTU. Invalid data [dec], ifvlan [hex]. Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA-IPSEC-2G-4-ACEXCPUCMRESP: XcpuCfgMonReqCallback:Can’t respond to host. Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA-IPSEC-2G-4-ACEXCPUCMRESP3: XcpuCfgMonReqCallback:Global stats...Can’t respond to host. Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1533



Error Message %SPA-IPSEC-2G-4-ACEXCPUCMRESP4: XcpuCfgMonReqCallback: PerFlow Stats....Can’t respond to host. Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA-IPSEC-2G-4-ACEXCPUCMRESP5: XcpuCfgMonReqCallback: PerFlow Stats....Can’t respond to host. Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA_IPSEC_2G-4-ANTIREPLAYWINDOWDEFAULT: Using default replay window for SA SPI [hex] Explanation Unable to allocate more than 8K extended replay windows. Recommended Action New SAs will use the default window size if no resource is available.

Error Message %SPA_IPSEC_2G-4-BULKIP: Wrong type [dec] size:5d. Explanation System IP address not downloaded correctly. Recommended Action Remove and reapply the IP address on the interfaces, and if the problem

persists, contact TAC.


1534


Error Message %SPA-IPSEC-2G-4-DUMPMEM: [hex]: [hex] [hex] [hex] [hex] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA-IPSEC-2G-4-EDSDEBUG: SingleBufErr:([hex]) Explanation Multibuffer packet received during FIPS test. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA-IPSEC-2G-4-FIPSCHECK2: FIPS RCVD Multi-buffer Packet. Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1535


Error Message %SPA-IPSEC-2G-4-FIPSCHECK3: FIPS Failed Packet Comparison. Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA-IPSEC-2G-4-FIPSCHECK4: FIPS Test Completed Successfully. Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA-IPSEC-2G-4-ICPUFRAG1: PktReasmSetAction failed. Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1536


Error Message %SPA-IPSEC-2G-4-ICPUPP2: SaCheckSelectors: Illegal pkt, no valid SA Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA-IPSEC-2G-4-ICPUPP3: Illegal pkt dst:[dec].[dec].[dec].[dec] proto:[dec] spi:[hex], no match on SA SPI [hex]. Explanation No matching SA was found for the received encrypted packet. This message is most

likely to occur during rekeying when the inbound SA is not yet established. Recommended Action If the message persists and packets are being lost, check whether the CPU is

overloaded or the crypto engine is oversubscribed.

Error Message %SPA-IPSEC-2G-4-ICPUPP4: Illegal pkt dst:[dec].[dec].[dec].[dec] proto:[dec] spi:[hex], no match on SA dst[dec].[dec].[dec].[dec] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA-IPSEC-2G-4-ICPUPP8: Illegal clear pkt src:[dec].[dec].[dec].[dec] dst:[dec].[dec].[dec].[dec] proto:[dec]. Explanation Clear packets were received that should have been encrypted. Recommended Action Check whether the remote peer has a correct security policy and SA to encrypt the packets. Compare IP addresses of the packets with crypto ACLs.


1537


Error Message %SPA-IPSEC-2G-4-ICPUPP9: Packet src:[dec].[dec].[dec].[dec] dst:[dec].[dec].[dec].[dec] seq num:[hex] failed replay check last seq num:[hex] for SA:[hex]. Explanation IPsec packets have failed the anti-replay check. A common cause is the use of QoS in

your network. With QoS, lower priority packets can arrive late, missing the anti-replay check window. When this condition occurs, higher level protocols can request retransmission so that functionality is not lost. Time-sensitive protocols, such as voice traffic, might be degraded due to dropped or late packets. Recommended Action Increase the anti-replay window size. If anti-replay checking is not needed,

disable it. Display the SA with the given index - show tacm ipr sa .

Error Message %SPA-IPSEC-2G-4-ICPUPP10: Packet src:[dec].[dec].[dec].[dec] dst:[dec].[dec].[dec].[dec] proto ESP, but not SA proto! Explanation The received packet’s protocol does not match the SA protocol. The SA expects AH, but

the packet uses ESP. Recommended Action Check whether the negotiated protocol matches the configured transform sets

of both peers. Contact TAC with outputs of show crypto ipsec sas command.

Error Message %SPA-IPSEC-2G-4-ICPUPP11: Packet src:[dec].[dec].[dec].[dec] dst:[dec].[dec].[dec].[dec] proto AH, but not SA proto! Explanation The received packet’s protocol does not match the SA protocol. The SA expects ESP, but the packet uses AH. Contact TAC with outputs of show crypto ipsec sas command. Recommended Action Check whether the negotiated protocol matches the configured transform sets

of both peers.

Error Message %SPA-IPSEC-2G-4-ICPUPP12: IPPE says IPSec, not pkt src:[dec].[dec].[dec].[dec] dst:[dec].[dec].[dec].[dec] proto:[dec]! Explanation An error has been reported by the firmware. Recommended Action No action.

Error Message %SPA-IPSEC-2G-4-ICPUPP13: Policy check failed for pkt src:[dec].[dec].[dec].[dec] dst:[dec].[dec].[dec].[dec] proto:[dec] SA index:[hex] Explanation The decrypted packet does not match the security policy. Recommended Action Check whether the security policy on both peers is symmetric.


1538


Error Message %SPA-IPSEC-2G-4-ICPUPP14: Pkt src:[dec].[dec].[dec].[dec] dst:[dec].[dec].[dec].[dec] proto:[dec] match deny; SA index [hex] Explanation Auditable event: Policy check failed for inbound packet. Recommended Action Check the crypto ACLs (whether the security policy on both peers is

symmetric).

Error Message %SPA-IPSEC-2G-4-ICPUPP15: SecInfo [hex] doesn’t match with SA [hex] SA index:[hex] Explanation An unexpected and unsupported nesting of SA was detected. Recommended Action Remove any nested SA.

Error Message %SPA-IPSEC-2G-4-ICPUPP16: Inner proto [dec] must be IPSec but is not Explanation An unexpected and unsupported nesting of SA was detected. Recommended Action Remove any nested SA.

Error Message %SPA-IPSEC-2G-4-ICPUSYSIPADDRADD: PktProcAddSysIpAddr: Unable to add local IP Addr [hex] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA-IPSEC-2G-4-ICPUSYSIPADDRDEL: PktProcAddSysIpAddr: Unable to delete local IP Addr [hex] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1539



Error Message %SPA-IPSEC-2G-4-ISAUNCA7: PktProcAtnModSas: Mismatch valid flag unca:invalid index:[hex] Explanation An error has been reported by the firmware. Recommended Action For details enter the show tcam ipr sa command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SPA-IPSEC-2G-4-RECOVERYDONE: CP Lockup Recovery - Done Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA-IPSEC-2G-4-RECOVERYFRAG: Ipfrag: Unable to transmit. CP Lockup Occured. Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1540


Error Message %SPA-IPSEC-2G-4-RECOVERYSTART: CP Lockup Recovery - Start(OCPU) Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA_IPSEC_2G-4-SINGLEIP: Wrong type [dec] size:[dec]. Explanation Error reported by firmware. Recommended Action No action.

Error Message %SPA_IPSEC_2G-4-SPDID: XcpuSetVlanSpdId: IpcAllocFailed Explanation Crypto connect config could not be programmed correctly. Recommended Action Remove and reapply crypto connect commands, and if problem persists,

contact TAC.

Error Message %SPA-IPSEC-2G-4-XCPURECOVERY: Error Disabling CP Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1541


SPA-IPSEC-2G-5 Error Message %SPA_IPSEC_2G-5-ACEPKADHGSHIDNOALL: PkaDhGenerateShared:DH session ID [dec] not allocated Explanation Invalid crypto ID used, command rejected, likely due to high system load. Recommended Action Reduce system load.

Error Message %SPA_IPSEC_2G-5-ACEPKADHGSIDINUSE: PKA: PkaDhGenerateSessionInt: DH session id [dec] already in use Explanation Invalid crypto ID used, command rejected, likely due to high system load. Recommended Action Reduce system load.

Error Message %SPA_IPSEC_2G-5-ACEPKADHGSINVID: PKA: PkaDhGenerateSessionInt: invalid DH session id [dec] Explanation Possible software bug. Recommended Action Contact TAC.

Error Message %SPA_IPSEC_2G-5-ACEPKAINITCMPL: BCM5820: Initialization complete Explanation These messages are normal after SPA bootup. Recommended Action Can ignore safely.

Error Message %SPA_IPSEC_2G-5-ACEPKANOBDESC: PKA: no data buffer descriptors available Explanation Out of buffers for crypto operation. Recommended Action Reduce system load.

Error Message %SPA_IPSEC_2G-5-ACEPKANOMOREDHGRPS: PKA: no more DH groups available Explanation Too many DH groups defined. Possible software error. Recommended Action Contact TAC.

Error Message %SPA_IPSEC_2G-5-ACEPKAPOSTRSTDELAY: PKA: BCM5820 post reset delay Explanation These messages are normal after SPA bootup. Recommended Action Can ignore safely.


1542


Error Message %SPA_IPSEC_2G-5-ACEPKARESUB: BCM5820: Resubmitting crypto request Explanation These messages are normal after SPA bootup. Recommended Action Can ignore safely.

Error Message %SPA_IPSEC_2G-5-ACEPKARESUBPK: BCM5820: Resubmitting PK request [hex] Explanation These messages are normal after SPA bootup. Recommended Action Can ignore safely.

Error Message %SPA_IPSEC_2G-5-ACEPKARSARMPSBUSYID: PKA: can’t remove busy RSA private session [dec] Explanation Trying to delete a busy RSA session. May be caused by out-of-order messaging on a

highly loaded system. Recommended Action Reduce system load.

Error Message %SPA_IPSEC_2G-5-ACEPKARST: PKA: BCM5820 in reset Explanation These messages are normal after SPA bootup. Recommended Action Can ignore safely.

Error Message %SPA_IPSEC_2G-5-ACEPKARSTCOMPL: BCM5820: Reset complete Explanation These messages are normal after SPA bootup. Recommended Action Can ignore safely.

SPA-IPSEC-2G-6 Error Message %SPA-IPSEC-2G-6-ACEPKAHWCRNGT: PKA: HW RNG has duplicate data, discarding Explanation Duplicate random data detected, duplicate data was discarded. Recommended Action This is normal operation if seen rarely. Contact TAC if seen frequently.

Error Message %SPA_IPSEC_2G-6-ACEPKAPKNOMCR2: PKA: no Public Key MCRs available Explanation Out of buffers for crypto operation. Recommended Action Reduce system load.


1543


Error Message %SPA-IPSEC-2G-6-ACEPKARNGDUP: PKA: A pseudo-random number was generated twice in succession. [hex][hex]; 0Unrecognized format ‘x%p’ 0Unrecognized format ‘x%p’ idx:[hex] Explanation An error has been reported by the firmware Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA_IPSEC_2G-6-ACEPKARNG: PKA: seed key is same as the seed, discarding Explanation Duplicate random data detected, duplicate data was discarded. Recommended Action This is normal operation if seen rarely. Contact TAC if seen frequently.

Error Message %SPA_IPSEC_2G-6-ACEPKARNGDUP: PKA: A pseudo-random number was generated twice in succession. [hex][hex]; 0Unrecognized format ‘x%p’ 0Unrecognized format ‘x%p’ idx:[hex] Explanation Duplicate random data detected, duplicate data was discarded. Recommended Action This is normal operation if seen rarely. Contact TAC if seen frequently. Recommended Action

Error Message %SPA-IPSEC-2G-6-ACEPKARNGKAT: PKA: RNG failed KAT Explanation Pseudo-RNG known-answer-test failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1544

SPA_MIB Messages

Error Message

SPA_MIB Messages This section contains SPA MIB messages.

Error Message %SPA_MIB-4-DATA_LEN: [chars]: MIB message lengths mismatch([chars]), expecting [dec] bytes, receiving [dec]. Explanation The MIB updates expected more data than was received. Recommended Action Copy the message exactly as it appears on the console or in the system log.


SPAN Messages This section contains Switched Port Analyzer (SPAN) messages.

SPAN-0 Error Message %SPAN-0-DISTRIBUTED_EGRESS_INCOMPATIBLE: Distributed egress SPAN is not recommended up to certain hardware revision of WS-X6708-10GE Explanation The distributed egress SPAN feature is not supported on WS-X6708-10GE hardware

revisions earlier than version 1.4. By default, the system will be in centralized mode. Attempting to enable the distributed feature will cause this warning message, but will not prevent the feature from being configured. Recommended Action Disable distributed egress SPAN by entering the no monitor session egress replication-mode distributed command in global configuration mode. For further caveats on the distributed egress SPAN feature, see the Cisco IOS software release notes and search for bug ID CSCso05127 using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl.


1545

SPAN Messages

SPAN-3 Error Message %SPAN-3-REDIR_HW_UNAVAIL: Redirect hardware resource not available [chars] Explanation The system could not allocate resource for redirecting BPDUs. A possible cause of this condition is that all available redirect registers in the policy feature card (PFC) are used by other features. Recommended Action Free up a redirect register in the PFC by unconfiguring features that use

redirect registers and retry allowing BPDUs for SPAN service modules. If protocol tunneling is configured on any ports, remove the protocol tunneling configuration from all ports to free up one redirect register.

Error Message %SPAN-3-SESS_DEC_CFG: SPAN hardware resource is in use. [chars] Explanation The system could not allocate a SPAN hardware resource for the feature specified in the

message. It is possible that a distributed EtherChannel has been configured in the system that is using SPAN hardware resource. Recommended Action Remove one or all of the distributed EtherChannels from the system and retry

the operation.

Error Message %SPAN-3-SESS_HW_UNAVAIL: SPAN hardware resource not available [chars] Explanation The system could not allocate a SPAN hardware resource for the feature specified in the

message. A possible cause of this condition is that all available SPAN source sessions are already in use. The system can be configured with a maximum of two SPAN source sessions or one RSPAN source session Recommended Action Remove one of the existing SPAN or RSPAN source sessions and retry the

operation.

SPAN-4 Error Message %SPAN-4-DISTRIBUTED_EGRESS_INCOMPATIBLE: Distributed egress SPAN is not recommended up to certain hardware revision of WS-X6708-10GE Explanation The distributed egress SPAN feature is not supported on hardware revisions earlier than

v1.4 of WS-X6708-10GE. By default the system will be in centralized mode. An attempt to enable the distributed feature will cause this warning message but will not prevent the feature from being configured. Recommended Action Disable distributed egress SPAN by entering the no monitor session egress replication-mode distributed command in global configuration mode. See the documentation release notes and DDTS CSCso05127 for more information on the caveats exposed by this feature.


1546

SPAN Messages

SPAN-5 Error Message %SPAN-5-ERSPAN_ADJ_TUNNEL: ERSPAN Destination behind a tunnel. Shutting down session [dec] Explanation The next hop to the IP address specified as the ERSPAN destination lies behind a tunnel. This configuration is not supported. The ERSPAN session is shut down when such a configuration is detected. Recommended Action Specify another ERSPAN destination IP address that does not have a tunnel as the next-hop adjacency.

Error Message %SPAN-5-PKTCAP_START: Packet capture session %d started Explanation A packet capture session was activated manually or after the scheduled time. Recommended Action Stop the capture if it is not required. By configuring the rate-limit value in the monitor session type capture configuration mode, you can change the rate of packets reaching the CPU for capture. If the capture traffic rate is too high, you can drop protocol packets.

Error Message %SPAN-5-PKTCAP_START_FAILED: Packet capture session [dec] failed to start. [chars] Explanation Packet capture is activated by user or after the scheduled time but failed to start. Recommended Action Correct the failure reason and re-activate or re-schedule the capture.

Error Message %SPAN-5-PKTCAP_STOP: Packet capture session %d ended %s, %d packets captured Explanation Packet capture was stopped. The capture stops if the capture buffer is full or if the user

manually stops the capture or if a capture timeout occurs. Recommended Action You can view the capture on the console or you can export the capture buffer using the monitor capture export buffer command. Delete the capture session if it is no longer required.


1547

SPANTREE Messages

SPAN-6 Error Message %SPAN-6-SPAN_EGRESS_REPLICATION_MODE_CHANGE: Span Egress HW Replication Mode Change Detected. Current replication mode for [chars] is [chars] Explanation When autodetection of egress SPAN replication mode is enabled, the system will

transition any available sessions to centralized mode when a distributed egress SPAN-incapable line card is inserted. The system will transition back the available sessions to distributed egress SPAN mode when the last distributed egress SPAN-incapable line card is removed. Recommended Action To prevent a session switching back to distributed egress SPAN mode, enter the

monitor session egress replication-mode centralized command.

SPANTREE Messages This section contains Spanning Tree Protocol (STP) messages.

SPANTREE-2 Error Message %SPANTREE-2-BRIDGE_ASSURANCE_BLOCK: Bridge Assurance blocking port %s%s. Explanation Bridge Protocol Data Units (BPDUs) were not received from a neighboring switch on

the interface that has spanning tree Bridge Assurance (BA) configured. As a result, the interface was moved to the spanning tree blocking state. Recommended Action Disable BA on the interface or make sure that the interface is connected to a

L2 switch or bridge device.

Error Message %SPANTREE-2-BRIDGE_ASSURANCE_UNBLOCK: Bridge Assurance unblocking port %s%s. Explanation The indicated interface has been restored to the normal spanning tree state after

receiving BPDUs from the neighboring Layer 2 switch or bridge. Recommended Action No action is required.

Error Message %SPANTREE-2-PVST_PEER_BLOCK: PVST+ peer detected on port %s Explanation Although the Multiple Spanning Tree Protocol (MSTP) Per-VLAN Spanning Tree Plus

(PVST+) simulation feature is disabled, PVST+ BPDU(s) are detected on the indicated interface. Recommended Action Make sure the PVST+ switch is removed from the network or enable the MSTP

PVST simulation feature.


1548

SPANTREE Messages

Error Message %SPANTREE-2-PVST_PEER_UNBLOCK: Unblocking port %s Explanation The indicated interface is no longer receiving the PVST+ BPDUs. The inconsistency is

cleared and the interface has returned to normal operation. Recommended Action No action is required.

Error Message %SPANTREE-2-PVSTSIM_OK: PVST Simulation inconsistency cleared on port [chars]. Explanation The listed interface is no longer receiving PVST BPDUs advertising information inconsistent with the CIST port information. The PVST simulation inconsistency condition is cleared and the interface will return to normal operation. Recommended Action No action is required.

SPANTREE-3 Error Message %SPANTREE-3-PRESTD_NEIGH: pre-standard MST interaction not configured ([chars]). Please, configure: ’spanning-tree mst pre-standard’ on ports connected to MST pre-standard switches. Explanation The switch has received a prestandard multiple spanning-tree (MST) BPDU on a port

that is not configured for prestandard MST BPDU transmission. The switch will automatically adjust its mode of operation on this port and will start sending prestandard BPDUs. However, this autodetection of prestandard neighbors is not 100 percent accurate and we recommended that you explicitly configure the port for prestandard MST BPDU transmission. This warning message will be displayed only once. Recommended Action Configure the spanning-tree mst pre-standard command on all the ports that

are connected to switches running the Cisco prestandard version of MST. We recommended that you migrate all the switches in the network to the IEEE standard MST version when it is possible.

SPANTREE-4 Error Message %SPANTREE-4-PORT_NOT_FORWARDING: [chars] [chars] [chars] [chars] Explanation The port is not in a forwarding state and is not forwarding packets. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1549

SPANTREE Messages

SPANTREE-6 Error Message %SPANTREE-6-PORTADD_ALL_VLANS: [chars] added to all Vlans Explanation The interface has been added to all VLANs Recommended Action This is an informational message only. No action is required.

Error Message %SPANTREE-6-PORTDEL_ALL_VLANS: [chars] deleted from all Vlans Explanation The interface has been deleted from all VLANs. Recommended Action This is an informational message only. No action is required.

Error Message %SPANTREE-6-PORT_STATE: Port [chars] instance [dec] moving from [chars] to [chars] Explanation The state of the specified spanning tree port has changed. Recommended Action No action is required.

SPANTREE-7 Error Message %SPANTREE-7-PORTDEL_SUCCESS: [chars] deleted from Vlan [dec] Explanation The interface has been deleted from the specified VLAN. Recommended Action This is an informational message only. No action is required.


1550

SPAN_ICC_ISSU Messages

SPAN_ICC_ISSU Messages This section contains SPAN intercard communication (ICC) in-service software upgrade (ISSU) messages.

SPAN_ICC_ISSU-3 Error Message %SPAN_ICC_ISSU-3-BUFFER: SPAN ICC ISSU client failed to get buffer for message, error %d Explanation The SPAN ICC ISSU client was unable to get a buffer for building a negotiation



Error Message %SPAN_ICC_ISSU-3-CAPABILITY: SPAN ISSU client %s Explanation The SPAN ISSU client detected an error during capability negotiation. A mismatch

exists in the client capability between the active and standby unit. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1551


Error Message %SPAN_ICC_ISSU-3-MSG_NOT_OK: SPAN ICC ISSU client message %d is not compatible Explanation The SPAN ICC ISSU client received an incompatible message from the peer unit. Since

the message is not compatible, it cannot be processed by this unit Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPAN_ICC_ISSU-3-MSG_SIZE: SPAN ICC ISSU client failed to get the message size for message %d Explanation The SPAN ICC ISSU client was unable to calculate the message size for the message

specified. The SPAN ICC ISSU client will be unable to send the message to the standby unit. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPAN_ICC_ISSU-3-POLICY: SPAN ICC ISSU client message type %d is %s Explanation The SPAN ICC ISSU client received a message type that it does not support. A policy


Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show issu session commands and your pertinent troubleshooting logs.


1552


Error Message %SPAN_ICC_ISSU-3-SEND_FAILED: SPAN ICC ISSU client failed to send a negotiation message, error %d Explanation The SPAN ICC ISSU client could not send a session negotiation message to the peer.



Error Message %SPAN_ICC_ISSU-3-SESSION: SPAN ICC ISSU client %s Explanation SPAN ICC ISSU client detected an error during a session negotiation with the peer unit.



Error Message %SPAN_ICC_ISSU-3-TRANSFORM: SPAN ICC ISSU client %s transform failed, error %s Explanation The SPAN ICC ISSU client could not transform the message. If the transmit

transformation failed, the ICC message cannot be sent to the peer unit. If the receive transformation failed, the ICC message cannot be applied on the peer unit. In either case, the SPAN ICC ISSU state will not be identical with the active unit. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1553

SPA_OIR Messages


SPA_OIR Messages This section contains shared port adapter (SPA) online insertion and removal (OIR) messages.

SPA_OIR-2 Error Message %SPA_OIR-2-INITFAIL: SPA OIR initialization error Explanation A failure occurred during the SPA OIR subsystem startup. SPA OIR is not functional

for the RP or line card that generated the message. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message %SPA_OIR-2-SUBSLOTINITFAIL: SPA OIR initialization error for [chars] Explanation A failure occurred during the SPA OIR subsystem startup. SPA OIR is not functional

for the specified slot or subslot. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

SPA_OIR-3 Error Message %SPA_OIR-3-CMD_ATTR: [chars]: Unexpected command identifier ([int]) Explanation An unexpected command identifier was detected when processing a command related

to a SPA OIR. The command was not processed. This is most likely due to a software problem. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show monitor event-log spa all command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


1554

SPA_OIR Messages

Error Message %SPA_OIR-3-CORRUPT_EVENT: [chars] Explanation Corruption was detected within a SPA OIR event for the subslot specified in the

message. When this error occurs, the system attempts automatic recovery by reloading the SPA. This condition could be caused by a software, firmware, or hardware problem, but a firmware or software problem is more likely. For distributed platforms, SPA OIR events are transported over different media depending on the platform (for example, the Cisco 12000 uses the MBUS). An unlikely cause of this error is that an event message was corrupted during transport. Recommended Action No immediate action is required on the system if the SPA is operational. Copy the message exactly as it appears on the console or in the system log. Enter the show monitor event-log spa all command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SPA_OIR-3-EVENT_DATA_ERROR: SPA OIR event data error - [chars]([int]) Explanation Invalid data was detected within a SPA OIR event. The SPA OIR state machines may

not reflect the state of the hardware. The problem affects only one SPA, but the SPA cannot be determined from the context where the error was detected. This condition could be caused by a software or hardware problem, but a software problem is more likely. For distributed platforms, SPA OIR messages are transported over different media depending on the platform (for example, the Cisco12000 uses the MBUS). An unlikely cause of this error is that an event message was corrupted during transport. Recommended Action Check the system log for other messages that may help determine which SPA

is affected. Enter the hw-module target_spa reload command, with target_spa being the slot or subslot of the affected SPA. Entering this command will perform a power cycle and synchronizes the affected SPA software with the hardware. Copy the message exactly as it appears on the console or in the system log. Enter the show monitor event-log spa all command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


1555

SPA_OIR Messages

Error Message %SPA_OIR-3-EVENT_HANDLING: [chars]: [chars][hex] Explanation A data structure error was detected when handling a SPA OIR event for the SPA in the

slot or subslot specified in the message. The SPA OIR state machines may not reflect the state of the hardware. This condition is most likely due to a software problem. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show monitor event-log spa all command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SPA_OIR-3-EVENT_TIMEOUT: [chars]: Timeout waiting for SPA OIR event Explanation While waiting for a SPA OIR event, a timeout occurred for the subslot specified in the

message. The SPA did not complete initialization. When this error occurs, the system attempts automatic recovery by reloading the SPA. This condition could be caused by a software or hardware problem, but a software problem is more likely. For distributed platforms, SPA OIR events are transported over different media depending on the platform (for example, the Cisco 12000 uses the MBUS). An unlikely cause of this error is that an event message was corrupted during transport. Recommended Action No immediate action is required on the system if the SPA is operational. Copy the message exactly as it appears on the console or in the system log. Enter the show monitor event-log spa all command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SPA_OIR-3-HW_INIT_TIMEOUT: [chars] Explanation A timeout occurred for the specified subslot while waiting for the SPA hardware to initialize. The SPA did not complete initialization. When this error occurs, the system attempts an automatic recovery by reloading the SPA. This condition could be caused by a software, firmware, or hardware problem, but a firmware or hardware problem is most likely. Recommended Action No immediate action is required on the system if the SPA is operational. Copy the message exactly as it appears on the console or in the system log. Enter the show monitor event-log spa all command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities


1556

SPA_OIR Messages

will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SPA_OIR-3-HW_SIGNAL_DEASSERTED: [chars] Explanation One or more hardware signals indicated that the SPA hardware in the specified subslot should be reinitialized. When this error occurs, the system attempts an automatic recovery by reloading the SPA. This condition could be caused by a software, firmware, or hardware problem, but a firmware or hardware problem is most likely. This condition could be caused by a rare interaction between SPA and its SIP. Recommended Action No immediate action is required on the system if the SPA is operational. Copy the message exactly as it appears on the console or in the system log. Enter the show monitor event-log spa all command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, or would like to report a suspected hardware failure, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SPA_OIR-3-MESSAGE_ERROR: [chars]: SPA OIR event message error [chars]([int]) Explanation An error was detected in a SPA OIR event message for the SPA in the specified slot or

subslot. The SPA OIR state machines may not reflect the state of the hardware for this SPA. This condition could be caused by a software or hardware problem, but a software problem is more likely. For distributed platforms, SPA OIR messages are transported over different media depending on the platform (for example, the Cisco 12000 uses the MBUS). An unlikely cause of this error is that an event message was corrupted during transport. Recommended Action Enter the hw-module target_spa reload command, with target_spa being the slot or subslot of the affected SPA. Entering this command will perform a power cycle and synchronizes the affected SPA software with the hardware. Copy the message exactly as it appears on the console or in the system log. Enter the show monitor event-log spa all command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support


1557

SPA_OIR Messages


Error Message %SPA_OIR-3-POST_EVENT_ERROR: [chars]: event [int] Explanation A SPA OIR event message was not enqueued for the SPA in the specified slot or subslot. The SPA OIR state machines may not reflect the state of the hardware for this SPA. This condition is most likely due to a software problem. Recommended Action Enter the hw-module target_spa reload command, with target_spa being the slot or subslot of the affected SPA. Entering this command will perform a power cycle and synchronizes the affected SPA software with the hardware. Copy the message exactly as it appears on the console or in the system log. Enter the show monitor event-log spa all command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SPA_OIR-3-RECOVERY_RELOAD: [chars]: Attempting recovery by reloading SPA Explanation The OIR facility attempted an automatic recovery by reloading the SPA in the specified

subslot. Look for other messages related to this SPA subslot to determine the failure that triggered the automatic recovery. Recommended Action This is an informational message only. No action is required.

Error Message %SPA_OIR-3-SEQUENCE_NUMBER_ERROR: [chars] Explanation A sequence number error was detected within a SPA OIR event for the specified subslot. When this error occurs, the system attempts an automatic recovery by reloading the SPA. This condition could be caused by a software, firmware, or hardware problem, but a firmware or software problem is most likely. For distributed platforms, SPA OIR events are transported over different media depending on the platform (for example, the Cisco 12000 uses the MBUS). An unlikely cause of this error is that an event message was corrupted during transport. Recommended Action No immediate action is required on the system if the SPA is operational. Copy the message exactly as it appears on the console or in the system log. Enter the show monitor event-log spa all command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, or would like to report a suspected hardware failure, open a case with the Technical Assistance Center


1558

SPA_OIR Messages

via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SPA_OIR-3-SPA_POWERED_OFF: [chars]: SPA [chars] powered off after [int] failures within [int] seconds Explanation The SPA was powered off because it failed too often. This condition may be caused by

a software, firmware, or hardware error. Recommended Action Look for other system messages related to this SPA subslot to determine the root cause of the failure. Enter the hw-module target_spa reload command, with target_spa being the slot or subslot of the affected SPA. Entering this command will perform a power cycle and synchronizes the affected SPA software with the hardware. Copy the message exactly as it appears on the console or in the system log. Enter the show monitor event-log spa all command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SPA_OIR-3-SW_INIT_TIMEOUT: [chars]: SPA initialization not completed Explanation A timeout occurred for the specified subslot while waiting for the SPA software driver

to initialize the SPA. The SPA did not complete initialization. When this error occurs, the system attempts automatic recovery by reloading the SPA. This condition could be caused by software, firmware or hardware problem, but a software or firmware problem is more likely. Recommended Action Check for other reported messages for more verification. Hardware

replacement should not occur on the first occurrence. Before requesting hardware replacement, review troubleshooting logs with a Cisco technical support representative. No immediate action is required on the system if the SPA is operational. Copy the message exactly as it appears on the console or in the system log. Enter the show monitor event-log spa all command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, or would like to report a suspected hardware failure, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


1559

SPA_OIR Messages

Error Message %SPA_OIR-3-UNEXPECTED_EVENT: [chars]: SPA OIR unexpected event([int]) Explanation An unexpected SPA OIR event was detected for the SPA in the specified slot or subslot.

The SPA OIR state machines may not reflect the state of the hardware for this SPA. This condition could be caused by software or hardware problem, but a software problem is more likely. For distributed platforms, SPA OIR messages are transported over different media depending on the platform (for example, the Cisco 12000 uses the MBUS). An unlikely cause of this error is that an event message was corrupted during transport. Recommended Action Enter the hw-module target_spa reload command, with target_spa being the slot or subslot of the affected SPA. Entering this command will perform a power cycle and synchronizes the affected SPA software with the hardware. Copy the message exactly as it appears on the console or in the system log. Enter the show monitor event-log spa all command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SPA_OIR-3-UNEXPECTED_INSERTED_EVENT: [chars] Explanation An unexpected inserted event occurred for the specified subslot. When this error occurs,

the system attempts automatic recovery by reloading the SPA. This condition could be caused by a software, firmware, or hardware problem, but a firmware or software problem is most likely. This condition could be caused by a rare interaction between SPA and its SIP. Recommended Action No immediate action is required on the system if the SPA is operational. Copy the message exactly as it appears on the console or in the system log. Enter the show monitor event-log spa all command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, or would like to report a suspected hardware failure, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SPA_OIR-3-UNEXPECTED_RECOVERY_ACTION: [chars]: SPA [chars], unexpected recovery action([int]) for fail code [hex] Explanation An error occurred while processing a failure message for the SPA in the slot or subslot

number specified in the message. The recovery action to be taken after a SPA failure is determined by calling a SPA driver function. This message indicates that the SPA driver function returned an


1560

SPA_OIR Messages

invalid recovery action. After this message was issued, the SPA was reloaded in an attempt to recover. The SPA driver most likely returned an invalid recovery action because of a software problem. Recommended Action No immediate action is required on the system if the SPA is operational. Copy the message exactly as it appears on the console or in the system log. Enter the show monitor event-log spa all command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, or would like to report a suspected hardware failure, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SPA_OIR-3-UNRECOGNIZED: The SPA of type [hex] in [chars] is not recognized Explanation The type of the SPA in the specified subslot is not recognized by the operating system.

Either the operating system might not support this SPA type on this platform or the SPA type identification stored on the SPA is invalid. Recommended Action Ensure that the system is running a version of the operating system that supports the specified SPA type on this platform. If the correct operating system version is in use, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Include the information about the SPA type found on the front of the SPA. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SPA_OIR-3-UNSUPPORTED: The [chars] in [chars] is not supported by the [chars] module Explanation The SPA in the specified subslot is not supported in the specified SIP by the version of the operating system currently running on the system. The SPA type may be supported by another SIP or by a later operating system release. Recommended Action Ensure that the SIP specified in the error message supports the specified SPA type. Ensure that the operating system release supports the SPA type in the SIP. It may be necessary to upgrade your system to the latest operating system release in your release train, or it may be necessary to use a different SIP type. If the SPA type specified in the error message does not match the interface types or numbers shown on the front of the SPA, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at


1561

SPA_OIR Messages

http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Include information regarding the SPA type found on the front of the SPA. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

SPA_OIR-6 Error Message %SPA_OIR-6-INSCARD: Card inserted in [chars] Explanation The OIR facility detected a newly inserted SPA. The interfaces associated with that SPA

are operational, but will be shut down until they are configured by the user. If any interfaces of that type were previously configured, they will be restored to their previous state. Recommended Action This is an informational message only. No action is required.

Error Message %SPA_OIR-6-PRECONFIG_MISMATCH: [chars]: Inserted SPA type does not match preconfigured SPA type. Configuration updated Explanation There is mismatch between the inserted SPA type and the preconfigured SPA type on

platforms that support preconfiguration. The inserted SPA replaces the preconfigured SPA. Recommended Action Verify the configuration by entering the show running-config command. If you would like to revert to the preconfigured type, remove the SPA and then update the configuration from a backup copy.

Error Message %SPA_OIR-6-REMCARD: Card removed from [chars], interfaces disabled Explanation The OIR facility detected the removal of a SPA from the specified slot or subslot. The

interfaces on that SPA will be administratively shut down and marked as removed. The routing table will be flushed of any routes through the removed interfaces. Recommended Action This is an informational message only. No action is required.

Error Message %SPA_OIR-6-SHUTDOWN: [chars] is administratively shutdown; Use ’no hw-module [chars] shutdown’ to enable Explanation The SPA was not brought up because the SPA bay is in an administrative down state.

The SPA bay will appear as hw-module target_spa shutdown in the running configuration. Recommended Action Use the no hw-module target_spa shutdown command to administratively

enable the SPA bay.


1562

SPA_PLIM Messages

SPA_PLIM Messages This section contains shared port adapter (SPA) physical layer interface module messages.

SPA_PLIM-3 Error Message %SPA_PLIM-3-FATALERROR: SPA in slot [dec] bay [dec] experienced a fatal error [chars] and is being reset. Explanation A fatal error was encountered during SPA operation. The SPA may be restarted. Recommended Action If the error is not observed more than once, it might be a singular event and the

SPA needs to be monitored. If the issue occurs repeatedly, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SPA_PLIM-3-FW_RELOAD: [chars] is being reloaded due to firmware/application exception. Explanation The SPA firmware application has failed. The SPA is being reloaded to recover its

operational state. Recommended Action Collect the application core file from flash. The core filename and time stamp are shown in the preceding message.

Error Message %SPA_PLIM-3-HEARTBEAT: [chars] has experienced an heartbeat failure Current Sequence [int] received Sequence [int] Time since last keep [dec]ms. Explanation The IPC communication between the local CPU and host in the specified slot is not

functional. The IPC module will be restarted, after which communication might be reestablished. If the problem persists the SPA will be reset. Recommended Action If the system continues running normally, no action is required. If this message

recurs, or the system behaves abnormally, collect the logs from the system (RP and line card). Copy the message exactly as it appears on the console or in the system log. Enter the show hw-module slot-number/subslot-number tech-support command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support


1563

SPA_PLIM Messages


Error Message %SPA_PLIM-3-INITFAIL: [chars] has failed initialization because SPA [chars]. Explanation A failure occurred during the SPA initialization. SPA is not functional and may be restarted by the RP or line card. Recommended Action If the line card or RP successfully initialized the SPA, no action is required. If the SPA was not successfully initialized, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SPA_PLIM-3-INIT_PORT: [chars] PLIM client IPC port has not been initialized. Explanation The specified PLIM client IPC port has not been initialized. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1564

SPA_PLIM Messages

SPA_PLIM-4 Error Message %SPA_PLIM-4-EXCEPTION: [chars] has experienced an exception: [chars]. Writing SPA crash dump information to [chars]. Explanation The local CPU in the specified slot has experienced an exception condition. The process

that caused the exception might have been restarted. If an exception core dump was created, the core dump is stored in the line card flash memory, if available. Recommended Action If the system continues running normally, no action is required. If this message

recurs, or the system behaves abnormally, collect the crash dump file from the line card flash. Copy the message exactly as it appears on the console or in the system log. Enter the show hw-module slot-number/subslot-number tech-support command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SPA_PLIM-4-SBE_ECC: [chars] reports [dec] SBE occurance at [dec] addresses Explanation The SPA has reported single-bit correctable ECC errors. The log shows that more than

one SBE has occurred. SBEs are correctable memory problems. It will not affect router operation. Excessive occurrences may indicate defective memory. Recommended Action Observe at the first occurrence. If the error recurs, replace the faulty memory

chip at the earliest opportunity.

Error Message %SPA_PLIM-4-SBE_OVERFLOW: [chars] SBE table([dec] elements) overflows. Explanation The SPA has reported more unique single-bit correctable ECC errors than the platform

defined internal table can hold. SBEs are correctable memory problems. It will not affect router operation. Excessive occurrences indicate defective memory. Recommended Action Replace the faulty memory chip at the earliest opportunity.


1565

SPA_PLUGIN Messages

SPA_PLIM-5 Error Message %SPA_PLIM-5-RECEIVINGFILE: Receiving [chars] from [chars]. Explanation The SPA has sent a file (syslog or core dump) to the line card and the file has been stored

in the line card flash if available. Recommended Action This is a debug message only. No action is required.

SPA_PLUGIN Messages This section contains shared port adapter (SPA) plug-in messages.

SPA_PLUGIN-3 Error Message %SPA_PLUGIN-3-AUXC2W_CREATE: [chars]: Device auxiliary C2W creation failed. Explanation Cannot allocate memory for auxiliary C2W structure. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message %SPA_PLUGIN-3-EEPROM_READ: [chars]: Error reading EEPROM. Explanation Cannot read EEPROM content. It indicates either an improperly seated SPA or a hardware failure. Recommended Action Power down and reseat the specified SPA card. If the condition persists, copy



1566

SPA_PLUGIN Messages

Error Message %SPA_PLUGIN-3-EFC_NOTSYNC: [chars]: Can not synchronize EFC bus. Explanation Extended flow control between the modular services card and the SPA is not

synchronized. The SPA is shut down. It indicates either an improperly seated SPA, a hardware failure, or an outdated ROMMON or FPGA image. Recommended Action Power down and reseat the specified SPA card. If the condition persists, copy


Error Message %SPA_PLUGIN-3-EXCEPTION: [chars]: Exception with cause [dec]. Explanation One of the SPA software components has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA_PLUGIN-3-FAILED: [chars]: Plugin initialization failed. Explanation Plug-in initialization has failed. Plug-in initialization can fail for many reasons.

Preceding messages may state the cause. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1567

SPA_PLUGIN Messages

Error Message %SPA_PLUGIN-3-FILE_ERROR: [chars]: Error accessing file [chars]. Explanation The specified file cannot be accessed. Either the file is not found, lack of permission,

out of space, or other file system or device errors. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA_PLUGIN-3-FILE_TRANSFER: [chars]: Failed to transfer file to or from SPA. Explanation Failed to transfer a file to or from the SPA. This error might be caused by lack of memory on the SPA or jacket card, IPC failures, improperly seated SPA, or other errors. Recommended Action Power down and reseat the specified SPA card. If the condition persists, copy


Error Message %SPA_PLUGIN-3-FIRMWARE_APPS_DOWNLOAD: [chars]: Firmware application download failed. Explanation Failed to download an application image to the SPA. This error might be caused by lack of memory on the SPA, IPC failures, an improperly seated SPA, or other download errors. Recommended Action Power down and reseat the specified SPA card. If the condition persists, copy



1568

SPA_PLUGIN Messages

Error Message %SPA_PLUGIN-3-FIRMWARE_APPS_STARTUP: [chars]: Firmware application startup failed. SPA status([hex]) host status([hex]) Explanation Cannot start application image downloaded to SPA. Possible causes might be either a

bad image on the line card flash disk, a hardware failure, or an outdated FPGA or ROMMON image. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA_PLUGIN-3-FIRMWARE_BADIMAGE: [chars]: Firmware file [chars] read failed. Explanation The firmware image pointed to by the path is not valid. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA_PLUGIN-3-FIRMWARE_BADPATH: [chars]: Invalid firmware file path [chars]. Explanation The specified firmware file path is invalid. This is a software error. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1569

SPA_PLUGIN Messages

Error Message %SPA_PLUGIN-3-FIRMWARE_DOWNLOAD: [chars]: Firmware download failed. Explanation Failed to download firmware image to the SPA. This error is caused by either lack of

memory on the SPA, IPC failures, an improperly seated SPA, or other download errors. Recommended Action Power down and reseat the specified SPA card. If the condition persists, copy


Error Message %SPA_PLUGIN-3-FIRMWARE_NOMEMORY: [chars]: Insufficient memory for firmware file [chars], size [dec]. Explanation Cannot allocate memory for firmware image downloading to the SPA. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message %SPA_PLUGIN-3-FIRMWARE_STARTUP: [chars]: Firmware startup failed. SPA status([hex]) host status([hex]) Explanation Cannot start the firmware image downloaded to the SPA. Possible causes are either a

bad image on the line card flash disk, hardware failures, or an outdated FPGA or ROMMON image. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA_PLUGIN-3-IOFPGA_CREATE: [chars]: Device IOFPGA creation failed. Explanation Cannot allocate memory for IOFPGA structure. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.


1570

SPA_PLUGIN Messages

Error Message %SPA_PLUGIN-3-NOPLIM: [chars]: No PLIM subblock. Explanation An invalid pointer was passed in. Cannot dereference the PLIM subblock pointer. This

is an internal error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA_PLUGIN-3-NOPORT: [chars]: Failed to open IPC port. Explanation The PLIM client IPC port has not been initialized. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA_PLUGIN-3-PLIM_CREATE: [chars]: PLIM subblock creation failed. Explanation Cannot allocate memory for a PLIM structure. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message %SPA_PLUGIN-3-RETRY_EXHAUSTED: [chars]: plugin initialization failed(retries exhausted). Explanation One or more critical conditions happened that prevented plug-in initialization from

moving forward, after the designated number of retries. Preceding messages may specify a failure cause. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1571

SPA_PLUGIN Messages


Error Message %SPA_PLUGIN-3-ROMMON: [chars]: ROMMON reports error. SPA status([hex]), host status([hex]). Explanation ROMMON has reported a fatal condition during bootup. It may be caused by outdated

ROMMON or FPGA images or by defective hardware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA_PLUGIN-3-SPI4_CREATE: [chars]: Device SPI4 creation failed. Explanation Cannot allocate memory for a SPI4 structure. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message %SPA_PLUGIN-3-SPI4_INIT: [chars]: SPI4 initializaion failed. Explanation SPI4 initialization has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1572

SPA_PLUGIN Messages

Error Message %SPA_PLUGIN-3-SPI4_NOTSYNC: [chars]: Can not synchronize SPI4 bus. Explanation The SPI4 bus between the modular services card and the SPA is not synchronized. It

indicates either an improperly seated SPA, a hardware failure, or an outdated ROMMON or FPGA image. Recommended Action Power down and reseat the specified SPA card. If the condition persists, copy


Error Message %SPA_PLUGIN-3-SPI4_SETCB: [chars]: IPC SPI4 set callback failed(status [dec]). Explanation Cannot set up a callback function for the SPI4 bus. It might be caused by an improperly

seated SPA, an outdated ROMMON or FPGA image, or a hardware failure. Recommended Action Power down and reseat the specified SPA card. If the condition persists, copy


Error Message %SPA_PLUGIN-3-SPI4_SETCB_PORT: [chars]: IPC SPI4 set callback failed(error: [dec]) for port [dec]. Explanation Cannot set up a callback function for the SPI4 bus for the specified interface port. It

might be caused by an improperly seated SPA, an outdated ROMMON or FPGA image, or a hardware failure. Recommended Action Power down and reseat the specified SPA card. If the condition persists, copy



1573

SPA_PLUGIN Messages

SPA_PLUGIN-4 Error Message %SPA_PLUGIN-4-LED_CREATE: [chars]: LED driver initialization failed. Explanation Cannot allocate memory for LED structure. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message %SPA_PLUGIN-4-LED_READ: [chars]: LED read failed for port [dec], status [dec]. Explanation Cannot read LED register values. This error indicates either an improperly seated SPA or a hardware failure. Recommended Action Power down and reseat the specified SPA card. If the condition persists, copy


Error Message %SPA_PLUGIN-4-LED_WRITE: [chars]: LED write failed for port [dec], status [dec]. Explanation Cannot write to the LED register. This error indicates either an improperly seated SPA

or a hardware failure. Recommended Action Power down and reseat the specified SPA card. If the condition persists, copy



1574

SPA_PMB Messages

SPA_PLUGIN-6 Error Message %SPA_PLUGIN-6-EFC_SYNC: [chars]: EFC bus synchronization achieved. Explanation Extended flow control between the modular services card and the SPA is synchronized. Recommended Action This is an informational message only. No action is required.

Error Message %SPA_PLUGIN-6-FIRMWARE_APPS_DOWNLOADING: [chars]: Downloading SPA firmware application ([chars])... Explanation Downloading SPA firmware application. Recommended Action This is an informational message only. No action is required.

Error Message %SPA_PLUGIN-6-FIRMWARE_DOWNLOADING: [chars]: Downloading SPA firmware ([chars])... Explanation Downloading SPA firmware. Recommended Action This is an informational message only. No action is required.

Error Message %SPA_PLUGIN-6-SPI4_SYNC: [chars]: SPI4 bus synchronization achieved. Explanation The SPI4 bus between the modular services card and the SPA is synchronized. Recommended Action This is an informational message only. No action is required.

SPA_PMB Messages This section contains SPA-specific power management bus messages.

Error Message %SPA_PMB-4-CANTREADSPAIDPROM: The SPA in Subslot [int]/[int] could not be accessed. The error code received is [dec] Explanation An internal software consistency issue regarding the SPA has been detected. Recommended Action If the SPA’s operation is affected, perform an OIR for the line card on which

the SPA or SPAs are located. The slot and subslot of the affected SPA is specified in the message. If this does not fix the problem, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support


1575

SPA_PMB Messages


Error Message %SPA_PMB-4-CARDPWREDON: The line card in slot [dec] is powered on due to out of range electrical signals Explanation The SPAs in the line card in the specified slot could not be accessed because of

out-of-range electrical signals. There might be problems in reading in startup configuration for the SPAs in the specified slot. Recommended Action Check the running and startup config for the specified slot. If the configuration

for the ports in the slot is different, then manually copy the startup config to the running config. If this problem recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SPA_PMB-4-NOACK: The device with id [hex] in slot [dec] is not responding Explanation The SPAs in the line card in the specified slot could not be accessed because of a

hardware problem.The system might not be able to read the startup configuration for the SPAs. Recommended Action Check the running and startup config for the specified slot. If the configuration

for the ports in the slot is different, then manually copy the startup config to the running config. If this problem recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


1576

SPA_T3E3 Messages

SPA_T3E3 Messages This section contains T3E3 (SPA_T3E3) messages.

SPA_T3E3-3 Error Message %SPA_T3E3-3-LOVEFAIL: [chars]: failed to send [chars] love letter Explanation A “love letter” (operating status or configuration message) was not sent. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA_T3E3-3-MSGERR: Illegal message type [dec] received for Interface [chars] Explanation An unknown message was received by the RP. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SPA_T3E3-3-SSBINIT: [chars]: Fail to initialize serial IDB Explanation Serial IDB initialization has failed. The most common reason is lack of system memory.

Previous messages might indicate memory allocation failures. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1577

SPA_T3E3 Messages


Error Message %SPA_T3E3-3-SUBRATE_FPGA_LOAD_FAILED2: [chars] Programming [chars] subrate FPGA failed again. The SPA will be disabled as it cannot recover from the FPGA image corruption. Explanation The specified subrate FPGA image is corrupted after an FPD upgrade. It might indicate

an FPD image package problem. The SPA is disabled until this problem is corrected. Recommended Action Verify the correctness of the FPD image package. The FPD image package

used in the upgrade should match the running Cisco IOS release. This can be verified by entering the show upgrade fpd package default command.

SPA_T3E3-4 Error Message %SPA_T3E3-4-SUBRATE_FPGA_LOAD_FAILED: [chars] Programming [chars] subrate FPGA failed. The FPGA image is corrupted. One upgrade attempt will be made to recover from the failure. Explanation The specified subrate FPGA image is corrupted and programming of the FPGA has

failed. One upgrade attempt will be made to recover from the failure. Recommended Action Automatically upgrade the subrate FPGA image using the default FPD image package. The package should match the running Cisco IOS release. This can be verified by entering the show upgrade fpd package default command. If the subrate FPGA failure persists after the upgrade, the SPA is disabled. Ensure that the package file is intact.

SPA_T3E3-5 Error Message %SPA_T3E3-5-BERT: Interface [chars], BERT [chars] Explanation The SPA T3E3 driver processed a BERT task. Recommended Action This is just a notification upon completion of a BERT task. No action is

required.

Error Message %SPA_T3E3-5-DEF_SUBRATE: [chars] [chars] Explanation The remote subrate configuration has changed. Recommended Action Inform the network operator that subrate configuration was changed by the

remote end.


1578

SPLC_DNLD Messages

SPLC_DNLD Messages SPLC_DNLD-1 Error Message %SPLC_DNLD-1-VS_HA_PS_NOT_SUPPORTED: Chassis Standby is not supported in the current release. Forcing the chassis standby in switch [dec] slot [dec] to drop to rommon Explanation Chassis Standby is not supported in Cisco IOS Release 12.2 SXI(1). Recommended Action No action is required.

Error Message %SPLC_DNLD-1-VS_HA_PS_RUNNING_LEGACY_IMAGE: Chassis Standby in switch [dec] slot [dec] is running non Virtual Switch image. Please remove the chassis standby. Explanation Chassis Standby running non Virtual Switch image is not supported. Recommended Action No action is required.

SPLC_DNLD-3 Error Message %SPLC_DNLD-3-VS_ADD_VSL_ENTRY_FAILED: Add VSL configured port for vslot [int] port [int] failed. Exceed port member count limit. Explanation Attempt to add entry for (vslot, port) to VSL configured port list failed. Exceed port

member count limit. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %SPLC_DNLD-3-VS_BOOLEAN_CREATE_FAILED: Unable to create watched boolean "[chars]" Explanation Unable to create the specified watched boolean due to unknown reasons Recommended Action No action is required.


1579

SPLC_DNLD Messages

Error Message %SPLC_DNLD-3-VS_ENQUEUE_FAILED: Unable to enqueue to [chars] queue Explanation An internal error occurred that prevented a message from being enqueued to the

specified process. The packet was dropped Recommended Action No action is required.

Error Message %SPLC_DNLD-3-VS_HA_HB_NOT_HEARD: Heartbeat messages have not been heard from [[chars]] for [dec] seconds Explanation Heartbeat messages have not been heard for a significant amount of time.

It is likely that a timeout will occur soon which will reset the system. Recommended Action No action is required.

Error Message %SPLC_DNLD-3-VS_HA_HB_TIMED_OUT: Heartbeat messages have failed, resetting [[chars]] Explanation Heartbeat messages have failed and the system is no longer operational. Recommended Action No action is required.

Error Message %SPLC_DNLD-3-VS_ICC_PAK_FAIL: Unable to get ICC packet for opcode [dec], operation [dec] Explanation Packet allocation failed for sending an ICC message to do the specified operation Recommended Action Issue the show tech-support command to gather data that may help identify the nature of the error. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message %SPLC_DNLD-3-VS_ICC_RESP_PAK_NULL: Failed to obtain response packet Explanation Response packet pointer is NULL. This could be no memory condition on response

packet sending side or failure to get IPC message on receiving side. Recommended Action Copy the error message exactly as it appears on the console or in the system



1580

SPLC_DNLD Messages

Error Message %SPLC_DNLD-3-VS_PROC_CREATE_FAILED: Unable to create process "[chars]" Explanation Unable to create the specified process due to unknown reasons Recommended Action No action is required.

Error Message %SPLC_DNLD-3-VS_QUEUE_CREATE_FAILED: Unable to create queue "[chars]" Explanation Unable to create the specified queue due to unknown reasons Recommended Action No action is required.

Error Message %SPLC_DNLD-3-VS_SPLC_CREATE_DNLD_INSTANCE_FAIL: Dnld instance could not be created for Inchassis-Standby on slot-id [dec] and switch-id [dec] Explanation Not available Recommended Action Not available

Error Message %SPLC_DNLD-3-VS_SPLC_CREATE_DNLD_PROC_FAIL: Dnld proc could not be created by Inchassis-Active for Inchassis standby on slot-id [dec] and switch-id [dec] Explanation Not available Recommended Action Not available

Error Message %SPLC_DNLD-3-VS_SPLC_DNLD_BAD_EVENT: Bad event for major [int] and minor [int] in Sup-LC download queue Explanation Not available Recommended Action Not available

Error Message %SPLC_DNLD-3-VS_SPLC_DNLD_CREATE_PROC_FAIL: Process creation for Sup-LC download at the vs_ha subsys init level Explanation Not available Recommended Action Not available

Error Message %SPLC_DNLD-3-VS_SPLC_DNLD_CREATE_QUEUE_FAIL: Create queue failed for SPLC dnld process at the vs_ha subsys init level Explanation Not available Recommended Action Not available


1581

SPLC_DNLD Messages

Error Message %SPLC_DNLD-3-VS_SPLC_DNLD_ENQUEUE_FAIL: Could not enqueue the message on the splc_dnld_rx_queue Explanation Not available Recommended Action Not available

Error Message %SPLC_DNLD-3-VS_SPLC_DNLD_IMAGE_INFO_FAIL: Unable to get the correct image size inchassis standby [dec] on switch-id [dec] Explanation Unable to get the correct image size for the inchassis standby from the inchassis active Recommended Action No action is required.

Error Message %SPLC_DNLD-3-VS_SPLC_DNLD_REQ_ACK_FAIL_SEQ_ABS: Inchassis-Active could not send splc_dnld_req_ack to Inchassis-standby on slot-id [dec] on switch-id [dec] due to missing seq_num Explanation Not available Recommended Action Not available

Error Message %SPLC_DNLD-3-VS_SPLC_DNLD_REQ_ACK_FAIL_SEQ_ERR: Inchassis-Active could not send splc_dnld_req_ack to Inchassis-standby on slot-id [dec] on switch-id [dec] due to seq_num error Explanation Not available Recommended Action Not available

Error Message %SPLC_DNLD-3-VS_SPLC_DNLD_REQ_MEM_FAIL: Inchassis-Standby could not get the scp request packet to be sent to Inchassis-Active due to scp get packet memory not present Explanation Not available Recommended Action Not available

Error Message %SPLC_DNLD-3-VS_SPLC_DNLD_REQ_SEND_FAIL: Inchassis-Standby could not send the dnld_request msg to Inchassis-Active Explanation Not available Recommended Action Not available


1582

SPLC_DNLD Messages

Error Message %SPLC_DNLD-3-VS_SPLC_DNLD_UNKNOWN: Unable to get sup-lc image filename for inchassis standby [dec] on switch-id [dec] Explanation Unable to get the correct image filename for the inchassis standby from the inchassis

active Recommended Action No action is required.

Error Message %SPLC_DNLD-3-VS_SPLC_GET_ARG_PTR_FAIL: Argument pointer for SUP-LC download failed on Inchassis-Standby slot-id :[dec] switch-id:[dec] Explanation Not available Recommended Action Not available

Error Message %SPLC_DNLD-3-VS_SPLC_GET_DNLD_IMAGE_FAIL: Sup-LC Image could not be downloaded to the Inchassis Standby slot-id: [dec] switch-id: [dec] Explanation Not available Recommended Action Not available

Error Message %SPLC_DNLD-3-VS_SPLC_SET_DNLD_INSTANCE_FAIL: Dnld instance could not be set on the inchassis-standby for slot-id [dec] switch-id [dec] Explanation Not available Recommended Action Not available

SPLC_DNLD-5 Error Message %SPLC_DNLD-5-VS_CONFIG_DIRTY: Configuration has changed. [chars] Explanation Attempt to reload ignored due to config change Recommended Action No action is required

Error Message %SPLC_DNLD-5-VS_SWITCH_NUMBER_CHANGE: Switch_number getting changed from [dec] to [dec]. Explanation Not available Recommended Action Not available.


1583

SPLC_DNLD Messages

SPLC_DNLD-6 Error Message %SPLC_DNLD-6-VS_HA_HOT_STANDBY_NOTIFY: Standby switch is in Hot Standby mode. Explanation Not available. Recommended Action Not available.

Error Message %SPLC_DNLD-6-VS_HA_ICS_EARL_MISMATCH: In-chassis Standby has an incompatible Earl version and will be put down. Explanation Not available. Recommended Action Not available.

Error Message %SPLC_DNLD-6-VS_HA_INCORRECT_ACTIVE: [chars] Explanation Informational messages regarding the state of the active supervisor. Recommended Action None.

Error Message %SPLC_DNLD-6-VS_HA_ISSU_SUP_INSERT: The supervisor in switch [dec] in slot [dec] was inserted during the ISSU cycle and was put down. Explanation As stated above. Recommended Action Please boot this supervisor manually after the ISSU cycle is complete.

Error Message %SPLC_DNLD-6-VS_ICA_ICS_SWITCHID_MISMATCH: Inconsistent switch id detected on ICS([dec])compared to ICA([dec]),correcting it to align with ICA Explanation Not available. Recommended Action Not available.

Error Message %SPLC_DNLD-6-VS_SPLC_IMAGE_VERSION_MISMATCH: In-chassis Standby in switch [dec] is trying to boot with a different image version than the In-chassis Active Explanation Not available Recommended Action Not available


1584

SRC Messages

SRC Messages This section contains Switch Redundancy Controller (SRC) messages.

SRC-3 Error Message %SRC-3-AFOVEN_ERROR: Attempt to enable [chars] protection autofailover on interface [chars] when port status is [hex] Explanation The software failed in an attempt to enable the autofailover feature. Recommended Action Copy the message exactly as it appears on the console or in the system log.


SRP Messages This section contains Spatial Reuse Protocol (SRP) messages.

SRP-1 Error Message %SRP-1-WRAPPING_PROCESS_LOCKED: [chars] The wrap/unwrap state-change process is locked Explanation A wrap and unwrap state change process did not complete in the maximum specified amount of time. Recommended Action If this message recurs periodically, enter the shutdown and no shutdown commands on the interface to shut down and restart the interface.


1585

SRPMIB Messages

SRP-3 Error Message %SRP-3-FALSE_VAL_ALARM: [chars] - error in [chars] Explanation A false value has been returned. Some features or commands may not work properly. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SRP-3-NULL_P_ALARM: Dereferencing NULL pointer [chars] in [chars] Explanation A pointer with a null value has been detected. Some features or commands may not

work properly. Recommended Action Copy the message exactly as it appears on the console or in the system log.


SRPMIB Messages This section contains Spatial Reuse Protocol (SRP) MIB messages.

SRPMIB-3 Error Message %SRPMIB-3-FALSE_VAL_ALARM: [chars] - error in [chars] Explanation A false value has been returned. Some features or commands may not work properly. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1586

SSA Messages


Error Message %SRPMIB-3-NULL_P_ALARM: Dereferencing NULL pointer [chars] in [chars] Explanation A pointer with a null value has been detected. Some features or commands may not

work properly. Recommended Action Copy the message exactly as it appears on the console or in the system log.


SSA Messages This section contains Super Santa Ana ASIC (SSA) messages.

SSA-4 Error Message %SSA-4-FABRICCRCERRS: [dec] Fabric CRC error events in 100ms period Explanation The SSA fabric interface encountered more CRC error events than the supervisor engine

CRC error threshold allows. Recommended Action The module has notified the supervisor engine, and the error has been logged. No action is required.

Error Message %SSA-4-FABRICSYNCERRS: [dec] Fabric sync error events in 100ms period Explanation The SSA fabric interface encountered more synchronization error events than the supervisor engine synchronization error threshold allows. Recommended Action The module has notified the supervisor engine, and the fabric interface will be resynchronized. No action is required.


1587

SSA Messages

Error Message %SSA-4-SSA_CONFIG_FAIL: The Super Santa Ana ASIC configuration failed Explanation The Super Santa Ana ASIC could not be configured. If the switch fabric has gone

inactive (down), this message can be expected. Recommended Action If the module comes on line and traffic processing resumes, no action is

required. Otherwise, capture the error and copy the message exactly as it appears on the console or in the system log. On the route processor, enter the show logging and show version commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

SSA-5 Error Message %SSA-5-CHAN_LINK_SPEED_OOB: Array access bounds violated, channel_num=[int], link_num=[int], speed=[int] Explanation The Cisco IOS code has attempted to access an internal array with an invalid index for an SSA channel number, link number, or speed. Recommended Action If there is no system impact, no action is required. If traffic stops or the line card fails, collect the logs and copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SSA-5-FABRICDOWN_CRCERRS: [dec] Fabric CRC error events in 100ms period Explanation The Super Santa Ana Fabric interface encountered more CRC errors than the maximum

configured threshold. However, the reason for this error is that the switch fabric is inactive (down). The line card has notified the supervisor engine of this condition and the error has been logged. Recommended Action This is an informational message only and occurs in normal operation. No

action is required.


1588

SSA Messages

Error Message %SSA-5-FABRICDOWN_SYNCERRS: [dec] Fabric sync error events in 100ms period Explanation The Super Santa Ana Fabric interface encountered more synchronization errors than the

maximum configured threshold. However, the reason for this error is that the switch fabric is inactive (down). Recommended Action This is an informational message only and occurs in normal operation. No

action is required.

Error Message %SSA-5-FABRICSYNC_DONE: Fabric sync on [chars] channel done. Explanation The fabric interface ASIC was resynchronized. Recommended Action No action is required.

Error Message %SSA-5-FABRICSYNC_REQ: Fabric sync requested on [chars] channel ([dec]) Explanation The line card has requested that the supervisor engine resynchronize its fabric interface

ASIC. Recommended Action No action is required.

Error Message %SSA-5-NOFABRICPROCESS: The Super Santa Ana fabric process could not be created Explanation The SSA fabric interface does not have a link process running because the system failed

to create it. This module will not support the fabric interface. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SSA-5-NULL_SSA_OBJECT: The Super Santa Ana device object pointer is set to NULL Explanation The memory location of the SSA device object is invalid. The SSA ASIC operation is

disabled, and the device interrupt is now masked. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1589

SSH Messages


Error Message %SSA-5-SMB_ACCESSERROR: The Module Super Santa Ana ASIC cannot be accessed Explanation The SSA ASIC read and write access failed. The serial bus that is connected to the SSA

ASIC on this module is not functioning correctly. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SSA-5-SSA_INIT_FAILURE: The Super Santa Ana ASIC initialization failed Explanation The SSA ASIC could not be initialized. As a result, this device is not operational and has been disabled. Recommended Action Copy the message exactly as it appears on the console or in the system log.


SSH Messages This section contains Secure Shell (SSH) Protocol messages.


1590

SSH Messages

SSH-4 Error Message %SSH-4-SSH2_UNEXPECTED_MSG: Unexpected message type has arrived. Terminating the connection Explanation SSH Session closure warning on receiving an inappropriate message from the peer Recommended Action If this message recurs, copy the error message exactly as it appears on the


SSH-5 Error Message %SSH-5-SSH2_CLOSE: SSH2 Session from [chars] (tty = [dec]) for user ’[chars]’ using crypto cipher ’[chars]’, hmac ’[chars]’ closed Explanation Displays the SSH session closure information. Recommended Action No action is required.

Error Message %SSH-5-SSH2_SESSION: SSH2 Session request from [chars] (tty = [dec]) using crypto cipher ’[chars]’, hmac ’[chars]’ [chars] Explanation Displays the SSH session request information. Recommended Action No action is required.

Error Message %SSH-5-SSH2_USERAUTH: User ’[chars]’ authentication for SSH2 Session from [chars] (tty = [dec]) using crypto cipher ’[chars]’, hmac ’[chars]’ [chars] Explanation Displays the SSH user authentication status information. Recommended Action No action is required.

Error Message %SSH-5-SSH_CLOSE: SSH Session from [chars] (tty = [dec]) for user ’[chars]’ using crypto cipher ’[chars]’ closed Explanation Displays the SSH session closure information. Recommended Action No action is required.


1591

SSP Messages

Error Message %SSH-5-SSH_SESSION: SSH Session request from [chars] (tty = [dec]) using crypto cipher ’[chars]’ [chars] Explanation Displays the SSH session request information. Recommended Action No action is required.

Error Message %SSH-5-SSH_USERAUTH: User ’[chars]’ authentication for SSH Session from [chars] (tty = [dec]) using crypto cipher ’[chars]’ [chars] Explanation Displays the SSH user authentication status information. Recommended Action No action is required.

SSP Messages This section contains State Synchronization Protocol Manager (SSP) messages.

SSP-3 Error Message %SSP-3-DATACREATEFAIL: Creation of required data structures failed. Explanation SSP will not operate properly due to the abnormal initialization of required data

structures. Recommended Action Reload the device. If the error persists, contact your technical service

representative.

Error Message %SSP-3-EXCEEDMAXDOI: SSP maximum DOI exceeded. Explanation The configuration has exceeded the maximum number of SSP clients allowed on this

device at any one time. Recommended Action Verify your configuration and reduce the number of SSP clients running at the same time. If a large number of SSP clients is required, contact your technical service representative for assistance.

Error Message %SSP-3-NOSTART: SSP could not initialize. Explanation The SSP process could not successfully initialize. This condition might be caused by

unusual protocol startup times in certain topologies. Recommended Action Ensure that your IP redundancy mechanism (HSRP) configuration is valid and that all protocols have started. Try to configure SSP again. If this error recurs, contact your technical support representative.


1592

SSP Messages

Error Message %SSP-3-SRVSOCKCREATEFAIL: SSP socket creation failed. Explanation The SSP process could not establish a socket connection with the SSP peer. This

condition is likely to occur because either the device is under extreme load or it is misconfigured. Recommended Action Verify that the SSP configuration is valid. Configure SSP to use a different port

number. Reduce the load on the device.

SSP-4 Error Message %SSP-4-CANNOTRUNVER: SSP version [dec].[dec] was requested but is not supported in this image. Explanation The version of SSP requested by the active device is not available in this image. SSP

will not run on this device until it is upgraded or the active device is downgraded. Recommended Action Verify that all SSP peers are running compatible images and that the

configuration on each device is correct.

Error Message %SSP-4-GROUPCREATEFAIL: The SSP group could not be created. Explanation The maximum number of SSP groups has been reached. Only one SSP group is

permitted at one time. Recommended Action No action is required.

Error Message %SSP-4-MISMATCHEDVERRECV: Wrong version on received packet. Explanation The SSP version information in a received packet does not match the version that is

currently running on this device. Recommended Action Verify the configuration of all the SSP peers. Ensure that all peers are running

the correct image.

SSP-5 Error Message %SSP-5-DISABLED: SSP entering disabled state. Explanation SSP has entered the disabled state. This condition is normal under many circumstances. An example of a normal condition is when the SSP configuration is changed or when a tracked interface is shut down or fails. Recommended Action If this change occurred because of failure on the active peer, eliminate the

cause of failure and reload the failed device.


1593

SSSMGR Messages

SSP-6 Error Message %SSP-6-ACTIVE: SSP entering active state. Explanation SSP has entered the active state. Recommended Action No action is required.

Error Message %SSP-6-IPREDGRPADD: An IP Redundancy group listed in the SSP config has been added to this device. Explanation The device might now become the active device or the redundant device if no other

configuration items are missing. Recommended Action No action is required.

Error Message %SSP-6-IPREDGRPDEL: An IP Redundancy group listed in the SSP config has been removed from this device. Explanation The device might not become the active device or the redundant device if any

configuration items are missing. Recommended Action Add the IP redundancy group to the device, or remove it from the SSP

configuration.

Error Message %SSP-6-STANDBY: SSP entering standby state. Explanation SSP has entered standby state. Recommended Action No action is required.

SSSMGR Messages This section contains Subscriber Service Switching (SSS) Manager messages.

SSSMGR-3 Error Message %SSSMGR-3-BAD_CONTEXT_HANDLE: Corrupted SSS handle [[hex]] in SSS message. Explanation An internal SSS manager error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1594

SSSMGR Messages


Error Message %SSSMGR-3-DYNAMIC_UPDATE_NOT_SUPPORTED: [%d] Dynamic session updates not allowed on this %s session. It is an unsupported configuration. Explanation Updates on these sessions are not supported. This is an unsupported configuration. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SSSMGR-3-INFO_TYPE_NO_COPY_VECTOR: info type has no copy vector (%d). Explanation An internal error occurred in the Subscriber Service Switching (SSS) Manager process. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SSSMGR-3-INIT: Initialisation failure, %s Explanation An initialization failure occurred in the SSS Manager process. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1595

SSSMGR Messages


Error Message %SSSMGR-3-INVALID_FSM_STATE: Encountered an invalid SSS Mgr state [dec] in [chars] Explanation An internal SSS manager error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SSSMGR-3-INVALID_INFO_TYPE: Received an INVALID info type value (%d). Explanation The SSS Manager received an invalid information type. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SSSMGR-3-INVALID_SERVICE_TYPE: Received an INVALID service type (%d)%s. Explanation The SSS Manager received an invalid service type. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1596

SSSMGR Messages

Error Message %SSSMGR-3-MEMORY_LOW: Memory low (%d times), disconnecting session Explanation The SSS Manager has disconnected a session due to insufficient memory. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SSSMGR-3-NULL_FSM_CONTEXT: Encountered a NULL SSS Mgr context in [chars] Explanation The system has encountered a null context in the SSS manager. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SSSMGR-3-NULL_INFO_STRING: Received a NULL info string value. Explanation The SSS Manager received a NULL information string value. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1597

SSSMGR Messages

Error Message %SSSMGR-3-POLICY_CTX_POISONED: Policy context [hex] has bad magic, [hex]. Explanation The magic number in the policy context is wrong. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SSSMGR-3-RESOURCE_OVERFLOW: Resource overflow Explanation A fixed-size system resource has been exceeded. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SSSMGR-3-UNEXPECTED_MSG: Encountered an unexpected message: %s Explanation The SSS Manager received an unexpected message. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1598

SSSMGR Messages

Error Message %SSSMGR-3-UNEXPECTED_SIP_INFO: Encountered an unexpected SIP info: %s Explanation The SSS Manager encountered an unexpected SIP. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SSSMGR-3-UNSUPPORTED_CFG: Unsupported configuration detected: [uid: [int]] [chars] Explanation Unsupported configuration detected. Recommended Action Copy the error message exactly as it appears on the console or in the system


SSSMGR-5 Error Message %SSSMGR-5-IFCFG_NOTALLWED_IN_SVC: Interface-config not allowed at service config level, ignoring Explanation The interface configuration attribute is not allowed while in a service profile. It is supported only in user profiles. Recommended Action Remove the interface configuration attribute from the service profile and

reconfigure using a user profile.

Error Message %SSSMGR-5-UNSUPPORTED_CFG_NOTICE: Unsupported configuration detected, [chars] Explanation The value of the specified configuration parameter was out of range. This is not

considered an error as the value was adjusted to be within the supported range. Update the configuration source to a value within the supported range to avoid this message. Recommended Action No action is required.


1599

STACKMGR Messages

STACKMGR Messages This section contains stack manager controller messages.

STACKMGR-6 Error Message %STACKMGR-6-HDM_GET_DEVICE_RECORD_FAIL: Device Manager could not get device record. Explanation This switch could not obtain the device record for some or all of the all other switches

in the stack. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %STACKMGR-6-MASTER_ELECTED: Switch [dec] has been elected as MASTER of the stack Explanation The specified switch has been selected as the active switch. Recommended Action No action is required.

Error Message %STACKMGR-6-MASTER_READY: Master Switch [dec] is READY Explanation The active switch is ready for use. Recommended Action No action is required.

Error Message %STACKMGR-6-MSG_FAIL: Failed to retrieve stack message from port-asic [dec] in direction [dec] Explanation The module for the stack manager module failed to retrieve stack messages. Recommended Action No action is required.


1600

STACKMGR Messages

Error Message %STACKMGR-6-NORECORD: Switch removed event for switch [dec] with no switch record Explanation The module for the stack manager notifier has detected that a switch has been removed, but no switch record exists for the removed switch. Recommended Action No action is required.

Error Message %STACKMGR-6-STACK_LINK_CHANGE: Stack Port [chars] Switch [dec] has changed to state [chars] Explanation The status of the specified stack port has changed to active or inactive (up or down). Recommended Action No action is required.

Error Message %STACKMGR-6-SWITCH_ADDED: Switch [dec] has been ADDED to the stack Explanation The specified switch has been added to the stack. Recommended Action No action is required.

Error Message %STACKMGR-6-SWITCH_ADDED_SDM: Switch [dec] has been ADDED to the stack (SDM_MISMATCH) Explanation The specified switch has been added to the stack. Recommended Action No action is required.

Error Message %STACKMGR-6-SWITCH_ADDED_VM: Switch [dec] has been ADDED to the stack (VERSION_MISMATCH) Explanation The specified switch has been added to the stack. Recommended Action No action is required.

Error Message %STACKMGR-6-SWITCH_READY: Switch [dec] is READY Explanation The specified switch is in the ready state. Recommended Action No action is required.

Error Message %STACKMGR-6-SWITCH_REMOVED: Switch [dec] has been REMOVED from the stack Explanation The specified switch has been removed from the stack. Recommended Action No action is required.


1601

STAPL_OPEN Messages

STAPL_OPEN Messages This section contains Standard Test And Programming Language (STAPL) processing messages.

STAPL_OPEN-4 Error Message %STAPL_OPEN-4-ERROR_ALLOC: %Error: Can’t allocate [dec] bytes for STAPL data Explanation The system could not allocate the required memory to access the file. Recommended Action Check the memory usage of the system and retry the operation.

Error Message %STAPL_OPEN-4-ERROR_OPEN: %Error: Can’t open [chars] Explanation The system is unable to open the specified file. Recommended Action Ensure that the file name is correct. Enter the dir command to verify the file

name.

Error Message %STAPL_OPEN-4-ERROR_READ: %Error: STAPL file [chars] read failed Explanation An unknown error has occurred while the system was copying the STAPL program file

to a local buffer. Recommended Action Enter the del [chars] command to remove the file. Enter the copy command to recopy the file from a known good source to its desired destination [chars]. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %STAPL_OPEN-4-ERROR_SIZE: %Error: Bad file size [chars] Explanation The file is too small or too large for a STAPL program file. Recommended Action Enter the dir command and check the size of the file. Retry the operation.


1602

STORM_CONTROL Messages

STORM_CONTROL Messages This section contains storm control messages.

STORM_CONTROL-3 Error Message %STORM_CONTROL-3-FILTERED: A [chars] storm detected on [chars]. A packet filter action has been applied on the interface. Explanation The amount of traffic that has been detected on the interface has exceeded the

configured threshold values. The system is filtering excess traffic when packets are received, and the system is not forwarding packet traffic. Recommended Action Determine and fix the root cause of the excessive traffic on the interface.

STP_ISSU Messages This section contains Spanning Tree Protocol (STP) in-service software upgrade (ISSU) messages.

STP_ISSU-3 Error Message %STP_ISSU-3-BUFFER: STP ISSU client failed to get buffer for message, error %d Explanation The Spanning Tree Protocol (STP) ISSU client was unable to get buffer space for

building a negotiation message. As a result, it cannot send the negotiation message to the standby unit and the standby unit cannot be brought up. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1603

STP_ISSU Messages

Error Message %STP_ISSU-3-CAPABILITY: STP ISSU client %s Explanation The STP ISSU client detected an error during capability negotiation. As a result, there

is a mismatch in the client capability between the active and standby unit. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %STP_ISSU-3-CFM_MISMATCH: Unsupported CFM and STP configuration detected. Reloading standby Explanation STP ISSU client observed MST PVST simuation capability negotiation

failure while CFM was enabled. When this error happens, remove CFM configuration on the active and restart ISSU upgrade. Recommended Action Issue the show tech-support command to gather data that may help identify the nature of the error. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message %STP_ISSU-3-INIT: STP ISSU client initialization failed at %s, error %s Explanation The STP ISSU client could not be initialized, this will cause catastrophic failure when

an ISSU upgrade or downgrade is performed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1604

STP_ISSU Messages

Error Message %STP_ISSU-3-MSG_NOT_OK: STP ISSU client message %d is not compatible Explanation The STP ISSU client received an incompatible message from the peer unit. The message

cannot be processed by this unit. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %STP_ISSU-3-MSG_SIZE: STP ISSU client failed to get the message size for message %d Explanation The STP ISSU client was unable to calculate the message size for the message specified.

The client will be unable to send the message to the standby unit. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %STP_ISSU-3-POLICY: STP ISSU client message type %d is %s Explanation The STP ISSU client received a message type that it does not support. A policy is




1605

STP_ISSU Messages

Error Message %STP_ISSU-3-SEND_FAILED: STP ISSU client failed to send a negotiation message, error %d Explanation The STP ISSU client could not send a session negotiation message to the peer. As a

result, the standby unit cannot be brought up. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %STP_ISSU-3-SESSION: STP ISSU client %s Explanation The STP ISSU client detected an error during a session negotiation with the peer unit.



Error Message %STP_ISSU-3-SESSION_UNREGISTRY: STP ISSU client failed to unregister session information. Error: %d (%s) Explanation The STP ISSU client was unable to unregister session information. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1606

STP_SP Messages

Error Message %STP_ISSU-3-TRANSFORM: STP ISSU client %s transform failed, error %s Explanation The STP ISSU client could not transform the message. If the transmit transformation

failed, the checkpoint message cannot be sent to the standby unit. If the receive transformation failed, the checkpoint message cannot be applied on the standby unit. In either case, the STP state will not be identical with the active unit. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %STP_SP-3-STP_MODE_CHANGE_NOT_ALLOWED: Unable to program port ASIC MAC match register on one or more slots. Cannot run change STP mode. Explanation The Spanning Tree Protocol (STP) is unable to reserve and program the port ASIC MAC match registers because insufficient match registers are available. PVST and rapid-PVST cannot be run. Recommended Action To make available more MAC match registers, disable other protocols that use the MAC match registers. You can view protocols that use port ASIC match registers by entering the remote command switch show platform mrm info command.

STP_SP Messages STP_SP-2 Error Message %STP_SP-2-STP_EARL_MR_PROG_FAIL: Failed to program the EARL match register for STP. Explanation The STP SSTP MAC address needs to be programmed in the Earl match register for

normal STP operations. There are a limited number of Earl match registers. This messages indicates that either a SW error occured or the HW resource is not available. Recommended Action Please review the configuration guidelines for the switch features. You can try rebooting the switch. If issue persists, please contact the Cisco Technical Support for further assistance.


1607

SUBSYS Messages

SUBSYS Messages This section contains software subsystems messages.

SUBSYS-3 Error Message %SUBSYS-3-UNORDERED: The subsys class [dec]([chars]) has no initialization order. Explanation The specified class subsystem has an unknown initialization order. Recommended Action Copy the message exactly as it appears on the console or in the system log.


SUPERVISOR Messages This section contains supervisor engine messages.

SUPERVISOR-3 Error Message %SUPERVISOR-3-FATAL: [chars] Explanation An internal error occurred in the supervisor engine ASIC. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1608

SUP_LINE_CARD_Messages

SUP_LINE_CARD_Messages Error Message %SUP_LINE_CARD_COMPATIBILITY-6-SW_VERSION_MISMATCH: [chars] Explanation Compatibility mismatch between software versions of Line Card and Supervisor. Card

allowed to bootup. Recommended Action No action is required.

SUPQ Messages This section contains supervisor engine queue messages.

SUPQ-3 Error Message %SUPQ-3-THROTTLE_CPU_QUEUE: Invalid application ID [dec] used for throttling Explanation An application has passed an invalid application ID to the facility that is used for throttle checking operations. Recommended Action Copy the message exactly as it appears on the console or in the system log.


SUPQ-4 Error Message %SUPQ-4-CPUHB_RECV_STARVE: [chars] Explanation The system has detected that messages directed for the CPU are being delayed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1609

SUPQ Messages


Error Message %SUPQ-4-CPUHB_SLOW_TRANSMIT: [chars] Explanation The interface is no longer transmitting at an optimal speed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SUPQ-4-CPUHB_TX_FAIL: [chars] Explanation The system is discarding system status or operational messages (heartbeat messages). Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SUPQ-4-PORT_QUEUE_STUCK: Port queue Stuck for asic [dec] port [dec] queue [dec] Explanation The system has detected that the port queue could not be cleared in a reasonable time. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1610

SUPW_PROCMIB Messages

Error Message %SUPQ-4-RECV_QUEUE_STUCK: Receive queue Stuck for asic [dec] queue [dec] Explanation The system has detected that the receive queue could not be cleared in a reasonable time. Recommended Action Copy the message exactly as it appears on the console or in the system log.


SUPW_PROCMIB Messages This section contains supervisor engine MIB messages.

SUPW_PROCMIB-3 Error Message %SUPW_PROCMIB-3-IPC_PORTOPEN_FAIL: Failed to open port while connecting to process statistics: error code = [chars] Explanation An error occurred during an attempt to open a port for an IPC message. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SUPW_PROCMIB-3-IPC_TRANSMIT_FAIL: Failed to send process statistics update : error code = [chars] Explanation An error occurred during an attempt to send an IPC message. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1611

SVCLC Messages


Error Message %SUPW_PROCMIB-3-MALLOC_FAILURE_IPC: Failed to allocate IPC message to contact process Explanation A memory allocation failure has occurred during the processing of an IPC message. Recommended Action Copy the message exactly as it appears on the console or in the system log.


SVCLC Messages This section contains service line card (SVCLC) messages.

SVCLC-2 Error Message %SVCLC-2-MAJORTEMP: Module [dec] CPU[dec] has exceeded its allowed operating temperature. (current temp=[dec]C) Module will be shut down immediately Explanation The specified service line card in the system has sent a thermal shutdown request to the

supervisor engine. The first [dec] is the module number, the second [dec] is the CPU number, and the third [dec] is the temperature. Recommended Action Determine if the environment is too hot. If the environment is not too hot,

replace the hardware.

SVCLC-4 Error Message %SVCLC-4-MINORTEMP: Module [dec] CPU[dec] has exceeded its normal operating temperature. (current temp=[dec]C) Explanation The specified CPU on the specified service line card is too hot. The first [dec] is the module number, the second [dec] is the CPU number, and the third [dec] is the temperature. Recommended Action Determine if the environment is too hot. If the environment is not too hot,

replace the hardware.


1612

SVCLC Messages

Error Message %SVCLC-4-TEMPRECOVER: Module [dec] CPU[dec] has returned to its normal operating temperature. (current temp=[dec]C) Explanation The specified service line card in the system has sent a thermal recovery event to the supervisor engine. The first [dec] is the module number, the second [dec] is the CPU number, and the third [dec] is the temperature. Recommended Action No action is required.

SVCLC-5 Error Message %SVCLC-5-FWTRUNK : Firewalled VLANs configured on trunks Explanation One or more secure VLANs belong to both secured and ordinary trunks. This

configuration may compromise the security of the secure VLANs. Recommended Action Change the trunk or the secure VLAN configuration so that they do not overlap. Enter either the switchport trunk allowed vlan command to change trunk configuration or the firewall vlan group command to change the secure VLAN configuration.

Error Message %SVCLC-5-INTDOWN: mod [dec] failed to bring up all interfaces Explanation One or more of the module interfaces failed to come up. Recommended Action Reset the module.

Error Message %SVCLC-5-SVCLCMULTI: Group [dec] being tied to more than one module Explanation The specified group is tied to multiple service modules. A group should not be

associated with more than one service module unless a failover configuration is being used. Recommended Action If a failover configuration is in use, no action is required. Otherwise enter the

show svclc module command to find out which group is being tied to more than one module. Then remove multiple associations by entering the no svclc module mod vlan-group group command.

Error Message %SVCLC-5-SVCLCNTP: Could not update clock on the module [dec], rc is [dec] Explanation Either the line card or the Cisco IOS software encountered some problems while

sending a clock update from Cisco IOS to the line card. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1613

SW_DAI Messages


Error Message %SVCLC-5-SVCLCSCP: Service module SCP communication failed for module [dec], subopcode is [dec] Explanation Either the line card or the Cisco IOS software encountered some problems while

communicating through SCP channels. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SVCLC-5-SVCLCVTPMODE: VTP mode is set to non-transparent Explanation VTP mode is not transparent, so VTP may dynamically modify VLANs, including those

that are associated with the service modules. Recommended Action Change the VTP to transparent mode by entering the vtp mode transparent

command.

SW_DAI Messages This section contains Dynamic ARP Inspection (DAI) messages.

SW_DAI-4 Error Message %SW_DAI-4-ACL_DENY: [dec] Invalid ARPs ([chars]) on [chars], vlan [dec].([[enet]/[chars]/[enet]/[chars]/[time-of-day]C]) Explanation The switch has received ARP packets that are considered invalid by ARP inspection.

The packets are invalid, and their presence indicates that administratively denied packets have been seen in the network. This log message shows up when packet(s) have been denied by ACLs either explicitly or implicitly (with static ACL configuration). The presence of these packets indicates that man-in-the-middle attack(s) may have been attempted in the network. Recommended Action This is an informational message only. No action is required.


1614

SW_DAI Messages

Error Message %SW_DAI-4-DHCP_SNOOPING_DENY: [dec] Invalid ARPs ([chars]) on [chars], vlan [dec].([[enet]/[chars]/[enet]/[chars]/[time-of-day]C]) Explanation The switch has received ARP packets that are considered invalid by ARP inspection.

The packets are invalid, and their presence may be an indication of man-in-the-middle attacks being attempted in the network. This message is logged when the sender’s IP and MAC binding for the received VLAN is not present in the DHCP snooping database. The first [chars] is either Req (request) or Res (response), and the second [chars] is the short name of the ingress interface. The second [dec] is the ingress VLAN ID. [enet]/[chars]/[enet]/[chars]/[time-of-day] is the MAC address of the sender, the IP address of the sender, the MAC address of the target, the IP address of the target, and the time of day. Recommended Action This is an informational message only. No action is required.

Error Message %SW_DAI-4-INVALID_ARP: [dec] Invalid ARPs ([chars]) on [chars], vlan [dec].([[enet]/[chars]/[enet]/[chars]/[time-of-day]C]) Explanation The switch has received ARP packets that are considered invalid by ARP inspection.

The packets do not pass one or more validation checks of the source or destination MAC address or the IP address. The first [dec] is the number of invalid ARP packets. The first [chars] is either Req (request), Res (response), or Invalid Opcode. The second [chars] is the short name of the ingress interface. The second [dec] is the ingress VLAN ID. [enet]/[chars]/[enet]/[chars]/[time-of-day] is the MAC address of the sender, the IP address of the sender, the MAC address of the target, the IP address of the target, and the time of day. Recommended Action This is an informational message only. No action is required.

Error Message %SW_DAI-4-PACKET_BURST_RATE_EXCEEDED: [dec] packets received in [dec] seconds on [chars]. Explanation The switch has received the given number of ARP packets in the specified burst interval.

The interface is in the error-disabled state when the switch receives packets at a higher rate than the configured packet rate every second over the configured burst interval. The message is logged just before the interface is error disabled and if the configured burst interval is more than a second. The first [dec] is the number of packets, the second [dec] is the number of seconds, and [chars] is the affected interface. Recommended Action This is an informational message only. No action is required.

Error Message %SW_DAI-4-PACKET_RATE_EXCEEDED: [dec] packets received in [dec] milliseconds on [chars]. Explanation The switch has received the specified number of ARP packets in the specified time on the specified interface. This message is logged just before the port is error-disabled because of the exceeded packet rate. This message also is logged when the burst interval is set to 1 second. Recommended Action This is an informational message only. No action is required.


1615

SW_DAI Messages

Error Message %SW_DAI-4-SPECIAL_LOG_ENTRY: [dec] Invalid ARP packets [[time-of-day]C] Explanation The switch has received ARP packets considered invalid by ARP inspection. The

packets are invalid, and their presence may be an indication of man-in-the-middle attacks being attempted in the network. This message differs from other messages in that while the others can be used to provide as much information about the packet as possible, this message is used as a general message when the rate of incoming packets exceeds the DAI logging rate. Recommended Action This is an informational message only. No action is required.

SW_DAI-6 Error Message %SW_DAI-6-ACL_PERMIT: [dec] ARPs ([chars]) on [chars], vlan [dec].([[enet]/[chars]/[enet]/[chars]/[time-of-day]C]) Explanation The switch has received ARP packets that have been permitted as a result of an ACL

match. Recommended Action This is an informational message only. No action is required.

Error Message %SW_DAI-6-DHCP_SNOOPING_PERMIT: [dec] ARPs ([chars]) on [chars], vlan [dec].([[enet]/[chars]/[enet]/[chars]/[time-of-day]C]) Explanation The switch has received ARP packets that have been permitted because the sender’s IP

and MAC address match against the DHCP snooping database for the received VLAN. The first [dec] is the number of valid ARP packets. The first [chars] is either Req (request) or Res (response), and the second [chars] is the short name of the ingress interface. The second [dec] is the ingress VLAN ID. [enet]/[chars]/[enet]/[chars]/[time-of-day] is the MAC address of the sender, the IP address of the sender, the MAC address of the target, the IP address of the target, and the time of day. Recommended Action This is an informational message only. No action is required.


1616

SWEPA Messages

SWEPA Messages This section contains software encryption port adapter (SWEPA) and key management messages.

SWEPA-6 Error Message %SWEPA-6-EPA_EXP_RUNNING: Exp Running .... Explanation The EXP process is running. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SWEPA-6-EPA_EXP_TIMER_EXPIRED: Exp Timer Expired! Explanation The EXP timer has expired. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SWEPA-6-FAILED_TO_ALLOCATE_ENCRYPT_QUE: Failed to allocate the encrypt queue. Explanation The encryption queue could not be allocated. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1617

SWEPA Messages


Error Message %SWEPA-6-FAILED_TO_START_DES_PROCESS: Failed to start DES process Explanation The DES process has failed to start. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SWEPA-6-FAILED_TO_START_EXP_PROCESS: Failed to start EXP process Explanation The EXP process has failed to start. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SWEPA-6-INIT_SW_EPA_IDB: Init swepa idb start ... Explanation The software encryption port adapter information descriptor block (IDB) is being

initialized. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1618

SWITCH Messages

Error Message %SWEPA-6-START_DES_PROCESS: DES process start ... Explanation The DES process has started. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SWEPA-6-START_EXP_PROCESS: EXP process start ... Explanation The EXP process has started. Recommended Action Copy the message exactly as it appears on the console or in the system log.


SWITCH Messages This section contains switch interface messages.

SWITCH-3 Error Message %SWITCH-1-RF_REGISTRTN_FAILED: unable to register switch driver client to RF Explanation The switch driver client could not be registered to the redundancy facility (RF). Recommended Action Copy the message exactly as it appears on the console or in the system log.



1619

SWITCHOVER Messages


SWITCHOVER Messages This section contains line card switchover-related messages.

SWITCHOVER-6 Error Message %SWITCHOVER-6-LC_HA_UNAWARE: Line card (type [hex]) in slot [dec] is not confgured HA mode aware Explanation The line card in the specified slot does not support the configured RP redundancy mode.

The line card will be reset and reinitialized during RP failover. Recommended Action No action is required.

SWITCH_QOS_TB Messages This section contains trusted boundary messages.

SWITCH_QOS_TB-5 Error Message %SWITCH_QOS_TB-5-TRUST_DEVICE_DETECTED: [chars] detected on port [chars], port trust enabled. Explanation The trusted boundary facility has detected a device that matches the trusted device

setting for the port, and the port trust state has been modified. Recommended Action No action is required.

Error Message %SWITCH_QOS_TB-5-TRUST_DEVICE_LOST: [chars] no longer detected on port [chars], port set to untrusted. Explanation The trusted boundary facility has lost contact with a trusted device, and has set the port

trust state to untrusted. Recommended Action No action is required.

SWITCH_SPAN_ISSU Messages This section contains span switch in-service software upgrade (ISSU) messages.


1620

SWITCH_SPAN_ISSU Messages

SWITCH_SPAN_ISSU-3 Error Message %SWITCH_SPAN_ISSU-3-BUFFER: span switch ISSU client failed to get buffer for message, error %d Explanation The SPAN switch ISSU client was unable to get a buffer for building a negotiation



Error Message %SWITCH_SPAN_ISSU-3-CAPABILITY: span switch ISSU client %s Explanation The SPAN switch ISSU client detected an error during capability negotiation. As a



Error Message %SWITCH_SPAN_ISSU-3-INIT: span switch ISSU client initialization failed at %s, error %s Explanation The SPAN switch ISSU client could not be initialized. This condition will cause a




1621



Error Message %SWITCH_SPAN_ISSU-3-MSG_NOT_OK: span switch ISSU client message %d is not compatible Explanation The SPAN switch ISSU client received an incompatible message from the peer unit. The message cannot be processed by this unit. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SWITCH_SPAN_ISSU-3-MSG_SIZE: span switch ISSU client failed to get the message size for message %d Explanation The SPAN switch ISSU client was unable to calculate the message size for the message



Error Message %SWITCH_SPAN_ISSU-3-POLICY: span switch ISSU client message type %d is %s Explanation The SPAN switch ISSU client received a message type that it does not support. A policy




1622


open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show issu session commands and your pertinent troubleshooting logs.

Error Message %SWITCH_SPAN_ISSU-3-SEND_FAILED: span switch ISSU client failed to send a negotiation message, error %d Explanation The SPAN switch ISSU client could not send a session negotiation message to the peer.



Error Message %SWITCH_SPAN_ISSU-3-SESSION: span switch ISSU client %s Explanation The SPAN switch ISSU client detected an error during a session negotiation with the




1623

SW_MGR Messages

Error Message %SWITCH_SPAN_ISSU-3-TRANSFORM: span switch ISSU client %s transform failed, error %s Explanation The SPAN switch ISSU client could not transform the message. If the transmit

transformation failed, the checkpoint message cannot be sent to the standby unit. If the receive transformation failed, the checkpoint message cannot be applied on the standby unit. In either case, the SPAN switch state will not be identical with the active unit. Recommended Action Copy the message exactly as it appears on the console or in the system log.


SW_MGR Messages This section contains segment switch manager messages.

SW_MGR-3 Error Message %SW_MGR-3-CM_ERROR: Connection Manager Error - [chars]. Explanation An error has occurred in the segment switch connection manager. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SW_MGR-3-CM_ERROR_CLASS: Connection Manager Error: Class [chars]: [chars]. Explanation An error has occurred in the connection manager. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1624

SW_MGR Messages


Error Message %SW_MGR-3-CM_ERROR_FEATURE: Connection Manager Feature Error: (%s) %s. Explanation A segment switch connection manager feature class error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SW_MGR-3-CM_ERROR_FEATURE_CLASS: Connection Manager Feature Error: Class %s: (%s) - %s. Explanation A segment switch connection manager feature error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SW_MGR-3-FHM_ERROR: SSM Feature Handler Manager Error - %s. Explanation A feature handler manager error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1625

SW_MGR Messages


Error Message %SW_MGR-3-INVALID_HANDLE: Segment Manager Error - Invalid [chars] handle - [dec]. Explanation The connection manager encountered an invalid handle. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SW_MGR-3-INVALID_SEGMENT: Segment Switch Manager Error - Invalid segment - [chars]. Explanation The segment switch manager encountered an invalid segment. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SW_MGR-3-SM_ERROR: Segment Manager Error - [chars]. Explanation An error has occurred in the segment manager. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1626

SW_VLAN Messages

Error Message %SW_MGR-3-SSM_SEG_ISSU: SSM Segment ISSU: [chars] not supported. Explanation ISSU of this SSM Segment is not supported. Recommended Action Not Available.

SW_VLAN Messages This section contains Virtual LAN (VLAN) manager messages.

SW_VLAN-4 Error Message %SW_VLAN-4-VLAN_ADD_FAIL: Failed to add VLAN [dec] to vlan database: [chars] Explanation The specified VLAN could not be added to the VLAN database. The platform may not

allow the addition or there may be insufficient memory to expand the VLAN database. Recommended Action Check the usage of the VLAN in the active and standby device to determine

whether the VLAN is valid. Check the memory usage in the standby device. Unconfigure the feature that occupies more memory and retry the VLAN creation operation. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SW_VLAN-4-VLAN_CREATE_FAIL: Failed to create VLANs [chars]: [chars] Explanation The specified VLANs could not be created. The VLAN manager called a VLAN

database routine to create one or more VLANs, but the port manager failed the VLAN creation requests. A possible cause of this error is that the VLANs already exist in the port manager as internal VLANs. Recommended Action Check the internal VLAN usage by entering the show vlan internal usage command. Unconfigure the feature that occupies the internal VLAN and retry the VLAN creation operation. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support


1627

SW_VLAN Messages


Error Message %SW_VLAN-4-VLANMGR_INVALID_DATABASE_DATA: VLAN MANAGER received bad data of type %s: value %d from function %s Explanation The VLAN manager received invalid data from a VLAN configuration database



Error Message %SW_VLAN-4-VTP_DB_INVALID_VLANID: Invalid VLAN ID [dec] found in VTP database download Explanation An invalid VLAN ID was detected in the VTP database during the download of the VTP configuration file. This condition indicates that the VTP configuration file in NVRAM is corrupted. Recommended Action Save a copy of the vlan.dat file that includes the invalid VLAN ID to help

investigate the condition. Copy the message exactly as it appears on the console or in the system log. Enter the show vtp status and the show vlan commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %SW_VLAN-4-VTP_DB_SIZE_CHECK_FAILED: The %s VTP database of length %d cannot be supported by the system Explanation The VLAN trunking protocol (VTP) database size is larger than the system can support. Recommended Action Reduce the database size by decreasing the configuration parameters. For

example, reduce the size of vlan-names.


1628

SW_VLAN Messages

Error Message %SW_VLAN-6-VTP_DOMAIN_NAME_CHG: VTP domain name changed to [chars]. Explanation The VTP domain name was changed through configuration to the name

specified in the message. A management domain is the naming scope of a VLAN name. Each VLAN has a name that is unique within the management domain. Recommended Action This is an informational message only. No action is required.

Error Message %SW_VLAN-4-VTP_PRIMARY_SERVER_CHG: %e has become the primary server for the %s VTP feature Explanation The primary server status has changed and the indicated device has become the primary

server for the indicated VTP feature. Recommended Action No action is required.

Error Message %SW_VLAN-4-VTP_SEM_BUSY: VTP semaphore is unavailable for function [chars]. Semaphore locked by [chars] Explanation The VTP database is currently locked by another task and is not available. Recommended Action Retry the operation later. If this condition recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

SW_VLAN-6 Error Message %SW_VLAN-6-OLD_CONFIG_FILE_READ: Old version [dec] VLAN configuration file detected and read OK. Version [dec] files will be written in the future. Explanation This message indicates that the VLAN software detected an old version of the VLAN configuration file format. The software was able to interpret the file with no problems but will create files using the new format in the future. The first [dec] is the old version number, and the second [dec] is the new version number. Recommended Action No action is required.


1629

SW_VLAN Messages

Error Message %SW_VLAN-6-VTP_DOMAIN_NAME_CHG: VTP domain name changed to [chars]. Explanation The VTP domain name was changed through configuration to the name specified in the

message. A management domain is the naming scope of a VLAN name. Each VLAN has a name that is unique within the management domain. Recommended Action No action is required.

Error Message %SW_VLAN-6-VTP_MODE_CHANGE: VLAN manager changing device mode from [chars] to [chars]. Explanation Some switch devices must automatically change VTP device modes upon receipt of a

VLAN configuration database containing more than a set number of VLANs, depending on the device. This message indicates that such a spontaneous conversion has occurred, what the previous mode was, and what the current mode is. [chars] is the VTP device mode. In VTP server mode, the VLAN manager must record each change of VTP configuration and each change of device configuration relating to VTP (such as mode changes, device domain name changes, and password changes) to non-volatile storage using IFS system calls. If a system call fails, the device must spontaneously convert to the VTP client mode. Call failures are usually the result of a hardware failure of the non-volatile storage system, which may require replacement. Other possible causes include software bugs or, in the case of TFTP storage, a transient network or TFTP server failure. Recommended Action No action is required.

Error Message %SW_VLAN-6-VTP_PRUNING_CHANGE: VTP Operational Pruning [chars]. Explanation VTP operational pruning has been enabled or disabled as shown in [chars], due to either

an administrative pruning change, a VTP mode change, or VTP configuration propagation. To view the reason for the change, enter the show vtp status command. Recommended Action No action is required.

SW_SP-VLAN Error Message %SW_VLAN-SP-6-VTP_DOMAIN_NAME_CHG: VTP domain name changed to %s. Explanation The VTP domain name was changed through configuration to the name specified in the

message. A management domain is the naming scope of a VLAN name. Each VLAN has a name that is unique within the management domain. Recommended Action No action is required.


1630

SW_VLAN_ISSU Messages

SW_VLAN_ISSU Messages This section contains switch VLAN in-service software upgrade (ISSU) messages.

SW_VLAN_ISSU-2 Error Message %SW_VLAN_ISSU-2-GET_BUFFER: Switch Vlan ISSU client failed to get buffer for message. Error: %d (%s) Explanation The switch VLAN ISSU client was unable to get buffer space for building a negotiation



Error Message %SW_VLAN_ISSU-2-INIT: Switch Vlan ISSU client initialization failed to %s. Error: %d (%s) Explanation The switch VLAN ISSU client could not be initialized. This initialization failure must

be addressed before an in-service software upgrade or downgrade can be performed successfully. Otherwise, a software upgrade or downgrade will result in downtime. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1631


Error Message %SW_VLAN_ISSU-2-SEND_NEGO_FAILED: Switch Vlan ISSU client failed to send negotiation message. Error: %d (%s) Explanation The switch VLAN ISSU client was unable to send a session negotiation message to the

peer device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SW_VLAN_ISSU-2-SESSION_NEGO: Switch Vlan ISSU client encountered unexpected client nego_done. Error: %d (%s) Explanation An ISSU-compliant client transitions through a series of internal states. The switch

VLAN ISSU client encountered a client negotiation done state that was unexpected. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SW_VLAN_ISSU-2-SESSION_REGISTRY: Switch Vlan ISSU client failed to register session information. Error: %d (%s) Explanation The switch VLAN ISSU client was unable to register session information. If a problem




1632



SW_VLAN_ISSU-3 Error Message %SW_VLAN_ISSU-3-CAP_INVALID_SIZE: Switch Vlan ISSU client capability list is empty. Explanation The switch VLAN ISSU client capability exchange list is empty, which is an invalid


Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show issu capability entires commands and your pertinent troubleshooting logs.

Error Message %SW_VLAN_ISSU-3-CAP_NOT_COMPATIBLE: Switch Vlan ISSU client capability exchange result incompatible. Explanation Based on the results of the capability exchange, the switch VLAN ISSU client is not

compatible with the peer. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SW_VLAN_ISSU-3-INVALID_SESSION: Switch Vlan ISSU client does not have a valid registered session. Explanation The switch VLAN ISSU client does not have a valid registered session. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1633


information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs.

Error Message %SW_VLAN_ISSU-3-MSG_NOT_COMPATIBLE_WITH_PEER: ’Message Type %d’ is not supported by Switch Vlan ISSU client at peer Explanation The switch VLAN ISSU client at the peer supervisor is not compatible for this message

type. The switch VLAN client will be marked as incompatible with the peer. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SW_VLAN_ISSU-3-MSG_NOT_OK: Switch Vlan ISSU client ’Message Type %d’ is not compatible Explanation The switch VLAN ISSU client received an incompatible message from the peer device.




1634


Error Message %SW_VLAN_ISSU-3-MSG_SIZE: Switch Vlan ISSU client failed to get the MTU for Message Type %d. Error: %d (%s) Explanation The switch VLAN ISSU client was unable to calculate the MTU for the specified

message. As a result, the client is unable to send the message to the standby device. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SW_VLAN_ISSU-3-SESSION_UNREGISTRY: Switch Vlan ISSU client failed to unregister session information. Error: %d (%s) Explanation The switch VLAN ISSU client was unable to unregister session information. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SW_VLAN_ISSU-3-TRANSFORM_FAIL: Switch Vlan ISSU client %s transform failed for ’Message Type %d’. Error: %d (%s) Explanation The switch VLAN ISSU client could not transform the specified message type. If the

transmit transformation failed, the checkpoint message was not sent to the standby device. If the receive transformation failed, the checkpoint message was not applied on the standby device. In either case, the switch VLAN state between the active device and the standby device is not identical. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1635

SW_VLAN_RF Messages


SW_VLAN_RF Messages This section contains switch VLAN redundancy facility (RF) messages.

SW_VLAN_RF-3 Error Message %SW_VLAN_RF-3-CREATE_PROCESS: Switch Vlan RF client failed to create %s process Explanation The switch VLAN redundancy facility (RF) client could not create a process. As a result, bulk synchronization will fail. Recommended Action Copy the message exactly as it appears on the console or in the system log.


SYS Messages This section contains operating system messages.

SYS-2 Error Message %SYS-2-BAD_BM_ARG: Invalid BM index boolean used as argument ([dec]) Explanation An illegal boolean manager index argument was referenced. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1636

SYS Messages


Error Message %SYS-2-CHUNKPARTIAL: Attempted to destroy partially full chunk, chunk [hex]. Explanation A software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SYS-2-FAILEDUPDATE: Failed to update Process id: %d in %s Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SYS-2-IMMORTAL: Attempt to shut down management process [dec] ([chars]). Explanation An attempt was made to shut down the specified management process. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands, the stack trace, and your pertinent troubleshooting logs.


1637

SYS Messages

Error Message %SYS-2-INPUT_GETBUF: Bad getbuffer, bytes= [dec], for interface= [chars] Explanation The software requested a buffer that is larger than the largest configured buffer size, or

it requested a negative-sized buffer. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SYS-2-NOPID: Process MIB is not aware of Process id: %d Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SYS-2-NV_BAD_PTR: Bad NVRAM pointer. NV Header values are, nv: %p .textbase: %p .textsize: %d .magic: 0x%X .checksum: 0x%X .system_version: %d .textptr: %p v1_ptr: %p .priv: %p Explanation A pointer corruption in NVRAM caused a failure in accessing the NVRAM. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1638

SYS Messages

Error Message %SYS-2-SYSMEMINFO: System Memory: [int]K total, [int]K used, [int]K free Explanation This is an auxiliary message to several memory-related messages. It provides only additional system memory information usage. Recommended Action Copy the message exactly as it appears on the console or in the system log.


SYS-3 Error Message %SYS-3-BADRESID: Clock hardware returned bad residual [dec]. Explanation A software error occurred. Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message %SYS-3-CHUNK_NO_EXMEM: No handler to [chars] external memory. Explanation An attempt was made to allocate or free a chunk of external memory, but no handler for

managing external memory was registered. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SYS-3-MEMSEMFAIL: Mempool semaphore creation failed for [chars] Explanation Semaphore creation for the specified memory pool has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1639

SYS Messages


Error Message %SYS-3-PREEMPTSUSP: Suspending a preemptive process [chars] Explanation A preemptive process attempted a suspend, which is not allowed because they are

expected to finish their work as quickly as possible and go back to idle queue. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SYS-3-PROCSEMFAIL: Process semaphore creation for preemptive processes failed. Explanation Creation of a process function semaphore to protect the critical section of the process

create routine has failed. The semaphore creation can fail if there is not enough chunk memory to create the event structure. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1640

SYS Messages

SYS-4 Error Message %SYS-4-CPURESRISING: %s%s is seeing %s cpu util %u%% at %s level more than the configured %s limit %u %% Explanation The system is experiencing high CPU usage, possibly from a process that is monopolizing the CPU. This condition demands immediate attention because packets or calls may be dropped. This message should be matched with a corresponding CPURESFALLING or CPURESUNAPPLY notification. Recommended Action No action is required.

SYS-5 Error Message %SYS-5-CONFIG: Configured from [chars] Explanation The router’s configuration was changed. Recommended Action This is a notification message only. No action is required.

Error Message %SYS-5-FIFOBUS_ERR: Flow-control threshold on module [dec] has exceeded the default value. Threshold will be set to lower value Explanation The FIFO threshold values are monitored for flow-control. When the threshold value

exceeds the default, the value is set to a new (lower) value Recommended Action This is an informational message only. No action is required.

Error Message %SYS-5-PRIV_I: Privilege level set to %d by%s%s Explanation The privileged mode is enabled or the privilege level is changed. As a result, the associated privilege level, user ID, and line information will be logged. Recommended Action No action is required. To disable logging of these events, enter the no logging userinfo command from the global configuration mode.

SYS-6 Error Message %SYS-6-CLOCKUPDATE: System clock has been updated from [chars] to [chars], configured from [chars] by [chars]. Explanation The system clock has been modified. Recommended Action This is an informational message only. No action is required.


1641

SYS Messages

Error Message %SYS-6-CPURESFALLING: %s%s is no longer seeing %s high cpu at %s level for the configured %s limit %u%%, current value %u%% Explanation The CPU usage has returned to normal after exceeding a threshold of high usage. Any

process that was disabled during the period of high CPU use can now be enabled. Recommended Action No action is required.

Error Message %SYS-6-CPURESUNAPPLY: %s%s is no longer monitoring %s cpu at %s level for the configured %s limit. Explanation CPU usage is no longer being monitored for the configured threshold level indicated in

the message. The corresponding policy is revoked. Recommended Action No action is required.

Error Message %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host %s%s%s%s Explanation System logging to the indicated server or host (VRF) has started or stopped. Recommended Action No action is required.

Error Message %SYS-6-NOBRIDGE: Bridging software not present Explanation Your system is not configured to be a bridge. Recommended Action Configure the bridging software.

Error Message %SYS-6-READ_BOOTFILE_SKIP: boot system [chars] command is skipped Explanation A configured boot system command is skipped. Either the system experienced a crash

while loading this image in the last attempt or the filename is not properly specified. Subsequent boot system commands will be tried Recommended Action Replace the failed boot system image with a good one. There could be various reasons that this specified image failed, for example the image might be with a bad checksum.

SYS-SP Error Message %SYS-SP-3-LOGGER_FLUSHING: System pausing to ensure console debugging output. Explanation Debugging or informational messages are being generated faster than they can be

displayed on the console. In order to guarantee that they can be seen, the rest of the system is paused until the console output catches up. This can break time-critical behavior, such as maintaining an ISDN link. Recommended Action Consider using conditional debugging, turning off console logging, or using

the o logging console guaranteed command, or turning off link-state messages for some interfaces.


1642

SYSLOGD Messages

Error Message %SYS-SP-3-LOGGER_FLUSHED: System was paused for %TE to ensure console debugging output. Explanation Debugging or informational messages are being generated faster than they can be

displayed on the console. In order to guarantee that they can be seen, the rest of the system was paused until the console output catches up. This can break time-critical behavior, such as maintaining an ISDN link. Recommended Action Consider using conditional debugging, turning off console logging, or using

the o logging console guaranteed command, or turning off link-state messages for some interfaces.

SYSLOGD Messages This section contains system logging (SYSLOG) messages.

SYSLOGD-3 Error Message %SYSLOGD-3-DROPPED_MESSAGES: A total of [int] messages have been dropped by the syslog daemon, due to [chars] Explanation The syslogd process has dropped received messages. The syslogd process may be

receiving too many messages to process before the buffer fills, or it may have received a message for which there was insufficient memory available. In either case, there may be a bug in the sending process. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1643

SYSMGR Messages

SYSMGR Messages This section contains system manager messages.

SYSMGR-3 Error Message %SYSMGR-3-ABNORMTERM: [chars]:[dec] (jid [dec]) abnormally terminated, [chars] Explanation A process was abnormally terminated. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SYSMGR-3-ERROR: [chars]:[dec] (jid [dec]) [chars] ([chars]) Explanation The system manager server has encountered an error condition. Recommended Action Copy the message exactly as it appears on the console or in the system log.


SYSMGR-6 Error Message %SYSMGR-6-ERROR_EOK: [chars]:[dec] (jid [dec]) [chars] Explanation The system manager server has encountered an error condition. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1644

SYSMGR_PLATFORM Messages


Error Message %SYSMGR-6-RESTART: Restarting process [chars] by [chars] Explanation A process was restarted through the CLI. Recommended Action This is an informational message only. No action is required.

SYSMGR_PLATFORM Messages This section contains Cisco Catalyst 6000 system manager process messages.

SYSMGR_PLATFORM-5 Error Message %SYSMGR_PLATFORM-5-WAIT_RP: Waiting RP to complete crashinfo and core file collection Explanation Sysmgr.proc process is waiting for the RP to signal the end of crashinfo or core file

collection. Recommended Action This is an informational message only. No action is required.

SYSTEM_BUS_ASIC Messages This section contains System Bus Translator ASIC messages.

SYSTEM_BUS_ASIC-3 Error Message %SYSTEM_BUS_ASIC-3-INTR_FATAL: SYSTEM BUS ASIC [dec]: recoverable interrupt [chars] Explanation The System Bus Translator ASIC detected an unexpected interrupt condition. This message indicates a hardware failure or malfunction. The system will reload to fix the problem. Recommended Action If this message recurs, copy the message exactly as it appears on the console



1645

SYSTEM_BUS_ASIC Messages


Error Message %SYSTEM_BUS_ASIC-3-INTR_RECOVERY: SYSTEM BUS ASIC [dec]: recoverable interrupt [chars] Explanation The System Bus Translator ASIC detected an unexpected interrupt condition. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %SYSTEM_BUS_ASIC-3-INTR_RESET: SYSTEM BUS ASIC [dec]: was reset Explanation The System Bus Translator ASIC was reset as part of the system recovery sequence. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %SYSTEM_BUS_ASIC-3-INTR_STATS_RECOVERY: SYSTEM BUS ASIC [dec]: Recoverable Interrupt warning [chars] Explanation The System Bus Translator ASIC detected an unexpected condition in the statistics

collection module. Recommended Action If this message recurs, copy the message exactly as it appears on the console



1646

SYSTEM_BUS_ASIC Messages

Error Message %SYSTEM_BUS_ASIC-3-INTR_WARN: SYSTEM BUS ASIC [dec]: Non-fatal Interrupt warning [chars] Explanation The System Bus Translator ASIC detected an unexpected nonfatal condition. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %SYSTEM_BUS_ASIC-3-INTR_WARN_TYPE2: SYSTEM BUS ASIC [dec]: Non-fatal interrupt Warning [chars] error code [dec] Explanation The System Bus Translator ASIC detected an unexpected nonfatal condition. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %SYSTEM_BUS_ASIC-3-KUMA_INTR_THROTTLED: SYSTEM BUS ASIC %d: Kuma interrupts throttled Explanation The system bus translator ASIC detected too many interrupts. To avoid performance degradation, the system has temporarily masked interrupts. Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


1647

SYSTEM_CONTROLLER Messages

Error Message %SYSTEM_BUS_ASIC-3-KUMA_INTR_UNTHROTTLED: SYSTEM BUS ASIC %d: Kuma interrupts unthrottled Explanation The system has unmasked the interrupts that were masked temporarily. Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

SYSTEM_CONTROLLER Messages This section contains system controller messages.

SYSTEM_CONTROLLER-3 Error Message %SYSTEM_CONTROLLER-3-COR_MEM_ERR: Correctable DRAM memory error. Count [dec], log [hex] Explanation A transient DRAM memory error was detected and corrected. Recommended Action If the error message appears infrequently, no action is required. If the message recurs, reseat the SDRAM SIMM on the supervisor engine. If errors persist, replace the SIMM. If the errors continue after the SIMM is replaced, the supervisor engine may need to be replaced.

Error Message %SYSTEM_CONTROLLER-3-ERROR: Error condition detected: [chars] Explanation The most common errors from the Mistral ASIC on the MSFC are

TM_DATA_PARITY_ERROR, SYSDRAM_PARITY_ERROR, SYSAD_PARITY_ERROR, and TM_NPP_PARITY_ERROR. Possible causes of these parity errors are random static discharge or other external factors. Recommended Action If the error message appears only once (or rarely), monitor the system log to

determine whether the error message was an isolated incident. If the message recurs, check the environmental conditions for problems such as power brownouts, static discharges, or strong EMI fields. If these environmental conditions are within normal ranges and the error continues to appear, the supervisor engine may need to be replaced.


1648

SYSTEM_CONTROLLER Messages

Error Message %SYSTEM_CONTROLLER-3-EXCESSIVE_RESET: System Controller is getting reset so frequently Explanation The MISTRAL ASIC is being reset frequently. The usual cause is an improperly seated

module or another hardware condition. Recommended Action Power down and reseat the module. If the problem persists, copy the message


Error Message %SYSTEM_CONTROLLER-3-INVALID_EARL_HANDLER: EARL interrupt handler is not valid Explanation The EARL interrupt handler is not valid. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %SYSTEM_CONTROLLER-3-MISTRAL_RESET: System Controller is reset:Normal Operation continues Explanation The system controller is being reset. Operation will continue, but the message rate will

be limited. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1649

TAC Messages

TAC Messages This section contains TACACS system messages.

Error Message %TAC-3-SERVCONF: Server config failure: [chars] Explanation The server configuration failed. Recommended Action Please configure the server properly.

Error Message %TAC-3-SERVINT: [chars] Explanation This is an internal software error. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %TAC-3-SERVNO: Server [chars] is not configured Explanation The server is not configured. Recommended Action Please configure a server before un-configuring it.

Error Message %TAC-4-SERVREFNAME: Warning: Server [chars] is still referenced by server group. Explanation The server being removed is still referenced by a server group. Recommended Action Please dereference the server from the server group as soon as possible. Recommended Action

Error Message %TAC-6-SERVDEP: tacacs-server host CLI will be deprecated soon. Please move to tacacs server CLI Explanation Migration from tacacs-server host CLI to tacacs server CLI. Recommended Action Please try to use the new CLI.


1650

TAR_FS Messages

TAR_FS Messages This section contains tar file system messages.

TAR_FS-3 Error Message %TAR_FS-3-IMAGE_FILE_INVALID: [chars] file not found in archive Explanation The tar file system could not locate the relevant tar element inside the archive. Recommended Action Check whether the archive is complete and not corrupted, or if it is the wrong format. If the problem can be recreated with debug ifs file turned on, you can more quickly identify the problem. Save the output of the archive tar /table archive-name command if it is a pure tar archive, or the show image contents file archive-name command if the archive is a system image. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

TCAM_MGR Messages This section contains TCAM manager messages.

TCAM_MGR-3 Error Message %TCAM_MGR-3-BAD_FIRST_DYN_REGION: [dec] Explanation A TCAM error was detected. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1651

TCAM_MGR Messages

Error Message %TCAM_MGR-3-BAD_LAST_DYN_REGION: [dec] Explanation A TCAM error was detected. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %TCAM_MGR-3-INTERNAL_ERROR: [chars], [chars], [dec] Explanation A TCAM error was detected. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %TCAM_MGR-3-INVALID_OPERATION: [chars], [dec] Explanation A TCAM error was detected. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1652

TCAM_MGR Messages

Error Message %TCAM_MGR-3-INVALID_REG_TYPE: [chars], [dec] Explanation A TCAM error was detected. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %TCAM_MGR-3-MALLOC_FAIL: [chars], [chars] Explanation A TCAM error was detected. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %TCAM_MGR-3-OP_FAIL: [chars] failed for application [chars], application entry [hex] with [chars] error Explanation A TCAM error was detected. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1653

TCAMMGR Messages

Error Message %TCAM_MGR-3-UNUSUAL_BUG_WARNING: [chars] mbu [hex] free_array_index [dec] region_id [dec] Explanation A TCAM error was detected. Recommended Action Copy the message exactly as it appears on the console or in the system log.


TCAMMGR Messages This section contains TCAM manager messages.

TCAMMGR-3 Error Message %TCAMMGR-3-GROW_ERROR: cam region [dec] can not grow Explanation This CAM region is configured as a static region with a fixed number of entries, and a

call was requested to add more CAM entries to the specified region. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %TCAMMGR-3-HANDLE_ERROR: cam handle [hex] is invalid Explanation The CAM handle that was used by the caller is invalid. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1654

TCAMMGR Messages


Error Message %TCAMMGR-3-INDEX_ERROR: cam value/mask index [dec] is invalid Explanation The CAM index that was used by the caller is invalid. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %TCAMMGR-3-MOVE_ERROR: cam entry move from index [int] to index [int] failed Explanation A move operation for a CAM entry from one index to another has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %TCAMMGR-3-REGION_ERROR: cam region [dec] is invalid Explanation The CAM region is invalid. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1655

TCATM Messages

Error Message %TCAMMGR-3-REGMASK_ERROR: invalid cam region [dec] mask [dec] pair Explanation Only a predetermined set of masks are allowed in a region. The caller requested to

install an entry in the specified region that contained an invalid mask for that region. Recommended Action Copy the message exactly as it appears on the console or in the system log.


TCATM Messages This section contains ATM tag distribution and control messages.

TCATM-3 Error Message %TCATM-3-INTERNAL: [chars] Explanation An operation that is required for proper operation of the TCATM has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


TCP Messages This section contains Transmission Control Protocol (TCP) messages.


1656

TCP Messages

TCP-2 Error Message %TCP-2-INVALIDTCB: Invalid TCB pointer: [hex] Explanation An invalid TCB is used. Recommended Action If this message recurs, copy it down exactly as it appears and contact your

technical support representative for assistance.

TCP-3 Error Message %TCP-3-BADMSS: Incorrect mss [dec] observed Explanation The maximum segment size is incorrect. TCP cannot guarantee further reliable

operation for this connection. Recommended Action Check the MTU for the interface and increase it as required. If, after adjusting the MTU, this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %TCP-3-CHKPT_INIT: TCP failed to initialize checkpoint storage: %s Explanation The TCP process failed to initialize checkpoint storage for ports. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1657

TCP Messages

Error Message %TCP-3-ERR_DUMP_DEB: netdump_print_context failed, %d Explanation Netdump print failed while dumping a process debug context. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %TCP-3-ERR_MD5_INVALID: MD5 validation failed, incoming packet src: %s:%d, dst: %s:%d Explanation MD5 validation failed on an incoming packet. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %TCP-3-ERR_MD5_WRITE: MD5 option write failed, dst: %s:%d Explanation The TCP process failed to write an MD5 option. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1658

TCP Messages

Error Message %TCP-3-ERR_NETWORK_INIT: TCP failed to connect with network layer: %s, error %s Explanation TCP initialization with the network layer failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %TCP-3-ERR_OUT_BUFF: ran out of buffer with %ld bytes %s to send Explanation TCP ran out of buffer space while copying segment data. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %TCP-3-ERR_PAK_FSV: %s Explanation An FSV operation failed on the packet. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1659

TCP Messages

Error Message %TCP-3-ERR_PAK_DISCARD: %s: %s,

->

Explanation Packet information from a discarded packet is displayed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %TCP-3-ERR_PCB_VECTOR: ip_pcb_get_family_vector failed, %d Explanation The TCP process failed to get a pointer to the PCB family vector. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %TCP-3-ERR_SET_APP_LEN: %s: set_Application_length failed: %s Explanation The TCP process failed to set an application buffer for the segment. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %TCP-3-FORKFAIL: Failed to start a process to negotiate options. Explanation The system failed to create a process to handle requests from a client. This condition

could be caused by insufficient memory. Recommended Action Reduce other system activity to ease memory demands.


1660

TCP Messages

Error Message %TCP-3-SOCKET_RESMGR_ATTACH: Failed to setup the transport as a resource manager: %s Explanation The TCP process failed to advertise itself to the system as a resource manager. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %TCP-3-TRACE_ERR: %s error (%d). Premature trace termination for control block 0x%p Explanation A trace terminated prematurely. Recommended Action Copy the message exactly as it appears on the console or in the system log.


TCP-4 Error Message %TCP-4-ERR_PAK_CLIENT: %s, res %d Explanation A packet client operation failed in TCP. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1661

TCP Messages

Error Message %TCP-4-WARNING_DEBUG: %s Explanation TCP failed to open the console device for debug. Recommended Action Copy the message exactly as it appears on the console or in the system log.


TCP-6 Error Message %TCP-6-INFO_RCV_SIG: recieved signal %d Explanation The TCP process received a signal. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %TCP-6-MD5NOSPACE: Insufficient space for MD5 option Explanation There was insufficient space for the MD5 option. This condition should not occur,

because the MD5 option, when requested, is required and is given preference over other TCP options. Recommended Action Unconfigure other TCP options, if any, in an attempt to create space for the

MD5 option. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


1662

TENGIGE_LC Messages

TCP-7 Error Message %TCP-7-ERR_TCP_INIT: TCP failed to initialize: %s, error %s Explanation TCP initialization failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


TENGIGE_LC Messages This section contains 10-Gigabit Ethernet line card messages.

TENGIGE_LC-3 Error Message %TENGIGE_LC-3-LASER_TEMP_ERR: Laser Temperature Alarm : [dec]/[dec] Explanation A laser temperature alarm condition has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %TENGIGE_LC-3-MIB_TENGIGE_LASER_FAILURE: Laser failure detected during soft-start procedures : [chars] Explanation A laser failure has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1663

TENGIGE_LC Messages


Error Message %TENGIGE_LC-3-MIB_TENGIGE_LOSYNC_ALM: Loss of Sync ; [chars] Explanation The Gigabit Ethernet function lost its synchronization. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %TENGIGE_LC-3-TENGIGE_LOSYNC_ALM: [chars] side Loss of Sync lock: [chars] Explanation The Gigabit Ethernet function lost its synchronization. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %TENGIGE_LC-3-TENGIGE_LOSYNC_ALM_CLR: CLEARED : [chars] Loss of Sync lock: [chars] Explanation The Gigabit Ethernet function lost its synchronization. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1664

TENGIGE_LC Messages


TENGIGE_LC-6 Error Message %TENGIGE_LC-6-LASER_DISABLED: Laser disabled as per user configuration [[dec]/[dec]] Explanation The laser has been disabled as specified by the user configuration. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %TENGIGE_LC-6-LASER_DISABLED_BY_HW: Laser disabled as per laser safety configuration [[dec]/[dec]] Explanation The laser has been disabled as specified by the safety configuration. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %TENGIGE_LC-6-MIB_TENGIGE_TRUNK_LOSYNC_PALM: Trunk side Loss of Sync Prealarm; [chars] Explanation The trunk lost its synchronization while it was receiving data. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1665

TID_HA Messages


Error Message %TENGIGE_LC-6-TENGIGE_TRUNK_RX_LOSYNC_PALM: Trunk side Loss of Sync lock Prealarm: [chars] Explanation The trunk lost its synchronization while it was receiving data. Recommended Action Copy the message exactly as it appears on the console or in the system log.


TID_HA Messages This section contains table ID high availability (HA) messages.

TID_HA-3 Error Message %TID_HA-3-ISSUERR: [chars] [chars] Explanation An error occurred during an in-service software upgrade (ISSU) versioning operation. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1666

TID_HA Messages

Error Message %TID_HA-3-ISSUERRCF: [chars] checkpoint code [dec] Explanation An error occurred during an ISSU versioning operation due to an error in the checkpoint

facility. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %TID_HA-3-RXFAIL1: [chars] Explanation An error occurred while receiving a table ID synchronization message. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %TID_HA-3-RXFAIL2: [chars], type [dec], version [dec], flags [hex] Explanation An error occurred while receiving a table ID synchronization message. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %TID_HA-3-RXFAIL3: [chars] type [dec], version [dec],flags [hex], application [dec], action [dec], tableid [dec], name [chars] Explanation An error occurred while receiving a table ID synchronization message. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1667

TID_HA Messages


Error Message %TID_HA-3-SYNCFAIL: [chars] Explanation Internal table ID information may have not been synchronized to the standby unit

correctly. Recommended Action Reload the standby unit. If the error condition persists, copy the message


Error Message %TID_HA-3-SYNCFAILCF: [chars] checkpoint code [dec] Explanation Internal table ID information may have not been synchronized to the standby unit

correctly due to an error in the checkpoint facility. Recommended Action Reload the standby unit. If the error condition persists, copy the message


Error Message %TID_HA-3-TXFAIL: [chars], name [chars] tableid [dec] action [dec] Explanation An error occurred while sending the internal table ID information. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1668

TIDP Messages


Error Message %TID_HA-3-TXFAILCF: [chars], name [chars], tableid [dec], action [dec], checkpoint code [dec] Explanation Failed to send internal table ID information due to an error in the checkpoint facility. Recommended Action Copy the message exactly as it appears on the console or in the system log.


TIDP Messages This section contains Threat Information Distribution Protocol (TIDP) messages.

TIDP-3 Error Message %TIDP-3-RESTART: Restarting TIDP due to unexpected error Explanation An unexpected error has occurred in the Threat Information Distribution Protocol

(TIDP) process. TIDP has been restarted in an attempt to restore operation. Recommended Action Enter the debug tidp errors and debug tidp events commands to gather data that may help identify the nature of the error. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


1669

TIDP Messages

TIDP-4 Error Message %TIDP-4-AUTHFAIL: Message from %s, %i failed authentication Explanation The signature of a received message failed authentication. The message has been

dropped. Recommended Action Check the local and peer configurations to make sure that compatible authentication key sets are used.

Error Message %TIDP-4-REPLAYMSG: Unexpected message from %s, %i received Explanation A message with a sequence number outside of the acceptable range was received and

has been dropped. The message might be a replay message and might indicate an intrusion attack. Recommended Action Verify that the peer’s hardware and configuration has not been altered. Verify

connectivity to the peer.

Error Message %TIDP-4-SRCCHANGED: Address changed was being used by TIDP Explanation An interface IP address was changed, but the former address was being used as the

Threat Information Distribution Protocol (TIDP) source address. TIDP cannot operate properly if the address is not local. Recommended Action Restore the original IP address to the original interface or to a new interface, or change the TIDP source address.

TIDP-5 Error Message %TIDP-5-BADMSG: Message from %s, %i failed validation Explanation A message has failed basic header and range check validation. The message has been

dropped. Recommended Action Check the local and peer configurations to make sure that compatible versions of TIDP and encryption keys are used.

Error Message %TIDP-5-OVERSIZE: Oversized message received from %s, %i Explanation A larger than expected message was received and has been dropped. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1670

TINY_FRAG_POLICER Messages


Error Message %TIDP-5-PEERSRCCHANGED: TIDP source address of the connection to peer %i is changed Explanation The Threat Information Distribution Protocol (TIDP) source address changed. The

change might be caused by DHCP renewal or by the user manually changing the IP address at the interface. Recommended Action No action is required.

Error Message %TIDP-5-REGFAIL: Failed to register to peer %s, %i, group %u Explanation Attempts to register with the specified peer have failed. Another attempt will be made

after the configured maximum retry interval. Recommended Action Verify connectivity to the peer and make sure that the configuration between

peers is compatible.

TIDP-6 Error Message %TIDP-6-DUPLICATE: Duplicate message from %s, %i received Explanation A message was received that had the same sequence number as a previously received

message. The message has been dropped. Recommended Action No action is required.

TINY_FRAG_POLICER Messages This section contains tiny fragment policer messages.

TINY_FRAG_POLICER-6 Error Message %TINY_FRAG_POLICER-6-AGGREGATE_THRESHOLD_EXCEEDED: [dec] bps: it is recommended to reduce the hi threshold value Explanation The fragment offset == 1 (fo1) packets aggregate threshold has exceeded the acceptable

value. Recommended Action Reduce the interface high-threshold values.


1671

TMS Messages

Error Message %TINY_FRAG_POLICER-6-HI_THRESHOLD_EXCEEDED: [dec] bps: installing rate limiter for vlan [int] on interface [chars] Explanation The fragment offset == 1 (fo1) packets high threshold has exceeded the acceptable

value. Recommended Action This is an informational message only. No action is required.

Error Message %TINY_FRAG_POLICER-6-RATELIMITER_FAILED: could not [chars]install rate limiter for vlan [int] interface [chars] Explanation The fragment offset == 1 (fo1) rate installer failed due to resource issues. Recommended Action This is an informational message only. No action is required.

Error Message %TINY_FRAG_POLICER-6-RATELIMITER_REMOVED: removing rate limiter for vlan [int] from interface [chars] Explanation The fragment offset == 1 (fo1) packets dropped below the low threshold. Recommended Action This is an informational message only. No action is required.

TMS Messages This section contains Threat Management Service (TMS) messages.

TMS-2 Error Message %TMS-2-PROCESS_ERR: Router could not create a TMS controller process Explanation The router was unable to create a TIDP-based Mitigation Services (TMS) controller

process. Recommended Action Reload the device.

TMS-4 Error Message %TMS-4-BAD_PKT: %s| Group=%u|%s Type=%d| Flags=%d Explanation The controller has received an invalid or unexpected packet from the consumer. Recommended Action Check the specified consumer for the TIDP-based Mitigation Services (TMS)

protocol operation.


1672

TMS Messages

Error Message %TMS-4-MSG_ERR: Unknown message event reveived Explanation The TIDP-based Mitigation Services (TMS) process received an unknown message

event. Recommended Action If this message recurs, reload the device.

Error Message %TMS-4-PROCESS_STOP: PROCESS=%s| ACTION=%s. Explanation The specified process is stopped. Recommended Action Reload the device.

Error Message %TMS-4-UNKN_EVENT_ERR: UNKNOWN Event for Event=%d. Explanation The TMS controller process received an unknown event. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %TMS-4-UNKN_PROCESS_ERR: An unknown operational error occurred. Explanation The TMS process cannot operate due to an internal system error. Recommended Action Reload the device.

Error Message %TMS-4-UNKN_TIMER_ERR: An unknown Timer operational error occurred Explanation The TMS process cannot operate due to an internal system error. Recommended Action Reload the device.

TMS-6 Error Message %TMS-6-CONSUMER_CLEAR: %s Explanation The consumer has cleared all statistics. Recommended Action No action is required.


1673

TMS Messages

Error Message %TMS-6-CONSUMER_STATE: %s Explanation This message indicates whether the TIDP-based Mitigation Services (TMS) consumer

is configured or unconfigured. Recommended Action No action is required.

Error Message %TMS-6-DEVICE: %s| Group=%u|%s Status=%s Explanation This message indicates whether a consumer is registered or unregistered on the

specified group. Recommended Action No action is required.

Error Message %TMS-6-GROUP: %s| Group=%u|%s Status=%s Explanation This message indicates whether a group is configured or unconfigured on the specified

host. Recommended Action No action is required.

Error Message %TMS-6-RESET: %s| Group=%u| %s Action=%s| Start TID=%d| End TID=%d Explanation The controller sent a reset request for an action to a specific consumer or a group. Recommended Action No action is required.

Error Message %TMS-6-STATUS: %s| Group=%u|%s Start TID=%d| End TID=%d Explanation The controller sent a status request to a specific consumer or a group. Recommended Action No action is required.

Error Message %TMS-6-THREAT: %s| Group=%u|%s TID=%d Explanation The controller sent a threat message to a specific consumer or a group. Recommended Action No action is required.

Error Message %TMS-6-THREATSTATUS: %s| Group=%u|%s Threat=%d| Version=%d| Action=%s Explanation This message displays the status of a threat on a consumer in the specified group. Recommended Action No action is required.


1674

TN Messages

Error Message

TN Messages This section contains Telnet messages.

TN-2 Error Message %TN-2-BADCONN: Bad conn pointer [hex] closing all connections on terminal line [dec] Explanation An internal software error has occurred. Recommended Action If this message recurs, copy the message exactly as it appears on the console


TOPN_COUNTERS Messages This section contains switch TopN report counters messages.

TOPN_COUNTERS-3 Error Message %TOPN_COUNTERS-3-MGMT: %s transmit receive byte count is excessive, 1st poll %llu, 2nd poll %llu Explanation The traffic counter value on the interface is higher than expected. The module might be

reporting an erroneous number. Recommended Action Verify the traffic flow on the interface. If the flow does not match the TOPN report, contact your Cisco technical support representative.


1675

TOPN_COUNTERS Messages

TOPN_COUNTERS-4 Error Message %TOPN_COUNTERS-4-MEM_UNAVAIL: Memory was not available for handling the TopN request Explanation The system cannot handle the TopN request because of lack of memory. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

TOPN_COUNTERS-5 Error Message %TOPN_COUNTERS-5-AVAILABLE: TopN report [dec] is available Explanation The specified report is ready and can be viewed by the users. Recommended Action This is an informational message only. No action is required.

Error Message %TOPN_COUNTERS-5-DELETED: TopN report [dec] deleted by [chars] Explanation The specified report has been deleted by the specified user. Recommended Action This is an informational message only. No action is required.

Error Message %TOPN_COUNTERS-5-KILLED: TopN report [dec] task killed by [chars] [chars] Explanation The system was in the process of generating the specified report, but the specified user

terminated the report before its completion. Recommended Action This is an informational message only. No action is required.

Error Message %TOPN_COUNTERS-5-NOPORTS: No interfaces in the system match the interface type for the generation of the topN report [dec] Explanation There were no interfaces in the system that matched the interface type selected in the specified report. Recommended Action This is an informational message only. No action is required.

Error Message %TOPN_COUNTERS-5-STARTED: TopN collection for report [dec] started by [chars] Explanation The TopN report that was requested by the specified user starts with the specified report

number. Recommended Action This is an informational message only. No action is required.


1676

TPLUS Messages

TPLUS Messages This section contains Terminal Access Controller Access Control System (TACACS) protocol messages.

TPLUS-3 Error Message %TPLUS-3-FORKFAIL: Failed to fork process for [chars]. Explanation A process fork failed, probably due to insufficient memory. Recommended Action If this message recurs, copy the message exactly as it appears on the console


TRACKING Messages This section contains object tracking (TRACKING) messages.

TRACKING-5 Error Message %TRACKING-5-STATE: %d %s %s %s %s-%s Explanation A tracked object has changed its state. Recommended Action No action is required.


1677

TRAFFIC_UTIL Messages

TRAFFIC_UTIL Messages This section contains traffic utilization (TRAFFIC_UTIL) messages.

TRAFFIC_UTIL-4 Error Message %TRAFFIC_UTIL-4-MONITOR_BACKPLANE_BELOW_THR: Backplane traffic utilization is %d%%, below threshold(%d%%) within %d second interval Explanation The backplane traffic utilization is below the utilization threshold. Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %TRAFFIC_UTIL-4-MONITOR_BACKPLANE_REACH_THR: Backplane traffic utilization is %d%%, reached threshold(%d%%) within %d second interval Explanation The backplane traffic utilization has reached a utilization threshold. Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %TRAFFIC_UTIL-4-MONITOR_FABRIC_EG_BELOW_THR: Module %d, Channel %d egress traffic utilization is %d%%, below or equal threshold(%d%%) within %d second interval Explanation The fabric channel egress traffic utilization is below a utilization threshold. Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,


1678

TRAFFIC_UTIL Messages


Error Message %TRAFFIC_UTIL-4-MONITOR_FABRIC_EG_REACH_THR: Module %d, Channel %d egress traffic utilization is %d%%, reached threshold(%d%%) within %d second interval Explanation The fabric channel egress traffic utilization has reached a utilization threshold. Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %TRAFFIC_UTIL-4-MONITOR_FABRIC_IG_BELOW_THR: Module %d, Channel %d ingress traffic utilization is %d%%, below or equal threshold(%d%%) within %d second interval Explanation The fabric channel ingress traffic utilization is below a utilization threshold. Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %TRAFFIC_UTIL-4-MONITOR_FABRIC_IG_REACH_THR: Module %d, Channel %d ingress traffic utilization is %d%%, reached threshold(%d%%) within %d second interval Explanation The fabric channel ingress traffic utilization has reached a utilization threshold. Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,


1679

TRANGE Messages


TRANGE Messages This section contains time-range (TRANGE) error messages.

TRANGE-2 Error Message %TRANGE-2-NOMEMORY: Alloc fail for time-range config buffer. Disabling distributed mode on lc Explanation The system was unable to allocate a buffer to send time-range configuration information to the line cards. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show chunks commands and your pertinent troubleshooting logs. show chunks

Error Message %TRANGE-2-WRONGREQUEST: Invalid request to allocate chunk of size %d Explanation A request was made to allocate a time-range chunk greater than the maximum allowed

size (TRANGE_LARGE_CHUNK_SZ). Recommended Action Copy the message exactly as it appears on the console or in the system log.



1680

TRANSCEIVER Messages

Error Message %TRANGE-2-WRONGSIZE: Incorrect length trange ipc xdr of len=%d received Explanation The RP sent a time-range configuration message of the wrong size. Recommended Action Copy the message exactly as it appears on the console or in the system log.


TRANSCEIVER Messages This section contains transceiver module messages.

TRANSCEIVER-3 Error Message %TRANSCEIVER-3-ATTACH_FAILURE: Detected for transceiver module in [chars], module disabled Explanation A software device driver attach has failed. This condition could be caused by a software,

firmware, or hardware problem, but a software or firmware problem is more likely. As a result of the error, the module is disabled. Recommended Action Power down and reseat the module. Hardware replacement should not occur on

the first occurrence. Before requesting hardware replacement, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


1681


Error Message %TRANSCEIVER-3-CHECKSUM_ERROR: Detected in the transceiver module in [chars], module disabled Explanation A checksum error was detected when reading the ID PROM of a transceiver module for

the specified interface. As a result of the error, the module is disabled. Recommended Action Power down and reseat the module. If the problem persists, copy the message


Error Message %TRANSCEIVER-3-INIT_FAILURE: Detected for transceiver module in [chars], module disabled Explanation An initialization failure occurred for the transceiver module for the specified interface.

This condition could be caused by a software, firmware, or hardware problem. As a result of the error, the module is disabled. Recommended Action Power down and reseat the module. Hardware replacement should not occur on


Error Message %TRANSCEIVER-3-INTERNAL_ERROR: [chars] Explanation The transceiver subsystem encountered an internal software error. The message contains

text that can be used to help identify the nature of the problem. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1682


Error Message %TRANSCEIVER-3-NOT_COMPATIBLE: Detected for transceiver module in [chars], module disabled Explanation The transceiver module for the specified interface is not compatible with the interface.

As a result of the error, the module is disabled. Recommended Action Replace the module with a compatible transceiver. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %TRANSCEIVER-3-NOT_IDENTIFIED: Detected for transceiver module in [chars], module disabled Explanation The transceiver module for the specified interface could not be identified and may not

be compatible with the interface. As a result of the error, the module is disabled. Recommended Action Replace the module with a compatible transceiver. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %TRANSCEIVER-3-NOT_SUPPORTED: Detected for transceiver module in [chars], module disabled Explanation The transceiver module for the specified interface is not a Cisco supported module. As

a result of the error, the module is disabled. Recommended Action Replace the module with a Cisco supported transceiver. If the problem persists,

copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


1683


Error Message %TRANSCEIVER-3-OPER_ENABLE_FAILURE: Detected for transceiver module in [chars], module disabled Explanation Failed to enable the transceiver module for the specified interface. This condition could

be caused by a software, firmware, or hardware problem. As a result of the error, the module is disabled. Recommended Action Power down and reseat the module. Hardware replacement should not occur on


Error Message %TRANSCEIVER-3-RPC_FAILED: Application error rc = [dec]: Explanation The system failed to retrieve the information required to execute the command. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Enter the show version command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %TRANSCEIVER-3-RPC_LC_PROC_INIT_FAIL: Transceiver RPC init failure: [chars] Explanation The system failed to create the resources required to process user interface commands

for transceivers. The error is not fatal but some show commands could fail. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1684


Error Message %TRANSCEIVER-3-RPC_PROCESSING_ERROR: Transceiver RPC error: [chars] Explanation A nonfatal error occurred during the processing of an RPC message. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %TRANSCEIVER-3-SM_CREATION_FAILURE: Transceiver OIR State Machine creation failed for [chars], module disabled. Explanation A state machine could not be created for the transceiver OIR operation. If a memory

allocation message was also received with this message, this condition indicates insufficient system memory. Other possible causes include an invalid subblock pointer. Recommended Action If it is insufficient system memory, reduce other system activity to ease

memory demands. If conditions warrant, upgrade to a larger memory configuration. Otherwise, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

TRANSCEIVER-6 Error Message %TRANSCEIVER-6-INSERTED: transceiver module inserted in [chars] Explanation The online insertion and removal (OIR) facility detected a newly inserted transceiver module for the interface specified in the error message. Recommended Action This is an informational message only. No action is required.

Error Message %TRANSCEIVER-6-REMOVED: Transceiver module removed from [chars] Explanation The online insertion and removal (OIR) facility detected the removal of a transceiver module from the specified interface. Recommended Action This is an informational message only. No action is required.


1685

TRIFECTA Messages

TRIFECTA Messages This section contains Trifecta service module messages.

Error Message %TRIFECTA-6-X86_FPGAVER_MISMATCH: Module [dec]: [chars] Explanation Trifecta X86 FPGA version mismatch. Recommended Action No action is required.

Error Message %TRIFECTA-6-X86ONLINE: Trifecta X86 in slot [dec] is online. Explanation Trifecta X86 has finished booting up and is online. Recommended Action No action is required.

Error Message %TRIFECTA-6-X86_RESTART_REASON: Module [dec]: [chars] Explanation Trifecta X86 restart reason. Recommended Action No action is required.

TTFIB_NP_CLIENT Messages This section contains Toaster Tag FIB (TTFIB) NP client messages.

TTFIB_NP_CLIENT-3 Error Message %TTFIB_NP_CLIENT-3-ERROR: [chars] [chars] [chars] Explanation Failed to set or clear port mode flags because the NP returned a failure condition. Recommended Action Reload the Cisco IOS image on the affected card or platform. Copy the



1686

TTFIB_NP_CLIENT Messages

Error Message %TTFIB_NP_CLIENT-3-INFO: [chars] Explanation TTFIB NP client failed to initialize properly, which results in improper operation of the

any transport over MPLS (AToM) feature. Recommended Action Reload the Cisco IOS image on the affected card or platform. Copy the


Error Message %TTFIB_NP_CLIENT-3-NOMEM: [chars] Explanation TTFIB NP client failed to initialize properly, which results in improper operation of the

any transport over MPLS (AToM) feature. Recommended Action This message may indicate that more memory must be installed on the affected

card or platform in order to service all the features and related entities enabled via the configuration. Reload the Cisco IOS image on the affected card or platform. If the error persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

TTFIB_NP_CLIENT-4 Error Message %TTFIB_NP_CLIENT-4-HDLC: [chars] Explanation Improper usage of SIP-400 for the HDLC over MPLS (HDLCoMPLS) feature. Recommended Action This is an informational message only. No action is required.

Error Message %TTFIB_NP_CLIENT-4-PPP: [chars] Explanation Improper usage of SIP-400 for the PPP over MPLS (PPPoMPLS) feature. Recommended Action This is an informational message only. No action is required.


1687

TUN Messages

Error Message %TTFIB_NP_CLIENT-4-VPLS: [chars] Explanation Improper usage of SIP-400 for the Virtual Private LAN Service (VPLS) feature. Recommended Action This is an informational message only. No action is required.

Error Message %TTFIB_NP_CLIENT-4-WARN: [chars] [dec] [chars] Explanation A TTFIB entry could not be added because the entry passed is invalid. Recommended Action Reload the Cisco IOS image on the affected card or platform. Copy the


TUN Messages This section contains tunnel messages.

TUN-3 Error Message %TUN-3-API_ARGS: unexpected arguments: [chars], [chars] Explanation A public tunnel component API was called with arguments outside the expected

boundaries. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %TUN-3-ENDPOINT_ERROR: [chars] [chars] Explanation An internal software error occurred during manipulating the tunnel endpoint database. Recommended Action No action is required.


1688

TUN Messages

Error Message %TUN-3-ENDPOINT_STORE: Operation [chars] failed for [chars] Explanation Manipulation of the tunnel endpoint store has failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %TUN-3-ILLEGAL_ARGS: Illegal arguments - [chars] Explanation An internal software error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %TUN-3-MTUCONFIGEXCEEDSL2MTU_IPV4: [chars] IPv4 MTU configured [int] exceeds tunnel maximum MTU [int] Explanation An IPv4 MTU value is configured on the tunnel interface and this value exceeds the

tunnel’s maximum MTU. This message is typically observed when the tunnel header size changes or when the MTU of the underlying exit interface changes. As a result of either, the tunnel maximum MTU can change. This message can also be observed when using an IPv6 tunnel to carry IPv4 since IPv4 MTU config in this case allows for a value to be configured that is greater than the tunnel’s maximum MTU. As a result of any of these conditions, packets may be dropped. Recommended Action If a specific IPv4 MTU value is not required, it is recommended that you leave the value at the default by typing no ip mtu on the tunnel interface. If a specific value is required, it is recommended that you check the interface MTU value from the show interface tunnel command and adjust ip mtu on the tunnel interface to be lower than or equal to this.

Error Message %TUN-3-MTUCONFIGEXCEEDSL2MTU_IPV6: [chars] IPv6 MTU configured [int] exceeds tunnel maximum MTU [int] Explanation An IPv6 MTU value is configured on the tunnel interface and this value exceeds the

tunnel’s maximum MTU. This message is typically observed when the tunnel header size changes or when the MTU of the underlying exit interface changes. As a result of either, the tunnel maximum


1689

TUN Messages

MTU can change. This message can also be observed when using an IPv6 tunnel to carry IPv6 since IPv6 MTU config in this case allows for a value to be configured that is greater than the tunnel’s maximum MTU. As a result of any of these conditions, packets may be dropped. Recommended Action If a specific IPv6 MTU value is not required, it is recommended that you leave the value at the default by typing no ipv6 mtu on the tunnel interface. If a specific value is required, it is recommended that you check the interface MTU value from the show interface tunnel command and adjust ipv6 mtu on the tunnel interface to be lower than or equal to this.

TUN-4 Error Message %TUN-4-MTUCONFIGEXCEEDSTRMTU_IPV4: [chars] IPv4 MTU configured [int] exceeds tunnel transport MTU [int] Explanation An IPv4 MTU value has been configured on the tunnel interface and this value exceeds

the tunnel’s transport (default) MTU. As a result, fragmentation of the transport packet may occur before this goes out of the underlying exit interface. Recommended Action If a specific IPv4 MTU value is not required, it is recommended that you leave the value at the default by typing no ip mtu on the tunnel interface. If a specific value is required, it is recommended that you check the tunnel transport MTU value from the show interface tunnel command and adjust ip mtu on the tunnel interface to be lower than or equal to this.

Error Message %TUN-4-MTUCONFIGEXCEEDSTRMTU_IPV6: [chars] IPv6 MTU configured [int] exceeds tunnel transport MTU [int] Explanation An IPv6 MTU value has been configured on the tunnel interface and this value exceeds

the tunnel’s transport (default) MTU. As a result, fragmentation of the transport packet may occur before this goes out of the underlying exit interface. Recommended Action If a specific IPv6 MTU value is not required, it is recommended that you leave the value at the default by typing no ipv6 mtu on the tunnel interface. If a specific value is required, it is recommended that you check the tunnel transport MTU value from the show interface tunnel command and adjust ipv6 mtu on the tunnel interface to be lower than or equal to this.

Error Message %TUN-4-MTUCONFIGLESSTHAN_MINIPV4MTU: [chars] IPv4 MTU [int] is lesser than the minimum IP MTU [int], fragmentation may occur Explanation The IPv4 MTU value calculated on the tunnel interface is less than the minimum IP MTU. The MTU of the underlying exit interface of the tunnel is too small. As a result, fragmentation of the transport packet may occur before this goes out of the underlying exit interface. Recommended Action If a specific MTU value is not required for the exit interface, it is recommended that you leave the value at the default by typing no mtu on the exit interface. If a specific value is required, it is recommended that you check the MTU value from the show interface command for the exit interface and adjust mtu on the tunnel exit to be higher than this.


1690

TUN Messages

Error Message %TUN-4-UDLR_IDB_ERROR: UDLR [chars] - [chars] Explanation An error was encountered on a unidirectional link routing (UDLR) interface. Recommended Action No action is required.

TUN-5 Error Message %TUN-5-HW_IF_INDEX_ILLEGAL: Attempt to create tunnel interface for [chars] with illegal index: [dec] Explanation The creation of a tunnel interface failed due to an invalid index. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %TUN-5-INIT_ERROR: A critical error [chars]occurred during initialization Explanation The creation of a tunnel subsystem failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %TUN-5-RECURDOWN_SRC: [chars] linestate down, recursive source interface, next output [chars] Explanation While the tunnel line state was being evaluated, a source interface was revisited. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1691

TUN Messages


Error Message %TUN-5-TUN_DB_IF: Operation on tunnel interface table failed for [chars] - [chars] Explanation A manipulation of the tunnel interface table failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %TUN-5-TUN_HWIDB_DELETE: Failed to delete hwidb for Tunnel [dec] index [dec] Explanation The deletion of a tunnel interface failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %TUN-5-TUN_HWIDB_LIST_DELETE: Failed to delete [chars] from tunnel hwidb list Explanation The deletion of a tunnel from the hardware IDB list failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1692

TUN Messages


Error Message %TUN-5-TUN_HWIDB_LIST_INSERT: Failed to add [chars] to tunnel hwidb list Explanation The insertion of a tunnel into the hardware IDB list failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %TUN-5-TUN_HWIDB_RECYCLE: Failed to recycle hwidb for Tunnel [dec] index [dec] Explanation The recycling of a tunnel interface failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %TUN-5-TUN_LIST_CREATE: Failed to create tunnel list [chars] Explanation The creation of a tunnel list failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1693

TUN Messages

Error Message %TUN-5-TUN_SWIDB_DELETE: Failed to delete swidb for Tunnel [dec] index [dec] Explanation The deletion of a tunnel interface failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %TUN-5-TUN_SWIDB_RECYCLE: Failed to recycle swidb for Tunnel [dec] index [dec] Explanation The recycling of a tunnel interface failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %TUN-5-TUN_TABLE: Operation [chars] on tunnel table failed for [chars] - [chars] Explanation The manipulation of the tunnel table failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1694

TUNSS Messages

Error Message %TUN-5-TUN_UNIT_LIST_DELETE: Failed to delete entry unit [dec] to tunnel unit list Explanation A deletion from the tunnel unit failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %TUN-5-TUN_UNIT_LIST_INSERT: Failed to add entry unit [dec] to tunnel unit list Explanation The insertion of the tunnel unit failed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


TUNSS Messages This section contains tunnel security messages.

Error Message %TUNSS-6-PROTECTION_BAD_TUN_MODE: Tunnel mode [chars] not supported by tunnel protection. Protection removed. Explanation The chosen tunnel mode is not supported by tunnel protection interfaces. Protection has

been turned off and removed. Recommended Action Unless protection is desired on this interface, no action is required. If

protection is desired, a crypto-map must be used instead.


1695

UAM Messages

Error Message %TUNSS-3-PROTECTION_PROCESS_FAIL : Failed to create tunnel security process Explanation The system failed to start a processes necessary to do tunnel protection. Recommended Action Copy the message exactly as it appears on the console or in the system log.


UAM Messages This section contains Upgrade Analysis Module (UAM) messages.

UAM-3 Error Message %UAM-3-IMPACT_FAMILY: UAM is unable to get the impact of the upgrade on ’%s’ linecards family (SR is ’%s’) Explanation The Upgrade Analysis Module (UAM) is unable to determine the impact of the current

upgrade for the line cards belonging to the specified family. An upgrade operation will probably result in the resetting of all line cards in that family. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %UAM-3-INVALID_CONTEXT: Trying to stop the upgrade, but there is no upgrade currently Explanation An application is trying to stop an upgrade cycle, but there is no upgrade in progress. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1696

UBL Messages


Error Message %UAM-3-INVALID_WB: Trying to set an invalid watched boolean Explanation During runtime, the UAM is trying to release a process using an invalid internal data structure. The command line interface will probably be blocked or the standby supervisor will be unable to boot. Recommended Action Copy the message exactly as it appears on the console or in the system log.


UBL Messages This section contains Universal Boot Loader (UBL) messages.

UBL-2 Error Message %UBL-2-SLAVE_FAIL: Could not download image due to - [chars]. Explanation The standby supervisor engine could not carry out its task of downloading an image

from the active supervisor engine due to the reason mentioned in the error message. This could be due to an internal error or due to an old image running on the active supervisor engine that does not support UBL. Prior error messages might provide more information about the actual problem. Recommended Action Ensure the conditions mentioned in the message are met. If preceding error messages in the log indicate that this is an internal error, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


1697

UDLD Messages

UDLD Messages This section contains UniDirectional Link Detection (UDLD) protocolmessages.

UDLD-3 Error Message %UDLD-3-UDLD_NOKADIS: UDLD unable to create the kadis timer, status [dec] Explanation A failure occurred during creation of the kadis timer from UDLD pseudo preemptive

process. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %UDLD-3-UDLD_NOPREEMP: UDLD unable to create pseudo preemptive process Explanation A failure occurred during creation of the UDLD pseudo preemptive process. Recommended Action Copy the error message exactly as it appears on the console or in the system


UDLD-4 Error Message %UDLD-4-UDLD_PORT_FAILURE: UDLD failure reported per user request, interface [chars], [chars] detected, Explanation An interface failure was reported because UDLD protocol detected the cause indicated

on the interface. Cause is likely due to bad interface hardware or cable misconfiguration. Interface not err-disabled as user choose to see error-report. User should investigate and take action. Recommended Action Copy the error message exactly as it appears on the console or in the system



1698

UNICAST_FLOOD Messages


UDLD-6 Error Message %UDLD-6-UDLD_PORT_LINKDOWN: Fast UDLD cache times out for intf [chars], moves port to linkdown state Explanation Fast UDLD cache entry for the reported interface times out. This could be due to either

remote side port shut, LC OIR, or real link failure. UDLD moved the port to linkdown state for all cases. If this is not caused by a link failure, UDLD should receive a PM linkdown notification within the next 4 seconds. If UDLD does not receive any notification, then it will consider this a link failure and will err-disable the port. Recommended Action Copy the error message exactly as it appears on the console or in the system


UNICAST_FLOOD Messages This section contains unicast flooding (UNICAST_FLOOD) messages.

UNICAST_FLOOD-4 Error Message %UNICAST_FLOOD-4-DETECTED: Host [enet] on vlan [dec] is flooding to an unknown unicast destination at a rate greater than/equal to [dec] Kfps Explanation A host was found going up and down between ports. Recommended Action Verify the reason why the host is sending traffic to an unknown unicast

destination.

Error Message %UNICAST_FLOOD-4-FILTER_TABLE_FULL: The filter table is full Explanation The system has detected too many unicast floods to unknown destinations. Recommended Action Investigate the reason why so many hosts in the network are sending traffic to unknown unicast destinations.


1699

UTIL Messages

UNICAST_FLOOD-5 Error Message %UNICAST_FLOOD-5-FILTER_INSTALLED: Filter for host [enet] has been installed. It will be removed in [dec] minute(s) Explanation A host was flooding unicast packets to an unknown destination. A filter has been

installed. Recommended Action No action is required.

UTIL Messages This section contains utility messages.

UTIL-3 Error Message %UTIL-3-DLL: Data structure error -- %s Explanation A software error occurred, resulting in data structure inconsistency. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %UTIL-3-IDTREE_NOTRACE: [chars] Explanation A software error occurred, resulting in a data structure inconsistency. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1700

VACL Messages

Error Message %UTIL-3-IDTREE_TRACE: [chars] Explanation A software error occurred, resulting in a data structure inconsistency. Recommended Action Copy the message exactly as it appears on the console or in the system log.


VACL Messages This section contains VLAN ACL messages.

VACL-4 Error Message %VACL-4-VLANACCESSMAP_ACTION_CHANGED: No redirect interfaces, map - sequence [dec] action set to DROP Explanation One or more redirect interfaces were removed, leaving the redirect interface list

emptyand changing the sequence action to DROP. Recommended Action Update the sequence, adding one or more valid redirect interfaces to the

affected VLAN access maps.

Error Message %VACL-4-VLANACCESSMAP_CWAN_DELETE: VLAN ACCESS-MAP [chars] applied on [chars] will be removed. Explanation Logical interface(MFR,MLP) with a VACL Access-map is being removed so the

associated vlan filter will be removed to avoid config errors and inconsistencies Recommended Action User has to re-configure the vlan filter if the removed logical interface is being

removed

Error Message %VACL-4-VLANACCESSMAP_RDT_DELETE: [chars] [chars] is removed from redirect list of map: [chars] - sequence [dec] Explanation One of the redirect interfaces in a VLAN access map needed to be removed from a

redirect sequence. This situation can occur if the interface was deleted or became an active member of an Ethernet channel that is not supported. Recommended Action Revert the state of the interface and add this redirect interface again to the

redirect sequence for the affected VLAN access maps.


1701

VALENCIA Messages

VALENCIA Messages This section contains Services SPA Carrier Card (SSC-600) Valencia ASIC messages.

VALENCIA-3 Error Message %VALENCIA-3-GIO: Bay [dec]: [chars]. Explanation A data corruption due to a parity error was detected on the GIO bus. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %VALENCIA-3-NP: Bay [dec], [chars][dec]: [chars]. Explanation Data corruption was detected in one of the network processors. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %VALENCIA-3-PL3: Bay [dec]: [chars]. Explanation A data corruption due to a parity error was detected on the PL3 interface. Recommended Action If this message recurs, copy the message exactly as it appears on the console



1702

VALENCIA Messages


Error Message %VALENCIA-3-PLL_LOCK: Bay [dec]: [chars] PLL Lock Failure Explanation The specified phase-locked loop (PLL) failed to lock. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %VALENCIA-3-PPE: Bay [dec], [chars]: [chars]. Explanation Data corruption was detected in the VLAN RAM. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %VALENCIA-3-SPI_FIFO: Bay [dec], [chars]: [chars] [chars]. Explanation Data corruption was detected in one of the SPI FIFOs. Recommended Action If this message recurs, copy the message exactly as it appears on the console



1703

VDD Messages

Error Message %VALENCIA-3-SPI_SNK: Bay [dec]: [chars]. Explanation There was an error receiving data from the SPA, possibly due to data corruption. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %VALENCIA-3-SPI_SNK_CHAN: Bay [dec]: [chars] error on channel [dec]. Explanation There was an error receiving data from the SPA. Recommended Action If this message recurs, copy the message exactly as it appears on the console


Error Message %VALENCIA-3-SPI_SRC: Bay [dec]: [chars]. Explanation There was an error sending data to the SPA. Recommended Action If this message recurs, copy the message exactly as it appears on the console


VDD Messages This section contains virtual device driver (VDD) messages.


1704

VDD Messages

VDD-3 Error Message %VDD-3-NULL_CB: Supplied %s control block is NULL. %s Explanation An NULL control block was passed internally as part of an operation to read or write to

the required register or memory address. As a result, the operation could not be processed and the address contents are now incorrect. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VDD-3-NULL_SPACE_CB: Supplied %s space control block is NULL. %s Explanation An NULL space control block was passed internally as part of an operation to read or

write to the required address. As a result, the operation could not be processed and the address contents are now incorrect. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VDD-3-SIZE_TOO_LARGE: An attempt was made to create a %s of size %d bits. Explanation The virtual device driver received a request to create a data entity that is larger than allowed. Because the entry cannot be created, its data will be lost. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1705

VFI Messages


VFI Messages This section contains virtual forwarding instance (VFI) messages.

VFI-3 Error Message %VFI-3-ILLEGAL: %s Explanation An illegal event was processed by the XCONNECT subsystem. Recommended Action No action is required.

VFI-4 Error Message %VFI-4-CONFIG: %s Explanation The specified configuration data for a virtual forwarding instance (VFI) is invalid. Recommended Action No action is required.

VINES Messages This section contains Banyan Virtual Integrated Network Service (VINES) messages.

Error Message %VINES-2-INVALIDROUTE: Bad [chars] in route for server entry [v-name] Explanation While searching the routing table, the code determined that a pointer that should point to a VINES route structure actually points to some other structure. Recommended Action Copy the message exactly as it appears, and report it your technical support

representative. If possible, clear the VINES routing table. This will result in a temporary loss of connectivity until all routes are relearned.

VIP Messages This section contains Versatile Interface Processor (VIP) messages.


1706

VIPMLP Messages

VIP-3 Error Message %VIP-3-SVIP_CRASHINFO_ERROR: Crashinfo initiation failed on the VIP. Explanation The crash information (crashinfo) file for the VIP could not be collected because the

process to collect the crashinfo file could not be properly initiated. Recommended Action If the error message recurs, copy the message exactly as it appears on the

console or in the system log and enter the show controllers vip slot# tech-support and show controllers vip slot# logging commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

VIPMLP Messages This section contains multilink PPP messages.

Error Message %VIPMLP-2-NOINTERLEAVE: [chars] Interleave not configured due to Insufficient memory Explanation Interleave was not configured due to insufficient memory. Recommended Action Copy the message exactly as it appears on the console or in the system log.


VLAN_MAPPING_ISSU Messages This section contains VLAN mapping in-service software upgrade (ISSU) messages.


1707

VLAN_MAPPING_ISSU Messages

VLAN_MAPPING_ISSU-3 Error Message %VLAN_MAPPING_ISSU-3-BUFFER: vlan_mapping VLAN Mapping ISSU client failed to get buffer for message, error %d Explanation The VLAN mapping ISSU client was unable to get a buffer for building a negotiation



Error Message %VLAN_MAPPING_ISSU-3-CAPABILITY: vlan_mapping VLAN Mapping ISSU client %s Explanation The VLAN mapping ISSU client detected an error during capability negotiation. As a



Error Message %VLAN_MAPPING_ISSU-3-INIT: vlan_mapping VLAN Mapping ISSU client initialization failed at %s, error %s Explanation The VLAN mapping ISSU client could not be initialized. This condition will cause a




1708



Error Message %VLAN_MAPPING_ISSU-3-MSG_NOT_OK: vlan_mapping VLAN Mapping ISSU client message %d is not compatible Explanation The VLAN mapping ISSU client received an incompatible message from the peer unit.

The message cannot be processed by this unit. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VLAN_MAPPING_ISSU-3-MSG_SIZE: vlan_mapping VLAN Mapping ISSU client failed to get the message size for message %d Explanation The VLAN mapping ISSU client was unable to calculate the message size for the

message specified. The client will be unable to send the message to the standby unit. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VLAN_MAPPING_ISSU-3-POLICY: vlan_mapping VLAN Mapping ISSU client message type %d is %s Explanation The VLAN mapping ISSU client received a message type that it does not support. A

policy is applied to make the session compatible. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1709


http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show issu session commands and your pertinent troubleshooting logs.

Error Message %VLAN_MAPPING_ISSU-3-SEND_FAILED: vlan_mapping VLAN Mapping ISSU client failed to send a negotiation message, error %d Explanation The VLAN mapping ISSU client could not send a session negotiation message to the

peer. As a result, the standby unit cannot be brought up. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VLAN_MAPPING_ISSU-3-SESSION: vlan_mapping VLAN Mapping ISSU client %s Explanation The VLAN mapping ISSU client detected an error during a session negotiation with the




1710

VOA Messages

Error Message %VLAN_MAPPING_ISSU-3-TRANSFORM: vlan_mapping VLAN Mapping ISSU client %s transform failed, error %s Explanation The VLAN mapping ISSU client could not transform the message. If the transmit

transformation failed, the checkpoint message cannot be sent to the standby unit. If the receive transformation failed, the checkpoint message cannot be applied on the standby unit. In either case, the vlan_mapping VLAN Mapping state will not be identical with the active unit. Recommended Action Copy the message exactly as it appears on the console or in the system log.


VOA Messages This section contains Hamptons variable optical attenuator (VOA) subcards messages.

VOA-3 Error Message %VOA-3-HIGH_ALM_THR: High Alarm Threshold for optical power on port [chars] [chars] Explanation The high alarm threshold for the optical power level has been exceeded. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1711

VOA Messages

Error Message %VOA-3-HIGH_WARN_THR: High Warning Threshold for optical power on port [chars] [chars] Explanation The high warning threshold for the optical power level has been exceeded. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VOA-3-LOW_ALM_THR: Low Alarm Threshold for optical power on port [chars] [chars] Explanation The low alarm threshold for the optical power level has been exceeded. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VOA-3-LOW_WARN_THR: Low Warning Threshold for optical power on port [chars] [chars] Explanation The low warning threshold for the optical power level has been exceeded. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1712

VPD Messages

VPD Messages Error Message %VPD-4-CESCLK_INIT: ATM CES (Voice Processor Deck) clock source initialized to local oscillator. Explanation Warning indicates that ATM CES (Voice Processor Deck ) clock used will be internal. Recommended Action No action is required.

VPDN Messages This section contains Virtual Private Dialup Networking (VPDN) messages.

VPDN-3 Error Message %VPDN-3-DROP_ADDR_MISMATCH: [chars] Explanation The remote server changed its address. Recommended Action Change initiate-to configuration at the LAC to point to the exact IP address

LNS will use.

Error Message %VPDN-3-IP_SWITCH_ERR: l2x ip switching vector not installed Explanation The platform-dependent Layer 2X IP Cisco Express Forwarding (CEF) switching

module is missing. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPDN-3-NORESOURCE: [chars] [chars] [chars] no resources for user [chars][chars][chars] Explanation The platform (for example, the Cisco Network Authentication Server and L2TP access

concentrator (NAS/LAC) or the home gateway and L2TP network server (HGW/LNS)) has exhausted its resources for forwarding a VPDN user. Recommended Action Check the available memory of the platform.


1713

VPDN Messages

VPDN-4 Error Message %VPDN-4-MIDERROR: [chars] [chars] [chars] unable to terminate user [chars][chars][chars] Explanation The HGW/LNS was unable to complete the forwarding of the VPDN user because of an

internal error. This condition may be resource-related or configuration-related. A reason string may be present in the message text to indicate the point of failure. Recommended Action Check the configuration of the HGW/LNS.

Error Message %VPDN-4-REFUSED: Session for %s Refused status = %x Explanation The remote server refused this session. Recommended Action Check the configuration of the home gateway (HGW) or L2TP Network Server

(LNS).

Error Message %VPDN-4-SESSIONERROR: [chars] [chars][chars] unable to terminate user [chars][chars][chars] Explanation The HGW/LNS was unable to complete the forwarding of the VPDN user due to an

internal error. This error may be resource related or configuration related. A reason string may be present to indicate the point of failure. Recommended Action Check the configuration on the HGW/LNS

VPDN-5 Error Message %VPDN-5-NOIDB: [chars] [chars] [chars] unable to terminate user [chars] Explanation The HGW/LNS has exhausted its resources for creating sessions for VPDN forwarded

users. It has reached the maximum number of interfaces allowed on the router. Recommended Action Limit the number of interfaces to the maximum allowable interfaces.

Error Message %VPDN-5-UNREACH: [chars] [chars] [chars] is unreachable Explanation The platform (for example, the Cisco NAS/LAC or the HGW/LNS) has timed out while

it was attempting to establish a tunnel connection to a HGW/LNS or NAS/LAC. The timeout may be due to network, authentication, or authorization issues. Recommended Action Check the configuration on the platform and check the network connectivity

between the NAS/LAC and HGW/LNS. Check to see if the tunnel setup requires a different source IP address from that of the NAS/LAC.


1714

VPDN Messages

VPDN-6 Error Message %VPDN-6-AUTHENERR: [chars] [chars] [chars] cannot locate a AAA server for [chars] [chars] [chars][chars][chars] Explanation Either the NAS/LAC or the HGW/LNS is unable to locate an AAA server for the

purposes of authenticating the user or tunnel. This condition indicates that the router was unable to establish a network connection with the designated or configured server. A reason string may be present in the message text to provide further information. Recommended Action Check the AAA configuration on the platform (for example, the Cisco NAS/LAC or the HGW/LNS) and check the network connectivity to the AAA servers.

Error Message %VPDN-6-AUTHENFAIL: [chars] [chars] [chars], [atalk_address]uthentication failure [chars]for [chars] [chars] [chars][chars][chars] Explanation The platform (for example, the Cisco NAS/LAC or the HGW/LNS) has failed to

authenticate a user or a tunnel, or the HGW/LNS has failed authentication with the client that initiated the session. For authentication failures of the user or tunnel, a reason string should be present in the message text to indicate the point of failure. When a client fails to authenticate the HGW, a reason string may be present, depending upon the point of failure. Recommended Action Check the username configuration on the platform and, possibly, the client. If

the HGW/LNS is failing authentication, removing the negotiation of outbound authentication (that is, authenticating the user only in the inbound direction) is one possible solution. If AAA is applicable to the condition, check the AAA configuration on the NAS/LAC or HGW/LNS and check the network connectivity to the AAA servers.

Error Message %VPDN-6-AUTHORERR: [chars] [chars] [chars] cannot locate a AAA server for [chars] [chars] [chars][chars][chars] Explanation The platform (for example, the Cisco NAS/LAC or the HGW/LNS) is unable to locate

a AAA server for the purposes of authorizing the user or tunnel. The router was unable to establish a network connection with the designated or configured server. A reason string may be present in the message text to provide further information. Recommended Action Check the AAA configuration on the platform and check the network

connectivity to the AAA servers.

Error Message %VPDN-6-AUTHORFAIL: [chars] [chars] [chars], [atalk_address]uthorization failure for [chars] [chars] [chars][chars][chars] Explanation The platform (for example, the Cisco NAS/LAC or the HGW/LNS) has failed to

authorize a user or a tunnel. A reason string may be present in the message text to indicate the point of failure. Recommended Action Check the authorization configuration on the platform. If AAA is applicable to

the condition, check the network connectivity to the AAA servers.


1715

VPDN Messages

Error Message %VPDN-6-CLOSED: [chars] [chars] [chars] closed [chars] [chars] [chars][chars][chars] Explanation The remote server, typically the HGW/LNS, closed this session. The reason for the

closing is encoded in a hexadecimal format and corresponds to the particular protocol descriptions. For the L2F protocol, the values are documented in section 4.4.5 of the Internet Draft. A description string may also be present that describes the reason for the closing. Recommended Action Check the configuration on the platform (for example, the configuration of the Cisco NAS/LAC or the HGW/LNS).

Error Message %VPDN-6-DOWN: %s %s %s changed state to down %s %s %s%s%s Explanation The remote server, typically the home gateway (HGW) and L2TP Network Server

(LNS), closed this tunnel. The reason for the closure is encoded in a decimal format defined in the particular protocol specification. For example, the closure values for Layer 2 Forwarding (L2F) are documented in section 4.4.5 of the L2F Internet Draft. The closure reason may also be displayed in a description string. Recommended Action Check the configuration on the network access server (NAS) and L2TP access concentrator (LAC) , or on the home gateway (HGW) and L2TP Network Server (LNS).

Error Message %VPDN-6-MAX_SESS_EXCD: %s %s %s has exceeded configured local session-limit and rejected %s %s %s%s%s Explanation The NAS/LAC or HGW/LNS has refused this session since the configured maximum

VPDN session limit has been reached. Recommended Action No action is required.

Error Message %VPDN-6-RESIZE: Updated [chars] session table size to [int] Explanation The platform (for example, the Cisco NAS/LAC or the HGW/LNS) has altered the size

of the session table using the CLI. Recommended Action No action is required.

Error Message %VPDN-6-SOFTSHUT: %s %s %s has turned on softshut and rejected %s %s %s%s%s Explanation The NAS/LAC or HGW/LNS can no longer accept new connections when the vpdn softshut command has been entered. Existing sessions will continue until termination. Recommended Action To allow new connections, enter the no vpdn softshut command. Otherwise,

no action is required.


1716

VPLS_NP_CLIENT Messages

Error Message %VPDN-6-TIMEOUT: [chars] [chars] [chars] disconnected [chars] [chars] [chars][chars][chars] Explanation The platform (for example, the Cisco NAS/LAC or the HGW/LNS) has disconnected

the user because of the expiration of a timer. This condition may be PPP negotiation-related or might be an absolute timeout for the session. Recommended Action If the session has timed out automatically, no action is required.

Error Message %VPDN-6-VPDN_DEADCACHE_EVENT: LSG dead cache entry [IP_address] [chars] Explanation A dead cache entry status is changed in the VPDN Load Sharing Group (LSG) table.

The event could be ’Added’, where a LSG entry goes Down, ’Deleted’, where an entry moves out of the Down status, or ’Cleared’, where an entry is cleared by a user.

VPLS_NP_CLIENT Messages This section contains VPLS NP client messages.

VPLS_NP_CLIENT-3 Error Message %VPLS_NP_CLIENT-3-INFO: [chars] Explanation The VPLS NP client failed to initialize properly. This condition will result in improper

operation of the any transport over MPLS (AToM) feature. Recommended Action Reload the Cisco IOS image on the affected card or platform. If this message



1717

VPLS_NP_CLIENT Messages

Error Message %VPLS_NP_CLIENT-3-NOMEM: [chars] Explanation The VPLS NP client failed to initialize properly. This condition will result in improper

operation of the AToM feature. This error may indicate that more memory must be installed on the affected card or platform in order to service all the features and related entities enabled by the configuration. Recommended Action Reload the Cisco IOS image on the affected card or platform. If this message


VPLS_NP_CLIENT-4 Error Message %VPLS_NP_CLIENT-4-WARN: [chars] [dec] [chars] Explanation The entry could not be added because it is invalid. Recommended Action Reload the Cisco IOS image on the affected card or platform. If this message



1718

VPN_HW Messages

VPN_HW Messages This section contains VPN hardware accelerator for IPSec (VPN_HW) messages.

VPN_HW-0 Error Message %VPN_HW-0-SELF_TEST_FAILURE: Hardware Crypto self-test failed ([chars]) Explanation One of the hardware crypto self-tests has failed. The crypto engine is not operable in

this state. Recommended Action If the failure persists, contact Cisco to replace the hardware.

VPN_HW-1 Error Message %VPN_HW-1-ALIGN: Slot: [dec] - Alignment failure on packet buffer: [hex] Explanation A software error has occurred. The VPN hardware accelerator driver has detected that

the buffer is not aligned correctly. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPN_HW-1-ERROR: slot: [dec] - [chars] Explanation An error occurred in the application that was using the VPN hardware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1719

VPN_HW Messages

Error Message %VPN_HW-1-HEARTBEAT: VPN Module in slot: [dec]: Keepalive lost. Explanation Keepalive messages have been lost, which indicates that the VPN hardware accelerator

is no longer operating. Recommended Action Reboot your router. If this message recurs, copy the message exactly as it


Error Message %VPN_HW-1-INITFAIL: Slot [dec]: [chars] Explanation The VPN hardware accelerator driver could not initialize the accelerator at the slot

specified in the error message at the specified point. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPN_HW-1-NOMEMORY: [chars] creation failed for slot [dec] Explanation During its initialization phase, the VPN hardware driver could not allocate memory for

the data structure that is specified in the error message. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


1720

VPN_HW Messages

Error Message %VPN_HW-1-OWNER: slot: [dec]: [chars] packet buffer, pak=[hex] Explanation A software or hardware error has occurred. The VPN hardware accelerator driver has

detected that the buffer ring is in an inconsistent and unrecoverable state. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPN_HW-1-PACKET_ERROR: slot: [dec] Packet Encryption/Decryption error, [chars] Explanation An unexpected error occurred during the encryption or decryption of a packet. Recommended Action This message can occur occasionally during normal operation of the system. It

may occur during the transition to a new session key for a security association. In such cases, no action is required. However, if it happens frequently, or is associated with traffic disruption, then note the status value and contact your Cisco technical support representative. The VPN hardware accelerator will most likely need to be replaced.

Error Message %VPN_HW-1-TOOBIG: Slot: [dec] - [chars] received a packet with size [dec]. Explanation A packet was received that was too large. The hardware supports only the MTU size

specified in the message. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPN_HW-1-UNSUPP: VPN Module in slot: [dec]: [chars] ([hex]). Explanation This revision or version of the VPN hardware accelerator in the slot specified in the error message is not supported. Recommended Action Verify that the VPN hardware adapter is the proper hardware level and software revision for the running version of the Cisco IOS software. If it is, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools


1721

VPN_HW Messages

and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

VPN_HW-3 Error Message %VPN_HW-3-MULTDEV: Cannot support more than one Encryption AIM Explanation A second Encryption AIM was discovered present in the system. The Encryption AIM

software only supports a single Encryption AIM. All other Encryption AIMs installed will be ignored. Recommended Action Remove one of the Encryption AIMs that are installed in your system.

VPN_HW-4 Error Message %VPN_HW-4-PACKET_ERROR: slot: [dec] Packet Encryption/Decryption error, [chars] Explanation An unexpected error occurred during the encryption or decryption of a packet. Recommended Action This message can occur occasionally during normal operation of the system.

It may occur during the transition to a new session key for a security association. In such cases, no action is required. However, if it happens frequently, or is associated with traffic disruption, then note the status value and contact your Cisco technical support representative. The VPN hardware accelerator will most likely need to be replaced.

VPN_HW-6 Error Message %VPN_HW-6-FIPSFAIL: FIPS test_id [dec]([chars]) Test Failure will be induced Explanation The FIPS test was forced to fail from ROMMON. Recommended Action If this condition is undesirable, do not set FIPS_FAIL using ROMMON.

Error Message %VPN_HW-6-INFO: slot: [dec] [chars] Explanation This is an informational message from the VPN hardware accelerator driver. Recommended Action No action is required.


1722

VPNMAP Messages

Error Message %VPN_HW-6-INFO_LOC: Crypto engine: [chars] [chars] Explanation This is an informational message from the VPN hardware accelerator driver. Recommended Action No action is required.

Error Message %VPN_HW-6-SHUTDOWN: [chars] shutting down Explanation The specified VPN hardware is shutting down. It may have been physically removed. Recommended Action This is an informational message only. No action is required.

VPNMAP Messages This section contains Virtual Private Network mapper (VPNMAP) messages.

VPNMAP-2 Error Message %VPNMAP-2-REALLOC_ERROR: Exceeded number of resources to support hardware switching of VRF %s. Please unconfigure some of the existing VRFs as some entries will be software switched in the next reload. Explanation Because no further hardware resources are available to support hardware switching of

VRFs, some VRFs must be software switched. Unconfigure the mls ipv6 vrf command or some of the existing features that use those resources. Examples of features using hardware switching resources are VRF, EoMPLS, and MDT. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, remote command module, show platform software vpn mapping, show platform software vpn status, and show running-config commands and your pertinent troubleshooting logs.


1723

VPNSM Messages

Error Message %VPNMAP-2-SPACE_EXCEEDED: Exceeded number of resources to support hardware switching of VRFs. Please unconfigure some of the existing VRFs as some entries will be software switched. Explanation Because no further hardware resources are available to support hardware switching of

VRFs, some VRFs must be software switched. Unconfigure the mls ipv6 vrf command or some of the existing features that use those resources. Examples of features using hardware switching resources are VRF, EoMPLS, and MDT. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, remote command module, show platform software vpn mapping, show platform software vpn status, and show running-config commands and your pertinent troubleshooting logs.

VPNSM Messages This section contains Virtual Private Network Services Module (VPNSM) messages.

VPNSM-2 Error Message %VPNSM-2-ACE_PKA_KAT_FAILURE: PKA: Known Answer Test failure: [chars] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1724

VPNSM Messages

Error Message %VPNSM-2-ACESCPERROR: Null MAC address pointer in SCP module Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


VPNSM-3 Error Message %VPNSM-3-ACEI0BADPARAM: PcpManCreateTunn: cannot create tunnel with expiring Sa Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI0TCAMFAILED: SpdSpInstall: cannot install Sp [dec]: TmInsertSp failed Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1725

VPNSM Messages

Error Message %VPNSM-3-ACEI1BADPARAM: SpdSpInstall: cannot install generic SP [dec] with non-zero priority Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI1OUTOFSA: PcpQOpCreSaBegin: cannot create new Sa using SpdMan Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI10OUTOFCME: PcpManCreateAcl: cannot allocate new Acl for aclId=[int] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1726

VPNSM Messages

Error Message %VPNSM-3-ACEI11NESTOVERFLOW: SpdSaAddTmInsCb: cannot have more than [dec] pending nested callbacks from TcamMan Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI11OUTOFSEL: PcpAclGetSpSelSet: cannot clone SelSet for ACL [dec] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI2BADPARAM: PcpManUpdateFlow: cannot update flow [dec] with invalid ID Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1727

VPNSM Messages

Error Message %VPNSM-3-ACEI12IDNOTINUSE: PcpManRemoveAcl: cannot remove non-existing access list [int] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI12OUTOFSAPAR: SpdSaSetKeys: cannot allocate new SaPar for Sa [dec] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI13IDINUSE: PcpManRemoveAcl: cannot remove access list [int] while in use Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1728

VPNSM Messages

Error Message %VPNSM-3-ACEI3OUTOFSEL: PcpQOpActSaBegin: cannot allocate selector set for outer Sa in flowId [dec] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI14BADCMEID: PcpSpdCreateCme: cannot create Cme with ID=[dec]: too large Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI14NOLOGA: SpdSaSetParams: cannot allocate SPI with TcamMan for Sa [dec] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1729

VPNSM Messages

Error Message %VPNSM-3-ACEI15IDNOTINUSE: PcpManRemoveCme: cannot remove non-existing Cme [int] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI16BADPARAM: PcpManActivateFlowAsync: cannot activate flow [dec]: Sa is in the wrong state Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI16TCAMFAILED: SpdSaTmInstallIn: cannot install inbound Sa [dec] with TcamMan Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1730

VPNSM Messages

Error Message %VPNSM-3-ACEI17BADPARAM: PcpManActivateFlowAsync: cannot activate non-existing flow [dec] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI17TCAMFAILED: SpdSaTmInstallOut: cannot install outbound Sa [dec] with TcamMan Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI18BADPARAM: PcpManCreateSMap: cannot create outbound SPD Map [int] with ingress access list [int] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1731

VPNSM Messages

Error Message %VPNSM-3-ACEI19BADCMEID: PcpManActivateFlowAsync: cannot activate flow [dec] with non-existing Cme [dec] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI2BADPARAM: PcpManUpdateFlow: cannot update flow [dec] with invalid ID Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI2NESTOVERFLOW: SpdSaInitTmSaOut: outer outbound Sa [dec] of Sa [dec] is above nesting limit of [dec] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1732

VPNSM Messages

Error Message %VPNSM-3-ACEI20OUTOFSEL: PcpUtilSelSetFromPar: cannot allocate new selector set Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI21BADPARAM: PcpAclAppend: got too many denys for aclId=[dec], max is [dec] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI22BADPARAM: PcpAclAppend: got out-of-sequence line number [dec] for aclId=[dec] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1733

VPNSM Messages

Error Message %VPNSM-3-ACEI23IDINUSE: PcpSpdCreateCme: cannot create Cme with ID=[int]: already used Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI24BADPARAM: PcpAclAppend: got invalid ranges for selector set at lineNo=[dec], aclId=[dec] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI25IDINUSE: PcpAclAppend: got duplicate line number [dec] for aclId=[dec] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1734

VPNSM Messages

Error Message %VPNSM-3-ACEI26OUTOFSP: PcpCmeInstallNext: cannot create a new Sp Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI27BADPARAM: PcpManSetFlowKeys: cannot set keys for flow [dec]: SA is in the wrong state Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI28IDINUSE: PcpQOpCreSaBegin: cannot create second Sa for flow [dec]: conditions for transport adj. are not met Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1735

VPNSM Messages

Error Message %VPNSM-3-ACEI29SPDFAILED: PcpCmeInstallNext: cannot install Sp [dec] with SpdMan Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI3NESTOVERFLOW: SpdSaGetXformSeq: outer inbound Sa [dec] of Sa [dec] is above nesting limit of [dec] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI3OUTOFSEL: PcpQOpActSaBegin: cannot allocate selector set for outer Sa in flowId [dec] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1736

VPNSM Messages

Error Message %VPNSM-3-ACEI30BADPARAM: PcpSpdUpdateCme: cannot update already queued Cme [int] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI31BADALENUM: PcpQOpActSaBegin: cannot find access list entry number [dec] for cmeId=[dec] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI32BADPARAM: PcpQOpActSaBegin: cannot delete old [chars]bound flow [dec] while activating [chars]bound flow [dec] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1737

VPNSM Messages

Error Message %VPNSM-3-ACEI33BADPARAM: PcpCmeActivateSa: got invalid lifetime values softSecs=[int], hardSecs=[int] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI34BADPARAM: PcpCmeActivateSa: got invalid lifetime values softKBytes=[int], hardKBytes=[int] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI35BADPARAM: PcpCmeIntersectSaWithSp: cannot activate flow [dec] with selector ranges not intersecting parent Sp Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1738

VPNSM Messages

Error Message %VPNSM-3-ACEI36BADSELADDR: PcpQOpActSaBegin: cannot activate per-host flow [dec] with addresses [dec].[dec].[dec].[dec] and [dec].[dec].[dec].[dec] not included in Sp [dec] selector sets Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI37OUTOFSEL: PcpQOpActSaBegin: cannot clone selector set to activate per-host flow [dec] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI38BADSELADDR: PcpQOpActSaBegin: cannot activate transport mode flow [dec] with addresses [dec].[dec].[dec].[dec] and [dec].[dec].[dec].[dec] not included in Sp’s selector sets Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1739

VPNSM Messages

Error Message %VPNSM-3-ACEI39BADPARAM: PcpTrInProcess: got invalid opcode [dec] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI4BADPARAM: PcpQOpCreSaBegin: got invalid addresses [int].[int].[int].[int] and [int].[int].[int].[int] for other Sa of flow [dec]: expected [int].[int].[int].[int] and [int].[int].[int].[int] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI40BADACLID: PcpManCreateCme: cannot create Cme with non-existing access list [int] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1740

VPNSM Messages

Error Message %VPNSM-3-ACEI41SPDFAILED: PcpQOpSaActivated: cannot finish activating Sa [dec] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI42QUEUEFULL: PcpCmeActivateSa: cannot activate Sa [dec]: queue is full Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI43BADPARAM: PcpAclAppend: got invalid line number [dec] for ACL [dec] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1741

VPNSM Messages

Error Message %VPNSM-3-ACEI44QUEUEFULL: PcpSpdCreateCme: cannot create Cme [int] (aclId=[int]): queue is full Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI45IDNOTINUSE: PcpManDestroyFlowAsync: cannot delete already deleted flow [dec] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI46BADPARAM: PcpQOpActSaBegin: cannot activate non-fully-specified Sa for Cme [dec] without Acl Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1742

VPNSM Messages

Error Message %VPNSM-3-ACEI47BADPARAM: PcpQOpActSaBegin: cannot activate Sa for manual Sp (cmeId=[dec],entry=[dec]), Sa already exists Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI48CMEINUSE: PcpManSetInitMode: cannot set fast init-mode in TcamMan: [dec] pending Ops, [dec] Flows and [int] Cmes already exist or TcamMan is busy Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI49BADPARAM: PcpManQueryFlow: cannot query flow [dec]: Sa is not active Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1743

VPNSM Messages

Error Message %VPNSM-3-ACEI5BADPARAM: SpdSaActivate: cannot activate Sa [dec], old Sa [dec] already has successor Sa [dec] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI5OUTOFSA: PcpQOpCreSaBegin: cannot create new Sa for flow [dec] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI50CMEINUSE: PcpQOpRemCmeBegin: cannot remove Cme [dec]: TcamMan is in Init mode Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1744

VPNSM Messages

Error Message %VPNSM-3-ACEI51BADPARAM: PcpSpdCreateCme: got invalid flags (manual,dynamic,discover,drop,clear) = ([dec],[dec],[dec],[dec],[dec]), cmeId=[dec] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI52IDINUSE: PcpManCreateAcl: cannot process opcode [int] for Acl [int] in state [int] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI53BADPARAM: PcpManCreateAcl: cannot create Acl with id [int] out of range [0,[int]] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1745

VPNSM Messages

Error Message %VPNSM-3-ACEI54CMENOTREADY: PcpSpdCreateCme: cannot create Cme [int] with Acl [int] when Acl state is [int] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI55SPDFAILED: PcpQOpActSaBegin: cannot begin activating Sa [dec] for flowId [dec] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI56IDNOTINUSE: PcpManDestroyFlowAsync: cannot delete flow [dec] already being deleted Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1746

VPNSM Messages

Error Message %VPNSM-3-ACEI57CMEINUSE: PcpManSetInitMode: cannot set normal init-mode in TcamMan: there are pending Flows or Cmes Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI58IDNOTINUSE: PcpManDestroyFlowAsync: flow [dec] already queued for deletion Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI59BADPARAM: PcpCmeActivateSa: cannot activate flow [dec] as per-host with subset of Sp as a selector set Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1747

VPNSM Messages

Error Message %VPNSM-3-ACEI6BADPARAM: PcpTrInProcess: got invalid size [dec] for opcode [dec] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI6OUTOFSEL: SpdSpInstall: cannot compute SP’s permit-SelSets from mixed SelSet list Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI60SPDFAILED: PcpManSaUpdateError: cannot update Flow [dec] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1748

VPNSM Messages

Error Message %VPNSM-3-ACEI61BADPARAM: PcpQOpActSaBegin: cannot activate Sa for cmeId=[dec], entry=[dec] with bad spdId=[dec] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI62IDINUSE: PcpQOpCreSaBegin: cannot setup Flow [dec] in trans.adj. with outer SA in tunnel mode Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI63CMEINUSE: PcpManActivateFlowAsync: cannot activate flow [dec] while using fast policy mode Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1749

VPNSM Messages

Error Message %VPNSM-3-ACEI64BADPARAM: PcpQOpActSaBegin: got invalid ranges for selector set of fully-specified flow [dec] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI65BADPARAM: PcpManSetInitMode: got invalid flags [hex] for setting fast policy mode Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI66NOTREADY: PcpManUpdateFlow: cannot update flow [dec] when SA is not active Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1750

VPNSM Messages

Error Message %VPNSM-3-ACEI67BADPARAM: PcpSpdCreateSMap: cannot create SMap [int] with Acl [int] when Acl state is [int] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI68BADPARAM: PcpAclAppend: got invalid flags [hex] at lineNo=[dec], aclId=[dec] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI69BADPARAM: PcpManCreateCme: cannot create Cme [int] with spdId [int] out of range [0,[int]] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1751

VPNSM Messages

Error Message %VPNSM-3-ACEI7BADPARAM: PcpManSetFlowKeys: cannot set keys for flow [dec]: invalid ID Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI7OUTOFSEL: SpdSaTmInstallOut: cannot compute outbound SA’s permit-SelSets from mixed SelSet list Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI70IDNOTINUSE: PcpManUpdateCme: cannot update non-existing Cme [int] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1752

VPNSM Messages

Error Message %VPNSM-3-ACEI71QUEUEFULL: PcpSpdUpdateCme: cannot update Cme [int]: queue is full Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI72QUEUEFULL: PcpSpdCreateSMap: cannot create SPD map with mapId [int]: queue is full Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI73BADPARAM: PcpSpdCreateSMap: cannot create SPD map with mapId [int] out of range [0,[int]] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1753

VPNSM Messages

Error Message %VPNSM-3-ACEI74IDINUSE: PcpSpdCreateSMap: cannot create SPD map with mapId [int] already in use Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI75TMFAILED: PcpSMapInstall: cannot insert SMap [int] with TcamMan Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI76BADPARAM: PcpSpdCreateSMap: cannot create SPD map [int] with invalid flags [hex] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1754

VPNSM Messages

Error Message %VPNSM-3-ACEI77BADPARAM: PcpManCreateSMap: cannot create SPD Map [int] using non-existent access list [int] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI78OUTOFSMAP: PcpSpdCreateSMap: cannot create SPD map [int]: out of memory Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI79BADPARAM: PcpQOpActSaBegin: cannot activate Sa for cmeId=[dec], entry=[dec] when Cme is not ready Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1755

VPNSM Messages

Error Message %VPNSM-3-ACEI80QUEUEFULL: PcpManDestroyFlowAsync: cannot delete flowId [dec]: operation queue is full Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI81IDNOTINUSE: PcpQOpDelSaBegin: cannot delete already deleted flow [dec] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI82QUEUEFULL: PcpManRemoveCme: cannot remove Cme with cmeId [int]: queue is full Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1756

VPNSM Messages

Error Message %VPNSM-3-ACEI83TMFAILED: PcpSpdInitialize: cannot insert SPD [int] with TcamMan Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI84BADPARAM: PcpManCreateSMap: cannot create SPD map [int] with spdId [int] out of range [0,[int]] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI85OUTOFSMAP: PcpManCreateSpd: cannot create SPD [int]: out of memory Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1757

VPNSM Messages

Error Message %VPNSM-3-ACEI86IDINUSE: PcpManActivateFlowAsync: cannot activate already active flow [dec] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI87BADPARAM: PcpManCreateFlow: cannot create Flow with id=[dec], max is [dec] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI88IDNOTINUSE: PcpManRemoveSMap: cannot remove non-existing SMap [int] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1758

VPNSM Messages

Error Message %VPNSM-3-ACEI89OUTOFCME: PcpSpdCreateCme: cannot allocate new Cme for aclId=[int] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ACEI92QUEUEFULL: PcpManCreateFlow: cannot create flowId [dec]: operation queue is full Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-3-ICPUBADGRESA: Invalid GRE SA - can’t find match. saptr:[hex] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1759

VPNSM Messages

Error Message %VPNSM-3-SPI_NOT_AVAIL: SPI [hex] is not available Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


VPNSM-4 Error Message %VPNSM-4-ACETCAMFULLINSMANSP: Full SA insertion for a manual SP. Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-4-ACETCAMPKTNOSA: Packet event for a non-existing SA. Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1760

VPNSM Messages

Error Message %VPNSM-4-ACETCAMPKTNOSP: Packet event for a non-existing SP. Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-4-ACEXCPUALLOC: IPC: Unable to allocate and send STATFLUSH. Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-4-ACEXCPUALLOC2: IPC: Unable to allocate IPC to set debug flag. Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1761

VPNSM Messages

Error Message %VPNSM-4-ACEXCPUALLOC3: IPC: Unable to allocate IPC to start 5840 test. Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-4-ACEXCPUCMMTU2: CFGMON: Failed to set MTU. Invalid data [dec], ifvlan [hex]. Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-4-ACEXCPUCMRESP: XcpuCfgMonReqCallback:Can’t respond to host. Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1762

VPNSM Messages

Error Message %VPNSM-4-ACEXCPUCMRESP3: XcpuCfgMonReqCallback:Global stats...Can’t respond to host. Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-4-ACEXCPUCMRESP4: XcpuCfgMonReqCallback: PerFlow Stats....Can’t respond to host. Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-4-ACEXCPUCMRESP5: XcpuCfgMonReqCallback: PerFlow Stats....Can’t respond to host. Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1763

VPNSM Messages

Error Message %VPNSM-4-DUMPMEM: [hex]: [hex] [hex] [hex] [hex] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-4-EDSDEBUG: SingleBufErr:([hex]) Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-4-FIPSCHECK2: FIPS RCVD Multi-buffer Packet. Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1764

VPNSM Messages

Error Message %VPNSM-4-FIPSCHECK3: FIPS Failed Packet Comparison. Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-4-FIPSCHECK4: FIPS Test Completed Successfully. Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-4-ICPUFRAG1: PktReasmSetAction failed. Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1765

VPNSM Messages

Error Message %VPNSM-4-ICPUPP2: SaCheckSelectors: Illegal pkt, no valid SA Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-4-ICPUPP3: Illegal pkt dst:[dec].[dec].[dec].[dec] proto:[dec] spi:[hex], no match on SA SPI [hex]. Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-4-ICPUPP4: Illegal pkt dst:[dec].[dec].[dec].[dec] proto:[dec] spi:[hex], no match on SA dst[dec].[dec].[dec].[dec] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1766

VPNSM Messages

Error Message %VPNSM-4-ICPUPP8: Illegal clear pkt src:[dec].[dec].[dec].[dec] dst:[dec].[dec].[dec].[dec] proto:[dec]. Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-4-ICPUPP9: Packet src:[dec].[dec].[dec].[dec] dst:[dec].[dec].[dec].[dec] seq num:[hex] failed replay check last seq num:[hex] for SA:[hex]. Explanation IPsec packets have failed the anti-replay check. A common cause is the use of QoS in

your network. With QoS, lower priority packets can arrive late, missing the anti-replay check window. When this condition occurs, higher level protocols can request retransmission so that functionality is not lost. Time-sensitive protocols, such as voice traffic, might be degraded due to dropped or late packets. Recommended Action If anti-replay checking is not needed, disable it by removing the HMAC

function from the transform set.

Error Message %VPNSM-4-ICPUPP10: Packet src:[dec].[dec].[dec].[dec] dst:[dec].[dec].[dec].[dec] proto ESP, but not SA proto! Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1767

VPNSM Messages

Error Message %VPNSM-4-ICPUPP11: Packet src:[dec].[dec].[dec].[dec] dst:[dec].[dec].[dec].[dec] proto AH, but not SA proto! Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-4-ICPUPP12: IPPE says IPSec, not pkt src:[dec].[dec].[dec].[dec] dst:[dec].[dec].[dec].[dec] proto:[dec]! Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-4-ICPUPP13: Policy check failed for pkt src:[dec].[dec].[dec].[dec] dst:[dec].[dec].[dec].[dec] proto:[dec] SA index:[hex] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1768

VPNSM Messages

Error Message %VPNSM-4-ICPUPP14: Pkt src:[dec].[dec].[dec].[dec] dst:[dec].[dec].[dec].[dec] proto:[dec] match deny; SA index [hex] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-4-ICPUPP15: SecInfo [hex] doesn’t match with SA [hex] SA index:[hex] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-4-ICPUPP16: Inner proto [dec] must be IPSec but is not Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1769

VPNSM Messages

Error Message %VPNSM-4-ICPUSYSIPADDRADD: PktProcAddSysIpAddr: Unable to add local IP Addr [hex] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-4-ICPUSYSIPADDRDEL: PktProcAddSysIpAddr: Unable to delete local IP Addr [hex] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-4-ISAUNCA7: PktProcAtnModSas: Mismatch valid flag unca:invalid index:[hex] Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1770

VPNSM Messages

Error Message %VPNSM-4-RECOVERYDONE: CP Lockup Recovery - Done Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-4-RECOVERYFRAG: Ipfrag: Unable to transmit. CP Lockup Occured. Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-4-RECOVERYSTART: CP Lockup Recovery - Start(OCPU) Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1771

VPNSM Messages

Error Message %VPNSM-4-XCPURECOVERY: Error Disabling CP Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


VPNSM-6 Error Message %VPNSM-6-ACEPKAHWCRNGT: PKA: HW RNG has duplicate data, discarding Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSM-6-ACEPKARNGDUP: PKA: A pseudo-random number was generated twice in succession. [hex][hex]; 0Unrecognized format ‘x%p’ 0Unrecognized format ‘x%p’ idx:[hex] Explanation An error has been reported by the firmware Recommended Action Copy the message exactly as it appears on the console or in the system log.



1772

VPNSMIOS Messages

Error Message %VPNSM-6-ACEPKARNGKAT: PKA: RNG failed KAT Explanation An error has been reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


VPNSMIOS Messages This section contains VPNSM crypto connection (VPNSMIOS) messages.

VPNSMIOS-3 Error Message %VPNSMIOS-3-ILLEGALINTERFACE: Traffic matching crypto maps on [chars] will go through unencrypted. Please reconfigure crypto maps as required by VPN service module. Explanation An attempt was made to apply an encryption (crypto) map set to an interface that is not a VLAN interface. When this IPsec VPN accelerator is being used, crypto map sets can only be applied to a VLAN interface that has a proper encryption (crypto) connection to a physical port. The interface has been disabled. For more information on crypto guidelines, consult the system configuration manuals. Recommended Action Remove the crypto map set from the virtual interface. For more details, consult

the configuration guidelines.

Error Message %VPNSMIOS-3-MACEDONCTVLALLOCFAIL: Failed to allocate Control vlan on stby Explanation An internal error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1773

VPNSMIOS Messages

Error Message %VPNSMIOS-3-MACEDONCTVLTIMERON: Control vlan timer is on on stby Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSMIOS-3-MACEDONNOCCONB2BERR: [chars]no crypto connect is disallowed Explanation The system cannot remove the cryptographic connection when a module-to-module partner is still active. Recommended Action Remove the module-to-module configuration before removing the

cryptographic connection.

Error Message %VPNSMIOS-3-MACEDONTUNNELADDCBERR: [chars]: tunnel addcb failed: reason[[chars]] tvlan[[dec]] slot[[chars]] Explanation An error response was received when attempting to seize the tunnel. In a virtual switch

system (VSS), slot [[chars]] indicates switch/slot/subslot; otherwise it indicates slot/subslot. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSMIOS-3-MACEDONTUNNELADDERR: [chars]: tunnel add failed: reason[[chars]] ifvlan[[dec]] tvlan[[dec]] slot[[chars]] src[[IP_address]] dst[[IP_address]] Explanation An attempt to seize the tunnel has failed. In a virtual switch system (VSS), slot [[chars]]

indicates switch/slot/subslot; otherwise it indicates slot/subslot. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1774

VPNSMIOS Messages


Error Message %VPNSMIOS-3-MACEDONTUNNELCREATEPOLOQERR: Failed to create PoloReplicateCfg Q Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSMIOS-3-MACEDONTUNNELCREATEPROCERR: Failed to create Ace Tunnel Task Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSMIOS-3-MACEDONTUNNELCREATEQERR: Failed to create watched Q Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1775

VPNSMIOS Messages


Error Message %VPNSMIOS-3-MACEDONTUNNELCREATETIDERR: Failed to create Ace Tunnel-id bitvector Explanation An internal error occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSMIOS-3-MACEDONTUNNELDELETEIFVLANNOTFOUNDERR: [chars]: no tm found while attempting to delete from ifvlan[[dec]] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSMIOS-3-MACEDONTUNNELDELETETMNOTFOUNDERR: [chars]: no tm found while attempting to delete Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1776

VPNSMIOS Messages

Error Message %VPNSMIOS-3-MACEDONTUNNELNOEVENTMSGHANDLERERR: msgtype[[chars]]: No event msg handler found. Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSMIOS-3-MACEDONTUNNELNOIDBERR: No tunnel idb Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSMIOS-3-MACEDONTUNNELNOTMMSGHANDLERERR: msgtype[[chars]]: No tm msg handler found. Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1777

VPNSMIOS Messages

Error Message %VPNSMIOS-3-MACEDONTUNNELREMOVECBERR: [chars]: tunnel removecb failed: reason[[chars]] tvlan[[dec]] slot[[chars]] Explanation An error response was received when attempting to release the tunnel. In a virtual

switch system (VSS), slot [[chars]] indicates switch/slot/subslot; otherwise it indicates slot/subslot. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSMIOS-3-MACEDONTUNNELREMOVEERR: [chars]: tunnel remove failed: reason[[chars]] ifvlan[[dec]] tvlan[[dec]] slot[[chars]] src[[IP_address]] dst[[IP_address]] id[[dec]] Explanation An attempt to release the tunnel has failed. In a virtual switch system (VSS), slot

[[chars]] indicates switch/slot/subslot; otherwise it indicates slot/subslot. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSMIOS-3-MACEDONTUNNELVACLERR: vlan[[dec]]: failed to set vacl: action[[dec]] reason[[dec]] Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1778

VPNSMIOS Messages

Error Message %VPNSMIOS-3-MACEDONTUNNELVLANERR: [chars]: allocated idb has invalid vlan id Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSMIOS-3-MACEDONTUNNELVLANIDBERR: [chars]: unable to allocate idb Explanation An internal error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSMIOS-3-SLOTMISMATCH: [chars] has mismatch crypto engine binding. Egress interface is binded to crypto engine [int]/[int] but tunnel protection is binded to [int]/[int]. This tunnel is now shutdown. Explanation To use VPN-SM for tunnel protection, the user must enter the crypto engine slot slot

command on both the egress interface VLAN and the tunnel interface. The slot on both interfaces must match. When this requirement is not met, this message is displayed. The tunnel is now shut down. Recommended Action Modify either one or both crypto engine slot values so that they match.

Error Message %VPNSMIOS-3-VLANALLOCFAIL: Failed to allocate vlan for %s Explanation The system was unable to allocate a VLAN for internal use. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1779

VPNSMIOS Messages

http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show platform hardware capacity vlan, and show vlan internal usage commands and your pertinent troubleshooting logs.

VPNSMIOS-4 Error Message %VPNSMIOS-4-DIFFCRYPTOENGINE: [chars]. Another interface [chars] has same local-address [chars] but is on a different crypto engine [chars] Explanation Two crypto interfaces with the same local address must be on the same crypto engine.

In a virtual switch system (VSS), crypto engine [chars] indicates switch/slot/subslot; otherwise it indicates slot/subslot. Recommended Action Reconfigure the crypto engine command on the interface.

Error Message %VPNSMIOS-4-LIMITFVRF: System has reached the limit of supported front-door VRF. ([dec]) Explanation The number of front-door VRFs supported by VPNSM has reached its limit. Recommended Action Unconfigure any unused VRFs.

Error Message %VPNSMIOS-4-PROMISCOUSMODE: Outside port failed to be in [chars] mode Explanation This message is relevant only if the outside port is an FEPA port. Recommended Action Reconfigure the crypto connect command.

Error Message %VPNSMIOS-4-VPNSMILLEGALQOS0: VPNSM Slot: [dec] can only support [dec] cos maps in high priority queue, CoS configuration ignored, reset cos map by issuing no priority queue cos-map 1 command Explanation An illegal configuration has been detected. Recommended Action Reset the CoS map by entering the no priority-queue cos-map 1 command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


1780

VPNSMIOSSP Messages

VPNSMIOSSP Messages This section contains VPN service module (VPNSM) crypto connection SP messages.

Error Message %VPNSMIOSSP-6-MACEDONPOWEROFF: Non crypto image detected, disallowing power to VPN-SM module in slot [chars]. Explanation The chassis was booted up with an image that does not have the necessary crypto

subsystems for the VPN-SM to run correctly. In a virtual switch system (VSS), slot [[chars]] indicates switch/slot/subslot; otherwise it indicates slot/subslot. Recommended Action Contact your Cisco technical support representative to obtain the correct

image. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

VPNSPA Messages This section contains Virtual Private Network shared port adapter (VPNSPA) messages.

VPNSPA-0 Error Message %VPNSPA-0-ACELOGTEST7: Log test: SEV_EMERG Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1781

VPNSPA Messages

VPNSPA-1 Error Message %VPNSPA-1-ACELOGTEST6: Log test: SEV_ALERT Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


VPNSPA-2 Error Message %VPNSPA-2-ACEIKEADRVPKRM: Decode of RSA Private Key %d failed Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-2-ACEIKEANVRWRT: RSA Private Key %d NOT written to NVRAM Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1782

VPNSPA Messages

Error Message %VPNSPA-2-ACEIKEANVWRT: RSA Private Key %d NOT zeroized in NVRAM Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-2-ACEIKEANVWRT2: RSA Private Key %d NOT written to NVRAM Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-2-ACEIKEAPRVCREDRV: Driver refused RSA Private Key Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1783

VPNSPA Messages

Error Message %VPNSPA-2-ACEIKEAPRVCRESES: Driver refused RSA Private Key %d Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-2-ACEIKEAPRVDRV: Driver refused RSA Private Key Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-2-ACEIKEAPRVNVRD: RSA Private Key %d NOT read from NVRAM Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1784

VPNSPA Messages

Error Message %VPNSPA-2-ACEIKEAPRVREJ: RSA Private Key %d NOT written to NVRAM Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-2-ACEIKEAPRVRMDRV: Decode of RSA Private Key %d failed Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-2-ACEIKEAPRVRMSESDRV: Decode of RSA Private Key %d failed Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1785

VPNSPA Messages

Error Message %VPNSPA-2-ACELOGTEST5: Log test: SEV_CRIT Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-2-ACENVRAMCSUM: NVRAM Checksum failed Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-2-ACENVRAMWR: Write to nvram failed Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1786

VPNSPA Messages

Error Message %VPNSPA-2-ACE_PKA_KAT_FAILURE: PKA: Known Answer Test failure: %s Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


VPNSPA-3 Error Message %VPNSPA-3-ACEI0BADPARAM: PcpManCreateTunn: cannot create tunnel with expiring Sa Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI0TCAMFAILED: SpdSpInstall: cannot install Sp %ld: TmInsertSp failed Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1787

VPNSPA Messages

Error Message %VPNSPA-3-ACEI10OUTOFCME: PcpManCreateAcl: cannot allocate new Acl for aclId=%u Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI11NESTOVERFLOW: SpdSaAddTmInsCb: cannot have more than %ld pending nested callbacks from TcamMan Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI11OUTOFSEL: PcpAclGetSpSelSet: cannot clone SelSet for ACL %d Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1788

VPNSPA Messages

Error Message %VPNSPA-3-ACEI12IDNOTINUSE: PcpManRemoveAcl: cannot remove non-existing access list %u Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI12OUTOFSAPAR: SpdSaSetKeys: cannot allocate new SaPar for Sa %ld Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI13IDINUSE: PcpManRemoveAcl: cannot remove access list %u while in use Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1789

VPNSPA Messages

Error Message %VPNSPA-3-ACEI14BADCMEID: PcpSpdCreateCme: cannot create Cme with ID=%ld: too large Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI14NOLOGA: SpdSaSetParams: cannot allocate SPI with TcamMan for Sa %ld Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI15IDNOTINUSE: PcpManRemoveCme: cannot remove non-existing Cme %u Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1790

VPNSPA Messages

Error Message %VPNSPA-3-ACEI16BADPARAM: PcpManActivateFlowAsync: cannot activate flow %ld: Sa is in the wrong state Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI16TCAMFAILED: SpdSaTmInstallIn: cannot install inbound Sa %ld with TcamMan Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI17BADPARAM: PcpManActivateFlowAsync: cannot activate non-existing flow %ld Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1791

VPNSPA Messages

Error Message %VPNSPA-3-ACEI17TCAMFAILED: SpdSaTmInstallOut: cannot install outbound Sa %ld with TcamMan Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI18BADPARAM: PcpManCreateSMap: cannot create outbound SPD Map %u with ingress access list %u Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI19BADCMEID: PcpManActivateFlowAsync: cannot activate flow %ld with non-existing Cme %ld Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1792

VPNSPA Messages

Error Message %VPNSPA-3-ACEI1BADPARAM: SpdSpInstall: cannot install generic SP %d with non-zero priority Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI1OUTOFSA: PcpQOpCreSaBegin: cannot create new Sa using SpdMan Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI20OUTOFSEL: PcpUtilSelSetFromPar: cannot allocate new selector set Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1793

VPNSPA Messages

Error Message %VPNSPA-3-ACEI21BADPARAM: PcpAclAppend: got too many denys for aclId=%d, max is %d Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI22BADPARAM: PcpAclAppend: got out-of-sequence line number %d for aclId=%d Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI23IDINUSE: PcpSpdCreateCme: cannot create Cme with ID=%u: already used Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1794

VPNSPA Messages

Error Message %VPNSPA-3-ACEI24BADPARAM: PcpAclAppend: got invalid ranges for selector set at lineNo=%d, aclId=%d Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI25IDINUSE: PcpAclAppend: got duplicate line number %d for aclId=%d Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI26OUTOFSP: PcpCmeInstallNext: cannot create a new Sp Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1795

VPNSPA Messages

Error Message %VPNSPA-3-ACEI27BADPARAM: PcpManSetFlowKeys: cannot set keys for flow %ld: SA is in the wrong state Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI28IDINUSE: PcpQOpCreSaBegin: cannot create second Sa for flow %ld: conditions for transport adj. are not met Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI29SPDFAILED: PcpCmeInstallNext: cannot install Sp %d with SpdMan Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1796

VPNSPA Messages

Error Message %VPNSPA-3-ACEI2BADPARAM: PcpManUpdateFlow: cannot update flow %ld with invalid ID Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI2NESTOVERFLOW: SpdSaInitTmSaOut: outer outbound Sa %ld of Sa %ld is above nesting limit of %d Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI30BADPARAM: PcpSpdUpdateCme: cannot update already queued Cme %u Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1797

VPNSPA Messages

Error Message %VPNSPA-3-ACEI31BADALENUM: PcpQOpActSaBegin: cannot find access list entry number %d for cmeId=%d Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI32BADPARAM: PcpQOpActSaBegin: cannot delete old %sbound flow %ld while activating %sbound flow %ld Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI33BADPARAM: PcpCmeActivateSa: got invalid lifetime values softSecs=%lu, hardSecs=%lu Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1798

VPNSPA Messages

Error Message %VPNSPA-3-ACEI34BADPARAM: PcpCmeActivateSa: got invalid lifetime values softKBytes=%lu, hardKBytes=%lu Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI35BADPARAM: PcpCmeIntersectSaWithSp: cannot activate flow %ld with selector ranges not intersecting parent Sp Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI36BADSELADDR: PcpQOpActSaBegin: cannot activate per-host flow %ld with addresses %d.%d.%d.%d and %d.%d.%d.%d not included in Sp %d selector sets Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1799

VPNSPA Messages

Error Message %VPNSPA-3-ACEI37OUTOFSEL: PcpQOpActSaBegin: cannot clone selector set to activate per-host flow %ld Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI38BADSELADDR: PcpQOpActSaBegin: cannot activate transport mode flow %ld with addresses %d.%d.%d.%d and %d.%d.%d.%d not included in Sp’s selector sets Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI39BADPARAM: PcpTrInProcess: got invalid opcode %d Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1800

VPNSPA Messages

Error Message %VPNSPA-3-ACEI3NESTOVERFLOW: SpdSaGetXformSeq: outer inbound Sa %ld of Sa %ld is above nesting limit of %d Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI3OUTOFSEL: PcpQOpActSaBegin: cannot allocate selector set for outer Sa in flowId %ld Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI40BADACLID: PcpManCreateCme: cannot create Cme with non-existing access list %u Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1801

VPNSPA Messages

Error Message %VPNSPA-3-ACEI41SPDFAILED: PcpQOpSaActivated: cannot finish activating Sa %ld Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI42QUEUEFULL: PcpCmeActivateSa: cannot activate Sa %ld: queue is full Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI43BADPARAM: PcpAclAppend: got invalid line number %d for ACL %d Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1802

VPNSPA Messages

Error Message %VPNSPA-3-ACEI44QUEUEFULL: PcpSpdCreateCme: cannot create Cme %u (aclId=%u): queue is full Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI45IDNOTINUSE: PcpManDestroyFlowAsync: cannot delete already deleted flow %ld Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI46BADPARAM: PcpQOpActSaBegin: cannot activate non-fully-specified Sa for Cme %d without Acl Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1803

VPNSPA Messages

Error Message %VPNSPA-3-ACEI47BADPARAM: PcpQOpActSaBegin: cannot activate Sa for manual Sp (cmeId=%d,entry=%d), Sa already exists Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI48CMEINUSE: PcpManSetInitMode: cannot set fast init-mode in TcamMan: %ld pending Ops, %ld Flows and %u Cmes already exist or TcamMan is busy Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI49BADPARAM: PcpManQueryFlow: cannot query flow %ld: Sa is not active Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1804

VPNSPA Messages

Error Message %VPNSPA-3-ACEI4BADPARAM: PcpQOpCreSaBegin: got invalid addresses %u.%u.%u.%u and %u.%u.%u.%u for other Sa of flow %ld: expected %u.%u.%u.%u and %u.%u.%u.%u Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI50CMEINUSE: PcpQOpRemCmeBegin: cannot remove Cme %ld: TcamMan is in Init mode Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI51BADPARAM: PcpSpdCreateCme: got invalid flags (manual,dynamic,discover,drop,clear) = (%d,%d,%d,%d,%d), cmeId=%d Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1805

VPNSPA Messages

Error Message %VPNSPA-3-ACEI52IDINUSE: PcpManCreateAcl: cannot process opcode %u for Acl %u in state %u Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI53BADPARAM: PcpManCreateAcl: cannot create Acl with id %u out of range [0,%u] Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI54CMENOTREADY: PcpSpdCreateCme: cannot create Cme %u with Acl %u when Acl state is %u Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1806

VPNSPA Messages

Error Message %VPNSPA-3-ACEI55SPDFAILED: PcpQOpActSaBegin: cannot begin activating Sa %ld for flowId %ld Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI56IDNOTINUSE: PcpManDestroyFlowAsync: cannot delete flow %ld already being deleted Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI57CMEINUSE: PcpManSetInitMode: cannot set normal init-mode in TcamMan: there are pending Flows or Cmes Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1807

VPNSPA Messages

Error Message %VPNSPA-3-ACEI58BADPARAM: PcpManQueryFlow: cannot query flow %ld: parent SP is not active Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI59BADPARAM: PcpCmeActivateSa: cannot activate flow %ld as per-host with subset of Sp as a selector set Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI5BADPARAM: SpdSaActivate: cannot activate Sa %ld, old Sa %ld already has successor Sa %ld Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1808

VPNSPA Messages

Error Message %VPNSPA-3-ACEI5OUTOFSA: PcpQOpCreSaBegin: cannot create new Sa for flow %ld Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI60SPDFAILED: PcpManSaUpdateError: cannot update Flow %ld Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI61BADPARAM: PcpQOpActSaBegin: cannot activate Sa for cmeId=%d, entry=%d with bad spdId=%ld Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1809

VPNSPA Messages

Error Message %VPNSPA-3-ACEI62IDINUSE: PcpQOpCreSaBegin: cannot setup Flow %ld in trans.adj. with outer SA in tunnel mode Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI63CMEINUSE: PcpManActivateFlowAsync: cannot activate flow %ld while using fast policy mode Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI64BADPARAM: PcpQOpActSaBegin: got invalid ranges for selector set of fully-specified flow %ld Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1810

VPNSPA Messages

Error Message %VPNSPA-3-ACEI65BADPARAM: PcpManSetInitMode: got invalid flags 0x%x for setting fast policy mode Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI66NOTREADY: PcpManUpdateFlow: cannot update flow %ld when SA is not active Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI67BADPARAM: PcpSpdCreateSMap: cannot create SMap %u with Acl %u when Acl state is %u Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1811

VPNSPA Messages

Error Message %VPNSPA-3-ACEI68BADPARAM: PcpAclAppend: got invalid flags 0x%x at lineNo=%d, aclId=%d Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI69BADPARAM: PcpManCreateCme: cannot create Cme %u with spdId %u out of range [0,%u] Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI6BADPARAM: PcpTrInProcess: got invalid size %d for opcode %d Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1812

VPNSPA Messages

Error Message %VPNSPA-3-ACEI6OUTOFSEL: SpdSpInstall: cannot compute SP’s permit-SelSets from mixed SelSet list Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI70IDNOTINUSE: PcpManUpdateCme: cannot update non-existing Cme %u Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI71QUEUEFULL: PcpSpdUpdateCme: cannot update Cme %u: queue is full Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1813

VPNSPA Messages

Error Message %VPNSPA-3-ACEI72QUEUEFULL: PcpSpdCreateSMap: cannot create SPD map with mapId %u: queue is full Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI73BADPARAM: PcpSpdCreateSMap: cannot create SPD map with mapId %u out of range [0,%u] Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI74IDINUSE: PcpSpdCreateSMap: cannot create SPD map with mapId %u already in use Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1814

VPNSPA Messages

Error Message %VPNSPA-3-ACEI75TMFAILED: PcpSMapInstall: cannot insert SMap %u with TcamMan Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI76BADPARAM: PcpSpdCreateSMap: cannot create SPD map %u with invalid flags 0x%x Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI77BADPARAM: PcpManCreateSMap: cannot create SPD Map %u using non-existent access list %u Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1815

VPNSPA Messages

Error Message %VPNSPA-3-ACEI78OUTOFSMAP: PcpSpdCreateSMap: cannot create SPD map %u: out of memory Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI79BADPARAM: PcpQOpActSaBegin: cannot activate Sa for cmeId=%d, entry=%d when Cme is not ready Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI7BADPARAM: PcpManSetFlowKeys: cannot set keys for flow %ld: invalid ID Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1816

VPNSPA Messages

Error Message %VPNSPA-3-ACEI7OUTOFSEL: SpdSaTmInstallOut: cannot compute outbound SA’s permit-SelSets from mixed SelSet list Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI80QUEUEFULL: PcpManDestroyFlowAsync: cannot delete flowId %ld: operation queue is full Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI81IDNOTINUSE: PcpQOpDelSaBegin: cannot delete already deleted flow %ld Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1817

VPNSPA Messages

Error Message %VPNSPA-3-ACEI82QUEUEFULL: PcpManRemoveCme: cannot remove Cme with cmeId %u: queue is full Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI83TMFAILED: PcpSpdInitialize: cannot insert SPD %lu with TcamMan Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI84BADPARAM: PcpManCreateSMap: cannot create SPD map %u with spdId %u out of range [0,%u] Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1818

VPNSPA Messages

Error Message %VPNSPA-3-ACEI85OUTOFSMAP: PcpManCreateSpd: cannot create SPD %u: out of memory Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI86IDINUSE: PcpManActivateFlowAsync: cannot activate already active flow %ld Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI87BADPARAM: PcpManCreateFlow: cannot create Flow with id=%ld, max is %ld Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1819

VPNSPA Messages

Error Message %VPNSPA-3-ACEI88IDNOTINUSE: PcpManRemoveSMap: cannot remove non-existing SMap %u Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI89OUTOFCME: PcpSpdCreateCme: cannot allocate new Cme for aclId=%u Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI8SPDFAILED: PcpManSetFlowKeys: cannot set keys for flow %ld using SpdMan Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1820

VPNSPA Messages

Error Message %VPNSPA-3-ACEI90CMEINUSE: PcpQOpRemCmeBegin: cannot remove Cme %ld while in state %d Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI91OUTOFSEL: PcpAclGetSpSelSet: cannot clone deny-SelSets for ACL %d Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI92QUEUEFULL: PcpManCreateFlow: cannot create flowId %ld: operation queue is full Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1821

VPNSPA Messages

Error Message %VPNSPA-3-ACEI93OUTOFSEL: PcpCmeIntersectSaWithSp: cannot clone deny selectors for flow %ld Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI9BADPARAM: PcpManQueryFlow: cannot query flow %ld: invalid ID Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEI9OUTOFSEL: SpdSaActivateOuterSa: cannot create selector set Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1822

VPNSPA Messages

Error Message %VPNSPA-3-ACELOGTEST4: Log test: SEV_ERR Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEPKARSAPRVXCR: PKA: PkaRsaPrivXcrypt() invalid input buffer length %ld Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEPKARSAPUBXCRBUFLEN: PKA: PkaRsaPubXcrypt() invalid input buffer length %ld Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1823

VPNSPA Messages

Error Message %VPNSPA-3-ACEPKASK0LENCROP2: PKA: 0 length crypto operation Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEPKASK0LENCRYOP3: PKA: 0 length crypto operation Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEPKASK0LENOP: PKA: 0 length crypto operation Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1824

VPNSPA Messages

Error Message %VPNSPA-3-ACEPKASK1STFRAGSHRT: PKA: 1st frag too short for crypto operation Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEPKASKDESNOTMUL82: PKA: DES/3DES data length not multiple of 8 Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ACEPKASKDESNOTMULT8: PKA: DES/3DES data length not multiple of 8 Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1825

VPNSPA Messages

Error Message %VPNSPA-3-ACEPKASKNOCRNOAUTH: PKA: Can’t have PKA_CRYPTO_NONE and PKA_HMAC_NONE Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ICPUBADGRESA: Invalid GRE SA - can’t find match. saptr:0x%x Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-3-ICPUPP22: ICMP received, let it go clear newId %d oldid %d Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1826

VPNSPA Messages

Error Message %VPNSPA-3-SPI_NOT_AVAIL: SPI 0x%x is not available Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


VPNSPA-4 Error Message %VPNSPA-4-ACEIPCMPINGPRE: IPC ping (%s): premature ping...awaiting response to previous ping Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-4-ACEIPCMPINGSEQ: IPC ping (%cCPU): seq.# does not match: Expected %d, got %d Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1827

VPNSPA Messages

Error Message %VPNSPA-4-ACEIPCMPINGSKIP: IPC ping (%cCPU): Skipped %d times before receiving reply Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-4-ACEIPCXNOBUF2: ICPU unable to allocate msg buf for Ping Reply: %ld Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-4-ACEIPCXNOBUF3: OCPU unable to allocate msg buf for Ping Reply: %ld Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1828

VPNSPA Messages

Error Message %VPNSPA-4-ACEIPCXPINGNOBUF: %d srcCPU unable to allocate msg buf for Ping Reply in CB: %ld Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-4-ACELOGTEST3: Log test: SEV_WARN Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-4-ACEPKADHRMKGIDBUSY: PkaDhRemoveKeyGroup(): DH group ID %d is busy Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1829

VPNSPA Messages

Error Message %VPNSPA-4-ACETCAMFULLINSMANSP: Full SA insertion for a manual SP. Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-4-ACETCAMPKTNOSA: IPC payload : %x Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-4-ACETCAMPKTNOSP: Packet event for a non-existing SP. Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1830

VPNSPA Messages

Error Message %VPNSPA-4-ACETCAMPKTNOSP1: EarlyPkt Exit1. Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.







1831

VPNSPA Messages

Error Message %VPNSPA-4-ACEXCPUALLOC: IPC: Unable to allocate and send STATFLUSH. Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-4-ACEXCPUALLOC2: IPC: Unable to allocate IPC to set debug flag. Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-4-ACEXCPUALLOC3: IPC: Unable to allocate IPC to start 5840 test. Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1832

VPNSPA Messages

Error Message %VPNSPA-4-ACEXCPUCMRESP3: XcpuCfgMonReqCallback:Global stats...Can’t respond to host. Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-4-ACEXCPUCMRESP4: XcpuCfgMonReqCallback: DataPath Stats....Can’t respond to host. Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-4-ACEXCPUCMRESP5: XcpuCfgMonReqCallback: PerFlow Stats....Can’t respond to host. Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1833

VPNSPA Messages

Error Message %VPNSPA-4-ANTIREPLAYWINDOWDEFAULT: Using default replay window for SA SPI 0x%x Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-4-BULKIP: Wrong type %d size:5d. Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-4-DUMPMEM: 0x%08x: 0x%08x 0x%08x 0x%08x 0x%08x Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1834

VPNSPA Messages

Error Message %VPNSPA-4-EDSDEBUG: Already in map: map[0x%x] newid0x%x flags:0x%x mtu:0x%x spdid:0x%x Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-4-FIPSCHECK2: FIPS RCVD Multi-buffer Packet. Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-4-FIPSCHECK3: FIPS Failed Packet Comparison. Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1835

VPNSPA Messages

Error Message %VPNSPA-4-FIPSCHECK4: FIPS Test Completed Successfully. Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-4-ICPUFRAG1: PktReasmSetAction failed. Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-4-ICPUPP10: Packet src:%d.%d.%d.%d dst:%d.%d.%d.%d proto ESP, but not SA proto! Explanation The received packet’s protocol does not match the security association (SA) protocol.

The SA expects Authentication Header (AH), but the packet uses Encapsulating Security Payload (ESP). Recommended Action Check whether the negotiated protocol matches the configured transform sets

of both peers.

Error Message %VPNSPA-4-ICPUPP11: Packet src:%d.%d.%d.%d dst:%d.%d.%d.%d proto AH, but not SA proto! Explanation The received packet’s protocol does not match the SA protocol. The SA expects ESP, but the packet uses AH. Recommended Action Check whether the negotiated protocol matches the configured transform sets

of both peers.


1836

VPNSPA Messages

Error Message %VPNSPA-4-ICPUPP12: IPPE says IPSec, not pkt src:%d.%d.%d.%d dst:%d.%d.%d.%d proto:%d! Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-4-ICPUPP13: Policy check failed for pkt src:%d.%d.%d.%d dst:%d.%d.%d.%d proto:%d SA index:0x%x Explanation The decrypted packet does not match the security policy. Recommended Action Check whether the security policy on both peers is symmetric.

Error Message %VPNSPA-4-ICPUPP14: Pkt src:%d.%d.%d.%d dst:%d.%d.%d.%d proto:%d match deny; SA index 0x%x Explanation Encrypted packets were received that should have been unencrypted. Recommended Action Check whether the security policy on both peers is symmetric.

Error Message %VPNSPA-4-ICPUPP15: SecInfo 0x%x doesn’t match with SA 0x%x SA index:0x%x Explanation An unexpected and unsupported nesting of SA was detected. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1837

VPNSPA Messages

Error Message %VPNSPA-4-ICPUPP16: Inner proto %d must be IPSec but is not Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-4-ICPUPP2: SaCheckSelectors: Illegal pkt, no valid SA Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-4-ICPUPP3: Illegal pkt dst:%d.%d.%d.%d proto:%d spi:0x%x, no match on SA SPI 0x%x. Explanation No matching SA was found for the received encrypted packet. This message is most

likely to occur during rekeying when the inbound SA is not yet established. Recommended Action If the message persists and packets are being lost, check whether the CPU is overloaded or the crypto engine is oversubscribed.

Error Message %VPNSPA-4-ICPUPP4: Illegal pkt dst:%d.%d.%d.%d proto:%d spi:0x%x, no match on SA dst%d.%d.%d.%d Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1838

VPNSPA Messages


Error Message %VPNSPA-4-ICPUPP8: Illegal clear pkt src:%d.%d.%d.%d dst:%d.%d.%d.%d proto:%d. Explanation Clear packets were received that should have been encrypted. Recommended Action Check whether the remote peer has a correct security policy and SA to encrypt

the packets.

Error Message %VPNSPA-4-ICPUPP9: Packet src:%d.%d.%d.%d dst:%d.%d.%d.%d seq num:0x%x failed replay check last seq num:0x%x for SA:0x%x. Explanation IPsec packets have failed the anti-replay check. A common cause is the use of QoS in

your network. With QoS, lower priority packets can arrive late, missing the anti-replay check window. When this condition occurs, higher level protocols can request retransmission so that functionality is not lost. Time-sensitive protocols, such as voice traffic, might be degraded due to dropped or late packets. Recommended Action Increase the anti-replay window size. If anti-replay checking is not needed,

disable it by removing the HMAC function from the transform set.

Error Message %VPNSPA-4-ICPUSYSIPADDRADD: PktProcAddSysIpAddr: Unable to delete sys IP Addr %d.%d.%d.%d Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-4-ISAUNCA7: PktProcAtnModSas: Mismatch valid flag unca:invalid index:0x%x Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1839

VPNSPA Messages


Error Message %VPNSPA-4-RECOVERYFRAG: Ipfrag: Unable to transmit. CP Lockup Occured. Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-4-SINGLEIP: Wrong type %d size:%d. Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-4-SPDID: XcpuSetVlanSpdId: IpcAllocFailed Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1840

VPNSPA Messages

Error Message %VPNSPA-4-XCPURECOVERY: Error Disabling EDDE EITD DMA Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


VPNSPA-5 Error Message %VPNSPA-5-ACELOGTEST2: Log test: SEV_NOTICE Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-4-ACEPKADHGRPNTALC: PkaDhRemoveKeyGroup(): DH group ID %d not allocated Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1841

VPNSPA Messages

Error Message %VPNSPA-5-ACEPKADHGSBADID: PkaDhGenerateSession(): DH group ID %d not defined Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-5-ACEPKADHGSHIDNOALL: PkaDhGenerateShared:DH session ID %d not allocated Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-5-ACEPKADHGSIDINUSE: PKA: PkaDhGenerateSessionInt: DH session id %ld already in use Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1842

VPNSPA Messages

Error Message %VPNSPA-5-ACEPKADHGSINVID: PKA: PkaDhGenerateSessionInt: invalid DH session id %ld Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-5-ACEPKAINITCMPL: BCM5820: Initialization complete Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-5-ACEPKANOBDESC: PKA: no data buffer descriptors available Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1843

VPNSPA Messages

Error Message %VPNSPA-5-ACEPKANOMOREDHGRPS: PKA: no more DH groups available Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-5-ACEPKAPOSTRSTDELAY: PKA: BCM5820 post reset delay Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-5-ACEPKARESUB: BCM5820: Resubmitting crypto request Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1844

VPNSPA Messages

Error Message %VPNSPA-5-ACEPKARESUBPK: BCM5820: Resubmitting PK request 0x%x Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-5-ACEPKARSACKBITSNMULT: PKA: RSA key create request of %d bits not a multiple of 64 Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-5-ACEPKARSACKMAXBITS: PKA: RSA key create request of %d bits exceeds max of %d bits Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1845

VPNSPA Messages

Error Message %VPNSPA-5-ACEPKARSACKTOOMANY: PKA: Too many RSA key create requests Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-5-ACEPKARSARMPSBUSYID: PKA: can’t remove busy RSA private session %ld Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-5-ACEPKARST: PKA: BCM5820 in reset Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1846

VPNSPA Messages

Error Message %VPNSPA-5-ACEPKARSTCOMPL: BCM5820: Reset complete Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


VPNSPA-6 Error Message %VPNSPA-6-ACEIPCSENDMSGLOCAL: %s send msg buf (local) Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-6-ACEIPCSENDMSGTOOBIG: %s unable to send msg buf (msg too big) Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1847

VPNSPA Messages

Error Message %VPNSPA-6-ACEIPCSENDMSGTOOMANYCLIENTS: %s unable to send msg buf (client id too big) Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-6-ACELOGTEST1: Log test: SEV_INFO Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-6-ACEPKAHWCRNGT: PKA: HW RNG has duplicate data, discarding Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1848

VPNSPA Messages

Error Message %VPNSPA-6-ACEPKAPKNOMCR2: PKA: no Public Key MCRs available Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-6-ACEPKARNG: PKA: seed key is same as the seed, discarding Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-6-ACEPKARNGDUP: PKA: A pseudo-random number was generated twice in succession. 0x%.8lx%.8lx; 0x%p 0x%p idx:0x%x Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1849

VPNSPA Messages

Error Message %VPNSPA-6-ACEPKARNGKAT: PKA: RNG failed KAT Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-6-ACEPKASKNOCRYCTXT: PKA: no Crypto CTXs available Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-6-ACEPKASKNOMCRS: PKA: no Crypto MCRs available Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1850

VPNSPA Messages

VPNSPA-7 Error Message %VPNSPA-7-ACELOGTEST0: Log test: SEV_DEBUG Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-7-ACELOGTESTA: Log test: SEV_DEBUG A Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-7-ACELOGTESTB: Log test: SEV_DEBUG B %d %s Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1851

VRRP Messages

Error Message %VPNSPA-7-ACESHI: git along %d %s Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VPNSPA-7-ACESLO: nuf said Explanation An error was reported by the firmware. Recommended Action Copy the message exactly as it appears on the console or in the system log.


VRRP Messages This section contains Virtual Router Redundancy Protocol (VRRP) messages.

VRRP-4 Error Message %VRRP-4-BADAUTH: Bad authentication from %i, group %d, type %d Explanation Two routers participating in Virtual Router Redundancy Protocol (VRRP) disagree on

authentication. Recommended Action Enter the vrrp authentication command to repair the VRRP authentication

discrepancy between the local system and the system whose IP address is reported.


1852

VSDA Messages

Error Message %VRRP-4-BADAUTHTYPE: Bad authentication from %i, group %d, type %d, expected %d Explanation Two routers participating in VRRP disagree on the valid authentication type. Recommended Action Enter the vrrp authentication command to repair the VRRP authentication

discrepancy between the local system and the system whose IP address is reported.

VSDA Messages This section contains virtual switch dual-active (VSDA) messages.

VSDA-3 Error Message %VSDA-3-ADD_LTL_INDEX_AND_FPOE: Unable to add LTL index 0x%04x and program fpoe for %u/%u Explanation An internal error occurred. Recommended Action No action is required.

Error Message %VSDA-3-GET_IDB_FAILED: Failed to get idb for port cookie (linkchange) Explanation An internal error occurred. Recommended Action No action is required.

Error Message %VSDA-3-ICC_ERR: %s Explanation A failure occurred during the intercard communications (ICC) operation. Recommended Action No action is required.

Error Message %VSDA-3-INVALID_PROC_EVENT: Got event %d:%d Explanation The process was awakened with an invalid event. Recommended Action No action is required.

Error Message %VSDA-3-INVALID_TIMER: Invalid timer %d for interface %s Explanation A timer event occurred, but the timer type was invalid. Recommended Action No action is required.


1853

VSDA Messages

Error Message %VSDA-3-INVALID_TIMER_TYPE: Invalid timer %d processed in %s Explanation A timer event occurred, but the timer type was invalid. Recommended Action No action is required.

Error Message %VSDA-3-LINK_DOWN: Interface %s is no longer dual-active detection capable Explanation The specified link is no longer capable of detecting dual-active situations. Recommended Action No action is required.

Error Message %VSDA-3-PKT_CREATE: Can’t create packet: %s Explanation A dual-active packet cannot be created due to the reason described. Recommended Action No action is required.

Error Message %VSDA-3-PKT_RX: Can’t process the received packet: %s Explanation A dual-active packet cannot be processed due to the reason described. Recommended Action No action is required.

Error Message %VSDA-3-PKT_TX: Can’t send packet: %s Explanation A dual-active packet cannot be sent due to the reason described. Recommended Action No action is required.

Error Message %VSDA-3-PROC_CREATE_FAILED: Unable to create process Explanation The specified process could not be created. Recommended Action No action is required.

Error Message %VSDA-3-QUEUE_CREATE_FAILED: Unable to create watched queue Explanation The specified watched queue could not be created. Recommended Action No action is required.

Error Message %VSDA-3-SET_PORT_LTL_INDEX: Unable to set LTL index for port %s to 0x%x Explanation An internal error occurred Recommended Action No action is required.


1854

VSDA Messages

Error Message %VSDA-3-TIMER_NULL_INTFC: NULL context for timer %d in %s Explanation A timer event occurred, but it specified a NULL interface. Recommended Action No action is required.

Error Message %VSDA-3-TIMER_STARTED: Timer %u on interface %s started Explanation The specified link is now capable of detecting dual-active situations. Recommended Action No action is required.

Error Message %VSDA-3-TX_THREAD_FAILURE: Thread %u: %s Explanation This is a general thread error message. Recommended Action No action is required.

Error Message %VSDA-3-VSDA_SCP_BAD_STATUS: SCP operation ([chars]) return status [dec] Explanation A non-blocking SCP operation of the specified type failed for dual-active fast-hello on

a line card Recommended Action No action is required.

Error Message %VSDA-3-VSDA_SCP_PAK_FAIL: Unable to get SCP packet for opcode [dec], operation [dec] Explanation Packet allocation failed for sending an SCP message to do the specified operation Recommended Action No action is required.

Error Message %VSDA-3-VSDA_SCP_SEND_FAIL: Unable to send SCP message for opcode [dec], operation subop [dec] Explanation Packet send failed for the SCP message to perform the specified operation Recommended Action No action is required.

VSDA-5 Error Message %VSDA-5-LINK_UP: Interface %s is now dual-active detection capable Explanation The specified link is now capable of detecting dual-active situations. Recommended Action No action is required.


1855

VSEC Messages

VSEC Messages This section contains VLAN security violation messages.

VSEC-4 Error Message %VSEC-4-VLANACCESSLOGRF: FAILED to set VACL-LOG rate limiter. Is strongly suggested to rate limit when using this feature Explanation The configuration for the VACL logging rate limiter has failed. Recommended Action Determine the rate limiter usage, free some resources if possible, and then try

to set the rate limiter again.

VS_GENERIC Messages This section contains virtual switch (VS) messages.

VS_GENERIC-1 Error Message %VS_GENERIC-1-VS_HA_PS_NOT_SUPPORTED: Chassis Standby is not supported in the current release. Forcing the chassis standby in switch [dec] slot [dec] to drop to rommon Explanation The chassis standby function is not supported in this release. Recommended Action No action is required.

Error Message %VS_GENERIC-1-VS_HA_PS_RUNNING_LEGACY_IMAGE: Chassis Standby in switch [dec] slot [dec] is running non Virtual Switch image. Please remove the chassis standby. Explanation The standby chassis is running an image that does not support virtual switch. Recommended Action Remove the standby chassis.


1856

VS_GENERIC Messages

VS_GENERIC-3 Error Message %VS_GENERIC-3-VS_ADD_VSL_ENTRY_FAILED: Add VSL configured port for vslot [int] port [int] failed. Exceed port member count limit. Explanation An attempt to add an entry for (vslot, port) to the VSL configured port list failed because

the port member count limit was exceeded. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VS_GENERIC-3-VS_BOOLEAN_CREATE_FAILED: Unable to create watched boolean "[chars]" Explanation The creation of the specified watched boolean failed. Recommended Action No action is required.

Error Message %VS_GENERIC-3-VS_ENQUEUE_FAILED: Unable to enqueue to [chars] queue Explanation An internal error occurred that prevented a message from being enqueued to the

specified process. The packet was dropped. Recommended Action No action is required.

Error Message %VS_GENERIC-3-VS_ICC_PAK_FAIL: Unable to get ICC packet for opcode [dec], operation [dec] Explanation A packet allocation failed for sending an ICC message to do the specified operation. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1857

VS_GENERIC Messages

Error Message %VS_GENERIC-3-VS_ICC_RESP_PAK_NULL: Failed to obtain response packet Explanation The response packet pointer is NULL. This could be due to an insufficient memory

condition on the response packet sending side or to a failure to get an IPC message on the receiving side. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VS_GENERIC-3-VS_NO_PAGP_CHANNEL_HWIDB: No PAgP channel hwidb for PAgP group [dec] Explanation An internal error occurred. Port Aggregation Protocol (PAgP) could not find the

hardware interface descriptor block (IDB) for this channel group. Recommended Action No action is required.

Error Message %VS_GENERIC-3-VS_PROC_CREATE_FAILED: Unable to create process "[chars]" Explanation The creation of the specified process failed. Recommended Action No action is required.

Error Message %VS_GENERIC-3-VS_QUEUE_CREATE_FAILED: Unable to create queue "[chars]" Explanation The creation of the specified queue failed. Recommended Action No action is required.

Error Message %VSL-3-VSL_PROC_ARGS_FAILED: Unable to process arguments "[chars]" Explanation The processing of the specified arguments failed. Recommended Action No action is required.


1858

VSL Messages

VS_GENERIC-5 Error Message %VS_GENERIC-5-VS_CONFIG_DIRTY: Configuration has changed. [chars] Explanation An attempt to reload was ignored due to a configuration change. Recommended Action No action is required.

VSL Messages This section contains virtual switch link (VSL) messages.

VSL-2 Error Message %VSL-2-VSL_STATUS: -======== VSL is [chars] ========Explanation The VSL status has changed to active (up) or inactive (down). Recommended Action No action is required.

VSL-3 Error Message %VSL-3-PRE_PEER_COMM_TIMEOUT: A timeout occurred while waiting for vsl_pre_peer_comm_op_done Explanation All applications failed to respond within the specified time. Operation is continuing. Recommended Action No action is required.

Error Message %VSL-3-TROUBLESHOOT: Structure type [int]: [chars] Explanation The specified structure could not be created to save VSL troubleshooting information

when VSL goes down. Recommended Action No action is required.

Error Message %VSL-3-VSL_ICC_PAK_FAIL: Unable to get ICC packet for opcode [dec], operation [dec] Explanation Packet allocation failed for sending an ICC message to do the specified operation. Recommended Action No action is required.


1859

VSL Messages

Error Message %VSL-3-VSL_ICC_SEND_FAIL: Unable to send ICC message for opcode [dec], operation subop [dec] Explanation Packet send failed for the ICC message to perform the specified operation. Recommended Action No action is required.

Error Message %VSL-3-VSL_INST_CREATE_FAIL: Failed to create VSLP instance for VSL Explanation Unable to create a VSLP instance for VSL. Recommended Action No action is required.

Error Message %VSL-3-VSL_INTERNAL_ERROR: [chars], port [dec]/[dec] Explanation An internal error occurred. Recommended Action No action is required.

Error Message %VSL-3-VSL_INVALID_PROC_EVENT: Got event [dec]:[dec] Explanation An invalid event activated the process. Recommended Action No action is required.

Error Message %VSL-3-VSL_INVALID_TIMER_CTXT: NULL or invalid timer context Explanation A timer expiration event was received with NULL or invalid context information. Recommended Action No action is required.

Error Message %VSL-3-VSL_INV_PORT_STATUS_CHANGE: Link status change ([chars]) on non-VSL port [dec]/[dec] Explanation A link status change was detected on a port that is not a VSL member. Recommended Action No action is required.

Error Message %VSL-3-VSL_MAX_PORTS: Cannot configure more than [dec] ports Explanation A port could not be added to the VSL because the maximum number of ports in the VSL

has been reached. Recommended Action No action is required.


1860

VSL Messages

Error Message %VSL-3-VSL_MODE_BAD_STATUS: VSL-mode programming ([dec]) returned status [dec] Explanation A VSL-mode operation of the specified type failed on a VSL line card. Recommended Action No action is required.

Error Message %VSL-3-VSL_PORT_CFG_MOD_OFFLINE: Module [dec] offline when port [dec] added to VSL Explanation A port was added to the VSL when the corresponding line card was offline. Recommended Action No action is required.

Error Message %VSL-3-VSL_PROC_CREATE_FAILED: Unable to create process "[chars]" Explanation The specified process could not be created for an unknown reason. Recommended Action No action is required.

Error Message %VSL-3-VSL_REGISTRY_ADD_FAIL: [chars] registry addition failed Explanation An addition to the given registry failed during initialization. Recommended Action No action is required.

Error Message %VSL-3-VSL_RESERVED_LTL_FAIL: Unable to allocate reserved LTL indices Explanation Platform-VSLP for VSL uses a number of reserved Local Target Logic (LTL) indices

allocated by the LTL Manager. Because this allocation failed, the system can no longer function. Recommended Action No action is required.

Error Message %VSL-3-VSL_ROLE_RES_BOOL_FAIL: Unable to create watched boolean for role resolution Explanation A watched boolean for role resolution could not be created. Recommended Action No action is required.

Error Message %VSL-3-VSL_SCP_BAD_STATUS: SCP operation ([chars]) return status [dec] Explanation A nonblocking SCP operation of the specified type. failed on a VSL line card Recommended Action No action is required.


1861

VSL Messages

Error Message %VSL-3-VSL_SCP_BLK_SEND_FAIL: [chars] for SCP opcode [dec], subopcode [dec] Explanation Failed to do the specified operation when sending the specified SCP message through a

blocking call. Recommended Action No action is required.

Error Message %VSL-3-VSL_SCP_FAIL: SCP operation failed Explanation A nonblocking SCP operation failed on a VSL line card. Recommended Action No action is required.

Error Message %VSL-3-VSL_SCP_PAK_FAIL: Unable to get SCP packet for opcode [dec], operation [dec] Explanation Packet allocation failed for sending an SCP message to do the specified operation. Recommended Action No action is required.

Error Message %VSL-3-VSL_SCP_SEND_FAIL: Unable to send SCP message for opcode [dec], operation subop [dec] Explanation Packet send failed for the SCP message to perform the specified operation. Recommended Action No action is required.

Error Message %VSL-3-VSL_UNCFG_BAD_PORT: Unconfigure on non-VSL port [dec]/[dec] Explanation An attempt was made to unconfigure a port from the VSL, but the port is not part of the

VSL. Recommended Action No action is required.

Error Message %VSL-3-VSL_UNCFG_FAILED: Unconfigure on VSL port [dec]/[dec] failed: [chars] Explanation While unconfiguring a VSL port, the specified operation failed. Recommended Action No action is required.


1862

VSL_BRINGUP Messages

VSL-5 Error Message %VSL-5-VSL_CNTRL_LINK: New VSL Control Link [chars] Explanation A new VSL control link was detected on a VSL line card. Recommended Action No action is required.

VSL_BRINGUP Messages This section contains virtual switch link (VSL) bringup messages.

VSL_BRINGUP-3 Error Message %VSL_BRINGUP-3-MODULE_DOWN: Failed to bring up VSL module in slot [dec] switch [dec]. [chars] Explanation The bringup of the specified module failed due to the reason indicated. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VSL_BRINGUP-3-NO_MODULE_UP: Failed to bring up any VSL modules on switch [dec] Explanation An attempt to bring up any VSL line cards or supervisor engines failed due to an internal




1863

VSL_BRINGUP Messages

Error Message %VSL_BRINGUP-3-PROC_CREATE_FAILED: Unable to create process "[chars]" Explanation The creation of the specified process failed. Recommended Action No action is required.

Error Message %VSL_BRINGUP-3-VS_OVERSUB_MODECHANGE_FAIL: Switching mode failed on Switch %d module %d port-group %d Explanation The VSL bringup process was unable to change the switching mode of the indicated

module. Recommended Action Copy the message exactly as it appears on the console or in the system log.


VSL_BRINGUP-6 Error Message %VSL_BRINGUP-6-MODULE_UP: VSL module in slot [dec] switch [dec] brought up Explanation The specified VSL module was brought up successfully. Recommended Action No action is required.

Error Message %VSL_BRINGUP-6-NOT_VS_CAPABLE_EARL: Supervisor card does not have Virtual Switch capable EARL daughter board Explanation The supervisor engine card does not have an EARL daughterboard capable of running

in virtual switch mode. An EARL 7.5 or above is required. Recommended Action Use a supported supervisor engine card for a virtual switch system.

Error Message %VSL_BRINGUP-6-PREEMPT_DISABLED: Preemption suppressed due to first time VS conversion Explanation A higher priority standby switch will not preempt a lower priority active switch when a

virtual switch (VS) system is converted for the first time from a standalone configuration. Recommended Action Use the switch accept mode virtual command to merge the standby VSL

configuration first. Then, if desired, use the redundancy force-switchover command to make the other switch active.


1864

VSLP Messages

Error Message %VSL_BRINGUP-6-SUP720_VS_NOT_SUPPORT: No support for Virtual Switch on SUP720. Booting up in Standalone mode Explanation The Supervisor Engine 720 is virtual switch capable. However, Cisco does not officially

support virtual switch mode on the Supervisor Engine 720. Recommended Action No action is required.

VSLP Messages This section contains Virtual Switch Link Protocol (VSLP) messages.

VSLP-2 Error Message %VSLP-2-VSL_DOWN: [chars] Explanation VSL status changed to DOWN. More detail is provided in the message. Recommended Action No action is required.

VSLP-3 Error Message %VSLP-3-ICC_ERR: [chars] Explanation A failure occurred during the inter-card communications (ICC) operation. Recommended Action No action is required.

Error Message %VSLP-3-ISSU_ERROR: %s Explanation The virtual switch link protocol (VSLP) was unable to perform an ISSU operation. Recommended Action No action is required.

Error Message %VSLP-3-PKT: VSLP packet error: [chars] Explanation A VSLP packet error occurred for the reason described. Recommended Action No action is required.

Error Message %VSLP-3-PKT_CREATE: Can’t create packet: [chars] Explanation A VSLP packet cannot be created due to the reason described. Recommended Action No action is required.


1865

VSLP Messages

Error Message %VSLP-3-PKT_RX: Can’t process the received packet: [chars] Explanation A VSLP packet cannot be processed due to the reason described. Recommended Action No action is required.

Error Message %VSLP-3-PKT_TX: Can’t send packet: [chars] Explanation A VSLP packet cannot be sent due to the reason described. Recommended Action No action is required.

Error Message %VSLP-3-REGISTRY_ADD_ERR: Failure in adding to [chars] registry Explanation A function could not be added to the registry. Recommended Action No action is required.

Error Message %VSLP-3-RRP_ERR_MSG: [chars] Explanation The VSLP role resolution protocol detected an error. Recommended Action No action is required.

Error Message %VSLP-3-RRP_INSTANCE_OUT_OF_BOUNDS: Instance value [dec] is outside the expected range Explanation The instance value received is out of bounds. Recommended Action No action is required.

Error Message %VSLP-3-RRP_INVALID_INSTANCE: Instance value [dec] is invalid Explanation The instance value received corresponds to an invalid instance. Recommended Action No action is required.

Error Message %VSLP-3-RRP_MEMORY_ALLOC_ERR: (Instance:[dec], Peer:[dec]): No memory available for [chars] Explanation The VSLP could not obtain the requested memory. Recommended Action No action is required.

Error Message %VSLP-3-RRP_PEER_INFO_ERR: (Instance:[dec], Peer:[dec]): Peer [chars] Explanation The role resolution protocol has encountered an error associated with this peer. Recommended Action No action is required.


1866

VSLP Messages

Error Message %VSLP-3-RRP_PEER_INSTANCE_ERROR: (Instance:[dec], Peer:[dec], Up:[dec], Valid:[dec], Switch:[dec], Role:[chars], PeerRole:[chars]): [chars] Explanation An error occurred pertaining to the instance and peer group specified. Recommended Action No action is required.

Error Message %VSLP-3-RRP_PEER_SUP_PSLOT_ERR: save_rrp_tlv_data->peer_sup_pslot:[int], my_sup_pslot:[int] Explanation The role resolution protocol detected a difference in the peer supervisor engine pslot. Recommended Action No action is required.

Error Message %VSLP-3-RRP_RESERVED_PEER_ERR: (Instance:[dec], Peer:[dec]): Reserved peer [dec] [chars] Explanation The role resolution protocol has detected an error related to the reserved peer. Recommended Action No action is required.

Error Message %VSLP-3-RRP_SESSION_ID_ERR: (Instance:[dec], Peer:[dec]): Session id mismatch. Expected [dec], got [dec] Explanation The VSLP role resolution protocol has detected a session ID mismatch. Recommended Action No action is required.

Error Message %VSLP-3-RRP_SLOT_PORT_ERR: (Slot:[dec], Port:[dec]): [chars] Explanation The role resolution protocol has detected an error related to the specified slot and port. Recommended Action No action is required.

Error Message %VSLP-3-RRP_TIMER_CREATE_FAIL: (Instance:[dec], Peer:[dec]): Unable to create RRP timer Explanation The role resolution protocol was unable to create a timer for the specified instance and

peer. Recommended Action No action is required.

Error Message %VSLP-3-RRP_UNEXPECTED_ROLE: Unexpected roles. Local role = [chars], Peer role = [chars] Explanation The role resolution protocol has encountered inconsistent role information. Recommended Action No action is required.


1867

VSLP Messages

Error Message %VSLP-3-RRP_VALUE_ERR: [chars]: [dec] Explanation The role resolution protocol has encountered an unknown value. Recommended Action No action is required.

Error Message %VSLP-3-VSLP_BOOLEAN_CREATE_FAILED: Unable to create watched boolean "[chars]" Explanation The specified watched boolean could not be created. Recommended Action No action is required.

Error Message %VSLP-3-VSLP_INST_INVALID_CAP: Invalid capability [dec] for VSLP instance [dec] Explanation A VSLP capability was requested that is beyond the current list of supported

capabilities. Recommended Action No action is required.

Error Message %VSLP-3-VSLP_INST_OUT_OF_RANGE_CREATE: Cannot create VSLP instance [dec] Explanation A VSLP instance could not be created for the switch ID because it is not within the

acceptable range. Recommended Action No action is required.

Error Message %VSLP-3-VSLP_INST_OUT_OF_RANGE_DESTROY: Cannot destroy VSLP instance [dec] Explanation The given VSLP instance could not be destroyed because it is not within the acceptable

range. Recommended Action No action is required.

Error Message %VSLP-3-VSLP_LMP_DOMAIN_MISMATCH: Domain ID in probe packet from peer %d is not the same as local Domain ID %d. The packet was dropped. Explanation The virtual switch domain ID in a probe packet from the peer is not the same as the local

domain ID. The packet was dropped. Recommended Action Investigate and correct this misconfiguration.

Error Message %VSLP-3-VSLP_LMP_FAIL_REASON: [chars]: [chars] Explanation This message displays the reason for a link to leave the LMP operational state. Recommended Action No action is required.


1868

VSLP Messages

Error Message %VSLP-3-VSLP_LMP_FLAG_SET: Incorrect flag value (0x%x) on port %d/%d Explanation The system detected an unexpected value for the flag field of a VSL link. This condition

is caused by an internal software error. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show vslp lmp summary, and show vslp lmp fsm commands and your pertinent troubleshooting logs.

Error Message %VSLP-3-VSLP_LMP_FSM_INVALID_TIMER: Invalid timer [dec] for port [dec]/[dec] in [chars] operation Explanation A timer event occurred, but the timer type was invalid. Recommended Action No action is required.

Error Message %VSLP-3-VSLP_LMP_FSM_NULL_CTXT: NULL context for FSM action [chars] Explanation An FSM action routine was invoked, but with a NULL context argument. Recommended Action No action is required.

Error Message %VSLP-3-VSLP_LMP_FSM_TIMER_BAD_CTXT: Invalid or NULL context for timer [dec] in [chars] operation Explanation A timer event occurred, but the FSM infrastructure passed to the handler a context pointer that is currently not in use or is NULL. Recommended Action No action is required.

Error Message %VSLP-3-VSLP_LMP_INVALID_PROC_EVENT: Got event [dec]:[dec] Explanation An invalid event woke up the process. Recommended Action No action is required.

Error Message %VSLP-3-VSLP_LMP_MAX_PGS: Cannot create more thatn [dec] LMP peer groups Explanation The number of LMP peer groups has reached the maximum per-LMP instance. Recommended Action No action is required.


1869

VSLP Messages

Error Message %VSLP-3-VSLP_LMP_MAX_PORTS: Cannot configure more than [dec] ports Explanation LMP could not be configured on a port because the maximum number of ports per-LMP

instance has been reached. Recommended Action No action is required.

Error Message %VSLP-3-VSLP_LMP_PG_CREATE_FAIL: Unable to create PG ([enet]:[dec]) for port [dec]/[dec] Explanation The peer group could not be created for the given port. This port is the first port

connected to this peer to move into the operational state. Recommended Action No action is required.

Error Message %VSLP-3-VSLP_LMP_PG_GET_FAIL: Unable to get PG (%e) for port %d/%d Explanation The system was unable to get the peer group for the given port. Recommended Action No action is required.

Error Message %VSLP-3-VSLP_LMP_PG_INCONSISTENT: PG [enet]:[dec] should have [dec] links, but none found Explanation A link has left a peer group that seems to have more links, but no other links were found. Recommended Action No action is required.

Error Message %VSLP-3-VSLP_LMP_PG_NO_CTRL_LINK: No control link for preferred PG [dec] Explanation A peer group with no control link has been set as the preferred peer group. Recommended Action No action is required.

Error Message %VSLP-3-VSLP_LMP_PG_OUT_OF_RANGE: Peer group [dec] is out of range Explanation A peer group has been passed to an API that is out of range. Recommended Action No action is required.

Error Message %VSLP-3-VSLP_LMP_RX_BAD_FIRST_TLV: Bad first TLV ([dec]) in received packet on port [dec]/[dec] Explanation The received LMP packet was dropped because its first type-length value (TLV) was not

a Probe TLV or a Hello TLV. Recommended Action No action is required.


1870

VSLP Messages

Error Message %VSLP-3-VSLP_LMP_RX_BAD_INTERFACE: Incorrect port [dec]/[dec] for received packet Explanation A received LMP packet was dropped because it had incorrect received packet

information. The LMP packet may have been received from an interface on which VSLP is not enabled. Recommended Action No action is required.

Error Message %VSLP-3-VSLP_LMP_RX_BAD_TLV_COUNT: Bad TLV count in received packet ([dec]) Explanation A received LMP packet was dropped because it had an incorrect number of type-length

values (TLVs). This includes the case where no TLVs are received. Recommended Action No action is required.

Error Message %VSLP-3-VSLP_LMP_RX_PLATFORM_REJECT: Platform TLV rejected for receieved [chars] packet Explanation A received LMP packet was dropped because one or more platform type-length values

(TLVs) were rejected. Recommended Action No action is required.

Error Message %VSLP-3-VSLP_LMP_RX_QUEUE_FAIL: Unable to enqueue received packet for processing Explanation An internal error occurred that prevented a packet from being enqueued to the packet

processing queue. The packet was dropped. Recommended Action No action is required.

Error Message %VSLP-3-VSLP_LMP_RX_XFORM: Failed to transform received %s packet Explanation An ISSU transformation failed on the received packet. The packet was dropped Recommended Action No action is required.

Error Message %VSLP-3-VSLP_LMP_SAME_SWITCH_ID: Switch id in probe packet is the same as the local switch id %d. The packet was dropped. Explanation The switch ID in a probe packet from the peer is the same as the local switch ID. The

packet was dropped. Recommended Action Investigate and correct this misconfiguration


1871

VSLP Messages

Error Message %VSLP-3-VSLP_NULL_ENTRY: Null [chars] entry in [chars] operation Explanation A NULL entry was passed in the specified operation. Recommended Action No action is required.

Error Message %VSLP-3-VSLP_PROC_CREATE_FAILED: Unable to create process "[chars]" Explanation The specified process could not be created due to unknown reasons. Recommended Action No action is required.

Error Message %VSLP-3-VSLP_QUEUE_CREATE_FAILED: Unable to create watched queue "[chars]" Explanation The specified watched queue could not be created due to unknown reasons. Recommended Action No action is required.

Error Message %VSLP-3-VSLP_REGISTRY_ADD_FAIL: [chars] registry addition failed Explanation The given registry addition failed during initialization. Recommended Action No action is required.

Error Message %VSLP-3-VSLP_THREAD_CREATE_FAILURE: tid %u/intvl %u: %s Explanation VSLP transmit thread creation failed for the specified reason. Recommended Action No action is required.

Error Message %VSLP-3-VSLP_THREAD_FAILURE: tid %u: %s Explanation A general VSLP transmit thread failure occurred for the specified reason. Recommended Action No action is required.

VSLP-4 Error Message %VSLP-4-ASIC_DUMP: [chars] Explanation The VSL physical link is up and the role was not resolved in RRP. Recommended Action No action is required.


1872

VSLP Messages

Error Message %VSLP-4-VSL_PREEMPT_TIMER: Preempt timer configured to [dec] minutes. Standby will takeover as active in [dec] minute(s) Explanation The preempt timer is configured on the standby unit. The standby unit will become

active after the timer expires. Recommended Action No action is required.

VSLP-5 Error Message %VSLP-5-RRP_ACTIVE_PEER_DOWN: Communication to active peer went down. Triggering switchover... Explanation The role resolution protocol has received an indication that communication with the

active peer has gone down. This condition will trigger a switchover. Recommended Action No action is required.

Error Message %VSLP-5-RRP_RT_CFG_CHG: Configured [chars] value is different from operational value. Change will take effect after config is saved and switch [dec] is reloaded. Explanation Role resolution protocol configuration changes by user Recommended Action No action is required.

Error Message %VSLP-5-RRP_MSG: [chars] Explanation A role resolution protocol event was received. Recommended Action No action is required.

Error Message %VSLP-5-RRP_NO_PEER: No VSLP peer found. Resolving role as Active Explanation Because VSLP could not communicate with any peer, it will boot up as active. Recommended Action No action is required.

Error Message %VSLP-5-RRP_PEER_TIMEOUT: VSLP peer timer expired without detecting peer. Resolving role as Active Explanation Because the role resolution protocol could not communicate with any peer before the

peer timer expiry, it will boot up as active. Recommended Action No action is required.


1873

VSLP Messages

Error Message %VSLP-5-RRP_PREEMPT: [chars] Switch [int]: Priority [int]: Preempt [chars] Switch [int]: Priority [int]: Preempt [chars]

Explanation Displays preemption configuration. Recommended Action No action is required.

Error Message %VSLP-5-RRP_PREEMPT_IGNORE: %s Explanation The preemption configuration is ignored due to unsaved configurations. Recommended Action No action is required.

Error Message %VSLP-5-RRP_ROLE_RESOLVED: Role resolved as [chars] by VSLP Explanation The role resolution protocol has communicated with a peer and has resolved its role. Recommended Action No action is required.

Error Message %VSLP-5-RRP_RT_CFG_CHANGE: [chars] Explanation The role resolution protocol configuration has been changed by a user. Recommended Action No action is required.

Error Message %VSLP-5-RRP_UNSAVED_CONFIG: Ignoring system reload since there are unsaved configurations. Please save the relevant configurations Explanation The role resolution protocol received an indication that the system must be reloaded due

to a role change from active to standby. No reload will occur because unsaved configurations exist and would be lost. Recommended Action No action is required.

Error Message %VSLP-5-RRP_WR_MEM_PROGRESS: Ignoring system reload since config save operation is in progress. Please wait till the configs are saved Explanation The role resolution protocol (RRP) received an indication that a system reload is

required due to a role change from active to standby. Since a configuration save operation is in progress, the system will not be reloaded. Recommended Action No action is required.


1874

VSLP_ISSU Messages

Error Message %VSLP-5-VSL_UP: [chars] Explanation VSL status has changed to UP, with more details provided in message. Recommended Action No action is required.

VSLP-6 Error Message %VSLP-6-ACTIVE: [chars] Explanation Displays the state of the virtual switch active supervisor engine. Recommended Action No action is required.

Error Message %VSLP-6-STANDBY: [chars] Explanation Displays the state of the virtual switch standby supervisor engine. Recommended Action No action is required.

VSLP_ISSU Messages This section contains Virtual Switch Link Protocol (VSLP) in-service software upgrade (ISSU) messages.

VSLP_ISSU-3 Error Message %VSLP_ISSU-3-CAP_RESULT_INCOMPAT: VSLP ISSU client capability exchange result incompatible. Explanation Based on the results of the capability exchange, the VSLP ISSU client is not compatible with the peer. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1875

VSLP_ISSU Messages

Error Message %VSLP_ISSU-3-INIT: VSLP ISSU client initialization failed at %s, error %s Explanation The VSLP ISSU client could not be initialized. This condition will cause a catastrophic

failure when an ISSU upgrade or downgrade is performed. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VSLP_ISSU-3-INTERNAL: An internal error occurred: %s Explanation A software error occurred during the specified operation. Recommended Action No action is required.

Error Message %VSLP_ISSU-3-INVALID_PROC_EVENT: Got event %d:%d Explanation The process was awakened with an invalid event. Recommended Action No action is required.

Error Message %VSLP_ISSU-3-ISSU_ERROR: %s failed with error code %d for peer %e Explanation An ISSU application program interface (API) was unable to perform an operation for

the VSLP layer. The message includes the error code from the ISSU library. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show issu fsm commands and your pertinent troubleshooting logs.


1876

VSLP_ISSU Messages

Error Message %VSLP_ISSU-3-MSG_NOT_OK: VSLP ISSU client message %s is not compatible Explanation The VSLP ISSU client received an incompatible message from the peer unit. Since the

message is not compatible, it cannot be processed by this unit. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VSLP_ISSU-3-NEGO_FAILED: VSLP ISSU start nego session with peer %e with error code %s Explanation The VSLP ISSU could not start its negotiation process. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show issu fsm commands and your pertinent troubleshooting logs.

Error Message %VSLP_ISSU-3-NULL_ENTRY: Null %s entry in %s Explanation A NULL entry was passed in the specified operation. Recommended Action No action is required.

Error Message %VSLP_ISSU-3-PROC_CREATE_FAILED: Unable to create process Explanation The specified process could not be created. Recommended Action No action is required.

Error Message %VSLP_ISSU-3-QUEUE_CREATE_FAILED: Unable to create watched queue Explanation The specified watched queue could not be created. Recommended Action No action is required.


1877

VSLP_ISSU Messages

Error Message %VSLP_ISSU-3-RX_BAD_INTERFACE: Incorrect port %d/%d for received packet Explanation A VSLP ISSU packet was received that contains incorrect received packet info. This

VSLP ISSU packet may have been received from an interface on which VSLP is not enabled. The packet was dropped. Recommended Action No action is required.

Error Message %VSLP_ISSU-3-RX_QUEUE_FAIL: Unable to enqueue received packet for processing Explanation An internal error occurred that prevented a packet from being enqueued to the packet

processing queue for processing. The packet was dropped. Recommended Action No action is required.

Error Message %VSLP_ISSU-3-SEND_FAILED: VSLP ISSU client failed to send a negotiation message Explanation The VSLP ISSU client could not send a session negotiation message to the peer. When

a problem occurs in the negotiation, the peer switch unit cannot be brought up as standby, resulting in two active switches in the system. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VSLP_ISSU-3-SESSION: VSLP ISSU client %s Explanation The VSLP ISSU client detected an error during a session negotiation with the peer unit.

As a result, the peer switch cannot be brought up as standby and two switches will be active in the system. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1878

VS_MERGE Messages


Error Message %VSLP_ISSU-3-TRANSFORM: VSLP ISSU client %s transform failed for %s message, error %s Explanation The VSLP ISSU client could not transform the message. If the transmit transformation

failed, the VSLP message cannot be sent to the standby unit. If the receive transformation failed, the VSLP message cannot be processed on the standby unit. In either case, the VSLP ISSU client state will not be identical with the active unit. Recommended Action Copy the message exactly as it appears on the console or in the system log.


VS_MERGE Messages VS_MERGE-3 Error Message %VS_MERGE-3-SAME_ACT_STDBY_PO: Invalid configuration - standby VSL port channnel number [int] is same as active VSL port channel. Auto-merge process is aborted. Explanation This is an invalid configuration. Active and standby must use different VSL port channel numbers. Auto-merge process is aborted. If this situation happens, standby switch will come up in RPR mode. Recommended Action Use different port channel numbers for active and standby VSL port channels

and its members. This change can be done by bringing down all VSL links so that standby switch comes up as active switch. Then enter configuration mode and make changes to use different VSL port channel number for local VSL port members. Once completed, reload this switch to start auto-merge procedure again.


1879

VS_MOD_PROV Messages

VS_MERGE-4 Error Message %VS_MERGE-4-STDBY_VSL_PO_EXIST: Overwriting existing port channel [int] with standby VSL port channel Explanation There exists a port channel that uses the same channel number as standby VSL port

channel. Overwrite the existing port channel configuration with standby VSL port channel configuration. Recommended Action If the existing port channel configuration is required, then reconfigure the port channel and its related configuration with a different port channel number

VS_MERGE-6 Error Message %VS_MERGE-6-SAVE_MERGED_CFG: Saving merged configuration... Explanation The merged configuration is being copied to startup-config. Recommended Action No action is required.

VS_MOD_PROV Messages This section contains virtual switch module provisioning messages.

VS_MOD_PROV-3 Error Message %VS_MOD_PROV-3-AUTO_ADD_SLOT_FAILED: Auto module provision add failed for chassis [dec] slot [dec] Explanation A call to add module provisioning information to a red-black tree (RBTree) has failed. Recommended Action No action is required.

Error Message %VS_MOD_PROV-3-AUTO_REM_SLOT_FAILED: Auto module provision remove failed for chassis [dec] slot [dec] Explanation Remove module provisioning slot information failed. Recommended Action Reproduce the issue after execute ’debug switch virtual ridprom all’CLI on

both active RP and SP before bringing up standby chassis. Collect the debug trace information from console.


1880

VS_MOD_PROV Messages

Error Message %VS_MOD_PROV-3-ICC_PAK_NULL: Pak pointer for icc msg is NULL Explanation An ICC packet buffer pointer could not be obtained. Recommended Action No action is required.

Error Message %VS_MOD_PROV-3-MSGBUF_PTR_NULL: Data buffer pointer is NULL Explanation A message or data buffer pointer could not be obtained. Recommended Action No action is required.

Error Message %VS_MOD_PROV-3-MTU_ZERO: MTU size is zero due to ISSU session negotiation failure. Explanation ISSU return negotiated message size equal to zero for this session. Most likely, there is an issue with IPC transport mechanism that causes ISSU negotiated message to time out. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %VS_MOD_PROV-3-NO_AUTO_PROV_PROC: Unable to create VS Auto Module Prov process. Explanation The virtual switch automatic module provisioning process could not be created. Recommended Action No action is required.

Error Message %VS_MOD_PROV-3-NO_AUTO_PROV_WB: Unable to create watched boolean(s). vs_auto_prov_add_wb = , vs_auto_prov_ha_wb = Explanation The specified watched booleans could not be created. Recommended Action No action is required.

Error Message %VS_MOD_PROV-3-SEND_PROV_DATA_FAILED: Sending of module provision info to ACTIVE failed. Explanation The ICC sending of module provisioning information from the standby module to the

active module failed. Recommended Action No action is required.


1881

VSPA Messages

VSPA Messages This section contains VPN Services Port Adapter (VSPA) messages.

VSPA-3 Error Message %VSPA-3-FIPSERROR: FIPS POST Failed. Explanation The power-on self test (POST) failed. The crypto engine is disabled. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %VSPA-3-HARDWARE_ERR: WS-IPSEC-3 Error: %s Explanation A hardware error occurred on the WS-IPSEC-3, causing an interrupt. The module will

automatically reload in the case of an unrecoverable error. Recommended Action Copy the error message (and any recent error messages) as it appears on the

console. In case of a WS-IPSEC-3 crash, collect the crashinfo file from the sup-bootdisk. Contact your Cisco technical support representative and provide the gathered information.

VSPA-4 Error Message %VSPA-4-FIPS_CRNG_NOTIFY: Same Random Number was generated twice in succession! Explanation The same random number was generated twice in succession. Recommended Action No action is required.

VSPA-5 Error Message %VSPA-5-FIPSNOTIFY: FIPS POST Successful. Explanation The power-on self test (POST) succeeded. Recommended Action No action is required.


1882

VSPA Messages

Error Message %VSPA-5-ILLEGALCLEAR: Illegal Clear Packet: Src =%u.%u.%u.%u, Dst =%u.%u.%u.%u, Proto =%u Explanation An unexpected clear (unencrypted) packet was received from the WAN. Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %VSPA-5-REPLAYERR: Replay Error: Current Seq. No. =%u, Highest Seq No. =%u Explanation A replay error was detected on IPsec inbound processing. Recommended Action Make sure the IPSec packets are not being reordered in the network, such as by

a QoS process.

Error Message %VSPA-5-SELCHECKERR: Selector Check Error: Src =%u.%u.%u.%u:%u, Dst =%u.%u.%u.%u:%u, Proto =%u, saidx =%u Explanation A packet was received that did not fall within the appropriate selector range. Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %VSPA-5-SEQOVERFLOW: Sequence number overflow: Src =%u.%u.%u.%u, Dst =%u.%u.%u.%u, Proto =%u, saidx =%u Explanation The sequence number in the security association has overflowed. Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support


1883

VS_PARSE Messages


VS_PARSE Messages This section contains virtual switch (VS) messages.

VS_PARSE-3 Error Message %VS_PARSE-3-ALLOC_ICC_PAK_FAIL: Unable to allocate memory for ICC packet Explanation A packet allocation failed for sending an ICC message to do the specified operation. Recommended Action No action is required.

Error Message %VS_PARSE-3-CONFIG_MISMATCH: [chars] Explanation The VSL configuration in the standby module’s configuration differs from either the

active module’s startup configuration or the active module’s running configuration. Recommended Action Use the show switch virtual redundancy config-mismatch command to

display the mismatch configuration. If the standby configuration differed from the active’s startup configuration or the active’s running configuration, you must fix the discrepancy in VSL configuration between the active and standby switch. Then, enter a write mem command to update the standby’s startup configuration and reload the standby.

Error Message %VS_PARSE-3-MISMATCH: %s Explanation Configuration mismatches were detected between the active and standby units in either

the running configuration, the startup configuration, or the EARL operating mode. Recommended Action Enter the show switch virtual redundancy mismatch command to display the

mismatch. Correct any discrepancy in the VSL configuration between the standby switch’s configuration and the active switch’s startup configuration or running configuration. Correct any discrepancy in the EARL operating mode between the standby switch’s configuration and the active switch’s configuration. Enter the write mem command and reload the standby switch.


1884

VS_QOS_ACL Messages

Error Message %VS_PARSE-3-VS_HWSB_CREATE_FAIL: Unable to create VS HW SB for vslot [int], port [int] Explanation An attempt to create a virtual switch hardware standby has failed due to unknown

reasons. During virtual switch mode conversion, the standby VSL port would flap when attempting to reconfigure the port on the active. It is recommended to have at least two physical links for a virtual switch mode conversion attempt in order to avoid a dual active scenario due to this error. Recommended Action No action is required.

VS_PARSE-4 Error Message %VS_PARSE-4-CONFIG_WARNING: %s: %d Explanation Errors were detected while parsing the virtual switch (VS) configuration. The switch will be in standalone mode with a switch number setting. Recommended Action If the VS conversion process is successful in bringing up virtual switch mode, no action is required. If the process fails, check the VS configuration.

Error Message %VS_PARSE-4-NO_VSL_CONFIG: No VSL interface is configured Explanation There are no VSL interfaces configured. This switch cannot communicate with the other

switch to form the virtual switch. Recommended Action No action is required.

Error Message %VS_PARSE-4-SWITCH_NUM: %s: %d Explanation A valid ROMMON variable SWITCH_NUMBER must be configured before the switch

can be brought up as a virtual switch. Recommended Action Configure a valid SWITCH_NUMBER in ROMMON.

VS_QOS_ACL Messages This section contains virtual switch QoS ACL messages.

VS_QOS_ACL-3 Error Message %VS_PORT_QOS_ACL-3-PIDX_BASE_MSG_FAILED: Setting of PIDX_BASE to value [hex] failed Explanation A message from the TCAM application to set the Tycho’s PDIX_BASE has failed. Recommended Action No action is required.


1885

VTSP Messages

VTSP Messages This section contains Voice Telephony Service Provider (VTSP) messages.

Error Message %VTSP-3-MSGSNDFAIL: channel:[chars] DSP ID:[hex] Message ID:[hex] Explanation A message could not be sent to the DSP. The call continued but may have experienced

problems. Recommended Action Verify that the DSP is still functioning properly by attempting to place a call

on the affected voice port. Contact your technical support representative, include the full text of the error message.

WARMUPGRADE Messages This section contains warm upgrade messages.

WARMUPGRADE-3 Error Message %WARMUPGRADE-3-char: Image file open/read failure. Explanation The warm upgrade process could not open or read from the image file specified. Recommended Action Check whether the specified image is present at the desired location and has the required read permissions. If the location is remote, check whether connectivity exists.

Error Message %WARMUPGRADE-3-CHECKSUM: [chars] image checksum mismatch. Explanation The checksum of the image in memory differs from the expected checksum. Recommended Action Check whether the image file is complete and uncorrupted.

Error Message %WARMUPGRADE-3-DECOMPRESS: Image file decompression failure. Explanation The warm upgrade process could not decompress the image file. Recommended Action Check whether the image file is complete and uncorrupted.

Error Message %WARMUPGRADE-3-FORMAT: Unknown image file format. Explanation The warm upgrade process could not recognize the format of the image file. Recommended Action Check whether the specified image is a valid Cisco IOS executable in a

supported format. Check the release notes for supported formats.


1886

WCCP Messages

Error Message %WARMUPGRADE-3-SIZE: [chars] image size mismatch. Explanation The size of the image in memory differs from the expected size. Recommended Action Check whether the image file is complete and uncorrupted.

WCCP Messages This section contains Web Cache Communication Protocol (WCCP) messages.

WCCP-3 Error Message %WCCP-3-SBADDFAIL: Unable to add WCCP subblock on interface [chars] Explanation This internal error message indicates that the WCCP process was unable to attach

interface-specific service information. Recommended Action Ensure that there is enough memory available for all processes.

Error Message %WCCP-3-SBCREATEFAIL: Unable to allocate WCCP subblock on interface [chars] Explanation This internal error message indicates that the WCCP process was unable to allocate

memory to hold interface specific service information. Recommended Action Ensure that there is enough memory available for all processes.

WiSM Messages This section contains WiFi services module messages.

WiSM-3 Error Message WiSM-3-PORTCHANNEL: Portchannel allocation failed for module [dec]. Explanation The system is unable to allocate enough port channel groups for WiSM card. [dec] is

the module number. Recommended Action If this message recurs, copy the message exactly as it appears on the console



1887

WiSM Messages


WiSM-5 Error Message %WiSM-5-DUP_SRVC_IP: Service IP [IP_address] of Controller [dec]/[dec] is same as Controller [dec]/[dec] Explanation The Cisco Wireless Services Module software detected that a controller is assigned with

an IP address on its service port that is being used by another controller. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %WiSM-5-RESET: Controller [dec]/[dec] not responding, WiSM in slot [dec] is being reset Explanation The Cisco Wireless Services Module in the specified slot is being reset because one of

the controllers failed to respond to 12 consecutive keepalive requests. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %WiSM-5-STATE: Controller [dec] in slot [dec] is [chars] Explanation A change has been detected in the Cisco Wireless Services Module controller. If the

controller status is Oper-Up, WCP communication between the controller and the supervisor engine is up or else it is down. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1888

WS_ALARM Messages


WS_ALARM Messages This section contains Windstar alarm messages.

WS_ALARM-6 Error Message %WS_ALARM-6-INFO: [chars] [chars] [chars] [chars] [chars] Explanation Displays alarm assertion or deassertion information. Recommended Action No action is required.

WS_IPSEC_3 Messages Error Message %WS_IPSEC_3-3-FIPSERROR: FIPS POST Failed. Explanation Power On Self Test failed. Crypto engine disabled. Recommended Action Contact TAC.

Error Message %WS_IPSEC_3-3-HARDWARE_ERR: WS_IPSEC_3 Error: [chars] Explanation A hardware error occured on the WS_IPSEC_3 causing an interrupt Recommended Action Copy the error message (and any recent error messages) as it appears on the

console. In case of a WS_IPSEC_3 crash, collect the crashinfo file from the sup-bootdisk. Contact your Cisco technical support representative and provide the gathered information. The SPA will automatically reload itself in case of a crash

Error Message %WS_IPSEC_3-4-FIPS_CRNG_NOTIFY: Same Random Number was generated twice in succession! Explanation Same random number was generated twice in succession. Recommended Action No Action Required.


1889

WS_IPSEC_3 Messages

Error Message %WS_IPSEC_3-5-FIPSNOTIFY: FIPS POST Successful. Explanation Power On Self Test succeeded. Recommended Action No Action Required.

Error Message %WS_IPSEC_3-5-ILLEGALCLEAR: Illegal Clear Packet: Src =[int].[int].[int].[int], Dst =[int].[int].[int].[int], Proto =[int] Explanation An unexpected clear packet was received from the WAN. Recommended Action If this message recurs, copy the error message exactly as it appears on the


Error Message %WS_IPSEC_3-5-REPLAYERR: Replay Error: Current Seq. No. =[int], Highest Seq No. =[int] Explanation Failed anti-replay check on IPsec inbound processing. Recommended Action Make sure the IPSec packets are not reordered in the networks. Follow up with

TAC.

Error Message %WS_IPSEC_3-5-SELCHECKERR: Selector Check Error: Src =[int].[int].[int].[int]:[int], Dst =[int].[int].[int].[int]:[int], Proto =[int], saidx =[int] Explanation A packet was received that did not fall within the appropriate Selector range. Recommended Action If this message recurs, copy the error message exactly as it appears on the



1890

X40G Messages

Error Message %WS_IPSEC_3-5-SEQOVERFLOW: Sequence number overflow: Src =[int].[int].[int].[int], Dst =[int].[int].[int].[int], Proto =[int], saidx =[int] Explanation The sequence number in the Security Association has overflowed. Recommended Action If this message recurs, copy the error message exactly as it appears on the


X40G Messages This section contains X40G client error messages.

X40G-2 Error Message %X40G-2-TCAM_MGR_CRIT_ERR: GTM ERROR: [chars] ([dec]) Explanation An X40G TCAM critical error was detected. Recommended Action Copy the error message exactly as it appears on the console or in the system


X40G-3 Error Message %X40G-3-TCAM_MGR_ERR: GTM ERROR: [chars] ([dec]) Explanation An X40G TCAM MGR interaction error was detected. Recommended Action Copy the error message exactly as it appears on the console or in the system



1891

X40G Messages

Error Message %X40G-3-TCAM_MGR_HW_ERR: GTM HW ERROR: [chars] ([dec]) [[dec]:[hex]] Explanation An X40G TCAM hardware error was detected. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %X40G-3-TCAM_MGR_HW_PERR: GTM HW ERROR: [chars] ([dec]) Explanation An X40G TCAM interface parity error was detected. Recommended Action Copy the error message exactly as it appears on the console or in the system


X40G-4 Error Message %X40G-4-TCAM_MGR_ALLOC_ERR: [chars] NP ([dec]), Region Id ([dec]) Explanation An NP TCAM entry allocation failure was detected. Recommended Action Copy the error message exactly as it appears on the console or in the system

log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the remote command module sh platform software xtcammgr instance info command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the gathered information.


1892

X40G Messages

X40G-5 Error Message %X40G-5-TCAM_MGR_INFO: [chars] Explanation An X40G TCAM driver error was detected. Recommended Action Copy the error message exactly as it appears on the console or in the system


X40G_PC_QOS-3 Error Message %X40G_PC_QOS-3-X40G_EXCEED_NUM_QUEUES: %Exceed number of supported queues for this interface Explanation Not available. Recommended Action Copy the error message exactly as it appears on the console or in the system


Error Message %X40G_PC_QOS-3-X40G_WRED_QLIMIT: %Queue limit and WRED cannot be configured together Explanation Not available. Recommended Action This error indicates a qos policymap configuration error occured. Qos

processing on the interface might not work as expected. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.


1893

X40G Messages

X40G_PC_QOS-4 Error Message %X40G_PC_QOS-4-X40G_PC_PMAP_INCOMPATIBLE: Warning - Policymap attached to port-channel EVC is incompatible with X40G member link. Explanation Policymap attached to port-channel EVC is with an X40G member link. Recommended Action Remove policymap attached to port-channel EVC before adding a X40G

member link to port-channel.

X40G_QOS-3 Error Message %X40G_QOS-3-ACTN: [chars] Explanation The x40g qos client detected a qos feature processing error event, specified in the

message Recommended Action This error indicates a qos policymap configuration error occured. Qos


Error Message %X40G_QOS-3-CFN: [chars] Explanation The x40g qos client detected a classification configuration error event, specified in the

message. Recommended Action This error indicates a qos policymap configuration error occured. Qos



1894

X40G Messages

Error Message %X40G_QOS-3-NOMEM: Memory Allocation Failure - [chars]) Explanation Memory required by the qos client to service one or more Network Processors could not be allocated. Recommended Action This error may indicate that more memory must be installed on the affected

card or platform in order to service all the features and related entities enabled via the configuration. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message %X40G_QOS-3-NP: [chars] Explanation The x40g qos client detected an npu programming error event, specified in the message. Recommended Action This error indicates a qos policymap configuration error occured. Qos


Error Message %X40G_QOS-3-PMAP_CONFIG:[chars] Explanation QoS processing on the interface specified in the msg is not functional Recommended Action This configuration error is not considered fatal to the operation of the Network

Processors. The software is designed to detect and report the error condition. Please refer to the cisco.com documentation for configuration to correct the problem.

Error Message %X40G_QOS-3-PRFL:[chars] Explanation The x40g qos client detected a hardware profile run out. Hardware profile type is

mentioned in the message Recommended Action Identify the QoS hardware profile that got exhausted on the ES+ linecard.

Modify the QoS configuration on the interface such that it can get a QoS profile shared with any other policymap on linecard or else remove policymap from the interface. Else Qos processing on the interface might not work as expected. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance,


1895

X40G Messages


Error Message %X40G_QOS-3-SVI_PMAP: [chars] Explanation Only one policymap is allowed to be attached to either direction of interface vlan at a

time. Recommended Action Please remove previous attached policymap and reattach the policymap. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

X40G_QOS-4 Error Message %X40G_QOS-4-CFG: [chars] Explanation When applying policymap, configuration may be changed by the NP because of

hardware support Recommended Action This error indicates a qos policymap configuration error occured. Qos



1896

XCONNECT Messages

XCONNECT Messages This section contains xconnect-related event and error messages.

XCONNECT-3 Error Message %XCONNECT-3-CONFIG: %s Explanation An invalid XCONNECT configuration or an error in processing the XCONNECT

configuration has occurred. Recommended Action No action is required.

Error Message %XCONNECT-3-ILLEGAL: %s Explanation An illegal event has been processed by the XCONNECT subsystem. Recommended Action No action is required.

XCONNECT-5 Error Message %XCONNECT-5-PW_STATUS: %s Explanation An event caused the pseudowire to change status. Recommended Action No action is required.

Error Message %XCONNECT-5-REDUNDANCY: %s Explanation An event caused the XCONNECT redundancy facility to generate a switchover to the

specified backup member. Recommended Action No action is required.


1897

XCPA Messages

XCPA Messages Error Message %XCPA-3-HWVER: bay [[dec]] incompatible microcode (hw:[int].[int], [int].[int]). Explanation An incompatability exists between the port adapter hardware and the version of

microcode that the system image attempted to load. Recommended Action Use the show microcode command to display the default and configured

versions of microcode for this port adapter hardware type. Assure that the correct version of microcode exists in flash. Use the microcode reload command to load the microcode. If the error still occurs, record the output from the following commands: show tech, show microcode, dir slot0:, dir slot1:, show log. Provide this information to your technical support representative.

XCVR Messages This section contains transponder messages.

XCVR-3 Error Message %XCVR-3-UNKNOWN_SFP_INSERTED: Unknown SFP inserted [chars] Explanation An unknown Small Form Factor Pluggable (SFP) transceiver has been inserted. Recommended Action If this message recurs, copy the message exactly as it appears on the console



1898

XDR Messages

XDR Messages This section contains eXternal Data Representation (XDR) messages.

XDR-3 Error Message %XDR-3-BYPASSFOFNEGO: Bypassing FOF ISSU client %s (%u) nego for XDR client %s, slot %s as FOF ISSU client is not present in %s image. Explanation This XDR client has a dependency on another ISSU client due to having foreign-owned

fields (FOFs). Because the ISSU client that owns the FOFs is not in the image, the XDR client will not wait for that client to finish ISSU negotiation. The missing client must be added to the image. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %XDR-3-CLIENTISSUBADENTITY: Unable to register ISSU entity for [chars], reason: [chars] Explanation Unable to register this XDR client’s ISSU entity due to problems with registering the

item given as a reason in the error message. ISSU will stop working for this client and may lead to unpredictable behavior. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1899

XDR Messages

Error Message %XDR-3-CLIENTISSUBADGROUP: New m/cast group (slots [chars]) has multiple members before nego complete. Explanation A new multicast group has been created with multiple slots before ISSU negotiation for

each client has completed. This condition will lead to unpredictable results. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %XDR-3-CLIENTISSUBADNEGOMSG: Unexpected nego msg - slot [chars], client [chars], ctxt [dec] Explanation XDR has received a negotiation message unexpectedly as this client is either not ISSU aware or has already completed negotiation for this slot. This condition is likely a precursor to unpredictable behavior for this client. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %XDR-3-CLIENTISSU_FOF_NEGOFAIL: ISSU negotiation failed for FOF client %u, for peer %s (ISSU peer %d), blocking ISSU client %s (%d) reason - %s Explanation The ISSU negotiation failed for a client that has registered ISSU foreign-owned field (FOF) client dependencies. The dependent clients on this slot and the remote slot cannot interoperate in SSO mode. Synchronizing of information to and from this slot cannot proceed for this client and the dependent clients. Enter the show xdr multicast command for full details. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1900

XDR Messages

following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show xdr multicast commands and your pertinent troubleshooting logs.

Error Message %XDR-3-CLIENTISSU_FOF_REGERROR: ISSU client %s (%d), entity %d, message %d (%s), failed ISSU FOF registration: %s, reason: %s, Explanation This ISSU client has a message containing a foreign-owned field (FOF) owned by

another client, but the client failed to register this dependency. This is an internal software error. Recommended Action Update to a later software release.

Error Message %XDR-3-CLIENTISSUNEGATIVEPADDING: Negative padding for [chars], slots [chars], msg [dec] (padded: [dec], unpadded: [dec]) Explanation An internal error occurred involving a mismatch of internal data structures. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %XDR-3-CLIENTISSU_NEGOFAIL: ISSU negotiation failed for [chars], slot [chars] [chars] Explanation ISSU negotiation failed. The XDR client on this slot and the remote slot cannot interoperate in SSO mode. Synchronizing of information to and from this slot will not happen for this client and dependent clients. Seethe output of the show xdr multicast command for full details. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1901

XDR Messages

Error Message %XDR-3-CLIENTISSUNEGONOTDONE: Attempting to push send XDR message ([dec]) to slots [chars] for [chars] before nego complete. Explanation An internal error occurred that may result in unpredictable behavior. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %XDR-3-CLIENTISSU_NEGOREGERROR: XDR client %s, failed ISSU negotiation result notification registration for ISSU client %s (%d), reason: %s, Explanation This client has a dependency on the successful ISSU negotiation of another client and

has failed to register this dependency. This is an internal software error. Recommended Action Update to a later software release.

Error Message %XDR-3-CLIENTISSU_NEGOUNREGERROR: Failed to unregister ISSU negotiation result notification registration for ISSU client %s (%d), reason: %s, Explanation This client has a dependency on the successful ISSU negotiation of another client and

has failed to unregister this dependency when not required. This is an internal software error. Recommended Action Update to a later software release.

Error Message %XDR-3-CLIENTISSUNOMSGGRP: Cannot determine ISSU message group for slot %d. Unknown %s Explanation Because the line card type for the specified slot is not recognized, the ISSU client cannot

determine the set of ISSU messages to be used between the local and remote slot. This condition might be due to a new line card type. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1902

XDR Messages

Error Message %XDR-3-CLIENTISSU_PUSHFAIL: Attempting to push send XDR message ([chars]) to slots [chars] via client [chars] failed due to [chars] Explanation An internal error occurred that may result in unpredictable behavior. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %XDR-3-CLIENTISSU_REGERROR: ISSU client [dec] ([chars]), entity [dec], failed ISSU registration: [chars] Explanation The ISSU negotiation failed for this XDR client. This is a software error. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %XDR-3-CLIENTISSUSENDFAILED: Can’t send XDR client ISSU nego msg: reason [chars], slot [chars], client [chars] Explanation XDR has failed to send an ISSU negotiation message for the given client. The slot will

be marked as ISSU-unaware, and communication with this slot will proceed on that basis. However, this is likely to lead to unpredictable behavior. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1903

XDR Messages

Error Message %XDR-3-CLIENTISSUSTARTNEGOFAIL: Can’t start nego: reason [chars], slot [chars], client [chars], sid [dec] Explanation XDR has failed to start ISSU negotiation with the remote slot for the reason given. The

slot will be marked as ISSU-unaware, and communication with this slot will proceed on that basis. However, this is likely to lead to unpredictable behavior. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %XDR-3-ISSUBADREGPARAMS: Client [chars] trying to register with incomplete ISSU support. Explanation This client does not properly support ISSU and will be registered as not supporting

ISSU. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %XDR-3-ISSUCAPNEGOFAIL: Client [chars] failed to [chars] capability/ies due to [chars] Explanation An internal software error occurred. The capability negotiation failed unexpectedly. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1904

XDR Messages

Error Message %XDR-3-ISSU_ENUM_ERROR: Enum for [chars] ([chars] component) is not ISSU-compliant: [chars] Explanation The given enumeration is not ISSU-compliant for the reason given. Unpredictable

behavior will result when interoperating with different Cisco IOS versions. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %XDR-3-ISSUINITFAIL: Unable to register XDR ISSU [chars], reason: [chars] Explanation Unable to register the given XDR ISSU parameter due to the reason given. This will stop ISSU working for this client and may lead to unpredictable behavior. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %XDR-3-ISSU_NEGOFAIL: ISSU negotiation failed for XDR, slot [chars] [chars] Explanation ISSU negotiation failed. XDR on this slot and the remote slot cannot interoperate.

Synchronizing of information to and from this slot for all XDR clients will not be allowed. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1905

XDR Messages

Error Message %XDR-3-MSGSIZEFAIL: The IPC message size is out of boundsThe ipc_msg_size is : [dec] while the maximum size we can handle is theXDR_IPC_BUFFER_SIZE : [dec] . Explanation The size of the IPC message that was received is larger than the maximum size that can

be handled. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %XDR-3-PRIOCLIENTISSU_NEGOFAIL: ISSU negotiation failed for [chars], slot [chars] [chars] Explanation ISSU negotiation failed for a core XDR client. XDR on this slot and the remote slot cannot interoperate in SSO mode. Synchronizing of information to and from this slot will not happen for any XDR client. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %XDR-3-XDRBADSLOT: An invalid slot %d was obtained during - %s Explanation An invalid slot was obtained. Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show xdr linecard, and show xdr multicast commands and your pertinent troubleshooting logs.


1906

XDR Messages

Error Message %XDR-3-XDRDEQUEUE: Failed to dequeue from [chars] with [dec] elements still queued Explanation A queueing failure has occurred. A nonempty queue could not be dequeued. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %XDR-3-XDRIPC: XDR IPC error on multicast-group [hex] due to [chars]. Explanation A general IPC-related error occurred, which may prevent transfer of data to other peers

using the IPC mechanism . Recommended Action Enter the show xdr multicast command immediately after this error. Copy the


Error Message %XDR-3-XDRMCASTJOIN: Attempt to join [chars] to [chars] failed because client [chars] returned an error Explanation An internal error occurred that may result in unpredictable XDR behavior. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1907

XDR Messages

Error Message %XDR-3-XDRMCASTJOINREQ: Client [chars] returned an invalid response to a join request for groups [chars] and [chars] Explanation An internal error occurred that may result in unpredictable XDR behavior. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %XDR-3-XDRMCAST_PEER_BINDING: XDR peer [chars] bind to group [chars] (was bound to [chars]): [chars] Explanation An internal error occurred that may result in unpredictable XDR behavior. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %XDR-3-XDRNOMEM: XDR failed to allocate memory during [chars] creation. Explanation Allocation of memory by the XDR subsystem has failed. This failure may result in

unpredictable XDR behavior. Recommended Action Make sure that there is enough memory for the operations being performed by your system. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


1908

XDR Messages

Error Message %XDR-3-XDROOS: Received an out of sequence IPC message. Expected [dec] but got [dec] Explanation An out-of-sequence or unknown IPC message was received. This condition indicates

that an IPC is not working properly. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %XDR-3-XDRPEER: An XDR peer error for slot [chars]. Due to [chars]. Explanation An error relating to an XDR peer has occurred. Recommended Action Enter the show xdr linecard command. Copy the message exactly as it appears


Error Message %XDR-3-XDRQUEUE: XDR queue error: [chars]. Explanation The XDR subsystem queueing operation failed. This may result in unpredictable

behavior of XDR. Recommended Action Make sure that there is enough memory for the operations being performed by your machine. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


1909

XDR Messages

Error Message %XDR-3-XDRSLOTFROMMASK: Cannot determine slot from mask [chars] (client [chars]) Explanation Mapping from slot mask to slot has failed. During ISSU negotiation, the message

destination cannot be determined, and the message will be dropped. Recommended Action Copy the message exactly as it appears on the console or in the system log.


XDR-6 Error Message %XDR-6-CLIENTISSUBADRCVTFM: Failed to rcv_transform message - from slot [chars], client [chars], context [dec] Explanation The system cannot perform an ISSU receive transform. This condition is likely due to

an earlier failure in negotiation, or when one side of an ISSU-enabled XDR connection is out of synchronization with the other. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %XDR-6-CLIENTISSUBADTXTFM: Failed to xmit_transform message - to slot [chars], client [chars], context [dec] Explanation The system cannot perform an ISSU transmit transform. This condition is likely due to

an earlier failure in negotiation, or when one side of an ISSU-enabled XDR connection is out of synchronization with the other. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1910

XDR Messages


Error Message %XDR-6-CLIENTISSU_BLOCKED: Client [chars] cannot sync info to/from slot [chars] due to ISSU negotiation failure of client [chars] Explanation This client depends on another XDR client for which ISSU negotiation has failed. As a

result, this client is prevented from communicating with the remote slot. This is due to ISSU incompatibilities between the two images. Functionality for this client will revert to RPR mode. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %XDR-6-CLIENTISSU_UNBLOCKED: Client [chars] can now sync info to/from slot [chars] due to ISSU negotiation success of client [chars] Explanation This client depends on another XDR client for which ISSU negotiation had previously

failed but has now succeeded. As a result, this client can resume communication with the remote slot. Functionality for this client will revert to SSO mode. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %XDR-6-CLIENTISSUUNREG: Failed to unregister session - client [chars], slot [chars], reason [chars] Explanation The system was unable to unregister this session. This condition will likely cause

problems when reregistering. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1911

XDR Messages


Error Message %XDR-6-CLIENTNOTREGONRP: Client [chars] has registered on slot [chars] before RP. Explanation The XDR client has registered on a non-RP card before an RP card. If this has occurred

while toggling the client’s registration status rapidly, it may be a transient problem that will resolve itself. If not, the client’s status may be unpredictable, and ISSU negotiation (if platform is ISSU-aware) may not take place correctly. Recommended Action Verify whether the client’s registration status is the same on both the RP and

the card on which the problem is reported by comparing the output of the show xdr client all command to see if the client is present or absent in both. If so, and no other error messages have been seen, then this is a transient issue and no further action is required. Otherwise, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %XDR-6-ISSUBADRCVTFM_DUMP: CSCsh95828 detected. Please collect ’show xdr linecard’, ’show monitor event-trace xdr all’, and the full system log, on both the RP and the related LC, and report this occurrence. Slot %s, data 0x%08x %08x %08x %08x %08x %08x %08x %08x Explanation This message contains a decoded packet dump and trace log information for

investigating CSCsh95828. Recommended Action Copy the message exactly as it appears and contact your Cisco technical

support representative.

Error Message %XDR-6-ISSUBADTXTFM: Failed to xmit_transform message - slot [chars], reason [chars] Explanation The system was unable to perform an ISSU transform on an outgoing XDR header. The

message will be ignored. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1912

XDR Messages


Error Message %XDR-6-ISSUCLIENTABSENT: ISSU client [chars] absent on slot [chars]. Client functionality may be affected. Explanation The remote slot does not support this ISSU client. The software will handle this by reducing client functionality locally to continue in SSO mode, or by forcing the remote peer into RPR mode as appropriate. This is expected behavior in ISSU-capable systems. Recommended Action No action is required.

Error Message %XDR-6-ISSUBADRCVTFM: Failed to rcv_transform message - slot [chars], reason: [chars] Explanation The system was unable to perform an ISSU transform on an incoming XDR header. The

message will be ignored. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %XDR-6-XDRDISABLEREQUEST: Peer in slot [chars] requested to be disabled due to: [chars]. Disabling linecard Explanation The line card has requested to be disabled due to an error condition. Recommended Action Enter the show monitor event-trace xdr command from the RP and the line

card in question. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


1913

XDR Messages

Error Message XDR-6-XDRINVALIDHDR: XDR for client ([chars]) dropped (slots:[chars] from slot:[dec] context:[dec] length:[dec]) due to: [chars] Explanation The XDR client specified in the message text could not be registered. A failure has

occurred that prohibits the XDR client from registering with the core. Recommended Action Copy the message exactly as it appears on the console or in the system log.


Error Message %XDR-6-XDRINVALIDHDRISSU: XDR ISSU negotiation message for client ([chars]) dropped (slots:[chars] from slot:[chars] context:[int] length:[int]) due to: [chars] Explanation The XDR ISSU negotiation message was dropped for the reason given. Recommended Action If the message occurred during an ISSU upgrade then it may be safely ignored.

Otherwise: Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message %XDR-6-XDRIPCNOTIFY: Message not sent to slot [chars] because of IPC error [chars]. Disabling linecard. (Expected during linecard OIR) Explanation A general IPC-related error has occurred that may prevent transfer of data to other peers

using the IPC mechanism. Recommended Action Enter the show xdr multicast and show xdr linecard internal commands

immediately after this error. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


1914

XDR Messages

Error Message %XDR-6-XDRIPCPEER: XDR IPC error occurred for peer in slot [chars] due to [chars][chars]. Explanation A general IPC-related error has occurred that may prevent transfer of data to other peers

using the IPC mechanism. Recommended Action Enter the show xdr multicast and show xdr linecard commands immediately after this error. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %XDR-6-XDRLCDISABLEREQUEST: Client [chars] requested to be disabled. [chars] Explanation The line card has requested to be disabled due to an error condition. Recommended Action Enter the show monitor event-trace xdr from the RP and the line card in

question. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %XDR-6-XDRMCASTINIT: XDR mcast subsystem initilisation error: [chars] Explanation A failure occurred that prohibits the XDR client from registering with the core. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1915

XDR Messages

Error Message %XDR-6-XDRREGISTRATION: XDR failed to register [chars] client due to [chars] Explanation The XDR client specified in the message text could not be registered. A failure has

occurred that prohibits the XDR client from registering with the core. Recommended Action Copy the message exactly as it appears on the console or in the system log.



1916

G LO S SA RY

The following glossary of acronyms expands acronyms and initialisms that are used in Cisco IOS System Messages, Release 12.2 SX.

Numerals 10GE

10-Gigabit Ethernet

AAA

authentication, authorization, and accounting

AAL5

ATM adaptation layer 5

ABM

asynchronous balanced mode

ABR

Area Border Router

AC

alternating current

ACE

Allegro Crypto Engine

ACIP

ATM Cable Interface Processor

ACK

acknowledgment

ACL

access control list

ACO

alarm cutoff

ACTLU

activate logical unit

ACTPU

activate physical unit

ADSL

asymmetric digital subscriber line

AFI

Address Family Identifier

AH

Authentication Header

AIC

Alarm Interface Controller

AIM

Advanced Interface Module

AIM

advanced integration module

AIP

ATM Interface Processor

AIS

alarm indication

A

System Messages for Cisco IOS Release 12.2 SX OL-xxxxx-xx

GL-1

Glossary

ALC

ATM line card

ALPS

Airline Product Set

AMD

Advanced Micro Devices

ANR

Automatic Network Routing

ANSI

American National Standards Institute

ANY-PHY

Any physical layer-data link layer

AP

access point

AP

authentication proxy

API

application programming interface

APING

APPC Ping

APN

access point name

APPC

Advanced Program-to-Program Communications

APPN

Advanced Peer-to-Peer Networking

APS

automatic protection switching

AQD

average queue depth

ARAP

AppleTalk Remote Access Protocol

ARB

Adaptive Rate-Based

ARP

Address Resolution Protocol

ARQ

automatic repeat request

AS

autonomous system

ASCU

agent-set control unit

ASIC

application-specific integrated circuit

ASP

ATM switch processor

ATA

Advanced Technology Attachment

ATA

Analog Telephone Adapter

ATF

area to free

ATM

Asynchronous Transfer Mode

AToM

Any Transport over MPLS

AURP

AppleTalk Update-Based Routing Protocol


GL-2

OL-xxxxx-xx

Glossary

AutoRP

Auto-Rendezvous Point

AVL

approved vendor list or Adelson-Velskii and Landis

BAP

Bandwidth Allocation Protocol

BB

broadband

BBI

begin bracket indicator

BCS

business critical solution

BERT

bit error rate tester

BFR

Bigger, Faster Router

BFRP

big fast route processor

BGP

Border Gateway Protocol

BGPPA

Border Gateway Protocol Policy Accounting

BIC

backplane interface card

BIDI

bidirectional bus

BIND

Berkeley Internet Name Domain

BIP

bit interleaved parity

BIS

Broadband Interface Shelf

BLLI

Broadband Low Layer Information

BMA

Buffer Management ASIC

BOOM

10BASE-T Ethernet LAN interface card

BOOTP

Bootstrap Protocol

BPDU

bridge protocol data unit

BPI

baseline privacy interface

BPVC

Bridged Permanent Virtual Circuit

BRI

Basic Rate Interface

BRF

Bridge Relay Function

BSC

Binary Synchronous Communications

B


GL-3

Glossary

BSS

Business Support System

BSTUN

Block Serial Tunnel

BTU

British thermal unit

BUS

broadcast-and-unknown server

CA

certification authority

CAIM

Compression Advanced Interface Module

CAM

content-addressable memory

CAMR

Cisco Access Metro Router

CAS

channel-associated signaling

CASA

Cisco Appliance and Services Architecture

CBAC

Context-Based Access Control

CBC

Cell Bus Controller

CBI

Cell Bus Interface

CBus

CiscoBus

CBWFQ

Class Based Weighted Fair Queueing

CCA

Common Configuration Architecture

CCAPI

call control API

CCB

call control block

CCB

configuration control block

CCO

Cisco Connection Online

CCW

channel command word

CDI

Common Driver Interface

CDL

Converged Data Link

CDM

cable data modem

CDP

Cisco Discovery Protocol

CDR

clock and data recovery

C


GL-4

OL-xxxxx-xx

Glossary

CE

certificate enrollment

CEB

Common EMS Base

CEBI

conditional end bracket indicator

CEF

Cisco Express Forwarding

CES

circuit emulation service

CET

Cisco Encryption Technology

CF

Checkpoint Facility

CFI

Common Flash Interface

CGMP

Cisco Group Management Protocol

CGX

CryptoGraphics eXtensions

CHAP

Challenge Handshake Authentication Protocol

cHPI

compact Host Port Interface

CI

connection identifier

CICS

Customer Information Control System

CIP

Channel Interface Processor

CIR

committed information rate

CIS

Card Information Services

CIU

Communication Interface Unit

CLAW

Common Link Access for Workstations

CLI

command-line interface

CLNS

Connectionless Network Service

CLS

Cisco link services

CLSI

Cisco link services interface

CMCC

Cisco Mainframe Channel Connection

CMNS

Connection Mode Network Service

CMPC

Cisco Multipath Channel

CMTS

cable modem termination system

CNR

Cisco Network Registrar

CNOS

change number of sessions System Messages for Cisco IOS Release 12.2 SX

OL-xxxxx-xx

GL-5

Glossary

CNS

Cisco Networking Services

CNSP

Complete Number Sequence PDU

COAPS

Count of APS switchovers

codec

coder-decoder

CoS

class of service

CoSQ

Class of Service Queues

COT

continuity testing

CP

control point

CP

coprocessor

CPA

Channel Port Adapter

CPE

customer premises equipment

CPI

common part indicator

CPI-C

common programming interface for communications

CPM

Combination Port Module

CRC

cyclic redundancy check

CRF

Concentrator Relay Function

CRL

certificate revocation list

cRTP

compressed Real-Time Protocol

CRV

call reference value

CSA

compression service adapter

CSAR

Cisco Cell Segmentation and Reassembly

CSC

clock switch card

CSG

Content Services Gateway

CSI

called subscriber identification

CSM

call switching mode

CSM

call switching module

CSNA

Cisco SNA

CSNP

Complete Sequence Number PDU

CSU

channel service unit


GL-6

OL-xxxxx-xx

Glossary

CTC

Cisco Transport Controller

CTL

Certificate Trust List

CTRC

Cisco Transaction Connection

CTS

Clear To Send

CV

Cisco View

CWAN

Constellation WAN

CWTLC

Constellation Wan Toaster Line Card

CyBus

Cisco Extended Bus

DAE

data aggregrator end

DBus

diagnostic bus

DC

direct-connect

DC

direct current

DCD

data carrier detect

DCE

data communications equipment

dCEF

distributed Cisco Express Forwarding

DDOS

distributed denial of service

DDR

dial-on-demand routing

DDSM

Digital Data Services Manager

DECnet

Digital Equipment Corporation network

DEMUX

demultiplexer

DFC

dial feature card

DFP

Dynamic Feedback Protocol

DFRAC

Dual Framer and RAC

DHCP

Dynamic Host Configuration Protocol

DHCPv6

Dynamic Host Configuration Protocol, version 6

DIB

Directory Information Base

D


GL-7

Glossary

DIP-4

4-bit Diagonal Interleaved Parity

DLC

data-link connection

DLC

data-link control

DLCI

data-link connection identifier

dLFI

Distributed Link Fragmentation and Interleaving

dLFIoATM

Distributed Link Fragmentation and Interleaving over ATM

dLFIoFR

Distributed Link Fragmentation and Interleaving over Frame Relay

DLR

designated local retransmitter

DLSw

data-link switching

DLU

dependent logical unit

DLU

destination logical unit

DLU

dynamic logical unit

DLUR

dependent logical unit requester

DLUS

dependent logical unit server

DM

dense mode

DM

disconnect mode

DMA

direct memory access

DMAC

destination MAC

DML

distributed multilink

DMLP

Distributed Multilink Point-to-Point Protocol

DNIS

dialed number identification service

DNS

Domain Name Server

DNS

Domain Name Service

DNS

Domain Name System

DOCSIS

Data-over-Cable Service Interface Specifications

DOI

domain of interpretation

DoS

denial of service

DPRAM

dual-port RAM

DR

Designated Router System Messages for Cisco IOS Release 12.2 SX

GL-8

OL-xxxxx-xx

Glossary

DR

dynamic replenishment

DRAM

dynamic RAM

DRDA

Distributed Relational Database Architecture

DRiP

Duplicate Ring Protocol

DRP

Director Response Protocol

DRQ

Direct memory access Receive Queue

DS

dial shelf

DSA

delayed stop accounting

DSC

dial shelf control

DSC

dial shelf controller

DSCP

differentiated service code pointer

DSI

dial shelf interconnect

DSI

dial shelf interface

DSIP

Dial Shelf Interconnect Protocol

DSL

digital subscriber line

DSLAM

digital subscriber line ATM multiplexer

DSMP

Distributed Stream Media Processor

DSP

digital signal processor

DSP

Domain Specific Part

DSP

digital signal processor

DSPFARM

digital signal processor farm

DSPM

digital signal processor module

DSPRM

Digital Signal Processor Resource Manager

DSPU

downstream physical unit

DSR

data set ready

DSU

data service unit

DSU

digital service unit

DTE

data terminal equipment

DTP

Dynamic Trunking Protocol System Messages for Cisco IOS Release 12.2 SX

OL-xxxxx-xx

GL-9

Glossary

DTQ

Direct memory access Receive Queue

DTR

data terminal ready

DVMRP

Distance Vector Multicast Routing Protocol

E1T1

E1 line or T1 line

EADI

Extended Availability Drop and Insert

EAIM

Encryption AIM

EAP

Extensible Authentication Protocol

EAPoUDP

Extensible Authentication Protocol over User Datagram Protocol

EARL

enhanced address recognition logic

EC

EtherChannel

ECA

ESCON Channel Adapter

ECC

error-correcting code

ECC

Error-Check Code

ECC

error checking and correction

ECM

Extensible Call Model

ECM

External Control Memory

EEM

Embedded Event Manager

EEPROM

electronically erasable programmable read-only memory

EFC

extended flow control

EGP

exterior gateway protocol

EHSA

enhanced high system availability

EID

endpoint identifier

EIGRP

Enhanced Interior Gateway Routing Protocol

EIO

Elastic I/O

ELAN

emulated LAN

ENUM

enumeration

E


GL-10

OL-xxxxx-xx

Glossary

ENVM

Constellation WAN Environmental Monitor

EOBC

Ethernet Out-of-Band Channel

EOC

embedded operations channel

EOF

end-of-frame

EOIR

enhanced online insertion and removal

EoMPLS

Ethernet over MPLS

EOU

Extensible Authentication Protocol over User Datagram Protocol

EPM

External Packet Memory

ESCON

Enterprise System Connection

ESMP

Even Simpler Management Protocol

ESP

Extended Services Processor

ESP

Extended Services Platform

ESW

Ethernet Switch

ESWILP

Ethernet Switch with Inline Power

ETM

Enhanced Timing Module

EXAR

Chip manufacturer

FAQ

frequently asked question

FB

feature board

FBB

fast back-to-back

FBB

from backplane buffer

FCFS

First Come First Served

FCIT

Fiber Channel Idle Time

FC-PFQ

feature card per-flow queueing

FCPA

Fibre Channel Port Adapter

FCS

frame check sequence

FDDI

Fiber Distributed Data Interface

F


GL-11

Glossary

FDL

Facility Data Link

FDM

frequency-division multiplexing

FE

Fast Ethernet

FEC

Fast EtherChannel

FECPM

Fast Ethernet Combo Port Module

FI

format indicator

FIA

Fabric Interface ASIC

FIB

forwarding information base

FIFO

first-in, first-out

FIR

Finite Impulse Response

FM

fault monitoring

FMSP

Fax Media Services Provider

FO1

fragment offset == 1

FPGA

field-programmable gate array

FPI

Forwarding Path Identifier

FQDN

fully qualified domain name

FQPCID

fully qualified procedure correlation identifier

FREEDM

Frame EnginE and Data link Manager

FRMR

Frame Reject

FRoM

FrameRelay over MPLS

FRoMPLS

FrameRelay over MPLS

FRR

Fast ReRoute

FRU

field-replaceable unit

FSIP

Fast Serial Interface Processor

FSM

finite state machine

FTBB

from/to backplane buffer

FTP

File Transfer Protocol


GL-12

OL-xxxxx-xx

Glossary

G GBIC

Gigabit Interface Converter

GC

global configuration

GDS

general data stream

GE

Gigabit Ethernet

GEFC

Gigabit Ethernet/Fibre Channel

GEIP

Gigabit Ethernet Interface Processor

GGSN

gateway GPRS support node

GKTMP

Gatekeeper Transaction Message Protocol

GLBP

Gateway Load Balancing Protocol

GLC

gigabit line card

GP

Global Pointer

GPRS

general packet radio service

GRP

gigabit route processor

GSN

GPRS support node

GSR

Internet router

GTF

Generalized Trace Facility

GTP

GPRS tunneling protocol

GULF

GULF-2488 ASIC

HA

High Availability

HA

Home Agent

HAL

Halcyon

HAPX

Hardware Assisted Packet Classification

HDLC

High-Level Data Link Control

HDV

High Density Voice

H


GL-13

Glossary

HDX

half-duplex

HEC

header error control

HGW

home gateway

HMAC

hash message authentication codes

HMS

Home Media Server

HPI

Host Port Interface

HPR

High-Performance Routing

HQF

Hierarchical Queuing Framework

HSA

high system availability

HSRP

Hot Standby Router Protocol

HSSI

High Speed Serial Interface

HT-FPGA

Hyper Transport Field-Programmable Gate Array

HWAF

Hardware Address Filtering

HWIC

High-Speed WAN Interface Card

HWICD

High-Speed WAN Interface Card, double-wide

HWIDB

hardware interface descriptor block

I2C

Inter-Integrated Circuit

IDB

interface descriptor block

IBGP

internal BGP

IBL

Input Buffer Logic

IBOC

in-band bit-oriented code

ICC

Inter Card Communication

ICC

Interface Controller Card

ICMP

Internet Control Message Protocol

ICPIF

Calculated Planning Impairment Factor

ICS

Integrated Communication System

I


GL-14

OL-xxxxx-xx

Glossary

IDAP

Internet Data Access Presentation

IDB

interface descriptor block

IDPROM

Identification PROM

IDS

Internal Data Services

IDT

Integrated Digital Terminal

IDU

indoor unit

IE

information element

IEEE

Institute of Electrical and Electronics Engineers

IETF

Internet Engineering Task Force

IF

intermediate frequency

IGMP

Internet Group Management Protocol

IGRP

Interior Gateway Routing Protocol

IIF

Input interface

IIH

IS to IS Hello PDU

IKE

Internet Key Exchange

ILMI

Integrated Local Management Interface

ILP

inline power

ILPM

inline power module

IMA

inverse multiplexing over ATM

IMSI

international mobile subscriber identity

IP

Internet Protocol

IPC

interprocess communication

IPDC

Internet Protocol device control

IPDLC

IP data link connection

IPE

Inter-PRE Ethernet

IPG

Inter Packet Gap

IPHC

IP Header Compression

IPM

Cisco Internetwork Performance Monitor

IPPCP

IP Payload Compression Protocol System Messages for Cisco IOS Release 12.2 SX

OL-xxxxx-xx

GL-15

Glossary

IPRM

IP Router Manager

IPS

IP Storage

IPSec

IP Security

IPv6

IP version 6

IPX

Internetwork Packet eXchange

ISA

Integrated Services Adapter

ISAKMP

Internet Security Association and Key Management Protocol

ISDN

Integrated Services Digital Network

ISE

Internet Services Engine

IS-IS

Intermediate System-to-Intermediate System

ISL

Inter-Switch Link

ISR

intermediate session routing

ISRHOG

Interrupt Service Routine HOG

ISSU

In-Service Software Upgrade

IST

Internal Spanning Tree

IVR

interactive voice response

IXP

Internet Exchange Point

L2

Layer 2

L2F

Layer 2 Forwarding

LAC

L2TP access concentrator

LACP

Link Aggregate Control Protocol

LAIS

SONET Line-level Alarm Indication Signal

LANCE

Local Area Network Controller Ethernet

LANE

LAN Emulation

LAPB

Link Access Procedure, Balanced

LAT

local-area transport

L


GL-16

OL-xxxxx-xx

Glossary

LC

line card

LCATM

Label controlled ATM

LCB

Line Control Block

LCC

Line card Configuration Coordinator

LCD

liquid crystal display

LCDOS

line card operating system software

LCI

local channel identifier

LCN

logical channel number

LDLC

LocalDirector link control

LDN

local directory number

LDP

Label Distribution Protocol

LEC

LANE Client

LECS

LANE Configuration Server

LED

light-emitting diode

LEN

low-entry networking

LES

LANE Server

LFD

Label Forwarding Database

LFSID

local-form session identifier

LIR

link incident report

LIU

line interface unit

LLC

logical link control

LLC2

Logical Link Control, type 2

LLD

low level design

LMI

Local Management Interface

LNM

LAN Network Manager

LNS

L2TP network server

LOF

Loss of Frame

LOS

Loss of Signal

LPD

line printer daemon System Messages for Cisco IOS Release 12.2 SX

OL-xxxxx-xx

GL-17

Glossary

LRC

line card redundancy controller

LRJ

location rejection

LRQ

location request

LS

LightStream

LSA

link-state advertisement

LSD

label switching database

LSIPC

LightStream interprocess communication

LSP

label switch path

LSP

link-state packet

LSP

Link-State PDU

LSS

LightStream switching

LTL

local target logic

LU

logical unit

LU6.2

logical unit type 6.2

LVC

label switched controlled virtual circuits

LYRA

Constellation+ Advanced Forwarding Engine Layer2

MAC

Media Access Control

MAR

Midrange Access Routers

MARS

Multicast Address Resolution Server

MATM

MAC Address Table Manager

MAU

media attachment unit

MAX

maximum

MBE

multiple-bit error

MBRI

Multi-BRI

MBRI

Multiport Basic Rate Interface

MBus

maintenance bus

M


GL-18

OL-xxxxx-xx

Glossary

MCNS

Multimedia Cable Network System Partners, Ltd.

MCOM

Microcom carrier card

MCDMA

Multi-Channel DMA

MCSC

Multi-Channel Serial Controller

MD5

message digest 5

MDB

Multicast Descriptor Block

MDL

maintenance data link

MDRR

Modified Deficit Round Robin

MDS

multicast distributed switching

MDSS

Multicast Distributed Shortcut Switching

MDT

multicast distribution tree

MEMD

memory device

MFD

Multicast Fast Drop

MFE

Multi-port Fast Ethernet

MFI

MPLS forwarding infrastructure

MFIB

Multicast Forwarding Information Base

MGCP

Media Gateway Control Protocol

MIB

Management Information Base

MIB/SMT

Management Information Base/Station Management

MIC

media interface connector

MICA

Modem ISDN channel aggregation

MID

Multiplex ID

MIDB

multicast interface data block

MII

media-independent interface

MLD

Multicast Listener Discovery

MLP

Multilink Point-to-Point Protocol

MLPPP

Multilink Point-to-Point Protocol

MLS

multilayer switching

MLSM

multilayer switching for multicast System Messages for Cisco IOS Release 12.2 SX

OL-xxxxx-xx

GL-19

Glossary

MLTG

multilink trunk group

MMAP

memory map

MMI

Modem Management Interface

MMLS

multicast multilayer switching

MNCNS

Multimedia Cable Network System Partners, Ltd.

MNP4

Microcom Networking Protocol 4

MP

Multilink Protocol

MPC

MultiPath Channel

MPC

Multiprotocol-over-ATM client

MPLS

Multiprotocol Label Switching

MPOA

Multiprotocol over ATM

MPPE

Microsoft Point to Point Encryption

MPS

Multiprotocol-over-ATM server

MQC

Modular Quality of Service (QoS) command line interface (CLI)

MRIB

Multicast Routing Information Base

MRP

Multiservice Routing Processor

MPT

Ministry of Posts and Telecommunications

mroute

Multicast route

MS

Management Services

MS

mobile subscriber

MSC

Modular Services Card

MSDP

Multicast Source Discovery Protocol

MSFC

Multilayer Switch Feature Card

MSP

Media Service Provider

MSR

Multiservice Switch Router

MSS

maximum segment size

MST

Multiple Spanning-Tree Protocol

MSTOO

multiple spanning tree root

Mtree

matings tree


GL-20

OL-xxxxx-xx

Glossary

MTU

maximum transmission unit

MURIB

Multicast Unicast Routing Information Base

mutex

mutual exclusivity lock

MVIP


MWAM

Multi-Processor WAN Application Module

Mx

Mueslix

NAK

negative acknowledgment

NAM

Network Analysis Module

NAS

network access server

NAT

Network Address Translation

NBAR

network-based application recognition

NBP

Name Binding Protocol

NCE

network connection endpoint

NCP

Network Control Program

NCP

Network Control Protocol

NEAT

E1 and T1 processor

NFAS

Non Facility Associated Signaling

NHDR

Network Layer Header

NHRP

Next Hop Resolution Protocol

NHS

Next Hop Server

NIM

network interface module

NIP

Nitro Interconnect Protocol

NLP

network-layer packet

NLSP

NetWare Link Services Protocol

NM

network module

NM-HD

high density network module

N


GL-21

Glossary

NME

Network Management Ethernet

NMI

nonmaskable interrupt

NMP

Network Management Processor

NMS

network management system

NMVT

network management vector transport

NNI

Network-to-Network Interface

NNS

network node server

NPE

network processing engine

NRM

normal response mode

NRP

Network Routing Processor

NRP

node route processor

NSAP

network service access point

NSDB

Network Security Database

NSE

network services engine

NSF

Non-stop forwarding

NSP

Network Switch Processor

NSP

node switch processor

NTP

Network Time Protocol

NVRAM

nonvolatile RAM

OAM

Operation, Administration, and Maintenance

OBL

Output Buffer Logic

OC

Optical Carrier

OCE

output chain elements

ODU

outdoor unit

OER

Optimized Edge Routing

OFC

open fiber control

O


GL-22

OL-xxxxx-xx

Glossary

OIF

Output interface

OIR

online insertion and removal

ONS

Optical Networking Systems

OOBP

out-of-band port

OOD

Online Offline Diagnostics

OOS

out of service

ORF

outbound route filter

OSCP

Optical Supervisory Channel Protocol

OSM

Optical Services Module

OSP

Open Settlements Protocol

OSPF

Open Shortest Path First

OSS

Operations Support System

OU

organizational unit

PA

port adapter

PAD

packet assembler/disassembler

PAgP

Port Aggregation Protocol

PAM

port adapter module card

PAM

pulse amplitude modulation

PAN

4-Port and (8+1) Port ESWILP HWIC

PAP

Password Authentication Protocol

PASCB

port adapter system control block

PASV

passive mode FTP

PBP

packet-by-packet

PC

program counter

PCA

Parallel Channel Adapter

PCF

Packet Control Function

P


GL-23

Glossary

PCF

Profile Configuration File

PCI

protocol control information

PCID

procedure correlation identifier

PCM

pulse code modulation

PCMCIA

Personal Computer Memory Card International Association

PCR

peak cell rate

PDP

policy decision point

PDSN

Packet Data Serving Node

PDU

protocol data unit

PEMF

Power Entry Module and Filter

PF

protocol filtering

PGM

Pragmatic General Multicast

PHAD

Physical Layer Interface Module (PLIM) header add-drop ASIC

PHY

physical layer interface

PIC

Peripheral Interface Controller

PIC

point in call

PIE

protocol information element

PIF

Packet Input FIFO

PIM


PIM-SM

Protocol Independent Multicast Sparse Mode

PIMv2

Protocol Independent Multicast version 2

PIU

PCM Interface Unit

PKCS

Public Key Cryptographic Standards

PKI

public key infrastructure

PLD

programmable logic device

PLIM

Physical Layer Interface Module

PLU

primary logical unit

PLX

PCI to local bus bridge vendor

PM

port management System Messages for Cisco IOS Release 12.2 SX

GL-24

OL-xxxxx-xx

Glossary

PMA

Packet Memory Access

PMB

power management bus

PMC

PCI Mezzanine Card

PMON

Performance Monitor

PNNI

Private Network-Network Interface

PNSP

Partial Number Sequence PDUs

POE

Power Over Ethernet

PoS

Packet over SONET

PoS

Packet over SONET/SDH

POST

power-on self test

POT1E1

Packet Over T1 E1

POTS

plain old telephone service

PPC

primary point code

PPP

Point-to-Point Protocol

PQUICC

Quad Integrated Communications Controller

PRBS

Pseudo-Random Bit Sequence

PRE

Performance Routing Engine

PRI

Primary Rate Interface

PROM

programmable read-only memory

PRP

Performance Route Processor

PSA

Packet Switching ASIC

PSC

processor and switch card

PSM

Protection Switch Module

PSNP

Partial Sequence Number PDU

PTB

Peer Transaction Bus

PU

physical unit

PU 2.0

Physical Unit type 2.0

PU 2.1

Physical Unit type 2.1

PVC

permanent virtual circuit System Messages for Cisco IOS Release 12.2 SX

OL-xxxxx-xx

GL-25

Glossary

PVC

permanent virtual connection

PVDM

Packet Voice DSP Module

PVID

Port VLAN ID

PVP

permanent virtual path

PVST+

Per-VLAN Spanning Tree

PXF

Parallel eXpress Forwarding

PXM

Processor Switching Module

QA

queue and accumulator

QEM

QEM driver

QLLC

Qualified Logical Link Control

QM

QoS manager

QMAC

Quad Token Ring Media Access Controller ASIC

QoS

quality of service

RA

registration authority

RAC

Resource Availability Confirm

RAC

Ring Access Controller

RADIUS

Remote Authentication Dial-In User Service

RARP

Reverse Address Resolution Protocol

RAS

Registration, Admission, and Status

RAS

remote access server

RBCP

Router Blade Configuration Protocol

RBD

receive buffer descriptor

RBS

Robbed-Bit Signaling

RCP

remote copy protocol

Q

R


GL-26

OL-xxxxx-xx

Glossary

RDB

relational database

RED

redundancy

REQACTPU

request to activate a physical unit

REQDACTPU

request to deactivate a physical unit

REQ(D)ACTPU (RSP)

Route Switch Processor request to activate or deactivate a physical unit

REXEC

remote execution

RF

radio frequency

RF

Redundancy frequency

RIB

Routing Information Base

RIP

Routing Information Protocol

RISC

reduced instruction set computing

RJE

remote job entry

RLM

Redundant Link Manager

RMON

Remote Network Monitoring

RNR

receive not ready

ROM

read-only memory

RP

Route Processor

RPA

Resource Pool Allocation

RPC

Remote Procedure Call

RPF

Reverse Path Forwarding

RPM

Route Processor Module

RPM

Resource Pool Management

RPMXF

Route Processor Module, express forwarding

RPR

Route Processor Redundancy

RPR+

Route Processor Redundancy plus

RPS

Ring Parameter Server

RR

receive ready

RRP

Redundant Route Processor


GL-27

Glossary

RS

router shelf

RS-232

EIA/TIA-232

RSA

Rivest, Shamir, and Adelman (a public-key cryptographic system)

RSC

route switch controller

RSCPB

RSC front panel push button

RSCV

Route Selection Control Vector

rsh

remote shell

RSL

remote switch link

RSM

Route Switch Module

RSP

Route Switch Processor

RSPAN

Remote Switched Port Analyzer

RSRB

remote source-route bridging

RSRC

Resource

RSVP

Resource Reservation Protocol

RTAL

Receive Telecombus Aligner/Interface

RTC

real-time console

RTM

Real Time Monitor

RTP

Rapid Transport Protocol

RTP

Real-Time Transport Protocol

RTR

response time reporter

RTS

Request To Send

RTT

round-trip time

RTTMON

Round Trip Time Monitor

RU

request/response unit

RUDP

Reliable User Data Protocol

Rx

Receive

RXP

Resonate Exchange Protocol


GL-28

OL-xxxxx-xx

Glossary

S SA

security association

SA

Source-Active

SA

Service Assurance

SADB

security association database

SAF24

SAR adapter FPGA OC24

SAFI

Subsequent Address Family Identifier

SAP

service access point

SAR

segmentation and reassembly

SBE

single-bit error

SCB

storage control blocks

SCB

system control board

SCC

Signaling Connection Control

SCCP

Signaling Connection Control Part

SCM

Service Connection Manager

SCP

Service Control Point

SCP

Switch-Module Configuration Protocol

SCP

System Control Protocol

SCR

sustained cell rate

SDCC

Serial Data Communication Channel

SDEE

Security Device Event Exchange

SDF

Signature Definition File

SDLC

Synchronous Data Link Control

SDLLC

Synchronous Data Logical Link Control

SDM

Security Device Manager

SDP

Session Description Protocol

SDP

Shelf Discovery Protocol

SDRAM

synchronous DRAM


GL-29

Glossary

SDT

Start Data Transfer

SEF

severely errored frames

SERDES

Serializer-Deserializer

SFC

switch fabric card

SFP

Small Form Factor Pluggable

SGBP

Stack Group Bidding Protocol

SGCP

Simple Gateway Control Protocol

SGSN

Serving GPRS Support Node

SID

Service ID

SIMM

single in-line memory module

SIP

Session Initiation Protocol

SLARP

Serial Line Address Resolution Protocol

SLB

Server Load Balancing

SLC

signaling link code

SLCI

Signaling Link Code Interface

SLIC

Subscriber Line Interface Circuit

SLIP

Serial Line Internet Protocol

SLU

secondary logical unit

SM

sparse mode

SM

state machine

SMbus

System Management bus

SMDS

Switched Multimegabit Data Service

SME

Signature Micro Engine

SMRP

Simple Multicast Routing Protocol

SMTP

Simple Mail Transfer Protocol

SNA

Systems Network Architecture

SNASw

SNA Switching Services

SNMP

Simple Network Management Protocol

SNR

signal-to-noise ratio


GL-30

OL-xxxxx-xx

Glossary

SNRM

Set Normal Response

SO-DIMM

Small Outline Dual In-line Memory Modules

SOF

start-of-frame

SOP

Second-Generation Packet-over-SONET

SP

Switch Processor

SPA

Shared Port Adapter

SPACP

SPA bus communications protocol

SPAN

Switched Port Analyzer

SPD

Security Policy Database

SPE

service processing element

SPI

security parameter index

SPI4

System Packet Interface Level 4

SPID

service profile identifier

SPM

source path message

SPMM

SIMM DSP module

SRA

source routing accelerator

SRAM

static RAM

SRC

Switch Redundancy Controller

SRCP

Simple Resource Coordination Protocol

SRDB

source route relational database

SRIC

Sculptor Input Controller

SRIF

Sculptor Interface

SROC

Sculptor Output Controller

SRP

Server Redundancy Protocol

SRP

Spatial Reuse Protocol

SRR

Single Ring Recovery Protocol

SSA

Serial Storage Architecture

SSCOP

Service-Specific Connection-Oriented Protocol

SSCP

system services control points System Messages for Cisco IOS Release 12.2 SX

OL-xxxxx-xx

GL-31

Glossary

SSE

silicon switching engine

SSG

Service Selection Gateway

SSH

Secure Shell

SSL

Secure Socket Layer

SSM

Single State Mode

SSM

Source Specific Multicast

SSO

Stateful SwitchOver

SSP

Silicon Switch Processor

SSP

state synchronization protocol

SSRAM

synchronous static RAM

SSRP

Simple Server Redundancy Protocol

SSS

Subscriber Service Switching

SSTP

Shared Spanning-Tree Protocol

STP

Spanning-Tree Protocol

STUN

serial tunnel

SU

service unit

SU

signaling unit

SVC

switched virtual circuit

SVI

switched virtual interface

SVIP

Versatile Interface Processor 2

SW56

switched 56K

SWIDB

software for Interface Descriptor Block

SYSMGT

system management

TAC

Cisco Technical Assistance Center

TACACS

Terminal Access Controller Access Control System

TBB

to backplane buffer

T


GL-32

OL-xxxxx-xx

Glossary

TBI

Ten Bit Interface

TBM

Transmit Buffer Manager

TCA

telecommunications access method

TCATM

Tag Control ATM

TCAM

Ternary Content Addressable Memory

TCB

Transmission Control Block

TCL

Toolkit Command Language

TCP

Transmission Control Protocol

TDM

time-division multiplexing

TDP

Tag Distribution Protocol

TDR

time domain reflectometer

TE

terminal equipment

TE

traffic engineering

TE

tunnel equipment

TE3

T3 or E3

TED

Tunnel Endpoint Discovery

TEI

terminal endpoint identifier

TFIB

Tag Forwarding Information Base

TFTP

Trivial File Transfer Protocol

TG

transmission group

TIB

Tag Information Base

TIM

Tree Information Base

TIC

Toaster Input Controller

TID

Terminal Identifier

TIFF

tagged image file format

TLB

translation look-aside buffer

TLV

type, length, value

TMQ

terminal port queueing

ToS

Type of Service System Messages for Cisco IOS Release 12.2 SX

OL-xxxxx-xx

GL-33

Glossary

TP

Transport Protocol

TR

Token Ring

TRANGE

time-range

TSC

Tag Switch Controller

TSCAM

Traffic Shaping Carrier Access Module

TSI

transmitting subscriber information

TSP

tag-switched path

TT2RP

Toaster-to-RP

TTAL

Transmit Telecombus Aligner/Interface

TTL

time to live

TVC

tag switched controlled virtual circuit

TVC

tag virtual circuits

Tx

transmit

UA

unnumbered acknowledgement

UART

Universal Asynchronous Receiver/Transmitter

UCB

University of California, Berkeley

Ucode

Microcode

UDLD

UniDirectional Link Detection

UDP

User Datagram Protocol

UPS

uninterruptible power supply

URM

Universal Router Module

uRPF

Unicast Reverse Path Forwarding

VACL

VLAN access control list

VAD

voice activity detection

U

V


GL-34

OL-xxxxx-xx

Glossary

VBR

variable bit rate

VBR-nRT

variable bit rate—non-real time

VC

virtual circuit

VCC

virtual channel connection

VCD

virtual circuit descriptor

VCCI

Virtual Channel Common Index

VCHAN

virtual channel

VCI

virtual channel identifier [ATM only]

VCN

virtual circuit number

VFC

voice feature card

VFC

VoIP feature card

VFR

Virtual Fragment Reassembly

VG

voice gateway

VIC

voice interface card

VIP


VLAN

virtual LAN

VMAC

Virtual MAC

VMPS

VLAN Membership Policy Server

VMR

value, mask, result

VNM

Voice Network Manager

VOA

variable optical attenuator

VoIP

Voice over IP

VP

virtual path

VPC

virtual path connection

VPD

voice packet driver

VPDN

Virtual Private Dialup Network

VPI

virtual path identifier

VPLS

Virtual Private LAN Service

VPN

Virtual Private Network System Messages for Cisco IOS Release 12.2 SX

OL-xxxxx-xx

GL-35

Glossary

VPNv4

Virtual Private Network version 4

VQP

VLAN Query Protocol

VQPC

VQP client

VRF

VPN Routing and Forwarding

VRRP

Virtual Router Redundancy Protocol

VSI

Virtual Switch Interface

VSM

Voice Service Manager

VT

virtual terminal

VTAM

virtual telecommunications access method

VTMS

Versatile Traffic Management and Shaping

VTP

VLAN Trunk Protocol

VTSP

voice telephony service provider

VTT

voltage termination

VWIC

Voice/WAN interface card

WCCP

Web Cache Communication Protocol

WCS

writable control store

WDS

Wireless Domain Services

WIC

WAN interface card

WLM

Workload Manager

WRED

Weighted Random Early Detection

WWW

World Wide Web

XCA

external communication adapter

XCVR

transceiver

XDR

eXternal Data Representation

W

X


GL-36

OL-xxxxx-xx

Glossary

XID

exchange identification

XML

eXtensible Markup Language

XNS

Xerox Network Systems

XOT

X.25-over-TCP

XTagATM

extended tag ATM

ZBT

zero bus turnaround

Z


GL-37

Glossary


GL-38

OL-xxxxx-xx

System Messages for Cisco IOS Release 12.2 SX

System Messages for Cisco IOS Release 12.2 SX

Suggest Documents

Cisco IOS XE System Messages

Cisco IOS CMTS Cable System Messages Guide

Cisco IOS H.323 Configuration Guide, Cisco IOS Release 12.4T

Caveats for Cisco IOS Release 15.1(3)

SIP Configuration Guide, Cisco IOS Release 12.4T

IPv6 Configuration Guide, Cisco IOS Release 12.4T

DBUS Messages - Cisco

sx sx sx sx sx sx sx sx sx sx sx sx

Cisco IOS Packaging for Switches

TCL Scripting for Cisco IOS

Cisco IOS Software Release 12.4(2)T Feature Sets for Cisco 7200 ...

Cisco IOS Software Release 12.4(2)T Feature Sets for Cisco 7200 ...

Cisco IOS Firewall

Cisco IOS Basic Skills

Cisco IOS XR Workbook

MPLS Basic MPLS Configuration Guide, Cisco IOS XE Release 3S

MPLS Layer 3 VPNs Configuration Guide, Cisco IOS Release 12.4

QoS: Classification Configuration Guide, Cisco IOS XE Release 3S

IPv6 Configuration Guide, Cisco IOS Release 15.2 MT

QoS: Classification Configuration Guide, Cisco IOS XE Release 3S

IP Addressing: NAT Configuration Guide, Cisco IOS Release 12.4T

MPLS LDP Configuration Guide, Cisco IOS Release 12.4

Cisco IOS Switching Services Command Reference, Release 12.2

Book-level PDF: Cisco IOS IP Configuration Guide, Release 12.2