Table Of Contents
Release Notes for the Cisco 7200 Series for Cisco IOS Release 12.2(11)YX1
June 23, 2003
Text Part Number OL-3617-02
These release notes describe changes to the software for the Cisco 7200 series routers for Cisco IOS Release 12.2(11)YX1.
Cisco IOS Software Release 12.1(11)YX1 features IPSec stateful failover, but with the addition of generic routing encapsulation (GRE), a tunnel interface not tied to specific "passenger" or "transport" protocols.
Tunneling protocols, such as GRE, encapsulate packets inside of a transport protocol. A tunnel interface creates a virtual point-to-point link between two routers at remote points over an IP internetwork. Each tunnel must be configured separately for each link.
GRE supports multicast traffic, critical for V3PN applications.
Figure 1 shows a sample topology for site-to-site configuration of IPSec Stateful Failover with GRE.
Figure 1 Sample Topology for Site-to-Site
Table 1 lists the software images and corresponding memory requirements for the and Cisco 7200 series routers in Cisco IOS Release 12.2(11)YX1.
Note For a complete list of the minimum memory recommendations for the Cisco 7200 series of routers in Cisco IOS Release 12.2, go to the following URL:
This release supports the Cisco 7200 series routers with NPE- 400, 300, 225, 200, and NSE-1 processors. The Cisco IOS Release 12.2(11)YX1 also supports the VPN Acceleration Module (VAM).
Note Cisco IOS Release 12.2(11)YX1 does not support the NPE-G1 processor or the service adapter VPN acceleration module (SA-VAM2).
For additional information about supported hardware for these platforms, refer to the Hardware/Software Compatibility Matrix in the Cisco Software Advisor at the following URL:
Determining the Software Version
To determine the version of Cisco IOS software running on your router, log in to the router and enter the show version EXEC command:
Note The following example shows output from the Cisco 7200 series router.
router> show versionCisco Internetwork Operating System SoftwareIOS (tm) 7200 series Software c7200-jk9o3s-mz, Version 12.2(11)YX, RELEASE SOFTWARE
Upgrading to a New Software Release
For general information about upgrading to a new software release, refer to Software Installation and Upgrade Procedures located at the following URL:
Feature Set Tables
The Cisco IOS software is packaged in feature sets consisting of software images—depending on the platform. Each feature set contains a specific set of Cisco IOS features.
For a complete list of feature sets supported by the Cisco 7200 series routers in Release 12.2, go to the following URL:
Caution Cisco IOS images with strong encryption (including, but not limited to, 168-bit Triple Data Encryption Standard [3DES] data encryption feature sets) are subject to United States government export controls and have limited distribution. Strong encryption images to be installed outside the United States are likely to require an export license. Customer orders may be denied or subject to delay because of United States government regulations. When applicable, purchaser and user must obtain local import and use authorizations for all encryption strengths. Please contact your sales representative or distributor for more information, or send an E-mail to email@example.com.
New and Changed Information
New Hardware Features in Cisco IOS Release 12.2(11)YX1
There are no new hardware features in Cisco IOS Release 12.2(11)YX1 or Cisco IOS Release 12.2(11)YX.
New Software Features in Cisco IOS Release 12.2(11)YX1
The following software feature is new to Cisco IOS Release 12.2(11)YX1:
•IPSec High Availability with generic routing encapsulation (GRE)—Adds a tunnel interface for each GRE endpoint. Because tunnels are point-to-point links, you must configure a separate tunnel for each link.
New Software Features in Release 12.2(11)YX
The following software features are new in Cisco IOS Release 12.2(11)YX:
•IPSec High Availability—Enables VPN tunnels to fail over from an active unit to a standby unit without reinitiating the VPN tunnels, and without detection by remote devices.
•IKE Acceleration—Reduces VPN tunnel setup time. This feature is useful in network storm situations, when a large number of tunnels need to be set up simultaneously.
•Dead Peer Detection (DPD)—Tracks peer connectivity for failover purposes. When a peer connection is down, failover occurs. While similar to IKE Keepalive functions, it provides improved scalability and less peer tracking overhead.
This section lists caveats for the Cisco IOS Release 12.2(11)YX and 12.2(11)YX1 by tracking number (DDTS #) and release number, and indicates whether the caveat has been corrected. An "O" indicates that the caveat is open in that release; a "C" indicates that the caveat is closed in that release, and an "R" indicates that the caveat is resolved in a later release.
Table 2 lists the caveats for the Cisco IOS Release 12.2(11)YX and 12.2(11)YX1.
Table 2 Release Caveats and Caveats Corrected Reference
Cisco IOS Software Release 12.2(11)YX and 12.2(11)YX1 DDTS Number Corrected
In this section, the following information is provided for each caveat:
•Symptoms—A description of what is observed when the caveat occurs.
•Conditions—The conditions under which the caveat has been known to occur.
•Workaround—Solutions, if available, to counteract the caveat.
Note If you have an account with Cisco.com, you can use Bug Navigator II to find caveats of any severity for any release. To reach Bug Navigator II, log in to Cisco.com and click Software Center: Cisco IOS Software: Bug Toolkit: Bug Navigator II. Another option is to go to http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl.
The caveats section includes the following subsections:
Open Caveats—Cisco IOS Release 12.2(11)YX1
This section describes possibly unexpected behavior by Cisco IOS Release 12.2(11)YX1. All the caveats listed in this section are open in Cisco IOS Release 12.2(11)YX1. This section describes severity 1 and 2 caveats and select severity 3 caveats.
Note Many caveats that apply to Cisco IOS Release 12.2 also apply to Cisco IOS Release 12.2(11)S. For information on severity 1 and 2 caveats in Cisco IOS Release 12.2, see the Caveats for Cisco IOS Release 12.2 document located on Cisco.com at the following URL:
Symptoms: In the event of a failure on the active device, Hot Standby Router Protocol (HSRP) does not report a change in state. Consequently, in the case of stateless failover, existing IPSec security associations (SAs) are not removed from the failed device. Also, where reverse route injection (RRI) is used with a static crypto map, routes on the failed device are not removed from the routing table.
Conditions: The HSRP failure to report symptom is observed with stateless failover configurations; for example, when using the redundancy keyword to apply a crypto map to an interface. The RRI symptom is observed with both stateless and stateful failovers, when the reverse-route keyword is added to a static crypto map.
Workaround: Do not use RRI, instead add static routes manually or use dynamic crypto maps. For stateless failover, enter the clear crypto sa command after a failover on the failed device.
Symptoms: If the redundancy name used in an Switch-to-Switch Protocol (SSP) configuration is more than 21 characters, the router crashes when booting. A long redundancy name causes a crash only when it is parsed as part of an SSP configuration.
Conditions: This symptom is observed when using a very long HSRP redundancy name.
Workaround: Use a redundancy name less than 21 characters.
Resolved Caveats—Cisco IOS Release 12.2(11)YX1
This section describes caveats that have been resolved by Cisco IOS Release 12.2(11)YX1.
Symptoms: Cisco IOS Software Release 12.2S supports generic routing encapsulation (GRE) in IPSec, which requires that the crypto map be applied to both the physical and tunnel interfaces on the router. At bootup, however, only the tunnel interface is activated.
Conditions: When you remove the crypto map from both the physical and tunnel interfaces, a crash results.
Symptoms: Reverse route injection works only after the initial injection.
When the Unity Client (UC) connects to the UUT, reverse route injection results and a route for address 220.127.116.11 is set up on the UUT.
Conditions: When you reload the UUT, and reinitiate the tunnel, the route is reinjected.
Workaround: Add static route for 18.104.22.168, however, this workaround does not always work.
Symptom: The active and standby route processors are in the high availability setup when the active route processor crashes with the traceback.
Conditions: In the following example 6513 is the active route processor and 6509-1 is the standby route processor. The crash occurred on the active route processor.
Symptom: As the active and standby routers boot up, the active router crashes immediately on initial SA setup with the remote router.
Conditions: This symptom appears under the following conditions:
1. The active and standby routers are loaded with the ddukes-special image.
2. The routers are configured for high availability (HA) with GRE.
3. All the routers are reloaded, and when the active router initially sets up SA with the remote, it crashes.
Symptom: This symptom occurs when using enc 3des on ike and/or ipsec.
Having the above configurations will not work when failing over from software to hardware crypto.
Condition: If the active router is using software crypto, updating a hardware-equipped standby router will not create an ike sa.
If both the active and standby routers are using a VPN Accelerator Module (VAM), this error does not occur.
Symptom: Phase one of stateful failover doesn't support clients.
Condition: When high availability is enabled over GRE tunnels, each GRE tunnel should use "ip unnumber interface xxx" to setup its ip address.
Workaround: Each GRE tunnel have its own ip address in addition to using ip unnumber.
Symptom: The remote router receives ike new sa packet when the standby router comes up from reload. The remote router receive another ike new sa packet when the standby router is reloaded. This is a regression bug.
1. Load HA routers with ddukes-special April 24 image.
2. Configure HA with GRE and wait for SA's and routes to settle.
3. Reload the Standby router and as it comes up, the Remote will receive an NewSA IKE packet.
The configuration for IPSec Stateful Failover builds on the standard Stateful Failover configuration, but with the addition of a tunnel interface for each GRE endpoint, as shown in Figure 1.
1. The crypto parameters on the Stateful Failover Pair must be the same for:
–isakmp policy (encryption, authentication, hash, lifetime, group)
–isakmp key (shared secret with remote peer)
–ipsec security-association lifetimes
–ipsec transform set
2. Crypto map has to be applied to BOTH the tunnel and physical interface. To get traffic to go to the Tunnel interface there should be a route to the Tunnel IP address from the crypto peer.
3. SSP group can be configured with up to 32 redundancy groups, (with 32 Virtual IP Addresses).
4. There must be an access-list for the gre traffic with the VIP as one of the endpoints.
Following is a sample configuration which uses multiple redundancy groups, and multiple GRE tunnels. Note that this isn't necessarily a realistic deployment, but was used in the lab to illustrate the failover of multiple redundancy groups with multiple GRE tunnels. Ethernet sub-interfaces were used to simulate multiple VIPs.
Note that the other redundant router would have the same configuration except that the physical IP addresses will be different, and the SSP remote address will be pointing to the physical IP address of the private interface of the SSP peer.
Head-end router:ip cef!ssp group 100remote 22.214.171.124redundancy GRE_1redundancy GRE_2
Note: 20.i.j.1 addresses are the remote peers!crypto isakmp policy 1encr 3desauthentication pre-sharecrypto isakmp key gre1 address 126.96.36.199crypto isakmp key gre2 address 188.8.131.52crypto isakmp ssp 100!!crypto ipsec security-association lifetime kilobytes 536870912crypto ipsec security-association lifetime seconds 86400!crypto ipsec transform-set HA_TRANSFORM esp-3des!crypto map gre_1 1 ipsec-isakmpset peer 184.108.40.206set transform-set HA_TRANSFORMmatch address gre_1!crypto map gre_2 1 ipsec-isakmpset peer 220.127.116.11set transform-set HA_TRANSFORMmatch address gre_2!!call rsvp-sync!!interface Tunnel1bandwidth 500ip unnumbered FastEthernet0/0.1tunnel source 18.104.22.168tunnel destination 22.214.171.124crypto map gre_1 ssp 100ip rsvp bandwidth!interface Tunnel2bandwidth 500ip unnumbered FastEthernet0/0.2tunnel source 126.96.36.199tunnel destination 188.8.131.52crypto map gre_2 ssp 100ip rsvp bandwidth!!
Note: Sub-interfaces are used to simulate failover of multiple hsrp groups.interface FastEthernet0/0no ip addressshutdownduplex fullspeed 100standby delay minimum 200 reload 200!interface FastEthernet0/0.1encapsulation dot1Q 500ip address 184.108.40.206 255.255.255.0standby delay minimum 60 reload 120standby 1 ip 220.127.116.11standby 1 timers 1 3standby 1 preemptstandby 1 name GRE_1standby 1 track FastEthernet0/1standby 1 track FastEthernet0/0crypto map gre_1 ssp 100!interface FastEthernet0/0.2encapsulation dot1Q 501ip address 18.104.22.168 255.255.255.0standby delay minimum 60 reload 120standby 2 ip 22.214.171.124standby 2 timers 1 3standby 2 preemptstandby 2 name GRE_2standby 2 track FastEthernet0/1standby 2 track FastEthernet0/0crypto map gre_2 ssp 100!!interface FastEthernet0/1ip address 126.96.36.199 255.255.255.0shutdownduplex fullspeed 100standby delay minimum 60 reload 120standby 255 ip 188.8.131.52standby 255 timers 1 3standby 255 preemptstandby 255 name PRIVATEstandby 255 track FastEthernet0/0!!ip classlessip route 10.0.1.1 255.255.255.255 Tunnel1ip route 10.0.1.2 255.255.255.255 Tunnel2ip route 184.108.40.206 255.255.255.0 220.127.116.11ip route 18.104.22.168 255.255.255.0 22.214.171.124ip route 126.96.36.199 255.255.255.0 188.8.131.52ip route 184.108.40.206 255.255.255.0 220.127.116.11ip route 18.104.22.168 255.255.255.0 22.214.171.124ip route 126.96.36.199 255.255.255.0 188.8.131.52ip route 184.108.40.206 255.255.255.0 220.127.116.11ip route 18.104.22.168 255.255.255.255 22.214.171.124no ip http server!
Note: Access-lists are needed to permit GRE traffic to flow.ip access-list extended gre_1permit gre host 126.96.36.199 host 188.8.131.52ip access-list extended gre_10permit gre host 184.108.40.206 host 220.127.116.11
Cisco 7200 Series Routers Documentation Roadmap
Cisco 7200 series router documentation roadmap is available on cisco.com at this URL:
Cisco provides several ways to obtain documentation, technical assistance, and other technical resources. These sections explain how to obtain technical information from Cisco Systems.
You can access the most current Cisco documentation on the World Wide Web at this URL:
You can access the Cisco website at this URL:
International Cisco websites can be accessed from this URL:
Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which may have shipped with your product. The Documentation CD-ROM is updated regularly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual or quarterly subscription.
Registered Cisco.com users can order a single Documentation CD-ROM (product number DOC-CONDOCCD=) through the Cisco Ordering tool:
All users can order monthly or quarterly subscriptions through the online Subscription Store:
You can find instructions for ordering documentation at this URL:
You can order Cisco documentation in these ways:
•Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Networking Products MarketPlace:
•Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, U.S.A.) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).
You can submit comments electronically on Cisco.com. On the Cisco Documentation home page, click Feedback at the top of the page.
You can e-mail your comments to firstname.lastname@example.org.
You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate your comments.
Obtaining Technical Assistance
Cisco provides Cisco.com, which includes the Cisco Technical Assistance Center (TAC) website, as a starting point for all technical assistance. Customers and partners can obtain online documentation, troubleshooting tips, and sample configurations from the Cisco TAC website. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC website, including TAC tools and utilities.
Cisco.com offers a suite of interactive, networked services that let you access Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.
Cisco.com provides a broad range of features and services to help you with these tasks:
•Streamline business processes and improve productivity
•Resolve technical issues with online support
•Download and test software packages
•Order Cisco learning materials and merchandise
•Register for online skill assessment, training, and certification programs
To obtain customized information and service, you can self-register on Cisco.com at this URL:
Technical Assistance Center
The Cisco TAC is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two types of support are available: the Cisco TAC website and the Cisco TAC Escalation Center. The type of support that you choose depends on the priority of the problem and the conditions stated in service contracts, when applicable.
We categorize Cisco TAC inquiries according to urgency:
•Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities, product installation, or basic product configuration. There is little or no impact to your business operations.
•Priority level 3 (P3)—Operational performance of the network is impaired, but most business operations remain functional. You and Cisco are willing to commit resources during normal business hours to restore service to satisfactory levels.
•Priority level 2 (P2)—Operation of an existing network is severely degraded, or significant aspects of your business operations are negatively impacted by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.
•Priority level 1 (P1)—An existing network is "down," or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.
Cisco TAC Website
The Cisco TAC website provides online documents and tools to help troubleshoot and resolve technical issues with Cisco products and technologies. To access the Cisco TAC website, go to this URL:
All customers, partners, and resellers who have a valid Cisco service contract have complete access to the technical support resources on the Cisco TAC website. Some services on the Cisco TAC website require a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to this URL to register:
If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco TAC website, you can open a case online at this URL:
If you have Internet access, we recommend that you open P3 and P4 cases online so that you can fully describe the situation and attach any necessary files.
Cisco TAC Escalation Center
The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. These classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer automatically opens a case.
To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this URL:
Before calling, please check with your network operations center to determine the Cisco support services to which your company is entitled: for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). When you call the center, please have available your service agreement number and your product serial number.
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
•The Cisco Product Catalog describes the networking products offered by Cisco Systems, as well as ordering and customer support services. Access the Cisco Product Catalog at this URL:
•Cisco Press publishes a wide range of networking publications. Cisco suggests these titles for new and experienced users: Internetworking Terms and Acronyms Dictionary, Internetworking Technology Handbook, Internetworking Troubleshooting Guide, and the Internetworking Design Guide. For current Cisco Press titles and other information, go to Cisco Press online at this URL:
•Packet magazine is the Cisco quarterly publication that provides the latest networking trends, technology breakthroughs, and Cisco products and solutions to help industry professionals get the most from their networking investment. Included are networking deployment and troubleshooting tips, configuration examples, customer case studies, tutorials and training, certification information, and links to numerous in-depth online resources. You can access Packet magazine at this URL:
•Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:
•Training—Cisco offers world-class networking training. Current offerings in network training are listed at this URL:
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Copyright © 2003 Cisco Systems, Inc. All rights reserved.