Log in to ask questions, share your expertise, or stay connected to content you value. Don’t have a login? Learn how to become a member.
I have been reading through the published Juniper campus design guides but the section regarding STP interactions are about are not really covered very well.<o:p></o:p>
They simply state that STP is not needed (in the core).
I have a L2 network in typical style.<o:p></o:p>
We have a Virtual chassis as a core switch which is the STP root.<o:p></o:p>
We have a number of access switches that hang from the virtual chassis. Some of these access switches also have attached access switches ( two layers deep ).<o:p></o:p>
All of this runs RSTP with the root being the core switch.<o:p></o:p>
I would like to understand better the interaction and recommended config for the STP configuration between the core and access layer.<o:p></o:p>
I understand that the VXLAN core is loop free due to its L3 underlay, but that it has no internal loop protection mechanism.<o:p></o:p>
<o:p> </o:p>Thus we have the risk of a loop being introduced by a miswiring (backdoor link) or some other loop creation problem in the access layer.
The access switches still need to run STP to make sure that there are no loops in their domain.<o:p></o:p>
But how is the VXLAN core configured?<o:p></o:p>
I have seen documents talking about EVPN loop-Protect (where OAM/CFM frames are used for loop protection) and also about placing [protocols layer2-control bpdu-block] on the edge ports of the switches.<o:p></o:p>
But what is the recommended template for the core switch?<o:p></o:p>
<o:p> </o:p><o:p></o:p>Is this stating that these commands should be implemented on the Core switch interface facing the access or are they stating that they should be on the access switch that faces the core switch?<o:p></o:p>
This is not explained very well. I would assume that it is on the edge interface of the core switch to isolate the troublesome access switch, but it then states: <o:p></o:p>
"Note: Ensure that the switch is connected to an end device.", thus it then gives the appearance that these commands are for the access switch…..<o:p></o:p>
This seems more of a DC related feature and looks like it may be QFX platform specific rather than a campus related feature.<o:p></o:p>
The design guides don't cover this and simply state that the VXLAN core is loop free (STP free).<o:p></o:p>
Can someone please share some recommended implementation details or someone from Juniper ask the Documentation Team to update these design guides to cover this topic please.