Table Of Contents

SPVC and SVC 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

clrpncon

clrpnconstats

cnfabr

cnfabrtparmdft

cnfcdvtdft

cnfcon

cnfmbsdft

cnfoamsegep

delcon

delcons

delconsegep

dncon

dspabrtparmdft

dspcdvtdft

dspcon

dspconinfo

dspconload

dspcons

dspconsegep

dspmbsdft

dspoamsegep

dsppncon

dsppncons

dsppnconstats

upcon

upport

SPVC and SVC Commands

---

This chapter describes the commands that apply to semi-permanent virtual circuits (SPVCs) and switched virtual circuits (SVCs). These commands allow you to add, delete, configure, display status, and specify statistics for these connections. 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.

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 Routing Switch Hardware Installation Guide, Release 2.1 or Cisco MGX 8950 Hardware Installation Guide, Release 1.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, E3	1-8	1-2
AXSM-2-622-E	OC12	1	1-2
AXSM-8-155-E	OC3	1-4	1-2
AXSM-16-T3E3-E	T3, 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 PXM45, you also need to configure a port on the CLI of the AXSM. Furthermore, when you display a connection on the AXSM, you identify that same connection using a different format on the PXM45 CLI. For specific examples of these parallel actions, see the Cisco MGX 8850 and MGX 8950 Software Configuration Guide, Release 2.1.

---

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 and MGX 8950 Switch Software Configuration Guide, Release 2.1, 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 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:

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

•Port is the physical line.

•Subport corresponds to the resource partition on the AXSM. For a UNI or NNI, this resource partition is the same number as the logical port number (ifNum) on the AXSM. For a virtual network-to-network interface (VNNI), these numbers do not directly correspond to each other.

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

Table 7-4 Mapping PNNI Port ID to AXSM Elements

PNNI port	AXSM
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)

addcon

Add Connection

Adds a logical connection as an SPVC on a service module. The switch assigns a 20 octet NSAP address to the slave endpoint, which is sent back to the master and uniquely identifies the endpoint on the network. An AXSM front card can support a maximum of 64K SPVCs. This command does not apply to SVCs.

Cards on Which This Command Runs

AXSM, AXSM-E

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, addpart, 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 the cnfabr command to configure the ABR parameters.

Usage Guidelines

The following sections detail the application of certain addcon parameters.

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

SCT Default Traffic Parameters

The Service Class Templates (SCTs) provide the default traffic parameters for the logical ports. The default traffic parameters are set to a fraction of the bandwidth available on the logical port. The SCT ID (sctID) and interface type (ifType) parameters that are specified using the addport command determine which default traffic parameters are used.

---

Note The default values of the SCTs cannot be changed using the Cisco WAN Manager (CWM).

---

Table 7-5 Default Traffic Parameters for AXSM

	PCR	SCR	MCR	ICR	MBS	MFS	CDVT
VSI-SIG	N/P	N/P	N/P	N/P	N/P	N/U	N/P
CBR.1	50	N/A	N/A	N/A	dspmbsdft	N/U	dspcdvtdft
VBR-RT.1	50	50	N/A	N/A	dspmbsdft	N/U	dspcdvtdft
VBR-RT.2	50	50	N/A	N/A	dspmbsdft	N/U	dspcdvtdft
VBR-RT.3	50	50	N/A	N/A	dspmbsdft	N/U	dspcdvtdft
VBR-nRT.1	50	50	N/A	N/A	dspmbsdft	N/U	dspcdvtdft
VBR-nRT.2	50	50	N/A	N/A	dspmbsdft	N/U	dspcdvtdft
VBR-nRT.3	50	50	N/A	N/A	dspmbsdft	N/U	dspcdvtdft
UBR.1	50	N/A	N/A	N/A	dspmbsdft	N/U	dspcdvtdft
UBR.2	50	N/A	N/A	N/A	dspmbsdft	N/U	dspcdvtdft
ABR	50	N/A	50	50	dspmbsdft	N/U	dspcdvtdft
CBR.2	50	N/A	N/A	N/A	dspmbsdft	N/U	dspcdvtdft
CBR.3	50	N/A	N/A	N/A	dspmbsdft	N/U	dspcdvtdft

Table 7-6 Ranges for PCR, SCR, and MCR for Each Line Type 

Parameter	Range
PCR	Minimum PCR is 7 cells per second (cps). Maximum PCR depends on the physical line on which the interface is configured: Ranges are as follows: •OC12: 7-1412832 cps •OC3: 7-353208 cps •T3: 7-96000 cps for PLCP or 7-104268 cps for ADM •E3: 7-80000 cps •T1: 7-3622 cps •E1: 7-4528 cps Default : Taken from the SCT which was chosen for the virtual interface. The service type is used as an index in choosing a value of PCR. The default value of PCR in the SCT is defined as a percentage of the interface bandwidth.
SCR	Minimum SCR is 7 cells per second (cps). Maximum is limited to the PCR. Default: Taken from SCT as a percentage of PCR. The AXSM-E has a lower minimum of 3 cps, so if the derived default is less than 3, it is rounded off to 3 cps.
MCR	Same as SCR

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.

For the MGX 8850 2.0 release, if you try to enable frame discard at the slave end point you will not get an error message. Nothing will happen, and frame discard will not take effect. In future releases, an error message will be displayed if you try to enable frame discard at the slave end point.

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

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

---

Note The switch uses the values of lpcr and rpcr you at the master endpoint only. If you specify lpcr and rpcr at the slave endpoint, they are ignored.

---

---

Note To specify an OAM segment endpoint, use the cnfcon command after you have created the connection by using the addcon command. With cnfcon, use the optional -segep parameter.

---

Syntax Description

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

