SPVC commands--Command Ref. for MGX8850, rel.2.0.10

Table Of Contents

SPVC Commands

Position-Dependent and Keyword-Driven Parameters

Command Entry

Identifying the AXSM Models

Connection Capacities of the AXSM

Identifying Physical and Logical Elements

AXSM Format

PNNI Format

addcon

Usage Guidelines

Traffic Parameters

Routing Parameters

Frame Discard

Local-Only Parameters

clrpncon

clrpnconstats

cnfabr

cnfabrtparmdft

cnfcdvtdft

cnfcon

Usage Guidelines

Traffic Parameters

Routing Parameters

Frame Discard

Local-Only Parameters

cnfconsegep

cnfmbsdft

cnfoamsegep

delcon

delcons

delconsegep

dncon

dspabrtparmdft

dspcdvtdft

dspcon

dspconinfo

dspcons

dspconsegep

dspmbsdft

dsppncon

dsppncons

dsppnconstats

upcon

upport

SPVC Commands

---

This chapter describes the commands that apply to semi-permanent virtual circuits (SPVCs). These commands allow you to add, delete, configure, display status, and specify statistics for SPVCs. The commands include the following areas:

•Adding a connection

•Modifying an existing connection

•Deleting a connection

•Display one connection or all connections

•Downing and upping a connection in the course of maintenance or troubleshooting

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

Table 7-1 Valid Line Numbers and Number of Bays for AXSM Card Types

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

Connection Capacities of the AXSM

The SVC and SPVC connection capacities for the front card, back card, and physical lines appear in Table 7-2 and Table 7-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 7-2 Maximum Connections by Connection Type and Front Card

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

Table 7-3 Maximum Connections on Back Cards and Lines

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

Identifying Physical and Logical Elements

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 PXM-45, 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 PXM-45 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.

---

AXSM Format

The AXSM items that you identify for addressing purposes are:

•Slot

•Bay

•Line

•Logical port

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.

PNNI Format

The elements of a port in the PNNI protocol are as follows:

•A shelf number. The shelf is always 1 for the current product and so is usually omitted.

•The slot number of the front card.

•Subslot is the number of the bay where the back card resides. This number is 1 or 2. Because the default is 1, subslot is frequently omitted.

•Port is the physical line.

•Subport corresponds to the logical port (ifNum) on the AXSM.

The PNNI port identifier (portid) appears on only the PXM-45 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 7-4.

Table 7-4 Mapping PNNI Port ID to AXSM Elements

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.

addcon

Add Connection

Adds a logical connection as an SPVC on a service module. An AXSM front card can support a maximum of 64K SPVCs. This command does not apply to SVCs.

Before Adding a Connection

Before you can add an SPVC, the following tasks must have been completed:

1. The switch must have a network controller (see addcontroller description).

2. A physical line must be active. Use the upln command or the CiscoView application.

3. At least one logical port must exist on the active physical line. Use the addport command or the CiscoView application to create the port. If necessary, modify the port through cnfport.)

4. At least one resource partition must exist on the logical port. Use addrscprtn or the CiscoView application. The resource partition should be associated with the controller added in step 1.

Adding a Connection

Adding a connection requires you first to provision a slave endpoint. Subsequently, you again execute addcon to provision a master endpoint. The master endpoint of the connection initiates the routing of the call and can be viewed as the "calling" party. The slave endpoint is the called endpoint. The following are characteristics of this master-slave arrangement:

•When you add a slave endpoint, the system returns a slave endpoint identifier. You subsequently need to provide this slave endpoint identifier when specifying the master endpoint.

•When you add the master endpoint, you must provide the slave endpoint identifier. (A copy and paste operation is probably more convenient than writing down the slave endpoint identifier.) After you finish adding the master endpoint, the switch starts routing the connection.

To modify the bandwidth parameters or configure usage parameter control (UPC), use cnfcon for all service types. In addition, ABR connections require more configurable parameters for implementing closed loop control. Use cnfabr to configure the ABR parameters.

Usage Guidelines

This section details about the application of certain addcon parameters. For example, a parameter may require you to specify it at both ends of a connection.

Traffic Parameters

Traffic parameters such as PCR, SCR, MBS are entered at both the master and slave endpoints for both the forward and reverse directions. Be sure that the value entered as "local" on one end is equal to the value entered as "remote" on the other end. For example, the lpcr on the slave endpoint should be same as the rpcr on the master endpoint and vice versa when you provision the connection at the other end. If you modify traffic parameters after creating an SPVC, you just modify them at both the master endpoint or the slave endpoint.

Traffic parameters such as CDV, CTD are entered at both the master and slave endpoints for both the forward and reverse directions. However, the values of these parameters entered at the slave end are ignored during call setup. Therefore, you can specify the lcdv, rcdv, lctd and rctd options at the master end only.

Routing Parameters

The routing parameter maxcost (specified using -mc option) need to be entered at the master endpoint only. The values of this parameters entered at the slave end is ignored and not considered during call setup.

Frame Discard

For the parameter frame discard (specified using -frame option), you need to enter it at only the master endpoint. This parameters has no significance at the slave end.

Local-Only Parameters

The parameters CDVT, stats enable, cc enable (specified using -cdvt, -stat, -cc) are significant only at the endpoint where you enter them. Therefore, they can be different at each end of the connection.

Card(s) on Which Command Executes

AXSM

Syntax

addcon
<ifNum>
<vpi>
<vci>
<service type>
<mastership>
[-slave <NSAP.vpi.vci>]
[-lpcr <local PCR >]
[-rpcr <remote PCR>]
[-lscr <local SCR>]
[-rscr <remote SCR>]
[-lmbs <local MBS>]
[-rmbs <remote MBS>]
[-cdvt <local CDVT>]
[-lcdv <local maxCDV>]
[-rcdv<remote maxCDV>]
[-lctd <local maxCTD>]
[-rctd <remote maxCTD>]
[-cc <OAM CC Cnfg>]
[-stat <Stats Cnfg>]
[-frame <frame discard>]
[-mc <maximum cost>]

Syntax Description

For the applicable parameters, the "local" end is the point at which you are provisioning the connection.

