Table Of Contents
Release Notes for Cisco MGX 8850 Software Version 2.1.70
Contents
About Release 2.1.70
Type of Release
Locating Software Updates
Acronyms
System Requirements
Software/Firmware Compatibility Matrix
Additional Compatibility Information
Hardware Supported
Hardware Compatibility Matrix
New and Changed Information
New Features
OAM Loopback
ITU-T APS Annex B
XPVC/XPVP Termination on AXSM-E
Config Verify
Enhancements in Release 2.1.70
Additional Software Information
MIB
Service Class Template File Information
New Hardware Supported in Release 2.1.70
Hardware Overview
New and Changed Commands
New and Changed Commands
New Commands
Changed Commands
Removed Commands
Limitations and Restrictions
General Limitations, Restrictions, and Notes
Important Notes
AXSM-E Limitations
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.70
Upgrade Process Overview
Quickstart Procedures for Software Upgrades
Browsing the File System
Copying Software Files to the Switch
Upgrade Procedures for PXM45 and AXSM Cards
Upgrade Procedures for RPM-PR Cards
Troubleshooting Upgrade Problems
Documentation
Related Documentation
Cisco WAN Manager Release 10.5 Documentation
Cisco MGX 8850 Release 2.1 Documentation
SES PNNI Release 1.1 Documentation
Cisco WAN Switching Software, Release 9.3 Documentation
MGX 8850 Multiservice Switch, Release 1.1.40 Documentation
MGX 8250 Edge Concentrator, Release 1.1.40 Documentation
MGX 8230 Multiservice Gateway, Release 1.1.40 Documentation
Ordering Documentation
Documentation on the World Wide Web
Documentation CD-ROM
Documentation Feedback
Technical Assistance
Cisco.com
Technical Assistance Center
Contacting TAC by Using the Cisco TAC Website
Contacting TAC by Telephone
Caveats
Known Anomalies for Release 2.1.70
Anomalies Resolved in Release 2.1.70
Anomaly Status Changes in Release 2.1.70
Known Anomalies in Release 2.1.60
Anomalies Resolved in Release 2.1.60
Anomaly Status Changes in Release 2.1.60
Known Anomalies in Release 2.1.10
Anomalies Resolved in Release 2.1.10
Anomaly Status Changes in Release 2.1.10
Anomalies Resolved in Release 2.1.00
Known RPM-PR/MPLS Anomalies
Known Anomalies for RPM
Anomalies Resolved for RPM /MPLS
Release Notes for Cisco MGX 8850 Software Version 2.1.70
Contents
About Release 2.1.70
These release notes describe the new features, system requirements, and limitations that apply to Release 2.1.70 for the MGX 8850 IP + ATM backbone switch. These notes also contain Cisco support information.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Type of Release
Release 2.1.70 is a software release for MGX 8850 switches that use the PXM45 processor card.
Locating Software Updates
Software updates are located at Cisco Connection Online (CCO) at http://www.cisco.com/kobayashi/sw-center/wan-planner.shtml.
Acronyms
Table 1 lists acronyms used in these release notes.
Table 1 Acronyms Used in These Release Notes
Acronym
|
Description
|
ABRFS
|
ABRFS: Available Bit Rate - Foresight
|
ABRSTD
|
ABRFS: Available Bit Rate - Standard
|
AINI
|
ATM Inter-Network Interface
|
APS
|
automatic protection switching
|
AR
|
Auto Route
|
ATM
|
asynchronous transfer mode
|
AXSM
|
ATM Switch Service Module
|
B-ISUP
|
Broadband ISDN User Part
|
BPX
|
broadband packet exchange
|
BXM
|
broadband switch module
|
BXM-E
|
broadband switch module - enhanced
|
CC
|
continuity check
|
CLI
|
command line interface
|
CM
|
connection manager
|
CPE
|
customer premises equipment
|
CRC
|
cyclic redundancy check
|
CWM
|
Cisco Wide Area Network Manager
|
DSLAM
|
digital subscriber line access module
|
ENNI
|
enhanced network-to-network Interface
|
FCES
|
Flow Control External Segment
|
FRSM
|
frame relay service module
|
IETF
|
Internet Engineering Task Force
|
ILMI
|
Interim Local Management Interface
|
IOS
|
internet operating system
|
ITU-T
|
International Telecommunication Union-Telecommunication
|
LDP
|
label distribution protocol
|
LMI
|
local management interface
|
LOS
|
loss of signal
|
LSC
|
label switch controller
|
LSP
|
label switched paths
|
LSR
|
label switch router
|
MGX
|
Multiservice Gigabit Switch
|
MIB
|
management information base
|
MPG
|
multiple peer group
|
MPLS
|
multiple protocol label switching
|
NCDP
|
network clock distribution protocol
|
NNI
|
network-to-network interface
|
OAM
|
Operations, Administration, and Maintenance
|
PNNI
|
private network-to-network interface
|
PVC
|
permanent virtual circuit
|
PXM
|
processor switch module
|
RDI
|
remote defect indicator
|
RPM
|
route processor module
|
RPM-PR
|
route processor module - Premium
|
SCT
|
service class template
|
SLA
|
service level agreement
|
SM
|
service module (a card)
|
SMFIR
|
single mode fiber - intermediate range
|
SNMP
|
simple network management protocol
|
SPVC
|
soft permanent virtual connection
|
SVC
|
switched virtual circuit
|
UNI
|
User-Network Interface
|
VCI
|
virtual channel identifier
|
VNNI
|
virtual network-to-network interface
|
VPI
|
virtual path identifier
|
VsVd
|
Virtual Source, Virtual Destination
|
WFQ
|
Weighted Fair Queuing (algorithm)
|
XLMI
|
extended local management interface
|
XPVC
|
extended permanent virtual circuit
|
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.70.
Table 2 MGX and RPM 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
|
n/a
|
n/a
|
MGX 1
|
1.2.00
|
1.1.40
|
1.1.34
|
MGX 2
|
2.1.70
|
2.1.60
|
2.0.15
|
BPG/IGX
|
9.3.35
|
9.3.24
|
9.2.40
|
MGX 8220
|
5.0.17
|
4.1.11
|
n/a
|
SES
|
1.1.70
|
n/a
|
1.0.15
|
Firmware
|
latest for all
|
n/a
|
n/a
|
IOS
|
12.2(4)T1
|
12.2(4)T
|
12.2(2)T3
|
VISM
|
2.2
|
2.1.1 (1 pair)
|
1.5.6 (1 pair)
|
Table 3 lists the software that is compatible for use in a switch running Release 2.1.70 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
|
pxm45_002.001.070.202_bt.fw
|
2.1.70
|
pxm45_002.001.070.202_mgx.fw
|
2.1.70
|
2.1.70
|
PXM45/B
|
pxm45_002.001.070.202_bt.fw
|
2.1.70
|
pxm45_002.001.070.202_mgx.fw
|
2.1.70
|
2.1.70
|
AXSM-1-2488
|
axsm_002.001.070.202_bt.fw
|
2.1.70
|
axsm_002.001.070.202.fw
|
2.1.70
|
2.1.70
|
AXSM-16-155
|
AXSM-4-622
|
AXSM-16-T3/E3
|
AXSM-1-2488/B
|
axsm_002.001.070.202_bt.fw
|
2.1.70
|
axsm_002.001.070.202.fw
|
2.1.70
|
2.1.70
|
AXSM-16-155/B
|
AXSM-4-622/B
|
AXSM-16-T3/E3/B
|
AXSM-2-622-E
|
axsme_002.001.070.202_bt.fw
|
2.1.70
|
axsme_002.001.070.202.fw
|
2.1.70
|
2.1.70
|
AXSM-8-155-E
|
AXSM-16-T3E3-E
|
RPM-PR
|
rpm-boot-mz.122-4.T1
|
12.2(4)T1
|
rpm-js-mz.122-4.T1
|
12.2(4)T1
|
12.2(4)T1
|
Additional Compatibility Information
The following notes provide additional compatibility information for this release:
•
You can gracefully upgrade to Release 2.1.70 from Releases 2.0.15, 2.1.10, and 2.1.60.
•MGX 2.1.70 interoperates with SES PNNI 1.1.70 plus BPX Switch Software (SWSW) 9.3.35 plus BXM MFR.
•This release supports feeder connections from Cisco MGX 8850 Release 1.1.40. Please see the "Release Notes for MGX 8850, 8230, and 8250 Software Version 1.1.40" for feeder feature issues. Release notes can be downloaded from http://www.cisco.com/univercd/cc/td/doc/product/wanbu/index.htm.
•You must use CWM Release 10.5.10 to manage networks that contain MGX 8850 switches running Release 2.1.70.
•The RPM-PR software in this release is based on IOS Release 12.2(4)T1.
Hardware Supported
Table 4 lists the hardware supported in Release 2.1.70.
Table 4 Hardware Supported in Release 2.1.70 for MGX 8850
Product ID
|
800 Part Number
|
Minimum Revision
|
AXSM-1-2488
|
800-05795-05
|
-A0
|
AXSM-1-2488/B
|
800-07983-02
|
-A0
|
AXSM-16-155
|
800-05776-06
|
-A0
|
AXSM-16-155/B
|
800-07909-05
|
-A0
|
AXSM-16-T3/E3
|
800-05778-08
|
-A0
|
AXSM-16-T3/E3/B
|
800-07911-05
|
-A0
|
AXSM-16-T3E3-E
|
800-18519-02
|
-A0
|
AXSM-2-622-E
|
800-18521-02
|
-A0
|
AXSM-4-622
|
800-05774-09
|
-B0
|
AXSM-4-622/B
|
800-07910-05
|
-A0
|
AXSM-8-155-E
|
800-18520-02
|
-A0
|
MGX-APS-CON-8850
|
800-05307-01
|
-A0
|
MGX-MMF-FE
|
800-03202-02
|
-A0
|
MGX-RJ45-4E/B
|
800-12134-01
|
-A0
|
MGX-RJ45-FE
|
800-02735-02
|
-A0
|
MMF-4-155/C
|
800-07408-02
|
-A0
|
MMF-8-155-MT
|
800-04819-01
|
-A1
|
MMF-8-155-MT/B
|
800-07120-02
|
-A0
|
PXM45
|
800-06147-07
|
-B0
|
PXM45/B
|
800-09266-04
|
-A0
|
PXM-HD
|
800-05052-03
|
-A0
|
PXM-UI-S3
|
800-05787-02
|
-A0
|
RPM-PR-256
|
800-07178-02
|
-A0
|
RPM-PR-512
|
800-07656-02
|
-A0
|
SMB-4-155
|
800-07425-02
|
-A0
|
SMB-8-E3
|
800-04093-02
|
-A0
|
SMB-8-T3
|
800-05029-02
|
-A0
|
SMFIR-1-622/C
|
800-07410-02
|
-A0
|
SMFIR-2-622
|
800-05383-01
|
-A1
|
SMFIR-2-622/B
|
800-07412-02
|
-B0
|
SMFIR-4-155/C
|
800-07108-02
|
-A0
|
SMFIR-8-155-LC
|
800-05342-01
|
-B0
|
SMFIR-8-155-LC/B
|
800-07864-02
|
-B0
|
SMFLR-1-2488
|
800-06635-04
|
-A0
|
SMFLR-1-2488/B
|
800-08847-01
|
-A0
|
SMFLR-1-622/C
|
800-07411-02
|
-A0
|
SMFLR-2-622
|
800-05385-01
|
-A1
|
SMFLR-2-622/B
|
800-07413-02
|
-B0
|
SMFLR-4-155/C
|
800-07409-02
|
-A0
|
SMFSR-1-2488
|
800-05490-05
|
-A0
|
SMFSR-1-2488/B
|
800-07255-01
|
-A0
|
SMFXLR-1-2488
|
800-05793-05
|
-A0
|
SMFXLR-1-2488/B
|
800-08849-01
|
-A0
|
Hardware Compatibility Matrix
Table 5 shows which back cards can be used with each front card in Release 2.1.70.
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
|
SMFSR-1-2488
SMFLR-1-2488
SMFXLR-1-2488
|
Yes
|
AXSM-1-2488/B
|
SMFSR-1-2488/B
SMFLR-1-2488/B
SMFXLR-1-2488/B
|
Yes
Yes
yes
|
AXSM-2-622-E
|
SMFIR-1-622/C
SMFLR-1-622/C
|
Yes
Yes
|
AXSM-4-622
|
SMFIR-2-622
SMFLR-2-622
|
Yes
|
AXSM-4-622/B
|
SMFIR-2-622/B
SMFLR-2-622/B
|
Yes
|
AXSM-8-155-E
|
MMF-4-155/C
SMFIR-4-155/C
SMFLR-4-155/C
SMB-4-155
|
Yes
Yes
Yes
|
AXSM-16-155
|
MMF-8-155-MT
SMFIR-8-155-LC
SMFLR-8-155-LC
|
Yes
|
AXSM-16-155/B
|
SMB-4-155
MMF-8-155-MT/B
SMFIR-8-155-LC/B
SMFLR-8-155-LC/B
|
Yes
|
AXSM-16-T3E3
|
SMB-8-T3
SMB-8-E3
|
|
AXSM-16-T3E3/B
|
SMB-8-T3
SMB-8-E3
|
|
AXSM-16-T3E3-E
|
SMB-8-T3
SMB-8-E3
|
|
PXM45
|
PXM-HD
PXM-UI-S3
|
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 describes new features, hardware, and commands in Release 2.1.70.
New Features
The following features are new in release 2.1.70:
•OAM Loopback
•ITU-T APS Annex B
•XPVC/XPVP Termination on AXSM-E
•Config Verify
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
•Currently, this feature is supported through CLI only.
•Only ingress channel loopback is supported.
•Statistics gathering is suspended for a connection in loopback.
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
•Currently, this feature is supported through CLI only.
•Interoperability of this feature between the BPX and the MGX is not supported.
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, using 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.70 with AXSM-E, BPX 9.3.30, and CWM 10.5.10.
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
•No support for LMI and hence no feeder shelf can be connected to AXSM-E. The AR- PNNI-Hybrid connection is not supported for the same reason.
•No support for XLMI and ENNI and hence AXSM-E should not be connected physically to BPX, BXM, or BXM-E for the purpose of migration.
•Only AR-PNNI connectivity type is supported since AXSM-E does not support ENNI.
•All CWM 10.5 limitations regarding AXSM support of XPVC/XPVP also apply to the AXSM-E.
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.
Enhancements in Release 2.1.70
The product enhancement requests (PERs) in Table 6 are included in MGX Release 2.x. The enhancements that are new to release 2.1.70 are marked with an asterisk (*). Refer to the "MGX 8850 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.x
Enhancement Number
|
Purpose
|
2832
|
This enhancement displays Bit Error Counts on AXSM lines. The command is dspbecnt. The AXSM-E card does not support this command in 2.1.70, but will in 2.1.71. 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: conntrace, dspcon, dsppnni-link, dsppnni-neighbor.
|
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 accomodate 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 Config ured 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, eg dspcdalms <slot #>
|
3417 *
|
The Trap managers will be automatically deleted if there is no `keep alive' request from CWM for the configured intervals.
|
Additional Software Information
MIB
The SNMP MIB release for 2.1.70 is mgxmibs2160.tar.
Service Class Template File Information
The default Service Class Templates (SCTs) provided with release 2.1.70 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
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.70
New Hardware Supported in Release 2.1.70
There is no new hardware supported by this release. However, the previous 2.1.60 release introduced the following new hardware:
•AXSM-E module (T3/E3, OC3c/STM1, OC12c/STM4)
•AXSM/B OC-48 (No APS support)
Hardware Overview
The following sections describe the hardware introduced in release 2.1.60.
AXSM-E module (T3/E3, OC3c/STM1, OC12c/STM4)
The AXSM-E module (AXSM-E module (T3/E3, OC3c/STM1, OC12c/STM4) is a double-height Service Module used on the PXM45-based MGX 8850 platform. The AXSM-E supports ATM cell transfer over the following physical interfaces: T3/E3, OC-3c/STM-1, and OC-12c/STM-4. The AXSM-E hardware is implemented with a base card (mother board) and various auxiliary cards (daughter boards) that each define the physical interface (T3/E3, and so on) being used.
AXSM-E card types include:
•AXSM-16-T3E3-E, which supports SMB-8-T3 and SMB-8-E3 back cards
•AXSM-8-155-E, which supports SMB-4-155, MMF-4-155/C, SMFIR-4-155/C, and SMFLR-4-155/C back cards
•AXSM-2-622-E, which supports SMFIR-1-622/C and SMFLR-1-622/C back cards
Note The front card hardware (mother board/daughter board) for each card type can support up to two back cards. But in Release 2.1.60 or higher, only one back card (i.e., half the port capacity available in hardware) is supported by software. The full port capacity will be supported with a future software release. No hardware changes will be required.
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 or SMFLR)
New and Changed Commands
Release 2.1.70 contains the new and changed commands listed in the following sections. Crossbar commands in particular have significantly changed to enhance the feature.
Please refer to the "MGX 8850 Command Reference, Release 2.1" (part DOC7812563=) for details about CLI commands (see the "Related Documentation" section later in these notes for additional documentation that supports this release).
New and Changed Commands
Release 2.1.70 contains new commands, listed below.
Please refer to the "MGX 8850 Command Reference, Release 2.1" (part DOC7812563=) for details about CLI commands (see the "Related Documentation" section later in these notes for additional documentation that supports this release).
New Commands
These commands are new to Release 2.1.70.
•cnfxbaradmin
•dspadjlnalms
•dspdevalms (was clrxbaralm(s))
•dspdeverr
•dspdeverrhist (was dspxbarerrcnt)
•dspxbarplanealms
•dspxbarslotbwalms
Changed Commands
These commands have changed:
•dspadjlnalm
•dspalm
•dspapsbkplane
•dspapsln
•dspapslns
•dspxbar
•dspxbarswalms
•switchapsln
Removed Commands
•dspxbaralm(s) is now dspdevalms
•dspxbarerrcnt is now dspdeverrhist
•dspxbaralarm
Limitations and Restrictions
This section describes the following issues for Release 2.1.70:
•General limitations, restrictions, and notes
•AXSM limitations
•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:
•For a graceful upgrade, you must upgrade from version 2.0.15, 2.1.10, or 2.1.60.
•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.
•The maximum number of logical interfaces with PXM45 cards is 99 and PXM45/B cards is 192. Of 192 PNNI interfaces, up to 100 interfaces can be signaling ports.
•AXSM-1-2488 and 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.
•Support for a total of 19 controllers (one for PNNI and 18 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.
•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.
•If the destination address is reachable for both an IISP and a PNNI link from the same node, ABR connections will not route. The current routing algorithm will always choose IISP links over PNNI links because it is local. Since IISP does not support ABR connections, the connection setup will fail.
•In this release, a Service Class Template (SCT) can be changed with connections present. However, if the change affects services in use, the connections will be rerouted.
•When CWM is used to manage the network, the IP address 10.0.x.x cannot be used as the LAN address (lnPci) for the switch.
Important Notes
This section provides general notes that apply to this release, and covers some procedures that are not yet in the manuals.
•You must use the SCT files released with 2.1.60 or later (number 2 and 3, which were included in version 2.0.13 are similar to number 2 and 3 for 2.1.60 and later) 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 using 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 minimize use of that link.
•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. (Refer to section "Decommissioning an AXSM Slot" in the Cisco MGX 8850 Switch Software Configuration Guide, Release 2.1.
•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 signalling VC for MPLS will be established automatically on 0/32. MinVPI is not negotiated by ILMI, so the user should set this parameter to the same value on both nodes.
AXSM-E Limitations
•No support for policing when used as NNI port.
•Only Level 2 and 3 statistics are supported. Once the stats level is selected, it cannot be changed if a port has any connection set up.
•With Level 2 statistics, OAM cells are not distinguished from user cells, and up to 62,000 connections are supported per service module.
•With Level 3 statistics, OAM cells and user cells are counted separately, and up to 32K connections are supported per service module.
•External loopback (addchanloop) from AXSM-E to CPE is supported via CLI only and not via SNMP.
•When external loopback is in effect, tstdelay and tstconseg are not supported.
•Continuity Check (CC) of the PNNI segment between AXSM-E and AXSM can be executed only with the CLI. The user must make sure that the SPVC end point is configured as segment end point before executing the continuity check, and reconfigure back to non-segment after the continuity check completes..
•Anomaly CSCdt17212 is caused by a limitation of our software/firmware. Here is the explanation:
According to the Atlas document, the policing rate is defined as 50000000 / PCR.
If we have a big PCR like OC12 line rate (1412830), the policing rate, parameter is a relatively small number (50000000/1412830 = ~35.38996). Since we are doing an integer division in this operation, values would be truncated. As a result, the policing parameter cannot be calculated accurately.
Moreover, the policing rate parameter is stored in a exponent (5-bits) and mantissa (9-bits) format, so this format cannot represent a small number very accurately.
Combining the above two factors, we cannot configure an accurate policing parameter when the rate is very large.
Since we want to make sure the user would get the rate they specified, our firmware would configure policing to the next larger rate that the hardware can represent.
If we select a large rate like 1400000, the firmware would program the actual policing rate to be 1428571.
•Anomaly CSCdv42527requires further explanation: For VC queued (WFQ) connections, the maximum rate of traffic that the connection can handle is 0.2% less than the PCR of the connection.
This is a hardware limitation (same as the limitation for BPX).
RPM-PR and MPLS Limitations, Restrictions, and Notes
For Release 2.1.70, no new RPM features are introduced. Some bugs were fixed. The same RPM-PR and MPLS limitations and restrictions that applied to release 2.1.60 also apply to 2.1.70:
•InterAS, MPLS TE and POS are not supported features on RPM-PR.
•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. But sometimes the RPM-PR card gets reset when a back card is removed. As rev A0 of these release notes goes to press, we are working this issue (CSCdu39287).
•After establishing redundancy between two RPM-PR cards with the addred command, you must enter the copy run start command on the primary RPM-PR card to save the configuration change.
•If a secondary RPM-PR card is redundant to primary cards x and y, you cannot delete redundancy for only card x.
•If you need to enter the softswitch and switchcc commands, Cisco Systems recommends that you wait at least 5 seconds after issuing the softswitch command, and then enter the switchcc command.
•IOS software images on primary and secondary RPM-PR cards do not have to be compatible, but the IOS software on a secondary card should be at the same level as the primary card or higher.
•For ELSR to LSC connectivity, the default control VC used is 32. If a PNNI partition exists with VCI 32 as part of its partition range, then when MPLS partition is added, there are two options to handle the situation:
–Add MPLS controller and define its partition with available range. On ELSR, define control VC rom any VCI value within the range defined in the partition. The same VC should be defined on the LSC on xTag interface.
–Reconfigure PNNI partition to spare the control VC usage on RPM-PR, AXSM, AXSM/B, or AXSM-E.
•Whenever the RPM-PR configuration is changed and a user wants to store that configuration, the user must enter the "copy run start" command on the RPM-PR. If this is not done, the changed configuration will be lost on RPM-PR card reboot or RPM-PR switchover in case of redundancy.
•Even though RPM-PR can have 1999 sub interfaces, the usage of sub interfaces should be planned in such a way that it does not cross a safe limit of 1985. This is because each sub interface takes one IDB (interface descriptor block) and the number of IDBs available in the card is 2000. Further, a user might need some IDBs for the RPM-PR back card and its ports.
RPM-PR and MPLS Notes
This section contains additional notes on using RPM-PR cards and MPLS in this release:
•RPM-PR back card status may be incorrect (anomaly CSCdt55154).
•For RPM-PR SPVC dax connections, the slave end must be deleted before the master endpoint.
Table 7 lists RPM commands that are different in MGX Releases 1.x and 2.x.
Table 7 RPM Commands that are Different in Releases 1 and 2
Release 1.x (PXM1)
|
Release 2.x (PXM45)
|
addcon
|
switch connection
|
rpmrscprtn
|
switch partition
|
atm pvc
|
pvc
|
New Bypass Feature for RPM in 12.2(4)T IOS Release
Note Information about the bypass feature and the IOS commands used to support it was not available at the time of the printing of the RPM documents; therefore, it is included in the these release notes.
RPM cards have a maximum storage of 128 KB for the NVRAM. This size limitation creates a problem for customers with large configurations, who find it impossible to store the configurations in the NVRAM, even with compression enabled.
In order to support storage of large configuration files, a new bypass feature is now available in the 12.2(4)T IOS Release. With the bypass feature enabled, the enhanced "write memory" is used to bypass the NVRAM and save the configuration on:
•For MGX Release 2, the file auto_config_slot## located in E:/RPM.
•For MGX Release 1, the file auto_config_slot## located in C:/RPM.
Where"##" represents the zero-padded slot number in which the RPM card is seated in the MGX chassis.
To enable the bypass feature, issue the command rpmnvbypass from the IOS run time image—not in the IOS boot image.
To disable the bypass feature, issue the command no rpmnvbypass.
To verify that the bypass feature is either enabled or disabled, issue the show running-configuration command. If the bypass feature is enabled, rpmnvbypass is seen on the display. If it is not seen, the feature is not enabled.
Example 1 through Example 5 illustrate how the feature is enabled and disabled, and how to validate each of these actions from the configuration display.
Note Since the bypass feature bypasses NVRAM, it is not necessary to compress the configuration file using the command service compress-config.
Caution 1) When using the bypass feature, you can only load the run time IOS image from the PXM hard-drive or from the boot flash. 2) Do not execute the command
no boot config because doing so may prevent the bypass feature from working properly. 3) If the command
write memory is issued with the bypass feature enabled, and is consequently followed by am RPM reset, previous versions of the boot image will trigger the RPM card to go into boot mode (unable to load run-time IOS).
Example 1 Running configuration without the bypass feature enabled
rpm_slot02#show running-config
Building configuration...
Current configuration : 470 bytes
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
boot system c:rpm-js-mz.122-3.6.T1
snmp-server community public RO
snmp-server community private RW
Example 2 Enable the bypass feature (rpmnvbypass)
rpm_slot02#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
rpm_slot02(config)#rpmnvbypass
The "boot config" statement has been (re)added to your
runing configuration. Do not remove it else risk not
using the nvbypass feature
Example 3 Running configuration with bypass feature enabled (note rpmnvbypass at end of output)
rpm_slot02#show running-config
Building configuration...
Current configuration : 515 bytes
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
boot system c:rpm-js-mz.122-3.6.T1
boot config c:auto_config_slot02 <==== Line added as per output above
snmp-server community public RO
snmp-server community private RW
Example 4 Disable the bypass feature (no rpmnvbypass)
rpm_slot02#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
rpm_slot02(config)#no rpmnvbypass
Example 5 Running configuration after the bypass feature is disabled
rpm_slot02#show running-config
Building configuration...
Current configuration : 503 bytes
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
boot system c:rpm-js-mz.122-3.6.T1
boot config c:auto_config_slot02
