-
Cisco IOS Release 12.4 System Messages, Volume 1 of 2
-
System Messages Overview
-
AAA through ASPP
-
AT through BGP
-
BIT through C6KPWR
-
C6MSFC through CHOPIN_MAINBOARD_ASYNC_PQII
-
CI through COT
-
CPAD through DBUS
-
DCV through DSCREDCLK
-
DSI through ENT
-
ENV_MON through FR_FRAG
-
FR_LMI through GSR_ENV
-
GSRIPC through IF
-
IFINDEX through ISA
-
ISDN through LCCOREDUMP
-
LCINFO through MBRI
-
Volume 1 Glossary
-
Table Of Contents
ENV_MON Messages
The following are Cisco 12000 platform environmental monitor messages.
Error Message%ENV_MON-2-FAN : Fan array has reached [chars] level.
Explanation There might be a hardware problem with the fan array. If the error condition continues for two minutes, the router shuts down automatically to prevent damage to router components.
Recommended Action If the system shuts down, replace the fan tray. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ENV_MON-2-FANOK : Fan array has recovered.
Explanation 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 shutdown
Explanation 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 cannot be resolved, contact your Cisco technical support representative for assistance.
Error Message%ENV_MON-2-SUPPLY : [chars] Power Supply is Non-Operational
Explanation A power supply is not working or has not been turned on.
Recommended Action Check that the power supply is on; if it is on and still does not operate, contact 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 and has reached or exceeded a condition that is outside its acceptable range.
Recommended Action Attempt to resolve the temperature problem. If the problem cannot be resolved, contact 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. A software error may have occurred, or the MBus data may have been corrupted.
Recommended Action 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 was received from an unknown supply. A software error may have occurred, or the MBus data may have been corrupted.
Recommended Action 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 contact your Cisco technical support representative for the repair or replacement of the equipment.
ENVM Messages
The following are environmental monitor messages.
Error Message%ENVM-3-BLOWER : [chars] may have failed
Explanation 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-1-CAN_NOT_POWER_ON_DFC : Can't power on DFC on slot [dec] for unknown reason.\n
Explanation A DFC has failed to power on.
Recommended Action Check the power plug to the DFC on the slot. If the DFC still fails to power on, unplug and perform diagnostics on the DFC.
Error Message%ENVM-3-CPUCARD : Unknown CPU type [dec]
Explanation A CPU card in the system was not recognized by the software.
Recommended Action Ensure that the image you are loading supports the NPE in the chassis. Enter the show version command. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ENVM-2-CRITICAL : [chars] measured at [chars]
Explanation One of the measured environmental test points for voltage or temperature, as indicated by the message, has exceeded a critical level.
Recommended Action Correct the specified condition as quickly as possible or take the system offline and power down. If the system fails, it shuts down automatically as a preventive measure.
If the message is a temperature warning, perform the following checks:
1.
Ensure that a fan in a power supply module or a fan module has not failed.
2.
3.
If it is a voltage problem on multiple cards, check your input AC/DC voltage source. If it is a voltage problem on a single card, ensure that a backup or spare card is available for replacement in case the voltage continues to deteriorate on that card.
If you think the message is in error, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ENVM-1-DFC_BUSYOUT : All DFCs are busy out due to board over temperature.\n
Explanation The system has experienced an over-temperature condition. For the Cisco AS5350 and AS5400: all DFCs are busy out to prevent the DFCs from damage and to cool the temperature of the system.
Recommended Action Check the air conditioning and the surrounding area of the Cisco AS5350 and AS5400. Enter the show environment command to display temperature data and compare that data with a temperature meter.
Error Message%ENVM-1-DFC_POWER_DOWN : A DFC is powered down due to board over-temperature. Slot: [dec], Type: [chars]\n
Explanation The system has experienced an over-temperature condition. For the Cisco AS5350 and AS5400: a DFC is powered down to prevent the DFC from damage and to cool the temperature of the system.
Recommended Action Check the air conditioning and the surrounding area of the Cisco AS5350 and AS5400. Enter the show environment command to display temperature data and compare that data with a temperature meter.
Error Message%ENVM-1-DFC_POWER_ON : A DFC is powered on due to board temperature cooling down. Slot: [dec], Type: [chars]\n
Explanation The temperature in the system has cooled down, and the DFC has been powered back on.
Recommended Action For the Cisco AS5350 and AS5400: when the board temperature cools down, a DFC is powered on and begins working. Enter the show environment command to display temperature data and compare that data with a temperature meter to verify the recovery.
Error Message%ENVM-1-DFC_UNBUSYOUT : All DFCs are unbusy out due to board temperature cooling down.\n
Explanation The system has experienced an over-temperature condition.
Recommended Action For the Cisco AS5350 and AS5400: when the board temperature cools down, all DFCs are unbusy out and resume working. Enter the show environment command to display temperature data and compare that data with a temperature meter to verify the recovery.
Error Message%ENVM-3-DISABLE_ENVM : AS5400/AS5350 Environmental Monitor is disabled.\n
Explanation A configuration command can disable the Cisco AS5350 or AS5400 environmental monitor when a user does not need it in certain situations.
Recommended Action For the Cisco AS5350 and AS5400: after the environmental monitor is disabled, both a console message and an SNMP trap are sent out. No action is required.
Error Message%ENVM-1-DROP_FAN_MONITOR : Environmental Monitor of Fans is dropped.\n
Explanation If a temperature sensor at an inlet or outlet fails to work, the system no longer performs environmental monitoring of the fans.
Recommended Action For the Cisco AS5350 and AS5400: after the fan monitoring is dropped, only a console message is sent out and the alarm is activated. Enter the show environment command to display temperature data and compare that data with the data received from a temperature meter. If the sensor has failed, contact your Cisco technical support representative to replace the temperature sensor.
Error Message%ENVM-1-DROP_TEMP_MONITOR : Environmental Monitor of Temperature is dropped.\n
Explanation If all temperature sensors fail to work, the system no longer performs environmental monitoring of the temperature.
Recommended Action For the Cisco AS5350 and AS5400: after the temperature monitoring is dropped, only a console message is sent out and the alarm is activated. Enter the show environment command to display temperature data and compare that data with the data received from a temperature meter. If the sensor has failed, contact your Cisco technical support representative to replace the temperature sensor.
Error Message%ENVM-3-ENABLE_ENVM : AS5400/AS5350 Environmental Monitor is enabled.\n
Explanation A configuration command can enable the Cisco AS5350 and AS5400 environmental monitor after it was disabled in certain situations.
Recommended Action For the Cisco AS5350 and AS5400: after the environmental monitor is enabled, both a console message and an SNMP trap are sent, and all the actions of the environmental monitor are taken if necessary.
Error Message%ENVM-2-ENVCRIT : [chars] measured at [chars]
Explanation One of the measured environmental test points exceeds an extreme threshold.
Recommended Action Correct the specified condition or the system might shut down as a preventive measure. This condition could cause the system to fail to operate properly. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ENVM-3-ENVDATA : Environment data in [chars] invalid at slot [dec]
Explanation The environmental threshold data in the ID EEPROM of the system board is corrupted.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show diag slot-number command, with slot-number being the slot number of the affected card. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support and show diag slot-number commands and your pertinent troubleshooting logs.
Error Message%ENVM-4-ENVM_NULL : [chars]
Explanation The software pointer for the environmental monitor table is empty. The platform subsystem may not have been initialized properly.
Recommended Action Shut down and restart the system. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ENVM-4-ENVM_TBL_NULL : [chars]
Explanation The pointer table for a temperature, voltage, or power supply environmental component is empty. The platform subsystem may not have been initialized properly.
Recommended Action Shut down and restart the system. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ENVM-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 this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ENVM-3-FAN_FAIL : [chars] fail to work.\n
Explanation Some cooling fans have failed to work. This situation is detected by the temperature delta between the inlet and outlet. A large temperature delta indicates a fan failure.
Recommended Action Replace the fan as soon as possible, or the system may shut itself down or fail to operate properly.
Error Message%ENVM-3-FAN_OK : [chars] recovered to work.\n
Explanation Some cooling fans have recovered. This situation is detected by the temperature delta between the inlet and outlet. A small temperature delta indicates fan recovery.
Recommended Action Verify that the fans are working properly by checking the four fans. Enter the show environment command to display temperature delta data and verify the recovery.
Error Message%ENVM-6-FANCHANGE : [chars] changed from [chars] to [chars]
Explanation The fan has changed its status because of the removal or insertion of a fan module in the system.
Recommended Action This is an informational message only. No action is required.
Error Message%ENVM-6-FANMISSING : Fan may have been removed
Explanation The software has detected that a fan is missing. If the system is not using a redundant power supply module, a fan module might be missing from the power supply bay.
Recommended Action Ensure that you have installed two power supply modules or one power supply module and one fan module. If the error message recurs despite the installation of the correct number of power supply and fan modules, copy the message exactly as it appears on the console or in the system log, and enter the show diag chassis command. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show diag chassis, show logging, and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ENVM-3-FRUUNKNOWN : Power supply or fan module in bay [dec] type unknown
Explanation The power supply or fan module type is unknown. The ID EEPROM of the module might not have been programmed or might have been corrupted, or the module might be an unsupported type.
Recommended Action Use only system-supported power supply or fan module types.
–
–
–
–
–
Error Message%ENVM-3-IDPROM : Access to [chars] failed at slot [dec]
Explanation Environmental monitoring threshold levels could not be read from the specified ID EEPROM for the specified card. The ID EEPROM is not accessible because of a hardware failure, because of incompatible Cisco IOS software, or because the ID EEPROM contents have been corrupted.
Recommended Action Enter the show diag slot-number command, with slot-number being the slot number of the affected card, and perform one of the following actions:
–
–
Error Message%ENVM-3-IOCARD_REV : [chars]
Explanation The revision number of the I/O card is not known. The I/O card plug-in is not recognized.
Recommended Action Insert the correct version of the I/O card. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ENVM-3-LASTENV : [chars]
Explanation Operational data related to environmental monitoring could not be saved to nonvolatile storage in the chassis backplane EEPROM. This condition can be caused by an EEPROM (hardware) failure.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ENVM-4-LONGBUSY : C2W Interface busy for long time reading temperature sensor [dec]
Explanation Not available.
Recommended Action Not available.
Error Message%ENVM-3-NOACK : Access to [chars] in slot [dec] failed
Explanation Access to one of the temperature sensors failed because the device was not ready. The software will attempt to access the sensor again.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ENVM-3-NOFORK : Could not start environment polling process
Explanation Because the software could not spawn the environmental monitoring process, possibly because of low memory, no monitoring is performed.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%ENVM-1-OIR_POWER_DOWN : Environmental monitor is trying to power down a DFC by simulating OIR removal. Slot: [dec], Type: [chars]\n
Explanation The system experienced an over-temperature condition. For the Cisco AS5350 and AS5400: a DFC has been powered down to prevent the DFC from damage and to cool down the temperature. The environmental monitor applies the scheme of OIR removal to power down the DFC.
Recommended Action Ensure that the ambient temperature of the room is not too high and that air flow to the card is not blocked. Check the air conditioning and the surrounding area of the Cisco AS5350 and AS5400.
Error Message%ENVM-1-OIR_POWER_ON : Environmental monitor is trying to power on a DFC by simulating OIR insertion. Slot: [dec], Type: [chars]\n
Explanation The temperature has cooled down inside the chassis. For the Cisco AS5350 and AS5400: when the board temperature cools down, a DFC has been powered back on and is working. The environmental monitor applies the scheme of OIR insertion to power on the DFC.
Recommended Action No action is required.
Error Message%ENVM-1-OK_FAN_MONITOR : Environmental Monitor of Fans is recovered.
Explanation The temperature sensors at the inlet or outlet have recovered and the environmental monitoring of the fans has recovered.
Recommended Action For the Cisco AS5350 and AS5400: once the fan monitoring is recovered, a console message is sent out and the alarm is disabled. The fan state is set as normal. Enter the show environment command to display temperature data and compare with a temperature meter to verify the recovery.
Error Message%ENVM-1-OK_TEMP_MONITOR : Environmental Monitor of Temperature is recovered.
Explanation The temperature sensor has recovered, and the environmental monitoring of the fans has recovered.
Recommended Action For the AS5350 and AS5400: after temperature monitoring is recovered, a console message is sent out and the alarm is disabled. The temperature state is set as normal. Enter the show environment command to display temperature data and compare that data with the data received from a temperature meter to verify the recovery.
Error Message%ENVM-6-PSCHANGE : [chars] changed from [chars] to [chars]
Explanation A new type of power supply in the system has been detected. This message can be expected when hot-swappable power supplies are swapped. This is an informational message only.
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 if possible. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ENVM-6-PSMISMATCH : Both AC and DC power supplies detected
Explanation A mix of AC and DC power supply modules has been detected. Such a mix is not supported. Both power supply modules must be of the same type, either AC or DC.
Recommended Action Use only one type of power supply. Remove one of the two power supply modules and either replace the removed one with the same type as the other power supply or operate the system on a single power supply.
If you think the message is in error, enter the show diag chassis and show environment all commands. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show commands and your pertinent troubleshooting logs.
Error Message%ENVM-6-PSOK : [chars] now appears to be working correctly.
Explanation The failed power supply has recovered and is now operational.
Recommended Action Check the external connections to the power supply and monitor it for any more failure messages. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ENVM-4-READERROR : Error reading temperature sensor [dec]
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%ENVM-3-REFVOLT : [chars]
Explanation The reference voltage has been measured as zero volts.
Recommended Action If this message is displayed 3 or more times, check the power supply. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ENVM-4-RPSFAIL : [chars] may have a failed channel
Explanation One of the power supplies in a dual (redundant) power supply might have failed.
Recommended Action Check the inputs to the power supply or replace the faulty power supply as soon as possible to avoid an unplanned outage. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ENVM-0-SHUT : Environmental Monitor initiated shutdown
Explanation The environmental monitor has initiated a system shutdown.
Recommended Action Look at previous environmental messages to determine the cause of the shutdown, and correct the condition if possible. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ENVM-0-SHUTDOWN : Environmental Monitor initiated shutdown due to [chars]in slot [dec]
Explanation The environmental monitor initiated a system shutdown because of a temperature or voltage condition.
Recommended Action Read any previous environmental messages to determine the cause of the shutdown and correct the cause, if possible. If you determine that the shutdown was in error, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ENVM-0-STATUS_NOT_READY : Environmental Monitor temperature sensor not ready
Explanation The temperature sensor is not ready.
Recommended Action The temperature hardware might have to be replaced. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ENVM-1-TEMP_SENSOR_FAIL : Temperature sensor #[dec] fails to work.\n
Explanation a sensor generates extraordinary data, such as recording a temperature higher than 200 degrees C; the temperature change exceeds limits in 1 minute, such as 25 degrees C; or the temperature differential between sensors in the same device is greater than the limit, such as 25 degrees C.
Recommended Action For the Cisco AS5350 and AS5400: after the failure of a temperature sensor is detected, the environmental monitor sets the temperature state of that sensor as disabled and sends out a console message. The temperature data from that sensor is ignored in temperature monitoring. Enter the show environment command to display the temperature data and compare that data with a temperature meter. If the sensor has failed, contact your Cisco technical support representative to replace the temperature sensor.
Error Message%ENVM-1-TEMP_SENSOR_OK : Temperature sensor #[dec] recovers to work.
Explanation A sensor generates extraordinary data, such as recording a temperature higher than 200 degrees C; the temperature change exceeds limits in 1 minute, such as 25 degrees C or the temperature differential between sensors is greater than the limit, such as 25 degrees C.
Recommended Action For the Cisco AS3500 and AS5400: Once the recovery of a temperature sensor is detected, the environmental monitor will set the sensor state of that sensor as normal and send a console message. The temperature data from that sensor is read again in temperature monitoring. Enter the show environment command to display temperature data and compare with a temperature meter to verify the recovery.
Error Message%ENVM-1-TEMP_STATE : System detected that temperature is in [chars] condition.
Explanation The environmental monitor detected a temperature change, either failure or recovery.
Recommended Action Ensure that the room temperature is not too high and that air flow to the card is not blocked. If this condition persists, the environmental monitor might shut down the system. Check the air conditioning and the surrounding environment of the Cisco AS5350 or AS5400. If necessary, contact your Cisco technical support representative.
Error Message%ENVM-3-VOLT_NORMAL : System sensor Voltage name: [chars], is now operating under NORMAL voltage at [dec] mV.
Explanation One of the measured environmental test points is below normal operating voltage.
Recommended Action Unavailable.
Error Message%ENVM-1-VOLT_WARNING : Environmental monitor detects voltage out-of-range warning. Voltage name: [chars], Nominal: [dec] Voltage sensor reading: [dec]
Explanation The voltage is either too high or too low. For AS5400/AS5350, a warning message is displayed on the console and an SNMP trap is sent out.
Recommended Action Make sure that the power supply to the AS5400/AS5350 is normal. If the problem can not be corrected, power off the system to avoid damage to the internal parts.
Error Message%ENVM-4-WARNING : [chars] measured at [chars]
Explanation One of the measured environmental test points for voltage or temperature has exceeded the warning level.
Recommended Action Closely monitor the condition and correct it if possible.
If the message is a temperature warning, perform the following checks:
1.
2.
3.
If it is a voltage problem on multiple cards, check your input AC/DC voltage source. If it is a voltage problem on a single card, ensure that a backup or spare card is available for replacement in case the voltage continues to deteriorate on that card.
If you think the message is in error, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
ENVMON Messages
The following are environmental monitor messages.
Error Message%ENVMON-5-48V_STATUS : -48V supply [chars]
Explanation The operational status of the -48V power supply has changed.
Recommended Action No action is required.
Error Message%ENVMON-3-FAN_FAILED : Fan [dec] not rotating
Explanation The fan is not rotating properly.
Recommended Action Ensure that the fan power cable is properly attached to the fan power connector on the main board. If the problem persists, it indicates a chassis that requires replacement. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative to obtain a replacement chassis.
Error Message%ENVMON-3-FAN_OK : Fan [dec] rotating again
Explanation The fan had previously reported a rotation error, but it is now operating correctly.
Recommended Action No action is required.
Error Message%ENVMON-1-NO_PROCESS : Failed to create environmental monitor process
Explanation An environmental monitor process could not be created. It is possible that sufficient memory in the router is unavailable.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ENVMON-3-OVERTEMP_OK : System temperature normal
Explanation The system previously detected an over-temperature condition that has now cleared. The over-temperature condition was most likely due to high ambient temperature where the router is located.
Recommended Action The system is now operating at a normal temperature. No action is required.
Error Message%ENVMON-5-RPS : Redundant power supply [chars]
Explanation A redundant power supply was either attached or removed.
Recommended Action No action is required.
Error Message%ENVMON-5-RPS_STATUS : RPS [chars]
Explanation The operational status of a redundant power supply has changed.
Recommended Action No action is required.
Error Message%ENVMON-4-RTC : The Real Time Clock may have battery problem or it has not been set to the current time
Explanation The real-time clock may have a battery problem or has not been set to the current time.
Recommended Action Set the real-time clock to the current time after the system has been powered on. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
EOU Messages
The following are Extensible Authentication Protocol (EAP) over User Datagram Protocol (UDP) messages.
Error Message%EOU-6-AUTHSTATUS : [chars]|[IP_address]
Explanation Authentication status has succeeded or failed for the specified host.
Recommended Action This is an informational message regarding the authentication status that was returned by AAA. No action is required.
Error Message%EOU-6-AUTHTYPE : IP=[IP_address]| AuthType=[chars]
Explanation This message describes the authentication type for the specified host.
Recommended Action This is an informational message only. No action is required.
Error Message%EOU-4-BAD_PKT : IP=[IP_address]| Bad Packet=[chars]
Explanation The router has received an invalid or malformed EAP packet from the specified host.
Recommended Action Check the specified host for correct EAP operation.
Error Message%EOU-6-CTA : IP=[IP_address]| CiscoTrustAgent=[chars]
Explanation This message reports whether Cisco Trust Agent has been detected on the specified host.
Recommended Action Install Cisco Trust Agent on the host if it was not detected.
Error Message%EOU-6-IDENTITY_MATCH : IP=[IP_address]| PROFILE=EAPoUDP| POLICYNAME=[chars]
Explanation The router has found the specified host under the EAPoUDP identity profile. There will no EAPoUDP association with this host, and the local policy, if configured, will be enforced.
Recommended Action If you do not want the specified host to be exempted from authentication, remove its entry from EAPoUDP identity profile.
Error Message%EOU-4-MSG_ERR : Unknown message event reveived
Explanation The EOU authentication process has received an unknown message event.
Recommended Action If this message recurs, reload the device.
Error Message%EOU-6-POLICY : IP=[IP_address]| [chars]=[chars]
Explanation The router has received policy attributes from AAA that will be enforced for the specified host.
Recommended Action This is an informational message. No action is required.
Error Message%EOU-6-POSTURE : IP=[IP_address]| HOST=[chars]| Interface=[chars]
Explanation This message reports the posture validation status for the specified host.
Recommended Action No action is required.
Error Message%EOU-2-PROCESS_ERR : Router could not create a EAPoUDP process
Explanation The router could not create a critical EAPoUDP process.
Recommended Action Reload the device.
Error Message%EOU-4-PROCESS_STOP : PROCESS=[chars]| ACTION=[chars].
Explanation The specified process has stopped.
Recommended Action Reload the device.
Error Message%EOU-5-RESPONSE_FAILS : Received an EAP failure response from AAA for host=[IP_address]
Explanation The router has received an EAP failure response from AAA indicating that host credentials could not be validated. The failure is probably due to unsuccessful validation of host credentials by AAA.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%EOU-6-SESSION : IP=[IP_address]| HOST=[chars]| Interface=[chars]
Explanation An entry has been created or deleted for the host on the specified interface.
Recommended Action This is an informational message only. No action is required.
Error Message%EOU-4-SOCKET : EAPoUDP socket binding fails for PORT=[hex]. Check if the interface
has valid IP address.Explanation The EAPoUDP process could not bind its port to a valid interface address. This condition is probably caused by a missing IP address on the interface.
Recommended Action Configure a valid IP address to the interface.
Error Message%EOU-6-SQ : IP=[IP_address]| STATUSQUERY|[chars]
Explanation The status query for the specified host either failed or was invalid.
Recommended Action No action is required.
Error Message%EOU-4-UNKN_EVENT_ERR : UNKNOWN Event for HOST=[IP_address]| Event=[dec].
Explanation An unknown message was received for the EAPoUDP process.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%EOU-4-UNKN_PROCESS_ERR : An unknown operational error occurred.
Explanation The EOU process cannot operate because of an internal system error.
Recommended Action Reload the device.
Error Message%EOU-4-UNKN_TIMER_ERR : An unknown Timer operational error occurred
Explanation The EOU process cannot operate because of an internal system error.
Recommended Action Reload the device.
Error Message%EOU-4-VALIDATION : Unable to initiate validation for HOST=[IP_address]| INTERFACE=[chars].
Explanation The EAPoUDP function could not start the posture validation procedure for the specified host. This condition is probably caused by a failure to bind the EAPoUDP port.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%EOU-4-VERSION_MISMATCH : HOST=[IP_address]| Version=[dec]
Explanation A mismatch in the EAPoUDP version was detected on the specified host. Incompatible EAPoUDP versions have been detected between peers.
Recommended Action Check the EAPoUDP versions on the peers.
EPAD Messages
The following are encryption port adapter driver (EPAD) 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, contact 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 help identify 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, contact 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 If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
EPLD Messages
The following are EPLD messages.
Error Message%EPLD-4-COMPLETE :
############# FEATURE CARDS FPGA DOWNLOAD COMPLETED #########
# In order for feature cards to function, power-cycle CMM #
# immediately! Do not change/save configuration #
# until after power-cycle or configurations for feature #
# cards will be lost... #
#############################################################Explanation Informational.
Recommended Action Power-cycle the CMM immediately. Reload the CMM with the same image or it will not function properly.
Error Message%EPLD-4-COMPLETE_ZP :
############# FEATURE CARDS FPGA DOWNLOAD COMPLETED #########
# In order for feature cards to function, power-cycle CMM #
# immediately and reload with ZP image! #
# Do not change/save configuration until after power-cycle #
# or configurations for feature cards will be lost... #
#############################################################Explanation Informational.
Recommended Action Power-cycle the CMM immediately. Reload the CMM with a ZP image, or the CMM will not function properly.
Error Message%EPLD-3-DOWNGRADE : [chars]
Explanation Informational.
Recommended Action No action is required.
Error Message%EPLD-3-ERROR : [chars]
Explanation Informational.
Recommended Action No action is required.
Error Message%EPLD-6-INFO : [chars]
Explanation Informational.
Recommended Action No action is required.
Error Message%EPLD-4-START_WARNING :
############### START FPGA DOWNLOAD PROCESS #################
# All feature cards will not be enabled during FPGA #
# download. Please ignore configuration 'invalid' messages #
# at boot up time. Do not change/save configuration #
# until after FPGA download is completed and power-cycle #
# or configurations for feature cards will be lost... #
#############################################################Explanation Informational.
Recommended Action Do not change or save the configuration or the feature card configurations will be lost. Wait for the download to complete and then power-cycle the CMM when prompted.
Error Message%EPLD-3-UPGRADE : [chars]
Explanation Informational.
Recommended Action No action is required.
Error Message%EPLD-4-WARNING : [chars]
Explanation Informational.
Recommended Action No action is required.
ESW_STORM_CONTROL Messages
The following are storm control messages.
Error Message%ESW_STORM_CONTROL-2-SHUTDOWN : Storm control shut down [chars]
Explanation Excessive traffic has been detected on a port that has been configured to be shut down if a storm event is detected.
Recommended Action Once the source of the packet storm has been fixed, reenable the port by entering the port command in global configuration mode.
ESW_WIC_FLTMG Messages
The following are Ethernet Switch WIC fault management messages.
Error Message%ESW_WIC_FLTMG-4-ESW_WIC_POWER_ERR : esw wic power : [chars]
Explanation An error involving the power of the Ethernet switch WAN interface card has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ESW_WIC_FLTMG-7-INTERNAL_ERR : Internal error: [chars]
Explanation An internal error has occurred. Additional details are available in the error message text.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ESW_WIC_FLTMG-5-NOTICE : Notice: [chars]
Explanation This message provides information regarding the Ethernet switch.
Recommended Action This is an informational message only. No action is required.
Error Message%ESW_WIC_FLTMG-4-VLANMACADDR_ALLOC_ERR : Ethernet Switch VLAN MAC Addr allocation error : [chars]
Explanation All available MAC addresses have been used, and no MAC addresses are available to allocate to the VLAN specified in the message. STP will not run for the specified VLAN as it does not have a MAC address for its bridge ID. The maximum number of VLANs have most likely been exceeded.
Recommended Action Ensure that the number of configured VLANs is less than the maximum number allowable for the system. If you determine that the number of configured VLANs are within the acceptable limit, copy the message exactly as it appears on the console or in the system log. Enter the show running-config and show spanning-tree brief commands to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show running-config and show spanning-tree brief commands and your pertinent troubleshooting logs.
Error Message%ESW_WIC_FLTMG-5-WARNING : Warning: [chars]
Explanation This message contains a warning-level Ethernet switch message. In general this message will alert the user to a problem concerning an invalid configuration. Additional details on the nature of the message are available in the error message text.
Recommended Action Correct the condition specified in the error message text. If you cannot correct the condition, copy the message exactly as it appears on the console or in the system log. open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
ESWILP_CFG Messages
The following are Ethernet switch module configuration messages.
Error Message%ESWILP_CFG-3-SWITCH_MODULE_COUNT : The number of switching modules in the system exceeds the supported configuration. The system supports a maximum of [dec] switching modules.
Explanation The number of switching modules has exceeded the maximum number that can be supported by the system.
Recommended Action Remove the extra switching modules and reload the router.
ESWILP_FLTMG Messages
The following are ESWILP fault management-related messages.
Error Message%ESWILP_FLTMG-4-ESWILP_POWER_ERR : eswilp power : [chars]
Explanation This is an ESWILP power-related message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ESWILP_FLTMG-4-ESWILP_STORMCTRL_ERR : eswilp stormctrl : [chars]
Explanation A condition related to ESWILP storm control has occurred. The message text provides more information on the nature of the condition.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ESWILP_FLTMG-7-INTERNAL_ERR : Internal error: [chars]
Explanation An internal error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ESWILP_FLTMG-5-NOTICE : Notice: [chars]
Explanation This is a notification message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ESWILP_FLTMG-5-STACKING_LINK : interface [chars], changed state to [chars]
Explanation An IDB state change has occurred because a stacking configuration has taken place.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ESWILP_FLTMG-4-VLANMACADDR_ALLOC_ERR : eswilp VLAN MAC Addr allocation error : [chars]
Explanation No more MAC addresses can be allocated for a given VLAN, so the STP that is running for the given VLAN can start using a MAC address for its bridge ID. There is a limited number of MAC addresses for each router:
–
–
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ESWILP_FLTMG-5-WARNING : Warning: [chars]
Explanation This is a warning message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
ESWITCH Messages
The following are Ethernet switch port adapter messages.
Error Message%ESWITCH-1-DEC21140 : ESWITCH([dec]) Failed to initialize DEC21140, shutting down bay
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, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ESWITCH-1-EALE : ESWITCH([dec]) Failed to initialize EALE
Explanation A hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ESWITCH-1-MULTICASTADD : ESWITCH([dec]), Cannot add multicast [enet]
Explanation A hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ESWITCH-5-NOBRIDGEGROUP : ESWITCH([dec]), Bridge-group must be configured
Explanation 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 supported
Explanation A configuration error has occurred.
Recommended Action Configure only 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, contact 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 bay
Explanation A hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ESWITCH-1-TSWITCH : ESWITCH([dec]) Failed to initialize TSWITCH
Explanation A hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ESWITCH-1-TSWITCHEALE : ESWITCH([dec]) Failed to initialize TSWITCH/EALE, shutting down bay
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, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ESWITCH-1-UNICASTADD : ESWITCH([dec]), Cannot add unicast [enet]
Explanation A hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ESWITCH-1-UNICASTDEL : ESWITCH([dec]), Cannot remove unicast [enet]
Explanation A hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
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, contact your Cisco 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 uplink
Explanation A hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
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, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ESWITCH-1-UNICASTLOCK : ESWITCH([dec]), Cannot lock unicast [enet]
Explanation A hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
ESWMOD Messages
The following are Ethernet switch module messages.
Error Message%ESWMOD-3-INITFAILURE : Initialization failure - [chars]
Explanation The Ethernet switch driver detected an error while it was being initialized.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ESWMOD-3-NOT_RESPONDING : Ethernet Switch Module is not responding\n
Explanation The switch module could not be configured.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ESWMOD-4-QUEUE_FULL : Ethernet Switch Module transmit queue is full\n
Explanation The transmit queue for the switch module is full and packets are being dropped.
Recommended Action Reduce the rate of packet transmission to the switched virtual interfaces to be lower than 9 Mbps.
Error Message%ESWMOD-1-UNSUPPORTED_CONFIG : The router has an unsupported combination of WIC-4ESW cards
Explanation Only one 4ESW WAN interface card is supported per router.
Recommended Action Insert only one 4ESW WAN interface card per router.
ESWMRVL_FLTMG Messages
The following are Ethernet switch fault management messages.
Error Message%ESWMRVL_FLTMG-5-ESW_MRVL_AGETIME_CFG : The aging time has been configured to [dec] seconds.Aging time is configurable only in increments of 16 seconds
Explanation The aging time has been configured to a time that cannot be divided by 16 seconds. The aging time is configurable only in increments of 16 seconds. For example, if the time is set to 40 seconds, the aging time will be configured to 32 seconds. The switch hardware supports a minimum aging time of 16 seconds and a maximum aging time of 4080 seconds.
Recommended Action Ensure that your aging time configuration is within the acceptable limits.
Error Message%ESWMRVL_FLTMG-4-ESWMRVL_POWER_ERR : Ethernet Switch power : [chars]
Explanation This message provides information regarding Ethernet switch power.
Recommended Action Enter the show power inline command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ESWMRVL_FLTMG-5-ESW_MRVL_SPAN_CFG : Either Tx or both Tx and Rx monitoring is supported. Configure Tx monitoring also.
Explanation The Ethernet switch hardware only supports port monitoring for Tx or Tx and Rx.
Recommended Action Configure Tx monitoring for port monitoring to be enabled.
Error Message%ESWMRVL_FLTMG-4-ESWMRVL_STORMCTRL_ERR : Ethernet switch stormctrl : [chars]
Explanation This message provides information regarding storm control for an Ethernet switch. Additional details on the nature of the error are available in the error message text.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ESWMRVL_FLTMG-7-INTERNAL_ERR : Internal error: [chars]
Explanation An internal error has occurred. Additional details on the nature of the error are provided in the error message text.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ESWMRVL_FLTMG-5-NOTICE : Notice: [chars]
Explanation This message provides notice-level information involving an Ethernet switch.
Recommended Action This is an informational message only. No action is required.
Error Message%ESWMRVL_FLTMG-5-STACKING_LINK : interface [chars], changed state to [chars]
Explanation The IDB has changed its state since a stacking configuration operation occurred.
Recommended Action This is an informational message only. No action is required.
Error Message%ESWMRVL_FLTMG-4-VLANMACADDR_ALLOC_ERR : Ethernet Switch VLAN MAC Addr allocation error : [chars]
Explanation There are no more MAC addresses left to allocate to the specified VLAN. STP will not run for the specified VLAN because it does not have a MAC address for its bridge ID. The maximum number of VLANs has most likely been exceeded.
Recommended Action Ensure that the number of configured VLANs is less than the maximum number allowable for your system. If you determine that the number of configured VLANs is within the acceptable limit, enter the show running-config and show spanning-tree brief commands. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show running-config, and show spanning-tree brief commands and your pertinent troubleshooting logs.
Error Message%ESWMRVL_FLTMG-5-WARNING : Warning: [chars]
Explanation This message contains a warning-level Ethernet switch message. In general this message will alert the user to a problem with an invalid configuration. Additional details on the nature of the message are available in the error message text.
Recommended Action Correct the condition specified in the error message text. If you cannot correct the condition, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
ET2 _MODULE Messages
The following are Ernest-T2 network module messages.
Error Message%ET2_MODULE-3-BERTBUSY : Controller [chars] - BERT hardware in use, command refused.
Explanation The current task requires hardware resources that are currently occupied by other tasks. The following tasks can use the BERT hardware:
–
–
Recommended Action Check to see if any of the allowed tasks are in progress on this controller.
Error Message%ET2_MODULE-3-FDLLLOOPDOWN : Controller [chars] - FDL line loopdown code detected, deactivating line loopback.
Explanation The system detects that an FDL line loop is down on the unit. Line loopback is being deactivated.
Recommended Action Unavailable.
Error Message%ET2_MODULE-3-FDLLLOOPUP : Controller [chars] - FDL line loopup code detected, activating line loopback mode.
Explanation The system detects that an FDL line loop is up on the unit. Line loopback is being activated.
Recommended Action Unavailable.
Error Message%ET2_MODULE-3-FDLLREQFAILED : Controller [chars] - Failed to put the remote end in line loopback mode via FDL.
Explanation The T1 FDL line loopup code has been sent to the remote end, but the remote end did not activate line loopback. This condition can be caused by the controller configuration, a line problem, or both.
Recommended Action Determine whether the controllers are both up.
Error Message%ET2_MODULE-3-FDLLREQOK : Controller [chars] - Remote end is put in line loopback mode via FDL.
Explanation The unit has sent the T1 FDL line loopup code to the remote end. The remote end has successfully activated line loopback.
Recommended Action Unavailable.
Error Message%ET2_MODULE-3-FDLPLOOPDOWN : Controller [chars] - FDL payload loopdown code detected, deactivating payload loopback.
Explanation The system detects an FDL payload loopdown code on the unit. Payload loopback is being deactivated.
Recommended Action Unavailable.
Error Message%ET2_MODULE-3-FDLPLOOPUP : Controller [chars] - FDL payload loopup code detected, activating payload loopback mode.
Explanation The system detects an FDL payload loopup code on the unit. Payload loopback is being activated.
Recommended Action Unavailable.
Error Message%ET2_MODULE-3-FDLPREQFAILED : Controller [chars] - Failed to put the remote end in payload loopback mode via FDL.
Explanation The T1 FDL payload loopup code has been sent to the remote end, but the remote end did not activate payload loopback. This condition can be caused by the controller configuration, a line problem, or both.
Recommended Action Determine whether the controllers are both up.
Error Message%ET2_MODULE-3-FDLPREQOK : Controller [chars] - Remote end is put in payload loopback mode via FDL.
Explanation The unit has sent the T1 FDL payload loopup code to the remote end. The remote end has successfully activated payload loopback.
Recommended Action Unavailable.
Error Message%ET2_MODULE-3-HWIDBFAILED : Controller [dec]/[dec] does not have idb
Explanation The system did not have a hardware IDB registered for the serial interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ET2_MODULE-3-IBOCLOOPDOWN : Controller [chars] - IBOC loopdown code detected, deactivating line loopback.
Explanation The system detects an IBOC loopdown code on the unit. IBOC loopback is being deactivated.
Recommended Action Unavailable.
Error Message%ET2_MODULE-3-IBOCLOOPUP : Controller [chars] - IBOC loopup code detected, activating line loopback mode.
Explanation The system detects an IBOC loopup code on the unit. Line loopback is being activated.
Recommended Action Unavailable.
Error Message%ET2_MODULE-3-IBOCREQFAILED : Controller [chars] - Failed to put the remote end in line loopback mode via IBOC.
Explanation The T1 IBOC loopup code has been sent to the remote end, but the remote end did not activate line loopback. This condition can be caused by the controller configuration, a line problem, or both.
Recommended Action Determine whether the controllers are both up.
Error Message%ET2_MODULE-3-IBOCREQOK : Controller [chars] - Remote end is put in line loopback mode via IBOC.
Explanation The unit has sent the T1 IBOC loopup code to the remote end. The remote end has successfully activated line loopback.
Recommended Action Unavailable.
Error Message%ET2_MODULE-3-INITFAILURE : ET2 (slot [dec]), [chars] failed at [chars] - line [dec] arg [hex]
Explanation The ET2 driver has failed hardware initialization.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ET2_MODULE-3-LINEFLAP : Interface [chars] receiving excessive errored packets
Explanation The serial interface is receiving an excessive number of packets with errors. This condition is caused by a mismatch in the controller configuration.
Recommended Action Check linecode, framing, timeslots and speed settings.
Error Message%ET2_MODULE-3-T1REQCANCELLED : Controller [chars] - T1 remote loopback has been cancelled.
Explanation The unit sent the T1 loopdown code to the remote end. The remote end is assumed to have received the loopdown code and deactivated loopback mode. However, a test is not being performed to ensure that the remote end has deactivated loopback mode.
Recommended Action Unavailable.
Error Message%ET2_MODULE-3-UNEXPEVENT : ET2 (bay [dec]), received an unexpected event=[hex]
Explanation The port adapter has received an unexpected event from the firmware.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ET2_MODULE-3-V54LOOPDOWN : Unit [chars] - V.54 loopdown code detected, deactivating V.54 payload loopback.
Explanation The system detects a V.54 loopdown code on the unit. V.54 payload loopback is being deactivated.
Recommended Action Unavailable.
Error Message%ET2_MODULE-3-V54LOOPUP : Unit [chars] - V.54 loopup code detected, activating V.54 payload loopback mode.
Explanation The system detects the V.54 loopup code on the unit and has successfully activated payload loopback.
Recommended Action Unavailable.
Error Message%ET2_MODULE-3-V54REQCANCELLED : Unit [chars] - Remote V.54 loopback has been cancelled.
Explanation The unit has sent the V.54 loopdown code to the remote end. The remote end is assumed to have received the loopdown code and deactivated loopback mode. However, a test is not being performed to ensure the remote end has deactivated loopback mode.
Recommended Action Unavailable.
Error Message%ET2_MODULE-3-V54REQFAILED : Unit [chars] - Failed to put the remote end in V.54 payload loopback mode.
Explanation The V.43 loopup code has been sent to the remote end, but the remote end did not activate payload loopback. This condition can be caused by a mismatched controller configuration or a line problem.
Recommended Action Check the timeslots and speed setting for the channel-group in question on both ends. Ensure that V.54 detection is enabled on the remote end.
Error Message%ET2_MODULE-3-V54REQOK : Unit [chars] - Remote end is put in V.54 payload loopback mode.
Explanation The unit has sent the V.54 loopup code to the remote end. The remote end has successfully activated payload loopback.
Recommended Action Unavailable.
ETHERNET Messages
The following are Ethernet for the C1000 series messages.
Error Message%ETHERNET-1-NOMEMORY : Unit [dec], no memory for [chars]
Explanation Insufficient memory exists to allocate the necessary memory pools.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
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. This condition may be caused by a bad configuration of the media type or a hardware problem with the cable, the transceiver, the other end of the cable, or the interface of the router itself. Extremely high traffic load can occasionally cause the router to generate this message.
Recommended Action Verify the configuration of the media type. If the media type is correctly set, replace the cable or the transceiver. If possible, try another port in the device to which the Ethernet is connected. If other measures fail, replace the hardware
Error Message%ETHERNET-4-UNSUPINTFC : Interface Ethernet[dec] not supported by [chars] image
Explanation The specific Ethernet interface is not supported by the operating system that is currently running.
Recommended Action If the hardware configuration is supported by a newer version of the operating system, you must upgrade the software to support this interface.
EVENT Messages
The following are Event MIB messages.
Error Message%EVENT-3-INSERT_FAILURE : Failed to insert [chars]
Explanation The event process has failed to insert the newly created row in its linked list data structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%EVENT-3-NULL_ELEMENT : Null pointer in the watched queue for [chars] test
Explanation The process has been woken up with a NULL element.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%EVENT-3-NULL_STRUCT : Null pointer to the [chars] structure
Explanation The process has been woken up with an element that had a null pointer to the test structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
EVENT_TRACE Messages
The following are messages for the Event Trace subsystem.
Error Message%EVENT_TRACE-3-CLOSE_FILE : Error closing file [chars]
Explanation The Event Trace subsystem cannot close the specified file.
Recommended Action No action is required. This condition will not affect system functionality.
Error Message%EVENT_TRACE-3-CONTINUOUS : Enable trace before setting continuous display
Explanation The specified event trace must be enabled before continuous display can occur.
Recommended Action Enable the specified event trace.
Error Message%EVENT_TRACE-6-ENABLE : Trace already enabled.
Explanation The specified event trace has already been enabled.
Recommended Action This is a debug message only. No action is required.
Error Message%EVENT_TRACE-3-GROUP_ID : Duplicate registration of group-id [dec]
Explanation The software subsystem is trying to register a group ID for an event trace that has already been used by another subsystem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%EVENT_TRACE-3-NO_FILENAME : Dump file not specified.
Explanation No filename has been specified as output for the event trace.
Recommended Action You must specify the trace dump filename. To specify the trace dump filename, enter the monitor event-trace comp dump-file filename command, with filename being the output file name, in global configuration mode
Error Message%EVENT_TRACE-6-NO_FORMATTER : [chars]: no formatter provided, binary dumping.
Explanation No formatter function was provided during the initialization of the specified event trace.
Recommended Action No action is required.
Error Message%EVENT_TRACE-3-NO_MEM : Not enough memory for [dec] trace elements.
Explanation The system memory is insufficient for the number of trace elements specified.
Recommended Action Reduce the size of the event trace.
Error Message%EVENT_TRACE-3-NO_TRACE_NAME : Invalid trace name [chars]
Explanation The trace buffer name that is specified in the error message is not configured or is invalid.
Recommended Action Determine if there is an event trace buffer configured by the name that was entered, and then enter the correct trace buffer name.
Error Message%EVENT_TRACE-3-NUM_ELEM : Number of trace element = [dec] is greater than number = [dec] allowed
Explanation The number of trace entries has exceeded the allowed amount.
Recommended Action Reduce the number of trace entries.
Error Message%EVENT_TRACE-3-OPEN : [chars]: Trace failed to open
Explanation Initialization of the specified event trace has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%EVENT_TRACE-3-OPEN_FILE : Couldn't open [chars]...
Explanation The Event Trace subsystem could not open a file for the specified event trace dump.
Recommended Action If a file by the same name already exists, rename the dump file or remove the existing file from the file system.
Error Message%EVENT_TRACE-3-RESIZE : Enable trace before resizing
Explanation The specified event trace must be enabled before resizing can occur.
Recommended Action Enable the specified event trace.
Error Message%EVENT_TRACE-3-SIZE_ELEM : Size of trace element = [dec] is greater than size = [dec] allowed
Explanation The size of the specified individual trace entry is greater than the allowed size.
Recommended Action Reduce the individual trace entry size so as not to exceed the maximum size while initializing the event trace.
Error Message%EVENT_TRACE-3-SIZE_FILENAME : Trace filename size = [dec] greater than size = [dec] allowed
Explanation The length of the specified event trace filename exceeds the allowed filename length.
Recommended Action Shorten the filename.
Error Message%EVENT_TRACE-3-WRITE_FILE : Error writing to file [chars]
Explanation The event trace is not able to write to the specified file system.
Recommended Action The file system might not be available. Try changing the destination file system and dumping there. If changing the destination file system does not work and this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
EXFREE Messages
The following are external memory manager messages.
Error Message%EXFREE-4-EXMALLOCFAIL : External memory allocation of [int] bytes failed from EXMEM [dec]
Explanation The requested memory allocation is not available from the specified memory pool. The current system configuration, network environment, or a software error exhausted or fragmented the router memory.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%EXFREE-2-EXMEMFREE : Free a non allocated ptr [hex] size [dec].
Explanation The system is attempting to free memory, and not all of the memory is marked as allocated.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%EXFREE-2-EXMEMINIT : EXMEM [dec]: [chars]
Explanation The requested external memory allocator has failed to be initialized.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%EXFREE-2-EXMEMPARAM : Bad parameter ([dec]) when calling to the allocator utility
Explanation An illegal parameter was used when a call to the allocator utility was made. This condition may indicate data corruption.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
EXPRESSION Messages
The following are Expression MIB messages.
Error Message%EXPRESSION-3-BADTYPE : Found data type [hex] in expression (should be [chars] type)
Explanation While an expression was being evaluated, an operand was found with an unexpected data type. 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, contact 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 has encountered a data value that is out of range or of an unexpected value, 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, contact your Cisco technical support representative, and provide the representative with the gathered information.
EXTASSIGNER Messages
The following are Extension Assigner messages.
Error Message%EXTASSIGNER-3-ERRSYNC : Failed to sync tag [dec] to standby CME
Explanation The system failed to update the new MAC address to the standby CME.
Recommended Action Check your configuration for Extension Assigner synchronization.
Error Message%EXTASSIGNER-3-ERRSYNC2 : Failed to sync re-assign tag [dec]) for [dec] to standby CME
Explanation The system failed to reassign the phone on the standby CME.
Recommended Action Check your configuration for Extension Assigner synchronization.
Error Message%EXTASSIGNER-3-ERRTAG : Invalid tag [dec]
Explanation Invalid tag number was entered.
Recommended Action Correct tag number needs to be entered.
Error Message%EXTASSIGNER-3-NOACTPHONE : Failed to find the calling phone
Explanation The system failed to find the calling phone. This should not happen.
Recommended Action Check your configuration.
Error Message%EXTASSIGNER-3-NOCB : Failed to find the skinnyCB
Explanation The system failed to find the registered phone. This may happen only if the phone was disconnected.
Recommended Action Check your configuration.
FABRIC Messages
The following are Fabric Interface ASIC (FIA) messages.
Error Message%FABRIC-3-CRC : Switch card [int]
Explanation An excessive number of CRC16 errors have been detected from one of the fabric switch cards. A hardware problem, either on the fabric card that is displayed in the error message or in the line card or RP that is reporting the error, may have occurred.
Recommended Action Enter the show controllers fia command on the RP and the execute-on all show controllers fia commands to determine if the problem is being seen by all the cards, or only one. If only one card is involved, replace that line card or RP. If all the cards are involved, replace the switch card.
Error Message%FABRIC-3-FIFOERR : [chars] FIFO Error was detected.
[chars], Data = [hex].Explanation A FIFO error has been detected by the FIA hardware.
Recommended Action The device will be reset. If this message persists, indicating a continued condition, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FABRIC-3-HALT : [chars]
Explanation The fabric hardware has not been able to correct itself.
Recommended Action Try reseating the boards. If this message persists, indicating a continued condition, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FABRIC-3-INIT : Bad Configuration master_sca = [hex] csc_installed = [hex].
Explanation The configuration of clock scheduler cards and switch cards is invalid.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FABRIC-3-LOS : LOS for slot [int] was [chars].
Explanation A loss of synchronization between the line card and the switch card was detected and cleared. The data shows the fabric card or cards on which the errors were detected.
Recommended Action Try reseating the boards. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FABRIC-3-PARITYERR : [chars] parity error was detected.
[chars] Data = [hex].Explanation A parity error has been detected by the FIA hardware.
Recommended Action The device will be reset. If the problem persists, the card will be automatically reset. If this message persists, indicating a continued condition, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FABRIC-3-REQUESTERR : Request error was detected. Type = [dec]
Explanation A request error was detected by the FIA hardware.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FABRIC-3-UNEXPECTED : Unexpected interrupt was detected from the [chars] FIA.
Explanation An unexpected interrupt was detected by the FIA hardware.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
FALLBACK Messages
The following are Voice over IP (VoIP) fallback messages.
Error Message%FALLBACK-5-AVBO_PROBE : A probe to [IP_address] is [chars] - codec [chars], icpif [dec], loss [dec], delay [dec]
Explanation There has been an AVBO probe status change.
Recommended Action Use the grace_period option to avoid a transit error.
Error Message%FALLBACK-3-CACHE_FULL : Function name [chars]: Cache is full
Explanation The fallback cache has overflowed and is unable to dump entries.
Recommended Action Increase the fallback cache size.
Error Message%FALLBACK-4-CACHE_OVERFLOW : Cache has overflowed.
Explanation The fallback cache has overflowed and dumped one-quarter of its entries.
Recommended Action Increase the fallback cache size.
Error Message%FALLBACK-3-INTERNAL_ERROR : [chars]: Internal error.
Explanation An internal error has occurred.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%FALLBACK-3-MALLOC_FAIL : [chars]: Memory allocation failed.
Explanation Allocation of memory has failed. The system memory pool might be exhausted.
Recommended Action No action is required.
Error Message%FALLBACK-3-NO_RTP_PORT : Function name [chars]: No available RTP ports.
Explanation No available voice RTP ports were found.
Recommended Action No action is required.
Error Message%FALLBACK-3-NO_STATS : [chars]: No stats were returned.\n
Explanation No statistical information was returned by the probe.
Recommended Action No action is required.
Error Message%FALLBACK-3-PROBE_FAILURE : A probe error to [IP_address] occured - [chars]
Explanation A probe error has occurred. Possibly, the responder on the remote router is not enabled, or no machine is on the specified IP.
Recommended Action Check the destination router.
Error Message%FALLBACK-3-RTR_CREATE_FAIL : [chars]: Creation of probe failed. Return code [dec]
Explanation An RTR probe could not be created. This condition can cause inaccurate ICPIF values and cause VoIP calls to be hairpinned when they should not be hairpinned.
Recommended Action No action is required.
Error Message%FALLBACK-3-RTR_START_FAIL : [chars]: probe could not be started. Return code [dec]
Explanation An RTR probe could not be started. This can cause inaccurate delay, loss, jitter, and ICPIF values and cause VoIP calls to be hairpinned when they should not be hairpinned.
Recommended Action No action is required.
Error Message%FALLBACK-3-RTR_STATS_FAIL : [chars]: Could not retrive statistics from the probe. Return code [dec] \n
Explanation RTR statistics could not be retrieved from the probe. This condition can cause inaccurate ICPIF values and cause VoIP calls to be hairpinned when they should not be hairpinned.
Recommended Action No action is required.
Error Message%FALLBACK-5-TEST_PROBE_ALREADY_RUNNING : A test probe is already running.
Explanation Only one test probe may run at a time.
Recommended Action Wait until the first test probe is finished.
FAN Messages
The following are fan messages.
Error Message%FAN-3-ERROR : Wrong value for Fan state
Explanation An error-level event has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FAN-3-FAN_FAILED : Fan [dec] had a rotation error reported.
Explanation The fan has reported a rotation error.
Recommended Action Replace the fan if it is not rotating.
Error MessageError Message%FAN-3-FAN_OK : Fan [dec] had earlier reported a rotation error. It is ok now
Explanation A fan that had earlier reported a rotation error is now working properly.
Recommended Action This is an informational message. No action is required.
FARM_DRPRM Messages
The following are Farm DSPRM messages.
Error Message%FARM_DSPRM-6-CALLDROPINFO : dspfarm active calls on this card dsp [dec] channel [dec] will be dropped.
Explanation The card specified in the message has been removed. DSPFARM active calls on this card will be dropped.
Recommended Action No action is required.
Error Message%FARM_DSPRM-6-CARDINSERTINFO : dspfarm card slot [dec] is inserted.
Explanation A DSPFARM card has been inserted into the slot.
Recommended Action No action is required.
Error Message%FARM_DSPRM-6-CARDREMOVEINFO : dspfarm card slot [dec] is removed.
Explanation A DSPFARM card type has been removed from the slot.
Recommended Action No action is required.
Error Message%FARM_DSPRM-4-NOC5510WARN : dsp service dspfarm can not be configured for this card type.
Explanation A C549 NM-HDV card has been configured for DSPFARM service. Only one DSPFARM card type is allowed.
Recommended Action If another card type (for example, a C5510 card type) is required for DSPFARM service, remove the C549 NM-HDV DSPFARM service and reconfigure DSPFARM service for the other card type.
FASTBLK Messages
The following are Fast Block messages.
Error Message%FASTBLK-4-CREATE_ERR : Fastblk pool creation error: [chars]
Explanation An unexpected error occurred while a Fast Block memory pool creation operation was being performed.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FASTBLK-4-DEALLOC_ERR : Fastblk deallocation error: [chars]
Explanation An unexpected error occurred while a Fast Block memory deallocation operation was being performed.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FASTBLK-4-GROW_ERR : Fastblk pool growth error: [chars]
Explanation An unexpected error occurred while a Fast Block memory pool growth operation was being performed.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FASTBLK-4-QUEUE_ERR : Fastblk queue error: [chars]
Explanation An unexpected error occurred while a Fast Block memory queue operation was being performed.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FASTBLK-4-SHRINK_ERR : Fastblk pool shrink error: [chars]
Explanation An unexpected error occurred while a Fast Block memory pool shrink operation was being performed.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FASTBLK-4-WARNING : Unexpected condition: [chars]
Explanation An unexpected condition was detected while a Fast Block memory operation was being performed.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
FB Messages
The following are Cisco AS5800 feature board messages.
Error Message%FB-3-AGENTSTATUS : Invalid change from [chars] ([dec]) to [chars] ([dec]) for slot [dec]
Explanation The software has detected an invalid state change for the 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, contact 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, contact 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, contact 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 in a restricted slot. This is not permitted.
Recommended Action Reinsert the feature board in the appropriate slot.
Error Message%FB-6-OIR : Card in slot [dec] [chars]
Explanation A feature card was inserted or removed from the specified slot.
Recommended Action No action is required.
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, contact your Cisco technical support representative, and provide the representative with the gathered information.
FB_COREDUMP Messages
The following are feature board core dump messages.
Error Message%FB_COREDUMP-3-NOMEMORY : No Memory or buffer for [chars] to be send to [dec]
Explanation There was insufficient memory for the router shelf to send any command or acknowledgment to the feature boards.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
FBINFO Messages
The following are Cisco AS5800 feature board crash information subsystem messages.
Error Message%FBINFO-3-CRASH : Feature board in slot [int] crashed
Explanation The feature board in the slot indicated has crashed and sent a "CRASH_START" message to the DSI. The DSI is now waiting for the rest of the crash information (stack trace, context, version, etc.) from the line card to be sent via the MBus. The crash information should be sent a few milliseconds after receiving the "CRASH_START" message. 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 indicating that the DSI did not receive the crash information messages and will notify the rest of the DSI software that the feature board has crashed.
Recommended Action Report this defect with as much information about the feature board in question, 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 RS.
Error Message%FBINFO-3-INVDEV : Invalid feature board number in MBUS callback (LC=[int])
Explanation The feature board crash information subsystem on the DSI was called from the 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 indicates a software defect in the system.
Recommended Action Report this defect with as much information 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 due to bad 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 is due to a software defect in that subsystem.
Recommended Action Report this defect with as much information about the MBus subsystem and the feature board crash information subsystem possible.
Error Message%FBINFO-3-NOPROCESS : Failed creating feature board slot [int] complete process
Explanation The create_process call failed while creating the crash complete process for the crash information subsystem. This error is probably due to a software defect or hardware failure and should happen only during initialization.
Recommended Action Reboot the system. If the error recurs on subsequent reloads of the system, a bug should be filed and the system should be reloaded with a different image.
Error Message%FBINFO-4-NOSPACE : Insufficient space to write crashinfo file [chars]
Explanation The attempt to write the crash information following a feature board crash failed because of insufficient free space in the Flash device. The crash information is available via a show context slot N command but will be lost after the next reload of the system.
Recommended Action Report this error to your Cisco technical support representative with as much information about the feature board in question, including the output of the show context summary, show context slot N, and show tech-support N commands in addition to the show tech-support command from the RS.
Error Message%FBINFO-4-OPENFAIL : Open of crashinfo file [chars] failed
Explanation The attempt to open a file in Flash memory to store the crash information following a feature board crash has failed. The crash information is available via a show context slot N command but will be lost after the next reload of the system.
Recommended Action Report this error to your Cisco technical support representative with as much information about the feature board in question, including the output of the show context summary, show context slot N, and show tech-support N commands in addition to the show tech-support command from the RS.
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 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 the same as a crash dump; this process contains a small amount of information that usually includes context, stack trace, etc. The information will be less than 8k bytes long. If an "END OF CRASH" information message is not received before the timer expires, the crash information record, which contains partial information is closed, this message is displayed, and the rest of the system is notified that the feature board has crashed, at which point it is probably reloaded. If the feature board sends more crash information after the timer goes off and before the system resets, the feature board additional "UNXMSG" error message might be displayed.
Recommended Action No action is required specifically because this message was displayed. However, since the feature board was crashing, there might be other defects to report. If this message is seen and the feature board has not crashed, report this defect with the output of the usual commands including the show tech-support command on the RS and on the feature board that did not crash but was referenced in this error message.
Error Message%FBINFO-4-TRUNC : Crash record ([int]=[chars]) truncated (expected=[int], actual=[int])
Explanation A feature board crashed and was sending crash information to the RS. The RS received a "CRASH RECORD START" message that indicated how many bytes of data would be received. Before the indicated number of bytes had been received, the RS received another "CRASH RECORD START" message indicating the start of another record. The first record was marked as truncated, and the next record was received, but the truncation of the first message is noted in the later message. This error might be a symptom of another underlying problem in addition to the line card crash that resulted in the sending of the first "CRASH RECORD START" message.
Recommended Action Report this defect with as much information about the MBus subsystem and the line card crash information subsystem as 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 an unexpected message for its state. The state and message type are given in the error message. This message does not have any adverse effect on the DSI since the DSI ignores the message and recovers from this occurrence. This message could occur if a feature board is failing. The source of the crash on the line card is more significant. If this message occurs and a line card has not crashed, it is caused by a stray or errant 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 crashing when the message occurred. If no feature board was crashing, report this defect with as much information about the MBus subsystem and the feature board crash information subsystem as possible. If this message persists, rebooting the router might remove this message.
FCIP Messages
The following are FCIP driver messages.
Error Message%FCIP-1-BADREFC : Bad refcount in FCIP particle [hex], refcount: [dec]\n
Explanation An error involving FCIP particle management has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-CORDDONE : Cordova device discovered and started\n
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%FCIP-1-COUNTERR : [chars] count is zero upon getting [chars] interrupt\n
Explanation The FCIP driver could not process an interrupt because of a counting error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-1-DESCERR : [chars] descriptor error. Descriptor count = [dec]\n
Explanation The FCIP driver could not send an FC frame because of errors in the descriptor.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-1-DLENERR : Length field error in descriptor for Desc : [hex], Stat : [hex]\n
Explanation The FCIP driver could not consume the packet because of errors in the descriptor.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-DSNULL : FCIP hwidb device speicifc (ds) structure is NULL!\n
Explanation Hardware IDB creation may not have occurred yet, or might have failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-FCDR2FDQFAIL : **** [chars]: Failed to create driver to FD Q ****\n
Explanation A driver could not be created to the FD queue.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-FCFDPROCFAIL : **** [chars]: Failed to create FD process ****\n
Explanation An FD process could not be created.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-1-FCLENERR : Interface [chars]: FC frame length exceeded for queue_id = [dec]\n
Explanation The FCIP driver could not send a FC frame because of an error involving the length of a frame.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-FCNOCHUNKMEM : **** [chars] [chars]: Chunk Malloc filed ****\n
Explanation Memory allocation for a chunk has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-FCNOPCLES : **** [chars] [chars]: Out of fcip particles ****\n
Explanation The system has run out of FCIP particles.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-1-FCQERROR : Enqueue to FC watched queue failed. Packet type ([dec])\n
Explanation The FCIP driver could not enqueue an FC event to an FC process.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-FCRVSNMISMATCH : **** [chars]: ELP: Illegal Revision [dec] ****\n
Explanation The ELP revision is earlier than Revision 2.
Recommended Action Upgrade the ELP to a Revision of 2 or later. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-FCSBADDFAIL : **** [chars]: Could not add FCAP hwsb ****\n
Explanation The FCAP module could not add the FCAP hardware subblock to the hardware subblock list.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-FCTOVMISMATCH : **** [chars]: ELP: ratov([dec]) NS MAX RATOV ([dec]) & edtov([dec]) NS MAX EDTOV([dec]) ****\n
Explanation One or more ELP TOV values has exceeded the maximum supported by the GG port adapter.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-FDNULLCB : **** [chars]: CB ptr is NULL ****\n
Explanation The control block pointer is of a null value.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-FDNULLIDB : **** [chars]: IDB ptr is NULL in pkt ****\n
Explanation The IDB pointer in the packet is of a null value.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-FDNULLMSG : **** [chars]: MSG ptr is NULL ****\n
Explanation The message pointer is of a null value.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-FDNULLPCLE : **** [chars] [chars]: Pcle ptr is NULL ****\n
Explanation The particle pointer is of a null value.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-FDNULLPKT : **** [chars]: Packet ptr is NULL ****\n
Explanation The packet pointer is of a null value.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-FDNULLTIMERLEAF : **** [chars]: FD mgdtimer expired, but leaf is NULL ****\n
Explanation The FD MGD timer expired, but the leaf is of a null value.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-FDSBADDFAIL : **** [chars]: Could not add FD hwsb ****\n
Explanation The FCFD module could not add the FD hardware subblock to the hardware subblock list.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-FDSMG2FDNOMEM : **** [chars] [chars]: No Memory to send msg to FD ****\n
Explanation No memory was available to send a message to the FD.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-HWINITFAIL : Interface [chars]: FCIP driver init did not complete possibly due to device error\n
Explanation The FCIP driver cannot initialize because the hardware is not yet initialized.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-HWRESET : [chars] port adaptor reset
Explanation The FCIP hardware has failed. The FCIP heartbeat (keepalive) is missing.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-HWREVERR : Interface [chars]:Port Adapter h/w version incorrect\n
Explanation The port adapter hardware version was determined to be incorrect. This condition might be caused by the port adapter serial EEPROM programming.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-IDBDOWN : FCIP idb state is not up\n
Explanation FCIP interface initialization has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-IDBNULL : FCIP hwidb is NULL!\n
Explanation Creating of the hardware IDB may not have occurred yet or might have failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-1-INDMISMATCH : [chars] descriptor index error. Desc = [hex] Req index = [hex] Stat index = [hex]\n
Explanation The FCIP driver could not consume an FC frame because of errors with the descriptor index.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-INIBUFPOOL : Interface [chars]: FCIP buffer mempool could not be created\n
Explanation The FCIP driver cannot allocate particles for descriptor rings.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-INIINST : Interface [chars]: FCIP driver could not initialize instance data structure\n
Explanation Shadow packet allocation may not have succeeded. The FCIP driver could not initialize the data structure for an instance.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-1-INITFAIL : [chars] init timed out\n
Explanation The FCIP port adapter failed to complete its hardware initialization.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-INITIDB : Interface [chars]: FCIP driver could not setup idb fields\n
Explanation The PCI memory pool allocation may not have succeeded.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-1-MSGTYPERR : Unknown message type received fron Northstar (msg = [hex])\n
Explanation The FCIP driver could not process a message.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-1-NOBUF2REL : No buffer in [chars] prb array. Index = [hex]\n
Explanation The FCIP driver could not release any buffers because of errors involving the index.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-1-NOBUFREL : Buffer still active in [chars] ([chars]) prb array. Index = [hex], mp at index = [hex]\n
Explanation The FCIP driver could not send any frames because of buffer release errors.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-1-NOCHUNKMEM : Chunk Memory insufficient to create FC event ([dec]) message\n
Explanation The FCIP driver cannot send FC events to the FCAP because of memory limitations.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-NOCORDOVA : Pay Bay ([dec]): Cordova device could not be found by system controller\n
Explanation The FCIP driver cannot be initialized because PCI device discovery has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-1-NODESC : Interface [chars]: Free [chars] descriptor not available\n
Explanation The FCIP driver could not send an FC frame because of descriptor errors.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-NOHBEAT : [chars] No heartbeat from GoldenGate
Explanation The FCIP hardware has failed. The FCIP heartbeat (keepalive) is missing.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-1-NOMEM : Interface [chars]: Memory insufficient to create [chars] descriptors\n
Explanation The FCIP driver cannot be initialized because of memory limitations.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-NOMEMFCSB : **** [chars]: Could not malloc FCAP hwsb ****\n
Explanation The FCAP module could not allocate memory for the FCAP hardware subblock.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-NOMEMFDSB : **** [chars]: Could not malloc FD hwsb ****\n
Explanation The FCFD module could not allocate memory for the FD hardware subblock.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-NOMEMORY : Memory insufficient to create FCIP driver process\n
Explanation The FCIP driver cannot initialize because of memory limitations.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-NOPARTPOO : FCIP particle pool could not be created\n
Explanation The FCIP driver cannot create particles for descriptor rings.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-NOPAVALID : [chars] port adaptor PA valid de-asserted
Explanation The FCIP hardware has failed. A wormhole is probably hung.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-1-NSBPMERR : [chars] error (at addr = [hex]) in Northstar engine..!\n
Explanation The FCIP driver could not send an FC frame because of buffer pointer errors.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-1-NSENGTOUT : Northstar timedout for [chars]. Wait count ([dec]) exceeded [chars]\n
Explanation The FCIP driver could not send an FC frame because of descriptor errors.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-1-NSERRSTAT : [chars] Status full set without Status Available (threshold hit = [dec] times)\n
Explanation The FCIP driver could not process the interrupt because of an NS error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-NSINITERR : Could not initialize Northstar registers\n
Explanation An error involving an incorrect FPGA (wormhole) version has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-1-NSPARERR : [chars] error (at addr = [hex]) in Northstar engine..!\n
Explanation The FCIP driver could not send an FC frame because of descriptor errors.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-1-NSTABERR : [chars] error at addr (high:low) [hex]:[hex]\n
Explanation The FCIP driver could not send an FC frame because of descriptor errors.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-NULLINTR : NULL interrupt (mask = [hex]) (Hardware INT status register=[hex]) (Hardware INT mask register==[hex]\n
Explanation A spurious interrupt was received from Northstar. The error may be one involving masking.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-NULPARTCLE : No free particle from mempool..!(pool id = [hex])\n
Explanation The FCIP driver cannot allocate particles for descriptor rings.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-PANICFRZ : [chars] PA valid de-asserted. GoldenGate panic/freeze..!\n
Explanation An FCIP panic condition has occurred. The reason for this error cannot be determined.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-PARTYERR : [chars] PA valid de-asserted. Cause : [chars] parity error\n
Explanation The wormhole has detected a parity error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-PATYPERR : PA type ([dec]) is not supported
Explanation The port adapter is of an unknown type.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-PAVALID : [chars] port adaptor PA valid asserted
Explanation The FCIP hardware is up. Firmware and the FPGA are operational.
Recommended Action No action is required.
Error Message%FCIP-3-POSTERR : [chars] POST failed..!\n
Explanation The FCIP power-on-self-test has failed because of a hardware error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-PUTNOSPACE : FCIP Tx ring (ch=[dec]) does not have enough room\m
Explanation A "put_segment" operation caused a "NO_SPACE" error to the "tcp_input" function.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-RAPAVAL : [chars] port adaptor PA valid re-asserted
Explanation The FCIP hardware is back up from de-assertion. The firmware and FPGA are operational.
Recommended Action No action is required.
Error Message%FCIP-3-RXEOPERR : EOP not set for port = [dec], conn = [chars], pps = [dec], rmd = [hex]\n
Explanation The FCIP driver detected that an end-of-particle flag was not set by the wormhole.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-RXNOPARTERR : Replacement particle error for port = [dec], conn = [chars]\n
Explanation The FCIP driver cannot allocate replacement particles for Rx descriptor rings.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-RXOWNERR : Descriptor ownership error for port = [dec], conn = [chars], rmd = [hex], pps = [dec], segsize = [hex], bufsize = [hex]\n
Explanation A hardware error (wormhole FPGA) error has occurred. The FCIP driver detected that the Rx ring ownership is not set to CuH by the wormhole.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-RXSEGLENERR : Segment length error for port = [dec], conn = [chars], rmd = [hex]\n
Explanation A hardware error (wormhole FPGA) occurred. The FCIP driver detected that the Rx ring has an incorrect valid byte length specified by the wormhole.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-SM_CHUNK_MALLOC_FAIL_ERR : SM:chunk malloc failed [chars]\n
Explanation SM chunk memory allocation has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-SM_ENQUEUE_FAIL_ERR : SM:process enqueue failed\n
Explanation An error involving SM has occurred. A process could not be enqueued.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-1-SPROMREAD : Unable to read serial eeprom for PA in slot [dec]\n
Explanation The FCIP driver could not read the PA serial EEPROM to build a WWN.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-1-SPURMSG : Spurious Message interrupt : No message is pending to be read\n
Explanation The FCIP driver could not process a message.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-1-TCPNOCHUNK : Unable to create chunk pool [chars]\n
Explanation The TCP module could not create a chunk pool during initialization.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-1-TCPNOMEM : Interface [chars]: Malloc failed for [chars]\n
Explanation Memory could not be allocated for a structure.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-TXSTATERR : Tx DMA error for status descriptor ([hex]). Error = ([hex])\n
Explanation A transmission dynamic memory allocation to the Northstar component has failed. This condition might have been caused by a hardware problem.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-TYPEMISM : Pay bay ([dec]), Bus# ([dec]): PA type ([dec]) does not match
Explanation The port adapter is of an unknown type.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FCIP-3-UNKWNERR : [chars] Port adaptor (unknown) error\n
Explanation An FCIP panic condition has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
FCL Messages
The following are Forward Control Layer (FCL) messages.
Error Message%FCL-3-INSERT_FAIL : FCL unable to insert entry through FDM, error code = [dec]
Explanation An internal error occurred in the Forward Control Layer component. The requested entry could not be added into the TCAM table.This condition can be caused by an invalid application request, the entry already being present, an allocation failure, or a send failure.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FCL-3-INVALID_NETWORK_ENTRY : No interface information in network data block
Explanation Invalid parameters have been sent to the Forward Control Layer component.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FCL-3-NO_STREAM_ID : FCL unable to obtain stream id from FM for slot [dec]. Interface Name = [chars] Interface type = [hex]
Explanation An internal error occurred in the Forward Control Layer component. The logical or default stream ID for the interface in the slot specified in the error message could not be obtained from the Forwarding Manager.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FCL-3-REMOVE_FAIL : FCL unable to remove entry through FDM, error code = [dec]
Explanation An internal error occurred in the Forward Control Layer component. The requested entry could not be removed from the TCAM table. This condition can be caused by an invalid application request, a lookup failure, or a send failure.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
FDDI Messages
The following are Fiber Distributed Data Interface (FDDI) messages.
Error Message%FDDI-3-BADSLOT : Unit [dec], Slot [dec] does not exist.
Explanation The main processor has detected an invalid slot location for one of the network interface cards. This should never happen.
Recommended Action Contact your Cisco technical support representative to obtain a replacement card.
Error Message%FDDI-3-BADUNIT : Bad unit number [dec]
Explanation 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 might help identify 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, contact 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.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
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 "FDDIFAIL" message and contains debug information.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
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, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FDDI-1-NOMEMORY : Unit [dec], no memory for [chars]
Explanation 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, contact your Cisco technical support representative, and provide the representative with the gathered information.
FDM Messages
The following are Firewall Service Module (FWSM) Device Manager messages.
Error Message%FDM-3-APPL_DELETE_FAIL : FDM appl=[dec] test key=[hex] mask=[hex] entry failed to be deleted.
Explanation The FDM application information could not be deleted from the forwarding database during the test. Either the database or the deletion software might be faulty. The system could also be forwarding traffic incorrectly.
Recommended Action During the next convenient maintenance window, reload the RSC that is reporting the error. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FDM-3-APPL_ENTRY_LOST : FDM appl=[dec] test key=[hex] info=[dec] entry not found after insertion.
Explanation The FDM application information was inserted, but the same information cannot be found in the forwarding database after the test insertion. The insertion software might be faulty or the system cannot use the database to forward the traffic.
Recommended Action During the next convenient maintenance window, reload the RSC that is reporting the error. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FDM-3-APPL_INFO_MISMATCH : FDM appl=[dec] test key=[hex] info=[dec] entry found, but mismatch with test info=[dec].
Explanation The FDM application information is corrupted in the forwarding database after inserting the test information. The forwarding database memory might be faulty, or the system might be forwarding traffic incorrectly.
Recommended Action During the next convenient maintenance window, reload the RSC that is reporting the error. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FDM-3-APPL_INSERT_FAIL : FDM appl=[dec] test key=[hex] info=[dec] entry is not inserted.
Explanation The FDM application information cannot be inserted in the forwarding database for testing. The insertion software might be faulty or the database might be full or faulty. It is also possible that the system cannot use the database to forward the traffic.
Recommended Action During the next convenient maintenance window, reload the RSC that is reporting the error. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FDM-3-APPL_RW_OK : FDM appl=[dec] test key=[hex] info=[dec] test entry is written and read ok through TCAM.
Explanation The FDM application and the hardware-based forwarding engine are functioning correctly. The application and the forwarding engine are writing and reading the information as expected.
Recommended Action No action is required.
Error Message%FDM-3-BAD_MASK : [chars], [dec]
Explanation The FDM software has detected that the mask passed was invalid.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FDM-3-TCAM_ENTRY_CORRUPTED : FDM appl=[dec] test key=[hex] internal key=[hex] index=[hex] is corrupted (expected index [hex]) in TCAM after insertion.
Explanation The FDM application information became corrupted in the hardware-based forwarding engine during the test. Unexpected results might occur where the hardware-based forwarding engine is used. If this error recurs, the system might have faulty hardware.
Recommended Action During the next convenient maintenance window, reload the RSC that is reporting the error. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FDM-3-TCAM_ENTRY_DANGLED : FDM appl=[dec] test key=[hex] is dangling in TCAM after deletion.
Explanation The system found unexpected information in the hardware-based forwarding engine after the test data was removed from the FDM application. Unexpected results might be seen where the hardware-based forwarding engine is used. If this error recurs, the system might have faulty hardware.
Recommended Action During the next convenient maintenance window, reload the RSC that is reporting the error. If the error recurs, replace the RSC with a spare. If this error persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FDM-3-TCAM_ENTRY_MISSING : FDM appl=[dec] test key=[hex] internal key=[hex] missed a direct hit reading in TCAM after insertion.
Explanation Expected information in the FDM application is missing from the hardware-based forwarding engine. The system might not be able to switch the packets as fast as it should. If this error recurs, the system might have faulty hardware.
Recommended Action During the next convenient maintenance window, reload the RSC that is reporting the error. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
FDM_HA Messages
Error Message%FDM_HA-3-NO_HA_LIST : Unable to locate redundancy list - type [dec].
Explanation This message is usually generated by a coding error. All regions that are being monitored by the FDM HA client have a list that the FDM HA client uses to keep track of redundancy information about that region. This list could not be found.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FDM_HA-3-NO_PURGE_STALE_ENTRIES_PROCESS : Unable to start process to purge stale FDM entries after switchover.
Explanation The process that removes FDM entries after a given time was unable to start. These entries existed before the switchover. Because the process cannot start, the entries cannot be purged. However, as long as numerous switchovers are not carried out, this condition should not have a negative impact on operations. Depending on the number of entries, numerous switchovers could eventually exhaust the router's memory.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FDM_HA-3-UNEXPECTED_REGION : While [chars] an unexpected region type ([dec]) was encountered.
Explanation Three regions within FDM have the potential to cause a checkpoint. A list processing one of these regions was instructed to process a region it was not maintaining and cannot maintain.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FDM_HA-3-UNKNOWN_MSG : [chars] checkpointing code received unknown msg type ([dec]).
Explanation The checkpointing code received an unknown event.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
FECPM Messages
The following are Fast Ethernet (FE) Combination Port Module (CPM) device driver messages.
Error Message%FECPM-3-BSCHUNT : BSC HUNT cmd for int [dec]/[dec] failed
Explanation An internal error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FECPM-1-DISCOVER : NM slot [dec]: only [dec] PCI dev found
Explanation Some of the interface controller devices on the FECPM NM did not initialize properly.
Recommended Action Power down, reinsert the port module, and reboot. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FECPM-3-DSCC4 : DSCC4 chip init slot [dec] failed
Explanation An internal error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FECPM-4-FPGA_UPDATE : FECPM FPGA (slot [dec]) updated, all EADI sessions terminated
Explanation The Cisco IOS image contains updated FECPM FPGA firmware that must be downloaded to the FPGA regardless of EADI sessions.
Recommended Action Verify the status of EADI sessions after the router is operational.
Error Message%FECPM-1-INITFAIL : NM slot [dec]: PCI dev [dec] init failed
Explanation A PCI device on the FECPM NM failed to successfully initialize the hardware.
Recommended Action Power down, reinsert the port module, and reboot. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FECPM-3-INVALID_CLOCKRATE : Unsupported clock rate req on int [dec]/[dec] - index [dec]
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, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FECPM-3-INVALID_SCC : Config req for invalid SCC via int [dec]/[dec]
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, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FECPM-3-NOMEMORY : No memory for [chars] of unit [dec]
Explanation The router does not have enough memory to function properly.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%FECPM-3-OWNERR : Buffer owner ship error on int [dec]/[dec], pak=[hex]
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, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FECPM-2-SCCFAIL : Init of SCC[dec] for int [dec]/[dec] failed to do [chars]
Explanation The software has failed to initialize or restart an SCC of a serial interface on the FECPM.
Recommended Action Clear the serial interface. If this error message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FECPM-3-SCCRESET : SCC reset for int [dec]/[dec] at [chars] failed
Explanation An internal error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FECPM-3-SPI_OP_FAILED : NM base addr - [hex], WIC slot - [dec], SPI op failed
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, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FECPM-5-SPURINT : Spurious [chars] int on SCC [dec] in slot [dec]
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, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FECPM-3-TDMSW : TDM switch init in slot [dec] failed
Explanation An internal error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FECPM-5-TOOBIG : On int [dec]/[dec], tx pak is [dec] bytes
Explanation A packet greater than the assigned MTU of this serial interface was placed in the transmission queue.
Recommended Action The system should recover. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FECPM-5-TOOSMALL : On int [dec]/[dec], tx pak size is [dec] bytes
Explanation A small packet (a packet of a size less than 2 bytes) was placed in the transmission queue. The interface cannot transmit packets that are 2 bytes or less in size.
Recommended Action The system should recover. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FECPM-3-TXCOMPNOTIFY : On int [dec]/[dec], tx_comp_notify vector is not set
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, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FECPM-3-UFHANDLE : UnderFlow handling on int [dec]/[dec] failed.
Explanation An internal error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FECPM-5-UNDERFLOW : Transmit underflow on int [dec]/[dec]
Explanation While transmitting a frame, the local buffer of the serial controller chip received insufficient data because data could not be transferred to the chip fast enough to keep pace with its output rate. Normally, this problem is temporary, depending on transient peak loads within the system.
Recommended Action The system should recover. No action is required.
Error Message%FECPM-1-UNKNOWN_WIC : NM slot [dec], wic card has an unknown id [hex]
Explanation The software does not recognize the type of WIC card plugged into the port module.
Recommended Action Check the part number on the WIC card and verify that it is supported in the IOS software release that is operational on the router. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
FESMIC_FLTMG Messages
The following are FESMIC fault management-related messages.
Error Message%FESMIC_FLTMG-3-CMIC : Warning: [chars]
Explanation A warning-level event has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FESMIC_FLTMG-5-EEPROM : Warning: [chars]
Explanation A warning-level event has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FESMIC_FLTMG-3-ESB : Warning: [chars]
Explanation A warning-level event has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FESMIC_FLTMG-7-INTERNAL_ERR : Internal error: [chars]
Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FESMIC_FLTMG-5-NOTICE : Notice: [chars]
Explanation A notice-level event has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FESMIC_FLTMG-3-TOOMANYSVI : Error: Cannot create more than [dec] VLAN interfaces
Explanation An error event has occurred. The error message text provides more information on the nature of the error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FESMIC_FLTMG-4-VLANMACADDR_ALLOC_ERR : fesmic VLAN MAC Addr allocation error : [chars]
Explanation No more MAC addresses can be allocated for the VLAN. The MAC address was to be used for the bridge ID for a VLAN STP.
Recommended Action Limit the number of VLAN STPs to the maximum that the router can support. For the Cisco 3660 and 3640 routers, a maximum of 64 STPs are allowed. For the Cisco 2600 series and the Cisco 3620 routers, a maximum of 32 STPs are allowed. If you require further assistance, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FESMIC_FLTMG-5-WARNING : Warning: [chars]
Explanation A warning-level event has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
FIB Messages
The following are forwarding information base (FIB) messages.
Error Message%FIB-2-DFIBSWITCH : Error trying to turn on Distributed CEF without CEF on
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in non-zipped, plain text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FIB-2-FIB_OVERLENGTH_XDR : Overlength CEF XDR message - len [dec] > [dec] from [chars]
Explanation An internal software error, which prevented the sending of a CEF XDR message, has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in non-zipped, plain text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FIB-3-FIBAUTOADJLIST : Error queueing interface [chars] to the auto adjacency list.
Explanation An attempt to queue the CEF auto adjacency list to an interface has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in non-zipped, plain text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FIB-3-FIBBADXDRDATA : Invalid XDR data. [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in non-zipped, plain text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FIB-3-FIBBADXDRHWSBDECODE : HW subblock decode ([chars] / [dec]) - wrong length read.
Explanation The specified hardware subblock is not being processed correctly on the line card. The error has been corrected, but it should be reported in case there are related problems that have to be addressed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FIB-3-FIBBADXDRHWSBID : Invalid hardware sub-block id [dec] in XDR data.
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in non-zipped, plain text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FIB-3-FIBBADXDRIPC : Invalid IPC/XDR. IPC len/XDRs len [dec]/[dec]. IPC at [hex]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in non-zipped, plain text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FIB-3-FIBBADXDRSBTYPE : Invalid sub-block type [dec] in XDR data.
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in non-zipped, plain text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FIB-3-FIBBADXDRSLOT : Invalid XDR slot. Type/len/slot [dec]/[dec]/[dec]. XDR at [hex]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in non-zipped, plain text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FIB-3-FIBBADXDRSWSBDECODE : SW subblock decode ([chars] / [dec]) - wrong length read.
Explanation The specified software subblock is not being processed correctly on the line card. The error has been corrected, but it should be reported in case there are related problems that have to be addressed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FIB-3-FIBBADXDRSWSBID : Invalid software sub-block id [dec] in XDR data.
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in non-zipped, plain text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FIB-3-FIBBADXDRTYPE : Invalid XDR type. Type [dec]. XDR at [hex]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in non-zipped, plain text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FIB-4-FIBCBLK : Missing cef table for tableid [dec] during [chars] event
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in non-zipped, plain text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FIB-3-FIBDISABLE : Fatal error, slot [dec]: [chars]
Explanation An internal software error has occurred because of an IPC problem between the LC and the RP. CEF switching is disabled on the specified slot.
Recommended Action Enter the clear cef linecard [slot no] command. Then check the status of the line card by entering the show cef linecard command. If the status shows that the line card is still disabled, disable and reenable DCEF and check the status of the line card again. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in non-zipped, plain text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FIB-2-FIBDOWN : CEF has been disabled due to a low memory condition.
It can be re-enabled by configuring "ip cef [distributed]"Explanation CEF was disabled due to a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade the RP so that it has more DRAM.
Error Message%FIB-4-FIBEVENT : Invalid event. Type [dec], event [dec]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in non-zipped, plain text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FIB-3-FIBHWIDB_NONAME : Missing name for fibhwidb (ifindex [dec])
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. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FIB-2-FIBHWTABLEILLEGAL : An internal software error occurred. Argument is missing.
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in non-zipped, plain text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FIB-4-FIBIDB : Missing cef idb for [chars] during [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in non-zipped, plain text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FIB-4-FIBIDBINDEX : Missing CEF idb for interface index [dec] during [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in non-zipped, plain text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FIB-4-FIBIDBINIT : Detected interface index mis-match ([dec], [dec])
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in non-zipped, plain text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error MessageError Message%FIB-4-FIBINVACL : Invalid ACL field: [chars] is [dec]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in non-zipped, plain text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FIB-4-FIBINVRMAP : Invalid route-map message field: Expected: [chars] ([dec]), Received [dec]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in non-zipped, plain text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FIB-3-FIBLC_OOSEQ : Slot [dec] disabled - Out of Sequence. Expected [dec], received [dec]
Explanation The RP has received an out-of-sequence IPC from the line card. CEF switching is disabled on the specified slot.
Recommended Action Enter the clear cef linecard [slot no] command. Then check the status of the line card by entering the show cef linecard command. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in non-zipped, plain text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FIB-4-FIBLCTUNSEQ : [chars] Error Initializating/Updating Linecard Tunnel Configutation
Explanation The configuration of a tunnel on this line card may have been unsuccessful because of an internal software error.
Recommended Action Reconfigure the affected tunnel. If the problem persists and this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in non-zipped, plain text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FIB-3-FIBLOADBALINITFAIL : Error initializing [chars] load sharing algorithm ([chars]). Default load sharing algorithm restored.
Explanation Initialization of the FIB load sharing algorithm failed because of the condition stated. The default algorithm for this platform and image has been restored.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in non-zipped, plain text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FIB-4-FIBMSG : Invalid message received. Type [dec], event/sub-type [dec], length [dec]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in non-zipped, plain text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FIB-4-FIBNOIDB : Missing idb on fibidb [chars] during [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in non-zipped, plain text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FIB-3-FIBPENDINGLIST : Error queueing interface [chars] to CEF pending event list.
Explanation An error occurred while queuing an interface to the CEF pending event list.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in non-zipped, plain text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FIB-4-FIBREMOVE : Fibtype deletion execption: [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in non-zipped, plain text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FIB-3-FIBSBINIT : Error initializing [chars] subblock data structure. [chars]
Explanation Initialization of the specified CEF subblock data structure could not be accomplished.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in non-zipped, plain text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message