IP routing directs IP packet forwarding on routers. Based on the destination IP address in the packet, a router looks up a route for the packet in a routing table and forwards the packet to the next hop. Routes are path information used to direct IP packets.

Routing table

A RIB contains the global routing information and related information, including route recursion, route redistribution, and route extension information. The router selects optimal routes from the routing table and puts them into the FIB table. It uses the FIB table to forward packets. For more information about the FIB table, see Layer 3—IP Services Configuration Guide.

Route categories

Table 1 categorizes routes by different criteria.

Table 1 Route categories

Criterion	Categories
Origin	· Direct route—A direct route is discovered by the data link protocol on an interface, and is also called an interface route. · Static route—A static route is manually configured by an administrator. · Dynamic route—A dynamic route is dynamically discovered by a routing protocol.
Destination	· Network route—The destination is a network. The subnet mask is less than 32 bits. · Host route—The destination is a host. The subnet mask is 32 bits.
Whether the destination is directly connected	· Direct route—The destination is directly connected. · Indirect route—The destination is indirectly connected.

Dynamic routing protocols

Static routes work well in small, stable networks. They are easy to configure and require fewer system resources. However, in networks where topology changes occur frequently, a typical practice is to configure a dynamic routing protocol. Compared with static routing, a dynamic routing protocol is complicated to configure, requires more router resources, and consumes more network resources.

Dynamic routing protocols dynamically collect and report reachability information to adapt to topology changes. They are suitable for large networks.

Dynamic routing protocols can be classified by different criteria, as shown in Table 2.

Table 2 Categories of dynamic routing protocols

Criterion	Categories
Operation scope	· IGPs—Interior gateway protocols, which run within an autonomous system (AS). Examples include RIP, OSPF, and IS-IS. · EGPs—Exterior gateway protocols, which run between ASs. The most popular EGP is BGP.
Routing algorithm	· Distance-vector protocols—Examples include RIP and BGP. BGP is also considered a path-vector protocol. · Link-state protocols—Examples include OSPF and IS-IS.
Destination address type	· Unicast routing protocols—Examples include RIP, OSPF, BGP, and IS-IS. · Multicast routing protocols—Examples include PIM-SM and PIM-DM.
IP version	· IPv4 routing protocols—Examples include RIP, OSPF, BGP, and IS-IS. · IPv6 routing protocols—Examples include RIPng, OSPFv3, IPv6 BGP, and IPv6 IS-IS.

An AS refers to a group of routers that use the same routing policy and work under the same administration.

Route preference

Routing protocols, including static and direct routing, each by default have a preference. If they find multiple routes to the same destination, the router selects the route with the highest preference as the optimal route.

The preference of a direct route is always 0 and cannot be changed. You can configure a preference for each static route and each dynamic routing protocol. The following table lists the route types and default preferences. The smaller the value, the higher the preference.

Table 3 Route types and default route preferences

Route type	Preference
Direct route	0
Multicast static route	1
OSPF	10
IS-IS	15
Unicast static route	60
RIP	100
OSPF ASE	150
OSPF NSSA	150
IBGP	255
EBGP	255
Unknown (route from an untrusted source)	256

Load sharing

A routing protocol might find multiple optimal equal-cost routes to the same destination. You can use these routes to implement equal-cost multi-path (ECMP) load sharing.

ECMP load sharing is available for the following routing protocols:

· Static routing.

· RIP and RIPng.

· OSPF and OSPFv3.

· BGP and IPv6 BGP.

· IS-IS and IPv6 IS-IS.

Route backup

Route backup can improve network availability. Among multiple routes to the same destination, the route with the highest priority is the primary route and others are secondary routes.

The router forwards matching packets through the primary route. When the primary route fails, the route with the highest preference among the secondary routes is selected to forward packets. When the primary route recovers, the router uses it to forward packets.

Route recursion

To use a BGP, static, or RIP route that has an indirectly connected next hop, a router must perform route recursion to find the output interface to reach the next hop.

Link-state routing protocols, such as OSPF and IS-IS, do not need route recursion, because they obtain directly connected next hops through route calculation.

The RIB records and saves route recursion information, including brief information about related routes, recursive paths, and recursion depth.

Route redistribution

Route redistribution enables routing protocols to learn routing information from each other. A dynamic routing protocol can redistribute routes from other routing protocols, including direct and static routing. For more information, see the respective chapters on those routing protocols in this configuration guide.

The RIB records redistribution relationships of routing protocols.

Extension attribute redistribution

Extension attribute redistribution enables routing protocols to learn route extension attributes from each other, including BGP extended community attributes, OSPF area IDs, route types, and router IDs.

The RIB records extended attributes of each routing protocol and redistribution relationships of different routing protocol extended attributes.

Configuring load sharing

Configuring load sharing mode

About this task

