Table Of Contents

_PDSN_CLUSTER Messages

NRP Messages

NRP2 Messages

NSE Messages

NSE100 Messages

NTP Messages

OER_BR Messages

OER_MC Messages

OER_TT_FLOW Messages

OIR Messages

ON_DIAG Messages

OSPF Messages

OSPFv3 Messages

PA Messages

PACC Messages

PACC_IPC Messages

PARSER Messages

PCI_FE Messages

PCMCIAFS Messages

PIF Messages

_PDSN_CLUSTER Messages

The following are PDSN cluster controller or PDSN cluster member messages.

Error Message    

%_PDSN_CLUSTER-4-CONFIG_ERROR : [chars]

Explanation    A configuration error has occurred. Reconfiguration is not allowed because the router has already been configured as a peer to peer or controller or controller member cluster, or sessions already exist.

Recommended Action    If reconfiguration must be performed, clear the sessions and remove the configuration of the peer to peer or controller or controller member cluster.

Error Message     

%_PDSN_CLUSTER-4-CONFIG_ERROR_IP : [IP_address] [chars]

Explanation    A configuration error has occurred. The cluster member IP address is same as a PCF address.

Recommended Action    Reconfigure the PCF address so that it is different from the cluster member IP address by entering the no cdma pdsn secure pcf command.

Error Message    

%_PDSN_CLUSTER-2-CONTROLLER_PERIODIC_PROCESS_NOT_CREATED : reconfigure a parameter to make router try create process again

Explanation    A controller periodic process could not be created.

Recommended Action    Increase the timeout parameters of the system so that the process will be created before the timeout period expires.

Error Message     

%_PDSN_CLUSTER-2-CONTROLLER_PROCESS_NOT_CREATED : reconfigure a parameter to make router try create process again

Explanation    A controller process could not be created.

Recommended Action    Increase the timeout parameters of the system so that the process will be created before the timeout period expires.

Error Message    

%_PDSN_CLUSTER-4-CONTROLLER_WARNING : Unconfigure
controller first, then configure the member.

Explanation    The router is being configured as a PDSN cluster controller. An attempt was made to configure the router as PDSN cluster member.

Recommended Action    Do not reconfigure the role of a PDSN, if possible. If reconfiguration must be performed, remove the configuration of the PDSN cluster controller by entering the no cdma pdsn cluster controller command. Then configure this PDSN as a cluster member. Note that if this configuration operation is performed, controller data structures regarding sessions in PDSN cluster members and member loads will be lost.

Error Message     

%_PDSN_CLUSTER-3-MEMBERA10TO : A11 send to controller:[dst:[IP_address]], no reply.

Explanation    An RP member controller connectivity error has occurred.

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    

%_PDSN_CLUSTER-3-MEMBER_PROCESS_NOT_CREATED : reconfigure a parameter to make router try create process again

Explanation    A member process could not be created. The PDSN will continue to operating in standalone mode.

Recommended Action    Increase the timeout parameters of the system so that the process will be created before the timeout period expires.

Error Message    

%_PDSN_CLUSTER-4-MEMBER_WARNING1 : Unconfigure \n the cluster member first, then configure the controller.

Explanation    The router is configured as a PDSN cluster member. An attempt was made to configure the router as a PDSN cluster controller.

Recommended Action    Do not reconfigure the role of a PDSN, if possible. If reconfiguration must be performed, remove the configuration of the PDSN cluster member by entering the no cdma pdsn cluster member command. Then configure this PDSN as a cluster member. Note that the PDSN cluster controller is a control function. Any A10 connections currently existing in this PDSN will be terminated, and no new A10 connections can be established.

Error Message     

%_PDSN_CLUSTER-4-MEMBER_WARNING2 : No message from PDSN cluster controler \nhas been received over the past [int] seconds.

Explanation    No message has been received from the controller during the period indicated in the message text. No response was received to seek messages sent by this PDSN cluster member.

Recommended Action    Verify that the PDSN cluster controller is configured by entering the show pdsn cluster controller command in the controller CLI. If there is no response, or a message is received that the controller has not yet been configured, configure the controller. Verify that there is network connectivity between the member and the controller by entering a ping ip-address command in the member CLI, where ip-address is the IPv4 address of the controller, and enter the ping ip-address command in the controller CLI, where ip-address is the IPv4 address of one of the members. If a message is received stating that the Success rate is 0 percent, no connectivity exists. Restore network connectivity or configure the controller, the member, or both for proper routing.

Error Message     

%_PDSN_CLUSTER-4-MEMBER_WARNING3 : PDSN cluster controler has not responded \nto reconfigured member state over the past [int] seconds.

Explanation    No message has been received from the controller during the period indicated in the message text in response to a request from a member for customer- or vendor-specific extensions containing the member state.

Recommended Action    Verify that the PDSN cluster controller is configured by entering the show pdsn cluster controller command in the controller CLI. If there is no response, or a message is received that the controller has not yet been configured, configure the controller. Verify that there is network connectivity between the member and the controller by entering a ping ip-address command in the member CLI, where ip-address is the IPv4 address of the controller, and enter the ping ip-address command in the controller CLI, where ip-address is the IPv4 address of one of the members. If a message is received stating that the Success rate is 0 percent, no connectivity exists. Restore network connectivity or configure the controller, the member, or both for proper routing.

Error Message    

%_PDSN_CLUSTER-3-OPERATION_ERROR : [chars] [dec] [chars] [dec]

Explanation    An operational error has occurred. A PDSN cluster controller or member may continue normal operation despite the existence of this condition.

Recommended Action    If this message recurs frequently, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With 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    

%_PDSN_CLUSTER-5-RE_CONFIGURED1 : [chars] [chars] from [dec]([hex]) to [dec]([hex])

Explanation    This message is a logging message that captures reconfiguration of any value. It is possible that the reconfigured value is not the same as one previously configured value.

Recommended Action    Remove the existing configuration before attempting to perform any reconfiguration operations.

Error Message     

%_PDSN_CLUSTER-5-RE_CONFIGURED2 : [chars] [chars] from [IP_address] to [IP_address]

Explanation    This messages is a logging message that captures reconfiguration of an IP address. Reconfiguration is not allowed because the controller IP address already exists and is not the same as the previously configured IP address.

Recommended Action    If reconfiguration must be performed, remove the existing configuration by entering the no cdma pdsn cluster member command before performing any reconfiguration operations.

Error Message     

%_PDSN_CLUSTER-5-RE_CONFIGURED3 : [chars] [chars] [chars]

Explanation    This message is a logging message that capturse reconfiguration of a string where a configuration already exists.

Recommended Action    If reconfiguration must be performed, remove the existing configuration first by entering the no cdma pdsn cluster member command.

Error Message    

%_PDSN_CLUSTER-6-WAITING : to be configured as PDSN cluster member or controller.

Explanation    This router can be configured as either a PDSN cluster member or PDSN cluster controller. This message indicates normal system operation.

