System Error Messages for 12.1 T

How to Read System Error Messages

Error Messages

System Error Messages for 12.1 T

This chapter lists and describes the system error messages for Cisco IOS Release 12.1 T, up to and including 12.1(3)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 lists only error messages for Cisco IOS Release 12.1 T that are not documented in the Cisco IOS Release 12.1 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 (e). 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
AAAA	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
AMD79C971	Am79C971 Fast Ethernet device driver
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 signaling 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
C29ATM	Catalyst 2900XL ATM Module
C2KATM	Catalyst 2820 ATM module
C3600	Cisco 3600 platform
C542	Voice driver for modular access routers
C54x	VoIP DSp Driver
C5RSP	Cisco Catalyst 5000 platform
C7200	Cisco 7200 platform
CAIM	Compression Advanced Interface Module
CALL_MGMT	Call management subsystem
CALLPROG	Call Progress Notification Manager subsystem
CALLRECORD	Modem Call Record
CALLTRKR	Call Tracker
CARRIER	Dial Feature Card (DFC) Carrier module
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
CMAPP	Call Manager application
CM622	ATM line card driver
CMCC	Cisco Mainframe Channel Connection interfaces
CM_DSPRM	Digital Signal Processor Resource Manager
CM_MONITOR	UBR900 Cable Access Router Personal Monitor
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
DFC	Dial Feature Card (DFC) carrier platform
DFC_CARRIER	Dial Feature Card (DFC) carrier card
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
DSCC4	DSCC4 driver
DSCCLOCK	Dial shelf controller clock
DSC_ENV	Cisco AS5800 environmental monitor
DSCEXTCLOCK	Dial shelf controller clock
DSC_MODEM	FB modem card
DSCREDCLK	Dial shelf controller redundancy clock
DSC_REDUNDANCY	Cisco AS5800 dial shelf controller redundancy
DSI	Cisco AS5800 dial shelf interconnect board
DS_MODEM	FB modem card
DSPDD	Digital Signal Processor Device Driver
DSPRM	Digital Signal Processor Resource Manager
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
EVENT	Event MIB
EXPRESSION	Expression MIB
FALLBACK	Voice over IP (VoIP) Fallback
FAN	Fan
FB	Cisco AS5800 feature board
FBINFO	Cisco 5800 feature board crash information subsystem
FDDI	Fiber Distributed Data Interface
FECPM	Fast Ethernet Combination Port Module device driver
FIB
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
GPRSMIB	Global Packet Radio Service MIB
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 environmental monitor
GSRIPC	Gigabit Switch Router IPC service routines
GT64010	GT64010 DMA controller driver
GTP	GPRS Tunnel Protocol
HAWKEYE	Token Ring PCI port adapter
HD	HD64570 serial controller
HDV	High Density Voice driver
HDX	HDX FSM
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
IVR	Integrated Voice Response
KINEPAK	Voice over IP for Cisco AS5800
L2R	L2RLY
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
MGCP	Media Gateway Control Protocol
MGCP_APP	Media Gateway Control Protocol application-specific
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
MODEMCALLRECORD	Modem call record
MODEM_HIST	Router shelf modem history/tracing
MODEM_NV	Modem NVRAM
MPA68360	VIP Multi-channel Port Adapter
MPLS_ATM_TRANS	ATM traffice over Multiprotocol Label Switching (MPLS)
MPLS_TE	Label Switch Path Tunnel
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
NP	NextPort driver
NP_BS	NextPort BootStrap
NP_EST	NextPort
NP_MD	NextPort modem driver
NP_MM	NextPort module manager
NP_SPE	NextPort Service Processing Element
NP_SSM	NextPort Session and Service Manager
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
PM_MODEM_HIST	Modem history and tracing
PM_MODEM_MAINT	Modem maintenance
PNNI	Private Network-Network Interface
PORT	Port
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
RADIO	Radio driver
RADIUS	Remote Access Dial-In User Service (RADIUS) facility
RADIX	Radix facility
RAIKO	RAIKO based feature board (FB)
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
RS_TDM	Router shelf time-division multiplexing
RTT	Round trip time monitor
S4T68360	Four-port synchronous serial adapter based on the 68360 processor
SARMGR	Segmentation and reassembly manager
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
SIGSM	Signalling Service Manager
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
SPE	Service Processing Element
SRCP	Simple Resource Coordination Protocol application
SSE	Silicon switching engine
SSH	Secure Shell Protocol
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
TRUNK_CLOCK	AS5400 clocking
TRUNK_DFC	Trunk Fial Feature Card
TSP_TUNNEL	Tag switch path (TSP) tunnel
TTY	TTY (all platforms)
TTYDRIVER	Router shelf asynchronous driver
TUN	Tunnel
UBR900	Cable modem system
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
VPA	Voice Port Adapter
VPDN	Virtual Private Dialup Networking
VPM	Voice port module
VPN	Virtual Private Dialup Network
VTSP
X25	X.25
XCCTSP_VOICE	XCCTSP voice subsystem
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-4-DNISGPUNDEF: Warning: DNIS group [chars] is not defined.

Explanation The Dialed Number Identification Service (DNIS) group was used without having first been defined.

Recommended Action Define the DNIS group before using it.

Error Message

%AAAA-3-DROPACCTLOWMEM: accounting record dropped due to low memory: [chars]-[chars] [chars] [chars], 10*ONESEC

Explanation An accounting record has been dropped because of a low memory condition.

Recommended Action Disable the periodic accounting feature if it is on. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message

%AAAA-3-DROPACCTSNDFAIL: accounting record dropped, send to server failed: [chars]-[chars] [chars] [chars], 10*ONESEC

Explanation An attempt to send an accounting record to the specified server has failed.

Recommended Action Ensure that the TACACS+ or RADIUS server is operational. Next, ensure that the network access server (NAS) is configured properly. Finally, ensure that the NAS can communicate with the server.

Error Message

%ALIGN-3-SPURIOUS: Spurious memory access made at 0x[hex] reading 0x[hex]

Explanation An error was identified and temporarily corrected within a software component of the router.

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

%ALPS-6-CIRCUIT_ASCU_REJECT: Circuit [chars] received a Circuit Open Confirm with a list of rejected ascus

Explanation An Airline Protocol Support (ALPS) circuit has sent a Circuit Open Request message and has received a Circuit Open Confirm reply with a list of rejected agent-sent control units (ASCUs).

Recommended Action No action is required.

Error Message

%AMD79C971_FE-5-FAILED_SUSPEND: Failed to suspend the amd79c971 chip

Explanation The AMD Am79C971 chip could not be suspended.

Error Message

%AMDP2_FE-6-EXCESSCOLL: [chars] TDR=[dec], TRC=[dec], MSGDEF_LIMIT_SLOW

Explanation Ethernet or Fast Ethernet is experiencing multiple collisions. This condition may occur under heavy traffic loads.

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

Error Message

%AMDP2_FE-3-TOOMANYPART: Bad packet with [dec] particles, pak=0x[hex]

Explanation The software has detected an invalid packet.

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

Error Message

%ATM-5-UPDOWN: Changing VC [dec]/[dec] VC-state to [chars]

Explanation The ATM virtual circuit (VC) has been created, removed, activated, or deactivated.

Recommended Action No action is required if the status change was intended; otherwise, the cause of the status change should be researched. To deactivate or activate the VC, use the shut cli command or the no shut cli command.

Error Message

%BGP-3-BGP_INCONSISTENT: [int] Inconsistent [chars], MSGDEF_LIMIT_SLOW

Explanation An inconsistency exists in the specified data structures.

Recommended Action The occurrence of data structure inconsistencies is a rare situation and is a result of an internal problem. Copy the error message exactly as 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

%BGP-3-MARTIAN_IP: [int] Martian prefix [chars] in [chars], MSGDEF_LIMIT_SLOW

Explanation A nonregistered or ill-formed prefix was found in the Border Gateway Protocol (BGP) message. This error indicates that there is some problem involving the remote router.

Recommended Action Inspect the remote router for problems.

Error Message

%CALL_MGMT-4-CALL_DISC: [chars]

Explanation The specific message text is supplied by the Call Management software. This message indicates that a call record is missing from the active call list.

Error Message

%CALLPROG-3-API_INIT: api front init failed for [chars]

Explanation The Call Progress Notification support structures could not be initialized for the indicated Application Programming Interfaces (APIs) because the system does not have sufficient memory.

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

Error Message

%CALLPROG-3-API_USE: no free front-end q elt's; dropping api call info (func=[dec])

Explanation The system has failed to retrieve a free element from the front end queue. The platform requires additional free elements in order to function properly.

Recommended Action Stop using the Call Progress Notification applications. Copy the error message exactly as 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

%CALLRECORD-6-MICA_TERSE_CALL_FAILED_REC: [chars]

Explanation A Terse MICA Call Failed Record has been received.

Recommended Action No action is required.

Error Message

%CALLRECORD-6-MICA_TERSE_CALL_REC: [chars]

Explanation A Terse MICA Call Failed Record has been received.

Recommended Action No action is required.

Error Message

%CALLTRKR-3-CALL_REC_ERROR: [chars]

Explanation A generated record has exceeded the capability of the system log.

Recommended Action No action is required.

Error Message

%CALLTRKR-6-CALL_RECORD: [chars]

Explanation Terse Call Tracker Call Record has been received.

Recommended Action No action is required.

Error Message

%CALLTRKR-6-MODEM_CALL_REC: [chars]

Explanation A Modem Verbose Call Tracker Call Record has been received.

Recommended Action No action is required.

Error Message

%CALLTRKR-6-MODEM_INFO_CALL_REC: [chars]

Explanation A Modem Information Verbose Call Tracker Call Record has been received.

Recommended Action No action is required.

Error Message

%CALLTRKR-6-MODEM_LINE_CALL_REC: [chars]

Explanation A Modem Line Verbose Call Tracker Call Record has been received.

Recommended Action No action is required.

Error Message

%CALLTRKR-6-MODEM_NEG_CALL_REC: [chars]

Explanation A Modem Negotiation Verbose Call Tracker Call Record has been received.

Recommended Action No action is required.

Error Message

%CALLTRKR-3-NO_MEM: Memory allocation failed for CT [chars] ([dec] bytes)

Explanation Call Tracker could not allocate a new record because no memory could be allocated for the task.

Recommended Action Disable Call Tracker by entering the no calltracker enable command. Enter the show memory command to find out where the memory has been allocated.

Error Message

%CALLTRKR-3-PRINT_BUFFER: calltrkr cli print buffer [chars]

Explanation The Call Tracker CLI (command-line interface) internal print buffer has overflowed.

Recommended Action Stop entering calltracker show commands. Copy the error message exactly as 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

%CALLTRKR-3-PROC: can't spawn [chars]

Explanation The Call Tracker process could not be spawned.

Recommended Action Disable Call Tracker by entering the no calltracker enable command. Then reenable it. If the error persists, contact your Cisco technical support representative.

Error Message

%CALLTRKR-3-TBL_INIT: Init of CT's [chars] table failed; CT unusable

Explanation The Call Tracker record table could not be initialized.

Recommended Action Disable Call Tracker by entering the no calltracker enable command. Then reenable it. If the error persists, contact your Cisco technical support representative.

Error Message

%CARRIER-2-CT3_8PRI_MIX: Cannot mix 8PRI and CT3 DFC in chassis, do not power up invalid card in slot [dec]

Explanation The user has placed 8PRI and CT3 Dial Feature Cards (DFCs) in the same chassis. You cannot mix 8PRI and CT3 DFC card types in the same chassis.

Recommended Action Remove the extra 8PRI or CT3 DFC card.

Error Message

%CARRIER-3-DFC_INIT_ALREADY: DFC is already initialized - DFC [dec]

Explanation The Dial Feature Card (DFC) has already been initialized; there is no need to initialize it again.

Error Message

%CARRIER-3-DFC_INIT_FAIL: DFC initialization is failed - DFC [dec]

Explanation The Dial Feature Card (DFC) initialization has failed.

Error Message

%CARRIER-3-DFC_POWER_INT: DFC Power Changed - DFC [dec]

Explanation The Dial Feature Card (DFC) power is fluctuating.

Error Message

%CARRIER-3-INVALID_DFC: Invalid DFC - DFC [dec] type [dec]

Explanation The Dial Feature Card (DFC) has an invalid board ID or type.

Error Message

%CARRIER-3-NO_DFC: DFC is not present - DFC [dec]

Explanation The Dial Feature Card (DFC) is not present in the carrier card.

Error Message

%CARRIER-3-PLATFORM_DFC: DFC Carrier Platform Init Failed - Slot [dec]

Explanation The Dial Feature Card (DFC) carrier platform initialization has failed.

Error Message

%CARRIER-3-POWER_DFC: DFC Power-On Failed - DFC [dec]

Explanation The Dial Feature Card (DFC) power-on has failed.

Error Message

%CARRIER-3-RESET_DFC: DFC Reset Failed - DFC [dec]

Explanation During the online insertion and removal (OIR) process, the Dial Feature Card (DFC) reset failed.

Error Message

%CARRIER-2-THREE_NP108_NOT_PRESENT: 3 NP108s were not found on Tetryl card, [dec] detected.

Explanation Fewer than three NP108s have been found on a tetryl card. A tetryl card requires three NP108s.

Error Message

%CARRIER-2-TOOMANY_8PRI: Too many 8PRI DFC cards, do not power up invalid card in slot [dec]

Explanation The user has placed too many 8PRI Dial Feature Cards (DFCs) in the chassis.

Recommended Action Remove the extra 8PRI DFC cards.

Error Message

%CARRIER-2-TOOMANY_CT3: Too many CT3 DFC cards, do not power up invalid card in slot [dec]

Explanation The user has placed too many CT3 Dial Feature Cards (DFCs) in the chassis.

Recommended Action Remove the extra CT3 DFC cards. If the problem persists, also check the 8PRI DFC cards.

Error Message

%CBUS-4-FIXBADTXVC: Detected and fixed bad tx vc encap on [chars], bad vc [dec], fixed vc [dec], ONEMIN

Explanation A transmit packet on a channelized serial interface does not have a virtual circuit (VC) number encapsulation.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue 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 command output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message

%CBUS-3-TXVCENCAPFAIL: Detected bad tx vc encap on [chars], vc [dec]. Board encap failed [hex], [hex], [hex], ONEMIN

Explanation Board encapsulation has failed on a transmit packet on a channelized serial interface that does not have the required virtual circuit (VC) number encapsulation.

Error Message

%CMAPP-6-PROCESS_CREATION_FAILED: Cannot create Call Manager Application process

Explanation The Call Manager Application process could not be created.

Recommended Action Ensure that there is adequate free memory.

Error Message

%CM_MONITOR-5-DNS_KILL: Terminating DNS process

Explanation A hardware or software error has occurred.

Error Message

%CM_MONITOR-5-DNS_RESP: Sending DNS response to [int] (request was for [int])

Explanation A hardware or software error has occurred.

Error Message

%CM_MONITOR-5-DNS_START: Starting DNS process

Explanation A hardware or software error has occurred.

Error Message

%CRYPTO-3-CERTCHECK: Certificates with invalid status have been detected!!!

Explanation A check of the certificates saved in the memory against the certificate revocation list (CRL) revealed that some certificates were detected as having invalid status.

Recommended Action Check the status, and contact the Certification Authority (CA) administrator. Enrollment may be required.

Error Message

%CRYPTO-6-CERTPENDING: Enter manual authentication ...

Explanation The Certification Authority (CA) server attempted to manually authenticate the router.

Recommended Action Follow a manual authentication procedure.

Error Message

%CRYPTO-3-GETCACERT: Failed to find CA cert in memory.

Explanation The Certification Authority (CA) certificate was not located in memory.

Recommended Action Check the status and contact the CA administrator.

Error Message

%CRYPTO-3-GETCARACERT: Failed to receive RA/CA certificates.

Explanation A failure was encountered when Certification Authority (CA) or Registration Authority (RA) certificates were parsed and processed.

Recommended Action Check the status and contact the CA administrator.

Error Message

%CRYPTO-6-GETCERTINITIAL: Certificate enrollment failed in manual mode

Explanation The current certificate enrollment has failed in manual mode.

Recommended Action Contact the Certification Authority (CA) administrator.

Error Message

%CRYPTO-3-GETCRL: Query the Certificate Revocation List from CA failed

Explanation The attempt to query the Certificate Revocation List from the Certification Authority (CA) server has failed. Several reasons are possible.

Recommended Action Contact the CA administrator.

Error Message

%CRYPTO-3-IKEINIT: [chars]

Explanation An Internet Key Exchange (IKE) initialization error has occurred.

Error Message

