Table Of Contents
Bidirectional Forwarding Detection Version 1
DSCP Marking on RPM-XF Management Interface
Support for AXSM-1-2488/B Card in 8830/B Chassis with PXM45C
Support for Clear Channel E1 Lines
Support for BERT Tests on Clear Channel T3/E3 Lines
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 Cisco 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
Changed Commands in Release 5.4.00
Changed Commands in Release 5.3.20
Changed Commands in Release 5.3.00
MGX Release 5.4.00 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
Caveats with Status Change in Release 5.4.00
Known Route Processor Module or MPLS Caveats
Cisco PNNI Network Planning Guide for MGX and SES Products Updates
Obtaining Documentation, Obtaining Support, and Security Guidelines
Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Software Release 5.4.00
Revised: September 26, 2007, OL-11771-01Contents
The content of this document is arranged into the following major sections:
Bidirectional Forwarding Detection Version 1
DSCP Marking on RPM-XF Management Interface
Support for AXSM-1-2488/B Card in 8830/B Chassis with PXM45C
Support for Clear Channel E1 Lines
Support for BERT Tests on Clear Channel T3/E3 Lines
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 Cisco 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
Changed Commands in Release 5.4.00
Changed Commands in Release 5.3.20
Changed Commands in Release 5.3.00
MGX Release 5.4.00 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
Caveats with Status Change in Release 5.4.00
Obtaining Documentation, Obtaining Support, and Security Guidelines
About This Release
Version .201 of Release 5.4.00 is a patch release for VXSM that introduce a new feature (see DTMF Squelching).
These release notes describe the system requirements, new features, and limitations that apply to Release 5.4.00. These notes also contain Cisco support information.
Release 5.4.00 is a software release for the following Cisco multiservice switches (MGXs):
•
Cisco MGX 8830 (Processor Switch Module, or PXM1E)
•
•
•
•
Note
Locating Software Updates
Release 5.4.00 software is located at:
http://www.cisco.com/kobayashi/sw-center/wan/wan-planner.shtml
Route Processor Module (RPM) Cisco IOS software images are located at:
http://www.cisco.com/kobayashi/sw-center/sw-ios.shtml
New Features
Release 5.4.00 includes the following new features for the Cisco MGX platforms:
•
•
DTMF Squelching
Version .201 of this release contains the enhancements to VXSM to completely squelch DTMF digits. This feature can be provisioned using the CLI commands shown below.
Note
For H.248
Syntax Description
cnfh248profdtmf <Index> <DigitOnDuration> <DtmfPauseDuration> <DetectLongDigitDuration> <SuppressBearerDigit>
Option SuppressBearerDigit should be set to 1 to enable DTMF squelching.
For XGCP
Syntax Description
cnfxgcpprofdtmf <ProfileIndex> <SuppressBearerDigit>
Option SuppressBearerDigit should be set to 1 to enable DTMF squelching.
Bidirectional Forwarding Detection Version 1
Bidirectional Forwarding Detection version 1 (BFDv1) improves protocol convergence times by rapidly detecting failures in the path between routers. This is especially important for media that does not provide failure signaling, such as Ethernet, because the OSPF protocol can take a second or more to detect a signaling loss using hello messages. This is too long for some applications and can result in excessive data loss, especially at gigabit rates. BFDv1 quickly detects a media failure so that the OSPF protocol can quickly update routes.
DSCP Marking on RPM-XF Management Interface
This release supports Differentiated Services Code Point (DSCP) or IP Precedence marking for quality of service (QoS) configurations on the RPM-XF management back cards. With this enhancement, the RPM-XF supports Layer 3 QoS on the Fast Ethernet management back card.
Limitations
The following limitations apply to the DSCP marking of management packets on the RPM_XF management back card:
•
•
Flash MIB Support
Network management systems (NMS) can manage software images stored in boot flash using SNMP when the device supports the CISCO-FLASH-MIB. The RPM-XF supports the CISCO-FLASH-MIB in this and later releases. For MGX 8800/8900 multiservice switches, the NMS can query objects defined in the CISCO-FLASH-MIB through the PXM management interface or the RPM-XF management interface.
SNMPv3
Simple Network Management Protocol Version 3 (SNMPv3) is a standards-based protocol for network management. SNMPv3 provides secure access to devices using a combination of authentication and encryption of packets over the network. This assures that data can be collected securely from SNMP devices and that configuration messages cannot be viewed or altered.
The security features provided in SNMPv3 are:
•
•
•
Trap Squelch Feature
The large number of traps a large system can generate can degrade the performance of a network management system. The trap squelch feature helps limit the number of traps that Cisco MGX switches generate. You can either block all traps of a specific type or limit the rate of specified traps.
Limitations
The following limitations apply:
•
•
Support for AXSM-1-2488/B Card in 8830/B Chassis with PXM45C
With this release, support for the AXSM-1-2488/B card in the MGX 8830/B chassis has been added. The AXSM-1-2488/B card is already supported in the MGX 8850 and 8950 chassis.
Features in Release 5.3.20
Release 5.3.20 has the following new and changed features:
•
•
MPSM Licensing Changes
Release 5.3.20 enforces licenses through sales and support, rather than through software locks. Table 1 lists the MPSM licenses that are required for MPSM services and features. You must purchase licenses for the services and features that you plan to use on each MPSM card.
Note
Release 5.3.20 removes the PXM commands that support software locks and license alarms, and changes the commands that display alarm information. The following commands are removed or changed:
•
–
–
–
–
–
–
•
–
–
–
The MIB for Release 5.3.20 does not change, but returned license information is no longer valid.
Support for Clear Channel E1 Lines
Release 5.3.20 adds support for E1 clear channel on MPSM-16-T1E1 cards. Clear channel E1 dedicates the entire E1 bandwidth (2048 Kbps) to a single data stream, and does not contain DS0 channels. To implement this feature, a new line type (dsx1E1CLEAR) is added to the cnfln command. You can configure Frame Relay, ATM, or IMA ports on lines configured for E1 clear channel.
The addport command syntax does not change, but you must use the default values for ds0speed (64K), ds0beg (1), and ds0num (32) when adding a clear channel, even though the line is not actually channelized.
For example, the following commands configure line 1.10 for clear channel, add port 11 to the line with type frameRelayService and the default SCT, and then add a slave connection with DLCI 400, channel type frNIW, high-priority service, and CIR of 2048 Kbps. Notice that the default values for addport correctly configure the channelization parameters for clear channel operation.
M8850_SF.27.MPSM16T1E1[FR].a > cnfln 1.10 -lt 9M8850_SF.27.MPSM16T1E1[FR].a > addport 11 1.10 1 0M8850_SF.27.MPSM16T1E1[FR].a > addcon 11 400 1 1 2 2048000For more information about configuring lines, see the Cisco ATM and Frame Relay Services (MPSM-T3E3-155 and MPSM-16T1E1) Configuration Guide and Command Reference, Release 5.2, "Preparing MPSM-T3E3-155 and MPSM-16-T1E1 Cards and Lines for Communication."
Support for BERT Tests on Clear Channel T3/E3 Lines
Release 5.3.20 adds support for BERT tests on clear channel T3/E3 lines on MPSM-T3E3-155 cards. To support this feature, the following commands now accept a line number (bay.line) for the bertifNum argument:
•
•
•
•
•
•
•
•
•
Additionally, the dsplnalm and dsplnalms commands display the BERT status for a T3/E3 line.
For more information about configuring BERT tests, see Cisco ATM and Frame Relay Services (MPSM-T3E3-155 and MPSM-16T1E1) Configuration Guide and Command Reference, "Card Management on MPSM-T3E3-155 and MPSM-16-T1E1."
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 a Cisco 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 Cisco 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 2 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 2). 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 a Cisco 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 Cisco 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 Cisco MGX 8850 (PXM45)-based PNNI networks. This release extends this capability to the following AXSM-XG cards:
•
•
For compatible back cards, see Table 9.
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.
Cisco MGX 8830/B Enhancements
The Cisco MGX 8830/B is a 7-double-height horizontal slot chassis, where slots 1 and 2 are reserved for the PXM. The Cisco 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
Guest
