Home | Skip to Content | Skip to Search | Skip to Navigation | Skip to Footer |
Worldwide [change] |Register |About Cisco
Guest

Hierarchical Navigation

Cisco MGX 8800 Series Switches

Release Notes for Cisco MGX Route Processor Module (RPM-PR) Cisco IOS Release 12.4(6)T1 for MGX Releases 1.3.14 and 5.3.00

Downloads

Table Of Contents

Release Notes for Cisco MGX Route Processor Module (RPM-PR) IOS Release 12.4(6)T1 for MGX Releases 1.3.14 and 5.3.00

Contents

Overview

About This Release

New Features in MGX Release 1.3.14 and 5.3.00

Features Introduced in Cisco IOS Release 12.4(6)T1 for MGX Release 5.3.00

MGX-RJ45-5-ETH Back Card Support

Offline Diagnostics

Features Introduced in Earlier Releases

Features Introduced in MGX Release 5

MGX-RPM-1FE-CP Back Card Support

OIR Commands

Features Introduced in Cisco MGX Release 1.2.21

RPM-PR Image Directory Change From E:RPM to C:/FW

Switching from Active to Standby—switchredcd Command

MPLS over ATM

Automatic Cell Bus Clocking on MGX Release 5 Switches

Automatic Cell Bus Clocking on MGX Release 1 Switches

VISM-PR to RPM-PR Connectivity

Configuring the Cell Bus Clock Rate

Configuring CBC Clock Rate on MGX Release 1 Switches

CBC Idle Cell Configuration

MPLS LDP Feature

Multi-LVC Feature

NVRAM Bypass Feature

RPM-PR Redundancy Support

Features Not Supported in This Release

SNMP MIB

New and Modified Commands in Cisco IOS Release 12.4(6)T1

debug rpm hwdiags

debug rpm hwdiags stats

debug rpm swdiags

debug rpm swdiags stats

hw-module rpm pxm-tod-ignore

hw-module rpm fecp-fail fc-xover

hw-module rpm bkcd-fail fc-xover

Notes and Cautions

Special Upgrade Procedure for Cisco IOS Release 12.1(5.3)T_XT

UPC Connection Parameters

UPC Connection Parameters

Booting the RPM-PR

RPM-PR Bootflash Precautions

RPM-PR Bootflash Precautions

Solving the RPM-PR Bandwidth Issue When Adding a 12th VISM Card

Limitations and Restrictions

CWM Recognition of RPM-PR and MGX-RPM-128M/B Back Cards

RPM/B and RPM-PR Front Card Resets on the Back Card Removal

MGX-RPM-128M/B Ethernet Back Card Support

RPM/B and RPM-PR Limitations and Restrictions for MGX Release 1.3.14

RPM-PR Limitations and Restrictions for PXM45 and PXM1E

Open Caveats

Open Caveats in Release 12.4(6)T1 for MGX 1.3.14 and MGX 5.3.00

Open Caveats in Release 12.3(11)T9 for MGX 1.3.14 and MGX 5.2.10

Open Caveats in Release 12.3(11)T7 for MGX 1.3.12 and MGX 5.2.00

Open Caveats in Release 12.3(11)T6 for MGX 1.3.12 and MGX 5.1.20

Open Caveats in Release 12.3(11)T3 for MGX 1.3.12 and MGX 5.1.00

Open Caveats in Release 12.3(7)T3 for MGX 1.3.10 and MGX 5.0.10

Resolved Caveats

Resolved Caveats in Release 12.4(6)T1 for MGX 1.3.14 and MGX 5.3.00

Resolved Caveats in Release 12.3(11)T9 for MGX 1.3.14 and MGX 5.2.10

Resolved Caveat in Release 12.3.(11)T7 for MGX 1.3.12 and MGX 5.2.00

Resolved Caveats in Release 12.3(11)T6 for MGX 1.3.12 and MGX 5.1.20

Resolved Caveats in Release 12.3(11)T3 for MGX 1.3.12 and MGX 5.1.00

Resolved Caveats in Release 12.3(7)T3 for MGX 1.3.10 and MGX 5.0.10

Resolved Caveats in Release 12.3(2)T6 for MGX 1.3.00 and MGX 5.0.00

Resolved Caveats in Release 12.3(2)T5 for MGX 1.3.00 and MGX 5.0.00

Compatibility Notes

RPM-PR Boot File and Firmware File Names and Sizes

RPM-PR Compatibility Matrix

MGX RPM/B and RPM-PR Hardware

Previous Cisco IOS Release Compatibility Information

About Cisco IOS Release 12.2(15)T5

About Cisco IOS Release 12.2(11)T1

About Cisco IOS Release 12.2(8)T4

About Cisco IOS Release 12.2(8)T1

About Cisco IOS Release 12.2(4)T3

About Cisco IOS Release 12.2(4)T1

About Cisco IOS Release 12.2(4)T

About Cisco IOS Releases 12.2(2)T2 and 12.2(2)T3

About Cisco IOS Release 12.1(5.3)T_XT

Caveats Fixed with Cisco IOS Release 12.1(5.3)T_XT

Special Installation and Upgrade Requirements

Upgrading from an MGX-RPM-128M/B Card to an RPM-PR Card

Upgrading RPM-PR Cards

Upgrading RPM-PR Boot Software

Upgrading RPM-PR Run-Time Software

Upgrading Boot Software and Run-Time Software for Non-Redundant Cards

Upgrading RPM-PR Boot Software and Run-Time Software for 1:N Redundancy