Load sharing can be implemented on a per-flow basis or per-packet basis.

In the per-flow load sharing mode, the device forwards flows over equal-cost routes. Packets of one flow travel along the same routes. You can configure the device to identify a flow based on the following criteria: source IP address, destination IP address, source port number, destination port number, and IP protocol number.

In a complex network, when the criteria cannot distinguish flows, you can use the algorithm keyword to specify an algorithm to identify flows.

Procedure

1. Enter system view.

system-view

2. Configure load sharing.

ip load-sharing mode { per-flow [ algorithm algorithm-number [ seed seed-number ] | [ dest-ip | dest-port | flow-label | ingress-port | ip-pro | src-ip | src-port ] * ] | per-packet } { global | slot slot-number }

By default, the device performs per-flow load sharing based on the destination IP address and source IP address.

Enabling IPv4 bandwidth-based load sharing

About this task

This feature load shares flow traffic among multiple output interfaces based on their load percentages. The device calculates the load percentage for each output interface in terms of the interface expected bandwidth.

Devices that run load sharing protocols, such as Locator/ID Separation Protocol (LISP), implement load sharing based on the ratios defined by these protocols.

Procedure

1. Enter system view.

system-view

2. Enable IPv4 bandwidth-based load sharing.

bandwidth-based-sharing

By default, the IPv4 bandwidth-based load sharing is disabled.

3. (Optional.) Configure the expected bandwidth of the interface.

a. Enter interface view.

interface interface-type interface-number

b. Configure the expected bandwidth of the interface.

bandwidth bandwidth

By default, the expected bandwidth is the physical bandwidth of the interface.

Enabling local-first load sharing

About this task

Local-first load sharing distributes traffic preferentially across the output interfaces on the receiving IRF member device if output interfaces for multiple equal-cost routes are on different members. This feature enhances packets forwarding efficiency.

Procedure

1. Enter system view.

system-view

2. Enable local-first load sharing.

ip load-sharing local-first enable

By default, local-first load sharing is enabled.

Enabling symmetric load sharing

About this task

Symmetric load sharing ensures that bidirectional traffic specific to a source and destination address pair flow along the same path.

Procedure

1. Enter system view.

system-view

2. Enable symmetric load sharing.

ip load-sharing symmetric enable

By default, symmetric load sharing is disabled.

Verifying and maintaining load sharing

Perform display tasks in any view.

· Display the load sharing mode in use.

display ip load-sharing mode slot slot-number

· Display the load sharing path selected for a flow.

display ip load-sharing path ingress-port interface-type interface-number packet-format { ipv4oe dest-ip ip-address [ src-ip ip-address ] | ipv6oe dest-ipv6 ipv6-address [ src-ipv6 ipv6-address | flow-label flow-label ]} [ dest-port port-id | ip-pro protocol-id | src-port port-id | vpn-instance vpn-instance-name ] *

Setting the maximum lifetime for routes and labels in the RIB

About this task

Perform this task to prevent routes of a certain protocol from being aged out due to slow protocol convergence resulting from a large number of route entries or long GR period.

Restrictions and guidelines

The configuration takes effect at the next protocol or RIB process switchover.

Procedure (IPv4)

1. Enter system view.

system-view

2. Enter RIB view.

rib

3. Create the RIB IPv4 address family and enter its view.

address-family ipv4

4. Set the maximum lifetime for IPv4 routes and labels in the RIB.

protocol protocol [ instance instance-name ] lifetime seconds

By default, the maximum lifetime for routes and labels in the RIB is 900 seconds.

Procedure (IPv6)

1. Enter system view.

system-view

2. Enter RIB view.

rib

3. Create the RIB IPv6 address family and enter its view.

address-family ipv6

4. Set the maximum lifetime for IPv6 routes and labels in the RIB.

protocol protocol [ instance instance-name ] lifetime seconds

By default, the maximum lifetime for routes and labels in the RIB is 900 seconds.

Setting the maximum lifetime for routes in the FIB

About this task

When GR or NSR is disabled, FIB entries must be retained for some time after a protocol process switchover or RIB process switchover. When GR or NSR is enabled, FIB entries must be removed immediately after a protocol or RIB process switchover to avoid routing issues. Perform this task to meet such requirements.

Procedure (IPv4)

1. Enter system view.

system-view

2. Enter RIB view.

rib

3. Create the RIB IPv4 address family and enter its view.

address-family ipv4

4. Set the maximum lifetime for IPv4 routes in the FIB.

fib lifetime seconds

By default, the maximum lifetime for routes in the FIB is 600 seconds.

Procedure (IPv6)

1. Enter system view.

system-view

2. Enter RIB view.

rib

3. Create the RIB IPv6 address family and enter its view.

address-family ipv6

4. Set the maximum lifetime for IPv6 routes in the FIB.

fib lifetime seconds

