A‑Link and Private Networks

Every everRun system requires a network for private management traffic between the two physical machines (PMs). This private network is referred to as priv0, which is a physical, direct Ethernet, or VLANed connection between the nodes. Priv0 is used for peer node discovery and can have no other entities on it that respond to IPv4 broadcasts.

In addition to priv0, each system has A-Link networks to increase data-replication performance between the PMs. A-Link networks let you sync disks, shunt networks, migrate VMs, and sync fault-tolerant memory.

By default, priv0 also performs the role of an A-Link network under the following conditions:

Priv0 cannot perform the A-Link role if its speed is less than 10 Gb and the system contains any 10 Gb ports (other than the management link). However, you can assign the A-Link role to priv0 at a later time.

The simplest priv0 consists of a single Ethernet cable (crossover or straight-through) that directly connects an embedded Ethernet port on each server. If a networking device other than a single Ethernet cable is used for priv0, see SplitSite Configurations.

Connect A-link networks between PMs either directly (that is, in the same manner that you connect priv0) or through a network switch.

Be sure to set up redundant A-Link networks.

The everRun installation software sets up priv0. It also sets up A-Link networks for any A-Link network ports that are physically connected at the time of the installation. To set up an A-Link network after the installation is complete (recommended if the network includes many additional A-Link network ports), see Connecting Additional Networks.

Related Topics

Business and Management Networks

A‑Link and Private Network Requirements

Network Architecture

Fixing a Network Connection