Using XModem to Download Flash to RPM-PR Cards

Related Documentation

Obtaining Documentation

Cisco.com

Product Documentation DVD

Ordering Documentation

Documentation Feedback

Cisco Product Security Overview

Reporting Security Problems in Cisco Products

Obtaining Technical Assistance

Cisco Technical Support & Documentation Website

Submitting a Service Request

Definitions of Service Request Severity

Obtaining Additional Publications and Information


Release Notes for Cisco MGX Route Processor Module (RPM-PR) IOS Release 12.4(6)T1 for MGX Releases 1.3.14 and 5.3.00

Part Number OL-8894-01 Revision B0, September 18, 2006

Contents

Overview

These release notes contain the following sections:

•"About This Release" section

•"New Features in MGX Release 1.3.14 and 5.3.00" section

•"Features Introduced in Earlier Releases" section

•"Features Not Supported in This Release" section

•"SNMP MIB" section

•"New and Modified Commands in Cisco IOS Release 12.4(6)T1" section

•"Notes and Cautions" section

•"Limitations and Restrictions" section

•"Open Caveats" section

•"Resolved Caveats" section

•"Compatibility Notes" section

•"Previous Cisco IOS Release Compatibility Information" section

•"Special Installation and Upgrade Requirements" section

•"Related Documentation" section

•"Obtaining Documentation" section

•"Documentation Feedback" section

•"Cisco Product Security Overview" section

•"Obtaining Technical Assistance" section

•"Obtaining Additional Publications and Information" section

About This Release

These release notes describe the system requirements, new features, and limitations that apply to the Cisco MGX Route Processor Module (RPM-PR) IOS Release 12.4(6)T1 for MGX Releases 1.3.14 and 5.3.00. These notes also contain Cisco support information.

For more information about configuring the RPM-PR, see the Cisco MGX Route Processor Module (RPM-PR) Installation and Configuration Guide, Release 5.2.

New Features in MGX Release 1.3.14 and 5.3.00

This section lists new features introduced by release for the Cisco MGX Route Processor Module (RPM-PR) IOS Release 12.4(6)T1 for MGX Releases 1.3.14 and 5.3.00.

Features Introduced in Cisco IOS Release 12.4(6)T1 for MGX Release 5.3.00

Cisco IOS Release 12.4(6)T1 introduces the following new features for MGX Release 5.3.00:

•MGX-RJ45-5-ETH Back Card Support

•Offline Diagnostics

MGX-RJ45-5-ETH Back Card Support

The MGX-RJ45-5-ETH back card is a five-port back card for the RPM-PR in the Cisco MGX 8830, Cisco MGX 8830/B, Cisco MGX 8850, and Cisco MGX 8850/B. You can install this back card in the upper or lower bay and can use it along with other supported back cards, even on the same front card.

Figure 1 shows the MGX-RJ45-5-ETH faceplate.

Figure 1 MGX-RJ45-5-ETH Back Card

1

ENABLE LED

•Green—The back card is active.

•Off—The back card is not active.

3

Port 0 status LED

•Green

–Data present (flashing).

–The link is up.

2

Port 0 speed LED

•Orange—1000 Mbps.

•Green—100 Mbps.

•Off—10 Mbps

 

Table 1 lists the maximum cable length for each of the supported speeds on the MGX-RJ45-5-ETH card.

Table 1 MGX-RJ45-5-ETH Card Supported Speeds and Maximum Cable Lengths

Configuration Interface Speed
Maximum Cable Length

10 Mbs

Up to 100 meters

100 Mbs

Up to 100 meters

1000 Mbs

Up to 50 meters


Note MGX-RJ45-5-ETH LAN ports require shielded cables for EMC compliance.

MGX-RJ45-5-ETH Features

The MGX-RJ45-5-ETH back card has the following features:

•Each port can independently operate as Ethernet, Fast Ethernet, or Gigabit Ethernet

•Each port supports auto-crossover by sensing the tx and rx pins on the remote port.

•Each port can be manually configured for speed and duplex settings or for autonegotiation.

•Each interface supports sub-interfaces and 802.1Q VLANs.

•In 1:N redundancy, switchover of the front card can be triggered by failure of the back card.

•Failure of the back card causes a front card switchover.

•SNMP traps for interface created, changed, or deleted are supported.

MGX-RJ45-5-ETH Limitations

The following limitations apply to the MGX-RJ45-5-ETH back card:

•The addred command is not allowed between RPM-PR with different back cards installed. Before configuring redundancy, make sure the RPM-PR cards use the same back cards.

•The ports support copper media with RJ45 connectors only. MMF is not supported.

•The traffic rate cannot exceed 400 Mbps, which is the bandwidth limit of the PCI bus. Make sure that the traffic on Gigabit Ethernet ports does not exceed this rate.

•The total traffic through all E/FE/GIGE ports on a RPM card cannot exceed 200 Mbps bidirectional. The PCI bus imposes this limit. Make sure that traffic on Gigabit Ethernet ports does not exceed this rate.

•ISL VLAN is not supported.

•The Gigabit Ethernet mode support full duplex only.

Note Gigabit Ethernet operation is achieved through automatic negotiation only (IEEE requirement). You cannot use the speed command to set 1000 Mbps.

MGX-RJ45-5-ETH Display

The dspcd command on the PXM card identifies the MGX-RJ45-5-ETH card as 5FE_RJ45. The following example shows an RPM-PR with a 5FE_RJ45 in the upper slot and a FE_RJ45 in the lower slot: 