By default, the maximum lifetime for routes in the FIB is 600 seconds.

Enabling the RIB to flush route attribute information to the FIB

1. Enter system view.

system-view

2. Enter RIB view.

rib

3. Create the RIB IPv4 address family and enter its view.

address-family ipv4

4. Enable the RIB to flush route attribute information to the FIB.

flush route-attribute protocol

By default, the RIB does not flush route attribute information to the FIB.

Setting the maximum number of ECMP routes

Restrictions and guidelines

This configuration takes effect at reboot. Make sure the reboot does not impact your network.

Procedure (IPv4)

1. Enter system view.

system-view

2. Set the maximum number of ECMP routes.

max-ecmp-num number

By default, the maximum number of ECMP routes is determined by the maximum number of ECMP routes supported by the system.

Procedure (IPv6)

1. Enter system view.

system-view

2. Set the maximum number of ECMP routes.

ipv6 max-ecmp-num number

By default, the maximum number of ECMP routes is determined by the maximum number of ECMP routes supported by the system.

Enabling the enhanced ECMP mode

About enhanced ECMP mode

When one or multiple ECMP routes fail, the default ECMP mode enables the device to reallocate all traffic to the remaining routes.

The enhanced ECMP mode enables the device to reallocate only the traffic of the failed routes to the remaining routes, which ensures forwarding continuity.

Restrictions and guidelines for enabling the enhanced ECMP mode

This configuration takes effect at reboot. Make sure the reboot does not impact your network.

Enabling the IPv4 and IPv6 enhanced ECMP mode

1. Enter system view.

system-view

2. Enable the IPv4 and IPv6 enhanced ECMP mode.

ecmp mode enhanced

By default, the IPv4 and IPv6 enhanced ECMP mode is disabled.

Configuring RIB NSR

About this task

When an active/standby switchover occurs, nonstop routing (NSR) backs up routing information from the active process to the standby process to avoid routing flapping and ensure forwarding continuity.

RIB NSR provides faster route convergence than protocol NSR during an active/standby switchover.

Prerequisites for RIB NSR

Use this feature with protocol GR or NSR to avoid route timeouts and traffic interruption.

Procedure (IPv4)

1. Enter system view.

system-view

2. Enter RIB view.

rib

3. Create the RIB IPv4 address family and enter its view.

address-family ipv4

4. Enable IPv4 RIB NSR.

non-stop-routing

By default, RIB NSR is disabled.

Procedure (IPv6)

1. Enter system view.

system-view

2. Enter RIB view.

rib

3. Create the RIB IPv6 address family and enter its view.

address-family ipv6

4. Enable IPv6 RIB NSR.

non-stop-routing

By default, RIB NSR is disabled.

Configuring inter-protocol FRR

About this task

Inter-protocol fast reroute (FRR) is applicable to services that are sensitive to packet loss and latency. This feature enables fast rerouting between routes of different protocols. A backup next hop is automatically selected to reduce the service interruption time caused by unreachable next hops. When the next hop of the primary link fails, the traffic is redirected to the backup next hop.

Among the routes to the same destination in the RIB, a router adds the route with the highest preference to the FIB table. After you configure this feature, the device selects a route of another routing protocol as the backup route. When the next hop of the primary route is unreachable, the device forwards packets through the backup route.

Restrictions and guidelines for inter-protocol FRR

This feature uses the next hop of a route from a different protocol as the backup next hop, which might cause loops.

If you configure both inter-protocol FRR and protocol-specific FRR, protocol-specific FRR takes effect.

Procedure (IPv4)

1. Enter system view.

system-view

2. Enter RIB view.

rib

3. Create the RIB IPv4 address family and enter its view.

address-family ipv4

4. Enable IPv4 RIB inter-protocol FRR.

inter-protocol fast-reroute [ vpn-instance vpn-instance-name ]

By default, inter-protocol FRR is disabled.

If you do not specify a VPN instance, inter-protocol FRR is enabled for the public network.

Procedure (IPv6)

1. Enter system view.

system-view

2. Enter RIB view.

rib

3. Create the RIB IPv6 address family and enter its view.

address-family ipv6

4. Enable IPv6 RIB inter-protocol FRR.

inter-protocol fast-reroute [ vpn-instance vpn-instance-name ]

By default, inter-protocol FRR is disabled.

If you do not specify a VPN instance, inter-protocol FRR is enabled for the public network.

Configuring BFD for primary route next hop availability detection

About configuring BFD for primary route next hop availability detection

This feature uses BFD to detect the availability of the primary route next hop for inter-protocol FRR or ECMP routes. When the primary route next hop unreachable, this feature enables the upper layer routing protocol to reallocate service traffic to the backup next hops or to the remaining ECMP next hops.

