Maximum number of control networks per Connectivity Server
Hi,
I'm working in an Online Upgrade (5.0 SP2 to 6.0.3-1) project and just realized that I have a Connectivity Server with multiple Control Networks configured (3 with independent services running at the same Connectivity with the same IP range). When I'm planning the new system at System configuration Console I do not have the option to created more than 1 service for OPC DA at 1 connectivity server. So my questions are:
1. Can I create just the first one and after importing the fullbackup all of them will work? At 5.0 this works, but I think it's not how it was supposed to be at 800xA
2. Can I move projects between different Control Networks and perform an Warm download instead of a Cold Download? (Remember it's an online upgrade.)
3. Any specific procedure to fix it(move from 3 to one Control Network)?
Regards,
LS
I'm working in an Online Upgrade (5.0 SP2 to 6.0.3-1) project and just realized that I have a Connectivity Server with multiple Control Networks configured (3 with independent services running at the same Connectivity with the same IP range). When I'm planning the new system at System configuration Console I do not have the option to created more than 1 service for OPC DA at 1 connectivity server. So my questions are:
1. Can I create just the first one and after importing the fullbackup all of them will work? At 5.0 this works, but I think it's not how it was supposed to be at 800xA
2. Can I move projects between different Control Networks and perform an Warm download instead of a Cold Download? (Remember it's an online upgrade.)
3. Any specific procedure to fix it(move from 3 to one Control Network)?
Regards,
LS
Asked 2 years ago
Voted best answer
3
Why 6.0.3.1 when 6.0.3.2 with new Control Builder M and support for Server 2016 is available?
Without making any official statement and sanctioning I would expect the answers to be: yes, yes and no.
I sincerely recommend properly verifying this in a virtual mockup with eg one controller to ensure you have got the correct approach (retaining warm download capability requires proper execution of the upgrade tasks; read up on the online procedures - not all paths are open).
There are more ways to upgrade than stated in the official guide. Backup often, backup early. Maintain images, snapshots, etc. during the upgrade to be able to double back and repeat a failed attempt as if it would be the first time you try it. System Installer does not support going backwards or ”undeploying” something you got wrong.
When you have new 6.0.3 CS online, you should be able to point as many control networks as you like to the one common OPC DA Connector service group and configure any number of NICs and controllers to use them (within the performance envelope of course).
Without making any official statement and sanctioning I would expect the answers to be: yes, yes and no.
I sincerely recommend properly verifying this in a virtual mockup with eg one controller to ensure you have got the correct approach (retaining warm download capability requires proper execution of the upgrade tasks; read up on the online procedures - not all paths are open).
There are more ways to upgrade than stated in the official guide. Backup often, backup early. Maintain images, snapshots, etc. during the upgrade to be able to double back and repeat a failed attempt as if it would be the first time you try it. System Installer does not support going backwards or ”undeploying” something you got wrong.
When you have new 6.0.3 CS online, you should be able to point as many control networks as you like to the one common OPC DA Connector service group and configure any number of NICs and controllers to use them (within the performance envelope of course).
Add new comment