Table Of Contents
Alphabetical Listing of SES PNNI Controller Commands
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
Attributes
Example
Abort the current configuration process.
SES_SJ.1.PXM.a > abortallsavesNo Save Process runningabortofflinediag
Abort Offline Diagnostics—PXM1
Use the abortofflinediag command to abort the current offline diagnostics.
Syntax
abortofflinediag <slot>
Syntax Description
Related Commands
None
Attributes
Example
Abort the offline diagnostics for slot number 1.
SES_SJ.1.PXM.a > abortofflinediag 1abortrev
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
Example
Abort revisions for slot 1.
spirita.1.PXM.a > abortrev 3.0(0.171)one or more card(s) in logical slot will be reset.Do you want to proceed (Yes/No)? n(command not executed)addaddr
Add Address—PXM1
Enter the addaddr command to add or delete an ATM address for a UNI or IISP. This command is also used to configure static routes to reachable addresses.
An ATM address can be provisioned only on a UNI if ILMI address registration is disabled. Provision an ATM address as follows:
•
On UNI ports, type must be internal and proto must be local.
•
Syntax
addaddr <portid> <atm-address> <length> [-type {int | ext}][-proto {local | static}]
[-plan {e164 | nsap}][-scope value][-redst {yes | no}]Syntax Description
Related Commands
deladdr, dspaddr, dsppnallgrpaddr
Attributes
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 nsapExample
Verify the results by entering the dspaddr command.
SES_SJ.1.PXM.a > dspaddr 2.345.0073.1300.0000.1010.1010.1010.0000.0000.0001.00length: 160 type: internal proto: localscope: 0 plan: nsap_e164 redistribute: falsetransit network id:SES_SJ.1.PXM.a >addapsln
Add APS Line—PXM1
Use the addapsln command to set APS on a specified line for a PXM.
Syntax
addapsln <work-line> <work-slot> <prot-line> <prot-slot> <mode>
Syntax Description
Related Commands
cnfapsln, delapsln, dspapsln, switchapsln
Attributes
Example
Enable the APS line pair for the applicable line.
spirita.1.PXM.a > addapsln 1 1 1 2 2addcon
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
Related Commands
cnfcon, delcon, dncon, dspcon, upcon
Attributes
Example
Add a slave endpoint.
spirita.1.PXM.a > addcon 2 11 100 8 sslave endpoint added successfullyslave endpoint id : 4700918100000000107BE92F7B00000103180200.11.100Example
Add a master endpoint.
spirita.1.PXM.a > addcon 2 11 100 8 m -slave 4700918100000000107BE92F7B00000103180200.11.100 -lcpr 1000 -rpcr 1000master endpoint added successfullymaster endpoint id : 4700918100000000107BE92F5100000103180200.11.100addfltset
Add Filter Set—PXM1
Use the addfltset command to add an ATM address filter set.
Note
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
Related Commands
cnffltset, delfltset, dspfltset
Attributes
Example
Add a filter set called "anyname."
spirita.1.PXM.a > addfltset anynameaddlmiloop
Add an LMI Loopback—PXM1
Use the addlmiloop command to add an LMI loopback line to the current card.
Note
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
Attributes
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
Related Commands
cnfpnni-node, delpnni-node, dsppnni-node
Attributes
Example
Add a PNNI node to the applicable ATM address.
spirita.1.PXM.a > addpnni-node 1 -atmAddress 47.00918100000000107b65f260.00107b65f260.01addpnni-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
Related Commands
delpnni-summary-addr, dsppnni-summary-addr
Attributes
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
Related Commands
delpnport, dnpnport, dsppnport
Attributes
Example
Add a UNI or NNI port to the applicable port ID.
spirita.1.PXM.a > addpnport 0.1.1addpref
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:
•
•
Once entered, the system returns the given numeric ID for that preferred route.
Note
Syntax
addpref [-name yes/no] [-h1 {<persNodeIndex>/<portId>}] [-h2 {<persNodeIndex/<portId>}] ...
[-h20 {<persNodeIndex>/<portId>}]Syntax Description
Related Commands
cnfconpref, delpref, dsppref, dspprefs, modpref
Attributes
Example
Check that node indexes 11, 34, 56 and 23 exist in the persistent topology database then, using the persNodeIndex method, configure a preferred route as follows:
addpref -h1 11/1:2.1.9 -h2 34/1:1.1.2 -h3 56/1:2.1.7 -h4 23/#pref Route ID = 2Specify the same route by using node names:
addpref -name yes -h1 altanta/1:2.1.( -h2 newyork/1:1.1.2 -h3 chicago/1:2.1.7 -h4 seattle/#pref route ID = 2addprfx
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
Attributes
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 4700ab0012340000addserialif
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
Example
Add a maintenance port.
spirita.1.PXM.a > addserialif 1Example
Add a serial port.
spirita.1.PXM.a > addserialif 2addtrapmgr
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
Related Commands
Attributes
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 50adduser
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
Related Commands
Attributes
Example
Add a user with the applicable access levels.
spirit.1.1.PXM.a > adduser fin ANYUSEREnter password:Re-enter password:spirit.1.1.PXM.a >aesa_ping
ATM End System Address Ping—ping any ATM end station connected to a PNNI network.
Use the aesa_ping command to ping an ATM end station address (AESA) based on an ATM address that you provide as a destination address. If you specify only the destination address, the local node merely looks up that address in its routing table. To actually confirm the reachability of another node, specify the optional parameters for setting up a SVC to send and receive keep-alive packets.
Syntax
aesa_ping {destination address} [-setupcall {yes | no}] [-qos {ubr | abr | vbr_rt | vbr_nrt}] [-trace {yes | no}] [-data {yes | no}] [-timeout {time out in secs}] [-interval {time}][-pcr {peak cell rate}] [-scr {sustain cell rate}]
Related Commands
Attributes
Example
Pings the ATM end station with the address 47.00918100000000500ffde873.00500ffde873.01.
spirita.1.PXM.a > aesa_ping 47.00918100000000500ffde873.00500ffde873.01Ping Got CLI message, index=0PING:from PNNI - SOURCE ROUTEDTL 1 :Number of (Node/port)elements 2DTL 1:NODE 1::56:160:71:0:145::238:238:238:238:Port 1:263168DTL 1:NODE 2::56:160:71:0:145::15:253:232:115:Port 2:0Port List :no of ports = 1Port ID 1:263168bootChange
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
Syntax
bootChange
Related Commands
None
Attributes
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 = quitboot device : lnPciprocessor number : 0host name :file name :inet on Ethernet (e) : 172.29.37.41:ffffff00inet on backplane (b):host inet (h) :gateway inet (g) : 172.29.37.1user (u) :ftp password (pw) (blank = use rsh):superuserflags (f) : 0x0target name (tn) :startup script (s) :other (o) :burnboot
Burn Boot—PXM1
Use the burnboot command to burn the boot code onto the PXM card.
Syntax
burnboot <slot> <revision>
Syntax Description
slot
Card slot number for the card to be upgraded, Enter 1 or 2.
revision
Software version number for the update.
Related Commands
None
Attributes
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
Attributes
Example
Exit the current CLI shell.
spirit.1.2.PXM.a > bye(session ended)cc
Change Card—PXM1
Use the cc command to navigate from card to card on the shelf.
Syntax
cc <slotNumber>
Syntax Description
Related Commands
None
Attributes
Example
Change the card to slot number 2.
spirita.1.PXM.a > cc 2cd
Change Directory—PXM1
Use the cd command to change to another directory on the PXM1 hard disk.
Syntax
cd <path name>
Syntax Description
Related Commands
Attributes
Example
Change the directory to FW.
SES_SJ.1.PXM.a > cd FWExample
Verify the current directory by entering the pwd command.
SES_SJ.1.PXM.a > pwdC:FWSES_SJ.1.PXM.a >Example
Go back to the root directory.
SES_SJ.1.PXM.a > cd ..Example
Verify the result by entering the pwd command.
SES_SJ.1.PXM.a > pwdC:SES_SJ.1.PXM.a >clidbxlevel
Command Line Interface Level—PXM1
Use the clidbxlevel command to display the attributes for each command. You must enter the clidbxlevel command on each card where you want to change the level of displayed information. For example, if you enter the clidbxlevel command on PXM1 on slot 1 and want to see the same level of information in slot 2, you must enter the clidbxlevel command for slot 2.
The following are the attributes:
•
•
•
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
Example
Specify level 1 for the CLI.
SES_SJ.1.PXM.a > clidbxlevel 1Value of cliDbxLevel is now 1Example
Enter the help command to view the access levels, card states, and log status for each applicable command.
SES_SJ.1.PXM.a > helpCommand Access Card Log---------------------------------------------------? ANYUSER A|S|I -abortallsaves GROUP1 A +abortofflinediag SERVICE_GP A|S -abortrev SERVICE_GP A|S +clrallcnf
Clear All Configuration—PXM1
Use the clrallcnf command to remove all configuration databases from the shelf, including configuration stored in BRAM by the shelf manager, and other configuration files currently stored on disk.
Warning
Syntax
clrallcnf
Syntax Description
None
Related Commands
clrcnf, restoreallcnf, saveallcnf
Attributes
Example
Clear all the configurations and restart the switch.
spirita.1.PXM.a > clrallcnfAll SM's config will be deleted, andthe shelf will be reset.Do you want to proceed (Yes/No)? n(command not executed)clrbecnt
Clear Bit-Error Count—PXM1
Use the clrbecnt command to remove all the statistics for the automatic protection switching (APS) bit-error counts
Syntax
clrbecnt <line>
Syntax Description
Related Commands
Attributes
Example
First display bit error count, then clear bit error count. Confirm by displaying again.
mpgses1.1.PXM.a > dspbecnt 1Line 1.1:24 Hour Bit Error Count 015 Minute Bit Error Count 015 Second Bit Error Count 0Line 2.1:24 Hour Bit Error Count 015 Minute Bit Error Count 3815 Second Bit Error Count 0mpgses1.1.PXM.a > clrbecnt 1Do you want to clear the bit-error count for line 1.1 [Y/N] ? YesThe bit-error count for line 1.1 is clearedDo you want to clear the bit error count for line 2.1 [Y/N] ? YesThe bit-error count for line 2.1 is clearedmpgses1.1.PXM.a > dspbecnt 1Line 1.1:24 Hour Bit Error Count 015 Minute Bit Error Count 015 Second Bit Error Count 0Line 2.1:24 Hour Bit Error Count 015 Minute Bit Error Count 015 Second Bit Error Count 0clrcnf
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
Example
Clear all card configurations.
spirita.1.PXM.a > clrcnfAll SM's disk config will be deleted, andthe shelf will be reset.clrcnf: Do you want to proceed (Yes/No)? Yclrconstats
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
Related Commands
dspconstats
Attributes
Example
spirita.1.PXM.a > clrconstats 4.1 4000 6000clrdiagerr
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
Related Commands
None
Attributes
Example
Clear all the diagnostic errors for slot 1.
SES_SJ.1.PXM.a > clrdiagerr 1clrdiagstat
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
Related Commands
Attributes
Example
Clear the diagnostic statistics for slot number 1.
SES_SJ.1.PXM.a > clrdiagstat 1clrerr
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
Related Commands
clrerrhist, dsptrapip, dsperrhist
Attributes
Example
Clear the error log files.
wilco.1.1.PXM.a > clrerrDo you want to proceed (Yes/No)? No(command not executed)wilco.1.1.PXM.a >clrerrhist
Clear Error History—PXM1
Use the clrerrhist command to display a log of errors and failures.
Syntax
clrerrhist <slot>
Syntax Description
slot
Number for the slot that contains the card you want to work on. Use this object to clear the log of errors and failures only on a specific slot.
Related Commands
clrerr, dsptrapip, dsperrhist, dsperrs
Attributes
Example
Clear the error history for the applicable slot.
spirit11.1.1.PXM.a > clrerrhist10 0x301f syncRam DB Reset Init from STBY failed 09/07/2000-20:44:25-----------------------------------------------------------------------------spirit11.1.1.PXM.a >clrlmistats
Clear Local Management Interface Statistics—PXM1
Use the clrlmistats command to clear the local management interface (LMI) related statistics on the current PXM.
Syntax
clrlmistats
Syntax Description
None
Related Commands
Attributes
Example
Clear the LMI statistics for PXM.
penguin.1.1.PXM.a > clrlmistatsEnabled : 1 Port Status : 1VPI.VCI : 3.31Polling enable : 1T393 : 10 N394 : 5T394 : 10 N395 : 5WaitStatus : 0 WaitStAck : 0Retry Timer : 0 Retry Count : 1Poll Timer : 6 Trans Num : 86Status Rx : 0 Status Tx : 0UpdtStatus Rx : 0 UpdtStatus Tx : 0Status Enq Rx : 0 Status Enq Tx : 0Status Ack Rx : 0 Status Ack Tx : 0NodeStatus Rx : 0 NodeStatus Tx : 0NodeStaAck Rx : 0 NodeStaAck Tx : 0Bad PDU Rx : 0 Bad PDU Len Rx : 0Unknown PDU Rx : 0 Invalid I.E. Rx: 0Invalid Trans : 0BPX IP Addr : 172.3.3.62penguin.1.1.PXM.a >clrlmitrace
Clear LMI Trace—PXM1
Use the clrlmitrace command to clear LMI trace on the switch.
Syntax
clrlmitrace
Syntax Description
None
Related Commands
None
Attributes
Example
Clear the LMI trace.
spirita.1.PXM.a > clrlmitraceclrlog
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
Attributes
Example
Clear the applicable log files.
wilco.1.1.PXM.a > clrlogDo you want to proceed (Yes/No)? Yeswilco.1.1.PXM.a >clrloginmsg
Clear Login Message—PXM1
Use the clrloginmsg command to delete the message that appears when any user logs into the switch.
Syntax
clrloginmsg
Syntax Description
None
Related Commands
Attributes
Example
Delete the login message.
SES_SJ.1.PXM.a > clrloginmsgLogin message resetExample
Confirm that no login message exists by using the dsploginmsg command.
SES_SJ.1.PXM.a > dsploginmsgSES_SJ.1.PXM.a >clrpathtracebuffer
Clear Path Trace Buffer—PXM45, PXM1E
The clrpathtracebuffer command clears the path trace buffer for an individual connection.
Syntax
clrpathtracebuffer <portid> <vpi> <vci>
Syntax Description
portid
PNNI physical port identifier slot.port
vpi
VPI of the connection.
vci
VCI of the connection.
Related Commands
clrpathtracebuffers, dsppathtracebuffer, dsppathtracebuffers
Attributes
Example
SES_SJ.1.PXM.a > clrpathtracebuffer 1.3 3 100SES_SJ.1.PXM.a >clrpathtracebuffers
Clear Path Trace Buffers—PXM45, PXM1E
The clrpathtracebuffers command clears the path trace buffer for every connection on the switch.
Syntax
clrpathtracebuffers
Syntax Description
This command takes no parameters.
Related Commands
clrpathtracebuffer, dsppathtracebuffer, dsppathtracebuffers
Attributes
Example
SES_SJ.1.PXM.a > clrpathtracebuffersSES_SJ.1.PXM.a >clrpncon
Clear a UNI or NNI Connection—PXM1
Use the clrpncon command to clear a specified call, or all calls within a logical port. This command does not apply to spvc endpoints.
Syntax
clrpncon <portid> [all | vpi] <vci>
Syntax Description
Related Commands
Attributes
Example
For this example, use clrpncon to release the connection on port
1.1 with the VPI/VCI of 100 1000spirita.1.PXM.a > clrpncon 1.1. allor
spirita.1.PXM.a > clrpncon 1.1 100 1000clrpnconstats
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
Related Commands
Attributes
Example
Clear either UNI or NNI connection statistics with the applicable port ID.
spirita.1.PXM.a > clrpnconstats 0.1.1spirita.1.PXM.a >clrqosdefault
Clear Quality of Service Default—PXM1
Use the clrqosdefault command to clear (resets to 0) the defaults for quality of service (QoS values) on the switch. You can clear the defaults for each service type on the switch.
Syntax
clrqosdefault
Syntax Description
None
Related Commands
Attributes
Example
Clear the QoS defaults on the switch. The system does not return a message unless an error occurs.
SES_SJ.1.PXM.a > clrqosdefaultclrscrn
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
Example
Clear the contents of the screen.
flyers01.1.17.AUSM.a > clrscrnflyers01.1.17.AUSM.a >clrsigstats
Clear Signal Statistics—PXM1
Use the clrsigstats command to clear existing signaling statistics for a specific port or all ports.
Syntax
clrsigstats [<portid>]
Syntax Description
portid
If portid is not specified, then signaling statistics for all ports will be cleared. Port ID is in the form of [shelf.]slot[:subslot].port[:subport].
Related Commands
Attributes
Example
Clear the existing signal statistics with the applicable port ID.
spirit11.1.1.PXM.a > clrsigstats 0.1.1Clearing Signaling Statistics for 1.1dspconinfospirit11.1.1.PXM.a >clrsntpstats
Clear SNTP Statistics—PXM1
Use the clrsntpstats command to clear the SNTP statistics.
The recommended procedure is to
1.
2.
3.
Syntax
clrsntpstats
Syntax Description
None
Related Commands
Attributes
Example
orses17.2.PXM.a > clrsntpstatsorses17.2.PXM.a > dspsntpstatsStatistic Counters For SNTP-----------------------------Receive server mode packets from servers in list: 0Receive server mode packets from servers not in list: 0Receive server mode packets which fail sanity check: 0Receive server mode packets which pass sanity check: 0Receive client mode packets: 0Receive other mode packets: 0Send server mode packets: 0Send client mode packets: 0Polling Timer Expire Counter: 0Polling Wait Timer Expire Counter: 0Rollback Timer Expire Counter: 0Rollback Wait Timer Expire Counter: 0Switch From Primary To Secondary Counter: 0Switch From Secondary To Primary Counter: 0Switch From Secondary To Secondary Counter: 0clrspvcnonpers
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
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
Example
Clear the SPVC nonpersistent endpoints for port 2.3 with VPI set to 100.
SES_SJ.1.PXM.a > clrspvcnonpers 2.3 100clrspvcnonpers: clear multiple calls. This might take a while.SES_SJ.1.PXM.a >clrsscopstats
Clear SSCOP Statistics—PXM1
Use the clrsscopstats command to clear existing SSCOP statistics for a specific port or all ports.
Syntax
clrsscopstats [<portid>]
Syntax Description
portid
If portid is not specified, then SSCOP statistics for all ports will be cleared. portid is in the form of [shelf.]slot[:subslot].port[:subport].
Related Commands
disablesscop, dspsscop, dspsscopstats
Attributes
Example
Clear statistics on all ports.
spirit11.1.1.PXM.a > clrsscopstatsspirit11.1.1.PXM.a >Example
Clear statistics on a specified port (0.1.1).
spirit11.1.1.PXM.a > clrsscopstats 0.1.1cmdhistory
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
Attributes
Example
View the last ten commands used for the current card.
spirit4.1.2.PXM.a > cmdhistorySize of cmdHistory is currently 10 line(s)1 dspconcnt 2.39.452 dsplmistats3 dsplmiloop4 dsplm5 clrportcnt6 dspportcnts7 dspportcnt8 dspportcnt 19 dsplmistats10 cmdhistoryspirit4.1.2.PXM.a >cnfabrtparmdft
Configure ABR Traffic Parameters—PXM1
Use the cnfabrtparmdft command to configure default ABR traffic parameters used by a port to set up ABR SPVCs. The traffic parameters are used in the SETUP message at the source when setting up an SPVC for ABR service category.
Syntax
cnfabrtparmdft <portid> [-rif RIF-value] [-rdf RDF-value] [-tbe TBE-value] [-nrm NRM-value] [-trm TRM-value] [-adtf ADTF-value] [-cdf CDF-value][-fsd FSD-value]
Syntax Description
Related Commands
Attributes
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 8cnfaddrreg
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
Example
Configure the address registration with the applicable port ID.
spirita.1.PXM.a > cnfaddreg 0.1.1 nospirita.1.PXM.a >cnfainihopcount
Configure AINI Hop Count—PXM1
Use the cnfainihopcount command to determine the maximum number of ATM Inter-Network Interface (AINI) links that a call can traverse. The specification applies to any call originating on the local node, and the area where the setting applies to the entire network.
The following functions are for the cnfainihopcount command:
•
•
Note
Syntax
cnfainihopcount [-hopcntgen {enable |disable}] [-maxhops <value>]
Syntax Description
Related Commands
Attributes
Example
Enable the AINI hop counting to specify a maximum of 20 hops.
Note
SES_SJ.1.PXM.a > cnfainihopcount -hopcntgen enable -maxhops 20Example
Display the configuration for the AINI hop count.
SES_SJ.1.PXM.a > dspainihopcountAINI Hop Counter Generation: enableMax AINI Hops: 20SES_SJ.1.PXM.a >cnfapsln
Configure APS Line—PXM1
Use the cnfapsln command to set APS parameters for a specified line on the PXM card.
Syntax
cnfapsln <line> <SFBER> <SDBER> <Revertive> <WTR> <Direction> <KIK2>
Syntax Description
Related Commands
addapsln, delapsln, dspapsln, switchapsln
Attributes
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 1flyers01.1.1.PXM.a >cnfautocnf
Configure Auto Configuration—PXM1
Use the cnfautocnf command to enable or disable the ILMI auto configuration for a specified port.
Syntax
cnfautocnf <portid> [yes | no]
Syntax Description
portid
Interface ID in the form of [shelf.]slot[:subslot].port[:subport].
yes | no
Enables or disables the ILMI automatic configuration procedure on the port.
Default: yes
Tip
Related Commands
None
Attributes
Example
Configure the auto configuration for ILMI.
spirita.1.PXM.a > cnfautocnf 0.1.1 nospirita.1.PXM.a >cnfcbclk
Configure Cellbus Clock—PXM1
Use the cnfcbclk command to configure the clock speed for the individual cellbuses. The cnfcbclk command lets you specify whether a cellbus runs at the default of 21 MHz or the double-speed rate of 42 MHz. Not every cellbus and the supported card slots can receive the double-speed clock. Use the dspcbclk command to see whether a particular cellbus can run at 42 MHz.
The backplane contains eight cellbuses: two cellbuses support two card slots and can support 21 MHz or 42 MHz clocking.
Syntax
cnfcbclk <cellBus> <clockRate>
Syntax Description
cellBus
Specifies the cellBus. Enter a string in the range of CB1-CB8. The string is not case sensitive.
clockRate
Specifies a clock rate of 21 MHz or 42 MHz. Enter either 21 or 42.
Related Commands
Attributes
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 > dspcbclkCellBus Rate (MHz) Slots Allowable Rates (MHz)----------------------------------------------------------CB1 21 3 21, 42CB2 21 5 21, 42CB3 21 10 21, 42CB4 21 12 21, 42CB5 21 11 21, 42CB6 21 6, 7 21, 42CB7 21 4 21, 42CB8 21 13, 14 21, 42Example
Configure a double-speed clock for cellbus 5. Check the configuration.
SES_SJ.1.PXM.a > cnfcbclk cb5 42SES_SJ.1.PXM.a > dspcbclkCellBus Rate (MHz) Slots Allowable Rates (MHz)----------------------------------------------------------CB1 21 3 21, 42CB2 21 5 21, 42CB3 21 10 21, 42CB4 21 12 21, 42CB5 42 11 21, 42CB6 21 6, 7 21, 42CB7 21 4 21, 42CB8 21 13, 14 21, 42cnfcdvtdft
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
Related Commands
Attributes
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 ubrspirita.1.PXM.a >Example
Configure the default CDVTD to request UPC for cells received on at a constant bit rate of
250,000 microseconds.spirita.1.PXM.a > cnfcdvtdft 0.1.1 cbrspirita.1.PXM.a >Example
Configure the default CDVTD to request UPC for cells received at an available bit rate of
240 microseconds.spirita.1.PXM.a > cnfcdvtdft 0.1.1 abr 240spirita.1.PXM.a >cnfcmdabbr
Configure Command Abbreviation—PXM1
Use the cnfcmdabbr command to specify whether the CLI requires the entire name of a command or accepts the first unique string of characters that identifies a command. For example, loa is enough to identify if the loadrev command abbreviation is enabled.
Note
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
Attributes
Example
Enable the command abbreviation.
SES_SJ.1.PXM.a > cnfcmdabbr onCommand abbreviations being allowedExample
Verify the status by using the dspcmdabbr command.
SES_SJ.1.PXM.a > dspcmdabbrCommand abbreviations allowedExample
Test the function of the command abbreviation by entering loa (for the loadrev command) without parameters.
SES_SJ.1.PXM.a > loaERR: Syntax: loadrev <slot> <revision>slot -- optional; value: 15,16,31,32revision - revision number. E.g.,2.0(1)2.0(1.255)2.0(0)I or 2.0(0)A2.0(0)P1 or 2.0(0)P22.0(0)P3 or 2.0(0)P4cnfcon
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
•
•
•
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
Related Commands
addcon, delcon, dncon, dspcon, rrtcon, upcon
Attributes
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 1SES_SJ.1.PXM.a >cnfconpref
Configure Connection Preferred Route—PXM1
Use the cnfconpref command to associate a SPVC/P connection to a preferred rout by using the preferred route id value.
Syntax
cnfconpref <portId> <vpi> <vci> <rteID> [-assoc {set | clr}] [-direct {set | clr}]
[-onPrefRte {yes | no}]Syntax Description
Related Commands
addpref, delpref, dsppref, dspprefs, modpref
Attributes
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 yesExample
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 yescnfconsegep
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
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
Attributes
Example
Configure a connection segment endpoint.
spirita.1.PXM.a > cnfconsegep 0.1.1 50 50cnfdate
Configure Date—PXM1
Use the cnfdate command to set the system date.
Syntax
cnfdate <mm/dd/yyyy>
Syntax Description
Related Commands
Attributes
Example
Set the system date.
wilco.1.1.PXM.a> cnfdate 12/17/1999cnfdiag
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
Related Commands
Attributes
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-Wcnfdiagall
Configure Diagnostics All—PXM1
Use the cnfdiagall command to enable and configure the online or offline diagnostics for all card slots.
Note
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
Related Commands
Attributes
Example
Configure all the diagnostics for all the card slots.
SES_SJ.1.PXM.a > cnfdiagall enable disable light 22:30 -M-Wcnfe164 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
Related Commands
None
Attributes
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 leftSES_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 rightSES_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
Attributes
Example
Enable the support of the enhanced IISP on port 1.6.
SES_SJ.1.PXM.a > cnfenhiisp 1.6 yesSES_SJ.1.PXM.a >
Example
Disable the support of the enhanced IISP on port 1.6.
SES_SJ.1.PXM.a > cnfenhiisp 1.6 noSES_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
Related Commands
Attributes
Example
pnnises1.1.PXM.a > cnffltset firstfilter -address 4712345678901234567890123456789012345678-length 160 -plan nsap -list calling -index 1 -accessMode denycnfilmienable
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
Related Commands
None
Attributes
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:1INFO: No ilmi address registeredspirita.2.PXM.a > dnpnport 1:1.1:1spirita.2.PXM.a > cnfilmienable 1:1.1:1 yesspirita.2.PXM.a > uppnport 1:1.1:1spirita.2.PXM.a >cnfilmiproto
Configure ILMI Protocol—PXM1
Use the cnfilmiproto command to configure how PNNI reacts to ILMI events that occur on the VSI slave (a service module). Use the dsppnilmi command to confirm changes to the configuration.
Syntax
cnfilmiproto <portid> [-securelink {yes | no}][-attachmentpoint {yes | no]
[-modlocalattrstd {yes | no]Syntax Description
Related Commands
Attributes
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 yesspirita.1.PXM.a >
Example
Verify the results by entering the dsppnilmi command for port 1.6.
SES_SJ.1.PXM.a > dsppnilmi 1.6Port: 1.6 Port Type: Private UNI Side: networkAutoconfig: disable UCSM: disableSecure Link Protocol: enableChange of Attachment Point Procedures: enableModification of Local Attributes Standard Procedure: enableAddressreg: disableVPI: 0 VCI: 0Max Prefix: 0 Total Prefix: 0Max Address: 0 Total Address: 0Resync State: 0 Node Prefix: yesPeer Port Id: 0 System_Id : 0.0.0.0.0.0Peer Addressreg: disablePeer Ip Address : 0.0.0.0Peer Interface Name :ILMI Link State : DisableILMI Version : ilmi40INFO: No Prefix registeredINFO: No ilmi address registeredSES_SJ.1.PXM.a >cnfintfcongth
Configure Interface Congestion Thresholds—PXM1
Use the cnfintfcongth command to set interface congestion thresholds parameters for a logical port. The thresholds apply to incoming calls and status enquiries. When the upper congestion limit is reached, the port can block incoming calls and adjust the pace of status enquiries.
Note
Syntax
cnfintfcongth <portid> [-setuphi {setupHiThreshold}]]
[-unackedStatEnqLo unackedStatEnqLothreshold]
[-unackedStatEnqHi unackedStatEnqrHithreshold]Syntax Description
Related Commands
Attributes
Example
Configure a congestion threshold of 100 cps for setup messages for port 1.5.
SES_SJ.1.PXM.a > cnfintfcongth 1.5 -setuphi 100Example
Verify the results by entering the dspintfcongth command.
SES_SJ.1.PXM.a > dspintfcongth 1.5Congestion Thresholds for port : 1.5Parameter Value unit--------- ----- ----setuphi 100 cpsunackedStatEnqLo 40 messagesunackedStatEnqHi 100 messagesSES_SJ.1.PXM.a >Example
Set the status enquiries low to 50 cps and the high to 60 cps.
SES_SJ.1.PXM.a > cnfintfcongth 1.5 -unackedstatenqlo 50 -unackedstatenqhi 60Example
Verify the results by entering the dspintfcongth command.
SES_SJ.1.PXM.a > dspintfcongth 1.5Congestion Thresholds for port : 1.5Parameter Value unit--------- ----- ----setuphi 100 cpsunackedStatEnqLo 50 messagesunackedStatEnqHi 60 messagesSES_SJ.1.PXM.a >cnfintvsvd
Configure Interface VS/VD—PXM1
Use the cnfintvsvd command to enable the internal or external virtual source/virtual destination (VS/VD) on a PNNI port. This command is used for SVC calls only and only for configuring ABR parameters. The cnfintvsvd command applies to ports configured for UNI 4.0 or higher. The port must be administratively down. For more information, see the dnpnport command.
Syntax
cnfintfvsvd <portid> [-internal {off |on | unspecified}][-external {off | on | unspecified}]
Syntax Description
Related Commands
addfltset, delfltset, dspfltset
Attributes
Examples
Example 1 :Failure to set VSVD because of port uppnnises1.1.PXM.a > cnfintfvsvd 11.1 -internal onERROR: Port is not out-of-serviceSyntax: 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 = 0internal -- internal {off|on|unspecified (default =unspecified)}external -- internal {off|on|unspecified (default = unspecified)}Example 2 :Failure to set VSVD because of non UNI4.0 portspnnises1.1.PXM.a > cnfintfvsvd 10.1 -internal onERROR: Cannot set vs/vd on a UNI3.0/UNI3.1/IISP interfaceTo turn on the VSVD for the portpnnises1.1.PXM.a > cnfintfvsvd 1.3 -internal onExample 3 :To turn on the VSVD for the portpnnises1.1.PXM.a > cnfintfvsvd 1.3 -internal onpnnises1.1.PXM.a > dsppnport 1.3Port: 1.3 Logical ID: 66304IF status: up Admin Status: upVSVD Internal Loop: onVSVD External Loop: unspecifiedUCSM: enable SVC Routing Pri: 8Auto-config: enable Addrs-reg: enableIF-side: network IF-type: uniUniType: private Version: uni4.0PassAlongCapab: n/aInput filter: 0 Output filter: 0minSvccVpi: 0 maxSvccVpi: 255minSvccVci: 35 maxSvccVci: 65535minSvpcVpi: 1 maxSvpcVpi: 255(P=Configured Persistent Pep, NP=Non-Persistent Pep, Act=Active)#Spvc-P: #Spvc-NP: #SpvcAct: #Spvp-P: #Spvp-NP: #SpvpAct:p2p : 3000 0 0 0 0 0p2mp: 0 0 0 0 0 0#Svcc: #Svpc: #Ctrl: Total:p2p : 0 0 0 0p2mp: 0 0 0 0Type <CR> to continue, Q<CR> to stop:Total: 0cnflmitrace
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
Related Commands
clrlmistats, clrlmitrace, dsplmistats, dsplmitrace
Attributes
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
Attributes
Example
Create the following login message:
Note
Call system administrator before using this switch.SES_SJ.1.PXM.a > cnfloginmsgEnter 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 switchConfirm entry of new message Y/N:(N) yStoring changed Login messageExample
Check the message by entering the dsploginmsg command.
SES_SJ.1.PXM.a > dsploginmsgCall system administrator before using this switchSES_SJ.1.PXM.a >cnfmbsdft
Configure the MBS Default—PXM1
Use the cnfmbsdft command to modify the default MBS for SPVCs on a port. The applicable service types are real-time and nonreal-time variable bit rate (rt-VBR and nrt-VBR).
The most likely connection type where you would use the cnfmbsdft command is SVC. You can also rely on the value set with this command as a default SPVCs if you do not specify an MBS through the addcon command for each SPVC of service type VBR.
The new configuration applies to new incoming calls while existing calls remain intact. The cnfmbsdft command is used regardless of the state of the port.
Syntax
cnfmbsdft <portid> <service_category> [num-of-cell]
Syntax Description
Related Commands
Attributes
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 1000SES_SJ.1.PXM.a >Example
Verify the results by entering the dspmbsdft command for port 2.3.
SES_SJ.1.PXM.a > dspmbsdft 2.3rt-vbr: nrt-vbr:MBS: 1024 1000SES_SJ.1.PXM.a >Example
Configure the MBS default to be 900 cells for rt-vbr for port 2.3.
SES_SJ.1.PXM.a > cnfmbsdft 2.3 rtvbr 900SES_SJ.1.PXM.a >Example
Verify the results by entering the dspmbsdft command for port 2.3.
SES_SJ.1.PXM.a > dspmbsdft 2.3rt-vbr: nrt-vbr:MBS: 900 1000SES_SJ.1.PXM.a >cnfname
Configure Name—PXM1
Use the cnfname command to set the name of the SES PNNI node. This name cannot be propagated throughout the network.
Syntax
cnfname <name>
Syntax Description
Related Commands
None
Attributes
Example
Configure the node name for the switch.
spirita.1.PXM.a > cnfname NewNamecnfname: Configured this node name to NewName Successfully.NewName.1.PXM.a >cnfndparms
Configure Node Parameters—PXM1
Use the cnfndparms command to specify numerical values or to enable a set of node-level parameters. The cnfndparms command has parameters that consist of an option number, a value, or a yes or no option. The configuration resides in nonvolatile RAM and utilizes a system reset or power cycle.
For information on related alarms, see dspenvalms and dspndalms commands.
Syntax
cnfndparms <option_number> <option_value>
Syntax Description
option_number
A number that selects an option. The current number range is 1-8. If you do not enter an option number, the interface displays all options. If you enter an option number but no value, the interface prompts for appropriate input.
The following are the eight option numbers:
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:
•
•
•
•
•
•
•
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:
•
•
•
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:
•
•
•
•
•
•
Related Commands
dspndparms, dspndalms, dspenvalms
Attributes
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 > cnfndparmsSES_SJ System Rev: 03.00 Jan. 31, 2002 23:14:43 GMTSES-CNTL Node Alarm: NONENODE CONFIGURATION OPTIONSOpt# 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 Enabled4 0x0 8bit Hex Required Power Supply Module Bitmap5 0 8bit Decimal Trap Manager Aging timeout value(Hour(s))6 atm0 8bit Decimal Primary IP interface for Netmgmt7 lnPci0 8bit Decimal Secondary IP interface for NetmgmtEnter option number (1-7): 8ERR: Option number 8 not in range 1-7Syntax: cnfndparms <option_number> <option_value><option_number> - number of option to configureuse dspndparms to see valid options<option_value> - value for optionif option is boolean: (Y/N)if option is 8bit Decimal: (0 - 255)if option is 16bit Decimal: (0 - 65535)if option is 32bit Decimal: (0 - 4294962795)if option is 8bit Hex: (0 - 0xff)if option is 16bit Hex: (0 - 0xffff)if option is 32bit Hex: (0 - 0xffffffff)SES_SJ.1.PXM.a >cnfnodalcongth
Configure the Nodal congestion Threshold—PXM1
Use the cnfnodalcongth command to set nodal congestion threshold parameters. The thresholds relate to call setup messages. stauts enquiries, queue levels, and so forth. You must specify at least one optional parameter.
Syntax
cnfnodalcongth [-setuphi <value>] [-statenqlo <value>] [-statenqhi <value>][-connpendlo <value>] [-connpendhi <value>] [-incompjour <value>][-vsiqmild <value>] [-vsiqmedium <value>]
[-vsiqsevere <value>]Syntax Description
Related Commands
Attributes
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 175Example
Verify the results by entering the dspnodalcongth command.
SES_SJ.1.PXM.a > dspnodalcongthParameter Value Unit=================================setuphi(prov) 80 cpssetuphi(curr) 80 cpsstatenqlo 100 cpsstatenqhi 200 cpsconnpendlo 400 messagesconnpendhi 500 messagesincompjour 5 cyclesvsiqmild 100 multipliervsiqmedium 140 multipliervsiqsevere 175 multipliercnfnodalfd
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
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
Attributes
Example
Install frame discard on the presence of the AAL5 IE.
SES_SJ.1.PXM.a > cnfnodalfd enableSES_SJ.1.PXM.a >
Example
Disable the frame discard on the presence of the AAL5 IE.
Note
SES_SJ.1.PXM.a > cnfnodalfd disableSES_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
Attributes
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 > cnfpasswdEnter existing password:Enter new password:Re-enter new password:cnfpri-routing
Configure Priority Routing—PXM1
Use the cnfpri-routing command to configure the number of bandwidth groups, the size of the first bandwidth group, and the increment between the successive groups. The cnfpri-routing command also configures the size of the routing event buffer as well as the delay before connections are routed during node startup.
The first bandwidth group contains connections for the bandwidth requirements that are below the start parameter. Each of the bandwidth groups contains connections for the bandwidth parameters that are more than the previous bandwidth group at or below the sum of the previous bandwidth group upper bound and the incr parameter. The last bandwidth group, which is specified by the grps parameter, contains all remaining connections that do not fit into any of the previous groups. Connections in the last bandwidth group, which require the most bandwidth, are routed as well as derouted ahead of connections in earlier bandwidth groups when the priority of the connections is the same.
Note
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
Related Commands
addcon, cnfcon, dspcon, dspcons, cnfpnportsig, dsppnportsig, dsppncon, dsppncon, dsppri-routing
Attributes
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 100SES_SJ.1.PXM.a > cnfpri-routing -pribuf 10 -nodebuf 50Example
Verify the priority routing results by entering the dsppri-routing command.
SES_SJ.1.PXM.a > dsppri-routingPriority Routing Configuration--------------------------------Number of bandwidth groups: 50Size of first bandwidth group (in cps): 500Increment between bandwidth groups (in cps): 100Routing event buffer size (in 0.1-seconds): 10Node startup routing delay (in 0.1-seconds): 50SES_SJ.1.PXM.a >cnfoamsegep
Configure an OAM Segment Endpoint—PXM1
Use the cnfoamsegep command to define a specified port as a segment endpoint for F4 and F5 OAM flow. This command does not take effect for existing connections. It takes effect only for newly established calls. The cnfoamsegep command is used regardless of the state of the port.
Syntax
cnfoamsegep <portid> [yes | no]
Syntax Description
Related Commands
cnfconsegep, delconsegep, dspoamsegep
Attributes
Example
Configure a port as a segment endpoint.
SES_SJ.1.PXM.a > cnfoamsegep 2.3 yesSES_SJ.1.PXM.a >Example
Verify the results to enable the OAM segment endpoint by entering the dspoamsegep command for
port 2.3.SES_SJ.1.PXM.a > dspoamsegep 2.3Port OAM End Point2.3 YesExample
Configure a port 2.3 so it is not a segment endpoint.
SES_SJ.1.PXM.a > cnfoamsegep 2.3 noSES_SJ.1.PXM.a >Example
Verify the results to disable the OAM segment endpoint by entering the dspoamsegep command for
port 2.3.SES_SJ.1.PXM.a > dspoamsegep 2.3Port OAM End Point2.3 NoSES_SJ.1.PXM.a >cnfpnctlvc
Configure PNNI Control VC—PXM1
Use the cnfpnctlvc command to configure bandwidth parameters for two types of control channels on a port. The types of control channels are service-specific connection-oriented protocol (SSCOP) or PNNI routing control channel (PNNI-RCC). You can enter this command for one VC type at a time.
Before using the cnfpnctlvc command, note the following issues:
•
•
•
Note
•
The VC for ILMI is also a control channel, but its bandwidth parameters are fixed. The following are the values for the parameters:
–
–
–
Syntax
cnfpnctlvc <portid> <vc-type> -pcr <pcr> -scr <scr> -mbs <mbs>
Syntax Description
Related Commands
Attributes
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 100ERROR: Port is not out-of-serviceExample
Down port 2.3 by entering the dnpnport command. Enter the cnfpnctlvc command to complete the task.
SES_SJ.1.PXM.a > dnpnport 2.3SES_SJ.1.PXM.a > cnfpnctlvc 2.3 sscop -mbs 100cnfpnctlvc SuccessfulExample
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.3vc type = pnnirccservice category : sig PCR : 906SCR : 453 MBS : 171vc type = sscop Parameter = Provisionedservice category : sig PCR : Not ProvisionedSCR : Not Provisioned MBS : 100SES_SJ.1.PXM.a > uppnport 2.3SES_SJ.1.PXM.a >cnfpnni-election
Configure PNNI PGL Election—PXM1
Use the cnfpnni-election command to specify the priority of a node for the purpose of electing a peer group leader (PGL). By using this ranking, you can promote or prevent certain nodes for consideration for PGL election.
In a multi-peer group environment, each peer group can elect one PGL. The election takes place for every level of the hierarchy. For example, if three levels exist, three PGL elections occur. To ensure that a node cannot win the PGL election, you can assign 0 for the priority.
Every node in a peer group runs the election algorithm—with one exception: a node with the nontransit for PGL Election Flag set.
The following are the specifications that are needed for the cnfpnni-election command:
•
•
•
Syntax
cnfpnni-election <node-index> [-priority priority][-initTime init-time]
[-overrideDelay override-delay][-reelectionTime reelection-time]Syntax Description
Related Commands
Attributes
Example
Specify the following PGL election parameters:
•
•
•
•
•
SES_SJ.1.PXM.a > cnfpnni-election 1 -priority 15 -initTime 10 -overrideDelay 20-reelectionTime 15SES_SJ.1.PXM.a > dsppnni-electionnode index: 1PGL state...... AwaitUnanimity Init time(sec)....... 10Priority....... 15 Override delay(sec).. 20Re-election time(sec) 15Pref PGL...............56:160:47.009181000000003071f813a1.003071f813a1.01PGL....................0:0:00.000000000000000000000000.000000000000.00Active parent node id..0:0:00.000000000000000000000000.000000000000.00SES_SJ.1.PXM.a >cnfpnni-intf
Configure PNNI Interface—PXM1
Use the cnfpnni-intf command to configure service category based administrative weight and aggregation token on a PNNI interface.
Aggregation Tokens
An aggregation token is a marker that indicates which uplinks, for example, links going out of the peer group, can be bundled or aggregated at the next logical level. If four links a, b, c, and d connect to peer groups X and Y, no aggregation exists for the links by default. The LGNs of these peer groups can have hypothetical names x02 and y02. They can be connected by a single logical link.
If you configure the aggregation token of link c as 1, x02 and y02 can have two logical links. One link corresponds to aggregation token 0, and the other link corresponds to aggregation token 1. Overall, an aggregation token is the number of links between a peer group leader and the lowest level of a PNNI hierarchy. The range for tokens is 1-32.
Administrative Weight
The administrative weight (AW) is a number that serves as a cost-based determinant of a route. Each port in a PNNI network has a default AW for the egress direction. Whether it uses the default AW or an AW you specify, PNNI adds all the AWs in a prospective route then determines whether the route is too expensive. For an SPVC, you can specify the maximum cost with the addcon command or the cnfcon command.
You can specify that all classes of service on the port have the same AW, or you can specify an AW for each service class on the port. If you specify the same AW for all, it overrides the default AW or the AW you might specify for individual services types.
The AW for a path is the sum, in both directions, of the individual weight of each link on the path.
Syntax
cnfpnni-intf <portid> [-aggregationToken token][-awcbr aw][-awrtvbr aw][-awnrtvbr aw]
[-awabr aw][-awubr aw] [-awall aw]Syntax Description
Related Commands
Attributes
Example
Specify the following AWs on port 2.3:
•
•
•
SES_SJ.1.PXM.a > cnfpnni-intf 2.3 -awrtvbr 11040 -awnrtvbr 20040 -awubr 1040Example
Verify the results by entering the dsppnni-intf command for port 2.3.
SES_SJ.1.PXM.a > dsppnni-intf 2.3Physical port id: 2.3 Logical port id: 131840Aggr token.......... 0 AW-NRTVBR........... 20040AW-CBR.............. 5040 AW-ABR.............. 5040AW-RTVBR............ 11040 AW-UBR.............. 1040SES_SJ.1.PXM.a >cnfpnni-link-selection
Configure PNNI Link Selection—PXM1
Use the cnfpnni-link-selection command to specify which routing policies are used to select one of the parallel links that connect a neighboring PNNI node. Neighboring node in this case means a directly connected node. The cnfpnni-link-selection command applies only if parallel links exist between the specified port and neighboring nodes.
Note
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
Related Commands
Attributes
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 maxavcrExample
Use the dsppnni-link-selection command to see the link selection policy on this port.
Note
SES_SJ.1.PXM.a > dsppnni-link-selection 2.3physical port id: 2.3 link selection: maxavcrlogical port id: 131840SES_SJ.1.PXM.a >cnfpnni-mtu
Configure PNNI Maximum Transmit Unit—PXM1
Use the cnfpnni-mtu command to configure the maximum PNNI packet size in number of bytes. The cnfpnni-mtu command is useful for internet working compatibility, which you must match the maximum packet size of your peer group to a size that another peer group can handle. You can use the cnfpnni-mtu command in lab trials to test the effect of various packet sizes on the performance of the peer group.
Use the dsppnni-mtu command to display the PNNI packet size configuration.
Syntax
cnfpnni-mtu <mtu>
Syntax Description
mtu
Specifies the maximum transmit unit (MTU) in number of bytes.
Range: 2048-8192 bytes
Default: 2048
Related Commands
Attributes
Example
Configure the maximum PNNI packet size to 3002 bytes.
SES_SJ.1.PXM.a > cnfpnni-mtu 3002Example
Verify the results by entering the dsppnni-mtu command.
SES_SJ.1.PXM.a > dsppnni-mtumax packet size : 3002SES_SJ.1.PXM.a >cnfpnni-node
Configure PNNI Node—PXM1
Use the cnfpnni-node command to modify parameters for an existing PNNI node.
The node must be put into administratively disable status, before changing its ATM address, node ID, peer group ID, or hierarchical level.
Note
The following are the functions of the node-level cnfpnni-node command:
•
•
–
–
The following are the modifications for the node configuration and state parameters:
•
•
•
•
•
•
•
•
•
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:
•
•
•
•
For these parameters, three executions of cnfpnni-node are necessary:
1.
2.
3.
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
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
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
Example
Specifies the PNNI configuration values for a node that already exists on the network. The following are the PNNI node configurations:
•
•
•
•
•
•
•
•
•
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 offExample
Use dsppnni-node to display the PNNI configuration values.
SES_SJ.1.PXM.a > dsppnni-nodenode index: 1 node name: SES_SJLevel............... 56 Lowest.............. trueRestricted transit.. off Complex node........ offBranching restricted onAdmin status........ up Operational status.. upNon-transit for PGL election.. offNode id...............56:160:47.009181000000003071f813a1.003071f813a1.01ATM address...........47.009181000000003071f813a1.003071f813a1.01Peer group id.........56:47.00.9181.0000.0000.0000.0000.00SES_SJ.1.PXM.a >cnfpnni-pkttrace
Configure PNNI Packet Trace—PXM1
The cnfpnni-pkttrace command applies to debugging. It causes the switch to check the PNNI packets transmitted and received at each peer. For example, if an interface is not receiving user-traffic, you can enter dsppnni-pktrace to display packet information that can help you find the level and type of blockage.
The cnfpnni-pkttrace command specifies the trace command examines the contents of PNNI packets exchanged between two neighboring nodes. A PNNI packet consists of a Hello packet and the topology information packets.
Note
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
Related Commands
dsppnni-pkttrace, dsppnport, dsppnports
Attributes
Example
Configure the following contents of PNNI Hello packets:
•
•
•
SES_SJ.1.PXM.a > cnfpnni-pkttrace tx 17504PNNI/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 2a00001aExample
Verify the trace by entering the dsppnni-pkttrace command.
SES_SJ.1.PXM.a > dsppnni-pkttrace tx -portId 17504Node Index :1 Port id: 17504 Tx Pkt Trace onSES_SJ.1.PXM.a >cnfpnni-routing-policy
Configure the PNNI Routing Policy—PXM1
Use the cnfpnni-routing-policy command to specify which routing policy values are used during UNI call setup. Routing policies control PNNI routing for your network.
The following specifications are for the cnfpnni-routing-policy command:
•
•
•
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:
