Hub spoke & full mesh || VPLS
- x
- convention：
- Emotion(0)
|
Hi, what are the hub spoke & full mesh scenerios in VPLS ? , ====== Please refer to the topology below: Hub & Spoke:
Full mesh:
where we use which scenarios ? ====== The hub & spoke is usually implemented between the HQ and branches. For example, the traffic between branches should be forwarded to the HQ, and then to the destination. This will help the HQ control the traffic between branches. The full mesh is usually used in the scenario that the amount of traffic between nodes are is basically the same. In this scenario, if we use the hub & spoke topology, it will burden the hub router. how to avoid loop? ====== In VPLS, "full connection" and "split-horizon forwarding" are used to avoid loops. Each PE must create a tree for each VPLS forwarding instance to all other PE devices under the instance. Each PE device must support the "split horizon" policy to avoid loops, that is, PEs cannot forward packets on PWs with the same VPLS instance. "Split horizon forwarding" means that packets received from PWs on the public network are no longer forwarded to other PWs, but can only be forwarded to the private network. Packets received from PEs cannot be forwarded to other PEs. The full connection and split horizon between PEs ensure the reachability and loop-free forwarding of VPLS. When multiple CEs are connected to PEs, or there are connections between different CEs connected to a VPLS VPN, VPLS cannot guarantee that there are no loops. The loop occurs, and other methods, such as STP, etc., need to be used to close the loop. |
|
|
Hi, what are the hub spoke & full mesh scenerios in VPLS ? , ====== Please refer to the topology below: Hub & Spoke:
Full mesh:
where we use which scenarios ? ====== The hub & spoke is usually implemented between the HQ and branches. For example, the traffic between branches should be forwarded to the HQ, and then to the destination. This will help the HQ control the traffic between branches. The full mesh is usually used in the scenario that the amount of traffic between nodes are is basically the same. In this scenario, if we use the hub & spoke topology, it will burden the hub router. how to avoid loop? ====== In VPLS, "full connection" and "split-horizon forwarding" are used to avoid loops. Each PE must create a tree for each VPLS forwarding instance to all other PE devices under the instance. Each PE device must support the "split horizon" policy to avoid loops, that is, PEs cannot forward packets on PWs with the same VPLS instance. "Split horizon forwarding" means that packets received from PWs on the public network are no longer forwarded to other PWs, but can only be forwarded to the private network. Packets received from PEs cannot be forwarded to other PEs. The full connection and split horizon between PEs ensure the reachability and loop-free forwarding of VPLS. When multiple CEs are connected to PEs, or there are connections between different CEs connected to a VPLS VPN, VPLS cannot guarantee that there are no loops. The loop occurs, and other methods, such as STP, etc., need to be used to close the loop. |
|
Comment
- Politically sensitive content
- Content concerning pornography, gambling, and drug abuse
- Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