M8850_LA.8.PXM.a > dspcd 9

M8850_LA                         System Rev: 05.02   Mar. 08, 2006 03:38:03 GMT

MGX8850                                              Node Alarm: CRITICAL

Slot Number:   9    Redundant Slot: NONE 


                    Front Card          Upper Card          Lower Card

                    ----------          ----------          ----------


Inserted Card:      RPM_PR              5FE_RJ45            FE_RJ45            

Reserved Card:      RPM_PR              UnReserved          UnReserved         

State:              Active              Active              Active         

Serial Number:      SAK0419001H         SAD09420ACM         SBK0512013X 

Prim SW Rev:        ---                 ---                 ---

Sec SW Rev:         ---                 ---                 ---

...

Offline Diagnostics

The RPM-PR already has online hardware and software diagnostics that can test either non-redundant RPM-PR cards or active RPM-PR cards in a redundancy configuration. Release 5.3.00 extends these diagnostic features to the standby card, where they are called offline diagnostics. This improves the availability of the standby card by checking for failures before a switchover.

Offline or online diagnostics run in the following modes:

•User mode—Diagnostic tests are initiated manually.

•Scheduler mode—Diagnostic tests run periodically on a programmable schedule.

This section explains how to use both online and offline diagnostics, but Release 5.3.00 introduces offline diagnostics only. For more information about diagnostic commands, refer to New and Modified Commands in Cisco IOS Release 12.4(6)T1.

Manually Initiating Diagnostics

You can initiate diagnostic tests from the command line as individual tests, tests of a targeted type, or all tests in a test class. A specific test might be an EEPROM cpu diagnostic, a test type might be memory diagnostics, and the test class is either hwdiags or swdiags.

Online diagnostics run on active RPM-PR cards in privileged EXEC mode, and offline diagnostics run on the standby RPM-PR in user EXEC mode. Otherwise, configuration and operational procedures for online and offline diagnostics are the same.

The following table summarizes the required steps to manually initiate online or offline diagnostics:

 
Command or Action
Purpose

Step 1 

enable (active card only)

For online diagnostics, enter the privileged exec mode.

Step 2 

debug rpm [hwdiags | swdiags] diag-type [diag-test]

Offline diagnostic example: 

router> debug rpm hwdiags nvram march

Start the desire tests. Test names and pass/fail results are displayed as they execute. For more information, see debug rpm hwdiags and debug rpm swdiags.

The following example shows how to initiate all NVRAM offline diagnostics on the standby RPM-PR: 

Router> Router> debug rpm hwdiags nvram 

NVRAM Data Pins - PASSED

NVRAM Data Pins - run time = 8 milliseconds

NVRAM Marching Pattern - PASSED

NVRAM Marching Pattern - run time = 8 milliseconds

Scheduling Diagnostics

A scheduler process can periodically run diagnostics tests at intervals. You can schedule individual tests, tests of a functional type, or all tests in a class.

The following table summarizes the required steps to schedule periodic online or offline diagnostics:

 
Command or Action
Purpose

Step 1 

enable (active card only)

For online diagnostics, enter the privileged exec mode.

Step 2 

debug rpm [hwdiags | swdiags] diag-type [diag-test]
[sched | unsched]

Offline diagnostic example: 

router> debug rpm swdiags mempool alloc sched

Schedule the desired diagnostic tests. For more information, see debug rpm hwdiags and debug rpm swdiags.

The following example shows how to schedule all software diagnostics on the standby RPM-PR: 

Router> debug rpm swdiags all sched

ATMDX - SCHEDULED

Mempool Alloc IO - SCHEDULED

Mempool Alloc PCI - SCHEDULED

Mempool Alloc Processor - SCHEDULED

Mempool Free IO - SCHEDULED

Mempool Free PCI - SCHEDULED

Mempool Free Processor - SCHEDULED

Pooltype Packet Header - SCHEDULED

Pooltype Packet Private - SCHEDULED

Pooltype Packet Public - SCHEDULED

Pooltype Particle Private - SCHEDULED

Pooltype Particle Public - SCHEDULED

Corrupt Sprocess - SCHEDULED

Critical Priority Sprocess - SCHEDULED

Dead Sprocess - SCHEDULED

High Priority Sprocess - SCHEDULED

Idle Sprocess - SCHEDULED

Low Priority Sprocess - SCHEDULED

Normal Priority Sprocess - SCHEDULED

Viewing Results of Scheduled Tests

The following table summarizes the required steps to view and analyze the results of scheduled diagnostic tests:

 
Command or Action
Purpose

Step 1 

enable (active card only)

For online diagnostics, enter the privileged exec mode.

Step 2 

debug rpm [hwdiags | swdiags] stats sched

Offline diagnostic example: 

router> debug rpm swdiags stats sched

Display the results of scheduled tests. For more information, see debug rpm hwdiags stats and debug rpm swdiags stats.

The following example shows how to display the results of scheduled tests: 

Router> debug rpm swdiags stats sched

Scheduler Software Diag Max Time = 10 milliseconds

Scheduler Software Diag Errors = 6

Scheduler has run 139608 Software Diags


Scheduler Software Diags:


ENABLED   Passed              0 millisec  ATMDX

ENABLED   Passed              0 millisec  Mempool Alloc IO

DISABLED  Passed              0 millisec  Mempool Alloc PCI

ENABLED   Passed              4 millisec  Mempool Alloc Processor

ENABLED   Passed              0 millisec  Mempool Free IO

DISABLED  Passed              0 millisec  Mempool Free PCI