Recommended Action    Configure the router for PSDN functionality.

NRP Messages

The following are Network Routing Processor (NRP) messages.

Error Message    

%NRP-5-NO_DBS_SUPPORT : DBS is not supported

Explanation    Dynamic Bandwidth Selection is not supported by Network Routing Processor version 1. Entering the dbs enable command will have no effect on the interface.

Recommended Action    No action is required.

NRP2 Messages

The following are Network Route Processor, type 2 messages.

Error Message    

%NRP2-4-SLAVE_DOWN : NRP2-REDUNDANCY Secondary NRP2 in slot [dec], went down.

Explanation    The Primary NRP2 has lost communication with the redundant NRP2.

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    

%NRP2-5-SLAVE_UP : NRP2-REDUNDANCY Secondary NRP2 in slot [dec], came up

Explanation    The redundant NRP2 has initialized and established communication with the primary NRP2.

Recommended Action    No action is required.

NSE Messages

The following are network services engine messages.

Error Message    

%NSE-3-EREVENT : [chars]

Explanation    This is a general error message to be used for sanity testing.

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.

NSE100 Messages

The following are NSE100 messages.

Error Message    

%NSE100-4-CITXFPGA : CI-DEMUX FPGA detected an error (Status [hex])

Explanation    The cluster interconnect DEMUX FPGA detected an error in an egress packet. The type of error is indicated in the message text after "Status".

Recommended Action    This is an informational message only. If the message is seen repeatedly, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/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 c7300 pxf accounting, show c7300 pxf interfaces all, show diag and show c7300 commands and your pertinent troubleshooting logs.

Error Message     

%NSE100-3-ERRORINTR : Fatal error interrupt.
IOFPGA error interrupt statuses : Asic/FPGA [hex], Line card [hex], OIR [hex], Envm. [hex]

Explanation    The system received an error interrupt from one of the sources specified in the text of the error message. The system has undergone a software-forced crash. This condition can be caused by errors inside the line card or errors in the hardware or FPGA of the Route Processor system.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. After the router reinitializes, enter the show c7300 pxf accounting, show c7300 pxf interfaces all, show diag and show c7300 commands. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With 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 c7300 pxf accounting, show c7300 pxf interfaces all, show diag, and show c7300 commands and your pertinent troubleshooting logs.

Error Message     

%NSE100-3-FPGA_DLL : [chars] check failed. FPGA may not be operational

Explanation    The hardware of one of the NSE100 FPGAs has lost its DLL lock. This error indicates a hardware failure.

Recommended Action    Power-cycle the router. If the problem persists, attempt to upgrade the FPGA. If you are already running the latest FPGA image but are able to downgrade the FPGA, downgrade the FPGA. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/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     

%NSE100-3-GBICRDFAIL : Failed to read GBIC register after [dec] retries

Explanation    A GBIC register could not be read after multiple retries.

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     

%NSE100-4-GBIC_TYPE_UNKNOWN : Unknown GBIC type or GBIC not inserted properly
for interface GigabitEthernet[dec]/[dec]

Explanation    The GBIC type was detected as an unknown media type. This condition can occur if the GBIC is not properly inserted into its slot.

Recommended Action    Remove and reinsert the GBIC and ensure that it is seated correctly.

Error Message     

%NSE100-3-INVALID_MGMT_FE_DESC : One of the management fastethernet port receive descriptors is invalid, entry = [dec], software buffer address = [hex], hardware buffer address = [hex]

Explanation    The value of the fields in one of the management fast Ethernet port receive descriptors is not correct. This condition indicates a software failure in the management fast Ethernet driver.

Recommended Action    Attempt to reset the management fast Ethernet interface by entering the shutdown and no shutdown commands to shut down and restart the interface. If the condition persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/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 interface fastethernet 0, and show controller fastethernet 0 commands and your pertinent troubleshooting logs.

Error Message     

%NSE100-4-LCCONFIG : System hardware configuration [chars]compliant
with recommended guidelines.

Explanation    The aggregate throughput of the line cards exceeds the capacity of the NSE to the line card interface in this system.

Recommended Action    Refer to the configuration guidelines for the maximum allowed aggregate throughput for the line cards in this system.

Error Message     

%NSE100-4-LCTHRUPUT : The aggregate throughput of the Line Cards changed from [dec] kbps ([chars]compliant) to [dec] kbps ([chars]compliant)

Explanation    The aggregate throughput of the line cards in the system has been changed to make the system compliant or noncompliant with the hardware configuration guidelines.

Recommended Action    Refer to the configuration guidelines for the maximum allowed aggregate throughput for the line cards in this system.

Error Message    

%NSE100-3-MACTBLFULL : Exceeded [dec] entries in Gigabit Ethernet[dec]/[dec] MAC filter table \n while adding [enet]

Explanation    The MAC address table has exceeded its configured maximum number of entries. The MAC address table can hold only 16 entries at a time.

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    

%NSE100-3-NO_GIG_SYNC : Inband Gig interface not syncronized, status [hex]

Explanation    The hardware for transmitting and receiving packets to and from the router is not functioning properly.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/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    

%NSE100-3-NO_MISTRAL_INIT_STATUS : Mistral init status of 0xf not obtained, status [hex]

Explanation    The initialization status of the Mistral ASIC could not be properly obtained.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/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    

%NSE100-3-NO_OBL_TO_INBAND : Mistral OBL to INBAND semaphore not obtained

Explanation    The Mistral OBL-to-inband semaphore could not be properly obtained.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With 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    

%NSE100-3-NOT_IDLE : Receive path not idle after reset

Explanation    The hardware used for receive operations is not idle after it has been reset.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With 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    

%NSE100-3-QSTATUS : Queue status FPGA FIFO overflow
(Qstatus frame [hex] from the line card i/f [chars] is dropped).

Explanation    The line card egress queue status FPGA FIFO queues have become full. This condition can occur because of errors inside the QSTATUS FPGA or the line card FPGA. A software-forced system crash will occur as a result of this condition.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. After the router reinitializes, enter the show c7300 pxf accounting, show c7300 pxf interfaces all, show diag and show c7300 commands. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With 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 c7300 pxf accounting, show c7300 pxf interfaces all, show diag and show c7300 commands and your pertinent troubleshooting logs.

Error Message    

%NSE100-6-ROMMON_UPD_DONE : ROM monitor upgrade in ROM [dec] successful.

Explanation    The ROMMON upgrade has completed successfully.

Recommended Action    No action is required.

Error Message     

%NSE100-3-ROMMON_UPD_FAIL : ROM monitor upgrade in ROM [dec] failed.

Explanation    An upgrade failure or user-initiated termination has occurred during an attempt to boot the system from a new, unused image in the writable ROM. As a result of this condition, the ROMMON image in ROM 0 has been set as the default ROMMON image.

Recommended Action    Note the following points and perform one of more of the following actions:

