5.3.4 is the last release for Trident and is one place you could park your devices, however there are no more SMUs on 5.3.4. 6.1.4 still gets SMUs for a bit longer, September (https://www.cisco.com/c/en/us/products/collateral/ios-nx-os-software/ios-xr-software/eos-eol-notice-c51-740473.html). The issue with going to 6.4.2 is actually due to the SWIMS package signing (https://www.cisco.com/c/en/us/support/docs/ios-nx-os-software/ios-xr-software/213745-ios-xr-upgrade-changes-certificate-expi.html) What you can do is if you choose 6.1.4 (which is a better choice than 5.3.4 in my opinion), you can install the software and service pack at the same time, meaning only 1 reload is needed. Otherwise you might as well upgrade to 5.3.4 then to 6.4.2 + SP in 2 reloads.   Sam ... View more

That's what I thought at first, but it looks like your bootflash where the MBI lives is corrupt. We can try to format it and do turboboot again, if this fails we will have to RMA the 9001 due to flash corruption.   1) From ROMMON try to boot into hsbi: rommon B1 > b hsbi: Beginning HSBI boot: Loading B image: ............... program load complete, entry point: 0x1fbfe8, size: 0x3b5a98 Config = uP, Running = uP ################## BSP: Board type : RO-RSP2 Use private TLB mappings *********************************************** 2) When it presents you with options list, choose next: To format bootflash: ksh /etc/flash0_init Hence the command would be: ksh /etc/flash0_init     If you get an error like this we need to RMA. rommon B3 > b hsbi: Boot Status 16 Beginning HSBI boot: Loading B image: loadprog: bad file magic number: 0x0 Loading A image: loadprog: bad file magic number: 0x0 Error loading HSBI image.     Thanks, Sam ... View more

It's trying to install to bootflash and not disk0:   There is this note in the guide that I put there a few years ago, can you give this a try?   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.     Sam ... View more

I think we are getting off track here, we need to understand why the 9001 keeps rebooting. You can certainty reimage the router using https://community.cisco.com/t5/service-providers-documents/asr9000-xr-understanding-turboboot-and-initial-system-bring-up/ta-p/3146024 but that likely is not going to resolve the rebooting problem. The image you want is the mini-px.vm image for the turboboot. For booting the card you need the .mbi image, this gets created automatically by the system in a directory on disk0. For some reason your RSP has no mbi image set to the BOOT variable so the RSP doesn't know how to boot, did you turboboot or just boot the .vm image without the turboboot variable? If so then you will need to turboboot to reimage the router.   Sam ... View more

That is just the mini pie file, not the boot image.   On the RP issue the command 'more nvram:/classic-rommon-var' and see what the boot image is set to and try booting from that. Or from rommon you can try the 'set' command to see if its already set and just try 'boot'. Most likely you exceeded the number of reboot attempts and will have to manually reload the card from admin mode (hw-module loc 0/0/cpu0 reload) to allow the card to try reloading.   Sam ... View more

I don't think the config size / rollback size is the issue but we can try clearing out the commitDB / rollback points to see if that helps. 'clear config commits oldest <x>'   Can you also paste the show install active summary and full show log here?   Thanks, Sam ... View more

Please open a TAC case, this is likely a new iteration of CSCvf45424.   Thanks, Sam ... View more

What code are you on? Are you using 'bgp attribute-download'?   Thanks, Sam ... View more

We support it for the duration of a MW. So long as you have an odd and even fabric card of the same type in the system it will remain up, so we typically recommend swapping 2 fabric cards at a time.   Sam ... View more

Are you connected on console?   Please try ctrl+o (“o” as in orange) on the console while in sysadmin. You will be directed to host and then press ctrl+o     Another way if you are not consoled in: sysadmin-vm:0_RP0# show sdr Sun May 26 19:13:28.249 UTC SDR: default-sdr Location IP Address Status Boot Count Time Started ----------------------------------------------------------------------------- 0/RP0/VM1 192.0.0.4 RUNNING 3 04/26/2019 00:50:06 0/RP0/VM2 192.0.0.6 RUNNING 3 04/26/2019 00:52:16 sysadmin-vm:0_RP0# run Sun May 26 19:13:32.391 UTC [sysadmin-vm:0_RP0:~]$ssh 192.0.0.4 Last login: Sun May 26 19:08:47 2019 from 192.0.0.1 [xr-vm_node0_RP0_CPU0:~]$/pkg/sbin/exec !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Banner !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! User Access Verification Username: smilstea Password: RP/0/RP0/CPU0:NCS-5502-B#exit Terminated [xr-vm_node0_RP0_CPU0:~]$exit logout [sysadmin-vm:0_RP0:~]$exit exit sysadmin-vm:0_RP0# ... View more

The attached picture should answer your question, its from an NCS5500 but same principles apply.   Sam ... View more

Usually a BSIT error on an asr9k LC that keeps rebooting means the card has to be replaced. If you search show logging for "NP" you should see "failed to setup" or similar errors for various NPs when setting up the hardware. I would RMA this card.   Sam ... View more