Upgrading from 4.1 SP1 to 4.2 SP2

[KurpeusLondon]

Hi Guys,

I'm planning to upgrade my cluster of 3300 CX II controllers. They are actually running MCD 4.1 SP1 and use SDS.

I've never done any upgrade before so not sure what to expect.

My plan of action is the following:
I upgrade my main controller first. First I reroute all incoming routes to secondary controller. I do a backup of the both controllers and I take the main controller off the network. I proceed with my upgrade and once completed, I reinstate the node in the network. I check everything is working properly and I can go to bed. The next night I proceed with the second controller (as they are separated by 300 miles) in the same way.

Is that a problem to have a cluster running different versions for 24 hours ? (Any configuration changes during that time will be prohibited)

Any advises you be really appreciated !

 

[kwbMitel]

Step 1 - Check AMC for Software Assurance on Both systems.
Step 2 - Backup system including embedded VM if exist
Step 3 - Route incoming calls to secondary??? (you know best)
Step 4 - Remove Controller from Network? - Not necessary but won't hurt anything
Step 5 - Proceed with upgrade
Note1: - PC running upgrade should have static address or one not supplied by Mitel Controller.
Note2: - For really nervous nellies, collect maintenance port data using terminal emulator.

Wait approx 45min to 1 hour for upgrade to complete

Step 6 - restore controller to service

No issues running separate Revs for short periods of time.



**********************************************
What's most important is that you realise ... There is no spoon.

 

[kwbMitel]

RE: Remove system from Network.

PC needs access to internet to download licensing from AMC. Might be best to leave system on network unless you have wireless access to internet from PC.

**********************************************
What's most important is that you realise ... There is no spoon.

 

[KurpeusLondon]

Thanks KwbMitel

I have few acd paths that terminate on the primary controller. I've created identical ACD paths on the secondary and both are using the same agent group IDs. For this case I change my speed dials to use the paths on the secondary controller. The home location of my phones is mixed between the two controllers and are resilient with the other.
The reason I want to take the controller off network is I don't want to have my phone belonging to the ACD paths re-homing to the controller while upgrading. I prefere to wait the system is stable before returning phones and services to the primary.

I believe I can manually enter the licence and I'll have wireless Internet access anyway.

I've seen I'll need to enter the ip load 1 - 100 (CX II controllers ) to change the firmware of the IP phones. Should I do that once both controllers are upgraded ?


Cheers,

 

[LoopyLou]

One: don't manually enter the licenses as that "locks" the system so that if you buy a user license you have to do the whole manual license procedure rather then simply having the system retrie the new license from the AMC. The sets won't rehome to the primary while you are doing an upgrade, it will take a while after that is complete before the sets try to go back. If you have wireless access via your laptop you can use internet connection sharing within Windows to allow the software installer to contact the AMC itself ( set your laptops NIC to the default gateway IP and run a cable from the laptop directly to the 3300 ).

Two: Only issues I am aware of when running verying loads with SDS is you get errors syncing COS for example if the COS in the new load contains new features not contained in the older load. Not a really a problem just a waring.

The single biggest problem with communications is the illusion that it has taken place.

 

[CharlesBr]

I have seen an issue regarding different versions in a cluster when the phones are resilient:

Controller A: MCD 4.2 SP1 (10.2.1.13)
Controller B: MCD 4.1 SP2 (10.1.2.16)

Primary controller for the phones was A, when they'd reboot on B they'd get the older firmware but upon rehoming on A some phones would not come back up (they'd get stuck @ upgrading flash)...