Configuring Network Monitoring - HP 7102dl - ProCurve Secure Router Configuration Manual

Network Monitoring

Configuring Network Monitoring

9-10
connection, the track reinstates the failed primary route—only to remove the
route again when the probes start to fail. Users lose their sessions as the
connection toggles up and down.
Use PBR to solve this problem. You configure a route map to forward probe
packets along the route that the probe tests. In this way, no matter what
actions tracks take on the routing table, the probes continue to test the correct
connection.
Configuring Network Monitoring
Network monitoring relies on tracks; each track monitors a certain network
function. A track can:
test the validity of a static route or of a default route received with a DHCP
or negotiated address
monitor a particular server or network service, such as a Web server or
File Transfer Protocol (FTP) site
To create a track, you must complete these basic steps:
1. Configure one or more probes.
2. If tracks monitor routes, configure PBR for the probe traffic.
3. Configure the track and associate it with one or two probes.
4. Enable the track to take an action, which typically includes:
• configuring the track to log changes in probe states
• associating the track with a route
5. If you are using Network Address Translation (NAT), configure the router
to use different translation statements depending on the current forward-
ing interface.
6. If you are using the ProCurve Secure Router firewall, create access
control policies (ACPs) to disable the reverse path forwarding (RPF)
check on traffic received on the primary and backup interfaces.
The following sections will first explain how to complete these steps and then
give examples of tracks configured to monitor various network functions.