Network Monitoring
Troubleshooting Network Monitoring
9-60
Incorrect probe destination—View a probe (show probe <name>) and
check for a miskeyed destination address or hostname, which would
cause the probe to fail when it should pass.
Inappropriate timeout and tolerance settings—You might find that you
need to adjust a probe's timeout or tolerance settings to account for
normal network congestion. If you find that a probe often fluctuates
between Pass and Fail, you can increase the tolerance, add a dampening
interval to the associated track, or both.
Misconfigured HTTP probe—You can customize the response required
from a Web server, but with this increased control comes increased risk
for misconfiguration. These two commands can cause an HTTP probe to
fail even when the probe receives a response for the server:
•
expect status <value>
•
expect regex <expression>
View the configuration for the probe associated with the track (show
running-config probe) and look for those commands. Look for and fix
obvious misconfigurations such as typos. If you cannot find a misconfig-
uration, try expanding the range of allowed statuses or simply removing
the commands in question entirely. Then check whether probes more
accurately test the Web server's status.
Backup Route Fails to Be Added
Network monitoring tracks can remove failed routes, but they cannot add
backup routes. You must configure those routes in advance. Simply create a
route to the network in question through the backup interface (typically a
demand interface), and assign the route a higher administrative distance than
the primary route.
Make sure that a demand interface is ready to initiate a call. It should be
spoofing an up status. See the Basic Management and Configuration Guide,
Chapter 8: Configuring Demand Routing for Primary ISDN Modules and
the Advanced Management and Configuration Guide, Chapter 3: Configur-
ing Backup WAN Connections for more information on configuring demand
routing.