Redundancy config.redu

[RKoczan]

I'm using a redundant system and have configured the config.redu file based on an example I found.
Manually initiating fail over works fine. However when I disconnect the active server from the network theres a delay of about 9 seconds before the system switches to the other server.
Ive edited the config.redu file, removing anything that's not applicable just leaving the following entries:

activeChangeInterval
aliveCheckInterval
aliveInterval
delayChange =1

Changing the values of activeChangeInterval, aliveCheckInterval and aliveInterval makes no difference what so ever.

If activeChangeInterval = 0, the redundancy switch should be immediately it not
also if If activeChangeInterval = 50 it still takes approx. 9s.

the config.redu is been read, as if I put a some junk in there that's reported in the logger.

Does anyone know how to speed up changeover when a server is disconnected?

Thanks

[leoknipp]

In the config.redu file for your project you only have to add those entries which shall be changed in your project.
There is no need to copy the config.redu file found in the WinCC OA installation to the project directory.

Probably it takes about 9-10 seconds in your project until the redundant servers detect that the connection is lost.
In the config file you should find entries similar to the following ones
WCCILevent (0), 2018.10.18 15:55:22.985, SYS, SEVERE, 39, Connection lost, Alive timeout expired, closing connection to (SYS: 315 Event -num 0 CONN: 2) (P) @ Server2-2 (192.168.120.23). Last message expected at 2018.10.18 15:55:22.860.

The alive timeout is defined with the config entry aliveTimeout.
Please take into account that using a aliveTimeout < 5 seconds is not recommended.

Even if it takes a few seconds until a loss of connection is detected you will not loose data.

Best Regards
Leopold Knipp
Senior Support Specialist