cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
108933
Views
65
Helpful
156
Comments
xthuijs
Cisco Employee
Cisco Employee



Introduction

This document provides an understanding of what Turboboot is and how to bring up a system running IOS-XR from scratch

There are two ways to upgrade the system:

  • One is to install add and activate the new XR software version. At a minimum this would require that mini.pie file
  • The second way is by performing a turboboot, fresh install, by booting the mini.vm file from rommon

This executable mini.vm file needs to be transferred via TFTP (on the RSP2) or can be loaded from the external USB port or TFTP (on the RSP440 and CRS-PRP). On the 9001 the USB ability is added in rommon 2.03 (5.1.1 release version).

No other media or protocols are possible to be used for a turboboot other then the ones specified above. Ex FTP is not allowed

File System overview

XR devices have multiple medias for storage and they all have their individual purpose.

 
VolumeRSP2RSP440TridentTyphoon
disk0:Embedded USBSSD (SATA)  
disk0a:Embedded USBSSD (SATA)  
disk1:Embedded USBSSD (SATA)  
disk1a:Embedded USBSSD (SATA)  
harddisk:Harddisk (SAS)Embedded USB  
harddiska:Harddisk (SAS)Embedded USB  
harddiskb:Harddisk (SAS)Embedded USB  
compactflash:Compactflash1External USB1  
lcdisk0:  Embedded USBEmbedded USB
lcdisk0a:  Embedded USBEmbedded USB
bootflash:NOR Flash NOR FlashNOR Flash
configflash:NOR Flash   
nvram:NVSRAMNVSRAM  
Kernel dumpHarddisk (SAS)SSD (SATA)TFTPbootflash:
 1. Removable   
     
Access (Mount) Points (in /dev)
VolumeRSP2RSP440TridentTyphoon
disk0:disk00t77hd0t77qsm to active rspqsm to active rsp
disk0a:disk00t78hd0t78qsm to active rspqsm to active rsp
disk1:disk10t77hd1t77qsm to active rspqsm to active rsp
disk1a:disk10t78hd1t78qsm to active rspqsm to active rsp
harddisk:hd0t79usb00t77qsm to active rspqsm to active rsp
harddiska:hd0t77usb00t78qsm to active rspqsm to active rsp
harddiskb:hd0t78usb00t11  
compactflash:disk20t6,11,121usb10t6,11,121  
lcdisk0:  lcdisk00t77lcdisk00t77
lcdisk0a:  lcdisk00t78lcdisk00t78
bootflash:fs0p1 fs0p1fs0p1
configflash:fs1p1   
nvram:nvramnvram  
Kernel dumphd0t80hd0t80 or hd1t802 fs0p2
 1. Any one2. Either one  
     
Usage
VolumeRSP2RSP440TridentTyphoon
disk0:IOS-XR Packages, ConfigsIOS-XR Packages, Configs  
disk0a:sysmgr_debugsysmgr_debug  
disk1:IOS-XR Packages (if Mirrored)IOS-XR Packages (if Mirrored)  
disk1a:wdsysmon_debugwdsysmon_debug  
harddisk:Crash files, logsCrash files, logs  
harddiska:NP logs, crash filesNP logs, crash files  
harddiskb:    
compactflash:File CopyFile Copy  
lcdisk0:  Kernel dump filesKernel dump files
lcdisk0a:    
bootflash:MBI Images   
configflash:OBFL   
nvram:ConfigsConfigs  
Kernel dumpRaw kernel dumpsRaw kernel dumps Raw kernel dumps
     
Filesystems
VolumeRSP2RSP440TridentTyphoon
disk0:QNX4QNX4  
disk0a:QNX4QNX4  
disk1:QNX4QNX4  
disk1a:QNX4QNX4  
harddisk:QNX4QNX4  
harddiska:QNX4QNX4  
harddiskb:QNX4FAT  
compactflash:FAT1FAT1,2  
lcdisk0:  QNX4QNX4
lcdisk0a:  QNX4QNX4
bootflash:FFSv3 FFSv3FFSv3
configflash:FFSv3   
nvram:CiscoCisco  
Kernel dumpRawRawFileRaw
 1. FAT F/S only2. Flash Media only  
     
Approximate Parition Size (minimum)
VolumeRSP2RSP440TridentTyphoon
disk0:1.6GB11.0GB  
disk0a:0.4GB2.2GB  
disk1:1.6GB11.0GB  
disk1a:0.4GB2.2GB  
harddisk:35GB3.1/6.2GB  
harddiska:8GB0.4/0.8GB  
harddiskb:8GB0.4/0.8GB  
compactflash:1GB1-32GB  
lcdisk0:  1.6GB1.6GB
lcdisk0a:  0.4GB0.4GB
bootflash:44MB 56MB56MB
configflash:28MB   
nvram:220K500K  
Kernel dump21GB500MB x 2 24MB
 

Note that unlike many IOS devices, nvram is NOT used for the configuration storage. Configurations are stored in a database on the boot disk (often disk0). Typically only rommon variables and license info are stored in nvram.

Summary steps for using turboboot

Because a  turboboot can erase configuration, SSH keys, and other items such as  licenses the following should be done to check and backup any files

1. Run a cfs check in admin & non-admin mode

2. Copy active licenses and SNMP files to tftp server

3. Copy running config to a tftp-server or laptop

4. Capture "show ipv4 int brief" output to a text file

5. Capture "show ipv6 int brief | i Up/Up" output to a text file

6.  Offline. Edit the saved RSP config - add "no shutdown" for all physical  interfaces that are up/up from the above IPv4 & IPv6 interface  captures and save cfg changes. Note that it is not necessary to “no  shut” sub-interfaces, only the main physical interface.

7. Connect a laptop console cable to the RSP in RSP0 slot and enable a log file to monitor and capture the RSP bootup logs.

8 . Turn the power supplies on to power up the asr9k system. (approx. 7-12 minutes)

