Table Of Contents
Release Notes for Cisco MGX 8950 Software Version 2.1.76
Contents
About Release 2.1.76
Type of Release
About the New MGX 8950 Switch
Description
The XM-60 Switch Fabric Card
Software Information
Benefits
Platforms/Considerations
Design Guides and Application Notes
References
Limitations
Marketing Contact
Locating Software Updates
Acronyms
System Requirements
Software/Firmware Compatibility Matrix
Additional Compatibility Information
Hardware Supported
Hardware Compatibility Matrix
New and Changed Information
New Features and Enhancements in Release 2.1.60 through 2.1.76
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
New Features in Release 2.1.70
Config Verify
New Features in Release 2.1.76
Multiprotocol Label Switching (MPLS) over ATM using VC Merge
Enhancements
Additional Software Information
MIB
Service Class Template File Information
New Hardware Supported in Release 2.1.76
AXSM-1-2488/B (No APS support)
New and Changed Commands
New Commands
New Commands for the MGX 8850 Switch Only
Changed CLI Commands
Removed Commands
Previously Undocumented 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
Preparing for Intercard APS
Managing Intercard APS Lines
Troubleshooting APS Lines
Clearing the Configuration on Redundant PXM45 Cards
Recommendations
Installing and Upgrading to Release 2.1.76
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
Using XModem to Download Flash to RPM Cards
Troubleshooting Upgrade Problems
Documentation
Related Documentation
Cisco WAN Manager Release 10.5 Documentation
Cisco MGX 8850 Release 2.1 Documentation
Cisco MGX 8950 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.76
Known RPM-PR/MPLS Anomalies
Release Notes for Cisco MGX 8950 Software Version 2.1.76
Contents
About Release 2.1.76
These release notes describe the system requirements, new features, and limitations that apply to Release 2.1.76 for the MGX 8950 multi-service switch. These notes also contain Cisco support information.
Use this document in conjunction with the documents listed in the "Related Documentation" section.
Type of Release
Release 2.1.76 is a maintenance release for the MGX 8850 switch and a hardware and software relesae for the new MGX 8950 switch.
For information about the MGX 8850, see the "Release Notes for Cisco MGX 8850 Software Version 2.1.76."
About the New MGX 8950 Switch
Description
The MGX 8950 switch extends the MGX family to provide backbone switching solutions for major service provider networks.
In its first release, the MGX 8950 leverages the AXSM/B card set currently available on the MGX 8850 for the service modules and the PXM-45/B for the control processor. MGX Release 2.1.76 is the first MGX software to support the MGX 8950 platform .
The MGX 8950 differs from the MGX 8850 in two major areas:
•
The MGX 8950 switch has no future narrowband support capability planned.
•The MGX 8950 introduces a new switching fabric card, the XM-60.
The majority of features developed in earlier releases of the MGX 8850 switch also apply to the new MGX 8950 switch. Please call Product Management for confirmation of a particular feature.
The XM-60 Switch Fabric Card
In order to increase the switching capacity of the MGX 8950 product, a new switch fabric card was developed, called the XM-60. MGX 8950 can accommodate up to four XM-60 cards, each of which provides up to 60 Gbps of raw switching capacity. MGX 8950 does not use the 45 Gbps switch on the PXM like the MGX 8850, the PXM45/Bs are used as processors and management interfaces. This physically separates the user traffic from the control traffic, an architecture designed for the highest availability. In later releases, an MGX 8950 populated with 4 XM-60 switching fabrics and OC192c/STM64 cards will allow a full-duplex 10 Gbps line rate to each slot (even if one of the XM-60s were to fail) . In the first release (2.1.76), the AXSM/B cards will use the XM-60s to achieve full line rate OC48c/STM-1, just as in the MGX 8850.
Software Information
The MGX 8950 uses the same software as the MGX 8850. The initial release of software that supports MGX 8950 is Release 2.1.76. This release also supports MPLS functionality. A later release will add higher speed line cards to fully use the capacity of the XM-60s and the serial lines on the backplane.
PNNI Information
The MGX 8950 uses the same PNNI code base as the MGX 8850, and runs it on the same processor--the PXM45/B. Complete interoperability is tested, and many if not all PNNI features that are supported on the MGX 8850 are supported on MGX 8950.
MPLS Information
MPLS functionality is supported in Release 2.1.76 by using a Route Processor Module (RPM-PR). Please note that since MGX 8950 is intended to be primarily a core platform with the current release, the RPM-PR acts only as the label switch controller for the platform. Even though the RPM-PR is the same one that is supported on the MGX 8850, edge functionality is not provided on the MGX 8950 with Release 2.1.76.
CWM Information
Basic connection provisioning on MGX 8950 is supported by CWM 10.5.10.
Benefits
Network applications that will benefit from the MGX 8950 include the following:
•Pure ATM scaling to OC-192c, with PNNI used throughout as the control plane
•High-end ATM-based multiservice aggregation, serving as a gateway to an IP/MPLS core. A PNNI control plane is used at the edge, and an MPLS control plane in the core. This migration can take place in stages.
•Non-IP multiservice traffic is maintained across an ATM core, and IP traffic is offloaded to a separate IP network.
Platforms/Considerations
The MGX 8950 is the high-end platform in the MGX family.
Design Guides and Application Notes
None available. See the "Related Documentation" list for additional customer documentation.
References
None available.
Limitations
•Only AXSM/B cards are s2upported. AXSM and AXSM-E cards are not supported on the MGX 8950 and will fail if installed in the system.
•Only PXM45/B control processors are supported. The earlier PXM45 version processor is not supported on MGX 8950, and will fail if installed in the system
Marketing Contact
Contact Hugues Metayer or David Pool in the Multiservice Switching Business Unit of Cisco.
Locating Software Updates
Software updates are located at Cisco Connection Online (CCO) at http://www.cisco.com/kobayashi/sw-center/beta
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/Firmware Compatibility Matrix
Table 2 lists Cisco WAN or IOS products that are interoperable with MGX Release 2.1.76.
Table 2 WAN and IOS Software Version Compatibility Matrix
Cisco WAN or IOS Products
|
Current Release
|
One release before current release
|
Two releases before current release
|
CWM
|
10.5.10 P1
|
n/a
|
n/a
|
MGX 1
|
1.2.01
|
1.1.40
|
1.1.34
|
MGX 2
|
2.1.76
|
2.1.75
|
2.1.70
|
BPG/IGX
|
9.3.36
|
9.3.35
|
9.3.24
|
MGX 8220
|
5.0.17
|
5.0.17
|
4.1.11
|
SES
|
1.1.75
|
1.1.70
|
n/a
|
Firmware
|
latest for all
|
latest for all
|
n/a
|
IOS
|
12.2(8)T1
|
12.2(4)T3
|
12.2(4)T1
|
VISM
|
2.2
|
2.2
|
2.1.1 (1 pair)
|
Table 3 lists the software that is compatible for use in a switch running Release 2.1.76 software. Note that the AXSM/B cards use the same software as AXSM cards.
Table 3 MGX and RPM Software Version Compatibility Matrix
Board Pair
|
Boot Software
|
Minimum
Boot Code
Version
|
Runtime Software
|
Latest
Firmware
Version
|
Minimum
Firmware
Version
|
PXM45/B
|
pxm45_002.001.076.100_bt.fw
|
2.1.76
|
pxm45_002.001.076.100_mgx.fw
|
2.1.76
|
2.1.76
|
AXSM-1-2488/B
|
axsm_002.001.076.100_bt.fw
|
2.1.76
|
axsm_002.001.076.100.fw
|
2.1.76
|
2.1.76
|
AXSM-16-155/B
|
AXSM-4-622/B
|
AXSM-16-T3/E3/B
|
RPM-PR
|
rpm-boot-mz.122-8.T
|
12.2(8)T1
|
rpm-js-mz.122-8.T
|
12.2(8)T1
|
12.2(8)T1
|
Additional Compatibility Information
The following notes provide additional compatibility information for this release:
•You can gracefully upgrade to Release 2.1.76 from Release 2.0.16 or Release 2.1.75.
•MGX 2.1.76 interoperates with SES PNNI 1.176 plus BPX Switch Software (SWSW) 9.3.30 plus BXM MFN.
•This release supports feeder connections from Cisco MGX 8850 Release 1.1.41 and 1.2.01. 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.10 (1) to manage networks that contain MGX switches running Release 2.1.76.
•The RPM-PR software in this release is based on IOS Release 12.2(8)T1.
•The SNMP MIB release for 2.1.76 is mgxmibs2176.tar
Hardware Supported
Table 4 lists the hardware supported in Release 2.1.76. Note that the MGX 8950 does not support the AXSM/A or the new AXSM-E cards. If these cards are present, they will show up as "Failed" when the dspcds command is issued.
Table 4 Hardware Supported in Release 2.1.76 for MGX 8950
Product ID
|
800 Part Number
|
Minimum Revision
|
PXM45/B
|
800-09266-04
|
-A0
|
PXM-UI-S3
|
800-05787-02
|
-A0
|
PXM-HD
|
800-05052-03
|
-A0
|
AXSM-1-2488/B
|
800-07983-02
|
-A0
|
SMFSR-1-2488/B
|
800-07255-01
|
-A0
|
SMFLR-1-2488/B
|
800-08847-01
|
-A0
|
SMFXLR-1-2488/B
|
800-08849-01
|
-A0
|
AXSM-16-155/B
|
800-07909-05
|
-A0
|
AXSM-4-622/B
|
800-07910-05
|
-A0
|
AXSM-16-T3E3/B
|
800-07911-05
|
-A0
|
MMF-8-155-MT/B
|
800-07120-02
|
-A0
|
SMFIR-8-155-LC/B
|
800-07864-02
|
-B0
|
SMFLR-8-155-LC/B
|
800-07865-02
|
-B0
|
SMFIR-2-622/B
|
800-07412-02
|
-B0
|
SMFLR-2-622/B
|
800-07413-02
|
-B0
|
SMB-8-T3
|
800-05029-02
|
-A0
|
SMB-8-E3
|
800-04093-02
|
-A0
|
SMB-4-155
|
800-07425-02
|
-A0
|
XM-60
|
800-04706-06
|
-A0
|
MGX-APS-CON-8950
|
800-15308-01
|
-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
|
Hardware Compatibility Matrix
Table 5 shows which back cards can be used with each front card in Release 2.1.76.
Table 5 Back Cards and Connectors Supported by Front Cards
Front Card Type
|
Back Card Types
|
Supports APS Connector (MGX-APS-CON)
|
AXSM-1-2488/B
|
SMFSR-1-2488/B
SMFLR-1-2488/B
SMFXLR-1-2488/B
|
Yes
Yes
Yes
|
AXSM-4-622/B
|
SMFIR-2-622/B
SMFLR-2-622/B
|
Yes
Yes
|
AXSM-16-155/B
|
SMB-4-155
MMF-8-155-MT/B
SMFIR-8-155-LC/B
SMFLR-8-155-LC/B
|
Yes
Yes
Yes
Yes
|
AXSM-16-T3E3/B
|
SMB-8-T3
SMB-8-E3
|
N/A
|
PXM45/B
|
PXM-HD
PXM-UI-S3
|
N/A
|
RPM-PR-256
RPM-PR-512
|
MGX-MMF-FE
MGX-RJ45-4E/B
MGX-RJ45-FE
|
N/A
|
New and Changed Information
This section contains a summary of recent features, hardware, or commands that have been implemented in MGX 8850.
New Features and Enhancements in Release 2.1.60 through 2.1.76
Release 2.1.60 contained 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
•RPM 1:N Redundancy on MGX 8950
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 and 8950 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.76 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.
New Features in Release 2.1.70
The following features were new in release 2.1.70:
•Config Verify
Config Verify
This is an off-line utility that runs on a Solaris workstation to verify the integrity of configuration files transferred from the hard disk of the MGX 8850 to the Solaris workstation. This tool helps validate uploaded configuration files.
New Features in Release 2.1.76
Release 2.1.76 introduced Multiprotocol Label Switching (MPLS) over ATM using virtual circuit (VC) merge.
Multiprotocol Label Switching (MPLS) over ATM using VC Merge
The virtual circuit (VC) merge facility allows a switch to aggregate multiple incoming flows with the same destination address into a single outgoing flow. Wherever VC merge occurs, several incoming labels are mapped to one single outgoing label. Cells from different virtual channel identifiers (VCIs) going to the same destination are transmitted to the same outgoing VC using multipoint-to-point connections. This sharing of labels reduces the total number of VCs required for label switching.
Without VC merge, each path consumes one label VC on each interface along the path. VC merge reduces the label space shortage by sharing labels for different flows with the same destination. Therefore, VC-Merge connections are unidirectional, and furthermore, all merged connections must be of the same service type.
Note To support VC-merge, the ATM switch requires that AXSM cards allow multiple VC frames to be merged into a single VC without interleaving cells inside AAL5 frames. The RPM is the control point, where LSC resides.
VC Merge is enabled by default when the MPLS over ATM network is configured and is only used when the RPM is used as an LSC (Label Switch Controller). Because it is enabled by default, the only commands necessary are:
no tag-switching atm vc-merge to disable VC Merge
and
tag-switching atm vc-merge to enable VC Merge
For more information, see MPLS Label Switch Controller and Enhancements at http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t8/ftlsc.htm#xtocid15
Enhancements
The product enhancement requests (PERs) in Table 6 were included in MGX 8850 and/or MGX 8950 Releases 2.1.70 through 2.1.76. Refer to the "MGX 8850 and MGX 8950 Command Reference for Release 2.1"at http://www.cisco.com/univercd/cc/td/doc/product/wanbu/8850r21/index.htm for further details about the commands mentioned in these enhancements.
Table 6 List of Product Enhancement Requests in MGX Release 2.1.76
Enhancement Number
|
Purpose
|
2832
|
This enhancement displays Bit Error Counts on AXSM lines. The command is dspbecnt. The AXSM-E card supports this command in 2.1.75. The display follows the same style as the PXM1 uplinks.
|
2835
|
The dclk command is available on the active PXM45 Card in an MGX 8850 node. It provides a display of the Digital to Analog Converter (DAC) value and the Deviation in Parts per Million of the output frequency for the current clock source from the nominal frequency value for the local oscillator on the PXM45 UIS3 card.
|
2837
|
After a user enters tstdelay/tstconseg, the results should be shown after the command is run.
|
2836
|
The node name was not shown in all command displays, and is now added to the following PNNI command displays: dspcon, dsppnni-link, dsppnni-neighbor.
Note: Correction to MGX 2.1.70 release notes: The conntrace command was removed from this list of commands, but the node name will be shown in conntrace in a future release.
|
2838
|
(CSCdv27524): Need master/slave filter on dspconcnt and dspcons. The dspconinfo command displays the connection counts by class of service (CSCdt11863), and the new enhancement (CSCdv27524) allows users to get master/slave counts in. The new feature provides a filter "-owner" with (slave/master) as options.
|
2839
|
The AXSM card now displays the total number of active lines, ports, and channels. A new CLI command "dsptotals" was added to accommodate this request.
|
2840
|
(CSCdt54869): This enhancement was made because dsppnports showed confusing DAX counts. The dsppnports command now shows three sections. The first section is called Summary of Active connections, the second section is called the Summary of Total Configured SPVC Endpoints, and the third section is called the Summary of Total Active SVC/SPVC Intermediate Endpoints.
|
2841
|
Since the SCT default Traffic Parameters (PCR, MCR, SCT etc.) are not used in programming the connection, then it should be removed from the SCT File.
|
2842
|
(CSCdu84598): Add threshold and current reset count info in the reset log. This PER has been implemented as requested. The log message associated with MAX_CD_RESET feature should show the threshold for resets that has been configured. The cnfndparms command is used to configure the max card reset PER window.
|
2843
|
This enhancement raises the priority of the CLI session. Enter ESC-CTRL-2 either while in a CLI session or at the login prompt. The session will remain at a higher priority until the session is terminated by logging out or timeout. This is available for debugging performance problems if a CLI command cannot be executed because the system is too busy. This should NOT be used for normal operations.
|
2844
|
The clrsarcnt command will clear the SAR Counters which are displayed in dspsarcnt.
|
2845
|
When a connection is being routed and there is no response to signaling for that connection, a crankback-type message will be generated so that the connection can try alternate routes instead of waiting forever.
|
2849
|
The dspstbyclksrcs command, available from the standby PXM45 card, displays the state of configured clock sources.
|
2889
|
A new command, checkflash, checks for data corruption by verifying flash content against its checksum.
|
2920
|
This PER is a configuration utility on a Workstation to verify the switch configuration database.
|
2892
|
The commands addlnloop and addchanloop should use the same name convention for Local & Remote loopback.
|
3092
|
All commands dealing with alarms should display a logical hierarchy, for example, e.g. dspcdalms <slot #>
|
3417
|
The Trap managers will be automatically deleted if there is no `keep alive' request from CWM for the configured intervals.
|
3737
|
This enhancement will display the total number of User Connections, Control Connections, and the sum of User and Control Connections in PNNI command dsppnports.
|
3917
|
This enhancement adds additional varbinds in the existing trap definitions to identify what kind of device trap has been sent.
|
5186
|
This enhancement will report consistent alarm on PXM and AXSM. AXSM standby will not show any alarm.
|
Additional Software Information
MIB
The SNMP MIB release for 2.1.76 is mgxmibs2176.tar.
Service Class Template File Information
The Service Class Template (SCT) bundle in release 2.1.76 includes updates:
•AXSME_SCT.CARD.5
•AXSME_SCT.PORT.5
•AXSME_SCT.PORT.6
The default SCTs provided with release 2.1.76 are as follows:
AXSM and AXSM/B
•SCT 2 - policing enabled, PNNI
•SCT 3 - policing disabled, PNNI
•SCT 4 - policing enabled, MPLS and PNNI
•SCT 5 - policing disabled, MPLS and PNNI
AXSM-E
•SCT 4 - policing enabled, ABR-tag parameter included
•SCT 5 - policing enabled, ABR-tag parameter not included. Use this SCT for upload to CWM workstation, because earlier versions of CWM had a problem uploading SCT files that included the TAG ABR serv type. We currently do not support TAG ABR, but the problem is fixed now. In general, this is for use on UNI ports.
•SCT 6 - port SCT with policing disabled. The card SCT that can be used with port SCT 6 is AXSME_SCT.CARD.5. In general, this is for use on NNI ports.
Note AXSM-E SCT 5 has some changes to the default values (other than TAG-ABR not being present). It is the latest version of the SCT file that is being released with 2.1.76.
New Hardware Supported in Release 2.1.76
The following new hardware is supported by the Release 2.1.76 software:
•AXSM/B OC-48 (No APS support)
•MGX 8950 Switch
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 forservice providers using MGX 8950 and those who prefer to use a single OC-48/STM-16 card type for both MGX 8950 and the MGX 8850.
New and Changed Commands
Before the introduction of the MGX 8950 switch, releases 2.1.60 and 2.1.70 introduced many new commands. The commands that are common to both the MGX 8850 and MGX 8950 switches are listed in "New Commands". The commands that are unique to the MGX 8850 switch are listed under "New Commands for the MGX 8850 Switch Only". There are no commands that are unique to the MGX 8950 switch.
Please refer to the "MGX 8850 and MGX 8950 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 were 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
These commands were new to Release 2.1.70.
•cnfxbaradmin
•dspadjlnalms
•dspdevalms (was clrxbaralm(s))
•dspdeverr
•dspdeverrhist (was dspxbarerrcnt)
•dspxbarplanealms
•dspxbarslotbwalms
New Commands for the MGX 8850 Switch Only
The following new commands apply only to the MGX 8850 switch:
•clradjlnalmcnt
•cnfautolndiag
•cnfbert
•cnfcdstat
•copycons
•dspadjlnalm
•dspadjlnalmcnt
•dspautolndiag
•dspbert
•dspbertstats
•dspcdstatcnf
•dspchanstat
•dspegrbucketcnt
•dsphardwaremastership
•dspingbucketcnt
•dsplnpmbucketcnt
•insbiterror
•reboot
•startbert
•stopbert
Changed CLI Commands
Because this is the introduction of the MGX 8950 switch, there are no changed commands.
Removed Commands
These commands were removed from release 2.1.70
•dspxbaralm(s) is now dspdevalms
•dspxbarerrcnt is now dspdeverrhist
•dspxbaralarm
Previously Undocumented Commands
The following commands are now documented in the "MGX 8850 and MGX 8950 Command Reference, Release 2.1":
•actaudit
•cnfpnctlvc
•cnfpnportloscallrel
•copycons, copychans
•dspcprotbls
•dspmsq and dspmsgqs
•dsppnctlvc
•dsppnportloscallrel
•routeadd
•routedelete
•routenetadd
•rrtcon
•sesnwatchdog
•smclrscrn
•xbaradmin
Limitations and Restrictions
This section describes the following issues for Releases 2.1.60 through 2.1.76:
•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 the MGX 8950, references to "AXSM" refer to the AXSM/B cards.
•For a graceful upgrade, you must upgrade from version 2.0.16 or 2.1.75 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/B cards do not have a policing function enabled.
•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.76 (number 2 and 3, which were included in version 2.0.13 are similar to number 2 and 3 for 2.1.76) 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:
•Whenever there are 2 RPM cards on adjacent slots, driven by the same cell bus clock, the clock rate should be set to 42 MHz for traffic shaping, using the command nfcbclk. This configuration will be lost if the node rebuilds due to resetsys or a power cycle. The user will have to manually re-configure the cell bus clock rate after the rebuild, using the cnfcbclk command.
•On an MGX 8850 or MGX 8950 node, when the chassis is loaded with 6 or more RPM-PR cards, and if every card is configured to download the IOS runtime image from the PXM-45 hard disk, occasionally, upon entering a resetsys command or after a power cycle, some of the RPM-PR cards may go into the failed state. To reset the failed RPM-PR cards, enter the resetcd <slot #> command for each failed card.
•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
