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-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 : RTR: Cannot create a new process
Explanation RTR is unable to start a new process, and might 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.
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-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 problem persists, LOG_STD_ACTION.
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-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 problem persists, LOG_STD_ACTION.
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.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_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.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-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.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