<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: How does a loop form in a misconfigured Etherchannel? in Switching</title>
    <link>https://community.cisco.com/t5/switching/how-does-a-loop-form-in-a-misconfigured-etherchannel/m-p/1577676#M158336</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Edison, Jon and everybody,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think I've got it. Please bear with me while I explain my thoughts.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As we have discussed here, a pure Etherchannel between just two switches, with one switch being configured for Etherchannel and the other not, may result in frames being &lt;STRONG&gt;reflected (bounced)&lt;/STRONG&gt; back but not in frames going around in circles. A frame received on a member port of an Etherchannel bundle will not be forwarded back through any member port of the same bundle, thus, the loop cannot be formed that way. I have tested this in our lab - I have connected two switches together with two links, one switch was configured for Etherchannel, the other not. No broadcast storm occured as the result although I have intentionally flooded the topology with broadcast traffic (a videostream sent to a broadcast IP address). As soon as I stopped transmitting the stream, the topology remained silent - no frames got caught in a loop, and no network collapse ensued whatsoever.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What I realized is that the loop must be formed by an additional redundant link in the topology that somehow - when combined with a misconfigured Etherchannel - results in multiple paths between switches, thus forming a loop. The networks we have seen to collapse under Etherchannel misconfiguration were always more redundant than just a single Etherchannel between switches. I began to suspect that there must be additional redundancy present in the network so that the loop can be formed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have therefore analyzed the simplest scenario fulfilling this requirement - adding a third standalone link between the two switches. To better visualize the concept, please have a look at the exhibit Example1.png I have attached. There are two switches - the Distribution Switch (DS) and the Access Switch (AS). The standalone link is the Fa0/1. Furthermore, DS has ports Fa0/2-3 bundled in an Etherchannel while AS has no Etherchannel configured. The DS is configured as STP Root. What will now happen?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Because DS is STP Root, all its ports (Fa0/1 and Po1) are Designated Forwarding&lt;/LI&gt;&lt;LI&gt;AS will receive BPDUs via Fa0/1 and via &lt;STRONG&gt;exactly one&lt;/STRONG&gt; of the links of the Etherchannel from DS. Let's assume that the link is Fa0/2&lt;BR /&gt;&lt;/LI&gt;&lt;LI&gt;AS will declare Fa0/1 to be its Root port (the lowest sender port ID) and Fa0/2 as Alternate Discarding.&lt;/LI&gt;&lt;LI&gt;However, AS receives no BPDUs on Fa0/3. Therefore, it declares the Fa0/3 as Designated Forwarding.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And voila! - we have a loop here - two links completely unblocked and forwarding: Fa0/1 and Fa0/3. A single broadcast now starts the usual broadcast storm that I've have striving for so long! &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And then it all suddenly began making sense. The true loop with frames endlessly circulating is not actually created by the presence of the misconfigured Etherchannel itself but rather &lt;STRONG&gt;by the modified operation of STP over an Etherchannel bundle - that the BPDUs for a particular VLAN are sent through a single link in the entire bundle&lt;/STRONG&gt;. All other bundled ports that do not carry BPDUs can be mistakenly considered as eligible for Designated Forwarding by the switch with a missing/misconfigured Etherchannel, and that forms the basis of the actual loops.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have subsequently analyzed a rather common scenario with two distribution layer switches and an access switch connected to both distribution switches. Please see first the Example2.png. The DS1 is configured as STP Root, the DS2 is configured as STP Secondary Root. In this exhibit, the AS has the ports Fa0/1-2 unconfigured by mistake (or not yet). Assuming that the bundle on AS towards DS2 becomes the root port (Etherchannel has a lower cost than individual links so with enough links in an Etherchannel of an appropriate speed, this may happen by default), one of the ports Fa0/1-2 on AS becomes Alternate Discarding (because it receives BPDUs from DS1) and the other becomes Designated Forwarding as it receives no BPDUs. A loop is thus formed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The Example3.png depicts another common scenario with ports Fa0/5-6 unbundled on AS. DS1 is again STP Root, DS2 is STP Secondary Root. Here, the bundle on AS towards DS1 will be declared Root port, and because the DS2 has a lower BID than AS (it is Secondary Root), its bundle towards AS will be declared as Designated Forwarding. Again, AS will declare one of the ports Fa0/5-6 as Alternate Discarding and the other as Designated Forwarding, and here we have the loop again.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I assume this is actually what brought down the networks with misconfigured Etherchannels.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have experimentally tested all three scenarios in our lab and I have been able to easily create the broadcast storm in each of these cases. Furthermore, &lt;STRONG&gt;I have not deactivated the STP Etherchannel Misconfig Guard&lt;/STRONG&gt;. Even with this guard left active, there was absolutely no problem in creating these loops as described earlier. The reason is that this guard basically reacts to arrival of BPDUs sent from differing MAC addresses on ports bundled in an Etherchannel which is not expected in correct configuration. However, in my particular topology, each bundle consisted of two links. Whenever AS declared one of these links as Alternate Discarding and the second as Designated Forwarding, the Etherchannel received BPDUs only via the Forwarding link and so the EC Misconfig Guard had no reason to kick in. It would be probably different if my bundles consisted of at least 3 links but for two-link bundles, this guard is helpless (which is logical - it performs only local decisions and so has very limited information).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Phew &lt;SPAN __jive_emoticon_name="wink" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/images/emoticons/wink.gif"&gt;&lt;/SPAN&gt; I would like to thank ANYONE that has joined this thread so far and helped me to finally resolve this mystery!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Peter&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 06 Dec 2010 18:37:18 GMT</pubDate>
    <dc:creator>Peter Paluch</dc:creator>
    <dc:date>2010-12-06T18:37:18Z</dc:date>
    <item>
      <title>How does a loop form in a misconfigured Etherchannel?</title>
      <link>https://community.cisco.com/t5/switching/how-does-a-loop-form-in-a-misconfigured-etherchannel/m-p/1577645#M158305</link>
      <description>&lt;P&gt;Dear friends,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It is a commonly seen and practically proven issue that if two switches are interconnected by a number of parallel links which are bundled into an Etherchannel on one switch (obviously using the &lt;STRONG&gt;on&lt;/STRONG&gt; mode) while being unbundled on the second switch, a Layer2 loop may well be created. However, I do not understand the exact mechanism of the formation of this loop.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am well aware of the basic principles behind: I know that STP treats the Port-channel interface as a single interface, and thus all member links bundled in this Etherchannel share the same STP state/role. I also understand that a broadcast/multicast/unknown unicast frame sent by a port in the Etherchannel will reach the opposite switch and get flooded over all remaining links, eventually arriving back at the switch with the configured Etherchannel.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And this precise moment is where my understanding ends: The frame arrived back and its destination is still unknown. However, from the viewpoint of the switch, the frame came in through a particular Port-channel interface. If this switch floods the frame, it will flood it through all remaining ports except the port through which the frame came in, meaning that the frame will never be sent back through the Port-channel. How does the loop get created, then?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you very much for helping me out with this!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Peter&lt;/P&gt;</description>
      <pubDate>Wed, 06 Mar 2019 22:21:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/how-does-a-loop-form-in-a-misconfigured-etherchannel/m-p/1577645#M158305</guid>
      <dc:creator>Peter Paluch</dc:creator>
      <dc:date>2019-03-06T22:21:29Z</dc:date>
    </item>
    <item>
      <title>Re: How does a loop form in a misconfigured Etherchannel?</title>
      <link>https://community.cisco.com/t5/switching/how-does-a-loop-form-in-a-misconfigured-etherchannel/m-p/1577646#M158306</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Peter,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Packets will be flooded out of all interfaces for unknown broadcast/unicast packets with the exception of the interface where the flood came from.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In a 2 switch topology, Switch A (which has the bundle) will flood the packet out of the members of the bundle expecting Switch B to receive the packet on its bundle.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However Switch B will only receive the packet on one of its physical interfaces and can potentially flood back to Switch B out of its other connected physical interface causing the STP loop.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edison.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 05 Dec 2010 12:40:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/how-does-a-loop-form-in-a-misconfigured-etherchannel/m-p/1577646#M158306</guid>
      <dc:creator>Edison Ortiz</dc:creator>
      <dc:date>2010-12-05T12:40:34Z</dc:date>
    </item>
    <item>
      <title>Re: How does a loop form in a misconfigured Etherchannel?</title>
      <link>https://community.cisco.com/t5/switching/how-does-a-loop-form-in-a-misconfigured-etherchannel/m-p/1577647#M158307</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Peter&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;And this precise moment is where my understanding ends: The frame arrived back and its destination is still unknown. However, from the viewpoint of the switch, the frame came in through a particular Port-channel interface. If this switch floods the frame, it will flood it through all remaining ports except the port through which the frame came in, meaning that the frame will never be sent back through the Port-channel. How does the loop get created, then?&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My undestanding is -&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sw1 = switch with etherchannel&amp;nbsp;&amp;nbsp; gi0/1 - 4&lt;/P&gt;&lt;P&gt;sw2 = switch without etherchannel gi0/1 - 4 not etherchanneled&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sw1 selects a port in the etherchannel and transmits the broadcast eg gi0/2.&amp;nbsp; It arrives at sw2 as you say and because the there is no etherchannel configured sw2 floods the broadcast on ports gi0/1, 3 &amp;amp; 4 but not 2 because it received it on that port.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sw1 receives the packet back on gi0/1, 3 &amp;amp; 4 but not gi0/2. So sw1 then refloods the packet on gi0/2 back to sw2 and the whole process starts over again.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 05 Dec 2010 12:43:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/how-does-a-loop-form-in-a-misconfigured-etherchannel/m-p/1577647#M158307</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2010-12-05T12:43:21Z</dc:date>
    </item>
    <item>
      <title>Re: How does a loop form in a misconfigured Etherchannel?</title>
      <link>https://community.cisco.com/t5/switching/how-does-a-loop-form-in-a-misconfigured-etherchannel/m-p/1577648#M158308</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Edison,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks so much for your reply.&lt;/P&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;&lt;P&gt;In a 2 switch topology, Switch A (which has the bundle) will flood 