ENABLED   Passed              0 millisec  Mempool Free Processor

ENABLED   Passed              0 millisec  Pooltype Packet Header

ENABLED   Passed              0 millisec  Pooltype Packet Private

ENABLED   Passed              0 millisec  Pooltype Packet Public

ENABLED   Passed              0 millisec  Pooltype Particle Private

ENABLED   Passed              0 millisec  Pooltype Particle Public

ENABLED   Passed              0 millisec  Corrupt Sprocess

ENABLED   Passed              0 millisec  Critical Priority Sprocess

ENABLED   Passed              0 millisec  Dead Sprocess

ENABLED   Passed              0 millisec  High Priority Sprocess

ENABLED   Passed              0 millisec  Idle Sprocess

ENABLED   Passed              0 millisec  Low Priority Sprocess

ENABLED   Passed              0 millisec  Normal Priority Sprocess

Features Introduced in Earlier Releases

The following releases did not introduce new features:

•Cisco IOS Release 12.3(11)T9 for MGX Release 1.3.14 and MGX Release 5.2.10

•Cisco IOS Release 12.3(11)T7 for MGX Release 1.3.12 and MGX Release 5.2.00

•Cisco IOS Release 12.3(11)T6 for MGX Release 1.3.12 and MGX Release 5.1.20

•Cisco IOS Release 12.3(11)T3 for MGX Release 1.3.12 and MGX Release 5.1.00

The following sections describe features introduced in releases earlier than MGX Release 1.3.12 and MGX Release 5.1.00.

Features Introduced in MGX Release 5

This section contains the features introduced with Cisco MGX Release 5.

MGX-RPM-1FE-CP Back Card Support

The RPM-PR in a Cisco MGX 8850 switch now supports MGX-RPM-1FE-CP back cards. This feature includes the following back card functions:

•The dspcd <rpm-slot> command correctly displays the back card type.

•SNMP Traps are sent for the following events:

–Interface up/down (for Admin and Line status)

–Interface Removal

–Interface insertion

•Back card failure or OIR triggers front card switchover if redundancy is configured. This feature is enabled by default. This feature can be disabled by entering the following command: 

slot12(config)#no hw-module rpm fecp-fail fc-xover

OIR Commands

When a user inserts a back card during graceful OIR, it causes the RPM-PR to crash. To avoid this, the following new commands were added. Users can enter either set of commands (Exec mode or Conf mode).

•Exec mode commands: 

hw-module slot <slot> stop

hw-module slot <slot> start

•Conf mode commands: 

hw-module slot <slot> shutdown powered

hw-module slot <slot> shutdown unpowered

Two sequences exist for safely initiating OIR. Perform the following steps for sequence 1:

Step 1 Enter the following command: 

hw-module slot <slot> stop

Step 2 Insert or remove the RPM-PR from the Cisco MGX 8850 switch.

Step 3 Enter the following command: 

hw-module slot <slot> start

Perform the following steps for sequence 2:

Step 1 Enter the following command: 

hw-module slot <slot> shutdown powered/unpowered

Step 2 Insert or remove the RPM-PR from the Cisco MGX 8850 switch.

Step 3 Enter the following command: 

no hw-module slot <slot> shutdown powered/unpowered

Features Introduced in Cisco MGX Release 1.2.21

The RPM-PR in Cisco MGX 8800 Release 1.2.21 supports all new and existing features introduced in the Release 1.2.x baseline. The following four new features were introduced for RPM-PR implementations using Cisco IOS Release 12.2(15)T5:

1. Multiprotocol Label Switching (MPLS) CoS Transparency—This feature allows the service provider to set the MPLS experimental field instead of overwriting the value in the customer's IP precedence field. The IP header remains available for customer use; the IP packet's CoS is not changed as the packet travels through the MPLS network.

For configuration information, go to:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftdtmode.htm

2. cRTP with MQC—Modular Quality of Service (QoS) Command-Line Interface (CLI). An RPM-PR in Cisco MGX 8800 Release 1.2.21 supports using the MQC to configure the compressed Real-Time Protocol (cRTP) header. The CLI commands introduced to support this feature include:

–ip rtp header-compression—Enables RTP header compression for a particular interface.

–no ip rtp header-compression—Disables RTP header compression for a particular interface.

–clear ip rtp header-compression <interface>—Resets all statistics for the interface to 0.

–show ip rtp header-compression <interface> [detail]—Shows all statistics for an interface.

–show policy-map int sw1.x—Shows the number of packets which are compressed because of a match in policy map.

For configuration information, go to:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/fthdrcmp.htm

3. Label Switch Controller (LSC) Redundancy

For configuration information, go to:

http://www.cisco.com/univercd/cc/td/doc/product/wanbu/8850px1e/rel4/scg/rpm.htm

4. MVPN—The frame-based Multicast Virtual Private Network (MVPN) feature enables the RPM-PR in Cisco MGX 8800 Release 1.2.21 to pass frame-based multicast traffic to VPNs across the ATM core.

For configuration information, go to:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios122s/122snwft/release/122s14/fs_mvpn.htm

RPM-PR Image Directory Change From E:RPM to C:/FW

Previously, all files used by RPM-PR were stored in E:RPM. All other service modules, including PXM, store their firmware files in C:/FW. You can now use the C:/FW (or x: from RPM-PR card) directory to download the RPM-PR images. As with all other service modules, by storing all the firmware files, including the RPM-PR files in C:/FW, the router blades can more easily integrate with the shelf architecture.

