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
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
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
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/#
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/#
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
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:
DTL 1:NODE 2::56:160:71:0:145::15:253:232:115:
Port List :no of ports = 1
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
inet on Ethernet (e) : 172.29.37.41:ffffff00
gateway inet (g) : 172.29.37.1
ftp password (pw) (blank = use rsh):superuser
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.
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.
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.
Example
Verify the current directory by entering the pwd command.
Example
Go back to the root directory.
Example
Verify the result by entering the pwd command.
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.
---------------------------------------------------
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
Do you want to proceed (Yes/No)? n
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
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
24 Hour Bit Error Count 0
15 Minute Bit Error Count 0
15 Second Bit Error Count 0
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
24 Hour Bit Error Count 0
15 Minute Bit Error Count 0
15 Second Bit Error Count 0
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.
All SM's disk config will be deleted, and
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.
Do you want to proceed (Yes/No)? No
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
-----------------------------------------------------------------------------
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
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
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.
Do you want to proceed (Yes/No)? Yes
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
Example
Confirm that no login message exists by using the dsploginmsg command.
SES_SJ.1.PXM.a > dsploginmsg
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
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
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
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
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
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.
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
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)
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
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
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
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
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)
----------------------------------------------------------
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)
----------------------------------------------------------
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
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
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
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.
ERR: Syntax: loadrev <slot> <revision>
slot -- optional; value: 15,16,31,32
revision - revision number. E.g.,
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
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:
|
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:
|
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
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
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 Ip Address : 0.0.0.0
ILMI Link State : Disable
INFO: No Prefix registered
INFO: No ilmi address registered
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
unackedStatEnqLo 40 messages
unackedStatEnqHi 100 messages
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
unackedStatEnqLo 50 messages
unackedStatEnqHi 60 messages
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
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)}
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
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 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
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:
#Svcc: #Svpc: #Ctrl: Total:
Type <CR> to continue, Q<CR> to stop:
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
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
Example
Verify the results by entering the dspmbsdft command for port 2.3.
SES_SJ.1.PXM.a > dspmbsdft 2.3
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
Example
Verify the results by entering the dspmbsdft command for port 2.3.
SES_SJ.1.PXM.a > dspmbsdft 2.3
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.
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)
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
=================================
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
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
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
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
Example
Configure a port 2.3 so it is not a segment endpoint.
SES_SJ.1.PXM.a > cnfoamsegep 2.3 no
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
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
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
service category : sig PCR : 906
vc type = sscop Parameter = Provisioned
service category : sig PCR : Not Provisioned
SCR : Not Provisioned MBS : 100
SES_SJ.1.PXM.a > uppnport 2.3
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
SES_SJ.1.PXM.a > dsppnni-election
PGL state...... AwaitUnanimity Init time(sec)....... 10
Priority....... 15 Override delay(sec).. 20
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
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
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
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
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
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
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
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: