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-XF) Cisco IOS Release 12.4(6)T10 for PXM45-based Switches, Release 5.3.10

Downloads

Table Of Contents

Release Notes for Cisco MGX Route Processor Module (RPM-XF) Cisco IOS Release 12.4(6)T10 for PXM45-based Switches, Release 5.3.10

Contents

About this Release

New Features

Features Introduced in Cisco IOS Release 12.4(6)T10

Features Introduced in Cisco IOS Release 12.4(6)T1

Secure Shell (SSH) Console

SAR Enhancements

Control Plane Policing

Bidirectional Forwarding Detection

Offline Diagnostics

Features Introduced in Cisco IOS Release 12.3(11)T9

Features Introduced in Cisco IOS Release 12.3(11)T7

Features Introduced in Cisco IOS Release 12.3(11)T6

Features Introduced in Cisco IOS Release 12.3(11)T3

Features Introduced in Cisco IOS Release 12.3(7)T3

Features Introduced in Cisco IOS Release 12.3(2)T6

Features Introduced in Cisco IOS Release 12.3(2)T5

Features Introduced in Cisco IOS Release 12.3(2)T4

Link Fragmentation Interleaving

Increased Maximum Number of Policy Maps

Multicast VPN Feature

Compressed Real-Time Protocol

WRED Drop Counters Feature

Traffic Matrix Statistics Feature

Segmentation and Reassembly-based Traffic Management and QoS Feature

Feature Introduced in Cisco IOS Release 12.3(2)T2

Transmission Control Protocol Decompression Support

2-Port Packet Over SONET and 2-Port Gigabit Ethernet Service Module Back Cards

Dual Multiprotocol Label Switching Partition for RPM-XF

Features Introduced Earlier than Cisco IOS Release 12.3(2)T2

Cisco MGX 8950 Switch Support for RPM-XF

Border Gateway Protocol Load-Balancing Feature

IP Accounting Counter Storage Feature

Applying Multiple Actions—police Command

QoS Suboptimal Link Use Feature

RPM-XF Redundancy Support

Features Not Supported in Cisco IOS Release 12.3(11)T7

Network Management Features

SNMP MIB

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

hw-module rpm check datapath info-file

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

debug rpm diags

hw-module rpm check data-path

debug rpm check data-path

show rpm check data-path

hw-module rpm pxm-tod-ignore

hw-module pxf cef-mem-threshold

atm sar-buffers tx

RPM-XF Limitations and Restrictions

Notes and Cautions

RPM-XF auto_config File Management

Card Management

RPM-XF Bootflash Precautions

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

Open Caveats

Open Caveats in Cisco IOS Release 12.4(6)T10

Open Caveats in Cisco IOS Release 12.4(6)T1

Open Caveats in Release 12.3(11)T9

Open Caveats in Release 12.3(11)T7

Open Caveats in Release 12.3(11)T6

Open Caveats in Release 12.3(11)T3

Open Caveats in Release 12.3(7)T3

Resolved Caveats

Resolved Caveats in Cisco IOS Release 12.4(6)T10

Resolved Caveats in Cisco IOS Release 12.4(6)T1

Resolved Caveats in Release 12.3(11)T9

Resolved Caveats in Release 12.3(11)T7

Resolved Caveats in Release 12.3(11)T6

Resolved Caveats in Release 12.3(11)T3

Resolved Caveats in Release 12.3(7)T3

Resolved Caveats in Release 12.3(2)T6

Resolved Caveats in Release 12.3(2)T5

Resolved Caveats in Release 12.3(2)T4

Resolved Caveats in Release 12.3(2)T2

Compatibility Notes

RPM-XF Boot File and Firmware File Names and Sizes

RPM-XF Compatibility Matrix

MGX RPM-XF Hardware

Cisco IOS Release Compatibility Information

Using XModem to Download Flash to RPM-XF Cards

Resolved Caveats in Cisco IOS Release 12.2.x Baseline

Resolved Caveats in Release 12.2(15)T5

Resolved Caveats in Release 12.2.15T

Resolved Caveats Prior to Release 12.2.15T

Related Documentation

Obtaining Documentation, Obtaining Support, and Security Guidelines


Release Notes for Cisco MGX Route Processor Module (RPM-XF) Cisco IOS Release 12.4(6)T10 for PXM45-based Switches, Release 5.3.10

Revised: May 20, 2008, OL-8893-02

Contents

About this Release

New Features

Features Introduced in Cisco IOS Release 12.4(6)T10

Features Introduced in Cisco IOS Release 12.4(6)T1

Secure Shell (SSH) Console

SAR Enhancements

Control Plane Policing

Bidirectional Forwarding Detection

Offline Diagnostics

Features Introduced in Cisco IOS Release 12.3(11)T9

Features Introduced in Cisco IOS Release 12.3(11)T7

Features Introduced in Cisco IOS Release 12.3(11)T6

Features Introduced in Cisco IOS Release 12.3(11)T3

Features Introduced in Cisco IOS Release 12.3(7)T3

Features Introduced in Cisco IOS Release 12.3(2)T6