For inter-protocol FRR, the primary route is the route with the highest preference among the routes to the same destination. If BFD detects that the next hop of the primary route is unreachable, it notifies the FIB of the issue. The FIB will use the backup next hops to guide traffic forwarding.

For ECMP routes of a routing protocol, the primary route is each ECMP route. If BFD detects that the next hop of an ECMP route is unreachable, it notifies the routing protocol of the issue. The routing protocol will reallocate the service traffic to the remaining ECMP next hops. When BFD detects that the next hops of all ECMP routes are invalid, BFD notifies the routing protocol to withdraw the routes. In addition, the device reselects optimal routes for the service traffic.

For more information about BFD, see High Availability Configuration Guide.

Restrictions and guidelines for configuring BFD for primary link availability detection

This feature takes effect and automatically creates a BFD session only when the primary route exists and a backup next hop is generated for it.

If you specify the ecmp-shared keyword when configuring FRR for a routing protocol, the device will use the LFA algorithm to calculate backup next hops for each ECMP route. The routes destined for the backup next hops are also added to the routing table as ECMP routes and the state of these routes is backup. BFD does not detect these backup ECMP routes.

Configuring BFD control packet mode

About this task

This mode uses BFD control packets to detect the status of a link bidirectionally at a millisecond level.

Restrictions and guidelines for BFD control packet mode

A control-packet-mode BFD session can be successfully established through negotiation between the two ends. To use a control-packet-mode BFD session to detect the primary route next hop availability, you must create a static BFD session that meets the following requirements on the next hop device:

· Create a single-hop BFD session in control packet mode.

· The source IP address of the BFD session is the destination IP address of the BFD session automatically created by the local end.

· The destination IP address of the BFD session is the source IP address of the BFD session automatically created by the local end.

· The remote discriminator of the BFD session is the local discriminator of the BFD session automatically created by the local end.

The local device can use a control-packet-mode BFD session to detect the primary route next hop only after you create the static BFD session on the primary route next hop device.

Procedure

1. Enter system view.

system-view

2. Enter RIB view.

rib

3. Create RIB IPv4 or IPv6 address family view and enter the view.

IPv4:

address-family ipv4

IPv6:

address-family ipv6

4. Enable BFD for primary link availability detection.

primary-path-detect bfd ctrl [ inter-protocol-frr | protocol-ecmp protocol ]

By default, BFD is disabled for primary link availability detection.

Configuring BFD echo packet mode

About this task

With BFD echo packet mode enabled, the output interface sends BFD echo packets to the destination device, and the device sends the packets back to test the link reachability.

Restrictions and guidelines

You do not need to configure BFD echo packet mode at the peer end.

Procedure

1. Enter system view.

system-view

2. (Optional.) Configure the source IP address of echo packets.

IPv4:

bfd echo-source-ip ip-address

By default, the source IPv4 address of echo packets is not configured.

As a best practice to avoid network congestion caused by excessive ICMP redirect packets from the peer, use this command. Make sure the source IPv4 address is not on the subnet of any interfaces on the device.

For more information about this command, see BFD in High Availability Command Reference.

IPv6:

bfd echo-source-ipv6 ipv6-address

By default, the source IPv6 address of echo packets is not configured.

As a best practice to avoid network congestion caused by excessive ICMPv6 redirect packets from the peer, use this command. Make sure the source IPv6 address is not on the subnet of any interfaces on the device.

You must specify a global unicast address as the source IPv6 address of BFD echo packets.

For more information about this command, see BFD in High Availability Command Reference.

3. Enter RIB view.

rib

4. Create RIB IPv4 or IPv6 address family view and enter the view.

IPv4:

address-family ipv4

IPv6:

address-family ipv6

5. Enable BFD for primary link availability detection.

primary-path-detect bfd echo [ inter-protocol-frr | protocol-ecmp protocol ]

By default, BFD is disabled for primary link availability detection.

Associating the direct routes on an interface with a track entry

About this task

Perform this task to associate the direct routes on an interface with a track entry to change the cost of the direct routes according to the track entry state.

· If the track entry does not exist or the track entry is in NotReady or Positive state, the cost of the direct routes changes to 0.

· If the track entry is in Negative state, the cost of the direct routes changes to the value configured by using the route-direct track or ipv6 route-direct track command.

For more information about associating the direct routes on an interface with a track entry, see Track configuration in High Availability Configuration Guide.

Procedure (IPv4)

1. Enter system view.

system-view

2. Enter interface view.

interface interface-type interface-number

3. Associate the IPv4 direct routes on the interface with a track entry and apply the specified cost value to the IPv4 direct routes after the track entry changes to Negative state.

route-direct track track-entry-number degrade-cost cost-value

By default, the IPv4 direct routes on an interface are not associated with a track entry.

To change the track entry associated with the IPv4 direct routes on an interface, you must first execute the undo route-direct track command to remove the original association.

