Emerson Exchange 365

workstations work slowly and having delay in opening PHV

Hi

I want to ask you again about a problem that I have already asked you but your recommendations did not work.

My problem is about that when I shut down proplus  or remove it from deltav  network all operator workstations work slowly for around  1 minute in opening main page and faceplates until proplus shut down completely .after around 1 min they can open their pages and faceplates. But the main issue is when they want to open continues historian (trend) in this situation they are not able to open trend or sometimes they can with delay. I must tell in such this situation a page with retry and cancel popped up  

But they have to close it and reopen the trend that they want .i checked to ensure myself that application station work properly or no. application worked properly and all workstations connected to that.

So until now all things placed In the right place.

 After all our attempts to resolve the problem and having no result. i got recommendation Base on emerson recommendation (DeltaV NIC Binding Order configuration for WIN server 2008 ) i did emerson procedure as followings:

A PC with redundant Control Network and a plant LAN not configured as an

RDS (3 NICs - default).

1. DeltaV Secondary

2. Plant LAN (in my plant printer port)

3.DeltaV primary .

 

I reconfigured all workstations and application to. we got no answer again With this type of NIC binding order configuratins .and problem remain.

 

I have to say we have upgraded our DCS from 6.3 to 11.3.1 with MD controller.

One thing more I should say is that I did not change PRI and SEC hub switch we still use the old one that we used with deltav 6.3 .

Is it depend on deltav switch or its configuration?

 PLEASE HELP TO  RESOLVE THIS PROBLEM.

THANKS IN ADVANCE.

mahdi8261

• 16 Nov 2016 3:29 AM
• Cancel

10 Replies

• handia

  

  • 16 Nov 2016 6:12 AM

  Hello mahdi8261,
  
  I think I cannot answer your complete question, but I can give you some of my experiences with similar behaviour of our System.
  
  I would recommend to don't shut down the proplus. The contineous historian doesn't work correctly if "alarms & events" will be collected on the proplus. I also thought that we do store everything on the AS, but we don't do. Normally there is a combination of alarms & events and your contineous historian in trend views, etc.. So the reason for your possibilitie to open it anyway could be that deltav waits for the answer of the proplus (alarms & events) for it's diagram. This may take 1 Minute, which is your delay.
  
  Why you cannot open faceplates and main pages correctly without the proplus, I don't know. I only know that our proplus is running 24/7 (excluding some short neccessary restart intervals). We sometimes have Problems because our System has "dynamic references" that are located on the proplus. When we shut down the PP this sometimes generates some problems in handling our processes.
  
  
  
  I hope I could give you some new issues to think about for the reason of your problem.
  
  Best regards

  • Cancel
• Rachelle McWright

  

  • 16 Nov 2016 3:32 PM

  Hello mahdi8261,

  Thanks for posting your issue in EE365. In order to provide you with the best resolution, our experts in this area have suggested that you speak to an Emerson representative to discuss the specifics of your system in greater detail. To do so, please view the contact page for Emerson's Guadian Support Center to find info for your geographic area.

  Best Regards,

  Rachelle McWright: Business Development Manager, Dynamic Simulation: U.S. Gulf Coast

  • Cancel
• Jason.Brumfield

  

  • 5 Dec 2016 1:01 PM

  Knowledge Base Article, AUS1-115-990607142410 address some of this. We had a similar issue, turned out that when we did our upgrade, the host file that helps map the DNS name to the IP addresses was missing, so it had a hard time finding the secondary communication path. When it was on the primary, it worked great, but when it switched to secondary it would take forever. We had to add the entries back into the host file with both primary & secondary IP addresses for the proplus & the appstation to correct the issue. Hope this helps.

  • Cancel
• MOH

  

  • 6 Dec 2016 1:48 AM

  In reply to Jason.Brumfield:

  Hi mr. Jason
  Can you explain or send procedure?
  Regards

  • Cancel
• Jason.Brumfield

  

  • 19 Dec 2016 2:26 PM

  In reply to MOH:

  on your proplus in the c:\windows\system32\drivers\etc directory you should have a Host file.  Inside that file you will have the IP addresses/DNS names  for both the primary & secondary.

  10.4.0.xx PROPLUS

  10.8.0.XX PROPLUS

  10.4.0.XX APPLICATION STATION

  10.8.0.XX APPLICATION STATION.

  You will need to change the .XX to your system ip addresses & you will need to change the names to match the names of your proplus & whatever you are using for your backup DNS server.  We use our app station.

  Hope this helps.  Also attached is the article that I referenced earlier.

  Performance limitations in Process History View.pdf

  • Cancel
• MOH

  

  • 21 Dec 2016 3:59 AM

  In reply to Jason.Brumfield:

  Thanks mr.Jason

  • Cancel
• Andre Dicaire

  

  • 3 Jan 2017 9:29 PM

  In reply to MOH:

  Did the Host File suggestion work for you? Did you contact your Emerson service provider or the GSC for this issue?
  
  There are many variables in the system that can cause unexpected behavior or performance issues, and exploring this type of problem in a forum like this can more often cause you to chase false "solutions" and waste your time. Or you get similar stories that a likely unrelated in their root cause.
  
  For example, no one has asked if your system is set up as a Domain or as a workgroup. The Pro Plus must be a domain controller, and is also setup as the DNS server, which would normally provide name resolution, and therefore replaces the need for the Host File. But if you do setup as a domain, you should always have a secondary Domain controller. When the Domain controller is not available, computer name resolution and user authentication can experience issues.
  
  Logging this through the GSC will help you move systematically to a resolution as opposed to receiving unrelated and unverified suggestions that can leave you no closer to a solution. I expect that once the underlying cause is found, the solution will make total sense in hindsight. I encourage you to log this issue with the GSC.

  Andre Dicaire

  • Cancel
• MOH

  

  • 6 Jan 2017 2:25 AM

  In reply to Andre Dicaire:

  Hi Andre
  Thanks for your answer, and good advice. I work on it. The system is configured as a work group and as mentioned in KB, host file is working for Domin configuration. I find, the Historian delay is related to opening of event, when I select Chart only in process history view the system has no delay. I need to work on it, and for station slow down during Pro+ shut down i had not found any solution If i call all the time for service support, I am sure will be fire in this year [:)].
  The best Regards
  Mohsenv

  • Cancel
• Andre Dicaire

  

  • 6 Jan 2017 6:16 PM

  In reply to MOH:

  If you have Guardian support, you can call as often as you need. Better to resolve the issue quickly. As for response to Event data being slow, that can be a function of how much event data your system is generating, and the horsepower of the server running the SQL database. If you have many nuisance alarms, events etc filling up the Event Journal, you should focus on addressing the root causes. If the Event Journal is on the Pro Plus, that would explain why E+CHART call ups a slow when the Pro Plus is shut down, as the query is not being serviced and you have wait for some time out.
  
  Good luck.

  Andre Dicaire

  • Cancel
• MOH

  

  • 7 Jan 2017 1:57 AM

  In reply to Andre Dicaire:

  Hi Andre
  we use application station and the hardware is same as operator stations, i try to delete old event ,and configure maximum caacity of event to 100MB.
  thanks for your advise.
  Best Regards
  Mohsenv

  • Cancel