Cisco Diagnostics Error Detected
Contents |
Help Follow Us Facebook Twitter Google + LinkedIn Newsletter Instagram YouTube DirectoryNetwork InfrastructureWAN, Routing and Switching LAN, Switching and Routing Network Management Remote Access cisco link-flap error detected Optical Networking Getting Started with LANs IPv6 Integration and Transition cisco loopback error detected EEM Scripting Other Subjects SecurityVPN Security Management Firewalling Intrusion Prevention Systems/IDS AAA, Identity and NAC
Cisco Bpdu Guard Error Detected
Physical Security MARS Email Security Web Security Other Subjects Service ProvidersMetro MPLS Voice Over IP XR OS and Platforms Video Other Subjects Collaboration, Voice
Cisco 3850 Gbic-invalid Error Detected
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 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 Resources Security Alerts Security Alerts News News Video Cisco Support YouTube Cisco YouTube Blogs Technical Documentation Cisco Products Products Services Services Solutions Solutions Global Support Numbers Cisco Support Community Directory Network In
Cisco Bug: CSCsy20589 - Port diagnostic failures following 'redundancy reload shelf' command Last Modified Sep 29, 2015 Product Cisco Catalyst 6000 Series Switches Known Affected Releases 12.2(33)SXI Description (partial) Symptom: VSS running SXI. 1.- One or two of the VSL link ports goes to error disable due a diagnostic failure: %PM-SW1_SP-4-ERR_DISABLE: diagnostics error detected on Te1/5/5, putting Te1/5/5 in err-disable state %PM-SW2_SPSTBY-4-ERR_DISABLE: diagnostics error detected on Te1/5/5, putting Te1/5/5 in err-disable state 2.- TestVslStatus and TestLoopback fail. Conditions: 6500 VSS mode with SXI. It has been seen after reload https://supportforums.cisco.com/discussion/10990636/cisco-6509-port-errdisable the sw2 when is active, ex: Step 1: chassis 1 active command -> redundancy force-switchover Step 2: chassis 2 master command -> redundancy reload shelf 2 NAM module is in the chassis. View Bug Details in Bug Search Tool Why Is Login Required? Bug details contain sensitive information and therefore require a Cisco.com account to be viewed. Bug Details Include Full Description (including https://quickview.cloudapps.cisco.com/quickview/bug/CSCsy20589 symptoms, conditions and workarounds) Status Severity Known Fixed Releases Related Community Discussions Number of Related Support Cases Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract. Learn More About Cisco Service Contracts Information For Small Business Midsize Business Service Provider Executives Industries Automotive Consumer Packaged Goods Education Energy Financial Services Government Healthcare Hospitality Life Sciences Manufacturing Materials and Mining Public Sector Retail Smart+Connected Communities Sports and Entertainment Transportation Workspace Transformation Marketplace Contacts Contact Cisco Meet our Partners Find a Reseller News & Alerts Newsroom Blogs Field Notices Security Advisories Technology Trends Cloud Internet of Things (IoT) Software Defined Networking (SDN) Support Downloads Documentation Communities DevNet Learning Network Support Community Video Portal Certifications Events Industries Inside Cisco Products Service Provider Services Technology Trends TechWiseTV About Cisco Investor Relations Corporate Social Responsibility Environmental Sustainability Trust and Transparency Center The Next Wave of The Internet Our People Careers Search Jobs Life at Cisco Programs Cisco Designated VIP Program Cisco Powered Financing Options Contacts Feedback Help Site Map Terms & Conditions PrivacyPrivacy Statement Cook
team • Delete all board cookies • All times are UTC - 8 hours Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group Advertisements by Advertisement Management
Windows Server Linux Server Forum Youtube Channel About Me Errdisable reason and recovery procedure February 13, 2011 CISCO, Switch No comments Errdisable reason and recovery procedure: This document defines the errdisabled reason & describes how to recover from it, and provides examples of errdisable recovery. Note: The port status of err-disabled displays in the output of the show interfaces interface_number status command. Function of Errdisable: When a switch port is error disabled state, it is effectively shut down and no traffic is sent or received on that port. The port LED is set to the color orange and, when you issue the show interfaces command, the port status shows err-disabled. bellow is an example of error-disabled port status looks like from the command-line interface (CLI) of the switch: SW1#show interfaces fastEthernet 0/1 status Port Name Status Vlan Duplex Speed Type Fa0/1 err-disabled 100 full 1000 1000BaseSX Or, if the interface has been disabled because of an error condition, you can see messages that are similar to these in both the console and the syslog: %SPANTREE-SP-2-BLOCK_BPDUGUARD: Received BPDU on port fastEthernet0/1 with BPDU Guard enabled. Disabling port. %PM-SP-4-ERR_DISABLE: bpduguard error detected on Fi0/1, putting Fi0/1 in err-disable state This message show when a host port receives the (BPDU) bridge protocol data unit. The actual message depends on the reason for the error condition. Errdisable reason: This feature was first implemented to handle special collision situations in which the switch detected excessive or late collisions on a port. Excessive collisions occur when a frame is dropped because the switch encounters 16 collisions in a row. Late collisions occur after every device on the wire should have recognized that the wire was in use. Possible causes of these types of errors include: A cable that is out of specification (either too long, the wrong type, or defective) A bad network interface card (NIC) card (with physical pr