ifNum	Logical port number. On the AXSM, the range is 1-60. This ifNum corresponds to the ifNum added through the addport command. When adding an endpoint on a NNI port, make sure that PNNI signaling is disabled on the PXM-45 (cnfpnportsig <portid> -nniver none).
vpi	Virtual path identifier value in the range 0-255 (UNI) or 0-4095 (NNI or VNNI). For VNNI, specify one VPI per port.
vci	Virtual connection identifier (VCI): •For a VCC on a UNI, the range is 1-4095. On an NNI or VNNI, the VCI range is 32-65535. For MPLS, the recommended minimum VCI is 35. •For a VPC, the vci is 0.
service type	Value in the range 1-12 to specify the service type: •1=CBR1 (Constant Bit Rate 1) •2=VBR1RT (Variable Bit Rate 1, Real Time) •3=VBR2RT (Variable Bit Rate 2, Real Time) •4=VBR3RT (Variable Bit Rate 3, Real Time) •5=VBR1NRT (Variable Bit Rate 1, Non-Real Time) •6=VBR2NRT (Variable Bit Rate 2, Non-Real Time) •7=VBR3NRT (Variable Bit Rate 3, Non-Real Time) •8=UBR1 (Unspecified Bit Rate 1) •9=UBR2 (Unspecified Bit Rate 2) •10=ABRSTD (Standard ABR—see cnfabr for ABR-specific parameters) •11=CBR2 (Constant Bit Rate 2) •12=CBR3 (Constant Bit Rate 3)
mastership	Value to specify the endpoint as master or slave: •1 or `m' specifies the master end. •2 or `s' specifies the slave end.
-slave	Keyword that precedes the slave-end identifier, an item you enter at the master end. This keyword is mandatory when you are adding a master endpoint (mastership=m or 1).
- lpcr	Local Peak Cell Rate (PCR). Specifies the PCR from a local endpoint to a remote endpoint (3-5651328 cells per second). Peak Cell Rate is the maximum cell rate for the connection at any time.
- rpcr	Remote Peak Cell Rate (PCR). Specifies the PCR from a remote endpoint to a local endpoint (3-5651328 cells per second). Peak Cell Rate is the maximum cell rate for the connection at any time.
- lscr	Local Sustained Cell Rate (SCR). Specifies the SCR from a local endpoint to a remote endpoint (3-5651328 cells per second). Sustained Cell Rate is the maximum cell rate that a connection can sustain for long periods.
- rscr	Remote Sustained Cell Rate (SCR). Specifies the SCR from a remote endpoint to a local endpoint (3-5651328 cells per second). Sustained Cell Rate is the maximum cell rate that a connection can sustain for long periods.
- lmbs	Local Maximum Burst Rate (MBS). Specifies the MBS from a local endpoint to a remote endpoint (1-5000000 cells). Maximum Burst Size is the maximum number of cells that can burst at the PCR and still be compliant.
- rmbs	Remote Maximum Burst Rate (MBS). Specifies the MBS from a remote endpoint to a local endpoint (1-5000000 cells). Maximum Burst Size is the maximum number of cells that can burst at the PCR and still be compliant.
- cdvt	Local Cell Delay Variation Tolerance (CDVT). Specifies the CDVT from a local endpoint to a remote endpoint (1-5000000 microseconds). Cell Delay Variation Tolerance controls the time scale over which the PCR is policed. Note that no remote CDVT is necessary.
- lcdv	Local Cell Delay Variation (CDV). Specifies the CDV from a local endpoint to a remote endpoint (1-16777215 microseconds). Cell Delay Variation is the peak to peak cell delay variation expressed in microseconds.
- rcdv	Remote Cell Delay Variation (CDV). Specifies the CDV from a remote endpoint to a local endpoint (1-16777215 microseconds). Cell Delay Variation is the peak to peak cell delay variation expressed in microseconds.
- cc	(Optional) Operations, administration, and maintenance continuity check (OAM CC): enter 1 to enable or 0 to disable. The default is 0. To provision continuity checking, you must enable this function at both ends of the connection, otherwise a connection alarm results. Therefore, even as you create the connection with this parameter, the connection goes into alarm until both ends of the connection are up.
- stat	(Optional) Statistics collection: enter 1 to enable or 0 to disable. The default is 0. The Cisco WAN Manager tool collects statistics for a connection if you enable it here. Statistics collection is disabled for all connections by default. Statistics collection has an impact (which may not be significant) on the real-time response, especially for SVCs (which can be affected even though you do not add SVCs). Therefore, you should enable statistics collection for only the subset of connections that really warrants such a feature.
- frame	Frame discard: Enter a 1 to enable or a 0 to disable. The default is disabled (0).
- mc	(Optional) Maximum cost (maxcost): a value that creates a priority for the connection route. The switch can select a route only if the cost does not exceed maxcost. The range for maxcost is 0-2147483647. If you do not specify maxcost, the connection has the highest routing priority by default. Therefore, the maxcost parameter lets you lower the routing priority of a connection. Note the following effects of values in the maxcost rage: •To assign the highest priority to an SPVC based on cost (any path is acceptable), enter 2147483647. You can achieve the same result by not specifying maxcost at all, in which case the cost appears as a -1 in the dspcon output. (You cannot enter a -1 for either maxcost in addcon or to the cnfpnni-intf command, but display commands can show unspecified values as -1.). •Enter a 0 for optimal (or least expensive) path. •For any non-zero maxcost, the switch assigns a path if the total cost for all links does not exceed maxcost. Although maxcost applies to an individual connection, routing costs substantially depend on a cost-per-link that you specify at every PNNI logical port in the network. The applicable PNNI command is cnfpnni-intf. (See the description of the administrative weight parameter for cnfpnni-intf in the chapter, "PNNI Commands." The cost of a route is as follows: routing cost=sum of all costs-per-link where: •The cost-per-link has been specified through cnfpnni-intf at the egress of each logical port under PNNI control throughout the network. The impact of cost-per-link is cumulative, not just local. •Each link has two egress points: one going to the far endpoint, and one in the return direction. The cost-per-link can differ in each direction, so the switch adds the cost-per-link in each egress instead multiplying cost by two. The cost-per-link applies to all connections of a particular service type on a port. For example, the cost-per-link is the same for all VBR.1 connections that PNNI controls on a port, and this cost can differ from all UBR.1 connections on the same port. Alternatively, you can use cnfpnni-intf to make the cost-per-link the same for all service types. To illustrate by examining a four-link route: 1. You specify a maxcost of 100000. 2. A potential route has four links for a total of eight egress points (four going to the endpoint and four coming back). 3. The cost-per-link at 6 ports is 5040 (the default) and 10000 at 2 ports. The PXM-45 would use the route because the resulting cost of 50240 is less than the maxcost of 100000.

Error Messages

The system displays error messages that can be printed out for the following reasons:

•Some of the traffic management parameters apply to specific service types (rt-VBR, for example). If you type a parameter that does not apply to a selected traffic type, the connection is rejected.

•Insufficient resources are available to accept the provisioning request.

•The type of card does not support a certain feature.

•The port cannot support SPVCs.

One of the following error messages appears if one of the preceding causes it true:

•"Port does not support requested serviceType"

•"lscr not allowed to exceed lpcr"

•"rscr not allowed to exceed rpcr"

•"lpcr must be defined for cbr serviceType"

•"rpcr must be defined for cbr serviceType"

•"lpcr and lscr must be defined for vbr serviceType"

•"rpcr and rscr must be defined for vbr serviceType"

•"lpcr must be defined for abr/ubr serviceType"

•"rpcr must be defined for abr/ubr serviceType"

•"Requested rcdv is too low"

•"Requested rctd is too low"

•"Requested max cell loss ratio (clr) is too high"

•"Requested cell rate (lscr/lpcr) is too high"

•"Requested cell rate (rscr/rpcr) is too high"

Related Commands

cnfcon, cnfabr, delcon, dspcon, dspcons, dncon, upcon

Attributes

Log: log

State: active

Privilege: GROUP1

Example

Add the slave end of a VCC on logical port 1 with VPI=10, VCI=40, CBR service type. Note that the system returns the slave end connection identifier in the hexadecimal NSAP format with the VPI.VCI at the end. When you add the master endpoint of the connection, type -slave followed by this connection identifier. You can do a copy and paste rather than typing the whole string.

pinnacle1.AXSM.a >addcon 1 10 40 1 s

slave endpoint added successfully

slave endpoint id : 00000E1000001C008051B730FFFFFF010B180100.10.40

clrpncon

Call Control Operations: Release Call

Releases a call.

Card(s) on Which Command Executes

PXM-45

Syntax

clrpncon <portid> 

{all | vpi} 

[vci]

Syntax Description

portid	See PNNI Format.
all | vpi	Clear all or a specific VPI of the call. Default = 0
vci	VCI of the call to clear. If no VCI is specified, this is a VP connection.

Related Commands

dsppncon, dspncons

Attributes

Log: log

State: active

Privilege: SUPER_GP

clrpnconstats

Call Control Operations: Clear Call Statistics

Clears existing call statistics for one port or all ports.

Card(s) on Which Command Executes

PXM-45

Syntax

clrpnconstats [ portid ]

Syntax Description

portid

See PNNI Format.

Related Commands

dsppnconstats

Attributes

Log: log

State: active

Privilege: GROUP1

Examples

cnfabr

Configures the ABR-specific parameters for an existing SPVC. The connection must be of service type ABR (in the addcon command, service type=10).

Card(s) on Which Command Executes

AXSM

Syntax

cnfabr <ifNum> <vpi <vci>
[-icr <Initial cell rate>]
[-adtf <ACR decr. factor>]
[-rdf <Rate decr. factor>]
[-rif <Rate incr. factor>]
[-nrm <Cells per fwd RM>]
[-trm <Time between fwd RMs>]
[-cdf <cutoff decrease factor>]
[-frtt <fix round trip delay>]
[-tbe <transient buffer exposure>]
[-intvsvd <internal vsvd config>]
[-extvsvd <external vsvd config>]

Syntax Description

ifNum	The port number of the connection to configure.
vpi	The VPI range for a UNI port endpoint is 0-255. The VPI range for an NNI or VNNI port endpoint is 0-4095.
vci	The VCI range for a UNI port endpoint is 1-4095. The VCI range for a NNI port endpoint is 32-65535. For MPLS, the recommended minimum VCI is 35.
-icr	Keyword that specifies the Initial Cell Rate (ICR) in cells per second. This is the rate at which the source should begin transmitting, and is also the rate at which the source should resume transmitting after an idle period. The range is 0-4294967295 cells per second.
-adtf	Keyword that specifies the ACR Decrease Time Factor (ADTF). This is the time permitted to decrease the cell rate from the RM-cell rate to the Allowed Cell Rate (ACR) for normal traffic. The range is 1-1023 milliseconds.
-rdf	Keyword that specifies the Rate Decrease Factor (RDF). This is the factor by which to decrease the Allowed Cell Rate (ACR). RDF is a power of 2 in the range 1/32768 to 1.
-rif	Keyword that specifies the Rate Increase Factor (RIF). This is the factor by which to increase the Allowed Cell Rate (ACR). RIF is a power of 2 in the range 1/32768 to 1.
-nrm	Keyword that specifies the maximum number of cells that the source can send for each forward RM-cell. Nrm is a power of 2 in the range 2-256.
-trm	Keyword that specifies the maximum number of milliseconds for one RM-cell to travel from source to endpoint. The range is 100 x 2-7 to 100 x 20 milliseconds.
-cdf	Keyword that specifies the Cutoff Decrease Factor (CDF). This controls the decrease in Allowed Cell Rate (ACR) associated with Missing RM-cell count (CRM). CDF can be either or the following: •Zero •A power of 2 in the range 1/64 to 1 CRM limits the number of forward RM-cells that may be sent in the absence of received backward RM-cells. CRM is an integer. Its size is implementation specific.
-frtt	Keyword that specifies the Fixed Round-Trip Time (FRTT). This is the sum of the fixed delays plus the propagation delays from the source to the destination and back. The range is 0- 16.7 seconds.
-tbe	Keyword that specifies the Transient Buffer Exposure (TBE). This is the negotiated number of cells that the network would like to limit the source to sending during startup periods, before the first RM-cell returns. The range is 0-16,777,215 cells.
-intvsvd	Keyword that specifies the internal virtual source / virtual destination (VS/VD). •1=Off •2=On •3=Unspecified
-extvsvd	Keyword that specifies the external virtual source / virtual destination (VS/VD). •1=Off •2=On •3=Unspecified

Related Commands

addcon, cnfabrtparmdft, dspabrtparmdft

Attributes

Log: log

State: active

Privilege: GROUP1

cnfabrtparmdft

Config ABR Traffic Parameters Default

Configures the default ABR traffic parameter(s), used for SPVC, per port.

When a user requests an ABR connection, the controller adds the default ABR traffic parameters before the connection is committed. The user can change the ABR traffic parameters, per connection, using the cnfabr command available on the AXSM.

The default ABR traffic parameters are used in the SETUP message at the source when an SPVC for ABR service category is set up.

Card(s) on Which Command Executes

PXM-45

Syntax

Syntax

cnfabrtparmdft <portid>
[-rif RIF-value]
[-rdf RDF-value]
[-tbe TBE-value]
[-nrm NRM-value]
[-trm TRM-value]
[-adtf ADTF-value]
[-cdf CDF-value]
[-fsd FSD-value]

Syntax Description

portid	The ID number of the port on which to configure the default ABR parameters. The format of is: [shelf.]slot[:subslot].port[:subport]
-rif	Keyword that specifies the Rate Increase Factor (RIF). This is the factor by which to increase the Allowed Cell Rate (ACR). RIF is a power of 2 in the range 1/32768 to 1.
-rdf	Keyword that specifies the Rate Decrease Factor (RDF). This is the factor by which to decrease the Allowed Cell Rate (ACR). RDF is a power of 2 in the range 1/32768 to 1.
-tbe	Keyword that specifies the Transient Buffer Exposure (TBE). This is the negotiated number of cells that the network would like to limit the source to sending during startup periods, before the first RM-cell returns. The range is 0-16,777,215 cells.
-nrm	Keyword that specifies the maximum number of cells that the source can send for each forward RM-cell. Nrm is a power of 2 in the range 2-256.
-trm	Keyword that specifies the maximum number of milliseconds for one RM-cell to travel from source to endpoint. The range is 100 x 2-7 to 100 x 20 milliseconds.
-adtf	Keyword that specifies the ACR Decrease Time Factor (ADTF). This is the time permitted to decrease the cell rate from the RM-cell rate to the Allowed Cell Rate (ACR) for normal traffic. The range is 1 to 1023 milliseconds.
-cdf	Keyword that specifies the Cutoff Decrease Factor (CDF). This controls the decrease in Allowed Cell Rate (ACR) associated with Missing RM-cell count (CRM). CDF can be either or the following: •Zero •A power of 2 in the range 1/64 to 1 CRM limits the number of forward RM-cells that may be sent in the absence of received backward RM-cells. CRM is an integer. Its size is implementation-specific.
-fsd	Keyword that specifies the Fixed-source-delay (default = 0).

Related Commands

addcon, cnfabr, dspabrtparmdft

Attributes

Log: log

State: active

Privilege: ANYUSER

cnfcdvtdft

Port Management: Configure Default CDVT

Configures the default CDVT to request UPC for cells received on the port. The new configuration applies to new incoming calls, not existing calls. This command can be used regardless of the state of the port.

Syntax

cnfcdvtdft <portid> 

<service_category> 

[ microseconds ]

Syntax Description

portid	See PNNI Format.
<service_category>	ATM 4.0 service category: cbr, rtvbr, nrtvbr, ubr, or abr. •cbr = constant bit rate •rtvbr = real time variable bit rate •nrtvbr = non-real time variable bit rate •ubr = unspecified bit rate •abr = available bit rate
micro seconds	Integer Range: (0 through 2147483647) Default value is set by the platform (250,000). If this parameter is not specified, the default is used/restored.

Related Commands

dspcdvtdft

Attributes

Log: log

State: active

Privilege: SUPER_GP

Examples

None unless errors occur.

cnfcon

Configure Connection

Modifies the connection bandwidth, policing, and routing parameters of an existing endpoint. For ABR-specific parameters, use the cnfabr command.

The command parameters consist of:

•A logical port, VPI, and VCI to identify the connection

•Bandwidth parameters for the local (master) end then the remote (slave) end

•Policing parameters for the connection as a whole

Note that after you specify the mandatory connection identifier, all other parameters are optional.

Card(s) on Which the Command Executes

AXSM

Usage Guidelines

This section details about the application of certain addcon parameters. For example, a parameter may require you to specify it at both ends of a connection.

Traffic Parameters

Traffic parameters such as PCR, SCR, MBS are entered at both the master and slave endpoints for both the forward and reverse directions. Be sure that the value entered as "local" on one end is equal to the value entered as "remote" on the other end. For example, the lpcr on the slave endpoint should be same as the rpcr on the master endpoint and vice versa when you provision the connection at the other end. If you modify traffic parameters after creating an SPVC, you just modify them at both the master endpoint or the slave endpoint.

Traffic parameters such as CDV, CTD are entered at both the master and slave endpoints for both the forward and reverse directions. However, the values of these parameters entered at the slave end are ignored during call setup. Therefore, you can specify the lcdv, rcdv, lctd and rctd options at the master end only.

Routing Parameters

The routing parameter maxcost (specified using -mc option) need to be entered at the master endpoint only. The values of this parameters entered at the slave end is ignored and not considered during call setup.

Frame Discard

For the parameter frame discard (specified using -frame option), you need to enter it at only the master endpoint. This parameters has no significance at the slave end.

Local-Only Parameters

The parameters CDVT, stats enable, cc enable (specified using -cdvt, -stat, -cc) are significant only at the endpoint where you enter them. Therefore, they can be different at each end of the connection.

Syntax

cnfcon
<ifNum>
<vpi>
<vci>
<service type>
<mastership>
[-slave <NSAP.vpi.vci>]
[-lpcr <local PCR >]
[-rpcr <remote PCR>]
[-lscr <local SCR>]
[-rscr <remote SCR>]
[-lmbs <local MBS>]
[-rmbs <remote MBS>]
[-cdvt <local CDVT>]
[-lcdv <local maxCDV>]
[-rcdv<remote maxCDV>]
[-lctd <local maxCTD>]
[-rctd <remote maxCTD>]
[-cc <OAM CC Cnfg>]
[-stat <Stats Cnfg>]
[-frame <frame discard>]
[-mc <maximum cost>]

Syntax Description

ifNum	Logical port number. On the AXSM, the range is 1-60.
vpi	Virtual path identifier in the range 0-255 (UNI) or 0-4095 (NNI or VNNI).
vci	Virtual connection identifier (VCI): •For a VCC on a UNI, the range is 1-4095. On an NNI or VNNI, the VCI range is 32-65535. For MPLS, the recommended minimum VCI is 35. •For a VPC, the vci is 0.
service type	Value in the range 1-12 to specify the service type: •1=CBR1 (Constant Bit Rate 1) •2=VBR1RT (Variable Bit Rate 1, Real Time) •3=VBR2RT (Variable Bit Rate 2, Real Time) •4=VBR3RT (Variable Bit Rate 3, Real Time) •5=VBR1NRT (Variable Bit Rate 1, Non-Real Time) •6=VBR2NRT (Variable Bit Rate 2, Non-Real Time) •7=VBR3NRT (Variable Bit Rate 3, Non-Real Time) •8=UBR1 (Unspecified Bit Rate 1) •9=UBR2 (Unspecified Bit Rate 2) •10=ABRSTD (Standard ABR—see cnfabr for ABR-specific parameters) •11=CBR2 (Constant Bit Rate 2) •12=CBR3 (Constant Bit Rate 3)
mastership	Value to specify the endpoint as master or slave: •1 or `m' specifies the master end. •2 or `s' specifies the slave end.
-slave	Keyword that specifies the slave-end identifier, an item you enter at the master end. This keyword is mandatory when you are adding a master endpoint (mastership=m or 1).
- lpcr	Keyword that specifies the Peak Cell Rate (PCR) from a local endpoint to a remote endpoint (3 to 5651328 cells per second). Peak Cell Rate is the maximum cell rate for the connection at any time.
- rpcr	Keyword that specifies the Peak Cell Rate (PCR) from a remote endpoint to a local endpoint (3 to 5651328 cells per second). Peak Cell Rate is the maximum cell rate for the connection at any time.
- lscr	Keyword that specifies the Sustained Cell Rate (SCR) from a local endpoint to a remote endpoint (3 to 5651328 cells per second). Sustained Cell Rate is the maximum cell rate that a connection can sustain for long periods.
- rscr	Keyword that specifies the Sustained Cell Rate (SCR) from a remote endpoint to a local endpoint (3 to 5651328 cells per second). Sustained Cell Rate is the maximum cell rate that a connection can sustain for long periods.
- lmbs	Keyword that specifies the Maximum Burst Rate (MBS) from a local endpoint to a remote endpoint (1 to 5000000 cells). Maximum Burst Size is the maximum number of cells that can burst at the PCR and still be compliant.
- rmbs	Keyword that specifies the Maximum Burst Rate (MBS) from a remote endpoint to a local endpoint (1 to 5000000 cells). Maximum Burst Size is the maximum number of cells that can burst at the PCR and still be compliant.
- cdvt	Keyword that specifies the Cell Delay Variation Tolerance (CDVT) from a local endpoint to a remote endpoint (1 to 5000000 microseconds). Cell Delay Variation Tolerance controls the time scale over which the PCR is policed. Note that no remote CDVT is necessary.
- rcdvt	Keyword that specifies the Cell Delay Variation Tolerance (CDVT) from a remote endpoint to a local endpoint (1 to 5000000 microseconds). Cell Delay Variation Tolerance controls the time scale over which the PCR is policed.
- lcdv	Keyword that specifies the Cell Delay Variation (CDV) from a local endpoint to a remote endpoint (1 to 16777215 microseconds). Cell Delay Variation is the peak to peak cell delay variation expressed in microseconds.
- rcdv	Keyword that specifies the Cell Delay Variation (CDV) from a remote endpoint to a local endpoint (1 to 16777215 microseconds). Cell Delay Variation is the peak to peak cell delay variation expressed in microseconds.
- cc	(Optional) Keyword that sets the OAM CC: Enter 1 to enable or 0 to disable. The default is 0.
- stat	(Optional) Keyword that sets the statistics collection: Enter 1 to enable or 0 to disable. The default is 0. The Cisco WAN Manager tool collects statistics for a connection if you enable it here. Statistics collection is disabled for all connections by default. Statistics collection has an impact (which may not be significant) on the real-time response, especially for SVCs (which can be affected even though you do not add SVCs). Therefore, you should enable statistics collection for only that subset of connections that really warrants such a feature.
- frame	Keyword that sets frame discard: Enter a 1 to enable or a 0 to disable. The default is 0.
- mc	(Optional) Keyword that specifies the maximum cost (maxcost): a value that creates a routing priority. If you do not specify this optional parameter, the connection defaults to having the highest routing priority. Therefore, the maxcost parameter lets you lower the priority of a connection—but only in regards to finding a route for it. The range for maxcost is 0-2147483647. The PXM-45 does not use a particular route if the cost for the route exceeds the maxcost. The cost of a route depends on a cost-per-link specified through the cnfpnni-intf command. The cost-per-link applies to at the egress a port for all connections of a particular service type. For example, the cost-per-link is the same for all VBR.1 connections that PNNI controls on a given port, but this cost can differ from all UBR.1 connections on the same port. For a route under consideration, the cost is the sum of all the cost-per-links at each egress in the forward and backward directions along the entire route. In a one-link route, for example, the cost is the sum of the cost-per-links at two ports. To illustrate further with a four-link route: 1. You specify a maxcost of 100000. 2. The route under consideration by the switching fabric has four links for a total of eight egress points. 3. The cost-per-link at six ports is 5040 (the default in cnfpnni-intf), and the cost per link at two ports is 10000. The node would use the route because the resulting cost of 50240 is less than the maxcost of 100000. Note that you can specify no limit for a service type by entering a cost-per-link of -1 through cnfpnni-intf. A -1 cost-per-link makes maxcost meaningless.

Related Commands

addcon, delcon, dspcon, dspcons, dspconstats

Attributes

Log: nolog

State: active, standby

Privilege: GROUP1

cnfconsegep

Configure Segment Endpoint for a Connection

Configures a connection as a segment endpoint. When both VPI and VCI are present, the segment endpoint is a F5 flow endpoint (for VCCs). When the optional VCI is not present, the segment endpoint is a F4 flow endpoint (for VPCs). Use this command only for established calls.

---

Note Before executing this command, you be sure continuity checking is de-activated. If you leave it on, continuity check failure occurs for the connection. Use cnfconsegep in conjunction with conntrace for fault isolation.

---

Command(s) on Which Command Executes

PXM-45

Syntax

cnfconsegep <portid> 

< vpi >

[vci]

Syntax Description

portid	See PNNI Format.
vpi	VPI of the connection
vci	VCI of the connection

Related Commands

cnfoamsegep, dspoamsegep, delconsegep, dspconsegep

Attributes

Log: log

State: active

Privilege: SUPER_GP

Examples

None.

cnfmbsdft

Port Management: Configure Default MBS

Configures the default MBS for cells received on the port. The new configuration applies to new incoming calls, not existing calls. This command can be used regardless of the state of the port.

Command(s) on Which Command Executes

PXM-45

Syntax

cnfmbsdft <portid> 

<service_category> 

[num-of-cell]:

Syntax Description

portid	See PNNI Format.
service_category	ATM 4.0 service category, either cbr, rtvbr, nrtvbr, ubr, or abr. •rtvbr = real time variable bit rate •nrtvbr = non-real time variable bit rate
num-of-cell	Integer. The MBS is expressed in cells. Range: (0 through 2147483647) Default: set by the platform (1024). If this parameter is not specified, the default is used/restored.

Related Commands

dspmbsdft

Attributes

Log: log

State: active

Privilege: SUPER_GP

Examples

None unless errors occur.

cnfoamsegep

Port Management: Configure OAM Segment Endpoint on a Port

Define the port as a segment endpoint for F4 and F5 OAM flow. This command does not take effective for existing connections, and only does for newly established calls. This command can be used regardless of the state of the port.

Command(s) on Which Command Executes

PXM-45

Syntax

cnfoamsegep <portid> 

[{yes | no}]

Syntax Description

portid	See PNNI Format.
yes	The port is configured as a segment endpoint, and is a segment endpoint for all connections on this port.
no	The port is not a segment endpoint. Default = no

Related Commands

dspoamsegep, cnfconsegep, delconsegep

Attributes

Log: log

State: active

Privilege: SUPER_GP

Examples

None unless errors occur.

delcon

Delete Connection

Use the delcon command to delete a connection. Delete the connection at both ends—first at the master end, then at the slave.

Card(s) on Which Command Executes

AXSM

Syntax

delcon  
<ifnum> 
<vpi> 
<vci>

Syntax Description

ifnum	The logical port where the connection exists. The range is 1-60.
vpi	The VPI of the connection.
vci	The VCI of the connection.

Related Commands

dspcon, addcon, cnfcon

Attributes

Log: log

State: active, standby

Privilege: GROUP1

delcons

Delete Connections

Delete a range of ATM connections.

---

Caution Before entering this command, you need to know exactly how many connections you need to delete. This command starts deleting connection endpoints in lexicographic order ( dspcons displays in the same order). Incorrect of this command could result in deletion of more endpoints than necessary, and repairing such damage could be very costly.

---

Card(s) on Which Command Executes

AXSM

Syntax

delcons  
<ifNum>  
<vpi>  
<vci>  
[-num <num. conns to del>]  
[-verbose < 1 | 0 >]

Syntax Description

ifNum	Logical port number. On the AXSM, the range is 1-60.
vpi	For a UNI, the range is 0-255. For an NNI, the range is 0-4095.
vci	For a VCC, the range is 32-65535. For a VPC, the only value is 0.
-num	(Optional) Keyword that specifies the number of connections to delete.
-verbose	(Optional) Keyword that enables (1) or disables (0) verbose mode. In verbose mode, the screen displays the connection identifier of each connection immediately after it is deleted.

Related Commands

None

Attributes

Log: nolog

State: active

Privilege: GROUP1

delconsegep

Operational Commands: Remove Segment Endpoint of a Connection

Removes a segment endpoint on a connection. When both VPI and VCI are present, the segment endpoint is a F5 flow endpoint (for VCCs). When the optional VCI is not present, the segment endpoint is a F4 flow endpoint (for VPCs).

Card(s) on Which Command Executes

PXM-45

Syntax

delconsegep <portid> 

vpi 

[vci] 

Syntax Description

portid	See PNNI Format.
vpi	VPI of the connection
vci	VCI of the connection

Related Commands

cnfoamsegep, dspoamsegep, cnfconsegep, dspconsegep

Attributes

Log: log

State: active

Privilege: SUPER_GP

Examples

dncon

Down Connection

Administratively deactivates (or "downs") so you can modify or troubleshoot the network. This operation applies to only SPVCs. To reactivate the connection, use upcon.

Card(s) on Which Command Executes

AXSM

Syntax

dncon  
<ifNum>  
<vpi>  
<vci>

Syntax Description

ifNum	The logical port (or logical interface) number. On the AXSM, the range is 1-60.
vpi	Virtual path identifier. On a UNI, the range is 0-255. On an NNI, the range is 0-4095.
vci	For a virtual connection (VCC) on a UNI, the range is 1-4095. On an NNI or VNNI, the VCI range is 32-65535. For MPLS, the recommended minimum VCI is 35. For a virtual path connection (VPC), the VCI is always 0.

Related Commands

upcon

Attributes

Log: log

State: active

Privilege: GROUP1

dspabrtparmdft

Display ABR Traffic Parameters Default

Displays the default ABR parameters for a logical port under PNNI.

Card(s) on Which Command Executes

PXM-45

Syntax

dspabrtparmdft <portid>

Syntax Description

portid has the format [shelf.]slot[:subslot].port[:subport]

Related Commands

addcon, cnfabr, cnfabrtparmdft

Attributes

Log: nolog

State: active

Privilege: ANYUSER

Example

Display the default ABR parameters on portid 1:1.1:1.

Default ABR Traffic Parameters For: 1:1.1:1 

-----------------------------------

RIF : 7 (= 1/512)

RDF : 4 (= 1/4096)

TBE : 1048320 (Cells)

NRM : 5 (= 32 Cells)

TRM : 8 (= 100 msec)

ADTF: 50 (= 0.50 Sec)

CDF : 7 (= 1/2)

FSD : 0 (microSec)

dspcdvtdft

Port Management: Show Default CDVT

Displays the default CDVT set for the port.

Card(s) on Which Command Executes

PXM-45

Syntax

dspcdvtdft <portid>

Syntax Description

portid

See PNNI Format.

Related Commands

dspcdvtdft, cnfcdvtdft

Attributes

Log: nolog

State: active, standby

Privilege: ANYUSER

Examples

	cbr	rt-vbr	nrt-vbr	ubr	abr
CDVT:	250,000	250,000	250,000	250,000	250,000

dspcon

Display Connection

Display information about an SPVC. The contents of the display on the AXSM and the PXM-45 slightly differ. On both cards, the dspcon output appears in sections to make the information easier to sort.

Most of the information in the dspcon output comes from addcon execution. See the addcon description for more information. Also, executing cnfpnni-intf can affect the dspcon output.

Display Connection on the PXM-45

On the PXM-45, dspcon shows the following connection identifiers:

•NSAP address, status, and ownership of local and remote ends of the connection. The display shows whether a particular endpoint is the master or slave.

The provisioning parameters in the display show:

•Connection type of VPC or VCC.

•Service type and compliance (for example, UBR for service type and UBR.1 for ATM Forum compliance).

•Bearer class.

•Whether continuity checking or frame discard are enabled (see addcon description).

•Cause of the last failure. This field can also show that no errors have occurred since the connection was first added by displaying "SPVC Established." If a failure occurred, the Attempts field shows the number of times the system attempted to re-establish service. If no failures have occurred, the Attempts field contains a 0.

•L-Util and R-Util are the local and remote percent of utilization assigned to the connection. Currently, the default of 100% is the only value.

•Cost values for the connection's route: the two fields in this category are Max Cost and Routing Cost. The Max Cost is a cost-per-link configured for a service type (such as UBR) through the cnfpnni-intf command. When you add the SPVC through addcon, you can specify a maximum routing cost through the maximum cost (maxcost) parameter. The maxcost represents the maximum cost for an individual connection. The system uses the cost-per-link for the service type and the maxcost for the connection to determine whether a route costs too much. After the system creates a route, the total number of links yields the Routing Cost.

The default cost-per-link is 5040, so if a particular service type uses the default and a route consists of 4 links, the Routing Cost is 20160. If the dspspvc display shows that Max Cost is -1, no limit was specified through cnfpnni-intf, and the resulting Routing Cost is 0.

•Broadcast type: point-to-point or multicast.

The Traffic Parameters section shows the standard parameters PCR, SCR, and CDV in the receive and transmit directions.

Display Connection on the AXSM

On the AXSM, dspcon shows the following connection identifiers:

•NSAP address, logical port, VPI/VCI, status, and ownership of local and remote ends of the connection. The display shows whether a particular endpoint is the master or slave.

The provisioning parameters in the display show:

•Connection type of VPC or VCC.

•Service type (for example, ABR)

•A number indicating the controller. For example, 2 refers to PNNI.) The addcontroller command specifies the controller.)

