This document describes the Nx Networks implementation of Frame Relay and how to configure it. It includes the following sections:
Frame Relay Overview
Frame Relay Manager (FRMGR)
Frame Relay LAN Emulation (FRLANE)
Frame Relay Virtual Circuit (FRVC)
Choosing Between FRLANE and FRVC
Frame Relay over ISDN
Displaying the Frame Relay Prompts
Configuring Frame Relay
FRMGR Commands
FRLANE Commands
FRVC Commands
Frame Relay Overview
Frame Relay (FR) lets you connect multiple LANs to a single high-speed WAN link using point-to-point virtual circuits. A virtual circuit is a logical connection between two sites. The FR network provides a number of virtual circuits that connect stations attached to the same Frame Relay network.
A Frame Relay network consists of the FR backbone, made up of FR switches, that provides the service. Typically, a public Frame Relay supplier offers the Frame Relay service. The router acts as the device that connects your LANs to the Frame Relay WAN.
Terminology
This document uses the following terminology.
Frame Relay Services
Like other Nx Networks WAN implementations, Frame Relay consists of a physical device and logical interfaces. Logical interfaces run over the physical device, and you can have multiple logical interfaces running over one physical device. In addition, multiple Frame Relay VCs can run over each logical interface.
The Frame Relay software provides a set of services made up of the following:
Frame Relay Manager (FRMGR), which manages the physical Frame Relay device, handles the connection to the Frame Relay switch, manages PVCs, and allows other Frame Relay services, FRLANE and FRVC, to run on the Frame Relay device.
Frame Relay LAN Emulation (FRLANE), which acts as a logical interface running over the Frame Relay device. An FRLANE interface looks like an Ethernet or Token Ring interface to protocols. Each FRLANE interface can have many PVCs.
Frame Relay Virtual Circuit (FRVC), which also acts as a logical interface running over the Frame Relay device. Each FRVC interface uses a single PVC.
Figure 1 Frame Relay Device With Two FRLANE Interfaces and One FRVC Interface

Frame Relay Features
Frame Relay provides the following features:
High throughput and low delay. Using the core aspects (error detection, addressing, and synchronization) of the Link Access Protocol, D-channel (LAPD) datalink protocol, FR eliminates all network layer (Layer 3) processing. By using only the core aspects, FR reduces the delay of processing each frame.
LAN Emulation. Using FRLANE, you can group many circuits onto one interface. FRLANE features include static or dynamic address mapping, multicast emulation, and protocol broadcast.
Single Virtual Circuit Mode. Using FRVC, the VC acts as a point-to-point connection to protocols that run over the VC.
PPP over FRVC. Frame Relay Virtual Circuits can send PPP traffic over the circuit using PPP over Frame Relay encapsulation specified in RFC 1973. Using this feature along with PPP data compression gives you a method of compressing data sent over the circuit.
Network management. As your network requires, Frame Relay can operate with or without a Local Management Interface (LMI).
Circuit access and control. As the router dynamically learns about nonconfigured circuits (orphan circuits), you can control access to those new circuits.
Congestion detection and control. Upon receiving Backward Explicit Congestion Notification (BECN), the router initiates a controlled slowdown of traffic, thereby avoiding a complete FR network shutdown.
1490 Encapsulation. The router encapsulates protocol packets as specified in RFC 1490.
Multiplexing Virtual Circuits. Frame Relay can pass multiple protocols over one circuit. OpenROUTE software supports IP, IPX, AppleTalk, and bridging.
Statistics. Frame Relay monitoring commands provide current statistics on circuits and LMI exchanges.
Figure 2 DLCIs in Frame Relay Network

Transports frames transparently. The network can modify only the DLCI, congestion bits, and frame check sequence. High-level Data Link Control (HDLC) flags and zero bit insertion provide frame delimiting, alignment, and transparency.
Detects transmission, format, and operational errors (frames with an unknown DLCI).
Preserves the ordering of frame transfer on individual VCs.
Does not acknowledge or retransmit frames.
Frame Relay Manager (FRMGR)
The FRMGR configuration applies to all logical interfaces that run over the physical Frame Relay device. FRMGR handles the following Frame Relay management tasks, which are described in the next sections.
PVC status, including whether a PVC is active or inactive or has been deleted. Through PVC status, FRMGR learns about orphan circuits. See Full Status Report.
The integrity of the physical link between the end station and the Frame Relay switch. See Link Integrity Verification Report.
Network congestion using FECN and BECN bit settings.
Figure 4 DLCIs in Frame Relay Network

