Table of Contents
Advertisement
Command Reference Guide
line-protocol
<name>
Network monitoring probes and their associated names are created using the command
probe on page
schedule <name> on page
command
Default Values
By default, a track list does not exist.
Command History
Release 15.1
Release 16.1
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.
An interface is IP routing if its line-protocol state is up and if it has a valid, nonzero IP address. This means
that interfaces using Dynamic Host Configuration Protocol (DHCP) or negotiated Point-to-Point Protocol
(PPP) will not pass until their primary IP address is dynamically configured.
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.
(config)#track LB
(config-track-track LB)#test list and
(config-track-track LB test)#if probe LB
(config-track-track LB test)#if probe LB2
(config-track-track LB test)#exit
(config-track-track LB)#no shutdown
The show track LB command is executed to see whether track LB is in a PASS state:
#show track LB
Current State: PASS
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
60000CRG0-35E
Specifies the line-protocol state of an interface will be tested.
Specifies the name of the probe or schedule.
1291. Schedules and their associated names are created using the command
1313. For more information about interfaces, refer to the
interface on page
74.
Command was introduced.
Command was expanded to include the interface parameter.
(Admin: UP)
Copyright © 2012 ADTRAN, Inc.
Network Monitor Track Command Set
2988
Advertisement
Table of Contents
