|
|
The following are CT1 Robbed-Bit Signalling (RBS) timeslot status error messages.
Error Message
%DSX0-5-RBSLINEDBUSYOUT: RBS of controller [dec] timeslot [dec] is dynamic busyoutExplanation 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-RBSLINEDOWN: RBS of controller [dec] timeslot [dec] is downExplanation Robbed-Bit Signalling (RBS) has been disabled on the specified time slot and controller.
Recommended Action No action is required.
Error Message
%DSX0-5-RBSLINESBUSYOUT: RBS of controller [dec] timeslot [dec] is static busyoutExplanation 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 controller [dec] timeslot [dec] is unbusyoutExplanation 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
%DSX0-5-RBSLINEUP: RBS of controller [dec] timeslot [dec] is upExplanation Robbed-Bit Signalling (RBS) has been enabled on the specified time slot and controller.
Recommended Action No action is required.
The following are channelized E1 (Europe) and T1 (US) telephony standard error messages.
Error Message
%DSX1-6-CLOCK_CHANGE: [chars] clock is now selected as clock sourceExplanation The los, ais, or cli command was entered, causing a change to the clock selected.
Recommended Action No action is required.
Error Message
%DSX1-3-FIRMWARE_RESTART: T1/E1 Firmware restartedExplanation The T1/E1 firmware has 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 Copy the error message exactly as 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
%DSX1-1-FIRMWARE_RUNNING: T1/E1 Firmware is runningExplanation The T1/E1 firmware is now running after recovering from a critical error.
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
%DSX1-1-FIRMWARE_STOPPED: T1/E1 Firmware is not runningExplanation A critical error has occurred in the T1/E1 firmware, and it has stopped running. The access server must be reloaded.
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
%DSX1-3-M32_AR_FAILURE: Munich 32 action request failure: Ctrl = 0x[hex], Channel = [dec]Explanation Munich 32 is not responding to a request.
Recommended Action If this error message recurs repeatedly, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSX1-3-M32_AR_TIMEOUT: Munich 32 action request timeout: Ctrl = 0x[hex], Channel = [dec]Explanation Munich 32 is not responding to an action request.
Recommended Action If this error message recurs repeatedly, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSX1-3-M32_BAD_BITRATE: Munich 32 bit rate not match: Ctrl = 0x[hex], Channel = [dec]Explanation The command cannot be carried out because of a bit rate mismatch.
Recommended Action Make sure the configured data matches the supported speed.
Error Message
%DSX1-3-M32_BAD_INTQ: Munich 32 bad interrupt queue: Ctrl = 0x[hex], Channel = [dec]Explanation There might be an overflow on the interrupt queue.
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
%DSX1-3-M32_BAD_STATE: Munich 32 in unknown state: Ctrl = 0x[hex], Channel = [dec]Explanation Munich 32 has gone into an unknown state.
Recommended Action If this error message recurs repeatedly, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSX1-3-M32_ERR: Munich 32 error configuring channelized interface: Ctrl = 0x[hex], Channel = [dec]Explanation Unidentified errors have occurred on Munich 32.
Recommended Action If this error message recurs repeatedly, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSX1-3-M32_ILLEGAL_CHANNEL: Munich 32 channel invalid: Ctrl = 0x[hex], Channel = [dec]Explanation The channel selection is not valid.
Recommended Action Make sure the channel supports the required feature.
Error Message
%DSX1-1-M32_INPUT_CONGEST: Munich 32 channel input queue is congestedExplanation The receiver cannot allocate receive buffers because the input queue is at its maximum. Data is coming in faster than the receiver can handle.
Recommended Action Reduce the volume of data that goes into this channel or increase the number of input queues for the channel.
Error Message
%DSX1-3-M32_MEM_ALLOC: Munich 32 channel memory allocation error: Ctrl = 0x[hex], Channel = [dec]Explanation The requested operation could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message
%DSX1-3-M32_NO_TIMESLOT: Munich 32 no timeslot available: Ctrl = 0x[hex], Channel = [dec]Explanation All the time slots on Munich 32 are assigned.
Recommended Action Make sure there are timeslots available before choosing one.
Error Message
%DSX1-3-M32_TIMESLOT_IN_USE: Munich 32 timeslot already configured: Ctrl = 0x[hex], Channel = [dec]Explanation This time slot has already been assigned and cannot be used.
Recommended Action Make sure the time slot is available before choosing it.
Error Message
%DSX1-3-NOMEMORY: msgtxt_nomemoryExplanation The requested operation could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
The following are dial shelf time-division multiplexing (TDM) error messages.
Error Message
%DS_TDM-3-ASSERT_FAIL: Slot [dec] Assertion failed: file `[chars]', line [dec]Explanation An internal sanity check has failed.
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
%DS_TDM-3-BAD_CONN: Slot [dec] Unrecognized TDM connect message received ([dec]) on [chars] feature boardExplanation An unrecognized time-division multiplexing (TDM) connect message has been received.
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
%DS_TDM-3-BAD_DISCONN: Slot [dec] Unrecognized TDM disconnect message received ([dec]) on [chars] feature boardExplanation An unrecognized time-division multiplexing (TDM) disconnect message has been received.
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
%DS_TDM-3-BAD_DSIP: Slot [dec] Unrecognized DSIP message received ([dec]) on [chars] feature boardExplanation An unrecognized Dial Shelf Interconnect Protocol (DSIP) message has been received.
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
%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.
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
%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.
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
%DS_TDM-3-TDM_CLOSE: Slot [dec] Close MT90820 (addr: 0x[hex]) connection failed - STo[dec], CHo[dec]Explanation An attempt to disable a digitally switched connection has failed.
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
%DS_TDM-3-TDM_OPEN: Slot [dec] Open MT90820 (addr: 0x[hex]) connection failed - STi[dec], CHi[dec], STo[dec], CHo[dec]Explanation An attempt to establish a digitally switched connection has failed.
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
%DS_TDM-3-VERIFY_DISCONN: Slot [dec] [chars] failed to verify disconnect: sto = [dec], ch_out = [dec]Explanation An attempt to verify a time-division multiplexing (TDM) hardware component has failed.
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
%DS_TDM-3-VERIFY_HILOWMEM: Slot [dec] [chars] failed to verify 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.
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
%DS_TDM-3-VERIFY_IMS: Slot [dec] [chars] failed to verify IMS: 0x[hex]Explanation An attempt to verify a time-division multiplexing (TDM) hardware component has failed.
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.
The following are Enhanced Interior Gateway Routing Protocol (EIGRP) error messages.
Error Message
%DUAL-3-ANCHORCOUNT: Anchor count negativeExplanation A software or hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DUAL-3-BADCOUNT: Route [chars], [dec] successors, [dec] rdbsExplanation A software or hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DUAL-6-EVENT: [chars], [chars]Explanation A software or hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DUAL-3-INTERNAL: [chars] [dec]: Internal ErrorExplanation A software or hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DUAL-3-LINKSEXIST: Interface [chars] going down and [dec] links existExplanation An interface is going down or is being removed from routing through Interior Gateway Routing Protocol (IGRP), but not all the links (neighbors) have been removed from the topology table.
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
%DUAL-3-LINKSTILLUP: Link [dec] [chars] still exists on [chars]Explanation A software or hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DUAL-3-MULTIFLOW: Flow control error, [chars], on [chars]Explanation A software or hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DUAL-5-NBRCHANGE: [chars] [dec]: Neighbor [chars] ([chars]) is [chars]: [chars]Explanation A neighbor has gone up or down.
Recommended Action No action is required.
Error Message
%DUAL-3-NOBUFFER: No buffers available for [int] byte packetExplanation The DUAL software was unable to allocate a packet buffer. 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
%DUAL-3-NOHANDLE: Handle [dec] is not allocated in poolExplanation A software or hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DUAL-3-NOMATCH: Nexthop and infosource don't match. N = [chars], I = [chars]Explanation A software or hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DUAL-3-NOSOCKET: Unable to open socket for AS [dec]Explanation A software or hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DUAL-3-PEERSEXIST: [dec] peers exist on IIDB [chars]Explanation A software or hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DUAL-3-PROBESEQ: Bad probe sequence [dec] from [chars], expecting [dec]Explanation A software or hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DUAL-3-RDBLEFT: Lingering DRDB deleting IIDB, dest [chars], nexthop [chars] ([chars]), origin [chars]Explanation A software or hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DUAL-3-REFCOUNT: Negative refcount in pakdesc [hex]Explanation A software or hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DUAL-3-SIA: Route [chars] stuck-in-active state in [chars] [dec]. Cleaning upExplanation A software or hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DUAL-3-SIANOHANDLE: Stuck-in-active and [dec] unallocated handle(s) in reply-status table ([hex]). Cleaning upExplanation A software or hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DUAL-3-UNKTIMER: Unknown timer type [dec] expirationExplanation A software or hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are Distance Vector Multicast Routing Protocol (DVMRP) error messages.
Error Message
%DVMRP-5-BADMASK: Bad mask [int] received from [int], Report ignoredExplanation A Distance Vector Multicast Routing Protocol (DVMRP) route having corrupted information was received and discarded by another system.
Recommended Action No immediate action is required. This error indicates a problem with the system that sent the bad routes or with the network media connected to that system. If the condition persists, contact the administrator of the malfunctioning system.
Error Message
%DVMRP-5-NBRDOWN: Neighbor [int] went down on [chars]Explanation Distance Vector Multicast Routing Protocol (DVMRP) activity has been shut down on the specified interface. This may be because the interface has been taken down or because the DVMRP routes on that interface have all expired. Note that DVMRP activity is mutually exclusive of tagswitching, so if the interface itself is still up, tagswitching will be automatically reenabled on that interface.
Recommended Action No action is required.
Error Message
%DVMRP-5-NBRUP: Neighbor [int] is up on [chars]Explanation A Distance Vector Multicast Routing Protocol (DVMRP) multicast neighbor is active on the specified interface because of the arrival and acceptance of DVMRP probes via that interface. This message may indicate that a multicast session has been subscribed via a path passing through this router. Note that DVMRP activity is mutually exclusive of tagswitching, so tagswitching may disabled on that interface.
Recommended Action No action is required.
Error Message
%DVMRP-4-NONPRUNER: Rejecting non-pruning peer [int] ([chars])Explanation The router has rejected an Internet Group Management Protocol (IGMP) report from a peer that is not capable of Distance Vector Multicast Routing Protocol (DVMRP) pruning and grafting. This is because the router was configured with the ip dvmrp reject-non-pruners command to reject nonpruning peers.
Recommended Action If rejection of nonpruning DVMRP hosts is consistent with the site policy, no action is required. Otherwise, the configuration can be changed by using the no ip dvmrp reject-non-pruners command.
Error Message
%DVMRP-4-REJDEFROUTE: Rejecting default route from [int]Explanation Two routers on each side of a tunnel are sending the default route to each other.
Recommended Action Correct the router configuration.
Error Message
%DVMRP-4-ROUTEHOG: Receiving [dec] routes from [int] ([chars]) in the last [chars]Explanation The number of Distance Vector Multicast Routing Protocol (DVMRP) routes that were received from the specified system exceeds the warning threshold for the DVMRP route traffic.
Recommended Action Use the ip dvmrp routehog-notification command to change the warning threshold if necessary. Otherwise check the system that is generating excessive DVMRP route traffic to find out the reason. The system may be in a loop and generating invalid information.
Error Message
%DVMRP-4-ROUTELIMIT: Exceeded route-limit of [dec] routes, check your access-listsExplanation The number of Distance Vector Multicast Routing Protocol (DVMRP) multicast routes exceeds the configured maximum number. New routes (subscribers and viewers) cannot be added unless the configuration is changed.
Recommended Action If priority multicast traffic is carried by this router, use the ip dvmrp route-limit command to increase the number of DVMRP routes. Otherwise, no action is required.
The following are E1T1 Module error messages.
Error Message
%E1T1_MODULE-3-HWIDBFAILED: Controller [dec]/[dec] does not have idbExplanation The system did not have a HWIDB registered for the serial interface.
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
%E1T1_MODULE-3-INITFAILURE: Slot [dec], Unit [dec] initialization failure - [chars]Explanation The E1T1 driver detected an error while initializing.
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
%E1T1_MODULE-3-LINEFLAP: Interface [chars] receiving excessive errored packetsExplanation The serial interface is receiving an excessive number of error packets. This problem is caused by a controller configuration mismatch.
Recommended Action Check Linecode, Framing, Timeslots and Speed settings.
The following are Exterior Gateway Protocol (EGP).
Error Message
%EGP-3-NOPDB: No pdb for [int]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, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%EGP-3-TOOBIG: Insufficient ([dec]) buffering for update messageExplanation An Exterior Gateway Protocol (EGP) update message was too large to fit into a single buffer.
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.
The following are Cisco 6400 Enhanced High System Availability (EHSA) error messages.
Error Message
%EHSA-3-CONFIG_SYNC: [chars]Explanation An Enhanced High System Availability (EHSA) configuration synchronization error has occurred. The details of what action was attempted and what malfunctioned will be printed.
Recommended Action Copy the error message exactly as it appears. Include the system configuration information along with any other relevant information. Call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%EHSA-3-EHSA_ALARMS: [chars]Explanation An Enhanced High System Availability (EHSA) alarm assertion error has occurred. The details of what action was attempted and what malfunctioned will be printed.
Recommended Action Copy the error message exactly as it appears. Include the system configuration information along with any other relevant information. Call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%EHSA-3-FSM: [chars]Explanation An Enhanced High System Availability (EHSA) Finite State Machine (FSM) error has occurred. The details of what action was attempted and what malfunctioned will be printed.
Recommended Action Copy the error message exactly as it appears. Include the system configuration information along with any other relevant information. Call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%EHSA-3-GENERAL: [chars]Explanation An Enhanced High System Availability (EHSA) error has occurred. The details of what action was attempted and what malfunctioned will be printed.
Recommended Action Copy the error message exactly as it appears. Include the system configuration information along with any other relevant information. Call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%EHSA-3-IPC: [chars] [chars]Explanation An interprocess communication (IPC) error has occurred. The details of what action was attempted and what malfunctioned will be printed.
Recommended Action Copy the error message exactly as it appears. Include the system configuration information along with any other relevant information. Call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%EHSA-3-PEER_MONITOR: [chars]Explanation An Enhanced High System Availability (EHSA) Peer Monitor error has occurred. The details of what action was attempted and what malfunctioned will be printed.
Recommended Action Copy the error message exactly as it appears. Include the system configuration information along with any other relevant information. Call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%EHSA-5-PEER_MONITOR_EVENT: [chars] ([chars][chars]([dec]))Explanation An Enhanced High System Availability (EHSA) Peer Monitor event occurred and was reported. The report indicates the reason for a switch-over.
Recommended Action No action is required.
The following are Enhanced Network Service Provider (ENSP) error messages.
Error Message
%ENSP-4-FMAIL_BAD_MESSAGE: FAXMAIL- Bad message receivedExplanation An unexpected message has been received.
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
%ENSP-2-FMAIL_INTERNAL_ERROR: Internal software errorExplanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ENSP-2-FMAIL_NO_AUTH_STARTED: AAA authentication startup failedExplanation AAA authentication startup has failed.
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
%ENSP-4-FMAIL_NO_SMTP: FAXMAIL- Can not connect o the SMTP serverExplanation No connection could be made to any of the specified Simple Mail Transfer Protocol (SMTP) servers.
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
%ENSP-4-FMAIL_NO_SMTP_SEND: FAXMAIL- Could not send data to the SMTP serverExplanation A connection was made to the Simple Mail Transfer Protocol (SMTP) server, but data cannot be sent.
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
%ENSP-2-INTERNAL_ERROR: FAX- Internal software errorExplanation An internal software has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ENSP-1-NOMEMORY: msgtxt_nomemoryExplanation The requested operation could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message
%ENSP-4-SMTP_NOT_CONNECTED: SMTP- failed [chars], [dec]Explanation An attempt to connect to a remote mail server has failed. This is unexpected behavior.
Recommended Action No action is required.
Error Message
%ENSP-6-SMTP_OPEN: SMTP- opening [chars], [dec]Explanation An attempt to connect to a remote mail server has failed. This is unexpected behavior.
Recommended Action No action is required.
The following are Entity MIB Application Programming Interface (API) error messages.
Error Message
%ENT_API-4-NOALIAS: [chars] entity not found when adding an alias with physical index = [int] and logical index = [int] to the Entity MIBExplanation The attempt to add an alias entry to the Entity MIB failed. A logical or physical entity with the specified index does not exist.
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. Using your network management system (NMS) tool, also provide the content of the Entity MIB table.
Error Message
%ENT_API-3-NOCREAT: EntityApiProcess not created - Entity MIB will not be initialisedExplanation Attempt to start the routine failed when the entity subsystem was initialized. The Entity MIB will not be populated.
Recommended Action The Entity MIB Application Programming Application Programming Interface (API) process was not created, possibly due to a lack of memory. If you want to use the Entity MIB API, reconfigure the system so that less memory is used by other features, or add more memory to the system. Reload the system after reconfiguring it.
Error Message
%ENT_API-4-NOENT: Trying to add or delete an unknown entity to the Entity MIBExplanation An attempt to add or delete an unknown entity to the Entity MIB was made. The request could not be processed.
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. Using your network management system (NMS) tool, also provide the contents of the Entity MIB table.
Error Message
%ENT_API-4-NOLPMAP: [chars] entity not found when adding an LPMapping entry with logical index = [int] and physical index = [int] to the Entity MIBExplanation An attempt to add an LPMapping entry to the Entity MIB was made. Since a logical or physical entity having the specified index does not exist, the LPMapping entry creation failed.
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. Using your network management system (NMS) tool, also provide the contents of the Entity MIB table.
Error Message
%ENT_API-4-NOPARENT: Parent physical entity [int] did not exist when trying to add child physical entity [int]Explanation An attempt to add a physical entity has failed because its parent physical entity does not exist in the entPhysicalTable of the Entity MIB.
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. Using your network management system (NMS) tool, also provide the contents of the Entity MIB table.
Error Message
%ENT_API-4-NOPORT: Physical entity does not have a Port PhysicalClass when adding an alias with physical index = [int] and logical index = [int] to the Entity MIBExplanation An attempt to add an alias entry to the Entity MIB was made. The physical entity having the specified index does not have an entPhysicalClass of 10 (Port class), and so the alias entry creation failed. See the RFC2037 document for the definition of the PhysicalClass textual-convention and the aliasMappingEntry object.
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. Using your network management system (NMS) tool, also provide the contents of the Entity MIB table.
The following are Route Processor Module (RPM) Environmental Support error messages.
Error Message
%ENVM-3-BLOWER: [chars] may have failedExplanation One of the cooling fans on the router may be close to failure.
Recommended Action Replace the fan as soon as possible or the system may either shut itself down or operate improperly.
Error Message
%ENVM-3-CPUCARD: Unknown CPU type [dec]Explanation A CPU card in the system was not recognized by the software.
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
%ENVM-2-ENVCRIT: [chars] measured at [chars]Explanation One of the measured environmental test points has exceeded an extreme threshold.
Recommended Action Correct the specified condition or the system may shut itself down as a preventive measure. This condition could cause the system to operate improperly. If the message recurs, copy the error message exactly as 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
%ENVM-4-ENVWARN: [chars] measured at [chars]Explanation One of the measured environmental test points has exceeded the warning threshold.
Recommended Action Closely monitor the condition and correct it if possible. If the message recurs, copy the error message exactly as 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
%ENVM-3-LASTENV: [chars]Explanation The nonvolatile electrically erasable programmable read-only memory (EEPROM) storage of environmental statistics has failed. This error may be caused by an EEPROM (hardware) failure.
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
%ENVM-3-NOACK: Access to [chars] failedExplanation One of the temperature sensors was not ready for the initiation of environmental temperature monitoring. The software is attempting to restart the sensor.
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
%ENVM-3-NOFORK: Could not start environment polling processExplanation Since the software could not spawn the environmental monitoring process, possibly because of low memory, no monitoring will be performed.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message
%ENVM-6-PSCHANGE: [chars] changed from [chars] to [chars]Explanation This message indicates the absence or detection of a new type of power supply in the system. This action is normal when hot-swappable power supplies are swapped.
Recommended Action No action is required.
Error Message
%ENVM-6-PSLEV: [chars] state changed from [chars] to [chars]Explanation One of the power supply test points has undergone a state change.
Recommended Action Closely monitor the condition and correct it if possible. If the message recurs, copy the error message exactly as 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
%ENVM-0-SHUT: Environmental Monitor initiated shutdownExplanation The environmental monitor has initiated a system shutdown.
Recommended Action Look at previous environmental messages to determine cause of shutdown and correct the problem if possible. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are Cisco 12000 environmental monitor error messages.
Error Message
%ENV_MON-2-FAN: Fan array has reached [chars] levelExplanation There might be a hardware problem with the fan array. If the error condition continues for more than two minutes, the router automatically shuts down to prevent damage to the router components.
Recommended Action If the system shuts down, replace the fan tray. Copy the error message exactly as it appears, and report it to your Cisco technical support representative.
Error Message
%ENV_MON-2-FANOK: Fan array has recoveredExplanation One or more of the variable speed fans has recovered from a prior failure.
Recommended Action No action is required.
Error Message
%ENV_MON-1-SHUTDOWN: Environmental Monitor initiated shutdownExplanation The system has reached a shutdown temperature level, and the router is being shut down to avoid any damage.
Recommended Action Attempt to resolve the temperature problem. If the problem is not resolved, call your Cisco technical support representative for assistance.
Error Message
%ENV_MON-2-SUPPLY: [chars] Power Supply is Non-OperationalExplanation A power supply is not working or has not been turned on.
Recommended Action Ensure that the power supply is on; if it is on and still does not operate, call your Cisco technical support representative for assistance.
Error Message
%ENV_MON-2-TEMP: [chars] temperature has reached [chars] level at [dec](C)Explanation The temperature sensor specified has reached a warning or critical level that is outside the acceptable range.
Recommended Action Attempt to resolve the temperature problem. If the problem is not resolved, call your Cisco technical support representative for assistance.
Error Message
%ENV_MON-3-UNKNOWN_TEMP_SENSOR: sensor [dec] in slot [dec] value = [dec].[dec]Explanation A temperature measurement has been received from an unknown sensor. This message probably indicates a software error. This message can also indicate that the maintenance bus (MBus) data has been corrupted.
Recommended Action This message is informational only. No action is required. However, if this message recurs, indicating a continued condition, contact your Cisco technical support representative.
Error Message
%ENV_MON-3-UNKNOWN_VOLTAGE_SUPPLY: supply [dec] in slot [dec] value = [dec]Explanation A voltage measurement has been received from an unknown supply. This message can also indicate that the maintenance bus (MBus) data has been corrupted.
Recommended Action This message is informational only. No action is required. However, if this message recurs, indicating a continued condition, contact your Cisco technical support representative.
Error Message
%ENV_MON-2-VOLTAGE: [chars] volts has reached [chars] level at [chars](V)Explanation The voltage supply specified has reached a critical level and is now out of specification.
Recommended Action Verify the failure and call your Cisco technical support representative to arrange for the repair or replacement of the equipment.
The following are encryption port adapter driver (EPAD) error messages.
Error Message
%EPAD-1-ERROR: [chars]Explanation A software error has occurred. The message will include more information that can be used to identify the problem.
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
%EPAD-1-INITFAIL: [chars]Explanation The encryption port adapter has failed to initialize.
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
%EPAD-1-WARNING: [chars]Explanation A nonfatal warning condition has occurred. The message will include more information about the nature of the problem.
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.
The following are Ethernet switch port adapter error messages.
Error Message
%ESWITCH-1-DEC21140: ESWITCH([dec]) Failed to initialize DEC21140, shutting down bayExplanation A software or hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ESWITCH-1-EALE: ESWITCH([dec]) Failed to initialize EALEExplanation A hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ESWITCH-1-MULTICASTADD: ESWITCH([dec]), Cannot add multicast [sci_notation]Explanation A hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ESWITCH-5-NOBRIDGEGROUP: ESWITCH([dec]), Bridge-group must be configuredExplanation A configuration error has occurred.
Recommended Action Configure a bridge group on the interface.
Error Message
%ESWITCH-5-NOMOREVLANS: ESWITCH([dec]), Only [dec] Bridge-Groups(vLANS) are supportedExplanation A configuration error has occurred.
Recommended Action Configure no more than the allowed number of Bridge-groups on the Ethernet switch port adapter.
Error Message
%ESWITCH-1-NOTPLX: ESWITCH([dec]) Device is not PLX 9060SD, Device reported [hex]Explanation A hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ESWITCH-1-PCIINIT: ESWITCH([dec]) Failed to initialize PCI devices, shutting down bayExplanation A hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ESWITCH-1-TSWITCH: ESWITCH([dec]) Failed to initialize TSWITCHExplanation A hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ESWITCH-1-TSWITCHEALE: ESWITCH([dec]) Failed to initialize TSWITCH/EALE, shutting down bayExplanation A software or hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ESWITCH-1-UNICASTADD: ESWITCH([dec]), Cannot add unicast [sci_notation]Explanation A hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ESWITCH-1-UNICASTDEL: ESWITCH([dec]), Cannot remove unicast [sci_notation]Explanation A hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ESWITCH-1-UNICASTDELP: ESWITCH([dec]), Cannot flush unicasts from port [dec]Explanation A hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and technical support representative, and provide the representative with the gathered information.
Error Message
%ESWITCH-1-UNICASTDELPV: ESWITCH([dec]), Cannot flush unicasts from vLAN [dec] on uplinkExplanation A hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ESWITCH-1-UNICASTDELV: ESWITCH([dec]), Cannot flush unicasts from vLAN [dec]Explanation A hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ESWITCH-1-UNICASTLOCK: ESWITCH([dec]), Cannot lock unicast [sci_notation]Explanation A hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are C1000 series Ethernet error messages.
Error Message
%ETHERNET-1-NOMEMORY: msgtxt_nomemoryExplanation Insufficient memory exists to allocate the necessary memory pools.
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
%ETHERNET-1-TXERR: [chars]: Fatal transmit error. Restarting...Explanation A fatal transmit error has occurred on the Ethernet line, causing the line to be restarted.
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
%ETHERNET-4-UNSUPINTFC: Interface Ethernet[dec] not supported by [chars] imageExplanation The specific Ethernet interface is not supported by the operating system currently running.
Recommended Action If the hardware configuration is supported by a newer version of the operating system, you must to upgrade the software in order to support this interface.
The following are Expression MIB error messages.
Error Message
%EXPRESSION-3-BADTYPE: Found data type [hex] in expression (should be [chars] type)Explanation While evaluating an expression, the software found an operand with an unexpected type of data. The evaluation of this expression has been aborted.
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
%EXPRESSION-3-FAILASSERT: Assertion failed: [chars]Explanation An operation within the Expression MIB subsystem encountered a data value that is out of range, indicating a logic error within the subsystem.
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.
The following are Fabric Interface ASIC (FIA) error messages.
Error Message
%FABRIC-3-CRC: Switch card [int]Explanation An excessive number of crc16 errors has been detected from one of the fabric switch cards. This error usually indicates a hardware problem, either on the fabric card that is displayed in the error message or on the line card or Route Processor (RP) reporting the error.
Recommended Action Use the show controller fia command on the RP and the execute-on all show controller fia command to determine wether the problem involves all the cards or only one. If only one card is involved, replace the line card or RP. If more than one is involved, replace the switch card.
Error Message
%FABRIC-3-FIFOERR: [chars] FIFO Error was detected. [chars], Data = 0x[hex]Explanation A First-in, First-out (FIFO) error has been detected by the Fabric Interface ASIC (FIA) hardware.
Recommended Action The device will be reset. If the problem persists, the card will be reset automatically. Call your Cisco technical support representative for assistance if this message appears repeatedly.
Error Message
%FABRIC-3-HALT: [chars]Explanation The fabric hardware has not been able to correct itself.
Recommended Action Try reseating the boards. Call your Cisco technical support representative for assistance if this message persists.
Error Message
%FABRIC-3-INIT: Bad Configuration master_sca = [hex] csc_installed = [hex]Explanation The configuration of clock scheduler cards and switch cards is incorrect.
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
%FABRIC-3-LOS: LOS for slot [int] was [chars]Explanation A loss of synchronization between the line card and the switch card has been detected or cleared. The data shows the fabric card(s) where the errors were detected.
Recommended Action Try reseating the boards. Call your Cisco technical support representative for assistance if this message persists.
Error Message
%FABRIC-3-PARITYERR: [chars] parity error was detected. [chars] Data = 0x[hex]Explanation A parity error has been detected by the Fabric Interface ASIC (FIA) hardware.
Recommended Action The device will be reset. If the problem persists, the card will be automatically reset. Call your Cisco technical support representative for assistance if this message persists.
Error Message
%FABRIC-3-REQUESTERR: Request error was detected. Type = [dec]Explanation A request error was detected by the Fabric Interface ASIC (FIA) hardware.
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
%FABRIC-3-UNEXPECTED: Unexpected interrupt was detected from the [chars] FIAExplanation An unexpected interrupt has been detected by the Fabric Interface ASIC (FIA) hardware.
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.
The following are fan error messages.
Error Message
%FAN-3-FAN_FAILED: Fan [dec] had a rotation error reportedExplanation The fan is not rotating properly.
Recommended Action Replace the fan.
Error Message
%FAN-3-FAN_OK: Fan [dec] had earlier reported a rotation error. It is ok nowExplanation The fan had reported a rotation error but is now functioning properly.
Recommended Action No action is required.
The following are Cisco AS5800 feature board error messages.
Error Message
%FB-3-AGENTSTATUS: Invalid change from [chars] ([dec]) to [chars] ([dec]) for slot [dec]Explanation The software detected an invalid state change for the maintenance bus (MBus) agent of the specified slot. This is a software error.
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
%FB-2-BADPORT: Out of range PCI port [dec]Explanation The software has specified an out-of-range port on the feature board. This is a software error.
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
%FB-3-EVENT: Unknown event [dec] for slot [dec]Explanation The software has generated an unknown event for the specified slot. This is a software error.
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
%FB-3-INVALIDSLOT: Invalid [chars] feature board present in slot [dec]Explanation A feature board has been inserted into a restricted slot. This is not permitted.
Recommended Action Reinsert the feature board into the appropriate slot.
Error Message
%FB-3-SLOTSTATUS: Invalid change from [chars] ([dec]) to [chars] ([dec]) for slot [dec]Explanation The software has detected an invalid state change for the specified slot. This is a software error.
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
%FB-6-OIR: Card in slot [dec] [chars]Explanation A dial shelf feature card has been inserted into or removed from the specified slot.
Recommended Action No action is required.
The following are Cisco 5800 feature board crash information subsystem error messages.
Error Message
%FBINFO-3-CRASH: Feature board in slot [int] crashedExplanation The feature board in the slot indicated went down and sent a "CRASH_START" message to the dial shelf interconnect (DSI). The DSI is now waiting for the rest of the crash information (stack trace, context, and version) from the line card to be sent by the maintenance bus (MBus). The crash information is sent a few milliseconds after the "CRASH_START" message is received. The DSI software will be notified of the line card crash after all the crash information has been sent to the DSI. In the unlikely event that the subsequent crash information messages are not received by the DSI within a reasonable time limit (perhaps 10 seconds), the DSI will print a "TIMEOUT" error message that confirms that the subsequent crash information was not received by the DSI.
Recommended Action Report this defect with as much information as possible about the failing feature board, including the output of the show context summary command, the show context slot n command, and the show tech-support n command, in addition to the usual information gathered by entering the show tech-support command from the router shelf (RS).
Error Message
%FBINFO-3-INVDEV: Invalid feature board number in MBUS callback (LC=[int])Explanation The feature board failure information subsystem on the dial shelf interface (DSI) was called from the maintenance bus (MBus) subsystem with an invalid DEVICE identifier. The DEVICE in this case is supposed to be the slot number of the line card, but it was out of range. This error indicates a software defect in the system.
Recommended Action Report this defect with as much information as possible about the MBus subsystem as possible. There is no adverse effect to the DSI. The DSI will ignore the bad callback and continue. If the problem persists, reboot the router. It is unlikely but possible that the problem is caused by defective MBus hardware somewhere in the system, most likely the DSI MBus module.
Error Message
%FBINFO-3-INVSTATE: Feature board crash server in bad state (LC=[int], state=[int])Explanation The feature board crash information subsystem for the feature board indicates that it is in an unknown state. This problem is caused by a software defect in that subsystem.
Recommended Action Report this defect with as much information as possible about the maintenance bus (MBus) subsystem and the feature board crash information subsystem.
Error Message
%FBINFO-3-NOPROCESS: Failed creating feature board complete processExplanation When creating the crash complete process for the crash information subsystem the create_process call failed. The create_process should not fail. This problem is caused by a software defect or a hardware failure. This failure should happen only during initialization.
Recommended Action Rebooting the system should fix this. If the condition persists on subsequent reloads of the system, a bug report should be filed and the system should be reloaded with a different image.
Error Message
%FBINFO-3-TIMEOUT: Timeout waiting for crash info from slot [int]Explanation The crash information complete timer expired. When a feature board crashes, it sends information to the dial shelf interconnect (DSI) for debugging and analysis. When the "START OF CRASH" message is received, a timer is set for approximately 10 seconds. The line card has 10 seconds to send all the crash information to the DSI. This process is not a crash dump. Only a small amount of information, which usually includes context and stack trace, will be included. If an "END OF CRASH" information message is not received before the timer goes off, the crash information record is closed, this message is displayed, and the rest of the system is notified that the feature board failed (at which point it probably reloaded). If the feature board sends more crash information, after the timer goes off and before the system resets, the additional feature board "UNXMSG" error message might be displayed.
Recommended Action No action is required specifically because this message was displayed. However, since the feature board was failing, there might be other defects to report. If this message is seen and a feature board has not failed, report this defect with the output of the show tech-support commands on the router shelf (RS) and on the feature board that did not crash but was mentioned in this error message.
Error Message
%FBINFO-4-TRUNC: Crash record ([int]=[chars]) truncated (expected=[int], actual=[int])Explanation A feature board failed and was sending details of the failure to the router shelf (RS). The RS received a "CRASH RECORD START" message that indicated how many bytes of data would be sent. Before the indicated number of bytes had been received, the RS received another "CRASH RECORD START" message indicating the start of another record. The record in progress was marked as truncated, and the next record was received, but the truncation of the first message is noted in this later message. The receipt of the second message indicates that there may be more hardware failures in addition to the line card failure that resulted in the sending of the first "CRASH RECORD START" message.
Recommended Action Report this defect with as much information about the maintenance bus (MBus) subsystem and the line card crash information subsystem possible.
Error Message
%FBINFO-4-UNXMSG: Unexpected crash info msg type ([chars]) in state [chars] (LC=[int])Explanation The feature board crash information subsystem has received a message that is unexpected for the state it is in. The state and message type are given in the error message. This message does not have any adverse effect on the dial shelf interconnect (DSI). The DSI will ignore the message and recover from this occurrence. This message could occur if a feature board is failing. The source of the failure on the line card is more significant. If this message occurs without the crashing of a line card, it is caused by a stray or errant maintenance bus (MBus) message that should be researched. This problem could also be the result of a dropped MBus message.
Recommended Action Find the source of the crash on the feature board if one was failing when the message occurred. If no feature board was failing, report this defect as soon as possible and with as much information as possible about the MBus subsystem and the feature board crash information subsystem. If this message recurs, reboot the router to remove this message.
The following are Fiber Distributed Data Interface (FDDI) error messages.
Error Message
%FDDI-3-BADSLOT: Unit [dec], Slot [dec] does not existExplanation The main processor detects an invalid slot location for one of the network interface cards. This should never happen.
Recommended Action Call your Cisco technical support representative to obtain a replacement card.
Error Message
%FDDI-3-BADUNIT: msgtxt_badunitExplanation This error message is displayed when the system cannot find the chipset registers where it expects them to be. This is most likely a hardware error.
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
%FDDI-3-FDDIFAIL: Interface [chars], [chars], [chars] = [hex]Explanation The FDDI interface has failed. An "FDDIFAIL" message will follow with debug information.
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
%FDDI-3-FDDIFAIL2: Interface [chars], [chars], [chars] = [hex], [chars] = [hex]Explanation The FDDI interface has failed. This message appears as the second line of the preceding "FDDIFAIL2" message. This message contains debug information.
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
%FDDI-3-NOCAM: Unit [dec], No CAM exists for this interface.Explanation A hardware or software ERROR has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%FDDI-1-NOMEMORY: msgtxt_nomemoryExplanation The FDDI Management Information Base/Station Management (MIB/SMT) processing functions could not initialize because of insufficient 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.
The following are file system error messages.
Error Message
%FILESYS-5-DEV: PCMCIA flash card [chars] [chars]Explanation The status of a file system has changed.
Explanation Follow any instructions provided with the message. No action is required.
Error Message
%FILESYS-3-FLASH: [chars] [chars] error [dec]Explanation A file system 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.
The following are LS1010 chip-specific error messages.
Error Message
%FPGA-3-DOWNLOAD: Download Fail, FPGA# [dec]Explanation An Field Programmable Gate-Array (FPGA) download has failed.
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
%FPGA-3-MCAST: Multicast FPGA don't reset properly, Control Register=[hex]Explanation The Multicast Field Programmable Gate-Array (FPGA) chip failed to respond after downloading its control microcode. This error is probably caused by a hardware failure. It is a fatal condition for the system and will be followed by a core dump.
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
%FPGA-3-NOFORK:Explanation The per-VC counter daemon could not be created.
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
%FPGA-3-STATUS_PIN: Error in status pin, FPGA# [dec]Explanation A status pin error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%FPGA-3-TRAFF: Traffic FPGA don't reset properly, Control Register=[hex]Explanation The traffic Field Programmable Gate-Array (FPGA) does not reset properly.
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
%FPGA-3-TYPE: ***WARNING*** Invalid feature card type - Use higher version of software: [hex]Explanation An invalid feature card type was used. A higher version of Cisco IOS software is required.
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
%FPGA-3-VERSION: Feature Card version invalid/old. Feature Card Version:[dec].[dec], ASP Version:[dec].[dec]Explanation The feature card version is not valid.
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.
The following are Frame Relay error messages.
Error Message
%FR-3-BQ_DEQ_ERR: fr_bq_proc: unknown packet on broadcast queue, packet droppedExplanation An invalid packet on the Frame Relay broadcast queue was dropped.
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
%FR-3-BQ_DEQ_PTR: fr_br_proc: hdr-[hex] size-[dec] dlci-[hex] [hex] [hex]Explanation An invalid datagram start was received on the Frame Relay broadcast queue. The packet was dropped.
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
%FR-3-BQ_ENQ_ERR: fr_oqueue: Invalid datagramstart [hex] [hex], pak droppedExplanation A broadcast packet with an invalid datagram start in the fr_oqueue has been received. The packet was dropped.
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
%FR-5-DLCICHANGE: Interface [chars] - DLCI [dec] state changed to [chars]Explanation The state of the Frame Relay permanent virtual circuit (PVC) specified by the data-link connection identifier (DLCI) has changed.
Recommended Action No action is required.
Error Message
%FR-4-DLCIDELETE: Interface [chars] - DLCI [dec] - PVC use count [dec]Explanation An attempt was made to remove a permanent virtual circuit (PVC) data-link connection identifier (DLCI) while it was still being used.
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
%FR-3-INCORRECT_INT: Incorrect output (sub)interface, broadcast packet droppedExplanation The output subinterface specified in the packet is incorrect. The broadcast packet was dropped.
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
%FR-4-NNISUBINTF: Subinterface not supported on Frame Relay NNIExplanation An attempt was made to change the state of a subinterface on the Frame Relay Network-to-Network Interface (NNI).
Recommended Action Reconfigure the Frame Relay link type or remove the subinterface.
Error Message
%FR-3-NOMEMORY: No memory for [chars]Explanation The requested operation could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
The following are Frame Relay/ATM interworking error messages.
Error Message
%FRATM-3-CONFIG_ERROR: [chars]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
%FRATM-2-INTERNAL_CRITICAL: [chars]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
%FRATM-3-INTERNAL_ERROR: [chars]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
%FRATM-4-INTERNAL_WARNING: [chars]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.
The following are CT3 trunk card Freedm error messages.
Error Message
%FREEDM-3-BUSYTIMEOUT: Freedm [chars] busy bit of register 0x[hex] never clearedExplanation The driver has timed out while waiting for the Freedm to acknowledge a request.
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
%FREEDM-2-FATALEVENT: Freedm [chars] fatal event occured: [hex][hex]Explanation A catastrophic Freedm error has occured.
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
%FREEDM-3-HDLC_ALLOC_FAIL: Freedm [chars]: Allocation of HDLC controller [dec] for channel [dec] failedExplanation Allocation of a High-Level Data Link Control (HDLC) controller has failed.
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
%FREEDM-3-HDLC_INUSE: Freedm [chars]: HDLC controller [dec] already in use on channel [dec]Explanation An attempt was made to use an High-Level Data Link Control (HDLC) controller that was already in use.
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
%FREEDM-3-INITFAIL: Freedm [chars] initialization failed: [chars]Explanation The Freedm device has failed initialization.
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
%FREEDM-3-NOTFREEDM: Freedm [chars] returned device/vendor of [hex]Explanation The protocol control information (PCI) device has returned an unrecognized value.
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.
The following are Frame Relay enhanced Local Management Interface (LMI) error messages.
Error Message
%FR_ELMI-3-INCORRECT_ID: Incorrect IDExplanation An incorrect ID was report in a quality of service (QoS) parameter message.
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
%FR_ELMI-3-INCORRECT_IE: Incorrect IEExplanation Enhanced Local Management Interface (LMI) is not configured on the interface. The frame was dropped.
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.
The following are Frame Relay Local Management Interface (LMI) error messages.
Error Message
%FR_LMI-3-INCORRECT_IE: Enhanced LMI not configured, incorrect IEExplanation An unexpected Local Management Interface (LMI) information element has been received.
Recommended Action Ensure that the configuration for enhanced Local Management Interface (LMI) on the switch matches the configuration on the router.
The following are Cisco 3801 platform error messages.
Error Message
%FTC_TRUNK-3-CID_IN_USE: [chars] connection-id [dec] is busy, try other cidExplanation When setting up a new session trunk, an operator has attempted to use a connection ID that is already assigned and in use.The selected connection id cannot be used for this session trunk.
Recommended Action Try to set up the new session trunk with a connection ID that is not already in use.
Error Message
%FTC_TRUNK-1-NOMEMORY: msgtxt_nomemoryExplanation The MPC860/PowerQUICC CPU was unable to access the memory it requires to carry out its functions. Here are some possible causes. The network is large, requiring a significant amount of memory for routing tables, and so on. The router configuration has many features enabled, each of which require a certain amount of memory. A software error (memory leak) exists.
Recommended Action Reduce system activity to ease the memory demand, or upgrade to a larger memory configuration.
Error Message
%FTC_TRUNK-1-RELOAD: Must reload to config Interface [chars] as ftc-trunk againExplanation If the operator first configures an interface based on the use of the encapsulation ftc-trunk command and later reconfigures the interface to some other encapsulation, such as High-Level Data Link Control (HDLC), and then attempts to reconfigure it based on the encap ftc-trunk command specifications, this error message is displayed to notify the operator that the reload command must first be entered before using the encap ftc-trunk command.
Recommended Action Enter the reload command.
Error Message
%FTC_TRUNK-3-TOOMANY: Cannot config more than [dec] ftc-trunksExplanation When the operator enters the encap ftc-trunk configuration command, if there are already four interfaces configured with the encap ftc-trunk command, this message is displayed to indicate that no more interfaces can be configured with this command.
Recommended Action Free up one of the other interfaces first or, if conditions warrant, upgrade to a larger configuration with more interfaces.
Error Message
%FTC_TRUNK-3-TOOMANY_SESSION: Cannot config more than [dec] session-trunksExplanation When the operator enters the encap ftc-trunk configuration command, if there are already four interfaces configured with the encap ftc-trunk command, this message is displayed to indicate that no more interfaces can be configured with this command.
Recommended Action Free up one of the other interfaces first or, if conditions warrant, upgrade to a larger configuration with more interfaces.
The following are File Transfer Protocol (FTP) server processes error messages.
Error Message
%FTPSERVER-6-CONNCLOSED: Connection closed after [dec] seconds. '[chars]'Explanation The File Transfer Protocol (FTP) connection to a client was closed after five minutes of inactivity.
Recommended Action Client inactivity will cause the server to close the connection. Restart FTP.
Error Message
%FTPSERVER-6-CWDFAILED: setcwd failed ([chars])Explanation A File Transfer Protocol (FTP) client request has failed to change to the requested directory.
Recommended Action Verify the correct path for the desired directory.
Error Message
%FTPSERVER-6-NETRDFAILED: FTP control connection / tcp_read failedExplanation An error occured while the command line from the File Transfer Protocol (FTP) client was being read.
Recommended Action Verify the network connection from the client to the server. Verify the FTP client operation.
Error Message
%FTPSERVER-6-NETWRTFAILED: FTP Server:connection / tcp_write failedExplanation A TCP write failed while sending an File Transfer Protocol (FTP) command reply to the client.
Recommended Action Verify the network connection from the client to the server. Verify the FTP client operation.
Error Message
%FTPSERVER-6-NEWCONN: FTP Server - new connection madeExplanation A new File Transfer Protocol (FTP) server connection has opened.
Recommended Action To disable the new FTP server connection, use the no ftp-server enable command in global configuration mode.
Error Message
%FTPSERVER-6-REPLYLOGN: (REPLY) [dec]Explanation An File Transfer Protocol (FTP) login has occurred.
Recommended Action This is an informational message only. Informational messages can be disabled by changing the logging level.
Error Message
%FTPSERVER-6-REPLYLOGTEXT: [dec][chars]Explanation This text was sent to the File Transfer Protocol (FTP) client.
Recommended Action This is an informational message only. Informational messages can be disabled by changing the logging level.
Error Message
%FTPSERVER-6-TOPDIRTEST: Input path failed Top-dir([chars]) testExplanation An operation has attempted to use a path that was not within the tree under the ftp-server topdir configuration parameter.
Recommended Action Reconfigure the server topdir parameter, or select another path.
Error Message
%FTPSERVER-4-XFER_WARNING: File may not have transferred correctlyExplanation Extra line feeds were received in ASCII mode.
Recommended Action If the file is not error-free, try using a different File Transfer Protocol (FTP) client.
The following are Fax Telephony Service Provider subsystem error messages.
Error Message
%FTSP-6-FAX_CONNECT: [chars]Explanation A fax carrier has been detected.
Recommended Action No action is required.
Error Message
%FTSP-6-FAX_DISCONNECT: [chars]Explanation A fax call has disconnected.
Recommended Action No action is required.
Error Message
%FTSP-4-FMAIL_FAILED_AUTHENTICATION: Authentication for > [chars] < failedExplanation An attempt to authenticate the specified user has failed.
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
%FTSP-4-FMAIL_NO_ACCOUNTING: FAXMAIL- Accounting or tty([dec]) failedExplanation Accounting has failed for the specified tty.
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
%FTSP-4-HARDWARE_ERROR: tty ([dec])Explanation A hardware interface had not been configured before a fax call was answered or attempted.
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
%FTSP-2-INTERNAL_ERROR: Internal software error. [chars]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, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%FTSP-1-NOMEMORY: msgtxt_nomemoryExplanation The requested operation could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message
%FTSP-4-UNEXPECTEDEVENT: Bad event received d, [dec]Explanation An unexpected event was received.
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.
The following are inspection subsystem error messages.
Error Message
%FW-4-ALERT_OFF: [chars], count ([dec]/[dec]) current 1-min rate: [dec]Explanation Either the number of half-open connections or the new connection initiation rate has gone below the max-incomplete low threshold. This message indicates that the rate of incoming new connections has slowed down and is issued only when the max-incomplete low threshold is crossed.
Recommended Action This message is for informational purposes only, but it may indicate that an attack has stopped.
Error Message
%FW-4-ALERT_ON: [chars], count ([dec]/[dec]) current 1-min rate: [dec]Explanation Either the max-incomplete high threshold of half-open connections or the new connection initiation rate has been exceeded. This error message indicates that an unusually high rate of new connections is coming through the firewall, and a DOS attack may be in progress. This message is issued only when the max-incomplete high threshold is crossed.
Recommended Action This message is for informational purposes only, but it may indicate a security problem.
Error Message
%FW-2-BLOCK_HOST: Blocking new TCP connections to host [int] for [dec] minute[chars] (half-open count [dec] exceeded)Explanation Any subsequent new TCP connection attempts to the specified host will be denied because the max-incomplete host threshold of half-open TCP connections is exceeded, and the blocking option is configured to block the subsequent new connections. The blocking will be removed when the configured block time expires.
Recommended Action This message is for informational purposes only, but it may indicate that a SYN flood attack was attempted.
Error Message
%FW-3-FTP_NON_MATCHING_IP_ADDR: Non-matching address [int] used in [chars] -- FTP client [int] FTP server [int]Explanation An File Transfer Protocol (FTP) client has attempted to use a PORT command or the FTP server has attempted to use the response to a PASV command to trick the firewall into opening access to a third-party host that is different from the two hosts engaged in the FTP connection. This message indicates that a suspicious violation was detected while attempting to modify the security policy in the firewall. The command is rejected and the connection is reset by the firewall.
Recommended Action This message is for informational purposes only, but it may indicate that an attempt was made to grant or open access to unauthorized hosts.
Error Message
%FW-3-FTP_PRIV_PORT: Privileged port [dec] used in [chars] -- FTP client [int] FTP server [int]Explanation An File Transfer Protocol (FTP) client attempted to use a PORT command or the FTP server has attempted to use the response to a PASV command to trick the firewall into opening access to a privileged port. This message indicates that a suspicious violation was detected from the FTP client/server attempting to modify the security policy in the firewall. The command is rejected and the connection is reset by the firewall.
Recommended Action This message is for informational purposes only, but it may indicate that an attempt was made to gain access to privileged ports.
Error Message
%FW-3-FTP_SESSION_NOT_AUTHENTICATED: Command issued before the session is authenticated -- FTP client [int] FTP server [int]Explanation An File Transfer Protocol (FTP) client has attempted to use the PORT command or an FTP server has attempted to use the response to a PASV command to open a data channel in the firewall prior to the client's completing a successful authentication with the server. This is a suspicious attempt by the client/server to trick the firewall into opening a hole so that outside attackers can take advantage of the firewall opening. This message indicates that a suspicious violation was detected, and the PORT or PASV command or response is rejected by the firewall. The data channel in the firewall will not be opened until the authentication is successfully completed.
Recommended Action This message is for informational purposes only, but it may indicate that an illegal attempt was made to modify the firewall security policy.
Error Message
%FW-4-HOST_TCP_ALERT_ON: Max tcp half-open connections ([dec]) exceeded for host [int]Explanation The max-incomplete host limit of half-open TCP connections has been exceeded. This message indicates that a high number of half-open connections is coming to the protected server, and it may indicate that a SYN flood attack is in progress and is targeted to the specified server host.
Recommended Action This message is for informational purposes only, but it may indicate that a SYN flood attack was attempted. If this alert is issued frequently and identified to be mostly false alarms, then the max-incomplete host threshold value is probably set too low, and there is a significant amount of legitimate traffic coming into that server. In this case, the max-incomplete host parameter should be set to a higher number to avoid false alarms.
Error Message
%FW-3-HTTP_JAVA_BLOCK: JAVA applet is blocked from ([int]:[dec]) to ([int]:[dec]Explanation A Java applet was seen in the HTTP channel, and the firewall configuration indicates that the applet from this Web site should be prohibited. The message indicates that the applet is being downloaded from one of the prohibited sites and its entrance to the protected network is not allowed. The connection is reset and the transmission of the detected applet is immediately aborted.
Recommended Action This message is for informational purposes only, but it may indicate a security problem.
Error Message
%FW-3-NOTFOUND: Session context for ([int]:[dec]) => ([int]:[dec]) not foundExplanation The Context-Based Access Control (CBAC) code was searching its database for information for a particular inspection session, but this information was not found.
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
%FW-3-SMTP_INVALID_COMMAND: Invalid SMTP command from initiator ([int]:[dec])Explanation The Context-Based Access Control (CBAC) code detected an invalid Simple Mail Transfer Protocol (SMTP) command in the inspected SMTP connection. This message indicates that a suspicious violation was detected that may be an attack on the mail server system. The command is rejected and the connection is reset immediately by the firewall .
Recommended Action This message is for informational purposes only, but it may indicate a security problem.
Error Message
%FW-4-TCP_MAJORDOMO_EXEC_BUG: Majordomo Execute Attack - from [int] to [int]Explanation A bug in the Majordomo program will allow remote users to execute arbitrary commands at the privilege level of the server.
Recommended Action For security reasons, users should not be allowed to execute programs through e-mail servers. This message is a very serious indication that your network may be under attack and the source should be blocked immediately.
Error Message
%FW-4-TCP_SENDMAIL_BAD_FROM_SIG: Sendmail Invalid Sender - from [int] to [int]Explanation This message appears whenever an e-mail message has a pipe symbol (|) in the "From:" field.
Recommended Action For security reasons users should not be allowed to execute programs through e-mail servers. This message is a very serious indication that your network may be under attack and the source should be blocked immediately.
Error Message
%FW-4-TCP_SENDMAIL_BAD_TO_SIG: Sendmail Invalid Recipient - from [int] to [int]Explanation This message appears whenever an e-mail message has a pipe symbol (|) in the recipient field.
Recommended Action For security reasons, users should not be allowed to execute programs through e-mail servers. This message is a very serious indication that your network may be under attack and the source should be blocked immediately.
Error Message
%FW-4-TCP_SENDMAIL_DECODE: Sendmail Decode Alias - from [int] to [int]Explanation This message appears whenever an e-mail message has "decode@" in the header. The "decode" alias is used to decode files and is implemented primarily as a convenience for system administration.
Recommended Action For security reasons, users should not be allowed to execute programs through e-mail servers. This message is a very serious indication that your network may be under attack and the source should be blocked immediately.
Error Message
%FW-4-TCP_SENDMAIL_INVALID_COMMAND: Invalid SMTP command - [int] to [int]Explanation This message appears whenever an invalid Simple Mail Transfer Protocol (SMTP) command is reported in the SMTP connection. This message indicates that a suspicious violation was detected that may be an attack on the mail server system.
Recommended Action This is unusual traffic and may warrant investigation.
Error Message
%FW-6-SESS_AUDIT_TRAIL: [chars] session initiator ([int]:[dec]) sent [int] bytes -- responder ([int]:[dec]) sent [int] bytesExplanation This message documents the per-session transaction log of network activities. The message is issued at the end of each inspected session and it records the source and destination addresses and ports, as well as the number of bytes transmitted by the client and server.
Recommended Action This message is for informational purposes only and can be used to collect the basic accounting for the inspected sessions.
Error Message
%FW-4-TCP_SENDMAIL_OLD_SIG: Archaic Sendmail Attacks - from [int] to [int]Explanation This message appears whenever wiz or debug commands are sent to the Simple Mail Transfer Protocol (SMTP) port.
Recommended Action For security reasons, users should not be allowed to execute programs through e-mail servers. This message is a very serious indication that your network may be under attack and the source should be blocked immediately.
Error Message
%FW-4-UNBLOCK_HOST: New TCP connections to host [int] no longer blockedExplanation New TCP connection attempts to the specified host are no longer being blocked. This message indicates that the blocking of new TCP connection attempts to the specified host has been lifted.
Recommended Action This message is for informational purposes only, but it may indicate that a SYN flood attack was attempted on the host.
The following are FX1000 Gigabit Ethernet controller error messages.
Error Message
%FX1000-1-DISCOVER: Only found [dec] interfaces on bay [dec], shutting down bayExplanation A possible hardware error resulted in the discovery of too few Gigabit Ethernet interfaces.
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
%FX1000-3-ERRINT: [chars], error interrupt, csr_STATUS=[hex]Explanation The Gigabit Ethernet controller has signaled an error condition.
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
%FX1000-1-INITFAIL_NOMEM: [chars], initialization failed, no buffer memoryExplanation The Gigabit Ethernet port initialization has failed because of insufficient memory.
Recommended Action Upgrade the GEIP with a larger memory model. If the message recurs, copy the error message exactly as 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
%FX1000-5-LOSTCARR: [chars] cable/transceiver problem?Explanation The Gigabit Ethernet port detects link failure, meaning that it is no longer receiving signals from the LAN. This problem can result from a disconnected Gigabit Ethernet cabling, a transceiver (GBIC) failure, or a shutdown on the remote end.
Recommended Action Check your Gigabit Ethernet wiring and port adapter. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%FX1000-2-NOISL: Interface [chars] does not support ISLExplanation The Inter-Switch Link (ISL) is not supported on the hardware of the specified interface.
Recommended Action No action is required.
Error Message
%FX1000-3-NOTFX1000: slot[[dec],[dec]] detects unknown PCI device (id=0x[hex])Explanation The Gigabit Ethernet port adapter does not contain a gigabit controller chip.
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
%FX1000-3-TOOBIG: [chars], packet too big ([dec]), from [sci_notation]Explanation The interface has detected a packet larger than what is defined by the maximum transmission unit (MTU).
Recommended Action Check the MTU setting of the other station. No other action is required.
Posted: Fri Jun 16 11:49:49 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.