Pm-4-err_disable L2ptguard Error Detected On
Contents |
Help Follow Us Facebook Twitter Google + LinkedIn Newsletter Instagram YouTube DirectoryNetwork InfrastructureWAN, Routing and Switching LAN, Switching and Routing Network Management Remote Access Optical
Error Disabled Port Cisco Switch
Networking Getting Started with LANs IPv6 Integration and Transition EEM Scripting link-flap error detected Other Subjects SecurityVPN Security Management Firewalling Intrusion Prevention Systems/IDS AAA, Identity and NAC Physical Security
Pm 4 Err_disable Bpduguard Error Detected
MARS Email Security Web Security Other Subjects Service ProvidersMetro MPLS Voice Over IP XR OS and Platforms Video Other Subjects Collaboration, Voice and VideoIP Telephony Video gbic-invalid error detected 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 errdisable recovery 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 Infrastructure WAN, Routing and Switching LAN, Switching and Routing Network Management
Community features CCIE forums and discussions for all tracks including Routing & Switching, Voice, Security, Service Provider, Wireless,,
Channel-misconfig (stp) Error Detected
and Storage. Through these online communities you can discuss your questions errdisable detect cause with thousands of your peers, hundreds of CCIE's and INE's own team of world renowned CCIE instructors and
Errdisable Recovery Cause Psecure-violation
authors, Brian Dennis - Quintuple CCIE #2210, Brian McGahan – Triple CCIE #8593, Petr Lapukhov - Quad CCIE #16379, and Mark Snow - Dual CCIE #14073. Home CCIE Forums Forums https://supportforums.cisco.com/discussion/10736211/l2pt-guard » CCIE Forums » CCIE Routing & Switching Technical » QinQ Help: errdisable problem Latest post 01-25-2011 12:03 AM by enyatoti. 16 replies. Page 1 of 2 (17 items) 1 2Next > Sort Posts: Oldest to newest Newest to oldest Previous Next 05-06-2010 2:25 PM acruz Joined on 11-17-2009 Cruz Associate Points 795 QinQ Help: errdisable problem Reply Contact I'm http://ieoc.com/forums/p/11493/109523.aspx having a booger of a problem with etherchannel over do1q tunneling. The "metro" switches (2 & 3) keep going into errdisable on the "customer-facing" ports with the following error: %PM-4-ERR_DISABLE: l2ptguard error detected on Fa0/21, putting Fa0/21 in err-disable state. Anyone see anything wrong with my config: Post Points: 110 05-06-2010 2:33 PM In reply to ccienotes Joined on 09-25-2008 Bangalore India Associate Points 330 Re: QinQ Help: errdisable problem Reply Contact here is the explaination of it. L2pt guard When the Layer 2 PDUs enter the tunnel or access port on the inbound edge switch, the switch overwrites the customer PDU-destination MAC address with a well-known Cisco proprietary multicast address (01-00-0c-cd-cd-d0). If 802.1Q tunneling is enabled, packets are also double-tagged. The outer tag is the customer metro tag and the inner tag is the customer VLAN tag. The core switches ignore the inner tags and forward the packet to all trunk ports in the same metro VLAN. The edge switches on the outbound side restore the proper Layer 2 protocol and MAC address information and for
tunneling technology known as l2protocol-tunneling or L2pt here on the blog. If you missed that article, you may want to go through and get a handle on that technology before jumping into Q-Q tunneling. The two usually go hand in hand, but I cover http://www.astorinonetworks.com/2011/12/13/q-q-tunneling-for-fun-profit/ them separately to show that they are two independent technologies that just so happen to http://gponsolution.com/errdisable-reason-and-recovery.html go nicely together. Today, we will look at Q-Q tunneling and a bit later we will show how to integrate L2PT with your Q-Q tunnels. What is the point of Q-Q tunneling you might ask? It is mainly a SP technology used in metro ethernet that essentially transparently connects different customer sites that connect into the metro ethernet cloud by "tunneling" their error detected traffic through the service provider network. The cool thing about it is that the tunneling aspect of the technology allows the customer to send as many VLANs as they need to while also keeping their traffic pretty much isolated from the SP core. How It Works I usually like to start with a diagram of what things look like. This helps me visualize what is happening. Take a look at this, and don't worry if you pm-4-err_disable l2ptguard error don't get why certain VLANs are where, we will deal with that. Let's just go with the general concepts for now Here we have Cat1 at customer site A and Cat4 at customer site B. The customer has elected to connect these two sites together by means of a metro ethernet service provided by our little service provider here consisting of Cat2 and Cat3. OK, cool. The goal of the SP is to make Cat1 and Cat4 appear to be directly connected from their perspectives. The SP wants to be as transparent as possible, and they also require that they keep their traffic isolated and secured from the customer traffic. Well, how do we do that, and how do we keep the VLANs separated if the traffic from two different organizations needs to pass through the same set of devices. This is where Q-Q comes in. Q-Q works by double encapsulating ethernet frames with two 802.1Q tags, hence the name Q-Q (Q in Q). When you think about it, it works a lot like MPLS L3 VPN actually so if you are familiar with that topic, this may come easier for you. What happens is that the customer sends some traffic tagged with whatever VLAN it is they need. When the SP edge switch receives that traffic, it keeps that existing "inner" tag and adds a a second
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 problems or driver problems) A port duplex misconfiguration A por