9.  After the LED's indicate IOS-XR on the LC's, and ACTV or STBY on the  RSP’s, log in via the console of the RSP that is ACTV and run some  preliminary checks to check system stability.

NOTE: The default root-system username and password on the RSP440 are root/root

(if root/root does not work also try cisco/cisco, or admin/admin or viking/viking)

 

10. Verify the ASR9K IOS XR version

11. Run a cfs check in admin & non-admin mode

12. (Optional) Install add & commit any missing SW packages (pies) or required SMU’s

13. Upgrade FPD in admin mode

14. Reload any nodes that had FPD upgrades

15.  Configure the Mgmt ethernet interface with an IP address to reach tftp  server & load and commit the saved RSP config from tftp server or  laptop

a) or log into the console and cut & paste a saved cfg from laptop

b) or copy saved cfg from laptop to usb, then insert usb into RSP440 and copy and commit cfg

c) copy licenses and snmp files back to the RSP’s

16. (Optional) create and generate new crypto keys if required.

Steps to Turboboot

 

As mentioned Turbobooting means that you load the "VM" (virtual machine) XR base OS image.

Turboboot is started from Rommon and is essentially the same as putting a disk with the desired OS in your laptop, reboot the machine to boot from CDROM, and installing the base OS.

Before the Turboboot process starts, you can instruct the system to wipe all files from the system and start clean or install the image to be turbobooted along side with any existing releases currently found on the disk. (see Set the Turboboot variables on the RSP)

Turbobooting may be required if you want to sweep clean your system, or we also had some issues in XR4.2.0 with the RSP2 whereby the upgrade pie could not be loaded. A turboboot was required in that case also.

Some or all of these procedures below are needed.

The command "set" gives you an overview of all the rommon environment variables currently set to their values.

Clear the ROM Monitor environmental variables on all RSPs

unset BOOT
unset TFTP_FILE
sync

the command *unset* clears the variable value from rommon.

the command *sync *saves or writes the newly set and unset variables to persistent memory so they are saved cross reloads and power cycles.

Clear disk mirroring variables

unset BOOT_DEV_SEQ_OPER
unset MIRROR_ENABLE
sync

By default, the two internal USB partitions (disk0 and disk1) are mirrored to each other, if you break the mirror, turboboot will only affect the disk

that you are turbobooting target to and not the other one (nice if you want to fall back).

Disable the CPU watchdog

priv
diswd <- Disable the CPU watchdog

If you omit this step and the TFTP download for the turboboot mini-vm image takes longer than 30 minutes due to network delays etc, then the RSP might reset and you'll have to start over. Disabling this watchdog makes sure the system is not going to reload during the transfer of the image in rommon.

Define the network and IP settings on the mgmt interface

IP_ADDRESS=ip_address
IP_SUBNET_MASK=mask
DEFAULT_GATEWAY=ip_address

Set TFTP environment variables

TFTP_RETRY_COUNT=4

sets the number of retries to contact the tftp server

TFTP_TIMEOUT=6000

sets the TFTP timeout for the transfer, you may need to set this larger to prevent abort during xfer if there are network delays

TFTP_CHECKSUM=1

whether checksum on the transfer is needed, this is adviceable in case the image gets corrupted during transfer.

TFTP_SERVER=server_ip_addr

the server address can also be specified in the boot statement, or fixed in the rommon variable.

TFTP_MGMT_INTF=0

which of the 2 mgmt interfaces you want to use, either 0 or 1 with 0 being the default.

TFTP_BLKSIZE=1400

Setting a larger TFTP block size is recommended to pack larger packets and transfer the VM image quicker. Note that for CRS this variable is TFTP_BLOCK_SIZE.

Set the Turboboot variable on the RSP

TURBOBOOT=on, {boot-device},[format | clean],[nodisablebreak]

on tells us to install add and install activate the packages when we boot from the VM image.

boot-device is which device we want to use to install the OS, typically disk0

format tells us to replace the OS completely except for the admin configuration

clean tells us to replace the OS completely, but other files such as the admin or exec configuration are saved

nodisablebreak allows us to terminate the turboboot via a break signal. The default is to ignore breaks

Example:

TURBOBOOT=on,disk0,format
sync

This will instruct the system to do a turboboot with disk0 as the selected boot device and to use the format option. The format key is optional.

Currently today we only support targeted install to disk0 but this will change likely in XR4.3.1 whereby you can use disk1 as install target.

NOTE: a recent tac case showed that the command for turboboot failed on the ASR9001.

Supposedly this was made to work by omitting the colon after disk0:

Suggesting to try the disk0 (without colon) if the command with colon fails.

 

ASR9K/CRS-PRP Additional Information

 

In CRS the format option works with FAT16 but not FAT32 or QNX4 so a new variable must also be used.

In ASR9K the format and clean options do work but in order to erase the exec configuration, admin configuration, and every other file this additional variable must be used.

 

For these scenarios the following must be set.

TURBOBOOT=on,disk0

MEDIA_FORMAT=disk0:,QNX4

 

Note: If the format or clean options are set in turboboot or confreg 0x2142 is set when also having the MEDIA_FORMAT variable set then when prompted for a new username/password we will be unable to write this to the disk. To fix this go back to rommon and properly set the variables.

 

Boot the remote mini.vm file

(Works only with the VM image, not the TAR file or mini.pie)

rommon> boot tftp://server/directory/filename

During the boot process the image is copied first on to the memory(RAM) and is installed from memory(RAM). Once it is insalled from memory, it will copy the image back on to disk0: and reload the device. Wait till you get the message "SYSTEM CONFIGURATION COMPLETED"

Output of show install active when in memory,

RP/0/RSP0/CPU0:ios#sh install active
<SNIP>
Active Packages:
mem:asr9k-mini-p-4.2.0

Output of show install active after image copied on to disk0:,

RP/0/RSP0/CPU0:ios#sh install active
<SNIP>
Active Packages:
disk0:asr9k-mini-p-4.2.0

The system will also self unset the TURBOBOOT rommon variable.

Restore disk mirroring

