When did updating a DP become such a headache? Maybe it's me. I remember a time when I would plug a DP2K into a show and if it had old software, the console would simply reload the proper software onto the DP and all was good. I have just tried updating my second Dp8K in two days to 3.2.5 and neither of them would update completely. I have tried reloading from the console, force loading from the console, force loading from a bootable usb stick....not one of them worked. The first DP8K didn't seem to respond to anything, just stayed on the DP8000 logo and wouldn't even attempt to update. The next one actually did attempt to update the software, but got to a point during boot up that it was just stop and then reboot again, and again, and again, and again, until I pulled all my hair out. I have successfully updated many DP8Ks, some with ease, but most have always been a headache. Am I wrong? Wasn't it easier to do this in builds past? It seems like now, if you have any kind of custom network settings, you have to go and reset to default in order to update it. I am waiting on a third DP8K to show up. Hopefully the third time is, in deed, the charm.
Right, I have finally got it to update and at risk of looking stupid I wanted to post again so that anyone making the same error will know what to do.
I ended up using a direct connection with a crossover cable. In the network settings I enabled DHCP Servers and also Boot Server and then used default network settings. Then after forcing a firmware reload it did it. The one thing I hadn't got selected earlier was the boot server, so I am sure this was my main issue. It may well have worked first time with my network switch connected....i'll find out next time I have to do this as this was my first time updating my DP.
Anyway, all sorted, thanks for your help Mitch. Hopefully if anyone has the same trouble they will learn from my mistake.
Is there anyway in the future the software could help this process out a little by alerting the user if key settings are not selected that are crucial to performing the update? Just a thought.
Right, I have finally got it to update and at risk of looking stupid I wanted to post again so that anyone making the same error will know what to do.
I ended up using a direct connection with a crossover cable. In the network settings I enabled DHCP Servers and also Boot Server and then used default network settings. Then after forcing a firmware reload it did it. The one thing I hadn't got selected earlier was the boot server, so I am sure this was my main issue. It may well have worked first time with my network switch connected....i'll find out next time I have to do this as this was my first time updating my DP.
Anyway, all sorted, thanks for your help Mitch. Hopefully if anyone has the same trouble they will learn from my mistake.
Is there anyway in the future the software could help this process out a little by alerting the user if key settings are not selected that are crucial to performing the update? Just a thought.