ifNum	The logical interface (or port) number. This ifNum corresponds to the ifNum added through the addport command. The ranges are as follow: •AXSM: 1-60 •AXSM-E: 1-32 Note When you add an endpoint on an NNI port, make sure that PNNI signaling is disabled on the PXM45 (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 VS/VD-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 for 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	This parameter specifies the peak cell rate (PCR) from the local endpoint to the remote endpoint. PCR is the maximum cell rate for the connection at any time. The range is 7-5651328 cells per second.
-rpcr	This parameter specifies the peak cell rate (PCR) from the remote endpoint to the local endpoint. PCR is the maximum cell rate for the connection at any time. The range is 7-5651328 cells per second.
-lscr	This parameter specifies the sustained cell rate (SCR) from the local endpoint to the remote endpoint. SCR is the maximum cell rate that a connection can sustain for long time periods. The range is 7-5651328 cells per second.
-rscr	This parameter specifies the sustained cell rate (SCR) from the remote endpoint to the local endpoint. SCR is the maximum cell rate that a connection can sustain for long time periods. The range is 7-5651328 cells per second.
-lmbs	This parameter specifies the maximum burst size (MBS) from the local endpoint to the the remote endpoint. MBS is the maximum number of cells that can burst at the PCR and still be compliant. The range is 1-5000000 cells
-rmbs	This parameter specifies the maximum burst size (MBS) from the remote endpoint to the local endpoint. MBS is the maximum number of cells that can burst at the PCR and still be compliant. The range is 1-5000000 cells.
-cdvt	This parameter specifies the cell delay variation tolerance (CDVT) from the local endpoint to the remote endpoint. CDVT controls the time scale over which the PCR is policed. The range is 1-5000000 microseconds. Note No remote CDVT is necessary.
-lcdv	This parameter specifies the peak to peak cell delay variation (CDV) from the local endpoint to the remote endpoint. The range is 1-16777215 microseconds. To revert to the default value, enter a -1.
-lctd	This parameter specifies the cell transfer delay (CTD) from the local endpoint to the remote endpoint. The range is 0-65535 microseconds. To return to the default value, enter a -1.
-rctd	This parameter specifies the cell transfer delay (CTD) from the remote (destination) endpoint to the local (source) endpoint. The range is 0-65535 microseconds. Default: -1 (To return to the default value, enter a -1.)
-rcdv	This parameter specifies the peak to peak cell delay variation (CDV) from a remote endpoint to a local endpoint. The range is 1-16777215 microseconds. Default: -1 (To return to the default value, enter a -1.)
-cc	Operations, administration, and maintenance continuity check (OAM CC): enter 1 to enable or 0 to disable. The default is 0. To provision continuity checking, enable this function at both ends of the connection, otherwise a connection alarm results. (When you add a connection at one endpoint and enable this parameter, the connection goes into alarm until you specify the other endpoint and enable continuity checking.)
-stat	Statistics collection: enter 1 to enable or 0 to disable. The default is 0. Cisco WAN Manager 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 be insignificant) on the real-time response, especially for SVCs. Therefore, enable statistics collection for only that subset of connections that really warrants it.
-frame	Use at only the master endpoint to enable or disable frame discard. Possible values: •1 to enable •0 to disable (the default)
-mc	The maximum cost (maxcost) parameter creates a priority for the connection route. PNNI can select a route only if the cost does not exceed maxcost. 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. The range is 0-2147483647, and 2147483647 is the default. Note the following effects of values in the maxcost range: •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. •Enter a 0 for the least expensive path. •For any non-zero maxcost, the switch assigns a path if the total cost for all links does not exceed maxcost. The maxcost parameter applies to an individual connection. Apart from maxcost, however, routing also substantially depends on the cost-per-link from the source to the destination and back. A cost-per-link exists for every port egress in the network, and you can configure this cost-per-link for each service class by using the cnfpnni-intf command. (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 impact of cost-per-link is cumulative along the route, and you can configure the cost-per-link at the egress of each PNNI port throughout the network. •Each link has two egress directions: one goes from the local endpoint to the far end, and the other goes from the far end egress back to the local end. Note that the cost-per-link can differ at each egress on the link, so the switch adds the cost-per-link at each egress instead of doubling a single cost-per-link. The cost-per-link applies to all connections of a particular service class on a port. For example, the cost-per-link is the same for all VBR.1 connections on a port, and this cost-per-link can differ from all UBR.1 connections on the port. (Alternatively, the cnfpnni-intf command lets you make the cost-per-link the same for all service types.) To illustrate, consider 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 destination and four coming back). 3. The cost-per-link at 6 ports is 5040 (the default) and 10000 at 2 ports. The PXM45 would use the route because the resulting cost of 50240 is less than the maxcost of 100000. Default: 2147483647 (To return maxcost to the default, you can use the cnfcon command and type -mc -1.)

Error Messages

The system can display error messages 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 is true:

•"Port does not support requested serviceType"

•"lscr/lmcr not allowed to exceed lpcr (dcmp)"

•"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: yes

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.

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

slave endpoint added successfully

slave endpoint id: 00000E1000001C008051B730FFFFFF010B180100.10.40

In the following two examples, the connection works with default values of PCR, SCT, MCR taken from the SCT. Defaults applied for the connection can be viewed by using the dspcon command.

MGX8850.1.11.AXSME.a > addcon 1 10 40 1 s

slave endpoint added successfully

slave endpoint id : 00000E1000001C008051B730FFFFFF010B180100.10.40

MGX8850.1.11.AXSME.a > addcon 1 10 50 1 m -slave 
00000E1000001C008051B730FFFFFF010B180100.10.40

master endpoint added successfully

master endpoint id : 00000E1000001C008051B730FFFFFF010B180100.10.50

In the following two examples, the connection works with default values of SCR, MCR derived from the PCR value specified using lpcr and rpcr keywords. Defaults applied for the connection can be viewed by using the dspchan command.

MGX8850.1.11.AXSME.a > addcon 1 10 40 1 s

slave endpoint added successfully

slave endpoint id : 00000E1000001C008051B730FFFFFF010B180100.10.40

MGX8850.1.11.AXSME.a > addcon 1 10 50 1 m -slave 
00000E1000001C008051B730FFFFFF010B180100.10.40 -lpcr 1000 -rpcr 1000

master endpoint added successfully

master endpoint id : 00000E1000001C008051B730FFFFFF010B180100.10.50

clrpncon

Clear Connection

