Cisco SES PNNI Controller Command Reference
Alphabetical Listing of SES PNNI Controller Commands
Downloads: This chapterpdf (PDF - 3.26MB) The complete bookPDF (PDF - 4.47MB) | Feedback

Alphabetical Listing of SES PNNI Controller Commands

Table Of Contents

Alphabetical Listing of SES PNNI Controller Commands

abortallsaves

abortofflinediag

abortrev

addaddr

addapsln

addcon

addfltset

addlmiloop

addpnni-node

addpnni-summary-addr

addpnport

addpref

addprfx

addserialif

addtrapmgr

adduser

aesa_ping

bootChange

burnboot

bye

cc

cd

clidbxlevel

clrallcnf

clrbecnt

clrcnf

clrconstats

clrdiagerr

clrdiagstat

clrerr

clrerrhist

clrlmistats

clrlmitrace

clrlog

clrloginmsg

clrpathtracebuffer

clrpathtracebuffers

clrpncon

clrpnconstats

clrqosdefault

clrscrn

clrsigstats

clrsntpstats

clrspvcnonpers

clrsscopstats

cmdhistory

cnfabrtparmdft

cnfaddrreg

cnfainihopcount

cnfapsln

cnfautocnf

cnfcbclk

cnfcdvtdft

cnfcmdabbr

cnfcon

cnfconpref

cnfconsegep

cnfdate

cnfdiag

cnfdiagall

cnfe164 justify

cnfenhiisp

cnffltset

cnfilmienable

cnfilmiproto

cnfintfcongth

cnfintvsvd

cnflmitrace

cnfloginmsg

cnfmbsdft

cnfname

cnfndparms

cnfnodalcongth

cnfnodalfd

cnfpasswd

cnfpri-routing

cnfoamsegep

cnfpnctlvc

cnfpnni-election

cnfpnni-intf

cnfpnni-link-selection

cnfpnni-mtu

cnfpnni-node

cnfpnni-pkttrace

cnfpnni-routing-policy

cnfpnni-scope-map

cnfpnni-svcc-rcc-timer

cnfpnni-timer

cnfpnportacc

cnfpnportcac

cnfpnportcc

cnfpnportloscallrel

cnfpnportncci

cnfpnportrange

cnfpnportsig

cnfpswdreset

cnfqosdefault

cnfrrtparm

cnfrteopt

cnfrteoptthld

cnfserialif

cnfsig

cnfsigdiag

cnfsnmp

cnfsntp

cnfspvcprfx

cnfsscop

cnfstatsmgr

cnfsvcoverride

cnftrftolerance

cnftime

cnftmzn

cnftmzngmt

cnftrapip

cnfuser

commitrev

conntrace

copy

cp

dbgsntp

deladdr

deladdrs

delapsln

delcon

delconsegep

delete

delfltset

dellmiloop

delpnni-node

delpnni-summary-addr

delpnport

delpnportacc

delpref

delprfx

delserialif

delsesn

delsigdiag

deltrapmgr

deluser

disablesscop

dncon

dnpnport

downloadflash

dspabrtparmdft

dspaddr

dspainihopcount

dspapscfg

dspapsln

dspatmaddr

dspbecnt

dspbkpl

dspcbclk

dspcd

dspcdalms

dspcderrs

dspcds

dspcdstatus

dspcdvtdft

dspclkinfo

dspcmdabbr

dspcon

dspconinfo

dspcons

dspconsegep

dspconstats

dspdate

dspdbinfo

dspdiagcnf

dspdiagerr

dspdiagstat

dspdiagstatus

dspdisk

dspenhiisp

dspenvalms

dsperr

dsperrhist

dsperrs

dspfltset

dspif

dspilmiaddr

dspintfcongcntr

dspintfcongflags

dspintfcongth

dspipconntask

dspipif

dspipifcache

dsplmilink

dsplmiloop

dsplmistats

dsplmitrace

dspln

dsplog

dsploginmsg

dsplogs

dspmbsdft

dspndalms

dspndparms

dspndstatus

dspnodalcongcntr

dspnodalcongflags

dspnodalcongth

dspnodalfd

dspoamsegep

dsppathtracebuffer

dsppathtracebuffers

dsppathtraceie

dsppathtracenode

dsppathtraceport

dsppingatmaddr

dsppnallgrpaddr

dsppncon

dsppncon

dsppncons

dsppnconstats

dsppnctlvc

dsppngrpmbrs

dsppnilmi

dsppnni-bn-path

dsppnni-bypass

dsppnni-election

dsppnni-idb

dsppnni-inducing-uplink

dsppnni-intf

dsppnni-link

dsppnni-link-selection

dsppnni-mtu

dsppnni-neighbor

dsppnni-node

dsppnni-node-list

dsppnni-path

dsppnni-pkttrace

dsppnni-ptse

dsppnni-reachable-addr

dsppnni-routing-policy

dsppnni-scope-map

dsppnni-spoke

dsppnni-summary-addr

dsppnni-svcc-rcc

dsppnni-svcc-rcc-timer

dsppnni-timer

dsppnport

dsppnportcac

dsppnportcc

dsppnportidmaps

dsppnportloscallrel

dsppnportncci

dsppnportrange

dsppnportrsrc

dsppnports

dsppnportsig

dsppnsysaddr

dsppref

dspprefs

dspprfhist

dspprfx

dsppri-routing

dsppswdreset

dsppvcif

dspqosdefault

dspred

dsprevs

dsprrtparm

dsprteoptcnf

dsprteoptstat

dspsem

dspsems

dspserialif

dspsesn

dspsig

dspsigdiag

dspsigstats

dspsnmp

dspsntp

dspsntpstats

dspspvcaddr

dspspvcprfx

dspsscop

dspsscopstats

dspstatsmgr

dspsvcparm

dspsvcoverride

dspswalms

dsptrapip

dsptrapmgr

dsptrftolerance

dspusers

dspversion

exit

forcecdnative

help

history

ifShow

ipifconfig

loadrev

logout

ls

memShow

modpref

optrte

pathtraceie

pathtracenode

pathtraceport

ping

pvcifconfig

pwd

remove

rename

resetcd

resetsys

restoreallcnf

routeShow

routestatShow

rrtcon

runrev

saveallcnf

sesntimeout

setrev

shellcon

showsyserr

stackdump

svcifconfig

switchapsln

switchcc

switchredcd

syserr

telnet

timeout

tstconseg

tstdelay

tstpndelay

upcon

uppnport

users

who

whoami


Alphabetical Listing of SES PNNI Controller Commands


This chapter provides an alphabetical listing of all the commands that are used for the SES PNNI Controller.

abortallsaves

Abort All Saves—PXM1

Use the abortallsaves command to abort the configuration save process that could have begun with either the saveallcnf command or an SNMP-based command. The purpose of the abortallsaves command is to stop a potentially time-consuming save operation so that you can begin a firmware upgrade. The time you save by aborting the process is significant only with a substantial number of configured entities in the node, for example, the maximum number of cards and logical entities. If the switch is not currently saving the configuration database, the switch displays the applicable message.

Syntax

abortallsaves

Syntax Description

None

Related Commands

restoreallcnf, saveallcnf

Attributes

Access level: GROUP1

State: active

Log: log


Example

Abort the current configuration process.

SES_SJ.1.PXM.a > abortallsaves


No Save Process running

abortofflinediag

Abort Offline Diagnostics—PXM1

Use the abortofflinediag command to abort the current offline diagnostics.

Syntax

abortofflinediag <slot>

Syntax Description

slot

Specifies the slot number of the card to abort offline diagnostics.


Related Commands

None

Attributes

Access level: SERVICE_GP

State: any

Log: no


Example

Abort the offline diagnostics for slot number 1.

SES_SJ.1.PXM.a > abortofflinediag 1

abortrev

Abort Revisions—PXM1

Use the abortrev command to abort revisions on the specified slot.

Syntax

abortrev <slot> <revision>

Syntax Description

slot

Slot number of the card for which the version is set.

revision

Revision number, for example, 3.0(0.171).


Related Commands

commitrev, dsprevs, loadrev, runrev, setrev

Attributes

Access level: SERVICE_GP

State: any

Log: log


Example

Abort revisions for slot 1.

spirita.1.PXM.a > abortrev 3.0(0.171)
one or more card(s) in logical slot will be reset.
Do you want to proceed (Yes/No)? n
(command not executed)

addaddr

Add Address—PXM1

Enter the addaddr command to add or delete an ATM address for a UNI or IISP. This command is also used to configure static routes to reachable addresses.

An ATM address can be provisioned only on a UNI if ILMI address registration is disabled. Provision an ATM address as follows:

On UNI ports, type must be internal and proto must be local.

On IISP ports, type must be exterior and proto must be static.

Syntax

addaddr <portid> <atm-address> <length> [-type {int | ext}][-proto {local | static}]
[-plan {e164 | nsap}][-scope value][-redst {yes | no}]

Syntax Description

portid

Interface number, in the form of [shelf.]slot[:subslot].port[:subport].

atm-address

ATM address or E.164 number, consisting of 1-20bytes.

length

Address length.

This entry represents the length in bits for an NSAP address.

This entry represents the length in digits for an E.164 address.

Range: 1-160

-type

Type of reachability from the advertising node to the address, as either internal or exterior.

Default: internal

-proto

Routing mechanism which establishes the connectivity from the advertising node to the reachable address.

Default: local

-plan

Address plan, either E.164 or NSAP.

For NSAP address, the first byte of the address automatically implies one of three NSAP address plans: NSAP E.164, NSAP DCC, or NSAP ICD.

Default: nsap

-scope

PNNI scope of advertisement (level of PNNI hierarchy) of the reachability from the advertising node to the address.

Range: 0-104

Default: 0

-redst

Indicates if the static address is distributed.

Default: no


Related Commands

deladdr, dspaddr, dsppnallgrpaddr

Attributes

Access level: GROUP1

State: active

Log: log


Example

Assign a 160-bit (20 byte) nsap address to logical port on line 2 of the back card of the PXM in slot 1.

spirita.1.PXM.a > addaddr 2.3 4500731300000010101010101000000000000100 160 -plan nsap

Example

Verify the results by entering the dspaddr command.

SES_SJ.1.PXM.a > dspaddr 2.3
45.0073.1300.0000.1010.1010.1010.0000.0000.0001.00
length: 160    type: internal      proto: local
scope: 0       plan: nsap_e164     redistribute: false
transit network id: 


SES_SJ.1.PXM.a >

addapsln

Add APS Line—PXM1

Use the addapsln command to set APS on a specified line for a PXM.

Syntax

addapsln <work-line> <work-slot> <prot-line> <prot-slot> <mode>

Syntax Description

work-line

Working line number. Enter the value 1.

work-slot

Enter value 1 or 2.
The following are the value types:
Value
Type

1

slot 1

2

slot 2

prot-line

Protection line number. Enter the value 1.

prot-slot

Protection slot number. Enter the value 1 or 2.

mode

Sets the APS architecture mode to be used on the working or protection line pair. Enter the value 2.


Related Commands

cnfapsln, delapsln, dspapsln, switchapsln

Attributes

Access level: SUPER_GP

State: active

Log: log


Example

Enable the APS line pair for the applicable line.

spirita.1.PXM.a > addapsln 1 1 1 2 2

addcon

Add Connection—PXM1

Use the addcon command to add a new SPVC connection endpoint. To create an SPVC first use addcon to add the slave endpoint, at which point the system returns a slave endpoint identifier. Then use addcon again to add the master endpoint, using the value of the slave endpoint identifier in the -slave parameter

You can assign a priority at the master end of an SPVC or SPVP. The PNNI controller routes higher priority connections before lower priority connections. For more information about assigning a priority to a connection, see the cnfpri-routing and dsppri-routing commands.

Syntax

addcon <portid> <vpi> <vci> <serviceType> <master_ship> <slave_nsap.vpi.vci>
[
-lpcr <local pcr>] [-lmcr <local MCR>] [-lscr <local SCR>] [-icr <local ICR>] [-lputil <local putil>] [-lmbs <local MBS>] [-cdvt <local CDVT>] [-lcdv <local CDV>] [-lctd <local CTD>]
[
-rpcr <remote PCR>] [-rmcr <remote MCR>] [-rscr <remote SCR>] [-rputil <remote putil>]
[
-rmbs <remote MBS>] [-rcdv <remote CDV>] [-rctd <remote CTD>] [-mc <Max Cost>]
[
-stats <enable(1)/disable(0)>] [-frame <enable(1)/disable(0)>] [-int_vsvd <1/2/3>]
[
-ext_vsvd <1/2/3>] [-slavepersflag <persistent(0)/nonpersistent(1)>]

Syntax Description

portid

Interface number, in the form of [shelf.]slot[:subslot].port[:subport].

vpi

Specify the starting virtual path identifier (VPI) to view active calls starting from the specified VPI of the specified port. Use this parameter only when the port is specified.

vci

Specify the starting virtual channel identifier (VCI) to view active calls starting from the specified VPI/VCI of the specified port. This parameter is used only if the VPI is specified.

VCI - VCC(32..65535); VPC (VCI = 0)

serviceType

Specifies the service type for the connection.

The following are the values:

Value
Service Type

1

cbr1

2

vbr1rt

3

vbr2rt

4

vbr3rt

5

vbr1nrt

6

vbr2nrt

7

vbr3nrt

8

ubr1

9

ubr2

10

abrstd

11

cbr2

12

cbr3

master_ship

Specifies whether the connection is a master or a slave.

slave = 1 or s

master = 2 or m

slave_nsap.vpi.vci

Slave ID. The value should look like this: NSAP_address.vpi.vci.

Use this parameter only for setting up a master connection.

-lpcr

This optional keyword can be used for specifying the PCR required for the connection in the local -> remote direction.

Default: 50 cps

-lmcr

This optional keyword can be used for specifying the MCR required for the connection in the local -> remote direction.

-lscr

This optional keyword can be used for specifying the SCR required for the connection in the local -> remote direction.

-icr

This optional keyword can be used for specifying the initial cell rate (ICR) required for the connection in the local -> remote direction. ICR range. The range is between minimum cell rate (MCR) and peak cell rate (PCR).

Default: l pcr

-lputil

Specifies the local percentage utilization factor.

Range: 1-100

Default: 100

-lmbs

This optional keyword can be used for specifying the MBS required for the connection in the local -> remote direction.

Default: dspmbsdft command value

-cdvt

This optional keyword can be used for specifying the CDVT required for the connection in the local -> remote direction.

Default: dspcdvtdft command value

-lcdv

This optional keyword can be used to specify the CDV required for the connection in the local -> remote direction.

Default: -1

-lctd

This optional keyword can be used to specify the CTD required for the connection in the local -> remote direction.

Default: -1

-rpcr

This optional keyword can be used to specify the PCR required for the connection in the remote -> local direction.

Default: 50 cps

-rmcr

This optional keyword can be used to specify the MCR required for the connection in the remote -> local direction.

-rscr

This optional keyword can be used to specify the SCR required for the connection in the remote -> local direction.

-rputil

Specifies the remote percentage utilization factor.

Range: 1-100

Default: 100

-rmbs

This optional keyword can be used to specify the MBS required for the connection in the remote -> local direction.

Default: dspmbsdft command value

-rcdv

This optional keyword can be used to specify the CDV required for the connection in the remote -> local direction.

Default: -1

-rctd

This optional keyword can be used to specify the CTD required for the connection in the remote -> local direction.

Default: -1

-mc

Maximum cost. This optional keyword is used to specify the routing cost for a parameter, which would be used by PNNI in choosing route based on weights assigned for different routes.

Default: -1

-stats

This optional keyword is used to enable or disable the -stat collection on SPVC. Stats collection: enable(1) | disable(0).

Default: disable

-frame

This optional keyword is used to enable or disable the frame discard on SPVC. Frame discard: enable(1) | disable(0).

Default: disable

-int_vsvd

Internal Segment VSVD: 1 (off) / 2 (on) /3 (unspec).

Default: off

-ext_vsvd

External Segment VSVD: 1 (off) / 2 (on) /3 (unspec).

Default: off

-slavepersflag

Specifies if the slave endpoint is persistent or nonpersistent. The slave persistent flag is applicable only when provisioning master endpoints. The following are the options for the -slavepersflag parameter:

persistent (0)

nonpersistent (1)


Related Commands

cnfcon, delcon, dncon, dspcon, upcon

Attributes

Access level: GROUP1

State: active

Log: yes


Example

Add a slave endpoint.

spirita.1.PXM.a > addcon 2 11 100 8 s 
slave endpoint added successfully
slave endpoint id : 4700918100000000107BE92F7B00000103180200.11.100

Example

Add a master endpoint.

spirita.1.PXM.a > addcon 2 11 100 8 m -slave 
4700918100000000107BE92F7B00000103180200.11.100 -lcpr 1000 -rpcr 1000
master endpoint added successfully
master endpoint id : 4700918100000000107BE92F5100000103180200.11.100

addfltset

Add Filter Set—PXM1

Use the addfltset command to add an ATM address filter set.


Note After a filter is created for a specific port, associate the filter to that port by using the cnfpnportacc command.


Syntax

addfltset <name> [-address address-template -length address-template-length [-plan {e164 | nsap}] [-list {calling | called}] [-index number] [-accessMode {permit | deny}]] [-cgPtyAbsentAction {permit | deny}] [-cdPtyAbsentAction {permit | deny}]

Syntax Description

name

The name of the filter set, consisting of 1-29 characters.

-address

The NSAP address, consisting of 1-40 digits, or the E.164 address, consisting of 1 to 15 digits. The address template can have prefix address digits followed by a trailing string "...," in which case, only the prefix part of the address is considered in the address pattern match. Likewise, the address template can have an initial string "...," followed by address digits, in which case, the trailing address digits are alone considered in the address pattern match. An address template can contain the character "*," in which case, that digit is not considered in the address pattern match.

Default: filter with no address.

-length

Length in bits (if NSAP) or bytes (if E.164). A length must be specified if the address is specified. However, a filter can be created without an address, in which case the length field is not applicable. If the address template consists of the string "..." or the character "*," the length field contents do not matter.

-plan

Address plan, either E.164 or NSAP. Use this parameter only if the address field is also specified.

Default: NSAP

-list

Address list in which address is included, either calling or called. Use this parameter only if the address is also specified.

Default: calling

-index number

Specifies how the address entries in a filter are set. This parameter has significance only if an address is also specified.

Range: 1-65535

Default: 1

-accessMode

Indicates whether or not to accept (permit) or reject (deny) a call on the port if the address pattern matching succeeds. This parameter has significance only if an address is also specified.

Default: permit

-cgPtyAbsentAction

Indicates whether or not to accept (permit) or reject (deny) a call on the port if the calling party does not match any entry in the calling party address list of the filter set.

Default: permit

-cdPtyAbsentAction

Indicates whether or not to accept (permit) or reject (deny) a call on the port if the called party does not match any entry in the called party address list of the filter set.

Default: permit


Related Commands

cnffltset, delfltset, dspfltset

Attributes

Access level: GROUP1

State: active

Log: log


Example

Add a filter set called "anyname."

spirita.1.PXM.a > addfltset anyname

addlmiloop

Add an LMI Loopback—PXM1

Use the addlmiloop command to add an LMI loopback line to the current card.


Note Activate only one PXM line on the feeder implementation of an SES node.


Syntax

addlmiloop <slot.port>

Syntax Description

slot

Slot number of the card on which you are adding the LMI loopback line. For an SES, the value for this parameter is either 1 or 2.

port

Port number.


Related Commands

dellmiloop, dsptrapip

Attributes

Access level: SUPER_GP

State: active

Log: no


Example

Add an LMI loopback line numbered 1 to the PXM in slot 1.

spirita.1.PXM.a > addlmiloop 1.1


addpnni-node

Add PNNI Node—PXM1

Use the addpnni-node command to add a PNNI node. When adding a new PNNI logical node, the hierarchical level of the new node must be higher than the level of the node which is currently at the highest hierarchy.

Syntax

addpnni-node level [lowest][-atmAddr atm-address][-nodeId node-id] [-pgId pg-id]
[-enable {true | false}] [-transitRestricted {on | off}] [-complexNode{on | off}]
[-branchingRestricted {on | off}] [-pglNoTransit {on | off}]

Syntax Description

level

The PNNI hierarchical level. Default to 56 for PNNI node at the lowest level if not specified.

It must be specified for nodes at higher levels. Once assigned, it may only be changed when the administrative status of the node is disabled.

lowest

Indicates the PNNI node at the lowest hierarchical level.

-atmAddr

The 20-byte ATM address assigned to a PNNI logical node operating on a local switching system.

If not specified, the default value is used. Once assigned, it may only be changed when the administrative status of the node is disabled.

-nodeId

The 22-byte PNNI node id assigned to a PNNI logical node operating on a local switching system. If not specified, the default value is used, which is the normal case. Once assigned, it may only be changed when the administrative status of the node is disabled.

-pgId

The 14-byte peer group ID assigned for a PNNI logical node operating on a local switching system. If not specified, the default value will be used, which is the normal case. Once assigned, it may only be changed when the administrative status of the node is disabled.

-enable

Specifies the administrative status for a PNNI node, as either enable or disable.

When administratively disabling a PNNI logical node, all nodes at higher hierarchies must be administratively disabled first.

Default: enable

-transitRestricted

Specifies if this node is a restricted transit node, as either on or off.

Default: off

-complexNode

Specifies if the node is a complex node, as either on or off. This setting is not applicable for a node at the lowest hierarchical level.

On: Complex node

Off: Not a complex node

Default: off

-branchingRestricted

Specifies support for additional point-to-multipoint branches by this node, as either on or off.

Default: on

-pglNoTransit

Specifies participation in PGL elections by this node, as either on or off.

Default: off


Related Commands

cnfpnni-node, delpnni-node, dsppnni-node

Attributes

Access level: SUPER_GP

State: active

Log: log


Example

Add a PNNI node to the applicable ATM address.

spirita.1.PXM.a > addpnni-node 1 -atmAddress 47.00918100000000107b65f260.00107b65f260.01 

addpnni-summary-addr

Add PNNI Summary Address—PXM1

Use the addpnni-summary-addr command to configure an ATM summary address prefix for a PNNI logical node operating on a local switching system.

Syntax

addpnni-summary-addr <node-index> <address-prefix> <prefix-length>
[-type {internal | exterior}] [-suppress {true | false}]

Syntax Description

node-index

Node index assigned to a PNNI logical node operating on a switching systems.

Range: 1-10

address-prefix

ATM address prefix assigned to the local switching system.

prefix-length

Length of the address-prefix, in number of bits, equal to or less than 152 bits.

Note Zero-length summary address is not currently supported.

-type

Type of summary address, as either internal or external.

Default: internal

-suppress

Indicates whether to advertise (false) or not advertise (true) the summary address.


Related Commands

delpnni-summary-addr, dsppnni-summary-addr

Attributes

Access level: SUPER_GP

State: active

Log: log


Example

spirita.1.PXM.a > addpnni-node 47.00918100000000107b65f260.00107b65f260.01 internal true

addpnport

Add a UNI or NNI Port—PXM1

Use the addpnport command to add a UNI or NNI port. After the port is added, its administrative state is down by default. This command is used to pre-configure a port on the controller. It is allowed only if the port does not yet exist on the switch.

Syntax

addpnport <portid>

Syntax Description

portid

Interface number, in the form of [shelf.]slot[:subslot].port[:subport].


Related Commands

delpnport, dnpnport, dsppnport

Attributes

Access level: GROUP1

State: active

Log: log


Example

Add a UNI or NNI port to the applicable port ID.

spirita.1.PXM.a > addpnport 0.1.1

addpref

Add Preferred Route—PXM1

Use the addpref command to add a new preferred route. This command does not associate the preferred route with any SPVC, to do this use the cnfconpref command.

The following are the functions for the addpref command:

Creates a route in the preferred route database. A preferred route ID value is assigned.

Specifies a new route as a list of up to 20 pairs of persNodeIdx and portId (unless the nodes are specified by name in which case up to 10 pairs can be specified).

Once entered, the system returns the given numeric ID for that preferred route.


Note At least one keyword needs to be entered to add a preferred route.


Syntax

addpref [-name yes/no] [-h1 {<persNodeIndex>/<portId>}] [-h2 {<persNodeIndex/<portId>}] ...
[-h20 {<persNodeIndex>/<portId>}]

Syntax Description

-name

Specifies the nodes by names. Enter either yes or no.

Default: no

-h1, -h2, -h20

Each -hn parameter refers to a node in the preferred route, in which there can up to 20 nodes. Each node is expressed as a persNodeIndex and portId pair. -h1 refers to the first pair for the first node, -h2 refers to the pair for the second node, and so on up -h20 which refers to the 20th node. If the -name yes option is selected, persNodeIndex stands for a name string. If -name no is selected or -name keyword is not specified then the persNodeIndex refers to an index called "table index." This index is derived from the persistent topology database. This database can be displayed entering the dsptopondlist command.


Related Commands

cnfconpref, delpref, dsppref, dspprefs, modpref

Attributes

Access level: GROUP1

State: active

Log: log


Example

Check that node indexes 11, 34, 56 and 23 exist in the persistent topology database then, using the persNodeIndex method, configure a preferred route as follows:

addpref -h1 11/1:2.1.9 -h2 34/1:1.1.2 -h3 56/1:2.1.7 -h4 23/#
pref Route ID = 2

Specify the same route by using node names:

