cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3746
Views
10
Helpful
9
Replies

ASR-9001 stuck in ROMMON

Boris Simunko
Level 1
Level 1

Hello all!

 

I'm dealing with a very naughty 9001, a customer handed it to me in a bad state already. They tried to do an upgrade, but something went wrong (not sure what or when). ROMMON is the only option at the moment...

 

I have been trying to ressurect it through a TFTP boot, but to no avail! I am using the asr9k-mini-px.vm-6.2.3 file (only one I got), but it seems the router does not like it. The TFTP transfer is successfull, but after the upload it spits this out:

 

tftp_process_packet: last packet, block=4173, size=1001.
File reception completed.
Image size=608252905, TFTP download size=608252905
image_checksum_test: NO checksum test. Not an ELF file.

TFTP: Disabling cache

Unable to handle image type: 0

 

I am not sure which image I just be using then?

 

rommon B1 > version

System Bootstrap, Version 3.4(20160331:102636) [ASR9K ROMMON], 
Copyright (c) 1994-2016 by Cisco Systems, Inc.

Compiled Thu 31-Mar-16 15:56 by skumarss

Board Type: 0x100401
CPU Board => Rev: 0x3
=========
FPGA ver: 01.0f
CBC: 16.72

1 Accepted Solution

Accepted Solutions

that was it! i downloaded a new vm file (6.2.3 acctually) and everything worked, must have been corrupted.

 

so first i did a tftp turboboot, the router booted with no problem, and i could than upgrade to 6.3.3

View solution in original post

9 Replies 9

tkarnani
Cisco Employee
Cisco Employee

would it be possible to try to use a usb instead of tftp?

just to rule out any issue during file transfer

it doesn't work, tried it 

 

rommon B1 > dev
Devices in device table:
id name
bootflash: bootflash
configflash: configflash
disk1: disk1
disk0a: disk0a


rommon B2 > dir disk0:
File System: FAT32

3 0 drw- System Volume Information
6 1681786880-rw- ASR9K-iosxr-px-k9-6.3.3.tar
410599 608252905 -rw- asr9k-mini-px.vm-6.2.3


rommon B3 > boot disk0:/asr9k-mini-px.vm-6.2.3

Boot Status 16
program load complete, entry point: 0x100000, size: 0x2ac20
Set baud rate to: 9600
Fail to open file name disk0//asr9k-mini-px.vm-6.2.3
loadprog: error - on file open
boot: cannot load "bootflash:disk0//asr9k-mini-px.vm-6.2.3"

Boot Status 15


rommon B4 > boot disk0:asr9k-mini-px.vm-6.2.3

Boot Status 16
program load complete, entry point: 0x100000, size: 0x2ac20
Set baud rate to: 9600
Fail to open file name disk0/asr9k-mini-px.vm-6.2.3
loadprog: error - on file open
boot: cannot load "bootflash:disk0/asr9k-mini-px.vm-6.2.3"

Boot Status 15


rommon B5 > dir bootflash:
usb_stor_BBB_comdat:usb_bulk_msg error
failed to send CBW status -2147483648

 

the router than just loops the 2 red lines until I take the usb out and reload it. i have tried with different usbs...

 

PS disk0 and disk1 are the same usb port when in ROMMON

can we try without the /

boot disk0:asr9k-mini-px.vm-6.2.3

 

also try

 

mediaboot usb:asr9k-mini-px.vm-6.2.3   or

boot usb:asr9k-mini-px.vm-6.2.3

here's how it boots after a reload:

 

Bootstrap, Version 3.4(20160331:102636) [ASR9K ROMMON],
Copyright (c) 1994-2016 by Cisco Systems, Inc.

Compiled Thu 31-Mar-16 15:56 by skumarss

Starting Initialization of FMAN0
Loading ucode for FMAN0, size: 6992, ver: 101.08.00
Starting Initialization of FMAN1
Loading ucode for FMAN1, size: 6992, ver: 101.08.00
Serdes Protocol: 0x10

CPU Reset Reason = 0x0001
Initializing GIGE SW...
PPC P40X0 (partnum 0x8023), Revision 03.00, (Core Version 03.01)

Sys Clock: 100 Mhz
Core Clock: 1500 Mhz
Plat Clock: 800 Mhz
LBC Clock: 25 Mhz
MEM Clock: 1300 Mhz

 

System Bootstrap, Version 3.4(20160331:102636) [ASR9K ROMMON],
Copyright (c) 1994-2016 by Cisco Systems, Inc.

Compiled Thu 31-Mar-16 15:56 by skumarss

Board Type: 0x100401
CPU Board => Rev: 0x3
=========
FPGA ver: 01.0f
CBC: 16.72


DTI programmed with latest image

TIMEX programmed with latest image
MLAN init done: ready to connect to the network
BCM5482PhyInit () : Port 0 --> SFP Not present
BCM5482PhyInit () : Port 1 --> SFP Not present

set_chassis_type: chassis_type=0xef0400 found=TRUE
ASR9001E (P40X0 PPC) RSP platform with 8192 Mb of main memory

program load complete, entry point: 0x100000, size: 0x2ac20
Set baud rate to: 9600

CARD_SLOT_NUMBER: 0
CPU_INSTANCE: 1
MBI Validation starts ...

Disabling both Mgt LAN ports
Enabling Cluster Port 0 and disabling Port 1
BCM5482 cluster port-1 reset done !!
Port 0. SFP Not Ready (0:0). Init failed

dtsec_init_hw: configuring DTSEC (port 8) for: 1GB, Full Duplex
Interface link changed state to UP.
Interface link state up.

MBI validation sending request.
HIT CTRL-C to abort
.. [CTRL-C]

 

there is no "mediaboot" command...

 

rommon B2 > dir disk1:
File System: FAT32

3 0 drw- System Volume Information
6 1681786880-rw- ASR9K-iosxr-px-k9-6.3.3.tar
410599 608252905 -rw- asr9k-mini-px.vm-6.2.3


rommon B3 > boot disk1:asr9k-mini-px.vm-6.2.3

Boot Status 16

Usage: <device name>:/<filename>

Boot Status 15


rommon B4 > boot disk1:/asr9k-mini-px.vm-6.2.3

Boot Status 16
usb_stor_BBB_comdat:usb_bulk_msg error
failed to send CBW status -2147483648

 

rommon B6 > boot usb:asr9k-mini-px.vm-6.2.3
Invalid boot device: usb:asr9k-mini-px.vm-6.2.3

Boot Status 15

 

 

This error seems to be an issue with the usb controller

 

usb_stor_BBB_comdat:usb_bulk_msg error
failed to send CBW status -2147483648

 

i would try once more, maybe download 6.3.3 vm file and try to boot with it.

both usb/tftp if you get the same errors, you have pretty much tried all combinations

 

if it fails at that point, i would open a TAC case and have them create an RMA for you

 

Thanks

 

it's not the same error, the tftp option fails with the "Unable to handle image type: 0" error, which looks to be not related to the file or file transfer itself...

 

i can not find the 6.3.3 mini vm file, is it this one ASR9K-iosxr-px-6.3.3-turboboot.tar ?

Yes, it should be in that tar

that was it! i downloaded a new vm file (6.2.3 acctually) and everything worked, must have been corrupted.

 

so first i did a tftp turboboot, the router booted with no problem, and i could than upgrade to 6.3.3

great!, glad it worked out