–After a new ROMMON image has been downloaded to the writable ROM, you must reload the Cisco IOS software in order for the new ROMMON image to take effect.

–The first time a new ROMMON image is loaded, you must allow the system to boot the Cisco IOS software before performing any system resets or power cycling.

–Download the ROMMON image again to the writable ROM and restart the ROMMON upgrade process.

If the problem persists, 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     

%NSE100-4-ROMMON_UPD_TERMINATE : ROM monitor upgrade in ROM [dec] terminated.

Explanation    During an attempt to boot the system from a new, unused image in the writable ROM, a user-initiated termination has occurred. This condition causes the verification process of this new ROMMON to fail, and automatically sets the ROMMON image to be invalid.

Recommended Action    Note the following points and perform one of more of the following actions:

–After a new ROMMON image has been downloaded to the writable ROM, you must reload the Cisco IOS software for the new ROMMON image to take effect.

–The first time a new ROMMON image is loaded, you must allow the system to boot up the Cisco IOS software before performing any system resets or power cycling.

–If the ROMMON loading process is interrupted, the system interprets this as a boot up failure of the new ROMMON image. Download the ROMMON image again to the writable ROM and restart the ROMMON upgrade process.

If the problem persists, 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    

%NSE100-3-TOOBIG : attempt to send giant packet on [chars] ([dec] bytes from [hex], max allowed [dec])

Explanation    A process inside the router is attempting to send an oversized packet.

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    

%NSE100-3-VA_ERROR : Vanallen ASIC detected an error condition: [chars]

Explanation    The Van Allen ASIC has detected an error condition. This message indicates either a hardware error or an error inside the packet.

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.

NTP Messages

The following are NTP messages.

Error Message    

%NTP-6-PEERREACH : Peer [IP_address] is reachable

Explanation    The NTP peer is reachable.

Recommended Action    No action is required.

Error Message     

%NTP-5-PEERSYNC : NTP synced to peer [IP_address]

Explanation    NTP has synchronized the local clock to a new peer.

Recommended Action    No action is required.

Error Message     

%NTP-4-PEERUNREACH : Peer [IP_address] is unreachable

Explanation    The NTP peer is unreachable.

Recommended Action    Check the network connection to the peer and check to ensure that NTP is running on the peer.

Error Message     

%NTP-6-RESTART : NTP process starts

Explanation    The NTP process has just started or restarted.

Recommended Action    No action is required.

Error Message     

%NTP-6-STOP : NTP process stops

Explanation    NTP is disabled.

Recommended Action    Check to see if NTP has been purposely disabled by a system administrator.

Error Message     

%NTP-4-UNSYNC : NTP sync is lost

Explanation    NTP synchronization to its peer has been lost.

Recommended Action    Perform the following checks:

–Check the network connection to the peer.

–Check to ensure that NTP is running on the peer.

–Check to ensure that the peer itself is synchronized to a stable time source.

–Check to see that NTP packets from the peer have passed validity tests specified in RFC 1305.

OER_BR Messages

The following are Optimized Edge Routing (OER) border router messages.

Error Message    

%OER_BR-1-ALERT : [chars]

Explanation    Unavailable.7

Recommended Action    Unavailable.

Error Message     

%OER_BR-3-ERROR : [chars]

Explanation    Unavailable.7

Recommended Action    Unavailable.

Error Message     

%OER_BR-6-INFO : [chars]

Explanation    Unavailable.7

Recommended Action    Unavailable.

Error Message     

%OER_BR-5-NOTICE : [chars]

Explanation    Unavailable.7

Recommended Action    Unavailable.

Error Message     

%OER_BR-4-WARNING : [chars]

Explanation    Unavailable.7

Recommended Action    Unavailable.

OER_MC Messages

The following are Optimized Edge Routing (OER) master controller messages.

Error Message     

%OER_MC-1-ALERT : [chars]

Explanation    Unavailable.7

Recommended Action    Unavailable.

Error Message     

%OER_MC-0-EMERG : [chars]

Explanation    Unavailable.7

Recommended Action    Unavailable.

Error Message     

%OER_MC-3-ERROR : [chars]

Explanation    Unavailable.7

Recommended Action    Unavailable.

Error Message     

%OER_MC-6-INFO : [chars]

Explanation    Unavailable.7

Recommended Action    Unavailable.

Error Message     

%OER_MC-5-NOTICE : [chars]

Explanation    Unavailable.7

Recommended Action    Unavailable.

Error Message     

%OER_MC-4-WARNING : [chars]

Explanation    Unavailable.7

Recommended Action    Unavailable.

OER_TT_FLOW Messages

The following are Optimized Edge Routing (OER) top talkers flow border router messages.

Error Message     

%OER_TT_FLOW-2-OER_TT_FLOW_BR_CACHEINIT : Error initializing OER TT Flow BR cache

Explanation    The NetFlow Top Talker cache could not be initialized on the border router because of a low-memory condition.

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

Error Message     

%OER_TT_FLOW-2-OER_TT_FLOW_BR_EXPORTINIT : Error initializing OER TT Flow BR Export queue

Explanation    The OER NetFlow Top Talker export queue could not be initialized on the border router because of a low-memory condition.

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

Error Message    

%OER_TT_FLOW-4-OER_TT_FLOW_BR_FLOWEXPORT : Error exporting [chars]

Explanation    An error involving a flow to the RP has occurred.

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

OIR Messages

The following are online insertion and removal (OIR) messages.

Error Message    

%OIR-6-CONSOLE : Changing console ownership to [chars] processor

Explanation    The OIR facility has switched the console to the specified processor.

Recommended Action    No action is required.

Error Message    

%OIR-3-PLUGIN_INIT_FAIL : Unable to create driver plugin in slot [dec]/[dec].

Explanation    A valid line card driver could not be plugged in. This condition might be the result of a memory allocation failure.

Recommended Action    Retry the line card OIR operation.

Error Message    

%OIR-3-PWRCYCLE : Card in slot [dec], is not responding; it is being power-cycled

Explanation    The OIR facility detected the line card as unresponsive and attempted to power-cycle the card.

Recommended Action    No action is required.

Error Message    

%OIR-3-STATE_MACHINE_BUG2 : Card_oir_insert_card: already have [hex], removing.

Explanation    The system has detected an invalid card type. The OIR operation will not be performed.

Recommended Action    Enter the show ip interface brief command to determine the resource allocated and determine the error. 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    

%OIR-3-UNKNOWN : Unknown card in slot [dec], card is being disabled

Explanation    The OIR facility detected a line card but could not determine the type.

Recommended Action    Reseat the card in the indicated slot.

ON_DIAG Messages

The following are online diagnostics subsystem messages.

Error Message    

%ON_DIAG-3-ALARM_UPDATE : [chars], Testname ([chars]), Type ([chars])

Explanation    The alarm for the test is being updated.

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    

%ON_DIAG-3-CLI_ERR : CLI failure [chars]

Explanation    A failure has occurred that may result in missing CLI commands or configuration options.

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    

