HP ProCurve Secure 7102dl, Справочное руководство

Страница: 1354 / 1455

SROS Command Line Interface Reference Guide Network Monitor Track Configuration Command Set
5991-2114 © Copyright 2006 Hewlett-Packard Development Company, L.P. 1352
ProCurve(config)# track DELAY
ProCurve(config-track-DELAY)# test if not schedule DELAY-AFTER-BOOT
The explanation that follows uses a real-world example to provide insight into the example above:
A customer has a primary Ethernet WAN interface, as well as a dial-on-demand interface enabled on an
SROS unit. The demand interface is intended as a backup for the primary Ethernet interface. During router
initialization and bootup, the Ethernet interface negotiates an IP address and default route from a DHCP
server. Due to this negotiation process, the active state of the Ethernet interface lags behind that of the
demand interface. As a result, the Ethernet interface appears “down” and the demand interface dials out to
back up the connection. The customer would like to prevent the demand interface from dialing out before
the Ethernet connection has had a chance to obtain its DHCP settings and become active. It is determined
that 180 seconds is a sufficient amount of time to allow for the Ethernet interface to become active.
The following bullets describe the setup via CLI to accomplish the customer's goals:
• A schedule called DELAY-AFTER-BOOT is created and specified to become active 180 seconds after
the SROS unit has booted up.
• A track named DELAY is created.
• Track DELAY is associated with the schedule DELAY-AFTER-BOOT via the following command:
(config-track-DELAY)# test if not schedule DELAY-AFTER-BOOT
The inverse logic of this command means that track DELAY will pass only if the schedule
DELAY-AFTER-BOOT is inactive. Therefore, this track will pass only during the first 180 seconds
following boot up of the SROS unit.
• A default route to null interface 0 is created and associated with track DELAY. This default route will
only be inserted into the routing table when track DELAY is in the pass state. The administrative
distance for the default route to null interface 0 is 10 and is set to be lower than the administrative
distance for the demand interface default route (200).
Output from the show run command summarizes the CLI configuration:
ProCurve#
show run
(some output omitted)…
.
schedule DELAY-AFTER-BOOT
!! Schedule is Inactive for first 180 seconds, then Active thereafter
relative start-after 180
!
track DELAY
log-changes
test if not schedule DELAY-AFTER-BOOT
Note
The inverse logic of this command means that track DELAY will pass only if the schedule
DELAY-AFTER-BOOT is inactive.