Orphan Circuits
An orphan circuit is a virtual circuit that is not configured, but that FRMGR dynamically learns through LMI. For example, in Figure 5 router B has a configured PVC to router C, but none to router A. Router A configures a PVC to router B. Router B then learns about the PVC to router A and classifies it as an orphan.
Figure 5 Orphan Circuit

The router treats orphan circuits the same as configured circuits, except that you can enable or disable them. Enabling orphan circuits allows the router to forward packets over circuits you did not configure. Disabling orphan circuits adds a measure of security to your network by preventing unauthorized entry into your network from a nonconfigured circuit.
Management Status Reporting
Upon request, LMI provides two types of status reports, a full status report and a link integrity verification report. The next sections describe these reports. FR sends status enquiries and responses over DLCI 0 for ANSI Annex D and CCITT or DLCI 1023 for LMI Rev 1.
Enter list lmi at the FRMGR <WAN> prompt to see current status information.
Full Status Report
When FRMGR requires a full status report, it sends a status enquiry to management requesting a full status report. LMI responds with a full status report consisting of the link integrity verification element and the status of all PVCs on the device. (The next section describes the link integrity verification element.)
The PVC status contains the following information: the local DLCI number for the PVC; the state of the PVC (active or inactive); and whether the PVC is new or an existing PVC that management already knows about. Note:
The number of PVCs that LMI supplies to the FR device is restricted by the network frame size and the amount of individual PVC information elements that can fit into a full status report. For example, 202 is the maximum number of PVCs for a network with a 1K frame size.
This sets an error threshold of 3 (n2 = 3) and a window size of 4 (n3 = 4), which causes the software to check four management events to determine if any are in error. If the number of events in error equals three (the n2 parameter) or more, the Frame Relay device considers the network to be Down and resets. For the Frame Relay device to consider the network to be Up, the number of events in error within the window must be less than n2 prior to any change in status.FRMGR Config <WAN> set n2-parameter
Parameter N2 [3]?
FRMGR Config <WAN> set n3-parameter
Parameter N3 [4]?
Committed Information Rate (CIR)
CIR is the data rate that the FR service provider commits to support for both PVCs and orphan circuits under normal, uncongested conditions. The CIR is a portion of the total throughput for the physical link between 300 bits per second (bps) and 1.54 Megabits per second (Mbps). The most common CIR, and the default CIR, is 64 Kilobits per second (Kbps).
Orphan Circuit CIR
The router assigns orphan circuits a CIR of 64 Kbps. If you rely on an orphan circuit to route important data, you should add a PVC in place of the orphan. Doing so lets you assign a CIR that the network commits to support.
Committed Burst (Bc) Size
Bc is the maximum amount of data in bits that the network commits to deliver during a calculated time (Tc) interval. To calculate the Tc, divide the Bc by the CIR.
For example, if a VC's CIR is 9600 bps, and the Bc is 14,400 bits, the Tc is 1.5 seconds (14,400/9600 = 1.5 seconds). This allows the VC to transmit a maximum of 14,400 bits in 1.5 seconds. The Bc is important because of its relationship to the maximum frame size. If the maximum frame size in bits is greater than the Bc, the network may discard frames whose size exceeds the Bc. Therefore, make sure the Bc is greater than or equal to the maximum frame size. The default Bc is 64000 bits.Bc/CIR = Tc
Bc/CIR=Tc).
The network delivers this excess data with a lower probability of success than committed burst size data. Set the Be greater than zero only if you are willing to accept the risk of discarded data and its effect on higher-layer protocol performance.
The default Be is 0.
Tc=Bc/CIR) during periods of network congestion. Set the minimum IR using the set ir-adjustment command.The maximum IR is the maximum amount of data the router sends. You do not set the maximum IR; the router calculates the maximum IR using the CIR, Bc, and Be as follows:
(Bc + Be) / Tc = maximum IR
Circuit congestion is occurring.
The router is the sender of frames.
CIR monitoring or congestion monitoring is enabled.
Congestion Monitoring
Congestion monitoring allows the VIR to vary in response to network congestion. The VIR assumes values between the minimum IR and a maximum of line speed. Congestion monitoring is enabled by default. You can disable it with the disable congestion-monitor command.
CIR monitoring, if enabled, overrides congestion monitoring. If both CIR monitoring and congestion monitoring are disabled, the VIR for each VC on the device is set to the line speed and does not change in response to network congestion.
Congestion Notification and Avoidance
Frame Relay frames contain two bits that notify the device sending or receiving frames if there is congestion on the network. The two bits are
Forward Explicit Congestion Notification (FECN), which notifies devices receiving frames that congestion is occurring in the direction the frame is being sent.
Backward Explicit Congestion Notification (BECN), which notifies devices sending frames that congestion is occurring in the opposite direction.
Figure 6 shows a congestion condition at switch B. Management notifies the downstream node (switch C) and the end station (router) that congestion is occurring by setting the FECN bit on all outgoing frames. Management must also notify switch A and the other end station that congestion is occurring by setting the BECN bit.
Figure 6 Congestion Notification and Throttle Down