%ON_DIAG-3-DG_INT_ERR : [chars]

Explanation    An internal error involving the online diagnostics subsystem 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    

%ON_DIAG-3-DG_PROC_ERR : Failed to spawn [chars] process

Explanation    An internal error has occurred a diagnostic process was attempting to be spawned.

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    

%ON_DIAG-3-NO_TST_CNF : Test suite configuration file not found

Explanation    The diagnostics configuration file could not be located. This condition indicates an internal 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    

%ON_DIAG-3-NULL_CTC : Null CTC message received

Explanation    An empty CTC message has been received.

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    

%ON_DIAG-3-NULL_DG_MSG : Null diagnostic message received

Explanation    An empty diagnostic message has been received.

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    

%ON_DIAG-3-UNKNOWN_CTC : Unknown CTC message type [dec] received

Explanation    An unknown CTC message type has been received.

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    

%ON_DIAG-3-UNKNOWN_DG_EVTCLASS : Unknown diagnostic event class [dec]

Explanation    An unknown diagnostic event class has been detected.

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    

%ON_DIAG-3-UNKNOWN_DG_MSG : Unknown diagnostic message type [dec] received

Explanation    An unknown diagnostic message type has been received.

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.

OSPF Messages

The following are Open Shortest Path First (OSPF) messages.

Error Message    

%OSPF-6-BADCHKSUM : Checksum Failure in database in area [chars]. Link State Id [IP_address] Old Checksum [hex] New Checksum [hex]

Explanation    OSPF has detected a checksum error in the database due to memory corruption.

Recommended Action    Restart the OSPF process.

Error Message     

%OSPF-4-BADLSAMASK : Bad LSA mask: Type [dec], LSID [IP_address] Mask [IP_address] from [IP_address]. NOTE: This route will not be installed in the routing table.

Explanation    The router has received an LSA with an invalid LSA mask. The cause is likely due to an incorrect configuration from the originator of the LSA.

Recommended Action    Find the originating router of this LSA with the invalid mask and correct any misconfiguration of the network for this LSA. For further debugging 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     

%OSPF-4-BADLSATYPE : Invalid lsa: [chars] Type [dec], LSID [IP_address] from [IP_address], [IP_address], [chars]

Explanation    The router has received an LSA with an invalid LSA type. The cause is either memory corruption or unexpected behavior on a router.

Recommended Action    Perform the following actions:

1. From a neighboring address, locate the problem router.

2. Collect a running configuration of the router by entering the show running-config command.

3. Enter the show ip ospf database command to gather data that may help identify the nature of the error.

4. Enter the show ip ospf database link-state-id command, with link-state-id being the IP address of the invalid LSA.

5. Enter the show logging command to gather data that may help identify the nature of the error. Reboot the router.

If you cannot determine the nature of the error from the collected information, 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    

%OSPF-4-CONFLICTING_LSAID : Found LSA with the same host bit set but using different mask: Existing: LSA ID [IP_address][IP_netmask] New: Destination [IP_address][IP_netmask]

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 nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%OSPF-4-NORTRID : OSPF process [dec] cannot pick a router-id. Please configure manually or bring up an interface with an ip address.

Explanation    An OSPF process failed while it was attempting to allocate a router ID from the IP address of one of its interfaces.

Recommended Action    Ensure that at least one interface is active (up) and has a valid IP address. If there are multiple OSPF processes running on the router, each requires a unique router ID. You must have enough active (up) interfaces so that each of them can obtain a router ID.

Error Message    

%OSPF-4-OSPF_MAX_LSA : Maximum number of non self-generated LSA has been exceeded "[chars]" - [dec] LSAs

Explanation    The maximum threshold for non-self-generated LSAs has been exceeded.

Recommended Action    Check to see if a router in the network is generating a large number of LSAs as a result of a misconfiguration.

Error Message     

%OSPF-4-OSPF_MAX_LSA_THR : Threshold for maximum number of non self-generated LSA has been reached "[chars]" - [dec] LSAs

Explanation    The maximum threshold for the number of non-self-generated LSA has been reached.

Recommended Action    Check to see if a router in the network is generating a large number of LSAs as a result of a misconfiguration.

Error Message    

%OSPF-4-WRONG_DEFAULT : Found generating default LSA with non-zero mask: LSA type : [dec] Mask : [IP_address] metric : [int] area : [chars]

Explanation    The router has attempted to generate a default LSA with an incorrect mask and, possibly, an incorrect metric due to an internal software error.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/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.

OSPFv3 Messages

The following are Open Shortest Path First Version 3 messages.

Error Message    

%OSPFv3-4-DUP_RTRID_AREA : Detected router with duplicate router ID [IP_address] in area [chars]

Explanation    An OSPF process received a hello packet from a neighbor that has the same router ID as this routing process. A full adjacency cannot be established.

Recommended Action    The OSPF router ID should be unique. Change the router ID of the neighbor.

Error Message    

%OSPFv3-3-INVALID_ENCR_KEY : Invalid encrypted key [chars].

Explanation    The specified encrypted key is not valid.

Recommended Action    Either specify a cleartext key and enter the service password-encryption command for encryption, or ensure that the specified encrypted key is valid. If the specified encrypted key is not valid, an error message will be displayed during system configuration.

Error Message     

%OSPFv3-3-IPSEC_CLOSE_SS_ERROR : Unable to close secure socket with SPI [int] on interface [chars]

Explanation    An IPSec API error has occurred. This message indicates an internal error.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/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    

%OSPFv3-3-IPSEC_CREATE_POLICY_ERROR : [chars] error occured when attempting to create an IPsec policy for SPI [int]

Explanation    An IPSec API error occurred. This message indicates an internal error.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/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    

%OSPFv3-3-IPSEC_ERROR_MSG_ABORT : IPsec sent a [chars] message [chars] to OSPFv3 for interface [chars]. Recovery aborted

Explanation    An internal software error has occurred. The maximum number of recovery attempts has been exceeded.

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    

%OSPFv3-3-IPSEC_ERROR_MSG_RETRY : IPsec sent a [chars] message [chars] to OSPFv3 for interface [chars]. Recovery attempt [dec]

Explanation    An internal error has occurred. The system is attempting to reopen the secure socket.

Recommended Action    The system will attempt to recover. No action is required.

Error Message     

%OSPFv3-3-IPSEC_GENERAL_ERROR : IPsec reported a GENERAL ERROR: message [chars], count [dec]

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    

%OSPFv3-3-IPSEC_POLICY_ALREADY_EXIST : SPI [int] is already in use with ospf process [dec].

Explanation    An attempt was made to use an SPI that has already been used.

Recommended Action    Choose a different SPI.

Error Message     

%OSPFv3-3-IPSEC_POLICY_INVALID_KEY_LEN : The key length used with SPI [int] is not valid

Explanation    The key length that was used with the SPI was incorrect. An MD5 authentication key must be 32 hexadecimal digits long.

