different software release on same cluster? 1

[brewski6666]

Have a cluster of three ICP 3300 release MCD 4.2, want to add a new 3300 to the existing cluster with the last release (MCD 5.2 SP2), don’t need to sync all the forms, the customer wants internal calls between sites and wants resiliency between the new 3300 and one of the existing ICP.
My question is: is there any issue that I can expect because of the different software release? (Customer don’t want to pay for the upgrade)

 

[LoopyLou]

You can mix the loads without major issues. Where you get problems is the differences in features between the loads. i.e MCD 5 has a feature in COS that MCD 4 doesn't. Therfore everytime you sync COS you will get SDS errors because the MCD 4 systems don't have the new feature.





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.

 

[brewski6666]

Thks Loopylou

 

[DoubleUT]

If you are going to programm resiliency then they should have the same software version. If different versions then you get a lot of SDS errors and possibly database issues. The system won't be supported and the easy fix is install 4.2 on the new system!

 

[LoopyLou]

One thing we have found is that you should make a set resilient then program it keys. We have had some issues with making a set resilient that has certain keys like multiline. If you have different loads you might want to cut back the forms you share to a minimum to reduce SDS errors.

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.