Note This change is backward compatible. That is, you can still use E:RPM or (e:from the RPM-PR card) to access and configure RPM-PR images.

Due to the large number and size of RPM-PR images in the E:RPM directory, the saveallcnf command would timeout. By moving these large image files to the C:/FW directory and leaving only the configuration files in the E:RPM directory, no timeouts occurred when executing the saveallcnf command.

Switching from Active to Standby—switchredcd Command

The MGX RPM-PR uses the switchredcd command to manually change the active card to the standby card as of Cisco MGX Release 3.0 and Cisco IOS Release 12.2(8)T4), similar to other Cisco MGX service modules. The switchredcd command replaces the softswitch command that was previously used and is now obsolete.

Be sure to execute the switchredcd command before removing an active RPM-PR card from the Cisco MGX 8000 series switch shelf.

See the "Related Documentation" section and the "Upgrading RPM-PR Cards" section.

For more information on the switchredcd command, refer to the Cisco MGX 8850, MGX 8950, and MGX 8830 Command Reference (PXM45/B and PXM1E), Release 3.

MPLS over ATM

Cisco MGX 8850 and MGX 8950 Release 2.1.76 Running Cisco IOS Release 12.2(8)T has the MPLS over ATM using VC Merge feature. The virtual circuit (VC) merge facility allows a switch to aggregate multiple incoming flows with the same destination address into one outgoing flow. Wherever VC merge occurs, several incoming labels are mapped to one single outgoing label. Cells from different virtual circuit identifiers (VCIs) going to the same destination are transmitted to the same outgoing VC using multipoint-to-point connections. This sharing of labels reduces the total number of VCs required for label switching.

Without VC merge, each path consumes one label VC on each interface along the path. VC merge reduces the label space shortage by sharing labels for different flows with the same destination. Therefore, VC-Merge connections are unidirectional, and furthermore, all merged connections must be of the same service type.

Note To support VC-merge, the ATM switch requires that AXSM cards allow multiple VC frames to be merged into a single VC without interleaving cells inside AAL5 frames. The RPM-PR is the control point, where LSC resides.

VC Merge is enabled by default when the MPLS over ATM network is configured and is only used when the RPM-PR functions as an LSC. Because it is enabled by default, the only commands necessary are the following:

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 this URL:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t8/ftlsc.htm#xtocid15

Automatic Cell Bus Clocking on MGX Release 5 Switches

If you are installing a combination of RPM-PR and MPSM-155 on slots covered by the same cellbus (for example, slots 5 and 6 or 3 and 4), you must enable the Auto Clock Setting feature using the cnfndparms command.

For more information on the cnfndparms command, see the appropriate section in the Cisco MGX 8850 (PXM1E/PXM45), MGX 8950, MGX 8830, and MGX 8880 Command Reference, Release 5, at this URL:

http://www.cisco.com/univercd/cc/td/doc/product/wanbu/8850px45/rel5/cmdref/3cnf.htm#wp1681477

The CLI commands dspcbclk and cnfcbclk allow for manual setting of the cellbus clock rates, as shown in the following listing:

unknown.7.PXM.a > dspcbclk


CellBus Rate (MHz) Slots Allowable Rates (MHz)

----------------------------------------------------------

CB1 21 1, 2 21, 42

CB2 21 3, 4 21, 42

CB3 21 5, 6 21, 42

CB4 21 17 - 22 21

CB5 21 9, 10 21, 42

CB6 21 11, 12 21, 42

CB7 21 13, 14 21, 42

CB8 21 25 - 30 21


To enable automatic setting of cellbus clock rates, a node parameter must be turned on. The CLI commands dspndparms and cnfndparms manipulate the node parameters, as shown in the following listing: 


unknown.7.PXM.a > dspndparms

unknown                          System Rev: 03.00   Oct. 02, 2002 13:42:53 PST

MGX8850                                              Node Alarm: MINOR

NODE CONFIGURATION OPTIONS

Opt#  Value       Type           Description

----  -----       ----           -----------

1     3600        16bit Decimal  SHM Card Reset Sliding Window (secs)         

2     3           8bit Decimal   SHM Max Card Resets Per Window (0 = infinite)

3     Yes         Boolean        Core Redundancy Enabled                      

4     No          Boolean        Expanded Memory on PXM45B Enabled            

5     0x0         8bit Hex       Required Power Supply Module Bitmap          

6     0x0         8bit Hex       Required Fan Tray Unit Bitmap                

7     0           8bit Decimal   Trap Manager Aging timeout value(Hour(s))    

8     atm0        8bit Decimal   Primary IP interface for Netmgmt             

9     lnPci0      8bit Decimal   Secondary IP interface for Netmgmt           

10    No          Boolean        Auto Setting of Cellbus Clock Rate Enabled   

11    Yes         Boolean        Inband Node-to-Node IP Connectivity Enabled

Turning on node parameter 10 allows for automatic setting of cellbus clock rates. After it is enabled, the software immediately determines if any cellbus rates need to be changed. If, for example, two RPM-PR cards exist in one cellbus, that cellbus rate is changed to 42 MHz, as shown in the following listing: 

unknown.7.PXM.a > cnfndparm 10 yes

NODE CONFIGURATION OPTIONS

Opt#  Value       Type           Description

----  -----       ----           -----------

10    Yes         Boolean        Auto Setting of Cellbus Clock Rate Enabled

After enabled, the dspcbclk command shows that you cannot manually configure the cellbus clock rate, as displayed in the following listing: 