•The administrative state is either up or down. This state results from addcon or dncon/upcon.

•The operational state is either OK or failed. The operational state can apply to a connection regardless of the administrative state.

The traffic management parameters consist of:

•Local and remote UPC parameters of PCR, MBS, CTD, CDVT, and so on. The characters "N/A" indicate that the parameter does not apply to the service type.

Other fields pertain to connection integrity:

•OAM connectivity check enable or disable

•Loopback test enable/disable and loopback type.

•Round trip delay in microseconds. This field is non-zero only if you previously executed tstdelay.

The dspcon command requires a unique connection identifier. If you do not have the information to identify a connection, execute dspcons. On the AXSM, dspcons identifies all the connections on the AXSM. On the PXM-45, dspcons identifies all the connections on the node. (See dspcons description).

Card(s) on Which Command Executes

AXSM, PXM-45

Syntax

On the AXSM:

dspcon  
<ifNum>  
<vpi>  
<vci>

On the PXM-45:

dspcon  
<portid>  
<vpi>  
<vci>

Syntax Description

ifNum AXSM	The logical port number in the range 1-60.
portid PXM-45	The portid has the format [shelf.]slot[:subslot].port[:subport], but shelf currently is always 1 and therefore optional.
vpi	VPI number. At the UNI, the range is 0-255. At the NNI, the range is 0-4095.
vci	VCI number. For a VCC, the range is 32-65535. For a VPC, the VCI is 0.

