Cisco 6500 Sp By Bus Error At Pc
Contents |
Catalyst 6500 Series SwitchesTroubleshoot and AlertsTroubleshooting TechNotes Catalyst 6000/6500 System Crashes Troubleshooting Download Print Available Languages Download Options PDF (159.2 KB) View with Adobe Reader on a
System Returned To Rom By Address Error At Pc
variety of devices ePub (82.3 KB) View in various apps on iPhone, iPad, system returned to rom by bus error at pc 0x0 address 0x0 Android, Sony Reader, or Windows Phone Mobi (Kindle) (89.2 KB) View on Kindle device or Kindle app on multiple "last reload reason address error at pc" devices Updated:Jun 13, 2016 Document ID:71095 ContentsIntroductionPrerequisitesRequirementsComponents UsedConventionsSupervisor Module Related CrashesSystem Returned to ROM by Power-on (SP by Abort)System Receives a Software Forced CrashSystem Returns to ROM by Unknown Reload Cause%PM_SCP-1-LCP_FW_ERR%SYSTEM_CONTROLLER-3-FATALFaulty Fan
Bus Error Linux
Causes the Supervisor to CrashSwitch Has Reset/Rebooted on Its OwnDFC-Equipped Module Has Reset on Its OwnBooting from the Wrong Device Causes a CrashCONST_DIAG-2-HM_SUP_CRSHEARL Driver: lyra_purge_search:process_push_event_list failedSNMP Query in ROMMon Upgrade Crashes the Switch%Error Opening Bootflash:Crashinfo (File Not Found)MSFC Module Related CrashesSystem Receives a Bus Error ExceptionSystem Receives a Cache Parity ExceptionOther Parity Related Errors%MISTRAL-3-ERRORGeneric Diagnostic Procedures for Switches that run CatOSSanity Check for CatOSRecover
System Returned To Rom By S/w Reset
Catalyst Switches that run CatOS from Booting FailuresRetrieve Information from the Crashinfo FileTroubleshoot Based on Error MessagesRelated Information Introduction This document discusses how to troubleshoot Cisco Catalyst 6000/6500 Series Switch Supervisor Engine switch processor (SP) and Multilayer Switch Feature Card (MSFC) route processor (RP) crashes. Prerequisites Requirements There are no specific requirements for this document. Components Used The information in this document is based on the Cisco Catalyst 6000/6500 Series Switch Supervisors and MSFC modules. The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command. Conventions Refer to Cisco Technical Tips Conventions for more information on document conventions. Supervisor Module Related Crashes System Returned to ROM by Power-on (SP by Abort) A Catalyst 6500/6000 with an SP configuration register that allows break, for example 0x2, and that receives a console break signal enters ROMmon diagnostic mode. The system appears to crash. Thi
Help Follow Us Facebook Twitter Google + LinkedIn Newsletter Instagram YouTube DirectoryNetwork InfrastructureWAN, Routing and Switching LAN, Switching and system was restarted by bus error at pc Routing Network Management Remote Access Optical Networking Getting
Cisco Bus Error
Started with LANs IPv6 Integration and Transition EEM Scripting Other Subjects SecurityVPN Security Management cisco crashinfo analyzer Firewalling Intrusion Prevention Systems/IDS AAA, Identity and NAC Physical Security MARS Email Security Web Security Other Subjects Service ProvidersMetro MPLS Voice Over http://www.cisco.com/c/en/us/support/docs/switches/catalyst-6500-series-switches/71095-6500-system-crash-ts.html IP XR OS and Platforms Video Other Subjects Collaboration, Voice and VideoIP Telephony Video Over IP Jabber Clients Unified Communications Applications TelePresence Digital Media System Contact Center Conferencing UC Migrations Other Subjects Wireless - MobilitySecurity and Network Management Wireless IP Voice and Video Getting Started https://supportforums.cisco.com/discussion/11433936/cat-6509-reboot with Wireless WLCCA Other Subjects ServicesCisco ServiceGrid Connected Analytics Smart Call Home Smart Net Total Care Operations Exchange Mobile ApplicationsCisco Proximity Cisco Technical Support Online Tools and ResourcesCisco Bug Discussions Technical Documentation Ideas Cisco CLI Analyzer Support Community Help Data CenterApplication Centric Infrastructure Application Networking Intelligent Automation Server Networking Storage Networking Unified Computing Wide Area Application Services (WAAS) Other Subjects Small BusinessNetwork Storage Routers Security Surveillance Switches Voice and Conferencing Wireless Solutions and ArchitecturesBorderless Networks Collaboration Cisco User GroupsSeattle Cisco User Group (SEACUG) Silicon Valley Cisco User Group (SVCUG) Southern California Cisco User Group (SCCUG) Cisco Certifications Cisco.com Idea Center Cisco Cafe Expert CornerTop Contributors Leaderboards Cisco Live! Events Events Community CornerAwards & Recognition Behind the Scenes Feedback Forum Cisco Certifications Cisco Press Café Cisco On Demand Support & Downloads Community
Catalyst 6500 Series http://www.cisco.com/c/en/us/support/docs/switches/catalyst-6500-series-switches/41265-186-ErrormsgIOS-41265.html SwitchesTroubleshoot and AlertsTroubleshooting TechNotes Common Error Messages on http://www.gossamer-threads.com/lists/cisco/nsp/124906 Catalyst 6500/6000 Series Switches Running Cisco IOS Software Download Print Available Languages Download Options PDF (219.3 KB) View with Adobe Reader on a variety of devices ePub (98.6 KB) View in various apps bus error on iPhone, iPad, Android, Sony Reader, or Windows Phone Mobi (Kindle) (129.2 KB) View on Kindle device or Kindle app on multiple devices Updated:Jul 14, 2016 Document ID:41265 ContentsIntroductionPrerequisitesRequirementsComponents UsedConventions%C6KPWR-SP-4-UNSUPPORTED: unsupported module in slot [num], power not allowed: [chars]ProblemDescriptionWorkaround%DUAL-3-INTERNAL: IP-EIGRP error at pc 1: Internal ErrorProblemDescriptionWorkaround%EARL_L3_ASIC-SP-4-INTR_THROTTLE: Throttling "IP_TOO_SHRT"ProblemDescriptionWorkaround%EARL_L3_ASIC-SP-3-INTR_WARN: EARL L3 ASIC: Non-fatal interrupt [chars]ProblemDescriptionWorkaround%EARL_NETFLOW-4-TCAM_THRLD: Netflow TCAM threshold exceeded, TCAM Utilization [[dec]%]ProblemDescriptionWorkaround%ETHCNTR-3-LOOP_BACK_DETECTED : Keepalive packet loop-back detected on [chars]ProblemDescriptionWorkaroundloadprog: error - on file open boot: cannot load "cisco2-Cat6k-MSFC"ProblemDescriptionWorkaround%L3_ASIC-DFC3-4-ERR_INTRPT: Interrupt TF_INT:FI_DATA_INTProblemDescription%MLS_STAT-SP-4-IP_LEN_ERR: MAC/IP length inconsistenciesProblemDescription%MLS_STAT-SP-4-IP_CSUM_ERR: IP checksum errorsProblemDescriptionWorkaround%MCAST-SP-6-ADDRESS_ALIASING_FALLBACKProblemDescriptionc6k_pwr_get_fru_present(): can't find fru_info for fru type 6, #ProblemDescription%MROUTE-3-TWHEEL_DELAY_ERRProblemDescriptionWorkaround%MCAST-SP-6-GC_LIMIT_EXCEEDEDProblemDescriptionWorkaround%MISTRAL-SP-3-ERROR: Error condition detected: TM_NPP_PARITY_ERRORProblemDescription%MLS_STAT-4-IP_TOO_SHRT: Too short IP packets receivedProblemDescriptionProcessor [number] of module in slot [number] cannot service session requestsProblemDescription%PM_SCP-1-LCP_FW_ERR: System resetting module [dec] to recover from error: [chars]ProblemDescriptionWorkaround%PM_SCP-2-LCP_FW_ERR_INFORM: Module [dec] is experiencing the following error: [chars]ProblemDescriptionWorkaround%PM_SCP-SP-2-LCP_FW_ERR_INFORM: Module [dec] is experiencing the following error: [chars]ProblemDescriptionWorkaround%PM_SCP-SP-4-UNK_OPCODE: Received unknown unsolicited message from module [dec], opcode [hex]ProblemDescriptionWorkaround%PM_SCP-SP-3-TRANSCEIVER_BAD_EEPROM: Integrity check on transceiver in LAN port 5/2 failed: bad keyProblemDescription%PM_SCP-SP-3-LCP_FW_ABLC: Late collision message from module [
Post #1 of 4 (2389 views) Permalink 6500 having a seizure Hey all... So we've been having issues with this 6500 for awhile now, just doing random stuff so we replaced the chassis and one of the Sups, so today while I was at lunch (doesn't it always happen this way) the switch had one of these: System returned to ROM by Stateful Switchover (SP by bus error at PC 0x402DF924, address 0x0) Good times, so after the switch finally "recovered" I noticed this in my log: .Feb 3 15:46:59.272 EST: %PM-SP-4-PORT_BOUNCED: Port Fa13/41 was bounced by Consistency Check IDBS Up. .Feb 3 15:46:59.272 EST: %PM-SP-4-PORT_BOUNCED: Port Fa13/42 was bounced by Consistency Check IDBS Up. .Feb 3 15:46:59.272 EST: %PM-SP-4-PORT_BOUNCED: Port Fa13/43 was bounced by Consistency Check IDBS Up. .Feb 3 15:46:59.272 EST: %PM-SP-4-PORT_BOUNCED: Port Fa13/44 was bounced by Consistency Check IDBS Up. .Feb 3 15:46:59.272 EST: %PM-SP-4-PORT_BOUNCED: Port Fa13/45 was bounced by Consistency Check IDBS Up. .Feb 3 15:46:59.272 EST: %PM-SP-4-PORT_BOUNCED: Port Fa13/46 was bounced by Consistency Check IDBS Up. ..Feb 3 15:46:59.276 EST: %PM-SP-4-PORT_BOUNCED: Port Fa13/48 was bounced by Consistency Check IDBS Up. Feb 3 15:46:59.276 EST: %PM-SP-4-PORT_BOUNCED: Port Fa3/41 was bounced by Consistency Check IDBS Down. .Feb 3 15:46:59.276 EST: %PM-SP-4-PORT_BOUNCED: Port Fa3/42 was bounced by Consistency Check IDBS Down. .Feb 3 15:46:59.276 EST: %PM-SP-4-PORT_BOUNCED: Port Fa3/43 was bounced by Consistency Check IDBS Down. .Feb 3 15:46:59.276 EST: %PM-SP-4-PORT_BOUNCED: Port Fa3/44 was bounced by Consistency Check IDBS Down. .Feb 3 15:46:59.276 EST: %PM-SP-4-PORT_BOUNCED: Port Fa3/45 was bounced by Consistency Check IDBS Down .Feb 3 15:47:00.304 EST: %PM-SP-4-PORT_BOUNCED: Port Fa3/47 was bounced by Consistency Check IDBS Down. .Feb 3 15:47:00.304 EST: %PM-SP-4-PORT_BOUNCED: Port Fa3/48 was bounced by Consistency Check IDBS Down Since then we replaced the other supervisor which we suspect might be bad, but we're trying to figure out if there is an actual REASON for that: Feb 3 15:46:59.276 EST: %PM-SP-4-PORT_BOUNCED: Port Fa3/41 was bounced by Consistency Check IDBS Down. error... We had to go in and shut/no shut interfaces 3/41 - 3/48 manually before the VLANs would come back up... We would like to avoid any more epilepsy from this box if possible, any ideas? thanks, -Drew _______________________________________________ cisco-nsp mailing list cisco-nsp