IO Server redundancy behaviour and syslog related query

With my redundant IO Server,

I monitored back to back trace entry for my modbus device's PORT in Standby SCADA's IOserver syslog,

2020-07-08 19:20:50:2050 +05:30 [TRACE] [CORE       ] [0x2b18] [IOServer        ] [(GLOBAL)        ] [InitChannel()                                     ] [plc_drv.cpp                   ] [1272] Channel nPort_009_S is Online
2020-07-08 19:21:20:2120 +05:30 [TRACE] [CORE       ] [0x2b18] [IOServer        ] [(GLOBAL)        ] [InitChannel()                                     ] [plc_drv.cpp                   ] [1272] Channel nPort_009_S is Online
2020-07-08 19:20:20:2020 +05:30 [TRACE] [CORE       ] [0x2b18] [IOServer        ] [(GLOBAL)        ] [InitChannel()                                     ] [plc_drv.cpp                   ] [1272] Channel nPort_009_S is Online
2020-07-08 19:20:50:2050 +05:30 [TRACE] [CORE       ] [0x2b18] [IOServer        ] [(GLOBAL)        ] [InitChannel()                                     ] [plc_drv.cpp                   ] [1272] Channel nPort_009_S is Online
2020-07-08 19:21:20:2120 +05:30 [TRACE] [CORE       ] [0x2b18] [IOServer        ] [(GLOBAL)        ] [InitChannel()                                     ] [plc_drv.cpp                   ] [1272] Channel nPort_009_S is Online

In this case my devices's communication is healthy all the time and no single entry found in Primary SCADA's IOserver syslog.

Can someone explain this behavior?

Primary SCADA Kernel,

Standby SCADA Kernel,

If this IODevice is connected to Primary SCADA Server then why error count in Driver windows increasing?

Why Unit status is offline in Standby instead of Standby?

Parents Reply Children
No Data