•BGP Prefix Independent Convergence—Provides the ability to converge BGP routes within sub seconds instead of multiple seconds. The Forwarding Information Base (FIB) is updated, independent of a prefix, to converge multiple 100K BGP routes with the occurrence of a single failure. This convergence is applicable to both core and edge failures and with or with out MPLS. This fast convergence innovation is unique to Cisco IOS XR software.

•Craft Works Interface (CWI)—CWI is a client-side application used to configure and manage Cisco routers. Management and configuration features include fault, configuration, security, and inventory, with an emphasis on speed and efficiency. The CWI provides a context-sensitive graphical representation of the objects in a Cisco router, simplifying the process of configuring and managing the router. The CWI allows you to log in to multiple routers and perform management tasks.

•6VPE over L2TPv3 support—Delivers IPv6 VPN traffic over L2TPv3 core with 6VPE support. This feature is also available on Cisco IOS software.

•Enhanced core competencies:

–IP fast convergence with Fast Reroute (FRR) support for Intermediate System-to-Intermediate System (IS-IS) and OSPF

–Path Computation Element (PCE) capability for traffic engineering

•L2TPv3 Tunneling Mechanism—Service Providers who do not use MPLS in the core, but want to offer VPN services can use the L2TPv3 tunneling mechanism. This feature support includes IPv4 (VPNv4) and IPv6 (6VPE) VPN services using L2TPv3 encapsulation. The L2TPv3 packet is encapsulated in an IPv4 delivery header and is carried across an IPv4 backbone. VPN prefixes are advertised with BGP labels and resolved over L2TPv3 tunnels. This feature is supported only on the Cisco XR 12000 Series Router.

Note If you are running Cisco IOS XR software on a Cisco XR120xx system with SIP 600, 401, 501, or 601, you must upgrade the fabric. For ROMMON, MBUS, and Fabric Downloader versions, see the "Other Firmware Support" section.

Other Firmware Support

The Cisco XR 12000 Series Router supports the following firmware code:

Minimum Firmware Requirement

•After completing an RMA the newly-received linecard may not have appropriate IOS XR firmware installed.

Depending on the type of firmware that needs upgrading the symptoms can vary as follows:

–ROMMON needs updating the linecard will not boot up

–MBUS needs updating the linecard may fail to boot or keeps reloading

–Fabric Loader needs updating the linecard will take long time to boot

–FPD needs updating the linecard experiences packet corruption / drop

Note The FPD PIE has to be installed in order to upgrade to the latest FPD image. Refer to the Upgrading FPD on Cisco IOS XR Software chapter of the Cisco IOS XR System Management Command Reference for the Cisco XR 12000 Router online.

RMA Card Firmware Upgrade Procedure:

To upgrade the fabric-downloader, ROMMON, Mbus, and current field-programmable device (FPD) image package on a single RMA linecard or on all modules installed in a router, use the upgrade all command in administration EXEC mode.

upgrade all location {node-id | all} [force]

Where location node-id specifies that all all firmware images (ROM, MBUS, Fabric Downloader and FPD) will be upgraded on the physical location of the line card received through RMA defined by the node-id argument. The node-id argument is entered in the rack/slot/module notation.

The upgrade all locationall commandupgrades all all firmware images (ROM, MBUS, Fabric Downloader and FPD) on all line cards (LCs) that are installed in the router.

For an RMA linecard firmware upgrade you'll want to use the upgrade all locationnode-id command.

The optional force parameter skips the version check and forces an upgrade.

•The list of minimum supported firmware versions is available online in this matrix:

•Refer to the Hardware Redundancy and Node Administration Commands on Cisco IOS XR Software chapter of the Cisco IOS XR System Management Command Reference for the Cisco XR 12000 Router for the upgrade all command syntax:

Requirement of Cisco IOS Image Level and Boot Helper Version for Migration

If you are migrating from Cisco IOS to Cisco IOS XR software on the Cisco XR 12000 Series Router, you must have the following minimum Cisco IOS image level and Boothelper version to support Release 3.9.1:

•Cisco IOS image—12.0(32)S

•Cisco IOS Boothelper—12.0(32)S0a

If you have an earlier version of this system, you must upgrade to the minimum supported level before performing a migration. Otherwise, your migration fails. For more information, see the Migrating from Cisco IOS to Cisco IOS XR Software on the Cisco XR 12000 Series Router document.

Determining 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:

Important Notes

•Default timestamp setting—The timestamp prompt that precedes console output is enabled by default in Cisco IOS XR Release 3.8. To disable the timestamp prompt, use the no service timestamp command. For more information, refer to the Cisco IOS XR System Management Command Reference for the Cisco XR 12000 Series Router.