Recommended Action    Choose a valid IPSec key.

Error Message     

%OSPFv3-3-IPSEC_POLICY_NOT_EXIST : SPI [int] is not being used by ospf process [dec].

Explanation    An attempt was made to unconfigure an SPI that is not being used by the OSPFv3 process.

Recommended Action    Enter a show command to see the SPIs that are being used by OSPFv3.

Error Message     

%OSPFv3-3-IPSEC_POLICY_SPI_IN_USE : SPI [int] is already in use by a process other than ospf process [dec].

Explanation    An attempt was made to use an SPI that is already in use.

Recommended Action    Choose a different SPI. Enter the show crypto ipv6 ipsec sa command to view a list of SPIs that are already being used.

Error Message     

%OSPFv3-3-IPSEC_POLICY_SPI_REUSE : [chars] [chars] is already configured with SPI [int].

Explanation    An attempt was made to use an SPI that is already in use.

Recommended Action    Unconfigure the SPI first, or choose a different one.

Error Message     

%OSPFv3-3-IPSEC_POLICY_STILL_IN_USE : The policy for SPI [int] could not be removed because it is in use.

Explanation    An attempt was made to remove the policy for the SPI specified in the message text, but the policy was still being used by a secure socket.

Recommended Action    No action is required.

Error Message     

%OSPFv3-3-IPSEC_REGISTER_CLIENT : OSPFv3 was unable to register with IPsec

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    

%OSPFv3-3-IPSEC_REMOVE_POLICY_ERROR : [chars] error occured when attemtping to remove the IPsec policy with SPI [int]

Explanation    An IPSec API error has occurred. This message indicates an internal error.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/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    

%OSPFv3-4-TWO_INT_ON_LINK : Multiple interfaces ([chars]/[chars]) on a single link detected. This is not supported

Explanation    OSPFv3 enabled on multiple interfaces on the same link is not supported.

Recommended Action    OSPFv3 should be disabled or made passive on all but one of the interfaces.

Error Message    

%OSPFv3-3-UNEXPECTED_MESSAGE : OSPFv3 has received an unexpected message: [hex] / [hex]

Explanation    The OSPFv3 process has received an unexpected interprocess 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.

PA Messages

The following are port adapter (PA) messages.

Error Message    

%PA-4-IMPROPER_REMOVAL : Improper removal for slot [dec].

Explanation    A PA was inserted and then removed while being initialized. If there is traffic running through the router, the initialization can take up to 30 seconds.

Recommended Action    After an insertion, the PA should be pulled out only after the initialization is complete.

PACC Messages

The following are Cisco 7300 port adapter carrier card (PACC) messages.

Error Message     

%PACC-1-ALLOCFAIL : [chars] (slot [dec]) [chars] allocation failure

Explanation    The router has failed to allocate sufficient memory for a component of the PA carrier card. The affected component is displayed after the slot number in the message text.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show memory summary 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, show tech-support, and show memory summary commands and your pertinent troubleshooting logs.

Error Message    

%PACC-0-DLL_OUTOFLOCK : [chars] HW DLLs failed to lock in linecard at slot [dec]

Explanation    The port adapter carrier card has failed to initialize. This condition indicates a hardware failure.

Recommended Action    Remove and reinsert the port adapter carrier card. If reseating the card does not fix the problem, a later Cisco IOS software image may have an updated FPGA bundle that could solve the problem. If this message recurs, 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, 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, and show diag slot-number commands and your pertinent troubleshooting logs.

Error Message    

%PACC-3-FLOWCTRL : PA-CC FPGA flow control failure from slot [dec]

Explanation    The FPGA on the port adapter carrier card cannot generate a flow-control frame. This problem could be caused by faulty hardware (either the Cisco 7300 or the port adapter carrier card), by a corrupted FPGA image, or, with a very low likelihood, by a software error.

Recommended Action    If this message occurs frequently, remove and reinsert the port adapter carrier card. If reseating the card does not fix the problem, a later Cisco IOS software image may have an updated FPGA bundle that could solve the problem. If this message recurs, 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, 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, and show diag slot-number commands and your pertinent troubleshooting logs.

Error Message    

%PACC-3-HEARTBEAT_LOSS : [chars] Loss of heartbeat from linecard in slot [dec]

Explanation    The port adapter carrier card has failed to send keepalive messages (heartbeats) to the RP. The slot number is specified in the error message. This condition usually indicates a software error.

Recommended Action    Copy the error message, and any messages preceding this message that might be related to this message, exactly as they appear on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With 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     

%PACC-0-INITFAIL : [chars] initialization failure for slot [dec], [chars]

Explanation    The initialization of a device on the port adapter carrier card has failed. The error message specifies the device whose initialization has failed. The message also displays the slot number and either the interface name or more details about the error. This condition indicates a software error.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show memory summary 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, show tech-support, and show memory summary commands and your pertinent troubleshooting logs.

Error Message    

%PACC-3-NOPA : No port adapter detected in slot [dec]

Explanation    The port adapter carrier card ROMMON cannot detect a port adapter being plugged into the port adapter carrier card.

Recommended Action    Ensure that the port adapter is plugged correctly into the port adapter carrier card.

Error Message     

%PACC-3-NOPATYPE : No port adapter type obtained for slot [dec]

Explanation    The port adapter carrier card ROMMON has not reported any information about the port adapter that is plugged into the port adapter carrier card. This condition could be caused by either a hardware or a software problem and indicates a communication problem between the ROMMON for the carrier card and the Cisco 7300.

Recommended Action    Remove and reinsert the port adapter carrier card. If this message recurs, 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, 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, and show diag slot-number commands and your pertinent troubleshooting logs.

Error Message    

%PACC-3-REVNOTSUPPORTED : The PA-CC in slot [dec] contains a PA with a H/W revision of ([dec].[dec]). The required minimum H/W revision for this PA is ([dec].[dec]).

Explanation    The port adapter in the slot specified in the error message has an old hardware revision level. A newer hardware revision level of the port adapter is required for the port adapter carrier card to function on the chassis.

Recommended Action    Replace the older port adapter with a port adapter that has a newer hardware revision level. The minimum hardware revision level is shown in the error message.

Error Message     

%PACC-3-RXOFLOW : PA-CC FPGA ingress buffer overflow on slot [dec]

Explanation    The FPGA on the port adapter carrier card has detected a failure of hardware flow control for ingress frames. This problem could be caused by faulty hardware (either the Cisco 7300 or the port adapter carrier card), by a corrupted FPGA image, or, with a very low likelihood, by a software error.

Recommended Action    Remove and reinsert the port adapter carrier card. If reseating the card does not fix the problem, a later Cisco IOS software image may have an updated FPGA bundle that could solve the problem. If this message recurs, 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, 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, and show diag slot-number commands and your pertinent troubleshooting logs.

Error Message    

%PACC-3-RXPAKLEN : PA-CC FPGA detected an ingress packet length error on slot [dec]

