[ Contents] [ Prev] [ Next] [ Index] [ Report an Error]

Optional: Configuring Integrated Routing and Bridging and VLAN IDs in a VPLS Routing Instance (MX-Series Routers Only)

You can configure VLAN identifiers for a VPLS instance in the following ways:

By using the input-vlan-map and the output-vlan-map statements at the [edit interfaces] hierarchy level. For more information, see the JUNOS Network Interfaces Configuration Guide and JUNOS Class of Service Configuration Guide.
By using the vlan-id or vlan-tags statements at the [edit routing-instances routing-instance-name instance-type vpls] hierarchy level.

The vlan-id and vlan-tags statements are used to perform the following functions:

Translate, or normalize, the VLAN tags of received packets received into a learn VLAN identifier.
Create multiple learning domains that each contain a learn VLAN identifier. A learning domain is a MAC address database to which MAC addresses are added based on the learn VLAN identifier.

To configure VLAN identifiers for a VPLS routing instance, include the vlan-id or vlan-tags statement at the [edit routing-instances routing-instance-name instance-type vpls] hierarchy level. For more information about how VLAN tags are processed and translated, see the JUNOS Routing Protocols Configuration Guide.

Note: You cannot configure VLAN mapping using the input-vlan-map and output-vlan-map statements if you configure a learn VLAN identifier for a VPLS instance using the vlan-id or vlan-tags statements.

IRB over VPLS cannot be used in conjunction with the vlan-id all statement. One or more Layer 2 logical interfaces must be configured inside the routing instance in order for IRB to function properly.

To configure IRB within a VPLS routing instance, include the routing-interface irb-interface-name statement at the [edit routing-instances routing-instance-name instance-type vpls] hierarchy level:



[edit]

routing-instances {




marketing {

instance-type vpls;


vlan-id 401;

route-distinguisher 11.11.11.11:10;

vrf-target target:100:100;

interface ae0.100;

interface ae0.200;


routing-interface irb.1234;

}







protocols {




vpls {

site-range 20; # If you specify a site ID that is greater
than the site range, your # connections won't come up.

no-tunnel-services;




site 2 {

site-identifier 2;

}




}




}




}

[ Contents] [ Prev] [ Next] [ Index] [ Report an Error]