Procedure (IPv6)

1. Enter system view.

system-view

2. Enter interface view.

interface interface-type interface-number

3. Associate the IPv6 direct routes on the interface with a track entry and apply the specified cost value to the IPv6 direct routes after the track entry changes to Negative state.

ipv6 route-direct track track-entry-number degrade-cost cost-value

By default, the IPv6 direct routes on an interface are not associated with a track entry.

To change the track entry associated with the IPv6 direct routes on an interface, you must first execute the undo ipv6 route-direct track command to remove the original association.

Enabling route fast switchover

About this task

This feature applies to a device that provides the same physical output interface for large numbers of routes, including ECMP routes and primary/secondary routes. When a link failure occurs on the interface, the device must perform the following tasks before switching the traffic to another route:

1. Deletes all ARP or ND entries for the link.

2. Instructs the FIB to delete the associated FIB entries.

This procedure is time consuming and interrupts traffic for a long time. To resolve this issue, you can enable route fast switchover. This feature allows the device to instruct the FIB to delete the invalid FIB entries for route switchover first.

Procedure (IPv6)

1. Enter system view.

system-view

2. Enable IPv6 route fast switchover.

ipv6 route fast-switchover enable

By default, IPv6 route fast switchover is disabled.

Configuring routing policy-based recursive lookup

About this task

Configure routing policy-based recursive lookup to control route recursion results. For example, when a route changes, the routing protocol has to perform a route recursion if the next hop is indirectly connected. The routing protocol might select an incorrect path, which can cause traffic loss. To prevent this problem, you can use a routing policy to filter out incorrect routes. The routes that pass the filtering of the routing policy will be used for route recursion.

Restrictions and guidelines for routing policy-based recursive lookup

The apply clauses in the specified routing policy cannot take effect.

Make sure a minimum of one related route can match the routing policy for correct traffic forwarding.

Procedure (IPv4)

1. Enter system view.

system-view

2. Enter RIB view.

rib

3. Create the RIB IPv4 address family and enter its view.

address-family ipv4

4. Configure routing policy-based recursive lookup.

protocol protocol nexthop recursive-lookup route-policy route-policy-name

By default, routing policy-based recursive lookup is not configured.

Procedure (IPv6)

1. Enter system view.

system-view

2. Enter RIB view.

rib

3. Create the RIB IPv6 address family and enter its view.

address-family ipv6

4. Configure routing policy-based recursive lookup.

protocol protocol nexthop recursive-lookup route-policy route-policy-name

By default, routing policy-based recursive lookup is not configured.

Configuring next hop recursion loop suppression

About next hop recursion loop suppression

A recursion loop occurs when a route recurses to a related route that recurses back to the route. It causes a route recursion failure and further lookup for a related route. If recursion loop persists, continuous route flapping will cause high system resource consumption and CPU utilization.

This feature enables the system to use a counter to record the number of route recursion failures. When the counter reaches 20, the system suppresses route recursion for a specified period of time to save system resources on the device.

Restrictions and guidelines for configuring next hop recursion loop suppression

The configuration of disabling next hop recursion loop suppression takes effect immediately.

The setting of clearing the recursion loop counter takes effect for the next recursion loop suppression.

Disabling suppression for next hop recursion loop (IPv4)

1. Enter system view.

system-view

2. Enter RIB view.

rib

3. Create the RIB IPv4 address family and enter its view.

address-family ipv4

4. Disable next hop recursion loop suppression.

nexthop recursive-lookup restrain disable

By default, next hop recursion loop suppression is enabled.

Setting the interval for clearing the recursion loop counter (IPv4)

1. Enter system view.

system-view

2. Enter RIB view.

rib

3. Create the RIB IPv4 address family and enter its view.

address-family ipv4

4. Set the interval for clearing the recursion loop counter.

nexthop recursive-lookup restrain clear-interval interval

By default, the interval for clearing the recursion loop counter is 600 seconds.

Disabling suppression for next hop recursion loop (IPv6)

1. Enter system view.

system-view

2. Enter RIB view.

rib

3. Create the RIB IPv6 address family and enter its view.

address-family ipv6

4. Disable next hop recursion loop suppression.

nexthop recursive-lookup restrain disable

By default, next hop recursion loop suppression is enabled.

Setting the interval for clearing the recursion loop counter (IPv6)

1. Enter system view.

system-view

2. Enter RIB view.

rib

3. Create the RIB IPv6 address family and enter its view.

address-family ipv6

4. Set the interval for clearing the recursion loop counter.

nexthop recursive-lookup restrain clear-interval interval

By default, the interval for clearing the recursion loop counter is 600 seconds.

Setting the maximum number of active routes supported by the device

About this task

The feature allows you to set the maximum number of active IPv4/IPv6 routes supported by the device.

