These release notes describe the features provided in Cisco IOS XR Software Release 3.4.2 and are updated as needed.

For a list of software caveats that apply to Cisco IOS XR Software Release 3.4.2, see the "Caveats" section. The caveats are updated for every release and are located on the World Wide Web at www.cisco.com.

•Quality of service (QoS)—Supports rich QoS mechanisms, including policing, marking, queuing, dropping, and shaping. Additionally, the operating systems support modular QoS command-line interface (MQC). MQC is used to configure various QoS features on various Cisco platforms.

•Craft Works interface (CWI)—The CWI is a client-side application used to configure and manage Cisco routers. The 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.

•In Service Software Upgrade (ISSU)—Supports a modular-packaging-based release model to minimize impact of upgrades and supports ISSU with NSF, where possible.

•SDR—Secure domain router (SDR) is a full-function router that is partitioned from one physical router running IOS XR. Each SDR can act as an independent router and perform all routing function as a physically separate router. SDR provides hardware fault isolation amongst other SDR running in router. SDR shares limited resource, such as fabric, power, and cooling. SDR allows multiple end-to-end service specific network aggregation on one physical router. SDR allows the ability to collapse many smaller service routers into one system. At a minimum, a management node such as RP/DRP and line card is needed to create SDR. SDR provides levels of isolation where a bug fix patch can be installed on an SDR without affecting other SDRs. SDRs interconnect using physical line card ports.

System Requirements

The Cisco IOS XR Software Release 3.4.2 is supported on the following platforms:

Important Notes

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.

When upgrading a Cisco XR 12000 Series Router from Cisco IOS to Cisco IOS XR software, follow the upgrade instructions provided to minimize traffic impact. For detailed instructions, see the Upgrading from Cisco IOS to Cisco IOS XR Software on the Cisco 12000 Series Router document for procedures.

Follow the instructions provided by Cisco for all card removal and replacement (fabric cards, line cards, fan controller and RP, and so on) to avoid impact to traffic. See the Cisco IOS XR Getting Started Guide for procedures.

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

Cisco SIP-600 line cards (for the Cisco XR 12000 Series Router) draw more power than previous 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 off 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.

Quality of Service Units of Measure Changes

Because the default units of measure may no longer be the same, care must be taken when taking a configuration earlier than Cisco IOS XR Software Release 3.3.0 and applying it to Cisco IOS XR Software Release 3.3.0 or later. Table 6 lists the changes to Quality of Service (QoS) units of measure.

Table 6 Changes to Quality of Service Units of Measure

Command

Cisco IOS XR Release 3.2 (Default)

Cisco IOS XR Release 3.3.x and Cisco IOS XR Release 3.4.x (Default)

bandwidth

kbps

kbps

police rate

kbps

bps (change)

queue-limit

bytes

packets (change)

random-detect

bytes

packets (change)

shape average

kbps

packets (change)

Note The default units of measure (see Table 6) will be inserted into the QoS policy following the upgrade. This will result in a change to the policy's behavior. Therefore, manual review and keyword changes must be performed by the operator to ensure the policy operates as expected.

Keywords cannot be inserted into the running configuration on a router running Cisco IOS XR Release 3.2.x in advance of the upgrade. An option is to edit the configuration offline, and add the necessary keywords.

Note To make change to a QoS policy, the policy must first be removed from any interfaces making a reference to it.

To remove a service policy from an input or output interface, use the no form of the service-policy command in interface configuration mode, as shown in the following syntax:

no service-policy {input | output}

When the policy is removed from any interfaces, the edited policy is applied. See the following Cisco IOS XR command reference sections:

Platform-Independent Caveats

The following caveats apply to Cisco CRS-1 and Cisco XR 12000 Series Routers:

Note Secure domain routers should be configured with lower case letters in order for specific installation operations to succeed. For more information, see the Cisco IOS XR Getting Started Guide, Release 3.4 on Cisco.com.