Features Introduced in Cisco IOS Release 12.3(2)T5

Features Introduced in Cisco IOS Release 12.3(2)T4

Link Fragmentation Interleaving

Increased Maximum Number of Policy Maps

Multicast VPN Feature

Compressed Real-Time Protocol

WRED Drop Counters Feature

Traffic Matrix Statistics Feature

Segmentation and Reassembly-based Traffic Management and QoS Feature

Features Introduced in Cisco IOS Release 12.3(2)T5

Transmission Control Protocol Decompression Support

2-Port Packet Over SONET and 2-Port Gigabit Ethernet Service Module Back Cards

Dual Multiprotocol Label Switching Partition for RPM-XF

Features Introduced Earlier than Cisco IOS Release 12.3(2)T2

Cisco MGX 8950 Switch Support for RPM-XF

Border Gateway Protocol Load-Balancing Feature

IP Accounting Counter Storage Feature

Applying Multiple Actions—police Command

QoS Suboptimal Link Use Feature

RPM-XF Redundancy Support

Features Not Supported in Cisco IOS Release 12.3(11)T7

Network Management Features

SNMP MIB

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

RPM-XF Limitations and Restrictions

Notes and Cautions

RPM-XF auto_config File Management

Card Management

RPM-XF Bootflash Precautions

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

Open Caveats

Open Caveats in Cisco IOS Release 12.4(6)T10

Open Caveats in Cisco IOS Release 12.4(6)T1

Open Caveats in Release 12.3(11)T9

Open Caveats in Release 12.3(11)T7

Open Caveats in Release 12.3(11)T6

Open Caveats in Release 12.3(11)T3

Open Caveats in Release 12.3(7)T3

Resolved Caveats

Resolved Caveats in Cisco IOS Release 12.4(6)T10

Resolved Caveats in Cisco IOS Release 12.4(6)T1

Resolved Caveats in Release 12.3(11)T9

Resolved Caveats in Release 12.3(11)T7

Resolved Caveats in Release 12.3(11)T6

Resolved Caveats in Release 12.3(11)T3

Resolved Caveats in Release 12.3(7)T3

Resolved Caveats in Release 12.3(2)T6

Resolved Caveats in Release 12.3(2)T5

Resolved Caveats in Release 12.3(2)T4

Compatibility Notes

RPM-XF Boot File and Firmware File Names and Sizes

RPM-XF Compatibility Matrix

MGX RPM-XF Hardware

Cisco IOS Release Compatibility Information

Using XModem to Download Flash to RPM-XF Cards

Resolved Caveats in Cisco IOS Release 12.2.x Baseline

Resolved Caveats in Release 12.2(15)T5

Resolved Caveats in Release 12.2.15T

Resolved Caveats Prior to Release 12.2.15T

Related Documentation

Obtaining Documentation, Obtaining Support, and Security Guidelines

About this Release

These release notes describe the system requirements, new features, and limitations of the Cisco MGX Route Processor Module (RPM-XF) Cisco IOS Release 12.4(6)T10 for PXM45-based Switches, Release 5.3.10 and VXSM Release 5.3.30. These notes also contain Cisco support information.

For more information on the RPM-XF, refer to the Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide, Release 5.2.

New Features

This section lists new features (introduced by release) for the Cisco MGX Route Processor Module (RPM-XF) Cisco IOS Release 12.4(6)T10 for PXM45-based Switches, Release 5.3.10 and VXSM Release 5.3.30 or earlier.

Features Introduced in Cisco IOS Release 12.4(6)T10

No new features were introduced in Cisco IOS Release 12.4(6)T10.

Features Introduced in Cisco IOS Release 12.4(6)T1

Features added to the RPM-XF in Cisco IOS Release 12.4(6)T1 include:

•Secure Shell (SSH) Console

•SAR Enhancements

•Control Plane Policing

•Bidirectional Forwarding Detection

•Offline Diagnostics

Secure Shell (SSH) Console

Secure Shell (SSH) is an application and a protocol that provides a secure replacement to the Berkeley r-tools. The application is similar to the Berkeley rexec and rsh tools. The protocol secures the sessions using standard cryptographic mechanisms. Two versions of SSH are available: SSH Version 1 and SSH Version 2. Cisco IOS Release 12.4(6)T1 implements SSH server and client for both versions. You must have the RPM-XF crypto image installed to use the SSH feature.

The SSH feature on the RPM-XF is useful if you want to manage the card through its management or high-speed back card. More often however, you manage the RPM-XF, and all other cards in the MGX chassis, from the PXM45 controller. The PXM45 controller also implements SSH and provides the same level of security.

If you plan to use SSH on the RPM-XF, consider disabling telnet access to improve security. Telnet transfers all user ID, password, and session management information between the client and the RPM-XF using clear text. Clear, or unencrypted text can be read by network analysis and snooping tools.

Note The RPM-XF must have the crypto image installed to use the SSH feature.

For software image information, refer to Compatibility Notes

SSH Configuration Guidelines

