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

Network interfaces configuration
Table of Contents

Advertisement

JUNOS 10.1 Network Interfaces Configuration Guide
NOTE: When the encapsulation type is set to Cisco-compatible Frame Relay
encapsulation, ensure that the LMI type is set to ANSI or Q933-A.
To configure the encapsulation on a physical interface, include the
statement at the
When you configure a point-to-point encapsulation (such as PPP or Cisco HDLC) on
a physical interface, the physical interface can have only one logical interface (that
is, only one
encapsulation (such as Frame Relay), the physical interface can have multiple logical
units, and the units can be either point to point or multipoint. Use PPP if you are
running Cisco IOS Release 12.0 or later. If you need to run Cisco HDLC, the JUNOS
Software automatically configures an ISO family MTU of 4469 in the router. This is
due to an extra byte of padding used by Cisco.
934
Configuring Interface Encapsulation on SONET/SDH Interfaces
TCC version (
cisco-hdlc-tcc
restrictions, but used for circuits with different media on either side of the
connection.
Frame Relay—Defined in RFC 1490, Multiprotocol Interconnect over Frame Relay.
E1, E3, SONET/SDH, T1, and T3 interfaces can use Frame Relay encapsulation.
Two related versions are supported:
CCC version (
frame-relay-ccc
0 through 511. DLCIs 512 through 1022 are dedicated to CCC. This
numbering restriction does not apply to IQ and IQE interfaces. The logical
interface must also have
TCC version (
frame-relay-tcc
configuration restrictions, but used for circuits with different media on either
side of the connection.
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
numbering restriction does not apply to IQ and IQE interfaces. This
encapsulation is used for circuits with different media on either side of the
connection.
Extended TCC version (
allows you to dedicate Cisco-compatible Frame Relay TCC for DLCIs 1 through
1022. This encapsulation is used for circuits with different media on either
side of the connection. All ether type TCC encapsulation is supported on the
same PICs as non-ether type Frame Relay TCC encapsulation.
[edit interfaces interface-name]
[edit interfaces interface-name]
encapsulation (cisco-hdlc | cisco-hdlc-ccc | cisco-hdlc-tcc | frame-relay | frame-relay-ccc |
frame-relay-tcc | frame-relay-tcc | ppp | ppp-ccc | ppp-tcc);
statement) associated with it. When you configure a multipoint
unit
)—Similar to CCC and has the same configuration
)—The same as standard Frame Relay for DLCIs
encapsulation.
frame-relay-ccc
)—Similar to Frame Relay CCC and has the same
frame-relay-ether-type
)—Physical interfaces can use
)—Cisco-compatible Frame Relay for
extended-frame-relay-ether-type-tcc
hierarchy level:
)—This encapsulation
encapsulation

Advertisement

Table of Contents
loading

This manual is also suitable for:

Junos 10.1

Table of Contents