the packet out of the members of the bundle expecting Switch B to 
receive the packet on its bundle.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However
 Switch B will only receive the packet on one of its physical interfaces
 and can potentially flood back to Switch B out of its other connected 
physical interface causing the STP loop.&lt;/P&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Exactly! And this is precisely what I wrote in my first post. But my doubts go further, and I will repost them here for clarity:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The frame arrived back to the switch A that has the bundle configured and the frame's destination is still unknown. However,&amp;nbsp; from the viewpoint of the switch, the frame came in through a particular&amp;nbsp; &lt;STRONG&gt;Port-channel&lt;/STRONG&gt; interface. If this switch floods the frame, it will flood&amp;nbsp; it through all remaining ports except the port through which the frame&amp;nbsp; came in, meaning that the frame will never be sent back through the&amp;nbsp; Port-channel.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is this assumption correct?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Peter&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 05 Dec 2010 12:46:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/how-does-a-loop-form-in-a-misconfigured-etherchannel/m-p/1577648#M158308</guid>
      <dc:creator>Peter Paluch</dc:creator>
      <dc:date>2010-12-05T12:46:26Z</dc:date>
    </item>
    <item>
      <title>Re: How does a loop form in a misconfigured Etherchannel?</title>
      <link>https://community.cisco.com/t5/switching/how-does-a-loop-form-in-a-misconfigured-etherchannel/m-p/1577649#M158309</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;&lt;P&gt;ediortiz wrote:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Peter,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Packets will be flooded out of all interfaces for unknown broadcast/unicast packets with the exception of the interface where the flood came from.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In a 2 switch topology, Switch A (which has the bundle) will flood the packet out of the members of the bundle expecting Switch B to receive the packet on its bundle.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However Switch B will only receive the packet on one of its physical interfaces and can potentially flood back to Switch B out of its other connected physical interface causing the STP loop.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edison.&lt;/P&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edison&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Okay, i'm confused now.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does etherchannel send a broadcast across all of it links or just pick one of them ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You also say when switch A floods the broadcast out of all the members of the bundle, switch B will only receive it one interface. Not understanding this as they are still physical connections so if A sends on all links B will receive on all links ? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could you explain a bit more ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 05 Dec 2010 12:46:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/how-does-a-loop-form-in-a-misconfigured-etherchannel/m-p/1577649#M158309</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2010-12-05T12:46:37Z</dc:date>
    </item>
    <item>
      <title>Re: How does a loop form in a misconfigured Etherchannel?</title>
      <link>https://community.cisco.com/t5/switching/how-does-a-loop-form-in-a-misconfigured-etherchannel/m-p/1577650#M158310</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jon,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you very much for joining this thread!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;&lt;P&gt;sw1 receives the packet back on gi0/1, 3 &amp;amp; 4 but not gi0/2. So sw1 
