Search

5 result(s) for Warm

• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  6.6.2.4.1 Overview
  addresses 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 ... additional 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
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  6.6.2.4.4 Server Failover modes
  available but not running (PC is running, but application is not started) Warm Warm Failover mode is where the backup Server(s) can be active, but is not operating
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  6.6.2.4.5.1 General
  connections and Failovers . 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 ... might connect and choose to treat it as if the Server was running in Warm Redundancy or Cold Redundancy . This choice is up to the Client . In the case
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  6.6.2.4.5.3 Warm
  Warm A Warm Failover mode is where the Client should connect to one or more Servers in the RedundantServerSet primarily to monitor the ServiceLevel . A Client can connect and create ... illustrates the steps a Client would perform when communicating with a Server using Warm Failover mode. The monitor connection logic is defined in 6.7 . Figure 30 - Warm Failover NOTE There
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.3.15 NonTransparentBackupRedundancyType
  formally defined in Table 24 . A Server represented by this Type shall use the Warm Failover mode defined in OPC 10000-4 . Table 24 - NonTransparentBackupRedundancyType definition Attribute Value BrowseName NonTransparentBackupRedundancyType