Table Of Contents
SNMP_CONTEXT_ MAPPING Messages
RTT Messages
The following are round-trip time monitor messages.
Error Message%RTT-4-DuplicateEvent : RTR [dec]: Duplicate event received. Event number [dec]
Explanation The RTR 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 might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands, information about the application that is configuring and polling the Service Assurance Agent probes, and your pertinent troubleshooting logs.Error Message%RTT-4-EPAPI : IPSLAs EP API: [chars] api failed, client = [chars], reason = [chars]
Explanation The IPSLAs Event Publisher API has failed.
Recommended Action The error code is reported to API client. Take the action recommended by the client identified.
Error Message%RTT-4-EPINIT : IPSLAs Event Publisher Init Failed. Reason = [chars]
Explanation The IPSLAs Event Publisher Initialization has failed. The system will try to recover by doing the initialization tasks when first client subscribes to IPSLAs events.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%RTT-3-EPNOTIFYFAILED : event type = [chars], client = [chars], reason = [chars]
Explanation Notification for specified type to specified IPSLAs Event Publisher client failed
Recommended Action This maybe transient system error and the notification may work next time. Take the action as suggested by the identified client for loss of notification.
Error Message%RTT-3-EPSTARTERROR : Failed to start IPSLAs Event Publisher
Explanation The IPSLAs is unable to start a new process for Event Publisher. Reaction Alert notifications will not work.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%RTT-3-EPURFTYPE : IPSLAs EventPublisher: Unknown reaction filter type for client [chars]
Explanation The IPSLAs Event Publisher encountered unknown filter type while sending the reaction alert to specified client Reaction Alert notifications may continue to work for same and other clients.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%RTT-4-OPER_CLOSS : condition [chars], entry number = [dec]
Explanation This message logs connection loss condition in the IPSLAs operations. This message is enabled when the ip sla monitor logging trap command is entered.
Recommended Action Ensure the the destination for the IPSLAs operation is reachable. Also ensure that the IPSLAs responder operation is configured on the destination. If you do not want to log these messages for IPSLA operations, enter the no ip sla monitor logging trap command to disable logging.
Error Message%RTT-4-OPER_TIMEOUT : condition [chars], entry number = [dec]
Explanation This message logs timeout condition in the IPSLAs operations. This message is enabled when the ip sla monitor logging trap command is entered.
Recommended Action Ensure that the destination for the IPSLAs operation is reachable. If you do not want to log these messages for IPSLAs operations, enter the no ip sla monitor logging trap command to disable the logging.
Error Message%RTT-3-REACTNOTIFYFAILED : entry number = [dec], reason = [chars]
Explanation IPSLAs Reaction condition was met for specified operation and one or more IPSLAs Event Publisher clients have registered interest for this condition but the notification for this occurrence failed.
Recommended Action These maybe transient system errors and the notification may work next time. Enter the show ip sla event-publisher command to see which clients are registered and take action recommended by them.
Error Message%RTT-4-REACTPARTIALEVENT : entry number = [dec], missing data = [chars]
Explanation IPSLAs Reaction Event is missing some interesting data
Recommended Action This could be because of IPSLAs software error. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show ip sla config command and your pertinent troubleshooting logs.Error Message%RTT-4-SAACLOCKNOTSET : RTR Probe(s) could not be scheduled because clock is not set.
Explanation One or more RTR probes could not be scheduled because 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 ocurred, or the starting time is invalid.
Recommended Action Reschedule the group scheduling entry with a valid start time.
Error Message%RTT-3-SAAMPLS : RTR([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 messages appears when the rtr logging trap command is 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 : RTR([dec]): Negative Value for [chars]
Explanation RTR statistics has 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center 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%RTT-3-SAANOPROCESS : IP SLAs: Cannot create a new process
Explanation The IP SLAs 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 : RTR: Error deleting the probe
Explanation Trying to delete a probe which 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center 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%RTT-4-SAASCHEDCONFIGFAIL : RTR Probe [dec]: [chars]
Explanation The RTR probe could not be scheduled. Either the configured starting time has already ocurred, or the starting time is invalid.
Recommended Action Reschedule the failed probe with a valid start time.
Error Message%RTT-6-SAATHRESHOLD : RTR([dec]): Threshold [chars] for [chars]
Explanation This informational message logs threshold violations in the Service Assurance Agent probes. This messages appears when the rtr logging trap command is 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-SAATWINITFAIL : IP SLAs: Generic Timer wheel timer functionality failed to initialize
Explanation The IP SLAs could not initialize the timer wheel.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show version and show running-config commands and your pertinent troubleshooting logs.RUDP Messages
The following are the RUDP messages.
Error Message%RUDP-3-INIT : rudp [dec]: [chars][chars].
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 gathered information.
Error Message%RUDP-4-LINK : rudp [dec]: [chars][chars].
Explanation A warning is given out for a particular RUDP link.
Recommended Action This is a debug message only. No action is required.
Error Message%RUDP-4-NOBUF : rudp [dec]: cannot get packet buffer for [chars].
Explanation A rudp link cannot allocate a packet buffer.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Recommended Action warrant, upgrade to a larger memory configuration.
RUNCFGSYNC Messages
The following are the RUNCFGSYNC messages.
Error Message%RUNCFGSYNC-6-HASRMSTATE : [chars]
Explanation The High Availability Single Router Mode has changed state. Additional
details are provided in the error message text.Recommended Action No action is required.
Error Message%RUNCFGSYNC-6-SYNCEVENT : [chars]
Explanation A Running Config sync event has happened
Recommended Action No action is required.
RXP_MANAGER Messages
The following are the RXP manager messages.
Error Message%RXP_MANAGER-3-BADBIND : illegal bind [int] [int]
Explanation A illegal bind operation has occurred.
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. Otherwise, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show version and show running-config commands and your pertinent troubleshooting logs.Error Message%RXP_MANAGER-3-BADINDEX : bad index value: [chars] [dec]
Explanation The index value is outside the array limits.
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. Otherwise, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show version and show running-config commands and your pertinent troubleshooting logs.Error Message%RXP_MANAGER-3-BADTYPE : [chars] [dec]
Explanation A illegal type has been encountered.
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. Otherwise, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show version and show running-config commands and your pertinent troubleshooting logs.Error Message%RXP_MANAGER-3-BADUNBIND : illegal unbind [int] [int]
Explanation An illegal bind operation has occurred.
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. Otherwise, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show version and show running-config commands and your pertinent troubleshooting logs.Error Message%RXP_MANAGER-3-BADVAL : unexpected value: [chars] [dec]
Explanation An unexpected value has been encountered.
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. Otherwise, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show version and show running-config commands and your pertinent troubleshooting logs.Error Message%RXP_MANAGER-3-DEFVEC : default vectors used: [chars]
Explanation The default vector has been used.
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. Otherwise, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show version and show running-config commands and your pertinent troubleshooting logs.Error Message%RXP_MANAGER-3-NULLPTR : [chars] [hex]
Explanation A null pointer has been encountered.
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. Otherwise, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show version and show running-config commands and your pertinent troubleshooting logs.Error Message%RXP_MANAGER-3-REFCOUNT : bad refcnt: [chars] [hex]
Explanation A bad reference count has occurred.
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. Otherwise, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show version and show running-config commands and your pertinent troubleshooting logs.Error Message%RXP_MANAGER-3-UNINIT : [chars] [int]
Explanation An uninitialized data structure has been encountered.
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. Otherwise, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show version and show running-config commands and your pertinent troubleshooting logs.S4T68360 Messages
The following are the S4T68360 messages.
Error Message%S4T68360-1-RESTART : Bay [dec] port adaptor
Explanation The S4T port adaptor hardware failed. The periodic check routine
detected the failure and restarted it.Recommended Action No action is required.
Error Message%S4T68360-5-RINGSIZE : [chars] TX packet dropped; particle count ([dec]) exceeds [dec]
Explanation The TX packet got dropped since the TX ring was full.
Explanation This is normal when the port adapter gets overdriven.
SAMI Messages
The following are Services and Application Module for IP messages.
Error Message%SAMI-4-FAILED_FILE_INIT_TASK : [chars] [chars] - [chars]
Explanation A file necessary for storing and retrieving configuration on the supervisor failed to be created.
Recommended Action Verify that there is space on the corresponding supervisor filesystem.
Error Message%SAMI-4-FAILED_FILE_SYNC : Failure creating or synchronizing SAMI configuration file to standby: [chars], [chars]
Explanation The active supervisor has failed to copy an SAMI configuration file from bootflash: to slavebootflash:. The standby supervisor will not be up-to-date with respect to the SAMI configuration files, should a switchover occur.
Recommended Action Verify that there is space available on the bootflash: and slavebootflash: devices. It may be necessary to squeeze either or both devices to recover space used by deleted or over-written files. After taking these actions, a new attempt to synchronize files can be started either by resetting the standby supervisor or by configuring no sami bootflash access followed immediately by sami bootflash access If these actions do not resolve the issue, gather the output from the commands:
- dir bootflash:
- dir slavebootflash:
- show bootflash:
- show slavebootflash:
- If possible set debug sami all on the active supervisor, then reset the standby supervisor with hw-module module <slot> reset capturing the debug information that appears on the active supervisor's console. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%SAMI-4-FAILED_TASK_INIT : Failed to start a required task: [chars], [chars]
Explanation A necessary process failed to be created.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message%SAMI-5-SAMI_SUBINTERFACE_STATE_DOWN : Interface [chars] state changed to DOWN, based on svclc configuration on the supervisor.
Explanation The subinterface will stay down until corresponding vlan is added with the svclcconfiguration on the supervisor.
Error Message%SAMI-5-SAMI_SUBINTERFACE_STATE_UP : Interface [chars] state changed to UP, based on svclc configuration on the supervisor.
Explanation The subinterface is marked up because it is enabled in the supervisor svclc configuration.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%SAMI-4-UNEXPECTED : Unexpected condition: [chars]
Explanation An unexpected condition was detected while performing SAMI Platform operation.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%SAMI-4-WARNING : Unexpected condition: [chars]
Explanation An unexpected condition was detected while performing SAMI Platform operation.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.SAMI_FLASH_OPS Messages
The following are Services and Application Module for IP Flash messages.
Error Message%SAMI_FLASH_OPS-6-NVRAM_CRC_FAILURE : Nvram CRC Failure: [dec]
Explanation NVRAM corruption.
Recommended Action Informational message only. No action is required.
Error Message%SAMI_FLASH_OPS-6-NVRAM_ERASE_FAILURE : Nvram Erase Failure: handle [hex], offset [hex], error [chars]
Explanation NVRAM Erase Failure.
Recommended Action Informational message only. No action is required.
Error Message%SAMI_FLASH_OPS-6-NVRAM_INIT_FAILURE : Nvram Init Failure of flash device at [dec] : [chars]
Explanation Unable to initialize flash device.
Recommended Action Informational message only. No action is required.
Error Message%SAMI_FLASH_OPS-6-NVRAM_INIT_MEMORY_FAILURE : Nvram Init Failure: [chars]
Explanation Unable to initialize flash device: Low Memory.
Recommended Action Informational message only. No action is required.
Error Message%SAMI_FLASH_OPS-6-NVRAM_MAGIC_CORRUPT : Nvram Magic Corrupt: Presetn [dec] Expected [dec]
Explanation NVRAM Corruption.
Recommended Action Informational message only. No action is required.
Error Message%SAMI_FLASH_OPS-6-NVRAM_WRITE_BLOCK_FAILURE : Nvram Write Failure: handle [hex], offset [hex], numbytes [hex] error [chars]
Explanation NVRAM Write Failure.
Recommended Action Informational message only. No action is required.
Error Message%SAMI_FLASH_OPS-6-NVRAM_WRITE_CONFIG_FAILURE : Nvram Write Config Failure:
Explanation NVRAM Write Failure.
Recommended Action Informational message only. No action is required.
SASL Messages
The following are Simple Authentication and Security Layer messages.
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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center 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%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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.SBETH Messages
The following are MAC controller (SBETH) messages.
Error Message%SBETH-1-BAD_IDB : Invalid Interface Descriptor Block
Explanation The driver failed in an attempt to fetch the IDB of the interface.
Recommended Action Copy the message exactly as it appears on the console or in the system log.Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. 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 troubleshooting logs.Error Message%SBETH-1-BAD_MEDIA : Unknown media-type in subblock
Explanation 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands, and your troubleshooting logs.Error Message%SBETH-1-BAD_PARTICLE : Problem getting particle size
Explanation 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands, and your troubleshooting logs.Error Message%SBETH-1-BAD_PLUGIN : Plugin function table incomplete or missing
Explanation The driver could not access the specific function table of the PA.
Recommended Action Copy the message exactly as it appears on the console or in the system log.Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands, and your troubleshooting logs.Error Message%SBETH-1-BAD_POOL : Could not init buffer pools
Explanation The driver failed to get 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands, and your troubleshooting logs.Error Message%SBETH-1-BAD_SB_NOMEM : [chars] - Cannot create IDB subblock due to insufficient memory
Explanation There was insufficent system memory to create the subblock.
Recommended Action The router requires more main memory.
Error Message%SBETH-1-BAD_STRUCT : Could not initialize structure
Explanation 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands, and your troubleshooting logs.Error Message%SBETH-1-BAD_SUBBLOCK : [chars] - Could not install or use IDB subblock
Explanation An internal Cisco IOS Software error prevented the IDB subblock from being installed or used.
Recommended Action Copy the message exactly as it appears on the console or in the system log.Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands, and your troubleshooting logs.Error Message%SBETH-3-DUPLICATE : [chars] - duplicate GBIC
Explanation The GBIC module for the interface specified in the error message is a duplicate of another GBIC in the system. As a result of the error, both modules are disabled.
Recommended Action Remove the duplicate module. 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands, and your troubleshooting logs.Error Message%SBETH-3-ERRINT : [chars], error interrupt, mac_status = [hex]
Explanation 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 gathered information.
Error Message%SBETH-1-IDBTYPE_UNK : Unknown IDBTYPE while starting driver
Explanation The IDBTYPE in the instance structure of the interface 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 gathered information.
Error Message%SBETH-1-INITFAIL_NOMEM : [chars], initialization failed, no buffer memory
Explanation The Ethernet port initialization failed due to insufficient memory.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%SBETH-3-MAC_LIMIT_EXCEEDED : Unable to add mac address [enet]
Explanation Maximum number of allowed mac entries reached. Cannot add any more.
Recommended Action Try removing some of the mac addresses, for example, those used by each unique hsrp group configuration. Standby use-bia could be used to limit the usage.
Error Message%SBETH-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 Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SBETH-2-NOISL : Interface [chars] does not support ISL
Explanation ISL is not supported on the hardware of the specified interface.
Recommended Action No action is required.
Error Message%SBETH-3-NOT_SUPPORTED : [chars] - unsupported GBIC
Explanation The GBIC module for the interface specified in the error message is not a Cisco-supported module. As a result of the error, the module is disabled.
Recommended Action Replace the module with a Cisco-supported GBIC. 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands, and your troubleshooting logs.Error Message%SBETH-1-RESET : MAC Still in Reset
Explanation An attempt was made to access the MAC while it was resetting.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in 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-TOOBIG : [chars], packet too big ([dec]), from [enet]
Explanation The interface has detected a packet that is larger than the MTU.
Recommended Action Check the MTU setting of the other station.
SBFIFO Messages
The following are the SBFIFO messages.
Error Message%SBFIFO-1-BAD_IDB : Allocation of an Interface Descriptor Block failed
Explanation The Packet FIFO MAC driver failed to obtain an IDB for the Packet FIFO MAC interface. This condition indicates a software problem.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in 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 size
Explanation 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 gathered information. Attach the following information to your case 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 initialize [chars]
Explanation The Packet FIFO MAC driver failed to obtain a pool of buffers from the Cisco IOS software. This condition indicates a software problem.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in 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 memory
Explanation There was insufficent system memory to create the subblock.
Recommended Action The router requires more main memory.
Error Message%SBFIFO-1-BAD_STRUCT : Could not allocate memory for [chars]
Explanation The Packet FIFO MAC driver failed to allocate memory for the specified component. This condition indicates a software problem.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in 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 subblock
Explanation An internal IOS error prevented the IDB subblock from being installed or used.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SBFIFO-3-ERRINT : [chars], error interrupt, mac_status = [hex]
Explanation The Packet FIFO 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 gathered information.
Error Message%SBFIFO-1-IDBTYPE_UNK : Unknown IDBTYPE while starting driver
Explanation The IDBTYPE in the interface's instance structure is undefined for this driver
Recommended Action Software bug - open a case with Development Engineering.
Error Message%SBFIFO-1-INITFAIL_NOMEM : [chars], initialization failed, no buffer memory
Explanation The packet FIFO MAC port has failed to initialize because of insufficient memory. This condition most likely indicates a software problem.
Recommended Action 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 gathered information. Attach the following information to your case 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 Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in 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-NOINT : Packet FIFO interface not created
Explanation A Packet FIFO interface could not be created.
Recommended Action Gather previous messages sent to the console as they should contain the exact reason.
Error Message%SBFIFO-1-RESET : MAC-FIFO Still in Reset
Explanation An attempt was made to access the MAC-FIFO while it was resetting.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in 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])
Explanation he packet FIFO interface has detected a packet that was larger than the predefined MTU. This condition most likely indicates a software problem.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SCCP-1-ALERT : [chars]
Explanation A condition that should be corrected immediately.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SCCP-2-CRITICAL : [chars]
Explanation 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 gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SCCP-3-ERROR : [chars]
Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SCCP-6-INFO : [chars]
Explanation This is an informational message only.
Recommended Action No action is required.
Error Message%SCCP-5-NOTICE : [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SCCP-0-PANIC : [chars]
Explanation An unrecoverable internal panic event has occurred that should be resolved immediately.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SCCP-4-WARNING : [chars]
Explanation A warning message has been received.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
SCP Messages
The following are the Switch Module Configuration Protocol (SCP) messages.
Error Message%SCP-5-ASYNC_WATERMARK : [dec] messages pending in [chars]
Explanation The indicated number of SCP messages are waiting in the indicated local queue. This condition might mean that the SP is generating many messages, that the SP is to busy to send them, or that the line card cannot process them at a sufficient pace. In most cases, this condition occurs when there is significant control plane activity. The type of activities that can cause this message to be generated are the formation of Layer 2 trunks, the addition of new VLANs, or the toggling of links.
Recommended Action If this message is occurring sporadically during configuration then, no action is required. Otherwise, check if the SP is busy or if the interface link is rapidly coming up and then going down. If these messages persist for more than 5 minutes then, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SCP-4-DACK_TIMEOUT_MSG : SCP delivery ack timeout for opcode=[hex]
Explanation RP did not receive the SCP delivery acks from SP even after two retries.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in 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 router has received module enable indication from Supervisor
Recommended Action No action is required.
Error Message%SCP-4-GET_PAK_MSG : Failed for message size=[dec]
Explanation The system is out of pak type buffers of required size.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SCP-2-NOMEM : No memory available for [chars]
Explanation The SCP protocol 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 gathered information. Attach the following information to your case 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-2-NOTREG : Process [dec]([chars]) not registered for SCP
Explanation The SCP application cannot send an SCP message because it has
not registered for a SAP.Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in 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-ONLINE : Module online [chars]
Explanation The router has received online indication from Supervisor
Recommended Action No action is required.
Error Message%SCP-3-SCP_FAILURE : SCP Opcode:[dec] Module: [dec] returned error [hex]
Explanation The SCP operation performed by RP/SP to communicate with the module 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 gathered information. Attach the following information to your case 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] times
Explanation 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 gathered information. Attach the following information to your case 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-2-TOO_MANY_SAP : Not enough space to register process [dec]([chars]) for SCP
Explanation The SCP application cannot register for a SAP because all possible
numbers have been assigned.Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
SCP-SP Messages
The following are SCP Protocol SP messages.
Error Message%SCP-SP-2-NOMEM : No memory available for [chars]
Explanation The SCP protocol system 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.SDLC Messages
The following are Synchronous Data Link Control (SDLC) error messages.
Error Message%SDLC-4-BADFRAME : [chars], Received bad SDLC [chars]frame, address [hex], control [hex]
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 gathered information.
Error Message%SDLC-3-CONFIGERR : [chars], addr [hex], 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 gathered information.
Error Message%SDLC-3-DLU_ERROR : [chars], DLU failed to close station [hex] before re-opening, [chars]/[chars]
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 gathered information.
Error Message%SDLC-2-ILLEGSTATE : [chars], illegal state for addr [hex], [chars]([dec])
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 gathered information. Attach the following information to your case 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-INVLDGRPCFG : Interface [chars], ignoring group-poll mismatch, UPOLL [hex]
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 gathered information.
Error Message%SDLC-3-NOINPIDB : Input idb not set
Explanation 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 gathered information. Attach the following information to your case 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-NULLPAK : Interface [chars], NULL packet ptr, rvr [dec], vs [dec], vr [dec]
Explanation An internal software error has occurred in the 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 gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
SDLLC Messages
The following are Synchronous Data Logical Link Control (SDLLC) Logical Link Control Type 2 (LLC2) translation messages.
Error Message%SDLLC-5-ACT_LINK : SDLLC: [chars] LINK address [hex] ACTIVATED: [chars]
Explanation An SDLLC media conversion session was activated.
Recommended Action No action is required.
SDM Messages
The following are SDM template messages.
Error Message%SDM-6-MISMATCH_ADVISE : [chars]
Explanation A line of output from the SDM mismatch is being displayed.
Recommended Action No action is required.
SEC Messages
The following are the IP Security messages.
Error Message%SEC-6-IPACCESSLOGDP : list [chars] [chars] [chars] [IP_address] [chars]-> [IP_address] ([dec]/[dec]), [dec] packet[chars]
Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action No action is required.
Error Message%SEC-6-IPACCESSLOGNP : list [chars] [chars] [dec] [IP_address] [chars]-> [IP_address], [dec] packet[chars]
Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action No action is required.
Error Message%SEC-6-IPACCESSLOGP : list [chars] [chars] [chars] [IP_address]([dec]) [chars]-> [IP_address]([dec]), [dec] packet[chars]
Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action No action is required.
Error Message%SEC-6-IPACCESSLOGRL : access-list logging rate-limited or missed [dec] packet[chars]
Explanation 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 No action is required.
Error Message%SEC-6-IPACCESSLOGRP : list [chars] [chars] [chars] [IP_address] [chars]-> [IP_address], [dec] packet[chars]
Explanation A packet matching the log criteria for the given access list has been detected.
Recommended Action No action is required.
Error Message%SEC-6-IPACCESSLOGS : list [chars] [chars] [IP_address] [dec] packet[chars]
Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action No action is required.
Error Message%SEC-3-NOMAX : No default for NLESO defined
Explanation An internal software error has occurred.
Recommended Action 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 gathered information. Attach the following information to your case 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-NOOPT : Box secured, no option on internal packet
Explanation An internal software error has occurred.
Recommended Action 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 gathered information. Attach the following information to your case 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-SECINS : Security opt in tcb not SECINSERT
Explanation An internal software error has occurred.
Recommended Action 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 gathered information. Attach the following information to your case 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-4-SHELFCTLRTELOPT : malformed option on vty[t-line] [char][char][char][dec] len [dec] [chars]
Explanation A packet containing shelf controller telnet options was malformed. Options were ignored or truncated.
Recommended Action No action is required.
SEC_LOGIN Messages
The following are secure login messages.
Error Message%SEC_LOGIN-4-25 : Login failed [user: [chars]] [Source: [IP_address]] [localport: [int]] [Reason: [chars]] at [chars]
Explanation Invalid User Name or Password is given from terminal.
Recommended Action This is a notification to indicate that login failed.
Error Message%SEC_LOGIN-3-INIT_FAILED : Secure Login Initialization failed. [chars]
Explanation Initialization of Secure Login Subsystem failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SEC_LOGIN-5-LOGIN_SUCCESS : Login Success [user: [chars]] [Source: [IP_address]] [localport: [int]] at [chars]
Explanation A successful login happened with the device.
Recommended Action This is a notification that login succeeded.
Error Message%SEC_LOGIN-5-QUIET_MODE_OFF : Quiet Mode is OFF, because [chars] at [chars]
Explanation Quiet Mode is OFF. Router now operates in normal connection processing mode.
Recommended Action A notification that the device now operates in normal connection processing mode and the reason why it switched mode is also indicated with the notification.
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 ON. No request for connection is accepted other than allowed by the Access List, if configured for the blocking period. Else an implicit *deny all* logins will be in force
Recommended Action As all the requests from other sources are blocked, check ACL and add any source addr, if needed.
SERIAL Messages
The following are WS SERIAL line card messages.
Error Message%SERIAL-3-DS3_IPC_MESSAGE_HANDLER_FAIL : Cannot create IPC message handler for DS3 Line card on RP.
Explanation The IPC handling process could not be created on RP. The condition indicates resource allocation issue for RP. The DS3 line card(s) on this router will not work properly.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SERIAL-3-DS3_IPC_QUEUE_FAIL : Can not create watched queue for the DS3 Line card on RP.
Explanation The condition indicates resource allocation issue on RP. The DS3 line card(s) on this router will not work properly.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SERIAL-1-FW_CRASHED : [chars] line card firmware in slot [dec] crashed
Explanation 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 gathered information. Attach the following information to 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_12IN1 Messages
The following are Serial 12IN1 Shared Port Adapter messages.
Error Message%SERIAL_12IN1-1-CLOCKRATE : [chars]:Link has been brought [chars] due to clock rate change, threshold configured = [int], received clock rate = [int]
Explanation 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. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center 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%SERIAL_12IN1-3-SPI4_ERR : SPA [dec]/[dec]: [chars] was encountered. Intr status: [hex]
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. Power down and reseat the indicated SPA card. If this message recurs, copy the message exactly as it appears on the console or in the system log.Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging, show monitor event-log spa all and show tech-support commands, and your troubleshooting logs.Error Message%SERIAL_12IN1-3-SPI4_HW_ERR : SPA [dec]/[dec]: [chars] was encountered.
Explanation The SPA driver has detected a hardware error condition on the SPA's SPI4 bus. This might result in improper operation.
Recommended Action Power down and reseat the indicated SPA card. If the condition persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac and the SPA hardware troubleshooting documentation. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message%SERIAL_12IN1-3-SW_ERR : [chars]: A software error was encountered at [chars]: [chars]
Explanation 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. Power down and reseat the indicated SPA card. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging, show monitor event-log spa all and show tech-support commands and your troubleshooting logs.Error Message%SERIAL_12IN1-3-SW_ERR_1 : [chars]: A software error was encountered at [chars]: [chars] [hex]
Explanation 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. Power down and reseat the indicated SPA card. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging, show monitor event-log spa all and show tech-support commands and your troubleshooting logs.Error Message%SERIAL_12IN1-3-SW_ERR_2 : [chars]: A software error was encountered at [chars]: [chars] [hex]/[hex]
Explanation 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. Power down and reseat the indicated SPA card. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format:the output of the show logging, show monitor event-log spa all and show tech-support commands and your troubleshooting logs.SERVICE_GROUP Messages
The following are the SERVICE_GROUP messages.
Error Message%SERVICE_GROUP-3-SG_CREATION_ERROR : An error is detected when creating Service Group [int] ([chars])
Explanation An error has been detected when creating a service group. The failure most likely occurred because of 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center 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%SERVICE_GROUP-3-SG_DELETION_ERROR : An error is detected when deleting Service Group [int] ([chars])
Explanation An error has been detected when deleting a service group. The failure most likely occurred because of the group is not configured or a software error.
Recommended Action If the group is configured, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center 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%SERVICE_GROUP-3-SG_INTERNAL_ERROR : Service Group detected an internal error ([chars] [int])
Explanation An internal error has been detected by the service group 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center 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%SERVICE_GROUP-3-SG_IPC_TRANSMIT_FAILED : Service Group IPC message transmission failure ([chars])
Explanation An error was detected when transmitting an IPC message between route processor and linecard. The failure most likely occurred because of a software error. The message output identifies the type of error that occurred.
Recommended Action This could be a transient error. If this error persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.SFP Messages
The following are Small Form-Factor Pluggable (SFP) module messages.
Error Message%SFP-4-EEPROM_CRC_ERR : EEPROM checksum error for SFP in [chars]
Explanation The SFP in the port specified in the error message has invalid EEPROM data.
Recommended Action Remove the SFP from the specified port.
Error Message%SFP-3-EEPROM_DUP_ERR : SFP on ports [chars] and [chars] have duplicate serial numbers
Explanation The GBIC/SFP was identified as a Cisco GBIC, but its vendor id and serial number match that of another GBIC on the 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message%SFP-4-EEPROM_READ_ERR : Error in reading SFP serial ID in [chars]
Explanation Error when reading SFP type from EEPROM.
Recommended Action Remove SFP from this port.
Error Message%SFP-4-EEPROM_SECURITY_ERR : SFP in [chars] failed security check
Explanation The SFP in the port specified in the error message has invalid EEPROM data.
Recommended Action Remove the SFP from the specified port.
Error Message%SFP-6-INSERTED : SFP module inserted in [chars]
Explanation The online insertion and removal (OIR) facility detected a newly inserted SFP module for the interface specified in the error message.
Recommended Action No action is required.
Error Message%SFP-3-NOT_COMPATIBLE : Detected for SFP module in [chars], module disabled
Explanation The SFP module for the interface specified in the error message is not compatible with the interface. As a result of the error, the module is disabled.
Recommended Action Replace the module with a compatible SFP.
Error Message%SFP-3-NOT_SUPPORTED : Detected for SFP module in [chars], module disabled
Explanation The SFP module for the interface specified in the error message is not a cisco supported module. As a result of the error, the module is disabled.
Recommended Action Replace the module with a cisco supported SFP.
Error Message%SFP-4-REMOVED : SFP module removed from [chars]
Explanation The online insertion and removal (OIR) facility detected the removal of an SFP module from the interface specified in the error message.
Recommended Action No action is required.
SFP_SECURITY Messages
The following are Small Form-Factor Pluggable (SFP) module security messages.
Error Message%SFP_SECURITY-4-DUPLICATE_SN : SFP interface [chars] has the same serial number as another SFP interface
Explanation The SFP was identified as a Cisco SFP, but its serial number matches that of another interface on the system.
Recommended Action Cisco SFPs are assigned unique serial numbers. Verify that the SFP was obtained from Cisco or a supported vendor.
Error Message%SFP_SECURITY-4-ID_MISMATCH : Identification check failed for SFP interface [chars]
Explanation The SFP was identified as a Cisco SFP, but the system was unable to verify its identity.
Recommended Action Check the list of supported SFPs for this version of the system software. An upgrade might be required for newer SFPs. Otherwise, verify that the SFP was obtained from Cisco or a supported vendor.
Error Message%SFP_SECURITY-4-SFP_INTERR : Internal error occurred in setup for SFP interface [chars]
Explanation The system could not allocate resources, or had some other problem, in the setup for the specified SFP interface.
Recommended Action Reload the system. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message%SFP_SECURITY-4-UNRECOGNIZED_VENDOR : SFP interface [chars] manufactured by an unrecognized vendor
Explanation The SFP was identified as a Cisco SFP, but the system was unable to match its manufacturer with one on the known list of Cisco SFP vendors.
Recommended Action Check the list of supported SFPs for this version of the system software. An upgrade might be required for newer SFPs.
Error Message%SFP_SECURITY-4-VN_DATA_CRC_ERROR : SFP interface [chars] has bad crc
Explanation The SFP was identified as a Cisco SFP, but it does not have valid crc in the eeprom data.
Recommended Action Check the list of supported SFPs for this version of the system software. An upgrade might be required for newer SFPs. Even if unrecognized, the SFP might still operate properly, perhaps with limited functionality.
SGBP Messages
The following are Stack Group Bidding Protocol (SGBP) messages.
Error Message%SGBP-7-ACTIVE : Member [chars] State -> 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.
Error Message%SGBP-5-ARRIVING : New peer event for member [chars]
Explanation This message is generated only when SGBP event debugging is enabled. An SGBP peer joined the group.
Recommended Action No action is required.
Error Message%SGBP-1-AUTHFAILED : Member [chars] failed authentication
Explanation This message is generated only when SGBP hellos or errors debugging is enabled. This indicates that an attempted peer connection ended in authentication failure. A peer might be misconfigured. Or this could indicate an attempted security breach.
Recommended Action Check if the peer is correctly configured. If there is a chance your network is under attack, obtain knowledgeable assistance. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center 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%SGBP-7-AUTHOK : Member [chars] State -> AuthOK
Explanation This message is generated only when SGBP errors or events debugging is enabled. A message was received from another SGBP member indicating that an authentication attempt to that member succeeded.
Recommended Action No action is required.
Error Message%SGBP-7-CANCEL : Local query #[dec]:[dec] for bundle [chars]
Explanation This message is generated only when SGBP query debugging is enabled. It provides information about queries in progress.
Recommended Action No action is required.
Error Message%SGBP-7-CHALLENGE : Send Hello Challenge to [chars] group [chars]
Explanation This message is generated only when SGBP hellos debugging is enabled. This indicates that an authentication challenge was sent to a peer.
Recommended Action No action is required.
Error Message%SGBP-7-CHALLENGED : Rcv Hello Challenge message from member [chars] using [IP_address]
Explanation This message is generated only when SGBP hellos debugging is enabled. This indicates that an authentication challenge was received from a peer.
Recommended Action No action is required.
Error Message%SGBP-7-CLOSE : Closing pipe for member [chars]
Explanation This message is generated only when SGBP event debugging is enabled. An interprocess communication link was closed.
Recommended Action No action is required.
Error Message%SGBP-1-DIFFERENT : Rcv [chars]'s addr [IP_address] is different from the hello's addr [IP_address]
Explanation The internally-configured address for an SGBP member does not match the address of the host that tried to authenticate as that member. The configuration is incorrect on either this system or the other member — they must agree.
Recommended Action Determine which configuration is in error and fix it.
Error Message%SGBP-7-DONE : Query #[dec] for bundle [chars], count [dec], master is [chars]
Explanation This message is generated only when SGBP query debugging is enabled. It provides information about queries in progress.
Recommended Action No action is required.
Error Message%SGBP-7-DUPL : Duplicate local query #[dec] for [chars], count [dec], ourbid [dec]
Explanation This message is generated only when SGBP query debugging is enabled. It provides information about queries in progress.
Recommended Action No action is required.
Error Message%SGBP-1-DUPLICATE : Rcv Duplicate bundle [chars] is found on member [chars]
Explanation This message is generated only when SGBP hellos or errors debugging is enabled. This indicates that a duplicate bundle was received from the same peer more than once. The duplicate was discarded.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SGBP-7-EQUAL : [dec] equal highest bids, randomly select bid# [dec]
Explanation This message is generated only when SGBP query debugging is enabled. It provides information about queries in progress.
Recommended Action No action is required.
Error Message%SGBP-7-HANGUP : I am a forward-only member, can't forward bundle [chars], hangup
Explanation This message is generated only when SGBP query, event and/or error debugging is enabled. This indicates a routine change of role for the router in its SGBP interactions with its peers.
Recommended Action No action is required.
Error Message%SGBP-3-INVALID : MQ message with [chars]
Explanation This message is generated only when SGBP error debugging is enabled. An invalid message was received and discarded.
Recommended Action This probably indicates an error in network media or peer which is generating erroneous packets. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center 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%SGBP-3-INVALIDADDR : Stack group [chars] IP address [IP_address]
Explanation The current configuration does not allow a local IP address to be configured using sgbp member <address>. Any local address is automatically removed fro the SGBP group.
Recommended Action Do not configure sgbp member <address> using a local IP address.
Error Message%SGBP-3-INVALIDB : [chars] for bundle '[chars]' -- [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center 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%SGBP-3-INVFIELD : [chars] field type [hex] has [chars] [dec] (expected [dec])
Explanation This message indicates that an SGBP request from a peer contained invalid or corrupt data.
Recommended Action Check the peer equipment or network media for any problems.
Error Message%SGBP-7-KEEPALIVE : Sending Keepalive to [chars], retry=[dec]
Explanation This message is generated only when SGBP hellos debugging is enabled. It indicates that a keepalive message was sent to an SGBP member.
Recommended Action No action is required.
Error Message%SGBP-7-KEEPALIVE_TIMEOUT : Keepalive timeout on [chars]
Explanation This message is generated only when SGBP hellos debugging is enabled. It indicates that keepalive messages were not answered so the pipe to an SGBP member has been closed.
Recommended Action No action is required.
Error Message%SGBP-5-LEAVING : Member [chars] leaving group [chars]
Explanation This message is generated only when SGBP event debugging is enabled. An SGBP peer has left the group.
Recommended Action No action is required.
Error Message%SGBP-1-MISSCONF : Possible misconfigured member [chars] using [IP_address]
Explanation This message is generated only when SGBP hellos or error debugging is enabled. This indicates a configuration error. Either this router has an incorrect IP address listed for the peer or the peer is using an incorrect IP address.
Recommended Action Find and correct the configuraton error.
Error Message%SGBP-7-MQ : [chars] ([hex]) for query [dec]:[dec], bundle [chars], bid [dec], len [dec]
Explanation This message is generated only when SGBP error debugging is enabled. This message indicates that an SGBP query has been received.
Recommended Action No action is required.
Error Message%SGBP-7-MQB : Bundle: [chars] State: [chars] OurBid: [dec]
Explanation This message is part of a list of debug states displayed at the request of the operator.
Recommended Action No action is required.
Error Message%SGBP-7-NEWL : Local query #[dec] for [chars], count [dec], ourbid [dec]
Explanation This message is generated only when SGBP query debugging is enabled. It provides information about queries in progress.
Recommended Action No action is required.
Error Message%SGBP-7-NEWP : Peer query #[dec] for [chars], count [dec], peerbid [dec], ourbid [dec]
Explanation This message is generated only when SGBP query debugging is enabled. It provides information about queries in progress.
Recommended Action No action is required.
Error Message%SGBP-7-NORESP : Failed to respond to [chars] group [chars], might not have password
Explanation An authentication challenge was received but there was noinformation available to respond to it. This probably indicates a configuration error, such as a missing password.
Recommended Action Refer to the documentation to configure a username with the same name as the SGBP group.
Error Message%SGBP-7-PB : [IP_address] State: [chars] Bid: [dec] Retry: [dec]
Explanation This message is part of a list of debug states displayed at the request of the operator.
Recommended Action No action is required.
Error Message%SGBP-3-PEERERROR : Peer [IP_address] [chars] during 'PB [chars]' state for bundle [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SGBP-7-RCVD : MQ [chars] from [IP_address] for query [dec]:[dec], bundle [chars], bid [dec], prot[chars]
Explanation This message is generated only when SGBP message debugging is enabled. It indicates that an SGBP packet was received.
Recommended Action No action is required.
Error Message%SGBP-7-RCVINFO : Received Info Addr = [IP_address] Reference = [hex]
Explanation This message is generated only when SGBP hellos debugging is enabled. It indicates that data was received by a listener process.
Recommended Action No action is required.
Error Message%SGBP-7-RESPONSE : Send Hello Response to [chars] group [chars]
Explanation This message is generated only when SGBP hellos debugging is enabled. This indicates that a response to an authentication challenge was sent to a peer.
Recommended Action No action is required.
Error Message%SGBP-7-RESPONSED : Rcv Hello Response message from member [chars] using [IP_address]
Explanation This message is generated only when SGBP hellos debugging is enabled. This indicates that a response to an authentication challenge was received from a peer.
Recommended Action No action is required.
Error Message%SGBP-7-SENDAUTHOK : Send Hello Authentication OK to member [chars] using [IP_address]
Explanation This message is generated only when SGBP hellos debugging is enabled. A message was sent or re-sent to another SGBP member indicating that an authentication attempt from that member succeeded.
Recommended Action No action is required.
Error Message%SGBP-7-SENDINFO : Send Info Addr to [chars]
Explanation This message is generated only when SGBP hellos debugging is enabled. It indicates that data was sent by the listener process in response to received data.
Recommended Action No action is required.
Error Message%SGBP-7-SENT : MQ [chars] to [IP_address] for query [dec]:[dec], bundle [chars], bid [dec], prot[chars], len [dec]
Explanation This message is generated only when SGBP message debugging is enabled. It indicates that an SGBP packet was sent.
Recommended Action No action is required.
Error Message%SGBP-5-SHUTDOWN : [chars]
Explanation This message is generated only when SGBP event debugging is enabled. A process involved in SGBP was terminated upon completion of its work.
Recommended Action No action is required.
Error Message%SGBP-5-STARTUP : [chars]
Explanation This message is generated only when SGBP event debugging is enabled. An process involved in SGBP was started.
Recommended Action No action is required.
Error Message%SGBP-3-TIMEOUT : Peer [IP_address] bidding; state 'PB [chars]' deleted
Explanation This message is generated only when SGBP event debugging is enabled. It indicates that a peer timed out while closing a query. The connection has been dropped.
Recommended Action Check the peer equipment and network media for problems.
Error Message%SGBP-3-UNEXP : MQ [chars] from [IP_address] for query [dec]:[dec], bundle [chars], bid [dec], state [chars]
Explanation This message is generated only when SGBP error debugging is enabled. The SGBP connection has entered an unexpected state, possibly 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center 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%SGBP-3-UNKNOWN : [IP_address] not known
Explanation This message is generated only when SGBP error debugging is enabled. An SGBP connection was attempted by a host which was not recognized as a peer. The connection was not accepted.
Recommended Action Depending on the network topology and firewalling, SGBP connection attempts from a non-peer host could indicate probing and attempts to breach security. If there is a chance your network is under attack, obtain knowledgeable assistance. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center 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%SGBP-3-UNKNOWNEVENT : Event [hex] from peer at [IP_address]
Explanation This message is generated only when SGBP error debugging is enabled. An invalid event occurred, which probably indicates an internal software error.
Recommended Action LOG_STD_ACTION.
Error Message%SGBP-1-UNKNOWNHELLO : Rcv Hello message from non-group member using [IP_address]
Explanation This message is generated only when SGBP hellos or error debugging is enabled. An SGBP Hello message was received from a host that is not a member of the SGBP group, and discarded.
Recommended Action This is a configuration error. Either that host should be listed in this router's configuration as a member (if that is actually true) or the other host is misconfigured to attempt to join this group.
Error Message%SGBP-3-UNKNOWNPEER : Event [hex] from peer at [IP_address]
Explanation This message is generated only when SGBP error debugging is enabled. An SGBP event came from a network host which was not recognizable as an SGBP peer. The event was discarded.
Recommended Action Check if a network media error could have corrupted the address, or if peer equipment is malfunctioning to generate corrupted packets. Depending on the network topology and firewalling, SGBP packets from a non-peer host could indicate probing and attempts to breach security. If there is a chance your network is under attack, obtain knowledgeable assistance. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.SIP200 Messages
The following are SPA Interface Processor 200 messages.
Error Message%SIP200-3-BADIFCTRL : Corrupted sip-200 information for interface [chars] [[hex]]
Explanation The interface SIP-200 information is not valid. This is an internal software error.
Recommended Action Collect the output of show memory command on the line card and copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SIP200-4-MEM_MODULE_MISMATCH : Memory modules are not identical
Explanation The memory modules do not have identical parameters.This might impact the performance.
Recommended Action Collect the output of show memory command on the line card and copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.SIP200_MP Messages
The following are 7600/Catalyst 6500 SIP-200 multiprocessing messages.
Error Message%SIP200_MP-3-INIT_FAILURE : Second CPU initialization failed
Explanation The line card CPU unit has two CPU cores in it. The second CPU core is not initialized successfully. The line card is operating with one CPU core only. You might also see a SYS-2-MALLOCFAIL warning message.
Recommended Action If this message appears when a line card boots up, reload the line card by entering the hw-module module <slot> reset command. Also, check how much memory the line card has by entering the show controller cwan command.
Error Message%SIP200_MP-4-PAUSE : Non-master CPU is suspended for too long, from [hex]([int]) to [hex] for [int] CPU cycles. [chars]
Explanation The line card CPU contains two CPU cores, one of which is the master CPU. The master CPU caused the second, non-master CPU to be suspended for too long a time. This condition could cause packet drops on the non-master CPU. This warning indicates a transient software problem and the line card should continue to operate normally.
Recommended Action This warning indicates a transient software problem. The line card should continue to operate normally. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SIP200_MP-4-TIMEOUT : Master CPU request timed out [chars]
Explanation The line card CPU contains two CPU cores, one of which is the master CPU. The non-master CPU is not responding in time to the request from the master CPU. This warning indicates a transient software problem. The line card should continue to operate normally.
Recommended Action This warning indicates a transient software problem. The line card should continue to operate normally. If the this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SIP200_MP-1-UNSAFE : Multiprocessor error on [chars]
Explanation The line card CPU contains two CPU cores, one of which is the master CPU. The CPU specified in the error message attempted to perform an operation that is illegal for multiprocessor operation between the two CPU cores.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.SIP200_SPIRX Messages
The following are 7600/Catalyst 6500 SIP-200 SPI4.2 bus ingress interface messages.
Error Message%SIP200_SPIRX-3-INITFAIL : Failed to configure the ingress SPI4.2 device. Error = [hex]
Explanation Unable to program/configure the ingress SPI4.2 device on the line card. This indicates an internal hardware error.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 <spa-id> efc channel <channel-id> command for the SPA.Error Message%SIP200_SPIRX-3-SPA_INTERRUPT : SPA [int] - [chars], SPA Int status = [hex]
Explanation SPA interrupt from the ingress SPI4.2 device.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 <spa-id> efc channel <channel-id> command for the SPA.Error Message%SIP200_SPIRX-3-SRAM_ERROR_DATA :
SRAM[dec] Address = [hex][hex] Data = [hex][hex][hex]_[hex][hex][hex]_[hex][hex][hex]_[hex][hex][hex]Explanation SRAM Address and Data Dump.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 <spa-id> efc channel <channel-id> command for the SPA.Error Message%SIP200_SPIRX-3-SRAM_INTERRUPT : [chars], Sram Int status = [hex]
Explanation SRAM interrupt from the ingress SPI4.2 device.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 <spa-id> efc channel <channel-id> command for the SPA.Error Message%SIP200_SPIRX-3-STATUS_INTERRUPT : [chars], Global Int status = [hex]
Explanation Status interrupt from the ingress SPI4.2 device.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 <spa-id> efc channel <channel-id> command for the SPA.SIP200_SPITX Messages
The following are 7600/Catalyst 6500 SIP-200 SPI4.2 bus egress interface messages.
Error Message%SIP200_SPITX-3-BADDESC : descriptor [hex], tag [hex], global channel [int]
Explanation The egress SPI4.2 device on the line card returns a descriptor entry that is corrupted.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 <spa-id> efc channel <channel-id> command for the SPA.Error Message%SIP200_SPITX-3-BADPAK : corrupted packet to [chars]
Explanation The egress SPI4.2 device on the line card is handling a packet that is corrupted. This indicates an internal software error. The corrupted packet is dropped.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 <spa-id> efc channel <channel-id> command for the SPA.Error Message%SIP200_SPITX-3-CHANNEL_ENABLE_FAIL : SPI4 Channel [int] for Bay [int], [chars] Failed
Explanation Unable to Enable/Disable a given SPI4 Channel.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 <spa-id> efc channel <channel-id> command for the SPA.Error Message%SIP200_SPITX-3-DESCR_ERR_SPA0 : SPAstatus=[hex], syndrome=[hex], RdRspOvf=[int], RdRspTo=[int], OvfVal=[int], OvfCh=[int], OvfDescHi=[hex], OvfDescLo=[hex], DisChk=[int], SeqErrVal=[int], SeqErrCh=[int]
Explanation The egress SPI4.2 device on the line card detected a sequence or fifo overflow error while processing a TX Descriptor. This condition could cause packet drops.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 <spa-id> efc channel <channel-id> command for the SPA.Error Message%SIP200_SPITX-3-DESCR_ERR_SPA1 : SPAstatus=[hex], syndrome=[hex], RdRspOvf=[int], RdRspTo=[int], OvfVal=[int], OvfCh=[int], OvfDescHi=[hex], OvfDescLo=[hex], DisChk=[int], SeqErrVal=[int], SeqErrCh=[int]
Explanation The egress SPI4.2 device on the line card detected a sequence or fifo overflow error while processing a TX Descriptor. This condition could cause packet drops.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 <spa-id> efc channel <channel-id> command for the SPA.Error Message%SIP200_SPITX-3-DESCR_ERR_SPA2 : SPAstatus=[hex], syndrome=[hex], RdRspOvf=[int], RdRspTo=[int], OvfVal=[int], OvfCh=[int], OvfDescHi=[hex], OvfDescLo=[hex], DisChk=[int], SeqErrVal=[int], SeqErrCh=[int]
Explanation The egress SPI4.2 device on the line card detected a sequence or fifo overflow error while processing a TX Descriptor. This condition could cause packet drops.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 <spa-id> efc channel <channel-id> command for the SPA.Error Message%SIP200_SPITX-3-DESCR_ERR_SPA3 : SPAstatus=[hex], syndrome=[hex], RdRspOvf=[int], RdRspTo=[int], OvfVal=[int], OvfCh=[int], OvfDescHi=[hex], OvfDescLo=[hex], DisChk=[int], SeqErrVal=[int], SeqErrCh=[int]
Explanation The egress SPI4.2 device on the line card detected a sequence or fifo overflow error while processing a TX Descriptor. This condition could cause packet drops.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 <spa-id > efc channel <channel-id> command for the SPA.Error Message%SIP200_SPITX-3-DMA_SQERR : Syndrome=[hex], SPA=[int], Ch=[int], RdSz=[int], RdOff=[int][chars]
Explanation The egress SPI4.2 device on the line card detected a sequence error while processing a DMA operation. This condition could cause packet drops.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 <spa-id> efc channel <channel-id> command for the SPA.Error Message%SIP200_SPITX-3-EFC_ERR_SPA0 : SPAstatus=[hex][chars]
Explanation The egress datapath device on the line card detected an error condition with the Extended Flow Control Bus interface. This condition could cause packet drops.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 <spa-id> efc channel <channel-id> command for the SPA.Error Message%SIP200_SPITX-3-EFC_ERR_SPA1 : SPAstatus=[hex][chars]
Explanation The egress datapath device on the line card detected an error condition with the Extended Flow Control Bus interface. This condition could cause packet drops.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 <spa-id> efc channel <channel-id> command for the SPA.Error Message%SIP200_SPITX-3-EFC_ERR_SPA2 : SPAstatus=[hex][chars]
Explanation The egress datapath device on the line card detected an error condition with the Extended Flow Control Bus interface. This condition could cause packet drops.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 <spa-id> efc channel <channel-id> command for the SPA.Error Message%SIP200_SPITX-3-EFC_ERR_SPA3 : SPAstatus=[hex][chars]
Explanation The egress datapath device on the line card detected an error condition with the Extended Flow Control Bus interface. This condition could cause packet drops.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log.Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 <spa-id> efc channel <channel-id> command for the SPA.Error Message%SIP200_SPITX-3-EFCEVNT_ERR : [chars]
Explanation The egress datapath device on the line card detected an error while processing internal extended flow-control events. This condition could cause a reduced packet rate.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 <spa-id > efc channel <channel-id> command for the SPA.Error Message%SIP200_SPITX-3-EFC_QUEUE_STUCK : [chars]
Explanation The egress datapath device on the line card detected an error condition with the Extended Flow Control Bus interface. This condition could cause packet drops.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 <spa-id> efc channel <channel-id> command for the SPA.Error Message%SIP200_SPITX-3-EFCSTAT_FAIL_SPA0 : [chars]
Explanation The egress SPI4.2 device on the line card detected a EFC Status Clock or synchronization failure. This condition could cause packet drops.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 <spa-id> efc channel <channel-id> command for the SPA.Error Message%SIP200_SPITX-3-EFCSTAT_FAIL_SPA1 : [chars]
Explanation The egress SPI4.2 device on the line card detected a EFC Status Clock or synchronization failure. This condition could cause packet drops.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 <spa-id> efc channel <channel-id> command for the SPA.Error Message%SIP200_SPITX-3-EFCSTAT_FAIL_SPA2 : [chars]
Explanation The egress SPI4.2 device on the line card detected a EFC Status Clock or synchronization failure. This condition could cause packet drops.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 <pa-id> efc channel <channel-id> command for the SPA.Error Message%SIP200_SPITX-3-EFCSTAT_FAIL_SPA3 : [chars]
Explanation The egress SPI4.2 device on the line card detected a EFC Status Clock or synchronization failure. This condition could cause packet drops.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 <spa-id> efc channel <channel-id> command for the SPA.Error Message%SIP200_SPITX-3-FCSTAT_FAIL_SPA0 : [chars]
Explanation The egress SPI4.2 device on the line card detected a SPI4.2 Status Clock or synchronization failure. This condition could cause packet drops.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 <spa-id> efc channel <channel-id> command for the SPA.Error Message%SIP200_SPITX-3-FCSTAT_FAIL_SPA1 : [chars]
Explanation The egress SPI4.2 device on the line card detected a SPI4.2 Status Clock or synchronization failure. This condition could cause packet drops.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 <pa-id> efc channel <channel-id> command for the SPA.Error Message%SIP200_SPITX-3-FCSTAT_FAIL_SPA2 : [chars]
Explanation The egress SPI4.2 device on the line card detected a SPI4.2 Status Clock or synchronization failure. This condition could cause packet drops.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 <spa-id> efc channel <channel-id> command for the SPA.Error Message%SIP200_SPITX-3-FCSTAT_FAIL_SPA3 : [chars]
Explanation The egress SPI4.2 device on the line card detected a SPI4.2 Status Clock or synchronization failure. This condition could cause packet drops.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 <spa-id> efc channel <channel-id> command for the SPA.Error Message%SIP200_SPITX-3-INITFAIL : Failed to configure the egress SPI4.2 device. Error = [hex]
Explanation Unable to program/configure the egress SPI4.2 device on the line card. This indicates an internal hardware error.
Recommended Action IIf this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 <spa-id> efc channel <channel-id> command for the SPA.Error Message%SIP200_SPITX-3-INT_PERR_SPA0 : IntMemPerr=[hex][chars]
Explanation The egress SPI4.2 device on the line card detected an internal memory parity error. This condition could cause packet drops.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 <pa-id> efc channel <channel-id> command for the SPA.Error Message%SIP200_SPITX-3-INT_PERR_SPA1 : IntMemPerr=[hex][chars]
Explanation The egress SPI4.2 device on the line card detected an internal memory parity error. This condition could cause packet drops.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 <spa-id> efc channel <channel-id> command for the SPA.Error Message%SIP200_SPITX-3-INT_PERR_SPA2 : IntMemPerr=[hex][chars]
Explanation The egress SPI4.2 device on the line card detected an internal memory parity error. This condition could cause packet drops.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 <spa-id> efc channel <channel-id> command for the SPA.Error Message%SIP200_SPITX-3-INT_PERR_SPA3 : IntMemPerr=[hex][chars]
Explanation The egress SPI4.2 device on the line card detected an internal memory parity error. This condition could cause packet drops.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 <spa-id> efc channel <channel-id> command for the SPA.Error Message%SIP200_SPITX-3-MISMATCH : Descriptor ring mismatch: expects [int] got [int]
Explanation The egress SPI4.2 device on the line card returns a descriptor entry that does not match what the line card CPU expects. This condition could cause packet drops.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 <spa-id> efc channel <channel-id> command for the SPA.Error Message%SIP200_SPITX-3-OVERRUN_DROP : SPI4 overrun drops packet for SPA [int], queue [int], count [int]
Explanation While the egress SPI4.2 device on the line card sends an packet on the extended flow controlled channel, it overruns the SPI4 channel but can not queue it to the internal hold queue. This indicates an internal software error.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 <spa-id> efc channel <channel-id> command for the SPA.Error Message%SIP200_SPITX-3-SPI4_ERR_SPA0 : SPAstatus=[hex][chars]
Explanation The egress SPI4.2 device on the line card detected an error condition with the SPI4.2 Bus interface. This condition could cause packet drops.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 <spa-id> efc channel <channel-id> command for the SPA.Error Message%SIP200_SPITX-3-SPI4_ERR_SPA1 : SPAstatus=[hex][chars]
Explanation The egress SPI4.2 device on the line card detected an error condition with the SPI4.2 Bus interface. This condition could cause packet drops.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 <spa-id> efc channel <channel-id> command for the SPA.Error Message%SIP200_SPITX-3-SPI4_ERR_SPA2 : SPAstatus=[hex][chars]
Explanation The egress SPI4.2 device on the line card detected an error condition with the SPI4.2 Bus interface. This condition could cause packet drops.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 <pa-id> efc channel <channel-id> command for the SPA.Error Message%SIP200_SPITX-3-SPI4_ERR_SPA3 : SPAstatus=[hex][chars]
Explanation The egress SPI4.2 device on the line card detected an error condition with the SPI4.2 Bus interface. This condition could cause packet drops.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 <spa-id> efc channel <channel-id> command for the SPA.Error Message%SIP200_SPITX-3-SRAM_ECCERR : EccSynd=[hex], Err1bit=[int], ErrMbit=[int], SecHalf=[int], SPA=[int], Ch=[int], Addr=[hex], DataHi=[hex], DataLo=[hex], DataEcc=[hex]
Explanation The egress SPI4.2 device on the line card detected a a parity error in the egress packet memory. This condition could cause packet drops.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 <spa-id> efc channel <channel-id> command for the SPA.SIP600 Messages
The following are SPA Interface Processor 600 messages.
Error Message%SIP600-4-MR_CFG_ALL_PORTS : CFM configuration is global to sip-600 and applies to all ports
Explanation An SCP message to configure match register functionality on the specified port will apply to all ports on the MSC-600 card as match register configurations are done on the Parsing Engine.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SIP600-4-SIP10G_PXF_IRAM_PARITY_ERROR : Correcting a PXF instruction error.
Explanation This PXF error was a detection and correction of a typically rare event. If the error is persistent, it might indicate faulty 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.SIP600_QOS Messages
The following are SIP-600 QoS messages.
Error Message%SIP600_QOS-4-NOTINSHAPE : Warning - Ingress shaping on [chars] not supported on this interface.
Explanation Ingress shaping on the specified precedences or DSCP not supported on this interface because such packets are control data, which go through a separate high priority path.
Recommended Action You do not need to reconfigure the QOS policy since the specific match statements are ignored. No action is required.
SIPSPA Messages
The following are Shared Port Adapter on GSR line card messages.
Error Message%SIPSPA-3-BADCMD : [chars]: Unsupported command [dec], arg0=[hex], arg1=[hex], arg2=[hex]
Explanation The Route Processor passed down a command that the software was not prepared to handle.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SIPSPA-3-BAD_IFCOMTYPE : Bad ifcom message type=[int]
Explanation The Route Processor passed down a message that the software was not prepared to handle.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SIPSPA-3-BADINT : Attempted to access HWIDB for port [int]
Explanation The line card attempted to access the HWIDB associated with a non-existent port.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SIPSPA-3-CMDNOINT : HWIDB Null for command [dec], arg=[hex]
Explanation The Route Processor passed down a command that the software was unprepared to handle.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SIPSPA-6-ERRORRECOVER : A Hardware or Software error occurred on [chars]. Reason : [chars] Automatic Error recovery initiated. No further intervention required.
Explanation An error occurred in one of the devices, recovery would be attempted. If recovery succeeds no further messages would be logged and no intervention would be required.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SIPSPA-3-FCI_NOT_SET : Bay [dec]: [chars]: FCI type not set
Explanation An FCI type of zero was detected.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SIPSPA-3-IPCALLOCFAIL : Failed to allocate IPC buffer [chars]
Explanation The line card failed to allocate a buffer for communication with the Route 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center 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%SIPSPA-3-IPCSENDFAIL : Failed to send IPC message [chars]
Explanation The line card failed to send a message to the Route 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center 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%SIPSPA-3-MSGTOOBIG : Message length exceeds max, [int] bytes
Explanation The line card attempted to send too large a message to the route 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message%SIPSPA-3-NODISPATCH : Dispatch vector Null, cmd=[dec], dintf=[dec]
Explanation No command dispatch vector was found for the specified interface.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. 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%SIPSPA-3-SONET_CLOCK_FAILED : SPA Sonet clock has failed (status = [hex])
Explanation The SPA SONET clock has failed. SPAs that rely on the SPA SONET clock for proper operation, such as POS and ATM will be affected.
Recommended Action If the SPA Sonet clock does not recover, perform an OIR.
Error Message%SIPSPA-3-SONET_CLOCK_RECOVERED : SPA Sonet clock has recovered (status = [hex])
Explanation SPA Sonet clock has recovered.
Recommended Action No action is required.
SLB Messages
The following are Server Load Balancing messages.
Error Message%SLB-4-IF_REMOVED : Access interface removed: [chars] [chars] being set to outofservice.
Explanation An interface being referenced in slb access configuration has been removed. The vserver, or firewall farms referencing this interface will be brought out of service.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.SLB_KAP Messages
The following are SLB_KAP messages.
Error Message%SLB_KAP-3-BIND_FAIL : SLB Keep Alive Application Protocol Socket_bind failed for Port:[dec]
Explanation SLB Keep Alive Application Protocol process attempts to bind a socket port failed.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SLB_KAP-4-UNEXPECTED : Unexpected error: [chars]
Explanation An unexpected error occurred while performing SLB Keep Alive Application Protocol operation.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.SMC Messages
The following are Smart Cookie messages.
Error Message%SMC-2-BAD_ID_HW : Failed Identification Test in [chars] [[dec]/[dec]]
The module in [chars] in this router might not be a genuine Cisco product. Cisco warranties and support programs only apply to genuine Cisco products. If Cisco determines that your insertion of non-Cisco memory, WIC cards, AIM cards, Network Modules, SPA cards, GBICs or other modules into a Cisco product is the cause of a support issue, Cisco might deny support under your warranty or under a Cisco support program such as SmartNet.
Explanation Hardware in the specified location could not be identified as a genuine Cisco product.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SMC-2-FAILED_ID_HW : Failed Identification Test in [chars] [[dec]/[dec]]
Explanation There was a problem while identifying hardware in the specified location.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SMC-2-PROTO_HW : Module ([chars]) is a registered proto-type for Cisco Lab use only, and not certified for live network operation.
Explanation Hardware in the specified location is a prototype module that came from Cisco.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.SM-SP Messages
The following are State Machine SP messages.
Error Message%SM-SP-4-BADEVENT : Event `[chars]' is invalid for the current state `[chars]': [chars] [chars]
Explanation An attempt was made to post an event to a state machine that is invalid for the current state.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered informationSNASW Messages
The following are Systems Network Architecture (SNA) Switching Services messages.
Error Message%SNASW-3-CLS_LOG_0 : PROBLEM - [int] - Could not validate process handle [chars]
Explanation CLS has passed SNA Switch a DLC packet, but SNA Switch does not have a valid handle to invoke the correct SNA process. The CLS message has been discarded.
Recommended Action Dump traces. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center 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%SNASW-3-HPR_LOG_20 : PROBLEM - [int] - Remote node supplied a corrupted RSCV: the next hop is the local CP [chars]
Explanation An HPR Route Setup RU has been received with an RSCV that gives the local node as the next ANR hop. This is invalid. Therefore the remote node is sending invalid protocol data.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SNASW-4-RTP_LOG_10 : EXCEPTION - [int] - LFSID in use, moving on to next one. [chars]
Explanation An LFSID was found to be in use so SNA Switch is using a different one.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.SNMP Messages
The following are Simple Network Management Protocol (SNMP) messages.
Error Message%SNMP-3-BADIFINDEXTABLE : The file nvram:ifIndex-table is corrupt.
Explanation The file is not in the expected format.
Recommended Action If possible, delete the file.
Error Message%SNMP-3-DVR_DUP_REGN_ERR : Attempt for dupe regn with SNMP IM by driver having ifIndex [dec] and ifDescr [chars]
Explanation Driver is attempting to register an idb with the interface manager while there is already an interface with the same ifIndex and ifDescr BUT different idb registered. This would lead to the problem that interface counters shown by snmp would not work properly for this particular interface.
Recommended Action Fix the duplicate registration in driver level.
Error Message%SNMP-3-DVR_DUP_REGN_WARNING : Attempt for dupe regn with SNMP IM by driver having ifIndex [dec] and ifDescr [chars]
Explanation Driver is attempting to register the same idb with the interface manager while it is already registered. This is just a warning message and handled by snmp.
Recommended Action Fix the duplicate registration in driver level.
Error Message%SNMP-3-DYNSYNCFAIL : Snmp Dynamic Sync Failed for [chars] = [chars]
Explanation One of the SNMP MIB Dynamic Sync(sync of Snmp SET) to standby failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SNMP-4-HIGHCPU : Process exceeds [dec]ms threshold ([dec]ms IOS quantum) for [chars] of [chars]--result [chars]
Explanation SNMP took more than the warning threshold processing a var-binding.
Recommended Action If feasible, use the debug snmp packet command to determine the contents of the SNMP request that is causing the message. Copy the error message exactly as it appears, and report it along with any debug output to your technical support representative. Some MIB objects require a relatively large amount of time to process. MIB objects in the multi-variable-binding are processed one by one. If possible, MIB objects appearing in this message should NOT be retrieved using multi-variable-binding SNMP PDUs.
Error Message%SNMP-3-INPUT_QFULL_ERR : Packet dropped due to input queue full
Explanation Snmp packet dropped due to input queue full error.
Recommended Action Use the command show snmp to see the number of packets dropped. Stop any SNMP access to the device until the error condition is recovered.
Error Message%SNMP-3-INTERRUPT_CALL_ERR : [chars] function, cannot be called from interrupt handler
Explanation A call has been made to the specified function from an interrupt handler. This is not permitted because it will fail and the device will reboot down the stack in memory allocation call.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. 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%SNMP-3-ISSU_ERR : [chars]
Explanation There has been an error during an ISSU versioning operation.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message%SNMP-5-LINK_DOWN : LinkDown:Interface [chars] changed state to down
Explanation The state of the Interface is changed to down.
Recommended Action No action is required.
Error Message%SNMP-5-LINK_UP : LinkUp:Interface [chars] changed state to up
Explanation The state of the Interface is changed to up.
Recommended Action No action is required.
Error Message%SNMP-3-MAX_TRAPS_EXCEED_ERR : Maximum number of traps exceeded the maximum allowed in the current sync-message to STANDBY
Explanation This message indicates the number of SNMP traps defined exceeded the maximum we can accomodate in a checkpoint sync-message. You need to increase SNMP_SYNC_BITMASK_MAX to a higher value. Check smci_rf_status_event() for further details.
Recommended Action Developers will never see this error message.
Error Message%SNMP-5-MODULERESET : [chars] object has been set to 'reset' for [chars]=[dec] from IP address [chars].
Explanation The SNMP server has reset a module.
Recommended Action Notification message only. No action required.
Error Message%SNMP-3-SYNCFAIL : SNMP MIB Sync Failure: [chars]
Explanation One of the SNMP MIB Synchronization to standby failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.SNMP_BULKSTAT Messages
The following are SNMP bulk-data collection messages.
Error Message%SNMP_BULKSTAT-3-5 : Memory not available for [chars] for [chars]
Explanation Data Collection or Transfer could not be successfully performed because of lack of memory.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%SNMP_BULKSTAT-4-BUFFER_OVERFLOW : Buffer size too small to accomodate data for one collection interval for [chars]
Explanation The bulk data file is too large for the configured buffer size for a single transfer interval. Data collection will continue in another new buffer of the configured size, and the collected buffer will be transferred to the configured destination.
Recommended Action Increase the maximum buffer size using the buffer-size <size-of-buffer> command, where size-of-buffer is the increased buffer size.
Error Message%SNMP_BULKSTAT-3-NO_MEMORY : Memory not available for [chars] for [chars]
Explanation The data collection or Transfer could not be successfully carried out because of lack of memory.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%SNMP_BULKSTAT-4-PRI_URL_UNREACHABLE : Primary network management station is unreachable for [chars]
Explanation The Collected Bulk data file could not be successfully transferred to the primary network management station address specified in the error message. This condition can occur because the primary network management address is not configured or the configured primary network management station address is unreachable. If a secondary network management station address is configured, the collected bulk data file will be sent to the secondary network management station address.
Recommended Action Ensure that the primary network management station address is configured. If the primary network management station address is configured, check the connectivity to the destination indicated by the primary network management station address specified in the error message.
Error Message%SNMP_BULKSTAT-3-REMOTE_FILE_WRITE_ERR : File Write failed for the remote file [chars]
Explanation Username or password specified in the error message might not have the required privileges to write a file to the network management station specified in the error message, or the destination directory specified in the error message is invalid.
Recommended Action Ensure that the user name and password in the network management station address have the necessary privileges to write to the destination directory.
Error Message%SNMP_BULKSTAT-4-SEC_URL_UNREACHABLE : Secondary network management station is unreachable for [chars]
Explanation The collected bulk data file could not be successfully transferred to the secondary network management station address destination specified in the error message. This condition can occur because the secondary network management station address is not configured or the configured secondary network management station address is unreachable. If a retention interval is not configured, the bulk data file will be immediately deleted. If a retention interval is configured, retries will be attempted for the configured number of times.
Recommended Action Check the connectivity to destination indicated by secondary network management station address indicated in the error message
Error Message%SNMP_BULKSTAT-3-TOOSMALL_BUFFER : Buffer size is insufficient to accommodate even the header part for [chars]
Explanation The buffer size is insufficient to accommodate the header for the bulk data file. The header contains the schema definitions of all the configured schemas.
Recommended Action Increase the maximum buffer size using the buffer-size size-of-buffer command, where size-of-buffer is the increased buffer size.
SNMP_CONTEXT_ MAPPING Messages
The following are Simple Network Management Protocol Context Mapping messages.
Error Message%SNMP_CONTEXT_MAPPING-3-TOPO_NOT_BASE : Multi Topology un-aware component is accessing a non base topology [chars], topoid [dec]
Explanation A software component that is not multi-topology aware is accessing a non base topology. When this happens the result is un-predictable.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.SNMP_MIB_ISSU Messages
Error Message%SNMP_MIB_ISSU-3-CAP_INVALID_SIZE : SNMP MIB ISSU client capability list is empty.
Explanation The SNMP MIB ISSU client capability exchange list size is invalid.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu capability entires <Client_ID> command to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center 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%SNMP_MIB_ISSU-3-CAP_NOT_COMPATIBLE : SNMP MIB ISSU client capability exchange result incompatible.
Explanation The SNMP MIB ISSU client capability exchange have negotiated as incompatible with the peer.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu negotiated capability <Session_ID> command to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SNMP_MIB_ISSU-2-GET_BUFFER : SNMP MIB ISSU client failed to get buffer for message. Error: [dec] ([chars])
Explanation The SNMP MIB 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 Copy the message exactly as it appears on the console or in the system log. Enter the show logging and show checkpoint client commands to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SNMP_MIB_ISSU-2-INIT : SNMP MIB ISSU client initialization failed to [chars]. Error: [dec] ([chars])
Explanation The SNMP MIB 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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center 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%SNMP_MIB_ISSU-3-INVALID_SESSION : SNMP MIB ISSU client does not have a valid registered session.
Explanation The SNMP MIB 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. Enter the show issu capability entries <client_id> and show issu session <client_id> and show issu negotiated capability <session_id> commands to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SNMP_MIB_ISSU-3-MSG_NOT_OK : SNMP MIB ISSU client 'Message Type [dec]' is not compatible
Explanation The SNMP MIB ISSU client received an incompatible message from the peer device. The message cannot be processed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu message group <client_id> and show issu session <client_id> and show issu negotiated version <session_id> commands to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SNMP_MIB_ISSU-3-MSG_SIZE : SNMP MIB ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] ([chars])
Explanation The SNMP MIB ISSU client failed to calculate the MTU for the specified message. The SNMP MIB ISSU client is not able to send the message to the standby device.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu message group <client_id> and show issu session <client_id> and show issu negotiated version <session_id> command to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SNMP_MIB_ISSU-2-SEND_NEGO_FAILED : SNMP MIB ISSU client failed to send negotiation message. Error: [dec] ([chars])
Explanation The SNMP MIB 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 Copy the message exactly as it appears on the console or in the system log. Enter the show logging and show checkpoint client commands to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SNMP_MIB_ISSU-2-SESSION_NEGO : SNMP MIB ISSU client encountered unexpected client nego_done. Error: [dec] ([chars])
Explanation An ISSU-compliant client transitions through a series of internal states. The SNMP MIB ISSU client encountered a 'client negotiation done' state that was unexpected. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu session <client_id> and show issu negotiated capability <session_id> commands to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SNMP_MIB_ISSU-2-SESSION_REGISTRY : SNMP MIB ISSU client failed to register session information. Error: [dec] ([chars])
Explanation The SNMP MIB 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 Copy the message exactly as it appears on the console or in the system log. Enter the show issu capability entries <client_id> and show issu session <client_id> and show issu negotiated capability <session_id> commands to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SNMP_MIB_ISSU-3-SESSION_UNREGISTRY : SNMP MIB ISSU client failed to unregister session information. Error: [dec] ([chars])
Explanation The SNMP MIB ISSU client failed to unregister session information.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu session <client_id> and show issu negotiated capability <session_id> commands to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SNMP_MIB_ISSU-3-TRANSFORM_FAIL : SNMP MIB ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] ([chars])
Explanation The SNMP MIB 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 SNMP MIB state between the active device and the standby device is not identical.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu session <client_id> and show issu negotiated version <session_id> commands to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.SNMP-STDBY Messages
The following are Simple Network Management Protocol Standby messages.
Error Message%SNMP-STDBY-5-COLDSTART : Cold Start Trap
Explanation The sending protocol entity is re-initializing itself so the configuration of the agent or the protocol entity implementation might be altered.
Recommended Action Informational message only. No action is required.
SONET Messages
The following are Synchronous Optical Network messages.
Error Message%SONET-3-DELAYTIMER : [chars]
Explanation Delay timer creation failure.
Recommended Action Report this occurrence to Engineering. Use Topic to search for a similar DDTS. If you find none, write a DDTS for this problem.
SPA Messages
The following are Shared Port Adapter messages.
Error Message%SPA-3-SW_ERROR : NULL
Explanation This error is seen when there is a problem in internal software coding. It should not be seen in normal operation.
Recommended Action LOG_STD_ACTION.
SPA_CHOC_DSX Messages
The following are Common Channelized Shared Port Adapter messages.
Error Message%SPA_CHOC_DSX-3-AUTODNR : [chars] failed for slot [dec] bay [dec]
Explanation AUTODNR/USNDNR process has failed.The SPA and LC are out of synchronization. This condition indicates 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.Error Message%SPA_CHOC_DSX-3-PERIODIC_PROCESS : [chars]: periodic process error [chars].
Explanation The SPA driver detected an error with the periodic processing routine.
Recommended Action If the ports on the SPA are not operating as expected, take it out of service by entering the hw-module subslot slot#/bay# stop command followed by hw-module subslot slot#/bay# start command for the indicated SPA card. If the error messages 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center 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%SPA_CHOC_DSX-3-SEMAHOG : SPA on [chars]: Semaphore Hog was encountered.Hogged by process [chars]
Explanation The semaphore used by the IPC communication between host and the SPA was hogged by one process. This behavior would cause other processes to fail to send commands down to the SPA. This might result in improper operation.
Recommended Action First, stop all the traffic on the SPA and then reload the configuration by entering a shut command then a no shut command on the controllers. If this message recurs, power cycle the SPA. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Provide the information you have gathered with a show tech-support command to your support representative, or attach it to your case in non-zipped, plain text format (.txt).Error Message%SPA_CHOC_DSX-3-VCCFG_ERROR : Interface [chars] config command error (cmd [int], arg [int], retval [int])
Explanation A command sent from the system to a line card has failed.
Recommended Action This is an internal software error. Decode the traceback and get the output of the show logging command on RP and SIP1 and check if there are any errors being reported. Try to recreate the problem to see if there is a consistant method to recreate. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Provide the above information along with the output of the show tech-support command.SPA_CHOCX Messages
The following are CHOCX shared port adapter messages.
Error Message%SPA_CHOCX-3-CORRUPT : Corrupt configuration, unsupported [chars] ([int]) encountered
Explanation The OC3/STM1 RP driver running configuration is corrupt.
Recommended Action This is a internal software error. Decode the traceback. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show running-config command and your pertinent troubleshooting logs.Error Message%SPA_CHOCX-3-CREATE_FAIL : Failed to create [chars] : slot/bay:[dec]/[dec]
Explanation The CHOCX SPA controller descriptor block creation failed. Check the amount of system memory available.
Recommended Action Upgrade your system to the latest version of Cisco IOS software in your release train. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message%SPA_CHOCX-5-DEF_SUBRATE : [chars] [chars]
Explanation The remote subrate configuration has changed.
Recommended Action Inform the network operator that subrate configuration changed by remote end.
Error Message%SPA_CHOCX-3-FATAL_ERROR : Fatal error for [chars] : slot/bay:[dec]/[dec]
Explanation The CHOCX SPA controller encounters a fatal error.
Recommended Action Upgrade your system to the latest version of Cisco IOS software in your release train. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message%SPA_CHOCX-3-FRR_ERROR : Error in handling FRR: [chars], [chars], [hex], [hex]
Explanation An error occurred during FRR processing.
Recommended Action This is a internal software error. If this message recurs, decode the traceback. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac and the SPA hardware troubleshooting documentation. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show running-config command and your pertinent troubleshooting logs.Error Message%SPA_CHOCX-3-INVALID_SPA_TYPE : Invalid SPA type : slot/bay:[dec]/[dec], spa_type=[dec].
Explanation The CHOCX SPA type cannot be recognized by the version of Cisco IOS software currently running on the system
Recommended Action Upgrade your system to the latest version of Cisco IOS software in your release train. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message%SPA_CHOCX-3-"NULL" : NULL [chars]
Explanation The NULL pointer was seen when getting the data structure.
Recommended Action This is a internal software error. Decode the traceback. Enable debug hw-module subslot <slot>/<bay> oir plugin when the problem is happening. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Also provide the output of the show logging and show tech commands.Error Message%SPA_CHOCX-3-NULL_INSTANCE : Null [chars] instance for [chars] : slot/bay:[dec]/[dec]
Explanation The instance pointer is NULL when getting datastructure.
Recommended Action This is a internal software error. Decode the traceback and get the output of show running-config. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. along with the output of show running and show tech details.Error Message%SPA_CHOCX-3-NULL_SUBBLOCK : Null ssb for [chars]
Explanation The HWIDB subblock is NULL.
Recommended Action This is a internal software error. Decode the traceback. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac and the SPA hardware troubleshooting documentation. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show running-config command and your pertinent troubleshooting logs.Error Message%SPA_CHOCX-3-RETURN_ERROR : Return error for [chars]: return_value=[dec]
Explanation Return error code received.
Recommended Action This is a internal software error. Decode the traceback and get the output of the show running-config command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Also provide the output of the show running and show tech commands.Error Message%SPA_CHOCX-3-UNKNOWN_OPTION : Received unknown [chars]: option=[dec]
Explanation Unknown option received.
Recommended Action This is a internal software error. Decode the traceback and get the output of show running-config. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Also provide the output of the show running and show tech commands.SPA_CHOCX_CWRP Messages
The following are CWRP CHOCX Shared Port Adapter interfaces messages.
Error Message%SPA_CHOCX_CWRP-1-ALLOCFAIL : OC3/STM1 [dec]/[dec] [chars] allocation failure
Explanation CHOCX controller or channel memory allocation failure.
Recommended Action This is a internal software error. Decode the traceback. Enable debug hw-module subslot <slot>/<bay> oir plugin when the problem is happening. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Also provide the output of the show logging and show tech commands.Error Message%SPA_CHOCX_CWRP-3-APS_CMD_FAIL : Failed to send APS command [hex] to [chars] (retcode [hex])
Explanation APS command sending failed.
Recommended Action This is a internal software error. If this error happened while configuring APS, try reconfiguring the interface. If the error persists or occurred during normal operation, decode the traceback and copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SPA_CHOCX_CWRP-3-CORRUPT : Corrupt configuration, unsupported [chars] ([int]) encountered
Explanation The OC3/STM1 RP driver running configuration is corrupt.
Recommended Action This is a internal software error. Copy the message exactly as it appears on the console or in the system log. Enter the show running-config to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Provide the output of the show tech command.Error Message%SPA_CHOCX_CWRP-5-DEF_SUBRATE : [chars] [chars]
Explanation Remote subrate configuration changed.
Recommended Action Inform the network operator that subrate configuration changed by remote end.
Error Message%SPA_CHOCX_CWRP-3-FRR_ERROR : Error in handling FRR: [chars], [chars], [hex], [hex]
Explanation Error in FRR processing.
Recommended Action This is a internal software error. If this error happened while configuring FRR, try reconfiguring the interface. If the error persists or occurred during normal operation, decode the traceback and copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%SPA_CHOCX_CWRP-3-NULL_SUBBLOCK : Null ssb for [chars]
Explanation The hwidb subblock is NULL.
Recommended Action This is a internal software error. Decode the traceback and get the output of show running-config. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Also provide the output of the show running and show tech commands.Error Message%SPA_CHOCX_CWRP-5-PATH_UPDOWN : Path [chars], changed state to [chars]
Explanation A Sonet high order path changed its state.
Recommended Action This is a internal software error. Decode the traceback and get the output of show controller sonet. Look into this output to see if there are any alarms being reported at the path level. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Also provide the above information along with the output of show tech detailsError Message%SPA_CHOCX_CWRP-3-PLUGIN_ERR : [chars]
Explanation The RP plugin encountered an error during one of the Plugin calls.
Recommended Action This is a internal software error. Decode the traceback. Enable debug hw-module subslot <slot>/<bay> oir plugin when the problem is happening. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Also provide the above information along with the output of the show logging andshow tech commands.Error Message%SPA_CHOCX_CWRP-5-T3_UPDOWN : T3 [chars], changed state to [chars]
Explanation A T3 within STS1 changed its state.
Recommended Action This is a internal software error. Decode the traceback and get the output of show controller sonet. Look into this output to see if there are any alarms being reported at the T3 level. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Also provide the above information along with the output of show tech detailsError Message%SPA_CHOCX_CWRP-3-TIMEOUT : Interface ([chars]): [chars]
Explanation The CHOCX RP driver queries the LC for SONET information, the LC didn't reply.
Recommended Action This is a internal software error. Decode the traceback. Enable debug hw-module subslot <slot>/<bay> command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Provide the above information along with the output of the show logging and show tech <NoCmdBold> commands.SPA_ETHER Messages
The following are 4-port 10/100, 2-Port 10/100/1000 Ethernet Shared Port Adapter messages.
Error Message%SPA_ETHER-1-ALLOCFAIL : Subslot [dec]/[dec], [chars] allocation failure ([chars])
Explanation The router has failed to allocate sufficient memory for a software module on the Ethernet SPA located in the specified subslot. The error message indicates the modular services card slot, the SPA subslot, the SPA type and the name of the software module.
Recommended Action Perform OIR of the SPA located in the specified subslot. Before removing the SPA, enter the hw-module subslot stop command. Remove th SPA, wait 5 seconds, and reinsert the SPA into the MSC. Enter the show memory summary command to gather data that might identify the nature of the message. Reduce system activity to reduce memory demands. If conditions warrant, upgrade to a larger memory configuration. If you require further assistance, reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%SPA_ETHER-4-BAY_NOT_FOUND : Subslot [dec]/[dec], [chars] Failed to get the bay information
Explanation Unable to retrieve a software data structure for the subslot. The error message indicates the modular services card slot, the affected subslot and the SPA type. This error indicates a software caveat.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SPA_ETHER-3-HW_ERROR : Subslot [dec]/[dec], [chars] Hardware device error ([chars]) detected, reactivating the SPA
Explanation An internal hardware device error has occurred on the Ethernet SPA. The error message indicates the modular services card slot, the SPA subslot, the SPA type and the name of the hardware device. The SPA has been deactivated and reactivated to resolve the problem. If the error occurs more than five times within an hour, no further attempts to reactivate the SPA will be made. This message is likely due to an unrecoverable hardware failure.
Recommended Action Perform OIR of the SPA located in the specified subslot. Before removing the SPA, enter the hw-module subslot stop command. Remove the SPA, wait 5 seconds, and reinsert the SPA into the MSC. If this message recurs, copy the message exactly as it appears on the console or in the system log. Enter the show diag command to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SPA_ETHER-3-INITFAIL : Subslot [dec]/[dec], [chars] initialization failure ([chars])
Explanation The initialization of an internal device on the Ethernet SPA in the specified subslot has failed. The error message indicates the modular services card slot, the SPA subslot, the SPA type and the name of the device that failed to initialize. The message also provides the interface name and other details about the error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SPA_ETHER-3-INVALID_PORT : Subslot [dec]/[dec], [chars] Incorrect port number ([dec]) specified for SPA
Explanation An internal error has been encountered by the Ethernet software driver for the SPA. The error message indicates the modular services card slot, the SPA subslot, the SPA type and the invalid interface port number. This problem is caused by a software caveat.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that migh