contains the DLCI that matches the protocol address, FR encapsulates that packet into a frame and sends the frame over the specified circuit.
does not contain a match, FR sends an ARP request over all of its configured PVCs. When the appropriate end point sends an ARP response, FR adds the local DLCI of the circuit that received the ARP response to the ARP cache.
Protocol Broadcast
Protocol broadcast allows protocols such as RIP to function over the FRLANE interface. The multicast parameter must be enabled for protocol broadcast to function properly. You can turn this feature on or off using the enable protocol-broadcast and disable protocol-broadcast FRLANE commands.
LAN Emulation Groups
LAN emulation groups allow an FRLANE interface to use only the VCs you configured for that FRLANE interface and not circuits that it learns about from FRMGR.
You may want to enable LAN emulation groups in either of the following situations:
If you have VCs on an FRLANE interface and want to prevent other FRLANE interfaces from using those VCs. Otherwise, if you have multiple FRLANE interfaces on one Frame Relay device, the first FRLANE to send a unicast frame on a circuit gets exclusive use of the circuit.
If you have a number of FRLANE interfaces on one device. Without LAN emulation groups, all FRLANE interfaces could send broadcasts to the FRMGR, and FRMGR could broadcast multiple copies of the same frame over the Frame Relay network.
Frame Relay Virtual Circuit (FRVC)
FRVC interfaces use a point-to-point connection over a single VC. You can have multiple FRVC interfaces on each physical Frame Relay device. Each FRVC has one VC. You can use FRVC interfaces over orphan circuits.
The router encapsulates IP, IPX, AppleTalk, and bridging packets using RFC 1490 encapsulation and then routes them over the FRVC interface.
You can also send PPP data over an FRVC. Using this feature along with PPP data compression gives you a method of sending compressed data over an FRVC. The router uses PPP over Frame Relay encapsulation specified in RFC 1973.
With FRVC, the VC acts as a point-to-point connection to protocols that run over the VC. For example, if you are using IP, you can run RIP or use static routes over the VC. You can also assign a different IP address to each FRVC interface, which allows you to set up separate IP filters for each FRVC.
FRVC responds to Inverse ARP requests that it receives.
Choosing Between FRLANE and FRVC
Consider the following when deciding whether to use FRLANE or FRVC.
FRVC
FRVC is the default configuration for Frame Relay devices. FRVC uses one VC for each FRVC interface, and it is simpler to set up than FRLANE.
FRVC causes a VC to act as a point-to-point connection to protocols. If you use FRVC, you can
assign different IP addresses to each VC
use RIP or static routes over the FRVC interface
enable PPP over FRVC, which lets you send compressed PPP data over your Frame Relay connection
Figure 7 Frame Relay Over ISDN Configuration

