If you enabled encryption in the previous section, have your security administrator present for this procedure. The security administrator should be the only person to see the encryption key.
- From the New Install Menu, enter x. If you run the installation as the install user, the wizard informs you that data-in-flight encryption is enabled.
The wizard asks for confirmation that it is legal to ship a system with data-in-flight encryption enabled to the country where the system is to be deployed.
Confirm Data in Flight Encryption / SSL ============================================= Data-in-flight encryption has been enabled for this HCP system. Global trade compliance prohibits shipping HCP systems to restricted countries with this feature enabled. Are you sure it is legal to ship an HCP system with data-in- flight encryption enabled to the country where the system will be deployed? Note: Control-C cancels input. Enter yes or no. [Default: no]: yes You chose: “yes”, is this correct? [Default: yes]:
- Enter yes to continue.
- Press Enter to confirm.
The wizard displays the configuration confirmation.
Configuration confirmation. ============================================= DNS Server (s) = 172.18.4.46 Allow Data at Rest Encryption = No Customer Support Contact Information = United States: (800) 446-0744. Outside the United states: (858) 547-4526 Multicast Network = 238.177.1.1 Storage configuration = internal Time Zone = America/New_York Gateway Router IPv4 Address = 172.20.59.254 Current Date and Time = None Domain Name for the System = hcp.example.com Encrypt Data at Rest on Primary Storage = No Reinstallation with DNS Failover in Effect = No Allow Data in Flight Encryption / SSL = Yes Time Settings Compliance Mode = No HCP System Serial Number = 00001 Blade Servers = No Distributor/OEM Key Access = Arizona MOE Index-only volumes = No Time Server(s) = internal Gateway Router Secondary IPv6 Address = None Gateway Router IPv6 Address = None Enable DNS = Yes Chassis = None Enable Replication on This System = Yes Configure Dedicated Database Volumes = Yes Spindown Volumes = No HCP Storage Nodes: 4 172.59.42.1 172.59.42.2 172.59.42.3 172.59.42.4 Use SHIFT+PGUP to review the Configuration. IS this Configuration Correct? (Default: no): yes You chose: “yes”, is this correct? (Default: yes]:
- Review the configuration. Then complete one of the following actions:
- If the configuration is not correct:
- Enter n or no.
- In response to the confirmation prompt, enter y or yes.
- Correct the configuration information.
- If the configuration is correct:
- a. Enter y or yes.
- In response to the confirmation prompt, enter y or yes.
- If the configuration is not correct:
- After you confirm that the configuration information is correct, HCP Setup performs a set of installation prechecks.
You chose "yes”, is this correct? [Default: yes]: Verifying system name Verifying run location Verifying running as install Verifying node connections Verifying SSH keys Verifying SSH Verifying systemwide SSH Verifying total memory > 32GB Verifying all network links Verifying software versions Verifying 64-bit hardware platform Verifying drive size Verifying disk space Verifying nobody using /fcfs_* Verifying nobody using /fs/* Verifying multicast enabled Syncing install password to all nodes. Updating EULA Syncing timezone to all nodes Syncing date to all nodes. Generating auth keys Generating system UUID Syncing HCP package to all nodes Checking to see if we need to run update schemaupgrade scripts False Updating schema scripts for upgrade.
- (Optional) If you previously selected that you want to configure dedicated database volumes, complete the following substeps:
- When prompted, select the dedicated database volume for the first node.
- Press Enter to confirm your selection.
- Repeat the Substeps a and b for each node in the system.
- After you select the dedicated database volumes for each node, HCP Setup confirms your selections and asks if you want to continue.
Select dedicated volume for each node. Found these volumes: node 001: 1. /dev/sdd at 2:0:0:1 (500GB) 2. /dev/sde at 2:0:0:2 (500GB) 3. /dev/sdd at 2:0:0:3 (500GB) 4. /dev/sde at 2:0:0:4 (1TB) node 002: 1. /dev/sdd at 2:0:0:1 (500GB) 2. /dev/sde at 2:0:0:2 (500GB) 3. /dev/sdd at 2:0:0:3 (500GB) 4. /dev/sde at 2:0:0:4 (1TB) node 003: 1. /dev/sdd at 2:0:0:1 (500GB) 2. /dev/sde at 2:0:0:2 (500GB) 3. /dev/sdd at 2:0:0:3 (500GB) 4. /dev/sde at 2:0:0:4 (1TB) node 004: 1. /dev/sdd at 2:0:0:1 (500GB) 2. /dev/sde at 2:0:0:2 (500GB) 3. /dev/sdd at 2:0:0:3 (500GB) 4. /dev/sde at 2:0:0:4 (1TB) Select dedicated database volume for node 001: 4 You chose: “4. /dev/sde at 2:0:0:4 (1TB)”, is this correct? [Default: yes]: Select dedicated database volume for node 002: 4 You chose: “4. /dev/sde at 2:0:0:4 (1TB)”, is this correct? [Default: yes]: Select dedicated database volume for node 003: 4 You chose: “4. /dev/sde at 2:0:0:4 (1TB)”, is this correct? [Default: yes]: Select dedicated database volume for node 004: 4 You chose: “4. /dev/sde at 2:0:0:4 (1TB)”, is this correct? [Default: yes]: Following volumes will be configured as dedicated database volumes: node 001: 4. /dev/sde at 2:0:0:4 (1TB) node 002: 4. /dev/sde at 2:0:0:4 (1TB) node 003: 4. /dev/sde at 2:0:0:4 (1TB) node 004: 4. /dev/sde at 2:0:0:4 (1TB) Do you want to continue? [Default: yes]?
- Press Enter to continue.
If the prechecks are successful, the HCP software is installed on all nodes in the system.Depending on the size of the logical volumes, this can take from several minutes to several hours.If you enabled encryption in the system configuration, HCP Setup performs some initial setup tasks and then displays the encryption key.Setup then prompts you to enter the key.Important: Before entering the encryption key, record it. After you enter the key, HCP Setup completes the installation. You do not get a second chance to see the key, and it is not stored for later retrieval.When the installation is complete, HCP Setup logs you out and restarts the nodes.The console then displays the login prompt.If HCP Setup exits before installation processing is complete, record all error messages. Then contact your authorized HCP service provider for assistance.After the installation is complete, the HCP VM nodes restart, and, instead of the operating system login prompt, you should see an hcp-node- nodeNumber prompt.You can also verify the run level of a node by pressing Alt+F5 at the console prompt.
Every 30.0s: /sbin/system-info Fri May 15 12:29:58 2020 Host Name: hcp-node-150.cluster-colo-089-vol.lalo.arehivas.com IS Mode: 150 [hcp_system] IP: 172.21.159.158 [hcp_system] Mask: 255.255.255.0 [hcp_system] Gateway: 172.20.27.254 [hcp_backend] IP: 172.21.159.150 [hcpbackend] Mask: 255.255.255.0 Version: 6.0.0.93 Operating System: OS 6.0.0.514 Linux Kernel: 3.1.5-5.x06_64 Current Run Level: 4 12:29:58 up 22:47, 0 users, load average: 0.00, 0.01, 0.06