|
Data commands apply to setting up, configuring, and statistical reporting on data connections. For descriptions of the data commands on a FastPAD, refer to the FastPAD User's Guide. Examples of the tasks described in the chapter are:
To set up a data connection:
Step 1 If necessary, configure the data channel at each end of the connection. Default configuration parameters exist, so using the following commands are optional. The designation of a data channel has the format slot.port. For example, 6.3 is port 3 on the card in slot 6. The items that need configuring depend on the type of data connection. The configuration commands and their associated parameters are as follows.
| Specifies the clocking for the data channel. |
| Sets the control leads for bidirectional pins 11 and 23 on an EIA/TIA-232 data channel. The default is input. |
| Use sixth lead feature to provide test port loopback. |
| Enables optional card redundancy. This step requires extra hardware. |
| Configures an interface control template that determines output lead behavior for data channels. Output leads can be either configured as steady state (on or off) or programmed to follow an input lead. Five types of templates exist for channels in active, conditioned, looped, near, and far states. |
| Copies interface control template information from one channel to another. This step is optional. |
Step 2 Add the connection with the addcon command. The above configuration must have been completed at each end before the connection can be added.
You can configure redundant data channels by installing two identical card sets in adjacent slots and connecting the cards to the customer's line through a Y-cable.
Data channels have an associated default interface control template for each of the active (normal), conditioned, looped, near and far states. The templates define how the control leads at the data interface are to be configured (asserted, inhibited, follow a local source or follow a remote source). The interface control template can be changed by using the cnfict command. Each template and each control lead must be configured individually. The cpyict (copy interface control panel) can be used to apply (copy) the settings of a template for one data channel to those of a template for another data channel.
DFM (Data Frame Multiplexing) is a feature on the IGX nodes in which repetitive data patterns (such as IDLE codes) are suppressed at the source and regenerated at the remote node. This feature has the effect of approximately doubling the bandwidth of the data channel.
Note DFM operates on connections with maximum rate of 128 Kbps. |
The command for changing the DFM enable-status for individual data channels is cnfchdfm. Before you execute this command, make sure the DFM feature has been activated on each applicable node by Customer Service. You can check the DFM configuration for a channel by using the dspchcnf command. When the DFM feature is first activated at a node, it has the following default values:
The EIA feature encodes the status of the CTS or RTS lead as the eighth bit in each data byte. The byte subsequently is processed in accordance with the DFM algorithm, which remains unchanged.
Any DCE and DTE combination at each end is valid. A typical configuration might have the LDP at one end of a connection as DCE (normal clocking) and an LDM at the other end as DTE (looped clocking). RTS is transmitted in encoded form from the remote end to the local end, and CTS is transmitted in the other direction. Other EIA leads use the non-interleaved format.
The EIA feature is allowed for all legal baud rates 19.2 kbps and below and is activated by typing encoding type 7/8E followed by an *Z when adding a connection using the addcon command. Different channels on the same card may be set up with or without the feature, but all ports on the card must be configured at or below 19.2 Kbps for EIA to be active. Note that you do not have to enter *Z after 7/8E on the command line because the system automatically enters it.
DDS Trunks normally operate at 56 Kbps. The IGX nodes can provide a direct interface to a DDS line and provide limited distance access to Data Service Units (DSUs) by using the DDS format over private lines. The LDI4/DDS back card and LDP (Model B) or LDM front card support DDS. Each LDI/DDS supports four DDS trunks in DSU or OCU modes.
In Release 9.2, the UVM and CVM cards on the IGX support Idle Code Suppression (ICS) for video calls. You can configure the idle code suppression (ICS) feature on an Nx64 super-rate PVC connection (which uses multiple channels) to stop FastPacket generation when the connected PBX has terminated a video call. No video traffic will be generated when a video call has terminated. Use the chfdch and dspchcnf commands to enable or disable idle code suppression for the UVM and CDP/CVM cards, and to display the configuration for the cards. All back card types supported by UVM/CVM/CDP support the idle code suppression feature.
Note The UXM/CVM firmware needs to be upgraded for this feature. The CVM model B revision E and above support this feature. The UVM's Model E and above supports this feature. The dspcd screen displays "Front card supports idle code suppression." |
The UVM/CVM card firmware detects the idle (on-hook) state of a video call, which uses an nx64K data connection, and suppresses packet transmission during this idle connection. The UVM or CVM at the far end of the connection plays out the idle code during this time. You use the switch software cnfdch and dspchcnf commands to enable/disable and display this feature on a per connection basis. The primary benefit of the ICS feature is the trunk bandwidth savings during the on-hook state of an nx64 connection. This extra bandwidth can be used by other connections.
Table 7-1 shows the full name and starting page of each description.
Mnemonic | Description | Page |
---|---|---|
addcon | Add connection | |
cnfchdfm | Configure Data Frame Multiplexing (DFM) | |
cnfcheia | Configure EIA | |
cnfcldir | Configure control lead direction | |
cnfdchtp | Configure data channel interface type | |
cnfdch | Configure data connection to have ICS (Idle Code Suppression) | |
cnfdclk | Configure data clock | |
cnfict | Configure interface control template | |
cpyict | Copy interface control template | |
delcon | Delete connection | |
dspchcnf | Display channel configuration | |
dspcon | Display connection | |
dspcons | Display connections | |
dspict | Display interface control template | |
prtchcnf | Print channel configuration | |
prtcons | Print connections | |
prtict | Print interface control template |
Establishes data channel connections between nodes in a network. After you add a connection using the addcon command, the node automatically routes the connection. The node where you execute addcon is the "owner" of the added connections. The concept of ownership is important because you must enter information about automatic rerouting and preferred routing at the node that owns the connection. See the cnfpref and cnfcos commands for more information on automatic rerouting. Before the node adds the connection, the proposed connection appears on the screen with a prompt for you to confirm the addition.
When applied to data connections, the addcon command adds a synchronous data connection to the network. You can add synchronous data connections to any node slot equipped with either an LDM or HDM in an IGX node. Before you add a connection, determine the desired data rate. To find the data rates that individual cards support, refer to the card descriptions in the Cisco IGX 8400 Series Reference manual or the Cisco IGX Reference manual.
When connecting sets of data channels, you do not have to specify the full channel set for the local end of the connection. You have to designate only the first channel in the range. For example, to add connects 27.1-4 at local node alpha to channels 9.1-4 at beta, you can enter
addcon 27.1-4 beta 9.1
If Y-cable redundancy has been specified, you can add data connections at only primary card slots (not at the secondary card slots). See the addyred description for more information. Standard Data Rates tables follow, listing data rates. The following notations appear with some data rates:
| Must be used with 8/8 or 8/8I coding. |
| Specifies a partially filled packet type: the /n allows partial packets to be sent and so avoid the delay incurred by waiting to build a full packet. |
| Entered after the data rate, an f specifies fast EIA (interleaved EIA) for the connection. |
| Indicates "transparent" (CDP or CVM subrate DS0A): if you include the t-option, the IGX node does not check for supervisory or control information. |
Bit Rate (kbps) | 7/8 Coding | 8/8 Coding | ||
---|---|---|---|---|
| Pkt/Sec | Bits/Pkt | Pkt/Sec | Bits/Pkt |
1.2 | 43 | 28 | 38 | 32 |
1.8 | 65 | 28 | 57 | 32 |
2.4 | 35 | 70 | 30 | 80 |
3.2 | 46 | 70 | 40 | 80 |
3.6 | 52 | 70 | 45 | 80 |
4.8 | 35 | 140 | 30 | 160 |
6.4 | 46 | 140 | 40 | 160 |
7.2 | 52 | 140 | 45 | 160 |
8 | 58 | 140 | 50 | 160 |
9.6 | 69 | 140 | 60 | 160 |
12 | 86 | 140 | 75 | 160 |
12.8 | 92 | 140 | 80 | 160 |
14.4 | 103 | 140 | 90 | 160 |
16 | 115 | 140 | 100 | 160 |
16.8 | 120 | 140 | 105 | 160 |
19.2 | 138 | 140 | 120 | 160 |
24 | 172 | 140 | 150 | 160 |
28.8 | 206 | 140 | 180 | 160 |
32 | 229 | 140 | 200 | 160 |
38.4 | 275 | 140 | 240 | 160 |
48 | 343 | 140 | 300 | 160 |
56 | 381 | 147 | 334 | 160 |
57.6 | 392 | 147 | 360 | 160 |
54 | 436 | 147 | 381 | 168 |
72 | 490 | 147 | 429 | 168 |
76.8 | 523 | 147 | 458 | 168 |
84 | 572 | 147 | 500 | 168 |
96 | 654 | 147 | 572 | 168 |
112 | 762 | 147 | 667 | 168 |
115.2 | 784 | 147 | 686 | 168 |
128 | 871 | 147 | 762 | 168 |
144 | 980 | 147 | 858 | 168 |
168 | 1143 | 147 | 1000 | 168 |
192 | 1307 | 147 | 1143 | 168 |
224 | 1524 | 147 | 1334 | 168 |
230.4 | 1568 | 147 | 1372 | 168 |
256 | 1742 | 147 | 1524 | 168 |
288 | 1960 | 147 | 1715 | 168 |
336 | 2286 | 147 | 2000 | 168 |
384 | 2613 | 147 | 2286 | 168 |
448 | 3048 | 147 | 2667 | 168 |
512 | 3483 | 147 | 3048 | 168 |
672 | 4572 | 147 | 4000 | 168 |
768 | 5225 | 147 | 4572 | 168 |
772 | 5252 | 147 | 4596 | 168 |
896 | 6096 | 147 | 5334 | 168 |
1024 | 6966 | 147 | 6096 | 168 |
1152 | 7837 | 147 | 6858 | 168 |
1344 |
|
| 8000 | 168 |
Unshaded connections generate time-stamped data packets. Shaded connections generate non-time-stamped data packets. |
Bit Rate (kbps) | 7/8 Coding | 8/8 Coding | ||
---|---|---|---|---|
| Pkt/Sec | Bits/Pkt | Pkt/Sec | Bits/Pkt |
1.2f | 35 | 35 | 30 | 40 |
1.8f | 52 | 35 | 45 | 40 |
2.4f | 35 | 70 | 30 | 80 |
3.2f | 46 | 70 | 40 | 80 |
3.6f | 52 | 70 | 45 | 80 |
4.8f | 69 | 70 | 60 | 80 |
6.4f | 92 | 70 | 80 | 80 |
7.2f | 103 | 70 | 90 | 80 |
8f | 115 | 70 | 100 | 80 |
9.6f | 138 | 70 | 120 | 80 |
12f | 172 | 70 | 150 | 80 |
12.8f | 183 | 70 | 160 | 80 |
14.4f | 206 | 70 | 180 | 80 |
16f | 229 | 70 | 200 | 80 |
16.8f | 240 | 70 | 210 | 80 |
19.2f | 275 | 70 | 240 | 80 |
24f | 343 | 70 | 300 | 80 |
28.8f | 412 | 70 | 360 | 80 |
32f | 458 | 70 | 400 | 80 |
38.4f | 549 | 70 | 480 | 80 |
48f | 686 | 70 | 600 | 80 |
56f | 800 | 70 | 700 | 80 |
57.6f | 823 | 70 | 720 | 80 |
54f | 915 | 70 | 800 | 80 |
72f | 1029 | 70 | 900 | 80 |
76.8f | 1098 | 70 | 960 | 80 |
84f | 1200 | 70 | 1050 | 80 |
96f | 1372 | 70 | 1200 | 80 |
112f | 1600 | 70 | 1400 | 80 |
115.2f | 1646 | 70 | 1440 | 80 |
128f | 1829 | 70 | 1600 | 80 |
144f | 2058 | 70 | 1800 | 80 |
168f | 2400 | 70 | 2100 | 80 |
192f | 2743 | 70 | 2400 | 80 |
224f | 3200 | 70 | 2800 | 80 |
230.4f | 3292 | 70 | 2880 | 80 |
256f | 3658 | 70 | 3200 | 80 |
288f | 4115 | 70 | 3600 | 80 |
336f | 4800 | 70 | 4200 | 80 |
384f | 5486 | 70 | 4800 | 80 |
448f | 6400 | 70 | 5600 | 80 |
512f | 7315 | 70 | 6400 | 80 |
1.2f | 35 | 35 | 30 | 40 |
1.8f | 52 | 35 | 45 | 40 |
2.4f | 35 | 70 | 30 | 80 |
3.2f | 46 | 70 | 40 | 80 |
3.6f | 52 | 70 | 45 | 80 |
4.8f | 69 | 70 | 60 | 80 |
6.4f | 92 | 70 | 80 | 80 |
Connections above the line generate time-stamped data packets. Shaded connections generate non-time-stamped data packets. DFM is not available on interleaved EIA connections.
|
Bit Rate (kbps) | 7/8 Coding | 8/8 Coding | ||
| Pkt/Sec | Bits/Pkt | Pkt/Sec | Bits/Pkt |
2.4/4 | 86 | 28 | 75 | 32 |
3.2/4 | 115 | 28 | 100 | 32 |
Bit Rate (kbps) | 7/8 Coding | 8/8 Coding | ||
| Pkt/Sec | Bits/Pkt | Pkt/Sec | Bits/Pkt |
3.6/4 | 129 | 28 | 113 | 32 |
4.8/10 | 69 | 70 | 60 | 80 |
4.8/4 | 172 | 28 | 150 | 32 |
6.4/10 | 92 | 70 | 80 | 80 |
6.4/4 | 229 | 28 | 200 | 32 |
7.2/10 | 103 | 70 | 90 | 80 |
7.2/4 | 258 | 28 | 225 | 32 |
8/10 | 115 | 70 | 100 | 80 |
9.6/10 | 138 | 70 | 120 | 80 |
12/10 | 172 | 70 | 150 | 80 |
12.8/10 | 183 | 70 | 160 | 80 |
14.4/10 | 206 | 70 | 180 | 80 |
All of the above connections generate time-stamped data packets. |
Bit Rate (kbps) | 7/8 Coding | 8/8 Coding | ||
---|---|---|---|---|
| Pkt/Sec | Bits/Pkt | Pkt/Sec | Bits/Pkt |
1.2 | 58 | 21 | 24 | 3 |
1.8 | 86 | 21 | 24 | 3 |
2.4 | 39 | 63 | 72 | 9 |
3.2 | 51 | 63 | 72 | 9 |
3.6 | 58 | 63 | 72 | 9 |
4.8 | 37 | 133 | 152 | 19 |
6.4 | 49 | 133 | 152 | 19 |
7.2 | 55 | 133 | 152 | 19 |
8 | 61 | 133 | 152 | 19 |
9.6 | 73 | 133 | 152 | 19 |
12 | 91 | 133 | 152 | 19 |
12.8 | 97 | 133 | 152 | 19 |
14.4 | 109 | 133 | 152 | 19 |
16 | 121 | 133 | 152 | 19 |
16.8 | 127 | 133 | 152 | 19 |
19.2 | 145 | 133 | 152 | 19 |
24 | 181 | 133 | 152 | 19 |
28.8 | 217 | 133 | 152 | 19 |
32 | 241 | 133 | 152 | 19 |
38.4 | 289 | 133 | 152 | 19 |
48 | 361 | 133 | 152 | 19 |
56 | 422 | 133 | 152 | 19 |
57.6 | 434 | 133 | 152 | 19 |
64 | 482 | 133 | 152 | 19 |
72 | 542 | 133 | 152 | 19 |
76.8 | 578 | 133 | 152 | 19 |
84 | 632 | 133 | 152 | 19 |
96 | 722 | 133 | 152 | 19 |
112 | 843 | 133 | 152 | 19 |
115.2 | 867 | 133 | 152 | 19 |
128 | 963 | 133 | 152 | 19 |
All of the above connections generate time-stamped data packets. |
Bit Rate (kbps) | 7/8 Coding | 8/8 Coding | ||
| Pkt/Sec | Bits/Pkt | Pkt/Sec | Bits/Pkt |
2.4/4 | 115 | 21 | 100 | 24 |
3.2/4 | 153 | 21 | 134 | 24 |
3.6/4 | 172 | 21 | 150 | 24 |
4.8/10 | 77 | 63 | 67 | 72 |
4.8/4 | 229 | 21 | 200 | 24 |
6.4/10 | 102 | 63 | 89 | 72 |
6.4/4 | 305 | 21 | 267 | 24 |
7.2/10 | 115 | 63 | 100 | 72 |
7.2/4 | 343 | 21 | 300 | 24 |
8/10 | 127 | 63 | 112 | 72 |
9.6/10 | 153 | 63 | 134 | 72 |
12/10 | 191 | 63 | 167 | 72 |
12.8/10 | 204 | 63 | 178 | 72 |
14.4/10 | 229 | 63 | 200 | 72 |
All of the above connections generate time-stamped data packets.
|
Bit Rate (kbps) | 7/8 Coding | 8/8 Coding | ||
| Pkt/Sec | Bits/Pkt | Pkt/Sec | Bits/Pkt |
1.2f/2 | 86 | 14 | 75 | 16 |
1.8f/2 | 129 | 14 | 113 | 16 |
2.4f/5 | 69 | 35 | 60 | 40 |
2.4f/2 | 172 | 14 | 150 | 16 |
3.2f/5 | 92 | 35 | 80 | 40 |
3.2f/2 | 229 | 14 | 200 | 16 |
3.6f/5 | 103 | 35 | 90 | 40 |
3.6f/2 | 258 | 14 | 225 | 16 |
4.8f/5 | 138 | 35 | 120 | 40 |
6.4f/5 | 183 | 35 | 160 | 40 |
7.2f/5 | 206 | 35 | 180 | 40 |
All of the above connections generate time-stamped data packets. DFM is not available on interleaved EIA connections. |
Bit Rate (kbps) | 7/8 Coding | 8/8 Coding | ||
| Pkt/Sec | Bits/Pkt | Pkt/Sec | Bits/Pkt |
2.4t |
|
| 35 | 80 |
4.8t |
|
| 35 | 160 |
9.6t |
|
| 70 | 160 |
56t |
|
| 381 | 168 |
t |
|
| 381 | 168 |
All sub-rate data connections use 8/8 coding. Unshaded connections generate time-stamped data packets. Shaded connections generate non-time-stamped data packets. DFM is not available on sub-rate connections. Interleaved EIA is not available on sub-rate connections. |
Bit Rate (kbps) | 7/8 Coding | 8/8 Coding | ||
| Pkt/Sec | Bits/Pkt | Pkt/Sec | Bits/Pkt |
2.4/4t |
|
| 88 | 32 |
4.8/10t |
|
| 70 | 80 |
4.8/4t |
|
| 175 | 32 |
9.6/10t |
|
| 140 | 80 |
All sub-rate data connections use 8/8 coding. All of the above connections generate time-stamped data packets. DFM is not available on sub-rate connections. Interleaved EIA is not available on sub-rate connections. |
Bit Rate (kbps) | 7/8 Coding | 8/8 Coding | ||
| Pkt/Sec | Bits/Pkt | Pkt/Sec | Bits/Pkt |
1x56 | 381 | 147 | 334 | 168 |
2x56 | 762 | 147 | 667 | 168 |
3x56 | 1143 | 147 | 1000 | 168 |
4x56 | 1524 | 147 | 1334 | 168 |
5x56 | 1905 | 147 | 1667 | 168 |
6x56 | 2286 | 147 | 2000 | 168 |
7x56 | 2667 | 147 | 2334 | 168 |
8x56 | 3048 | 147 | 2667 | 168 |
1x64 | 436 | 147 | 381 | 168 |
2x64 | 871 | 147 | 871 | 168 |
3x64 | 1307 | 147 | 1307 | 168 |
4x64 | 1742 | 147 | 1143 | 168 |
5x64 | 2177 | 147 | 1524 | 168 |
6x64 | 2613 | 147 | 1905 | 168 |
7x64 | 3048 | 147 | 2286 | 168 |
8x64 | 2483 | 147 | 2667 | 168 |
All of the above connections generate non-time-stamped data packets. DFM is not available on interleaved EIA connections.
|
In fast EIA signalling mode, an interleaved byte of EIA signalling information is associated with every byte of data in a packet. This format is appropriate for applications where EIA lead transitions must closely synchronize with user data. Fast EIA can apply to data rates up to 512 Kbps.
When FastPackets are built using the 7/8 coding format, each octet in the FastPacket payload consists of seven user data bits followed by a 1. This "bit-stuffing" allows these FastPackets to be safely carried on trunks which enforce ones density requirements by ensuring that each octet contain at least one 1 (such as IGX trunks configured for ZCS or AMI encoding). The user data may have any format and may contain any pattern, including all 0s. The single 1 inserted in the final bit position of each octet ensures that no more than seven consecutive 0s occur in a FastPacket. The 7/8 coding format is the safest mode to use when the data protocol is unknown and certain trunks in the network use ZCS or AMI.
When FastPackets are built using the 8/8 coding format, each octet in the FastPacket payload consists of eight user data bits. The 8/8 coding format is more efficient than the 7/8 format. However, the ones density requirement on trunks must be met by one of the following:
The vast majority of trunks today use intelligent ones density enforcement schemes, such as B8ZS, HDB3, B3ZS, or CMI. All such trunks can safely carry 8/8 data connections with no risk of data corruption. Data connections can be configured to NOT use ZCS trunks by specifying the optional "*Z" routing restriction.
When FastPackets are built using the 8/8I coding format, each octet in the FastPacket payload consists of eight inverted user data bits, i.e., each 0 is changed to a 1 and each 1 is changed to a 0. The bits are re-inverted at the far end of the connection. For such connections, the ones' density requirement on trunks must be met by one of the following:
As with the 8/8 coding format, 8/8I connections can be safely carried on the vast majority of trunks today. However, the 8/8I format is primarily intended to provide the efficiency of 8/8 coding for any data which is HDLC or SDLC-based. HDLC/SDLC can never send more than six consecutive 1s, which, when inverted, automatically meets the ones density requirements of every possible trunk format.
If the data protocol requires an acknowledgment and is delay-sensitive, avoid routing the connection over a satellite line (*s for avoid). If 8/8 or 8/8I coding is the selected format, avoid trunks with zero code suppression (*z for avoid) because the zero code suppression could corrupt the last bit in the byte.
Add a connection
addcon <local channel> <remote node> <remote channel> <type> <coding> [avoid]
delcon, dncon, dspcon, dspcons, upcon
Privilege | Jobs | Log | Node | Lock |
1-2 | Yes | No | IGX | Yes |
addcon 6.1 pubsigx2 11.1 56
Add a low speed data connection of 56 Kbps at 6.1. The connections are highlighted on the screen. A prompt appears asking you to confirm these connections. Respond "y" for yes to add the connection. The connections screen then appears showing that data channel 11.1 on node pubsigx2 is connected to channel 6.1 on node pubsigx1. The 56 under the type category indicates that the data rate for the channel is 56 Kbps.
pubsigx1 TN SuperUser IGX 8420 9.2 July 25 1998 06:23 PDT
From Remote Remote
6.1 NodeName Channel State Type Compress Code COS
6.1 pubsigx2 11.1 Ok 56 7/8 0
Last Command: addcon 6.1 pubsigx2 11.1 56
Next Command:
addcon 5.1 beta 6.1-4 4x64
For a CDP super-rate connection, add a 256 Kbps (4x64) connection from an SDP at node alpha to the CDP at node beta. Data rates come from the Standard Data Rate Connections in the preceding pages. The elements on the command line consist of the following:
addcon slot.port remote nodename slot.start channel at far-end channel rate
addcon 5.4-7 beta 6.1-4 4x64
For CDP to CDP or CVM to CVM, add a 256 Kbps (4x64) data connection from a CDP (or CVM) at node alpha to the CDP (or CVM) at node beta. The syntax for this example requires that the start and end channel are entered for both ends of the connection and that the data rate is specified to be the same at both ends. The channel numbers can be different on each end if they are contiguous.
addcon | slot.start channel -end channel | remote nodename |
| slot.start channel -end channel | rate |
Parameter | Description |
---|---|
local channel | Specifies the local channel or set of channels in the format slot.port [-port]. (The brackets indicate you can specify a range of channels.) |
remote node | Specifies the name of the node at the other end of the connection. For a DACS-type connection (where a channel on a node connects to a channel on the same node), use the local node name for remote node. |
remote channel | Specifies the remote channel or set of channels in the format slot.port [-port]. (The brackets indicate you can specify a range of channels.) |
type | Specifies the data connection bit rate, EIA control lead mode, and in some cases, the number of data bytes in a data packet. Refer to the Standard Data Connection rates for allowable bit rates. |
coding | Specifies the data coding format for data transmissions. Valid formats are:
|
Parameter | Description |
---|---|
avoid | Specifies the type of trunk for the connection to avoid. The default is no avoidance. The choices are:
|
Enables or disables Data Frame Multiplexing (DFM) for individual channels and sets the DFM parameters for the channels. The default state when the DFM feature is activated on a card is enabled. Because DFM is a purchased option, the Cisco Technical Assistance Center (TAC) must activate on the applicable nodes before you use the cnfchdfm command.
The DFM feature must be both installed and enabled. The DFM feature must be installed through software control at each node terminating the connection. If DFM is not installed for a pertinent node in the network, the cnfchdfm command has no effect at that node. Furthermore, you must use cnfchdfm at both ends of the connection to enable DFM.
Configure channel DFM
cnfchdfm <channel(s)> <7 | 8 | 16> [e | d]
dspchcnf
Privilege | Jobs | Log | Node | Lock |
1-2 | Yes | Yes | IGX | Yes |
cnfchdfm 5.1 8
Set the DFM pattern length to 8 bits for data channel 5.1.
alpha TRM YourID:1 IGX 8420 9.2 Aug. 15 1998 16:21 PST
Maximum EIA % DFM Pattern DFM
Channels Update Rate Util Length Status
5.1 15 100 8 Enabled
5.2-4 2 100 8 Enabled
Last Command: cnfchdfm 5.1 8
Next Command:
Parameter | Description |
---|---|
channel | Specifies the channel or range of channels. |
7/8/16 | Specifies the pattern length in bits for the DFM algorithm. The default is 8 bits |
Parameter | Description |
---|---|
e/d | Enables or disables DFM. The default is "e." Note that DFM works at rates no higher than 128 Kbps. |
Sets the sampling rate for the updating EIA control leads. You can set this rate from 0 (no sampling) to packet-generation rate for the EIA leads associated with the channel.
At 20 updates/second, the control leads are polled for changes every 50 msec. Therefore, changes occurring more rapidly than that may not be detected. If there is no change in EIA lead status, no packet is sent. A minimum of one update per second is sent if the maximum update rate chosen is from 1 to 20. If the connection is configured in such a way that an implied isochronous clock is detected, the update rate is always 20 per second in the same direction as that of the clock signal. For 1.544 Mbps data connections, this defaults to 0. This does not affect EIA sampling rates of fast EIA or embedded EIA leads.
Configure EIA update rate for channels
cnfcheia <channel(s)> <update_rate>
dspchcnf
Privilege | Jobs | Log | Node | Lock |
1-2 | Yes | Yes | IGX | Yes |
cnfcheia 5.1 15
Set the EIA update rate to 15 sec. for data channel 5.1.
alpha TRM YourID:1 IGX 8420 9.2 Aug. 15 1998 16:20 PST
Maximum EIA % DFM Pattern DFM
Channels Update Rate Util Length Status
5.1 15 100 8 Enabled
Last Command: cnfcheia 5.1 15
Next Command:
Parameter | Description |
---|---|
channel | Specifies the channel or range of channels over which to configure the EIA update rate. |
update rate | Specifies the maximum EIA update rate in updates per second. |
Sets the control lead direction for pins 11 and 23 on the EIA/TIA-232 data channels of an SDP or HDM card set. This allows the control leads to carry "backward" channels. Pins 11 and 23 on an EIA/TIA-232 interface are bidirectional. The signals on these pins can have various names, such as SI, SF, CH, CI, and QM. To display control lead information about pins 11 and 23, use the dspbob command. Use the cnfict command to configure the behavior of all output leads.
Configure control lead direction
cnfcldir <channel> <lead> <direction>
cnfict, dspbob, dspict
Privilege | Jobs | Log | Node | Lock |
1-2 | Yes | Yes | IGX | Yes |
cnfcldir 3.1 11 input
Configure lead number 11 of channel 3.1 to be an input. The screen example shows the display after the system has accepted the input as valid.
pubsigx1 TN SuperUser IGX 8420 9.2 Aug. 14 1998 00:30 GMT
Port: 3.1
Interface: V35 DCE
Clocking: Normal
Inputs from User Equipment Outputs to User Equipment
Lead Pin Lead Pin Lead Pin Lead Pin
RTS C CTS D
DTR H DSR E
TxD P/S DCD F
TT U/W RI J
TM K
RxD R/T
RxC V/X
TxC Y/a
Last Command: cnfcldir 3.1 11 input
Next Command:
Parameter | Description |
---|---|
channel | Specifies the EIA/TIA-232 data channel whose control lead direction to configure. |
pin number | Specifies the pin number of the control lead. The valid pin numbers are 11 and 23. |
direction | Specifies the direction of the control lead signal. Valid control lead directions are Input = The control lead acts as an input to the IGX node. This is the default. |
The cnfdch command lets you configure a super-rate data connection that has idle code suppression (ICS) enabled or disabled, before you add a connection. The ICS information in the cnfdch screen is identical to that of dspchcnf.
The idle code suppression feature provides a way to stop FastPacket generation on an Nx64 super-rate PVC connection when the connected PBX has terminated a video call and there are no video calls in progress. Traffic on the data network is therefore reduced. Bursty data can then use this unused bandwidth.
The idle code suppression feature enables the UVM and CVM to detect the on-hook condition of video conferencing calls. During the on-hook phase, FastPacket generation ceases, resulting in more trunk bandwidth becoming available. All connections that use ForeSight can use this bandwidth, resulting in higher information rate.
The cnfdch command is blocked if one or more specified channels is carrying a voice connection (including t-type).
If some of the specified channels do not yet have any connection attached, those channels will be initialized to a data type channel.
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 a level 2 access command, which lets you configure a super-rate data connection that has idle code suppression (ICS) enabled or disabled.
The cnfdchl command lets you configure a channel before you add a connection. The configuration remains the same when connections are removed and added again. This configuration will be removed when the associated line is deactivated.
The Idle Code Suppression feature supported in Release 9.2 provides a way to stop FastPacket 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.
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 bandwidth.
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 the cnfdch command to configure a channel before you add a connection. The configuration will stay the same even if connections are removed and added again.
Because there are multiple channels involved in an Nx64 data connection, the idle code suppression configuration of the first channel in the Nx64 bundle will be used for the entire connection.
Configuration must be done for each endpoint of a connection. When the state of an ICS connection changes, no network message is sent to the other end. You can choose to configure the other end if ICS is supported on the other end also. To maximize the benefit of the idle code suppression feature, you should enable ICS on both endpoints of the connection.
To interwork with HDM/LDM/SDP/LDP cards, idle code suppression on UVM/CVM/CDP channel will be turned off for any super-rate connection that also terminates on HDM/LDM/SDP/LDP.
All super-rate data connections will have their ICS state set to "disabled" state unless they have been specifically configured with the cnfdch command to be enabled, or through Cisco WAN Manager (or another SNMP manager application).
When a video call terminates, the PBX generates the appropriate line idle code (for example, 0x7f for mu-law). Per ITU H.221 video coding scheme, no byte will be repeated on one DS0 for more than
80 times. In the case of BONDING protocol, the maximum is 256 (32 msec). The firmware can distinguish a video call and an idle channel carrying idle code. Idle code suppression is not programmable. Any byte that repeats for more than 32 msec in all DS0s in a super-rate connection will be suppressed.
Switch software determines idle code suppression capability on a card based on firmware model and revision number (for example, it considers that the CVM card supports idle code suppression starting with model B revision E firmware).
The idle code suppression feature for the UVM and CVM cards on the IGX detects the idle (on-hook) state of a video call, which uses an Nx64K data connection, and suppresses packet transmission during this idle condition. The UVM or CVM at the far end plays out the idle code during this time. You disable or enable and display the status of idle code suppression on a per-connection basis through the switch software CLI cnfdch and dspchcnf commands.
The UVM and CVM card firmware identifies an on-hook or idle condition by detecting repetition of idle codes. These codes can be present in the regular video traffic also (that is, in H.221 or BONDING frames). The code must repeat a certain number of times before it can be concluded that the call is on-hook. It is not necessary to look for specific idle codes. Any byte-code repeating beyond the threshold (about 32 ms) indicates idle channels. The firmware monitors byte repetition on each Nx64 connection for which this feature is enabled. On detecting repetition beyond the specified threshold, FastPacket generation for such a connection would cease. This results in the remote side of the connection to under-run. In this condition, it would transmit the previously transmitted byte on each DS0 for the connection. The UVM/CVM continues to monitor DS0s for the connection to detect a change in data received. Any change would indicate an off-hook condition, after which FastPacket transmission would resume.
The idle code suppression feature consists of IGX switch software Release 9.2, and requires UVM model E firmware and CVM/CDP model B revision E firmware. The new UVM/CVM/CDP firmware ensures that idle code suppression can interoperate with UVM/CVM/CDP cards that do not have idle code suppression capability. Such a configuration means that FastPacket generation stops in one direction while the other end continues to generate FastPackets. This behaves exactly the same as enabling idle code suppression on one side but not on the other side.
All back card types supported by UVM/CVM/CDP support idle code suppression.
The standard configuration involves UVM/CVM/CDP cards on both ends of the video connections. An Nx64 super-rate PVC is set up between the two cards. Each video codec is connected through a PBX, which is attached to the UVM/CVM/CDP cards.
The idle code suppression feature is available on IGX. When idle code suppression is disabled on a connection (the default), switch software behaves the same as in releases previous to Release 9.2.
UVM/CVM/CDP cards that support idle code suppression can interwork with HDM/LDM/SDP/LDP cards. If the UVM/CVM/CDP channels are configured with idle code suppression enabled, the actual channel will not have idle code suppression enabled if the other end of the connection is not a UVM/CVM/CDP (that is, HDM/LDM/SDP/LDP).
All connection limitations that exist in Release 9.1 remain the same. A t-type connection is not supported. On a VNS controlled network, t-type SVCs are used for video calls. VNS does not support Nx64 super-rate connections.
The idle code suppression feature provides a way to stop FastPacket 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. Current UVM/CVM/CDP implementation restricts N to between 1 and 8. This feature is intended to work with video codecs that implement H.221 or BONDING protocol only.
The basic idea is that when a video call terminates, the PBX will generate the appropriate line idle code (for example, 0x7f for mu-law). Per the ITU H.221 video coding scheme, no byte will be repeated on one DS0 for more than 80 times. In the case of BONDING protocol, the maximum is 256 (32 msec). The firmware can distinguish a video call and an idle channel carrying idle code. It is important to understand that the idle code is not programmable. It is a more general approach where any byte that repeats for more than 32 msec in all DS0s in a super-rate connection will be suppressed.
Switch software's job is mainly one of providing interfaces for configuring of channels by enabling/disabling idle code suppression for super-rate data connections. In turn, switch software informs the UVM/CVM/CDP card if idle code suppression should be used on each of the super-rate connections.
No new hardware is needed. All back card types supported by UVM/CVM/CDP support the idle code suppression feature.
The SNMP agent interface on the IGX provides the following operations: Get/Set of MIB information of the desired state of idle code suppression (enabled/disabled).
If a request fails, a General Error is returned to Cisco WAN Manager. An error string is logged in the switch software error table. Cisco WAN Manager can then optionally obtain the error string from switch software. Examples of error messages are "Card in slot does not support Idle Code Suppression" and "E1 CAS and Voice Channels - Not Configured".
Given an active non-Y-redundant UVM/CVM/CDP card without ICS support, upgrades to a card with ICS are allowed. However, you cannot downgrade a card with ICS capability to a card that does not support ICS (see Table 7-17).
Given a pair of cards in a Y-redundancy configuration, whether any of them is active or not, they must have the same ICS capability (see Table 7-18).
ICS Support | Comment | |
---|---|---|
Old Card | New Card | |
NO | NO | OK - same card |
NO | YES | OK |
YES | NO | mismatch |
YES | YES | OK - same card |
ICS Support | Comment | |
---|---|---|
Old Card | New Card | |
NO | NO | OK |
NO | YES | OK but ICS is not available until both cards support ICS |
YES | NO | Mismatch if both cards support ICS before |
YES | YES | OK |
To ensure that cards with the same ICS capability be allowed to be a Y-redundancy pair, addyred blocks cards that have different idle code suppression capability.
ICS Support | Comment | |
---|---|---|
Primary Card | Secondary Card | |
NO | NO | OK |
NO | YES | addyred blocked |
YES | NO | addyred blocked |
YES | YES | OK |
Given an active non-Y-redundant UVM/CVM/CDP card without idle code suppression support, an upgrade to a card with ICS support is allowed. Downgrading a card with ICS capability to a card without ICS capability is not allowed.
Upgrading the ICS feature to a Y-redundancy pair that does not support the ICS feature is not allowed. The Y-redundancy pair must be deleted first to upgrade the feature. After both cards complete the ICS upgrade, the cards can be added as a Y-redundancy pair.
ICS Support | Comment | |
---|---|---|
Old Card | New Card | |
NO | NO | OK - same card |
NO | YES | mismatch |
YES | NO | mismatch |
YES | YES | OK - same card |
ICS Support | Comment | |
---|---|---|
Old Card | New Card | |
NO | NO | OK |
NO | YES | OK but ICS is not available until both cards support ICS |
YES | NO | Mismatch if both cards support ICS before |
YES | YES | OK |
T-type connections are not supported. On a VNS controlled network, t-type SVCs are used for video calls. VNS does not support Nx64 super-rate connections.
This feature is intended to work with video codecs that implement H.222 or BONDING protocol only.
Configures a voice connection to have idle code suppression enabled/disabled
cnfdch <channel><ch_ics_state>
dspchcnf, dspcons
Privilege | Jobs | Log | Node | Lock |
2-6 | Yes | No | IGX | No |
cnfdch 9.1.35
Display configuration values for channels 9.1.3 through 9.1.5.
sw176 TRM StrataCom IGX 8420 9.2.0r 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
Parameter | Description |
---|---|
channel | slot.line.channel for UVM or line.channel for CVM/CDP. A channel range is allowed. |
ch_ics_state | Channel idle code suppression state: d for disabled; e for enabled. |
Configures a voice connection to have idle code suppression enabled/disabled
cnfdch <channel><ch_ics_state>
cnfdch 9.1.3-5
Configures a CDP, CVM, or LDP or LDM DDS port interface type to OCU or DSU. When configuring DDS operations, this command returns an error if executed on a slot with an EIA/TIA-232 back card. It forces a back card slot from EIA/TIA-232 mode to DDS mode if a back card is not installed and there are no connections. Any Y-cable association is deleted in this case. The clocking tracks the DDS port interface type. OCU type interfaces are configured as looped, and DSU type interfaces are configured as normal. The default interface is DSU.
When configuring CDP, CVM, LDP, or LDM operation, this command configures DCE types as normal clocking and DTE types as looped clocking. The default type is DCE. For T1 lines, DS0A on T1 unassigned signalling is configurable. When a connection is not present, voice channels are converted to data channels.
Configure data channel interface type
cnfdchtp <channel> <interface type> [unassigned signaling]
none
Privilege | Jobs | Log | Node | Lock |
1-2 | Yes | Yes | IGX | Yes |
cnfdchtp 31.1 oc
Configure DDS channel 31.1 as OCU.
beta TRM YourID:1 IGX 8430 9.2 Aug. 15 1998 17:30 MST
Data Channel: 31.1
Interface: DDS-4 OCU Config
Clocking: Looped
Interface Control Template for Connection while ACTIVE
Lead Output Value Lead Output Value
DSR ON CTS ON
DCD ON
Last Command: cnfdchtp 31.1 oc
Next Command:
cnfdchtp 22.1 dce
Configure channel 22.1 as DCE with T1 unassigned signalling.
beta TRM YourID:1 IGX 32 9.2 Aug. 15 1998 17:30 MST
Data Channel: 22.1
Interface: Missing DDS0A DCE Configuration
Clocking: Normal
Interface Control Template for Connection while ACTIVE
Lead Output Value Lead Output Value
DSR ON CTS ON
DCD ON
Last Command: cnfdchtp 22.1 dce t
Next Command:
Parameter | Description |
---|---|
channel | Specifies the channel to configure in the format <slot>. <port>. |
interface type | Specifies the interface type to configure. An LDP or LDM DDS port can be configured as DSU or OCU (enter ds or oc). A CDP or CVM port can be configured as DCE or DTE (enter dce or dte). |
Parameter | Description |
---|---|
channel | Specifies the channel to configure in the format slot. port |
unassigned signalling | Specifies an optional parameter for T1 lines to indicate DS0A or T1 unassigned signalling. Enter d for DS0A or t for T1. |
Configures the clocking for a data channel. In general, the clock configuration may be normal, split, or looped for an SDP or HDM (fewer options for an LDP or LDM). The clock configuration of each channel of a connection determines how the clock will be propagated through the network, and how external equipment should be synchronized.
If clocking is not set correctly, there may be no synchronization, and the connection will operate in a plesiochronous mode. Each data port can be configured independently to act as either DCE or DTE by adjusting the jumper (SDI card) or changing the adapter cable (LDI card) on the data interface card. The effect of the clocking type designated depends on whether each data port is configured as DTE or DCE. The following data clocking configurations are possible with the cnfdclk command:
When the data port is configured as DCE, selecting a clocking type of n (for normal) results in clocking as illustrated below. The IGX node, acting as DCE, provides both the transmit and receive data clocks to the user equipment.
When the data port is configured as DCE, selecting a clocking type of s (for split) results in clocking as illustrated below. In split clocking, TT may be generated independently of RxC. The maximum data rate for split clocking is 112 Kbps.
When the data port is configured as DCE, selecting a clocking type of l (for looped) results in clocking as illustrated below. The Terminal Timing signal, called TT or XTC, is simply RxC looped back from the user equipment. In this configuration, it is important that the two clocks (RxC and TT) be frequency locked. This clocking configuration is supported for all data rates.
When the data port is configured as DTE, selecting a clocking type of n (for normal) results in clocking as illustrated below. The IGX, acting as DTE, receives both the transmit and receive data clocks from the user equipment. When the user equipment is not referenced to the network clock, the maximum data rate for this configuration is 112 Kbps. The two clocks must be frequency-locked for proper operation.
When the data port is configured as DTE, selecting a clocking type of s (for split) results in the clocking as illustrated below. When the user equipment is not referenced to the network clock, the maximum data rate for this configuration is 112 Kbps. The two clocks must be frequency-locked for proper operation.
If you specify clocking type of l (looped) when the data port is in DTE mode, the result is the clocking arrangement shown in Figure 7-6 . The RxC clock signal is the TT(XTC) signal looped back to the IGX node by the user equipment. The network supports this clocking configuration for all data rates. The restrictions to the data clocking schemes are
Configure data channel clocking type
cnfdclk <channel> <normal/split/looped>
none
Privilege | Jobs | Log | Node | Lock |
1-2 | Yes | Yes | IGX | Yes |
cnfdclk 5.1 n
Configure the clocking for channel 5.1 to normal.
alpha TRM YourID:1 IGX 8420 9.2 Aug. 23 1998 10:41 PST
Data Channel: 5.1
Interface: V35 DCE
Clocking: Normal
Interface Control Template for Connection while ACTIVE
Lead Output Value Lead Output Value
RI(J) OFF DSR (E) ON
CTS(D) ON TN (K) OFF
DCD(F) ON
Last Command: cnfdclk 5.1 n
Next Command:
Parameter | Description |
---|---|
channel | Specifies the channel to configure in the format <slot>. <port>. |
normal/split/looped | Specifies the clocking type to assign to the channel. Valid clocking types are:
|
Sets the interface control template signals. The signals that can be set using cnfict depend on the type of back card used and whether the hardware is configured for DCE or DTE. On an IGX node, the applicable front cards are the LDM, HDM, FRM, CVM (for data), and FTM (for data). Each data channel has a default interface control template for its active, conditioned, and looped near and far states. The cnfict command is used to change a control template. Each interface control lead in each template is individually configured.
When Y-cable redundancy is in effect, the control template configuration for the data channels terminating at the primary slot is also applied to the data channels of the secondary slot. Any configuration information for the secondary slot is ignored. Table 7-26 shows the configurable leads and the equivalence between EIA/TIA-232C, EIA/TIA-232D, EIA/TIA-449, V.35, and X.21 interfaces. The 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 specifying input or output leads on the command line. A node treats leads impartially for non-interleaved connections. Any signal received on an EIA pin at one end may be transmitted to any pin at the other end, up to the maximum of 12 EIA leads on any interface type. For interleaved EIA connections, refer to the Fast EIA column. The column shows which leads are carried in the interleaved bytes of the data packets. All remaining leads are carried in standard control lead packets.
Configurable Leads | ||||||||
---|---|---|---|---|---|---|---|---|
Source | IGX Name | EIA/TIA- 232C | EIA/TIA- 232D | EIA/TIA- 449 | V.35 | X.21 | Fast EIA | Function |
DTE | RTS | CA | CA | RS | C |
| F4 | Request to Send |
DCE | CTS | CB | CB | CS | D |
| F4 | Clear to Send |
DCE | DSR | CC | CC | DM | E |
| F3 | Data Set Ready |
DCE | DCD | CF | CF | RR | F |
| F7 | Data Carrier Detect (RLSD) |
DCE | QM | QM | QM |
|
|
|
| Equalizer Mode |
DTE | pin 11 | 11 | 11 |
|
|
|
| Sometimes used for Data |
DCE | SDCD | SCF | SCF |
|
|
|
| Secondary Data Carrier Detect |
DCE | SCTS | SCB | SCB |
|
|
|
| Secondary Clear to Send |
DTE | STxD | SBA | SBA |
|
|
| F5 | Secondary Transmit Data |
DTE | NS |
|
| NS |
|
| F7 | New Sync |
DCE | SRxD | SBB | SBB |
|
|
| F5 | Secondary Receive Data |
DCE | DCR | DCR |
|
|
|
|
| Divided Receiver Clock |
DTE | RL |
| RL | RL |
|
| F6 | Remote Loopback |
DTE | SRTS | SCA | SCA |
|
|
|
| Secondary Request to Send |
DTE | DTR | CD | CD | TR | H |
| F3 | Data Terminal Ready |
DCE | SQ | CG | CG | SQ |
|
|
| Signal Quality Detect |
DCE | RI | CE | CE | IC | J** |
|
| Ring Indicator |
DTE | SF | CH | CH | SF |
|
|
| Signal Rate Select (to DCE) |
DCE | SI | CI | CI | SI |
|
|
| Signaling 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 | K1 |
| F6 | Test Mode |
DTE | SS |
|
| SS |
|
|
| Select Standby |
DTE | C |
|
|
|
| C |
| Control |
DCE | I |
|
|
|
| I |
| Indicator |
1Applicable to SDP cards only. |
Note that pins 11 and 23 on an EIA/TIA-232 port are bidirectional, 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. You can then edit it by using the cnfict command. The dspbob command displays the state of leads at specified intervals.
Configure interface control templates
cnfict <port> <template> <output> <source>
addextlp, dspict, tstport
Privilege | Jobs | Log | Node | Lock |
1-2 | Yes | Yes | IGX | Yes |
cnfict 31.1 c SB on
Configure the conditioned interface control template for channel 31.1 to SB on (DDS).
beta TRM YourID:1 IGX 8420 9.2 Aug. 15 1998 17:30 MST
Data Channel: 31.1
Interface: DDS-4 OCU Config
Clocking: Looped
Interface Control Template for Connection while CONDITIONED
Lead Output Value Lead Output Value
SB ON RI OFF
DSR OFF CTS ON
DCD OFF
Last Command: cnfict 31.1 c sb on
Next Command:
cnfict 25.1 a CTS on
Configure the active interface control template for channel 25.1 to CTS on (EIA/TIA-232).
beta TRM YourID:1 IGX 8430 9.2 Aug. 15 1998 17:36 MST
Data Channel: 25.1
Interface: EIA/TIA-232 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 5.1 active CTS on
Configure the active interface control template for channel 5.1 to CTS on (V.35).
alpha TRM YourID:1 IGX 8420 9.2 Aug. 23 1998 10:29 PST
Data Channel: 5.1
Interface: V35 DCE
Clocking: Normal
Interface Control Template for Connection while ACTIVE
Lead Output Value Lead Output Value
RI (J) OFF DSR (E) ON
CTS (D) ON TM (K) OFF
DCD (F) ON
Last Command: cnfict 5.1 a cts on
Next Command:
Parameter | Description | |||
---|---|---|---|---|
port | Specifies the data channel or Frame Relay port whose interface control template is to be configured. Entered as <slot.port>. On an IGX node, the applicable cards are the LDM, HDM, FRM, CVM, and FTM. | |||
template | Specifies which interface control template to configure for the channel and has the format <a/c/l/n/f>. Valid entries are listed below. 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 | |||
| Entry | Template | Description |
|
| a | Active | The active control template is in effect while the data channel is active (normal operation) i.e., when the connection is routed and not failed.
| |
| Entry | Template | Description | |
| 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 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 addloclp or addrmtlp 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. | |
output | Specifies the output lead. Refer to the Configurable Lead information in the command description for abbreviations. Configurable output leads vary with the type of data interface (EIA/TIA-232, V.35, X.21, or EIA/TIA -449). | |||
source | Specifies how the lead is to be configured and has the format | |||
| Source Options | |||
| on | The output lead is asserted. | ||
| off | The output lead is inhibited. | ||
| l | Local. Indicates that the output follows a local lead. | ||
| r | Remote. Indicates that the output follows a remote lead. | ||
| input | Specifies the name of the local or remote input lead that the output lead follows. | ||
| delay | Specifies 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. |
Copies all control template information associated with a given channel: the active template information, the conditioned template information, and the looped template information for near and far ends. Once copied, the control template information may be edited with the cnfict command. See the cnfict command for more information on interface control templates.
On an IGX node, the applicable front cards are the LDM, HDM, FRM, CVM (for data), and FTM (for data).
Copy interface control templates
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 for data 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: EIA/TIA 232 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 whose interface control template information to copy. |
designating channel | Specifies the data channel or Frame Relay port that will receive the copied control template information. |
Removes connections from the network. After entry of the channel or range of channels to delete, a prompt requests confirmation of the selection. 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 does 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.
Delete connections
delcon <channel(s)>
addcon, dspcon, dspcons
Privilege | Jobs | Log | Node | Lock |
1-2 | Yes | Yes | IGX | Yes |
delcon 3.1
Delete connection 3.1.
pubsigx1 TN SuperUser IGX 8410 9.2 Aug. 14 1998 00:53 GMT
Local Remote Remote
Channel NodeName Channel State Type Compress Code COS
3.1 pubsigx1 3.2 Ok 64 7/8
3.2 pubsigx1 3.1 Ok 64 7/8
5.1.101 pubsigx1 5.1.102 Ok fr
5.1.102 pubsigx1 5.1.101 Ok fr
5.1.111 pubsigx1 9.1.1 Ok atfr
5.1.203 pubsigx1 5.1.204 Ok fst
5.1.204 pubsigx1 5.1.203 Ok fst
5.1.222 pubsigx1 8.5.2 Ok atfst
5.1.223 pubsigx1 8.5.3 Ok atfst
8.5.1 pubsigx1 5.1.111 Ok atfr
8.5.2 pubsigx1 5.1.222 Ok atfst
8.5.3 pubsigx1 5.1.223 Ok atfst
13.1 pubsigx1 13.2 Failed p
This Command: delcon 3.1
Delete these connections (y/n)?
Parameter | Description |
---|---|
channel | Specifies the data channel or channels to delete. The format is slot.port. |
Displays configuration details for data channels. This command provides information for voice, Frame Relay, ATM, and data channels. For data connections on the specified card and starting with the specified channel, the dspchcnf command displays the following information:
The data cards that support this command are the HDM, LDM, UVM, and CVM/CVP cards on the IGX node.
Display channel configurations
dspchcnf <start_channel>
cnfdch, cnfchadv, cnfchdfm, cnfchdl, cnfcheia, cnfchgn, cnfchtp, cnfchutl, cnffrcon
Privilege | Jobs | Log | Node | Lock |
1-6 | No | No | IGX | No |
dspchcnf 3.1
Display the configuration values for data channels starting at 3.1.
pubsigx1 TN SuperUser IGX 8410 9.2 Jan. 9 1998 00:04 GMT
Maximum EIA % DFM Pattern DFM
Channels Update Rate Util Length Status
3.1-4 2 100 8 Enabled
Last Command: dspchcnf 3.1
Next Command:
dspchcnf 9.1.3
Display the configuration values for data channels starting at channel 9.1.3.
sw176 TRM StrataCom IGX 8420 9.2.a2 Apr. 3 1998 17:32 PST
Maximum EIA % DFM Pattern DFM Idle Code PreAge
From 9.1.3 Update Rate Util Length Status Suppr (usec)
9.1.3-8 - - - - Enabled 0
Last Command: dspchcnf 9.1.3
Parameter | Description |
---|---|
start channel | Specifies the starting channel using the format slot.port |
Displays connection information for a specified channel. The information displayed includes:
The status that may be displayed includes:
| OK | Connection OK |
| FAILED | Connection failed |
Display connection
dspcon <channel>
cnfchec, cnfrtcost
Privilege | Jobs | Log | Node | Lock |
1-6 | No | No | IGX | No |
dspcon 13.1
Display information for data channel 13.1. This connection is FAILED and off hook.
pubsigx1 TN SuperUser IGX 8420 9.2 Aug. 14 1998 00:20 GMT
Conn: 13.1 pubsigx1 13.2 p
Desc: bogus Status:Failed
Path: Route information not applicable for local connections
pubsigx1 Line 13: Failed OFFHK pubsigx1 Line 13: Failed OFFHK
Last Command: dspcon 13.1
Next Command:
Parameter | Description |
---|---|
channel | Specifies the channel. The command displays connection information for one channel at a time. The format for channel specification is slot.channel. |
Displays a summary of the connections on an IGX node. Status that you can display includes:
| OK | Connection OK |
| FAILED | Connection failed |
Table 7-32 describes the fields in the dspcons screens.
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 state of the connection(s) as follows: OK = Routed Down = Downed OK Downed = Waiting for onhook to occur to allow courtesy down to take place for connection(s) that have been courtesy downed using the dncon command. Failed = unrouted, but trying |
Type | The type of connection (v = voice, d = data, fr = Frame Relay, atfr = ATM to Frame Relay interworking, atfst = ATM to Frame Relay interworking with ForeSight, -fail = failed connections; data rate in Kbps for 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 or ICS for data connections). |
COS | Class Of Service. |
Loopback | A connection with a local loopback is indicated by a right parenthesis symbol between the Local Channel and Remote NodeName columns. A Frame Relay connection with a port loopback is indicated by a right bracket symbol between the Local Channel and Remote NodeName columns. A connection with a remote loopback is indicated by a right parenthesis symbol before the channel number in the Remote Channel column. |
Display connections
dspcons [start_channel] [nodename] [connection type]
addcon, cnfchadv, chfchdfm
Privilege | Jobs | Log | Node | Lock |
1-6 | No | No | IGX | No |
dspcons
Display a summary of all connections.
alpha TRM YourID:1 IGX 8410 Rev:9.2 Aug. 16 1998 09:42 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 gamma 8.1 Ok v 0 L
9.2 beta 19.2 Ok v 0 L
14.1 gamma 15.1 Ok v VAD 2 L
Last Command: dspcons
Next Command:
dspcons
Display the connection with descriptors.
pubsigx1 TN SuperUser IGX 8410 9.2 July 25 1998 06:40 PDT
Local Remote Remote
Channel NodeName Channel State Type Descriptor
5.1.100 pubsigx3 5.1.200 Ok fr
6.1 pubsigx2 11.1 Ok 56
Last Command: dspcons +d
Next Command:
dspcons
Display a summary of all connections.
sw176 TRM StrataCom IGX 16 9.2.a2 Apr. 3 1998 17:36 PST
Local Remote Remote
Channel NodeName Channel State Type Compress Code COS
9.1.2-3 sw176 9.1.2-3 Ok 2x64 7/8
9.1.4 sw176 9.1.4 Ok 1x64 ICS 7/8
9.1.6 sw176 9.1.6 Ok g729r8 LDCELP
9.1.7 sw176 9.1.7 Ok 1x64 7/8
9.1.9 sw176 9.1.9 Ok c32 VAD/ADPCM
9.1.10-13 sw176 9.1.10-13 Ok 4x64 ICS 7/8
Parameter | Description |
---|---|
start channel | Specifies the channel to begin the display. The start channel is specified as follows: |
node name | Specifies that only connections to this remote node from the local node be displayed. If no nodename is designated, connections from the local node to all other nodes are displayed. |
connection type | Specifies that only connections of this type be displayed. If no connection type is designated, all connections appear. When you enter the connection type on the command line, precede it with a hyphen (-). Valid connection types to display are: -v = Displays only voice connections. -d = Display only data connections. -f = Displays Frame Relay connections. -abit = Shows A-bit (nni) status. -fabit = Shows connections with failed A-bit (nni) status. -fail = Shows only failed connections. |
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.
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 | 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 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. |
Displays interface control template information for data channels and Frame Relay ports. Displayed information includes:
For Frame Relay ports, the entire port configuration screen is displayed (see dspfrport command). The input being followed, where applicable, is specified. 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 | IGX | No |
dspict 25.1
Display the active interface control template for 25.1.
beta TRM YourID:1 IGX 8430
9.2 Aug. 15 1998 17:33 MST
Data Channel: 25.1
Interface: EIA/TIA 232 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
Next Command:
Parameter | Description |
---|---|
channel | Specifies the channel. The format of the channel specification is slot.port. |
template | Specifies which control template to display for the channel. There are three templates available for data channels and one available (a only) for Frame Relay ports. You also specify which end of the circuit. a = Active control template (normal operation). The only choice for a c = Conditioned control template (when connection fails). l = Looped control template (with local or remote loopback). n = Near. f = Far. |
Prints the configuration details for voice channels or data channels. This command uses the same syntax, and prints the same information as the dspchcnf command. See the dspchcnf description for syntax and output information.
Print channel configurations
prtchcnf <start_channel>
dspchcnf
Privilege | Jobs | Log | Node | Lock |
1-6 | Yes | No | IGX | Yes |
prtchcnf 14.1
Print the configuration values of circuit line 14.1.
None available as this command produces hardcopy.
Parameter | Description |
---|---|
start channel | Specifies the channel at which the printout begins. The format is slot.channel. |
Prints a summary of connections terminated at the IGX node.
Print connections
prtcons [start_channel] [nodename] [type]
dspcons
Privilege | Jobs | Log | Node | Lock |
1-6 | Yes | No | IGX | Yes |
prtcons
Print a summary of all connections.
None available as this command produces hardcopy.
Parameter | Description |
---|---|
start channel | Specifies the channel to begin the display. The start channel is specified as follows: slot.channel |
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 type | Specifies that only connections of this type be displayed. If no connection type is designated, all connections display. When you enter the connection type on the command line, it must be preceded with a hyphen (-). Valid connection types to display are -v = Displays only voice connections. -d = Display only data connections. -f = Displays Frame Relay connections. -nni = Displays Frame Relay network to network connections for -fail = Displays only failed connections. |
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 interface control template
prtict <port> <template>
cnfict, cpyict
Privilege | Jobs | Log | Node | Lock |
1-2 | Yes | No | IGX | Yes |
prtict 25.1
Print the active interface control template for 25.1.
None as this command produces hardcopy.
Parameter | Description |
---|---|
channel | Specifies the channel containing the data card. The start channel has the format slot.port. |
template | Specifies which control template to display for the channel. Three templates are available for data channels. One template (option "a") is available for Frame Relay ports. You can also specify the near or far end of the connection. a = Active control template (normal operation). The only choice for a Frame Relay port. c = Conditioned control template (when connection fails). l = Looped control template (with local or remote loopback). n = Near. f = Far. |
Posted: Mon Aug 19 21:29:31 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.