}# End of customer-c1-v1-to-v1000
customer-c1-v1500{
instance-typevpls;
vlan-id1500;
interfacege-1/0/0.11;
interfacege-6/0/0.11;
}# End of customer-c1-v1500
}# End of routing-instances
Notethe use of the vlan-id all and vlan-id-range statements in the VPLS instancecalled
customer-c1-v1-to-v1000.The vlan-id all statement implicitly createsmultiple learning
domains,each with its own normalized VLAN.
Thefollowing happens as a result of the vlan-idall configuration:
Packetsreceived on logicalinterfaces ge-1/0/0.1, or ge-2/0/0.1, or ge-3/0/0.1,with a
singleVLAN tag in the range from 1 through 1000 in the frame areaccepted.
UnknownsourceMAC addresses and unknown destination MACaddresses are learned
basedon their normalized VLAN values of 1 through 1000.
Allpackets sent on the VPLS pseudowirehave a normalized VLAN tag after the source
MACaddress field in the encapsulatedEthernet packet.
Althoughthere are only three logical interfacesin the VPLS instance called
customer-c1-v1-to-v1000,the same MAC address (for example,M1) can be learned on
differentlogical interfaces fordifferent VLANs. For example, MAC address M1 could
belearned on logical interface ge-1/0/0.1for VLAN 500 and also on logical interface
ge-2/0/0.1for VLAN 600.
Related
Documentation
MXSeries Ethernet Services Routers SolutionsPage
VLANsWithin a Bridge Domain or VPLS Instance on page 43
PacketFlow Through a BridgedNetwork with Normalized VLANs on page 44
ConfiguringLearning Domains for VLAN IDs Bound to Logical Interfaceson page 47
Copyright© 2010, Juniper Networks,Inc.58
Junos10.4 MX Series Ethernet ServicesRouters Solutions Guide