Unable to Upgrade to 5.2.2 ASR9k

johnmarkmlumanog · ‎01-20-2015

Dear Guru's

I'm trying to upgrade the ASR9k to 5.2.2 and i was stuck in "waiting for ARP reply"... already change to different TFTP server. below are my configurations.

rommon 21 > IP_ADDRESS=10.1.1.10
rommon 22 > IP_SUBNET_MASK=255.255.255.0
rommon 23 > TURBOBOOT=on,disk0,format
rommon 24 > TFTP_SERVER=10.1.1.1
rommon 25 > DEFAULT_GATEWAY=10.1.1.1
rommon 26 > TFTP_FILE=asr9k-mini-px.vm-5.2.2
rommon 27 > TFTP_BLKSIZE=1024
rommon 28 > sync
rommon 29 > boot tftp://10.1.1.1/asr9k-mini-px.vm-5.2.2

Beginning TFTP boot:
TFTP server specified is:
TFTP filename specified is: asr9k-mini-px.vm-5.2.2
Selecting MGMT LAN 0 interface.

IP_ADDRESS: 10.1.1.10
IP_SUBNET_MASK: 255.255.255.0
DEFAULT_GATEWAY: 10.1.1.1
TFTP_SERVER: 10.1.1.1
TFTP_FILE: asr9k-mini-px.vm-5.2.2
TFTP_MACADDR: 50:87:89:77:34:d8
TFTP_VERBOSE: Progress
TFTP_RETRY_COUNT: 18
TFTP_TIMEOUT: 7200
TFTP_CHECKSUM: Yes
ETHER_PORT: 3
ETHER_SPEED_MODE: Auto Detect
TFTP attempt 1 of 1
GigE link up, waiting for ARP reply ...
Receiving asr9k-mini-px.vm-5.2.2 from 10.1.1.1 ................... [TIMED OUT]
TFTP: Operation terminated.
Failed to TFTP boot from MGT LAN 0.
TFTP boot aborted by user.

tia,

Mark

xthuijs · ‎01-20-2015

Hi Mark,

Try either or both of the following:

Disable CPU watchdog reload after 30 minutes

At ROMMON promt

Rommon> priv

Rommon> diswd <- Disable the CPU watchdog

this will disable the reload even after 30 mins..

Set a larger tftp block size in rommon:

Rommon> TFTP_BLKSIZE=1400

this assumes that the ARP does resolve, if that arp doesnt resolve then we need to look at that further, but from your log it seems like that the transfer aborted after some period of time.

regards

xander

johnmarkmlumanog · ‎01-20-2015

Hi Sir Xander,

Thanks for your feedback. I've tried to reboot the machine before disabling the watching and I also changed the TFTP_BLKSIZE. And after doing so, the result is still the same. I'm using solarwinds tftp server at the moment and below are my configuration.

rommon 1 > IP_ADDRESS=10.1.1.10
rommon 2 > IP_SUBNET_MASK=255.255.255.0
rommon 3 > TURBOBOOT=on,disk0,format
rommon 4 > TFTP_SERVER=10.1.1.1
rommon 5 > DEFAULT_GATEWAY=10.1.1.1
rommon 6 > TFTP_BLKSIZE=1400
rommon 7 > priv
You now have access to the full set of monitor commands.
Warning: some commands will allow you to destroy your
configuration and/or system images and could render
the machine unbootable.
rommon 8 > diswd
Watchdog Disabled
rommon 9 > set
PS1=rommon ! >
CLUSTER_RACK_ID=0
ACTIVE_FCD=1
RMEMVA=
TURBOBOOT=on,disk0,format
TFTP_FILE=asr9k-mini-px.vm-5.2.2
?=0
TFTP_BLKSIZE=1400
IP_ADDRESS=10.1.1.10
IP_SUBNET_MASK=255.255.255.0
TFTP_SERVER=10.1.1.1
DEFAULT_GATEWAY=10.1.1.1
rommon 10 > sync
rommon 11 > boot tftp://10.1.1.1/asr9k-mini-px.vm-5.2.2
Beginning TFTP boot:
TFTP server specified is:
TFTP filename specified is: asr9k-mini-px.vm-5.2.2
Selecting MGMT LAN 0 interface.

IP_ADDRESS: 10.1.1.10
IP_SUBNET_MASK: 255.255.255.0
DEFAULT_GATEWAY: 10.1.1.1
TFTP_SERVER: 10.1.1.1
TFTP_FILE: asr9k-mini-px.vm-5.2.2
TFTP_MACADDR: 50:87:89:77:34:d8
TFTP_VERBOSE: Progress
TFTP_RETRY_COUNT: 18
TFTP_TIMEOUT: 7200
TFTP_CHECKSUM: Yes
ETHER_PORT: 3
ETHER_SPEED_MODE: Auto Detect
TFTP attempt 1 of 1
GigE link up, waiting for ARP reply ...
TFTP error 0 received (Connection timeout).
TFTP: Operation terminated.
Failed to TFTP boot from MGT LAN 0.
MGT LAN 1 port link is down. Verify port connectivity to switch.

tia,

mark

xthuijs · ‎01-21-2015

ok that so confirms that we're using the right mgmt port (0), but somehow the tfpt is not completing. I have seen that with certain tftp servers being an issue.

I have had good luck with the "winagents tftpserver 4" you may want to try.

another possible reason is a heavily down rev rommon that may not be able to boot a PX file properly. the easiest remedy is there to do a memboot on 434, update the rommon fpd on the rsp only and then either do a turboboot to the desired 522 release or a install upgrade to 522.

yes not very user friendly all suggestions, but some of them we have fixes for in place already other things (such as a manual fpd rommon update) is in the works to alleviate the complexity experienced here.

If you can get me the current rommon version you're having then we may want to consider a manual upgrade (eg tftp booting the rommon firmware to reprogram it).

xander

johnmarkmlumanog · ‎01-26-2015

Hi Sir Xander,

we have successfully upgraded the ASR9K to 5.2.2 by reseating the RSP's and we used the new IOS file image that cisco gave us and all went well. thank you for the help and support.

Thanks,

Mark

xthuijs · ‎01-27-2015

hey mark!

ah great ti worked out in the end, thanks for the update, that is awesome!

cheers

xander