Complete GUI Guide
9: Configuring with the GUI
To connect to the RSF-1 GUI, direct your browser to hostname:port as shown in the output of the pkgadd installation procedure as shown in section 3.2.
The first stage is to tell the GUI configurator the name of the other node to be added to the cluster. Before the above dropdown menu appears, the GUI scans the local network for other servers running RSF-1 in cluster-discovery
mode and populates the dropdown menu with the name of any host it finds.
NOTE – A node cannot enter RSF-1 cluster-discovery mode until it has been licensed and therefore it will be necessary to enter the other cluster node name manually in the box provided
Once the other node name has been entered, you will be asked to confirm selection before the configuration process starts.
Once confirm is clicked, the first stage process will quickly complete.
9.1: Licensing RSF-1 with the GUI
At this point, it is necessary to license the product on both nodes. If you have already been provided with a temporary or permanent license, this can be entered manually by selecting the manual option; alternatively, a temporary evaluation license can be obtained by clicking Auto.
In either case, the RSF-1 End User License Agreement (EULA) must be accepted before proceeding.
Once the terms and conditions have been accepted, enter a valid email address to receive the temporary licenses.
To manually install the license, select the Manual option and enter the codes exactly as provided in the respective fields and click confirm. This will install licenses on both cluster nodes and only needs to be performed once.
Once the license keys have been successfully installed, RSF-1 will automatically restart and both cluster nodes can be configured.
9.2: RSF-1 Configuration through the GUI
Once RSF-1 has automatically restarted, the cluster is ready to be configured.
, three ZFS pools, POOLA
, have already been created and imported using the zpool create command. To being configuration, click the Configure
Once initialization has completed, you can begin to configure services and add ZFS volumes.
9.3: Creating Services and Adding Volumes
Click the Volumes
tab on the left-hand column to go to the Cluster Volume Operations
page, and select a volume to cluster from the pull down list as shown:
In this example, we are going to configure a service for POOLA
Once selected, complete the fields for IPV4 Failover hostname and click Confirm. In the following example, a second service, POOLB
, is configured with the associated VIP support-staff-public
In this example, we also want to add a second pool, POOLC
, to the POOLA
service. Select the Advanced Operations tab on the left column to access the Advanced Operations page, and then click on the Add/Remove Volumes
tab. You can now drag-and-drop the additional pool, POOLC
, on to the service meaning that both POOLA
are associated with the same RSF-1 service and will move together through the cluster.
to complete this configuration.
9.4: RSF-1 Status with the GUI
To view the current cluster status, click on the Status tab on the left-hand column to access the Cluster Status page.
This screen shows the current location of each service and the respective Volume states and Failover modes and allows the operator to stop, start and move services throughout the cluster. Right-click the mouse over each of the pools to see what operations are possible. The following screenshot shows the operations available on remus for POOLB.
9.5: Moving Services between Cluster Nodes
In this example, we want to move the service POOLB
During this process, POOLB
will be cleanly stopped on remus
and then restarted on romulus
Once this move has completed, romulus
is running POOLB
and remus POOLA
9.6: Viewing Cluster Heartbeats with the GUI
In addition to the cluster status
page, you can also view the cluster heartbeats
page by clicking the Heartbeats
tab on the left column. The first tab, Volume Heartbeats
, shows the disk heartbeats.
The second tab, Appliance Heartbeats
, shows the network heartbeats.
9.7: Adding Additional Network Heartbeats with the GUI
We can also add additional network heartbeats on this page. In the worked example, we also have a private network connection between the two servers named romulus-priv
respectively. To add network heartbeats using this private interface, right-click over the server name to see the option:
In this example, we are going to add a heartbeat connection between remus
and between romulus
The status now shows two separate network heartbeats connecting both nodes:
Click Save Settings
to confirm the addition.
The basic cluster is now configured. For additional File/Block service configuration, please refer to section 7, and to section 8 for failover testing.
Please also consult the RSF-1 Administrators Guide
available from http://www.high-availability.com/resources/