Documente Academic
Documente Profesional
Documente Cultură
Download the tar file (rommon-2.1.tar), untar it on a PC and copy the binaries to disk0:
The following files should be on the flash disk (only the ppc files are required):
Step 2
rommon--hfr--ppc7450--sc--dsmp--A.bin
rommon--hfr--ppc7450--sc--dsmp--B.bin
rommon--hfr--ppc7455--asmp--A.bin
rommon--hfr--ppc7455--asmp--B.bin
rommon--hfr--ppc8255--sp--A.bin
rommon--hfr--ppc8255--sp--B.bin
rommon--hfr--ppc8347--sp--A.bin
rommon--hfr--ppc8347--sp--B.bin
Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide
OL-13669-03
A-1
Appendix A
Please do not power cycle, reload the router or reset any nodes until all upgrades are
completed.
Please check the syslog to make sure that all nodes are upgraded successfully. If you
need to perform multiple upgrades, please wait for current
13 upgrade to be completed before proceeding to another upgrade. Failure to do so may
render the cards under upgrade to be unusable.
RP/0/RP0/CPU0:Oct 13 14:00:06.596 : upgrade_daemon[358]: Running rommon upgrade
RP/0/RP1/CPU0:Oct 13 14:00:06.600 : upgrade_daemon[358]: Running rommon upgrade
SP/0/SM3/SP:Oct 13 14:00:06.657 : upgrade_daemon[130]: Running rommon upgrade [SNIP]
Step 3
Verify that ROMMON B was upgraded successfully by executing the show logging command.
RP/0/RP0/CPU0:CRS-C(admin)#show logging | inc is programmed successfully
RP/0/RP0/CPU0:Oct 13 14:00:13.566 : rommon_burner[65770]: %PLATFORM-ROMMON_BURNER--5--progress : ROMMON B is programmed successfully.
RP/0/RP0/CPU0:Oct 13 14:00:13.523 : syslog_dev[83]: upgrade_daemon[358]: OK, ROMMON B
is programmed successfully.
RP/0/RP0/CPU0:Oct 13 14:00:13.580 : syslog_dev[83]: upgrade_daemon[358]: OK, ROMMON B
is programmed successfully. [SNIP]
Step 4
Now you can upgrade ROMMON A with the following command from admin mode:
RP/0/RP0/CPU0:CRS-1(admin)#upgrade rommon a all disk0
Step 5
Verify that ROMMON A was upgraded successfully by executing the show logging command.
RP/0/RP0/CPU0:CRS-C(admin)#show logging | inc is programmed successfully
RP/0/RP0/CPU0:Oct 13 14:00:13.566 : rommon_burner[65770]: %PLATFORM-ROMMON_BURNER--5--progress : ROMMON A is programmed successfully.
RP/0/RP0/CPU0:Oct 13 14:00:13.523 : syslog_dev[83]: upgrade_daemon[358]: OK, ROMMON B
is programmed successfully.
RP/0/RP0/CPU0:Oct 13 14:00:13.580 : syslog_dev[83]: upgrade_daemon[358]: OK, ROMMON B
is programmed successfully. [SNIP]
Note
Note
To save an additional reload the new ROMMON can be activated together with the turboboot.
Turboboot Instructions
Step 1
When the system comes back up, take note of the ROMMON version in the pre-loading information. The
version should reflect the new updated ROMMON.
PCI1 device[3]: Device ID 0x5618
PCI1 device[3]: Vendor ID 0x14e4
Configuring MPPs ...
Configuring PCMCIA slots ...
System Bootstrap, Version 2.1(20100723:223432) [CRS--1 ROMMON],
Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide
A-2
OL-13669-03
Appendix A
Step 2
This will bring the standby RP in a booting loop. If you turboboot a MC this has to be done on all
nonDSC RPs. The RP(s) will remain in the booting loop (mbi hunt) until they receive a MBI
confirmation with the remote image to boot from the active RP of the DSC. The MBI confirmation will
be received once the active RP on the DSC has booted the mini image. Refer to the next step.
Step 3
Configure the rommon variables on the active RP and boot the vm image.
Rommon1>IP_ADDRESS=<a.b.c.d>
Rommon2>IP_SUBNET_MASK=<mask>
Rommon3>TFTP_SERVER=<a.b.c.d>
Rommon4>DEFAULT_GATEWAY=<a.b.c.d>
Rommon5>unset BOOT
Rommon6>TURBOBOOT=on,disk0,format
Rommon7>sync
Rommon8>boot tftp://a.b.c.d/path/hfr-mini-px.vm-4.0.0
Instead of a tftp server disk1 can be specified as well. But this will take significant longer
Warning
Do NOT use the option "formatif you migrate to a flash disk formatted with the FAT32 file system or if
you have a flash disk formatted with FAT32.
The installation is complete when all nodes on the system are in state "IOS XR RUN" and the standby
RP is "NSR-ready.
Example
RP/0/RP0/CPU0:router#sh red
Wed Oct 13 09:33:43.367 UTC
Redundancy information for node 0/RP0/CPU0:
==========================================
Node 0/RP0/CPU0 is in ACTIVE role
Partner node (0/RP1/CPU0) is in STANDBY role
Standby node in 0/RP1/CPU0 is ready
Standby node in 0/RP1/CPU0 is NSR--ready
Reload and boot info
--------------------RP reloaded Wed Oct 13 09:23:20 2010: 10 minutes ago
Active node booted Wed Oct 13 09:23:20 2010: 10 minutes ago
Standby node boot Wed Oct 13 09:24:00 2010: 9 minutes ago
Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide
OL-13669-03
A-3
Appendix A
Standby node last went not ready Wed Oct 13 09:33:14 2010: 29 seconds ago
Standby node last went ready Wed Oct 13 09:33:15 2010: 28 seconds ago
There have been 0 switch--overs since reload
Active node reload "Cause: Turboboot completed successfully"
Standby node reload "Cause: MBI--HELLO reloading node on receiving reload
notification"
Step 4
When the turboboot installation is complete the optional PIEs can be added and activated from admin
mode.
Example
router(admin)# install add source tftp://10.1.1.1/users/bla/ hfr--mcast-- px.pie-4.0.0.T hfr--mgbl--px.pie--4.0.0.T hfr--mpls--px.pie--4.0.0.T hfr-k9sec--px.pie--4.0.0.T hfr-- diags--px.pie--4.0.0.T sync
router(admin)# install activate disk0:hfr--mcast--4.0.0.T disk0:hfr--mgbl-4.0.0.T disk0:hfr--k9sec--4.0.0.T disk0:hfr--mpls--4.0.0.T disk0:hfr-diags--4.0.0.T sync
12 minutes for the system to reload and boot up to standby ready state and all line cards in IOS XR
RUN
Warning
Rolling back down to Cisco IOS XR software Release 3.7.2 or lower (which does not support a FAT32
boot disk) is much more difficult after the file system and partition has been changed to the FAT32
format. If you want to have an easy rollback capability, do not change the file system to FAT32 until
you are upgrading from a Split Boot supported image to another Split Boot support image. Changing
the file system is only possible when running Cisco IOS XR software Release 3.8 or higher.
Also, using the CLI based format command will change the file system back to FAT16.
Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide
A-4
OL-13669-03
Appendix A
Step 1
Attach to the Standby RP by typing the command run attach 0/rp1/cpu0 at the router prompt
Example with Standby RP at 0/RP1/CPU0.
RP/0/RP0/CPU0:Router#run attach 0/rp1/cpu0
attach: Starting session 1 to node 0/rp1/cpu0
Note
Step 2
KSH commands are very unforgiving. Please pay very close attention to make sure the
commands are entered exactly as listed in this procedure.
Step 3
At the KSH prompt, enter the command fdisk /dev/disk0 add -t6 -p88
# fdisk /dev/disk0 add -t6 -p88
Step 4
At the KSH prompt, enter the command fdisk /dev/disk0 add -t4 -p100
# fdisk /dev/disk0 add -t4 -p100
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Execute the reload location 0/RP1/CPU0 command in Admin Mode to reload the Standby RP at
0/RP1/CPU0:
RP/0/RP0/CPU0:Router(admin)# reload location 0/RP1/CPU0
Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide
OL-13669-03
A-5
Appendix A
Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide
A-6
OL-13669-03