cc/td/doc/product/wanbu/bpx8600/9_1
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Data Connections

Data Connections

Data commands apply to the 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:

The nodes and card sets to which the commands in this chapter apply are:

Setting Up a Data Connection

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.

♦ cnfdclk

Specifies the clocking for the data channel

♦ cnfcldir

Sets the control leads for bidirectional pins 11 and 23 on an EIA/TIA-232 data channel. The default is input

♦ tstport

Use sixth lead feature to provide test port loopback

♦ addyred

Enables optional card redundancy. This step requires extra hardware.

♦ cnfict

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.

♦ cpyict

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.

Configuring Data Channel Redundancy

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. Applicable commands are"

Using an Interface Control Template

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.

Enabling DFM and Data Channel Utilization

DFM (Data Frame Multiplexing) is a feature on the IPX and 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:

Enabling Embedded EIA Operation on the LDP or LDM

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.

Setting Up DDS Trunks

DDS Trunks normally operate at 56 Kbps. The IPX and 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.

Summary of Commands

Table 7-1 shows the full command name and starting page of each description:


Table 7-1: Data Connection Commands
Mnemonic Description Page

addcon

Add connection

7-5

cnfchdfm

Configure Data Frame Multiplexing (DFM)

7-18

cnfcheia

Configure EIA

7-20

cnfcldir

Configure control lead direction

7-22

cnfdchtp

Configure data channel interface type

7-24

cnfdclk

Configure data clock

7-27

cnfict

Configure interface control template

7-31

cpyict

Copy interface control template

7-37

delcon

Delete connection

7-39

dspchcnf

Display channel configuration

7-41

dspcon

Display connection

7-43

dspcons

Display connections

7-45

dspict

Display interface control template

7-50

prtchcnf

Print channel configuration

7-52

prtcons

Print connections

7-53

prtict

Print interface control template

7-55

addcon

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 LDP or SDP card in an IPX node or 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 IPX 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.

♦ /n

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

♦ f

Entered after the data rate, an f specifies "fast EIA" (interleaved EIA) for the connection.

♦ t

Indicates "transparent" (CDP or CVM subrate DS0A): if you include the t-option, the IGX node does not check for supervisory or control information.


Table 7-2: Data Connection Load Table with Normal EIA and No DFM
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 timestamped data packets. Shaded connections generate non-timestamped data packets.


Table 7-3: Data Connection Load Table with Interleaved EIA
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

Connections above the line generate timestamped data packets. Shaded connections generate non-timestamped data packets. DFM is not available on interleaved EIA connections.


Table 7-4: Data Connection Load Table with Partially Filled Paclets and No DFM
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

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 timestamped data packets.


Table 7-5: Data Connection Load Table with Normal EIA and DFM
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 timestamped data packets.


Table 7-6: Data Connection Load Table with Partially Filled Packets and DFM
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 timestamped data packets.


Table 7-7: Data Connection Load Table with Partially Filled Packets and Interleaved EIA
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 timestamped data packets. DFM is not available on interleaved EIA connections.


Table 7-8: Sub-Rate Data Connection Load Table (HDM to HDM)
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 timestamped data packets. Shaded connections generate non-timestamped data packets. DFM is not available on sub-rate connections. Interleaved EIA is not available on sub-rate connections.


Table 7-9: Sub-Rate Data Connection Load Table (HDM to HDM)
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 timestamped data packets. DFM is not available on sub-rate connections. Interleaved EIA is not available on sub-rate connections.


Table 7-10: Super-Rate Data Connection Load Table (LDM to HDM)
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-timestamped 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 "0"s. The single "1" inserted in the final bit position of each octet ensures that no more than seven consecutive "0"s 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 "1"s, 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.

Full Name

Add a connection

Syntax

addcon <local channel> <remote node> <remote channel> <type> <coding> [avoid]

Related Commands

delcon, dncon, dspcon, dspcons, upcon

Attributes

Privilege

1-2

Jobs

Yes

Log

No

Node