Explanation    The PA carrier card has detected a packet length error while an ingress packet was being received. This condition could be caused by one of the following:

–Faulty hardware involving either the Cisco 7300 or the PA carrier card

–A corrupted FPGA image

–By software problems (very unlikely)

Recommended Action    Remove and reinsert the port adapter carrier card. If reseating the card does not fix the problem, a later Cisco IOS software image may have an updated FPGA bundle that could solve the problem. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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    

%PACC-3-RXPARITY : Ingress packet parity error on slot [dec]

Explanation    The FPGA on the PA carrier card detected a parity error on an ingress frame.

Recommended Action    Remove and reinsert the port adapter carrier card. If reseating the card does not fix the problem, a later Cisco IOS software image may have an updated FPGA bundle that could solve the problem. If this message recurs, 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, 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, and show diag slot-number commands and your pertinent troubleshooting logs.

Error Message    

%PACC-3-RXSMALLPAK : PA-CC FPGA ingress packet too small error on slot [dec]

Explanation    The FPGA on the port adapter carrier card has detected a packet that is too small for an ingress frame from the port adapter carrier card CPU interface.

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, 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, and show diag slot-number commands and your pertinent troubleshooting logs.

Error Message    

%PACC-3-SYSRET : PA-CC in slot [dec] has returned to ROM Monitor:\n[chars]

Explanation    The port adapter carrier card in the slot specified in the error message has experienced a system failure and has returned to ROMMON mode. Additional information in the error message shows the stack trace from the port adapter carrier card failure.

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, 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, and show diag slot-number commands and your pertinent troubleshooting logs.

Error Message    

%PACC-3-TXERROR : PA-CC FPGA Common Logic egress packet error on slot [dec]

Explanation    The backplane side of the common logic in the FPGA on the port adapter carrier card has experienced an error on an egress packet. This problem could be caused by faulty hardware (either the Cisco 7300 or the port adapter carrier card), by a corrupted FPGA image, or, with a very low likelihood, by a software error.

Recommended Action    Remove and reinsert the port adapter carrier card. If reseating the card does not fix the problem, a later Cisco IOS software image may have an updated FPGA bundle that could solve the problem. If this message recurs, 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, 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, and show diag slot-number commands and your pertinent troubleshooting logs.

Error Message    

%PACC-3-TXOFLOW : PA-CC FPGA Common Logic egress buffer overflow on slot [dec]

Explanation    The backplane side of the common logic in the FPGA on the port adapter carrier card has experienced a buffer overflow for egress packets. This problem could be caused by faulty hardware (either the Cisco 7300 or the port adapter carrier card), by a corrupted FPGA image, or, with a very low likelihood, by a software error.

Recommended Action    Remove and reinsert the port adapter carrier card. If reseating the card does not fix the problem, a later Cisco IOS software image may have an updated FPGA bundle that could solve the problem. If this message recurs, 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, 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, and show diag slot-number commands and your pertinent troubleshooting logs.

Error Message    

%PACC-3-TXPAKLEN : PA-CC FPGA detected an egress packet length error on slot [dec]

Explanation    The PA carrier card has detected a packet length error while an egress packet was being transmitted. This condition could be caused by either faulty hardware involving either the Cisco 7300 or the PA carrier card, by a corrupted FPGA image, or, with a very low likelihood, by software problems.

Recommended Action    If this occurs frequently, remove and reinsert the PA carrier card. If reseating the card does not fix the problem, a later Cisco IOS image may have an updated FPGA bundle that could solve the problem. If this message recurs, copy the 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, 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, and show diag slot-number commands and your pertinent troubleshooting logs.

Error Message     

%PACC-3-TXPARITY : Egress packet parity error on slot [dec]

Explanation    The FPGA on the port adapter carrier card has detected a parity error on an egress frame. This problem could be caused by faulty hardware (either the Cisco 7300 or the port adapter carrier card), by a corrupted FPGA image, or, with a very low likelihood, by a software error.

Recommended Action    Remove and reinsert the port adapter carrier card. If reseating the card does not fix the problem, a later Cisco IOS software image may have an updated FPGA bundle that could solve the problem. If this message recurs, 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, 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, and show diag slot-number commands and your pertinent troubleshooting logs.

Error Message    

%PACC-3-TXSLOTID : Egress packet slot ID mismatch on slot [dec]

Explanation    The FPGA on the port adapter carrier card has detected a slot ID mismatch on an egress packet. This problem could be caused by faulty hardware (either the Cisco 7300 or the port adapter carrier card), by a corrupted FPGA image, or, with a very low likelihood, by a software error.

Recommended Action    Remove and reinsert the port adapter carrier card. If reseating the card does not fix the problem, a later Cisco IOS software image may have an updated FPGA bundle that could solve the problem. If this message recurs, 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, 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, and show diag slot-number commands and your pertinent troubleshooting logs.

Error Message    

%PACC-3-UNKNPA : Unrecognized port adapter in slot [dec]

Explanation    The port adapter carrier card ROMMON has detected a port adapter but has not been able to determine the port adapter type from the port adapter IDPROM.

Recommended Action    Remove the port adapter carrier card, and then remove the port adapter from the line card. Reinsert the port adapter into the line card and ensure that the port adapter is fully inserted. Close the latch on the port adapter carrier card and reinsert the port adapter carrier card into the router. If the problem persists, insert the port adapter into another Cisco router (for example, a Cisco 7200, Cisco 7400, Cisco 7301, or Cisco 7500). If the port adapter is not functional in another router, the port adapter has to be replaced.

Error Message     

%PACC-3-UNSUPPORTED_PA : Unsupported port adapter (type [dec]) in slot [dec]

Explanation    An unsupported port adapter of the indicated type has been inserted into the port adapter carrier card in the slot indicated in the error message.

Recommended Action    Replace the port adapter.

PACC_IPC Messages

The following are Port Adapter Carrier Card (PACC) interprocess communication (IPC) messages.

Error Message     

%PACC_IPC-1-DECODE : Unrecognised message: [dec]

Explanation    The port adapter carrier card has received an unrecognized IPC message. The error message shows the unrecognized command. This condition indicates a software 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    

%PACC_IPC-0-DOORBELL : Doorbell register information incorrect

Explanation    A number of parameters are passed to the initialization code through registers known as doorbells. The parameters supplied by the RP are of an incorrect 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    

%PACC_IPC-0-DOORBELL_NOINT : Nothing written to doorbells yet

Explanation    The RP software has not written the information required by the port adapter carrier card startup code. Because the startup code does not wait for the data, the port adapter carrier card could not be 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    

%PACC_IPC-3-EGRESS : IPC received too many particles ([dec])

Explanation    The IPC code on the port adapter carrier card received a packet that had too many particles. This condition indicates a software 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    

%PACC_IPC-1-EVENT : Unexpected wakeup event [dec]. Process: [chars]

Explanation    An unexpected event was received in a process while waiting for timer events. This condition indicates a software 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    