Related Commands

addcon, dspcons, cnfcon

Attributes

Log: nolog

State: active, standby

Privilege: ANYUSER

Examples

Display connection 2 20 1000 on the current AXSM.

ITNODE3.1.AXSM.a > dspcon 2 20 1000

--------------------------------------------------------------------------

Local   :                NSAP  Address                    vpi       vci

(S)       4700918100000000107B65F27C00000101180200          20      1000

Remote  :                NSAP  Address                    vpi       vci

(M)       4700918100000000107B65F30C0000010B180200          20      1000

--------------------------------------------------------------------------

Conn. Type    :      VCC                          Admn Status  :  ADMN-UP

Service Type  :   abrstd                          Oper Status  :       OK

Controller    :        2                          Record #     :       18

--------------------------------------------------------------------------

Local PCR     :       50                          Remote PCR   :       50

Local SCR     :      N/A                          Remote SCR   :      N/A

Local CDV     :      N/A                          Remote CDV   :      N/A

Local CTD     :      N/A                          Remote CTD   :      N/A

Local MBS     :      N/A                          Remote MBS   :      N/A

Max Cost      :       -1                          Frame discard:        N

Local CDVT    :   250000

--------------------------------------------------------------------------

OAM CC Config : DISABLED                          Statistics   : DISABLED

