web service issue

Hi Robert,

 

 

Does the pool have a monitor enabled? If so, it is marked up? If not, does LTM have a self IP on the same subnet as the servers? If there isn't one, you'll need a route.

 

 

Do you see the pool stats incrementing?

 

 

If you run a tcpdump (tcpdump -ni 0.0 -Xs0 host 1.1.1.1) looking for traffic destined for the server(s) IP do you see a reply coming back when a client connects to the VS? If not, is the server default gateway pointing to a TMM self IP? If not, you'll need to use source address translation. You can test with SNAT automap enabled on the virtual server.

 

 

Aaron

yes it has tcp under the health monitors for the pool. This pool is setup the same way as the pool that handles the HTTP traffic on port 80 on the same two servers with the exception of the session persistence. Port 80 has it and port 81 doesn't!! The port 80 traffic is working fine but the web service on port 81 isn't. The HTTP traffic and the port 81 traffic share the same virtual server 10.194.11.111

Can you try a tcpdump then:

 

 

tcpdump -ni 0.0 -Xs0 host 1.1.1.1 and port 81

 

 

Aaron

Is TCP port 81 added to your list of available virtual services?

I did the TCP dump using the "Support" option and downloaded it but how do I read it? WinDbg opens it but most of it is unreadable.

You can use wireshark:

 

 

http://www.wireshark.org/download.html

 

 

Basically you should look for a three way TCP handshake to the pool member. If that's happening, then you can right click on one of the packets and select follow TCP stream to see the payloads in one view.

 

 

Aaron

I have the info but can I email to you and let you take a look at it? I don't know what a TCP handshake looks like; I'm a newbie at this!

If you need help analyzing the tcpdump you can open a support case.

 

 

Aaron

Thanks.

Robert,

 

 

The obvious things to look for in wireshark is two way traffic. Are you seeing traffic to your servers' ip addresses and corresponding traffic from the server's ip addresses? If you're only seeing traffic in one way, e.g. dest is always x.x.x.x but never source x.x.x.x then that indicates an issue. Also, if you install wireshark on your web servers and run a packet capture, again, you want to see traffic from and to the client ip / or if using snat the LTM ip address. If port 80 is working hopefully you'll see noticeable differences. Pop "port 80" in the filter bar and then "port 81" to see these differences (without the quotes).

 

 

Also, in the GUI statistics, if you select Pool Member stats (I think that's what it's called" do you see the connections increment when you try to attach? If not then the request isn't even been sent to the pool member.

 

 

Hope this helps a bit.

 

 

N