%PACC_IPC-1-EVENT_PORT : Cannot open event port. IPC error [chars]

Explanation    The IPC port that receives events from the RP could not be opened. The IPC error code is specified at the end of the error 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    

%PACC_IPC-0-IPC_MASTER : Cannot create the master seat

Explanation    The master IPC seat could not be created. The master seat resides on the RP. The port adapter carrier card was not able to create an entry to the RP seat. This error indicates a communication problem with the RP.

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    

%PACC_IPC-1-LOCAL_CMD : Cannot register local command port. IPC error [chars]

Explanation    The IPC local command port could not be registered with the RP. The IPC error code is specified at the end of the error 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    

%PACC_IPC-1-PORT_CREATE : Cannot create IPC port. IPC error [chars]

Explanation    The IPC command port could not be created on the port adapter carrier card. This condition indicates a resource allocation problem in the IPC code.

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    

%PACC_IPC-3-REPLY_MSG : Cannot obtain an IPC reply buffer

Explanation    The port adapter carrier card could not obtain an IPC message buffer to send a reply back to the RP. This condition indicates a resource allocation problem in the IPC code.

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    

%PACC_IPC-3-SEND_FAILED : Failed to send IPC message. IPC error [chars]

Explanation    An IPC message could not be sent. This condition indicates a resource allocation problem in the IPC code.

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.

PARSER Messages

The following are parser messages.

Error Message    

%PARSER-3-BADUNLOCKREQ : Unlock requested by process '[dec]'. You are not the lock owner

Explanation    A configuration unlock has been requested by an alien.

Recommended Action    Check the code flow for an unwanted configuration unlock request.

Error Message    

%PARSER-3-CFGLOG_CLI_INITFAILED : Initialization of the Config Log CLI failed.

Explanation    Initialization of the configuration log CLI failed. Configuration logging CLI commands may not be accessible. The configuration logger may not be accessible by using Cisco IOS software CLI commands.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With 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    

%PARSER-3-CFGLOG_EMPTYCMD : User:[chars]

Explanation    The user entered an empty command for which a log attempt was made. Normally, empty commands will not be logged.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show version and show cfglog user username xml detailed commands, with username being the user name listed in the error message text. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With 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     

%PARSER-3-CFGLOG_INCONSISTENT : User:[chars] command:[chars]

Explanation    When logging a command entered by CLI, the configuration logger detected an inconsistency in the log. This inconsistency may result in a failure to log the command.

Recommended Action    Copy the error message exactly as it appears on the console or on the system log. Enter the show version command. If possible, determine which users are presently logged in to the router, and who was copying configuration files or executing commands in global configuration mode (or via SNMP or HTTP). If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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     

%PARSER-3-CFGLOG_INITFAILED : Initialization of the Config Log subsystem failed.

Explanation    During initialization of the configuration logger subsystem, one or more queues or data structures that are essential to the configuration logger could not be set up. As a result, the configuration logger will not be available for use.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show version command. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/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     

%PARSER-5-CFGLOG_LOGGEDCMD : User:[chars] logged command:[chars]

Explanation    The configuration logger, which logs every CLI command, has an option to log messages to system logging (syslog). If this option is enabled, this message will be displayed every time a CLI command is processed. This message does not denote any error condition and is a part of the normal operation of the parser and configuration logger.

Recommended Action    If you do not wish to see this syslog message, enter the no cfglog send to syslog command.

Error Message    

%PARSER-3-CFGLOG_NOMEM : User:[chars] [chars]

Explanation    The command that was entered could not be logged because of a lack of memory. The configuration logger will free old entries one by one until the system logger (syslog) has enough memory to log the command so that an NMS can receive notification of it.

Recommended Action    Attempt to free up memory on the router by stopping nonessential processes or unused features that may be running. Once sufficient memory is available, this message no longer appears.

Error Message    

%PARSER-3-CFGLOG_NOUSER : Command:[chars]

Explanation    The user could not be determined while this command was being logged. Therefore, the command could not be saved in the configuration log.

Recommended Action    Copy the error message exactly as it appears on the console or on the system log. Enter the show version command. If possible, determine which users are presently logged in to the router and who was copying configuration files or executing commands in global configuration mode (or via SNMP or HTTP). If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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    

%PARSER-3-CFGLOG_RESIZE_FAILED : Could not resize the config logger to new size:[dec]

Explanation    Because of an internal error, a request to resize the configuration log was not started or completed. Apart from a failure to resize, there should be no change in the behavior of the configuration logger.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show version command. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/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    

%PARSER-3-CFGLOG_SESSIONERR : Could not delete config log session:[dec] for user:[chars].

Explanation    When a user logged out, the configuration logger was unable to clean up information about the login session for the user. This condition might result in a memory leak or in an inability to add new commands to the configuration log.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show version command. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/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    

%PARSER-6-CONFIGLOCKCLEARED : Configuration lock cleared by user '[chars]' process '[dec]' from terminal '[dec]'

Explanation    A configuration lock has been cleared by using a clear configuration lock command.

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

Error Message     

%PARSER-6-CONFIGLOCKNOTSUPPORTED : Configuration lock not supported for this transport '[chars]'

Explanation    Configuration lock enabled from a transport other than telnet/SSH.

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

Error Message     

%PARSER-3-CONFIGNOTLOCKED : Unlock requested by process '[dec]'. Configuration not locked.

Explanation    Configuration unlock requested on a FREE lock.

Recommended Action    Check the code flow for excess configuration unlock request.

Error Message     

%PARSER-6-EXPOSEDLOCKACQUIRED : Exclusive configuration lock acquired by user '[chars]' from terminal '[dec]'

Explanation    Exclusive configuration lock acquired by the user.

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

Error Message     

%PARSER-6-EXPOSEDLOCKRELEASED : Exclusive configuration lock released by user '[chars]'from terminal '[dec]'

Explanation    Exclusive configuration lock released by the user.

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

Error Message    

%PARSER-6-LI_VIEW_INIT : LI-View initialised.

Explanation    LI-View has successfully been initialized.

Recommended Action    No action is required.

Error Message    

%PARSER-6-SUPER_VIEW_CREATED : super view '[chars]' successfully created.

Explanation    A super view has been successfully created. The system has entered into view configuration mode.

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

Error Message     

%PARSER-6-SUPER_VIEW_DELETED : super view '[chars]' successfully deleted.

Explanation    A super view has been successfully deleted.

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

Error Message    

%PARSER-6-SUPER_VIEW_EDIT_ADD : view [chars] added to superview [chars].

Explanation    A view has been successfully added to the super view. All view-related configurations can be accessed from the super view.

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

Error Message    

%PARSER-6-SUPER_VIEW_EDIT_REMOVE : view [chars] removed from superview [chars].

Explanation    A view has been successfully removed from the super view.

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

Error Message    

%PARSER-6-VIEW_CREATED : view '[chars]' successfully created.

