09-10-2021 03:16 AM
after upgrade 1001x:
Initializing Hardware ...
System integrity status: 00000610
U
System Bootstrap, Version 16.9(4r), RELEASE SOFTWARE
Copyright (c) 1994-2018 by cisco Systems, Inc.
Current image running: Boot ROM1
Last reset cause: LocalSoft
ASR1001-X platform with 8388608 Kbytes of main memory
File size is 0x306f999d
Located asr1001x-universalk9.16.12.05.SPA.bin
Image size 812620189 inode num 14, bks cnt 198394 blk size 8*512
#############################################################################################################################################################################################################################################
Boot image size = 812620189 (0x306f999d) bytes
ROM:RSA Self Test Passed
ROM:Sha512 Self Test Passed
Package header rev 1 structure detected
Calculating SHA-1 hash...done
validate_package_cs: SHA-1 hash:
calculated 5bfc5c46:5941b63e:a7e1c9a3:4903de32:b6870cf5
expected 5bfc5c46:5941b63e:a7e1c9a3:4903de32:b6870cf5
Validating main package signatures
RSA Signed RELEASE Image Signature Verification Successful.
Image validated
Sep 10 10:17:47.605: %PMAN-3-PROCFAIL: R0/0: The process cmand has failed (rc 134)
Sep 10 10:17:57.376: %PMAN-3-PROCHOLDDOWN: R0/0: The process cmand has been helddown (rc 134)
Sep 10 10:17:57.550: %PMAN-0-PROCFAILCRIT: R0/0: pvp: A critical process cmand has failed (rc 134)
Sep 10 10:17:57.745: %PMAN-3-RELOAD_SYSTEM: R0/0: pvp: Reloading: System will be reloaded
Sep 10 10:17:58.764: %PMAN-5-EXITACSep 10 10:18:01.794: %PMAN-3-PROCESS_NOTIFICATION: R0/0: pvp: System report core/RP_0-system-report_20210910-101801-Universal.tar.gz (size: 2120 KB) generated and System report info at core/RP_0-systemt
09-10-2021 03:59 AM
Can i know what is the reason of Upgrade, is that recommended due to any vulenrability.
the error you getting, looks for me Bug, suggest to raise an TAC case (if this is production and effecting any services)~.
09-10-2021 04:12 AM - edited 09-10-2021 04:13 AM
Contact Cisco TAC and get them to confirm if this is CSCvz54262 (or not).
Avoid 16.12.X -- Go with the latest 16.6.X or 16.9.X.
09-10-2021 04:30 AM
I cant break boot to rommon
09-10-2021 06:09 AM
@mborej wrote:
I cant break boot to rommon
My response is: Contact Cisco TAC and get them to confirm if this is CSCvz54262 (or not).
09-11-2021 03:24 PM
Hello,
After the image 16.12.5 is validated, the logs generated suggests that cmand (Chassis manager daemon) process is failing and a system report is generated, stored in core folder.
It is too early to pinpoint a bug or a reason for it. If you have a SMARTnet contract, I suggest opening a service request with us to investigate further.
Thank you.
Marin Grabovschi
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide