Question

A network engineer configures an IP SLA HTTP GET operation on a branch router to monitor availability of an internal web server referenced by hostname (intranet.corp.local). The operation consistently reports a return code indicating failure, and 'show ip sla statistics' shows the DNS RTT is high or timing out while the TCP connect portion never runs. Pinging the server's IP address directly from the router succeeds. What is the most likely cause?

Accepted Answer

The router has no reachable DNS name-server configured (or 'ip domain-lookup' is disabled), so the HTTP operation cannot resolve the hostname before connecting

Answer

The IP SLA responder is not enabled on the web server, so the HTTP operation cannot complete

Answer

The HTTP operation requires a UDP jitter codec to be specified before it will resolve names

Answer

The control protocol on port 1967 is being blocked between the router and the web server