Explanation    The view has successfully been created and the user is currently in view configuration mode.

Recommended Action    No action is required.

Error Message     

%PARSER-6-VIEW_DELETED : view '[chars]' successfully deleted.

Explanation    The specified view has been successfully deleted.

Recommended Action    No action is required.

Error Message     

%PARSER-6-VIEW_SWITCH : successfully set to view '[chars]'.

Explanation    The view has been successfully switched to the view specified in the message.

Recommended Action    No action is required.

PCI_FE Messages

The following are Peripheral Component Interconnect (PCI) Fast Ethernet (FE) messages.

Error Message    

%PCI_FE-3-ID_INVALID : PCI FE MAC id [hex] is different from expected id [hex]

Explanation    The PCI FE MAC vendor and device identification number are invalid. The PCI FE MAC hardware used for the RSC BIC might be faulty, or it can have the wrong version. The RSC BIC might not operate as expected.

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.

PCMCIAFS Messages

The following are PCMCIA disk messages.

Error Message    

%PCMCIAFS-5-DFS_CLOSE_ERR : Error during close of the file [chars]. [chars]

Explanation    An error occurred during a file close operation.

Recommended Action    Enter the fsck filesystem: command, with filesystem: being the file system prefix indicating the disk to be checked, to check and attempt to repair the disk. If this operation does not fix the problem, reformat the disk.

Error Message    

%PCMCIAFS-4-DFS_FSCK_ERR : Error while running fsck on the file [chars].

Explanation    Fsck is running in a loop while walking through the cluster chain of a file and has aborted.

Recommended Action    Report this occurrence to Engineering. Use Topic to search for a similar bug. If you find none, submit a bug report for this problem.

Error Message    

%PCMCIAFS-3-RESETERR : PCMCIA disk [dec] [chars]

Explanation    A PCMCIA disk could not be reset while the system was being initialized or reloaded. This condition will cause a transient disk error or disk timeout error, when the ROMMON initialization code attempts to read the DIB. The system will be able to access the disk and continue normal system operation.

Recommended Action    No action is required.

PIF Messages

The following are RSC PIF messages.

Error Message    

%PIF-3-DOWNLOAD_ERROR : [chars], [chars]

Explanation    The image for the port interface could not be downloaded because the image either is corrupt, is invalid, or is not available. The interface could not be initialized.

Recommended Action    Check the port interface status by entering the show pif command, and repeat the procedure with port interface debug logs enabled. Enter the debug pif download command to enable the debug log. 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    

%PIF-3-DOWNLOAD_SUBSYS_ERROR : [chars]

Explanation    The download subsystem could not be created. The download procedure could not be started. The download attempt might not succeed.

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    

%PIF-3-DYN_DOWNLOAD_ERROR : [chars], [chars]

Explanation    The image for the port interface could not be downloaded because the image either is corrupt, is invalid, or is not available. The interface could not be initialized.

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    

%PIF-3-EPIF_MIPC_ERROR : [chars]

Explanation    An error occurred while port interface-related operations were being performed on the board. This message indicates that an operation has failed. This condition may occur if the port interface is not initialized properly.

Recommended Action    Check to see if the port interface process is up and running on the port interface board by entering the show pif 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 nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PIF-3-GIGE_AUTO_NEG_INIT_ERROR : [chars]

Explanation    The Gigabit Ethernet autonegotiation operation failed while the Gigabit Ethernet interface was being configured.

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    

%PIF-3-GIGE_DISABLE_GMAC_ERROR : [chars]

Explanation    The gigabit MAC could not be disabled while the Gigabit Ethernet interface was being disabled.

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    

%PIF-3-GIGE_ENABLE_GGI_ERROR : [chars]

Explanation    The generic Gigabit Ethernet interface could not be enabled while the Gigabit Ethernet interface was being initialized.

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    

%PIF-3-GIGE_INIT_GMAC_ERROR : [chars]

Explanation    The gigabit MAC could not be initialized while the Gigabit Ethernet interface was being configured.

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    

%PIF-3-GIGE_LINKUP_INIT_ERROR : [chars]

Explanation    The Gigabit Ethernet linkup initialization operation failed while Gigabit Ethernet was being configured.

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    

%PIF-3-IDB_CONFIG_PUNT_ERROR : Error configuring [char]PIF on RSC [dec] for packet punting

Explanation    The system could not configure the specified hardware to redirect packets to the specified RSC. The most likely cause of this condition is the absence or failure of the peer RSC.

Recommended Action    Replace or insert the peer RSC. 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    

%PIF-3-PIF_INTERNAL : Internal PIF error [[chars]]

Explanation    An internal error occurred in the port interface driver software.

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    

%PIF-3-PIF_MAC_ERROR : [chars], [chars]

Explanation    An internal software error has occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With 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    

%PIF-3-PIF_RESET_INT : Function [chars] called from interrupt context

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 nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PIF-3-READ_IMEM_ERROR : [chars], [chars]

Explanation    An error occurred while operations relating to the port interface were being performed on the board. An operation has failed. This condition may occur if the port interface is not initialized properly.

Recommended Action    Check to see that the port interface process is up and running on the port interface board by entering the show pif 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 nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PIF-3-READ_PHY_ERROR : [chars], [chars]

Explanation    An error occurred while operations relating to the port interface were being performed on the board. An operation has failed. This condition may occur if the port interface is not initialized properly.

Recommended Action    Check to see that the port interface process is up and running on the port interface board by entering the show pif 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 nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PIF-3-SLICER_ENABLE_ERROR : Enabling Tx/Rx on SMDR for [chars] port[dec] failed

Explanation    An error relating to the port interface has occurred. The transceiver on the Station Message Detail Recording port could not be enabled.

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    

%PIF-3-UNKNOWN_EGRESS_CARD_TYPE_ERROR : Unknown Egress Card type [hex] for RSC [dec].

Explanation    The system could not configure the specified hardware. The most likely cause is that the egress card either is unsupported or has experienced a hardware failure.

Recommended Action    Replace the RSC or the egress card of the RSC. 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    

%PIF-3-WRITE_IMEM_ERROR : [chars], [chars]

Explanation    An error occurred while operations relating to the port interface were being performed on the board. An operation has failed. This condition may occur if the port interface is not initialized properly.

Recommended Action    Check to see that the port interface process is up and running on the port interface board by entering the show pif 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 nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PIF-3-WRITE_PHY_ERROR : [chars], [chars]

Explanation    An error occurred while operations relating to the port interface were being performed on the board. An operation has failed. This condition may occur if the port interface is not initialized properly.

Recommended Action    Check to see that the port interface process is up and running on the port interface board by entering the show pif 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 nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PIF-3-XPIF_MIPC_ERROR : [chars]

Explanation    An error occurred while operations relating to the port interface were being performed on the board. An operation has failed. This condition may occur if the port interface is not initialized properly.

Recommended Action    Check to see that the port interface process is up and running on the port interface board by entering the show pif 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 nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.