--------------------------------------------------------------------------

Loopback Type : No  Lpbk | Dir: N/A     | Status: No Lpbk | RTD:      0us

--------------------------------------------------------------------------

Type <CR> to continue, Q<CR> to stop: 

--------------------------------------------------------------------------

Port side Tx  :  normal                           Swth side Tx :  normal

Port side Rx  :  normal                           Swth side Rx :  normal

--------------------------------------------------------------------------

I-AIS/RDI   E-AIS/RDI   CONDITIONED   CCFAIL   IfFail   Mismatch  LMI-ABIT

   NO          NO           NO          NO       NO        NO         NO

--------------------------------------------------------------------------

Internal VSVD config               :   No  Cnfg

External VSVD config               :   No  Cnfg

Local MCR                          :         50  cells/second

Remote MCR                         :         50  cells/second

Initial cell rate          (ICR)   :         50  cells/second

ACR decrease factor        (ADTF)  :         50  x 10 millisec

Rate decrease factor       (RDF)   :          4

Rate increase factor       (RIF)   :          7

Cells per forward RM       (NRM)   :          5

Time between forward RM    (TRM)   :          8

cutoff decrease factor     (CDF)   :          7

fixed round trip delay     (FRTT)  :          0  microseconds

transient buffer exposure  (TBE)   :    1048320  cells

