Importance of deltav patches, Redundancy problems for controllers, cioc and Batch Executive

Dear all,

I have a running DeltaV 12.3.1 build 5219. I inserted in to the system 3 new servers, one pair redundant batch executive and one batch historian, with the latest patch ws_34_css. If I restart the servers, first the primary and then after the secondary, i get  active batch executive station the preferred active, and preferred standby (_S) as standby,  and i am able to request switch over between this two stations. The problem is that i am unable to request switch over back , because after the switch over the preferred active is seen in (_S) as not configured, not available. I got all kind of strange readings about all the devices from deltaV network as there's secondary ports are disconnected.

Another stange thing is that after the switch over the server that is set as standby is not longer recognised in DeltaV Diagnostic, communications are in bad, ping from deltav diagnostic is not possible, but the ping from  windows works.

Another thing is that the deltav process does not start, but if I reboot  them so preferred active is set as active everything goes to normal.

I noticed that every time i have introduced in to the deltav system some redundant device (cioc controller, controller),  at first the redundant node it does not work , the communication is Bad for the secondary node, after some downloads it will be eventually recognised. But still if i trigger an request switchover the former active card goes not recognised, not available (as it is disconnected) , then recognised but not available, and then after available and seen as valid for switchover. The duration of these transitions is about 5-10 minutes. For me it seems a strange behaviour, could someone confirm this is ok?

How important is to have the same patches installed in all of the servers of the domain? Is it any difference if the Pro Plus has the original patches  from installation and on the computers from domain the patches varies (some BE have ws_21_css, some the original ws_01_css, the new ones BE ws_34_css)

And could someone tell me why the software revision for this bex pair is 5316 for preferred active and 5312 for preferred standby? Is it normal?

2 Replies

  • I omitted to mention that after the switchover when the prefered active set as stanby , on the batch facesplate the Error is active, no communication is seen, and in the DeltaV diagnostic is seen as not configured, not downloaded, active not available, deltav service does not run unless i reboot the server.
  • In reply to stamate_mircea:

    The most weird thing is that the swrev on standby is "Matilda" , and diagnostic run from primary it shown last download "Normal", but diagnostic run from (_S) it shows "Not executed" and "Active not configured". Could someone tell me what /who is matilda ?