Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

Configuring VPLS Ports in a Virtual Switch

In Junos OS Release 9.3 and later, you can configure VPLS ports in a virtual switch so that the logical interfaces of the Layer 2 bridge domains in the virtual switch can handle VPLS routing instance traffic. VPLS configuration no longer requires a dedicated routing instance of type vpls. Packets received on a Layer 2 trunk interface are forwarded within a bridge domain that has the same VLAN identifier.

A trunk interface is implicitly associated with bridge domains based on VLAN membership. Whereas access interfaces can be part of one VLAN only, trunk interfaces multiplex traffic from multiple VLANs and usually interconnect switches. A Layer 2 trunk port also supports IRB.

1. To configure the Layer 2 trunk ports that you will associate with the bridge domains in the virtual switch, include the following statements in the configuration:

   [edit]interfaces {interface-name {unit logical-unit-number { # Call this ’L2-trunk-port-A’family bridge {interface-mode trunk;vlan-id-list [ vlan-id-numbers ] ; # Trunk mode VLAN membership for this interface}}}...interface-name {unit logical-unit-number { # Call this ’L2-trunk-port-B’family bridge {interface-mode trunk;vlan-id-list [ vlan-id-numbers ] ; # Trunk mode VLAN membership for this interface}}}}
   To configure a logical interface as a trunk port, include the interface-mode statement and the trunk option at the [edit interfaces interface-name unit logical-unit-number family bridge] hierarchy level.

   To configure all the VLAN identifiers to associate with a Layer 2 trunk port, include the vlan-id-list [ vlan-id-numbers ] statement at the [edit interfaces interface-name unit logical-unit-number family bridge] hierarchy level.

   Each of the logical interfaces “L2-trunk-port-A” and “L2-trunk-port-B” accepts packets tagged with any VLAN ID specified in the respective vlan-id-list statements.

2. To configure a virtual switch consisting of a set of bridge domains that are associated with one or more logical interfaces configured as a trunk ports, include the following statements in the configuration:

   [edit]routing-instance {routing-instance-nameinstance-type virtual-switch;interface L2-trunk-port-A; # Include one trunk portinterface L2-trunk-port-B; # Include the other trunk portbridge-domains {bridge-domain-name-0 {domain-type bridge;vlan-id number;}bridge-domain-name-1 {domain-type bridge;vlan-id number;}}protocols {vpls {vpls-id number;... vpls-configuration ...}}}}
   To begin configuring a virtual switch, include the instance-type statement and the virtual-switch option at the [edit routing-instances routing-instance-name] hierarchy level.

   To configure a virtual switch consisting of a set of bridge domains that are associated with one or more logical interfaces configured as a trunk ports, you must identify each logical interface by including the interface interface-name statement at the [edit routing-instances routing-instance-name] hierarchy level.

   For each VLAN configured for a trunk port, you must configure a bridge-domain that includes the trunk port logical interface and uses a VLAN identifier within the range carried by that trunk interface. To configure, include the domain-type bridge, vlan-id number, and statements at the [edit routing-instances routing-instance-name bridge-domain bridge-domain-name] hierarchy level.