Table Of Contents
PORT_SECURITY Messages
The following are port security messages.
Error Message%PORT_SECURITY-2-INELIGIBLE : Port security configuration on [chars] is being made inactive since the port is now not eligible for port security as [chars].
Explanation A port had port security configuration on it, but the port now has a configuration not supported with port security. Since the port is now not eligible for port security, the port security configuration on it is being made inactive.
Recommended Action Check the port's configuration and remove the offending configuration that is not compatible with port security.
Error Message%PORT_SECURITY-6-VLAN_REMOVED : VLAN(S) [chars] is/are no longer allowed on port [chars]. Their port security configuration has been removed.
Explanation A configured vlan has been excluded on a trunk port and is being removed from the configuration.
Recommended Action No action is required.
POS Messages
The following are Packet over SONET subsystem messages.
Error Message%POS-3-ISSU_ATTACH : POS LC ISSU attach function received invalid call type [dec]
Explanation An internal POS LC ISSU 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.POSLC Messages
The following are POS Line Card messages.
Error Message%POSLC-3-CORRUPT : [chars]
Explanation A NULL SERIAL or SONET subblock was retrieved while trying to fetch SERIAL or SONET subblock.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.PQ3_FE Messages
The following are PQ3 FEC messages.
Error Message%PQ3_FE-4-BABBLE : PQ3/FE([dec]/[dec]), Babble error, CSR[dec]=[hex]
Explanation The transmitter has been on the channel longer than the time taken to transmit the largest
frame.Recommended Action The system should recover. No action is required.
Error Message%PQ3_FE-5-EXECOLL : PQ3/FE([dec]/[dec]), Excessive collision
Explanation Excessive collisions occurred on the Fast Ethernet interface.
Recommended Action No action is required.
Error Message%PQ3_FE-1-INITFAILP : PQ3/FE([dec]/[dec]), Init failed at [chars]
Explanation The FE could not allocate a I/O buffer pool.
Recommended Action Clear the interface. 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%PQ3_FE-5-LATECOLL : PQ3/FE([dec]/[dec]), Late collision
Explanation Late collisions occurred on the Fast Ethernet interface.
Recommended Action If the interface is Fast Ethernet, verify that both peers are in the same duplex mode. Otherwise, no action is required.
Error Message%PQ3_FE-5-LOSTCARR : PQ3/FE([dec]/[dec]), Lost carrier. Transceiver problem?
Explanation The cable and/or transceiver is not connected.
Recommended Action Connect the cable and/or transceiver.
Error Message%PQ3_FE-1-MACADDRFAIL : PQ3/FE([dec]/[dec]), Unable to set the Mac-address for the interface
Explanation The FEC could not set the mac address of the interface.
Recommended Action Clear the interface. 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%PQ3_FE-2-NOISL : Interface [chars] does not support ISL
Explanation The interface cannot be configured as an ISL trunk.
Recommended Action Check the configuration.
Error Message%PQ3_FE-3-OVERFLO : PQ3/FE([dec]/[dec]), Receive overflow
Explanation While receiving a frame, the controller chip's local buffer transmitted insufficient data because data could not be transferred to DRAM fast enough to keep pace with its input rate. Normally, such a problem is temporary, depending on transient peak loads within the system.
Recommended Action The system should recover. No action is required.
Error Message%PQ3_FE-1-SHOWFAIL : PQ3/FE([dec]/[dec]), Memory error at [chars]
Explanation The FEC could not allocate memory to display controller.
Recommended Action Clear the interface. 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%PQ3_FE-3-UNDERFLO : PQ3/FE([dec]/[dec]), Transmit underflow
Explanation While transmitting a frame, the controller chip's local buffer received insufficient data because data could not be transferred to the chip fast enough to keep pace with its output rate. Normally, such a problem is temporary, depending on transient peak loads within the system.
Recommended Action The system should recover. No action is required.
PQ3_TSEC Messages
The following are PQ3 TSEC messages.
Error Message%PQ3_TSEC-4-BABBLE : PQ3/FE([dec]), Babble error, CSR[dec]=[hex]
Explanation The transmitter has been on the channel longer than the time taken to transmit the largest
frame.Recommended Action The system should recover. No action is required.
Error Message%PQ3_TSEC-5-COLL : PQ3/FE([dec]), Excessive collisions, TDR=[dec], TRC=[dec].
Explanation Ethernet/Fast Ethernet is seeing multiple collisions. This might occur under heavy loads.
Recommended Action The system should recover. No action is required.
Error Message%PQ3_TSEC-5-EXCESSCOLL : PQ3/FE([dec]), Excessive collision
Explanation Ethernet/Fast Ethernet is seeing multiple collisions. This might occur under heavy loads.
Recommended Action The system should recover. No action is required.
Error Message%PQ3_TSEC-1-INITFAIL : PQ3/FE([dec]), Init failed, CSR[dec]=[hex]
Explanation The software failed to initialize or restart an Ethernet/Fast Ethernet interface.
Recommended Action Clear the interface. 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%PQ3_TSEC-1-INITFAILP : PQ3/FE([dec]), Init failed at [chars]
Explanation The FEC could not allocate an I/O buffer pool.
Recommended Action Clear the interface. 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%PQ3_TSEC-5-LATECOLL : PQ3/FE([dec]), Late collision
Explanation Late collisions occurred on the Ethernet/Fast Ethernet interface.
Recommended Action If the interface is Fast Ethernet, verify that both peers are in the same duplex mode. For regular Ethernet, the system should recover. No action is required.
Error Message%PQ3_TSEC-5-LOSTCARR : PQ3/FE([dec]), Lost carrier. Transceiver problem?
Explanation The cable is not connected to the port.
Recommended Action Connect the cable to the port.
Error Message%PQ3_TSEC-1-MEMERR : PQ3/FE([dec]), Memory error, CSR[dec]=[hex]
Explanation The interface could not access system resources for a long time. This problem might occur under very heavy loads.
Recommended Action The system should recover. No action is required. 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%PQ3_TSEC-2-NOISL : Interface [chars] does not support ISL
Explanation The interface cannot be configured as an ISL trunk.
Recommended Action Check the configuration.
Error Message%PQ3_TSEC-3-OVERFLO : PQ3/FE([dec]), Receive overflow
Explanation While receiving a frame, the controller chip's local buffer transmitted insufficient data because data could not be transferred to DRAM fast enough to keep pace with its input rate. Normally, such a problem is temporary, depending on transient peak loads within the system.
Recommended Action The system should recover. No action is required.
Error Message%PQ3_TSEC-3-OWNERR : PQ3/FE([dec]), Buffer ownership error, pak=[hex]
Explanation The software detected an error in descriptor ownership.
Recommended Action Try a later version of the software. 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%PQ3_TSEC-1-SHOWFAIL : PQ3/FE([dec]), Memory error at [chars]
Explanation The FEC could not allocate memory to display controller.
Recommended Action Clear the interface. 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%PQ3_TSEC-3-UNDERFLO : PQ3/FE([dec]), Transmit underflow
Explanation While transmitting a frame, the controller chip's local buffer received insufficient data because data could not be transferred to the chip fast enough to keep pace with its output rate. Normally, such a problem is temporary, depending on transient peak loads within the system.
Recommended Action The system should recover. No action is required.
PQUICC3 Messages
The following are MPC860 Quad Integrated Communications Controller messages.
Error Message%PQUICC3-1-BADHDXFSM : PQUICC3([dec]/[dec]), Unexpected HDX state [dec], event [dec]
Explanation A bad event was detected in the state machine for half-duplex transmission/reception.
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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%PQUICC3-1-CTSLOST : PQUICC3([dec]/[dec]), Clear to Send Lost
Explanation The Clear To Send (CTS) input signal on a data terminal equipment (DTE) serial interface became inactive while transmitting a frame. This problem is a result of a communication line failure or cable disconnection.
Recommended Action Check the serial interface cable and/or communication equipment, such as the channel service unit or data service unit (CSU/DSU).
Error Message%PQUICC3-1-INITFAIL : PQUICC3([dec]/[dec]), SCC[dec] init failed
Explanation The software failed to initialize or restart a 1T serial card.
Recommended Action Clear the serial interface. 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%PQUICC3-1-LINEFLAP : PQUICC3([dec]/[dec]), Excessive modem control changes
Explanation The system received too many modem control signal interrupts. Modem control signals are hardware handshake signals between data terminal equipment (DTE) and data communications equipment (DCE). The signals include either a data carrier detect (DCD) or a data set ready (DSR),
or both DCD and DSR.Recommended Action Check the serial interface cable. The error can occur if the cable is disconnected or has come loose and is picking up noise. If the cable appears to be connected correctly, check the equipment connected to the cable.
Error Message%PQUICC3-1-LOSTCARR : Unit [dec], lost carrier. Transceiver problem?
Explanation The Ethernet 10BASE-T cable is unplugged.
Recommended Action Reconnect the Ethernet 10BASE-T cable.
Error Message%PQUICC3-1-NOMEMORY : Unit [dec], no memory for [chars]
Explanation The MPC8500/PowerQUICC CPU was unable to access the memory it needs to carry out its functions. Here are some possible causes. The network is large, requiring a lot of memory for routing tables. The router configuration has many features enabled, each of which require a certain amount of memory. A software error (memory leak) exists.
Recommended Action Reduce system activity to ease the memory demand, or upgrade to a larger memory configuration.
Error Message%PQUICC3-3-OWNERR : Unit [dec], buffer ownership error, pak = [hex]
Explanation An internal software error occurred.
Recommended Action Call your technical support representative to obtain a software upgrade.
Error Message%PQUICC3-1-QMC_GLOBAL_ERROR : PQUICC3([dec]/[dec]), Global error [hex] in QMC
Explanation One or more of the channels served by the QMC instance encountered transmitter underflow or receiver overflow or the QMC interrupt table overflowed. Normally, such a problem is temporary, depending on transient peak loads within the system.
Recommended Action The system should recover. No action is required.
Error Message%PQUICC3-3-SPURIOUS_INTERRUPT : Interface card in slot [dec] generated a spurious interrupt
Explanation Interface card on the router which is not supported by this image generated a spurious interrupt that cannot be handled.
Recommended Action No action is required. To avoid seeing this message in the future, remove the unsupported card or use an image that supports it.
Error Message%PQUICC3-1-TOOBIG : PQUICC3([dec]/[dec]), packet too big, packet size was [dec] bytes
Explanation A packet greater than the assigned MTU of this serial interface was queued up for transmission.
Recommended Action The system should recover. No action is required. If this message recurs, it might indicate an error related to data traffic patterns. 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%PQUICC3-1-TOOSMALL : PQUICC3([dec]/[dec]), packet was less than 2 bytes,
packet size was [dec] bytesExplanation A small packet (less than two bytes) was queued up for transmission. The interface cannot handle such small packets for transmission.
Recommended Action The system should recover. No action is required. If this message recurs, it might indicate a hardware error related to data traffic patterns. 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%PQUICC3-1-UNDERFLO : PQUICC3([dec]/[dec]), Transmit underflow
Explanation While transmitting a frame, the serial controller chip's local buffer received insufficient data because data could not be transferred to the chip fast enough to keep pace with its output rate. Normally, such a problem is temporary, depending on transient peak loads within the system.
Recommended Action The system should recover. No action is required.
Error Message%PQUICC3-1-UNEXPECTED_INTERRUPT : PQUICC3([dec]), Unexpected modem-signal interrupt
Explanation The software did not expect to see a modem control signal change on this interface.
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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%PQUICC3-3-UNKNOWN_SCCS : PQUICC3, Incorrect SCC number
Explanation An internal software error occurred.
Recommended Action Call your technical support representative to obtain a software upgrade.
Error Message%PQUICC3-3-UNKNOWN_SCC_TX_VECTOR : PQUICC3, Unknown TX vector on port [dec]
Explanation An internal software error 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%PQUICC3-1-UNKNOWN_WIC : PQUICC3([dec]), WIC card has an unknown ID of [hex]
Explanation The software does not recognize the type of WIC card plugged into the port module.
Recommended Action Check the part number on the WIC card to verify that it is supported in the IOS release operational on the router, or contact your technical support representative.
Error Message%PQUICC3-1-UNSUPPORTED_CONFIG : Slot [dec] has an unsupported combination of ISDN WAN interface cards
Explanation It is not possible to support this type of BRI card in slot 1 along with another BRI card in slot 0.
Recommended Action Remove one of the BRI cards from either slot.
Error Message%PQUICC3-1-WRONG_SLOT : PQUICC3([dec]), BRI card in wrong slot(1)
Explanation The BRI card is not supported in WIC slot 0.
Recommended Action Power down, move the BRI card to the other WIC slot on the port module and reboot.
PREDNLD Messages
The following are Minimum Disruption Restart State Machine messages.
Error Message%PREDNLD-3-INIT_FAIL : Initialisation error '[chars]'
Explanation During Pre-download initialization, an error has occurred. Most likely pre-download will not be able to be performed and the associated line card(s) will be reset up on switchover.
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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.PRST_IFS Messages
The following are Persistent Media IFS messages.
Error Message%PRST_IFS-3-char : persistent media IFS file error: [chars]
Explanation Persistent media module (file system) file 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%PRST_IFS-3-GENERAL : persistent media IFS general error: [chars]
Explanation Persistent media module (file system) general 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.PT Messages
The following are PT messages.
Error Message%PT-3-PT_NO_SWSB : Protocol Tunneling software subblock not found. [chars]
Explanation The software subblock that is used for protocol tunnelling could not be found for the port specified in the message text. Protocol tunnelling has been disabled on this port.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.PXF Messages
The following are Parallel eXpress Forwarding (PXF) messages.
Error Message%PXF-5-RESTARTEDALL : All PXFs have been restarted.
Explanation All PXF coprocessors have been restarted, either manually via a microcode reload, or as a result of an exception.
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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.PXF_ACL Messages
The following are Parallel eXpress Forwarding (PXF) ACL-specific messages.
Error Message%PXF_ACL-3-WS_ACL_ALLOC_FAIL : Failed to allocate a PXF data structure for access-list '[chars]', ACL will not function correctly. Only [int] ACLs are supported.
Explanation The system failed to allocate a PXF data structure for the specified ACL. The ACL will not be processed properly in PXF.
Recommended Action If you have configured more ACLs than are supported, remove one or more ACLs from your configuration, reload the system, and then attempt to configure the new ACL again. To determine if you have configured too many ACLs, enter the test platform acl command and under the 'name = SH_TT_ACL' line, ensure that the value shown for 'alloc_failed' is 0.
Error Message%PXF_ACL-3-WS_ACL_ALLOC_FIRST_ROW : Failed to allocate first table row in PXF memory for node [int] ([chars], block type [int], row size [int])
Explanation The system failed to allocate the first row in a Turbo ACL table in PXF memory. ACL processing in PXF will be disabled.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the test platform acl command to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message%PXF_ACL-3-WS_ACL_BLOCK_ARRAY_ERROR : Failed to add [chars] to node [int] due to an unallocated row pointer table in node [int]
Explanation While adding a table entry or row to the specified node, it was found that the row pointer table in the specified row was not allocated. This might be due to a previous memory allocation failure or due to an internal error. All traffic requiring ACL classification that does not already have matching table entries in PXF will be punted.
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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message%PXF_ACL-3-WS_ACL_CHUNK_RESIZE : Failed to resize PXF memory chunk for node [int] ([chars], block type [int]) to row size [int]
Explanation The system failed to change the block size of the PXF memory chunk for the specified Turbo ACL node. This might be due to an out-of-memory condition. ACL processing in PXF will be disabled.
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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message%PXF_ACL-2-WS_ACL_CONSISTENCY_ERROR : An internal consistency check has failed and ACL processing will be affected: [chars]
Explanation An internal consistency check has failed. Security ACL, QoS, NAT, and RPF ACL functionality in PXF are likely to be affected.
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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message%PXF_ACL-3-WS_ACL_CONSISTENCY_WARN : An internal consistency check has failed: [chars]
Explanation An internal consistency check has failed. Unless otherwise indicated by another message, forwarding will continue normally.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the test platform acl command to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%PXF_ACL-2-WS_ACL_DISABLED : Turbo ACL processing in PXF has been disabled due to an error
Explanation Due to an error in installing new Turbo ACL tables after ACL compilation completed, Turbo ACL processing in PXF cannot continue and has been disabled. All traffic requiring ACL classification will be punted to the RP.
Recommended Action Look for messages preceding this one that will indicate the cause of the failure and what action you should take.
Error Message%PXF_ACL-3-WS_ACL_NO_ACLS : An internal error occurred while processing a new ACL outcome
Explanation The system failed to process a new ACL outcome because no ACLs appear to be configured. If you have any ACLs configured, they will not be processed properly in PXF.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show access-lists compiled command to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message%PXF_ACL-3-WS_ACL_NODE_TOO_LARGE : Turbo ACL node [int]'s table size of [int] entries is too large for PXF
Explanation The size of the Turbo ACL table for the specified node is larger than the amount of PXF memory set aside for that node. ACL processing in PXF will be disabled.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show access-lists compiled command to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message%PXF_ACL-3-WS_ACL_RESULT_TOO_MANY_ACLS : Turbo ACL Security ACL result table initialization failed: [int] ACLs, [int] fixed outcomes, [int] bytes PXF memory allocated
Explanation The system failed to initialize the Turbo ACL Security ACL result table in PXF because the number of ACLs configured allows too few outcomes to fit in the table. ACL processing in PXF will be disabled.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the test platform acl command to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message%PXF_ACL-3-WS_ACL_TABLE_UPDATE_ERROR_ADDR_RANGE : Failed to add an entry to node [int] due to an internal error: address [hex] is not in range [hex] to [hex]
Explanation While adding an entry to the specified Turbo ACL node's table in PXF, an internal consistency error was found. This might be due to a previous memory allocation failure or due to an internal error. One or more traffic flows requiring ACL classification will be punted.
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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message%PXF_ACL-3-WS_ACL_TABLE_UPDATE_ERROR_LT : Failed to add [chars] to node [int] due to an internal error: [chars] [int] is not less than [chars] [int]
Explanation While adding an entry or row to the specified Turbo ACL node's table in PXF, an internal consistency error was found. This might be due to a previous memory allocation failure or due to an internal error. One or more traffic flows requiring ACL classification will be punted.
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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message%PXF_ACL-2-WS_ACL_TOO_MANY_ACES : More than [int] ACEs are present. Failed to allocate [chars]. New ACEs will be treated as 'deny's and counters will not be maintained properly.
Explanation More ACEs are present than are supported by the platform. For any ACE configured above this limit, the action will be treated as deny and counters will not be maintained properly. The number of ACEs supported is shown in the message. ACEs that were previously configured but have been unconfigured without a reload might count against this limit, as will internal ACEs created by the router when the QoS class-map command is configured.
Recommended Action Reload the router and reduce the number of configured ACEs. When the limit has been reached, any ACEs that are subsequently configured will be treated as having a deny action. This condition cannot be resolved without reloading the system. You can determine how many ACEs are currently configured by entering the test c7300 acl command if you are using a Cisco IOS Release earlier than 12.2(25)S or the test platform acl command in later releases. In the output of the command, look for the line with the text name = ACL_REAL_ACE. The number that is shown below this line, next to alloced, indicates the number of ACEs that are currently configured. The number next to max indicates the maximum number of ACEs that can be configured.
PXFAPI Messages
The following are Parallel eXpress Forwarding (PXF) API-related messages.
Error Message%PXFAPI-2-CHUNK_ALLOC_INTERNAL_ERROR : Failed to allocate a block from chunk [chars] (type [int]) due to an internal error (block index [int], bit index [int], entry index [int], entry [hex], full mask [hex], allocated mask [hex])
Explanation An attempt was made to allocate memory from the indicated chunk. The memory could not be allocated due to an internal consistency error in the memory management software. This error was most likely caused by an internal software error and might have resulted in memory corruption.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show platform memory chunk statistics command to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message%PXFAPI-2-CHUNK_FREEFREE : Attempted to free unallocated block at [hex_addr] (index [int]) in chunk [chars] (type [int]) (bit index [int], entry index [int], entry [hex], mask [hex])
Explanation An attempt was made to free memory at the indicated location. The memory could not be freed because it was not allocated. This error was most likely caused by an internal software error and might have resulted in memory corruption.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show platform memory chunk statistics command to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message%PXFAPI-3-IFNUMZERO : Interface (Slot [dec], Slotunit [dec], Subunit [dec]) number unavailable.
Explanation The PXF interface table was accessed without first obtaining the index for the given interface.
Recommended Action This error can affect the forwarding in the PXF switching path when MPLS is enabled on the interfaces belonging to the slot indicated in the message. A graceful restart of the corresponding line card can correct this error. Graceful restart can be performed by entering the hw-module slot slot-number stop command followed by the hw-module slot slot-number start command. If you have received this message, check Bug Toolkit on the Cisco web site to search for existing bugs. If you do not find a match, collect the output from show platform, show pxf interfaces all, copy the running configuration and the system messages 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.PXF_CLIENT_VTMS Messages
The following are PXF Client for VTMS messages.
Error Message%PXF_CLIENT_VTMS-4-PXF_TO_RP_BLOCKED : The PXF to RP path would have frozen for [int] seconds; corrected.
Explanation An internal error was detected which would have resulted in no traffic being passed from PXF to RP for some seconds. The error has been corrected, but there might have been a brief delay.
Recommended Action No action is required, but this is recommended: 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%PXF_CLIENT_VTMS-4-PXF_TO_RP_Q_BLOCKED : A PXF to RP queue would have frozen for [int] milliseconds; corrected.
Explanation An internal error was detected which would have resulted in no traffic being passed on one of the queues from PXF to RP for some seconds.The error has been corrected.
Recommended Action No action is required, but this is recommended: 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.PXF_GEC Messages
The following are PXF EtherChannel messages.
Error Message%PXF_GEC-3-PXF_MEM_ERR_HASH : PXF MEM ERROR when downloading FE/GEChannel hash info to PXF (Addr=[hex])
Explanation An error occurred when writing to PXF memory. EtherChannel hash information could not be properly downloaded to PXF.
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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message%PXF_GEC-3-PXF_MEM_ERR_MAP : PXF MEM ERROR when downloading Map table to PXF (Addr=[hex])
Explanation An error occurred when writing to PXF memory. EtherChannel map table could not be properly downloaded to PXF.
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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.PXF_NAT Messages
The following are Parallel eXpress Forwarding (PXF) Network Address Translation (NAT)-related messages.
Error Message%PXF_NAT-3-QUEUE_PROCESSING : PXF NAT: Dynamic NAT reply address Queue has an incomplete entry. Action Code: [dec]
Explanation A queue entry from the dynamic NAT reply address queue did not contain the NAT session information. Connections to the global address with new port values with a non-overload configuration might fail.
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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.PXF_NICKEL Messages
The following are NICKEL messages.
Error Message%PXF_NICKEL-3-FTS_ERROR : FTS [chars] Error: [dec] in nicket[dec]/port[dec]
Explanation Ingress Nickel-->Cobalt3 ASIC communication error.
Recommended Action Monitor system to determine if this message is persistent.If this error is presistent (for example, it appears more than once or twice in a day), then there might be a hardware issue. 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%PXF_NICKEL-3-STT_ERROR : STT [chars] [chars] Error: [dec] in nickel[dec]
Explanation Egress Cobalt3-->Nickel ASIC communication error .
Recommended Action Monitor system to determine if this error does not appear together with a PXF restart. If this error is presistent (for example, it appears more than once or twice in a day and it does not appear together with a PXF restart), then there might be a hardware issue. 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%PXF_NICKEL-3-STT_PORT_ERROR : STT [chars] Error: [dec] in nickel[dec]/port[dec]
Explanation Egress Cobalt3-->Nickel ASIC communication error.
Recommended Action Monitor system to determine if this error does not appear together with a PXF restart. If this error is presistent (for example, it appears more than once or twice in a day and it does not appear together with a PXF restart), then there might be a hardware issue. 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%PXF_NICKEL-3-TBB_ERROR : TBB [chars] Error: [dec] in slot [dec]/subslot[dec]
Explanation Egress Cobalt3-->Nickel ASIC communication error.
Recommended Action Monitor system to determine if this message is persistent.If this error is presistent (for example it appears more than once or twice in a day), then there might be a hardware issue. 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.PXF_QOS Messages
The following are Parallel eXpress Forwarding (PXF) Quality of Service (QoS)-related messages.
Error Message%PXF_QOS-3-PXF_QOS_L2_MEMORY_EXCEEDED : Maximum possible outcomes exceeded for L2 classification tables. Only [int] bytes free.
Explanation QoS PXF L2 Classification Engine (based on turbo acl): Memory limit has been exceeded.
Recommended Action Modifying the L2 ACLs to trigger re-compilation might free some memory.
Error Message%PXF_QOS-3-QOS_RP_GEN_XOFF : XOFF with tif number 0 is generated
Explanation PXF received an unexpected XOFF from RP; it was overridden.
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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.PXF_VRFS Messages
The following are Parallel eXpress Forwarding (PXF) VRF selection-specific messages.
Error Message%PXF_VRFS-3-CHUNKFREE : Node resource could not be freed
Explanation The router tried to free a node resource for an IP address range but failed to do so. The router might still continue to function correctly; however, if this message recurs often, the router might run out of memory and reload.
Recommended Action This is a software 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message%PXF_VRFS-3-NOADD : IP address range [IP_address]/[IP_address] not added to the VRF selection table: [chars]
Explanation When the router processed a configuration command to add an IP address range to a VRF selection table, the router could not complete the command. The message shows the reason.
Recommended Action Reasons for this to happen could be software errors and resource problems. Should the message indicate that memory allocation failed, then try reducing the number of IP addresses or address ranges or try making them less specific. If this does not solve the problem, you might need to install more memory in the router.
Error Message%PXF_VRFS-6-NOHWNODE : No PXF node resource available to add IP address range
Explanation When adding an IP address range to a VRF selection table, PXF could not allocate a node structure for the IP address range shown in the message. The reason for this is that too many addresses have been added already and PXF has run out of resources for VRF-Select to maintain a larger number of addresses.
Recommended Action Try reducing the number of IP addresses or address ranges or try making them less specific. If this does not solve the problem then you might need to turn PXF off or use a non-PXF routing engine.
Error Message%PXF_VRFS-6-NONODE : No node resource available for [IP_address]/[IP_address]
Explanation When adding an IP address range to a VRF selection table the router could not allocate a node structure for the IP address range shown in the message. The reason for this is that too many addresses have been added already and the router has run out of resources for VRF-Select to maintain a larger number of addresses.
Recommended Action Try reducing the number of IP addresses or address ranges or try making them less specific. If this does not solve the problem, you might need to install more memory in the router.
Error Message%PXF_VRFS-3-NOTABLE : Initialization for PXF VFR-Select failed: [chars]
Explanation The router failed to initialize the internal database to keep the VRF selection table. The reason is shown in the message.
Recommended Action The reason for this can be a software problem or router memory exhaustion. Verify that the router has enough memory by entering the show memory summary command. If the router does have enough memory, 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message%PXF_VRFS-3-NOTFOUND : Node for IP address range [IP_address]/[IP_address] was not found
Explanation When the router processed a configuration command to remove an IP address range from a VRF selection table, the router could not find the entry in its internal database.
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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.QBM Messages
The following are QBM messages.
Error Message%QBM-3-QBM_CONSISTENCY : QBM internal error: [chars]
Explanation An action attempted by the QoS Bandwidth Manager implementation encountered an unexpected software condition.
Recommended Action Search the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl for existing bugs and upgrade the software if necessary. If this message recurs, copy the message exactly as it appears on the console or in the system log. Enter the show qbm client, show qbm pool, show running, and show version commands to gather data which might help identify the nature of the message. 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. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.QM Messages
The following are QoS Manager (QM) messages.
Error Message%QM-2-ACL_FAILURE : Interface [chars] traffic will not comply with ACLs in [chars] direction(s)
Explanation ACLs will not be applied to traffic for this interface due to TCAM resource contention.
Recommended Action The configured ACLs are too large to all fit in the hardware TCAM. Try and share the same ACLs across multiple interfaces in order to reduce TCAM resource contention.
Error Message%QM-2-ACL_MERGE_NO_MEM : Memory low: ACL merge failed for interface [chars] in [chars] direction
Explanation Inadequate system memory while trying to merge ACLs.
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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%QM-4-AGG_POL_EXCEEDED : QoS Hardware Resources Exceeded : Out of Aggregate policers
Explanation Only a limited number of aggregate policers can be supported. On Earl7 based switches, this limit is 1023.
Recommended Action Try to aggregate policers if possible.