To restore disk mirroring, use the mirror command in the global configuration mode. For more information on the mirror command, see the "Boot Commands on Cisco IOS XR Software" module in Cisco ASR 9000 Series Aggregation Services Router System Management Command Reference.

How to boot from the external USB port

The RSP-440 (and 9001 with rommon 2.03) can boot from the USB front panel port. Instead of using "boot tftp:// or boot disk0:/" you need to use a different command, mediaboot.

The command is:

rommon> mediaboot usb:\release_mini.vm

In later revisions of the rommon, the mediaboot has been superseded to boot usb:/<file>

so make sure you try them both.

 

NOTE:

Some newer rommon versions on the 9001 want to use the boot usb:/ directive. (see Q&A/comment section below this article).

It is also seen in rommon versions post 2.04 that the usb is referred to as disk1 in which case you can use: boot disk1:/...

To find out the mapping of the usb disk use the rommon "dev" command to see all filesystem devices.

 

On the CRS-PRP use boot disk2:hfr-mini-px.vm<image>

CRS does not use the mediaboot command.

How to update the FPD's

FPD upgrade for all ASR9K devices using FPD.

a) Enter admin mode via the admin command, and capture the output of the current firmware versions using CLI show hw-module fpd location all. save this output to a text file. Notice any LC that has a “yes” in the Upg/Dng?  column. This indicates the FPD should be upgraded or downgraded to match the current FPD version.

b) From admin mode upgrade FPD using the CLI: upgrade hw-module fpd location r/s/m

or if all locations require FPD upgrade (suggested) use CLI:* upgrade hw-module fpd location all *

Disk Space occupied for each image

Simplest way is to use the ksh df utility.

Install a release and packages and run df:

# df /disk0:

/dev/disk00t77           3813344    733477   3079867      20%  /dev/disk0:/   

Divide the highlighted number by 2000. That gives the approximate size in MB. 366MB in this case.

Repeat for any other releases we should be interested in.

If you do an upgrade, gather the df output before and after upgrade and compute the difference in df output.

Related Information

Xander Thuijs, CCIE #6775

Principal Engineer ASR9000

Sam Milstead,

Customer Support Engineer TAC XR

Comments
ops@chime.net.au
Community Member

Please delete this comment. 

V_V
Level 1
Level 1

Hi Bradley,

Can you the steps you have outlined above can you clarify this step: 

3:06am – From ROMMON set turboboot, then “boot harddisk:\asr9k-mini-px.vm-5.3.3”

 I'm trying to upgrade 4.3.4 to 5.3.3 on A9K-RSP-4G. 

Thanks,

VV 

xthuijs
Cisco Employee
Cisco Employee

The rommon of an RSP2 doesnt have access to the harddisk. Only devices with a SSD (9001, RSP440/880) can directly boot from harddisk.

regards

xander

V_V
Level 1
Level 1

Thank you Xander for your prompt response and clarifying - tftp it is then:) 

anursriv
Cisco Employee
Cisco Employee

Hello Community

I had a seemingly basic question.  My customer is going to install a newly purchased ASR 9010 in their network in addition to upgrading the existing ones. The existing ones are running 3.9.2.

It is clear that the upgrade must be performed through turboboot and the previous upgrade was performed in September 2015 (upgraded to 5.1.3)

I would like to understand:

1. Seeing as we have crossed Oct 17, 2015, will I require to install any pre-requisite SMU (SAM change set), or can I directly turboboot to 5.3.3?

2. The new ASR 9000 boxes - Will they contain pre loaded XR, or will I be boot in ROMMON? (If yes and if it is pre 5.3.1, I will install the certificate and post-expiry SMU and activate accordingly, else the procedure seems straight forward)

I do not have a great deal of experience in this matter, hence any inputs would be greatly appreciated. 

Thanks

Hello Anursriv,

1. I was able to turboboot directly from 4.3.4 SP5 to 5.3.3 with no SMUs. Same with 5.1.3. Version 4.3.4 SP5 to 5.1.3 required SMUs due to the Abraxis server change for validating files.

dhernandez
Level 1
Level 1

Hello Xander,

We have an asr9000 working with a RSP-8G and 4.2.3, We need to replace the standby RSP, (RMA), and the new one has 5.2.4.

Documented procedure indicates a turbo boot to downgrade from 5.2.4 to pre 430 images. 

Since it is undesirable to have a maintenance window, at least not a large one, do you know what would hapen if we insert the new rsp with 5.2.4? Would it sync the version?

Regards

Aleksandar Vidakovic
Cisco Employee
Cisco Employee

The newly inserted standby RSP will sync with the active.

Have you already thought of upgrading the SW release from 4.2.3 to 5.3.4? Release 5.3.4 is our strong suggestion for general deployment.

Regards,

/Aleksandar

dhernandez
Level 1
Level 1

Thank you Aleksandar,

Working on a plan to upgrade, just waiting to evaluate 5.3.4 and SMUs, this is because as far as we know this is the version for 8G

Regards

David

Aleksandar Vidakovic
Cisco Employee
Cisco Employee

hi David,

that's correct, release 5.3.4 is the last one with support for Trident line cards and A9K-RSP-4G and A9K-RSP-8G.

regards,

/Aleksandar

keigo_komatsu
Level 1
Level 1

Someone knows if is possible to perform turboboot using the Harddisk0: as a source of VM file?

xthuijs
Cisco Employee
Cisco Employee

hi keigo,

depends a bit on the RSP version you have and the rommon version running.

For sure on RSP2 that has a spinning harddisk, you cant do that (no drivers in rommon).

On RSP440/880 the harddisk is not spinning anymore and SSD/eUSB based and rommon may be able to reach it. The rommon version is dependent on the last XR version ran and if the fpd's (of which rommon is one) has been updated.

You can check in rommon via :

rommon 1> dev

to see if the harddisk is mounted/listed and if so, you can do a boot <location> from there.

cheers

xander

haifwang
Cisco Employee
Cisco Employee

