Capture bootup logs in router's flash

[johnlloyd_13]

hi,

i got an ASR920 that failed a ROMMON firmware upgrade and we don't have the USB console adapter and it's a very remote place. i would like to know is there a way to capture the upgrade/bootup logs similar when we're connected via console and send them to the router's flash memory or to an external server?

[Leo Laohoo]

If the router has generated a crashinfo/crashlog then the bootup can be found inside it.  

I have not tried it yet, but there is also another file, starts with "dmlog", and that might yield something useful.

[johnlloyd_13]

hi leo,

there was no crashinfo file generated when i tried to upgrade the ROMMON a few times. if only we got the console adapter and someone at the remote site, which is not practical at the moment to due covid-19, we might be able to decode what's going on. the ROMMON file is not corrupted since i checked the MD5 hash is correct and has the same byte size in other ASR920.

ASR920#upgrade rom-monitor filename bootflash:asr920_15_6_32r_s_rommon.pkg all  <<< 32r

Upgrade rom-monitor on Route-Processor 0

Target copying rom-monitor image file
Checking upgrade image...
1966080+0 records in
3840+0 records out
Upgrade image MD5 signature is 40966c321c22ab1671ab5617c4ce3b79
Burning upgrade partition...
1966080+0 records in
1966080+0 records out
Checking upgrade partition...
1966080+0 records in
1966080+0 records out
Upgrade flash partition MD5 signature is 40966c321c22ab1671ab5617c4ce3b79
ROMMON upgrade complete.
To make the new ROMMON permanent, you must restart the RP.
ASR920#
ASR920#reload

System configuration has been modified. Save? [yes/no]: yes
Building configuration...
[OK]
Proceed with reload? [confirm]

ASR920#sh platform
Chassis type: ASR-920-24SZ-M

Slot Type State Insert time (ago)
--------- ------------------- --------------------- -----------------
0/0 24xGE-4x10GE-FIXED-Sok 00:04:19
R0 ASR-920-24SZ-M ok, active 00:06:18
F0 ok, active 00:06:18
P0 ASR920-PSU0 ok 00:05:37
P1 ASR920-PSU1 ok 00:04:59
P2 ASR920-FAN ok 00:05:01

Slot CPLD Version Firmware Version
--------- ------------------- ---------------------------------------
R0 16012726 15.6(10r)S <<< STILL 10r NOT 32r
F0 16012726 15.6(10r)S

[Leo Laohoo]

Ok, I have seen read this sort of behaviour but I not seen/heard/read it on an ASR920 before.  Have a look at CSCvg52180 or CSCvg94612.  The two bugs talk about ISR4k but the behaviour is exactly the same.  

Currently the appliance is on ROMMON version 15.6(10r)S and you are jumping to 15.6(32r)S. 
Try jumping to the latest one, 15.6(44r)S.  Failing that try jumping "lower" to, say, 15.6(17r)S and then make a jump up.  

[johnlloyd_13]

hi leo,

are you're suggesting to upgrade to a higher ROMMON version then downgrade to our target 15.6(32r)S?

the bug CSCvg94612 link mentioned to upgrade the main IOS-XE first then do the ROMMON upgrade afterwards. is my understanding correct and is this advisable?

i thought standard procedure is to upgrade ROMMON firmware first BEFORE the main IOS-XE upgrade.

Workaround:
As a workaround, please boot IOS-XE 16.3.3 to auto upgrade the ROMMON to 16.2(1r).
After the upgrade process has finished, please boot IOS-XE 16.3.3 again.
Use the IOS cli upgrade commands to manually upgrade to the ROMMON ti 16.7(3r).

[Leo Laohoo]

My recommendation is to jump to 15.6(44r)S and stay there.