Table B.2: Redundancy Behavior
(Continued)
Repair MeasuresEffect
Fault
Treatment
Fault DetectionFault Condition
Repair Ethernet
connection.
System
degrades to
non-redundant
system.
Secondary
device
clears
configuration.
Secondary
device
assumes and
indicates
non-operational
state
2
Time-out on TCP
connection.
Detection time less than
2 s during activity and less
than 7 s during idle times.
TCP connection
lost between
primary device and
secondary device.
7
Secondary device
may reboot in some
cases depending on
prior state and will
receive
configuration data
from primary device.
Repair or reconnect
redundancy link.
System
degrades to
non-redundant
system.
Secondary
device
assumes and
indicates
non-operational
state.
Loss of serial
communication.
Detection time less than
800 ms.
Redundancy link
broken or removed
between primary
device and
secondary device.
8
Secondary device
will reboot and
receive
configuration data
from primary device.
1. This fault condition may also result in a cyclic reboot of the secondary device.
2. If the secondary device reboots cyclically in this state, set the TCP acknowledge timeout (object 22223)
to a smaller value.
In any case, the fully redundant state will be obtained again when the secondary device
indicates “operational” (refer to Status Indicators - LEDs on page 37) and its H1 live lists
are complete. In highly populated, tightly configured H1 links, it may take several minutes
to acquire the live lists. Before the live lists are completed, redundancy switching is
possible but client server connections can only be established to H1 devices that are in
the live list.
Any further error that occurs before the fully redundant state is reached, may cause the
system to fail.
2PAA114135-610 111
B Technical Reference
B.6 Redundancy
To Next Page
Loading...
