Issue: The Sage RTU 3030M has two ethernet ports available, is there a way to use this two ports for a redundancy communication with the RTU, in case one connection fails, take advantage of the other.
Product Line: Sage RTU Devices
Environment: Industrial communication networks and protocols
Cause: Lack of information about this configuration in the corresponding manuals.
Resolution: The two ethernet ports are independent of each other, so you can assign each socket to a particular ethernet interface (primary vs secondary RJ45 connector). It is necessary to create a different socket, program it with the desire protocol and then you will have two independent comm paths to the RTU.
Notice that, if using ethernet, creating a 2nd socket is not enough to create redundant communication path if using the same ethernet interface, as that is a single point of failure. If a switch or router goes down, both the main and the redundant comm paths are taken down. DNPR also has the comm associations feature (is in the manual), that creates multiple Data Link paths to a single Application Layer session to accomplish that. But it is recommended to have the different Data Link paths be different communications paths.
Product Line: Sage RTU Devices
Environment: Industrial communication networks and protocols
Cause: Lack of information about this configuration in the corresponding manuals.
Resolution: The two ethernet ports are independent of each other, so you can assign each socket to a particular ethernet interface (primary vs secondary RJ45 connector). It is necessary to create a different socket, program it with the desire protocol and then you will have two independent comm paths to the RTU.
Notice that, if using ethernet, creating a 2nd socket is not enough to create redundant communication path if using the same ethernet interface, as that is a single point of failure. If a switch or router goes down, both the main and the redundant comm paths are taken down. DNPR also has the comm associations feature (is in the manual), that creates multiple Data Link paths to a single Application Layer session to accomplish that. But it is recommended to have the different Data Link paths be different communications paths.
