System Error Messages for 12.0 T

How to Read System Error Messages

Error Messages

System Error Messages for 12.0 T

This chapter lists and describes the system error messages for Cisco IOS Release 12.0 T, up to and including 12.0(7)T. The system software sends these error messages to the console (and, optionally, to a logging server on another system) during operation. Not all system error messages indicate problems with your system; some are purely informational, while others may help diagnose problems with communications lines, internal hardware, or the system software.

This chapter only lists error messages for Cisco IOS Release 12.0 T that are not documented in the Cisco IOS Release 12.0 Cisco IOS Software System Error Messages manual. For additional system error messages, refer to the Cisco IOS Software System Error Messages manual.

How to Read System Error Messages

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 error message is followed by an explanation and a recommended action.

System error messages begin with a percent sign (%) and are structured as follows:

%FACILITY-SEVERITY-MNEMONIC: Message-text

FACILITY is a code consisting of two or more uppercase letters that indicates 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 facilities codes.

SEVERITY 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.

MNEMONIC is a code that uniquely identifies the error 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 error message:

%LINK-2-BADVCALL: Interface [chars], undefined entry point

Some error messages also indicate the card and slot reporting the error. These error messages begin with a percent sign (%) and are structured as follows:

%CARD-SEVERITY-MSG:SLOT %FACILITY-SEVERITY-MNEMONIC: Message-text

CARD is a code that describes the type of card reporting the error. VIP and FEIP are possible card types.

MSG is a mnemonic that indicates 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 numeral. (For example, SLOT5.)

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

Code	Facility
AAA	TACACS+ authentication, authorization, and accounting security
ADJ	Adjacency subsystem
AIP	ATM Interface Processor
ALIGN	Memory optimization in Reduced Instruction-Set Computer (RISC) processor
ALPS	Airline Protocol Support
AMDP2	AMDP2 Ethernet and Fast Ethernet
APPN	Advanced Peer-to-Peer Networking
ARAP	Apple Remote Access Protocol
ASPP	Asynchronous Security Protocol
AT	AppleTalk
ATM	Asynchronous Transfer Mode
ATMCES	ATM access concentrator PCI port adapter driver
ATMCORE	ATM core
ATMOC3	ATM OC-3 network module
ATMPA	ATM port adapter
ATMSIG	ATM signalling subsystem
ATMSSCOP	ATM Service Specific Connection Oriented Protocol (SSCOP)
AUTORP	PIMv2 AUTORP
BAP	PPP Bandwidth Allocation Protocol (BAP)
BCM3220	Cable modem MAC controller interface
BGP	Border Gateway Protocol
BRI	Integrated Services Digital Network (ISDN) Basic Rate Interface
BRIMUX	AS5200 BRIMUX board
BSC	Binary Synchronous Communications mode
BSTUN	Block serial tunneling
C1400	Cisco 1400 platform
C1600	Cisco 1600 platform
C1700	Cisco 1700 platform
C2KATM	Catalyst 2820 ATM module
C3600	Cisco 3600 platform
C542	Voice driver for modular access routers
C5RSP	Cisco Catalyst 5000 platform
C7200	Cisco 7200 platform
C29ATM	Catalyst 2900XL ATM Module
C54x	VoIP DSp Driver
CAIM	Compression Advanced Interface Module
CALL_MGMT	Call management subsystem
CALLRECORD	Modem Call Record
CASA	Content Aware Services Architecture
CBUS	ciscoBus controller
CDM	Cable Data Modem subsystem
CDP	Cisco Discovery Protocol
CE3	CE3 port adapter
CES	Circuit Emulation Service
CI	Cisco 7500 platform chassis interface
CIPDUMP	CIP core dump
CIRRUS	CD2430 asynchronous controller
CIRRUS_PM	Slow speed asynchronous/synchronous port module
CLEAR	Clear facility
CLNS	OSI Connectionless Network Service
CLOCKSW	Cisco 6400 network clocking
CLS	Cisco Link Services
CLSDR	Cisco Link Services Driver
CM622	ATM line card driver
CMCC	Cisco Mainframe Channel Connection interfaces
CM_DSPRM	Digital Signal Processor Resource Manager
CNSES	Cisco Network Services Event Service Client
COMP	Point-to-point compression
CONTROLLER	Controller
COT	Continuity test
CPAD	Compression service adapter
CPM	Combo Port Module device driver
CRYPTO	Encryption
CSC2	CSC2/CSC3 CPU cards
CSM	Call switching module
CSM_VOICE	Telephony voice calls on the PSTN interface
CT3	Channelized T3 port adapter
CTRC	Cisco Transaction Connection
DBCONN	Database Connection
DBUS	Data bus
DCU	ATM access concentrator PCI port adapter
DEC21140	DEC21140 Fast Ethernet controller
DHCPD	DHCP Server
DIALER	Dial-on-demand routing
DIALSHELF	Dial shelf messages
DIRECTOR	Director server
DLC	Data-link control
DLSw	Data-link switching
DLSWMasterSlave	Data Link Switching Master Slave
DLSWP	Data Link Switching Peer
DMA	Direct Memory Access
DMTDSL	Digital/discrete multitone digital subscriber line
DNET	DECnet
DNSSERVER	DNS server
DRIP	Duplicate RIng Protocol
DRP	Director Response Protocol
DRVGRP	Interface driver
DSCCLOCK	Dial shelf controller clock
DSC_ENV	Cisco AS5800 environment monitor
DSC_REDUNDANCY	Cisco AS5800 dial shelf controller redundancy
DSCEXTCLOCK	Dial shelf controller clock
DSCREDCLK	Dial shelf controller redundancy clock
DSI	Cisco AS5800 dial shelf interconnect board
DSPDD	Digital Signal Processor Device Driver
DSPU	Downstream physical unit
DS_TDM	Dial Shelf Time Division Multiplex
DSX0	CT1 RBS timeslot status
DSX1	Channelized E1 (Europe) and T1(US) telephony standard
DUAL	Enhanced Interior Gateway Routing Protocol
DVMRP	Distance Vector Multicast Routing Protocol
E1T1	E1T1 Module
EGP	Exterior Gateway Protocol
EHSA	Cisco 6400 Enhanced High System Availability
ENSP	Enhanced Network Service Provider
ENT_API	Entity MIB API
ENV	Environmental monitor card
ENV_MON	Cisco 12000 environmental monitor
EPAD	Encryption port adapter driver
ESWITCH	Ethernet switch port adapter
ETHERNET	Ethernet for the C1000 series
EXPRESSION	Expression MIB
FAN	Fan
FB	Cisco AS5800 feature board
FBINFO	Cisco 5800 feature board crash information subsystem
FDDI	Fiber Distributed Data Interface
FILESYS	File system
FLASH	Flash nonvolatile memory
FPGA	LS1010 chip-specific
FR	Frame Relay
FREEDM	CT3 trunk card Freedm
FR_ELMI	Frame Relay enhanced Local Management Interface
FR_LMI	Frame Relay Local Management Interface
FTC_TRUNK	Cisco 3801 platform
FTPSERVER	FTP server processes
FTSP	Fax Telephony Service Provider Subsystem
FW	Inspection subsystem
FX1000	FX1000 Gigabit Ethernet controller
GRIP	Xerox Network Systems (XNS) Routing Protocol
GRP	Gigabit route processor
GRPGE	Gigabit Ethernet GRP driver
GRP_OC12_CH_DS3	OC-12-CH-DS3 route processor driver
GRPPOS	POS route processor
GSR_ENV	Gigabit Switch Router environment monitor
GSRIPC	Gigabit Switch Router IPC service routines
GT64010	GT64010 DMA controller driver
HAWKEYE	Token Ring PCI port adapter
HD	HD64570 serial controller
HDV	High Density Voice driver
HMM_ASYNC	Hex modem network module asynchronous driver
HOOD	LAN controller 100VG-AnyLAN interface
HP100VG	100VG-AnyLAN PA driver
HUB	Cisco Ethernet hub
IBM2692	IBM Token Ring chipset
IDTATM25	IDT ATM25 network module
IFS	IOS File System
IGRP	Interior Gateway Routing Protocol
ILACC	ILACC driver
IMA	Inverse multiplexing for ATM
INTERFACE_API	Binary API for the interface descriptor block
IOCARD	I/O CARD-specific
IP	Internet Protocol
IPACCESS	IP security
IPC	Interprocess communication
IPCGRP	RP interprocess communication
IPCLC	Gigabit Switch Router line card interprocess communication
IPC_RPM	Interprocess communication
IPC_RSP_CBUS	Interprocess communication
IPFAST	IP fast switching
IPFLOW	IP flow
IPM_C54X	Voice over IP driver
IPMCAST	Gigabit Switch Router line card IP multicast
IPMOBILE	IP Mobility
IPRT	Internet Protocol routing
IP-SNMP	Simple Network Management Protocol specific to IP
IPX	Internetwork Packet Exchange protocol
ISA	Integrated Service Port Adapter, a hardware accelerator for IPSEc
ISDN	Integrated Services Digital Network
KINEPAK	Voice over IP for Cisco AS5800
LANCE	Local Area Network Controller Ethernet
LANE	LAN Emulation
LANMGR	IBM LAN Network Manager
LAPB	X.25 Link Access Procedure, Balanced
LAT	DEC local-area transport
LC	Line card
LCB	Line Control Block event process
LCCEF	ATM Cisco Express Forwarding (CEF) adjacency
LCFE	Fast Ethernet LC driver
LCGE	Gigabit Ethernet line card driver
LCOC12_CH_DS3	GSR OC-12-channelized-to-DS3 line card
LES_FDDI	LAN Emulation Server/Fiber Distributed Data Interface
LEX	LAN extension
LIBT2F	Text to fax library
LIBTIFF	Tag Image File Format (TIFF) library
LINEPROTO	Line Protocol
LINK	Data link
LLC2	Logical link control type 2
LLIST	Linked list facility
LNMC	LAN network manager
LPD	Line printer daemon
M32X	M32X Basic Rate Interface trunk card
MAILBOX	ChipCom mailbox support
MBRI	Multi-BRI port module
MBUS	Maintenance bus
MBUS_SYS	MBUS system
MCI	Multiport Communications Interface
MEMSCAN	Memory scan
MICA	Modem ISDN Channel Aggregation modem
MIF68840	PCI MC68840 FDDI port adapter
MIMIC	MCOM integrated modem network modules
MK5	MK5025 serial controller
MMODEM	Integrated modem network module
MODEM	Router shelf modem management
MODEM_HIST	Router shelf modem history/tracing
MODEM_NV	Modem NVRAM
MPA68360	VIP Multi-channel Port Adapter
MROUTE	Multicast route
MSDP	Multicast Source Discovery Protocol
MUESLIX	Mx serial application-specific integrated circuit (ASIC)
MXT_FREEDM	8PRI/4T board
NETWORK_CLOCK	Network clock synchronization
NHRP	Next Hop Resolution Protocol
NIC100	NIC100 driver
NIM	Network interface module
NRP	Network Routing Processor
NSP	Node Switch Processor
NSP_OIR	NSP online insertion and removal
OIR	Online insertion and removal
OOBP	Out of band port
OSPF	Open Shortest Path First
PA	Port adapter
PAD	X.25 packet assembler/disassembler
PAMMBOX	Port adapter module mailbox platform-independent messages
PARSER	Parser
PERUSER	PPP per-user configuration
PIM	Protocol-independent multicast
PLATFORM	Platform-specific
PNNI	Private Network-Network Interface
POSDW	Packet over SONET double wide PCI port adapter driver
POT1E1	VIP multichannel port adapter
PPP	Point-to-Point Protocol
PQUICC	MPC860 quad integrated communications controller
PQUICC_ETHER	Ethernet MPC860 quad integrated communications controller ethernet
PQUICC_FE	Fast Ethernet MPC860 quad integrated communications controller
PQUICC_SERIAL	Serial MPC860 quad integrated communications controller serial
PS	Power supply
QA	Queue and accumulator
QEM	QEM driver
QLLC	Qualified Logical Link Control
QUICC	MC68360 quad integrated communications controller
QUICC_ASYNC	Asynchronous MC68360 quad integrated communications controller
QUICC_Ethernet	Ethernet MC68360 quad integrated communications controller
QUICC_SERIAL	Serial MC68360 quad integrated communications controller
RADIUS	Remote Access Dial-In User Service (RADIUS) facility
RADIX	Radix facility
RCMD	Remote commands
RIP	IP Routing Information Protocol
RM	Resource Manager
RPA	Resource Pool Allocation
RPM_VIRTUAL_PORT	RPM virtual port
RPS	Redundant power supply
RRR_RCALC	RRR path calculation
RSP	Route Switch Processor
RSRB	Remote source-route bridging
RTT	Round trip time monitor
SAR Manager	Segmentation and reassembly manager
S4T68360	Four-port synchronous serial adapter based on the 68360 processor
SCHED	Scheduler
SDLC	Synchronous Data Link Control
SDLLC	SDLC/logical link control type 2 (LLC2) translation
SEC	IP security
SERVICE_MODULE	Service module
SGCP	Simple Gateway Control Protocol
SGBP	Stack Group Bidding Protocol
SHELF	Router shelf
SLIP	Serial Line Internet Protocol
SLOTDUMP	Slot dump
SMF	Software MAC Filter
SMRP	Simple Multicast Routing Protocol
SNAPSHOT	Snapshot dial-on-demand routing
SNASW	SNA Switching Services
SNMP	Simple Network Management Protocol
SNMP_MGR	SNMP Proxy
SONET	Synchronous Optical Network
SONETMIB	Synchronous Optical Network Management Information Base
SPARC	3800 SPARC coprocessor subsystem
SSE	Silicon switching engine
STANDBY	Hot Standby Router Protocol (HSRP)
STUN	Serial tunneling
SUBSYS	Software subsystems
SW56	Switch 56K
SWITCH	Switch interface
SYS	Operating system
SYSCTLR	System controller subsystem
SYSLOG_SERVER	Syslog-server file system routines
SYSMGT	System management
TAC	Terminal Access Controller Protocol Access Control System
TAGCON	Tag distribution and control
TBRIDGE	Transparent bridging
TCATM	ATM TAG control
TCP	Transmission Control Protocol
TDM	Time-division multiplexing
TDP	Tag Distribution Protocol
TE_LDPB	Traffic engineering loop prevention
TFIB	Tag Forwarding Information Base
TI1570	PCI/TI1570-based ATM port adapter
TIB	Tag Information Base
TMQ	Inbound terminal port queueing
TN	Telnet
TN3270	TN3270 protocol
TR	Token Ring
TRAFFENG	Traffic engineering
TRUNK	E1/T1 trunk card
TSP_TUNNEL	Tag switch path (TSP) tunnel
TTYDRIVER	Router shelf asynchronous driver
TUN	Tunnel
UBR7200	Cable modem termination system
UCODE	Microcode
UNIX	UNIX
UTIL	Utility
VINES	Banyan VINES
VIP	Versatile Interface Processor
VOICE_FSM	MC3810 voice FSM subsystem
VOICE_RC	MC3810 voice resource subsystem
VPDN	Virtual Private Dialup Networking
VPM	Voice port module
VPN	Virtual Private Dialup Network
X25	X.25
XCPA	Mainframe Channel Port Adapter

Table 2: Error 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

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

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

Table 3: Representation of Variable Fields in Error 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

[inet]

Internet address (for example, 12.128.2.16)

[int]

Integer number

[node]

Address or node name

