Juniper Networks 10.4 - page 78

encapsulationvlan-vpls;
vlan-id302;
}
}
routing-instances{
customer-c1-vsi{
instance-typevpls;
vlan-id100;
interfacege-1/0/0.1;
interfacege-2/0/0.1;
interfacege-3/0/0.1;
}# End of customer-c1-vsi
customer-c2-vsi{
instance-typevpls;
vlan-idnone;# This will remove the VLAN tags from packetssent on VPLS for customer
2
interfacege-1/0/0.11;
interfacege-6/0/0.11;
}# End of customer-c2-vsi
}# End of routing-instances
NOTE: Thisis not a complete routerconfiguration.
Considerthe first VLAN for customer C1. The vlan-id100 statementin the VPLS instance
calledcustomer-c1-vsi sets the normalized VLAN to 100.All packets sent over the
pseudowireshave a VLAN tag of 100.
Thefollowing happens on VLAN 100 as a result of this configuration:
•Packetsreceived on logicalinterfaces ge-1/0/0.1or ge-2/0/0.1 with a single VLAN tag
of100 in the frame are accepted.
•Packetsreceived on logicalinterface ge-3/0/0.1with a single VLAN tag of 200 in the
frameare accepted and have their tagvalues translated to the normalized VLAN tag
valueof 100.
•UnknownsourceMAC addresses and unknown destination MACaddresses are learned
basedon their normalized VLAN values of 100.
•Allpackets sent on the VPLS pseudowire have vlan-id100 in their VLAN tag fields.
Nowconsider the secondVLAN for Customer C2. The vlan-id none statement in the VPLS
instancecalled customer-c2-vsi removesthe incoming VLAN tags before the packets
aresent over the VPLS pseudowires.
Copyright© 2010, Juniper Networks,Inc.54
Junos10.4 MX Series Ethernet ServicesRouters Solutions Guide