Maximum Phone Reboot.

[RedTech443]

What would be a safe number for a maximum amount of phones to reboot for new firmware.
Phones are 9608 / 9611
Using s8300d utility servers on 6.3
I have a few thousand to reboot, and did not want to do them all at once.

 

[Wanebo]

I've rebooted over 2500 sets at a single time, but that said there are some considerations.

How fast is your network? Are you hosting the ftp files locally or do the sets have to reach across a WAN to fetch them? How well will your users tolerate the occasional set that does not come back up cleanly on their own? How quickly can you troubleshoot the sets that don't come back cleanly?

The first two don't impose a limit on the amount of sets you can reboot at once, but they will affect how quickly the sets come back up.

The second two will impose somewhat of a line on how many you should limit yourself to doing at a time. You will have sets that do not come back up cleanly. It's almost a given certainty. Then it becomes a game of whether the end users won't freak out that their phone needs (at the very least) to be power cycled, or how many you can identify that did not come back up and how efficiently you can isolate those sets to the network port they are connected to and shut/no shut those ports.

 

[kyle555]

I agree with Wanebo. As an example, I've found copying gateway firmware over even a capable WAN to be slow - kind of like how your browser can have a download slow down and then speed up, it's like gateways don't know how to speed up again.

You used plural 'utility servers', so if you've got S8300s at each branch that can do it, you should be able to have each phone upgrade from something local and on the lan. Brush up on reset ip-stations and you can do it for 'ip-phones' and by IP range or network region

 

[RedTech443]

So to clarify a few things I forgot to add in the OP.

The network is all gig switches, all the files are local on each utility server, all servers are s8300d with minimum ram (so they are slow).

I figure after testing a bit that the best way is to do each subnet of each network region. This way I am limited to a range of 255 resets at one time, when that completes move to the next subnet for that region.

Probably safer to do it this way then just reset the whole ip-network-region at once.

 

[Wanebo]

That would be a good approach to use. As a bonus, since the order of the reloads will be so well defined, it probably will make it easier to track and find the sets that do not reload cleanly.

 

[RedTech443]

The way I do it is by first exporting the registered phones in that region using Site Admin, by doing a list reg reg # - then exporting to csv and then excel.
when I complete I do it again to compare with an excel formula and find the missing phones and ones that did not get new firmware. Works out pretty well.

Thanks for all the suggestions and help, hope you all have a good rest of the day.