Feedback
Table Of Contents
Regen_MAINBOARD_ASYNC_PQUICC-3
SIP600_PARSING_ENGINE Messages
RADIUS Messages
This section contains RADIUS messages.
RADIUS-3
Error Message %RADIUS-3-AIDDEFINEFAILED: a_id definition ignored.Explanation An attempt to store a corrupted authority ID (a_id) failed or memory allocation failed during authority ID definition. Any existing authority ID will be preserved.
Recommended Action Configure a proper authority ID.
Error Message %RADIUS-3-CANNOT_OPEN_SOCKET: Cannot open UDP socket for service %sExplanation The router is unable to open a socket for UDP communications by the indicated service.
Recommended Action Check your configuration to make sure that no other services are using the same port.
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 the RADIUS subsystem is missing, which indicates 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %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 There was no response from the RADIUS server, and the maximum number of retransmissions has been exceeded. The network or the RADIUS server may be down.
Recommended Action Check the network connectivity to the RADIUS servers and check that the servers are running.
Error Message %RADIUS-3-NOATTRLIST: No attribute-list passed through parser.Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %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 be of either type: standard or nonstandard.
Recommended Action Check the running configuration and verify that all the radius servers in the specified server group are of the same type: either standard or nonstandard.
Error Message %RADIUS-3-SOURCEPORTALLOCERROR: Warning: Unable to allocate port [dec]Explanation The system was unable to allocate the port specified in the message. The system will not have the full range of source ports.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RADIUS-3-UNKNOWNAPI: Unknown API type %dExplanation The RADIUS process has been invoked using an unknown application program interface (API) type. This condition is the result of a fault in the RADIUS subsystem.
Recommended Action Collect traceback and contact your technical support representative.
Error Message %RADIUS-3-ZEROATTRLEN: Radius attr [dec] len 0Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
RADIUS-4
Error Message %RADIUS-4-UNAVAILABLE: RADIUS server %i:%u,%u has returned.Explanation A RADIUS server that previously was not responding has responded to a new request
Recommended Action LOG_STD_NO_ACTION
Error Message %RADIUS-4-UNAVAILABLE: RADIUS server %i:%u,%u is not responding.Explanation A RADIUS server has not responded to repeated requests.
Recommended Action Check to see if the RADIUS server is still active.
Error Message %RADIUS-4-UNAVAILABLE: Unable to process attribute list.Explanation The attribute list is syntactically incorrect.
Recommended Action Please specify the attribute list as a comma-delimited string of integers between 1 and 255.
Error Message %RADIUS-4-UNAVAILABLE: Warning: Attribute list %s is not defined.Explanation The given attribute list is not defined.
Recommended Action Please define the attribute list as soon as possible.
Error Message %RADIUS-4-UNAVAILABLE: Warning: No servers werefound in the public server list.Explanation The given server is not on the global public serverslist. 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RADIUS-4-UNAVAILABLE: Warning: Server %i:%d,%d is not defined.Explanation The given server is not on the master-list, and should be defined, or unexpected things might happen.
Recommended Action Please define the server on the appropriate master-list as soon as possible.
Error Message %RADIUS-4-UNAVAILABLE: Warning: Server %i:%d,%d is still referenced by server group.Explanation The server being removed is still referenced by a server group
Recommended Action Please dereference the server from the server group as soon as possible.
RADIUS-6
Error Message %RADIUS-6-UNAVAILABLE: Group %s: Marked alive as Radius server %i:%d,%d configured.Explanation Radius server is configured in the server group which was previously marked dead.
Recommended Action No action required.
Error Message %RADIUS-6-UNAVAILABLE: Group %s: Radius server %i:%d,%d is responding again (previously dead).Explanation A radius server, which previously was dead, has started responding again.
Recommended Action No action required.
Error Message %RADIUS-6-UNAVAILABLE: Retrieving IP-Pools via user %sExplanation Getting initial IP-Pool definitions from radius, using the given user's profile
Recommended Action No action required.
Error Message %RADIUS-6-UNAVAILABLE: Retrieving static routes in user %sExplanation Getting initial static routes from radius, using the given user's profile
Recommended Action No action required.
Error Message %RADIUS-6-UNAVAILABLE: Saving config with new acct ident in nvram.Explanation Saving an accounting ident in nvram.
Recommended Action No action required.
RADIX-2
Error Message %RADIX-2-UNAVAILABLE: No memory for radix initialization: %sExplanation The system ran out of memory during initialization. This should only occur if an image is too large for the existing dynamic memory.
Recommended Action Use a smaller subset image or upgrade hardware.
RADIX-3
Error Message %RADIX-3-UNAVAILABLE: Error adding mask entry, %sExplanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %RADIX-3-UNAVAILABLE: Error deleting trie entry, %sExplanation A software programming error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %RADIX-3-UNAVAILABLE: Invalid pointer to head of tree, 0x%xExplanation A software programming error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %RADIX-3-UNAVAILABLE: No memory available %sExplanation The system is out of memory.
Recommended Action Try one of these actions to correct the problem: Reduce the number of routes accepted by this router. Upgrade hardware. Use a smaller subset image on run-from-RAM platforms.
RADIX-4
Error Message %RADIX-4-UNAVAILABLE: Orphaned mask %#x, refcount=%d at %#x, next=%#xExplanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
RAIKO-3
Error Message %RAIKO-3-UNAVAILABLE: Slot %d: Mgmt int. handler's registration routine was passed NULL callback address(es) -- enabler=0x%x, handler=0x%x; registering party's callback details ignoredExplanation A Mgmt-level interrupt handler has registered incorrectly with device-independent code; a software fix is required
Error Message %RAIKO-3-UNAVAILABLE: Slot %d: a Mgmt interrupt occured but was not processed by a device-specific handler; following sources masked out: %sExplanation A source of Mgmt-level interrupts does not have a handler registered for it; a software fix is needed to install the proper handler
Error Message %RAIKO-3-UNAVAILABLE: Slot %d: id of DFC%u is invalid (zero); cookie probably unprogrammedExplanation When the cookie on the specified DFC was read for the id of the DFCan invalid value of 0 was returned. This suggests the DFC's cookiehas not been programmed properly.
Error Message %RAIKO-3-UNAVAILABLE: Slot %d: installation of Mgmt int. handler apparently failed -- routine currently installed at IOS Level %d is 0x%xExplanation Tried to install required Mgmt interrupt handler at given IOS level but, upon checking, another handler was found there
Error Message %RAIKO-3-UNAVAILABLE: Slot %d: installation of desired Mgmt interrupt handler failed -- no routine is currently installed at IOS Level %dExplanation Tried to install required Mgmt interrupt handler at given IOS level but, upon checking, no handler was installed whatsoever
Error Message %RAIKO-3-UNAVAILABLE: Slot %d: no free Mgmt int. handler callback entries (all %d in use); registering party's callback details droppedExplanation More Mgmt interrupt handlers have registered than can be catered for; a software fix is required
Error Message %RAIKO-3-UNAVAILABLE: Slot %d:DFC %d ERROR %sExplanation A PCI error has occured trying to access a DFC The DFC has been shut down
Recommended Action Replace Hardware
RANDOM Messages
This section contains utility messages.
RANDOM-6
Error Message %RANDOM-6-RANDOM: A pseudo-random number was generated twice in successionExplanation 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, which is not a problem. However, if this message occurs frequently, the system should be manually reloaded. If the message is persistent across reloads, copy the error message exactly as it appears, and report it to your Cisco technical support representative.
RASP16 Messages
This section contains interface multiplexer ASIC messages.
Error Message %RASP16-5-NULL_RASP16_OBJECT: The Interface Multiplexer device object pointer is set to NULL.Explanation The memory location of the interface multiplexer device object is invalid. The interface multiplexer ASIC operation is disabled and the device interrupt is now masked.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RASP16-5-RASP_INIT_FAILURE: The Interface Multiplexer ASIC initialization failed.Explanation The interface multiplexer ASIC could not be initialized. As a result, this device is not operational and has been 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
RBM Messages
This section contains Role-based Access Control Manager (RBM) messages.
RBM-0
Error Message %RBM-0-RBM_EMERG: %sExplanation An error occurred in the Role-based Access Control Manager (RBM).
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
RBM-1
Error Message %RBM-1-RBM_ALERT: %sExplanation An error occurred in the Role-Based Manager (RBM).
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
RBM-2
Error Message %RBM-2-RBM_CRIT: %sExplanation An error occurred in the Role-based Access Control Manager (RBM).
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
RBM-3
Error Message %RBM-3-RBM_ERR: %sExplanation An error occurred in the Role-based Access Control Manager (RBM).
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RBM-3-RBM_PARSE_ACE: Could not parse command for adding ACE '[chars]' to [chars] Role-Based Access List '[chars]'Explanation An error occured while attempting to add an ACE to a Role-Based Access List. The ACE syntax is most likely incompatible with the type of RBACL.
Recommended Action Verify the syntax of the ACEs of the RBACL in ACS and the IP protocol versions the RBACL applies to. RBACL ACE syntax could be verified by manually configuring IP/IPv6 RBACL on the system within (config-rb-acl)/(config-ipv6rb-acl) configuration mode respectively.
Error Message %RBM-3-RBM_PARSE_RBACL: Could not parse command for creating [chars] Role-Based Access List '[chars]' '[chars]'Explanation An error occured while attempting to create Role-Based Access List.
Recommended Action This error could occur when TrustSec attempts to install RBACL it has acquired from ACS while configuration mode is locked exclusively. TrustSec will retry this operation and should eventually succeed once configuration mode is no longer locked. If the error occurs when the configuration mode is not locked or if the RBACL does not get installed after the configuration mode lock is released.
RBM-4
Error Message %RBM-4-RBM_WARNING: %sExplanation An error occurred in the Role-based Access Control Manager (RBM).
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
RBM-5
Error Message %RBM-5-RBM_NOTICE: %sExplanation This is a notice message from the Role-based Access Control Manager (RBM).
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
RBM-6
Error Message %RBM-6-RBM_INFO: %sExplanation This is an informational message from the Role-based Access Control Manager (RBM).
Recommended Action No action is required.
RBM-7
Error Message %RBM-7-RBM_ASSERT: Assertion Failure ( %s @%s:%d ) : %sExplanation An error occurred in the Role-based Access Control Manager (RBM).
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
RCMD-4
Error Message %RCMD-4-UNAVAILABLE: DNS hostname/ip address mismatch. %s unknown to DNSExplanation The IP address for an incoming rcmd request is not registered with DNS.
Recommended Action Add the IP address to DNS.
Error Message %RCMD-4-UNAVAILABLE: Remote copy from %s at %s deniedExplanation An attempt was made to connect to a router through RCP, but the router was not configured as an RCP server.
Recommended Action Configure an RCP server.
Error Message %RCMD-4-UNAVAILABLE: Remote shell from %s at %s deniedExplanation An attempt was made to connect to a router through rsh, but the router was not configured as an rsh server.
Recommended Action Configure an rsh server.
RED_MODE Messages
This section contains high availability redundancy mode messages.
RED_MODE-3
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 redundancy 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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %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 redundancy 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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RED_MODE-3-CAP_REG: Red Mode cap reg failed: reason [dec]Explanation The capabilities of 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 capability arguments command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %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 redundancy 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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RED_MODE-3-CLIENT_REG: Red Mode Client ([dec]) Registration failed ([chars])Explanation The redundancy 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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RED_MODE-3-CLIENT_REG_FAILED: Red Mode ISSU client ([dec]) Client registration failed. [chars]Explanation The redundancy 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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %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. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RED_MODE-3-ENTITY_REG: Red Mode Entity ([dec]) Registration failed ([chars])Explanation The redundancy 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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RED_MODE-3-GET_BUFFER: Red Mode ISSU session ([dec]) failed to get bufferExplanation The redundancy mode ISSU session was unable to get a buffer.
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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RED_MODE-3-ISSU_BASE_CLIENT_INCOMP: One or more ISSU base clients are incompatible, fallback to RPRExplanation An incompatible ISSU base client caused the redundancy mode to revert to route processor redundancy (RPR) mode.
Recommended Action Check the console log for the name and ID of the incompatible ISSU base clients.
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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RED_MODE-3-ISSU_RESET_PEER_IMAGE_COMP: Failed to reset peer image to be compatibleExplanation The redundancy process was unable to reset the peer image to be compatible after the standby device came back up in RPR mode. This message is usually seen in conjunction with an ISSU module error message.
Recommended Action Examine the associated ISSU message for the cause of the failure and the recommended action.
Error Message %RED_MODE-3-ISSU_SET_BASE_CLIENT_INCOMP: Failed to set base client incompatibilityExplanation The redundancy process was unable to set the base client incompatibility.
Recommended Action Check the console log for the name and ID of the incompatible ISSU base clients.
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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %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 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 message groups command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RED_MODE-3-MSG_MTU: Red Mode Client ([dec]) get msg mtu failed. Error = [dec]Explanation The redundancy mode ISSU client could not obtain the 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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RED_MODE-3-MSGTYPE_REG: Red Mode Msg Type for Entity ([dec]) Registration failed ([chars])Explanation The message type for the redundancy 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 message types command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RED_MODE-3-NO_DEREGISTER: Could not deregister plugin for redundancy mode [chars]Explanation At system initialization 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RED_MODE-3-RED_MODE_MSG_NOT_OK: Red Mode ISSU msg type ([dec]) is not okExplanation 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 issu message types clientID command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %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 issue sessions command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %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 error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RED_MODE-3-SESSION_UNREG: Red Mode session ([dec]) Un-Registration failed ([chars])Explanation The redundancy mode ISSU session could not be unregistered.
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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
REDUNDANCY Messages
This section contains high availability redundancy messages.
REDUNDANCY-3
Error Message %REDUNDANCY-3-UNAVAILABLE: %s %sExplanation An Interprocess Communication (IPC) error occurred. The details about what was attempted and what went wrong will be printed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %REDUNDANCY-3-UNAVAILABLE: %sExplanation A REDUNDANCY Alarm assertions error occurred. The details about what was attempted and what went wrong will be printed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %REDUNDANCY-3-UNAVAILABLE: %sExplanation A REDUNDANCY Finite State Machine (FSM) error occurred. The details about what was attempted and what went wrong will be printed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %REDUNDANCY-3-UNAVAILABLE: %sExplanation A REDUNDANCY Peer Monitor error occurred. The details about what was attempted and what went wrong will be printed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %REDUNDANCY-3-UNAVAILABLE: %sExplanation A REDUNDANCY config sync error occurred. The details about what was attempted and what went wrong will be printed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %REDUNDANCY-3-UNAVAILABLE: %sExplanation A REDUNDANCY error occurred. The details about what was attempted and what went wrong will be printed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %REDUNDANCY-3-UNAVAILABLE: %s failed with error code [ %s ]Explanation An ISSU related REDUNDANCY error occurred. The details about what was attempted and what went wrong will be printed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %REDUNDANCY-3-UNAVAILABLE: RP switchover (%s)Explanation A REDUNDANCY switchover has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %REDUNDANCY-3-UNAVAILABLE: Standby processor fault (%s)Explanation The standby processor is no longer available.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %REDUNDANCY-3-UNAVAILABLE: WARNING, nonsymetrical configuration: Active has %dK Standby has %dKExplanation The redundant RPs have different memory configurations.
Recommended Action The configuation is allowed but discouraged.
REDUNDANCY-4
Error Message %REDUNDANCY-4-PEER_DID_NOT_RESPOND: Resetting peer [chars] because it did not respond to verification of HA role.Explanation The platform uses high availability (HA) hardware lines to perform HA role negotiation during the system boot time. The standby controller card verifies its role as the standby with the active controller card through the MBUS. If the active controller card does not respond, it is reset as it is either nonresponsive (hung) or is running an earlier version of Cisco IOS software.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %REDUNDANCY-4-RELOADING_STANDBY: Reloading the Standby [chars]Explanation The active system has sent a reload IPC request to the standby peer. If the reload is not successful, the standby peer will be power cycled rather than 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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
REDUNDANCY-5
Error Message %REDUNDANCY-5-UNAVAILABLE: %s (%s%s(%d))Explanation A REDUNDANCY Peer Monitor event occurred and reported. The report should help to find out the reason for a switch-over.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
REDUNDANCY-6
Error Message %REDUNDANCY-6-STANDBY_HAS_RELOADED: The Standby [chars] has reloaded; reason: [chars]Explanation The standby peer reloaded itself to correct a configuration mismatch between the active system and the standby peer. The standby peer detected that it is missing the configuration for a line card. This situation probably occurred because the standby peer was reloaded before the new card was inserted.
Recommended Action No action is required.
Error Message %REDUNDANCY-6-SWITCHOVERTIME: Time taken to switchover = [dec] millisecondsExplanation This message displays the time elapsed for the standby peer to become active following a failure of the existing active system.
Recommended Action No action is required.
REDUNDANCY_UTILS Messages
This section contains high availability redundancy utilities messages.
Error Message %REDUNDANCY_UTILS-3-INVALID_UNIT_DESIGNATION: An invalid redundancy designation ([chars]) has been detected.Explanation The redundancy utility assigns each system a unit designation of either active unit, standby unit, or other unit. This designation was found to be invalid in the run-time module associated with the system traceback message. This condition most likely occurred because of a software error. The message text provides more information on the specific cause of the error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
REGISTRY Messages
This section contains registry-related (REGISTRY) messages.
REGISTRY-2
Error Message %REGISTRY-2-REG_FLAG_DEADLOCK: Registry call to [chars] timed out due to deadlockExplanation When a remote registry is not serviced within 25 seconds, the remote process (and presumably the entire system) is deadlocked. This message is printed when the deadlock is broken by a 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %REGISTRY-2-REG_PARSE_ERROR: [chars]: Could not parse notification [chars] : error/no. of items = [dec]Explanation The registry library is unable to parse a notification that was received from a name server. This condition could exist for several reasons:
- There is a bug in the sscanf function.
- The notification block is corrupted.
- The pathname published to the name server is invalid.
This issue is serious and affects interprocess communications.Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
REGISTRY-3
Error Message %REGISTRY-3-FASTCASE_OUT_OF_BOUNDS: Attempt made in [chars] to register with out of bounds key.Explanation In FASTCASE registry, the key must be smaller than the size specified when the registry was created. An attempt was made to register with a key that is out of bounds.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %REGISTRY-3-REG_FLAG_ERR: Invalid combination of registry flag and scheduler control : [chars]Explanation Process blocking has been disabled using either the raise_interrupt_level or the assign_blocking_disabled process. As a result of this action, a remote registry that contains the reg_flag_data_safe or reg_flag_peer flag has been invoked.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %REGISTRY-3-REG_SUSPEND: Registry of type SUSPEND called when suspends are not allowed.Explanation Process blocking has been disabled using either the raise_interrupt_level or the assign_blocking_disabled process. As a result of this action, a remote registry of the suspend type has been invoked.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %REGISTRY-3-REG_XDR: [chars]Explanation An error occurred while processing a parameter to a remote (interprocess) registry call.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %REGISTRY-3-SEQ_LIST_OVERWRITE: Attempt made to overwrite a set sequence function (%s)Explanation A single function can be set as a callback for a specified sequence number for a sequenced list registry. An attempt to set a new callback failed because a callback function has already been set for this sequence number.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
REMOTE_OIR_ISSU Messages
This sections contains remote online insertion and removal (OIR) in-service software upgrade (ISSU) messages.
REMOTE_OIR_ISSU-3
Error Message %REMOTE_OIR_ISSU-3-BUFFER: Cat6K Remote OIR ISSU client failed to a buffer for message, error %dExplanation The remote OIR ISSU client failed to get a buffer for building a negotiation message. As a result, the client cannot send a negotiation message and the standby unit cannot be brought up.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs.
Error Message %REMOTE_OIR_ISSU-3-CAPABILITY: Cat6K Remote OIR ISSU client %sExplanation The remote OIR ISSU client detected an error during capability negotiation. As a result, there is a mismatch in the client capability between the active and standby unit.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs.
Error Message %REMOTE_OIR_ISSU-3-INIT: Cat6K Remote OIR ISSU client initialization failed at %s, error %sExplanation The remote OIR ISSU client could not be initialized. This condition will cause a catastrophic failure when an ISSU upgrade or downgrade is performed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %REMOTE_OIR_ISSU-3-MSG_NOT_OK: Cat6K Remote OIR ISSU client message %d is not compatibleExplanation The remote OIR ISSU client received an incompatible message from the peer unit. The message cannot be processed by this unit.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs.
Error Message %REMOTE_OIR_ISSU-3-MSG_SIZE: Cat6K Remote OIR ISSU client failed to get the message size for message %dExplanation The remote OIR ISSU client was unable to calculate the message size for the message specified. The client will be unable to send the message to the standby unit.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs.
Error Message %REMOTE_OIR_ISSU-3-POLICY: Cat6K Remote OIR ISSU client message type %d is %sExplanation The remote OIR ISSU client received a message type that it does not support. A policy is applied to make the session 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show issu session commands and your pertinent troubleshooting logs.
Error Message %REMOTE_OIR_ISSU-3-SEND_FAILED: Cat6K Remote OIR ISSU client failed to send a negotiation message, error %dExplanation The remote OIR ISSU client could not send a session negotiation message to the peer. As a result, the standby unit cannot be brought up.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs.
Error Message %REMOTE_OIR_ISSU-3-SESSION: Cat6K Remote OIR ISSU client %sExplanation The remote OIR ISSU client detected an error during a session negotiation with the peer unit. As a result, the standby unit cannot be brought up.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs.
Error Message %REMOTE_OIR_ISSU-3-TRANSFORM: Cat6K Remote OIR ISSU client %s transform failed, error %sExplanation The remote OIR ISSU client could not transform the message. If the transmit transformation failed, the checkpoint message cannot be sent to the standby unit. If the receive transformation failed, the checkpoint message cannot be applied on the standby unit. In either case, the OIR state of the bay will not be identical with the active unit.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs.
REP Messages
This sections contains Resilient Ethernet Protocol (REP) messages.
REP-4
Error Message %REP-4-LINKSTATUS: %s (segment %d) is %sExplanation The Resilient Ethernet Protocol (REP) link status has changed. If the status changed to nonoperational, a reason is displayed.
Recommended Action No action is required.
REP-5
Error Message %REP-5-PREEMPTIONFAIL: can not perform preemption on segment %d due to %sExplanation A Resilient Ethernet Protocol (REP) preempt operation failed. The failure could be caused by specifying an invalid port ID or neighbor number with the rep preempt block port command or by configuring the rep preempt block port preferred command while no REP port is configured with a preferred flag.
Recommended Action Correct the configuration and run REP manual preemption on the primary edge port by entering the rep preempt segment command.
REPP-5
Error Message %REPP-5-UNAVAILABLE: Connected to serverExplanation REPP Layer connected to REPP server
Recommended Action LOG_STD_NO_ACTION
Error Message %REPP-5-UNAVAILABLE: Disconnected from serverExplanation REPP Layer dis-connected from REPP server
Recommended Action LOG_STD_NO_ACTION
REP_ISSU Messages
This sections contains Resilient Ethernet Protocol (REP) in-service software upgrade (ISSU) messages.
REP_ISSU-3
Error Message %REP_ISSU-3-BUFFER: REP ISSU client failed to get buffer for message, error %dExplanation The Resilient Ethernet Protocol (REP) ISSU client was unable to get buffer space for building a negotiation message. As a result, it cannot send the negotiation message to the standby unit and the standby unit cannot be brought up.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs.
Error Message %REP_ISSU-3-CAPABILITY: REP ISSU client %sExplanation The REP ISSU client detected an error during capability negotiation. As a result, there is a mismatch in the client capability between the active and standby unit.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs.
Error Message %REP_ISSU-3-INIT: REP ISSU client initialization failed at %s, error %sExplanation The REP ISSU client could not be initialized. This condition will cause a catastrophic failure when an ISSU upgrade or downgrade is performed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %REP_ISSU-3-MSG_NOT_OK: REP ISSU client message %d is not compatibleExplanation The REP ISSU client received an incompatible message from the peer unit. The message cannot be processed by this unit.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs.
Error Message %REP_ISSU-3-MSG_SIZE: REP ISSU client failed to get the message size for message %dExplanation The REP ISSU client was unable to calculate the message size for the message specified. The REP ISSU client will be unable to send the message to the standby unit.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs.
Error Message %REP_ISSU-3-POLICY: REP ISSU client message type %d is %sExplanation The REP ISSU client received a message type that it does not support. A policy is applied to make the session 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show issu session commands and your pertinent troubleshooting logs.
Error Message %REP_ISSU-3-SEND_FAILED: REP ISSU client failed to send a negotiation message, error %dExplanation The REP ISSU client could not send a session negotiation message to the peer. As a result, the standby unit cannot be brought up.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs.
Error Message %REP_ISSU-3-SESSION: REP ISSU client %sExplanation The REP ISSU client detected an error during a session negotiation with the peer unit. As a result, the standby unit cannot be brought up.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs.
Error Message %REP_ISSU-3-SESSION_UNREGISTRY: REP ISSU client failed to unregister session information. Error: %d (%s)Explanation The REP ISSU client was unable to unregister session information.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs.
Error Message %REP_ISSU-3-TRANSFORM: REP ISSU client %s transform failed, error %sExplanation The REP ISSU client could not transform the message. If the transmit transformation failed, the checkpoint message cannot be sent to the standby unit. If the receive transformation failed, the checkpoint message cannot be applied on the standby unit. In either case, the port manager state will not be identical with the active unit.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs.
RESETMGR Messages
This sections contains reset manager messages.
RESETMGR-3
Error Message %RESETMGR-3-NOMEM: Failed to allocate memory to add ID (%d) to tableExplanation The reset manager was unable to allocate memory to add the unique ID and process name to its table. If this process is restarted on the active system, the standby system might not be reset due to this 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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RESETMGR-3-RESET: Reset Manager has reset the system due to '%s' process restartExplanation The standby system is being forced to reset by the reset manager. The reset manager stores a set of IDs, each of which uniquely identifies a process on the system. If one of these monitored processes is restarted, the standby unit will be reset so that the versioning infrastructure can renegotiate. This is not a software fault.
Recommended Action No action is required.
Error Message %RESETMGR-3-RESET_UNKNOWN: A restarted process could not be identified by its Job ID, the Reset Manager has reset the Standby system.Explanation The reset manager stores a set of IDs, each of which uniquely identifies a process on the system. A process was restarted but it could not be uniquely identified by its job ID. Because it cannot be determined whether the restarted process was being monitored by the reset manager, the standby system is being reset. This is probably due to a software fault on the system.
Recommended Action No action is required.
Error Message %RESETMGR-3-SYSMGR_JOBID_LOOKUP: Failed to get the job ID of the Reset Manger (IOS blob) from SysMgrExplanation The reset manager was unable to get its job ID from the system manager. The reset manager cannot function without this information and will suspend any further initialization.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
RESETMGR-4
Error Message %RESETMGR-4-SYSMGR_PROCNAME_LOOKUP: Failed to lookup process name from SysMgr, job ID = %dExplanation The reset manager was unable to get the name of the process with the specified job ID from the system manager. Although this is a system manager error, the system can continue to operate normally because the process name is used only for reference purposes.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
RESOURCE_MON-1
Error Message %RESOURCE_MON-1-UNAVAILABLE: %sExplanation The specific message text is supplied by the Resource Monitor software. This indicates an initialization failure. When this occurs, the Resource Monitor subsystem is not operational.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RESOURCE_MON-1-UNAVAILABLE: %sExplanation The specific message text is supplied by the Resource Monitor software. This indicates that internal data was corrupted due to a 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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
RF Messages
This sections contains redundancy facility (RF) messages.
RF-1
Error Message %RF-1-UNAVAILABLE: %sExplanation An automatic switch of activity occurred when it had been 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
RF-3
Error Message %RF-3-CANNOT_SWITCH: Cannot switchover; the peer Route Processor (RP) is not availableExplanation Cannot initiate switchover. The peer RP is not available.
Recommended Action This is an informational message only. No action is required.
Error Message %RF-3-CANT_GET_VERSION: Cannot get version info from peer Route Processor (RP); the RP software is incompatable.Explanation The standby RP cannot get version information from the peer RP. The likely cause is incompatible software.
Recommended Action Ensure that the same software image is running on both RPs.
Error Message %RF-3-FAILED_SET_RED_MODE: ACTIVE failed to set redundancy mode. STANDBY has selected mode but unable to get confirmation from ACTIVE.Explanation Under normal conditions, the standby RP selects the redundancy mode and sends its decision to the active RP. The active RP uses it to determine the system mode and returns the final decision on the mode to the standby RP. This system message indicates that the exchange has failed, and the standby RP does not have the right redundancy mode to proceed.
Recommended Action Allow the standby RP to reset once. If the problem persists, verify that all modules are working properly.
Error Message %RF-3-NEGOTIATED_ROLE_MISMATCH: Negotiated Role mismatch; The Route Processor (RP) believes it should be ACTIVE while the System Processor (SP) believes the RP should be STANDBY... or vice versa.Explanation The RP negotiates its role (active or standby) at boot time. If the other RP is running an image that does not contain role negotiation code, then the role that is negotiated may not be valid. When this occurs, the RP detecting a mismatch between the role specified by the SP and the role negotiated will be rebooted.
Recommended Action Ensure that the same software image is running on both RPs. Make sure that neither RP is running the bootloader image.
Error Message %RF-3-NON_HA_SWITCHOVER: The SP switchover was NOT stateful. To support SSO on the RP, the SP must be configured with HA enabled.Explanation The switch processor switchover that occurred was not stateful. Stateful switchover (SSO) mode on the route processor requires the switch processor to run with high availability enabled to ensure that appropriate state is synchronized between the switch processors and that there is sufficient state information on the new active switch processor to support the switchover of the route processor while in stateful switchover mode. Because there is insufficient state to support a route processor switchover in stateful switchover mode, the recovery is to reset the route processor and reboot it.
Recommended Action Configure the SP to enable HA. If HA is enabled, it is possible that resource exhaustion (such as memory) might have caused this non-HA switchover. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RF-3-NOTIF_TID: Notification timer extended for the wrong client, cur-client=%d, req-client=%dExplanation The current redundancy facility (RF) client attempted to extend the RF notification timer using a client ID other than its own. This is an internal software error. The message text on the console or in the system log contains error details such as the current client ID number and the requested client ID number.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show redundancy history commands and your pertinent troubleshooting logs.
Error Message %RF-3-PEER_RP_RELOAD: The peer Route Processor (RP) is being reset because [chars]Explanation This message provides the reason that the peer RP reset. The peer RP resets in an attempt to recover from an indeterminate state.
Recommended Action If the condition persists after the reset, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RF-3-VERSION_MISMATCH: Version Info mismatch; Not running same version of software on each Route Processor (RP). Cannot run in SSO mode; will go to RPR mode instead.Explanation Each RP must be running the same version of software. The version check indicates that there is a version mismatch. As a result, the RPs cannot run in SSO (hot-standby) mode and operation will regress to RPR mode.
Recommended Action Ensure that both RPs are running the same software image.
Error Message %RF-3-WAKEUP_STANDBY_NOT_SEEN: Active-Standby RP Handshake Error. The Standby RP did not receive a WAKEUP_STANDBY message from the Active RP during the early initialization phase on the Standby RP.Explanation As part of the early initialization phase, the standby RP requests that the active RP notify it when the active RP is ready to support the standby RP. The active RP has failed to wake the standby RP. The active RP may have failed during the standby RP's early initialization phase or some other error has prevented the active RP from completing this handshake.
Recommended Action The standby RP will be restarted. If the problem persists, restart the system.
RF-4
Error Message %RF-4-MEMORY_SIZE_MISMATCH: Memory Size mismatch: The redundant Route Processors have different memory configurations. To support the High Availability feature, it is recommended that both RPs have the same memory configurations.Explanation To support the high availability feature, it is recommended that both redundant route processors have the same memory configuration.
Recommended Action Install the same amount of memory on both RPs.
RF-5
Error Message %RF-5-RF_RELOAD: %s. Reason: %sExplanation The current redundancy facility (RF) has invoked a reload.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show redundancy history reload commands and your pertinent troubleshooting logs.
Error Message %RF-5-RF_TERMINAL_STATE: Terminal state reached for (%s)Explanation The current redundancy facility (RF) has reached a terminal state for the operating mode.
Recommended Action This is a notification message only. No action is required.
Error Message %RF-5-SEND_FAIL: RF client progression send failure for reason (%s)Explanation The current redundancy facility (RF) failed to send a client progression to the standby 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show redundancy history commands and your pertinent troubleshooting logs.
RF-6
Error Message %RF-6-CONS_MSG: Console Message from [chars] RP: [chars]Explanation This message is a console message from the peer RP.
Recommended Action This is an informational message only. No action is required.
Error Message %RF-6-NEGOTIATED_RED_MODE: Negotiated Redundancy MODE is [chars]Explanation The negotiated redundancy mode may be either SSO or RPR.
Recommended Action This is an informational message only. No action is required.
Error Message %RF-6-STANDBY_READY: The Standby RP has reached HOT-STANDBY state and is now ready for stateful switchover.Explanation The standby RP has reached the hot-standby state and is now ready to take over operation in the event that the active RP should fail.
Recommended Action No action is required.
RF-7
Error Message %RF-7-KPA_WARN: RF KPA messages have not been heard for [dec] secondsExplanation RF keepalive messages have not been sent from the peer. This message is posted after every third KPA timer expiry.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
RFPROXY-2
Error Message %RFPROXY-2-UNAVAILABLE: Initialization failedExplanation The RF Proxy subsystem failed during its initialization
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RFPROXY-2-UNAVAILABLE: No memory availableExplanation The RF Proxy subsystem could not obtain the memory it needed
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RFPROXY-2-UNAVAILABLE: RPC message failureExplanation The RF Proxy could not send an RPC message.
RF_ISSU Messages
This sections contains redundancy facility (RF) in-service software upgrade (ISSU) messages.
RF_ISSU-3
Error Message %RF_ISSU-3-CAPENTRY_REG: RF Cap Entry ([dec]) for Entity ([dec]) Registration failedExplanation A capability entry could not be registered for the RF 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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RF_ISSU-3-CAPGROUP_REG: RF Cap Group ([dec]) for Entity ([dec]) Registration failedExplanation A capability group could not be registered for the RF 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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RF_ISSU-3-CAP_REG: RF cap reg failed: reason [dec]Explanation The capabilities of the RF 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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RF_ISSU-3-CAPTYPE_REG: RF Cap Type for Entity ([dec]) Registration failedExplanation A capability type could not be registered for the RF 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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RF_ISSU-3-CLIENT_REG: RF Client ([dec]) Registration failedExplanation The RF 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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RF_ISSU-3-CLIENT_REG_FAILED: RF ISSU client ([dec]) Client registration failed. [chars]Explanation The RF 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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RF_ISSU-3-ENTITY_REG: RF Entity ([dec]) Registration failedExplanation The RF 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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RF_ISSU-3-GET_BUFFER: RF ISSU session ([dec]) failed to get bufferExplanation The RF ISSU failed to get a buffer.
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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RF_ISSU-3-MSG_DATAPTR: RF Client ([dec]) get msg dataptr failed. Error = [dec]Explanation The RF 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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RF_ISSU-3-MSGGROUP_REG: RF Msg Group ([dec]) for Entity ([dec]) Registration failedExplanation The message group for the RF 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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RF_ISSU-3-MSG_MTU: RF Client ([dec]) get msg mtu failed. Error = [dec]Explanation The RF 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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RF_ISSU-3-MSG_REG: RF msg reg failed: reason [dec]Explanation Messages for the RF 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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RF_ISSU-3-MSG_SEND: RF ISSU client for session ([dec]) failed to send messageExplanation The RF 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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RF_ISSU-3-MSGTYPE_REG: RF Msg Type for Entity ([dec]) Registration failedExplanation The message type for the RF 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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RF_ISSU-3-RF_MSG_NOT_OK: RF ISSU msg type ([dec]) is not okExplanation RF 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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RF_ISSU-3-SESSION_REG: RF session for Entity ([dec]) Registration failedExplanation The RF 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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RF_ISSU-3-SESSION_UNREG: RF session ([dec]) Un-Registration failedExplanation The RF ISSU session could not be unregistered.
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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
RFS Messages
This section contains remote file system messages.
RFS-3
Error Message %RFS-3-CAPENTRY_REG: RFS Cap Entry ([dec]) for Entity ([dec]) Registration failedExplanation RFS ISSU cap entry registration has failed.
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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RFS-3-CAPGROUP_REG: RFS Cap Group ([dec]) for Entity ([dec]) Registration failedExplanation RFS ISSU cap group registration has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu capability groups command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RFS-3-CAPTYPE_REG: RFS Cap Type for Entity ([dec]) Registration failedExplanation RFS ISSU cap type registration has failed.
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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RFS-3-CLIENT_REG: RFS Client ([dec]) Registration failedExplanation RFS ISSU client registration has failed.
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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RFS-3-CLIENT_SESSION_REG: RFS ISSU client shared msg session for entity ([dec]) registration failedExplanation RFS ISSU client shared message session registration has failed.
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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RFS-3-CLIENT_SESSION_UNREG: RFS session ([dec]) Un-Registration failedExplanation RFS ISSU client session unregistration has failed.
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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RFS-3-CREATE_ACTIVE_PORT: RFS create active port ([chars]) failedExplanation RFS ISSU active port creation has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show ipc port command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RFS-3-CREATE_CLIENT_PORT: RFS create client port (%s) failedExplanation The remote file system (RFS) ISSU client was unable to create a client port.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show ipc port commands and your pertinent troubleshooting logs.
Error Message %RFS-3-CREATE_SERVER_PORT: RFS create server port (%s) failedExplanation The RFS ISSU client was unable to create a server port.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show ipc port commands and your pertinent troubleshooting logs.
Error Message %RFS-3-CREATE_STANDBY_PORT: RFS create standby port ([chars]) failedExplanation RFS ISSU standby port creation has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show ipc port command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RFS-3-ENTITY_REG: RFS Entity ([dec]) Registration failedExplanation RFS ISSU entity registration has failed.
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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RFS-3-IPC_GET_BUFFER: RFS issu ipc get buffer failedExplanation RFS ISSU IPC get buffer has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RFS-3-LOCATE_PORT: RFS locates port ([chars]) failedExplanation RFS ISSU port location has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show ipc port command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RFS-3-MSGGROUP_REG: RFS Msg Group ([dec]) for Entity ([dec]) Registration failedExplanation RFS ISSU message group registration has failed.
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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RFS-3-MSG_MTU: RFS Client ([dec]) get msg mtu failed. Error = [dec]Explanation RFS ISSU client get message MTU has failed.
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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RFS-3-MSG_RCV: RFS Client ([dec]) receive msg failed. Error = [dec]Explanation RFS ISSU client receive message has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RFS-3-MSGTYPE_REG: RFS Msg Type for Entity ([dec]) Registration failedExplanation RFS ISSU message type registration has failed.
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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RFS-3-MSG_XMIT: RFS Client ([dec]) send msg failed. Error = [dec]Explanation RFS ISSU client send message has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RFS-3-NEGO_COMP: RFS nego is not compatible ([dec])Explanation RFS ISSU start shared negotiation session has failed.
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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RFS-3-NEGO_SESSION_REG: RFS nego session for Entity ([dec]) Registration failedExplanation RFS ISSU shared negotiation session registration has failed.
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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RFS-3-NEGO_SESSION_UNREG: RFS session ([dec]) Un-Registration failedExplanation RFS ISSU shared negotiation session unregistration failed.
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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RFS-3-OPEN_ACTIVE_PORT: RFS open active port ([chars]) failedExplanation The RFS ISSU client was unable to open an active port.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show ipc port command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RFS-3-OPEN_CLIENT_PORT: RFS open client port (%s) failedExplanation The RFS ISSU client was unable to open a client port.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show ipc port commands and your pertinent troubleshooting logs.
Error Message %RFS-3-OPEN_SERVER_PORT: RFS open server port (%s) failedExplanation The RFS ISSU client was unable to open a server port.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show ipc port commands and your pertinent troubleshooting logs.
Error Message %RFS-3-OPEN_STANDBY_PORT: RFS open standby port ([chars]) failedExplanation The RFS ISSU client was unable to open a standby port.
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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RFS-3-RECEIVE_NEGO_FAILED: RFS receive nego message ([dec]) failedExplanation RFS ISSU receive negotiation message has failed.
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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RFS-3-RECEIVE_NEGO_NOT_DONE: RFS receive nego message is not done ([dec])Explanation RFS ISSU receive negotiation message is not done.
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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RFS-3-REG_PORT: RFS reg port ([dec]) failedExplanation RFS ISSU register port has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show ipc port command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RFS-3-RFS_BOOL_CREATE_ERR: %s.Explanation The RFS redundancy facility (RF) client detected an error when creating a watched boolean.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RFS-3-RFS_ISSU_NEGO_PROCESS: RFS create rfs_issu_start_port watch boolean failedExplanation RFS ISSU create negotiation process has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RFS-3-RFS_ISSU_START_PORT: RFS create rfs_issu_start_port watch boolean failedExplanation The RFS ISSU client was unable to create anrfs_issu_start_port watched boolean.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RFS-3-RFS_ISSU_START_SESSION: RFS create rfs_issu_start_session watch boolean failedExplanation The RFS ISSU client was unable to create anrfs_issu_start_session watched boolean.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RFS-3-RFS_RF_PROG_ERR: %s %d.Explanation The RFS RF client detected 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RFS-3-RFS_RF_PROG_NOT_SENT_ERR: %s.Explanation The RFS RF client detected an error when sending a client progression.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RFS-3-SEND_NEGO_MESSAGE: RFS send nego message ([dec]) failedExplanation RFS ISSU send negotiation message has failed.
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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RFS-3-START_NEGO_SESSION: RFS start shared nego session ([dec]) failed: [dec]Explanation RFS ISSU start shared negotiation session has failed.
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 may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RFS-3-UNREG_ENTITY: RFS ISSU Client unreg entity failed.Explanation The RFS ISSU client unregister entity has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
RFS_ISSU Messages
This section contains remote file system in-service software upgrade (ISSU) messages.
RFS_ISSU-3
Error Message %RF_ISSU-3-INVALID_SESSION: RF ISSU client does not have a valid registered session.Explanation The redundancy facility (RF) ISSU client does not have a valid registered session.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs.
Error Message %RF_ISSU-3-RF_CAP_INVALID_SIZE: RF ISSU client capability list is empty.Explanation The RF ISSU capability list is empty, which is an invalid condition.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show issu capability entries commands and your pertinent troubleshooting logs.
Error Message %RF_ISSU-3-RF_CAP_RESULT_INCOMP: RF ISSU client capability exchange result incompatible.Explanation Based on the results of the capability exchange, the RF ISSU client is not compatible with the peer.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show issu negotiated capability commands and your pertinent troubleshooting logs.
RIP-3-
Error Message %RIP-3-UNAVAILABLE: Unable to open socketExplanation The requested operation could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
RITE Messages
This sections contains IP traffic export messages.
RITE-5
Error Message %RITE-5-ACTIVATE: Activated IP traffic export on interface [chars]Explanation IP traffic export has been enabled on the specified interface.
Recommended Action No action is required.
Error Message %RITE-5-DEACTIVATE: Deactivated IP traffic export on interface [chars]Explanation IP traffic export has been disabled on the specified interface.
Recommended Action No action is required.
Error Message %RITE-5-MODIFIED: Changed IP traffic export outbound interface from [chars] to [chars]Explanation The outbound interface for IP traffic export has been changed.
Recommended Action No action is required.
RLM-3
Error Message %RLM-3-UNAVAILABLE: rlm %d: %s%s.Explanation RLM initialization operation fails.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
RLM-4
Error Message %RLM-4-UNAVAILABLE: rlm %d: %s%s.Explanation A warning is given out for a particular RLM link.
Recommended Action LOG_STD_DBG_ACTION
RM-3
Error Message %RM-3-UNAVAILABLE: %s: RG-info conversion failed (%u).Explanation 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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RM-3-UNAVAILABLE: Bad state rg %s: %dExplanation 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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RM-3-UNAVAILABLE: Memory boundary violationExplanation 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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RM-3-UNAVAILABLE: No response-code from local RMExplanation 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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RM-3-UNAVAILABLE: Out of buffers in RM event buffer queueExplanation 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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RM-3-UNAVAILABLE: Unexpected Call on %s. Current state is %d.Explanation A call came in on a line where we think we still have an active call.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RM-3-UNAVAILABLE: Uninitialized value being usedExplanation 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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RM-3-UNAVAILABLE: Unknown Accounting type (%d), flag (%d).Explanation Get either invalid accounting type or flag
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RM-3-UNAVAILABLE: Wavl errorExplanation 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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
RMON Messages
This section contains Remote Monitoring (RMON) messages.
RMON-5
Error Message %RMON-5-HCFALLINGTRAP: Falling trap is generated because the value of %s has fallen below the falling-threshold hc value %lluExplanation A falling trap was generated. The value of the specified MIB object fell below the falling threshold value as configured by the rmon hc-alarms command for the specified object.
Recommended Action Take the appropriate action on the specified MIB object.
Error Message %RMON-5-HCRISINGTRAP: Rising trap is generated because the value of %s exceeded the rising-threshold hc value %lluExplanation A rising trap was generated. The value of the specified MIB object exceeded the rising threshold value as configured by the rmon hc-alarms command for the specified object.
Recommended Action Take the appropriate action on the specified MIB object.
ROllBACK-ISSU Messages
ROLLBACK-ISSU-2
Error Message %ROLLBACK_ISSU-2-GET_BUFFER: Rollback ISSU client failed to get buffer for message. Error: [dec] ([chars])Explanation The Rollback ISSU client failed to get buffer space for building a negotiation message. A negotiation message cannot be sent to the standby device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.
Recommended Action Issue the show logging and show checkpoint client command to gather data that may help identify the nature of the error. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.
Error Message %ROLLBACK_ISSU-2-INIT: Rollback ISSU client initialization failed to [chars]. Error: [dec] ([chars])Explanation The Rollback ISSU client could not be initialized. This initialization failure must be addressed before in-service software upgrade or downgrade can be performed successfully. If you do not address this failure, there will be downtime during software upgrade or downgrade.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.
Error Message %ROLLBACK_ISSU-2-SEND_NEGO_FAILED: Rollback ISSU client failed to send negotiation message. Error: [dec] ([chars])Explanation The Rollback ISSU client failed to send a session negotiation message to the peer device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.
Recommended Action Issue the show logging and show checkpoint client command to gather data that may help identify the nature of the error. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.
Error Message %ROLLBACK_ISSU-2-SESSION_NEGO_FAIL_START: Failed to start Rollback ISSU session negotiation. Error: [dec] ([chars])Explanation The Rollback ISSU client failed to start session negotition. If a problem occurs with the ISSU session start, the standby device cannot be brought up properly.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.
Error Message %ROLLBACK_ISSU-2-SESSION_REGISTRY: Rollback ISSU client failed to register session information. Error: [dec] ([chars])Explanation The Rollback ISSU client failed to register session information. If a problem occurs with the ISSU session registration, the standby device cannot be brought up properly.
Recommended Action Issue the show issu capability entries and show issu session and show issu negotiated capability command to gather data that may help identify the nature of the error. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.
ROLLBACK-ISSU-3
Error Message %ROLLBACK_ISSU-3-INVALID_SESSION: Rollback ISSU client does not have a valid registered session.Explanation The Rollback ISSU client does not have a valid registered session.
Recommended Action Issue the show issu capability entries and show issu session and show issu negotiated capability command to gather data that may help identify the nature of the error. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.
Error Message %ROLLBACK_ISSU-3-MSG_NOT_OK: Rollback ISSU client 'Message Type [dec]' is not compatibleExplanation The Rollback ISSU client received an incompatible message from the peer device. The message cannot be processed.
Recommended Action Issue the show issu message group and show issu session and show issu negotiated version command to gather data that may help identify the nature of the error. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.
Error Message %ROLLBACK_ISSU-3-MSG_SIZE: Rollback ISSU client failed to get the MTU for Message Type [dec].Error: [dec] ([chars])Explanation The Rollback ISSU client failed to calculate the MTU for the specified message. The Rollback ISSU client is not able to send the message to the standby device.
Recommended Action Issue the show issu message group and show issu session and show issu negotiated version command to gather data that may help identify the nature of the error. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.
Error Message %ROLLBACK_ISSU-3-SESSION_UNREGISTRY: Rollback ISSU client failed to unregister session information. Error: [dec] ([chars])Explanation The Rollback ISSU client failed to unregister session information.
Recommended Action Issue the show issu capability entries and show issu session and show issu negotiated capability command to gather data that may help identify the nature of the error. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.
Error Message %ROLLBACK_ISSU-3-TRANSFORM_FAIL: Rollback ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] ([chars])Explanation The Rollback ISSU client could not transform the specified message type. If the transmit transformation failed, the checkpoint message was not sent to the standby device. If the receive transformation failed, the checkpoint message was not applied on the standby device. In both cases, the Rollback state between the active device and the standby device is not identical.
Recommended Action Issue the show issu session and show issu negotiated version command to gather data that may help identify the nature of the error. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.
ROUTEMAP Messages
This section contains route map messages.
ROUTEMAP-4
Error Message %ROUTEMAP-4-BADTRACKOBJECTTYPE: can't track this type of objectExplanation Route maps only support STATE type track objects. This object is not a STATE object.
Recommended Action Reconfigure the track object to make it a STATE object.
ROUTEMAP_IPC-2
Error Message %ROUTEMAP_IPC-2-UNAVAILABLE: Alloc fail for route-map ipc bufferExplanation Unable to malloc a buffer to send route-map configuration down to linecards.
Recommended Action Enter a show chunks command and report the output, along with this error message, to your technical support representative.
Error Message %ROUTEMAP_IPC-2-UNAVAILABLE: The length of route map name tag is too longExplanation The length of route map name tag is too long for IPC. The receiver has a 256 character long limit on route map name tag
Recommended Action Use a route map name tag with the length of 256 or less characters
RPA-3-
Error Message %RPA-3-UNAVAILABLE: %sExplanation This message type is created for all those messages which have simple ASCII text and does not take any parameter. Message tells what the problem is.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RPA-3-UNAVAILABLE: CAS Entry does not exist for slot: %d, ctrl:%d, channel:%dExplanation CAS entry does not exist for the given controller and channel.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RPA-3-UNAVAILABLE: Unknown message type %d enqueued to RPA CAS ProcessExplanation A message type which is not known to RPA CAS process is enqueued to it's queue.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
RPF-4
Error Message %RPF-4-UNAVAILABLE: Error deleting an rpf entry from the multicast rpf treeExplanation An internal software error occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RPF-4-UNAVAILABLE: Error inserting a new rpf entry into the multicast rpf treeExplanation An internal software error occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
RPM-3
Error Message %RPM-3-UNAVAILABLE: Can't allocate MAC address for interface %u/%uExplanation MAC address allocation failed because of an incorrect slot and port combination, which exceeds the maximum available hardware.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
RPM-4
Error Message %RPM-4-UNAVAILABLE: Corrupt or missing MAC address cookie using random base %eExplanation The contents of MAC address EEPROM are invalid. The system is providing random MAC addresses
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RPM-4-UNAVAILABLE: Invalid CPU ID, assuming revision 1Explanation The CPU ID could not be read from the EEPROM. This is probably due to a hardware failure
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RPM-4-UNAVAILABLE: PCI activation failed, bay %d, 0x%xExplanation The system received an invalid PCI signal from the port adapter. This is probably due to a hardware failure.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
RPM_VIRTUAL_PORT-3
Error Message %RPM_VIRTUAL_PORT-3-UNAVAILABLE: %sExplanation This error indicates that the delete request to PXM has failed, timed out, or been rejected by PXM.
Recommended Action In the case of the failure or time-out the connection's state will be set to TIMEOUT and the resync process will periodically attempt to update PXM. In the case where the request is rejected by PXM (which should never occur) Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %RPM_VIRTUAL_PORT-3-UNAVAILABLE: %s Error String = %s. Error Code = %dExplanation The rpc/ipc request to PXM has failed or been rejected by PXM.
Recommended Action If the error message indicates rpc-timeout, the last command must be retried later. For other error cases copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %RPM_VIRTUAL_PORT-3-UNAVAILABLE: %s Message size = %dExplanation The error message indicates that the size of the message which is supposed to be sent to PXM or is received from PXM is too big.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %RPM_VIRTUAL_PORT-3-UNAVAILABLE: %s Message size = %dExplanation The ipc_get_pak_message failed. This could be due to the insufficient memeory.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %RPM_VIRTUAL_PORT-3-UNAVAILABLE: %s request_type = %dExplanation The rpc request from Virtual-Port or Resync process is not valid. This error should never occur
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %RPM_VIRTUAL_PORT-3-UNAVAILABLE: An unexpected FW error has occured. %sExplanation An unexpected FW error has 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RPM_VIRTUAL_PORT-3-UNAVAILABLE: ERROR: clrAllCnf --- Fail to delete clrAllCnf file on PXM C: disk ... Please delete file manually by doing delete c:auto_config_slot%d.Explanation This error indicates that the re-configuration request to PXM has failed, timed out, or been rejected by PXM.
Recommended Action In the case of the failure or time-out the connection's state will be set to TIMEOUT and the resync process will periodically attempt to update PXM. In the case where the request is rejected by PXM the connection state will be set to FAILED until the connection is deleted or re-configured.
Error Message %RPM_VIRTUAL_PORT-3-UNAVAILABLE: ERROR: clrAllCnf --- Fail to write to NVRAM. NOTE: Configuration in NVRAM is not cleaned up.RPS-3
Error Message %RPS-3-UNAVAILABLE: Redundant Power System DC Output Voltage condition is now normalExplanation The Redundant Power System DC Output Voltage is normal.
Recommended Action This is an informational message only. No action is required.
Error Message %RPS-3-UNAVAILABLE: Redundant Power System FAN condition is now normal.Explanation The Redundant Power System FAN is now normal.
Recommended Action The Redundant Power Supply previously detected fan failure condition which has now cleared.
Error Message %RPS-3-UNAVAILABLE: Redundant Power System Input Voltage condition is now normalExplanation The Redundant Power System Input Voltage is normal.
Recommended Action This is an informational message only. No action is required.
Error Message %RPS-3-UNAVAILABLE: Redundant Power System THERMAL condition is now normal.Explanation The Redundant Power System THERMAL is now normal.
Recommended Action The Redundant Power Supply previously detected an over temperature condition which has now cleared. This is most likely due to high ambient temperature where the Redundant Power Supply is located. A Redundant Power System thermal failure can also be caused by a fan failure in the Redundant Power Supply.
Error Message %RPS-3-UNAVAILABLE: Redundant Power System VOLTAGE is now normal.Explanation The Redundant Power System voltage is now normal.
Recommended Action The Redundant Power System previously detected an over voltage condition which has now cleared.
Error Message %RPS-3-UNAVAILABLE: Redundant Power System detected OVERVOLTAGE condition.Explanation The Redundant Power System detected OVERVOLTAGE condition.
Recommended Action The Redundant Power System detected an over voltage condition.
Error Message %RPS-3-UNAVAILABLE: Redundant Power System is now normalExplanation The Redundant Power System is operating normally.
Recommended Action This is an informational message only. No action is required.
Error Message %RPS-3-UNAVAILABLE: System detected Redundant Power System DC Output Voltage failure condition.Explanation The Redundant Power System experienced a DC Output Voltage failure condition in one of the power supplies.
Recommended Action One of the DC outputs has failed on the Redundant Power Supply. For 3600 and 2600 Redundant Power supplies, DC Status LED on the front of the Power Supply will identify which DC output has failed. For 5300 Redundant Power Supply, DC OK LED on the front of the Power Supply will identify which DC output has failed. When there is a DC failure, you need to replace the Redundant Power Supply.
Error Message %RPS-3-UNAVAILABLE: System detected Redundant Power System FAN FAIL condition.Explanation The Redundant Power System experienced a Fan failure condition.
Recommended Action One of the fans has failed and you should replace the Redundant Power Supply.
Error Message %RPS-3-UNAVAILABLE: System detected Redundant Power System Input Voltage failure condition.Explanation The Redundant Power System experienced an Input Voltage failure in one of the power supplies.
Recommended Action One of the AC or DC inputs has failed on the Redundant Power Supply. For 3600 and 2600 Redundant Power supplies, AC Input LED on the front of the Power Supply will identify which AC input has failed. For 5300 ACDC Redundant Power Supply, AC OK LED on the front of the Power Supply will identify which AC input has failed. For 5300 DCDC Redundant Power Supply, DC Input LED on the front of the Power Supply will identify which DC input has failed. Make sure that the AC/DC circuit in your building is operational, verify that the power cord is plugged into the Redundant Power Supply, and make sure that the AC/DC power switch on the Redundant Power Supply is on.
Error Message %RPS-3-UNAVAILABLE: System detected Redundant Power System THERMAL FAIL condition.Explanation The Redundant Power System experienced either a Fan failure or an Over Temperature condition.
Recommended Action For 3600 and 2600 Redundant Power supplies, look at the FAN and TEMP LEDs on the front of Power Supply. If the FAN LED is amber, one of the fans has failed and you should replace the Redundant Power Supply. If the TEMP LED is amber, the ambient temperature is too high. For 5300 RPS unit, this message is displayed when the ambient temperature is too high.
Error Message %RPS-3-UNAVAILABLE: System temperature is now normal.Explanation The system is operating at a normal temperature.
Recommended Action The system previously detected an over temperature condition which has now cleared. This is most likely due to high ambient temperature where the router is located.
Error Message %RPS-3-UNAVAILABLE: There is more than one failure with the Redundant Power System; please resolve problems immediatelyExplanation The Redundant Power System experienced multiple failures. This is a critical condition
Recommended Action There are multiple failures on the Redundant Power Supply. Examine the LEDs on the front of the Redundant Power Supply to find out which failures it has.
RPC Messages
This section contains Remote Procedure Call (RPC) messages.
RPC-2
Error Message %RPC-2-6: Recovered from RPC send failure for request [chars]. Resending request.Explanation A communication error occurred during an RPC request. RPC will retry.
Recommended Action This is an informational message only. No action is required.
Error Message %RPC-2-CORE_SAT_RPC_FAIL: RPC between Core and Remote Switch - [chars] failed (non-fatal)Expected when VSL goes downExplanation A nonfatal communication error occurred during an RPC request between the core and a remote switch or vice versa. This error message is not considered a failure when the virtual switch link (VSL) goes down.
Recommended Action No action is required.
Error Message %RPC-2-FAILED: Failed to send RPC request [chars] (fatal)Explanation A fatal communication error occurred during an RPC request.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RPC-2-FAILED_RETRY: Failed to send RPC request [chars] (will try again)Explanation A communication error occurred during an RPC request. The system will attempt the RPC request again.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RPC-2-FAILED_USERHANDLE: Failed to send RPC request [chars]Explanation A communication error occurred during an RPC request.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RPC-2-RETRY: Recovered from RPC send failure for request [chars]. Resending request.Explanation A communication error occurred during an RPC request.
Recommended Action The RPC will retry the request. If the 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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
RPF Messages
This section contains multicast Reverse Path Forwarding (RPF) messages.
RPF-3
Error Message %RPF-3-RTAVLDELETE: Error deleting an rpf entry from the multicast rpf treeExplanation An internal software error occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RPF-3-RTAVLINSERT: Error inserting a new rpf entry into the multicast rpf treeExplanation An internal software error occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
RPF-4
Error Message %RPF-4-AVLDELETE: Error deleting an rpf entry from the multicast rpf treeExplanation An internal software error occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RPF-4-AVLINSERT: Error inserting a new rpf entry into the multicast rpf treeExplanation An internal software error occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RPF-4-SNMP_RADIX_ERR: Failed to [chars] snmp node [chars] snmp radix tree for multicast group (*, [IP_address]).Explanation An error occured while adding or deleting snmp node in snmp radix tree when mroute is created or deleted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.
RP_MLP Messages
This section contains route processor Multilink Point-to-Point Protocol (RP_MLP) messages.
RP_MLP-3
Error Message %RP_MLP-3-ADJ_FAIL: Adjacency walk for [chars] failedExplanation An adjacency update for the specified multilink interface failed.
Recommended Action Reset the multilink interface by entering the shutdown command followed by the no shutdown command on the interface. If traffic does not resume, collect the output of the show adjacency internal and show cef interface internal commands. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RP_MLP-3-INCOMPATIBLELINK: The current config cannot be supported as link([chars]) [chars] for bundle ([chars])Explanation When using multilink, the following restrictions must be met:
- All the links should be from the same port.
- Non-channelized T3 interfaces are not supported on multilink.
- Any added link should be compatible with the existing links in the bundle.
- All the links should be distributed.Recommended Action Modify the configuration so that the restrictions are not violated.
Error Message %RP_MLP-3-UNSUPPORTEDCONFIG: The current config cannot be supported as [chars] for [chars]Explanation When using multilink on hardware-assisted SPAs, the maximum number of links in the bundle and number of bundles should not exceed the maximum permissible by device. Refer to the product documentation for restrictions.
Recommended Action Modify the configuration so that it does not violate the restrictions.
RP_MLP-4
Error Message %RP_MLP-4-DLFIONELINKSUPPORT: Only ONE link should be configured for dLFI bundle!!Explanation The system attempted to configure more than one link for the Distributed Link Fragmentation and Interleaving (dLFI) bundle interface. The dLFIoFR and the dLFIoATM do not support configuring more than one link.
Recommended Action No action is required.
RP_MLP-5
Error Message %RP_MLP-5-SPAWARNING: Feature support switching to LC based software for [chars] as [chars]Explanation A link was added to the bundle, but it is not on the same bay as other member links of the bundle. The specified link that is not on the same bay has become active, and the bundle has been switched to line card-based software support instead of the hardware mode that is supported on FREEDM.
Recommended Action When a link is added to a bundle, ensure that it is on the same bay as the other member links of the bundle, in order to have the MLP bundle in hardware mode supported on FREEDM.
Error MessageRSP Messages
This section contains Route Switch Processor (RSP) messages.
RSP-2
Error Message %RSP-2-UNAVAILABLE: Overrun detected. End of MEMD buffer : 0x%x End of datagram : 0x%x bufhdr %x: %08x %08x %08x %08x Flushing Processor CacheExplanation A packet was processed that was greater in size than the maximum possible MTU size, or an illegal buffer header data area was found.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, enter the show tech-support and show logging commands, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message %RSP-2-UNAVAILABLE: %s error, %s at addr %04x (%s) log %08x, data %08x %08xExplanation While the system was attempting to process a hardware queue, an error was detected by the QA ASIC. The error could be either a zero link error or a reuse error. A zero link error is caused by an attempt to place in the hardware queue a buffer header with an address of 0x0. A reuse error occurs when the QA ASIC detects or attempts to place in the hardware queue a buffer header that is the same as another buffer header in another hardware queue. Either of these errors can occur because of a software or hardware problem with the RSP or a line card.
Recommended Action Run the show logging command and see that whether any parity errors were recorded just before the QAERROR error message was received. If any parity error was recorded before the QAERROR, a hardware error has occurred. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. If no parity error was recorded, and the problem recurs, enter the show tech-support and show logging commands, contact your Cisco technical support representative, and provide the representative with the output of the commands.
Error Message %RSP-2-UNAVAILABLE: No memory available for %sExplanation An attempt at memory allocation failed.
Recommended Action Try these actions to remedy the problem: Add memory. Disable some features. Apply filtering to decrease the size of system data structures - the routing table, for example. In general, reduce other system activities to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message %RSP-2-UNAVAILABLE: QA Diagnostic %s error at %#08xExplanation An error occurred during an attempt to access the RSP.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, enter the show tech-support and show logging commands, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message %RSP-2-UNAVAILABLE: partially inserted or removed IPs on cyBus%uExplanation The RSP detected a stall condition of cbus.Most likely, a board is not fully seated in the chassis. A less likely possibility is a hardware problem with the RSP or backplane.
Recommended Action Try reseating the boards. Call your technical support representative for assistance if this message persists.
RSP-3
Error Message %RSP-3-UNAVAILABLE: %s %sExplanation An IPC error has occurred. The exact nature of the problem is described in the error message.
Recommended Action Copy the router configuration, along with any other relevant information. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message %RSP-3-UNAVAILABLE: %s (slot %u) has wrong hardware revision %u.%uExplanation The hardware in the indicated slot needs to upgraded for operation with the RSP.
Recommended Action Upgrade the board.
Error Message %RSP-3-UNAVAILABLE: %s acc %08x had bad value %dExplanation An incorrect value has been written on an accumulator.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative. A micro reload can correct the error condition as a workaround.
Error Message %RSP-3-UNAVAILABLE: %s, address %xExplanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %RSP-3-UNAVAILABLE: %s: unable to schedule restart for output queueExplanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %RSP-3-UNAVAILABLE: %x corrupt: %08x %08x %08x %08xExplanation The event handler at the RSP has detected a status update message from an interface processor, but the field in the status message that identifies the associated interface processor is not valid. This condition indicates that the status message is corrupted. This error could occur because of a hardware or a software problem. The address of the status message buffer and the first four words of the message will be displayed for diagnostic purposes.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, enter the show tech-support and show logging commands, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message %RSP-3-UNAVAILABLE: Bad Turbo IPC msg (%s): msg=%#x lastmsg=%#x hdrsize=%#x size=%#xExplanation An error was discovered in an IPC 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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RSP-3-UNAVAILABLE: Bad or missing ID EEPROM, controller type %uExplanation The ID EEPROM on the RSP is missing or bad.
Recommended Action This message indicates a manufacturing error. Report this error to your technical support representative.
Error Message %RSP-3-UNAVAILABLE: Bengal error. %sExplanation System controller Bengal has reported an error/event
Recommended Action Read error reports. SBE are generally not fatal. Most others are
Error Message %RSP-3-UNAVAILABLE: Can't allocate MAC address for interface %u/%uExplanation No MAC address was available for allocation to the specified interface.
Recommended Action Report this error to your technical support representative.
Error Message %RSP-3-UNAVAILABLE: Card %s wants %d byte love letters, but only got %d bytesExplanation An inconsistency between the microcode and the system code was detected.
Recommended Action Report this error to your technical support representative.
Error Message %RSP-3-UNAVAILABLE: Fixing %s by setting to default %sExplanation The characters shown can be either on the slave RSP setting or on the master RSP setting. The ROM monitor default slave RSP setting is not synchronized with the system configuration file specifications. During bootup, the system image detects the mismatch and modifies the ROM monitor setting to conform with these specifications. This mismatch most likely occurred because a new RSP was being installed and booted in a high system availability (HSA) environment (dual RSPs) for the first time. Alternatively, in established HSA configurations, this message may result from a previous Interprocess Communication (IPC) error occurring while the HSA environment is reconfigured.
Recommended Action Using the show version or show boot command, determine which slot contains the current slave RSP. Using the show config command, determine which slot has been specified as the default slave RSP. If there is no slave default-slot n command in the configuration file, the value defaults to the highest numbered CPU slot (slot 3 on a Cisco 7507, and slot 7 on a Cisco 7513). If the slot number obtained in Step 1 is the same as the number obtained in Step 2, then no further action is required. You have configured HSA in simple hardware backup mode, and both RSPs are identical. However, if the two slot numbers differ, you have configured HSA in software error protection mode, and will have different images running, depending on which RSP is currently the slave RSP. If the slot numbers discovered in Steps 1 and 2 differ, reload your router to ensure that the desired system image is running. After the reload, the actual slave RSP will match the default slave RSP specified in (or inferred from) the system configuration file. For details of various HSA configuration modes consult the Cisco IOSConfiguration Fundamentals Configuration Guide. See the Loading System Images and Configuration Files chapter (Cisco 7500 series only).
Error Message %RSP-3-UNAVAILABLE: Invalid return queue bcast_id=%d bufhdr %x: %08x %08x %08x %08xExplanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %RSP-3-UNAVAILABLE: Invalid return queue next=%#x, hwidb=%#x, type=%#x queue_ptr=%#x, bufhdr_offset=%#x, id=%d, bcast_id=%d bufhdr %x: %08x %08x %08x %08xExplanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %RSP-3-UNAVAILABLE: Malloc to %s failed for slot %d bay %dExplanation The information structure for the port adapter could not be created. The interfaces on the specified port adapter might no longer be functional. A possible reason for this is a memory allocation failure involving the port adapter. This can occur as a result of insufficient hardware memory or a memory leak.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RSP-3-UNAVAILABLE: Master has m/s version %d, slave has m/s version %dExplanation The master and slave are running incompatible software versions with regards to the master/slave exchange process.
Recommended Action If the slave image global configuration is used to override the default slave image from the bundle, then the slave image is incompatible. Update either the master or slave image to ensure the two are compatible. If the slave is running the image from the bundle, execute and record the output of show version, show running-config, and show controller cbus commands. Report this information and the error message to your technical support representative.
Error Message %RSP-3-UNAVAILABLE: Master/slave watchdog timed outExplanation While handling the interrupts from the DBUS FPGA, the RSP has detected that the timeout bit in the interrupt status register has been set. This condition indicates that the master RSP no longer controls the CBUS and DBUS. The slave may become active during this time. So, the rest of the interrupt handler will not be processed. This behavior could be the result of either a hardware or a software problem.
Recommended Action Copy the error message exactly as it appears. If this problem recurs, copy down the router's configuration along with any other relevant information, such as the output of show tech-support and show logging commands. Contact your Cisco technical support representative for assistance, and provide him with all the gathered information.
Error Message %RSP-3-UNAVAILABLE: NULLExplanation An internal software error has occurred. The exact nature of the problem is described in the error message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message %RSP-3-UNAVAILABLE: NULLExplanation The cBus buffer memory has been reset and reallocated. The exact nature of the problem is described in the error message.
Recommended Action Reset the memory manually (by changing the MTU on an interface, for example). If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message %RSP-3-UNAVAILABLE: No microcode for %s card, slot %uExplanation No microcode is defined or available for the specified card.
Recommended Action Reconfigure the card to specify an existing microcode file.
Error Message %RSP-3-UNAVAILABLE: Panic: %s %08x %08x %08x %08xExplanation The status message handler for the interface processor has detected that the firmware for the interface processor has experienced a critical condition. The name of the affected interface and the first four words of the status message buffer will be displayed along with the message for diagnostics
Recommended Action Copy the error message exactly as it appears on the console or in the system log, enter the show tech-support and show logging commands, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message %RSP-3-UNAVAILABLE: Slave NVRAM is temporarily busyExplanation Another process is temporarily locking the slave config.
Recommended Action Retry the command that caused the error message. If the error message recurs, check for other execs via the show users command. If you know that there are no other users locking the slave nvram, then contact your technical support representative for assistance.
Error Message %RSP-3-UNAVAILABLE: Slave changed state from %s to %sExplanation The slave RSP has undergone a hardware state change. Both the old state and new state are shown. Possible states are nonparticipant slave master unplugged Possible state changes indicated by the above message are any to unplugged unplugged to nonparticipant or slave nonparticipant to slave slave to nonparticipant Any other combination is unexpected.
Recommended Action The slave RSP has been removed. Consider reinstalling it if continued high system availability (HSA) operation is required. If the slave RSP is present, ensure that it is properly seated in the card cage. A slave RSP has been installed. Configure the router for HSA. See the Configuration Fundamentals Configuration Guide, in the Loading System Images and Configuration Files chapter (Cisco 7500 series only) for more details. In particular, use the slave sync config command to ensure that the new slave RSP is configured consistently with the current master RSP. CAUTION: Failure to ensure a consistent configuration on a freshly installed slave RSP might result in undefined behavior if the router reloads. A previously crashed slave RSP has been reset, or a newly installed slave RSP is in transition from unplugged to nonparticipant, and finally to slave state. No action is required. The slave RSP image has crashed. Log in to the slave RSP's console using the if-console slot command. You will now be connected to the ROM monitor prompt on the slave RSP. Diagnose the slave RSP failure. For example, capture the output from the stack and context ROM monitor commands. Provide that information to your technical support representative, along with the router's configuration and any other relevant information, so that the problem can be investigated. Log out from the slave RSP's console port using Ctrl-c or Ctrl-z, and enter the slave reload global configuration command on the master RSP to bring the slave RSP back online. All other state changes indicate a software or hardware error. Provide the router's configuration and any other relevant information to customer support so that the problem can be investigated.
Error Message %RSP-3-UNAVAILABLE: Slave stole mastershipExplanation The master RSP has detected that the slave RSP configuration was changed from slave to master. The old master RSP will reload and become the slave RSP, allowing the new master RSP take over. This behavior indicates a software or hardware error.
Recommended Action Copy the router configuration, along with any other relevant information. Copy the error message exactly as it appears on the console or in the system log, enter the show tech-support and show logging commands, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message %RSP-3-UNAVAILABLE: bad vc %u on %sExplanation A chennelized interface driver received a packet on an unconfigured channel.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative, along with the output of 'show tech-support'.
Error Message %RSP-3-UNAVAILABLE: cmd %u to %s (slot %u) took %u usecs, done %xExplanation A command from the RSP to an IP took longer for the system to process than expected. This condition may be caused by a heavily loaded CPU.
Recommended Action If this error recurs, copy the error message exactly as it appears on the console or in the system log, enter the show tech-support and show logging commands, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message %RSP-3-UNAVAILABLE: corrupt bufhdr %x: %08x %08x %08x %08xExplanation A miscommunication occurred between the RSP and an IP.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, enter the show tech-support and show logging commands, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message %RSP-3-UNAVAILABLE: queue=%#x, bufhdr %x: %08x %08x %08x %08xExplanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %RSP-3-UNAVAILABLE: reload command not allowed on standby RSPExplanation The reload command in exec mode is not allowed on thestandby RSP
Recommended Action Enter the slave reload commandin exec mode.
RSP-4
Error Message %RSP-4-UNAVAILABLE: %sExplanation Report this error to your technical support representative.
Error Message %RSP-4-UNAVAILABLE: %uMB required for HSAExplanation HSA requires a minimum of 24mb of memory.
Recommended Action Upgrade your system to meet minimum memory requirements for HSA.
Error Message %RSP-4-UNAVAILABLE: Corrupt or missing MAC address cookie using random base %eExplanation This message indicates the part containing the MAC addresses allocated to this chassis could not be accessed or was found to be corrupt, either due to a hardware problem or manufacturing problem.
Recommended Action Report this error to your technical support representative.
Error Message %RSP-4-UNAVAILABLE: DCEF switching should be enabled on member links of %sExplanation DCEF should be enabled for Multilink interfaces if required.
Recommended Action Go to the multilink interface configuration mode using the interface multilink multilink# command , and then enable DCEF on the interface using ip route-cache distributed as per your requirement
Error Message %RSP-4-UNAVAILABLE: Error saving crashinfo for slot %d. Reason: %sExplanation A VIP crashinfo file has not been saved due to the indicated reason.
Recommended Action If the reason indicates Out of space, the bootflash may not have sufficient memory to save the crashinfo file. Otherwise, open a case with the Technical Assistance Center via the Internet at www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RSP-4-UNAVAILABLE: Insufficient DRAM to adequately run this IOS version. %dM is recommended.Explanation The quantity of RSP DRAM is below the recommended amount.
Recommended Action Add DRAM.
Error Message %RSP-4-UNAVAILABLE: Slave configuration not updated for %s.Explanation The configuration on the slave cannot be synced with the master.
Recommended Action Ensure that 'slave auto-sync config' is configured, and that the slave is active
Error Message %RSP-4-UNAVAILABLE: VIP in slot %d was empty and was disabledExplanation The system failed to copy the specified file to the standbyRSP.
Recommended Action Ensure that the standby RSP exists and has enoughmemory for the file.
Error Message %RSP-4-UNAVAILABLE: size mismatch, master %uMB, slave %uMBExplanation Memory size mismatch between Master & Slave RSP.
Recommended Action Configure both Master and Slave RSPs to have an equal amount of memory.
RSP-5
Error Message %RSP-5-UNAVAILABLE: Slave changed to state Running, Buffer memory state : %sExplanation This is an informational message to indicate that the slave RSP has started running the slave RSP image. This message after the router boots or after the slave reload global configuration command is issued on the master RSP.
Recommended Action No action required.
RSP-6
Error Message %RSP-6-TXSTUCK: Txacc of Interface [chars] is at [dec]% of its txlimitExplanation The specified interface has a low TXACC value. This might be a transient condition and might be harmless if it occurs during periods of high packet traffic. If this condition is detected more than once during periods of relatively moderate traffic, it could indicate a problem. Distributed packet switching might be disrupted as a result of this condition.
Recommended Action If the message recurs during periods of relatively moderate traffic, this might indicate a disruption in distributed packet switching. If such a disruption occurs, enter the microcode reload command to recover. 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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
RSRB-3
Error Message %RSRB-3-UNAVAILABLE: %s: %d/%i: version mismatch, mine %d, theirs %dExplanation The remote end of a TCP remote peer is running the wrong version of the system software. Either the local end, the remote end, or both are not up to date.
Recommended Action Call your technical support representative for an update.
Error Message %RSRB-3-UNAVAILABLE: %s: %s: %i, op %x, len %d, trn %dExplanation The remote end of a direct serial RSRB connection detected a configuration problem or traffic that is not recognized by the configuration.
Recommended Action Examine the configuration on both sides of the serial connection for possible problems. Examine the traffic being offered for propagation with respect to the configuration. The destination target ring is denoted by the value of trn.
Error Message %RSRB-3-UNAVAILABLE: %s: %s: %s, op %x, len %d, trn %dExplanation The remote end of a direct serial RSRB connection detected a configuration problem or traffic that is not recognized by the configuration.
Recommended Action Examine the configuration on both sides of the serial connection for possible problems. Examine the traffic being offered for propagation with respect to the configuration. The destination target ring is denoted by the value of trn.
Error Message %RSRB-3-UNAVAILABLE: %s: sent %s to %sExplanation The local end of a direct serial RSRB connection detected a configuration problem or traffic that is not recognized by the configuration.
Recommended Action Examine the configuration on both sides of the serial connection for possible problems. Examine the traffic being offered for propagation with respect to the configuration.
Error Message %RSRB-3-UNAVAILABLE: FSTin: %s: version mismatch, mine %d, theirs %dExplanation The remote end of a direct serial peer is running the wrong version of the system software. Either the local end, the remote end, or both are not up to date.
Recommended Action Call your technical support representative for an update.
Error Message %RSRB-3-UNAVAILABLE: IFin: %s: version mismatch, mine %d, theirs %dExplanation The remote end of a direct serial peer is running the wrong version of the system software. Either the local end, the remote end, or both are not up to date.
Recommended Action Call your technical support representative for an update.
Error Message %RSRB-3-UNAVAILABLE: Null idb and not remoteExplanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message %RSRB-3-UNAVAILABLE: Peer %d/%i, HDR, vrp state wrong, %dExplanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message %RSRB-3-UNAVAILABLE: Peer %i, HDR, no vrpExplanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message %RSRB-3-UNAVAILABLE: Unit %d, no memory for %sExplanation The requested operation could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
RSRB-4
Error Message %RSRB-4-UNAVAILABLE: Bad vre typeExplanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message %RSRB-4-UNAVAILABLE: Peer %d/%i, %s, bad length %d, trn %dExplanation An internal software error occurred.
Recommended Action If either message recurs, call your technical support representative for assistance.
Error Message %RSRB-4-UNAVAILABLE: Peer %d/%i, CONN, illegal state %dExplanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message %RSRB-4-UNAVAILABLE: Peer %d/%i, HDR, recv state invalid, not empty %dExplanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message %RSRB-4-UNAVAILABLE: Peer %s [%-08x], illegal state %dExplanation An internal software error occurred.
Recommended Action If either of these messages recur, call your technical support representative for assistance.
Error Message %RSRB-4-UNAVAILABLE: Peer %s, %s, bad length %d, trn %dExplanation An internal software error occurred.
Recommended Action If either message recurs, call your technical support representative for assistance.
Error Message %RSRB-4-UNAVAILABLE: Peer %s, CONN, illegal state %dExplanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message %RSRB-4-UNAVAILABLE: Peer %s, IFin, bad connection state %dExplanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message %RSRB-4-UNAVAILABLE: Peer %s, wrong state %dExplanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message %RSRB-4-UNAVAILABLE: Remopened and t NULLExplanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message %RSRB-4-UNAVAILABLE: Ring exchange failure, resetting peer: %sExplanation The RSRB peer initiation logic failed due to a memory shortage or congestion condition.
Recommended Action The problem should clear and the peers should re-open without operator intervention.
Error Message %RSRB-4-UNAVAILABLE: Unit %d, local/vring set simultaneously, vrn %dExplanation An internal software error occurred.
Recommended Action If either of these messages recur, call your technical support representative for assistance.
RSVP Messages
This section contains RSVP protocol messages.
RSVP-1
Error Message %RSVP-1-RSVP_AUTH_NO_KEYS_LEFT: No valid keys left for [IP_address]Explanation The router attempted to use a key in an RSVP key chain but discovered that all the keys in the chain have expired and no other per-neighbor or per-interface keys are available for the specified neighbor. The router will continue to use the last key in the chain rather than revert to an unauthenticated condition. However, the specified neighbor router may start discarding RSVP messages as a result, and reservations with that neighbor may eventually time out.
Recommended Action Update the key chain by updating the text and expiration times for the expired keys.
RSVP-2
Error Message %RSVP-2-RSVP_AUTH_KEY_CHAIN_EXPIRED: All the keys in chain [chars] have expired - please update the key chain nowExplanation The router attempted to use a key in an RSVP key chain but discovered that all the keys in the chain have expired. The router will attempt to find another suitable key. If no other suitable per-neighbor key can be found, the router will attempt to use key (chain) configured for the interface over which the authenticated RSVP message is being sent or received.
Recommended Action Update the key chain by updating the text and expiration time(s) for the expired key(s).
RSVP-3
Error Message %RSVP-3-UNAVAILABLE: %08x %08x %08x %08x %08x %08x %08x %08xExplanation This is an auxiliary message to several packet-related messages. It provides a raw display of the information in the header of a corrupted data block.
Recommended Action This message provides additional information only. Copy the error message exactly as it appears, and report it to your technical support representative as part of the previously printed error message.
Error Message %RSVP-3-UNAVAILABLE: %08x %08x %08x %08x %08x %08x %08x %08xExplanation This is an auxiliary message to several packet-related messages. It provides a raw display of the information in the header of a corrupted data block.
Recommended Action This message provides additional information only. Copy the error message exactly as it appears, and report it to your technical support representative as part of the previously printed error message.
Error Message %RSVP-3-UNAVAILABLE: %s message from %i discarded - authentication algorithm mismatchExplanation The router received an RSVP message from a source that required authentication but the received message was using the wrong authentication algorithm.
Recommended Action Issue a show ip rsvp authentication detail command on the router to display the expected algorithm type. Then find the source and change its configuration to match.
Error Message %RSVP-3-UNAVAILABLE: %s message from %i discarded - authentication seq #%llu is a duplicateExplanation The router received an RSVP message with an authentication sequence number that has already been seen. RSVP discarded the message because an untrusted source may be (unsuccessfully) attempting an RSVP message replay attack.
Recommended Action If you can verify that the source is trusted, it is possible that the source has rebooted and its clock has gone backward in time; in this case, the source should be configured to synchronize its clock with an NTP server. Otherwise, the sender could be an untrusted source (unsuccessfully) attempting an RSVP message replay attack; try to find and disable the untrusted source.
Error Message %RSVP-3-UNAVAILABLE: %s message from %i discarded - challenge failed for key ID %*sExplanation The router sent an RSVP message to challenge the untrusted source to compute a secure hash on a random piece of data and return the hash with the same data, but the source did not return the expected data. RSVP discarded the response because the untrusted source may be (unsuccessfully) attempting an RSVP challenge response replay attack.
Recommended Action If you can verify that the source is trusted, it is possible that the source has malfunctioned; in this case, copy the error message exactly as it appears on the console or in the system log, issue the show tech-support rsvp command to gather data which may help identify the nature of the error, and send this information to your Cisco technical support representative. Otherwise, try to find and disable the untrusted source.
Error Message %RSVP-3-UNAVAILABLE: %s message from %i discarded - incorrect message digestExplanation The router received an RSVP message that contained a different secure hash from the one computed by the router. RSVP discarded the message because the message may have come from an untrusted source.
Recommended Action Check the configuration on the router and the sending system to make sure they are using the correct security key and secure hash algorithm.
Error Message %RSVP-3-UNAVAILABLE: %s message from %i discarded - seq #%llu outside authentication windowExplanation The router received an RSVP message whose authentication sequence number is less than the lower limit of the out-of-order window. RSVP discarded the message because an untrusted source may be (unsuccessfully) attempting an RSVP message replay attack.
Recommended Action It is possible that a trusted source is sending a burst of reordered RSVP messages that is too large for the authentication window size. If you can verify that the source is trusted and its messages are being sent in large reordered bursts, use the ip rsvp authentication window-size command to increase the window size on the receiving router. It is also possible that a trusted source has rebooted and its clock has gone backward in time; in this case, the source should be configured to synchronize its clock with an NTP server. Otherwise, the sender could be an untrusted source (unsuccessfully) attempting an RSVP message replay attack; try to find and disable the untrusted source.
Error Message %RSVP-3-UNAVAILABLE: %s message from %i discarded: no security association for %i - no RSVP security key configured or no memory left.Explanation The router received an RSVP message that contained a secure hash but dropped the message because the router was not able to create a security association for the sending system.
Recommended Action Check the configuration on the router to make sure that RSVP has access to a security key for the sending system. If such a key is configured, then check to see if the router has run out of memory.
Error Message %RSVP-3-UNAVAILABLE: %s: %s %s %sExplanation An action attempted by the rsvp implementation encountered an unexpected condition
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support rsvp command to gather data which may help identify the nature of the error. Then send this information to your Cisco technical support representative.
Error Message %RSVP-3-UNAVAILABLE: Inconsistent rsvp reliable message timerExplanation The summary refresh timer may be blocked.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support rsvp command to gather data which may help identify the nature of the error. Then send this information to your Cisco technical support representative.
Error Message %RSVP-3-UNAVAILABLE: No response to challenge issued to %i for key ID %*sExplanation The router sent an RSVP message to challenge the untrusted source to compute a secure hash on a random piece of data and return the hash with the same data, but the source did not reply. The source may have crashed or lost its network connection. However, it is also possible that the source was (unsuccessfully) attempting to replay an RSVP message before the challenge and gave up when it saw the challenge from the router
Recommended Action If you can verify that the source is trusted, try to determine if it has crashed or lost its network connection and then restore network connectivity to it. If the source repeatedly crashes when challenged, a temporary workaround might be to disable challenges on the router by issuing a no ip rsvp authentication challenge command until the problem on the source is resolved. Otherwise, assume the source is untrusted; try to find and disable it.
Error Message %RSVP-3-UNAVAILABLE: RSVP Message had a bad checksum: %d foo: %dExplanation The router received an incorrect RSVP message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support rsvp command to gather data which may help identify the nature of the error. Then send this information to your Cisco technical support representative.
Error Message %RSVP-3-UNAVAILABLE: RSVP Message had a bad length; ip data len: %d rsvp len: %dExplanation The router received an incorrect RSVP message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support rsvp command to gather data which may help identify the nature of the error. Then send this information to your Cisco technical support representative.
Error Message %RSVP-3-UNAVAILABLE: RSVP Message had a bad type: %dExplanation The router received an incorrect RSVP message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support rsvp command to gather data which may help identify the nature of the error. Then send this information to your Cisco technical support representative.
Error Message %RSVP-3-UNAVAILABLE: RSVP Message had a bad version: %dExplanation The router received an incorrect RSVP message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support rsvp command to gather data which may help identify the nature of the error. Then send this information to your Cisco technical support representative.
Error Message %RSVP-3-UNAVAILABLE: RSVP Message was malformed; traversed objects len: %d rsvp msg len: %dExplanation The router received an incorrect RSVP message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support rsvp command to gather data which may help identify the nature of the error. Then send this information to your Cisco technical support representative.
Error Message %RSVP-3-UNAVAILABLE: RSVP calculated Recovery Time is longer than TE Rewrite Hold-Time registered with LSD. Some LSPs may not be be recovered.Explanation TE registered a maximum cutover time with the LSD that is less than the time it may actually take to recover all LSPs. As a result, more than usual traffic loss may occur on some LSPs during recovery
Recommended Action Make note of the number of Checkpointed LSPs in the RSVP HA database by issuing the command show ip rsvp high-availability database internal . This number likely exceeds the hard defined limit of the number of recoverable LSPs. Provide this information to Cisco technical support representative.
Error Message %RSVP-3-UNAVAILABLE: Received a bad RSVP message, num objs: %d obj len: %d msg_len: %dExplanation The router received an incorrect RSVP message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support rsvp command to gather data which may help identify the nature of the error. Then send this information to your Cisco technical support representative.
RSVP-4
Error Message %RSVP-4-RSVP_AUTH_DUPLICATE_KEY_ID: Key chains [chars] and [chars] contain duplicate key ID [int]Explanation An attempt is being made to add a new key identifier to a key chain in the router configuration but RSVP detected that this identifier is found in another key chain already assigned to RSVP. Becaue key identifiers must be unique across all the key chains used by RSVP, RSVP will not use the keys with this identifier in all such key chains. This could cause RSVP authentication to fail in some cases.
Recommended Action Update the listed key chain(s) so they use different key identifiers.
RSVP-5
Error Message %RSVP-5-RSVP_AUTH_KEY_ACL_CHANGE: Key chain [chars] [chars] for [IP_address] because ACL "[chars]" [chars]Explanation The ACL specified in the message text associates the key chain specified in the message text with a set of RSVP neighbors. RSVP uses the specified key chain to authenticate each RSVP message exchanged with that set of RSVP neighbors after the association is configured. Subsequently, the specified ACL has been reconfigured such that the key chain association is no longer valid for one or more RSVP neighbors in the set. This causes RSVP to search the configuration for another suitable key chain to use with those neighbors. If no such key chain is found, RSVP will no longer be able to provide authentication for messages exchanged with those RSVP neighbors. This causes RSVP to discard RSVP messages from that set of neighbors. Because this may ultimately lead to loss of RSVP functionality with those neighbors, RSVP generates this system message. This system message may also be generated if the ACL is subsequently changed so that it reassociates RSVP neighbors with the specified key chain. If RSVP is not using another key chain for the set of RSVP neighbors specified by the ACL, RSVP will begin using the specified key chain to exchange authenticated RSVP messages with that set of RSVP neighbors, potentially restoring RSVP functionality with those neighbors.
Recommended Action If the ACL change unexpectedly caused authentication to be disabled or enabled for one or more RSVP neighbors, undo the ACL change so that RSVP authentication is not impacted.
Error Message %RSVP-5-RSVP_AUTH_ONE_KEY_EXPIRED: Key (ID) [int] in chain [chars] has expiredExplanation The router has detected that one key in a RSVP key chain has expired and that RSVP has switched to the next unexpired key in that chain.
Recommended Action Update the key chain by changing the text and expiration time(s) for the expired key.
RSVP_HA Messages
This section contains RSVP high availability (HA) protocol messages.
RSVP_HA-3
Error Message %RSVP_HA-3-CF_REGISTER_FAILED: Failed to register with CFExplanation The system may be low on memory.
Recommended Action Verify system memory availability. Deconfigure graceful restart full mode and configure it again. This will attempt to restart the RSVP HA process and reregister with compact flash (CF).
Error Message %RSVP_HA-3-CLI_ADD_FAILED: Failed to add RSVP HA to CLIExplanation The system may be low on memory.
Recommended Action Verify system memory availability. Deconfigure graceful restart full mode and configure it again. This will attempt to restart the RSVP HA process and reregister with compact flash (CF).
Error Message %RSVP_HA-3-DB_INIT_FAILED: Database init failedExplanation The system may be low on memory.
Recommended Action Verify system memory availability. Deconfigure graceful restart full mode and configure it again. This will attempt to restart the RSVP HA process and reregister with compact flash (CF).
Error Message %RSVP_HA-3-ENTRY_MOVE_FAILED: Failed to move a database entry to [chars] treeExplanation An internal 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RSVP_HA-3-ISSU_INIT_FAILED: In Service Software Upgrade (ISSU) Init failedExplanation The system may be low on memory.
Recommended Action Verify system memory availability. Deconfigure graceful restart full mode and configure it again. This will attempt to restart the RSVP HA process and reregister with compact flash (CF).
Error Message %RSVP_HA-3-ITEM_SIZE_TOO_BIG: Item size ([int]) bigger than default CF buffer ([int])Explanation An internal 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RSVP_HA-3-MAIN_INIT_FAILED: Main init failedExplanation The system may be low on memory.
Recommended Action Verify system memory availability. Deconfigure graceful restart full mode and configure it again. This will attempt to restart the RSVP HA process and reregister with compact flash (CF).
Error Message %RSVP_HA-3-MSG_MGR_INIT_FAILED: Message Manager init failedExplanation The system may be low on memory.
Recommended Action Verify system memory availability. Deconfigure graceful restart full mode and configure it again. This will attempt to restart the RSVP HA process and reregister with compact flash (CF).
Error Message %RSVP_HA-3-PROCESS_CREATE_FAILED: Failed to create RSVP HA processExplanation The system may be low on memory.
Recommended Action Verify system memory availability. Deconfigure graceful restart full mode and configure it again. This will attempt to restart the RSVP HA process.
Error Message %RSVP_HA-3-PROCESS_KILL: Killing RSVP HA processExplanation The RSVP HA process is terminating.
Recommended Action No action is required.
Error Message %RSVP_HA-3-RF_REGISTER_FAILED: Failed to register with RFExplanation The system may be low on memory.
Recommended Action Verify system memory availability. Deconfigure graceful restart full mode and configure it again. This will attempt to restart the RSVP HA process and reregister with compact flash (CF).
Error Message %RSVP_HA-3-RF_UNREGISTER_FAILED: Failed to unregister with RFExplanation The RSVP HA client may not have registered with RF.
Recommended Action No action is required.
RS_TDM-3
Error Message %RS_TDM-3-UNAVAILABLE: A TDM function is used with a bad argument: %sExplanation An internal software error has occurred. A TDM function was called with invalid arguments and could not be processed. The invalid arguments are specified at the end of this error message, along with any other useful data.
Recommended Action Enter the debug tdm command. If the problem recurs, copy the error message, the trace message, and surrounding debug text exactly as they appear on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message %RS_TDM-3-UNAVAILABLE: Clash in usage for TDM backplane timeslot %dExplanation The TDM backplane timeslot to be allocated is already in use
Recommended Action Check the split dial-shelf settings on both router shelves for conflicting setting
Error Message %RS_TDM-3-UNAVAILABLE: TDM backplane timeslot %d is in an unknown stateExplanation The TDM backplane timeslot specified is in an unknown state
Recommended Action Check the split dial-shelf settings on both router shelves for conflicting setting
Error Message %RS_TDM-3-UNAVAILABLE: TDM extended split on Router shelf Clashes to my %s other %s extended backplane ds0Explanation The number of extended backplane ds0 for this router clashes with the other router shelf
Error Message %RS_TDM-3-UNAVAILABLE: TDM legacy split on Router shelf Clashes to my %d other %d legacy backplane ds0Explanation The number of legacy backplane ds0 for this router clashes with the other router shelf
Error Message %RS_TDM-3-UNAVAILABLE: TDM split on %s Router shelf Reduced to %d backplane ds0Explanation The number of backplane ds0 for this router has been forced lower
Error Message %RS_TDM-3-UNAVAILABLE: TDM split user setting are in conflict: my RS %s = %d, other RS %s = %dExplanation The user setting for tdm split on this router shelf is in conflict with the setting on the other router, More backplane DS0 are in usethan 2048 DS0
Recommended Action Set the other router dial-shelf split backplane-ds0 to non conflicting setting
Error Message %RS_TDM-3-UNAVAILABLE: TDM split user setting are not matched pairs my RS %s = %d ds0, expected other RS %s = %d ds0, actual other RS %s = %d ds0Explanation The user setting for tdm split on this router shelf is not compatible with the setting on the other router
Recommended Action Set the other router dial-shelf split backplane-ds0 to above setting
RTT Messages
This section contains round-trip time monitor messages.
RTT-3
Error Message %RTT-3-PathSetupFailed: %RTR Probe [int]: Error in setting current Path. Probe will be stoppedExplanation An internal software error has occurred.
Recommended Action Reschedule the probe operation that was stopped. Copy the message exactly as it appears on the console or in the system log. Enter the show rtr configuration command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RTT-3-SAAMPLS: IP SLA Monitor([dec]): SAA MPLS [chars] Probe [chars] [chars] for destination-address [IP_address] lsp-selector [IP_address]Explanation This informational message logs violations in the Service Assurance Agent probes. This message appears after the rtr logging trap command has been entered.
Recommended Action If this message is not necessary, enter the no rtr logging trap command to disable logging. Otherwise, no action is required.
Error Message %RTT-3-SAANEGATIVEVALUE: IP SLA Monitor([dec]): Negative Value for [chars]Explanation The IP SLA monitor statistics generated an error message.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RTT-3-SAANOPROCESS: IP SLA Monitor: Cannot create a new processExplanation The IP SLA monitor is unable to start a new process, and may not be running.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message %RTT-3-SAAPROBENOTFOUND: IP SLA Monitor: Error deleting the probeExplanation A deletion attempt was performed on a probe that does not exist.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RTT-3-SAARESPTWINITFAIL: IP SLAs responder initialzation failedExplanation The IP Service Level Agreement (IP SLA) responder initialization process was unable to initialize the timer wheel. As a result, the IP SLA probes on other routers for which this router acts as responder will not work.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RTT-3-SAATWINITFAIL: IP SLAs: Generic Timer wheel timer functionality failed to initializeExplanation IP SLAs could not initialize the timer wheel.
Recommended Action Search for resolved software issues using the Bug Toolkit at Active
Explanation This message is generated only when SGBP errors or events debugging is enabled. This indicates that a link to another SGBP member has completed the interactions to set it up and is now entering the active state.
Recommended Action No action is required.
RTT-4
Error Message %RTT-4-DuplicateEvent: IP SLA Monitor [dec]: Duplicate event received. Event number [dec]Explanation The IP SLA monitor process has received a duplicate event.
Recommended Action This is only a warning message. If this message recurs, copy the message exactly as it appears on the console or in the system log. Enter the show rtr configuration command to gather data that may help identify the cause of the error.Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered along with information about the application that is configuring and polling the Service Assurance Agent probes. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %RTT-4-OPER_CLOSS: condition %s, entry number = %dExplanation This message displays connection loss conditions in the IP Service Level Agreement (IP SLA) operations. This message is enabled when the ip sla monitor logging trap command is entered.
Recommended Action Ensure that the destination for the IP SLA operation is reachable and that the IP SLA responder operation is configured on the destination. To disable these messages for IP SLA operations, enter the no ip sla monitor logging trap command.
Error Message %RTT-4-OPER_TIMEOUT: condition %s, entry number = %dExplanation The timeout condition is displayed for the IP SLA operations. This message is enabled when the ip sla monitor logging trap command is entered.
Recommended Action Ensure that the destination for the IP SLA operation is reachable. To disable these messages for IP SLA operations, enter the no ip sla monitor logging trap command.
Error Message %RTT-4-SAACLOCKNOTSET: IP SLA Monitor Probe(s) could not be scheduled because clock is not set.Explanation One or more IP SLA monitor probes could not be scheduled because the system clock is not set.
Recommended Action Ensure that the system clock is functional by using Network Time Protocol or another mechanism.
Error Message %RTT-4-SAAGRPSCHEDCONFIGFAIL: Group Schedule Entry [dec]: [chars]Explanation The probes could not be group scheduled. Either the configured starting time has already occurred, or the starting time is invalid.
Recommended Action Reschedule the group scheduling entry with a valid start time.
Error Message %RTT-4-SAASCHEDCONFIGFAIL: IP SLA Monitor Probe [dec]: [chars]Explanation The IP SLA Monitor probe could not be scheduled. Either the configured starting time has already occurred, or the starting time is invalid.
Recommended Action Reschedule the failed probe with a valid start time.
RTT-6
Error Message %RTT-6-SAATHRESHOLD: IP SLA Monitor([dec]): Threshold [chars] for [chars]Explanation This informational message logs threshold violations in the Service Assurance Agent probes. This messages appears after the rtr logging trap command has been entered.
Recommended Action If this message is not necessary, enter the no rtr logging trap command to disable logging. Otherwise, no action is required.
RUDP-3
Error Message %RUDP-3-UNAVAILABLE: rudp %d: %s%s.Explanation RUDP initialization operation fails.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
RUDP-4
Error Message %RUDP-4-UNAVAILABLE: rudp %d: %s%s.Explanation A warning is given out for a particular RUDP link.
Recommended Action LOG_STD_DBG_ACTION
Regen-1
Error Message %Regen-1-UNAVAILABLE: System detected OVERTEMPERATURE condition. Putting the system in Power save mode and going to rommon. Please resolve cooling problem and restart system!Explanation The environmental monitor detected a high-temperature condition.
Recommended Action Make sure that the room temperature is not too high and that air flow to the card is not blocked. If this condition persists, the environmental monitor might shut down the system. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Regen-3
Error Message %Regen-3-UNAVAILABLE: Can't allocate MAC address for interface %u/%uExplanation All the available MAC addresses for the system have been allocated.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %Regen-3-UNAVAILABLE: Detected invalid NVRAM size: %d bytesExplanation The detected size of NVRAM is not one of the supported sizes.The NVRAM may be bad.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %Regen-3-UNAVAILABLE: Failed to erase config due to internal errorExplanation Password protection feature failed to erase config due to internal error
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %Regen-3-UNAVAILABLE: Invalid Port Adaptor type (%d) reported for mainboardExplanation The 'virtual' port adaptor type derived from the mainboard type isnot one of the supported types. It may be that this mainboard is a newmainboard type and the software release you are running does not supportthe new mainboard type.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %Regen-3-UNAVAILABLE: PCI Configuration Read Cycle Failed for bus %d, Device %d, function %d, register %dExplanation A PCI Bus Configuration Read cycle failed. The mainboard needs to be replaced.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %Regen-3-UNAVAILABLE: PCI Configuration Write Cycle Failed for bus %d, Device %d, function %d, register %dExplanation A PCI Bus Configuration Write cycle failed. The mainboard needs to be replaced.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %Regen-3-UNAVAILABLE: get_pci_dev_num: Invalid bay (%d) or device number offset (%D)Explanation A software error occurred in trying to determine PCI device addressing. This is most likely a 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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %Regen-3-UNAVAILABLE: pas_get_device_subunit: Invalid PCI device number: %dExplanation A software error occurred in trying to determine PCI device addressing. This is most likely a 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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %Regen-3-UNAVAILABLE: regen_big_endian_addr: Attempted conversion of invalid address (0x%x)Explanation A software error occurred in trying to determine PCI device addressing. This is most likely a 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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %Regen-3-UNAVAILABLE: regen_little_endian_addr: Attempted conversion of invalid address (0x%x)Explanation A software error occurred in trying to determine PCI device addressing. This is most likely a 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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Regen_MAINBOARD_ASYNC_PQUICC-3
Error Message %Regen_MAINBOARD_ASYNC_PQUICC-3-UNAVAILABLE: No memory for %s of unit %dExplanation The router does not have enough memory to perform the function
Recommended Action Consider adding more shared memory. Copy the error message exactly as it appears, and report it to your technical support representative.
RUNCFGSYNC Messages
This section contains Auto-Running Configuration Synchronization (RUNCFGSYNC) messages.
RUNCFGSYNC-6
Error Message RUNCFGSYNC-6-HASRMSTATE: [chars]Explanation HA single router mode has changed state. Additional details are provided in the error message text.
Recommended Action No action is required.
SASL Messages
This section contains Simple Authentication and Security Layer (SASL) messages.
SASL-2
Error Message %SASL-2-FORKFAIL: Cannot fork process [chars]Explanation An attempt to fork a process has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SASL-2-INITFAIL: Initialization failed - [chars]Explanation SASL component 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
SBETH-1
Error Message %SBETH-1-UNAVAILABLE: %s - Cannot create IDB subblock due to insufficient memoryExplanation There was insufficent system memory to create the subblock.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SBETH-1-UNAVAILABLE: %s - Could not install or use IDB subblockExplanation An internal IOS error prevented the IDB subblock from being installed or used.
Recommended Action Software bug - open a case with Development Engineering. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Recommended Action %SBETH-1-UNAVAILABLE: %s, initialization failed, no buffer memory
Explanation The Ethernet port initialization failed due to insufficient memory
Recommended Action The router requires more packet memory - consider upgrade. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SBETH-1-UNAVAILABLE: Could not init buffer poolsExplanation The driver failed to get a pool of buffers from IOS
Recommended Action Software bug - open a case with Development Engineering.Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Recommended Action %SBETH-1-UNAVAILABLE: Could not initialize structure
Explanation The driver failed to initialize a structure
Recommended Action Software bug - open a case with Development Engineering. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SBETH-1-UNAVAILABLE: Invalid Interface Descriptor BlockExplanation The driver tried to fetch the interface's IDB 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SBETH-1-UNAVAILABLE: MAC Still in ResetExplanation An attempt was made to access the MAC while it was in reset
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SBETH-1-UNAVAILABLE: Plugin function table incomplete or missingExplanation The driver could not access the PA's specific function table
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SBETH-1-UNAVAILABLE: Problem getting particle sizeExplanation The driver was unable to get the particle size for this interface
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SBETH-1-UNAVAILABLE: Unknown IDBTYPE while starting driverExplanation The IDBTYPE in the interface's instance structure is undefined for this driver
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SBETH-1-UNAVAILABLE: Unknown media-type in subblockExplanation The media-type specified in the driver subblock is 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SBETH-1-UNAVAILABLE: Unknown or invalid chip mode (MII/TBI)Explanation The driver subblock contains an invalid or undefined chip operating mode (MII or TBI mode)
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
SBETH-2
Error Message %SBETH-2-UNAVAILABLE: Interface %s does not support ISLExplanation ISL is not supported on the specified interface's hardware.
Recommended Action LOG_STD_NO_ACTION
SBETH-3
Error Message %SBETH-3-UNAVAILABLE: %s - GBIC contains a bad EEPROMExplanation Interface contains a GBIC with a bad EEPROM. This causes the link to be down.
Recommended Action Please make sure the GBIC type is compatible with the interface. Verify that the GBIC was obtained from Cisco or a supported vendor
Error Message %SBETH-3-UNAVAILABLE: %s - Unknown GBIC typeExplanation Interface contains a GBIC of unknown type. This causes the link to be down.
Recommended Action Please make sure the GBIC type is compatible with the interface. Verify that the GBIC was obtained from Cisco or a supported vendor
Error Message %SBETH-3-UNAVAILABLE: %s, error interrupt, mac_status = 0x%016llxExplanation The MAC controller has signalled an error condition.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SBETH-3-UNAVAILABLE: %s, packet too big (%d), from %eExplanation The interface detects a packet larger than what is defined by MTU
Recommended Action Check the other station's MTU setting LOG_STD_NO_ACTION
SATVS_DNLD Messages
This section contains satellite switch virtual switch (VS) download messages.
S4T68360-1
Error Message %S4T68360-1-UNAVAILABLE: %s %sExplanation A software or hardware error occurred. The S4T interface is not responding to commands used to initialize it.
Recommended Action This failure will happen due to S4T port initialization or reset failure. Collect the 'show tech' and 'show log' information at the time of problem and send it to the technical support representative
Error Message %S4T68360-1-UNAVAILABLE: %s %sExplanation The S4T port adaptor failed to respond to a request to disable an interface.
Recommended Action This failure will happen due to S4T port initialization or reset failure. Collect the 'show tech' and 'show log' information at the time of problem and send it to the technical support representative
Error Message %S4T68360-1-UNAVAILABLE: Bay %d for microcode downloadExplanation The S4T port adaptor hardware failed. The S4T port adaptor would not begin to download the operational microcode.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %S4T68360-1-UNAVAILABLE: Bay %d port adaptorExplanation The S4T port adaptor hardware failed. The periodic check routine detected the failure and restarted it.
Recommended Action LOG_STD_NO_ACTION
Error Message %S4T68360-1-UNAVAILABLE: Bay %d: %sExplanation The S4T port adaptor failed to complete hardware initialization.
Recommended Action Try to reseat the PA properly in the system slots. If the error still happens, then verify for the hardware failure including the 7200 chasis in case of 7200 or vip in case of RSP and the PA as this error will come only if there is failure in hardware.
Error Message %S4T68360-1-UNAVAILABLE: Failed for bay %d, sent = 0x%x, received = 0x%xExplanation The download of the internal firmware to the S4T failed to checksum correctly. This usually indicates a hardware failure of the S4T or the Versatile Interface Processor (VIP).
Recommended Action Perform a power cycle. If the problem persists, the S4T hardware may have a problem.
Error Message %S4T68360-1-UNAVAILABLE: Microcode download to bay %d failedExplanation The S4T port adaptor hardware failed. It did not acknowledge the completion of the operational microcode download.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %S4T68360-1-UNAVAILABLE: Microcode to port adaptor in bay %dExplanation The S4T hardware has failed. It could not download its operational microcode.
Recommended Action Try to reseat the PA properly in the system slots. If the error still happens, then verify for the hardware failure including the 7200 chasis in case of 7200 or vip in case of RSP and the PA as this error will come only if there is failure in hardware.
S4T68360-3
Error Message %S4T68360-3-UNAVAILABLE: %s packet buffer, pak=0x%xExplanation A software or hardware error occurred. The S4T driver detected that the transmit ring is an inconsistent state.
Recommended Action Do shut/no shut on the interface and if still this problem happens, then do OIR of the PA. If this also doesn't solve the problem then there may be a hardware failure. Please verify for it. send the 'show tech' and 'show log' information collected at the time of problem to the technical support representative
Error Message %S4T68360-3-UNAVAILABLE: Bay %d device ID seen as %#x, expected %#xExplanation The S4T hardware failed. A non-S4T device pointed at the software for the S4T.
Recommended Action Check the system configuration for the failure in the bay number that is reported. If it is not a M4T PA, contact the appropriate component to which that PA in that slot belongs. If it is a M4T PA, then try to reseat the PA once agian and if the error still happens, then send the 'show tech' and 'show log' information to the technical support representative.
Error Message %S4T68360-3-UNAVAILABLE: Bay %d stale msg %s- mbx0:%lx, mbx1:%lx, mbx2:%lxExplanation The S4T has not responded to a message from the Versatile Interface Processor (VIP) within a specified time.
Recommended Action Perform a microcode reload of the VIP. If the problem persists, it indicates that the S4T or VIP hardware failed.
Error Message %S4T68360-3-UNAVAILABLE: Bay %d, Exception %d, trace %dExplanation The S4T firmware detected an illegal or unexpected CPU exception or condition. This may be caused by a software error or by a hardware failure.
Recommended Action Perform a microcode reload of the Versatile Interface Processor (VIP). If the problem persists, it indicates that the S4T hardware failed.
S4T68360-5
Error Message %S4T68360-5-UNAVAILABLE: %s TX packet dropped; particle count (%d) exceeds %dExplanation The TX packet got dropped since the TX ring was full.
Recommended Action This is normal when the port adapter gets overdriven. LOG_STD_NO_ACTION
SARMGR-1
Error Message %SARMGR-1-UNAVAILABLE: The 1575 device analysis failedExplanation The SAR Manager failed its initialization
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
SARMGR-3
Error Message %SARMGR-3-UNAVAILABLE: Device reported %08xExplanation PCI devide ID was not correct.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
SATVS_DNLD-3
Error Message %SATVS_DNLD-3-RS_BOOT_RDY_MEM_FAIL: Unable to allocate space for BOOT_READY msgExplanation The remote switch failed to allocate memory for a BOOT READY message to the virtual switch.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_DNLD-3-RS_BOOT_RDY_SEND_FAIL: Unable to send BOOT_READY messageExplanation The Remote Switch failed in sending a BOOT READY message to the Virtual Switch.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_DNLD-3-RS_DNLD_BAD_EVENT: Got invalid event [hex]:[hex]Explanation An invalid event was 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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_DNLD-3-RS_DNLD_BAD_QUEUE_EVENT: Event on bad queue [hex]Explanation An unknown message queue event was 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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_DNLD-3-RS_DNLD_BAD_TIMER_EVENT: Invalid timer [hex]Explanation An invalid event was received or the message queue was unknown.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_DNLD-3-RS_DNLD_CREATE_PROC_FAIL: Failed to create image download processExplanation Failed to create a message queue on the remote switch for downloading related messages from the virtual switch.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_DNLD-3-RS_DNLD_CREATE_QUEUE_FAIL: Failed to created watched queue for download messagesExplanation Failed to create a message queue on the remote switch for downloading related messages from the virtual switch.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_DNLD-3-RS_DNLD_FAILED: Failed to start download from the Virtual Switch ([chars])Explanation The remote switch was unable to initiate a download from the virtual switch. This could be because of problems in the RSL.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_DNLD-3-RS_DNLD_PROC_FAIL: Download rocess killed. So dropping dnld dataExplanation The download process is not running on the remote switch.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_DNLD-3-RS_MSG_ENQUEUE_FAIL: Unable to enqueue messageExplanation Failed to enqueue a message.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_DNLD-3-VS_BOOT_MSG_INVALID_SWITCH: Invalid switch_id (Internal) [dec] (switch number [dec])! Droppping BOOT_READY msgExplanation An invalid BOOT RDY message was received at the virtual switch.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_DNLD-3-VS_BOOT_RDY_RESP_MEM_FAIL: Unable to allocate memory for BOOT_READY response for [chars] [dec]Explanation The virtual switch failed to allocate memory to send a BOOT READY response message to the remote switch.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_DNLD-3-VS_BOOT_RDY_RESP_SEND_FAIL: Unable to send BOOT_READY response to [chars] [dec]Explanation The virtual switch was unable to send a BOOT READY response message to the remote switch.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_DNLD-3-VS_BOOT_RDY_SCP_RESP_FAIL: scp_send_pak() returned 0 for BOOT_READY resp for [chars] [dec]Explanation The virtual switch was unable to send a valid BOOT READY response message to the remote switch.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_DNLD-3-VS_CREATE_DNLD_INSTANCE_FAIL: Failed to create a download instance for [chars] [dec]Explanation An internal 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_DNLD-3-VS_CREATE_DNLD_PROC_FAIL: Failed to create a download process for [chars] [dec]Explanation An internal 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_DNLD-3-VS_DNLD_IMAGE_INFO_FAIL: Unable to get image info for [chars] [dec]Explanation Failed to get image information for the remote switch from the bundled image.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_DNLD-3-VS_DNLD_IMAGE_VER_INFO_FAIL: Unable to get version for [chars] [dec]Explanation Failed to get image version information for the remote switch from the bundled image.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_DNLD-3-VS_DNLD_UNKNOWN_RS: Unknown RS type [dec] for [chars] sup [dec]Explanation An unknown type of hardware was detected on the remote switch.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_DNLD-3-VS_GET_DNLD_IMAGE_FAIL: Unable to get image for [chars] [dec]Explanation Failed to get image information to be downloaded to the remote switch from the 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_DNLD-3-VS_GET_DNLD_INSTANCE_FAIL: Failed to get the download process instance for Remote SwitchExplanation An internal 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_DNLD-3-VS_GET_PSLOT_FAIL: Unable to get the physical slot for the Remote Switch in virtual slot [dec]Explanation Failed to get physical slot for the remote switch.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_DNLD-3-VS_IMAGE_DNLD_FAIL: Image download of size ([dec]) failed for [chars] [dec]Explanation The virtual switch failed to download the image to the remote switch.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_DNLD-3-VS_INVALID_BOOT_MSG: BOOT_READY message in ONLINE state for [chars] [dec]. NAKingExplanation The virtual switch received an invalid BOOT RDY 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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_DNLD-3-VS_RS_REGISTRY_ADD_FAIL: [chars] registry addition failed.Explanation Failed to create registries during initialization.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_DNLD-3-VS_SET_DNLD_INSTANCE_FAIL: Failed to set the download process instance for [chars] [dec]Explanation An internal 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_DNLD-3-VS_VLSOT_ALLOC_FAIL: Unable to allocate vslot for [chars] [dec] slot [dec]Explanation Failed to allocate a virtual slot to the remote switch.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
SATVS_IBC Messages
This section contains satellite switch virtual switch (VS) interboard communications messages.
SATVS_IBC-3
Error Message %SATVS_IBC-3-VS_IBC_PVTPOOL_PAKALLOC_FAIL: Unable to allocate Pak from VS Inband Private buffer Pool: [chars] Allocating from Public Buffer PoolExplanation Inband packet allocation could not be done from the virtual switch link (VSL) inband private buffer pool due to the reason stated.
Recommended Action No action is required.
Error Message %SATVS_IBC-3-VSL_DOWN_IP_DROP: VSL inactive - dropping cached IP-over-EoBC packet: (SA/DA:[hex]/[hex], eSA/eDA:[enet]/[enet])Explanation The VSL is no longer active. The other virtual switch to which the VSL was attached had one or more IP-over-EoBC packets remaining in the cache after the VSL became inactive (down). The cached IP-over-EoBC packets are being dropped. This condition indicates normal system operation.
Recommended Action No action is required.
Error Message %SATVS_IBC-3-VSL_DOWN_SCP_DROP: VSL inactive - dropping cached SCP packet: (SA/DA:[hex]/[hex], SSAP/DSAP:[hex]/[hex], OP/SEQ:[hex]/[hex], SIG/INFO:[hex]/[hex], eSA:[enet])Explanation The VSL is no longer active. The other virtual switch to which the VSL was attached had one or more SCP packets remaining in the cache after the VSL became inactive (down). The cached SCP packets are being dropped.
Recommended Action No action is required.
SATVS_IBC-5
Error Message %SATVS_IBC-5-VSL_DOWN_IPC_DROP: VSL inactive - dropping cached IPC packet: (SA/DA:[hex]/[hex], SEQ:[hex], Pak_pointer: [hex])Explanation The VSL is no longer active. The other virtual switch to which the VSL was attached had one or more IPC packets remaining in the cache after the VSL became inactive (down). The cached IPC packets are being dropped.
Recommended Action This condition does not affect normal system processing. No action is required.
Error Message %SATVS_IBC-5-VSL_DOWN_SCP_DROP: VSL inactive - dropping cached SCP packet: (SA/DA:[hex]/[hex], SSAP/DSAP:[hex]/[hex], OP/SEQ:[hex]/[hex], SIG/INFO:[hex]/[hex], eSA:[enet])
Explanation The VSL is no longer active. The other virtual switch to which the VSL was attached had one or more SCP packets remaining in the cache after the VSL became inactive (down). The cached SCP packets are being dropped.
Recommended Action This condition does not affect normal system processing. No action is required.
SATVS_UL_MGMT Messages
This section contains satellite switch virtual switch (VS) messages.
SATVS_UL_MGMT-3
Error Message %SATVS_UL_MGMT-3-RS_DNLD_ABORT: Image download aborted because RSL went downExplanation An ongoing remote switch image download was aborted because the remote switch link (RSL) went down. This condition can be caused by any of the following:
- The port channel forming the RSL was shutdown.
- All members of the port channel have been shutdown.
- The cables hooking to all members have been removed.
- The remote switch was deconfigured.
- The remote switch detected another virtual switch with a a better priority value.Recommended Action Check for the above conditions and resolve them. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-RS_HW_PROG_TIMEOUT: H/w programming timed out.Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-RS_INVALID_BNDL_EVENT: Bundle event on already bundled port [chars]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-RS_INVALID_BOOL_EVENT: Invalid boolean event [hex]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-RS_INVALID_EVENT: [chars]: Invalid event [hex]:[hex]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-RS_INVALID_UNBNDL_EVENT: Unbundle event on already unbundled port [chars]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-RS_INV_FAILED: Failed to send inventory data to Virtual Switch. Will keep tryingExplanation The remote switch failed to send inventory data to the virtual switch even though the RSL is up. It will keep trying forever.
Recommended Action Wait 10 minutes for the system to recover from this condition. If the system does not recover, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-RS_NO_PORT_BNDL_NUMBER: No bundle port number in RSL -- SI set to BIT BUCKETExplanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-RS_NO_UPLINK: No uplink to master core -- SI set to BIT BUCKETExplanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_DEALLOC_VSLOT_MSG_FAIL: [chars] for VS UL dealloc vslot msg [dec]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_DROP_INV_MSG: Dropping Inventory message from unknown Remote Switch number [dec] switch-id(Internal) [dec]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_DUP_INV_MSG: NAKing duplicate inventory from Remote Switch number [dec] switch-id(Internal) [dec]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_GET_PSLOT_FAIL: Unable to get the physical slot of supervisor for [chars] [dec]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_GET_SWITCH_NUMBER_FAIL: Unable to get switch number for switch-id(internal) [dec]Explanation Failed to get switch number from internal switch ID. An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_ICC_REQ_FAIL: Unable to alloc memory for status update message for [chars] [chars]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_ICC_RESP_FAIL: icc_get_resp_pak failedExplanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_ICC_RESP_UPLINK_STATUS_FAIL: icc_req_resp_pak to SP failed for [chars] [chars]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_INVALID_BNDL_EVENT: Bundle event on already bundled port [chars] for switch number [dec] switch-id(Internal) [dec]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_INVALID_UNBNDL_EVENT: Unbundle event on already unbundled port [chars] for switch number [dec] switch-id(Internal) [dec]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_INV_FAILED: Failed to process inventory data for Remote Switch [dec]. Will remain OFFLINEExplanation The virtual switch is unable to process the inventory data received from the remote switch even though the RSL is up. This switch will be held offline.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_INV_VER_MISMATCH: Versin of INVENTORY message mismatch. Forcing download to switch number [dec] switch-id(internal) [dec]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_NO_INFO_EM_RECOVERY: No PM info on EM recovery for port [chars]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_NON_INV_MSG: Dropping non-INVENTORY message.Explanation A non-inventory message was received from the remote switch.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_NON_RSL_EM_AGE: EM aging event on non-RSL port [chars]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_NO_SWIDB_EM_AGE: No swidb for EM aging event (gpid = [dec])Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_NO_SWIDB_EM_RECOVERY: No swidb for EM recovery event (gpid = [dec])Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_ADD_PORT_AGPORT_FAIL: Unable to add port [chars] to RSL.Explanation A failure occurred while attempting to add the port to the RSL.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_ADD_TLV_FAIL: Too few bytes for [chars] TLV in PAgP (reqd. [dec], got [dec]) on port [chars]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_BAD_SUB_OPCODE: Dropping bad sub opcode ([hex]) from [chars] [dec]Explanation An invalid message was received from the remote switch. The message could be corrupted.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_BAD_VER_STR: Bad version string - inventory failedExplanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_CF_CLIENT_ADD_FAIL: CF: Failed to create client (err_code = [hex])Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_CF_INVALID_SYNC: CF: TLV sync for unconfigured port ([chars])Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_CHKPT_INVALID_SYNC: CF: Received invalid sync type [hex]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_CHKPT_MSG_FAIL: CF: Send FAIL statusExplanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_CHKPT_MSG_MEM_FAIL: CF: Unable to get chkpt buffer for sync type [hex] (retval [hex])Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_CHKPT_MSG_SEND_FAIL: CF: Unable to sync type [hex] to standby (retval [hex])Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_CLEAR_LTL_INDEX: Unable to clear LTL index [hex] (retval [hex])Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_CREATE_BOOL_FAIL: Failed to create watched boolean to monitor uplink comm upExplanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_CREATE_PROC_FAIL: Failed to create the [chars] processExplanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_CREATE_QUEUE_FAIL: Failed to create watched queue for [chars]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_ENQUEUE_FAIL: Unable to enqueue unsolicited messageExplanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_GET_LTL_PORT_INDEX: Unable to get LTL index for port [chars] (retval [hex])Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_GET_OID_FAIL: Failed to get OID - inventory failedExplanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_GET_UPLINK_INFO_FAIL: Failed to get uplink info for port [chars]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_ICC_REQ_FAIL: RP-SP sync: Unable to get memory for RP-SP sync type [hex]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_IGNORE_ICS_TLV: Ignore ICS TLV on non-uplink port [chars]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_IMAGE_NOT_FOUND: The system failed to find an image to download to Remote Switch [dec]. Will remain OFFLINEExplanation The virtual switch failed to find an image for the remote switch. The remote switch will remain offline.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_IMAGE_NOT_FOUND_INV_RESP: Remote Switch image NOT found in Virtual SwitchExplanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_INVALID_ARGS: Both [chars] [dec] and idb for port ([chars]) specifiedExplanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_INVALID_BOOL_EVENT: Invalid [chars] boolean event [dec]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_INVALID_EVENT: Invalid [chars] event [dec]:[dec]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_INVALID_ICS_TLV: Invalid ICS TLVs from port [chars]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_INVALID_QUEUE_EVENT: Event on invalid [chars] queue [dec]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_INVALID_SW_ID: Invalid switch-id(Internal) [dec]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_INVALID_SWITCH_INFO: switch number [dec] has no switch_infoExplanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_INVALID_TIMER_ID: Invalid [chars] timer [dec]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_INVALID_TLV: Received [chars] TLV on non-uplink port [chars]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_INVALID_TLV_RS: Received Remote Switch side UL mgmt TLV on Remote Switch on port [chars]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_INVALID_TLV_VS: Received Virtual Switch side UL mgmt TLV on Virtual Switch on port [chars] for [chars] [dec]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_INVENTORY_FAIL: Out of memory - inventory failedExplanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_INV_RESP_FAIL: Failed sending INVENTORY response [chars]to [chars] [dec]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_INV_RESP_MEM_FAIL: Alloc failure for INVENTORY response to switch number [dec] switch-id(Internal) [dec]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_INV_SEND_FAIL: Inventory:scp send failed - session [dec]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RSL_BOUNCE: Remote switch [dec] OFFLINE since RSL bouncedExplanation The remote switch is now offline because the remote switch link (RSL) was bounced. This condition can be caused by any of the following:
- An SSO switchover resulted in failures on the RSL line cards that required the RSL to be bounced.
- The remote switch failed to respond to a sanity check request after an SSO switchover.Recommended Action Check for the above conditions. Note that the first condition can occur when the switchover happens during a critical operation on the RSL line card. If this is not the case, or if the second condition occurred, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_LTL_ALLOC_FAIL: Dynamic allocation also failed for Remote Switch private indices (retval [hex])Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_MAX_INV_OID_SIZE: OID too long ([dec]) - inventory failedExplanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_NAK_INV_RESP: Virtual Switch NAKed Inventory.Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_NON_RSL_CONN_INFO_REQ: Dropping non-RSL connect info request messageExplanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_NON_UPLINK_PORT_RM: Attempt to remove port [chars] that is not an uplink of [chars] [dec]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_NO_RS_INFO_INV_SYNC: CF: No Remote Switch info for inventory sync for [chars] [dec]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_NO_RS_INFO_STATE_SYNC: CF: No Remote Switch info for state sync for [chars] [dec]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_NOT_ENOUGH_PRIVATE_INDICES: Not enough private indices (reqd [dec], got [dec]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_NULL_RP_SP_SYNC_MSG: RP-SP sync: Received NULL sync msgExplanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_NULL_SWIDB: Unable to get swidb for port [dec]:[dec].Explanation The specified port has a null software interface descriptor block.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_PO_AGG_RS_OFFLINE: Port [chars] aggregated but switch-id(InternaL) [dec] OFFLINEExplanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_PORT_ADD_REMOVE_ERR: Port ([chars]) add/remove from unconfigured [chars] [dec]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_REGISTRY_ADD_FAIL: [chars] registry addition failedExplanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_RF_CLIENT_ADD_FAIL: RF: Failed to create client (retcode = [hex])Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_RSL_CONN_INFO_RESP_FAIL: No RSL connect info info response received from [chars] [dec]Explanation The RSL connect information response was not heard from the remote switch. This could be due to an invalid switch number, or the virtual switch may not be actively connected to the remote switch at this time.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_RSL_CONN_INFO_RESP_MSG_FAIL: Unable to alloc memory for RSL connect info responseExplanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_RSL_CONN_REQ_MEM_FAIL: Unable to allocate memory for sending RSL connect info request to [chars] [dec]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_RSL_CONN_RESP_SEND_FAIL: Sending RSL connect info response failed.Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_RSL_LTL_INDEX_FAIL: Unable to get the local RSL LTL indexExplanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_SET_LTL_INDEX: Unable to [chars] index [hex] on supervisor [chars] [chars] (retval [hex])Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_SET_PORT_LTL_INDEX: Unable to set LTL index for port [chars] to [hex]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_SET_RSH_MODE: Unable to set RSH mode on port [chars].Explanation The system failed to set RSH mode.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_SET_SRC_INDICES_FAIL: Failed to [chars] SCP msg to set src indices.Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_SSO_EVENT: SSO switchover event in oir_online (slot [dec])-- not supported in Remote SwitchExplanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_TLV_INVALID_METRIC: ICS TLV on [dec] with invalid metric on port [chars]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_RS_VSLOT_ALLOC_FAIL: Unable to alloc vslot for switch number [dec] switch-id(Internali) [dec] slot [dec]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-3-VS_UNKNOWN_MSG: Unknown message type [dec]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
SATVS_UL_MGMT-4
Error Message %SATVS_UL_MGMT-4-RS_RS_MISMATCH: Virtual switch indicates software mismatch. Requesting downloadExplanation Because the software running on the remote switch does not match that in the virtual switch, the proper image will be downloaded.
Recommended Action The image download is automatic. If it fails to complete, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-4-RS_RS_OFFLINE: Remote switch OFFLINE since RSL went downExplanation The remote switch is now offline because the remote switch link (RSL) went down. This condition can be caused by any of the following:
- The port channel forming the RSL was shutdown.
- All members of the port channel have been shutdown.
- The cables hooking to all members have been removed.
- The remote switch was deconfigured.
- The remote switch detected another virtual switch with a a better priority value.Recommended Action Check for the above conditions and resolve them. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-4-VS_GET_PM_COOKIE_FAIL: RF: Unable to get cookie for port [chars]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-4-VS_RS_MAX_UPLINKS_CONF: Attempt to add port [chars] to [chars] [dec] that already has [dec] uplinks to itExplanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-4-VS_RS_MISMATCH: Remote switch [dec] software version mismatch. Forcing downloadExplanation Because the software that is running on the remote switch does not match the software that is running on the virtual switch, matching software will be downloaded to the remote switch.
Recommended Action The image download is automatic. If it fails to complete, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-4-VS_RS_OFFLINE: Remote switch [dec] OFFLINE since RSL went downExplanation The remote switch is now offline because the remote switch link (RSL) went down. This condition can be caused by any of the following:
- The port channel forming the RSL was shutdown.
- All members of the port channel have been shutdown.
- The cables hooking to all members have been removed.
- The remote switch was deconfigured.
- The remote switch detected another virtual switch with a a better priority value.
- The remote switch was powered off.
- The remote switch rebooted.Recommended Action Check for the above conditions and resolve them. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-4-VS_RS_REG_READ_FAIL: Unable to read register [hex] of port [chars]Explanation The virtual switch failed to read the port adapter registers to verify that RSH is enabled on them.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-4-VS_RS_RS_CONF: Attempt to [chars]-configure [chars] [dec]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-4-VS_RS_VLAN_BLOCK: Unable to [chars] VLANS [hex] - [hex] for [chars]Explanation The system could not block or unblock a range of VLANs.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
SATVS_UL_MGMT-5
Error Message %SATVS_UL_MGMT-5-RS_ICS_SWITCHOVER: ICS swtichover due to priority change on RSL member [chars] from Virtual Switch [enet]Explanation The remote switch has detected a priority change at the virtual switches and will do an ICS switchover to a new virtual switch. All RSL members, except the one from which the priority change was detected, will be bounced to allow faster detection of this situation at the virtual switches.
Recommended Action This is an informational message. No action is required.
Error Message %SATVS_UL_MGMT-5-RS_RSL_DOWN: RSL is DOWNExplanation The remote switch link is down.
Recommended Action This is an informational message. No action is required.
Error Message %SATVS_UL_MGMT-5-RS_RSL_UP: RSL is UPExplanation The remote switch link is up.
Recommended Action This is an informational message. No action is required.
Error Message %SATVS_UL_MGMT-5-RS_RSL_UP_INV: RSL is UP. Sending inventory dataExplanation The remote switch link is up. The remote switch is sending inventory data to the virtual switch.
Recommended Action This is an informational message. No action is required.
Error Message %SATVS_UL_MGMT-5-RS_RS_ONLINE: Remote switch is ONLINE. Exporting line card data to Virtual SwitchExplanation The remote switch is now online. The virtual switch will now look for line cards on the remote switch and try to bring them online.
Recommended Action This is an informational message. No action is required.
Error Message %SATVS_UL_MGMT-5-VS_RSL_UP: RSL to Remote Switch [dec] is UP. Waiting for inventory dataExplanation The remote switch link is up and waiting for inventory from the remote switch.
Recommended Action This is an informational message. No action is required.
Error Message %SATVS_UL_MGMT-5-VS_RS_ONLINE: Remote switch [dec] ONLINE. Looking for line cards on itExplanation The remote switch is now online. The virtual switch will now look for line cards on the remote switch and try to bring them online.
Recommended Action This is an informational message. No action is required.
SATVS_UL_MGMT-6
Error Message %SATVS_UL_MGMT-6-RS_RSL_MEMBER_BOUNCE: RSL member [chars] bounced due to unbundle actionExplanation The RSL member was bounced after it became unbundled.
Recommended Action This is an informational message. No action is required.
Error Message %SATVS_UL_MGMT-6-RS_VS_RSL_BOUNCE: RSL members to the active Virtual Switch bounced as RSL went downExplanation Because the remote switch link (RSL) is down, all members to the same virtual switch are bounced to allow the virtual switch to recognize the RSL down condition.
Recommended Action This is an informational message. No action is required.
Error Message %SATVS_UL_MGMT-6-VS_RS_INVALID_RP_SP_SYNC_TYPE: RP-SP sync: Received invalid sync type [hex]Explanation An internal RP-SP synchronization error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_UL_MGMT-6-VS_RSL_MEMBER_BOUNCE: RSL member [chars] bounced due to unbundle actionExplanation The remote switch link (RSL) member was bounced after it became unbundled.
Recommended Action This is an informational message. No action is required.
SATVS_WARM_UPGRADE Messages
This section contains satellite switch virtual switch (VS) warm upgrade messages.
SATVS_WARM_UPGRADE-3
Error Message %SATVS_WARM_UPGRADE-3-VS_RS_BAD_SUB_OPCODE: (WUG)Dropping bad sub opcode ([hex]) from [chars] [dec]Explanation Received an invalid message from the remote switch. The message could be corrupted.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_WARM_UPGRADE-3-VS_RS_INVALID_EVENT: Invalid [chars] event [dec]:[dec]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_WARM_UPGRADE-3-VS_RS_INVALID_QUEUE_EVENT: Event on invalid [chars] queue [dec]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_WARM_UPGRADE-3-VS_RS_WUG_RESP_FAIL: Failed sending WARM_UPGRADE response [chars]to [chars] [dec]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_WARM_UPGRADE-3-VS_RS_WUG_RESP_MEM_FAIL: Alloc failure for WARM_UPGRADE_RESP to switch-id(Internal) [dec]Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_WARM_UPGRADE-3-VS_RS_WUG_SEND_FAIL: WUG start:scp send failedExplanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SATVS_WARM_UPGRADE-3-VS_RS_WUG_TEST: Test msg_satvs_warm_upgradeExplanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
SBFIFO Messages
This section contains packet first-in, first-out (FIFO) MAC controller messages.
SBFIFO-1
Error Message %SBFIFO-1-BAD_IDB: Invalid Interface Descriptor BlockExplanation The driver failed to get the interface descriptor block (IDB).
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %%SBFIFO-1-BAD_PARTICLE: Problem getting particle sizeExplanation The driver was unable to obtain the particle size for this interface.
Recommended Action This is a software bug. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SBFIFO-1-BAD_POOL: Could not init buffer poolsExplanation The driver failed to obtain a pool of buffers from the Cisco IOS software.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SBFIFO-1-BAD_SB_NOMEM: [chars] - Cannot create IDB subblock due to insufficient memoryExplanation There was insufficient system memory to create the subblock.
Recommended Action The router requires more main memory. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SBFIFO-1-BAD_STRUCT: Could not initialize structureExplanation The driver failed to initialize a structure.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SBFIFO-1-BAD_SUBBLOCK: [chars] - Could not install or use IDB subblockExplanation An internal Cisco IOS error prevented the IDB subblock from being installed or used.
Recommended Action This is a software bug. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SBFIFO-1-IDBTYPE_UNK: Unknown IDBTYPE while starting driverExplanation The IDBTYPE in the interface's instance structure is undefined for this driver.
Recommended Action This is a software bug. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SBFIFO-1-INITFAIL_NOMEM: [chars], initialization failed, no buffer memoryExplanation The Ethernet port initialization failed due to insufficient memory. The router requires more packet memory.
Recommended Action Consider a system upgrade. 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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SBFIFO-1-MODE_INVALID: Unknown or invalid chip mode (MII/TBI)Explanation The driver subblock contains an invalid or undefined chip operating mode (MII or TBI mode).
Recommended Action This is a software bug. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SBFIFO-1-RESET: MAC-FIFO Still in ResetExplanation An attempt was made to access the MAC-FIFO while it was in reset.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
SBFIFO-3
Error Message %SBFIFO-3-ERRINT: [chars], error interrupt, mac_status = [hex]Explanation The MAC-FIFO controller signalled an error condition.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SBFIFO-3-TOOBIG: [chars], packet too big ([dec]), from [enet]Explanation The interface detects a packet larger than the value that is defined by MTU.
Recommended Action Determine the MTU setting of the other station. No action is required.
SCCP-0
Error Message %SCCP-0-UNAVAILABLE: %sExplanation Unrecoverable Internal Panic
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
SCCP-2
Error Message %SCCP-2-UNAVAILABLE: %sExplanation Critical Conditions
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
SCCP-3
Error Message %SCCP-3-UNAVAILABLE: %sExplanation Errors
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
SCCP-4
Error Message %SCCP-4-UNAVAILABLE: %sExplanation Warning
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
SCCP-5
Error Message %SCCP-5-UNAVAILABLE: %sExplanation Notice
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
SCCP-6
Error Message %SCCP-6-UNAVAILABLE: %sExplanation Informational
Recommended Action LOG_STD_NO_ACTION
SCHED Messages
This section contains scheduler messages.
SCHED-0
Error Message %SCHED-0-UNAVAILABLE: Interrupt of level %ld running for a long time.%sExplanation The indicated Interrupt Service Routine ran for more than 2 minuteswithout relinquishing control and so caused the system to reset
Recommended Action When reporting this message, copy the message text exactly as it appears; include the stack trace; and report it to your technical support representative.
Error Message %SCHED-0-UNAVAILABLE: Scheduler running for a long time, more than the maximum configured (%ld) secs.%sExplanation Scheduler was running for a long time and so caused the system to reset
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
SCHED-2
Error Message %SCHED-2-UNAVAILABLE: %s attempted to unlock an unlocked semaphoreExplanation Some sections of code use semaphores to protect critical sections of software. This message indicates that an attempt was made to unlock a semaphore that was not locked.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SCHED-2-UNAVAILABLE: %s attempted to unlock semaphore owned by %s.Explanation Some sections of code use semaphores to protect critical sections of software. This message indicates that an attempt was made to unlock a semaphore that was not owned by the process attempting to unlock it.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SCHED-2-UNAVAILABLE: %s timer %x not being watched.Explanation A process can register to be notified when various events occur in the router. This message indicates that an attempt was made to deregister a timer expiration event that is not currently registered.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SCHED-2-UNAVAILABLE: Attempt to %s attribute %s on process %d.Explanation Each process has various public and private attributes associated with it. This message indicates that an attempt was made to set or get a private attribute belonging to another process.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SCHED-2-UNAVAILABLE: Attempt to %s unknown process attribute %d.Explanation Each process has various attributes associated with it. This message indicates that an attempt was made to set or get a nonexistent process attribute.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SCHED-2-UNAVAILABLE: Attempt to delete non-empty watched queue %s (address %x).Explanation A process can register to be notified when various events occur in the router. This message indicates that an attempt was made to destroy a queue that still contained items. These items are lost and not returned to free memory.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SCHED-2-UNAVAILABLE: Attempt to set %s priority on process %d (%s)Explanation Each process executes at a specified priority level. Higher priority processes must use the new scheduler primitives, while lower priority processes can use primitives from either the new or old scheduler. This message indicates that an attempt was made to set the specified priority too high for a process using old scheduler primitives.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SCHED-2-UNAVAILABLE: Attempt to set bad %s value (%x) on process %dExplanation Each process has various attributes associated with it. This message indicates that an attempt was made to set the specified attribute to an invalid value.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SCHED-2-UNAVAILABLE: Critical/high priority process %s may not dismiss.Explanation Each process executes at a specified priority level. Higher priority processes must use the new scheduler primitives, while lower priority processes can use primitives from either the new or old scheduler. This message indicates that a higher priority process attempted to use an old scheduler primitive.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SCHED-2-UNAVAILABLE: Key (%s) does not match key (%s) of process (%d) in process_send_message requestExplanation An attempt was made to send a message to a process. The key associated with that process did not match the key in the message. This usually means an incorrect process id was used in the send message request.
Recommended Action Copy the error message exactly as it appears; include the stack trace; and report it to your technical support representative. If this message recurs, revert to an IOS image that did not exhibit this behavior.
SCHED-3
Error Message %SCHED-3-UNAVAILABLE: %s attempted to lock a semaphore, already locked by itselfExplanation Some sections of code use semaphores to protect critical sections of software. This message indicates that an attempt was made to lock a semaphore that was already locked.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SCHED-3-UNAVAILABLE: Illegal priority (%d) specified for process %s.Explanation Each process executes at a specified priority level. Higher priority processes must use the new scheduler primitives, while lower priority processes can use primitives from either the new or old scheduler. This message indicates that an attempt was made to set the specified process to a priority level that is not allowed for the type of scheduler primitives used.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SCHED-3-UNAVAILABLE: Illegal stack size (%d) specified for process %s.Explanation Each process has its own stack space, which must be one of several predefined sizes. This message indicates that an attempt was made to specify an illegal stack size.
Recommended Action Copy the error message exactly as it appears; include the stack trace; and report it to your technical support representative. If this message recurs, revert to a previous IOS image that did not exhibit the problem.
Error Message %SCHED-3-UNAVAILABLE: Invalid scheduler action (%s) at interrupt levelExplanation This message indicates that a process_set_wakeup_reasons was attempted from an interrupt handler.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message %SCHED-3-UNAVAILABLE: Low memory modified by %s (%#x = %#x)Explanation In all Cisco products, the first 256 bytes of memory are unused and are off limits. Newer platforms have hardware to immediately trap reads or writes to this area. Older platforms periodically check this memory. This message appears only on older platforms and indicates that this off-limits memory area was modified.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SCHED-3-UNAVAILABLE: Process received unknown event (maj %x, min %x).Explanation A process can register to be notified when various events occur in the router. This message indicates that a process received an event it did not know how to handle.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SCHED-3-UNAVAILABLE: Process still watching %s %sExplanation A process can register to be notified when various events occur in the router. This message indicates that a process destroyed a set of events without first individually removing each event in the set.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SCHED-3-UNAVAILABLE: Process still watching %s timer %xExplanation A process can register to be notified when various events occur in the router. This message indicates that a process destroyed a set of events without first individually removing each event in the set.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SCHED-3-UNAVAILABLE: Process thrashing on watched %s.Explanation A process can register to be notified when various events occur. This message indicates that the indicated process relinquished control 50 consecutive times and there were still outstanding events to be processed.
Recommended Action Copy the error message exactly as it appears, include the stack trace; and report it to your technical support representative.
Error Message %SCHED-3-UNAVAILABLE: Queue event for unknown queue (index %d).Explanation A process can register to be notified when various events occur in the router. This message indicates that a process received a queuing event for an unknown queue.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SCHED-3-UNAVAILABLE: Scheduler '%s' corrupted by process %s (expected %x, found %x)Explanation The scheduler has determined that its data structures were corrupted during the execution of the current process. This corruption is the result of either the actions of the process (multiple errors reported against the same process) or an interrupt driver (multiple errors reported against different processes).
Recommended Action This message is a sign of memory corruption. Copy the error message text exactly as it appears; include the stack trace; and report it to your technical support representative. Reset the system. If this message re-occurs, revert to a previous release of IOS.
Error Message %SCHED-3-UNAVAILABLE: Sleep with expired managed timer %x, time %#Ta (%TE ago).Explanation A process can register to be notified when various events occur. This message indicates that a registered timer has expired and its value is unchanged after the process has received control twice.
Recommended Action Copy the error message exactly as it appears, include the stacktrace; and report it to your technical support representative. Reset the system. If the error recurs, revert to a previous IOS image that did not exhibit the problem.
Error Message %SCHED-3-UNAVAILABLE: Sleep with expired timer %x, time %#Ta (%TE ago).Explanation A process can register to be notified when various events occur. This message indicates that a registered timer has expired and its value is unchanged after the process has received control twice.
Recommended Action Copy the error message exactly as it appears; include the stack trace; and report it to your technical support representative.
Error Message %SCHED-3-UNAVAILABLE: Unknown message %x received (ptr arg %x, num arg %x).Explanation A process can register to be notified when various events occur in the router. This message indicates that a process received a message from another process that it does not know how to handle.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SCHED-3-UNAVAILABLE: Unknown timer expiration, timer = %x, type %d.Explanation A process can register to be notified when various events occur in the router. This message indicates that a process received a timer expiration event for an unknown timer.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SCHED-3-UNAVAILABLE: Wakeup information for process %s lost (maj %x, min %x).Explanation A process can register to be notified when various events occur in the router. This message indicates that an event for the specified process was lost and that the system might not be functioning correctly.
Recommended Action Copy the error message text exactly as it appears; include the stack trace; and report it to your technical support representative. Reset the system.
SCHED-4
Error Message %SCHED-4-UNAVAILABLE: Invalid argument (%d msec) for process_set_schedtimeExplanation This message indicates that there was an attempt to change the maximum time a process can run per scheduling to an invalid value. The value should range between 20msec to 200msec
Recommended Action Copy the error message exactly as it appears; include the stack trace; and report it to your technical support representative. If this message recurs, revert to an IOS image that did not exhibit this behavior.
SCHED-7
Error Message %SCHED-7-UNAVAILABLE: Attempt to %s uninitialized watched %s (address %x).Explanation A processes can register to be notified when various events occur. This message indicates that an attempt was made to register for an event without first creating the data structure for that event.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
SCP Messages
This section contains Switch Module Configuration Protocol (SCP) messages.
SCP-1
Error Message %SCP-1-TASK_CREATE_FAIL: Failed to create SCP Generic Unsolicited message handler taskExplanation The system could not spawn a process that handles certain types of incoming SCP packets. This could be due to low memory on the switch, in which case other related errors may appear.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
SCP-3
Error Message %SCP-3-ETHERTYPE_FAIL: Ethertype configuration on module [dec], port [dec], failed with return code [hex]Explanation The EtherType configuration failed on the specified port. This usually means that the module hardware does not support the EtherType configuration. The return error code provides more information.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SCP-3-SCP_HA_FAIL: SCP HA Seq Set - Module: [dec] failed [dec] timesExplanation The system did not receive the SCP HA sequence set acknowledgment.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
SCP-4
Error Message %SCP-4-UNK_OPCODE: Received unknown unsolicited message from src_addr [hex], dest_addr [hex], length [dec], dsap [dec], ssap [dec], opcode [hex]Explanation An unsupported SCP message was sent to this processor.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
SCP-5
Error Message %SCP-5-ASYNC_WATERMARK: [dec] messages pending in [chars]Explanation The specified number of SCP messages are waiting in the specified local queue. This condition might indicate that the SP is generating many messages, that the SP is too busy to send them, or that the module cannot process them at a faster pace. In most cases, this condition occurs when there is heavy control plane activity, such as the formation of Layer 2 trunks, the addition of new VLANs, or the toggling of links.
Recommended Action Determine if the SP is busy or if there is interface link toggling. If this condition persists for more than five minutes, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SCP-5-ENABLE: Module enabled [chars]Explanation The supervisor engine sent a message to the router to indicate that a module has been enabled.
Recommended Action No action is required.
SDLC Messages
This section contains Synchronous Data Link Control (SDLC) protocol messages.
SDLC-2
Error Message %SDLC-2-UNAVAILABLE: %s, illegal state for addr %02x, %s(%d)Explanation An internal SDLC state violation 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SDLC-2-UNAVAILABLE: AW_SDLC_SEC with no sdllc_llc pointer.Explanation An error condition occurred during SDLLC initiation.
Recommended Action No action is required. The SDLLC session will restart without operator intervention.
Error Message %SDLC-2-UNAVAILABLE: No memory available: %sExplanation The requested operation failed because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
SDLC-3
Error Message %SDLC-3-UNAVAILABLE: %s, DLU failed to close station %02x before re-opening, %s/%sExplanation A hardware or software error occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SDLC-3-UNAVAILABLE: %s, addr %02x, Sent SNRM, received SNRM. Check link station roles.Explanation A hardware or software error occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SDLC-3-UNAVAILABLE: Input idb not setExplanation This is a software error. A frame was given to the SDLC handler to process, but the interface on which the frame arrived is not known.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SDLC-3-UNAVAILABLE: Interface %s, NULL packet ptr, rvr %d, vs %d, vr %dExplanation An internal software error occurred in the router's SDLC processing system.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
SDLC-4
Error Message %SDLC-4-UNAVAILABLE: %s, XID mismatch for %02x. CONNECTION REJECTEDExplanation An inbound exchange identification (XID) from a PU 2.0/PU 2.1 node was rejected. The targeted SDLC address is displayed. The XID information is displayed in a subsequent message = SDLLC-6-XID_DISPLAY or SDLLC-6-FORMAT.
Recommended Action This is a security feature. Additional information is displayed to help trace the source of the rejected XID. If the message is undesirable, simply remove the XID statement from the router configuration.
Error Message %SDLC-4-UNAVAILABLE: %s, Received bad SDLC %sframe, address %02x, control %2XExplanation A hardware or software error occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SDLC-4-UNAVAILABLE: %s, addr %02x received command %02x in response to SNRM, expected UAExplanation The router received a frame other than a UA in response to a SNRM.
Recommended Action Check the end station to see if the SNA stack is up and running.
Error Message %SDLC-4-UNAVAILABLE: Dropped SDLC packet from SDLC hold queueExplanation An SDLC frame had to be dropped from the output hold queue, usually because of excessive congestion on the output link.
Recommended Action If this message occurs frequently, determine why your SDLC link is being overloaded with data and resolve the cause (typically by either increasing bandwidth to your SDLC line or reducing the load on your link).
Error Message %SDLC-4-UNAVAILABLE: Interface %s, Frame error: CF %#x, VS %d %c VR %d, Reason %#xExplanation A FRMR frame was received. This can be due to a noisy serial line, an overloaded SDLC device, or corrupted data.
Recommended Action If this message recurs, service the serial line and the devices attached to it.
Error Message %SDLC-4-UNAVAILABLE: Interface %s, Info field not permittedExplanation A bad SDLC frame was received.
Recommended Action If this message recurs, check the SDLC serial line and the devices attached to it.
Error Message %SDLC-4-UNAVAILABLE: Interface %s, Invalid NR valueExplanation A bad SDLC frame was received.
Recommended Action If this message recurs, check the SDLC serial line and the devices attached to it.
Error Message %SDLC-4-UNAVAILABLE: Interface %s, Invalid control fieldExplanation A bad SDLC frame was received.
Recommended Action If this message recurs, check the SDLC serial line and the devices attached to it.
Error Message %SDLC-4-UNAVAILABLE: Interface %s, N1 too largeExplanation An information frame was received from the other end of the SDLC link that was larger than allowed with the N1 parameter on this link.
Recommended Action Either increase the value of the N1 parameter for this interface on the router or reduce the size of the maximum information frame sent by the other end of the link.
Error Message %SDLC-4-UNAVAILABLE: Interface %s, ignoring group-poll mismatch, UPOLL %02xExplanation A hardware or software error occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SDLC-4-UNAVAILABLE: SDLC_ERROR with no pollExplanation A protocol error was detected on a secondary station, but FRMR could not be sent because the station did not own the poll bit. This message indicates either poor line conditions or a faulty SDLC implementation.
Recommended Action If this message recurs, run traces on the SDLC line. Copy the error message exactly as it appears, and report it to your technical support representative.
SDLC-5
Error Message %SDLC-5-UNAVAILABLE: Interface %s, not configured for group-poll frame, received %02xExplanation An unnumbered poll (UP) was received with the wrong group poll address.
Recommended Action Make sure the group poll address configured on the router matches the one configured in the physical unit macro (GP3174=XX) in the Network Control Program (NCP) generate file.
SDLC-6
Error Message %SDLC-6-UNAVAILABLE: sa %e da %e ss %x ds %x [%02x%02x%02x%02x]Explanation This message supplies the information for the received and rejected XID.
Recommended Action See the SDLC-6-XID_NOMATCH error message.
Error Message %SDLC-6-UNAVAILABLE: Unsupported XID format received, format %dExplanation An inappropriate exchange identification (XID) format was received for this mode of SDLLC operation. Review the type of devices you are connecting with SDLLC to make sure they are supported.
Recommended Action See the SDLLC-6-XID_NOMATCH error message.
SDLLC-5
Error Message %SDLLC-5-UNAVAILABLE: SDLLC: %s LINK address %02x ACTIVATED: %sExplanation An SDLLC media conversion session was activated.
Recommended Action LOG_STD_NO_ACTION
Error Message %SDLLC-5-UNAVAILABLE: SDLLC: %s LINK address %02x DEACTIVATED: %sExplanation An SDLLC media conversion session was deactivated. If deactivation is a result of an error condition, this message will include a reason.
Recommended Action If the message does not include a description of an error, the deactivation was normal and the message is for information only. If the message does include a description of an error, begin problem analysis. Determine whether session loss is related to LLC2 timers by issuing the debug llc2-err command. If the problem is related to LLC2 timers, consider using SDLLC with the local acknowledgment feature. Copy the error message exactly as it appears, and report it to your technical support representative.
SDM Messages
This section contains Security Device Manager (SDM) template messages.
SDM-6
Error Message %SDM-6-MISMATCH_ADVISE: [chars]Explanation This message provides information regarding an SDM mismatch.
Recommended Action No action is required.
SEC_LOGIN Messages
This section contains Secure Login messages.
SEC_LOGIN-1
Error Message %SEC_LOGIN-1-QUIET_MODE_ON: Still timeleft for watching failures is [int] secs, [user: [chars]] [Source: [IP_address]] [localport: [int]] [Reason: [chars]] [ACL: [chars]] at [chars]Explanation Quiet mode is now on. No request for connections are now accepted other than those allowed by the ACL, if the ACL is configured for the blocking period. An implicit deny all of any logins will be in effect.
Recommended Action Because all requests from other sources are blocked, check the ACL and add any source addresses as necessary.
SEC-2
Error Message %SEC-2-UNAVAILABLE: Box secured, no option on internal packetExplanation An internal software error occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %SEC-2-UNAVAILABLE: First opt in tcb not BASIC securityExplanation An internal software error occurred.
Recommended Action If this message recurs, contact your technical support representative.
Error Message %SEC-2-UNAVAILABLE: Security opt in tcb not SECINSERTExplanation An internal software error occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
SEC_LOGIN-3
Error Message %SEC-3-UNAVAILABLE: No default for NLESO definedExplanation An internal software error occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
SEC_LOGIN-4
Error Message %SEC_LOGIN-4-25: Login failed [user: [chars]] [Source: [IP_address]] [localport: [int]] [Reason: [chars]] at [chars]Explanation A user name or password is invalid.
Recommended Action Specify a vaild user name or password.
SEC_LOGIN-5
Error Message %SEC_LOGIN-5-LOGIN_SUCCESS: Login Success [user: [chars]] [Source: [IP_address]] [localport: [int]] at [chars]Explanation Login has succeeded.
Recommended Action No action is required.
Error Message %SEC_LOGIN-5-QUIET_MODE_OFF: Quiet Mode is OFF, because [chars] at [chars]Explanation Quiet mode is now off. The router is now operating in normal connection processing mode. The reason for the change is specified in the message text.
Recommended Action No action is required.
SEC-6
Error Message %SEC-6-UNAVAILABLE: access-list logging rate-limited or missed %d packet%sExplanation Some packet matching logs were missed because the access list log messages were rate-limited or no access list log buffers were available.
Recommended Action LOG_STD_NO_ACTION
Error Message %SEC-6-UNAVAILABLE: list %s %s %d %i %s- %i, %d packet%sExplanation A packet matching the log criteria for the given access list was detected.
Recommended Action LOG_STD_NO_ACTION
Error Message %SEC-6-UNAVAILABLE: list %s %s %i %d packet%sExplanation A packet matching the log criteria for the given access list was detected.
Recommended Action LOG_STD_NO_ACTION
Error Message %SEC-6-UNAVAILABLE: list %s %s %s %i %s- %i (%d/%d), %d packet%sExplanation A packet matching the log criteria for the given access list was detected.
Recommended Action LOG_STD_NO_ACTION
Error Message %SEC-6-UNAVAILABLE: list %s %s %s %i %s- %i, %d packet%sExplanation A packet matching the log criteria for the given access list was detected.
Recommended Action LOG_STD_NO_ACTION
Error Message %SEC-6-UNAVAILABLE: list %s %s %s %i(%d) %s- %i(%d), %d packet%sExplanation A packet matching the log criteria for the given access list was detected.
Recommended Action LOG_STD_NO_ACTION
SEP-3
Error Message %SEP-3-UNAVAILABLE: %sExplanation Sep subsystem has experienced a problem gettting the required memory to complete this operation.
Recommended Action Check system memory for other memory allocation errors and contact Technical support for problem resolution. In the absence of IOS errors upgrading the memory in the network device may be required.
SERIAL-0
Error Message %SERIAL-0-UNAVAILABLE: %s (slot %d) %s %dExplanation A very high rate of bad packets were received on the specified port. This can happen due to port mis-configuration - specially for mis-matched DSU subrates (most common with Kentrox). The port is shutdown for this reason so that the line card is not overwhelmed with these bad packets.
Recommended Action Verify that the configuration is correct and matching on both ends of the connection. These include clock source (one end line, other internal), DSU (mode and subrate), encapsulation. Also verify the physical condition on the line (run BERT or other tests), signal strength, cable length.
Error Message %SERIAL-0-UNAVAILABLE: %s HW DLLS failed to lock in linecard at slot %dExplanation The DS3 line card could not initialize. The line card is deactivated
Recommended Action Try to reactivate the line card using the hw-module slot slot-number start command. If the error persists, copy the error message exactly as it appears on the console or in the system log. Enter the show diag slot-number command to gather additional data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative with the gathered information
Error Message %SERIAL-0-UNAVAILABLE: %s Linecard local processor at slot %d failed to bootExplanation The DS3 line card local processor boot code did not initialize properly. The line card will be deactivated. This error indicates a line card hardware failure
Recommended Action Enter the hw-module slot slot-number start command to try and reactivate the card. If the line card does not recover from the error, copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather additional data, and contact your Cisco technical support representative with the gathered information
Error Message %SERIAL-0-UNAVAILABLE: %s initialization failure for slot %d, %sExplanation The DS3 line card driver has failed to initialize properly. This indicates a software initialization issue. The line card is deactivated
Recommended Action Try to reactivate the line card using the hw-module slot slot-number start command. If the error persists, copy the error message exactly as it appears on the console or in the system log. Enter the show diag slot-number command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show diag slot-number output, contact your Cisco technical support representative with the gathered information.
SERIAL-1
Error Message %SERIAL-1-UNAVAILABLE: %s (slot %d) %s Allocation failure.Explanation The DS3 driver data structure could not be allocated during line card initialization. This condition occurs when the system is running low on memory because of a misconfiguration or because the memory installed in the system is not large enough to meet the demands of different applications in high traffic conditions. The line card is deactivated on this error.
Recommended Action Try to reactivate the line card using the hw-module slot slot-number start command. If the error recurs, check the system configuration for the amount of Route Processor-switched traffic. A large amount of Route Processor switched traffic can cause this error, so reconfigure the system for less Route Process switched traffic if possible. If the amount of installed memory can be upgraded, consider upgrading main memory by removing and replacing the SDRAM SODIMM. If the problem persists, collect the show tech-support command output and the error message exactly as it appears on the console and contact your Cisco technical support representative
Error Message %SERIAL-1-UNAVAILABLE: %s line card firmware in slot %d crashedExplanation DS3 linecard firmware crashed
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
SERIAL-3
Error Message %SERIAL-3-UNAVAILABLE: %s %d/%d%s hardware IDB is missingExplanation DS3 port hardware IDB is missing
Recommended Action Copy the error message exactly as it appears on the console or in the system log and call your Cisco technical support representative.
Error Message %SERIAL-3-UNAVAILABLE: %s (slot %d) %s HDLC, %s %s%s. (src=0x%x, det1=0x%x, det2=0x%x)Explanation A hardware race condition, which occurs when access to shared memory is not properly synchronized, has occurred. The linecard has been deactivated and an automatic recovery has been initiated. If the error occurs more than five times within an hour, the line card will not be reactivated
Recommended Action The linecard can be reactivated manually using the hw-module slot slot-number start command if it has been deactivated after five failures. If the error persists, copy the error message exactly as it appears on the console or in the system log. Enter the show diag slot-number command to gather additional data , and contact your Cisco technical support representative with the gathered information.
Error Message %SERIAL-3-UNAVAILABLE: %s (slot %d) %s HDLC, %s. %s, port %d (src=0x%x, det1=0x%x, det2=0x%x)Explanation The High-Level Data Link Control (HDLC) engine inside the HDLC ASIC on the line card detected unrecoverable errors. The line card is deactived and then an automatic recovery is initiated. If this error occurs more than five times within an hour, the line card is deactivated
Recommended Action If the line card is no longer automatically reactivating, copy the error message exactly as it appears on the console or in the system log, enter the show version and show diag slot-number commands to gather additional data, and contact your Cisco technical support representative with the gathered information to determine whether to replace the line card or upgrade the IOS version.
Error Message %SERIAL-3-UNAVAILABLE: %s (slot %d) %s HDLC, %s. %s=0x%x%s. (src=0x%x, det1=0x%x, det2=0x%x)Explanation A parity error occurred in the HDLC engine SRAM memory. The source of the problem is a hardware failure. The line card has been deactivated and automatically reactivated. If this error occurs more than five times in an hour, the automatic reactivation will not occur after the fifth reactivation and the line card will remain deactivated
Recommended Action If the line card is no longer automatically reactivating, copy the error message exactly as it appears on the console or in the system log, enter the show diag slot-number command to gather additional data, and contact your Cisco technical support representative with the gathered information for a replacement of the line card.
Error Message %SERIAL-3-UNAVAILABLE: %s (slot %d) %s HDLC, %s. BMA_DATA[3:0]=0x%x. (src=0x%x, det1=0x%x, det2=0x%x)Explanation A parity error occurred on the High-Level Data Link Control Broadcast Multi-Access (HDLC BMA) engine data bus. The line card has been deactivated and subsequently reactivated. If the error occurs more than five times within an hour, the line card will not be reactivated. This message is likely due to a hardware failure
Recommended Action If the line card has been deactivated, copy the error message exactly as it appears on the console or in the system log, enter the show diag slot-number command to gather additional data that may help identify the nature of the error, and contact your Cisco technical support representative with the gathered information
Error Message %SERIAL-3-UNAVAILABLE: %s Corrupt configuration, unsupported %s (%u) encounteredExplanation The running configuration for the DS3 line card is corrupted. The DS3 driver data structures which store snapshots of interface configurations are corrupted or are not correctly updated with the corresponding interface configurations in NVRAM. This problem is caused by a software caveat
Recommended Action Attempt a graceful OIR of the line card by removing and reinserting the line card into the same slot or into another slot. A graceful OIR can also be performed by entering the hw-module slot slot-number stop command followed by the hw-module slot slot-number start command. If the problem persists, copy the error message exactly as it appears on the console or in the system log, enter the show tech-support command to gather additional data, and contact your Cisco technical support representative with the gathered information.
Error Message %SERIAL-3-UNAVAILABLE: %s DS3 LC(slot %d), %sExplanation An informational message has been sent from the DS3 line card firmware to the system main processor on the NSE
Recommended Action None. Just an informational message from firmware.
Error Message %SERIAL-3-UNAVAILABLE: %s Interface %s received an unknown far end request (%u)Explanation The DS3 driver received an unknown FEAC code from the far end of the link. The request has been ignored. This is not a catastrophic condition
Recommended Action Check the configurations at both ends of the connection. If the configuration appears correct, copy the error message exactly as it appears on the console or in the system log. Enter the show controller serial slot-number/port-number command to gather additional data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show controller serial slot-number/port-number output, contact your Cisco technical support representative with the gathered information.
Error Message %SERIAL-3-UNAVAILABLE: %s Loss of keepalives from linecard in slot %dExplanation The system main processor is not receiving keepalive messages from the line card local processor. The source of the problem could be a line card hardware failure or a software failure. The line card has been deactivated and will be automatically reactivated. If this error occurs more than five times in an hour, the automatic reactivation will not occur and the line card will remain deactivated.
Recommended Action If the line card is no longer automatically reactivating, copy the error message exactly as it appears on the console or in the system log, enter the show version and show diag slot-number commands to gather additional data, and contact your Cisco technical support representative with the gathered information to determine whether to replace the line card or upgrade the IOS version
Error Message %SERIAL-3-UNAVAILABLE: %s Slot %d: %sExplanation A daughter card was detected in the line card in the specified slot. The line card has been disabled since the daughter card is not supported. If the message appears even though no daughter card is present on the line card, an I2C bus access failure has occurred on the line card
Recommended Action Remove the line card and inspect it for any daughter card. If present, unmount the daughter card from the line card. After removing the daughter card, or if no daughter card was found, reinsert the line card. If the error persists, copy the error message exactly as it appears on the console or in the system log, enter the show tech-support command to gather additional data, and contact your Cisco technical support representative with the gathered information
Error Message %SERIAL-3-UNAVAILABLE: %s linecard boot code in slot %d crashed, reason: %s (0x%x)Explanation The DS3 line card local processor boot code crashed. This error message indicates a line card hardware failure. The line card will be deactivated.
Recommended Action Manually attempt to activate the line card using the hw-module slot slot-number start command and check if the linecard recovers from the error. If the error persists, copy the error message exactly as it appears on the console or in the system log, enter the show diag slot-number command to gather additional data, and contact your Cisco technical support representative with the gathered information
Error Message %SERIAL-3-UNAVAILABLE: %s linecard boot code in slot %d not ready for firmware download, boot code status 0x%xExplanation The DS3 line card boot code did not initialize properly. This error message indicates a line card hardware failure. The line card will be deactivated
Recommended Action Manually attempt to initialize the line card using the hw-module slot slot-number start command and check if the linecard recovers from the error. If the error persists, copy the error message exactly as it appears on the console or in the system log, enter the show diag slot-number command to gather additional data, and contact your Cisco technical support representative with the gathered information
Error Message %SERIAL-3-UNAVAILABLE: %s linecard in slot %d firmware download failedExplanation The DS3 firmware download from the system main processor on the NSE to the line card local processor memory failed
Recommended Action This error, if not preceded by a firmware checksum failed error, indicates a software failure. Copy the error message exactly as it appears on the console or in the system log. Enter the show diag slot-number command to gather additional data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show diag slot-number output, contact your Cisco technical support representative with the gathered information
Error Message %SERIAL-3-UNAVAILABLE: %s linecard in slot %d firmware integrity check failed.(section: %d, expected checksum: 0x%x, calculated checksum: 0x%x)Explanation The DS3 line card local processor firmware crashed. The line card will be restarted after the firmware crash. If the firmware crashes more than five times consecutively, the line card will not reactivate after the fifth crash.
Recommended Action A line card firmware failure has occured. Copy the error message exactly as it appears on the console or in the system log. Enter the show diag slot-number command to gather additional data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show diag slot-number output, contact your Cisco technical support representative with the gathered information.
Error Message %SERIAL-3-UNAVAILABLE: %s linecard in slot %d firmware ipc initialization failedExplanation The Cisco IPC module in the DS3 linecard local processor firmware failed to complete a successful initialization. The source of the problem could be a line card hardware failure or a software failure. The line card has been deactivated and will be automatically reactivated. If this error occurs more than five times in an hour, the automatic reactivation will not occur and the line card will remain deactivated.
Recommended Action If the line card is no longer automatically reactivating, copy the error message exactly as it appears on the console or in the system log and enter the show version, show diag slot-number, show ipc status, and show ipc port commands to gather additional data. Contact your Cisco technical support representative with the gathered information to determine whether to replace the line card or upgrade the IOS.
SERIAL-4
Error Message %SERIAL-4-UNAVAILABLE: %s %d/%d%s parameter value is unknownExplanation The IPC command parameter is unknown and the corresponding IPC message has been dropped. This is an informational message.
Recommended Action Check the release notes for your IOS version to see if this is associated with a documented caveat. If not, copy the error message exactly as it appears on the console or in the system log, gather the show tech-support command output, and contact your Cisco technical support representative with the gathered information.
SERIAL-5
Error Message %SERIAL-5-UNAVAILABLE: %s Interface %s %s far end request of type (%s)Explanation The DS3 driver received and processed a known far end request.
Recommended Action None. The purpose of this message is to provide notification that a known request was received from the far end of the link and was processed successfully.
Error Message %SERIAL-5-UNAVAILABLE: Interface %s, BERT %sExplanation The DS3 driver processed a BERT task.
Recommended Action None, this is just a notification upon completion of a BERT task.
SERIAL_12IN1-1
Error Message %SERIAL_12IN1-1-UNAVAILABLE: %s:Link has been brought %s due to clock rate change, threshold configured = %u, received clock rate = %uExplanation The received clock rate is changed from below the threshold configured to above or vice versa..
Recommended Action Check the received clock rate from the provider end and the clockrate threshold configuration, if the clock rate goes below the threshold configured, interface is brought down
Recommended Action
SERIAL_12IN-3
Error Message %SERIAL_12IN1-3-UNAVAILABLE: %s: A software error was encountered at %s: %sExplanation The SPA driver detected a software error condition on the SPA card. This might result in improper operation.
Recommended Action The SPA driver has encountered a software error.Please power down and reseat the indicated SPA card. Copy the error message exactly as it appears andopen a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact your Cisco technical support representative. Be sure to provide the the information you have gathered and a 'show tech-support' to your support representative, or attach it to your case in non-zipped, plain text format (.txt).
Error Message %SERIAL_12IN1-3-UNAVAILABLE: %s: A software error was encountered at %s: %s 0x%xExplanation The SPA driver detected a software error condition on the SPA card. This might result in improper operation.
Recommended Action The SPA driver has encountered a software error.Please power down and reseat the indicated SPA card. Copy the error message exactly as it appears andopen a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact your Cisco technical support representative. Be sure to provide the the information you have gathered and a 'show tech-support' to your support representative, or attach it to your case in non-zipped, plain text format (.txt).
Error Message %SERIAL_12IN1-3-UNAVAILABLE: SPA %d/%d: %s was encountered.Explanation The SPA driver detected a Hardware error condition on the SPA card. This might result in improper operation.
Recommended Action The SPA driver has encountered a Hardware error on the SPA's SPI4 bus.Please power down and reseat the indicated SPA card. If the condition persists, copy the error message exactly as it appears. Next research and attempt to resolve the issue using the SPA hardware troubleshooting documentation as well as the tools and utilities provided at http://www.cisco.com/public/support/tac/tools.shtml. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact your Cisco technical support representative. Be sure to provide the the information you have gathered and a 'show tech-support' to your support representative, or attach it to your case in non-zipped, plain text format (.txt).
SERVER_CLOCK_SYNC-3
Error Message %SERVER_CLOCK_SYNC-3-UNAVAILABLE: bad request - %s - from client - %sExplanation An internal software error occurred.
Recommended Action If this message recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message %SERVER_CLOCK_SYNC-3-UNAVAILABLE: cannot create port %s due to %sExplanation An internal software error occurred.
Recommended Action If this message recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message %SERVER_CLOCK_SYNC-3-UNAVAILABLE: cannot open port %s due to %sExplanation An internal software error occurred.
Recommended Action If this message recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message %SERVER_CLOCK_SYNC-3-UNAVAILABLE: cannot register port %s due to %sExplanation An internal software error occurred.
Recommended Action If this message recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message %SERVER_CLOCK_SYNC-3-UNAVAILABLE: could not locate port %sExplanation An internal software error occurred.
Recommended Action If this message recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message %SERVER_CLOCK_SYNC-3-UNAVAILABLE: list creation failureExplanation An internal software error occurred.
Recommended Action If this message recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message %SERVER_CLOCK_SYNC-3-UNAVAILABLE: watched boolean creation failure. bool %sExplanation An internal software error occurred.
Recommended Action If this message recurs, copy it exactly as it appears and report it to your technical support representative.
SERVICE_MODULE-0
Error Message %SERVICE_MODULE-0-UNAVAILABLE: Unit %s - failed to create data structures used for module-accessExplanation The CSU/DSU driver failed to allocate memory for its data structures. This is a catastrophic error. The system has crashed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SERVICE_MODULE-0-UNAVAILABLE: Unit %s - failed to download properlyExplanation The CSU/DSU driver detected a checksum error while downloading WIC firmware.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
SERVICE_MODULE-3
Error Message %SERVICE_MODULE-3-UNAVAILABLE: Unit %s - WARNING - Loopdown of remote unit failedExplanation A remote CSU is looping pings/test patterns back to the system. This error could be triggered if the user disabled loopbacks on the remote CSU after placing the remote CSU into remote loopback.
Recommended Action Execute a clear command on the remote CSU.
SERVICE_MODULE-4
Error Message %SERVICE_MODULE-4-UNAVAILABLE: Unit %s - Could not access alarm status - disabling alarm processingExplanation The system issued an alarm interrupt, but could not read the alarm status register from the module. This caused the system to disable alarm processing.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SERVICE_MODULE-4-UNAVAILABLE: Unit %s - failed to create reset process - non-default module configuration may be lostExplanation To execute a reset, the Cisco IOS softwa