An Ethernet virtual LAN (VLAN) circuit can be configured using either the vlan-ccc or extended-vlan-ccc encapsulation. If you configure the extended-vlan-ccc encapsulation on the physical interface, you cannot configure the inet family on the logical interfaces. Only the ccc family is allowed. If you configure the vlan-ccc encapsulation on the physical interface, both the inet and ccc families are supported on the logical interfaces. Ethernet interfaces in VLAN mode can have multiple logical interfaces.
For encapsulation type vlan-ccc, VLAN IDs from 512 through 4094 are reserved for CCC VLANs. For the extended-vlan-ccc encapsulation type, all VLAN IDs 1 and higher are valid. VLAN ID 0 is reserved for tagging the priority of frames.
 |
Note: Some vendors use the proprietary TPIDs 0x9100 and 0x9901 to encapsulate a VLAN-tagged packet into a VLAN-CCC tunnel to interconnect a geographically separated metro Ethernet network. By configuring the extended-vlan-ccc encapsulation type, a Juniper Networks router can accept all three TPIDs (0x8100, 0x9100, and 0x9901). |
Configure an Ethernet VLAN circuit with the vlan-ccc encapsulation as follows:
- interfaces {
-
-
type-fpc/pic/port {
- vlan-tagging;
- encapsulation vlan-ccc;
-
- unit logical-unit-number {
- encapsulation vlan-ccc;
- vlan-id vlan-id;
- }
- }
- }
You can configure these statements at the following hierarchy levels:
Configure an Ethernet VLAN circuit with the extended-vlan-ccc encapsulation statement as follows:
- interfaces {
-
-
type-fpc/pic/port {
- vlan-tagging;
- encapsulation extended-vlan-ccc;
-
- unit logical-unit-number {
- vlan-id vlan-id;
- family ccc;
- }
- }
- }
You can configure these statements at the following hierarchy levels:
Whether you configure the encapsulation as vlan-ccc or extended-vlan-ccc, you must enable VLAN tagging by including the vlan-tagging statement.
 | Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |