ERPS and MSTP
Question about ERPS on TP-Link switches:
When configuring ERPS on a TP-Link L2+ / L3 switch, we specify an MSTP instance as the protection domain of the ERPS ring (the MSTP instance contains both the control VLAN and the data VLAN(s)) - can this MSTP Instance additionally be activated on other physical interfaces that we need the data VLANs to transit? And, if so, is it safe / acceptable to set the MSTP region to a value other than the MAC of the switch? (The TP-Link ERPS documentation does not say anything about setting the region - nor any other parameters of the MSTP config, other than that the Instance must cover the protection VLAN and the data VLAN(s) of the ring.)
Thanks in advance
-f
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @Nlx
Thanks for posting in our business forum.
From what you described, it looks like more of a presale consultation.
You can take a look at the following articles: How to configure MSTP on L2 Managed switches using the new GUI
Spanning Tree Configuration in Omada SDN Controller Mode
I think they can answer your questions. Note that our Omada switch does not support ERPS(new models SG6000 series seem not available in many regions). Some old models from the Jetstream series support that.
If this reply does not resolve your questions, please be specific about the docs you are referring to. So we can discuss on the same page.)
- Copy Link
- Report Inappropriate Content
Nope, not presales: we have a mix of sx3008 and sx3016 operating in an ERPS ring configuration for many months now. There are single 10GbE links between each switch, carrying two counter-directional ring instances. Each instance carries approx 5-6 data VLANs plus one protection VLAN. This was all configured per the TP-Link ERPS configuration guide, and works great - fail over recovery is very fast, and the rings are an economical approach to running a redundant multi-story small commercial building backbone.
We now want to extend some of these VLANs out of the ring switches, with a single link to a switch that doesn't support ERPS - because of the single link and because the non-ring switches don't support ERPS, there is a need to use some variant of stp to protect against loops.
TP link stands alone in ERPS providers (as far as my experience) in that the TP link ERPS declaration requires use of an MSTP instance to identify the VLANs protected by the ring - so we are asking if the MSTP instance used for the ring can also be used on non-ring ports: the little documentation TP link provides is totally silent on this! Further, the documentation does not state if we can assign a region name to the MSTP instance, or if the region needs to be left at the standard default of each switch Mac address.
Note that we definitely can't use a separate MSTP instance to provide loop protection for this application, as a VLAN can only be a member of a single MSTP instance and the ring requires that instance be for the ring.
If you can't answer this basic question about a product function, please refer me to someone who can - we can't afford to test this in production with the risk of knocking out our building backbone. Thanks.
-f
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 118
Replies: 3
Voters 0
No one has voted for it yet.