unknown.7.PXM.a > dspcbclk


     CellBus    Rate (MHz)    Slots     Allowable Rates (MHz)

    ----------------------------------------------------------

       CB1         21        1, 2            21, 42 (Auto Setting Enabled)

       CB2         21        3, 4            21, 42 (Auto Setting Enabled)

       CB3         21        5, 6            21, 42 (Auto Setting Enabled)

       CB4         21        17 - 22         21

       CB5         21        9, 10           21, 42 (Auto Setting Enabled)

       CB6         21        11, 12          21, 42 (Auto Setting Enabled)

       CB7         21        13, 14          21, 42 (Auto Setting Enabled)

       CB8         21        25 - 30         21

If you attempt to manually configure the cellbus clock rate while automatic cellbus rate changes are enabled, you receive an error message similar to the following: 

unknown.7.PXM.a > cnfcblclk 1 42

Err: Illegal value for option -rate

    -cb <cellBus>, where cellBus is a string CB1..CB8

    -rate <clockRate>, where clockRate is 21 or 42 (MHz)


unknown.7.PXM.a >

Automatic Cell Bus Clocking on MGX Release 1 Switches

To implement automatic cell bus clocking, an -autoClkMode option was added to the xcnfcbclk command. The default is disabled for backward compatibility. To enable this feature, enter the xcnfcbclk -autoClkMode enable command. The PXM scans the entire shelf to verify if two RPMs reside on the same cell bus, and then changes that cell bus to run at a 42 MHz clock rate. The clock rate for the remaining cell buses is not changed. The active PXM updates the disk DB and sends the update to the standby PXM.

When you enable this feature, you cannot manually configure the cell bus clock rate for any of the cell buses. When you disable this feature using the xcnfcbclk -autoClkMode disable command, the PXM does not change the clock rate for any of the cell buses, but still updates the disk DB and sends the update to the standby PXM.

Note The command to enable or disable the feature is on a per shelf basis.

Note The clock is automatically changed to 21 MHz if one of the two RPM-PRs residing on the same cell bus is removed from the shelf.

Note After disabling the automatic cell bus clocking, you can manually configure the cell bus clock.

The output from the dspcbclk command changes to reflect this new feature. A column indicates whether the feature is enabled or disabled on the cell buses. When the feature is enabled and an RPM-PR card is inserted, the PXM checks whether the card that resides next to it on the same cell bus is also an RPM-PR card. If both cards are RPM-PR cards and neither of them is in failed, reserved, unknown, self-test-fail, or no-card state, the cell bus clock rate is automatically set to 42 MHz.

Conversely, when the feature is enabled, and an RPM-PR card with a cell bus clock rate of 42 MHz is removed or fails, the PXM sets the cell bus to 21 MHz, as shown in the following example: 

mgx574.1.7.PXM.a > dspcbclk


     CellBus    Rate (MHz)     Slot     AutoClkMode

    --------------------------------------------------

       CB1         21           1, 2       disable

       CB2         21           3, 4       disable

       CB3         21           5, 6       disable

       CB4         21        17 - 22       disable

       CB5         21          9, 10       disable

       CB6         21         11, 12       disable

       CB7         21         13, 14       disable

       CB8         21        25 - 30       disable


mgx574.1.7.PXM.a > cnfcbclk 1 42


WARNING: Certain Service Modules will not operate at the clock rate you specified.

         Please check the Service Modules in the slots where the Cell Bus clock rate is 
effected by this command.


mgx574.1.7.PXM.a > cnfcbclk 5 42


WARNING: Certain Service Modules will not operate at the clock rate you specified.

         Please check the Service Modules in the slots where the Cell Bus clock rate is 

effected by this command.


mgx574.1.7.PXM.a > dspcbclk


     CellBus    Rate (MHz)     Slot     AutoClkMode

    --------------------------------------------------

       CB1         42           1, 2       disable

       CB2         21           3, 4       disable

       CB3         21           5, 6       disable

       CB4         21        17 - 22       disable

       CB5         42          9, 10       disable

       CB6         21         11, 12       disable

       CB7         21         13, 14       disable

       CB8         21        25 - 30       disable


mgx574.1.7.PXM.a > xcnfcbclk

Not enough arguments (?)

xcnfcbclk "-cb <cellBus> -rate <clockRate> -autoClkMode <autoClkEnable>"

    -cb <cellBus>, where cellBus is a string CB1..CB8

    -rate <clockRate>, where clockRate is 21 or 42 (MHz)

    -autoClkMode <autoClkEnable>, where autoClkEnable is enable or disable


mgx574.1.7.PXM.a > xcnfcbclk -autoClkMode enable


mgx574.1.7.PXM.a > dspcbclk


     CellBus    Rate (MHz)     Slot     AutoClkMode

    --------------------------------------------------

       CB1         42           1, 2       enable 

       CB2         21           3, 4       enable 

       CB3         21           5, 6       enable 

       CB4         21        17 - 22       enable 

       CB5         21          9, 10       enable 

       CB6         42         11, 12       enable 

       CB7         21         13, 14       enable 

       CB8         21        25 - 30       enable

VISM-PR to RPM-PR Connectivity

The VISM-PR card supports 144 channels when used with the G.723.1 codec, whereas earlier VISM cards supported 64 channels with the G.723.1 codec.

The following VISM Release 3.0 features require either the PXM1E or PXM45 card in your Cisco MGX 8000 Series switch chassis:

•Expanded Clock Source Selection

•Private Network-to-Network Interface (PNNI) Priority Routing

•Specifying a Connection Up or Down

