cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1476
Views
0
Helpful
8
Replies

GSS polling HTTP HEAD failed

liangzheng
Level 1
Level 1

Hi,

I was configuring a new answer for a site on GSS. I confirmed that the GSS is able to get HTTP HEAD keepalive packets back, but it still considers the answer is offline. I also confirmed that the page that I am using for polling is working fine.

Keepalive statistics:

AnswerTypeNameKeepAliveMethodLocationgss1gss2
1xx.yy.252.15 VIP steel-prod 1xx.yy.252.15 Shared HTTP HEAD STEEL 272
0
0
68
1
240
240
0
80
1
1xx.yy.252.14 VIP vb-prod 1xx.yy.252.14 Shared HTTP HEAD VB 268
0
0
67
1
237
237
0
79
1

Does anyone know what might cause this? Any help will be appreciated.

James

8 Replies 8

venkatkr
Cisco Employee
Cisco Employee

Hi,

what isthe GSS version ? Also can you grab a tcpdump from the GSS for the http head failure. In the trace see the server's response. See if you see a big cookie?

Thanks
Venky

GSS Version 3.1(2).

How can grab the tcpdump? Do you mean capture the packets?

I don't think there is any big cookie there, it is just a simple plain page.

James

tcpdump:

16:10:38.846359 IP (tos 0x0, ttl  64, id 2172, offset 0, flags [DF], proto 6, length: 40) 10.1.99.5.49364 > 142.93.252.14.http: S [tcp sum ok] 3756145484:3756145484(0) win 32000
16:10:38.849633 IP (tos 0x0, ttl 251, id 534, offset 0, flags [DF], proto 6, length: 40) 142.93.252.14.http > 10.1.99.5.49364: S [tcp sum ok] 3643387910:3643387910(0) ack 3756145485 win 1608
16:10:38.849672 IP (tos 0x0, ttl  64, id 2173, offset 0, flags [DF], proto 6, length: 79) 10.1.99.5.49364 > 142.93.252.14.http: P [tcp sum ok] 1:40(39) ack 1 win 32000
16:10:38.853623 IP (tos 0x0, ttl 251, id 538, offset 0, flags [DF], proto 6, length: 192) 142.93.252.14.http > 10.1.99.5.49364: P [tcp sum ok] 1:153(152) ack 40 win 1647
16:10:38.853635 IP (tos 0x0, ttl 251, id 540, offset 0, flags [DF], proto 6, length: 40) 142.93.252.14.http > 10.1.99.5.49364: F [tcp sum ok] 153:153(0) ack 40 win 1647
16:10:38.853662 IP (tos 0x0, ttl  64, id 2174, offset 0, flags [DF], proto 6, length: 40) 10.1.99.5.49364 > 142.93.252.14.http: R [tcp sum ok] 40:40(0) ack 153 win 32000
16:10:50.898697 IP (tos 0x0, ttl  64, id 2193, offset 0, flags [DF], proto 6, length: 40) 10.1.99.5.49371 > 142.93.252.14.http: S [tcp sum ok] 3765278765:3765278765(0) win 32000
16:10:50.902054 IP (tos 0x0, ttl 251, id 13789, offset 0, flags [DF], proto 6, length: 40) 142.93.252.14.http > 10.1.99.5.49371: S [tcp sum ok] 1240700577:1240700577(0) ack 3765278766 win 1608
16:10:50.902097 IP (tos 0x0, ttl  64, id 2194, offset 0, flags [DF], proto 6, length: 79) 10.1.99.5.49371 > 142.93.252.14.http: P [tcp sum ok] 1:40(39) ack 1 win 32000
16:10:50.906026 IP (tos 0x0, ttl 251, id 13816, offset 0, flags [DF], proto 6, length: 192) 142.93.252.14.http > 10.1.99.5.49371: P [tcp sum ok] 1:153(152) ack 40 win 1647
16:10:50.906039 IP (tos 0x0, ttl 251, id 13819, offset 0, flags [DF], proto 6, length: 40) 142.93.252.14.http > 10.1.99.5.49371: F [tcp sum ok] 153:153(0) ack 40 win 1647
16:10:50.906064 IP (tos 0x0, ttl  64, id 2195, offset 0, flags [DF], proto 6, length: 40) 10.1.99.5.49371 > 142.93.252.14.http: R [tcp sum ok] 40:40(0) ack 153 win 32000

Does these indicate anything?

James

James,

You need to save the capture so that we can open in wireshark to see  the HTTP header.

on the GSS, if you type tcpdump and do "?" (without quotes) and keep following with the options. In the end you will get filename where you can put http.pcap and save the file. The file should save in /home directory.

With that i can confirm what is the issue.


Thanks
Venky

Thanks Venky,

The tcpdump file is attached.

James

HI James,


Its not working because the url the GSS is requesting is not getting a 200 OK from the Server. Youa re getting 403. forbidden. Try a different URL for the http head.  The keepalive will fail if the server is nto going to send 200 OK.

Hope it helps. Let me know


Thanks
Venky

I comfirmed the URL is working fine. However, GSS is using a HTTP 1.0 agent to poll the page, but the web server only support 1.1 or high. Is that a way to change the HTTP agent to HTTP 1.1?

Thanks,

James

Let me check and get back to you. IN the mean time open up and IE browser and got to Tools--internetoption and disable "use http 1.1" and test the url. If you get the same error then the server is not RFC complaint. Take a packet capture to use http watch to confirm the http version.

Thanks

Venky

Review Cisco Networking for a $25 gift card