then refloods the packet on gi0/2 back to sw2 and the whole process 
starts over again.&lt;/P&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Right, the sw1 will receive the frame back on Gi0/1, Gi0/3 and Gi0/4. But for the sw1, all these ports are just members of the Port-channel interface. A frame arriving through any of the member links is treated as arriving through the Port-channel itself.&amp;nbsp; Even the MAC addresses are learned on Port-channel interfaces, not on physical member ports. Therefore, when sw1 forwards the frame, it - by an elementary switch logic - cannot forward it back through the original ingress interface &lt;STRONG&gt;which is Port-channel&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And this is my trouble here.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Peter&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 05 Dec 2010 12:53:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/how-does-a-loop-form-in-a-misconfigured-etherchannel/m-p/1577650#M158310</guid>
      <dc:creator>Peter Paluch</dc:creator>
      <dc:date>2010-12-05T12:53:01Z</dc:date>
    </item>
    <item>
      <title>Re: How does a loop form in a misconfigured Etherchannel?</title>
      <link>https://community.cisco.com/t5/switching/how-does-a-loop-form-in-a-misconfigured-etherchannel/m-p/1577651#M158311</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Jon,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Your explanation and mine are the same - I don't understand how you can be confused.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The EC will hash out of one link but the logical link will be treated as one for the STP loop so it will eliminate this interface as a candidate for the egress flood.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*** Edited for Clarification&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 05 Dec 2010 12:53:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/how-does-a-loop-form-in-a-misconfigured-etherchannel/m-p/1577651#M158311</guid>
      <dc:creator>Edison Ortiz</dc:creator>
      <dc:date>2010-12-05T12:53:21Z</dc:date>
    </item>
    <item>
      <title>Re: How does a loop form in a misconfigured Etherchannel?</title>
      <link>https://community.cisco.com/t5/switching/how-does-a-loop-form-in-a-misconfigured-etherchannel/m-p/1577652#M158312</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;EM&gt;I don't understand how you can be confused.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ohh, that can happen all too easily &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;No problem, must be the way i was reading it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 05 Dec 2010 12:58:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/how-does-a-loop-form-in-a-misconfigured-etherchannel/m-p/1577652#M158312</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2010-12-05T12:58:09Z</dc:date>
    </item>
    <item>
      <title>Re: How does a loop form in a misconfigured Etherchannel?</title>
      <link>https://community.cisco.com/t5/switching/how-does-a-loop-form-in-a-misconfigured-etherchannel/m-p/1577653#M158313</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You are correct but the frame that was sent originally came back via the same interface - in essence that's a loop.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As you stated, it won't send the frame back out but take into account a network with tons of unknown of multicast/broadcast traffic.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 05 Dec 2010 13:05:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/how-does-a-loop-form-in-a-misconfigured-etherchannel/m-p/1577653#M158313</guid>
      <dc:creator>Edison Ortiz</dc:creator>
      <dc:date>2010-12-05T13:05:53Z</dc:date>
    </item>
    <item>
      <title>Re: How does a loop form in a misconfigured Etherchannel?</title>
      <link>https://community.cisco.com/t5/switching/how-does-a-loop-form-in-a-misconfigured-etherchannel/m-p/1577654#M158314</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 05 Dec 2010 13:06:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/how-does-a-loop-form-in-a-misconfigured-etherchannel/m-p/1577654#M158314</guid>
      <dc:creator>Edison Ortiz</dc:creator>
      <dc:date>2010-12-05T13:06:14Z</dc:date>
    </item>
    <item>
      <title>Re: How does a loop form in a misconfigured Etherchannel?</title>
      <link>https://community.cisco.com/t5/switching/how-does-a-loop-form-in-a-misconfigured-etherchannel/m-p/1577655#M158315</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Edison,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;You are correct but the frame that was sent originally came back via the same interface - in essence that's a loop.&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Certainly, I agree with this. But this kind of loop does not result in the same broadcast frame to loop forever. Yet, we have seen the network being brought to its knees by misconfigured Etherchannels. A broadcast frame hitting a switch twice and being dropped afterwards, pardon me... I don't believe it can cause such a massive outage.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So what happens in such instances?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Peter&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 05 Dec 2010 13:18:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/how-does-a-loop-form-in-a-misconfigured-etherchannel/m-p/1577655#M158315</guid>
      <dc:creator>Peter Paluch</dc:creator>
      <dc:date>2010-12-05T13:18:39Z</dc:date>
    </item>
    <item>
      <title>Re: How does a loop form in a misconfigured Etherchannel?</title>
      <link>https://community.cisco.com/t5/switching/how-does-a-loop-form-in-a-misconfigured-etherchannel/m-p/1577656#M158316</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Peter&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Etherchannel can be configured to learn addresses in 2 ways -&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) aggregate port learning ie. the mac-addresses are associated with the port-channel interface&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2) physical port learning - speaks for itself really&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the switch was using physical port learning then there could indeed be a loop created by the method Edison and I described as far as i can see.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, having said that,i noticed your recent post (yesterday) on the etherchannel broadcast storm and after checking the config guides for both 2960 and 3750 switches it states that physical port learning is not supported on those switches so it doesn't answer the previous posts issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 05 Dec 2010 13:28:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/how-does-a-loop-form-in-a-misconfigured-etherchannel/m-p/1577656#M158316</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2010-12-05T13:28:34Z</dc:date>
    </item>
    <item>
      <title>Re: How does a loop form in a misconfigured Etherchannel?</title>
      <link>https://community.cisco.com/t5/switching/how-does-a-loop-form-in-a-misconfigured-etherchannel/m-p/1577657#M158317</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Peter,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Packet duplication in a large network can certainly put any switch on its knees. The cases may be different on each EC misconfiguration. It depends on the network state. I've seen networks with EC misconfiguration running for a while until heavy traffic traverses those links.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Say you deploy multicast on that segment after those switches have been misconfigured for a while and hell break loose. You would attribute the problem with the multicast deployment while the culprit was a bad design to begin with.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 05 Dec 2010 13:57:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/how-does-a-loop-form-in-a-misconfigured-etherchannel/m-p/1577657#M158317</guid>
      <dc:creator>Edison Ortiz</dc:creator>
      <dc:date>2010-12-05T13:57:12Z</dc:date>
    </item>
    <item>
      <title>Re: How does a loop form in a misconfigured Etherchannel?</title>
      <link>https://community.cisco.com/t5/switching/how-does-a-loop-form-in-a-misconfigured-etherchannel/m-p/1577658#M158318</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jon,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your insights. Correct, I have almost forgotten about the physical learning method for Etherchannels. But even if taking that into account, I still do not believe that it could cause frames to be caught in a loop. Let me explain.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We all agree that a frame can be returned back to switch A (with the Etherchannel) if the neighboring switch B does not have the Etherchannel configured. No doubt about that. Jon, now, your supposition is that because the unknown frame is forwarded back to switch A through almost all member links of the bundle, the switch A will somehow re-flood the frame back to switch B. Is that correct?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note that this situation is not specific only for Etherchannel misconfiguration. The switch B can have the Etherchannel configured just fine but it suddenly receives a burst of frames with different destination MACs, all unknown, or its load-balancing mechanism may react to something different that just the source/destination MAC combination. From the switch A viewpoint, the situation is no different, and yet, no looping ensues - even with physical address learning, otherwise the Etherchannel would be unusable per se.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Peter&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 05 Dec 2010 14:03:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/how-does-a-loop-form-in-a-misconfigured-etherchannel/m-p/1577658#M158318</guid>
      <dc:creator>Peter Paluch</dc:creator>
      <dc:date>2010-12-05T14:03:13Z</dc:date>
    </item>
    <item>
      <title>Re: How does a loop form in a misconfigured Etherchannel?</title>
      <link>https://community.cisco.com/t5/switching/how-does-a-loop-form-in-a-misconfigured-etherchannel/m-p/1577659#M158319</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Peter&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;A viewpoint, the situation is no different, and yet, no looping ensues - even with physical address learning, otherwise the Etherchannel would be unusable per se.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That's a good point, it would be no different than an etherchannel receiving an unknown unicast or broadcast for that matter from a fully functioning etherchanel at the other end.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 05 Dec 2010 14:09:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/how-does-a-loop-form-in-a-misconfigured-etherchannel/m-p/1577659#M158319</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2010-12-05T14:09:38Z</dc:date>
    </item>
    <item>
      <title>Re: How does a loop form in a misconfigured Etherchannel?</title>
      <link>https://community.cisco.com/t5/switching/how-does-a-loop-form-in-a-misconfigured-etherchannel/m-p/1577660#M158320</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Edison,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I get the point. I am now moving on a thin ice as I am talking about something I &lt;STRONG&gt;believe to have seen in the past&lt;/STRONG&gt; but I am not entirely sure: with a misconfigured Etherchannel, an obvious storm ensued, with the switches indicating heavy traffic on all their LEDs (blinking wildly). That would mean the frames received by a Port-channel interface were reflooded back which is actually the reason behind this entire thread. Have you had a similar experience?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Peter&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 05 Dec 2010 14:09:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/how-does-a-loop-form-in-a-misconfigured-etherchannel/m-p/1577660#M158320</guid>
      <dc:creator>Peter Paluch</dc:creator>
      <dc:date>2010-12-05T14:09:42Z</dc:date>
    </item>
    <item>
      <title>Re: How does a loop form in a misconfigured Etherchannel?</title>
      <link>https://community.cisco.com/t5/switching/how-does-a-loop-form-in-a-misconfigured-etherchannel/m-p/1577661#M158321</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Edison,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Still one more comment, though:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;Packet duplication in a large network can certainly put any switch on its knees.&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Agree. But the switch having the Etherchannel configured should actually not be bothered so much with the traffic "reflected" back from the opposite unconfigured switch - it would merely drop it which is performed in the hardware as one of the basic switching functions. Even the unconfigured switch should not be loaded in a significantly higher way - it is in the same position as a switch receiving a broadcast/multicast traffic on a port and replicating the flow on remaining ports. Neither of these switch is actually going to &lt;STRONG&gt;process and forward&lt;/STRONG&gt; any such frame twice.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Peter&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 05 Dec 2010 14:23:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/how-does-a-loop-form-in-a-misconfigured-etherchannel/m-p/1577661#M158321</guid>
      <dc:creator>Peter Paluch</dc:creator>
      <dc:date>2010-12-05T14:23:27Z</dc:date>
    </item>
    <item>
      <title>Re: How does a loop form in a misconfigured Etherchannel?</title>
      <link>https://community.cisco.com/t5/switching/how-does-a-loop-form-in-a-misconfigured-etherchannel/m-p/1577662#M158322</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Peter,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I haven't seen the case where packets are being flooded back via the EC - if that was your intended question. However,&amp;nbsp; I wouldn't discard this scenario which can be attributed to a software defect along with poor design implementation.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 05 Dec 2010 14:33:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/how-does-a-loop-form-in-a-misconfigured-etherchannel/m-p/1577662#M158322</guid>
      <dc:creator>Edison Ortiz</dc:creator>
      <dc:date>2010-12-05T14:33:30Z</dc:date>
    </item>
    <item>
      <title>Re: How does a loop form in a misconfigured Etherchannel?</title>
      <link>https://community.cisco.com/t5/switching/how-does-a-loop-form-in-a-misconfigured-etherchannel/m-p/1577663#M158323</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We need to take into account where the STP Root may be located as well.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 05 Dec 2010 14:34:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/how-does-a-loop-form-in-a-misconfigured-etherchannel/m-p/1577663#M158323</guid>
      <dc:creator>Edison Ortiz</dc:creator>
      <dc:date>2010-12-05T14:34:15Z</dc:date>
    </item>
    <item>
      <title>Re: How does a loop form in a misconfigured Etherchannel?</title>
      <link>https://community.cisco.com/t5/switching/how-does-a-loop-form-in-a-misconfigured-etherchannel/m-p/1577664#M158324</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Do either of you guys know what would happen if a switch received a packet on a port-channel interface and the destination mac was pointing back out the same po1 interface eg.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;po1 = gi0/1&amp;nbsp; - 4&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;switch receives packet with dst mac aa.bb on gi0/2 and has recorded in it's cam table that aa.bb is reachable via po1 ? Would it simply select one of it'sl links and send the packet back out ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 05 Dec 2010 15:01:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/how-does-a-loop-form-in-a-misconfigured-etherchannel/m-p/1577664#M158324</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2010-12-05T15:01:04Z</dc:date>
    </item>
  </channel>
</rss>

