Virtual Server creation

The BigIP acts as a proxy. So you can debug it at both the bigip/client and bigip/server side to see whats happening.

 

If you tcpdump both sides, what do you see? Does the connection between client and bigip succeed? Do you see the request come from the client? (I usually test using telnet for this point as browsers just get in the way at this level).

 

If that all looks OK, what do you see at the server side? Does BigIP open a connection to the server? Is the request passed through?

 

Are you seeing any errors in /var/log/ltm? Perhaps your client is using HTTP methods not supported by the HTTP profile?

 

• This all assumes of course that your pool and poolmembers are marked as available by your pool monitor already...

H

 

Hi Hamish,

 

Thanks for the answer. Being new user of F5, I could not get lots of things which you asked. Can you please let me know how I can do tcpdump in both sides ?

 

I used telnet command to see whether I am able to connect virtual server IP with port, but I could not succeed. And that the reason I am thinking that Virtual server which I created is not accessible at all.

 

-Sandeep

 

it is up to you, but perhaps you should start with something simpler then.

one virtual server (standard) listening on port 80 (HTTP), one pool with one member also on port 80. not special profiles, just the basic and go from there.

then see if you can browse to the virtual server and get the website of the pool member to show up.

for tcpdump on both sides you can use the interface 0.0, so:

tcpdump -i 0.0 -nn

if that causes to much traffic you could use it with a filter, but then you need to use both the virtual server ip and the nodes.

tcpdump -i 0.0 -nn host  or host  or host 

Hi,

 

As I said earlier that my virtual server is not responding at all because when I use telnet command with virtual server ip and port its refusing the connection saying no route to host.

 

Let me tell all the things which I done till now. * Download F5 Big-IP LTM VE trial version * Running F5 via VMPlayer (VMPlayer is installed on my machine). * In console window of F5, I used command "config" and then set the IP address of f5. * Now I can access admin console from Browser. * After admin/admin credential, I created pool / members etc.. * Now last thing remaining is to create new virtual server. * As a lemon person: in Destination side I selected Type as Host and gave new random IP (111.111.111.100) with Service port as 80:HTTP * Everything looks good and I can see Green signal in Availability side

 

Now I back to my VMPlayer console and try to use telnet command to access new virtual server IP (111.111.111.100) with port.

 

Browser side. I tried to use http://111.111.111.100:80

 

As I am not a sysadmin person but I want to try F5 for evaluation purpose. And I am pretty much sure that creation of virtual server has some problem.

 

If we create virtual server with random IP (111.111.111.100), What all other things need to be consider ? I thought that I can give any random number because one of the f5 LAB video, I observed this.

 

-Sandeep

 

you have to consider being able to reach the F5 on the virtual server IP and the F5 being able to reach the pool members. i'm not sure how VMPlayer handles this, the LTM VE will probably choose interfaces it connects with for an external and internal network and management, but how exactly i don't know.

 

did you follow any documentation for setting it up you can share?

 

see below linked which I followed.

 

http://www.youtube.com/watch?v=_tEzfsoMxJ4

 

http://www.dasblinkenlichten.com/f5-ltm-ve-setting-up-basic-load-balancing/

 

http://www.f5.com/pdf/deployment-guides/tomcat-dg.pdf

 

-Sandeep

 

For installation of LTM VE on VMPlayer, I used this link http://www.youtube.com/watch?v=1gyiQOYeS0A

 

-Sandeep

 

In console window of F5, I tried to use command : tmsh list ltm virtual ltm virtual CCE-Tomcat_virtual_server { destination 172.29.0.44:http ip-protocol tcp mask 255.255.255.255 persist { CCE-Tomcat_persist_profile { default yes } } pool CCE-Tomcat_pool profiles { CCE-Tomcat_lan-optimized_tcp_profile { } CCE-Tomcat_one_connect_profile { } bea_weblogic_http-lan-optimized-caching_shared_http { } } snat automap translate-address disabled }

 

Is there any way to change the netmask ?

 

In general I am using netmask 255.255.254.0

 

I tried to create virtual server with Network option but got the error:

 

01070348:3: Virtual Server CCE-Tomcat_virtual_server destination 172.29.0.44 and netmask 255.255.254.0 are not valid.

 

Would appreciate any help to configure Virtual server ?

 

-Sandeep

 

Is there any way to change the netmask ? In general I am using netmask 255.255.254.0

you can use modify ltm virtual command. please make sure translate-address is enabled (i.e. it will translate destination ip to pool member ip). also, you may have to enable arp on network virtual address.

e.g.

root@ve10(Active)(tmos) list ltm virtual bar
ltm virtual bar {
    destination 172.28.19.252:http
    ip-protocol tcp
    mask 255.255.255.255
    pool foo
    profiles {
        http { }
        tcp { }
    }
    snat automap
}

root@ve10(Active)(tmos) modify ltm virtual bar destination 172.28.18.0:80 mask 255.255.254.0 translate-address enabled

root@ve10(Active)(tmos) list ltm virtual bar
ltm virtual bar {
    destination 172.28.18.0:http
    ip-protocol tcp
    mask 255.255.254.0
    pool foo
    profiles {
        http { }
        tcp { }
    }
    snat automap
}

root@ve10(Active)(tmos) list ltm virtual-address 172.28.18.0
ltm virtual-address 172.28.18.0 {
    arp disabled
    mask 255.255.254.0
}

root@ve10(Active)(tmos) modify ltm virtual-address 172.28.18.0 arp enabled

root@ve10(Active)(tmos) list ltm virtual-address 172.28.18.0
ltm virtual-address 172.28.18.0 {
    mask 255.255.254.0
}

Hi sundeep,

 

I am not sure but I believe you must configure the in and out interfaces as well, to get the request in to the VS them to specific pool member.

 

I suggest, you must go through the configuration and creation part of the VS, pool member and nodes.