Forum Discussion

spudsdragons_86's avatar
spudsdragons_86
Icon for Nimbostratus rankNimbostratus
Jan 28, 2010

URI in pools

I am running version: 4.5.13

 

 

I'm able to get the URI just fine, but when load balancing to my pool the uri (/folder) does not pass to the pool.

 

 

For Example:

 

 

url: www.testhost.com/folder --> Virtual Server(192.1.2.2) --> Test_Pool

 

 

 

Test_Pool -> Members

 

192.1.2.3/folder

 

192.1.2.4/folder

 

 

Any help would be greatly appreciated.

 

7 Replies

  • Do you have a standard HTTP VIP defined which points to a pool of web servers? Or is it HTTPS?

     

     

    What happens when a client makes a request for /folder? If you use a browser plugin like HttpFox for Firefox or Fiddler for IE, do you get any response from the VIP? What does the browser display when a request fails?

     

     

    Aaron
  • It is a standard HTTP Virtual IP not HTTPS.

     

     

    When the client makes a request I get "Problem loading page error". Using HttpFox I don't see a response from the VIP, the first thing I get back is a 300 post (Aborted) text/plain (NS_Binding_ABORTED). Using FireFox the browser displays "The connection was reset"

     

     

    Thanks in advance for any help or guidance.

     

     

    Hector
  • Hi Hector,

     

     

    Can you check to see if the request gets to the pool member and if so, what response BIG-IP gets from the server? You can use tcpdump to do this:

     

     

    tcpdump -ni VLAN_EXT -Xs0 host CLIENT_IP

     

     

    tcpdump -ni VLAN_INT -Xs0 host POOL_IP_1 or host POOL_IP_2

     

     

    Thanks,

     

    Aaron
  • Browser displays =>

     

     

    The connection was reset

     

     

     

    The connection to the server was reset while the page was loading.

     

     

    * The site could be temporarily unavailable or too busy. Try again in a few

     

    moments.

     

     

    * If you are unable to load any pages, check your computer's network

     

    connection.

     

     

    * If your computer or network is protected by a firewall or proxy, make sure

     

    that Firefox is permitted to access the Web
  • When I run the windump since this is going to a BEA webserver on Windows 2003 I get this:

     

     

    E:\WinDump>windump -i 2 tcp port 80

     

    windump: listening on \Device\NPF_{F1CD4694-2262-4405-8407-E5A43CD0982D}

     

    11:02:25.350966 IP dnfhb71.promero.com.2468 > fllccabea1.promero.com.80: S 13944

     

    99931:1394499931(0) win 8192

     

    11:02:25.350994 IP fllccabea1.promero.com.80 > dnfhb71.promero.com.2468: S 29685

     

    54047:2968554047(0) ack 1394499932 win 16384

     

    11:02:29.240339 IP fllccabea1.promero.com.80 > dnfhb71.promero.com.2468: S 29685

     

    54047:2968554047(0) ack 1394499932 win 16384

     

    11:02:30.709663 IP dnfhb71.promero.com.2468 > fllccabea1.promero.com.80: S 13944

     

    99931:1394499931(0) win 8192

     

    11:02:38.974524 IP fllccabea1.promero.com.80 > dnfhb71.promero.com.2468: S 29685

     

    54047:2968554047(0) ack 1394499932 win 16384

     

    11:02:39.711328 IP dnfhb71.promero.com.2468 > fllccabea1.promero.com.80: S 13944

     

    99931:1394499931(0) win 8192

     

    11:02:56.714186 IP dnfhb71.promero.com.2468 > fllccabea1.promero.com.80: S 13944

     

    99931:1394499931(0) win 8192

     

    11:03:15.241442 IP dnfhb71.promero.com.2482 > fllccabea1.promero.com.80: S 22606

     

    73499:2260673499(0) win 8192

     

    11:03:15.241468 IP fllccabea1.promero.com.80 > dnfhb71.promero.com.2482: S 30482

     

    20573:3048220573(0) ack 2260673500 win 16384

     

    11:03:19.005128 IP fllccabea1.promero.com.80 > dnfhb71.promero.com.2482: S 30482

     

    20573:3048220573(0) ack 2260673500 win 16384

     

    11:03:20.727838 IP dnfhb71.promero.com.2482 > fllccabea1.promero.com.80: S 22606

     

    73499:2260673499(0) win 8192

     

    11:03:27.551864 IP fllccabea1.promero.com.80 > dnfhb71.promero.com.2482: S 30482

     

    20573:3048220573(0) ack 2260673500 win 16384

     

    11:03:29.719461 IP dnfhb71.promero.com.2468 > fllccabea1.promero.com.80: S 13944

     

    99931:1394499931(0) win 8192

     

    11:03:29.719488 IP fllccabea1.promero.com.80 > dnfhb71.promero.com.2468: S 29851

     

    70085:2985170085(0) ack 1394499932 win 16384

     

    11:03:29.729291 IP dnfhb71.promero.com.2482 > fllccabea1.promero.com.80: S 22606

     

    73499:2260673499(0) win 8192

     

    11:03:33.458024 IP fllccabea1.promero.com.80 > dnfhb71.promero.com.2468: S 29851

     

    70085:2985170085(0) ack 1394499932 win 16384

     

    11:03:43.286005 IP fllccabea1.promero.com.80 > dnfhb71.promero.com.2468: S 29851

     

    70085:2985170085(0) ack 1394499932 win 16384
  • It will be most useful to get tcpdumps from both VLANs on the BIG-IP. If you need help capturing or analyzing the tcpdumps, you can open a case with F5 Support.

     

     

    For quick analysis of the traces, you can use the -X flag to write out the hex to ascii.

     

     

    Aaron