<?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: Loop-detection with Delta equipement (furnace) shutdown port when power outage. in ICX Switches</title>
    <link>https://community.ruckuswireless.com/t5/ICX-Switches/Loop-detection-with-Delta-equipement-furnace-shutdown-port-when/m-p/32099#M1854</link>
    <description>Hello,&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;the equipment have only one network connector plug and he's plugged directly in a ICX7250.&amp;nbsp; The ICX7250 is plug in a router ICX6610.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;We made many others tests.&amp;nbsp; On a ICX6450, the loop-detection dont shutdown the port with the same equipment.&amp;nbsp; It seem to happends only with ICX7250.&amp;nbsp; I tried many software version 08030, 08070 and 08090.&amp;nbsp; No difference.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Finaly I think I will put a shutdown disable for that device.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;bye</description>
    <pubDate>Tue, 03 Mar 2020 19:15:27 GMT</pubDate>
    <dc:creator>ala_ma</dc:creator>
    <dc:date>2020-03-03T19:15:27Z</dc:date>
    <item>
      <title>Loop-detection with Delta equipement (furnace) shutdown port when power outage.</title>
      <link>https://community.ruckuswireless.com/t5/ICX-Switches/Loop-detection-with-Delta-equipement-furnace-shutdown-port-when/m-p/32097#M1852</link>
      <description>We have a network with ICX7250 switches and loop-detection activated on ports.&amp;nbsp; On some Delta equipments (for furnace control), when it have a power outage, the switch detect a loop and shutdown the port.&amp;nbsp; The port come down when the power is lost, not when it come back.&amp;nbsp; If we make a debug, we can see the loop detection packet come back on the switch.&amp;nbsp; The equipment continu to make some packet transfert before shuthing down.&amp;nbsp; If we remove the loop detection protection, the loop goes on the router and make many next hop router errors.&amp;nbsp; Even if we change that equipement it's the same problem.&amp;nbsp; For us, it's clear that the problem come from the design of this equipment.&amp;nbsp; Is there any way to disable loop detection and configure the router to prevent problem coming from that equipment?&lt;BR /&gt;Thank you</description>
      <pubDate>Thu, 27 Feb 2020 16:28:30 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ICX-Switches/Loop-detection-with-Delta-equipement-furnace-shutdown-port-when/m-p/32097#M1852</guid>
      <dc:creator>ala_ma</dc:creator>
      <dc:date>2020-02-27T16:28:30Z</dc:date>
    </item>
    <item>
      <title>Re: Loop-detection with Delta equipement (furnace) shutdown port when power outage.</title>
      <link>https://community.ruckuswireless.com/t5/ICX-Switches/Loop-detection-with-Delta-equipement-furnace-shutdown-port-when/m-p/32098#M1853</link>
      <description>Good Morning:&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;If the connected interface is going into an error-disabled state due to loop-detection during a power-outage, most likely some other piece of equipment is behaving strangely reflecting the loop-detection frames (PDU for Layer-2 where "Packet" is the PDU for Layer-3) are being reflected back at the ICX unit.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Specifically, the way loop-detection works is that the same switch that generates the loop-detection will recognize it should it come back into another Interface.&amp;nbsp; This normally happens when there is a loop in the network topology.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Usually when you see a route change notification in the logging, it is because the ARP table reflects the next-hop IP available via a MAC address that is reachable via a different interface.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Does the device you are reaching go through something else and have two (2) connections to your Rucks ICX devie?&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;You will need to explain more about your network topology to get better support.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;I can assure you the loop-detection works extremely well in every implementation we have tried.&amp;nbsp; Its only downside we have found is if you have multiple units they pass it through transparently...&amp;nbsp; i.e. you run loop-detection on a VLAN, if that VLAN crosses a trunk (i.e. a link between switches carrying multiple VLANs) that if someone loops something (i.e. connecting an Avaya VoIP phone on two interfaces that go to different closets or switches), the loop-detection frame will get picked up and passed through the other devices which do not recognize it as theirs, and it gets back to the switch that made the loop-detection frame only on a trunk or fiber link.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;All that said, what about just not making loops?&amp;nbsp; or using spanning-tree, which is excellent at mitigating loops?&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;</description>
      <pubDate>Fri, 28 Feb 2020 14:14:38 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ICX-Switches/Loop-detection-with-Delta-equipement-furnace-shutdown-port-when/m-p/32098#M1853</guid>
      <dc:creator>netwizz</dc:creator>
      <dc:date>2020-02-28T14:14:38Z</dc:date>
    </item>
    <item>
      <title>Re: Loop-detection with Delta equipement (furnace) shutdown port when power outage.</title>
      <link>https://community.ruckuswireless.com/t5/ICX-Switches/Loop-detection-with-Delta-equipement-furnace-shutdown-port-when/m-p/32099#M1854</link>
      <description>Hello,&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;the equipment have only one network connector plug and he's plugged directly in a ICX7250.&amp;nbsp; The ICX7250 is plug in a router ICX6610.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;We made many others tests.&amp;nbsp; On a ICX6450, the loop-detection dont shutdown the port with the same equipment.&amp;nbsp; It seem to happends only with ICX7250.&amp;nbsp; I tried many software version 08030, 08070 and 08090.&amp;nbsp; No difference.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Finaly I think I will put a shutdown disable for that device.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;bye</description>
      <pubDate>Tue, 03 Mar 2020 19:15:27 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ICX-Switches/Loop-detection-with-Delta-equipement-furnace-shutdown-port-when/m-p/32099#M1854</guid>
      <dc:creator>ala_ma</dc:creator>
      <dc:date>2020-03-03T19:15:27Z</dc:date>
    </item>
  </channel>
</rss>

