|
|
This chapter describes the commands that let you improve the use of network resources. The commands consist primarily of route optimization commands. The chapter begins with a generic description of command syntax.
A command can include parameters that are keyword-driven or position-dependent.
For position-dependent parameters, you must type parameters in the order they appear in the syntax description or on-line help. To create a logical port, for example, the position-dependent syntax is:
addport <ifNum> <bay.line> <guaranteedRate> <maxrate> <sctID> <ifType> [vpi]
For a keyword-driven parameter, a keyword must precede the value. The keyword is preceded by a dash and followed by the parameter (-timeout <secs>, for example). The order you enter keyword-driven parameters does not matter—although any preceding or succeeding, position-dependent parameters must appear as they do in the command syntax description.
In the following syntax example, the command is to delete more than one connection at a time. The mandatory, position-dependent connection identifier consist of a logical port (ifNum) and the VPI and VCI of the first connection to delete. After the connection identifier, the line shows two optional, keyword-driven parameters. These keyword-driven parameters let you enter the number of connections to delete and specify verbose mode:
delcons <ifNum> <vpi> <vci> [-num <num. conns to del>] [-verbose < 1 | 0 >]
When you enter a command with the current version of the product, you must type all intended arguments before you press the Return key or Enter key.
If you press the Return key or Enter key with incorrect parameters or no parameters (if the command requires parameters), a message displays the syntax and parameter ranges. The returned message may also suggest what the problem is. For example, the message may warn of too few parameters. No error messages or warnings appear until you complete the command.
The model number of an AXSM identifies the line speed, line count, and number of bays (see Table 8-1.) Note that the number of lines applies to an individual back card, so the total number of lines supported by the front card equals the highest line number times the number of bays. The OC-48 card AXSM-1-2488 has the lowest number of lines—one. The highest number of lines exist on the AXSM-16-155 and AXSM-16-T3E3—16, as the name indicates.
The MGX 8850 node use the concept of a bay. The bay refers to the upper or lower location of a single-height card. (The switch has a double-height card cage, so a single-height back card necessarily occupies either an upper or lower position.)
The T3/E3, OC-3, and OC-12 versions of the AXSM can have two back cards, one in bay 1 (upper location of the back slot) and the second in bay 2 (lower slot). The MGX-AXSM-1-2488 (OC-48 AXSM) can have a back card in bay 1 only. For further descriptions and illustrations of the card sets, refer to Cisco MGX 8850 Hardware Installation, Rel 2.0.
| Front Card | Speed | Lines | Bays |
|---|---|---|---|
AXSM-1-2488 | OC-48 | 1 | 1 |
AXSM-4-622 | OC-12 | 1-4 | 1-2 |
AXSM-16-155 | OC-3 | 1-8 | 1-2 |
AXSM-16-T3E3 | T3 or E3 | 1-8 | 1-2 |
The SVC and SPVC connection capacities for the front card, back card, and physical lines appear in Table 8-2 and Table 8-3. The capacity of a single AXSM card is greater than that of the node itself. Nevertheless, the tables provide these maximums when you plan the use of commands such as addrscprtn, addcon, and any other command where you may want to know the capacity of the configured item to support connections.
| Front Card | SVC | SPVC |
|---|---|---|
AXSM-1-2488 | 128 K | 64 K |
AXSM-4-622 | 128 K | 64 K |
AXSM-16-155 | 128 K | 64 K |
AXSM-16-T3E3 | 128 K | 64 K |
| Card Type | Back Card Maximum | Physical Line Maximum |
|---|---|---|
OC-48c | 128 K | 64 K |
OC-12c | 64 K | 32 K |
OC-3c | 64 K | 32 K |
T3 | 64 K | 64 K |
E3 | 64 K | 64 K |
The Private Network-to-Network Interface (PNNI) control protocol and the AXSM use different formats to identify the same elements. This section describes the format of these elements in the PNNI and AXSM contexts and how they correspond to each other. When you configure or view items on the CLIs of different cards, you often need to specify it in PNNI as well as the AXSM. For example, when you configure a PNNI port on the CLI of the PXM45, you also need to configure a port on the CLI of the AXSM. Furthermore, when you display a connection on the AXSM, you identify that same connection using a different format on the PXM45 CLI. For specific examples of these parallel actions, see the Cisco MGX 8850 Software Configuration Guide, 2.0.
 |
