Login
- Table of Contents
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 14-MTR configuration | 61.22 KB |
Configuring MTR
Overview
Multi-Topology Routing (MTR) splits a base topology into multiple topologies, which intersect or overlap with one another. Route calculation is performed on a per-topology basis.
For example, IS-IS MTR enables IS-IS to perform separate route calculation for the IPv4 and IPv6 topologies in an IS-IS routing domain.
Work mechanism
Figure 1 Work mechanism of MTR
As shown in Figure 1, the base topology is split into two topologies, topology A and topology B. You can forward voice traffic through topology A and video traffic through topology B.
Router B does not belong to topology A. In topology B, no direct link exists between Router A and Router D, or between Router B and Router C. Route calculation and traffic forwarding are performed in each topology independently.
Supported features
· IS-IS MTR. For more information, see "Configuring IS-IS" and "Configuring IPv6 IS-IS."
· Static routing MTR. For more information, see "Configuring static routing."
Configuring MTR
MTR classifies traffic by MTR policy. An MTR policy uses ACL, DSCP, and IP precedence as the match criteria.
An MTR policy can contain multiple nodes, which are in a logical OR relationship. A node with a smaller number is matched first. A packet that matches one node matches the MTR policy.
Each node contains a set of if-match and apply clauses.
· if-match—Defines a criterion to match packet attributes. The if-match clauses of a node are in an OR relationship. If a packet matches one of the if-match clauses, it matches the node.
· apply—Specifies a topology for packets matching the MTR policy node.
|
|
IMPORTANT: A node must contain both if-match and apply clauses. Otherwise, the topology configuration cannot take effect. |
To configure MTR:
|
Step |
Command |
Remarks |
|
1. Enter system view. |
system-view |
N/A |
|
2. Create the global address family and enter its view. |
global-address-family ipv4 [ unicast ] |
By default, no global address family exists. |
|
3. Create a topology and enter its view. |
topology topo-name |
By default, no topologies exist. |
|
4. (Optional.) Configure the maximum number of active routes supported by the topology. |
routing-table limit number { warn-threshold | simply-alert } |
N/A |
|
5. Return to system view. |
quit |
N/A |
|
6. Enter interface view. |
interface interface-type interface-number |
N/A |
|
7. Associate the interface with a topology and enter IPv4 unicast topology view of the interface. |
topology ipv4 [ unicast ] topo-name |
By default, the interface is not associated with any topology. |
|
8. Return to system view. |
quit |
N/A |
|
9. Create an MTR policy node and enter its view. |
mtr-policy policy-name node node-value |
By default, no MTR policy node is created. |
|
10. Specify a topology for the MTR policy node. |
apply topology topo-name |
By default, no topology is specified for the MTR policy node. |
|
11. Configure the match criteria. |
· Configure an ACL match criterion: · Configure a DSCP match criterion: · Configure an IP precedence match criterion: |
By default, no match criterion is configured. |
|
12. Return to system view. |
quit |
N/A |
|
13. Enter global address family view. |
global-address-family ipv4 [ unicast ] |
N/A |
|
14. Enable the MTR policy. |
topology-routing mtr-policy policy-name |
By default, the MTR policy is disabled. |
Displaying and maintaining MTR
Execute display commands in any view.
|
Command |
|
|
Display topology information. |
display topology [ name topo-name ] |
|
Display MTR policy information. |
display mtr-policy [ name mtr-policy-name ] |
