Login
- Table of Contents
-
- H3C WX6103 Access Controller Switch Interface Board Configuration Guide-6W102
- 00-Preface
- 01-Login Configuration
- 02-VLAN Configuration
- 03-IP Addressing and IP Performance Configuration
- 04-QinQ-BPDU Tunneling Configuration
- 05-Port Correlation Configuration
- 06-Link Aggregation Configuration
- 07-MAC Address Table Management Configuration
- 08-Port Security Configuration
- 09-MSTP Configuration
- 10-IP Routing-GR Overview Configuration
- 11-IPv4 Routing Configuration
- 12-IP Source Guard Configuration
- 13-DLDP Configuration
- 14-Multicast Configuration
- 15-LLDP Configuration
- 16-sFlow Configuration
- 17-ARP Configuration
- 18-DHCP Configuration
- 19-ACL Configuration
- 20-QoS Configuration
- 21-Port Mirroring Configuration
- 22-UDP Helper Configuration
- 23-SNMP-RMON Configuration
- 24-NTP Configuration
- 25-DNS Configuration
- 26-File System Management Configuration
- 27-Information Center Configuration
- 28-System Maintaining and Debugging Configuration
- 29-NQA Configuration
- 30-SSH Configuration
- 31-SSL-HTTPS Configuration
- 32-PKI Configuration
- 33-Track Configuration
- 34-Acronyms
- 35-Index
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 33-Track Configuration | 74.38 KB |
Table of Contents
Collaboration Between the Track Module and the Detection Modules
Collaboration Between the Track Module and the Application Modules
Configuring Collaboration Between the Track Module and the Detection Modules
Configuring Track-NQA Collaboration
Configuring Collaboration Between the Track Module and the Application Modules
Configuring Track-Static Routing Collaboration
Displaying and Maintaining Track Object(s)
Static Routing-Track-NQA Collaboration Configuration Example
The term switch in this document refers to a switch in a generic sense or an access controller configured with the switching function unless otherwise specified.
When configuring Track, go to these sections for information you are interested in:
l Track Configuration Task List
l Configuring Collaboration Between the Track Module and the Detection Modules
l Configuring Collaboration Between the Track Module and the Application Modules
l Displaying and Maintaining Track Object(s)
Track Overview
Figure 1-1 Collaboration through the Track module
The Track module is used to implement collaboration between different modules.
The collaboration here involves three parts: the application modules, the Track module, and the detection modules. These modules collaborate with one another through collaboration objects. That is, the detection modules trigger the application modules to perform certain operations through the Track module. More specifically, the detection modules probe the link status, network performance and so on, and inform the application modules of the detection result through the Track module. After the application modules are aware of the changes of network status, they deal with the changes accordingly to avoid communication interruption and network performance degradation.
The Track module works between the application modules and the detection modules and is mainly used to obscure the difference of various detection modules to provide a unified interface for application modules.
Collaboration Between the Track Module and the Detection Modules
You can establish the collaboration between the Track module and the detection modules through configuration. A detection module probes the link status and informs the Track module of the probe result. The Track module then changes the status of the Track object accordingly:
l If the probe succeeds, the status of the corresponding Track object is Positive;
l If the probe fails, the status of the corresponding Track object is Negative.
At present, the detection modules that can collaborate with the Track module include the Network Quality Analyzer (NQA) only. Refer to NQA in H3C WX6103 Access Controller Switch Interface Board Configuration Guide for details of NQA.
Collaboration Between the Track Module and the Application Modules
You can establish the collaboration between the Track module and the application modules through configuration. If the status of the Track object changes, the Track module tells the application modules to deal with the change accordingly.
At present, the application modules that can collaborate with the Track module include:
l Static routing
Track Configuration Task List
To implement the collaboration function, you need to establish collaboration between the Track module and the detection modules, and between the Track module and the application modules.
Complete these tasks to configure Track module:
|
Task |
Remarks |
|
|
Configuring Collaboration Between the Track Module and the Detection Modules |
Required |
|
|
Configuring Collaboration Between the Track Module and the Application Modules |
Required |
|
Configuring Collaboration Between the Track Module and the Detection Modules
Configuring Track-NQA Collaboration
Through the following configuration, you can establish the collaboration between the Track module and the NQA, which probes the link status and informs the Track module of the probe result.
Follow these steps to configure Track-NQA collaboration:
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
— |
|
Create a Track object and associate it with the specified Reaction entry of the NQA test group |
track track-entry-number nqa entry admin-name operation-tag reaction item-num |
Required No Track object is created by default. |
When you configure a Track object, the specified NQA test group and Reaction entry can be nonexistent. In this case, the status of the configured Track object is Invalid.
Configuring Collaboration Between the Track Module and the Application Modules
Configuring Track-Static Routing Collaboration
You can check the validity of a static route in real time by establishing collaboration between Track and static routing.
If you specify the next hop but not the egress interface when configuring a static route, you can associate the static route with a Track object and thus check the validity of the static route according to the status of the Track object.
l If the status of the Track object is Positive, then the next hop of the static route is reachable, and the configured static route is valid.
l If the status of the Track object is Negative, then the next hop of the static route is unreachable, and the configured static route is invalid.
Follow these steps to configure the Track-Static Routing collaboration:
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
— |
|
Configure the Track-Static Routing collaboration, so as to check the reachability of the next hop of the static route |
ip route-static dest-address { mask | mask-length } next-hop-address track track-entry-number [ preference preference-value ] [ tag tag-value ] [ description description-text ] |
Required Not configured by default. |
l 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 object are associated directly; for a nonexistent static route, the system creates the static route and then associates it with the specified Track object.
l The Track object to be associated with the static route can be a nonexistent one. After you use the track command to create the Track object, the association takes effect.
l If a static route needs route recursion, the associated Track object must monitor the next hop of the recursive route instead of that of the static route; otherwise, a valid route may be considered invalid.
l For details of static route configuration, refer to the Static Routing Configuration part in IPv4 Routing in H3C WX6103 Access Controller Switch Interface Board Configuration Guide.
Displaying and Maintaining Track Object(s)
|
To do… |
Use the command… |
Remarks |
|
Display information about the specified Track object or all Track objects |
display track { track-entry-number | all } |
Available in any view |
Track Configuration Example
Static Routing-Track-NQA Collaboration Configuration Example
Network requirements
l The next hop of the static route from access controller (AC) A to Switch is AC B.
l Configure Static Routing-Track-NQA collaboration on AC A to implement real-time monitoring of the validity of the static route to Switch.
Network diagram
Figure 1-2 Network diagram for Static Routing-Track-NQA collaboration configuration
Configuration procedure
1) Configure the IP address of each interface as shown in Figure 1-2.
2) Configure a static route on AC A and associate it with the Track object.
# Configure the address of the next hop of the static route to Switch as 10.2.1.1, and configure the static route to associate with Track object 1.
<ACA> system-view
[ACA] ip route-static 10.1.1.2 24 10.2.1.1 track 1
3) Configure an NQA test group on AC A.
# Create an NQA test group with the administrator admin and the operation tag test.
[ACA] nqa entry admin test
# Configure the test type as ICMP-echo.
[ACA-nqa-admin-test] type icmp-echo
# Configure the destination address as 10.2.1.1
[ACA-nqa-admin-test-icmp-echo] destination ip 10.2.1.1
# Configure the test frequency as 100 ms.
[ACA-nqa-admin-test-icmp-echo] frequency 100
# Configure Reaction entry 1, specifying that five consecutive probe failures trigger the Static Routing-Track-NQA collaboration.
[ACA-nqa-admin-test-icmp-echo] reaction 1 checked-element probe-fail threshold-type consecutive 5 action-type trigger-only
[ACA-nqa-admin-test-icmp-echo] quit
# Start NQA probes.
[SwitchA] nqa schedule admin test start-time now lifetime forever
4) Configure a Track object on AC A.
# Configure Track object 1, and associate it with Reaction entry 1 of the NQA test group (with the administrator admin, and the operation tag test).
[ACA] track 1 nqa entry admin test reaction 1
5) Verify the configuration
# Display information of the Track object on AC A.
[ACA] display track all
Track ID: 1
Status: Positive
Reference object:
NQA entry: admin test
Reaction: 1
# Display the routing table of Switch.
[Switch] display ip routing-table
Routing Tables: Public
Destinations : 5 Routes : 5
Destination/Mask Proto Pre Cost NextHop Interface
10.1.1.0/24 Static 60 0 10.2.1.1 Vlan3
10.2.1.0/24 Direct 0 0 10.2.1.2 Vlan3
10.2.1.2/32 Direct 0 0 127.0.0.1 InLoop0
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 information above indicates the NQA test result, that is, the next hop 10.2.1.1 is reachable (the status of the Track object is Positive), and the configured static route is valid.
# Remove the IP address of interface VLAN-interface 3 on AC B.
<ACB> system-view
[ACB] interface vlan-interface 3
[ACB-Vlan-interface3] undo ip address
# Display information of the Track object on AC A.
[ACA] display track all
Track ID: 1
Status: Negative
Reference object:
NQA entry: admin test
Reaction: 1
# Display the routing table of AC A.
[ACA] display ip routing-table
Routing Tables: Public
Destinations : 4 Routes : 4
Destination/Mask Proto Pre Cost NextHop Interface
10.2.1.0/24 Direct 0 0 10.2.1.2 Vlan3
10.2.1.2/32 Direct 0 0 127.0.0.1 InLoop0
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 information above indicates the NQA test result, that is, the next hop 10.2.1.1 is unreachable (the status of the Track object is Negative), and the configured static route is invalid.
