|
|
To achieve peak network performance, the routing of traffic and the use of available bandwidth is configurable. The information used in configuring traffic routing and bandwidth is gathered from historical network trends. The tasks required to optimize the network are specifying channel utilization, specifying the class of service (including the use of the priority bumping feature), and managing bandwidth. These tasks are discussed in the paragraphs that follow.
Use the cnfchutl command to specify the expected utilization of Frame Relay, data, or voice channel as a percentage of the channel's total capacity. The specified value can be in the range of 0% to 100%; 100% is the default for data and Frame Relay channels. The default for voice channels is 40%. To display the utilization of a particular trunk, use the dsptrkutl command. This command displays a details on the packets transmitted over the trunk. The user can specify the rate in seconds at which the screen is updated. Use the dspload command to display the load for a specified trunk at a node.
Use the cnfcos command to specify a class of service (COS) for a Frame Relay, data, or voice channel connection. The class of service is the delay in seconds before the network reroutes a connection in the event of a trunk failure. The range is 0-15. By spreading out the COS numbers to vary the rerouting delay, one class of channels has a chance to reroute before the another class starts to reroute.
Priority bumping allows both BPX and IGX to switch connections that are classified as more important (via COS value) to bump existing connections that are less important when network resources become scarce. While the existing AutoRoute feature is capable of automatically redirecting all failed connections onto other paths, use the priority bumping command cnfbmpparm command to activate the priority bumping feature in order to retain important connections when network resources are diminished to a point when all connections cannot be sustained. Network resources are reclaimed for the more important connections by bumping (or derouting) the less important connections. Priority bumping is triggered by insufficient resources (such as bandwidth), resulting from a number of events, including changes to the network via the addcon, upcon, cnfcon, cnfpref, cnftrk, deltrk, as well as a trunk line/card failure, and node failure. The most typical event is a trunk failure.
In priority bumping, connections are defined by their Class of Service (COS) value. Connections tagged with the lowest COS, zero, are the most important to maintain. Connections tagged with the highest COS, 15, have the lowest priority. Connections that have a COS value in between 0 and 15 are progressively less important as they ascend upward.
The COS values are categorized into a set of 8 bands. These bands can be configured to meet the specific needs of each network. However, when priority bumping is enabled, the default settings are as follows:
| Band | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 |
COS | 0/1 | 2/3 | 4/5 | 6/7 | 8/9 | 10/11 | 12/13 | 14/15 |
 |