To use SSH the first time, you must activate the SSH server. You can then enable or disable SSH, or other management protocols, on the asynchronous (vty) ports. You enable the SSH server and configure SSH ports on the RPM-XF as you would other Cisco routers running Cisco IOS Release 12.4(6)T1.

The RPM-XF stores crypto keys in a secure way on the PXM hard disk. This is necessary to support 1:N redundancy for RPM-XF cards. The PXM card stores the crypto key for each RPM-XF in the following directory and file:

E:/RPM/private_config_slotnn

where nn is the two digit logical slot number

Note Do not remove or modify the crypto key file; doing so disables SSH on the RPM-XF.

For more information about configuring SSH, refer to:

•Cisco IOS Security Configuration Guide, Release 12.4

Management Port Configuration Guidelines

All management sessions to the RPM-XF, including those initiated with the cc command at the PXM card, utilize the asynchronous (vty) ports. In Release 5.3.00 the RPM-XF supports up to 250 vty ports (CSCsd05487).

Note Earlier releases supported up to 1000 vty ports.

You allocate vty ports among the management protocols you plan to use:

•ssh

•rlogin

•telnet

•rpm ipc

•all

•none

You assign protocols to vty ports using the transport command (See SSH Commands). Always configure a few vty lines for rpm ipc, so you can manage the RPM-XF from the PXM card. Then, configure other vty lines for the protocols you plan to permit on backcard interfaces.

Note You must enable at least one line for rpm ipc to manage the RPM-XF from the PXM.

The following example configures three ports for rpm ipc and two for ssh: 

line vty 0 2

 password cisco

 login

 transport input rpm ipc

 transport output rpm ipc

line vty 3 4

 password cisco

 login local

 transport input ssh

 transport output ssh

In this example, the login local command specifies that ssh should use a local database of users. In a production environment, you would usually use an authentication server instead.

SSH Commands

The SSH feature in Cisco IOS Release 12.4(6)T1 adds the following global configuration commands to the RPM-XF:

•crypto key generate rsa (only RSA keys are supported)

•ip ssh

The SSH feature also adds the following user exec commands:

•show crypto

•show ip ssh

•show ssh

The SSH feature extends the following line configuration command:

•transport {input | output} {rpm ipc | all | none | rlogin | ssh | telnet}

The RPM-XF extends the standard transport command to include the rpm ipc option, which supports internal management sessions with the PXM card.

For command reference information, refer to the following:.

•Cisco IOS Master Commands List, Release 12.4

SAR Enhancements

This section describes the segmentation and reassembly (SAR) performance enhancements for the RPM-XF.

SAR Buffer Pool Allocation

Release 5.3.00 introduces the atm sar-buffers tx configuration command under interface Switch1. Releases earlier than 5.3.00 statically allocate SAR buffers to the UBR, VBR and LVC classes in the ratio of 1:2:1. Static allocation leads to under-utilization of buffers in some cases. When the traffic on an RPM-XF is predominantly VBR, this under-utilization can lead to reduced tolerance for bursty traffic. You use the atm sar-buffers tx command to reallocate the total SAR buffers between UBR, VBR and the LVC classes based on expected usage for these traffic classes (See atm sar-buffers tx).

To display the buffer pool allocation and usage counters, enter the show controllers Switch1 command. This command displays the in-use /allocated buffers for each of the three classes. 

RPM-XF_SF#show controllers switch 1 sar

Interface Switch1 is up

...

Data Path SAR buffer usage statistics:

Data Res SAR Class 1 current buffer usage: 0x00000002 / 0x00054000

Data Res SAR Total current buffer usage : 0x00000002 / 0x00054000

Data Res SAR Total buffer usage ratio : 000%

Data Seg SAR Class 1 current buffer usage: 0x00000003 / 0x00015000

Data Seg SAR Class 2 current buffer usage: 0x00000001 / 0x0002A000

Data Seg SAR Class 3 current buffer usage: 0x00000000 / 0x00015000

Data Seg SAR Total current buffer usage : 0x00000004 / 0x00054000

Data Seg SAR Total buffer usage ratio : 000%

...

RPM-XF_SF#

SAR Cumulative Queue Size Counters

The SAR cumulative queue size counters display the sum of all queue size configurations of the VCs belonging to a traffic class. These counters, in conjunction with the buffer pool usage counters, provide information about over-subscription, if any.

To display the cumulative queue size configuration for each class and detect potential oversubscription of buffer classes, enter the show controllers switch 1 command. (CSCei21134) 

RPM-XF_SF#show controllers switch 1 sar

Interface Switch1 is up

...

Data Seg SAR cumulative queue size per buffer class:

Data Seg SAR Class 1 cumulative queue size  : 0x000003C0

Data Seg SAR Class 2 cumulative queue size  : 0x00007C80

Data Seg SAR Class 3 cumulative queue size  : 0x00000000


Data Seg SAR Total cumulative queue size    : 0x00008040


...

RPM-XF_SF#

SAR CoS Queue and Weight Allocation