--------------------------------------------------------------------------

On the CLI of the PXM-45, display connection 20 100 on 11:1.1:2.

Unknown.7.PXM.a > dspcon 11:1.1:2 20 100

Port                   Vpi Vci                         Owner      State

-------------------------------------------------------------------------

Local  11:1.1:2        20.100                          MASTER     FAIL

       Address: 47.00918100000000107b65f33d.0000010b1802.00

Remote 11:1.1:2        10.100                          SLAVE      FAIL

       Address: 47.00918100000000107b65f33d.0000010b1802.00

-------------------- Provisioning Parameters --------------------

Connection Type: VCC          Cast Type: Point-to-Point

Service Category: CBR         Conformance: CBR.1

Bearer Class: BCOB-X

Last Fail Cause: SPVC Established                 Attempts: 0

Continuity Check: Disabled    Frame Discard: Disabled

L-Utils: 100   R-Utils: 100   Max Cost: -1    Routing Cost: 0

---------- Traffic Parameters ----------

Tx PCR:  50             Rx PCR:  50

Tx CDV:  N/A            Rx CDV:  N/A

Tx CTD:  N/A            Rx CTD:  N/A 

Display information for VPI/VCI 10 100 on port ID 1:1.1:1. In this case, port ID and remote and local NSAP addresses are the same, so the connection is a DAXCON. Also, the Max Cost is -1. The Max Cost of -1 means no cost-per-link was specified for UBR service, and therefore the Routing Cost is 0.

node19.8.PXM.a > dspcon 1:1.1:1 10 100

Port                   Vpi Vci                         Owner      State

-------------------------------------------------------------------------

Local  1:1.1:1         10.100                          SLAVE      OK

       Address: 47.00918100000000001a53c82d.000001011801.00

Remote 1:1.1:1         11.101                          MASTER     OK

       Address: 47.00918100000000001a53c82d.000001011801.00

-------------------- Provisioning Parameters --------------------

Connection Type: VCC          Cast Type: Point-to-Point

Service Category: UBR         Conformance: UBR.1

Bearer Class: BCOB-X

Last Fail Cause: SPVC Established                 Attempts: 0

Continuity Check: Disabled    Frame Discard: Disabled

L-Utils: 100   R-Utils: 100   Max Cost: -1    Routing Cost: 0

---------- Traffic Parameters ----------

Tx PCR:  14             Rx PCR:  14

Tx SCR:  3              Rx SCR:  3

Tx MBS:  1              Rx MBS:  1

Tx CDVT: -1             Rx CDVT: -1

Tx CDV:  N/A            Rx CDV:  N/A

Tx CTD:  N/A            Rx CTD:  N/A 

dspconinfo

Display Summaries of Connection Information (SPVCs Only)

The dspconinfo runs on the PXM-45 and lists the total number SPVCs on each PNNI port on the node. For each port, the display shows:

•Number of active connections

•Number of failed connections

•Total number of connections

Card(s) on Which Command Executes

PXM-45

Syntax

dspconinfo

Syntax Description

This command takes no parameters.

Related Commands

none

Attributes

Log: nolog

State: active, standby

Privilege: ANYUSER

Example

Display the SPVC summaries for the current node. This example shows all connections as failed.

popeye10.7.PXM.a > dspconinfo

Local Port      #Active   #Failed     #Total

---------------------------------------------

6:1.4:4             0          1          1

6:1.5:5             0      19800      19800

12:1.1:1            0      10001      10001

14:1.1:1            0      10000      10000

14:1.2:2            0      19900      19900 

dspcons

Display Connections—Display basic information for all connections.

The default usage of dspcons means no parameters and causes all available information for the connections to appear. To narrow the scope of the output, use one or more optional parameters.

The dspcons command runs on the CLI of either the AXSM or the PXM-45. The set of optional parameters and the output are different on these cards. See the sections, "Syntax Description (PXM-45)" and "Syntax Description (AXSM)" for the card-specific parameters. On the AXSM, the columns at the head of the information fields are:

record	A number for the connection with internal application only. It resides in the database on the AXSM and is not affected by user input. The system creates this number when you create the connection. The Cisco WAN Manager application uses this number.
Identifier	Identifies the connection in the format port vpi vci.
Type	Shows whether the connection is a VCC or a VPC.
SrvcType	The service type—VBR, and so on. (See addcon description).
M/S	Indicates whether the endpoint specified by Identifier is the master or slave.
Upld	The hexadecimal "Upload" number is an encoded timestamp the Cisco WAN Manager application uses to determine when a connection was created or modified. In the CLI context, this field has little meaning.
Adm	The administrative state of the connection. If the connection is down, it may have resulted from the dncon command.
Alarm	Shows the alarm status of the connection.

When you execute dspcons on the CLI of the PXM-45, the output shows:

Local and Remote Port ID	The display contains a column for the local port ID and a column for the remote port ID. The port ID has the format that the network controller utilizes: [shelf.]slot[:subslot].port[:subport]
Local and Remote VPI.VCI	The VPI and VCI at the local and remote ends of the connection.
State	The State column shows whether the connection is OK, down (by the dncon command), failed, or has an alarm indication signal (AIS) or abit errors.
Owner	Whether the endpoint is master or slave.
Local and Remote NSAP	An NSAP address for each end of the connection.

Card(s) on Which Command Executes

PXM-45, AXSM

Syntax (PXM-45)

dspcons 
[-port portid]  
[-vpi starting-vpi]  
[-vci starting vci]  
[-state {fail|ais|abit|ok|down}]   
[-owner {master|slave}]

Syntax Description
(PXM-45)

-port	The port identifier (portid) in the format that the network controller utilizes: [shelf.]slot[:subslot].port[:subport] Currently, the value for shelf is always 0 and therefore is not necessary.
-vpi	The VPI of the connection that you would like to serve as the starting connection in the display.
-vci	The VPI of the connection that you would like to serve as the starting connection in the display.
-state	A specific connection state. The display shows only the connections with the state you specify. Note that on the PXM-45, you must spell out the entire state keyword: failed—only failed connections ais—connections with alarm indication signal (AIS) set abit—connections on which an A-bit error has occurred ok—connections with no problems down—connections that are administratively down because a user has downed them through dncon
-owner	Specifies connections where the local endpoint is either master or slave.

Syntax (AXSM)

dspcons 
[-conn <conn id>] 
[-filt <filter options>] 
[-if <intf no>] 
[-vpi <vpi filter>] 
[-vci <vci filter>]

Syntax Description
(AXSM)

-conn	The connection ID (conn ID) of the connection to begin the display. The format of conn ID is: ifNum.vpi.vci On the AXSM, the range for ifNum is 1-60. The VPI has the range 0-4095. The VCI has the range 32-65535.
-filt	Note that, unlike the state keywords on the PXM-45, you enter only a number on the AXSM CLI to indicate the state. The display criteria are: 1 ingr—for errors in the ingress direction 2 egr—for errors in the egress direction 3 condn—for connections where the switch has conditioned the connection 4 iffail—for connection on a failed logical interface 5 ccfail 6 mis 7 abit—for connections where an A-bit error has occurred
-if	A particular logical interface for connection display.
-vpi	The VPI of all the connections that you would like to display.
-vci	The VCI of all the connections that you would like to display.

Related Commands

dspcon, addcon, cnfcon, delcon, dncon, upcon

Attributes

Log: nolog

State: active

Privilege: ANYUSER

