Network Monitoring
Configuring Network Monitoring
Be careful when configuring raw strings. The CLI does not stop you from
inputting incorrect commands.
You can use raw HTTP probes to submit information to the remote Web server.
For example, you might want to notify the remote network whether the router
is currently using a primary or a backup link. For each link, configure an HTTP
raw probe that submits this notification. For example, the raw string that
follows configures the MyPrimaryWeb probe to notify the remote Web server
that the primary connection on this particular ProCurve Secure Router is
active.
ProCurve(config-probe-MyPrimaryWeb)# raw-string
#GET /log.php?hostname=$SYSTEM_NAME
&serial=$SYSTEM_SERIAL_NUMBER&link=Primary HTTP/1.0
#\r\n
#\r\n
#exit
You would create a similar string for the MyBackupWeb probe:
ProCurve(config-probe-MyBackupWeb)# raw-string
#GET /log.php?hostname=$SYSTEM_NAME
&serial=$SYSTEM_SERIAL_NUMBER&link=Backup HTTP/1.0
#\r\n
#\r\n
#exit
You would give each probe the same destination, but set up PBR to route one
probe over the primary connection and one probe over the backup. The
remote Web server logs which probe actually reaches it.
Activating and Shutting Down the Probe
By default, a probe is shut down and does not initiate any tests until you
activate it. Once you activate the probe, it begins running tests—and consum-
ing bandwidth—even though it does not actually have any effect until you have
associate it with a track. Therefore, you might want to configure the track
before you activate the probe. When shutdown, the probe's status is always
Pass, so the track will not fail in the time that it takes you to activate the probe.
To activate the prove, from the network monitor probe configuration mode
context, enter:
Syntax: no shutdown
9-25