Juniper Networks JUNOS OS 10.4 User Manual

Page 74

vlan-id 302;

}

}
routing-instances {

customer-c1-vsi {

instance-type vpls;
vlan-id 100;
interface ge-1/0/0.1;
interface ge-2/0/0.1;
interface ge-3/0/0.1;

} # End of customer-c1-vsi
customer-c2-vsi {

instance-type vpls;
vlan-id none; # This will remove the VLAN tags from packets sent on VPLS for customer

interface ge-1/0/0.11;
interface ge-6/0/0.11;

} # End of customer-c2-vsi

} # End of routing-instances

NOTE:

This is not a complete router configuration.

Consider the first VLAN for customer C1. The

vlan-id 100

statement in the VPLS instance

called

customer-c1-vsi

sets the normalized VLAN to 100. All packets sent over the

pseudowires have a VLAN tag of 100.

The following happens on VLAN 100 as a result of this configuration:

•

Packets received on logical interfaces

ge-1/0/0.1

ge-2/0/0.1

with a single VLAN tag

of 100 in the frame are accepted.

•

Packets received on logical interface

ge-3/0/0.1

with a single VLAN tag of 200 in the

frame are accepted and have their tag values translated to the normalized VLAN tag
value of 100.

•

Unknown source MAC addresses and unknown destination MAC addresses are learned
based on their normalized VLAN values of 100.

•

All packets sent on the VPLS pseudowire have

vlan-id 100

in their VLAN tag fields.

Now consider the second VLAN for Customer C2. The

vlan-id none

statement in the VPLS

instance called

customer-c2-vsi

removes the incoming VLAN tags before the packets

are sent over the VPLS pseudowires.

The following happens on the C2 VLAN as a result of the

vlan-id none

configuration:

•

A MAC table is created for each instance of

vlan-id none

. All MAC addresses learned

over the interfaces belonging to this VPLS instance are added to this table. The received
or configured VLAN tags are not considered when the MAC addresses are added to
this table. This is a case of shared VLAN learning.

•

Packets with a single VLAN tag value of 301 are accepted on interface

ge-1/0/0.11

. The

VLAN tag value 301 is then popped and removed from the frame of this packet.

Junos OS 13.1 MX Series 3D Universal Edge Routers Solutions Guide