Configuring Frame Relay

crc

• Use to set the number of bits used for CRC.
• The CRC is an error-checking technique that uses a calculated numeric value to detect errors in transmitted data.
• 16 and 32 indicate the number of bits per frame that are used to calculate the frame check sequence (FCS).
• A 32-bit CRC transmits longer streams at faster rates and therefore provides better ongoing error detection, such as for an OC12/STM4 POS module.
• The default is 16. You must configure CRC (CRC16 or CRC32) to match the configuration on the other side of the Frame Relay connection.
• Example
  host1(config-if)#crc 32
• Use the no version to set the CRC to the default value.
• See crc.

encapsulation frame-relay ietf

• Use to specify Frame Relay as the encapsulation method for the interface.
• The router uses IETF format (RFC 2427 encapsulation).
• Example
  host1(config-if)#encapsulation frame-relay ietf
• Use the no version to remove Frame Relay configuration from an interface.
• See encapsulation frame-relay ietf.

frame-relay description

• Use to assign a text description or an alias to a Frame Relay interface or subinterface.
• You can use this command to help you identify the interface and keep track of interface connections.
• The description or alias can be a maximum of 80 characters.
• Use show frame-relay interface or show frame-relay subinterface to display the text description.
• Examples
  host1(config-if)#frame-relay description boston01 host1(config-subif)#frame-relay description toronto011
• Use the no version to remove the text description or alias.
• See frame-relay description.

frame-relay interface-dlci ietf

• Use to configure a Frame Relay permanent virtual circuit (PVC) over a subinterface.
• The ietf keyword is mandatory and indicates RFC 2427 encapsulation.
• Define a DLCI in the range 16–1007.
• To configure a Frame Relay PVC, you must specify a DLCI.
• Frame Relay service is offered in the form of PVCs. A PVC is a data-link connection that is predefined on both ends of the connection. A network operator assigns the endpoints of the circuit. Although the actual path taken through the network may vary from time to time, the beginning and end of the circuit do not change. This type of circuit behaves like a dedicated point-to-point circuit.
• PVCs are identified by DLCIs. A DLCI is a 10-bit channel number that is attached to data frames to tell a Frame Relay network how to route the data. Frame Relay is statistically multiplexed, which means that only one frame can be transmitted at a time, but many logical connections can coexist on a single physical line. The DLCI allows the data to be logically tied to one of the connections, so that when the data gets to the network, the network knows where to send it.
• DLCIs on the same physical line must match. However, DLCIs have local significance; that is, if the DLCIs are not on the same physical line, the end devices at two different ends of a connection may use a different DLCI to refer to the same connection.
• The router does not support switched virtual circuits (SVCs). An SVC is an any-to-any connection that can be established or removed as needed. With SVCs, you initiate calls using Frame Relay by requesting a destination address and assigning a DLCI, which is established for the duration of the call.
• Example
  host1(config-subif)#frame-relay interface-dlci 17 ietf
• Use the no version to remove DLCI/PVC assignment.
• See frame-relay interface-dlci ietf.

frame-relay intf-type

• Use to configure a Frame Relay interface circuit to operate as data communications equipment (DCE), data terminal equipment (DTE), or NNI.
• Frame Relay provides packet-switching data communications between user devices and network equipment across the interface. User devices are referred to as DTE.
• Network equipment that interfaces with a DTE is referred to as a DCE.
• NNI provides a connection between two Frame Relay subnetworks.
• If your router is connected to a Frame Relay switch, configure the interface as a DTE. If your router is connected by a point-to-point line, configure one end as the DTE and the other as the DCE.
• Example
  host1(config-if)#frame-relay intf-type dte
• Use the no version to set the default of DTE.
• See frame-relay intf-type.

frame-relay keepalive

• Use to enable the LMI on the interface.
• You can specify the keepalive interval in seconds.
• Make sure the value on the DTE is less than the value set on the DCE.
• The default is 10 seconds.
• Example
  host1#no frame-relay keepalive
• Use the no version to disable LMI on the interface.
• See frame-relay keepalive.

frame-relay lmi-n391dte

frame-relay lmi-n392dce

frame-relay lmi-n392dte

frame-relay lmi-n393dce

frame-relay lmi-n393dte

frame-relay lmi-t391dte

frame-relay lmi-t392dce

• Use to configure LMI counters and timers.
• LMI counters and timers have configurable ranges that allow you to control the state of the Frame Relay interface. In general, accept the default values for the timers and counters, unless you need to modify them according to a special arrangement with your customers.
• Some commands have DTE and DCE versions. Use the dte version of the command if the interface is operating as a DTE. Use the dce version of the command if the interface is operating as a DCE. Use both versions of the command if the interface is operating as an NNI.
• Use the frame-relay lmi-n391dte command to set the N391 full-status polling counter. When you set this counter to a number, n, the nth request is a full-status request. The range is 1–255 event messages. The default is 6 event messages.
• Use the frame-relay lmi-n392dte or frame-relay lmi-n392dce command to set the N392 error threshold counter, which specifies the number of errors within N393 events that will place the interface in an operationally down state. The range is 1–10. The default for the DTE version is 3. The default for the DCE version is 2.
• Use the frame-relay lmi-n393dte or frame-relay lmi-n393dce command to set the N393 monitored events counter to specify the diagnostic window used to verify link integrity. Detection of N392 errors within the window of N393 samples places the interface in an operationally down state. The range is 1–10 events. The default for the DTE version of the command is 4 events. The default for the DCE version is 2 events.
• Use the frame-relay lmi-t391dte command to set the T391 link integrity polling timer interval between status inquiries issued by the DTE. The network checks that the DTE polls within the verification interval, T392. The range is 5–30 seconds. The default is 10 seconds.
• Use the frame-relay lmi-t392dce command to set the T392 polling verification timer that specifies the maximum interval (in seconds) between the receipt of status inquiries from the DTE equipment before it considers it as an error event. The range is 5–30 seconds. The default is 15 seconds.
• Example
  host1(config-if)#frame-relay lmi-n391dte 20