%CRYPTO-6-IKE_TED_BAD_REPLY: Received TED reply that did not correspond to a TED probe, MSGDEF_LIMIT_GLACIAL

Explanation The received Tunnel End-Point Discovery (TED) reply does not match the TED probe that is currently outstanding. This error might be a one-time occurrence caused by delay of the TED reply. This error might also be caused by ill-formed packets that were sent by the peer. Ill-formed packets sent by the peer may be a hostile event.

Recommended Action If the problem occurs more than once, contact the administrator of the peer.

Error Message

%CRYPTO-4-IKMP_NO_SA: IKE message from %15i has no SA and is not an initialization offer

Explanation Internet Key Exchange (IKE) maintains state for a communication in the form of security associations. No security association exists for this packet, and it is not an initial offer from the peer to establish one. This situation could denote a denial-of-service attack.

Recommended Action Contact the remote peer and the administrator of the remote peer.

Error Message

%CRYPTO-6-RANDOM: A pseudo-random number was generated twice in succession, 10*ONESEC

Explanation A pseudorandom number generator produced the same number twice in succession.

Recommended Action Under normal circumstances, it is not a problem if a pseudorandom number generator occasionally produces the same number twice in succession. If this message occurs frequently, manually reload the system. If the message is persistent across reloads, copy the error message exactly as it appears, and report it to your Cisco technical support representative.

Error Message

%CRYPTO-0-SELF_TEST_FAILURE: Encryption self-test failed ([chars])

Explanation One of the encryption self-tests has failed. The encryption engine is not operable in this state.

Recommended Action If the failure persists, contact Cisco to obtain a replacement Cisco IOS image.

Error Message

%CRYPTO-3-SOCKETSELECT: Failed to select the socket

Explanation A socket selection has caused a failure.

Recommended Action Check the TCP or socket debugging message.

Error Message

%CTRC-3-NOBUFFS: No buffers available to [chars]

Explanation (Cisco IOS Release 12.1(3)T message) Cisco Transaction Connection (CTRC) failed to allocate a buffer while performing the operation described in the message text. The buffer pool does not contain enough items to fulfill the allocation request. The failed buffer allocation request occurs most commonly when a public buffer pool runs out of elements.

Recommended Action Determine which pool has run out of buffers by entering the show buffers command. Adjust the pool size using the buffers configuration command.

Error Message

%CTRC-3-NOBUFFS: No buffers available to [chars], MSGDEF_LIMIT_FAST

Explanation Cisco Transaction Connection (CTRC) failed to allocate a buffer while performing the operation described in the message text. The buffer pool does not contain enough items to fulfill the allocation request. The failed buffer allocation request occurs most commonly when a public buffer pool runs out of elements.

Recommended Action Determine which pool has run out of buffers by entering the show buffers command. Adjust the pool size using the buffers configuration command.

Error Message

%DFC-1-DFC_BAD_DFC_TYPE: DFC in slot [dec] has incorrect board id of [dec]

Explanation A Dial Feature Card (DFC) board does not have a correct board ID.

Recommended Action Ensure that the board cookie was correctly programmed, or try a new board.

Error Message

%DFC-1-DFC_OLD_HW_REV: DFC in slot [dec] has old hw rev [dec].[dec] when should be [dec].[dec]

Explanation A Dial Feature Card (DFC) board does not have the latest hardware revision. If the hardware version is not the latest, the board must be updated to the version indicated in the error message output.

Error Message

%DFC-1-DFC_OLD_TULUM_VERSION: DFC in slot [dec] has old Tulum version [dec] when should be [dec]

Explanation A Dial Feature Card (DFC) board does not have the latest Tulum version.

Recommended Action Update the Tulum version on the DFC board.

Error Message

%DFC_CARRIER-1-CARRIER_OLD_HW_REV: DFC Carrier in slot [dec] has old hw revision [dec].[dec] when hw revision should be [dec].[dec].

Explanation A Dial Feature Card (DFC) carrier card does not have the latest revision.

Recommended Action If the hardware version is not the latest, update the DFC carrier card with the latest revision as specified in the error message output.

Error Message

%DSCC4-3-ANALYZE_DEVICE_FAILURE: [chars]

Explanation A DSCC4 analyze device has failed.

Error Message

%DSCC4-3-GENERIC: [chars]

Explanation A generic error message has been received.

Error Message

%DSCC4-1-INITFAIL: DSCC4([dec]/[dec]), SCC[dec] init failed

Explanation The software has failed to initialize or restart the SCC of a serial interface.

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

Error Message

%DSCC4-3-INVALID_CLOCKRATE: DSCC4([dec]/[dec]), invalid clock rate (index [dec]) requested

Explanation An internal software error has occurred.

Error Message

%DSCC4-3-NOMEMORY: No memory for [chars] of unit [dec]

Explanation The router does not have enough memory to perform the specified function.

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

Error Message

%DSCC4-3-OWNERR: DSCC4([dec]/[dec]), Buffer ownership error, pak=0x[hex]

Explanation An internal software error has occurred.

Error Message

%DSCC4-3-TOOBIG: DSCC4([dec]/[dec]), packet too big

Explanation A packet greater than the assigned MTU of this serial interface has been queued up for transmission. The system should recover.

Recommended Action 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

