3.4.1. Check status of F5 instances before proceeding.

From the AWS Web Console => Services => EC2 => INSTANCES => Instances. Select the Big-IP1… Select the “Status Check” tab below.

../../_images/1_aws_console_ec2_bigip_status_check.png

From the AWS Web Console => Services => EC2 => INSTANCES => Instances. Select the Big-IP2… Select the “Status Check” tab below.

../../_images/2_aws_console_ec2_bigip_status_check2.png

Attention

Ensure both the System Status Checks and the Instance Status Checks have passed (green font) before proceeding.

3.4.2. Create terraform data resource to read CloudFormation outputs.

From the Visual Studio Code Terminal, enable the f5-cft-outputs.tf terraform file.

mv f5-cft-outputs.tf.zzz f5-cft-outputs.tf
../../_images/3_vscode_mv_f5_cft_outputs_zzz_to_tf.png

terraform init

terraform init

terraform validate

terraform validate
../../_images/5_vscode_terraform_validate.png

terraform plan

terraform plan -var 'bigip_admin_password=f5letme1n'
../../_images/6_vscode_terraform_plan.png

terraform apply

terraform apply -var 'bigip_admin_password=f5letme1n' -auto-approve
../../_images/7_vscode_terraform_apply.png

terraform apply completed.

../../_images/8_vscode_terraform_apply_complete.png

3.4.3. SSH to Big-IP1 and Big-IP2

Run the create-ssh-to-bigip-alias.sh shell script to create convenient command aliases for bigip1 and bigip2.

source create-ssh-to-bigip-alias.sh
../../_images/9_create_ssh_to_bigip_alias.png

Confirm the bigip1 and bigip2 aliases were created.

type bigip1
type bigip2
../../_images/10_type_bigip_alias.png

SSH to Big-IP1 to confirm state and change the admin password.

Attention

Ensure the system status prompt is either Active or Standby before proceeding. All other status prompts indicate the system is not ready. Use the screenshots as a guide.

bigip1
modify auth user admin password f5letme1n
modify /sys global-settings gui-setup disabled
save /sys config
quit

Acknowledge the ssh remote host when prompted “Are you sure you want to continue connecting (yes/no)?” yes

../../_images/11_bigip1_confirm_state.png ../../_images/12_bigip1_modify_auth.png

SSH to Big-IP2 to confirm state and change the admin password.

Attention

Ensure the system status is either Active or Standby before proceeding. All other status prompts indicate the system is not ready. Use the screenshots as a guide.

bigip2
modify auth user admin password f5letme1n
modify /sys global-settings gui-setup disabled
save /sys config
quit

Acknowledge the ssh remote host when prompted “Are you sure you want to continue connecting (yes/no)?” yes

../../_images/13_bigip2_modify_auth.png

3.4.4. Configuration Utility (WebUI) HTTPS access to Big-IP1 and Big-IP2

We need the management address to connect to the Configuration utility (WebUI). Invoke terraform output and look for:

Bigip1Url

Bigip2Url

terraform output
../../_images/14_terraform_output_cft.png

From the Visual Studio Code Terminal, Ctrl + click to follow link for “BigIP1Url” =

../../_images/16_bigip1_url.png

We are using self-signed certificates in the lab. Bypass the TLS warnings. “Accept the Risk and Continue”.

../../_images/17_bigip1_bypass_tls_warning.png

Login to the Big-IP1 Configuration Utility (WebUI):

Username: admin

Password: f5letme1n

../../_images/18_bigip1_login.png

Look in the upper-left-hand corner. Note whether this is the active or standby unit.

../../_images/18a_bigip1_login_active.png

From the Visual Studio Code Terminal, Ctrl + click to follow link for “BigIP2Url” =

../../_images/19_bigip2_url.png

We are using self-signed certificates in the lab. Bypass the TLS warnings. “Accept the Risk and Continue”.

../../_images/20_bigip2_bypass_tls_warning.png

Login to the Big-IP2 Configuration Utility (WebUI):

Username: admin

Password: f5letme1n

../../_images/21_bigip2_login.png

Look in the upper-left-hand corner. Note whether this is the active or standby unit.

../../_images/21a_bigip2_login_active.png