•CSCse83983

Basic Description:

IA tunnel does NOT go down and come up on topo change in non-head area.

Symptom:

When IOS XR Release 3.4 MPLS Traffic Engineering node is a non-head area node and there is a topology change triggered either due to IGP link add/removal or any other topology change in the IGP (say) Level 1 to Level 2 for the links on that node. The inter-area tunnels originating from the Head and going via that link will NOT flap as a result of this topology change.

Conditions:

This behavior is seen in IOS XR Release 3.4 in a non-head area node and inter-area TE tunnel is being setup with loose hop in the path ERO.

Additional Notes:

Path verification and tunnel reoptimization indication are not done by the midpt ABR node. This is similar to the IOS behavior today. This feature will be added in a future release.

Workaround:

None.

•CSCse97786

Basic Description:

L2VPN: Control word cant be set if PW is established with cbit=0

Symptom:

Router not sending Control Word even when Controlk word is enabled.

Conditions:

If a PW is established with cbit=0, and later using config we enabled control word or if neighbor sends a label mapping with control word cbit=1, IOX will still send cbit=0.

Workaround:

The workaround is to delete and reconfigure the PW on both the PE's

•CSCse80235

Basic Description:

L2VPN: Support destination with Rtg ID different than LDP rtr Id

Symptom:

Can't establish PW to a non LDP router ID address

Conditions:

PW can be established on to the LDP router ID. Currently IOX does not support PW to non LDP router ID's

Workaround:

None

•CSCsi59202

Basic Description:

`show mpls lsd forwarding' displays invalid format_tbl:136

Symptom:

`show mpls lsd forwarding' displays invalid format_tbl:136

Conditions:

Under normal scenarios.

Workaround:

There is no workaround for this as of now.

Cisco CRS-1-specific Caveats

The following caveats are specific to the Cisco CRS-1 platform:

•CSCsg18108

Basic Description:

netio process restarts when trying to restore config from disk.

Symptom:

An unexpected Netio process termination may occur when trying to restore configuration from disk or when changing the encapsulation of an interface from ppp to hdlc and vice versa.

Conditions:

Condition1: If the router has POS or serial interfaces and the configuration is cleared using following commands:

–commit replace

–yes

–end

And then restored back from disk, the netio process can terminate.

Condition 2: If the encapsulation of serial interface is changed repeatedly from ppp to hdlc and viceversa, and if the packets are being sent out of that interface at the same time, the netio process can terminate

Workaround:

Workaround for Condition 1: When loading the configuration from disk, make sure the POS and serial interfaces are in a shut-down state. Once the configuration is loaded, the interfaces can be enabled again.

Workaround for Condition 2: If there is a need to change the encaps of a serial or POS interface, shut the interface before changing the encapsulation. The interface can be enabled after the configuration change has been made.

•CSCsh45459

Basic Description:

Line protocol state for SONET controller should be admin-down after LC reload.

Symptom:

When shutting down the SONET controller, Intf/LineP state shown in show controllers sonet should be admin-down/admin-down. However, LineP goes to the down state after LC reload.

Conditions:

After the LC reload.

Workaround:

No shutdown the controller once then shutdown it again.

•CSCsh48689

Basic Description:

Unable to upgrade FPD for oc3/12 SPA.

Symptom:

FPGA upgrade may fail on OC3/12 SPA in a named SDR.

Conditions:

Normal operation.

Workaround:

Move the card in owner SDR, upgrade the FPGA and move it back to the named SDR.

•CSCsj09823

Basic Description:

syslogd process crashed.

Symptom:

syslogd process crashed.

Conditions:

The logging level was debug and cctl debugs were enabled.

Workaround:

The syslogd process was automatically restarted.

•CSCsj24973

Basic Description:

After FailOver instdir process crashed twice on RP.

Symptom:

After FailOver instdir process crashed twice on RP.

Conditions:

Active RP reload.

Workaround:

