Table Of Contents
Command Descriptions
This chapter contains the descriptions of all the user-commands that can run on the PXM45/A, PXM45/B, and PXM1E processor cards. The descriptions appear in alphabetical order.
?
? (or Help)—PXM45, PXM1E
Use ? or help to view all commands you can use on the current card and current privilege level. The display does not show commands with a privilege level that is higher than that of the current user.
If you follow the ? with part of a command name, the output shows all commands that contain that string. If you follow the ? with the complete name of one command, the output simply states whether that command is available.
If you can enter two parameter strings, help provides information for each of the two strings separately (not a single, two-part string).
Syntax
? [command]
Syntax Description
Related Commands
help
Attributes
Example
View all commands associated with a partial command entry string.
PXM1E_SJ.7.PXM.a > ? conAvailable commands------------------addconaddcontrollerclrconntracebufferclrconntracebuffersclrpnconclrpnconstatscnfconcnfconprefcnfconsegepcnfintfcongthcnfnodalcongthconntracecopyconsdbgcondelallcondelcondelconsdelconsegepdelcontrollerType <CR> to continue, Q<CR> to stop:abortallsaves
Abort All Saves—PXM45, PXM1E
The abortallsaves command aborts the configuration save process. The configuration save could have begun with either the saveallcnf command or an SNMP-based command. The purpose of abortallsaves is to stop a potentially time-consuming save operation so that you can instead 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 (nearing the maximum number of cards and logical entities). With this narrow context of usefulness, you would not often need to consider using abortallsaves. If the switch is not currently saving the configuration database, the switch displays an appropriate message.
Syntax
abortallsaves
Syntax Description
This command takes no parameters.
Related Commands
saveallcnf, restoreallcnf
Attributes
Example
Abort the current save operation.
pop20one.7.PXM.a > abortallsavesNo Save Process runningabortofflinediag
Abort Offline Diagnostic—PXM1E
Aborts the current offline diagnostics.
Note
See the cnfdiag command for a detailed description of the diagnostics.
Syntax
abortofflinediag <slot>
Syntax Description
Caution
Related Commands
cnfdiag, cnfdiagall, dspdiagcnf
Attributes
Example
abortofflinediag 1abortrev
Abort Revision—PXM45, PXM1E
The abortrev command causes the target card to use the previous operational firmware image. It provides a way out of a graceful upgrade that has shown signs of unacceptable performance. (For example, a new feature may not perform as expected.) The commands for changing firmware versions commands run on the PXM, but they can target either a service module or the PXM itself.
Note
You can run the abortrev command after you have used either the loadrev or runrev command but before using the commitrev command. (After commitrev, the only way to restore the previous version is to force-load it by executing setrev or restoreallcnf.) The following list outlines the sequence for a graceful upgrade. For a state-by-state view that elaborates on this subject, see Table 2-1 and Table 2-2.
1.
2.
3.
4.
Note
A graceful upgrade takes a redundant card pair through different states. In addition, the stage at which you execute abortrev on a redundant pair determines whether the system resets one or both cards in the pair. The reset depends on whether you execute abortrev before or after runrev. The stages of a graceful upgrade and the reset actions appear in Table 2-1 and Table 2-2. For a single-card upgrade, see Table 2-1. For a redundant-pair upgrade, see Table 2-2.
The tables start by showing that, initially, the primary and secondary versions of firmware are 2.x, so the only possible operational version is 2.x. The loadrev command loads a generic version called 2.y, and the upgrade sequence progressively changes the primary and secondary firmware versions.
Note
Note
Syntax
abortrev <slot> <revision>
Syntax Description
slot
Number of the slot where firmware must revert to previous version. In an MGX 8950 switch, the slot number cannot be 9, 10, 25, or 26.
revision
Revision number derived from the name of the firmware file. For an explanation, see the section, "Version Numbering Conventions," in the loadrev description.
Related Commands
loadrev, commitrev, runrev, setrev
Attributes
Example
Abort the graceful upgrade to firmware file pxm45_002.001.070.000_mgx.fw (so 2.1(70) is the version). The system prompts you to confirm that you want the command to proceed.
pinnacle.8.PXM.a > abortrev 8 2.1(70)actaudit
Active Audit—PXM45, PXM1E
The actaudit command lets you enable or disable a certain background process at the node level, This process periodically sends a status enquiry across a link for a very small number of connections to determine whether two peers have the same record of the connection.
Caution
Syntax
actaudit <enable | disable>
Syntax Description
Related Commands
dspactaudit
Attributes
addaddr
Add Address—PXM45, PXM1E
Use addaddr to specify one or more ATM addresses for a port. The port can be a UNI or an IISP port. For each port, the mandatory parameters are an ATM address and the length of that address. For a description of the format of an ATM address and address planning in general, see either of the following books: Cisco MGX 8850 and MGX 8950 Switch Software Configuration Guide (PXM45), Release 3 or Cisco MGX 8850 and MGX 8830 Software Configuration Guide (PXM1E), Release 3.
The optional parameters for addaddr let you specify:
•
•
•
•
•
Note
Creating a Group
In addition to uniquely identifying a port or creating a summary address for multiple ports, you can create a group of PNNI logical ports. (Group addresses can be either ILMI-registered or user-provisioned.) The way to create a group is by assigning the same address for more than one port. These ports can exist on the same switch or throughout the network. The application of such grouping is called "anycast" and depends on the design purposes of the customer.
Creating a group requires two conditions for the ATM address:
•
•
To see the members of a group, use dsppngrpmbrs. To see all ATM addresses that are part of a group, use dsppnallgrpaddr.
Syntax
addaddr <portid> <atm-address> <length> [-type {int | ext}] [-proto {local | static}]
[-plan {e164 | nsap}] [-scope value] [-redst {yes | no}] [-tnid tnid]Syntax Description
portid
The format of the PNNI physical port identifier can vary, as follows:
•
•
–
–
•
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.
•
•
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.
•
20 bytes x 8 bits per byte = 160 bits•
-type
The type of reachability of the node. The reachability is either internal or external. For internal, the address of this port is advertised to only the nodes within the current PNNI network. The default is internal.
The external address can go outside the PNNI network and applies to an IISP link, an AINI link, or a public UNI. For example, the boundary node on the far side of an IISP link must have access to the ATM address of the near-side boundary node to be able to reach the near-side boundary node. Note that, for any ATM address on an IISP port or a public UNI, you must specify external.
Possible entries: "internal" (or just "int"" or "external (or just "ext").
Default: int-proto
The protocol for advertising a reachable address:
•
•
Possible entries: local or static.
Default: local
-plan
The address plan: E.164 or NSAP. If you choose NSAP address, the first byte of the address implies one of the three NSAP address plans: NSAP E.164, NSAP DCC, or NSAP ICD. For example, 47 is reserved for NSAP ICD (see Example section).
Valid entries: e164 or nsap
Default: nsap
-scope
The PNNI hierarchal level to which the address is advertised. In a single peer group (SPG), only `0' applies.
Range: 0-104
Default: 0-redst
Enable for distribution of a static address. Enter "yes" to enable (distribute) or "no" to disable (do not distribute). Enabling this option means that the address you are now adding is visible to all nodes within the PNNI network. Other networks cannot see specific port addresses unless you enable such addresses for distribution.
Default: no
-tnid
The transit network ID identifies a network where connections from the current node do not terminate.This number applies to static addresses only. The application of this option depends on the design intent of the user. The ID can have up to four IA5 characters (IA5 is a superset of the ASCII character set).
Default: (no default for this parameter)
Related Commands
deladdr, deladdrs, dspaddr, dsppngrpmbrs, dsppnallgrpaddr
Attributes
Example
For logical port 11:2.8:28, specify the address that follows. Specify its length in bits (160), and leave all optional parameters in the default state. Use dspaddr to confirm the address. Note that the ICD code differs from the default from Cisco Systems. The address is:
47.0077.6400.0000.0000.0ca7.9e01.4000.0c81.8000.00
Geneva.7.PXM.a > addaddr 11:2.8:28 47.0077.6400.0000.0000.0ca7.9e01.4000.0c81.8000.00 160Geneva.7.PXM.a > dspaddr 11:2.8:2847.0077.6400.0000.0000.0ca7.9e01.4000.0c81.8000.00length: 160 type: internal proto: local scope: 0 plan: nsap_icd redistribute: falsetransit network id:Geneva.7.PXM.a >addapsln
Add APS Line—PXM1E
The addapsln command adds automatic protection switching (APS) to a pair of SONET lines. You can subsequently configure APS by using the cnfapsln command. For example, the default APS mode is unidirectional GR-253 1+1. To change this or other parameters, use cnfapsln.
When you use addapsln on a PXM, the pertinent SONET lines reside on the following card types:
•
•
Note
APS provides line-level redundancy for a pair of SONET lines. The pair consists of a working line and a protection line. During normal operation, the working line is active, and the protection line serves as a backup. The selected architecture mode determines whether the backup line also passes traffic even while it is in standby mode. APS is defined in Bellcore and ITU standards for North American SONET and international Synchronous Digital Hierarchy (SDH) optical network links. The relevant standards are Bellcore GR-253 and ITU-T G.783.
Coordination of APS of line switching relies on an in-band signaling protocol. If the active line is severed or damaged, the signaling protocol must detect the fault within 10 milliseconds. After the protocol has detected the fault, it must switch the user traffic to the standby line within 50 milliseconds.
With the revertive option enabled (by the cnfapsln command, the signaling protocol attempts to switch the traffic back to the working line after the working line becomes available and a waiting period elapses.
Direction
APS can be configured in bidirectional or unidirectional operation (see direction parameter in cnfapsln description). Bidirectional means that both the receiving and transmitting paths are switched upon failure. Unidirectional means that only the interrupted path (receiving or transmitting) is switched.
Intra-card APS
With intra-card (same-card) APS, the working slot and protection slot are the same, but the working line and protection line must be sequential. In the current release, the SRME does not support intra-card APS. The PXM1E supports intra-card APS in bay 2 only. The architecture mode for intra-card APS is 1:1.
Note
Inter-card APS
With inter-card (cross-card) APS, the working slot and the protection slot are adjacent. The working and protection line numbers must be the same. For example, an APS pair could be specified as 7.1.9 and 8.1.9. In the current release, the SRME bay is always 1, and the PXM1E bay is always 2. Note that, for inter-card APS, card redundancy is required but automatic under PXM control.
Summary of Supported Modes
The current release supports the following combinations of modes and electrical connectivity:
•
–
–
•
APS Architecture Modes (archmode)
The current product supports two architecture modes through this command, as follows:
•
•
•
•
–
–
Mini-backplane Requirement for Inter-Card APS on SRME
For inter-card APS, a special mini-backplane is necessary to connect the cards in the following combination of card and chassis:
•
•
Note
Syntax
addapsln <workingIndex> <protectIndex> <archmode>
Note
Syntax Description
In this section, the possible values for slot, bay, and line are given in two formats. The first format is a table (Table 2-3) that sorts out the values for slot and line numbers by chassis type and controller card type. This table also states whether the chassis needs the special APS mini-backplane. The second format is the standard list of parameter definitions. This list contains information in common with Table 2-3.
Related Commands
cnfapsln, delapsln, dspapsln, dspapslns, switchapsln, dspapsbkplane, clrbecnt, dspbecnt
Attributes
Example
On the PXM1E, add intercard APS on line 9 with an archmode of 1+1.
PXM1E_SJ.8.PXM.a > addapsln 7.2.9 8.2.9 1addcon
Add Connection—PXM1E
The addcon command lets you add a connection on the PXM1E. (To add a connection on a service module, use the addcon command on the CLI of that card.) This description contains the details for adding a dual-ended or single-ended SPVC or SPVP. This command does not apply to SVCs or SVPs.
The connection is either a dual-ended connection or a single-ended connection. For a dual-ended connection, you first add the endpoint at the slave-end switch. Upon successful addition of the slave endpoint, the slave-end node generates a 20 octet NSAP address for that endpoint that is used at the master endpoint. The slave endpoint identifier uniquely identifies the endpoint in the network, and you must use this identifier when adding the master endpoint of a dual-ended connection. For a single-ended connection, you add the connection only at the master end.
Note
Before Adding a Connection
Before you can add a connection, note the following tasks:
1.
2.
3.
4.
5.
Adding a Connection
Adding a connection requires you first to provision a slave endpoint. Subsequently, you use addcon to provision a master endpoint. The master endpoint of the connection initiates the routing of the call and can be viewed as the calling party. The slave endpoint is the called endpoint. The following characteristics pertain to this master-slave arrangement:
•
•
To modify the bandwidth parameters or configure usage parameter control (UPC), use cnfcon for all service types. For supported ABR parameters (excluding VS/VD), use the cnfabr command.
Usage Guidelines
The sections that follow describe the application of certain addcon parameters.
Traffic Parameters
Traffic parameters such as PCR, SCR, MBS are entered at both the master and slave endpoints for both the forward and reverse directions. Be sure that the value entered as "local" on one end is equal to the value entered as "remote" on the other end. For example, the lpcr on the slave endpoint should be same as the rpcr on the master endpoint and vice versa when you provision the connection at the other end. If you modify traffic parameters after creating a dual-ended SPVC, you must modify them using the same set of parameters at both the master endpoint and the slave endpoint. For a single-ended connection, modify them at the master endpoint only.
Traffic parameters CDV and CTD are entered at both the master and slave endpoints for both the forward and reverse directions. However, the parameters entered at the slave end are ignored during call setup. Therefore, specify the lcdv, rcdv, lctd and rctd options at the master end only.
Default Traffic Parameters in Service Class Templates
The Service Class Templates (SCTs) provide the default traffic parameters for the logical ports. The default traffic parameters are set to a fraction of the bandwidth available on the logical port. The SCT ID (sctID) and interface type (ifType) parameters that are specified using the addport command determine which default traffic parameters are used.
Note
Note
Routing Parameters
Routing parameter, such as maximum route cost (-mc maxcost) or the routing priority (-rtngprio routingPriority) need to be entered at the master endpoint only.
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. The user-configurable range for a connection is, in descending order of priority, 1-15. The default is 8. See cnfpri-routing for a detailed description of the Priority Routing feature. Also, the cnfpri-routing command lets you configure groups of bandwidth so that the order of routing also reflects the bandwidth requirements of the connection.
A connection created with older software that does not support Priority Routing receives the default priority of 8 after an upgrade. You can modify this priority by using the cnfcon command.
Frame Discard
The current release supports two types of frame discard for VCCs carrying AAL5 cells. These frame discard mechanisms are policing-based and congestion-based. Policing-based discard depends on the -frame option in the addcon or cnfcon command (specified only at the master end). Congestion-based policing for all cell streams is governed by settings in the current port SCT. The two types of frame discard are independent of each other and may or may not coexist.
When policing-based frame discard is enabled, the policer discards all cells of an AAL5 frame that follow a non-compliant cell. Specific actions for PCR and SCR non-compliance are detailed in the section, "Policer Settings and Consequences."
When congestion based frame discard is enabled by the current port-level SCT, if the arriving cells exceed an EPD threshold, the whole frame is discarded.
The table below shows the action applied to a connection according to the frame discard setting. The following information clarifies the table contents:
•
–
–
•
–
–
Restrictions
Frame discard applies to connections that use ATM AAL5 adaptation (ITU-T I.363.5). Although enabling frame discard on an AAL5 cell stream is not mandatory, it helps improve the useful throughput on a VC by discarding complete frames during times of congestion on the switch. Without frame discard enabled on an AA5 cell stream, corrupted AAL5 frames (containing dropped cells) can reach upper layers and trigger numerous re-sends. Conversely, enabling frame discard on other (non-AAL5) types of cell streams can bring uncertain results. In a worst case, total discard of end-to-end traffic of a non-AAL5 stream can occur in either direction.
The hardware does not support frame-based discard on VPCs. Only VCCs support frame-based discard.
Note
Policer Settings and Consequences
This section describes two types of conformance tests that occur when you enable frame discard through this frame discard parameter. The tests are PCR and SCR conformance tests.
The PCR conformance test is performed using GCRA1 in exactly the same manner as normal cell policing. For this test, the Action should be set to discard. If the PCR conformance test is deemed to be non-compliant, the action will be to discard of the cells in the current frame. In other words, a "partial packet action" can be taken when cells in the current frame fail this conformance test. The PCR conformance test implements a partial packet discard (PPD). The policer does a complete frame discard if the first cell of the packet was discarded as a result of PCR failure
The SCR conformance test is performed using GCRA2, although it differs slightly from the normal cell policing.The SCR conformance test is performed only at the start of a frame. If the first cell of a frame is a conforming CLP=0 cell, then all remaining cells will be as if they are conforming to the SCR conformance test. The SCR conformance test can be programmed to tag non-conforming CLP=0 cells. If the first cell of a frame is a non-conforming CLP=0, then that cell and all other cells in that frame (including the EOM) will be tagged. In other words, the tagged action taken by this conformance test is determined at frame boundaries only. If the SCR conformance test is programmed to discard, the policer can discard at any point in the frame and is not restricted by frame boundaries.
Local-Only Parameters
The parameters CDVT, stats enable, (specified using -cdvt, -stat) are significant only at the endpoint where you enter them. Therefore, they can be different at each end of the connection.
Note that cc must be enabled at both ends or disabled at both ends.
Interoperability With Other Switches
The current release supports interoperability with nodes manufactured by other vendors or Cisco ATM WAN switches other than the MGX and BPX families of switches. The other Cisco devices include the LS 1010 switch, DSLAMs such as the Cisco 6160 and Cisco 6250 products, and feeder nodes.
The mechanism that supports this interoperability is the single-ended provisioning of a connection. With single-ended provisioning, you specify both endpoints at the master endpoint only, and the slave endpoint is called a nonpersistent slave endpoint.
In single-ended provisioning, the slave endpoint is not actually provisioned on the far-end service module. The slave endpoint exists only on the PNNI controller on the local node. The slave endpoint is cleared when the connection is derouted by either the dncon command or the clrspvcnonpers command (the delcon command does not apply to non-persistent endpoints).
Specifying a Single-ended Connection
In the current release, a single-ended connection can be added only through the addcon command. CWM currently does not support addition of single-ended connections but only shows these connections.
The single-ended connection is specified at the master endpoint only. The specific parameters that create a single-ended connection are as follows:
•
•
•
When you add a dual-ended connection, command entry for the slave endpoint automatically returns the connection identifier for the slave endpoint. For single-ended connections, you must already have the connection identifier for the non-persistent, slave endpoint. How you get the slave endpoint ID depends on the vendor of the switch, as follows:
•
•
•
To delete a single-ended connection, use the delcon command at the master endpoint. To de-route a single-ended connection, use the clrspvcnonpers command at the slave endpoint.
Overriding a Slave-end SVC or SVP
A routed SVC may have a VPI and VCI at the slave-end port that is needed by an incoming, single-ended connection. Because an existing SVC can take the next available VPI/VCI on the port, you can enable an override of the SVC's VPI/VCI. To override an SVC or SVP use the cnfsvcoverride command.
Limits
For the current release, note the following limitations for single-ended connections.
•
–
–
•
•
•
Syntax
addcon <ifNum> <vpi> <vci> <service type> <mastership> [-slave <NSAP.vpi.vci>] [-lpcr <local PCR>] [-rpcr <remote PCR>] [-lscr <local SCR>] [-rscr <remote SCR>] [-lmbs <local MBS>] [-rmbs <remote MBS>] [-cdvt <local CDVT>] [-lcdv <local maxCDV>]
[-rcdv <remote maxCDV>] [-lctd <local maxCTD>] [-rctd <remote maxCTD>] [-cc <OAM CC Cnfg>] [-stat <Stats Cnfg>] [-frame <frame discard>] [-mc <maximum cost>] [-lputil <local util>] [-rputil <remote util>] [-slavepersflag <slavepers>] [-rtngprio <routingPriority>]
Note
Note
Note
Syntax Description
For the applicable parameters, the "local" end is the point at which you are provisioning the connection.
ifNum
The logical interface (or port) number. This ifNum corresponds to the ifNum added through the addport command. The range is 1-31.
Note
vpi
The range for virtual path identifier (VPI) depends on the interface type, as follows:
•
•
See addport description for details on virtual UNIs or NNIs.
vci
The range for virtual connection identifier (VCI) depends on the interface type, as follows:
•
–
–
–
•
service type
Type a number in the range 1-12 to specify one of the following service types:
•
•
•
•
•
•
•
•
•
•
•
•
mastership
Value to specify the endpoint as master or slave:
•
•
-slave
This parameter specifies the slave-end connection ID (NSAP.vpi.vci). For a dual-ended or single-ended P2P connection, this parameter is mandatory when you are adding a master endpoint (mastership=1). However, -slave is not used at all for a P2MP connection. Note the following:
•
•
-lpcr
Local peak cell rate (PCR). Specifies the PCR from a local endpoint to a remote endpoint (3-5651328 cells per second). PCR is the maximum cell rate for the connection at any time.
-rpcr
Remote peak cell rate (PCR). Specifies the PCR from a remote endpoint to a local endpoint (3-5651328 cells per second). PCR is the maximum cell rate for the connection at any time.
-lscr
Local sustained cell rate (SCR). Specifies the SCR from a local endpoint to a remote endpoint (3-5651328 cells per second). SCR is the maximum cell rate that a connection can sustain for long periods.
-rscr
Remote sustained cell rate (SCR). Specifies the SCR from a remote endpoint to a local endpoint (3-5651328 cells per second). SCR is the maximum cell rate that a connection can sustain for long periods.
-lmbs
Local maximum burst size (MBS). Specifies the MBS from a local endpoint to a remote endpoint (1-5000000 cells). MBS is the maximum number of cells that can burst at the PCR and still be compliant.
-rmbs
Remote maximum burst size (MBS). Specifies the MBS from a remote endpoint to a local endpoint (1-5000000 cells). MBS is the maximum number of cells that can burst at the PCR and still be compliant.
-cdvt
Local cell delay variation tolerance (CDVT). Specifies the CDVT from a local endpoint to a remote endpoint (1-5000000 microseconds). Cell Delay Variation Tolerance controls the time scale over which the PCR is policed.
Note that no remote CDVT is necessary.
-lcdv
The local cell delay variation (CDV) parameter specifies the peak to peak cell delay variation from the local endpoint to the remote endpoint. The range is 1-16777215 microseconds.
-rcdv
The remote cell delay variation (CDV) parameter specifies the peak to peak cell delay variation from the remote endpoint to the local endpoint. The range is 1-16777215 microseconds.
Default: -1
-lctd
Local cell transfer delay (CTD). This parameter specifies the CTD from a local endpoint to a remote endpoint. The range is 0-65535 microseconds.
-rctd
Remote cell transfer delay (CTD). This parameter specifies the CTD from the remote endpoint to the local endpoint. The range is 0-65535 microseconds.
Default: -1
-cc
Operations, administration, and maintenance continuity check (OAM CC): enter 1 to enable or 0 to disable.
To provision continuity checking, enable this function at both ends of the connection, otherwise a connection alarm results. When you add a connection and include this parameter, the connection goes into alarm until both ends of the connection are added.)
Default: 0
-stat
Statistics collection: enter 1 to enable or 0 to disable. The default is 0.
The Cisco WAN Manager tool collects statistics for a connection if you enable it here. Statistics collection is disabled for all connections by default. Statistics collection has an impact (which may not be significant) on the real-time response, especially for SVCs (which can be affected even though you do not add SVCs). Therefore, you should enable statistics collection for only the subset of connections that really warrants such a feature.
-frame
This optional parameter lets you enable or disable frame discard for the connection. See the section, "Frame Discard," for important details on frame discard.
Note
Type a "1" or a "0," as follows:
•
•
Default: disabled
-mc
Maximum cost (maxcost): a value that creates a priority for the connection route. The switch can select a route if the cost does not exceed maxcost. The range for maxcost is 0-4294967295. If you do not specify maxcost, the connection has the highest routing priority by default. Therefore, the maxcost parameter lets you lower the routing priority of a connection. Note the following effects of values in the maxcost range:
•
•
•
Although maxcost applies to an individual connection, routing costs substantially depend on a cost-per-link that you specify at every PNNI logical port in the network. The applicable PNNI command is cnfpnni-intf.
The cost of a route is as follows:
routing cost=sum of all costs-per-link
where:
•
•
The cost-per-link applies to all connections of a particular service type on a port. For example, the cost-per-link is the same for all VBR.1 connections that PNNI controls on a port, and this cost can differ from all UBR.1 connections on the same port. Alternatively, you can use cnfpnni-intf to make the cost-per-link the same for all service types.
To illustrate by examining a four-link route:
1.
2.
3.
The route is usable because the cost of 50240 is less than the maxcost of 100000.
Default: 4294967295 The default makes maxcost meaningless for the connection, so PNNI does not use it as a routing metric.
Note
-lputil
Local Percentage Utilization: Range 1-100. The default is 100.
-rputil
Remote Percentage Utilization: Range 1-100. The default is100.
-slavepersflag
The slave endpoint persistency flag is necessary for setting up a single-ended connection. For details, see the section, "Interoperability With Other Switches."
•
•
Default: persistent
-rtngprio
You can modify the priority of this connection. The range is 1-15. See the cnfpri-routing description for details on this feature.
Default: 8
Error Messages
The system can display error messages for the following reasons:
•
•
•
•
One of the following error messages appears if one of the preceding causes is true:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Related Commands
cnfcon, cnfabr, delcon, clrspvcnonpers, dspcon, dspcons, dncon, upcon, cnfpnportcc, cnfpri-routing, cnfsvcoverride, dspsvcoverride
Attributes
Example
Add the slave end of a VCC on logical port 1 with VPI=10, VCI=40, CBR service type. Note that the system returns the slave end connection identifier in the hexadecimal NSAP format with the VPI.VCI at the end. When you add the master endpoint of the connection, type -slave followed by this connection identifier. You can do a copy and paste rather than typing the whole string.
PXM1E_SJ.7.PXM.a >addcon 1 10 40 1 sslave endpoint added successfullyslave endpoint id: 00000E1000001C008051B730FFFFFF010B180100.10.40In the following two examples, the connection works with default values of PCR, SCT, MCR taken from the SCT. Defaults applied for the connection can be viewed by using the dspcon command.
PXM1E_SJ.7.PXM.a > addcon 1 10 40 1 sslave endpoint added successfullyslave endpoint id : 00000E1000001C008051B730FFFFFF010B180100.10.40PXM1E_SJ.7.PXM.a > addcon 1 10 50 1 m -slave 00000E1000001C008051B730FFFFFF010B180100.10.40master endpoint added successfullymaster endpoint id : 00000E1000001C008051B730FFFFFF010B180100.10.50In the following two examples, the connection works with default values of SCR, MCR derived from the PCR value specified using lpcr and rpcr keywords. Defaults applied for the connection can be viewed by using the dspchan command.
PXM1E_SJ.7.PXM.a > addcon 1 10 40 1 sslave endpoint added successfullyslave endpoint id : 00000E1000001C008051B730FFFFFF010B180100.10.40PXM1E_SJ.7.PXM.a > addcon 1 10 50 1 m -slave 00000E1000001C008051B730FFFFFF010B180100.10.40 -lpcr 1000 -rpcr 1000master endpoint added successfullymaster endpoint id : 00000E1000001C008051B730FFFFFF010B180100.10.50addcontroller
Add Controller—PXM45, PXM1E
The addcontroller command identifies a network control protocol to the switch. If you do not identify a network control protocol (or simply controller), the switch does not use it.
Adding a controller through the addcontroller command requires the following information:
•
•
–
–
Note
If you discover an error in your controller specification after you add it, delete the controller by using delcontroller, then add it again.
Reserved Controller IDs and Controller Types
To support earlier implementations of VSI and legacy service modules, the following combinations of controller ID (ctrlr_id) and controller type (cntrlrType) are reserved:
•
•
•
For a controller ID of 4 or higher, any combination of controller type and controller ID is valid.
Syntax
The syntax differs for internal and external controllers (identified by the "i" and the "x" in the syntax).
Note
Internal controller
addcontroller <cntrlrId> i <cntrlrType> <lslot> [cntrlrName]
External controller:
addcontroller <cntrlrId> x <cntrlrType> <lslot> <bay> <line> <vpi> <vci> [cntrlrName]
Syntax Description for Internal Controller
Syntax Description for External Controller
Note
Related Commands
dspcontrollers, delcontroller
Attributes
Example
Add an internal PNNI controller. The optional controller name is "pnni." No system response appears unless an error occurs.
MGX8850.PXM45.a > addcontroller 2 i 2 7 pnniaddfltset
Add Filter Set—PXM45, PXM1E
The addfltset command lets you create a new filter set or modify the contents of an existing filter set. (A filter controls the access of incoming calls to a port.) Note that, if you want to change the address plan, you must delete the filter set and re-create it. You can assign more than one filter to a port.
Note
Syntax
addfltset <name> [-address atm-address <-length address-length> [-plan {nsap | e164}] [-list {calling | called}]] [-index number] [-accessMode {permit | deny}] [-cgPtyAbsentAction {permit | deny}] [-cdPtyAbsentAction {permit | deny}]
Syntax Description
Related Commands
cnffltset, delfltset, dspfltset, cnfpnportacc
Attributes
Examples
On the port with prefix 47.1111.1111, create address filter "mendocino." The 47 indicates NSAP ICD address plan. Note that the three-dot notation is necessary for the prefix, and the address length of 40 is the 40 bits that make up that hex prefix.
Unknown.1.1.PXM.a > addfltset mendocino -address 47.1111.1111... -length 40 -index 2addimagrp
Add IMA Group—PXM1E
The addimagrp command lets you create a new group for inverse multiplexing over ATM (IMA). In the current release of the PXM1E, the system supports IMA on NNI only. To modify an IMA group, use the cnfimagrp command.
Note
The use of IMA affects the maximum number of connections you can add to a PXM1E UNI/NNI with 16 T1/E1 lines: if all connections are to be in IMA groups, the maximum is 13.5K connections.The order of command usage for the IMA feature and subsequent connection provisioning is as follows:
1.
2.
3.
4.
5.
6.
7.
8.
Syntax
addimagrp <group> <version> <minLinks> <txImaId> <txFrameLen> <txclkMode> <diffDelayMax>
Syntax Description
Related Commands
delimagrp, dspimagrp, dspimagrps, cnfimagrp, rstimagrp, dspimalnk, rstrtimagrp, dspimalnks
Attributes
Example
Add an IMA group with the parameters in the following list, then display the resulting group (whose alarms indicate the far end line has not been upped):
•
•
•
•
•
•
For the display part of this example, see also the dspimagrp description for the details that are not configured through the addimagrp command.
PXM1E-IMA-227.7.PXM.a > addimagrp 2.1 1 1 10 128 1 100PXM1E-IMA-227.7.PXM.a > dspimagrp 2.1Group Number : 2.1NE IMA Version : Version 1.0Group Symmetry : Symm OperationTx Min Num Links : 1Rx Min Num Links : 1NE TX Clk Mode : CTCFE TX Clk Mode : CTCTx Frame Len : 128Rx Frame Len : 128Group GTSM : DownNE Group State : StartUpFE Group State : StartUpGroup Failure Status : Other FailureTx Ima Id : 10Rx Ima Id : 0Max Cell Rate (c/s) : 0Avail Cell Rate (c/s) : 0Diff Delay Max (msecs) : 100Diff Delay Max Observed (msecs) : 0Accumulated Delay (msec) : 0GTSM Up Integ time(msec) : 10000GTSM Dn Integ time(msec) : 2500Num Tx Cfg Links : 0Num Rx Cfg Links : 0Num Act Tx Links : 0Num Act Rx Links : 0Least Delay Link : UnknownTx Timing Ref Link : UnknownRx Timing Ref Link : UnknownGroup Running Secs : 0Alpha Val : 2Beta Val : 2Gamma Val : 1Tx OAM Label : 1Rx OAM Label : 0Test Pattern Procedure Status : DisabledTest Link : UnknownTest Pattern : 255PXM1E-IMA-227.7.PXM.a >addimalnk
Add IMA Link—PXM1E
This command adds an IMA link to an IMA group. You can add up to 16 T1 or E1 links to a group. The link type matches the line type. Each link addition requires one iteration of the addimalnk command.
The order of command usage for the IMA feature and subsequent connection provisioning is as follows:
1.
2.
3.
4.
5.
6.
7.
8.
Syntax
addimalnk <link> <group>
Syntax Description
Related Commands
dspimalnk, dspimalnks, dspimagrp, dspimagrps, cnfimagrp, rstimagrp, delimalnk
Attributes
Examples
In the first example, add one IMA link to group 1, as follows:
1.
2.
3.
4.
5.
PXM1E-IMA-227.7.PXM.a > addimalnk 2.1 2.1ERR:Line is active alreadyPXM1E-IMA-227.7.PXM.a > dnln 2.1PXM1E-IMA-227.7.PXM.a > addimalnk 2.1 2.1PXM1E-IMA-227.7.PXM.a > dsplnsLine Line Line Line Valid AlarmNum State Type Lpbk Intvls State---- ----- --------- ----------- ---------- -------2.1 Up dsx1E1CRCMF NoLoop 0 CriticalIn the second example, add two links to IMA group 2. In this case, group 2 initially does not exist. Display the results first after adding the group then after adding the links.
PXM1E-IMA-227.7.PXM.a > addimalnk 2.2 2.2ERR:IMA group does not existPXM1E-IMA-227.7.PXM.a > addimagrp 2.2 1 2 10 128 1 100PXM1E-IMA-227.7.PXM.a > dspimagrpsIma Min Tx Rx Tx Diff NE-IMA FE-IMA IMAGrp Lnks Frm Frm Clk Delay state state VerLen Len Mode (ms)--------------------------------------------------------------------------------2.1 1 128 128 CTC 100 StartUp StartUp 1.02.2 2 128 32 CTC 100 StartUp StartUp 1.0XM1E-IMA-227.7.PXM.a > addimalnk 2.2 2.2PXM1E-IMA-227.7.PXM.a > addimalnk 2.3 2.2PXM1E-IMA-227.7.PXM.a > dspimalnksLink Grp Rel Ne Ne NeRx Tx RxNum Num Dly Tx Rx Fail Lid Lid(ms) State State Status------------------------------------------------------------------------------2.2 2.2 0 Unusable Not In Grp Lif Fail 1 2552.3 2.2 0 Unusable Not In Grp Lif Fail 2 255addimaport
Add IMA Port—PXM1E
The addimaport command lets you create a new IMA virtual interface.
Note
The order of command usage for the IMA feature and subsequent connection provisioning is as follows:
1.
2.
3.
4.
5.
6.
7.
8.
The maximum bandwidth available on the IMA port is determined by the number of links in the IMA group and the transmission frame length. The following tables can be used to determine the maximum bandwidth for each line type. For T1, see Table 2-6. For E1, see Table 2-7.
Syntax
addimaport <ifNum> <group> <guaranteedRate> <maxRate> <sctID> <ifType> [-vpi <vpi>]
[-minvpi <minvpi>] [-maxvpi <maxvpi>]Syntax Description
Related Commands
dspport, dspports, delport, cnfport, addimagrp
Attributes
Example
Add an IMA port 1 with the following parameters:
•
•
•
•
•
MGX8850.7.PXM1E.a> addimaport 1 2.16 10000 10000 54 2addlink
Add a Link—PXM45, PXM1E
The addlink command applies to bulk mode distribution on a Service Resource Module (SRM-3T3/C or SRME). This command lets you link a number T1 or E1 tributaries within a T3 or OC3/STM1 stream. Note, however, that only the SRME can support bulk distribution to E1 service modules. The SRM-3T3/C or SRME maps these tributaries to lines on a service module.
Note
Note the following characteristics of bulk distribution:
•
•
•
•
Pre-Requisite Tasks for Adding a Link
Before you add a link, the following line-related tasks should be complete:
•
•
The cnfln command configures line-level framing for a T3 or OC3/STM1 line. For SONET-to-T1 mapping on an SRME, you can override the line-level, byte-sync mapping for individual links by using the cnflink command).
Syntax
addlink <SrmStartLinkIf> <NumberOfLinks> <TargetIf>
Syntax Description
Related Commands
cnflink (E1 support on an SRME only), dsplink, dellink, delslotlink
Attributes
Example
For the SRM-3T3/C in slot 15, link the T1 tributaries 4-10 of the second T3 line to T1 lines 2-8 of the service module in slot 11. The breakdown of the parameters is as follows:
•
–
–
–
•
•
Node.1.7.PXM.a> addlink 15.2.4 7 11.2addlnloop
Add Line Loop—PXM1E
Specifies a loopback state for a line on the UNI/NNI back card.
Note
Syntax
addlnloop < -ds3 | -e3 | -sonet | -ds1 | -e1 > <bay.line> <-lpb loopback type>
Syntax Description
Related Commands
dellnloop
Attributes
Example
Add a DS3 line in the local loopback state.
MGX8850.7.pxm1e.a > addlnloop -ds3 1.1 -lpb 2addlpback
Add Loopback—PXM45, PXM1E
The addlpback command lets you start a loopback on a service module that does not have a native loopback capability. This type of loopback requires a Service Resource Module (SRM-3T3/C or SRME). Before starting the loopback, check the ability of the card, line, and port on the service module to support the particular loopback. The dspbertcap command shows what you can configure for a loopback (and BERT, as well).
Note
Syntax
addlpback <LSMSlot.Line.Port> <loopbackType> <loopbackCode>
Syntax Description
Related Commands
dellpback, dspbertcap
Attributes
addpart
Add Resource Partition—PXM1E
The addpart command lets you partition the bandwidth and other resources on a logical port. The entity that makes use of the resources in a partition is a network controller. Currently, the available controllers are the Private Network to Network Interface (PNNI) and the Label Switch Controller (LSC). In the current release of the PXM1E, only PNNI is supported. Before you add a resource partition, have a plan for future changes, such as the addition of a new controller.
A resource partition consists of:
•
•
•
Note
Pre-requisite Tasks for Adding a Partition
Before adding a resource partition, the following tasks must have been completed:
•
•
•
Ports, Partitions, Controllers, and Interface Types
This section contains details regarding ports, partitions, and controllers that you should note before adding a partition.
On each port—regardless of the interface type—you can add one partition for each controller. Therefore, on a port, you can add one partition for PNNI and one for LSC (but keep in mind that the PXM1E currently uses only PNNI). This requirement applies regardless of whether an interface (specified through addport) is UNI, NNI, VUNI, or VNNI.
The pairing of partition ID and controller ID must be the same across all interfaces. In this situation, the interface number uniquely identifies the partition. For example, on a PXM1E-4-OC3 with two UNIs and two NNIs, you could specify:
•
•
•
•
Hypothetically, you could also add partitions on each port for LSC. Such partitions could begin with logical interface 1, partition ID 2, controller ID 3, and so on.
Also note the VPIs and VCIs you add with the addpart command must be within the range specified when the port was created through the addport command,
Syntax
addpart <ifNum> <partId> <ctrlrId> <egrminbw> <egrmaxbw> <ingminbw> <ingmaxbw> <min_vpi> <max_vpi> <min_vci> <max_vci> <minConns> <maxConns>
Syntax Description
For many partition parameters, you can dynamically modify the parameter without administratively downing the port by using the cnfpart or cnfrscprtn command. In contrast, before you can modify the minimum or maximum VPI or VCI, the port must be down (by the dnport command).
Related Commands
cnfpart, delpart, dspparts, dsppart
Attributes
Example
Create a resource partition with the following parameters:
•
•
•
•
•
•
PXM1E-IMA-30.7.PXM.a > addpart 15 1 2 100000 100000 100000 100000 0 255 1 1000 10 1000PXM1E-IMA-30.7.PXM.a > dsppart 15 1Interface Number : 15Partition Id : 1 Number of SPVC: 0Controller Id : 2 Number of SPVP: 0egr Guaranteed bw(.0001percent): 1000000 Number of SVC : 0egr Maximum bw(.0001percent) : 1000000ing Guaranteed bw(.0001percent): 1000000ing Maximum bw(.0001percent) : 1000000min vpi : 0max vpi : 255min vci : 100max vci : 2000guaranteed connections : 10maximum connections : 1000
addpnni-node
Add PNNI Node—PXM45, PXM1E
The addpnni-node command creates an instance of a PNNI logical node on the switch. The maximum number of PNNI logical nodes on a switch is 10. Use addpnni-node to add a node in the following circumstances:
•
•
•
For a single-peer network, you do not initially need to execute addpnni-node
For a multi-peer group, you must execute addpnni-node for each peer group level. For all levels above the lowest level, you need to specify only the level parameter because the ATM address of the lowest level applies to all peer groups in the switch. Use dsppnni-node to view the PNNI node configuration.
To modify an existing PNNI node, use cnfpnni-node. For some of the node parameters, you first must disable the node by executing cnfpnni-node -enable false. The following are applicable parameters:
•
•
•
•
The sections that follow define the preceding fields. Refer to the description of cnfpnni-node for the actual instructions to modify these items. Also, the Syntax Description section for addpnni-node provides details about these parameters.
Address Field Descriptions
The addpnni-node parameters include two types of identifiers and an ATM address that have similar formats. Their contents overlap to varying degrees. The sections that follow describe these parameters.
ATM Address of the Node
A switch-level ATM address consists of:
•
•
•
•
–
–
–
Note
Figure 2-1 Switch-Level ATM Address
PNNI Logical Node Identifier
A PNNI logical node identifier (node ID) consists of:
•
•
•
•
Figure 2-2 PNNI Logical Node Identifier
Peer Group Identifier
A peer group identifier (pgID) consists of:
•
•
Figure 2-3 Peer Group Identifier
Syntax
addpnni-node <level> [lowest | other]] [-atmAddr atm-address] [-nodeId node-id] [-pgId pg-id] [-enable {true | false}] [-transitRestricted {on | off}] [-complexNode{on | off}] [-branchingRestricted {on | off}]
Syntax Description
level
The level specifies the level of the node in a PNNI hierarchy and does so by indicating the number of valid bits for a node ID (-nodeId parameter) or peer group ID (-pg-id parameter). The maximum number of levels you can configure on a switch 10. This limit is meaningful in a multi-peer group only. Although the level can any value, selecting an 8-bit boundary makes network planning and address management easier. Four example, using 56 for a level is more expedient than using a level of 59.
Range: 1-104 bits
Default: 56 bitslowest | other
Indicates whether the logical node you are adding is the lowest node in the hierarchy or exists at a level other than the lowest. Type the entire word "lowest" or "other." If the node you are adding is not the lowest, type the word "other."
If you are adding the node at the lowest level of the switch, you must also specify -atmAdd atm-address.
Default: lowest
-atmAddr
The ATM address of a PNNI logical node consists of 20 hexadecimal, 8-bit bytes.
If you are adding the lowest node in the switch, you must include an ATM address. For all levels above the lowest level, this ATM address is meaningless. The first byte of atm-address indicates the address plan. For example, 47 is reserved for NSAP ICD, as in the following example:
47.00918100000000309409f1f1.00309409f1f1.01.
Default: The Cisco default appears in Figure 2-4.
-nodeId
The PNNI logical node identifier (node ID). The node-id consists of the following logical elements, starting at the most significant byte:
•
•
•
Default: The Cisco default appears in Figure 2-4.
-pgId
The peer group ID (pg-id) identifies a PNNI peer group. (A PNNI peer group consists of all logical nodes with matching pg-ids.)
The number of 8-bit bytes in the peer group ID (pg-id) is 14. However, the value of the level parameter is the number of bits that are actually used for the peer group ID. For example, with the default level of 56 bits (7 bytes), only the first 7 bytes of the peer group ID are relevant. Regardless of the number relevant bytes, the applicable display commands always show 14 bytes for a peer group ID and fill in the irrelevant byte positions with 0s.
Default: The Cisco default appears in Figure 2-4.
-enable
Specify the administrative state of the PNNI node. Most applications use the default—node enabled. However, you can add a node in the disabled state according to the necessities of your implementation. For example, you might want to configure the PNNI protocol but not be ready to enable. Later, you can enable it by executing cnfpnni-node -enable true.
true: Enable this logical node.
false: Disable this logical node.Default: true
-transitRestricted
Specifies whether this node can act as a transit node. You can restrict transit to secure the node or to minimize the traffic on a node that either has low-capacity or is high-priority.
on: Allow calls to transit this node.
off: Allow only call that terminate on this node.Default: off
-complexNode
The complexNode parameter specifies whether the PNNI node is a complex node. Complex nodes exist only above the lowest node in the hierarchy.
on: This node is a complex node.
off: This node is not a complex node.Default: off
-branchingRestricted
The branchingRestricted parameter specifies whether the PNNI node disallows point-to-multipoint branches. To enable or disable branching, this parameter actually turns on or off the restriction:
•
•
on: Do not allow point-to-multipoint branches.
off: Allow point-to-multipoint branches.Default: on
Usage Guidelines
All nodes ship with a default ATM address, node ID, and peer group ID. Cisco uses these defaults to set up and test the switch. Before the switch carries live traffic, you must specify new addresses. For this purpose, you can either use cnfpnni-node or clear the configuration then use addpnni-node. To see an explanation of node-addressing, see the section, "Guidelines for Creating an Address Plan," in either of the following books: Cisco MGX 8850 and MGX 8950 Switch Software Configuration Guide (PXM45), Release 3 or Cisco MGX 8850 and MGX 8830 Software Configuration Guide (PXM1E), Release 3.
Related Commands
cnfpnni-node, delpnni-node, dsppnni-node
Attributes
Example
Add a PNNI node with the following configuration then use dsppnni-node to check the configuration:
•
•
•
•
•
•
•
Enter the parameters in a contiguous line. The CLI allows wrapping (not apparent in the example).
SanJose.7.PXM.a > addpnni-node 56 -lowest true -atmAddr 47.00918100000000309409f1f1.00309409f1f1.01 -nodeId 56:160:47.0091 81000000 00309409f1f1.00309409f1f1.01 -pgId 56:47.00.9181.0000.0000.0000.0000.00 -enable true -transitRestricted offSanJose.7.PXM.a >Display the PNNI node configuration.
SanJose.7.PXM.a > dsppnni-nodenode index: 1 node name: SanJoseLevel............... 56 Lowest.............. trueRestricted transit.. off Complex node........ offBranching restricted onAdmin status........ up Operational status.. upNon-transit for PGL election.. offNode id...............56:160:47.00918100000000309409f1f1.00309409f1f1.01ATM address...........47.00918100000000309409f1f1.00309409f1f1.01Peer group id.........56:47.00.9181.0000.0000.0000.0000.00SanJose.7.PXM.a >
addpnni-summary-addr
Add PNNI Summary Address—PXM45, PXM1E
The addpnni-summary-addr command lets you create a summary address for a logical node. The result of this operation is a range of addresses. The controller uses this summary to accept or reject calls that arrive at an address within the address range. Using a summary address decreases both the provisioning time and the call setup time for an address within the range.
Syntax
addpnni-summary-addr <node-index> <address-prefix> <prefix-length> [-type {internal | exterior}] [-suppress {true | false}]
Syntax Description
The default address prefix and peer group ID share values with the ATM address. If you change the peer group ID, you should change the corresponding fields in the PNNI summary address. (See Figure 2-4.)
Figure 2-4 Defaults for PNNI Peer Group Identifier, PNNI Summary Address, ATM Address, and PNNI Node Identifier
node-index
The node index indicates the relative position of the logical node within a multi-peer group on the switch. The range is 1-10, and the lowest level is 1. If you do not have the node index, use dsppnni-node to see a list of all logical nodes and node indexes on the current switch.
Range: 1-10
Default: 1addressprefix
The summary address assigned to the node. The length of addressprefix is the value of prefixlength.
As shown in Figure 2-4, addressprefix is a formatted hexadecimal string.
Default: The default is the first 13 bytes of the atm-addr.
prefixlength
Specify the length of the address-prefix in bits. The range is 1-152 bits. You configure PNNI routing to look at a specific length in the address, so the length of the PNNI summary address is also configurable. For example, if you configure a node with an 88-bit PNNI summary address, that node sets up a call from any addresses that matches the first 88 bits. The number of addresses that a PNNI summary address can include is inversely related to the length of the PNNI summary address—a shorter summary address can include more addresses than a shorter prefix.
Range: 1-152 bits
Default: none-type
Specify the type of the PNNI summary address, either exterior or internal.
internal: The summary address includes only addresses that are within the peer group.
exterior: The summary address includes addresses that are outside of the peer group.
Default: internal
-suppress
Specify whether the summary address is advertised to other nodes
false: The summary address is advertised (is not suppressed).
true: The summary address is not advertised (is suppressed).Default: false
Usage Guidelines
The PNNI summary address table information comes from the internal data base (IDB). If you change or create a PNNI summary address, a topology state packet carries the information to the IDB. The summary address table updates itself from the IDB.
Related Commands
delpnni-summary-addr, dsppnni-summary-addr
Attributes
Example
This example shows the addpnni-summary-addr command line that adds a PNNI address prefix, configured as follows:
•
•
•
•
Use dsppnni-summary-addr to display the PNNI address prefixes.
SanJose.7.PXM.a > addpnni-summary-addr 1 47.0091.8100.0000.0030.9409.f1f1 104 -type internal -suppress falseSanJose.7.PXM.a > dsppnni-summary-addr 1node index: 1Type.............. internal Suppress.............. falseState............. advertisingSummary address........47.0091.8100.0000.0030.9409.f1f1/104SanJose.7.PXM.a >
addpnport
Add PNNI Port—PXM45, PXM1E
The addpnport command lets you pre-configure an NNI or UNI port. The purpose of pre-configuring is that it may best serve the configuration strategy of some companies.
To pre-configure a port means you add it on the PXM before you add it on the service module (by using addport). Eventually, you must run addport on the service module. The addpnport command is optional because when you create the port by using addport (and a resource partition by using addpart), PNNI automatically creates the port. Therefore, after you create the port on the service module, using the addpnport command is not necessary.
After you pre-configure the port through addpnport at the controller, its administrative and operational states are down by default. Use uppnport to bring up the port.
The addpnport command only creates the port. The PNNI commands for configuring the operational characteristics of the port are cnfpnportrange, cnfpnportcac, and cnfpnportsig. If the configuration you specify with these commands conflict with the values you specify on the service module through the addport or cnfport commands, these PNNI commands override the slave-side configuration.
Note that the format of a PNNI logical port and the format of a logical port on the VSI slave map to each other. See AXSM Format and PNNI Format in "Introduction," for a description.
Syntax
addpnport <portid>
Syntax Description
portid
The format of the PNNI physical port identifier can vary, as follows:
•
•
–
–
•
For more details, see the section, "PNNI Format," in "Introduction."
Related Commands
On the PXM: delpnport, dnpnport, uppnport, dsppnports, dsppnport, cnfpnportcac, cnfpnportsig, cnfpnportrange
On the PXM1E or a service module: addport, cnfport, dspport, dspports
Attributes
Example
Add a port with the ID 6:1.1:1. Use the dsppnports command to see if 6:1.1:1 appears in a list of all ports.(If many PNNI ports already existed, you could use the dsppnport command for 6:1.1:1) It appears at the end of the list—after the entries for BITS clock ports in the format 7.x.
Note that the IF status and the Administrative status are both up. (The IF refers to the logical interface on the service module—the slave side rather than the PNNI controller side.) That IF status and the Administrative status are up indicates that the addpart and addport commands have already been used on the service module. If these commands had not been executed, IF and Admin would be "provisioning" and "down," respectively. For details on the content of the dsppnports command, see its description.
M8850_NY.7.PXM.a > addpnport 6:1.1:1M8850_NY.7.PXM.a > dsppnportsSummary of total connections(p2p=point to point,p2mp=point to multipoint, SpvcD=DAX spvc,SpvcR=Routed spvc)Type #Svcc: #Svpc: #SpvcD: #SpvpD: #SpvcR: #SpvpR: #Total:p2p: 0 0 0 0 0 0 0p2mp: 0 0 0 0 0 0 0Total= 0/50000Summary of total configured SPVC endpointsType #SpvcR #SpvpR #SpvcD #SpvpD Totalp2p: 0 0 2 0 2p2mp: 0 0 0 0 0Total=2Summary of total active SVC/SPVC intermediate endpointsType #Svcc #Svpc #SpvcR #SpvpR Totalp2p: 0 0 0 0 0p2mp: 0 0 0 0 0Total=0EndPoint Grand Total = 2/100000Per-port status summaryPortId LogicalId IF status Admin status ILMI state #Conns7.35 17251107 up up NotApplicable 07.36 17251108 up up NotApplicable 07.37 17251109 up up NotApplicable 07.38 17251110 up up NotApplicable 01:2.1:1 16848897 up up UpAndNormal 02:2.2:1 16914433 provisioning up NotApplicable 03:1.1:1 16979969 down up Disable 03:1.2:2 0 provisioning down NotApplicable 06:1.1:1 17176577 up up Disable 0M8850_NY.7.PXM.a >addport
Add Port—PXM1E
The addport command lets you create a logical interface on an active physical line on the PXM1E network interface back card. (See upln description as needed.) Beginning with Release 4, the PXM1E supports virtual trunking so that it now supports the following interface types:
•
•
Before you add a port to the PXM1E, you may need to consider the PXM1E's capacity to support all ports on all cards in the switch. At the node level, the PXM1E supports the following port totals:
•
•
•
The possible number of ports you can add to the PXM1E itself depends on the port types, as follows:
•
•
The range of port numbers is 1-31 regardless of the port type. The port numbers do not need to follow a sequence.
The information you specify with addport consists of the following:
•
•
•
•
•
•
Service Class Templates
The switch supports a template approach to specifying traffic parameters. The name of such a template is service class template (SCT). This approach is appropriate for configuring traffic parameters for large numbers of connections. You must specify an SCT for each logical port you add with the addport command. On the PXM1E, these templates apply to logical ports. (On the AXSM models and the FRSM-12-T3E3, a card-level SCT also applies to the card as a whole.)
The SCT approach does not cover all parameters of an individual connection. You can specify parameters for an individual connection whether or not the SCT specifies them by using cnfcon.
Cisco Systems provides a variety of SCTs for different applications. The IDs of the supplied SCTs are: 2, 3, 4, 5, 6, 52, 53, 54, and 55. An SCT must have been loaded from a workstation to the PXM disk before you can assign it to a port. See the addsct description for details about SCT management, and use the dspscts command see a list of SCTs already on the PXM hard drive. Until SCTs have been downloaded from a workstation, a port can use the default, placeholder SCT number 0.
The PXM1E supports SCTs for the following applications:
•
•
•
The following two types of tasks may be helpful before you assign SCTs:
•
•
–
–
Until you specify an SCT, the PXM1E has a default SCT of 0. The system uses SCT ID = 0 when:
•
•
Characteristics of Command Usage
Before you use the addport command, note the following important characteristics:
•
•
•
Syntax
addport <ifNum> <bay.line> <guaranteedRate> <maxrate> <sctID> <ifType> [-vpi <vpi>] [-minvpi <minvpi>] [-maxvpi <maxvpi>]
Syntax Description
Note
ifNum
A logical port (interface) number. Only one logical port is allowed if the line operates as a UNI or NNI. For the virtual network to network interface (VNNI), multiple ports can exist on a line.
Range: 1-31
bay.line
Identifies the bay and the number of the line. Possible values are as follows:
bay: always 2
line: 1 to the highest numbered line on the back card.
guaranteedRate
Guaranteed rate on a port in cells per second (CPS). The total guaranteed rates cannot exceed the highest value in the following ranges:
OC3: 50-353207 cps
T3: 50-96000 cps for PLCP or 104268 cps for ADM
E3: 50-80000 cps
T1: 50-3622 cps
E1: 50-4528 cpsmaxRate
Maximum rate on a logical port in cells per second. The total maximum rates cannot exceed the highest value in the following ranges:
OC3: 50-353207 cps
T3: 50-96000 cps for PLCP or 104268 cps for ADM
E3: 50-80000 cps
T1: 50-3622 cps
E1: 50-4528 cpssctID
This parameter identifies an SCT for the port. The range is 0-255. Cisco Systems provides SCT numbers 2, 3, 4, 5, 6, 52, 53, 54, and 55. The SCT must exist on the PXM disk before you can identify it through sctID. (For details on SCT, see also the addsct descriptions.)
•
•
ifType
The logical interface type: for UNI and NNI, only one interface can exist on a line. For virtual interfaces or enhanced virtual interfaces, multiple interfaces can exist on the same line.
1 = UNI
2 = NNI
3 = VNNI (virtual NNI)
4 = VUNI (virtual UNI)
5 = EVUNI (enhanced virtual UNI)
6 = EVNNI (enhanced virtual NNI)Note
-vpi vpi
This optional VPI applies to standard virtual trunks (VNNI or VUNI), as follows:
•
•
-minvpi minvpi
In the current release, this optional parameter applies to EVNNI and EVUNI but is not supported.
-maxvpi maxvpi
In the current release, this optional parameter applies to EVNNI and EVUNI but is not supported.
Related Commands
cnfport, delport, dspport, dspports, dspportsct, dspscts
Attributes
Example
With port-level SCT 4 confirmed on the disk, create logical port 3 on line 3 of bay 1. The minimum and maximum cells per second are the same—96000 cps in this example. The port SCT file ID is 4. The interface type is NNI—specified by the 2 at the end of the command input. Confirm the result.
M8850_NY.7.PXM1E.a > addport 3 1.3 96000 96000 4 2M8850_NY.7.PXM1E.a > dspport 3Interface Number : 3Line Number : 1.3Admin State : Up Operational State : DownGuaranteed bandwidth(cells/sec): 96000 Number of partitions: 0Maximum bandwidth(cells/sec) : 96000 Number of SPVC : 0ifType : NNI Number of SPVP : 0Port SCT Id : 4VPI number(VNNI only) : 0 Number of SVC : 0M8850_NY.7.PXM1E.a >addpref
Add Preferred Route—PXM45, PXM1E
The addpref command lets you define a preferred route. The preferred route feature for PNNI gives you more control over how an SPVC or SPVP is routed in the network. Preferred routes can aid in overall resource allocation and distribution, redundancy planning, and overall traffic engineering.
Each platform has a maximum number of hops that it can record for defining preferred routes, as follows:
•
•
•
Note
Note
Details of the Preferred Routes Feature
If an SPVC has an associated preferred route, the PNNI routing protocol considers that route to be the most desirable route for the connection if that route is available. Alternatively, the connection receives another route according to standard PNNI routing policies if both of the following are true:
•
•
The preferred route feature is optional and applies to only the master endpoints on a switch. Therefore, when you use cnfconpref to associate a preferred route with a connection, do it at the master end of the connection. Also, preferred route is significant to only the local node.
A preferred route consists of a sequential list of nodes and links between nodes that stretch from the local node to the destination node. Each node and link in the preferred route must be within the same peer group as the originating node. A node can appear only once in the preferred route.
In this software release, the following characteristics apply to the preferred routes feature:
•
Note
•
•
•
•
•
•
•
•
•
•
•
•
•
•
The preferred route feature does not affect the following characteristics of the switch:
•
•
•
Syntax
addpref [-name yes | no] [-h1 {<persNodeIndex>/<portId>}]
[-h2 {<persNodeIndex/<portId>}] ... [-h20 {<persNodeIndex>/<portId>}]After PNNI creates the preferred route, the system returns a route index in the range 1-5000. This route index is necessary for the related commands delpref, dsppref, and modpref. To see a list of route indexes, use the dspprefs command.
Syntax Description
-name
A hop in a preferred route can be identified by the pairing of the node name with the port ID rather than the node index with the port ID. (The node name must have been defined through the cnfname command.) If you use node names, the total number of -h(n) keywords you can specify with this command is limited to 10. See the section, "Detailed Usage Guidelines for the addpref Command." To use node names, type -name yes. The choice is yes or no. A no means that the persistent node index is used.
The route definition must contain either all indexes or all node names.
Default: no
-h1, -h2 ... -h20
Including the local node, you can define up to 20 nodes in the preferred route.
Each hop in the preferred route is defined by a pairing of the persistent node index and the PNNI physical port ID. For the last port ID in the route, type a "#" instead of a numeric value. This # appears in the outputs of the display commands for preferred routes. Separate these values by a slash and no spaces, as follows:
persNodeIndex/portid
The node must exist in the persistent topology database. Use dsptopondlist to see the nodes in this database. (An alternate to using node indexes is using node names.)
The format for portid is slot:subslot.port:subport. For a description of each field in the physical port ID, see the section, "PNNI Format," in "Introduction."
Detailed Usage Guidelines for the addpref Command
Before actually using the addpref command, note the following details:
•
•
•
•
•
•
Related Commands
dsppnports, dsppnport, dsptopondlist, cnfconpref, dsppref, dspprefs, delpref, modpref
Attributes
Examples
After confirming the presence of the node indexes 11, 23, 34, and 56 in the persistent topology database, configure a preferred route, as follows:
addpref -h1 112/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 atlanta/1:2.1:9 -h2 newyork/1:1.1:2 -h3 chicago/1:2.1.7 -h4 seattle/#Pref Route ID = 2addprfx
Add Prefix—PXM45, PXM1E
The addprfx command lets you add an ATM prefix for ILMI to a UNI or IISP.
Syntax
addprfx <portid> <atm-prefix>
Syntax Description
portid
The format of the PNNI physical port identifier can vary, as follows:
•
•
–
–
•
For more details, see the section, "PNNI Format," in "Introduction."
atm-prefix
A 13-byte ATM prefix (26 hexadecimal characters).
Related Commands
dspprfx, delprfx
Attributes
Examples
Add prefix47.0091.8100.0000.0000.0ca7.9e01 to PNNI physical port 3:1.1:1. Display ARM address prefixes for this port. Only the one just added exists.
M8850_NY.7.PXM.a > addprfx 3:1.1:1 47.0091.8100.0000.0000.0ca7.9e01M8850_NY.7.PXM.a > dspprfx 3:1.1:1ILMI Configured Port Prefix(es):47.0091.8100.0000.0000.0ca7.9e01M8850_NY.7.PXM.a >addred
Add Redundancy—PXM45, PXM1E
The addred command links two slots to support card-level redundancy for a pair of service modules. When a switch has two PXMs, they are automatically redundant—without the addred command. (Note that on the PXM1E, card-level redundancy is automatic for the UNI/NNI back card and SRMs when card pairs are present. Therefore, addred on the PXM1E applies to narrowband service modules.)
A redundant pair consists of a primary slot and a secondary slot. Both cards must be in the active state for you to configure redundancy. After configuration, the secondary service module goes into the standby state.
The current product supports the following card-level redundancy schemes:
•
•
•
To see the redundancy exists, use dspcd, dspcds, or dspred.
The 1:N redundancy supported by an SRM can be in bulk mode or non-bulk mode. For a description of bulk mode distribution, see the addlink description or its description in either of the following books: Cisco MGX 8850 and MGX 8950 Switch Software Configuration Guide (PXM45), Release 3 or Cisco MGX 8850 and MGX 8830 Software Configuration Guide (PXM1E), Release 3.
For non-bulk mode, note the following:
•
•
The following requirements apply to 1:N redundancy in bulk mode and non-bulk mode:
•
•
•
•
The secondary card does not carry traffic unless a switchover occurs due to one of the following:
•
•
Note
Syntax
addred <redPrimarySlotNum> <redSecondarySlotNum> <RedType>
Syntax Description
Related Commands
dspred, delred, switchredcd
Attributes
Example
Add 1:N redundancy such that slot 5 is the primary, and slot 6 is the secondary slot. Check the results by running the dspred command. In addition to the RPM pairing in slots 5 and 6, the dspred output shows the automatic, redundant pairing of the PXM45s in slots 7 and 8.
Note that the "PXM45-U" indicates that these cards have undergone a firmware upgrade that is running (via the loadrev or runrev command) but not yet committed (via the commitrev command).
rswpop7.8.PXM.a > addred 5 6 2Secondary slot 6 will now run Primary Slot 5 image revisionrswpop7.8.PXM.a > dspredMGX8850 Node Alarm:MAJORPrimary Primary Primary Secondary Secondary Secondary RedundancySlotNum Reserved State SlotNum Reserved State TypeType Type------- -------- ------- --------- --------- --------- ----------5 RPM-PR Active 6 RPM-PR Empty 1:n7 PXM45 Standby-U 8 PXM45 Active-U 1:1addrscprtn
Add Resource Partition—PXM1E
The addrscprtn command lets you partition bandwidth and other resources on a logical port. The entity that makes use of the resources in a partition is a network controller. Currently, the available controllers are the Private Network to Network Interface (PNNI) and the Label Switch Controller (LSC). Before you add a resource partition, have a plan for future changes, such as the addition of a new controller.
A resource partition consists of:
•
•
•
Note
Pre-requisite Tasks for Adding a Partition
Before adding a resource partition, the following tasks must have been completed:
•
•
•
Ports, Partitions, Controllers, and Interface Types
This section contains details regarding ports, partitions, and controllers that you should note before adding a partition.
On each port—regardless of the interface type—you can add one partition for each controller. Therefore, on a port, you can add one partition for PNNI and one for LSC (but keep in mind that the PXM1E currently uses only PNNI). This requirement applies regardless of whether an interface (specified through addport) is UNI, NNI, VUNI, or VNNI.
The pairing of partition ID and controller ID must be the same across all interfaces. In this situation, the interface number uniquely identifies the partition. For example, on a PXM1E-4-OC3 with two UNIs and two NNIs, you could specify:
•
•
•
•
Hypothetically, you could also add partitions on each port for LSC. Such partitions could begin with logical interface 1, partition ID 2, controller ID 3, and so on.
Also note the VPIs and VCIs you add with the addpart command must be within the range specified when the port was created through the addport command,
Syntax
addrscprtn <ifNum> <partId> <ctrlrId> <egrminbw> <egrmaxbw> <ingminbw> <ingmaxbw> <min_vpi> <max_vpi> <min_vci> <max_vci> <minConns> <maxConns>
Syntax Description
For many partition parameters, you can dynamically modify the parameter without administratively downing the port by using the cnfpart or cnfrscprtn command. In contrast, before you can modify the minimum or maximum VPI or VCI, the port must be down (by the dnport command).
Related Commands
cnfrscprtn, delrscprtn, dsprscprtns, dsprscprtn
Attributes
Example
Create a resource partition with the following parameters:
•
•
•
•
•
•
PXM1E-IMA-30.7.PXM.a > addrscprtn 15 1 2 100000 100000 100000 100000 0 255 1 1000 10 1000PXM1E-IMA-30.7.PXM.a > dsprscprtn 15 1Interface Number : 15Partition Id : 1 Number of SPVC: 0Controller Id : 2 Number of SPVP: 0egr Guaranteed bw(.0001percent): 1000000 Number of SVC : 0egr Maximum bw(.0001percent) : 1000000ing Guaranteed bw(.0001percent): 1000000ing Maximum bw(.0001percent) : 1000000min vpi : 0max vpi : 255min vci : 100max vci : 2000guaranteed connections : 10maximum connections : 1000addsct
Add Service Class Template—PXM45, PXM1E
Use the addsct command to register a major version of an SCT on the switch. To register an SCT means that you move the SCT from a temporary directory to a directory that is unique to the card type. In general terms, the move is from the C:SCT/TEMP directory to the F:SCT/card_type directory. From the directory on the F: drive, you can load a port or card SCT to the appropriate destination.
Note that you do not need to specify the path when using the addsct command. Note also that addsct actually moves rather than copies the SCT.
Note
The addsct command is part of a series of tasks for transferring SCTs from a workstation to the switch and then to a card or port. You can perform the task on a network-wide basis through CWM. To perform these tasks on individual witches through the CLI, do the following:
1.
2.
3.
Note
Nodal Configuration, SCTs, and the clrallcnf Command
The presence of SCT files on the PXM's hard drive is a part of the switch's configuration, so these files are deleted by the clrallcnf command. Unless the configuration was saved through the saveallcnf command, you must reinstall SCT files by using the addsct command. Before using the clrallcnf command, consider whether the existing SCT configuration calls for you to run the saveallcnf command before the clrallcnf command.
Syntax
addsct <cardtype> <scttype> <sctId> <majorversion> <checksum>
Syntax Description
Related Commands
delsct, cnfsct, dspscts, setsctver, addport, cnfport, dspport, cnfcdsct, dspportsct, dspcdsct, dspsct
Attributes
Example
Add port SCT 53, version 1, and a checksum of 0x18a4fdad.
Unknown.7.PXM.a > addsct pxm1e card 53, 1 0x18a4fdadInstall card-level, AXSM-E SCT 3, version 1.
p2spvc2.8.PXM.a > addsct 2 2 00003 00001 0x46f6c566 test_modified_version_of_Cisco_SCT_4Install card-level SCT 122 for the AXSM cards.
p2spvc2.8.PXM.a > addsct AXSM CARD 00122 00001 0x6fae1018 feb_1stSCTaddserialif
Add Serial Interface—PXM45, PXM1E
The addserialif command activates a serial port on the PXM45-UI-S3 back card. The two types of serial ports are the console port and the maintenance port. These ports provide user-access for controlling the switch. The default rate on a serial interface is 9600 bits per second, and you can select a different rate for the terminal by running the cnfserialif command.
Each port connects to a different type of terminal implementation. For a description of how to use these physical ports for switch control, refer to either of the following books: Cisco MGX 8850 and MGX 8950 Switch Software Configuration Guide (PXM45), Release 3 or Cisco MGX 8850 and MGX 8830 Software Configuration Guide (PXM1E), Release 3.
Syntax
addserialif <port#>
Syntax Description
Related Commands
cnfserialif, delserialif, dspserialif
Attributes
Example
Activate a console port.
node19.8.PXM.a > addserialif 2addsntprmtsvr
Add SNTP Remote Server—PXM45, PXM1E
The addsntprmtsvr command lets you specify a remote device as a server for Simple Network Time Protocol (SNTP) The remote server can be a CWM workstation or a switch. SNTP synchronizes the time of day (TOD) on client nodes by sending updates to each client switch. You can also specify a remote switch as the primary server or secondary server and specify the version of the network timing protocol.
The addsntprmtsvr command works in tandem with the cnfsntp command. Various related timers are configurable through the cnfsntp command. For the purpose of server redundancy, you can configure an SNTP server to synchronize with a remote SNTP/NTP server by activating the SNTP client. (See the cnfsntp description for details.) To modify the parameters you configure with addsntprmtsvr, use the cnfsntprmtsvr command.
NTP Version 3 and SNTP Version 4
The Simple Network Time Protocol (SNTP) Version 4, which is an adaptation of the Network Time Protocol (NTP), should be used to synchronize TOD in an ATM network.
The Network Time Protocol (NTP) Version 3 specified in RFC 1305 is widely used to synchronize computer clocks in the global internet. It provides comprehensive mechanisms to access national time and frequency dissemination services, organize the time synchronization subnet, and adjust the local clock in each participating subnet peer. In most places of the Internet of today, NTP provides accuracies of 1-50 milliseconds, depending on the characteristics of the synchronization source and network paths.
Syntax
addsntprmtsvr {server IP address} [-version {version}] [-primary {yes | no}]
Syntax Description
Related Commands
cnfsntp, cnfsntprmtsvr, dspsntp, dspsntprmsvr, delsntprmtsvr, dspsntpstats, clrsntpstats, dbgsntp, dspsntp-dbg
Attributes
Example
On the client switch named PXM1E_SJ, register M8850_NY as the primary server by using the addsntprmtsvr command. On the client, display its SNTP status and note that it has synchronized to the server: the "sync" field shows "yes." Note also that the current stratum is 2, which is the stratum of the primary server plus 1. (For the meaning of "stratum" in the SNTP context, see the cnfsntp description.)
PXM1E_SJ.7.PXM.a > addsntprmtsvr 172.29.52.56 -primary yesPXM1E_SJ.7.PXM.a > dspsntpclient: yesserver: nopolling: 64waiting: 5rollback: 1024stratum(default): 5stratum(current): 2sync: yesDisplay the date and time on the client and note its proximity to those of the primary server.
PXM1E_SJ.7.PXM.a > dspdateDec 27 2002 02:41:07 GMTM8850_NY.7.PXM.a > dspdateDec 27 2002 02:41:09 GM
addtrapmgr
Add Trap Manager—PXM45, PXM1E
Set up an SNMP manager that you intend to receive SNMP traps. The maximum number of trap managers on a node is 12.
The trap managers you add through addtrapmgr and the trap managers that are added by the SNMP manager (Cisco WAN Manager or other application) do not age and are not deleted. To delete a trap manager, use either the deltrapmgr command or an SNMP Set on the intended object.
Syntax
addtrapmgr <ip_addr> <portnum>
Syntax Description
Related Commands
deltrapmgr, dsptrapmgr
Attributes
Example
Add a trap manager with IP address 161.10.144.56 to port 50.
node501.7.PXM.a > addtrapmgr 161.10.144.56 50adduser
Add User—PXM45, PXM1E
The adduser command lets you add a user account with associated name, privilege level, and password to the local database. The maximum number of user accounts on a switch is 100.
The privilege of the user you are adding must be lower than the user-level at which you use adduser. For example, to add a user with a privilege of GROUP1, you must log at SUPER_GP or above.
The commands available to a particular user have either the same or a lower privilege level than that of the user-account. With SUPER_GP access, for example, you can use commands that require SUPER_GP, GROUP1, or ANYUSER privilege. The minimum access level for a command appears in the Attributes section of each description.
In descending order of access privilege:
•
•
•
•
•
Syntax
adduser <user ID> <accessLevel>
Syntax Description
After you enter a user ID and access level, the system prompts for a password, as the example shows.
Related Commands
cnfuser, dspusers, deluser, cnfpasswd, whoami
Attributes
Example
Add a user named "fin" with privilege level GROUP1. To add a GROUP1 user, the current user-prefilter level must be SUPER_GP or higher. To determine the current username, execute the whoami command. To see all current privilege levels, execute dspusers.
If the privilege level of the current user in this example is GROUP1 or lower, the command fails after you enter the password for the second time, and the system returns a message stating that you entered an incoherent value for "-l " (the level).
pinnacle.7.PXM.a > adduser fin GROUP1Enter password:Re-enter password:Add the user "leroy" but without establishing a password for "leroy." The system displays the default password "newuser." Subsequently, either a network administrator or the user "leroy" can execute the cnfpasswd command to create a password.
pop20two.7.PXM.a > adduser leroy ANYUSEREnter password:(default password "newuser" will be used)aesa_ping
ATM End Station Address Ping—PXM45, PXM1E
The aesa_ping command contacts any ATM end station address (AESA) connected to a PNNI network. Use this command to check PNNI connectivity to the given destination address. You can use the optional arguments -setupcall, -qos, -trace, and -data to send packets and provide greater granularity to the information that the command sends to the screen.
The parameters that you enter in the aesa_ping command don't specify anything except the execution of the command itself. All behaviors started by the command stop when the interval -timeout expires.
Syntax
aesa_ping <destination address> [-setupcall {yes/no} ] [-qos {ubr | abr | cbr | vbr_rt | vbr_nrt}]
[-pcr {peak cell rate}] [-scr {sustain cell rate}] [-trace {yes/no}] [-timeout {time out in secs}]
[-data {yes/no}] [-interval {time}]Syntax Description
Related Commands
dsppingatmaddr
Attributes
Example
This example shows the aesa_ping command line that pings the ATM end station with the address 47.00918100000000d058ac23ac.00d058ac23ac.01. The ping is configured as follows:
•
•
•
•
•
•
•
•
SanJose.7.PXM.a > aesa_ping 47.00918100000000d058ac23ac.00d058ac23ac.01 -setupcall no -qos ubr -trace no -data disable -timeout 6 -interval 60 -pcr 5 -scr 5Ping 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:262656DTL 1:NODE 2::56:160:71:0:145::88:172:35:172:Port 2:0Port List :no of ports = 1Port ID 1:262656SanJose.7.PXM.a >bootchange
Boot Change—PXM45, PXM1E
The bootchange command lets you configure the boot IP address and gateway address of the PXM's Ethernet interface.
The Ethernet interface is multi-purpose. It serves as the boot interface for the PXM during boot-up, and it serves the interface to network management software during regular operation. To accomplish this dual purpose, two types of Ethernet IP addresses need to be configured on the PXM, as follows:
•
•
Note
Applicable Parameters
Currently, the only parameters you should enter are as follows:
•
•
•
•
The bootchange command presents one parameter at a time. (The Example shows the screen layout.) To skip a field that you should not specify, press the Return or Enter key without typing a value at the prompt. To see the current configuration, use the bootchange command without changing parameters as you skip through the fields.
Characteristics of Boot IP Address Support
Note the following details about how the switch manages a boot IP address;
•
•
•
•
•
•
•
•
•
•
Syntax
bootchange
Related Commands
ipifconfig
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. For all fields except the ethernet and gateway prompts, press Return or Enter.
pinnacle.7.PXM.a > bootchange'.' = clear field; '-' = go to previous field; ^D = quitboot device : lnPciprocessor number : 0host name : winterfile name : /users/joloughl/pxm45_002.000.014-A1.fwinet on ethernet (e) : 170.11.52.61inet on backplane (b):host inet (h) : 170.11.25.42gateway inet (g) : 170.11.52.2user (u) : rliftp password (pw) (blank = use rsh):flags (f) : 0x0target name (tn) : pxm45-71startup script (s) :other (o) :burnboot
Burn Boot Software—PXM45, PXM1E
The burnboot command lets you burn a boot software revision onto a standby card. The applicable card types are as follows:
•
•
•
•
Note the following characteristics of the burnboot command:
•
•
•
Note
Syntax
burnboot <slot> <revision> [-force]
Syntax Description
Related Commands
None
Attributes
Examples
In the first example, the target is the service module in slot 1, and boot software version is 3.0(1.166)D.
MGX8850.7.PXM.a > burnboot 1 3.0(1.166)DIn the second example. the crossbars are healthy. The target is the standby PXM45 (slot 8). The bootcode version is 3.0(10.0)D. Because the card is reset by this command, the system prompts you to confirm whether or not to proceed.
rishic-mgx.7.PXM.a > burnboot 8 3.0(10.0)DThe card in slot 8 will be reset.burnboot:Do you want to proceed (Yes/No)? YChecking burnboot viability .....................[OK]Retrieving boot file information .......ImgHdr:image_type=2,shelf_type=5,card_type=3000Checksum size is 1024344 ...Resetting the card...In the third example, the crossbar is unhealthy, and the command is blocked ("FAILED"). Thereafter, another attempt is made but with the -force option and a response of "n" at the prompt that asks if the forced procedure should continue. Lastly, the -force option is used with a "yes" response both prompts.
rishic-mgx.7.PXM.a > burnboot 8 3.0(10.0)DThe card in slot 8 will be reset.burnboot:Do you want to proceed (Yes/No)? YChecking burnboot viability ..............[FAILED]Crossbar is not healthy. It's not advisable to reset the standby cardright now.If you still want to execute this command, use -force flag with 'burnboot'rishic-mgx.7.PXM.a > burnboot 8 3.0(10.0)D -forceThe card in slot 8 will be reset.burnboot:Do you want to proceed (Yes/No)? YChecking burnboot viability ..............Crossbar is not healthy. It's not advisable to reset the standby cardright now.burnboot:Do you want to proceed (Yes/No)? Nrishic-mgx.7.PXM.a > burnboot 8 3.0(10.0)D -forceThe card in slot 8 will be reset.burnboot:Do you want to proceed (Yes/No)? YChecking burnboot viability ..............Crossbar is not healthy. It's not advisable to reset the standby cardright now.burnboot:Do you want to proceed (Yes/No)? Y.....[OK]Retrieving boot file information .......ImgHdr:image_type=2,shelf_type=5,card_type=3000Checksum size is 1024344 ...Resetting the card...bye
Bye—PXM45, PXM1E
Exit the current CLI session.
Syntax
bye
Related Commands
logout, exit
Attributes
Exit the current CLI shell.
MGX8850.8.PXM.a > bye(session ended)
