Table Of Contents
Release Notes for Cisco IOS XR Software Release 3.6.2
Determining the Software Version
New Software Features in Cisco IOS XR Software Release 3.6.2
Cisco CRS-1 and Cisco XR 12000 Series Router
Cisco CRS-1 Router-Specific Features Only
Cisco XR 12000 Series Router-Specific Features Only
Cisco XR 12000 Series Router Services
New Hardware Features Supported in Cisco IOS XR Release 3.6.2
Software Feature Documentation
Enhanced Tuning of SPF LSA Counts for OSPF Topology
Implementing LDP-IGP Synchronization Enhancements for OSPF
MPLS Traffic Engineering and Fast-Reroute Enhancements on OSPF
Implementing MPLS Traffic Engineering Shared-Risk Link Group (SRLG)
MPLS SRLG-Related Command Reference Information
Using MPLS Tunnel Drop Counts to Display Drop or Error Packets on MPLS TE Interfaces
New and Enhanced Fabric Diagnostic Tests
Minimum Flash Disk Requirements When Upgrading to Release 3.6.2
Activation Requirements for the Cisco CRS-1 Multishelf System Encryption PIE
Cisco CRS-1 and Cisco XR 12000 Series Router Caveats
Caveats Specific to the Cisco CRS-1 Router
Caveats Specific to the Cisco XR 12000 Series Router
Upgrading Cisco IOS XR Software
Using a Software Maintenance Update (SMU)
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco IOS XR Software Release 3.6.2
February 2, 2009
Cisco IOS XR Software Release 3.6.2
Text Part Number OL-17968-03
Note
For information about Cisco IOS XR Software Release 3.6.2, see "Important Notes" section.
Note
You can find the most current Cisco IOS XR software documentation on the World Wide Web at http://www.cisco.com/en/US/partner/products/ps5845/tsd_products_support_series_home.html. These electronic documents may contain updates and modifications. For more information on obtaining Cisco documentation, see the "Obtaining Documentation and Submitting a Service Request" section.
These release notes describe the features provided in the Cisco IOS XR Software Release 3.6.2 and are updated as needed.
For a list of software caveats that apply to Cisco IOS XR Software Release 3.6.2, see the "Caveats" 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:
•
New Features and Enhancements
•
Upgrading Cisco IOS XR Software
•
Using a Software Maintenance Update (SMU)
•
Obtaining Documentation and Submitting a Service Request
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), Routing Information Protocol (RIP), Intermediate System-to-Intermediate System (IS-IS), Open Shortest Path First (OSPF), IP Multicast, Routing Policy Language (RPL), Hot Standby Router Protocol (HSRP), or Virtual Router Redundancy Protocol features (VRRP).
•
BGP Prefix Independent Convergence—Provides the ability to converge BGP routes within sub seconds instead of multiple seconds. The Forwarding Information Base (FIB) is updated, independent of a prefix, to converge multiple 100K BGP routes with the occurrence of a single failure. This convergence is applicable to both core and edge failures and with or with out MPLS. This fast convergence innovation is unique to Cisco IOS XR software.
•
Multiprotocol Label Switching (MPLS)—Supports MPLS protocols, including Traffic Engineering (TE), Resource Reservation Protocol (RSVP), Label Distribution Protocol (LDP), Layer 2 Virtual Private Network (L2VPN), and Layer 3 Virtual Private Network (L3VPN).
•
Multicast—Provides comprehensive IP Multicast software including Source Specific Multicast (SSM). Cisco Carrier Routing System (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 command-line interface (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); routing authentications; Authentication, Authorization, and Accounting (AAA)/Terminal Access Controller Access Control System (TACACS+); Secure Shell (SSH); and Simple Network Management Protocol version3 (SNMPv3). Control plane protections integrated into line card Application-Specific Integrated Circuits (ASICs) include Generalized TTL Security Mechanism (GTSM), RFC 3682, and Dynamic Control Plane Protection (DCPP).
•
Craft Works Interface (CWI)—CWI is a client-side application used to configure and manage Cisco routers. 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. The 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).
•
Multicast service delivery in SP NGN—MVPNv4 support carries multicast traffic over an ISP MPLS core network.
•
Cisco IOS IPv6 Provider Edge Router support for IPv6 applications—Delivers IPv6 traffic over an IPv4/MPLS core with Cisco IOS IPv6 Provider Edge Router (6PE) support (Cisco XR 12000 Series Router only).
•
IPv6 VPN over MPLS (6VPE) support—Delivers IPv6 VPN over MPLS (IPv6) VPN traffic over an IPv4 or MPLS core with 6VPE support (Cisco XR 12000 Series Router only).
•
6VPE over L2TPv3 support—Delivers IPv6 VPN traffic over L2TPv3 core with 6VPE support (Cisco XR 12000 Series Router only). This feature is also available on Cisco IOS Software.
•
Enhanced core competencies:
–
Support for IS-IS and OSPF.
–
IP fast convergence with Fast Reroute (FRR) support for Intermediate System-to-Intermediate System (IS-IS)
–
Traffic engineering support for unequal load balancing
–
Path Computation Element (PCE) capability for traffic engineering
•
Firewall Services—Seamless insertion of Firewall Services in the data path with Virtual Firewall support on Multiservice Blade (XR-12K-MSB) for the Cisco XR 12000 Series Router.
•
VPN IPSec Aggregation—The IPSec Aggregation feature is provided through SPA-IPSEC-2G-2 card. The IPSec Aggregation feature allows you to terminate up to 64-K VPN tunnels, both site-to-site and remote access, if four VPN SPAs are used.
•
Voice Video—Voice Video interconnect between providers with Session Border Controller (SBC) on the Cisco XR 12000 Series Router.
•
L2TPv3 Tunneling Mechanism—Service Providers who do not use MPLS in the core, but want to offer VPN services can use the L2TPv3 tunneling mechanism. This feature support includes IPv4 (VPNv4) and IPv6 (6VPE) VPN services using L2TPv3 encapsulation. The L2TPv3 packet is encapsulated in an IPv4 delivery header and is carried across an IPv4 backbone. VPN prefixes are advertised with BGP labels and resolved over L2TPv3 tunnels.
For more information about new features provided on various platforms for Cisco IOS XR Software Release 3.6.2, see the "New Features and Enhancements" section in this document.
System Requirements
Cisco IOS XR Software Release 3.6.2 supports the following platforms:
To determine the software versions or levels of your current system, see the "Determining the Software Version" section.
Cisco CRS-1
This section describes the system requirements for Cisco IOS XR Software Release 3.6.2 supported on the Cisco CRS-1 router. The system requirements include the following information:
To determine the software versions or levels of your current system, see Determining the Software Version.
Feature Set Table
The 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.6.2 features. Table 1 lists the Cisco IOS XR software feature set matrix (PIE files) and associated filenames available for the Cisco IOS XR Software Release 3.6.2 supported on the Cisco CRS-1 router.
Table 1 Cisco CRS-1 Supported Feature Sets (Cisco IOS XR Software Release 3.6.2 PIE Files)
Feature Set Filename Description Composite PackageCisco IOS XR IP Unicast Routing Core Bundle
comp-hfr-mini.pie-3.6.2
Contains the required core packages including OS, Admin, Base, Forwarding, and Routing SNMP Agent, and Alarm Correlation.
Cisco IOS XR IP Unicast Routing Core Bundle
comp-hfr-mini.vm-3.6.2
Contains the required core packages including OS, Admin, Base, Forwarding, and Routing SNMP Agent, and Alarm Correlation.
Optional Individual Packages1Cisco IOS XR Manageability Package
hfr-mgbl-p.pie-3.6.2
Cisco IOS XR MPLS Package
hfr-mpls-p.pie-3.6.2
MPLS-TE,4 LDP,5 MPLS Forwarding, MPLS OAM,6 LMP,7 OUNI,8 RSVP,9 and Layer-2 VPN and Layer-3 VPN.
Cisco IOS XR Multicast Package
hfr-mcast-p.pie-3.6.2
Multicast Routing Protocols (PIM, MSDP,10 IGMP,11 Auto-RP), Tools (SAP, MTrace), and Infrastructure (MRIB,12 MURIB13 , MFWD14 ), and BIDIR-PIM.15
Cisco IOS XR Security Package
hfr-k9sec-p.pie-3.6.2
Support for Encryption, Decryption, IPSec,16 SSH,17 SSL,18 and PKI19 (Software based IPSec support - maximum of 500 tunnels).
Cisco IOS XR Documentation Package
hfr-doc.pie-3.6.2
Man pages for Cisco IOS XR CLI commands
Cisco IOS XR FPD Package
hfr-fpd.pie-3.6.2
Firmware for Fixed PLIM20 and SPA21 modules as well as ROMMON22 images for Cisco CRS-1 chassis.
Cisco IOS XR Diagnostic Package
hfr-diags-p.pie-3.6.2
Diagnostic utilities for routers running Cisco IOS XR software.
Cisco IOS XR Session Border Controller Package
hfr-sbc-p.pie-3.6.2
Session Border Controller package for the Cisco CRS-1 router.
1 Packages are installed individually
2 Common Object Request Broker Architecture
3 Extensible Markup Language
4 MPLS Traffic Engineering
5 Label Distribution Protocol
6 Operations, Administration, and Maintenance
7 Link Manager Protocol
8 Optical User Network Interface
9 Resource Reservation Protocol
10 Multicast Source Discovery Protocol
11 Internet Group Management Protocol
12 Multicast Routing Information Base
13 Multicast-Unicast RIB
14 Multicast forwarding
15 Bidirectional Protocol Independent Multicast
16 IP Security
17 Secure Shell
18 Secure Socket Layer
19 Public-key infrastructure
20 Physical layer interface module
21 Shared port adapters
22 ROM monitor
Table 2 lists Cisco CRS-1 TAR files.
Memory Requirements
CautionIf you remove the media in which the software image or configuration is stored, the router may become unstable and fail.
The minimum memory requirements for Cisco CRS-1 routers running Cisco IOS XR Software Release 3.6.2 consist of the following:
•
4-GB memory or greater on the route processors (RPs)
•
2-GB memory or greater on the modular services cards (MSCs)
•
1-GB or greater PCMCIA Flash Disk
Also review the flash disk memory space requirements for future upgrades under the "Minimum Flash Disk Requirements When Upgrading to Release 3.6.2" section. Release 3.7.x and later releases require installation of at least 2 GB of flash memory before you upgrade.
Hardware Supported
Cisco IOS XR Software Release 3.6.2 is supported on all Cisco CRS-1 routers. Likewise, all the Cisco CRS-1 hardware features are supported by Cisco IOS XR software, subject to the memory requirements specified in the "Memory Requirements" section.
Table 3 lists these Cisco CRS-1 hardware components and the minimum versions of Cisco IOS XR software required in each case. For more information, see the "Firmware Support" section.
Software Compatibility
Cisco IOS XR Software Release 3.6.2 is compatible with the following Cisco CRS-1 systems:
•
Cisco CRS-1 4-Slot Line Card Chassis
•
Cisco CRS-1 8-Slot Line Card Chassis
•
Cisco CRS-1 16-Slot Line Card Chassis
Firmware Support
The Cisco CRS-1 router supports the following firmware code:
•
The minimum ROMMON version required for this release is 1.49. For more information about ROMMON specifications, go to: http://www.cisco.com/web/Cisco_IOS_XR_Software/index.html.
•
The minimum CPUCNTRL version required for this release is 2.07. For more information about CPU controller bits, go to: http://www.cisco.com/en/US/docs/ios_xr_sw/iosxr_r3.6/system_management/configuration/guide/yc36hdwr.html.
Cisco XR 12000 Series Router
This section describes the system requirements for Cisco IOS XR Software Release 3.6.2 supported on the Cisco XR 12000 Series Router. The system requirements include the following information:
To determine the software versions or levels of your current system, see "Determining the Software Version" section.
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.6.2 features. Table 4 lists the Cisco IOS XR software feature set matrix (PIE files) and associated filenames available for Cisco IOS XR Software Release 3.6.2 and supported on the Cisco XR 12000 Series Router.
Table 4 Cisco XR 12000 Series Router Supported Feature Set (Cisco IOS XR Software
Release 3.6.2 PIE Files) Feature Set Filename Description Composite PackageCisco IOS XR IP Unicast Routing Core Bundle
c12k-mini.pie-3.6.2
Contains the required core packages, including OS, Admin, Base, Forwarding, Routing, SNMP Agent, and Alarm Correlation.
Cisco IOS XR IP Unicast Routing Core Bundle
c12k-mini.vm-3.6.2
Contains the required core packages including OS, Admin, Base, Forwarding, and Routing SNMP Agent, and Alarm Correlation.
Optional Individual Packages1Cisco IOS XR Manageability Package
c12k-mgbl.pie-3.6.2
CORBA2 agent, XML Parser, and HTTP server packages.
Cisco IOS XR MPLS Package
c12k-mpls.pie-3.6.2
MPLS-TE,3 LDP, 4 MPLS Forwarding, MPLS OAM,5 LMP,6 OUNI,7 and RSVP.8
Cisco IOS XR Multicast Package
c12k-mcast.pie-3.6.2
Multicast Routing Protocols (PIM,9 MSDP,10 IGMP,11 Auto-RP, BSR12 ), Tools (SAP, MTrace, MRINFO), and Infrastructure (MRIB,13 MURIB,14 MFWD)15 .
Cisco IOS XR Security Package
c12k-k9sec.pie-3.6.2
Support for Encryption, Decryption, IPSec16 , SSH,17 SSL,18 and PKI.19 (Software based IPSec support - maximum of 500 tunnels or Hardware based IPSec - maximum of 64K tunnels using the SPA-IPSEC-2G-2)
Cisco IOS XR Standby RP Boot Image
mbiprp-rp.vm-3.6.2
Support for booting the Standby RP on a Cisco XR 12000 Series Router.
Cisco IOS XR Session Border Controller Package
c12k-sbc.pie-3.6.2
Session Border Controller Package for a Cisco XR 12000 Series Router.
Cisco IOS XR Service IPSec controller Package
c12k-ipsec-service.pie-3.6.2
Support for service-ipsec and service-gre interfaces in Cisco IOS XR software.
Cisco IOS XR Firewall package
c12k-firewall.pie-3.6.2
Support for Virtual Firewall (vFW) on a Cisco XR 12000 Series Router.
Cisco IOS XR Documentation Package
c12k-doc.pie-3.6.2
Man pages for Cisco IOS XR CLI commands.
Cisco IOS XR FPD Package
c12k-fpd.pie-3.6.2
Firmware for shared port adapters (SPA) and for fixed port line cards supported in Cisco IOS XR.
Cisco IOS XR Diagnostic Package
c12k-diags.pie-3.6.2
Diagnostic utilities for Cisco IOS XR routers.
1 Packages are installed individually
2 Common Object Request Broker Architecture
3 MPLS Traffic Engineering
4 Label Distribution Protocol
5 Operations, Administration, and Maintenance
6 Link Manager Protocol
7 Optical User Network Interface
8 Resource Reservation Protocol
9 Protocol Independent Multicast
10 Multicast Source Discovery Protocol
11 Internet Group Management Protocol
12 Bootstrap router
13 Multicast Routing Information Base
14 Multicast-Unicast RIB
15 Multicast forwarding
16 IP Security
17 Secure Shell
18 Secure Socket Layer
19 Physical layer interface module
Table 5 lists the Cisco XR 12000 Series Router TAR files.
Memory Requirements
CautionIf you remove the media in which the software image or configuration is stored, the router may become unstable and fail.
The minimum memory requirements for Cisco XR 12000 Series Routers running Cisco IOS XR Software Release 3.6.2 consist of the following:
•
2-GB or more route memory on Performance Route Processor 2 (PRP-2)
Note
4-GB route memory on PRP-2 is required if IPSec tunnel scale of 64 K is planned.
•
2-GB or greater ATA flash memory on PRP-2
•
1-GB line card route memory on all Engine 3 line cards
•
1-GB line card memory on all Engine 5-based SPA interface processors (SIPs)
–
The default route memory on the 12000-SIP-600 is 1 GB.
–
The default route memory on the 12000-SIP-401, 501, and 601 is 2 GB.
Note
The performance route processor 1 (PRP-1) is not supported in production environments.
Hardware Supported
Cisco IOS XR Software Release 3.6.2 is supported on the Cisco XR 12000 Series Router. Likewise, all Cisco XR 12000 Series Router hardware features are supported by Cisco IOS XR software, subject to the memory requirements specified in the "Memory Requirements" section.
Table 6 lists the supported hardware components on the Cisco XR 12000 Series Router and the minimum versions of Cisco IOS XR software they require. For more information, see the "Determining the Software Version" section.
Software Compatibility
Cisco IOS XR Software Release 3.6.2 is compatible with the following Cisco XR 12000 Series Router systems:
•
Cisco XR 12004 Router
•
Cisco XR 12006 Router
•
Cisco XR 12010 Router
•
Cisco XR 12016 Router
•
Cisco XR 12404 Router
•
Cisco XR 12406 Router
•
Cisco XR 12410 Router
•
Cisco XR 12416 Router
•
Cisco XR 12810 Router
•
Cisco XR 12816 Router
Following chassis are supported for an existing installed base:
•
Cisco 12008 Router
•
Cisco 12010 Router
•
Cisco 12012 Router
Note
If you are running Cisco IOS XR software on a Cisco IOS XR 120xx system with SIP 600, 401, 501, and 601, you must upgrade the fabric. For ROMMON, MBUS, and Fabric Downloader versions, see Firmware Support.
Firmware Support
The Cisco XR 12000 Series Router supports the following firmware:
•
Line Card (LC)
–
Maintenance Bus (MBUS) Agent software—RAM Version 2.54, ROM Version 3.53
–
ROM Monitor Version 17.1
–
Fabric Downloader—RAM Version 6.5, ROM Version 6.5
For Engine 3 Line Card:
–
Maintenance Bus (MBUS) Agent software-RAM Version 2.56, ROM Version 3.53
–
ROM Monitor Version 17.1
–
Fabric Downloader—RAM Version 7.3, ROM Version 7.3
For Engine 5 Line Card:
–
Maintenance Bus (MBUS) Agent software—RAM Version 2.56, ROM Version 3.51
–
ROM Monitor Version 17.1
–
Fabric Downloader—RAM Version 4.3, ROM Version 4.3
•
Route Processors (RPs)
–
Maintenance Bus (MBUS) Agent software—RAM Version 2.54, ROM Version 3.53
–
ROM Monitor Version 1.18
Requirement of Cisco IOS Image Level and Boot Helper Version for Migration
If you are migrating from Cisco IOS to Cisco IOS XR software on the Cisco XR 12000 Series Router, you must have the following minimum Cisco IOS Image Level and Boot Helper version to support Release 3.6.2:
•
Cisco IOS image—12.0(32)S
•
Cisco IOS Boot Helper—12.0(32)S0a
If you have an earlier version of this system, you must upgrade to the minimum supported level before performing a migration. Otherwise, your migration fails. For more information, see the Migrating from Cisco IOS to Cisco IOS XR Software on the Cisco XR 12000 Series Router document.
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 versionCisco CRS-1
On the Cisco CRS-1 router, you should see a response similar to the following:
Cisco IOS XR Software, Version 3.6.2[00]Copyright (c) 2008 by Cisco Systems, Inc.ROM: System Bootstrap, Version 1.49(20080319:195807) [CRS-1 ROMMON],MPLS-MR-FF-8 uptime is 8 hours, 46 minutesSystem image file is "disk0:hfr-os-mbi-3.6.2/mbihfr-rp.vm"cisco CRS-4/S (7457) processor with 4194304K bytes of memory.7457 processor at 1197Mhz, Revision 1.28 Packet over SONET/SDH network interface(s)8 SONET/SDH Port controller(s)9 TenGigabitEthernet/IEEE 802.3 interface(s)2 Ethernet/IEEE 802.3 interface(s)8 GigabitEthernet/IEEE 802.3 interface(s)1019k bytes of non-volatile configuration memory.38079M bytes of hard disk.981440k bytes of ATA PCMCIA card at disk 0 (Sector size 512 bytes).Configuration register on node 0/0/CPU0 is 0x102Boot device on node 0/0/CPU0 is mem:Package active on node 0/0/CPU0:hfr-fpd, V 3.6.2[00], Cisco Systems, at disk0:hfr-fpd-3.6.2Built on Thu Nov 6 05:32:45 PST 2008By edde-bld1 in /auto/srcarchive1/production/3.6.2/hfr/workspace for c2.95.3-p8...Cisco XR 12000 Series Router
On the Cisco XR 12000 Series Router, you should see a response similar to the following:
Cisco IOS XR Software, Version 3.6.2[00]Copyright (c) 2008 by Cisco Systems, Inc.ROM: System Bootstrap, Version 12.0(20071023:043238) [sunnaik-rommon_hang 1.20] RELEASE SOFTWARECopyright (c) 1994-2007 by cisco Systems, Inc.12406-CE3 uptime is 33 minutesSystem image file is "disk0:c12k-os-mbi-3.6.2/mbiprp-rp.vm"cisco 12406/PRP (7457) processor with 2097152K bytes of memory.7457 processor at 1266Mhz, Revision 1.21 Cisco 12000 Series Performance Route Processor1 Cisco 12000 4-Port ISE ATM Over SONET OC12/STM-4 Controller (4 ATM)1 Cisco 12000 Series SPA Interface Processor-601/501/4011 1 Port ISE Packet Over SONET OC-48c/STM-16 Controller (1 POS)1 Cisco 12000 4 Port Gigabit Ethernet Controller (4 GigabitEthernet)2 T3 Port controller(s)4 ATM Network Interface(s)1 Packet over SONET/SDH network interface(s)5 SONET/SDH Port controller(s)5 PLIM QoS controller(s)3 Ethernet/IEEE 802.3 interface(s)1 Controller for the management of multilink interfacess9 GigabitEthernet/IEEE 802.3 interface(s)1018k 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).Configuration register on node 0/0/CPU0 is 0x2102Boot device on node 0/0/CPU0 is disk0:Package active on node 0/0/CPU0:c12k-mgbl, V 3.6.2[00], Cisco Systems, at disk0:c12k-mgbl-3.6.2Built on Thu Nov 6 15:10:56 UTC 2008By edde-bld1 in /auto/srcarchive1/production/3.6.2/c12k/workspace for c2.95.3-p8c12k-mcast, V 3.6.2[00], Cisco Systems, at disk0:c12k-mcast-3.6.2Built on Thu Nov 6 15:10:26 UTC 2008By edde-bld1 in /auto/srcarchive1/production/3.6.2/c12k/workspace for c2.95.3-p8...
New Features and Enhancements
The following sections contain information on new features and enhancements in Cisco IOS XR Software Release 3.6.2:
•
New Software Features in Cisco IOS XR Software Release 3.6.2
•
New Hardware Features Supported in Cisco IOS XR Release 3.6.2
•
Software Feature Documentation
New Software Features in Cisco IOS XR Software Release 3.6.2
Cisco CRS-1 and Cisco XR 12000 Series Router
The following Cisco IOS XR Software Release 3.6.2 software features or enhancements to existing features are supported on both the Cisco CRS-1 router and Cisco XR 12000 Series Router platforms:
•
Enhanced Tuning of SPF LSA Counts for OSPF Topology
•
Implementing LDP-IGP Synchronization Enhancements for OSPF
•
MPLS Traffic Engineering and Fast-Reroute Enhancements on OSPF
•
Implementing MPLS Traffic Engineering Shared-Risk Link Group (SRLG)
Cisco CRS-1 Router-Specific Features Only
The following new feature in Cisco IOS XR Software Release 3.6.2 is supported only on the Cisco CRS-1 platform:
•
Using MPLS Tunnel Drop Counts to Display Drop or Error Packets on MPLS TE Interfaces
•
New and Enhanced Fabric Diagnostic Tests
Cisco XR 12000 Series Router-Specific Features Only
None.
Cisco XR 12000 Series Router Services
None.
New Hardware Features Supported in Cisco IOS XR Release 3.6.2
Support for 4-GB flash memory is being introduced on the Cisco XR 12000 Series Router and Cisco CRS-1 router with the current release.
Note
The distributed route processors (DRP and DRP-B) do not support the 2-GB flash.
For minimum flash disk memory requirements and upgrade information, see the "Minimum Flash Disk Requirements When Upgrading to Release 3.6.2" section.
Software Feature Documentation
The following documentation about how to use the features introduced in the current maintenance release, is organized by the feature name for which it has been introduced.
•
Enhanced Tuning of SPF LSA Counts for OSPF Topology (Both Cisco CRS-1 and Cisco XR 12000 Series Router platforms)
•
Implementing LDP-IGP Synchronization Enhancements for OSPF (Both Cisco CRS-1 and Cisco XR 12000 Series Router platforms)
•
MPLS Traffic Engineering and Fast-Reroute Enhancements on OSPF (Both Cisco CRS-1 and Cisco XR 12000 Series Router platforms)
•
Implementing MPLS Traffic Engineering Shared-Risk Link Group (SRLG) (Both Cisco CRS-1 and Cisco XR 12000 Series Router platforms)
•
Using MPLS Tunnel Drop Counts to Display Drop or Error Packets on MPLS TE Interfaces (Cisco CRS-1 platform only)
•
New and Enhanced Fabric Diagnostic Tests (Cisco CRS-1 platform only)
Note
The command and configuration information appearing here may not found in Cisco IOS XR Software Release 3.6.0 documentation online.
Enhanced Tuning of SPF LSA Counts for OSPF Topology
Three new commands have been added to enhance the tuning of link-state advertisements (LSAs) processed per shortest path first (SPF) counts on OSPF topology:
•
queue dispatch rate-limited-lsa
queue dispatch rate-limited-lsa
To set the maximum number of rate-limited link-state advertisements (LSAs) processed per run, use the queue dispatch rate-limited-lsa command in router configuration mode. To return to the system default value, use the no form of this command.
queue dispatch rate-limited-lsa count
no queue dispatch rate-limited-lsa
Syntax Description
Defaults
The default number of rate-limited LSAs processed per run is 300 (when this count is not configured).
Command Modes
Router configuration
Command History
Release ModificationRelease 3.6.2
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to set the maximum number of rate-limited LSAs to 30:
RP/0/RP0/CPU0:router(config-ospf)# queue dispatch rate-limited-lsa 30queue dispatch incoming
To limit the number of continuous incoming events processed, use the queue dispatch incoming command in router configuration mode. To return to the system default value, use the no form of this command.
queue dispatch incoming count
no queue dispatch incoming
Syntax Description
Command Default
The default incoming count is 300 packets (when the count is not configured).
Command Modes
Router configuration
Command History
Release ModificationRelease 3.6.2
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to limit the number of continuous incoming events processed to 30:
RP/0/RP0/CPU0:router(config-ospf)# queue dispatch incoming 30Use the show ospf message-queue command to see the queue dispatch values, peak lengths, and limits.
queue dispatch spf-lsa-limit
To change the maximum number of Type 3-4 and Type 5-7 link-state advertisements (LSAs) processed per shortest path first (SPF) run, use the queue dispatch spf-lsa-limit command in router configuration mode. To return to the system default value, use the no form of this command.
queue dispatch spf-lsa-limit count
no queue dispatch spf-lsa-limit
Syntax Description
count
Maximum number of continuous Type 3-4 and Type 5-7 LSAs processed per SPF in each scheduled run. Range is 30 to 3000.
Defaults
The default number of Type 3-4 and Type 5-7 processed per run is 150 LSAs (when this command is not configured).
Command Modes
Router configuration
Command History
Release ModificationRelease 3.6.2
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to limit the number of continuous Type 3-4 and Type 5-7 LSAs processed by SPF per scheduling run, to 100:
RP/0/RP0/CPU0:router(config-ospf)# queue dispatch spf-lsa-limit 100Implementing LDP-IGP Synchronization Enhancements for OSPF
•
LDP-IGP Synchronization Enhancements for OSPF
•
Information About LDP-IGP Synchronization Enhancements for OSPF
•
Restrictions for LDP-IGP Synchronization Enhancements for OSPF
•
LDP-IGP Synchronization Enhancements for OSPF: New or Changed Commands
LDP-IGP Synchronization Enhancements for OSPF
With this feature, Interior Gateway Protocol (IGP) advertises maximum metric over a link on which LDP synchronization is enabled until the LDP session on the corresponding link is up and has converged. This is referred to as synchronization. This ensures that the link chosen is the one least used unless it is the only available path for forwarding both IP and MPLS traffic until LDP has exchanged labels over the link. This avoids "black-holing" of multilabel traffic such as virtual private networks (VPN) traffic, which can occur when outbound label information is unavailable.
Information About LDP-IGP Synchronization Enhancements for OSPF
This feature is supported on both the Cisco CRS-1 router and the Cisco XR 12000 Series Router.
LDP-IGP synchronization is enabled under OSPF and IS-IS. However, the CLI changes being introduced in the current release affect OSPF protocol only.
Restrictions for LDP-IGP Synchronization Enhancements for OSPF
Under IS-IS, this feature supports an IPv4 unicast topology, while under OSPF, it supports an IPv4 unicast VRF-default topology.
LDP-IGP Synchronization Enhancements for OSPF: New or Changed Commands
This feature affects the following commands:
•
mpls ldp igp sync delay (LDP)
mpls ldp sync-igp-shortcuts
To enable LDP-IGP synchronization shortcuts in an MPLS network, use the mpls ldp sync-igp-shortcuts command in the appropriate OSPF configuration mode. To return to the default behavior, use the no form of this command.
mpls ldp sync-igp-shortcuts [disable]
no mpls ldp sync-igp-shortcuts
Syntax Description
Defaults
No default behavior or values
Command Modes
OSPF interface configuration
OSPF router configuration
OSPF area configurationCommand History
Release ModificationRelease 3.5.4
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
Release 3.6.2
No modifications.
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to enable LDP-IGP synchronization shortcuts under OSPF interface configuration, using the mpls ldp sync-igp-shortcuts command on a tunnel-te interface. However, the command applies to all interfaces under the applicable configuration mode.
RP/0/RP0/CPU0:router(config)# router ospf 100RP/0/RP0/CPU0:router(config-ospf)# area 0RP/0/RP0/CPU0:router(config-ospf-ar)# interface tunnel-te 1RP/0/RP0/CPU0:router(config-ospf-ar-if)# mpls ldp sync-igp-shortcutsshow mpls ldp igp sync
The tunnel-te interface was added as a new interface type available to the existing show mpls ldp igp sync command.
show mpls ldp igp sync [interface {tunnel-te {tunnel-range}}]
debug mpls ldp igp sync
The tunnel-te interface was added as a new interface type available to the existing debug mpls ldp igp sync command.
debug mpls ldp igp sync [interface type instance] [location node-id]
mpls ldp igp sync delay (LDP)
To configure an LDP-IGP synchronization delay within an MPLS network, use the mpls ldp igp sync delay command in global configuration mode. To return to the default behavior, use the no form of this command.
mpls ldp igp sync delay delay-time
no mpls ldp igp sync delay delay-time
Syntax Description
show ospf interface
The show ospf interface command output now includes the new interface type tunnel-te.
show ospf instance-name interface [type interface-path-id]
The following example shows the new output information for the show ospf interface command:
RP/0/0/CPU0:router# show ospf 1 interface tunnel-te 1tunnel-te1 is up, line protocol is upInternet Address 0.0.0.0/0, Area 0Process ID 1, Router ID 192.168.0.11, Network Type POINT_TO_POINT, Cost: 33LDP Sync IGP-shortcuts Enabled, Sync Status: Not AchievedInterface is a tunnel igp-shortcutTransmit Delay is 1 sec, State POINT_TO_POINT,Timer intervals configured, Hello 10, Dead 40, Wait 0, Retransmit 5No Hellos (Passive interface)Index 0/0, flood queue length 0Next 0(0)/0(0)Last flood scan length is 0, maximum is 0Last flood scan time is 0 msec, maximum is 0 msecNeighbor Count is 0, Adjacent neighbor count is 0Suppress hello for 0 neighbor(s)Multi-area interface Count is 0
MPLS Traffic Engineering and Fast-Reroute Enhancements on OSPF
MPLS Traffic Engineering (MPLS-TE) and Fast Reroute (FRR) features supported in Cisco IOS XR Software Release 3.6.2 allow the IGP-area in which constraint-based shortest path first (CSPF) is performed to be specified in tunnel configuration.
In conjunction with the support of 25 IGP areas, there are no longer hard limits on the number of adjacencies permitted on a single link.
Restrictions for MPLS Traffic Engineering and Fast-Reroute Enhancements on OSPF
Only point-to-point interfaces are supported for OSPF multiple adjacencies. These may be either native point-to-point (P2P) interfaces or broadcast interfaces on which the OSPF P2P configuration command is applied to force them to behave as P2P interfaces as far as OSPF is concerned. This restriction does not apply to IS-IS.
Note
The tunnel-te interface is not supported under IS-IS.
Summary Steps
1.
configure
2.
interface type interface-path-id
3.
path-option {preference-priority | protecting preference-priority}{dynamic [isis | lockdown | ospf | pce] | explicit {identifier path-number | name name} [isis | lockdown | ospf | verbatim]} area area-id
4.
Repeat Step 3. as many times as needed.
5.
end
or
commitDetailed Steps
Example
CSPF areas are configured on a per-path-option basis, as illustrated below. This example demonstrates the use of a traffic-engineering tunnels (tunnel-te) interface for this purpose. The show mpls traffic-eng tunnels command in the following example provides sample output for the active path in MPLS traffic engineering tunnel.
RP/0/RP0/CPU0:router(config)# configRP/0/RP0/CPU0:router(config)# interface tunnel-te 0RP/0/RP0/CPU0:router(config-if)# path-option 1 explicit id 6 ospf 126 area 0RP/0/RP0/CPU0:router(config-if)# path-option 2 explicit name 234 ospf 3 area 7 verbatimRP/0/RP0/CPU0:router(config-if)# path-option 3 dynamic isis mtbf level 1 lockdownRP/0/RP0/CPU0:router(config-if)# commitRP/0/RP0/CPU0:router(config-if)# exitRP/0/RP0/CPU0:router(config)# exitRP/0/RP0/CPU0:router# show mpls tr tu 1Name: tunnel-te1 Destination: 103.0.0.3Status:Admin: up Oper: up Path: valid Signalling: connectedpath option 1, type dynamic (Basis for Setup, path weight 2)OSPF 0 area 0G-PID: 0x0800 (derived from egress interface properties)Config Parameters:Bandwidth: 9001 kbps (CT0) Priority: 7 7 Affinity: 0x0/0xffffMetric Type: TE (default)AutoRoute: disabled LockDown: disabledLoadshare: 0 equal loadsharesAuto-bw: disabled(0/0) 0 Bandwidth Requested: 9001Direction: unidirectionalEndpoint switching capability: unknown, encoding type: unassignedTransit switching capability: unknown, encoding type: unassignedHistory:Tunnel has been up for: 4d19hCurrent LSP:Uptime: 4d19hPrior LSP:ID: path option 1 [10]Removal Trigger: path verification failedPath info (ospf 0 area 0):Hop0: 11.0.0.1Hop1: 11.0.0.2Hop2: 11.4.4.2Hop3: 11.4.4.3Hop4: 103.0.0.3
Implementing MPLS Traffic Engineering Shared-Risk Link Group (SRLG)
•
MPLS Engineering Shared-Risk Link Group (SRLG)
•
How to Configure MPLS Traffic Engineering Shared-Risk Link Groups
•
Prerequisites for MPLS Traffic Engineering Shared-Risk Link Groups
•
Restrictions for MPLS Traffic Engineering Shared-Risk Link Groups
•
Configuring the SRLG Membership of Each Link That Has a Shared Risk with Another Link
•
MPLS SRLG-Related Command Reference Information
MPLS Engineering Shared-Risk Link Group (SRLG)
The term shared-risk link groups (SRLG) refers to situations in which links in a network share a common fiber (or a common physical attribute). If one link fails, other links in the group may fail too. Links in the group have a shared risk.
The MPLS traffic engineering SRLG feature enhances backup tunnel path selection, so that a backup tunnel does not use links that are in the same SRLG as the interfaces the backup tunnel is protecting. Otherwise, when the protected link fails, the backup tunnel fails too.
There are two ways to avoid a backup tunnel using the same links in the SRLG as its protected interface:
•
The router does not create the backup tunnel unless it avoids SRLGs of the protected interface.
•
The router tries to avoid SRLGs of the protected interface but, if that fails, the router creates the backup tunnel anyway. In this case, there are two explicit paths. The first explicit path tries to avoid the SRLGs of the protected interface. If that does not work, the backup tunnel uses the second path, which ignores SRLGs.
Intermediate System-to-Intermediate System (IS-IS) floods the SRLG membership information (including other TE link attributes such as bandwidth availability and affinity), so that all routers in the network have the SRLG information for each link. With this topology information, routers can compute backup tunnel paths that exclude links having SRLGs in common with their protected interfaces.
How to Configure MPLS Traffic Engineering Shared-Risk Link Groups
Note
The current implementation of this MPLS feature requires a dual operating system approach in your network.
To activate the MPLS traffic engineering SRLG feature, perform the following tasks:
•
Configure the SRLG membership of each link that has a shared risk with another link. See "Configuring the SRLG Membership of Each Link That Has a Shared Risk with Another Link" in the current document.
•
Configure the router acting as a point of local repair (PLR) in the network to automatically create backup tunnels that avoid the SRLGs of the protected interfaces. See the Cisco IOS Software documentation "Configuring the Routers That Automatically Create Backup Tunnels to Avoid SRLGs of Their Protected Interfaces" under MPLS Traffic Engineering: Shared Risk Link Groups (SRLG) for Cisco IOS Software Release 12.0S at http://www.cisco.com/en/US/docs/ios/12_0s/feature/guide/fs29srlg.html .
Prerequisites for MPLS Traffic Engineering Shared-Risk Link Groups
•
To be able to set up auto-tunnels, you must have one router in the network in which you intend to use this feature configured as a point of local repair (PLR), and the router must be running
Cisco IOS, Release 12.0 S.Restrictions for MPLS Traffic Engineering Shared-Risk Link Groups
•
Cisco IOS XR MPLS-TE does not currently support auto-tunnels.
Configuring the SRLG Membership of Each Link That Has a Shared Risk with Another Link
Configure the SRLG membership of each link that has a shared risk with another link by completing the following task.
Note
You may configure up to eight SRLGs per interface.
SUMMARY STEPS
1.
configure
2.
mpls traffic-eng
3.
interface type interface-path-id
4.
srlg membership-number
5.
end
or
commitDETAILED STEPS
MPLS SRLG-Related Command Reference Information
•
Enhanced show Commands for MPLS SRLG
New Commands
This release introduces the following new command.
srlg
To configure an MPLS traffic engineering shared-risk link group (SRLG) membership for a link on a given interface, use the srlg command in MPLS-TE interface configuration mode. To disable this configuration, use the no form of this command.
srlg membership-number
no srlg membership-number
Syntax Description
Command Default
No default behavior or values
Command Modes
MPLS-TE interface configuration
Command History
Release ModificationRelease 3.6.2
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to configure an SRLG:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# mpls traffic-eng
RP/0/RP0/CPU0:router(config-mpls-te)# interface POS 0/3/0/2
RP/RP0/RP0/CPU0:router(config-mpls-te-if)# srlg 10Enhanced show Commands for MPLS SRLG
Several existing show commands were updated with the following new output fields to support MPLS SRLG:
•
show mpls traffic-eng link-management advertisements
•
show mpls traffic-eng link-management interface
•
show mpls traffic-eng topology
show isis data verbose
The following new fields, described here, are displayed in boldface in the following example:
–
MPLS SRLG—Neighbor hostname or system ID.
–
Interface IP Address—Local interface IP address.
–
Neighbor IP Address—Remote interface IP address.
–
Flags—Flags carried in SRLG TLV. The LSB (Least Significant Bit) is set if the interface is numbered.
–
SRLGs—SRLG values.
RP/0/RP0/CPU0:router# show isis database sanjose verboseIS-IS test (Level-1) Link State DatabaseLSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OLsanjose.00-00 * 0x00000c07 0xfbec 1093 0/0/0Area Address: 00Area Address: 01NLPID: 0xccNLPID: 0x8eMT: Standard (IPv4 Unicast)MT: IPv6 Unicast 0/0/0MT: IPv4 Multicast 0/0/0MT: IPv6 Multicast 0/0/0Hostname: boxsterIP Address: 192.168.0.145IPv6 Address: 192:168::145Router ID: 192.168.0.145Metric: 10 IS-Extended raleigh.01Metric: 10 IS-Extended sanjose.00Metric: 10 IS-Extended sanjose.00Affinity: 0x00000000Interface IP Address: 10.3.11.145Neighbor IP Address: 10.3.11.143Physical BW: 155520 kbits/secReservable Global pool BW: 0 kbits/secGlobal Pool BW Unreserved:[0]: 0 kbits/sec [1]: 0 kbits/sec[2]: 0 kbits/sec [3]: 0 kbits/sec[4]: 0 kbits/sec [5]: 0 kbits/sec[6]: 0 kbits/sec [7]: 0 kbits/secMPLS SRLG: sanjose.00Interface IP Address: 10.3.11.145Neighbor IP Address: 10.3.11.143Flags: 0x1SRLGs:[0]: 10, [1]: 20Metric: 10 IP-Extended 10.1.5.0/24Metric: 10 IP-Extended 10.3.10.0/24Metric: 10 IP-Extended 10.3.11.0/24Metric: 10 IP-Extended 11.0.1.0/24Metric: 10 IP-Extended 192.168.0.145/32Metric: 10 MT (IPv6 Unicast) IS-Extended raleigh.01Metric: 10 MT (IPv6 Unicast) IS-Extended sandiego.03Metric: 10 MT (IPv6 Unicast) IS-Extended sanjose.00Metric: 10 MT (IPv6 Unicast) IPv6 10:1:5::/64Metric: 10 MT (IPv6 Unicast) IPv6 10:3:10::/64Metric: 10 MT (IPv6 Unicast) IPv6 11:0:1::/64Metric: 10 MT (IPv6 Unicast) IPv6 192:168::145/128Metric: 10 MT (IPv4 Multicast) IS-Extended raleigh.01Metric: 10 MT (IPv4 Multicast) IS-Extended sandiego.03Metric: 10 MT (IPv4 Multicast) IS-Extended sanjose.00Metric: 10 MT (IPv4 Multicast) IP-Extended 10.1.5.0/24Metric: 10 MT (IPv4 Multicast) IP-Extended 10.3.10.0/24Metric: 10 MT (IPv4 Multicast) IP-Extended 11.0.1.0/24Metric: 10 MT (IPv4 Multicast) IP-Extended 192.168.0.145/32Metric: 10 MT (IPv6 Multicast) IPv6 10:3:11::/64Metric: 10 MT (IPv6 Multicast) IPv6 192:168::145/128show mpls traffic-eng link-management advertisements
The following new field, described here, is displayed in boldface in the following example:
•
SRLGs—SRLG values advertised for the link.
RP/0/RP0/CPU0:router# show mpls traffic-eng link-management advertisementsFlooding Status : readyLast Flooding : 50 seconds agoLast Flooding Trigger : TE Link came UpNext Periodic Flooding In : 70 secondsDiff-Serv TE Mode : Not enabledConfigured Areas : 1IGP Area[1]:: IS-IS test level 1Flooding Protocol : IS-ISIGP System ID : 0000.0000.0010MPLS TE Router ID : 192.168.0.145Flooded Links : 1Link ID:: 0 (POS0/3/0/3)Link IP Address : 10.3.11.145O/G Intf ID : 3Neighbor : ID 0000.0000.0234.00, IP 10.3.11.143TE Metric : 10IGP Metric : 10Physical BW : 155520 kbits/secBCID : RDMMax Reservable BW : 0 kbits/secRes Global BW : 0 kbits/secRes Sub BW : 0 kbits/secSRLGs : 10, 20Downstream::Global Pool Sub Pool----------- -----------Reservable BW[0]: 0 0 kbits/secReservable BW[1]: 0 0 kbits/secReservable BW[2]: 0 0 kbits/secReservable BW[3]: 0 0 kbits/secReservable BW[4]: 0 0 kbits/secReservable BW[5]: 0 0 kbits/secReservable BW[6]: 0 0 kbits/secReservable BW[7]: 0 0 kbits/secAttribute Flags: 0x00000000show mpls traffic-eng link-management interface
The following new field, described here, is displayed in boldface in the following example:
•
SRLGs—SRLG values configured for the link.
RP/0/RP0/CPU0:router# show mpls traffic-eng link-management interface pos 0/3/0System Information::Links Count : 1 (Maximum Links Supported 100)Link ID:: POS0/3/0/3 (10.3.11.145)Local Intf ID: 3Link Status:Link Label Type : PSC (inactive)Physical BW : 155520 kbits/secBCID : RDMMax Reservable BW : 0 kbits/sec (reserved: 100% in, 100% out)BC0 (Res. Global BW): 0 kbits/sec (reserved: 100% in, 100% out)BC1 (Res. Sub BW) : 0 kbits/sec (reserved: 100% in, 100% out)SRLGs : 10, 20MPLS TE Link State : MPLS TE on, RSVP on, admin-upInbound Admission : allow-allOutbound Admission : allow-if-roomIGP Neighbor Count : 1Max Res BW (RDM) : 0 kbits/secBC0 (RDM) : 0 kbits/secBC1 (RDM) : 0 kbits/secMax Res BW (MAM) : 0 kbits/secBC0 (MAM) : 0 kbits/secBC1 (MAM) : 0 kbits/secAttributes : 0x0Admin Weight : 1 (OSPF), 10 (ISIS)Neighbors :ID 0000.0000.0234.00, IP 10.3.11.143 (Up)Flooding Status: (1 area)IGP Area[1]: IS-IS test level 1, floodedshow mpls traffic-eng topology
The following new field, described here, is displayed in boldface in the following example:
•
SRLG—SRLG values flooded by IGPs to TE.
RP/0/RP0/CPU0:router# show mpls traffic-eng topology 192.168.0.145 briefIGP Id: 0000.0000.0010.00, MPLS TE Id: 192.168.0.145 Router Node (ISIS test level-1)Link[0]:Point-to-Point, Nbr IGP Id:0000.0000.0234.00, Nbr Node Id:4, gen:5Frag Id:0, Intf Address:10.3.11.145, Intf Id:0Nbr Intf Address:10.3.11.143, Nbr Intf Id:0TE Metric:10, IGP Metric:10, Attribute Flags:0x0SRLGs: 10, 20Switching Capability:, Encoding:BC Model ID:RDMPhysical BW:155520 (kbps), Max Reservable BW Global:0 (kbps)Max Reservable BW Sub:0 (kbps)Using MPLS Tunnel Drop Counts to Display Drop or Error Packets on MPLS TE Interfaces
Two new fields displaying drop and error packets were added to the output of the show interfaces tunnel-te command, which runs only on the Cisco CRS-1 router.
show interfaces tunnel-te
To verify whether or not there are drop or error packets on MPLS traffic engineering (TE) tunnel interfaces, use the show interfaces tunnel-te command in EXEC mode.
show interfaces tunnel-te tunnel-number
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
The show interfaces tunnel-te command, which runs only on the Cisco CRS-1 router, was modified by the addition of two new fields, drop counter and error counter.
Note
FRR drops cannot account for the total packet loss seen end-to-end during FRR. Rather, the command output accounts only for packets dropped by the forwarding path, because the software is programmed to recognize that the primary interface is down and that the backup is not on the same line card.
Field Descriptions
Field1 Descriptiondrop counter
Displays dropped packets that result from oversubscription of the egress link hosting the TE-tunnel in an MPLS network
error counter
Displays packets dropped during a fast-reroute (FRR) on the line card hosting the primary TE tunnel in an MPLS network.
1 These are not the names of the fields, but rather their purpose.
Task ID
Examples
The following example shows sample output from the show interfaces tunnel-te command with the newly added information in boldface:
RP/0/RP0/CPU0:router# show interfaces tunnel-te 1RP/0/RP0/CPU0:router# tunnel-te1 is down, line protocol is downInterface state transitions: 1Hardware is Tunnel-TEInternet address is UnknownMTU 1500 bytes, BW 0 Kbitreliability 255/255, txload Unknown, rxload UnknownEncapsulation TUNNEL, loopback not set,Last clearing of "show interface" counters never5 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 0 bits/sec, 0 packets/sec0 packets input, 0 bytes, 0 total input drops0 drops for unrecognized upper-level protocolReceived 0 broadcast packets, 0 multicast packets0 packets output, 0 bytes, 0 total output dropsOutput 0 broadcast packets, 0 multicast packets0 output errorsNew and Enhanced Fabric Diagnostic Tests
The following new functionality is being introduced with the current release:
•
Fabric Diagnostic Test—Enhancement of the existing test.
•
Fabric Multicast Diagnosis Test—A new fabric diagnostic test for multicast networks.
Fabric Diagnostic Test
A nondisruptive, fault isolation test that "unicast pings" each RP/LC/DRP node in a chassis from the standby RP node using a unicast address. The test steers unicast ping test packets through different fabric planes, aggregates unicast ping (pass or fail) results with fabric plane information, analyzes these results, and points out the most logical point of failure (if any) in the chassis. The test can be executed only from the standby RP as one of the following test types:
•
On demand
•
Scheduled
•
Configured to monitor health
Executing this test in a Cisco CRS-1 multishelf system may help determine which fabric stage (S1, S2, or S3) is the most logical point of failure for unicast 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 the fabric chassis of the system.
Fabric Multicast Diagnosis Test
Added for multicast networks in Release 3.6.2, this nondisruptive, fault isolation test that "multicast pings" each RP/LC/DRP node in a chassis from the standby RP node using a multicast address. The test steers multicast ping test packets through different fabric planes, aggregates multicast ping (pass or fail) results with fabric plane information, analyzes these results, and points out the most logical point of failure (if any) in the chassis. The test can be executed only from the standby RP as one of the following test types:
•
On demand
•
Scheduled
•
Configured to monitor health
Executing this test in a Cisco CRS-1 multishelf system may help determine which fabric stage (S1, S2, or S3) is the most logical point of failure for multicast 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 the fabric chassis of the system.
Important Notes
•
Country-specific laws, regulations, and licences—In certain countries, use of these products may be prohibited and subject to laws, regulations, or licenses, including requirements applicable to the use of the products under telecommunications and other laws and regulations; customers must comply with all such applicable laws in the countries in which they intend to use the products.
•
Migrating from Cisco IOS to Cisco IOS XR Software on the Cisco XR 12000 Series Router—When migrating a Cisco XR 12000 Series Router from Cisco IOS to Cisco IOS XR software, follow the instructions provided in Migrating from Cisco IOS to Cisco IOS XR Software on the Cisco XR 12000 Series Router, Release 3.6.
•
Card, fan controller, and RP removal—For all card removal and replacement (including fabric cards, line cards, fan controller, and RP) follow the instructions provided by Cisco to avoid impact to traffic. See the Cisco IOS XR Getting Started Guide for procedures.
•
Exceeding Cisco testing—If you intend to test beyond the combined maximum configuration tested and published by Cisco, contact your Cisco Technical Support representative to discuss how to engineer a large-scale configuration maximum for your purpose.
•
More power required for Cisco SIP-600 line cards on the Cisco XR 12000 Series Router—These line cards draw more power than the previous ones. Depending on the exact configuration of power entry modules (PEMs) and other cards in the chassis, there may not be enough power available when inserting a new card or removing a PEM. Before you insert a new card or remove a PEM, run the following command in admin mode:
RP/0/0/CPU0:router# adminRP/0/0/CPU0:router# show environment power-supply table48V CurrentR/S/I Module (V) (A)0/24/* PEM1 54 4PEM2 53 40/25/* PEM1 54 4PEM2 53 4Total Power Supplies: 3200WRedundant Power Supplies: 1600WWorst Case Power Used: 621WCurrent Power Used: 428WCurrent Redundant Power Available: 1172WCurrent Total Power Available: 2772WWorst Case Redundant Power Available: 979WWorst Case Total Power Available: 2579WPID Description Watts--- ----------- -----GRP-B Route Processor 38PRP-1 Cisco 12000 Series Performance Route Processor 60LC-4OC-3-POS-SM 4 Port Packet Over SONET OC-3c/STM-1 804OC3X/POS-MM-MJ-B 4 port ISE OC3 90...If you plan to insert a new card, locate the entry for the card to be inserted and note the power consumed by it. If this power is less than the figure given in Worst Case Redundant Power Available (the figure is displayed in the show environment power-supply table command output), the card can be safely inserted. As long as the Worst Case Redundant Power Available is not zero, a PEM can be powered down for replacement without impact.
Note
No alerts are issued if more cards are inserted than the PEMs can support. It is your responsibility to determine your power budget for the chassis before making any changes to it. Exceeding the power budget may result in the PEM being overloaded and cards powering down due to insufficient power being provided.
•
Per-interface Internet Control Message Protocol (ICMP) disable feature is not supported on Cisco XR 12000 Series Routers.
•
Disable the preempt feature in the VFW application—In all Cisco IOS XR 3.6 releases, you must disable the preempt feature in the VFW application. Ensure that you use the no preempt command for all fault-tolerant groups under the Admin context on the VFW application. See the following example:
ft group 1peer 1no preemptassociate-context ctx1inservice•
Online Diagnostics is not supported on the Cisco XR 12000 Series Router—If you execute the diagnostic command, an error appears stating that there is no online diagnostics process running on the router.
•
rp mgmtethernet forwarding command—This command is not supported on the Cisco XR 12000 Series Router.
Minimum Flash Disk Requirements When Upgrading to Release 3.6.2
•
Cisco CRS-1—As of Cisco IOS XR Release 3.6.2, the Cisco CRS-1 router supports an upgrade from the 1-GB flash disk to either a 2-GB or 4-GB flash disk. It is not, however, a requirement unless you are upgrading from Cisco IOS XR Software Release 3.5.4.
Note
If you are upgrading from Release 3.5.4 to Release 3.6.2, you must, at minimum, upgrade to 2 GB of flash memory.
It is recommend that, before you upgrade from Cisco IOS XR Software Release 3.5.4 to Cisco IOS XR Software Release 3.6.2, you install all recommended Release 3.5.4 SMUs.
Be aware that an installation of Cisco IOS XR Software Release 3.6.2, with all optional packages installed, requires at least 450 MB of free flash disk memory. For this reason, make sure that you have enough free space available before you try to upgrade to Release 3.6.2.
Tip
Cisco CRS-1 platform customers should consider upgrading to 4-GB flash disk memory before installing Cisco IOS XR Software Release 3.6.2. An upgrade of the flash disk memory to 2 GB or more is required in Cisco IOS XR Software Release 3.7.0. However, because more than 2 GB of flash memory may be required in later releases, upgrading now to 4 GB of flash memory saves you this effort in future.
•
Cisco XR 12000 Series Router—Starting with Cisco IOS XR Software Release 3.6.0, an upgrade from the 1-GB to 2-GB flash memory is required on the Cisco XR 12000 Series Router.
Table 7 specifies the Cisco IOS XR releases when the flash memory upgrade is mandatory for the Cisco CRS-1 router and the Cisco XR 12000 Series Router.
.
Table 7 Cisco IOS XR Releases Requiring a Mandatory Upgrade in Flash Memory
Platform Release 3.5.41(min.) Release 3.6.01(min.) Release 3.6.21(min.) Release 3.7.01(min.) Release 3.81(min.)Cisco CRS-1
2-GB2
2 GB3
2 GB
2 GB
Cisco XR 12000 Series Router
2 GB
2 GB
2 GB
2 GB
1 Supports 2- and 4-GB flash disk memory on both platforms.
2 Upgrade to 2 GB or 4 GB of flash disk memory is only compulsory if you are upgrading from Release 3.4.0.
3 Upgrade to 2 GB or 4 GB of flash disk memory is only compulsory if you are upgrading from Release 3.5.4. An upgrade from any other previous release does not require this.
The flash disk size of a Cisco CRS-1 router or Cisco XR 12000 Series Router running Cisco IOS XR Software Release 3.4.0, Release 3.5.0, or Release 3.6.1 can be either 1 GB, 2 GB, or 4 GB.
Note
The flash disk size upgrade from 2 GB to 4 GB is also supported for Cisco IOS XR Software Release 3.4.0 and Release 3.5.0 for both router platforms, with the following restriction: Cisco IOS XR Software Release 3.4.0 and Release 3.5.0 are not capable of showing the 4-GB flash disk and it appears as though only a 2-GB Flash Disk were present. As of Cisco IOS XR Software Release 3.6.0, the 4-GB flash disks appear as two 2-GB partitions.
For details about these flash disks, including the upgrade procedure for both platforms, see the flash disk upgrade instructions at:
http://www.cisco.com/en/US/docs/routers/xr12000/xr_line_cards/flashdisk/flashdisk.pdf.
Activation Requirements for the Cisco CRS-1 Multishelf System Encryption PIE
Previously the Cisco CRS-1 multishelf system encryption PIE was installed and activated when you ordered the Cisco IOS XR IP/MPLS Core Software 3DES image.
With this release, you must explicitly activate the Cisco IOS XR IP/MPLS Core Software 3DES image [hfr-k9sec-p.pie-3.6.2, PID is XC-RPK9-03.06], by following these instructions:
Caveats
Caveats describe unexpected behavior in Cisco IOS XR software releases. Severity-1 caveats are the most serious.
Open Caveats—Release 3.6.2
This section lists the caveats for Cisco IOS XR Software Release 3.6.2:
•
Cisco CRS-1 and Cisco XR 12000 Series Router Caveats
•
Caveats Specific to the Cisco CRS-1 Router
•
Caveats Specific to the Cisco XR 12000 Series Router
Cisco CRS-1 and Cisco XR 12000 Series Router Caveats
The following caveats apply to both platforms:
•
CSCeg39062
Basic Description:
Using FTP to install packages may result in incorrect parsing of the FTP URL. URLs that have multiple slashes may be sent to the server as a relative path instead of an absolute path.
Conditions:
Use of a path such as ftp://username:password@server//directory/file normally initiates an attempt to download /directory/file from the server. However, due to incorrect parsing, an attempt is actually made to download $HOME/directory/file instead.
Workaround:
Two possible workarounds exist:
–
Locate the target file in the user's home directory, so that it can be accessed through a relative path. Use of syntax such as the following solves the problem illustrated under "Conditions," and the command operates correctly, because it looks for a relative file location:
ftp://username:password@server/directory/file downloads $HOME/directory/file–
Use alternative transport mechanism, such as TFTP.
•
CSCso79938
Basic Description:
SNMP traps such as coldStart, warmStart are missing.
Detailed Problem Description:
At startup, the SNMP agent uses information in RIB to identify whether configured SNMP trap recipients are reachable. After the SNMP agent detects them as reachable, the SNMP agent forwards traps generated by various MIB DLLs.
Availability of the route does not guarantee reachability to destination. FIB should have updated its forwarding path by performing an ARP, so that traps generated from the SNMP agent reach their destination. This fails to occur, however, and traps generated by the SNMP agent do not reach their destinations.
Conditions:
System reload or switchover of the active controller card.
Workaround:
None.
Generating a few packets to destination would cause the necessary forwarding agent to trigger an ARP for those packets, and that would result in the complete setup of Layer 2 adjacencies. In this case, the SNMP agent would execute ICMP PING to the configured trap destination before commencing SNMP trap forwarding.
•
CSCsl29159
Basic Description:
The netio process crashes while enabling debug commands with ACL filter.
Symptom:
Sometimes, the netio process terminates abnormally when debug cef command with acl filter is used.
Conditions:
The problem occurs when the user enables debug cef packet ipv4acl and there is slowpathipv6 traffic being switched.
Workaround:
Specify the afi filter to the debug cef command that matches the type of debug acl being supplied to the debug command.
For example, use the commands in the following formats:
–
debug cef ipv4 packet [level<n>] ipv4acl
Or
–
debug cef ipv6 packet [level <n>] ipv6acl
•
CSCsq09232
Basic Description:
Connection to TACACS lost on RP failover.
Symptom:
After RP failover, a pre-existing exec (telnet) user is unable to execute any command. The issue is not seen consistently. However whenever it occurs, the EXEC user is not allowed to execute any command.
Conditions:
After RP failover when the EXEC session is replicated, it initiates an Interprocess Communications (IPC) connection to the locald process. This connection attempt fails at times, if locald is still not available. This could have happened if the system and thereby locald is still initializing. In such a case, if command authorization is configured, EXEC is unable to verify authorization for the command (as no channel is available to communicate request to locald). As such, the user is denied permission to execute the command.
Workaround:
Exit from the session and log in again.
Caveats Specific to the Cisco CRS-1 Router
•
CSCsr49786
Basic Description:
LPTS application (lpts_pa) runs out of its allocated pool of Fabric Group Identifiers (FGIDs) and is not able to allocate any new FGIDs.
Symptom:
When this problem is observed, LPTS client applications, services, or protocols may stop functioning correctly. For example, protocols such as PIM, OSPF, or BGP that execute on the RP may not be able to establish neighborships or receive packets.
This may be seen following an RP failover event.
Conditions:
LPTS may hit its FGID limit after several RP failovers. The number of RP failovers required to hit this max limit depends on the number of FGIDs allocated by LPTS. To see the allocation, use the administration-level command show controller fabric fgid stat pool detail | beg LPTS.
In the sample output below, the InUse FGIDs is 512:
Pool Name is LPTSPool type is DedicatedThe starting FGID of this pool is 11264Total FGIDs of this pool is 32768InUse FGIDs of this pool is 512High Water Mark InUse FGIDs of this pool is 512The following example shows the state observed if this issue is encountered:
Pool Identifier is 1Pool Name is LPTSPool type is DedicatedThe starting FGID of this pool is 11264Total FGIDs of this pool is 32768InUse FGIDs of this pool is 32768High Water Mark InUse FGIDs of this pool is 0
Because the InUse FGID value equals the Total FGID value, no further FGIDs can be allocated.
Workaround:
Periodically restart the lpts_pa process on the active RP with the command process restart lpts_pa to ensure that FGIDs are available. The lpts_paprocess can be restarted without any impact to services. If the issue has been encountered, restarting lpts_pa can be used to recover from the situation.
•
CSCsl09040
Basic Description:
If a class has bandwidth remaining percent 0 configured, that class may receive more bandwidth than the minimum bandwidth configured in that class.
Conditions:
This behavior is observed in classes where bandwidth remaining percent 0 has been configured.
Workaround:
Configure shape bandwidth to be the same as minimum bandwidth of that class.
•
CSCsu63356
Basic Description:
Copying a very large prefix set, or a configuration with a very large prefix set, to the running configuration takes 30 minutes or more due to the prefix set verification process. The larger the prefix list, the more time it takes.
Conditions:
This condition is seen under the following circumstances:
–
When applying a very large prefix list to running configuration.
–
When rolling back the configuration after the prefix list has been deleted.
Workaround:
None.
•
CSCsl67014
Basic Description:
Sometimes, exec process is terminated when describe CLI commands are used.
Symptom:
WD sysmon may terminate the exec process if there is a severe increase in CPU usage.
Conditions:
This symptom is observed on Cisco CRS-1 routers when using the command describe show tech-support or describe show screddrv standby.
Workaround:
None. However, this problem appears very rarely and there is no impact to the functionality of the router.
Caveats Specific to the Cisco XR 12000 Series Router
The following caveats are specific to the Cisco XR 12000 Series Router platform:
•
CSCsh50132
Basic Description:
Ace error messages appear and the traffic stops during spa-mix while sending IPSec and Clear IP Traffic over SPA-4XCT3/DS0 and SPA-IPSEC-2G.
Symptom:
Fails to process HAPI rx packet when spa-mix.
Conditions:
–
High rate traffic, over 600 Mpbs.
–
With spa-mix, when two IPSec SPA on the same linecard or IPSecSPA and other SPA types.
Workaround:
If the IPSec SPA is used at full rate (1 Gbps per direction), locate the other SPA on a separate line card.
•
CSCsk56789
Basic Description:
Bit error rate test (BERT) errors for the 3-in-24 pattern on the channel-group BERT for the 8-Port Channelized T1/E1 Shared Port Adapters (SPA).
Symptom:
Invoking BERT pattern 3-in-24 on the channel-group may result in BERT errors incrementing for the 8-Port Channelized T1/E1 SPA.
Conditions:
For the 8-Port Channelized T1/E1 SPA, invoking BERT pattern 3-in-24 on the channel-group may result in an increase in BERT errors.
Workaround:
None. There is no impact on the functionality of the system.
•
CSCsl58364
Basic Description:
After a physical OIR, the show environment command reports incorrect values for the services card.
Symptom:
After a physical OIR of the Services card, the temperature for that slot disappears (as seen in the show environment temperatures command).
Conditions:
After an OIR, the show temperature command does not display the temperature for the services card.
Workaround:
None.
•
CSCsl54803
Basic Description:
Before initiating field diagnostics, the user is not warned to remove the cabling from the linecard under test.
Symptom:
Unexpected interrupts while field diagnostics are in progress.
Conditions:
–
External cables are connected to the line card
–
Field diagnostics is initiated on the line card
Workaround:
Remove all external cables to the line card under test before initiating field diagnostics.
Upgrading Cisco IOS XR Software
Cisco IOS XR software is installed and activated from modular packages, allowing specific features or software patches to be installed, upgraded, or downgraded without affecting unrelated processes. Software packages can be upgraded or downgraded on all supported card types, or on a single card (node).
Software packages are installed from package installation envelope (PIE) files that contain one or more software components.
The following URL contains links to information about how to upgrade Cisco IOS XR software:
http://www.cisco.com/web/Cisco_IOS_XR_Software/index.html
Note
Refer to the "Minimum Flash Disk Requirements When Upgrading to Release 3.6.2" section for upgrade details.
Using a Software Maintenance Update (SMU)
A SMU is used as a software `patch' delivery unit that after installation and activation provides a `point-fix' for a critical issue in a given software release. The SMU consists of a SMU file and an associated caveat listing.
You should remember to periodically check the online SMU download page for new SMUs that may apply to your software release. Go to this URL and then click on IOS XR Software Maintenance Upgrades (SMU):
The following URL points to SMU FAQs to assist you with questions you may have regarding how and when to install SMUs for your release:
http://www.cisco.com/web/Cisco_IOS_XR_Software/pdf/SMU_FAQ.pdf
Troubleshooting
For information on troubleshooting Cisco IOS XR software, see the Cisco IOS XR Getting Started Guide and Cisco IOS XR Troubleshooting Guide.
Related Documentation
The following sections describe the documentation available for the Cisco CRS-1 and the Cisco XR 12000 Series Router. Documentation is available in the form of PDF and HTML files and is available on www.Cisco.com.
Use these release notes with the following documents:
Hardware Documents
To access the most current hardware documentation, go to:
Cisco CRS-1:
http://www.cisco.com/en/US/products/ps5763/tsd_products_support_series_home.html
Cisco XR 12000 Series Router:
http://www.cisco.com/en/US/products/ps6342/tsd_products_support_series_home.html
Software Documents
The Cisco IOS XR software documentation set includes the Cisco IOS XR software configuration guides and command references, as well as a getting started guide. For a full list, see About Cisco IOS XR Software Documentation for Release 3.6 for a list of Cisco IOS XR Software documentation for Release 3.6.0.
To access the most current software documentation, go to:
http://www.cisco.com/en/US/products/ps5845/tsd_products_support_series_home.html
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
CCDE, CCENT, Cisco Eos, Cisco HealthPresence, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0812R)
Copyright © 2009 Cisco Systems, Inc. All rights reserved



