Product Documentation

To configure a YUM repository server

1. • Prerequisites:

     See Prerequisites for configuring Resiliency Platform components.

   • In any non-AWS environment, log in to the virtual appliance console or SSH using the following credentials:

     • Username: admin

     • Password: P@ssw0rd

     After a successful login, you are prompted to change the password of the admin user.

     See Password policies for Resiliency Platform virtual appliance.

     If you are logged in to SSH, you will be logged off the SSH session after the password change and you need to again log in to complete the rest of the steps of the bootstrap process. If you are logged in to the virtual appliance console, you can continue and complete the rest of the steps of the bootstrap process.

   • In AWS environment, do one of the following:

     • For Linux system:

       Use SSH with the private key from the key-pair that you had selected while launching the instance in AWS. For example:

       ssh -i private_key_file admin@ip_address_of_aws_instance

       Ensure to modify the permissions for the private key file as 600 before using the file.

     • For Windows system:

     Follow the documentation of AWS to connect to the Linux instance from a Windows system using PuTTY.

2. Accept the End User License agreement (EULA) to proceed with the configuration.
3. In the Host Network Settings section, you can configure the appliance network by using DHCP or static IP address (v4 or v6).

   If the DHCP configuration is working in the environment, the details are printed on the screen. Confirm if you want to proceed with these settings.

   In case of DHCP, you need to ensure that a Dynamic Host Configuration Protocol (DHCP) server is working in the subnet where the virtual appliance is deployed. In case of static IP, you need to respond to the following additional prompts:

   • Enter the fully qualified hostname:

   • Enter the IP (v4 or v6) address:

   • Enter the prefix length as an integer between 1 and 32:

   • Enter the Gateway:

   • Do you want to add static route for interface? (y/n): [n]

   • Enter the DNS server (space separated if more than one DNS, maximum 2 DNS entries):

4. Confirm if you are in Network Address Translation (NAT) environment and want to verify the NAT configuration using an external IP and hostname.

   Note:

   Since NAT is not supported for IPv6 address, hence when you configure the virtual appliance using IPv6 address only and both IPv4 and IPv6 address, you are not asked about the NAT configuration. To know more about NAT support in Resiliency Platform

   See About NAT support in Veritas Resiliency Platform. See About IPv6 network support in Resiliency Platform.

   You need to respond to the following additional prompts:

   • Enter the fully qualified external hostname:

   • Enter the external IP address:

   Note:

   The external hostname or IP that you provide are set as the appliance hostname or IP.

5. In the Appliance Settings section, do the following:

   • Press the Enter key to confirm the use of an NTP server for configuring the date and time.

   • You are required to select the time zone. Follow the instructions as displayed on the virtual appliance console or SSH session to select the correct time zone.

   • Enter the FQDN or IP address of the NTP server. The appliance verifies the NTP server details. If there are any issues, details are displayed on the screen and you are prompted to enter the details again.

   You can reset the timezone and NTP server at a later point of time using klish menu. Changing the system settings can affect the product functionality if incorrect values are set.

6. Product Settings: This section configures the appliance as a repository server.
7. After a successful product configuration, a confirmation message will be displayed and you will be logged out of the virtual appliance console.
8. If the bootstrap is in AWS environment, you must log in once again using the SSH key and set the admin user password. You need to use this password for subsequent logins to the console.