•From Cisco IOS XR Software Release 3.6.0, WRED statements are collapsed in that if different random-detect statements using the same match types (EXP, DSCP, Prec, and so forth) are entered with identical minimum and maximum threshold values, a single configuration line is shown in the output of show running config. This reduces the length of the configuration but creates a problem with backward compatibility with previous releases. In such a situation, on rollback, the QoS policy is rejected and must be manually entered again.

Configuration prior to Cisco IOS XR Software Release 3.6.0:

Policy-map wred_example

Class class-default

random-detect exp 0 384 packets 484 packets

random-detect exp 1 384 packets 484 packets

random-detect exp 2 384 packets 484 packets

random-detect exp 3 484 packets 584 packets

random-detect exp 4 484 packets 584 packets

random-detect discard-class 0 384 packets 484 packets

random-detect discard-class 1 384 packets 484 packets

random-detect discard-class 2 484 packets 584 packets

bandwidth remaining percent 20

Cisco IOS XR Software Release 3.6.0 and later releases:

policy-map wred_example

class class-default

random-detect exp 0,1,2 384 packets 484 packets

random-detect exp 3,4 484 packets 584 packets

random-detect discard-class 0,1 384 packets 484 packets

random-detect discard-class 2 484 packets 584 packets

bandwidth remaining percent 20

!

end-policy-map

!

end

In 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.

•Country-specific laws, regulations, and licences—In certain countries, use of these products may be prohibited and subject to laws, regulations, or licenses, including requirements applicable to the use of the products under telecommunications and other laws and regulations; customers must comply with all such applicable laws in the countries in which they intend to use the products.

•Migrating from Cisco IOS to Cisco IOS XR Software on the Cisco XR 12000 Series Router—When migrating a Cisco XR 12000 Series Router from Cisco IOS to Cisco IOS XR software, follow the instructions provided in Migrating from Cisco IOS to Cisco IOS XR Software on the Cisco XR 12000 Series Router.

•Card, fan controller, and RP removal—For all card removal and replacement (including fabric cards, line cards, fan controller, and RP) follow the instructions provided by Cisco to avoid impact to traffic. See theCisco IOS XR Getting Started Guide for the Cisco XR 12000 Series Router for procedures.

•Exceeding Cisco testing—If you intend to test beyond the combined maximum configuration tested and published by Cisco, contact your Cisco Technical Support representative to discuss how to engineer a large-scale configuration maximum for your purpose.

•More power required for Cisco SIP line cards (SIP-401/501/600/601) on the Cisco XR 12000 Series Router—These line cards draw more power than previous generation line cards. Depending on the exact configuration of power entry modules (PEMs) and other cards in the chassis, there may not be enough power available when inserting a new card or removing a PEM. Before you insert a new card or remove a PEM, run the following command in admin mode:

RP/0/0/CPU0:router# admin

RP/0/0/CPU0:router# show environment power-supply table

48V Current

R/S/I Module (V) (A)

