Juniper Networks JUNOS OS 10.4 User Manual
Page 78
For the same network topology illustrated in
, if VLANs 1 through 1000
for customer C1 span the same sites, you can normalize the VLANs by doing one of the
following. Using either of these optimal methods, you can switch and normalize all of
these VLANs in an effective, streamlined manner without configuring separately for each
VLAN ID.
•
By configuring a VPLS routing instance if the logical interfaces are specified with a
range of consecutive VLANs or a list of non-contiguous VLAN IDs and using VLAN maps
to rewrite the VLAN tags on all of the incoming and outgoing packets on the logical
interfaces with a normalized VLAN ID
•
By configuring a virtual-switch instance consisting of a set of bridge domains that are
associated with one or more logical interfaces configured as a trunk port
You cannot use the
vlan-id
statement to enable VLAN normalization in VPLS instances,
if the logical interfaces in the VPLS instance are configured with the
vlan-id-list
or
vlan-id-range
statement. In such a scenario, you can use the
input-vlan-map
or the
output-vlan-map
option to achieve VLAN normalization.
The following example illustrates the use of the VLAN mapping functionality in VPLS
routing instances to normalize VLANs. This method is beneficial in scenarios with flexible
VLAN tagging (asymmetric tag depth). In such an environment, the VLAN configuration
data that you specified applies the appropriate VLAN tags to the input and output VLAN
maps for the ingress and egress logical interfaces respectively. For example, if certain
packets are received as single- tagged packets and if the remaining packets are received
as double-tagged packets, using VLAN mapping enables normalization.
Using the VLAN mapping capability is effective only if packets of unequal VLAN tags are
received or transmitted from logical interfaces to achieve normalization. We recommend
that you do not use VLAN mapping in environments in which the VLAN tags are of equal
tag depths for optimal configuration. In such cases, you can use the
vlan-id all
statement
to enable normalization of VLANs.
[edit]
interfaces ge-1/0/0 {
encapsulation flexible-ethernet-services;
flexible-vlan-tagging;
unit 1 {
encapsulation vlan-vpls;
vlan-id-range 1-1000;
input-vlan-map {
push; /* Push the service vlan on input */
vlan-id 1200; # This VLAN ID is the normalized VLAN for incoming packets
}
output-vlan-map pop; /* Pop the service vlan on output */
}
unit 11 {
encapsulation vlan-vpls;
vlan-id 1500;
}
}
interfaces ge-2/0/0 {
encapsulation flexible-ethernet-services;
flexible-vlan-tagging;
unit 1 {
Copyright © 2013, Juniper Networks, Inc.
58
Junos OS 13.1 MX Series 3D Universal Edge Routers Solutions Guide