SROS Command Line Interface Reference Guide
Network Monitor Track Configuration Command Set
5991-2114
© Copyright 2006 Hewlett-Packard Development Company, L.P.
1355
Functional Notes
There is no limit to how many probes, schedules, or interfaces can be tested within a single test list.
However, only one type (AND, OR, or weighted) of test list can exist on a track at any given time.
Usage Examples
The following example demonstrates use of the
test list and
command to create a Boolean track test list
where ALL tests must PASS in order for the track to PASS. The test list for track LB contains two probe
tests, LB and LB2.
ProCurve(config)#
track LB
ProCurve(config-track-track LB)#
test list and
ProCurve(config-track-track LB test)#
if probe LB
ProCurve(config-track-track LB test)#
if probe LB2
ProCurve(config-track-track LB test)#
exit
ProCurve(config-track-track LB)#
no shutdown
The
show track LB
command is executed to see whether track LB is in a PASS state:
ProCurve#
show track LB
Current State: PASS (Admin: UP)
Testing:
probe LB (PASS)
AND probe LB2 (PASS)
Dampening Interval: 1 seconds
Time in current state: 0 days, 0 hours, 0 minutes, 29 seconds
Track State Changes: 2
Tracking:
Currently, track LB is in a PASS state. Due to the AND Boolean logic for this test list, track LB is in a PASS
state because the test probe statements within the test list (probe LB and LB2) are also BOTH in a PASS
state.
Now, probe LB has been forced to fail for demonstration purposes in this example. Output from the
show
track LB
command shows track LB in a FAIL state.
ProCurve(config-loop 1)#
do show track LB
Current State: FAIL (Admin: UP)
Testing:
probe LB (FAIL)
AND probe LB2 (PASS)
Dampening Interval: 1 seconds
Time in current state: 0 days, 0 hours, 0 minutes, 10 seconds
Track State Changes: 3
Tracking:
Probe LB is now in a FAIL state. As a result, track LB is also in a FAIL state.