FRMGR unconditionally calls the Frame Relay switch when the router restarts even if you have dial-on-demand enabled. It does so because Frame Relay needs the status of PVCs.
You can set up FRMGR to disconnect from the Frame Relay switch if no upper-layer protocol requests a connection. (Use the set idle-timeout FRMGR configuration command.)
You can also set up FRMGR to periodically reconnect to the Frame Relay switch to update PVC status. (Use the set redial-timer FRMGR configuration command.)
Circuit Config <NET-#> prompt for the device you use to get to the FRMGR prompt.
To display the FR Manager configuration prompt (FRMGR Config <WAN>), Config> prompt, enter list interfaces to see a list of interfaces configured on the router.
Config>set data-link frame-relay
Interface Number [0]? 1
Config>network
What is the network number [0]? 1
Circuit Configuration
Circuit Config <NET-1>
Circuit Config <NET-1> frmgr
Frame Relay Manager Configuration
FRMGR Config <WAN>
FRMGR <WAN>), Monitor> prompt, enter list interfaces to see a list of interfaces configured on the router. Enter network followed by the number of the Frame Relay interface that you want to monitor.
Monitor>network 1
Circuit <NET-1>
Circuit <NET-1> frmgr
Frame Relay Manager Console
FRMGR <WAN>
FRMGR Config <WAN>),Config> prompt, enter list interfaces to see a list of interfaces configured on the router.
Config>set data-link frame-relay
Interface Number [0]? 1
Config>enable lan-emulation
Interface number [0]? 1
Config>network
What is the network number [0]? 1
Circuit Configuration
Circuit Config <NET-1>
Circuit Config <NET-1> frlane
Frame Relay LAN Emulation User Configuration
FRLANE Config <NET-1>
FLANE <NET-#>), Monitor> prompt, enter list interfaces to see a list of interfaces configured on the router. Enter network followed by the number of the Frame Relay interface that you want to monitor.
Monitor>network 1
Circuit <NET-1>
Circuit <NET-1> frlane
Frame Relay LAN Emulation Console
FRLANE <NET-1>
FRVC <NET-#>), Monitor> prompt, enter list interfaces to see a list of interfaces configured on the router.
Monitor>network 1
Circuit <NET-1>
Circuit <NET-1> frvc
Frame Relay Virtual Circuit Console
FRVC <NET-1>
And/Or
The next sections describe each of these tasks. Once you finish configuring Frame Relay, restart the router for your configuration to take effect.
Frame Relay Worksheet
To configure Frame Relay, you need the following information. Your Frame Relay provider or network administrator can give you this information.
Configuring Frame Relay Manager
Follow these steps to configure the Frame Relay Manager (FRMGR).
FRMGR Config <WAN> prompt.
FRMGR Config <WAN> add permanent-virtual-circuit
Circuit number [16]?
Committed Information Rate (CIR) in bps [64000]?
Committed Burst Size (Bc) in bits [64000]?
Excess Burst Size (Be) in bits [0]?
Assign circuit name? rochester
FRMGR Config <WAN> set lmi-type rev1
| Parameter | Default |
|---|---|
| Cable Type* | RS-232 DTE |
| Clocking* | External |
| Encoding | NRZ |
| Frame size | 2048 bytes |
| Idle | Flag |
| Speed | 64,000 bps |
| Transmit delay | 0 |
* Not configurable on all platforms. Some platforms automatically detect the cable type and set clocking to internal or external. To set these parameters, enter sl at the circuit configuration prompt, and then use the set hdlc commands.
Circuit Config <NET-1> sl
Serial Line Configuration
Serial Config <WAN> set hdlcSpace
The choices/prefixes are (a complete list):
CABLE
CLOCKING
ENCODING
FRAME-SIZE
IDLE
SPEED
TRANSMIT-DELAY
BRI Config <WAN>.You can also use the set idle-timeout and set redial-timer commands to control connections to the Frame Relay switch.FRMGR Config <WAN2-1> set switch-address-name
Assign switch address name? rochester
For information on how to set up ISDN, see Using the ISDN Interface.
Configuring Frame Relay LAN Emulation
Follow these steps to configure FRLANE.
Config>add interface frame-relay
Adding interface 2 linked to base device WAN.
Config>enable lan-emulation
Interface number [0]? 1Config>enable lan-emulation
Interface number [0]? 2
FRLANE Config <NET-#> prompt.
To run IPX or bridging over the FRLANE interface, in the FRMGR configuration, add a PVC that has the same number as the circuit you add here and optionally assign a name to the PVC.
FRLANE Config <NET-1> add circuit
Circuit number [16]?
Is circuit required for interface operation? [N]?
FRLANE Config <NET-1> enable lane-group
FRLANE Config <NET-1> add protocol-address
Protocol name or number [IP]?
IP Address [0.0.0.0]? 10.1.65.3
Config>add interface frame-relay
Adding interface 2 linked to base device WAN.
Config>disable lan-emulation
Interface number [0]? 2
Config>network
What is the network number [0]? 2
Circuit Configuration
Circuit Config <NET-2> set destination
Assign destination address name []? rochester
Running PPP over FRVC
You can optionally set up an FRVC to send PPP data over the FRVC. By also enabling PPP data compression, you can compress the data that the router sends over the FRVC. To use PPP over FRVC, enable it at the configuration prompt and then set up PPP as you normally would.
Note: Make sure you also enable PPP over FRVC on the remote router to which this FRVC connects.Config>enable ppp-over-frvc
Interface Number [0]? 2
Circuit Config <NET-#> prompt for the device you use to get to the FRMGR prompt.
Press Space twice after you type a command to display the available options for each command. Enter help for information about using the command line interface.
[C] means the command is available at the FRMGR Config <WAN> prompt.
[M] means the command is available at the FRMGR <WAN> prompt.
Add [C]
Adds a PVC to the FRMGR configuration. Add a PVC if you
have disabled LMI,
do not want to use orphan circuits to a specific destination,
need to change the default information rates for a circuit, or
are running IPX or bridging over an FRLANE interface. In this case, you must either
assign a name to the PVC that you add here and use that name when you set up IPX or bridging, or
use the circuit number that you add here in your IPX or bridging configuration.
In the FRLANE configuration, you also need to add a circuit that has the same number as the PVC you add here. See add circuit.
add permanent-virtual-circuit
Circuit Number [16]?
Committed Information Rate (CIR) in bps [64000]?
Committed Burst Size (Bc) in bits [64000]?
Excess Burst Size (Be) in bits [0]?
Assign Circuit name []?
Change [C]
Changes the configuration of PVCs.
Syntax: change
change permanent-virtual-circuit
Circuit Number [16]?
Committed Information Rate in bps [64000]?
Committed Burst Size (Bc) in bits [64000]?
Excess Burst Size (Be) in bits [0]?
Assign Circuit Name: []?
Monitor> prompt.
Syntax: clear
Example: clear
delete permanent-virtual-circuit
Circuit number [16]? 20
disable cir-monitor
disable congestion-monitor
FRMGR Config <WAN> prompt.Note:
Disabling LMI allows for normal operation or end-to-end Frame Relay testing in the absence of a real network or management interface. For end-to-end Frame Relay testing, add PVCs on both ends of the link and assign the same circuit number to them.
Example: disable lmi
FRMGR Config <WAN> prompt.
Example: disable orphan-circuits
Example:
enable cir-monitor congestion-monitor
Enables congestion monitoring, which allows a circuit's information rate to vary in response to network congestion. The default is enabled.
See Congestion Monitoring.
Example:
enable congestion-monitor lmi
Enables management activity. The default is LMI ANSI enabled. Use enable lmi to resume LMI management if you previously disabled LMI.
To change the management type, use the set set lmi-type command
This command is available only at the
FRMGR Config <WAN> prompt.
Example: enable lmi orphan-circuits
Allows FRMGR to use orphan circuits, which is the default. The CIR of orphan circuits is 64000 bps, the committed burst (Bc) size is 64000 bps, and the excess burst (Be) size is 0.
This command is available only at the FRMGR Config <WAN> prompt.
Example: enable orphan-circuits Exit [C] [M]
Returns to the previous prompt.
Syntax: exit
exit
Circuit Config <NET-1>
list lmi
Frame Relay LMI Configuration
LMI enabled = Yes LMI DLCI = 0
LMI type = ANSI LMI Orphans OK = Yes
Congestion monitoring = Yes CIR monitoring = No
PVCs P1 allowed = 64 CIR monitor adjustment = 1
Timer T1 seconds = 10 Counter N1 increments = 6
LMI N2 error threshold = 3 LMI N3 error threshold window = 4
MIR % of CIR = 25 IR % increment = 12
IR % decrement = 25 Redial timer = 0
Idle timeout = 0
Switch address name = seattle
permanent-virtual-circuits
Displays all PVCs configured on the FRMGR.
Example: list permanent-virtual-circuit
Maximum PVCs allowable = 64
Total PVCs configured = 2
Circuit Circuit Circuit CIR Burst Excess
Name Number Type in bps Size Burst
-------------------- ------- ------- ------ ----- -----
houston 16 Permanent 64000 64000 0
portland 32 Permanent 64000 64000 0
List [M]
Displays statistics and configuration information.
Syntax: list
list circuit
Circuit number [16]?
Circuit name = houston
Circuit state = Idle Circuit is orphan = No
Frames transmitted = 0 Bytes transmitted = 0
Frames received = 0 Bytes received = 0
Total FECNs = 0 Total BECNs = 0
Times congested = 0 Times Inactive = 0
CIR in bits/second = 9600 Current Info Rate = 9600
Committed Burst (Bc) = 64000 Excess Burst (Be) = 0
Xmit frames dropped due to queue overflow = 0
lmi
Displays statistics and configuration information related to the logical management of the Frame Relay device.
Example: list lmi
Management Status:
------------------
LMI state = Initial
LMI enabled = Yes LMI DLCI = 0
LMI type = ANSI LMI orphans OK = Yes
LMI sequence interval seconds = 10
Congestion monitoring = Yes CIR monitoring = No
PVCs P1 allowed = 64 Interface MTU in bytes = 2048
Line access rate bps = 9600 CIR monitor adjustment = 1
Timer T1 seconds = 10 Counter N1 increments = 6
LMI N2 threshold = 3 LMI N3 threshold window = 4
MIR % of CIR = 25 IR % increment = 12
IR % decrement = 25 Redial timer = 0
Idle timeout = 0
Switch address name =
Current receive sequence = 0
Current transmit sequence = 0
Total status enquiries = 0 Total status responses = 0
Total sequence requests = 0 Total responses =
PVC Status:
-----------
Total allowed = 64 Total configured = 1
Total active = 0 Total congested = 0
Total left net = 0 Total join net = 0
permanent-virtual-circuits
Shows the circuits that FRMGR knows about, either PVCs or orphan circuits.
Example: list permanent-virtual-circuits
Orphan Type/ Frames Frames
Circuit# Circuit Name Circuit State Transmitted Received
-------- ------------------------ ------- ----- ----------- ----------
16 houston No P/I 0 0
A - Active I - Inactive R - Removed
P - Permanent M - Multicast C - Congested
Remove [C]
Deletes PVCs from the FRMGR configuration.
Syntax: remove
remove permanent-virtual-circuit
Circuit number [16]? 20
set idle-timeout
Idle timeout in seconds (1-65535) [60]?
IR adjustment % increment [12]?
IR adjustment % decrement [25]?
Minimum IR as % of CIR [100]?
Example:
set lmi-type ansi n1-parameter
Sets the number of T1 timer intervals that must expire before Frame Relay makes a complete PVC status enquiry. The range is 5 to 30. The default is 2.
Example: set n1-parameter
Parameter N1 [2]?
The range is 1 to 10. The default is 3. Set this parameter less than or equal to the n3-parameter.
Example:
set n2-parameter
Parameter N2 [3]?
Parameter N3 [4]?
set p1-parameter
Parameter P1 [64]?
set redial-timer
Redial timer in seconds (0-65535, 0 means no redial) [0]?
BRI Config <WAN>.
Example: set switch-address-name
Assign switch address name? seattle
set t1-parameter
Parameter T1 [10]?
set circuit
Circuit Number [16]?
Committed Information Rate in bps [64000]?
Committed Burst Size (Bc) in bits [64000]?
Excess Burst Size (Be) in bits [0]?
set ir-adjustment
IR adjustment % increment [12]?
IR adjustment % decrement [25]?
Minimum IR as % of CIR [100]?
Space twice after you type a command to display the available options for each command. Enter help for information about using the command line interface.
[C] means the command is available at the FRLANE Config <NET-#> prompt.
[M] means the command is available at the FRLANE <NET-#> prompt.Note:
To display these prompts, you must first enter enable lan-emulation at the Config> prompt.
Add [C]
Adds a circuit or destination protocol address.
Syntax: add
add circuit
Circuit Number [16]?
Is circuit required for interface operation? [N]?
This parameter prompts you for different information depending on the type of protocol address you are adding.
Example:
add protocol-address
Protocol name or number [IP]?
IP Address [0.0.0.0]?
Circuit number [16]?
Host Number (in hex)[]?
Circuit number [16]?
Network number (1-65279) []?
Node number (1-253) []?
Circuit number [16]?
Change [C]
Changes circuits or protocol addresses that were added with the add command.
Syntax: change
change circuit
Circuit number [16]?
Is circuit required for interface operation? [N]? y
change protocol-address
Protocol name or number [IP]?
IP Address [0.0.0.0]? 128.185.10.2
Circuit number [16]?
clear
delete circuit
Circuit number [16]?
delete protocol-address
Protocol name or number [IP]?
IP Address [0.0.0.0]? 128.185.10.2
Circuit number [16]?
disable lane-group
disable multicast-emulation
disable protocol-broadcast
disable no-pvc
enable lane-group
enable multicast-emulation
enable protocol-broadcast
enable no-pvc
Circuit Config <NET-1>
list circuits
Frame Relay LAN Emulation Configured Circuits
Circuit# Required
-------- --------
16 No
list lane
Frame Relay LAN Emulation Configuration
LANE emulation group = Disabled
Protocol broadcast = Yes Multicast emulation = No
Down if no circuits = No
list protocol-addresses
Frame Relay Protocol Address Translations
Protocol Type Protocol Address Circuit Number
------------- ---------------- --------------
IP 128.185.10.2 16
|
Protocol Type
| The name of the protocol running over the interface. |
|
Protocol Address
| The address of the protocol running over the interface. |
|
Circuit Number
| The VC that is running the protocol. |
List [M]
Displays statistics and configuration information for FRLANE circuits.
Syntax: list
list all
Frame Relay LAN Emulation
State = Up
LAN emulation group = Disabled
Protocol broadcast = No Emulate multicast = Yes
Down if no circuits = No
Active circuits = 0 Total circuits = 1
Type/ Frames Frames
Circuit# Circuit Name State Transmitted Received
-------- ------------------------ ------ ----------- ----------
16 houston S/I 0 0
D - Dynamic S - Static * - Required
A - Active I - Inactive
circuits
Displays statistics for the circuit that you specify.
Example: list circuit
Circuit number [16]?
Circuit name = houston
Circuit state = Inactive
Frames transmitted = 0 Bytes transmitted = 0
Frames received = 0 Bytes received = 0
Remove [C]
Deletes circuits or protocol addresses that you added with the add command.
Syntax: remove
remove circuit
Circuit number [16]?
remove protocol-address
Protocol name or number [IP]?
IP Address [0.0.0.0]? 128.185.10.2
Circuit number [16]?
Space twice after you type a command to display the available options for each command. Enter help for information about using the command line interface.
There is no configuration prompt for FRVC.
[M] means the command is available at the FRVC <NET-#> prompt.
| Command | Function |
|---|---|
| Clear [M] | Resets all statistics for Frame Relay Virtual Circuits. |
| Exit [M] | Returns to the previous prompt. |
| List [M] | Displays statistics for the virtual circuit. |
Clear [M]
Clears all statistics for Frame Relay Virtual Circuits.
Syntax: clear
clear
exit
Circuit <NET-1>
list
Frame Relay Virtual Circuit
Circuit name =
State = Down
Frames transmitted = 0 Bytes transmitted = 0
Frames received = 0 Bytes received = 0