4.
Configure PBR for the probe traffic. In this case, the probes test routes
that use the same forwarding interface, so you can create a single route
map entry:
ProCurve(config)# ip access-list extended ProbeBranch
ProCurve(config-ext-nacl)# permit icmp any host 10.2.1.1
ProCurve(config-ext-nacl)# permit icmp any host 10.3.1.1
ProCurve(config-ext-nacl)# exit
ProCurve(config)# route-map Probes 10
ProCurve(config-route-map)# match ip address ProbeBranch
ProCurve(config-route-map)# set interface ppp 1 null 0
ProCurve(config-route-map)# exit
ProCurve(config)# ip local policy route-map Probes
5.
This router has two demand interfaces, one to place a call to each remote
office. (See the Basic Management and Configuration Guide, Chapter
8: Configuring Demand Routing for Primary ISDN Modules for instruc-
tions on configuring those interfaces, including selecting the traffic that
initiates a call.) Create floating backup routes through those interfaces:
ProCurve(config)# ip route 10.2.0.0 /16 demand 1 2
ProCurve(config)# ip route 10.3.0.0 /16 demand 2 2
6.
The routers at the remote branch offices must also use network monitor-
ing and be configured with the same retries and timeout settings in order
for this configuration to function correctly.
Monitor Connectivity to a Mission-Critical TCP Server
This company includes a main office and a branch office, which connect
through the Internet. The branch office network administrator wants to
monitor the connection to the main office's primary and backup FTP servers.
If the connection to both of these servers fails, an ISDN call to the headquarters
initiates. (The primary connection can continue forwarding other Internet
traffic.)
This scenario requires two probes:
one probe to monitor the connection to the primary FTP server
(FTPServer1)
one probe to monitor the connection to the backup FTP server
(FTPServer2)
The probes will use the default TCP timeout (10 seconds), but a longer period
to minimize overhead.
Network Monitoring
Configuring Network Monitoring
9-47