Technical Documentation

Option: Selecting Interfaces to Process VPLS Traffic

On M Series and T Series routers, the PICs that can create VPLS virtual ports dynamically from vt interfaces include the Tunnel Services PIC, the Link Services PIC, and the Adaptive Services PIC. On MX Series routers, logical tunnel interfaces configured by including the tunnel-services statement at the [edit chassis fpc slot-number pic number] hierarchy level can create VPLS virtual ports dynamically from vt interfaces.

By default, the JUNOS Software automatically and randomly selects vt interfaces to act as VPLS virtual ports in a round-robin fashion. However, if your routing platform contains two or more of these tunnel-enabled interfaces, you can manually select which interfaces process traffic for each VPLS domain.

You can select an interface to be the primary device responsible for VPLS traffic processing. You can also select a group of interfaces to share responsibility for VPLS traffic processing. When the primary interface is operating normally, it handles all VPLS-related tasks. If the primary device is not available, any interfaces included in the VPLS interface group assume responsibility.

To select an interface to be the primary device responsible for VPLS traffic processing, include the primary statement at the [edit routing-instances instance-name protocols vpls tunnel-services] hierarchy level. To select a group of interfaces to share responsibility for VPLS traffic processing, include the devices statement at the [edit routing-instances instance-name protocols vpls tunnel-services] hierarchy level.

[edit]routing-instances {instance-name {protocols {vpls {tunnel-services {devices [vt-0/0/0 vt-1/0/0 vt-2/0/0];primary vt-0/0/0;}}}}}

Published: 2010-04-15