Hi Xander,

Thanks for such a great post.

For a normal XR upgrade scenario that turbo-boot is not mandatory, such as 4.2.1 -> 4.2.3 or 4.2.3 -> 5.3.4, we can upgrade by either "install activate" or "burbo-boot".

But which one is more recommended? 

In the upgrade procedure document, I found " Turboboot (Highly NOT recommended) ", so I guess normally we should use "install activate" unless we have to use turbo-boot.

http://www.cisco.com/web/Cisco_IOS_XR_Software/pdf/ASR9K_Upgrade_Downgrade_Procedure_IOSXR_Rel_533.pdf

Am I right? If possible, could you explain the reason?

Regards,

Tobi

xthuijs
Cisco Employee
Cisco Employee

hi tobi! thank you :) yeah normally an upgrade should be possible without turboboot. there are a few scenarios whereby we know that it is the only option and that is documented in teh upgrade guides when that applies.

the reason why it is mentioned not recommended for 533, is because we verified that this can be done with the install activate, which is recommended always (when possible) because it saves a lot of time and simplifies the upgrade process not having to restore configurations etc. There is no technical reason as such :).

To simplify the upgrade even more you can use CSM (software manager). For some info on that check:

cheers!

xander

jaouadalu
Level 1
Level 1

i am trying a turbo on 5.3.3 

and i get this 


rommon 6 > dir /usb
ls/dir: Cannot open directory /usb - No Mapping

We are the testing the rollback from RP2 to the old rp's

without the turboboot i get this:

CPU reset reason = 2 (CPU_RESET_OIR_POR)
########## Environment Variables ##########
PS1=rommon ! >
?=0
CLUSTER_RACK_ID=0
ACTIVE_FCD=1
IOX_ADMIN_CONFIG_FILE=
BSI=0
CLUSTER_NO_BOOT=
BOOT_DEV_SEQ_CONF=
BOOT_DEV_SEQ_OPER=
RMEMVA=
BOOT=disk0:asr9k-os-mbi-5.3.3.CSCvc18326-1.0.0/0x100305/mbiasr9k-rsp3.vm,1;
###########################################
Total DRAM Memory: 12288 MB
MAC Address from cookie: 10:f3:11:7a:11:70
Board type: 0x0010030f
Chassis type: 0x00ef02f8
Slot number: 01
Chassis serial: FOX1737GND4

##########################################################
System Bootstrap, Version 5.15 [ASR9K x86 ROMMON],
Copyright (c) 1994-2012 by Cisco Systems, Inc.
Compiled on Tue 05/05/2015 23:53:10.55 by myekkar

Rommon : 5.15
Ibex Peak : 6
Jasper Forest: 1.0
CBC0 : Part 1=25.3, Part 2=25.2, Act Part=1
CBC1 : Part 1=25.3, Part 2=25.3, Act Part=2
Rodimus : 1.5.0 (primary)
Redondo : 1.3.0 (primary)
Newport : 1.4.0 (primary)
Scimitar : 1.5.0 (primary)
UTI : 4.9 (primary)
Timex : 0.2.1 (primary)
==========================================================
mbi_boot_smart_reload() - Fastboot status is zero
Sending Boot Image validation request.
HIT CTRL-C to abort
Candidate Boot Image num 0 is disk0:asr9k-os-mbi-5.3.3.CSCvc18326-1.0.0/0x100305/mbiasr9k-rsp3.vm
-----------
Interface link did not come up. Timed out.
Boot Image validation: Link failure
Sending Boot Image validation request.
HIT CTRL-C to abort
Candidate Boot Image num 0 is disk0:asr9k-os-mbi-5.3.3.CSCvc18326-1.0.0/0x100305/mbiasr9k-rsp3.vm
Interface link changed state to UP.
Interface link state up.
................Boot Image validation: Boot response retry
Sending Boot Image validation request.
HIT CTRL-C to abort
Candidate Boot Image num 0 is disk0:asr9k-os-mbi-5.3.3.CSCvc18326-1.0.0/0x100305/mbiasr9k-rsp3.vm
Interface link changed state to UP.
Interface link state up.
................Boot Image validation: Boot response retry
Trying local boot path 0: disk0:asr9k-os-mbi-5.3.3.CSCvc18326-1.0.0/0x100305/mbiasr9k-rsp3.vm ...
Beginning Media boot:
boot_disk2 - Launching image.


#################################################################
Program load complete, Entry point: 0x40d9d8, size: 0x1bc5b3c
Startup-code initializing, running on Storm (0010030f)
BSP date: May 11 2015 09:44:50
Debugging enabled; debug_flag = 1, vendor_debug_flag = 0
Page Address Extension mode (PAE) enabled with 36bit physical addressing.
Running on a ASR9K x86 RSP
Found 12288MB of main memory
Reading back MTRR config from boot processor.
Found LP at APIC ID 2
Found LP at APIC ID 4
Found LP at APIC ID 6
IPL reports 4 logical processors
Family = 00000006, Model = 0000001e
4 CPU cores available
Initializing logical processor 0 (APIC ID 0).......OK (BSP)
Initializing logical processor 1 (APIC ID 2).......OK
Initializing logical processor 2 (APIC ID 4).......OK
Initializing logical processor 3 (APIC ID 6).......OK
Chassis Type: ASR9922 (00ef02f8)
Region shmwin1: 70000000:b0000000
Region pakman: b0000000:b8000000
##############################################################################################################################################################

System page at phys:00023000 user:fed25000 kern:fed28000
Starting next program at vfe041610
Kernel Dumper Boot Init
*** Welcome to QNX neutrino!
*** ASR9K RSP.
tracelogger: starting tracing in background ring mode
tracelogger running with args: -startring -F 1 -F 2
Use private TLB mappings
Restricted Rights Legend

Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.

cisco Systems, Inc.
170 West Tasman Drive
San Jose, California 95134-1706

