Oh, loop on the same circuit...

I get it now.  

From: Faisal Imtiaz 
Sent: Tuesday, October 25, 2016 2:23 PM
To: [email protected] 
Subject: Re: [AFMUG] stp

The obvious benefit of using STP (or any  flavor of it) is that it protects the 
layer2 network from loops.
    What is a loop... see a cat or dog video of it chasing it's own tail.. now 
watch it non-stop !

The short coming of having STP (or any flavor of it)  ON on a port that is 
connecting to someone else's network device is...
    they can create a Loop and thus signal the upstream devices to block the 
port... obviously this is a bad thing.

The fun part of STP (sarcastically speaking) is that for most devices it does 
not report to the system logs, and one has to issue a separate command to see 
what is the status.
But the stuff that can catch a service provider off guard, from the left field 
is that.... some devices e.g. Cisco's, will listen and react to STP packets 
from other connected networks, leaving one with a 'wtf look' pulling one's hair 
out.....
Sometimes such conditions can also be created is the upstream puts a loop-back 
on the port for testing (fiber connections).

I have a say that recently I saw strange STP behavior between a MT (CCR) and 
Netonix switch, where a STP loop was detected, while the configuration clearly 
suggest that there should not have been a loop.

It's like the sharp blunt nose electrician scissors, they are awesome at 
clipping wires, clipping tie wraps, blunt nose is good... but it is also very 
easy to cut your hand with them if you don't use them properly....

:)  


Faisal Imtiaz
Snappy Internet & Telecom
7266 SW 48 Street
Miami, FL 33155
Tel: 305 663 5518 x 232

Help-desk: (305)663-5518 Option 2 or Email: [email protected]


--------------------------------------------------------------------------------

  From: "George Skorup" <[email protected]>
  To: [email protected]
  Sent: Tuesday, October 25, 2016 4:06:11 PM
  Subject: Re: [AFMUG] stp

  Lots of switch vendors and even MikroTik (in the 6.37 branch, IIRC) support 
loop protection. If all you care about is stopping a loop, then use that. Use 
STP if you need its functionality.


  On 10/25/2016 1:16 PM, Josh Reynolds wrote:

    If one of the ports has a loop, it will block only that port. Obviously, 
disable STP on uplinks.


    On Oct 25, 2016 1:08 PM, "Chuck McCown" <[email protected]> wrote:

      But if you only have one upstream connection and you fall, it isn’t going 
to do anything, right?

      From: Josh Reynolds
      Sent: Tuesday, October 25, 2016 12:01 PM
      To: [email protected]
      Subject: Re: [AFMUG] stp

      STP is a safety net. Its not doing much unless you fall.


      On Oct 25, 2016 12:44 PM, "Chuck McCown" <[email protected]> wrote:

        How can STP being enabled help anything if you are not using it?

        From: Josh Luthman
        Sent: Tuesday, October 25, 2016 10:10 AM
        To: [email protected]
        Subject: Re: [AFMUG] stp

        I just learned the other day thanks to Steve the Mikrotik software 
bridges are (R?) STP by default.


        Josh Luthman
        Office: 937-552-2340
        Direct: 937-552-2343
        1100 Wayne St
        Suite 1337
        Troy, OH 45373

        On Tue, Oct 25, 2016 at 12:07 PM, Bill Prince <[email protected]> 
wrote:

          Actually Netonix (one t, no r). I don't know that I would leave it 
on, but I don't know how you're using it.

            https://www.netonix.com/wisp-switch.html

bp
<part15sbs{at}gmail{dot}com>

On 10/25/2016 9:04 AM, Josh Reynolds wrote:

            Nettonix.

            You could always leave it on... If your access network is layer2 up 
to that switch, it could help.


            On Oct 25, 2016 11:03 AM, "CBB - Jay Fuller" 
<[email protected]> wrote:


              just discovered on one of our nettronix switches spanning tree 
protocol was enabled.
              we've run this switch probably four months - no real side effects 
- but i don't run stp anywhere
              else.  any reason to leave this on?

              thanks







Reply via email to