Quantcast
Viewing all articles
Browse latest Browse all 27527

Second opinion on vLAN tagging

I'm looking for a second opinion to make sure I'm not being brain dead and missing something.

We have two sites, both sites are on different \16 subnets.  They are connected via a carrier provided MPLS.  

I have the vlans replicated on both sides of the MPLS, meaning that the X vlan is servers and the Y vlan is phones on both sides, but they're different subnets. 

I was reviewing my switch config in the primary location and noticed that I had X, Y, and other vLAN's tagged on the MPLS switch port.  

As I'm thinking about it, this shouldn't be necessary and it could be causing unnecessary traffic going across the MPLS link.  

If a device in Site A wants to talk to a device in Site B, it's going to need to be routed and isn't going to find the partner via broadcast anyway.  But because the MPLS port is a tagged member of the vLAN broadcasts on that vLAN ARE going go into the MPLS pipe for no reason...

In my current thinking, the only vLAN's I would want tagged on the MPLS port are those that have the same subnet on both sides?  The only reason I would want to keep tagging on the MPLS port would be to ensure that vlan tags remain with the packets and any QOS measures in the MPLS pipe can be applied.  

Am I missing something?


Viewing all articles
Browse latest Browse all 27527

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>