For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

laudo_359006's avatar
laudo_359006
Icon for Nimbostratus rankNimbostratus
Apr 18, 2018

Create second VIP for new application / not able to get to application

I have a F5 virtual appliance in AWS. Single nic. IT has a public IP and I am able to get to it using .   I create a VIP(10.0.1.44:443)-> Pool1 -> (node1,node2,node3(8080)) and am able to get to ...
BIG-IP
cloud
devops
Chase_Abbott's avatar
Chase_Abbott
Icon for Admin rankAdmin
Apr 18, 2018

Without knowing more about the static config of BIG-IP, 8443 is used for BIG-IP management access (versions after 12.1). Public IP does not equal elastic IP so if we are just using the public DNS using NAT gateways, then you may be using the self IP for the applicaiton access. If we are talking about different IP's from what BIG-IP is using for it's self IP then I suspect traffic isn't making it to the BIG-IP interface.

 

If you look at the VIP statistics tab, you'll see if any traffic is hitting that address. I suspect there may be some security group requirements that still need to be setup for 8443 from the elastic IP (you're using elastic for the public access correct?).

 

Can you provide some more details around the IP configurations within BIG-IP and how the security groups are configured around the incoming traffic through the elastic IP that translates to your BIG-IP?