Forum Discussion

Geoff_Littlewoo's avatar
Geoff_Littlewoo
Icon for Nimbostratus rankNimbostratus
Oct 20, 2014

Deploying BIG-IP Virtual Edition in AWS - trouble with traffic not routing

Just installed 11.5.1 on AWS. I have confugured it as follows :- Mgmt Interface 10.25.12.120 Interface External 10.25.8.50

 

I have then created a node, pool, and VIP (10.25.8.100) then assigend it to eth1:0 from within the AWS portal (interface to an EIP (elastic IP address). I can ping 10.25.8.50 and 10.25.8.100 from the manamenet interface (putty login to console/mgmt interface). The health monitor on nide, pool and VIP are green. I have tested a web site is up onthe back end node but, when I connect to the EIP address from external via a brower or vial telnet I get nothing going through. I can confirmed with Amazon that all seem to be configured properly, including security groups on the interface. So my question is, am I missing something on the configuartion ? traffic from 10.25.8.100 does not seem to be routing through 10.25.8.50. Is there a step I have missed ? Appreciate any help I followed the install guide :- https://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/bigip-ve-setup-amazon-ec2-11-5-0/2.htmlunique_2105128447

 

eth0 --- private IP = 10.25.12.120 --- public IP = 54.172.17.11 eth1 --- private IP = 10.25.8.50 --- public IP = [none] eth1:0 --- private IP = 10.25.8.100 --- public IP = xxx.xxx.xxx.xxx

 

application delivery
deployment
LTM

1 Reply

Sort By
  • Geoff_Littlewoo's avatar
    Geoff_Littlewoo
    Icon for Nimbostratus rankNimbostratus
    Oct 20, 2014

    It seems after reading https://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/bigip-ve-setup-amazon-ec2-11-4-0.pdf i may need to add routing to my interface on eth1 . I only have added a single interface and asigned it to 1.1 (external) but no interface for Internal. Do I need to have this configured ? When I created a new VIP and assigned 10.25.8.100 to the VIP I was able to asign the EIP to this VIP address in interface association on the AWS console. Assuming it is a routing issue for the interface 1.1 (external) how does or why do I need a third interface for 1.2 ? Do I associate the node on this interface 1.2 and thr BIG-IP will deal with routing ?