<?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: Loopback bringing network down in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/loopback-bringing-network-down/m-p/1318908#M824409</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There is one drawback to using the old spanning tree and that is that the switches do not open the port until aprox 30 seconds, that can affect the dhcp process depending on how fast the computers are.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"old" spanning-tree&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/sw_ntman/cwsimain/cwsi2/cwsiug2/vlan2/stpapp.htm" target="_blank"&gt;http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/sw_ntman/cwsimain/cwsi2/cwsiug2/vlan2/stpapp.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rapid Spanning-tree&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/tech/tk389/tk621/technologies_white_paper09186a0080094cfa.shtml" target="_blank"&gt;http://www.cisco.com/en/US/tech/tk389/tk621/technologies_white_paper09186a0080094cfa.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 16 Nov 2009 10:34:23 GMT</pubDate>
    <dc:creator>hobbe</dc:creator>
    <dc:date>2009-11-16T10:34:23Z</dc:date>
    <item>
      <title>Loopback bringing network down</title>
      <link>https://community.cisco.com/t5/network-security/loopback-bringing-network-down/m-p/1318905#M824406</link>
      <description>&lt;P&gt;Hi, tricky one. We've just taken over management of a site and my responsibility is for their Pix. This customer has 2 other sites that connect via MPLS (looked after by BT) who's traffic is filtered by the pix. However, one of these sites has an issue whereby if one of the users plugs a network cable into 2 ports it slowly brings down the network and stops access to our site. Given that this site is a school and the users are students, this happens quite often.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Would I be right in thinking that any solution would need to be implemented on either the switch or router at the remote site? As I dont know must about routing protocols for switches or routers is there any advice I can give them given that I dont have any access to that site and is there anything I can implement on the firewall to help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks, Rex.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 16:40:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/loopback-bringing-network-down/m-p/1318905#M824406</guid>
      <dc:creator>Rex Biesty</dc:creator>
      <dc:date>2019-03-11T16:40:04Z</dc:date>
    </item>
    <item>
      <title>Re: Loopback bringing network down</title>
      <link>https://community.cisco.com/t5/network-security/loopback-bringing-network-down/m-p/1318906#M824407</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;My guess is that it is best solved with spanning tree in the switches.&lt;/P&gt;&lt;P&gt;If they have "new" cisco switches then try to enable rapid spanning tree (if all the switches support it) and set the ports to portfast (it works nice with rapid)&lt;/P&gt;&lt;P&gt;if the switches does not support rapid spanning tree, then use the "normal" spanning tree but do not set the ports to portfast (unless they are for a server)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Since it is a school there are probably some bright kids there so there are some nice features that there is a possibility to implement fx floodguard and bpdu guard features.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And no there is nothing you can do on your end. This is a local problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Nov 2009 10:16:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/loopback-bringing-network-down/m-p/1318906#M824407</guid>
      <dc:creator>hobbe</dc:creator>
      <dc:date>2009-11-16T10:16:21Z</dc:date>
    </item>
    <item>
      <title>Re: Loopback bringing network down</title>
      <link>https://community.cisco.com/t5/network-security/loopback-bringing-network-down/m-p/1318907#M824408</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks, just the answer I was looking for. I'll pass this info on to those that look after the switches at the remote site to sort.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Nov 2009 10:25:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/loopback-bringing-network-down/m-p/1318907#M824408</guid>
      <dc:creator>Rex Biesty</dc:creator>
      <dc:date>2009-11-16T10:25:35Z</dc:date>
    </item>
    <item>
      <title>Re: Loopback bringing network down</title>
      <link>https://community.cisco.com/t5/network-security/loopback-bringing-network-down/m-p/1318908#M824409</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There is one drawback to using the old spanning tree and that is that the switches do not open the port until aprox 30 seconds, that can affect the dhcp process depending on how fast the computers are.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"old" spanning-tree&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/sw_ntman/cwsimain/cwsi2/cwsiug2/vlan2/stpapp.htm" target="_blank"&gt;http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/sw_ntman/cwsimain/cwsi2/cwsiug2/vlan2/stpapp.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rapid Spanning-tree&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/tech/tk389/tk621/technologies_white_paper09186a0080094cfa.shtml" target="_blank"&gt;http://www.cisco.com/en/US/tech/tk389/tk621/technologies_white_paper09186a0080094cfa.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Nov 2009 10:34:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/loopback-bringing-network-down/m-p/1318908#M824409</guid>
      <dc:creator>hobbe</dc:creator>
      <dc:date>2009-11-16T10:34:23Z</dc:date>
    </item>
    <item>
      <title>Re: Loopback bringing network down</title>
      <link>https://community.cisco.com/t5/network-security/loopback-bringing-network-down/m-p/1318909#M824410</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks again.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Nov 2009 10:38:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/loopback-bringing-network-down/m-p/1318909#M824410</guid>
      <dc:creator>Rex Biesty</dc:creator>
      <dc:date>2009-11-16T10:38:12Z</dc:date>
    </item>
  </channel>
</rss>

