Skip to Content
Last modified by Mark Kohlmann on 2024/04/05 22:02
From version 2.1
edited by Mark Kohlmann
on 2024/04/05 18:33
Change comment: There is no comment for this version
To version 3.1
edited by Mark Kohlmann
on 2024/04/05 22:02
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -47,7 +47,7 @@
47 47  * VC-4 Virtual Machine High Availability
48 48  ** VC-4 supports high availability at the hypervisor or operating system level
49 49  ** Option A - Hypervisor HA:
50 -*** Run VMWare ESXi with VMMotion or similar product
50 +*** Run VMWare ESXi with vMotion or similar product
51 51  *** VM infrastructure maintains state of VC-4 across multiple hosts.  If a host fails the system automatically fails over to a different host.
52 52  *** Caveats:
53 53  **** Doesn't protect against a failure of the operating system, VC-4, or ShowRunnerCLC™
... ... @@ -68,7 +68,7 @@
68 68  ** Once line is cutover, if the backup is online, the devices will be pulled and online within a few seconds or less.
69 69  * Cresnet Bridge
70 70  ** Cresnet devices may be redirected to a new processor via a simple IP Table change and reboot
71 -** Bridges generally support fewer devices and provide isolation between NETs only with alternate power options offering better protection than a processor connected Cresnet network.
71 +** Bridges generally support fewer devices and provide isolation between NETs with alternate power options offering better protection than a processor connected Cresnet network.
72 72  ** Caveats:
73 73  *** Typically the bridge must be rebooted after the change.  Downtime is typically 30 seconds to a minute before everything comes back online.
74 74  * Caveats:
... ... @@ -94,12 +94,12 @@
94 94  ** Backup would need to be reachable on the network
95 95  ** Primary and Backup Gateways would need to be the same model
96 96  ** Supervisory program would need to have a backup copy of the trust center from the primary gateway
97 -** The below thoughts are theoretically and have not be tested.
97 +** The below thoughts are theoretically and have not been tested
98 98  * Connect to the backup gateway and load the trust center from the primary gateway
99 99  * Configure the IP table on the backup to point to the correct processor
100 100  * Connect to primary gateway and wipe its trust center and IP table if reachable
101 101  * Devices should join the now active gateway.  How long this takes would need to be tested.
102 -* It is not known if the trust center backup/restore processor must be done through Toolbox or if it's something that could be embedded in a program without the need for Toolbox.
102 +* It is not known if the trust center backup/restore processor must be done through Toolbox or if it's something that could be embedded in a program without the need for Toolbox.  This will require significant development effort.
103 103  
104 104  ==== Best Practices ====
105 105