High Availability system requirements

Lists the hardware, software, and network requirements for deploying
FactoryTalk® Optix™
High Availability
.

Requirements summary

Review these hardware, software, and network requirements before you begin installation.
High Availability system requirements
Requirement
Details
Cluster layout
Exactly three Ubuntu cluster nodes, each on a separate physical machine.
Windows management workstation requirements
A workstation required for the High Availability Manager. See Windows management workstation.
Networking
All three cluster node IP addresses and the virtual IP (VIP) must be on the same local network, connected to the same physical switch or VLAN, with no router between them, because automatic failover does not work across routers. Reserve one extra free IP address for the VIP.
Time synchronization
All cluster nodes must use the same approved NTP sources, with time synchronization active before provisioning. Node clocks must differ by no more than 1 second; do not continue if any node is unsynchronized or differs by 5 seconds or more. 10 seconds is an absolute maximum for lab use only.
Critical dependencies
SSH connectivity from the Windows management workstation to all three cluster nodes, static IP configuration on each node, matching port configuration between the cluster and your project, and the administrator password that you set during installation.
TIP: If you are not sure whether the network meets this requirement, check with the network administrator before you begin.

Windows management workstation

The Windows management workstation must meet these network requirements:
  • The Windows management workstation must have an internet connection.
  • Port
    22
     must be available for SSH-based provisioning.
  • Port
    6443
     must be available for Kubernetes API communication with
    kubectl
    .
  • Port
    443
     must be available for HTTPS downloads of
    helm.exe
     and
    kubectl.exe
    .
The Windows management workstation must include these tools.
Required tools
Tool
Version
Purpose
Windows PowerShell
5.1 or PowerShell 7+
Run manager functionality.
OpenSSH client
Built into Windows 10 or Windows 11
Connect to the Ubuntu cluster nodes over SSH.
kubectl
Compatible with K3s v1.34.6
Manage and inspect the Kubernetes cluster. It is installed automatically by the High Availability Manager.
Helm
3.x
Deploy the cluster charts. It is installed automatically by the High Availability Manager.
FactoryTalk Optix
 Studio
1.8.0 or later
Create and deploy your
FactoryTalk Optix
 project to the cluster.

Ubuntu cluster nodes

Each cluster node must meet these requirements.
Cluster node requirements
Requirement
Details
Operating system
Ubuntu 22 (64-bit)
RAM
Minimum 3 nodes at 4 vCPU and 8 GB RAM, recommended 3 nodes at 4 vCPU and 10 to 16 GB RAM
Disk space
Minimum 50 GB per node (for the OS, K3s, application data, and audit logs)
IP address
Static IP address, on the same network segment as the other cluster nodes and the VIP
User account
A user account with
sudo
 privileges
Internet access
Required to download K3s and other required packages during installation
SSH server
openssh-server
 must be installed and running. The HA Manager connects to each node over SSH during installation.
IMPORTANT: If you restore, reboot, suspend/resume, or perform network recovery on a node VM, check time synchronization on all cluster nodes before continuing with provisioning.
Clients always connect to the VIP to reach the
FactoryTalk Optix
 application, never to an individual node IP address.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal