Search
4 result(s) for Hot
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services6.6.2.4.1 Overviewaddresses and unique ApplicationUris . The Server also has additional Failover modes of Cold , Warm , Hot and HotAndMirrored . The Client shall be aware of the RedundantServerSet and shall be required ... examples and explanations are provided in 6.6.2.4.5.2 .for Cold , 6.6.2.4.5.3 for Warm , 6.6.2.4.5.4 for Hot and 6.6.2.4.5.5 for HotAndMirrored . A Client needs to be able to expect that the SourceTimestamp
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services6.6.2.4.4 Server Failover modesServiceLevel of the available backup Server will be in the Degraded ServiceLevel sub-range. Hot Hot Failover mode is where all Servers are powered-on, and are up and running
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services6.6.2.4.5.1 GeneralFailovers . Table 107 - Redundancy Failover actions Failover mode and Client options Cold Warm Hot (a) Hot (b) HotAndMirrored On initial connection in addition to actions on Active Server : Connect ... treat a Server using a lesser Failover mode, i.e. for a Server that provides Hot Redundancy , a Client might connect and choose to treat it as if the Server
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services6.6.2.4.5.4 HotHot A Hot Failover mode is where the Client should connect to two or more Servers in the RedundantServerSet and to subscribe to the ServiceLevel variable defined ... each connected Server . Clients have the following choices for implementing Subscription behaviour in a Hot Failover mode: The Client connects to multiple Servers and establishes Subscription (s) in each where