Two active event managers negotiation time.
- nurlygayanov
- Posts:2
- Joined: Sun Oct 02, 2016 12:01 pm
Two active event managers negotiation time.
If I cut connection between two redundant event mangagers, they will both become active. If I restore the connection after that, they will both remain active for some time and then one becomes active and another one passive. I was wondering if there is a way to speed up the process of deciding which of the two will become active after the connection is restored. In my case, the process usually takes about 15 seconds.
- fmulder
- Posts:330
- Joined: Wed Feb 03, 2010 9:46 am
Re: Two active event managers negotiation time.
In my opinion you should always prevent to have two active servers. We try to prevent that by using two cross-cables between the servers.
This is the cheapest solution to ensure the best possible connection between the two
Good luck
share the fun
Frenk Mulder
This is the cheapest solution to ensure the best possible connection between the two
Good luck
share the fun
Frenk Mulder
- leoknipp
- Posts:2928
- Joined: Tue Aug 24, 2010 7:28 pm
Re: Two active event managers negotiation time.
Normally for connection attempts between two WinCC OA processes the interval defined with connectDelay is used.
The default value is defined with 20 seconds.
With the debug option -dbg dispatch for the event- and the redu-manager you can see when they are trying to establish a connection.
Then you can see the interval which is used for establishing the connection to the redundant partner.
Maybe the time can be decreased by defining the following config entries, the values is defined in seconds:
[event]
connectDelay = 10
[redu]
connectDelay = 10
I didn't test it therefore I do not know exactly if it works in that case.
As one server needs to be restarted for the recovery after the connection has been established it should not make a big difference if takes 10 or more seconds to detect that the connection is available again.
Best Regards
Leopold Knipp
Senior Support Specialist
The default value is defined with 20 seconds.
With the debug option -dbg dispatch for the event- and the redu-manager you can see when they are trying to establish a connection.
Then you can see the interval which is used for establishing the connection to the redundant partner.
Maybe the time can be decreased by defining the following config entries, the values is defined in seconds:
[event]
connectDelay = 10
[redu]
connectDelay = 10
I didn't test it therefore I do not know exactly if it works in that case.
As one server needs to be restarted for the recovery after the connection has been established it should not make a big difference if takes 10 or more seconds to detect that the connection is available again.
Best Regards
Leopold Knipp
Senior Support Specialist