[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 number (hex or decimal)

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
[inet]	Internet address (for example, 12.128.2.16)
[int]	Integer number
[node]	Address or node name
[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 number (hex or decimal)

Error Messages

This section lists error messages alphabetically by facility and mnemonic.

Error Message

%AAAA-6-ACCTSTART: [chars]

Explanation A AAA accounting start message.

Recommended Action This is an informational message only.

Error Message

%AAAA-6-ACCTSTOP: [chars]

Explanation A AAA accounting stop message.

Recommended Action This is an informational message only.

Error Message

%AAAA-6-ACCTWATCH: [chars]

Explanation A AAA accounting watchdog/update message.

Recommended Action This is an informational message only.

Error Message

%AAAA-6-ADMINMSG: [chars] [chars]: [chars]

Explanation This administrative message passed to the network access server from the AAA server.

Recommended Action No action need be taken, but the message may contain useful information regarding some event on the server.

Error Message

%AAAA-3-BADCOMM: Trying config command but should not be

Explanation An internal error occurred.

Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%AAAA-3-BADREG: Illegal registry call

Explanation An internal error occurred.

Error Message

%AAAA-4-BADSGNAME: Bad server-group name [chars] (type [chars])

Explanation The given server-group name either does not exist or the given type does not match the defined server-group.

Recommended Action Verify that the group exists and has the same type.

Error Message

%AAAA-3-ILLEGALNAME: Illegal [chars] [chars] name [chars] rejected

Explanation A method-list name should not be the same as a method name.

Recommended Action Choose a different method-list name (that is not a method-name).

Error Message

%AAAA-3-ILLSGNAME: Illegal server-group name [chars] (type [chars])

Explanation The given server-group name is a name that could conflict with internally chosen lists.

Recommended Action Choose a different server-group name.

Error Message

%AAAA-3-INTERNAL_ERROR: [chars]

Explanation An internal software error occurred.

Error Message

%AAAA-3-LISTCREATE: The list [dec] for [chars] is NULL. This should never be

Explanation One of the method-lists, created at startup, was not created. This may cause a reload.

Error Message

%AAAA-3-NOREG: [chars] method [dec] has no registry

Explanation An internal error occurred.

Error Message

%AAAA-3-NOSERV: No name for servergroup in method [chars]

Explanation An internal error occurred.

Error Message

%AAAA-4-NOSERVER: Warning: Server [int] is not defined

Explanation The given server is not on the master-list and should be defined, or unexpected events might happen.

Recommended Action Define the server on the appropriate master-list as soon as possible.

Error Message

%AAAA-3-NOSG: No server-group passed through parser

Explanation An internal error occurred.

Error Message

%AAAA-6-SERVERMSG: [chars] [chars]: [chars]

Explanation This message passed to the network access server from the AAA server.

Recommended Action No action is required. However, the message may contain useful information regarding some event on the server.

Error Message

%AAAA-4-SERVUNDEF: The server-group [chars] is not defined, please define it

Explanation A given server-group was listed in a method-list and was not defined first. Server-groups should be defined before use.

Recommended Action Define the server-group before using it.

Error Message

%ALC-3-CMDERR: ([dec]/[dec]) Interface ([chars]): [chars] IPC command fails (cause: 0x[hex])

Explanation The ATM RP driver experienced an IPC command error.

Recommended Action Copy the error message exactly as it appears, and report it to your Cisco technical support representative.

Error Message

%ALC-3-EVENT: ([dec]/[dec]) Interface ([chars]): unknown IPC event ([int]) from line card

Explanation The ATM RP driver received an unknown event from the line card.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%ALC-4-HIRATE: ([dec]/[dec]) Interface ([chars]): SAR limits VBR VC PCR to [dec] kbps, opening UBR VC instead

Explanation The SAR limits VBR VC PCR to one-half of the link bandwidth.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%ALC-4-NULLCEFIDB: ([dec]/[dec]) Interface ([chars])

Explanation CEF IDB is missing from the interface.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%ALC-4-UNSUP: ([dec]/[dec]) Interface ([chars]): unsupported feature: [chars]

Explanation This feature is not supported by GSR ATM RP.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%ALC-3-VCADJ: ([dec]/[dec]) Per-VC adjacency error: VC:[int] [chars]

Explanation The ATM RP driver experienced a per-VC adjacency software error.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%ALC-3-VCENCTYPE: ([dec]/[dec]) VC:[int] unknown VC encapsulation type ([int])

Explanation The ATM RP driver experienced an unknown VC encapsulation software error.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

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-PEER_BUSY_END: Peer ([int], [chars]) has excited a congested state

Explanation An ALPS peer connection no longer is experiencing congestion.

Recommended Action No action is required.

Error Message

%ALPS-6-PEER_BUSY_START: Peer ([int], [chars]) has entered a congested state

Explanation An ALPS peer connection is experiencing congestion.

Recommended Action No action is required.

Error Message

%ALPS-5-PEER_CLOSED: Peer ([int], [chars]) changed state to closed

Explanation An ALPS peer connection is now closed.

Recommended Action No action is required.

Error Message

%ALPS-5-PEER_CLOSED_DYNAMIC_INACTIVITY: Peer ([int], [chars]) closed due to inactivity

Explanation An ALPS peer connection now is closed because of inactivity.

Recommended Action No action is required.

Error Message

%ALPS-5-PEER_CONN_ID_CHANGE: Peer ([int], [chars]) ID modified to ([int], [chars])

Explanation An ALPS peer connection identifier changed.

Recommended Action No action is required.

Error Message

%ALPS-7-PEER_DROPS_MAX_SIZE_EXCEEDED: Threshold exceeded for maximum size exceeded drops for peer ([int], [chars])

Explanation The number of ALPS peer drops that are caused by the maximum size being exceeded exceeds the ALPS peer threshold value.

Recommended Action No action is required.

Error Message

%ALPS-7-PEER_DROPS_PEER_UNREACHABLE: Threshold exceeded for peer unreachable peer drops for peer ([int], [chars])

Explanation The number of ALPS peer drops that are caused by 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 ([int], [chars])

Explanation The number of ALPS peer drops that are caused by queue overflow exceeds the ALPS peer threshold value.

Recommended Action No action is required.

Error Message

%ALPS-7-PEER_DROPS_VERSION_MISMATCH: Threshold exceeded for version mismatch peer drops for peer ([int], [chars])

Explanation The number of ALPS peer drops that are caused by a version mismatch exceeds the ALPS peer threshold value.

Recommended Action No action is required.

Error Message

%ALPS-5-PEER_OPEN: Peer ([int], [chars]) changed state to open

Explanation An ALPS peer connection is now open.

Recommended Action No action is required.

Error Message

%ALPS-6-PEER_OPEN_FAIL: Peer ([int], [chars]) open failed, rsn = [chars]

Explanation An ALPS peer connection attempted to open, but failed.

Recommended Action No action is required.

Error Message

%AMDP2_FE-4-BABBLE: AMDP2/FE 0/0/[dec], Babble error

Explanation The sender has been on the channel longer than the time taken to send the largest frame.

Recommended Action The system should recover. No action is required.

Error Message

%AMDP2_FE-5-COLL: AMDP2/FE 0/0/[dec], Excessive collisions, TDR=[dec], TRC=[dec]

Explanation The Ethernet/Fast Ethernet interface is experiencing multiple collisions. This may occur under heavy loads.

Recommended Action The system should recover. No action is required.

Error Message

%AMDP2_FE-5-CONFIGNOT: The Internal Ethernet Interface is not configurable

Explanation The internal Ethernet is for system use only.

Recommended Action No action is required.

Error Message

%AMDP2_FE-1-INITFAIL: AMDP2/FE 0/0/[dec], Init failed, CSR[dec]=0x[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

%AMDP2_FE-5-LATECOLL: AMDP2/FE 0/0/[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 mode. For regular Ethernet, the system should recover. No action is required.

Error Message

%AMDP2_FE-5-LOSTCARR: AMDP2/FE 0/0/[dec], Lost carrier, possible transceiver problem

Explanation The cable or transceiver is not connected.

Recommended Action Connect the cable or transceiver.

Error Message

%AMDP2_FE-1-MEMERR: AMDP2/FE 0/0/[dec], Memory error, CSR[dec]=0x[hex]

Explanation The interface could not access system resources for a long time. This message 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

%AMDP2_FE-2-NOISL: Interface [chars] does not support ISL

Explanation The interface cannot be configured as an ISL trunk.

Recommended Action Check the configuration of the router.

Error Message

%AMDP2_FE-1-NOMII: AMDFE 0/0/[dec], MII Interface transceiver not connected

Explanation The MII transceiver disconnected while the MII port was selected.

Recommended Action Connect the transceiver and enter the shut down and no shut down commands for the interface in the configuration menu.

Error Message

%AMDP2_FE-3-NOTAMDP2: Device reported [hex]

Explanation The software could not recognize the interface chips.

Recommended Action Power down, reseat the interface card, and reboot. If the message recurs, call your technical support representative for assistance.

Error Message

%AMDP2_FE-3-OVERFLO: AMDP2/FE 0/0/[dec], Receive overflow

Explanation While receiving a frame, the local buffer of the controller chip sent insufficient data because data could not be transferred to DRAM fast enough to keep pace with its input rate. Such a problem usually is temporary, depending on transient peak loads within the system.

Recommended Action The system should recover. No action is required.

Error Message

%AMDP2_FE-3-OWNERR: AMDP2/FE 0/0/[dec], Buffer ownership error, pak=0x[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.

Error Message

%AMDP2_FE-3-SPURIDON: AMDP2/FE 0/0/[dec], Spurious IDON interrupt, CSR[dec]=0x[hex]

Explanation An illegal condition indicating initialization done has occurred.

Recommended Action Clear the interface. If this message recurs, call your technical support representative for assistance.

Error Message

%AMDP2_FE-4-SPURIOUS: AMDP2/FE 0/0/[dec], Spurious interrupt error

Explanation An illegal condition was encountered during initialization.

Recommended Action The system should recover. No action is required.

Error Message

%AMDP2_FE-3-UNDERFLO: AMDP2/FE 0/0/[dec], Transmit underflow

Explanation While sending a frame, the local buffer of the controller chip received insufficient data because data could not be transferred to the chip fast enough to keep pace with its output rate. Such a problem usually is temporary, depending on transient peak loads within the system.

Recommended Action The system should recover. No action is required.

Error Message

%ATMSIG-3-ATMSIG_LISTEN_FAILED_DUP: Duplicate LISTEN by [chars] for existing NSAP [chars] owned by [chars]

Explanation An application attempted to either LISTEN on a network service access point (NSAP) owned by another application or to LISTEN for the same NSAP twice.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%ATMPA-3-BADPARTICLE: [chars]: bad rx particle 0x[hex] flags 0x[hex] index [dec]

Explanation The port adapter host driver detected a duplicate rx host buffer returned.

Error Message

%ATMSIG-3-DBINITFAIL: Signalling control block initialization failure, [chars]

Explanation An internal software or resource error occurred.

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.

Error Message

%BGP-3-AFIINDEX: Address family index inconsistent in the neighbor [int] [dec] [dec]

Explanation This message indicates an internal data structure inconsistency.

Recommended Action This is a rare situation and is a result of an internal problem. The problem should be reported to your Cisco technical support representative.

Error Message

%BGP-3-BADROUTEMAP: Bad parameters in the route-map [chars] applied for [chars]

Explanation The route-map should be changed.

Recommended Action Correct the route-map.

Error Message

%BGP-3-DELPATH: Attempted to delete path from an empty net for [chars]

Explanation A BGP path could not be deleted because of an error.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%BGP-3-DELROUTE: Unable to remove route for [chars] from radix trie

Explanation A deletion from the radix trie could not be completed because of an error.

Error Message

%BGP-4-MAXPFX: No. of prefix received from [int] (afi [dec]) reaches [dec], max [dec]

Explanation The number of prefixes received from a neighbor reached the warning limit.

Recommended Action Check the number of prefixes received from the neighbor and determine if the limit should be increased.

Error Message

%BGP-3-MAXPFXEXCEED: No. of prefix received from [int] (afi [dec]): [dec] exceed limit [dec]

Explanation The number of prefixes received from a neighbor exceeds the configured limit.

Recommended Action Check the number of prefixes received from the neighbor and determine if the limit should be increased.

Error Message

%BGP-3-NEGCOUNTER: Prefix-accepted counter negative for peer [int], prefix [chars]

Explanation The counter value for accepted prefixes is incorrect and less than zero.

Recommended Action This is a rare situation and is a result of an internal problem. Reset the session to correct it.

Error Message

%BGP-5-VERSION_WRAP: bgp version wrapped of [chars]

Explanation The BGP table version reached its maximum value and wrapped around. The message describes this event.

Recommended Action This message is informational. However, frequent occurrences of this event might indicate high error rates or high packet loss in the network, and should be investigated.

Error Message

%BSTUN-4-DUPROUTE: Cannot define duplicate route on the same group

Explanation This route command is defined on another interface belonging to the same group. A duplicate route cannot be defined Son the same group.

Recommended Action Consider defining a new group and moving this interface onto that group.

Error Message

%C1700-3-BADIMAGE: The IOS image loaded supports voice. The platform you are running is not voice capable

Explanation The voice-capable Cisco IOS detects that it is running on a platform that does not support voice.

Recommended Action Check the image and the platform. If you must use voice, you should get a C1750. If you will not use voice, you should load an image that does not include voice.

Error Message

%C1700-1-OVERTEMP: System detected OVERTEMPERATURE condition. Putting the system in Power save mode and going to rommon. Please resolve cooling problem and restart system!

Explanation The environmental monitor detected a high-temperature condition.

Recommended Action Ensure that the room temperature is not too high and that air flow to the card is not blocked. If this condition persists, the environmental monitor might shut down the system. Call your technical support representative for assistance, if necessary.

Error Message

%C29ATM-4-AT_DEBUG: [chars]: [chars] : [dec]

Explanation Address Table Management.

Error Message

%C29ATM-4-AT_DEBUG_MAC: [chars]: [chars] : [sci_notation]

Explanation Address Table Management.

Error Message

%C29ATM-4-AT_DEBUG_TB: [chars]: [chars] : [dec]

Explanation Address Table Management.

Error Message

%C29ATM-4-AT_VLAN_DEBUG: [chars]: [chars] : [dec]

Explanation Address Table Management.

Error Message

%C29ATM-4-BIG_CONTROL_FRAME: AAL5 discarded because it is too large to buffer: vpi = [dec], vci = [dec], size = [dec]

Explanation An AAL5 frame destined for Cisco IOS was discarded because it was too large to buffer.

Error Message

%C29ATM-4-NOVCINFO: [chars] discarded because it is not associated with a VCD: vpi = [dec] vci = [dec]

Explanation An OAM cell or an AAL5 frame was discarded because it was not associated with a VCD.

Recommended Action Check the configuration of your ATM switch.

Error Message

%C29ATM-3-OUT_BAD_VCD: The module attempted to transmit frame on a closed or non-existent VCD: vcd = [dec]

Explanation The module attempted to send a frame on a closed or nonexistent VCD.

Error Message

%C29ATM-3-OUT_OF_VCD: Cannot create VCC for [chars], run out of VCD

Explanation The module was unable to create a VCC for the specified service.

Error Message

%C54x-1-NO_RING_DESCRIPTORS: No more ring descriptors available on [dec] slot.

Explanation The C54X DSP driver cannot queue messages up to the DMA engine for transmission.

Error Message

%C54x-1-TOOBIG: [chars], packet(size [dec]) too big

Explanation A packet greater than the 256 bytes was received on this interface.

Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%C3600-3-CHASSIS: Unknown chassis model

Explanation Data stored in midplane is invalid or incomplete.

Recommended Action Call your Cisco technical support representative to update your system.

Error Message

%C3600-4-COOKIE: Corrupt or missing MAC address cookie using random base [sci_notation]

Explanation Data stored in midplane is invalid.

Recommended Action Call your Cisco technical support representative to update your system.

Error Message

%C3600-4-MACBLKSIZE: Unknown MAC address block size

Explanation Data stored in backplane is invalid or incomplete.

Recommended Action Call your Cisco technical support representative to update your system.

Error Message

%C3600-3-SLOTS: Number of slots in chassis are undefined

Explanation Data stored in midplane is invalid or incomplete.

Recommended Action Call your Cisco technical support representative to update your system.

Error Message

%C3600-4-VERSION_MISMATCH: Midplane data version mismatch

Explanation Data stored in midplane is out of date and needs to be updated.

Recommended Action Call your Cisco technical support representative to update your system.

Error Message

%CAIM-1-HIFNERR: Caim [int]: Hifn 9711 Errors reported: 9711 Status 0x[hex] DMA status 0x[hex]

Explanation The specified CAIM reported an Hifn9711 error.

Recommended Action This is an indication of a serious malfunction of the compression AIM or of the system bus. The compression AIM should be replaced.

Error Message

%CAIM-1-HIFNREV: Compression AIM type in slot [int] is not supported by this platform

Explanation The compression AIM installed is not supported by this platform.

Recommended Action Power down and replace the compression AIM card.

Error Message

%CASA-4-BADMSG: Message parsing error: [chars] [chars]

Explanation Failed to parse an incoming packet.

Recommended Action If this message is occurring repeatedly, enter the debug ip casa error command and record the output. Call your Cisco technical support representative and provide the gathered information.

Error Message

%CASA-3-BADVER: Incoming packet is CASA v[dec], this router is v[dec]

Explanation A packet was received for the wrong version of CASA.

Recommended Action Verify that all CASA devices are running the same version of the protocol.

Error Message

%CASA-2-NOMEM: Out of memory: [chars]

Explanation CASA failed to allocate memory.

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

Error Message

%CASA-4-PORTCHANGE: Wildcard overlap: [chars]

Explanation A CASA wildcard, received on one port, was overwritten by a service manager sending to another port. This message may appear once if you are migrating your service to a new forwarding-agent port. If the error recurs, it could indicate a configuration problem.

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

Error Message

%CASA-4-SECURITY_FAIL: [chars] security information in CASA packet [chars]

Explanation A security check failed.

Recommended Action Make sure all CASA systems are configured with the same password.

Error Message

%CASA-4-UNEXPECTED: Unexpected error: [chars]

Explanation An unexpected error occurred while the CASA operation was being performed.

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

Error Message

%CBUS-5-INPUTERR: Interface [chars] excessive input error rate

Explanation The interface was disabled because too many input errors occurred.

Recommended Action Inspect the condition of the attached network hardware.

Error Message

%CES-2-INTERNAL_CRITICAL: [chars], CES_COMPLAIN_IVL

Explanation The CES subsystem encountered an internal software error. The error message contains text that can be used to help identify the nature of the problem.

Error Message

%CES-3-INTERNAL_ERROR: [chars], CES_COMPLAIN_IVL

Explanation The CES subsystem encountered an internal software error. The error message contains text that can be used to help identify the nature of the problem.

Error Message

%CES-4-INTERNAL_WARNING: [chars], CES_COMPLAIN_IVL

Explanation The CES subsystem encountered an internal software error. The error message contains text which can be used to help identify the nature of the problem.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message

%CI-3-ASPMEM: LS1010 equipped with [chars] requires at least [dec] MB of RAM Only [dec] MB of RAM installed

Explanation An LS1010 equipped with the specified feature card requires a minimum amount of memory to be installed.

Recommended Action Upgrade to the memory configuration recommended in the message.

Error Message

%CI-5-ASPREV: Hot swapping the ASP will cause hardware damage

Explanation This message will appear as a reminder during LS1010 or C5X00 startup. The ASP is NOT hot-swappable on the LS1010 even though it is hot-swappable on C5X00 platforms. Removing an ASP from an LS1010 while the system is operating causes the system to shut down and might cause hardware damage to the ASP. Also, if this warning appears on a C5X00, the ASP that is installed is not hot-swappable, so the same warning applies.

Recommended Action Do not remove a non hot-swappable ASP while the power is on.

Error Message

%CI-3-ASPREVC5500: Can not determine Power Supply type/detect Power Supply fan alarm

Explanation This message will appear as a reminder during C5X00 startup. The revision of the ASP installed in the router is unable to provide information about the power supply type and fan status.

Recommended Action If this is considered a cause for concern, call your Cisco technical support representative.

Error Message

%CI-3-BLOWER: Fan failure

Explanation A route cooling fan may have failed or may be close to failure.

Recommended Action Replace the fan as soon as possible or the system may shut itself down or fail to operate properly.

Error Message

%CI-6-BLOWEROK: Fan OK

Explanation The specified fan has changed status to an acceptable condition. This is an informational message only. It will be displayed after replacement of a bad fan or any time the software determines a failure condition has ended.

Recommended Action No action is required.

Error Message

%CI-3-FCTYPE: Can not recognize Feature Card

Explanation The Cisco IOS software found an unrecognized Feature Card during LS1010 initialization. This could mean that a hardware failure caused an actual failure to determine the card type, or that the software needs to be upgraded to support hardware that did not exist yet at the time the software was written.

Error Message

%CI-1-NOFORK: Could not start environment polling daemon

Explanation System initialization failed to start the task that monitors the internal chassis environment. This is probably due to a low-memory condition. System operation is continuing without environment polling. This problem demands immediate attention because it could allow damaging conditions such as over-temperature to go undetected.

Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Reboot the system to restart the environment polling daemon.

Error Message

%CI-6-PSCHANGE: Power supply [int] changed from [chars] to [chars]

Explanation This is an informational message only that indicates the absence or detection of a new type of power supply in the system. This can be expected when hot-swappable power supplies are swapped.

Recommended Action No action is required.

Error Message

%CI-6-PSFANOK: Power supply fan [int] OK

Explanation This is an informational message only that indicates the specified power supply fan changed status to an acceptable condition. It will be displayed after replacement of a bad power supply or any time the software determines a failure condition has ended.

Recommended Action No action is required.

Error Message

%CI-6-PSOK: Power supply [int] OK

Explanation This is an informational message only that indicates the specified power supply has changed status to an acceptable condition. It will be displayed after replacement of a bad power supply or any time the software determines a failure condition has ended.

Recommended Action No action is required.

Error Message

%CI-3-PSTYPE: , , Incompatible power supply types - One is AC, the other is DC

Explanation Mixing AC and DC power supplies is not supported.

Recommended Action Change power supplies to match one another.

Error Message

%CI-3-SHUTDOWN: Shutting down due to over temperature

Explanation The system reached a shutdown temperature level, and the router is being shut down to avoid any damage.

Recommended Action Attempt to resolve the temperature problem. If the problem is not resolved, call your Cisco technical support representative for assistance.

Error Message

%CI-3-TEMP: Overtemperature warning

Explanation The temperature sensor indicates a high-temperature condition.

Recommended Action Make sure that the room temperature is not too high and that airflow to the chassis is not blocked. If this condition persists, the system will shut itself down to avoid damage. Call your Cisco technical support representative for assistance, if necessary.

Error Message

%CI-6-TEMPOK: Temperature OK

Explanation The temperature sensor indicates that the chassis air temperature has returned to acceptable levels.

Recommended Action No action is required.

Error Message

%CI-3-VOLTAGE: Voltage out of range

Explanation The voltage has reached a critical level and is now out of specification.

Recommended Action Verify the failure and call your Cisco technical support representative for repair or replacement.

Error Message

%CI-6-VOLTAGEOK: Voltage OK

Explanation The voltage level has changed status to an acceptable condition.

Recommended Action No action is required.

Error Message

%CIRRUS-4-DOWNREV_NM: Network Module card in slot [dec] is incompatible with the system

Explanation The network module in this slot is an old revision that is not compatible with this system. Please upgrade that network module.

Error Message

%CLNS-5-ADJCLEAR: [chars][chars]: All [chars]adjacencies cleared

Explanation All Intermediate System-to-Intermediate System (IS-IS) or NetWare Link Services Protocol (NLSP) adjacencies of the specified type were cleared. This message appears only if the log-adjacency-changes command is configured for the IS-IS or NLSP process.

Recommended Action This informational message appears after appropriate console or configuration commands.

Error Message

%CLNS-3-ONLIST: ISIS: entry already threaded, prev [hex], next [hex], area = [chars] , index [dec], ver [dec]

Explanation An internal error occurred in the Intermediate System-to-Intermediate System (IS-IS) or NetWare Link Services Protocol (NLSP).

Error Message

%CM622_CM155-4-ATMCLKINT: ([dec]/[dec]) ATM Clock Internal Set on ([dec]/[dec]) too

Explanation CM155 ATM Clock Internal is enabled for the other channel on the same framer. The framer defines one bit for both channels.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%CM622_CM155-4-FRMROP: Error: ([dec]/[dec]) [chars] (value=0x[hex])

Explanation Line card ATM driver framer operation errors occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%CM622_CM155-4-FWCKSUM: [chars] SAR firmware selftest failure (expected 0x[hex], obtained 0x[hex])

Explanation Line card ATM SAR firmware checksum errors occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%CM622_CM155-4-OP: Error: ([dec]/[dec]) [chars]

Explanation Line card ATM driver general operation errors occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%CM622_CM155-4-RPCMD: [chars] command error: [chars]

Explanation Line card ATM driver handles RP command errors occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%CM622_CM155-4-RXSARIND: ([dec]/[dec]) RX SAR doing [chars] error: [chars] (indication=0x[hex] 0x[hex] 0x[hex])

Explanation Line card ATM driver RX SAR indication errors occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%CM622_CM155-4-SAROP: [chars] SAR doing [chars] error: [chars]

Explanation Line card ATM driver SAR operation errors occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%CM622_CM155-4-TXSARIND: TX SAR [chars] command error: [chars] (indication=0x[hex])

Explanation Line card ATM driver TX SAR indication errors occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%CM622_CM155-4-VCCLOSE: ([dec]/[dec]) VC:[int] is close pending

Explanation The VC is in the TX SAR close pending state.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%CM622_CM155-4-VCCMD: ([dec]/[dec]) VC:[int] [chars] error (cause: [chars])

Explanation A CM622/CM155 ATM SAR VC operation error occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%CM622_CM155-4-VCTYPE: ([dec]/[dec]) VC:[int] unsupported vc encapsulation type=[int]

Explanation A CM622/CM155 ATM SAR VC operation error occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%CM_DSPRM-1-INTERNALERROR: DSPRM internal error[[chars]:[dec]

Explanation The router or access server detected an internal error.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%CM_DSPRM-1-NODSPRMEVENTS: DSPRM event unavailable

Explanation The router or access server could not allocate internal resources.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%CM_DSPRM-1-NOIOSBUFFERS: IOS buffer pool unavailable [[chars]:[dec]]

Explanation The router or access server could not allocate internal resources.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%CM_DSPRM-1-NOIOSMEMORY: IOS memory unavailable [[chars]:[dec]]

Explanation The router or access server could not allocate memory for internal data structures.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%CRYPTO-6-IKMP_NO_ID_CERT_ADDR_MATCH: ID of %15i (type [dec]) and certificate addr with %15i

Explanation Internet Security Association and Key Management Protocol (ISAKMP) entities assume an identity to inform the peer of who or what they are. The claimed identity did not match the information gleaned from the IP address of the certificate of the peer.

Recommended Action Contact the remote peer if this situation persists.

Error Message

%CRYPTO-6-IKMP_NO_ID_CERT_DN_MATCH: ID of [chars] (type [dec]) and certificate DN with [chars]

Recommended Action Contact the remote peer if this situation persists.

Error Message

%CRYPTO-6-IKMP_NO_ID_CERT_FQDN_MATCH: ID of [chars] (type [dec]) and certificate fqdn with [chars]

Recommended Action Contact the remote peer if this situation persists.

Error Message

%CRYPTO-6-IKMP_NO_ID_CERT_USER_FQDN_MATCH: ID of [chars] (type [dec]) and certificate user fqdn with [chars]

Recommended Action Contact the remote peer if this situation persists.

Error Message

%CRYPTO-3-IKMPPAKFAIL: Failed to build reply packet

Explanation The user is unable to build a packet as part of an Internet Key Exchange (IKE) due to a shortage of memory, or a failure of the encryption engine (hardware or software).

Error Message

%CRYPTO-3-IKMP_PEER_INIT_FAILURE: IKE failed to create IKE peer tree.

Explanation IKE failed to allocate memory for the Internet Key Exchange (IKE) peer tree.

Recommended Action More DRAM may be required in order to run the image.

Error Message

%CSM_VOICE-3-ADDINTRFFAIL: The Voice Telephony Service Provider has rejected our request to add this voice interface ([dec]/[dec]:[dec])

Explanation The voice software was unable to report a new signalling interface to the voice telephony service provider.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message

%CSM_VOICE-3-MALLOC: No memory is available to build any internal data structure for the voice software

Explanation The voice software was unable to allocate memory to build any internal data structures. The system may be out of memory.

Error Message

%CSM_VOICE-3-NOMEM: No memory is available to build the voice interface ([dec]:[dec])

Explanation The voice software was unable to allocate memory to build a voice interface data structure. The system may be out of memory.

Error Message

%CSM_VOICE-3-NOSDB: No signaling data block is available to build the voice interface([dec]/[dec]:[dec])

Explanation The voice software was unable to obtain a signalling data block from the voice telephony service provider. The system may be out of memory.

Error Message

%CSM_VOICE-3-UNDEFDSX0: Undefined dsx0 interface for controller([dec]/[dec])

Explanation The dsx0 interface for the specified controller is not defined but the voice software use it.

Recommended Action This is an internal software fault. Contact your Cisco technical support representative if this message is coincident with dropped calls.

Error Message

%CSM_VOICE-3-UNDEFVOICEINTRF: Invalid interface slot:controller:group([dec]/[dec]:[dec])

Explanation The voice interface defined by the slot:controller:group command is not yet defined within the voice software but attempts were made to use this interface.

Recommended Action This is an internal software fault. Contact your Cisco technical support representative if this message is coincident with dropped calls.

Error Message

%CTRC-3-APPCERROR: [chars]

Explanation An unexpected APPC error occurred. The CTRC uses APPC API calls to SNASW to communicate with the remote database server.

Recommended Action This message usually indicates a problem in the Systems Network Architecture (SNA) network. Enter the ctrc ping command to test connectivity to the remote database server. If the ctrc ping fails, check the status of the SNA link to the remote database server with the show snasw link command. If the link is active, try stopping and starting the link. If the problem persists, contact your SNA network administrator for help in troubleshooting. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.If possible, also provide the output of the debug ctrc appc command and an SNA line trace between the router and the remote database server, for the period during which this message appeared.

Error Message

%CTRC-3-APPCVERB: Unexpected APPC error: opcode [hex], primary code [hex], secondary code [hex]

Explanation An unexpected APPC error occurred. The CTRC uses APPC API calls to SNASW to communicate with the remote database server. Opcode identifies the APPC API call that received the error. Primary and secondary return codes are returned by the APPC API.

Recommended Action This message usually indicates a problem in the Systems Network Architecture (SNA) network. Enter the ctrc ping command to test connectivity to the remote database server. If the ctrc ping command fails, check the status of the SNA link to the remote database server with the show snasw link command. If the link is active, try stopping and starting the link. If the problem persists, contact your SNA network administrator for help in troubleshooting. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information. If possible, also provide the output of the debug ctrc appc command and an SNA line trace between the router and the remote database server, for the period during which this message appeared.

Error Message

%CTRC-4-APPCWARN: [chars]

Explanation An unexpected APPC error occurred. The CTRC uses APPC API calls to SNASW to communicate with the remote database server.

Recommended Action This error message usually indicates a temporary problem in the SNA network. Enter the ctrc ping command to test connectivity to the remote database server. If the ctrc ping command fails, check the status of the SNA link to the remote database server with the show snasw link command. If the link is active, try stopping and starting the link. If the problem persists, contact your SNA network administrator for help in troubleshooting. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information. If possible, also provide the output of the debug ctrc appc command, and an SNA line trace between the router and the remote database server, for the period during which this message appeared.

Error Message

%CTRC-3-SNASWNOTSTARTED: SNASW is not started --- unable to connect to remote database.

Explanation A client connected to a CTRC server, but the CTRC server was unable to connect out to the remote database because SNASW is not started. CTRC uses SNASW to connect to the remote database server. You must start SNASW before the CTRC clients attempt to connect.

Recommended Action Start the SNASW and retry the client connection.

Error Message

%CTRC-3-SNASWSTOPPED: SNASW was stopped --- existing connections have been closed

Explanation SNASW was stopped while CTRC connections were open. Stopping SNASW caused all open SNA connections to the remote database server to be lost. As a result, all client connections were disconnected. You should not stop SNASW while there are open CTRC connections.

Recommended Action Restart SNASW. Disconnected clients must reconnect.

Error Message

%DBCONN-3-LICENSEEXPERROR: License is expired for Database and Transaction Connection

Explanation This system is using a temporary key for its Database and Transaction Connection. The license is expired.

Recommended Action Contact StarQuest Software to acquire a permanent key.

Error Message

%DBCONN-3-LICENSEEXPWARNING: License is about to expire for Database and Transaction Connection

Explanation This system is using a temporary key for its Database and Transaction Connection. The license is about to expire.

Recommended Action Contact StarQuest Software to acquire a permanent key.

Error Message

%DBCONN-3-LICENSEHWWARNING: Number of connections for TXCONN and DBCONN is at 90%% license limit

Explanation The number of allowed Database and Transaction Connection client in this system is reaching the limit.

Recommended Action Contact StarQuest Software to acquire more licenses.

Error Message

%DBCONN-5-PWDEXPIRED: APPC security failed, client [int] using userid '[chars]' for server [chars]

Explanation The password passed in by the client was rejected by the remote database server because it is expired.

Recommended Action This is an informational message only. No action is required.

Error Message

%DBCONN-5-PWDINVALID: APPC security failed, client [int] using userid '[chars]' for server [chars]

Explanation The password passed in by the client was rejected by the remote database server.

Recommended Action This is an informational message only. No action is required.

Error Message

%DBCONN-5-PWDMISSING: APPC security failed, client [int] using userid '[chars]' for server [chars]

Explanation The remote database server requires a user ID and password, but the password was not provided.

Recommended Action This is an informational message only. No action is required.

Error Message

%DBCONN-5-SECUNKNOWN: APPC security failed, client [int] using userid '[chars]' for server [chars]

Explanation An unspecified security failure occurred. The database host system may be able to provide more specific information.

Recommended Action This is an informational message only. No action is required.

Error Message

%DBCONN-5-UIDINVALID: APPC security failed, client [int] using userid '[chars]' for server [chars]

Explanation An invalid user ID was used to connect to the remote database server.

Recommended Action This is an informational message only. No action is required.

Error Message

%DBCONN-5-UIDMISSING: APPC security failed, client [int] using userid '[chars]' for server [chars]

Explanation The remote database server requires a user ID , but the user ID was not provided.

Recommended Action This is an informational message only. No action is required.

Error Message

%DBCONN-5-UIDREVOKED: APPC security failed, client [int] using userid '[chars]' for server [chars]

Explanation The user ID used to connect to the remote database server was revoked.

Recommended Action This is an informational message only. No action is required.

Error Message

%DBCONN-5-WLMDOWN: All WLM routes on server [chars] have become unavailable. Recovery is in progress.

Explanation A load-balanced Workload Manager server has lost connectivity to all destinations in its server list. All client connections to this server will be rejected until a host in the complex becomes available again.

Recommended Action This is an informational message only. No action is required.

Error Message

%DBCONN-5-WLMMISMATCH: WLM transport type mismatch on server [chars]

Explanation The transport type within a server list received from a Workload Manager load-balanced database does not match the transport type of the corresponding DBCONN server. If the conflicting server list specifies SNA transport type, the default mode #INTER will be used to establish the connection.

Recommended Action This is an informational message only. No action is required.

Error Message

%DBUS-3-DBUSINTERRSWSET: Slot [dec], Internal Error due to VIP crash

Explanation A processor reported an error. The processor will be reset and not used until the next online insertion and removal (OIR) event or microcode download, when it will be retested.

Recommended Action Reinstall the processor or download the microcode. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%DEC21140-3-DUPLEX_SPEED: [chars] doesn't support the configured duplex and speed combination

Explanation The Fast Ethernet port was configured for a duplex/speed combination that this particular hardware does not support.

Recommended Action Specify a different speed and duplex combination. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%DEC21140-5-NOCARR: [chars] cable/connector problem?

Explanation The Fast Ethernet port did not find a carrier when preparing to transmit a packet, indicating that it is no longer receiving signals from the LAN. This problem can be caused by disconnected Fast Ethernet cabling or a transceiver failure.

Recommended Action Check your Fast Ethernet wiring and port adapter. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%DIALSHELF-2-DSCDOWN: DSC in slot [dec] changes state to down.

Explanation DSC in dial shelf went down.

Recommended Action Try to bring up the DSC by checking LCD and LEDs of the DSC or checking the RS LESSTHAN-DSC connection. If neither method works, contact your Cisco technical support representative.

Error Message

%DIALSHELF-4-UNRECOMMENDED: Number of [chars] may exceed recommended configuration

Explanation More than one CT3, or more than two T1/E1 are installed, therefore exceeding the recommended configuration.

Recommended Action Stay within recommended limits of CT3 and T1/E1, install a split dial-shelf configuration, or upgrade the router shelf to NPE300.

Error Message

%DLSWMasterSlave-3-DLSWMS: [chars] #define DLSWMS_ERR &msgsym(DLSWMS, DLSWMasterSlave)

Explanation A data-link switching (DLSw) master-slave error occurred.

Recommended Action No action is required.

Error Message

%DLSWMasterSlave-3-DLSWMSDLX: [chars] [hex] from [sci_notation]

Explanation A data-link switching (DLSw) master-slave error occurred.

Recommended Action No action is required.

Error Message

%DLSWMasterSlave-3-DLSWMSRCV: [chars] from [sci_notation]

Explanation A data-link switching (DLSw) master-slave error occurred.

Recommended Action No action is required.

Error Message

%DLSWMasterSlave-3-DLSWMSSAP: [chars] [chars] #define DLSWMS_SAP_ERR &msgsym(DLSWMSSAP, DLSWMasterSlave)

Explanation A DLSw master-slave error occurred.

Recommended Action No action is required.

Error Message

%DLSWP-3-PNOCOOKIE: DLSw: uninitalized peer [chars] from [int]([dec]) to [int]([dec])

Explanation Data-link switching (DLSw) received a packet on an uninitialized peer connection.

Recommended Action Verify configuration and DLSw peer status on both routers.

Error Message

%DMTDSL-3-BADINITDSL: DMTDSL([dec]/[dec]), interface not initialized

Explanation The ATM network module hardware may be bad.

Error Message

%DMTDSL-3-DMTHWBAD: DMTDSL([dec]/[dec]), Hardware failed self test

Explanation The digital subscriber line (DSL) chipset failed its self-test.

Error Message

%DMTDSL-3-FAILFINDATM: DMTDSL([dec]/[dec]), Could not find ATM interface

Explanation The digital subscriber line (DSL) network module hardware may be bad.

Error Message

%DMTDSL-1-INITFAIL: DMTDSL([dec]/[dec]), Init failed, [chars]

Explanation The ADSL network module hardware may be bad.

Error Message

%DMTDSL-3-NOMEM: DMTDSL([dec]/[dec]), Out of memory

Explanation The router does not have enough installed memory to run this image.

Error Message

%DSPDD-1-DSPFWFAILURE: DSPRM internal error[[chars]:[dec]

Explanation The router or access server detected an internal error.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%DSPDD-1-INTERNALERROR: DSPRM internal error[[chars]:[dec]

Explanation The router or access server detected an internal error.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%DSPDD-1-NOIOSBUFFERS: IOS buffer pool unavailable [[chars]:[dec]]

Explanation The router or access server could not allocate internal resources.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%DSPDD-1-NOIOSMEMORY: IOS memory unavailable [[chars]:[dec]]

Explanation The router or access server could not allocate memory for internal data structures.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%DSPRM-5-DSPFAIL: DSP [dec] in slot [dec], is in the failed state

Explanation The domain specific part (DSP) entered the FAILED state caused by alarm indications.

Recommended Action Replace the domain specific part (DSP) resource.

Error Message

%DSPRM-3-INSUFFICIENT: Insufficient DSP resources for timeslot [dec] on port [chars]

Explanation The configuration requires more domain specific part (DSP) resources than are available.

Recommended Action Change the configuration to specify fewer used timeslots. Install additional domain specific part (DSP) resources to allow more complex configurations.

Error Message

%DSPRM-5-KEEPALIVE: DSP [dec] in slot [dec], NOT RESPONDING - auto restart([dec] times)

Explanation The domain specific part (DSP) failed the background keepalive test.

Recommended Action No action is required.

Error Message

%DSPRM-5-UPDOWN: DSP [dec] in slot [dec], changed state to [chars]

Explanation The domain specific part (DSP) resource changed state.

Recommended Action No action is required.

Error Message

%DSX1-1-FIRMWARE_RUNNING: T1/E1 Firmware is running

Explanation T1/E1 firmware is now running after recovering from critical error.

Error Message

%E1T1_MODULE-3-HWIDBFAILED: Controller [dec]/[dec] does not have idb

Explanation The system did not have an HWIDB registered for the serial interface.

Error Message

%E1T1_MODULE-3-INITFAILURE: Slot [dec], Unit [dec] initialization failure - [chars]

Explanation The E1T1 driver detected an error while initializing.

Error Message

%E1T1_MODULE-3-LINEFLAP: Interface [chars] receiving excessive errored packets

Explanation The serial interface is receiving excessive errored packets.

Recommended Action This error is caused by a controller configuration mismatch. Check linecode, framing, timeslots, and speed settings.

Error Message

%EHSA-5-PEER_MONITOR_EVENT: [chars] ([chars][chars]([dec]))

Explanation An EHSA Peer Monitor event occurred and was reported. The report should help find the reason for a switch-over.

Error Message

%FAN-3-FAN_FAILED: Fan [dec] had a rotation error reported

Explanation The fan experienced a rotation error.

Recommended Action Replace the fan if it is not rotating.

Error Message

%FAN-3-FAN_OK: Fan [dec] had reported a previous rotation error, however is now functioning

Explanation This is an informational message only. A fan that had reported a rotation error is now functional.

Recommended Action No action is required.

Error Message

%FB-3-INVALIDSLOT: Invalid [chars] feature board present in slot [dec]

Explanation A feature board has been inserted in a restricted slot. This in not permitted.

Recommended Action Reinsert the feature board in the appropriate slot.

Error Message

%FR-3-BQ_DEQ_ERR: fr_bq_proc: unknown packet on broadcast queue, packet dropped

Explanation An invalid packet on a Frame Relay broadcast queue was dropped.

Recommended Action Inform your Cisco technical support representative.

Error Message

%FR-3-BQ_DEQ_PTR: fr_br_proc: hdr-[hex] size-[dec] dlci-[hex] [hex] [hex]

Explanation An invalid datagram start on a Frame Relay broadcast queue was dropped.

Recommended Action Inform your Cisco technical support representative.

Error Message

%FR-3-BQ_ENQ_ERR: fr_oqueue: Invalid datagramstart [hex], pak dropped

Explanation A broadcast packet with an invalid datagram start in fr_oqueue was dropped.

Recommended Action Inform your Cisco technical support representative.

Error Message

%FW-4-TCP_MAJORDOMO_EXEC_BUG: Majordomo Execute Attack - from [int] to [int]

Explanation A bug in the Majordomo program will allow remote users to execute arbitrary commands at the privilege level of the server.

Recommended Action For security reasons users should not be allowed to execute programs via e-mail servers. This is a very serious indication that your network may be under attack and the source should be shunned immediately.

Error Message

%FW-4-TCP_SENDMAIL_BAD_FROM_SIG: Sendmail Invalid Sender - from [int] to [int]

Explanation This message is triggered by any mail message with a pipe (|) symbol in the From: field.

Error Message

%FW-4-TCP_SENDMAIL_BAD_TO_SIG: Sendmail Invalid Recipient - from [int] to [int]

Explanation This message is triggered by any mail message with a pipe (|) symbol in the recipient field.

Error Message

%FW-4-TCP_SENDMAIL_DECODE: Sendmail Decode Alias - from [int] to [int]

Explanation This message is triggered by any mail message with decode@ in the header. The decode alias is used to uudecode files and is primarily implemented as a convenience for system administration.

Error Message

%FW-4-TCP_SENDMAIL_INVALID_COMMAND: Invalid SMTP command - [int] to [int]

Explanation This message is triggered by an invalid SMTP command in the SMTP connection. A suspicious violation was detected that may be an attack to the mail server system.

Recommended Action This is unusual traffic and may warrant investigation. Call your Cisco technical support representative.

Error Message

%FW-4-TCP_SENDMAIL_OLD_SIG: Archaic Sendmail Attacks - from [int] to [int]

Explanation This message is triggered when wiz or debug commands are sent to the SMTP port.

Error Message

%FX1000-1-DISCOVER: Only found [dec] interfaces on bay [dec], shutting down bay

Explanation A possible hardware error resulted in too few GE interfaces discovered.

Error Message

%FX1000-3-NOTFX1000: slot[[dec], [dec]] detects unknown PCI device (id=0x[hex])

Explanation For some reason, the GE PA does not contain a Gigabit controller chip.

Error Message

%GLCFR-3-DLCIRANGE: [chars]([chars]) bad dlci value [int]

Explanation The GLC Frame Relay support code received a bad dlci number.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%GRP-3-LC_CARD_TYPE_INVALID: line card has invalid card type [hex]

Explanation The line card type is invalid. The line card electrically erasable programmable read-only memory (EEPROM) is programmed with an invalid card type.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%GRP-3-LC_FLASH_PROG_FAIL: Slot [dec] failed program flash with [chars]

Explanation Programming of the line card Flash failed. The line card Flash may have a problem.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%GRPGE-3-CMDERR: Interface ([chars]): [chars] IPC command fails (cause: 0x[hex])

Explanation The Gigabit Ethernet RP driver experienced an IPC command error.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%GRPGE-3-EVENT: Interface ([chars]): unknown IPC event ([int]) from line card

Explanation The Gigabit Ethernet RP driver received an unknown event from the line card.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%GRPGE-3-INIT: Gigabit Ethernet driver ([int]/[int]) initialization [chars].

Explanation The Gigabit Ethernet RP driver experienced a software initialization error.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%GRPGE-4-MSGVERSION: Incompatible message version with slot [dec]

Explanation The POS statistics are not reported to the GRP. There is incompatibility between the message version being sent by the line card and the message version used by the GRP. This type of incompatibility could happen if GRP and the line card are using different Cisco IOS versions due to a GRP OIR event.

Recommended Action A microcode reload will solve the problem.

Error Message

%GRPGE-4-NULLCEFIDB: Interface ([chars])

Explanation This interface does not have CEF IDB by mistake.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%GRPGE-3-OP: Interface ([chars]): [chars]

Explanation The Gigabit Ethernet RP driver received an unexpected event.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show gsr and show ipc status commands to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show gsr and show ipc status commands, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%GRPGE-6-SH_CAM_FULL: Failed to add address [sci_notation] to full [dec] entry shadow CAM

Explanation An entry to the CAM MAC address filter was not added.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. If you cannot determine the nature of the error from the error message text, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%GRPGE-4-UNSUP: Interface ([chars]): unsupported feature: [chars]

Explanation This feature is not supported by GSR Gigabit Ethernet RP.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%HDV-3-DISCOVER: HDV in slot [dec]: the HDV failed to initialize properly.

Explanation An initialization action failed for the HDV. This problem can be caused by a lack of system resources, improper or no voice interface card (VIC) installed in the port module, or defective HDV hardware.

Recommended Action Power down. Check that a supported voice interface card (VIC) module is properly installed in the HDV module. Reinsert the VIC module. Then reinsert the port module and reboot the router. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%HDV-2-FATAL_ERROR: HDV in slot [dec]: An unrecoverable error occurred.

Explanation The HDV card experienced an internal unrecoverable error. This may be caused by a internal firmware error or defective HDV hardware.

Recommended Action Power down, reinsert the network module, and reboot. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%HDV-3-FW_START: HDV in slot [dec]: the firmware on the port module did start properly.

Explanation The firmware on the card did not start after a reset. This error is usually caused by a defective HDV module or improperly seated HDV module.

Recommended Action Power down, reinsert the HDV port module, and reboot. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%HDV-3-HW_START: HDV in slot [dec]: the port module did not reset and start up properly.

Explanation The hardware on the card did not start after a reset. This error is usually caused by a defective HDV module or an improperly seated HDV module.

Error Message

%HDV-3-INCORRECT_PMID: HDV in slot [dec]: Incorrect [dec] PM-ID device not supported.

Explanation An interface controller device did not have the correct PM-ID.

Recommended Action Check that the HDV is inserted properly. If necessary, turn off the router and reinsert the HDV port module. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%HDV-3-INVALID_PCI_ID: HDV in slot [dec]: reports an invalid device id of [hex]

Explanation The HDV port module hardware may be defective or improperly seated.

Error Message

%HDV-1-NOPCIMEMORY: HDV in slot [dec]: No PCI memory available.

Explanation The system is experiencing memory exhaustion in the protocol control information (PCI)/packet memory. This error is probably caused by heavy traffic congestion, but could also be a software error.

Recommended Action Review the configuration for performance bottlenecks. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%HDV-1-NO_DAUGHTER_CARD: HDV in slot [dec]: no VIC card is inserted in the HDV.

Explanation The software did not detect the presence of a voice interface card (VIC) card inserted in the HDV port module.

Recommended Action Check that there is a voice interface card (VIC) inserted properly into the HDV. If so, then check the part number on the VIC to see if it is supported in the version of Cisco IOS software operational on the router, or contact your technical support representative.

Error Message

%HDV-1-TOOBIG: HDV in slot [dec]: packet size ([dec]) too big.

Explanation A packet greater than the 256 bytes was received on this interface.

Recommended Action The system should recover. No action is required. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%HDV-1-UNKNOWN_VIC: HDV in slot [dec]: VIC daughter card has an unknown id of 0x[hex]

Explanation The software did not recognize the type of voice interface card (VIC) card plugged into the HDV port module.

Recommended Action Check the part number on the voice interface card (VIC) card to see if it is supported in the version of Cisco IOS software operational on the router, or contact your technical support representative.

Error Message

%HDV-1-UNSUPPORTED_VIC: HDV in slot [dec]: VIC daughter card ([chars]/0x[hex]) is unsupported

Explanation The voice interface card (VIC) plugged into the HDV is not of a supported type.

Recommended Action Replace this voice interface card (VIC) with a type that is supported by this version of Cisco IOS software, or change the version of Cisco IOS software to support this VIC type.

Error Message

%IDS-4-ICMP_ECHO_REPLY_SIG: Sig:2000:ICMP Echo Reply - from [int] to [int]

Explanation This message is triggered when an IP datagram is received with the protocol field of the IP header set to 1 (ICMP) and the type field in the ICMP header set to 0 (Echo Reply).

Recommended Action This is common network traffic. Suspicion should be raised when a large number of these packets are found on the network. If no legitimate reason for this traffic can be identified, prudent security practices would suggest that the source be shunned.

Error Message

%IDS-4-ICMP_ECHO_SIG: Sig:2004:ICMP Echo Request - from [int] to [int]

Explanation This message is triggered when an IP datagram is received with the protocol field of the IP header set to 1 (ICMP) and the type field in the ICMP header set to 8 (Echo Request). This is commonly used to perform reconnaissance sweeps. Suspicion should be raised when a large number of these packets are found on the network.

Recommended Action The ICMP Echo Request is entered by the source to determine if the destination is alive. When the destination receives the request it will reply with an ICMP Echo Reply. This request/reply pair is most commonly implemented via the ping utility. Many network management tools use this utility or some derivative. This is common network traffic. Suspicion should be raised when a large number of these packets are found on the network. If no legitimate reason for this traffic can be identified, prudent security practices would suggest that the source be shunned.

Error Message

%IDS-4-ICMP_FRAGMENT_SIG: Sig:2150:Fragmented ICMP Traffic - from [int] to [int]

Explanation This message is triggered when an IP datagram is received with the protocol field of the IP header set to 1 (ICMP) and either the more fragments flag is set to 1 (ICMP) or there is an offset indicated in the offset field.

Recommended Action IP datagrams may be fragmented normally as they are transported across the network, but ICMP is rarely fragmented. The traffic should be investigated. If no legitimate reason for the fragmentation can be found and especially if the packets seem to be originating from a single source, prudent security practices would suggest that the host be shunned.

Error Message

%IDS-4-ICMP_INFO_REPLY_SIG: Sig:2010:ICMP Information Reply - from [int] to [int]

Explanation This message is triggered when an IP datagram is received with the protocol field of the IP header set to 1 (ICMP) and the type field in the ICMP header set to 16 (ICMP Information Reply). No known exploit exists.

Recommended Action This datagram type is obsolete and should not be encountered. When nonspecific network traffic of this type is encountered, the most prudent action from a security perspective is to shun or disallow it. If the source of this traffic is legitimate the user will then identify itself.

Error Message

%IDS-4-ICMP_INFO_SIG: Sig:2009:ICMP Information Request - from [int] to [int]

Explanation This message is triggered when an IP datagram is received with the protocol field of the IP header set to 1 (ICMP) and the type field in the ICMP header set to 15 (Information Request).

Error Message

%IDS-4-ICMP_MASK_REPLY_SIG: Sig:2012:ICMP Address Mask Reply - from [int] to [int]

Explanation This message is triggered when an IP datagram is received with the protocol field of the IP header set to 1 (ICMP) and the type field in the ICMP header set to 18 (Address Mask Reply). No known exploits incorporate this option.

Recommended Action The ICMP Address Mask request/reply pair can be used to determine the subnet mask used on the network. The requesting system issues the Address Mask Request bound for a destination; the destination system responds with an Address Mask Reply message. This is normal network traffic, but is uncommon on most networks. Suspicion should be raised when a large number of these packets are found on the network. If no legitimate reason for this traffic can be identified prudent security practices would suggest that the source be shunned.

Error Message

%IDS-4-ICMP_MASK_SIG: Sig:2011:ICMP Address Mask Request - from [int] to [int]

Explanation This message is triggered when an IP datagram is received with the protocol field of the IP header set to 1 (ICMP) and the type field in the ICMP header set to 17 (Address Mask Request). ICMP Address Mask Requests could be used to perform reconnaissance sweeps of networks.

Recommended Action The ICMP Address Mask request/reply pair can be used to determine the subnet mask used on the network. The requesting system issues the Address Mask Request bound for a destination; the destination system responds with an Address Mask Reply message. This is normal network traffic, but is uncommon on most networks. Suspicion should be raised when a large number of these packets are found on the network. If no legitimate reason for this traffic can be identified, prudent security practices would suggest that the source be shunned.

Error Message

%IDS-4-ICMP_PARAMPROB_SIG: Sig:2006:ICMP Parameter Problem on Datagram - from [int] to [int]

Explanation This message is triggered when an IP datagram is received with the protocol field of the IP header set to 1 (ICMP) and the type field in the ICMP header set to 12 (Parameter Problem on Datagram). No known exploits incorporate this option.

Recommended Action ICMP Parameter Problem datagrams are issued when a router has had to drop a datagram because it was malformed. This is a normal and necessary type of network traffic. Large numbers of this datagram type on the network are indicative of network difficulties or may be indicative of hostile actions. If no network problems can be identified to account for the traffic, prudent security practices would suggest that the source be shunned.

Error Message

%IDS-4-ICMP_PING_OF_DEATH_SIG: Sig:2154:ICMP Ping of Death Attack - from [int] to [int]

Explanation This message is triggered when an IP datagram is received with the protocol field of the IP header set to 1(ICMP), when the Last Fragment bit is set, and when ( IP offset * 8 ) plus ( IP data length) is 65535.That is, the IP offset (which represents the starting position of this fragment in the original packet, and which is in 8-byte units) plus the rest of the packet is greater than the maximum size for an IP packet. This indicates a denial of service attack.

Recommended Action It is likely that the source address has been spoofed, making shunning ineffective. Call your Cisco technical support representative.

Error Message

%IDS-4-ICMP_REDIRECT_SIG: Sig:2003:ICMP Redirect - from [int] to [int]

Explanation This message is triggered when an IP datagram is received with the protocol field of the IP header set to 1 (ICMP) and the type field in the ICMP header set to 5 (Redirect).

Recommended Action The redirect message may be issued from a router to inform a host of a better route to a requested destination. The host then updates its routing table to include this route. This method of updating routing tables is an uncommon practice today. When nonspecific network traffic of this type is encountered, the most prudent action from a security perspective is to shun or disallow it. If the source of this traffic is legitimate the user will then identify itself.

Error Message

%IDS-4-ICMP_SOURCEQUENCH_SIG: Sig:2002:ICMP Source Quench - from [int] to [int]

Explanation This message is triggered when an IP datagram is received with the protocol field of the IP header set to 1 (ICMP) and the type field in the ICMP header set to 4 (Source Quench). This datagram may be used in network management to provide congestion control. Large numbers of this datagram type on the network are indicate network difficulties or may indicate hostile actions.

Recommended Action This datagram may be used in network management to provide congestion control. A Source Quench packet will be issued when a router is beginning to lose packets due to the transmission rate of a source. The Source Quench is a request to the source to reduce the rate of datagram transmission. This datagram type is rarely if ever seen on networks, and some systems do not even support it. Large numbers of this datagram type on the network indicate network difficulties or may indicate hostile actions. If no network problems can be identified to account for the traffic, prudent security practices would suggest that the source be shunned.

Error Message

%IDS-4-ICMP_TIME_REPLY_SIG: Sig:2008:ICMP Timestamp Reply - from [int] to [int]

Explanation This message is triggered when an IP datagram is received with the protocol field of the IP header set to 1 (ICMP) and the type field in the ICMP header set to 14 (Timestamp Reply). No known exploits incorporate this option.

Recommended Action The ICMP Timestamp request/reply pair can be used to synchronize system clocks on the network. The requesting system issues the Timestamp Request bound for a destination; the destination system responds with a Timestamp Reply message. This is normal network traffic, but is uncommon on most networks. Suspicion should be raised when a large number of these packets are found on the network. If no legitimate reason for this traffic can be identified, prudent security practices would suggest that the source be shunned.

Error Message

%IDS-4-ICMP_TIME_SIG: Sig:2007:ICMP Timestamp Request - from [int] to [int]

Explanation This message is triggered when an IP datagram is received with the protocol field of the IP header set to 1 (ICMP) and the type field in the ICMP header set to 13 (Timestamp Request). ICMP Timestamp Requests could be used to perform reconnaissance sweeps of networks. No known exploits incorporate this option.

Error Message

%IDS-4-ICMP_TIMXCEED_SIG: Sig:2005:ICMP Time Exceeded for a Datagram - from [int] to [int]

Explanation This message is triggered when an IP datagram is received with the protocol field of the IP header set to 1 (ICMP) and the type field in the ICMP header set to 11 (Time Exceeded for a Datagram). No known exploits incorporate this option.

Recommended Action ICMP Time Exceeded datagrams are issued when a router has had to drop a datagram whose Time to Live (TTL) flag has expired. This is a normal and necessary type of network traffic. Large numbers of this datagram type on the network indicate network difficulties or may indicate hostile actions. If no network problems can be identified to account for the traffic prudent, security practices would suggest that the source be shunned.

Error Message

%IDS-4-ICMP_TOOLARGE_SIG: Sig:2151:Large ICMP Traffic - from [int] to [int]

Explanation Although it is possible to receive ICMP datagrams that have a size greater than 1024 bytes, this is a highly unusual occurrence that warrants investigation.

Recommended Action If no legitimate reason for the large packet size can be found and especially if the packets seem to be originating from a single source, prudent security practices would suggest that the host be shunned.

Error Message

%IDS-4-ICMP_UNREACH_SIG: 2001:ICMP Host Unreachable - from [int] to [int]

Explanation This message is triggered when an IP datagram is received with the protocol field of the IP header set to 1 (ICMP) and the type field in the ICMP header set to 3 (Host Unreachable). This is the common response to large numbers of this datagram type on the network. It indicates network difficulties or may indicate hostile actions.

Recommended Action This is the common response provided to a client when there is no path available to the requested host. This is a very common type of network traffic. Large numbers of this datagram type on the network indicate network difficulties or may indicate hostile actions. If no network problems can be identified to account for the traffic, prudent security practices would suggest that the source be shunned.

Error Message

%IDS-4-IPFRAG_ATTACK_SIG: Sig:1100:IP Fragment Attack - from [int] to [int]

Explanation This message is triggered when any IP datagram is received with the "more fragments" flag set to 1 or if an offset is indicated in the offset field.

Recommended Action IP datagrams may be fragmented normally as they are transported across the network. This is not uncommon, but is unusual enough that the traffic should be investigated. This is especially important if the network is protected by a packet filtering firewall.

Error Message

%IDS-4-IPOPTS_BAD_SIG: Sig:1000:Bad IP Option List - from [int] to [int]

Explanation This message is triggered on receipt of an IP datagram where the list of IP options in the IP datagram header is incomplete or malformed. No known exploits purposely incorporate this option.

Recommended Action There is no legitimate use for malformed datagrams. This may indicate systems that are experiencing problems with their kernel or network interface cards. This is unusual traffic and warrants investigation. When nonspecific network traffic of this type is encountered, the most prudent action from a security perspective is to shun or disallow it. If the source of this traffic is legitimate the user will then identify itself.

Error Message

%IDS-4-IPOPT_LSRR_SIG: Sig:1004:IP options-Loose Source Route - from [int] to [int]

Explanation This message is triggered on receipt of an IP datagram where the IP option list for the datagram includes option 3 (Loose Source Route). This option may be misused to defeat authentication mechanisms that rely on IP addresses as their basis for trust relationships.

Recommended Action Although network troubleshooting may require the legitimate use of this feature, this type of traffic is rarely if ever noted and should comprise less than 1 percent of network traffic. Small amounts of source routed traffic most probably indicates that a network problem is being investigated. Large amounts of source routed traffic is more suspicious. Thoroughly investigate of the source and reason.

Error Message

%IDS-4-IPOPT_RR_SIG: Sig:1001:IP options-Record Packet Route - from [int] to [int]

Explanation The IP options list contains one or more options that perform various network management or debugging tasks. This alarm may indicate a reconnaissance attack is in progress against your network.

Recommended Action Although network troubleshooting may require the legitimate use of this feature, this is unusual traffic that warrants investigation. When nonspecific network traffic of this type is encountered, the most prudent action from a security perspective is to shun or disallow it. If the source of this traffic is legitimate the user will then identify itself.

Error Message

%IDS-4-IPOPT_SATID_SIG: Sig:1005:IP options-SATNET ID - from [int] to [int]

Explanation This message is triggered on the receipt of an IP datagram where the IP option list for the datagram includes option 8 (SATNET stream identifier). No known exploit exists.

Recommended Action This option is obsolete and should not be encountered. When nonspecific network traffic of this type is encountered, the most prudent action from a security perspective is to shun or disallow it. If the source of this traffic is legitimate the user will then identify itself.

Error Message

%IDS-4-IPOPT_SECURITY_SIG: Sig:1003:IP options-Provide s, c, h, tcc - from [int] to [int]

Explanation This message is triggered on the receipt of an IP datagram where the IP option list for the datagram includes option 2 (Strict Source Routing). No known exploit exists.

Recommended Action This signature will trigger if you have implemented IP security options on your network. However, this is rarely if ever implemented . When nonspecific network traffic of this type is encountered, the most prudent action from a security perspective is to shun or disallow it. If the source of this traffic is legitimate the user will then identify itself.

Error Message

%IDS-4-IPOPT_SSRR_SIG: Sig:1006:IP options-Strict Source Route - from [int] to [int]

Explanation This message is triggered on the receipt of an IP datagram in which the IP option list for the datagram includes option 2 (Strict Source Routing). This option may be misused to defeat authentication mechanisms that rely on IP addresses as their basis for trust relationships.

Recommended Action Although network troubleshooting may require the legitimate use of this feature, this type of traffic is rarely if ever noted and should comprise much less than 1% of network traffic. Small amounts of source routed traffic most probably indicate that a network problem is being investigated. Large amounts of source routed traffic is more suspicious. Thoroughly investigate the source and reason.

Error Message

%IDS-4-IPOPT_TS_SIG: Sig:1002:IP options-TimeStamp - from [int] to [int]

Explanation This message is triggered on the receipt of an IP datagram where the IP option list for the datagram includes option 4 (Timestamp). This alarm indicates that a reconnaissance attack may be in progress against your network.

Error Message

%IDS-4-IP_IMPOSSIBLE_SIG: Sig:1102:Impossible IP Packet - from [int] to [int]

Explanation This message is triggered when an IP packet arrives with source equal to destination address. This signature will catch the so-called Land Attack.

Recommended Action This should never occur in legitimate traffic. Call your Cisco technical support representative.

Error Message

%IDS-4-IP_UNKNOWN_PROTO_SIG: Sig:1101:Unknown IP Protocol - from [int] to [int]

Explanation This message is triggered when an IP datagram is received with the protocol field set to 101 or greater. The use of these protocol types is highly unusual and should be investigated.

Recommended Action Locally developed protocols that may use these protocol types will trigger the signature. The use of these protocol types is highly unusual and should be investigated. When nonspecific network traffic of this type is encountered, the most prudent action from a security perspective is to shun or disallow it. If the source of this traffic is legitimate the user will then identify itself.

Error Message

%IDS-4-LOST_CONNECT: Connection to HostID:[int] OrgID:[int]

Explanation This message is triggered when a connection drops and there is no previous connection.

Recommended Action This message indicates that the IDS cannot communicate with the Director. Check connectivity to the Director and check Postoffice configuration on both the router and the Director.

Error Message

%IDS-4-RPC_CALLIT_REQUEST: Sig:6103:Proxied RPC Request - from [int] to [int]

Explanation This message is triggered when a proxied RPC request is sent to the portmapper of a target host.

Recommended Action If this procedure is allowed on your network, those users that employ it will trigger the signature. This may be a serious attempt at gaining unauthorized access. If the source of the attempt is not within your network it should be shunned.

Error Message

%IDS-4-RPC_DUMP_REQUEST: Sig:6102:RPC Dump - from [int] to [int]

Explanation This message is triggered when an RPC dump request is issued to a target host.

Recommended Action This is a common procedure performed by many system administrators and wary users to determine which RPC services are being offered. Executing this procedure is most likely due to curiosity on the part of a novice user or a system administrator performing system maintenance. If upon investigation no valid user can be associated with this event, prudent security practices would suggest shunning the source.

Error Message

%IDS-4-RPC_PORTREQ_MOUNTD: Sig:6155:RPC mountd Portmap Request - from [int] to [int]

Explanation This message is triggered when a request is made to the portmapper for the mount daemon (mountd) port.

Error Message

%IDS-4-RPC_PORTREQ_REXD: Sig:6175: RPC rexd Portmap Request - from [int] to [int]

Explanation This message is triggered when a request is made to the portmapper for the remote execution daemon (rexd) port. The remote execution daemon is the server responsible for remote program execution. This may indicate an attempt to gain unauthorized access to system resources.

Recommended Action If this procedure is allowed on your network, those users who employ it will trigger the signature. This may be a serious attempt at gaining unauthorized access. If the source of the attempt is not within your network, it should be shunned.

Error Message

%IDS-4-RPC_PORTREQ_YPBIND: Sig:6151:RPC ypbind Portmap Request - from [int] to [int]

Explanation This message is triggered when a request is made to the portmapper for the YP bind daemon (ypbind) port.

Error Message

%IDS-4-RPC_PORTREQ_YPPASSWDD: Sig:6152:RPC ypbind yppasswdd Portmap Request - from [int] to [int]

Explanation This message is triggered when a request is made to the portmapper for the YP password daemon (yppasswdd) port.

Error Message

%IDS-4-RPC_PORTREQ_YPSERV: Sig:6150:RPC ypserv Portmap Request - from [int] to [int]

Explanation This message is triggered when a request is made to the portmapper for the YP server daemon (ypserv) port.

Error Message

%IDS-4-RPC_PORTREQ_YPUPDATED: Sig:6153:RPC ypupdated Portmap Request - from [int] to [int]

Explanation This message is triggered when a request is made to the portmapper for the YP update daemon (ypupdated) port.

Error Message

%IDS-4-RPC_PORTREQ_YPXFRD: Sig:6154:RPC ypxfrd Portmap Request - from [int] to [int]

Explanation This message is triggered when a request is made to the portmapper for the YP transfer daemon (ypxfrd) port.

Error Message

%IDS-4-RPC_REXD_REQUEST: Sig:6180:RPC rexd Attempt - from [int] to [int]

Explanation This message is triggered when a call to the rexd program is made. The remote execution daemon is the server responsible for remote program execution. This may indicate of an attempt to gain unauthorized access to system resources.

Recommended Action If this service is being used legitimately, this alarm will fire. For security purposes, this service really should not be used. Call your Cisco technical support representative.

Error Message

%IDS-4-RPC_SET_REQUEST: Sig:6100:RPC Port Registration - from [int] to [int]

Explanation This message is triggered when attempts are made to register new RPC services on a target host.

Recommended Action No benign triggers exist for this signature. Prudent security practices suggest that the source of this attempt should be shunned.

Error Message

%IDS-4-RPC_STATD_OVFLW: Sig:6190:statd Buffer Overflow - from [int] to [int]

Explanation This message is triggered when a large statd request is sent.

Recommended Action You should not see this in legitimate traffic. Call your Cisco technical support representative.

Error Message

%IDS-4-RPC_UNSET_REQUEST: Sig:6101:RPC Port Unregistration - from [int] to [int]

Explanation This message is triggered when attempts are made to unregister new RPC services on a target host.

Recommended Action No benign triggers exist for this signature. Prudent security practices suggest that the source of this attempt should be shunned.

Error Message

%IDS-4-STR_MATCH_SIG: Sig:8000:FTP Retrieve Password File - from [int] to [int]

Explanation This message is triggered on string "passwd" issued during an FTP session.

Recommended Action System administrators might use this service to update system files. It is a high security risk if this is normal practice, and should be avoided. No other benign triggers exist for this signature. If investigation shows the alarm was not generated by a system administrator, prudent security practices would suggest that the source be shunned.

Error Message

%IDS-4-TCP_FIN_ONLY_SIG: Sig:3042:TCP - FIN bit with no ACK bit in flags - from [int] to [int]

Explanation This message is triggered when a TCP packet is received with the FIN bit set but with no ACK bit set in the flags field.

Recommended Action There is no legitimate use for malformed TCP datagrams. This is unusual traffic and warrants investigation. Hacker tools will generate TCP packets with the FIN bit set but with no ACK bit set in the flags field in an attempt to elude intrusion dection. When nonspecific network traffic of this type is encountered, the most prudent action from a security perspective is to shun or disallow it. If the source of this traffic is legitimate the user will then identify itself.

Error Message

%IDS-4-TCP_FTP_CWDROOT_SIG: Sig:3152:FTP CWD ~root - from [int] to [int]

Explanation This message is triggered when attempts are made to execute the CWD ~root command.

Recommended Action There is no known reason that this command should ever be executed. If this signature is triggered from a source outside of your network, prudent security practices would suggest that the source be shunned.

Error Message

%IDS-4-TCP_FTP_PORT_BADADDR_SIG: Sig:3153:FTP Improper Address Specified - from [int] to [int]

Explanation An improper address was specified.

Recommended Action If you can not determine the nature of the error from the error message text, call your Cisco technical support representative, and provide the representative with gathered information.

Error Message

%IDS-4-TCP_FTP_PORT_BADPORT_SIG: Sig:3154:FTP Improper Port Specified - from [int] to [int]

Explanation An improper port was specified which contains 65535.

Recommended Action If you cannot determine the nature of the error from the error message text, call your Cisco technical support representative, and provide the representative with gathered information.

Error Message

%IDS-4-TCP_FTP_SITE_SIG: Sig:3150:FTP Remote Command Execution - from [int] to [int]

Explanation This message is triggered when attempts are made to execute the FTP SITE command.

Recommended Action The FTP Site command allows a user to execute a limited number of commands via the FTP server on the host machine. No authentication is required to execute the command. The commands that may be executed vary from system to system and on many systems the SITE command is not implemented. Recommend that the SITE command be disabled on FTP servers if possible. If this signature is triggered from a source outside of your network prudent security practices would suggest that the source be shunned.

Error Message

%IDS-4-TCP_FTP_SYST_SIG: Sig:3151:FTP SYST Command Attempt - from [int] to [int]

Explanation This message is triggered when someone tries to execute the FTP SYST command.

Recommended Action The FTP SYST command returns the type of operating system that the FTP server is running. Authentication is not required to execute this command. SYST provides information that may be used to refine attack methods. FTP from Linux causes SYST signature to fire. Some proxies, such as the TIS Toolkit, enter the SYST command as a matter of course. Running an FTP version with SYST disabled.

Error Message

%IDS-4-TCP_MAJORDOMO_EXEC_BUG: Sig:3107:Majordomo Execute Attack - from [int] to [int]

Explanation A bug in the Majordomo program will allow remote users to execute arbitrary commands at the privilege level of the server.

Recommended Action Prudent security practices would suggest that the source of this attempt be shunned.

Error Message

%IDS-4-TCP_NO_FLAGS_SIG: Sig:3040:TCP - No bits set in flags - from [int] to [int]

Explanation This message is triggered when a TCP packet is received with no bits set in the flags field.

Recommended Action There is no legitimate use for malformed TCP datagrams. This is unusual traffic and warrants investigation. Hacker tools will generate TCP packets with no bits set in the flags field in an attempt to elude intrusion dection. When nonspecific network traffic of this type is encountered, the most prudent action from a security perspective is to shun or disallow it. If the source of this traffic is legitimate the user will then identify itself.

Error Message

%IDS-4-TCP_SENDMAIL_BAD_FROM_SIG: Sig:3102:Sendmail Invalid Sender - from [int] to [int]

Explanation This message is triggered on any mail message with a pipe (|) symbol in the from: field.

Error Message

%IDS-4-TCP_SENDMAIL_BAD_TO_SIG: Sig:3101:Sendmail Invalid Recipient - from [int] to [int]

Explanation This message is triggered on any mail message with a pipe (|) symbol in the recipient field.

Error Message

%IDS-4-TCP_SENDMAIL_BOUNCE_SIG: Sig:3100:Smail Attack - from [int] to [int]

Explanation This message is triggered on the very common "smail" attack against e-mail servers. This attack attempts to cause e-mail servers to execute programs on behalf of the attacker.

Error Message

%IDS-4-TCP_SENDMAIL_DECODE: Sig:3105:Sendmail Decode Alias - from [int] to [int]

Explanation This message is triggered on any mail message with decode in the header. The decode alias is used to uudecode files and is primarily implemented as a convenience for system administration.

Recommended Action The decode alias is used to uudecode files and is primarily implemented as a convenience for system administration. For security purposes this should not be allowed and the service should be disabled. If allowed, users that mail to the alias will trigger this signature. Shunning of hosts that attempt to mail to this alias, especially if they are outside of your network is recommended.

Error Message

%IDS-4-TCP_SENDMAIL_INVALID_COMMAND: Invalid SMTP command - from [int] to [int]

Explanation This message is triggered on an invalid SMTP command in the SMTP connection. It indicates that a suspicious violation was detected that may be an attack to the mail server system.

Recommended Action This is unusual traffic and may warrant investigation. Call your Cisco technical support representative.

Error Message

%IDS-4-TCP_SENDMAIL_OLD_SIG: Sig:3104:Archaic Sendmail Attacks - from [int] to [int]

Explanation This message is triggered when wiz or debug commands are sent to the SMTP port.

Recommended Action There is no reason for this type of traffic to be seen on modern networks. There is little chance that there will be any adverse effects from someone attempting these old hacks. Prudent security practices would suggest that the source of this attempt be shunned.

Error Message

%IDS-4-TCP_SENDMAIL_SPAM_SIG: Sig:3106:Excessive Rcpt to: (SPAM) - from [int] to [int]

Explanation Parse for "RCPT TO:" in header. Alarm on threshold.

Recommended Action Some mailing list software may trigger this signature.Call your Cisco technical support representative.

Error Message

%IDS-4-TCP_SENDMAIL_VRFY_SIG: Sig:3103:Sendmail Reconnaissance - from [int] to [int]

Explanation This message is triggered when "expn" or "vrfy" commands are entered to the SMTP port.

Recommended Action These commands are commonly used to verify that a user mail account exists on the server or to expand an alias to determine who the actual recipients of a message may be. Users that use the EXPN and VRFY functions for legitimate purposes will trigger this signature. The information that can be obtained is useful, but not dangerous on its own. Monitoring of future traffic for patterns of misuse is recommended.

Error Message

%IDS-4-TCP_SYN_ATTACK_SIG: Sig:3050:Half-Open Syn Flood - from [int] to [int]

Explanation This message is triggered when the number of half-open TCP connections exceeds the high-water mark or the one-minute high-rate mark.

Recommended Action There are no known sources that would legitimately generate this traffic pattern. This may indicate some type of network problem and should be investigated. To avoid depletion of your network resources it is recommended that the source be shunned during the course of the investigation. If no network problems are discovered prudent security practices would suggest that the source be shunned permanently.

Error Message

%IDS-4-TCP_SYN_FIN_SIG: Sig:3041:TCP - SYN and FIN bits set - from [int] to [int]

Explanation This message is triggered when a TCP packet is received with both the SYN and FIN bits set in the flags field.

Recommended Action There is no legitimate use for malformed TCP datagrams. This is unusual traffic and warrants investigation. Hacker tools will generate TCP packets with the SYN and FIN bits set in the flags field in an attempt to elude intrusion dection. When nonspecific network traffic of this type is encountered, the most prudent action from a security perspective is to shun or disallow it. If the source of this traffic is legitimate the user will then identify itself.

Error Message

%IDS-4-UDP_BOMB_SIG: Sig:4050:UDP Bomb - from [int] to [int]

Explanation This message is triggered when the UDP length specified is less than the IP length specified. This malformed packet type is associated with a denial of service attempt.

Recommended Action There is no legitimate use for malformed datagrams. This may be indicative of systems that are experiencing problems with their kernel or network interface cards. This is unusual traffic and warrants investigation. When nonspecific network traffic of this type is encountered, the most prudent action from a security perspective is to shun or disallow it. If the source of this traffic is legitimate the user will then identify itself.

Error Message

%IDS-4-UDP_TFTP_PASSWD_SIG: Sig:4100:Tftp Passwd File - from [int] to [int]

Explanation This message is triggered when someone tries to send a password file using TFTP.

Recommended Action System administrators might use this service to update system files. It is a high security risk if this is normal practice and should be avoided. No other benign triggers exist for this signature. If investigation shows the alarm was not generated by a system administrator, prudent security practices would suggest that the source be shunned.

Error Message

%IDTATM25-6-TXLIMIT: ATM transmit bandwidth is limited to smallest shaped value

Explanation Any PVC configured with traffic shaping will limit the entire ATM interface to not exceed the bandwidth of any traffic-shaped PVC.

Recommended Action If the bandwidth currently set is too limited, reconfigure all PVCs with an appropriate bandwidth, or remove traffic shaping from the configuration.

Error Message

%IMA-5-ACTIVE_LINK_CHANGE: IMA Group [chars] now has [dec] active links, active link bitmap is [hex]

Explanation Active links were added or removed from the group, changing its bandwidth.

Recommended Action No action is required.

Error Message

%IMA-1-BAD_CMD: Command opcode [hex] on channel [dec] on slot [dec] was rejected

Explanation The IMA firmware rejected the command because of the current protocol state of the interface, or the opcode is undefined.

Error Message

%IMA-4-CLOCK_MODE_COMMON_DELAYED: Link [dec] will become the common transmit clock once it is added to group [chars]

Explanation The link configured as the common transmit clock is not a member of the group, so it cannot provide the clock. The group will use a common transmit clock that is automatically chosen from one of the other active links.

Recommended Action No action is required.

Error Message

%IMA-1-DISCOVER: The Network Module in slot [dec] did not initialize

Explanation The Network Module failed its initialization.

Error Message

%IMA-1-DOWNLOAD_FAILED: Download of [chars] to failed to at [hex] on IMA Network Module in slot [dec]

Explanation An error occurred during the download of firmware to the IMA Network Module.

Error Message

%IMA-1-FPGA_DOWNLOAD_FAIL: FPGA Download on module in slot [dec] failed.

Explanation An error occurred during the download of the FPGA on the IMA NM.

Error Message

%IMA-1-INVALID_PCI_ID: The Network Module in slot [dec] reports an invalid [chars] device id of [hex]

Explanation The IMA Network Module hardware may be bad.

Error Message

%IMA-1-MAILBOX_FULL: The mailbox for channel [dec] on IMA Network Module in slot [dec] is completely full, Message [dec] was dropped

Explanation The IMA Network Module mailboxes are full and cannot accept any more requests.

Error Message

%IMA-1-NETWORK_PROCESSOR_NOT_READY: Network processor on module in slot [dec] failed to come up

Explanation An error occurred during a reset of the IMA Network Module.

Error Message

%IMA-1-NO_ATM_CHANNEL_AVAILABLE: Delaying activation of [chars] until a currently active interface is shutdown

Explanation The IMA Network Module can only support up to four activate interfaces at one time. Once more than four are shut down, each interface will wait for an existing interface to be shut down before becoming activated.

Error Message

%IMA-5-NO_LINK_MEMBERS: [chars] is using channel [dec] but has no configured links

Explanation The IMA interface has been configured Up but has no link members. It cannot become active until active links are added to the group.

Recommended Action No action is required.

Error Message

%IMA-1-NO_MAIL_REPLY: Timed out waiting for a response to command [hex] from slot [dec]

Explanation The IMA Network Module failed to respond with the requested information. Information to be displayed by the requesting exec command or SNMP manager is incomplete. This is an extremely rare event and should only happen under severe system load.

Error Message

%IMA-1-PCMCIA: The IMA Network Module in slot [dec] is incompatible with the PCMCIA controller in the router

Explanation The PCMCIA controller is down level.

Recommended Action Copy the error message exactly as it appears, and contact your technical support representative for upgrade information.

Error Message

%IMA-1-PROCESS_NEVER_RECEIVED_MAIL_REPLY: Previous process [dec] never received mail response from slot [dec]

Explanation The previous requesting process was terminated before a mail reply was received.

Error Message

%IMA-1-SHARED_MEMORY_ERROR: Module in slot [dec] had a shared memory error

Explanation Memory on the Network Module failed the power-on diagnostic check.

Error Message

%IMA-4-TEST_LINK_DELAYED: Link [dec] will initiate the test pattern procedure once it is added to group [chars]

Explanation The link chosen to send the test pattern is not a member of the group, thereby preventing the transmission of the test pattern.

Recommended Action No action is required.

Error Message

%IMA-4-TEST_LINK_STOPPED: Stopping test pattern procedure on group [chars]

Explanation The link sending the test pattern has been removed from the group, thereby stopping the transmission of the test pattern.

Recommended Action No action is required.

Error Message

%INTERFACE_API-4-BADPOINTER: Function [chars] detected an invalid [chars] pointer of [hex], ignoring

Explanation A software error occurred. This message is displayed when an invalid pointer is detected.

Error Message

%INTERFACE_API-1-NOMORESWIDB: No more SWIDB can be allocated, maximum allowed [dec]

Explanation No more interfaces can be created because the maximum number of SWIDB allowed for this platform has been reached.

Error Message

%IOCARD-3-IONOT0: IO card discovered in non-zero slot [dec]

Explanation An I/O card was detected in a nonzero slot.

Error Message

%IOCARD-3-UNSUPPORTED: [chars] in slot[dec] is not supported on [chars] chassis

Explanation The software identified and disabled the Fast Ethernet (FE) on the I/O card.

Recommended Action No action required.

Error Message

%IP-5-ACL: [chars]

Explanation An error occurred in IP access checks.

Error Message

%IPCGRP-3-EVENTOP: Event [int] from slot[int]: [chars]

Explanation IPC event processing operational errors occurred.

Error Message

%IPCLC-3-INTRLVL: LC interrupt level IPC event, [chars]

Explanation IPC event processing errors occurred at the LC interrupt level.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%IPFAST-2-PAKSTICK: Corrupted pak header for [chars], flags [hex], ONEMIN

Explanation A programming error occurred.

Error Message

%IPM_C54X-3-DSP_ALARM_INDICATION: DSP [dec] Sending alarm indication

Explanation The domain specific part (DSP) is indicating that an unexpected event has occurred. Therefore, the domain specific part (DSP) may not continue to process calls.

Error Message

%IPM_C54X-1-DSP_TIMEOUT: dsp [dec] NOT RESPONDING

Explanation The domain specific part (DSP) driver cannot queue messages up to the direct memory access (DMA) engine for transmission.

Error Message

%IPM_C54X-3-EPIC_NOT_RESPONDING: Epic TDM Switch failure

Explanation The EPIC TDM switch failed to acknowledge a command.

Error Message

%IPM_C54X-3-ERROR_INIT_BLDR: [chars] Unable to download the Boot loader firmware, ret = 0x[hex]

Explanation An error initializing the domain specific part (DSP) with the bootloader firmware occurred.

Recommended Action Power down, reinsert the port module, and reboot. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%IPM_C54X-3-ERROR_INIT_OVERLAY: [chars] Unable to download the Application overlay firmware. Status returned 0x[hex]

Explanation An error initializing the domain specific part (DSP) with the application/overlay firmware has occurred.

Error Message

%IPM_C54X-3-IDB_CREATE: Unable to allocate IDB

Explanation This message indicates that it is not possible to allocate the domain specific part (DSP) Interface IDB.

Error Message

%IPM_C54X-3-INIT_CONFIG_FAILED: DSP [dec] Sending alarm indication

Explanation The domain specific part (DSP) is indicating that it is not able to properly initialize the port(s) it services.

Error Message

%IPM_C54X-3-NODSP: Can't get dsp resources

Explanation There are not enough domain specific parts (DSPs) for all the VICs in the router.

Recommended Action Upgrade your domain specific part (DSP) module to get more DSPs. Use the show diag command to confirm the number of DSPs on the router.

Error Message

%IPM_C54X-3-NO_BUFFERS: No buffers available for DSP buffer pool

Explanation Unable to allocate buffers to domain specific part (DSP) receive buffer pool.

Error Message

%IPM_C54X-1-NO_RING_DESCRIPTORS: No more ring descriptors available on [dec] slot

Explanation The domain specific part (DSP) driver cannot queue messages up to the Direct Memory Access (DMA) engine for transmission.

Error Message

%IPM_C54X-1-TOOBIG: [chars], packet(size [dec]) too big

Explanation A packet greater than the 256-byte limit was received on this interface.

%IPMOBILE-6-SECURE: Security violation on [chars] from [chars] [int] - errcode [chars] ([dec]), reason [chars] ([dec])

Explanation A security violation occurred during registration attempt.

Recommended Action No action is required.

Error Message

%IPRT-3-IPTABLEINIT: IP routing table creation failure - [chars]

Explanation An internal software error occurred that prevents the creation of a new IP routing table.

Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.

Error Message

%IPRT-3-ROUTELIMITEXCEEDED: IP routing table limit exceeded - [chars], [int]%m

Explanation The number of routes in the named IP routing table reached the configured limit. No further routes will be added to the table.

Recommended Action Reduce the number of routes in the table, or reconfigure the limit.

Error Message

%IPRT-3-ROUTELIMITWARNING: IP routing table limit warning - [chars]

Explanation The number of routes in the named IP routing table reached the configured warning limit.

Recommended Action Reduce the number of routes in the table, or reconfigure the limit.

Error Message

%ISA-1-ALIGN: Alignment failure on packet buffer: 0x[hex]

Explanation A software error occurred. The Integrated Service Port Adapter (ISA) driver detected that the buffer is not aligned correctly.

Error Message

%ISA-1-ERROR: [chars]

Explanation An error occurred in the application using Integrated Service Port Adapter (ISA).

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 Integrated Service Port Adapter (ISA) driver failed to initialize at the specified point.

Error Message

%ISA-1-INITFAIL: Slot [dec]: [chars]

Explanation The Integrated Service Port Adapter (ISA) driver failed to initialize at the specified point.

Error Message

%ISA-1-NOMEMORY: [chars] creation failed for slot [dec]

Explanation The Integrated Service Port Adapter (ISA) driver, in its initialization phase, could not allocate memory for the specified data structure.

Recommended Action Consider adding more shared memory. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%ISA-1-OWNER: [chars] packet buffer, pak=0x[hex]

Explanation A software or hardware error occurred. The Integrated Service Port Adapter (ISA) driver detected that the buffer ring is in an inconsistent and unrecoverable state.

Error Message

%ISA-6-SHUTDOWN: [chars] shutting down

Explanation The specified Integrated Service Port Adapter (ISA) is shutting down. It may have been physically removed.

Recommended Action This is an informational message only. It occurs in normal operation.

Error Message

%ISA-1-TOOBIG: [chars] received a packet with size [dec].

Explanation The software cannot accept a packet of this size.

Error Message

%ISDN-4-BAD_DSL_FOR_CREATE_DELETE_L2: [chars]: isdn_create_delete_signalling_channel: Unknown DSL [int] for [chars]

Explanation The Creation/Deletion service for the Layer 2 signalling handler for the given digital subscriber line (DSL) is missing.

Error Message

%ISDN-4-GET_STATUS_STATE_FAIL: [chars]: isdn_get_status_state: Unknown DSL [int]

Explanation This message indicates an attempt to retrieve the status of a digital subscriber line (DSL) that is not currently configured.

Error Message

%ISDN-4-INVALID_EVENT: [chars]: Bad Event Received For Current State

Explanation The State Transition for the ISDN Layer 2 socket process failed.

Error Message

%ISDN-4-ISDN_L2_INTERFACE_NOT_REGISTERED: [chars]: isdn_to_L2: Unknown DSL [int] for command [chars]

Explanation The ISDN Stack has not registered its Layer 2 Message Handler.

Error Message

%ISDN-4-OPEN_TEMP_SOCKET_FAIL: [chars]: Failed to Open Required Temporary Socket[chars]

Explanation The (Re)Open attempt for a required temporary socket failed; without this socket the Layer 2 socket process will fail.

Error Message

%ISDN-4-SPURIOUS_CONNECT: [chars]: Spurious Connection Accepted and Closed on port [int]

Explanation An unknown TCP connection was refused.

Error Message

%KINEPAK-3-CONTIGUOUS: Contiguous packet sent for transmit

Explanation A software error occurred, resulting in an unexpected packet being set up for transmission and the packet was dropped.

Error Message

%KINEPAK-3-ERR_DSPWARE_DNLD: dsp[dec] cannot download dspware [chars]

Explanation A software error occurred, resulting in failure to download a DSPWARE component.

Error Message

%KINEPAK-3-ERR_DSPWARE_IMG: Cannot find dspware [chars] component

Explanation A software error occurred resulting in failure to download a DSPWARE component.

Error Message

%KINEPAK-3-NODSPENTRY: No dsp entry in dsp list

Explanation The software structure that is used to maintain the domain specific part (DSP) instance is missing.

Error Message

%KINEPAK-3-NOMAILELEMENTS: Cannot create message buffer

Explanation A software error occurred, resulting in failure to create a message buffer to send messages among processes.

Error Message

%KINEPAK-3-NOPARTICLE: No particle available for ingress packet

Explanation A software error occurred, resulting in failure to obtain a particle to hold an ingress packet from domain specific part (DSP).

Error Message

%KINEPAK-3-NOPARTICLEPOOL: Cannot create particle pool

Explanation A software error occurred, resulting in failure to create a particle pool to receive packets from domain specific part (DSP).

Error Message

%KINEPAK-3-NORXPAK: Static receive paktype unavailable

Explanation A software structure was found in an unexpected state during the runtime for the indicated domain specific part (DSP).

Error Message

%LANE-3-LEC_RD_REGISTER: [chars] RD REGISTER failed for Route Descriptor [hex]

Explanation A software or hardware error occurred.

Error Message

%LAPB-3-BADPAYLOAD: Interface [chars], Invalid payload value: [chars]

Explanation An internal software error occurred.

Recommended Action If either of these messages recur, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

%LAT-3-BADDATA: Tty%t, Data pointer does not correspond to current packet

Explanation An internal software error occurred.

Error Message

%LAT-3-BUFFULL: Tty%t, data buffer full with count [dec]

Explanation An internal software error occurred.

Error Message

%LAT-3-NOSYNC: Tty%t, Output data ptrs out of sync with byte count

Explanation An internal software error occurred.

Error Message

%LAT-3-REUSE: Tty%t, Attempt to re-use slot array, empty = [dec], fill = [dec]

Explanation An internal software error occurred.

Error Message

%LCB-3-LOCKFAILURE: Multiple LCB event processes scheduled

Explanation This message occurs when LCB event process fails to lock the semaphore that used to prevent multiple LCB processes from running. This implies that multiple LCB processes that should not happen have been scheduled to run.

Recommended Action Try executing the command again after a few minutes. If the problem persists, contact your Cisco technical support representative.

Error Message

%LCB-3-QUEUEFAILURE: LCB process unable to create event queue

Explanation The LCB process was not able to create an LCB event queue. The LCB process has quit, and the operating system was unable to allocate RAM space for the queue.

Recommended Action Try executing the command again after a few minutes. If the problem persists, there is a lack of RAM space. Most likely, the router image requires more system memory, or RAM, than the router contains.

Error Message

%LC-3-LC_FLASH_PROG_ALLOC: Can not allocate [chars]

Explanation For the GLC Flash program command, the watch queue, buffer, or process creation failed.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%LC-3-LOOKUP_COMPL: Hardware assist lookup error 0x[hex] in memory encountered. hw 0x[hex] sw 0x[hex] ip 0x[hex] root 0x[hex] first 0x[hex] second 0x[hex] third 0x[hex] leaf 0x[hex]

Explanation Memory corruption was detected.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%LC-3-LOOKUP_RANGE: Hardware assist lookup error 0x[hex] in memory encountered. hw 0x[hex] sw 0x[hex] ip 0x[hex] root 0x[hex] first 0x[hex] second 0x[hex] third 0x[hex] leaf 0x[hex]

Explanation A memory corruption detected.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%LC-3-MACSTR: Adj/midb ([chars]) incorrect macstring: length=[dec], macstr word=0x[hex]

Explanation The line card CEF/MDS received an adjacency/midb with the incorrect MAC rewrite string. Packets forwarded to that adjacency/midb will be dropped.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%LC-3-MLLC: Channel or Port [int]: [chars] malloc failure

Explanation A memory allocation failure on LC occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%LC-3-OUTINFO: Adj/midb([chars]): incorrect output_info=0x[hex] maclen=[dec]

Explanation The line card CEF/MDS received an adjacency/midb with the incorrect output_info field. Packets forwarded to that adjacency/midb will be dropped.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%LCFE-4-CAM_DONE_TIME: CAM [chars]: wait for DONE exceeded timeout ([dec] ms)

Explanation The LC Fast Ethernet RX Translator CAM DONE bit was not reset to 1 on a write or read within the given timeout period.

Error Message

%LCFE-6-CAM_INIT: HW MAC address filter (CAM) init failed: CAM disabled

Explanation The CAM hardware containing the MAC address filter failed.

Error Message

%LCFE-3-FE_RX_MICE: NULL

Explanation LC Fast Ethernet Mice FPGA could not be loaded.

Error Message

%LCFE-1-INITFAIL: LCFE([dec]/[dec]), initialization timeout failure

Explanation LC Fast Ethernet hardware initialization failed.

Error Message

%LCFE-6-LINE_STATE: Line state [chars]

Explanation A line state error was detected or fixed as specified in the message.

Recommended Action Check cable connections. The local RX cable must be connected to the remote TX cable, and vice versa.

Error Message

%LCFE-4-OP: error: [chars]

Explanation Line card Fast Ethernet driver general operation errors occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%LCFE-4-RPCMD: [chars] command error: [chars]

Explanation Line card Fast Ethernet driver handles RP command errors occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%LCFE-6-RX_LOS: [chars] RX Loss of Signal

Explanation ARX loss of signal error was detected or fixed as specified in the message.

Recommended Action Check cable connections. The local RX cable must be connected to remote TX cable, and vice versa.

Error Message

%LCFE-3-RX_TX_TRANS: NULL

Explanation LC Fast Ethernet RX/TX Translator FPGA could not be loaded.

Error Message

%LCFE-6-SYNC_LOSS: [chars]

Explanation A loss of synchronization error was detected or was cleared as specified in the message.

Recommended Action Check cable connections. The local RX cable must be connected to the remote TX cable, and vice versa.

Error Message

%LCGE-6-CAM_ADD: Failed to add address [sci_notation] to CAM

Explanation An entry was not added to the CAM MAC address filter.

Error Message

%LCGE-4-CAM_DONE_ITER: CAM [chars]: wait for DONE exceeded [dec] iterations

Explanation The LC Gigabit Ethernet RX GigaTranslator CAM DONE bit was not reset to 1 on a write or read within the given number of iterations.

Error Message

%LCGE-6-CAM_EXCEEDED: [dec] entries to add [dec] entries available

Explanation An entry was not added to the CAM MAC address filter.

Error Message

%LCGE-6-CAM_INIT: CAM MAC address filter init failed: CAM disabled

Explanation An entry was not added to the CAM MAC address filter.

Error Message

%LCGE-6-CAM_REMOVE: Failed to remove address [sci_notation] from CAM

Explanation An entry was not added to the CAM MAC address filter.

Error Message

%LCGE-6-GBIC_OIR: [chars] [chars] [dec]

Explanation A GBIC insertion/removal event was detected as specified in the message.

Recommended Action No action is required.

Error Message

%LCGE-6-GBIC_READ: Cannot read GBIC in port [dec], perhaps absent or faulty

Explanation The GBIC can not be read, check if it is inserted correctly. If it is inserted and the problem persists, replace the GBIC.

Error Message

%LCGE-6-GBIC_TX_FAULT: GBIC TX Fault [chars]

Explanation A GBIC TX Fault error was detected or fixed as specified in the message.

Recommended Action Check GBIC and cable connections.The local RX cable must be connected to remote TX cable, and vice versa.

Error Message

%LCGE-1-INITFAIL: LCGE([dec]/[dec]), initialization timeout failure

Explanation Line card gigabit Ethernet hardware initialization failed.

Error Message

%LCGE-3-INTR: [chars]

Explanation LC gigabit Ethernet RX GigaTranslator FPGA could not be loaded.

Error Message

%LCGE-6-LINE_STATE: Line state [chars]

Explanation A GBIC line state error was detected or fixed as specified in the message.

Recommended Action Check GBIC and cable connections. Local RX cable must be connected to the remote TX cable, and vice versa.

Error Message

%LCGE-4-OP: error: [chars]

Explanation Line card gigabit Ethernet driver general operation errors occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%LCGE-4-RPCMD: [chars] command error: [chars]

Explanation Line card gigabit Ethernet driver handles the RP command errors.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%LCGE-6-RX_LOS: [chars] RX Loss of Signal

Explanation A GBIC RX loss of signal error was detected or fixed as specified in the message.

Recommended Action Check GBIC and cable connections. The local RX cable must be connected to remote TX cable, and vice versa.

Error Message

%LCGE-3-RX_TRANS: NULL

Explanation LC gigabit Ethernet RX GigaTranslator FPGA could not be loaded.

Error Message

%LCGE-3-RX_TRANS_PROG: NULL

Explanation LC gigabit Ethernet RX GigaTranslator FPGA is not programmed.

Error Message

%LCGE-6-SYNC_LOSS: [chars]

Explanation A GBIC loss of synchronization error was detected or was cleared as specified in the message.

Recommended Action Check GBIC and cable connections. The local RX cable must be connected to the remote TX cable, and vice versa.

Error Message

%LINK-2-BADVCALL: Interface [chars], undefined entry point

Explanation An internal software error occurred. The high-level system code tried to use an unimplemented entry point with the virtual interface descriptor block (IDB) driver.

Error Message

%LINK-2-INTVULN: In critical region with interrupt level=[dec], intfc=[chars]

Explanation An internal software error occurred. The high-level system code tried to call this routine with interrupts enabled.

Error Message

%LINK-0-REENTER: Fatal reentrancy, level=[dec], intfc=[chars]

Explanation An internal software error occurred. The system code tried to access a critical data structure that was already in use.

Error Message

%LPD-3-MANYLF: Line %t, packet has too many newlines to convert

Explanation An internal buffer did not have enough room to add all the necessary carriage returns to a packet of the line printer daemon (LPD) data destined for a printer configured with a newline-convert command. This message is unlikely to occur with a file containing valid data.

Recommended Action Check the file being printed to see whether it contains valid, printable data.

Error Message

%M32X-1-AR_TIMEOUT: M32X controller [dec], channel 0x[hex]: No Response from device. Action Request Timeout

Explanation The Action Request for a particular failed after retry.

Recommended Action No action is required.

Error Message

%M32X-5-REMLOOP: M32X controller [dec], channel [dec]: remote loopback [chars], [chars]

Explanation The interface entered or exited a remote loopback.

Recommended Action No action is required.

Error Message

%MBUS-3-INSUFF_BW: Insufficient fabric bandwidth to launch and operate card in slot [dec]

Explanation Some line cards (for example 4 Port E.D. Packet over SONET OC-12c/STM-4, or 1 Port E.D. Packet over SONET OC-48c/STM-16) cannot operate in quarter bandwidth mode. Full fabric bandwidth must be available to launch and operate these line cards. Full fabric bandwidth typically is achieved either by one CSC and three SFCs or two CSCs and two SFCs. To obtain fully redundant full fabric bandwidth, two CSCs and three SFCs are the only possible configurations. In any case a minimum of one CSC and three or more switch cards (CSC or SFC) is required for full fabric bandwidth.

Recommended Action Make sure the CSCs and SFCs are properly inserted and in good working condition. Verify that there are a total of four working switch cards with the minimum of one CSC. If switch cards are missing or nonoperational, contact your technical support representative.

Error Message

%MBUS-0-OLD_SCA: Old SCA found on clock switch card (CSC) in slot [dec]

Explanation The CSC is an old or nonproduction card.

Recommended Action Obtain a new CSC from your technical support representative.

Error Message

%MEMSCAN-2-BSSREG: Parity error(0x[hex]) found in imagebss region

Explanation A parity error was found in the BSS region of memory.

Recommended Action Schedule a reboot of the system to clear memory as soon as possible. If this parity error is touched in normal operation of the router the router will crash. If more parity errors are found at this address after the reboot, replace the DRAM in the router or the processor board.

Error Message

%MEMSCAN-2-DATAREG: Parity error(0x[hex]) found in imagedata region

Explanation A parity error was found in the data region of memory.

Recommended Action Schedule a reboot of the system to clear memory as soon as possible. If this parity error is touched in normal operation of the router, it will fail. If more parity errors are found at this address after the reboot, replace the DRAM in the router or the processor board.

Error Message

%MEMSCAN-3-DUPERR: Another parity error(0x[hex]) found in bolck(0x[hex]). Not scrubbed

Explanation Multiple errors have been found in a memory block.

Error Message

%MEMSCAN-3-INPREV: Parity error(0x[hex]) found in block field , , previous

Explanation A parity error was found in a critical field of a block header.

Error Message

%MEMSCAN-3-INUSE: Parity error(0x[hex]) found in busy bolck(0x[hex])

Explanation A parity error was found in a busy block that cannot be scrubbed nor moved to the defective list.

Recommended Action Schedule a reboot of the system to clear memory as soon as possible. If this parity error is touched in normal operation of the router, the router will fail. If more parity errors are found at this address after the reboot, replace the DRAM in the router or the processor board.

Error Message

%MEMSCAN-6-LINKED: Error(0x[hex]) block(0x[hex]) linked, size [dec]

Explanation A parity error was found in a free block that could not be scrubbed. The free block has been moved to a defective list so that it cannot be used again.

Recommended Action Schedule a reboot of the system to clear memory. If more parity errors are found at this address after the reboot, replace the DRAM in the router or the processor board.

Error Message

%MEMSCAN-6-MSCRUBED: Parity error(0x[hex]) scrubbed multiple times

Explanation Multiple parity errors were found at this address.

Recommended Action Power down the router and replace the DRAM.

Error Message

%MEMSCAN-6-SCRUBED: Parity error(0x[hex]) scrubbed

Explanation A memory parity error was found and scrubbed.

Recommended Action No action is required.

Error Message

%MEMSCAN-6-SPLIT: Error(0x[hex]) block(0x[hex]) split, bad block(0x[hex]) linked, size 0x[hex]

Explanation A parity error was found in a free block that could not be scrubbed. The free block was fragmented and the fragment with the parity error was moved to a defective list so that it cannot be used again.

Recommended Action Schedule a reboot of the system to clear memory. If more parity errors are found at this address after the reboot, replace the DRAM in the router or the processor board.

Error Message

%MEMSCAN-2-TEXTREG: Parity error(0x[hex]) found in imagetext region

Explanation A parity error was found in the text region of memory.

Error Message

%MEMSCAN-3-UNKNOWN: Parity error(0x[hex]) found in other(unknown) region

Explanation A parity error was found in an unknown region of memory.

Error Message

%MICA-1-BOOTFLASH: [chars]

Explanation The MICA modem firmware download file was not found in BOOTFLASH.

Error Message

%MICA-3-MODEMBAD: Modem number [dec]/[dec] is bad, Error code is [hex]

Explanation A message from the MICA modem driver indicates that the modem is defective.

Error Message

%MICA-3-NOMAILELEMENTS: Exhausted free mail elements for modem_num [dec]

Explanation The software structures that are used to receive and send messages from the MICA modems were temporarily exhausted.

Error Message

%MODEM-1-DL_FAIL: Firmware download failed for slot [dec] module_mask [hex]

Explanation The modem modules did not send back an initialized message after the download.

Error Message

%MODEM-1-DL_FAIL_FILE_XFER: Firmware download failed for slot [dec] module_mask 0x[hex] due to file transfer error

Explanation The download of a portware file to the modem card over DSIP as part of a modem firmware upgrade attempt timed out and failed to successfully complete.

Error Message

%MODEM_HIST-7-MICA_DEBUG_EVT: [chars]: [chars]:

Explanation This is a tracing message indicating a host debug event reported by the specified MICA modem.

Recommended Action This is a debug message only. No action is required.

Error Message

%MODEM_HIST-7-MICA_LEAD_EVT: [chars]: [chars]: [chars], [chars], [chars], [chars]

Explanation This is a tracing message indicating a lead event reported by the specified MICA modem.

Recommended Action This is a debug message only. No action is required.

Error Message

%MODEM-3-MODEMSTART_OUTOFMEM: Error -- Unable to allocate memory to startup modem board in slot [dec]

Explanation During modem board startup, modem memory ran out.

Recommended Action Save the output of the show memory command showing the amount of processor and IO memory usage, and output of the show version command, and call your technical support representative for assistance.

Error Message

%MROUTE-4-RPF_LOOKUP_LOOP: RPF route lookup loop for [int], route [int]/[dec]

Explanation This message indicates a possible routing loop caused by routers using Reverse Path Forwarding (RPF) to use different tables.

Recommended Action Check routing tables used for Reverse Path Forwarding (RPF).

Error Message

%MSDP-5-PEER_UPDOWN: Session to peer [int] going [chars]

Explanation A session to a peer is going up or down.

Recommended Action Determine if the router is low on memory.

Error Message %NRP-3-IPC: [chars] [chars]

Explanation An Interprocess Communication (IPC) error occurred. The details about what was attempted and what went wrong will be printed.

Recommended Action Copy the error message exactly as it appears. Copy the configuration of the router along with any other relevant information, and call your Cisco technical support representative for assistance.

Error Message

%NRP-4-SLAVE_DOWN: NRP-REDUNDANCY Secondary NRP in slot [dec], went down

Explanation The Primary NRP lost communication with the redundant NRP.

Recommended Action Call your Cisco technical support representative for assistance.

Error Message

%NRP-5-SLAVE_UP: NRP-REDUNDANCY Secondary NRP in slot [dec], came up

Explanation The Redundancy NRP came up and established communication with the Primary NRP.

Recommended Action Call your Cisco technical support representative for assistance.

Error Message

%OSPF-6-BADCHKSUM: Checksum Failure in database in area [chars] Link State Id [int] Old Checksum [hex] New Checksum [hex] , OSPF_COMPLAIN_IVL

Explanation Open Shortest Path First (OSPF) detected a checksum error in the database caused by memory corruption.

Recommended Action Restart the OSPF process.

Error Message

%OSPF-3-DUP_RTRID: OSPF detected duplicate router-id [int] from [int] on interface [chars]

Explanation Open Shortest Path First (OSPF) received a hello packet from a neighbor that has the same router-id as this routing process. A full adjacency cannot be established.

Recommended Action The Open Shortest Path First (OSPF) router ID should be unique. Change the router ID of the neighbor.

Error Message

%OSPF-3-INIT_IDB: OSPF is enabled on [chars] during idb initialization

Explanation An internal error occurred.

Error Message

%OSPF-4-NORTRID: OSPF process [dec] cannot start. There must be at least one up IP interface, for OSPF to use as router ID, OSPF_COMPLAIN_IVL

Explanation The Open Shortest Path First (OSPF) process failed while attempting to allocate a router ID from the IP address of one of its interfaces.

Recommended Action Ensure that there one interface is up and has a valid IP address. If multiple Open Shortest Path First (OSPF) processes are running on the router, each requires a unique router ID. You must have enough "up" interfaces so that each of them can obtain a router ID.

Error Message

%OSPF-6-NOTREDIST3: build_ex_route(): don't redistribute net [int]%m, [int] advertises it already, OSPF_COMPLAIN_IVL

Explanation This message is informational only.

Recommended Action No action is required.

Error Message

%OSPF-3-RECONF_VL: OSPF process [dec] is changing router-id. Reconfigure virtual link neighbors with our new router-id

Explanation The Open Shortest Path First (OSPF) process is being reset, and will select a new router ID which will bring down all virtual links.

Recommended Action Change virtual link configuration on all the virtual link neighbors, to reflect the new router ID.

Error Message

%PA-3-CONFIG: Recommended port adapter configuration exceeded

Explanation The total bandwidth of fast and medium bandwidth port adapters exceeded the rated capacity of this system.

Recommended Action Refer to the configuration guidelines for the maximum allowed high and medium bandwidth port adapters for the system.

Error Message

%PAD-3-GETLINE: Tty%t, bad return code [dec] from x3_getline()

Explanation An internal software error occurred.

Error Message

%PAD-2-PUTSETUP: Tty%t, buffer already setup

Explanation An internal software error occurred.

Error Message

%PA-2-ILLEGALPA: Illegal Port Adaptor type [dec] in bay [dec] of [chars]

Explanation The port adapter is not supported by the controller it is plugged into.

Recommended Action Remove the port adapter and return the controller to its original configuration.

Error Message

%PA-4-PCIVALID: PCI activation failed, bay [dec], 0x[hex]

Explanation The system received an invalid protocol control information (PCI) signal from the port adapter. This message is probably due to a hardware failure.

Error Message

%PA-3-REVNOTSUPPORTED: PA in slot[dec] ([chars]) requires base h/w revision of ([dec].[dec]) for this [chars]

Explanation A newer hardware revision of the port adapter is required for functional operation on this chassis.

Error Message

%PARSER-4-INVLDLINE: Invalid line in NV generation: %t The parser failed an internal software check.

Explanation The parser failed an internal software check.

Error Message

%PA-2-UNDEFPABRIDGE: Unsupported Port Adaptor Bridge [hex] in bay [dec]

Explanation The software does not have a driver for the port adapter protocol control information bridge in the specified bay.

Error Message

%PGM-6-DLR_ADDR_ERR: Invalid DLR address [int]

Explanation An OPT_RDIR with an invalid DLR address was received.

Recommended Action No action is required.

Error Message

%PGM-3-EXP_TSI_SQN_ERR: Expiring TSI [chars] has retransmit state

Explanation An expiring PGM TSI has unexpired retransmit state. This error can only occur due to an internal error or memory that cannot be freed.

Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco representative, and provide the representative with the gathered information.

Error Message

%PGM-6-NAK_IIF_FIXUP: NAK for [int] received on [int], fixed input interface

Explanation A NAK packet was received on an interface other than the one it was addressed to.

Recommended Action No action is required.

Error Message

%PGM-3-PAK_ALLOC_ERR: Failed to allocate buffer for [chars]

Explanation Resources (memory) for allocating packet buffers are not serviceable.

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

Error Message

%PGM-6-PAK_MALFORMED_ERR: Malformed packet: [chars]

Explanation A PGM packet did not pass the internal sanity check.

Recommended Action No action is required.

Error Message

%PGM-6-QUEUE_FULL: Serviced full queue of PGM packets

Explanation The PGM process is busy, either because of an excessive retransmit state or because of excessive traffic.

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

Error Message

%PGM-3-RTX_STATE_ALLOC_ERR: Failed to allocate [chars] state

Explanation Resources (memory) for retransmit state are exhausted or otherwise not serviceable.

Recommended Action Manually clear all retransmit state using the clear ip pgm router command or deconfigure and reconfigure PGM. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%PGM-3-RTX_STATE_FREE_ERR: Failed to free [chars] state

Explanation Resources (memory) for retransmit state are not serviceable.

Error Message

%PGM-6-TSI_GROUP_CHANGE: TSI group changed from [int] to [int]

Explanation A PGM SPM advertising a new group for the TSI was processed.

Recommended Action No action is required.

Error Message

%PIM-1-INVALID_RP_REG: Received Register from [int] for [int], not willing to be RP

Explanation A protocol-independent multicast (PIM) router received a register message from another PIM router configured for 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-INVALID_SRC_REG: Received Register from [int] for ([int], [int]), not willing to be RP

Explanation A protocol-independent multicast (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 Route Processor (RP).

Recommended Action No action is required.

Error Message

%PLATFORM-4-COOKIE: Corrupt or missing MAC address cookie using random base [sci_notation]

Explanation The contents of the MAC address electrically erasable programmable read-only memory (EEPROM) is invalid. The system is providing a random MAC address.

Recommended Action No action is required.

Error Message

%PLATFORM-4-NOCPUVER: Invalid CPU ID, assuming revision 1

Explanation The CPU ID could not be read from electrically erasable programmable read-only memory (EEPROM). This error is probably due to a hardware failure.

Recommended Action No action is required.

Error Message

%PLATFORM-3-NOMAC: Can't allocate MAC address for interface [int]/[int]

Explanation The MAC address allocation failed because of an incorrect slot and port combination, which exceeds the maximum available hardware.

Recommended Action No action is required.

Error Message

%PLATFORM-3-PACONFIG: Exceeds [dec] [chars]

Explanation The total bandwidth of fast and medium bandwidth port adapters exceeded the rated capacity of this system.

Recommended Action Refer to the configuration guidelines for the maximum allowed high and medium bandwidth port adapters for the system.

Recommended Action

Error Message

%PQUICC_ASYNC-3-CTSLOST: Unit [dec], Clear to Send Lost

Explanation The Clear To Send (CTS) input signal on a data terminal equipment (DTE) serial interface became inactive while sending a frame. This problem is a result of a communication line failure or cable disconnection.

Recommended Action Check the serial interface cable or communication equipment, such as the channel service unit/data service unit (CSU/DSU).

Error Message

%PQUICC-1-BADHDXFSM: PQUICC([dec]/[dec]), Unexpected HDX state [dec], event [dec]

Explanation A failed event was detected in the state machine for half duplex transmission/reception.

Error Message

%PQUICC-5-COLL: Unit [dec], excessive collisions. Retry limit [dec] exceeded

Explanation An Ethernet cable is broken or not terminated.

Recommended Action Check cables for proper connections, termination, and so on.

Error Message

%PQUICC-1-CTSLOST: PQUICC([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 a frame was being sent. This problem is a result of a communication line failure or cable disconnection.

Recommended Action Check the serial interface cable or communication equipment, such as the channel service unit/data service unit (CSU/DSU).

Error Message

%PQUICC_ETHER-5-COLL: Unit [dec], excessive collisions. Retry limit [dec] exceeded

Explanation An Ethernet cable is broken or not terminated.

Recommended Action Check cables for proper connections, termination, and so on.

Error Message

%PQUICC_ETHER-5-HBEAT: Unit [dec], heartbeat check failure

Explanation The Ethernet transceiver is malfunctioning.

Recommended Action Replace the hardware.

Error Message

%PQUICC_ETHER-1-INITFAIL: msgtxt_initfail

Explanation A software or hardware error occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%PQUICC_ETHER-5-LATECOLL: Unit [dec], late collision error

Explanation The Ethernet cable might be too long, or there could be too many repeaters such that the delay from one end to the other is too long. The Ethernet cable might be overloaded with too many users.

Recommended Action Verify that your Ethernet cable is the correct length and that you do not have too many repeaters in use. If these are not the problem, remove hosts from the Ethernet segment to reduce the load.

Error Message

%PQUICC_ETHER-1-LOSTCARR: Unit [dec], lost carrier. Transceiver problem?

Explanation The 10BaseT Ethernet cable is unplugged.

Recommended Action Connect the 10BaseT Ethernet cable.

Error Message

%PQUICC_ETHER-1-TXERR: [chars]: Fatal transmit error. Restarting...

Explanation A fatal transmit error occurred on the interface, causing the line to be restarted.

Recommended Action If this message recurs, call your technical support representative for assistance.

Error Message

%PQUICC_ETHER-3-UNDERFLO: Unit [dec], underflow error

Recommended Action No action is required.

Error Message

%PQUICC-5-HBEAT: Unit [dec], heartbeat check failure

Explanation The Ethernet transceiver is malfunctioning.

Recommended Action Replace the hardware.

Error Message

%PQUICC-1-INITFAIL: msgtxt_initfail

Explanation A software or hardware error occurred.

Error Message

%PQUICC-5-LATECOLL: Unit [dec], late collision error

Explanation The Ethernet cable might be too long, or there could be too many repeaters so that the delay from one end to the other is too long. The Ethernet cable might be overloaded with too many users.

Recommended Action Verify that your Ethernet cable is the correct length and that you do not have too many repeaters in use. If these are not the problem, try removing hosts from the Ethernet segment to reduce the load.

Error Message

%PQUICC-1-LINEFLAP: PQUICC([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.

Error Message

%PQUICC-1-LOSTCARR: Unit [dec], lost carrier. Transceiver problem?

Explanation The Ethernet 10BaseT cable is unplugged.

Recommended Action Connect the 10BaseT Ethernet cable.

Error Message

%PQUICC-1-NOMEMORY: msgtxt_nomemory

Explanation The MPC860/PowerQUICC CPU was unable to access the memory it needs to carry out its functions. The following are some possible causes: The network is large, requiring a lot of memory for routing tables; the router configuration has many features enabled, each of which require a certain amount of 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

%PQUICC-3-OWNERR: msgtxt_ownerror

Explanation An internal software error occurred.

Recommended Action Call your Cisco technical support representative to obtain a software upgrade.

Error Message

%PQUICC_SERIAL-3-CTSLOST: Unit [dec], Clear to Send Lost

Explanation The Clear To Send (CTS) input signal on a data terminal equipment (DTE) serial interface became inactive while sending a frame. This problem stems from 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

%PQUICC_SERIAL-1-INITFAIL: msgtxt_initfail

Explanation The serial interface controller of the PQUICC chip could not be initialized or started for operation. Most likely, a hardware problem exists.

Recommended Action Power cycle the system. If the error recurs, replace the unit.

Error Message

%PQUICC_SERIAL-5-LINEFLAP: Unit [dec], excessive modem control changes

Error Message

%PQUICC_SERIAL-3-UNDERFLO: Unit [dec], underflow error

Explanation While sending a frame, the local buffer of the serial controller chip received insufficient data because data could not be transferred to the chip fast enough to keep pace with its output rate. Such a problem usually is temporary, depending on transient peak loads within the system.

Recommended Action The system should recover. No action is required. If the problem recurs, it indicates a hardware error that might be related to data traffic patterns. Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%PQUICC-1-TOOBIG: PQUICC([dec]/[dec]), packet too big

Explanation A packet greater than the assigned maximum transmission unit (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, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%PQUICC-1-TOOSMALL: PQUICC([dec]/[dec]), packet was less than 2 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, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%PQUICC-1-TXERR: [chars]: Fatal transmit error. Restarting...

Explanation A fatal transmit error occurred on the interface, causing the line to be restarted.

Recommended Action If this message recurs, call your technical support representative for assistance.

Error Message

%PQUICC-3-UNDERFLO: Unit [dec], underflow error

Explanation While sending a frame, the local buffer of the controller chip 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. If the problem recurs, it indicates a hardware error that might be related to data traffic patterns. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%PQUICC-1-UNEXPECTED_INTERRUPT: PQUICC([dec]), Unexpected modem-signal interrupt

Explanation The software did not expect to see a modem control signal change on this type of WAN interface card (WIC) interface.

Error Message

%PQUICC-1-UNKNOWN_WIC: PQUICC([dec]), WIC card has an unknown ID of 0x[hex]

Explanation The software does not recognize the type of WAN interface card (WIC) plugged into the port module.

Recommended Action Check the part number on the WAN interface card (WIC) to verify that it is supported in the Cisco IOS software release operational on the router, or contact your technical support representative.

Error Message

%PQUICC-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.

Error Message

%PS-3-DCOUTPUTVOLTFAIL: System detected Power System [dec] DC FAIL condition

Explanation The power system experienced a DC failure.

Recommended Action One of the DC outputs failed on the power supply. Identify which DC output failed and replace the power supply.

Error Message

%PS-3-DCOUTPUTVOLTOK: Power System DC condition is now normal

Explanation This is an informational message only. The power system DC is normal.

Recommended Action No action is required.

Error Message

%PS-1-INITSYS: [chars]

Explanation Environmental monitor process failed to be created. This problem is most likely due to lack of memory.

Recommended Action The amount of memory available in the router may not be sufficient. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%PS-3-INPUTVOLTFAIL: System detected Power System [dec] AC FAIL condition.

Explanation The power system experienced an AC failure.

Recommended Action One of the AC inputs failed on the power supply. Identify which AC input failed. Make sure that the AC circuit in your building is operational, verify that the power cord is plugged into the power supply, and make sure that the AC power switch on the power supply is on.

Error Message

%PS-3-INPUTVOLTOK: Power System AC condition is now normal

Explanation This is an informational message only. The power system AC is normal.

Recommended Action No action is required.

Error Message

%PS-3-MULTFAIL: There is more than one failure with the Power System [dec]; please resolve problems immediately

Explanation The power system experienced multiple failures. This is a critical condition.

Recommended Action Examine the LEDs on the front of the power supply to find out which failures it has.

Error Message

%PS-3-OVERTEMP_OK: System temperature is now normal.

Explanation The system is operating at a normal temperature.

Recommended Action The system previously detected an over-temperature condition, which has now cleared. This message is most likely due to high ambient temperature where the router is located. Call your Cisco technical support representative for assistance.

Error Message

%PS-3-PSOK: Power System is now normal

Explanation This is an informational message only. The power system is operating normally.

Recommended Action No action is required.

Error Message

%PS-3-THERMOK: Power System THERMAL condition is now normal

Explanation The power system THERMAL is now normal.

Recommended Action The power supply previously detected an over-temperature condition, which has now cleared. This message is most likely due to high ambient temperature where the power supply is located. A power system thermal failure can also be caused by a fan failure in the power supply.

Error Message

%RADIUS-4-NOSERV: Warning: Server [int]:[dec], [dec] is not defined.

Explanation The given server is not on the master list and should be defined, or you may experience errors or unanticipated actions.

Recommended Action Define the server on the appropriate master list as soon as possible.

Error Message

%RADIUS-3-SECRETLENMAX: Secret exceeded max length

Explanation The user is attempting to store per-server secret, which exceeds the maximum length of 65 characters.

Recommended Action Configure a shorter secret.

Error Message

%RADIUS-6-SERVERALIVE: Radius server [int]:[dec], [dec] is responding again (previously dead).

Explanation A RADIUS server, which previously was dead, has started responding again.

Recommended Action No action is required.

Error Message

%RADIUS-4-SERVREF: Warning: Server [int]:[dec], [dec] is still referenced by server group.

Explanation The server being removed is still referenced by a server group.

Recommended Action De-reference the server from the server group as soon as possible.

Error Message

%Regen-3-BADADDR2: regen_big_endian_addr: Attempted conversion of invalid address (0x[hex])

Explanation A software error occurred while protocol control information (PCI) device addressing was being determined. This problem is most likely a software error.

Error Message

%Regen-3-BADADDR: regen_little_endian_addr: Attempted conversion of invalid address (0x[hex])

Explanation A software error occurred while protocol control information (PCI) device addressing was being determined. This problem is most likely a software error.

Error Message

%Regen-3-BADBAYDEV: get_pci_dev_num: Invalid bay ([dec]) or device number offset (%D)

Explanation A software error occurred while protocol control information (PCI) device addressing was being determined. This problem is most likely a software error.

Error Message

%Regen-3-BADDEVNO: pas_get_device_subunit: Invalid PCI device number: [dec]

Explanation A software error occurred while protocol control information (PCI) device addressing was being determined. This problem is most likely a software error.

Error Message

%Regen-3-BADNV: Detected invalid NVRAM size: [dec] bytes

Explanation The detected size of NVRAM is not one of the supported sizes. The NVRAM may be invalid.

Error Message

%Regen-3-BADPA: Invalid Port Adaptor type ([dec]) reported for mainboard

Explanation The virtual port adapter type derived from the mainboard type is not one of the supported types. It may be that this mainboard is a new mainboard type and the software release running does not support the new mainboard type.

Error Message

%Regen-3-BADPCIRD: PCI Configuration Read Cycle Failed for bus [dec], Device [dec], function [dec], register [dec]

Explanation A protocol control information (PCI) Bus Configuration Read cycle failed. The mainboard needs to be replaced.

Error Message

%Regen-3-BADPCIWR: PCI Configuration Write Cycle Failed for bus [dec], Device [dec], function [dec], register [dec]

Explanation A protocol control information (PCI) Bus Configuration Write cycle failed. The mainboard needs to be replaced.

Error Message

%Regen-3-NOMAC: Can't allocate MAC address for interface [int]/[int]

Explanation All of the available MAC addresses for the system have been allocated.

Error Message

%Regen-3-NVERASEFAIL: Failed to erase config due to internal error

Explanation Password protection failed to erase a configuration due to internal error.

Error Message

%Regen-1-OVERTEMP: System detected OVERTEMPERATURE condition. Putting the system in Power save mode and going to rommon. Please resolve cooling problem and restart system!

Explanation The environmental monitor detected a high-temperature condition.

Recommended Action Make sure that the room temperature is not too high and that airflow to the card is not blocked. If this condition persists, the environmental monitor might shut down the system. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical representative, and provide the representative with the gathered information.

Error Message

%Regen_MAINBOARD_ASYNC_PQUICC-3-NOMEMORY: No memory for [chars] of unit [dec]

Explanation The router does not have enough memory to perform the function.

Recommended Action Consider adding shared memory. Copy the error message exactly as it appears, and report it to your Cisco technical support representative.

Error Message

%RM-3-BADACCT: Unknown Accounting type ([dec]), flag ([dec])

Explanation An invalid accounting type or flag was detected.

Error Message

%RM-3-BADCALL: Unexpected Call on [chars], Current state is [dec]

Explanation A call came in on a line where an active call may still exist.

Error Message

%RM-3-BADRG: Bad state rg [chars]: [dec]

Explanation An internal software error occurred.

Error Message

%RM-3-BOUNDARY: Memory boundary violation

Explanation An internal software error occurred.

Error Message

%RM-3-NORESP: No response-code from local RM

Explanation An internal software error occurred.

Error Message

%RM-3-OUTOFBUFFS: Out of buffers in RM event buffer queue

Explanation An internal software error occurred.

Error Message

%RM-3-RGINFO: [chars]: RG-info conversion failed ([int])

Explanation An internal software error occurred.

Error Message

%RM-3-WAVL: Wavl error

Explanation An internal software error occurred.

Error Message

%RM-3-ZEROVAL: Uninitialized value being used

Explanation An internal software error occurred.

Error Message

%RPA-3-FLEXIBLE: [chars]

Explanation This message type is created for all those messages that have simple ASCII text and do not take any parameter. This message tells what the problem is.

Error Message

%RPA-3-NO_CAS_ENTRY: CAS Entry does not exist for slot: [dec], ctrl:[dec], channel:[dec]

Explanation CAS entry does not exist for the given controller and channel.

Error Message

%RPA-3-UNKNOWN_MSG: Unknown message type [dec] enqueued to RPA CAS Process

Explanation A message type that is not known to RPA CAS process is enqueued to its queue.

Error Message

%RRR_PCALC-2-PCALC_DUP_IP_ADDRESS: [chars] [int] [chars]

Explanation Two nodes have the same stable IP address.

Recommended Action Find the system that has the duplicate IP address and configure a different address.

Error Message

%RRR_PCALC-2-PCALC_DUP_RRR_ID: [chars] [int] [chars]

Explanation Two nodes have the same stable router ID.

Recommended Action Find the system that has the duplicate router ID and configure a different one.

Error Message

%RRR_PCALC-3-PCALC_INIT: [chars]: rrr_pcalc_system_id_size == 0

Explanation An internal inconsistency was detected when an attempt was made to initialize the RRR path calculation system ID before the system_id size was known.

Error Message

%RRR_PCALC-3-PCALC_LSA: [chars] [chars]

Explanation An internal inconsistency was detected when an attempt was made to establish handle received link-state advertisement (LSA) for RRR topology database.

Error Message

%RRR_PCALC-2-PCALC_MEM: [chars] [dec]

Explanation A failure at an attempt to allocate memory was detected.

Error Message

%RRR_PCALC-3-PCALC_PATH: [chars]

Explanation An internal inconsistency was detected when an attempt was made to establish an RRR tunnel using the RRR path calculation subsystem.

Error Message

%RSP-2-BADCACHE: Overrun detected. End of MEMD buffer : 0x[hex] End of datagram : 0x[hex] bufhdr [hex]: [hex] [hex] [hex] [hex] Flushing Processor Cache

Explanation A packet greater than the maximum possible maximum transmission unit (MTU) was processed, or an illegal buffer header data area was found.

Error Message

%RSP-3-INVRTN: Invalid return queue next=[hex], hwidb=[hex], type=[hex] queue_ptr=[hex], bufhdr_offset=[hex], id=[dec], bcast_id=[dec] bufhdr [hex]: [hex] [hex] [hex] [hex]

Explanation A software or hardware error occurred.

Error Message

%RUDP-3-INIT: rudp [dec]: [chars][chars].

Explanation The Reliable User Data Protocol (RUDP) initialization operation fails.

Error Message

%RUDP-4-LINK: rudp [dec]: [chars][chars].

Explanation A warning is given out for a particular Reliable User Data Protocol (RUDP) link.

Recommended Action This is a debug message only. No action is required.

Error Message

%RUDP-4-NOBUF: rudp [dec]: cannot get packet buffer for [chars].

Explanation An Reliable User Data Protocol (RUDP) link cannot allocate a packet buffer.

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

Error Message

%SARMGR-1-ANALYZE1575FAILED: The 1575 device analysis failed

Explanation The SAR Manager failed its initialization.

Error Message

%SARMGR-3-NOTNRPSARMGRDEV: Device reported [hex]

Explanation The protocol control information (PCI) device ID was not correct.

Error Message

%SGCP-2-INTERNAL_CRITICAL: [chars], SGCP_COMPLAIN_IVL

Explanation The SGCP subsystem encountered an internal software error. The error message contains text that can be used to help identify the nature of the problem.

Error Message

%SGCP-3-INTERNAL_ERROR: [chars], SGCP_COMPLAIN_IVL

Explanation The SGCP subsystem encountered an internal software error. The error message contains text that can be used to help identify the nature of the problem.

Error Message

%SGCP-4-INTERNAL_WARNING: [chars], SGCP_COMPLAIN_IVL

Explanation The SGCP subsystem encountered an internal software error. The error message contains text that can be used to help identify the nature of the problem.

Error Message

%SNASW-4-APPN_LOG_0: EXCEPTION -%lu - SNA Switch could not allocate necessary storage [chars]

Explanation The SNA switch could not allocate necessary storage. Some operation may fail. See other logs.

Recommended Action Either decrease the system load by reducing the number of active sessions, for example, or make more storage available to the SNA switch.

Error Message

%SNASW-3-APPN_LOG_1: PROBLEM - %lu - SNA Switch could not allocate necessary storage [chars]

Explanation The SNA switch could not allocate necessary storage. Some operations may fail. See other logs/verbs.

Recommended Action Either decrease the system load by reducing the number of active sessions, for example, or make more storage available to the SNA switch.

Error Message

%SNASW-4-APPN_LOG_2: EXCEPTION - %lu - SNA Switch cryptography call failed, possibly due to missing password [chars]

Explanation A call from the SNA switch to perform a cryptographic operation failed. Session activation will fail, or an active session will end abnormally with the given sense code, or some other action will fail. More information may appear in subsequent logs.

Recommended Action Check following logs for evidence of failed session activation. If this is evident, check MODE, LS, or INTERNAL PU definitions for cryptographic support. Check that any passwords necessary have been defined. If This message occurs intermittently or with sessions already active with the same PLU, SLU, and mode then make more storage available to the SNA switch.

Error Message

%SNASW-3-ASM_LOG_0: PROBLEM - %lu - Received BIND request directed at this node with unrecognized secondary LU name [chars]

Explanation A BIND request directed at this node (that is, either without an RSCV, or at the last hop on the RSCV) was received with an unrecognized secondary LU name. This message usually indicates a configuration error at the primary LU. Session activation will fail with the specified sense code.

Recommended Action Correct primary LU configuration.

Error Message

%SNASW-3-ASM_LOG_11: PROBLEM - %lu - Received BIND request with badly formed secondary LU name [chars]

Explanation A BIND request with badly formed secondary LU name was received. This message may indicate an interoperability problem. Session activation will fail with the specified sense code.

Error Message

%SNASW-3-ASM_LOG_12: PROBLEM - %lu - Received BIND request where network ID of secondary LU does not match local network ID [chars]

Explanation A BIND request in which the network identifier of the secondary LU does not match the local network identifier was received. The session activation will fail with the specified sense code.

Error Message

%SNASW-4-ASM_LOG_15: EXCEPTION - %lu - Insufficient storage to deactivate link [chars]

Explanation There is not enough storage to deactivate a link. The link will not be deactivated.

Recommended Action Either decrease the system load by reducing the number of active sessions, for example, or make more storage available to the SNA switch.

Error Message

%SNASW-4-ASM_LOG_18: EXCEPTION - %lu - Unable to correlate received BIND response [chars]

Explanation A BIND response that could not be correlated was received. This message indicates a normal race condition, caused by a BIND being followed immediately by an UNBIND for the same session. The BIND response is discarded.

Recommended Action No action is required.

Error Message

%SNASW-3-ASM_LOG_19: PROBLEM - %lu - Received BIND using LFSID that is already in use [chars]

Explanation A BIND was received that uses an LFSID that is already in use. This message is usually caused by a race condition (a BIND, UNBIND, BIND sequence all using the same LFSID, in which the second BIND overtakes the UNBIND). Nodes at the current level of Advanced Peer-to-Peer Networking (APPN) contain "LFSID aging" processing to minimize the changes of this race condition, but some older implementations may not support this processing. BIND will be rejected with specified sense code.

Recommended Action If problem is persistent, or occurs frequently, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%SNASW-3-ASM_LOG_22: PROBLEM - %lu - Session control request received with invalid LFSID [chars]

Explanation A session control request was received with an invalid local form session identifier. This message means that the LFSID is not in a range appropriate for the request. This message may indicate an interoperability problem. The request will be rejected with the specified sense code.

Error Message

%SNASW-3-ASM_LOG_24: PROBLEM - %lu - Failed to initialize address space instance [chars]

Explanation There is not sufficient storage to create a local form session identifier routing table for a link station. Link activation will fail.

Recommended Action Either decrease the system load by reducing the number of active sessions, for example, or make more storage available to the SNA switch.

Error Message

%SNASW-4-ASM_LOG_25: EXCEPTION - %lu - Unable to extend local form session identifier routing table [chars]

Explanation The local form session identifier routing table cannot be extended. Session activation will fail with the specified sense code.

Recommended Action Either decrease the system load by reducing the number of active sessions, for example, or make more storage available to the SNA switch.

Error Message

%SNASW-4-ASM_LOG_26: EXCEPTION - %lu - Independent LU session deactivated because LU deleted [chars]

Explanation An independent LU-LU session has been deactivated because the local LU has been deleted.

Recommended Action No action is required.

%SNASW-3-ASM_LOG_27: PROBLEM - %lu - Detected fatal BIND or UNBIND protocol error [chars]

Explanation Detected fatal BIND or UNBIND protocol error. This message may indicate an interoperability problem. Sense codes are as follows: 20110000---BIND pacing window overrun, or PI not set when expected; 20110001---unexpected solicited BIND IPM; 20110002---PI set when not expected; 20110003---pacing response not IPM; 10020000---RU (BIND, UNBIND or BIND IPM) length error; 10010003---BIND IPM format error; 80070000---BIND or RSP (BIND) segment out of sequence, or segmented UNBIND or RSP (UNBIND); 80070002---BIND or RSP (BIND) segments interleaved; 800F0000---LFSID incorrect for SC request; 800F0001---ODAI incorrect link will be deactivated.

Error Message

%SNASW-3-ASM_LOG_28: PROBLEM - %lu - Received BIND IPM on link where adaptive BIND pacing not supported [chars]

Explanation Received BIND IPM on the link where adaptive BIND pacing is not supported. This message may indicate an interoperability problem. BIND IPM will be discarded.

Error Message

%SNASW-4-ASM_LOG_29: EXCEPTION - %lu - Dependent LU session deactivated because LU deleted [chars]

Explanation A dependent LU-LU session has been deactivated because the LU has been deleted.

Recommended Action No action is required.

Error Message

%SNASW-3-ASM_LOG_2: PROBLEM - %lu - Insufficient storage to generate an Alert [chars]

Explanation There is not sufficient storage to generate an alert message to report a BIND segmentation or pacing error. The alert message will not be sent.

Recommended Action Either decrease the system load by reducing the number of active sessions, for example, or make more storage available to the SNA switch.

Error Message

%SNASW-3-ASM_LOG_3: PROBLEM - %lu - Insufficient storage to process received BIND request [chars]

Explanation There is not sufficient storage to process received BIND request. The BIND will be rejected with the specified sense code.

Recommended Action Either decrease the system load by reducing the number of active sessions, for example, or make more storage available to the SNA switch.

Error Message

%SNASW-3-ASM_LOG_4: PROBLEM - %lu - ACTPU, ACTLU, DACTPU or DACTLU received on link on which dependent LUs are not supported [chars]

Explanation ACTPU, ACTLU, DACTPU or DACTLU received over a link on which dependent LUs are not supported. This message may indicate an interoperability problem. The request will be rejected with the specified sense code.

Error Message

%SNASW-3-ASM_LOG_5: PROBLEM - %lu - Branch Network Node received BIND request with badly formed RSCV [chars]

Explanation A Branch Network Node has received a BIND request with a badly formed RSCV. This message may indicate an interoperability problem. Session activation will fail.

Error Message

%SNASW-3-ASM_LOG_6: PROBLEM - %lu - Badly-formed BIND request rejected by SNA Switch [chars]

Explanation The SNA switch received and rejected a badly formed BIND request. This message may indicate an interoperability problem. Session activation will fail.

Error Message

%SNASW-3-BAD_MSG_NAME: Invalid message name specified for snasw msg-trap

Explanation An invalid message name was supplied on a the snasw msg-trap command.

Recommended Action Reissue the command with a valid message name.

Error Message

%SNASW-4-CH2_LOG_0: EXCEPTION - %lu - CRV exchange failed on a PLU-SLU session. The session will fail [chars]

Explanation The call reference value (CRV) exchange failed. This message indicates the cryptography keys configured at this LU and the partner LU are inconsistent. The session will be deactivated with the specified sense code 08350001.

Recommended Action Use information on the session deactivated problem log (log 271) to identify the local LU and the partner LU, and correct the mismatch in cryptography keys.

Error Message

%SNASW-4-CH2_LOG_1: EXCEPTION - %lu - Protocol error during CRV exchange [chars]

Explanation A protocol error occurred during call reference value (CRV) exchange. This message indicates a possible interoperability problem. Sense codes are as follows: 20090000---CRV request received from secondary LU, or CRV response received from primary LU, or CRV not received when expected; 10020000---CRV RU too short; 400F0000---CRV with FI not set; 400B0000---CRV chain indicators not set to BC, EC; 40140000---CRV not RQD1; 40110000---CRV not expedited; 40150000---CRV with QRI not set; 40080000---CRV with PI set; 400C0000---CRV request with BBI, EBI or CEBI set; 400D0000---CRV request with CDI set; 40100000---CRV request with CSI set to CODE1; 40160000---CRV request with EDI set; 40170000---CRV request with PDI set; 40130000---CRV response RTI and SDI inconsistent. The session will be deactivated with specified sense code.

Recommended Action Use the information on the session deactivated problem log 271 to identify the local LU and the partner LU. Run a trace on the specified link station, and contact a Cisco technical support representative with the log and trace.

Error Message

%SNASW-4-CH2_LOG_2: EXCEPTION - %lu - Insufficient storage to initialize half session [chars]

Explanation There is not sufficient storage to initialize the half session. The half session will fail to activate with the specified sense code.

Recommended Action Either decrease the system load by reducing the number of active sessions, or make more storage available to the SNA switch.

Error Message

%SNASW-4-CH_LOG_0: EXCEPTION - %lu - LU type 0, 1, 2 or 3 format error [chars]

Explanation The LU type 0,1,2 or 3 format error occurred. This message may indicate an interoperability problem. The PIU containing the error was discarded.

Error Message

%SNASW-4-CH_LOG_1: EXCEPTION - %lu - LU type 0, 1, 2 or 3 session ended abnormally because of insufficient storage [chars]

Explanation The LU type 0, 1, 2, or 3 session ended abnormally because of insufficient storage. The session will be deactivated with the specified sense code.

Recommended Action Either decrease the system load by reducing the number of active sessions, for example, or make more storage available to the SNA switch.

Error Message

%SNASW-4-CH_LOG_2: EXCEPTION - %lu - LU type 0, 1, 2 or 3 session ended abnormally while receiving data [chars]

Explanation The LU type 0, 1, 2, or 3 session ended abnormally while receiving data. The session will be deactivated with the specified sense code.

Error Message

%SNASW-4-CH_LOG_3: EXCEPTION - %lu - LU type 0, 1, 2 or 3 session ended abnormally because of invalid application data [chars]

Explanation The LU type 0, 1, 2, or 3 session ended abnormally because of invalid data received from the application. The session will be deactivated with the specified sense code.

Error Message

%SNASW-4-CH_LOG_4: EXCEPTION - %lu - Application sent invalid Data message [chars]

Explanation The LU type 0, 1, 2, or 3 application sent invalid data message. Status Acknowledge (NACK-2) was sent to the application.

Error Message

%SNASW-4-CH_LOG_5: EXCEPTION - %lu - Application sent invalid Status Control message [chars]

Explanation The LU type 0, 1, 2, or 3 application sent an invalid Status Control message. Status Control (NACK-2) was sent to the application.

Error Message

%SNASW-4-CH_LOG_6: EXCEPTION - %lu - Application sent invalid Acknowledgment or Status message [chars]

Explanation The LU type 0, 1, 2, or 3 application sent an invalid Acknowledgment or Status message. Status Error sent to the application.

Error Message

%SNASW-4-CH_LOG_8: EXCEPTION - %lu - Insufficient storage to report RTM statistics to Host [chars]

Explanation There was not sufficient storage to report RTM statistics to the host. The RTM statistics displayed by host will be inconsistent.

Recommended Action Either decrease the system load by reducing the number of active sessions, for example, or make more storage available to the SNA switch.

Error Message

%SNASW-4-CH_LOG_9: EXCEPTION - %lu - Insufficient storage to report RTM status to application [chars]

Explanation Therewas not sufficient storage to report RTM status to the application. RTM statistics reported and displayed by application may be inconsistent.

Recommended Action Either decrease the system load by reducing the number of active sessions, for example, or make more storage available to the SNA switch.

Error Message

%SNASW-3-CLSIBadPrimitive: CLSI bad primitive type, header= [chars]

Explanation An internal software error occurred.

Error Message

%SNASW-3-CLSIBadReturnCode: CLSI bad return code: [dec], header= [chars]

Explanation An internal software error occurred.

Error Message

%SNASW-3-CLSIFailure: SNASW failed to process CLSI message, header= [chars]

Explanation An internal software error occurred.

Error Message

%SNASW-6-CS2_LOG_0: INFO - %lu - Implicit link limit on port reached [chars]

Explanation An implicit, dynamic, or discovery link could not be activated because the implicit link limit defined on the port was reached or exceeded. The link type being activated is: 1 (dynamic); 3 (implicit); 4 (discovery)

Recommended Action No action is required.

%SNASW-4-CS2_LOG_10: EXCEPTION - %lu - Link activation retry limit reached [chars]

Explanation An automatic retry link station is still inactive after the maximum allowed number of retries. The link station will remain inactive awaiting operator intervention. In the meantime, the activation of any sessions relying on this link station will fail.

Recommended Action Check surrounding logs for link activation failures. Check the configuration of the link station. Check the state of the adjacent node. Enter the snasw start link command to retry activation.

Error Message

%SNASW-4-CS2_LOG_11: EXCEPTION - %lu - A request to activate a connection network TG was rejected because the local and destination link addresses were incompatible [chars]

Explanation The SNA switch cannot start a link to an adjacent node over a connection network TG because the link address on the local node is not compatible with the link address on the adjacent node. The session will fail, with the specified sense code.

Recommended Action Check the local and destination link addresses.

Error Message

%SNASW-4-CS2_LOG_12: EXCEPTION - %lu - A request to activate a connection network TG was rejected because a defined link was already active between the local and destination address and multiple links are not supported [chars]

Explanation The SNA switch cannot start a link to an adjacent node over a connection network TG because the DLC does not support multiple links between the local and destination addresses. The session will fail, with the specified sense code.

Recommended Action Check the local and destination link addresses.

Error Message

%SNASW-4-CS2_LOG_25: EXCEPTION - %lu - Insufficient resources to (un)register adjacent LEN [chars]

Explanation The Branch Network node has insufficient resources to de-register an adjacent LEN node. The directory of this node or that of its NNS may become inconsistent, in that the LEN CP will still be present when it should not be, or vice versa. Thus session activation to the LEN node may fail when a link to it is active, or neighboring nodes may believe the LEN node to be contactable when the link to is down.

Recommended Action Ensure sufficient resources are available to SNA switch and then recycle the link to the required state.

Error Message

%SNASW-4-CS2_LOG_26: EXCEPTION - %lu - Invalid TG descriptor received from DLUS [chars]

Explanation An invalid TG descriptor was received from a Dependent LU Server (DLUS). The PU will not be activated.

Recommended Action Check the configuration of the Dependent LU Server (DLUS) named by this log. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%SNASW-4-CS2_LOG_27: EXCEPTION - %lu - A DLUS-defined downstream DLUR-served link could not be defined [chars]

Explanation A Dependent LU Server (DLUS)-defined downstream DLUR-served link could not be defined because of either of the following situations: the specified port does not exist, or there is an existing link station to the same destination address. In either situation the PU will not be activated.

Recommended Action Correct the configuration.

Error Message

%SNASW-4-CS2_LOG_28: EXCEPTION - %lu - A DLUS-defined downstream DLUR-served link failed to activate [chars]

Explanation A Dependent LU Server (DLUS)-defined downstream link failed to activate. The PU will not be activated.

Recommended Action Check that the named port is active. Check that the downstream node at the given address is powered up. Check surrounding logs for reasons that the named LS has not activated. Check the configuration of the Dependent LU Server (DLUS).

Error Message

%SNASW-4-CS2_LOG_29: EXCEPTION - %lu - DLUS-defined DSPU name clashes with locally-defined DSPU name [chars]

Explanation A Dependent LU Server(DLUS)-defined downstream physical unit (DSPU) name is identical to the locally defined DSPU name of a different PU. An implicit link will fail. The ACTPU for the DSPU connected over this link will be rejected.

Recommended Action Reconfigure this node, or the Dependent LU Server (DLUS), to remove the duplication in the use of this PU name. If the DLUS and the DLUR use the same PU name, then they must apply this name to the same PU.

Error Message

%SNASW-4-CS2_LOG_2: EXCEPTION - %lu - Link activation race detected - local node responsible for disconnect [chars]

Explanation A link activation race was detected on an ATM port. The local node is responsible for resolving this race. The local node will disconnect its link. The link activation request of the remote node will succeed.

Recommended Action This message indicates a normal race condition. No action is required.

Error Message

%SNASW-4-CS2_LOG_30: EXCEPTION - %lu - Insufficient information to create a DLUS-defined link to a DLUR DSPU [chars]

Explanation There is not sufficient information to create a Dependent LU Server (DLUS)-defined link. A PU will not be activated. The ACTPU for the named PU will be rejected with the given sense code.

Recommended Action Correct the PU definition at the Dependent LU Server (DLUS). The DLUS-defined link could not be created using the information from the DLUS in the TG descriptor (CV x'46'). For example, for a Token Ring link to be created, the SNA switch requires the x'46' to contain the following subfields: - x'91' Signalling information CV specifying EBCDIC 'TR'; - x'92' Port identifier containing an 8-byte EBCDIC port name; - x'93' LSAP info containing a 1-byte destination SAP address; - x'94' MAC info containing a 6-byte destination MAC address.

Error Message

%SNASW-4-CS2_LOG_3: EXCEPTION - %lu - Link activation race detected - adjacent node responsible for disconnect [chars]

Explanation A link activation race was detected on an ATM port. The remote node is responsible for resolving this race. The local node will send a negotiation error CV indicating that the remote link activation request should fail. The activation request of the local node link will succeed.

Recommended Action This message indicates a normal race condition. No action is required.

Error Message

%SNASW-4-CS2_LOG_4: EXCEPTION - %lu - PORT_BANDWIDTH_UPDATE (status = QUIESCING) received [chars]

Explanation A PORT_BANDWIDTH_UPDATE signal (status = QUIESCING) was received. Any Connection Network TGs on this port will be advertised as quiescing. Any automatically activated TGs will be advertised as nonoperational.

Recommended Action If possible, increase the bandwidth available to the local port.

Error Message

%SNASW-4-CS2_LOG_5: EXCEPTION - %lu - PORT_BANDWIDTH_UPDATE (status = OK) received [chars]

Explanation A PORT_BANDWIDTH_UPDATE signal (status = OK) was received. Any Connection Network TGs on this port which had been advertised as quiescing will be advertised as active. Any automatically activated TGs that had been advertised as nonoperational will be advertised as operational.

Recommended Action To avoid future bandwidth shortage problems, increase the bandwidth available to the local port.

Error Message

%SNASW-3-CS2_LOG_9: PROBLEM - %lu - DLC failure during creation [chars]

Explanation The data-link connection (DLC) has returned inconsistent data during creation. The DLC will be destroyed, and all ports and link stations defined on the DLC will be inoperative.

Recommended Action Run a trace on the data-link connection (DLC) and provide a Cisco technical support representative with the log and trace information.

Error Message

%SNASW-3-CS_LOG_0: PROBLEM - %lu - An active link station has failed [chars]

Explanation An active link station failed. The link and any sessions using it will be deactivated. Attempt to restart the link. If the problem persists, inspect the log for problems or exceptions logged by the data-link connection (DLC) that give more specific reasons for the failure, and follow the actions specified by those logs. Otherwise, run a trace on the specified port or link station to find the reason for the failure.

Error Message

%SNASW-3-CS_LOG_10: PROBLEM - %lu - Link to host not configured [chars]

Explanation An unexpected SET_MODE, for example, received before exchange identification (XID) exchange had completed, was received from an adjacent host and no link was configured to that host. An implicit link cannot be activated because no local PU was defined to use the link. The inbound link activation will fail.

Recommended Action Define a link station by entering the snasw link command with adj_cp_type set to NAP_HOST_XID3 or NAP_HOST_XID0.

Error Message

%SNASW-3-CS_LOG_11: PROBLEM - %lu - Parallel TGs not supported to this adjacent node [chars]

Explanation An attempt was made to activate more than one TG to an adjacent node that does not support parallel TGs. Link activation will fail.

Recommended Action Modify the configuration so that only one link station is defined to the specified adjacent node. Alternatively, several links to the adjacent node can be defined, but only one can be active concurrently.

Error Message

%SNASW-4-CS_LOG_12: EXCEPTION - %lu - Insufficient storage to perform orderly link deactivation (link deactivated immediate instead) [chars]

Explanation There is not sufficient storage to perform an orderly link deactivation, therefore an immediate deactivation will occur instead.

Recommended Action Either decrease the system load by reducing the number of active sessions, for example, or make more storage available to the SNA switch.

Error Message

%SNASW-3-CS_LOG_13: PROBLEM - %lu - Conflicting requirements for error recovery, link is not HPR-capable [chars]

Explanation There are conflicting requirements for error recovery between the local node and a partner node when an attempt is made to activate a link that is HPR-capable.

Recommended Action In order to allow HPR protocols to be used on the link, the local and partner nodes must be able to accommodate error recovery requirements from one another. At the minimum this will require reconfiguration but may not always be possible.

Error Message

%SNASW-4-CS_LOG_14: EXCEPTION - %lu - Insufficient storage to update ANR routing tables following deactivation of an HPR-capable link [chars]

Explanation There is not sufficient storage to update the ANR routing tables following the deactivation of an HPR-capable link. The node may not be able to free resources that are no longer required but will otherwise operate normally.

Recommended Action Either decrease the system load by reducing the number of active sessions, for example, or make more storage available to the SNA switch.

Error Message

%SNASW-4-CS_LOG_15: EXCEPTION - %lu - Insufficient storage to update ANR routing tables following activation of an HPR-capable link [chars]

Explanation There is not sufficient storage to update the ANR routing tables following activation of an HPR-capable link. The HPR traffic using this ANR label will not be routed correctly, and therefore may cause the RTP connections to path-switch, or fail altogether.

Recommended Action Either decrease the system load by reducing the number of active sessions, for example, or make more storage available to the SNA switch.

Error Message

%SNASW-3-CS_LOG_17: PROBLEM - %lu - DLC failed [chars]

Explanation A data-link connection (DLC) has ended abnormally. All ports and link stations defined on the DLC will be inoperative.

Recommended Action Restart the data-link connection (DLC) using the snasw start port command. If the problem persists, look for DLC-specific logs giving more information on the reason for the failure.

Error Message

%SNASW-4-CS_LOG_19: EXCEPTION - %lu - Insufficient storage to forward Alert generated by DLC [chars]

Explanation There is insufficient storage to forward the Alert generated by the data-link connection (DLC). The Alert will be discarded.

Recommended Action Either decrease the system load by reducing the number of active sessions, for example, or make more storage available to the SNA switch.

Error Message

%SNASW-3-CS_LOG_1: PROBLEM - %lu - XID exchange count exceeds activation limit [chars]

Explanation The number of exchange identifications (XIDs) received during link activation exceeded the limit defined for the port. This message could indicate an XID protocol error, or an excessively unreliable physical medium. The sense data gives more information about the error: 083E0001---the limit was exceeded while exchanging prenegotiation or negotiation XIDs; 0809003A---the limit was exceeded while exchanging NULL XIDs. The link activation will fail.

Recommended Action Retry the activation. If the SNA switch is still unable to activate the link station, run a trace on the link station or port to diagnose the problem.

Error Message

%SNASW-3-CS_LOG_22: PROBLEM - %lu - Unable to deactivate port [chars]

Explanation It is not possible to deactivate the port. The snasw stop port command will fail, and the port may not restart successfully.

Recommended Action If required, attempt to restart the port. If this method fails, look for data-link connection (DLC)-specific logs giving more information on the reason for the failure.

Error Message

%SNASW-3-CS_LOG_24: PROBLEM - %lu - Unrecoverable DLC failure [chars]

Explanation An unrecoverable data-link connection (DLC) failure occurred. The DLC will be destroyed, and all ports and link stations defined on the DLC will be inoperative.

Recommended Action Restart the data-link connection (DLC) and ports by entering the snasw start port command. If these operations fail, or this problem persists, run a trace on the DLC. Provide a Cisco technical support representative with the log and trace information.

Error Message

%SNASW-4-CS_LOG_25: EXCEPTION - %lu - Link not configured for automatic activation or last stopped non-automatically [chars]

Explanation A session or application required the SNA switch to automatically activate a link station, but the link station was not configured to be automatically activated or was last stopped manually. The session or application will fail, with the specified sense code.

Recommended Action Either manually activate the link by entering the snasw start link command, or redefine the link to support automatic activation by entering the snasw link command.

Error Message

%SNASW-4-CS_LOG_26: EXCEPTION - %lu - Unable to activate link station because owning port is not active [chars]

Explanation A session or application required the SNA switch to automatically activate a link station, but the request failed because the owning port was not active. This message usually indicates an inconsistent network topology, which may be transient, that is, caused by a normal race condition, or permanent, as indicated by logs 127 or 128. The session or application will fail, with the specified sense code.

Recommended Action If possible, increase the port link-activation limits. Otherwise, check the consistency of the network topology.

Error Message

%SNASW-4-CS_LOG_27: EXCEPTION - %lu - Unable to find requested link [chars]

Explanation A session required the SNA switch to automatically activate a link station, but the SNA switch was unable to identify the requested link. This message usually indicates an inconsistent network topology, which may be transient, that is, caused by a normal race condition, or permanent, as indicated by logs 127 or 128. The session will fail, with the specified sense code.

Recommended Action Check the consistency of the network topology.

Error Message

%SNASW-4-CS_LOG_28: EXCEPTION - %lu - Unable to activate dynamic link station because owning port is not active [chars]

Explanation A session required the SNA switch to automatically activate a dynamic link station, but the request was failed because the owning port was not active. This message usually indicates an inconsistent network topology, which may be transient, that is, caused by a normal race condition, or permanent, as indicated by logs 127 or 128. The session will fail, with the specified sense code.

Recommended Action If possible, increase the port activation limits. Otherwise, check the consistency of the network topology.

Error Message

%SNASW-4-CS_LOG_29: EXCEPTION - %lu - Unable to find requested connection network [chars]

Explanation A session required the SNA switch to automatically activate a dynamic link station, but the SNA switch was unable to identify the requested connection network. This message usually indicates an inconsistent network topology, which may be transient, that is, caused by a normal race condition, or permanent, as indicated by logs 127 or 128. The session will fail, with the specified sense code.

Recommended Action Check the consistency of the network topology.

Error Message

%SNASW-3-CS_LOG_2: PROBLEM - %lu - XID exchange count exceeds nonactivation limit [chars]

Explanation The number of exchange identifications (XIDs) received during a nonactivation exchange exceeded the limit defined for the port. This message could indicate an XID protocol error, or an excessively unreliable physical media. The nonactivation XID exchange will fail and the link will be deactivated.

Recommended Action Run a trace on the link station or port to diagnose the problem. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

%SNASW-3-CS_LOG_30: PROBLEM - %lu - Incoming call rejected because port link-activation limits exceeded [chars]

Explanation An incoming call was rejected because the port link-activation limits would be exceeded. The link activation will fail.

Recommended Action If possible, increase the port link-activation limits.

Error Message

%SNASW-3-CS_LOG_31: PROBLEM - %lu - The CP name on an XID3 received from adjacent node is different to that expected [chars]

Explanation The CP name on an XID3 received from an adjacent node is different from what was expected. The link activation will fail.

Recommended Action If the received adjacent CP name is correct, correct the link station configuration by entering the snasw link command. Depending on other aspects of the link station definition, the CP name check can be disabled by entering the snasw link command with the adj_cp_name field set to all zeros.

Error Message

%SNASW-3-CS_LOG_32: PROBLEM - %lu - The node ID on an XID3 received from a back-level node is different to that expected [chars]

Explanation The node ID on an XID3 received from a back level node is different from what expected. The link activation will fail.

Recommended Action If the received node ID is correct, the link station configuration by entering the snasw link command. Depending on other aspects of the link station definition, the node ID check can be disabled by entering the snasw link command with the adj_node_id field set to all zeros.

Error Message

%SNASW-3-CS_LOG_33: PROBLEM - %lu - The node type indicated on an XID3 received from an adjacent node is different to that expected [chars]

Explanation The node type indicated on an XID3 received from an adjacent node is different from what expected. The link activation will fail.

Recommended Action If the received node type is correct, the link station configuration by entering the snasw link command. Depending on other aspects of the link station definition, the node type check can be disabled by entering the snasw link command with the adj_node_type field set to NAP_LEARN_NODE.

Error Message

%SNASW-3-CS_LOG_34: PROBLEM - %lu - Both sent and received XIDs indicate the same, non-negotiable, link station role [chars]

Explanation Both the sent and the received XIDs indicate the same nonnegotiable link station role. The link activation will fail.

Recommended Action Either correct the local port definition, or the remote definition, so that the link station roles are complementary, or at least one link station is negotiable.

Error Message

%SNASW-4-CS_LOG_35: EXCEPTION - %lu - Unable to activate link station because port total link-activation limit reached [chars]

Explanation A session or application required the SNA switch to automatically activate a link station, but the request failed because it would have exceeded the port total link-activation limit. This message usually indicates an inconsistent network topology, which may be transient, that is, caused by a normal race condition, or permanent, as indicated by logs 127 or 128. The session or application will fail, with the specified sense code.

Recommended Action Check the consistency of the network topology.

Error Message

%SNASW-4-CS_LOG_36: EXCEPTION - %lu - Unable to activate link station because port outbound link-activation limit reached [chars]

Explanation A session or application required the SNA switch to automatically activate a link station, but the request was failed because it would have exceeded the maximum number of concurrently active outbound links allowed for the owning port. This number is the total link-activation limit minus the inbound link-activation limit---that part of the total limit reserved for active inbound links. This message usually indicates an inconsistent network topology, which may be transient, that is, caused by a normal race condition, or permanent, as indicated by logs 127 or 128. The session or application will fail with the specified sense code.

Recommended Action Check the consistency of the network topology.

Error Message

%SNASW-4-CS_LOG_37: EXCEPTION - %lu - Unable to activate dynamic link station because port total link-activation limit reached [chars]

Explanation A session required the SNA switch to automatically activate a dynamic link station, but the request was failed because it would have exceeded the port total link-activation limit. This message usually indicates an inconsistent network topology, which may be transient, that is, caused by a normal race condition, or permanent, as indicated by logs 127 or 128. The session or application will fail with the specified sense code.

Recommended Action Check the consistency of the network topology.

Error Message

%SNASW-4-CS_LOG_38: EXCEPTION - %lu - Unable to activate dynamic link station because port outbound link-activation limit reached [chars]

Explanation A session required the SNA switch to automatically activate a dynamic link station, but the request failed because it would have exceeded the maximum number of concurrently active outbound links allowed for the owning port. This number is the total link-activation limit minus the inbound link-activation limit---that part of the total limit reserved for active inbound links. This message usually indicates an inconsistent network topology, which may be transient, that is, caused by a normal race condition, or permanent, as indicated by logs 127 or 128. The session or application will fail with the specified sense code.

Recommended Action Check the consistency of the network topology.

Error Message

%SNASW-6-CS_LOG_39: INFO - %lu - Link station to host started [chars]

Explanation A non-Advanced Peer-to-Peer Networking (APPN) link station to an upstream host has been successfully started.

Recommended Action No action is required.

Error Message

%SNASW-3-CS_LOG_3: PROBLEM - %lu - Insufficient storage to activate link [chars]

Explanation There is insufficient storage to activate the link. The link activation will fail.

Recommended Action Either decrease the system load by reducing the number of active sessions, for example, or make more storage available to the SNA switch.

Error Message

%SNASW-6-CS_LOG_40: INFO - %lu - Link station to DSPU started [chars]

Explanation A non-Advanced Peer-to-Peer Networking (APPN) link station to a downstream PU was successfully started.

Recommended Action No action is required.

Error Message

%SNASW-6-CS_LOG_41: INFO - %lu - Link station to host stopped [chars]

Explanation A non-Advanced Peer-to-Peer Networking (APPN) link station to an upstream host was successfully stopped.

Recommended Action No action is required.

Error Message

%SNASW-6-CS_LOG_42: INFO - %lu - Link station to DSPU stopped [chars]

Explanation A non-Advanced Peer-to-Peer Networking (APPN) link station to a downstream PU was successfully stopped.

Recommended Action No action is required.

Error Message

%SNASW-4-CS_LOG_43: EXCEPTION - %lu - Unable to find requested link [chars]

Explanation A locally initiated dependent session activation request required the SNA switch to automatically activate a link to a specified PU name, but the SNA switch was unable to identify the link to the PU. This message indicates an inconsistent local configuration that is transient and is caused by a recent modification. The session activation request will fail with the specified sense code.

Recommended Action Check the consistency of the local configuration. Enter the show snasw link command to view the link definitions.

Error Message

%SNASW-6-CS_LOG_44: INFO - %lu - SNA Switch link started [chars]

Explanation An SNA switch link was successfully started.

Recommended Action No action is required.

Error Message

%SNASW-3-CS_LOG_4: PROBLEM - %lu - Link to back-level LEN node not configured [chars]

Explanation An XID3 from an adjacent back level low-entry networking (LEN) node that is not carrying a network name control vector was received and no link was configured to that back-level LEN node. An implicit link cannot be activated because the CP name of the adjacent node is not known. The inbound link activation will fail.

Recommended Action Define a link station by entering the snasw link command with adj_cp_type set to NAP_BACK_LEVEL_LEN_NODE.

Error Message

%SNASW-3-CS_LOG_51: PROBLEM - %lu - Intra-node session support ended abnormally [chars]

Explanation The intranode session support ended abnormally. This error should only occur because of a shortage of available storage. Any active intranode sessions will fail, and you will not be able to activate any more intranode sessions.

Recommended Action Either decrease the system load by reducing the number of active sessions, for example, or make more storage available to the SNA switch.

Error Message

%SNASW-4-CS_LOG_52: EXCEPTION - %lu - Unable to find requested connection network [chars]

Explanation A session required the SNA switch to automatically activate a dynamic link station, but the SNA switch was unable to identify the requested connection network TG. This message usually indicates an inconsistent network topology, which may be transient, that is, caused by a normal race condition, or permanent, as indicated by logs 127 or 128. The session will fail with the specified sense code.

Recommended Action Check the consistency of the network topology.

Error Message

%SNASW-3-CS_LOG_54: PROBLEM - %lu - Insufficient storage to generate link Alert [chars]

Explanation There was insufficient storage to generate a link Alert. The Alert will not be sent.

Recommended Action Either decrease the system load by reducing the number of active sessions, for example, or make more storage available to the SNA switch.

Error Message

%SNASW-6-CS_LOG_55: INFO - %lu - HPR-capable SNA Switch link started [chars]

Explanation An SNA switch link was successfully started on a node that supports HPR.

Recommended Action No action is required.

Error Message

%SNASW-6-CS_LOG_56: INFO - %lu - SNA switch link stopped [chars]

Explanation An SNA switch link was successfully stopped.

Recommended Action No action is required.

Error Message

%SNASW-6-CS_LOG_57: INFO - %lu - DLC started [chars]

Explanation A data-link connection (DLC) was successfully started.

Recommended Action No action is required.

Error Message

%SNASW-6-CS_LOG_58: INFO - %lu - DLC stopped [chars]

Explanation A data-link connection (DLC) was successfully stopped.

Recommended Action No action is required.

Error Message

%SNASW-6-CS_LOG_59: INFO - %lu - Port started [chars]

Explanation A port was successfully started.

Recommended Action No action is required.

Error Message

%SNASW-3-CS_LOG_5: PROBLEM - %lu - Link to host not configured correctly (host is not a Type 2.1 node) [chars]

Explanation The link to the host was configured correctly as a link to a Type 2.1 node. The link activation will fail.

Recommended Action Redefine the link station by entering the snasw link command with adj_cp_type set to NAP_HOST_XID3 or NAP_HOST_XID0.

Error Message

%SNASW-6-CS_LOG_60: INFO - %lu - Port stopped [chars]

Explanation A port was successfully stopped.

Recommended Action No action is required.

Error Message

%SNASW-4-CS_LOG_61: EXCEPTION - %lu - Unable to start requested CP-CP sessions with adjacent node [chars]

Explanation The specified link is configured to support CP-CP sessions, but these sessions could not be started. This error has occurred either because the remote node is not configured to support CP-CP sessions on this link, or because both the local and remote nodes are end nodes, and therefore the CP-CP sessions are not allowed to be started. CP-CP sessions will not be established.

Recommended Action Correct the configuration mismatch, either by removing CP-CP session support from the local connection definition, or by adding it to the connection definition of the adjacent node.

Error Message

%SNASW-3-CS_LOG_62: PROBLEM - %lu - Failed to create DLC [chars]

Explanation A data-link connection (DLC) could not be started either because of insufficient resources or because the specified DLC type is not supported. The DLC is inoperative.

Recommended Action If the data-link connection (DLC) type is supported, either decrease the system load by reducing the number of active sessions, for example, or make more storage available to the SNA switch.

Error Message

%SNASW-3-CS_LOG_63: PROBLEM - %lu - Pre-defined TG number does not match that sent by adjacent node [chars]

Explanation The specified link station is configured with a predefined TG number but the adjacent node sent a different nonzero TG number. Link activation will fail.

Recommended Action Correct the mismatched TG number configuration by entering the snasw link command at this node or at an adjacent node.

Error Message

%SNASW-3-CS_LOG_64: PROBLEM - %lu - Adjacent node sent a TG number that was pre-assigned to another LS [chars]

Explanation An adjacent node attempted to use a TG number for this link that is already predefined on another link station. Link activation will fail.

Recommended Action Correct the mismatched TG number configuration by entering the snasw link command at this node or at adjacent node.

Error Message

%SNASW-3-CS_LOG_65: PROBLEM - %lu - Adjacent node sent a TG number that was already in use by another LS [chars]

Explanation An adjacent node attempted to use a TG number for this link that is already in use by another link station. This message may indicate an interoperability problem. Link activation will fail.

Recommended Action Run a trace on the link station or port to get more diagnostic information on the problem, and provide a Cisco technical support representative with the log and trace.

Error Message

%SNASW-6-CS_LOG_66: INFO - %lu - Adjacent node has changed its CP name [chars]

Explanation An adjacent node changed its CP name.

Recommended Action No action is required.

Error Message

%SNASW-3-CS_LOG_67: PROBLEM - %lu - Insufficient storage to update topology database with link station [chars]

Explanation There is insufficient storage to update the topology database with the link station information. The topology will be inconsistent, and may result in unexpected session activation failures, typically with sense codes 8014xxxx, 0806002B, or 08500001.

Recommended Action Either decrease the system load by reducing the number of active sessions, for example, or make more storage available to the SNA switch. Cycling the specified link station by either activating then deactivating, or deactivating then activating, may clear the condition.

Error Message

%SNASW-3-CS_LOG_68: PROBLEM - %lu - Insufficient storage to update topology database with connection network [chars]

Error Message

%SNASW-3-CS_LOG_69: PROBLEM - %lu - Insufficient storage to enable intra-node sessions [chars]

Explanation There is insufficient storage to enable intranode sessions. The intranode session cannot be activated.

Recommended Action Either decrease the system load by reducing the number of active sessions, for example, or make more storage available to the SNA switch.

Error Message

%SYS-2-BADPID: Bad pid [dec] for tty %t

Explanation An internal software error occurred.

Recommended Action If this messages recurs, copy it exactly as it appears, and report it to your technical support representative.

Error Message

%SYS-3-BAD_RESET: Questionable reset of process [dec] on tty%t

Explanation A process was reset without giving it a chance to clean itself up.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%SYS-2-CHUNKBADELESIZE: Chunk element size is more than 64k for [chars]

Explanation Chunk manager cannot function properly with big chunk elements.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%SYS-2-CHUNKBADPOOLSIZE: Bad poolsize returned by the system : [int]

Explanation The system returned a nonoptimal pool size. A change in pool size is required.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%SYS-2-CHUNKBOUNDS: Could not find the sibling to allocate memory from. Chunk [chars], total free [dec] inuse [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-2-CHUNKBOUNDSIB: Error noticed in the sibling of the chunk [chars] Chunk index : [dec], Chunk real max : [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-2-CHUNKEXPANDFAIL: Could not expand chunk pool for [chars]. No memory available

Explanation There is not enough processor memory left to grow this chunk pool.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%SYS-2-CHUNKINCONSIS: Inconsistent counters for chunk : [chars] total free [dec]/[dec], total sibs [dec]/[dec], total alloc [dec]/[dec]

Explanation The system returned a nonoptimal pool size. A change in pool size is required.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%SYS-3-DUP_TIMER: Same tty%t in linewatch_timers, type [dec]

Explanation A TTY appeared twice in a timer list where it should have only appeared once.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message

%SYS-2-EXCEPTIONDUMP: System Crashed, Writing Core....

Explanation The system has crashed because of an exception. A core is being generated.

Error Message

%SYS-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 caught 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 no logging console guaranteed command, or turning off link-state messages for some interfaces.

Error Message

%SYS-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.

Error Message

%SYS-3-NOELEMENT: [chars]:Ran out of buffer elements for enqueue

Explanation The process was unable to enqueue data because it ran out of buffer elements.

Recommended Action Copy the error message exactly as it appears and also record the output from the show buffers command, and report it to your technical support representative.

Error Message

%TAC-3-PICKCTX: No pick-context

Explanation The context to pick the next server has disappeared.

Error Message

%TCATM-4-INTERFACE: Request bind interface [chars] same as output interface for [int]%m

Explanation This message appears when it has been determined that the incoming interface of a request bind PIE is the same as the next hop interface for the prefix. This may be due to a transient routing loop during routing protocol convergence or a permanent routing loop due to misconfiguration. As a side effect, the tag VC requests at the upstream neighbor will remain in BindWait state until the situation clears up.

Recommended Action If the situation persists, check the configuration and network paths for the relevant prefix.

Error Message

%TFIB-7-SCANSABORTED: TFIB scan not completing. [chars] [chars]

Explanation The periodic TFIB scan is being repeatedly aborted due to some problem such as an unresolved adjacency.

Recommended Action The system proceeds by letting a TFIB scan complete. Copy the message exactly as it appears, and report it to your technical service representative.

Error Message

%TTY-3-AUTOCONFIG: TTY%t: Modem auto-configuration failed

Explanation Modem auto-configuration failed either because the modem rejected the configuration string or because of a timeout. An attempt should be made to apply the configuration string manually.

Error Message

%TTY-3-NOPROCESS: Cannot create [chars] process

Explanation The process failed to be created.

Error Message

%UBR7200-3-INTERCEPT: Interface [chars], Failed to send intercept packet to server [int]:[dec]

Explanation An internal software error occurred.

Error Message

%UBR7200-5-MAXHOST: New host with IP address [int] and MAC [sci_notation] on SID [dec] is ignored., 2000

Explanation The number of hosts on the SID has been exceeded.

Recommended Action Locate the Cable Modem in question. Call your Cisco technical support representative for assistance.

Error Message

%UBR7200-0-TEMPHIGH: [chars] measured at [chars] is too high: shutdown temperature [chars]

Explanation Current temperature exceeds the maximum shutdown temperature.

Recommended Action Determine cause of the high temperature and correct it if possible. For further assistance, call your Cisco technical support representative.

Error Message

%UBR7200-5-USCONTEND: Interface [chars] Port U[dec], continuous frequency hop ended at [int].%03u MHz

Explanation At least one modem came back online. This message logs the abort of continuous frequency hop.

Recommended Action No action is required.

Error Message

%UBR7200-5-USCONTHOP: Interface [chars] Port U[dec], continuous frequency hop started

Explanation All modems just went offline. This message logs the start of continuous frequency hop.

Recommended Action No action is required.

Error Message

%UBR7200-0-VOLTHIGH: [chars] measured at [chars] is too high: shutdown voltage [chars]

Explanation Current voltage exceeds the maximum shutdown voltage.

Recommended Action Determine the cause of the high voltage and correct it if possible.

Error Message

%UBR7200-0-VOLTLOW: [chars] measured at [chars] is too low: shutdown voltage [chars]

Explanation Current voltage exceeds the minimum shutdown voltage.

Recommended Action Determine the cause of the low voltage and correct it if possible.

Error Message

%VPDN-6-SOFTSHUT: [chars] [chars] [chars] has turned on softshut and rejected [chars] [chars] [chars][chars][chars]

Explanation The NAS/LAC or HGW/LNS can no longer accept a new connection when softshut has been turned on. The existing session will continue until termination.

Recommended Action Call your Cisco technical support representative for assistance.

Error Message

%WCCP-5-CACHEFOUND: Web Cache [int] acquired

Explanation The router has acquired the specified Web cache.

Recommended Action No action is required.

Error Message

%WCCP-1-CACHELOST: Web Cache [int] lost

Explanation The router has lost contact with the specified Web cache.

Recommended Action Verify operation of the specified Web cache.

Error Message

%X25-3-ERR_SUBST_XOT_DNS_DEST: Error substituting regular expression for XOT DNS destination pattern, X25_COMPLAIN_LEVEL

Explanation This message occurs when the regular expression substitute utility fails to arrive at X.25 host name pattern to be sent to Domain Name System (DNS) for an address resolution.

Recommended Action Correct the Domain Name System (DNS) substitution pattern of the X.25 route command.

Error Message

%X25-3-TRUNCATE_ALT_XOT_DNS_DEST: Truncating excess XOT addresses ([dec]) returned by DNS, X25_COMPLAIN_LEVEL

Explanation This message occurs when an X.25 route Domain Name System (DNS) returns more than the six permissible X.25 over TCP (XOT) destination addresses.

Recommended Action Review the Domain Name System (DNS) database entries used for X.25 over TCP (XOT) destination for possible modification.

Error Message

%XCCTSP_VOICE-3-ADDINTRFFAIL: The Voice Telephony Service Provider has rejected our request to add this voice interface ([dec]:[dec])

Explanation The voice software was unable to report a new signalling interface to the voice telephony service provider.

Error Message

%XCCTSP_VOICE-3-MALLOC: No memory is available to build any internal data structure for the voice software

Explanation The voice software was unable to allocate memory to build any internal data structures. The system may be out of memory.

Error Message

%XCCTSP_VOICE-3-NOMEM: No memory is available to build the voice interface ([dec]:[dec])

Explanation The voice software was unable to allocate memory to build a voice interface data structure. The system may be out of memory.

Error Message

%XCCTSP_VOICE-3-NOSDB: No signaling data block is available to build the voice interface([dec]:[dec])

Explanation The voice software was unable to obtain a signalling data block from the voice telephony service provider. The system may be out of memory.

Error Message

%XCCTSP_VOICE-3-NOTDMCHNL: XCCTSP failed to get a free dsp tdm channel from the DSP Resource Manager (DSPRM) to handle an incoming call

Explanation The voice software was unable to obtain the TDM channel for a free DSP from the DSP Resource Manager. All of the DSPs have been used to process calls, or have been taken out of service.

Error Message

%XCCTSP_VOICE-3-NOVOICEVDEV: Cannot find the voice data block which matches an asynchronous response for a call

Explanation This is an internal software fault. Call your field service representative if this message is coincident with dropped calls.

Error Message

%XCCTSP_VOICE-3-UNDEFDSX0: Undefined dsx0 interface for controller([dec])

Explanation This is an internal software fault. The dsx0 interface for the specified controller is not defined. However, the voice software uses it.

Recommended Action Call your field service representative if this message is coincident with dropped calls.

Error Message

%XCCTSP_VOICE-3-UNDEFVOICEINTRF: Invalid voice interface controller:group([dec]:[dec])

Explanation The voice interface defined by the controller group is not yet defined within the voice software, but attempts were made to use this interface.

Recommended Action This is an internal software fault. Call your field service representative if this message is coincident with dropped calls.

Error Message

%XCPA-3-STATUS: bay [[dec]] [chars] (code=[dec])

Explanation The channel port adapter is reporting a condition that has affected the operational status of the card. The message contains the reason reported by the channel port adapter. The port adapter will automatically be restarted.

Recommended Action If the channel port adapter does not automatically restart after detecting an operation status error, enter the microcode reload command. In either case, report this status along with the output from the following commands:

show tech
dir slot 0:
dir slot1:
show log

Table of Contents