Veritas Resiliency Platform 3.0

After Veritas Resiliency Platform (Resiliency Platform) deployment, when you log into the virtual appliance console for the first time using the admin user credentials, the bootstrap process is automatically invoked. This bootstrap process is used to set up or configure the Resiliency Platform component for the first time.

The default network protocol for virtual appliance is Dynamic Host Configuration Protocol (DHCP). If the appliance detects DHCP during the first boot or before the completion of bootstrap process, the appliance network automatically gets configured. After the network configuration, you can either use the virtual appliance console or Secure Shell (SSH) to log in as admin user and complete the bootstrap process.

If DHCP is not configured in your environment, you have an option to use a static IP for the appliance. Since the appliance network is not automatically configured in this case, you can only use the console to log into the virtual appliance.

To configure the Resiliency Manager or IMS

    • 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.

  1. Accept the End User License agreement (EULA) to proceed with the configuration.

    If the bootstrap is in AWS environment, you are prompted to set a password for the admin user in the Admin Password Settings after accepting EULA.

    See Password policies for Resiliency Platform virtual appliance

    You need to use this password for subsequent logins to the console.

  2. In the Host Network Settings section, you can configure the appliance network by using DHCP or static IP.

    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 address:

    • Enter the Subnet mask:

    • Enter the Default Gateway:

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

  3. Confirm if you are in Network Address Translation (NAT) environment and want to verify the NAT configuration using an external IP and hostname. You need to respond to the following additional prompts:

    • Enter the fully qualified external hostname:

    • Enter the external IP address:

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

    For recovery to AWS, if the VPN is configured between the sites using the private network, then NAT option will not be applicable.

  4. 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.

  5. In the Product Settings section, the virtual appliance is configured as Resiliency Manager or IMS.

  6. After a successful product configuration, a message is displayed. If you have configured Resiliency Manager on the virtual appliance, a URL for the Resiliency Platform web console login is provided. You can type the URL in a web browser and log in to the web console.

Veritas Resiliency Platform 3.0

After Veritas Resiliency Platform (Resiliency Platform) deployment, when you log into the virtual appliance console for the first time using the admin user credentials, the bootstrap process is automatically invoked. This bootstrap process is used to set up or configure the Resiliency Platform component for the first time.

The default network protocol for virtual appliance is Dynamic Host Configuration Protocol (DHCP). If the appliance detects DHCP during the first boot or before the completion of bootstrap process, the appliance network automatically gets configured. After the network configuration, you can either use the virtual appliance console or Secure Shell (SSH) to log in as admin user and complete the bootstrap process.

If DHCP is not configured in your environment, you have an option to use a static IP for the appliance. Since the appliance network is not automatically configured in this case, you can only use the console to log into the virtual appliance.

To configure the Resiliency Manager or IMS

    • 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.

  1. Accept the End User License agreement (EULA) to proceed with the configuration.

    If the bootstrap is in AWS environment, you are prompted to set a password for the admin user in the Admin Password Settings after accepting EULA.

    See Password policies for Resiliency Platform virtual appliance

    You need to use this password for subsequent logins to the console.

  2. In the Host Network Settings section, you can configure the appliance network by using DHCP or static IP.

    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 address:

    • Enter the Subnet mask:

    • Enter the Default Gateway:

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

  3. Confirm if you are in Network Address Translation (NAT) environment and want to verify the NAT configuration using an external IP and hostname. You need to respond to the following additional prompts:

    • Enter the fully qualified external hostname:

    • Enter the external IP address:

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

    For recovery to AWS, if the VPN is configured between the sites using the private network, then NAT option will not be applicable.

  4. 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.

  5. In the Product Settings section, the virtual appliance is configured as Resiliency Manager or IMS.

  6. After a successful product configuration, a message is displayed. If you have configured Resiliency Manager on the virtual appliance, a URL for the Resiliency Platform web console login is provided. You can type the URL in a web browser and log in to the web console.