Port isolation

[mcnnetops]

Our network designs are different, but I am also on the learning path for MSTP.

Nothing as frustrating as dealing with unexpected configuration behavior. So you might want to subscribe to this other thread about a potential MSTP bug I uncovered:

viewtopic.php?f=17&t=6787&p=33868#p33866

At this point - Ill try anything (once).

Thanks for this, Ill check it out!

:)

[JustJoe]

...

At this point - Ill try anything (once).

Thanks for this, Ill check it out!

:)

Indeed! Now if Stephen could actually find time to take a look at that bug. ;)

[Stephen]

Looking into that and TLS 1.2 this week.

[mcnnetops]

Our network designs are different, but I am also on the learning path for MSTP.

Nothing as frustrating as dealing with unexpected configuration behavior. So you might want to subscribe to this other thread about a potential MSTP bug I uncovered:

viewtopic.php?f=17&t=6787&p=33868#p33866

So, I started having consultant looking at our lab set up and give me some recommendations. May move away from MSTP - but get this:

(My guess is that as I turn it off each night that counts as a reboot) - but MSTP is working!

All my links have been up all morning / day no drop outs no weird forward / learning / discarding changes. All OSFP routes are working, and when a link goes down all traffic still goes the other way.

After reading your post(s) - I seem to be seeing similar issues that when the switch is power cycled MSTP works...?

I may be missing a lot so take that with a grain of salt as they say, but wanted to give some feed back.

[JustJoe]

Yes, turning off the switch and back on is one of the ways it started working for me (basically also the same thing after a GUI software reboot request). The other was doing a separate apply after an MSTP revision number change.

It was when I started closely watching msti (instance) numbers in each log message that I realized they weren't matching up, while the VLAN messages were.

As I also mentioned today in another thread, I only started testing at v1.5.6. Maybe MSTP did not have this problem in earlier versions

[mike99]

Sorry for the late reply.

I would personnaly not use a flat network even for management. I personnaly use a management vlan ID by tower to make sure every tower are isolated at L2 from each other.

MSTP and ERPS are both at beta state since really few use those and I was probably the only one interested in those feature until today. Anyway, even if those 2 would be working perfectly, I would limit the L2 network to 3 or 4 towers since it's really easy to have issue with a L2 network and the more large is the L2 network, the more difficult it is to narrow the source of the issue.

[JustJoe]

Sorry for the late reply.

I would personnaly not use a flat network even for management. I personnaly use a management vlan ID by tower to make sure every tower are isolated at L2 from each other.

MSTP and ERPS are both at beta state since really few use those and I was probably the only one interested in those feature until today. Anyway, even if those 2 would be working perfectly, I would limit the L2 network to 3 or 4 towers since it's really easy to have issue with a L2 network and the more large is the L2 network, the more difficult it is to narrow the source of the issue.

Ah, from the forums, I saw you provided a lot of feedback on MSTP in the past. :)

If you have a chance, please see if you can reproduce viewtopic.php?f=17&t=6787&p=33868#p33866

The log & config are uploaded in the second post.

Stephen has mentioned that the newer-implemented ERPS is beta-ish. But after a few years I thought MSTP would have been more solid by now..

[JustJoe]

.......

Hi mike99, If you have some time, can you comment on this thread about MSTP revisions?

viewtopic.php?f=6&t=6794