|
|
The Frame Relay commands let you add, configure, delete, and specify statistical reporting for Frame Relay connections. In addition to describing the commands, this chapter tells you how to:
The Frame Relay commands in this chapter operate on an FRM or UFM card set in an IGX node. For the Frame Relay commands that operate on an FRSM in an MGX 8220 shelf, refer to the Cisco MGX 8220 Command Reference. For the Frame Relay commands that operate on the FastPADs and supporting service cards, refer to the FastPAD manuals.
For a greater number of low-speed connections, the Port Concentrator Shelf (PCS) is available. The PCS is an external device that requires an FRM-2/FRI-2 card set in an IGX node. The system recognizes an FRM-2 or FRC-2 and accepts commands for the PCS.
This section describes the command-related issues for physical and logical Frame Relay ports.
In the IPX and IGX nodes, the Frame Relay-only cards are the FRP, FRM and UFM card sets. (The FTM supports Frame Relay, voice, and serial data but is not described in this manual.) In the FRP and FRM, both physical and logical ports can exist. The UFM has logical ports and physical lines.
In the FRP and FRM card sets, a logical port is a convention that applies to a T1 or E1 back card. In contrast, the ports on an X.21 or V.35 back card are physical. The reason that T1 and E1 ports on an FRP or FRM card set are logical is that these ports use one, bidirectional connector. To support the range of possible PVCs, the traffic passes through a demultiplexer on a T1 or E1 FRI. Therefore, although only one connector exists on the card, the Frame Relay commands accept port numbers 1-24 (T1) or 1-31 (E1). When a Frame Relay command takes the parameter slot.port, the port in this case is logical, and the node tracks it accordingly.
On the UFI back cards, the presence of multiple physical lines adds a parameter to the connection identifier. When you identify a UFM-C channel, use the format slot.port line.DS0_range. Due to the architecture of the software, port is a logical specification, and line is a physical specification. The range of logical ports is 1-250. The number of physical lines (hardware connectors) on the UFI-8T1 and UFI-8E1 is 8 (regardless of whether the front card is a UFM-4C or UFM-8C). The range of DS0s is 1-24 for T1 and 1-31 for E1.
For interfaces attached to a UFM-U front card, the range of ports is 1-12 for the UFI-12V.35 or UFI-12X.21 and 1-4 for the UFI-4HSSI.
Frame relay connections can exist between the following cards:
An IPX or IGX node provides a Permanent Virtual Circuit (PVC) Frame Relay Service for interconnecting user devices (routers, bridges, and packet switches). The PVCs are internally created on the node and rely on FastPacket switching. The user device connects to the Frame Relay back card in the node. The back card provides the adaptation layer function to convert between the Frame Relay format and the FastPacket format.
In addition to the interface cards just listed, Frame Relay connections require a trunk card. Trunk cards can be an NTC or AIT in an IPX node or an NTM, BTM, or ALM/B in an IGX node. Because Frame Relay is a purchased option, Cisco must enable it on each applicable WAN Switching node.
A variety of external user devices can operate with an IGX node. The configuration on these devices must be appropriate for the type of interface on the back card.
The following command sequence brings up a Frame Relay port and adds a Frame Relay connection.
Step 1 Activate a Frame Relay port with the upfrport command.
Step 2 Use cnffrport to specify the Frame Relay parameters for the Frame Relay service.
An optional command may be applicable to a Port Concentrator Shelf (PCS): you can use cnffrcport to configure the concentrated link between the PCS and Frame Relay cards.
Step 3 Use the dspcls command to view the existing Frame Relay classes. Decide on a class if a suitable class exists, otherwise create a suitable class using the cnffrcls command. Use the class number in the addcon command.
Step 4 Use the vt command to access the node at the remote end of the proposed Frame Relay connection, then use the upfrport and cnffrport commands as in steps 1 and 2.
Step 5 Use the addcon command on the local node to add the Frame Relay connection.
For each Frame Relay connection you add, you must specify a Frame Relay class. A Frame Relay class is a set of parameters that specify the bandwidth and congestion-prevention characteristics for a connection. Cisco provides ten (10) predefined classes, but you can modify any of the 10 Frame Relay classes with cnffrcls. To see the parameters in all connection classes, execute dspfrcls. A Frame Relay class is relevant only at the time you add a connection with addcon. Once the connection exists, the system uses the parameters but does not keep track of the class number.
Apart from using the cnffrcls command, you can change one or more Frame Relay parameters with the addcon command. When you add a Frame Relay connection with addcon, a prompt appears requesting a Frame Relay class. At this prompt you can do one of the following:
If you are overriding class parameters, but want to keep the existing value of the parameter, use the asterisk to cause the connection to use the existing value of the parameter in that class. Most parameters are bi-directional and have the format parameter/parameter. If you want to keep a value for both directions, enter a single *. If you want to change a value for only one direction, enter the parameter in the form */new_parameter or new_parameter/*. When you type individual parameters, you need to enter characters only up to the last changed item. Before the last item, you must enter new values or * as a placeholder.
The parameters in the list that follows make up a Frame Relay class. Collectively, the name of these parameters is frp_bw. For most parameters, you can specify the value for each direction of the connection, so most parameter names appear in the format parameter/parameter. ForeSight (FST) is the exception because ForeSight automatically applies to both directions.
X.21 ports use a fixed, active control template. In contrast, although V.35 and V.28 ports use an active control template, you can set the signals that are active to on or off. These ports cannot use looped, conditioned, near, or far.
You can use the cnfchutl command to enter the expected channel utilization of a Frame Relay circuit into the system. This command helps the system allocate the proper bandwidth to the circuit.
A Frame Relay connection has either low or high priority. The default is low priority. You can use cnfchpri to assign a high priority to a circuit or to re-assign a high priority circuit to low priority.
Nodes collect statistics for Frame Relay traffic, channel use, and Explicit Congestion Notification. Use dspchstats to display these statistics. Use clrchstats to clear the statistics and start collecting new statistics. To display Frame Relay use and error statistics, use dspportstats.
This table lists the full name and starting page of the description for each Frame Relay command.
| Mnemonic | Name | Page |
|---|---|---|
addcon | Add connection | |
addfrport | Add Frame Relay port | |
clrfrcportstats | Clear Port Concentrator link statistics | |
cnfchpri | Configure channel priority | |
cnffrcls | Configure Frame Relay class | |
cnffrcon | Configure Frame Relay connection | |
cnffrcport | Configure Frame Relay port on a Port Concentrator Shelf | |
cnffrport | Configure Frame Relay port | |
cnfict | Configure interface control template | |
cnfmode | Configure mode | |
cpyict | Copy interface control template | |
delcon | Delete connection | |
delfrport | Delete Frame Relay port | |
dnfrport | Down Frame Relay port | |
dspchcnf | Display channel configuration | |
dspchstats | Display channel statistics | |
dspcon | Display connection | |
dspcons | Display connections | |
dspfrcls | Display Frame Relay class | |
dspfrport | Display Frame Relay port | |
dspict | Display interface control template | |
dspmode | Display mode | |
dspmodes | Display modes | |
dsppcs | Display Port Concentrator Shelf | |
dspportids | Display port IDs | |
dspportstats | Display port statistics | |
prtchcnf | Print channel configuration | |
prtcons | Print connections | |
prtict | Print interface control template | |
upfrport | Up Frame Relay port |
Adds a Frame Relay connection to the network. After you add a connection, the system automatically routes the connection. The node on which you execute addcon is the owner of the connection. The concept of ownership is important because you must specify automatic rerouting and preferred routing information at the node that owns the connection. See the cnfpref and cnfcos descriptions for information on automatic rerouting. Before it actually adds the connection, the system displays the parameters you have specified and prompts you to confirm them.
Each Frame Relay connection (and associated user device) has a local identification in the form of a unique DLCI. The total range for DLCIs is 1-1023. Typically, DLCIs 16-1007 are available for local and remote channels. According to ANSI standards, DLCIs 1-15 and 1008-1022 are reserved. DLCI 1023 is reserved for LMI signaling.
Only a UFM could come close to using all DLCIs. The maximum number of connections on a UFM is 1000. The maximum number of Frame Relay connections on an FRC or FRM is 252.
If a user device can automatically determine the network configuration by using the LMI, you do not need to specify the DLCIs in the network to the device. If a device cannot interrogate the network to determine the DLCIs in the network, you must specify the network DLCIs to the user device.
As the following sections describe, you can generally differentiate Frame Relay connections as normal, bundled, grouped, and frame forwarding. In particular, a Frame Relay connection can also terminate at a Frame Relay endpoint or an ATM endpoint if the endpoints have firmware to support this arrangement. A connection that terminates at Frame Relay and ATM endpoints uses service interworking (SIW).
Frame relay connections that terminate at ATM endpoints require service interworking (SIW) support. At the Frame Relay end, service interworking is one of the optional parameters. The line cards on which you can add service interworking connections are the UFM on an IGX node, ASI on a BPX node, and FRSM in an MGX 8220 shelf. The Frame Relay endpoint has an identifier in the format slot.port.DLCI. For SIW connections, the ATM endpoint identifier has the format slot.port.vpi.VCI.
A normal connection is a single PVC. A Frame Relay PVC can terminate at either a Frame Relay endpoint or an ATM endpoint.
Connection bundling creates a full mesh of connections between two groups of Frame Relay ports by executing addcon command only once. When you add a bundle between two groups of ports, you create a connection between each port of one group of ports and each port of the other group of ports. Each group of Frame Relay ports can include up to four ports. Consequently, the maximum number of connections in a bundle is 16 (resulting from a full mesh of connections between two groups of four ports each). Note that a Port Concentrator Shelf does not support bundling. Characteristics of connection bundling are:
When you create a connection bundle with addcon, you do not explicitly specify the required DLCI at each endpoint of each connection. Instead, the DLCIs are automatically assigned using global addressing with the Port IDs, which have been previously assigned to the ports. Consequently, you must first assign a Port ID (other than 0) to every port to which you plan to assign a connection bundle. Use cnffrport to assign a Port ID or dspport to see an existing Port ID.
For example, the command
addcon 6.1x3 alpha 7.2x3 1
defines a single connection bundle between a local group of 3 ports (ports 1, 2, and 3 on card 6) and a remote group of 2 ports (ports 2 and 3 on card 7). The resulting connection bundle consists of the following six connections:
local node slot 6.port 1 to node alpha slot 7.port 2
local node slot 6.port 1 to node alpha slot 7.port 3
local node slot 6.port 2 to node alpha slot 7.port 2
local node slot 6.port 2 to node alpha slot 7.port 3
local node slot 6.port 3 to node alpha slot 7.port 2
local node slot 6.port 3 to node alpha slot 7.port 3
Each connection in the bundle is assigned the parameters of the same Frame Relay class (class 1, in the example above). Notice that no DLCIs were specified for the six connections. The DLCIs are automatically assigned using the Port IDs of the ports.
As an example, assume that the following Port IDs had been previously assigned for the five ports.
port 6.1 Port ID = 22
port 6.1 Port ID = 534
port 6.3 Port ID = 487
port 7.2 Port ID = 92
port 7.3 Port ID = 796
As a result of the addcon command, the six connections that you create are automatically assigned DLCIs using global addressing as follows.
6.1.92 - 7.2.22
6.1.796 - 7.3.22
6.2.92 - 7.2.534
6.2.796 - 7.3.534
6.3.92 - 7.2.487
6.3.796 - 7.3.487
The dspcons display shows the entire bundle as a single item. Therefore, you cannot see the automatically assigned DLCIs on the dspcons screen. (The automatically assigned DLCIs in the preceding list appear in italics.) To see the DLCIs, use dspcon, as in the following example:
dspcon 6.1x3 alpha 7.2x3
The preceding shows one screen for the whole bundle then an additional screen for each connection in the bundle. The assigned DLCIs appear in these individual connection display screens.
A non-Frame Relay data connection (such as HDLC or SDLC) that is routed through Frame Relay cards can bypass a router or take advantage of DFM at higher data rates. The format slot.port.* identifies a frame forwarding connection. An example is:
addcon 11.2.* alpha 12.3.* 2
The "*" indicates to the node that a DLCI is meaningless.
For any Frame Relay card set that has a maximum frame length of 4510 bytes, the use and type of signaling protocol you may have (optionally) specified with the cnffrport command results in a limit on the possible number of connections per physical or logical port. The maximum number of connections per port for each protocol is as follows:
The addcon command does not prevent you from adding more than the maximum number connections on a port. If the number of connections is exceeded, the particular LMI does not work on the port, the full status messages that result are discarded, and LMI timeouts occur on the port. A port failure results and subsequently leads to a-bit failures in segments of the connection path.
Add connection
addcon <local_channel> <remote_node> <remote_channel> [con_type] <frame_relay_class | [individual parameters]> [route_avoid]
delcon, dncon, dspcon, dspcons, upcon
| Privilege | Jobs | Log | Node | Lock |
1-2 | Yes | Yes | IGX, (and BPX for service internetworking | Yes |
addcon 6.1.100 beta 6.2.200 3
addcon 6.1 101 delta 4.1.102 2
addcon 4.1.100 beta 6.2.101 4
addcon 4.1.200 gamma 5.1.300 1
Execute the preceding commands at node Alpha to configure the following network shown in Figure 8-1.
addcon 9.1.200 gamma 8.1.300 1
Add a connection between the user-device at alpha port 9.1 and the user-device at gamma port 8.1. The user-device at alpha refers to the connection using local DLCI 200. The user-device at gamma refers to this connection using local DLCI 300. The DLCIs have only local significance, so a DLCI must apply to only one connection.
alpha TRM YourID:1 IGX 8420 9.2 Aug. 23 1998 10:12 PST
Local Remote Remote Route
Channel NodeName Channel State Type Compression Code Avoid COS O
5.1 beta 25.1 Ok 256 7/8 0 L
9.1.100 gamma 8.1.200 Ok fr 0 L
9.1.200 gamma 8.1.300 Ok fr 0 L
9.2.400 beta 19.2.302 Ok fr 0 L
14.1 gamma 15.1 Ok v 0 L
Last Command: addcon 9.1.200 gamma 8.1.300 1
Next Command:
addcon 9.1.100 beta 6.2.300 2
Add another connection at local port 9.1. A DLCI of 100 is used at the local node. A DLCI of 300 can be used at both beta gamma because the DLCIs have only local significance.
addcon 6.1.80 beta 9.2.79 2
addcon 6.1.81 gamma 4.1.79 1
addcon 4.1.80 beta 6.2.81 5
The network to configure in this example is as in Figure 8-2.
addcon 8.1x3 alpha 19.2x4 1
Add a bundle of connections between Frame Relay ports 8.1-3 on node gamma and 19.2-4 on node alpha. For this bundle, the network routes traffic between gamma port 8.2 and alpha port 19.2.
pubsigx3 VT SuperUser IGX 8410 9.2 Aug. 3 1998 19:41 GMT
Local Remote Remote
Channel NodeName Channel State Type Compress Code COS
8.1x3 alpha 19.2x4 Ok fr
This Command: addcon 8.1x3 alpha 19.2x4 1
Add these connections (y/n)?
addcon 8.2.* alpha 19.2.* 1
Add a frame forwarding connection between the local node's port 8.2 and 19.2 on node alpha.
Locals Remote Remote Route
Channel NodeName Channel State Type Compression Code Avoid COS O
6.1 beta 25.2 Ok 256 7/8 0 R
8.1.200 alpha 9.1.100 Ok fr 0 R
8.2.300 beta 19.1.101 Ok fr 0 R
15.1 alpha 14.1 Ok v 0 R
This Command: addcon 8.2.* alpha 19.2.* 1
Add these connections (y/n)?
addcon 8.3.101 beta 19.3.201 7 * * * * 30/30 * * Y 80/80
Parameters specified by Frame Relay class 7 for this connection are modified by substituting 30 for Cmax in both directions, enabling ForeSight, and reducing percent utilization from 100% to 80%.
gamma TRM YourID:1 IGX 8410 9.2 Aug. 23 1998 12:10 CST
Local Remote Remote Route
Channel NodeName Channel State Type Compression Code Avoid COS O
6.1 beta 25.2 Ok 256 7/8 0 R
8.1.200 alpha 9.1.100 Ok fr 0 R
8.2.300 beta 19.1.101 Ok fr 0 R
15.1 alpha 14.1 Ok v 0 R
Last Command: dspcons
Next Command: addcon 8.3.101 beta 19.3.201 7 * * * * 30/30 * * Y 80/80
| Parameter | Description |
|---|---|
local channel | Specifies the local channel to connect in the format: slot.port.DLCI | x port | .* On an FRP or FRM, the range for port is 1-24 or 1-31. On a UFM-C, the range for port is 1-250. (For connections on a UFM-C, line is not necessary because of the port-to-line mapping through addfrport). For a UFM-U, the range for port is 1-12 for V.35 or X.21 and 1-4 for HSSI. The range for DLCI is 16-1007. |
node | Specifies the name of the remote node at the other end of the connection. |
remote channel | Specifies the connection at the far end. For Frame Relay termination points, use: slot.port.DLCI | x port | .* If the far end is an ATM termination (as in interworking), use: slot.port.vpi.vci where vpi has a range of 0-255, and vci has a range of 1-4095. One exception to these ranges is the ALM/A, which has a vci range of 0-255. Another exception is an interface shelf (which uses Annex G signaling) in a tiered network, as follows:
Access devices such as the Cisco 3800 use the following format for the remote channel specification: <slot.port> <access_device_connection_ID> where slot is the slot number of the FTC or FTM card, port is the port number, and access_device_connection_ID is in the range 1-252. |
Frame Relay class | Specifies a Frame Relay class. Entering a Frame Relay class is a shortcut for specifying bandwidth parameters. You must enter a Frame Relay class, but then you can modify any of the bandwidth parameters specified by the class. To do so, do not press Return after you type the class number but continue typing either a value for the parameter or a * to keep the current value. The system does not display the parameters, but the description of the frp_bw parameters in the"Optional Parameters" table that follows shows the order and ranges of the parameters you can specify. For more details on the parameters and the Frame Relay classes, refer to "Using Frame Relay Classes " earlier in this chapter. |
| Parameter | Description |
|---|---|
con_type | Specifies the type of ATM-to-Frame Relay service interworking. (If the connection is Frame Relay-to-Frame Relay, the network selects any necessary interworking.) The possible con_type entries are atft and atfx. To specify service interworking in transparent mode, type "atft." To specify service interworking in translation mode, type "atfx." In translation mode, a standard set of encapsulation protocols are translated. If system software does not recognize an encapsulation protocol for an atfx connection, it generates one of two Frame Relay endpoint statistics: rcvFramesDscdUnknownProtocol or xmtFramesDscdUnknownProtocol. |
frp_bw | Optionally specifies individual bandwidth parameters. The parameter name "frp_bw" is the label for the bandwidth parameters described here. The slash (/) between the repeated parameter name shows that you can specify a value for each direction. (FST is the exception.) Two parameters can be either the (default) Cisco versions or the Frame Relay Forum standard parameters. To switch between Cisco and Frame Relay Forum, use the cnfsysparm command. Note that all parameters you select with cnfsysparm are network-wide and not confined to the current connection addition. The switchable parameters are as follows: Cisco Parameters Standard Parameters PIR (peak information rate) Be (excess burst) VC_Q (VC queue depth) Bc (committed burst) When you are using the Cisco parameter set, the names and order of specification are as follows: MIR/MIR, CIR/CIR, VC_Q/VC_Q, PIR/PIR, Cmax/Cmax ECNQ_thresh/ECNQ_thresh, QIR/QIR, FST, %utl/%utl When you are using the parameters with the two Frame Relay Forum versions, the names and order of specification are as follows: MIR/MIR, CIR/CIR, Bc/Bc, Be/Be, Cmax/Cmax, ECNQ_thresh/ECNQ_thresh, QIR/QIR, FST, %utl/%utl For the definition of each parameter and important information on setting CIR=0, refer to the section titled "Using Frame Relay Classes " earlier in this chapter. |
avoid | Specifies the type of trunk or route to avoid for the connection. The default is no avoidance. To specify an avoid value, type it after the Frame Relay class or — if you override the Frame Relay class — after the frp_bw values. Be sure to include the asterisk (*). The avoid parameters are: *s Avoid satellite trunks. *t Avoid terrestrial trunks. *z Avoid trunks using zero-code suppression techniques that modify any bit |
Activates a logical Frame Relay port on a channelized FRP, FRM, or UFM card set. Only T1 or E1 lines carry channelized Frame Relay traffic, so the addfrport command does not apply to a Port Concentrator Shelf or front cards with a V.35, X.21, or HSSI interface.
The addfrport command adds a logical Frame Relay port by using the slot number of the FRM and the DS0/timeslots that make up the logical port. On a UFM, the logical ports span the whole range of physical lines: you associate the logical ports to the lines as needed, then include the DS0s as the last field of the argument. Table 8-2 lists the error and warning messages for addfrport.
| Messages | Reason for Message |
|---|---|
"Slot is out of range" | Line number not correct for T1/E1. You cannot add slots 0-31, that is, you cannot have a port at E1 speed. The maximum you can get is 31 slots (1984) using CCS (Common Channel Signalling) since slot 0 is used for FAS, etc. |
"Line must first be upped" | Line is down. |
"invalid channel range" | Channel is out of the range 1-24 or 1-31 (16 is a reserved channel for E1). |
"Channel is busy" | Channel is already assigned to a logical port. |
"You cannot use signaling channel 16" (E1) | CAS channel 16 included in logical port (E1). CCS permits the use of channel 16 but not in all countries. |
"Invalid rate" | Entered rate is not 56 Kbps or 64 Kbps. |
"This rate is available for single channel only" | Entered rate is 56 Kbps, but multiple channels specified. |
Add Frame Relay port T1/E1
For FRP or FRM card sets: addfrport <slot.port> [DS0 channel] [56 | 64]
For UFM-C card sets: addfrport <slot.port> <line.DS0_channel>
upln (upcln is the obsolete name), delfrport, cnffrcport, cnffrport, dspfrport
| Privilege | Jobs | Log | Node | Lock |
1-2 | Yes | Yes | IGX | Yes |
addfrport 21.9 -15
Add a single Frame Relay port that occupies DS0s (timeslots) in the range 9-15. For a T1 line, this channel rate is 7 x 64 Kbps = 448 Kbps, as the screen example shows. The card is an FRP.
gamma TRM YourID:1 IGX 8410 9.2 Aug. 15 1998 17:28 CST
Port configuration for FRP 21
From Chan Speed Interface State
1 9-15 448 FRI T1 INACTIVE
Last Command: addfrport 21.9-15
Next Command:
| Parameter | Description |
|---|---|
slot.port (FRP or FRM series) slot.port line.DS0 channel (for UFM-C series) | Specifies the FRI T1 or E1 line number and the logical port number. For a UFM-U, specifies the physical slot and port. For an example of a T1 or E1: 8.12 is physical slot 8 and timeslot (or channel) 12. For the UFM card sets, this parameter specifies the slot and logical port, the physical line (the connector), and one or more contiguous DS0s. The range of logical ports is 1-250. The range of lines is 1-4 for the UFM-4C and 1-8 for the UFM-8C. Note the space between the port and line. |
| Parameter | Description |
|---|---|
- chan | Specifies that multiple DS0/timeslots should form one logical port. A "-" separates the starting and ending DS0s/timeslots). Timeslots must be contiguous. An example is addfrport 8.1-5. The system uses the lowest DS0/timeslot number as the logical port number and shows this in related displays. |
rate | Specifies the rate of a single, logical port. By default, a single logical port (or channel) is 64Kbps. A single DS0 (timeslot) may be 56 Kbps or 64 Kbps. If you do not enter a rate, the default is 64 Kbps. |
The cnfdch command lets you configure a super-rate data connection has idle code suppression (ICS) enabled or disabled. All super-rate data connections will have the Idle Code Suppression (ICS) state set to "disabled" unless it has been specifically configured with the new cnfdch command or through SNMP. The cnfdch screen is identical to that of dspchcnf.
The Idle Code Suppression feature supported in this release provides a way to stop fast packet generation on an Nx64 super-rate PVC connection when the connected PBX has terminated a video call. No video traffic will be generated when a video call has terminated.
Configuration is done for each of channel of an endpoint. Upon changes in the state of Idle Code Suppression of a connection, no network message will be sent to the other end. You can choose to configure the other end if ICS is supported there also. To maximize the benefit of this feature, you should enable ICS on both sides of a connection.
The cnfdch command prompts you to enable or disable idle code suppression with the following prompt:
Enable or Disable Idle Code Suppression (e/d)?[d]: The cnfdch command is available for level 2 users and above; that is, you must have at least privilege level 2 or above to use this command. Use it to configure a channel before you add a connection. If some of the specified channels do not yet have any connection attached, those channels will be initialized to a data type channel.
The configuration will stay the same even if connections are removed and added again.
The cnfdch command will be blocked at the CLI if one or more of the specified channels is carrying a voice connection (including t-type).
The switch software provides an interface to configure channels to enable or disable idle code suppression for super-rate data connections, In turn, the switch software tells the UVM/CVM/CDP card if idle code suppression should be used on each of the super-rate connections.
Because there are multiple channels involved in an Nx64 data connection, the idle code suppression configuration of the first channel in the Nx64 channel will be used for the entire connection. The configuration of the other channels in the bundle will be ignored in channel programming or on the dspcons screen.
To inter-work with HDM/LDM/SDP/LDP cards, idle code suppression on a UVM/CVM/CDP channel will be turned off for any super-rate connection that also terminates on HDM/LDM/SDP/LDP.
Configures data connection to have ICS enabled/disabled.
prtchcnf
| Privilege | Jobs | Log | Node | Lock |
2-6 | No | No | IGX | No |
dspchcnf 31.1.8
Display configuration values for channel 9.1.3-5
sw176 TRM StrataCom IGX 16 9.2.a2 Apr. 3 1998 17:28 PST
Maximum EIA % DFM Pattern DFM Idle Code PreAge
From 9.1.3 Update Rate Util Length Status Suppr (usec)
9.1.3-5 - - - - Disabled 0
This Command: cnfdch 9.1.3-5
dspchcnf [parameters]
| Parameter | Description |
|---|---|
channel(s) | slot.line.chan for UVM or line.chan for CVM/CDP. You can enter a range of channels. |
ch_ics_state | Channel idle code suppression state: d for disabled; e for enabled. |
Clears port statistics for FRM-2 or FRP-2 physical ports connected to a Port Concentrator Shelf. To see the statistics that you clear with clrfrcportstats, execute dspfrcportstats. The controller card collects statistics from the FRM-2 or FRP-2 once per minute. Because clrfrcportstats clears statistics on the controller card, it may not clear statistics generated within the last minute.
Clear FRC/FRM port statistics
clrfrcportstats <slot.port | *>
dspfrcportstats
| Privilege | Jobs | Log | Node | Lock |
1-5 | Yes | Yes | IGX | No |
| Parameter | Description |
|---|---|
slot,port | * | Slot and port of the physical port. The range for port is 1-4. An asterisk (*) specifies all FRC-2/FRM-2 physical ports. |
Sets the channel priority for a Frame Relay connection. The Channel Priority feature permits some Frame Relay connections to receive a higher priority within a port queue than other Frame Relay traffic on a per-connection basis. The default priority is low. You can configure Frame Relay LMI ports to communicate the priority to a router. You must change the priority on both ends of a connection.
Configure Frame Relay channel priority
cnfchpri <connection> <priority>
dspchcnf
| Privilege | Jobs | Log | Node | Lock |
1-2 | Yes | Yes | IGX | Yes |
cnfchpri 9.1.100 h
Configure a high priority for Frame Relay connection 9.1.100.
alpha TRM YourID:1 IGX 8410 9.2 Aug. 15 1998 16:00 PST
Conn: 9.1.100 gamma 8.1.200 fr
MIR CIR VC Q Depth PIR Cmax ECN QThresh QIR FST
9.6/9.6 9.6/9.6 5/5 256/256 10/10 65535/65535 9.6/9.6 n
% Util: 100/100
Owner: LOCAL Restriction: NONE COS: 0 Status: OK
Group: NONE Priority: H TestRTD: 0 msec
Path: alpha 14--13beta 15--15gamma
Pref: Not Configured
alpha 9.1.100 gamma 8.1.200
FRP: OK FRP: OK
FRI: OK FRI: OK
Last Command: cnfchpri 9.1.100 h
Next Command:
| Parameter | Description |
|---|---|
channels | Specifies the channel or range of channels. The format is slot.port.DLCI. |
h | l | The priority: h = high; l = low. |
Configures a system-wide Frame Relay connection class. Refer to the "Using Frame Relay Classes " section at the beginning of this chapter for a definition of a Frame Relay class. The following are characteristics of this command:
Configure Frame Relay class
cnffrcls <class_num> [<BW params>] [<description>]
addcon, dspfrcls
| Privilege | Jobs | Log | Node | Lock |
1-2 | Yes | Yes | IGX | Yes |
cnffrcls 1 *
Configure Frame Relay class #1 to operate with ForeSight. The list of * parameters leaves those parameters unchanged, and "y" enables ForeSight. Because the utilization and description parameters have not been entered, any existing values for these parameters remain in effect.
alpha TRM YourID:1 IGX 8410 9.2 Aug. 15 1998 16:05 PST
Frame Relay Connection Classes
# MIR CIR VC Q Depth PIR Cmax ECN QThresh QIR FST
.6/9.6 9.6/9.6 65535/65535 128/128 10/10 65535/65535 9.6/9.6 y
% Util: 100/100 Description: "Default 9.6"
2 19.2/19.2 19.2/19.2 65535/65535 */* 10/10 65535/65535 19.2/19.2 n
% Util: 100/100 Description: "Default 19.2"
3 16/16 16/16 65535/65535 */* 10/10 65535/65535 16/16 n
% Util: 100/100 Description: "Default 16"
4 32/32 32/32 65535/65535 */* 10/10 65535/65535 32/32 n
% Util: 100/100 Description: "Default 32"
5 56/56 56/56 65535/65535 */* 10/10 65535/65535 56/56 n
% Util: 100/100 Description: "Default 56"
Last Command: cnffrcls 1 * * * * * * * y
Continue (y): y
alpha TRM YourID:1 IGX 8410 9.2 Aug. 15 1998 16:03 PST
Frame Relay Connection Classes
# MIR CIR VC Q Depth PIR Cmax ECN QThresh QIR FST
6 64/64 64/64 65535/65535 */* 10/10 65535/65535 64/64 n
% Util: 100/100 Description: "Default 64"
7 128/128 128/128 65535/65535 */* 10/10 65535/65535 128/128 n
% Util: 100/100 Description: "Default 128"
8 192/192 192/192 65535/65535 */* 10/10 65535/65535 192/192 n
% Util: 100/100 Description: "Default 192"
9 256/256 256/256 65535/65535 */* 10/10 65535/65535 256/256 n
% Util: 100/100 Description: "Default 256"
10 512/512 512/512 65535/65535 */* 10/10 65535/65535 512/512 n
% Util: 100/100 Description: "Default 512"
Last Command: cnffrcls 1 * * * * * * * y
Next Command:
| Parameter | Description |
|---|---|
frp_bw | Optionally specifies individual bandwidth parameters. The parameter name "frp_bw" is the label for the bandwidth parameters described here. The slash (/) between the repeated parameter name shows that you can specify a value for each direction. (FST is the exception.)Two parameters can be either the (default) Cisco versions or the Frame Relay Forum standard parameters. To switch between Cisco and Frame Relay Forum, use the cnfsysparm command. Note that all parameters you select with cnfsysparm are network-wide and not confined to the current connection addition. The switchable parameters are as follows: Cisco Parameters Standard Parameters PIR (peak information rate) Be (excess burst) VC_Q (VC queue depth) Bc (committed burst) When you are using the Cisco parameter set, the names and order of specification are as follows: MIR/MIR, CIR/CIR, VC_Q/VC_Q, PIR/PIR, Cmax/Cmax ECNQ_thresh/ECNQ_thresh, QIR/QIR, FST, %utl/%utl When you are using the parameters with the two Frame Relay Forum versions, the names and order of specification are as follows: MIR/MIR, CIR/CIR, Bc/Bc, Be/Be, Cmax/Cmax, ECNQ_thresh/ECNQ_thresh, QIR/QIR, FST, %utl/%utl For the definition of each parameter and important information on setting CIR=0, refer to the section titled "Using Frame Relay Classes " earlier in this chapter. |
description | Any text string up to 25 characters terminated by a <RET>. This is used to provide the user with a descriptive identifier for the class. |
Configures bandwidth parameters or enables ForeSight for an individual Frame Relay connection. Because you normally specify bandwidth parameters through the Frame Relay class or by the option of overriding bandwidth parameters through specific arguments for addcon, using cnffrcon tends to be used for instances where you need to customize a single connection's bandwidth parameters.
Be sure the MIR you specify is appropriate. If the MIR is too high, bandwidth is wasted. If it is too low, the connection may drop data. The statistics reports are the best source of information to help you determine the appropriate MIR.
The PIR usually is set to the port speed. You can specify a lower PIR if other constraints on the data generation rate exist. Be sure the PIR you specify is appropriate. If it is too low, frames are dropped. If it is too high, bandwidth may be wasted unless the network has ForeSight.
You should change the Cmax, VC Q, and ECN Q values by only knowledgeable users and when tuning data is available to support the determination of appropriate values. These values affect system buffering resources, so any change from the defaults requires caution. Refer to the Cisco WAN Switching System Overview for more details on connection parameters.
If the connection type has ForeSight (FST = y), the result of the last test round trip delay command (Test RTD) is displayed. Note that this is not the current RTD but the result of the last, user-specified test. High or low connection priority is displayed for both standard Frame Relay connections and ForeSight connections.
The node checks the bandwidth parameters to promote efficient use of network bandwidth. The following messages reflect the checks on bandwidth usage.
Error | Min cannot exceed peak. |
Warning | Min exceeds this port's speed. |
Warning | Sum of mins exceeds port's speed. |
Warning | Peak exceeds this port's speed. |
Warning messages are informational and do not indicate that the command is failing to execute. Error messages indicate the command is not executing.
When you specify the frp_bw parameters, enter all changes (or unchanged values indicated by an asterisk) on the line. You must specify either a change or a place-holder (*) up to at least the last changed value (after which place-holders are unnecessary). Decide on any changes before starting this command. The parameters section of this command description lists frp_bw parameters. The section "Using Frame Relay Classes " at the beginning of this chapter describes the parameters.
Configure Frame Relay Connection
cnffrcon <channel> [bandwidth_parameters]
addcon, dspcon
| Privilege | Jobs | Log | Node | Lock |
1-2 | Yes | Yes | IGX | Yes |
cnffrcon 8.1.200
Configure Frame Relay connection 8.1.200.
gamma TRM YourID:1 IGX 8410 9.2 Aug. 15 1998 17:28 CST
Conn: 8.1.200 alpha 9.1.100 fr
MIR CIR VC Q Depth PIR Cmax ECN QThresh QIR FST
9.6/9.6 9.6/9.6 5/5 256/256 10/10 65535/65535 9.6/9.6 n
% Util: 100/100
Owner: REMOTE Restriction: NONE COS: 0 Status: OK
Group: NONE Priority: L TestRTD: 0 msec
Path: gamma 15--15beta 13--14alpha
Pref: Not Configured
gamma 8.1.200 alpha 9.1.100
FRP: OK FRP: OK
FRI: OK FRI: OK
Last Command: cnffrcon 8.1.200
Next Command:
| Parameter | Description |
|---|---|
channel | Specifies the channel to configure connection parameters. The command configures connection information for one channel at a time. You cannot specify a set of channels. The channel has the following format: slot.port.DLCI |
| Parameter | Description |
|---|---|
bandwidth_para- | Specifies the bandwidth parameters in the following format: MIR/MIR, CIR/CIR, VC_Q/VC_Q, PIR/PIR, Cmax/Cmax ECNQ_thresh/ECNQ_thresh, QIR/QIR, FST, %utl/%utl See "Using Frame Relay Classes " in this chapter for information on the bandwidth parameters. A slash indicates you can specify a value for each direction. FST is either ForeSight enable (y) or disable (n). A "*" is a place-holder for a parameter you do not change. |
Configures the port speed and percent of utilization on the concentrated link of a Port Concentrator Shelf (PCS). This is not a standard command. Primarily, you would use cnffrcport to adjust the rate on the concentrated link due to some unusual system configuration.
Because this command applies to the FRC interface (the concentrated link) rather than the user port for the CPE, the port number and the range of speeds is the same as that of the FRP or FRM card. Thus, the port numbers are 1-4 with rates varying from 56 Kbps through 2 Mbps. During port configuration, a prompt for each parameter appears. To keep the current value of the parameter, press the Return key without typing anything.
Configure Frame Relay port
cnffrcport <slot.port> <percent utilization>
upfrport, dnfrport, dspfrport, dspcd
| Privilege | Jobs | Log | Node | Lock |
1-2 | Yes | Yes | IGX | Yes |
cnffrcport 6.1 512 88
Reconfigure PCS port 6.1 to have a speed of 512 Kbps and a concentrated link utilization of 88%. (Note that executing dspcd for this slot would show a port count of 44, which indicates that the card set supports a PCS. The Configured Clock of 512 Kbps by itself does not indicate a PCS because a standard FRP-2 or FRM-2 also supports this rate.
minnow TN SuperUser IGX 8410 9.2 Aug. 30 1998 10:16 PST
Physical Port: 6.1 [INACTIVE]
Interface: FRI-X21 DCE Configured Clock: 512 Kbps
Clocking: Normal Measured Rx Clock: 0 Kbps
Min Flags / Frames 1
Port ID 1022
Port Queue Depth 65535 OAM Pkt Threshold 3 pkts
ECN Queue Threshold 65535 T391 Link Intg Timer 10 sec
DE Threshold 100 % N391 Full Status Poll 6 cyl
Signalling Protocol None EFCI Mapping Enabled No
Asynchronous Status No CLLM Enabled/Tx Timer No/ 0 msec
T392 Polling Verif Timer 15 IDE to DE Mapping Yes
N392 Error Threshold 3 Interface Control Template
N393 Monitored Events Count 4 Lead I
Communicate Priority No State ON
Upper/Lower RNR Thresh 75%/ 25% Concentrated Link Util 88%
Last Command: cnffrcport 6.1 512 88
Next Command:
| Parameter | Description |
slot.port | Specifies the card slot and port number. Because the port number is that of the concentrated link rather than the user port number, the range is 1-4 (not 1-44). |
speed | Specifies the port clock speed for a 2.0 Mbps FRP-2 or FRM-2. The display shows the configured speed as Configured Clock and the actual speed as Measured Rx Clock. The available speeds are: 1 port (selected speeds, 56-2048 Kbps) |
utilization | Specifies the percent of utilization of the concentrated link. |
Configures the parameters of a Frame Relay port. The cnffrport command applies to the UFM/UFI, FRP/FRI, FRM/FRI, and FRM-2/FRP-2. (Note that a less commonly used command also exists for the concentrated link between the PCS and FRM-2 or FRP-2: cnffrcport.)
During port configuration, a prompt for each parameter appears. To keep the current value of the parameter, press the Return key without typing any characters. When a parameter is not configurable for an application, the parameter appears shaded or with dashed lines. You can mix the data rate for each of the ports if the total for all ports does not exceed the maximum composite data rate that the card set supports. Table 8-12 shows the supported data rates for individual T1 and E1 lines.
| Data Rates at 56 Kbps Increments | Data Rates at 64 Kbps Increments | ||||||
|---|---|---|---|---|---|---|---|
56 | 112 | 168 | 224 | 64 | 128 | 192 | 256 |
280 | 336 | 392 | 448 | 320 | 384 | 448 | 512 |
504 | 560 | 616 | 672 | 576 | 640 | 704 | 768 |
728 | 784 | 840 | 896 | 832 | 896 | 960 | 1024 |
952 | 1008 | 1064 | 1120 | 1088 | 1152 | 1216 | 1280 |
1176 | 1232 | 1288 | 1344 | 1344 | 1408 | 1472 | 1536 |
1400 | 1456 | 1512 | 1568 | 1600 | 1664 | 1728 | 1792 |
1624 | 1680 | 1736 | 1792 | 1856 | 1920 | 1984 | 2048 |
Table 8-13 shows the available data rates on a single, PCS user-port. For the FRP-2 and FRM-2 cards, the maximum composite data rate over the 44 logical, user-ports is 1.792 Mbps.
| Data Rates in Kbps | |||||||
|---|---|---|---|---|---|---|---|
9.6 | 14.4 | 16 | 19.2 | 32 | 38.4 | 48 | 56 |
64 | 112 | 128 | 168 | 192 | 224 | 256 | 280 |
320 | 336 | 384 |
|
|
|
|
|
For a PCS, some additional rules for assigning data rates to the 44 ports apply:
This section introduces the implementation of two signaling timers and related parameters you can specify through the cnffrport command.
Periodically, devices use signaling to request the status of other, connected devices or networks. The signaling can be a simple confirmation of the other device's existence or more detailed information, such as the DLCIs, bandwidth, and state of all PVCs. The signaling described here occurs between:
Periodically, Frame Relay ports within the network transmit a Status Enquiry and wait for a Status response. These exchanges occur across the UNI and the NNI. At the UNI, the user-equipment periodically sends a series of Status Enquiries and awaits a Status response for each enquiry. At the NNI of any network, a Frame Relay port can generate Status Enquiries and, at alternate times, receive Status Enquiries. In this way, the signaling between networks mirror each other. (Figure 8-3 shows the three possible exchanges.) The timers for Status Enquiry and Status response and other, related parameters are the:
In the preceding list, an event is either a Status Enquiry or a Status response. The meaning of the event depends on whether the link integrity timer or the polling verification timer is waiting for the event. The link integrity timer waits for Status responses. The polling verification timer waits for Status Enquiries.
Most Status Enquiries contain only a sequence number. After sending these simple Status Enquiries, the polling device checks for the sequence number. Periodically, a full status polling cycle takes place, in which the polling device waits for all applicable information, such as the status of all connections that cross the NNI. For signaling across the UNI, the Frame Relay Forum has recommended a full status polling cycle at every sixth polling cycle. The Frame Relay Forum has not recommended a frequency for the NNI. The cnffrport command lets you select a frequency in the range of once every 1-10 polling cycles.
The Frame Relay port or user-device counts a user-specified number of errors out of a user-specified number of attempts before it signals a Port Communication Failure. These parameters are the error threshold and the monitored events count, respectively. The defaults for these parameters are 3 and 4, respectively. To use the defaults in an example: if 3 out of 4 events are either missing or erroneous within the specified time period, the port signals a Port Communication Failure (a minor alarm).
An event has a user-specified amount of time to arrive. The allowed time period for the arrival of a valid event is the number of seconds you assign to a timer. If an enquiry or response is missing or bad within the timer value, the event is failed. Again, using all default values in an example: if the polling verification timer is 15 seconds and no Status Enquiry arrives within that time, the port records a missing Status Enquiry. If no Status Enquiry arrives during the next two 15-second periods, the port signals a Port Communication Failure. In the UNI example in the figure, the third Status Enquiry does not arrive. Note that each time a Status Enquiry arrives, the polling verification timer restarts counting at 0 seconds rather than waiting until the specified number of seconds has elapsed.
Whether the port is on a UNI or NNI, the polling verification timer setting must be longer than the link integrity timer. (Refer to the forthcoming cnffrport parameters table for values.) You cannot set the link integrity timer for the user-equipment with cnffrport. Usually, the link integrity timer on user-equipment is 10 seconds, which you can verify by executing dspportstats and counting the number of seconds between statistical updates. On the NNI, you can set both timers (they use either Annex A or Annex D).
The data rates available with the 1 Mbps FRI are:
| Port Data Rates in Kbps for 1Mbps FRI
| |||
|---|---|---|---|
1024 | 512 | 256 | 128 |
896 | 448 | 224 | 112 |
768 | 384 | 192 | 64 |
672 | 336 | 168 | 56 |
The rules for assigning data rates to the four ports when using the 1 Mbps FRI are:
Configure Frame Relay port
cnffrport <slot.port> <line.DS0_range> <port queue depth> <ecn queue threshold>
<de threshold> <signaling protocol> [protocol parameters]
cnffrport <slot.port> <port type> <port queue depth> <ecn queue threshold>
<de threshold> <signaling protocol> [protocol parameters]
cnffrport <slot.port> <port queue depth> <ecn queue threshold> <de threshold>
<signaling protocol> [protocol parameters]
cnffrport <slot.port> <speed> <port queue depth> <clocking> <de_threshold> <min-flags-bet-frames> <ECN q_threshold> <port ID> <signaling protocol y/n>
[protocol parameters]
addfrport, upfrport, dnfrport, dspfrport
| Privilege | Jobs | Log | Node | Lock |
1-2 | Yes | Yes | IGX | Yes |
cnffrport 3.1 48000 48000 100 n N Y 1
Change Frame Relay port 3.1 to have queue depths of 48000. The interface in this example is a T1.
pubsigx1 TN SuperUser IGX 32 9.2 Sep. 10 1997 16:25 GMT
Port: 3.1 [ACTIVE ]
Interface: FRI-T1 Configured Clock: 64 Kbps
Clocking: None Measured Rx Clock: None
Min Flags / Frames 1
Port ID - Channel Range 1
Port Queue Depth 48000 OAM Pkt Threshold 3 pkts
ECN Queue Threshold 48000 T391 Link Intg Timer 10 sec
DE Threshold 100 % N391 Full Status Poll 6 cyl
Signalling Protocol None EFCI Mapping Enabled No
Asynchronous Status No CLLM Enabled/Tx Timer No/ 0 msec
T392 Polling Verif Timer 15 IDE to DE Mapping Yes
N392 Error Threshold 3 Channel Speed 64
N393 Monitored Events Count 4
Communicate Priority No
Upper/Lower RNR Thresh 75%/ 25%
Last Command: cnffrport 3.1 48000 48000 100 n N Y 1
Next Command:
cnffrport 5.1 256 n 12000 10000 100 a N N 15 3 4 3 y y 100 Y 1
Change queue depths for port 8.1. An explanation of the screen appears after the screen example.
padma VT SuperUser IGX 8410 9.2 Sep. 10 1998 16:39 GMT
Port: 5.1 [ACTIVE ]
Interface: FRI-V35 DCE Configured Clock: 256 Kbps
Clocking: Normal Measured Rx Clock: 256 Kbps
Min Flags / Frames 1
Port ID 0
Port Queue Depth 12000 OAM Pkt Threshold 3 pkts
ECN Queue Threshold 10000 T391 Link Intg Timer 10 sec
DE Threshold 100 % N391 Full Status Poll 6 cyl
Signalling Protocol Annex A UNI EFCI Mapping Enabled Yes
Asynchronous Status No CLLM Enabled/Tx Timer Yes/100 msec
T392 Polling Verif Timer 15 IDE to DE Mapping Yes
N392 Error Threshold 3 Interface Control Template
N393 Monitored Events Count 4 Lead CTS DSR DCD
Communicate Priority No State ON ON ON
Upper/Lower RNR Thresh 75%/ 25%
Last Command: cnffrport 5.1 256 NORMAL 0 12000 10000 100 a N N 15 3 4 3 y y 100
Y 1
Next Command:
The screen in Example 2 shows the following:
♦ Port Speed (configured, measured) | 256 Kbps | The screen displays both the configured clock speed and the measured clock speed—256 Kbps for both in this case. |
♦ Clocking (type) | Normal | Of the two clocking types, the interface uses normal clocking. |
♦ Port ID | 0 | The optional Port ID has not been specified. |
♦ Port Queue Depth | 12000 | Depth of port queue is set at 12000 bytes. |
♦ ECN Queue Depth | 10000 | Port queue must reach 10000 bytes before FECN and BECN bits are set. |
♦ DE Threshold | 100 | Port buffer must be 100% full before DE frames are dropped. |
♦ Signaling Protocol | Annex A | The selected protocol for the UNI. |
♦ Asynchronous Status | N | No asynchronous messages to user-device; wait for polling from user-device. |
♦ Polling Verify Timer | 15 | 15 seconds heartbeat period. |
♦ Error Threshold | 3 | 3 failures trigger port communication failure. |
♦ Monitored Events Count | 4 | 4 events are monitored. |
♦ Communicate Priority | N | Do not communicate port priority to user-device. |
♦ Upper RNR Threshold | 75 | 75% of buffer capacity triggers receiver not ready condition. |
♦ Lower RNR Threshold | 25 | 25% of buffer capacity clears a receiver not ready condition. |
♦ Minimum Flags/Frame | 1 | One flag exists for each FR data frame. |
cnffrport 13.1
Configure the parameters for the newly upped V.35 port at 13.1. In this case, the only change is the port type: the interface becomes a DTE in this example.
sw180 TN SuperUser IGX 16 9.2 July 30 1997 00:09 GMT
Port: 13.1 [ACTIVE ]
Interface: V35 DCE Configured Clock: 256 Kbps
Clocking: Normal Measured Rx Clock: 0 Kbps
Port ID 0 Min Flags / Frames 1
Port Queue Depth 65535 OAM Pkt Threshold 3 pkts
ECN Queue Threshold 65535 T391 Link Intg Timer 10 sec
DE Threshold 100 % N391 Full Status Poll 6 cyl
Signalling Protocol None EFCI Mapping Enabled No
Asynchronous Status No CLLM Enabled/Tx Timer No/ 0 msec
T392 Polling Verif Timer 15 IDE to DE Mapping Yes
N392 Error Threshold 3 Interface Control Template
N393 Monitored Events Count 4 Lead CTS DSR DCD
Communicate Priority No State ON ON ON
Upper/Lower RNR Thresh 75%/ 25%
Last Command: cnffrport 13.1 DTE 256 NORMAL 0 65535 65535 100 n N N Y
Next Command:
| Parameter | Description |
|---|---|
slot.port | Specifies the logical port on the FRP, FRM, or UFM-U in the format slot.port. For a T1/E1 line on an FRM or FRP, port is a logical number. For a UFM-C, the range for port is 1-250. (See the description of slot.port line in the Cisco IGX 8400 Series Reference manual.) For a Port Concentrator Shelf, port is to the logical port in the range 1-44. |
port type For port type on a | Specifies whether a port on a UFM-U is DCE or DTE. The prompt appears if the system detects a UFM-U. The default is DCE. For an FRM or FRP, "port Type" is display-only because jumper blocks on the back cards set the mode. When you use cnffrport in a job, the "Enter mode (line or port)" prompt follows slot.port. Note that this mode is the interface type of the Frame Relay port rather than the mode of the UFM-U. Valid entries are HSSI, V35, X21, PORT (PORT is generically "unchannelized"), or LINE (LINE indicates T1 or E1). If the front card is a UFM-U, a subsequent prompt asks you to specify DCE or DTE. |
port type (For port type on | Port type for a PCS tells switch software whether the port is V.35, V.11 or V.28. Port type for a PCS does not actually configure the port: to configure the port, you must install the appropriate card in the PCS. See the port type description for the UFM-U for information on cnffrport in a job. |
interface type | Specifies an interface type for a Port Concentrator Shelf (PCS). This parameter appears if switch software detects a PCS. It applies to the user interface display only and not the PCS itself because system software does not detect the interface type within the PCS. To change the user-interface type, you must change a card in the PCS. |
slot.port line | Specifies the UFM-C slot, port, and line number, where port can be 1-250, and line can be 1-8. Note that the maximum number of T1/E1 lines per node is 32. This maximum could be, for example, spread over 4 UFM-8C card sets that utilize all 8 lines on each back card. |
speed | Specifies a port clock speed in Kbps for a 2.0 Mbps UFM, FRP, or FRM. The configured speed appears under the Configured Clock heading. The actual clock rate appears under the Measured Rx Clock heading. Note that this option does not apply to T1/E1 lines because these line types use 64 or 56 Kbps timeslots. The range of speeds according to the number of active ports is as follows:
Refer to the table at the beginning of this command description for the available clock rates for all port combinations. |
clocking | Specifies the port's clock type for HSSI, V.35, and X.21 lines. Clocking does not apply to T1, E1, or Port Concentrator lines. The clock is either normal or looped. Four combinations of clocking are available for the V.35 ports. Two combinations of clocking are available for HSSI and X.21. Note that the clock and data direction in DCE mode is the opposite of the direction for DTE mode. The possibilities are:
For a description of looped and normal clocking, refer to the Cisco IGX 8400 Series Reference manual, or the Cisco WAN Switching System Overview. |
port ID | Specifies the DLCI associated with the port (0-1024) {0}. A node uses this number when you add bundled connections. Otherwise, port ID can be used as a network destination number in global addressing. The port ID does not apply to T1, E1, or PCS ports. |
port queue depth | Specifies the maximum bytes in the transmission queue at the UFM, FRP, or FRM port. The range is 0-65535 bytes. The default is 65535 bytes. |
ecn queue threshold | Specifies the threshold at which the system begins to generate explicit congestion notification (BECN and FECN bits) for the port. The range is 0-65535 bytes. The default is 65535 bytes. |
de threshold | Specifies the port queue depth above which the system discards frames with a set Discard Eligibility (DE) bit. The range is 0-100%. The default is 100%. A threshold of 100% disables DE for the port because a queue cannot contain more than 100% of its capacity. |
signaling protocol | Specifies the LMI operation mode. The first time you execute cnffrport on a port, the command line interface displays the following options for this parameter: "none, Strata LMI, a (for Annex A), and d (for Annex D)." If you enter "a" or "d," the subsequent prompt asks if the interface is NNI. For the initial port specification and subsequent port specifications for a particular port, you can also use a single digit from the LMI definition list that follows. The total industry standard range is 0-255, but Cisco WAN Switching nodes recognize only the following (the default is internally recognized as LMI=2): LMI = 0 LMI is disabled at this port. LMI = 1 Cisco LMI and the asynchronous update process is enabled at this port. LMI = 2 LMI is disabled at this port. LMI = 3 Cisco LMI is enabled at this port, but asynchronous update process LMI = 4 The port configuration is UNI using CCITT Q.933 Annex A parameters. LMI = 5 The port configuration is UNI using ANSI T1.617 Annex D parameters. LMI = 6 The port configuration is NNI using CCITT Q.933 Annex A parameters. LMI = 7 The port configuration is NNI using ANSI T1.617 Annex D parameters. For any Frame Relay card set that has a maximum frame length of 4510 bytes, the use and type of a signaling protocol results in a limit on the possible number of connections per port (the port here is either physical or logical). The maximum number of connections per port for each protocol is as follows: For Annex A: 899 For Annex D: 899 For StrataLMI: 562 Neither addcon nor cnffrport prevents you from adding more than the maximum number of connections on a port. (You might, for example, use cnffrport to specify an LMI when too many connections for that particular LMI already exist.) If the number of connections is exceeded for a particular LMI, the LMI does not work on the port, the full status messages that result are discarded, and LMI timeouts occur on the port. A port failure results and also subsequently leads to a-bit failures in other segments of the connection path. |
asynchronous status | Specifies whether the node should send unsolicited LMI update messages when they appear or wait for the user-device to poll. Enter y (yes) or n (no). |
polling verify timer | Specifies a Link Integrity Verification Timer heartbeat (keep-alive) period. The range is 5-30. The default is 15. Set the timer to 5 secs. more than the setting in the user equipment. |
error threshold | Specifies the number of failures in the monitored events that cause the "keep alive" process to report an alarm. The theoretical range is 0-255. The valid range is 1-10. A threshold of 0 reverts to 1. A threshold greater than 10 reverts to 10. |
monitored events count | Specifies the number of monitored events for the "keep alive" process. It has a theoretical range of 0-255 and a valid range of 1-10. A port communication-fail condition is cleared after this number of successful polling cycles. A value of 0 reverts to 1, and a value more than 10 reverts to 10. |
communicate priority | Specifies whether the system should communicate the SNA priority of the connections to the user-device on the port. Enter y (yes) or n (no). (SNA priority is either H or L.) |
upper/lower RNR | Specifies the receiver not ready (RNR) thresholds. The upper threshold is the number of receiver not ready indications from the user equipment before an alarm is generated for this port. The lower RNR threshold is the number of indications from the user equipment before an alarm is cleared. The range is 1-255. The default for the upper RNR threshold is 75. The default for the lower RNR threshold is 25. |
Enable EFCI to BECN mapping | Directs the system to map the ForeSight congestion bit (which is set in the FastPackets by a trunk card) to the FECN and BECN bits on the affected PVC. |
ForeSight over port | Specifies whether the system should use CLLM over the port. |
min. flags/frame | Specifies the minimum number of flags between frames when the direction of transmission is from the node to the user-equipment. Any value greater than 0 is valid on the UFM, FRP or FRM. The default is 1. On a Port Concentrator Shelf, the range is 1-16. |
OAM FastPacket | Specifies how many OAM FastPackets must arrive from a remote NNI port before the local port generates "Abit = 0" in the signaling protocol message to the locally attached device. The range for this parameter is 0-15 packets. The default is 3 packets. A 0 disables this function. The OAM FastPacket threshold setting applies to UNI and NNI ports. The following two paragraphs provide a more detailed explanation of the Abit and OAM FastPacket threshold usage. On any Frame Relay port (UNI or NNI) that is using a signaling protocol (Cisco LMI, Annex A, or Annex D), the FRP or FRM provides a Status message to the attached equipment in response to a Status Enquiry message or as an Asynchronous Update. These Status messages contain details about every PVC configured on the port. In particular, the "PVC Active" bit (the Abit) represents whether a PVC is active (Abit=1) or out of service (Abit = 0). If the other end of the connection PVC on a UNI port, the only conditions that can cause the local Frame Relay card to send an Abit=0 are:
If the other end of the PVC terminates on an NNI port, one additional condition can cause the local UFM, FRP, or FRM to send an Abit=0 to the local device: if the remote NNI port on the card receives an Abit=0 from the remote network over the remote NNI, then the local card can propagate an Abit=0 out the local port. The mechanism by which the remote card notifies the local card of the Abit=0 coming from the remote network is OAM FastPackets. The local node sends one OAM FastPacket every 5 seconds for as long as the Abit coming from the remote network is 0. |
link integrity timer | Specifies the interval after which the system sends Status Enquiry messages across the NNI port. The range for the interval is 5-30 seconds. The default is 6 seconds. Both networks do not need to have the same T391 value. On a Frame Relay NNI port, the Link Integrity Timer (T391) specifies how often the UFM, FRP, or FRM generates a Status Enquiry message to the attached network using the selected NNI signaling protocol (Annex A or Annex D). The card should receive a Status message for every Status Enquiry message it transmits. If the Frame Relay card receives either no responses or invalid responses, a Port Communication Failure results (and causes a minor alarm). Using the default values for N392 Error Threshold and N393 Monitored Events Count in an example: an error occurs when no response (or a bad response) arrives for 3 out of the last 4 Status Enquiry messages. (The default for N392 Error Threshold is 3. For N393 Monitored Events Count, the default is 4.) |
N392 error threshold | Specifies the number of bad or undelivered responses to Status Enquiry messages that can occur before the system records a Port Communication Failure. The range is 1-10. The default is 3. See the description of the link integrity timer parameter for example usage. |
N393 monitored events count | Specifies the number of Status Enquiry messages in a period wherein the system waits for responses to the enquiries. The range is 1-10. The default is 4. See the description of the link integrity timer parameter for example usage. |
full status polling cycle (N391) | Specifies the interval at which the system sends the Full Status Report request for all PVCs across the NNI port. The range is 1-255 polling cycles. The default is 10 cycles. The Full Status reports the status of all the connections across the NNI. |
card type | Specifies the card type when you enter the cnffrport command in a job. This parameter is not available except when you specify cnffrport in a job by using the addjob command. During the job specification, you enter the card type just after the slot.port during the command specification phase of addjob. Valid card types are "V.35," "X.21," "port," and "line," where "line" indicates a T1 or E1 line. |
CLLM status Tx Timer | Specifies an interval for the system to send ForeSight congestion messages across the NNI. The range is 40 ms-350 ms. The default is 100 ms. Both networks must be Cisco WAN Switching networks. |
IDE to DE mapping | Specifies whether the destination system should map the internal DE bit (IDE) status in the FastPacket or ATM cell to the Frame Relay DE bit at the destination. Enter y (yes) or n (no). If you specify the non-standard case of CIR=0 with either addcon or cnffrcls, you must first enable IDE to DE mapping. Refer to the section titled "Using Frame Relay Classes " for important information on setting CIR=0. |
interface control | Specifies the control leads available on the V.35 and X.21 physical Frame Relay ports and the meaning for each lead. |
channel range | Specifies the DS0s for the T1 or E1 logical port. The value can be 1 or a contiguous combination in the range 1-24 for T1 or 1-31 for E1. For example, 7-12 indicates 6 DS0s for the port, starting with DS0 7. Before you use this command, specify the valid channel range with the addfrport command. |
channel speed | Specifies the bandwidth available to a logical port. The speed is 64 Kbps times the number of DS0s you specify with the channel range parameter. |
Configures the interface control template signals. Each interface control lead must be individually configured. (Each data channel has a default interface control template for its active, conditioned, and looped-near and far states.) The signals available to cnfict depend on the type of back card and whether the port mode is DCE or DTE. On an IPX node, the applicable front cards are the SDP, LDP, FRP, CDP (for data), and FTC (for data). On an IGX node, the applicable front cards are the LDM, HDM, FRM, UFM, CVM (for data), and FTM (for data).
When Y-cable redundancy is in effect, the control template configuration for the data channels terminating at the primary slot also applies to the data channels of the secondary slot. Any configuration information you attempt to apply to the secondary slot is ignored. The following lists which leads are configurable for each type of data interface supported by the IGX node. The entries under the "IGX Name" column indicate the abbreviations to use when you specify input or output leads on the command line.
| Source | IGX Name | EIA/TIA- 232C | EIA/TIA- 232D | EIA/TI- 449 | V.35 | X.21 | Fast EIA | CCITT (ITU-T) Equivalent | Function |
|---|---|---|---|---|---|---|---|---|---|
DTE | RTS | CA | CA | RS | C |
| F4 | 105 | Request to Send |
DCE | CTS | CB | CB | CS | D |
| F4 | 106 | Clear to Send |
DCE | DSR | CC | CC | DM | E |
| F3 | 107 | Data Set Ready |
DCE | DCD | CF | CF | RR | F |
| F7 | 109 | Data Carrier Detect (RLSD) |
DCE | QM | QM | QM |
|
|
|
|
| Equalizer Mode |
DTE | pin 11 | 11 | 11 |
|
|
|
|
| Sometimes used for Data |
DCE | SDCD | SCF | SCF |
|
|
|
| 122 | Secondary Data Carrier Detect |
DCE | SCTS | SCB | SCB |
|
|
|
| 121 | Secondary Clear to Send |
DTE | STxD | SBA | SBA |
|
|
| F5 | 118 | Secondary Transmit Data |
DTE | NS |
|
| NS |
|
| F7 |
| New Sync |
DCE | SRxD | SBB | SBB |
|
|
| F5 | 119 | Secondary Receive Data |
DCE | DCR | DCR |
|
|
|
|
|
| Divided Receiver Clock |
DTE | RL |
| RL | RL |
|
| F6 |
| Remote Loopback |
DTE | SRTS | SCA | SCA |
|
|
|
| 120 | Secondary Request to Send |
DTE | DTR | CD | CD | TR | H |
| F3 | 108.2 | Data Terminal Ready |
DCE | SQ | CG | CG | SQ |
|
|
| 110 | Signal Quality Detect |
DCE | RI | CE | CE | IC | J** |
|
| 125 | Ring Indicator |
DTE | SF | CH | CH | SF |
|
|
| 111 | Signal Rate Select (to DCE) |
DCE | SI | CI | CI | SI |
|
|
| 112 | Signal Rate Select (to DTE) |
DTE | BSY | BSY |
| IS |
|
| F1 |
| Busy (In Service) |
DCE | SB |
| TST | SB |
|
| F1 |
| Test Indicator |
DTE | LL |
|
| LL |
|
| F2 |
| Local Loopback |
DCE | TM |
|
| TM | K** |
| F6 |
| Test Mode |
DTE | SS |
|
| SS |
|
|
|
| Select Standby |
DTE | C |
|
|
|
| C |
|
| Control |
DCE | I |
|
|
|
| I |
|
| Indicator |
Asterisks (**) indicate the listing is applicable to only an SDP or HDM card. Pins 11 and 23 on an RS-232 port are bi-directional, and their default direction is input. See the cnfcldir command for information on changing the direction of these pins. The cpyict command can be used to copy an interface control template from one data channel to another. The template can then be edited using the cnfict command. The dspbob command displays the state of leads at specified intervals.
The preceding list shows the equivalence between RS-232C, RS-232D, RS-449, V.35, and X.21 interfaces. An IGX treats leads impartially for non-interleaved connections. Any signal arriving on an EIA pin at one end may be transmitted to any pin at the other end. An imposed maximum of 12 EIA leads applies to any interface type. For interleaved EIA connections, the "Fast EIA" column shows which leads are carried in the interleaved bytes in the data packets. All remaining leads are carried in traditional control lead packets.
Full Name
Configure interface control template
cnfict <port> <template> <output> <source>
addextlp, dspict, tstport
| Privilege | Jobs | Log | Node | Lock |
1-2 | Yes | Yes | IGX | Yes |
cnfict 25.1 a cts on
Configure the active interface control template for channel 25.1 to CTS-on. CTS-on means that when the port is active, the CTS lead is asserted.
beta TRM YourID:1 IGX 8430 9.2 Aug. 15 1998 17:36 MST
Data Channel: 25.1
Interface: RS232 DCE
Clocking: Normal
Interface Control Template for Connection while ACTIVE
Lead Output Value Lead Output Value
RI OFF DSR ON
CTS ON SRxD ON
DCR OFF DCD ON
SCTS ON SDCD ON
SQ ON
Last Command: cnfict 25.1 a cts on
Next Command:
cnfict 9.1 a rts on
Configure the active interface control template to have RTS-on. This means that when the port is active. the RTS lead is asserted.
alpha TRM YourID:1 IGX 8430 9.2 Aug. 23 1998 10:23 PST
Port: 9.1 [ACTIVE ]
Interface: FRI-V35 DTE Configured Clock: 256 Kbps
Clocking: Normal Measured Rx Clock: 0 Kbps
Port ID 7
Port Queue Depth 65535 OAM Pkt Threshold 3 pkts
ECN Queue Threshold 65535 T391 Link Intg Timer 6 sec
DE Threshold 100 % N391 Full Status Poll 10 cyl
Signalling Protocol None ForeSight (CLLM) No
Asynchronous Status No CLLM Status Tx Timer 0 msec
T392 Polling Verif Timer 15 Interface Control Template
N392 Error Threshold 3 Lead State
N393 Monitored Events Count 4 RTS ON
Communicate Priority No DTR ON
Upper/Lower RNR Thresh 75%/ 25%
Min Flags / Frames 1
Last Command: cnfict 9.1 a rts on
Next Command:
cnfict 31.1 n dsr on
Configure the near interface control template for 31.1, to DSR on (DDS trunk).
beta TRM YourID:1 IGX 8430 9.2 Aug. 15 1998 17:38 MST
Data Channel: 31.1
Interface: DDS-4 OCU Config
Clocking: Looped
Interface Control Template for Connection while NEAR EXT LOOPED
Lead Output Value Lead Output Value
DSR ON CTS ON
DCD ON
Last Command: cnfict 31.1 near dsr on
Next Command:
| Parameter | Description | |||
|---|---|---|---|---|
port | Specifies the data channel or Frame Relay port whose interface control template you want to configure. Specify the port in the format slot.port | |||
template | Specifies which interface control template to configure for the channel and has the format: a/c/l/n/f. Valid entries are: | |||
| Entry | Template | Description |
|
| a | Active | The active" control template is in effect while the data channel is active (normal operation). | |
| c | Conditioned | The conditioned control template is in effect when conditioning is applied to the data channel. The conditioned template is used when the network detects that it cannot maintain the connection because of card failures or lack of bandwidth (The connection is failed.) | |
| l | Looped | The looped template is in effect when the data channel is being looped back in either direction. The looped template is used when the addloclp command or the addrmtlp command has been used to loop the connection within the network. | |
| n | Near loopback | The near template is in effect when running a tstport n command or an addextlp n command on a port. The port is configured such that the external near modem is placed in a loopback. | |
| f | Far loopback | The far template is in effect when running a tstport f command or an addextlp f command on a port. The port is configured such that the external far-end modem is placed in a loopback. | |
| The only valid template for a Frame Relay port, X.21 or V.35, is the ACTIVE template. Also, all the output leads have steady state values and do not follow local or remote inputs. | |||
output | Specifies the output lead to configure. Valid abbreviations for output leads are listed in the previous parameter (template). Configurable output leads vary depending on the type of data interface: RS-232, V.35, X.21, or RS-449. | |||
source | Specifies how the lead is to be configured and has the format:
Delay is an optional parameter. The following lists the valid source choices: | |||
| on | The output lead is asserted. | ||
| off | The output lead is inhibited. | ||
| l | (for local) indicates that the output follows a local lead. | ||
| r | (for remote) indicates that the output follows a remote lead. | ||
| input | The name of the local or remote input lead that the output lead follows. | ||
| delay | The time in milliseconds that separates the "off" to "on" lead transitions. Delay is valid only when the output lead is CTS and the input lead is local RTS. "On" to "Off" lead transitions are not subject to this delay. | ||
Selects a mode of the card for a UFM-U back card. The mode of a card is combination of maximum port speeds and for specific port numbers. Table 8-18 lists the maximum port speeds and active ports for each mode. The cnfmode command lets you select 1 of 27 modes for either a UFI-12V.35 back card or a UFI-12X.21 back card. For a UFI-4HSSI back card, 3 modes are available. Note that you specify the actual speed of an individual port by using cnffrport. The IGX documentation describes the application of the modes and the sequence of execution of these commands.
Note that cnfmode and cnfufmumode are the same command.
| V.35 and X.21 Ports | HSSI Ports | ||||
|---|---|---|---|---|---|
| Group A | Group B | Group C | A | B | |
| Mode | 1 2 3 4 | 5 6 7 8 | 9 10 11 12 | 1 2 | 3 4 |
1 | 3 3 3 3 | 3 3 3 3 | 3 3 3 3 | 8 8 | 8 8 |
2 | 8 - 8 - | 8 - 8 - | 8 - 8 - | 16 - | 16 - |
3 | 10 - - - | 10 - - - | 10 - - - | 16 - | - - |
4 | 8 - 8 - | 3 3 3 3 | 3 3 3 3 |
|
|
5 | 10 - - - | 3 3 3 3 | 3 3 3 3 |
|
|
6 | 8 - 8 - | 8 - 8 - | 3 3 3 3 |
|
|
7 | 10 - - - | 8 - 8 - | 3 3 3 3 |
|
|
8 | 10 - - - | 10 - - - | 3 3 3 3 |
|
|
9 | 10 - - - | 8 - 8 - | 8 - 8 - |
|
|
10 | 10 - - - | 10 - - - | 8 - 8 - |
|
|
11 | 3 3 3 3 | 8 - 8 - | 3 3 3 3 |
|
|
12 | 3 3 3 3 | 3 3 3 3 | 8 - 8 - |
|
|
13 | 3 3 3 3 | 10 - - - | 3 3 3 3 |
|
|
14 | 3 3 3 3 | 3 3 3 3 | 10 - - - |
|
|
15 | 8 - 8 - | 3 3 3 3 | 8 - 8 - |
|
|
16 | 3 3 3 3 | 8 - 8 - | 8 - 8 - |
|
|
17 | 8 - 8 - | 10 - - - | 3 3 3 3 |
|
|
18 | 8 - 8 - | 3 3 3 3 | 10 - - - |
|
|
19 | 3 3 3 3 | 8 - 8 - | 10 - - - |
|
|
20 | 3 3 3 3 | 10 - - - | 8 - 8 - |
|
|
21 | 10 - - - | 3 3 3 3 | 8 - 8 - |
|
|
22 | 10 - - - | 3 3 3 3 | 10 - - - |
|
|
23 | 3 3 3 3 | 10 - - - | 10 - - - |
|
|
24 | 8 - 8 - | 10 - - - | 8 - 8 - |
|
|
25 | 8 - 8 - | 8 - 8 - | 10 - - - |
|
|
26 | 10 - - - | 8 - 8 - | 10 - - - |
|
|
27 | 8 - 8 - | 10 - - - | 10 - - - |
|
|
Configure mode
cnfmode <port> <mode>
cnffrport, dspmode, dspmodes
| Privilege | Jobs | Log | Node | Lock |
1-2 | Node | Yes | IGX | Yes |
cnfmode 13 4
Configure the UFM-U card set in slot 13 to have mode 4. Note that the display shows which ports are active for each mode number but does not show the current mode of the UFM-U. To see the current mode of the UFM-U, use dspmode.
w180 TN SuperUser IGX 16 9.2 July 30 1997 01:25 GMT
UFMU MODES AND PORT AVAILABILITY BITMAP
Mode[ 1]:111111111111 Mode[ 2]:101010101010 Mode[ 3]:100010001000
Mode[ 4]:101011111111 Mode[ 5]:100011111111 Mode[ 6]:101010101111
Mode[ 7]:100010101111 Mode[ 8]:100010001111 Mode[ 9]:100010101010
Mode[10]:100010001010 Mode[11]:111110101111 Mode[12]:111111111010
Mode[13]:111110001111 Mode[14]:111111111000 Mode[15]:101011111010
Mode[16]:111110101010 Mode[17]:101010001111 Mode[18]:101011111000
Mode[19]:111110101000 Mode[20]:111110001010 Mode[21]:100011111010
Mode[22]:100011111000 Mode[23]:111110001000 Mode[24]:101010001010
Mode[25]:101010101000 Mode[26]:100010101000 Mode[27]:101010001000
This Command: cnfmode 13
Enter The New UFMU Mode [1]: 4
| Parameter | Description | |||
|---|---|---|---|---|
slot | Specifies the slot of the UFM-U card. | |||
mode | Specifies the mode of the UFM-U card set. The range for V.35 and X.21 ports is 1-27. The range for HSSI ports is 1-3. You may have to delete connections and down one or more ports before you execute cnfmode. To determine if you must delete connection or for a detailed description of the modes of a UFM-U, see the Cisco IGX 8400 Series Reference. | |||
Copies all control template information associated with a given channel: the active template information, the conditioned template information, and the looped template information near, far. Once copied, you can edit the control template information with the cnfict command. See the cnfict command for more information on interface control templates.
Copy SDP/LDP/FRP interface control template
cpyict <source_port> <destination_port>
cnfict, dspict
| Privilege | Jobs | Log | Node | Lock |
1-2 | Yes | Yes | IGX | Yes |
cpyict 25.1 25.2
Copy the interface control template on channel 25.1 to channel 25.2.
beta TRM YourID:1 IGX 8430 9.2 Aug. 15 1998 17:40 MST
Data Channel: 25.2
Interface: RS232 DCE
Clocking: Normal
Interface Control Template for Connection while ACTIVE
Lead Output Value Lead Output Value
RI OFF DSR ON
CTS ON SRxD ON
DCR OFF DCD ON
SCTS ON SDCD ON
SQ ON
Last Command: cpyict 25.1 25.2
Next Command:
cpyict 25.1 25.2
Copy the Frame Relay interface control template on port 25.1 to 25.2.
beta TRM YourID:1 IGX 8430 9.2 Aug. 15 1998 17:40 MST
Data Channel: 25.2
Interface: RS232 DCE
Clocking: Normal
Interface Control Template for Connection while ACTIVE
Lead Output Value Lead Output Value
RI OFF DSR ON
CTS ON SRxD ON
DCR OFF DCD ON
SCTS ON SDCD ON
SQ ON
Last Command: cpyict 25.1 25.2
Next Command:
| Parameter | Description |
|---|---|
source channel | Specifies the data channel or Frame Relay port. |
destination channel | Specifies the data channel or Frame Relay port you want to receive the copied control template information. |
Removes connections from the network. A prompt appears for confirming the deletion. Connections can be deleted from the node at either end of the connection. Do not delete a connection when the node at the other end of the connection is unreachable. The unreachable node will not recognize the deletion. It is especially important not to delete a connection to an unreachable node and then connect that channel to another node. Channel connections are added to the network with the addcon command.
Delete connections
delcon <channel(s)>
addcon, dspcon, dspcons
| Privilege | Jobs | Log | Node | Lock |
1-2 | Yes | Yes | IGX | Yes |
delcon 25.1
Delete connection 25.1. The connections to delete are highlighted. A prompt asks you to confirm the deletion. Respond with "y" for yes. Connection 25.1 is deleted.
beta TRM YourID:1 IGX 8430 9.2 Aug. 15 1998 15:43 MST
Local Remote Remote Route
Channel NodeName Channel State Type Compression Code Avoid COS O
19.1.101 gamma 8.2.300 Ok fr 0 L
19.2.302 alpha 9.2.400 Ok fr 0 R
25.2 gamma 6.1 Ok 256 7/8 0 L
Last Command:
Next Command: delcon 25.1
| Parameter | Description |
|---|---|
channel | Specifies the channel or set of channels in the following format: slot.port.DLCI. On an FRP or FRM, the range for port is 1-24 or 1-31. On a UFM-C, the range for port is 1-250. (For connections on a UFM-C, line is not necessary because of the port-to-line mapping through addfrport). For a UFM-U, the range for port is 1-12 for V.35 or X.21 and 1-4 for HSSI (unless Y-cable redundancy exists on the HSSI, in which case port can be only "1"). The range for DLCI is typically 16-1007. |
The information in this description applies to only Frame Relay ports using a T1 or E1 line. The delfrport command deletes logical ports on FRP, FRM, or UFM-C cards and "unassigns" associated DS0/timeslots. The deleted DS0/timeslots are available for you to assign to new logical ports (with the addfrport command). The port display (normally visible through dspfrport command) appears regardless of whether the port has been successfully deleted. The screen displays the defined port numbers for the specified line. The following lists the error and warning messages for this command.
| Messages | Reason for Message |
|---|---|
"Slot is out of range" | Line number is not correct for FRP T1/E1. |
"Port does not exist" | Logical port number does not exist. |
"You must first down the port" | Logical port is up. |
"You must first down the port" | Specified port is not first DS0/timeslot of logical port. |
Delete Frame Relay port
For FRM or FRP: delfrport <slot.port>
For UFM: delfrport <slot.port> <line.ds0_range>
addfrport, dspfrport, dnfrport
| Privilege | Jobs | Log | Node | Lock |
1 | Yes | Yes | IGX | Yes |
delfrport 8.1
Delete Frame Relay port 8.1.
alpha TRM YourID:1 IGX 8420 9.2 Aug. 15 1998 17:28 CST
Port configuration for FRP 8
From Chan Speed Interface State
1 9-15 448 FRI T1 ACTIVE
20 20-24 320 FRI T1 ACTIVE
Last Command: delfrport 8.1
Next Command:
| Parameter | Description |
|---|---|
slot | Specifies the physical FRP or FRM T1 or E1 line. The range of logical port numbers is 1-24 for T1 lines and 1-31 for E1 lines. |
port | Specifies the logical port number of the port to delete. |
Deactivates ("downs") the specified Frame Relay port. Before deactivating a port, you must delete all connections on the port (see delcon description).
Down Frame Relay port
For UFM-U, FRM, or FRP: dnfrport <slot.port>
For UFM-C: dnfrport <slot.port> <line.ds0_range>
cnffrport, dspfrport, upfrport
| Privilege | Jobs | Log | Node | Lock |
1-2 | Yes | Yes | IGX | Yes |
delfrport 3.1
Down Frame Relay port 3.1.
pubsigx1 TN SuperUser IGX 32 9.2 Aug. 14 1997 03:49 GMT
Port: 3.1 [INACTIVE]
Interface: FRI-T1 Configured Clock: 64 Kbps
Clocking: None Measured Rx Clock: None
Min Flags / Frames 1
Port ID - Channel Range 1
Port Queue Depth 65535 OAM Pkt Threshold 3 pkts
ECN Queue Threshold 65535 T391 Link Intg Timer 10 sec
DE Threshold 100 % N391 Full Status Poll 6 cyl
Signalling Protocol None EFCI Mapping Enabled No
Asynchronous Status No CLLM Enabled/Tx Timer No/ 0 msec
T392 Polling Verif Timer 15 IDE to DE Mapping Yes
N392 Error Threshold 3 Channel Speed 64
N393 Monitored Events Count 4
Communicate Priority No
Upper/Lower RNR Thresh 75%/ 25%
Last Command: dnfrport 3.1
Next Command:
| Parameter | Description |
|---|---|
slot | Specifies the slot number of the Frame Relay card with the port to down. |
port | Specifies the port number to deactivate on the card specified by slot. On an FRP or FRM, the range is 1-24 or 1-31. On a UFM-C, the range is 1-250. On a UFM-U with a V.35 or X.21 interface, the range is 1-12. On a UFM-U with a HSSI interface, the range is 1-4. |
line | The physical line on UFM-C card sets (not used for UFM-U cards). |
Displays configuration details for voice, data, or Frame Relay channels.
Voice channels display: | Utilization, Adaptive Voice, Gain, Dial Type, Interface Type, and OnHook and Conditioning specifications. |
Data channels display: | Maximum EIA Update Rate, Percentage Utilization, DFM Pattern Length, and DFM Status. |
Frame relay channels display: | Minimum Information Rate, VC Queue Buffer Size or Bc, Peak Information Rate or Be, Maximum Credits, ECN Queue Buffer Size, Quiescent Information Rate, ForeSight enabled or not, and Percentage Utilization. |
If the channel specified is a voice channel, the display includes configuration details for all channels on the specified circuit line starting with the specified channel. If the channel specified is a data channel, the display includes configuration details for all channels on the specified data card (CDP, SDP or LDP) starting with the specified channel. If the channel specified is a Frame Relay channel, the display includes configuration details for all channels on the specified FRP port starting with the specified channel. If you specify a Frame Relay port only with no DLCI, the display includes configuration details for all channels on the Frame Relay port specified. The display also indicates either Cisco parameters or standard Frame Relay parameters where appropriate.
Display channel configuration
dspchcnf <start_channel>
cnfchadv, cnfchdfm, cnfchdl, cnfcheia, cnfchgn, cnfchpri, cnfchutl, cnffrcon
| Privilege | Jobs | Log | Node | Lock |
1-6 | No | No | IGX | No |
dspchcnf 9.1
Display configuration values for all channels on Frame Relay port 9.1.
alpha TRM YourID:1 IGX 8430 9.2 Aug. 15 1998 15:56 PST
Frame Relay Channel Configuration Port: 9.1
Channel MIR CIR VC Q Depth PIR Cmax ECN QThresh QIR FST % Util
9.1.100 9.6 9.6 5 256 10 65535 9.6 n 100
Last Command: dspchcnf 9.1
Next Command:
| Parameter | Description |
|---|---|
channel | Specifies the channel at which the display begins. The format is slot.port.DLCI. The DLCI parameter is optional. |
Displays traffic statistics and the statistics collection period for the specified channel. The display shows when the statistics were last cleared and the time that has elapsed during the current collection period. The statistical parameters include:
For each parameter, the values appear in the following categories:
The dspchstats command also displays ECN (Explicit Congestion Notification) statistics.
♦ FECN: Lists number of frames sent to the receiving end router with the FECN (Forward Explicit Congestion Notification) bit set and the ratio of these frames to the total number of frames sent. This is a measure of Frame Relay congestion and the extent to which the receiving router has been informed of frames received that encountered congestion. ♦ BECN: Lists number of frames sent to the transmitting end router with the BECN (Backward Explicit Congestion Notification) bit set and the ratio of these frames to the total number of frames sent. This is a measure of Frame Relay congestion and the extent to which the transmitting router has been informed of frames received that encountered congestion. ♦ Min-Pk. bytes rcvd: Lists number of bytes received at the receiving end router during the greatest minute-peak of bytes received. ♦ minutes congested: Lists number of congested minutes of received data since the command started.
The following 35 statistics are available for each Frame Relay PVC (channel. Note that the statistic field name listed may be slightly different from the field name on the dspchstats screen.
1) Frames Received
2) Receive Frames Discarded
3) Frames Transmitted
4) Transmit Frames Discarded
5) Packets Received
6) Receive Packets Discarded
7) Packets Transmitted
10) Bytes Received
11) Receive Bytes Discarded
12) Bytes Transmitted
13) Transmit Bytes Discarded
17) Seconds In Service
18) Frames Transmitted with FECN
19) Frames Transmitted with BECN
21) Minutes Congested
22) DE Frames Received
23) DE Frames Transmitted
24) DE Frames Dropped
25) DE Bytes Received
26) Frames Received in Excess of CIR
27) Bytes Received in Excess of CIR
28) Frames Transmitted in Excess of CIR
29) Bytes Transmitted in Excess of CIR
32) Rx Frames Discarded - Deroute/Down
33) Rx Bytes Discarded - Deroute/Down
34) Rx Frames Discarded - VC Q Overflow
35) Rx Bytes Discarded - VC Q Overflow
36) Tx Frames Discarded - Q Overflow
37) Tx Bytes Discarded - Q Overflow
38) Tx Frames Discarded - Ingress CRC
39) Tx Bytes Discarded - Ingress CRC
40) Tx Frames Discarded - Trunk Discard
41) Tx Bytes Discarded - Trunk Discard
42) Tx Frames During Ingress LMI Fail
43) Tx Bytes During Ingress LMI Fail
| Statistic | Description |
|---|---|
Frames Received (Ingress) | This statistic provides a count of the number of frames received from the attached equipment. This statistic is incremented even when the received frame is invalid or discarded for any reason. (See possible reasons below.) |
Receive Frames Discarded (Ingress) | This statistic provides a count of the number of frames received from the attached equipment which were discarded before being sent into the network or aborted after some portion had been already sent into the network. Possible reasons for discard are: —Invalid CRC - that is, the CRC calculated by the IGX does not match the CRC provided by the attached equipment in the last 2 octets of the frame. (Frames received with an invalid CRC are also included in the port Receive Frame CRC Errors statistic.) —Invalid Frame Length - that is, the length of the received frame, including the header and frame check sequence (FCS, or CRC) octets, is either too short (less than 5 octets) or too long (more than 4510 octets). (Frames received with an invalid frame length are also included in the port Illegal Length Receive Frames statistic.) —Invalid Alignment - that is, the length of the received frame is not an integral number of octets. (Frames received with an invalid alignment are also included in the port Receive Frame Alignment Errors statistic.) Frame received with DE = 1 and the PVC's ingress queue is filled at least to the DE threshold and the global DE feature is enabled (using the cnfsysparm command). Frames discarded for this reason are specifically counted in the PVC DE Frames Dropped statistic (below). —PVC "failed" (due to endpoint hardware failure/absence or inability to find a route through the network) or "downed" (intentionally out of service due to operator action). Frames discarded for this reason are specifically counted in the PVC Rx Frames Discarded - Deroute/Down statistic (below). —PVC ingress queue full. The queue may fill (and overflow) due to sustained transmission above the PVC's MIR or as a result of MUXBUS oversubscription. Frames discarded for this reason are specifically counted in the PVC Rx Frames Discarded - VC Q Overflow statistic (below). This statistic is a subset of the PVC Frames Received statistic.) |
Frames Transmitted (Egress) | This statistic provides a count of the number of frames transmitted to the attached equipment. |
Transmit Frames Discarded | This statistic provides a count of the number of frames which were not able to be transmitted to the attached equipment. Possible reasons for discard are: Port transmit queue overflow - that is, the frame traversed the network successfully but encountered a full egress port queue. Frames discarded for this reason are specifically counted in the PVC Tx Frames Discarded - Q Overflow statistic (below) and the port Tx Frames Discarded - Queue Overflow statistic (above). Incomplete frame at egress (that is, no end-of-frame (EOF) packet received) for any reason The most common cause is a CRC error detected at ingress - that is, the beginning of the frame traversed the network successfully but the end of the frame was never sent because a CRC error was detected at the end of the frame at ingress. Frames discarded due to a missing EOF packet (because of ingress CRC error or EOF packets dropped in a trunk) are specifically counted in the PVC Tx Frames Discarded - Ingress CRC statistic (below). Ingress CRC errors are also counted in the ingress port Receive Frame CRC Errors statistic (above). Incorrect frame length, that is, the expected frame length (recorded in the end-of-frame packet) is different than the total payload of all the packets which arrive. Such a frame length error could be caused by: —one or more packets being missing due to discard(s) on a trunk, or —a transmission bit error on the frame length field in the end-of-frame packet. Frames discarded for this reason are counted in the PVC Tx Frames Discarded - Trunk Discard statistic (below). Invalid frame length, that is, the frame is longer than 4510 octets long. This could occur if the end-of-frame packet from one frame and the start-of-frame packet of the next frame are both missing due to discards on a trunk, resulting in a concatenated frame. Frames discarded for this reason are counted in the PVC Tx Frames Discarded - Trunk Discard statistic (below). Frame CRC error - that is, the calculated CRC at the destination does not match the original frame's CRC (contained within the received packets). This situation can occur as a result of transmission bit errors on payload bits on one or more packets of the frame. Frames discarded for this reason are specifically counted in the PVC Tx Frames Discarded - Trunk Discard statistic (below). |
Packets Received | This statistic provides a count of the number of packets received across the network. These are the packets that are used to re-create all the frames which are counted in the PVC Frames Transmitted and Transmit Frames Discarded statistics (above). |
Receive Packets Discarded | This statistic provides a count of the number of packets received across the network but whose payload was ultimately discarded because they contained portions of the frames which are discarded and counted in the Transmit Frames Discarded statistic (above). |
Packets Transmitted | This statistic provides a count of the number of packets submitted to the network. These packets are all the packets that were generated from the ònon-erroredó received frames (Frames Received minus Receive Frames Discarded) as well as some of the packets from the errored received frames (Receive Frames Discarded). Some packets from errored receive frames may be submitted to the network because the IGX does not wait to receive the entire frame before starting to packetize the frame and send it through the network. Consequently, if an error is detected at the end of the frame (for example, CRC error, alignment error, length error), the frame is aborted only after some packets may have been sent. |
Bytes Received | This statistic provides a count of the number of octets in the frames counted in the Frames Received statistic (above). The octets counted include the Frame Relay header octets as well as the frame check sequence (FCS, or CRC) octets. |
Receive Bytes Discarded | This statistic provides a count of the number of octets in the frames counted in the Receive Frames Discarded statistic (above). The octets counted include the Frame Relay header octets as well as the frame check sequence (FCS, or CRC) octets. |
Bytes Transmitted | This statistic provides a count of the number of octets in the frames counted in the Frames Transmitted statistic (above). The octets counted include the Frame Relay header octets as well as the frame check sequence (FCS, or CRC) octets. |
Transmit Bytes Discarded | This statistic provides a count of the number of octets in the frames counted in the Transmit Frames Discarded statistic (above). The octets counted include the Frame Relay header octets as well as the frame check sequence (FCS, or CRC) octets. |
Seconds in Service | This statistic provides a count of the number of seconds during which the PVC was òin serviceó. The PVC is considered in service any time the PVC is not òfailedó (due to endpoint hardware failure/absence or inability to find a route through the network) or òdownedó (intentionally out of service due to operator action). |
Frames Transmitted with FECN | This statistic provides a count of the number of frames transmitted to the attached equipment with the Forward Explicit Congestion Notification (FECN) bit set, regardless of where in the network the congestion was experienced. This statistic is a subset of the PVC Frames Transmitted statistic. This statistic is also a subset of the port Frames Transmitted with FECN statistic. |
Frames Transmitted with BECN | This statistic provides a count of the number of frames transmitted to the attached equipment with the Backward Explicit Congestion Notification (BECN) bit set, regardless of where in the network the congestion was experienced. This statistic is a subset of the PVC Frames Transmitted statistic. This statistic is also a subset of the port Frames Transmitted with BECN statistic. |
Minutes Congested | This statistic provides a count of the number of minutes during which 50% or more of the frames transmitted to the attached equipment have the Forward Explicit Congestion Notification (FECN) bit set. |
| The threshold (default: 50%) which defines congestion is configurable (by a SuperUser) using the cnffstparm command. |
DE Frames Received | This statistic provides a count of the number of frames received from the attached equipment with the Discard Eligible (DE) bit already set. This statistic is a subset of the PVC Frames Received statistic |
DE Frames Transmitted | This statistic provides a count of the number of frames transmitted to the attached equipment with the Discard Eligible (DE) bit set, regardless of why or where the DE bit was set. If IDE-to-DE mapping is enabled on the port, this statistic includes those frames which have their DE bit set by the IDE-to-DE mapping function This statistic is a subset of the PVC Frames Transmitted statistic. |
DE Frames Dropped | This statistic provides a count of the number of frames received from the attached device which were discarded because the frame's DE bit is set and the PVC's ingress buffer has reached the DE threshold. The DE threshold is configured as part of the port configuration (cnfport command). This statistic is a subset of the PVC Frames Received statistic. This statistic is a subset of the PVC Receive Frames Discarded statistic. This statistic is a subset of the PVC DE Frames Received statistic. |
DE Bytes Received | This statistic provides a count of the number of octets in the frames counted in the DE Frames Received statistic (above). The octets counted include the Frame Relay header octets as well as the frame check sequence (FCS, or CRC) octets. This statistic is a subset of the PVC Bytes Received statistic. |
Frames Received in Excess of CIR | This statistic provides a count of the number of frames received from the attached equipment which exceed the configured Committed Information Rate (CIR) for the PVC. Whether a frame is considered òin excess of CIRó depends on whether the DE feature is enabled (using the cnfsysparm command). —If the DE feature is enabled, only frames with DE=0 are counted against Bc. Thus, this statistic only counts those frames which exceeded Bc and had DE=0. (If a frame is received with DE=1, only the DE Frames Received statistic is incremented and the frame is not counted against Bc.) If the DE feature is not enabled, all frames are counted against Bc. If the frame exceeds Bc, it is included in this statistic. This statistic is a subset of the PVC Frames Received statistic |
Bytes Received in Excess of CIR | This statistic provides a count of the number of octets in the frames counted in the Frames Received in Excess of CIR statistic (above). The octets counted include the Frame Relay header octets as well as the frame check sequence (FCS, or CRC) octets. This statistic is a subset of the PVC Bytes Received statistic. |
Frames Transmitted in Excess of CIR | This statistic provides a count of the number of frames transmitted to the attached equipment which: —were determined at ingress to exceed the configured Committed Information Rate (CIR) for the PVC, or —were received at ingress with DE=1 and the DE feature is enabled, or —were received at ingress when the VC_Q exceeded the configured DE threshold and the DE feature is enabled. All of these conditions have in common that the packets carrying these frames all have CLP=1. It is actually the status of the CLP bits in the arriving packets that is monitored at egress. This statistic is a subset of the PVC Frames Transmitted statistic. |
Bytes Transmitted in Excess of CIR | This statistic provides a count of the number of octets in the frames counted in the Frames Transmitted in Excess of CIR statistic (above). The octets counted include the Frame Relay header octets as well as the frame check sequence (FCS, or CRC) octets. This statistic is a subset of the PVC Bytes Transmitted statistic. |
Rx Frames Discarded - Deroute/Down | This statistic provides a count of the number of frames received from the attached equipment which are discarded because the PVC is routed (due to endpoint hardware failure/absence or inability to find a route through the network) or downed (intentionally out of service due to operator action). This statistic is a subset of the PVC Frames Received statistic. |
Rx Bytes Discarded—Deroute/Down | This statistic provides a count of the number of octets in the frames counted in the Rx Frames Discarded - Deroute/Down statistic (above). The octets counted include the Frame Relay header octets as well as the frame check sequence (FCS, or CRC) octets. This statistic is a subset of the PVC Bytes Received statistic. This statistic is also a subset of the PVC Receive Bytes Discarded statistic. |
Rx Frames Discarded - VC Q Overflow | This statistic provides a count of the number of frames received from the attached equipment which are discarded because the PVC ingress buffer (VC Q) is full. This statistic is a subset of the PVC Frames Received statistic. |
Rx Bytes Discarded—VC Q Overflow | This statistic provides a count of the number of octets in the frames counted in the Rx Frames Discarded - VC Q Overflow statistic (above). The octets counted include the Frame Relay header octets as well as the frame check sequence (FCS, or CRC) octets. This statistic is a subset of the PVC Bytes Received statistic. This statistic is also a subset of the PVC Receive Bytes Discarded statistic. |
Tx Frames Discarded—Q Overflow | This statistic provides a count of the number of frames which were not able to be transmitted to the attached equipment because the port's egress buffer is full. The port's egress buffer may fill (and overflow) due to oversubscription. This statistic is a subset of the PVC Transmit Frames Discarded statistic. This statistic is a subset of the port Tx Frames Discarded - Q Overflow statistic. |
Tx Bytes Discarded—Q Overflow | This statistic provides a count of the number of octets in the frames counted in the Tx Frames Discarded - Q Overflow statistic (above). The octets counted include the Frame Relay header octets as well as the frame check sequence (FCS, or CRC) octets. This statistic is a subset of the PVC Transmit Bytes Discarded statistic. This statistic is a subset of the port Tx Bytes Discarded - Q Overflow statistic. |
Tx Frames Discarded - Ingress CRC | This statistic provides a count of the number of frames which were not able to be transmitted to the attached equipment because the frame is incomplete. Specifically, this statistic is incremented any time an end-of-frame (EOF) packet is missing. In other words: —a start-of-frame packet is followed by another start-of-frame packet, or start-of-frame packet is followed by an encapsulated-frame packet, or —a middle-of-frame packet is followed by a start-of-frame packet, or —middle-of-frame packet is followed by an encapsulated-frame packet The most likely cause of any of these conditions is a CRC error detected at ingress causing the end of the frame (including at least the end-of-frame packet and maybe one or more middle-of-frame packets) to not be sent. A less likely cause for the missing EOF packet is that the packet was dropped due to a transmission bit error in the packet header that is detected by a trunk along the PVC's path. Such conditions are included in this statistic. This statistic is a subset of the PVC Transmit Frames Discarded statistic. |
Tx Bytes Discarded—Ingress CRC | This statistic provides a count of the number of octets in the frames counted in the Tx Bytes Discarded - Ingress CRC statistic (above). The octets counted include the Frame Relay header octets as well as any octets which arrived successfully. This statistic is a subset of the PVC Transmit Bytes Discarded statistic. |
Tx Frames Discarded - Trunk Discard | This statistic provides a count of the number of frames that were not able to be transmitted to the attached equipment because the frame: has an incorrect length, that is, the expected frame length (recorded in the end-of-frame packet) is different than the total payload of all the packets which arrive. Such a frame length error could be caused by: —one or more packets being missing due to discard(s) on a trunk, or —a transmission bit error on the frame length field in the end-of-frame packet. —has an invalid length, that is, the frame is longer than 4510 octets long. This could occur if the end-of-frame packet from one frame and the start-of-frame packet of the next frame are both missing due to discards on a trunk, resulting in a concatenated frame. In any of the cases above, a packet could be discarded on a network trunk either due to extreme trunk congestion or a detected transmission bit error on the packet header. This statistic is a subset of the PVC Transmit Frames Discarded statistic. |
Tx Bytes Discarded - Trunk Discard | This statistic provides a count of the number of octets in the frames counted in the Tx Bytes Discarded - Trunk Discard statistic (above). The octets counted include the Frame Relay header octets as well as the frame check sequence (FCS, or CRC) octets. This statistic is a subset of the PVC Transmit Bytes Discarded statistic. |
Tx Frames During Ingress LMI Failure | This statistic provides a count of the number of frames that were transmitted to the attached equipment while the signaling protocol on the local port was failed (that is, when the port was in a Port Communication Failure state). This statistic is a subset of the PVC Frames Transmitted statistic |
Tx Bytes During Ingress LMI Failure
| This statistic provides a count of the number of octets in the frames counted in the Tx Frames During Ingress LMI Failure statistic (above). The octets counted include the Frame Relay header octets as well as the frame check sequence (FCS, or CRC) octets. |
| DE Feature Enabled | DE = 1 | > CIR | VC_Q > DE Threshold | Action |
No | Don't care | No | Don't care | Send |
No | Don't care | Yes | Don't care | Set CLP=E1 in all packets |
Yes | No | No | No | Send |
Yes | No | No | Yes | Set CLP=E1 in all packets |
Yes | No | Yes | No | Set CLP=E1 in all packets |
Yes | No | Yes | Yes | Set CLP=E1 in all packets |
Yes | Yes | Don't care | No | Set CLP=E1 in all packets |
Yes | Yes | Don't care | Yes | Discard frame |
| DE Feature Enabled | DE=1 | > CIR | VC_Q > DE Thresh | Action |
No | Don't care | No | Don't care | Send |
No | Don't care | Yes | Don't care | Set CLP=1 in all packets |
Don't care | No | No | No | Send |
Don't care | No | No | Yes | Set CLP=1 in all packets |
Don't care | No | Yes | No | Set CLP=1 in all packets |
Don't care | No | Yes | Yes | Set CLP=1 in all packets |
Yes | Yes | Don't care | No | Set CLP=1 in all packets |
Yes | Yes | Don't care | Yes | Discard frame |
| DE Feature Enabled | DE=1 | > CIR | Action |
No | Don't care | No | Send |
No | Don't care | Yes | Set CLP=1 in all packets |
Don't care | No | No | Send |
Don't care | No | Yes | Set CLP=1 in all packets |
Yes | Yes | Don't care | Set CLP=1 in all packets |
| IDE = 1 | IDE = 1 | IDE to DE Mapping Enabled | Action |
Yes | Don't care | Don't care | DE=1 (No change to DE bit) --> Tx_Q |
No | No | Don't care | DE=1 (No change to DE bit) --> Tx_Q |
No | Yes | No | DE=1 (No change to DE bit) --> Tx_Q |
No | Yes | Yes | DE=1 (Change DE bit) --> Tx_Q |
| DE Feature Enabled | DE=1 | Tx_Q > DE Threshold | Action |
No | Don't care | Don't care | If space available, put frame into Tx_Q |
Yes | No | Don't care | If space available, put frame into Tx_Q |
Yes | Yes | No | If space available, put frame into Tx_Q |
Yes | Yes | Yes | Discard frame |
Display Frame Relay channel statistics
dspchstats <channel> [interval]
clrchstats, cnfchstats
| Privilege | Jobs | Log | Node | Lock |
1-6 | No | No | IGX | No |
dspchstats 5.1.100
Display the channel statistics for connection 5.1.100.
pubsigx1 TN SuperUser IGX 8420 9.2 Aug. 7 1998 04:04 PDT
Channel Statistics: 5.1.100 Cleared: July 25 1997 06:07
MIR: 9.6 kbps Collection Time: 12 day(s) 21:48:41 Corrupted: YES
Frames Avg Size Avg Util Packets Avg
(bytes) (fps) (%) (pps)
From Port: 0 0 0 0
To Network: 0 0 0 0 58732 0
Discarded: 0 0 0 0
From Network: 1 5 0 0 1 0
To Port: 0 0 0 0
Discarded: 1 5 0 0 1 0
ECN Stats: Avg Rx VC Q: 0 ForeSight RTD --
Min-Pk bytes rcvd: 0 FECN Frames: 0 FECN Ratio (%) 0
Minutes Congested: 0 BECN Frames: 0 BECN Ratio (%) 0
Frames rcvd in excess of CIR: 0 Bytes rcvd in excess of CIR: 0
Frames xmtd in excess of CIR: 0 Bytes xmtd in excess of CIR: 0
This Command: dspchstats 5.1.100
Hit DEL key to quit:
| Parameter | Description |
|---|---|
channel | Specifies the channel. The command displays connection information for one channel at a time, so you cannot specify a range of channels. The format for channel is slot.port. |
| Parameter | Description |
|---|---|
interval | Specifies the refresh interval for displaying data. The range is 1-60 seconds. The default is 10 seconds. If you do not specify a value for the refresh interval, the screen refresh defaults to 10. If the Rx Q depth and the Tx Q depth fields remain "0", make sure that a value other than "0" is specified for the interval parameter. |
Displays connection information for a channel. The information displayed includes:
A failure that affects the connection flashes on the screen. For Frame Relay NNI ports, the NNI value indicates the Abit value was received over the NNI from the remote network. The possible status messages are:
♦ OK | Connection OK. |
♦ FAILED | Connection failed. |
♦ MISSING | DLCI was deleted in other network at NNI. A previous status report indicated a valid DLCI was present but an updated report did not. |
♦ UNUSED | Indicates the UNI port does not support reporting of NNI Abit status. |
Display connections
dspcon <slot.port.DLCI>
addcon, cnfcos, cnfpref, cnfrtcost, dspcons
| Privilege | Jobs | Log | Node | Lock |
1-6 | No | No | IGX | No |
dspcon 19.1.101
Display connection information for Frame Relay channel 19.1.101 (cost based routing is configured).
beta TRM YourID:1 IGX 8430 9.2 Aug. 15 1998 15:42 MST
Conn: 19.1.101 gamma 8.2.300 fr
MIR CIR VC Q Depth PIR Cmax ECN QThresh QIR FST
9.6/9.6 9.6/9.6 65535/65535 256/256 10/10 65535/65535 9.6/9.6 n
% Util: 100/100
Owner: LOCAL Restriction: NONE COS: 0 Status: OK
TestRTD: 0 msec Trunk Cell Routing Restrict: Y Max Cost: 100 Route Cost: 36
Path: beta 15--15gamma
Pref: Not Configured
beta 19.1.101 gamma 8.2.300
FRP: OK FRP: OK
FRI: OK FRI: OK
Last Command: dspcon 19.1.101
Next Command:
| Parameter | Description |
|---|---|
channel | Specifies the channel in the format slot.port.DLCI. The dspcon command displays information for one connection at a time. |
Displays information about the connections on an IGX node. The following table lists all possible information headings that appear in the display. The actual headings that appear depend on the choice of selected optional parameters—including no parameters. Entering the command with no parameters displays all connections. The screen examples in this description reflect various parameter options, including no parameters.
The OAM Loopback Test (configured with cnfoamlpbk command) will consider a PVC to be failed if ten consecutive loopback cells do not return. When a failure occurs, this information will be stored in switch software. The test will continue to run even when connections are in a failed state. You can view the results of the test by using the dspcons -oam command.
You can view a display of connections that have failed the OAM Loopback Test by using the dspcons command. The dspcons command with no optional parameters will show all connections, and those that have failed the OAM Loopback Test but are otherwise OK will show a state of "OAM". Other states will supersede OAM. You can use the dspcons -oam command to view all connections that have failed the OAM Loopback Test. When an OAM Loopback failure occurs, the state field shows "OAM-F".
| Fields | Description | |
|---|---|---|
Local Channel | The connection's channel at this node. | |
Remote Node Name | The name of the node at the other end of the connection. | |
Remote Channel | The connection's channel at the remote node. | |
State | The possible connections states are as follows: | |
| State | Description |
| OK | routed, Abit = 1. |
| Down | downed. |
| Failed | unrouted, but trying; Abit = 0. |
| Unused | The UNI port does not support reporting of NNI Abit status. |
| OAM | Connections that have failed OAM Loopback test, but are otherwise OK. |
| OAM-F | Indicates OAM Loopback failure |
Type | The type of connection. For example, this can be Frame Relay, Frame Relay with interworking, voice, data, and so on. | |
Only __ | If one parameter pre-empts another, this heading appears with the accepted parameter type. To name two examples: if the parameter is -d for data or -fail for failed connections only, this heading becomes either "Only d" or Only fail," respectively. | |
Code | The encoding used for data connections (7/8 = data byte is 7 bits of user data plus a "1" in the last bit position, 8/8 = data byte is 8 bits of user data, 8/8I = data byte is 8 bits of inverted user data). | |
Route Avoid | The type of lines to avoid when routing (satellite lines, terrestrial lines, lines with zero code suppression). | |
Compression | The type of compression applied to the connection (PCM, PCM and VAD, ADPCM, VAD and ADPCM for voice connections), (DFM for data connections). | |
COS | The Class Of Service. | |
Abit | Abit status at both ends of the connection. | |
Loopback | This is not a heading but rather the standard loopback symbols indicating the presence of a test loop. See the "Troubleshooting" chapter for an explanation of these symbols. | |
Display connections
dspcons [start_channel] [nodename] [-f] [-v] [-d] [-atfr] [-abit] [-fabit] [-fail] [-down]
where
start_channel | is the starting channel to display |
nodename | specifies that connections for only the named node appear in the display |
-f | equals display Frame Relay connection only |
-v | equals display only voice connections |
-d | equals display only data connections and do so in Kbps. |
-atfr | equals Frame Relay to ATM interworking connections (also displays atfr with ForeSight) |
-abit | equals show status of the Abit |
-fabit | equals show only connections with failed A-bits |
-fail | equals show only failed connections |
-down | equals show only downed connections |
addcon, cnfchadv, chfchdfm
| Privilege | Jobs | Log | Node | Lock |
1-6 | No | No | IGX | No |
dspcons
Displays all connections
sw83 VT SuperUser IGX 8430 9.2 Aug. 14 1998 12:58 PST
From Remote Remote
3.1.27 NodeName Channel State Type Compress Code COS
3.1.27 sw86 13.1.1.27 Ok atfst 0
3.1.28 sw86 13.1.1.28 Ok atfst 0
3.1.29 sw86 13.1.1.29 Ok atfst 0
3.1.30 sw86 13.1.1.30 Ok atfst 0
3.1.31 sw86 13.1.1.31 Ok atfst 0
3.1.32 sw86 13.1.1.32 Ok atfst 0
3.1.33 sw86 13.1.1.33 Ok atfst 0
3.1.34 sw86 13.1.1.34 Ok atfst 0
3.1.35 sw86 13.1.1.35 Ok atfst 0
3.1.36 sw86 13.1.1.36 Ok atfst 0
3.1.37 sw86 13.1.1.37 Ok atfst 0
3.1.38 sw86 13.1.1.38 Ok atfst 0
3.1.39 sw86 13.1.1.39 Ok atfst 0
This Command: dspcons
Continue?
dspcons 19.1
Display connections starting with 19.1. This example shows frame and data connections.
beta TRM YourID:1 IGX 8430 9.2 Aug. 15 1998 15:37 MST
Local Remote Remote Route
Channel NodeName Channel State Type Compression Code Avoid COS O
19.1.101 gamma 8.2.300 Ok fr 0 L
19.2.302 alpha 9.2.400 Ok fr 0 R
25.1 alpha 5.1 Ok 256 7/8 0 L
25.2 gamma 6.1 Ok 256 7/8 0 L
Last Command: dspcons 19.1
Next Command:
dspcons -f
Display Frame Relay connections only.
beta TRM YourID:1 IGX 8430 9.2 Aug. 15 1998 15:38 MST
Local Remote Remote Only Route
Channel NodeName Channel State f Compression Code Avoid COS O
19.1.101 gamma 8.2.300 Ok fr 0 L
19.2.302 alpha 9.2.400 Ok fr 0 R
Last Command: dspcons -f
Next Command:
dspcons -abit
Display connections and show the status of the Abit on the local and remote nodes.
sw83 VT SuperUser IGX 8410 9.2 Aug. 14 1998 13:02 PST
Local Remote Remote Local Remote
Channel NodeName Channel State Abit Abit
3.1.1 sw86 13.1.1.1 Ok OK OK
3.1.2 sw86 13.1.1.2 Ok OK OK
3.1.3 sw86 13.1.1.3 Ok OK OK
3.1.4 sw86 13.1.1.4 Ok OK OK
3.1.5 sw86 13.1.1.5 Ok OK OK
3.1.6 sw86 13.1.1.6 Ok OK OK
3.1.7 sw86 13.1.1.7 Ok OK OK
3.1.8 sw86 13.1.1.8 Ok OK OK
3.1.9 sw86 13.1.1.9 Ok OK OK
3.1.10 sw86 13.1.1.10 Ok OK OK
3.1.11 sw86 13.1.1.11 Ok OK OK
3.1.12 sw86 13.1.1.12 Ok OK OK
3.1.13 sw86 13.1.1.13 Ok OK OK
This Command: dspcons -abit
Continue?
dspcons
Display connections
sw99 TN StrataCom BPX 8620 9.2.10 Aug. 27 1998 08:59 GMT
Local Remote Remote Route
Channel NodeName Channel State Type Avoid COS O
------- -------- ------- ----- ---- ----- --- --
3.2.6.16 sw14 10.1.6.16 Ok vbr 0 L
3.2.6.17 sw14 10.1.6.17 Ok vbr 0 L
3.2.6.18 sw14 10.1.6.18 Ok vbr 0 L
3.2.6.19 sw14 10.1.6.19 Ok vbr 0 L
3.2.6.20 sw14 10.1.6.20 Ok vbr 0 L
3.2.6.21 sw14 10.1.6.21 Ok vbr 0 L
3.2.6.22 sw14 10.1.6.22 Ok vbr 0 L
3.2.6.16 sw157 16.1.6 Failed atfr 0 L
3.2.6.17 sw157 16.1.7 Failed atfr 0 L
3.2.8.18 sw157 16.1.8 OAM-F atfr 0 L
3.2.8.19 sw157 16.1.9 OAM-F atfr 0 L
Last Command: dspcons
dspcons -oam
Display connections that have failed the OAM Loopback test
sw99 TN StrataCom BPX 15 9.2.10 Aug. 27 1998 08:59 GMT
Local Remote Remote Route
Channel NodeName Channel State Type Avoid COS O
------- -------- ------- ----- ---- ----- --- --
3.2.6.16 sw157 16.1.6 OAM-F atfr 0 L
3.2.6.17 sw157 16.1.7 OAM-F atfr 0 L
3.2.8.18 sw157 16.1.8 OAM-F atfr 0 L
3.2.8.19 sw157 16.1.9 OAM-F atfr 0 L
Last Command: dspcons -oam
Next Command:
| Parameter | Description |
|---|---|
start channel | Specifies the channel to begin the display. Specify start channel in one of the following formats: slot.port.DLCI (Frame Relay channel) If you do not specify a starting channel, the display begins at the first connection. |
node name | Specifies that only connections to this remote node from the local note be displayed. If no nodename is designated, connections from the local node to all other nodes are displayed. |
(connection types) | Specifies that only connections of a certain type be displayed. If you do not add at least one argument to specify a particular connection type, all connections appear. When you enter the connection type on the command line, precede it with a hyphen (-). In some cases, you can add more than one connection type (with a space between), but not all compound arguments are compatible, so you may not always see the expected combination of types. The connection types are: -v displays only voice connections. -d displays only data connections. -f displays only Frame Relay connections. -abit shows Abit (nni) status. -fabit shows connections with failed Abit (nni) status. -fail shows only failed connections. -siw shows service interworking connections. -atfr shows only network interworking connections. |
Displays the configuration of a Frame Relay class. Network-wide classes are available to provide a shortcut for adding Frame Relay connections. Refer to the section titled "Using Frame Relay Classes " at the beginning of this chapter for a definition of a Frame Relay class.
The */* in the PIR (Peak Information Rate) column means that if a connection is added using this Frame Relay class, the PIR for this connection will be equal to that of the port speed on which the connection was added. For example, if the port speed for port 6.1 = 64 kbps, and if a connection 6.1.100 is adding using the Frame Relay class, it will have a value of 64 kbps for the PIR parameter.
Display Frame Relay classes
dspfrcls
addcon, cnffrcls
| Privilege | Jobs | Log | Node | Lock |
1-2 | No | No | IGX | No |
dspfrcls
Display the Frame Relay class configurations.
The screen display is the same as that for the cnffrcls command.
sw83 TN SuperUser IGX 8420 9.2 Aug. 23 1998 13:43 GMT
Frame Relay Connection Classes
# MIR CIR VC Q Depth PIR Cmax ECN QThresh
1 9.6/9.6 9.6/9.6 65535/65535 */* 10/10 65535/65535
QIR: 9.6/9.6 FST: n % Util: 100/100 Description: "Default 9.6"
2 19.2/19.2 19.2/19.2 65535/65535 */* 10/10 65535/65535
QIR: 19.2/19.2 FST: n % Util: 100/100 Description: "Default 19.2"
3 16/16 16/16 65535/65535 */* 10/10 65535/65535
QIR: 16/16 FST: n % Util: 100/100 Description: "Default 16"
4 32/32 32/32 65535/65535 */* 10/10 65535/65535
QIR: 32/32 FST: n % Util: 100/100 Description: "Default 32"
5 56/56 56/56 65535/65535 */* 10/10 65535/65535
QIR: 56/56 FST: n % Util: 100/100 Description: "Default 56"
This Command: dspfrcls
Continue?
Displays information on Frame Relay cards and physical and logical ports. The applicable card sets are the FRP, FRM, and UFM. The content of the information display depends on the arguments you include with the command. The information can be:
The following are examples of the dspfrport command syntax:
| dspfrport | Display the states of all Frame Relay ports in the node. |
| dspfrport 8 | Display the port states for FRP in slot 8. |
| dspfrport 8.1 | Display the configuration for port 1 of the FRP in slot 8. |
| dspfrport 6.44 | Display the configuration for logical port 44 of the FRP-2 in slot 6. |
The following is a list of possible displayed port parameters for a single port. For a more detailed description of these parameters, refer to the cnffrport command.
| Parameters | Parameters |
|---|---|
Port number | Polling Verification Timer |
DLCI number | Error Threshold |
State: Active or inactive | Monitored Events Count |
Interface Type: V.35 or X.21, DCE or DTE | Priority Communicated |
Configured clock speed in Kbps | The lead states in the Interface Control Template |
Measured clock speed in Kbps | Receiver Not Ready Thresholds |
The port VC queue depth in bytes | Flags per frame |
The VC queue ECN threshold in bytes | OAM FastPacket Threshold (for NNI ports) |
The DE threshold | Link Integrity Timer (for NNI ports FRP rev. F/H or above) |
The Signaling Protocol | Full Status Polling cycle (for NNI ports) |
Asynchronous Status |
|
Display Frame Relay port
dspfrport [slot | slot.port]
cnffrport, upfrport, dnfrport
| Privilege | Jobs | Log | Node | Lock |
1-2 | No | No | IGX | No |
dspfrport
Display the port status of the Frame Relay ports in the node.
alpha TRM YourID:1 IGX 8420 9.2 Aug. 15 1997 15:48 PST
FRP Port States
Port ID State
9.1 0 ACTIVE
9.2 0 ACTIVE
9.3 0 INACTIVE
9.4 0 INACTIVE
Last Command: dspfrport
Next Command:
dspfrport 5
Display the status of the ports on the FRP in slot 5.
pubsipx1 TN SuperUser IGX 8420 9.2 Sep. 7 1997 02:11 PDT
Port configuration for FRP 5
Port ID Speed Interface State Protocol Port Type
1 0 256 FRI-V35 (DCE) ACTIVE None FR
2 0 256 FRI-V35 (DCE) INACTIVE None FR
3 0 256 FRI-V35 (DCE) INACTIVE None FR
4 0 256 FRI-V35 (DCE) INACTIVE None FR
Last Command: dspfrport 5
Next Command:
dspfrport 5.1
Display port status for logical Frame Relay port 5.1. In the example, note the range of channels.
sw109 VT SuperUser IGX 16 9.2 Aug. 21 1997 18:14 GMT
Port: 5.1 [ACTIVE ]
Interface: E1B Configured Clock: 960 Kbps
Clocking: None Measured Rx Clock: None
Port ID - Min Flags / Frames 1
Port Queue Depth 32000 OAM Pkt Threshold 3 pkts
ECN Queue Threshold 65535 T391 Link Intg Timer 10 sec
DE Threshold 100 % N391 Full Status Poll 6 cyl
Signalling Protocol None EFCI Mapping Enabled No
Asynchronous Status No CLLM Enabled/Tx Timer No/ 0 msec
T392 Polling Verif Timer 15 IDE to DE Mapping Yes
N392 Error Threshold 3 Channel Speed 64
N393 Monitored Events Count 4 Line Number 1
Communicate Priority No Channel Range 1-15
Upper/Lower RNR Thresh 75%/ 25%
Last Command: dspfrport 5.1
Next Command:
dspfrport 5
Display port status for all the Port Concentrator ports at slot 5.
tecate LAN SuperUser IGX 8420 9.2 Aug. 6 1997 09:59 PST
Port configuration for FRP 5
Port ID Speed Interface State Protocol
1 0 64 V.35 (DCE) ACTIVE None
2 0 64 V.35 (DCE) ACTIVE None
3 0 38.4 V.11 (DTE) ACTIVE None
4 0 38.4 V.11 (DCE) ACTIVE None
5 0 38.4 V.11 (DCE) ACTIVE None
6 0 38.4 V.11 (DTE) ACTIVE None
7 0 19.2 V.11 (DCE) ACTIVE None
8 0 19.2 V.28 (DCE) ACTIVE None
9 0 19.2 V.28 (DTE) ACTIVE None
10 0 38.4 V.28 (DCE) INACTIVE None
11 0 38.4 V.28 (DCE) INACTIVE None
12 0 38.4 V.28 (DCE) INACTIVE None
Last Command: dspfrport 5
Continue?
dspfrport 6.44
Display port configuration for Frame Relay port 6.44 (a Port Concentrator port).
singha TN SuperUser IPX 32 9.2 July 7 1997 13:38 GMT
Port: 6.44 [FAILED]
Interface: V.11 DCE Configured Clock: 38.4 Kbps
Clocking: Normal Startup Rx Clock: 0 Kbps
Min Flags / Frames 1
Port ID 0
Port Queue Depth 65535 OAM Pkt Threshold 3 pkts
ECN Queue Threshold 65535 T391 Link Intg Timer 10 sec
DE Threshold 100 % N391 Full Status Poll 6 cyl
Signalling Protocol None EFCI Mapping Enabled No
Asynchronous Status No CLLM Enabled/Tx Timer No/ 0 msec
T392 Polling Verif Timer 15 IDE to DE Mapping Yes
N392 Error Threshold 3 Interface Control Template
N393 Monitored Events Count 4 Lead I
Communicate Priority No State ON
Upper/Lower RNR Thresh 75%/ 25%
Last Command: dspfrport 6.44
Next Command:
Displays physical port configuration for FRM-2 or FRP-2 ports connected to a Port Concentrator. The following is a list of possible displayed parameters for a port.
| Field | Meaning |
|---|---|
Interface | |
Clocking | Always Normal for PCS ports. |
Port Type | Specifies port type, always FR (Frame Relay) for PCS ports. |
Port ID | Specifies the DLCI for the port, always 1022 for PCS ports. |
Port Queue Depth | Specifies the maximum bytes queued for transmission from the FRM-2 or FRP-2 port. The range is 0-65535; 65535 is the default. |
DE Threshold | Specifies the port depth queue above which frames with the Discard Eligibility bit set will be discarded. Valid entries are 0-100%, with a default of 100%. 100% effectively disables DE for the port. |
Signaling Protocol | For Frame Relay ports, specifies LMI operation mode. For PCS ports, this is set to None. |
Measured Rx Clock | The actual speed of received data as clocked by the FRM-2 or FRP-2. Under normal operation, this should always display the fixed concentrated link speed of 512 Kbps. Clock speed is measured by the FRM-2 or FRP-2 once per minute. |
Concentrated Link Util | Current utilization percentage of the concentrated link. Utilization is defined as the percentage of the fixed link speed (512K) used for data. Since the maximum allowable aggregate for each link's 11 ports is 448 Kbps, 88% is the maximum value for this field. |
Min Flags / Frames | Specifies the minimum number of flags per frame. All values greater than zero are valid; the default is 1. |
OAM Pkt Threshold | Specifies the OAM FastPackets used within the local node to transmit the NNI status from the remote network. The range of values is 0-15 packets. The default is 3. A 0 disables this function. |
Display FRC-2/FRM-2 port configuration
dspfrcport <slot.port> <interval>
dspfrcport, dspbob
| Privilege | Jobs | Log | Node | Lock |
1-2 | No | No | IPX, IGX | No |
dspfrcport 3.1
Display the configuration of port 3.1.
tecate LAN SuperUser IGX 8420 9.2 Aug. 6 1998 10:25 PST
Physical Port: 3.1 [ACTIVE]
Interface: FRI-X.21 DCE Configured Clock: 512 Kbps
Clocking: Normal Measured Rx Clock: 512 Kbps
Port Type FR Min Flags / Frames 1
Port ID 1022
Port Queue Depth 65535 OAM Pkt Threshold 3 pkts
ECN Queue Threshold 65535 T391 Link Intg Timer 6 sec
DE Threshold 100 % N391 Full Status Poll 10 cyl
Signalling Protocol None ForeSight (CLLM) No
Asynchronous Status No CLLM Status Tx Timer 0 msec
T392 Polling Verif Timer 15 IDE to DE Mapping Yes
N392 Error Threshold 3 Interface Control Template
N393 Monitored Events Count 4 Lead I
Communicate Priority No State ON
Upper/Lower RNR Thresh 75%/ 25% Concentrated Link Util 88%
Last Command: dspfrcport 3.1
Next Command:
| Parameter | Description |
|---|---|
slot.port | Specifies the physical slot and port of the Frame Relay card set. The range is 1-4. |
interval | Specifies the screen update interval in seconds. The default is five seconds |
Displays interface control template information for data channels and Frame Relay ports. The information includes:
The specified channel.
The type of template: a, c, l, n, or f.
The associated output leads and their status:
For Frame Relay ports, the entire port configuration screen is displayed (see dspfrport command). The input being followed is specified, when applicable. Any RTS to CTS delay is also shown.
Display interface control template
dspict <port> <template>
cnfict, cpyict
| Privilege | Jobs | Log | Node | Lock |
1-2 | No | No | IPX, IGX | No |
dspict 25.1 a
Display the active interface control template for channel 25.1.
beta TRM YourID:1 IPX 32 9.2 Aug. 15 1997 17:33 MST
Data Channel: 25.1
Interface: RS232 DCE
Clocking: Normal
Interface Control Template for Connection while ACTIVE
Lead Output Value Lead Output Value
RI OFF DSR ON
CTS ON SRxD ON
DCR OFF DCD ON
SCTS ON SDCD ON
SQ ON
Last Command: dspict 25.1 a
Next Command:
dspict 9.1 a
Display the Frame Relay data channel 9.1 interface control template.
alpha TRM YourID:1 IGX 8420 9.2 Aug. 23 1997 10:26 PST
Port: 9.1 [ACTIVE ]
Interface: FRI-V35 DTE Configured Clock: 256 Kbps
Clocking: Normal Measured Rx Clock: 0 Kbps
Port ID 7
Port Queue Depth 65535 OAM Pkt Threshold 3 pkts
ECN Queue Threshold 65535 T391 Link Intg Timer 6 sec
DE Threshold 100 % N391 Full Status Poll 10 cyl
Signalling Protocol None ForeSight (CLLM) No
Asynchronous Status No CLLM Status Tx Timer 0 msec
T392 Polling Verif Timer 15 Interface Control Template
N392 Error Threshold 3 Lead State
N393 Monitored Events Count 4 RTS ON
Communicate Priority No DTR ON
Upper/Lower RNR Thresh 75%/ 25%
Min Flags / Frames 1
Last Command: dspict 9.1 a
Next Command:
| Parameter | Description |
|---|---|
port | Specifies the physical slot and port of the Frame Relay card set. |
template | Specifies the template. Choices are a, c, n, l, and f. |
Displays the mode of the card. The mode applies only to a UFM-U back card. The UFM-U back cards are the UFI-12V.35, UFI-12X.21, and UFI-4HSSI. A card mode is a combination of maximum port speeds and for specific port numbers. Table 8-40 lists the maximum port speeds and active ports for each mode. For a description of the UFM-U modes, see the UFM-U description in the Cisco IGX 8400 Series Reference.
| V.35 and X.21 Ports | HSSI Ports | |||
|---|---|---|---|---|
| Group A | Group B | Group C | ||
| Mode | 1 2 3 4 | 5 6 7 8 | 9 10 11 12 | 1 2 3 4 |
1 | 3 3 3 3 | 3 3 3 3 | 3 3 3 3 | 8 8 8 8 |
2 | 8 - 8 - | 8 - 8 - | 8 - 8 - | 16 - 16 - |
3 | 10 - - - | 10 - - - | 10 - - - | 16 - - - |
4 | 8 - 8 - | 3 3 3 3 | 3 3 3 3 |
|
5 | 10 - - - | 3 3 3 3 | 3 3 3 3 |
|
6 | 8 - 8 - | 8 - 8 - | 3 3 3 3 |
|
7 | 10 - - - | 8 - 8 - | 3 3 3 3 |
|
8 | 10 - - - | 10 - - - | 3 3 3 3 |
|
9 | 10 - - - | 8 - 8 - | 8 - 8 - |
|
10 | 10 - - - | 10 - - - | 8 - 8 - |
|
11 | 3 3 3 3 | 8 - 8 - | 3 3 3 3 |
|
12 | 3 3 3 3 | 3 3 3 3 | 8 - 8 - |
|
13 | 3 3 3 3 | 10 - - - | 3 3 3 3 |
|
14 | 3 3 3 3 | 3 3 3 3 | 10 - - - |
|
15 | 8 - 8 - | 3 3 3 3 | 8 - 8 - |
|
16 | 3 3 3 3 | 8 - 8 - | 8 - 8 - |
|
17 | 8 - 8 - | 10 - - - | 3 3 3 3 |
|
18 | 8 - 8 - | 3 3 3 3 | 10 - - - |
|
19 | 3 3 3 3 | 8 - 8 - | 10 - - - |
|
20 | 3 3 3 3 | 10 - - - | 8 - 8 - |
|
21 | 10 - - - | 3 3 3 3 | 8 - 8 - |
|
22 | 10 - - - | 3 3 3 3 | 10 - - - |
|
23 | 3 3 3 3 | 10 - - - | 10 - - - |
|
24 | 8 - 8 - | 10 - - - | 8 - 8 - |
|
25 | 8 - 8 - | 8 - 8 - | 10 - - - |
|
26 | 10 - - - | 8 - 8 - | 10 - - - |
|
27 | 8 - 8 - | 10 - - - | 10 - - - |
|
Display mode
dspmode <slot>
cnffrport, cnfmode, dspmodes
| Privilege | Jobs | Log | Node | Lock |
1-6 | No | Yes | IGX | Yes |
dspmode 13
Display the mode of the UFM-U in slot 13.
sw180 TN SuperUser IGX 16 9.2 July 30 1997 01:39 GMT
UFMU Card Mode Configuration
Slot Number Configured Mode Available Ports Currently Activated Ports
13 1 [111111111111] [100000000000]
Last Command: dspmode 13
Next Command:
| Parameter | Description | |||
|---|---|---|---|---|
slot | Specifies the slot of the UFM-U card. | |||
Displays the ports that are active with each mode of an unchannelized UFM. The mode applies only to a UFM-U back card. The UFM-U back cards are the UFI-12V.35, UFI-12X.21, and UFI-4HSSI. A card mode is a combination of maximum port speeds and specific port numbers. Refer to the description of dspmode for the table that lists the maximum port speeds and active ports for each mode. For a description of the UFM-U modes, see the UFM-U description in the Cisco IGX 8400 Series Reference.
The dspmodes command takes no parameters. Also, note that only the first three modes apply to a UFI-4HSSI.
Display mode
dspmode
cnffrport, cnfmode, dspmode
| Privilege | Jobs | Log | Node | Lock |
1-6 | No | Yes | IPX, IGX | Yes |
dspmodes
Display the possible modes.
sw180 TN SuperUser IGX 16 9.2 July 30 1997 01:39 GMT
UFMU Card Mode Configuration
Slot Number Configured Mode Available Ports Currently Activated Ports
13 1 [111111111111] [100000000000]
Last Command: dspmode 13
Next Command:
Displays status and level information for either a specific Port Concentrator Shelf or all Port Concentrators attached to the node. When the command has a specific slot number for an argument, information appears for each concentrated link. The information for each concentrated link is as follows (see also Example 1):
Status, where "OK" means the FRM-2 or FRP-2 is communicating with the PCS, and "Failed" means the FRM-2 or FRP-2 is not communicating with the PCS on the concentrated link.
When the command executes without a specified slot, a general status statement and the firmware revision for each port appear (see Example 2).
Display Port Concentrator Shelf
dspport [slot]
cnffrport, dspfrcport, dspfrcbob, dspportstats
| Privilege | Jobs | Log | Node | Lock |
1-3 | No | No | IPX, IGX | No |
dsppcs 6
Display PCS information for port 6.
singha TN SuperUser IPX 32 9.2 July 7 1997 14:04 GMT
Detailed Port Concentrator Display For FRP in slot 6
Link Number: 1 Link Number: 3
Status: Failed Status: OK
Test Status: No Test Test Status: Passed
FW Revision: FW Revision: P3
Boot PROM Date: Boot PROM Date: 11/9/95
Boot PROM Revision: Boot PROM Revision: P3
Link Number: 2 Link Number: 4
Status: Failed Status: OK
Test Status: No Test Test Status: Passed
FW Revision: FW Revision: P3
Boot PROM Date: Boot PROM Date: 11/9/95
Boot PROM Revision: Boot PROM Revision: P3
Last Command: dsppcs 6
Next Command:
dsppcs
Display information for all Port Concentrator Shelves.
singha TN SuperUser IPX 32 9.2 July 7 1997 14:02 GMT
Port Concentrator Status
Slot.Port Status FW Revision
6.1 Failed
6.2 Failed
6.3 OK P3
6.4 OK P3
Last Command: dsppcs
Next Command:
| Parameter | Description |
|---|---|
slot | Specifies slot associated with the ports you want to display. |
Displays port IDs. The port ID is a user-specified identifier for a particular Frame Relay port where several virtual circuits share the same physical interface. The port ID can be any numeric value in the range 1-1024. The command for specifying a port ID is cnffrport. Note that a Port Concentrator does not use port IDs.
Display port IDs
dspport IDs
cnffrport
| Privilege | Jobs | Log | Node | Lock |
1-2 | No | No | IPX, IGX | No |
dspportids
Display the port IDs throughout the network.
alpha TRM YourID:1 IGX 8420 9.2 Aug. 15 1997 15:55 PST
Frame Relay Port IDs
ID Node
7 alpha |
9 alpha |
Last Command: dspportids
Next Command:
Displays a summary of port statistics for a Frame Relay port. Statistics include the data byte count in the transmit and receive directions and error counts associated with the port. The display indicates the date and time the statistics were cleared and the amount of time since the node last cleared the statistics. Bytes transmitted indicates the amount of data transmitted from the port to the user device. Bytes received indicates the amount of data received at the port from the user device.
Corrupted statistics result from channel/port loopbacks or port tests. A "yes" in this field indicates that loopback or port tests have occurred since the statistics were last cleared. The statistics for User-to-Network Interface (UNI) ports (connections to user devices) are displayed with one screen. The following lists usage statistics displayed in screen 1.
The dspportstats command also displays the following statistics: IMA port summary statistics. A summary and description of these statistics follows:
| Statistics | Description |
|---|---|
IMA Unavailable Seconds |
|
IMA Near end Failed counts |
|
Last IMA protocol failure code |
|
| Frame Errors | LMI Statistics | Miscellaneous Statistics |
|---|---|---|
Invalid CRC | Status Enquiries Received | Average TX Port Q |
Invalid Alignment | Status Transmitted | FECN Frames |
Invalid Frame Length | Update Transmit | FECN Ratio (%) |
Invalid Frame Format | Invalid Requests | BECN Frames |
Unknown DLCIs | Sequence # Mismatches | BECN Ratio (%) |
Last Unknown DLCI | Timeouts | Resource Overflow |
| Signaling Protocol | DE Frames Dropped (Egress) |
Network to Network (NNI) ports require two screens to display all the parameters. The first screen is the same as described previously for UNI ports—you display the second screen by responding with a "y" for yes to the Continue? prompt. The second screen compares receive LMI statistics with transmit LMI statistics. The LMI receive statistics are repeated from the middle column of the first screen and displayed again so you can compare them. The following lists the usage statistics in screen 2.
| LMI Receive Protocol Stats | LMI Transmit Protocol Statistics |
|---|---|
Status Enquiries Received | Status Inquiries Transmitted |
Status Enquiries Transmitted | Status Received |
Asynchronous Status Transmitted | Asynchronous Status Received |
Sequence # Mismatches | Sequence # Mismatches |
Timeouts | Timeouts |
Invalid Frames |
|
Signaling Protocol |
|
The command displays the following statistics: frame error, LMI, and miscellaneous. A summary and description of these statistics follows:
| Statistics | Description |
|---|---|
CRC Errors | Based on a CRC CCITT 16-bit frame check sequence, which is a cyclic redundancy check. If the frame received at a port has an incorrect CRC, it is flagged as a CRC error, and the frame is discarded. Receive Frame CRC Errors (Ingress). Provides a count of the number of frames received from the attached equipment in which the CRC calculated by the IGX does not match the CRC provided by the attached equipment in the last 2 octets of the frame. Any frame received with an incorrect CRC is discard by the network. However, the IGX does not wait to receive the entire frame before starting to packetize the frame and send it through the network. As long as the frame header format is valid (see Invalid Format Receive Frames statistic) and the DLCI field in the frame header is recognized (see Receive Frames Undefined DLCI Count statistic below), packets containing the beginning of the frame are created (one start-of-frame (SOF) packet and subsequent middle-of-frame (MOF) packets) and sent as soon as possible. If the frame is short and if there are other packets already waiting to be sent, the detection of the CRC error will cause all the packets of the frame to be discarded. However, if the frame is long and there is no congestion in the ingress VC queue, some packets are sent through the network before the CRC error is detected. As soon as the CRC error is detected, any portion of the frame that has not yet been sent is discarded. In particular, no end of frame (EOF) packet is ever sent. At the far end, when an SOF packet arrives that does not immediately follow an EOF packet, the incomplete frame is discard and counted in the PVC statistic of Transmit Frames Discarded. If the CRC is incorrect because of a bit error in the DLCI field in the frame header, then the error will also be recorded as a Receive Frame with Undefined DLCI unless the reerrored's DLCI is also configured on the port. This statistic is a subset of the Frames Received statistic. |
Alignment error | Frame was not an integral number of bytes. Receive Frame Alignment Errors (Ingress). This statistic provides a count of the number of frames received from the attached equipment in which the total frame length is not an integral number of octets. Any frame received with an incorrect alignment is discarded by the network. However, the IGX does not wait to receive the entire frame before starting the packetize the frame and send it to the network. As long as the frame header format is valid (See Invalid Format Receive Frames statistic), and the DLCI field in the frame header is recognized (see Receive Frames Undefined DLCI Count statistic), packets containing the beginning of the frame are created (one start-of-frame (SOF) packet and subsequent middle-of-frame (MOF) packets) and sent as soon as possible. If the frame is short or if there are other packets already waiting to be sent, the detection of the alignment error will cause all the packets of the frame to be discarded. However, if the frame is long and there is no congestion in the ingress VC queue, some packets are sent through the network before the alignment error is detected. As soon as the alignment error is detected, any portion of the frame that has not yet been sent is discarded. In particular, no end-of-frame (EOF) packet is ever sent. When the next frame arrives, a new SOF packet is sent, etc. At the far end, when a SOF packet arrives that does not immediately follow an EOF packet, the incomplete frame is discarded and counted in the PVC statistic of Transmit Frames Discarded. This statistic is a subset of the Frames Received statistic. |
Frame length errors | Frames < 5 bytes or >4096 bytes. Illegal Length Receive Frames (Ingress). Provides a count of the number of frames received from the attached equipment in which the total frame length is either too short or too long. To be accepted, a frame must be at least five octets, but no more than 4510 octets long, including the header and frame check sequence (FCS, or CRC) octets. Any frame received with an invalid length is discard by the network. A frame that is too short is immediately detected and discarded. For a frame that is too long, the IGX does not wait to receive the entire frame before starting to packetize the frame and send it through the network. As long as the frame header format is valid (see Invalid Format Receives Frames statistic), and the DLCI field in the frame header is recognized (see Receive Frames Undefined DLCI Count statistic below), packets containing the beginning of the frame are created (one start of frame (SOF) packet and sent as soon as possible. Since the frame is very long, it is very likely that some packets are sent through the network before the length error is detected. As soon as the length error is detected, any portion of the frame that has not yet been sent is discarded. In particularly, no end-frame (EOF) packet is ever sent. When the next frame arrives, a new SOF packet arrives that does not immediately follow an EOF packet, the incomplete frame is discarded and counted in the PVC statistic of Transmit Frames Discarded. This statistic is a subset of the Frames Received statistic. |
Frame format | Occurs when either of the least significant bits in the first two bytes of the Frame Relay header are set incorrectly. These two bytes are the frame's address field. The first byte's least significant bit is defined to be a zero, meaning that there is a second byte to the address. The second byte's least significant bit is defined to be a one, meaning this is the last byte of the address because it's a two byte address field. Invalid Format Receive Frames (Ingress). Provides a count of the number of frames received from the attached equipment in which the Extended Address (EA) bits (the least significant bit in each of the two Frame Relay header octets) is incorrect. The IGXIGX must see a r0s as the least significant bit of the first octet and a r1s as the least significant bit of the second octet. Any frame received with incorrect EA bits is discarded immediately. This statistic is a subset of the Frames Received statistic. |
Unknown DLCIs | Occurs when a frame arrives at a Frame Relay port and the DLCI has not been mapped and the frame is discarded. Received Frames Undefined DLCI Count (Ingress). Provides a count of the number of frames received with a DLCI for which no PVC is provisioned on this port. This count includes any signalling protocol frames received while no signaling protocol is enabled or the wrong signalling protocol is enabled (such as by enabling the StrataLMI signaling protocol while the attached equipment is generating Annex A or Annex D signaling protocol frames, or vice versa). Any frame received with an undefined DLCI is discarded immediately. This statistic is a subset of the Frames Received statistic. |
Last unknown DLCI | Displayed so that the user can see the unknown DLCI. |
| Statistics | Description |
|---|---|
Status inquiries transmitted/received | Provides a count of the number of status enquiry frames received from the attached equipment as part of the selected signaling protocol. This statistic is valid for any UIN signaling protocol chosen (StrataLMI, ANSI Annex D, or CCITT Annex A). This statistic is a subset of the Frames Received statistic. LMI UNI Status Enquiries (Ingress). Provides a count of the number of status enquiry frames received from the attached equipment as part of the selected signaling protocol. This statistic is valid for any UNI signaling protocol chosen (StrataLMI, ANSI Annex D, or CCITT Annex A). This statistic is also valid for any NNI signaling protocol chosen (ANSI Annex D, or CCITT Annex A). This statistic is a subset of the Frames Received statistic. LMI NNI Status Enquiries (Egress). Provides a count of the number of status enquiry frames transmitted to the attached equipment as part of the selected signaling protocol. This statistic is valid for any NNI signaling protocol chosen (ANSI Annex D or CCITT Annex A). This statistic is a subset of the Frames Transmitted statistic. |
Status transmit/received | The number of Status messages sent to the user device. LMI UNI Status Transmit Count (Egress). Provides a count of the number of status frames transmitted to the attached equipment as part of the selected signaling protocol. This statistic is valid for any UNI signalling protocol. This statistic is valid for any UNI signaling protocol chosen (StrataLMI, ANSI Annex D, or CCITT Annex A). This statistic is a subset of the Frames Transmitted statistic. LMI NNI Status Transmit Count (Egress). Provides a count of the number of status frames transmitted to the attached equipment as part of the selected signaling protocol. This statistic is valid for any UNI signalling protocol. This statistic is valid for any NNI signaling protocol chosen (StrataLMI, ANSI Annex D, or CCITT Annex A). This statistic is a subset of the Frames Transmitted statistic. |
Async status Xmit | The number of asynchronous status messages sent to the user device. Provides a count of the number of asynchronous status update frames transmitted to the attached equipment as part of the selected signaling protocol. This statistic is valid for any UNI signaling protocol chosen (StrataLMI, ANSI Annex D, or CCITT Annex A). This statistic is also valid for any NNI signaling protocol chosen (ANSI Annex D, or CCITT Annex A). If enabled as part of the port configuration (cnfport command), an asynchronous status update frame is generated any time a PVC is failed or downed and again any time a PVC is repaired or upped. This statistic is a subset of the Frames Transmitted statistic. |
Invalid requests | The number of invalid requests received from the user device. LMI Invalid Status Enquiries (Ingress). Provides a count of the number of status enquiry frames with an invalid format received from the attached equipment as part of the selected signaling protocol. This statistic is valid for any UNI signaling protocol chosen (StrataLMI, ANSI Annex D, or CCITT Annex A). This statistic is also valid for any NNI signaling protocol chosen (ANSI Annex D, or CCITT Annex A). This statistic is a subset of the Frames Received statistic. |
Timeouts | The number of LMI protocol timeouts. LMI UNI Link Timeout Errors. Provides a count of the number of times that the rT392 Polling Verification Timers times out without a Status Enquiry frame having been received. This statistic is valid for any UNI signaling protocol chosen (StrataLMI, ANSI Annex D, or CCITT Annex A). The rT392 Polling Verification Timers is configured as part of the port configuration (cnfport command). LMI NNI Link Timeout Errors. Provides a count of the number of times that the rT392 Polling Verification Timers times out without a Status Enquiry frame having been received. This statistic is valid for any NNI signaling protocol chosen (StrataLMI, ANSI Annex D, or CCITT Annex A). The rT392 Polling Verification Timers is configured as part of the port configuration (cnfport command). |
Sequence number mismatches | The number of LMI protocol sequence number mismatches. LMI UNI Keepalive Sequence Errors. Provides a count of the number of times that there was a discontinuity in the (normally consecutive) sequence numbers contained the Status Enquiry frames received from the attached equipment. This statistic is valid for any UNI signalling protocol chosen (StrataLMI, ANSI Annex D, or CCITT Annex A). LMI NNI Keepalive Sequence Errors. rovides a count of the number of times that there was a discontinuity in the (normally consecutive) sequence numbers contained the Status Enquiry frames received from the attached equipment. This statistic is valid for any NNI signalling protocol chosen (StrataLMI, ANSI Annex D, or CCITT Annex A). . |
Signaling protocol | The protocol selected for this Frame Relay port interface: Cisco LMI, Annex A UNI, Annex D UNI, Annex A NNI, or Annex D NNI. |
| Miscellaneous Statistics | |
|---|---|
| Statistics | Description |
Average queue depth | The average fill of the VC queue at the input of the FRP or FRM. Transmit Frames Discarded—Queue Overflow (Egress). Provides a count of the number of frames that were discarded because the port's transmit queue (egress queue) was full. The size of the port's transmit queue is configured as part of the port configuration (cnfport) command. Transmit Bytes Discarded—Queue Overflow (Egress). Provides a count of the number of octets in the Transmit Frames Discarded—Queue Overflow statistic. The octets counted include the Frame Relay header octets as well as the frame check sequence (FCS, or CRC) octets. |
BECN frames | Number Explicit Congestion Notification frames transmitted to the receiving router. Number of Explicit Congestion Notification frames transmitted to the transmitting router. Percentage of BECN frames sent to the total number of frames sent. Frames Transmitted with BECN (Egress). Provides a count of the number of frames transmitted to the attached equipment with the Backward Explicit Congestion Notification (BECN) bit set, regardless of where in the network the congestion was observed. |
FECN frames | The percentage of FECN frames sent to the total number of frames sent. Frames Transmitted with FECN (Egress). Provides a count of the number of frames transmitted to the attached equipment with the Forward Explicit Congestion Notification (FECN) bit set, regardless of the where in the network the congestion was experienced. This statistic is a subset of the Frames Transmitted statistic. |
Rsrc overflow | Resource overflow indicates the number of times the port shut down due to receive frame buffer overflow or receive queue entries. |
DE Frames Dropped (Egress) | The total number of frames with Discard Eligibility that were discarded. Provides a count of the number of frames to be transmitted to the attached device that were discarded because the frame's DE bit is set and the port's egress buffer has reached the DE threshold. The DE threshold is configured as part of the port configuration (cnfport command). This statistic is a subset of the corresponding PVCs Transmit Frames Discarded statistic. |
The dspportstats command also displays the following statistics: IMA port summary statistics. A summary and description of these statistics follows:
| Statistics | Description |
|---|---|
IMA Unavailable Seconds |
|
IMA Near end Failed counts |
|
Last IMA protocol failure code |
|
| Statistics | Description |
|---|---|
CLLM Frames Received | Provides a count of the number of Consolidated Link Layer Management (CLLM) frames received from the attached equipment. CLLM frames are used to exchange PVC congestion information over an NNI port to allow the ForeSight algorithm to regulate the flow of traffic on each PVC based on congestion in the local network as well as congestion in the attached network. This is not intended to be a full implementation of the CLLM suite. The CLLM mechanism is enabled as part of the port configuration (cnfport command). This statistic is a subset of the Frames Received statistic. |
CLLM Bytes Received (Ingress) | Provides a count of the number of octets in the frames counted in the CLLM Frames Received statistic. The octets counted include the Frame Relay header octets as well as the frame check sequence (FCS, or CRC) octets. This statistic is a subset of the Bytes Received statistic. |
CLLM Frames Transmitted (Egress) | Provides a count of the number of Consolidated Link Layer Management (CLLM) frames transmitted to the attached equipment. CLLM frames are used to exchange PVC congestion information over an NNI port to allow the ForeSight algorithm to regulate the flow of traffic on each PVC based on congestion in the local network as well as congestion in the attached network. This is not intended to be a full implementation of the CLLM suite. The CLLM mechanism is enabled as part of the port configuration (cnfport command). This statistic is a subset of the Frames Transmitted statistic. |
CLLM Bytes Transmitted (Egress) | Provides a count of the number of Consolidated Link Layer Management (CLLM) frames transmitted to the attached equipment. CLLLM frames are used to exchange PVC congestion information over an NNI port to allow the ForeSight algorithm to regulate the flow of traffic on each PVC based on congestion in an attached network. This is not intended to be a full implementation of the CLLM suite. The CLLM mechanism is enabled as part of the port configuration (cnfport command). This statistic is a subset of the Frames Transmitted statistic. |
CLLM Failures | Provides a count of the number of times that: % no CLLM frame was received within one second (not configurable), or% a CLLM frame was received with any invalid internal format. An invalid CLLM frame that is discarded is included in the statistic of Frames Received. |
Display Frame Relay port statistics
dspportstats <slot.port> [interval]
clrportstats
| Privilege | Jobs | Log | Node | Lock |
1-6 | No | No | IPX, IGX | Yes |
dspportstats 4.1
Display the port statistics for Frame Relay port 4.1.
alpha32 LAN SuperUser IPX 32 9.2 Aug. 21 1997 12:44 PST
Port Statistics for 4.1 Cleared: Aug. 21 1997 09:45 Snapshot
Port Speed: 256 kbps Collection Time: 0 day(s) 02:56:48 Corrupted: NO
Bytes Average (kbps) Util (%) Frames
From Port: 0 0 0 0
To Port: 0 0 0 0
Frame Errors LMI Receive Protocol Stats Misc Statistics
Invalid CRC 0 Status Enq Rcvd 0 Avg Tx Port Q 0
Invalid Alignment 0 Status Xmit 0 FECN Frames 0
Invalid Frm Length 0 Asynch Xmit 0 Ratio (%) 0
Invalid Frm Format 0 Seq # Mismatches 0 BECN Frames 0
Unknown DLCIs 0 Timeouts 0 Ratio (%) 0
Last Unknown DLCI 0 Invalid Req 0 Rsrc Overflow 0
Sig Protocol: None DE Frms Dropd 0
Last Command: dspportstats 4.1
Continue to next page? (y/n)
Enter "y" to see subsequent screens.
alpha32 LAN SuperUser IPX 32 9.2 Aug. 21 1997 12:49 PST
Port Statistics for 4.1 Cleared: Aug. 21 1997 09:45
Port Speed: 256 kbps Collection Time: 0 day(s) 03:03:42 Corrupted: NO
Bytes Average (kbps) Util (%) Frames
From Port: 0 0 0 0
To Port: 0 0 0 0
LMI Receive Protocol Stats LMI Transmit Protocol Stats CLLM (ForeSight) Stats
Status Enq Rcvd 0 Status Enq Xmit -- Frames Rcvd --
Status Xmt 0 Status Rcd -- Bytes Rcvd --
Asynch Xmit 0 Asynch Rcvd -- Frames Xmt --
Seq # Mismatches 0 Seq # Mismatches -- Bytes Xmt --
Timeouts 0 Timeouts -- CLLM Failures --
Invalid Frames 0
Sig Protocol: None
This Command: dspportstats 4.1
Hit DEL key to quit:
| Parameter | Description |
|---|---|
slot | Specifies the Frame Relay card set slot. |
port | Specifies the port on the back card. The range is 1-4 for the FRI-V.35 or FRI-X.21 back cards. For channelized ports, the range is 1-24 or 1-31 for a FRI-T1 or FRI-E1, respectively, and 1-250 for a UFI back card. |
| Parameter | Description |
|---|---|
interval | Specifies the refresh interval time for data. The range is 1-60 seconds. The default interval is 1 second. |
This command displays the cache of all cost-based routing connections. The optional 'index' parameter lets you specify a cache entry index. The optional 'c' parameter clears the cache. The information displayed includes:
Display cost-based route cache
dsprtcache [index] [c]
[index] specifies the cache entry index
[c] specifies to clear the entire cache or a single entry
dspcon, cnfrtcost, cnfpref
| Privilege | Jobs | Log | Node | Lock |
1-6 | No | No | IPX, IGX, BPX | No |
dsprtcache
Display route cache contents, and let you monitor and manually clear the cache.
pissaro TN StrataCom BPX 15 9.1 Jun. 18 1997 11:11 GMT
Route Cache (Summary)
Index Use No. Cost Delay Restrict Load VPC Hops RemoteNode
0 Yes 1 Yes No None VBR No 2 lautrec
1 Yes 6 Yes No *s BDB No 3 vangogh
2 Yes 9 Yes No None BDA No 3 matisse
3 Yes 3 Yes No *t BDB No 3 rousseau
4 Yes 1 Yes No None CBR No 3 seurat
<- current
5 No 0 No No None --- No 0 ---
6 No 0 No No None --- No 0 ---
7 No 0 No No None --- No 0 ---
8 No 0 No No None --- No 0 ---
9 No 0 No No None --- No 0 ---
10 No 0 No No None --- No 0 ---
11 No 0 No No None --- No 0 ---
Last Command: dsprtcache
Next Command:
| Parameter | Description |
|---|---|
index | Specifies a particular route entry within the cache. When used with the c parameter, the route is either displayed or cleared from the cache. |
c | Clears the cache, or if you also enter the index parameter, clears the route cache specified by the index number. |
Prints the configuration details for voice channels or data channels. This command uses the same syntax, and prints the same information as is displayed using the dspchcnf command. See the dspchcnf command for syntax and output information.
Print channel configurations
prtchcnf [start_channel] (see dspchcnf description)
dspschcnf
| Privilege | Jobs | Log | Node | Lock |
1-2 | Yes | Yes | IPX, IGX | Yes |
Prints a summary of connections terminated at the IPX or IGX node. This command uses the same syntax and prints the same information as is displayed using the dspcons command. See the dspcons command for syntax and output information.
Full Name
Print connection
prtcons [start_channel] [nodename] [type] [+d]
dspcons
| Privilege | Jobs | Log | Node | Lock |
1-6 | Yes | No | IPX, IGX | Yes |
| Parameter | Description |
|---|---|
start channel | Specifies the channel to begin the display. Specify start channel in one of the following formats: slot.port.DLCI (Frame Relay channel) If no starting channel is specified, the display begins with the first connected channel. |
node name | Specifies that only connections to the remote node from the local note are displayed. If no "nodename" is designated, connections from the local node to all other nodes are displayed. |
-v | Voice only. |
-d | Data only. |
-f | Frame relay only. |
-atfr | Interworking connections. |
-g | Grouped connections. |
+d | Connection descriptor. |
-abit | Abit status. |
-fabit | Abit errors. |
-fail | Failed connections. |
-down | Downed connections. |
type | Types listed in Syntax section. The state that may be displayed for Frame Relay and NNI connection types includes: OK: Connection OK, Abit = 1. FAILED: Connection failed, Abit = 0. MISSING: DLCI was deleted in other network NNI. A previous status report indicated a valid DLCI present but an updated UNUSED: The UNI port does not support reporting of NNI Abit status. |
Prints a data channel's interface control template. The prtict command uses the same syntax and prints the same information as dspict. See the dspict description for output information.
Print interface control template
prtict <port> <template>
dspict
| Privilege | Jobs | Log | Node | Lock |
1-2 | Yes | No | IPX, IGX | Yes |
| Parameter | Description |
|---|---|
port | Specifies the physical slot and port of the Frame Relay card set. |
template | Specifies the template. Choices are a, c, n, l, and f. |
Activates a port on a Frame Relay card. The applicable cards are all versions of the FRP, FRM, and UFM series of cards. If the port has not been configured through the cnffrport command, a set of default configuration values apply.
With a Port Concentrator Shelf (PCS), upping the first port causes the FRP-2 or FRM-2 to begin communicating with the four PCS modules and to download code to them if necessary.
Up Frame Relay port
For UFM-U, FRM, or FRP: upfrport <slot.port>
For UFM-C: upfrport <slot.port> <line>
dnfrport, cnffrport
| Privilege | Jobs | Log | Node | Lock |
1-2 | Yes | Yes | IPX, IGX | Yes |
upfrport 9.2
Activate port 2 on the FRP in slot 9.
alpha TRM YourID:1 IGX 8420 9.2 Aug. 15 1997 15:51 PST
Port: 9.2 [ACTIVE ]
Interface: FRI-V35 DTE Configured Clock: 256 Kbps
Clocking: Normal Measured Rx Clock: 0 Kbps
Port ID 0
Port Queue Depth 65535 OAM Pkt Threshold 3 pkts
ECN Queue Threshold 65535 T391 Link Intg Timer 6 sec
DE Threshold 100 % N391 Full Status Poll 10 cyl
Signalling Protocol None ForeSight (CLLM) No
Asynchronous Status No CLLM Status Tx Timer 0 msec
T392 Polling Verif Timer 15 Interface Control Template
N392 Error Threshold 3 Lead State
N393 Monitored Events Count 4 RTS ON
Communicate Priority No DTR ON
Upper/Lower RNR Thresh 75%/ 25%
Min Flags / Frames 1
Last Command: upfrport 9.2
Next Command:
| Parameter | Description |
|---|---|
slot | Specifies slot number of the card containing the port. |
port | Specifies the port. The ranges are: |
line | Applies to UFM-C only. The line is the physical connector. The range is 1-8 for T1 or E1. |
Posted: Fri Nov 8 07:10:22 PST 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.