Troubleshooting Network Monitoring; Track Fails To Take Action - HP 7102dl - ProCurve Secure Router Configuration Manual

Network Monitoring

Troubleshooting Network Monitoring

9-58
Table 9-6. Network Monitoring clear Commands
Command Clears
clear counters probe for all probes:
• number of tests run
• time in current state
clear counters probe for the specified probe:
<name>
• number of tests run
• time in current state
clear counters track for all tracks:
• number of times that the
• time in current state
clear counters track for the specified track:
<name>
• number of times that the
• time in current state
Troubleshooting Network Monitoring
This section explains common causes of general problems with network
monitoring:
The track does not take action (remove a route or log a change) when it
should.
The track takes action (removes a route or logs a change) when it should
not.
A primary route is removed, but a backup route is not added.
A primary route fails and is removed from the routing table, but then
reappears periodically.

Track Fails to Take Action

You receive complaints that a remote server is down, but fail to see any logs
in the event history about this problem. You ping a network, and the ping fails,
but your track fails to remove the route. In either case, your track is not taking
the action that you expect.
track state has changed
track state has changed