Table Of Contents
Release Notes for Cisco MGX 8850, Cisco MGX 8950, and Cisco MGX 8830, Software Release 5.3.10
Non-Redundant Upgrade Procedure
Cisco MGX 8800 Series Operating and Storage Environment
Guidance for Operating and Storage Environments
Operating Environment Specifications
Non-operating and Storage Environment Specifications
Multilink Point-to-Point Protocol Enhancements for CDMA2000 and EV-DO
Fractional T1/E1 Links for ATM Services
Fractional T1/E1 Configuration
Fractional T1/E1 Configuration Limitations
Remote IP Management Connection Enhancements
Management Connection Limitations
Configuring an RPM Management Connection
Management Configuration—Example
Routing Enhancement for AXSM-XG Cards
Graceful Upgrades to AXSM-XG Cards
Multilink PPP on the MPSM-T3E3-155 Card
PXM45/C Support in the MGX 8830/B Chassis
Compression and Multiplexing Support for RPM-PR Cards
Multilink PPP Feature for CDMA2000 and EV-DO
MPSM-155-T3E3 and MPSM-16-T1E1 Online Diagnostics
Private Network Node Interface Current Route Feature
Operational and Redundancy Limitations
Software/Firmware Compatibility Matrix
MGX and RPM Software Version Compatibility Matrix
Product IDs, Card Types, and APS Connectors
Service Class Template File Information
MGX Release 5.3.10 Limitations, Restrictions, and Notes
MGX Voltage Measurement Limitation
MGX Chassis Bandwidth Limitations
PXM1E Reserved Virtual Channel Identifiers
PXM1E Point to Multipoint Support
PXM45 and PXM1E System Limitations
Clearing the Configuration on Redundant PXM45 and PXM1E Cards
SPVC Interoperability Limitations
AXSM-16-155-XG with MCC Back Card Limitations
AXSM-32-T1E1-E and PXM1E-16-T1E1 Card Limitations
Clearing Card Configuration Notes
Persistent Topology Limitations
Fault Isolation and Trace Limitations
Serial Bus Path Fault Isolation Limitation
Cell Bus Path Fault Isolation and Recovery Limitations
Path and Connection Trace Notes
Non-native Controller Front Card and PXM-HD Card Notes
Other Limitations and Restrictions
Installation and Upgrade Procedures
Online Insertion or Removal of the MGX-RPM-1FE-CP Back Card
Known Anomalies in Release 5.3.10
Resolved Anomalies in Release 5.3.10
Status Changed Anomalies in Release 5.3.10
Resolved Anomalies in Previous Releases
Resolved Anomalies in Release 5.3.00
Resolved Anomalies in Release 5.2.10
Resolved Anomalies in Release 5.2.00
Resolved Anomalies in Release 5.1.20
Resolved Anomalies in Release 5.1
Resolved Anomalies in Release 5.0.20
Resolved Anomalies in Release 5.0.10
Resolved Anomalies in Release 5.0.00
Known Route Processor Module or MPLS Anomalies
Cisco PNNI Network Planning Guide for MGX and SES Products Updates
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
Product Alerts and Field Notices
Obtaining Technical Assistance
Cisco Technical Support & Documentation Website
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Release Notes for Cisco MGX 8850, Cisco MGX 8950, and Cisco MGX 8830, Software Release 5.3.10
Part Number OL-11147-01 Revision C1, May 2008
Table of Contents
Overview
These release notes contain the following sections:
•
Service Class Template File Information
•
•
•
•
•
•
About Release 5.3.10
Version .201 of Release 5.3.10 is a patch release that does not introduce new features. The resolved anomalies for Version .201 are listed in Table 16.
These release notes describe the system requirements, new features, and limitations that apply to Release 5.3.10. These notes also contain Cisco support information. Release 5.3.10 is a software and hardware release for the following Cisco multiservice switches (MGXs):
•
•
•
•
•
Locating Software Updates
Release 5.3.10 software is located at:
http://www.cisco.com/public/sw-center/wan/wan-planner.shtml
Route Processor Module (RPM) Cisco IOS software images are located at:
http://www.cisco.com/public/sw-center/sw-ios.shtml
Features in Release 5.3.10
Release 5.3.10 includes the following new features and warnings.
Enhanced VXSM Card Support
Release 5.3.10 supports the Processor Switch Module Hard Disk Voice (PXM-HDV) back card, which supports four or more VXSM cards on an MGX 8850 switch. The size of the D partition on the PXM-HDV back card is 2000 Mb.
Non-Redundant Upgrade Procedure
To migrate from PXM-HD to PXM-HDV back cards in a non-redundant configuration, perform the following steps:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Redundant Upgrade Procedure
To migrate from PXM-HD to PXM-HDV back cards in a redundant configuration, perform the following steps:
Step 1
Step 2
Step 3
Step 4
Cisco MGX 8800 Series Operating and Storage Environment
This section describes the operating and storage environments for the Cisco MGX 8800 series multiservice switches, and explains how to prevent oxidation and corrosion problems.
Guidance for Operating and Storage Environments
Dew points indicate the amount moisture in the air. The higher the dew point, the higher the moisture content of the air at a given temperature. Dew point temperature is defined as the temperature to which the air would have to cool (at constant pressure and constant water vapor content) in order to reach saturation. A state of saturation exists when the air is holding the maximum amount of water vapor possible at the existing temperature and pressure
When the Relative Humidity is high, the air temp and dew point temperatures are very close. The opposite it true when the Relative Humidity is low. When the dew point temperature and air temperature are equal, the air is saturated with moisture. Locations with high relative humidities have air that is close to being saturated with moisture. When saturated air cools it cannot hold as much moisture and can cause moisture migration and penetration into the system. This moisture can cause corrosion of internal components.
A storage environment that experiences temperature and/or humidity variations over a short period of time can create a condensing environment, and this is considered an uncontrolled environment. An environment that maintains constant temperature and humidity is considered and climate controlled environment. A temperature and humidity controlled operating and storage environment is required at all times to prevent condensation that can subsequently lead to oxidation of plated metal parts. Cisco recommends that both long term and short term storage environments be climate controlled to prevent humidity and temperature variations that create condensation. Buildings in which climate is controlled by air-conditioning in the warmer months and by heat during the colder months usually maintain an acceptable level of humidity for system equipment.
Note
To prevent oxidation, avoid touching contacts on boards and cards, and protect the system from extreme temperature variations and moist, salty environments.
Operating Environment Specifications
The following specifications define the operating environment:
•
–
–
•
–
–
•
–
–
Non-operating and Storage Environment Specifications
The following specifications define the non-operating and storage environments:
•
–
–
•
–
–
•
–
–
Features in Release 5.3.00
This release includes the following new features:
•
•
•
•
Multilink Point-to-Point Protocol Enhancements for CDMA2000 and EV-DO
CDMA2000 applications can use the MGX 8850 (PXM45) platform to aggregate traffic from several Base Transceiver Station (BTS) routers and transfer that traffic to an IP network. This application relies on the Multilink Point-to-Point Protocol (MLPPP), which carries traffic between the BTS routers and MPSM service modules. This capability was introduced in earlier releases; this release enhances the MLPPP features on the MPSM and RPM-XF cards.
The MLPPP feature for MPSM-16-T1E1 and MPSM-T3E3-155 cards includes:
•
•
•
•
•
•
The RPM-XF supports:
•
Summary of MLPPP Changes
Table 1 compares the features of Release 5.2 to Release 5.3:
MLPPP Configuration
The MLPPP features in Release 5.3 do not change the MLPPP configuration procedures and command syntax; only the valid ranges for links and bundles change (see Table 1). For more information about command updates, see the "Changed MPSM Commands" section.
For information about MLPPP configuration procedures and commands, see the following documents:
•
In the Provisioning Multilink PPP chapter, the new limits for bundle and link parameters apply.
•
MLPPP Upgrade Considerations
Consider the following MLPPP characteristic when upgrading to software Release 5.3:
•
Software Releases 5.1 and 5.2 permit different speed links, so existing bundles may exist with links that have mismatched speeds. After you upgrade to Release 5.3, the dspppplinks command still shows the mismatched links, but the links are down and the system logs the following error:
EM-7-EM_EVENT emRoot transactAddPppLinkEM Event: Id:448e, Line#825:64kbps ppp link 23 cannot be added to the bundlehaving 56kbps linksTo restore PPP link operation, delete the mismatched links and add links of equal speeds to the bundle.
•
Software Releases 5.1 and 5.2 permit 64 Kbps links on lines with AMI coding, so your system may be configured with these links. After you upgrade to Release 5.3, the dspppplinks command still shows the links, but the links are down and the system logs the following error:
EM-7-EM_EVENT emRoot transactAddPppLinkEM Event: Id:448e, Line#860:64Kbps PPP link "LinkNum" not supported on lineswith AMI line codingTo restore PPP link operation, delete the 64 Kbps links, change the line coding to b8zs, and then add the links back into the bundle.
•
•
Bundles added before upgrading to software Release 5.3 have a default value of 8600 cps. For bundles with E1 links, modify the normpvcbw value manually using the cnfmpbundleparams command.
Fractional T1/E1 Links for ATM Services
The initial release of the MPSM-16-T1E1 card supported ATM services, but for full T1/E1 lines only. This release expands the ATM service capabilities to support both full and fractional T1/E1 ports.
Fractional T1/E1 Configuration
The configuration procedures for ATM services do not change for fractional T1/E1 ports. When you add a fractional T1E1 port, you specify the range of DS0s to use. The addport command has arguments to specify a range of DS0s, and the dspport command shows DS0 ranges. For more information about command updates, see the "Changed MPSM Commands" section.
For more information about ATM configuration procedures and commands, see the following documents:
•
•
Fractional T1/E1 Configuration Limitations
Fractional T1/E1 configurations have the following configuration restrictions:
•
•
•
•
Fractional T1/E1 configurations have the following functional limitations:
•
•
•
•
•
•
•
•
Security Enhancements
Release 5.3.00 introduces the following security enhancements:
•
•
SFTP and SSH Features
Cisco MGX switches currently support the following remote access applications and protocols:
•
•
This release adds SFTP to the PXM45 card and SSH to the RPM-XF card. SFTP is an alternative to FTP that provides for secure (and authenticated) file transfer between a PXM card and a remote host.
For more information about managing Telnet and SSH features, see the following:
•
–
–
•
–
SFTP Limitations
The SFTP feature has the following limitations:
•
•
•
•
–
–
–
–
–
–
Disabling Telnet and FTP
By default, the PXM45 permits unsecured access from Telnet and FTP clients, as well as secure access from SSH and SFTP clients. Option 16 of the cnfndparm command, along with option 15, disables unsecured Telnet and FTP access from remote hosts while permitting secure SFTP and SSH sessions.
If you plan to use SFTP and SSH on the PXM45, you should consider disabling FTP and Telnet access to improve security. Telnet and FTP transfer all user ID, password, and session management information between the client and the PXM45 using clear text. Clear (or unencrypted) text can be read by network analysis and snooping tools.
Initializing SFTP
Upgrading PXM software is not sufficient to initialize and enable the SFTP feature. You must initialize the sshd_config file and reset the MGX chassis. Because resetting a chassis can interrupt traffic, you should initialize SFTP before upgrading software so you do not need to reset it later.
To initialize SFTP, perform the following steps:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Note
Remote IP Management Connection Enhancements
You can manage an MGX 8850 node directly from an Ethernet or console port on the PXM, or you can configure a remote path to the PXM through a service module or route processor module. The following management paths are supported in earlier releases:
•
•
Earlier releases supported intranode connections only, and you could only have one PVC between an RPM and PXM. Release 5.3.00 enhances the ATM0 feature to internode connections, where an RPM on one MGX switch connects to PXMs on other MGX switches using PNNI. And now you can manage multiple PXMs from a single RPM.
Management Connection Limitations
The IP addresses of hosts accessing the MGX 8850 node are stored in a RAM cache. Because this cache has a limit of 50 entries, only 50 IP hosts can actively access the node at one time. New IP hosts are blocked until the cache clears (as result of inactivity from some hosts) to make room for new entries.
Multiple RPMs can connect to the same PXM, but each RPM can have only one connection to the PXM. This is because the PXM has a single ATM0 address.
Note
Note
Configuring an RPM Management Connection
The following quick start procedure summarizes the RPM configuration procedure. This procedure assumes the RPM already has a switch partition configured for the management connection.
The following quick start procedure summarizes the PXM configuration procedure.
Management Configuration—Example
This example shows how to configure a management connection between an RPM-XF on one switch and the PXM on another switch. In this example, the RPM-XF switch partition and the PXM ATM0 interface are already available.
The following example shows how to configure the RPM-XF switch interface, add a slave connection, and display the NSAP address.
Router(config)#interface switch1.100 point-to-pointRouter(config-subif)#ip address 10.10.10.200 255.255.255.0Router(config-subif)#pvc 0/100Router(config-if-atm-vc)#ubr 1544Router(config-if-atm-vc)#switch connection vcc 0 100 master remoteRouter(config-if-swconn)#endRouter#show switch connection vcc 0 100----------------------------------------------------------Alarm state : No alarmLocal Sub-Interface : 100Local VPI : 0Local VCI : 100Remote NSAP address : defaultLocal NSAP address : 47.0091810001040000ABCD7777.000001011802.00Remote VPI : 0Remote VCI : 0The following example shows how to configure the ATM0 interface of the PXM card, add a master connection to the RPM-XF, and verify that the connection is state is up. The NSAP address and VPI/VCI entered are the values previously displayed at the RPM-XF.
LA.8.PXM.a > ipifconfig atm0 10.10.10.144 netmask 255.255.255.0LA.8.PXM.a > svcifconfig atm0 remote 47.0091810001040000ABCD7777.000001011802.00 pvc 0.100LA.8.PXM.a > dspsvcifM8850_LA System Rev: 05.02 Apr. 25, 2006 16:36:38 PSTMGX8850 Node Alarm: NONEIP CONNECTIVITY SVC CACHE--------------------------------------------------------------------atm (unit number 0):Remote AESA: 47.0091.8100.0104.0000.abcd.7777.0000.0101.1802.00SPVC VPI.VCI: 0.100 (PCR=3642 cps)Flags: (0x6) ATMARP,LLCENCAPState: (0x1) UPRxLCN: 1505 TxLCN: 1505LCNindex: 766 LCNcallid: 0x80000001Input Frames: 1 Output Frames: 1Input Errors: 0 Output Errors: 0Input ArpReq: 0 Output ArpReq: 0Input ArpRply: 0 Output ArpRply: 0Input InArpReq: 0 Output InArpReq: 0Input InArpRply: 1 Output InArpRply: 0Routing Enhancement for AXSM-XG Cards
Extended link management interface (XLMI) and enhanced network-network interface (ENNI) are protocols that connect broadband packet exchange (BPX)-based autoroute networks to MGX 8850 (PXM45)-based PNNI networks. This release extends this capability to the following AXSM-XG cards:
•
•
For compatible back cards, see Table 8.
For more information about XLMI/ENNI configuration procedures and commands, see the XLMI Link Configuration Quickstart section in the following document:
•
Platform Enhancements
This release adds the following MGX platform enhancements.
•
•
•
Through this QoS enhancement, the PXM QE1210 is programmed using information from the MPSM so it can manage traffic dynamically based on the committed rate of the connections and interface policy.
MGX 8830/B Enhancements
The MGX 8830/B is a 7-double-height horizontal slot chassis, where slots 1 and 2 are reserved for the PXM. The MGX 8830/B (PXM45/C) now supports the RPM-PR and RPM-XF cards.
RPM-PR Ethernet Back Card
The MGX-RJ45-5-ETH is a single-height back card for the RPM-PR that provides five RJ-45 connectors for Gigabit Ethernet, Fast Ethernet, or Ethernet lines. Figure 1 shows the MGX-RJ45-5-ETH faceplate.
Figure 1 MGX-RJ45-5-ETH Back Card
Table 2 lists the maximum cable length for each of the supported speeds on the MGX-RJ45-5-ETH card.
Table 2 MGX-RJ45-5-ETH Card Supported Speeds and Maximum Cable Lengths
10 Mbs
Up to 100 meters
100 Mbs
Up to 100 meters
1000 Mbs
Up to 50 meters
Features in Release 5.2.10
Release 5.2.10 adds Unique Device Identifier (UDI) compliance for the Cisco MGX 8830/B chassis and backplane.
Features in Release 5.2.00
Release 5.2.00 has the following features:
•
•
•
•
MGX-VXSM-T3 Card
Release 5.2.00 introduced a third VXSM card for the support of T3 lines. The card consists of a front card with six T3 ports and a half height back card with three T3 ports. The front card can be configured with either one back card or two back cards.
AXSM-8-622-XG Card
The AXSM-8-622-XG is an 8-port OC-12/STM-4 card that supports clear-channel OC-12c/STM-4 or OC-12/STM-4 channelized down to OC-3c/STM-1 and DS3. This card complements the family of AXSM-XG cards, which includes the AXSM-16-155-XG, AXSM-4-2488-XG, and AXSM-1-9953-XG.
The AXSM-8-622-XG card has the following functionality:
•
•
•
•
•
•
•
•
•
•
•
–
–
–
•
–
–
–
–
–
–
•
–
–
–
–
–
•
•
•
•
–
–
•
•
–
–
•
The AXSM-8-622-XG card has the following restrictions:
•
•
•
Graceful Upgrades to AXSM-XG Cards
You can gracefully upgrade AXSM, AXSM/B, and AXSM-E cards to AXSM-XG cards. The AXSM-16-155-XG and AXSM-8-622-XG cards have a higher port density than the equivalent AXSM-E cards, and the AXSM-16-155-XG and AXSM-8-622-XG have better traffic management support than their AXSM/B counterparts.
Graceful upgrades simplify the process of migrating to the newer AXSM-XG cards. During the upgrade, the MGX control processor transfers the configuration/connection database from the previously installed AXSM card to the new AXSM-XG, which preserves all connection configurations. The upgrade process might cause an outage of up to 4 minutes.
You can install and operate any number of AXSM-XG cards in conjunction with AXSM, AXSM/B or AXSM-E in an MGX 8850 chassis equipped with the PXM45 processor. You can install and operate any number of AXSM-XG cards in conjunction with AXSM/B in an MGX 8950.
Card redundancy is supported only between identical front and back card pairs. For example, an AXSM-16-155-XG can only be redundant to another AXSM-16-155-XG, where the two front cards use an identical set of back cards.
For more information about the upgrade procedure, see the Cisco MGX 8800/8900 Series Configuration Guide, Release 5.2.
Multilink PPP on the MPSM-T3E3-155 Card
This release adds Multilink PPP (MLPPP) to the MPSM-T3E3-155 card. MLPPP includes the following capabilities:
•
•
•
•
•
•
•
•
•
•
•
•
•
The MLPPP feature has the following restriction:
•
PXM45/C Support in the MGX 8830/B Chassis
A PXM45/C controller in an MGX8830/B chassis provides support for a selection of narrowband and broadband interfaces in an 8-slot chassis. The PXM45/C controller's 45Gbps switch matrix makes it possible to aggregate and switch traffic from a mix of narrow-band, DS3/E3, OC-3c/STM-1, and OC-12/STM-4 ATM ports, and simplifies the process of scaling a network node as connection counts increase.
Mobile PNNI Support
This release adds the Mobile PNNI feature to the existing PNNI functionality. Generally a PNNI network has a fixed hierarchy where each element has a fixed point of attachment. Mobile PNNI extends a fixed network infrastructure to mobile ATM switches that are roaming in the network. To maintain connectivity when the location of the mobile ATM switch changes, mobile switches are allowed to dynamically change peer group membership. To implement this feature, you establish a link to the fixed network; the mobile network then finds the proper peer group and hierarchy and joins the network.
Mobile PNNI allows each mobile network to build its own PNNI hierarchy and integrate the hierarchy of the fixed network as a logical group node (LGN). In the context of mobile PNNI, it is called Mobile LGN. A mobile logical group node has the capability to dynamically change its membership from one peer group to another as it attaches to different fixed switches. A mobile logical group node is only permitted to join a parent peer group of one of the fixed switches.
The ATM forum describes mobile PNNI in publication AF-RA-0123.000, PNNI addendum for mobility extensions Version 1.0, which is available at the following location:
ftp://ftp.atmforum.com/pub/approved-specs/af-ra-0123.000.pdf
Compression and Multiplexing Support for RPM-PR Cards
The MGX-RPM-1FE-CP (one-port, Fast Ethernet-Co-processor) back card is an MGX8850/RPM-PR back card that off-loads the following processes from the Route Processor Module (RPM-PR):
•
•
This feature was previously supported on PXM1 systems only. This release extends this capability to PXM1E/PXM45 systems.
For more information, refer to:
http://cisco.com/en/US/products/hw/routers/ps4062/prod_module_install_config_guide09186a00801f42d7.html
Features in Release 5.1.20
Release 5.1.20 supports Evolution-Data Optimized (EV-DO) traffic on the MPSM-16-T1E1. EV-DO is a high-speed data overlay for CDMA2000, where the MGX 8850 operates as the aggregation node:
•
Features in Release 5.1.00
This section contains the descriptions of the following new features in Release 5.1.00:
•
•
MPSM-16-T1E1 Card
The MPSM-16-T1E1 is a single-height front card that accommodates one single-height back card and fits into a slot in the upper or lower bay of the following chassis systems:
•
•
The MPSM-16-T1E1 front card supports 16 ports with T1/E1 capabilities, depending upon which back card is installed. Each line can be channelized or unchannelized.
Limitation: Consolidated Link Layer Management for Frame Relay is not supported in this release.
Operational Modes
The MPSM-16-T1E1 supports two software modes:
•
•
During initial card startup, boot into either one mode or the other.
Supported Features
This section lists the features that are supported on the MPSM-16-T1E1 card.
Supported Services
The following services are supported:
•
•
•
•
•
General Features
The MPSM-16-T1E1 card supports the following general features:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
ATM Features
The MPSM-16-T1E1 card supports the following ATM features:
•
•
Guest
