To configure the Veritas Access cluster on the appliance

1. Log on to the Access Appliance shell menu of one of the appliance nodes.
2. From the Main_Menu > Manage > Cluster view, type the following command to start the cluster configuration wizard:

   Configure

3. Type yes to continue.
4. Enter a name for the cluster.

   Cluster names should be DNS-compatible. DNS-compliant cluster names should conform to the following naming conventions:

   • Must be at least three and no more than 63 characters long.

   • Allowed characters in a cluster name are lowercase letters, numbers, and hyphens 'a-z, 0-9, -'. Any other character is invalid.

   • Must start with a lowercase letter and must not start with a hyphen ('-') or number.

   • Must end with a lowercase letter or a number.

   • Should not be an IP address.

5. Enter the eth1 IP addresses for each node, separated by a space.
6. Enter the Maintenance user password for appliance nodes.
7. Specify whether you want to configure network bonding for the public network interfaces eth4 and eth5. To configure network bonding, type yes and continue to step Step 8; else type no and go to step Step 9.

   Note:

   Network bonding can be configured only when you configure the cluster.

8. If you typed yes in step Step 7, complete the following steps and go to step Step 12.

   • Specify the mode for the network bonding.

   • If you select mode 3 (balance-xor) or 5 (802.3ad), specify the transmit hash policy to use.

   • Enter the starting IP address from the range of public IP addresses that you have reserved. At a minimum, you need to reserve two continuous public IP addresses.

   • Enter the starting virtual IP address from the range of virtual IP addresses that you have reserved. At a minimum, you need to reserve two continuous virtual IP addresses.

   See About obtaining IP addresses for Veritas Access.

9. Enter the starting public IP address or four individual public IP addresses for the data network. You can specify IPv4 or IPv6 addresses. The addresses need not be contiguous. An IPv4 range is supported.

   For example, if you type 10.182.12.89, the appliance will use 10.182.12.89-92 for public IP addresses.

   See About obtaining IP addresses for Veritas Access.

10. Enter the number of virtual IP addresses to assign to each network interface in the data network.
11. Enter the starting virtual IP address or individual virtual IP addresses separated by a space or a comma. You can specify IPv4 or IPv6 addresses. The addresses need not be contiguous. An IPv4 range is supported.
12. Enter the netmask for the data network IP addresses.
13. Enter the data network IP address.
14. Enter the console virtual IP address.
15. Specify whether you want to configure a DNS server.

    If you opted to configure a DNS server, enter the DNS server IP address.

    Note:

    This is an optional step, and only required if the DNS server was not configured earlier, or you had configured the appliance node host name, or you want to change the previous DNS configuration. Ensure that the configured DNS server can resolve the eth1 IP address to a valid node host name as this is required for AutoSupport CallHome to work correctly.

16. Enter the DNS server domain name
17. Specify whether you want to configure the NTP server. You can choose to configure the NTP server after the cluster is configured.
18. Enter the starting private IP address.

    The private network can be any IPv4 address that does not conflict with the provided management or data network ranges.

    Note:

    The base network IP address is calculated by using the netmask that is specified for the private network, and the IP addresses are assigned starting from this base IP address. The first IP address is reserved for the NLM (Network Lock Manager) service and successive IP addresses are assigned to the network interfaces.

19. Enter the netmask for the private IP address.

    The netmask is used to customize the private IP range. The netmask must be 255.252.0.0 or greater.

20. Review the configuration summary and type yes to continue and begin the configuration.

    If you have configured network bonding, bond0 is created for the public network and the message Public network connection provided by bond0 with subordinate network interfaces is displayed.

    The configuration process can take around 40 minutes to complete. During the configuration, disk-based fencing is configured. You cannot change the fencing configuration.

    The URL to access the Access web interface is displayed during the configuration.

21. Change the known default password of the admin, maintenance, master, and IPMI (if the sysadmin account uses the default password) user accounts.

    Veritas enforces changing the known default passwords during the initial configuration to ensure that the default passwords do not remain active on the node.

    Ensure that the following password requirements are met:

    • The password cannot reverse the entire user name.

    • The password must contain at least eight characters.

    • The password must contain at least one numeric character (0-9).

    • The password must contain at least one lowercase character (a-z).

    • The password must contain at least one uppercase character (A-Z).

    • The password must contain at least one special character (~!@#$%^&).

    Note:

    The Maintenance user password must be the same on each node. If the password expires, log in to the Access web interface with the maintenance account to change the password.

22. After the cluster is configured, you are prompted to reboot the cluster to bring up the Access services. Type yes.

    Note:

    If you choose to reboot the cluster later, you can access the cluster but all the functionality might not be supported till all the services are up.