Primary SIS Controller IP
10.4.0.26
Secondary SIS Controller IP
10.8.0.26
Issue Not Communicating.
Well I can ping both IP but there is cross in DeltaV Explorer.
In Diagnostic if ping it.
It is also ping the CPU (10.4.0.26) but sometime it also pinging 10.5.0.26.
And continuously show me Not Communicating.
You mention it is trying to ping the 10.5.#.#.
That is the redundant partner's IP address (regardless of which physical node is the active node). Do you have redundant controllers?
Was the comms working previously or have you just commissioned this node?
In reply to Youssef.El-Bahtimy:
In reply to AdrianOffield:
In reply to obi1987:
10.4.#.# and 10.8.#.# represent the primary and secondary network connections on an active node.
10.5.#.# and 10.9.#.# represent the primary and secondary network connections on a standby redundant node.
I believe your redundant node pair is fighting over who is the active and is thus limiting comms with DeltaV. When you physically removed the redundant partner, you settled the argument, and the node that is left carried on communicating.
You should make sure both controllers are at the same firmware revision. Inspect the telnet log on the active controller to see if you can discern any notable events.
The third and fourth octets of the IP addresses of the standby controller are the same as the active controller. So you would have an IP address setup that looks like the following:
Where the third and fourth octets (.0.10 above) would vary based on the IP assigned to the controller.