Cisco Cisco IOS XR Software Release 4.0
54
Release Notes for Cisco ASR 9000 Series Aggregation Services Routers for Cisco IOS XR Software Release 4.0.3
OL-24346-01
Upgrading Cisco IOS XR Software
There are no workarounds for set-actions for qos-group/discard-class for BVI traffic. For L2->BVI
path, DSCP of the packet could be modified using an ingress policy, which would set exp based on
the modified DSCP.
path, DSCP of the packet could be modified using an ingress policy, which would set exp based on
the modified DSCP.
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 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. Refer to
software components. Refer to
Table 1
for a list of the Cisco ASR 9000 Series Router software feature
set matrix (PIE files) and associated filenames available for the Cisco IOS XR Software Release 4.0.3
supported on the Cisco ASR 9000 Series Router.
supported on the Cisco ASR 9000 Series Router.
The following URL contains links to information about how to upgrade Cisco IOS XR software:
For information on troubleshooting Cisco IOS XR software, see the
Cisco ASR 9000 Series Aggregation Services Routers Getting Started Guide and the Cisco ASR 9000
Series Router Troubleshooting Feature Module.
Cisco ASR 9000 Series Aggregation Services Routers Getting Started Guide and the Cisco ASR 9000
Series Router Troubleshooting Feature Module.
Resolving Upgrade File Issues
Note
In some very rare cases inconsistencies in the content of the internal configuration files can
appear. In such situations, to avoid configuration loss during upgrade, the following steps can be
optionally done before activating packages:
appear. In such situations, to avoid configuration loss during upgrade, the following steps can be
optionally done before activating packages:
a.
Clear the NVGEN cache:
RP/0/RSP0/CPU0:PE44_ASR-9010# run nvgen –F 1
b.
Create a dummy config commit:
RP/0/RSP0/CPU0:PE44_ASR-9010# config
RP/0/RSP0/CPU0:PE44_ASR-9010(config)# hostname <hostname>
RP/0/RSP0/CPU0:PE44_ASR-9010(config)# commit
RP/0/RSP0/CPU0:PE44_ASR-9010(config)# end
c.
Force a commit update by using the reload command. Press “n” when the confirmation prompt
appears:
appears:
RP/0/RSP0/CPU0:PE44_ASR-9010# reload
Updating Commit Database. Please wait...[OK]
Proceed with reload? [confirm]
d.
Press “n”.
In some cases other activity may preclude a reload. The following message may display: