Dear,
I hope my answer will help you.
The Virtual Private LAN Service (VPLS) is an Ethernet-based service that allows geographically scattered Ethernet LANs to communicate with one another. It transports packets using MPLS as the transport/backbone network while keeping the enterprise interface looking like a regional or national Ethernet. Even though the packets traverse the service provider's MPLS network, the enterprise's locations appear to be on the same Ethernet LAN. A 100 Mbps VPLS interface can offer an SLA for customer traffic speeds ranging from 1 Mbps to 100 Mbps, commonly in 1 Mbps increments.
The MAC address is used by VPLS to locate the other endpoint. The IP address isn't used in any way. With VPLS, the organization needs to address RTP header compression. This header compression can be used in enterprise routers that are connected to VPLS. With RTP header compression, voice bandwidth requirements are reduced by 20 percent to 60 percent.
For a few sites, VPLS works great, but it does not scale effectively. Ethernet broadcast flooding uses network bandwidth, which cannot be alleviated by purchasing more bandwidth, and QoS is ineffective. It should be fine as long as the remote offices connect to regional sites via the Internet rather than VPLS. VPLS, on the other hand, is not the greatest technology for scaling to hundreds of sites. MPLS is a much better option for businesses with a significant number of remote locations.
Benefits
- Reduced latency
- A network that is fast, secure, and homogeneous.
- Private lines are more expensive.
- In addition to IP, it supports legacy protocols.
Issues
- It's difficult to keep track of a big number of MAC addresses because they don't have a hierarchy like IP addresses.
- The customer, not the carrier, is in charge of their own network. These resources are more likely to be found in larger organizations.
- If you understand Ethernet, technology is not difficult.
- Not as adaptable to a broad range of sites.
