Feedback
Table Of Contents
Position-Dependent and Keyword-Driven Parameters
Connection Capacities of the AXSM
Identifying Physical and Logical Elements
Network Optimization Commands
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.
Position-Dependent and Keyword-Driven Parameters
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 used 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 >]
Command Entry
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.
Identifying the AXSM Models
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.
An MGX 8850 or MGX 8950 node uses 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, Release 2.1 or Cisco MGX 8950 Hardware Installation, Release 1.0.
Connection Capacities of the AXSM
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.
Table 8-2 Maximum Connections by Connection Type and Front Card
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
Table 8-3 Maximum Connections on Back Cards and Lines
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
Identifying Physical and Logical Elements
The Private Network-to-Network Interface (PNNI) control protocol and the service modules use different formats to identify the same entity. For example, the format of a logical port that you enter on an AXSM is different from the format you would enter on the PXM45. This section describes these formats in the PNNI and AXSM contexts and how they correspond to each other. The parallel actions of configuring or displaying logical elements on different cards is broadly illustrated in the Cisco
MGX 8850 and MGX 8950 Switch Software Configuration Guide, Release 2.1.Apart from the way PNNI and the lower levels of logic identify the same element, the sequence of commands also needs explanation. When you configure logical ports—for just one example—you must complete certain tasks on the AXSM CLI before or after related PNNI tasks. For certain commands, this manual lists prerequisite commands or tasks. For more details on the sequence of tasks, refer to the Cisco
MGX 8850 and MGX 8950 Switch Software Configuration Guide, Release 2.1, for more details of this sequence.AXSM Format
On a service module, you identify the follow when you provision the capabilities of the card:
•
Slot
•
•
•
•
•
Not all of these elements correspond to elements you specify on the PXM45. Subsequent paragraphs describe only the common elements that are visible on the CLI of the PXM and the service module. The preceding elements are further defined in the Cisco MGX 8850 and MGX 8950 Switch Software Configuration Guide, Release 2.1.
For a UNI or NNI, one logical interface (or logical port) exists per physical line. For virtual network to network interfaces (VNNIs), you can configure multiple ports on a line. The maximum number of logical ports on an AXSM is 60 or 32 on an AXSM-E, regardless of the number of AXSM back cards or whether the interface type is UNI, NNI, or VNNI.
PNNI Format
The PNNI controller requires the following format to identify a physical port:
[shelf.]slot:subslot.port:subport
The PNNI physical port identifier (physical port ID) consists of a series of mandatory elements. Note the period or colon associated with each element inside the square brackets. The elements of the physical port ID are as follows:
•
•
•
•
•
For each physical port number, PNNI also generates a logical port number as an encrypted form of the physical port number. The logical port number appears as an unformatted numerical string. For example, a PNNI physical port ID may have the form 1:1.2:2, so the PNNI logical port number would be 16848898. Where needed, the descriptions in the PNNI command chapter define the need for this logical port number. (This section does not define a PNNI logical port number, nor does it describe the correspondence between an AXSM port and a PNNI logical port number.) For the correspondence between a PNNI physical port and the port identifier on an AXSM, see Table 8-4.
Table 8-4 Mapping PNNI Port ID to AXSM Elements
Shelf
N/A
Slot
Slot
Subslot
Bay (for upper or lower back card)
Port
Line
Subport
Logical interface (or port)
As the table shows, a port from the PNNI side is a line on the AXSM, and a subport from the PNNI side is a logical interface (or logical port) on an AXSM. An example of a PNNI physical port identifier is 1:2.1:1. This portid corresponds to an AXSM, with the following particulars:
Slot 1
Bay 2
Line 1
Logical interface 1 (or logical port 1)
cnfpnportloscallrel
Configure PNNI Port Loss of Signal Call Release
The cnfpnportloscallrel command lets you shut off the standard delay for rerouting calls on a port when the system detects loss of signal (LOS) on a port.
When the system detects LOS on an NNI link, the switch does not immediately tear down the calls on the link—in case the break is momentary. By default, the system waits for the SSCOP "no-response" and T309 timers to time out before it releases calls on the broken link. The default values for these timers are 30 seconds and 10 seconds, respectively. The system-level assumption (and therefore the default for cnfpnportloscallrel) is to retain all the calls for a temporary loss of connectivity, but this can also have the effect of delaying the rerouting of connections. The cnfpnportloscallrel command lets you direct the system to reroute calls without delay on a particular port.
Cards on Which This Command Runs
PXM45
Syntax
cnfpnportloscallrel <portid> <yes|no>
Sybtax Description
portid
Identifies a PNNI physical port. The format is slot:subslot.port:subport. For a description of each field, see the section, "PNNI Format," at the beginning of the chapter.
yes | no
Specifies whether immediate call release is enabled upon LOS. To enable this feature—to remove the standard reroute delay—type "yes."
Default: no.
Related Commands
dsppnportloscallrel
Attributes
Example
Enable call release upon LOS for port 3:1.1:1, then confirm its status.
8850_NY.8.PXM.a > cnfpnportloscallrel 3:1.1:1 yes
8850_NY.8.PXM.a > dsppnportloscallrel 3:1.1:1
Call release on Los :enabled
cnfrrtparm
Configure Reroute Retry Parameters—configures the waiting time intervals for rerouting a failed SPVC.
The cnfrrtparm command allows you configure the time periods that the switch waits between each reroute retry attempt.
When an SPVC fails, the system immediately attempts to reroute the connection. If the first reroute attempt fails, the switch keeps trying to reroute the connection according to the slow retry interval (-slowtmr) and the fast retry interval base(-fasttmrbase).
The fast retry interval base is an incremental value (in 100-millisecond units) that is incremented each time the switch attempts to reroute the connection and fails. The switch then waits the incremented amount of time before it attempts to reroute the connection again. The fast retry interval base continues to increment after each reroute attempt until it is equal to the slow retry interval value or until the reroute succeeds.
The slow retry interval is a fixed value (in seconds) that occurs between all subsequent reroute attempts. After the fast retry interval base reaches the slow retry interval, the switch attempts to reroute the connection at the rate of the slow retry interval. No limit exists for the number of reroute attempts once the slow retry interval begins.
For example, if the fast retry interval base is 50 100-millisecond intervals (5 seconds) and the slow retry interval is 300 seconds (5 minutes), the switch attempts to reroute the connection 5 seconds after the first attempt, 10 seconds after the second attempt, 15 seconds after the third attempt, and so on until the fast retry interval base equals 300 seconds (5 minutes). After that, the switch continues to attempt to reroute the connection every 5 minutes or until the reroute is successful.
Cards on Which This Command Runs
PXM45
Syntax
cnfrrtparm [-slowtmr <slow retry interval>] [-fasttmrbase <fast retry interval base]Syntax Description
Related Commands
dsprrtparm
Attributes
Example
Set the slow timer to 300 second intervals and the fast timer base to 7 seconds (70 x 100 milliseconds). Check the results by executing dsprrtparm.
8850_NY.7.PXM.a > cnfrrtparm -slowtmr 300 -fasttmrbase 708850_NY.7.PXM.a > dsprrtparmGlobal SPVC Retry Parameters:--------------------------------Slow Retry Interval: 300 secFast Retry Interval Base: 70 (in 100 msec)8850_NY.7.PXM.a >
cnfrteopt
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. (To force immediate route optimization, use the optrte command.) The load created by route optimization is extremely small and cannot cause congestion.
You can choose a time period for optimization so that disruption is minimal. For example, you could specify that the switch starts grooming a range of SPVCs for one hour at midnight. Note, that route optimization is a background process and does not attempt to optimize all possible connections at once.
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. The PNNI protocol identifies this maximum cost by another name: administrative weight (AW).
Note
Usage Guidelines
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:
•
•
•
•
Cards on Which This Command Runs
PXM45
Syntax
cnfrteopt <portid> [{enable | disable}] [-range <starting-vpi/vci..ending-vpi/vci>]
[-interval <interval>] [-tod <start-time..end-time>]Syntax Description
portid
Identifies a PNNI physical port. The format is slot:subslot.port:subport. For a description of each field, see the section, "PNNI Format," at the beginning of the chapter.
enable | disable
Enables or disables route optimization. The default is disabled, but if grooming is operational and you want to disable it, run cnfrteopt and enter "disable."
-range
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 entry. The ranges are as follows:
•
•
In the variable parameter starting-vpi/vci..ending-vpi/vci, the starting and ending VPIs are independent of the starting and ending VCIs. For example, -range 3/40..5/50 means the following:
Optimize all SPVCs that have a VPI in the range 3-5 and a VCI in the range 40-50.
This example range could include 3/40, 3/45, 4/45, 5/45 and 5/50 but not 4/60.
Note that the default for -range is all connections on the PNNI port specified by portid. Therefore, to groom all connections on the port, leave out the -range parameter.
-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. If you execute cnfrteopt during the time specified by tod, the optimization cycle begins during the next time interval.
If the time for the node changes (by way of the cnftime command, for example), the node might skip one optimization cycle.
Note
Cards on Which This Command Runs
PXM45
Related Commands
cnfrteoptthld, optrte, dsprteoptcnf, dsprteoptstat
Attributes
Examples
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:00cnfrteoptthld
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.
Syntax
cnfrteoptthld <percent>
Syntax Description
percent
The percent of reduction in routing cost that triggers re-routing. The range is 5-100. The default is 30.
Cards on Which This Command Runs
PXM45
Related Commands
cnfrteopt, optrte, dsprteoptcnf, dsprteoptstat
Attributes
Example
Change the re-routing threshold to a 20% reduction in the route cost.
pinnacle.7.PXM> cnfrteoptthld 20dspconload
Display Connection Load—display the number of cells actually traversing the ingress and egress.
The dspconload command lets you see the current load on a connection. With the statistics provided by dspconload, you can determine whether the current load on the connection suggests a modification to the connection or possible troubleshooting.
Cards on Which This Command Runs
AXSM, AXSM-E
Syntax
dspconload <ifNum> <vpi> <vci>
Related Commands
dspcons, dspcon, dspload
Attributes
AXSM Example
Display the load on the connection with a VPI and VCI of 101 and 101, respectively, on logical port 3. In this case, no traffic currently exists on the connection.
MGX8850.10.AXSM.a > dspconload 3 101 101Getting the stats. Please wait ...Ingress EgressCell rate (cps) : 0 0AXSM-E Example
Display the load on the connection with a VPI and VCI of 10 and 100, respectively, on logical port 1.
MGX8850.6.AXSME.a > dspconload 1 10 100Ingress Egress-------------------------------------- --------------------------------------All non-compliant cells : 0CLP1 non-compliant : 0CLP0 non-compliant : 0CLP0 -> CLP1 : 0Cells from port(Before policing) : 999 Cells to port : 999CLP0 from port : 999 CLP0 to port : 999CLP1 from port : 0 CLP1 to port : 0EOF from port : 0 EOF to port : 0EFCI1 from port : 0 EFCI1 to port : 0RM to port : 0Cells to network : 999 Cells from network : 999CLP0 to network : 999 CLP0 from network : 999CLP1 to network : 0 CLP1 from network : 0EFCI1 to network : 0 EFCI1 from network : 0Cells discarded in qe : 0 Cells discarded in qe : 0CLP0 discarded in qe : 0 CLP0 discarded in qe : 0CLP1 discarded in qe : 0 CLP1 discarded in qe : 0EOF discarded in qe : 0EFCI1 discarded in qe : 0VC queue depth : 0 VC queue depth : 0ACR (Valid for WFQ conns) : 1 ACR (Valid for WFQ conns) : 1OAM from port : 0 OAM to port : 0RM from port : 0RM to network : 0 RM from network : 0OAM to network : 0 OAM from network : 0OAM discarded in qe : 0 OAM discarded in qe : 0EFCI1 discarded in qe : 0RM discarded in qe : 0 RM discarded in qe :dspload
Display Load—displays maximum channels and bandwidth and available channels and bandwidth on a partition.
This command displays the configured maximum and guaratneed number of channels and the configured maximum and guaranteed bandwidth on a partition on a logical interface. It also displays the currently available number of channels and the currently available bandwidth on the partition.
This information can allow you to determine the throughput requirements for a partition and the actual resource utilization.
The output shows the configured bandwidth for user connections of all service classes.
The display also shows the load created by control VCs. The control VCs are of three types: SSCOP, PNNI-RCC, and ILMI (if ILMI is enabled). The bandwidth allocations for SSCOP and PNNI-RCC control VCs are configurable (see cnfpnctlvc.) The bandwidth for an ILMI VC is fixed, as follows: PCR=1000 cps; SCR=50cps; and MBS=1024 cells.
Card(s) on Which Command Executes
AXSM
Syntax
dspload <ifNum> <partId>
Syntax Description
Related Commands
dsprscprtn, addcon, dspcons, dspcon, cnfcon
Attributes
Example
Display the load on partition number 1 on logical port 1.
MGX8850.1.AXSM.a > dspload 1 1+--------------------------------------------+| I N T E R F A C E L O A D I N F O |+--------------------------------------------+| Maximum Channels : 0001000 || Guaranteed Channels : 0000000 || Igr Maximum Bandwidth : 0353208 || Igr Guaranteed Bandwidth : 0176604 || Egr Maximum Bandwidth : 0353208 || Egr Guaranteed Bandwidth : 0176604 || Available Igr Channels : 0000998 || Available Egr Channels : 0000998 || Available Igr Bandwidth : 0351708 || Available Egr Bandwidth : 0351708 |+--------------------------------------------+| E X C E P T -- V A L U E S |+--------------------------------------------+| SERV-CATEG | VAR-TYPE | INGRESS | EGRESS || VSI-SIG | Avl Chnl | 0000998 | 0000998 || CBR | Avl Chnl | 0000998 | 0000998 || VBR-RT | Avl Chnl | 0000998 | 0000998 || VBR-nRT | Avl Chnl | 0000998 | 0000998 || UBR | Avl Chnl | 0000998 | 0000998 || ABR | Avl Chnl | 0000998 | 0000998 |+--------------------------------------------+| VSI-SIG | Avl Bw | 0351708 | 0351708 || CBR | Avl Bw | 0351708 | 0351708 || VBR-RT | Avl Bw | 0351708 | 0351708 || VBR-nRT | Avl Bw | 0351708 | 0351708 || UBR | Avl Bw | 0351708 | 0351708 || ABR | Avl Bw | 0351708 | 0351708 |+--------------------------------------------+
dsppnportloscallrel
Display PNNI Port Loss of Signal Call Release
This command displays the enable status of the LOS call release feature. See cnfpnportloscallrel for a description of this feature.
Cards on Which This Command Runs
PXM45
Syntax
dsppnportloscallrel <portid>
Sybtax Description
portid
Identifies a PNNI physical port. The format is slot:subslot.port:subport. For a description of each field, see the section, "PNNI Format," at the beginning of the chapter.
Related Commands
cnfpnportloscallrel
Attributes
Example
First, confirm that LOS call release is disabled on port 3:1.1:1. Enable it, then confirm that it's enabled.
8850_NY.8.PXM.a > dsppnportloscallrel 3:1.1:1Call release on Los :disabled8850_NY.8.PXM.a > cnfpnportloscallrel 3:1.1:1 yes8850_NY.8.PXM.a > dsppnportloscallrel 3:1.1:1Call release on Los :enableddspportload
Display Port Load—display the current number of cells on a logical port.
The dspportload command can help you determine the current state of a port. Using the parameters displayed by dspcon, you can determine whether the current load on the port needs modification or troubleshooting.
Cards on Which This Command Runs
AXSM, AXSM-E
Syntax
dspportload <ifNum>
ifNum
The logical interface (or port) number.
For AXSM, the range is 1-60.
For AXSM-E, the range is 1-32.
Related Commands
dspports, dspport, cnfport
Attributes
Example
Display the load on logical port 1 on AXSM. In this case, no traffic currently exists on the connection.
MGX8850.10.AXSM.a > dspportload 1Getting the stats. Please wait ...Ingress EgressCell rate (cps) : 0 0Display the load on logical port 1 on AXSM-E.
Cupertino.6.AXSME.a > dspportload 1Interface Num : 1Egr Rcv Clp0 Cells : 1000Egr Rcv Clp1 Cells : 0Egr Clp0 Disc Cells : 0Egr Clp1 Disc Cells : 0Egr Xmt Clp0 Cells : 999Egr Xmt Clp1 Cells : 0Egr Rcv OAM Cells : 0Egr Rcv RM Cells : 0Egr Xmt EFCI Cells : 0Egr Rcv EFCI Cells : 0Egr Xmt OAM Cells : 0dsprrtparm
Display Reroute Parameters—displays the current values for two types of reroute intervals.
The dsprrtparm command shows the current slow interval time and fast timer base. See the description of cnfrrtparm for the function of these intervals.
Cards on Which This Command Runs
PXM45
Syntax
dsprrtparm
Syntax Description
This command takes no parameters.
Related Commands
cnfrrtparm
Attributes
Example
Display the current, global reroute parameters for SPVCs. The parameters are the defaults.
8850_NY.7.PXM.a > dsprrtparmGlobal SPVC Retry Parameters:--------------------------------Slow Retry Interval: 60 secFast Retry Interval Base: 50 (in 100 msec)
dsprteoptcnf
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:
•
•
•
•
•
Cards on Which This Command Runs
PXM45
Syntax
dsprteoptcnf
Syntax Description
This command takes no parameters.
Related Commands
cnfrteopt, opte, dsprteoptstat, cnfrteoptthld
Attributes
Example
Display the current route optimization for the switch. No optimization has been configured on any ports.
pop20two.7.PXM.a > dsprteoptcnfConfiguration of Route Optimization:Percentage Reduction Threshold: 30Port Enable VPI/VCI Range Interval Time Range1:2.1:2 no1:2.2:3 nodsprteoptstat
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.
Cards on Which This Command Runs
PXM45
Syntax
dsprteoptstat
Syntax Description
This command takes no parameters.
Related Commands
cnfrteopt, cnfrteoptthld, optrte, dsprteoptstat
Attributes
Example
Display the current route optimization status for the switch. The display shows the default optimization of 30%.
pop20two.7.PXM.a > dsprteoptstatConfiguration of Route Optimization:Percentage Reduction Threshold: 30optrte
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.
Cards on Which This Command Runs
PXM45
Syntax
optrte <portid> [-vpi <vpi>] [-vci <vci>] [-range <starting-vpi/vci..ending-vpi/vci>]
Syntax Description
portid
Identifies a PNNI physical port. The format is slot:subslot.port:subport. For a description of each field, see the section, "PNNI Format," at the beginning of the chapter.
-vpi
Keyword that specifies the vpi. The range is 0-4095.
-vci
Keyword that specifies the vci. The range is 32-65535.
-range
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 entry. The ranges are as follows:
•
•
In the variable parameter starting-vpi/vci..ending-vpi/vci, the starting and ending VPIs are independent of the starting and ending VCIs. For example, -range 3/40..5/50 means the following:
Optimize all SPVCs that have a VPI in the range 3-5 and a VCI in the range 40-50.
This example range could include 3/40, 3/45, 4/45, 5/45 and 5/50 but not 4/60.
Note that the default for -range is all connections on the PNNI port specified by portid. Therefore, to groom all connections on the port, leave out the -range parameter.
Related Commands
cnfrteopt, cnfrteoptthld, dsprteoptcnf, dsprteoptstat
Attributes
Example
Immediately find a better route for the SPVC with vpi.vci 1000.50000 on port 1:2.1:1.
pop20two.7.PXM.a > optrte -vpi 1000 -vci 50000routeShow
Route Show
Show the current IP routing of the network layer of the operating system.
Card(s) on Which Command Executes
PXM45
Syntax
routeShow
Related Commands
routestatShow
Attributes
Example
Display the current IP routing of the network layer of the operating system.
pinnacle.8.PXM.a > routeShowROUTE NET TABLEdestination gateway flags Refcnt Use Interface------------------------------------------------------------------------0.0.0.0 172.29.23.149 1 1 21778 lnPci00.0.0.0 172.29.23.1 3 0 2755 lnPci0172.1.1.0 172.1.1.149 1 0 0 atm0172.29.23.0 172.29.23.149 1 2 5275 lnPci0------------------------------------------------------------------------ROUTE HOST TABLEdestination gateway flags Refcnt Use Interface------------------------------------------------------------------------0.0.0.0 0.0.0.0 5 0 0 sl0127.0.0.1 127.0.0.1 5 1 0 lo0172.29.23.3 172.1.1.149 5 0 3555 atm0172.29.23.5 172.1.1.149 5 0 3304 atm0172.29.23.7 172.1.1.149 5 0 3335 atm0171.71.29.18 172.1.1.149 5 0 3304 atm0172.29.23.18 172.1.1.149 5 0 3304 atm0172.29.23.28 172.1.1.149 5 0 6127 atm0172.29.23.29 172.1.1.149 5 1 6065 atm0171.71.29.32 172.1.1.149 5 0 5842 atm0171.71.29.44 172.1.1.149 5 0 3304 atm0172.29.23.53 172.1.1.149 5 0 3304 atm0171.71.29.59 172.1.1.149 5 0 3304 atm0171.71.28.126 172.1.1.149 5 0 3309 atm0------------------------------------------------------------------------pinnacle.8.PXM.a >routestatShow
Show Routing Statistics
Display statistics for the current IP routing in the network layer of the system.
Card(s) on Which Command Executes
PXM45
Syntax
routestatShow
Related Commands
routeShow
Attributes
Display the current IP routing statistics.
pinnacle.8.PXM.a > routestatShowrouting:0 bad routing redirect0 dynamically created route0 new gateway due to redirects0 destination found unreachable11095 uses of a wildcard routepinnacle.8.PXM.a >rrtcon
Re-route Connection—force the system to re-route a connection
The rrtcon command lets you trigger the immediate re-routing of a connection.
Card(s) on Which Command Executes
AXSM, AXSM-E
Syntax
rrtcon <ifNum> <vpi> <vci>
Syntax Description
Related Commands
dspcons, dspcon
Attributes