•AAL1 and AAL2 Switched Virtual Circuits

As of Cisco MGX Release 3.0 and Cisco IOS Release 12.2(8)T4, setting connections between a VISM-PR card and an RPM-PR card in your Cisco MGX 8000 Series switch chassis requires that you use the new VBR (NRT) 3 connection type.

If you are using a VISM-PR card in combination with either a PXM1E or PXM45 card, you must use the VBR (NRT) 3 selection when adding a connection. Use the modified addcon or cnfcon commands to configure this connection type.

For more information, refer to the Cisco VISM Installation and Configuration Guide, Release 3.

Configuring the Cell Bus Clock Rate

As of Cisco MGX Release 1.2.10 and Cisco IOS Release 12.2(8)T4), when two RPM-PR cards are on the same cell bus occupying adjacent slots (for example, slots 1 and 2 or slots 3 and 4), set the cell bus clock (CBC) rate to 42 MHz. Correspondingly, if only one RPM-PR exists on the cell bus, set the clock to the default value of 21 MHz.

If one of the adjacent RPM-PRs goes to failed or empty state, the CBC for that cell bus must be reconfigured for traffic shaping to work correctly on the active RPM-PR. On MGX Release 3, reconfiguration of CBC rate from 42 MHz to 21 MHz is done automatically. On MGX 1 switches, you must change the CBC rate manually.

Configuring CBC Clock Rate on MGX Release 1 Switches

On Cisco MGX 1 switches with Release 1.2.10, you must use the cnfcbclk command to change the CBC from 42 MHz to 21 MHz. Use the dspcbclk command from the PXM1 to confirm the CBC rate. The following output displays the use of the cnfcbclk and dspcbclk commands used to change the clock on cell bus 1 (for slots 1 and 2) from 21 MHz to 42 MHz and confirm the change: 

PXM> dspcbclk


     CellBus    Rate (MHz)    Slot

    -------------------------------

       CB1         21        1, 2

       CB2         21        3, 4

       CB3         21        5, 6

       CB4         21        17 - 22

       CB5         21        9, 10

       CB6         21        11, 12

       CB7         21        13, 14

       CB8         21        25 - 30


PXM> cnfcbclk CB1 42

WARNING: Certain Service Modules will not operate at the clock rate you specified.

         Please check the Service Modules in the slots where the Cell Bus clock rate is 
effected by this command


mgx3.1.7.PXM.a > dspcbclk

     CellBus    Rate (MHz)    Slot

    -------------------------------

       CB1         42        1, 2

       CB2         21        3, 4

       CB3         21        5, 6

       CB4         21        17 - 22

       CB5         21        9, 10

       CB6         21        11, 12

       CB7         21        13, 14

       CB8         21        25 - 30

CBC Idle Cell Configuration

The RPM-PR makes use of idle cells for traffic shaping and scheduling. If two RPM-PRs exist in adjacent slots on the same cell bus and one of the RPM-PRs is put into a failed state by the PXM while that card is alive, then the failed RPM-PR must stop sending idle cells to avoid having an impact on traffic shaping on the adjacent functional RPM-PRs. The rpm-auto-cbclk-change command implements the RPM-PR support for this feature. This command instructs the RPM-PR to stop sending idle cells if the RPM-PR is put into a failed state by the PXM and thus prevents an impact on traffic shaping on an adjacent functional RPM-PR.

This command may be used if traffic shaping is not required.

The following output displays an example of the rpm-auto-cbclk-change command: 

RPM-11#config terminal

  Enter configuration commands, one per line. End with CNTL/Z.

  RPM-11(config)#int sw1

  RPM-11(config-if)#rpm-auto-cbclk-change

  RPM-11(config-if)#end

  RPM-11#write mem

  Building configuration...

  [OK]

  RPM-11#show run int sw1

Building configuration...


Current configuration:142 bytes

!

interface Switch1

 no ip address

 no atm ilmi-keepalive

 rpm-auto-cbclk-change

 switch autoSynch off

end

! rpm_tag_id Apr 04 2002 02:49:04

If traffic shaping is not a requirement, enter the no rpm-cbclk-change command, either manually or during card configuration. The following output displays an example of the no rpm-auto-cbclk-change command: 

RPM-11#config terminal

  Enter configuration commands, one per line. End with CNTL/Z.

  RPM-11(config)#int sw1

  RPM-11(config-if)#no rpm-auto-cbclk-change

  RPM-11(config-if)#end

  RPM-11#write mem

  Building configuration...

  [OK]

  RPM-11#show run int sw1

Building configuration...


Current configuration:145 bytes

!

interface Switch1

 no ip address

 no atm ilmi-keepalive

 no rpm-auto-cbclk-change

 switch autoSynch off

end

! rpm_tag_id Apr 04 2002 02:49:57

Note The CBC feature is enabled by default on the RPM-PR.

MPLS LDP Feature

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.

1. 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.

2. The resulting labeled paths, called label switch paths (LSPs), forward label traffic across an MPLS backbone to particular destinations.

These capabilities enable service providers to implement Cisco MPLS-based IP VPNs and IP+ATM services across multivendor MPLS networks.

From an historical and functional standpoint, LDP is a superset of the Cisco 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 embedded in their implementation details, such as the encoding of protocol messages.

Cisco IOS Release 12.2(8)T1 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 both:

•A per-interface basis for directly-connected neighbors and

•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.

MPLS LDP offers the following features:

•IETF Standards-based label distribution protocol

•Multivendor interoperability