This release improves the CoS weight calculation to overcome the deficit counter wrap issue. The weight of a cosq controls the average number of cells a cosq services at each turn. The deficit counter keeps track of the actual number of cells serviced at each turn. If a wrap-around of the deficit counter occurs, it can cause inconsistencies in bandwidth distribution between classes of a service policy. Release 5.3.00 resolves this problem.

SAR 1.4 Upgrade

This release integrates the new GA version of SAR ucode from Mindspeed, which has backward support for version 1.3. This new version has critical bug fixes.

Control Plane Policing

Control Plane Policing (CoPP) increases router security by protecting the route processor from unnecessary and potentially malicious traffic. The route processor handles important and time critical packets, such as layer 2 and layer 3 keep alive messages, routing protocol updates, control protocol, network management, and other process level tasks related to control plane operation. Without CoPP, the control and management planes can be vulnerable to high rates of undesirable traffic that can interfere with routing stability, reachability, and packet delivery.

Note The RPM-XF does not support control plane protection options host, cef-exception, or transit.

CoPP Configuration Guidelines

You enable and configure CoPP as you would on other Cisco routers running Cisco IOS Software Release 12.4T. The following table summarizes the required steps:

 
Command or Action
Purpose

Step 1 

class-map

Example: 

router(config)#class-map match-all TEST-CLASS

router(config-cmap)#match access-group 101

Define the packet classification criteria.

Step 2 

policy-map

Example: 

router(config-pmap)#policy-map TEST-POLICY

router(config-pmap)#class TEST-CLASS 

router(config-pmap-c)#police rate 12 pps

Define the service policy.

Step 3 

control-plane

Example: 

router(config)#control-plane

Access the control plane.

Note The RPM-XF does not support control plane protection options host, cef-exception, or transit.

Step 4 

service-policy

Example: 

router(config-cp)# service-policy input 
TEST-POLICY

Apply the service policy.

For more information about control plane policing, refer to the following guides:

•Control Plane Policing [Cisco IOS Software Release 12.4]

•Control Plane Protection [Cisco IOS Software Release 12.4 T]

•Cisco IOS Master Commands List, Release 12.4

Bidirectional Forwarding Detection

Bidirectional Forwarding Detection (BFD) 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 OSPF hello messages can take a second or more to detect the loss. This is too long for some applications and can result in excessive data loss, especially at gigabit rates. BFD quickly detects a media failure so that the OSPF protocol can quickly update routes.

BFD Restrictions

The BFD implementation on the RPM-XF has the following limitations:

•OSPF protocol only

•GIGE interfaces only

BFD Configuration Guidelines

You enable and configure BFD as you would on other Cisco routers running Cisco IOS Software Release 12.4T. BFD is a supporting protocol for OSPF in the RPM-XF, so OSPF must be up and running before BFD can start. The following table summarizes the required steps:

 
Command or Action
Purpose

Step 1 

sh ip ospf neighbors

Example: 

router# show ip ospf neighbors

Verify that OSPF neighbors are present and operational.

Step 2 

bfd interval msec min_rx msec multiplier number

Example: 

router(config)# interface GigabitEthernet 1/0

router(config-if)# bfd interval 150 min_rx 150 
multiplier 4

Configure BFD parameters on interfaces, specifying the interval between sending BFD packets, the interval between receiving BFD packets, and the number of missing BFD packets permitted before declaring a failure.1

Step 3 

ip ospf bfd

Example: 

router(config-if)# ip ospf bfd

Enable BFD on interfaces.

 

bfd all-interfaces

Example: 

router(config)# router ospf 123

router(config-router)# bfd all-interfaces

Alternatively, enable BFD globally on all interfaces.

Step 4 

show bfd neighbors

Example 

router# show bfd neighbors

Verify that BFD neighbors are present and that the state is up.

1 For configuration restrictions, see CSCsc10658.

BFD Commands

The BFD feature uses the following Cisco IOS commands:

•bfd all-interfaces

•bfd interval

•ip ospf bfd

•show bfd

For command reference information, refer to the following document:

•Cisco IOS Master Commands List, Release 12.4

Offline Diagnostics

The RPM-XF already has online hardware and software diagnostics that can test either non-redundant RPM-XF cards or active RPM-XF 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.

Similarly, the RPM-XF already has a data-path check that verifies the sanity of the data-path for either non-redundant RPM-XF cards or active RPM-XF cards a redundancy configuration. Release 5.3.00 extends the data-path check to the standby card to test the sanity of its data-path components. This assures that the data path of the standby card is operational and ready to forward traffic if an active card fails.

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.

Note Only scheduled diagnostics raise alarms and log events.

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 the fast Ethernet backcard 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 mempool free

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 mempool offline diagnostics on the standby RPM-XF: 

Router> debug rpm swdiags mempool free

Mempool Free IO - PASSED

Mempool Free IO - run time = 0 milliseconds

Mempool Free PCI - PASSED

Mempool Free PCI - run time = 0 milliseconds

Mempool Free Processor - PASSED

Mempool Free Processor - run time = 0 milliseconds

Scheduling Diagnostics

A scheduler process can periodically run diagnostics tests at a configurable interval. 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 hwdiags cache delay sched

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

Step 3 

