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.
Hello Community,I am looking to find some information in regards to BUM packet handling in VPLS.I am more or less understand on how it works, but looking to have some "documentation" that can prove my understanding. I sow some topics around unicast packet flow, and this more or less good described, but did not found any details about the BUM.Some confusion is around "split horizon" rules and principals... and how the L2 loop can damage the full mash (multi tenant instance) due to Broadcast.Thank you for any feedback and information.BR,
I would say that broadcast is not the same as l2 loop for the purposes of a BUM filter. While it is true that an L2 loop will generate lots of broadcast this is not what the BUM filter is aimed at correcting.BUM filters are simple rate limiting function because we know there is a distance and link limitation between the L2 devices. As a result we don't want a large portion of the traffic to be these BUM member packets and using too much of these limited links. So the BUM filter is just rate limiting the potential for taking too much of the link resource rather than trying to mitigate a problem that has occurred in the layer 2 domain like a loop.Sorry, that I don't have a documentation link. you are right that the docs tend to focus on how and configs and not so much the why.
Thank you so much Steve,Most probably I did not formulated correct the request.The main idea I am looking to clarify is the behaviour of BUM traffic in a Full Mesh VPLS instance.- How the PE will handle the traffic received from CE port (BUM traffic)- How the PE will handle the traffic received from PE port (BUM traffic)As the main idea of VPLS (the way how I understand this) is to replicate the functionality of a Standard Switch - the Broadcast frame may/will leave forever in a Full Mesh VPLS - as there is no TTL or any other way to stop/discard it?I am confident it's not the case - and I was looking for some documentation that could describe how the PE device will handle the BUM traffic been part of a full Mesh VPLS.BR,
VPLS does handle BUM traffic as the RFC dictate, there are not changes to that part.What the BUM filter is for is rate limiting to prevent too much of the traffic from being sent between instances and clogging the limited path.
Thank you so much!
So (just to have sort of confirmation to my understanding), according to RFC4762 , the BUM will be flooded to all ports (section 4.1)Same time section 4.4 says there should be sort of "
some loop-breaking protocol, like a spanning tree
And this part I am looking to understand better.How this is realised within the Juniper devices?Any references on this matter?BRAndrei
Sorry I was missing the point. I think I see the issue you are trying to address now, and agree you do NOT want to directly neighbor vpls instances in a loop. They do behave similar to old style hubs and the rate limit is minimal protection. For these scenarios where you want redundancy between multiple vpls instances you could use pseudo wire l2 circuits with failover paths so that only one is active at a time in a mesh group. These circuits stitch into the vpls and provide a connection with redundant failover.
These are some documentation examples.
some loop-breaking protocol, like a spanning tree protocol.