This chapter describes the Frame Relay configuration and operational commands and includes the following sections:
Notes:
This section describes the Frame Relay configuration commands. Enter all commands at the Frame Relay n> prompt, where n represents the interface number. You must restart the router for new configuration changes to take effect. Table 71 shows the commands. To access the Frame Relay n> prompt, perform the following steps:
Config> net 2 Frame Relay user configuration FR 2 Config>
Table 71. Frame Relay Configuration Commands Summary
| Command | Function |
|---|---|
| ? (Help) | Displays all the commands available for this command level or lists the options for specific commands (if available). See "Getting Help". |
| Add | Adds PVCs, Required PVC groups, SVCs, and destination protocol addresses to the Frame Relay interface. |
| Change | Modifies a PVC, SVC, or Required PVC group previously defined by the add command. |
| Disable | Disables any enabled Frame Relay features. |
| Enable | Enables Frame Relay features such as circuit monitoring, management options, multicast, protocol-broadcast, fragmentation, and orphans. |
| List | Displays the current configuration of the LMI, PVCs, Required PVC groups, SVCs, HDLC information, and protocol addresses. |
| LLC | Configures LLC parameters on the Frame Relay interface. These LLC parameters are required when running APPN over the Frame Relay interface. |
| Remove | Deletes any previously added PVCs, SVCs, or required PVC groups (if empty), or protocol addresses. |
| Set | Configures the Frame Relay management options and parameters (N1-parameter, N2-parameter, N3-parameter, P1 parameter, and T1-parameter). Configures the physical-layer parameters for FR serial interfaces. Sets the maximum frame size. |
| Exit | Returns you to the previous command level. See "Exiting a Lower Level Environment". |
| Note: | In this section, the terms circuit number and PVC are synonymous with the term DLCI (Data Link Circuit Identifier). |
Use the add command to add a circuit, required PVC group, or destination protocol address supported by the Frame Relay interface.
Syntax:
Example:
FR 4 config> add frame-handler-pvc 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 []? Network number of FH partner PVC [0]? Circuit number of FH partner PVC [16]? Maximum outbound queue depth (in number of packets) [10]? 1
Valid Values: 16 to 1007. The circuit number must be unique with respect to all other PVCs and FH PVCs on this interface and all associated subinterfaces.
| Note: | The default value is determined according to the CIR defaults set at the interface level. |
| Note: | The default value is determined according the Bc defaults set at the interface level. |
| Note: | The default value is determined according to the Be defaults set at the interface level. |
Valid Values: 5 to 100
Default Value: 10
Adds a PVC to the Frame Relay interface beyond the reserved range 0 through 15. The maximum number of PVCs that can be added is approximately 992, but the actual number of PVCs that the interface can support depends upon these conditions:
Example:
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 []? Is circuit required for interface operation [N]?y Does the circuit belong to a required PVC group [N]? y What is the group name []? group1 Do you want to have data compression performed [Y]? Do you want to have end-to-end fragmentation performed [Y]? Fragment size (50 to 8190)[256]? Fragmented packet reassembly timer (3 to 10 seconds [3]? Enable circuit for voice forwarding [N]? y Network number of voice forwarding PVC [0]? Circuit number of voice forwarding PVC [16]? Do you want to have data encryption performed [N]? y Should the encryption algorithm be CDMF (CDMF) or triple-DES (3DES) [CDMF]? Data encryption requires a key that is 16 hexadecimal characters long for CDMF, 48 hexadecimal characters long for 3DES. You will be asked to enter the key twice for security reasons Please enter the key for the first time now A valid encryption key has been entered Please confirm the key by entering it again The encryption keys match - the key has been accepted
Valid Values: 16 to 1007. The circuit number must be unique with respect to all other PVCs and FH PVCs on this interface and all associated subinterfaces.
| Note: | The default value is determined according the CIR-defaults set at the interface level. |
Notes:
| Note: | The default value is determined according the Be defaults set at the interface level. |
| Note: | If you enable compression on a PVC and exceed the interface's compression circuit limit, you will get a message. Compression will be performed on the circuit, if possible, that is, the active compression limit has not been exceeded when the circuit becomes active. Compression limit includes the number of compression contexts allocated to SVCs as well as PVCs. |
When you specify the fragment size and reassembly timer values, you can override the defaults for the end-to-end fragment size and reassembly timer values configured for this interface.
Specifying the Encryption Key: You must specify the encryption key value in hexadecimal characters.
Valid Values: 16 hex characters for CDMF, 48 hex characters for 3DES
| Note: | Encryption support is optional and must be added to your software load using the load add command. See Load. |
This parameter prompts you for different information depending on the type of protocol that you are adding.
Example:
add protocol-address Protocol name or number [IP]?
IP Address [0.0.0.0]? Circuit Number or name [16]?
Host Number (in hex)[]? Circuit Number or name [16]?
Network Number (1-65279) []? Node Number (1-253) []? Circuit Number or name[16]?
Node address [0.0]? Circuit Number or name[16]?
Unknown protocol name, try again
For example, you may have erroneously specified one of the following:
Prot# Name 0 IP 4 DN 7 IPX 22 AP2
To see a list of supported protocol types, type ? at the Protocol name or number [IP]? prompt.
| Note: | SVCs may not belong to a required PVC group. |
FR 4 Config>add switched-virtual-circuit Circuit name []? svc01 Remote party number []? 12345 Remote party number numbering plan (E.164 or X.121) [E.164]? Remote party number type (Unknown or International) [International]? Remote party subaddress in hexadecimal []? 01 Remote party subaddress format (private or NSAP) [private]&idotless.? Requested outgoing Committed Information Rate (CIR) in bps [64000]? Minimum acceptable outgoing Committed Information Rate (CIR) in bps [64000]? Requested incoming Committed Information Rate (CIR) in bps [64000]? Minimum acceptable incoming Committed Information Rate (CIR) in bps [64000]? Requested outgoing Committed Burst size (Bc) in bits [64000]? Requested incoming Committed Burst size (Bc) in bits [64000]? Requested outgoing Excess Burst size (Be) in bits [0]? Requested incoming Excess Burst size (Be) in bits [0]? Idle timer in seconds [60]? Establish circuit to learn remote protocol addresses [Y]? Is multicast required for this circuit [Y]? Are call-ins allowed for this circuit [Y]?
Valid Values: A 1 to 32 character ASCII string
Default Value: The name is required and must be unique for this interface
Valid Values: A 1 to 20 character string of decimal digits
Default Value: None
Valid Values: E.164 (ISDN) or X.121 (Data)
Default Value: E.164
Valid Values: International or Unknown
Default Value: International
The format of the remote party subaddress can be:
The number of digits entered must be even and in the range of X'0' - X'F'.
If the encoding is BCD, then an odd number of digits in the range of 0 - 9 can be entered.
If the encoding is not BCD, then an even number of digits in the range of X'0' - X'F' can be entered.
The combination of remote party number and remote party subaddress must be unique on this interface and any associated subinterface. If parallel connections between two router interfaces are required, the subaddress must be used to uniquely identify each switched virtual connection definition.
Valid Values: 1 - 40 character hexadecimal string
Default Value: None
Valid Values: The CIR can be either 0, or a value in the range 300 bps to 2 048 000 bps.
| Note: | The valid values for a FR interface on a HSSI adapter are: 0 or 300 - 52 000 000 |
Default Value: Default value is determined according to CIR-defaults at the interface level
Valid Values: The CIR can be either 0, or a value in the range 300 bps to 2 048 000 bps with a maximum of the requested outgoing throughput (CIR).
| Note: | The valid values for a FR interface on a HSSI adapter are: 0 or 300 - 52 000 000 |
Default Value: Default value is determined according to CIR-defaults at the interface level
Valid Values: The CIR can be either 0 or a value in the range 300 bps to 2 048 000 bps.
| Note: | The valid values for a FR interface on a HSSI adapter are: 0 or 300 - 52 000 000 |
Default Value: Value of the requested outgoing CIR
Valid Values: The CIR can be either 0 or a value in the range 300 bps to 2 048 000 bps with a maximum of the requested incoming CIR.
| Note: | The valid values for a FR interface on a HSSI adapter are: 0 or 300 - 52 000 000 |
Default Value: Same as minimum acceptable outgoing CIR
Valid Values: The CIR can be either 0 or a value in the range 300 bps to 2 048 000 bps.
| Note: | The valid values for a FR interface on a HSSI adapter are: 0 or 300 - 52 000 000 |
Default Value: Value determined according to CIR-defaults at the interface level
Valid Values: The CIR can be either 0, or a value in the range 300 bps to 2 048 000 bps.
| Note: | The valid values for a FR interface on a HSSI adapter are: 0 or 300 - 52 000 000 |
Default Value: Value equal to requested outgoing Bc
Valid Values: The CIR can be either 0, or a value in the range 300 bps to 2 048 000 bps.
| Note: | The valid values for a FR interface on a HSSI adapter are: 0 or 300 - 52 000 000 |
Default Value: Value determined according to CIR-defaults at the interface level
Valid Values: The CIR can be either 0, or a value in the range 300 bps to 2 048 000 bps.
| Note: | The valid values for a FR interface on a HSSI adapter are: 0 or 300 - 52 000 000 |
Default Value: Same as requested outgoing excess burst size (Be)
Valid Values: 0 to 65535 seconds
Default Value: 60
Valid Values: yes or no
Default Value: yes
Valid Values: yes or no
Default Value: Defaults according to the multicast emulation setting at the interface level
Valid Values: yes or no
Default Value: yes
Valid Values: yes or no
Default Value: yes, if compression is enabled for the interface. Otherwise, no.
Specifying the Encryption Key: You must specify the encryption key value in hexadecimal characters.
Valid Values: 16 for CDMF, 48 for 3DES
| Note: | Encryption support is optional and must be added to your software load using the load add command. See Load. |
Use the change permanent-virtual-circuit command to change any previous PVCs that were added with the add permanent-virtual-circuit command. If you use end-to-end type fragmentation, use the change permanent-virtual-circuit command to designate the PVCs over which end-to-end fragmentation will take place.
Syntax:
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: []? Is the circuit required for interface operation [N]? Does the circuit belong to a required PVC group [N]? Do you want to have data compression performed [Y]? Do you want end-to-end fragmentation performed on this circuit [Y]? Fragment size (50 to 8190) [256]? Fragmented packet reassembly timer (3 to 10 seconds) [3]? Do you want to have data encryption performed [N]? Enable circuit for voice forwarding [N]?
See the add frame-handler-pvc command on page *** for a description of the parameters.
See the add permanent-virtual-circuit command on page *** for a description of the parameters, except for the fragmentation parameters. These are described at the enable fragmentation command.
FR 4 Config>change switched-virtual-circuit Circuit name []? svc01 Remote party number []? 12345 Remote party number numbering plan (E.164 or X.121) [E.164]? Remote party number type (Unknown or International) [International]? Remote party subaddress in hexadecimal []? 01 Remote party subaddress format (private or NSAP) [private]&idotless.? Requested outgoing Committed Information Rate (CIR) in bps [64000]? Minimum acceptable outgoing Committed Information Rate (CIR) in bps [64000]? Requested incoming Committed Information Rate (CIR) in bps [64000]? Minimum acceptable incoming Committed Information Rate (CIR) in bps [64000]? Requested outgoing Committed Burst size (Bc) in bits [64000]? Requested incoming Committed Burst size (Bc) in bits [64000]? Requested outgoing Excess Burst size (Be) in bits [0]? Requested incoming Excess Burst size (Be) in bits [0]? Idle timer in seconds [60]? Establish circuit to learn remote protocol addresses [Y]? Is multicast required for this circuit [Y]? Are call-ins allowed for this circuit [Y]?
See page *** for a description of the parameters.
Use the disable command to disable those features previously enabled using the enable command.
Syntax:
| Note: | The parameters in the following list can be enabled and disabled on an FR
subinterface:
These parameters can have different values on an FR subinterface than they do on the FR base interface. The remaining parameters can be disabled and enabled only on the FR base interface. The values of these parameters on the FR subinterfaces are determined by their values on the FR base interface. For example, if encryption is disabled on the FR base interface, it is disabled on all FR subinterfaces that are associated with that base interface. |
| Note: | This option is presented as a configuration option only when the router software contains the DECnet Phase IV protocol. This option can be set on an FR subinterface and can differ from the value on the FR base interface. |
| Note: | Encryption support is optional and must be added to your software load using the load add command. See Load. |
The following cable types are supported:
The default setting is disable lower-dtr.
Disables multicast emulation on each active VC. The default setting for this feature is enabled. If you disable this feature, you are required to add protocol static address maps. This option can be set on a FR subinterface and can differ from the setting on the FR base interface.
Some protocols, such as IPX RIP, will not function on the Frame Relay interface if multicast-emulation is disabled. The protocol-broadcast feature also requires multicast-emulation in order to function properly. For more information, see "Multicast Emulation and Protocol Broadcast".
Prohibits protocols such as IP RIP from functioning over the Frame Relay interface. For more information, see "Multicast Emulation and Protocol Broadcast". The default setting for this feature is enabled. This option can be set on a FR subinterface and can differ from the setting on the FR base interface.
Use the enable command to enable Frame Relay features.
Syntax:
| Note: | The parameters in the following list can be enabled and disabled on an FR
subinterface:
These parameters can have different values on an FR subinterface than they have on the FR base interface. The remaining parameters can be disabled and enabled only on the FR base interface. The values of these parameters on the FR subinterfaces are determined by their values on the FR base interface. For example, if encryption is enabled on the FR base interface, it is enabled on all FR subinterfaces that are associated with that base interface. |
| Note: | The circuit monitoring feature overrides the congestion monitoring feature if there is a conflict when both are enabled. The default setting for this feature is disabled. |
For additional information on CIR monitoring, see "CIR Monitoring".
| Note: | To maximize throughput for circuits running data compression, you should not enable CIR monitoring on the same interface on which you have enabled compression. Because the device uses the uncompressed size of frames to determine if the VIR of a PVC is being exceeded and compressed frames will require less bandwidth, the CIR of a PVC will be under-utilized if the device strictly monitors and does not exceed the configured CIR. Instead, congestion monitoring can be used to allow the device to react to congestion indications sent by the FR network to avoid frame loss. |
| Note: | To maximize throughput for circuits running data compression, you should not enable CIR monitoring on the same interface on which you have enabled compression. Because the device uses the uncompressed size of frames to determine if the VIR of a VC is being exceeded and compressed frames will require less bandwidth, the CIR of a VC will be under-utilized if the device strictly monitors and does not exceed the configured CIR. Instead, congestion monitoring can be used to allow the device to react to congestion indications sent by the FR network to avoid frame loss. |
| Note: | The circuit monitoring feature overrides the congestion monitoring feature if there is a conflict when both are enabled. The default setting for this feature is enabled. |
For additional information on congestion monitoring, see "Congestion Monitoring".
| Note: | This option is presented as a configuration option only when the router software contains the DECnet Phase IV protocol. This option can be disabled and enabled for FR subinterfaces and can differ from the value of the FR base net. |
FR subinterfaces associated with the FR base interface will have the same value for encryption as the base interface.
| Note: | Encryption support is optional and must be added to your software load using the load add command. See Load. |
Keep in mind that you should configure the Bandwidth Reservation System (BRS) when you enable fragmentation to give priority to real-time traffic such as voice. For information on bandwidth reservation over Frame Relay, refer to "Using Bandwidth Reservation and Priority Queuing" and "Configuring and Monitoring Bandwidth Reservation" in Using and Configuring Features.
FR subinterfaces associated with the FR base interface will have the same value for fragmentation as the FR base interface.
User Network Interface (UNI)/Network-to-Network Interface (NNI) is the default type. UNI is DTE to DCE fragmentation; NNI is DCE to DCE fragmentation; and end-to-end is DCE to DCE fragmentation over particular specified PVCs within the interface.
When UNI/NNI fragmentation is enabled, fragmentation occurs for all circuits on the interface, including management PVCs, that is, DLCI 0. When you configure fragmentation over a PVC, the fragmentation type for that circuit is always end-to-end. You must enable end-to-end fragmentation for both ends of the PVC when fragmenting. The fragment size need not be the same in both directions, however.
If the path to the next router passes through a Frame Relay switch, you should use the end-to-end fragmentation type. If you use UNI/NNI connection from the 2216 to the next router, make sure that your Frame Relay network provider supports UNI/NNI fragmentation.
Valid Values: UNI/NNI, or end-to-end
Default Value: UNI/NNI
The fragment sizes are not negotiated and do not need to be the same on both sides of the PVC. However, the frame sent cannot be larger than the MTU of the receiving end of the PVC, regardless of the fragment size. If the frame exceeds the MTU of the receiving end, when the fragment arrives that overloads the receiver, the receiver will perform the following actions:
Tips for Selecting the Fragment Size:
Valid Values: 50 to 8190 bytes
Default Value: 256 bytes
Valid Values: 3 to 10 seconds
Default Value: 3 seconds
After issuing the enable lmi command, use the set lmi-type command to select the management mode for your Frame Relay interface. See "Enabling Frame Relay PVC Management". The system defaults to ANSI T1.617 Annex D management.
Use the enable lmi command to resume LMI management if you have previously disabled Frame Relay management.
LMI only provides information about PVCs on an interface, so it does not need to be enabled if only SVCs are used unless it is required by the network. Q.922 determines the usability of all SVCs on an interface and is an indicator of the state of the interface itself. When both PVCs and SVCs are on an interface, LMI and Q.922 may be active at the same time.
LMI is a function that can be configured only on the FR base interface, not on FR subinterfaces.
When lower-dtr is enabled, DTR will be lowered when the interface is disabled. This behavior may be desirable in situations where the interface has been configured as an alternate link for WAN Reroute and the interface is connected to a dial-out modem which maintains its dial connection based on the state of the DTR signal.
If this feature is enabled and the interface is disabled, the DTR signal is low and the modem keeps the dial connection down. When the interface is enabled, due to a WAN Reroute backup scenario, DTR is raised and the modem dials a stored number to the backup site. When the primary interface is restored, the alternate interface is disabled, DTR is lowered, and the modem hangs up the dial connection.
The following cable types are supported:
The default setting is disable lower-dtr.
Enables multicast emulation. This allows a multicast/broadcast frame to be transmitted on each active VC. This option can be set on a FR subinterface and can differ from the setting on the FR base interface.
Protocols such as ARP, IPX RIP, and IP RIP require multicast emulation to be enabled to function correctly over a Frame Relay interface. For more information, see "Multicast Emulation and Protocol Broadcast". The default for this parameter is enabled.
Controls whether the interface is considered active or inactive. When this feature is enabled, the Frame Relay interface becomes inactive when there are no active PVCs on the interface. If at least one PVC is active, the Frame Relay interface becomes active when a successful LMI exchange occurs between the router and the FR switch. This option can be set on a FR subinterface and can differ from the setting on the FR base interface.
Allows protocols such as IP RIP to function correctly over the Frame Relay interface. The multicast emulation feature must be enabled for the protocol-broadcast feature to function correctly. The default setting for this feature is enabled. This option can be set on a FR subinterface and can differ from the setting on the FR base interface.
You can also use the enable switched-virtual-circuits command to change configured SVC interface parameters if SVCs have already been enabled.
Example:
FR 1 Config> enable switched Local party number []? 4141990 Local party number numbering plan (E.164 or X.121) [E.164]? Local party number type (Unknown or International) [International]? Are call-ins allowed on this interface [Y]? Call-out redial attempts [2]? Network emulation mode [N]?
Valid Values: A 1 - 20 character string of decimal digits
Default Value: None
Valid Values: E.164 (ISDN) or X.121 (Data)
Default Value: E.164
Valid Values: International or Unknown
Default Value: International
Default Value: 2
Use the list command to display currently configured management and PVC information.
Syntax:
Example for a FR base interface:
list hdlc
Frame Relay HDLC Configuration
Maximum frame size = 2048
Encoding = NRZ
Idle state = Flag
Clocking = External
Cable type = V.35 DTE
Line speed (bps) = 64000
Transmit delay = 0
Lower DTR = Enabled
Example for an FR subinterface:
list hdlc interface
Frame Relay Subinterface Configuration
Frame Relay base network number = 1
Emulate multicast = Yes Protocol broadcast = Yes
Point-to-point = Yes Interface down if no PVCs = No
Notes:
| Note: | For FR subinterfaces, this command displays the same information as the command list hdlc. FR subinterfaces do not support LMI management. |
Example:
Frame Relay Configuration
LMI network type = UNI LMI DLCI = 0
LMI type = ANSI LMI Orphans OK = Yes
CLLM enabled = No Timer Ty seconds = 11
SVC network number = 15
SVC Number type = International
SVC Numbering plan = E.164 SVC Call-out redial attempts = 2
SVC Call-ins allowed = Yes SVC Network emulation mode = No
Protocol broadcast = Yes Congestion monitoring = Yes
Emulate multicast = Yes CIR monitoring = No
Notify FECN source = No Throttle transmit on FECN = No
Point-to-point = No
Data compression = No
(1)
Fragmentation Type = END-TO-END
Fragmentation Size = 440 Fragment reassembly timer = 3
Number VCs P1 allowed = 64 Interface down if no PVCs = No
Timer T1 seconds = 10 Timer T2 seconds = 15
LMI N1 increments = 6 LMI N2 error threshold = 3
LMI N3 error threshold = 4
MIR % of CIR = 25 IR % Increment = 12
IR % Decrement = 25 DECnet length field = No
Default CIR = 64000 Default Burst Size = 64000
Default Excess Burst = 0
(1) The two lines that follow this marker appear only when fragmentation is on (yes).
| Note: | Encryption support is optional and must be added to your software load using the load add command. See Load. |
| Note: | Enabling compression on orphan circuits will decrease the number of available
compression contexts available for the native PVCs on the device.
Orphan compression applies to both PVCs and SVCs. |
Example:
FR 1 Config>list permanent virtual circuits
Maximum circuits allowable = 64
Circuits configured this interface = 2
PVCs configured this interface = 1
Total circuits configured = 4
Total PVCs configured = 2
Circuit Circuit CIR Burst Excess
Name Number Options in bps Size Burst
---------------------------------- ------- -------- -------- -------- --------
circ16 16 c 64000 64000 0
R = circuit is required
G = circuit is required and belongs to a required PVC group
F = circuit is fragmentation capable
c = circuit is data compression capable
d = circuit is CDMF data encryption capable
t = circuit is triple-DES data encryption capable
V = circuit is voice forwarding enabled
H = frame handler circuit
Example:
list protocol-addresses
Frame Relay Protocol Address Translations
Protocol Type Protocol Address Circuit Number or Name
------------- ---------------- ----------------------
IP 125.2.29.4 21
IPX 000000004503 16
Example:
list pvc-groups
Required PVC group = group1
Circuit # 16
Example:
FR 1 Config>list subinterfaces
Maximum circuits allowable = 64
Circuits configured this interface = 2
Total circuits configured = 4
Circuit
Circuit Name Number Remote Party Number Interface
-------------------------------- ------- -------------------- ----------
circ16 16 1 (base)
circ17 17 4
svc1 998 1 (base)
svc2 998 4
FR 0 Config>LIST SWITCHED-VIRTUAL-CIRCUITS
Maximum circuits allowable = 64
Circuits configured this interface = 2
SVCs configured this interface = 1
Total circuits configured = 5
Circuit Opt- Idle Outgoing Incoming
Name ions Timer Value Value
-------------------------------- ------ ------ ---------- ----------
SVC1 ILM c 60 CIR: 64000 64000
Remote party number: IE3445667 Min CIR: 64000 64000
Remote subaddress: Burst: 64000 64000
Pc4456d Excess: 0 0
svc1 ILM c 60 CIR: 64000 64000
Remote party number: IE3445666 Min CIR: 64000 64000
Remote subaddress: Burst: 64000 64000
P344566 Excess: 0 0
Options: I - call-ins allowed, L - learn protocols, M - Multicast required
c - compression capable, F - UNI/NNI fragmentation enabled
Address type: I - International, U - Unknown
Numbering plan: E - E.164, X - X.121
Subaddress format: N - NSAP, P - private
FR 2 Config>list voice Circuit Circuit Forwarding Forwarding Name Number Network Circuit ---------------------- ----------- ---------- ---------- circ11 17 0 16
Use the LLC command to access the LLC configuration environment. See "LLC Configuration Commands" for an explanation of each of these commands.
| Note: | The LLC command is supported only if APPN is in the software load. |
Syntax:
Use the remove command to delete any PVC, Required PVC group, frame-handler-pvc, or protocol-address previously added using the add command.
Syntax:
Deletes any configured PVC in the range 16 to 1007.
Notes:
| Note: | Encryption support is optional and must be added to your software load using
the load add command. See the CONFIG process load command
in Nways Multiprotocol Access Services Software User's Guide.
The use of multiple encryption (using encryption at both the IP Security Layer and at the Frame Relay or PPP data-Link Layer) within the router is restricted by U.S.A. Government export regulations. It is only supported in software loads that are under strict export control (software loads that support RC4 with 128 bit keys and Triple DES). |
Example:
remove protocol-address Protocol name or number [IP]?
IP Address [0.0.0.0]? Circuit Name or Number [16]?
Host Number (in hex)[]? Circuit Name or Number [16]?
Network Number (1-65279) []? Node Number (1-253) []? Circuit Name or Number [16]?
Node address [0.0]? Circuit Name or Number [16]?
Unknown protocol name, try again
To see a list of supported protocols, type ? at the Protocol name or number [IP]? prompt.
Example: remove pvc-group PVC group name [IP]?
Use the set command to configure the interface to run the Frame Relay protocol.
| Note: | The Talk 6 set command is not applicable for FR subinterfaces. |
Set Command Considerations
Two parameters, the n2-parameter and the n3-parameter, require further explanation before you configure them. The n2-parameter sets the error threshold for management events, and the n3-parameter sets the number of events that are monitored in the event window. If the number of management errors in the event window equals n2, the Frame Relay interface resets. For example:
set n3-parameter 4
set n2-parameter 3
You now have a window size of 4 (n3 = 4) and an error threshold of 3 (n2 = 3). That means the system is monitoring 4 management events and checking to determine if any of those are in error. If the number of events in error equals 3 (the n2 parameter), the Frame Relay interface is reset and the status of the network is considered network down.
For the status of the network to be considered network up, the number of events in error within the window must be less than n2 prior to any change in status.
Syntax:
| * Note: | The commands with an * following them are not available for FR dial circuit interfaces. |
A DTE cable is used when you are attaching the router to some type of DCE device (for example, a modem or a DSU/CSU). A DCE cable is used when the router is acting as the DCE and providing the clocking for direct attachment.
The available options are:
| Physical Interface Link Type | Data Connection Type |
|---|---|
| EIA 232 (RS-232) | DTE, DCE |
| V35 | DTE, DCE |
| V36 | DTE, DCE |
| X21 | DTE, DCE |
| HSSI | DTE, DCE (see note) |
| Note: | When a HSSI DCE cable is used, the other device must also be configured to use a HSSI DCE cable. |
Valid Values: 0 or 300 to 204 800 bps
Default Value: 64 000
For HSSI, the maximum value that can be configured is 52 000 000 bps.
Valid Values: See "Committed Burst (Bc) Size"
Default Value: 64 000
For HSSI, the maximum value that can be configured is 52 000 000 bps.
Valid Values: See "Excess Burst (Be) Size"
Default Value: 0
For HSSI, the maximum value that can be configured is 52 000 000 bps.
Example:
FR 6 config> set cir-default Default Committed Information Rate (CIR) in bps [64000]? 48000 Default Committed Burst Size (Bc) in bits [64000]? 40000 Default Excess Burst Size (Be) in bits [0]? 52000
To connect directly to another DTE device, configure internal clocking, select the appropriate DCE cable with the set cable command, and configure the clocking/line speed with the set line-speed command.
Default: external
| Note: | CRC type can only be configured for a FR interface on a HSSI adapter. |
| Note: | Encoding is set to NRZ for a FR interface on a HSSI adapter and is not configurable. |
| IP | 4 bytes |
| IPX | 10 bytes |
| Appletalk Phase 2 | 10 bytes |
| DECnet Phase IV (DNA IV) | 12 bytes |
| Banyan Vines | 10 bytes |
| OSI | 10 bytes |
| Bridging | 10 bytes |
| APPN | 58 bytes (see note) |
| Note: | Assumes worst case for APPN BAN where a T/R MAC address header and LLC header are added in addition to the FR header bytes. |
When using Frame Relay SVCs, the maximum information field size must be the same at both ends of the virtual circuit. To determine the maximum information field size, subtract 16 bytes from the frame size if encryption is enabled on the SVC and subtract 4 bytes if encryption is not enabled on the SVC.
| Note: | Idle is set to flag for a FR interface on a HSSI adapter and is not configurable. |
The minimum IR, expressed as a percentage of CIR, is the lower limit of the information rate. The minimum percentage is 1 and the maximum percentage is 100. The default is 25.
When network congestion clears, the information rate is gradually incremented by the IR adjustment increment percentage until the maximum information rate is reached. The minimum percentage is 1 and the maximum percentage is 100. The default is 12.
When network congestion occurs, the information rate is decremented by the IR adjustment decrement percentage each time a frame containing BECN is received until the minimum information rate is reached. The minimum percentage is 1, and the maximum percentage is 100. The default is 25.
Example:
set ir-adjustment IR adjustment % increment [12]? IR adjustment % decrement [25]? Minimum IR as % of CIR [25]?
For internal clocking, use this command to specify the speed of the transmit and receive clock lines.
For external clocking, this command does not affect the operation of the WAN/serial line but it does set the speed that some protocols, such as IPX, use to determine routing cost parameters. You should set the speed to match the actual line speed. If the speed is not configured, the protocols assume a speed of 1 000 000 bps.
Valid Values:
Internal Clocking: See Table 72
External Clocking: See Table 73
Table 72. Line Speeds When Internal Clocking is Used for 2216 Interfaces
| Adapter Type | Speed Range |
|---|---|
| 8-port EIA 232 | 9600 to 64 000 bps |
| 6-port V.35/V.36 | 9600 to 460 800 bps, 1 544 000 bps, or 2 048 000 bps |
| 8-port X.21 | 9600 to 460 800 bps, 1 544 000 bps, or 2 048 000 bps |
| 1-port HSSI | 22 368 000 bps or 44 736 000 bps |
Table 73. Line Speeds When External Clocking is Used for 2216 Interfaces
| Adapter Type | Speed Range |
|---|---|
| 8-port EIA 232 | 2400 to 64 000 bps |
| 6-port V.35/V.36 | 2400 to 2 048 000 bps |
| 8-port X.21 | 2400 to 2 048 000 bps |
| 1-port HSSI | 1 544 000 bps to 52 000 000 bps |
| Note: | The LMI network type must be compatible with the adjacent FR node. For example, if the adjacent node is configured as UNI, this FR interface must be configured with a LMI network type of NUI, and when using the NNI support both this interface and the adjacent FR node's interface must be using a LMI network type of NNI. |
Valid Values:
Default Value: UNI
Table 74. Frame Relay Management Options
| Command | Management Type | Description |
|---|---|---|
| set | lmi-type rev1 | Conforms to LMI Revision 1, (Stratacom's Frame Relay Interface Specification) |
| set | lmi-type ansi | Conforms to ANSI T1.617 ISDN-DSS1-Signalling Specification for Frame Relay Bearer Service (known as Annex D) |
| set | lmi-type ccitt | Conforms to Annex A of ITU-T/CCITT Recommendation Q.933 - DSS1 Signalling Specification for Frame Mode Basic Call Control. |
| Note: | If you configure a non-zero transmit delay for a FR interface on the 8-port EIA-232E adapter, 6-port V.35/V.36 adapter, or 8-port X.21 adapter, you must configure the line speed using the set line-speed command. |
Table 75. Transmit Delay Units and Range for the 2216 Serial Interface
| Unit | Minimum | Maximum |
|---|---|---|
| Extra Flags | 0 | 15 |
Valid Values: 5 to 30 seconds.
Default Value: 11 seconds.
To access the Frame Relay operating commands and to monitor Frame Relay on your router, perform the following steps:
+ net 2 Frame Relay Monitoring FR 2 >
This section summarizes and then explains the Frame Relay Monitoring
commands. Use these commands to gather information from the
database. Table 76 shows the commands.
Table 76. Frame Relay Monitoring Commands Summary
| Command | Function |
|---|---|
| ? (Help) | Displays all the commands available for this command level or lists the options for specific commands (if available). See "Getting Help". |
| Clear | Clears statistical information on the Frame Relay interface. |
| Disable | Disables CIR monitoring and congestion monitoring on the Frame Relay interface. |
| Enable | Enables CIR monitoring and congestion monitoring on the Frame Relay interface. |
| List | Displays statistics specific to the data-link layer and Frame Relay management. |
| LLC | Displays the LLC monitoring prompt. |
| Notrace | Disables packet tracing capability for individual circuits or for the entire interface. |
| Set | Sets CIR, Committed Burst Size, and Excess Burst Size for a Frame Relay VC. |
| Trace | Enables packet tracing capability for individual circuits or for the entire interface. |
| Exit | Returns you to the previous command level. See "Exiting a Lower Level Environment". |
| Note: | In this section, the terms circuit number and PVC are equivalent to the term data link circuit identifier (DLCI). |
Use the clear command to zero statistical counters on the Frame Relay interface.
| Note: | Statistics can also be cleared by using the OPCON clear command. |
Syntax:
Use the disable command to disable the Frame Relay CIR monitoring and congestion monitoring features.
The disable command dynamically changes the router configuration. These changes will be lost when the router is restarted.
Syntax:
Use the enable command to enable the Frame Relay CIR monitoring and congestion monitoring features.
The enable command dynamically changes the router configuration. These changes will be lost when the router is restarted.
Syntax:
Use the list command to display statistics specific to the data-link layer and the Frame Relay interface.
Syntax:
Example:
list circuit 347 Circuit name = Valencia Circuit state = Active 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 = 64000 Potential Info Rate = 56000 Committed Burst (BC) = 1200 Excess Burst (Be) = 54800 Minimum Info Rate = 16000 Maximum Info Rate = 64000 Required = Yes PVC group name = group1 Compression capable = Yes Operational = Yes R-Rs received = 0 R-Rs transmitted = 0 R-As received = 0 R-As transmitted = 0 R-R mode discards = 0 Enlarged frames = 0 Decompress discards = 0 Compression errors = 0 Compression ratio = 1.72 to 1 Decompression ratio = 1.10 to 1 Fragmentation type = END-TO-END Fragmentation Size = 0 Reassembly timer = 0 Fragments xmitted = 0 Fragments received = 0 Voice Frames xmitted = 0 Voice Frames rcv'd = 0 Encryption capable = Yes Operational = Yes Encryption errors = 0 Decryption errors = 0 Rcv error discards = 0 Current number of xmit frames queued = 0 Xmit frames dropped due to queue overflow = 0
If this field has a value of "Line Speed", then the maximum data rate is the actual line speed even if the line speed was not configured or was configured incorrectly for this interface.
| Note: | If end-to-end fragmentation is configured, the fragment size shows the size configured of the interface, not the size for every PVC. |
| Note: | Encryption support is optional and must be added to your software load using the load add command. See Load. |
Example:
Frame Relay Frame Handler Configuration
Circuit Circuit Status Forwarding Max
Name Number (L/R) Net/Circuit Queue (L/R)
-------------------------------- ------- ------ ----------- -----------
Raleigh 16 A/A 2/18 10/10
Sum of outbound queue limits = 10 Input buffers allocated = 24
Total congested frms discard = 0 Total frms currently queued = 0
Total BECNs set = 0 Total FECNs set = 0
Local/Remote circuit states: A - Active I - Inactive R - Removed
Displays statistics relevant to the logical management on the Frame Relay interface. If you enter this command for an FR subinterface, the information for its FR base interface is displayed.
Example:
list lmi
Management Status:
------------------
LMI network type = UNI LMI DLCI = 0
LMI type = ANSI LMI Orphans OK = YES
CLLM enabled = No
SVC local net number = 12345678
SVC Number type = International
SVC Numbering plan = E.164 SVC Call-out retries = 2
SVC Call-ins allowed = Yes SVC Network emulation mode = No
Protocol broadcast = Yes Congestion monitoring = Yes
Emulate multicast = Yes CIR monitoring = No
Notify FECN source = No Throttle transmit on FECN = No
Number VCs P1 allowed = 64 Interface down if no PVCs = No
Line speed (bps) = 1000000 Maximum frame size (bytes) = 2048
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 DECnet length field = No
Default CIR = 64000 Default Burst Size = 64000
Default Excess Burst = 0
Current receive sequence = 0
Current transmit sequence = 1
Total status enquiries = 9 Total status responses = 0
Total sequence requests = 0 Total responses = 0
Data compression enabled = No
Data encryption enabled = No
Fragmentation enabled = No
Virtual Circuit Status:
-----------------------
Total allowed = 64 Total configured = 2
Total active = 0 Total congested = 0
Total PVCs left net = 0 Total PVCs join net = 0
Management Status:
| Note: | Encryption support is optional and must be added to your software load using the load add command. See Load. |
| Note: | Enabling compression on orphan circuits will decrease the number of available
compression contexts available for the native VCs on the device.
Orphan compression applies to both PVCs and SVCs. |
| Note: | Encryption support is optional and must be added to your software load using the load add command. See Load. |
Example:
FR 0>LIST PERMANENT-VIRTUAL-CIRCUITS
Circuit Type/ Frames Frames
Number Circuit Name Options State Transmitted Received
------- -------------------------------- ------- ----- ----------- ----------
16 Unassigned R P/I 0 0
17 Bigcir F V P/I 0 0
18 Unassigned P/I 0 0
Circuit type: O - Orphan P - PVC S - SVC
Circuit state: A - Active I - Inactive R - Removed C - Congested
R - Required G - Required and belongs to a PVC group
F - circuit is fragmentation capable
c - Data compression capable but not operational
C - Data compression capable and operational
d - CDMF DES data encryption capable but not operational
D - CDMF DES data encryption capable and operational
t - 3DES data encryption capable but not operational
T - 3DES data encryption capable and operational
V - circuit is voice forwarding enabled
H - Frame Handler circuit
Example:
list pvc-groups
Group name Circuits in group Circuit status
---------- ----------------- --------------
group1 16 active
44 inactive
240 removed
Example:
Frames Frames Frames Frames High
DLCI Circuit Name Sent Rcv'd Discard Queued Queue
---- -------------------------------- -------- -------- -------- ------ ------
18 Phoenix 11946 12041 2 41 41
Example:
FR 1>list subinterfaces
Circuit Circuit Circuit Interface
Name Number Type Number
-------------------------------- ------- --------- ----------
svc1 Switched 1 (base)
circ16 16 Permanent 1 (base)
svc2 Switched 4
circ17 17 Permanent 4
Example:
FR 1>list svcs
Circuit Call
Circuit Name Remote party number State State DLCI
-------------------------------- -------------------- ------- ----- -----
flotsam 911 R N 0
jetsam 666 R N 0
Circuit states: A - Active I - Inactive R - Removed C - Congested
Call states: N - Null I - Call Initiated O - Outgoing call proceeding
A - Active D - Disconnect request R - Release request
Example:
FR 1>list switched-virtual-circuit flotsam
Circuit Opt- Idle Outgoing Incoming
Name ions Timer Value Value
-------------------------------- ----- ------ ---------- ----------
flotsam ILMF 60 CIR: 0 0
Call state: Null Burst: 0 0
Call Initiated by: None DLCI: 0 Excess: 0 0
Remote party number: IE14
Remote subaddress: None
Options: I - call-ins allowed, L - learn protocols, M - multicast required
F - UNI/NNI fragmentation capable C - compression capable and operational
c - compression capable, d - CDMF DES data encryption capable but not operational
D - CDMF DES data encryption capable and operational t - 3DES data encryption
capable but not operational T - 3DES data encryption capable and operational
Address type: I - International, U - Unknown Numbering plan: E - E.164,
X - X.121 Subaddress format: N - NSAP, P - private
FR 1>list virtual-circuits
Circuit Type/ Frames Frames
Number Circuit Name Options State Transmitted Received
------- -------------------------------- ------- ----- ----------- ----------
16 Unassigned F P/I 0 0
17 Unassigned F H P/I 0 0
23 To-Kitty F H P/I 0 0
Circuit type: O - Orphan P - PVC S - SVC
Circuit state: A - Active I - Inactive R - Removed C - Congested
R - Required G - Required and belongs to a PVC group
F - circuit is fragmentation capable
c - Data compression capable but not operational
C - Data compression capable and operational
d - CDMF DES data encryption capable but not operational
D - CDMF DES data encryption capable and operational
t - 3DES data encryption capable but not operational
T - 3DES data encryption capable and operational
V - circuit is voice forwarding enabled
FR 2>list voice-forwarding-circuits
Circuit Circuit Forwarding Forwarding
Name Number Network Circuit
--------------- ----------- ------------- ------------
circ16 16 2 17
circ17 17 2 16
Use the LLC command to access the LLC monitoring prompt. LLC commands are entered at this new prompt. See "LLC Monitoring Commands" for an explanation of each of these commands.
Syntax:
| Note: | The LLC command is supported only if APPN is in the software load. |
Use the notrace command to disable packet tracing for individual circuits or the entire interface. This command can be used as a filter when tracing specific circuits or interfaces is required. The default setting is to trace all circuits.
Syntax:
Example:
notrace 16
Disables packet tracing on circuit (PVC or SVC) with DLCI 16.
notrace circuit phoenix
Disables packet tracing on circuit (PVC or SVC) named phoenix.
notrace circuit all
Disables packet tracing on all circuits on this interface.
Use the set command to set the values for Committed Information Rate (CIR), Committed Burst Rate, and Excess Burst Rate for the specified VC. You also can set values for IR adjustment rates.
Changes made with this command do not affect the configuration data. They are in effect only until the router is restarted.
Syntax:
Example:
set circuit Circuit number [16]? Committed Information Rate (CIR) in bps [1200]? Committed Burst Size (Bc) in bits [1200]? Excess Burst Size (Be) in bits [56000]?
| Note: | If CIR is configured as 0 then the committed burst size is set to 0 and you are not prompted for a value. For additional information, see "Committed Burst (Bc) Size". |
| Note: | The Talk 5 set ir-adjustment command is not applicable for FR subinterfaces. |
The minimum IR, expressed as a percentage of CIR, is the lower limit of the information rate. The minimum percentage is 1 and the maximum percentage is 100. The default is 25.
When network congestion clears, the information rate is gradually incremented by the IR adjustment increment percentage until the maximum information rate is reached. The minimum percentage is 1 and the maximum percentage is 100. The default is 12.
When network congestion occurs, the information rate is decremented by the IR adjustment decrement percentage each time a frame containing BECN is received until the minimum information rate is reached. The minimum percentage is 1, and the maximum percentage is 100. The default is 25.
Example:
set ir-adjustment
IR adjustment % increment [12]?
IR adjustment % decrement [25]?
Minimum IR as % of CIR [25]?
Use the Trace command to enable packet tracing for individual circuits or the entire interface and to list the tracing capability of all circuits on this interface. This command can be used as a filter when tracing specific circuits or interfaces is required. The default setting is to trace all circuits.
Syntax:
Example:
trace 16
Enables packet tracing on circuit (PVC or SVC) with DLCI 16.
trace circuit phoenix
Enables packet tracing on circuit (PVC or SVC) named phoenix.
trace circuit all
Enables packet tracing on all circuits on this interface.
trace list
The following circuits are available for packet trace
Circuit Name Circuit Number
-------------------------------- --------------
Unassigned 16
phoenix 25
jetsam 0
Lists the packet tracing capability of all circuits on this
interface.
While Frame Relay interfaces have a monitoring process for monitoring purposes, the router also displays complete statistics for installed interfaces when you use the interface command from the GWCON environment. (For more information on the interface command, refer to "The Operating/Monitoring Process (GWCON - Talk 5) and Commands")
Statistics similar to the following are displayed when you execute the interface command from the GWCON environment for Frame Relay interfaces. The actual display will vary somewhat depending upon the adapter type, for example, X.21, V.35, or HSSI.
If FR subinterfaces have been configured, the GWCON statistics and error commands for the FR base interface will display cumulative counts for all circuits on the FR base interface and all associated subinterfaces. For a subinterface, these commands will list counts for only the circuits defined for the subinterface.
+interface 10
Self-Test Self-Test Maintenance
Nt Nt' Interface Slot-Port Passed Failed Failed
10 10 FR/0 Slot: 8 Port: 0 2 1 0
Frame Relay MAC/data-link on V.35/V.36 interface
Adapter cable: V.35 DTE
V.24 circuit: 105 106 107 108 109
Nicknames: RTS CTS DSR DTR DCD
PUB 41450: CA CB CC CD CF
State: ON ON ON ON ON
Line speed: ~64.000 Kbps
Last port reset: 1 hour, 20 minutes, 42 seconds ago
Input frame errors:
CRC error 0 alignment (byte length) 0
missed frame 182 too long (> 2062 bytes) 0
aborted frame 0 DMA/FIFO overrun 0
Output frame counters:
DMA/FIFO underrun errors 0 Output aborts sent 0
| Note: | For FR dial circuit interfaces, Nt' is different from Nt. Nt' indicates the base interface (ISDN) that the dial circuit is running over. |
| Note: | The symbol - - - in monitoring output indicates that the value or state is unknown. |
Input frame errors:
| Note: | It is unlikely that the L & F bits not set counter will be affected by traffic. |
Output frame counters:
Statistics similar to the following are displayed for Frame Relay dial circuits when you execute the interface command from the GWCON environment:
+interface 3
Self-Test Self-Test Maintenance
Nt Nt' Interface Passed Failed Failed
3 2 FR/1 1 0 0
Frame Relay MAC/data-link on ISDN Primary Rate interface
This section describes dynamic reconfiguration (DR) as it affects Talk 6 and Talk 5 commands.
Frame Relay supports the CONFIG (Talk 6) delete interface command with no restrictions.
Frame Relay supports the GWCON (Talk 5) activate interface command with the following considerations:
All Frame Relay configuration changes are automatically activated except
the following changes:
| Commands whose changes are not activated by the GWCON (Talk 5) activate interface command | ||
CONFIG, net, enable compression
|
Frame Relay supports the GWCON (Talk 5) reset interface command with the following considerations:
All Frame Relay configuration changes are automatically activated except
the following changes:
| Commands whose changes are not activated by the GWCON (Talk 5) reset interface command | ||
CONFIG, net, set frame-size
| ||
CONFIG, net, enable compression
|
Frame Relay supports the following GWCON commands that temporarily
change the operational state of the device. These changes are lost
whenever the device is reloaded, restarted, or you execute any dynamically
reconfigurable command.
| Commands |
| GWCON, net, set circuit |
| GWCON, net, set ir-adjustment |
| GWCON, net, enable cir-monitor |
| GWCON, net, enable cllm |
| GWCON, net, enable congestion-monitor |
| GWCON, net, enable notify-fecn-source |
| GWCON, net, enable throttle-transmit-on-fecn |
| GWCON, net, disable cir-monitor |
| GWCON, net, disable cllm |
| GWCON, net, disable congestion-monitor |
| GWCON, net, disable notify-fecn-source |
| GWCON, net, disable throttle-transmit-on-fecn |