debug rpm diags display

Offline diagnostic example: 

router> debug rpm diags display

Verify that the scheduler is running. If it is not, start the scheduler. For more information, see debug rpm diags.

The following example shows how to schedule all software diagnostics: 

Router> debug rpm swdiags all sched

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

Starting and Configuring the Scheduler

To perform scheduled diagnostics you must enable the scheduler. Optionally, you can configure the test interval or level of detail for logging (tracelevel). The verbose tracelevel setting is for debugging only.

The following table summarizes the required steps to start and configure the diagnostic scheduler:

 
Command or Action
Purpose

Step 1 

enable (active card only)

For online diagnostics, enter the privileged exec mode.

Step 2 

debug rpm diags cnf enable

Offline diagnostic example: 

router> debug rpm diags cnf enable

Start the scheduler. For more information, see debug rpm diags.

Step 3 

debug rpm diags cnf {period | tracelevel}

Offline diagnostic example: 

router> debug rpm diags cnf period 60

Optionally, configure the scheduler period.

Note The tracelevel option is for troubleshooting only.

For more information, see debug rpm diags.

Step 4 

debug rpm diags display

Offline diagnostic example: 

router> debug rpm diags display

Verify that the scheduler is running. If it is not, start the scheduler. For more information, see debug rpm diags.

The following example shows how to enable the diagnostic scheduler: 

Router> debug rpm diags display

Configuration:

    Test: Enabled. Test Interval: 30(secs)

Status:

    Process name:        RPMXF DIAG

    Diag State:          RUN

    Process Error:       No Error

    Last Event Received: ONLN_ENABLE

    Last Event Trigger:  ONLN_ENABLE


Statistics:

    Software Diag runs: 27, failures: 0

    Hardware Diag runs: 49, failures: 0

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.

Step 3 

show log

show facility-alarm status

or from the PXM:

dspcdalms <slot#>

dsplog

For tests that fail, determine the reason.

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

Router> debug rpm swdiags stats sched

Scheduler Software Diag Max Allowed Run Time = 20 milliseconds

Scheduler Software Diag Errors = 0

Scheduler has run 32 Software Diags


Scheduler Software Diags:


ENABLED   Passed            ERR_INJ_OFF    8 millisec  Mempool Alloc IO

ENABLED   Passed            ERR_INJ_OFF    0 millisec  Mempool Alloc PCI

ENABLED   Passed            ERR_INJ_OFF    8 millisec  Mempool Alloc Processor

ENABLED   Passed            ERR_INJ_OFF    0 millisec  Mempool Free IO

ENABLED   Passed            ERR_INJ_OFF    0 millisec  Mempool Free PCI

ENABLED   Passed            ERR_INJ_OFF    0 millisec  Mempool Free Processor

ENABLED   Passed            ERR_INJ_OFF    0 millisec  Pooltype Packet Header

ENABLED   Passed            ERR_INJ_OFF    0 millisec  Pooltype Packet Private

ENABLED   Passed            ERR_INJ_OFF    0 millisec  Pooltype Packet Public

ENABLED   Passed            ERR_INJ_OFF    0 millisec  Pooltype Particle Private

ENABLED   Passed            ERR_INJ_OFF    0 millisec  Pooltype Particle Public

ENABLED   Passed            ERR_INJ_OFF    0 millisec  Corrupt Sprocess

ENABLED   Passed            ERR_INJ_OFF    0 millisec  Critical Priority Sprocess

ENABLED   Passed            ERR_INJ_OFF    0 millisec  Dead Sprocess

ENABLED   Passed            ERR_INJ_OFF    0 millisec  High Priority Sprocess

ENABLED   Passed            ERR_INJ_OFF    0 millisec  Idle Sprocess

ENABLED   Passed            ERR_INJ_OFF    0 millisec  Low Priority Sprocess

ENABLED   Passed            ERR_INJ_OFF    0 millisec  Normal Priority Sprocess

Starting and Configuring the Data-Path Check

The data-path check tests the communication link between the active or standby RPM-XF cards and the PXM by periodically transmitting packets and verifying that they are received back correctly. After the maximum retry count when the data-path check is not receiving any packets, the RPM-XF raises an alarm.

You can enable this feature on active and standby RPM-XF cards, but the recovery option (reboot) is not available for the standby card. After a redundancy switchover, the data path check on the standby card is disabled and all the statistics (packets tx/rx) are cleared as the card becomes active.

The following table summarizes the required steps to start and configure the data-path check on the standby card:

 
Command or Action
Purpose

Step 1 

cc slot or ssh

Establish a management session with the standby RPM-XF.

Step 2 

debug rpm check data-path

Start the data-path check. For more information, see debug rpm check data-path.

Step 3 

debug rpm check data-path {interval | retry}

Configure the data-path check. For more information, see debug rpm check data-path.

The following table summarizes the required steps to start the data-path check on the active card:

 
Command or Action
Purpose

Step 1 

enable

Enter the privileged exec mode.

Step 1 

configure terminal

Enter the global configuration mode.

Step 2 

hw-module rpm check data-path

