encapsulation
You configure three encapsulation types: one for the encapsulation on the logical interface, one for the encapsulation on the physical interface, and one for the Layer 2 protocol on the routing instance.
encapsulation (logical interface)
Syntax
encapsulation (atm-ccc-cell-relay | atm-ccc-vc-mux | atm-tcc-vc-mux | atm-cisco-nlpid | atm-mlppp-llc | atm-nlpid | atm-snap | atm-tcc-snap | atm-vc-mux | ether-over-atm-llc | ether-vpls-over-atm-llc | frame-relay-ccc | frame-relay-tcc | multilink-frame-relay-end-to-end | multilink-ppp | vlan-ccc);Hierarchy Level
[edit interfacesinterface-nameunitlogical-unit-number],[edit logical-routerslogical-router-nameinterfacesinterface-nameunitlogical-unit-number]Description
Logical link-layer encapsulation type.
Options
atm-ccc-cell-relay—Use ATM cell relay encapsulation.
atm-ccc-vc-mux—Use ATM virtual connection (VC) multiplex encapsulation on CCC circuits. When you use this encapsulation, you can configure the familyccconly.
atm-tcc-vc-mux—Use ATM VC multiplex encapsulation on TCC circuits. When you use this encapsulation, you can configure the familytcconly.
atm-cisco-nlpid—Use Cisco ATM NLPID encapsulation. When you use this encapsulation, you can configure the familyinetonly.
atm-mlppp-llc—Use Multilink PPP over ATM adaptation layer 5 (AAL5) logical link control (LLC). This encapsulation type is used only on ATM 2 interfaces. For this encapsulation type, your router must be equipped with a Link Services PIC.
atm-nlpid—Use ATM NLPID encapsulation. When you use this encapsulation, you can configure the familyinetonly.
atm-snap—Use ATM Subnetwork Access Protocol (SNAP) encapsulation.
atm-tcc-snap—Use ATM SNAP encapsulation on TCC circuits.
atm-vc-mux—Use ATM VC multiplex encapsulation. When you use this encapsulation, you can configure the familyinetonly.
ether-over-atm-llc—For interfaces that carry IPv4 traffic, use Ethernet over ATM logical link control (LLC) encapsulation. When you use this encapsulation, you cannot configure multipoint interfaces.
ether-vpls-over-atm-llc—Use Ethernet VPLS over ATM LLC encapsulation. This encapsulation type enables a VPLS instance to support bridging between Ethernet interfaces and ATM interfaces, as described in RFC 2684, Multiprotocol Encapsulation over ATM Adaptation Layer 5. This encapsulation type is used only on ATM 2 interfaces.
frame-relay-ccc—Use Frame Relay encapsulation on CCC circuits. When you use this encapsulation, you can configure the familyccconly.
frame-relay-tcc—Use Frame Relay encapsulation on TCC circuits for connecting unlike media. When you use this encapsulation, you can configure the familytcconly.
multilink-frame-relay-end-to-end—Use Multilink Frame Relay (MLFR) FRF.15 encapsulation for multilink and link services interfaces and their constituent T1 or E1 interfaces.
multilink-ppp—Use Multilink Point-to-Point Protocol (MLPPP) encapsulation. This encapsulation is used only on multilink interfaces and their constituent T1 or E1 interfaces.
vlan-ccc—Use Ethernet VLAN encapsulation on CCC circuits. When you use this encapsulation, you can configure the familyccconly.Usage Guidelines
See Configure CCC Encapsulation on Interfaces or Configure TCC Encapsulation on Interfaces.
Required Privilege Level
interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration.encapsulation (physical interface)
Syntax
encapsulation (atm-ccc-cell-relay | atm-pvc | cisco-hdlc | cisco-hdlc-ccc | cisco-hdlc-tcc |
ethernet-ccc | ethernet-vpls | frame-relay | frame-relay-ccc | frame-relay-tcc |
multilink-frame-relay-uni-nni | ppp | ppp-ccc | ppp-tcc | vlan-ccc | vlan-vpls |
extended-vlan-ccc | extended-vlan-vpls);Hierarchy Level
[edit interfacesinterface-name],[edit logical-routerslogical-router-nameinterfacesinterface-name]Description
Physical link-layer encapsulation type.
Options
atm-ccc-cell-relay—Use Asynchronous Transfer Mode (ATM) cell relay encapsulation.
atm-pvc—Use ATM permanent virtual connection (PVC) encapsulation.
cisco-hdlc—Use Cisco-compatible High-level Data Link Control (HDLC) framing.
cisco-hdlc-ccc—Use Cisco-compatible HDLC framing on circuit cross-connect (CCC) circuits.
cisco-hdlc-tcc—Use Cisco-compatible HDLC framing on translational cross-connect (TCC) circuits for connecting unlike media.
ethernet-ccc—Use Ethernet CCC encapsulation on Ethernet interfaces that must accept packets carrying standard Tag Protocol ID (TPID) values.
ethernet-tcc—For interfaces that carry Internet Protocol Version 4 (IPv4) traffic, use Ethernet TCC encapsulation on interfaces that must accept packets carrying standard TPID values. Ethernet TCC is not currently supported on Fast Ethernet 48-port Physical Interface Cards (PICs).
ethernet-vpls—Use Ethernet Virtual Private LAN Service (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, 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-ccc—Use extended virtual local area network (VLAN) encapsulation on CCC circuits with Gigabit Ethernet and 4-port Fast Ethernet interfaces that must accept packets carrying 802.1Q values.
extended-vlan-tcc—For interfaces that carry IPv4 traffic, use extended VLAN encapsulation on TCC circuits with Gigabit Ethernet interfaces on which you want to use 802.1Q tagging. Extended Ethernet TCC is not currently supported on Fast Ethernet 48-port PICs.
extended-vlan-vpls—Use extended 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, 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.
frame-relay—Use Frame Relay encapsulation.
frame-relay-ccc—Use plain Frame Relay (frame-relay) encapsulation or Frame Relay encapsulation on CCC circuits.
frame-relay-tcc—Use Frame Relay encapsulation on TCC circuits for connecting unlike media.
multilink-frame-relay-uni-nni—Use only on link services interfaces functioning as FRF.16 bundles and their constituent T1, E1, or NxDS-0 interfaces.
ppp—Use serial Point-to-Point Protocol (PPP) encapsulation.
ppp-ccc—Use serial PPP encapsulation on CCC circuits. When you use this encapsulation, you can configure the familyccconly.
ppp-tcc—Use serial PPP encapsulation on TCC circuits for connecting unlike media. When you use this encapsulation, you can configure the familytcconly.
vlan-ccc—Use Ethernet VLAN encapsulation on CCC circuits.
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, 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.Default
Usage Guidelines
See Configure CCC Encapsulation on Interfaces or Configure TCC Encapsulation on Interfaces.
Required Privilege Level
interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration.encapsulation (Layer 2 VPN)
Syntax
Hierarchy Level
[edit logical-routerslogical-router-namerouting-instancesrouting-instance-nameprotocols l2vpn],[edit routing-instancesrouting-instance-nameprotocols l2vpn]Description
Layer 2 protocol used for traffic from the customer edge (CE) router.
Options
type—The following Layer 2 encapsulation types are supported:
atm-aal5—ATM Adaptation Layer (AAL/5)atm-cell—ATM cell relayatm-cell-port-mode—ATM cell relay port promiscuous modeatm-cell-vc-mode—ATM virtual circuit (VC) cell relay non-promiscuous modeatm-cell-vp-mode—ATM virtual path (VP) cell relay promiscuous modecisco-hdlc—Cisco Systems-compatible HDLCethernet—Ethernetethernet-vlan—Ethernet VLANframe-relay—Frame Relayinterworking—Layer 2.5 interworking VPNppp—PPPUsage Guidelines
See Configure the Encapsulation Type.
Required Privilege Level
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.See also