Table Of Contents
dbgcon
dbgilmi
dbgpnni
dbgsntp
dclk
deladdr
deladdrs
delallusers
delapsln
delbert
delclksrc
delcon
delcons
delconsegep
delcontroller
delfltset
delimagrp
delimalnk
dellink
dellnloop
dellpback
delncdpclksrc
delpart
delpnni-node
delpnni-summary-addr
delpnport
delpnportacc
delport
delpref
delprfx
delred
delrscprtn
delsct
delsesn
delsigdiag
delslotlink
delsntprmtsvr
deltopond
deltrapmgr
deluser
disablesscop
dncon
dnimagrp
dnilmi
dnln
dnpnport
dnport
downloadflash
dbgcon
Debug Connection—PXM45, PXM1E
The node-level dbgcon command enables or disables the SPVC (or SPVP) error log. You can enable the error log for a specific connection by specifying a port ID, VPI, and VCI. To see whether the connection error log is enabled, use the dspcons-dbg command.
This command can substantially increase CPU usage, so you should seriously consider whether its usage is safe in your circumstances. This potential is greater when all connections are included.
Syntax
dbgcon <enable | disable> [-port <portid> -vpi <vpi> -vci <vci>]
Syntax Description
enable | disable
|
Enter enable or disable to start or stop the SPVC log.
Default: disabled.
|
-port
|
Enter -port followed by the value of the portid for the specific SPVC. The format of the PNNI physical port identifier can vary, as follows:
• On a PXM45: slot:subslot.port:subport
• On a PXM1E for UNI/NNI back card: slot:subslot.port:subport. On the UNI/NNI back card, the subslot is always 2, but the slot depends on the chassis, as follows:
– In an MGX 8850 chassis, slot is always the logical slot 7.
– In an MGX 8830 chassis, slot is always the logical slot 1.
• On a PXM1E for a narrowband service module (NBSM): slot.port.
For more details, see the section, "PNNI Format," in "Introduction."
|
-vpi
|
Enter -vpi followed by the value of the vpi for the specific SPVC. The range is 0-4095.
|
-vci
|
Enter -vci followed by the value of the vpi for the specific SPVC. The range is 1-65535.
|
Related Commands
dspcons-dbg
Attributes
Log: no
|
State: active, standby
|
Privilege: SERVICE_GP
|
Example
Enable the SPVC log for the connection with port ID 9:1.8:8 and VPI/VCI100/100.
MGX8850.8.PXM.a > dbgcon enable -port 9:1.8:8 -vpi 100 -vci 100
dbgilmi
Debug ILMI—PXM45, PXM1E
Use dbgilmi to debug ILMI functionality (such as address registration or auto configuration).
Note
VSI pass-through information is exchanged between only the controller (PPNI) and the switch.
Syntax
dbgilmi {enable | disable} [<portid>] [-log <vsi | func | minor | major | warning | error | dump | fatal | all>] [-dbg <vsi | func | minor | major | warning | error | dump | fatal | all>]
Syntax Description
enable | disable
|
Activate or de-activate ILMI debugging.
|
portid
|
The format of the PNNI physical port identifier can vary, as follows:
• On a PXM45: slot:subslot.port:subport
• On a PXM1E for UNI/NNI back card: slot:subslot.port:subport. On the UNI/NNI back card, the subslot is always 2, but the slot depends on the chassis, as follows:
– In an MGX 8850 chassis, slot is always the logical slot 7.
– In an MGX 8830 chassis, slot is always the logical slot 1.
• On a PXM1E for a narrowband service module (NBSM): slot.port.
For more details, see the section, "PNNI Format," in "Introduction."
|
-log
|
If you type the optional keyword log, follow it with at least one of the following:
vsi func minor major warning error dump fatal all: log all
|
-dbg
|
If you type the optional keyword dbg, follow it with at least one of the following:
vsi func minor major warning error dump fatal all: dbg all
|
Attributes
Log: yes
|
State: active, standby
|
Privilege: SERVICE_GP
|
dbgpnni
Debug PNNI Messages—PXM45, PXM1E
The dbgpnni command lets you specify the types of debug messages that appear in the display of the dsppnni-dbg command.
Note
The selections you make with this command can significantly affect network performance. The simultaneous dumping of multiple types of debug messages can increase the overhead more than incrementally as each type is added. Consider the options individually rather than simultaneously.
Syntax
dbgpnni [-all {on | off}] [-hello {on | off}] [-election {on | off}] [-nbr {on | off}] [-itf {on | off}] [-timer {on | off}] [-lgn {on | off}] [-spt {on | off}] [-nodereachability {on | off}] [-address {on | off}] [-itdb {on | off}] [-ra {on | off}] [-cp {on | off}] [-linkselection {on | off}]
Syntax Description
-all
|
Specify whether all types of debug message go to the console.
on: All types of debug message go to the console. off: Only the debug message-types specified by the other dbgpnni parameters are active.
Default: none
|
-timer
|
Specify whether the timer debug messages go to the console.
on: The timer debug messages go to the console. off: The timer debug messages do not go to the console.
Default: none
|
-hello
|
Specify whether the hello debug messages go to the console.
on: The hello debug messages go to the console. off: The hello debug messages do not go to the console.
Default: none
|
-nbr
|
Specify whether the PNNI neighbor FSM debug messages go to the console.
on: The PNNI neighbor FSM messages go to the console. off: The PNNI neighbor FSM debug messages do not go to the console.
Default: none
|
-election
|
Specify whether the PNNI PGL election debug messages go to the console.
on: The PNNI PGL election messages go to the console. off: The PNNI PGL election debug messages do not go to the console.
Default: none
|
-nodereachability
|
Specify whether the debug messages about PNNI node reachability computation go to the console.
on: The PNNI node reachability computation messages go to the console. off: The PNNI node reachability computation is not active
Default: none
|
-itf
|
Specify whether the interface FSM debug messages go to the console.
on: The interface FSM messages go to the console. off: The interface FSM debug messages do not go to the console.
Default: none
|
-address
|
Specify whether the debug messages about the handling on addresses go to the console.
on: The debug handling on addresses is active off: The debug handling on addresses is not active
Default: none
|
-lgn
|
Specify whether the logical group node debug messages go to the console.
on: The PNNI logical group node messages go to the console. off: The PNNI logical group node debug messages do not go to the console.
Default: none
|
-itdb
|
Specify whether the debug messages about the handling on the internal topology database go to the console.
on: The debug messages for the internal topology database go to the console. off: The debug messages for the internal topology database does not go to the console.
Default: none
|
-cp
|
Specify whether the control point debug messages go to the console.
on: The control point debug messages go to the console. off: The control point debug messages do not go to the console.
Default: none
|
-spt
|
Specify whether the shortest path tree debug messages go to the console.
on: The shortest path tree debug messages go to the console. off: The shortest path tree debug messages do not go to the console.
Default: none
|
-ra
|
Specify whether the route agent debug messages go to the console.
on: The route agent debug messages go to the console. off: The route agent debug messages do not go to the console.
Default: none.
|
-linkselection
|
Specify whether the link selection debug messages go to the console.
on: The link selection debug messages go to the console. off: The link selection debug messages do not go to the console.
Default: none
|
Related Commands
dsppnni-dbg
Attributes
Log: yes
|
State: active
|
Privilege: CISCO_GP
|
Example
Specify the following PNNI debug message-options:
•
Interface debugging is enabled.
•
Address handling debugging is enabled.
Use dsppnni-dbg to check which debug messages types appear on the terminal.
SanJose.7.PXM.a > dsppnni-dbg
hello election nbr itf timer lgn spt node reachability
----- -------- --- --- ----- --- --- -----------------
off off off off off off off off
address itdb ra cp link selection
------- ---- --- --- --------------
SanJose.7.PXM.a > dbgpnni -itf on -address on
SanJose.7.PXM.a > dsppnni-dbg
hello election nbr itf timer lgn spt node reachability
----- -------- --- --- ----- --- --- -----------------
off off off on off off off off
address itdb ra cp link selection
------- ---- --- --- --------------
In the second example, the parameters are changed as follows:
•
Interface debugging is disabled.
•
Address handling debugging is disabled.
SanJose.7.PXM.a > dbgpnni -itf off -address off
SanJose.7.PXM.a > dsppnni-dbg
hello election nbr itf timer lgn spt node reachability
----- -------- --- --- ----- --- --- -----------------
off off off off off off off off
address itdb ra cp link selection
------- ---- --- --- --------------
dbgsntp
Debug Simple Network Time Protocol—PXM45, PXM1E
The dbgsntp command lets you enable SNTP debugging and specify the level of debugging. Use the dspsntp-dbg command to see the debugging configuration created with the dbgsntp command.
Syntax
dbgsntp <enable | disable> [ipaddr] [-level <info | trace | debug>]
Syntax Description
enable or
disable
|
Type the "enable" to "disable" either to enable or to disable SNTP debugging.
Default: disable
|
ipaddr
|
Enter the IP address of a particular switch to debug SNTP between the current switch and the other switch.
|
-level
|
You can specify a level of debugging by entering one of the following:
• info means informational only.
• trace means a trace is sent.
• debug means that detailed debugging is enabled.
Default: info
|
Related Commands
cnfsntp, cnfsntprmtsvr, dspsntp, dspsntprmtsvr, addsntprmtsvr, delsntprmtsvr, dspsntpstats
Attributes
Log: yes
|
State: active
|
Privilege: ANYUSER
|
Example
dclk
Display Clock Measured by System Clock Test—PXM45, PXM1E
Display the Digital to Analog Converter (DAC) value and the deviation, in parts-per-million, of the output frequency of the current clock source. This is the nominal frequency value for the local oscillator on the PXM45 UIS3 card.
The local oscillator of the UIS3 is an Over-Controlled Crystal Oscillator (OCXO) with a nominal frequency of 19.44Mhz. The control voltage applied to the OCXO by the hardware circuitry on the board adjusts the output frequency range of the clock between +/- 7 PPM (136Hz) to +/- 14PPM (272Hz).
The DAC value is used to convert the digital voltage value, from the DSP FPGA, to the analog voltage, which controls the OCXO. The range of the input DAC value is from 0x0000 to 0xffff with a nominal value of 0x8000.
The dclk output displays the DAC value field, which is the difference between the current measured DAC value and the nominal DAC value of 0x8000, and the PPM values for the last 100 current clock samples that have been taken at the rate of one every second.
Syntax
dclk
Syntax Description
This command takes no parameters.
Related Commands
None
Attributes
Log: no
|
State: active
|
Privilege: SERVICE_GP
|
Example
deladdr
Delete Address—PXM45, PXM1E
Removes an ATM address for a UNI or IISP.
Syntax
deladdr <portid> <atm-address> <length> [-plan {e164 | nsap}]
Syntax Description
portid
|
The format of the PNNI physical port identifier can vary, as follows:
• On a PXM45: slot:subslot.port:subport
• On a PXM1E for UNI/NNI back card: slot:subslot.port:subport. On the UNI/NNI back card, the subslot is always 2, but the slot depends on the chassis, as follows:
– In an MGX 8850 chassis, slot is always the logical slot 7.
– In an MGX 8830 chassis, slot is always the logical slot 1.
• On a PXM1E for a narrowband service module (NBSM): slot.port.
For more details, see the section, "PNNI Format," in "Introduction."
|
atm-address
|
The ATM address: its format depends on whether the address type is NSAP or E.164. The address plan specifies the address type and so determines the maximum number of bytes or bits in the address. You can specify the address plan with the forthcoming -plan option. The default plan is NSAP.
• An NSAP address can have 1-20, 8-bit bytes (where a byte is 2 hexadecimal characters). Cisco recommends that you use 20 bytes for the NSAP address.
• An E.164 address can 8-15 decimal digits.
The number of bits or bytes in the ATM address effects the uniqueness of the address. The longest address ensures total uniqueness of the address. With a one-byte address, any caller that sends an address whose first address byte matches that one-byte ATM address goes to that port.
|
length
|
Address length. The units of measure differ for each address plan. The -plan option lets you specify E.164 or NSAP.
• For an NSAP address plan, the units of measure are bits. The range is 0-160. Using the maximum of a 20-byte address: 20 bytes x 8 bits per byte = 160 bits.
• For an E.164 address plan, the value is the number of decimal digits. If the ATM address consists of 15 digits, the value for this parameter is also 15.
|
-plan
|
Address plan: E.164 or NSAP.
Default: nsap
|
Related Commands
addaddr, dspaddr, deladdrs
Attributes
Log: yes
|
State: active
|
Privilege: GROUP1
|
Example
On port 11:2.8:22, delete 47.0091.8100.0000.0000.0ca7.9e01.4000.0c81.8000.00. Note that the command entry includes the address length of 160 after the address.
Geneva.7.PXM.a > deladdr 11:2.8:28 47.0091.8100.0000.0000.0ca7.9e01.4000.0c81.8000.00 160
deladdrs
Delete Addresses—PXM45, PXM1E
Removes all ATM addresses on a UNI, AINI, or IISP. The optional plan parameter lets you differentiate by address plan:
•
E164
•
NSAP
•
All address plans (the default)
Syntax
deladdrs <portid> [-plan {e164 | nsap | all}]
Syntax Description
portid
|
The format of the PNNI physical port identifier can vary, as follows:
• On a PXM45: slot:subslot.port:subport
• On a PXM1E for UNI/NNI back card: slot:subslot.port:subport. On the UNI/NNI back card, the subslot is always 2, but the slot depends on the chassis, as follows:
– In an MGX 8850 chassis, slot is always the logical slot 7.
– In an MGX 8830 chassis, slot is always the logical slot 1.
• On a PXM1E for a narrowband service module (NBSM): slot.port.
For more details, see the section, "PNNI Format," in "Introduction."
|
-plan
|
Address plan: E.164, NSAP, or all.
Default: all
|
Related Commands
addaddr, dspaddr, deladdr
Attributes
Log: yes
|
State: active
|
Privilege: GROUP1
|
Example
On port 11:2.8:22, delete all the addresses (regardless of address plan).
Geneva.7.PXM.a > deladdrs 11:2.8:28
delallusers
Delete All Users—PXM45, PXM1E
Use the delallusers command to delete every user account except the default user.
Syntax
delallusers
Syntax Description
This command takes no parameters, but the system prompts for confirmation (see Example).
Related Commands
adduser, dspusers, deluser, users
Attributes
Log: yes
|
State: active
|
Privilege: CISCO_GP
|
Example
Before you use the delallusers command, check the existing user accounts by using the dspusers command to be sure that deleting all users except the defaults is appropriate. Check the list of users after you run the delallusers command.
Delete all users except the default user.
Unknown.7.PXM.a > dspusers
-------------------------
Unknown.7.PXM.a > delallusers
This command deletes all users except the default users
delallusers:Do you want to proceed (Yes/No)? y
Unknown.7.PXM.a > dspusers
-------------------------
delapsln
Delete APS Line—PXM1E
Removes the specified APS line from the switch.
See the description for the addapsln command for a detailed explanation of Automatic Protection Switching (APS).
Syntax
delapsln <workingline>
Syntax Description
workingline
|
Slot number, bay number, and line number of the working index, in the format:
slot.bay.line
• The slot number depends on the chassis as well as the card type, as follows:
– MGX 8850 chassis: the slot is 7 for the UNI/NNI back card. For the SRME, the slot is 15 or 31.
– MGX 8830 chassis: the slot is 1 for the UNI/NNI back card. For the SRME, the slot is 7.
• Bay: 1 or 2, and variations occur as follows:
– For UNI/NNI back card, the working bay is always 2.
– For SRME in an MGX 8850 chassis, working bay is 1 or 2. In an MGX 8830 chassis, SRME working bay is always 1.
• The line number depends on the card type, as follows:
– UNI/NNI OC3c/STM1 back card: 9-12 on the combo card or 1-4 on the regular card.
• SRME: always 1.
|
Related Commands
addapsln, cnfapsln, dspapsln, switchapsln, dspapsbkplane, clrbecnt, dspbecnt
Attributes
Log: yes
|
State: active
|
Privilege: GROUP1
|
Example
delbert
Delete Bit Error Rate Test—PXM1E
The delbert command lets you terminate a BERT session. This command applies to service modules that do not have native BERT capability and so require a Service Resource Module (SRM-3T3/C or SRME). An alternative to this command is the cnfbert command but with the enable parameter set to "destroy BERT." See cnfbert syntax description.
Note
In the current release, the PXM45 does not support this BERT command.
Syntax
delbert <LSMSlot.Line.Port>
Syntax Description
LSMSlot.Line.Port
|
The fields in the parameter can have the following values:
• LSMslot can have a value in one of the following ranges: 1-6, 9-14, 17-22, or 25-30.
• Line has a range from 1 though the maximum number of lines on the card.
• The Port has a value from 1 though the maximum ports supported by the service module.
|
Related Commands
cnfbert, dspbert, dspbertcap
Attributes
Log: yes
|
State: active
|
Privilege: GROUP1
|
delclksrc
Delete Clock Source—PXM45, PXM1E
Deletes a user-specified primary or secondary clock source. This command applies on switches that have a manual clock configuration. (See also cnfclksrc and cnfncdp descriptions.) Changing a clock source or changing the priority of the source (primary or secondary) are the most frequent uses of delclksrc. See the description of cnfclksrc for these common uses of delclksrc.
Note
If the node has a redundant PXM, it automatically receives changes to the clock configuration as well as automated changes to clock status that occur under node management. For example, executing delclksrc is a configuration change that the standby card automatically implements. Also, a switch from primary to secondary clock source is recorded by the standby PXM.
Syntax
delclksrc <priority>
Related Commands
cnfclksrc, dspclksrcs, dspclkalms
Attributes
Log: yes
|
State: active
|
Privilege: SUPER_GP
|
Example
Delete the primary clock source.
pinnacle.7.PXM.a> delclksrc primary
delcon
Delete Connection—PXM1E
Use the delcon command to delete an SPVC or SPVP. For dual-ended connections, delete the connection at both ends—first at the master end, then at the slave. To delete a single-ended connection, use this command at the master end only.
Syntax
delcon <ifnum> <vpi> <vci>
Syntax Description
ifnum
|
The range for logical interface (or port) numbers is are as follows 1-31.
|
vpi
|
Virtual path identifier in the range 0-255 (UNI) or 0-4095 (NNI or VNNI).
|
vci
|
Virtual connection identifier (VCI):
• For a VCC on a UNI, the range is 1-4095. On an NNI or VNNI, the VCI range is 1-65535. For MPLS, the recommended minimum VCI is 35.
• For a VPC, the vci is 0.
|
Related Commands
dspcon, addcon, cnfcon
Attributes
Log: yes
|
State: active
|
Privilege: GROUP1
|
Example
MGX8850.7.pxm1e.a > delcon 1 10 40
delcons
Delete Connections—PXM1E
Delete a range of connections.
Caution 
The
delcons command is intended for Cisco development engineers to use during the troubleshooting of system software. The command is too dangerous to use in user networks carrying live traffic because it can delete far more than the anticipated number of connections. Repairing such damage could be very costly.
Syntax
delcons <ifNum> <vpi> <vci> [-num <num. conns to del>] [-verbose < 1 | 0 >]
Syntax Description
ifNum
|
The range for logical interface (or port) numbers is are as follows 1-31.
|
vpi
|
For a UNI, the range is 0-255. For an NNI, the range is 0-4095.
|
vci
|
For a VCC, the range is 1-65535. For a VPC, the only value is 0.
|
-num
|
(Optional) Keyword that specifies the number of connections to delete.
|
-verbose
|
(Optional) Keyword that enables (1) or disables (0) verbose mode. In verbose mode, the screen displays the connection identifier of each connection immediately after it is deleted.
|
Related Commands
None
Attributes
Log: no
|
State: active
|
Privilege: SERVICE_GP
|
delconsegep
Delete Connection Segment Endpoint—PXM45, PXM1E
Deletes a segment endpoint on a connection. When both VPI and VCI are present, the segment endpoint is an F5 flow endpoint (for VCCs). When the optional VCI is not present, the segment endpoint is an F4 flow endpoint (for VPCs).
Note
The delconsegep command works for SVCs only.
Syntax
delconsegep <portid> <vpi> [vci]
Syntax Description
portid
|
The format of the PNNI physical port identifier can vary, as follows:
• On a PXM45: slot:subslot.port:subport
• On a PXM1E for UNI/NNI back card: slot:subslot.port:subport. On the UNI/NNI back card, the subslot is always 2, but the slot depends on the chassis, as follows:
– In an MGX 8850 chassis, slot is always the logical slot 7.
– In an MGX 8830 chassis, slot is always the logical slot 1.
• On a PXM1E for a narrowband service module (NBSM): slot.port.
For more details, see the section, "PNNI Format," in "Introduction."
|
vpi
|
VPI of the connection.
|
vci
|
VCI of the connection.
|
Related Commands
cnfoamsegep, dspoamsegep, cnfconsegep, dspconsegep
Attributes
Log: yes
|
State: active
|
Privilege: GROUP1
|
delcontroller
Delete Controller—PXM45, PXM1E
Delete a controller. The delcontroller command does not erase the controller software but directs the switch not to use it.
Syntax
delcontroller <cntrlrId>
Syntax Description
cntrlrId
|
The controller ID (cntrlrId) has a range of 1-20 and is assigned using addcontroller. To see all controllers on the switch, use dspcontrollers.
|
Related Commands
addcontroller, dspcontrollers
Attributes
Log: yes
|
State: active
|
Privilege: SUPER_GP
|
Example
Delete controller 3. In this example, the 3 is the reserved controller ID for LSC.
MGX8850.8.PXM.a > delcontroller 3
delfltset
Delete Filter Set—PXM45, PXM1E
Removes an ATM address filter set.
Syntax
delfltset <name> [index]
Syntax Description
name
|
The name of the filter set.
|
index
|
Delete a specific filter element.
Range: 1-65535 Default: 0
|
Related Commands
addfltset, cnffltset, dspfltset
Attributes
Log: yes
|
State: active
|
Privilege: GROUP1
|
Example
Remove the "connect" filter set from the port.
Geneva.7.PXM.a > delfltset connect
delimagrp
Delete IMA Group—PXM1E
This command deletes an IMA group.
Syntax
delimagrp <group>
Syntax Description
group
|
The group identifier consists of a bay number as well as a group number in the format bay.group, as follows:
• bay: always 2 on the PXM1E
• group: 1-16
|
Related Commands
addimagrp, dspimagrp, dspimagrps, cnfimagrp, rstimagrp
Attributes
Log: yes
|
State: active
|
Privilege: ANYUSER
|
Example
Delete IMA group 6.
MGX8850.7.PXM1E.a > delimagrp 2.6
delimalnk
Delete IMA Link—PXM1E
This command deletes a link from an IMA group.
Syntax
delimalnk <link>
Syntax Description
link
|
The link to be deleted, specified as bay.ds1.
• bay: always 2
• ds1: 1-16
|
Related Commands
dspimagrp, cnfimagrp, rstimagrp, dspimalnk, addimalnk
Attributes
Log: yes
|
State: active
|
Privilege: GROUP1
|
Example
Delete link 16.
MGX8850.7.PXM1E.a > delimalnk 2.16
dellink
Delete Link—PXM45, PXM1E
The dellink command lets you remove a link. A link is part of the bulk distribution feature on the SRM-3T3 and SRM-E. See the addlink description for information on bulk mode distribution.
Syntax
dellink <SrmStartLinkIf>
Syntax Description
SrmStartLinkIf
|
The format for SrmStartLinkIf is slot.line.link. The SrmStartLinkIf parameter identifies physical and logical elements of the SRM. The slot is logical and refers to the primary SRM slots as well as the standby slots. The physical line is one of three T3s on an SRM-3T3 or an OC3/STM1 on an SRME. The link is the starting T1 or E1 tributary that you intend to make up the link. When planning the link mapping, keep track of the starting tributary. The ranges are as follows:
• The slot is the logical slot depends on the chassis, as follows:
– In an MGX 8850 chassis, slot can be either 15 or 31.
– In an MGX 8830 chassis, slot is 7.
• The line has the following possible ranges:
– For SRM-E, line is 1.
– For SRM-3T3, line has a range of 1-3.
• The range for link depends firstly on the SRM front card and secondly on the tributary type, as follows.
– For SRM-3T3, line has a range of 1-28.
– For SRM-E and tributary type T1, line has a range of 1-84.
For SRM-E and tributary type E1, line has a range of 1-63.
|
Related Commands
addlink, cnflink, dsplink
Attributes
Log: yes
|
State: active
|
Privilege: GROUP1
|
dellnloop
Delete Line Loop—PXM1E
Remove the line loopback state from a line.
Syntax
dellnloop < -ds3 | -e3 | -sonet | -ds1 | -e1 > <bay.line>
Syntax Description
-ds3 -e3 -sonet -ds1 -e1
|
Specifies a DS3, E3, T3, SONET (OC-3c), DS1, or E1 line.
|
bay.line
|
The bay is always 2. The line number can be 1 to the highest line on the back card.
|
Related Commands
addlnloop
Attributes
Log: yes
|
State: active
|
Privilege: GROUP1
|
Example
Deleting a DS3 loopback line.
MGX8850.1.7.PXM1E.a > dellnloop -ds3 2.6 -lpb 3
Line loop-back status will be changed.
Do you want to proceed (Yes/No) ?
dellpback
Delete Loopback—PXM1E
The addlpback command lets you delete a specific loopback that is running on a service module.
Note
In the current release, this command runs on the PXM1E only.
Syntax
dellpback <LSMSlot.Line.Port> <loopbackType> <loopbackCode>
Syntax Description
LSMSlot.Line.Port
|
The fields in the parameter can have the following values:
• LSMslot can have a value in one of the following ranges: 1-6, 9-14, 17-22, or 25-30.
• Line has a range from 1 though the maximum number of lines on the card.
• The Port has a value from 1 though the maximum ports supported by the service module.
|
loopbackType
|
To select a loopback type, enter the number that corresponds to the loopback.
Note In the current release, the SRME does not support payload loopback types.
• 1: farEndLineLoopback
• 2: farEndPayloadLoopback
• 3: remoteLineLoopback
• 4: remotePayloadLoopback
• 5: localLoopback
|
loopbackCode
|
To select a loopback code, type the number that corresponds to the code.
• 1: nonLatchOCUwith1
• 2: nonLatchOCUwithout1
• 3: nonLatchCSU
• 4: nonLatchDSU
• 5: latchDS0Drop
• 6: latchDS0Line
• 7: latchOCU
• 8: latchCSU
• 9: latchDSU
• 10: latchHL96
• 11: v54PN127Polynomial
• 12: lineInband
• 13: lineLoopbackESF
• 14: payloadLoopbackESF
• 15: noCode
• 16: lineLoopbackFEAC
• 17: SmartJackInband
|
Related Commands
addlpback, dspbertcap
Attributes
Log: yes
|
State: active
|
Privilege: GROUP1
|
delncdpclksrc
Delete NCDP Clock Source—PXM45, PXM1E
The delncdpclksrc command lets you delete an NCDP clock source. See the cnfncdp description for details on the Network Clock Distribution Protocol (NCDP).
Syntax
delncdpclksrc <portID> [clocktype <e1 | t1>]
Syntax Description
portid
|
The format of the PNNI physical port identifier can vary, as follows:
• On a PXM45: slot:subslot.port:subport
• On a PXM1E for UNI/NNI back card: slot:subslot.port:subport. On the UNI/NNI back card, the subslot is always 2, but the slot depends on the chassis, as follows:
– In an MGX 8850 chassis, slot is always the logical slot 7.
– In an MGX 8830 chassis, slot is always the logical slot 1.
• On a PXM1E for a narrowband service module (NBSM): slot.port.
For BITS clocks only, portid can be 7.35 or 7.36 in an MGX 8850. In an MGX 8830 chassis, the portid for BITS is either 1.35 or 1.36.
For more details, see the section, "PNNI Format," in "Introduction."
|
clocktype
|
Enter e1 or t1 as needed when the port ID is one of the following:
• 7.35 or 7.36 in an MGX 8950 or MGX 8850 chassis
• 1.35 or 1.36 in an MGX 8830 chassis
If the clock type is the default E1, this parameter is not necessary for port IDs 7.35 or 7.36 (or 1.35.or 1.36).
Default: e1
|
Related Commands
cnfncdp, cnfncdpclksrc, cnfncdpport, dspncdp, dspncdpclksrc, dspncdpclksrcs, dspncdpport, dspncdpports
Attributes
Log: yes
|
State: active
|
Privilege: SUPER_GP
|
delpart
Delete Resource Partition—PXM1E
Note
The delpart and delrscprtn commands are identical. The name `delrscprtn' is consistent with the corresponding command in Release 1 of the MGX 8850 switch. You can use either command.
Syntax
delpart <if_num> <part_id>
Syntax Description
if_num
|
The range for logical interface (or port) numbers is are as follows 1-31.
|
part_id
|
The partition ID number in the range 1-20. Use dspparts (or dsprscprtns) to see all resource partitions if necessary.
|
Related Commands
addpart, cnfpart, dsppart
Attributes
Log: yes
|
State: active
|
Privilege: GROUP1
|
Example
MGX8850.7.PXM1E.a > delpart 1 1
delpnni-node
Delete PNNI Node—PXM45, PXM1E
The delpnni-node command removes a PNNI node from the PNNI network topology. A node that this command deletes can be restored with the related command addpnni-node. Confirm the deletion of nodes with the dsppnni-node command.
Syntax
delpnni-node <node-index>
Syntax Description
node-index
|
The node index indicates the relative level of the logical node within a multi-peer group on the switch. The range is 1-10, and the lowest level is 1.
Range: 1-10 Default: 1
|
Related Commands
addpnni-node, cnfpnni-node, delpnni-node
Attributes
Log: yes
|
State: active
|
Privilege: SUPER_GP
|
Example
Delete the node with the node-index of 3. Execute dsppnni-node and specify a node index of 3. The last line of the d display shows the error "node does not exist," indicating you successfully deleted the node.
SanJose.7.PXM.a > delpnni-node 3
SanJose.7.PXM.a > dsppnni-node 3
Syntax: dsppnni-node [node-index]
nodeIndex -- node-index: 32 bit number starting from 1, Optional parameter
delpnni-summary-addr
Delete PNNI Summary Address—PXM45, PXM1E
The delpnni-summary-addr command deletes a PNNI summary address for a PNNI node.
Syntax
delpnni-summary-addr <node-index> <address-prefix> <prefix-length>
Syntax Description
node-index
|
The node index indicates the relative level of the logical node within a multi-peer group on the switch. The range is 1-10, and the lowest level is 1.
Range: 1-10 Default: 1
|
address-prefix
|
The PNNI summary address.
Default: none
|
prefix-length
|
The length of the address-prefix in bits is less than or equal to 152.
Default: none
|
Related Commands
addpnni-summary-addr, dsppnni-summary-addr
Attributes
Log: yes
|
State: active
|
Privilege: SUPER_GP
|
Example
Delete a summary address, as follows:
•
The node-index is 1.
•
The node address prefix is 47.0091.8100.0000.0030.9409.f1f1.
•
The length of the address prefix is 104 bits.
If necessary, use dsppnni-summary-addr to confirm the deletion.
SanJose.7.PXM.a > delpnni-summary-addr 1 47.0091.8100.0000.0030.9409.f1f1 104
delpnport
Delete PNNI Port—PXM45, PXM1E
The delpnport command lets you remove a UNI or NNI port from the controller. It is allowed only if the PNNI port does not exist on the switch i.e, the PNNI partition associated with the port is removed. If the controller does no provisioning on the port in the Plug and Play Scenario, then the PNNI port on the controller is removed if you remove the PNNI Partition on the switch.
Syntax
delpnport <portid>
Syntax Description
portid
|
The format of the PNNI physical port identifier can vary, as follows:
• On a PXM45: slot:subslot.port:subport
• On a PXM1E for UNI/NNI back card: slot:subslot.port:subport. On the UNI/NNI back card, the subslot is always 2, but the slot depends on the chassis, as follows:
– In an MGX 8850 chassis, slot is always the logical slot 7.
– In an MGX 8830 chassis, slot is always the logical slot 1.
• On a PXM1E for a narrowband service module (NBSM): slot.port.
For more details, see the section, "PNNI Format," in "Introduction."
|
Related Commands
addpnport, uppnport, dnpnport, dsppnport
Attributes
Log: yes
|
State: active
|
Privilege: GROUP1
|
Example
Delete port 11:2.8:28 from the switch.
Geneva.7.PXM.a > delpnport 11:2.8:28
delpnportacc
Delete Port Access—PXM45, PXM1E
Removes an address access filter group from a port.
Syntax
delpnportacc <portid> {in | out}
Syntax Description
portid
|
The format of the PNNI physical port identifier can vary, as follows:
• On a PXM45: slot:subslot.port:subport
• On a PXM1E for UNI/NNI back card: slot:subslot.port:subport. On the UNI/NNI back card, the subslot is always 2, but the slot depends on the chassis, as follows:
– In an MGX 8850 chassis, slot is always the logical slot 7.
– In an MGX 8830 chassis, slot is always the logical slot 1.
• On a PXM1E for a narrowband service module (NBSM): slot.port.
For more details, see the section, "PNNI Format," in "Introduction."
|
in
|
Delete incoming access group for the port.
|
out
|
Delete outgoing access group for the port.
|
Related Commands
cnfpnportacc
Attributes
Log: yes
|
State: active
|
Privilege: GROUP1
|
Example
Delete the filter group for incoming calls from port 11:2.8:28.
Geneva.7.PXM.a > delpnportacc 11:2.8:28 in
delport
Delete Port—PXM1E
Remove a logical port from a service module. You must delete all connections and resource partitions on the port before you can delete it.
Syntax
delport <ifNum>
Syntax Description
ifNum
|
The range for logical interface (or port) numbers is are as follows 1-31.
|
Related Commands
addport, cnfport, dspport, dspports
Attributes
Log: yes
|
State: active
|
Privilege: GROUP1
|
delpref
Delete Preferred Route—PXM45, PXM1E
The delpref command lets you delete a preferred route description. For you to do so, no SPVCs can have the preffered route currently associated with them. For detailed information about preferred routes, see the addpref description.
Syntax
delpref <route-id>
Syntax Description
route-id
|
The route ID indicates the preferred route.
Range: 1-5000
Default: none
|
Related Commands
addpref, dsppref, dspprefs, modpref
Attributes
Log: yes
|
State: active
|
Privilege: GROUP1
|
Example
delprfx
Delete Prefix—PXM45, PXM1E
The delprfx command lets you delete an ILMI address prefix associated with a UNI, IISP, or AINI.
Syntax
delprfx <portid> <atm-prefix>
Syntax Description
portid
|
The format of the PNNI physical port identifier can vary, as follows:
• On a PXM45: slot:subslot.port:subport
• On a PXM1E for UNI/NNI back card: slot:subslot.port:subport. On the UNI/NNI back card, the subslot is always 2, but the slot depends on the chassis, as follows:
– In an MGX 8850 chassis, slot is always the logical slot 7.
– In an MGX 8830 chassis, slot is always the logical slot 1.
• On a PXM1E for a narrowband service module (NBSM): slot.port.
For more details, see the section, "PNNI Format," in "Introduction."
|
atm-prefix
|
A 13-byte ATM address prefix, specified as 26 hexadecimal characters.
|
Related Commands
addprfx, dspprfx
Attributes
Log: yes
|
State: active
|
Privilege: GROUP1
|
Examples
Delete ATM prefix 47.0091.8100.0000.0000.0ca7.9e01 from PNNI physical port 3:1.1:1. Display prefixes for this port.
M8850_NY.7.PXM.a > delprfx 3:1.1:1 47.0091.8100.0000.0000.0ca7.9e01
M8850_NY.7.PXM.a > dspprfx 3:1.1:1
INFO: No Prefix registered
delred
Delete Redundancy—PXM1E
The delred command lets you delete the redundancy between a pair of card slots. It applies to 1:1 and 1:N redundancy.
Note
1:N redundancy requires a Service Resource Module (SRM-3T3/C or SRME) in the switch.
In the current release, only the PXM1E supports SRMs.
The higher speed cards support only 1:1 redundancy. The T1 and E1 service modules can have 1:N redundancy provided by an SRM. When you delete redundancy, the switch resets the primary card.
Syntax
delred <redPrimarySlotNumber>
Syntax Description
redPrimarySlotNumber
|
The range of slot numbers for the primary depend on the node, as follows:
• MGX 8950 node (PXM45): 1-6 and 11-16
• MGX 8850 node (PXM45): 1-6 and 9-14
• MGX 8850 node (PXM1E): 1-6, 9-14, 17-22, and 25-30
• MGX 8830 node (PXM1E): 3-6 and 10-13
|
Related Commands
addred, dspred, switchredcd
delrscprtn
Delete Resource Partition—PXM1E
Delete a resource partition. Note that you must delete all connections in the resource partition before you delete it. For information on resource partitions, refer to the description of addrscprtn.
Syntax
delrscprtn <if_num> <part_id>
Syntax Description
if_num
|
The range for logical interface (port) numbers is 1-31.
|
part_id
|
The partition ID number in the range 1-20. Use dsprscprtns to see all resource partitions if necessary.
|
Related Commands
addrscprtn, dsprscprtns, delpart, addpart, dsppart
Attributes
Log: yes
|
State: active
|
Privilege: GROUP1
|
Example
MGX8850.7.PXM1E.a > delrscprtn 1 1
delsct
Delete Service Class Temple—PXM45, PXM1E
The delsct command completely removes a service class template (SCT) from the switch. For an SCT that already operates at the port or card level, this command has no immediate effect. The purpose of this command is to remove excess or unused SCTs.
Before the operation proceeds to completion, the system prompts you with a warning, as follows:
Note
"Warning: this SCT may be in use on the service modules or the PXM1E. Please verify SCT usage on these cards by using the dspports command. After a reset, cards may revert to default SCT if the provisioned SCT is not found. Do you want to proceed (Yes/No)?"
Syntax
delsct <cardtype> <scttype> <sctid> <majorversion>
Syntax Description
-cardtype
|
The cardtype parameter is an integer that refers to one of the following:
• 1: AXSM
• 2: AXSM-E
• 3: PXM1E
• 4: FRSM12
|
-scttype
|
The scttype parameter identifies either a port-level or a card-level SCT, as follows:
• 1: Port-level SCT
• 2: Card-level SCT
Default: None
|
-sctid
|
The range is 1-65535.
Default: none
|
-majorversion
|
The range is 1-65535.
Default: none
|
Related Commands
addsct, cnfsct, dspscts, setsctver, addport, cnfport, dspport, cnfcdsct, dspportsct, dspcdsct, dspsct
Attributes
Log: yes
|
State: active
|
Privilege: GROUP1
|
Example
Delete port-level SCT 1 for AXSM card types. When prompted with a warning, abort the operation.
D1.7.PXM.a > delsct 1 1 1 1
Warning: this SCT may be in use on the service modules or the PXM1E. Please verify SCT
usage on these cards by using the dspports command. After a reset, cards may revert to
default SCT if the provisioned SCT is not found.
Do you want to proceed (Yes/No)? n
delsesn
Delete Session—PXM45, PXM1E
The delsesn command lets you terminate one or more user-sessions. To see the number of the each active session, use the dspsesn command. Termination takes place immediately upon command execution. Before it proceeds, the CLI warns you that the command is destructive. If you proceed with the deletion, the user whose session is being deleted receives the message, "Forced Logout By <userid> !!!!!!!!!!!," where userid is the user running the delsesn command. Note that you can delete any user-session with this command.
Syntax
delsesn {<sesn no> | <sesn no> <sesn no> .... | all }
Syntax Description
sesn no
|
The session number has a range of 1-15. You can specify one session, a series of user sessions, or all user sessions. The dspsesn command displays the user-session numbers.
|
Related Commands
dspsesn, who
Attributes
Log: yes
|
State: active, standby, init
|
Privilege: SERVICE_GP
|
Example
Use the dspsesn command to determine the existing user-sessions. Delete session 2 (user "david9"), then repeat the dspsesn command. Note that the dspsesn output provides a form of the user-session number that delsesn requires: "Session 2."
M8850_NY.7.PXM.a > M8850_NY.7.PXM.a > dspsesn
Port Slot Idle UserId From
-------------------------------------------------------------
telnet.01 * 7 0:00:00 david 10.19.238.35
telnet.02 7 0:00:18 david9 10.19.238.35
M8850_NY.7.PXM.a > M8850_NY.7.PXM.a > dspsesn
-----------------------------------------
-----------------------------------------
Executing command: dspsesn
-----------------------------------------
Waiting for user input...
M8850_NY.7.PXM.a > delsesn 2
WARNING! delsesn is a destructive command it will
non-gracefully delete sessions selected by you
Do you wish to proceed ? [y/n] y
M8850_NY.7.PXM.a > dspsesn
-----------------------------------------
-----------------------------------------
Executing command: dspsesn
delsigdiag
Delete Signaling Diagnostic—PXM45, PXM1E
Removes a signaling diagnostics filter table entry or removes some configuration values within a filter table entry.
Syntax
delsigdiag [index] [-cldaddr nsap-address] [-clgaddr nsap-address] [-cldaddrmask {yes | no}] [-clgaddrmask {yes | no}] [-casttype {yes | no}] [-clrcause {yes | no}] [-connctgy {yes | no}] [-inport {yes | no}] [-outport {yes | no}] [-maxrec {yes | no}] [-scope {yes | no}] [-servctgy {yes | no}]
Syntax Description
index
|
Specifies the diagnostics index number for the filter table. If no other keywords are entered, the indexed filter table entry is deleted.
Range: 1-50
|
-cldaddr
|
Removes the configured called address from the filter entry.
|
-clgaddr
|
Removes the configured calling address from the filter entry.
|
-cldaddrmask
|
yes returns the called address mask to the default.
Default: no
|
-clgaddrmask
|
yes returns the calling address mask to the default.
Default: no
|
-casttype
|
yes to disable filtering by connection type.
Default: no
|
-clrcause
|
yes to disable filtering by the release cause code.
Default: no
|
-connctgy
|
yes returns the connection category to the default.
Default: no
|
-inport
|
yes returns the incoming port to the default.
Default: no
|
-outport
|
yes returns the outgoing port to the default.
Default: no
|
-maxrec
|
yes returns the maximum records to the default.
Default: no
|
-scope
|
yes to disable filtering by scope.
Default: no
|
-servctgy
|
yes returns the service category to the default.
Default: no
|
Related Commands
cnfsigdiag, delsigdiag, dspsigstats, clrsigstats
Attributes
Log: yes
|
State: active
|
Privilege: ANYUSER
|
delslotlink
Delete Slot Link—PXM1E
The delslotlink command lets you delete either one link or all links between an SRM and a service module. See the addlink description for details on bulk mode distribution.
Syntax
delslotlink <SM SlotNum> < SM LineNum>
Syntax Description
SM SlotNum
|
The SM SlotNum parameter identifies the slot number of the service module. Possible entries depend on the chassis, as follows:
• MGX 8850: 1-6, 9-14, 17-22, 25-30
• MGX 8830: 3-6 8-13
|
SM LineNum
|
The SM LineNum parameter identifies a particular line or all lines, as follows:
• 0: all links
• 1-8: the number of the individual line
|
Related Commands
addlink, cnflink, dsplink, dspslotlink
Attributes
Log: yes
|
State: active
|
Privilege: ANYUSER
|
delsntprmtsvr
Delete SNTP Remote Server-—PXM45, PXM1E
The delsntprmtsvr command lets you delete the role of a remote switch as an SNTP server. Alternatively, you can delete all servers from the list of SNTP servers.
Syntax
delsntprmtsvr {server IP address} | all
Syntax Description
server IP address
all
|
Specify the IP address of one switch to remove it from the list of servers, or type "all" to clear the entire list of servers.
|
Related Commands
addsntprmtsvr, cnfsntprmtsvr, dspsntprmtsvr, dspsntp, cnfsntp
Attributes
Log: yes
|
State: active
|
Privilege: GROUP1
|
deltopond
Delete Node From Persistent Topology Database—PXM45, PXM1E
The deltopond command deletes a single node from the persistent topology database.
Syntax
deltopond <nodeIndex>
Syntax Description
nodeIndex
|
Provide the current node's index to delete it from the persistent topology database. To see a list of all indexes and nodes, use the dsptopondlist command.
|
Related Command
cnftopogw, dsptopogw, dsptopogwndlist, dsptopondlist
Attributes
Log: yes
|
State: active
|
Privilege: SUPER_GP
|
deltrapmgr
Delete Trap Manager—PXM45, PXM1E
Delete a trap manager. The deltrapmgr command requires an IP address for deletion. To see existing trap managers, use dsptrapmgr.
For more information about trap managers, see one of the following documentation sources:
•
The Cisco MGX 8850 (PXM45) and MGX 8950 Software Configuration Guide
•
The Cisco MGX 8850 (PXM1E) and MGX 8830 Software Configuration Guide
•
The addtrapmgr description
Syntax
deltrapmgr <ip_addr>
Syntax Description
ip_addr
|
IP address in dotted decimal format:
nnn.nnn.nnn.nnn, n=0-9 and nnn < 256
|
Related Commands
addtrapmgr, dsptrapmgr
Attributes
Log: yes
|
State: active
|
Privilege: SUPER_GP
|
Example
Delete trap manager with IP address 161.10.144.56.
node501.7.PXM.a > deltrapmgr 161.10.144.56
deluser
Delete User—PXM45, PXM1E
Removes a user from the list of users on a node. The system does not allow you to delete a user with a privilege level higher than the level at which you execute the command. For example, if the current user privilege is 2 (GROUP2), you cannot delete a user at level 1 (GROUP1). See the adduser description for the user-privilege hierarchy. No screen output appears unless an error occurs.
Syntax
deluser <user ID>
Syntax Description
user ID
|
User name, consisting of up to 12 characters.
|
Related Commands
dspusers, adduser
Attributes
Log: yes
|
State: active
|
Privilege: GROUP1
|
disablesscop
Disable SSCOP—PXM45
The disablesscop command lets you disable SSCOP on a port. The port must be administratively down (by the dnpnport command). Be sure a valid and useful reason exists for disabling SSCOP.
Syntax
disablesscop <portid> {yes | no}
Syntax Description
portid
|
The format of the PNNI physical port identifier can vary, as follows:
• On a PXM45: slot:subslot.port:subport
• On a PXM1E for UNI/NNI back card: slot:subslot.port:subport. On the UNI/NNI back card, the subslot is always 2, but the slot depends on the chassis, as follows:
– In an MGX 8850 chassis, slot is always the logical slot 7.
– In an MGX 8830 chassis, slot is always the logical slot 1.
• On a PXM1E for a narrowband service module (NBSM): slot.port.
For more details, see the section, "PNNI Format," in "Introduction."
|
yes or no
|
The choice for disabling or enabling SSCOP on the port:
• yes means disable SSCOP.
• no means enable SSCOP.
Default: no (enable SSCOP on the specified port)
|
Related Commands
cnfsscop, dspsscop, dspsscopstats
Attributes
Log: no
|
State: active
|
Privilege: GROUP1
|
Example
Disable SSCOP on port 11:2.8:28.
Geneva.7.PXM.a > disablesscop 11:2.8:28 yes
dncon
Down Connection—PXM1E
Administratively deactivates (or "downs") so you can modify or troubleshoot the network. This operation applies to only SPVCs. To reactivate the connection, use upcon.
Syntax
dncon <ifNum> <vpi> <vci>
Syntax Description
ifNum
|
The range for logical interface (or port) numbers is are as follows 1-31.
|
vpi
|
Virtual path identifier. On a UNI, the range is 0-255. On an NNI, the range is 0-4095.
|
vci
|
For a virtual connection (VCC) on a UNI, the range is 1-4095. On an NNI or VNNI, the VCI range is 1-65535. For MPLS, the recommended minimum VCI is 35.
For a virtual path connection (VPC), the VCI is always 0.
|
Related Commands
upcon
Attributes
Log: yes
|
State: active
|
Privilege: GROUP1
|
dnimagrp
Down IMA Group—PXM1E
This command administratively disables an IMA group.
The order of commands for downing and upping an IMA group is as follows:
1.
dnimagrp
2.
upimagrp
3.
rstrtimagrp
Syntax
dnimagrp <group>
Syntax Description
group
|
The group identifier consists of a bay number as well as a group number in the format bay.group, as follows:
• bay: always 2 on the PXM1E
• group: 1-16
|
Related Commands
upimagrp
Attributes
Log: no
|
State: active
|
Privilege: ANYUSER
|
Example
Disable IMA group number 16.
MGX8850.7.PXM1E.a > dnimagrp 2.16
dnilmi
Down ILMI—PXM1E
The dnilmi command lets you de-activate (down) ILMI on a logical port so you can modify a configuration, troubleshoot, or run certain commands that require ILMI to be inoperative.
Syntax
dnilmi <ifNum> <partId>
Syntax Description
ifNum
|
The range for logical interface (or port) numbers is are as follows 1-31.
|
partId
|
The range for partition ID is 1-20.
|
Related Commands
dspilmi, dspilmis, upilmi
Attributes
Log: yes
|
State: active, standby
|
Privilege: SERVICE_GP
|
dnln
Down Line—PXM45, PXM1E
On a PXM1E, the dnln command de-activates a line on one of two different card types. The line can be on the PXM1E UNI/NNI back card or on a service resource module (SRME or SRM-3T3). A dnln command also runs on the AXSMs in a switch with a PXM45. See the other dnln description for details.
Note
On the CLI of the PXM45, the dnln command appears but is not supported in the current release.
Syntax
dnln <X>.<line>
Syntax Description
X
|
X identifies the card. For SRMs, X differs in an MGX 8850 and MGX 8830 chassis:
X = 2 identifies the UNI/NNI back card on the PXM1E
X = 15 or 31 identifies an SRM in an MGX 8850 chassis (includes redundant cards in 16 or 32)
X = 7 identifies an SRM in an MGX 8830 chassis (includes redundant card in slot 14)
|
line
|
The range for line numbers depends on the card type and is from 1 to the highest numbered line on the back card, as follows:
• PXM1E back card: 1-16
• SRM-3T3: 1-3
• SRME: 1
|
Related Commands
dspln, dsplns, cnfln, upln
Attributes
Log: yes
|
State: active
|
Privilege: GROUP1
|
Example
Down line 1 on the back card of the PXM1E.
MGX8850.7.PXM1E.a > dnln 2.1
dnpnport
Down PNNI Port—PXM45, PXM1E
The dnpnport command takes a UNI or NNI port out of service (administratively "downs" a port). For example, downing a port is necessary for certain provisioning activity or maintenance activity. Where appropriate, the applicable commands state that you must down a port by using dnpnport.
Note
This command deletes all connections on a port—except for SPVCs whose endpoints are on the port.
Syntax
dnpnport <portid>
Syntax Description
portid
|
The format of the PNNI physical port identifier can vary, as follows:
• On a PXM45: slot:subslot.port:subport
• On a PXM1E for UNI/NNI back card: slot:subslot.port:subport. On the UNI/NNI back card, the subslot is always 2, but the slot depends on the chassis, as follows:
– In an MGX 8850 chassis, slot is always the logical slot 7.
– In an MGX 8830 chassis, slot is always the logical slot 1.
• On a PXM1E for a narrowband service module (NBSM): slot.port.
For more details, see the section, "PNNI Format," in "Introduction."
|
Related Commands
addpnport, delpnport, uppnport, dsppnport
Attributes
Log: yes
|
State: active
|
Privilege: GROUP1
|
Examples
Remove port 11:2.8:22 from service.
Geneva.7.PXM.a > dnpnport 11:2.8:28
dnport
Down Port—PXM1E
The dnport command disables (or downs) a logical port and thereby halts all traffic on the logical port. The usual purpose for using dnport is troubleshooting. The configuration for the port remains intact whether the logical port is a UNI or an NNI. The command for enabling a downed port is upport.
For an NNI, the PXM de-routes the failed connections then re-routes them through other trunks. After you re-enable an NNI port through upport, you cannot return the re-routed connections to the upped port. The PXM routes connections over the trunk as needed.
On a UNI, the connections continue to exist, but remain in the failed state until you enable the port by executing upport.
Caution 
On an AXSM-E card, do not use this command unless you want to change the SCT configuration. All connection configurations on the port are lost when you execute this command on the AXSM-E.
Syntax
dnport <ifNum>
Syntax Description
ifNum
|
The range for logical interface (or port) numbers is 1-31.
Use dspports or dspport as needed to determine the need to disable a port.
|
Related Commands
dspport, dspports, upport
Attributes
Log: yes
|
State: active
|
Privilege: GROUP1
|
Example
Disable port 1 on the current card.
MGX8850.7.PXM1E.a > dnport 1
downloadflash
Download Flash—PXM45, PXM1E
The downloadflash command does not execute at the runtime prompt. It operates in bootmode only.
A downloadflash session concludes the sequence of tasks for performing a PXM boot code load. Prior to executing this command, you must access the boot code and transfer the file to the PXM hard drive by using a "put" command). Arguments within the "put" command let you load boot code to any combination of standby or active PXMs. (See Example section for details.) Once firmware is installed in slot 7, the bootcode is mirrored to a new PXM in slot 8 if present. However, to ensure that the boot code is correct, use downloadflash as a manual way to download the boot code to the standby PXM.
Note
Make sure only one version of backup boot code resides in the firmware directory: either delete or rename old versions to ensure that downloadflash uses the correct version.
Syntax
downloadflash
Related Commands
None
Attributes
Log: no
|
State: active, standby
|
Privilege: SUPER_GP
|
Example
Do a PXM45 boot code load. Start with a tftp to the boot code source. Conclude with the download to the standby and the active PXM45. Despite the ".fw" argument in the command string, this is NOT a firmware load. The first lines show an attempt to run downloadflash within the runtime image.
Unknown.7.PXM.a > downloadflash
Error: flash_file supported only at backup boot
> ftp <switch_dest_addr>
> bin
> put <pxm_bkup_version>.fw PINNACLE@PXM45.BT
> quit
wilco.7.PXM.a > downloadflash
•
To place the boot code on the active PXM45 only, use the following "put" string:
>put pxm_bkup_version>.fw PINNACLE@PXM45_ACTIVE.BT
•
To place the boot code on the standby PXM45 only, use the following "put" string:
>put pxm_bkup_version>.fw PINNACLE@PXM45_STANDBY.BT