0/24/* PEM1 54 4

PEM2 53 4

0/25/* PEM1 54 4

PEM2 53 4

Total Power Supplies: 3200W

Redundant Power Supplies: 1600W

Worst Case Power Used: 621W

Current Power Used: 428W

Current Redundant Power Available: 1172W

Current Total Power Available: 2772W

Worst Case Redundant Power Available: 979W

Worst Case Total Power Available: 2579W

PID Description Watts

--- ----------- -----

GRP-B Route Processor 38

PRP-1 Cisco 12000 Series Performance Route Processor 60

LC-4OC-3-POS-SM 4 Port Packet Over SONET OC-3c/STM-1 80

4OC3X/POS-MM-MJ-B 4 port ISE OC3 90

If you plan to insert a new card, locate the entry for the card to be inserted and note the power consumed by it. If this power is less than the figure given in Worst Case Redundant Power Available (the figure is displayed in the show environment power-supply table command output), the card can be safely inserted. As long as the Worst Case Redundant Power Available is not zero, a PEM can be powered down for replacement without impact.

Note No alerts are issued if more cards are inserted than the PEMs can support. It is your responsibility to determine your power budget for the chassis before making any changes to it. Exceeding the power budget may result in the PEM being overloaded and cards powering down due to insufficient power being provided.

•Per-interface Internet Control Message Protocol (ICMP) disable feature is not supported on the Cisco XR 12000 Series Router.

•Online Diagnostics is not supported on the Cisco XR 12000 Series Router—If you execute the diagnostic command, an error appears stating that there is no online diagnostics process running on the router.

•The rp mgmtethernet forwarding command is not supported on the Cisco XR 12000 Series Router.

•mpls traffic engineering igp-intact command—This command must be used only when policy based tunnel selection is configured for all tunnels originating on the device.

Caveats

This section contains caveats that are generic to the Cisco IOS XR Release 3.9.1 software and those specific to the Cisco XR 12000 Series Router.

Cisco IOS XR Caveats

The following open caveats apply to Cisco IOS XR Software Release 3.9.1 and are not platform specific:

•CSCtf93555

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.

•CSCte01589

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.

•CSCtd17516

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.

•CSCtf72035

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.

•CSCsy98575

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.

•CSCta71930

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.

•CSCti67148

Basic Description:

Optional task-maps not downloaded as part of exec authorization & Service exec tasks received from the TACACS server are not processed during AAA authorization

Symptom:

Command authorization fails:

RP/0/RP0/CPU0:router#show int desc

% This command is not authorized

RP/0/RP0/CPU0:router#

Conditions:

This happens:

–On a router running IOS XR 3.9.2 or 4.0.0. These are the only 2 versions affected. It did not happen before and it's fixed afterwards.

–Tacacs authorization is enabled.

–Router is supposed to retrieve its list of usergroup/taskgroup/task from the tacacs server through a service exec (optional) task configured on the tacacs server.

The problem with this bug is that the service exec tasks received from the tacacs server are not processed during aaa authorization with tacacs. So the user ends up with no task on the router and no command is authorized. Even though the command is permitted on the tacacs server.

Workaround:

Instead of using wild cards, explicitly name each package to be activated.

Recovery:

The way to make tacacs authorization work in 3.9.2 or 4.0.0 is through a privilege level:

–If privilege level 15 is assigned on the tacacs server, then user will end up with the tasks/commands of the group root-system.

–If privilege level 14 is assigned on the tacacs server, then user will end up with the tasks/commands of the group owner-sdr.

–If a privilege level between 1 and 13 (let's call it X), then we can configure a usergroup 'privX' on the router and the user will inherit the list of tasks of that group. For instance, if we want to have a user with all commands available, we can assign privilege level 13 on the router and configure this usergroup on the router:

usergroup priv13

taskgroup root-system

taskgroup cisco-support

•CSCti50227

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:

–Removing a set or policy referred by another policy that is attached to any attach point directly or indirectly.

–Modifying the policy to remove the reference to the same set or policy that is getting removed.

Workaround:

The commit must be performed in two steps:

1. Modify the policy to remove the reference to the policy or set and then commit.

2. Remove the policy or set and commit.

Caveats Specific to the Cisco XR 12000 Series Router

The following open caveats are specific to the Cisco XR 12000 Series Router:

•CSCtf95238

Basic Description:

POS Bundle not forwarding traffic after SPA /LC Reload

Symptom:

You have more than two members in a bundle. You have bundle max-active links set to 1. This is to ensure the other links are standby links. There is a trigger in the system( shut of the active link, reload of spa of active link, change of priority) so that the standby link has to become active. The other link becomes active but the adjacency has discard mtu set and traffic is not forwarded on this link. But OSPF stays up.

Conditions:

The problem occurs only in MPLS adjacency case and doesn't occur with IPv4. An example of the discard mtu set behavior is shown below.

QoS Set action for Ethernet traffic - 'set cos' will not work for Ethernet Layer2 Traffic egressing out of the system toward the customer cloud. While issue was raised on Local Switching, it can also be seen in AToM IPIW and L2TPv3 IPIW. This automatically means that any match actions done on the Customer System connected to the Ethernet interface will not work.

Workaround:

None. There is no workaround for this issue. If the set-cos policy is configured, it will not work. .

Recovery:

Recovery action is not needed here.

•CSCta86699

Basic Description:

Entity goes missing after RP Failover on the 16 slot c12000

Symptom:

Some subentities in the Entity-MIB go missing after RP FO. This condition occurs intermittently on a 16 slot GSR chassis.

Conditions:

On an RP failover on the 16 slot C12000 chassis, there is an intermittent condition in which subentities go missing.

Workaround:

None.

Recovery:

A forced failover or restart of the invmgr process should resolve the condition.

The issue is not seen when some time gap (~3-5 sec) is given between removing and re-adding OSPF process.

•CSCtg09403

Basic Description:

multilink MTU size is not pushed to member links

Symptom:

On a multilink bundle, when MTU is changed under the bundle interface, the value should be automatically pushed to all member links but this does not happen.

Conditions:

This applies to changing the MTU value of multilink bundles.

Workaround:

Set the MTU on all member links before adding to the bundle. Set the bundle MTU properly at creation time.

Recovery:

All member links need to be removed from bundle and then change their their MTU and finally set the MTU on the bundle itself. This will be service impacting.

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:

Troubleshooting

For information on troubleshooting Cisco IOS XR software, refer to the Cisco IOS XR Troubleshooting Guide for the Cisco XR 12000 Series Router and the Cisco IOS XR Getting Started Guide for the Cisco XR 12000 Series Router.

Related Documentation

The most current Cisco XR 12000 Series Router hardware documentation is located at the following URL:

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 XR 12000 Series Router software documentation is located at the following URL:

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.

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)