Guys,
How is your rollout of the new 8.1.5.1 firware proceeding?
So far we have rolled out in one cluster. Had a few crashes that we reported to support butsince then no crashes reported. We are seeing a number of watchdog resets and the SM appears to reboot but this was also happening in 7.3.6.
We have not yet upgraded any Backhaul links.
We rolled out 8.1.5.1 to all of our locations except for one which has a high number of NAT users in setups similar to the “known issues” in the documentation. I will be waiting on that AP until they resolve those issues.
We deployed 8.1.5.1 on a backhaul set. This involved an upgrade from 7.1.4
What we did was:
1) Upgraded both Master and Slave to 7.3.6
2) Switched to HWS
3) Upgraded the Master to 8.1.4
4) Upgraded the Master to 8.1.5.1
5) Upgraded the Slave to 8.1.4
6) Upgraded the slave to 8.1.5.1
Note that if you have the Master on 7.3.6 and the Slave on vers 8 you will not manage to sync.
Just for everyone’s info we have upgraded SMs to 8.1.5.1 directly from 7.3.6 without going to 8.1.4
All went well. Only issue is that those of you who use 5.4 and do NOT need DFS will have to disable DFS individually on each SM as it comes back online.
I also upgraded a 900AP and six SM’s from 7.3.6 to 8.1.5.1 with no hitches.
I’m waiting until the weather gets better to do the rest of the network.
vanilla wrote:
All went well. Only issue is that those of you who use 5.4 and do NOT need DFS will have to disable DFS individually on each SM as it comes back online.
This isn't easy task when you have 5000 SMs. Acording to Moto we will have to pay $200000 for Prizm to do so...
Or you could script it. Use wget and view the source of the pages to figure out what you’ll have to send to each sm…