Note Configuring priority bumping requires a thorough knowledge of AutoRouting capabilities (also known as Automatic Routing Management) available bandwidth, and COS values. |
For an example of how this feature works, refer to Figure 10-1. If a trunk is established between switches A and B with a bandwidth of 1000 load units, it can support connection 1 (Conn. 1) with a bandwidth of 800. However, if we add a second connection (Conn. 2) with a bandwidth of 500, the trunk can no longer support both connections.
Conn. 1 (800) + Conn. 2 (500) = total bandwidth of 1300
When priority bumping is enabled the least important connection is bumped.
The lower COS connection has the higher priority. Conn. 1 with a COS of 5 is failed in order for Conn. 2 traffic (with a COS of 0) to flow without interruption.
Another example with three switches is illustrated in Figure 10-2. Three trunks are established:
| Trunk | Bandwidth |
AB | 1000 |
AC | 500 |
BC | 600 |
Two connections are established:
| Connection | Between Switches | COS | Band | Bandwidth |
|---|---|---|---|---|
1 | AB | 10 | 5 | 400 |
2 | BC | 14 | 7 | 300 |
All traffic on the connections is uninterrupted, but if Trunk AB fails, Trunk BC, with a bandwidth of 600, cannot handle the total bandwidth of both connections (700). Conn. 1 is in Band 5; Conn. 2 is in Band 7. The lower the band, the higher the priority. Conn. 2 is bumped to accommodate Conn. 1 with the higher priority.
|
Note For more information about the "bumping" or rerouting process, please refer to an update on this topic at: http://lbj.cisco.com/push_targets1/ucdit/cc/td/doc/product/wanbu/9_3/igx8400/u8400_93 /9_3_00rn.htm |
There are a number of commands that assist in managing bandwidth to achieve satisfactory traffic patterns.
upcon, dncon, cnfcon | The up and down connection commands can be used to temporarily down connections of a specified COS, thus releasing bandwidth for other services. Often it is possible to down some voice connections to provide more bandwidth for data and Frame Relay connections. Use the cnfcon command to change the bandwidth used by a connection. |
cnfpref | The configure preference command can be used to instruct a connection to route over a preferred path. This command can be used to assist in balancing the load on the network's trunks. |
dsprts, prtrts | The display and print routes commands can be used in conjunction with the cnfpref command to display the current connection routing information. |
Table 10-1 Shows the full command name and starting page for each description.
| Command | Description | Page |
|---|---|---|
cnfbmpparm | Configure priority bumping | |
cnfchutl | Configure channel utilization | |
cnfcmb | Configure combined timeout parameters | |
cnfcon | Configure a connection | |
cnfcos | Configure class of service | |
cnfpref | Configure preferences | |
cnfrtcost | Configure cost based routing | |
dncon | Down connections | |
dspbmpparm | Display priority bumping parameters | |
dbmpstats | Display priority bumping operational statistics | |
dspload | Display load | |
Display open space for routes | ||
dsprts | Display routes | |
dsptrkutl | Display trunk utilization | |
prtrts | Print routes | |
upcon | Up connections |
Priority bumping requires a number of configuration parameters which are saved in the BRAM and sent to the Standby Processor card. The parameters consist of a feature activation flag, a bundle size, and a set of seven COS bands (0-7), implicitly defining eight COS bands. Unlike AutoRoute capabilities, which include a number of different operational flavors, priority bumping is strictly a COS-based (or, more accurately, band-based) algorithm. Each band is defined by the low-end COS value within the band. Band 0 (implicitly defined) is the most important one, whereas Band 7 is the least important. Each connection within a band is equally important, despite the fact that it might be tagged with a different COS. Note that Band 0 is not bumpable.
A minimum of two bands are required to be defined for the priority bumping feature to work. A network with only one band is equivalent to having the priority bumping feature disabled.
The entire network must be upgraded to 9.3.0 in order for the priority bumping feature to be operational.
Use the following steps to setup priority bumping:
1. For a BPX switch, a license must be purchased for each BPX node on the network using the cnfswfunc 6 e command (see Example 10-1). The Cisco System Engineer enters the password to purchase priority bumping license. The license is granted immediately with the correct password.
Purchasing PB license on a BPX
---------------------------------------------
bpx1 TN StrataCom BPX 8620 9.3.0K Jan. 26 2000 14:16 PST
Index Status Function
1 Enabled Configuration Save/Restore
2 Enabled ForeSight
3 Enabled Multiple VTs (6 sessions enabled)
4 Enabled Virtual Trunks
5 Enabled ABR standard with VSVD
6 Enabled Priority Bumping
Last Command: cnfswfunc 6 e
2. From either an IGX switch or a BPX switch, enable priority bumping from any node on the network using the cnfbmpparm. Parameter changes made at one node are propagated to the rest of the network, then updated both to the BRAM and Standby Processor card.
| Band | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 |
COS | 0/1 | 2/3 | 4/5 | 6/7 | 8/9 | 10/11 | 12/13 | 14/15 |
3. To test priority bumping (optional) you can create an environment to "stress" bandwidth resources and see how the feature works. For example:
a. Delete a trunk.
b. Physically remove a cable to a connection.
c. Add connections to create limited bandwidth resources on a trunk.
4. To display the COS-based loads, use the dspload command. Information about the COS-based loads within each band helps you determine where to add connections in a priority bumping environment. In Example 10-2, the loads are displayed for a trunk. The total capacity is shown at the bottom of the display, and the load for each Band is displayed at the top. Any connection that is added to a band could bump and utilize bandwidth resources for the band that follows it; for example, adding a connection to Band 5 can bump connections in Band 6 and Band 7, allowing connections in Band 5 to utilize the bandwidth from those bands.
igxaf1 TN StrataCom IGX 8420 9.3 the.0F Jan. 10 2000 15:33 PST
Configured Trunk Loading: TRK igxaf1 16.4--10.1 bpx2
Band: CoS Xmt-c Rcv-c
B1 : 1- 1 191 191 Conid In Use+Avail 256
B2 : 2- 2 288 288
B3 : 3- 3 1036 1036 VPC conids: 0/256
B4 : 4- 4 216 216
B5 : 5- 5 216 216 Trunk type is Terrestrial
B6 : 6-13 900 900 Trunk supports cell routing
B7 :14-15 300 300 Trunk does not use ZCS
Total In Use 3147 3147 Trunk end supports all gateway types
Reserved 400 400 Gateway conns: 28/200
Available 75 75 Traffic: V TS NTS FR FST CBR NRT-VBR ABR
Total Capacity 3622 3622 RT-VBR
Lcn/GwLcn bmap, oe: 7F/5F,7F/00
1. Priority bumping does not support a situation when VPC CONIDs (or any resources other than bandwidth and LCN) are in short supply.
2. Priority bumping can only be activated when all nodes are upgraded to Release 9.3.0 switch software, or higher.
3. In a 9.3 network, there can be some nodes (BPX only) that do not purchase the priority bumping feature. Consequently, they are not capable of participating in the priority bumping operations. These nodes are not chosen during route selection unless the trunks leading to or from the nodes have sufficient network resources.
4. The maximum number of low priority connections that can be bumped in each attempt to route a high priority connection is 1023.
5. The maximum number of connections that can be bundled in a routing attempt is 50.
Configure priority bumping.
cnfbmpparm [1 [<enable>|<disable>] ]
[2 <bundle> ]
[3 <b1> <b2> [<b3> [<b4> [<b5> [<b6> [<b7>]]]]]]
| Privilege | Jobs | Log | Node | Card Type and Memory Requirement | Lock |
1-2 | No | No | IGX or BPX | NPM-32 NPM-64 BCC-64. | Yes |
dspbmpparm, dspbmpstats
| Parameter | Values | Description |
|---|---|---|
Priority Bumping Enabled | ON or OFF Default OFF | This flag specifies whether the priority bumping feature is activated on the node. |
Priority Bumping Bundle | 1 .. 50 | The number of connections that can be selected in a priority bumping routing request. |
Bumping Band 1 | 1 .. 15 Default 2 | The lowest value in the second most important COS band. Connections with a COS value below Bumping Band 1 are implicitly grouped as the most important band, Band 0. Connections in Band 0 can bump those in other bands, but cannot be bumped. Connections in Band 1 can bump those in bands 2-7, and can only be bumped by those in Band 0. |
Bumping Band 2 | 1 .. 15 Default 4 | The lowest value in the third most important COS band. Connections in this band can bump those in bands 3-7, and can be bumped by those in bands 0-1. Bumping Band 2 cannot be less than Bumping Band 1. If they are equal, the band definition ends. |
Bumping Band 3 | 1 .. 15 Default 6 | The lowest value in the fourth most important COS band. Connections in this band can bump those in bands 4-7, and can be bumped by those in bands 0-2. Bumping Band 3 cannot be less than Bumping Band 2. If they are equal, the band definition ends. |
Bumping Band 4 | 1 .. 15 Default 8 | The lowest value in the fifth most important COS band. Connections in this band can bump those in bands 5-7, and can be bumped by those in bands 0-3. Bumping Band 4 cannot be less than Bumping Band 3. If they are equal, the band definition ends. |
Bumping Band 5 | 1 .. 15 Default 10 | The lowest value in the sixth most important COS band. Connections in this band can bump those in bands 6-7, and can be bumped by those in bands 0-4. Bumping Band 5 cannot be less than Bumping Band 4. If they are equal, the band definition ends. |
Bumping Band 6 | 1 .. 15 Default 12 | The lowest value in the seventh most important COS band. Connections in this band can only bump those in Band 7, and can be bumped by those in bands 0-5. Bumping Band 6 cannot be less than Bumping Band 5. If they are equal, the band definition ends. |
Bumping Band 7 | 1 .. 15 Default 14 | The lowest value in the least important COS band. Connections in this band cannot bump, but can be bumped by those in bands 0-6. Bumping Band 7 cannot be less than Bumping Band 6. |
The default configuration is priority bumping disabled. However, when the feature is simply enabled (without changing the other banding parameters), the network would operate with eight COS bands.
| Band | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 |
COS | 0/1 | 2/3 | 4/5 | 6/7 | 8/9 | 10/11 | 12/13 | 14/15 |
A sample PB_Band configuration of 1, 2, 3, 4, 5, 11 and 13 provides a better granularity of COS banding at the more important end of the spectrum
| Band | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 |
COS | 0 | 1 | 2 | 3 | 4 | 5-10 | 11/12 | 13-15 |
Another sample PB_Band configuration of 3, 5, 8, 12, 13, 14 and 15 provides a better granularity of COS banding at the less important end of the spectrum.
| Band | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 |
COS | 0-2 | 3/4 | 5-7 | 8-11 | 12 | 13 | 14 | 15 |
A sample PB_Band configuration of 1, 2, 8, 9, 9, 9 and 9 provides a reduced COS banding, thus allowing better routing performance (with fewer iterations through the bands)
| Band | 0 | 1 | 2 | 3 | 4 |
COS | 0 | 1 | 2-7 | 8 | 9-15 |
The following screen illustrates how the bands in Example 10-5 are configured, than displayed.
bpx1 TN StrataCom BPX 8620 9.3.0K Jan. 26 2000 14:28 PST
1 Priority Bumping Enabled [ YES]
2 Priority Bumping Bundle [ 10] (D)
3 Priority Bumping Bands:
Bumping Band 1 [ 1] (D)
Bumping Band 2 [ 2] (D)
Bumping Band 3 [ 8] (D)
Bumping Band 4 [ 9] (D)
Bumping Band 5 [ 9] (D)
Bumping Band 6 [ 9] (D)
Bumping Band 7 [ 9] (D)
Last Command: cnfbmpparm 3 1 2 8 9 9
bpx1 TN StrataCom BPX 8620 9.3.0K Jan. 26 2000 14:28 PST
1 Priority Bumping Enabled [ YES]
2 Priority Bumping Bundle [ 10] (D)
3 Priority Bumping Bands:
Bumping Band 1 [ 1] (D)
Bumping Band 2 [ 2] (D)
Bumping Band 3 [ 8] (D)
Bumping Band 4 [ 9] (D)
Bumping Band 5 [ 9] (D)
Bumping Band 6 [ 9] (D)
Bumping Band 7 [ 9] (D)
Priority Bumping Active on this node [ YES]
Number of Priority Bumping Bands [ 4] (D)
Last Command: dspbmpparm
Another sample PB_Band configuration of 1, 1, 1, 1, 1, 1 and 1 provides a minimum COS banding of only two bands)
| Band | 0 | 1 |
COS | 0 | 1-15 |
Informs the system software of the expected utilization rate of connections with traffic-dependent compression algorithms (voice connections with VAD, data connections with DFM, Frame Relay connections). The software load model then takes the user-specified rate of the connection and modifies it by using the percent of utilization you specify with cnfchutl. The resulting rate is used in calculations for loading trunks. The load model uses these figures instead of calculated estimates from real traffic patterns.
For the full benefits of the compression algorithms to be used, the default utilizations should be modified after traffic studies have been performed. Traffic studies of Frame Relay connections should be used to determine optimum utilization settings. When calculating loads in a network, the load allocated to a connection is:
For example, with a channel utilization of 50% and a full load of 480 packets per second, the load allocated to a connection is:
For voice connections with VAD turned off, the bandwidth allocated is always the maximum bandwidth for the connection type. In other words, the utilization, although configurable, is ignored for a voice channel without VAD and a data channel without DFM.
If you use cnfchutl to increase the utilization of a connection, the system verifies that the additional bandwidth is available on the connection's current route. If the bandwidth is not available, the system attempts to reroute the connection. If no other route is found, the connection is failed.
If you use cnfchutl to decrease the utilization of a connection, the system makes the bandwidth available to other connections that require a route. The screen displayed by the cnfchutl command depends upon whether a data channel, voice channel, or Frame Relay channel is specified.
Configure channel utilization
cnfchutl <channel(s)> <%_util>
dspchcnf
| Privilege | Jobs | Log | Node | Lock |
1-2 | Yes | Yes | IGX | Yes |
cnfchutl 5.1 40
Description
Set utilization on data channel 5.1 at 40%.
alpha TRM YourID:1 IGX 8420 9.2 Aug. 23 1998 10:45 PST
Maximum EIA % DFM Pattern DFM
Channels Update Rate Util Length Status
5.1 15 40 8 Enabled
5.2-4 2 100 8 Enabled
Last Command: cnfchutl 5.1 40
Next Command:
cnfchutl 14.1 55
Description
Set utilization on voice channel 14.1 at 55%.
alpha TRM YourID:1 IGX 8420 9.2 Aug. 16 1998 10:10 PST
% Adaptive Gain (dB) Dial OnHk Cond
Channels Util Voice In Out Type Interface Type A B C D Crit.
14.1 55 Enabled -4 - User Unconfig ? ? - - a
14.2-24 40 Enabled 0 - Inband Unconfig ? ? - - a
Last Command: cnfchutl 14.1 55
Next Command:
cnfchutl 8.1.100 60
Description
Set utilization on Frame Relay channel 8.1.100 at 60%.
alpha TRM YourID:1 IGX 8420 9.2 Aug. 23 1998 10:45 PST
Frame Relay Channel Configuration Port: 8.1
From Minimum Peak AvgFrame Cmax VC Q ECN Q % Util
8.1.100 9.6 * 70 10 65535 65535 60
8.1.301 9.6 * 70 10 65535 65535 100
Last Command: cnfchutl 8.1.100 60
Next Command:
| Parameter | Description |
|---|---|
channel | Specifies the channel for configuring utilization. The channel can be in voice, data, Frame Relay. The format for channel depends on the technology, as follows:
|
percent utilization | Specifies the percentage of utilization of the channel. The is range 0-100. The default value for data or Frame Relay is 100%. The default value for voice is 40%. |
Configures a time the node waits for a second packet to become available for placing in an ATM cell. You can use the cnfcmb command to control the time that the node waits for individual traffic types. When you enter a value for a parameter, switch software multiplies the value by 125 microseconds to derive the timeout.
Configure combine timeout parameters
cnfcmb <parameter number> <value>
dspchcnf
| Privilege | Jobs | Log | Node | Lock |
service | Yes | No | IGX | Yes |
cnfcmb 1 1
Description
Change the timeout for voice packets from the default of 2 * 125 microseconds to 1 * 125 microseconds.
pubsigx1 TN SuperUser IGX 32 9.2 Sep. 17 1998 23:38 PDT
System-Wide Combine Timeout Parameters
1 Packet Combining Timeout for Voice (125 usec *)...................... 2
2 Packet Combining Timeout for Time Stamped Traffic (125 usec *)....... 2
3 Packet Combining Timeout for High Priority Traffic (125 usec *)...... 0
4 Packet Combining Timeout for Non Time Stamped Traffic (125 usec *)... 2
5 Packet Combining Timeout for Bursty Data 1 Traffic (125 usec *)...... 255
6 Packet Combining Timeout for Bursty Data 2 Traffic (125 usec *)...... 255
This Command: cnfcmb
Which parameter do you wish to change: 1 1
| Parameter | Description | Default |
|---|---|---|
1 | Timeout for Voice (multiplied by 125 microseconds) | 2 |
2 | Timeout for Time Stamped Traffic (multiplied by 125 microseconds). | 2 |
3 | Timeout for High Priority Traffic (multiplied by 125 microseconds) | 0 |
4 | Timeout for Non Time Stamped Traffic (multiplied by 125 microseconds) | 2 |
5 | Timeout for Bursty Data 1 Traffic (multiplied by 125 microseconds) | 255 |
6 | Timeout for Bursty Data 2 Traffic (multiplied by 125 microseconds) | 255 |
Determines the priority for rerouting a connection. You determine the priority by specifying a delay before the network reroutes one or more failed connections. The COS applies to:
When connections have failed (typically due to a trunk failure), the network reroutes them according to priorities that are set primarily by the class of service (COS). The value of COS is the number of seconds the network waits before it begins to reroute the connection, so the COS determines the rerouting order for connections owned by a node. The range of possible COS values is 0-15.
The number of connections in a network has an effect on the increment between COS values you should use. For larger numbers of connections, you should allow more time to reroute the connections in a class. To facilitate the greater time required to reroute larger numbers of connections, use a larger increment between COS values. In a larger network, for example, you could specify COS values that are 3 seconds apart (such as 0, 3, 6, 9, 12, and so on, for example). For a network with less traffic, assign COS values in increments of 1 or 2. This strategy ensures that all connections of a given COS reroute before the connections with the next COS start to reroute.
Configure class of service for connections
cnfcos <group | channel(s)> <cos>
dspcons
| Privilege | Jobs | Log | Node | Lock |
1-2 | Yes | Yes | IGX | Yes |
cnfcos 5.1 0
Set the COS for channel 5.1 to 0.
alpha TRM YourID:1 IGX 8420 9.2 Aug. 16 1998 10:12 PST
Local Remote Remote Route
Channel NodeName Channel State Type Compression Code Avoid COS O
5.1 beta 25.1 Ok 256 7/8 0 L
9.1.100 gamma 8.1.200 Ok fr 0 L
9.2.400 beta 19.2.302 Ok fr 0 L
14.1 gamma 15.1 Ok v 0 L
Last Command: cnfcos 5.1 0
Next Command:
| Parameter | Description |
|---|---|
channels | Specifies the voice, data, Frame Relay, or Fast PAD voice/data channel(s), where channel is one of the following:
|
cos | Specifies the class of service number to assign to the channel, range of channels, or connection group. The range is 0-15 seconds, so the rerouting priority is inversely proportional to the COS (a low COS values means a high routing priority). |
Specifies the preferred route for a connection or range of connections. Enter cnfpref only at a node that is an end point of the connection. This command applies only to connections that exist within a domain. Do not attempt to execute cnfpref on connections that exist between domains.
The preferred route for a connection is used when possible. If the preferred route is different from the existing route, the connection automatically moves to the preferred route whenever network conditions allow (for example, when trunks are out of alarm and sufficient bandwidth exists).
Configure preferred route for connections
cnfpref <channel(s) | *> <route> < + | -> [d]
dsprts
| Privilege | Jobs | Log | Node | Lock |
1-2 | Yes | Yes | IGX, BPX | Yes |
cnfpref 14.1 13/beta 15/gamma d
Description
Select the preferred route for channel 14.1 to be through beta trunk 13 to beta then to gamma trunk 15. For gamma, the "d" in the command specifies that the route is directed.
alpha TRM YourID:1 IGX 8420 9.2 Aug. 16 1998 10:22 PST
From 14.1 Route
14.1
alpha 14--13beta 15--15gamma
Pref:(D) alpha 14--13beta 15--15gamma
Last Command: cnfpref 14.1 13/beta 15/gamma d
Next Command:
cnfpref 6.4 -
Description
Remove the preferred route for channel 6.4.
cnfpref * +
Description
Designate the current routing of all locally owned connections to be the preferred routing. Using a "-" instead of a "+" in the command would remove the preferred routing designation of all locally owned connections.
alpha TRM YourID:1 IGX 8420 9.2 Aug. 23 1998 10:48 PST
Chan/Grp Route
5.1
alpha 10-- 7beta
Pref: alpha 10-- 7beta
9.1.100
alpha 14--13beta 15--15gamma
Pref: alpha 14--13beta 15--15gamma
9.1.200
alpha 10-- 7beta 15--15gamma
Pref: alpha 10-- 7beta 15--15gamma
9.2.400
alpha 10-- 7beta
Pref: alpha 10-- 7beta
Last Command: cnfpref * +
Next Command:
| Parameter | Description |
|---|---|
channels | Specifies the channel or range of channels for preferred route configuration. The channel specifier has one of the following formats
A "*" specifies all locally owned connections and applies only to the "+" and "-". |
route | Designates the preferred route for the connection(s) to take through the network. The route is designated by one or more "trunk/node name" pairs. At a given node alpha, for example, entering a route of "12/delta 6/epsilon", would route the connection from alpha to delta via delta's trunk 12. The connection would then go from delta to epsilon via epsilon's trunk 6. A "+" causes the connection's current route to become the preferred route. A "-" removes the connection's preferred route designation. |
| Parameter | Description |
|---|---|
d | Specifies directed routing. If the preferred route is not available, the connection is failed. |
Configures the cost cap for a connection when cost-based routing is configured.
A maximum allowable cost value (cost cap) is used during route determination to prevent selection of a route which exceeds an acceptable cost. For routing based on delay, the cost cap is the acceptable end-to-end delay for the connection type. This cap is configured network-wide per delay-sensitive connection type.
For routing based on trunk cost, the cost cap is the acceptable end-to-end cost. This cap is configured per connection. The default cost cap is 100, which is derived from the maximum hops per route (10) and default cost per trunk (10). The cost cap can be changed at any time. If the cost cap is decreased below the current route cost, the connection is not automatically rerouted. A manual reroute is required to route the connection to fit under the new cost cap. This gives the user more control over the connection reroute outage.
|
Note cnfrtcost is only valid at the node where the connection was added. |
Display connection loading
cnfrtcost <connection> <max cost>
<connection> indicates the connection endpoint (that is, slot.port.vpi.vci)
<max cost> indicates the maximum allowable route cost
Valid values = 1 - 500
dspcon, cnfpref, dsprtcache
| Privilege | Jobs | Log | Node | Lock |
1-2 | Yes | Yes | IGX, BPX | Yes |
cnfrtcost 9.2.5.100 40 1
After configuring the cost cap for a connection, you can check to see the configured value with the dspcon command, as is shown in the System Response example. This is the dspcon response for 9.2.5.100 with the additional fields of Max Cost (40) and Route Cost (1). For a route optimized on trunk delay, the cost labels are updated to indicate delay: Max Cost becomes Max Delay and Route Cost becomes Route Delay.
Select route cost for channel 9.2.5.100.
sw203 TN StrataCom BPX 8620 9.1.a4 Sep. 24 1998 18:18 GMT
Conn: 9.2.5.100 sw242 14.2.5.100 cbr Status:OK
PCR(0+1) % util CDVT(0+1) Policing
50/50 100/100 10000/10000 4/4
Owner: LOCAL Restriction: NONE COS: 0
TestRTD: 0 msec Trunk Cell Routing Restrict: Y Max Cost: 40 Route Cost: 1
Path: sw203 3.1.1-- 2.1.1sw242
Pref: Not Configured
sw203 ASI-T3 : OK sw242 ASI-OC-3 : OK
Line 9.2 : OK Line 14.2 : OK
OAM Cell RX: Clear NNI : OK
NNI : OK
Last Command: dspcon 9.2.5.100
Next Command:
Deactivates (downs) a connection, bundle of connections, a connection group or all connection in a COS or COS range. The dncon command temporarily removes one or more connections from the network. This command is useful for temporarily removing voice connections when additional bandwidth is necessary for other types of connections.
Connections can be downed immediately or with courtesy. Even with immediate downing, a prompt appears that requests confirmation. With courtesy downing, the system waits until the connection is onhook before downing the connection. Courtesy downing is possible only if the onhook status has been configured with the cnfvchtp command. The upcon command reactivates the voice connections. The up/down status of the voice connections appears in the "State" column of the dspcons screen. Table 10-8 shows each item in the State column.
| State | Description |
|---|---|
"OK" (routed) | Connection is activated and able to carry traffic. |
"Down" | Connection has been added to the network database but is not activated and is not able to carry traffic. |
"OK(Dn)" | 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 to reroute. |
Down connection
dncon {<group | local_chan(s)> | COS <cos_range>} {i | c}
upcon
| Privilege | Jobs | Log | Node | Lock |
1-2 | Yes | Yes | IGX | Yes |
dncon 14.1 c
Down connection 14.1 with courtesy.
dncon 14.1 i
Down connection 14.1 immediately.
dncon cos 4-8 c
Courtesy down on-hook connections network-wide with COS 4 through 8. This command marks all connections that may be courtesy downed at one time and does not monitor new connections or those that later fit the COS.
dncon 3.1.100 i
Immediately down connection 3.1.100.
pubsigx1 TN SuperUser IGX 32 9.2 Aug. 26 1998 16:51 GMT
Local Remote Remote
Channel NodeName Channel State Type Compress Code COS
3.1.100 pubsigx1 3.2.200 Ok fr
3.2.200 pubsigx1 3.1.100 Ok fr
This Command: dncon 3.1.100 i
Down these connections (y/n)?
dncon cos 4-8 i
Immediately down all connections network-wide with COS 4 through 8. This command executes once, so if individual connections are subsequently upped or new connections added in this COS range, they remain up.
| Parameter | Description |
|---|---|
channels or group | Specifies a group, a channel, or a range of channels to down. |
cos range | Specifies the COS or COS range. The range is 0-15. |
| Parameter | Description |
|---|---|
i/c | Specifies immediate downing (i) of the specified connections or courtesy downing (c) of the specified connections. |
Displays the priority bumping parameters.
Display priority bumping parameters
dspbmpparm
igxr2 TN StrataCom IGX 8420 9.3.0K Jan. 26 2000 15:19 PDT
1 Priority Bumping Enabled [ YES]
2 Priority Bumping Bundle [ 10] (D)
3 Priority Bumping Bands:
Bumping Band 1 [ 2] (D)
Bumping Band 2 [ 4] (D)
Bumping Band 3 [ 6] (D)
Bumping Band 4 [ 8] (D)
Bumping Band 5 [ 10] (D)
Bumping Band 6 [ 12] (D)
Bumping Band 7 [ 14] (D)
Priority Bumping Active on this node [ YES]
Number of Priority Bumping Bands [ 7] (D)
Last Command: dspbmpparm
bpx1 TN StrataCom BPX 8620 9.3.0K Jan. 26 2000 14:20 PST
1 Priority Bumping Enabled [ YES]
2 Priority Bumping Bundle [ 10] (D)
3 Priority Bumping Bands:
Bumping Band 1 [ 2] (D)
Bumping Band 2 [ 4] (D)
Bumping Band 3 [ 6] (D)
Bumping Band 4 [ 8] (D)
Bumping Band 5 [ 10] (D)
Bumping Band 6 [ 12] (D)
Bumping Band 7 [ 14] (D)
Priority Bumping Active on this node [ NO]
Number of Priority Bumping Bands [ 0] (D)
Last Command: dspbmpparm
cnfbmpparm
| Parameter | Values | Description |
|---|---|---|
Priority Bumping Enabled | ON or OFF Default OFF | This flag specifies whether the priority bumping feature is activated on the node. |
Priority Bumping Bundle | 1 .. 50 | The number of connections that can be selected in a priority bumping routing request when PB is enabled. |
Bumping Band 1 | 1 .. 15 Default 2 | The lowest value in the second most important COS band. Connections with a COS value below Bumping Band 1 are implicitly grouped as the most important band, Band0. Connections in Band 0 can bump those in other bands, but cannot be bumped. Connections in Band 1 can bump those in bands 2-7, and can only be bumped by those in Band 0. |
Bumping Band 2 | 1 .. 15 Default 4 | The lowest value in the third most important COS band. Connections in this band can bump those in bands 3-7, and can be bumped by those in bands 0-1. Bumping Band 2 cannot be less than Bumping Band 1. |
Bumping Band 3 | 1 .. 15 Default 6 | The lowest value in the fourth most important COS band. Connections in this band can bump those in bands 4-7, and can be bumped by those in bands 0-2. Bumping Band 3 cannot be less than Bumping Band 2. |
Bumping Band 4 | 1 .. 15 Default 8 | The lowest value in the fifth most important COS band. Connections in this band can bump those in bands 5-7, and can be bumped by those in bands 0-3. Bumping Band 4 cannot be less than Bumping Band 3. |
Bumping Band 5 | 1 .. 15 Default 10 | The lowest value in the sixth most important COS band. Connections in this band can bump those in bands 6-7, and can be bumped by those in bands 0-4. Bumping Band 5 cannot be less than Bumping Band 4. |
Bumping Band 6 | 1 .. 15 Default 12 | The lowest value in the seventh most important COS band. Connections in this band can only bump those in Band7, and can be bumped by those in bands 0-5. Bumping Band 6 cannot be less than Bumping Band 5. |
Bumping Band 7 | 1 .. 15 Default 14 | The lowest value in the least important COS band. Connections in this band cannot bump, but can be bumped by those in bands 1-6. Bumping Band 7 cannot be less than Bumping Band 6. |
Priority Bumping Active on this node? | YES or NO Default = NO | Indicates whether priority bumping is enabled or disabled on a particular node. |
Number of Priority Bumping Bands | 0 through 7 | Indicates the number of priority bands enabled. If priority bumping is not enabled, this value is 0. |
Displays priority bumping operational statistics for the priority bumping feature.
Display priority bumping statistics.
dspbmpstats
dspbmpparm, cnfbmpparm, dsprrsts, rrtinf
| Privilege | Jobs | Log | Node | Lock |
? | Yes | Yes | IGX/BPX | ? |
dspbmpstats command from a BPX
sw67 TN StrataCom BPX 8620 9.3.0L Jan. 28 2000 18:57 PST
PB Routing Statistic
Latest bumping band - Latest bumped band -
Hwm bumping band - Lwm bumped band -
Latest # bumping conns/req 0 Latest # bumped conns/req 0
Hwm # bumping conns/req 0 Hwm # bumped conns/req 0
Accum # bumping conns 0 Accum # bumped Lcons 0
Avg # bumping conns/req 0.00 Accum # bumped VLcons 0
Last Command: dspbmpstats
| Statistics Object | Description |
|---|---|
Latest bumping band | The band value of the latest reroute connection which originates from this node. |
Latest bumped band | The band value of the latest connection which is bumped from this node. The bumped connection can be mastered or slaved on this node. It can even be simply traversing this node. The bumping connection also can be mastered on, slaved on, or simply which originates from this node. |
Hvm bumping band | The high water mark, since the last resetting of statistics, of the band value of any reroute connection which traverses this node |
Lwm bumped band | The low water mark, since the last resetting of statistics, of the band value of any connection which has been bumped from this node. |
Latest # bumping conns/req | The number of reroute candidate connections in the most recent reroute request. If there are many similar connections to be routed to the same destination, this value usually represents the bundle size of the Priority Bumping reroute request. |
Latest # bumped conns/req | The number of connections selected to be bumped from this node in the most recent reroute request. |
Hwm # bumping conns/req | The high water mark, since the last resetting of statistics, of the number of reroute candidate connections in any reroute request. |
Hwm # bumped conns/req | The high water mark, since the last resetting of statistics, of the number of connections selected to be bumped from this node in any reroute request. |
Accum # bumping conns | The total number, since the last resetting of statistics, of successfully routed connections. |
Accum # bumped Lcons | The total number, since the last resetting of statistics, of master or slave connections bumped from this node. |
Avg # bumping conns/req | The average number, since the last resetting of statistics, of successfully routed connections in a reroute request. |
Accum # bumped VLcons | The total number, since the last resetting of statistics, of via connections bumped from this node. |
Displays both the used and available bandwidth (both in the transmit and receive directions) for each trunk at the specified node. The "transmit" direction is from the node specified and to the node at the other end of the trunk. In the screen display, the numbers of disabled trunks appear in dim, reverse video on the screen.
The dspload display reflects the static load model stored by the node and used to determine the bandwidth available for new connections and reroutes. The display does not represent changes due to the dynamic utilization of the trunks. Some types of connections, such as voice connections using adaptive voice and data connections using Data Frame Multiplexing (DFM), suppress packets. In contrast, Frame Relay connections may generate additional packets when bandwidth permits.
When this command is executed at a local node in structured networks, the information displayed is for any node on the intra-domain lines belonging to the same domain. The node uses the terminating and through routed connections' calculated load to calculate the trunk load. The connection type (v, c, a, or d) or baud rate (9.6 Kbps, 56 56 Kbps, and so on) and other factors determine its basic load. The calculated trunk load is also modified by the cnfchutl command for connections that use VAD, DFM, or Frame Relay.
A certain amount of bandwidth is reserved for each trunk (using cnftrk). The reserved bandwidth is available only for high priority packets (for example, PCC traffic). The node cannot route connections using this reserved bandwidth. The following loading, in packets per second, is calculated for each trunk in each direction:
If the dspload arguments include a trunk number, detailed information for each of the packet types on that line appears. See Example 2. Additional categories of information for Frame Relay loads on the trunk include Cmax In Use, Cmax Available, and Cmax Capacity.
As shown in Example 3, the dspload screen displays the bandwidth used by rt-VBR and nrt-VBR connections on a trunk.
And in Example 4, the dspload screen used with the -cos parameter displays the load categorized by bands. This is applicable and meaningful only when the Priority Bumping option is enabled.
Display connection loading
dspload [nodename] [line number] [-cos]
dsptrkutl, cnfcmparm
| Privilege | Jobs | Log | Node | Lock |
1-6 | No | No | IGX, BPX | No |
dspload
Display the load for all trunks that terminate on the current node.
alpha TRM YourID:1 IGX 8420 9.2 Aug. 16 1998 11:54 PST
Trunk loads for node 'alpha'
Units Used Available Reserved Cmax In Use Cmax In Use
PLN Xmt Rcv Xmt Rcv Xmt Rcv Xmt Rcv XmtA RcvA XmtB RcvB
10 Pkts Pkts 1760 1744 8304 8320 600 600 0 0 0 0
14 Pkts Pkts 504 504 6896 6896 600 600 20 20 0 0
Last Command: dspload
Next Command:
dspload 10
Display the load for the trunk in slot 10 of the current node.
sw151 TN SuperUser IGX 16 9.2 Aug. 26 1998 17:05 GMT
Configured Trunk Loading: TRK sw151 10--10 sw150
Load Type Xmt-p Rcv-p lcl
NTS 2016 2016 Conid In Use 11
TS 432 432 Conid Available 1760
Voice 208 208 Total Capacity 1771
BData A 0 0
BData B 0 0 Line type is Terrestrial
CBR 0 0 Line supports BData Load
rt-VBR 0 0 Line does not use ZCS
nrt-VBR 50 50
ABR 0 0 Traffic class:
Total In Use 2656 2656 V TS NTS FR FST CBR nrt-VBR ABR rt-VBR
Reserved 992 992
Available 76352 76352
Total Capacity 80000 80000
Last Command: dspload 10
Next Command:
dspload 1.1
Displays the load for trunk 1 in slot 1 of the current node based on load type (CBR, ABR, etc.). The trunk queue delay is also displayed if routing with delay is enabled.
sw203 TN SuperUser BPX 8620 9.2 Sep. 24 1998 17:05 GMT
Configured Trunk Loading: TRK sw203 1.1-- 1.1 sw242
Load Type Xmt-c Rcv-c lcl
NTS 0 0 Conid In Use 1068
TS 0 0 Conid Available 703
Voice 0 0 Total Capacity 1771
BData A 0 0
BData B 0 0 Trunk cost: 26
CBR 23100 23100 Trunk V Qdelay: 2.5 msec
rt-VBR 14300 14300 Trunk NTS Qdelay: 31.9 msec
nrt-VBR 14300 14300 Trunk end doesn't support complex gateway
ABR 18901 18901 Trunk is Terrestrial
Total In Use 56301 56301 Trunk does not use ZCS
Reserved 1000 1000 Trunk end doesn't support complex gateway
Available 38699 38690 Traffic class: V TS NTS FR FST CBR nrt-VBR ABR
Total Capacity 96000 96000 rt-VBR
Last Command: dspload 1.1
Next Command:
dspload 1.1 -cos
Displays the "cos based" load for trunk 1 in slot 1 of the current node. The -cos option displays the load categorized by bands. This is applicable and meaningful only when the Priority Bumping option is enabled.
sw67 TRM StrataCom BPX 8620 9.3.a7 Mar. 2 2000
13:52 GMT
Configured Trunk Loading: TRK sw67 1.1--13.1 sw66
Band: CoS Xmt-c Rcv-c
B0 : 0- 1 50 50 Conid In Use+Avail: 1+
1770= 1771
B1 : 2- 3 0 0 VPC conids: 0/256
B2 : 4- 5 0 0
B3 : 6- 7 0 0 Trunk is Terrestrial
B4 : 8- 9 0 0 Trunk supports cell routing
B5 :10-11 0 0 Trunk does not use ZCS
B6 :12-13 0 0 Trunk end doesn't support complex
gateway
B7 :14-15 0 0 Traffic: V TS NTS FR FST CBR
NRT-VBR ABR
Total In Use 50 50 RT-VBR
Reserved 5000 5000 Lcn/GwLcn bmap, oe: 00/00,00/00
Available 90950 90950
Total Capacity 96000 96000
Last Command: dspload 1.1 -cos
| Parameter | Description |
|---|---|
nodename | Specifies the local node. |
line number | Specifies the physical line whose loading information is displayed. |
-cos | Displays loading based on all cos band values. |
Displays the open space for a connection route.
Display open space for a route
dspospace <connection | group>
none
| Privilege | Jobs | Log | Node | Lock |
1-6 | No | No | IGX | No |
dspospace 4.1.1
Description
Display the open space for the ATM Frame Relay connection 4.1.1. The line interface card is a UFM-8C.
sw110 TN SuperUser IGX 16 9.2 Jan. 22 1998 19:11 GMT
Open Space for 4.1.1 Snapshot
Domain
Local: sw110 8--10.3sw86 6.2-- 6.1sw81
ms_cur_pkts: 524272 ms_cur_cells: 12576
sm_cur_pkts: 4368 sm_cur_cells: 11296
Last Command: dspospace 4.1.1
Next Command:
| Parameter | Description |
|---|---|
connection | Specifies the connection. |
This command displays the cache of all cost-based routing connections. The optional 'index' parameter lets you specify a cache entry index. The optional 'c' parameter clears the cache. The information displayed includes:
Display cost-based route cache
dsprtcache [index] [c]
[index] specifies the cache entry index
[c] specifies to clear the entire cache or a single entry
dspcon, cnfrtcost, cnfpref
| Privilege | Jobs | Log | Node | Lock |
1-6 | No | No | IGX, BPX | No |
dsprtcache
Display route cache contents, and let you monitor and manually clear the cache.
pissaro TN StrataCom BPX 8620 9.2 Jun. 18 1998 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 the routes used by all connections at a node. The display shows the trunk numbers and names of all nodes in the path.
The command dsprts displays the current cost for all connection routes. A derouted connection shows no current cost. A connection route optimized with trunk delay shows the current total delay. A highlighted connection on the display has exceeded the maximum route cost.
Display connection routing
dsprts [start group | chan] [nodename]
cnfpref
| Privilege | Jobs | Log | Node | Lock |
1-6 | No | No | IGX, BPX | No |
dsprts
Display the connection routes.
sw203 TN SuperUser BPX 8620 9.2 Sep. 24 1998 17:47 GMT
Conn Route
9.1.1.* (Cost = 5)
sw203 1.1-- 1.1sw242
Pref: Not Configured
9.2.5.100 (Cost = 1)
sw203 3.1.1-- 2.1.1sw242
Pref: Not Configured
9.2.5.101 (Cost = 1)
sw203 3.1.1-- 2.1.1sw242
Pref: Not Configured
9.2.5.102 (Cost = 5)
sw203 1.1-- 1.1sw242
Pref: Not Configured
This Command: dsprts
Continue?
| Parameter | Description |
|---|---|
start group or channel | Specifies the starting group or channel with which to begin the display. Channel displays are in numeric order. If no starting channel is specified, the display begins with the first connected channel. Start channel is specified in one of the following formats: Voice connection: slot.channel Data connection: slot.port Frame relay connection: slot.port.DLCI Frame relay connection group: remote node.groupname Access device connection: slot.port.device_ID |
node name | Specifies that connections from only the local node to the current node are displayed. If no nodename is entered, connections from the local node to all other nodes are displayed. |
Displays dynamic utilization information for a specified trunk. The trunk must be upped and added to use this command. Table 10-17 lists the trunk utilization and terminated connection parameters included in the display. The parameter values are updated according to the specified or default interval and the screen remains displayed until the DEL key is depressed. Disabled trunks have their trunk number displayed in dim, reverse video on the screen.
If you notice that data traffic has slowed or stopped due to the very high trunk utilization due to network traffic, it may be because a node is receiving excessive volumes of network traffic (CC) traffic. In this case, the node may start dropping messages, which will result in communication breaks with other nodes as well as possible communication failures on some of its trunks.
You can detect the excessive traffic by displaying various statistics such as network statistics (nwstats), SAR statistics (srstats), and check utilization of the node's trunks by using the dsptrkutl command. In the event of excessive traffic, these command displays will show values that are increasing at a high rate. (See the cnfnodeparm parameters Enable Degraded Mode, Auto Switch on Degrade, and Max Degraded Aborts for descriptions of how to set parameters so that if a node has exhausted its internal resources due to excessive messaging (among other possible causes), which leads the node to abort, the node will either switch to the standby CC if available, or it will enter degraded mode (if the cnfnodeparm Enable Degraded Mode parameter is enabled).
| Trunk Utilization Parameters and Statistics | Description |
|---|---|
Elapsed Time (seconds) | Elapsed time in seconds.since the command was started |
Total Packets Transmitted | Number of packets transmitted during the elapsed time. |
Overall Packet Rate | Number of packets transmitted per second during the (pkts/sec)elapsed time. |
Overall utilization | Bandwidth used, expressed as a percentage of the available bandwidth during the elapsed time. This is: 100 x ("Total packets transmitted")/("Elapsed Time" x bandwidth (in packets per second)). |
Peak Interval Utilization | Bandwidth used, expressed as a percentage of the available bandwidth during the peak interval. This is: 100 x ("Total packets transmitted")/("Peak Interval" x bandwidth (in packets per second)). |
Last Interval (seconds) | Elapsed time, in seconds, for the last screen update interval. |
Interval packets generated | Number of packets transmitted during the last interval. |
Interval packet rate (pkts/sec) | Number of packets transmitted per second during the last interval. |
Interval utilization | The used bandwidth expressed as a percentage of the available bandwidth during the last interval. The derivation of interval utilization is as follows: 100 x ("Interval packets transmitted") / ("Last Interval" x bandwidth (in packets per second)). |
Total Connections | Total number of connections routed over the trunk. |
Terminated/Via | Terminated: Number of connections routed over the trunk that terminate at this node. Via: Number of connections routed over the trunk that do not terminate at this node. |
| Terminated Connection Statistics | Description |
|---|---|
Voice terminated | Number of voice connections terminated at this node that are routed over his trunk. |
Data terminated | Number of data connections terminated at this node that are routed over this trunk. |
Frame relay terminated | Number of Frame Relay connections terminated at this node that are routed over this trunk. |
Num voice offhook | Number of voice connections off-hook that are terminated at this node and routed over this trunk. |
Connection Type | Voice connection types: c, a, v, p or t. |
Connection Num | Number of terminated voice connections of each type: c, a, v, p and t. |
Modem On | Number of terminated connections with modem detected. |
Modem V.25 | Number of terminated connections with V.25 modem detected. |
VAD Enabled | Number of terminated connections with VAD enabled. |
Display trunk utilization
dsptrkutl <trunk number> [interval]
dspload, dspchhist, dsptrkhist
| Privilege | Jobs | Log | Node | Lock |
1-6 | No | No | IGX, BPX | Yes |
dsptrkutl 5.3
Display trunk utilization for port 3 of the BNI in slot 5. The node is a BPX.
bootzilla TN SuperUser BPX 8620 9.2 Aug. 27 1998 15:21 GMT
TRK 5.3 Utilization Display
Elapsed time (seconds) 160.1 Terminated Connection Statistics
Total cells transmitted 30 Voice terminated 0
Overall cell rate (cells/sec) 0 Data terminated 0
Overall utilization 0% ATM and FR terminated 1584
Peak interval utilization 1% Num voice OffHook 0
Last interval (seconds) 5.1
Interval cells generated 0 Connection Modem Modem VAD
Interval cell rate (cells/sec) 0 Type Num On V.25 Enabled
Interval utilization 0% c 0 0 0 0
a 0 0 0 -
Terminated Connections 1584 v 0 0 0 0
Via Connections and Groups 0 p/t 0 0 0 -
This Command: dsptrkutl 5.3
Hit DEL key to quit:
| Parameter | Description |
|---|---|
trunk number | Specifies the number of the trunk in the format slot.trunk. If the card has only one trunk, you can enter just the slot. |
| Parameter | Description |
|---|---|
interval | Specifies the number of seconds between screen updates. The range is 1-60. The default is 5. |
Prints the connection routes for channels on the IGX node. It uses the same syntax and prints the same information as the dsprts command. See the dsprts description for output information.
Print connection routes
prtrts [start_channel] [dest_nodename]
dsprts
| Privilege | Jobs | Log | Node | Lock |
1-6 | Yes | No | IGX | Yes |
prtrts
Print connection routes.
None available as command produces hardcopy.
| Parameter | Description |
|---|---|
start channel | Specifies the channel with which to print. Channels are printed in numeric order. If no starting channel is specified, the display begins with the first connected channel. Start channel is specified in one of the following formats: slot.channel voice connection. slot.port data connection. slot.port.DLCI Frame Relay connection. remote node.groupname Frame Relay connection group. |
destination node name | Specifies the printing of connection routes from only the local node to the current node. Without a specified node name, the printout shows connections from the local node to all other nodes. |
Ups (activates) a connection, bundle of connections, group of connections, or all connections with a COS or COS range. When a connection is upped, the system tries to route. If the connection cannot immediately be routed, the connection is failed and generates a major alarm. The State display column in an upcon or dspcons screen has the following meaning:
| (routed). |
| (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. |
| (not routed, but trying). |
Up a connection
upcon {<group | local_chan(s)> | COS <cos_range>}
dncon, dspcon, dspcons
| Privilege | Jobs | Log | Node | Lock |
1-2 | Yes | Yes | IGX | Yes |
upcon 5.1
Activate connections 5.1.
alpha TRM YourID:1 IGX 8420 9.2 Aug. 23 1998 11:33 PST
Local Remote Remote Route
Channel NodeName Channel State Type Compression Code Avoid COS O
5.1 beta )25.1 Ok 256 7/8 0 L
9.1.100 gamma 8.1.200 Ok fr 0 L
9.1.200 gamma 8.1.300 Ok fr 0 L
9.2.400 beta 19.2.302 Ok fr(Grp) 0 L
14.1 )gamma 15.1 Ok v 0 L
Last Command: upcon 5.1
Next Command:
upcon 9.1-4
Activate a range of connections 9.1-4
upcon alpha
Activate a Frame Relay group connection
upcon 9
Activate all downed connections with a COS of 9
upcon cos 9-12
Activate all downed connections with a COS of 9-12
| Parameter | Description |
|---|---|
group or channel(s) | Specifies a group, a channel, or a range of channels to activate. |
COS /cos range | Specifies the COS or COS range. The range is 0-15. |
Posted: Mon Aug 19 21:30:56 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.