you can configure flexible Ethernet services encapsulation on the physical interface.
For interfaces with flexible-ethernet-services encapsulation, all VLAN IDs are valid.
VLAN IDs from 1 through 511 are not reserved.
•
For encapsulation types extended-vlan-ccc and extended-vlan-vpls, all VLAN IDs are
valid.
The upper limits for configurable VLAN IDs vary by interface type.
When you configure a TCC encapsulation, some modifications are needed to handle
VPN connections over unlike Layer 2 and Layer 2.5 links and terminate the Layer 2 and
Layer 2.5 protocol locally.
The router performs the following media-specific change:
•
ATM—Operation, Administration, and Maintenance (OAM) and Interim Local
Management Interface (ILMI) processing is terminated at the router. Cell relay is not
supported. The Junos OS strips all ATM encapsulation data from incoming frames
before forwarding them. For output, the next hop is changed to ATM encapsulation.
Example: Configuring the Encapsulation on a Physical Interface
Configure PPP encapsulation on a SONET/SDH interface. The second and third family
statements allow Intermediate System-to-Intermediate System (IS-IS) and MPLS to
run on the interface.
[edit interfaces]
so-7/0/0 {
encapsulation ppp;
unit 0 {
point-to-point;
family inet {
address 192.168.1.113/32 {
destination 192.168.1.114;
}
}
family iso;
family mpls;
}
}
Related
Documentation
• Configuring Interface Encapsulation on Logical Interfaces
505Copyright © 2017, Juniper Networks, Inc.
Chapter 16: Configuring Point-to-Point Protocol (PPP)
To Next Page
Loading...
Need help?
General
