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

One VPLS Instance for Several VLANs

Consider the VPLS network shown in Figure 9.

Figure 9: Many VLANs on one VPLS Instance

Image g016828.gif

The L2 PE routers are MX-series routers. Each site is connected to two P routers for redundancy, although both links are only shown for L2-PE1 at Site 1. Site 1 is connected to P0 and P1, Site 2 is connected to P0 and P2 (not shown), Site 3 is connected to P2 and P3, and Site 4 is connected to P1 and P3. VPLS pseudowires configured on the PE and P routers carry traffic between the sites.

The pseudowires for the VPLS instances are shown with distinct dashed and dotted lines. Most sites have multiple VLANs configured.

Service provider SP-1 is providing VPLS services for customer C1, services that could span several sites. Now customer C1 can have many VLANs in the range from 1 through 1000 (for example).

If VLANs 1 through 1000 for customer C1 span the same sites, then the vlan-id all and vlan-range statements provide a way to switch all of these VLANs with a minimum configuration effort and fewer switch resources.

Note: You cannot use the vlan-id all statement if you configure an IRB interface on one or more of the VLANs.

The following example illustrates the use of the vlan-id all statement:



[edit]
interfaces ge-1/0/0 {
flexible-vlan-services;
flexible-vlan-tagging;


unit 1 {
encapsulation vlan-vpls;
vlan-id-range 1-1000;
}




unit 11 {
encapsulation vlan-vpls;
vlan-id 1500;
}


}
interfaces ge-2/0/0 {
flexible-vlan-services;
flexible-vlan-tagging;


unit 1 {
encapsulation vlan-vpls;
vlan-id-range 1-1000; # Note the use of the VLAN id range
statement.
}


}
interfaces ge-3/0/0/ {
flexible-vlan-services;
flexible-vlan-tagging;


unit 1 {
encapsulation vlan-vpls;
vlan-id 1-1000;
}


}
interfaces ge-6/0/0 {
flexible-vlan-services;
flexible-vlan-tagging;


unit 11 {
encapsulation vlan-vpls;
vlan-id 1500;
}


}
routing-instances {


customer-c1-v1-to-v1000 {
instance-type vpls;
vlan-id all; # Note the use of the VLAN id all statement
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;
vlan-id 1500;
interface ge-1/0/0.11;
interface ge-6/0/0.11;
} # End of customer-c1-v1500


} # End of routing-instances

Note the use of the vlan-id all and vlan-id-range statements in the VPLS instance called customer-c1-v1-to-v1000. The vlan-id all statement implicitly creates multiple learning domains, each with its own normalized VLAN.

The following happens as a result of the vlan-id all 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.
Unknown source MAC addresses and unknown destination MAC addresses are learned based on their normalized VLAN values of 1 through 1000.
All packets sent on the VPLS pseudowire have a normalized VLAN tag after the source MAC address field in the encapsulated Ethernet packet.
Although there are only three logical interfaces in the VPLS instance called customer-c1-v1-to-v1000, the same MAC address (for example, M1) can be learned on different logical interfaces for different VLANs. For example, MAC address M1 could be learned on logical interface ge-1/0/0.1 for VLAN 500 and also on logical interface ge-2/0/0.1 for VLAN 600.

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