Lx to MXe3 Upgrade

[f1fanatic]

HI All,

I am upgrading an LX to and Mxe3, and as part of this taking them up to MCD4.2, my question is this, the MXe3 come out as part of MCD4.2, i need to migrate the database on the LX from release 8 to MCD4.2, the MXe3 has shipped on MCD4.2, do i need to downgrade it to MCD4.0, migrate then re-upgrade to MCD4.2, but i am thinking that the MXe3 is not supported and will not work if try to downgrade to MCD4.0.

What is the best method of doing this?

Thanks

 

[bobcheese]

you will need to upgrade to MCD4.0 on the LX (providing it is on of the model numbers supported. This should be in the release notes) then convert database to Common data distribution and then restore to the MXeIII running MCD4.2

 

[DoubleUT]

THIS WILL NOT WORK!
You are trying to replace the LX with a MXe. Todo so they need to be at the same level based on AMC. The LX has "old" license structure and that can only be used on mxe systems running 4.0 or lower. After they have been registered on the AMC you can upgrade to higher software version.

 

[DoubleUT]

Forgot to mention that MXe III systems only run 4.2 software, you need to purchase MXe II system.

 

[Supernova99]

This is a PITA to do going forward for anyone who is upgrading to a MXe3 from a LX with 256mb RAM installed.
As I see it you will need to
1. upgrade the LX to rel 9.0 ur3
2. Datasave
3. install 4.0 on a MXe2
4. Clear hardware ID on AMC
5. retrieve licences on MXe2
6. restore database from LX
7. migrate to common data sharing
8. upgrade to rel 4.2
9. datasave
10. clear hardware ID on AMC
11. restore database from MXe2

Share what you know - Learn what you don't

 

[f1fanatic]

Just spoke to Tech Support, the way suggested was to take the Lx to 4.0, perform database migration to RDN sync, then backup database and restore it to the MXeIII. The Lx just needs to have 512mb of Ram.

Thanks all.

 

[Supernova99]

If your LX has 512mb then all you need to do is

1. upgrade to rel 4.0
2. migrate to common data sharing
3. upgrade to rel 4.2
4. perform datasave
5. clear hardware ID on AMC
6. enter app record on new MXe3 controller and retrieve licences
7. restore from backup

Share what you know - Learn what you don't

 

[bobcheese]

Hey f1fanatic, just to clarify, despite what DoubleUT says this is possible (process as per my and Supernova's post providing you have 512 RAM. Just another note to make, alot of the old controllers came with free software assurance until 01/01/11 so if you are planning on doing this work after this date then you will need to ensure you have active software assurance on this application record before attempting the upgrade.

 

[Supernova99]

Good catch Bob

Share what you know - Learn what you don't

 

[DoubleUT]

Guys,
Please read the docs delivered with 4.2 explaining that
MXe III can only run 4.2 and is only licenced with the New Standard or Enterprise Licences. So again this only works with MXe II system and not with MXe III. The AMC is a stumbling block in this matter.

 

[DoubleUT]

Copy of the release notes from 4.2:

Hardware Changes
3300 MXe III Controller
Following the curve on technology improvements, we will begin transitioning (based on inventory) from the current MXe II Controller to a new MXe III Controller. The updated MXe III Controller will be very similar in form factor and capacity size to the MXe II Controller but will see new SATA-based drives incorporated into the Controller. The 3300 MXe II Controller will continue to be available and will remain in the MCD 4.2 Sales WorkBench product view.

Note: ***The 3300 MXe III Controller will only work with MCD software 4.2 and above.***

Copy from a Sales dokument:

3300 MX Controller running 3300 Software Release 9.0 wants to upgrade to a 3300 Controller running MCD 4.2
• Purchase new 3300 Controller that can run MCD 4.0
• Complete a System Back-up of the old Release 9.0 system
• Install the new 3300 Controller running MCD 4.0 in a Classic distribution model
• Reset the Application Record Hardware ID in the AMC
• Connect the new 3300 Controller to the newly reset Application Record ID
• Restore the old 3300 Release 9.0 System back up onto the MCD 4.0 system
• Migrate the MCD 4.0 to utilize the new System Data Synchronisation model following the upgrade and migrate instruction.
• Upgrade the system to MCD 4.2
• Dispose of the old 3300 Controller

Looking at the first stap of the Sales doc. you have purchased the wrong hardware. Swap this for a MXeII and you are good to go.

 

[bobcheese]

i think you are missing a trick here DoubleUT. If the LX controller has 512Mb of RAM then it IS supported on MCD4.0 and therefore there is no need to purchase an MXeII controller. once controller is upgraded to MCD4.0 and the subsiquently upgraded to MCD4.1 (after db conversion) the AMC will automatically upgrade the base package to 'standard' or 'enterprise' depending on the options purchased. Then its just a case of reseting the hardware id on the AMC, sync'ing the new controller and restoring the 4.1 db to the MXeIII controller running MCD4.2

 

[Supernova99]

That is the way I see it too.
Granted if you have a MX controller the only way is via a MXe2 as the MX only has 256mb RAM.
But if the LX has 512mb RAM then this is entirely possible.

Share what you know - Learn what you don't

 

[DoubleUT]

The fact that he has a LX system connected to a NSU made me think that his LX system is an older one, therefore 256mb and not a 512mb system.

 

[bobcheese]

sorry, dont see any mention of NSU here?

 

[f1fanatic]

Bobcheese, DoubleUT is correct on the NSU, i created a sepearte post, as i have never worked on them so wanted some heads up on possible catches.

Agreed with everyone, it all depends on the LX having 512mb RAM, which to give dues to DoubleUT i beleive it will only have 256mb due to age of system. So may need to use an MXe2, with sys id from MXe3, perform upgrade and migration and swicth the sys id back to MXe3, and then restore DB from MXe2 to MXe3, long way round but will get me there i suppose.

I thank everyone for their input, many thanks.

And happy new year to all.