Table Of Contents
PLATFORM_CATALYST2940 Messages
PLATFORM_CATALYST2950 Messages
PLATFORM_CATALYST2955 Messages
PLATFORM Messages
The following are platform-specific messages.
Error Message%PLATFORM-0-ARP : ARP error: [chars]
Explanation An unexpected error occurred while performing ARP operation .
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://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%PLATFORM-3-CLK_SET_FAILED : Failed to set clock received from proc0
Explanation System clock is not updated with the proc0 clock during bootup.
Recommended Action Set the clock manually, or configure ntp.
Error Message%PLATFORM-3-CLK_SYNC_FAILED : Failed to receive clock update from proc0
Explanation System clock is not updated with the proc0 clock during bootup.
Recommended Action Set the clock manually, or configure ntp.
Error Message%PLATFORM-1-CRASHED : [chars]
Explanation The system is attempting to display the crash message from the previous crash.
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%PLATFORM-1-DP_HM_FAIL : Failed to receive response from [chars]. Check `sami health-monitoring' configuration and see `show sami health-monitoring' for more info
Explanation Data path monitoring has missed configured number of responses and indicating failure. This can be caused if there is an issue in the hardware path between backplane and NP (IXP) or a software issue or a configuration issue. Check the probe configuration on the sami processor and also on the supervisor. Try sending ping messages from line card processor to validate connectivity to the supervisor probe.
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://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%PLATFORM-4-DP_HM_WARN : Failed to receive response from [chars] in [int] retries, system will reboot if it continues to fail receiving response in another [int] retries (i.e. in the next [int] secs.) Check `sami health-monitoring' configuration and see `show sami health-monitoring' for more info
Explanation This is a warning message indicating the possibility of system reload in future due to the chances of data path monitoring missing configured number of responses. This can be caused if there is an issue in the hardware path between backplane and NP (IXP) or a software issue or a configuration issue. Check the probe configuration on the sami processor and also on the supervisor. Try sending ping messages from line card processor to validate connectivity to the supervisor probe.
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://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%PLATFORM-4-FPGA_MISMATCH : FPGA image in slot [dec] (name = [chars], hardware version = [dec].[dec], current fpga version = [chars]) does not match the FPGA image in Cisco IOS software (version [dec].[dec]). Approximate time to update the FPGA image is [dec] minutes.
Explanation The version of the FPGA image on the specified card differs from the Cisco IOS software bundled FPGA image version.
Recommended Action Update the FPGA image by entering the upgrade fpga all command.
Error Message%PLATFORM-4-FPGAUPD_RELOAD_SKIP : After the FPGA update, the card in slot [dec] was not reloaded. The card should be reloaded for the new FPGA image to take effect.
Explanation The FPGA image on the specified card is updated. The new FPGA image will not be operational until the card is reloaded. The FPGA image upgrade will take effect after the next reload of the card. The card was not reloaded due to negative user response to the reload prompt.
Recommended Action Reload the card in the specified slot. If the card is a processor, reload the router.
Error Message%PLATFORM-4-FPGA_VER_INVALID : FPGA version information for the hardware in slot [dec] (fpga [dec]) has not been cached.
Explanation An attempt to read the current FPGA version from the cache was unsuccessful. Normally, the FPGA version on the RP and line cards is read from the flash memory device and is cached during the initialization of the card. However, the FPGA image version information for the card in the specified slot has not been cached. This problem is caused by a software 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. 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%PLATFORM-1-HMPROBE_IPFAIL : [chars] while sending probe to [IP_address]. Effectively, probe monitoring will be ignored. Please make necessary modifications to sami health-monitoring probe CLI
Explanation The CLI sami health-monitoring probe will not be effective because either there is no suitable local source ip that can be used to send ping packets to the configured address, or the peer address is not responding, or there is some other data path issue.
Recommended Action Correct configuration such that pings can be sent and responses received by using ping ip. If you do not need the probe monitoring, you can unconfigure it using the CLI no sami health-monitoring probe. If pings are working fine without giving any explicit source ip address but this message is still seen, then cCopy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%PLATFORM-4-HWTIMERALLOCFAIL : Failed to allocate hardware timer for [chars]
Explanation The system software was unable to allocate a hardware timer from the system hardware timer pool. The feature indicated in the message will be non-functional due to this 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. 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%PLATFORM-4-IOMEM_MISMATCH : I/O memory size mismatch. Configured size is [dec], allocated size is [dec]
Explanation The allocated I/O memory size does not agree with the configured size. It will not affect the functionality of the system.
Recommended Action Informational message only. No action is required.
Error Message%PLATFORM-3-NO_HARDWARE_RESOURCES : Not enough hardware resources. Shutting down [chars]
Explanation Too many VLANs and routed ports.
Recommended Action Reduce the total number of VLANs and routed ports to be less than 1023 . If this configuration and connectivity needs to be maintained across reboots, save the configuration to NVRAM.
Error Message%PLATFORM-6-NONESSINITFAIL : Initialization failed for [chars]
Explanation The router tried to initialize the indicated component of the software; however this failed. The component that was to be initialized is non-essential and therefore the router can continue.
Recommended Action No action is required. The router will function normally. 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%PLATFORM-3-PW_REC_HRPC_BAD_LENGTH : Received incompatible length (=[dec]) in set-password-recovery HRPC message from box [dec].
Explanation The system has received an incompatible length parameter in the set-password-recovery HRPC message. This condition could be caused by a stack operating with incompatible software versions on different stack members.
Recommended Action Ensure that all stack members are running compatible software images. If this message recurs, copy the message exactly as it appears on the console or in the system log. Copy the message exactly as it appears on the console or in the system log.Research and attempt to resolve the 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%PLATFORM-3-PW_REC_HRPC_NOT_ON_MASTER : Set-password-recovery HRPC msg from box [dec] received on master.
Explanation The stack master has received a set-password-recovery HRPC message. These messages should be received only on slave devices.
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%PLATFORM-3-PW_REC_HRPC_ONLY_ON_MASTER : Get-password-recovery HRPC msg from box [dec] received on slave.
Explanation A slave switch has received a get-password-recovery HRPC message. These messages should be received by only the stack master.
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%PLATFORM-3-SAMI_HM_FAIL : [chars]
Explanation Platform 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://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%PLATFORM-4-SAMI_HM_UNKNOWN : Unknown/Unexpected message rcvd with opcode = [int], received from [chars]
Explanation Unknown/unexpected message 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://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%PLATFORM-0-SAMI_INVALID_SLOT_ID : Invalid slot id [dec] in ROMMON cookie at [hex]
Explanation Unable to determine the slot number of the 7600/6500 chassis containing this SAMI card. Since the card cannot continue to operate without this information, it was reloaded.
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://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%PLATFORM-3-SAMI_IPC_FAIL : [chars]
Explanation Platform 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://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%PLATFORM-3-SAMI_IPC_IXP_FAIL : [chars]
Explanation Error in PowerPC - IXP Communication. Further configuration may not be effective.
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://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%PLATFORM-4-SAMI_PKT : [chars]: [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]
Explanation Unknown/unexpected 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://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%PLATFORM-3-SAMI_SVC_FAIL : [chars]
Explanation Platform 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://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%PLATFORM-3-UNEXPECTED : [chars]
Explanation Platform 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://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.PLATFORM_CAPABILITY Messages
The following are platform capability subsystem messages.
Error Message%PLATFORM_CAPABILITY-4-CALL : Fatal Initialization Error - [chars]
Explanation An internal software 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. 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%PLATFORM_CAPABILITY-4-INIT : Fatal Initialization Error - [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. 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.PLATFORM_CAT2950 Messages
The following are Cisco Catalyst 2950 ASIC driver messages.
Error Message%PLATFORM_CAT2950-3-REG_READ_FAILURE : Register read failed for register [chars] in [chars]
Explanation An attempt to read a valid location in the internal chip register failed. This could be due to a hardware defect.
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. 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%PLATFORM_CAT2950-3-REG_WRITE_FAILURE : Register write failed for register [chars] in [chars]
Explanation An attempt to write to a location in the internal chip register failed. This might be caused by writing to a invalid register location, or a defect in the hardware.
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. 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.PLATFORM_CATALYST2940 Messages
The following are Calhoun uplink messages.
Error Message%PLATFORM_CATALYST2940-3-C2940_UPLINK_SELECT : [chars] is selected as uplink port
Explanation A single uplink is selected at startup. Other uplink ports remain shutdown.
Recommended Action No action is required.
PLATFORM_CATALYST2950 Messages
The following are low-level platform messages.
Error Message%PLATFORM_CATALYST2950-1-CRASHED : [chars]
Explanation The system is attempting to display the crash message from the previous crash.
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.PLATFORM_CATALYST2955 Messages
The following are Calhoun uplink messages.
Error Message%PLATFORM_CATALYST2955-3-PORT_NOT_OPERATING : [chars] [chars] [chars] [chars]
Explanation The port is not operating, the startup selftest has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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.PLATFORM_FBM Messages
The following are platform-specific Fallback Bridging messages.
Error Message%PLATFORM_FBM-4-RECOVERED : Fallback bridging recovered from resource crunch.
Explanation Fallback bridging has recovered from earlier resource crunch.
Recommended Action No action is required.
Error Message%PLATFORM_FBM-4-RESOURCE_CRUNCH : Fallback bridging on bridge-group [dec] is experiencing a resource crunch. One or more bridge-groups might not be functional. It will recover automatically when system recovers from resource crunch. Delete the bridge-group to immediately recover.
Explanation Fallback bridging could not be configured properly. Most likely cause is TCAM full condition on at least one stack member.
Recommended Action Stop all traffic, enter the clear mac-address-table dynamic command, and restore the switch to normal operation.
PLATFORM_IPC Messages
The following are platform IPC messages.
Error Message%PLATFORM_IPC-3-COMMON : [chars]
Explanation IPC failure.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%PLATFORM_IPC-3-MASTER : [chars]
Explanation A failure on the master.
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%PLATFORM_IPC-3-SLAVE : [chars]
Explanation A failure on the slave.
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%PLATFORM_IPC-3-STACK_EVENT : [chars]
Explanation IPC failure.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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.PLATFORM_N2 Messages
The following are SAMI Platform crypto messages.
Error Message%PLATFORM_N2-3-INIT_FAIL : [chars]
Explanation Platform 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://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%PLATFORM_N2-3-NOMEMORY : Could not allocate memory for [chars] [int]
Explanation Unknown or unexpected message 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://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.PLATFORM_PBR Messages
The following are policy-based routing messages.
Error Message%PLATFORM_PBR-4-CPU_SUPPORTED_ACTION : Set action in sequence [dec] of route-map [chars] supported by forwarding to CPU
Explanation The route-map attached to an interface for policy routing contains an action that is not supported in hardware since it contains a 'set interface', 'set ip default next-hop', 'set default interface' or or 'set ip df' actions. This requires the packets to be forwarded by the CPU.
Recommended Action Reconfigure the route-map. Use only set ip next-hop in the route-map, if possible.
Error Message%PLATFORM_PBR-3-INSTALL_FAIL : Policy route-map [chars] not installed in hardware
Explanation The PBR manager was unable to install the complete route-map in the hardware, so this will have to be applied in software. This requires the packets to be forwarded by the CPU.
Recommended Action Reconfigure the route-map to use a simpler configuration. Use the same route-map on multiple interfaces, if possible.
Error Message%PLATFORM_PBR-3-MERGE_FAIL : [chars] ACL merge error [dec] on route-map [chars]
Explanation The PBR manager could not complete the merge of the configured route-map into a form suitable for loading into the hardware. The most likely cause is specifying an ACL that is too large or too complex for the system to handle.
Recommended Action Try specifying a smaller and less complicated configuration.
Error Message%PLATFORM_PBR-3-NO_LABEL : Cannot allocate label for route-map [chars]
Explanation The PBR manager could not allocate a label for this route-map. This means that the hardware cannot be programmed to implement policy routing. There is a limit of 247 labels for policy routing.
Recommended Action Use a less complicated configuration that allows label sharing. Use the same route-maps on multiple interfaces, if possible.
Error Message%PLATFORM_PBR-2-NO_RMAP : Cannot create PBR data structures for route-map [chars]
Explanation The PBR manager could not allocate the data structures needed to describe a route-map being used for policy routing. Probably caused by lack of available memory.
Recommended Action Use a less complicated configuration that requires less memory.
Error Message%PLATFORM_PBR-4-RETRY_INSTALL : Route-map [chars] installed in hardware upon retry
Explanation The PBR manager was able to fit the complete configuration into the hardware. One or more route-maps had previously not been loaded because of lack of space.
Recommended Action No action is required.
Error Message%PLATFORM_PBR-4-SDM_MISMATCH : [chars] requires sdm template routing
Explanation In order to support this feature, sdm template routing needs to enabled.
Recommended Action Modify the Switch Database Management (SDM) template to enable the switch to support the routing template. Enter the sdm prefer routing configuration command, and then reload the switch by entering the reload privileged EXEC command.
Error Message%PLATFORM_PBR-3-UNSUPPORTED_RMAP : Route-map [chars] not supported for Policy-Based Routing
Explanation The route-map attached to an interface for policy routing contains an action that is not supported on this platform. This is a hardware limitation.
Recommended Action Reconfigure the route-map. Use only permit entries and set ip next-hop action in the route-map.
PLATFORM_PM Messages
The following are platform-specific port manager messages.
Error Message%PLATFORM_PM-3-IFCOUNTERROR : Unit number [dec] of interface [chars] is more than max allowed value of [dec]
Explanation System supports limited number of interfaces for each interface type. User created more than the number of supported interfaces.
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%PLATFORM_PM-3-INTVLANINUSE : internal vlan-id [dec] allocated for interface [chars] is still in use
Explanation internal vlan-id allocated for an interface is still in use.
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%PLATFORM_PM-3-NOINTVLAN : internal vlan of interface [chars] is not active for vlan-id [dec]
Explanation internal vlan_data is not active for the given vlan-id.
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.PLATFORM_RPC Messages
The following are platform RPC messages.
Error Message%PLATFORM_RPC-3-BAD_CLASS : Bad Class in RPC message: [int]
Explanation Class table missing entry for message class.
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%PLATFORM_RPC-3-MSG_THROTTLED : RPC Msg Dropped by throttle mechanism: type [int], class [int], max_msg [int], total throttled [int]
Explanation Too many outgoing messages queued up for msg class.
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%PLATFORM_RPC-3-PERSISTENT_UNABLE_TO_SEND : System is consistently unable to send RPC message: [chars], paks_outstanding: [int]
Explanation Persistent Low-level transport failure in sending RPC 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. 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%PLATFORM_RPC-0-RESOURCE_CRASH : [chars]
Explanation System is unable to allocate memory for RPC.
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%PLATFORM_RPC-3-RESP_FAIL : Unexpected response or failure, class [dec], req [dec], switch [dec], error [dec], [chars]
Explanation Received a response which is unexpected.
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%PLATFORM_RPC-3-SEND_FAIL : Failed to send RPC message in class [dec], req [dec], [chars]
Explanation Local resource error or too many outgoing messages queued up for msg class .
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%PLATFORM_RPC-3-UNABLE_TO_SEND : System is unable to send RPC message: [chars], paks_outstanding: [int]
Explanation Low-level transport failure in sending RPC 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. 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.PLATFORM_SPAN Messages
The following are platform SPAN messages.
Error Message%PLATFORM_SPAN-3-PACKET_DROP : Decreased egress SPAN rate.
Explanation When SPAN is enabled with multicast routing or bridge groups, the egress span rates will decrease. All packets going out might not be monitored.
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.PLATFORM_UCAST Messages
The following are platform unicast routing messages.
Error Message%PLATFORM_UCAST-3-ADJ : [chars]
Explanation Platform unicast routing adjacency module encountered an 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%PLATFORM_UCAST-3-ARP : [chars]
Explanation Platform unicast routing arp module encountered an 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%PLATFORM_UCAST-3-CEF : [chars]
Explanation Platform unicast routing cef module encountered an 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%PLATFORM_UCAST-3-DYNAMIC : [chars]
Explanation Platform's dynamic address tracking mechanism encountered an 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%PLATFORM_UCAST-3-ERROR : [chars]
Explanation An internal platform unicast routing error occured.
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%PLATFORM_UCAST-3-HSRP : [chars]
Explanation Platform unicast routing hsrp module encountered an 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%PLATFORM_UCAST-3-INTERFACE : [chars]
Explanation Platform unicast routing interface related error occured.
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%PLATFORM_UCAST-3-LB : [chars]
Explanation Platform unicast routing loadbalance module encountered an 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%PLATFORM_UCAST-3-LB_BACKWALK : [chars]
Explanation Platform unicast routing backwalk loadbalance module encountered an 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%PLATFORM_UCAST-3-NULL_HANDLE : [chars]
Explanation Platform unicast routing module received a NULL software object handle.
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%PLATFORM_UCAST-3-RPC : [chars]
Explanation Platform unicast routing rpc module encountered an 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.PLATFORM_VLAN Messages
The following are platform-specific VLAN messages.
Error Message%PLATFORM_VLAN-3-LOCK_FAIL : Failed to lock vlan-id [dec], associated mapped vlan id value [dec]
Explanation VLAN lock operation failed. Most likely cause might be either the vlan already active in the system or the vlan-id is not active.
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%PLATFORM_VLAN-3-MVID_ERROR : Mapped Vlan ID value [dec] associated with vlan-id [dec] is invalid
Explanation Each active vlan in the system is associated with a mapped-vlan-id and the mvid is not correct or valid.
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%PLATFORM_VLAN-3-UNLOCK_FAIL : Failed to unlock vlan-id [dec], associated mapped vlan id value [dec]
Explanation failed to unlock vlan-id. Most likely cause is the vlan is already freed.
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.PM Messages
The following are Port Manager messages.
Error Message%PM-1-INCONSISTENT_PORT_STATE : Inconsistent HW/SW port state for [chars]. Please shut/no shut the interface
Explanation The hardware and software port state has become inconsistent.
Recommended Action Enter a shutdown then a no shutdown command for the specified port.
Error Message%PM-3-INVALID_BRIDGE_PORT : Bridge Port number [dec] is out of range
Explanation The value of bridge portnumber that is passedto an internal Port Manager function is invalid. This indicates 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://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%PM-3-INVALID_SLOT_PORT : Slot/Port [dec]/[dec] is out of range
Explanation The values of slot and/or port that are passedto an internal Port Manager function are invalid. This indicates 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://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%PM-4-PVLAN_TYPE_CFG_ERR : Failed to set VLAN [dec] to a [chars] VLAN
Explanation Platform failed to set private VLAN 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. 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%PM_SCP-4-UNK_OPCODE : Received unknown unsolicited message from src_slot [dec], dest_slot [dec], length [dec], dsap [dec], ssap [dec], opcode [hex], seq_num [dec]
Explanation A message was sent to the supervisor by the linecard firmware.
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.POLICY_API Messages
The following are Policy API messages.
Error Message%POLICY_API-4-POLICYDYNCLR : Dynamic policy on intf:[chars] cleared. Static policy in use.
Explanation A dynamic policy was overriding the static policy. The dynamic policy has been cleared, the static policy is now in effect.
Recommended Action No action is required.
Error Message%POLICY_API-4-POLICYOVERIDE : Dynamic policy overriding static on intf:[chars]
Explanation Static policy and dynamic policy are configured on the interface. The dynamic policy will override the static policy.
Recommended Action Remove the static policy configuration, if desired.
Error Message%POLICY_API-3-SBINIT : Error initializing [chars] subblock data structure. [chars]
Explanation Initialization of the specified subblock data structure could not be accomplished.
Recommended Action Unavailable.
POLICY_MANAGER Messages
The following are Policy Manager messages.
Error Message%POLICY_MANAGER-2-INIT_FAILURE : Init failure: [chars]
Explanation A problem occurred in the Policy Manager during initialization.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%POLICY_MANAGER-3-INVALID_ACTION : Invalid action
Explanation An invalid Policy Manager action was 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. 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%POLICY_MANAGER-3-INVALID_PARAMETERS : A call to Policy Manager is made with invalid parameters
Explanation A call to Policy Manager was made with one or more invalid parameters.
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%POLICY_MANAGER-3-INVALID_SEVERITY : Invalid event severity [hex]
Explanation The event that was received by the Policy Manager contained an invalid severity and was therefore not processed.
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%POLICY_MANAGER-2-NO_FREE_EVENT_BUFFERS : Event pool depleted: [chars]
Explanation The event pool has been depleted. There are no free buffers to process event.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%POLICY_MANAGER-3-NO_FREE_POLICY_IDS : No more Policy IDs available
Explanation There are no more Policy IDs that can be allocated. The effect of this condition is that Policy Manager policies can no longer be created.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%POLICY_MANAGER-3-NULL_ACTION_ROUTINE : NULL action routine invoked
Explanation The Policy Manager attempted to invoke an action which was NULL.
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%POLICY_MANAGER-3-PRE_INIT_CALL : Policy Manager routine called prior to initialization
Explanation The Policy Manager component was called prior to initialization.This could result in vital information being lost.
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.PORTCHAN Messages
The following are Ethernet channel messages.
Error Message%PORTCHAN-6-LINKMTU : [chars]
Explanation Notification of etherchannel link MTU changes.
Recommended Action No action is required.
PORT_SECURITY Messages
The following are Port Security messages.
Error Message%PORT_SECURITY-4-PORTSEC_RATELIMIT_DISABLED : Layer 2 port security rate limiter disabled while port security enabled.
Explanation Layer 2 port security rate limiter disabled by user while port security is enabled.
Explanation Configure: mls rate-limit layer2 port-security 6000 10.
Error Message%PORT_SECURITY-4-PORTSEC_RATELIMIT_FAIL : Fail to set port security rate limiter when enabling port security.
Explanation This failure happens when enabling port security.
Recommended Action Configure: mls rate-limit layer2 port-security 6000 10. It may be necessary to remove an existing layer 2 rate limiter.
POS Messages
The following are packet over SONET messages.
Error Message%POS-6-EVENTSYNC : Redundancy state event synchronization failure slot [dec]/[dec] - ([chars])
Explanation A failure occurred in trying to synchronize POS state information.
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. 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%POS-3-INTERNAL : POS internal error, [chars] [dec] [dec]
Explanation Internal POS 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%POS-3-INTERNALCMD : POS LC command internal error, [chars] [dec] [dec]
Explanation Internal POS LC command 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%POS-3-INTERNALEVT : POS LC Event internal error, [chars] [dec] [dec]
Explanation Internal POS LC event 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%POS-3-ISSU_ATTACH : POS LC ISSU attach function received invalid call type [dec]
Explanation Internal POS LC ISSU 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%POS-6-MESSAGESYNC : Redundancy state message synchronization failure - ([chars])
Explanation A failure occurred in trying to synchronize POS state information.
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. 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%POS-3-MIBINITFAIL : POS MIB initialization failed, [chars] [dec]
Explanation MIB initialization for POS Failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%POS-3-REDFATALLCEVT : Fatal error event on i/f ([chars]) reason: [chars]
Explanation Internal redundant LC fatal event.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%POS-4-REDINLCEVT : Redundant inactive i/f ([chars]) event: [chars], reason: [chars]
Explanation Internal redundant LC event.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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.POT1E1 Messages
The following are Versatile Interface Processor (VIP) multichannel port adapter messages.
Error Message%POT1E1-3-FREEDMFATAL : Bay [dec]: freedm reset, command-status register [hex]
Explanation POT1E1 experienced fatal freedm related 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. 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%POT1E1-2-NOACCPTR : VC=[dec] [chars]
Explanation POT1E1 had a do_inc=FALSE.
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%POT1E1-2-NOINC : [chars]
Explanation POT1E1 had a NULL ACC PTR while incrementing.
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%POT1E1-2-QTAIL : Qhead=[hex] particle_count=[dec] size=[dec]
Explanation POT1E1 had a NULL Qhead.
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%POT1E1-2-TXBADVC : [chars], vc [dec]
Explanation POT1E1 had a Tx Bad VC.
Recommended Action CCopy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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.PPP Messages
The following are Point-to-Point Protocol (PPP) messages.
Error Message%PPP-3-ISSU_ERR : [chars]
Explanation An error occurred during an ISSU versioning operation.
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.PRBS Messages
The following are Pseudo-Random Bit Sequence messages.
Error Message%PRBS-5-DECERR : Slot:[dec],Subcard:[dec],Port:[dec] Decoding error [dec] at time [dec] sec.
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%PRBS-5-GETARGERR : process_get_arg_num error.
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%PRBS-5-LOSSLOCK : Slot:[dec],Subcard:[dec],Port:[dec] Loss of Lock at time [dec] sec.
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%PRBS-5-PASSED : Slot:[dec],Subcard:[dec],Port:[dec] [dec] sec PRBS test passed.
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%PRBS-5-STATUSERR : Slot:[dec],Subcard:[dec],Port:[dec] at [dec] sec status error [dec], quit.
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%PRBS-5-STOP : Slot:[dec],Subcard:[dec],Port:[dec] PRBS test stop at [dec] sec.
Explanation Unavailable.
Recommended Action Unavailable.
PRST_IFS Messages
The following are persistent media IFS messages.
Error Message%PRST_IFS-3-FILE : 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. 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://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.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, so 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, issue 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. Research and attempt to resolve the 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-3-WS_ACL_BLOCK_ARRAY_ERROR : Failed to [chars] node [int] due to an unallocated row pointer table in node [int]
Explanation While adding or removing a table entry or row to or from 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.Error Message%PXF_ACL-3-WS_ACL_BLOCK_ARRAY_WARN : Failed to [chars] node [int] due to an unallocated row pointer table in node [int]
Explanation While adding or removing a table entry or row to or from 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. Unless otherwise indicated by another error message, forwarding will continue normally.
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%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.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.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 error 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 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. 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-3-WS_ACL_CONTEXT_EVENT : [chars] [chars]
Explanation An invalid turbo ACL context is used to call block init, possibly due to process level watchdog timeout.
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%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 Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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-3-WS_ACL_EVENT : [chars]
Explanation Generic PXF TurboACL errors.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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-3-WS_ACL_MALLOC_EVENT : [chars] [chars]
Explanation Dynamic allocation for a turbo ACL node failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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-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. Research and attempt to resolve the 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-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. Research and attempt to resolve the 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-3-WS_ACL_PXF_CONTEXT_EVENT : [chars] [chars]
Explanation An invalid PXF turbo ACL context is used to call block init, possibly due to process level watchdog timeout.
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%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 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. 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-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.Error Message%PXF_ACL-3-WS_ACL_TABLE_UPDATE_ERROR_LT : Failed to [chars] node [int] due to an internal error: [chars] [int] is not less than [chars] [int]
Explanation While adding or removing an entry or row to or from 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.Error Message%PXF_ACL-3-WS_ACL_TABLE_UPDATE_WARN_LT : Failed to [chars] node [int] due to an internal error: [chars] [int] is not less than [chars] [int]
Explanation While adding or removing an entry or row to or from 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. Unless otherwise indicated by another error message, forwarding will continue normally.
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%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 issuing the test c7300 acl command if you are using a release prior to 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.
Error Message PXFAPI MessagesError 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. Research and attempt to resolve the 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%PXFAPI-2-CHUNK_FREEFREE : Attempted to free unallocated block atUnrecognized format ` %p' (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. Research and attempt to resolve the 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%PXFAPI-3-IFNUMZERO : Interface (Slot [dec], Slotunit [dec], Subunit [dec]) number unavailable.
Explanation This error occurs when the PXF interface table is 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 gotten 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 commands. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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.PXFAPI Messages
The following are Parallel eXpress Forwarding (PXF) API-related messages.
Error Message%PXFAPI-3-TIFBAD : TIF [int] is not available or invalid.
Explanation The PXF interface instance which was requested is not available or invalid.
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%PXFAPI-3-TIFINUSE : Request for in-use reserved TIF [int]
Explanation A PXF interface instance was requested but is currently reserved as it is still in use.
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%PXFAPI-3-TIFNODETACH : TIF [int] could not be detached.
Explanation The PXF interface instance could not be detached.
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_CLIENT_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_DMA Messages
The following are Parallel eXpress Forwarding (PXF) DMA subsystem messages.
Error Message%PXF_DMA-3-DATAVALID_TIMEOUT : RP indirect read access timed out (column [dec], local address [hex])
Explanation While attempting an indirect read access to an XCM or ICM location, the RP timed out waiting for the DataValid bit to indicate that the access is complete
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%PXF_DMA-3-FBB_LINE_CARD : [chars]
Explanation A PXF DMA FBB Line Card 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.Error Message%PXF_DMA-3-FTBB_ERROR : FTBB is set to disable for slot [int]/[int]!
Explanation FTBB is 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.Error Message%PXF_DMA-3-IRONBUS_NOTRUNNING : Data path to slot [int]/[int] failed to synchronize ([chars])
Explanation PXF DMA data path 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. 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_DMA-2-TBB_SYNC_FAILED : TBB sync of the RP failed. No traffic is being sent to the RP!
Explanation TBB synchronization of RP failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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_DMA-2-TBB_SYNC_LC_FAILED : TBB sync of the line card failed (slot [int]/[int]). No traffic is being through the line card. Need to reset the line card.
Explanation TBB synchronization of RP failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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_FIB Messages
The following are Parallel eXpress Forwarding (PXF) FIB select-specific messages.
Error Message%PXF_FIB-3-WS_FIB_RW_EVENT : [chars] [dec] [chars]
Explanation Layer 2 information of The Interface is not consistent in PXF. The router might resume operation after this message.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that 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_FIB-3-WS_FIB_TIF_EVENT : [chars] [chars]
Explanation Interface is not having a valid PXF Handle attached to it. The router might resume operation after this 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. 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_FLOW Messages
The following are Parallel eXpress Forwarding (PXF) Netflow-related messages.
Error Message%PXF_FLOW-4-INVLDAGG : The netflow aggregation scheme is not supported in PXF. All netflow enabled interfaces will be marked as unsupported by the PXF, all incoming or outgoing traffic in these interfaces will be processed in the RP.
Explanation The only netflow aggregation schemes supported in the PXF are: AS aggregation, proto port aggregation, source prefix aggregation and destination aggregation.
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%PXF_FLOW-4-INVLDAGG_SINGLE : The netflow aggregation scheme is not supported in PXF. This interface will be marked as unsupported by the PXF, all incoming or outgoing traffic to this interface will be processed in the RP.
Explanation The only netflow aggregation schemes supported in the PXF are: AS aggregation, proto port aggregation, source prefix aggregation and destination aggregation.
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_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 into PXF memory. EtherChannel hash info 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.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 into 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.PXF_GRE Messages
The following are Parallel eXpress Forwarding (PXF) GRE tunnel-related messages.
Error Message%PXF_GRE-4-PXF_MEM_ERR : Memory allocation error while [chars]
Explanation An error has occured while allocating memory. PXF could not process tunneled packet 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. 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_GRE-3-PXF_MEM_ERR_CLR_TSTATS : PXF MEM ERROR when clearing PXF tunnel stats (Addr=[hex])
Explanation An error occurred when clearing the tunnel stats from PXF memory. The tunnel statistics could not be properly cleared.
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%PXF_GRE-3-PXF_MEM_ERR_HINFO : PXF MEM ERROR when downloading tunnel hash info to PXF (Addr=[hex])
Explanation An error occurred when writing into PXF memory. tunnel hash info could not be properly downloaded.
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%PXF_GRE-3-PXF_MEM_ERR_HTIFS : PXF MEM ERROR when downloading tunnel hashed tifs to PXF (Addr=[hex])
Explanation An error occurred when writing into PXF memory. Hashed tunnel tifs 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.Error Message%PXF_GRE-3-PXF_MEM_ERR_READ_TSTATS : PXF MEM ERROR when reading PXF tunnel stats (Addr=[hex])
Explanation An error occurred when reading the tunnel stats from PXF memory. The tunnel statistics could not be properly read.
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%PXF_GRE-3-PXF_MEM_ERR_TID : PXF MEM ERROR when downloading tunnel id to PXF (Addr=[hex])
Explanation An error occurred when writing into PXF memory. The tunnel id 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.Error Message%PXF_GRE-3-PXF_MEM_ERR_TVRF : PXF MEM ERROR when downloading tunnel vrf to PXF (Addr=[hex])
Explanation An error occurred when writing into PXF memory. The tunnel vrf 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.PXF_MPLS_TE Messages
The following are Parallel eXpress Forwarding (PXF) MPLS TE messages.
Error Message%PXF_MPLS_TE-4-PXF_MEM_ERR : Memory allocation error while [chars]
Explanation An error has occured while allocating memory. PXF could not process tunneled packet 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. 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_MPLS_TE-3-PXF_MEM_ERR_CLR_TSTATS : PXF MEM ERROR when clearing PXF tunnel stats (Addr=[hex])
Explanation An error occurred when clearing the tunnel stats from PXF memory. The tunnel statistics could not be properly cleared.
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%PXF_MPLS_TE-3-PXF_MEM_ERR_LKUP_TABLE : PXF MEM ERROR when downloading TE tunnel look-up table to PXF (Addr=[hex])
Explanation An error occurred when writing into PXF memory. Look-up 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.Error Message%PXF_MPLS_TE-3-PXF_MEM_ERR_READ_TSTATS : PXF MEM ERROR when reading PXF tunnel stats (Addr=[hex])
Explanation An error occurred when reading the tunnel stats from PXF memory. The tunnel statistics could not be properly read.
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_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 An 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.PXF_NICKEL Messages
The following are NICKEL messages.
Error Message%PXF_NICKEL-2-BOUND_MODE_OTHER_SSLT_IB_ERR : Card for which Ironbus interface restart is being initiated is running in Bound mode.
Opposing subslot is slot [dec], subslot [dec]
Opposing subslot's IB error statistics counts are as follows:
multisop_1frm = [int], bad9th_bit_frm = [int], allzeros = [int], unexp_fsync = [int],
missing_fsync = [int], len_hi_nonzero = [int], giant = [int], runt = [int]Explanation In bound mode, opposing subslot IB errors.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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-2-BOUND_MODE_OTHER_SSLT_IMCMP_ERR : Card for which Ironbus interface restart is being initiated is running
in Bound mode and opposing subslot's Ironbus interface is not in a compatible
state. (i.e. - Opposing subslot is either in reset, not ready, or does not have
Cobalt event processing enabled for it.)
Opposing subslot is slot [dec], subslot [dec]
Opposing subslot's reset bit = [hex] (1 = subslot in reset)
Opposing subslot's ready bit = [hex] (0 = subslot not in ready state)
Opposing subslot's event mask bit = [hex] (1 = event processing for subslot is not enabled)Explanation In bound mode, opposing subslot not compatible.
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%PXF_NICKEL-3-FBB_LINE_CARD : A Nickel FBB Line Card Error has occurred.
Explanation A Nickel FBB Line Card 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.Error Message%PXF_NICKEL-3-FTBB_ERROR : FTBB is set to disable for slot [int]/[int]!
Explanation FTBB is 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.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 error message is persistent. 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%PXF_NICKEL-2-GLOB_EVT_FBB_EVT : Nickel FBB Error: nickel[dec] fbb_event_reg @ [hex] = [hex]
Explanation Nickel FBB Event.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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-2-GLOB_EVT_FTS_EVT : Nickel FTS Error: nickel[dec] fts_event_reg @ [hex] = [hex]
Explanation Nickel FTS Event.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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-2-GLOB_EVT_IB_EVT : Nickel Ironbus Error: ib_event @ [hex] = [hex]
Explanation Nickel IB Event.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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-2-GLOB_EVT_IB_SEC_READ_ERR : Nickel Ironbus Err Second Read Non-Zero: stat1=[hex], stat2=[hex], stat3=[hex]
Explanation Nickel IB Error Not Clear on Read.
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%PXF_NICKEL-2-GLOB_EVT_IB_SLT : Nickel Ironbus Error: nickel[dec] IB slot[dec]/subslot[dec] event
Explanation Nickel IB Event In Slot.
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%PXF_NICKEL-2-GLOB_EVT_IB_STAT : Nickel Ironbus Stat[dec]: @ [hex] = [hex]
Explanation Nickel IB Statistic.
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%PXF_NICKEL-2-GLOB_EVT_REG : Nickel Global Event Reg: nickel[dec]: Addr = [hex], Value = [hex]
Explanation Nickel Global Event Register.
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%PXF_NICKEL-2-GLOB_EVT_STT_EVT : Nickel STT Error: nickel[dec] stt_event_reg @ [hex] = [hex]
Explanation Nickel STT Event.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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-2-GLOB_EVT_TBB_EVT : Nickel TBB Error: nickel[dec] tbb_event_reg @ [hex] = [hex]
Explanation Nickel TBB Event.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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-2-IB_ENABLE_FAILED : Ironbus enable failed
Explanation Ironbus enable failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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-2-IB_ERR_OVER_THRSHLD : IB error statistics exceeded threshold for slot [dec], subslot [dec]
IB restart initiated. Subslot error statistics counts are as follows:
multisop_1frm = [int], bad9th_bit_frm = [int], allzeros = [int], unexp_fsync = [int],
missing_fsync = [int], len_hi_nonzero = [int], giant = [int], runt = [int]Explanation Too many ironbus errors .
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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-2-IB_ERR_SPR : IB Stuck Pause Request Error in slot[dec]/subslot[dec]: status reg @ [hex] = [hex]
Explanation Ironbus Stuck Pause Request 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%PXF_NICKEL-2-IB_STATUS_FAILED : [chars] received failure status
Explanation Ironbus status failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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-INIT_ERR : Nickel Initialization failed!
Explanation Nickel ASIC initialization failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show hardware nickel command to gather data that might 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. 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-2-INVALID_EVNT_ID : [chars]: invalid event id ([dec])
Explanation Invalid event ID.
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%PXF_NICKEL-2-INVALID_SLOT0_CFG : Current HW level not allow to configure subslot 0.
Explanation Incorrect configuration to slot 0.
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%PXF_NICKEL-2-INVALID_SLOT_PTR : get_vanadium_revision(): Error - Invalid slot pointer
Explanation Invalid slot pointer.
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%PXF_NICKEL-3-IRONBUS_NOTRUNNING : Data path to slot [int]/[int] failed to synchronize ([chars])
Explanation NICKEL data path 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. 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-2-LC_ASIC_VER_ERR : Error:get_lc_asic_ver() failed. Slot[dec]
Explanation Incorrect LC ASIC version.
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%PXF_NICKEL-2-LC_NOT_IN_SLOT : LC in slot [dec] doesn't exist
Explanation No LC in the slot.
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%PXF_NICKEL-3-MALLOCFAIL : Nickel driver malloc failed!
Explanation Not enough free memory for the NICKEL driver to operate.
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%PXF_NICKEL-2-NOT_HANDLED_EVNT : Event [chars] not handled
Explanation Not handled event.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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-NOT_INIT : Either no Nickel on the board or Nickel init failed.
Explanation Either no Nickel on the board or Nickel initialization failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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-2-PLL_NOT_LOCK : PLLs did not lock: glob_status @[hex] = [hex]
Explanation PLL not lock.
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%PXF_NICKEL-3-REG_ADDR_ERR : Nickel Address Error [chars], Bad Address Range: [hex] through [hex]
Explanation Access to invalid Nickel register address.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show hardware nickel command to gather data that might 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. 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-2-SLOT_OUT_OF_RANGE : is_slot_bound(): Received out-of-range slot value. Slot passed in = [dec].
Explanation Slot number passed into is_slot_bound() is out of range.
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%PXF_NICKEL-3-SPI_SYNC_FAIL : Nickel[int] SPI RX/TX Sync Failure: spi4_status=[hex]
Explanation NICKEL SPI RX/TX sync failure.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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 which warrants further investigation by Cisco Technical Support
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 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%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 error message is persistent.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%PXF_NICKEL-2-TBB_SYNC_FAILED : TBB sync of the RP failed. No traffic is being sent to the RP!
Explanation TBB synchronization of RP failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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-2-TBB_SYNC_LC_FAILED : TBB sync of the line card failed (slot [int]/[int]). No traffic is being through the line card. Need to reset the line card.
Explanation TBB synchronization of RP failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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-2-TIB_IB_RESET_FAILED : TIB IRONBUS_RESET command failed
Explanation Reset TIB failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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-2-UNKNOWN_EVNT_REG : [chars]: unknown event register ([dec])
Explanation Unknown event register.
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%PXF_NICKEL-3-VAN_V1_NOT_SUPPORT : slot [int] contains a Vanadium version 1 LC which is no longer supported by C10K3.
Explanation This slot contains a Vanadium1 LC not supported by C10K3.
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_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 recompilation might free some memory.
Error Message%PXF_QOS-3-QOS_RP_GEN_XOFF : XOFF with tif number 0 is generated
Explanation PXF received unexpected XOFF from RP; 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.Error Message%PXF_QOS-3-QOS_STAT_GENERATION_FAIL : Cannot [chars] actual QoS statistics generation in PXF
Explanation An error occurred when enabling or disabling QoS Statistic Generation.
Recommended Action Disable and re-enable PXF qos-statistics. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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_QOS-3-SUB_INTF_SRVPOL_FAIL : Error attaching [chars] service-policy PXF data to [chars]: [chars]
Explanation The assignment of the PXF portion of the service-policy data to a sub-interface has failed. This means that, even though the configuration shows that the service-policy is attached to the sub-interface, the download of the necessary PXF data has not occurred. Because of that, the service-policy will not be effective on the sub-interface.
Recommended Action Detach and reattach the service-policy to the sub-interface. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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_QOS-3-WS_QOS_L2C_CLASS_NODE_TOO_LARGE : Classification node [dec]'s table size of [int] is too large for PXF. PXF QoS layer 2 classification will not function correctly.
Explanation PXF QoS Layer 2 Classification: the size of classification table for the specified node is larger than the amount of PXF memory set aside for that node.
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%PXF_QOS-3-WS_QOS_L2C_EGRESS_CLASS_ENTRY_PXF_MEM_ERR : PXF MEM ERROR when downloading classification entry of egress traffic to PXF (Addr=[hex]). PXF QoS layer 2 classification will not function correctly.
Explanation PXF QoS Layer 2 Classification: an error occurred when writing to PXF memory. The classification entry could not be properly downloaded.
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%PXF_QOS-3-WS_QOS_L2C_MALLOC_FAILED_PLATFORM_INIT : The system failed to allocate a PXF data structure for layer 2 classification engine. PXF QoS layer 2 classification will not function correctly.
Explanation PXF QoS Layer 2 Classification: there is not enough memory to setup layer 2 classification engine.
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%PXF_QOS-3-WS_QOS_L2C_TOO_MANY_L2_LKP_TBLS : Too many possible PXF QoS layer 2 lookup tables: [int]. PXF QoS layer 2 classification will not function correctly.
Explanation PXF QoS Layer 2 Classification: the resulted PXF QoS layer 2 lookup tables exceeds system limitation.
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_VRFS Messages
The following are Parallel eXpress Forwarding (PXF) VRFS 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 re-occurs 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.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 error message shows the reason why.
Recommended Action Reasons for this to happen could be software errors and resource problems. Should the error 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 then 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 then 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 error message.
Recommended Action The reason for this can be a software problem or router memory exhaustion. Verify that the router has enough memory using the show memory summary command. If the router does have enough memory then copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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_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.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 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. 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.QM Messages
The following are quality of service messages.
Error Message%QM-4-NO_IP_DSCP_RW_SLOT_IGNORED :
'no mls qos rewrite ip dscp slot [dec]' will not be effective. Disable
the ip-dscp-rewrite on Supervisor (slot [chars]) to avoid ip-dscp-rewrite of
packets coming in on non-DFC linecards.
Explanation If a non-PFC or non-DFC slot is provided in the no mls qos rewrite ip dscp command, the command will not be effective for the slot. If ip-dscp-rewrite must be
disabled for packets coming in on a non-DFC line card, the Active Supervisor slot
must be provided in the command.Recommended Action To disable dscp-rewrite of packets coming in on a non-DFC line card, disable the dscp-rewrite on the Active Supervisor slot.
Error Message%QM-4-UNEXPECTED_INTERNAL_QOS_CONDITION : Unexpected internal QoS condition.
Explanation This message means that an unexpected internal QoS condition has occurred. QoS debug might be enabled to obtain more information in case the condition recurs.
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.QOS Messages
The following are QoS messages.
Error Message%QOS-6-ACTIVATE :
Activating service policy [chars] on [chars] in [chars] directionExplanation The interface bandwidth is more than the total bandwidth that is required for QoS policy on this interface.
Recommended Action No action is required.
Error Message%QOS-6-ACTIVATE_NOHW :
Activating service policy [chars] in [chars] directionExplanation Unavailable.
Recommended Action Unavailable.
Error Message%QOS-3-ATLEAST_ONE_FAILOVER_ERR : Fail-over of dynamic interface [chars] failed
Explanation Dynamic interface has changed its route out of different physical interface and queueing cannot set-up data-sructures for that new physical interface.
Recommended Action One possibility is that new physical interface already has service-policy or some other dynamic interface already has queueing data-structures associated with that physical interface and conjuction of such service-policies are not allowed. Remove one or the other service-policy in that case. If that is not the case, then copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%QOS-3-BADXDRSLOT : Invalid XDR slot. Type/len/slot [dec]/[dec]/[chars]. XDR at [hex]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%QOS-3-BURST_BC_ERR : Burst Bc increased to [dec] bytes
Explanation If Burst BC is less than the default burst size then Burst Bc is increased to AF_DEAFULT_BURST.
Recommended Action This is informational message. No action is required.
Error Message%QOS-3-COEX_NOT_ALLWD : queueing policy at session cannot co-exist with servicepolicy at sub-interface/pvc
Explanation There already might be user-defined flat policy or hierarchical policy at the sub-interface/pvc. With existing of such policy no queueing policy is allowed on session.
Recommended Action Remove the policy attached to the sub-interface or pvc before attaching a new policy to a session.
Error Message%QOS-6-EXTENDED_BURST_CHANGED_WARN : Illegal extended burst size; it is increased to [int]
Explanation The configured extended burst size is illegal because it is less than the burst rate. It has been increased to an amount equal to the rate, depending on the MTU of the interface.
Recommended Action Informational message only. No action is required.
Error Message%QOS-4-FO_IN_USE : Releasing feature object with reference count [dec]
Explanation This is an internal software error. A QoS policy feature object has a stale reference.
Recommended Action If the message recurs, isolate the traffic conditions which trigger the message and contact technical support. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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 tech-support and show policy-map interface command and your pertinent troubleshooting logs.Error Message%QOS-3-HA_BULK_SYNC_BEFORE_TIMEOUT : [chars] Failure in completing bulk sync before timeout
Explanation QoS configuration canot be synchronized to the standby.
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%QOS-3-HQFNOPAK : interface [chars]: pak_reparent failed
Explanation Pak_reparent has been invoked and failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%QOS-3-HQFPAKREQUEUE : interface [chars]: pak_requeue_head has been invoked
Explanation pak_requeue_head() function has been invoked on a packet. One or more packets have been dropped. This is not the normal mode of operation.
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%QOS-3-HQF_QID_ERR : Maximum number of QoS queues ([dec]) reached.
Explanation The system has run out of QoS queue identifiers and cannot allocate any more until existing queues are freed.
Recommended Action Remove the existing QoS configurations to free up more queue identifiers. For example, remove the existing QoS service-policy configurations or modify policy-map templates to have fewer queueing actions.
Error Message%QOS-3-INVALID_POLICY : queueing policy at session can co-exist only with class-default shaping policy at sub-interface/pvc
Explanation There already might be user-defined flat policy or hierarchical policy at the sub-interface/pvc. With existing of such policy no queueing policy is allowed on session.
Recommended Action Make sub-interface/pvc based policy just one level policy with only class-default.
Error Message%QOS-4-LC_STATS_MSG_DROPPED : QoS statistics update message dropped due to [chars]
Explanation Changes to QoS counters are sent periodically from line cards to the route processor. One of these statistics updatemessages was discarded because it was inconsistent or because the route processor ran out of message buffers.The packet and bytes counters for a single service-policy might be underreported by show commands and SNMP queries.
Recommended Action This is an informational message only. No action is required.
Error Message%QOS-6-NORMAL_BURST_CHANGED_WARN : Illegal normal burst size; it is increased to [int]
Explanation The configured extended burst size is illegal because it is less than the burst rate. It has been increased to an amount equal to the rate, depending on the MTU of the interface.
Recommended Action Informational message only. No action is required.
Error Message%QOS-6-SUSPEND :
Suspending service policy [chars] on [chars] in [chars] directionExplanation The interface bandwidth is less than the total bandwidth that is required for QoS policy on this interface.
Recommended Action No action is required.
Error Message%QOS-3-VTEMP_MAIN_ERR : Attaching a service policy to a PPP/PPPoE virtual-access interface is not allowed when another policy is already attached to the main interface to which the PPP/PPPoE virtual-access interface is bound.
Explanation Attaching a service policy to a PPP/PPPoE virtual-access interface is not allowed when another policy is already attached to the main interface to which the PPP/PPPoE virtual-access interface is bound.
Recommended Action Remove the policy attached to the main interface before attaching a new policy to a PPP/PPPoE virtual-access interface.
Error Message%QOS-3-VTEMP_MLP_ERR : A service policy cannot be attached to a PPP virtual-access interface when ppp multilink is enabled. A service policy can be attached to a ppp multilink bundle interface only.
Explanation A service policy attached to a virtual-template is usually copied to associated virtual-access interfaces. However, if such a virtual-access interface joins a multilink ppp bundle, the policy is not attached to the virtual-access interface.
Recommended Action This is an informational message. No action is required.
Error Message%QOS-3-VTEMP_SUB_ERR : Attaching a service policy to a PPP/PPPoE virtual-access interface is not allowed when another policy is already attached to the subinterface to which the PPP/PPPoE virtual-access interface is bound.
Explanation Attaching a service policy to a PPP/PPPoE virtual-access interface is not allowed when another policy is already attached to the subinterface to which the PPP/PPPoE virtual-access interface is bound.
Recommended Action Remove the policy attached to the subinterface before attaching a new policy to a PPP/PPPoE virtual-access interface.
Error Message%QOS-3-VTEMP_VC_ERR : Attaching a service policy to a PPP/PPPoE virtual-access interface is not allowed when another policy is already attached to the vc/pvc to which the PPP/PPPoE virtual-access interface is bound.
Explanation Attaching a service policy to a PPP/PPPoE virtual-access interface is not allowed when another policy is already attached to the vc/pvc to which the PPP/PPPoE virtual-access interface is bound.
Recommended Action Remove the policy attached to the vc or pvc before attaching a new policy to a PPP/PPPoE virtual-access interface.
Error Message%QOS-3-XDRLEN : Invalid XDR length. Type [dec][chars]. XDR/buffer len [dec]/[dec]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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.QOSMGR Messages
The following are QoS manager messages.
Error Message%QOSMGR-4-ACTION_NOT_SUPPORTED : Action is not supported in policymap [chars]
Explanation An action other than the set, trust, and police policy-map class configuration commands was configured in a policy map. This is a hardware limitation.
Recommended Action Configure only the supported actions of set, trust, and police when in policy-map class configuration mode.
Error Message%QOSMGR-4-CLASS_NOT_SUPPORTED : Classification is not supported in classmap [chars]
Explanation This message means the an unsupported match class-map configuration command was configured in a policy map and attached to an egress interface, or that more than one match command was configured. This is a hardware limitation.
Recommended Action Reconfigure the class map or the policy map. Use only the match ip dscp dscp-list class-map configuration command in a policy map that is attached to an egress interface. Only one match per class map is supported.
Error Message%QOSMGR-4-COMMAND_FAILURE : Execution of [chars] command failed on [chars]
Explanation The command to configure a QoS setting failed. This is possible due to lack of hardware resources. Check if any other messages along with this message indicate resource failure.
Recommended Action If other messages indicate that the hardware resources exceeded, retry the command with a smaller configuration. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%QOSMGR-3-FEATURE_NOT_FOUND : Cannot find feature for [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. Enter the show running-config command to gather data that might 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. 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%QOSMGR-3-FILTERTYPE_INVALID : Internal Error Invalid Policy filtertype [dec]
Explanation An internal software error has occurred.
Recommended Action
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather data that might 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. 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%QOSMGR-4-HARDWARE_NOT_SUPPORTED : Hardware limitation has reached for policymap [chars]
Explanation The policy map configuration has exceeded the limitation of the hardware. You configured more QoS ACL entries than the number specified in the Switch Database Management (sdm) template.
Recommended Action Reconfigure the class map or the policy map, and reduce the number of QoS ACLs.
Error Message%QOSMGR-4-MATCH_NOT_SUPPORTED : Match type is not supported in classmap [chars]
Explanation Match ACL, match ip dscp and match ip precedence are the match types that are supported.
Recommended Action Reconfigure the class map; use only the match access-group, match ip dscp, and match ip precedence class-map configuration commands within the class map.
Error Message%QOSMGR-3-MERGE_RES_COUNT : Internal Error Invalid count
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather data that might 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. 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%QOSMGR-3-NO_POLICER_QOSLABEL : Creating port Class Label Failed
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather data that might 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. 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%QOSMGR-4-NOT_SUPPORTED : Action '[chars]' is not supported for a policymap attached to output side.
Explanation This message means that a set or trust policy-map class configuration command was configured in a policy map and attached to an egress interface. A warning message is logged, and the actions do not take affect. This is a hardware limitation.
Recommended Action Do not configure a set or trust policy-map class configuration command in a policy map and attach it to an egress interface. These policy-map actions are supported only on ingress interfaces.
Error Message%QOSMGR-3-NO_VMR_QOSLABEL : qm_generate_vmrs have no qos label
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather data that might 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. 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%QOSMGR-3-NULL_POLICER : Internal Error Invalid Policer
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather data that might 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. 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%QOSMGR-4-POLICER_PLATFORM_NOT_SUPPORTED : Policer configuration has exceeded hardware limitation for policymap [chars]
Explanation The policy map configuration has exceeded the limitation of the hardware. You configured more policers together in all policy maps (by using the police or police aggregate policy-map class configuration command) than supported by hardware.
Recommended Action Reconfigure the class map or the policy map or delete policy from some interfaces.
Error Message%QOSMGR-4-POLICER_POLICY_NOT_SUPPORTED : Number of policers has exceeded per policy hardware limitation for policymap [chars]
Explanation The policy map configuration has exceeded the limitation of the hardware. You configured more policers in a policy map (by using the police or police aggregate policy-map class configuration command) than supported.
Recommended Action Reconfigure the class map or the policy map, and reduce the number of policers.
Error Message%QOSMGR-3-POLICER_RES_COUNT : Internal Error Invalid Policer count
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather data that might 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. 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%QOSMGR-3-POLICYMAP_NOT_FOUND : Cannot find policymap for [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. Enter the show running-config command to gather data that might 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. 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%QOSMGR-3-QUEUE_PTR_ERROR : queue pointers out of order [hex] [hex] [hex] [hex]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather data that might 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. 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%QOSMGR-3-RESERVE_COUNT_ERROR : Reserved Count Exceeding total [dec]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather data that might 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. 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%QOSMGR-3-RESOURCE_INTERNAL : Internal Error in resource allocation
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather data that might 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. 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%QOSMGR-3-VMRSEQ_INVALID : Internal Error Invalid VMR sequence
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather data that might 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. 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.QUICC Messages
The following are QUICC Ethernet messages.
Error Message%QUICC3-1-LOSTCARR : Unit [dec], lost carrier. Transceiver problem?
Explanation The Ethernet 10BASE-T cable is unplugged.
Recommended Action Reconnect the Ethernet 10BASE-T cable.
RADIUS Messages
The following are RADIUS messages.
Error Message%RADIUS-3-ALLDEADSERVER : Group [chars]: No active radius servers found. Id [dec].
Explanation This error message occurs when all the servers configured in a server group are found to be unresponsive.
Recommended Action Check the network connectivity to the RADIUS servers, and check that the servers are running.
Error Message%RADIUS-3-BUFFER_OVERFLOW : Radius I/O buffer has overflowed
Explanation An unusually large number of RADIUS attributes has caused AAA to overflow its RADIUS I/O buffer.
Recommended Action This is an internal software error. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%RADIUS-3-CANNOT_OPEN_SOCKET : Cannot open UDP socket for service [chars]
Explanation The router is unable to open a socket for UDP communications by the indicated service. Most of the time another service might be using the same port.
Recommended Action Check your configuration to make sure that no other services are using the same port. If this message recurs, copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather data that might 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. 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%RADIUS-3-CORRUPTCONTEXT : Bad Magic pattern in [chars]:[hex], magic:[hex]!
Explanation The magic pattern imprinted on the internal hash table data structures in RADIUS subsystem is missing and indicates memory corruption. The memory is getting overwritten by a misbehaving process. The traceback and the process information is generated to the result of the error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that 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%RADIUS-3-FORKFAIL : Failed to fork process for [chars].
Explanation Quite likely, we ran out of memory. Other explanations are possible.
Recommended Action If this message recurs, 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 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%RADIUS-3-FORMATLONG : Format string too long.Maximum allowed length is [dec].
Explanation The user is attempting to configure a format string with a prefix that is too long.
Recommended Action Enter a shorter string to configure.
Error Message%RADIUS-6-GETPOOLS : Retrieving IP-Pools via user [chars]
Explanation Getting initial IP-Pool definitions from RADIUS, using the given user's profile.
Recommended Action No action is required.
Error Message%RADIUS-6-GETROUTES : Retrieving static routes in user [chars]
Explanation Getting initial static routes from RADIUS, using the given user's profile.
Recommended Action No action is required. The message is informatory in nature indicating that it is getting the static routes based on user's profile.
Error Message%RADIUS-3-IDENTFAIL : Saving of unique accounting ident aborted. Configuration has been modified.
Explanation The configuration has been modified. It cannot save the unique accounting IDENT to nvram. The message is to inform the user that the saving of unique accountingident is aborted due to the change in configuration.
Recommended Action If this message recurs, 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 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%RADIUS-6-IDENTSAVE : Saving config with new acct ident in nvram.
Explanation Saving an accounting ident in nvram.
Recommended Action Informational message only. No action is required.
Error Message%RADIUS-3-INVALIDFORMAT : Invalid Nas Port Format: [chars] [char]
Explanation The user is attempting to configure an incorrect format string.
Recommended Action Enter a 32-character string using supported characters only.
Error Message%RADIUS-3-NOACCOUNTINGRESPONSE : Accounting message [chars] for session [chars] failed to receive Accounting Response.
Explanation Maximum number of retransmissions is exceeded. Thenetwork is not accessible or the RADIUS server is down.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show running-config 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%RADIUS-3-NOATTRLIST : No attribute-list passed through parser.
Explanation An internal error has occurred. The reason could be hardware or software. The error appears when no attribute list is passed through the parser.
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%RADIUS-3-NOHOSTNAME : Failed to retrieve my hostname.
Explanation Could not find the router's hostname. A hostname needs to be defined, since it determines the RADIUS profile we will retrieve.
Recommended Action Define a hostname on the router's config. Refer to the hostname configuration section of IOS documentation.
Error Message%RADIUS-4-NOPUBLICSERV : Warning: No servers werefound in the public server list.
Explanation The given server is not on the global public servers list. This is an internal consistency 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%RADIUS-4-NOSERV : Warning: Server [IP_address]:[dec],[dec] is not defined.
Explanation The given server is not globally defined.
Recommended Action Define the server. Refer to the server configuration section of IOS documentation.
Error Message%RADIUS-3-NOSERVERS : No Radius hosts configured or no valid server present in the server group [chars]
Explanation RADIUS is attempting to send a request, but there are no hosts configured to which the request is sent.
Recommended Action Configure a host with the radius-server command providing the IP address of the server. Refer to the radius-server host configuration section of IOS documentation.
Error Message%RADIUS-3-OVERRUN : Insufficient buffer space [dec] for string value.
Explanation This error occurs due to the insufficient memory allocated to the buffer. The condition could be caused by a software, less likely by a hardware. The traceback and process information is generated due to this condition.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Enter show tech-support 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%RADIUS-4-RADIUS_ALIVE : RADIUS server [IP_address]:[int],[int] is being marked alive.
Explanation A RADIUS server that previously was not responding has responded to a new request or the deadtimer has expired.
Recommended Action No action is required.
Error Message%RADIUS-4-RADIUS_DEAD : RADIUS server [IP_address]:[int],[int] is not responding.
Explanation The server might not be available to serve request. server has not responded to repeated requests.
Recommended Action Check for the connectivity to server. Check if the RADIUS server is still active. If this message recurs, copy the message exactly as it appears on the console or in the system log. Enter show running-config 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%RADIUS-6-RESETDEADSERVER : Group [chars]: Marked alive as Radius server [IP_address]:[dec],[dec] configured.
Explanation RADIUS server is now configured in the server group which was previously marked dead.
Recommended Action Informational message only. No action is required.
Error Message%RADIUS-3-SECRETDEFINEFAILED : Key definition ignored.
Explanation The user is attempting to store either a corrupted shared secret or memory allocation failed during secret definition. Any existing shared secret will be preserved.
Recommended Action Configure a proper secret. Refer to the shared secret configuration section for RADIUS servers in IOS documentation.
Error Message%RADIUS-6-SERVERALIVE : Group [chars]: Radius server [IP_address]:[dec],[dec] is responding again (previously dead).
Explanation A RADIUS server, which previously was dead, has started responding again.
Recommended Action Informational message only. No action is required.
Error Message%RADIUS-3-SERVERTYPEMISMATCH : Servers [IP_address] and [IP_address] in server group '[chars]' are of different types.
Explanation All the servers in a server group should either be of type standard or non-standard.
Recommended Action Enter show running-config command and enure all the RADIUS servers in the server group printed above are of the same type — either standard or non-standard.
Error Message%RADIUS-4-SERVREF : Warning: Server [IP_address]:[dec],[dec] is still referenced by server group.
Explanation The server being removed is still referenced by a server group. This message appears when server configuration is removed but in a server group it still exists.
Recommended Action De-reference the server from the server group as soon as possible. Refer to server group configuration section in IOS documentation.
Error Message%RADIUS-3-UNKNOWNAPI : Unknown API type [dec]
Explanation RADIUS code has been invoked using an unknown API type. This is the result of a bug in the RADIUS subsystem.
Recommended Action Check bug toolkit on Cisco web-site to look for a bug which has symptoms similar to the one occured. If there is no entry for the problem you faced, collect traceback and copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%RADIUS-3-ZEROATTRLEN : Radius attr [dec] len 0
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. 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.RADPROXY Messages
The following are RADIUS Proxy messages.
Error Message%RADPROXY-3-INIT : Initialisation failure, [chars]
Explanation An internal error occurred during RP initialization.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%RADPROXY-3-INVALID_FSM_EVENT : Received invalid RP event [chars] in state [chars]
Explanation An internal RP 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%RADPROXY-3-INVALID_FSM_STATE : Encountered an invalid RP state [dec] in [chars]
Explanation An internal RP 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%RADPROXY-3-MEMORY_LOW : Memory low in RP terminating session
Explanation System memory is running low.
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%RADPROXY-3-NULL_FSM_CONTEXT : Encountered a NULL RP context in [chars]
Explanation Encountered a NULL context in 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. 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%RADPROXY-3-PROTOCOL_VIOLATION : RP encountered fatal protocol violation
Explanation Unrecoverable protocol 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.RANDOM Messages
The following are utility messages.
Error Message%RANDOM-6-RANDOM : A pseudo-random number was generated twice in succession
Explanation A pseudo-random number generator produced the same number twice in succession.
Recommended Action Under normal circumstances a pseudo-random number generator will occasionally produce the same number twice in succession and this is not a problem. However if this message occurs frequently, the system should be manually reloaded. 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.RED Messages
The following are redundancy-related messages.
Error Message%RED-3-CHKPTADDCLIENT : Check Point Client [dec] Add Failed - [dec]
Explanation Check Point message Client failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%RED-3-CHKPTALLOC : Check Point Message Allocation Failed - [dec]
Explanation Check Point buffer allocation failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%RED-3-CHKPTGETDATAPTR : Check Point Get Data Pointer Failed
Explanation Check Point message 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. 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%RED-3-CHKPTINVALIDDATA : Check Point Client has invalid data
Explanation Check Point message has invalid data.
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%RED-3-CHKPTMSGCOPY : Check Point Message Copy Failed
Explanation Check Point message 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. 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%RED-3-CHKPTMSGSIZE : Check Point Message Size is Zero!
Explanation Check Point Message size is zero.
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%RED-3-CHKPTRIMRCSACTIVE : Check Point RIM RCS ACTIVE Failed
Explanation Check Point process RIM RCS active 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%RED-3-CHKPTSENDFAIL : Check Point Message Send - Unsuccessful delivery
Explanation Check Point message sent - Unsucessful delivery.
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%RED-3-CHKPTSENDMSG : Check Point Message Send Failed - [dec]
Explanation Check Point message send failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%RED-3-DATADECODE : Decode Data Descriptor for data type Failed
Explanation Decode Data Descriptor failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%RED-3-DATAENCODE : Encode Data Descriptor for data type [chars] Failed
Explanation Encode Data Descriptor failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%RED-5-REDCHANGE : EHSA Register changed Prev - [hex]h, Current - [hex]h
Explanation Peer RP sent change via EHSA Register.
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.RED_MODE Messages
The following are High-Availability redundancy mode messages.
Error Message%RED_MODE-3-CAPENTRY_REG : Red Mode Cap Entry ([dec]) for Entity ([dec]) Registration failed ([chars])
Explanation A capability entry could not be registered for the Red Mode ISSU.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu capability entries 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%RED_MODE-3-CAPGROUP_REG : Red Mode Cap Group ([dec]) for Entity ([dec]) Registration failed ([chars])
Explanation A capability group could not be registered for the Red Mode ISSU.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show capability groups 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 %RED_MODE-3-CAP_REG: Red Mode cap reg failed: reason [dec]
Explanation The capabilities of the Red Mode ISSU could not be registered.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu capability <arguments> 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%RED_MODE-3-CAPTYPE_REG : Red Mode Cap Type for Entity ([dec]) Registration failed ([chars])
Explanation A capability type could not be registered for the Red Mode ISSU.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu capability types 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%RED_MODE-3-CLIENT_REG : Red Mode Client ([dec]) Registration failed ([chars])
Explanation The Red Mode ISSU client could not be registered.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu clients 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%RED_MODE-3-CLIENT_REG_FAILED : Red Mode ISSU client ([dec]) Client registration failed. [chars]
Explanation The Red Mode ISSU client could not be registered during system initialization.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu clients 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%RED_MODE-3-DELAYED_REGISTER : Delayed registration could not be completed succesfully, Operand = [dec]
Explanation The delayed registration operation for the RF-proxy clients could not complete successfully.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu clients 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%RED_MODE-3-ENTITY_REG : Red Mode Entity ([dec]) Registration failed ([chars])
Explanation The Red Mode ISSU entity could not be registered.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu entities 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%RED_MODE-3-GET_BUFFER : Red Mode ISSU session ([dec]) failed to get buffer
Explanation Red Mode ISSU failed to get a buffer.
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%RED_MODE-3-IPC_AGENT : [chars] [ [chars] ]
Explanation There has been a failure in the redundancy mode IPC agent.
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%RED_MODE-3-ISSU_NEGOTIATION : [chars] [ [chars] ]
Explanation There has been a failure in the redundancy mode client.
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%RED_MODE-3-MSG_DATAPTR : Red Mode Client ([dec]) get msg dataptr failed. Error = [dec]
Explanation The redundancy mode ISSU client could not obtain a message data pointer.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu fsm 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%RED_MODE-3-MSGGROUP_REG : Red Mode Msg Group ([dec]) for Entity ([dec]) Registration failed ([chars])
Explanation The message group for the redundancy mode ISSU could not be registered.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu message groups 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%RED_MODE-3-MSG_MTU : Red Mode Client ([dec]) get msg mtu failed. Error = [dec]
Explanation The redundancy mode ISSU client could not obtain message size.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu fsm 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%RED_MODE-3-MSG_REG : Red Mode msg reg failed: reason [dec]
Explanation Messages for the redundancy mode ISSU could not be registered.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu message <arguments> 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%RED_MODE-3-MSG_SEND : Red Mode ISSU client for session ([dec]) failed to send message. Error Code = [chars]
Explanation The redundancy mode ISSU client could not send a negotiation message to a peer.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu fsm 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%RED_MODE-3-MSGTYPE_REG : Red Mode Msg Type for Entity ([dec]) Registration failed ([chars])
Explanation The message type for the redundancy mode ISSU could not be registered.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu message types 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%RED_MODE-3-NO_DEREGISTER : Could not deregister plugin for redundancy mode [chars]
Explanation At system initialisation the plugin that describes the capabilities of this redundancy mode could not be deregistered with the redundancy mode client.
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%RED_MODE-3-RED_MODE_MSG_NOT_OK : Red Mode ISSU msg type ([dec]) is not ok
Explanation The redundancy mode ISSU message type has not negotiated correctly.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show message types <Client_ID> 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%RED_MODE-3-RED_MODE_START_NEGO_FAILED : Red Mode ISSU start nego session failed ([chars])
Explanation The redundancy mode ISSU could not start its negotiation process.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu fsm 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%RED_MODE-3-RED_MODE_XFROM_FAIL : Red Mode ISSU [chars] transformation failed ([chars])
Explanation The transformation operation for the redundancy mode ISSU message has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu fsm and show issu sessions commands 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%RED_MODE-3-SELECT_MODE : The mode change to [dec] was unsuccessful rc = [dec], force = [dec], caller = [dec]
Explanation The specified mode change operation did not complete successfully.
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%RED_MODE-3-SESSION_REG : Red Mode session for Entity ([dec]) Registration failed ([chars])
Explanation The redundancy mode ISSU session could not be registered.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu sessions 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