Delete a call—either all SVCs or a specific SVC on a port. (If you attempt to clear an SPVC with this command, the switch deletes the connection but then automatically attempts to reroute it. For an SPVC or SPVP, use delcon so you can delete the endpoints.)

Cards on Which This Command Runs

PXM45

Syntax

clrpncon <portid> {all | 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.
all | vpi	Specifies either all VPIs on the port or a specific VPI. Possible values are either the string "all" or a VPI in the range 0-4095.
vci	VCI of a specific SVC to clear. If you are clearing a virtual path connection (VPC), do not enter a VCI.

Related Commands

dsppncon, dspncons

Attributes

Log: yes

State: active

Privilege: SUPER_GP

Examples

First, list the connections on the port to identify the specific connection to delete. For this example, use clrpncon to release the connection on port 1.2 with the VPI/VCI or 1 100. This connection is the first in the display output. Thereafter, use dsppncons to check the results.

Geneva.7.PXM.a > dsppncons 

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 

Geneva.7.PXM.a > clrpncon 1.2 1 100

Geneva.7.PXM.a > dsppncons

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

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 

Geneva.7.PXM.a >

clrpnconstats

Call Control Operations

Clears existing call statistics for one logical port or all logical ports.

Cards on Which This Command Runs

PXM45

Syntax

clrpnconstats [portid]

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.

Related Commands

dsppnconstats

Attributes

Log: yes

State: active

Privilege: SUPER_GP

cnfabr

Configure ABR—configures VS/VD parameters for ABR connections.

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

This command applies to only an AXSM-E. Nevertheless. the differences for ABR on an AXSM and an AXSM-E are pointed out here:

•The AXSM-E supports ABR virtual source/virtual destination (VS/VD). Therefore, it can generate resource management (RM) cells and turn them around.

•AXSM supports ABR standard but not VS/VD. Therefore, an AXSM cannot generate RM cells nor turn them around. However, it can stamp RM cells with congestion information if congestion exists on the card.

---

Note With ABR VS/VD, you can specify parameters but leave the VS/VD service disabled. You can later enable the service and thus activate the previously configured parameters.

You can enable VS/VD at the PNNI port level by using the cnfintfvsvd command on the PXM45.

---

Cards on Which This Command Runs

AXSM-E

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.
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	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	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	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	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	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	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	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	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	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	Enable or disable for VS/VD on the internal loop. •1=Off •2=On •3=Unspecified (Unspecified means that the connection takes the on or off status of VS/VD from the VS/VD specification in the SCT file.) See description of the cnfintfvsvd command to enable VS/VD at the PNNI port level. Default: off
-extvsvd	Enable or disable for VS/VD on the external loop. •1=Off •2=On •3=Unspecified (Unspecified means that the connection takes the on or off status of VS/VD from the VS/VD specification in the SCT file.) See description of the cnfintfvsvd command to enable VS/VD at the PNNI port level. Default: off

Related Commands

addcon, cnfabrtparmdft, dspabrtparmdft, cnfintfvsvd

Attributes

Log: yes

State: active

Privilege: GROUP1

Example

MGX8850.1.10.AXSME.a > cnfabr 1 77 777 -mcr 100

 THE SG NUM is: 0.

Configuration successful

cnfabrtparmdft

Configure ABR Traffic Parameter Defaults

The cnfabrtparmdft command lets you configure default, ABR-specific parameters for all ABR SPVCs on a PNNI port. These parameters apply to SPVCs only.

When you add an ABR connection, the controller provides the default ABR traffic parameters before the connection is committed. The default ABR traffic parameters are used in the SETUP message at the source when an SPVC with ABR service is set up. (Note also that you can change VS/VD-specific parameters for an individual ABR connection by using the cnfabr command on the AXSM-E.)

Cards on Which This Command Runs

PXM45

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

Attributes

Log: no

State: active

Privilege: GROUP1

cnfcdvtdft

Configure Cell Delay Variation Tolerance Default

For all connections of a particular service type on a PNNI logical port, cnfcdvtdft configures the default number of microseconds for the cell delay variation tolerance (CDVT). The direction is ingress. The new configuration applies to new incoming calls but not existing calls. You can execute cnfcdvtdft whether the port is in the provisioning state (prior to addport on the service module) or administratively up.

Cards on Which This Command Runs

PXM45

Syntax

cnfcdvtdft <portid> <service_category> [microseconds]

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.
service_category	Service type: cbr, rtvbr, nrtvbr, ubr, or abr.
micro seconds	The number of microseconds for CDVT. Range: 0-2147483647 Default: 250,000

Related Commands

dspcdvtdft

Attributes

Log: yes

State: active

Privilege: GROUP1

Examples

Specify a CDVT of 125000 microseconds for ABR connections on port 4:1.1:11. Check the results by executing dspcdvtdft for the port.

Geneva.7.PXM.a >   cnfcdvtdft 4:1.1:11 abr 125000

Geneva.7.PXM.a > dspcdvtdft 4:1.1:11 

              cbr:     rt-vbr:    nrt-vbr:        ubr:        abr:

CDVT:       250000      250000      250000      250000     125000

Geneva.7.PXM.a > 

cnfcon

Configure Connection

Modifies the bandwidth, policing, and routing parameters of an existing endpoint. This command applies to only an SPVC or SPVP. For VS/VD-specific parameters for an ABR connection, use cnfabr.

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

After you specify the mandatory connection identifier, all other parameters are optional.

Card(s) on Which the Command Executes

AXSM, AXSM-E

Usage Guidelines for cnfcon

The following sections discuss the application of certain cnfcon parameters.

---

Note On DAX connections, using cnfcon at the slave end has no effect. For DAX connections, use cnfcon at the master end only: the parameters will take effect on the slave end as well.

---

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

For the MGX 8850 2.0 release, if you try to enable frame discard at the slave end point you will not get an error message. Nothing will happen, and frame discard will not take effect. In future releases, an error message will be displayed if you try to enable frame discard at the slave end point.

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.

AXSM Syntax

cnfcon <ifNum> <vpi> <vci>
[-lpcr <local to remote PCR>]
[-rpcr <remote to local PCR>]
[-lscr <local to remote SCR>]
[-rscr <remote to local SCR>]
[-lmbs <local to remote MBS>]
[-rmbs <remote to local MBS>]
[-lcdv <local to remote maxCDV>]
[-rcdv <remote to local maxCDV>]
[-lctd <local to remote maxCTD>]
[-rctd <remote to local maxCTD>]
[-lmcr <local to remote MCR>]
[-rmcr <remote to local MCR>]
[-cdvt <local CDVT>]
[-cc <OAM CC Cnfg>]
[-stat <Stats Cnfg>]
[-frame <frame discard>]
[-mc <Max Cost>]
[-segep <OAM segment endpoint>]

AXSM Syntax Description

ifNum	Logical interface (or port) number. The ranges are as follows: •AXSM: 1-60 •AXSM-E: 1-32
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 1-65535. For MPLS, the recommended minimum VCI is 35. •For a VPC, the vci is 0.
-lpcr	This parameter specifies the peak cell rate (PCR) from the local endpoint to the remote endpoint. PCR is the maximum cell rate for the connection at any time. The range is 7-5651328 cells per second.
-rpcr	This parameter specifies the peak cell rate (PCR) from the remote endpoint to the local endpoint. PCR is the maximum cell rate for the connection at any time. The range is 7-5651328 cells per second.
-lscr	This parameter specifies the sustained cell rate (SCR) from the local endpoint to the remote endpoint. SCR is the maximum cell rate that a connection can sustain for long time periods. The range is 7-5651328 cells per second.
-rscr	This parameter specifies the sustained cell rate (SCR) from the remote endpoint to the local endpoint. SCR is the maximum cell rate that a connection can sustain for long time periods. The range is 7-5651328 cells per second.
-lmbs	This parameter specifies the maximum burst size (MBS) from the local endpoint to the remote endpoint. MBS is the maximum number of cells that can burst at the PCR and still be compliant. The range is 1-5000000 cells
-rmbs	This parameter specifies the maximum burst size (MBS) from the remote endpoint to the local endpoint. MBS is the maximum number of cells that can burst at the PCR and still be compliant. The range is 1-5000000 cells.
-cdvt	This parameter specifies the cell delay variation tolerance (CDVT) from the local endpoint to the remote endpoint. CDVT controls the time scale over which the PCR is policed. The range is 1-5000000 microseconds. Note No remote CDVT is necessary.
-lcdv	This parameter specifies the peak to peak cell delay variation (CDV) from the local endpoint to the remote endpoint. The range is 1-16777215 microseconds. To revert to the default value, enter a -1.
-lctd	This parameter specifies the cell transfer delay (CTD) from the local endpoint to the remote endpoint. The range is 0-65535 microseconds. To return to the default value, enter a -1.
-rctd	This parameter specifies the cell transfer delay (CTD) from the remote (destination) endpoint to the local (source) endpoint. The range is 0-65535 microseconds. Default: -1 (To return to the default value, enter a -1.)
-rcdv	This parameter specifies the peak to peak cell delay variation (CDV) from a remote endpoint to a local endpoint. The range is 1-16777215 microseconds. Default: -1 (To return to the default value, enter a -1.)
-cc	Operations, administration, and maintenance continuity check (OAM CC): enter 1 to enable or 0 to disable. The default is 0. To provision continuity checking, enable it at both ends of a connection, otherwise a connection alarm results. (As you create a connection with this parameter, the connection goes into alarm until both ends of the connection are added.)
-stat	This option enables or disables statistics collection: type a 1 to enable or a 0 to disable. Default: 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 varying impact on the real-time response, especially for SVCs (which can be affected even though you do not add SVCs). The impact may be small. You should enable statistics collection for only that subset of connections that really warrants it.
-frame	This optional parameter lets you enable or disable frame discard for the connection. Note that you can use it at only the master endpoint of a connection. Possible values are: •1 to enable •0 to disable Default: 0 (disabled)
-mc	The maximum cost (maxcost) parameter creates a priority for the connection route. PNNI can select a route only if the cost does not exceed maxcost. 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. The range is 0-2147483647, and 2147483647 is the default. Note the following effects of values in the maxcost range: •To assign the highest priority to an SPVC based on cost ("any path is acceptable"), enter 2147483647. You can create the same result by not specifying maxcost at all, in which case the cost appears as -1 in the dspcon output. •Enter a 0 for the least expensive path. •For any non-zero maxcost, the switch assigns a path if the total cost for all links does not exceed maxcost. The maxcost parameter applies to an individual connection. Apart from maxcost, however, routing also substantially depends on the cost-per-link from the source to the destination and back. A cost-per-link exists for every port egress in the network, and you can configure this cost-per-link for each service class by using the cnfpnni-intf command. (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 impact of cost-per-link is cumulative along the route, and you can configure the cost-per-link at the egress of each PNNI port throughout the network. •Each link has two egress directions: one goes from the local endpoint to the far end, and the other goes from the far end egress back to the local end. Note that the cost-per-link can differ at each egress on the link, so the switch adds the cost-per-link at each egress instead of doubling a single cost-per-link. The cost-per-link applies to all connections of a particular service class on a port. For example, the cost-per-link is the same for all VBR.1 connections on a port, and this cost-per-link can differ from all UBR.1 connections on the port. (Alternatively, the cnfpnni-intf command lets you make the cost-per-link the same for all service types.) To illustrate further with a four-link route: 1. You specify a maxcost of 100000. 2. A route under consideration by PNNI has four links for a total of eight egress points. 3. The cost-per-link at six of the ports is 5040 (the default in cnfpnni-intf), and the cost per link at two ports is 10000. PNNI would use the route because the resulting cost of 50240 is less than 100000. Default: 2147483647 (To return maxcost to the default, you can type -mc -1.)
-segep	OAM segment endpoint: Enter a 1 to enable or a 0 to disable.

Related Commands

addcon, delcon, dspcon, dspcons, dspconstats

Attributes

Log: yes

State: active

Privilege: GROUP1

Example

MGX8850.1.11.AXSM.a > cnfcon 1 10 40 -cc 1

Configuration successful

cnfmbsdft

Configure Maximum Burst Size Default

Configures the default maximum burst size (MBS) for SPVCs on a port. The applicable service types are real-time and non real-time variable bit rate (rt-VBR and nrt-VBR).

The most likely connection type for which you would use cnfmbsdft is SVC. You can also rely on the value set with this command as a default for SPVCs if you do not specify an MBS through addcon for each SPVC of service type VBR.

The new configuration applies to new incoming calls, not existing calls. You can use cnfmbsdft whether the port is active or in the provisioning state.

Cards on Which This Command Runs

PXM45

Syntax

cnfmbsdft <portid> <service_category> [num-of-cell]:

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.
service_category	For the ATM 4.0 service category, type either rtvbr or nrtvbr.
num-of-cell	The units of measure for MBS are cells. Range: 0-2147483647 cells Default: set by the platform to 1024 cells.

Related Commands

dspmbsdft

Attributes

Log: yes

State: active

Privilege: GROUP1

Examples

Configure a default MBS of 10000 cells for nrt-VBR.

cnfmbsdft 11:2.1:1 nrtvbr 10000

cnfoamsegep

Configure OAM Segment Endpoint

Define the port as a segment endpoint for F4 and F5 operations administration and maintenance (OAM) cells. 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

PXM45

Syntax

cnfoamsegep <portid> [{yes | no}]

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

State: active

Privilege: GROUP1

delcon

Delete Connection

Use the delcon command to delete an SPVC or SPVP. Delete the connection at both ends—first at the master end, then at the slave.

Cards on Which This Command Runs

AXSM, AXSM-E

Syntax

delcon <ifnum> <vpi> <vci>

Syntax Description

ifnum	Logical interface (or port) number. The ranges are as follows: •AXSM: 1-60 •AXSM-E: 1-32
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.

Related Commands

dspcon, addcon, cnfcon

Attributes

Log: yes

State: active

Privilege: GROUP1

Example

MGX8850.1.3.AXSME.a > delcon 1 10 40

Deletion successful

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 usage of this command could result in deletion of more endpoints than necessary, and repairing such damage could be very costly.

---

Cards on Which This Command Runs

AXSM, AXSM-E

Syntax

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

Syntax Description

ifNum	Logical interface (or port) number. The ranges are as follows: •AXSM: 1-60 •AXSM-E: 1-32
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: no

State: active

Privilege: SERVICE_GP

delconsegep

Delete Connection Segment Endpoint

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

---

Note The delconsegep command works for SVCs only.

---

Cards on Which This Command Runs

PXM45

Syntax

delconsegep <portid> <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	VPI of the connection.
vci	VCI of the connection.

Related Commands

cnfoamsegep, dspoamsegep, cnfconsegep, dspconsegep

Attributes

Log: yes

State: active

Privilege: GROUP1

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.

Cards on Which This Command Runs

AXSM, AXSM-E

Syntax

dncon <ifNum> <vpi> <vci>

Syntax Description

ifNum	The logical interface (or port) number in the following range: •For AXSM, 1-60 •For AXSM-E, 1-32
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: yes

State: active

Privilege: GROUP1

dspabrtparmdft

Display ABR Parameter Defaults

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

Cards on Which This Command Runs

PXM45

Syntax

dspabrtparmdft <portid>

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.

Related Commands

addcon, cnfabr, cnfabrtparmdft

Attributes

Log: no

State: active, standby

Privilege: ANYUSER

Example

Display the default ABR parameters on port ID 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 misc.)

ADTF: 50 (= 0.50 Sec)

CDF: 7 (= 1/2)

FSD: 0 (microSec)

dspcdvtdft

Display CDVT Default

Displays the default CDVT for the port.

Cards on Which This Command Runs

PXM45

Syntax

dspcdvtdft <portid>

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.

Related Commands

dspcdvtdft, cnfcdvtdft

Attributes

Log: no

State: active, standby

Privilege: ANYUSER

Example

Display the CDVT defaults for port 11:1.1:11.

Geneva.7.PXM.a > dspcdvtdft 11:1.1:11

              cbr:     rt-vbr:    nrt-vbr:        ubr:        abr:

CDVT:       250000      250000      250000      250000      250000

dspcon

Display Connection

Display information about an SPVC. The contents of the display on the AXSM and the PXM45 differ slightly. 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 PXM45

On the PXM45, 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 (relates to voice traffic and is reserved for future use).

•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. Note that, after you down a connection with at the connection master endpoint, the dspcon command shows the connection as "down" when you execute it at the master endpoint and "failed" when you execute it at the slave endpoint. (See also dncon description).

•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. A -1 in a field means that the parameter was not specified. The characters "N/A" indicate that the parameter does not apply to the service type.

These other fields also 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 PXM45, dspcons identifies all the connections on the node. (See dspcons description).

Display Connection on the AXSM-E

The display output on the AXSM-E also displays RDI (Remote Defect Indication) information at the ATM Layer through the OAM mechanism in Ingress and Egress directions.

Cards on Which This Command Runs

AXSM, AXSM-E, PXM45

Syntax

On the AXSM and AXSM-E:

dspcon <ifNum> <vpi> <vci>

On the PXM45:

dspcon <portid> <vpi> <vci>

Syntax Description

ifNum	(AXSM, AXSM-E) Logical interface (port) number. For AXSM, the range is 1-60. For AXSM-E, the range is 1-32.
portid	(PXM45) 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	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: no

State: active, standby

Privilege: ANYUSER

Examples

Display connection 5 31 63000 on the current AXSM.

MGX8850.1.AXSM.a > dspcon 5 31 63000

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

Local   :               NSAP  Address               port     vpi    vci

(M)       4700918100000000107BE92F3F00000101180500  1.01.05 31 63000

Remote  :               NSAP  Address               port     vpi    vci

(S)       4700918100000000107BE92F3F00000101180500  1.01.05   3201 100

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

Conn. Type    :     VCC                          Admn Status  : ADMN-UP

Service Type  :    cbr1                          Oper Status  : FAIL

Controller    :       2

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

Local PCR     :   10000                          Remote PCR   : 1000

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

Local CDV     :      -1                          Remote CDV   : -1

Local CTD     :      -1                          Remote CTD   : -1

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

Local CDVT    :      -1                          Remote CDVT  : -1

Admin weight  :      -1                          Frame discard: N

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

OAM CC Config :DISABLED                          Statistics   : DISABLED

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

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

On the CLI of the PXM45, 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 

Display output for AXSM-E, port 1, VPI 10, VCI 100.

MGX8850.6.AXSME.a > dspcon 1 10 100

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

Local   :                NSAP  Address                     vpi       vci   

(S)       47009181000000002A231F3C4A00000106180100          10       100  

Remote  :                NSAP  Address                     vpi       vci   

(M)       47009181000000002A231F3C4A00000106180200          10       100  

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

Conn. Type    :        VCC                      Admn Status  :    ADMN-UP

Service Type  :       cbr1                      Oper Status  :         OK

Controller    :          2                      Record #     :          0

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

Local PCR     :       1000                      Remote PCR   :       1000 

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      :        N/A                      Frame discard:          N

Local CDVT    :     250000                      OAM segment  :    ENABLED

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

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 :        AIS

Port side Rx  :     normal                      Swth side Rx :     normal

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

Ing-E2E-AIS   ING-SEG-AIS   Ing-E2E-RDI   Ing-SEG-RDI  

   NO              NO             NO            NO 

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

Egr-E2E-AIS   Egr-SEG-AIS   Egr-E2E-RDI   Egr-SEG-RDI  

  YES             NO             NO              NO 

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

Ing-E2E-CCFAIL   Ing-SEG-CCFAIL   Egr-E2E-CCFail   Egr-SEG-CCFail 

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

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

CONDITIONED  IfFail   Mismatch   LMI-ABIT

   NO         YES         NO         NO 

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

dspconinfo

Display Connection Information—display summaries of connection configurations (SPVCs or SPVPs only)

The dspconinfo runs on the PXM45 and lists the total number SPVCs on each PNNI port on the switch. The default operation of the command is to show all SPVCs or SPVPs, With the optional parameters, you can specify one or more types of information to display.

The display shows:

•PNNI physical port number

•Number of active connections

•Number of failed connections

•Number of administratively inactive (or down) connections as a result of dncon

•Total number of connections

Note that dspconinfo checks for the down state at the master end of the connection (status at the slave endpoint is failed). See also the descriptions for dncon and dspcon.

Cards on Which This Command Runs

PXM45

Syntax

dspconinfo
[-port portid] [-detail {true | false}] [-owner {master | slav] -sc {cbr | rtvbr | nrtvbr | abr | ubr}

Syntax Description

-port	Identifies a PNNI physical port. The format for portid is slot:subslot.port:subport. For a description of each field, see the section, "PNNI Format," at the beginning of the chapter.
-detail	Determines whether the display contains information for all interfaces and slots or just slots. Type "true" after the keyword for all interfaces and slots. Type "false" for just slots. Default: true
-owner	Lets you specify the endpoint of the connection. Type "master" or "slave."
-sc	Directs the command to display connections of a particular service type. Type one of the following after the keyword: cbr, nrtvbr, rtvbr, abr, or ubr. Default: no default

Related Commands

None

Attributes

Log: no

State: active, standby

Privilege: ANYUSER

Examples

Display the SPVC summaries on the switch with the following conditions:

•No options: a total of 13 active connections exist.

•UBR connections: a total of 2 endpoints are listed.

•Connections on port 5:1.2:2.

•Connections at slot 5.

•Slave endpoints.

atlanta.7.PXM.a > dspconinfo

Local Port     #Active   #Failed      #Down     #Total  

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

5:1.2:2            13          0          0         13

atlanta.7.PXM.a > dspconinfo -sc ubr

Local Port     #Active   #Failed      #Down     #Total  

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

5:1.2:2             2          0          0          2

atlanta.7.PXM.a > dspconinfo -port 5:1.2:2

Local Port     #Active   #Failed      #Down     #Total  

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

5:1.2:2            13          0          0         13

atlanta.7.PXM.a > dspconinfo -detail false

Local Slot     #Active    #Failed      #Down     #Total  

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

5                   13          0          0         13

atlanta.7.PXM.a > dspconinfo -owner slave

Local Port     #Active   #Failed      #Down     #Total  

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

5:1.2:2             0          0          0          0

dspconload

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>

Syntax Description

ifNum	Logical interface (port) number. For AXSM, the range is 1-60. For AXSM-E, the range is 1-32.
vpi	The VPI of the connection. The range is 0-4095.
vci	The VCI of the connection. The range is 0-65635.

Related Commands

dspcons, dspcon, dspload

Attributes

Log: no

State: active, standby

Privilege: ANYUSER

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 101

Getting the stats. Please wait ...

                        Ingress            Egress

Cell rate (cps)       : 0                  0 

AXSM-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 100

           Ingress                                         Egress

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

All non-compliant cells   :          0

CLP1 non-compliant        :          0

CLP0 non-compliant        :          0

CLP0 -> CLP1              :          0

Cells from port          

(Before policing)         :        999      Cells to port             :        999

CLP0 from port            :        999      CLP0 to port              :        999

CLP1 from port            :          0      CLP1 to port              :          0

EOF from port             :          0      EOF to port               :          0

EFCI1 from port           :          0      EFCI1 to port             :          0

                                            RM to port                :          0

Cells to network          :        999      Cells from network        :        999

CLP0 to network           :        999      CLP0 from network         :        999

CLP1 to network           :          0      CLP1 from network         :          0

EFCI1 to network          :          0      EFCI1 from network        :          0

Cells discarded in qe     :          0      Cells discarded in qe     :          0

CLP0 discarded in qe      :          0      CLP0 discarded in qe      :          0

CLP1 discarded in qe      :          0      CLP1 discarded in qe      :          0

EOF discarded in qe       :          0

                                            EFCI1 discarded in qe     :          0

VC queue depth            :          0      VC queue depth            :          0

ACR (Valid for WFQ conns) :          1      ACR (Valid for WFQ conns) :          1

OAM from port             :          0      OAM to port               :          0

RM from port              :          0

RM to network             :          0      RM from network           :          0

OAM to network            :          0      OAM from network          :          0

OAM discarded in qe       :          0      OAM discarded in qe       :          0

EFCI1 discarded in qe     :          0

RM discarded in qe        :          0      RM discarded in qe        :

dspcons

Display Connections—display basic information for all connections.

The default usage of dspcons has 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 (any model) or the PXM45. The set of optional parameters and the output are different on these cards. (See Syntax Description for the card-specific parameters.) On an 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 PXM45, 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.

Cards on Which This Command Runs

PXM45, AXSM, AXSM-E

PXM45 Syntax

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

PXM45 Syntax Description

-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 PXM45, you must spell out the entire state keyword. The keywords for specifying a state are 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 executed dncon to down the connection
-owner	Specifies connections where the local endpoint is either master or slave.
-sc	Specifies the service class: ABR, VBR, CBR, UBR.

AXSM/AXSM-E Syntax

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

AXSM/AXSM-E Syntax Description

-conn	Identify a connection to begin the display. The connection ID has the following format: ifNum.vpi.vci The fields in the connection ID have the following ranges: •ifNum on an AXSM: 1-60 •ifNum on an AXSM-E: 1-32 •VPI: 0-4095 •VCI: 32-65535
-filt	An integer after the filt keyword identifies a type of filter, as follows: 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
-if	Identify a logical interface for connection display. The output shows all connections on the specified interface. The ranges are: •AXSM: 1-60 •AXSM-E: 1-32
-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, dsppncon, dsppncons

PXM45 Attributes

Log: no

State: active, standby

Privilege: ANYUSER

AXSM /AXSM-E Attributes

Log: no

State: active, standby

Privilege: GROUP1

PXM45 Example

Display all connections by entering dspcons on the CLI of the PXM45.

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

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

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

AXSM Examples

Display all the connections on the card.

atlanta.5.AXSME.a > dspcons

record    Identifier   Type   SrvcType   M/S    Upld    Admn   Alarm

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

    0  02 0010 00100   VCC        cbr1   M   03d25966     UP      none

    1  02 0011 00000   VPC        cbr2   M   03d25982     UP      none

    2  02 0012 00100   VCC        cbr3   M   03d2598d     UP      none

    3  02 0013 00100   VCC      vbr1rt   M   03d2599a     UP      none

    4  02 0014 00100   VCC      vbr2rt   M   03d259a1     UP      none

    5  02 0015 00000   VPC      vbr3rt   M   03d259ae     UP      none

    6  02 0016 00100   VCC     vbr1nrt   M   03d259bd     UP      none

    7  02 0017 00000   VPC     vbr2nrt   M   03d259c4     UP      none

    8  02 0018 00000   VPC     vbr3nrt   M   03d259ce     UP      none

    9  02 0019 00000   VPC        ubr1   M   03d259d5     UP      none

   10  02 0020 00100   VCC        ubr2   M   03d259dd     UP      none

   11  02 0021 00000   VPC      abrstd   M   03d259e8     UP      none

   12  02 0022 00100   VCC      abrstd   M   03d259f2     UP      none

Display all connections on logical interface 2 starting with VPI.VCI 20.100.

atlanta.5.AXSME.a > dspcons -conn 2.20.100

record    Identifier   Type   SrvcType   M/S    Upld    Admn   Alarm

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

   10  02 0020 00100   VCC        ubr2   M   03d259dd     UP      none

   11  02 0021 00000   VPC      abrstd   M   03d259e8     UP      none

   12  02 0022 00100   VCC      abrstd   M   03d259f2     UP      none

Display all connections on logical interface 2.

atlanta.5.AXSME.a > dspcons -if 2

record    Identifier   Type   SrvcType   M/S    Upld    Admn   Alarm

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

    0  02 0010 00100   VCC        cbr1   M   03d25966     UP      none

    1  02 0011 00000   VPC        cbr2   M   03d25982     UP      none

    2  02 0012 00100   VCC        cbr3   M   03d2598d     UP      none

    3  02 0013 00100   VCC      vbr1rt   M   03d2599a     UP      none

    4  02 0014 00100   VCC      vbr2rt   M   03d259a1     UP      none

    5  02 0015 00000   VPC      vbr3rt   M   03d259ae     UP      none

    6  02 0016 00100   VCC     vbr1nrt   M   03d259bd     UP      none

    7  02 0017 00000   VPC     vbr2nrt   M   03d259c4     UP      none

    8  02 0018 00000   VPC     vbr3nrt   M   03d259ce     UP      none

    9  02 0019 00000   VPC        ubr1   M   03d259d5     UP      none

   10  02 0020 00100   VCC        ubr2   M   03d259dd     UP      none

   11  02 0021 00000   VPC      abrstd   M   03d259e8     UP      none

   12  02 0022 00100   VCC      abrstd   M   03d259f2     UP      none

atlanta.5.AXSME.a >

Display all connections on the current AXSM. In this example, only one connection exists. Master and slave endpoints are shown.

GN.6.AXSM.a > dspcons

record    Identifier   Type   SrvcType   M/S    Upld    Admn   Alarm

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

    0  01.0010.00100   VCC        cbr1   S   010c7953    UP      none

    1  04.0020.00100   VCC        cbr1   M   010c7964    UP      none

AXSM-E Example

Display all connections on the current AXSM-E.

MGX8850.6.AXSME.a > dspcons

record    Identifier   Type   SrvcType   M/S    Upld    Admn   Alarm

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

    0  01 0010 00100   VCC        cbr1   S   01b945d2     UP   multiple

    1  02 0010 00100   VCC        cbr1   M   01b945f2     UP   E-AisRdi

On the AXSM-E in slot 5, display all connections with a VCI of 100.

tokyo.5.AXSME.a > dspcons -vci 100

record    Identifier   Type   SrvcType   M/S    Upld    Admn   Alarm

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

    0  02 0010 00100   VCC        cbr1   M   03d25966     UP      none

    2  02 0012 00100   VCC        cbr3   M   03d2598d     UP      none

    3  02 0013 00100   VCC      vbr1rt   M   03d2599a     UP      none

    4  02 0014 00100   VCC      vbr2rt   M   03d259a1     UP      none

    6  02 0016 00100   VCC     vbr1nrt   M   03d259bd     UP      none

   10  02 0020 00100   VCC        ubr2   M   03d259dd     UP      none

   12  02 0022 00100   VCC      abrstd   M   03d259f2     UP      none

   13  02 0081 00100   VCC      abrstd   M   03db32b0     UP      none

   14  02 0082 00100   VCC        ubr2   M   03db5176     UP      none

   15  02 0083 00100   VCC      abrstd   M   03db54da     UP      none

   16  02 0084 00100   VCC        ubr2   M   03db54e4     UP      none

   17  02 0085 00100   VCC      abrstd   M   03db54f4     UP      none

   18  02 0086 00100   VCC        ubr2   M   03db54fc     UP      none

tokyo.5.AXSME.a > 

dspconsegep

Display Connection Segment Endpoint

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

---

Note The delconsegep command applies to SVCs only.

---

Cards on Which This Command Runs

PXM45

Syntax

dspconsegep <portid> <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	The VPI of the connection.
vci	The VCI of the connection.

Related Commands

cnfoamsegep, dspoamsegep, cnfconsegep, delconsegep

Attributes

Log: yes

State: active, standby

Privilege: ANYUSER

dspmbsdft

Display MBS Default

Displays the default MBS configured for the port.

Cards on Which This Command Runs

PXM45

Syntax

dspmbsdft <portid>

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.

Related Commands

cnfmbsdft

Attributes

Log: no

State: active, standby

Privilege: ANYUSER

Example

Display the MBS default for port 11:1.1:11.

Geneva.7.PXM.a > dspmbsdft 11:1.1:11

           rt-vbr:       nrt-vbr:

  MBS:        1024           1024

dspoamsegep

Display OAM Segment Endpoint

Displays whether or not the given port (portid) is designated as an OAM Segment Endpoint. See cnfoamsegep.

Operation, administration, and maintenance (OAM) is an ATM Forum specification for cells used to monitor virtual circuits. OAM cells provide a virtual circuit-level loopback which demonstrates whether a circuit is up or not.

Cards on Which This Command Runs

PXM45

Syntax

dspoamsegep <portid>

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.

Related Commands

cnfoamsegep

Attributes

Log: no

State: active

Privilege: ANYUSER

Example

Display OAM Segment Endpoint for slot 1, port 1.

MGX8850.7.a > dspoamsegep 1.1

dsppncon

Display PNNI Connection—display information about an existing call.

Displays information for an active SVC, SPVC, or SPVP. 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.

Cards on Which This Command Runs

PXM45

Syntax

dsppncon <portid> <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	VPI for the call. Default: 0
vci	VCI for the call. If no VCI is specified, this is a VP connection. Default: 0

Related Commands

dsppncons

Attributes

Log: no

State: active, standby

Privilege: ANYUSER

Example

Display VPI/VCI 100 100 on port 1.5.

mpgses1.2.PXM.a > dsppncon 1.5 100 100

 Port :            1.5 VPI :    100  VCI :    100 

 CallRef:      116  CallRefFlag:   0  CallLeafRef :        0 

 Calling-address: 47.009181000000003071f80e4a.000000010500.00

 Calling-subaddress #1: N/A

 Calling-subaddress #2: N/A

 Called-address: 47.009181000000003071f80e49.000000010500.00

 Called-subaddress #1: N/A

 Called-subaddress #2: N/A

 OE Port :            1.7 OE VPI :      1  OE VCI :     39 

 OE CallRef:       39  OE CallRefFlag:   0

 OAM-Type : Not an OAM Endpoint

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

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

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

 Tx pcr :         50           Rx pcr :         50

 Tx scr :    N/A Rx scr :    N/A

 Tx mbs :    N/A Rx mbs :    N/A

 Tx cdvt : 250000

 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 :    N/A    Max Rx clr :    N/A

NCCI value: 47 00 91 81 00 00 00 00 30 71 f8 0e 4a 00 30 71 f8 0e 4a 01 00 01

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

Display PNNI Connections

Displays a summary of active calls on one port or all ports.

Cards on Which This Command Runs

PXM45

Syntax

dsppncons [-port portid] [-vpi starting-vpi] [-vci starting-vci]
[-type {p2p | p2mp | ctrl}]

Syntax Description

-port	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	The starting VPI in the display. You can specify this parameter only if you specified a port ID.
-vci	The starting VCI in the display. Specify this parameter only if you specified a starting VPI.
-type	The type of connection to display. If you specify this optional parameter, only one of the following types appear in the output: p2p = point-to-point connections. p2mp = point-to-multipoint connections. The current release does not support point-to-multipoint connections. ctrl = control VCs.

Related Commands

dsppncon

Attributes

Log: no

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

Display PNNI Connection Statistics

Displays call statistics for a PNNI logical port.

Cards on Which This Command Runs

PXM45

Syntax

dsppnconstats <portid>

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.

Related Commands

clrpnconstats

Attributes

Log: no

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—bring a connection back into service.

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

Cards on Which This Command Runs

AXSM, AXSM-E

Syntax

upcon <ifNum > <vpi> <vci>

Syntax Description

ifNum	Logical interface (or port) number. The ranges are as follows: •AXSM: 1-60 •AXSM-E: 1-32
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: yes

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.

Cards on Which This Command Runs

AXSM, AXSM-E

Syntax

upport <ifNum>

Syntax Description

ifNum

Logical interface (or port) number. The ranges are as follows: •AXSM: 1-60 •AXSM-E: 1-32

Related Commands

dspport, dspports, dnport

Attributes

Log: yes

State: active

Privilege: GROUP1

Enable port 1 on the current card.

chicago.1.AXSM.a > upport 1