Displaying and maintaining track entries, Track configuration examples, Vrrp-track-nqa collaboration configuration example – H3C Technologies H3C MSR 5600 User Manual
Page 71: Network requirements
63
Step Command
Remarks
4.
Associate Track with IPv6
PBR.
•
Set the outgoing interface, and associate it
with a track entry:
apply output-interface { interface-type
interface-number [ track
track-entry-number ] }&<1-n>
•
Set the next hop, and associate it with a
track entry:
apply next-hop [ vpn-instance
vpn-instance-name | inbound-vpn ]
{ ipv6-address [ direct ] [ track
track-entry-number ] }&<1-n>
•
Set the default outgoing interface, and
associate it with a track entry:
apply default-output-interface
{ interface-type interface-number [ track
track-entry-number ] }&<1-n>
•
Set the default next hop, and associate it
with a track entry:
apply default-next-hop [ vpn-instance
vpn-instance-name | inbound-vpn ]
{ ipv6-address [ direct ] [ track
track-entry-number ] }&<1-n>
Use at least one of the
commands.
Displaying and maintaining track entries
Execute display commands in any view.
Task Command
Display information about a specific or
all track entries.
display track { track-entry-number | all }
Track configuration examples
VRRP-Track-NQA collaboration configuration example
In this example, the master monitors the uplink.
Network requirements
As shown in
, configure Host A to access Host B on the Internet. The default gateway of Host A
is 10.1.1.10/24.
Router A and Router B belong to VRRP group 1, which has the virtual IP address 10.1.1.10.
When Router A works correctly, packets from Host A to Host B are forwarded through Router A. When
NQA detects that a fault is on the uplink of Router A, packets from Host A to Host B are forwarded
through Router B.