Cisco IOS XR Software for the Cisco XR ASR9K, Version 5.3.3
Copyright (c) 2016 by Cisco Systems, Inc.
Media storage device /harddisk: was repaired. Check fsck log at /harddisk:/chkfs_repair.log
Apr 19 07:37:05.073: Install Setup: Booting with committed software
CPU reset reason = 5 (CPU_RESET_POR)
########## Environment Variables ##########
PS1=rommon ! >
?=0
CLUSTER_RACK_ID=0
ACTIVE_FCD=1
IOX_ADMIN_CONFIG_FILE=
CLUSTER_NO_BOOT=
BOOT_DEV_SEQ_CONF=
BOOT_DEV_SEQ_OPER=
RMEMVA=
BSI=0
BOOT=disk0:asr9k-os-mbi-5.3.3.CSCvc18326-1.0.0/0x100305/mbiasr9k-rsp3.vm,1;
###########################################
Total DRAM Memory: 12288 MB
MAC Address from cookie: 10:f3:11:7a:11:70
Board type: 0x0010030f
Chassis type: 0x00ef02f8
Slot number: 01
Chassis serial: FOX1737GND4

##########################################################
System Bootstrap, Version 5.15 [ASR9K x86 ROMMON],
Copyright (c) 1994-2012 by Cisco Systems, Inc.
Compiled on Tue 05/05/2015 23:53:10.55 by myekkar

Rommon : 5.15
Ibex Peak : 6
Jasper Forest: 1.0
CBC0 : Part 1=25.3, Part 2=25.2, Act Part=1
CBC1 : Part 1=25.3, Part 2=25.3, Act Part=2
Rodimus : 1.5.0 (primary)
Redondo : 1.3.0 (primary)
Newport : 1.4.0 (primary)
Scimitar : 1.5.0 (primary)
UTI : 4.9 (primary)
Timex : 0.2.1 (primary)
==========================================================
mbi_boot_smart_reload() - Fastboot status is zero
Sending Boot Image validation request.
HIT CTRL-C to abort
Candidate Boot Image num 0 is disk0:asr9k-os-mbi-5.3.3.CSCvc18326-1.0.0/0x100305/mbiasr9k-rsp3.vm
-----------
Interface link did not come up. Timed out.
Boot Image validation: Link failure
Sending Boot Image validation request.
HIT CTRL-C to abort
Candidate Boot Image num 0 is disk0:asr9k-os-mbi-5.3.3.CSCvc18326-1.0.0/0x100305/mbiasr9k-rsp3.vm
Interface link changed state to UP.
Interface link state up.
................Boot Image validation: Boot response retry
Sending Boot Image validation request.
HIT CTRL-C to abort
Candidate Boot Image num 0 is disk0:asr9k-os-mbi-5.3.3.CSCvc18326-1.0.0/0x100305/mbiasr9k-rsp3.vm
Interface link changed state to UP.
Interface link state up.
................Boot Image validation: Boot response retry
Trying local boot path 0: disk0:asr9k-os-mbi-5.3.3.CSCvc18326-1.0.0/0x100305/mbiasr9k-rsp3.vm ...
Beginning Media boot:
boot_disk2 - Launching image.


#################################################################
Program load complete, Entry point: 0x40d9d8, size: 0x1bc5b3c
Startup-code initializing, running on Storm (0010030f)
BSP date: May 11 2015 09:44:50
Debugging enabled; debug_flag = 1, vendor_debug_flag = 0
Page Address Extension mode (PAE) enabled with 36bit physical addressing.
Running on a ASR9K x86 RSP
Found 12288MB of main memory
Reading back MTRR config from boot processor.
Found LP at APIC ID 2
Found LP at APIC ID 4
Found LP at APIC ID 6
IPL reports 4 logical processors
Family = 00000006, Model = 0000001e
4 CPU cores available
Initializing logical processor 0 (APIC ID 0).......OK (BSP)
Initializing logical processor 1 (APIC ID 2).......OK
Initializing logical processor 2 (APIC ID 4).......OK
Initializing logical processor 3 (APIC ID 6).......OK
Chassis Type: ASR9922 (00ef02f8)
Region shmwin1: 70000000:b0000000
Region pakman: b0000000:b8000000
##############################################################################################################################################################

System page at phys:00023000 user:fed25000 kern:fed28000
Starting next program at vfe041610
Kernel Dumper Boot Init
*** Welcome to QNX neutrino!
*** ASR9K RSP.
tracelogger: starting tracing in background ring mode
tracelogger running with args: -startring -F 1 -F 2
Use private TLB mappings
Restricted Rights Legend

Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.

cisco Systems, Inc.
170 West Tasman Drive
San Jose, California 95134-1706

Cisco IOS XR Software for the Cisco XR ASR9K, Version 5.3.3
Copyright (c) 2016 by Cisco Systems, Inc.
Media storage device /harddisk: was repaired. Check fsck log at /harddisk:/chkfs_repair.log
Apr 19 07:44:06.075: Install Setup: Booting with committed software
CPU reset reason = 5 (CPU_RESET_POR)
########## Environment Variables ##########
PS1=rommon ! >
?=0
CLUSTER_RACK_ID=0
ACTIVE_FCD=1
IOX_ADMIN_CONFIG_FILE=
CLUSTER_NO_BOOT=
BOOT_DEV_SEQ_CONF=
BOOT_DEV_SEQ_OPER=
RMEMVA=
BSI=0
BOOT=disk0:asr9k-os-mbi-5.3.3.CSCvc18326-1.0.0/0x100305/mbiasr9k-rsp3.vm,1;
###########################################
Total DRAM Memory: 12288 MB
MAC Address from cookie: 10:f3:11:7a:11:70
Board type: 0x0010030f
Chassis type: 0x00ef02f8
Slot number: 01
Chassis serial: FOX1737GND4

##########################################################
System Bootstrap, Version 5.15 [ASR9K x86 ROMMON],
Copyright (c) 1994-2012 by Cisco Systems, Inc.
Compiled on Tue 05/05/2015 23:53:10.55 by myekkar

