Инструкции По Установке для 3com S7906E

Скачать
Страница из 2621
 
1-7 
 
For the configuration of Track-Static Routing collaboration, the specified static route can be an 
existent or nonexistent one. For an existent static route, the static route and the specified track 
entry are associated directly; for a nonexistent static route, the system creates the static route and 
then associates it with the specified track entry.  
The track entry to be associated with the static route can be a nonexistent one. After you use the 
track command to create the track entry, the association takes effect. 
If the track module detects the next hop reachability of the static route in a private network through 
NQA, the VPN instance name of the next hop of the static route must be consistent with that 
configured for the NQA test group. Otherwise, the reachability detection cannot function properly. 
If a static route needs route recursion, the associated track entry must monitor the next hop of the 
recursive route instead of that of the static route; otherwise, a valid route may be considered 
invalid. 
For details of static route configuration, refer to Static Routing Configuration in the IP Routing 
Volume.  
 
Displaying and Maintaining Track Entries 
To do… 
Use the command… 
Remarks 
Display information about the 
specified track entry or all track 
entries 
display track 
track-entry-number all } 
Available in any view 
 
Track Configuration Examples 
VRRP-Track-NQA Collaboration Configuration Example (The Master Monitors the 
Uplink) 
Network requirements 
As shown in 
, 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 there is a fault on the uplink of Switch A through NQA, packets from Host A 
to Host B are forwarded through Switch B.