05-09-2017 11:52 PM
->Tried it, same result. Also tried just a hafailover.
did you issued only "hafailover" or "hareboot" ?
become the Standby CP as Active CP
05-10-2017 12:01 AM
I tried both.
I think the reason is that the standby CP is not availible on the network after a failover. It answers on ping but you can't log into it with ssh.
05-10-2017 12:13 AM
I would suggest to try to do "firmwaredownload" from a CLI and not from BNA.
another option you can try is to launch "firmwaredownload -s" also on a single CP
If the error persist, then open TAC.
05-10-2017 12:15 AM
As mentioned earlier I have done the firmwaredownload from CLI also.
I have not done for each CP. Would that work if I did it for the active one first, then hafailover to standby and to that one when it's active?
1. firmwaredownload -s on active (cp0)
2. hafailover to standby
3. firmwaredownload -s on active (cp1)
05-10-2017 12:29 AM
to summarize, what ever CP (or or 1) which is standby is answering pings, but no reachable via ssh or able to do firmwaredownload. I would work out the networking issue before doing the firmwaredownload to 8.0.2b. Feels like a networking issue.
But one way would be to use the firmwareactivate possibility - assuming CP0 is active
on CP0: firmwaredownload -lr
on CP0: hafailover
on CP1: firmwaredownload -lr
on CP1: firnmwareactivate
I have never used the firmwareactivate on a director class switch, only on pizza boxes.
05-10-2017 04:04 AM
I will try an upgrade from a USB stick first and see if that works just to exclude the networking issues.
Also add that the standby CP does not respond to ping either after a failover. So there is something wrong I think.
But I will try a USB upgrade first.
05-10-2017 10:11 AM
So the USB download worked just fine. So the problem is network related.
I will make a new thread for the network problem I am having.
Thanks for all the suggested solutions.