Cobalt 8.1 - 20181029
227
ETC recommends that ETCNet2 systems should be in the 10.101.x.y range - "Primary" NIC.
Network - Server takeover, loss and return (8.0)
If consoles in any segment of a Session lose contact with consoles in any other segment, each segment
will select a new Server. If segments then rejoin the network, the Session must rapidly detect which
segment is the leader and rejoin it, with all other Servers becoming Backups.
There are three possible situations
No activity has occurred in any segment.
• There is no show data to resolve.
• The lowest-numbered Server stays as Server, all higher number Servers return to the Backup
state
Activity has occurred in only one segment
• The inactive Server becomes a Backup.
• Consoles enter the “Catching” state and catch up to the rest of the Session
Activity has occurred in more than one segment
• The Server with the most recent Session activity remains Server
• All others become a Backup
• All consoles enter the Catching state and sync their activity.
If changes were made to the same object in two segments, the older changes are lost in both cases. If a
network switch is lost, many Consoles in the Session will then become isolated from each other. Some
of these may be able to see each other, while others do not.