Hi All!
I Have a query regarding Redundant Standby Controller Network Communication.
I am unable to ping to the Secondary connection of one of the Redundant Standby Controller in the DeltaV system (There is no comms and the request times out)
There is some issue with the connection I suppose.
In the DeltaV diagnostics, the secondary of the Redundant Standby Controller still shows healthy.
It should show bad and that Comms not healthy.
Anyone else faced this issue before?
Thanks
Andre Dicaire
In reply to Andre Dicaire:
Hi Andre Thanks for the reply, The DeltaV Version is 13.3.1, The controller types whose Secondary comms is not working (Only for the redundant standby controller)MD+, MD and MQ types, More than 20 controllers, Only 6 controllers(Md+, MQ and SD+ types) have all their comms which ping.
The addresses that I pinged were 10.4.**.**, 10.5.**.**,10.8.**.**,10.9.**.**, I am unable to ping 10.9.** when 10.5 is standby and 10.8 where 10.4 controller is standby.
I pinged from Diagnostics and also from the cmd prompt but the request times out in both the cases. The strange thing is on these controllers in diagnostics, when I try the the TCP/IP through Secondary comms of the standby controller it fails, but says detected with multicast ping, Also the Telnet does not work through these secondary comms. The other Strange thing is secondary comms of both the active and standby controllers are connected to the same Switch in the Rack room and come through the single fiber to the control room network switch, and Iam able to ping to the secondary of the active controller, No issues there.
The other thing is some Fiber ports on the secondary switch are blinking in a different manner than the primary and some secondary port connections.
These ports in the DeltaV network command center are showing port locking violation though these ports are enabled. I can send a video of that If you provide me your mail id.
In reply to dikshitsh:
Hi Andre Yes. we are using RM100 smart switches. The firmware is 9.0.12.
The interesting thing was though the ports were enabled but also had a locking violation (We never have changed/removed cables after upgrade/installing smart switches). Yesterday, I had done an unlock of these switches with the auto lock of 60 minutes enabled, The comms were restored but as soon as the 60 mins expired and the switch was locked again, we got the same standby sec. comms. failure (Locking violation again) on a few controllers (Not all which had this issue initially), So I again unlocked (Without the auto lock timer) and locked it manually after the unlock was successful, have been 16 odd hours as I reply and all the comms are working fine, Dont know what the root cause for this comms failure was (Lock violation) or Why It wasnt fixed first time when I unlocked and locked the switches. I had logged a call with GSC a couple of days ago, sent them the DDC but still await their feedback, I shall update you once I hear back from them. Thanks for the reply and help.