Rommon : 5.15
Ibex Peak : 6
Jasper Forest: 1.0
CBC0 : Part 1=25.3, Part 2=25.2, Act Part=1
CBC1 : Part 1=25.3, Part 2=25.3, Act Part=2
Rodimus : 1.5.0 (primary)
Redondo : 1.3.0 (primary)
Newport : 1.4.0 (primary)
Scimitar : 1.5.0 (primary)
UTI : 4.9 (primary)
Timex : 0.2.1 (primary)
==========================================================
mbi_boot_smart_reload() - Fastboot status is zero
Sending Boot Image validation request.
HIT CTRL-C to abort
Candidate Boot Image num 0 is disk0:asr9k-os-mbi-5.3.3.CSCvc18326-1.0.0/0x100305/mbiasr9k-rsp3.vm
-----------
Interface link did not come up. Timed out.
Boot Image validation: Link failure
Sending Boot Image validation request.
HIT CTRL-C to abort
Candidate Boot Image num 0 is disk0:asr9k-os-mbi-5.3.3.CSCvc18326-1.0.0/0x100305/mbiasr9k-rsp3.vm
Interface link changed state to UP.
Interface link state up.
................Boot Image validation: Boot response retry
Sending Boot Image validation request.
HIT CTRL-C to abort
Candidate Boot Image num 0 is disk0:asr9k-os-mbi-5.3.3.CSCvc18326-1.0.0/0x100305/mbiasr9k-rsp3.vm
Interface link changed state to UP.
Interface link state up.
................Boot Image validation: Boot response retry
Trying local boot path 0: disk0:asr9k-os-mbi-5.3.3.CSCvc18326-1.0.0/0x100305/mbiasr9k-rsp3.vm ...
Beginning Media boot:
boot_disk2 - Launching image.


#################################################################
Program load complete, Entry point: 0x40d9d8, size: 0x1bc5b3c
Startup-code initializing, running on Storm (0010030f)
BSP date: May 11 2015 09:44:50
Debugging enabled; debug_flag = 1, vendor_debug_flag = 0
Page Address Extension mode (PAE) enabled with 36bit physical addressing.
Running on a ASR9K x86 RSP
Found 12288MB of main memory
Reading back MTRR config from boot processor.
Found LP at APIC ID 2
Found LP at APIC ID 4
Found LP at APIC ID 6
IPL reports 4 logical processors
Family = 00000006, Model = 0000001e
4 CPU cores available
Initializing logical processor 0 (APIC ID 0).......OK (BSP)
Initializing logical processor 1 (APIC ID 2).......OK
Initializing logical processor 2 (APIC ID 4).......OK
Initializing logical processor 3 (APIC ID 6).......OK
Chassis Type: ASR9922 (00ef02f8)
Region shmwin1: 70000000:b0000000
Region pakman: b0000000:b8000000
##############################################################################################################################################################

System page at phys:00023000 user:fed25000 kern:fed28000
Starting next program at vfe041610
Kernel Dumper Boot Init
*** Welcome to QNX neutrino!
*** ASR9K RSP.
tracelogger: starting tracing in background ring mode
tracelogger running with args: -startring -F 1 -F 2
Use private TLB mappings
Restricted Rights Legend

Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.

cisco Systems, Inc.
170 West Tasman Drive
San Jose, California 95134-1706

Cisco IOS XR Software for the Cisco XR ASR9K, Version 5.3.3
Copyright (c) 2016 by Cisco Systems, Inc.
Media storage device /harddisk: was repaired. Check fsck log at /harddisk:/chkfs_repair.log
Apr 19 07:46:42.071: Install Setup: Booting with committed software
CPU reset reason = 5 (CPU_RESET_POR)
########## Environment Variables ##########
PS1=rommon ! >
?=0
CLUSTER_RACK_ID=0
ACTIVE_FCD=1
IOX_ADMIN_CONFIG_FILE=
CLUSTER_NO_BOOT=
BOOT_DEV_SEQ_CONF=
BOOT_DEV_SEQ_OPER=
RMEMVA=
BSI=0
BOOT=disk0:asr9k-os-mbi-5.3.3.CSCvc18326-1.0.0/0x100305/mbiasr9k-rsp3.vm,1;
###########################################
Total DRAM Memory: 12288 MB
MAC Address from cookie: 10:f3:11:7a:11:70
Board type: 0x0010030f
Chassis type: 0x00ef02f8
Slot number: 01
Chassis serial: FOX1737GND4

##########################################################
System Bootstrap, Version 5.15 [ASR9K x86 ROMMON],
Copyright (c) 1994-2012 by Cisco Systems, Inc.
Compiled on Tue 05/05/2015 23:53:10.55 by myekkar

Rommon : 5.15
Ibex Peak : 6
Jasper Forest: 1.0
CBC0 : Part 1=25.3, Part 2=25.2, Act Part=1
CBC1 : Part 1=25.3, Part 2=25.3, Act Part=2
Rodimus : 1.5.0 (primary)
Redondo : 1.3.0 (primary)
Newport : 1.4.0 (primary)
Scimitar : 1.5.0 (primary)
UTI : 4.9 (primary)
Timex : 0.2.1 (primary)
==========================================================
mbi_boot_smart_reload() - Fastboot status is zero
Sending Boot Image validation request.
HIT CTRL-C to abort
Candidate Boot Image num 0 is disk0:asr9k-os-mbi-5.3.3.CSCvc18326-1.0.0/0x100305/mbiasr9k-rsp3.vm
-----------
Interface link did not come up. Timed out.
Boot Image validation: Link failure
Sending Boot Image validation request.
HIT CTRL-C to abort
Candidate Boot Image num 0 is disk0:asr9k-os-mbi-5.3.3.CSCvc18326-1.0.0/0x100305/mbiasr9k-rsp3.vm
Interface link changed state to UP.
Interface link state up.
................Boot Image validation: Boot response retry
Sending Boot Image validation request.
HIT CTRL-C to abort
Candidate Boot Image num 0 is disk0:asr9k-os-mbi-5.3.3.CSCvc18326-1.0.0/0x100305/mbiasr9k-rsp3.vm
Interface link changed state to UP.
Interface link state up.
................Boot Image validation: Boot response retry
Trying local boot path 0: disk0:asr9k-os-mbi-5.3.3.CSCvc18326-1.0.0/0x100305/mbiasr9k-rsp3.vm ...
Beginning Media boot:
boot_disk2 - Launching image.