Examples

Display connections on the current AXSM. In this example, only one master endpoint appears.

GN.6.AXSM.a > dspcons

record    Identifier   Type   SrvcType   M/S    Upld    Admn   Alarm

------    ----------   ----   --------   ---    ----    ----   -----

    0  02 0010 00100   VCC        cbr1   S   016cfdb2     UP      none

    2  02 0010 00200   VCC      vbr1rt   S   016cfe00     UP      none

    4  02 0010 00300   VCC      vbr2rt   S   016cfe54     UP      none

    6  02 0010 00400   VCC      vbr3rt   S   016cfea0     UP      none

    8  02 0010 00500   VCC     vbr1nrt   S   016cfeef     UP      none

   10  02 0010 00600   VCC     vbr2nrt   S   016cff42     UP      none

   12  02 0010 00700   VCC     vbr3nrt   S   016cff95     UP      none

   14  02 0010 00800   VCC        ubr1   S   016cffe4     UP      none

   16  02 0010 00900   VCC        ubr2   S   016d0034     UP      none

    1  02 0020 00100   VCC        cbr1   S   016cfdd7     UP      none

    3  02 0020 00200   VCC      vbr1rt   S   016cfe2a     UP      none

    5  02 0020 00300   VCC      vbr2rt   S   016cfe7a     UP      none

    7  02 0020 00400   VCC      vbr3rt   S   016cfec6     UP      none

    9  02 0020 00500   VCC     vbr1nrt   S   016cff17     UP      none

   11  02 0020 00600   VCC     vbr2nrt   S   016cff6d     UP      none

   13  02 0020 00700   VCC     vbr3nrt   S   016cffbe     UP      none

   15  02 0020 00800   VCC        ubr1   S   016d000b     UP      none

   17  02 0020 00900   VCC        ubr2   S   016d005c     UP      none

   18  02 0020 01000   VCC      abrstd   S   016d0088     UP      none

   20  21 0001 00000   VPC        cbr1   M   016d01ee     UP      none

Type <CR> to continue, Q<CR> to stop: 

Display all connections by entering dspcons on the CLI of the PXM-45.

Unknown.7.PXM.a > dspcons

Local Port         Vpi.Vci   Remote Port        Vpi.Vci    State   Owner

----------------------------+-----------------------------+-------+------

3:1.1:1            20 0      6:1.1:1            20 0       OK          MASTER

Local  Addr: 47.00918100000000107b65f33d.000001031801.00

Remote Addr: 47.00918100000000107b65f33d.000001061801.00

5:1.1:1           100 100    5:1.1:1           100 200     OK          SLAVE

Local  Addr: 47.00918100000000107b65f33d.000001051801.00

Remote Addr: 47.00918100000000107b65f33d.000001051801.00

5:1.1:1           100 200    5:1.1:1           100 100     OK          MASTER

Local  Addr: 47.00918100000000107b65f33d.000001051801.00

Remote Addr: 47.00918100000000107b65f33d.000001051801.00

6:1.1:1            20 0      3:1.1:1            20 0       OK          SLAVE

Local  Addr: 47.00918100000000107b65f33d.000001061801.00

Remote Addr: 47.00918100000000107b65f33d.000001031801.00

6:1.1:1           100 100    6:1.1:1           100 200     OK          SLAVE

Local  Addr: 47.00918100000000107b65f33d.000001061801.00

Remote Addr: 47.00918100000000107b65f33d.000001061801.00

6:1.1:1           100 200    6:1.1:1           100 100     OK          MASTER

Local  Addr: 47.00918100000000107b65f33d.000001061801.00

Remote Addr: 47.00918100000000107b65f33d.000001061801.00

6:1.1:1           200 100    6:2.1:3           200 200     OK          SLAVE 

Type <CR> to continue, Q<CR> to stop: 

6:1.1:1           100 200    6:1.1:1           100 100     OK          MASTER

Local  Addr: 47.00918100000000107b65f33d.000001061801.00

Remote Addr: 47.00918100000000107b65f33d.000001061801.00

6:1.1:1           200 100    6:2.1:3           200 200     OK          SLAVE

Type <CR> to continue, Q<CR> to stop:

Local  Addr: 47.00918100000000107b65f33d.000001061801.00

Remote Addr: 47.00918100000000107b65f33d.000001061803.00

6:2.1:3           200 200    6:1.1:1           200 100     OK          MASTER

Local  Addr: 47.00918100000000107b65f33d.000001061803.00

Remote Addr: 47.00918100000000107b65f33d.000001061801.00

9:1.3:3            10 100    Routed              0 0       FAIL        SLAVE

Local  Addr: 47.00918100000000107b65f33d.000001091803.00

Remote Addr: 00.000000000000000000000000.000000000000.00

11:1.1:2           10 100    11:1.1:2           20 100     OK          SLAVE

Local  Addr: 47.00918100000000107b65f33d.0000010b1802.00

Remote Addr: 47.00918100000000107b65f33d.0000010b1802.00

Local Port         Vpi.Vci   Remote Port        Vpi.Vci    State   Owner

----------------------------+-----------------------------+-------+------

11:1.1:2           20 100    11:1.1:2           10 100     OK          MASTER

Local  Addr: 47.00918100000000107b65f33d.0000010b1802.00

Remote Addr: 47.00918100000000107b65f33d.0000010b1802.00

dspconsegep

Display Connection Segment Endpoint

Displays OAM segment endpoint for a connection endpoint. When both VPI and VCI are present, the segment endpoint is a F5 flow endpoint (for VCCs). When the optional VCI is not present, the segment endpoint is a F4 flow endpoint (for VPCs). This command is used only for established calls.

Card(s) on Which Command Executes

PXM-45

Syntax

dspconsegep <portid> 

vpi 

[vci] 

Syntax Description

portid	See PNNI Format.
vpi	The VPI of the connection.
vci	The VCI of the connection.

Related Commands

cnfoamsegep, dspoamsegep, cnfconsegep, delconsegep

Attributes

Log: log

State: active, standby

Privilege: ANYUSER

dspmbsdft

Port Management: Show Default MBS

Displays the default MBS configured for the port.

Syntax

dspmbsdft <portid> 

Syntax Description

portid

See PNNI Format.

Related Commands

cnfmbsdft

Attributes

Log: nolog

State: active, standby

Privilege: ANYUSER

Examples

	rt-vbr	nrt-vbr
MBS:	1024	1024

dsppncon

Call Control Operations: Show Call Info

Displays information for an active call. The displayed call information corresponds to the objects described in the portCallTable and portAbrCallTable MIBs. This command can be issued at any node in the route path.

Syntax

dsppncon <portid> 

<vpi> 

<[vci]>

Syntax Description

portid	See PNNI Format.
vpi	VPI for the call.
vci	VCI for the call. If no VCI is specified, this is a VP connection.

Examples

dsppncon 4.2 2 42 

 Port :           4.2 VPI :     2  VCI :    42 

 CallRef:      14  CallLeafRef :       0 

 Calling-address:47.00918100000000d058ac24a2.000000040300.00 

 Calling-subaddress:N/A 

 Called-address:47.00918100000000d058ac24a2.000000040200.00 

 Called-subaddress:N/A 

 OE Port :           4.3 OE VPI :     2  OE VCI :    42  OE CallRef:      14 

 OAM-Type :OAM Endpoint 

 Connection-type :SPVC   Cast-type :point-to-point   Bearer-class :BCOBX 

 Service-category :VBR-RT   Call-clipping-susceptibility:no 

 Tx conformance :VBR.1  Rx conformance :VBR.1 

 Tx pcr :       100           Rx pcr :        50 

 Tx scr :    50 Rx scr :    50 

 Tx mbs :  1024 Rx mbs :  1024 

 Tx cdvt :   229 

 Tx frame-discard-option :disable  Rx frame-discard-option :disable 

 Max ctd :   N/A 

 Max Tx cdv :   N/A    Max Rx cdv :   N/A 

 Max Tx clr :   255    Max Rx clr :   255 

Related Commands

dsppncons

Attributes

Log: nolog

State: active, standby

Privilege: ANYUSER

Examples

Non-ABR Call:

Port: 5.3   VPI: 33 VCI: 44

CallRef: <call-id>    CallLeafRef: <leaf-id> 

Calling-address: <calling AESA address>

Calling-subaddress: <calling AESA sub-address>

Called-address: <called AESA address>

Called-subaddress: <called AESA sub-address>

OE port: <oe_port_id>    OE VPI: <oe_vpi>   OE VCI: <oe_vci>

OE callRef: <oe_callid>

Call-start-time: <timestamp>

