Veritas InfoScale™ 7.4.1 Virtualization Guide - Linux on ESXi

To configure SFCFSHA cluster settings

1. Run installer - configure or just continue from where we left in the previous step entering y.
2. Fencing would normally be the next step in configuring SFCFSHA. However, the I/O fencing configuration depends on other factors which are not yet determined:

   • VMDKs or RDMP storage devices are used

   • How I/O and network paths are configured

   • Configuration of coordination point (CP) server (or, in some cases, Coordination Disks)

   For now you can enter n when prompted to configure IO fencing in enabled mode and come back to it later in the configuration process.

3. Configure the cluster name when prompted.

   The cluster name for the example deployment is cfs0

4. Configure the NICs used for heartbeat when prompted.

   LLT (Low Latency Protocol) can be configured over Ethernet or UDP. UDP is needed only when routing between the nodes is necessary. If UDP is not needed, then Ethernet is the clear recommendation.

   In the example deployment, eth4 and eth5 are the private links. Eth3 is the public link, and it will be only used as low priority heartbeat path (so it only will be used if the other two paths fail).

   All media speed checking should succeed. If not, please review your node interconnections.

5. Configure the cluster ID when prompted. A unique cluster ID is needed: it is vital to choose a number that is not used in any other cluster. This is especially true when using the same network interconnection (both private and public). The CPI generates a random number, and checks the network to make sure that packets with that ID do not exist. However the CPI cannot guarantee that the ID is not being used in a cluster that is currently powered off. The best practice is to maintain a register of the cluster IDs used across the data center to avoid use of duplicate IDs. In the example configuration, no other clusters with that ID have been found.

6. At this point a summary of the configuration to be deployed is presented. Examine the summary and enter y if everything is correct. If not enter n and go through the steps again.

7. The installer prompts for a Virtual IP to manage the cluster. This is not mandatory, and the cluster can be configured without that IP. Depending on your implementation, it might be a best practice.

8. Decide whether or not to use secure mode.

   In the past, the difficulty in configuring Cluster Server secure mode deterred many users from using it. For SFCFSHA:

   • Secure mode configuration is much easier

   • The installer takes care of the entire configuration

   • A validated user and password from the OS is used instead of the traditional admin/password login

   For demonstration purposes, secure mode is used in the example deployment, but feel free to choose the option that best suits your needs.

   FIPS is not used for the example configuration as it is not certified for deployment with CP servers. Option 1, secure mode without FIPS is used.

9. SMTP is not needed for the example.
10. SNMP notifications are not needed for the example.

    At this point the cluster configuration will be initiated.