Downloads |
Table Of Contents
Release Notes for Cisco MGX 8850 Software Version 2.1.79
Software/Firmware Compatibility Matrix
Additional Compatibility Information
New Features and Enhancements in Release 2.1.60 through 2.1.79
Hierarchical PNNI (Multiple Peer Group [MPG])
New Features in Release 2.1.70
XPVC/XPVP Termination on AXSM-E
New Features in Release 2.1.79
Multiprotocol Label Switching (MPLS) over ATM using VC Merge
Additional Software Information
Service Class Template File Information
New Hardware Supported in Release 2.1.76
AXSM-E module (T3/E3, OC3c/STM1, OC12c/STM4)
AXSM-1-2488/B (No APS support)
Commands with Privilege Changes
Previously Undocumented Commands
General Limitations, Restrictions, and Notes
Limitations for rteopt via parallel links
RPM-PR and MPLS Limitations, Restrictions, and Notes
Clearing the Configuration on Redundant PXM45 Cards
Installing and Upgrading to Release 2.1.79
Quickstart Procedures for Software Upgrades
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
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
Documentation on the World Wide Web
Contacting TAC by Using the Cisco TAC Website
Known Anomalies in Release 2.1.79
Anomalies Resolved in Release 2.1.79
Anomaly Status Changes in 2.1.79
Known Anomalies in Release 2.1.76
Anomalies Resolved in Release 2.1.76
Anomaly Status Changes in Release 2.1.76
Known Anomalies for Release 2.1.75
Anomalies Resolved in Release 2.1.75
Anomaly Status Changes in Release 2.1.75
Known Anomalies in Release 2.1.70
Anomalies Resolved in Release 2.1.70
Anomaly Status Changes in Release 2.1.70
Release Notes for Cisco MGX 8850 Software Version 2.1.79
Contents
About Release 2.1.79
These release notes describe the system requirements, new features, and limitations that apply to Release 2.1.79 for the MGX 8850 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.79 is a maintenance release for the MGX 8850 switch and a hardware and software release for the new MGX 8950 switch.
For information about the MGX 8950, see the "Release Notes for Cisco MGX 8950 Software Version 2.1.79."
Locating Software Updates
Software updates are located at Cisco Connection Online (CCO) at http://www.cisco.com/kobayashi/sw-center/wan/wan-planner.shtml and ftp://ftp.cisco.com/cisco/wan/firmware/mgx/8850/.
Acronyms
Table 1 lists acronyms used in these release notes.
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.79.
Table 3 lists the software that is compatible for use in a switch running Release 2.1.79 software. Note that the AXSM/B cards use the same software as AXSM cards.
Table 3 MGX and RPM Software Version Compatibility Matrix
Additional Compatibility Information
The following notes provide additional compatibility information for this release:
•
You can gracefully upgrade to Release 2.1.79 from Release 2.0.16 or Release 2.1.76.
•
•
•
•
•
Hardware Supported
Table 4 lists the hardware supported in Release 2.1.79.
Hardware Compatibility Matrix
Table 5 shows which back cards can be used with each front card in Release 2.1.76.
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.79
Release 2.1.60 contained these new features:
•
•
•
•
•
•
•
•
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:
•
•
•
•
•
•
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.79 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:
•
•
•
•
•
•
•
•
Note
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
•
•
•
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:
•
•
•
switchredcd Command on RPM-PR
The MGX RPM-PR now uses the switchredcd command to change active cards. This command replaces the softswitch command that was previously used and is now obsolete.
Enter the switchredcd command to manually change the active card to the standby card. You may want to do this if you need to remove the original active card from the MGX 8850 or MGX 8950 shelf.
Note
Using switchredcd to Change the Active Card
To change the active cards, follow the steps below, in which the primary or active card in slot 2 is switched to standby or secondary, and the standby card in slot 11 is switched to primary or active.
Step 1
Unknown.7.PXM.a > switchredcd 2 11switchredcd:Do you want to proceed (Yes/No)? ywhere 2 is the active or primary card and 11 is the standby or secondary card.
The card in slot 11 is now the active RPM-PR card, and the RPM-PR card in slot 2 is reset. It comes up in standby mode after a couple of minutes.
The new active card will not revert to standby mode automatically. Enter switchredcd to manually switch over the active card back to standby mode. This is the only way the active card will switch over to standby, unless the active card fails.
Step 2
Unknown.7.PXM.a > switchredcd 11 2switchredcd:Do you want to proceed (Yes/No)? ywhere 11 is now the active card and 2 is now the standby/secondary card.
New Features in Release 2.1.70
The following features were new in release 2.1.70:
•
•
•
•
OAM Loopback
This feature allows a PVC or SPVC ATM connection terminating on an AXSM-E card to be put into a loopback mode for testing purposes. Standard or non-standard OAM cell patterns are transmitted toward the AXSM-E with or without a CRC error. These cells are then looped back by the AXSM-E in the opposite direction. At the sourcing device, returning cells are compared to known transmitted cells in order to verify the integrity of the link. Up to 8 loopback connections are supported per AXSM-E card.
This loopback feature is available only on AXSM-E OC-3 cards with SMFIR line modules, and does not apply to VNNI links or SVC connections.
Benefits
This feature is targeted at ATM network applications requiring layer 2 loopback testing.
Limitations
•
•
•
ITU-T APS Annex B
Automatic Protection Switching, as described in ITU-T G.783, is supported on the AXSM-E OC-3 card with an SMFIR line module. Interoperability of this feature between the BPX and the MGX is not supported.
Benefit
This feature brings high levels of resiliency to ITU-T compliant network applications.
Limitations
•
•
XPVC/XPVP Termination on AXSM-E
This feature is intended to support the use of AXSM-E ports as end points for XPVC/XPVP connections in networks evolving from AR to PNNI, starting with MGX Release 2.1.70, BPX 9.3.30 and CWM 10.5.10.
Benefit
This feature further extends the Network Migration 1B capabilities to cover a new card type on the MGX Release 2.
Platforms and Considerations
The minimum release bundle required consists of MGX 8850 R2.1.79 with AXSM-E, BPX 9.3.36, and CWM 10.5.10 patch 1.
Design Guide and Application Notes
Similar to AXSM, AXSM-E does not support ABRFS service type. CWM allows the user to select ABRSTD or ABRFS at the BXM/AUSM-8/FRSM-8 for setting up XPVC/XPVP connections to AXSM-E. In the case of an ABRSTD connection, CWM automatically enables the necessary parameters at the termination points and at the NNI termination points to create a single congestion control loop between AXSM-E termination point and the remote XPVC/XPVP termination point.
For all service modules that do not support ABRSTD, for example, the ones on MGX 8220, FRSM-VHS and FRSM-2CT3 on MGX 82xx, XPVC/XPVB connection with AXSM-E will involve ABRFS segment in the AR domain and an ABRSTD segment in the PNNI domain. Each segment will have its own congestion control loop.
In this case, CWM checks if BXM-E is used for the XLMI link at the BPX gateway node. It automatically enables the corresponding AR termination point in that BXM-E with FCES, and also enables the internal VsVd at the AXSM-E termination point.
For BXM to AXSM-E connections with ABRFS service type, CWM automatically enables FCES at the BXM termination points in the AR segment, and enables internal VsVd at the AXSM-E termination point.
CWM aggregates alarms from the AR and PNNI segments to display the overall condition for the XPVC and for the individual XPVC segments. This is no change of functionality from using AXSM as XPVC/XPVP end points in terms of connections monitoring in the CM GUI.
CWM Service Agent supports the connection management of AR-PNNI type XPVC/XPVP with termination point on AXSM-E. This is no change of functionality from AXSM support.
The WFQ, Policing, VsVd and ABRSTD VsVd parameters in the SCT associated with AXSM-E must be configured prior to provisioning of any XPVC/XPVP. CWM provides the ability to download SCT files to the switch and associate them with AXSM-E.
Limitations
•
•
•
•
References
See the CWM 10.5.10 Release Note, the CWM 10.5 Installation Guide, and the Cisco MGX 8850 Switch Software Configuration Guide, Release 2.1 for the basic feature set of XPVC/XPVP Provisioning.
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.79
Release 2.1.79 was a maintenance release.
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
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.
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.79 includes updates:
•
•
•
The default SCTs provided with release 2.1.79 are as follows:
AXSM and AXSM/B
•
•
•
•
AXSM-E
•
•
•
Note
New Hardware Supported in Release 2.1.76
No new hardware was introduced in release 2.1.79, however the following new hardware was supported by Release 2.1.76 software:
•
•
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:
•
•
•
Note
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:
•
•
•
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 service those who prefer to use a single OC-48/STM-16 card type for the MGX 8850.
New and Changed Commands
This section summarizes commands that were added or changed in releases 2.1.60 and 2.1.70. 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
Caution
The command switchredcd is new to release 2.1.79, and makes softswitch obsolete. It is used to manually change the active card to the standby card.
These commands were new in Release 2.1.60:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
These commands were new to Release 2.1.70.
•
•
•
•
•
•
•
Changed CLI Commands
This command was changed in release 2.1.79:
•
These commands were changed in release 2.1.70:
•
•
•
•
•
•
•
•
These commands were changed in release 2.1.60:
•
•
•
•
•
•
•
•
•
•
•
•
Here are additional details for other commands that have changed in release 2.1.60.
•
•
•
•