• Use the no version to remove the current setting and set the default.
• See frame-relay lmi-n391dte.
• See frame-relay lmi-n392dce.
• See frame-relay lmi-n392dte.
• See frame-relay lmi-n393dce.
• See frame-relay lmi-n393dte.
• See frame-relay lmi-t391dte
• See frame-relay lmi-t392dce

frame-relay lmi-type

• Use to configure one of the local management interface types.
• LMI provides configuration and status information relating to the virtual circuits operating over Frame Relay.
• LMI specifies polling mechanisms to receive incremental and full-status updates from the network.
• E Series routers conform to the following LMI specifications:
  • ansi—ANSI T1.617 Annex D
  • q933a—ITU-T Q.933 Annex A
  • cisco—Original Group of Four specification developed by DEC, Northern Telecom, Stratacom, and Cisco
  • none—Suppresses LMI
• The default is cisco.
• Example
  host1(config-if)#frame-relay lmi-type ansi
• Use the no version to return to the default LMI type.
• See frame-relay lmi-type.

interface pos

• Use to configure a POS interface in slot/port format:
  • slot—Router chassis slot
  • port—Line module port
• Example
  host1(config)#interface pos 0/1
• Use the no version to remove the POS interface.
• See interface pos.

interface serial

• Use to configure a serial interface in the appropriate format by selecting a previously configured physical interface on which you want to configure Frame Relay. For example, for a channelized T3 interface use slot/port:channel/subchannel.
• Use to configure a Frame Relay subinterface in the appropriate format by selecting a previously configured physical interface. For example, for a T3-Frame interface use slot/port.subinterface ; for a channelized T1/channelized E1 interface use slot/port.channel-group.subinterface.

  Note: Before you configure Frame Relay, see the appropriate chapter in this guide for details on configuring physical interfaces.

  • slot—Router chassis slot
  • port—CT3, T3, or E3 module I/O port
  • channel—T1 (DS1) channel
  • subchannel—Set of DS0 timeslots. See section Fractional T1 in JunosE Physical Layer Configuration Guide
  • subinterface—User-assigned nonnegative number that identifies a Frame Relay subinterface
• Example
  host1(config-if)#interface serial 3/1:2/1.1
• Use the no version to remove the subinterface or the serial interface.
• See interface serial.

ip address

• Use to assign an IP address and subnet mask to a subinterface.
• Example
  host1(config-subif)#ip address 192.32.10.2 255.255.255.0
• Use the no version to remove an IP address or to disable IP processing.
• See ip address.

pos description

• Use to assign a text description or an alias to a POS HDLC interface.
• You can use this command to help you identify the interface and keep track of interface connections.
• The description or alias can be a maximum of 80 characters.
• Use show interfaces pos to display the text description. For details, see Monitoring POS in Configuring Packet over SONET.
• Example
  host1(config-if)#pos description austin01 pos interface
• Use the no version to remove the text description or alias.
• See pos description.

serial description

• Use to assign a text description or an alias to a serial HDLC interface.
• You can use this command to help you identify the interface and keep track of interface connections.
• The description or alias can be a maximum of 80 characters.
• Use the show interfaces serial command to display information about the serial interfaces you configured. For more information about the descriptions of the fileds displayed in the output of this command, see the show interfaces serial section in JunosE Physical Layer Configuration Guide. For example, for a channelized T3 interface, see the Monitoring Interfaces section in JunosE Physical Layer Configuration Guide.
• Example
  host1(config-if)#serial description ottawa012 hdlc channel
• Use the no version to remove the text description or alias.
• See serial description.

shutdown

• Use to disable a Frame Relay interface.
• Example
  host1(config-if)#shutdown
• Use the no version to restart a disabled interface.
• See shutdown.

snmp trap frame-relay link-status

• Use to enable SNMP link status processing for a Frame Relay major interface or subinterface.
• To enable SNMP link status processing for a Frame Relay major interface, you must issue the command from Interface Configuration mode.
• To enable SNMP link status processing for a Frame Relay subinterface, you must issue the command from Subinterface Configuration mode.
• Examples
  host1(config-if)#snmp trap frame-relay link-status host1(config-subif)#snmp trap frame-relay link-status
• Use the no version to disable SNMP link status processing for a Frame Relay major interface or subinterface.
• See snmp trap frame-relay link-status.