•TDP to LDP migration and interoperability

Multi-LVC Feature

Cisco IOS Release 12.2(8)T1 enables support for initiation of multiple LSPs per destination on the RPM-PR. Different label switched paths are established for different classes of service (CoS). This feature enables interface level queueing rather than per-vc level on the RPM-PR based on MPLS CoS policy. With Multilabel switched controlled virtual circuits (Multi-LVC) support, customers can deploy IP VPN services with CoS Service Level Agreements (SLAs).

NVRAM Bypass Feature

RPM-PR cards have a maximum storage of 128 KB for the nonvolatile RAM (NVRAM). This size limitation creates a problem for customers with large configurations who find it impossible to store the complete configuration in the NVRAM, even with compression enabled.

To allow customers to store large configuration files, a bypass feature was added in Cisco IOS Release 12.2(4)T. With the bypass feature enabled, users execute the enhanced write memory command to bypass NVRAM and save the configuration in the following location:

For MGX Release 1, the file auto_config_slot## is located in the C:/RPM directory on the PXM1.

Where ## represents the zero-padded slot number in which the RPM-PR card is seated in the MGX chassis.

To enable the bypass feature, enter the rpmnvbypass command from the Cisco IOS run-time image (not in the Cisco IOS boot image).

To disable the bypass feature, enter the no rpmnvbypass command.

To verify the bypass feature is either enabled or disabled, enter the show running-configuration command. If the bypass feature is enabled, rpmnvbypass appears in the window. If it does not appear, the feature is not enabled.

Note Because the bypass feature bypasses NVRAM, it is not necessary to compress the configuration file using the service compress-config command.

Table 2 lists the cautions that are important to successfully use the bypass feature.

Table 2 Boot Cautions 

Caution
Description

When using the bypass feature, you can load the run-time Cisco IOS image from the PXM hard drive or from the bootflash.

You can load the Cisco IOS image in one of three ways:

1. From the PXM hard drive.

2. From the bootflash.

3. From the network (for example, through TFTP) from the RPM-PR back card (Ethernet or Fast Ethernet).

When the bypass feature is enabled, the boot config statement (c:auto_config_slot##) is automatically generated. The NVRAM configuration is cleared upon executing a write memory command. To load from the network, the RPM-PR must have an IP address for its back card. This information is part of the NVRAM configuration, which was just cleared by enabling the bypass feature. Hence, it is not possible to load the Cisco IOS image from the network upon a reload of the RPM-PR after you execute the rpmnvbypass and write memory commands.

Do not execute the no boot config command.

Doing so may prevent the bypass feature from working properly.

When you enable the bypass feature, the following boot config statement is automatically generated, and the NVRAM configuration is cleared: 

c:auto_config_slot##

Any writes are subsequently directed to the boot config file. This is essential, as a write memory command expects the boot config statement to be present.

If the boot config statement is not present, and you enter the write memory command, this writes the configuration into the NVRAM, which is not desirable when the objective is to save a complete configuration that is large and requires more space.

If the command write memory is issued with the bypass feature enabled, and is consequently followed by an RPM-PR card reset, previous versions of the boot image trigger the RPM-PR card to enter boot mode (unable to load run-time Cisco IOS software).

For safety purposes, the location of the system image is stored in a special area called the ROM monitor (ROMmon) area in the NVRAM. The ROMmon is always intact.

The Release 12.2(4)T boot image accesses and reads ROMmon to load the Cisco IOS image. Boot images earlier than Release 12.2(4)T do not read the ROMmon area.

Generally, Cisco IOS boot and run-time images are the same versions. However, if you change the boot image to one earlier than Release 12.2(4)T on a reload, the boot image sees that the NVRAM configuration is empty [which is normal when the bypass feature is enabled]. But because boot images earlier than Release 12.2(4)T cannot access the ROMmon area, the boot image cannot read the location of the Cisco IOS image. Because it cannot see the Cisco IOS image, it loads itself.


Example 1 through Example 5 illustrate how to enable and disable the bypass feature, and how to validate each of these actions from the configuration display.

Example 1 Running Configuration—No Bypass Feature Enabled 

rpm_slot02#show running-config

Building configuration...


Current configuration : 470 bytes

!

version 12.2

service timestamps debug uptime

service timestamps log uptime

no service password-encryption

!

hostname rpm_slot02

!

boot system c:rpm-js-mz.<new_rel>

enable password cisco

!

ip subnet-zero

!

!

!

!

interface Switch1

 no ip address

 no atm ilmi-keepalive

 switch autoSynch off

!

ip classless

no ip http server

ip pim bidir-enable

!

!

snmp-server community public RO

snmp-server community private RW

!

!

line con 0

line aux 0

line vty 0 4

 no login

!

end

Example 2 Enabling 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

running configuration. Do not remove it else risk not

using the nvbypass feature


rpm_slot02(config)#end

rpm_slot02#

Example 3 Running Configuration with Bypass Feature Enabled—rpmnvbypass at End of Output 

rpm_slot02#show running-config

Building configuration...


Current configuration: 515 bytes

!

version 12.2

service timestamps debug uptime

service timestamps log uptime

no service password-encryption

!

hostname rpm_slot02

!

boot system c:rpm-js-mz.<new_rel>

boot config c:auto_config_slot02    <==== Line added as per output above

enable password cisco

!

ip subnet-zero

!

!

!

interface Switch1

 no ip address

 no atm ilmi-keepalive

 switch autoSynch off

!

ip classless

no ip http server

ip pim bidir-enable

!

!