How to configure redundant OPC network link for the 3rd Party OPC Servers.
Here in one project I’m facing a problem in one of the OPC communication. OPC is working fine and server redundancy also working. But customer is asking for network redundancy.
Please find the configuration attached herewith.
In PLC control configuration aspect, in edit drive popup, OPC server node and redundancy server node we gave our primary and secondary server name and in opc server we browse one of matrikon tunneller IP(192.168.121.218). And that’s working fine. But they have another IP address 192.168.122.218.
Where to give the second IP path to our system? We tried to give the path to “access path (optional, OPC server specific data)), but it’s not working.
I believe PLC Connect redundancy is achieved by configuring two (2) PLC Connect connectivity servers.
If you have a singular PLC Connect connectivitity server but would like to enable redundant networks you must make use of some network redundancy capable protocol, e.g. ABB's RNRP.
Apart from RNRP you can also use some open redundancy protocol like OSPF, STP, etc.
While we connecting to third party OPC Server, We have to use the Node/Host/Computer name, instead of giving IP Address. By Giving remote Computer name to connect/ping, it will reach the remote computer by whatever means of network availability.
In your case - Server Name is OPCCS02P having IP Address1: 192.168.121.218 and IP Address2: 192.168.122.218.
Here you have to give server Name "OPCCS02P" in OPC Server Node input filed instead giving two IP Address. By giving Computer name, first it will try to connect through first NIC, if it fails then automatically it will try to connect through second NIC. Hence network redundancy is achieved via mentioning Server name instead of IP Address.