Start the data-path check. For more information, see hw-module rpm check data-path.

Viewing the Data-Path Check Results

The following table summarizes the required steps to view and analyze the results of the data-path check:

 
Command or Action
Purpose

Step 1 

cc slot or ssh

Establish a management session with the RPM-XF.

Step 2 

show rpm check data-path

Display the data-path check results. For more information, see show rpm check data-path.

Step 3 

show log

show facility-alarm status

or from the PXM:

dspcdalms <slot#>

dsplog

For failures, determine the reason.

The following example shows how to display the results of the data-path diagnostic: 

Router> show rpm check data-path

Data Path Check Health Status:          Good

Data Path Check Feature enabled:        Yes

Data Path Check Recovery enabled:       No

Data Path Check Interval(in sec):       6

Data Path Check Retry Count:            5

Data Path Check Packets Sent:           928

Data Path Check Packets Rcvd:           928

Data Path Check Packets Good:           928

DPC Packets received with Bad header:   0

DPC Packets received with Bad pattern:  0

Data Path Check Outstanding Packets:    1

Data Path Check Time since Last Send:   1

Data Path Check Failures Reported:      0

Data Path Check Recovery Skips Done:    0

Data Path Check Packet Not Sent Reason: None

Data Path Check Packet Sent Wait Time:  0

Features Introduced in Cisco IOS Release 12.3(11)T9

No new features were introduced in Cisco IOS Release 12.3(11)T9.

Features Introduced in Cisco IOS Release 12.3(11)T7

No new features were introduced in Cisco IOS Release 12.3(11)T7.

Features Introduced in Cisco IOS Release 12.3(11)T6

No new features were introduced in Cisco IOS Release 12.3(11)T6.

Features Introduced in Cisco IOS Release 12.3(11)T3

Features added to the RPM-XF in Cisco IOS Release 12.3(11)T3 include:

•Copper small-form factor pluggable (SFP)

•RPM-XF software—Queueing elements, statistics, FTP elements, compressed Real-Time Protocol (cRTP) elements, MIBs

•Dynamic bandwidth

For more information, refer to the Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide, Release 5.

Features Introduced in Cisco IOS Release 12.3(7)T3

Features introduced in Cisco IOS Release 12.3(7)T3 include:

•MGX-XF-UI/B notched back card—A redesign of the user interface back card for the RPM-XF. The notch was added to allow clearance for installation of the RCON APS connector on the Cisco MGX 8850B and MGX 8880 chassis.

•Preferred routes on RPM-XF—Cisco IOS software Release 12.3(7)T3 contains enhanced support for preferred routes on the RPM-XF. Currently the AXSM and other service modules provide the facility to associate an already-defined preferred route on the PXM to an soft permanent virtual connection (SPVC) mastered on that service module. The commands described below are updated to support Preferred Route association through a command-line interface (CLI) or Simple Network Management Protocol (SNMP) for SPVC, Hybrid, and extended permanent virtual connection (XPVC) configured with an RPM-XF as the master end.

Syntax Description

Router(config-if-swconn)#[no] prefrte <Route ID>

Route ID—An identifier for the configured preferred route that is associated with this connection. Preferred routes are maintained in a separate database on the PXM and referenced by the ID. The range is 0 through 65535. Setting the ID to 0 means no preferred route is configured. The default value for preferred route ID is zero (no preferred route attached).

Router(config-if-swconn)#[no] directrte

Setting the Directed Route flag to Yes sets the connection to be routed only on the specified preferred route. The default value for a directed route is No.

Router(config-if-swconn)# prefrte ?

<1 - 65535> Preferred Route ID value

Router(config-if-swconn)# directrte ?

<cr>

Note If you use the directrte command to specify a directed route for a connection with its preferred route ID set to zero, an error message appears. Both the prefrte and directrte commands must be run on the master end of the connection. If you try to use these commands on the slave end of the connection, an error message appears.

Examples

To configure a preferred route ID value of 10 for the connection: 

Router(config-if-swconn)# prefrte 10

To configure a preferred route ID value of 5 and set the connection on directed route: 

Router(config-if-swconn)# prefrte 5

Router(config-if-swconn)# directrte

To change the directed route flag for the connection to No: 

Router(config-if-swconn)# no directrte

To set the preferred route id to zero and set the directed route to No: 

Router(config-if-swconn)# no prefrte

Features Introduced in Cisco IOS Release 12.3(2)T6

The following new features were introduced in Cisco IOS Release 12.3(2)T6:

•Enhanced Interior Gateway Routing Protocol (eiGRP) between customer edge (CE) to provider edge (PE).

•Basic Point-to-Point Protocol (PPP) over ATM feature evaluation on various port speeds from 768 Kbps up to DS3 with a maximum of T1 bandwidth per flow.

•PPP over ATM with cRTP on various port speeds from 768 Kbps up to DS3 with a maximum of T1 bandwidth per flow.

•PPP over ATM with cRTP and QoS enabled on the links.

•Scaling up to 200 cRTP enabled pppoATM links with QoS.

Features Introduced in Cisco IOS Release 12.3(2)T5

