Deploy Super-NetOps host

Launch new EC2 resource.

  1. In the AWS Management Console, navigate to EC2 and click Launch Instance.

  2. Select Amazon Linux AMI 2018.03.0 (HVM), SSD Volume Type - ami-cfe4b2b0.

    ../../_images/image410.png

  3. For Instance Size* select t2.micro then click Next: Configure Instance Details

  4. For the Network select your Student#-VPC-CFT

  5. For the Subnet select your Student#-VPC-CFT-MgmtSubnet

  6. For Auto-assign Public IP select Enable

  7. Expand Advanced Details on bottom of page and paste the following code into User Data box.

    #!/bin/bash
yum update -y
yum install -y docker
yum install -y telnet
yum install -y curl
yum install -y ab
/sbin/chkconfig --add docker
service docker start
    Copy to clipboard

  8. Click Next: Add Storage

  9. Click Next: Add Tags

  10. Click Next: Configure Security Group

  11. Select Existing Security and find your Student#-VPC-CFT-bigipManagement

  12. Click Review and Launch

  13. Click Launch

  14. For SSH Key utilize the Student#-BIG-IP key

  15. Check the I acknowledge that AWS CloudFormation might create IAM resources box and click Launch Instances.

Launch F5 Super-NetOps docker instance

  1. View Instances and filter for your Student# to see your unamed instance.
  2. Connect to Super-NetOps host using ssh utility. For example; ssh -i “Student#-BIG-IP.pem” ec2-user@<Super-NetOps_IP>
  3. Type sudo docker run -it f5usecases/f5-rs-container:latest
  4. Type git clone https://github.com/gotspam/as3-examples.git
  5. Type cd as3-examples

Modify ansible files for your environment

  1. Type vim inventory/hosts and change ipaddress to your BIG-IP Private IP Address (eth0). This is the BIG-IP Management IP and is typically the first Private IP listed or by clicking on eth0.

    ../../_images/image415.png

  2. Type vim roles/hackazon/files/hackazon.json and change ipaddress to your BIG-IP Private IP Address of the Elastic IP found in Lab2.

    ../../_images/image416.png

Test Super-NetOps communication with BIG-IP

You will now need to setup security permissions on AWS EC2 console so that Super-NetOps can communicate with your BIG-IP.

  1. In the AWS EC2 console go to Network Interfaces and Filter by your Student#.

  2. Select the Interface with the description labeled Primary network interface.

  3. In the bottom area look for the**Primary private IPv4 IP:**

  4. Now select Security Groups on the left hand side.

  5. Filter by your Student# and then select the BIG-IP Management instance.

  6. Click the Inbound tab at the bottom and then select Edit.

  7. Click on Add Rule.

  8. Select SSH and then put the IP you found earlier in the source with a /32.

  9. Click on Add Rule again.

  10. Select HTTPS and then put the IP you found earlier in the source with a /32.

  11. Click on Save.

  12. Go back to your SSH session on the Super-NetOps host.

  13. Ensure your Super-NetOps host can communicate with your BIG-IP Management instance.

    • Type ssh admin@<BIG-IP Private IP Address (eth0)>.
    • After successfully logging in, type quit to disconnect ssh session.
    • Type ansible-playbook playbooks/cmd.yaml.
    • Enter BIG-IP Username and Password when prompted.
    ../../_images/image417.png