· You can use the routing-table limit number warn-threshold command to specify an alarm threshold. When the percentage of active routes exceeds the alarm threshold, the system generates a system log message but still accepts active routes. You can take relevant actions based on the message to save system resources. If the number of active routes reaches the maximum number, no more routes can be added and new routes are discarded.

· You can use the routing-table limit number simply-alert command to specify an alarm threshold. When the maximum number of active IPv4/IPv6 routes is exceeded, the device still accepts new active routes but generates a system log message. You can take relevant actions based on the message to save system resources.

Procedure (IPv4)

1. Enter system view.

system-view

2. Enter RIB view.

rib

3. Create the RIB IPv4 address family and enter its view.

address-family ipv4

4. Set the maximum number of active IPv4 routes supported by the device.

routing-table limit number { warn-threshold | simply-alert }

By default, the maximum number of active IPv4 routes is not set for the device.

Configuration in RIB IPv4 address family view limits the number of active IPv4 routes for the public network and all VPN instances.

Procedure (IPv6)

1. Enter system view.

system-view

2. Enter RIB view.

rib

3. Create the RIB IPv6 address family and enter its view.

address-family ipv6

4. Set the maximum number of active IPv6 routes supported by the device.

routing-table limit number { warn-threshold | simply-alert }

By default, the maximum number of active IPv6 routes is not set for the device.

Configuration in RIB IPv6 address family view limits the number of active IPv6 routes for the public network and all VPN instances.

Setting the maximum number of RIB next hop records or route entry records

About this task

When adding, modifying, or deleting RIP next hops or route entries, the device records associated information to facilitate troubleshooting. To view the recorded information, execute the display rib nib record command.

As a best practice to avoid excessive system resource usage, set the maximum number of RIB next hop records or route entry records properly. When the maximum number is reached, the device can continue to record new information. The new records will overwrite the earliest records.

Procedure (IPv4)

1. Enter system view.

system-view

2. Enter RIB view.

rib

3. Create the RIB IPv4 address family and enter its view.

address-family ipv4

4. Set the maximum number of RIB next hop records or route entry records.

record-limit limit [ rib nib [ flush [ delete | update ] | receive [ add | delete | update ] ] ]

By default, the maximum number of RIB next hop records or route entry records is 1000.

Procedure (IPv6)

1. Enter system view.

system-view

2. Enter RIB view.

rib

3. Create the RIB IPv6 address family and enter its view.

address-family ipv6

4. Set the maximum number of IPv6 RIB next hop records or route entry records.

record-limit limit [ rib nib [ flush [ delete | update ] | receive [ add | delete | update ] ] ]

By default, the maximum number of IPv6 RIB next hop records or route entry records is 1000.

Enabling MTP

About this task

Use maintenance probe (MTP) to locate faults for routing protocols depending on your network maintenance requirements. MTP enables the device to automatically ping and tracert a neighbor upon expiration of the neighbor hold timer and record the ping and tracert results. To view detailed fault information, use the display commands of routing protocols, for example, the display bgp troubleshooting command. To view detailed MTP information, use the display logbuffer command.

Procedure

1. Enter system view.

system-view

2. Enable MTP.

maintenance-probe enable

By default, MTP is disabled.

Enabling notifications for RIB

About this task

Use this feature to report critical RIB events to an NMS. For RIB event notifications to be sent correctly, you must also configure SNMP on the device. For more information about SNMP configuration, see the network management and monitoring configuration guide for the device.

Procedure (IPv4)

1. Enter system view.

system-view

2. Enable SNMP notifications for IPv4 RIB.

By default, SNMP notifications are enabled for IPv4 RIB.

Procedure (IPv6)

1. Enter system view.

system-view

2. Enable SNMP notifications for IPv6 RIB.

By default, SNMP notifications are enabled for IPv6 RIB.

Verifying and maintaining basic IP routing (IPv4)

Displaying IPv4 routing table information

Perform display tasks in any view.

· Display routing table information.

display ip routing-table [ all-vpn-instance | vpn-instance vpn-instance-name ] [ verbose ]

display ip routing-table all-routes

· Display information about routes permitted by an IPv4 basic ACL.

display ip routing-table [ vpn-instance vpn-instance-name ] acl ipv4-acl-number [ verbose ]

· Display information about routes to a specific destination address.

display ip routing-table [ vpn-instance vpn-instance-name ] ip-address [ mask-length | mask ] [ longer-match ] [ verbose ]

· Display information about routes to a range of destination addresses.

display ip routing-table [ vpn-instance vpn-instance-name ] ip-address1 to ip-address2 [ verbose ]

· Display information about routes permitted by an IP prefix list.

display ip routing-table [ vpn-instance vpn-instance-name ] prefix-list prefix-list-name [ verbose ]

· Display information about routes installed by a protocol.

