We currently have 17 sites running 9.3.29. We are trying to get them all upgrade to 5.0. Here is the problem each site has 2 controllers. 1 controller uses a IVR that is not compatible with any of 4.0 releases. We have worked with the vendor and have 5.0 working. Mitel is suggesting we can bo a back up and then restore to a different controller ( we have 4 MXE's in our lab) then upgrade the controllers all the way to 5 then do a back up and a fresh install on the original controllers to 5.0 and do a restore. One of my concerns is if we dont have the same licenses on our lab controllers what will it do? Say I have 30 user licenses in the lab and 100 on the controller I need to upgrade will it keep the 100 users or will it delete them after the 30 licenses are used? Any ideas would be greatly appreciated. We are trying to do this as effectively as possible so we dont have the sites down a long time to try to do upgrades on both controllers from 9. to 5.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Need advice
- Thread starter dclynch
- Start date
You can't jump from 9 to MCD 5. You have to go from 9 to MCD 4, enable SDS and shared directory then go from 4 to 5.
You also can't restore a database to a system of less licenses then what was on the system the database was taken from. In that case you could use the over subscribe in MCD 5 but you would have to find some means of going from 9 to MCD 4 first. You would need a MCD 4 system with sufficient licenses for the migratiom from 9 to MCD 4.
I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.
You also can't restore a database to a system of less licenses then what was on the system the database was taken from. In that case you could use the over subscribe in MCD 5 but you would have to find some means of going from 9 to MCD 4 first. You would need a MCD 4 system with sufficient licenses for the migratiom from 9 to MCD 4.
I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.
can you not remove internet access from the original controllers, resync the lab systems to the arid giving them the same licenses. bit of hardware resetting needed and never done it myself but maybe someone else can add a bit to this if possible
- Thread starter
- #6
Well we have a small site that is at 4.2 so I did a restore of that to our lab that is at 5.0. Here are the problems I ran into. Could not use DNS to get to the original controller as it went to the lab not a big deal. Found the restore only brought over 1 Spectr-link phone instead of the 4 on the original controller. It did not bring over any of the analog devices but I suspect the reason for that is we dont have a ASU on the lab going to play with the 9.0 and see what happens when we restore to 10.0. I will continue to post the issues we have. I appreciate all the comments so far.
It is quite simple really.
Remove the DNS setting on the active system to prevent syncronization
Modify AMC record for site and clear the hardware ID
Configure the lab system with the same IP settings as the active system
Use the lab system to download the licenses from the AMC - This will reset the hardware ID
Upgrade the lab system using Full Install to 4.0 and restore using copy of existing DB
Migrate DB to SDS Mode Synching
Upgrade to release 5
Get backup to restore to active system.
You will need Mitel to clear the Hardware ID's again once all upgrades have been made.
The other logistics of this seem obvious to me so I'll hold off on advice not requested.
**********************************************
What's most important is that you realise ... There is no spoon.
Remove the DNS setting on the active system to prevent syncronization
Modify AMC record for site and clear the hardware ID
Configure the lab system with the same IP settings as the active system
Use the lab system to download the licenses from the AMC - This will reset the hardware ID
Upgrade the lab system using Full Install to 4.0 and restore using copy of existing DB
Migrate DB to SDS Mode Synching
Upgrade to release 5
Get backup to restore to active system.
You will need Mitel to clear the Hardware ID's again once all upgrades have been made.
The other logistics of this seem obvious to me so I'll hold off on advice not requested.
**********************************************
What's most important is that you realise ... There is no spoon.
- Thread starter
- #8
Thanks KWB that is what I was thinking. I am waiting for approval from the boss to do this. I also found a spare ASU so I can hook that up to my lab system and will have all hardware requirements to get everything working. My only question and it may sound stupid. When I disable the DNS settings will it have any effect on the working system other than not being able to contact the AMC. We are trying to do this with as little impact to the sites as possible. I can go into the AMC to clear the hardware ID and I understand that I will need to contact Mitel to have it cleared a second time. Good Information making me less nervous. I am going to try and start Sunday night.
This is how our techs do these type of upgrades:
Using a pc with 2 NIC's connect 1 NIC (using DHCP) on the data LAN for AMC access, the other NIC with a static IP address to connect to the controller. When setting the static address for the NIC that connects to the controller click the "Use this DNS" at the bottom of the settings window and enter the DNS that the customer uses for their data connections. (This would also work with a laptop that has wireless access for the data LAN connection. The ethernet port would have the static address and connect to the controller.)
Use the Software Installer tool to upgrade the controller from 9.x to 4.0. Click the License box during the SI set up and enter the ARID when the License form appears in the SI tool. The SI tool will get the licenses from the AMC and then apply them to the controller during the upgrade.
During logon to the new 4.0 software select SDS. After logon do a DBMS Save and then use the SI tool to upgrade from 4.0 to 5.0 again using the License form in the SI tool with the ARID to update the licenses. This whole process should take about 3 hours and requires the 4.0 and 5.0 software and appropriate SI tools. This way the license sync is done by the SI tool during the upgrade process and does not require any controller access to the AMC or any hardware id resets or software release changes in the AMC. The SI tool does all that.
(Our techs also use Filezilla as the FTP server and keep multiple 3300 releases in separate release folders. They only have to load the correct SI tool for the release of software they want to use and enter the FTP username in the SI tool that matches the release they are loading. But that is another discussion.)
I hope this makes sense. It's easier to do than describe.
Using a pc with 2 NIC's connect 1 NIC (using DHCP) on the data LAN for AMC access, the other NIC with a static IP address to connect to the controller. When setting the static address for the NIC that connects to the controller click the "Use this DNS" at the bottom of the settings window and enter the DNS that the customer uses for their data connections. (This would also work with a laptop that has wireless access for the data LAN connection. The ethernet port would have the static address and connect to the controller.)
Use the Software Installer tool to upgrade the controller from 9.x to 4.0. Click the License box during the SI set up and enter the ARID when the License form appears in the SI tool. The SI tool will get the licenses from the AMC and then apply them to the controller during the upgrade.
During logon to the new 4.0 software select SDS. After logon do a DBMS Save and then use the SI tool to upgrade from 4.0 to 5.0 again using the License form in the SI tool with the ARID to update the licenses. This whole process should take about 3 hours and requires the 4.0 and 5.0 software and appropriate SI tools. This way the license sync is done by the SI tool during the upgrade process and does not require any controller access to the AMC or any hardware id resets or software release changes in the AMC. The SI tool does all that.
(Our techs also use Filezilla as the FTP server and keep multiple 3300 releases in separate release folders. They only have to load the correct SI tool for the release of software they want to use and enter the FTP username in the SI tool that matches the release they are loading. But that is another discussion.)
I hope this makes sense. It's easier to do than describe.
You don't need the ASU. The system will restore even if the hardware is not present. Its the licensing that will be the issue. There are two suggestions above that are prerfect for what you want.
We have done the reset hardware ID, use it in a lab, then reset it again to return it to the customers hardware. Works a treat.
One final thing if your MXE's are MXe III's in the lab make sure you use MCD 4 SP 4 for the 9 to MCD 4 upgrade.
I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.
We have done the reset hardware ID, use it in a lab, then reset it again to return it to the customers hardware. Works a treat.
One final thing if your MXE's are MXe III's in the lab make sure you use MCD 4 SP 4 for the 9 to MCD 4 upgrade.
I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.
- Thread starter
- #11
Ok cleared app records got 4.0 SP4 loaded on 2 controllers tried to configure SDS road block . Error restore was from a different IP address (which it was ) . Ok pulled both controllers off network changed IP addresses to correct address did a restore again. Now the problem is getting the 2 PBX's to talk to implement SDS. Any ideas? Here is what we have tried so far. We took a cheapo linksys router . One controller is on a .64 subnet while the other is on a .68 subnet. We plugged a cable into the .68 PBX and used the internet port on the router and the .64 into a port then used 2 ports for our Pc's to connect. We set our IP addresses to .64 and .68 The .68 can access both PBx's but the .64 can only access the .64 PBX. Any ideas on how to get them to talk?
easiest way in my thinking is if you have network gear where you can create VLANs, then create two new VLANs with the subnets you require. Then setup routing between the two subnets. This of course depends what you have available.
I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.
I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.
- Thread starter
- #13
Thanks Loopy we got them talking. It was a stupid mistake on my part had the wrong gate way programmed. I will keep everyone up to date. Hoping to get to 5.0 tonight. I want to thank everyone for the help on this. This will save us a tremendous amount of over time (and I wont have to work the weekends for the next 4 months) and only will have our sites down for 2 -3 hours instead of days.
I'd use something like a HP layer 3 switch (2610)
create 2 vlans set a port to be untagged in each vlan , connect the mitel to this port
set the IP addresses for each vlan as the current gateway addresses of the Mitel controllers
turn on Ip routing... easy
I have done 6 site Clustering in this method pre deployment
create 2 vlans set a port to be untagged in each vlan , connect the mitel to this port
set the IP addresses for each vlan as the current gateway addresses of the Mitel controllers
turn on Ip routing... easy
I have done 6 site Clustering in this method pre deployment
- Thread starter
- #15
- Status
Similar threads
- Locked
- Question