The following decoded TCPDump capture shows the trace of a failing health monitor.
00:00:13.245104 IP 10.29.29.60.51947 > 10.0.0.12.http: P 1:59(58) ack 1 win 46 <nop,nop,timestamp
2494782300 238063789> out slot1/tmm3 lis=
0x0000: 4500 006e 3b19 4000 4006 ce0c 0a1d 1d3c E..n;.@.@……<
0x0010: 0a00 000c caeb 0050 8be5 aca3 dd65 e3e1 …….P…..e..
0x0020: 8018 002e 1b41 0000 0101 080a 94b3 5b5c …..A……..[\\
0x0030: 0e30 90ad 4745 5420 2f74 6573 745f 7061 .0..GET./test_pa
0x0040: 6765 2e68 746d 6c20 4854 5450 312e 310d ge.html.HTTP1.1.
0x0050: 0a48 6f73 743a 200d 0a43 6f6e 6e65 6374 .Host:…Connect
0x0060: 696f 6e3a 2043 6c6f 7365 0d0a 0d0a 0105 ion:.Close……
0x0070: 0100 0003 00 …..
00:00:13.245284 IP 10.0.0.12.http > 10.29.29.60.51947: . ack 59 win 362 <nop,nop,timestamp 238063789
2494782300> in slot1/tmm3 lis=
0x0000 0ffd 0800 4500 00c9 6f68 4000 8006 755d ….E…oh@…u]
0x0010 0a29 0015 0a29 0103 0050 e0d6 4929 90eb .)…)…P..I)..0x0020 6f12 d83c 8019 fab3 9b31 0000 0101 080a o..<…..1……
0x0030 0068 4e10 5240 6150 4854 5450 2f31 2e31 .hN.R@aPHTTP/1.1
0x0040 2034 3030 2042 6164 2052 6571 7565 7374 .400.Bad.Request
0x0050 0d0a 436f 6e74 656e 742d 5479 7065 3a20 ..Content-Type:.
0x0060 7465 7874 2f68 746d 6c0d 0a44 6174 653a text/html..Date:
0x0070 2054 6875 2c20 3231 204a 616e 2032 3031 .Mon,.01.Jan.201
0x0080 3020 3138 3a35 383a 3537 2047 4d54 0d0a 2.00:00:01.GMT..
0x0090 436f 6e6e 6563 7469 6f6e 3a20 636c 6f73 Connection:.clos
0x00a0 650d 0a43 6f6e 7465 6e74 2d4c 656e 6774 e..Content-Lengt
0x00b0 683a 2032 300d 0a0d 0a3c 6831 3e42 6164 h:.20….<h1>Bad
0x00c0 2052 6571 7565 7374 3c2f 6831 3e .Request</h1>
The health monitor is sending the string shown in the capture; however, the server response is NOT as
expected. The correct response should be an HTML page including the string ‘SERVER IS UP’.
What is the issue?
A.
The /test_page.html does NOT exist on the web server.
B.
Incorrect syntax in send string. ‘HTTP1.1’ should be ‘HTTP/1.1’.
C.
Incorrect syntax in send string. ‘Connection: Close’ should be ‘Connection: Open’.
D.
The wrong HTTP version is specified in the send string. Version 1.2 should be used instead of version
1.1.