display ip routing-table [ vpn-instance vpn-instance-name ] protocol protocol [ inactive | verbose ]

· Display brief routing table information, including maximum number of ECMP routes, maximum number of active routes, and number of remaining active routes.

display ip routing-table [ vpn-instance vpn-instance-name ] summary

Displaying and clearing IPv4 routing table statistics

To display IPv4 route or route prefix statistics, execute the following command in any view:

display ip routing-table [ all-routes | all-vpn-instance | vpn-instance vpn-instance-name ] [ prefix ] statistics

To clear route statistics, execute the following commands in user view:

· reset ip routing-table statistics protocol [ vpn-instance vpn-instance-name ] { protocol | all }

· reset ip routing-table [ all-routes | all-vpn-instance ] statistics protocol { protocol | all }

Displaying and clearing IPv4 route entry records

To display IPv4 route entry records, execute the following commands in any view:

· display ip routing-table record flush [ delete | update ] [ verbose ]

· display ip routing-table record notify [ delete | update ] [ verbose ]

· display ip routing-table record receive [ add | delete | update ] [ verbose ]

To clear IPv4 route entry records, execute the following command in user view:

reset ip routing-table record

Displaying ECMP route information

Perform display tasks in any view.

· Display the maximum number of ECMP routes.

display max-ecmp-num

· To display ECMP mode information, execute the following command in any view:

display ecmp mode

Displaying IPv4 RIB information

Perform display tasks in any view.

· Display route attribute information in the RIB.

display rib attribute [ attribute-id ]

· Display RIB GR state information.

display rib graceful-restart

· Display next hop information in the RIB.

display rib nib [ self-originated ] [ nib-id ] [ verbose ]

display rib nib [ sub-nib nib-id ] [ verbose ]

display rib nib protocol protocol [ verbose ]

· Display next hop information for direct routes.

display route-direct nib [ nib-id ] [ verbose ]

Displaying and clearing IPv4 RIB next hop records

To display IPv4 RIB next hop records, execute the following commands in any view:

· display rib nib record flush [ delete | update ] [ verbose ]

· display rib nib record receive [ add | delete | update ] [ verbose ]

To clear IPv4 RIB next hop records, execute the following command in user view:

reset rib nib record

Verifying and maintaining basic IP routing (IPv6)

Displaying IPv6 routing table information

Perform display tasks in any view.

· Display IPv6 routing table information.

display ipv6 routing-table [ all-vpn-instance | vpn-instance vpn-instance-name ] [ verbose ]

display ipv6 routing-table all-routes

· Display information about routes to an IPv6 destination address.

display ipv6 routing-table [ vpn-instance vpn-instance-name ] ipv6-address [ prefix-length ] [ longer-match ] [ verbose ]

· Display information about routes permitted by an IPv6 basic ACL.

display ipv6 routing-table [ vpn-instance vpn-instance-name ] acl ipv6-acl-number [ verbose ]

· Display information about routes to a range of IPv6 destination addresses.

display ipv6 routing-table [ vpn-instance vpn-instance-name ] ipv6-address1 to ipv6-address2 [ verbose ]

· Display information about routes permitted by an IPv6 prefix list.

display ipv6 routing-table [ vpn-instance vpn-instance-name ] prefix-list prefix-list-name [ verbose ]

· Display information about routes installed by an IPv6 protocol.

display ipv6 routing-table [ vpn-instance vpn-instance-name ] protocol protocol [ inactive | verbose ]

· Display brief IPv6 routing table information, including maximum number of ECMP routes, maximum number of active routes, and number of remaining active routes.

display ipv6 routing-table [ vpn-instance vpn-instance-name ] summary

Displaying and clearing IPv6 routing table statistics

To display IPv6 route or route prefix statistics, execute the following command in any view:

display ipv6 routing-table [ all-routes | all-vpn-instance | vpn-instance vpn-instance-name ] [ prefix ] statistics

To clear IPv6 route statistics, execute the following commands in user view:

· reset ipv6 routing-table statistics protocol [ vpn-instance vpn-instance-name ] { protocol | all }

· reset ipv6 routing-table [ all-routes | all-vpn-instance ] statistics protocol { protocol | all }

Displaying and clearing IPv6 route entry records

To display IPv6 route entry records, execute the following commands in any view:

· display ipv6 routing-table record flush [ delete | update ] [ verbose ]

· display ipv6 routing-table record notify [ delete | update ] [ verbose ]

· display ipv6 routing-table record receive [ add | delete | update ] [ verbose ]

To clear IPv6 route entry records, execute the following command in user view:

reset ipv6 routing-table record

Displaying IPv6 ECMP route information

Perform display tasks in any view.

· Display the maximum number of IPv6 ECMP routes.

display ipv6 max-ecmp-num

· To display ECMP mode information, execute the following command in any view:

display ecmp mode

Displaying IPv6 RIB information

