Juniper JUNOS 10.1 - CONFIGURATION GUIDE 1-2010 Configuration Manual page 191

Ethernet services encapsulation on the physical interface, VLAN IDs from
1 through 511 are no longer reserved for normal VLANs.
Flexible Frame Relay (
flexible-frame-relay
Frame Relay encapsulation. You use flexible Frame Relay encapsulation when
you want to configure multiple per-unit Frame Relay encapsulations. This
encapsulation type allows you to configure any combination of TCC, CCC, and
standard Frame Relay encapsulations on a single physical port. Also, each logical
interface can have any data-link connection identifier (DLCI) value from
1 through 1022.
Frame Relay ( )—Defined in RFC 1490, Multiprotocol Interconnect over
frame-relay
Frame Relay. E1, E3, link services, SONET/SDH, T1, T3, and voice services
interfaces can use Frame Relay encapsulation. Five related versions are supported:
CCC version ( frame-relay-ccc
0 through 511. DLCIs 512 through 1022 are dedicated to CCC. The logical
interface must also have
encapsulation type, you can configure the
TCC version (
frame-relay-tcc
configuration restrictions, but used for circuits with different media on either
side of the connection.
Extended CCC version (
allows you to dedicate DLCIs 1 through 1022 to CCC. The logical interface
must have
frame-relay-ccc
type, you can configure the
Extended TCC version (
Relay CCC, this encapsulation type allows you to dedicate DLCIs 1 through
1022 to TCC, which is used for circuits with different media on either side
of the connection.
Port CCC version (
frame-relay-port-ccc
Relay Encapsulation over Pseudo-Wires (expired December 2002). This
encapsulation type allows you to transparently carry all the DLCIs between
two customer edge (CE) routers without explicitly configuring each DLCI on
the two provider edge (PE) routers with Frame Relay transport. The
connection between the two CE routers can be either user-to-network
interface (UNI) or network-to-network interface (NNI); this is completely
transparent to the PE routers. The logical interface does not require an
encapsulation statement. When you use this encapsulation type, you can
configure the ccc family only.
Frame Relay Ether Type (
Frame Relay ether type encapsulation for compatibility with Cisco Frame Relay.
IETF frame relay encapsulation identifies the payload format using NLPID and
SNAP formats. Cisco-compatible Frame Relay encapsulation uses the Ethernet
type to identify the type of payload. Two related versions are supported:
TCC version ( frame-relay-ether-type-tcc
DLCIs 0 through 511. DLCIs 512 through 1022 are dedicated to TCC. This
encapsulation is used for circuits with different media on either side of the
connection.
Configuring Interface Encapsulation on Physical Interfaces
Chapter 3: Configuring Physical Interface Properties
)—IQ and IQE interfaces can use flexible
)—The same as standard Frame Relay for DLCIs
encapsulation. When you use this
frame-relay-ccc
ccc family only.
)—Similar to Frame Relay CCC and has the same
extended-frame-relay-ccc
encapsulation. When you use this encapsulation
ccc family only.
)—Similar to extended Frame
extended-frame-relay-tcc
)—Defined in the IETF document Frame
)—Physical interfaces can use
frame-relay-ether-type
)—Cisco-compatible Frame Relay for
)—This encapsulation type
121