addpref -name yes -h1 altanta/1:2.1.( -h2 newyork/1:1.1.2 -h3 chicago/1:2.1.7 -h4 
seattle/#
pref route ID = 2

addprfx

Add an ILMI Address Prefix for UNI—PXM1

Use the addprfx command to add an ILMI address prefix for UNI. When adding a prefix, this prefix must be stored on both the controller and the platform. Therefore, a successful return status from the command line does not guarantee this prefix is added onto the platform prefix table. You should check the event log to ensure this prefix is added successfully in the prefix table on the platform. You can add up to 16 prefix per port.

Syntax

addprfx <portid> <atm-prefix>

Syntax Description

portid

Interface number, in the form of [shelf.]slot[:subslot].port[:subport].

atm-prefix

ATM address prefix. The prefix must be eight or thirteen bytes in length.


Related Commands

delprfx, dspprfx

Attributes

Access level: GROUP1

State: active

Log: log


Example

Add an ILMI address prefix for UNI with the applicable port ID and atm address prefix.

spirita.1.PXM.a > addprfx 0.1.1 4700ab0012340000

addserialif

Add Serial Interface—PXM1

Use the addserialif command to add a serial interface to the port.

Syntax

addserialif <port#>

Syntax Description

port#

Indicates the type of port you want to add. Enter 1 to add a maintenance port. Enter 2 to add a console port.


Related Commands

None

Attributes

Access level: SUPER_GP

State: active

Log: no


Example

Add a maintenance port.

spirita.1.PXM.a > addserialif 1

Example

Add a serial port.

spirita.1.PXM.a > addserialif 2

addtrapmgr

Add Trap Manager—PXM1

Use the addtrapmgr command to set up an SNMP manager to receive traps. Trap managers added through addtrapmgr command or through the SNMP manager (Cisco WAN Manager or other application) do not age and are not deleted. To delete a trap manager, enter either the deltrapmgr command or an SNMP Set on the intended object.

Syntax

addtrapmgr <ip_addr> <portnum>

Syntax Description

ip_addr

IP address in dotted decimal format. For example,

nnn.nnn.nnn.nnn, n = 0-9 and nnn < 256

portnum

Port number on the workstation that receives traps. If you add a trap manager through SNMP, the default portnum is 162.

Range: 0-65535


Related Commands

deltrapmgr, dsptrapmgr

Attributes

Access level: SUPER_GP

State: active

Log: log


Example

Add a trap manager with IP address 161.10.144.56 to port 50.

spirit11.1.1.PXM.a > addtrapmgr 161.10.144.56 50

adduser

Add User—PXM1

Use the adduser command to configure a user name and associated access level on the PXM.

Syntax

adduser <user ID> <accessLevel>

Syntax Description

user ID

Case-sensitive name to be used as the login at the PXM.

The name can consist of up to 12 characters composed of alpha numeric characters and special characters, such as "_" and "-."

Note The name must begin with an alpha character and cannot contain spaces.

accessLevel

System privilege level to be allocated for the user ID by using one of the following options:

SERVICE_GP

SUPER_GP

GROUP1 (highest level)

GROUP2

GROUP3

GROUP4

GROUP5

ANYUSER (lowest level)

You cannot configure a new user for an accessLevel that is higher than that defined for the current login ID.


Related Commands

cnfuser, users

Attributes

Access level: GROUP1

State: active

Log: log


Example

Add a user with the applicable access levels.

spirit.1.1.PXM.a > adduser fin ANYUSER
Enter password:
Re-enter password: 
 
spirit.1.1.PXM.a >

aesa_ping

ATM End System Address Ping—ping any ATM end station connected to a PNNI network.

Use the aesa_ping command to ping an ATM end station address (AESA) based on an ATM address that you provide as a destination address. If you specify only the destination address, the local node merely looks up that address in its routing table. To actually confirm the reachability of another node, specify the optional parameters for setting up a SVC to send and receive keep-alive packets.

Syntax

aesa_ping {destination address} [-setupcall {yes | no}] [-qos {ubr | abr | vbr_rt | vbr_nrt}] [-trace {yes | no}] [-data {yes | no}] [-timeout {time out in secs}] [-interval {time}][-pcr {peak cell rate}] [-scr {sustain cell rate}]

destination address

Destination address in NSAP format. For example,

47.00918100000000500ffde873.00500ffde873.01

-setupcall

Sets up an SVC call as part of the ping. If you do not include the setupcall parameter, the system performs only route lookup for the QoS parameters to the destination.

Possible values: yes or no

Default: no

-qos

Quality of service (QoS) used for SVC ping connection. This parameter applies only if you enable setupcall. Enter one of the following options:

ubr

abr

cbr

vbr_rt

vbr_nrt

-trace

Enable path trace during ping. This parameter only applies if -setupcall is enabled. Enter either yes or no.

Default: no

-data

If you enable data, the switch transfers data then prints statistics at the end of the timeout. Enter either enable or disable.

Default: disable

-timeout

Connection timeout for the ping. This parameter applies only if setup call is enabled.

Range: 5-120 sec

Default: 5 sec

-interval

The interval between the call setup of successive transmissions. This parameter applies only if setup call is enabled.

Range: 5-120 sec

Default: 5 sec

-pcr

Peak cell rate of the ping. This parameter applies only if you enable setup call.

Range: 1-100 sec

Default: 10

-scr

Sustained cell rate of the ping. This parameter applies only if you enable setup call.

Range: 1-50 sec

Default: 5


Related Commands

dsppingatmaddr

Attributes

Access level: SUPER_GP

State: active

Log: log


Example

Pings the ATM end station with the address 47.00918100000000500ffde873.00500ffde873.01.

spirita.1.PXM.a > aesa_ping 47.00918100000000500ffde873.00500ffde873.01
 
Ping Got CLI message, index=0
 
PING:from PNNI - SOURCE ROUTE
DTL    1 :Number of (Node/port)elements    2
 
DTL 1:NODE 1::56:160:71:0:145::238:238:238:238:
 
Port 1:263168
 
DTL 1:NODE 2::56:160:71:0:145::15:253:232:115:
 
Port 2:0
 
Port List :no of ports =    1
 
Port ID    1:263168 

bootChange

Boot Change—PXM1

Use the bootChange command to specify the boot IP address and gateway address of a PXM card. The IP address you define with the bootChange command is used only when the PXM is in the boot state.

In the current release, the only parameters you should enter are "inet on ethernet (e)" and "gateway inet (g)." The bootChange command presents one parameter at a time. Therefore, press Return (or Enter) at each prompt except for these two. The example in this description shows the two fields where you need to enter an IP address and the fields you skip.


Note Run this command in boot-mode only.


Syntax

bootChange

Related Commands

None

Attributes

Access level: SERVICE_GP

State: active

Log: log


Example

Specify an IP address of 170.11.52.61 for the Ethernet port and 170.11.52.2 for the gateway IP address. The display shows all the fields that the node presents. Press Return or Enter at all fields except for the ethernet and gateway prompts.

ses64.1.PXM.a > bootchange
'.' = clear field;  '-' = go to previous field;  ^D = quit
boot device          : lnPci
processor number     : 0
host name            :
file name            :
inet on Ethernet (e) : 172.29.37.41:ffffff00
inet on backplane (b):
host inet (h)        :
gateway inet (g)     : 172.29.37.1 
user (u)             :
ftp password (pw) (blank = use rsh):superuser 
flags (f)            : 0x0
target name (tn)     :
startup script (s)   :
other (o)            : 

burnboot

Burn Boot—PXM1

Use the burnboot command to burn the boot code onto the PXM card.

Syntax

burnboot <slot> <revision>

Syntax Description

slot

Card slot number for the card to be upgraded, Enter 1 or 2.

revision

Software version number for the update.


Related Commands

None

Attributes

Access level: SERVICE_GP

State: active

Log: log


Example

Burn the boot code for the PXM card.

spirita.1.PXM.a > burnboot 1 2.0(0)

bye

Bye—PXM1

Use the bye command to exit the current CLI shell.

Syntax

bye

Related Commands

exit

Attributes

Access level: ANYUSER

State: all

Log: log


Example

Exit the current CLI shell.

spirit.1.2.PXM.a > bye
 
(session ended)

cc

Change Card—PXM1

Use the cc command to navigate from card to card on the shelf.

Syntax

cc <slotNumber>

Syntax Description

slotNumber

The number of the slot that contains the card you want to work on, either 1 or 2.


Related Commands

None

Attributes

Access level: ANYUSER

State: all

Log: log


Example

Change the card to slot number 2.

spirita.1.PXM.a > cc 2

cd

Change Directory—PXM1

Use the cd command to change to another directory on the PXM1 hard disk.

Syntax

cd <path name>

Syntax Description

path name

Specifies the name of the destination directory.


Related Commands

rename, copy

Attributes

Access level: ANYUSER

State: all

Log: log


Example

Change the directory to FW.

SES_SJ.1.PXM.a > cd FW

Example

Verify the current directory by entering the pwd command.

SES_SJ.1.PXM.a > pwd
C:FW

SES_SJ.1.PXM.a > 

Example

Go back to the root directory.

SES_SJ.1.PXM.a > cd ..

Example

Verify the result by entering the pwd command.

SES_SJ.1.PXM.a > pwd
C:

SES_SJ.1.PXM.a >

clidbxlevel

Command Line Interface Level—PXM1

Use the clidbxlevel command to display the attributes for each command. You must enter the clidbxlevel command on each card where you want to change the level of displayed information. For example, if you enter the clidbxlevel command on PXM1 on slot 1 and want to see the same level of information in slot 2, you must enter the clidbxlevel command for slot 2.

The following are the attributes:

The minimum user-privilege for the command.

The required card state of execution.

The status of the log file for the command.

Syntax

clidbxlevel [level]

Syntax Description

level

Indicates the level is either 0 or 1. If you do not include the level, the switch states the current level.


Related Commands

None

Attributes

Access level: SERVICE_GP

State: all

Log: no


Example

Specify level 1 for the CLI.

SES_SJ.1.PXM.a > clidbxlevel 1
Value of cliDbxLevel is now 1

Example

Enter the help command to view the access levels, card states, and log status for each applicable command.

SES_SJ.1.PXM.a > help

    Command          Access           Card         Log
    ---------------------------------------------------
    ?                ANYUSER          A|S|I         -
    abortallsaves    GROUP1           A             +
    abortofflinediag SERVICE_GP       A|S           -
    abortrev         SERVICE_GP       A|S           +

clrallcnf

Clear All Configuration—PXM1

Use the clrallcnf command to remove all configuration databases from the shelf, including configuration stored in BRAM by the shelf manager, and other configuration files currently stored on disk.


Warning This is a destructive command.


Syntax

clrallcnf

Syntax Description

None

Related Commands

clrcnf, restoreallcnf, saveallcnf

Attributes

Access level: SERVICE_GP

State: any

Log: no


Example

Clear all the configurations and restart the switch.

spirita.1.PXM.a > clrallcnf
All SM's config will be deleted, and
        the shelf will be reset.
Do you want to proceed (Yes/No)? n
(command not executed)

clrbecnt

Clear Bit-Error Count—PXM1

Use the clrbecnt command to remove all the statistics for the automatic protection switching (APS) bit-error counts

Syntax

clrbecnt <line>

Syntax Description

line

Enter the value 1.


Related Commands

dspbecnt

Attributes

Access level: SUPER_GP

State: active

Log: no


Example

First display bit error count, then clear bit error count. Confirm by displaying again.

mpgses1.1.PXM.a > dspbecnt 1
Line 1.1:
    24 Hour   Bit Error Count 0
    15 Minute Bit Error Count 0
    15 Second Bit Error Count 0
Line 2.1:
    24 Hour   Bit Error Count 0
    15 Minute Bit Error Count 38
    15 Second Bit Error Count 0

mpgses1.1.PXM.a > clrbecnt 1
Do you want to clear the bit-error count for line 1.1 [Y/N] ? Yes

The bit-error count for line 1.1 is cleared
Do you want to clear the bit error count for line 2.1 [Y/N] ? Yes

The bit-error count for line 2.1 is cleared

mpgses1.1.PXM.a > dspbecnt 1
Line 1.1:
    24 Hour   Bit Error Count 0
    15 Minute Bit Error Count 0
    15 Second Bit Error Count 0
Line 2.1:
    24 Hour   Bit Error Count 0
    15 Minute Bit Error Count 0
    15 Second Bit Error Count 0

clrcnf

Clear Configuration—PXM1

Use the clrcnf command to clear all card configurations on the switch.

Syntax

clrcnf

Syntax Description

None

Related Commands

clrallcnf, restoreallcnf, saveallcnf

Attributes

Access level: SERVICE_GP

State: active

Log: no


Example

Clear all card configurations.

spirita.1.PXM.a > clrcnf 
All SM's disk config will be deleted, and 
         the shelf will be reset.
clrcnf: Do you want to proceed (Yes/No)? Y

clrconstats

Clear Connection Statistics—PXM1

Use the clrconstats command to clear existing statistics for a specified active spvc connection (specified using portid, vpi, vci).

Syntax

clrconstats <portid> <vpi> [<vci>]

Syntax Description

portid

PNNI logical port, in the format [shelf.]slot[:subslot].port[:subport]. Using the short form where only the mandatory elements are appropriate, the portid has the format slot.port.

vpi

Minimum VPI value for the connection.

Range: 0-4095

vci

Minimum VCI value for the connection.

Range: 0-65535

The default value for vp connections is 0.


Related Commands

dspconstats

Attributes

Access level: ANYUSER

State: active

Log: log


Example

spirita.1.PXM.a > clrconstats 4.1 4000 6000

clrdiagerr

Clear Diagnostic Error—PXM1

Use the clrdiagerr command to clear all the diagnostics error messages that are currently in memory.

Syntax

clrdiagerr <slot>

Syntax Description

slot

Specifies the slot of the card where to clear the diagnostic errors.


Related Commands

None

Attributes

Access level: SERVICE_GP

State: any

Log: no


Example

Clear all the diagnostic errors for slot 1.

SES_SJ.1.PXM.a > clrdiagerr 1

clrdiagstat

Clear Diagnostic Statistics—PXM1

Use the clrdiagstat command to clear all the diagnostic statistics currently in memory. The diagnostics program keeps count of how many times the diagnostics has run.

Syntax

clrdiagstat <slot>

Syntax Description

slot

Specifies the slot of the card to clear the diagnostic statistics.


Related Commands

dspdiagstat

Attributes

Access level: SERVICE_GP

State: any

Log: no


Example

Clear the diagnostic statistics for slot number 1.

SES_SJ.1.PXM.a > clrdiagstat 1

clrerr

Clear Error—PXM1

Use the clrerr command to remove a specified file or all error log files. This command queries for confirmation prior to clearing the error log files from the system.

Syntax

clrerr [-en <error number>][-sl <slot number>]

Syntax Description

-en

Command delineator that precedes the error number entry. The error number indicates the number of the log file to clear.

-sl

Command delivered that proceeds the slot number entry. The slot number indicates the number of the slot where the selected card resides.


Related Commands

clrerrhist, dsptrapip, dsperrhist

Attributes

Access level: SUPER_GP

State: any

Log: no


Example

Clear the error log files.

wilco.1.1.PXM.a > clrerr
Do you want to proceed (Yes/No)? No
(command not executed) 
wilco.1.1.PXM.a > 

clrerrhist

Clear Error History—PXM1

Use the clrerrhist command to display a log of errors and failures.

Syntax

clrerrhist <slot>

Syntax Description

slot

Number for the slot that contains the card you want to work on. Use this object to clear the log of errors and failures only on a specific slot.


Related Commands

clrerr, dsptrapip, dsperrhist, dsperrs

Attributes

Access level: ANYUSER

State: all

Log: no


Example

Clear the error history for the applicable slot.

spirit11.1.1.PXM.a > clrerrhist
10      0x301f   syncRam DB Reset Init from STBY failed  09/07/2000-20:44:25

-----------------------------------------------------------------------------
spirit11.1.1.PXM.a > 

clrlmistats

Clear Local Management Interface Statistics—PXM1

Use the clrlmistats command to clear the local management interface (LMI) related statistics on the current PXM.

Syntax

clrlmistats

Syntax Description

None

Related Commands

dsplmistats

Attributes

Access level: ANYUSER

State: any

Log: no


Example

Clear the LMI statistics for PXM.

penguin.1.1.PXM.a > clrlmistats

Enabled        :          1   Port Status    :          1
VPI.VCI        :        3.31
Polling enable :          1
T393           :         10   N394           :          5
T394           :         10   N395           :          5
WaitStatus     :          0   WaitStAck      :          0
Retry Timer    :          0   Retry Count    :          1
Poll Timer     :          6   Trans Num      :         86
Status     Rx  :          0   Status     Tx  :          0
UpdtStatus Rx  :          0   UpdtStatus Tx  :          0
Status Enq Rx  :          0   Status Enq Tx  :          0
Status Ack Rx  :          0   Status Ack Tx  :          0
NodeStatus Rx  :          0   NodeStatus Tx  :          0
NodeStaAck Rx  :          0   NodeStaAck Tx  :          0
Bad PDU Rx     :          0   Bad PDU Len Rx :          0
Unknown PDU Rx :          0   Invalid I.E. Rx:          0
Invalid Trans  :          0
BPX IP Addr    :  172.3.3.62

penguin.1.1.PXM.a > 

clrlmitrace

Clear LMI Trace—PXM1

Use the clrlmitrace command to clear LMI trace on the switch.

Syntax

clrlmitrace

Syntax Description

None

Related Commands

None

Attributes

Access level: CISCO_GP

State: any

Log: no


Example

Clear the LMI trace.

spirita.1.PXM.a > clrlmitrace 

clrlog

Clear Log—PXM1

Use the clrlog command to clear specified or all event log files.

Syntax

clrlog [-log <log slot>]

Syntax Description

-log

Command delineator that precedes the log slot entry. The log slot of the file that you want to clear from the event log file.


Related Commands

dsplog, dsplogs

Attributes

Access level: SUPER_GP

State: any

Log: log


Example

Clear the applicable log files.

wilco.1.1.PXM.a > clrlog
Do you want to proceed (Yes/No)? Yes 
wilco.1.1.PXM.a > 

clrloginmsg

Clear Login Message—PXM1

Use the clrloginmsg command to delete the message that appears when any user logs into the switch.

Syntax

clrloginmsg

Syntax Description

None

Related Commands

cnfloginmsg, dsploginmsg

Attributes

Access level: ANYUSER

State: all

Log: log


Example

Delete the login message.

SES_SJ.1.PXM.a > clrloginmsg
Login message reset

Example

Confirm that no login message exists by using the dsploginmsg command.

SES_SJ.1.PXM.a > dsploginmsg


SES_SJ.1.PXM.a > 

clrpathtracebuffer

Clear Path Trace Buffer—PXM45, PXM1E

The clrpathtracebuffer command clears the path trace buffer for an individual connection.

Syntax

clrpathtracebuffer <portid> <vpi> <vci>

Syntax Description

portid

PNNI physical port identifier slot.port

vpi

VPI of the connection.

vci

VCI of the connection.


Related Commands

clrpathtracebuffers, dsppathtracebuffer, dsppathtracebuffers

Attributes

Log: yes

State: active

Privilege: SUPER_GP


Example

SES_SJ.1.PXM.a > clrpathtracebuffer 1.3 3 100


SES_SJ.1.PXM.a > 

clrpathtracebuffers

Clear Path Trace Buffers—PXM45, PXM1E

The clrpathtracebuffers command clears the path trace buffer for every connection on the switch.

Syntax

clrpathtracebuffers

Syntax Description

This command takes no parameters.

Related Commands

clrpathtracebuffer, dsppathtracebuffer, dsppathtracebuffers

Attributes

Access level: SUPER_GP

State: active

Log: yes


Example

SES_SJ.1.PXM.a > clrpathtracebuffers


SES_SJ.1.PXM.a > 

clrpncon

Clear a UNI or NNI Connection—PXM1

Use the clrpncon command to clear a specified call, or all calls within a logical port. This command does not apply to spvc endpoints.

Syntax

clrpncon <portid> [all | vpi] <vci>

Syntax Description

portid

Port ID of the call you want to clear, in the form of [shelf.]slot[:subslot].port[:subport].

all | vpi

VPI of the call to clear. Can be all or specific VPI.

Default: 0

vci

VCI of the call to clear. If no VCI is specified, this is a VP connection.


Related Commands

clrpncon, dsppncon

Attributes

Access level: SUPER_GP

State: active

Log: log


Example

For this example, use clrpncon to release the connection on port

1.1 with the VPI/VCI of 100 1000
spirita.1.PXM.a > clrpncon 1.1. all

or

spirita.1.PXM.a > clrpncon 1.1 100 1000


clrpnconstats

Clear UNI or NNI Connection Statistics—PXM1

Use the clrpnconstats command to clear existing call statistics for a specific port or all ports.

Syntax

clrpnconstats <portid>

Syntax Description

portid

The port identifier for the port on which you want to clear the call statistics. If portid is not specified, call statistics for all ports are cleared. Portid is in the form of [shelf.]slot[:subslot].port[:subport].


Related Commands

dsppnconstats

Attributes

Access level: SUPER_GP

State: active

Log: log


Example

Clear either UNI or NNI connection statistics with the applicable port ID.

spirita.1.PXM.a > clrpnconstats 0.1.1 

spirita.1.PXM.a >

clrqosdefault

Clear Quality of Service Default—PXM1

Use the clrqosdefault command to clear (resets to 0) the defaults for quality of service (QoS values) on the switch. You can clear the defaults for each service type on the switch.

Syntax

clrqosdefault

Syntax Description

None

Related Commands

cnfqosdefault, dspqosdefault

Attributes

Access level: GROUP1

State: active

Log: log


Example

Clear the QoS defaults on the switch. The system does not return a message unless an error occurs.

SES_SJ.1.PXM.a > clrqosdefault

clrscrn

Clear Screen—PXM1

Use the clrscrn command to remove the contents of the control terminal screen. After this command executes, the current command line prompt displays only on the terminal screen.

Syntax

clrscrn

Syntax Description

None

Related Commands

None

Attributes

Access level: ANYUSER

State: all

Log: no


Example

Clear the contents of the screen.

flyers01.1.17.AUSM.a > clrscrn
flyers01.1.17.AUSM.a > 

clrsigstats

Clear Signal Statistics—PXM1

Use the clrsigstats command to clear existing signaling statistics for a specific port or all ports.

Syntax

clrsigstats [<portid>]

Syntax Description

portid

If portid is not specified, then signaling statistics for all ports will be cleared. Port ID is in the form of [shelf.]slot[:subslot].port[:subport].


Related Commands

dspsigstats

Attributes

Access level: SUPER_GP

State: active

Log: log


Example

Clear the existing signal statistics with the applicable port ID.

spirit11.1.1.PXM.a > clrsigstats 0.1.1

Clearing Signaling Statistics for 1.1dspconinfo

spirit11.1.1.PXM.a >

clrsntpstats

Clear SNTP Statistics—PXM1

Use the clrsntpstats command to clear the SNTP statistics.

The recommended procedure is to

1. Enter the dspsntpstats command to display the current counters.

2. Enter the clrsntpstats command.

3. Enter the dspsntpstats commands again to ensure the all the counters have been reset to zero.

Syntax

clrsntpstats

Syntax Description

None

Related Commands

cnfsntp, dspsntp, dbgsntp

Attributes

Access level: ANYUSER

State: any

Log: no


Example

orses17.2.PXM.a > clrsntpstats 

orses17.2.PXM.a > dspsntpstats 

Statistic Counters For SNTP 
----------------------------- 
Receive server mode packets from servers in list: 0 
Receive server mode packets from servers not in list: 0 
Receive server mode packets which fail sanity check: 0 
Receive server mode packets which pass sanity check: 0 
Receive client mode packets: 0 
Receive other  mode packets: 0 
Send server mode packets: 0 
Send client mode packets: 0 
Polling Timer Expire Counter: 0 
Polling Wait Timer Expire Counter: 0 
Rollback Timer Expire Counter: 0 
Rollback Wait Timer Expire Counter: 0 
Switch From Primary To Secondary Counter: 0 
Switch From Secondary To Primary Counter: 0 
Switch From Secondary To Secondary Counter: 0

clrspvcnonpers

Clear SPVC Nonpersistent Endpoint—PXM1

Use the clrspvcnonpers command to release the specified nonpersistent endpoint. To tear down a specific endpoint, specify both the VPI and VCI. If a VPI is specified, all nonpersistent slaves on that VPI are released. The single-end provisioned SPVC is rerouted.


Note If the port ID is the only parameter specified, all the nonpersistent slaves on the port are cleared.


Syntax

clrspvcnonpers <portid> <vpi> <vci>

Syntax Description

portid

Specifies the interface where the nonpersistent slaves are released.

vpi

Specifies the VPI for the nonpersistent connections.

vci

Specifies the VCI for the nonpersistent connections.


Related Commands

cnfpnportcc, cnfsvcoverride, dsppnportcc,

Attributes

Access level: SUPER_GP

State: active

Log: log


Example

Clear the SPVC nonpersistent endpoints for port 2.3 with VPI set to 100.

SES_SJ.1.PXM.a > clrspvcnonpers 2.3 100
clrspvcnonpers: clear multiple calls. This might take a while. 

SES_SJ.1.PXM.a >

clrsscopstats

Clear SSCOP Statistics—PXM1

Use the clrsscopstats command to clear existing SSCOP statistics for a specific port or all ports.

Syntax

clrsscopstats [<portid>]

Syntax Description

portid

If portid is not specified, then SSCOP statistics for all ports will be cleared. portid is in the form of [shelf.]slot[:subslot].port[:subport].


Related Commands

disablesscop, dspsscop, dspsscopstats

Attributes

Access level: SUPER_GP

State: active

Log: no


Example

Clear statistics on all ports.

spirit11.1.1.PXM.a > clrsscopstats

spirit11.1.1.PXM.a >

Example

Clear statistics on a specified port (0.1.1).

spirit11.1.1.PXM.a > clrsscopstats 0.1.1

cmdhistory

Command History—PXM1

Use the cmdhistory command to view the last ten commands executed on the current card.

Syntax

cmdhistory

Syntax Description

None

Related Commands

help

Attributes

Access level: ANYUSER

State: all

Log: no


Example

View the last ten commands used for the current card.

spirit4.1.2.PXM.a > cmdhistory

Size of cmdHistory is currently 10 line(s)
  1 dspconcnt 2.39.45
  2 dsplmistats
  3 dsplmiloop
  4 dsplm
  5 clrportcnt
  6 dspportcnts
  7 dspportcnt
  8 dspportcnt 1
  9 dsplmistats
 10 cmdhistory

spirit4.1.2.PXM.a > 

cnfabrtparmdft

Configure ABR Traffic Parameters—PXM1

Use the cnfabrtparmdft command to configure default ABR traffic parameters used by a port to set up ABR SPVCs. The traffic parameters are used in the SETUP message at the source when setting up an SPVC for ABR service category.

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 the port to be configured, in the form of [shelf.]slot[:subslot].port[:subport].

-rif

Specifies the Rate Increase Factor (RIF). This controls the amount by which the cell transmission rate may increase upon receipt of an RM-cell. RIF is a power of two, ranging from 1/32768 to 1. The following are the acceptable choices for this parameter:

1 = 1/32768

2 = 1/16384

3 = 1/8192

4 = 1/4096

5 = 1/2048

6 = 1/1024

7 = 1/512

8 = 1/256

9 = 1/128

10 = 1/64

11 = 1/32

12 = 1/16

13 = 1/8

14 = 1/4

15 = 1/2

16 = 1

-rdf

Specifies the Rate Decrease Factor (RDF). This controls the decrease in the cell transmission rate. RDF is a power of two, ranging from 1/32768 to 1. Acceptable choices are the same as RIF. The default choice is 4 (= 1/4096).

-tbe

Transient buffer exposure.

Default: 1048320

-nrm

Specifies the maximum number of cells a source may send for each forward RM-cell. NRM is a power of two, ranging from 2 to 256. The following are the acceptable choices for this parameter:

1 = 2

2 = 4

3 = 8

4 = 16

5 = 32

6 = 64

7 = 128

8 = 256

The default choice is 55 (= 32 cells).

-trm

Specifies the upper bound on the time between forward RM-cells for an active source. TRM is 100 * a power of two milliseconds, ranging from 100*(2^-7) to 100*(2^0). The following are the acceptable choices for this parameter:

1 = 0.78125

2 = 1.5625

3 = 3.125

4 = 6.25

5 = 12.5

6 = 25

7 = 50

8 = 100

The default choice is 8 (= 100 msec)

-adtf

Specifies the Allowed Cell Rate (ACR) Decrease Time Factor. This is the time permitted between sending RM-cells before the rate is decreased to ICR. ADTF is in unit of 10 milliseconds, ranging from 1-1023 units, for example, .01 to 10.23 seconds.

Default: 50 (= 0.5 sec)

-cdf

Specifies the Cutoff Decrease Factor (CDF). This controls the decrease in ACR associated with missing RM-cell count (CRM). CDF is zero, or a power of two ranging from 1/64 to 1. The following are the acceptable choices for this parameter:

1 = 0

2 = 1/64

3 = 1/32

4 = 1/16

5 = 1/8

6 = 1/4

7 = 1/2

8 = 1

The default choice is 7 (= 1/2).

-fsd

Specifies the Fixed Source Delay (FSD) for the source. The Fixed Round-Trip Time (FRTT) is then accumulated during the call setup and is the sum of the fixed and propagation delays from the source to the furthest destination and back. FRTT is in unit of 10 microseconds, ranging from 0-16777215 units, for example, 0 to 167.77215 seconds.

Default: 0


Related Commands

dspabrtparmdft

Attributes

Access level: GROUP1

State: active

Log: no


Example

Configure the ABR traffic parameters with the applicable port ID and values. This example shows the -rif value is 8.

orses18.1.PXM.a > cnfabrtparmdft 1.1 -rif 8

cnfaddrreg

Configure Address Registration—PXM1

Use the cnfaddrreg command to set ILMI address registration options for a specified port. At least one keyword must be specified. This command can be used only when the port is added and administratively down. Currently, the address registration can be also enabled or disabled from the BPX cnfport command for backward compatibility reason. Furthermore, in order for the address registration to work, the peer must support address registration table and procedure. Therefore, you must ensure that the address registration is enabled on all three places to have address registration work.

Syntax

cnfaddrreg <portid> [yes | no]

Syntax Description

portid

Interface ID in the form of [shelf.]slot[:subslot].port[:subport].

yes | no

Enables or disables ILMI address registration on the port.

Default: yes


Related Commands

None

Attributes

Access level: GROUP1

State: active

Log: log


Example

Configure the address registration with the applicable port ID.

spirita.1.PXM.a > cnfaddreg 0.1.1 no

spirita.1.PXM.a >

cnfainihopcount

Configure AINI Hop Count—PXM1

Use the cnfainihopcount command to determine the maximum number of ATM Inter-Network Interface (AINI) links that a call can traverse. The specification applies to any call originating on the local node, and the area where the setting applies to the entire network.

The following functions are for the cnfainihopcount command:

Enable or disable the counter. This counter generates the hop counter information element (IE).

Specify the maximum number of AINI hops. The hop counter IE is initialized to this value in the setup message. With each AINI link that the setup message traverses, the counter is decremented. This hop count applies to only AINI interfaces. For more information, see the cnfpnportsig command.


Note To enable the AINI hop count, you must also enable it at each port by entering the cnfpnportsig command and enter enable for the -hopcntgen parameter.


Syntax

cnfainihopcount [-hopcntgen {enable |disable}] [-maxhops <value>]

Syntax Description

-hopcntgen

Enables the counting for AINI hops. Enter either enable or disable.

If you enable the hop count generation, the counter initializes the value for maxhops.

Default: enable

-maxhops

Determines the maximum number of AINI hops that a connection can take.

Range: 1-31

Default: 31


Related Commands

dspainihopcount

Attributes

Access level: SUPER_GP

State: any

Log: log


Example

Enable the AINI hop counting to specify a maximum of 20 hops.


Note No response appears unless an error occurs.


SES_SJ.1.PXM.a > cnfainihopcount -hopcntgen enable -maxhops 20

Example

Display the configuration for the AINI hop count.

SES_SJ.1.PXM.a > dspainihopcount
AINI Hop Counter Generation: enable
Max AINI Hops: 20


SES_SJ.1.PXM.a >

cnfapsln

Configure APS Line—PXM1

Use the cnfapsln command to set APS parameters for a specified line on the PXM card.

Syntax

cnfapsln <line> <SFBER> <SDBER> <Revertive> <WTR> <Direction> <KIK2>

Syntax Description

line

OC-3 line number. Enter the value 1.

SFBER

Signal failure BER threshold.

Range: 3-5

SDBER

Signal degrade BER threshold.

Range: 5-9

Revertive

Value to set the APS revertive or non-revertive function.

1: Non-revertive

2: Revertive

This setting allows the line to switch back to the working line after the Wait-To-Restore interval has expired and the working line SF/SD is cleared.

WTR

Number of minutes to wait before attempting to switch back to the working line, in the range 1through12. This setting is not applicable if the line is configured in non-revertive mode (Revertive set to 1).

Direction

Value to set the switching direction for either unidirectional or bidirectional.

1 = Unidirectional: APS line supports switching one end of the line.

2 = Bidirectional: APS line supports switching both ends of the line.

K1K2

Enables or disables the K1/K2 inband protocol on the protection line.

1: enable

2: disable


Related Commands

addapsln, delapsln, dspapsln, switchapsln

Attributes

Access level: SUPER_GP

State: active

Log: log


Example

To set the APS working line 1 on the active PXM card in slot 1 to have a signal failure bit error rate (BER) threshold of 10^^-5, a signal degrade BER threshold of 10^^-5, to enable switch back after signal failure or degradation cleared, to wait 2 minutes before attempting to switch back, to make switching bidirectional, and to enable the K1/K2 inband protocol on the protection line.

flyers01.1.1.PXM.a > cnfapsln 1 5 5 2 2 2 1
flyers01.1.1.PXM.a > 

cnfautocnf

Configure Auto Configuration—PXM1

Use the cnfautocnf command to enable or disable the ILMI auto configuration for a specified port.

Syntax

cnfautocnf <portid> [yes | no]

Syntax Description

portid

Interface ID in the form of [shelf.]slot[:subslot].port[:subport].

yes | no

Enables or disables the ILMI automatic configuration procedure on the port.

Default: yes



Tip This command is used only when the port is added and administratively down.


Related Commands

None

Attributes

Access level: GROUP1

State: active

Log: log


Example

Configure the auto configuration for ILMI.

spirita.1.PXM.a > cnfautocnf 0.1.1 no

spirita.1.PXM.a >

cnfcbclk

Configure Cellbus Clock—PXM1

Use the cnfcbclk command to configure the clock speed for the individual cellbuses. The cnfcbclk command lets you specify whether a cellbus runs at the default of 21 MHz or the double-speed rate of 42 MHz. Not every cellbus and the supported card slots can receive the double-speed clock. Use the dspcbclk command to see whether a particular cellbus can run at 42 MHz.

The backplane contains eight cellbuses: two cellbuses support two card slots and can support 21 MHz or 42 MHz clocking.

Syntax

cnfcbclk <cellBus> <clockRate>

Syntax Description

cellBus

Specifies the cellBus. Enter a string in the range of CB1-CB8. The string is not case sensitive.

clockRate

Specifies a clock rate of 21 MHz or 42 MHz. Enter either 21 or 42.


Related Commands

dspcbclk

Attributes

Access level: SUPER_GP

State: active

Log: log


Example

Display the current cellbus clock configuration to determine which slots can run at a higher rate. The display shows that all cellbuses currently have the default speed of 21 MHz.

SES_SJ.1.PXM.a > dspcbclk

     CellBus    Rate (MHz)    Slots     Allowable Rates (MHz)
    ----------------------------------------------------------
       CB1         21        3               21, 42
       CB2         21        5               21, 42
       CB3         21        10              21, 42
       CB4         21        12              21, 42
       CB5         21        11              21, 42
       CB6         21        6, 7            21, 42
       CB7         21        4               21, 42
       CB8         21        13, 14          21, 42

Example

Configure a double-speed clock for cellbus 5. Check the configuration.

SES_SJ.1.PXM.a > cnfcbclk cb5 42

SES_SJ.1.PXM.a > dspcbclk

     CellBus    Rate (MHz)    Slots     Allowable Rates (MHz)
    ----------------------------------------------------------
       CB1         21        3               21, 42
       CB2         21        5               21, 42
       CB3         21        10              21, 42
       CB4         21        12              21, 42
       CB5         42        11              21, 42
       CB6         21        6, 7            21, 42
       CB7         21        4               21, 42
       CB8         21        13, 14          21, 42

cnfcdvtdft

Configure CDVT Default—PXM1

Use the cnfcdvtdft command to modify the default CDVT to request UPC for cells received on a port. The new configuration applies to new incoming calls while existing calls remain intact. This command is used regardless of the state of the port.

Syntax

cnfcdvtdft <portid> <service_category> [num-of-micro-seconds]

Syntax Description

portid

Interface ID in the form of [shelf.]slot[:subslot].port[:subport].

service_category

ATM 4.0 service category. Enter one of the following bit rates:

cbr = constant bit rate

rtvbr = real-time variable bit rate

nrtvbr = non-real-time variable bit rate

ubr = unspecified bit rate

abr = available bit rate

num-of-micro-seconds

Specifies that the integer ranges from 10,000-5,000,000. The CDVT is expressed in microseconds.

If this parameter is not specified, the default will be used/restored.

Default: 250,000 microseconds


Related Commands

dspcdvtdft

Attributes

Access level: GROUP1

State: active

Log: log


Example

Configure the default CDVTD to request UPC for cells received at an unspecified bit rate of
250,000 microseconds:

spirita.1.PXM.a > cnfcdvtdft 0.1.1 ubr

spirita.1.PXM.a >

Example

Configure the default CDVTD to request UPC for cells received on at a constant bit rate of
250,000 microseconds.

spirita.1.PXM.a > cnfcdvtdft 0.1.1 cbr

spirita.1.PXM.a >

Example

Configure the default CDVTD to request UPC for cells received at an available bit rate of
240 microseconds.

spirita.1.PXM.a > cnfcdvtdft 0.1.1 abr 240

spirita.1.PXM.a >

cnfcmdabbr

Configure Command Abbreviation—PXM1

Use the cnfcmdabbr command to specify whether the CLI requires the entire name of a command or accepts the first unique string of characters that identifies a command. For example, loa is enough to identify if the loadrev command abbreviation is enabled.


Note The string lo is not enough to identify a particular command because of the logout command.


Syntax

cnfcmdabbr <flag>

Syntax Description

flag

Specifies a Boolean expression to enable or disable the command abbreviation.

Enter on to enable or off to disable the command abbreviation.


Related Commands

dspcmdabbr

Attributes

Access level: SERVICE_GP

State: active

Log: log


Example

Enable the command abbreviation.

SES_SJ.1.PXM.a > cnfcmdabbr on
Command abbreviations being allowed

Example

Verify the status by using the dspcmdabbr command.

SES_SJ.1.PXM.a > dspcmdabbr
Command abbreviations allowed

Example

Test the function of the command abbreviation by entering loa (for the loadrev command) without parameters.

SES_SJ.1.PXM.a > loa
ERR: Syntax: loadrev <slot> <revision> 
        slot -- optional; value: 15,16,31,32
           revision - revision number. E.g.,
                      2.0(1)
                      2.0(1.255)
                      2.0(0)I  or 2.0(0)A
                      2.0(0)P1 or 2.0(0)P2
                      2.0(0)P3 or 2.0(0)P4

cnfcon

Configure Connection—PXM1

Use the cnfcon command to modify the connection bandwidth, policing, and routing parameters of an existing endpoint. This command applies to only an SPVC or SPVP.

The following are the functions of the command parameters

Identifies the connection for a logical port, VPI, and VCI.

Specifies the bandwidth parameters for the local (master) end then the remote (slave) end.

Specifies the policing parameters for the connection as a whole.

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

You can assign a priority at the master end of an SPVC or SPVP. The PNNI controller routes higher priority connections before lower priority connections. For more information about assigning a priority to a connection, see the cnfpri-routing and dsppri-routing commands.

Syntax

cnfcon <portid> <vpi> <vci>

[-lpcr <local PCR>] [-lmcr <local MCR>] [-lscr <local SCR>] [-icr <local ICR>]
[
-lputil <local putil>] [-lmbs <local MBS>] [-cdvt <local CDVT>] [-lcdv <local CDV>]
[
-lctd <local CTD>] [-rpcr <remote PCR>] [-rmcr <remote MCR>] [-rscr <remote SCR>]
[
-rputil <remote putil>] [-rmbs <remote MBS>] [-rcdv <remote CDV>] [-rctd <remote CTD>]
[
-stats <enable(1)/disable(0)>] [-frame <enable(1)/disable(0)>] [-mc <Max Cost>]
[
-int_vsvd <internal segment>] [-ext_vsvd <external segment>] [-rtngprio <routingPriority>]

Syntax Description

portid

Interface ID in the form of [shelf.]slot[:subslot].port[:subport].

vpi

Specify the starting VPI to view active calls starting from the specified VPI of the specified port. The parameters can be used only if the port is specified.

Range: 0-4095

vci

Specify the starting VCI to view active calls starting from the specified VPI/VCI of the specified port. This parameters can only be used if VPI is specified.

Range: 32-65535

-lpcr

Local PCR range.

-lmcr

Local MCR range.

-lscr

Local SCR range.

-icr

Local ICR range.

-lputil

Specifies the local percentage utilization factor.

Range: 1-100

Default: 100

-lmbs

Local MBS range.

-cdvt

CDVT range.

-lcdv

Local CDV range.

-lctd

Local CTD range.

-rpcr

Remote PCR range.

-rmcr

This optional keyword can be used for specifying the MCR required for the connection in the remote -> local direction.

Default: rpcr

-rscr

This optional keyword can be used for specifying the SCR required for the connection in the remote -> local direction.

Default: rpcr

-rputil

Specifies the remote percentage utilization factor.

Range: 1-100

Default: 100

-rmbs

This optional keyword can be used for specifying the MBS required for the connection in the remote -> local direction.

Default: dspmbsdft value

-rcdv

This optional keyword can be used for specifying the CDV required for the connection in the remote -> local direction.

Default: -1

-rctd

Remote CTD range.

-stats

Enables or disables statistics. Enter one of the following options:

1: enable

2: disable

-frame

Enables or disables frame. Enter one of the following options:

1: enable

2: disable

-mc

Maximum cost.

-int_vsvd

Internal Segment VSVD. Enter one of the following options:

1: off

2: on

3: unspecified

-ext_vsvd

External Segment VSVD. Enter one of the following options:

1: off

2: on

3: unspecified

-rtngprio

The routing priority of the SPVC connection. This parameter is used to specify the connection priority of the SPVC when provisioning the master endpoint.

Note The -rtngprio parameter is not applicable to the slave end of the SPVC connection.

Range: 1-15

Default: 8


Related Commands

addcon, delcon, dncon, dspcon, rrtcon, upcon

Attributes

Access level: GROUP1

State: active

Log: log


Example

Configure the connection for port 1.6. Set the routing priority to 1.

SES_SJ.1.PXM.a > cnfcon 1.6 50 50 -rtngprio 1

SES_SJ.1.PXM.a >

cnfconpref

Configure Connection Preferred Route—PXM1

Use the cnfconpref command to associate a SPVC/P connection to a preferred rout by using the preferred route id value.

Syntax

cnfconpref <portId> <vpi> <vci> <rteID> [-assoc {set | clr}] [-direct {set | clr}]
[-onPrefRte {yes | no}]

Syntax Description

portId

Specifies the port where the master end of the SPVC is anchored. The format is [shelf.]slot[:subslot].port[:subport].

vpi

Specifies the virtual path identifier (VPI) of the SPVC.

vci

Specifies the virtual circuit identifier (VCI) of the SPVC. If set to 0, SPVC becomes a VPC.

rteId

Specifies a number between one and the maximum database size that uniquely identifies the route location in the database.

Range: 1-1000

-assoc

Indicates either associating or disassociating a route with a preferred route when the SPVC is modified. Enter one of the following options:

set—Specifies that the SPVC is configured to use the given preferred route. The preferred route ID must be specified.

clr—Removes the current configuration.

Default: set

-direct

Indicates a change to the setting of the directed status for the SPVC. Enter one of the following options:

set—Specifies that the SPVC is set to use the preferred route as a directed route.

clr—Clears the directed flag. If a preferred route has not been configured, the parameter is ignored. If the parameter is not stated in the CLI, the setting is not changed.

-onPrefRte

If the SPVC connection is already routed on a route that is the same as the preferred route of the associated SPVC, you can indicate the association with the -onPrefRte option. Enter either yes or no. Before setting this option to true, the user should make sure that the connection is really routed on the preferred route.The default for this option is no.


Related Commands

addpref, delpref, dsppref, dspprefs, modpref

Attributes

Access level: GROUP1

State: active

Log: log


Example

Associate a preferred route port 1, VPI/VCI = 1.100 route ID = 2.
SES_SJ.1.PXM.a > cnfconpref 1 1 100 2 -assoc set -direct set -onPrefRte yes

Example

Disassociate a preferred route port 1, VPI/VCI = 1.100 route ID = 2.
SES_SJ.1.PXM.a > cnfconpref 1 1 100 2 -assoc clr -direct set -onPrefRte yes

cnfconsegep

Configure Connection Segment Endpoint—PXM1

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


Note Before executing this command, continuity check must be de-activated. Otherwise, continuity check failure will occur for the connection. This command is used with the conntrace command for fault isolation.


Syntax

cnfconsegep <portid> <vpi> [vci]

Syntax Description

portid

Interface ID in the form of [shelf.]slot[:subslot].port[:subport].

vpi

VPI of the connection.

vci

VCI of the connection. The default VCI value is 0 for the VP connection.


Related Commands

delconsegep

Attributes

Access level: GROUP1

State: active

Log: log


Example

Configure a connection segment endpoint.

spirita.1.PXM.a > cnfconsegep 0.1.1 50 50

cnfdate

Configure Date—PXM1

Use the cnfdate command to set the system date.

Syntax

cnfdate <mm/dd/yyyy>

Syntax Description

mm/dd/yyyy

Month, date, and year.


Related Commands

dspdate

Attributes

Access level: SUPER_GP

State: active

Log: log


Example

Set the system date.

wilco.1.1.PXM.a> cnfdate 12/17/1999

cnfdiag

Configure Diagnostics—PXM1

Use the cnfdiag command to enable either online or offline diagnostics. The cnfdiag command also configures the time settings for the start time and coverage to run the offline diagnostics. When you enter the cnfdiag command with not parameters, it displays the current configuration and status of the diagnostics.

The cnfdiagall command is identical to the cnfdiag command except that it configures all the slots at once.

Syntax

cnfdiag <slot> <onEnb> <offEnb> [<offCover> <offStart> <offDow>]

Syntax Description

slot

Configures the diagnostics for the slot of the card.

onEnb

Enables or disables online diagnostics.

Default: disable

offEnb

Enables or disables offline diagnostics.

Default: disable

offCover

Sets the offline diagnostics coverage time to light, medium, or full.

The following are the parameter measurements:

Parameter
Measurement

light

5 min or less

medium

30 min or less

full

60 min or less

offStart

Sets the time for the offline diagnostics to begin using 24-hour time. The format is hh:mm.

The following is an example:

22:30

offDow

Sets the day of the week to run the offline diagnostics. The format is SMTWTFS. The following is an example:

-M-W--- = Mon and Wed only

Related Commands

cnfdiagall, dspdiagcnf

Attributes

Access level: SERVICE_GP

State: any

Log: no


Example

Configure the online or offline diagnostics with the applicable time settings.

SES_SJ.1.PXM.a > cnfdiag 1 enable disable light 22:30 -M-W

cnfdiagall

Configure Diagnostics All—PXM1

Use the cnfdiagall command to enable and configure the online or offline diagnostics for all card slots.


Note This command is identical to the cnfdiag command except that it effects all slots instead of just one.


When you enter the cnfdiagall command with no parameters, it displays the current configuration and status of the diagnostics.

Syntax

cnfdiagall <onEnb> <offEnb> [<offCover> <offStart> <offDow>]

Syntax Description

onEnb

Enables or disables online diagnostics.

offEnb

Enables or disables offline diagnostics.

offCover

Sets the offline diagnostics coverage time to light, medium, or full.

The following are the parameter measurements:

Parameter
Measurement

light

5 min or less

medium

30 min or less

full

60 min or less

offStart

Sets the time for the offline diagnostics to begin using 24-hour time. The format is hh:mm.

The following is an example:

22:30

offDow

Sets the day of the week to run the offline diagnostics. The format is SMTWTFS.

Enter a dash (-) for days where you do not want diagnostics to run.

The following is an example:

-M-W--- = Mon and Wed only

Related Commands

cnfdiag

Attributes

Access level: SERVICE_GP

State: any

Log: no


Example

Configure all the diagnostics for all the card slots.

SES_SJ.1.PXM.a > cnfdiagall enable disable light 22:30 -M-W

cnfe164 justify

Configure E.164 AESA Justification—PXM1

Use the cnfe164justify command to configure whether the E.164 AESAs with the E.164 AFI are converted to the left or right-justified encoding format. The default is left-justified.

To ensure that PNNI searches the address correctly, all nodes in the PNNI network must be set for the same justification.

Syntax

cnfe164justify {left | right}

Syntax Description

left | right

Convert E.164 AESAs with the E.164 AFI to the left or right.

Default: left


Related Commands

None

Attributes

Access level: SUPER_GP

State: active

Log: log


Example

Configure the E.164 AESAs with the E.164 AFI to be converted to the left-justified encoding format.

SES_SJ.1.PXM.a > cnfe164justify left

SES_SJ.1.PXM.a >

Example

Configure the E.164 AESAs with the E.164 AFI to be converted to the right-justified encoding format.

SES_SJ.1.PXM.a > cnfe164justify right

SES_SJ.1.PXM.a >

cnfenhiisp

Configure Enhanced IISP—PXM1

Use the cnfenhiisp command to enable or disable the enhanced IISP features on a port. This command is used only on an IISP port, regardless of the state of the port. The new configuration applies to new incoming calls while existing calls remain intact.

Currently only the support of VBR-rt service category is controlled by this command. If the support is enabled on the port, the VBR-rt service category, which uses an illegal combination of traffic parameters in the Broadband Bearer Capability (BBC) IE, is transported across the IISP port without any modification.

Syntax

cnfenhiisp <portid> {yes | no}

Syntax Description

portid

Interface ID in the form of [shelf.]slot[:subslot].port[:subport].

yes | no

Enables or disables the support of the enhanced IISP on the port.

Default: no


Related Commands

dspenhiisp

Attributes

Access level: GROUP1

State: active

Log: log


Example

Enable the support of the enhanced IISP on port 1.6.

SES_SJ.1.PXM.a > cnfenhiisp 1.6 yes

SES_SJ.1.PXM.a >

Example

Disable the support of the enhanced IISP on port 1.6.


SES_SJ.1.PXM.a > cnfenhiisp 1.6 no

SES_SJ.1.PXM.a >

cnffltset

Configure Filter Set—PXM1

Use the cnffltset command to configure or modify an existing filter set. The configuration is in the form of adding more addresses to the filter set, or changing the access mode or address field of a filter set entry.

Syntax

cnffltset <name>{-address template -length length [-plan {e164 | nsap}][-list {calling | called}]}
[
-index number] [-accessMode {permit | deny}]

Syntax Description

name

Name of the filter set, consisting up to 29 characters.

-address

template: The NSAP address, consisting of 1-40 digits, or the E.164 address, consisting of 1-15 digits. The address template can have prefix address digits followed by a trailing string "..." in which case, only the prefix part of the address is considered in the address pattern match. Likewise, the address template can have an initial string "..." followed by address digits, in which case, the trailing address digits are alone considered in the address pattern match. An address template can contain the character "*" in which case, that digit is not considered in the address pattern match.

The address can be added to an existing filter set.

The default is modifying the -accessMode field of a filter element, using only the index, in which case the address field is not necessary.

-length

Length in bits (if NSAP) or bytes (if E.164). If the address template consists of the string "..." or the character "*" the length field contents do not matter.

A length must be specified if the address is specified.

-plan

Address plan, either E.164 or NSAP. Use this parameter only if the address field is also specified.

Default: nsap

-list

Specifies the address list which is either calling or called. You can specify this field only if you also specify the address field.

Default: calling

-index number

Determines the order in which the address entries in a filter are set.

Range: 1-65535

Default: 1

-accessMode

Indicates whether or not to accept (permit) or reject (deny) a call on the port if the address pattern-matching succeeds.

Default: permit


Related Commands

delfltset, dspfltset

Attributes

Access level: SUPER_GP

State: active

Log: log


Example

pnnises1.1.PXM.a > cnffltset firstfilter -address  
4712345678901234567890123456789012345678 
-length 160 -plan nsap -list calling -index 1 -accessMode deny

cnfilmienable

Configure ILMI Enable—PXM1

Use the cnfilmienable command to enable ILMI on a PNNI port. Prior to the cnfilmienable command, you must use the dnpnport command to de-activate the port.

Syntax

cnfilmienable <portid> [yes | no]

Syntax Description

portid

PNNI logical port, in the format [shelf.]slot[:subslot].port[:subport]. Using the short form where only the mandatory elements are appropriate, the port ID has the format slot.port.

yes | no

Enables or disables ILMI on the switch. Enter yes to enable or no to disable.

Default: yes


Related Commands

None

Attributes

Access level: GROUP1

State: active

Log: log


Example

Show the cnfilmienable command line that enables ILMI on a PNNI port. Before you enter this command, you must use the dnpnport command to take down PNNI on that port.


spirita.2.PXM.a > dspilmi 1:1.1:1
INFO:  No ilmi address registered

spirita.2.PXM.a > dnpnport 1:1.1:1
 
spirita.2.PXM.a > cnfilmienable 1:1.1:1 yes
 
spirita.2.PXM.a > uppnport 1:1.1:1
spirita.2.PXM.a > 

cnfilmiproto

Configure ILMI Protocol—PXM1

Use the cnfilmiproto command to configure how PNNI reacts to ILMI events that occur on the VSI slave (a service module). Use the dsppnilmi command to confirm changes to the configuration.

Syntax

cnfilmiproto <portid> [-securelink {yes | no}][-attachmentpoint {yes | no]
[-modlocalattrstd {yes | no]

Syntax Description

portid

Identifies a PNNI physical port in the form of [shelf.]slot[:subslot].port[:subport].

-securelink

Sets the flag -securelink to make PNNI release the call if it loses the connection to the ILMI slave. The following options are

no: do not enable the ILMI secure link protocol.

yes: disable the ILMI secure link protocol.

Default: yes

-attachmentpoint

Sets the flag -attachmentpoint to make PNNI release the call if the slave ILMI session sees changes in peer information, for example, the system name or system ID. The following options are

no: do not enable the detection loss of the attachmentpoint flag.

yes: enable the detection loss of the attachmentpoint flag.

Default: yes

-modlocalattrstd

Sets the flag -modlocalattrstd to make PNNI release the call if the slave ILMI sees the ATM layer (partition resource) changes, for example, VPI or VCI. The following options are

no: disable the ILMI standard procedure for modification of the local ATM parameter.

yes: enable the ILMI standard procedure for modification of the local ATM parameter.

Default: yes


Related Commands

cnfilmienable, dsppnilmi

Attributes

Access level: GROUP1

State: active

Log: log


Example

Configure the ILMI protocol port 1.6. The -securelink, -attachmentpoint, and -modlocattrstd flags are enabled.

spirita.1.PXM.a > cnfilmiproto 1.6 -securelink yes -attachmentpoint yes -modlocalattrstd 
yes

spirita.1.PXM.a >

Example

Verify the results by entering the dsppnilmi command for port 1.6.

SES_SJ.1.PXM.a > dsppnilmi 1.6

Port:  1.6                 Port Type:  Private UNI      Side:  network  
Autoconfig:  disable      UCSM: disable   
Secure Link Protocol:  enable    
Change of Attachment Point Procedures:  enable    
Modification of Local Attributes Standard Procedure:  enable    
Addressreg:  disable                             
VPI:       0                VCI:       0
Max Prefix:       0      Total Prefix:       0
Max Address:       0     Total Address:      0
Resync State:      0     Node Prefix: yes       
Peer Port Id:           0   System_Id : 0.0.0.0.0.0 
Peer Addressreg:  disable   
Peer Ip Address : 0.0.0.0 
Peer Interface Name :   
ILMI Link State : Disable                  
ILMI Version : ilmi40

INFO:  No Prefix registered

INFO:  No ilmi address registered

SES_SJ.1.PXM.a >

cnfintfcongth

Configure Interface Congestion Thresholds—PXM1

Use the cnfintfcongth command to set interface congestion thresholds parameters for a logical port. The thresholds apply to incoming calls and status enquiries. When the upper congestion limit is reached, the port can block incoming calls and adjust the pace of status enquiries.


Note You must specify at least one keyword.


Syntax

cnfintfcongth <portid> [-setuphi {setupHiThreshold}]]
[-unackedStatEnqLo unackedStatEnqLothreshold]
[-unackedStatEnqHi unackedStatEnqrHithreshold]

Syntax Description

portid

Specifies the interface ID in the form of [shelf.]slot[:subslot].port[:subport].

-setuphi

Determines the number of connection setup messages per second. Above this number, the condition of setup messages on the interface is congested.

Range: 1-105 cps

Default: 100 cps

-unackedStatEnqLo

Determines the number of status enquires yet to be acknowledged by the peer-to peer interface. Below this value, the congestion condition for status enquiries at the interface level is dropped.

Range: 1-500 messages

Default: 40

-unackedStatEnqHi

Determines the number of status enquires yet to be acknowledged by the peer-to-peer interface. When this threshold is reached, the interface is considered to be congested with status enquiries.

Range: 1-500 messages

Default: 100


Related Commands

dspintfcongth

Attributes

Access level: GROUP1

State: active

Log: log


Example

Configure a congestion threshold of 100 cps for setup messages for port 1.5.

SES_SJ.1.PXM.a > cnfintfcongth 1.5 -setuphi 100

Example

Verify the results by entering the dspintfcongth command.

SES_SJ.1.PXM.a > dspintfcongth 1.5

Congestion Thresholds for port : 1.5 

Parameter            Value        unit
---------            -----        ----
setuphi              100          cps
unackedStatEnqLo     40           messages
unackedStatEnqHi     100          messages

SES_SJ.1.PXM.a >

Example

Set the status enquiries low to 50 cps and the high to 60 cps.

SES_SJ.1.PXM.a > cnfintfcongth 1.5 -unackedstatenqlo 50 -unackedstatenqhi 60

Example

Verify the results by entering the dspintfcongth command.

SES_SJ.1.PXM.a > dspintfcongth 1.5

Congestion Thresholds for port : 1.5 

Parameter            Value        unit
---------            -----        ----
setuphi              100          cps
unackedStatEnqLo     50           messages
unackedStatEnqHi     60           messages

SES_SJ.1.PXM.a >

cnfintvsvd

Configure Interface VS/VD—PXM1

Use the cnfintvsvd command to enable the internal or external virtual source/virtual destination (VS/VD) on a PNNI port. This command is used for SVC calls only and only for configuring ABR parameters. The cnfintvsvd command applies to ports configured for UNI 4.0 or higher. The port must be administratively down. For more information, see the dnpnport command.

Syntax

cnfintfvsvd <portid> [-internal {off |on | unspecified}][-external {off | on | unspecified}]

Syntax Description

portid

Identifies a PNNI physical port and has the format [shelf.]slot:subslot.port:subport.

-internal

Indicates the internal loop for VS/VD.

Default: unspecified

The following are the options:

Parameter
Description

off

At the port level, the VS/VD service for available bit rate (ABR) connections is disabled. Therefore, for an ABR connection to have VS/VD support, you must use to enable it.

on

At the port level, the VS/VD service for ABR connections is enabled. Therefore, all ABR connections on the port have VS/VD support. If you do not want a particular ABR connection to have VS/VD, you must use to disable it for that connection.

unspecified

The port defaults to the VS/VD capability for the specific port-level SCT.

Default: off

-external

Indicates the external loop for VS/VD.

The following options are

Parameter
Description

off

At the port level, the VS/VD service for ABR connections is disabled. Therefore, for an ABR connection to have VS/VD support, you must use to enable it.

 

on

At the port level, the VS/VD service for ABR connections is enabled. Therefore, all ABR connections on the port have VS/VD support. If you do not want a particular ABR connection to have VS/VD, you must use to disable it for that connection.

unspecified

The port defaults to the VS/VD capability for the specific port-level SCT.

Default: off


Related Commands

addfltset, delfltset, dspfltset

Attributes

Access level: GROUP1

State: active

Log:


Examples

Example 1 : 
Failure to set VSVD because of port up
pnnises1.1.PXM.a > cnfintfvsvd 11.1 -internal on

ERROR: Port is not out-of-service 

Syntax: cnfintfvsvd <portid> 

       [-internal {off|on|unspecified}]

       [-external {off|on|unspecified}]

shelf.slot:subslot.port:subport -- [shelf.]slot[:subslot].port[:subport]default=Mandatory 
Parameter; shelf -- valid value = 0
        internal -- internal {off|on|unspecified (default =unspecified)} 
        external -- internal {off|on|unspecified (default = unspecified)} 

Example 2 : 
Failure to set VSVD because of non UNI4.0 ports 
pnnises1.1.PXM.a > cnfintfvsvd 10.1 -internal on

ERROR: Cannot set vs/vd on a UNI3.0/UNI3.1/IISP interfaceTo turn on the VSVD for the port
pnnises1.1.PXM.a > cnfintfvsvd 1.3 -internal on

Example 3 : 
To turn on the VSVD for the port

pnnises1.1.PXM.a > cnfintfvsvd 1.3 -internal on
pnnises1.1.PXM.a > dsppnport 1.3

Port:               1.3               Logical ID:       66304
IF status:          up                Admin Status:     up
VSVD Internal Loop: on
VSVD External Loop: unspecified
UCSM:               enable            SVC Routing Pri:  8
Auto-config:        enable            Addrs-reg:        enable
IF-side:            network           IF-type:          uni
UniType:            private           Version:          uni4.0
PassAlongCapab:     n/a
Input filter:       0                 Output filter:    0
minSvccVpi:         0                 maxSvccVpi:       255
minSvccVci:         35                maxSvccVci:       65535
minSvpcVpi:         1                 maxSvpcVpi:       255

       (P=Configured Persistent Pep, NP=Non-Persistent Pep, Act=Active)
       #Spvc-P:  #Spvc-NP:  #SpvcAct:  #Spvp-P:  #Spvp-NP:  #SpvpAct:
p2p :  3000      0          0          0         0          0
p2mp:  0         0          0          0         0          0
       #Svcc:     #Svpc:        #Ctrl:     Total:
p2p :  0          0             0             0
p2mp:  0          0             0             0

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

cnflmitrace

Configure LMI Trace—PXM1

Use this command to see the LMI messages exchanged between two nodes for each configured LMI trunk.

The messages can be one of five different types, with corresponding hex codes: STATUS_REPORT (0x7E), STATUS_ENQUIRY (0x76), UPDATE_STATUS (0x77), STATUS_ACK (0x7F) and NODE_STATUS (0x7A). The logical trunk numbers are 0 based. For example, if the dsplmilink command shows the trunk id to be 1.1 (slot.port), then the logical trunk number is (port-1) i.e. 0

The direction indicates whether to log LMI messages that are being received by the local node, or those being transmitted, or both.h.

Syntax

cnflmitrace <BufWrap> <TrcEnable> <FuncCode> <Ltrk> <Dir>

Syntax Description

BufWrap

Enables or disables the buffer wrap. Enter yes to enable the buffer, or no to disable it.

TrcEnable

Enables or disables the LMI trace. Enter yes to enable the LMI trace, or no to disable it.

FuncCode

String of function codes in HEX separated by commas.

Ltrk

String of trunk numbers in HEX, separated by commas.

Dir

Direction to be traced.


Related Commands

clrlmistats, clrlmitrace, dsplmistats, dsplmitrace

Attributes

Access level: CISCO_GP

State: any

Log: no


Example

mpgses1.1.PXM.a > cnflmitrace Yes Yes 0x7A,0x7E 0 *

cnfloginmsg

Configure Login Message—PXM1

Use the cnfloginmsg command to create a message that appears when any user logs into the switch. The CLI prompts you for a login message. The maximum length is 500 characters. Also, the CLI instructs you to terminate a message by putting a period on line with no other characters on that line.

Syntax

cnfloginmsg

Syntax Description

None

Related Commands

clrloginmsg, dsploginmsg

Attributes

Access level: ANYUSER

State: all

Log: no


Example

Create the following login message:


Note Complete the message by typing a period on the next line.


Call system administrator before using this switch
.

SES_SJ.1.PXM.a > cnfloginmsg
Enter new Login Message (Less than 500 characters)
To complete message enter a line with only a "."
Call system administrator before using this switch
.
Following message will be displayed when user logs in :
Call system administrator before using this switch

Confirm entry of new message Y/N:(N) y
Storing changed Login message 

Example

Check the message by entering the dsploginmsg command.

SES_SJ.1.PXM.a > dsploginmsg

Call system administrator before using this switch

SES_SJ.1.PXM.a >

cnfmbsdft

Configure the MBS Default—PXM1

Use the cnfmbsdft command to modify the default MBS for SPVCs on a port. The applicable service types are real-time and nonreal-time variable bit rate (rt-VBR and nrt-VBR).

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

The new configuration applies to new incoming calls while existing calls remain intact. The cnfmbsdft command is used regardless of the state of the port.

Syntax

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

Syntax Description

portid

Identifies a PNNI physical port in the form of [shelf.]slot[:subslot].port[:subport].

service_category

ATM 4.0 service category. Enter one of the following options:

cbr = constant bit rate

rtvbr = real time variable bit rate

nrtvbr = non-real time variable bit rate

ubr = unspecified bit rate

abr = available bit rate

num-of-cell

Determines the integer in the range of 1-5,000,000. The MBS is expressed in cells.

If this parameter is not specified, the default is either used or restored.

Range: 0-2147483647 cells.

Default: 1024 cells


Related Commands

dspmbsdft

Attributes

Access level: GROUP1

State: active

Log: log


Example

Configure the MBS default to be 1000 cells for nrt-vbr for port 2.3.

SES_SJ.1.PXM.a > cnfmbsdft 2.3 nrtvbr 1000
SES_SJ.1.PXM.a > 

Example

Verify the results by entering the dspmbsdft command for port 2.3.

SES_SJ.1.PXM.a > dspmbsdft 2.3

           rt-vbr:       nrt-vbr:
  MBS:        1024           1000

SES_SJ.1.PXM.a > 

Example

Configure the MBS default to be 900 cells for rt-vbr for port 2.3.

SES_SJ.1.PXM.a > cnfmbsdft 2.3 rtvbr 900
SES_SJ.1.PXM.a > 

Example

Verify the results by entering the dspmbsdft command for port 2.3.

SES_SJ.1.PXM.a > dspmbsdft 2.3

           rt-vbr:       nrt-vbr:
  MBS:         900           1000

SES_SJ.1.PXM.a > 

cnfname

Configure Name—PXM1

Use the cnfname command to set the name of the SES PNNI node. This name cannot be propagated throughout the network.

Syntax

cnfname <name>

Syntax Description

name

Name of the SES PNNI node that consists of up to 8 alpha-numeric characters.


Related Commands

None

Attributes

Access level: SUPER_GP

State: active

Log: log


Example

Configure the node name for the switch.

spirita.1.PXM.a > cnfname NewName
cnfname: Configured this node name to NewName Successfully.

NewName.1.PXM.a >

cnfndparms

Configure Node Parameters—PXM1

Use the cnfndparms command to specify numerical values or to enable a set of node-level parameters. The cnfndparms command has parameters that consist of an option number, a value, or a yes or no option. The configuration resides in nonvolatile RAM and utilizes a system reset or power cycle.

For information on related alarms, see dspenvalms and dspndalms commands.

Syntax

cnfndparms <option_number> <option_value>

Syntax Description

option_number

A number that selects an option. The current number range is 1-8. If you do not enter an option number, the interface displays all options. If you enter an option number but no value, the interface prompts for appropriate input.

The following are the eight option numbers:

Option
Description

1

Specifies the card reset sliding window in seconds. The number of seconds to count the resets of the shelf management cards. A value of 0 means an infinite time period. The impact of an infinite time period is that only a specified count of resets can stop the resets.

Range: 0-65355 (16-bit decimal number)

Default: 3600 sec (1 hour)

2

Specifies the maximum card reset per window. The maximum number of resets of the shelf management card group per time period. You can specify the time period with option 1. The meaning of the value of 0 for this parameter is an infinite number of resets per time period.

Range: 0-255

Default: 3 resets per period

3

Enables or disables core card core redundancy. Enter yes to enable or no to disable alarms on a missing, redundant core card. Because the default is enable, the alarm appears when a redundant core card is not installed.

Default: enable

4

Enables or disables the expanded memory on PXM45B. Enter yes to enable or no to disable. When you enable expanded memory, the system responds with the following message:

More connections and interfaces can be added.

Default: disable

option_number

5

Specifies the required power supply module bitmap. The locations are identified for the required power supplies in an AC-powered system. The following are the 8-bit hexadecimal types:

0x0: The default means that no specified power supply requirement is related to this particular form of alarm generation. But the configuration must still meet the power requirements of the switch.

0x01: PSU A1 is required.

0x02: PSU A2 is required.

0x04: PSU A3 is required.

0x10: PSU B1 is required.

0x20: PSU B2 is required.

0x40: PSU B3 is required.

Default: 0x0

6

Specifies the trap manager aging timeout value in hours. The node configuration occurs before the trap manager registration is deleted. The default value of 0 means no aging takes place. Therefore, to delete a particular trap manager, you can enter the deltrapmgr command.

Range: any integer

Default: 0

7

Specifies the primary IP interface for network management. The primary interface type is discovered by CWM ILMI node discovery mechanism. The following are the range of values for option 7:

0: The atm0 interface will be the primary.

1: No interface will be used. This prevents ILMI Node Discovery.

2: The lnPci0 interface will be the primary.

Default: 0

8

Specifies the secondary IP interface for network management. The IP address of the secondary IP interface is sent with the primary IP address to other MGX nodes. CWM can then discover both IP addresses from any node.

option_value

The option value can be a decimal or hexadecimal number or a yes or no entry. The following are the possible ranges or values for each type of numeric option:

8-bit decimal: 0-255

16-bit decimal: 0-65535

32-bit decimal: 0-4294962795

8-bit hexadecimal: 0-0xff

16-bit hexadecimal: 0-0xffff

32-bit hexadecimal: 0-0xffffffff


Related Commands

dspndparms, dspndalms, dspenvalms

Attributes

Access level: SUPER_GP

State: active

Log: no


Example

Enter the cnfndparms command without an option number and note the response. Specify a LAN interface for the secondary network management interface.

SES_SJ.1.PXM.a > cnfndparms
SES_SJ                           System Rev: 03.00   Jan. 31, 2002 23:14:43 GMT
SES-CNTL                                             Node Alarm: NONE
NODE CONFIGURATION OPTIONS
Opt#  Value       Type           Description
----  -----       ----           -----------
1     3600        16bit Decimal  SHM Card Reset Sliding Window (secs)         
2     3           8bit Decimal   SHM Max Card Resets Per Window (0 = infinite)
3     Yes         Boolean        Core Redundancy Enabled                      
4     0x0         8bit Hex       Required Power Supply Module Bitmap          
5     0           8bit Decimal   Trap Manager Aging timeout value(Hour(s))    
6     atm0        8bit Decimal   Primary IP interface for Netmgmt             
7     lnPci0      8bit Decimal   Secondary IP interface for Netmgmt           

Enter option number (1-7): 8
ERR: Option number 8 not in range 1-7
Syntax: cnfndparms <option_number> <option_value>
    <option_number>        - number of option to configure
            use dspndparms to see valid options
    <option_value>         - value for option
            if option is boolean:       (Y/N)
            if option is 8bit Decimal:  (0 - 255)
            if option is 16bit Decimal: (0 - 65535)
            if option is 32bit Decimal: (0 - 4294962795)
            if option is 8bit Hex:      (0 - 0xff)
            if option is 16bit Hex:     (0 - 0xffff)
            if option is 32bit Hex:     (0 - 0xffffffff)

SES_SJ.1.PXM.a > 

cnfnodalcongth

Configure the Nodal congestion Threshold—PXM1

Use the cnfnodalcongth command to set nodal congestion threshold parameters. The thresholds relate to call setup messages. stauts enquiries, queue levels, and so forth. You must specify at least one optional parameter.

Syntax

cnfnodalcongth [-setuphi <value>] [-statenqlo <value>] [-statenqhi <value>][-connpendlo <value>] [-connpendhi <value>] [-incompjour <value>][-vsiqmild <value>] [-vsiqmedium <value>]
[-vsiqsevere <value>]

Syntax Description

-setuphi

The number of connection setup message per second, above which setup messages are dropped within a second.

Range: 1-105 cps

Default: 100

-statenqlo

The number of status enquiry message per second, below which the status enquiry congestion condition abates.

Range: 1-500 cps

Default: 100 cps

-statenqhi

The number of connection setup messages per second, above which the status enquiry congestion condition sets in.

Range: 1-500 cps

Default: 200 cps

-connpendlo

The aggregate number of connections in the establishment phase below which the establishment congestion abates.

Range: 1-1000 connections

Default: 400 connections

-connpendhi

The aggregate number of connections in the establishment phase above which the establishment congestion sets in.

Range: 1-1000 connections

Default: 500 connections

-incompjour

The number of incomplete journaling cycles above which the journaling speed is increased.

Range: 1-10 cycles

Default: 5 cycles

-vsiqmild

The Q depth above which VSI master is mildly congested. This is represented as a percentage of VSI master-slave communication window size. This threshold is applicable to all the interfaces in the node.

Range:1-175

Default: 5

-vsiqmedium

The Q depth above which VSI master is congested at a medium level. This is represented as a percentage of VSI master-slave communication window size. This threshold is applicable to all the interfaces in the node.

Range: 1-175

Default: 10

-vsiqsevere

The Q depth above which VSI master is severely congested. This is represented as a percentage of VSI master-slave communication window size. This threshold is applicable to all the interfaces in the node.

Range: 1-175

Default: 20


Related Commands

dspnodalcongth

Attributes

Access level: SUPER_GP

State: active

Log: log


Example

Configure the nodal length threshold with the applicable setup and status enquiry messages.

SES_SJ.1.PXM.a > cnfnodalcongth -setuphi 80 -vsiqmild 100 -vsiqmedium 140 -vsiqsevere 175

Example

Verify the results by entering the dspnodalcongth command.

SES_SJ.1.PXM.a > dspnodalcongth
Parameter         Value      Unit
=================================
setuphi(prov)       80       cps
setuphi(curr)       80       cps
statenqlo          100       cps
statenqhi          200       cps
connpendlo         400       messages
connpendhi         500       messages
incompjour           5       cycles
vsiqmild           100       multiplier
vsiqmedium         140       multiplier
vsiqsevere         175       multiplier

cnfnodalfd

Configure Nodal Frame Discard—PXM1

Use the cnfnodalfd command to install or not to install frame discard if the AAL5 IE is present. This changes the information used by the switch when determining whether or not to install frame discard on SVCs. UNI 4.0 signaling allows explicit signaling of frame discard. Prior to UNI 4.0, the presence of the AAL5 IE was used to determine whether or not to install frame discard. If the AAL5 IE is present, frame discard is installed. However, UNI 4.0 signaling element controlling frame discard overrides the configuration specifying to use AAL5 IE.


Note The default is to install the frame discard on the presence of the AAL5 IE in the SETUP message.


Syntax

cnfnodalfd <enable | disable>

Syntax Description

enable | disable

Enables or disables the installation of frame discard on the presence of the AAL5 IE.

Default: enable


Related Commands

dspnodalfd

Attributes

Access level: SUPER_GP

State: active

Log: log


Example

Install frame discard on the presence of the AAL5 IE.


SES_SJ.1.PXM.a > cnfnodalfd enable

SES_SJ.1.PXM.a >

Example

Disable the frame discard on the presence of the AAL5 IE.


Note Do not install frame discard on the presence of the AAL5 IE.


SES_SJ.1.PXM.a > cnfnodalfd disable

SES_SJ.1.PXM.a >

cnfpasswd

Configure Password—PXM1

Use the cnfpasswd command to change your own password. After the cnfpasswd command is entered, the switch prompts you to enter the new password. Then, you are prompted to reenter the password again.

Syntax

cnfpasswd

Syntax Description

None

Related Commands

adduser, cnfuser, dspusers

Attributes

Access level: ANYUSER

State: active

Log: no


Example

Change your password. After you enter the cnfpasswd command, the switch prompts you to enter a new password and reenter it again.

SES_SJ.1.PXM.a > cnfpasswd
Enter existing password: 
Enter new password: 
Re-enter new password:

cnfpri-routing

Configure Priority Routing—PXM1

Use the cnfpri-routing command to configure the number of bandwidth groups, the size of the first bandwidth group, and the increment between the successive groups. The cnfpri-routing command also configures the size of the routing event buffer as well as the delay before connections are routed during node startup.

The first bandwidth group contains connections for the bandwidth requirements that are below the start parameter. Each of the bandwidth groups contains connections for the bandwidth parameters that are more than the previous bandwidth group at or below the sum of the previous bandwidth group upper bound and the incr parameter. The last bandwidth group, which is specified by the grps parameter, contains all remaining connections that do not fit into any of the previous groups. Connections in the last bandwidth group, which require the most bandwidth, are routed as well as derouted ahead of connections in earlier bandwidth groups when the priority of the connections is the same.


Note The cnfpri-routing command fails if there are no connections pending to be rerouted.


For a long period of time, both time and delay parameters are recommended to be set at 1 sec and 5 sec, which helps with setting more effective connections.

Syntax

cnfpri-routing [-bwstart <start>] [-bwincr <incr>][-pribuf <time>]
[-nodebuf <delay>]

Syntax Description

-bwstart

Defines the upper bound of the first bandwidth group. The start parameter is the upper bound bandwidth of the first bandwidth group.

Range: 1-500000 cps

Default: 5000 cps

-bwincr

Defines the bandwidth difference between successive groups. The incr parameter is the increment between successive bandwidth groups.

Range: 1-500000 cps

Default: 1000 cps

-pribuf

Defines the waiting time between the first rerouting event and the actual rerouting event. The time parameter is the buffering time between the arrival of the first rerouting event and the actual rerouting event.

Range: 0-60 sec

Default: 0 sec

-nodebuf

Defines the waiting time after the first interface came up until the SPVC rerouting commences during the node rebuild. The delay parameter is the waiting time between the first interface and the commencement of the SPVC.

Range: 0-300 sec

Default: 0 sec


Related Commands

addcon, cnfcon, dspcon, dspcons, cnfpnportsig, dsppnportsig, dsppncon, dsppncon, dsppri-routing

Attributes

Access level: SUPER_GP

State: active

Log: log


Example

Configure the upper bound bandwidth to start at 500 cps, and the increment for the bandwidth groups is set to 100 cps. Then, set the buffering time to be 10 sec and the waiting time to be 50 sec.

SES_SJ.1.PXM.a > cnfpri-routing -bwstart 500 -bwincr 100

SES_SJ.1.PXM.a > cnfpri-routing -pribuf 10 -nodebuf 50

Example

Verify the priority routing results by entering the dsppri-routing command.

SES_SJ.1.PXM.a > dsppri-routing

Priority Routing Configuration
--------------------------------
Number of bandwidth groups: 50
Size of first bandwidth group (in cps): 500 
Increment between bandwidth groups (in cps): 100 
Routing event buffer size (in 0.1-seconds): 10 
Node startup routing delay (in 0.1-seconds): 50  

SES_SJ.1.PXM.a >

cnfoamsegep

Configure an OAM Segment Endpoint—PXM1

Use the cnfoamsegep command to define a specified port as a segment endpoint for F4 and F5 OAM flow. This command does not take effect for existing connections. It takes effect only for newly established calls. The cnfoamsegep command is used regardless of the state of the port.

Syntax

cnfoamsegep <portid> [yes | no]

Syntax Description

portid

Interface ID in the form of [shelf.]slot[:subslot].port[:subport].

yes

The specified port is configured as a segment endpoint, and is a segment endpoint for all connections on this port.

no

The specified port is not a segment endpoint.

Default: no


Related Commands

cnfconsegep, delconsegep, dspoamsegep

Attributes

Access level: GROUP1

State: active

Log: log


Example

Configure a port as a segment endpoint.

SES_SJ.1.PXM.a > cnfoamsegep 2.3 yes

SES_SJ.1.PXM.a > 

Example

Verify the results to enable the OAM segment endpoint by entering the dspoamsegep command for
port 2.3.

SES_SJ.1.PXM.a > dspoamsegep 2.3

           Port       OAM End Point
           2.3                 Yes

Example

Configure a port 2.3 so it is not a segment endpoint.

SES_SJ.1.PXM.a > cnfoamsegep 2.3 no
SES_SJ.1.PXM.a > 

Example

Verify the results to disable the OAM segment endpoint by entering the dspoamsegep command for
port 2.3.

SES_SJ.1.PXM.a > dspoamsegep 2.3

           Port       OAM End Point
           2.3                 No
SES_SJ.1.PXM.a > 

cnfpnctlvc

Configure PNNI Control VC—PXM1

Use the cnfpnctlvc command to configure bandwidth parameters for two types of control channels on a port. The types of control channels are service-specific connection-oriented protocol (SSCOP) or PNNI routing control channel (PNNI-RCC). You can enter this command for one VC type at a time.

Before using the cnfpnctlvc command, note the following issues:

You can enter the cnfpnctlvc command for one type of control VC at a time.

A control VC belongs to a special service type called virtual switch interface signaling (VSI-SIG).

The port must be down for you to enter the cnfpnctlvc command.


Note First, you may have to enter the dnppnport command.


The bandwidth used by control-type VCs (including ILMI, when enabled) adds to the bandwidth load on the port. Enter the dspload command to determine the load on port resources.

The VC for ILMI is also a control channel, but its bandwidth parameters are fixed. The following are the values for the parameters:

PCR: 1000 cps

SCR: 50 cps

MBS: 1024 cells

Syntax

cnfpnctlvc <portid> <vc-type> -pcr <pcr> -scr <scr> -mbs <mbs>

Syntax Description

portid

PNNI logical port, in the format [shelf.]slot[:subslot].port[:subport]. Using the short form where only the mandatory elements are appropriate, the portid has the format slot.port.

vc-type

The type of control VC to be configured. Enter pnnircc or sscop.

-pcr

Peak cell rate for the control VC.

Range: 1-5000 cps

Defaults:

If the vc-type is pnnircc, the default is 906 cps.

If the vc-type is sscop, the default is 1500 cps.

-scr

The sustained cell rate of the control VC.

Range: 1-5000

Defaults:

If the vc-type is pnnircc, the default is 453 cps.

If the vc-type is sscop, the default depends on the line rate.

-mbs

The maximum burst size of the control VC.

Range: 1-1000 cells

Defaults:

If the vc-type is pnnircc, the default is 171 cells.

If the vc-type is sscop, the default is 1000 cells.


Related Commands

dsppnctlvc

Attributes

Access level: GROUP1

State: active

Log: log


Example

Change the MBS of the PNNI-RCC VC on port 2.3 to 100 cells. The switch returns the error message that the port is still in service.

SES_SJ.1.PXM.a > cnfpnctlvc 2.3 sscop -mbs 100

ERROR: Port is not out-of-service 

Example

Down port 2.3 by entering the dnpnport command. Enter the cnfpnctlvc command to complete the task.

SES_SJ.1.PXM.a > dnpnport 2.3

SES_SJ.1.PXM.a > cnfpnctlvc 2.3 sscop -mbs 100
cnfpnctlvc Successful

Example

Verify the results by entering the dsppnctlvc command for port 2.3. One section of the display labeled provisioned shows the configured parameters, and the other section shows the operational VC parameters. The provisioned section reflects that you did not configure bandwidth parameters other than MBS, and the operational section shows the actual bandwidth parameters, which includes the MBS configuration.

Then, up port 2.3 by entering the uppnport command.

SES_SJ.1.PXM.a > dsppnctlvc 2.3


vc type = pnnircc 
service category : sig                       PCR :             906
SCR :              453                       MBS :             171 


vc type = sscop      Parameter = Provisioned
service category : sig                       PCR : Not Provisioned
SCR :  Not Provisioned                       MBS :             100 
SES_SJ.1.PXM.a > uppnport 2.3

SES_SJ.1.PXM.a > 

cnfpnni-election

Configure PNNI PGL Election—PXM1

Use the cnfpnni-election command to specify the priority of a node for the purpose of electing a peer group leader (PGL). By using this ranking, you can promote or prevent certain nodes for consideration for PGL election.

In a multi-peer group environment, each peer group can elect one PGL. The election takes place for every level of the hierarchy. For example, if three levels exist, three PGL elections occur. To ensure that a node cannot win the PGL election, you can assign 0 for the priority.

Every node in a peer group runs the election algorithm—with one exception: a node with the nontransit for PGL Election Flag set.

The following are the specifications that are needed for the cnfpnni-election command:

Number of seconds that the node delays advertising its choice of preferred PGL.

Number of seconds that the node waits to be declared the preferred PGL by unaminous agreement among its peer group members.

Number of seconds that the node waits before it restarts the election of a new PGL after connectivity to the current PGL is lost.

Syntax

cnfpnni-election <node-index> [-priority priority][-initTime init-time]
[-overrideDelay override-delay][-reelectionTime reelection-time]

Syntax Description

node-index

The node index to identify a PNNI logical node on a local switching system.

Range: 1-10

-priority

The PNNI leadership priority in a peer group.

Range: 1-20

Default: 0

-initTime

The amount of time, in seconds, this node will delay advertising its choice of preferred PGL after initializing operation and reaching the full state with at least one neighbor in the peer group.

Default: 15 sec

-overrideDelay

The amount of time, in seconds, a node will wait for itself to be declared the preferred PGL by unanimous agreement among its peers.

Default: 30 sec

-reelectionTime

The amount of time, in seconds, after losing connectivity to the current peer group leader that this node can wait before restarting the process of electing a new peer group leader.

Default: 15 sec


Related Commands

dsppnni-election

Attributes

Access level: SUPER_GP

State: active

Log: log


Example

Specify the following PGL election parameters:

The node index is 1.

The node election priority is 15.

The Init time is 10 sec.

The node waits 20 sec before proclaiming itself the peer group leader.

If the node looses connection with the peer group leader for 15 sec, it starts the election process.


SES_SJ.1.PXM.a > cnfpnni-election 1 -priority 15 -initTime 10 -overrideDelay 20
-reelectionTime 15
SES_SJ.1.PXM.a > dsppnni-election

node index: 1
   PGL state...... AwaitUnanimity     Init time(sec).......        10
   Priority.......             15     Override delay(sec)..        20
                                      Re-election time(sec)        15
   Pref PGL...............56:160:47.009181000000003071f813a1.003071f813a1.01
   PGL....................0:0:00.000000000000000000000000.000000000000.00
   Active parent node id..0:0:00.000000000000000000000000.000000000000.00



SES_SJ.1.PXM.a >

cnfpnni-intf

Configure PNNI Interface—PXM1

Use the cnfpnni-intf command to configure service category based administrative weight and aggregation token on a PNNI interface.

Aggregation Tokens

An aggregation token is a marker that indicates which uplinks, for example, links going out of the peer group, can be bundled or aggregated at the next logical level. If four links a, b, c, and d connect to peer groups X and Y, no aggregation exists for the links by default. The LGNs of these peer groups can have hypothetical names x02 and y02. They can be connected by a single logical link.

If you configure the aggregation token of link c as 1, x02 and y02 can have two logical links. One link corresponds to aggregation token 0, and the other link corresponds to aggregation token 1. Overall, an aggregation token is the number of links between a peer group leader and the lowest level of a PNNI hierarchy. The range for tokens is 1-32.

Administrative Weight

The administrative weight (AW) is a number that serves as a cost-based determinant of a route. Each port in a PNNI network has a default AW for the egress direction. Whether it uses the default AW or an AW you specify, PNNI adds all the AWs in a prospective route then determines whether the route is too expensive. For an SPVC, you can specify the maximum cost with the addcon command or the cnfcon command.

You can specify that all classes of service on the port have the same AW, or you can specify an AW for each service class on the port. If you specify the same AW for all, it overrides the default AW or the AW you might specify for individual services types.

The AW for a path is the sum, in both directions, of the individual weight of each link on the path.

Syntax

cnfpnni-intf <portid> [-aggregationToken token][-awcbr aw][-awrtvbr aw][-awnrtvbr aw]
[-awabr aw][-awubr aw] [-awall aw]

Syntax Description

portid

Port identifier of the logical port, as selected by the PNNI protocol entity for the specific interface. This value is meaningful only to the node associated with the physical port. In the form of [shelf.]slot[:subslot].port[:subport]

-aggregationToken

Specifies a 32-bit number that is used for link aggregation purposes.

Range: 0-2147483648

Default = 0 (when interface is added)

-awcbr

Specifies a 32-bit number that is used as administrative weight on this interface. This value is applied to all QoS classes if aw l is specified. Otherwise, this value is applied only to the single service class.

The maximum value is a 24-bit unsigned integer.

Range: 0-4,194,304

Default: 5040

-awrtvbr

Specify the administrative weight for real-time variable bit rate (rt-VBR) on this interface.

Range: 0-4,194,304

Default: 5040

-awnrtvbr

Specify the administrative weight for non-real-time variable bit rate (nrt-VBR) on this interface.

Range: 0-4,194,304

Default: 5040

-awabr

Specify the administrative weight for available bit rate (ABR) on this interface.

Range: 0-4,194,304

Default: 5040

-awubr

Specify the administrative weight for unspecified bit rate (UBR) on this interface. UBR connections can include SVC ping connections.

Range: 0-4,194,304

Default: 5040

-awall

Specify the administrative weight for all service types on this interface. If you use -awall, this aw becomes the AW for every service type on this port.

Range: 0-4,194,304

Default: 5040


Related Commands

dsppnni-intf

Attributes

Access level: SUPER_GP

State: active

Log: log


Example

Specify the following AWs on port 2.3:

The AW for real time variable bit rate is 11040.

The AW for non-real time variable bit rate is 20040.

The AW for unspecified bit rate is 1040.

SES_SJ.1.PXM.a > cnfpnni-intf 2.3 -awrtvbr 11040 -awnrtvbr 20040 -awubr 1040

Example

Verify the results by entering the dsppnni-intf command for port 2.3.

SES_SJ.1.PXM.a > dsppnni-intf 2.3

Physical port id: 2.3              Logical port id:     131840
   Aggr token..........         0     AW-NRTVBR...........     20040
   AW-CBR..............      5040     AW-ABR..............      5040
   AW-RTVBR............     11040     AW-UBR..............      1040



SES_SJ.1.PXM.a > 

cnfpnni-link-selection

Configure PNNI Link Selection—PXM1

Use the cnfpnni-link-selection command to specify which routing policies are used to select one of the parallel links that connect a neighboring PNNI node. Neighboring node in this case means a directly connected node. The cnfpnni-link-selection command applies only if parallel links exist between the specified port and neighboring nodes.


Note Link selection applies only to CBR and VBR connections. Preference is in the order of minaw, maxavcr, txspeedmax, and load-balance in case the configuration options on the links disagree. In case of equal value, the link is selected randomly.


For ABR and UBR connections, link is selected depend on (AvCR for ABR + AvCR for UBR)/(# of ABR connections + # of UBR connections).

Syntax

cnfpnni-link-selection <portid> [minaw | maxavcr | maxcr | loadbalance]

Syntax Description

portid

Port identifier. In the form of [shelf.]slot[:subslot].port[:subport]

minaw

Use this option to select the link with the least administrative weight in the egress direction.

Default: minaw policy

maxavcr

Use this option to select the link with the largest available cell rate (AvCR) in the egress direction.

The AvCR is the remaining bandwidth after the total utilized bandwidth is subtracted from the maximum cell rate (MaxCR).

The maxavcr policy works well for traffic that consistently requires a large amount of bandwidth.

maxcr

Use this option to select the link with the largest maximum cell rate (MaxCR) in the egress direction.

Typically, the MaxCR is the maximum speed of the line (or trunk). Therefore, if one link traverses an OC3 line and another link traverses a T3 line, the MaxCR policy dictates that PNNI select the OC3 line. Only when sufficient bandwidth does not exist on a line does the routing protocol switch to AvCR.

The maxcr policy works well for bursty traffic.

loadbalance

Use this option to select random selection of the link.

The load balance policy works well with links that have identical or very similar AW or bandwidth characteristics.


Related Commands

dsppnni-link-selection

Attributes

Access level: SUPER_GP

State: active

Log: log


Example

Specify the maximum available cell rate as the routing policy for the link with port 2.3.

SES_SJ.1.PXM.a > cnfpnni-link-selection 2.3 maxavcr

Example

Use the dsppnni-link-selection command to see the link selection policy on this port.


Note The dsppnni-link-selection command shows the logical port number for the physical port ID.


SES_SJ.1.PXM.a > dsppnni-link-selection 2.3

physical port id:             2.3     link selection: maxavcr
 logical port id:          131840



SES_SJ.1.PXM.a >

cnfpnni-mtu

Configure PNNI Maximum Transmit Unit—PXM1

Use the cnfpnni-mtu command to configure the maximum PNNI packet size in number of bytes. The cnfpnni-mtu command is useful for internet working compatibility, which you must match the maximum packet size of your peer group to a size that another peer group can handle. You can use the cnfpnni-mtu command in lab trials to test the effect of various packet sizes on the performance of the peer group.

Use the dsppnni-mtu command to display the PNNI packet size configuration.

Syntax

cnfpnni-mtu <mtu>

Syntax Description

mtu

Specifies the maximum transmit unit (MTU) in number of bytes.

Range: 2048-8192 bytes

Default: 2048


Related Commands

dsppnni-mtu

Attributes

Access level: SUPER_GP

State: active

Log: log


Example

Configure the maximum PNNI packet size to 3002 bytes.

SES_SJ.1.PXM.a > cnfpnni-mtu 3002

Example

Verify the results by entering the dsppnni-mtu command.

SES_SJ.1.PXM.a > dsppnni-mtu

max packet size : 3002



SES_SJ.1.PXM.a > 

cnfpnni-node

Configure PNNI Node—PXM1

Use the cnfpnni-node command to modify parameters for an existing PNNI node.

The node must be put into administratively disable status, before changing its ATM address, node ID, peer group ID, or hierarchical level.


Note When administratively disabling a PNNI logical node, all nodes at higher hierarchies must be administratively disabled first.


The following are the functions of the node-level cnfpnni-node command:

Modify the parameters of an existing logical node.

Enable or disable a node. This ability applies to

Parameters that require the node to be disabled before you can modify them (if you do not modify parameters that require a disabled node, you can modify one or more parameters with one execution of cnfpnni-node).

A situation where you created the node in the disabled state with addpnni-node.

The following are the modifications for the node configuration and state parameters:

ATM address—requires the node to be disabled

Level of the node within the hierarchy—requires the node to be disabled

Node ID—requires the node to be disabled

Peer group ID—requires the node to be disabled

Whether the node is the lowest node in the hierarchy

State of the node—enabled or disabled

Whether connections can transit this node

Whether or not the node is complex

Whether the node supports point-to-multipoint connections

The preceding parameters appear as optional parameters in the syntax. The required parameter for this command is the local node index. The local node index is a number in the range 1-10 that indicates the level of the logical node within a multi-peer hierarchy on the switch. If you do not know the value of this system-generated item, use the dsppnni-node command.

Disabling the Node for Parameters

For some of parameters, you must first disable the node. The following are the applicable parameters:

Level

ATM address

Node ID

Peer group ID

For these parameters, three executions of cnfpnni-node are necessary:

1. cnfpnni-node -enable false

2. cnfpnni-node (change parameters, including those that do not require a disabled node)

3. cnfpnni-node -enable true

Be sure to synchronize applicable changes (such a change in level) throughout the network and follow up with dsppnni-node or other applicable display commands.

Syntax

cnfpnni-node node-index [-atmAddr atm-address][-level level][-nodeId node-id]
[-pgId pg-id][-enable {true | false}] [-transitRestricted {on | off}] [-complexNode{on | off}] [-branchingRestricted {on | off}]

Syntax Description

node-index

The node index assigned to a PNNI logical node within the hierarchy of a multi-peer group. The lowest level is 1. Each new logical node added to the hierarchy automatically gets the next higher index number so you cannot configure the node index.

Range: 1-10

-atmAddr

Specifies the ATM address for this logical node. For you to change the ATM address, the node must be disabled.

If not specified, the default value is used, Once assigned, it can be changed only when the administrative status of the node is disabled.

Figure 3-1 shows the factory-set default.

-level

Specifies the level of the node within the PNNI hierarchy. The level of the node is the number of bits in the node ID (-nodeId parameter) or peer group ID (-pg-id parameter). For example, the default level of 56 means that the node ID is 56 bits long. If you specify a level of 48, the node ID has a length of 48 bits.The maximum number of levels you can configure on a switch is 10. This limit is meaningful in a multi-peer group only. Although the level can be any value within the 1-104 range, selecting an 8-bit boundary makes network planning and address management easier. For example, using 56 for a level is more expedient than using a level of 59.

Range: 1-104 bits

Default: 56 bits

-nodeId

Specifies the PNNI node identifier assigned to a PNNI node. The node ID consists of the PNNI hierarchy level (-level), followed by the length of the ATM address (addaddr length), followed by the ATM address (-atmAddr). As shown in Figure 3-1, node-id is a 22-byte, formatted hexadecimal string.

Note Before you change the node ID, you must first use the cnfpnni-node command one time with the parameter string -enable false to disable the node.

Figure 3-1 shows the factory-set default.

-pgId

Specifies that all members of a peer group have the same peer group identifier (pgID) and exist on the same level. (The level is either the existing number of bits or whatever you specify with -level level).

The default value of level is 56 (7 bytes), which specifies the length of -pgId to 7 bytes. However, the maximum length of -pgId is 14 bytes, so display commands always show -pgId as 14 bytes with trailing zeros filling the undefined fields. If you increase the value of level, you change the length, and therefore the value, of -pgId, but it will always be displayed as 14 bytes.

Before you change the value of pg-id, disable the node by entering cnfpnni-node -enable false.

This is a 14-byte, formatted hexadecimal string.

Figure 3-1 shows the factory-set default

-enable

Specifies the administrative status of the PNNI node. Before you change a node ATM address, node ID, peer group ID, or hierarchical level, the node must be disabled.

true: Enable the node.

false: Disable the node.

Default: true

-transitRestricted

Specifies whether connections can transit this node. You can disallow via connections for security reasons, to minimize traffic supported by either a low bandwidth node or a highly critical node, and so on.

on: This node allows via connections.

off: Via connections cannot transit this node.

Default: off

-complexNode

Specifies whether this node is a complex node. The lowest-level node cannot be a complex node.

on: This node is a complex node.

off: This node is not a complex node.

Default: off

-branchingRestricted

Specifies whether the PNNI node allows point-to-multipoint branches.

on: This node does not allow point-to-multipoint branches.

off: This node allows point-to-multipoint branches.

Default: on



Caution Cisco factory-set defaults for address prefixes and the peer group ID share field values with the ATM address. If you change the peer group ID, you should change the corresponding fields in the ATM address and node identifier. See Figure 3-1 for the mapping between these addresses.

Figure 3-1 Cisco Factory-shipped Defaults for PNNI Peer Group Identifier, PNNI Summary Address, ATM Address, and PNNI Node Identifier

Related Commands

addpnni-node, delpnni-node, dsppnni-node

Attributes

Access level: SUPER_GP

State: active

Log: log


Example

Specifies the PNNI configuration values for a node that already exists on the network. The following are the PNNI node configurations:

The PNNI hierarchy level is 56.

The node ATM address is 47.0091 8100000000309409f1f1.00309409f1f1.01.

The node PNNI identifier is 56:160:47.00918100000000309409f1f1.00309409f1f1.01.

The node PNNI group identifier is 56:47.009181.0000.00. The length specified by the hierarchy level is 56 (8 bytes) the following 12 zeros are fill.

The node is at the lowest level of the network PNNI hierarchy.

The node is enabled.

The node does not permit traffic to cross it on the way to other nodes.

The node is not a complex node.

The node permits branching.

SES_SJ.1.PXM.a > cnfpnni-node 1 -level 56 -nodeId 56:160:47.009181000000003071f813a1.003071f813a1.01
-atmAddr 47.009181000000003071f813a1.003071f813a1.01 -pgId 56:47.00.9181.0000.0000.0000.0000.00 -lowest true 
-enable true -transitRestricted off -complexNode off -branchingRestricted off 

Example

Use dsppnni-node to display the PNNI configuration values.

SES_SJ.1.PXM.a > dsppnni-node

node index: 1                      node name: SES_SJ         
   Level...............        56     Lowest..............      true
   Restricted transit..       off     Complex node........       off
   Branching restricted        on
   Admin status........        up     Operational status..        up
   Non-transit for PGL election..       off
   Node id...............56:160:47.009181000000003071f813a1.003071f813a1.01
   ATM address...........47.009181000000003071f813a1.003071f813a1.01
   Peer group id.........56:47.00.9181.0000.0000.0000.0000.00



SES_SJ.1.PXM.a >

cnfpnni-pkttrace

Configure PNNI Packet Trace—PXM1

The cnfpnni-pkttrace command applies to debugging. It causes the switch to check the PNNI packets transmitted and received at each peer. For example, if an interface is not receiving user-traffic, you can enter dsppnni-pktrace to display packet information that can help you find the level and type of blockage.

The cnfpnni-pkttrace command specifies the trace command examines the contents of PNNI packets exchanged between two neighboring nodes. A PNNI packet consists of a Hello packet and the topology information packets.


Note Executing the cnfpnni-pkttrace command can significantly increase operational overhead; therefore, degrading network performance. You should consider executing this command while the node carries little or no live traffic. If you enter cnfpnni-pkttrace while live traffic is present, you can consider tracing the packets for one direction at a time (transmit or receive).


If you plan to use the optional -portId parameter but do not have the logical format of the port ID, use the dsppnport command.

Syntax

cnfpnni-pkttrace {tx { on | off }|rx { on | off } [ node-index] [ -portId port-id |-svcIndex svc-index]]

Syntax Description

tx

Specifies whether the switch traces transmitted packets.

on: Trace the transmitted packets

off: Do not trace the transmitted packets

Default: (no default)

rx

Specifies whether the switch traces received packets.

on: Trace the received packets

off: Do not trace the received packets

Default: (no default)

node-index

The node index indicates the relative level of the logical node within a multi-peer group on the switch.

Range: 1-10

-portId

The port ID in this instance has the format of the logical ID number. The format is a 32-bit encoded number in the range 1-2147483648. If you do not have the port ID in this form, use the dsppnport command and provide the common portID format of slot[:subslot].port[:subport}. The output of the dsppnport command shows the logical number for the port ID. Use this value for the -portID parameter.

-svcIndex

PNNI uses the SVC index as a reference to the SVC-based, logical, horizontal link. This parameter is meaningful only if you specify node-index.

Default: none


Related Commands

dsppnni-pkttrace, dsppnport, dsppnports

Attributes

Access level: SERVICE_GP

State: active

Log: log


Example

Configure the following contents of PNNI Hello packets:

The transmit packets are traced.

The packet trace occurs at node index of 1 (the default for cnfpnni-pkttrace and therefore omitted).

The packet trace takes place on the port identifier of 17504.

SES_SJ.1.PXM.a > cnfpnni-pkttrace tx 17504 
PNNI/tx_packet on port 17504 at level 56
> 01:00010064  01010100  000038a0  47009181  00000000  309409f3  b8003094
> 02:09f3b801  47009181  00000000  309409f3  b8003094  09f3b801  38470091
> 03:81000000  00000000  000038a0  47009181  00000000  001a531c  2a00001a

Example

Verify the trace by entering the dsppnni-pkttrace command.

SES_SJ.1.PXM.a > dsppnni-pkttrace tx -portId 17504

Node Index :1   Port id:        17504   Tx Pkt Trace on

SES_SJ.1.PXM.a >

cnfpnni-routing-policy

Configure the PNNI Routing Policy—PXM1

Use the cnfpnni-routing-policy command to specify which routing policy values are used during UNI call setup. Routing policies control PNNI routing for your network.

The following specifications are for the cnfpnni-routing-policy command:

Generating background routing tables

Load balancing

On-demand routing—applies to crankback or a situation where the node must route a call to a destination for which no route exists in the pre-computed routing tables

The two dynamic routing protocols are shortest path and on-demand routing.

Background Routing Tables

The background routing tables contain all routes within the peer group. The routes are calculated from information in the internal data base (IDB). When a topology change affects usable routes within the peer group, a PNNI topology state packet carries the formation to each node so it can update its IDB. The background routing tables are updated to reflect the change in routing parameters.

The following are generated (or pre-computed) to support routing based on the shortest path:

The AW background routing table stores the AWs for all routes.

The cell transfer delay (CTD) background routing table stores the CTD data for known routes.

The cell delay variation (CDV) background routing table stores the CDV data for known routes.

On-demand routing is used if any of the following occur:

All pre-computed routing tables are disabled.

A route does not appear in the precomputed routing tables.

Crankback is enabled within a designated transit list (DTL).


Caution Poor routing policies can cripple or even crash a network. You should not change routing policies on a deployed network unless you have carefully planned the changes and know how the changes can affect the network.

Syntax

cnfpnni-routing-policy [-sptEpsilon epsilon][-sptHolddown holddown][-bnPathHolddown bn-path-holddown] [-loadBalance {random | maxbw}] [-onDemand {firstfit | bestfit}]
[-awBgTable {on | off}] [-ctdBgTable {on | off}] [-cdvBgTable {on |off}]

Syntax Description

-sptEpsilon

The shortest path (SPT) epsilon you supply specifies a tolerance in the form of a percent that can influence which paths qualify as equal-cost during route calculation. A higher tolerance results in a broader range of path cost-values that can qualify as equal-cost. If two paths have very similar administrative weights (AWs), a large enough tolerance eliminates equal-cost as a routing factor because the routing algorithm regards the costs as equal.

The range of 0-20 for this parameter comes from the ATM Forum PNNI specification. However, the percent of tolerance that the numbers dictate is determined by individual vendors.

Cisco currently maps the following percentages for the Cisco SES PNNI Controller switch:

0: the total AWs along both directions of the route must be identical.

1-2: the total AWs along both directions of the route must be within 1.5%.

3-4: the total AWs along both directions of the route must be within 3.0%.

5-9: the total AWs along both directions of the route must be within 6.0%.

10-15: the total AWs along both directions of the route must be within 12.5%.

16-20: the total AWs along both directions of the route must be within 25.0%.

Range: 0-20

Default: 0 (exact match required)

-sptHolddown

The interval between two consecutive calculations for generating routing tables. If a network is stable, it may not be necessary to generate routing tables 10 times per second. In such a case, you can increase the value to reclaim CPU time needlessly used to update unchanging routing tables.

Units: 100 ms

Range: 1-600 (0.1-60 seconds)

Default: 1

-bnPathHolddown

The minimum interval between consecutive calculations of routing tables for border nodes. For a stable network, generating the routing tables 10 times a second can be unnecessary. You can increase the interval to save the CPU time spent on updating routing tables that are not changing.

Units: 100 ms

Range: 2-600 (0.2-60 sec)

Default: 2

-loadBalance

The PNNI routing protocol relies on the load balance policy when it determines that the routes to a destination have equal cost. (PNNI determines routes to be identical according to the metrics in the AW, CDV, or CTD routing table.)

Note The SPT epsilon value is a factor when PNNI calculates cost.

The choice for load balancing is random or maxbw. Enter the entire word.

With random load balancing, PNNI randomly chooses between the equal cost routes. This rule requires less computational overhead.

With maxbw load balancing, PNNI selects the route with more available bandwidth when it chooses between equal cost routes. This rule has more overhead due to ongoing comparison of available bandwidth on the routes.

Default: no default

-onDemand

On-demand routing applies to crankback or a situation where the node must route a call to a destination for which no route exists in the pre-computed routing tables. The on-demand policy is either firstfit and bestfit.

With firstfit (the default), PNNI selects the first route to the destination. This approach minimizes search time but may not result in the best route.

With bestfit, PNNI selects a route based on the following:

The route with the lowest cost.

Link verification.

Path constraint checks.

Avoidance of blocked nodes and links.

Checking limits in the designated transit list (DTL).

With bestfit, PNNI selects the optimum route but entails greater computing overhead. The search-time depends on the density and complexity of the network.

Default: firstfit

-awBgTable

Enable or disable the background routing table for AW. The following are the options:

on: The background routing table of AW is enabled.

off: The background routing table of AW is disabled.

Default: on

-ctdBgTable

Enable or disable the background routing table of CTD. The CTD parameter is the interval between a cell exiting the source PNNI node and entering the destination PNNI node. The following options are

on: The background routing table of CTD is enabled.

off: The background routing table of CTD is disabled.

Default: on

-cdvBgTable

Enable or disable the background routing table of CDV. The CDV parameter is a component of cell transfer delay, and is a quality of service (QoS) delay parameter associated with CBR and VBR service. Cell Delay Variation is the variation of delay between cells, measured peak to peak. The following options are

on: The background routing table of CDV is enabled.

off: The background routing table of CDV is disabled.

Default: on


Related Commands

dsppnni-routing-policy

Attributes

Access level: SUPER_GP

State: active

Log: log


Example

Enter the cnfpnni-routing-policy command to specify the following routing policy:

Only paths with identical values qualify as equal-cost paths.

The routing tables are generated every 0.1 seconds.

The load balancing is purely random.

On-demand routing selects to the optimal route.

The background routing table for AW is enabled.

The background routing table for cell transfer delay is enabled.

The background routing table for cell delay variation is enabled.

SES_SJ.1.PXM.a > cnfpnni-routing-policy -sptEpsilon 15 -sptHolddown 100 -bnPathHolddown 
100 -loadBalance random -onDemand bestfit

Example

Verify the settings by entering the dsppnni-routing-policy command.

SES_SJ.1.PXM.a > dsppnni-routing-policy

   SPT epsilon.........        15     Load balance........    random
   SPT holddown time...       100     On demand routing...  best fit
   SPT path holddown time     100     AW Background Table         on
   CTD Background Table        on     CDV Background Table        on 
SES_SJ.1.PXM.a > 

cnfpnni-scope-map

Configure PNNI Scope Map—PXM1

Use the cnfpnni-scope-map command to configure the scope map table. The cnfpnni-scope-map command specifies how UNI 4.0 address scope values are mapped to PNNI hierarchal levels. The parameters are stored in the scope map table.

Syntax

cnfpnni-scope-map <scope> <level>

Syntax Description

scope

Specifies the UNI 4.0 address scope.

The following ranges are

1: LocalNetwork

2: LocalNetworkPlusOne

3: LocalNetworkPlusTwo

4: SiteMinusOne

5: IntraSite

6: SitePlusOne

7: OrganizationMinusOne

8: IntraOrganization

9: OrganizationPlusOne

10: CommunityMinusOne

11: IntraCommunity

12: CommunityPlusOne

13: Regional

14: InterRegional

15: Global

Default: none

level

Specifies the PNNI level where the UNI 4.0 address scope is mapped.

Range: 1-104

Default: 56


Related Commands

dsppnni-scope-map

Attributes

Access level: SUPER_GP

State: active

Log: log


Example

Configure the scope map table for the following:

The variable scope is 12.

The variable level is 100.

The values map to UNI 4.0 scope 12 to the PNNI hierarchical level 56.

SES_SJ.1.PXM.a > cnfpnni-scope-map 12 100

Example

Verify the results by entering the dsppnni-scope-map command.

SES_SJ.1.PXM.a > dsppnni-scope-map



UNI  Scope                Pnni Routing Level
----------------------    ------------------
LocalNetwork(1)                           56
LocalNetworkPlusOne(2)                    56
LocalNetworkPlusTwo(3)                    56
SiteMinusOne(4)                           40
IntraSite(5)                              40
SitePlusOne(6)                            32
OrganizationMinusOne(7)                   32
IntraOrganization(8)                      24
OrganizationPlusOne(9)                    24
CommunityMinusOne(10)                     24
IntraCommunity(11)                         8
CommunityPlusOne(12)                     100
Regional(13)                               0
InterRegional(14)                          0
Global(15)                                 0

SES_SJ.1.PXM.a > 

cnfpnni-svcc-rcc-timer

Configure PNNI SVCC RCC Timer—PXM1

Use the cnfpnni-svcc-rcc-timer command to define the initial PNNI SVCC-based variables for a specified PNNI logical node in this switching system.

Syntax

cnfpnni-svcc-rcc-timer <node-index> [-initTime init-time] [-retryTime retry-time] [-callingIntegrityTime calling-integrity-time] [-calledIntegrityTime called-integrity-time]

Syntax Description

node-index

The node index indicates the relative level of the logical node within a multi-peer group on the switch.

Range: 1-10

-initTime

The number of seconds this node waits before it advertises its choice of preferred SVCC to a neighbor with a numerically lower ATM address. This node does so after determining that such an SVCC should be established.

Range: 1-10 sec

Default: 4

-retryTime

The number of seconds this node waits before it attempts to re-establish an apparently necessary and viable SVCC-based RCC that was unexpectedly torn down.

Range: 10-60 sec

Default: 30

-callingIntegrityTime

The number of seconds the node waits while it attempts to set up an SVCC as the calling party. If the SVCC is not fully established within this time period, the node tears down the connection.

Range: 5-300

Default: 35

-calledIntegrityTime

The number of seconds the node waits while it attempts to set up an SVCC as the called party. If the SVCC is not fully established within this time period, the node tears down the connection.

Range: 10-300

Default: 50


Related Commands

dsppnni-svcc-rcc-timer

Attributes

Access level: SUPER_GP

State: active

Log: log


Example

Configure the PNNI SVCC-based variables for node index 1 by entering the cnfpnni-svcc-rcc-timer command.

SES_SJ.1.PXM.a > cnfpnni-svcc-rcc-timer 1 -initTime 10 -retryTime 60 -callingIntegrityTime 
35 -calledIntegrityTime 50

Example

Verify the results by entering the dsppnni-svcc-rcc-timer command.

SES_SJ.1.PXM.a > dsppnni-svcc-rcc-timer

node index: 1
   Init time...........        10     Retry time..........        60
   Calling party integrity time...        35
   Called party integrity time....        50



SES_SJ.1.PXM.a > 

cnfpnni-timer

Configure PNNI Timer—PXM1

Use the cnfpnni-timer command to define the initial PNNI timer values and significant change thresholds of a network node. You must carefully plan the use of this command because modifying a timer can significantly change the efficiency of the network.

Syntax

cnfpnni-timer <node-index> [-ptseHolddown ptse-holddown][-helloHolddown hello-holddown] [-helloInterval hello-interval]
[-helloInactivity-factor hello-inactivity-factor]
[-horizontal-link-inactivity-time horizontal-link-inactivity-time]
[-ptseRefreshInterval ptse-refresh-interval]
[-ptseLifetimeFactor ptse-lifetime-factor]
[-retransmitInterval retransmit-interval]
[-ptseDelayedAckInterval ptse-delayed-ack-interval][-avcrPm avcr-pm][-avcrMt avcr-mt]
[-cdvPm cdv-pm][-ctdPm ctd-pm]

Syntax Description

node-index

The node index indicates the relative level of the logical node within a multi-peer group on the switch.

Range: 1-101

-ptseHolddown

The holddown value is the time the switch waits before it broadcasts PTSEs. The increments are tenths of a second. For example, -ptseHolddown 1 means 0.1 second, -ptseHolddown 10 means 1 second, and so forth.

Range: 0.1-1000

Default: 10 (1 sec)

-helloHolddown

Specifies he initial value for the Hello hold down timer that the node uses to limit the rate at which it sends Hellos.

Units: 100 ms. 1 = 0.1sec

Range: 0.1-1000

Default: 10 (1 sec)

-helloInterval

Specifies the initial value for the Hello timer in seconds. The value limits the rate at which the node sends Hellos.

Range: 1-300 sec

Default: 15 sec

-helloInactivity-factor

The product of the hello-inactivity-factor and the peer neighbor hello-interval is the maximum time (in sec) that the neighbor is considered alive after the last reception of a Hello packet.

Range: 1-50 sec

Default: 5 sec

-horizontal-link-inactvity-time

Inactivity time, in seconds, on a horizontal link between two-logical group nodes.

Default: 120 sec

-ptseRefreshInterval

Specifies the initial time allowed for the PTSE to reoriginate specified in seconds.

Range: 30-1800 sec

Default: 1800 sec

-ptseLifetimeFactor

Specifies the value for the lifetime multiplier, expressed as a percentage. The product of it and the ptse-refresh-interval is the initial value of the remaining lifetime of a self-created PTSE.

Range: 101-1000%

Default: 200

-retransmitInterval

Specifies the period between retransmissions of unacknowledged DS, PTSE request, and PTSP specified in seconds.

Range: 5-60 sec

Default: 5 sec

-ptseDelayedAckInterval

Specifies the minimum interval between transmissions of delayed PTSE acknowledgment packets.

Units: 100 ms. 1 = 0.1 sec

Range: 1-10

Default: 10 (1 sec)

-avcrPm

Specifies the proportional multiplier used in the algorithms to determine significant change for available cell rate (AvCR) parameters.

avcr-pm is expressed as a percentage.

Range: 1-99%

Default: 50%

-avcrMt

Specifies the minimum threshold used in the algorithms that determine significant change for available cell rate (AvCR) parameters, which are expressed as a percentage. You can change this value to minimize the overhead created by advertisements triggered by AVCR changes.

avcr-mt is expressed as a percentage.

Range: 1-99%

Default: 3%

-cdvPm

Specifies the proportional multiplier used in the algorithms to determine significant change for cell delay variation (CDV) parameters that are expressed as a percentage, the variation of delay between cells, and measured peak to peak. You can change this value to minimize the overhead created by advertisements triggered by CDV changes.

cdv-pm is expressed as a percentage.

Range: 1-99%

Default: 25%

-ctdPm

Specifies the proportional multiplier used in the algorithms to determine significant change for cell transfer delay (CTD) parameters that are expressed as a percentage. You can change this value to minimize the overhead created by advertisements triggered by changes to CTD values.

ctd-pm is expressed as a percentage.

Range: 1-99%

Default: 50%


Related Commands

dsppnni-timer

Attributes

Access level: SUPER_GP

State: active

Log: log


Example

Enter the cnfpnni-timer command that is set with the following parameter values:

The hello should be hold down for 1.0 sec.

The PTSE should be hold down for 1.0 sec.

The node Hello timer is 15 seconds.

The node hello-inactivity-factor is 5 seconds.

The node recreates PTSEs every 1800 seconds (30 min).

The node evaluates the initial PTSE lifetime by multiplying the ptse-refresh-interval (1800 sec) by 200.

The node retransmits every 5 sec.

If the node broadcasts a PTSE and the PTSE is not acknowledged, the node waits 1 second to rebroadcast its PTSE.

The node multiplies an algorithm by 3% to determine the value that qualifies as a significant change for AvCR parameters.

The node multiplies an algorithm by 50% to determine the value that qualifies as the minimum threshold for significant change of AvCR parameters.

The node multiplies an algorithm by 25% to determine the value that qualifies as a significant change for CDV parameters.

The node multiplies an algorithm by 50% to determine the value that qualifies as a significant change for CTD parameters.

You can confirm your settings with the related command dsppnni-timer.

SSES_SJ.1.PXM.a > cnfpnni-timer 1 -ptseHolddown 10 -helloHolddown 10 -helloInterval 15 
-helloInactivity-factor 5 -horizontalLinkInactivityTime 120 -ptseRefreshInterval 1800 
-ptseLifetimeFactor 200 -retransmitInterval 50 -ptseDelayedAckInterval 10 -avcrPm 50 
-avcrMt 3 -cdvPm 25 -ctdPm 50

Verify the settings by entering the dsppnni-timer command.

SES_SJ.1.PXM.a > dsppnni-timer 1

node index: 1
   Hello holddown(100ms)...        10     PTSE holddown(100ms)...        10
   Hello int(sec)..........        15     PTSE refresh int(sec)..      1800
   Hello inactivity factor.         5     PTSE lifetime factor...       200
   Retransmit int(sec).....         5
   AvCR proportional PM....        50     CDV PM multiplier......        25
   AvCR minimum threshold..         3     CTD PM multiplier......        50
   Peer delayed ack int(100ms)...................        10
   Logical horizontal link inactivity time(sec)..       120



SES_SJ.1.PXM.a > 

cnfpnportacc

Configure PNNI Port Access—PXM1

Use the cnfpnportacc command to associate an ATM filter set with a port (after you create the filter set with the addfltset command). You must specify at least one filter set.


Note To view the access filter group configuration for a port, enter the dsppnport command.


Syntax

cnfpnportacc <portid> [-in {in-filter-name}] [-out {out-filter-name}]

Syntax Description

portid

Interface ID in the form of [shelf.]slot[:subslot].port[:subport].

-in

Specifies the filter set applicable to SETUP messages incoming to the port.

-out

Specifies the filter set applicable to SETUP messages outgoing from the port.


Related Commands

dsppnport

Attributes

Access level: GROUP1

State: active

Log: log


Example

Consider a filter "firstfilter" created via the addfltset command.

To attach it to port 4.1 for filtering incoming setup messages, the following command will be used:


pnnises1.1.PXM.a > cnfpnportacc 4.1 -in firstfilter

cnfpnportcac

Configure PNNI Port CAC—PXM1

Use the cnfpnportcac command to set CAC policy parameters for a specified port. The new configuration applies to new incoming calls while existing calls remain intact. This command is used regardless of the state of the port. At least one keyword must be specified.

The bookfactor is interpreted as percentage utilization, and applied in CAC. The booking factor is not applied to AvCR advertised by the switch to the controller. When the default of maxbw and minbw is used for all service categories, the common AvCR is to be advertised for all the service categories. The booking factor is applied to AvCR advertised by the PNNI to its neighbor nodes.

Syntax

cnfpnportcac <portid> <service_category> [-bookfactor {utilization-factor}]
[-maxbw {max-bw-percent}][-minbw {min-bw-percent}] [-maxvc {max-vc-percent}]
[-minvc {min-vc-percent}][-maxvcbw {max-vc-bw}]

Syntax Description

portid

Interface ID in the form of [shelf.]slot[:subslot].port[:subport].

service_category

ATM 4.0 service category. Enter one of the following options:

cbr = constant bit rate

rtvbr = real time variable bit rate

nrtvbr = non-real time variable bit rate

ubr = unspecified bit rate

abr = available bit rate

-bookfactor

Service Category Utilization Factor (SCUF) for a service category on this port, in the range 1 through 200.

Range: 1-200

Default: 100

-maxbw

Maximum percentage of guaranteed bandwidth for a service category on this port.

Range: 0-100.0000

Default: 100.000

-minbw

Minimum percentage guaranteed bandwidth for a service category on this port.

Range: 0-100.0000

Default: 0

-maxvc

Maximum percentage of VCs for a service category on this port.

Range: 0-100

Default: 100

-minvc

Minimum percentage of VCs for a service category on this port.

Range: 0-100

Default: 0

-maxvcbw

Maximum bandwidth, as specified by the PCR, allowed for a VC in a service category on this port.

Range: 0 through the maximum possible line rate (in cps)

Default: 0 (disabled)


Related Commands

dsppnportcac

Attributes

Access level: GROUP1

State: active

Log: log


Example

Configure the PNNI port CAC with port 2.3 and the service category.

spirita.1.PXM.a > cnfpnportcac 2.3 nrtvbr

Example

Verify the results by entering the dsppnportcac command for port 2.3.

SES_SJ.1.PXM.a > dsppnportcac 2.3

                  cbr:       rt-vbr:       nrt-vbr:          ubr:         abr:          
sig:
bookFactor:       100%          100%           100%          100%         100%          
100%
maxBw:       100.0000%     100.0000%      100.0000%     100.0000%    100.0000%     
100.0000%
minBw:         0.0000%       0.0000%        0.0000%       0.0000%      0.0000%       
0.0000%
maxVc:            100%          100%           100%          100%         100%          
100%
minVc:              0%            0%             0%            0%           0%            
1%
maxVcBw:            0             0              0             0            0             
0

SES_SJ.1.PXM.a > 

cnfpnportcc

Configure PNNI Port Call Control—PXM1

Use the cnfpnportcc command to set call control parameters for a specified port. At least one keyword must be specified. This command is used regardless of the state of the port. The new configuration applies to new incoming calls while existing calls remain intact.

The following are the applications for the cnfpnportcc command:

Specify maximum root and leaf connections for point-to-multipoint connections.

Specify whether all SVCs or all SPVCs are blocked on the port.

Configures the port to reject or reenable all nonpersistent slave establishments.

You can enter cnfpnportcc command whether the port is active or in the provisioning state.


Note The current release does not support point-to-multipoint calls.


Syntax

cnfpnportcc <portid>[-maxp2mproot {max-p2mp-root}][-maxp2mpleaf {max-p2mp-leaf}]
[-svcblock {yes | no}][-spvcblock {yes | no}] [-nonpersblock {yes | no}]

Syntax Description

portid

Specifies the port ID for the modified configuration. Interface ID in the form of [shelf.]slot[:subslot].port[:subport].

-maxp2mproot

Maximum number of root VCs on this port.

Default: 1000

-maxp2mpleaf

Maximum number of leaf VCs on this port.

Default: 4095

-svcblock

Enable or disable SVC blocking on the port. Enter yes or no.

yes: no new call setups are accepted.

no: new call setups are accepted.

Default: no

-spvcblock

Enable or disable SPVC blocking on the port. Enter yes or no.

yes: attempts to add an SPVC through addcon or Cisco WAN Manager fails. The resulting error message is ERR: SPVC blocking is enabled on this interface.

no: adds SPVCs through addcon or Cisco WAN Manager.

Default: no

-nonpersblock

Specifies the flag that indicates if nonpersistent slave blocking is enabled or disabled. The -nonpersblock option ensures that no nonpersistent slaves are allowed on the port after the port is configured entering the cnfpnportcc command to block nonpersistent slaves.

Enter either yes or no.

Default: no


Related Commands

dsppnportcc

Attributes

Access level: GROUP1

State: active

Log: log


Example

Configure the applicable PNNI port call control parameters.

SES_SJ.1.PXM.a > cnfpnportcc 2.3 -maxp2mproot 900 -maxp2mpleaf 2000 -svcblock yes 
-spvcblock yes -nonpersblock yes

Example

Verify the results by entering the dsppnportcc command for port 2.3.

SES_SJ.1.PXM.a > dsppnportcc 2.3
maxP2mpRoot:              900
maxP2mpLeaf:             2000
svc blocking option:        yes
spvc blocking option:       yes
nonpers blocking option:    yes

SES_SJ.1.PXM.a >

cnfpnportloscallrel

Configure PNNI Port LOS Call Release—PXM1

Use the cnfpnportloscallrel command to shut off the standard delay for rerouting calls on a port when the system detects loss of signal (LOS) on a port.

When the system detects LOS on an NNI link, the switch does not immediately tear down the calls on the link—in case the break is momentary. By default, the system waits for the SSCOP no-response and T309 timers to time out before it releases calls on the broken link. The default values for these timers are 30 sec and 10 sec. The system-level assumption, the default for the cnfpnportloscallrel command, is to retain all the calls for a temporary loss of connectivity, but this can also have the effect of delaying the rerouting of connections. The cnfpnportloscallrel command directs the system to reroute calls without delay on a particular port.

Syntax

cnfpnportloscallrel < portid> [ yes | no]

Syntax Description

portid

Interface ID in the form of [shelf.]slot[:subslot].port[:subport].

yes | no

Enables or disables release of SVCs/SPVCs after a physical LOS.

Default: yes


Related Commands

dsppnportloscallrel

Attributes

Access level: SUPER_GP

State: active

Log: log


Example

Enable the release of SVCs/SPVCs after a physical LOS for port 2.3.

SES_SJ.1.PXM.a > cnfpnportloscallrel 2.3 yes

SES_SJ.1.PXM.a >

Example

Verify the results by entering the dsppnportloscallrel command for port 2.3.

SES_SJ.1.PXM.a > dsppnportloscallrel 2.3
Call release on Los :enabled 

SES_SJ.1.PXM.a >

Example

Disable the release of SVCs/SPVCs after a physical LOS for port 2.3.

SES_SJ.1.PXM.a > cnfpnportloscallrel 2.3 no
SES_SJ.1.PXM.a >

Example

Verify the results by entering the dsppnportloscallrel command for port 2.3.

SES_SJ.1.PXM.a > dsppnportloscallrel 2.3
Call release on Los :disabled 

SES_SJ.1.PXM.a >

cnfpnportncci

Configure Port Network Call Correlation Identifier—PXM1

Use the cnfpnportncci command to configures an action for a call correlation identifier. The cnfpnportncci command determines the action that PNNI takes on a call correlation identifier.

The following are the responses to the call correlation identifier:

Forward the identifier.

Discard the identifier.

Assign a new identifier.


Note The cnfpnportncci command applies only to UNI 4.0 and AINI. It does not apply to UNI 3.x, IISP, and PNNI.


Syntax

cnfpnportncci <portid> [-action {forward |discard |assign}]

Syntax Description

portid

Identifies a PNNI physical port. The format is slot:subslot.port:subport.

-action

The action that the controller takes on the network call correlation identifier.

The following choices are

forward

discard

assign

Default: forward


Related Commands

dsppnportncci

Attributes

Access level: GROUP1

State: active

Log: log


Example

Configure the network call correlation identifier for port 2.3.

SES_SJ.1.PXM.a > cnfpnportncci 2.3 -action forward

Verify the results by entering the dsppnportncci command for port 2.3.

SES_SJ.1.PXM.a > dsppnportncci 2.3

NCCI action: forward
SES_SJ.1.PXM.a >

cnfpnportrange

Configure PNNI Port Range—PXM1

Use the cnfpnportrange command to set VPI values for SVCC and SVPC on a specified port. This command is used only when a port is administratively down (by dnpnport). At least one keyword must be specified. The maxsvccvpi is defaulted to 4095 to allow a maximum negotiation advantage during ILMI auto-configuration. Moreover, this value is limited by the high VPI value given by the switch irrespective of the port type (UNI/NNI).

Syntax

cnfpnportrange <portid> [-minsvccvpi <min-svcc-vpi>][-maxsvccvpi <max-svcc-vpi>]
[-minsvccvci <min-svcc-vci>][-maxsvccvci <max-svcc-vci>]
[-minsvpcvpi <min-svpc-vpi>][-maxsvpcvpi <max-svpc-vpi>]

Syntax Description

portid

Interface ID in the form of [shelf.]slot[:subslot].port[:subport].

-minsvccvpi

Minimum VPI value for SVCC.

Range: 0-4095

Default: 0

-maxsvccvpi

Maximum VPI value for SVCC.

Range: 0-4095

Default: 4095

-minsvccvci

Minimum VCI value for SVCC.

Range: 0-65535

Default: 35

-maxsvccvci

Maximum VCI value for SVCC.

Range: 32-65535

Default: 65535

-minsvpcvpi

Minimum VPI value for SVPC.

Range: 1-4095

Default: 1

-maxsvpcvpi

Maximum VPI value for SVPC.

Range: 1-4095

Default: 4095


Related Commands

dsppnportrange

Attributes

Access level: GROUP1

State: active

Log: log


Example

Configure the PNNI port range with the applicable VPI values for port 2.3.

SES_SJ.1.PXM.a > cnfpnportrange 2.3 -minsvccvpi 0 -maxsvccvpi 4095 -minsvccvci 35 
-maxsvccvci 65535 -minsvpcvpi 1 -maxsvpcvpi 4095

Example

Verify the results by entering the dsppnportrange command for port 2.3.

SES_SJ.1.PXM.a > dsppnportrange 2.3

minSvccVpi:         0             maxSvccVpi:      4095
minSvccVci:        35             maxSvccVci:     65535
minSvpcVpi:         1             maxSvpcVpi:      4095

SES_SJ.1.PXM.a >

cnfpnportsig

Configure PNNI Port Signaling—PXM1

Use the cnfpnportsig command to set ATM signaling parameters on a specified port. This command is used only when a port is administratively down (by dnpnport). At least one keyword must be specified. The parameters univer and nniver are mutually exclusive and determine the port type either as uni or nni respectively. For UNI port on the controller, the port on BPX switch must be configured as a UNI port. For IISP port on the controller, the port on the switch must be configured as UNI port. For PNNI port on the controller, the port on the switch must be configured either as NNI port or trunk.

Syntax

cnfpnportsig <portid> [-univer {uni30 | uni31 | uni40 |q2931 |none |self}]
[
-nniver {iisp30 | iisp31 | pnni10|enni |aini}][-unitype {public | private}]
[
-addrplan {both |aesa | e164}][-side {user |network}][-vpi <vpi>][-sigvci <signalling-vci>]
[
-rccvci <routing-vci>][-cntlvc {ip}][-passalongcap {enable | disable}]
[
-hopcntgen {enable |disable}][-vpivcialloc {enable |disable}] [-svcroutingpri <svcroutingPriority>]

Syntax Description

portid

Interface ID in the form of [shelf.]slot[:subslot].port[:subport].

-univer

The UNI version: uni30, uni31, uni40, none, or self.

Note univer and nniver are mutually exclusive.

The interface at each end of the connection must have the same interface type. Also, the port type on the PNNI controller must be the same as on the slave. If this version is sufficient, you can forego this parameter. However, to change a UNI version, the port must be down. Remember to up the port by using the uppnport command after completing the cnfpnportsig command.

The none choice applies to any port that does not need to run SSCOP protocol, for example, SPVC endpoints. The self choice applies to voice SVCs.

Default: uni31

-nniver

The NNI version: iisp30, iisp31, pnni10, aini, or enni.

Note univer and nniver are mutually exclusive.

The interface at each end of the connection must have the same interface type. Also, the port type on the PNNI controller must be the same as on the slave.

If this version is sufficient, you can forego this parameter. However, to change an NNI version, the port must be down. Remember to up the port by using the uppnport command after completing the cnfpnportsig command.

Default: pnni10

-unitype

The type of UNI is either private or public. This parameter is relevant only if you specified a UNI interface through the -univer parameter.

Default: private

-addrplan

The address plan of the calling party that the interface accepts. The choices are both, e164, and aesa.

Only a public UNI can use this parameter. For all other interface types, the port automatically accepts either AESA or E.164 address plans.

Default: both (for public) and aesa (for private)

-side

The side of the port: enter either user or network. This parameter applies to IISP only and public UNI. An NNI interface type automatically is network.

An IISP or public UNI has a user side and a network side. If both sides are the same, a configuration error has occurred. The network side is the side that assigns the VPI and VCI. These links do not distinguish between SVCs and SPVCs.

Default: network

-vpi

The VPI of the signaling and routing control channel (RCC) on the port.

Range: 0-4095

Default: 0

-sigvci

The signaling VCI for the port. If you do not use the default of 5, this VCI must be in the range 32-65535.

Range: 5 or 32-65535

Default: 5

-rccvci

The routing control channel-vci: the VCI for PNNI RCC. If you do not use the default of 18, this VCI must be in the range 32-65535.

Range: 18 or 32-65535

Default: 18

-cntlvc

Enable for an IP-based signaling channel. This option applies only to a feeder connected to the switch. An IP-based control channel is mutually exclusive of either UNI or NNI. The only choice for -cntlvc is ip.

Default: ip

-passalongcap

Pass-along capability: enter enable or disable. With this capability, the port has the ability to pass along unrecognized information elements (IEs) or messages. Enabling or disabling the pass-along capability applies to AINI, IISP, and public UNI. For all other types, the port behaves as if pass-along is enabled. You cannot disable pass-along on the other port types.

Default: enable

-hopcntgen

This parameter applies to AINI only. Enter either enable or disable. If you enable hop counting for AINI, the controller generates the hop counter information IE for all setup messages that pass through the interface if this IE does not already exist in the setup message. You must also enable AINI hop count IE for the switch by using the cnfainihopcount command.

Default: enable

-vpivcialloc

This parameter applies to AINI only: enter enable or disable. If you enable it, the interface becomes responsible for assigning the VPI and VCI for any SVC or SPVC.

Note If you enable VPI/VCI allocation on one side of the AINI link, allocation must be disabled on the other side of the link,

Default: enable

-svcroutingpri

This parameter is the SVC routing priority for any connections entering the network. The connections that are tagged 1, which is the highest routing priority, are routed ahead of other lower priority connections.

Range: 1-15

Default: 8


Related Commands

dsppnportsig

Attributes

Access level: GROUP1

State: active

Log: log


Example

Specify an RCC VCI of 10000 for port 2.3. Ensure that the interface type is compatible with the parameter you want to change and perform the following tasks:

1. Confirm that the interface type for 1:2.1:1 is NNI.

2. Down the port.

3. Configure the RCC VCI to be 10000.

SES_SJ.1.PXM.a > dsppnport 2.3

Port:               2.3               Logical ID:       131840            
IF status:          up                Admin Status:     up                
UCSM:               enable            
Auto-config:        enable            Addrs-reg:        enable            
IF-side:            network           IF-type:          nni               
UniType:            private           Version:          pnni10            
PassAlongCapab:     n/a               
Input filter:       0                 Output filter:    0                 
minSvccVpi:         0                 maxSvccVpi:       255               
minSvccVci:         35                maxSvccVci:       65535             
minSvpcVpi:         1                 maxSvpcVpi:       255               

       #SpvcCfg:  #SpvcActive:  #SpvpCfg:  #SpvpActive:  
p2p :  0          0             0          0             
p2mp:  0          0             0          0             
       #Svcc:     #Svpc:        Total:     
p2p :  0          0             0          
p2mp:  0          0             0          
                                Total:     0             
SES_SJ.1.PXM.a >

SES_SJ.1.PXM.a > dnpnport 2.3
SES_SJ.1.PXM.a > cnfpnportsig 2.3 -rccvci 10000

Example

Verify the port by entering the dsppnportsig command.

SES_SJ.1.PXM.a > dsppnportsig 2.3

provisioned IF-type: nni   version:     pnni10  
sigType:  private          side:        network 
addrPlan:  aesa    
VpiVciAllocator:  n/a      HopCounterGen:  n/a
PassAlongCapab:  n/a
sigVpi:          0         sigVci:             5
rccVpi:          0         rccVci:         10000

Example

Up port 2.3 by entering the uppnport command.

SES_SJ.1.PXM.a > uppnport 2.3

SES_SJ.1.PXM.a >

Example

Configure the SVC routing priority to 8 for port 2.3.

SES_SJ.1.PXM.a > cnfpnportsig 2.3 -svcroutingpri 8

Example

Verify the SVC priority routing value for port 2.3 by entering the dsppnportsig command.

SES_SJ.1.PXM.a > dsppnportsig 2.3

provisioned IF-type: uni   version:     uni3.1  
sigType:  private          side:        network 
addrPlan:  aesa    
VpiVciAllocator:  n/a      HopCounterGen:  n/a
PassAlongCapab:  n/a
sigVpi:          0         sigVci:             5
rccVpi:        n/a         rccVci:           n/a
svc routing priority: 8 

SES_SJ.1.PXM.a >

cnfpswdreset

Configure Password Reset—PXM1

Use the cnfpswdreset command to enable or disable the function carried out by the sequence of key strokes that resets the node to the Cisco default password.

Enter the sequence ESC CTRL-Y.

Syntax

cnfpswdreset <flag>

Syntax Description

flag

A Boolean expression to enable or disable password reset. Enter on to enable or off to disable the sequence of keys that resets the password.


Related Commands

dsppswdreset

Attributes

Access level: SERVICE_GP

State: active

Log: log


Example

Enable the password reset.

SES_SJ.1.PXM.a > cnfpswdreset on

Example

Verify the results by entering the dsppswdreset command.

SES_SJ.1.PXM.a > dsppswdreset
Password Reset feature currently enabled

SES_SJ.1.PXM.a >

cnfqosdefault

Configure Quality of Service Default—PXM1

Use the cnfqosdefault command to specify default, switch-level QoS values for three service classes. The applicable service classes are CBR, rt-VBR, and nrt-VBR. The switch applies these default values to an SVC or SPVC if the incoming setup message does not contain the QoS specification. For an SPVC, the values specified through addcon or cnfcon override the defaults configured through the cnfqosdefault command.

You can specify defaults for one service class at a time. In addition to the bandwidth parameters, you can either enable (activate) or disable the default configuration.

The default state is disabled. Therefore, be sure to enable the configuration for each QoS if you want PNNI to use it. You can configure the parameters and leave them disabled until a suitable time.

The following are the optional bandwidth parameters:

Maximum cell transfer delay

Peak-to-peak cell delay variation

Maximum cell loss ratio for cells with CLP = 0

Maximum cell loss ratio for cells with CLP = 1 or 0

Syntax

cnfqosdefault <cbr | rtvbr | nrtvbr>[<-maxctd> maxctd] [<-ppcdv> ppcdv] [<-maxclrclp0> maxclrclp0] [<-maxclrclp01> maxclrclp01] [<-enable> {yes | no}]

Syntax Description

cbr, rtvbr, nrtvbr

Specifies the service class for the current iteration of the command.

-maxctd

Specifies the maximum cell transfer delay.

Range: 0-65535 ms

Default: unspecified

-ppcdv

Specifies the peak-to-peak cell delay variation.

Range: 0-16777215 ms

Default: unspecified

-maxclrclp0

Specifies an integer for the maximum cell loss ratio for CLP0.

Range: 1-15

Default: unspecified

-maxclrclp01

Specifies an integer for the maximum cell loss ratio for CLP+0.

Range: 1-15

Default: unspecified

-enable

Specifies the entry to enable or disable the switch level defaults for the current service class. Enter yes to enable and no for the default state.

Default: no


Related Commands

clrqosdefault, dspqosdefault

Attributes

Access level: GROUP1

State: active

Log: log


Example

For CBR, configure and enable the following:

Maximum cell transfer delay of 100 ms

Maximum cell delay variation of 1000 microseconds

Maximum cell loss ratio for CLP0 of 10

Maximum cell loss ratio for CLP0+1 of 5

SES_SJ.1.PXM.a > cnfqosdefault cbr -maxctd 100 -ppcdv 1000 -maxclrclp0 10 -maxclrclp01 5 
-enable yes

Example

After configuring the defaults, disable them. Check the configuration by entering the dspqosdefault command. Then, reenable the switch level defaults and recheck them.


Note The output of the dspqosdefault command is edited to show only the CBR values.


SES_SJ.1.PXM.a > dspqosdefault


Service Category = cbr                        Qos Default Enable = yes             
MaxCTD =           100                        ppCDV  =             1000            
MaxClrClp0 =       10                         MaxClrClp01 =        5               


Service Category = rt-vbr                     Qos Default Enable = no              
MaxCTD =           Not Provisioned            ppCDV  =             Not Provisioned 
MaxClrClp0 =       Not Provisioned            MaxClrClp01 =        Not Provisioned 


Service Category = nrt-vbr                    Qos Default Enable = no              
MaxCTD =           Not Provisioned            ppCDV  =             Not Provisioned 
MaxClrClp0 =       Not Provisioned            MaxClrClp01 =        Not Provisioned 

SES_SJ.1.PXM.a > cnfqosdefault cbr -enable no

SES_SJ.1.PXM.a > dspqosdefault


Service Category = cbr                        Qos Default Enable = no              
MaxCTD =           100                        ppCDV  =             1000            
MaxClrClp0 =       10                         MaxClrClp01 =        5               


Service Category = rt-vbr                     Qos Default Enable = no              
MaxCTD =           Not Provisioned            ppCDV  =             Not Provisioned 
MaxClrClp0 =       Not Provisioned            MaxClrClp01 =        Not Provisioned 


Service Category = nrt-vbr                    Qos Default Enable = no              
MaxCTD =           Not Provisioned            ppCDV  =             Not Provisioned 
MaxClrClp0 =       Not Provisioned            MaxClrClp01 =        Not Provisioned 

SES_SJ.1.PXM.a > cnfqosdefault cbr -enable yes

SES_SJ.1.PXM.a > dspqosdefault


Service Category = cbr                        Qos Default Enable = yes             
MaxCTD =           100                        ppCDV  =             1000            
MaxClrClp0 =       10                         MaxClrClp01 =        5               


Service Category = rt-vbr                     Qos Default Enable = no              
MaxCTD =           Not Provisioned            ppCDV  =             Not Provisioned 
MaxClrClp0 =       Not Provisioned            MaxClrClp01 =        Not Provisioned 


Service Category = nrt-vbr                    Qos Default Enable = no              
MaxCTD =           Not Provisioned            ppCDV  =             Not Provisioned 
MaxClrClp0 =       Not Provisioned            MaxClrClp01 =        Not Provisioned 

SES_SJ.1.PXM.a > 

cnfrrtparm

Configure Reroute Parameters—PXM1

Use the cnfrrtparm command to configure the time periods that the switch waits between each reroute retry attempt. When an SPVC fails, the system immediately attempts to reroute the connection. If the first reroute attempt fails, the switch keeps trying to reroute the connection according to the slow retry interval (-slowtmr) and the fast retry interval base (-fasttmrbase).

The fast retry interval base is an incremental value (in 100 ms units) that is incriminated each time the switch attempts to reroute the connection and fails.

The switch then waits the incremented amount of time before it attempts to reroute the connection again. The fast retry interval base continues to increment after each reroute attempt until it is equal to the slow retry interval value or until the reroute succeeds.

The slow retry interval is a fixed value (in seconds) that occurs between all subsequent reroute attempts. After the fast retry interval base reaches the slow retry interval, the switch attempts to reroute the connection at the rate of the slow retry interval. No limit exists for the number of reroute attempts once the slow retry interval begins.

For example, if the fast retry interval base is 50-100 ms intervals (5 sec) and the slow retry interval is 300 sec (5 min), the switch attempts to reroute the connection 5 sec after the first attempt, 10 sec after the second attempt, 15 sec after the third attempt, and so on until the fast retry interval base equals 300 sec (5 min). Afterwards, the switch continues to attempt to reroute the connection every 5 min or until the reroute is successful.

Syntax

cnfrrtparm [-slowtmr <slow-retry-interval>] [-fasttmrbase <fast-retry-interval-base>]

Syntax Description

-slowtmr

Specifies the slow call retry frequency in seconds.

Range: 1-65535

Default: 60 sec

-fasttmrbase

Specifies the fast call retry base in seconds.

Range: 1-3600

Default: 5 sec


Related Commands

dsprrtparm

Attributes

Access level: SUPER_GP

State: active

Log: log


Example

Set the slow timer to 300 sec intervals and the fast timer base to 7 sec (70 x 100 ms).

SES_SJ.1.PXM.a > cnfrrtparm -slowtmr 300 -fasttmrbase 70

SES_SJ.1.PXM.a >

Example

Check the results by entering the dsprrtparm command.

SES_SJ.1.PXM.a > dsprrtparm

Global SPVC Retry Parameters: 
--------------------------------
Slow Retry Interval: 300 sec
Fast Retry Interval Base: 70 (in 100 msec)

SES_SJ.1.PXM.a >

cnfrteopt

Configure Route Optimization—PXM1

Use the cnfrteopt command to configure periodic route optimization to improve bandwidth utilization. This type of optimization is a type of connection grooming. To automate route optimization, the cnfrteopt command specifies an interval between new optimization cycles.


Note To force immediate route optimization, use the optrte command.


The load created by route optimization is extremely small and cannot cause congestion.

You can choose a time period for optimization so that disruption is minimal. For example, you could specify that the switch starts grooming a range of SPVCs for one hour at midnight.


Note Route optimization is a background process and does not attempt to optimize all possible connections at once.


The nature of SPVCs provides a reason for periodic grooming: during the course of daily operation, better routes may become available. The determining factor for a better route is the maximum cost (maxcost). For details about the maxcost parameter, see the addcon description. The PNNI protocol identifies this maximum cost by another name: administrative weight (AW).


Note If you do not specify a maxcost with either the addcon or cnfcon command, the routing protocol uses the AW on only forward links to calculate a new route for the connection.


If the connection has a specified maxcost, the routing protocol calculates possible routes by using the AW in both directions.

Syntax

cnfrteopt <portid> {enable | disable}[-range <starting-vpi/vci..ending-vpi/vci>][-interval <interval>]
[
-tod <start-time..end-time>]

Syntax Description

portid

Identifies the a port for which route optimization is configure, in the form of [shelf.]slot[:subslot].port[:subport].

enable | disable

Enables or disables route optimization. If grooming is operational and you want to disable it, run the cnfrteopt command and enter disable.

Default: disable

-range

Specifies a range of SPVCs to receive route optimization. starting-vpi/vci and ending-vpi/vci are in VPI/VCI format. The ending VPI/VCI must be greater than or equal to the starting VPI/VCI. If no range is specified, all active SPVCs on the port are considered, or use the option all to specify that all SPVCs on the port are considered.

Range: 0-4095 (VPI)

Range: 32-65535 (VCI)

-interval

Specifies the frequency of route optimization in minutes. Keyword that specifies the frequency at which grooming begins. The units of measure are minutes. Counting starts at one of the following two moments:

The moment you enter the cnfrteopt command.

The starting time specified by TOD for the cnfrteopt command.

If the interval is less than half the amount of time specified by the start-time..end-time parameter, route optimization can begin more than once during the time period. For example, if the periods of optimization are two hours beginning at midnight and 4:00 AM and the interval is one hour, route optimization can occur two to four times per day.

Range: 10-10000

Default: 60 min

-tod

Specifies the keyword for the time to start and stop grooming. The format is a 24-hour clock: 00:00-23:59. The default for both start and end-time is 00:00. If you enter cnfrteopt during the time specified by tod, the optimization cycle begins during the next time interval.

If the time for the node changes (for example, by way of the cnftime command), the node might skip one optimization cycle.

Note Enter two dots with no spaces between starting and ending times.

The default time range is anytime.



Note Only one SPVC range is supported. The newly entered range replaces the old range. Same is true for the time range.


Related Commands

cnfrteoptthld, dsprteoptcnf, dsprteoptstat, optrte

Attributes

Access level: GROUP1

State: active

Log: log


Example

Enable route optimization for specific SPVCs with parameters other than default.

SES_SJ.1.PXM.a > cnfrteopt 1.6 enable -range 1/40..10/1000 -interval 45 -tod 23:00..23:30

SES_SJ.1.PXM.a > 

cnfrteoptthld

Configure Route Optimization Threshold—PXM1

Use the cnfrteoptthld command to specify the percentage reduction in the administrative weight of the existing path required to trigger route optimization. The criterion for selecting a new route is a threshold in the form of the percent of difference in route cost.

The default for route optimization is a 30% reduction of the cost of a route. By entering the cnfrteoptthld command, you can change the percentage of routing cost-improvement.

Syntax

cnfrteoptthld <percent>

Syntax Description

percent

Determines the percent of reduction in routing cost that triggers rerouting.

Range: 5-100

Default: 30


Related Commands

cnfrteopt, dsprteoptcnf, dsprteoptstat, optrte

Attributes

Access level: GROUP1

State: active

Log: log


Example

Change the re-routing threshold to a 50% reduction in the route cost.

spirita.1.PXM.a > cnfrteoptthld 50

spirita.1.PXM.a > 

cnfserialif

Configure Serial Interface—PXM1

Use the cnfserialif command to change the data rate on a serial interface on the PXM-UI back card. The two types of serial ports are the console port and the maintenance port. These ports provide user-access for controlling the switch. The default speed on a serial interface is 9600 bps, but higher speed terminals are frequently available.

Each port connects to a different type of terminal implementation. For a description of how to use these physical ports for switch control, refer to the Cisco SES PNNI Controller Software Configuration Guide.

Syntax

cnfserialif <port#> <speed>

Syntax Description

port#

Specifies the physical port. Enter 1 to select the maintenance port, or 2 to select the console port.

speed

Specifies a data rate in bits per second. Valid entries are 1200, 2400, 4800, 9600, 19200, 38400.


Related Commands

delserialif, dspserialif

Attributes

Access level: SUPER_GP

State: active

Log: no


Example

Configure the maintenance port to have a data rate of 19200 bps.

spirita.1.PXM.a > cnfserialif 1 19200

Example

Verify the results by entering the dspserialif command.

SES_SJ.1.PXM.a > dspserialif 1
  SerialPortNum   : 1
  SerialPortType  : maintenance
  SerialPortSpeed : 19200

SES_SJ.1.PXM.a > 

cnfsig

Configure Signaling—PXM1

Use the cnfsig command to configure signaling timers for a port. At least one keyword must be specified. This command is used regardless of the state of the port. The new configuration applies to new incoming calls while existing calls remain intact.

Syntax

cnfsig <portid>[-t301 <t301-timer>][-t303 <t303-timer>][-t308 <t308-timer>]
[-t310 <t310-timer>][-t316 <t316-timer>][-t317< t317-timer>][-t322 <t322-timer>]
[-t397 <t397-timer>][-t398 <t398-timer>][-t399 <t399-timer>][-maxcrbk <value>]

Syntax Description

portid

Identifies the port for the call in the form of [shelf.]slot[:subslot].port[:subport].

-t301

Set the T301 timer.

Range: 150-240 sec

Default: 180

-t303

Set the T303 timer.

Range: 4-8 sec

Default: 4

-t308

Set the T308 timer.

Range: 20-45 sec

Default: 30

-t310

Set the T310 timer.

Range: 10-20 sec for UNI 3.1/3.1and 30-120 sec for UNI 4.0.

Default: 10

-t316

Set the T316 timer.

Range: 90-300 sec

Default: 90

-t317

Set the T317 timer.

Range: 60-300 sec

Default: 60

-t322

Set the T322 timer.

Range: 4-20 sec

Default: 4

-t397

Set the T397 timer.

Range: 180-240 sec

Default: 180

-t398

Set the T398 timer.

Range: 4-20 sec

Default: 4

-t399

Set the T399 timer.

Range is 14-28 sec for UNI 3.0/3.1 and 34-124 sec for UNI 4.0

Default: 14

-maxcrbk

Set the maximum crankback attempts allowed for a port.

Range: 1-10

Default: 3


Related Commands

dspsig, dspsigdiag, dspsigstats

Attributes

Access level: GROUP1

State: active

Log: log


Example

Configure port 1.6 to have the maximum crankback count of 5.

SES_SJ.1.PXM.a > cnfsig 1.6 -maxcrbk 5

Example

Check the results by entering the dspsig command for port 1.6.


Note Check the default values in the dspsig output.


SES_SJ.1.PXM.a > dspsig 1.6

Signaling Timers for port : 1.6 

Timer           Value(secs)
-----           -----------
t301            180
t303            4
t308            30
t310            10
t316            90
t317            60
t322            4
t397            180
t398            4
t399            14

Max Crankback:  5

SES_SJ.1.PXM.a > 

cnfsigdiag

Configure Signaling Diagnostic—PXM1

Use the cnfsigdiag command to create a filter table for signaling diagnostics or disable signaling diagnostics. Signaling diagnostics are disabled by default.

The ATM signaling diagnostics are tools used to troubleshoot call failures in the network and should not be enabled while the switch is operating.

Syntax

cnfsigdiag {[enable | disable | index]} [-cldaddr nsap-address] [-clgaddr nsap-address]
[-cldaddrmask atm-address-mask] [-clgaddrmask atm-address-mask] [-casttype {all | p2p | p2mp}]
[-clrcause clear-cause-code] [-connctgy {all | svc | svp | swvc | swvp}] [-inport portid]
[-outport portid] [-maxrec max-num-records ] [-scope {all | ext | int}]
[-servctgy {all | cbr | rtvbr | nrtvbr | ubr | abr}] [-status {active | inactive}]

Syntax Description

enable, disable, or index

Enables or disables the signaling diagnostics or configures an index.

Specifies the diagnostics index number for the filter table and enter the diagnostics configuration mode. The range for the index is 1-50. If you do not specify an index, the enable or disable condition globally applies to all signaling diagnostics.

Default: disable

-cldaddr

Determines the nsap-address the filter for ATM signaling call failures against this called address.

Default: NULL

-clgaddr

Determines the nsap-address the filter for ATM signaling call failures against this calling address.

Default: NULL

-cldaddrmask

Determines the atm-address-mask to identify valid bits of the called NSAP address field, for example, ff.ff.ff. To match this selection criterion, a failed connect setup must have a called party address value equal to the configured called party address for all bits that are 1 in the specified mask.

Default: NULL. NULL means the rejected call matches the filter criteria for any called address in the rejected call.

-clgaddrmask

Determines the atm-address-mask to identify valid bits of the calling NSAP address field, for example, ff.ff.ff. To match this selection criteria, a failed connect setup must have a calling party address value equal to the configured calling party address for all bits that are 1 in the specified mask.

Default: NULL. NULL means the call matches the filter criteria for any calling address in the rejected call.

-casttype

Determines the F = filtering by connection type. The types are point-to-point (p2p), point-to-multipoint (p2mp)—currently not supported, or both (all).

Default: all

-clrcause

Determines the clear-cause-code. The filters for the ATM signaling call failures are specified by the release cause code (a decimal number) as specified in the ATM Forum UNI 3.1 specification.

Default: 0, meaning the cause code is not considered during filtering.

-connctgy

Determines the filters for ATM signaling call failures by virtual circuit category (SPVC, SPVP, SVC, SVP, or all of these circuit categories).

Default: all

-inport

Specifies the portid. The filters for the ATM signaling call failures are based on the incoming port of the call.

Default: 0, meaning the incoming port is not considered during filtering.

-outport

Specifies the portid. The filters for the ATM signaling call failures are based on the outgoing port of the call.

Default: 0, meaning the outgoing port is not considered during filtering.

-maxrec

Specifies the max-num-records. The maximum number of records are collected for a particular signaling diagnostics filter table entry. When the maximum value is reached, the older records are deleted. If this field is set to -1, the records are not overwritten. Setting this field to -1 increases memory usage for call failure records and can lead to shortages of available system memory.

Range: -1-214783647

Default: 20

-scope

Specifies that the filtering scope choices are within the switch (int), on other switches (ext), or both (all).

Default: all

-servctgy

Determines the filters for the ATM signaling call failures by service category (service type): valid entries are: all (for all service types), cbr, rtvbr, nrtvbr, ubr, or abr.

Default: all

-status

Specifies the status of the entry for the signaling diagnostics filter table. Enter active to begin filtering failed connections or inactive to stop filtering failed connections. The inactive specification causes the node to delete all the records associated with the filter entry.

Default: inactive


Related Commands

clrsigstats, delsigdiag, dspsigdiag. dspsigstats

Attributes

Access level: SERVICE_GP

State: active

Log: log


Example

Enable the signaling diagnostics.

SES_SJ.1.PXM.a > cnfsigdiag enable

Example

Verify the results by entering the dspsigdiag command with the applicable option.

SES_SJ.1.PXM.a > dspsigdiag status
An Index of 0 will be treated as a request for all filters
Dspsigdiag option : 3 
 Index : 0 
 message ID : 292 
message Length : 1704 

  Signalling diagnostics enabled globally 

SES_SJ.1.PXM.a >

cnfsnmp

Configure SNMP—PXM1

Use the cnfsnmp command to configure SNMP strings. The three strings are community, contact, and system location. You can configure only one of these strings with a single execution of the cnfsnmp command.

Syntax

cnfsnmp <community [string <ro | rw>]> <contact [string]> <location [string]>

Syntax Description

community

A community string provides an authentication mechanism to access MIB objects by using SNMPv1 protocol. One read-only (ro) access string and one read-write (rw) access string are supported. You can specify your own rw and ro strings (up to 32 characters each) or keep one or both of the reserved strings. You cannot set ro and rw to the same string value. If you specify no community strings, "private rw" is assumed. The following are the reserved strings:

Community rw string private

Community ro public

The string acts like a password to permit access to the SNMP Protocol. Further, the access privilege of either ro or rw determines allowable operations on MIB Objects. The setting can be either "ro" for read-only or "rw" for read-write. With read-only access, a management station is allowed only to retrieve information. With read-write access, authorized management stations are able to retrieve and modify MIB objects.

contact

Keyword that specifies the system contact string for sysContact MIB object in MIB-II. The string in this case is text that describes the contact. For example, the contact could be an administrator's email address. Spaces are allowed between character strings. You can reset the contact string to no text by entering the cnfsnmp command and contact keyword then press Enter or Return with no other text.

Default: no text

location

Keyword that specifies the location of the system. The system location string is used for sysLocation MIB object in MIB-II. You can reset the location string to no text by entering the cnfsnmp command and location keyword then press Enter or Return with no other text.

Default: no text


Related Commands

dspsnmp

Attributes

Access level: SUPER_GP

State: active

Log: log


Example

Configure the following community strings.

1. Configure the rw string as toplevel.

2. Enter the contact davids@be.com.

3. Enter the location Building 3/Room 214.

SES_SJ.1.PXM.a > cnfsnmp community toplevel rw

SES_SJ.1.PXM.a > cnfsnmp contact davids@be.com

SES_SJ.1.PXM.a > cnfsnmp location Building 3/Room 214

Example

Display the SNMP settings by entering the dspsnmp command.

SES_SJ.1.PXM.a > dspsnmp
SES_SJ                           System Rev: 03.00  Jan. 22, 2002 10:33:07 PST
SES-CNTL                                             Node Alarm: MAJOR

Community (rw):          toplevel                        
Community (ro):          public                          
System Location:         Building 3/Room 214                     
System Contact:          davids@be.com                           

Example

Reset the contact and location strings to no text and reenter the dspsnmp command.

SES_SJ.1.PXM.a > cnfsnmp location

SES_SJ.1.PXM.a > cnfsnmp contact

SES_SJ.1.PXM.a > dspsnmp
SES_SJ                           System Rev: 03.00  Jan. 22, 2002 10:33:48 PST
SES-CNTL                                             Node Alarm: MAJOR

Community (rw):          toplevel                        
Community (ro):          public                          
System Location:                                                 
System Contact:                                                  

SES_SJ.1.PXM.a >

cnfsntp

Configure SNTP—PXM1

Use the cnfsntp command to configure the timers for the client and to turn the SNTP server on or off.

Syntax

cnfsntp {[-polling insecond] [-waiting insecond] [-rb insecond] [-client on |off] [-server on | off]
[-stratum 0-15]}

Syntax Description

-polling insecond

Specifies the synchronization time for the client polling server period.

Default: 64 sec

-waiting insecond

Specifies that the client waits for the response time.

Default: 5 sec

-rb insecond

Polls the primary server when rollback is enabled.

Default: 1024 sec

-client

The client cannot be turned on by the SES must be set to off.

Default: off

-server

Enables the server or disables the server. Enter either on or off.

Default: off

-stratum

Determines the stratum value.

Note The round trip delay value is 200 ms.

Default: 0


Related Commands

clrsntpstats, dbgsntp, dspsntp, dspsntpstats

Attributes

Access level: GROUP1

State: active

Log: log


Example

Configure the SNTP stratum value to be 0.

SES_SJ.1.PXM.a > cnfsntp -stratum 0

SES_SJ.1.PXM.a >

Example

Verify the results by entering the dspsntp command.

SES_SJ.1.PXM.a > dspsntp

client: no
server: no

polling: 64
waiting: 5
rollback: 1024
stratum(default): 0
stratum(current): 0
sync: no

SES_SJ.1.PXM.a >

cnfspvcprfx

Configure SPVC Prefix—PXM1

Use the cnfspvcprfx command to configure the SPVC prefix. The port at each end of the SPVC must have a globally unique SPVC address. When the connection is defined, the address is generated by the switch, and consists of the SPVC prefix and an internal, generated number that identifies the port.

For the node to support SPVCs, it must have a 13-byte SPVC prefix that applies to the entire node. No SPVCs can exist on the node until it has an SPVC prefix.

Likewise, to change this prefix, no SPVCs can exist on the node.


Note If you change the peer group ID for the switch, you should also change the SPVC address prefix so that the bytes that correspond to the peer group ID match the corresponding bytes in the SPVC prefix.


The following list shows the order of prerequisite commands and the cnfspvcprfx command. All commands run on the PXM.

cnfpnni-intf command

cnfspvcprfx command

dspspvcprfx command

For more information on configuring the SPVC prefix, refer to the Cisco MGX and SES PNNI Network Planning Guide.

Syntax

cnfspvcprfx -prfx <prefix|default>

Syntax Description

-prfx

Unique 13 byte SPVC node prefix.

The default SPVC prefix is the first 13-bytes of the default ATM address


Related Commands

dspspvcprfx

Attributes

Access level: SUPER_GP

State: active

Log: log


Example

Configure the SPVC prefix with he default node prefix.

SES_SJ.1.PXM.a > cnfspvcprfx -prfx default

Example

Verify the SPVC node prefix by entering the dspspvcprfx command. The International Code Designator (ICD) field shows the prefix is the default from Cisco (0091).

SES_SJ.1.PXM.a > dspspvcprfx

SPVC Node Prefix: 47.009181000000003071f813a1


cnfsscop

Configure SSCOP—PXM1

Use the cnfsscop command to set SSCOP parameters for a specified port. At least one keyword must be specified. This command is used regardless of the state of the port.

Syntax

cnfsscop <portid>[-polltmr {poll-timer value | 0}][-keepalivetmr {keepalive-timer value | 0}]
[-idletmr {idle-timer value| 0}][-cctmr {cc-timer value| 0}]
[-norsptmr {noresponse-timer value| 0}][-t309tmr {t309-timer value| 0}]
[-maxcc {retries | 0}][-sndwnd {send-window-size | 0}][-rcvwnd {recv-window-size | 0}]

Syntax Description

portid

Interface ID in the form of [shelf.]slot[:subslot].port[:subport].

-polltmr

Number of seconds to send POLL PDUs at the active phase. 0 means to restore the default value.

Valid Range: 1-5 sec

Default: 1 sec

-keepalivetmr

Number of seconds to send POLL PDUs at the transient phase. 0 means to restore the default value.

Valid Range: 2-10 sec

Default: 5 sec

-idletmr

Number of seconds to send POLL PDUs at the idle phase. 0 means to restore the default value.

Valid Range: 5-20 sec

Default: 10 sec

-cctmr

Number of seconds to send BGN/END/RS/ER PDUs at the connection control phase. 0 means to restore the default value.

Valid Range: 1-5 sec

Default: 1 sec

-norsptmr

Number of seconds at least one STAT PDU needs to be received. 0 means to restore the default value.

Valid Range: 7-45 sec

Default: 30 sec

-t309tmr

Number of seconds before which SAAL reconnection occurs after having been disconnected earlier.

Valid Range: 10-15 sec

Default: 10 sec

-maxcc

Maximum number of retries for connection control operations. 0 means to restore the default value.

Valid Range: 4-15

Default: 10

-sndwnd

Number of packets the port can send before it must receive an acknowledgment from the ATM switch. 0 means to restore the default value.

Valid Range: 1-127

Default: 30

-rcvwnd

Number of packets the port can receive before it must send an acknowledgment to the ATM switch. 0 means to restore the default value.

Valid Range: 1-127

Default: 30


Related Commands

clrsscopstats, disablesscop, dspsscop, dspsscopstats

Attributes

Access level: GROUP1

State: active

Log: log


Example

Configure SSCOP parameters with the default settings for port 1.6.

SES_SJ.1.PXM.a > cnfsscop 1.6

Example

Verify the default settings by entering the dspsscop command for port 1.6.

SES_SJ.1.PXM.a > dspsscop 1.6

SSCOP details for interface: 1.6

   Current State = enabled, Current Link State = Unknown State , 
SSCOP version = Invalid
   Send Sequence Number: Current = 0,  Maximum = 0
   Send Sequence Number Acked = 0
   Rcv Sequence Number: Lower Edge = 0, Upper Edge = 0, Max = 0
   Poll Sequence Number = 0, Poll Ack Sequence Number = 0
   Vt(Pd) = 0   Vt(Sq) = 0
   Timer_IDLE = 10 - Inactive
   Timer_CC = 1 - Inactive
   Timer_POLL = 1 - Inactive
   Timer_KEEPALIVE = 5 - Inactive
   Timer_NO-RESPONSE = 30 - Inactive
   Timer_T309 = 10 - Inactive
   Max CC = 10
   Send Window = 30
   Recv Window = 30
   Current Retry Count = 0, Maximum Retry Count = 0
   AckQ count = 0, RcvQ count = 0, TxQ count = 0
   AckQ HWM = 0,  RcvQ HWM = 0, TxQ HWM = 0

Type <CR> to continue, Q<CR> to stop: 
      Statistics -
      Pdu's Sent = 0, Pdu's Received = 0, Pdu's Ignored = 0
      Begin = 0/0, Begin Ack = 0/0, Begin Reject = 0/0
      End = 0/0, End Ack = 0/0
      Resync = 0/0, Resync Ack = 0/0
      Sequenced Data = 0/0, Sequenced Poll Data = 0/0
      Poll = 0/0, Stat = 0/0, Unsolicited Stat = 0/0
      Unassured Data = 0/0, Mgmt Data = 0/0, Unknown Pdu's = 0
      Lack of credit = 0
SES_SJ.1.PXM.a > 

cnfstatsmgr

Configure Statistics Manager—PXM1

Use the cnfstatsmgr command to set the IP address of the Cisco WAN Manager (CWM) that manages statistics for this node.

Syntax

cnfstatsmgr <index> <IP Address>

Syntax Description

index

The following are the indexes:

1: primary statistics manager

2: secondary statistics manager

3: tertiary statistics manager

4: statistics master

IP Address

IP address of the CWM statistics manager for this node.


Related Commands

dspstatsmgr

Attributes

Access level: SERVICE_GP

State: active

Log: no


Example

Configure the IP address for the statistics manager for index 1.

SES_SJ.1.PXM.a > cnfstatsmgr 1 172.29.4.50

Example

Verify the results by entering the dspstatsmgr command.

SES_SJ.1.PXM.a > dspstatsmgr
 Statistics Manager     IP Address
 ------------------     ----------
 Primary                172.29.4.50 
 Secondary              0.0.0.0 
 Tertiary               0.0.0.0 
 Statistics Master      0.0.0.0 

SES_SJ.1.PXM.a >

cnfsvcoverride

Configure SVC Override—PXM1

Use the cnfsvcoverride command to configure the SVC override parameters on a per port basis. The SVC override configuration is part of the nodal database and is persistent and redundant. If a single ended SPVC establishment request is received and the VPI/VCI on the port is being used by an SVC connection, the nodal configuration for the SVC override is checked. If the SVC override option is enabled, the existing SVC is torn down and the SPVC request is rejected. Therefore, the next time the SPVC establishment request is received, the connection can setup the VPI/VCI on the port.

Syntax

cnfsvcoverride [-spvcoverridesvc {enable | disable}] [-spvcoverridesvp {enable | disable}] [-spvpoverridesvp {enable | disable}]

Syntax Description

-spvcoverridesvc

Enter one of the following options:

enable—Specifies that the incoming SPVC overrides the active SVC on the same port for VPI and VCI.

disable

Default: disable

-spvcoverridesvp

Enter one of the following options:

enable—Specifies that the incoming SPVC overrides the active SVP on the same port for VPI.

disable

Default: disable

-spvpoverridesvp

Enter one of the following options:

enable—Specifies that the incoming SPVP overrides the active SVC on the same port for VPI.

disable

Default: disable


Related Commands

cnfpnportcc, clrspvcnonpers, dsppnportcc, dsptrftolerance

Attributes

Access level: SUPER_GP

State: active

Log: log


Example

Enable the -spvcoverridesvc parameter to override the active SVC on the same port for VPI and VCI.

SES_SJ.1.PXM.a > cnfsvcoverride -spvcoverridesvc enable

SES_SJ.1.PXM.a >

Example

Verify that the spvcoverridesvc parameter is enabled by entering the dspsvcoverride command.

SES_SJ.1.PXM.a > dspsvcoverride
spvcoverridesvc:          Enabled
spvcoverridesvp:          Disabled
spvpoverridesvp:          Disabled

SES_SJ.1.PXM.a >

cnftrftolerance

Configure Traffic Conformance Tolerance—PXM1

Use the cnftrftolerance command to configure the traffic conformance tolerance between the master and slave traffic parameters for the SPVC connections. The configuration is persistent and redundant. When the traffic conformance is a nonzero value, the connection is accepted if the slave traffic parameters are within the configured tolerance with respect to the master's traffic parameters.

Syntax

cnftrftolerance % (0% to 5%)

Syntax Description

%

Specifies the node tolerance percentage. By default, the tolerance value for each parameter for all service types is 0%, which implies that the exact parameter needs to be matched.

Default: 5%


Related Commands

cnfpnportcc, clrspvcnonpers, dsppnportcc, dsptrftolerance

Attributes

Access level: SUPER_GP

State: active

Log: log


Example

Configure the traffic conformance tolerance to 1%.

SES_SJ.1.PXM.a > cnftrftolerance 1

SES_SJ.1.PXM.a >

Example

Verify the traffic conformance tolerance settings by entering the dsptrftolerance command.

SES_SJ.1.PXM.a > dsptrftolerance
Trf Tolerance for SPVCs: 1

SES_SJ.1.PXM.a >

cnftime

Configure Time—PXM1

Use the cnftime command to set the system time for the node. To see the time after you enter the cnftime command, enter the dspdate command. The system displays the time in 24-hour format.


Note Configure a time zone through cnftmzn and optional GMT offset through cnftmzngmt before you configure the time through cnftime.


Syntax

cnftime <Time>

Syntax Description

Time

Specifies the time in the following format:

hh is the hour in the range 01-24.

mm is the minute in the range 01-60.

ss is the second in the range 01-60.


Related Commands

cnfdate, cnftmzn, cnftmzngmt, dspdate

Attributes

Access level: SUPER_GP

State: active

Log: yes


Example

Set time for 11 PM. plus 20 minutes and 30 seconds.

SES_SJ.1.PXM.a > cnftime 11:20:30

cnftmzn

Configure Time Zone—PXM1

Use the cnftmzn command to configure the time zone in the Western Hemisphere for the switch. To configure a time zone outside the four standard time zones of the Western Hemisphere, enter the GMT argument, then enter the cnftmzngmt command to specify an offset in hours from Greenwich Mean Time.

The system returns no messages unless an error occurs. To see the time zone, enter the dspdate command.

Syntax

cnftmzn <Timezone>

Syntax Description

Timezone

Sets the system time zone. Enter one of the following time zones:

GMT, Greenwich Mean Time

EST, Eastern Standard Time

CST, Central Standard Time

MST, Mountain Standard Time

PST, Pacific Standard Time

EDT, Eastern Daylight Time

CDT, Central Daylight Time

MDT, Mountain Daylight Time

PDT, Pacific Daylight Time


Related Commands

cnfdate, cnftmzn, cnftmzngmt, dspdate

Attributes

Access level: SUPER_GP

State: active

Log: log


Example

Configure the time zone in the node to U.S. Pacific Standard Time.

SES_SJ.1.PXM.a > cnftmzn PST

SES_SJ.1.PXM.a >

cnftmzngmt

Configure Time Zone Management—PXM1

Use the cnftmzngmt command to configure the time zone for the node relative to GMT. Typically, this command applies to nodes outside the four standard time zones of the Western Hemisphere.

Use the cnftmzngmt command according to the following sequence:

1. Enter the cnftmzn command to specify the time zone as GMT.

2. Specify an offset in hours relative to Greenwich Mean Time by entering the cnftmzngmt command. The values are GMT plus or minus an integer in the range 1-12.

Use the dspdate command to see the time.

Syntax

cnftmzngmt <GMToffset>

Syntax Description

GMToffset

System time zone offset value. Enter one of the following time zone offset values:

-12

-11

-10

10

11

12


Related Commands

cnfdate, cnftime, cnftmzn, dspdate

Attributes

Access level: SUPER_GP

State: active

Log: log


Example

Set time zone in the shelf to GMT plus 4 hours.

SES_SJ.1.PXM.a > cnftmzngmt 4

SES_SJ.1.PXM.a >

cnftrapip

Configure Trap IP—PXM1

Use the cnftrapip command to configure the trap IP for Cisco WAN Manager. You can use the dsptrapip command to confirm the trap IP address.

Before you use the cnftrapip command, do the following steps:


Step 1 Install the SNMP agent.

Step 2 Ensure that the interface for the switch contains an IP address. To assign an IP address for the switch interface, enter the ipifconfig command.


For information about installing the SNMP agent for CWM, refer to the Cisco WAN Manager Installation for Solaris, Release 10.

Syntax

cnftrapip <ip address>

Syntax Description

ip address

Ethernet IP address where traps are configured.


Related Commands

addtrapmgr, cnfsnmp, deltrapmgr, dsptrapip, dsptrapmgr

Attributes

Access level: SUPER_GP

State: active

Log: no


Example

Set the IP address 172.29.4.50 to the switch.

SES_SJ.1.PXM.a > cnftrapip 172.29.4.50
IP Address set successfully

Example

Verify the trap IP address by entering the dsptrapip command.

SES_SJ.1.PXM.a > dsptrapip

Trap IP Address :172.29.4.50

SES_SJ.1.PXM.a >

cnfuser

Configure User—PXM1

Use the cnfuser command to configure a new password or privilege level for a user. If the user does not already exist, enter the cnfuser command with a new user-name creates that user.

If you do not specify a user-name (userID) but include one or more of the other parameters, the command applies to the current user.

Syntax

cnfuser -u <userId> [-p <password>] [-l <accessLevel>]

Syntax Description

-u

Keyword that specifies a string of 1-12 characters that identifies a user. The maximum number of users a system can accept is 50.

-p

(Optional) Keyword that specifies a new password with 5-15 characters for userId.

-l

(Optional) Keyword that specifies a new access level for the user. The accessLevel can be SERVICE_GP, SUPER_GP, GROUP1, or ANYUSER.

The new level you type must be lower than the privilege of the current user.

System privilege level to be allocated for the user ID by using one of the following options:

SERVICE_GP

SUPER_GP

GROUP1 (highest level)

GROUP2

GROUP3

GROUP4

GROUP5

ANYUSER (lowest level)

The new user cannot be configured for an access level that is higher than the level defined for the current login ID.


Related Commands

cnfname, cnfoamsegep, deluser, dspusers, users

Attributes

Access level: GROUP1

State: active

Log: yes


Example

Configure the user information with the applicable user ID, password, and access level.

SES_SJ.1.PXM.a > cnfuser -u aa -p passw123 -l ANYUSER

SES_SJ.1.PXM.a >

commitrev

Commit Revision—PXM1

Use the commitrev command to commit to the current running firmware version.

The following impacts of the commitrev command are

The primary firmware image is activated through the runrev command and is accepted.

The previous image is removed from the card's main memory (but continues to reside on disk).

Starting another graceful revision change becomes possible. If you attempt loadrev on the same card before you enter the commitrev command, the system blocks loadrev and states that a revision change is in progress.

You cannot use the abortrev command to revert to the previous image. To bring a previous image into memory and run it, you must use setrev to force-load the image (a non-graceful revision change) or enter the restoreallcnf command.

Syntax

commitrev <slot> <revision>

Syntax Description

slot

Slot number of the card where the version is set.

revision

Revision number that is derived from the name of the firmware file, for example, 3.0(0.171)P3.


Related Commands

abortrev, dspcd, dsprevs, loadrev, runrev

Attributes

Access level: SERVICE_GP

State: active

Log: log


Example

Commit to the current firmware version with the applicable slot number.

SES_SJ.1.PXM.a > commitrev 1 3.0(0.171)P3
one or more card(s) in logical slot will be reset.
Do you want to proceed (Yes/No)? n
(command not executed)

conntrace

Connection Trace—PXM1

Use the conntrace command to trace an established connection that includes a soft PVC connection. The result is displayed on the screen.

Syntax

conntrace <portid> [-callRef <callRef>] [-endptRef <endptRef>] [-vpi <vpi>][-vci <vc-i>]

Syntax Description

portid

Identifies the port for the soft PVC in the form of [shelf.]slot[:subslot].port[:subport].

-callRef

Specifies the call reference for the soft PVC.

Range: 1-16777215

-endptRef

Endpoint reference for a point-to-multipoint call. If no endpoint reference is specified, this is a point-to-point call.

Range: 1-32767

-vpi

VPI value of connection endpoint.

Range: 1-4095

-vci

VCI value of connection endpoint.

Range: 1-65535


Related Commands

pathtraceie, pathtracenode, pathtraceport

Attributes

Access level: SUPER_GP

State: active

Log: log


Example

Configure the connection trace with the applicable port ID and default settings.

spirita.1.PXM.a > conntrace 0.1.2 -callRef 1000

Result:Succ/Fail Reason: "Desc"
InterfaceId: "--"			EndptRef: "--" 
Originating Interface VPI: "--"
Originating Interface VCI: "--"
Originating Interface CallRef: "--"

NodeId	Egress Port		Vpi	Vci	CallRef	PhysPortid
XXXX	ZZZZ		aaa	bbb	cccc	eeee
XXXX	ZZZZ		aaa	bbb	cccc	eeee


Terminating Interface VPI: "--"
Terminating Interface VCI: "--"
Terminating Interface CallRef: "--"

copy

Copy—PXM1

Use the copy command to copy files.

Syntax

copy <source file name> <destination file name>

Syntax Description

source file name

The name of the file you intend to copy.

destination file name

The name of the new file resulting from copy or the name of the existing file that is over-written as a result of copy.


Related Commands

cp, cd, ls, rm, pwd, rename

Attributes

Access level: GROUP1

State: all

Log: log


Example

Enter the saveallcnf command at the prompt and enter y to proceed. Then, cd to the C: /CNF directory.

SES_SJ.1.PXM.a > saveallcnf

SES_SJ.1.PXM.a > cd C:/CNF

SES_SJ.1.PXM.a > ll
  size          date       time       name
--------       ------     ------    --------
     512    APR-07-2001  01:43:42   .                 <DIR>
     512    APR-07-2001  01:43:42   ..                <DIR>
     512    DEC-06-2001  12:28:00   TMP               <DIR>
  100328    DEC-06-2001  13:33:24   SES_SJ_01_200112061332.zip  
  100725    JAN-23-2002  05:55:06   SES_SJ_01_200201230553.zip  

In the file system : 
    total space :  819200 K bytes
    free  space :  782210 K bytes

SES_SJ.1.PXM.a > copy C: \pxm1_001.001.070.201_ses.fw

cp

Copy—PXM1

Use the cp command to copy a file to a new file on the disk. This command is the same as the copy command.

Syntax

cp <source file name> <destination file name>

Syntax Description

source file name

The name of the file you intend to copy.

destination file name

The name of the new file resulting from copy or the name of the existing file that is over-written as a result of copy.


Related Commands

cp, cd, ls, rm, pwd, rename

Attributes

Access level: GROUP1

State: all

Log: log


Example

Enter the saveallcnf command at the prompt. Enter y to proceed. Then, cd to the C: /CNF directory.

SES_SJ.1.PXM.a > saveallcnf

SES_SJ.1.PXM.a > cd C:/CNF

SES_SJ.1.PXM.a > ll
  size          date       time       name
--------       ------     ------    --------
     512    APR-07-2001  01:43:42   .                 <DIR>
     512    APR-07-2001  01:43:42   ..                <DIR>
     512    DEC-06-2001  12:28:00   TMP               <DIR>
  100328    DEC-06-2001  13:33:24   SES_SJ_01_200112061332.zip  
  100725    JAN-23-2002  05:55:06   SES_SJ_01_200201230553.zip  

In the file system : 
    total space :  819200 K bytes
    free  space :  782210 K bytes

SES_SJ.1.PXM.a > cp pxm1_001.001.070.201_ses.fw 

dbgsntp

Debug SNTP—PXM

Use the dbgsntp command to either turn the SNTP debug and trace capabilities on or off.

Syntax

dbgsntp <enable | disable> [ipaddr] [-level <info | trace | debug>]

Syntax Description

enable | disable

Enables or disables the SNTP debug and trace capabilities.

ipaddr

Specifies the IP address.

-level

Enter one of the following options:

infothe functional level of the trace only.

traceinfo level plus important events.

debugtrace level plus NTP message dump.


Related Commands

cnfsntp, deltrapmgr, dspsntp, dspsntpstats, clrsntpstats

Attributes

Access level: ANYUSER

State: active

Log: no


Example

Enable the SNTP debug and trace capabilities.

SES_SJ.1.PXM.a > dbgsntp enable -level trace

SES_SJ.1.PXM.a >

deladdr

Delete ATM Address—PXM1

Use the deladdr command to remove an ATM address for a UNI, IISP, or AINI.

Syntax

deladdr <portid> <atm-address> <length> [-plan <e164|nsap>]

Syntax Description

portid

Identifies a PNNI physical port. The format is slot:subslot.port:subport.

atm-address

Determines an ATM address or E.164 number.

The address plan specifies the address type and so determines the maximum number of bytes or bits in the address. You can specify the address plan with the forthcoming -plan option. The default plan is NSAP.

An NSAP address can have 1-20, 8-bit bytes. For example, a byte is 2-hexadecimal characters. Cisco recommends that you use 20 bytes for the NSAP address.

An E.164 address can have 8-15 decimal digits.

The number of bits or bytes in the ATM address effects the uniqueness of the address. The longest address ensures total uniqueness of the address. With a one-byte address, any caller that sends an address whose first address byte matches that one-byte ATM address goes to that port.

length

Determines the address length. The units of measure differ for each address plan. The -plan option lets you specify E.164 or NSAP.

For NSAP address, this entry represents the length in bits by using the maximum of a 20-byte address: 20 bytes x 8 bits per byte = 160 bits.

Range: 1-160

For an E.164 address plan, the value is the number of decimal digits. If the ATM address consists of 15 digits, the value for this parameter is also 15.

-plan

Determines the address plan for either E.164 or NSAP.

For NSAP address, the first byte of the address automatically implies one of three NSAP address plans: NSAP E.164, NSAP DCC, or NSAP ICD.

Default: nsap


Related Commands

addaddr, deladdrs, dspaddr

Attributes

Access level: GROUP1

State: active

Log: log


Example

On port 12..2 , delete 47.1111.1111.1111.1111.1111.1111.1111.1111.1111.11 160. Note that the command entry includes the address length of 160 after the address.


SES_SJ.1.PXM.a > deladdr 12.2 47.1111.1111.1111.1111.1111.1111.1111.1111.1111.11 160

deladdrs

Delete ATM Addresses—PXM1

Use the deladdrs command to delete all ATM addresses on a specified port. The deladdrs command removes all ATM addresses on a UNI, AINI, or IISP. The optional plan parameter lets you differentiate by the address plan for the following:

E164

NSAP

All address plans (the default)

Syntax

deladdrs <portid> [-plan {e164 | nsap | all}]

Syntax Description

portid

Identifies a PNNI physical port. The format is slot:subslot.port:subport.

-plan

Determines the address plan for the following:

E.164

NSAP

all

Default: all


Related Commands

addaddr, deladdr, dspaddr

Attributes

Access level: GROUP1

State: active

Log: log


Example

Delete all the addresses (regardless of address plan) for port 12.2

SES_SJ.1.PXM.a > deladdrs 12.2
This command will delete all the addresses of the port
deladdrs: Do you want to proceed (YesNo)? y

SES_SJ.1.PXM.a > 

delapsln

Delete APS Line—PXM1

Use the delapsln command to delete APS from a line on the PXM card.

Syntax

delapsln <line>

Syntax Description

line

Specifies the working line number. Enter the value 1.


Related Commands

addapsln, cnfapsln, dspapsln

Attributes

Access level: SUPER_GP

State: active

Log: log


Example

Delete the APS configuration for working line number 1.

spirita.1.PXM.a > delapsln 1 

delcon

Delete Connection—PXM1

Use the delcon command to delete a configured endpoint. Delete the master first and then the slave.

Syntax

delcon <portid> <vpi> <vci>

Syntax Description

portid

Interface number.

vpi

VPI assigned to the endpoint.

Range: 1-255 (UNI interface)

Range: 0-4095 (NNI interface)

vci

VCI assigned to the endpoint.

Range: 32-65535 (VCC connection)

Range: 0 (VPC connection)


Related Commands

addcon, cnfcon, dncon, rrtcon, upcon

Attributes

Access level: GROUP1

State: active

Log: log


Example

Delete a configured connection with the applicable default settings.

spirita.1.PXM.a > delcon 0.1.1 1 100 

Deletion successful

spirita.1.PXM.a >

delconsegep

Delete Connection Segment Endpoint—PXM1

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

Syntax

delconsegep <portid> <vpi> [<vci>]

Syntax Description

portid

Interface number.

vpi

VPI assigned to the endpoint. For a UNI interface, this parameter can take a value between 1-255. For a NNI interface, this can take a value between 1-4095.

vci

VCI assigned to the endpoint. In case of a VCC connection, this parameter takes a value between 32-65535. For a VPC connection, this parameter is specified as 0.


Related Commands

cnfconsegep

Attributes

Access level: GROUP1

State: active

Log: Log


Example

Delete the connection segment endpoint with the applicable port ID, VP,I and VCI values.

spirita.1.PXM.a > delconsegep 0.1.1 1 100 

spirita.1.PXM.a >

delete

Delete—PXM1

Use the delete command to remove any files on the disk.

Syntax

delete <file name>

Syntax Description

file name

Name of the file to be removed.


Related Commands

deladdr

Attributes

Access level: GROUP1

State: all

Log: log


Example

Delete the applicable files from the disk.

spirita.1.PXM.a > delete any_file

delfltset

Delete Filter Set—PXM1

Use the delfltset command to delete an ATM address filter set. If the index is specified, the address entry in the filter set corresponding to the index is removed. If no index is specified, the filter set and all the address entries contained in it are removed.

Syntax

delfltset <name> [-index number]

Syntax Description

name

Name of the filter set to be deleted.

-index

Index value of the filter to be deleted.

Range: 1-65535

Default: 0


Related Commands

cnffltset

Attributes

Access level: GROUP1

State: active

Log: log


Example

Consider a filter "firstfilter" created via the addfltset command. This filter can be deleted using the delfltset command as follows:


pnnises1.1.PXM.a > delfltset firstfilter

dellmiloop

Delete LMI Loopback—PXM1

Use the dellmiloop command to remove LMI loopback state for a line.


Note You can activate only one PXM line on the feeder implementation of an SES node.


Syntax

dellmiloop <slot.port>

Syntax Description

slot

Specifies the slot number.

Range: 1-32

port

Specifies the port number.

Range: 1-256


Related Commands

addlmiloop

Attributes

Access level: SUPER_GP

State: active

Log: no


Example

Delete the LMI loopback line from the current PXM.

spirit11.1.1.PXM.a > dellmiloop 1.6

delpnni-node

Delete a PNNI Node—PXM1

Use the delpnni-node command to delete a PNNI node from the PNNI network topology. The delpnni-node command removes a PNNI node from the PNNI network topology. A node that this command deletes can be restored with the related addpnni-node command. Confirm the deletion of nodes with the dsppnni-node command.

Syntax

delpnni-node <node-index>

Syntax Description

node-index

The node index indicates the relative level of the logical node within a multi-peer group on the switch.

Range: 1-10


Related Commands

cnfpnni-node, dsppnni-node

Attributes

Access level: SUPER_GP

State: active

Log: log


Example

Delete the node with the node-index 3.

SES_SJ.1.PXM.a > delpnni-node 3

Example

Enter the dsppnni-node command and specify a node-index of 3. The last line of the d display states the error node does not exist, which indicates that you successfully deleted the node.

SES_SJ.1.PXM.a > dsppnni-node 3

Syntax: dsppnni-node [node-index]

        nodeIndex -- node-index: 32-bit number starting from 1, Optional parameter

        possible errors are:
node does not exist


SES_SJ.1.PXM.a > 
   Unknown Error Code

delpnni-summary-addr

Delete PNNI Summary Address—PXM1

Use the delpnni-summary-addr command to remove a PNNI summary address from the node. The delpnni-summary-addr command deletes a PNNI summary address for a PNNI node.

Syntax

delpnni-summary-addr <node-index> <address-prefix> <prefix-length>

Syntax Description

node-index

The node index indicates the relative level of the logical node within a multi-peer group on the switch is 1.

Range: 1-10

address-prefix

ATM address prefix assigned to the local switching system.

Default: none

prefix-length

Length of the address-prefix, in number of bits, equal to or less than 152 bits.

Note Zero-length summary address is not currently supported.

Default: none


Related Commands

addpnni-summary-addr, dsppnni-summary-addr

Attributes

Access level: SUPER_GP

State: active

Log: log


Example

Delete a summary address as follows:

The node-index is 1.

The node address prefix is 47.0091.8100.0000.0030.9409.f1f1.

The length of the address prefix is 104 bits.

If necessary, enter the dsppnni-summary-addr command to confirm the deletion.

SES_SJ.1.PXM.a > delpnni-summary-addr 1 47.0091.8100.0000.0030.9409.f1f1 104
SES_SJ.1.PXM.a > 

delpnport

Delete PNNI Port—PXM1

Use the delpnport command to remove a specified UNI or NNI port. This command is used to remove a port from the controller. It is allowed only if the PNNI port does not exist on the switch, for example, the PNNI partition associated with the port is removed. In the plug and play scenario, if no provisioning activity is done on the port from the controller, removing the PNNI partition on the switch will automatically remove the PNNI port on the controller.

Syntax

delpnport <portid>

Syntax Description

portid

Specifies the interface number.


Related Commands

addpnport, dnpnport, dsppnport, uppnport

Attributes

Access level: GROUP1

State: active

Log: log


Example

Delete port 1.6 from the switch.

spirita.1.PXM.a > delpnport 1.6

spirita.1.PXM.a >

delpnportacc

Delete PNNI Port Access—PXM1

Use the delpnportacc command to delete an address access filter group for a port.

Syntax

delpnportacc <portid> {in | out}

Syntax Description

portid

Interface number.

in

Delete the incoming address access filter group for the port.

Default: 1

out

Delete the outgoing address access filter group for the port.

Default: 1


Related Commands

cnfpnportacc

Attributes

Access level: GROUP1

State: active

Log: log


Example

Delete the filter group for incoming calls from port 1.6.

SES_SJ.1.PXM.a > delpnportacc 1.6 in

SES_SJ.1.PXM.a >

delpref

Delete Preferred Route—PXM1

Use the delpref command to delete a preferred route description from the preferred route database. Only if no SPVCs are currently using a preferred route, is the preferred route deleted.

Syntax

delpref <routeId>

Syntax Description

routeId

Specifies a number that uniquely identifies the route location within the database.

Range: 1-1000


Related Commands

addpref, cnfconpref, dsppref, dspprefs, modpref

Attributes

Access level: GROUP1

State: active

Log: log


Example

Remove a preferred route description 10.

SES_SJ.1.PXM.a > delpref 10

SES_SJ.1.PXM.a >

delprfx

Delete Prefix—PXM1

Use the delprfx command to remove an ILMI address prefix associated with UNI, IISP, or AINI.

Syntax

delprfx <portid> <atm-prefix>

Syntax Description

portid

Interface number.

atm-prefix

A 13-byte ATM address prefix, specified as 26 hexadecimal digits.


Related Commands

addprfx, dspprfx

Attributes

Access level: GROUP1

State: active

Log: log


Example

Delete ATM prefix 47.0091.8100.0000.0000.0ca7.9e01 from PNNI physical port 0:1.5:1.


SES_SJ.1.PXM.a > delprfx 0:1.5:1 47.0091.8100.0000.0000.0ca7.9e01
SES_SJ.1.PXM.a >

delserialif

Delete Serial Interface—PXM1

Use the delserialif command to delete a serial interface.

Syntax

delserialif <port#>

Syntax Description

port#

Indicates the type of port you want to add. Enter 1 to delete a maintenance port. Enter 2 to delete a console port.


Related Commands

cnfserialif, dspserialif

Attributes

Access level: superuser

State: active

Log: yes


Example

Delete a maintenance port.

SES_SJ.1.PXM.a > delserialif 1

Example

Verify the settings by entering the dspserialif command.

SES_SJ.1.PXM.a > dspserialif 1
  SerialPortNum   : 1
  SerialPortType  : maintenance
  SerialPortSpeed : 19200

SES_SJ.1.PXM.a >

delsesn

Delete Session—PXM1

Use the delsesn command to ungracefully delete a user-session. The delsesn command lets you terminate one or more user-sessions. Termination takes place immediately upon command execution. Each user receives a message that their session is being terminated by a foreign host.

To determine the number of the session, use the who command. The session number appears as a number appended to the session type in the who display. The session types are console and telnet.

Syntax

delsesn <sesn no> <sesn no>...

Syntax Description

sesn no

Specifies the number of the session in the range of 0-15. The who command or the dspsesn command can provide the user-session numbers. The dspsesn command output is more conducive for the delsesn command.

Note The session number that the who command displays is a hexadecimal number.

For the delsesn command, enter it in decimal format. For example, if the session that the who command displays is telnet.0a, enter 10 for the delsesn command.


Related Commands

dspsesn, who

Attributes

Access level: SERVICE_GP

State: all

Log: log


Example

Determine the existing user-sessions. For comparison, first run the who command then the dspsesn command. (The privilege level for who is ANYUSER, and the privilege level for the dspsesn command is SERVICE_GP.) Compare the output of each command.


Note The dspsesn command output provides a form of the user-session number that is a requirement for the delsesn command.


The asterisk indicates that the session where the who and dspsesn commands originated. The only session in this case is 1. Delete session 1 (user cisco), then repeat the dspsesn command.

SES_SJ.1.PXM.a > who

    Port        Slot      Idle       UserId       From
    -------------------------------------------------------------
    telnet.01 *    1     0:00:00     cisco        10.21.66.169

SES_SJ.1.PXM.a > dspsesn

-----------------------------------------
 > Session 0 (console): 
Waiting for login...

-----------------------------------------
*> Session 1 (telnet): 
Executing command: dspsesn

user name:         cisco
access level:      CISCO_GP
slot:              1
slotFallback:      1
From:              10.21.66.169

SES_SJ.1.PXM.a > delsesn 1
WARNING! delsesn is a destructive command it will 
non-gracefully delete sessions selected by you 
Do you wish to proceed ? [y/n] n

delsigdiag

Delete Signaling Diagnostic—PXM1

Use the delsigdiag command to remove a signaling diagnostics filter table entry or some configuration values within a filter table entry.

Syntax

delsigdiag [index] [-cldaddr nsap-address] [-clgaddr nsap-address] [-cldaddrmask {yes | no}]
[-clgaddrmask {yes | no}] [-casttype {yes | no}] [-clrcause {yes | no}] [-connctgy {yes | no}]
[-inport {yes | no}] [-outport {yes | no}] [-maxrec {yes | no}] [-scope {yes | no}]
[-servctgy {yes | no}] [-agetimeout {yes | no}]

Syntax Description

index

Specifies the diagnostics index number for the filter table. If no other keywords are entered, the indexed filter table entry is deleted.

Range: 1-50

-cldaddr

Removes the configured called address from the filter entry in NSAP format.

Default: NULL

-clgaddr

Removes the configured calling address from the filter entry in NSAP format.

Default: NULL

-cldaddrmask

yes returns the called address mask to the default NULL.

Default: no

-clgaddrmask

yes returns the calling address mask to the default NULL.

Default: no

-casttype

yes disables the filtering by connection type.

Default: no

-clrcause

yes disables the filtering by the release cause code.

Default: no

-connctgy

yes returns the connection category to the default ALL.

Default: no

-inport

yes returns the incoming port to the default value 0.

Default: no

-outport

yes returns the outgoing port to the default value 0.

Default: no

-maxrec

yes returns the maximum records to default value 20.

Default: no

-scope

yes disables the filtering by scope.

Default: no

-servctgy

yes returns the service category to the default ALL.

Default: no

-agetimeout

yes returns the agetimeout to default 600.

Default: no


Related Commands

clrsigstats, cnfsigdiag, dspsigstats

Attributes

Access level: SERVICE_GP

State: active

Log: log


Example

Delete index entry 12 in the signaling diagnostics filter table.

SES_SJ.1.PXM.a > delsigdiag 12

SES_SJ.1.PXM.a >

Change index entry 12 in the signaling diagnostics filter table so that the -clrcause parameter value is changed to no.

SES_SJ.1.PXM.a > delsigdiag 12 -clrcause no

SES_SJ.1.PXM.a >

deltrapmgr

Delete Trap Manager—PXM1

Use the deltrapmgr command to delete a trap manager. The deltrapmgr command requires an IP address for deletion. To see existing trap managers, enter the dsptrapmgr command.

Syntax

deltrapmgr <ip_addr>

Syntax Description

ip_addr

IP address in the following dotted decimal format:

nnn.nnn.nnn.nnn, n=0-9 and nnn =< 256


Related Commands

addtrapmgr, cnfsnmp, dspsnmp, dsptrapmgr

Attributes

Access level: SUPER_GP

State: active

Log: log


Example

Delete the trap manager with IP address 172.29.52.25.

SES_SJ.1.PXM.a > deltrapmgr 172.29.52.25

Example

Verify that the trap manager with IP address 172.29.52.25 is deleted by entering the dsptrapmgr command.

SES_SJ.1.PXM.a > dsptrapmgr
    Shelf Database table empty.trapsConfig.trapConfigTable

  LastTrapSeqNum:     1078
  NumOfValidEntries:  0

SES_SJ.1.PXM.a >

deluser

Delete User—PXM1

Use the deluser command to remove a user from the list of users on the SES node. The system does not allow you to delete a user with a privilege level higher than the level at which you enter the command. For example, if the current user privilege is 2 (GROUP2), you cannot delete a user at level 1 (GROUP1). No screen output appears unless an error occurs.

Syntax

deluser <user_Id>

Syntax Description

user_Id

User name, consisting of up to 12 characters.


Related Commands

bootChange, cnfuser, dspusers, users

Attributes

Access level: GROUP1

State: active

Log: log


Example

Delete a user from the list.

spirita.1.PXM.a > deluser myname

disablesscop

Disable SSCOP—PXM1

Use the disablesscop command to enable or disable SSCOP on a port. This command is used only when a port is administratively down (by the dnpnport command).


Note Make sure a valid and useful reason exists for disabling SSCOP.


Syntax

disablesscop <portid> {yes | no}

Syntax Description

portid

Interface number.

yes | no

Disables or enables SSCOP on a port with the following options.

yes: disables SSCOP

no: enables SSCOP

Note Do not disable SSCOP on a port.

Default: no (enable SSCOP on the specified port)


Related Commands

clrsscopstats, dspsscop, dspsscopstats

Attributes

Access level: GROUP1

State: active

Log: log


Example

Disable SSCOP on a port 1.6.

spirita.1.PXM.a > dnpnport 1.6
spirita.1.PXM.a > disablesscop 1.6 yes

spirita.1.PXM.a >

Example

Enable SSCOP on a port 2.3.

spirita.1.PXM.a > dnpnport 2.3
spirita.1.PXM.a > disablesscop 2.3 no

spirita.1.PXM.a >

dncon

Down Connection—PXM1

Use the dncon command to down a connection. If the connection is routed, it is derouted. The dncon command administratively deactivates (or "downs") so you can modify or troubleshoot the network. This operation applies to only SPVCs. To reactivate the connection, enter the upcon command.

Syntax

dncon <portid> <vpi> <vci>

Syntax Description

portid

Specifies the interface number.

Range: 1-60

vpi

Specifies that the starting VPI is to view active calls starting from the specified VPI of the specified port. This parameter is used only if the port is specified.

Range: 0-4095

vci

Specifies that the starting VCI is to view active calls starting from the specified VPI/VCI of the specified port. This parameter is used only if the VPI is specified.

Range: 32-65535


Related Commands

addcon, cnfcon, delcon, upcon

Attributes

Access level: GROUP1

State: active

Log: log


Example

Down a connection on a port. Set the starting VPI to 1. Set the starting VCI to 100.

spirita.1.PXM.a > dncon 2.3 1 100
Admin state of connection is DOWN

dnpnport

Down PNNI Port—PXM1

Use the dnpnport command to take a specified UNI or NNI port out of service on the controller (administratively "down" on the controller). This command is used to bring a port out of service for provisioning and maintenance activity. For example, the port needs to be down to change some of the port configuration parameters, which are affecting service.


Note The dnpnport command deletes all connections on a port—except for SPVCs whose endpoints are on the port.


Syntax

dnpnport <portid>

Syntax Description

portid

Interface number.


Related Commands

addpnport, delpnport, dsppnport, uppnport

Attributes

Access level: GROUP1

State: active

Log: log


Example

Down a PNNI port with the applicable port ID for either UNI or NNI.

spirita.1.PXM.a > dnpnport 2.3

spirita.1.PXM.a >

downloadflash

Download Flash—PXM1

Use the downloadflash command to load the first boot code found by the PXM1 hard drive into flash memory. The downloadflash command does not execute at the runtime prompt. It operates in bootmode only.

A downloadflash session concludes the sequence of tasks for performing a PXM1 boot code load. Prior to entering this command, you must access the boot code and transfer the file to the PXM1 hard drive by entering a put command). Arguments within the put command let you load boot code to any combination of standby or active PXM1s. Once firmware is installed in slot 1, the bootcode is mirrored to a new PXM1 in slot 2 if present.

However, to ensure that the boot code is correct, enter the downloadflash command as a manual way to download the boot code to the standby PXM1.


Note Make sure only one version of backup boot code resides in the firmware directory: either delete or rename old versions to ensure that downloadflash uses the correct version.


Syntax

downloadflash

Syntax Description

None

Related Commands

None

Attributes

Access level: SERVICE_GP

State: any

Log: no


Example

SES_SJ.1.PXM.a > downloadflash
Error: flash_file supported only at backup boot

SES_SJ.1.PXM.a > 
> ftp <switch_dest_addr>

> bin

> put <pxm_bkup_version>.fw PINNACLE@PXM45.BT

> quit

wilco.7.PXM.a > downloadflash

 

     To place the boot code on the active PXM45 only, use the following "put" string:
     >put pxm_bkup_version>.fw PINNACLE@PXM45_ACTIVE.BT

     To place the boot code on the standby PXM45 only, use the following "put" string:
     >put pxm_bkup_version>.fw PINNACLE@PXM45_STANDBY.BT

dspabrtparmdft

Display ABR Traffic Parameter Defaults—PXM1

Use the dspabrtparmdft command to display default ABR traffic parameters used by a port to set up ABR SPVCs.

Syntax

dspabrtparmdft <portid>

Syntax Description

portid

Specifies the port to be configured.


Related Commands

cnfabrtparmdft

Attributes

Access level: ANYUSER

State: any

Log: no


Example

Display the applicable default ABR traffic parameters for port 2.3.

SES_SJ.1.PXM.a > dspabrtparmdft 2.3

Default ABR Traffic Parameters For: 2:-1.3:-1           
-----------------------------------
RIF : 7 (= 1/512)
RDF : 4 (= 1/4096)
TBE : 1048320 (Cells)
NRM : 5 (= 32 Cells)
TRM : 8 (= 100 msec)
ADTF: 50 (= 0.50 Sec)
CDF : 7 (= 1/2)
FSD : 0 (microSec)

SES_SJ.1.PXM.a >

dspaddr

Display Address—PXM1

Use the dspaddr command to view ATM addresses and associated information, such as address plan and scope for UNI or IISP.

The following items are in the display:

ATM addresses on the port and the length of each

Address plan

Type of address—internal or external

Protocol for advertising the address

Choice for address distribution

ID number of transit node

Scope—applicable to multi-peer groups only

Syntax

dspaddr <portid>

Syntax Description

portid

Specifies the port to be configured.


Related Commands

addaddr, deladdr

Attributes

Access level: ANYUSER

State: any

Log: no


Example

Display the ATM addresses for the applicable port ID.

SES_SJ.1.PXM.a > dspaddr 2.3
45.0073.1300.0000.1010.1010.1010.0000.0000.0001.00
length: 160    type: internal      proto: local
scope: 0       plan: nsap_e164     redistribute: false
transit network id: 


SES_SJ.1.PXM.a >

dspainihopcount

Display AINI Hop Count—PXM1

Use the dspainihopcount command to enable or disable the status and the limit for the number of hops a connection can have over AINI links. The counter is the Hop Counter Information Element. This configuration applies to the entire node.

Syntax

dspainihopcount

Syntax Description

None

Related Commands

cnfainihopcount

Attributes

Access level: ANYUSER

State: any

Log: log


Example

Display the current configuration for AINI hop count.

SES_SJ.1.PXM.a > dspainihopcount
AINI Hop Counter Generation: enable
Max AINI Hops: 20


SES_SJ.1.PXM.a >

dspapscfg

Display APS Configuration—PXM1

Use the dspapscfg command to view APS configuration information.

Syntax

dspapscfg

Syntax Description

None

Related Commands

cnfapsln, delapsln, dspapsln, switchapsln

Attributes

Access level: ANYUSER

State: any

Log: no


Example

Display the configuration for APS.

spirita.1.PXM.a > dspapscfg
 SlotLine  Type   SFBER  SDBER  WTR  Dir  Revert  K1K2
 -----------------------------------------------------
 1.1&2.1   1+1_2  3      5      1    UNI  NRV     ENA

dspapsln

Display APS Line—PXM1

Use the dspapsln command to view the current APS line parameters on the PXM card. This command is entered for either a working line or a protection line.

Syntax

dspapsln

Syntax Description

None

Related Commands

addapsln, cnfapsln, delapsln, switchapsln

Attributes

Access level: any

State: any

Log: no


Example

Display the current APS configuration for the PXM lines.

spirita.1.PXM.a > dspapsln
 SlotLine Type  Act W_LINE P_LINE APS_ST CDType Dir  Revt LastUsrSwReq
------------------------------------------------------------------------
 1.1&2.1  1+1_2 2.1 ALM    YEL    OK     OC-3   UNI  NRV  NO_REQUEST

dspatmaddr

Display ATM Address—PXM1

Use the dspatmaddr command to view all active ATM addresses for a port. The output includes configured ATM addresses, configured ILMI address prefixes, and ATM addresses registered through an ILMI address registration procedure.

Syntax

dspatmaddr <portid>

Syntax Description

portid

Specifies the port to be configured.


Related Commands

addaddr, deladdr, dspaddr

Attributes

Access level: ANYUSER

State: any

Log: no


Example

Display the active ATM addresses for the applicable port ID.

spirita.1.PXM.a > dspatmaddr 0.1.2

Port Id: 2.1
Configured Port Address(es):
	 39.8401.8011.3744.0000.0040.1005.3456.7834.7777.77
 	88.8888.8888.0000.0000.0000.0000.0000.0000.5151.00
 
ILMI Configured Port Prefix(es):
 	47.0091.8100.0000.0000.0ca7.9e01
 	88.8888.8888.0000.0000.0000.0000
 
ILMI Registered Port Address(es):
	47.0091.8100.0000.0000.0ca7.9e01.1234.5678.9012.34
 	88.8888.8888.0000.0000.0000.0000.1234.5678.9012.34

LECS Address(es):
 	47.0091.8100.0000.0000.0ca7.9e01.4000.0c81.9030.01
 	47.0091.8100.0000.0000.0ca7.9e01.4000.0c81.9030.02

spirita.1.PXM.a >

dspbecnt

Display Bit-Error Count—PXM1

Use the dspbecnt command to view the APS bit-error information for a generic line.

Syntax

dspbecnt <line>

Syntax Description

line

Working line number. Enter the value 1.


Related Commands

clrbecnt

Attributes

Access level: superuser

State: active

Log: no


Example

Display the APS bit-error information for the applicable line.

mpgses1.1.PXM.a > dspbecnt 1
Line 1.1:
    24 Hour   Bit Error Count 0
    15 Minute Bit Error Count 0
    15 Second Bit Error Count 0
Line 2.1:
    24 Hour   Bit Error Count 0
    15 Minute Bit Error Count 38
    15 Second Bit Error Count 0


dspbkpl

Display Backplane—PXM1

Use the dspbkpl command to display the switch backplane information.

The following types of information are for the backplane:

Card type (a hexadecimal number)

Chassis-level part number and revision number

PCB 73-level part number

Chassis serial number

CLEI code

PCB 28-level part number

Syntax

dspbkpl

Syntax Description

None

Related Commands

None

Attributes

Access level: ANYUSER

State: any

Log: no


Example

Display the information for the switch backplane.

SES_SJ.1.PXM.a > dspbkpl


BackPlane Information
---------------------

Card Type:                     0x145
Chassis 800-level P/N:         800-04793-05
Chassis 800-level rev:         A0
PCB 73-level P/N:              73-3349-04
Chassis serial number:         SCA050209X1
CLEI CODE:                     BAM8MNOBRB
PCB 28-level P/N:              28-2687-04

SES_SJ.1.PXM.a >

dspcbclk

Display Cellbus Clock—PXM1

Use the dspcbclk command to display clock speed for individual cellbuses.

The following functions are for the dspcbclk command:

Cellbuses support only the default clock rate of 21 MHz and either support 21 Mhz or 42 Mhz rates.

Individual cellbus is running at the standard rate of 21 MHz or the double-speed rate of 42 Mhz.

Card slots that reside on each of the eight cellbuses.

Syntax

dspcbclk

Syntax Description

None

Related Commands

cnfcbclk

Attributes

Access level: ANYUSER

State: any

Log: no


Example

Display the current cellbus clock configuration. The display shows that all cellbuses currently have the default speed of 21 Mhz.

SES_SJ.1.PXM.a > dspcbclk

     CellBus    Rate (MHz)    Slots     Allowable Rates (MHz)
    ----------------------------------------------------------
       CB1         21        3               21, 42
       CB2         21        5               21, 42
       CB3         21        10              21, 42
       CB4         21        12              21, 42
       CB5         21        11              21, 42
       CB6         21        6, 7            21, 42
       CB7         21        4               21, 42
       CB8         21        13, 14          21, 42

SES_SJ.1.PXM.a >

dspcd

Display Card—PXM1

Use the dspcd command to view the hardware and firmware information about the selected PXM.

The following information is listed in the display contents:

Serial numbers.

Front and back card types and the status of each.

Runtime and boot firmware revision numbers. (See the loadrev command description for an explanation of how to interpret the revision field.)

Status, possibly including the reason for the last reset and state of the integrated alarm.

General node information, such as node name, date, and time.

Crossbar status.

Current version of firmware.

Syntax

dspcd <slot>

Syntax Description

slot

Slot number of the installed PXM. Enter either 1 or 2.


Related Commands

dspcds, dspcdstatus

Attributes

Access level: ANYUSER

State: all

Log: no


Example

The System Rev field contains 03.00. The 0s are leading 0s only. Therefore, the major release number is 3, and the minor release number is 1. This information corresponds to the major and minor release numbers in the primary, secondary, and current software revision numbers (the fields labeled Prim SW Rev:, Sec SW Rev:, and Cur SW Rev:).

Display the card information for the slot number 1.

SES_SJ.1.PXM.a > dspcd 1
SES_SJ                           System Rev: 03.00   Jan. 31, 2002 22:40:01 GMT
SES-CNTL                                             Node Alarm: NONE
Slot Number    1    Redundant Slot:  2

                    Front Card          Upper Card          Lower Card
                    ----------          ----------          ----------

Inserted Card:      PXM1_OC3            UIA BackCard        SMFIR_4_OC3        
Reserved Card:      PXM1_OC3            UIA BackCard        SMFIR_4_OC3        
State:              Active              Active              Active         
Serial Number:      SBK043200VK         SBK041200W7         SBK05070188 
Prim SW Rev:        3.0(0.171)P3        ---                 ---
Sec SW Rev:         3.0(0.171)P3        ---                 ---
Cur SW Rev:         3.0(0.171)P3        ---                 ---
Boot FW Rev:        3.0(0.171)P3        ---                 ---
800-level Rev:      B0                  A0                  E1   
800-level Part#:    800-06454-03        800-03688-01        800-05351-01
CLEI Code:          BAA6CCVCAA          BAI9Y00AAA          BA2IKNHBAA 
Reset Reason:       On Reset From Shell
Card Alarm:         NONE                
Failed Reason:      None                
Miscellaneous Information:

Type <CR> to continue, Q<CR> to stop: 
SES_SJ                           System Rev: 03.00   Jan. 31, 2002 22:40:01 GMT
SES-CNTL                                             Node Alarm: NONE

Crossbar Slot Status:      No Crossbar

Alarm Causes
------------
    NO ALARMS                 

SES_SJ.1.PXM.a > 

dspcdalms

Display Card Alarms—PXM1

Use the dspcdalms command to view the summary of node card alarms. This includes line alarms, port alarms, and channel alarms.

The following are the definitions of each alarm severity from Bellcore TR-NWT-000474:

Critical, indicating complete, non-recoverable failure, loss of data, and do on. The failed entity must be restored. A power failure or a disconnected line is an example.

Major, indicating service-affecting errors. This event indicates that a major service is damaged or lost, but the existing traffic is not affected.

Minor, indicating non-service affecting errors or errors on a remote node. Corrective action is appropriate to prevent a serious fault from developing. An example is a fan failure, where no subscribers are immediately affected, but calamity could result if the situation persists. Note that an accumulation of lower-level alarms does equal a higher-level alarm.

Frequently, the dspcdalms command follows the higher-level command dspndalms.

Syntax

dspcdalms [slot]

Syntax Description

slot

Identifies a particular slot.


Related Commands

dspcdstatus, dspndalms

Attributes

Access level: ANYUSER

State: active

Log: no


Example

Display card alarms without specifying a slot.

SES_SJ.1.PXM.a > dspcdalms
Card Alarm Summary

Slot  Critical   Major     Minor 
----  --------  -------   -------
 1          0        0         0   
 2          0        1         0   
 3          0        0         0   
 4          0        0         0   
 5          0        0         0   
 6          0        0         0   
 7          0        0         0   

Use dspcdalms <slot> to see more detail.

Example

Display the card alarm for slot 1.

SES_SJ.1.PXM.a > dspcdalms 1
Card Alarm Summary


Alarm Type                     Critical        Major          Minor
----------                     --------       -------        -------
Hardware Alarm                       0             0              0
Card State Alarm                     0             0              0
Disk Alarm                           0             0              0
SRM Alarm                            0             0              0
Line Alarm                           0             0              0
Port Alarm                           0             0              0
LMI Alarm                            0             0              0
Channel Alarm                        0             0              0

SES_SJ.1.PXM.a >

dspcderrs

Display Card Errors—PXM1

Use the dspcderrs command to display information about card errors.

Syntax

dspcderrs

Syntax Description

None

Related Commands

clrerr, dsptrapip, dsperrs

Attributes

Access level: ANYUSER

State: any

Log: no


Example

Display information about the card errors.

spirit11.1.1.PXM.a > dspcderrs

dspcderrs
08/05/95-18:53:05 tRootTask    3 Task failed          : scm 
09/05/95-09:14:08 tRootTask    3 Task failed          : scm  

value = 0 = 0x0
spirit11.1.1.PXM.a >

dspcds

Display Card Status—PXM1

Use the dspcds command to view status of all installed cards in the SES PNNI Controller. The dspcds command also displays high-level information for all the cards in the node.

The following contents are provided in the dspcds command:

Revision level of the boot firmware

Revision level of the system software

Date and time of command execution, including GMT offset

Backplane serial number and its hardware revision level

IP address of the statistics master (a workstation)

Type of card in the front and back slots and the (active/standby) state of each

Alarm status for each card and the shelf itself

Redundancy configuration for each slot

Syntax

dspcds

Syntax Description

None

Related Commands

dspcd

Attributes

Access level: ANYUSER

State: all

Log: no


Example

Display the card status for all the cards.

SES_SJ.1.PXM.a > dspcds
SES_SJ                           System Rev: 03.00   Jan. 31, 2002 22:50:38 GMT
Chassis Serial No:   SCA050209X1 Chassis Rev: A0     GMT Offset: 4
                                                     Node Alarm: NONE
Card  Front/Back          Card           Alarm      Redundant   Redundancy     
Slot  Card State          Type           Status     Slot        Type   
---   ----------          --------       --------   -------     -----  



01    Active/Active       PXM1_OC3       NONE       02          PRIMARY SLOT
02    Empty Resvd/Empty   ---            NONE       01          SECONDARY SLOT
03    Empty               ---            ---        ---         ---    
04    Empty               ---            ---        ---         ---    
05    Empty               ---            ---        ---         ---    
06    Empty               ---            ---        ---         ---    
07    Empty               ---            ---        ---         ---    

SES_SJ.1.PXM.a > 

dspcdstatus

Display Card Status—PXM1

Use the dspcdstatus command to view the status of the card alarms. The dspcdstatus command displays the most serious alarms reported by a service module.

The following pertains to alarm information:

Lines

Ports

Connections

Feeders

Severity of each alarm

You can enter the dspcdstatus command to isolate the alarm source if, for example, you see that a Critical Alarm LED is lit or just want to check the node for alarms. You can subsequently use other alarm commands to locate the problem.

The following are the commands related to the dspcdstatus command:

The dspndalms command displays various types of alarms on the node from a high-level perspective. With the information in the dspndalms display, you can select one of the other commands to investigate the alarm further.

The dspcdalms command identifies line, port, feeder, or connection alarms.

The dspclkalms command shows alarms related to network clocks.

The dspenvalms command lists alarms for out-of-range conditions for temperature, voltage sources, and so forth.

The dspswalms command shows alarms related to the switching hardware on PXM1.

The alarm monitoring function on PXM1 uses two criteria to determine which alarm to display. One criterion is alarm severity, and the other is hierarchy. For more information about the alarm severity definitions, see the dspcdalms command.

Two hierarchies of alarm types are card alarms and node alarms. For a list of alarm categories, see Figure 3-2.

Figure 3-2 Alarm Type Hierarchy

The alarm monitoring function reports the highest status alarm after it sorts the current alarms first by severity then by hierarchy. If alarms of equal severity exit in both hierarchies, the system reports the node alarm as the highest status alarm. For example, if a major alarm exists on a line and a major power alarm exists, the dspcdstatus command displays the power alarm as the highest status alarm.

Syntax

dspcdstatus <slot_number>

Syntax Description

slot_number

Command delineator that precedes the slot number entry.


Related Commands

dspcdalms, dspenvalms, dspndalms, dspswalms

Attributes

Access level: ANYUSER

State: active

Log: no


Example

Display the card alarm status for slot 1.

spirita.1.PXM.a > dspcdstatus
Defaulting to logical slot   1.

Logical Slot   1    Physical Slot   1

Card Alarm Status - Type LINE              Severity CRITICAL

dspcdvtdft

Display CDVT Default—PXM1

Use the dspcdvtdft command to view the default cell delay variation tolerance (CDVT) set for a specified port.

Syntax

dspcdvtdft <portid>

Syntax Description

portid

Specifies the port to be configured.


Related Commands

cnfcdvtdft

Attributes

Access level: ANYUSER

State: any

Log: no


Example

Display the CDVT default for port 2.3.

SES_SJ.1.PXM.a > dspcdvtdft 2.3

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

SES_SJ.1.PXM.a > 

dspclkinfo

Display Clock Information—PXM1

Use the dspclkinfo command to display clock information.

Syntax

dspclkinfo

Syntax Description

None

Related Commands

None

Attributes

Access