Perform display tasks in any view.

· Display route attribute information in the IPv6 RIB.

display ipv6 rib attribute [ attribute-id ]

· Display IPv6 RIB GR state information.

display ipv6 rib graceful-restart

· Display next hop information in the IPv6 RIB.

display ipv6 rib nib [ self-originated ] [ nib-id ] [ verbose ]

display ipv6 rib nib [ sub-nib nib-id ] [ verbose ]

display ipv6 rib nib protocol protocol [ verbose ]

· Display next hop information for IPv6 direct routes.

display ipv6 route-direct nib [ nib-id ] [ verbose ]

Displaying and clearing IPv6 RIB next hop records

To display IPv6 RIB next hop records, execute the following commands in any view:

· display ipv6 rib nib record flush [ delete | update ] [ verbose ]

· display ipv6 rib nib record receive [ add | delete | update ] [ verbose ]

To clear IPv6 RIB next hop records, execute the following command in user view:

reset ipv6 rib nib record

Basic IP routing configuration examples

Example: Configuring load sharing based on source and destination addresses

Network configuration

As shown in Figure 1, Router A has two equal-cost routes to Router B. Configure load sharing based on source and destination addresses on Router A to forward packets through Router B to the destination IP address 1.2.3.4/24.

Figure 1 Network diagram

‌

Procedure

# On Router A, configure IP addresses for GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2.

<RouterA> system-view

[RouterA] interface gigabitethernet 1/0/1

[RouterA-GigabitEthernet1/0/1] ip address 10.1.1.1 24

[RouterA-GigabitEthernet1/0/1] quit

[RouterA] interface gigabitethernet 1/0/2

[RouterA-GigabitEthernet1/0/2] ip address 20.1.1.1 24

[RouterA-GigabitEthernet1/0/2] quit

# On Router B, configure IP addresses for GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2.

<RouterB> system-view

[RouterB] interface gigabitethernet 1/0/1

[RouterB-GigabitEthernet1/0/1] ip address 10.1.1.2 24

[RouterB-GigabitEthernet1/0/1] quit

[RouterB] interface gigabitethernet 1/0/2

[RouterB-GigabitEthernet1/0/2] ip address 20.1.1.2 24

[RouterB-GigabitEthernet1/0/2] quit

# On Router A, configure two static routes to the destination IP address 1.2.3.4.

[RouterA] ip route-static 1.2.3.4 24 10.1.1.2

[RouterA] ip route-static 1.2.3.4 24 20.1.1.2

[RouterA] quit

# On Router A, display FIB entries matching the destination IP address 1.2.3.4.

<RouterA> display fib 1.2.3.4

FIB entry count: 2

Flag:

U:Usable G:Gateway H:Host B:Blackhole D:Dynamic S:Static

R:Relay F:FRR

Destination/Mask Nexthop Flag OutInterface/Token Label

1.2.3.0/24 10.1.1.2 USGR GE1/0/1 Null

1.2.3.0/24 20.1.1.2 USGR GE1/0/2 Null

# On Router A, configure per-flow load sharing based on source and destination IP addresses.

<RouterA> system-view

[RouterA] ip load-sharing mode per-flow dest-ip src-ip global

[RouterA] quit

Verifying the configuration

# Verify that Router A implements load sharing.

<RouterA> display counters outbound interface GigabitEthernet

Interface Total (pkts) Broadcast (pkts) Multicast (pkts) Err (pkts)

GE1/0/1 1045 0 0 0

GE1/0/2 1044 0 0 0

07-Layer 3—IP Routing Configuration Guide

Dynamic routing protocols

Route preference

Load sharing

Extension attribute redistribution

Configuring load sharing mode

About this task

Procedure

About this task

Procedure

About this task

Procedure

About this task

Procedure

About this task

Restrictions and guidelines

Procedure (IPv4)

Procedure (IPv6)

About this task

Procedure (IPv4)

Procedure (IPv6)

Restrictions and guidelines

Procedure (IPv4)

Procedure (IPv6)

About this task

Prerequisites for RIB NSR

Procedure (IPv4)

Procedure (IPv6)

About this task

Restrictions and guidelines for inter-protocol FRR

Procedure (IPv4)

Procedure (IPv6)

About this task

Restrictions and guidelines for BFD control packet mode

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Procedure (IPv4)

Procedure (IPv6)

About this task

Procedure (IPv6)

About this task

Restrictions and guidelines for routing policy-based recursive lookup

Procedure (IPv4)

Procedure (IPv6)

About this task

Procedure (IPv4)

Procedure (IPv6)

About this task

Procedure (IPv4)

Procedure (IPv6)

About this task

Procedure

About this task

Procedure (IPv4)

Procedure (IPv6)

Network configuration

Procedure

Verifying the configuration

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business

News & Events

Contact Us