Forum Discussion

consult_001_174's avatar
consult_001_174
Icon for Nimbostratus rankNimbostratus
Oct 23, 2014

Virtual Servers (LTM on EC2)

Hello,

 

I have installed the F5 AMI on EC2. Let's assume its IP is

 

1.0.0.1

 

I have provisioned three more machines running Apache each of which serves up a simple web page on port 80. Assume these servers' IPs are...

 

1.0.0.2 1.0.0.3 1.0.0.4

 

I have created a Pool with these Apache servers as members and have associated this Pool with a Virtual Server. Within the Virtual Server section, I have set the Destination Type to 'Host' and the Destination Address to the same address as the F5 instance (i.e. 1.0.0.1). I have set the Service Port to 80.

 

When I try to browse 1.0.0.1:80, I get page not found instead of the request being 'load balanced' to one of the Apache servers. Why is this?

 

I realize that, on 1.0.0.1, the admin console runs on port 443 but 80 should be free, right?

 

I also know that my pool is set up correctly, because the health monitoring I've set up in it is reporting the status of each of the three Apache servers correctly.

 

My EC2 security group for the F5 and Apache servers is correct.

 

I can browse each of the Apache server web pages if I access that IP directly.

 

Any ideas?

 

Thanks,

 

Matthew

 

APM
application delivery
AWS
cloud
LTM
management
security

2 Replies

Sort By
  • THi's avatar
    THi
    Icon for Nimbostratus rankNimbostratus
    Oct 23, 2014

    Seems to be one legged configuration, i.e. virtual server and pool members (nodes) are in the same subnet.

     

    Might be a routing problem for the return packets from the servers. If you monitor the packets to the server do you see any traffic going to the servers and anything coming back? You can check with GUI: Statistics ›› Module Statistics : Local Traffic ›› Virtual Servers or Nodes: Bits/Packets In /Out. If you see something going in but 0 out, then the return packets may bypass the BIG-IP and connection cannot be made.

     

    Do the servers have a route back to the client via the BIG-IP? Where is the servers' default gateway pointing? If not to the BIG-IP self IP (1.0.0.1), do you have any SNAT, like SNAT Automap for the virtual defined? SNAT Automap will rewrite client address to be the BIG-IP's address for the server bound packets. Thus the servers think they are communicating with the BIG-IP on packet level, and will send the return packets back to the BIG-IP, which will pass them back to the client.

     

  • What_Lies_Bene1's avatar
    What_Lies_Bene1
    Icon for Cirrostratus rankCirrostratus
    Oct 27, 2014

    Can you describe the IP and VLAN setup of your instance please? How many interfaces and IPs do you have configured?