#################################################################
Program load complete, Entry point: 0x40d9d8, size: 0x1bc5b3c
Startup-code initializing, running on Storm (0010030f)
BSP date: May 11 2015 09:44:50
Debugging enabled; debug_flag = 1, vendor_debug_flag = 0
Page Address Extension mode (PAE) enabled with 36bit physical addressing.
Running on a ASR9K x86 RSP
Found 12288MB of main memory
Reading back MTRR config from boot processor.
Found LP at APIC ID 2
Found LP at APIC ID 4
Found LP at APIC ID 6
IPL reports 4 logical processors
Family = 00000006, Model = 0000001e
4 CPU cores available
Initializing logical processor 0 (APIC ID 0).......OK (BSP)
Initializing logical processor 1 (APIC ID 2).......OK
Initializing logical processor 2 (APIC ID 4).......OK
Initializing logical processor 3 (APIC ID 6).......OK
Chassis Type: ASR9922 (00ef02f8)
Region shmwin1: 70000000:b0000000
Region pakman: b0000000:b8000000
##############################################################################################################################################################

System page at phys:00023000 user:fed25000 kern:fed28000
Starting next program at vfe041610
Kernel Dumper Boot Init
*** Welcome to QNX neutrino!
*** ASR9K RSP.
tracelogger: starting tracing in background ring mode
tracelogger running with args: -startring -F 1 -F 2
Use private TLB mappings
Restricted Rights Legend

Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.

cisco Systems, Inc.
170 West Tasman Drive
San Jose, California 95134-1706

Cisco IOS XR Software for the Cisco XR ASR9K, Version 5.3.3
Copyright (c) 2016 by Cisco Systems, Inc.
Media storage device /harddisk: was repaired. Check fsck log at /harddisk:/chkfs_repair.log
Apr 19 07:49:23.075: Install Setup: Booting with committed software
CPU reset reason = 5 (CPU_RESET_POR)
########## Environment Variables ##########
PS1=rommon ! >
?=0
CLUSTER_RACK_ID=0
ACTIVE_FCD=1
IOX_ADMIN_CONFIG_FILE=
CLUSTER_NO_BOOT=
BOOT_DEV_SEQ_CONF=
BOOT_DEV_SEQ_OPER=
RMEMVA=
BSI=0
BOOT=disk0:asr9k-os-mbi-5.3.3.CSCvc18326-1.0.0/0x100305/mbiasr9k-rsp3.vm,1;
###########################################
Total DRAM Memory: 12288 MB
MAC Address from cookie: 10:f3:11:7a:11:70
Board type: 0x0010030f
Chassis type: 0x00ef02f8
Slot number: 01
Chassis serial: FOX1737GND4

##########################################################
System Bootstrap, Version 5.15 [ASR9K x86 ROMMON],
Copyright (c) 1994-2012 by Cisco Systems, Inc.
Compiled on Tue 05/05/2015 23:53:10.55 by myekkar

Rommon : 5.15
Ibex Peak : 6
Jasper Forest: 1.0
CBC0 : Part 1=25.3, Part 2=25.2, Act Part=1
CBC1 : Part 1=25.3, Part 2=25.3, Act Part=2
Rodimus : 1.5.0 (primary)
Redondo : 1.3.0 (primary)
Newport : 1.4.0 (primary)
Scimitar : 1.5.0 (primary)
UTI : 4.9 (primary)
Timex : 0.2.1 (primary)
==========================================================
mbi_boot_smart_reload() - Fastboot status is zero
Sending Boot Image validation request.
HIT CTRL-C to abort
Candidate Boot Image num 0 is disk0:asr9k-os-mbi-5.3.3.CSCvc18326-1.0.0/0x100305/mbiasr9k-rsp3.vm
-----------
Interface link did not come up. Timed out.
Boot Image validation: Link failure
Sending Boot Image validation request.
HIT CTRL-C to abort
Candidate Boot Image num 0 is disk0:asr9k-os-mbi-5.3.3.CSCvc18326-1.0.0/0x100305/mbiasr9k-rsp3.vm
Interface link changed state to UP.
Interface link state up.
................Boot Image validation: Boot response retry
Sending Boot Image validation request.
HIT CTRL-C to abort
Candidate Boot Image num 0 is disk0:asr9k-os-mbi-5.3.3.CSCvc18326-1.0.0/0x100305/mbiasr9k-rsp3.vm
Interface link changed state to UP.
Interface link state up.
................Boot Image validation: Boot response retry
Trying local boot path 0: disk0:asr9k-os-mbi-5.3.3.CSCvc18326-1.0.0/0x100305/mbiasr9k-rsp3.vm ...
Beginning Media boot:
boot_disk2 - Launching image.


#################################################################
Program load complete, Entry point: 0x40d9d8, size: 0x1bc5b3c
Startup-code initializing, running on Storm (0010030f)
BSP date: May 11 2015 09:44:50
Debugging enabled; debug_flag = 1, vendor_debug_flag = 0
Page Address Extension mode (PAE) enabled with 36bit physical addressing.
Running on a ASR9K x86 RSP
Found 12288MB of main memory
Reading back MTRR config from boot processor.
Found LP at APIC ID 2
Found LP at APIC ID 4
Found LP at APIC ID 6
IPL reports 4 logical processors
Family = 00000006, Model = 0000001e
4 CPU cores available
Initializing logical processor 0 (APIC ID 0).......OK (BSP)
Initializing logical processor 1 (APIC ID 2).......OK
Initializing logical processor 2 (APIC ID 4).......OK
Initializing logical processor 3 (APIC ID 6).......OK
Chassis Type: ASR9922 (00ef02f8)
Region shmwin1: 70000000:b0000000
Region pakman: b0000000:b8000000
##############################################################################################################################################################

