Juniper JUNOSE, Configuration Manual

Page: 554 / 738

S-VLAN Subinterface with an Untagged C-VLAN ID Overview
In previous releases, you could configure an S-VLAN subinterface with a C-VLAN ID
in the range 0–4095 or with the
any (5001) keyword for the VLAN ID. The single-
tagged frames with a valid S-VLAN ID or untagged frames were ignored for the
subinterface. You can now configure an S-VLAN subinterface with a C-VLAN ID, the
anyUntagged (5003) keyword , when the C-VLAN is configured inside S-VLAN as
part of a pseudowire. As a result, both customer-tagged and untagged frames can
be transported inside a prescribed S-VLAN-tag over a single pseudowire.
Observe the following guidelines when you configure an S-VLAN subinterface with
any untagged VLAN, for which the C-VLAN ID 0 is reserved.
■
Only Ethertype 0x8100 is supported on an S-VLAN subinterface that is configured
with the
anyUntagged C-VLAN ID. If you attempt to configure Ethertype 0x9100
and 0x8a88 on this S-VLAN subinterface, an error message is displayed.
■
The default Ethertype of an S-VLAN subinterface that is configured with the
anyUntagged C-VLAN id is set to 0x8100. For other VLAN subinterfaces, it is set
to 0x9100.
■
You cannot configure an S-VLAN subinterface with an S-VLAN ID value and the
C-VLAN ID as
anyUntagged if its Ethertype is 0x8100 and if any VLAN
subinterface on the same major VLAN is configured with a VLAN ID value.
Similarly, you cannot configure a VLAN subinterface with a VLAN ID value if any
S-VLAN subinterface on the same major VLAN is configured with the same S-VLAN
ID value, C-VLAN ID as
anyUntagged , and Ethertype as 0x8100. If you attempt
these procedures, an error message is displayed.
■
If you attempt to configure the Ethertype as 0x8100 on an S-VLAN subinterface,
which is configured with a valid S-VLAN ID value and C-VLAN ID as
anyUntagged ,
and if any VLAN subinterface is previously configured with a VLAN ID value on
the same major VLAN, an error message is displayed.
Related Topics
S-VLAN Subinterface with an Untagged C-VLAN ID Examples on page 551
■
■
svlan id
Multiple ATM Virtual Circuits over a Single Pseudowire Overview
In JUNOSe releases earlier than Release 10.2.x, ATM Martini circuit functionality was
supported on ERX14xx models, ERX7xx models, and the ERX310 router that enabled
the ATM cells that pertained to a particular ATM virtual circuit (VC) to be transported
over a single pseudowire. This behavior was achieved by emulating connectivity
between two ATM ports for a single virtual circuit. However, if you wanted to emulate
the connectivity between two ATM ports instead of between ATM VCs using a single
VC over a single pseudowire, all the necessary VCs had to be configured separately.
Also, in such cases, the corresponding pseudowires for each of the VCs had to be
configured individually. This method was not efficient because of the amount of
518 ■
S-VLAN Subinterface with an Untagged C-VLAN ID Overview
JUNOSe 11.0.x BGP and MPLS Configuration Guide