Note Apart from the way PNNI and the lower levels of logic identify the same element, the issue of configuration sequence needs explanation. When you configure logical ports—as just one example—you must complete certain tasks on the AXSM CLI before and after related PNNI tasks. This manual describes prerequisites for certain commands, but refer to the Cisco MGX 8850 Software Configuration Guide, 2.0 for more details of this sequence. |
The AXSM items that you identify for addressing purposes are:
A logical port on an AXSM (and its CLI) always uses the label ifNum. For a UNI and NNI interface, a one-to-one correspondence exists between a logical port and a physical line. For virtual trunks, you can configure multiple ports for a line.
The maximum number of logical ports on an AXSM is 60 regardless of the AXSM model or the number of AXSM back cards. The range for ifNum is 1-60, also regardless of the whether the interface type is UNI. NNI, or VNNI.
The elements of a port in the PNNI protocol are as follows:
The PNNI port identifier (portid) appears on only the PXM45 CLI. Throughout this manual, portid refers the following format:
[shelf.]slot[:subslot].port[:subport]
The portid consists of a series of mandatory and optional elements. Note the period or colon associated with each optional element inside the square brackets. For the correspondence between a PNNI port and the AXSM elements, see Table 8-4.
| PNNI port | AXSM |
|---|---|
Shelf | N/A |
Slot | Slot |
Subslot | Bay (for back cards |
Port | Line |
Subport | Logical port (ifNum) |
An example of a PNNI port identifier is 1:2.1:3. This portid corresponds to slot 1, bay 2, line 1, and logical port 3 on an AXSM.
Configure Route Optimization
Configure periodic route optimization to improve bandwidth utilization. This type of optimization is a type of connection grooming. To automate route optimization, cnfrteopt lets you specify an interval between new optimization cycles—every 2 hours, for example. (To force immediate route optimization, use the optrte command.)
You can specify a time period for optimization to minimize any disruption. For example, you could specify that the switch starts grooming a range of SPVCs for one hour at midnight. Note, however, that route optimization is a background process and does not attempt to optimize all possible connections at once. The load created by route optimization is extremely small and cannot cause congestion.
The nature of SPVCs provides a reason for periodic grooming: during the course of daily operation, better routes may become available. The determining factor for a better route is the maximum cost (maxcost). See the addcon description for details about the maxcost parameter.
Note the following characteristics of route optimization:
By default, the PXM45 calculates that a route is better if its routing cost is 30% less than the current cost. You can change this cost threshold through the cnfrteoptthld command.
The following briefly characterizes the defaults for cnfrteopt:
cnfrteopt
<portid>
[{enable | disable}]
[-range <starting-vpi/vci..ending-vpi/vci>]
[-interval <interval>]
[-tod <start-time..end-time>]
portid | Port identifier has the format [shelf.]slot[:subslot].port[:subport]. |
enable | disable | Enables or disables route optimization. The default is disabled, but if grooming is operational and you want to disable it, you must execute cnfrteopt and enter "disable." |
-range | Keyword that specifies a range of connections for grooming. Use the notation as it appears on the syntax line: type a slash between the VPI and VCI and two dots with no spaces between the starting and ending values. For example, 100/1000..200/10000 is a valid parameter to follow the -range keyword. The ranges are:
The VPI of the starting SPVC must be less than the ending VPI, and the starting VCI must be less than the ending VCI. Note that the default range is all connections on the port specified by portid. Therefore, if you want to groom all connections on the portid, simply leave out the -range command delineator. |
-interval | Keyword that specifies the frequency at which grooming begins. The units of measure are minutes. The range is 10-10000. The default is 60. Counting starts at one of two moments:
If the interval is less than half the amount of time specified by the start-time..end-time parameter, route optimization may begin more than once during the time period. For example, if the periods of optimization are two hours beginning at midnight and 4:00 AM and the interval is one hour, route optimization could occur two to four times per day. |
-tod | Keyword that specifies the time to start and stop grooming. The format is a 24-hour clock: 00:00-23:59. The default for both start and end-time is 00:00. Use the notation as it appears in the Syntax section: type two dots with no spaces between the starting and ending times. |
PXM45
cnfrteoptthld, optrte, dsprteoptcnf, dsprteoptstat
Log: log | State: active | Privilege: GROUP1 |
For logical port 2 on the lower bay of the service module in slot 1, configure 1 hour of connection grooming starting between 1:00 and 3:00 AM local time. The range of SPVCs is 100.1000 through 100.10000.
cnfrteopt 1:2.1:2 enable -range 100/1000..100/10000 -interval 60 -tod 01:00..03:00
Configure Route Optimization Threshold
Configure a threshold the system uses to decide whether one route is a sufficient improvement to warrant re-routing. The criterion for selecting a new route is a threshold in the form of the percent of difference in route cost.
The default for route optimization is a 30% reduction of the cost of a route. Using this mechanism, the PXM45 selects a given route if it costs 30% less than the cost of the current route. With cnfrteoptthld, you can change the percentage of routing cost-improvement.
cnfrteoptthld
<percent>
percent | The percent of reduction in routing cost that triggers re-routing. The range is 5-100. The default is 30. |
PXM45
cnfrteopt, optrte, dsprteoptcnf, dsprteoptstat
Log: log | State: active | Privilege: GROUP1 |
Change the re-routing threshold to a 20% reduction in the route cost.
pinnacle.7.PXM> cnfrteoptthld 20
Display Load
Display the current level of usage of various parameters on a partition. To convey a picture of what is available on a resource partition, the display shows the configured bandwidth and connection numbers and what has actually been utilized.
AXSM
dspload
<ifNum>
<partId>
ifNum | The logical port number. On the AXSM, the range is 1-60. |
partId | The partition identifier. The range is 1-20. If necessary, use dsprscprtns to see the existing partitions. |
dsprscprtn, addcon, dspcons, dspcon, cnfcon
Log: nolog | State: active, standby State | Privilege: ANYUSER |
Display the load on partition number 1 on logical port 1. The display shows that very little of the available connections and bandwidth have been used. Also, no exceptions have been recorded.
node19.1.AXSM.a > dspload 1 1
+--------------------------------------------+
| I N T E R F A C E L O A D I N F O |
+--------------------------------------------+
| Maxm Connections : 0010000 |
| Guaranteed Connections:0001000 |
| Maximum Bandwidth : 1412831 |
| Guaranteed Bandwidth : 1412831 |
| Available Igr Connections: 0009997 |
| Available Egr Connections: 0009997 |
| Available Igr Bandwidth : 1411931 |
| Available Egr Bandwidth : 1411931 |
+--------------------------------------------+
| E X C E P T -- V A L U E S |
+--------------------------------------------+
| SERV-CATEG | VAR-TYPE | INGRESS | EGRESS |
+--------------------------------------------+
+--------------------------------------------+
Display Route Optimization Configuration
Display the current configuration for route optimization. The configuration itself originates with the cnfrteopt command. The dsprteoptcnf display shows the following:
PXM45
dsprteoptcnf
This command takes no parameters.
cnfrteopt, opte, dsprteoptstat, cnfrteoptthld
Log: nolog | State: active, standby state | Privilege: ANYUSER |
Display the current route optimization for the switch. No optimization has been configured on any ports.
pop20two.7.PXM.a > dsprteoptcnf Configuration of Route Optimization: Percentage Reduction Threshold: 30 Port Enable VPI/VCI Range Interval Time Range 1:2.1:2 no 1:2.2:3 no
Display Route Optimization Status
Display the current percent of route cost reduction. This percent is a threshold that the PXM45 requires to determine that one route costs sufficiently less to warrant re-routing. The percent applies to all connections on the node. The system default is 30%, but you can configure a percent through the cnfrteoptthld command. For more details on route optimization, see the cnfrteopt description.
PXM45
dsprteoptstat
This command takes no parameters.
cnfrteopt, cnfrteoptthld, optrte, dsprteoptstat
Log: nolog | State: active, standby | Privilege: ANYUSER |
Display the current route optimization status for the switch. The display shows the default optimization of 30%.
pop20two.7.PXM.a > dsprteoptstat Configuration of Route Optimization: Percentage Reduction Threshold: 30
Optimize Routes
Force immediate optimization of either a single SPVC route, a range of SPVCs, or all SPVCs on a particular port. (Connection grooming is a common word for optimization.)
Re-routing depends on a reduction in the cost of the route. If the PXM45 can find a route with sufficiently lower cost, the SPVC is de-routed then re-routed. The system default is a 30% reduction in the cost but is configurable through the cnfrteoptthld command. For a detailed explanation of route optimization, see the description of cnfrteopt.
PXM45
optrte <portid>
[-vpi <vpi>]
[-vci <vci>]
[-range <starting-vpi/vci..ending-vpi/vci>]
portid | Port identifier has the format [shelf.]slot[:subslot].port[:subport]. |
-vpi | Keyword that specifies the vpi range: 0-4095. |
-vci | Keyword that specifies the vci range: 32-65535. |
-range | Keyword that specifies the range of connections for grooming. The VPI of the starting SPVC must be less than the ending VPI, and the starting VCI must be less than the ending VCI. Use the notation as it appears on the syntax line: type a slash between the VPI and VCI and two dots with no spaces between the starting and ending values. For example, 100/1000..200/10000 is a valid parameter to follow the -range keyword. The ranges are:
Note that the default range is all connections—on the entity specified by portid. Therefore, if you want to groom all connections on the portid, simply leave out the -range command delineator. |
cnfrteopt, cnfrteoptthld, dsprteoptcnf, dsprteoptstat
Log: log | State: active | Privilege: GROUP1 |
Immediately find a better route for the SPVC with vpi.vci 1000.50000 on portid 1:2.1:1
pop20two.7.PXM.a > optrte 1000 50000
Route Show
Show the current IP routing of the network layer of the operating system.
PXM45
routeShow
routestatShow
Log: nolog | State: active, standby | Privilege: ANYUSER |
Display the current IP routing of the network layer of the operating system.
pinnacle.8.PXM.a > routeShow ROUTE NET TABLE destination gateway flags Refcnt Use Interface ------------------------------------------------------------------------ 0.0.0.0 172.29.23.149 1 1 21778 lnPci0 0.0.0.0 172.29.23.1 3 0 2755 lnPci0 172.1.1.0 172.1.1.149 1 0 0 atm0 172.29.23.0 172.29.23.149 1 2 5275 lnPci0 ------------------------------------------------------------------------ ROUTE HOST TABLE destination gateway flags Refcnt Use Interface ------------------------------------------------------------------------ 0.0.0.0 0.0.0.0 5 0 0 sl0 127.0.0.1 127.0.0.1 5 1 0 lo0 172.29.23.3 172.1.1.149 5 0 3555 atm0 172.29.23.5 172.1.1.149 5 0 3304 atm0 172.29.23.7 172.1.1.149 5 0 3335 atm0 171.71.29.18 172.1.1.149 5 0 3304 atm0 172.29.23.18 172.1.1.149 5 0 3304 atm0 172.29.23.28 172.1.1.149 5 0 6127 atm0 172.29.23.29 172.1.1.149 5 1 6065 atm0 171.71.29.32 172.1.1.149 5 0 5842 atm0 171.71.29.44 172.1.1.149 5 0 3304 atm0 172.29.23.53 172.1.1.149 5 0 3304 atm0 171.71.29.59 172.1.1.149 5 0 3304 atm0 171.71.28.126 172.1.1.149 5 0 3309 atm0 ------------------------------------------------------------------------ pinnacle.8.PXM.a >
Show Routing Statistics
Use the routestatShow command to view the current IP routing statistics for the network layer of the operating system.
PXM45
routestatShow
routeShow
Log: nolog | State: active, standby | Privilege: ANYUSER |
Display the current IP routing statistics for the network layer of the operating system
pinnacle.8.PXM.a > routestatShow
routing:
0 bad routing redirect
0 dynamically created route
0 new gateway due to redirects
0 destination found unreachable
11095 uses of a wildcard route
pinnacle.8.PXM.a >
Posted: Mon Oct 2 19:33:26 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.