Table Of Contents
Release Notes for Cisco IOS XR Software Release 3.5.4
Determining Your Software Version
New Software Features in Cisco IOS XR Software Release 3.5.4
Cisco CRS-1 and Cisco XR 12000 Series Router Platforms
Cisco CRS-1 Router-Specific Features Only
Cisco XR 12000 Series Router Services
New Hardware Features in Cisco IOS XR Software Release 3.5.4
DC-PEM and Fan Tray Modifications
Acoustic Levels Reduced on Two Chassis
Software Feature Documentation
Enhanced Tuning of SPF LSA Counts for OSPF Topology
LDP-IGP Synchronization Enhancements for OSPF
MPLS Traffic Engineering and Fast-Reroute Enhancements on OSPF
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
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco IOS XR Software Release 3.5.4
January 15, 2009
Cisco IOS XR Software Release 3.5.4
Text Part Number OL-17314-03
Please see the "Important Notes" section for important information on Cisco IOS XR Software Release 3.5.4.
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. See the "Obtaining Documentation and Submitting a Service Request" section for more information on obtaining Cisco documentation.
These release notes describe the features provided in Cisco IOS XR software for the current release and are updated as needed.
For a list of software caveats that apply to Cisco IOS XR software for the current release, 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:
•
Software Feature Documentation
•
•
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:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
–
–
–
–
•
•
•
See the "New and Changed Information" section for a detailed list of new features by platform for Cisco IOS XR software for the current release.
System Requirements
Cisco IOS XR Software Release 3.5.4 is supported on the following platforms:
To determine the software versions or levels of your current system, see the"Determining Your Software Version" section.
Cisco CRS-1 Router
This section describes the system requirements for Cisco IOS XR software for the current release supported on Cisco CRS-1 routers, and includes the following information:
To determine the software versions or levels of your current system, see Determining Your 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 features related to the current release. Table 1 and Table 2 list the Cisco IOS XR software feature set matrix and associated filenames available that are supported on the Cisco CRS-1 router in the current release.
Table 1 Cisco CRS-1 Supported Feature Sets (Cisco IOS XR Software Release 3.5.4 PIE Files)
Cisco IOS XR IP Unicast Routing Core Bundle
comp-hfr-mini.pie-3.5.4
Contains the required core packages, including OS, Admin, Base, Forwarding, Modular Services Card, Routing, SNMP Agent, and Alarm Correlation.
Cisco IOS XR IP Unicast Routing Core Bundle
comp-hfr-mini.vm-3.5.4
Contains the required core packages including, OS, Admin, Base, Forwarding, and Routing SNMP Agent, and Alarm Correlation.
Cisco IOS XR Manageability Package
hfr-mgbl-p.pie-3.5.4
Cisco IOS XR MPLS Package
hfr-mpls-p.pie-3.5.4
MPLS-TE,4 LDP,5 MPLS Forwarding, MPLS OAM,6 LMP,7 OUNI,8 RSVP,9 and Layer-2 and Layer-3 VPNs.
Cisco IOS XR Multicast Package
hfr-mcast-p.pie-3.5.4
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.5.4
Support for Encryption, Decryption, IPSec,16 SSH,17 SSL,18 and PKI.19
Cisco IOS XR Documentation Package
hfr-doc.pie-3.5.4
Manual pages for Cisco IOS XR CLI commands
Cisco IOS XR FPD Package
hfr-fpd.pie-3.5.4
Firmware for Fixed PLIM and SPA modules as well as ROMMON images for Cisco CRS-1 chassis.
Cisco IOS XR Diagnostic Package
hfr-diags-p.pie-3.5.4
Diagnostic utilities for running Cisco IOS XR software.
Cisco IOS XR Session Border Controller Package
hfr-sbc-p.pie-3.5.4
Session Border Controller package for a 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
Memory Requirements
Caution
The minimum memory requirements for Cisco CRS-1 routers running Cisco IOS XR software for the current release consist of the following:
•
•
Hardware Supported
Cisco IOS XR software for the current release supports Cisco CRS-1 routers. All hardware features are supported on 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 router and the minimum software versions required. See the "Other Firmware Code" section.
Software Compatibility
Cisco IOS XR software for the current release is compatible with the following Cisco CRS-1 systems:
•
•
•
Other Firmware Code
The following firmware code is supported by the Cisco CRS-1 router:
•
•
Cisco XR 12000 Series Router
This section describes the system requirements for Cisco IOS XR Software Release 3.5.4, supported on the Cisco XR 12000 Series Router, and includes the following information:
To determine the software versions or levels of your current system, see Determining Your Software Version.
Feature Set Table
Cisco IOS XR software is packaged in feature sets (also called software images). Each package contains a specific set of Cisco IOS XR software features related to the current release. Table 4 and Table 5 list the Cisco IOS XR software feature set matrix and associated filenames available for Cisco IOS XR Software Release 3.5.4, supported on the Cisco XR 12000 Series Router.
Table 4 Cisco XR 12000 Series Router Supported Feature Sets (Cisco IOS XR Software
Release 3.5.4 PIE Files)Cisco IOS XR IP Unicast Routing Core Bundle
c12k-mini.pie-3.5.4
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.5.4
Contains the required core packages including, OS, Admin, Base, Forwarding, and Routing SNMP Agent, and Alarm Correlation.
Cisco IOS XR Manageability Package
c12k-mgbl.pie-3.5.4
CORBA agent, XML Parser, and HTTP server packages.
Cisco IOS XR MPLS Package
c12k-mpls.pie-3.5.4
MPLS-TE, LDP, MPLS Forwarding, MPLS OAM, LMP, OUNI, and RSVP.
Cisco IOS XR Multicast Package
c12k-mcast.pie-3.5.4
Multicast Routing Protocols (PIM, MSDP, IGMP, Auto-RP, BSR), Tools (SAP, MTrace, MRINFO), and Infrastructure (MRIB, MURIB, MFWD).
Cisco IOS XR Security Package
c12k-k9sec.pie-3.5.4
Support for Encryption, Decryption, IPSec, SSH, SSL, and PKI.
Cisco IOS XR Standby RP Boot Image
mbiprp-rp.vm-3.5.4
Support for booting the Standby RP on a Cisco XR 12000 Series Router.
Cisco IOS XR Session Border Controller Package
c12k-sbc.pie-3.5.4
Session Border Controller Package for a Cisco XR 12000 Series Router.
Cisco IOS XR Service IPSec Controller Package
c12k-ipsec-service.pie-3.5.4
Support for service-ipsec and service-gre interfaces in Cisco IOS XR software.
Cisco IOS XR Firewall Package
c12k-firewall.pie-3.5.4
Support for Virtual Firewall (VFW) on a Cisco XR 12000 Series Router.
Cisco IOS XR Documentation Package
c12k-doc.pie-3.5.4
Manual pages for Cisco IOS XR CLI commands.
Cisco IOS XR FPD Package
c12k-fpd.pie-3.5.4
Firmware for shared port adapters (SPA) and for fixed port line cards supported in routers running Cisco IOS XR software.
Cisco IOS XR Diagnostic Package
c12k-diags.pie-3.5.4
Diagnostic utilities for routers running Cisco IOS XR software.
1 Packages are installed individually.
Memory Requirements
Caution
The minimum memory requirements for Cisco XR 12000 Series Routers running Cisco IOS XR Software Release 3.5.4 consist of the following:
•
•
•
•
–
–
Note
Hardware Supported
Cisco IOS XR software for the current release 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 Your Software Version" section.
Software Compatibility
Cisco IOS XR software for the current release is compatible with the Cisco XR 12000 Series Router systems:
•
•
•
•
•
•
For the existing installed base, the following chassis are supported:
•
•
•
Note
Other Firmware Code
The following minimum firmware code is supported by the Cisco XR 12000 Series Router:
•
–
–
–
•
–
–
Minimum Cisco IOS Image Level and Boot Helper Version for Migration to Cisco IOS XR Software on the Cisco XR 12000 Series Router
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.5.4:
•
•
If you have an older version of this system, you must upgrade to the minimum level supported before performing a migration. Otherwise, your migration will fail. For more detailed information, see the document Migrating from Cisco IOS to Cisco IOS XR Software on the Cisco XR 12000 Series Router.
Determining Your 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, as illustrated below.
Step 1
Step 2
RP/0/RP0/CPU0:router# show versionCisco CRS-1
On the Cisco CRS-1 router, you should see a response similar to the following:
Wed Aug 6 17:05:57.529 PST PDTCisco IOS XR Software, Version 3.5.4[00]Copyright (c) 2008 by Cisco Systems, Inc.ROM: System Bootstrap, Version 1.49(20080319:195807) [CRS-1 ROMMON],router uptime is 49 minutesSystem image file is "disk0:hfr-os-mbi-3.5.4/mbihfr-rp.vm"cisco CRS-16/S (7457) processor with 4194304K bytes of memory.7457 processor at 1197Mhz, Revision 1.21 DWDM controller(s)61 GigabitEthernet/IEEE 802.3 interface(s)6 Ethernet/IEEE 802.3 interface(s)104 Packet over SONET/SDH network interface(s)104 SONET/SDH Port controller(s)92 TenGigabitEthernet/IEEE 802.3 interface(s)2043k bytes of non-volatile configuration memory.38079M bytes of hard disk.981440k bytes of ATA PCMCIA card at disk 0 (Sector size 512 bytes).1000592k bytes of ATA PCMCIA card at disk 1 (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.5.4[00], Cisco Systems, at disk0:hfr-fpd-3.5.4Built on Wed Aug 6 06:00:33 PDT 2008By edde-bld1 in /auto/srcarchive3/production/3.5.4/hfr/workspace for c2.95.3-p8hfr-diags, V 3.5.4[00], Cisco Systems, at disk0:hfr-diags-3.5.4Built on Wed Aug 6 05:59:51 PDT 2008By edde-bld1 in /auto/srcarchive3/production/3.5.4/hfr/workspace for c2.95.3-p8hfr-mcast, V 3.5.4[00], Cisco Systems, at disk0:hfr-mcast-3.5.4Built on Wed Aug 6 04:31:36 PDT 2008By edde-bld1 in /auto/srcarchive3/production/3.5.4/hfr/workspace for c2.95.3-p8hfr-mpls, V 3.5.4[00], Cisco Systems, at disk0:hfr-mpls-3.5.4Built on Wed Aug 6 04:15:29 PDT 2008By edde-bld1 in /auto/srcarchive3/production/3.5.4/hfr/workspace for c2.95.3-p8hfr-lc, V 3.5.4[00], Cisco Systems, at disk0:hfr-lc-3.5.4Built on Wed Aug 6 04:33:48 PDT 2008By edde-bld1 in /auto/srcarchive3/production/3.5.4/hfr/workspace for c2.95.3-p8hfr-fwdg, V 3.5.4[00], Cisco Systems, at disk0:hfr-fwdg-3.5.4Built on Wed Aug 6 04:33:17 PDT 2008By edde-bld1 in /auto/srcarchive3/production/3.5.4/hfr/workspace for c2.95.3-p8hfr-admin, V 3.5.4[00], Cisco Systems, at disk0:hfr-admin-3.5.4Built on Wed Aug 6 04:33:47 PDT 2008By edde-bld1 in /auto/srcarchive3/production/3.5.4/hfr/workspace for c2.95.3-p8hfr-base, V 3.5.4[00], Cisco Systems, at disk0:hfr-base-3.5.4Built on Wed Aug 6 04:38:50 PDT 2008By edde-bld1 in /auto/srcarchive3/production/3.5.4/hfr/workspace for c2.95.3-p8hfr-os-mbi, V 3.5.4[00], Cisco Systems, at disk0:hfr-os-mbi-3.5.4Cisco 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.5.3[00]Copyright (c) 2008 by Cisco Systems, Inc.ROM: System Bootstrap, Version 12.0(20041108:104740) [ashp-cisp-rommon 1.16dev(0.1)] DEVELOPMENT SOFTWARECopyrigh, Inc.PE1 uptime is 9 hours, 49 minutesSystem image file is "disk0:c12k-os-mbi-3.5.3/mbiprp-rp.vm"cisco 12416/PRP (7457) processor with 2097152K bytes of memory.7457 processor at 1266Mhz, Revision 1.21 4 Port ISE Packet Over SONET OC-12c/STM-4 Controller (4 POS)1 Cisco 12000 Series SPA Interface Processor-6002 Cisco 12000 Series - Multi-Service Blade Controllers1 1 Port ISE Packet Over SONET OC-48c/STM-16 Controller (1 POS)1 Cisco 12000 4 Port Gigabit Ethernet Controller (4 GigabitEthernet)2 Cisco 12000 Series Performance Route Processors1 Cisco 12000 4-Port ISE ATM Over SONET OC3/STM-1 Controller (4 ATM)3 Cisco 12000 Series SPA Interface Processor-601/501/4014 ATM Network Interface(s)8 FastEthernet/IEEE 802.3 interface(s)14 GigabitEthernet/IEEE 802.3 interface(s)6 Ethernet/IEEE 802.3 interface(s)2 Controller for the management of multilink interfacess42 Multilink network interface(s)13 PLIM QoS controller(s)5 Packet over SONET/SDH network interface(s)124 Serial network interface(s)10 SONET/SDH Port controller(s)140 T1 Port controller(s)6 T3 Port controller(s)1 TenGigabitEthernet/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).Boot device on node 0/0/CPU0 is mem:Package active on node 0/0/CPU0:c12k-sbc, V 3.5.3[00], Cisco Systems, at disk0:c12k-sbc-3.5.3Built on Wed Jan 16 14:55:34 PST 2008By zamboni in /auto/srcarchive2/production/3.5.3/c12k/workspace for c2.95.3-p8c12k-firewall, V 3.5.3[00], Cisco Systems, at disk0:c12k-firewall-3.5.3Built on Wed Jan 16 10:57:41 PST 2008By zamboni in /auto/srcarchive2/production/3.5.3/c12k/workspace for c2.95.3-p8c12k-mcast, V 3.5.3[00], Cisco Systems, at disk0:c12k-mcast-3.5.3Built on Wed Jan 16 10:02:43 PST 2008By zamboni in /auto/srcarchive2/production/3.5.3/c12k/workspace for c2.95.3-p8c12k-mpls, V 3.5.3[00], Cisco Systems, at disk0:c12k-mpls-3.5.3Built on Wed Jan 16 10:02:16 PST 2008By zamboni in /auto/srcarchive2/production/3.5.3/c12k/workspace for c2.95.3-p8c12k-k9sec, V 3.5.3[00], Cisco Systems, at disk0:c12k-k9sec-3.5.3Built on Wed Jan 16 10:03:35 PST 2008By zamboni in /auto/srcarchive2/production/3.5.3/c12k/workspace for c2.95.3-p8c12k-lc, V 3.5.3[00], Cisco Systems, at disk0:c12k-lc-3.5.3Built on Wed Jan 16 10:11:31 PST 2008By zamboni in /auto/srcarchive2/production/3.5.3/c12k/workspace for c2.95.3-p8c12k-fwdg, V 3.5.3[00], Cisco Systems, at disk0:c12k-fwdg-3.5.3Built on Wed Jan 16 10:10:30 PST 2008By zamboni in /auto/srcarchive2/production/3.5.3/c12k/workspace for c2.95.3-p8c12k-admin, V 3.5.3[00], Cisco Systems, at disk0:c12k-admin-3.5.3Built on Wed Jan 16 10:09:43 PST 2008By zamboni in /auto/srcarchive2/production/3.5.3/c12k/workspace for c2.95.3-p8c12k-base, V 3.5.3[00], Cisco Systems, at disk0:c12k-base-3.5.3Built on Wed Jan 16 10:08:19 PST 2008By zamboni in /auto/srcarchive2/production/3.5.3/c12k/workspace for c2.95.3-p8c12k-os-mbi, V 3.5.3[00], Cisco Systems, at disk0:c12k-os-mbi-3.5.3Built on Wed Jan 16 10:04:25 PST 2008By zamboni in /auto/srcarchive2/production/3.5.3/c12k/workspace for c2.95.3-p8
New and Changed Information
The following sections contain information on new features in Cisco IOS XR Software Release 3.5.4:
•
•
•
New Software Features in Cisco IOS XR Software Release 3.5.4
Cisco CRS-1 and Cisco XR 12000 Series Router Platforms
The following new features in Cisco IOS XR Software Release 3.5.4 are supported on the Cisco CRS-1 router and Cisco XR 12000 Series Router platforms:
•
•
•
Cisco CRS-1 Router-Specific Features Only
The following new feature in Cisco IOS XR Software Release 3.5.4 is supported only on the Cisco CRS-1 platform:
•
Cisco XR 12000 Series Router Services
None.
New Hardware Features in Cisco IOS XR Software Release 3.5.4
The following hardware features are new in the current release:
•
•
For detailed information on the shared port adapters (SPAs) and SPA interface processors (SIPs), see the following documents:
•
•
DC-PEM and Fan Tray Modifications
The existing DC-PEM and fan trays have been modified on the Cisco CRS-1 16-Slot Line Card Chassis and the Cisco CRS-1 24-Slot Fabric Chassis (CRS-FC24) to reduce fan speed and require less power during normal operation.
•
•
Acoustic Levels Reduced on Two Chassis
When you install the Cisco CRS-1 16-Slot Line Card Chassis with the new DC PEM and fantrays, described under DC-PEM and Fan Tray Modifications, the reduction in noise now brings the chassis into compliance with the NEBS Acoustic Noise Requirement (Telcordia GR-63-CORE Issue 3). When the Cisco CRS-1 24-Slot Fabric Chassis is installed with these new components, the reduction in noise now brings it near to compliance with the requirement.
Software Feature Documentation
The following documentation on how to use the features introduced in the current maintenance release, is organized by the feature name for which it has been introduced.
•
•
•
Note
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
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 3.5.4
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 3.5.4
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 follwing 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 3.5.4
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 100MPLS Tunnel Drop Counts
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
Release 3.2
This command was introduced on the Cisco CRS-1.
Release 3.3.0
No modification.
Release 3.5.4
Two new fields were added to the output.
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.
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
Field Descriptions
drop 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 errorsLDP-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 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.
New or Changed Commands
This feature affects the following commands:
•
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 3.5.4
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 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 instance]
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 0MPLS 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.5.4 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 ISIS.
Note
Summary Steps
1.
2.
3.
4.
5.
6.
7.
8.
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)# interface tunnel-te 0RP/0/RP0/CPU0:router(config-if)# path-option 1 explicit name 234 ospf 3 area 7 verbatimRP/0/RP0/CPU0:router(config)# interface tunnel-te 0RP/0/RP0/CPU0:router(config-if)# path-option 1 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
Important Notes
•
•
•
•
•
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
•
•
ft group 1peer 1no preemptassociate-context ctx1inservice
Caution
Caveats
Caveats describe unexpected behavior in Cisco IOS XR software releases. This section lists the open caveats for Cisco IOS XR Software Release 3.5.4:
•
•
•
Cisco CRS-1 and Cisco XR 12000 Series Router Caveats
The following caveat applies to both router platforms:
•
Basic Description:
TE tunnels flap after RP failover.
Symptom:
TE tunnels flap after RP FO on the multichassis system.
Conditions:
Seen after designated shelf controller RP failover.
Workaround:
Increase the signaling refresh interval to 180 as a workaround on all the RSVP links. Box will recover by itself. With the workaround, no traffic loss is expected.
•
Basic Description:
Cannot successfully perform clear counter t1 command.
Symptom:
Ambiguous command:
RP/0/0/CPU0:Router# clear counter t1 0/1/0/0Condition:
This occurs when both MPLS and k9sec pies are installed on a router and the clear counter command is issued from EXEC mode. The cause of the issue is that the above two pies introduces two software interface types "tunnel-te" and "tunnel-ipsec" and the parser detects an ambiguity between these two types. This is a bug in the parser, because at the same level a controller type "T1" is an allowed option. However, the parser does not honor this longest match.
Workaround:
Provided that you have a root-system task-id authorization, you can execute the same clear command as follows:
RP/0/0/CPU0:Router# run exec_t1e1 clear T1R_S_M_P clear_statswhere:
T1R_S_M_P is the T1 controller name (without spaces between the type and instance) and the characters in the instance are separated by underscores (_).
Caveats Specific to the Cisco CRS-1 Router
The following caveats are specific to the Cisco CRS-1 platform:
•
Symptom:
Standby RP is not ready after Cisco CRS-1 RP failover.
Conditions:
Occurs when a transient control Ethernet outage takes place, lasting 10 seconds. When the RP switches to an active state, the designated shelf controller (DSC) sends a request to the QSM to remove all the entries belonging to the standby node in its database.
Workaround:
Restarting the QSM on the active node fixes the issue. To restart the QSM, issue the following command:
P/0/RP0/CPU0:Router# process restart qsm•
Symptom:
Console is continuously flooded with the following message:
%ROUTING-RIB-3-SHUTDOWN : Process is shutting down: ''sysdb'' detected the ''warning'' condition ''A SysDB client attempted to register for verification or as an EDM on a path which was already registered''Conditions:
Triggered sporadically by designated shelf controller RP failover.
Workaround:
No workaround as such, but you can perform the following steps to reestablish a steady state:
1.
RP/0/RP0/CPU0:Router# show placement process proc-name2.
RP/0/RP0/CPU0:Router# show process proc-name location all3.
Note
Note
4.
RP/0/RP0/CPU0:Router# placement reoptimize
Note
•
Symptom:
The parser_server process and nvgen_server processes, or both, crash repeatedly on standby or nondesignated shelf controller RP after RP reload or switchover.
Conditions:
The problem appears to be triggered by repeated card reloads or switchovers, and may be due to disk corruption.
The crash is due to .parser files becoming corrupted on the disk of the RP and being truncated to zero length. After a reload, the parser_server and nvgen_server processes try to read these files and crash because the files have been corrupted. The processes are automatically restarted, but continue to crash as they attempt to re-read the files on restart.
Workaround:
Execute the command install verify packages repair location problem-node to copy good versions of the damaged files from the active DSC RP. The crashes stop as soon as the corrupted files are repaired. In rare cases, the install verify packages repair command may not be effective due to CSCsr75888. If crashes continue after repair, use the following procedure to manually repair the files:
1.
Info: /install/hfr-mcast-3.5.4: [ERROR] Detected anomalies.Info: /install/hfr-mcast-3.5.4/parser/igmp_cmds.parser: exists with unexpected file size.2.
copy filename location DSC-location filename location problem-nodeThe following example shows use of this command and output similar to the following that should appear:
RP0/RP0/CPU0:router(admin)# copy disk0:/hfr-mcast-3.5.4/parser/igmp_cmds.parser location RP0/RP0/CPU0 disk0:/hfr-mcast-3.5.4.13I/parser/igmp_cmds.parser location 2/RP0/CPU0Copy : Destination exists, overwrite ?[confirm]C7714 bytes copied in 0 sec3.
a.
b.
c.
RP0/RP0/CPU0:router(admin)# dir disk0:/hfr-mcast-3.5.4/parser/igmp_cmds.parser location 2/RP0/CPU0Directory of net/node2_RP0_CPU0/disk0:/hfr-mcast-3.5.4/parser521144192 -rwx 7714 Tue Aug 5 21:17:04 2008 igmp_cmds.parser4.
•
Symptom:
Card resets due to a loss of heartbeat.
Conditions:
During reload SMU installations or during a router reload, a card or node may reload due to loss of heartbeat and then recover .
Workaround:
Because the current release has an auto-recovery mechanism that takes effect when a node resets due to loss of heartbeat, the node automatically recovers from this state. As a result, no workaround is needed.
•
Basic Description:
4-port OC-3 SPA falsely reads critical high temperature after reload of the jacket card.
Conditions:
Occurs when users reload the jacket card by attaching it to the CPU0 node and they issue the command reload location x/x/CPU0, but they do not issue a reload command on the SP node.
Workaround:
After attaching a jacket card to CPU0, do not issue a reload command on this slot without also doing so for the SP node. You may also issue the command hw-module loc x/x/sp reload on both the SP and the CPU0 nodes, causing them both to be reloaded.
•
Basic Description:
OC48 SPA fails to boot after performing MSC swap.
Symptom:
OC48 SPA fails to boot.
Conditions:
The issue can be run into after doing MSC swap when the SIP-800 card is loaded with 6 SPAs.
Workaround:
Perform a soft online insertion and removal of the SPA card using the hw-module subslot x/x/x reload command.
Caveats Specific to the Cisco XR 12000 Series Router
The following caveats are specific to the Cisco XR 12000 Series Router platform:
•
Symptom:
When booting the router with the Release 3.5.4 image, the Engine 3 (E3) line card appears to be in the "In Reset" state in the output from the show platform command.
Conditions:
The condition only occurs if the router is upgraded to Release 3.7.0, automatically upgrading the MBUS agent to version 4.x (which is incompatible with this release), followed by a downgrade to Release 3.5.0 (which does not downgrade the MBUS agent automatically).
Workaround:
Downgrade MBUS ROM to Release 3.5.4 by taking the following steps.
With the router running the Release 3.5.4 image and E3 in the In Reset state, enter the following commands:
RP/0/0/CPU0:router-upgrade(admin)# test mbus download loc node-idRP/0/0/CPU0:router-upgrade(admin)# upgrade mbus force loc node-idRP/0/0/CPU0:router-upgrade# hw-module location node-id reload•
Basic Description:
Cisco IOS XR Routing Command Reference Releases 3.4 through 3.5 incorrectly documents enablement of Label Distribution Protocol (LDP)-Interior Gateway Protocol (IGP) synchronization for OSPF.
Workaround:
To enable Label Distribution Protocol (LDP)-Interior Gateway Protocol (IGP) synchronization, use the mpls ldp sync command in the appropriate mode. To disable LDP-IGP synchronization, use the no form of this command:
mpls ldp sync
no mpls ldp sync
Syntax Description
This command has no arguments or keywords.
Defaults
LDP-IGP synchronization is disabled for OSPF.
Command Modes
Interface configuration
Area configuration
Router configurationCommand Usage
To disable LDP-IGP synchronization under the interface and area submodes, use the following command:
mpls ldp sync disable
•
Basic Description:
Cisco IOS XR Interface and Hardware Components Command Reference for Release 3.5.0 and later release neglects to state that the Cisco XR 12000 Series Router does not support counters on Layer3/atm Eng3 subinterface level.
Symptom:
RP/0/0/CPU0:router# sh int ATM0/4/0/0.101Thu May 29 15:19:23.138 EST EDTATM0/4/0/0.101 is up, line protocol is upInterface state transitions: 2Hardware is ATM network sub-interface(s)Internet address is 10.211.213.102/30MTU 4470 bytes, BW 622000 Kbitreliability Unknown, txload Unknown, rxload UnknownEncapsulation AAL5/SNAP, controller loopback not set,Last clearing of "show interface" counters UnknownDatarate information unavailable.Interface counters unavailable.•
Basic Description:
PIM process crashes during an online insertion and removal (OIR) operation on a line card.
Conditions:
The crash occurs due to a corruption of the unicast routing information maintained by PIM. The information may be updated incorrectly during the OIR operation and cause the crash.
Note
Workaround:
None. PIM process restarts and recovers its state.
•
Basic Description:
Session Border Control (SBC) process fails anda restart occurs after multiservice blade (MSB) failover.
Conditions:
This issue was seen under the following conditions:
–
–
Workaround:
None.
•
Basic Description:
Configuring the serviceability design requirements (SDR) with a "/" in the SDR name crashes the LRd process.
Symptom:
Configuring SDR with a sdr-name argument containing the character "/" causes a crash of the LRd process. Subsequent operations are stalled because SDR configuration fails.
Conditions:
Config operation involving SDR carve operation.
Workaround:
Avoid using / in the sdr-name argument during configuration. If a configuration already exists, replace the sdr-name argument and reapply the configuration.
•
Basic Description:
Ensure that the minimum boot images (MBI) are compatible before the software upgrade.
Symptom:
1.
2.
Conditions:
1.
2.
3.
Workaround:
1.
(a) Verify that this is the issue or situation. Check for the following:
- Install operation completed successfully before issuing a reload for all nodes (console logs).
- Wait for the active RP to come up and verify that it is running Release 3.5.2 (show install active command).
- Verify that standby RP is trying to boot Release 3.4.2. This can be seen on the standby console in the banner when the image is booting (for example, "Cisco IOS XR Software for the Cisco XR c12000-mbiprp, Version 3.4.2[1]").
- The following error should appear periodically on the standby console:
Insthelper encountered a fatal error condition, and is exiting: Error value = (1341786888), Error string = ('Subsystem(8180)' detected the 'warning' condition 'Code(5)': Host is down)(b) Bring standby RP to ROMMON. This can be done, for example:
- Issue the hw-module loc location reload command from the designated shelf controller.
- Issue the send break command on the standby RP console line when the following appears:
DRAM DIMM Slot 1: 2048M found, Slot 2: Empty MPC7457 platform with 2097152 Kbytes of main memory(c) Reset BOOT variable to a new value.
- Check its current value. It should be pointing to disk0:c12k-os-mbi-3.4.2/mbiprp-rp.vm
- Check if Release 3.5.2 MBI exists on the disk, for example:
rommon 7 > dir disk0:c12k-os-mbi-3.5.2.14I File size Perms File name 0 drw- etc 0 drw- instdb_v 0 drw- mbi 0 drw- drp 0 drw- gsr 10088776 -rw- mbiprp-rp.vm 0 drw- instdb- Set the BOOT variable to the new Release 3.5.2 MBI value, for example:
rommon 8 > BOOT=disk0:c12k-os-mbi-3.5.2.14I/mbiprp-rp.vm rommon 9 > syncIssue the reset command to reload this node and let it come up with Release 3.5.2 MBI.
If you changed the config-register value when bringing it to ROMMON, change it back to the original value.
If the Release 3.5.2 MBI is not present on the disk, you must perform the diskboot procedure for the standby. Refer in this case to Scenario 2 below.
(d) Verify that the node comes up successfully with Release 3.5.2, then wait until it is in the Cisco IOS XR RUN state.
(e) When all nondesignated shelf controller RP nodes are up, issue the install commit command.
2.
rommon 1 > boot tftp address://directory/mbiprp-rp.vm-3.5.2 192.85.16.23For more documentation on the diskboot procedure, refer to Migrating From Cisco IOS to Cisco IOS XR Software on the Cisco XR 12000 Series Router, Release 3.5 on cisco.com.
•
Basic Description:
SPA-4XCT3/DS0 out-of-service state after restarting packet process.
Symptom:
4xCT3/DS0 SPA out of service after restarting packet process. Problem happens in a Cisco XR 12000 Series Router running a Cisco IOS XR Release 3.5.2 image.
Workaround:
None. Only a reload fixes the problem.
•
Basic Description:
Clock Scheduler Card switchover cannot access the router console or router auxiliary port.
Symptom:
Shutting down the Clock Scheduler Card or a switchover of the Clock Scheduler Card on the Cisco XR 12000 Series Router blocks accessibility to the router console and auxiliary ports.
Workaround:
Reload the router.
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 or downgrade Cisco IOS XR Software to the current release:
http://www.cisco.com/web/Cisco_IOS_XR_Software/index.html
Troubleshooting
For information on troubleshooting Cisco IOS XR software, see the Cisco IOS XR Getting Started Guide and the document Cisco IOS XR Troubleshooting.
Related Documentation
The following sections describe the documentation available for the Cisco CRS-1 and Cisco XR 12000 Series Router. Documentation is available in the form of PDF and HTML files and is available on www.Cisco.com.
Hardware Documents
You can find the most current hardware documentation at the following URLs:
Cisco CRS-1 Series Router:
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.5.0 for a list of Cisco IOS XR Software documentation for Release 3.5.0.
You can find the most current software documentation at the following URL:
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
Guest