%DSCC4-3-TOOSMALL: DSCC4([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. The system should recover.

Error Message

%DSCC4-3-UNKNOWN_SCCS: DSCC4, Incorrect SCC number

Explanation An internal software error has occurred.

Error Message

%DSC_ENV-4-MANUALBOOT: Setting config-register to 0x0 will prevent the feature boards from booting when router shelf is rebooted

Explanation The dial shelf controller cannot be booted manually.

Recommended Action Set the configuration register to 0x2 to enable the automatic boot feature.

Error Message

%DSC_REDUNDANCY-3-TDMSPLITCONFLICT: Tdm Split conflict detected, my tdm [dec], other rs [dec]

Explanation Another router is connected to the dial shelf, and it is claiming ownership of the backplane time slots that this router requires. This problem is probably caused by online insertion and removal (OIR) activity involving the moving of trunk cards from one half of the split to the other.

Recommended Action Resolve the ownership conflict by reloading the router whose time-division multiplexing (TDM) number is greater than the trunk capacity for that router. In some cases it may be necessary to reset both routers.

Error Message

%DS_MODEM-3-BADCB: Unexpected DSIP data callback for modem

Explanation An unexpected software event has occurred.

Error Message

%DS_MODEM-3-FLOWCONTROLACCOUNT: DS-RS flow control has got out of sync, connection has too many particles free. slot:[dec] ttynum:[dec] parts_avail:[dec]

Explanation The flow control accounting on the DS has gotten out of synchronization.

Error Message

%DS_MODEM-3-LOWPARTICLES: Not enough particles - modem number:[dec] particles needed:[dec] available:[dec]; CTS [chars]

Explanation A breakdown of flow control between the RS and the DS has occurred. The RS has sent more particles than are available for this connection.

Error Message

%DS_MODEM-3-NORXPAK: Static receive paktype unavailable

Explanation A software structure was found in an unexpected state during the run-time for the indicated modem.

Error Message

%DS_MODEM-3-OUTPUTDROP: Output drop - modem number:[dec] refunded [dec]; particle count [dec], pool size [dec], queue size [dec]

Explanation The system was temporarily unable to allocate particles for sending traffic to the modem module. This problem indicates a breakdown of flow control between the RS and the DS.

Error Message

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

Explanation The router or access server has detected an internal error.

Error Message

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

Explanation The router or access server has detected an internal error.

Error Message

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

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

Error Message

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

Explanation The Digital Signal Processor (DSP) entered the FAILED state because of alarm indications.

Recommended Action Replace the DSP resource.

Error Message

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

Explanation The Digital Signal Processor (DSP) has failed the background keepalive test.

Recommended Action No action is required.

Error Message

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

Explanation The Digital Signal Processor (DSP) resource has changed state.

Recommended Action No action is required.

Error Message

%DS_TDM-3-ASSERT_FAIL: Slot [dec]: Assertion failed: file `[chars]', line [dec]

Explanation An internal sanity check has failed.

Error Message

%DS_TDM-3-ATTACH_ERR: Slot [dec]: tried but failed to set COMBO_SELECT bit on [chars] FB; cannot attach to backplane

Explanation The time-division multiplexing (TDM) subsystem could not configure the feature board (FB) to attach to the backplane in the manner desired. The FB is defective.

Error Message

%DS_TDM-3-BAD_CONN: Slot [dec]: unrecognized TDM connect message received ([dec]) on [chars] feature board

Explanation An unrecognized time-division multiplexing (TDM) connect message has been received.

Error Message

%DS_TDM-3-BAD_DISCONN: Slot [dec]: unrecognized TDM disconnect message received ([dec]) on [chars] feature board

Explanation An unrecognized time-division multiplexing (TDM) disconnect message has been received.

Error Message

%DS_TDM-3-BAD_DSIP: Slot [dec]: unrecognized DSIP message received ([dec]) on [chars] feature board

Explanation An unrecognized Dial Shelf Interconnect Protocol (DSIP) message has been received.

Error Message

%DS_TDM-3-BAD_MAPPING: Slot [dec]: Legacy FB ([chars]), with static port-to-DS0 mapping, was passed dynamic mapping info

Explanation A software error has caused dynamic port-to-DS0 mapping information to be passed to a statically mapped feature board (FB).

Error Message

%DS_TDM-3-BAD_S4_POWER_UP: Slot [dec]: [chars] powered-up with one or more incorrect default settings ([chars])

Explanation The specified S4 ASIC did not power up with some of the default settings expected by the software; therefore, the time-division multiplexing (TDM) data integrity could have been compromised.

Error Message

%DS_TDM-3-CONN_FAILED: Slot [dec]: handling of sub-msg ([dec]/[int]/[int]/[int]/[int]/[int]) [int] of [int] failed; processing of rest of DSIP msg aborted

Explanation The processing of a submessage encapsulated within a Dial Shelf Interconnect Protocol (DSIP) TDM_CONNECT message has failed. Any remaining submessages in the DSIP message have not been processed.

Error Message

%DS_TDM-3-CONV_CLOSE: Slot [dec]: open MT8986 (addr: [hex]) connection failed - STo[dec], CHo[dec]

Explanation (Cisco IOS Release 12.1(3)T message) An attempt to disable a rate-converted connection has failed.

Error Message

%DS_TDM-3-CONV_CLOSE: Slot [dec]: open MT8986 (addr: 0x[hex]) connection failed - STo[dec], CHo[dec]

Explanation An attempt to disable a rate-converted connection has failed.

Error Message

%DS_TDM-3-CONV_OPEN: Slot [dec]: open MT8986 (addr: 0x[hex]) [chars] connection failed - STi[dec], CHi[dec], STo[dec], CHo[dec]

Explanation An attempt to establish a rate-converted connection has failed.

Error Message

%DS_TDM-3-CONV_OPEN: Slot [dec]: open MT8986 (addr: [hex]) [chars] connection failed - STi[dec], CHi[dec], STo[dec], CHo[dec]

Explanation (Cisco IOS Release 12.1(3)T message) An attempt to establish a rate-converted connection has failed.

Error Message

%DS_TDM-3-DISC_FAILED: Slot [dec]: handling of sub-msg ([dec]/[int]/[int]/[int]/[int]/[int]) [int] of [int] failed; processing of rest of DSIP msg aborted

Error Message

%DS_TDM-3-DISC_FOR_NO_CONN: Slot [dec]: got disc msg for non-existent conn: [chars]-st[int]-ts[int]/gts>[int]><[int]</[chars]-st[int]-ts[int]

Explanation The feature board (FB) has received a request to disconnect an unrecognized connection.

Error Message

%DS_TDM-3-NO_RECOMB_BUS_DS0: Slot [dec]: no free Recombination bus DS0s left; connection not made

Explanation The time-division multiplexing (TDM) Mezzanine card of the Raiko-based feature board (FB) does not have any free recombination bus DS0s.

Error Message

%DS_TDM-3-RECOMB_BUS_TS_BAD_USE: Slot [dec]: convention broken for Mezz's Recomb. bus t'slots: [chars]-st[int]-ts[int]/gts>[int]><[int]</[chars]-st[int]-ts[int]

Explanation The usage convention has been broken for recombination bus time slots. The broken usage convention is a time-division multiplexing (TDM) error.

Error Message

%DS_TDM-3-S4_INT: Slot [dec]: [chars] generated interrupt [chars]

Explanation The S4 ASIC has generated the specified interrupt message.

Error Message

%DS_TDM-3-TDM_CLOSE: Slot [dec]: close MT90820 (addr: [hex]) connection failed - STo[dec], CHo[dec]

Explanation An attempt to disable a digitally switched connection has failed.

Error Message

%DS_TDM-3-TDM_OPEN: Slot [dec]: open MT90820 (addr: [hex]) connection failed - STi[dec], CHi[dec], STo[dec], CHo[dec]

Explanation An attempt to establish a digitally switched connection has failed.

Error Message

%DS_TDM-3-UNEXPECTED_INT: Slot [dec]: got unexpected interrupt from masked-out source '[chars]'

Explanation Although it had been masked out, an interrupt has been received from the specified source.

Error Message

%DS_TDM-3-UNSUPPORTED_MEZZ_VER: Slot [dec]: the detected version ([int]) of Mezzanine card is not supported by this software image

Explanation The software does not support the Mezzanine card that is currently installed on the Raiko card.

Error Message

%DS_TDM-3-VERIFY_DISCONN: Slot [dec]: [chars] failed to veryify disconnect: sto = [dec], ch_out = [dec]

Explanation An attempt to verify a time-division multiplexing (TDM) hardware component has failed.

Error Message

%DS_TDM-3-VERIFY_HILOWMEM: Slot [dec]: [chars] failed to veryify himem, or lowmem: sto = [dec], ch_out = [dec], sti = [dec], ch_in = [dec]

Explanation An attempt to verify a time-division multiplexing (TDM) hardware component has failed.

Error Message

%DS_TDM-3-VERIFY_IMS: Slot [dec]: [chars] failed to veryify IMS: [hex]

Explanation An attempt to verify a time-division multiplexing (TDM) hardware component has failed.

Error Message

%DSX0-5-RBSLINEDBUSYOUT: RBS of slot [dec] controller [dec] timeslot [dec] is dynamic busyout

Explanation Robbed-Bit Signalling (RBS) has been dynamically busied out on the specified time slot and controller.

Recommended Action No action is required.

Error Message

%DSX0-5-RBSLINESBUSYOUT: RBS of slot [dec] controller [dec] timeslot [dec] is static busyout

Explanation Robbed-Bit Signalling (RBS) has been statically busied out on the specified time slot and controller.

Recommended Action No action is required.

Error Message

%DSX0-5-RBSLINEUNBUSYOUT: RBS of slot [dec] controller [dec] timeslot [dec] is unbusyout

Explanation Robbed-Bit Signalling (RBS) has been restored from a busied out condition on the specified time slot and controller.

Recommended Action No action is required.

Error Message

%DSX1-3-FIRMWARE_RESTART: T1/E1 Firmware in slot [dec] restarted

Explanation T1/E1 firmware has been restarted. All the active calls on the T1/E1 lines will be disconnected, and the controllers will come back up within a few seconds.

Recommended Action No action is required.

Error Message

%DSX1-1-FIRMWARE_RESTART_FAILED: Trunk Firmware in slot [dec] reset failed

Explanation The trunk could not be restarted.

Error Message

%DSX1-1-FIRMWARE_RUNNING: T1/E1 Firmware in slot [dec] is running

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

Error Message

%DSX1-1-FIRMWARE_STOPPED: T1/E1 Firmware in slot [dec] is not running

Explanation The T1/E1 firmware has experienced a critical error and has stopped running. The access server must be reloaded.

Error Message

%EVENT-3-INSERT_FAILURE: Failed to insert [chars]

Explanation The event process has failed to insert the newly created row in its linked list data structure.

Error Message

%EVENT-3-NULL_ELEMENT: Null pointer in the watched queue for [chars] test

Explanation The process was interrupted by a Null element.

Error Message

%EVENT-3-NULL_STRUCT: Null pointer to the [chars] structure

Explanation The process was interrupted by an element that contained a Null pointer to the test structure.

Error Message

%E1T1_MODULE-3-BERTBUSY: Controller [chars] - BERT hardware in use, command refused

Explanation The current task requires bit error rate tester (BERT) hardware resources that are currently occupied with other tasks.

Recommended Action The BERT chip could be in use by either of the following tasks: sending V.54 loopup or loopdown code to the remote end or running a BERT test. Determine if either of the tasks is in progress on this controller.

Error Message

%E1T1_MODULE-3-FDLLLOOPDOWN: Controller [chars] - FDL line loopdown code detected, deactivating line loopback.

Explanation The system has detected Facility Data Link (FDL) line loopdown code on the unit, and it is deactivating the line loopback.

Recommended Action No action is required.

%E1T1_MODULE-3-FDLPREQOK: Controller [chars] - Remote end is put in payload loopback mode via FDL.

Explanation The T1 Facility Data Link (FDL) payload loopup code was sent to the remote end from the unit, and the remote end has activated the payload loopback.

Recommended Action No action is required.

Error Message

%E1T1_MODULE-3-IBOCLOOPDOWN: Controller [chars] - IBOC loopdown code detected, deactivating line loopback.

Explanation The system has detected inband bit-oriented code (IBOC) loopdown code on the unit, and is it deactivating the line loopback.

Recommended Action No action is required.

Error Message

%E1T1_MODULE-3-IBOCLOOPUP: Controller [chars] - IBOC loopup code detected, activating line loopback mode.

Explanation The system has detected inband bit-oriented code (IBOC) loopup code on the unit, and it is activating the line loopback.

Recommended Action No action is required.

Error Message

%E1T1_MODULE-3-IBOCREQFAILED: Controller [chars] - Failed to put the remote end in line loopback mode via IBOC.

Explanation The T1 inband bit-oriented code (IBOC) loopup code was sent to the remote end, but the remote end did not activate the line loopback. The remote end may not have activated the payload loopback because of a controller configuration or line problem.

Recommended Action Ensure that both controllers are up.

Error Message

%E1T1_MODULE-3-IBOCREQOK: Controller [chars] - Remote end is put in line loopback mode via IBOC.

Explanation The T1 inband bit-oriented code (IBOC) loopup code was sent to the remote end from the unit, and the remote end has activated the line loopback.

Recommended Action No action is required.

Error Message

%E1T1_MODULE-3-T1REQCANCELLED: Controller [chars] - T1 remote loopback has been cancelled.

Explanation T1 loopdown code has been sent to the remote end from the specified unit. The remote end is assumed to have received the loopdown code and deactivated the loopback mode. However, no test has been performed to ensure that the remote end has deactivated the loopback mode.

Recommended Action No action is required.

Error Message

%E1T1_MODULE-3-V54REQFAILED: Unit [chars] - Failed to put the remote end in V.54 payload loopback mode

Explanation The V.54 loopup code was sent to the remote end, but the remote end did not activate loopback. This error could be caused by a controller configuration mismatch or line problem.

Recommended Action Check the time slots and speed setting on both ends for the channel group in question, and ensure that V.54 detection is enabled on the remote end.

Error Message

%FALLBACK-4-CACHE_OVERFLOW: Cache has overflowed.

Explanation The fallback cache has overflowed and has dumped a fourth of the entries.

Recommended Action Increase the fallback cache size.

Error Message

%FALLBACK-3-INTERNAL_ERROR: [chars]: Internal error.

Explanation An internal error has occurred.

Error Message

%FALLBACK-3-MALLOC_FAIL: [chars]: Memory allocation failed.

Explanation A memory allocation has failed, possibly because of the fact that system memory pool is exhausted.

Recommended Action Allocate more system memory.

Error Message

%FALLBACK-3-NO_RTP_PORT: No available RTP ports.

Explanation No available voice Real-Time Transport Protocol (RTP) ports were found.

Error Message

%FALLBACK-3-NO_STATS: [chars]: No stats were returned.

Explanation No statistics were returned with the probe.

Recommended Action No action is required.

Error Message

%FALLBACK-3-PROBE_FAILURE: A probe error to [IP_address] occurred - [chars]

Explanation A probe error has occurred. The responder on the remote router may not have been enabled, or there may not have been any machine on the specified IP address.

Recommended Action Check the destination router.

Error Message

%FALLBACK-3-RTR_CREATE_FAIL: [chars]: Creation of probe failed. Return code [dec]

Explanation A response time reporter (RTR) probe could not be created. Not having an RTR probe can cause inaccurate Calculated Planning Impairment Factor (ICPIF) values and also can cause Voice over IP (VoIP) calls to be hairpinned when they should not be hairpinned.

Error Message

%FALLBACK-3-RTR_START_FAIL: [chars]: probe could not be started. Return code [dec]

Explanation A response time reporter (RTR) probe could not be started. Not having an RTR probe can cause lost or inaccurate Calculated Planning Impairment Factor (ICPIF) values, and can cause VoIP calls to be hairpinned when they should not be hairpinned.

Error Message

%FALLBACK-3-RTR_STATS_FAIL: [chars]: Could not retrive statistics from the probe. Return code [dec]

Explanation Response time reporter (RTR) statistics could not be retrieved from the probe. The absence of RTR statistics can result in inaccurate Calculated Planning Impairment Factor (ICPIF) values and can cause Voice over IP (VoIP) calls to be hairpinned when they should not be hairpinned.

Error Message

%FALLBACK-5-TEST_PROBE_ALREADY_RUNNING: A test probe is already running.

Explanation Only one test probe may run at a time.

Recommended Action Wait until the first test probe has finished before initiating a second test probe.

Error Message

%FECPM-3-BSCHUNT: BSC HUNT cmd for int [dec]/[dec] failed

Explanation An internal software error has occurred.

Error Message

%FECPM-1-DISCOVER: NM slot [dec]: only [dec] PCI dev found

Explanation Some of the interface controller devices on the Fast Ethernet Combination Port Module network module did not initialize properly.

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

%FECPM-3-DSCC4: DSCC4 chip init slot [dec] failed

Explanation An internal software error has occurred.

Error Message

%FECPM-1-INITFAIL: NM slot [dec]: PCI dev [dec] init failed

Explanation A protocol control information (PCI) device on the Fast Ethernet Combination Port Module device driver network module has failed to successfully initialize the hardware.

Error Message

%FECPM-3-INVALID_CLOCKRATE: Unsupported clock rate req on int [dec]/[dec] - index [dec]

Explanation An internal software error has occurred.

Error Message

%FECPM-3-INVALID_SCC: Config req for invalid SCC via int [dec]/[dec]

Explanation An internal software error has occurred.

Error Message

%FECPM-3-NOMEMORY: No memory for [chars] of unit [dec]

Explanation The router does not have enough memory to perform the specified function.

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

Error Message

%FECPM-3-OWNERR: Buffer owner ship error on int [dec]/[dec], pak=0x[hex]

Explanation An internal software error has occurred.

Error Message

%FECPM-2-SCCFAIL: Init of SCC[dec] for int [dec]/[dec] failed to do [chars]

Explanation The software has failed to initialize or restart a Signaling Connection Control (SCC) of a serial interface on the Fast Ethernet Combination Port Module device driver network module.

Recommended Action Clear the serial interface. If the message recurs, copy the error message exactly as 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

%FECPM-3-SCCRESET: SCC reset for int [dec]/[dec] at [chars] failed

Explanation An internal software error has occurred.

Error Message

%FECPM-3-SPI_OP_FAILED: NM base addr - 0x[hex], WIC slot - [dec], SPI op failed

Explanation An internal software error has occurred.

Error Message

%FECPM-5-TOOBIG: On int [dec]/[dec], tx pak is [dec] bytes

Explanation A packet greater than the assigned maximum transmission unit (MTU) of this serial interface was queued up for transmission. The system should recover.

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

%FECPM-5-TOOSMALL: On int [dec]/[dec], tx pak size is [dec] bytes

Explanation A small packet (fewer than 2 bytes) was queued up for transmission. The interface cannot send packets that are smaller than 2 bytes. The system should recover.

Error Message

%FECPM-3-TXCOMPNOTIFY: On int [dec]/[dec], tx_comp_notify vector is not set

Explanation An internal software error has occurred.

Error Message

%FECPM-3-UFHANDLE: UnderFlow handling on int [dec]/[dec] failed

Explanation An internal software error has occurred.

Error Message

%FECPM-5-UNDERFLOW: Transmit underflow on int [dec]/[dec]

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 the output rate of the chip. Normally, this system problem is temporary, depending on transient peak loads within the system.

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

Error Message

%FECPM-1-UNKNOWN_WIC: NM slot [dec], wic card has an unknown id [hex]

Explanation The software does not recognize the type of WAN interface card (WIC) that is plugged into the port module.

Recommended Action Check the part number on the WIC card to verify that it is supported in the Cisco IOS release that is operational on the router. Copy the error message exactly as 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

%FIB-3-FIBSBINIT: Error initializing [chars] subblock data structure. [chars]

Explanation The initialization of the specified Cisco Express Forwarding (CEF) subblock data structure could not be accomplished.

Error Message

%FIB-3-MAXPATHS_EXCEEDED: Max paths is [dec], [dec] attempted. Address was [IP_address], mask was [IP_address]

Explanation An internal software error has occurred. An attempt was made to set up more than the supported number of routing paths. Cisco Express Forwarding (CEF) switching has been disabled on this slot.

Recommended Action Investigate why the number of routing paths has been exceeded.

Error Message

%FIB-3-POLICY_NULL_ROUTEMAP: Empty or missing policy routemap found on [chars]

Explanation The expected policy route map was empty or missing.

Recommended Action Investigate why an empty route map was associated with this slot.

Error Message

%FR-3-FRTSZEROCIR: FRTS: attempt to configure zero CIR

Explanation It it not possible to configure a zero committed information rate (CIR). Configuring a zero CIR would prevent data transmission on the virtual circuit (VC).

Error Message

%GPRSMIB-4-FRAGMENT_ERROR: fragmentation error (s_uid = [hex]) received

Explanation An internal software error has occurred.

Error Message

%GPRSMIB-4-INVALIDMSG: Invalid GPRSMIB message (msg_type [hex]) received

Explanation An internal software error has occurred.

Error Message

%GTP-2-APNINVALID: APN name requested ([chars]) is not valid for the GSN node from [int]

Explanation An access-point name (APN) lookup has failed.

Error Message

%GTP-2-CGWUPDOWN: Charging Gateway [int] changed state to [chars]

Explanation The primary or secondary charging gateway has changed its state from up to down or from down to up.

Error Message

%GTP-6-EXTIPADDRALLOCFAIL: ip address allocation failed from external source. APN: [chars] TID: [hex] Reason: [chars]

Explanation The Gateway GPRS Support Node (GGSN) has failed to allocate the dynamic IP address.

Error Message

%GTP-2-GSNPATHFAIL: Path to GSN peer [int] failed

Explanation No echo message was received from the GSN peer, and the path has timed out.

Error Message

%GTP-2-GSNSERVICEUPDOWN: GSN service [chars] changed state to [chars]

Explanation The Gateway GPRS Support Node (GGSN) or Serving GPRS Service Node (SGSN) service has started or has shut down.

Error Message

%GTP-6-INTIPADDRALLOCFAIL: ip address allocation failed from internal local pool. APN: [chars] TID: [hex] Reason: [chars]

Explanation The Gateway GPRS Support Node (GGSN) has failed to allocate a dynamic IP address from the local pool.

Error Message

%GTP-6-INVALIDIE: Invalid information element (type [dec]) for message type 0x[hex] from [int]

Explanation The system has received a GPRS Tunneling Protocol (GTP) packet with an invalid message format.

Recommended Action Determine why the source of the packet is not generating a correct message.

Error Message

%GTP-6-INVALIDLFN: Invalid GTP header (lfn bit): [char]

Explanation The system has received a GPRS Tunneling Protocol (GTP) packet with an invalid header element.

Recommended Action Determine why the source of the packet is not generating a correct header.

Error Message

%GTP-6-INVALIDTID: Invalid GTP header (TID): [hex] from [int]

Explanation The system has received a GPRS Tunneling Protocol (GTP) packet with an invalid or unknown Terminal Identifier (TID).

Recommended Action Determine why the source of the packet is not generating a correct header.

Error Message

%GTP-2-MSGTOOSHORT: GTP message is too short for the message type, msgtype: [dec], len: [dec], from [ipaddr]

Explanation The GPRS Tunneling Protocol (GTP) message received is too short to contain all expected information elements.

Error Message

%GTP-2-NORESOURCE: System resources exhausted: ([chars])

Explanation The system resources are exhausted.

Error Message

%GTP-2-PDPACTIVATIONFAIL: GTP PDP activation/update failed, GSN: [int], TID: [hex], Reason: [chars]

Explanation A PDP context activation has failed.

Error Message

%GTP-6-PDUPURGED: PDP context purged, TID: ([hex])

Explanation A PDP context idle timeout has occurred.

Error Message

%GTP-2-PROCESSDOWN: GTP Process creation failed

Explanation The system cannot start the GPRS Tunneling Protocol (GTP) process.

Error Message

%GTP-2-SOCKETSENDFAILED: GTP send failed, errno [dec]

Explanation The system cannot send a GPRS Tunneling Protocol (GTP) message using this socket.

Error Message

%GTP-2-UNEXPECTEDMSG: Unexpected GTP signalling message (type 0x[hex]) received from [int]

Explanation An internal software error has occurred.

Error Message

%GTP-2-UNKNOWNMSG: Unknown GTP message (type 0x[hex]) received from [int]

Explanation An internal software error has occurred.

Error Message

%GTP-2-VERSIONNOTSUPPORT: GTP Version is not supported, source GSN [int], version received: ([dec]), version supported: ([dec])

Explanation The GPRS Tunneling Protocol (GTP) version received is not supported.

Error Message

%HDX-3-BADFSM: On int [dec]/[dec], unexpected state [dec], event [dec]

Explanation An unexpected state and event pair were detected in the rx/tx half-duplex state machine.

Error Message

%INTERFACE_API-3-NODESTROYSUBBLOCK: The [chars] subblock named [chars] was not removed

Explanation A software error has occurred. The specified Interface Descriptor Block (IDB) subblocks cannot be removed.

Error Message

%IP-4-UNICASTRPF: IP unicast reverse-path check disabled on [chars]

Explanation The IP Verify Unicast Reverse-path feature was disabled because Cisco express forwarding (CEF) has been disabled, either through configuration or because of an internal error.

Error Message

%IPC-3-LOWBUFF: The main IPC message header cache below application reserve count ([dec])., MSGDEF_LIMIT_SLOW

Explanation The main IPC message header cache has fallen below the application reserve count.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ipc status 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 ipc status command output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message

%IPC-2-NOACKRECEIVER: Got an ACK with data, couldn't find receiver.

Explanation A preview function has inserted data into an ACK, but there is no corresponding ACK receiver.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue 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

%IPFAST-4-INVALFAIL: Error invalidating IP fast cache due to memory shortage

Explanation This debugging message appears when a memory shortage has occurred. The memory shortage could cause incorrect switching decisions.

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

Error Message

%IPFAST-2-IPCACHEINIT: Error initializing IP fast cache structures

Explanation A programming error has occurred.

Error Message

%ISDN-2-ISDN_GENERAL_TRACEBACK: [chars]:[dec]

Explanation A debug traceback condition has occurred.

Recommended Action No action is required.

Error Message

%ISDN-4-RLM_STATUS_CHANGE: ISDN SC [chars]: Status Changed to: [chars]

Explanation The ISDN has been notified by the Redundant Link Manager (RLM) component of a status change in the RLM link.

Recommended Action No action is required.

Error Message

%IVR-3-BAD_IVR_VERSION: Script requires version [dec].[dec], image supports [dec].[dec]

Explanation The Integrated Voice Response (IVR) script requires a more recent version of IVR infrastructure.

Recommended Action Upgrade the version of Cisco IOS software, or use a more recent IVR script.

Error Message

%IVR-3-NOSCRIPT: Could not load IVR script [chars] errno=[dec]=[chars]

Explanation The IVR script could not be loaded.

Recommended Action Ensure that the script exists on the server, and ensure that it is readable.

Error Message

%L2R-4-DROP_PAK: l2r uid [dec] drop packet (type [hex]) from/to uid [dec] when [chars]

Explanation A packet was dropped.

Error Message

%L2R-4-FRAGMENT_ERROR: fragmentation error (s_uid = [hex]) received

Explanation An internal software error has occurred.

Error Message

%L2R-4-INVALIDMSG: Invalid L2R message (msg_type [hex]) received from UID [dec] at line [dec]

Explanation An internal software error has occurred.

Error Message

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

Explanation An internal software error has occurred.

Error Message

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

Explanation An internal software error has occurred.

Error Message

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

Explanation An internal software error has occurred.

Error Message

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

Explanation An internal software error has occurred.

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 Line printer daemon (LPD) data destined for a printer configured with the newline-convert command. This message is unlikely to occur with a file that contains valid data.

Recommended Action Check the file being printed to see whether it contains valid, printable data.

Error Message

%MGCP-2-INTERNAL_CRITICAL: [chars], MGCP_COMPLAIN_IVL

Explanation An internal software error has occurred.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue 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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%MGCP-3-INTERNAL_ERROR: [chars], MGCP_COMPLAIN_IVL

Explanation An internal software error has occurred.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue 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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%MGCP-4-INTERNAL_WARNING: [chars], MGCP_COMPLAIN_IVL

Explanation An internal software error has occurred.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue 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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%MGCP_APP-6-EVT_NODE_ALLOC_FAILED: Failed to allocate memory for event node

Explanation A memory allocation for the event node has failed.

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

Error Message

%MGCP_APP-6-GEN_INIT_NO_IP_INTF_FAILED: Suspended initialization of MGCP services. No IP interface up yet

Explanation The initialization of Media Gateway Control Protocol (MGCP) services has been suspended. No IP interface has been brought up yet.

Recommended Action Ensure that there is at least one interface configured with an IP address.

Error Message

%MICA-3-CRASH: Runtime error on MICA module [dec] Hex [dec]

Explanation A software error has occurred on the modem firmware that is running on the specified modem module.

Error Message

%MICA-3-INBANDNAK: Inband NAK from modem ([dec]/[dec]): opcode = 0x[hex]

Explanation An in-band message that had been sent to the specified modem has been rejected.

Error Message

%MICA-3-INBANDNAK: Inband NAK from modem [dec] -- payload 0x[hex][hex][hex][hex][hex][hex] 0x[hex][hex]

Explanation An in-band message that had been sent to the specified modem has been rejected.

Error Message

%MICA-3-INBAND_UNKNOWN_OPCODE: Inband message with unknown opcode received from modem [dec] -- payload [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]

Explanation An in-band message with an unknown operation code has been received from the specified modem.

Error Message

%MICA-3-INVALID_PARAM: Mica sent invalid stack address or length, MICA module [dec], addr 0x[hex], length [dec]

Explanation A run-time error has occurred on the Modem ISDN channel aggregation modem (MICA) module. The MICA module has sent an invalid stack address or length.

Error Message

%MICA-3-UNKNINBAND: Unknown inband msg from modem ([dec]/[dec]): opcode = 0x[hex]

Explanation An unknown in-band message has been received from the specified modem.

Error Message

%MODEM-3-MODEM_INFO_CREATE_FAIL: Unable to create modem infos for slot [dec]

Explanation During online insertion and removal (OIR) of the specified board, the modem information could not be created because of a lack of memory.

Recommended Action Save the output of the show memory command, showing the amount of processor and I/O memory usage only, along with the output of the show version command. Call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%MODEMCALLRECORD-3-PM_CALL_RECORD_ERROR: [chars]

Explanation An Exceeded Syslog Capability record has been received.

Recommended Action No action is required.

Error Message

%MODEMCALLRECORD-3-PM_NO_CALL_RECORD_BUF: [chars]

Explanation A buffer to build the modem call record could not be allocated.

Recommended Action No action is required.

Error Message

%MODEMCALLRECORD-6-PM_TERSE_CALL_FAILED_RECORD: [chars]

Explanation A Terse Modem Call Failed Record has been received.

Recommended Action No action is required.

Error Message

%MODEM_HIST-7-CONTROL: [chars]: Control Reply: [hex][hex]

Explanation A reply to a control message has been received.

Recommended Action This is a debug message only. No action is required.

Error Message

%MODEM_HIST-7-CSM_IC_CALLED_NUM: [chars]: ISDN incoming called number: [chars]

Explanation This tracing message shows the number of the ISDN line that is receiving a call.

Recommended Action This is a debug message only. No action is required.

Error Message

%MODEM_HIST-7-CSM_IC_CALLING_NUM: [chars]: ISDN incoming caller number: [chars]

Explanation This tracing message shows the number of an incoming ISDN caller.

Recommended Action This is a debug message only. No action is required.

Error Message

%MODEM_HIST-7-CSM_OC_CALLED_NUM: [chars]: ISDN outgoing called number: [chars]

Explanation This tracing message shows a dialed ISDN number.

Recommended Action This is a debug message only. No action is required.

Error Message

%MODEM_HIST-3-DC_EVT_POLL: [chars]: DC session response: [chars]

Explanation This trace log event provides information for a DC Session response event.

Recommended Action No action is required.

Error Message

%MODEM_HIST-3-DC_SESSION: [chars]: DC Session received reply

Explanation This trace log event confirms that the DC Session has received a reply.

Recommended Action No action is required.

Error Message

%MODEM_HIST-7-MICA_DEBUG_EVT: [chars]: [chars]:

Explanation This tracing message provides information about a host debug event that had been reported by the specified Modem ISDN Channel Aggregation (MICA) modem.

Recommended Action This is a debug message only. No action is required.

Error Message

%MODEM_HIST-7-MICA_DYNAMIC_EVT: [chars]: [chars]: [chars]

Explanation This tracing message provides information about a dynamic event that had been reported by the specified Modem ISDN Channel Aggregation (MICA) modem.

Recommended Action This is a debug message only. No action is required.

Error Message

%MODEM_HIST-7-MICA_END_CONN_EVT: [chars]: [chars]: [chars]

Explanation This tracing message provides information about an end connection event that had been reported by the specified Modem ISDN Channel Aggregation (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 tracing message provides information about a lead event that had been reported by the specified Modem ISDN Channel Aggregation (MICA) modem.

Recommended Action This is a debug message only. No action is required.

Error Message

%MODEM_HIST-7-MICA_OOS_EVT: [chars]: [chars] [chars] Cause: [chars]

Explanation This tracing message provides information about an out-of-service event that had been reported by the specified Modem ISDN Channel Aggregation (MICA) modem.

Recommended Action This is a debug message only. No action is required.

Error Message

%MODEM_HIST-7-MICA_STARTUP_EVT: [chars]: [chars] [chars]. [chars] Modem firmware = [dec].[dec].[dec].[dec]

Explanation This tracing message confirms the successful startup of the specified Modem ISDN Channel Aggregation (MICA) modem.

Recommended Action This is a debug message only. No action is required.

Error Message

%MODEM_HIST-7-MICA_STATE_EVT: [chars]: [chars] [chars] State: [chars]

Explanation This tracing message provides information about a state event that had been reported by the specified Modem ISDN Channel Aggregation (MICA) modem.

Recommended Action This is a debug message only. No action is required.

Error Message

%MODEM_HIST-7-MICA_STATIC_EVT: [chars]: [chars]: [chars]

Explanation This tracing message provides information about a static event that had been reported by the specified Modem ISDN Channel Aggregation (MICA) modem.

Recommended Action This is a debug message only. No action is required.

Error Message

%MODEM_HIST-7-MICA_STATUS_EVT: [chars]: [chars]: [chars]. [chars] Modem firmware = [dec].[dec].[dec].[dec]

Explanation This tracing message provides information about a status event that had been reported by the specified Modem ISDN Channel Aggregation (MICA) modem.

Recommended Action This is a debug message only. No action is required.

Error Message

%MODEM_HIST-7-POLL_ANALOG: [chars]: Modem Analog signal event: TX = [dec], RX = [dec], Signal to noise = [dec]

Explanation This tracing message reports a change in analog signal status.

Recommended Action This is a debug message only. No action is required.

Error Message

%MODEM_HIST-7-POLL_CALLER_ID: [chars]: Caller ID event: [chars]

Explanation Caller ID data has been received.

Recommended Action This is a debug message only. No action is required.

Error Message

%MODEM_HIST-7-POLL_CONN_1: [chars]: Connection event: TX/RX Speed = [int]/[int], Modulation = [chars]

Explanation This tracing message confirms the establishment of a connection.

Recommended Action This is a debug message only. No action is required.

Error Message

%MODEM_HIST-7-POLL_CONX_UPDATE: [chars]: Connection update event: TX/RX Speed = [int]/[int], Modulation = [chars]

Explanation This tracing message reports a connection state change.

Recommended Action This is a debug message only. No action is required.

Error Message

%MODEM_HIST-3-POLL_DSP_NEEDED: [chars]: DSP Image Needed Event

Explanation The digital signal processor (DSP) image needs to be downloaded to the modem in order to achieve 56K operation.

Recommended Action Download the DSP image to the modem.

Error Message

%MODEM_HIST-7-POLL_DTR: [chars]: DTR event: [chars]

Explanation This tracing message reports a change in the data terminal ready (DTR) signal.

Recommended Action This is a debug message only. No action is required.

Error Message

%MODEM_HIST-7-POLL_END_1: [chars]: End connection event: Retransmits for MNP block (TX/RX) = [dec]/[dec]

Explanation This tracing message reports an end-of-connection status.

Recommended Action This is a debug message only. No action is required.

Error Message

%MODEM_HIST-7-POLL_ERROR: [chars]: Polling protocol error event: [hex]

Explanation This tracing message reports a polling protocol error.

Recommended Action This is a debug message only. No action is required.

Error Message

%MODEM_HIST-7-POLL_EVT_LOST: [chars]: Status event lost: [hex]

Explanation This tracing message reports that a polling event was lost.

Recommended Action This is a debug message only. No action is required.

Error Message

%MODEM_HIST-7-POLL_INACT: [chars]: Modem Activity event: [chars]

Explanation This tracing message reports a change in data activity status.

Recommended Action This is a debug message only. No action is required.

Error Message

%MODEM_HIST-7-POLL_MODEM_STATE: [chars]: Modem State event: [chars]

Explanation This tracing message reports a modem state change.

Recommended Action This is a debug message only. No action is required.

Error Message

%MODEM_HIST-7-POLL_NO_RESP: [chars]: No poll response event: [hex]

Explanation This tracing message confirms that no response was received to a poll.

Recommended Action This is a debug message only. No action is required.

Error Message

%MODEM_HIST-7-POLL_PHONE: [chars]: Phone number event: [chars]

Explanation This tracing message shows a phone number that is being dialed.

Recommended Action This is a debug message only. No action is required.

Error Message

%MODEM_HIST-7-POLL_PROGRESS: [chars]: Call Progress event: [chars]

Explanation This tracing message reports the status of a call in progress.

Recommended Action This is a debug message only. No action is required.

Error Message

%MODEM_HIST-7-POLL_RS232: [chars]: RS232 event: [chars][char] [chars][char] [chars][char] [chars][char] [chars][char] [chars][char] [chars][char]

Explanation This tracing message provides information about RS-232 events.

Recommended Action This is a debug message only. No action is required.

Error Message

%MODEM_HIST-7-POLL_TX_RX: [chars]: TX/RX event: TXD=[chars], RXD=[chars]

Explanation This tracing message provides information about transmit and receive events.

Recommended Action This is a debug message only. No action is required.

Error Message

%MODEM_HIST-7-POLL_UNKNOWN: [chars]: Unknown or lost event [hex]

Explanation This tracing message contained an unrecognized modem history event. One or more events may be missing from the trace, because there is insufficient space to store the modem history.

Recommended Action If modem history events are required, a possible remedy is to reduce the number of events recorded between history dumps. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message

%MODEM_HIST-7-STARTUP: [chars]: Startup Response: [chars]. Modem (boot) firmware = [dec].[dec].[dec] ([dec].[dec].[dec])

Explanation This tracing message confirms the successful startup of the specified modem.

Recommended Action This is a debug message only. No action is required.

Error Message

%MODEM_HIST-7-TRACE_HDR: [chars] Modem [chars] Events Log:

Explanation This tracing message confirms the start of the trace of the specified modem. The stored trace messages of the modem will follow.

Recommended Action This is a debug message only. No action is required.

Error Message

%MODEM_HIST-7-UNKNOWN_FRAME: [chars]: Error in events log

Explanation A formatting error in the modem event history has occurred. One or more events may be missing from the trace.

Recommended Action This is a debug message only. No action is required.

Error Message

%MPA68360-1-DWNLDCKSM: Failed for bay [dec], sent = [hex], received = [hex]

Explanation The download of the internal firmware to the MPA68360 has failed to checksum correctly. An unsuccessful checksum process usually indicates a hardware failure of the MPA6836.

Recommended Action Perform a power cycle. If the problem persists, the MPA68360 hardware may be defective.

Error Message

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

Explanation The PRI port adapter has failed to complete hardware initialization.

Error Message

%MPA68360-3-MBXREAD: [chars] has stale msg - mbx0:[hex], mbx1:[hex], mbx2:[hex]

Explanation The MPA68360 hardware has not responded to a message within the specified time.

Error Message

%MPA68360-1-NOTCMPLT: Microcode download to bay [dec] failed

Explanation The MPA68360 hardware has failed and could not download its operational microcode.

Error Message

%MPA68360-3-NOTMPA68360: Bay [dec] device ID seen as [hex], expected [hex]

Explanation The MPA68360 hardware has failed. A device other than the MPA68360 pointed at the software for the MPA68360 serial.

Error Message hardware

%MPA68360-1-NOTREADY: Bay [dec] for microcode download

Explanation An error has occurred on the communication path between the driver and the MPA68360 hardware.

Error Message

%MPA68360-3-PANIC: Exception [dec], trace [dec]

Explanation The MPA68360 firmware has detected an illegal or unexpected CPU exception or condition. This problem may be caused by a software error or by a hardware failure.

Error Message

%MPA68360-1-STARTFAIL: [chars] channel not enabled

Explanation A software or hardware error has occurred. The MPA68360 serial interface is not responding to the commands that were used to initialize it.

Error Message

%MPA68360-1-STOPFAIL: [chars] channel not disabled

Explanation The PRI port adapter has failed to respond to a request to disable an interface.

Error Message

%MPLS_ATM_TRANS-3-CONSISTENCY: [chars]

Explanation An action attempted by the ATM-over-MPLS feature has encountered an unexpected condition.

Error Message

%MPLS_TE-3-CONSISTENCY: [chars]: [chars] [chars] [chars], MSGDEF_LIMIT_SLOW

Explanation An action attempted by the traffic engineering tunnel implementation has encountered an unexpected condition.

Error Message

%MPLS_TE-5-LSP: [chars]

Explanation An informational traffic engineering tunnel trap has been generated for an link-state packet (LSP) event.

Recommended Action This is an informational message only. Save this message for tunnel operation debugging analysis.

Error Message

%MPLS_TE-3-SIGNALLERINIT: Signaller unable to [chars]register RSVP [chars]

Explanation A message handler used by the signaler to receive events or requests from Resource Reservation Protocol (RSVP) could not be installed or removed.

Recommended Action Copy and save the error message. If possible, restart the tag-switched path (TSP) tunnel signaling process by issuing the no tag-switching tsp-tunnels command, followed by the tag-switching tsp-tunnels command. If the message recurs after you have restarted the signaling process several times, contact your Cisco technical support representative for assistance.

Error Message

%MPLS_TE-5-TUN: [chars]

Explanation An informational traffic engineering tunnel trap was generated for a tunnel event.

Recommended Action This is an informational message only. Save this message for tunnel operation debugging analysis.

Error Message

%MPLS_TE-3-TUNNELKILL: Tunnel removal attempt (by [chars]) failed for tunnel [chars]: [chars], MSGDEF_LIMIT_SLOW

Explanation A state that is associated with a tag-switched path (TSP) tunnel could not be completely removed because of an internal failure.

Recommended Action Copy and save this message. If possible, remove all local TSP tunnel states by issuing the no tag-switching tsp-tunnels command, followed by the tag-switching tsp-tunnels command. The TSP tunnels that were removed by the first command should be resignaled shortly after the second command has been issued. If the message recurs, copy and save the message and call your Cisco technical support representative for assistance.

Error Message

%MROUTE-3-ROUTECOUNT_ERR: Running multicast route count [int]

Explanation The running count of multicast routes is different from the number of multicast routes that is reported in the multicast routing table. An error involving the maintenance of the multicast route count has occurred.

Error Message

%MROUTE-3-ROUTECOUNT_ZERO: Multicast route count reached zero, MSGDEF_LIMIT_GLACIAL

Explanation The running count of multicast routes has reached zero. The count of multicast routes cannot be zero. An error involving the maintenance of the multicast route count has occurred.

Error Message

%MROUTE-4-ROUTELIMIT: [int] routes exceeded multicast route-limit of [dec], MSGDEF_LIMIT_GLACIAL

Explanation The number of multicast routes has exceeded the configured maximum number. New routes cannot be added unless the configuration is changed.

Recommended Action No action is required unless multicast traffic is of higher priority than the other traffic carried by this router. To increase the number of multicast routes, enter the ip multicast route-limit command.

Error Message

%NP-3-CTRL_POOL_CREATION_FAIL: Control buffer pool could not be created

Explanation The NextPort (NP) driver could not create the control buffer pool required for the TX and RX portions of the NP control messages.

Error Message

%NP-3-MODNOTEXIST: Slot [dec], DFC [dec], Module [dec] not exist.

Explanation No virtual console opens for this module.

Error Message

%NP-3-NAKRSP: NAK Response Received - command [hex], result code [hex], msg id [hex], session id [hex], msg tag [hex]

Explanation A NAK response was sent by the NextPort module.

Error Message

%NP-3-NOTMSGID: Message Id [hex] not supported.

Explanation The NextPort module does not support the specified control message ID.

Error Message

%NP-3-QUEUEFULL: [chars] queue is full for Slot [dec], DFC [dec], Module [dec].

Explanation The TX queue is full for the specified module.

Error Message

%NP-3-RESET_DFC: DFC Reset-Cleared Failed - DFC [dec]

Explanation A dial feature card (DFC) Reset-Cleared operation has failed.

Error Message

%NP_BS-3-CRC_FAIL: NextPort Module [dec]/[dec]/[dec] failed firmware image validation

Explanation The NextPort BootStrap and Crash Monitor has detected a failed NextPort firmware cyclic redundancy check (CRC) validation.

Error Message

%NP_BS-3-INITSYS: [chars]

Explanation A NextPort BootStrap and Crash Monitor initialization has failed.

Error Message

%NP_BS-3-INVALID_FW: Invalid NextPort Firmware for [dec]/[dec]/[dec]

Explanation The NextPort BootStrap and Crash Monitor has detected invalid NextPort firmware.

Error Message

%NP_BS-3-INVALID_IDT: NextPort Module [dec]/[dec]/[dec] detected an invalid IDT

Explanation The NextPort BootStrap and Crash Monitor has detected an invalid IDT.

Error Message

%NP_BS-3-INVALID_MC_POST: NextPort Module [dec]/[dec]/[dec] detected a module POST failure [hex]

Explanation The NextPort BootStrap and Crash Monitor has detected a failed module.

Error Message

%NP_BS-3-MEM_TEST_FAIL: NextPort Module [dec]/[dec]/[dec] memory test failed

Explanation The NextPort BootStrap and Crash Monitor has detected a failed NextPort module memory test.

Error Message

%NP_BS-3-MODULE_ACCESS_ERR: Failed to access NextPort module [dec]/[dec]/[dec] crash info

Explanation The NextPort BootStrap and Crash Monitor has failed to access crash information.

Recommended Action No action is required.

Error Message

%NP_BS-6-MODULE_STARTED: NextPort module [dec]/[dec]/[dec] Started - [dec].[dec].[dec].[dec]

Explanation The NextPort BootStrap and Crash Monitor has successfully started the specified module.

Recommended Action No action is required.

Error Message

%NP_BS-6-MODULE_STOPPED: NextPort module [dec]/[dec]/[dec] Stopped

Explanation The NextPort BootStrap and Crash Monitor has stopped the specified module.

Recommended Action No action is required.

Error Message

%NP_BS-3-NO_KEEPALIVE: NextPort module [dec]/[dec]/[dec] failed to respond to keepalive message

Explanation The NextPort BootStrap and Crash Monitor has detected a module that has failed to respond to a keepalive message.

Recommended Action No action is required.

Error Message

%NP_BS-3-NOMEM: [chars]

Explanation The NextPort BootStrap and Crash Monitor could not allocate memory for an internal module database.

Recommended Action No action is required.

Error Message

%NP_BS-3-NO_SUCH_MODULE: [chars] nonexisting NP module [dec]/[dec]/[dec]

Explanation The NextPort BootStrap and Crash Monitor has detected an internal database error.

Recommended Action No action is required.

Error Message

%NP_BS-3-NULL_FW_PTR: NULL NextPort Firmware pointer for [dec]/[dec]/[dec]

Explanation The NextPort BootStrap and Crash Monitor has detected a null NextPort firmware pointer.

Error Message

%NP_BS-3-Q_FAILURE: NextPort Module [dec]/[dec]/[dec] control queue creation failure

Explanation The NextPort BootStrap and Crash Monitor has detected a failed control queue creation.

Error Message

%NP_BS-2-THREE_NP108_NOT_PRESENT: DFC in slot [dec] does not have three NP108s!

Explanation The Dial Feature Card (DFC) does not have three NP108s. A correct configuration has three NP108s.

Error Message

%NP_EST-6-CTRL_NAK_RSP: [chars]

Explanation An EST Control No-Acknowledge Notification has been sent to the Cisco IOS software system to convey additional debug data regarding a NAK that occurred on the control queue.

Recommended Action No action is required.

Error Message

%NP_EST-6-DIAG_POST_NTF: [chars]

Explanation An EST diagnostic POST notification has been sent to the Cisco IOS software system to convey additional information about the power-on self-test or a diagnostic test result.

Recommended Action No action is required.

Error Message

%NP_EST-3-MSG_ERR: [chars]

Explanation EST has detected an internal error.

Recommended Action No action is required.

Error Message

%NP_EST-6-RUNTIME_ERR_NTF: [chars]

Explanation An EST run-time error notification has been sent to Cisco IOS software system to convey additional debug data that may help to identify the cause of the run-time error.

Recommended Action No action is required.

Error Message

%NP_MD-3-BADENCAP: Unknown encapsulation [dec] on interface [chars]

Explanation A software error has occurred and has resulted in an unknown encapsulation type on the specified interface.

Error Message

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

Explanation A software error has occurred and has caused an unexpected packet to be set up for transmission and then dropped by the NextPort modem driver.

Error Message

%NP_MD-3-DATA_CHAN_RX_OVERFLOW: Too many buffers ([dec]) rxd for port [dec]

Explanation The NextPort module sent more buffers than are allowed for the specified channel.

Error Message

%NP_MD-3-DATA_QUEUE_SEND_FAIL: Could not send to data queue for port [dec], inflight tx buffers [dec]

Explanation The NextPort modem driver could not send a buffer to the interface driver.

Error Message

%NP_MD-3-MODEM_SLOT_CREATION_FAIL: Modem slot structure for slot [dec] could not be created

Explanation The NextPort modem driver could not create the modem slot structure that is required for the modem services of the specified card.

Error Message

%NP_MD-6-MODULE_DOWN: NextPort module [dec]/[dec]/[dec] down

Explanation The NextPort modem driver has detected a module going down.

Recommended Action No action is required.

Error Message

%NP_MD-6-MODULE_UP: NextPort module [dec]/[dec]/[dec] up

Explanation The NextPort modem driver has detected a module coming up.

Recommended Action No action is required.

Error Message

%NP_MD-0-NOHWIDBS: Cannot allocate interface Async[dec]/[dec]

Explanation An allocation of interface structure has failed. Either there is not enough memory or the maximum number of interfaces has been exceeded.

Error Message

%NP_MD-0-NOMEMORY: Cannot allocate [dec] bytes of memory for [chars]

Explanation The system has failed to allocate an important data structure because of a lack of memory.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show mem 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 mem output, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%NP_MD-0-NO_MODULE_ELEMENTS: Cannot bring up the module [dec]/[dec]/[dec] due to lack of module elements

Explanation The NextPort modem driver cannot allocate an important data structure, called module element, which is necessary to bring up the module. The inability to call up the module element normally should not happen and may indicate an error condition.

Error Message

%NP_MD-0-NOPAKS: TTY [chars]: Cannot allocate [chars]

Explanation An important buffer cannot be allocated because of the shortage of packet memory.

Error Message

%NP_MD-3-NO_SEED_BUFFER: No buffer to seed data queue for module [dec]/[dec]/[dec]

Explanation The NextPort modem driver could not obtain a buffer while trying to seed the module data queue because of a shortage of packet memory.

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

%NP_MD-0-NO_SUCH_LINE: Attempt to [chars] a data channel on the unexisting line [dec]/[dec]

Explanation An internal software error that probably resulted in a corrupted modem database has occurred.

Error Message

%NP_MD-0-NO_SUCH_MODEM: Attempt to [chars] a data channel on the unexisting modem [dec]/[dec]

Explanation An internal software error that probably resulted in a corrupted modem database has occurred.

Error Message

%NP_MD-0-NO_SUCH_SLOT: Slot [dec] is not present in the system

Explanation An internal software error that possibly resulted in a corrupted slot database has occurred.

Error Message

%NP_MD-0-NOTTYS: Cannot allocate TTY[dec] ([dec]/[dec])

Explanation An allocation of a tty structure has failed. Either there is not enough memory or the tty number is too big.

Error Message

%NP_MD-3-NOTXPAK: Static transmit paktype unavailable

Explanation A software structure was found in an unexpected state during the run-time for the specified modem.

Error Message

%NP_MD-3-RETURN_DATA_BUFF_FAIL: Failed to return data buffer for port [dec]

Explanation A call to the NextPort modem driver to replenish the data buffer for this channel has failed.

Error Message

%NP_MD-3-RTSLOW: TTY [chars]: RTS is deasserted though rx queue is empty

Explanation A software error that resulted in an invalid state for the Request to Send (RTS) modem signal has occurred.

Error Message

%NP_MD-3-SEED_BUFFER_FAIL: Could not seed data queue for module [dec]/[dec]/[dec]

Explanation The NextPort modem driver could not seed the data queue with buffers.

Error Message

%NP_MD-0-SLOT_ALREADY_PRESENT: Slot [dec] is already present in the system

Explanation An internal software error that may have resulted in a corrupted slot database has occurred.

Error Message

%NP_MD-6-SLOT_INSERTED: Slot [dec] ([dec] ports max) inserted

Explanation The NextPort modem driver has detected a slot being inserted in the system. During the startup process, all slots that are present in the system are treated as being inserted.

Recommended Action No action is required.

Error Message

%NP_MD-6-SLOT_REMOVED: Slot [dec] removed

Explanation A slot has been removed from the system.

Recommended Action No action is required.

Error Message

%NP_MD-3-TX_INBAND_MSG_FAILURE: Failed to send inband message for TTY [chars]

Explanation A call to send an in-band message on the specified data queue has failed.

Error Message

%NP_MD-3-TXQUEUE_EMPTY: TTY [chars]: No buffers available to set up the transmit queue

Explanation A software error has occurred and has resulted in an unexpected exhaustion of the pool of data buffers that are used by the modem drivers.

Error Message

%NP_MD-1-UNKNOWN_ESCAPE_CHAR: TTY [chars]: Attempt to set an unknown special character (type [dec]) to [hex]

Explanation The NextPort modem driver has received a request for the hardware detection of an unknown type of special character that has resulted from an internal software error.

Error Message

%NP_MD-3-UNKNOWN_INBAND: TTY [chars]: Unknown NextPort in-band message (msg_id [hex]) received

Explanation The NextPort modem driver has received an unknown message from a NextPort module. Unknown messages may be received when new firmware is used with an older version of Cisco IOS software.

Error Message

%NP_MM-3-COUNTRY_CODE_FAILURE: Module country code failure [dec]/[dec]/[dec]

Explanation The NextPort Module Manager has failed to set the country code.

Error Message

%NP_MM-3-DATA_Q_FAILED: Failed to create Data Q for NP module [dec]/[dec]/[dec]

Explanation The NextPort Module Manager has failed to create the data queue.

Error Message

%NP_MM-3-INVALID_ACK_RSP: Unsupported module ACK response [dec]/[dec]/[dec]: msg len = [dec], session ID = [dec], msg tag = [dec], msg ID = [dec], cmd msg ID = [dec], result code = [dec]

Explanation The NextPort Module Manager has received an unsupported message response.

Error Message

%NP_MM-3-INVALID_NPADDRESS: Invalid NP_ADDRESS [dec]/[dec]/[dec]/[dec] - [chars]

Explanation The NextPort Module Manager has detected an invalid NP_ADDRESS.

Error Message

%NP_MM-3-INVALID_RSP: Unsupported module response [dec]/[dec]/[dec]: msg len = [dec], session ID = [dec] msg tag = [dec], msg ID = [dec]

Explanation The NextPort Module Manager has received an unsupported message response.

Error Message

%NP_MM-3-INVALID_STATE: Invalid NP module state([chars]) [dec]/[dec]/[dec] - [chars]

Explanation The NextPort (NP) Module Manager has detected an invalid NP module state.

Error Message

%NP_MM-3-MEM_ERR: Failed to allocate control message buffer for NP module [dec]/[dec]/[dec] - [chars]

Explanation The NextPort Module Manager has failed to allocate a control message buffer.

Error Message

%NP_MM-3-MODULE_CRASH: Module Crash detected [dec]/[dec]/[dec]: state = [dec], cause code = [dec]

Explanation The NextPort Module Manager has detected a failed module.

Error Message

%NP_MM-3-RESTART_EXCEEDED: Module exceeded restart threshold [dec]/[dec]/[dec]

Explanation The NextPort Module has exceeded the restart threshold.

Error Message

%NP_MM-3-RUNTIME_ERR: Module Run Time Error [dec]/[dec]/[dec] : recovery = [hex], error = [hex]

Explanation The NextPort Module Manager has received a module run-time error.

Error Message

%NP_MM-3-SEND_FAILED: Failed to send [chars] message to NP module [dec]/[dec]/[dec]

Explanation The NextPort Module Manager has failed to send a control message.

Error Message

%NP_SPE_DS-3-SPE_DNLD_FAIL: SPE [dec]/[dec]/[dec]/[dec]: [chars]

Explanation The Service Processing Element (SPE) download code has failed, and the download has been aborted.

Recommended Action No action is required.

Error Message

%NP_SPE_DS-3-SPE_DNLD_INIT_FAIL: [chars]

Explanation The Service Processing Element (SPE) download code has failed to initialize, and the SPE download will fail.

Recommended Action No action is required.

Error Message

%NP_SSM-3-INVALID_HANDLE: SSM([dec]/[dec]): Invalid Session/Service Instance Handle

Explanation The NextPort Session and Service Manager has failed to obtain its instance handle for the specified slot and port.

Recommended Action No action is required.

Error Message

%NP_SSM-3-INVALID_MSG: SSM: Invalid Session/Service Message, ID = [hex]

Explanation The NextPort Session and Service Manager has received an invalid message from the NextPort Message Dispatcher.

Recommended Action No action is required.

Error Message

%NP_SSM-6-NULL_SSM_INFO: NULL SSM Info Handle for slot [dec], port [dec]

Explanation The NextPort Session and Service Manager has failed to obtain a control information handle for the specified slot and port numbers.

Error Message NextPort

%NP_SSM-6-NULL_VDEV_COMMON: NULL Vdev Common Handle for slot [dec], port [dec]

Explanation The NextPort Session and Service Manager has failed to obtain a Voice Device information handle for the specified slot and port numbers.

Error Message NextPort

%NP_SSM-3-RUNTIME_ERROR: SSM([dec]/[dec]): Session Runtime Error Code = [dec], Recovery Action = [dec]

Explanation The Session and Service Manager has received a run-time error for the specified slot and port.

Recommended Action No action is required.

Error Message

%NSP-3-BOGUS_PARAMETER: Bogus parameter passed: [chars] [dec]

Explanation An internal software error has occurred. The parameter passed to the routine is invalid.

Error Message

%PAD-3-GETLINE: Tty%t, bad return code [dec] from x3_getline()

Explanation An internal software error has occurred.

Error Message

%PAD-2-PUTSETUP: Tty%t, buffer already setup

Explanation An internal software error has occurred.

Error Message

%PARSER-4-INVLDLINE: Invalid line in NV generation: %t

Explanation The parser has failed an internal software check.

Error Message

%PIM-1-INVALID_SRC_REG: Received Register from [int] for ([int], [int]), not willing to be RP, MSGDEF_LIMIT_GLACIAL

Explanation A Protocol-Independent Multicast (PIM) router that is configured as a rendezvous point has 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

%PIM-5-REG_ENCAP_INVALID: Bad register from [int] for ([int], [int]). Trace = [hex] [hex], MSGDEF_LIMIT_MEDIUM

Explanation A Protocol-Independent Multicast (PIM) router that is configured as a rendezvous point or configured with a network address translation (NAT) has received a PIM register packet from another PIM router. The data encapsulated in this packet is invalid.

Recommended Action No action is required.

Error Message

%PIM-5-SA_ENCAP_INVALID: Bad SA from RP [int] for ([int], [int]). Trace = [hex] [hex], MSGDEF_LIMIT_MEDIUM

Explanation A Protocol-Independent Multicast (PIM) router that is configured as an Multicast Source Discovery Protocol (MSDP) peer has received Source-Active (SA) message with encapsulated data. The data encapsulated in this packet is invalid.

Recommended Action No action is required.

Error Message

%PM_MODEM_HIST-7-CSM_IC_CALLED_NUM: [chars]: ISDN incoming called number: [chars]

Explanation A tracing message that shows the number of the ISDN line receiving a call has been received.

Recommended Action This is a debug message only. No action is required.

Error Message

%PM_MODEM_HIST-7-CSM_IC_CALLING_NUM: [chars]: ISDN incoming caller number: [chars]

Explanation A tracing message that shows the number of an incoming ISDN caller has been received.

Recommended Action This is a debug message only. No action is required.

Error Message

%PM_MODEM_HIST-7-CSM_OC_CALLED_NUM: [chars]: ISDN outgoing called number: [chars]

Explanation A tracing message that shows a dialed ISDN number has been received.

Recommended Action This is a debug message only. No action is required.

Error Message

%PM_MODEM_HIST-7-MODEM_DYNAMIC_EVT: [chars]: [chars] [chars]

Explanation A tracing message that contains information about a dynamic event that was reported by the specified modem has been received.

Recommended Action This is a debug message only. No action is required.

Error Message

%PM_MODEM_HIST-7-MODEM_END_CONN_EVT: [chars]: [chars] [chars]

Explanation A tracing message that contains information about an end connection event from the specified modem has been received.

Recommended Action This is a debug message only. No action is required.

Error Message

%PM_MODEM_HIST-7-MODEM_ROS_EVT: [chars]: [chars] [chars]

Explanation A tracing message that contains information about a link rate event that was reported by the specified modem has been received.

Recommended Action This is a debug message only. No action is required.

Error Message

%PM_MODEM_HIST-7-MODEM_STATE_EVT: [chars]: [chars] [chars] State: [chars]

Explanation A tracing message that contains information about a state event that was reported by the specified modem has been received.

Recommended Action This is a debug message only. No action is required.

Error Message

%PM_MODEM_HIST-7-MODEM_STATIC_EVT: [chars]: [chars] [chars]

Explanation A tracing message that contains information about a static event that was reported by the specified modem has been received.

Recommended Action This is a debug message only. No action is required.

Error Message

%PM_MODEM_HIST-7-PORT_STATE_REACHED_NTF_EVT: [chars]: [chars] [chars]

Explanation A tracing message that contains information about a link rate event that was reported by the specified modem has been received.

Recommended Action This is a debug message only. No action is required.

Error Message

%PM_MODEM_HIST-7-TRACE_HDR: Modem [chars] Events Log:

Explanation An initial message that confirms the trace of the specified modem has been received. The stored trace messages of the modem will follow.

Recommended Action This is a debug message only. No action is required.

Error Message

%PM_MODEM_HIST-7-UNKNOWN_EVENT: [chars]: Error in events log

Explanation A tracing message that reports a formatting error in the modem event history has been received. One or more events may be missing from the trace.

Recommended Action This is a debug message only. No action is required.

Error Message

%PM_MODEM_HIST-7-UNKNOWN_FRAME: [chars]: Error in events log

Explanation A tracing message that reports a formatting error in the modem event history has been received. One or more events may be missing from the trace.

Recommended Action This is a debug message only. No action is required.

Error Message

%PM_MODEM_MAINT-4-B2BABORT: Modems ([chars]) and ([chars]) back-to-back test: aborted

Explanation A tracing message that reports that a back-to-back test failed between the two specified Modem ISDN channel aggregation (MICA) modems has been received.

Recommended Action Perform more back-to-back tests by pairing the failed modems with other modems to determine which modem is defective. Check the failed modems again after performing a power cycle. If the message recurs, copy the error message exactly as 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

%PM_MODEM_MAINT-5-B2BCONNECT: Modems ([chars]) and ([chars]) connected in back-to-back test: [chars]

Explanation A back-to-back test connection has been made between the selected modems. The test is still in progress.

Recommended Action No action is required.

Error Message

%PM_MODEM_MAINT-5-B2BINIT: Auto Back-to-Back test initiated by [chars]

Explanation An automatic back-to-back test has been initiated by the specified Modem ISDN channel aggregation (MICA) modem.

Recommended Action This is a debug message only. No action is required.

Error Message

%PM_MODEM_MAINT-5-B2BMODEMS: Modems ([chars]) and ([chars]) completed back-to-back test: success/packets = [dec]/[dec]

Explanation The specified modems have passed the back-to-back test without any errors.

Recommended Action No action is required.

Error Message

%PM_MODEM_MAINT-1-BADEVENT: Invalid modem management [chars] event [hex] for modem([chars])

Explanation The modem management facility has received an unrecognized event.

Error Message

%PM_MODEM_MAINT-1-BADMODEM: Modem ([chars]) failed [chars]

Explanation A software or hardware problem has been detected on a modem. The specific modem and problem are listed in the message.

Error Message

%PM_MODEM_MAINT-4-BADMODEMS: Modems ([chars]) and ([chars]) failed back-to-back test: [chars]

Explanation The two modems reported in the message have failed a back-to-back test. At least one modem is defective.

Error Message

%PM_MODEM_MAINT-1-INITFAIL: Initialization failed.

Explanation A modem maintenance facility initialization has failed.

Recommended Action Disable the autotest as well as the power-on test, and do not start a manual back-to-back test. Copy the error message exactly as 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

%PM_MODEM_MAINT-5-MODEM_OK: Modem ([chars]) passed the test

Explanation Tests on the specified modem were successful.

Recommended Action No action is required.

Error Message

%PORT-6-NULL_OBJ: Port object [chars] is unavailable.

Explanation Information about the specified port could not be retrieved. The port may not exist.

Recommended Action No action is required.

Error Message

%PORT-6-PORT_RECOVERY: [chars] [chars]

Explanation Port recovery has been triggered. Configured action will take place on the port.

Recommended Action No action is required.

Error Message

%PORT-6-SESSION_RECOVERY: [chars] [chars] [dec]

Explanation The session recovery has an invalid cause code.

Recommended Action No action is required.

Error Message

%PORT-6-SM_PORT_CLEARED: [chars]

Explanation The ports will be reset, and any active calls on these ports will be terminated.

Recommended Action No action is required.

Error Message

%RADIUS-3-ALLDEADSERVER: Group [chars]: No active radius servers found. Id [dec].

Explanation No responsive RADIUS servers were found.

Recommended Action Check the network connectivity to the RADIUS servers, and ensure that the servers are running.

Error Message

%RADIUS-6-SERVERALIVE: Group [chars]: Radius server [int]:[dec], [dec] is responding again (previously dead).

Explanation A RADIUS server that was previously inactive has started responding again.

Recommended Action No action is required.

Error Message

%RADIO-4-BAD_IF_PIC: Radio[dec]/0, bad IF PIC version ([dec]) on IDU

Explanation A hardware configuration may be incorrect.

Error Message

%RADIO-4-BAD_RF_PIC: Radio[dec]/0, bad RF PIC version ([dec]) on ODU [dec]

Explanation A hardware configuration may be incorrect.

Error Message

%RADIO-4-CHECKSUM_ERR: Radio[dec]/0, radio phy eeprom [chars] checksum (stored:0x[hex], calculated:0x[hex])

Explanation The checksum error is probably caused by the shut or no shut command.

Recommended Action Enter the no shut command.

Error Message

%RADIO-5-CLEAR_METRICS: Radio[dec]/0, link metrics cleared

Explanation A user requested the link metrics to be cleared.

Recommended Action No action is required.

Error Message

%RADIO-5-CONFIG_HW: Radio[dec]/0, hardware does not support requested configuration: [chars]

Explanation A hardware configuration may be incorrect.

Recommended Action Change the configuration to match the hardware.

Error Message

%RADIO-5-CONFIG_MISMAT: Radio[dec]/0, invalid or inconsistent configuration requested [chars]

Explanation This error message probably resulted from automatic repeat request (ARQ) settings that are not supported by the current radio channel parameters.

Recommended Action Use the radio arq reset command to change the ARQ settings to allowed values, given the current radio channel parameters.

Error Message

%RADIO-4-DSPHPITIMEOUT: Radio[dec]/0, HPI timeout while attempting to access DSP [chars]

Explanation A digital signal processor (DSP) on the RADIO line card was not granting access to its memory. This error message was probably caused by a DSP firmware internal error.

Error Message

%RADIO-4-DSPINDERR: Radio[dec]/0, Error processing indication from DSP [chars] ([chars]:[dec])

Explanation A DSP on the RADIO line card generated an indication message that could not be processed. Messages are not processed when the router is operating under a severe traffic load.

Error Message

%RADIO-4-DSPSPURRESP: Radio[dec]/0, spurious DSP response from [chars]: [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]

Explanation A DSP on the RADIO line card generated a response message unexpectedly. Messages are not processed when the router is operating under severe traffic load.

Error Message

%RADIO-4-DSPULOFLOW: Radio[dec]/0, uplink message queue overflow reported by DSP [chars]

Explanation At least one DSP-to-router message was lost because the uplink queue of that digital signal processor (DSP) was full. DSP-to-router messages can be lost when many thresholds, histograms, and time lines are being triggered or expiring at the same time.

Recommended Action Change the thresholds and reduce histogram or time line usage to decrease the load on the system.

Error Message

%RADIO-4-FPGADONEPINLOW: Radio[dec]/0, DONE pin on FPGA [chars] did not assert after downloading

Explanation The DONE pin of an field-programmable gate array (FPGA) device on the RADIO line card did not assert after the downloading of the device. This error message probably indicates an existing or developing hardware failure.

Error Message

%RADIO-4-FPGAINITPINHIGH: Radio[dec]/0, INIT pin on FPGA [chars] asserted during downloading

Explanation The INIT pin of a field-programmable gate array (FPGA) device on the RADIO line card asserted midway through the downloading of the device. The most likely cause of this error is a corrupted FPGA image.

Error Message

%RADIO-4-FPGAINITPINLOW: Radio[dec]/0, INIT pin on FPGA [chars] not asserted when PROG pin asserted

Explanation The INIT pin of a field-programmable gate array (FPGA) device on the RADIO line card did not assert when the PROG pin was asserted. The most likely cause of this error is either a faulty FPGA device or software problem that resulted from resetting a faulty FPGA device.

Error Message

%RADIO-4-IF_COMM: Radio[dec]/0, IDU IF internal serial communication error - [chars]

Explanation An internal serial communication error has occurred. The most likely cause of this error is a loose IF baby board.

Recommended Action Replace the loose IF baby board.

Error Message

%RADIO-4-IF_OSC: Radio[dec]/0, Internal [chars] Oscillator out of Lock [chars]

Explanation A hardware error has occurred. The most likely cause of this error is vibration or hardware failure.

Recommended Action Replace the internal card.

Error Message

%RADIO-5-IMAGE_BAD_CRC: [chars][dec]/[dec], detected a bad CRC while downloading image [chars] to chip [chars]

Explanation An internal software error has occurred. The most likely cause of this error is a protocol error while downloading.

Recommended Action If the download is a Trivial File Transfer Protocol (TFTP) download, try it again. If the error recurs, call your Cisco technical support representative.

Error Message

%RADIO-6-IMAGE_NOT_FOUND: [chars][dec]/[dec], could not find image [chars] for chip [chars]

Explanation An internal software error has occurred. The most likely cause of this error is an incorrectly typed URL for the image.

Recommended Action Enter the correct URL.

Error Message

%RADIO-5-IMAGE_TIMEOUT: [chars][dec]/[dec], timeout trying to open image [chars] for chip [chars]

Explanation An internal software error has occurred. The most likely cause of this error is a protocol error that occurred while the image was being opened.

Recommended Action If the download is a Trivial File Transfer Protocol (TFTP) download, try it again. If the error recurs, call your Cisco technical support representative.

Error Message

%RADIO-5-LOCAL_IN_SYNC: Radio[dec]/0, Link synchronization acquired

Explanation The physical layer has successfully acquired the link.

Recommended Action No action is required.

Error Message

%RADIO-5-LOCAL_NO_CW: Radio[dec]/0, Still trying to establish link (validate codeword)

Explanation An internal software error has occurred. The most likely cause of this error is that the remote system is not sending on the correct frequency.

Recommended Action Enter the no shut command for the remote system.

Error Message

%RADIO-5-LOCAL_NO_FREQ: Radio[dec]/0, Still trying to establish link (frequency sync)

Explanation An internal software error has occurred. The most likely cause of this error is that the remote system is not sending on the correct frequency.

Recommended Action Enter the no shut command for the remote system.

Error Message

%RADIO-5-LOCAL_NO_SYNC: Radio[dec]/0, Still trying to establish link (timing sync)

Explanation An internal software error has occurred. The most likely cause of this error is that the remote system is not sending on the correct timing frequency.

Recommended Action Enter the no shut command for the remote system.

Error Message

%RADIO-5-LOCAL_NO_TRANSMIT: Radio[dec]/0, ODU saftey interlock is preventing transmission. Check ODU and cables. [chars]

Explanation An internal software error has occurred. The most likely cause of this error is an unattached cable or an overheated Outdoor unit (ODU).

Recommended Action Check the ODU and cables.

Error Message %RADIO-5-LOCAL_NO_VITERBI: Radio[dec]/0, Still trying to establish link (viterbi sync)

Explanation An internal software error has occurred. The most likely cause of this error is that the remote system is not sending on the correct frequency.

Recommended Action Enter the no shut command for the remote system.

Error Message

%RADIO-5-METRICS_THRESH: Radio[dec]/0, [chars] per [chars] threshold met([dec]=[dec])

Explanation An internal software error has occurred. The most likely cause of this error is a misaligned antenna.

Recommended Action Realign the antenna.

Error Message

%RADIO-4-NEWER_IF_EEPROM: Radio[dec]/0, Unsupported IF PIC major eeprom version ([int]) on IDU

Explanation The Cisco IOS software should be upgraded to support the new EEPROM.

Error Message

%RADIO-4-NEWER_RF_EEPROM: Radio[dec]/0, Unsupported RF PIC major eeprom version ([int]) on ODU [dec]

Explanation The Cisco IOS software should be upgraded to support the new EEPROM.

Error Message

%RADIO-4-NO_HWCAP_FIELD: Radio[dec]/0, could not find HW Capabilities field in IDPROM

Explanation An internal software error has occurred. The most likely cause of this error is an improperly programmed IDPROM.

Recommended Action Reprogram the IDPROM on the line card.

Error Message

%RADIO-4-NO_IMAGE: [chars][dec]/[dec], Chip [chars]: failed to find image given current configuration

Explanation An internal software error has occurred. The most likely cause of this error is that the configuration uses external files.

Recommended Action Change the configuration to use internal files.

Error Message

%RADIO-4-PHY_REQ: Radio[dec]/0, link synchronization [chars]

Explanation An internal software error has occurred. The most likely cause of this error is a loose Outdoor unit (ODU) cable.

Recommended Action Check the ODU cables.

Error Message

%RADIO-5-PHY_RETRY: Radio[dec]/0, event %23s in state %15s

Explanation An internal software error has occurred. The most likely cause of this error is an incorrect configuration.

Recommended Action Review the configuration and hardware capabilities.

Error Message

%RADIO-4-PHY_SYNC_FAIL: Radio[dec]/0, link synchronization [chars]

Explanation An error has occurred. The most likely cause of this error is a loose Outdoor unit (ODU) cable.

Recommended Action Check the ODU cables.

Error Message

%RADIO-5-PHY_SYNC_LOST: Radio[dec]/0, Lost link. Check remote transmitter

Explanation An internal software error has occurred. The most likely cause of this error is a remote system that is not sending.

Recommended Action Enter the no shut command for the remote system.

Error Message

%RADIO-4-PHY_SYNC_OK: Radio[dec]/0, link synchronization acquired

Explanation An internal software error has occurred. The most likely cause of this error is that the no shut command was entered.

Recommended Action No action is required.

Error Message

%RADIO-4-PHY_SYNC_REOK: Radio[dec]/0, link synchronization re-acquired

Explanation An internal software error has occurred. The most likely cause of this error is that the no shut command was entered on the remote end.

Recommended Action No action is required.

Error Message

%RADIO-5-REMOTE_LOST_SYNC: Radio[dec]/0, Remote end reports: [chars]

Explanation Ahardware error has occurred. The most likely cause of this error is an unattached cable or an overheated Outdoor unit (ODU).

Recommended Action Check the ODU cables.

Error Message

%RADIO-5-REMOTE_NO_SYNC: Radio[dec]/0, Remote end reports: Unable to acquire link synchronization

Explanation A hardware error has occurred. The most likely cause of this error is an unattached cable or an overheated Outdoor unit (ODU).

Recommended Action Check the ODU cables.

Error Message

%RADIO-4-RF_AGC: Radio[dec]/0, ODU [dec] max transmitter power exceeded [chars]

Explanation An internal software error has occurred.

Recommended Action Replace the radio frequency (RF) Outdoor unit (ODU).

Error Message

%RADIO-4-RF_ANTENNA: Radio[dec]/0, ODU [dec] is [chars]

Explanation A hardware error has occurred. The most likely cause of this error is a disconnected cable.

Recommended Action Check or replace the cable from the UBR to the Outdoor unit (ODU).

Error Message

%RADIO-4-RF_COMM: Radio[dec]/0, ODU [dec] serial communication error - [chars]

Explanation A hardware error has occurred. The most likely cause of this error is a disconnected cable.

Recommended Action Check or replace the cable from the UBR to the Outdoor unit (ODU).

Error Message

%RADIO-4-RF_OSC: Radio[dec]/0, ODU [dec] [chars] Oscillator out of Lock [chars]

Explanation A hardware error has occurred. The most likely cause of this error is vibration or hardware failure.

Recommended Action Replace the electronics on the Outdoor unit (ODU).

Error Message

%RADIO-2-RF_OVERTEMP: Radio[dec]/0, ODU [dec]: over temperature [chars]

Explanation A hardware error has occurred. The most likely cause of this error is hardware failure or solar heating.

Recommended Action Keep the radio frequency (RF) Outdoor unit (ODU) cool.

Error Message

%RADIO-4-RF_TEMP: Radio[dec]/0, ODU [dec]: temperature is [dec] degrees C, threshold is [dec] degrees C

Explanation A hardware error has occurred. The most likely cause of this error is hardware failure or solar heating.

Recommended Action Keep the radio frequency (RF) Outdoor unit (ODU) cool.

Error Message

%RADIO-4-RF_VOLT: Radio[dec]/0, ODU [dec]: supply voltage out of range [chars]

Explanation A hardware error has occurred.

Recommended Action Replace the radio frequency (RF) Outdoor unit (ODU).

Error Message

%RADIO-3-SELF_TEST_FAILED: Radio[dec]/0, failed self-test

Explanation A hardware error has occurred.

Error Message

%RADIO-6-SELF_TEST_SUCCESS: Radio[dec]/0, self-test successful

Explanation The system has passed a self-diagnostic test.

Recommended Action No action is required. Passing the self-diagnostic test is a desired result.

Error Message

%RADIO-5-THRESHOLD: Radio[dec]/0, [chars] [chars] threshold crossed ODU [dec]

Explanation An internal software error has occurred. The most likely cause of this error is a user-defined threshold.

Recommended Action No action is required.

Error Message

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

Explanation A system or hardware failure has occurred.

Recommended Action Replace the line card.

Error Message

%RADIO_DRIVER-3-DMADESCSEQERR: DMAC detected a descriptor sequence error (DMAC Status Register is 0x[hex])

Explanation An internal software error has occurred.

Error Message

%RADIO_DRIVER-3-LOCALBUSERR: A line card local bus error, error status 0x[hex], error address 0x[hex]

Explanation A device on the RADIO line card local bus either did not respond to a selection, timed out once selected, or issued an error while selected. This action probably indicates an existing or developing hardware failure.

Error Message

%RADIO_DRIVER-3-NOTRADIO: Device reported [hex]

Explanation A hardware error has occurred.

Recommended Action Replace the defective hardware.

Error Message

%RADIO_DRIVER-3-PCIPERROR: DMAC reported PCI parity error (DMAC Status Reg: 0x[hex])

Explanation A parity error has occurred on the protocol control information (PCI) bus while the RADIO direct memory access (DMA) controller was performing a read/write operation. This parity error probably indicates an existing or developing hardware failure.

Error Message

%RADIO_DRIVER-3-PCITARGETABORT: Device received a PCI Target Abort (DMAC Status Register is 0x[hex])

Explanation When attempting a protocol control information (PCI) master read/write operation, the target issued an abort to the direct memory access (DMA) controller. This error usually indicates that an incorrect target was selected, and in this case it means that shared packet memory was not the target. This is likely a software error causing the RADIO destination MAC (DMAC) to access an invalid target.

Error Message

%RADIUS-3-SECRETDEFINEFAILED: Key definition ignored.

Explanation The user is attempting to store either a corrupted shared secret or memory allocation that has failed during the secret definition. Any existing shared secret will be preserved.

Recommended Action Configure an appropriate secret.

Error Message

%RAIKO-3-BAD_MGMT_INT_HNDLR_CB_REG: Slot [dec]: Mgmt int. handler's registration routine was passed NULL callback address(es) -- enabler=[hex], handler=[hex]; registering party's callback details ignored

Explanation A management level interrupt handler has been registered incorrectly with device-independent code. A software fix is required.

Error Message

%RAIKO-3-BRIDGE_PCI_ERROR: Slot [dec]:DFC [dec] ERROR [chars]

Explanation A protocol control information (PCI) error has occurred during an attempt to access a Dial Feature Card (DFC). The DFC has been shut down.

Recommended Action Replace the DFC.

Error Message

%RAIKO-3-DFC_ID_ZERO: Slot [dec]: id of DFC[int] is invalid (zero); cookie probably unprogrammed

Explanation When the cookie on the specified Dial Feature Card (DFC) was read for the ID of the DFC, an invalid value of 0 was returned. The invalid value indicates that the cookie on the DFC has not been programmed properly.

Recommended Action Reprogram the cookie on the DFC.

Error Message

%RAIKO-3-MGMT_INT_HNDLR_INST_FAILED: Slot [dec]: installation of desired Mgmt interrupt handler failed -- no routine is currently installed at IOS Level [dec]

Explanation An attempt to install the required management interrupt handler at the specified Cisco IOS level has failed.

Error Message

%RAIKO-3-MGMT_INT_UNCLAIMED: Slot [dec]: a Mgmt interrupt occurred but was not processed by a device-specific handler; following sources masked out: [chars]

Explanation A source of management level interrupts does not have a handler registered for it. A software fix is needed to install the proper handler.

Error Message

%RAIKO-3-NO_MGMT_INT_HNDLR_CB_ENTRY: Slot [dec]: no free Mgmt int. handler callback entries (all [dec] in use); registering party's callback details dropped

Explanation More management interrupt handlers have registered than can be managed; a software fix is required.

Error Message

%RAIKO-3-UNEXPECTED_MGMT_INT_HNDLR: Slot [dec]: installation of Mgmt int. handler apparently failed -- routine currently installed at IOS Level [dec] is [hex]

Explanation An attempt to install the required management interrupt handler at the specified Cisco IOS level has failed because, upon checking, another handler was found there.

Error Message

%RPM-4-NOCPUVER: Invalid CPU ID, assuming revision 1

Explanation The CPU ID could not be read from the EEPROM. The most likely cause of this error is a hardware failure.

Error Message

%RPM_VIRTUAL_PORT-3-CLRALLCNF_DELETE_FILE: ERROR: clrAllCnf --- Fail to delete clrAllCnf file on PXM C: disk ... Please delete file manually by doing delete c:auto_config_slot[dec].

Explanation The reconfiguration request to Processor Switching Module (PXM) has failed, timed out, or been rejected by PXM.

Recommended Action No action is required. In the case of failure or timeout, the state of the connection will be set to TIMEOUT, and the resynchronization process will periodically attempt to update PXM. If the request had been rejected by PXM, the connection state will be set to FAILED until the connection is deleted or reconfigured.

Error Message

%RS_TDM-3-TDM_BACKPLANE_CLASH: Clash in usage for TDM backplane timeslot [dec]

Explanation The time-division multiplexing (TDM) backplane time slot to be allocated is already in use.

Recommended Action Check the split dial shelf settings on both router shelves for conflicting settings.

Error Message

%RS_TDM-3-TDM_CONFLICT: TDM split user setting are in conflict: my RS [chars] = [dec], other RS [chars] = [dec]

Explanation The user setting for the time-division multiplexing (TDM) split on this router shelf is in conflict with the setting on the other router. More backplane DS0 settings are in use than the allowed maximum of 2048 DS0s.

Recommended Action Set the other router dial shelf split backplane DS0 to another setting within the range.

Error Message

%RS_TDM-3-TDM_EXTEND_CLASH: TDM extended split on Router shelf Clashes to my [chars] other [chars] extended backplane ds0

Explanation The time-division multiplexing (TDM) extended split backplane DS0 for this router conflicts with the extended backplane DS0 of another router shelf.

Error Message

%RS_TDM-3-TDM_LEG_CLASH: TDM legacy split on Router shelf Clashes to my [dec] other [dec] legacy backplane ds0

Explanation The number of legacy backplane DS0s for the specified router shelf conflicts with the number of legacy backplane DS0s on the other specified router shelf.

Error Message

%RS_TDM-3-TDM_NOT_SPLIT_PAIR: TDM split user setting are not matched pairs my RS [chars] = [dec] ds0, expected other RS [chars] = [dec] ds0, actual other RS [chars] = [dec] ds0

Explanation The user setting for the time-division multiplexing (TDM) split on the specified router shelf is not compatible with the TDM split setting on the other specified router shelf.

Recommended Action Set the other router dial shelf split backplane DS0 to the same setting.

Error Message

%RS_TDM-3-TDM_REDUCED_TDM_SPLIT: TDM split on [chars] Router shelf Reduced to [dec] backplane ds0

Explanation The number of backplane DS0s for this router has been forced to a lower number.

Error Message

%RS_TDM-3-TDM_UNKNOWN_TS_STATE: TDM backplane timeslot [dec] is in an unknown state

Explanation The specified time-division multiplexing (TDM) backplane time slot is in an unknown state.

Recommended Action Check the split dial shelf settings on both router shelves for conflicting settings.

Error Message

%SIGSM-1-EVENT_ERR: Unexpected event

Explanation An error in the signaling state machine has occurred.

Error Message

%SIGSM-1-NO_TEMPLATE_ERR: No static template found for slot [dec] port [dec] with parameters provided

Explanation The system could not find a matching static template that has the same parameters as those used by the controller.

Error Message

%SGBP-3-UNEXP: MQ [chars] from [int] for query [dec]:[dec], bundle [chars], bid [dec], state [chars]

Explanation This message is generated only when Stack Group Bidding Protocol (SGBP) error debugging is enabled. The SGBP connection has entered an unexpected state, possibly because of a software error.

Error Message

%SNASW-3-BAD_MSG_NAME: Invalid message name specified for sna sw msg-trap

Explanation An invalid message name was entered for the snasw msg-trap command.

Recommended Action Reissue the command with a valid message name.

Error Message

%SNASW-4-CPUUsage: SNASw process, type 0x[hex] ran for more than %lu ms processing IPS of type 0x[hex]

Explanation A process within the SNA switch has run for an unexpectedly long time.

Error Message

%SNASW-4-CPUUsage: SNASw process, type [hex] ran for [int] ms processing IPS of type [hex], address [hex]

Explanation (Cisco IOS Release 12.1(3)T message) A process within the SNA switch has run for an unexpectedly long time.

Error Message

%SNASW-4-DLUR_LOG_21: EXCEPTION - %lu - Different PUs have LUs whose names clash [chars]

Explanation Two logical units (LUs) of the same name exist under different physical units (PUs). One LU is already activated, and Dependent LU Server (DLUS) has attempted to activate the second LU. The second LU will not be activated.

Recommended Action Rename one of the LUs with a unique network name.

Error Message

%SNASW-3-TRACE_2: Resizing of [chars] buffer failed due to insufficient memory; using buffer-size of [dec]K.

Explanation A cyclic trace buffer could not be resized because of insufficient memory. The previously allocated buffer, if one exists, will continue to be used.

Recommended Action Reconfigure a smaller buffer size for the specified buffer type.

Error Message

%SONETMIB-3-NULLCFGPTR: NULL SONET MIB config pointer, if_index=[dec]

Explanation An attempt was made to initialize the SONET MIB using a null pointer.

Error Message

%SPE-3-MSMGR_REGISTRATION_ERR: Failed to register [chars] with Modem Service Manager

Explanation The Port Management has failed to register with the Modem Service Manager.

Recommended Action No action is required.

Error Message

%SPE-6-NULL_OBJ: SPE object [chars] is unavailable.

Explanation Information about this Service Processing Element (SPE) could not be retrieved. The SPE may not exist.

Recommended Action No action is required.

Error Message

%SPE-3-PM_DB_NO_MEM: Failed to allocate [chars] for slot [dec]

Explanation The port management has failed to allocate memory to create the specified slot object.

Recommended Action No action is required.

Error Message

%SPE-3-PM_DIRECT_MODEM_QUERY_ERR: Failed to find the response buffer for modem [chars] command

Explanation Modem direct query responses could not find a buffer in which to send data to the router shelf.

Recommended Action No action is required.

Error Message

%SPE-3-PM_SLOT_NO_MODULES: Database reported 0 modules for slot [dec]

Explanation The card in the specified slot should contain multiple modules. However, the database indicates that there are none.

Recommended Action No action is required.

Error Message

%SPE-3-RECOVERY_DNLD_MAINT_NO_MEM: Recovery Download Maintenance ran out of chunk memory; [chars]

Explanation The Recovery Download Maintenance messages cannot be sent.

Error Message

%SPE-6-SM_BUSIEDOUT: SPE [chars] busiedout(maintenance will be allowed)

Explanation The Service Processing Element (SPE) has been taken out of service temporarily. Maintenance activities can still be performed.

Recommended Action No action is required.

Error Message

%SPE-6-SM_CLEARED: SPE [chars] Cleared

Explanation The Service Processing Element (SPE) will be redownloaded with the configured firmware.

Recommended Action No action is required.

Error Message

%SPE-3-SM_CRASHED: SPE [chars] crashed

Explanation The firmware running on the Service Processing Element (SPE) has been aborted.

Recommended Action No action is required.

Error Message

%SPE-6-SM_DEFER_DOWNLOAD: SPE [chars] : Firmware download deferred

Explanation The firmware download for the Service Processing Element (SPE) has been postponed on account of active calls.

Recommended Action No action is required.

Error Message

%SPE-3-SM_DOWNLOAD_FAILED: SPE [chars] is BAD - [chars].

Explanation The Service Processing Element (SPE) has failed to download, and it will be marked "BAD".

Recommended Action No action is required.

Error Message

%SPE-3-SM_EVENT_NO_MEM: SPE SM out of event buffers; [chars] [chars]

Explanation The PM Service Processing Element (SPE) state machine has run out of event memory.

Error Message

%SPE-3-SM_POST_FAILED: SPE [chars] is BAD.

Explanation The Service Processing Element (SPE) has failed the POST process, and it will be marked "BAD".

Recommended Action No action is required.

Error Message

%SPE-3-SM_RESPONSE_NO_MEM: SPE SM out of response buffers

Explanation The PM Service Processing Element (SPE) state machine has run out of response event memory.

Error Message

%SPE-6-SM_SHUTDOWN: SPE [chars] shutdown

Explanation The Service Processing Element (SPE) has been taken out of service. Maintenance activities cannot be performed.

Recommended Action No action is required.

Error Message

%SPE-6-SM_START_DOWNLOAD: SPE [chars] : Firmware download initiated

Explanation The firmware download for the Service Processing Element (SPE) has been initiated.

Recommended Action No action is required.

Error Message

%SPE-4-SPE_ACT_SESS_WARN: Active session count = [dec]. Country code not set

Explanation The country code could not be set on the system because it had active sessions.

Recommended Action No action is required.

Error Message

%SPE-4-SPE_CONFIG_WARN: Country Code Trunk card mismatch for.

Explanation A country code was configured that may not work with the trunk card.

Recommended Action No action is required.

Error Message

%SPE-6-SPE_DNLD_MAINT: [chars] [chars]

Explanation Download maintenance is running. This message contains information regarding the maintenance download.

Recommended Action No action is required.

Error Message

%SPE-6-SPE_DNLD_MAINT_PROCESS: [chars]

Explanation This message contains download maintenance process information.

Recommended Action No action is required.

Error Message

%SPE-3-ST_API_ERR: PM failed to create [chars].

Explanation The Port Management has failed to initialize the call switching module (CSM) event processing component.

Error Message

%SPE-3-ST_EVENT_NO_MEM: PM ST failed to create [chars].

Explanation The Port Management has failed to allocate dynamic chunk memory for event logging.

Error Message

%SRCP_APP-6-DNS_QUEUE_FAILED: Failed to create DNS message watched queue

Explanation A Domain Name System (DNS) message watched queue could not be created.

Recommended Action Ensure that the size of free memory is adequate.

Error Message

%SRCP_APP-2-INTERNAL_CRITICAL: [chars], SRCP_COMPLAIN_IVL

Explanation An internal software error has occurred.

Error Message

%SRCP_APP-3-INTERNAL_ERROR: [chars], SRCP_COMPLAIN_IVL

Explanation An internal software error has occurred.

Error Message

%SRCP_APP-4-INTERNAL_WARNING: [chars], SRCP_COMPLAIN_IVL

Explanation An internal software error has occurred.

Error Message

%SRCP_APP-6-PROCESS_CREATION_FAILED: Cannot create SRCP application process

Explanation The Simple Resource Coordination Protocol (SRCP) application process could not be created.

Recommended Action Ensure that the size of free memory is adequate.

Error Message

%SRCP_APP-6-SOCKET_OPEN_FAILED: Failed to open UDP port for SRCP

Explanation The User Datagram Protocol (UDP) port for the Simple Resource Coordination Protocol (SRCP) process could not be opened.

Recommended Action Check if any other application uses the same UDP port number 2427.

Error Message

%SRCP_APP-6-SYS_QUEUE_FAILED: Failed to create SRCP system message watched queue

Explanation The Simple Resource Coordination Protocol (SRCP) system message watched queue could not be created.

Recommended Action Ensure that the size of free memory is adequate.

Error Message

%SSH-5-DISABLED: SSH [dec].[dec] has been disabled

Explanation The Secure Shell (SSH) protocol was disabled for connections.

Recommended Action No action is required.

Error Message

%SSH-5-ENABLED: SSH [dec].[dec] has been enabled

Explanation The Secure Shell (SSH) protocol was enabled for connections.

Recommended Action No action is required.

Error Message

%SSH-3-KEYPAIR: Attempt to generate server keys failed - error code: [chars]

Explanation The Server RSA key-pair could not be generated.

Recommended Action If this messages recurs, copy it exactly as it appears, and report it to your Cisco technical support representative.

Error Message

%SSH-3-PRIVATEKEY: Unable to retrieve RSA private key for [chars]

Explanation The RSA private key does not exist or is corrupted.

Recommended Action If this messages recurs, copy it exactly as it appears, and report it to your Cisco technical support representative.

Error Message

%SYS-3-BAD_RESET: Questionable reset of process [dec] on tty%t

Explanation A process was reset before it could clean itself up.

Error Message

%SYS-3-CRASHINFOINITFAIL: Crashinfo subsys initialization did not add registry crashinfo_get_default_file_name.

Explanation An internal software error has occurred.

Error Message

%SYS-3-DUP_TIMER: Same tty%t in linewatch_timers, type [dec]

Explanation A tty has appeared twice in a timer list where it should have appeared only once.

Error Message

%SYS-3-MGDTMRRUN: TTY%t: Managed Timer(s) [chars] still running

Explanation One or more managed timers for a tty that had been deleted are still running.

Error Message

%TCP-2-BADREFCNT: Tty%t: Bad refcnt for packet 0x[hex] during retransmit, [chars]:[dec] to [chars]:[dec], state [dec]

Explanation An internal software error has occurred.

Error Message

%TCP-2-BUFFER: Tty%t, buffering bug

Explanation An internal software error has occurred.

Error Message

%TCP-2-HALFCLOSE: Tty%t, tcp_putbyte() write disabled

Explanation TCP received a packet from a user application after the connection was already half closed.

Recommended Action Determine which TCP application is still sending packets after the connection is half closed.

Error Message

%TCP-6-NOBUFF: TTY[t-line], no buffer available

Explanation An internal software error has occurred.

Error Message

%TCP-6-TOOBIG: Tty%t, too many bytes of options ([dec])

Explanation An internal software error has occurred.

Recommended Action If this messages recurs, copy it exactly as it appears, and report it to your Cisco technical support representative.

Error Message

%TFIB-4-FIBCBLK: Missing MPLS Forwarding Information Base table for tableid [dec] during [chars] event

Explanation An internal software error has occurred.

Error Message

%TRUNK_CLOCK-6-BAD_CLOCKS: There are no good clocks in the system. Remain in HOLDOVER mode

Explanation The clock selection algorithm has failed to select any clock as the time-division multiplexing (TDM) primary clock.

Recommended Action No action is required.

Error Message

%TRUNK_CLOCK-6-EXTERNAL: Switching to the user configured external clock on motherboard

Explanation The time-division multiplexing (TDM) primary clock is switching from the default clock to the user-configured external clock in the motherboard.

Recommended Action No action is required.

Error Message

%TRUNK_CLOCK-6-FREERUN: Switching to the user configured freerunning clock on motherboard

Explanation The time-division multiplexing (TDM) primary clock is switching from the default clock to the user-configured free running clock in the motherboard.

Recommended Action No action is required.

Error Message

%TRUNK_CLOCK-3-NOMEMORY: Failed to allocate memory for the clocks

Explanation The clock switching software has failed to allocate memory while adding a clock.

Recommended Action No action is required.

Error Message

%TRUNK_CLOCK-6-SWITCH: Switching to the clock on slot [dec] port [dec] priority [dec] as the current primary has gone bad

Explanation The time-division multiplexing (TDM) primary clock has switched to a backup clock coming in through the specified trunk because the current primary clock has failed.

Recommended Action No action is required.

Error Message

%TRUNK_CLOCK-6-TRUNK: Switching to the user configured trunk clock on slot [dec] port [dec] priority [dec]

Explanation The time-division multiplexing (TDM) primary clock is switching from the default clock to the user-configured trunk clock.

Recommended Action No action is required.

Error Message

%TRUNK_DFC-3-CONTRCREATE: Failed to create controller for [dec]/[dec]

Explanation An internal software error has occurred.

Error Message

%TRUNK_DFC-3-DSX3CONTEXT: Failed to create context for dsx3 controller in [dec]/[dec]

Explanation An internal software error has occurred.

Error Message

%TRUNK_DFC-3-SDRAM_TEST_FAILED: Trunk DFC in slot [dec]: SDRAM failed [[hex]..[hex]]

Explanation The trunk Dial Feature Card (DFC) SDRAM test has failed, indicating a failed memory location.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue 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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%TRUNK_DFC-3-TRUNK_FIRMWARE_DOWNLOAD_FAILED: Could not download trunk firmware in slot [dec]

Explanation The trunk firmware cannot be downloaded.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue 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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%TRUNK_DFC-3-TRUNK_FIRMWARE_NOT_READY: Trunk DFC firmware in slot [dec] is not ready

Explanation The trunk Dial Feature Card (DFC) firmware has failed to start.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue 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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%TRUNK_DFC-3-TRUNK_RESET_FAILED: Reset failed for Trunk DFC ROM in slot [dec]

Explanation The Trunk Dial Feature Card (DFC) cannot be taken out of reset mode.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue 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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%TRUNK_DFC-3-TRUNK_ROM_FAILED: Trunk DFC ROM in slot [dec] failed: [chars]

Explanation The trunk Dial Feature Card (DFC) ROM has failed to boot properly.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue 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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%TRUNK_DFC-3-TRUNK_SLOT_CREATE: Failed to create trunk slot instance for slot [dec]

Explanation An internal software error has occurred.

Error Message

%TTY-3-AUTOCONFIG: TTY%t: Modem auto-configuration failed

Explanation Modem autoconfiguration has failed either because the modem rejected the configuration string or because a timeout has occurred.

Recommended Action An attempt should be made to apply the configuration string manually. Copy the error message exactly as 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

%TTYDRIVER-3-RTSLOW: TTY [chars]: RTS is deasserted though rx queue is empty

Explanation A software error resulting in an invalid state for the request to send (RTS) modem signal has occurred.

Error Message

%TTYDRIVER-3-UNKNOWN_PORT_ARCH_TYPE: Unknown port type ([dec])

Explanation A software error has occurred because of an unrecognized port type.

Error Message

%UBR900-7-RNG_REQ_TRANSMITTED: Periodic ranging request message transmitted.

Explanation A periodic ranging message has been sent.

Recommended Action No action is required.

Error Message

%UBR900-7-RNG_RSP_MSG_RCVD: Periodic ranging response message received.

Explanation A periodic ranging response message has been received.

Recommended Action No action is required.

Error Message

%UBR7200-6-ACTIVE: Cable clock [chars] reference active

Explanation The clock reference has become active.

Recommended Action No action is required.

Error Message

%UBR7200-5-CLASSFAIL: Registration failed for Cable Modem [sci_notation] on interface [chars][chars]: [chars], 2000

Explanation The registration of this modem has failed because of an invalid or unsupported class of service (CoS) setting.

Recommended Action Make sure the class of service (CoS) fields in the configuration file are set correctly.

Error Message

%UBR7200-3-DBDSPDEAD: AWACS Slot [dec] is dead

Explanation The daughter card digital signal processor (DSP) has failed.

Recommended Action Reload the image. If it still fails, replace the defective daughter card.

Error Message

%UBR7200-6-DBDSPDOWNLOADDONE: Downloading dsp code completed

Explanation Downloading of digital signal processor (DSP) code is completed.

Recommended Action No action is required.

Error Message

%UBR7200-3-DBDSPDOWNLOADERR1: failed init download

Explanation The initial download of the digital signal processor (DSP) has failed.

Recommended Action Reload the image. If the download still fails, replace the defective daughter card.

Error Message

%UBR7200-3-DBDSPDOWNLOADERR2: Failed downloading

Explanation The digital signal processor (DSP) downloading has failed.

Recommended Action Reload the image. If the download still fails, replace defective daughter board.

Error Message

%UBR7200-3-DBDSPDOWNLOADERR3: Failed end downloading

Explanation The last step of the digital signal processor (DSP) downloading has failed.

Recommended Action Reload the image. If the download still fails, replace the defective daughter card.

Error Message

%UBR7200-6-DBDSPDOWNLOADSTART: Downloading dsp code initiated

Explanation The downloading of the digital signal processor (DSP) code started.

Recommended Action No action is required.

Error Message

%UBR7200-3-DBDSPERR1: DSP SRAM failed

Explanation The daughter card hardware has failed.

Recommended Action Replace the defective daughter card.

Error Message

%UBR7200-3-DBDSPERR2: DSP SRAM semaphore failed

Explanation The daughter card hardware has failed.

Recommended Action Replace the defective daughter card.

Error Message

%UBR7200-3-DBDSPERR3: DSP side dual-port SRAM failed

Explanation The daughter card hardware has failed.

Recommended Action Replace the defective daughter card.

Error Message

%UBR7200-3-DBDSPERR4: DSP FLASH memory failed

Explanation The daughter card hardware has failed.

Recommended Action Replace the defective daughter card.

Error Message

%UBR7200-3-DBDSPERR5: DSP failed for unknown reason(0x[hex])

Explanation The daughter card hardware has failed.

Recommended Action Replace the defective daughter card.

Error Message

%UBR7200-3-DBDSPERR6: Switching to backup dsp image failed

Explanation The daughter card hardware has failed.

Recommended Action Replace the defective daughter card.

Error Message

%UBR7200-3-DBDSPIDERR: DSP id read 0x[hex]pect 0x[hex]

Explanation The daughter card hardware has failed.

Recommended Action Replace the defective daughter card.

Error Message

%UBR7200-5-DBDSPRECOVER2: Switching to backup dsp image succeeded

Explanation The switch to the backup digital signal processor (DSP) image has succeeded.

Recommended Action No action is required.

Error Message

%UBR7200-5-DBDSPRECOVER3: Recovering and switching back to regular dsp image succeeded

Explanation The digital signal processor (DSP) recover operation using the backup image has succeeded.

Recommended Action No action is required.

Error Message

%UBR7200-5-DBDSPUP: Handshake DSP is successful after [dec] ms delay

Explanation The digital signal processor (DSP) is up and running.

Recommended Action No action is required.

Error Message

%UBR7200-6-DBDSPVERSION: Current DSP version : [dec], DSP flash version : [dec]

Explanation This message confirms that the current digital signal processor (DSP) version and the version of DSP that booted up are the same.

Recommended Action No action is required.

Error Message

%UBR7200-3-DBFPGAERR: XILINX not up, reset reg is 0x[hex]

Explanation The daughter card hardware has failed.

Recommended Action Replace the defective daughter card.

Error Message

%UBR7200-3-DBPLX9050ERR: Plx9050 id read 0x[hex]pect 0x[hex]

Explanation The daughter card hardware has failed.

Recommended Action Replace the defective daughter card.

Error Message

%UBR7200-3-DBPLX9080ERR: Plx9080 id read 0x[hex]pect 0x[hex]

Explanation The daughter card hardware has failed.

Recommended Action Replace the defective daughter card.

Error Message

%UBR7200-6-DRVMP: Midplane TDM clock reference defaults to Clockcard

Explanation The clockcard primary reference is from the midplane time-division multiplexing (TDM) clock.

Recommended Action No action is required.

Error Message

%UBR7200-6-FREERUN: Cable clock in Freerun mode

Explanation The clockcard is in free run mode.

Recommended Action No action is required.

Error Message

%UBR7200-6-HOLDOVER: Cable clock in Holdover mode

Explanation The clockcard has switched to holdover mode.

Recommended Action Check the reference source.

Error Message

%UBR7200-4-HWFAULT: Hardware Fault

Explanation There is a hardware fault in the clockcard.

Recommended Action Replace the clockcard.

Error Message

%UBR7200-6-LOS: Cable clock [chars] reference Loss of Signal

Explanation The clock reference has been lost.

Recommended Action Check the reference source.

Error Message

%UBR7200-4-RECALLED_NPE: Old version NPE-175/225 with Rev = 0x[hex] system controller. Contact upgrades-info@cisco.com for replacement

Explanation The NPE-175 or NPE-225 board has been recalled because of an error involving the system controller chip.

Recommended Action Replace NPE-175/225 board.

Error Message

%UBR7200-6-REFLOCK: Cable clock locked to [chars] reference

Explanation The clockcard has locked onto the clock source.

Recommended Action No action is required.

Error Message

%UBR7200-6-SRCMP: Cable Clock primary reference is midplane TDM clock

Explanation The clockcard primary reference is from the midplane time-division multiplexing (TDM) clock.

Recommended Action No action is required.

Error Message

%UTIL-6-RANDOM: A pseudo-random number was generated twice in succession, 10*ONESEC

Explanation A pseudorandom number generator has produced the same number twice in succession.

Recommended Action Under normal circumstances a pseudorandom number generator occasionally producing the same number twice in succession is not a problem. However, if this message occurs frequently, the system should be manually reloaded. If the message is persistent across reloads, copy the error message exactly as it appears, and report it to your Cisco technical support representative.

Error Message

%VPA-3-BADVC: [chars] [dec]/[dec] got bad VC packet [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex], 1 * ONEMIN

Explanation An interface has received a packet with bad virtual circuit (VC) encapsulation. Receiving a a packet with bad VC encapsulation indicates either a software or a hardware problem.

Error Message

%VPA-3-CMDFAIL: [chars] Command Failed at [chars] - line [dec], arg [dec]

Explanation The port adapter has failed to process a command.

Error Message

%VPA-6-NODATA: Data call is not supported on [chars]., 30*ONEMIN

Explanation Data call is not supported in this version of Cisco IOS software.

Recommended Action Remove the data call configuration/setup.

Error Message

%VPA-6-NOTDMBP: No TDM backplane is supported on slot [dec]., 10*ONESEC

Explanation Ds0 cannot be cross-connected into the slot without the time-division multiplexing (TDM) backplane.

Error Message

%VPA-1-RPTFAIL: [chars] failed to send report [dec] at [chars] - line [dec]

Explanation The port adapter has failed to send a report from virtual IP.

Error Message

%VPA-3-TDMFAIL: VPA-TDM, access failed at [chars] - line [dec], arg1=0x[hex], arg2=0x[hex]

Explanation The port adapter has failed to access the time-division multiplexing (TDM) switch.

Error Message

%VTSP-3-VTSP_HAIRPIN_FAILED: Call hairpinning failed. cdb [hex], dst_cdb [hex], dst_call_id [dec]

Explanation A call without a digital signal processor (DSP) could not be hairpinned. Under heavy traffic, this failure may happen because no time-division multiplexing (TDM) resources are available.

Error Message

%VTSP-3-VTSP_HAIRPIN_NOTPOSSIBLE: Call can't be hairpinned. cdb [hex], dst_cdb [hex], dst_call_id [dec]

Explanation A call without a digital signal processor (DSP) could not be hairpinned.

Recommended Action Check the dial peer configuration.

Error Message

%VTSP-3-VTSP_HAIRPINN: hairpin peer cdb does not exist, cdb [hex], dst_call_id [dec]

Explanation A hairpin call setup has failed because the other call leg does not exist.

Error Message

%XCCTSP_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 signaling 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. Issue 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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%XCCTSP_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 signaling data block from the Voice Telephony Service Provider. The system may be out of memory.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue 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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

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

Explanation The voice interface defined by controller:group is not yet defined within the voice software, but attempts were made to use this interface. An internal software error has occurred.

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

Table of Contents