No new features were introduced in Cisco IOS Release 12.3(2)T5.

Features Introduced in Cisco IOS Release 12.3(2)T4

This section contains the descriptions of the features that were introduced in 12.3(2)T4.

Link Fragmentation Interleaving

Cisco IOS Release 12.3(2)T4 adds support for Link Fragmentation Interleaving (LFI). For more information on the CLI commands introduced or modified to support this feature on the RPM-XF, refer to the Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide, Release 4.

For Cisco IOS software configuration informationabout LFI, go to:

•Link Fragmentation and Interleaving for Frame Relay and ATM Virtual Circuits
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121t/121t5/dtlfifra.htm

Increased Maximum Number of Policy Maps

Policy maps, class maps, and service policy maps define traffic policies, and attach them to interfaces. In earlier releases, you could create 256 separate policy maps and up to 256 class maps per policy map. In Cisco IOS Release 12.3(2)T4, the maximum number of policy maps is increased to 2048. Each policy map supports up to 32 class maps per policy map. For more information on the CLI commands that have been introduced or modified to support this feature on the RPM-XF, refer to the Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide, Release 4.

Multicast VPN Feature

The frame-based Multicast VPN (MVPN) feature enables the RPM-XF to pass frame-based multicast traffic to VPNs across the ATM core.

For multicast configuration information, go to:

•Multicast VPN—IP Multicast Support for MPLS VPNs

Compressed Real-Time Protocol

The Cisco IOS Release 12.3(2)T4 of the RPM-XF adds the ability to configure the 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

WRED Drop Counters Feature

The WRED Drop Counters feature adds class-based packet counters to existing RPM-XF functionality. The counters can be Differentiated Services Code Point (DSCP) based or precedence based. For more information on the CLI commands introduced or modified to support the weighted random early detection (WRED) Drop Counters feature on the RPM-XF, refer to the Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide, Release 4.

Traffic Matrix Statistics Feature

The Traffic Matrix Statistics (TMS) feature allows an administrator to gather the number of packets and bytes that travel across the backbone from internal and external sources. These packets and bytes are called traffic matrix statistics. Use the statistics collected to determine how much traffic the backbone handles. The statistics are always collected on the incoming interface. For more information on CLI commands introduced or modified to support TMS on the RPM-XF, refer to the Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide, Release 4.

Segmentation and Reassembly-based Traffic Management and QoS Feature

Traffic management, weighted random early detection WRED, and cell-based weighted fair queuing algorithm processing is accomplished using the Segmentation and Reassembly (SAR) engine.

Feature Introduced in Cisco IOS Release 12.3(2)T2

This section contains the descriptions of the features that were introduced in 12.3(2)T2.

Transmission Control Protocol Decompression Support

Cisco IOS Release 12.3(2)T2 adds support for Transmission Control Protocol (TCP) decompression as an adjunct to supporting the cRTP header feature on the RPM-XF.

2-Port Packet Over SONET and 2-Port Gigabit Ethernet Service Module Back Cards

Cisco IOS Release 12.3(2)T2 adds support for two service module back cards that provide either two Gigabit Ethernet or two Packet over SONET (POS) ports. For more information on the fit and function of the back cards and CLI commands which support the back cards on the RPM-XF, refer to the Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide, Release 4.

Dual Multiprotocol Label Switching Partition for RPM-XF

Cisco IOS Release 12.3(2)T2 adds support for dual Multiprotocol Label Switching (MPLS) partitions on the RPM-XF. This is related to label switch controller (LSC) redundancy.

For configuration information, go to:

•Preparing RPM Cards for Operation

Features Introduced Earlier than Cisco IOS Release 12.3(2)T2

This section contains the descriptions of the features that were introduced in releases prior to 12.3(2)T2.

Cisco MGX 8950 Switch Support for RPM-XF

In Cisco MGX Release 3.0.10 and later, the Cisco MGX 8950 switch supports the MGX RPM-XF card set. The MGX RPM-XF card set can occupy any of the available service module slots in the Cisco MGX 8950 switch, which are slots 1 through 6 and slots 11 through 16.

Border Gateway Protocol Load-Balancing Feature

To load-balance by external Border Gateway Protocol (eBGP) and internal Border Gateway Protocol (iBGP) on multiple paths to a destination, traffic is directed on multiple available paths between autonomous systems (AS) by gateway routers.

The following CLI commands are used to implement this feature.

Command
Description

maximum-path <nums>

Configure maximum number of eiBGP parallel routes.

For example: 

bgpbox-zenith-CE1(config)#router bgp 4

bgpbox-zenith-CE1(config-rout)#maximum-paths 3

bgpbox-zenith-CE1(config-rout)#end

show ip bgp

•This command is enhanced to show the multipaths.

•Each multipath is marked as multipath.

•The bestpath is marked as multipath and bestpath.

•The output describes the type of multipath that is enabled.

For example: 

bgpbox-zenith-CE1#sh ip bgp 141.22.0.0

BGP routing table entry for 141.22.0.0/16, version 18

