Table Of Contents
Release Notes for Cisco IOS XR Software Release 3.3.3
Determining the Software Version
Determining the Software Version
Configuring Health-Monitoring Diagnostics
Running Health-Monitoring Diagnostics: Example
Configuring Fabric Diagnosis Testing: Example
Quality of Service (QoS) Units of Measure Changes
Cisco XR 12000 Series Router Caveats
Upgrading Cisco IOS XR Software
Changes to the Format of the File System
Obtaining Documentation, Obtaining Support, and Security Guidelines
Release Notes for Cisco IOS XR Software Release 3.3.3
March 28, 2008
Cisco IOS XR Software Release 3.3.3
Text Part Number OL-12488-05
Note
Please see the "Important Notes" section for important information about Cisco IOS XR Software Release 3.3.3.
Note
You can find the most current Cisco IOS XR software documentation on the World Wide Web at http://www.cisco.com/univercd/cc/td/doc/product/ioxsoft/iox33/index.htm. These electronic documents may contain updates and modifications. See the "Obtaining Documentation, Obtaining Support, and Security Guidelines" section for more information on obtaining Cisco documentation.
These release notes describe the features provided in Cisco IOS XR Software Release 3.3.3 and are updated as needed.
For a list of software caveats that apply to Cisco IOS XR Software Release 3.3.3, see the "Caveats—Release 3.3.3" section. The caveats are updated for every release and are located on the World Wide Web at www.cisco.com.
We recommend that you view the field notices for this release to see if your software or hardware platforms are affected, at http://www.cisco.com/public/support/tac/fn_index.html.
Contents
These release notes contain the following sections:
•
Upgrading Cisco IOS XR Software
•
Obtaining Documentation, Obtaining Support, and Security Guidelines
Introduction
Cisco IOS XR software is a distributed operating system designed for continuous system operation combined with service flexibility and high performance.
Cisco IOS XR software provides the following features and benefits:
•
IP and Routing—Supports a wide range of IPv4 and IPv6 services and routing protocols, such as Border Gateway Protocol (BGP), Intermediate System-to-Intermediate System (IS-IS), Open Shortest Path First (OSPF), IP Multicast, Routing Policy Language (RPL), and Hot Standby Router Protocol (HSRP)/Virtual Router Redundancy Protocol features (VRRP).
•
Multiprotocol Label Switching (MPLS)—Supports MPLS protocols, including Traffic Engineering (TE), Resource Reservation Protocol (RSVP), and Label Distribution Protocol (LDP).
•
Multicast—Provides comprehensive IP Multicast software, including Source Specific Multicast (SSM). The Cisco CRS-1 router supports Bidirectional Protocol Independent Multicast (BIDIR-PIM).
•
Quality of Service (QoS)—Supports rich QoS mechanisms, including policing, marking, queuing, dropping, and shaping. Additionally, the operating systems support Modular QoS CLI (MQC). MQC is used to configure various QoS features on various Cisco platforms.
•
Manageability—Provides industry-standard management interfaces including modular command-line interface (CLI), Simple Network Management Protocol (SNMP), and native Extensible Markup Language (XML) interfaces.
•
Security—Provides comprehensive network security features, including access control lists (ACLs), the routing authentications AAA and TACACS+, Secure Shell (SSH), and SNMPv3. Control plane protections integrated into line card ASICs include Global Time-to-Live Security Mechanism (GTSM), RFC 3682, and dynamic control plane protection (DCoPP).
•
Craft Works interface (CWI)—The CWI is a client-side application used to configure and manage Cisco routers. The management and configuration features include fault, configuration, security, and inventory, with an emphasis on speed and efficiency. The CWI provides a context-sensitive graphical representation of the objects in a Cisco router, simplifying the process of configuring and managing the router. CWI allows you to log in to multiple routers and perform management tasks.
•
Availability—Supports rich availability features such as fault containment, fault tolerance, fast switchover, link aggregation, and nonstop forwarding (NSF).
See the "New and Changed Information" section for a detailed list of new features by platform for Cisco IOS XR Software Release 3.3.3.
System Requirements
The Cisco IOS XR Software Release 3.3.3 is supported on the following platforms:
Cisco CRS-1 Router
This section describes the system requirements for Cisco IOS XR Software Release 3.3.3 supported on a Cisco CRS-1 router and includes the following information:
•
Determining the Software Version
Note
The Designated Shelf Controller (DSC) migration feature requires that both shelf route processors (RPs) are in the default SDR of the Cisco CRS-1 Multichassis System.
Feature Set Table
Cisco IOS XR software is packaged in feature sets (also called software images). Each feature set contains a specific set of Cisco IOS XR Software Release 3.3.3 features. These features are delivered in a package called a package installation envelope (PIE). Table 1 and Table 2 list the Cisco IOS XR software feature set matrix and associated PIE and TAR filenames available for the Cisco IOS XR Software Release 3.3.3 supported on the Cisco CRS-1 router.
Table 1 Cisco CRS-1 Supported Feature Sets (Cisco IOS XR Software Release 3.3.3 PIE Files)
Feature Set Filename Description Composite PackageCisco IOS XR IP Unicast Routing Core Bundle
comp-hfr-mini.pie-3.3.3
Contains the required core packages, including OS, Admin, Base, Forwarding, Modular Services Card, and Routing packages.
Optional Individual Packages1Cisco IOS XR Manageability Package
hfr-mgbl-p.pie-3.3.3
CORBA agent, XML Parser, HTTP server, SNMP Agent, and Alarm correlation.
Cisco IOS XR MPLS Package
hfr-mpls-p.pie-3.3.3
MPLS-TE, LDP, MPLS Forwarding, MPLS OAM, LMP, OUNI, and RSVP.
Cisco IOS XR Multicast Package
hfr-mcast-p.pie-3.3.3
Multicast Routing Protocols (PIM, MSDP, IGMP, Auto-RP), Tools (SAP, MTrace), and Infrastructure (MRIB, MURIB, MFWD), and BIDIR.
Cisco IOS XR Security Package
hfr-k9sec-p.pie-3.3.3
Support for Encryption, Decryption, IPSec, SSH, SSL, and PKI.
Cisco IOS XR Diagnostic Package
hfr-diags-p.pie-3.3.3
Diagnostic utilities, both online and offline, for Cisco IOS XR routers.
1 Packages are installed individually.
Memory Requirements
The minimum memory requirements for Cisco CRS-1 routers running Cisco IOS XR Software
Release 3.3.3 are:•
2-GB memory on the route processors (RPs)
•
1-GB memory on the modular services cards (MSCs)
Hardware Supported
Cisco IOS XR Software Release 3.3.3 supports Cisco CRS-1 routers. All hardware features are supported by Cisco IOS XR software, subject to the memory requirements specified in the "Memory Requirements" section.
Table 3 lists the hardware components supported on the Cisco CRS-1 and the minimum software versions required. See the "Determining the Software Version" section.
Software Compatibility
Cisco IOS XR Software Release 3.3.3 is compatible with the following Cisco CRS-1 systems:
•
Cisco CRS-1 8-Slot Line Card Chassis
•
Cisco CRS-1 16-Slot Line Card Chassis
Note
The Cisco CRS-1 4-Slot Line Card Chassis requires Cisco IOS XR Software Release 3.4.0 and, therefore cannot operate with Cisco IOS XR Software Release 3.3.3.
Determining the Software Version
To determine the version of Cisco IOS XR software running on your router, log in to the router and enter the show version command:
Step 1
Establish a Telnet session with the router.
Step 2
Enter the show version command:
RP/0/RP0/CPU0:router# show versionRP/0/RP0/CPU0:ios#show versionCisco IOS XR Software, Version 3.3.3[00]Copyright (c) 2007 by cisco Systems, Inc.ROM: System Bootstrap, Version 1.43(20061109:045749) [CRS-1 ROMMON],ios uptime is 2 hours, 13 minutesSystem image file is "disk0:hfr-os-mbi-3.3.3/mbihfr-rp.vm"cisco CRS-8/S (7457) processor with 4194304K bytes of memory.7457 processor at 1197Mhz, Revision 1.217 Packet over SONET/SDH network interface(s)17 SONET/SDH Port controller(s)8 TenGigabitEthernet/IEEE 802.3 interface(s)2 Ethernet/IEEE 802.3 interface(s)8 GigabitEthernet/IEEE 802.3 interface(s)2043k bytes of non-volatile configuration memory.38079M bytes of hard disk.998576k bytes of ATA PCMCIA card at disk 0 (Sector size 512 bytes).Configuration register on node 0/RP0/CPU0 is 0x102
Other Firmware Code
The following firmware code is supported by the Cisco CRS-1 router:
•
The minimum ROMMON version required for this release is 1.45. For detailed information on ROMMON specifications, see http://www.cisco.com/web/Cisco_IOS_XR_Software/index.html.
Note
Before you upgrade a Cisco CRS-1 system to Cisco IOS XR Software Release 3.3.3 or a later release, make sure that ROM Monitor software is version 1.45 or a later version on all RPs and all nodes on the router. If the router comes up with an incompatible version of the ROM Monitor, the standby RP or other nodes might fail to boot.
In addition, Cisco CRS-1 multishelf systems should be upgraded to ROMMON version 1.45 before being upgraded to Cisco IOS XR software Release 3.3.3 to ensure that RPs receive the correct rack number assignments during system boot.•
The minimum CPUCNTRL version required for this release is 2.07.
•
For detailed information on ROMMON, see Cisco IOS XR ROM Monitor Guide.
Cisco XR 12000 Series Router
This section describes the system requirements for Cisco IOS XR Software Release 3.3.3 supported on the Cisco XR 12000 Series Router and includes the following information:
•
Determining the Software Version
Feature Set Table
The Cisco IOS XR software is packaged in feature sets (software images). Each feature set contains a specific set of features. Table 4 and Table 5 list the Cisco IOS XR software feature set matrix and the associated filenames for the Cisco XR 12000 Series Router.
Table 4 Cisco XR 12000 Series Router Supported Feature Sets (Cisco IOS XR Software Release 3.3.3 PIE Files)
Feature Set Filename Description Composite PackageCisco IOS XR IP Unicast Routing Core Bundle
c12k-mini.vm-3.3.3
Contains the required core packages including, OS, Admin, Base, Forwarding, and Routing packages.
Optional Individual Packages1Cisco IOS XR Manageability Package
c12k-mgbl.pie-3.3.3
CORBA agent, XML Parser, HTTP server, SNMP Agent, and Alarm correlation.
Cisco IOS XR MPLS Package
c12k-mpls.pie-3.3.3
MPLS-TE, LDP, MPLS Forwarding, MPLS OAM, LMP, OUNI, and RSVP.
Cisco IOS XR Multicast Package
c12k-mcast.pie-3.3.3
Multicast Routing Protocols (PIM, MSDP, IGMP, Auto-RP), Tools (SAP, MTrace), and Infrastructure (MRIB, MURIB, MFWD).
Cisco IOS XR Security Package
c12k-k9sec.pie-3.3.3
Support for Encryption, Decryption, IPSec, SSH, SSL, and PKI.
Cisco IOS XR Standby RP Boot Image
mbiprp-rp.vm-3.3.3
Support for booting the standby RP on a Cisco XR 12000 Series Router (PRP).
Cisco IOS XR Diagnostic Package
c12k-diags.pie-3.3.3
Diagnostic utilities for Cisco IOS XR routers
1 Packages are installed individually.
Memory Requirements
CautionIf you remove the medium in which the software image or configuration is stored, the router might become unstable and fail.
The minimum memory requirements for Cisco XR 12000 Series routers running Cisco IOS XR Software Release 3.3.3 are:
•
2-GB route memory on Performance Route Processor 2 (PRP-2)
•
1-GB ATA flash storage on PRP-2
•
1-GB industrial grade compact flash storage on PRP-2 (FLASH-PRP2-1G)
Note
1-GB compact flash is supported only with Cisco IOS XR software version 3.3.0 and later releases. Therefore, if you are upgrading from a release prior to Release 3.3.0, you must continue to use disk0.
In the current release, only the FLASH-PRP2-1G compact flash is supported.•
1-GB line-card route memory on all line Engine 3 cards installed in the system
•
1-GB line-card route memory on all Engine 5-based SPA Interface Processors in the system:
–
The default route memory on the 1200-SIP-600 is 1G.
–
The default route memory on the 1200-SIP-401, 1200-SIP-501, and 1200-SIP-601 is 2 G.
Hardware Supported
Cisco IOS XR Software Release 3.3.3 supports the Cisco XR 12000 Series Router. All hardware features are supported on Cisco IOS XR software, subject to the memory requirements specified in the "Memory Requirements" section.
Table 6 lists the hardware components supported on the Cisco XR 12000 Series Router and the minimum software versions required. See the "Determining the Software Version" section.
.
Software Compatibility
Cisco IOS XR Software Release 3.3.3 is compatible with the following Cisco XR 12000 Series Router systems:
•
Cisco XR 12404 Router
•
Cisco XR 12406 Router
•
Cisco XR 12410 Router
•
Cisco XR 12416 Router
For the existing installed base, the following chassis are supported:
•
Cisco 12006 Router
•
Cisco 12008 Router
•
Cisco 12010 Router
•
Cisco 12012 Router
•
Cisco 12016 Router
Determining the Software Version
To determine the version of Cisco IOS XR software running on your router, log in to the router and enter the show version command:
Step 1
Establish a Telnet or SSH session with the router.
Step 2
Enter the show version command:
RP/0/5/CPU0:PE4#show versionCisco IOS XR Software, Version 3.3.3[00]Copyright (c) 2007 by cisco Systems, Inc.ROM: System Bootstrap, Version 12.0(20041108:104740) [ashp-cisp-rommon 1.16dev(0.1)] DEVELOPMENT SOFTWARECopyright, Inc.PE4 uptime is 18 hours, 49 minutesSystem image file is "disk0:c12k-os-mbi-3.3.3/mbiprp-rp.vm"cisco 12406/PRP (7457) processor with 2097152K bytes of memory.7457 processor at 1265Mhz, Revision 1.23 1 Port ISE Packet Over SONET OC-48c/STM-16 Controllers (3 POS)1 Cisco 12000 Series SPA Interface Processor- Controller (4294967295 Unknown)2 Cisco 12000 Series Performance Route Processors4 Packet over SONET/SDH network interface(s)4 SONET/SDH Port controller(s)4 PLIM QoS controller(s)6 Ethernet/IEEE 802.3 interface(s)10 GigabitEthernet/IEEE 802.3 interface(s)2042k bytes of non-volatile configuration memory.1000496k bytes of ATA PCMCIA card at disk 0 (Sector size 512 bytes).65536k bytes of Flash internal SIMM (Sector size 256k).
Other Firmware Code
The following firmware code is supported by the Cisco XR 12000 Series Router:
•
The minimum ROMMON version required for this release is 1.15. For more information on the minimum ROMMON version required for this release, ROMMON upgrade procedures, and flashdisk information, see the Upgrading from Cisco IOS to Cisco IOS XR Software on the Cisco XR 12000 Series Router document.
•
The flashdisk Cisco part numbers are: MEM-12KRP-FD512M (=), MEM-12KRP-FD1G(=), and FLASH-PRP2-1G
New and Changed Information
No new software or hardware features are introduced in Cisco IOS XR Software Release 3.3.3.
This section includes the following information:
•
Health-Monitoring Diagnostics
•
Quality of Service (QoS) Units of Measure Changes
Health-Monitoring Diagnostics
Health-monitoring diagnostic tests are non disruptive and run in the background while the system is in operation. The role of health-monitoring diagnostics is to be proactive in detecting hardware failures in the live network environment and inform appropriate entities of a failure. It is up to you to determine the interval at which to run health-monitoring checks. The interval can be as granular as 50ms.
You can configure health-monitoring diagnostics, including support for monitor intervals and the failure count thresholds of tests.
The show diagnostic content command output was modified to include diagnostic monitoring support.
Note
Health-monitoring and other diagnostic configurations are not persistent across system reloads. You must manually reapply the configurations after rebooting the system.
Configuring Health-Monitoring Diagnostics
To configure health-monitoring diagnostic testing on specified cards while the router is connected to a
live network, perform the following procedure. You can configure the:
•
Execution interval for each health-monitoring test
•
Failure threshold for each health-monitoring test
•
Location where each health-monitoring test is run
Prerequisites
The Cisco IOS XR Diagnostics Package must be installed before starting this procedure. See Cisco IOS XR Getting Started Guide for information on installing packages.
SUMMARY STEPS
1.
admin
2.
configure
3.
diagnostic monitor location node-id test {id | test-name} [disable]
4.
diagnostic monitor interval location node-id test {id | test-name} number-of-days hour:minutes:seconds.milliseconds
5.
diagnostic monitor threshold location node-id test {id | test-name} failure count failures
DETAILED STEPS
Running Health-Monitoring Diagnostics: Example
In the following example, health-monitoring diagnostic test 1 for 0/1/CPU0 is enabled:
RP/0/RP0/CPU0:router(admin-config)# diagnostic monitor location 0/1/cpu0 test 1In the following example, health-monitoring diagnostic test 1 for 0/1/CPU0 is set to an interval of every 15 days and 6 hours:
RP/0/RP0/CPU0:router(admin-config)# diagnostic monitor interval location 0/1/cpu0 test 115 6:0:0.0In the following example, the health-monitoring diagnostic testing failure threshold is set to 25 failures for test 1 on 0/1/CPU0:
RP/0/RP0/CPU0:router(admin-config)# diagnostic monitor threshold location 0/1/CPU0 test 1 failure count 25The following example shows a sample result of the diagnostic test using the show diagnostic result location <loc> detail command.
Overall diagnostic result: PASSDiagnostic level at card bootup: minimalTest results: (. = Pass, F = Fail, U = Untested)1 ) ControlEthernetPingTest ---------> .Error code ------------------> 0 (DIAG_SUCCESS)Total run count -------------> 1Last test execution time ----> Wed Oct 4 05:29:28 2006First test failure time -----> n/aLast test failure time ------> n/aLast test pass time ---------> Wed Oct 4 05:29:28 2006Total failure count ---------> 0Consecutive failure count ---> 02 ) SelfPingOverFabric --------------> .Error code ------------------> 0 (DIAG_SUCCESS)Total run count -------------> 1Last test execution time ----> Wed Oct 4 05:29:28 2006First test failure time -----> n/aLast test failure time ------> n/aLast test pass time ---------> Wed Oct 4 05:29:28 2006Total failure count ---------> 0Consecutive failure count ---> 03 ) FabricPingTest ------------------> .Error code ------------------> 0 (DIAG_SUCCESS)Total run count -------------> 1Last test execution time ----> Wed Oct 4 05:29:58 2006First test failure time -----> n/aLast test failure time ------> n/aLast test pass time ---------> Wed Oct 4 05:29:58 2006Total failure count ---------> 0Consecutive failure count ---> 04 ) ControlEthernetInactiveLinkTest -> .Error code ------------------> 0 (DIAG_SUCCESS)Total run count -------------> 1Last test execution time ----> Wed Oct 4 05:30:00 2006First test failure time -----> n/aLast test failure time ------> n/aLast test pass time ---------> Wed Oct 4 05:30:00 2006Total failure count ---------> 0Consecutive failure count ---> 05 ) RommonRevision ------------------> .Error code ------------------> 0 (DIAG_SUCCESS)Total run count -------------> 1Last test execution time ----> Wed Oct 4 05:30:09 2006First test failure time -----> n/aLast test failure time ------> n/aLast test pass time ---------> Wed Oct 4 05:30:09 2006Total failure count ---------> 0Consecutive failure count ---> 0By default, tests do not report any syslogs during health-monitoring. Only test results indicate any errors.
Fabric Diagnosis Testing
Fabric Diagnosis test is a non-disruptive, fault isolation test that "pings" each fabric node in a chassis from the standby RP node. The test steers ping test packets through different fabric planes, aggregates ping (pass or fail) results with fabric plane information, analyzes the results, and points out the most logical point of failure (if any) in the chassis. The test can only be executed from the standby RP Executing this test in a Cisco CRS-1 Carrier Routing System Multishelf System may help determine which fabric stage (s1, s2, or s3) is the most logical point of failure in the system. This test must be run in each LC rack standby RP in the system. For example, if the test reports failures on multiple LC racks, and the failure information points to the same fabric plane, then the most likely point of failure is the S2 stage, which is the card in fabric chassis of the system.
This test is recommended for Health Monitoring and reports syslogs, regardless of the "monitor syslog" setting. For certain types of failures, this test can help quickly detect fabric hardware issues.
The following restrictions apply to the Fabric Diagnosis tests:
•
By default, this test is not running in Health Monitoring mode. You must activate the test manually.
•
When you first run the test, you might not receive reports of defects. If you run the test manually, (and it is not already configured for Health Monitoring active mode), run the test once, wait for a couple of minutes, and then run it again to get a definite test result.
This initial period also applies when you start or restart a card that is running IOS XR. The test takes a few minutes before it can reliably detect issues with the newly added card.
Configuring Fabric Diagnosis Testing: Example
Cisco recommends that you configure the fabric diagnosis test as periodical health monitoring. Set the interval based on how soon you want to catch and isolate the fabric error. Cisco recommends that you set the interval for a minimum of 2 seconds. The following example shows the recommended configuration:
RP/0/RP0/CPU0:router(admin-config)#diagnostic monitor location 0/RP0/CPU0 test 4RP/0/RP0/CPU0:router(admin-config)#diagnostic monitor interval location 0/RP0/CPU0 test 4 0 00:00:03.0RP/0/RP0/CPU0:router(admin-config)#diagnostic monitor location 0/RP1/CPU0 test 4RP/0/RP0/CPU0:router(admin-config)#diagnostic monitor interval location 0/RP1/CPU0 test 4 0 00:00:03.0RP/0/RP0/CPU0:router(admin-config)#commitUse the show running-config command to confirm the settings.
RP/0/RP0/CPU0:router# show running-configdiagnostic monitor location 0/RP0/CPU0 test FabricDiagnosisTestdiagnostic monitor interval location 0/RP0/CPU0 test FabricDiagnosisTest 0 00:00:03.0diagnostic monitor location 0/RP1/CPU0 test FabricDiagnosisTestdiagnostic monitor interval location 0/RP1/CPU0 test FabricDiagnosisTest 0 00:00:03.0DRP Update
DRP and DRP-B are now supported as "location" in the CLI from RPs in the system.
The diagnostic CLI is not available on the DRP console. You must configure DRP tests from RP consoles.
Diagnostic CLI Change
Syntax for specifying a list of tests in configuration of "diagnostic schedule location <R/S/I> test <ID list>... " has changed. The new syntax for <ID list> is now "i;j-k" (previously "i,j-k").
Quality of Service (QoS) Units of Measure Changes
For Cisco IOS XR Software Release 3.3.0 and later releases, a number of new units of measure that have been introduced as options within the various Modular QoS command-line interface (MQC) can be applied within policy-maps.
Because the default units of measure may no longer be the same, care must be taken when taking a configuration earlier than Cisco IOS XR Software Release 3.3.0 and applying it to Cisco IOS XR Software Release 3.3.0 or later releases. Table 7 lists the changes to QoS units of measure.
Note
The default units of measure (see Table 7) are inserted into the QoS policy following the upgrade. This results in a change to the policy's behavior. Therefore, manual review and keyword


