Edge high availability requires a Core; however, it is not a prerequisite to have Cores in a high-availability configuration. If Core high availability is configured, the active Edge in an HA pair can be added to either Core. The details for the Core you choose must be added to the Edge. After you configure Core high availability on the Core, the system automatically relays and stores information about the peer Core to the Edge.

On the Edge you want to use as the standby peer, choose Storage > Storage Edge Configuration. The standby peer must be the same appliance model as the active peer. Both peer appliances must be running Edge supported versions and must be configured for iSCSI/block mode. The peer appliance cannot have any local LUNs configured. Select Connect to an active Edge as Standby Peer for High Availability.

Specifies the serial number of the active peer. To find the serial number, choose Help on the active peer to display the Help page. The serial number appears under Appliance Details.

Specifies the self-identifier for the active peer. To find the Edge ID, choose Storage > Storage Edge Configuration on the active peer. The Edge identifier appears under Settings. This value is case sensitive and limited to these characters: 0 through 9, a through z, A through Z, period (.), and hyphen (-).

Both peer appliances must use the same self-identifier. In this case, you can use a value that represents the group of appliances.

Specifies the IP address of the Edge active peer. The active peer must not already be in an HA configuration with another Edge.

Specifies the local interface for the standby peer to connect to the active peer IP address. The blockstore Edge on-disk local cache synchronization happens through two local network interfaces for shared bandwidth and scalability.

Edge sends the data over the first local interface. Edge 4.3 uses Multipath NetDisk for blockstore synchronization between Edges in an HA configuration. If this local interface reaches 100% utilization, the rest of the traffic spills over to the second local interface. In Edge 4.1 and earlier, only one interface is in use at a time.

The first local interface transfers data until it reaches maximum throughput, and then the second local interface transfers the remainder of the data. For example, if the local interfaces are 1 GB and 10 GB, and you expect the 10 GB interface to transfer the bulk of the data, specify the 10 GB link as your first local interface.

Both the local and second local interfaces participate in load-balancing. When more than one interface is transmitting data, the total bandwidth is increased or decreased dynamically (the links are not utilized evenly). When all preferred paths are transmitting data, the data is queued.

Specifies the IP address of the active peer, which is different from the first peer IP address.

Specifies the local interface for the standby peer to connect to the second peer IP address.

As of Edge 4.3, the second local interface is used for data synchronization between Edges in an HA configuration using Multipath NetDisk (see Local Interface).

Multipath NetDisk is enabled by default as of version 4.3. To lower the HA throughput, you can disable multipath NetDisk using the no edge modify id netdisk-mpio active-active command. After using this command, you need to restart the Edge service using the service storage restart command.

Specifies the local interface for the current appliance to use when connecting with the Core appliance.

Completes the configuration and connect to the active peer appliance.

After configuring the product, the page displays the current settings and status, and it provides access to additional settings and information. If you have configured Edge high availability, the page displays the peer self-identifier and whether it is assuming the standby or active role.