H3C S5120-EI Series - Associating the Track Module with an Application Module; Associating Track with Static Routing

127
Ste
p
Command Remarks
2. Associate track with interface
management.
Create a track entry, associate it with the
interface management module to monitor
the physical status of an interface, and
specify the delay time for the track module
to notify the associated application
module when the track entry status
changes:
track track-entry-number interface
interface-type interface-number [ delay
{ negative negative-time | positive
positive-time } * ]
Create a track entry, associate it with the
interface management module to monitor
the Layer 3 protocol status of an interface,
and specify the delay time for the track
module to notify the associated
application module when the track entry
status changes:
track track-entry-number interface
interface-type interface-number protocol
{ ipv4 | ipv6 } [ delay { negative
negative-time | positive positive-time } * ]
Use either approach.
No track entry is created by
default.
Associating the track module with an application
module
Associating track with static routing
A static route is a manually configured route. With a static route configured, packets to the specified
destination are forwarded through the path specified by the administrator.
The disadvantage of using static routes is that they cannot adapt to network topology changes. Faults or
topological changes in the network can make the routes unreachable, causing network breaks.
To prevent this problem, configure another route to back up the static route. When the static route is
reachable, packets are forwarded through the static route. When the static route is unreachable, packets
are forwarded through the backup route, avoiding network breaks and enhancing network reliability.
To check the accessibility of a static route in real time, establish association between the track and the
static route.
If you specify the next hop but not the egress interface when configuring a static route, you can establish
collaborations among the static route, the track module, and detection modules. This enables you to
check the accessibility of the static route by the status of the track entry.
• The Positive state of the track entry shows that the next hop of the static route is reachable and that
the configured static route is valid.
• The Negative state of the track entry shows that the next hop of the static route is not reachable and
that the configured static route is invalid.