Emerson Exchange 365

communication slow down

Hello

We face a difficulty in our Deltav System, when we shutdown PRO+ station all operators stations slow down for about 20 seconds, and after that will be normal and only delay in Trend and event remain.we use application station and trend ad event are not configured in PRO+ station.we use deltav ver11.3.1, Pro+ windows server, and workgroup configuration

Regrads

Mohsenv

MOH

• 17 Oct 2016 7:31 AM
• Cancel

16 Replies

• Neil Castro

  

  • 18 Oct 2016 8:33 AM

  Hello Mohsenv,
  
  There are lots of reasons why the trend and event become slow when the PRO+ is disconnected or shutdown. In my experience following are a couple of reasons.
  1. Installation issue like NIC binding order not set to Emerson recommendation.
  2. Security issue like DeltaVAdmin password mismatch or user accessing the PHV is not present in the Application Station to where the continuous historian or event chronicle is located.
  3. Client not properly set. PHV data source not pointing to the continuous historian or event chronicle node. Try using the IP address of the continuous historian or event chronicle node on the PHV source.
  
  If it is possible you might want to post or send the Windows event logs (Application, System, and Security logs) of one of the affected operator station to have a better visibility of what is happening in the system.
  
  Hope this help.
  
  Cheers,
  Neil Castro

  • Cancel
• MOH

  

  • 18 Oct 2016 4:48 PM

  In reply to Neil Castro:

  hi Mr.Castro
  I face only slow down and not any error. the DeltavAdmin Password is same for all stations.
  I did not see any document related to NIC installation and recommendation.
  is there any special error or events and need to checked or attention to them
  Thanks
  Mohsenv

  • Cancel
• Neil Castro

  

  • 18 Oct 2016 10:11 PM

  In reply to MOH:

  Hello Mohsenv,
  
  There is a document from Emerson called XPHelp.chm and Win7Help.pdf that shows the proper installation of DeltaV nodes and it contains on how to properly configure the NIC binding order. This document may be downloaded from DeltaV support site.
  
  Look for warnings or errors in the Windows logs. Access error/warning or hardware error/warning may show some clue on what is causing the slowdown.
  
  Cheers,
  Neil

  • Cancel
• MOH

  

  • 19 Oct 2016 5:53 AM

  In reply to Neil Castro:

  Hello Neil
  Thanks, i will check.
  Regards
  Mohsenv

  • Cancel
• Andre Dicaire

  

  • 19 Oct 2016 4:03 PM

  In reply to MOH:

  As Neil indicated, the likely issue is the Binding order of the NIC's. It is a good place to start. You need to make sure the order matches with the Historian server. So check the server first, and set it up per the recommended order. Then check one of your Workstations and see if there is any thing out that needs to be adjusted. If you adjust the order and it fixes your problem, great. If not, continue to verify all the other workstations are correctly set up, including the Pro Plus. Then we can move on to other possible causes.

  Andre Dicaire

  • Cancel
• MOH

  

  • 19 Oct 2016 4:52 PM

  In reply to Andre Dicaire:

  Hi Andre
  thanks , for your answer. the order of NIC'S are correct. first one is primary second one is secodary and third one is plant lan.
  Regards
  Mohsenv

  • Cancel
• Steve Elves

  

  • 19 Oct 2016 4:57 PM

  I don’t think that’s correct.  The first NIC in the binding order should be for the DeltaV Secondary connection.  The second NIC in the binding order should be for the Plant LAN, and the third NIC should be for the DeltaV Primary connection.

   

  • Cancel
• MOH

  

  • 19 Oct 2016 5:08 PM

  In reply to Steve Elves:

  Hi Mr.Elves
  your answer is correct but i didnot see any communication error.
  Regards
  Mohsenv

  • Cancel
• Andre Dicaire

  

  • 19 Oct 2016 5:37 PM

  In reply to MOH:

  The Binding Order of the NIC's determines which network TCP/IP communications will use first. DeltaV process information does not use TCP and does not rely on the Ethernet Protocol to "find" the right NIC. It will explicitly send primary packets on the primary and Secondary packets on the Secondary. It uses UDP which is a connectionless transport, and so binding order does not affect DeltaV communications.
  
  PHV and OPC use the TCP layer and rely on the connection oriented transport and as such, connections must be established before communication happens. The connection is tried on the first NIC, then the second, then the third. Since DeltaV traffic prefers the primary, PHV data is passed over the Secondary as the preferred network. The second should be at the top of the binding order, the Primary should be at the bottom.
  
  So if the Primary is at the top of the Binding Order on all the computers, then binding order would not be an issue, though you should still set this to the recommended order as you want to eliminate any inconsistencies as you move towards a solution. With the Binding order "wrong", you may be experiencing some consequencial issue that is not seen as an issue when binding order is correct. You need to align the system with the supported setup first and move onto the next step. Skipping this puts anything else into question that has not been tested.
  
  As for why communication is affected by removing the Pro Plus from the system, that is still a mystery and I don't have an explanation why that would affect these machines or how binding order would play a role.
  
  We will need more detail as to what you mean by all machines are slow for 20 seconds. Focus on one machine and describe in more detail some specific behavior that is "slow". What is the behavior like normally?
  
  But fix the binding order first.

  Andre Dicaire

  • Cancel
• MOH

  

  • 19 Oct 2016 5:52 PM

  In reply to Andre Dicaire:

  Hi Andre

  Thanks i will try to reorder NIC's. when i did  restart or shutdown PRO+ station , operator stations are slow down or freeze for 20 seconds when operators click on display or try to change pages see waiting clock symbol in windows and not respons and after about 20 seconds will be normal but trends and event remain slow (try to open trendsin faceplate, time to show trends is take too)

  Regards

  Mohsenv

  • Cancel
• Dan Cascioli

  

  • 19 Oct 2016 7:23 PM

  In reply to MOH:

  In the event that a Plant LAN NIC is not used or the customer has decided to run a simplex DeltaV network, is it acceptable to move the DeltaV Primary NIC up or to the top of the Binding order respectively?
  Regards, Dan.

  • Cancel
• Brian Atkinson

  

  • 19 Oct 2016 7:32 PM

  The DeltaV documentation on workstation setup includes proper binding order for all sorts of network architectures, including simplex / duplex, PlantLAN or not, etc. 

  
  

  
  

  • Cancel
• Tinh Phan

  

  • 19 Oct 2016 9:01 PM

  In reply to Brian Atkinson:

  Here is a link to a KBA that may help to identify your issue: www3.emersonprocess.com/.../NA-0500-0025.pdf

  • Cancel
• MOH

  

  • 20 Oct 2016 4:44 AM

  In reply to Tinh Phan:

  Thanks Tinh

  • Cancel
• damer.j1975

  

  • 21 Oct 2016 7:17 AM

  In reply to MOH:

  Dear Mohesn,
  Run Server Password tools from BIN directory for all workstation or do Workstation configuration for all workstation one by one.
  I thinks it could be helpful.
  B/R
  Jefry

  • Cancel