QuestionQ141

Identify and Resolve LTM Device Issues

An LTM Specialist has configured an HTTP monitor as follows:

ltm monitor http stats_http_monitor \{  
defaults-from http  
destination *:*  
interval 5  
recv "Health check: OK"  
send "GET /stats/stats.html HTTP/1.1\\r\\nHost: www.example.com\\r\\nAccept-EncodinG. gzip, deflate\\r\\nConnection: close\\r\\n\\r\\n" time-until-up 0 timeout 16  
\}  

The monitor is marking every node down. A trace of the HTTP conversation shows:

GET /stats/stats.html HTTP/1.1 -  
  
Host: www.example.com -  
  
Accept-EncodinG. gzip, deflate -  
  
Connection: close -  
HTTP/1.1 401 Authorization Required  
DatE. Tue, 23 Oct 2012 19:38:56 GMT  
Server: Apache/2.2.15 (Unix)  
WWW-AuthenticatE. Basic realm="Please enter your credentials"  
  
Content-LengtH. 480 -  
  
Connection: close -  
Content-TypE. text/html; charset=iso-8859-1  

Which action resolves the problem?

  • A Add an NTLM profile to the virtual server.
  • B Add a valid username and password to the monitor.
  • C Use an HTTPS monitor with a valid certificate instead.
  • D Add a backslash before the colon in the receive string.
Explanation

An HTTP 401 response with WWW-Authenticate: Basic indicates that the monitored resource requires HTTP Basic authentication. Configuring valid monitor credentials allows BIG-IP to send the authenticated request and receive the required health-check content. BIG-IP HTTP monitors provide username and password properties specifically for monitored targets that require authentication.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!