 Feedback
|
Table Of Contents
Release Notes for Cisco CRS-1 for Cisco IOS XR Software Release 3.9.1
Key Changes from Previous Releases in Cisco IOS XR Release 3.9.1
Determining Your Software Version
New Features in Cisco IOS XR Software Release 3.9.1
New Software Features Supported on all Platforms
Cisco CRS-1 Router-Specific Software Features
New Hardware Features for the Cisco CRS-1 Router
New DWDM Configuration Requirement
Summary of Important DWDM Changes in Cisco IOS XR Software Release 3.9.0 and Later Releases
Configuration Examples in Cisco IOS XR Software Release 3.9.0 and Later Releases
Minimum Flash Disk Requirements When Upgrading to Release 3.9.1
Caveats Specific to the Cisco CRS-1 Router
Resolved Cisco IOS XR Software PSIRT-Related Caveats
Upgrading Cisco IOS XR Software
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco CRS-1 for Cisco IOS XR Software Release 3.9.1
April 15, 2013
Cisco IOS XR Software Release 3.9.1
Text Part Number OL-22785-04
These release notes describe the features provided in the Cisco IOS XR Software Release 3.9.1 for the Cisco CRS-1 Router and are updated as needed.
Note
For information on the Cisco CRS-1 Router running Cisco IOS XR Software Release 3.9.1, see the "Important Notes" section.
You can find the most current Cisco IOS XR software documentation at
http://www.cisco.com/en/US/products/ps5763/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".
For a list of software caveats that apply to Cisco IOS XR Software Release 3.9.1, see the "Caveats" section. The caveats are updated for every release and are described at www.cisco.com.
We recommend that you view the field notices for this release located at the following URL to see if your software or hardware platforms are affected:
http://www.cisco.com/public/support/tac/fn_index.html
Key Changes from Previous Releases in Cisco IOS XR Release 3.9.1
Cisco IOS XR Software Release 3.9.1 requires a 2-GB Flash Disk as a minimum. Therefore, you must upgrade an existing PCMCIA 1-GB Flash Disk to 2 GB or 4 GB before upgrading to Cisco IOS XR Software Release 3.9.1. For more information, see the "Minimum Flash Disk Requirements When Upgrading to Release 3.9.1" section.
Contents
These release notes contain the following sections:
•
•
•
•
•
•
Introduction
Cisco IOS XRsoftware is a distributed operating system designed for continuous system operation combined with service flexibility and high performance.
Cisco IOS XR software running on the Cisco CRS-1 Router provides the following features and benefits:
•
•
•
•
•
•
•
•
•
•
•
•
•
–
–
–
For more information about new features provided on the Cisco CRS-1 Router for Cisco IOS XR Software Release 3.9.1, see the "New Features in Cisco IOS XR Software Release 3.9.1" section in this document.
System Requirements
This section describes the system requirements for Cisco IOS XR Software Release 3.9.1 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 the "Determining Your 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.9.1 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.9.1 supported on the Cisco CRS-1 Router.
Table 1 Cisco CRS-1 Supported Feature Sets
(Cisco IOS XR Software Release 3.9.1 PIE Files)Cisco IOS XR IP Unicast Routing Core Bundle
comp-hfr-mini.pie-3.9.1
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.9.1
Contains the required core packages including OS, Admin, Base, Forwarding, Modular Services Card, Routing, SNMP Agent, and Alarm Correlation.
Cisco IOS XR Manageability Package
hfr-mgbl-p.pie-3.9.1
Cisco IOS XR MPLS Package
hfr-mpls-p.pie-3.9.1
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.9.1
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.9.1
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
The documentation package is not supported in Cisco IOS XR Software Release 3.9.1.
Please refer to the Cisco CRS-1 command reference documentation located at the following URL:
http://www.cisco.com/en/US/products/ps5763/prod_command_reference_list.html
Cisco IOS XR FPD Package
hfr-fpd.pie-3.9.1
Firmware for Fixed PLIM20 and SPA21 modules as well as ROMMON22 images for Cisco CRS-1 chassis.
Cisco IOS XR Diagnostic Package
hfr-diags.pie-3.9.1
Diagnostic utilities for Cisco IOS XR routers.
Cisco IOS XR Documentation Package
hfr-doc.pie-3.9.1
.man pages for Cisco IOS XR software on the Cisco CRS-1 chassis.
Cisco IOS XR Carrier Grade NAT Package
hfr-cgn-p.pie-3.9.1
Support for Carrier Grade NAT on Cisco CRS-1 routers.
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 the Cisco CRS-1 Router TAR files.
Memory Requirements
Caution
The minimum memory requirements for a Cisco CRS-1 running Cisco IOS XR Software Release 3.9.1 consist of the following:
•
•
•
Note
Hardware Supported
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 supported hardware components on the Cisco CRS-1 and the minimum required software versions. For more information, see the "Other Firmware Support" section.
Software Compatibility
Cisco IOS XR Software Release 3.9.1 is compatible with the following Cisco CRS-1 systems:
•
•
•
•
Other Firmware Support
The Cisco CRS-1 supports the following firmware code:
•
http://www.cisco.com/en/US/products/ps5763/products_installation_and_configuration_guides_list.html•
Determining Your Software Version
To determine the version of Cisco IOS XR software running on your router, log into the router and enter the show version command:
Step 1
Step 2
RP/0/RP0/CPU0:router# show versionTue May 4 11:46:15.685 PSTCisco IOS XR Software, Version 3.9.1[00]Copyright (c) 2010 by Cisco Systems, Inc.ROM: System Bootstrap, Version 1.54(20091016:214209) [CRS-1 ROMMON],FQ-PE1 uptime is 1 day, 20 hours, 9 minutesSystem image file is "bootflash:disk0/hfr-os-mbi-3.9.1/mbihfr-rp.vm"cisco CRS-16/S (7455) processor with 4194304K bytes of memory.7455 processor at 800Mhz, Revision 3.42 Management Ethernet4 T344 SONET/SDH43 Packet over SONET/SDH4 Serial network interface(s)65 GigabitEthernet8 TenGigE1 Asynchronous Transfer Mode1019k bytes of non-volatile configuration memory.38079M bytes of hard disk.2053440k bytes of disk0: (Sector size 512 bytes).1000432k bytes of disk1: (Sector size 512 bytes).Boot device on node 0/5/CPU0 is mem:Package active on node 0/5/CPU0:hfr-cgn, V 3.9.1[00], Cisco Systems, at disk0:hfr-cgn-3.9.1Built on Sun May 2 00:21:20 PST 2010By sjc-lds-511 in /auto/srcarchive4/production/3.9.1/hfr/workspace for c4.2.1-p0hfr-fpd, V 3.9.1[00], Cisco Systems, at disk0:hfr-fpd-3.9.1Built on Sun May 2 00:17:56 PST 2010By sjc-lds-511 in /auto/srcarchive4/production/3.9.1/hfr/workspace for c4.2.1-p0hfr-mcast, V 3.9.1[00], Cisco Systems, at disk0:hfr-mcast-3.9.1Built on Sun May 2 02:55:10 PST 2010By sjc-lds-511 in /auto/srcarchive4/production/3.9.1/hfr/workspace for c4.2.1-p0hfr-mpls, V 3.9.1[00], Cisco Systems, at disk0:hfr-mpls-3.9.1Built on Sun May 2 02:54:49 PST 2010By sjc-lds-511 in /auto/srcarchive4/production/3.9.1/hfr/workspace for c4.2.1-p0hfr-lc, V 3.9.1[00], Cisco Systems, at disk0:hfr-lc-3.9.1Built on Sat May 1 23:58:46 PST 2010By sjc-lds-511 in /auto/srcarchive4/production/3.9.1/hfr/workspace for c4.2.1-p0hfr-fwdg, V 3.9.1[00], Cisco Systems, at disk0:hfr-fwdg-3.9.1Built on Sat May 1 23:54:25 PST 2010By sjc-lds-511 in /auto/srcarchive4/production/3.9.1/hfr/workspace for c4.2.1-p0hfr-admin, V 3.9.1[00], Cisco Systems, at disk0:hfr-admin-3.9.1Built on Sat May 1 23:48:02 PST 2010By sjc-lds-511 in /auto/srcarchive4/production/3.9.1/hfr/workspace for c4.2.1-p0hfr-base, V 3.9.1[00], Cisco Systems, at disk0:hfr-base-3.9.1Built on Sat May 1 23:48:14 PST 2010By sjc-lds-511 in /auto/srcarchive4/production/3.9.1/hfr/workspace for c4.2.1-p0hfr-os-mbi, V 3.9.1[00], Cisco Systems, at disk0:hfr-os-mbi-3.9.1Built on Sat May 1 23:20:10 PST 2010By sjc-lds-511 in /auto/srcarchive4/production/3.9.1/hfr/workspace for c4.2.1-p0Boot device on node 0/6/CPU0 is mem:Package active on node 0/6/CPU0:hfr-cgn, V 3.9.1[00], Cisco Systems, at disk0:hfr-cgn-3.9.1Built on Sun May 2 00:21:20 PST 2010By sjc-lds-511 in /auto/srcarchive4/production/3.9.1/hfr/workspace for c4.2.1-p0hfr-fpd, V 3.9.1[00], Cisco Systems, at disk0:hfr-fpd-3.9.1Built on Sun May 2 00:17:56 PST 2010By sjc-lds-511 in /auto/srcarchive4/production/3.9.1/hfr/workspace for c4.2.1-p0hfr-mcast, V 3.9.1[00], Cisco Systems, at disk0:hfr-mcast-3.9.1Built on Sun May 2 02:55:10 PST 2010By sjc-lds-511 in /auto/srcarchive4/production/3.9.1/hfr/workspace for c4.2.1-p0hfr-mpls, V 3.9.1[00], Cisco Systems, at disk0:hfr-mpls-3.9.1Built on Sun May 2 02:54:49 PST 2010By sjc-lds-511 in /auto/srcarchive4/production/3.9.1/hfr/workspace for c4.2.1-p0hfr-lc, V 3.9.1[00], Cisco Systems, at disk0:hfr-lc-3.9.1Built on Sat May 1 23:58:46 PST 2010By sjc-lds-511 in /auto/srcarchive4/production/3.9.1/hfr/workspace for c4.2.1-p0hfr-fwdg, V 3.9.1[00], Cisco Systems, at disk0:hfr-fwdg-3.9.1Built on Sat May 1 23:54:25 PST 2010By sjc-lds-511 in /auto/srcarchive4/production/3.9.1/hfr/workspace for c4.2.1-p0hfr-admin, V 3.9.1[00], Cisco Systems, at disk0:hfr-admin-3.9.1Built on Sat May 1 23:48:02 PST 2010By sjc-lds-511 in /auto/srcarchive4/production/3.9.1/hfr/workspace for c4.2.1-p0hfr-base, V 3.9.1[00], Cisco Systems, at disk0:hfr-base-3.9.1Built on Sat May 1 23:48:14 PST 2010By sjc-lds-511 in /auto/srcarchive4/production/3.9.1/hfr/workspace for c4.2.1-p0hfr-os-mbi, V 3.9.1[00], Cisco Systems, at disk0:hfr-os-mbi-3.9.1Built on Sat May 1 23:20:10 PST 2010By sjc-lds-511 in /auto/srcarchive4/production/3.9.1/hfr/workspace for c4.2.1-p0RP/0/RP0/CPU0:P2_CRS-8#
New Features in Cisco IOS XR Software Release 3.9.1
The following sections contain information on new features and enhancements in Cisco IOS XR Software Release 3.9.1:
•
•
•
Note
New Software Features Supported on all Platforms
The following new software features in Cisco IOS XR Software Release 3.9.1 are supported on all platforms:
•
•
Cisco CRS-1 Router-Specific Software Features
The following new software features were introduced in Cisco IOS XR Software Release 3.9.1 on the Cisco CRS-1 platform:
•
•
•
•
•
Cisco IOS XR Software Release 3.9.1 includes support for prefix-length notation for ACLs on the Cisco CRS-1 platform.
The following example shows how to define an access list named Internetfilter with prefix-length notation:
RP/0/RSP0/CPU0:router(config)# ipv4 access-list Internetfilter10 permit ipv4 12.10.10.1/24 any20 permit ipv4 125.10.10.1/16 any30 permit ipv4 135.10.10.1/27 any40 permit ipv4 135.200.10.1/24 any50 permit ipv4 any anyNew Hardware Features for the Cisco CRS-1 Router
The following new hardware features were introduced in Cisco IOS XR Software Release 3.9.1 on the Cisco CRS-1 Router.
•
•
For detailed information on the shared port adapters (SPAs) and SPA interface processors (SIPs), see the following documents:
•
•
For detailed information on the CGSE (Carrier Grade Services Engine), see the following document:
•
Note
Important Notes
•
•
Configuration prior to Cisco IOS XR Software Release 3.6.0:
Policy-map wred_exampleClass class-defaultrandom-detect exp 0 384 packets 484 packetsrandom-detect exp 1 384 packets 484 packetsrandom-detect exp 2 384 packets 484 packetsrandom-detect exp 3 484 packets 584 packetsrandom-detect exp 4 484 packets 584 packetsrandom-detect discard-class 0 384 packets 484 packetsrandom-detect discard-class 1 384 packets 484 packetsrandom-detect discard-class 2 484 packets 584 packetsbandwidth remaining percent 20Cisco IOS XR Software Release 3.6.0 and later releases:
policy-map wred_exampleclass class-defaultrandom-detect exp 0,1,2 384 packets 484 packetsrandom-detect exp 3,4 484 packets 584 packetsrandom-detect discard-class 0,1 384 packets 484 packetsrandom-detect discard-class 2 484 packets 584 packetsbandwidth remaining percent 20!end-policy-map!endIn Cisco IOS XR Software Release 3.6.0 and later releases, the implicitly assigned QoS class class-default must have at least 1 percent bandwidth made available to it. This can be done either by assigning at least 1 percent explicitly (bandwidth remaining percent 1) or by ensuring that the total bandwidth assigned to all other classes in the policy is a maximum of 99 percent, leaving 1 percent available for the class-default. A QoS policy that does not have any bandwidth for class-default is rejected when upgrading to Cisco IOS XR Software Release 3.6.0 or later releases.
•
•
•
•
•
–
–
–
–
•
–
RP/0/RP0/CPU0:CRS-A(config)#bfdRP/0/RP0/CPU0:CRS-A(config-bfd)#ipv6 checksum disableRP/0/RP0/CPU0:CRS-A(config-bfd)#end–
RP/0/RP0/CPU0:CRS-A(config)#bfdRP/0/RP0/CPU0:CRS-A(config-bfd)#no ipv6 checksum disableRP/0/RP0/CPU0:CRS-A(config-bfd)#end•
•
LDP session hold time <= (Hello hold time - Hello interval) * 3
This means that for default values of 15/5 seconds respectively for the link Hello hold time and the Hello interval, the LDP session hold time should be set to 30 seconds or less.
For more information, refer to the "Implementing MPLS Label Distribution Protocol on Cisco IOS XR Software" section of the Cisco IOS XR MPLS Configuration Guide, Release 3.9.1.
New DWDM Configuration Requirement
Note
Cisco IOS XR Software Release 3.9.0 introduces new commands in addition to an important change to the default laser state for all of the DWDM physical layer interface modules (PLIMs) supported on the Cisco CRS-1 router, which impacts the required configuration to support those cards.
This change affects all models of the following hardware on the Cisco CRS-1 router:
•
•
Summary of Important DWDM Changes in Cisco IOS XR Software Release 3.9.0 and Later Releases
•
•
Configuration Examples in Cisco IOS XR Software Release 3.9.0 and Later Releases
This section provides configuration examples for turning on and off the laser on a DWDM PLIM.
Turning On the Laser: Example
Note
The following example shows how to turn on the laser and place a DWDM port in In Service (IS) state:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:Router(config)# controller dwdm 0/1/0/1RP/0/RP0/CPU0:Router(config-dwdm)# admin-state in-serviceRP/0/RP0/CPU0:Router(config-dwdm)# commitTurning Off the Laser: Example
Note
The following example shows how to turn off the laser, stop all traffic and place a DWDM port in Out of Service (OOS) state:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:Router(config)# controller dwdm 0/1/0/1RP/0/RP0/CPU0:Router(config-dwdm)# admin-state out-of-serviceRP/0/RP0/CPU0:Router(config-dwdm)# commitMinimum Flash Disk Requirements When Upgrading to Release 3.9.1
Cisco IOS XR Software Release 3.9.1 requires a 2-GB Flash Disk as a minimum. If your Cisco CRS-1 currently uses a 1-GB Flash Disk, you must upgrade it to 2-GB before upgrading to Cisco IOS XR Software Release 3.9.1. The PCMCIA 1-GB Flash Disk was the default size for the Cisco CRS-1 running Cisco IOS XR Software Release 3.6 and earlier.
In Cisco IOS XR Software Release 3.6 and later releases, disk partitioning is supported. Partitioning of a 2-GB disk is possible but not required. Partitioning of a 4-GB disk is required.
A 4-GB Flash Disk can be installed instead of the 2-GB for greater disk storage.
To upgrade from a 1-GB flash disk to a 2-GB or greater flash disk, refer to the Flash Disk Upgrade Tasks link on the following Cisco CRS-1 Router Installation and Upgrade URL: http://www.cisco.com/en/US/products/ps5763/prod_installation_guides_list.html
Additional upgrade instructions for the Cisco CRS-1 router are available from http://www.cisco.com/web/Cisco_IOS_XR_Software/pdf/ReplacingPCMCIACardOnCRS-1.pdf
Caveats
Caveats describe unexpected behavior in Cisco IOS XR software releases. Severity-1 caveats are the most serious caveats; severity-2 caveats are less serious.
This section contains caveats that are generic to the Cisco IOS XR Release 3.9.1 software and those specific to the Cisco CRS-1 Router.
Cisco IOS XR Caveats
The following open caveats apply to Cisco IOS XR Software Release 3.9.1 and are not platform specific:
•
Basic Description:
CLI command not authorized to execute during persist time of EEM policy
Symptom:
After persist time start for eem policy user, CLI command failed to authorize.
Conditions:
When the TACACS server is down, persist time starts for the user credentials which registered for EEM policy. If the EEM policy gets triggered and opens a vty connection and try to execute any CLI while the TACACS server is down, it failed to authorize that command.
Workaround:
None.
Recovery:
Bring the TACACS server up.
•
Basic Description:
Unable to execute commands through telnet session
Symptom:
First show command after telnet to the router prints incomplete output and then hangs. It does not respond to "ENTER".
Conditions:
This happens after multiple VTY sessions being opened and closed at the same time.
Workaround:
None.
Recovery:
option 1
Create a new telnet session. FIRST command to execute from this session is "proc restart devc-vty".
If all the telnet sessions are exhausted, terminate one of the sessions. This frees up a session to use for recovery.
OR
option 2
Connect to the router through a Console or AUX. Recover by executing "proc restart devc-vty" command.
•
Basic Description:
CLI over XML Configuration Fails
Symptom:
CLI over XML configuration request fails.
Conditions:
This happens when
- CLI command lines in XML request execeeds 200 lines or more
AND
- CLI commands are split internally and it happens to be split in middle of sub-mode.
Workaround:
- No need to use CLI over XML for config commands that already support XML natively.
- Split the commands into multiple requests so that command lines of each request are less than 200 lines.
Recovery:
None.
•
Basic Description:
XML query equivalent to "show version | in uptime" is broken
Symptom:
XML request echoes an error in response.
Conditions:
Perform XML query equivalent to "show version | in uptime".
Workaround:
None, use CLI instead.
Recovery:
None.
•
Basic Description:
%SECURITY-LOCALD-3-LWA_ADD_FAIL error when Secret is added for a User
Symptom:
When a user tries to configure username and secret, the configuration succeeds, but the following console message is generated, which seems to suggest that the configuration did not succeed:
"% Failed to commit one or more configuration items. Please issue 'show configuration failed' from this session to view the errors"
Conditions:
No specific trigger is identified. This is an issue that has been observed a handful of times over several months.
Workaround:
None. Although we get the configuration failure message, operation is successful both on disk and as well as in Sysdb. No Operational Impact of this bug to other parts of this system since it is purely a configuration operation failure.
Recovery:
Do not need. Console message only, no functional impact.
•
Basic Description:
lpts_pa tracebacks after clear cef on line card
Symptom:
An error log is printed along with the traceback when a message send to BCDL agent fails.
Conditions:
The BCDL agent has gone down thus the message send is failing. This is a very rare scenario and would not happen under normal circumstances.
Workaround:
Not required, as BCDL will come up eventually.
Further Problem Description:
The error message is just to say that BCDL agent might have gone down. This would not cause an error in lpts as BDCL will eventually come up and the messages will be sent again. The only caveat is that it might be some time before the messages are sent again. The solution would aim to put an upper bound on the resend time by having a retrying mechanism for the same.
•
Basic Description:
Not able to modify RPL and delete prefix-set in a single commit.
Symptom:
When a policy that is attached directly or indirectly to an attach point needs to be modified, a single commit operation cannot be performed when:
–
–
Workaround:
The commit must be performed in two steps:
1.
2.
Caveats Specific to the Cisco CRS-1 Router
The following open caveats are specific to the Cisco CRS-1 platform:
•
Basic Description:
CRS MSC Traffic loss due to incorrectly programmed TCAM entries
Symptom:
CRS1 line card may exhibit dropping of traffic flows through the card.
Conditions:
This problem has a very low rate of incidence; only two incidents in the past 12 months are known to be related to this condition.
This problem may occur on any line card where combinations of TCAM applications incur a high incidence of TCAM updates.
Workaround:
None.
Recovery:
When this condition occurs, it can sometimes correct itself. This occurs only if the TCAM entries that were mismatched receive additional updates that trigger the reprogramming of those entries into the TCAM.
Should the entries not correct themselves, the line card needs to be reloaded.
•
Basic Description:
ATM SPA errors after VPI reuse in scaled configuration
Symptom:
SPA related errors generally accompanied by channel stats error.
Conditions:
1. Configure a scaled setup with 4k ATM xconnect sessions under a L2 VP mode.
2. Delete the L2 VPs thus bringing the xconnects down.
3. Configure VC mode L2 transport and bring the xconnect sessions backup.
Under such a sequence of actions, there is a possibility that one of the VP teardown does not go through clean leaving behind stale Channel of the VP. If a subsequent VC is created with same VPI value, it might sometimes result in traffic outage on that particular L2-VC.
When the problem occurs, the show hw-module subslot <> counter sar will indicate a CID for VCD mapped to the L2 VP which was deleted indicating it is stale.
Workaround:
Avoid using a L2VC with the same VPI value as the VPI of the previously configured VP on the same port. If the VPI has been re-used and the traffic does not pass over the newly configured L2 connection, change the VPI value to have a different CID allocated..
Recovery:
Please reload the SPA to recover from this issue.
•
Basic Description:
On a fibre pull, LOS counter is not always incremented
Symptom:
The LOS counter may not increment correctly on the 1x10GE WANPHY SPA.
Conditions:
When a LOS occurs on the 1x10GE Wanphy SPA receive port, a LOS alarm is raised as expected, however the LOS counter may fail to increment. This condition occurs only when LOS is caused due to a fiber pull.
Workaround:
None.
•
Basic Description:
Tacacs authentication fails when mismatched server key is configured
Symptom:
Authentication failures with tacacs+ when mismatched server key is configured on router for primary server.
Conditions:
Configure wrong key for 1st (primary server) on the router but correct key for 2nd server and try to login to the router with an username configured only on tacacs servers.
Workaround:
If a local user is configured and authentication is set to have local as the backup authentication method that login will succeed. Configure the correct server key. Alternately, "turn off" the primary tac server (on the server side) long enough to get onto the router (via secondary tac server auth) and fix the key.
Recovery:
If no local user is configured and you are unable to match the router key on the tacacs+ server side you must proceed with password recovery. Please contact technical support for further assistance.
•
Basic Description:
Preconfig / RP FO after CGSE shutdown is not supported for CGN feature
Symptom:
Attempting to preconfigure CGN feature-specific configuration on empty or non-CGSE linecard slots fails or, in other words:
For applying CGN feature specific config, CGSE Plim must be present/active in the Router.
OR
Messages on the console indicating termination of 'cgn_ma', 'sesvimgr' & 'service_director' are seen on the console repeatedly.
Conditions:
1. When CGN specific config is applied and CGSE is not present.
2. CGSE PLIM was present with CGSE config on a particular slot and the if the slot was POWERED down later. At this stage if an RP FO / Chassis reload can cause the above mentioned messages appearing on the console.
Workaround:
None.
•
Basic Description:
NAT fails on modifying Active/Standby pair config to Active only after Failover
Symptom:
NAT Translation fails on following actions -
1) CGSE Failover in redundancy setup.
2) Remove standby location config to make it non redundant setup.
Conditions:
This symptom is observed when all of the following conditions occur: When Active/Standby CGSE is configured and Failover is triggered. Modify the service-location config to preferred active only and do not configure standby location
Workaround:
Restart cgn_ma process.
•
Basic Description:
VRF related configurations failing if standby alone reloaded
Symptom:
CGN specific VRF and Address pool map related config doesn't get applied on standby CGSE after reloading standby CGSE alone.
Conditions:
This symptom is observed when all of the following conditions occur: When Active & Standby CGSE is configured and Standby CGSE is reloaded. When preferred-active location is configured first and then configure preferred standby location along with active location. Modify preferred standby location.
Workaround:
Restart cgn_ma process.
•
Basic Description:
fib_mgr : Platform upd failed traceback console messages were seen for CGSE
Symptom:
Following error message is observed on the console once (while service interface creation) or in very rare cases every 15 seconds on a CGSE LC.
LC/0/7/CPU0:Jan 25 17:48:07.576 : fib_mgr[163]: %ROUTING-FIB-3-PLATF_UPD_FAIL: Platform upd failed: Obj=DATA_TYPE_NHINFO[ptr=a40c65dc,refc=0,flags=0]Action=CREATE Proto=ipv6. Cerr=Invalid argument : pkg/bin/fib_mgr :(PID=122975) : -Traceback= 4d270a9c 4005e144 400683fc 40069c44 4006c8244006cca4 400a15c0 400a1a70 400071c4 4c2146b8 4c2127d4 400004fc 4000f6c8 4c2943c4LC/0/0/CPU0:Aug 7 01:26:40.960 : fib_mgr[146]: %ROUTING-FIB-3-PLATF_UPD_FAIL: Platform upd failed: Obj=DATA_TYPE_NHINFO[ptr=7a9e7ed4,refc=0x1,flags=0]Action=MODIFY Proto=ipv4. Cerr=Invalid argument : pkg/bin/fib_mgr :(PID=86104) : -Traceback= f90745d0 48255c10 4825c5d4 48261c70 48262988f917ac34 f8209120 f8206f88 48200f08 4820cff8 f82895ecThis message is seen on both Active and Standby CGSE linecards.
Conditions:
This symptom is observed when one of the following conditions occur:
Configuring/modifying Service interfaces on a CGSE PLIM.
CGSE Reload.
Delete one / more already configured serviceapp interfaces from a stable system and you follow it up with a fib_mgr or an aib restart on that CGSE linecard.
Workaround:
No workaround other than CGSE linecard OIR.
•
Basic Description:
Upgrade from Cisco IOS XR software release 3.9.x to Cisco IOS XR software release 4.0.0 fails with CGN PIE
Symptom:
Upgrade from Cisco IOS XR software release 3.9.x to Cisco IOS XR software release 4.0.0 fails with CGN PIE. There is no issue if there is no CGN PIE involved in the upgrade.
Conditions:
Seen while upgrading from Cisco IOS XR software release 3.9.x to Cisco IOS XR software release 4.0.0.
Workaround:
Remove the CGN PIE and upgrade from Cisco IOS XR software release 3.9.x to Cisco IOS XR software release 4.0.0 and than install the CGN PIE.
Similar workaround needs to be applied if you downgrade from Cisco IOS XR software release 4.0.0 to Cisco IOS XR software release 3.9.x.
Procedure for Workaround
Step 1
Step 2
Step 3
Step 4
Step 5
Note
•
Basic Description:
CSCth49227 in 4.0.1 broke the fix for CSCti55946
Symptom:
Upgrade from Cisco IOS XR software release 3.9.x to Cisco IOS XR software release 4.0.1 fails with CGN PIE. There is no issue if there is no CGN PIE involved in the upgrade.
Conditions:
Seen while upgrading from Cisco IOS XR software release 3.9.x to Cisco IOS XR software release 4.0.1.
Workaround:
Remove the CGN PIE and upgrade from Cisco IOS XR software release 3.9.x to Cisco IOS XR software release 4.0.1 and than install the CGN PIE.
Similar workaround needs to be applied if you downgrade from Cisco IOS XR software release 4.0.1 to Cisco IOS XR software release 3.9.x.
Procedure for Workaround
Step 1
Step 2
Step 3
Step 4
Step 5
Resolved Cisco IOS XR Software PSIRT-Related Caveats
•
Basic Description:
BGP flaps due to unknown attribute
Symptom:
Cisco IOS XR Software contains a vulnerability in the Border Gateway Protocol (BGP) feature. The vulnerability manifests itself when a BGP peer announces a prefix with a specific, valid but unrecognized transitive attribute. On receipt of this prefix, the Cisco IOS XR device will corrupt the attribute before sending it to the neighboring devices. Neighboring devices that receive this corrupted update may reset the BGP peering session.
Conditions:
Affected devices running Cisco IOS XR Software corrupt the unrecognized attribute before sending to neighboring devices, but neighboring devices may be running operating systems other than Cisco IOS XR Software and may still reset the BGP peering session after receiving the corrupted update. This is per standards defining the operation of BGP.
Workaround:
No workaround. Cisco developed a fix that addresses this vulnerability and will be releasing free software maintenance upgrades (SMUs) progressively starting 28 August 2010.
A Security Advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20100827-bgp.shtml
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
Troubleshooting
For information on troubleshooting Cisco IOS XR software, refer to the Cisco IOS XR Troubleshooting Guide for the Cisco CRS-1 Router and the Cisco IOS XR Getting Started Guide for the Cisco CRS-1 Router.
Related Documentation
The most current Cisco CRS-1 Router hardware documentation is located at the following URL:
http://www.cisco.com/en/US/products/ps5763/tsd_products_support_series_home.html
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. See About Cisco IOS XR Software Documentation for Release 3.9 for a list of Cisco IOS XR Release 3.9.1 software documentation.
The most current Cisco CRS-1 Router software documentation is located at the following URL:
http://www.cisco.com/en/US/products/ps5763/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 What's New in Cisco Product Documentation at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html.
Subscribe to What's New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation, as an RSS feed and deliver content directly to your desktop using a reader application. The RSS feeds are a free service.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned 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. (1110R)
© 2010 Cisco Systems, Inc. All rights reserved.
