Cisco Cisco IOS XR Software Release 3.2

Use the following procedure to install the SMU on the Cisco CRS-1:

Add the hfr-admin-3.0.1.CSCeh04631.pie SMU to disk0:.

RP/0/RP0/CPU0:router# install add <device or 
tftp:/ftp:/rcp:>/hfr-admin-3.0.1.CSCeh04631.pie to disk0:

Activate the hfr-admin-3.0.1.CSCeh04631-1.0.0 SMU.

RP/0/RP0/CPU0:router# install activate disk0:hfr-admin-3.0.1.CSCeh04631-1.0.0

Enter the install commit command to commit the SMU and save the active software set to be persistent 
across route reloads.

RP/0/RP0/CPU0:router# install commit

Before performing an upgrade, perform the following pre-upgrade checks on the Cisco CRS-1:

Verify system stability through commands described in 

.

Verify that the ROMMON is at least version 1.32. If not, see 

 to upgrade the ROMMON. 

Back up running-config prior to upgrade, as follows: 

RP/0/RP0/CPU0:router# copy running-config storage_device

Run the following command and note the latest rollback point available before performing the upgrade:

RP/0/RP0/CPU0:router# show install rollback ?

Verify that all applicable mandatory SMUs are active on the router. Optional packages and SMUs can 
also be active on the system. If any of the mandatory SMUs are not active, they must be activated before 
proceeding with the upgrade.

Make sure all your files on the RP/standby RP/LC/SP boot flashes are backed up:

RP/0/RP0/CPU0:router# copy bootflash:/source harddisk:/destination

SMU Filename

hfr-admin-3.0.1.CSCeh04631.pie 

DDTS

CSCeh04631: Downgrade to 3.0 from 3.2 caused failover problems 
with MBI error.

SMU Install Impact

Low. There should be no impact to running system.

Problem Summary

Without this SMU, any node reload (or failover) causes the system to 
re-sync all of the packages on the booting node, resulting in longer 
boot up time. This is caused by non-backward-compatible MBI 
related changes made in Release 3.2.2.