ondamother
IS-IT--Management
Hi all, I upgraded a resilient cluster recently and have some questions from that.
The site has 3 Mitel 3300's (MXe's and LX) We have upgraded them from ver 8.0.11.7_3 to Ver 4.0 sp2. The upgrade of Entman and OPSman went well as did the upgrade of the first two sites.
The issue started on the upgrade of the last controller, where on starting the upgrade the Phones tried to hone to there secondary controller which was expected. Unfortunately they sat on DHCP discovery and on the secondary controller I received errors stating the below.
ViPER
Description: ValidateProtocolVersions() -> Protocol version mismatch (required=1.2.9 actual=1.2.8)
Once the Primary Controller was upgraded. The IP phones did not hone back and still tried to get there load from there secondary controller. Which in turn caused issues, due to the amount of TFTP sessions happening at one time…
As a result it took hours for the IP phones to load.
I think this was our error where after each 3300 was upgraded we entered the {Load all IP devices} command once all the IP phones had honed back to there Primary Controllers. This more than likely became a problem once everything had being upgraded, the last site had no where to Failover too but a Controller of a later version...
Should this command be entered after all 3300's in a cluster, that are resilient to each other, have been upgraded?
Any advice much appreciated.
The site has 3 Mitel 3300's (MXe's and LX) We have upgraded them from ver 8.0.11.7_3 to Ver 4.0 sp2. The upgrade of Entman and OPSman went well as did the upgrade of the first two sites.
The issue started on the upgrade of the last controller, where on starting the upgrade the Phones tried to hone to there secondary controller which was expected. Unfortunately they sat on DHCP discovery and on the secondary controller I received errors stating the below.
ViPER
Description: ValidateProtocolVersions() -> Protocol version mismatch (required=1.2.9 actual=1.2.8)
Once the Primary Controller was upgraded. The IP phones did not hone back and still tried to get there load from there secondary controller. Which in turn caused issues, due to the amount of TFTP sessions happening at one time…
As a result it took hours for the IP phones to load.
I think this was our error where after each 3300 was upgraded we entered the {Load all IP devices} command once all the IP phones had honed back to there Primary Controllers. This more than likely became a problem once everything had being upgraded, the last site had no where to Failover too but a Controller of a later version...
Should this command be entered after all 3300's in a cluster, that are resilient to each other, have been upgraded?
Any advice much appreciated.