When trying to update the remote switch in our SCN scenario, the upgrade failed and I can no longer connect to it. Is there anyway to reconnect to it remotely or will I have to connect to it?
It's only when your upgrading from 2.1 it's possible.
Your remote 406 have now erased it's *.bin file, and is broadcasting a TFTP-request on the local network.
You need to.
1. Set up a PC with a TFTP-server (Manager)
2. Change the PC's IP to the 192.168.42.0 range
3. Look in the Manager's TFTP-log, where you should see the request
4. Write down the IPO's IP-adr. and mac-adr.
5. Create a Bootp-entry with the details, pointing to the ip406.bin file (just use v2.1)
6. Boot the IPO (shouldn't be neccesary)
7. The unit should now come up with a green light!
Funny thing actually... I have done exactly the same as MTVilla a little month ago. My system was about 700 km's away, and had to run the next day. Damn i danced around when the helper at the remote site said the light was green!
One advantage of keeping a copy of manager installed on a PC at your remote sites, you can take over the desktop of that PC and do these sorts of things AS IF you were local...
but you are still up a cirtane body of water without a means of propulsion if the upgrade fails.
at least with the new 2.1 upgrade procedure the bin files are uploaded & veriffied BEFORE the system is erased.
I have upgraded my SOE at home from the office a number of times druing the 2.1 trials without a problem
I will be doing the same with 3.0 when it hits trial - hopefully by the end of august.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.