System page at phys:00023000 user:fed25000 kern:fed28000
Starting next program at vfe041610
Kernel Dumper Boot Init
*** Welcome to QNX neutrino!
*** ASR9K RSP.
tracelogger: starting tracing in background ring mode
tracelogger running with args: -startring -F 1 -F 2
Use private TLB mappings
Restricted Rights Legend

Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.

cisco Systems, Inc.
170 West Tasman Drive
San Jose, California 95134-1706

Cisco IOS XR Software for the Cisco XR ASR9K, Version 5.3.3
Copyright (c) 2016 by Cisco Systems, Inc.
Media storage device /harddisk: was repaired. Check fsck log at /harddisk:/chkfs_repair.log
Apr 19 07:51:53.077: Install Setup: Booting with committed software
CPU reset reason = 5 (CPU_RESET_POR)
########## Environment Variables ##########
PS1=rommon ! >
?=0
CLUSTER_RACK_ID=0
ACTIVE_FCD=1
IOX_ADMIN_CONFIG_FILE=
CLUSTER_NO_BOOT=
BOOT_DEV_SEQ_CONF=
BOOT_DEV_SEQ_OPER=
RMEMVA=
BSI=0
BOOT=disk0:asr9k-os-mbi-5.3.3.CSCvc18326-1.0.0/0x100305/mbiasr9k-rsp3.vm,1;
###########################################
Total DRAM Memory: 12288 MB
MAC Address from cookie: 10:f3:11:7a:11:70
Board type: 0x0010030f
Chassis type: 0x00ef02f8
Slot number: 01
Chassis serial: FOX1737GND4

##########################################################
System Bootstrap, Version 5.15 [ASR9K x86 ROMMON],
Copyright (c) 1994-2012 by Cisco Systems, Inc.
Compiled on Tue 05/05/2015 23:53:10.55 by myekkar

Rommon : 5.15
Ibex Peak : 6
Jasper Forest: 1.0
CBC0 : Part 1=25.3, Part 2=25.2, Act Part=1
CBC1 : Part 1=25.3, Part 2=25.3, Act Part=2
Rodimus : 1.5.0 (primary)
Redondo : 1.3.0 (primary)
Newport : 1.4.0 (primary)
Scimitar : 1.5.0 (primary)
UTI : 4.9 (primary)
Timex : 0.2.1 (primary)
==========================================================
mbi_boot_smart_reload() - Fastboot status is zero
Sending Boot Image validation request.
HIT CTRL-C to abort
Candidate Boot Image num 0 is disk0:asr9k-os-mbi-5.3.3.CSCvc18326-1.0.0/0x100305/mbiasr9k-rsp3.vm
-----------
Interface link did not come up. Timed out.
Boot Image validation: Link failure
Sending Boot Image validation request.
HIT CTRL-C to abort
Candidate Boot Image num 0 is disk0:asr9k-os-mbi-5.3.3.CSCvc18326-1.0.0/0x100305/mbiasr9k-rsp3.vm
Interface link changed state to UP.
Interface link state up.
................Boot Image validation: Boot response retry
Sending Boot Image validation request.
HIT CTRL-C to abort
Candidate Boot Image num 0 is disk0:asr9k-os-mbi-5.3.3.CSCvc18326-1.0.0/0x100305/mbiasr9k-rsp3.vm
Interface link changed state to UP.
Interface link state up.
................Boot Image validation: Boot response retry
Trying local boot path 0: disk0:asr9k-os-mbi-5.3.3.CSCvc18326-1.0.0/0x100305/mbiasr9k-rsp3.vm ...
Beginning Media boot:
boot_disk2 - Launching image.


#################################################################
Program load complete, Entry point: 0x40d9d8, size: 0x1bc5b3c
Startup-code initializing, running on Storm (0010030f)
BSP date: May 11 2015 09:44:50
Debugging enabled; debug_flag = 1, vendor_debug_flag = 0
Page Address Extension mode (PAE) enabled with 36bit physical addressing.
Running on a ASR9K x86 RSP
Found 12288MB of main memory
Reading back MTRR config from boot processor.
Found LP at APIC ID 2
Found LP at APIC ID 4
Found LP at APIC ID 6
IPL reports 4 logical processors
Family = 00000006, Model = 0000001e
4 CPU cores available
Initializing logical processor 0 (APIC ID 0).......OK (BSP)
Initializing logical processor 1 (APIC ID 2).......OK
Initializing logical processor 2 (APIC ID 4).......OK
Initializing logical processor 3 (APIC ID 6).......OK
Chassis Type: ASR9922 (00ef02f8)
Region shmwin1: 70000000:b0000000
Region pakman: b0000000:b8000000
##############################################################################################################################################################

System page at phys:00023000 user:fed25000 kern:fed28000
Starting next program at vfe041610
Kernel Dumper Boot Init
*** Welcome to QNX neutrino!
*** ASR9K RSP.
tracelogger: starting tracing in background ring mode
tracelogger running with args: -startring -F 1 -F 2
Use private TLB mappings
Restricted Rights Legend

Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.

cisco Systems, Inc.
170 West Tasman Drive
San Jose, California 95134-1706

Cisco IOS XR Software for the Cisco XR ASR9K, Version 5.3.3
Copyright (c) 2016 by Cisco Systems, Inc.
Media storage device /harddisk: was repaired. Check fsck log at /harddisk:/chkfs_repair.log
Apr 19 07:54:45.075: Install Setup: Booting with committed software

This (D)RP Node is not ready or active for login /configuration

This (D)RP Node is not ready or active for login /configuration

This (D)RP Node is not ready or active for login /configuration

This (D)RP Node is not ready or active for login /configuration

The RP stays in reload loop.

Can someone help to fix this problem

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Quick Links