Originally Posted by apw2607
Search the thread. The updating process has being discussed already.
Saw lots of discussions of if you should, what features they have, what they fix, what they break, what they do, what they don't do, metaphysical repercussions thereof, etc... All stuff I'd read before purchasing the unit.
I saw nothing discussing hung updates. I may have missed it, but I did a keyword scan on every post in the thread.
At any rate, it was fairly obvious from checking the port usage on the switch and bandwidth usage from the router that the thing wasn't talking. When the thing booted up it pulled DHCP immediately and saw the patch. I don't like to let infrastructure type network devices sit on DHCP, so I gave it it's hard IP that the previous player had, then went in and told it to update. Mayhap some logic within the update process got into a schitzo "there's an update, but the network went away, but the network's here, but oh noes I confused". Doesn't matter. It wasn't talking, and once I took it's physical network away it figured it out and shut off. Once back up, with the hard IP from boot it saw the update availability and started pulling it down in what I presume is a normal fashion.
How many folks are going to worry about messing with a hard IP on one of these? Can't speak to that. But if anyone does, my suggestion would be to bounce the chassis one more time after changing IP's before updating firmware.
It's a pretty specific combination of events, and will probably only happen that one magical time someone's first hooking up the chassis, but there it is.