Juniper Networks JUNOS OS 10.4 - Manual (Page 79)

encapsulation vlan-vpls;
vlan-id-range 1-1000; # Note the use of the VLAN id range statement.
input-vlan-map {
push; /* Push the service vlan on input */
vlan-id 1300; # This VLAN ID is the normalized VLAN for incoming packets
}
output-vlan-map pop; /* Pop the service vlan on output */
}
}
}
interfaces ge-3/0/0 {
encapsulation flexible-ethernet-services;
flexible-vlan-tagging;
unit 1 {
encapsulation vlan-vpls;
vlan-id 1-1000;
input-vlan-map {
push; /* Push the service vlan on input */
vlan-id 1400; # This VLAN ID is the normalized VLAN for incoming packets
}
output-vlan-map pop; /* Pop the service vlan on output */
}
}
}
interfaces ge-6/0/0 {
encapsulation flexible-ethernet-services;
flexible-vlan-tagging;
unit 11 {
encapsulation vlan-vpls;
vlan-id 1500;
}
}
routing-instances {
customer-c1-v1-to-v1000 {
instance-type vpls;
interface ge-1/0/0.1;
interface ge-2/0/0.1;
interface ge-3/0/0.1;
} # End of customer-c1-v1-to-v1000
customer-c1-v1500 {
instance-type vpls;
interface ge-1/0/0.11;
interface ge-6/0/0.11;
} # End of customer-c1-v1500
} # End of routing-instances
The following operations are performed when you use the VLAN mapping configuration:
• Packets received on logical interfaces ge-1/0/0.1 , or ge-2/0/0.1 , or ge-3/0/0.1 , with a
single VLAN tag in the range from 1 through 1000 in the frame are accepted.
• The VLAN tags of a received packet are compared with the normalized VLAN tags
specified with the vlan-id statement in the input VLAN map. If the VLAN tags of the
received packet are different from the normalized VLAN tags, then the received VLAN
tag is converted to the normalized VLAN tag of 1200 for packets received on the logical
interface
ge-1/0/0.1 . Similarly, for logical interface ge-2/0/0.1 , the normalized VLAN
59 Copyright © 2013, Juniper Networks, Inc.
Chapter 4: VLANs Within Bridge Domain and VPLS Environments