Table Of Contents
Release Notes for Cisco MGX 8850 Software Version 2.1.60
Contents
About Release 2.1.60
Type of Release
Locating Software Updates
Acronyms
System Requirements
Software Compatibility Matrix
Additional Compatibility Information
Hardware Supported
Hardware Compatibility Matrix
New and Changed Information
New Features and Enhancements in Release 2.1.60
MGX/BPX APS Interoperability
Hierarchical PNNI (Multiple Peer Group [MPG])
192 Interfaces on PXM45/B
UNI 4.0
AINI
LDP on RPM-PR
Multi-LVC on RPM
RPM 1:N Redundancy
Enhancements
New Hardware Supported in Release 2.1.60
AXSM-E module (T3/E3, OC3c/STM1, OC12c/STM4)
AXSM-1-2488/B (No APS support)
New and Changed Commands
New Commands
Changed CLI Commands
Commands with Privilege Changes
Previously Undocumented Commands
Removed Commands
Limitations and Restrictions
General Limitations, Restrictions, and Notes
Important Notes
RPM-PR and MPLS Limitations, Restrictions, and Notes
RPM-PR and MPLS Notes
Booting the RPM-PR
RPM-PR Bootflash Precautions
APS Management Information
Open APS Issues
Clearing the Configuration on Redundant PXM45 Cards
Recommendations
Installing and Upgrading to Release 2.1.60
Upgrade Process Overview
Quickstart Procedures for Software Upgrades
Browsing the File System
Copying Software Files to the Switch
Upgrade Procedures for PXM45 and AXSM Cards
Upgrade Procedures for RPM-PR Cards
Troubleshooting Upgrade Problems
Documentation
Related Documentation
Cisco WAN Manager Release 10.5 Documentation
Cisco MGX 8850 Release 2.1 Documentation
SES PNNI Release 1.1 Documentation
Cisco WAN Switching Software, Release 9.3 Documentation
MGX 8850 Multiservice Switch, Release 1.1.40 Documentation
MGX 8250 Edge Concentrator, Release 1.1.40 Documentation
MGX 8230 Multiservice Gateway, Release 1.1.40 Documentation
Ordering Documentation
Documentation on the World Wide Web
Documentation CD-ROM
Documentation Feedback
Technical Assistance
Cisco.com
Technical Assistance Center
Contacting TAC by Using the Cisco TAC Website
Contacting TAC by Telephone
Caveats
Known Anomalies in Release 2.1.60
Anomalies Resolved in Release 2.1.60
Anomaly Status Changes in Release 2.1.60
Known Anomalies in Release 2.1.10
Anomalies Resolved in Release 2.1.10
Anomaly Status Changes in Release 2.1.10
Anomalies Resolved in Release 2.1.00
Known RPM-PR/MPLS Anomalies
Release Notes for Cisco MGX 8850 Software Version 2.1.60
Contents
About Release 2.1.60
These release notes describe the system requirements, new features, and limitations that apply to Release 2.1.60 for the MGX 8850 IP + ATM backbone switch. These notes also contain Cisco support information.
Type of Release
Release 2.1.60 is a software and hardware release for the MGX 8850 Switch.
Locating Software Updates
Software updates are located at Cisco Connection Online (CCO) at http://www.cisco.com/kobayashi/sw-center/sw-wan.shtml.
Acronyms
Table 1 lists acronyms used in these release notes.
Table 1 Acronyms and Their Descriptions
Acronym
|
Description
|
AINI
|
ATM Inter-Network Interface
|
APS
|
automatic protection switching
|
ATM
|
asynchronous transmission mode
|
AXSM
|
ATM Switch Service Module
|
B-ISUP
|
Broadband ISDN User Part
|
BPX
|
an earlier Cisco backbone switch
|
CLI
|
command line interface
|
CWM
|
Cisco Wide Area Network Manager
|
DSLAM
|
digital subscriber line access module
|
IETF
|
Internet Engineering Task Force
|
LDP
|
label distribution protocol
|
LSC
|
label switch controller
|
LSP
|
label switched paths
|
LSR
|
label switch router
|
MIB
|
management information base
|
MPG
|
multiple peer group
|
MPLS
|
multiple protocol label switching
|
NCDP
|
network clock distribution protocol
|
PNNI
|
private network-to-network interface
|
PXM
|
processor switch module
|
RPM
|
route processor module
|
RPM-PR
|
route processor module - Premium
|
SCT
|
service class template
|
SLA
|
service level agreement
|
SM
|
service module (a card)
|
SNMP
|
simple network management protocol
|
SPVC
|
soft permanent virtual connection
|
SVC
|
switched virtual circuit
|
UNI
|
User-Network Interface
|
VCI
|
virtual channel identifier
|
VPI
|
virtual path identifier
|
System Requirements
This section describes software compatible with this release, and lists the hardware supported in this release.
Software Compatibility Matrix
Table 2 lists the software that is compatible for use in a switch running Release 2.1.60 software.
Table 2 Software Compatibility Matrix
Board Pair
|
Boot Software
|
Minimum
Boot Code
Version
|
Runtime Software
|
Latest
Firmware
Version
|
Minimum
Firmware
Version
|
PXM45
|
pxm45_002.001.060.100_bt.fw
|
2.1.60
|
pxm45_002.001.060.100_mgx.fw
|
2.1.60
|
2.1.60
|
PXM45/B
|
pxm45_002.001.060.100_bt.fw
|
2.1.60
|
pxm45_002.001.060.100_mgx.fw
|
2.1.60
|
2.1.60
|
AXSM-1-2488
|
axsm_002.001.060.100_bt.fw
|
2.1.60
|
axsm_002.001.060.100.fw
|
2.1.60
|
2.1.60
|
AXSM-16-155
|
AXSM-4-622
|
AXSM-16-T3/E3
|
AXSM-1-2488/B
|
axsm_002.001.060.100_bt.fw
|
2.1.60
|
axsm_002.001.060.100.fw
|
2.1.60
|
2.1.60
|
AXSM-16-155/B
|
AXSM-4-622/B
|
AXSM-16-T3/E3/B
|
AXSM-2-622-E
|
axsme_002.001.060.100_bt.fw
|
2.1.60
|
axsme_002.001.060.100.fw
|
2.1.60
|
2.1.60
|
AXSM-8-155-E
|
AXSM-16-T3E3-E
|
RPM-PR
|
rpm-boot-mz.122-4.T
|
12.2(4)T
|
rpm-js-mz.122-4.T
|
12.2(4)T
|
12.2(4)T
|
Additional Compatibility Information
The following notes provide additional compatibility information for this release:
•
You can gracefully upgrade to Release 2.1.60 from Release 2.0.15 or Release 2.1.10.
•MGX 2.1.60 interoperates with SES PNNI 1.1.60 plus BPX Switch Software (SWSW) 9.3.30 plus BXM MFN.
•This release supports feeder connections from Cisco MGX 8850 Release 1.1.40. Please see the "Release Notes for MGX 8850, 8230, and 8250 Software Version 1.1.40" for feeder feature issues. Release notes can be downloaded from http://www.cisco.com/univercd/cc/td/doc/product/wanbu/index.htm.
•You must use CWM Release 10.5 to manage networks that contain MGX 8850 switches running Release 2.1.60.
•The RPM-PR software in this release is based on IOS Release 12.2(4)T.
•The SNMP MIB release for 2.1.60 is mgxmibs2160.tar
Hardware Supported
Table 3 lists the hardware supported in Release 2.1.60.
Table 3 Hardware Supported in Release 2.1.60 for MGX 8850
Product ID
|
800 Part Number
|
Minimum Revision
|
PXM45
|
800-06147-07
|
-B0
|
PXM45/B
|
800-09266-04
|
-A0
|
PXM-UI-S3
|
800-05787-02
|
-A0
|
PXM-HD
|
800-05052-03
|
-A0
|
AXSM-1-2488
|
800-05795-05
|
-A0
|
AXSM-1-2488/B
|
800-07983-02
|
-A0
|
SMFSR-1-2488
|
800-05490-05
|
-A0
|
SMFLR-1-2488
|
800-06635-04
|
-A0
|
SMFSR-1-2488/B
|
800-07255-01
|
-A0
|
SMFLR-1-2488/B
|
800-08847-01
|
-A0
|
AXSM-16-155
|
800-05776-06
|
-A0
|
AXSM-4-622
|
800-05774-09
|
-B0
|
AXSM-16-T3/E3
|
800-05778-08
|
-A0
|
AXSM-16-155/B
|
800-07909-05
|
-A0
|
AXSM-4-622/B
|
800-07910-05
|
-A0
|
AXSM-16-T3/E3/B
|
800-07911-05
|
-A0
|
SMFIR-2-622
|
800-05383-01
|
-A1
|
SMFIR-2-622/B
|
800-07412-02
|
-B0
|
SMB-8-T3
|
800-05029-02
|
-A0
|
SMB-8-E3
|
800-04093-02
|
-A0
|
MMF-8-155-MT
|
800-04819-01
|
-A1
|
SMFIR-8-155-LC
|
800-05342-01
|
-B0
|
MMF-8-155-MT/B
|
800-07120-02
|
-A0
|
SMFIR-8-155-LC/B
|
800-07864-02
|
-B0
|
SMB-4-155
|
800-07425-02
|
-A0
|
RPM-PR-256
|
800-07178-02
|
-A0
|
RPM-PR-512
|
800-07656-02
|
-A0
|
MGX-MMF-FE
|
800-03202-02
|
-A0
|
MGX-RJ45-4E/B
|
800-12134-01
|
-A0
|
MGX-RJ45-FE
|
800-02735-02
|
-A0
|
AXSM-16-T3E3-E
|
800-18519-02
|
-A0
|
AXSM-8-155-E
|
800-18520-02
|
-A0
|
AXSM-2-622-E
|
800-18521-02
|
-A0
|
MMF-4-155/C
|
800-07408-02
|
-A0
|
SMFIR-4-155/C
|
800-07108-02
|
-A0
|
MGX-SMFLR-4-155/C
|
800-07409-02
|
-A0
|
SMFIR-1-622/C
|
800-07410-02
|
-A0
|
MGX-SMFLR-1-622/C
|
800-07411-02
|
-A0
|
MGX8850-CH
|
73-3772-03
|
-A0
|
MGX-APS-CON
|
800-05307-01
|
-A0
|
Hardware Compatibility Matrix
Table 4 shows which back cards can be used with each front card in Release 2.1.60.
Table 4 Back Cards and Connectors Supported by Front Cards
Front Card Type
|
Back Card Types
|
Supports APS Connector (MGX-APS-CON)
|
AXSM-1-2488
|
SMFSR-1-2488
SMFLR-1-2488
SMFXLR-1-2488
|
Yes
|
AXSM-1-2488/B
|
SMFSR-1-2488/B
SMFLR-1-2488/B
SMFXLR-1-2488/B
|
Yes
Yes
yes
|
AXSM-4-622
|
SMFIR-2-622
SMFLR-2-622
|
Yes
|
AXSM-4-622/B
|
SMFIR-2-622/B
SMFLR-2-622/B
|
Yes
|
AXSM-16-155
|
MMF-8-155-MT
SMFIR-8-155-LC
SMFLR-8-155-LC
|
Yes
|
AXSM-16-155/B
|
SMB-4-155
MMF-8-155-MT/B
SMFIR-8-155-LC/B
SMFLR-8-155-LC/B
|
Yes
|
AXSM-16-T3E3
|
SMB-8-T3
SMB-8-E3
|
|
AXSM-16-T3E3/B
|
SMB-8-T3
SMB-8-E3
|
|
AXSM-16-T3E3-E
|
SMB-8-T3
SMB-8-E3
|
|
AXSM-8-155-E
|
MMF-4-155/C
SMFIR-4-155/C
SMFLR-4-155/C
SMB-4-155
|
Yes
Yes
Yes
|
AXSM-2-622-E
|
SMFIR-1-622/C
SMFLR-1-622/C
|
Yes
Yes
|
PXM45
|
PXM-UI-S3
|
|
|
PXM45/B
|
PXM-UI-S3
|
|
|
RPM-PR-256
RPM-PR-512
|
MGX-MMF-FE
MGX-RJ45-4E/B
MGX-RJ45-FE
|
|
New and Changed Information
This section describes new features, hardware, and commands in Release 2.1.60.
New Features and Enhancements in Release 2.1.60
Release 2.1.60 contains these new features:
•MGX/BPX automatic protection switching (APS) Interoperability
•Hierarchical PNNI (Multiple Peer Group [MPG])
•192 Interfaces on PXM45/B
•UNI 4.0
•ATM Inter-Network Interface (AINI)
•LDP on RPM-PR
•Multi-LVC on RPM
MGX/BPX APS Interoperability
This feature verifies that the Automatic Protection Switching (APS) feature operates as described in the Telcordia GR-253 standard on both the MGX and the BPX switches.
Benefits
Cisco's multiservice customers, whose networks started out with the BPX as a backbone switch, have APS operation unchanged as their networks evolve to include the MGX 8850 switch.
Hierarchical PNNI (Multiple Peer Group [MPG])
Hierarchical PNNI (also referred to as Multiple Peer Group PNNI) allows the growth of PNNI networks to a very large size. As a simple example, a network with two levels of hierarchy and 50 nodes in each peer group and 50 groups would have 2500 nodes. Another way to describe this is as 50 peer groups, each containing 50 nodes. Expanding the same design to 3 levels of hierarchy yields 125,000 nodes. While network topology constraints will usually limit the size to smaller numbers, the growth potential is clear.
The practical size of PNNI networks is limited by several factors, all of which use either processor real time, or memory on the node:
•Number of nodes in a peer group.
•Number of "visible" nodes. This is the number of nodes seen by a node that connects to other peer groups. This number includes the number of nodes in the local peer group, as well as all other peer groups that can be seen from a particular node's view into the hierarchical network.
•The number of PNNI links in a peer group.
•The number of registered ATM addresses in a network.
•The number of connections supported on the local node.
•The average number of 10 links per node and 2000 addresses per node with average of 2 summary addresses per node.
For complete details, refer to the "Cisco MGX and SES PNNI Network Planning Guide" (see "Related Documentation" later in these notes).
The software can support up to 10 hierarchical levels. Testing of 2.1.60 is performed for four hierarchical levels.
To prepare for the future addition of hierarchy to a PNNI network, the addressing scheme should be planned prior to the provisioning of any connections on a PNNI network. If, at any time in the future, hierarchy must be added to a network in which the addressing was not planned properly, connections will have to be re-provisioned using the new addressing scheme.
Benefits
The introduction of hierarchical PNNI enables the building of very large ATM networks. It also enables the growth of flat PNNI networks with the addition of hierarchy. Enabling hierarchy on an existing PNNI network has no impact on existing ATM connections, assuming that the addressing scheme was planned in advance to accommodate hierarchy. Since connections can be managed end-to-end across a hierarchical network, the manageability of networks can be increased in situations that previously required splitting a large network into multiple routing domains.
192 Interfaces on PXM45/B
The PXM45/B module supports up to 192 interfaces. A physical port/trunk, virtual trunk or a logical port is counted as an interface. Among 192 interfaces, up to 100 interfaces can be signaling ports. The other 92 interfaces should be non-signaling ports, such as non self-supporting ports.
Benefits
Support for 192 interfaces allows the ability to completely fill the chassis (12 slots) with broadband service module ports, e.g., AXSM-16-155/B.
UNI 4.0
MGX 8850 switches currently provide UNI signaling compliant with ATM Forum UNI 3.1 (af-uni-0010.002). This feature adds the ability to utilize the UNI 4.0 protocol when connecting to ATM UNI devices that require signaling support. Also included in this feature is support for the ITU signaling specification Q.2931.
Benefits
The UNI 4.0 signaling capability is required to provide complete and standard interoperability with UNI devices in common use. Applications enabled by the full implementation of UNI 4.0 include voice transport, connection to certain class 5 voice switching equipment, and enhanced SVC UNI services including ABR.
AINI
The ATM Inter-Network Interface (AINI) is the new inter-networking standard for PNNI to PNNI, PNNI to B-ISUP, and B-ISUP to B-ISUP internetworking. AINI provides most of the advantages of PNNI networking and allows for a secure interface that does not allow the exchange of network topology and availability information.
AINI provides a resilient interface between networks since it takes advantage of many aspects of PNNI. Despite using static routes, AINI offers crankback, alternate routes, and load balancing across multiple parallel links. Crankback is defined as a mechanism for partially releasing a connection setup in progress, which has encountered a failure. This mechanism allows PNNI to perform alternate routing.
AINI support includes:
•UNI 4.0 based signalling
•Supports UNI 4.0 call types including ABR
•Crankback on AINI links used for Alternate routing
•Load balancing across multiple AINI links
•Path and Connection Trace across AINI links
•Support for Hop Counter Information Element to detect loops
•Configurable VPI/VCI allocator Node (between AINI peer nodes)
•Connection terminates at AINI ports.
Note Support of Path and Connection Trace on AINI links is provided as a configurable option. For standards compliance, it should be disabled.
Benefits
AINI allows two or more carriers to interconnect their PNNI-based networks without exchanging topology information. It provides end-to-end provisioning and resiliency of connections. This provides a significant manageability improvement over the traditional method of interconnecting such networks using standard NNI links.
The DSL Forum has defined AINI as the preferred protocol for interconnecting ATM switches with DSLAMs. This feature allows use of the MGX 8850 in applications such as DSL, wireless, and other aggregation applications.
LDP on RPM-PR
The MPLS label distribution protocol (LDP), as standardized by the Internet Engineering Task Force (IETF) and as enabled by Cisco IOS software, allows the construction of highly scalable and flexible IP Virtual Private Networks (VPNs) that support multiple levels of services.
LDP provides a standard methodology for hop-by-hop, or dynamic label, distribution in an MPLS network by assigning labels to routes that have been chosen by the underlying Interior Gateway Protocol (IGP) routing protocols. The resulting labeled paths, called label switch paths or LSPs, forward label traffic across an MPLS backbone to particular destinations. These capabilities enable service providers to implement Cisco's MPLS-based IP VPNs and IP+ATM services across multivendor MPLS networks.
From an historical and functional standpoint, LDP is a superset of Cisco's pre-standard Tag Distribution Protocol (TDP), which also supports MPLS forwarding along normally routed paths. For those features that LDP and TDP share in common, the pattern of protocol exchanges between network routing platforms is identical. The differences between LDP and TDP for those features supported by both protocols are largely embedded in their respective implementation details, such as the encoding of protocol messages, for example.
This software release of LDP provides the means for transitioning an existing network from a TDP operating environment to an LDP operating environment. Thus, you can run LDP and TDP simultaneously on any given router platform. The routing protocol that you select can be configured on a per-interface basis for directly connected neighbors and on a per-session basis for non directly connected (targeted) neighbors. In addition, a label switch path (LSP) across an MPLS network can be supported by LDP on some hops and by TDP on other hops.
Benefits
•IETF Standards-based Label distribution protocol
•Multi-Vendor Interoperability
•TDP to LDP migration and interoperability
Multi-LVC on RPM
This feature enables support for initiation of Multiple label switched paths (LSPs) per destination on the RPM. Different label switched paths are established for different class of services. This feature enables interface level queueing rather than per-vc level on the RPM based on MPLS class of service policy.
Benefits
Customers can deploy IP VPN services with Class of service SLAs.
RPM 1:N Redundancy
RPM 1:N redundancy is used to switch configuration and traffic from one RPM card to another. The main benefits are:
•Route processing continues even if an RPM fails and there is no operator or direct access to swap the failed card or fix the problem.
•An RPM card with hardware problems can be fixed while the redundant standby card takes over its functionality.
•Software upgrades are easier and can be done with less downtime.
Enhancements
This release of software includes the following product enhancement requests (PERs):
•3005 Support displaying Bit Error Counts on lines in MGX 2x
•3008 Need dclk-like command to test external clock inputs
•3009 Node name is not shown in all commands (partial delivery)
•3010 tstdelay/tstconseg results should be shown after command run
•3011 Need command for connection counts by class and master/slave endpoints (dspconinfo MASTER/SLAVE not done)
•3012 Need command on AXSM to show provisioning
•3013 dsppnports show confusing counts for DAX SPVCs
•3014 Default bandwidth not honored in SCT
•3015 Need better log messages for MAX_CD_RESET (new log introduced, but old message still to be removed)
•3016 Need High Priority login function/commands
•3017 clrsarcnt command
•3018 Crankback to alternate paths when no response to signal on selected path (crankback due to "building_vc/down_in_prog" not done)
•3061 Require a command to validate the contents of the flash
•3064 Need consistent naming for addchanloop and addlnloop
Contact your account representative for details about these enhancements.
New Hardware Supported in Release 2.1.60
The following new hardware is supported by the Release 2.1.60 software:
•AXSM-E module (T3/E3, OC3c/STM1, OC12c/STM4)
•AXSM/B OC-48 (No APS support)
AXSM-E module (T3/E3, OC3c/STM1, OC12c/STM4)
The AXSM-E is a double-height Service Module used on the PXM45-based MGX 8850 platform. The AXSM-E supports ATM cell transfer over various physical interfaces: T3/E3, OC-3c/STM-1, and OC-12c/STM-4. The AXSM-E hardware is implemented with a base card (mother board) and various auxiliary cards (daughter boards) that each define the physical interface (T3/E3, and so on) being used. .
AXSM-E card types include:
•AXSM-16-T3E3-E, which supports SMB-8-T3 and SMB-8-E3 back cards
•AXSM-8-155-E, which supports SMB-4-155, MMF-4-155/C, SMFIR-4-155/C, and SMFLR-4-155/C back cards
•AXSM-2-622-E, which supports SMFIR-1-622/C and SMFLR-1-622/C back cards
Note The front card hardware (mother board/daughter board) for each card type can support up to two back cards. But in Release 2.1.60, onlyone back card (i.e., half the port capacity available in hardware) is supported by software. The full port capacity will be supported with a future software release. No hardware changes will be required.
Benefits
The AXSM-E card's ATM engine supports a variety of Traffic Management features, including Standard ABR with VS/VD and per-VC traffic shaping, along with multilevel statistics. In addition, the AXSM-E allows configurations of ports and trunks on the same card and provides APS, virtual interfaces, VSI support, SVC and SPVC capability.
The AXSM-E supports all these functions while being used as a trunk or port module for the PXM-45 switch fabric in any of the following environments:
•IP+ATM Edge switching
•IP+ATM Core switching
•IP+ATM Standalone switching, working with other MPLS- and PNNI-compliant switches
AXSM-1-2488/B (No APS support)
The AXSM-1-2488/B/(OC-48/STM-16) is a double-height ATM service module that uses serial line traces to access the crossbar switching fabric. It supports 1:1 module redundancy and provides ATM switching and line functions. A future software release will activate the APS capability on the AXSM-1-2488/B.
One port is supported per single-height back card (SMFSR, SMFLR)
Benefits
This card is targeted for those who prefer to use a single OC-48/STM-16 card type for the MGX 8850.
New and Changed Commands
Release 2.1.60 contains many new commands, listed below.
Please refer to the "MGX 8850 Command Reference, Release 2.1" (part DOC7812563=) for details about these commands (see the "Related Documentation" section later in these notes for additional documentation that supports this release).
New Commands
These commands are new in Release 2.1.60:
•addapsln
•bringupnewstandby
•clearhelp
•clradjlnalmcnt
•clrconstats
•clrconstats
•clrqosdefault
•cnfainihopcount
•cnfautolndiag
•cnfbert
•cnfcdstat
•cnfcmdabbr
•cnfetherif
•cnfintfvsvd
•cnfpnportloscallrel
•cnfpnportncci
•cnfpswdexpire
•cnfpswdreset
•cnfspvcprfx
•cnfxbaradmin
•cnsainihopcount
•copycons
•deladdrs
•dspadjlnalm
•dspadjlnalmcnt
•dspainihopcount
•dspalm
•dspalmcnt
•dspautolndiag
•dspbert
•dspbertstats
•dspcdsct
•dspcdstatcnf
•dspchanstat
•dspcmdabbr
•dspconfigs
•dspdbsvrdb
•dspdbsvrdbbyname
•dspdbsvrsecdb
•dspdbsvrsecdbbyname
•dspegrbucketcnt
•dspfile
•dsphardwaremastership
•dsphelpver
•dsphwmastership
•dspingbucketcnt
•dsplncnt
•dsplnpmbucketcnt
•dspoamsegep
•dsppnallgrpaddr
•dsppnallgrpmbrs
•dsppnportloscallrel
•dsppnportncci
•dspprf
•dsppswdexpire
•dsppswdreset
•dspsct
•dspspvcaddr
•dspspvcaddr
•dspstbyclksrcs
•dsptotals
•dspversions
•dumpalllogs
•dumpconfigs
•dumpversions
•insbiterror
•installhelp
•reboot
•startbert
•stopbert
Changed CLI Commands
These commands have changed:
•addapsln
•cnfnodalfd used to be cnffdonaal5
•dspalm
•dspalmcnt
•dspbecnt
•dspcdsct
•dsplnalms used to be dspalms
•dsplncnt
•dspnodalfd used to be dspsigparms
•dspsct
•dspsct
•dspsct
Here is additional detail for other commands that have changed in this release.
•addcon/cnfcon now blocks the user from specifying frame discard on the slave endpoint
•addpnni-node help information now shows that you can enter on or true to enable or off or false to disable.
•clrchancnt and clrchancnts now run on the AXSM-E as well as the AXSM.
•cnfcon now accepts a -1 for maxcost (-mc) and two other parameters. Previously, software would not allow a user to enter a -1, although it would display -1 in some cases.
•cnfuser now has a parameter for specifying a password expiration interval of 1-60 days.
•cnfxbaradmin— on or off instead 1 or 0
•core has two new parameters: "?" and "priority."
•dnport and dnallports now have a warning about possible service disruption and a recommendation to use dnpnport instead
•dspalms now has an APS alarm field
•dspapsbkplane now works on the AXSM-E
•dspapsln has a new row (or field)
•dspapsln now shows the state of the working line and protection line.
•dspbert has three new elements in its display (Error Insertion Rate, Tx Pattern Inversion, Rx Pattern Inversion) and has changed from a horizontal display to a vertical display
•dspchanstat on the AXSM-E has been changed to dspchancnt (to match AXSM)
•dspcon executed on the PXM45 now shows the name of the node
•dspconinfo now has three optional parameters: portID, a "detail" switch, and an option for selecting the service class for the display.
•dspcons on the PXM45 has a new filter. It is "sc" for selecting a service class.
•dsperr has a new option for trace in the error log. This option has the syntax: -tr {P|L|N} where the 'P' option stands for 'Pause'. This pauses when it encounters trace data and prompts to determine if it should be displayed. The 'L' option stands for "List." It lists all of the trace-data file names. The 'N' option stands for 'No' and this prints the error log without trace data. The full command syntax is: dsperr -sl <slot #> [Options] Options: -en <error #> -tr <P|L|N>
•dspilmicnt will apply to AXSM-E
•dsplns output now accommodates mixed T3E3 back card arrangements. For parameters that do not apply to E3, the display shows "N/A."
•dsppncons has a new filter added to its "type" parameter: ctrl, to specify control VCs.
•dsppnilmi: One of the various possible states has changed: "Undefined" is now "Not Applicable."
•dsppnni-node-list now includes the level
•dsppnni-reachable-addr and dsppnsysaddr each now have a field called "Physical Desc" which is just the portID. However, if the displayed address is switch level, the contents of this field are "NA."
•dsppnport
•dspportcnt output now shows the last time the counters were cleared and the time since they were last cleared
•dspred now shows the inserted card in brackets on a (new) row below the line that shows the reserved card. This can be important if the reserved card is different from the inserted card.
•dspsct now has "abr" and line type parameters (T3, etc)
•dspsesn should become visible
•switchapsln has a third failure reason (see the "MGX 8850 Command Reference, Release 2.1")
•upilmi now gives a warning about possible rerouting of connections
Commands with Privilege Changes
The following commands had changes in privileges:
•addfdr : ANYUSER -> GROUP
•clralmcnt : SUPER -> SERVICE
•clrbecnt : SUPER -> SERVICE
•clrbucketcstat : SUPER -> SERVICE
•clrcdcnt : SUPER -> SERVICE
•clrchancnt, clrchancnts : SUPER -> SERVICE
•clrchandbgcnt : SUPER -> SERVICE
•clrcosdbgcnt : SUPER -> SERVICE
•clrfdrstat : ANYUSER -> SERVICE
•clrlncnt : SUPER -> SERVICE
•clrportcnt : SUPER -> SERVICE
•clrportcnts : SUPER -> SERVICE
•copychans : SERVICE -> GROUP
•copycons : SERVICE -> GROUP
•delfdr : ANYUSER -> GROUP
•delfdr : ANYUSER -> GROUP
•dnilmi : ANYUSER -> GROUP
•dspbecnt : SUPER -> ANYUSER
•dspcon : GROUP -> ANYUSER
•dspcons : GROUP -> ANYUSER
•dspcosdbgcnf : ANYUSER -> SERVICE
•dspcosdbgcnt : ANYUSER -> SERVICE
•dsplnbucketcnt : CISCO -> ANYUSER
•tstconseg : GROUP -> SERVICE
•tstdelay : GROUP -> SERVICE
•upilmi : ANYUSER -> GROUP
Previously Undocumented Commands
The following commands are now documented in the "MGX 8850 Command Reference, Release 2.1":
•actaudit
•cnfpnctlvc
•cnfpnportloscallrel
•copycons, copychans
•dspcprotbls
•dspmsq and dspmsgqs
•dsppnctlvc
•dsppnportloscallrel
•routeadd
•routedelete
•routenetadd
•rrtcon
•sesnwatchdog
•smclrscrn
•xbaradmin
Removed Commands
There are no commands removed from version 2.1.60.
Limitations and Restrictions
This section describes the following issues for Release 2.1.60:
•General limitations, restrictions, and notes
•RPM-PR and MPLS limitations, restrictions, and notes
•APS management information and open issues
•Clearing the configuration on redundant PXM45/B cards
General Limitations, Restrictions, and Notes
The following limitations and restrictions apply to this release.
Note
•For a graceful upgrade, you must upgrade from version 2.0.15 or 2.1.10 or above.
•Presently, the PXM CLI allows for provisioning of a PNNI controller (controller id 2) on any slot in the chassis, but for this release, such provisioning should be restricted to slot 7 only.
•APS is not supported on AXSM-1-2488/B.
•Of 192 PNNI interfaces, up to 100 interfaces can be signaling ports. The other 92 interfaces should be non-signaling ports, such as non self-supporting ports.
•AXSM-1-2488 and AXSM-1-2488/B cards do not have a policing function enabled.
•The front card hardware (mother board/daughter board) for each card type can support up to two back cards. But in Release 2.1.60, onlyone back card (i.e., half the port capacity available in hardware) is supported by software. The full port capacity will be supported with a future software release. No hardware changes will be required.
•Trace information captured in the error logs of non PXM slots (seen with dsperr -sl <slotnum>) will not translate addresses in the trace to correct symbolic names. Such files with trace data need to be moved off the system using FTP and forwarded to TAC and engineering.
•Support for 3 controllers only (1 for PNNI and 2 for LSC). Controller ID 2 is reserved for a PNNI controller; IDs 3-20 are available for LSC controllers.
•Partition ID 1 is reserved for PNNI.
•The maximum number of logical interfaces (physical trunks, virtual trunks, logical ports) supported in this release with PXM45 cards is 99 and PXM45/B cards is 192.
•If an active AXSM card is stuck in the active INIT state, the standby PXM will not go to the standby Ready state until the active AXSM goes to a steady state. Steady states are: Active Ready, Failed, Mismatch, Empty, Empty Reserved, Standby Ready. With redundancy configured, if a standby AXSM card is stuck in a standby init state, with an active Active AXSM already in a Active Ready state, the standby PXM will go to the standby Ready state without any delay. If both AXSMs in the redundancy pair are not in a steady state, then the standby PXM will not go to the standby Ready state until one or both of the 2 AXSM cards are in the active Ready state.
•AXSM cards are in some other steady state (e.g., FAILED). If the destination address is reachable for both an IISP and a PNNI link from the same node, ABR connections will not route. The current routing algorithm will always choose IISP links over PNNI links because it is local. Since IISP does not support ABR connections, the connection setup will fail.
•In this release, a Service Class Template (SCT) can be changed with connections present. However, if the change affects services in use, the connections will be rerouted.
•When CWM is used to manage the network, the IP address 10.0.x.x cannot be used as the LAN address (lnPci) for the switch.
Important Notes
This section provides general notes that apply to this release, and covers some procedures that are not yet in the manuals.
•You must use the SCT files released with 2.1.60 (number 2 and 3, which were included in version 2.0.13 are similar to number 2 and 3 for 2.1.60) for the Control VC feature. If you are using the MPLS feature, then you will need to change to SCT 4 or 5, which were released with version 2.1.00.
•By default, 900 cps and 543 cps will be reserved for SSCOP and PNNI Signalling VC respectively, even when you disable SSCOP and PNNI. These values are configurable by the cnfpnctlvc command.
•Do not execute the delcontroller command when connections/ports still exists. The impact of executing delcontroller with connections is that the connections cannot be recovered until the controller is re-added using addcontroller and the AXSM cards or the entire node has to be reset (otherwise ports remain in the provisioning state). There is now a warning to the user of the impact of the command when there are existing connections/ports.
•Analysis of the code has identified a situation which has a low probability of occurring and in fact has not been encountered in any test scenarios to date. This caution and associated workaround is provided as a precautionary measure. When the link bandwidth for SPVC connections is reaching full capacity, making minimal bandwidth available for new SPVC connections, a condition can be encountered where the initial software check believes there is sufficient bandwidth for the new SPVC connection; however, the final software confirmation for available bandwidth may be rejected because there is no bandwidth available. If this problem occurs, the system will recover when the PNNI updates are refreshed. (This will happen at the default time of 30 minutes.) The user can recover from this problem by making the Administrative weight of that link very high to avoid that link from being used.
•To replace one type of AXSM front card with another type, you must delete all connections, partitions, ports and down lines. If an AXSM card fails, the same type of AXSM card must be installed in its slot.
•When the switch cannot automatically resolve nativity check conflicts, you can force a configuration rebuild from a specific hard disk by establishing a console port session through the corresponding PXM-UI-S3 card and issuing the shmRecoverIgRbldDisk command. This command ignores the nativity check and configures the entire switch according to the configuration on the hard disk.
•PNNI default min VCI is 35 unless changed explicitly. The reason for the default is to reserve VCI=32-34 for other control purposes (e.g., MPLS and NCDP). For users who would like to add MPLS controller in future releases of MGX 8850, it is highly recommend to set the min-vci value to be 35 or more for all partitions on the port where the MPLS partition will be added. By doing so, the TDP sig vc for MPLS will be established automatically on 0/32. MinVPI is not negotiated by ILMI, so the user should set this parameter same on both nodes.
RPM-PR and MPLS Limitations, Restrictions, and Notes
The RPM-PR and MPLS limitations and restrictions that apply to this release are as follows:
•Saveallcnf (issued on the PXM45/B card) captures configuration data saved by the RPM-PR card (as well as AXSM and PXM45 cards), and saves it on the active PXM45/B card's hard disk. Users must have configured RPM to store its configuration on the PXM45/B hard disk (E:/RPM). That is, on RPM, a user should have this line in its running configuration ("boot config e:auto_config_slot#). To ensure that the saved file contains the latest RPM configuration, the user needs to execute the copy run start command on each RPM card prior to the saveallcnf command. This way, the RPM files on the active PXM45 hard disk will contain the latest configuration to be saved.
•A single RPM-PR can only function as either an Edge LSR or as an LSC, but not as both.
•Total of (OC12 minus T3) Mbps intrashelf traffic for Cell bus based modules are supported.
•To configure redundancy, the primary and secondary RPM-PR cards need to be in the Active state and the secondary card should not have any configuration.
•Removing a back card does not cause RPM-PR switchover.
•After establishing redundancy between two RPM-PR cards with the addred command, you must enter the copy run start command on the primary RPM-PR card to save the configuration change.
•If a secondary RPM-PR card is redundant to primary cards x and y, you cannot delete redundancy for only card x.
•If you need to enter the softswitch and switchcc commands, Cisco Systems recommends that you wait at least 5 seconds after issuing the softswitch command, and then enter the switchcc command.
•IOS software images on primary and secondary RPM-PR cards do not have to be compatible, but the IOS software on a secondary card should be at the same level as the primary card or higher.
•For ELSR to LSC connectivity, default control vc used is 32. If PNNI partition exists with VCI 32 as part of its partition range, then when MPLS partition is added, there are two options to handle the situation:
–Add MPLS controller and define its partition with available range. On ELSR, define control vc from any VCI value within the range defined in partition. The same VC should be defined on LSC on xTag interface.
–Reconfigure PNNI partition to spare the control VC usage both on RPM-PR and AXSM, AXSM/B or AXSM-E APS Management Information.
•Whenever the RPM-PR configuration is changed and a user wants to store that configuration, the user must enter the "copy run start" command on the RPM-PR. If this is not done, the changed configuration will be lost on RPM-PR card reboot or RPM-PR switchover in case of redundancy.
•Even though RPM-PR can have 1999 sub interfaces, the usage of sub interfaces should be planned in such a way that it does not cross a safe limit of 1985. This is because each sub interface takes one IDB (interface descriptor block) and the number of IDBs available in the card is 2000. Further, a user might need some IDBs for the RPM-PR back card and its ports.
RPM-PR and MPLS Notes
This section contains additional notes on using RPM-PR cards and MPLS in this release:
•RPM-PR back card status may be incorrect (anomaly CSCdt55154).
•For RPM-PR SPVC dax connections, the slave end must be deleted before the master endpoint.
Table 5 lists RPM comma
