
T1/E1 WAN Configuration Guide Configuring Layer 2 Protocols (Frame Relay, PPP, HDLC)
61200860L1-29.6A Copyright © 2005 ADTRAN, Inc. 5
Configuring Layer 2 Protocols (Frame Relay, PPP, HDLC)
Each WAN connection in your AOS product must contain a physical interface (T1, E1, ADSL, etc.) and a
Layer 2 protocol (ATM, frame relay/multilink frame relay, PPP/multilink PPP, or HDLC). The physical
interface provides the actual bandwidth between your device and the network provider. The Layer 2
protocol defines how the data is packaged and presented on the physical interface. Layer 2 protocols must
be configured to match the protocol provided on the circuit. For example, configuring the
AOS product for PPP operation on a frame relay circuit would not be successful.
AOS currently supports the following Layer 2 protocols for T1/E1 physical links:
• frame relay, including multilink frame relay (FRF.16)
• point-to-point protocol (PPP), including multilink PPP
• high-level data link control (HDLC) protocol
Configuring the Frame Relay Interfaces (and Sub-Interfaces)
There are two settings to consider when configuring frame relay interfaces. The interface type
(frame-relay intf-type) and signaling type (frame-relay lmi-type) must be configured to match the
specifications supplied on your frame relay circuit by your network provider. By default, all NetVanta
frame relay interfaces are configured as a DTE interface (frame-relay intf-type dte) with Annex D
signaling (frame-relay lmi-type ansi).
Frame relay interfaces have a sub-interface component for each PVC which must also be configured. Each
frame relay sub-interface contains a DLCI (frame-relay interface-dlci) and IP address (ip address). You
must manually configure the frame relay sub-interface DLCI and IP address because there are no default
DLCIs or IP addresses defined. Access policies are also applied at the sub-interface level (see Creating
Access Lists and Policies on page 9).
Each PVC should also have a configured committed burst value (frame-relay bc) which is equivalent to
the committed information rate (CIR) given to you by your network provider. PVCs will also have a
negotiated burst rate (frame-relay be) which is equivalent to the excess information rate (EIR) given to
you by your network provider. Both the CIR and EIR should be decided on by you and your service
provider when defining your service agreement. To determine the appropriate committed burst value and
EIR, you need to know the CIR and physical bandwidth for both the local and remote connections. If one
side transmits data at a rate much higher than the other side’s CIR (or physical bandwidth), packets will be
dropped causing a decrease in efficiency. A general rule is to provision the committed burst value with the
remote side CIR and configure the EIR with the difference between the CIR and the actual physical
bandwidth at the location. The committed burst value plus the EIR should not be greater than the physical
bandwidth.
The following commands specify the configuration parameters required for a standard frame relay
interface:
>enable
#config terminal
(config)#interface fr 1
(config-fr 1)#no shutdown
(config-fr 1)#exit
Comentarios a estos manuales