Paths: (2 available, best #1)

Multipath: eBGP

Advertised to non peer-group peers:

7.0.76.9

100 5

7.0.76.2 from 7.0.76.2 (100.0.0.2)

Origin IGP, localpref 100, valid, external, multipath, 
best

100 5

7.0.76.9 from 7.0.76.9 (100.0.0.9)

Origin IGP, localpref 100, valid, external, multipath

Limitations of eiBGP Load-Balancing

The limitations of eiBGP are as follows:

•If multiple alternate paths for a peering point exist, only one of the paths is used for a given prefix.

•Only per-flow load-balancing is supported. Per-packet load-balancing is not supported.

•eiBGP load-balancing is supported only in MPLS and VPN networks.

•Load-balancing proportional to link bandwidth (see dmz-linkbw command) is not supported. The load-balancing is performed on the available links with equal costs.

•The maximum number of paths that can be used for load-balancing is 6. This is the current Cisco IOS software limitation.

•Load-balancing does not work if RDs are the same as RRs. If RRs are used, RDs must be different.

•Having CEs in different VPNs using the same RDs does not work.

IP Accounting Counter Storage Feature

The Cisco MGX RPM-XF only stores packet/byte counters based on precedence and DSCP values on a per-interface level at input.

The following CLIs are added or enhanced for this release to implement this feature:

Command
Description

ip accounting ? 

pop20-slot6(config-if)#ip accounting ?

precedence         Count packets by IP precedence on 
this interface

dscp               Count packets by DSCP on this 
interface

ip accounting precedence ? 

pop20-slot6(config-if)#ip accounting precedence ?

input   received packets and bytes

ip accounting dscp ? 

pop20-slot6(config-if)#ip accounting dscp ?

input   received packets and bytes

show int [interface] precedence 

pop20-slot5# show int [interface] precedence

show int [interface] dscp 

pop20-slot5# show int [interface] dscp

clear counters 

pop20-slot5# clear counters

Limitations

The limitations are as follows:

•Counters are maintained only at the input per interface.

•There is no count of dropped or transmitted packets based on DSCP/PREC packets per interface.

Applying Multiple Actions—police Command

The MGX RPM-XF police command is similar to the Cisco IOS RPM command. Therefore, you can apply multiple exceed and conform actions on the police command.

The police CLI command is enhanced. Before this release, the police command had no menus and all parameters were listed on one line, as shown in the following example: 

domino80p01-z001#sh policy test1z

.............

police 128000 8000 8000 conform-action transmit exceed-action drop

This allowed only one value for the conform-action and exceed-action fields.

The new police command functions as shown in the following example: 

ipfrtx90r14-01(config-pmap-c)#police 128000 8000 8000

ipfrtx9(config-pmap-c-police)#conform-action transmit

ipfrtx9(config-pmap-c-police)#exceed-action set-dscp 28

ipfrtx9(config-pmap-c-police)#exceed-action set-mpls 2

Note that you can configure multiple conform-action and exceed-action parameters.

QoS Suboptimal Link Use Feature

RPM-XF uses Versatile Traffic Management System (VTMS) as a scheduling algorithm. VTMS schedules queues based on the current link use in real time. The previous version of the VTMS algorithm was efficient and mapped well in an ASIC or network processor; however, it did not fully use the link.

Cisco IOS Release 12.3(2)T2 adds support through the CLI to allow you to specify the oversubscription factor on a queue. The factor is in the range of 1 through 31 and can be denoted as 2n. An oversubscription factor of n = 2 on any queue means to subscribe that queue by a factor of 4 (2n where n is 2; so 2 raised to power 2 = 4).

The syntax for the bandwidth and priority commands is: 

[no] bandwidth {<kbps> | percent <percentage> | remaining percent <percentage>} 
[maximize-utilization [<max-shift>]] 

[no] priority {<kbps> | percent <percentage>} [maximize-utilization

RPM-XF Redundancy Support

RPM-XF 1:N redundancy is used to switch configuration and traffic from one RPM-XF module to another RPM-XF module. Route processing continues with minimal traffic loss even if an RPM-XF fails and there is no operator or direct access to swap the failed card or fix the problem. Redundancy that ensures Layer 2 state restoration is supported. Layer 3 state is restored through convergence.

Note When you reset a chassis with RPM-XFs configured for 1:N redundancy, we recommend that you bring up the primary slots in active state.

Benefits of 1:N redundancy include the following:

•An RPM-XF card with hardware problems can be fixed while the redundant standby card takes over its functionality.

•Software upgrades are easier and can be performed with less downtime.

•LAN interface redundancy supported with MAC addresses of primary RPM-XF copied to standby RPM-XF.

•1:N redundancy support for Gigabit Ethernet interface back cards during front card switchover.

•Y cable redundancy support for POS back cards during front card switchover. With Y cable, 1:N redundancy is restricted to N = 1.

The following are general guidelines for redundancy on the RPM-XF:

•The Addred command is not allowed between RPM-PR and RPM-XF.

•To configure redundancy, the primary RPM-XF should be in active state and secondary RPM-XF card must be in active/standby state.