IPX, IGX

Lock

Yes

Example 1

addcon 6.1 pubsipx2 11.1 56

Description

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 pubsipx2 is connected to channel 6.1 on node pubsipx1. The "56" under the "type" category indicates that the data rate for the channel is 56 Kbps.

System Response
pubsipx1 TN SuperUser IPX 16 9.1 July 25 1997 06:23 PDT From Remote Remote 6.1 NodeName Channel State Type Compress Code COS 6.1 pubsipx2 11.1 Ok 56 7/8 0 Last Command: addcon 6.1 pubsipx2 11.1 56 Next Command:
Example 2

addcon 5.1 beta 6.1-4 4x64

Description (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

Example 3

addcon 5.4-7 beta 6.1-4 4x64

Description (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


Table 7-11: addcon-Parameters

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:

7/8 7 bits of user data plus a "1" inserted in the final bit position of each data byte in a data packet. This is the default coding.

7/8e Used with LDP or LDM application.

8/8 8 bits of user data for each data byte in a data packet.

8/8I 8 bits of user data for each data byte in a packet. The data is inverted


Table 7-12: addcon-Optional Parameters
Parameter Description

avoid

Specifies the type of trunk for the connection to avoid. The default is no avoidance. The choices are:

*s avoid satellite trunks.

*t avoid terrestrial trunks.

*z avoid trunks using zero code suppression techniques that modify any bit position to prevent long strings of 0s.

cnfchdfm

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 cards that support the use of cnfchdfm are the SDP and LDP on the IPX node and the LDM and HDM on the IGX node.

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.

Full Name

Configure channel DFM

Syntax

cnfchdfm <channel(s)> <7 | 8 | 16> [e | d]

Related Commands

dspchcnf

Attributes

Privilege

1-2

Jobs

Yes

Log

Yes

Node

IPX, IGX

Lock

Yes

Example 1

cnfchdfm 5.1 8

Description

Set the DFM pattern length to 8 bits for data channel 5.1.

System Response
alpha TRM YourID:1 IPX 16 9.1 Aug. 15 1997 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:
Table 7-13: cnfchdfm-Parameters
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


Table 7-14: cnfchdfm-Optional Parameters
Parameter Description

e/d

Enables or disables DFM. The default is "e." Note that DFM works at rates no higher than 128 Kbps.

cnfcheia

Sets the sampling rate for the updating EIA control leads. This rate can be set from 0 (no sampling) to 20 updates per second and defaults to 2 seconds. This rate governs the polling interval and 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.

Full Name

Configure EIA update rate for channels

Syntax

cnfcheia <channel(s)> <update_rate>

Related Commands

dspchcnf

Attributes

Privilege

1-2

Jobs

Yes

Log

Yes

Node

IPX, IGX

Lock

Yes

Example 1

cnfcheia 5.1 15

Description

Set the EIA update rate to 15 sec. for data channel 5.1.

System Response
alpha TRM YourID:1 IPX 16 9.1 Aug. 15 1997 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:
Table 7-15: cnfcheia-Parameters
Parameter Description

channel

Specifies the channel or range of channels to over which to configure the EIA update rate.

update rate

Specifies the maximum EIA update rate in updates per second.

cnfcldir

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 bi-directional. 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.

Full Name

Configure control lead direction

Syntax

cnfcldir <channel> <lead> <direction>

Related Commands

cnfict, dspbob, dspict

Attributes

Privilege

1-2

Jobs

Yes

Log

Yes

Node

IPX, IGX

Lock

Yes

Example 1

cnfcldir 3.1 11 input

Description

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.

System Response
pubsipx1 TN SuperUser IPX 16 9.1 Aug. 14 1997 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:
Table 7-16: cnfcldir-Parameters
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 IPX or IGX node.
This is the default.
Output: The control lead acts as an output from the IPX or IGX node.

cnfdchtp

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.

Full Name

Configure data channel interface type

Syntax

cnfdchtp <channel> <interface type> [unassigned signaling]

Related Commands

none

Attributes

Privilege

1-2

Jobs

Yes

Log

Yes

Node

IPX, IGX

Lock

Yes

Example 1

cnfdchtp 31.1 oc

Description

Configure DDS channel 31.1 as OCU.

System Response
beta TRM YourID:1 IPX 32 9.1 Aug. 15 1997 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:
Example 2

cnfdchtp 22.1 dce

Description

Configure channel 22.1 as DCE with T1 unassigned signalling.

System Response
beta TRM YourID:1 IPX 32 9.1 Aug. 15 1997 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:
Table 7-17: cnfdchtp-Parameters
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').


Table 7-18: cnfdchtp-Optional Parameters
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.

cnfdclk

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:

DCE-Configured Data Port: Normal Clocking

When the data port is configured as DCE, selecting a clocking type of "n" (for normal) results in clocking as illustrated below. The IPX or IGX node, acting as DCE, provides both the transmit and receive data clocks to the user equipment.


Figure 7-1: Normal Clocking on a DCE


DCE-Configured Data Port: Split Clocking

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.


Figure 7-2: Split Clocking on a DCE


DCE-Configured Data Port: Looped Clocking

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.


Figure 7-3: Looped Clocking on a DCE


DTE-Configured Data Port: Normal Clocking

When the data port is configured as DTE, selecting a clocking type of "n" (for normal) results in clocking as illustrated below. The IPX node, 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.


Figure 7-4: Normal Clocking on a DTE


DTE-Configured Data Port: Split Clocking

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.


Figure 7-5: Split Clocking on a DTE


DTE Configured Data Port: Looped Clocking

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 IPX or IGX node by the user equipment. The network supports this clocking configuration for all data rates. The restrictions to the data clocking schemes are:


Figure 7-6: Looped Clocking on a DTE


Full Name

Configure data channel clocking type

Syntax

cnfdclk <channel> <normal/split/looped>

Related Commands

none

Attributes

Privilege

1-2

Jobs

Yes

Log

Yes

Node

IPX, IGX

Lock

Yes

Example 1

cnfdclk 5.1 n

Description

Configure the clocking for channel 5.1 to normal.

System Response
alpha TRM YourID:1 IPX 16 9.1 Aug. 23 1997 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 TM (K) OFF DCD(F) ON Last Command: cnfdclk 5.1 n Next Command:
Table 7-19: cnfdclk-Parameters
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:

  • n for Normal

  • s for Split

  • l for Looped

cnfict

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 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, 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-20 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 IPX or IGX node. The entries under the "IPX/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.


Table 7-20: Configurable Lead Names and Functions
Configurable Leads
Source IPX/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 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. It can then be edited using the cnfict command. The dspbob command displays the state of leads at specified intervals.

Full Name

Configure interface control templates

Syntax

cnfict <port> <template> <output> <source>

Related Commands

addextlp, dspict, tstport

Attributes

Privilege

1-2

Jobs

Yes

Log

Yes

Node

IPX, IGX

Lock

Yes

Example 1

cnfict 31.1 c SB on

Description

Configure the conditioned interface control template for channel 31.1 to SB on (DDS).

System Response
beta TRM YourID:1 IPX 32 9.1 Aug. 15 1997 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:
Example 2

cnfict 25.1 a CTS on

Description

Configure the active interface control template for channel 25.1 to CTS on (EIA/TIA-232).

System Response
beta TRM YourID:1 IPX 32 9.1 Aug. 15 1997 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:
Example 3

cnfict 5.1 active CTS on

Description

Configure the active interface control template for channel 5.1 to CTS on (V.35).

System Response
alpha TRM YourID:1 IPX 16 9.1 Aug. 23 1997 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:
Table 7-21: cnfict-Parameters
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 IPX node, the applicable cards are the SDP, LDP, FRP, CDP, and FTC. 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.

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 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
<on | off |local | remote> <input> [delay]. Valid source choices follow:

Source Options

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

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.

cpyict

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 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, CVM (for data), and FTM (for data).

Full Name

Copy interface control templates

Syntax

cpyict <source_port> <destination_port>

Related Commands

cnfict, dspict

Attributes

Privilege

1-2

Jobs

Yes

Log

Yes

Node

IPX, IGX

Lock

Yes

Example 1

cpyict 25.1 25.2

Description

Copy the interface control template for data channel 25.1 to channel 25.2.

System Response
beta TRM YourID:1 IPX 32 9.1 Aug. 15 1997 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:
Table 7-22: cpyict-Parameters
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.

delcon

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.

Full Name

Delete connections

Syntax

delcon <channel(s)>

Related Commands

addcon, dspcon, dspcons

Attributes

Privilege

1-2

Jobs

Yes

Log

Yes

Node

IPX, IGX

Lock

Yes

Example 1

delcon 3.1

Description

Delete connection 3.1.

System Response
pubsipx1 TN SuperUser IPX 16 9.1 Aug. 14 1997 00:53 GMT Local Remote Remote Channel NodeName Channel State Type Compress Code COS 3.1 pubsipx1 3.2 Ok 64 7/8 3.2 pubsipx1 3.1 Ok 64 7/8 5.1.101 pubsipx1 5.1.102 Ok fr 5.1.102 pubsipx1 5.1.101 Ok fr 5.1.111 pubsipx1 9.1.1 Ok atfr 5.1.203 pubsipx1 5.1.204 Ok fst 5.1.204 pubsipx1 5.1.203 Ok fst 5.1.222 pubsipx1 8.5.2 Ok atfst 5.1.223 pubsipx1 8.5.3 Ok atfst 8.5.1 pubsipx1 5.1.111 Ok atfr 8.5.2 pubsipx1 5.1.222 Ok atfst 8.5.3 pubsipx1 5.1.223 Ok atfst 13.1 pubsipx1 13.2 Failed p This Command: delcon 3.1 Delete these connections (y/n)?
Table 7-23: delcon-Parameters
Parameter Description

channel

Specifies the data channel or channels to delete. The format is slot.port.

dspchcnf

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 SDP and LDP on the IPX node and the HDM and LDM on the IGX node.

Full Name

Display channel configurations

Syntax

dspchcnf <start_channel>

Related Commands

cnfchadv, cnfchdfm, cnfchdl, cnfcheia, cnfchgn, cnfchtp, cnfchutl, cnffrcon

Attributes

Privilege

1-6

Jobs

No

Log

No

Node

IPX, IGX

Lock

No

Example 1

dspchcnf 3.1

Description

Display the configuration values for data channels starting at 3.1.

System Response
pubsipx1 TN SuperUser IPX 16 9.1 Jan. 9 1997 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:
Table 7-24: dspchcnf-Parameters
Parameter Description

start channel

Specifies the starting channel using the format slot.port

dspcon

Displays connection information for a specified channel. The information displayed includes:

The status that may be displayed includes:

OK

Connection OK

FAILED

Connection failed

Full Name

Display connection

Syntax

dspcon <channel>

Related Commands

cnfchec, cnfrtcost

Attributes

Privilege

1-6

Jobs

No

Log

No

Node

IPX, IGX

Lock

No

Example 1

dspcon 13.1

Description

Display information for data channel 13.1. This connection is FAILED and "off hook."

System Response
pubsipx1 TN SuperUser IPX 16 9.1 Aug. 14 1997 00:20 GMT Conn: 13.1 pubsipx1 13.2 p Desc: bogus Status:Failed Path: Route information not applicable for local connections pubsipx1 Line 13: Failed OFFHK pubsipx1 Line 13: Failed OFFHK Last Command: dspcon 13.1 Next Command:
Table 7-25: dspcon-Parameters
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.

dspcons

Displays a summary of the connections on an IPX or IGX node. Status that may be displayed includes:

OK

Connection OK

FAILED

Connection failed

Table 7-26 describes the fields in the dspcons screens.


Table 7-26: Fields in the dspcons Display
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 for data connections).

COS

The 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.

Full Name

Display connections

Syntax

dspcons [start_channel] [nodename] [connection type]

Related Commands

addcon, cnfchadv, chfchdfm

Attributes

Privilege

1-6

Jobs

No

Log

No

Node

IPX, IGX

Lock

No

Example 1

dspcons

Description

Display a summary of all connections.

System Response
alpha TRM YourID:1 IPX 16 Rev:9.1 Aug. 16 1997 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:
Example 2

dspcons

Description

Display the connection with descriptors.

System Response
pubsipx1 TN SuperUser IPX 16 9.1 July 25 1997 06:40 PDT Local Remote Remote Channel NodeName Channel State Type Descriptor 5.1.100 pubsipx3 5.1.200 Ok fr 6.1 pubsipx2 11.1 Ok 56 Last Command: dspcons +d Next Command:
Table 7-27: dspcons-Optional Parameters
Parameter Description

start channel

Specifies the channel to begin the display. The start channel is specified as follows:
slot.channel | slot.port.dlci | slot.vpi.vci

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 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.

dsprtcache

New in Release 9.1, 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:

Full Name

Display cost-based route cache

Syntax

dsprtcache [index] [c]

[index] specifies the cache entry index

[c] specifies to clear the entire cache or a single entry

Related Commands

dspcon, cnfrtcost, cnfpref

Attributes

Privilege

1-6

Jobs

No

Log

No

Node

IPX, IGX, BPX

Lock

No

Example 1

dsprtcache

Description

Display route cache contents, and let you monitor and manually clear the cache.

System Response
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:

Table 7-28: dsprtcache-Parameters
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.

dspict

Displays interface control template information for data channels and frame relay ports. Displayed information includes:

  ON.
OFF.
Following a local input.
Following a remote input.

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.

Full Name

Display interface control template

Syntax

dspict <port> <template>

Related Commands

cnfict, cpyict

Attributes

Privilege

1-2

Jobs

No

Log

No

Node

IPX, IGX

Lock

No

Example 1

dspict 25.1

Description

Display the active interface control template for 25.1.

System Response
beta TRM YourID:1 IPX 32 9.1 Aug. 15 1997 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:
Table 7-29: dspict-Parameters

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 frame relay port.

c Conditioned control template (when connection fails).

l Looped control template (with local or remote loopback).

n Near.

f Far.

prtchcnf

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.

Full Name

Print channel configurations

Syntax

prtchcnf <start_channel>

Related Commands

dspchcnf

Attributes

Privilege

1-6

Jobs

Yes

Log

No

Node

IPX, IGX

Lock

Yes

Example 1

prtchcnf 14.1

Description

Print the configuration values of circuit line 14.1.

System Response

None available as this command produces hardcopy.


Table 7-30: prtchcnf-Parameters
Parameter Description

start channel

Specifies the channel at which the printout begins. The format is slot.channel.

prtcons

Prints a summary of connections terminated at the IPX or IGX node.

Full Name

Print connections

Syntax

prtcons [start_channel] [nodename] [type]

Related Commands

dspcons

Attributes

Privilege

1-6

Jobs

Yes

Log

No

Node

IPX, IGX

Lock

Yes

Example 1

prtcons

Description

Print a summary of all connections.

System Response

None available as this command produces hardcopy.


Table 7-31: prtcons-Optional Parameters
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 failed
connections only.
-fail Displays only failed connections.

prtict

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.

Full Name

Print interface control template

Syntax

prtict <port> <template>

Related Commands

cnfict, cpyict

Attributes

Privilege

1-2

Jobs

Yes

Log

No

Node

IPX, IGX

Lock

Yes

Example 1

prtict 25.1

Description

Print the active interface control template for 25.1.

System Response

None as this command produces hardcopy.


Table 7-32: prtict-Parameters
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). This choice is the only option 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.


hometocprevnextglossaryfeedbacksearchhelp
Posted: Thu Aug 22 09:34:54 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.