Connection-type: SVC    Cast-type: point-to-point    Bearer-class: <bc>

Service-category: CBR   Call-clipping-susceptibility: no

Tx conformance: CBR.1               Rx conformance: CBR.1

Tx pcr: <tx pcr>                    Rx pcr: <rx pcr>

Tx scr: <tx scr>                    Rx scr: <rx scr>

Tx mbs: <tx mbs>                    Rx mbs: <rx mbs>

Tx cdvt: <tx cdvt>                  Rx cdvt: <rx cdvt>

Tx frame-discard-option: disable    Rx frame-discard-option: disable

Max ctd: <max ctd>

Max Tx cdv: <max tx cdv>            Max Rx cdv: <max rx cdv>

Max Tx clr: <max tx clr>            Max Rx clr: <max rx clr>

ABR Call

Port: 5.3  VPI: 100  VCI: 200

CallRef: <call-id>    CallLeafRef: <leaf-id>

Calling-address: <calling AESA address>

Calling-subaddress: <calling AESA sub-address>

Called-address: <called AESA address>

Called-subaddress: <called AESA sub-address>

OE port: <oe_port_id>    OE VPI: <oe_vpi>   OE VCI: <oe_vci>

OE callRef: <oe_callid>

Call-start-time: <timestamp>

Connection-type: SVC    Cast-type: point-to-point   Bearer-class: <bc>

Service-category: ABR   Call-clipping-susceptibility: no

Tx conformance: ABR

Tx pcr: <tx pcr>                    Rx pcr: <rx pcr>

Tx mcr: <tx mcr>                    Rx mcr: <rx mcr>

Tx icr: <tx icr>                    Rx icr: <rx icr>

Tx rif: <tx rif>                    Rx rif: <rx rif>

Tx rdf: <tx rdf>                    Rx rdf: <rx rdf>

Tx tbe: <tx tbe>                    Rx tbe: <rx tbe>

Tx nrm: <tx nrm>                    Rx nrm: <rx nrm>

Tx trm: <tx trm>                    Rx trm: <rx trm>

Tx adtf: <tx adtf>                  Rx adtf: <rx adtf>

Tx cdf: <tx cdf>                    Rx cdf: <rx cdf>

Tx frame-discard-option: disable    Rx frame-discard-option: disable

Frtt: <frtt>                        Max ctd: <max ctd>

Max Tx cdv: <max tx cdv>            Max Rx cdv: <max rx cdv> 

Max Tx clr: <max tx clr>            Max Rx clr: <max rx clr>

dsppncons

Call Control Operations: Show Calls

Displays a summary of active calls on one port or all ports. This command can be issued at any node.

Syntax

dsppncons 

[-port portid] 

[-vpi starting-vpi] 

[-vci starting-vci] 

[-type {p2p | p2mp}] 

Syntax Description

-portid	Keyword that sets the port ID. See PNNI Format.
-vpi	Keyword that specifies the VPI at which to begin displaying. This keyword can only be used if portid is specified.
-vci	Keyword that specifies the VCI at which to begin displaying. This keyword can only be used if -vpi is used.
-type	Keyword that sets the cast type. Only connections of this cast type will be displayed.

Related Commands

dsppncon

Attributes

Log: nolog

State: active, standby

Privilege: ANYUSER

Examples

Port       VPI  VCI       CallRef X-Port       VPI  VCI   CallRef  Type OAM-Type 

1:1.2:2     1   100       33       1:1.2:2      1   101      32    PTP    No 

    Calling-Addr:47.00918100000000107be92f3d.000001011802.00 

    Called-Addr:47.00918100000000107be92f3d.000001011802.00 

1:1.2:2     1   101       32       1:1.2:2      1   100       33   PTP    No 

    Calling-Addr:47.00918100000000107be92f3d.000001011802.00 

    Called-Addr:47.00918100000000107be92f3d.000001011802.00 

1:1.2:2     2   200       34       1:1.6:6      0    49   8388609  PTP    No 

    Calling-Addr:47.00918100000000107be92f3f.000001011804.00 

    Called-Addr:47.00918100000000107be92f3d.000001011802.00 

1:1.6:6     0    49  8388609       1:1.2:2      2   200        34  PTP    No 

    Calling-Addr:47.00918100000000107be92f3f.000001011804.00 

    Called-Addr:47.00918100000000107be92f3d.000001011802.00 

dsppnconstats

Call Control Operations: Show Call Statistics

Displays call statistics for the port.

Card(s) on Which Command Executes

PXM-45

Syntax

dsppnconstats <portid>

Syntax Description

portid

See PNNI Format.

Related Commands

clrpnconstats

Attributes

Log: nolog

State: active

Privilege: ANYUSER

Examples

Call Statistics for <portid>

Incoming Call Attempts:     0    Outgoing Call Attempts:     0

Incoming Call Success:      0    Outgoing Call Success:      0

Incoming Call Failures:     0    Outgoing Call Failures:     0

Incoming Filtering Failures:0    Outgoing Filtering Failures:0

Incoming Routing Failures:  0    Outgoing Routing Failures:  0

Incoming CAC Failures:      0    Outgoing CAC Failures:      0

Incoming Timer Failures:    0    Outgoing Timer Failures:    0

Incoming Crankback Failures:0    Outgoing Crankback Failures:0

Output Description

Incoming Call Attempts	Number of incoming signaling messages—Setup and AddParty—received on this port for call establishment.
Incoming Call Success	Number of incoming signaling messages—Connect and AddPartAck—received on this port, which indicate successful call establishment.
Incoming Call Failures	Number of incoming point-to-point and point-to-multipoint SVC/SPVC call attempts that failed on this port.
Incoming Call Filtering Failures	Number of incoming point-to-point and point-to-multipoint SVC/SPVC call attempts that failed the address filtering on this port.
Incoming Routing Failures	Number of incoming point-to-point and point-to-multipoint SVC/SPVC call attempts that failed on this port because there was no route to the destination.
Incoming CAC Failures	Number of incoming point-to-point and point-to-multipoint SVC/SPVC call attempts that failed on this port because there were not enough resources as requested in the traffic parameters of the call.
Incoming Timer Failures	Number of signaling timers that timed out on incoming point-to-point and point-to-multipoint SVC/SPVC calls recieved on this port.
Incoming Crankback Failures	Number of crankback IEs recieved on this port for incoming point-to-point and point-to-multipoint SVC/SPVC call attempts.
Outgoing Call Attempts	Number of outgoing signalling messages—Setup and AddParty—sent from this port for call establishment.
Outgoing Call Success	Number of outgoing signaling messages—Connect and AddPartAck—sent from this port, which indicate successful call establishment.
Outgoing Call Failures	Number of outgoing point-to-point and point-to-multipoint SVC/SPVC call attempts that failed on this port.
Outgoing Call Filtering Failures	Number of outgoing point-to-point and point-to-multipoint SVC/SPVC call attempts that failed the address filtering on this port.
Outgoing Routing Failures	Number of outgoing point-to-point and point-to-multipoint SVC/SPVC call attempts that failed on this port because there was no route to the destination.
Outgoing CAC Failures	Number of outgoing point-to-point and point-to-multipoint SVC/SPVC call attempts that failed on this port because there was not enough resources as requested in the traffic parameters of the call.
Outgoing Timer Failures	Number of signaling timers that timed out on outgoing point-to-point SVC/SPVC calls sent from this port.
Outgoing Crankback Failures	Number of crankback IEs sent from this port for outgoing signaling release messages.

upcon

Up Connection

Activate a connection that was previously brought down by the dncon command. (The typical purpose of dncon is some form of operational modification or troubleshooting.)

Card(s) on Which Command Executes

AXSM

Syntax

upcon  
<ifNum >  
<vpi>  
<vci>

Syntax Description

ifNum	Port number, in the range 1-60.
vpi	Virtual path identifier. On the AXSM, the range is 0-255.
vci	Virtual connection identifier. On t he AXSM, the range is 32-65535 for a VCC. For a VPC, the only vci is 0.

Related Commands

dncon

Attributes

Log: log

State: active

Privilege: GROUP1

upport

Up Port

The upport command enables (or "ups") a logical port. The usage of upport follows dnport. See the dnport description for information on the use of these commands.

Use dspports or dspport as needed to determine the port to enable or to see the status of the port after you enable it.

Card(s) on Which Command Executes

AXSM

Syntax

upport  
<ifNum>

Syntax Description

ifNum

The logical port number.

Related Commands

dspport, dspports, dnport

Attributes

Log: nolog

State: active, standby

Privilege: GROUP1

Enable port 1 on the current card.

chicago.1.AXSM.a > upport 1