Login
- Table of Contents
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 02-Track configuration | 197.03 KB |
Contents
Restrictions and guidelines: Track configuration
Restrictions: Hardware compatibility with Track
Collaboration application example
Associating Track with a detection module object
Associating Track with interface management
Associating Track with route management
Associating Track with a tracked list
Associating Track with a Boolean list
Associating Track with a percentage threshold list
Associating Track with a weight threshold list
Associating the Track module with an application module
Prerequisites for associating the Track module with an application module
Associating Track with static routing
Verifying and maintaining Track
Example: Configuring static routing-Track-NQA collaboration
Configuring Track
The term router in this chapter refers to a routing-capable device.
About Track
Collaboration mechanism
The Track module collaborates with detection modules and application modules.
As shown in Figure 1, collaboration is enabled when you associate the Track module with a detection module and an application module, and it operates as follows:
1. The detection module probes specific objects such as interface status, link status, network reachability, and network performance, and informs the Track module of detection results.
2. The Track module sends the detection results to the application module.
3. When notified of changes for the tracked object, the application modules can react to avoid communication interruption and network performance degradation.
Figure 1 Collaboration through the Track module
Collaboration between the Track module and a detection module
The detection module sends the detection result of the tracked object to the Track module. The Track module changes the status of the track entry as follows:
· If the tracked object operates correctly, the state of the track entry is Positive. For example, the track entry state is Positive in one of the following conditions:
¡ The target interface is up.
¡ The target network is reachable.
· If the tracked object does not operate correctly, the state of the track entry is Negative. For example, the track entry state is Negative in one of the following conditions:
¡ The target interface is down.
¡ The target network is unreachable.
· If the detection result is invalid, the state of the track entry is NotReady. For example, the track entry state is NotReady if its associated NQA operation does not exist.
You can associate a track entry with an object of a detection module, such as the state of an interface or reachability of an IP route. The state of the track entry is determined by the state of the tracked object.
You can also associate a track entry with a list of objects called a tracked list. The state of a tracked list is determined by the states of all objects in the list. The following types of tracked lists are supported:
· Boolean AND list—The state of a Boolean AND list is determined by the states of the tracked objects using the Boolean AND operation.
· Boolean OR list—The state of a Boolean OR list is determined by the states of the tracked objects using the Boolean OR operation.
· Percentage threshold list—The state of a percentage threshold list is determined by comparing the percentage of positive and negative objects in the list with the percentage thresholds configured for the list.
· Weight threshold list—The state of a weight threshold list is determined by comparing the weight of positive and negative objects in the list with the weight thresholds configured for the list.
Collaboration between the Track module and an application module
Supported detection modules
The following detection modules can be associated with the Track module:
· NQA.
· Interface management.
· Route management.
· LLDP.
Restrictions and guidelines: Track configuration
When configuring a track entry for an application module, you can set a notification delay to avoid immediate notification of status changes.
When the delay is not configured and the route convergence is slower than the link state change notification, communication failures occur. For example, when the master in a VRRP group detects an uplink interface failure through Track, Track immediately notifies the master to decrease its priority. A backup with a higher priority then preempts as the new master. When the failed uplink interface recovers, the Track module immediately notifies the original master to restore its priority. If the uplink route has not recovered, forwarding failure will occur.
Restrictions: Hardware compatibility with Track
|
Hardware series |
Model |
Product code |
Track compatibility |
|
WX3500X series |
· WX3510X · WX3520X · WX3540X |
· EWP-WX3510X · EWP-WX3520X · EWP-WX3540X |
No |
|
WCG380 series |
WCG382 |
EWP-WCG382 |
Yes |
|
Hardware series |
Model |
Product code |
Feature compatibility |
|
WX3800X series |
· WX3820X · WX3840X |
· EWP-WX3820X · EWP-WX3840X |
No |
Collaboration application example
This example shows how to implement collaboration between NQA, Track, and uplink detection.
If the uplink fails, the AC disables the radio on the AP that associates with the AC. If the uplink recovers, the AC enables the radio on the AP. For this purpose, configure collaboration between the NQA, Track, and uplink detection.
1. Configure an NQA operation to check the accessibility of the Device.
2. Create a track entry and associate it with the NQA operation.
¡ When the Device is reachable, the track entry is in Positive state.
¡ When the Device becomes unreachable, the track entry is in Negative state.
3. Associate the track entry with the WLAN uplink detection feature.
¡ When the associated track entry turns to Negative state, the uplink detection feature disables the radio on the AP. Wireless clients will not be associated with the AP.
¡ When the track entry changes to the Positive state, the uplink detection feature enables the radio on the AP. Wireless clients can be associated with the AP.
Track tasks at a glance
To implement the collaboration function, establish associations between the Track module and detection modules, and between the Track module and application modules.
To configure the Track module, perform the following tasks:
1. Associating Track with a detection module object
¡ Associating Track with interface management
¡ Associating Track with route management
2. Associating Track with a tracked list
¡ Associating Track with a Boolean list
¡ Associating Track with a percentage threshold list
¡ Associating Track with a weight threshold list
3. Associating the Track module with an application module
¡ Associating Track with static routing
Associating Track with a detection module object
Associating Track with NQA
About this task
NQA supports multiple operation types to analyze network performance and service quality. For example, an NQA operation can periodically detect whether a destination is reachable, or whether a TCP connection can be established.
An NQA operation operates as follows when it is associated with a track entry:
· If the consecutive probe failures reach the specified threshold, the NQA module notifies the Track module that the tracked object has malfunctioned. The Track module then sets the track entry to Negative state.
· If the specified threshold is not reached, the NQA module notifies the Track module that the tracked object is operating correctly. The Track module then sets the track entry to Positive state.
For more information about NQA, see Network Management and Monitoring Configuration Guide.
Restrictions and guidelines
If you associate a track entry with a nonexistent NQA operation or reaction entry, the state of the track entry is NotReady.
Procedure
1. Enter system view.
system-view
2. Create a track entry associated with an NQA reaction entry and enter its view.
track track-entry-number nqa entry admin-name operation-tag reaction item-number
3. (Optional.) Set the delay for notifying the application module of track entry state changes.
delay { negative negative-time | positive positive-time } *
By default, the Track module notifies the application module immediately when the track entry state changes.
Associating Track with interface management
About this task
The interface management module monitors the link status or network-layer protocol status of interfaces. The associated Track and interface management operate as follows:
· When the link or network-layer protocol status of the interface changes to up, the interface management module informs the Track module of the change. The Track module sets the track entry to Positive state.
· When the link or network-layer protocol status of the interface changes to down, the interface management module informs the Track module of the change. The Track module sets the track entry to Negative state.
Procedure
1. Enter system view.
system-view
2. Create a track entry associated with an interface and enter its view. Choose the options to configure as needed:
¡ Create a track entry associated with the link status of an interface.
track track-entry-number interface interface-type interface-number
¡ Create a track entry associated with the physical status of an interface.
track track-entry-number interface interface-type interface-number physical
¡ Create a track entry associated with the network layer protocol status of an interface.
track track-entry-number interface interface-type interface-number protocol { ipv4 | ipv6 }
3. (Optional.) Set the delay for notifying the application module of track entry state changes.
delay { negative negative-time | positive positive-time } *
By default, the Track module notifies the application module immediately when the track entry state changes.
Associating Track with route management
About this task
The route management module monitors route entry changes in the routing table. The associated Track and route management operate as follows:
· When a monitored route entry is found in the routing table, the route management module informs the Track module. The Track module sets the track entry to Positive state.
· When a monitored route entry is removed from the routing table, the route management module informs the Track module of the change. The Track module sets the track entry to Negative state.
Associating a track entry with an IPv4 route entry
1. Enter system view.
system-view
2. Create a track entry associated with an IPv4 route and enter its view.
track track-entry-number ip route ip-address { mask-length | mask } reachability
3. (Optional.) Set the delay for notifying the application module of track entry state changes.
delay { negative negative-time | positive positive-time } *
By default, the Track module notifies the application module immediately when the track entry state changes.
Associating a track entry with an IPv6 route entry
1. Enter system view.
system-view
2. Create a track entry associated with an IPv6 route and enter its view.
track track-entry-number ipv6 route ipv6-address prefix-length reachability
3. (Optional.) Set the delay for notifying the application module of track entry state changes.
delay { negative negative-time | positive positive-time } *
By default, the Track module notifies the application module immediately when the track entry state changes.
Associating Track with LLDP
About this task
The LLDP module detects neighbor availability and informs the detection result to the Track module. The associated Track and LLDP operate as follows:
· When the neighbor is available, the Track module sets the track entry to Positive state.
· When the neighbor is unavailable, the Track module sets the track entry to Negative state.
For more information about LLDP, see Network Connectivity Configuration Guide.
Procedure
1. Enter system view.
system-view
2. Create a track entry and associate it with an LLDP interface.
track track-entry-number lldp neighbor interface interface-type interface-number [ delay { negative negative-time | positive positive-time } * ]
Associating Track with a tracked list
Associating Track with a Boolean list
About this task
A Boolean list is a list of tracked objects based on a Boolean logic. It can be further divided into the following types:
· Boolean AND list—A Boolean AND list is set to the Positive state only when all objects are in Positive state. If one or more objects are in Negative state, the tracked list is set to the Negative state.
· Boolean OR list—A Boolean OR list is set to the Positive state if any object is in Positive state. If all objects are in Negative state, the tracked list is set to the Negative state.
Procedure
1. Enter system view.
system-view
2. Create a track entry.
See "Associating Track with a detection module object."
Create a track entry before you add it as a tracked object to a tracked list.
A minimum of one track entry must be created.
3. Create a Boolean tracked list and enter its view.
track track-entry-number list boolean { and | or }
4. Add the track entry as an object to the tracked list.
object track-entry-id [ not ]
By default, a tracked list does not contain any objects.
Repeat this step to add all interested objects to the tracked list.
5. (Optional.) Set the delay for notifying the application module of tracked list state changes.
delay { negative negative-time | positive positive-time } *
By default, the Track module notifies the application module immediately when the tracked list state changes.
Associating Track with a percentage threshold list
About this task
A percentage threshold list uses a percentage threshold to measure the state of the list.
· If the percentage of positive objects is equal to or above the positive state threshold, the list is set to the Positive state.
· If the percentage of positive objects is equal to or below the negative state threshold, the list is set to the Negative state.
· The state of a percentage threshold list remains unchanged if the percentage of positive objects is below the positive state threshold and above the negative state threshold.
Procedure
1. Enter system view.
system-view
2. Create a track entry.
See "Associating Track with a detection module object."
Create a track entry before you add it as a tracked object to a tracked list.
A minimum of one track entry must be created.
3. Create a percentage threshold list and enter its view.
track track-entry-number list threshold percentage
4. Add the track entry as an object to the tracked list.
object track-entry-id
By default, a tracked list does not contain any objects.
Repeat this step to add all interested objects to the tracked list.
5. Configure the threshold values used to determine the state of the percentage threshold list.
threshold percentage { negative negative-threshold | positive positive-threshold } *
By default, the negative state threshold is 0% and the positive state threshold is 1%.
6. (Optional.) Set the delay for notifying the application module of tracked list state changes.
delay { negative negative-time | positive positive-time } *
By default, the Track module notifies the application module immediately when the tracked list state changes.
Associating Track with a weight threshold list
About this task
A weight threshold list uses a weight threshold to measure the state of the list.
· If the total weight of positive objects is equal to or above the positive state threshold, the list is set to the Positive state.
· If the total weight of positive objects is equal to or below the negative state threshold, the list is set to the Negative state.
· The state of a weight threshold list remains unchanged if the total weight of positive objects is below the positive state threshold and above the negative state threshold.
Procedure
1. Enter system view.
system-view
2. Create a track entry.
See "Associating Track with a detection module object."
Create a track entry before you add it as a tracked object to a tracked list.
A minimum of one track entry must be created.
3. Create a weight threshold list and enter its view.
track track-entry-number list threshold weight
By default, no tracked lists exist.
4. Add the track entry as an object to the tracked list.
object track-entry-number [ weight ]
By default, a tracked list does not contain any objects.
Repeat this step to add all interested objects to the tracked list.
5. Configure the threshold values used to determine the state of the weight threshold list.
threshold weight { negative negative-threshold | positive positive-threshold } *
By default, the negative state threshold is 0 and the positive state threshold is 1.
6. (Optional.) Set the delay for notifying the application module of tracked list state changes.
delay { negative negative-time | positive positive-time } *
By default, the Track module notifies the application module immediately when the tracked list state changes.
Associating the Track module with an application module
Before you associate the Track module with an application module, make sure the associated track entry has been created.
Prerequisites for associating the Track module with an application module
Create a track entry first before you associate it with an application module.
An application module might obtain incorrect track entry status information if the associated track entry does not exist.
Associating Track with VRRP
About this task
When VRRP is operating in standard mode or load balancing mode, associate the Track module with the VRRP group to implement the following actions:
· Change the priority of a router according to the status of the uplink. If a fault occurs on the uplink of the router, the VRRP group is not aware of the uplink failure. If the router is the master, hosts in the LAN cannot access the external network. To resolve this problem, configure a detection module-Track-VRRP collaboration. The detection module monitors the status of the uplink of the router and notifies the Track module of the detection result.
When the uplink fails, the detection module notifies the Track module to change the status of the monitored track entry to Negative. The priority of the master decreases by a user-specified value. A router with a higher priority in the VRRP group becomes the master.
· Monitor the master on a backup. If a fault occurs on the master, the backup operating in switchover mode will switch to the master immediately to maintain normal communication.
When VRRP is operating in load balancing mode, associate the Track module with the VRRP VF to implement the following functions:
· Change the priority of the AVF according to its uplink state. When the uplink of the AVF fails, the track entry changes to Negative state. The weight of the AVF decreases by a user-specified value. The VF with a higher priority becomes the new AVF to forward packets.
· Monitor the AVF status from the LVF. When the AVF fails, the LVF that is operating in switchover mode becomes the new AVF to ensure continuous forwarding.
For more information about configuring VRRP, see "Configuring VRRP."
Restrictions and guidelines for Track association with VRRP
· VRRP tracking does not take effect on an IP address owner. The configuration takes effect when the router does not act as the IP address owner.
An IP address owner is the router with its interface IP address used as the virtual IP address of the VRRP group.
· When the status of the track entry changes from Negative to Positive or NotReady, the associated router or VF restores its priority automatically.
Associating Track with a VRRP group
1. Enter system view.
system-view
2. Enter interface view.
interface interface-type interface-number
3. Associate a track entry with a VRRP group.
vrrp [ ipv6 ] vrid virtual-router-id track track-entry-number { forwarder-switchover member-ip ip-address | priority reduced [ priority-reduced ] switchover | weight reduced [ weight-reduced ] }
By default, no track entry is associated with a VRRP group.
This command is supported when VRRP is operating in both standard mode and load balancing mode.
Associating Track with a VRRP VF
1. Enter system view.
system-view
2. Enter interface view.
interface interface-type interface-number
3. Associate Track with a VRRP VF.
vrrp [ ipv6 ] vrid virtual-router-id track track-entry-number { forwarder-switchover member-ip ip-address | priority reduced [ priority-reduced ] switchover | weight reduced [ weight-reduced ] }
By default, no track entry is associated with a VRRP VF.
This command is configurable when VRRP is operating in standard mode or load balancing mode. However, the configuration takes effect only when VRRP is operating in load balancing mode.
Associating Track with VSRP
About this task
VSRP determines the availability of the TCP control channel based on the TCP connection state. You can associate the Track module with VSRP to detect the availability of the control channel.
The device does the following based on the state of the track entry:
· When the track entry is in Positive or NotReady state, the device attempts to establish a TCP connection to the peer.
· When the track entry is in Negative state, the device terminates the TCP connection.
For more information about VSRP, see "Configuring VSRP."
Procedure
1. Enter system view.
system-view
2. Create a VSRP peer and enter VSRP peer view.
vsrp peer peer-name
3. Associate VSRP with a track entry.
track track-entry-number
By default, no track entry is associated with VSRP.
Associating Track with static routing
About this task
A static route is a manually configured route to route packets. For more information about static route configuration, see Network Connectivity Configuration Guide.
Static routes cannot adapt to network topology changes. Link failures or network topological changes can make the routes unreachable and cause communication interruption.
To resolve 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.
To check the accessibility of a static route in real time, associate the Track module with the static route.
If you specify the next hop but not the output interface when configuring a static route, you can configure the static routing-Track-detection module collaboration. This collaboration enables you to verify the accessibility of the static route based on the track entry state.
· If the track entry is in Positive state, the following conditions exist:
¡ The next hop of the static route is reachable.
¡ The configured static route is valid.
· If the track entry is in Negative state, the following conditions exist:
¡ The next hop of the static route is not reachable.
¡ The configured static route is invalid.
· If the track entry is in NotReady state, the following conditions exist:
¡ The accessibility of the next hop of the static route is unknown.
¡ The static route is valid.
Restrictions and guidelines
· If a static route needs route recursion, the associated track entry must monitor the next hop of the recursive route. The next hop of the static route cannot be monitored. Otherwise, a valid route might be considered invalid.
Associating Track with an IPv4 static route
1. Enter system view.
system-view
2. Associate an IPv4 static route with a track entry to check the accessibility of the next hop.
ip route-static dest-address { mask-length | mask } { interface-type interface-number [ next-hop-address ] | next-hop-address [ permanent | track track-entry-number ] [ preference preference ] [ tag tag-value ] [ description text ]
By default, Track is not associated with any IPv4 static routes.
For more information about this command, see Network Connectivity Command Reference.
Associating Track with an IPv6 static route
1. Enter system view.
system-view
2. Associate an IPv6 static route with a track entry to check the accessibility of the next hop.
ipv6 route-static ipv6-address prefix-length { interface-type interface-number [ next-hop-address ] track track-entry-number | next-hop-address track track-entry-number } [ preference preference ] [ tag tag-value ] [ description text ]
By default, Track is not associated with any IPv6 static routes.
For more information about this command, see Network Connectivity Command Reference.
Associating Track with PBR
About this task
PBR uses user-defined policies to route packets. You can specify parameters in a PBR policy to guide the forwarding of the packets that match specific criteria. For more information about PBR, see Network Connectivity Configuration Guide.
PBR cannot detect the availability of any action taken on packets. When an action is not available, packets processed by the action might be discarded. For example, if the output interface specified for PBR fails, PBR cannot detect the failure, and continues to forward matching packets out of the interface.
To enable PBR to detect topology changes and improve the flexibility of the PBR application, configure Track-PBR-detection module collaboration.
After you associate a track entry with an apply clause, the detection module associated with the track entry sends Track the detection result of the availability of the tracked object.
· The Positive state of the track entry indicates that the object is available, and the apply clause is valid.
· The Negative state of the track entry indicates that the object is not available, and the apply clause is invalid.
· The NotReady state of the track entry indicates that the apply clause is valid.
The following objects can be associated with a track entry:
· Output interface.
· Next hop.
· Default output interface.
· Default next hop.
Prerequisites for Track association with PBR
Before you associate Track with PBR, create a policy or a policy node, and configure the match criteria.
Associating Track with PBR
1. Enter system view.
system-view
2. Create a policy or policy node and enter PBR policy node view.
policy-based-route policy-name [ deny | permit ] node node-number
3. Define a match criterion.
¡ Define a packet length match criterion.
if-match packet-length min-len max-len
¡ Define an ACL match criterion.
if-match acl { acl-number | name acl-name }
4. Associate Track with PBR.
¡ Set the output interface, and associate it with a track entry.
apply output-interface { interface-type interface-number [ track track-entry-number ] }&<1-n>
By default, no output interface is set.
¡ Set the next hop, and associate it with a track entry.
apply next-hop { ip-address [ direct ] [ track track-entry-number ] }&<1-n>
By default, no next hop is set.
¡ Set the default output interface, and associate it with a track entry.
apply default-output-interface { interface-type interface-number [ track track-entry-number ] }&<1-n>
By default, no default output interface is set.
¡ Set the default next hop, and associate it with a track entry.
apply default-next-hop { ip-address [ direct ] [ track track-entry-number ] }&<1-n>
By default, no default next hop is set.
Associating Track with IPv6 PBR
1. Enter system view.
system-view
2. Create a policy or policy node and enter PBR policy node view.
ipv6 policy-based-route policy-name [ deny | permit ] node node-number
3. Define a match criterion.
¡ Define an IPv6 packet length match criterion.
if-match packet-length min-len max-len
¡ Define an ACL match criterion.
if-match acl { ipv6-acl-number | name ipv6-acl-name }
4. Associate Track with IPv6 PBR.
¡ Set the output interface, and associate it with a track entry.
apply output-interface { interface-type interface-number [ track track-entry-number ] }&<1-n>
By default, no output interface is set.
¡ Set the next hop, and associate it with a track entry.
apply next-hop { ipv6-address [ direct ] [ track track-entry-number ] }&<1-n>
By default, no next hop is set.
¡ Set the default output interface, and associate it with a track entry.
apply default-output-interface { interface-type interface-number [ track track-entry-number ] }&<1-n>
By default, no default output interface is set.
¡ Set the default next hop, and associate it with a track entry.
apply default-next-hop { ipv6-address [ direct ] [ track track-entry-number ] }&<1-n>
By default, no default next hop is set.
Associating Track with EAA
About this task
You can configure EAA track event monitor policies to monitor the positive-to-negative or negative-to-positive state changes of track entries.
· If you specify only one track entry for a policy, EAA triggers the policy when it detects the specified state change on the track entry.
· If you specify multiple track entries for a policy, EAA triggers the policy when it detects the specified state change on the last monitored track entry. For example, if you configure a policy to monitor the positive-to-negative state change of multiple track entries, EAA triggers the policy when the last positive track entry monitored by the policy is changed to the Negative state.
You can set a suppression time for a track event monitor policy. The timer starts when the policy is triggered. The system does not process messages that report the monitored track event until the timer times out.
For more information about EAA, see System Management Configuration Guide.
Procedure
1. Enter system view.
system-view
2. Create a CLI-defined monitor policy and enter its view, or enter the view of an existing CLI-defined monitor policy.
rtm cli-policy policy-name
3. Configure a track event.
event track track-entry-number-list state { negative | positive } [ suppress-time suppress-time ]
By default, a monitor policy does not monitor any track event.
Verifying and maintaining Track
To display track entry information, execute the following command in any view:
display track { track-entry-number | all [ negative | positive ] } [ brief ]
Track configuration examples
Example: Configuring static routing-Track-NQA collaboration
Network configuration
As shown in Figure 3:
· The AC is the default gateway of the hosts in network 20.1.1.0/24.
· Switch C is the default gateway of the hosts in network 30.1.1.0/24.
· Hosts in the two networks communicate with each other through static routes.
To ensure network availability, configure route backup and static routing-Track-NQA collaboration on the AC and Switch C as follows:
· On the AC, assign a higher priority to the static route to 30.1.1.0/24 with next hop Switch A. This route is the master route. The static route to 30.1.1.0/24 with next hop Switch B acts as the backup route. When the master route is unavailable, the backup route takes effect.
· On Switch C, assign a higher priority to the static route to 20.1.1.0/24 with next hop Switch A. This route is the master route. The static route to 20.1.1.0/24 with next hop Switch B acts as the backup route. When the master route is unavailable, the backup route takes effect.
Procedure
1. Create VLANs and assign ports to them. Configure the IP address of each VLAN interface, as shown in Figure 3. (Details not shown.)
2. Configure the AC:
# Configure a static route to 30.1.1.0/24 with next hop 10.1.1.2 and the default priority (60). Associate this static route with track entry 1.
<AC> system-view
[AC] ip route-static 30.1.1.0 24 10.1.1.2 track 1
# Configure a static route to 30.1.1.0/24 with next hop 10.3.1.3 and priority 80.
[AC] ip route-static 30.1.1.0 24 10.3.1.3 preference 80
# Configure a static route to 10.2.1.4 with next hop 10.1.1.2.
[AC] ip route-static 10.2.1.4 24 10.1.1.2
# Create an NQA operation with administrator name admin and operation tag test.
[AC] nqa entry admin test
# Specify the ICMP echo operation type.
[AC-nqa-admin-test] type icmp-echo
# Specify 10.2.1.4 as the destination address of the operation.
[AC-nqa-admin-test-icmp-echo] destination ip 10.2.1.4
# Specify 10.1.1.2 as the next hop of the operation.
[AC-nqa-admin-test-icmp-echo] next-hop ip 10.1.1.2
# Configure the ICMP echo operation to repeat every 100 milliseconds.
[AC-nqa-admin-test-icmp-echo] frequency 100
# Configure reaction entry 1 so that five consecutive probe failures will trigger collaboration with the Track module.
[AC-nqa-admin-test-icmp-echo] reaction 1 checked-element probe-fail threshold-type consecutive 5 action-type trigger-only
[AC-nqa-admin-test-icmp-echo] quit
# Start the NQA operation.
[AC] nqa schedule admin test start-time now lifetime forever
# Configure track entry 1, and associate it with reaction entry 1 of the NQA operation.
[AC] track 1 nqa entry admin test reaction 1
3. Configure Switch A:
# Configure a static route to 30.1.1.0/24 with next hop 10.2.1.4.
<SwitchA> system-view
[SwitchA] ip route-static 30.1.1.0 24 10.2.1.4
# Configure a static route to 20.1.1.0/24 with next hop 10.1.1.1.
[SwitchA] ip route-static 20.1.1.0 24 10.1.1.1
4. Configure Switch B:
# Configure a static route to 30.1.1.0/24 with next hop 10.4.1.4.
<SwitchB> system-view
[SwitchB] ip route-static 30.1.1.0 24 10.4.1.4
# Configure a static route to 20.1.1.0/24 with next hop 10.3.1.1.
[SwitchB] ip route-static 20.1.1.0 24 10.3.1.1
5. Configure Switch C:
# Configure a static route to 20.1.1.0/24 with next hop 10.2.1.2 and the default priority (60). Associate this static route with track entry 1.
<SwitchC> system-view
[SwitchC] ip route-static 20.1.1.0 24 10.2.1.2 track 1
# Configure a static route to 20.1.1.0/24 with next hop 10.4.1.3 and priority 80.
[SwitchC] ip route-static 20.1.1.0 24 10.4.1.3 preference 80
# Configure a static route to 10.1.1.1 with next hop 10.2.1.2.
[SwitchC] ip route-static 10.1.1.1 24 10.2.1.2
# Create an NQA operation with administrator name admin and operation tag test.
[SwitchC] nqa entry admin test
# Specify the ICMP echo operation type.
[SwitchC-nqa-admin-test] type icmp-echo
# Specify 10.1.1.1 as the destination address of the operation.
[SwitchC-nqa-admin-test-icmp-echo] destination ip 10.1.1.1
# Specify 10.2.1.2 as the next hop of the operation.
[SwitchC-nqa-admin-test-icmp-echo] next-hop ip 10.2.1.2
# Configure the ICMP echo operation to repeat every 100 milliseconds.
[SwitchC-nqa-admin-test-icmp-echo] frequency 100
# Configure reaction entry 1 so that five consecutive probe failures will trigger collaboration with the Track module.
[SwitchC-nqa-admin-test-icmp-echo] reaction 1 checked-element probe-fail threshold-type consecutive 5 action-type trigger-only
[SwitchC-nqa-admin-test-icmp-echo] quit
# Start the NQA operation.
[SwitchC] nqa schedule admin test start-time now lifetime forever
# Configure track entry 1, and associate it with reaction entry 1 of the NQA operation.
[SwitchC] track 1 nqa entry admin test reaction 1
Verifying the configuration
# Display information about the track entry on the AC.
[AC] display track all
Track ID: 1
State: Positive
Duration: 0 days 0 hours 0 minutes 32 seconds
Notification delay: Positive 0, Negative 0 (in seconds)
Tracked object:
NQA entry: admin test
Reaction: 1
Remote IP/URL: 10.2.1.4
Local IP:--
Interface:--
The output shows that the status of the track entry is Positive, indicating that the NQA operation has succeeded and the master route is available.
# Display the routing table of the AC.
[AC] display ip routing-table
Destinations : 10 Routes : 10
Destination/Mask Proto Pre Cost NextHop Interface
10.1.1.0/24 Direct 0 0 10.1.1.1 Vlan2
10.1.1.1/32 Direct 0 0 127.0.0.1 InLoop0
10.2.1.0/24 Static 60 0 10.1.1.2 Vlan2
10.3.1.0/24 Direct 0 0 10.3.1.1 Vlan3
10.3.1.1/32 Direct 0 0 127.0.0.1 InLoop0
20.1.1.0/24 Direct 0 0 20.1.1.1 Vlan6
20.1.1.1/32 Direct 0 0 127.0.0.1 InLoop0
30.1.1.0/24 Static 60 0 10.1.1.2 Vlan2
127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0
127.0.0.1/32 Direct 0 0 127.0.0.1 InLoop0
The output shows that the AC forwards packets to 30.1.1.0/24 through Switch A.
# Remove the IP address of VLAN-interface 2 on Switch A.
<SwitchA> system-view
[SwitchA] interface vlan-interface 2
[SwitchA-Vlan-interface2] undo ip address
# Display information about the track entry on the AC
[AC] display track all
Track ID: 1
State: Negative
Duration: 0 days 0 hours 0 minutes 32 seconds
Notification delay: Positive 0, Negative 0 (in seconds)
Tracked object:
NQA entry: admin test
Reaction: 1
Remote IP/URL: 10.2.1.4
Local IP:--
Interface:--
The output shows that the status of the track entry is Negative, indicating that the NQA operation has failed and the master route is unavailable.
# Display the routing table of the AC.
[AC] display ip routing-table
Destinations : 10 Routes : 10
Destination/Mask Proto Pre Cost NextHop Interface
10.1.1.0/24 Direct 0 0 10.1.1.1 Vlan2
10.1.1.1/32 Direct 0 0 127.0.0.1 InLoop0
10.2.1.0/24 Static 60 0 10.1.1.2 Vlan2
10.3.1.0/24 Direct 0 0 10.3.1.1 Vlan3
10.3.1.1/32 Direct 0 0 127.0.0.1 InLoop0
20.1.1.0/24 Direct 0 0 20.1.1.1 Vlan6
20.1.1.1/32 Direct 0 0 127.0.0.1 InLoop0
30.1.1.0/24 Static 80 0 10.3.1.3 Vlan3
127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0
127.0.0.1/32 Direct 0 0 127.0.0.1 InLoop0
The output shows that the AC forwards packets to 30.1.1.0/24 through Switch B. The backup static route has taken effect.
# Verify that hosts in 20.1.1.0/24 can communicate with the hosts in 30.1.1.0/24 when the master route fails.
[AC] ping -a 20.1.1.1 30.1.1.1
Ping 30.1.1.1: 56 data bytes, press CTRL_C to break
Reply from 30.1.1.1: bytes=56 Sequence=1 ttl=254 time=2 ms
Reply from 30.1.1.1: bytes=56 Sequence=2 ttl=254 time=1 ms
Reply from 30.1.1.1: bytes=56 Sequence=3 ttl=254 time=1 ms
Reply from 30.1.1.1: bytes=56 Sequence=4 ttl=254 time=2 ms
Reply from 30.1.1.1: bytes=56 Sequence=5 ttl=254 time=1 ms
--- Ping statistics for 30.1.1.1 ---
5 packet(s) transmitted, 5 packet(s) received, 0.00% packet loss
round-trip min/avg/max/std-dev = 1/1/2/1 ms
# Verify that the hosts in 30.1.1.0/24 can communicate with the hosts in 20.1.1.0/24 when the master route fails.
[SwitchA] ping -a 30.1.1.1 20.1.1.1
Ping 20.1.1.1: 56 data bytes, press CTRL_C to break
Reply from 20.1.1.1: bytes=56 Sequence=1 ttl=254 time=2 ms
Reply from 20.1.1.1: bytes=56 Sequence=2 ttl=254 time=1 ms
Reply from 20.1.1.1: bytes=56 Sequence=3 ttl=254 time=1 ms
Reply from 20.1.1.1: bytes=56 Sequence=4 ttl=254 time=1 ms
Reply from 20.1.1.1: bytes=56 Sequence=5 ttl=254 time=1 ms
--- Ping statistics for 20.1.1.1 ---
5 packet(s) transmitted, 5 packet(s) received, 0.00% packet loss
round-trip min/avg/max/std-dev = 1/1/2/1 ms
