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

ReynaldoQ_14206's avatar
ReynaldoQ_14206
Icon for Nimbostratus rankNimbostratus
Jun 05, 2014

virtual server setup

I have setup two virtual servers on a internal F5 load balancer. Same ip but one is http port 80 and another http port 8085.

 

when i enter virtual server ip on a browser browser can not locate it but if I do "telnet 80 or 8085 I get connected.

 

when i enter the real server ip on the browser I get the IIS page which it should be.

 

Any idea what I did wrong or other setup required?

 

Thanks for any ideas.

 

6 Replies

  • How are you associating the pool to the Virtual Server (iRule or default pool)?

     

  • What is the topology? Is the pool member/s on a isolated subnet behind the LTM? Could there be asymmetric routing, that is being blocked by a firewall?

     

  • can you post the virtual server and pool configuration?

     tmsh list ltm virtual (name)
     tmsh list ltm pool (name)
    
  • [root@bip-bxb-internal2:Standby] config tmsh list ltm virtual vs_sbmorchestration_80 ltm virtual vs_sbmorchestration_80 { destination 172.24.157.73:http ip-protocol tcp mask 255.255.255.255 persist { source_addr { default yes } } pool pl_sbmorchestration_80 profiles { http { } tcp { } } } [root@bip-bxb-internal2:Standby] config tmsh list ltm virtual vs_sbmorchestration_8085 ltm virtual vs_sbmorchestration_8085 { destination 172.24.157.73:8085 ip-protocol tcp mask 255.255.255.255 persist { source_addr { default yes } } pool pl_sbmorchestration_8085 profiles { tcp { } } } [root@bip-bxb-internal2:Standby] config tmsh list ltm pool pl_sbmorchestration_80 ltm pool pl_sbmorchestration_80 { members { 172.22.240.23:http { session monitor-enabled } 172.24.1.27:http { session monitor-enabled } } monitor http } [root@bip-bxb-internal2:Standby] config tmsh list ltm pool pl_sbmorchestration_8085 ltm pool pl_sbmorchestration_8085 { members { 172.22.240.23:8085 { session monitor-enabled } 172.24.1.27:8085 { session monitor-enabled } } monitor http_8085 }

     

  • does bigip have route to pool members (172.22.240.23 and 172.24.1.27)?

     

    is the pool members' default gateway bigip? if not, can you try snat automap setting under virtual server configuration?

     

    by the way, why telnet gets connected is how full proxy architecture works.

     

    sol8082: Overview of TCP connection setup for BIG-IP LTM virtual server types

     

    http://support.f5.com/kb/en-us/solutions/public/8000/000/sol8082.html