None. The instdir process was restarted after the two crashed.

•CSCsj10619

Basic Description:

Garbled character of authentication string on "show vrrp detail".

Symptom:

The last portion of the string value for "show vrrp detal" command is garbled.

Conditions:

When the eight alphanumeric characters are used by "authentication string" for VRRP.

Workaround:

None. The string value of "show vrrp detail" is normal when the alphanumeric characters from one to seven are used for authentication.

Cisco XR 12000 Series Router-specific Caveats

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

•CSCsj08727

Basic Description:

CEF is inconsistent on active and standby RP.

Symptom:

After "hw-module reload loc all" on dual rp system when mgmt subnet has multiple interfaces mgmt-1 on actv rp and mgmt-2 on sby rp, it is possible that CEF entry for a nbr hanging of this connected subnet can be criss-crossed on act/sby rp. As result of this when pkt to such nbr is to be sent out of rtr, it can loop between Act/Sby rp and result in high cpu util on act/sby rp (fabric_driver_rp).

Conditions:

This happens only when we execute "hw-module reload loc all" on a router which has dual RP card.

Recovery:

shut/unshut of mgmt interface of the standby rp.

•CSCsi46306

Basic Description:

ipv4_io_ea times out during commit replace due to FIB

Symptom:

commit replace from an empty config to a scaled config like FR with 4k DLCIs causes ipv4_io_ea timeout.

Conditions:

The user has to have an empty or minimal config and swtch to the scaled config like FR with 4k DLCIs.

Workaround:

None.

•CSCsj21527

Basic Description:

acl not getting attached to the interface

Symptom:

When we do a SPA OIR follwoed by a redundancy switchover and if the SPA interfaces are going to have ACL configs attached to its interfaces we will hit with this issue.

Conditions:

This only happens if the following 2 conditions are met1.If you have acl configs attached to the interfaces of a SPA.2.and if you a do SPA OIR immediately followed by a redundancy switchover.

Recovery:

Reapply the acl configs into the interfaces after the redundancy switchover.

•CSCsj19998

Basic Description:

qos service policies not getting attached to interface after SPA OIR

Symptom:

When we do a SPA OIR follwoed by a redundancy switchover and if the SPA interfaces are going to have qos service policy configs attached to its interfaces we will hit with this issue.

Conditions:

This only happens if the following 2 conditions are met1.If you have qos service policy configs attached to the interfaces of a SPA.2.and if you a do SPA OIR immediately followed by a redundancy switchover.

Recovery:

Reapply the qos service policy configs into the interfaces after the redundancy switchover.

Resolved Cisco IOS XR Software PSIRT-Related Caveats

•CSCti62211

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.

Note Before you install or upgrade the software, you must upgrade the ROM Monitor software to the correct version. If a Cisco CRS-1 system running Cisco IOS XR software Release 3.4.2 is brought up with the incorrect ROM Monitor software, the standby RP fails to boot and an error message appears. For information on correct ROM Monitor software on a single-shelf router, see "Upgrading and Downgrading ROM Monitor Software on Cisco CRS-1 Routers" in the Cisco IOS XR ROM Monitor Guide.

Troubleshooting

See the Cisco IOS XR Getting Started Guide for information on troubleshooting the Cisco IOS XR software.

Related Documentation

The following sections describe the documentation available for the Cisco CRS-1 and Cisco XR 12000 Series Router. These documents consist of hardware and software installation guides, Cisco IOS XR software configuration and command references, feature modules, and other documents.

Documentation is available as electronic documents, which are available online on Cisco.com.

Software Documents

The Cisco IOS XR software documentation set consists of the Cisco IOS XR software configuration guides and command references, a getting started guide, and other supporting documents. See the About Cisco IOS XR Software Documentation for Release 3.4.0 for a list of Cisco IOS XR software documentation for Release 3.4.2.

Obtaining Documentation, Obtaining Support, and Security Guidelines

For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

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)

Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.