Table of Contents

Chapter 1 Track Configuration. 1-1

1.1 Track Overview. 1-1

1.1.1 Collaboration Between the Track Module and the Detection Modules. 1-2

1.1.2 Collaboration Between the Track Module and the Application Modules. 1-2

1.2 Track Configuration Task List 1-2

1.3 Configuring Collaboration Between the Track Module and the Detection Modules. 1-3

1.3.1 Configuring Track-NQA Collaboration. 1-3

1.4 Configuring Collaboration Between the Track Module and the Application Modules. 1-3

1.4.1 Configuring Track-Static Routing Collaboration. 1-3

1.5 Displaying and Maintaining Track Object(s) 1-4

1.6 Track Configuration Example. 1-4

1.6.1 Static Routing-Track-NQA Collaboration Configuration Example. 1-4

 

Chapter 1  Track Configuration

When configuring Track, go to these sections for information you are interested in:

l           Track Overview

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)

l           Track Configuration Example

1.1  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.

1.1.1  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 Configuration for details of NQA.

1.1.2  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

1.2  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	Configuring Track-NQA Collaboration	Required
Configuring Collaboration Between the Track Module and the Application Modules	Configuring Track-Static Routing Collaboration	Required

 

1.3  Configuring Collaboration Between the Track Module and the Detection Modules

1.3.1  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.

 

 

1.4  Configuring Collaboration Between the Track Module and the Application Modules

1.4.1  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.

 

 

1.5  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

 

1.6  Track Configuration Example

1.6.1  Static Routing-Track-NQA Collaboration Configuration Example

I. Network requirements

l           The next hop of the static route from Switch A to Switch C is Switch B.

l           Configure Static Routing-Track-NQA collaboration on Switch A to implement real-time monitoring of the validity of the static route to Switch C.

II. Network diagram

Figure 1-2 Network diagram for Static Routing-Track-NQA collaboration configuration (on switches)

III. Configuration procedure

1)         Configure the IP address of each interface as shown in Figure 1-2.

2)         Configure a static route on Switch A and associate it with the Track object.

# Configure the address of the next hop of the static route to Switch C as 10.2.1.1, and configure the static route to associate with Track object 1.

<SwitchA> system-view

[SwitchA] ip route-static 10.1.1.2 24 10.2.1.1 track 1

3)         Configure an NQA test group on Switch A.

# Create an NQA test group with the administrator admin and the operation tag test.

[SwitchA] nqa entry admin test

# Configure the test type as ICMP-echo.

[SwitchA-nqa-admin-test] type icmp-echo

# Configure the destination address as 10.2.1.1

[SwitchA-nqa-admin-test-icmp-echo] destination ip 10.2.1.1

# Configure the test frequency as 100 ms.

[SwitchA-nqa-admin-test-icmp-echo] frequency 100

# Configure Reaction entry 1, specifying that five consecutive probe failures trigger the Static Routing-Track-NQA collaboration.

[SwitchA-nqa-admin-test-icmp-echo] reaction 1 checked-element probe-fail threshold-type consecutive 5 action-type trigger-only

[SwitchA-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 Switch 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).

[SwitchA] track 1 nqa entry admin test reaction 1

5)         Verify the configuration

# Display information of the Track object on Switch A.

[SwitchA] display track all

Track ID: 1

  Status: Positive

  Reference object:

    NQA entry: admin test

    Reaction: 1

# Display the routing table of Switch A.

[SwitchA] 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 Switch B.

<SwitchB> system-view

[SwitchB] interface vlan-interface 3

[SwitchB-Vlan-interface3] undo ip address

# Display information of the Track object on Switch A.

[SwitchA] display track all

Track ID: 1

  Status: Negative

  Reference object:

    NQA entry: admin test

        Reaction: 1

# Display the routing table of Switch A.

[SwitchA] 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.