Configuring the VPLS Interface Encapsulation

You need to specify an encapsulation type for each PE-router-to-CE-router interface configured for VPLS. This section describes the encapsulation statement configuration options available for VPLS. For a full description of all of the options available for this statement, see the JUNOS Network Interfaces Configuration Guide.

To configure the encapsulation type on the physical interface, include the encapsulation statement:

You can include the encapsulation statement for physical interfaces at the following hierarchy levels:

• [edit interfaces interface-name]
• [edit logical-systems logical-system-name interfaces interface-name]

You can configure the following physical interface encapsulations for VPLS routing instances:

• ethernet-vpls—Use Ethernet VPLS encapsulation on Ethernet interfaces that have VPLS enabled and that must accept packets carrying standard Tag Protocol ID (TPID) values. On M-series routers (except the M320), the 4-port Fast Ethernet TX PIC and the 1-port, 2-port, and 4-port, 4-slot Gigabit Ethernet PICs can use the Ethernet VPLS encapsulation type.
• extended-vlan-vpls—Use extended virtual LAN (VLAN) VPLS encapsulation on Ethernet interfaces that have VLAN 802.1Q tagging and VPLS enabled and that must accept packets carrying TPIDs 0x8100, 0x9100, and 0x9901. On M-series routers (except the M320), the 4-port Fast Ethernet TX PIC and the 1-port, 2-port, and 4-port, 4-slot Gigabit Ethernet PICs can use the Ethernet VPLS encapsulation type.

  Note: The built-in Gigabit Ethernet PIC on an M7i router does not support extended VLAN VPLS encapsulation.

• vlan-vpls—Use VLAN VPLS encapsulation on Ethernet interfaces with VLAN tagging and VPLS enabled. Interfaces with VLAN VPLS encapsulation accept packets carrying standard TPID values only. On M-series routers (except the M320), the 4-port Fast Ethernet TX PIC and the 1-port, 2-port, and 4-port, 4-slot Gigabit Ethernet PICs can use the Ethernet VPLS encapsulation type.

To configure the encapsulation type for logical interfaces, include the encapsulation statement:

You can include the encapsulation statement for logical interfaces at the following hierarchy levels:

• [edit interfaces interface-name unit number]
• [edit logical-systems logical-system-name interfaces interface-name unit number]

You can configure the following logical interface encapsulations for VPLS routing instances:

• ether-vpls-over-atm-llc—Use Ethernet VPLS over Asynchronous Transfer Mode (ATM) logical link control (LLC) encapsulation to bridge Ethernet interfaces and ATM interfaces over a VPLS routing instance (as described in RFC 2684, Multiprotocol Encapsulation over ATM Adaptation Layer 5). Packets from the ATM interfaces are converted to standard ENET2/802.3-encapsulated Ethernet frames with the frame check sequence (FCS) field removed. This encapsulation type is supported on ATM intelligent queuing (IQ) interfaces only.
• vlan-vpls—Use VLAN VPLS encapsulation on Ethernet interfaces with VLAN tagging and VPLS enabled. Interfaces with VLAN VPLS encapsulation accept packets carrying standard TPID values only. On M-series routers (except the M320), the 4-port Fast Ethernet TX PIC and the 1-port, 2-port, and 4-port, 4-slot Gigabit Ethernet PICs can use the Ethernet VPLS encapsulation type.

When you configure the physical interface encapsulation as vlan-vpls, you also need to configure the same interface encapsulation for the logical interface. You need to configure the vlan-vpls encapsulation on the logical interface because the vlan-vpls encapsulation allows you to configure a mixed mode, where some of the logical interfaces use regular Ethernet encapsulation (the default for logical interfaces) and some use vlan-vpls. For more information, see the JUNOS Network Interfaces Configuration Guide.

Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice.