Displaying and maintaining track entries, Track configuration examples, Network requirements – H3C Technologies H3C S10500 Series Switches User Manual

Page 183

Advertising
background image

174

To do…

Use the command…

Remarks

Define an ACL match criterion

if-match acl acl-number

Optional
By default, no packets are
filtered.

Set the next hop and associate it
with a track entry

apply ip-address next-hop ip-address
[ direct ] [ track track-entry-number ]

[ ip-address [ direct ] [ track
track-entry-number ] ]

Set the default next hop, and
associate it with a track entry

apply ip-address default next-hop
ip-address [ track track-entry-number]
[ ip-address [ track track-entry-number] ]

Required
Configure at least one of the
commands.

NOTE:

You can associate a nonexistent track entry with PBR. The association takes effect only after you use the
track command to create the track entry.

For more information about PBR, see

Layer 3—IP Routing Configuration Guide.

Displaying and maintaining track entries

To do…

Use the command…

Remarks

Display information about the
specified or all track entries

display track { track-entry-number |
all } [ | { begin | exclude |

include } regular-expression ]

Available in any view

Track configuration examples

VRRP-track-NQA collaboration configuration example (the

master monitors the uplink)

Network requirements

As shown in

Figure

47

, Host A needs to access Host B on the Internet. The default gateway of Host

A is 10.1.1.10/24.

Switch A and Switch B belong to VRRP group 1, whose virtual IP address is 10.1.1.10.

When Switch A works normally, packets from Host A to Host B are forwarded through Switch A.
When VRRP finds that a fault is on the uplink of Switch A through NQA, packets from Host A to Host

B are forwarded through Switch B.

Advertising