No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Fat AP and Cloud AP V200R008C00 CLI-based Configuration Guide

Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Configuring Static Routes

Configuring Static Routes

Static routes are applicable to the networks with simple structures. Proper configuration and usage of static routes improve the network performance and meet the bandwidth requirement of important applications.

Configuring IPv4 Static Routes

On a network, you can accurately control route selection by configuring IPv4 static routes.

Pre-configuration Tasks

Before configuring IPv4 static routes, complete the following task:

  • Configuring IP addresses for interfaces to ensure network-layer communication between neighbor nodes

Configuration Procedures

You can perform the following configuration tasks (excluding the task of Checking the Configuration) in any sequence as required.

Creating IPv4 Static Routes

Context

When creating static routes, you can specify both the outbound interface and next hop. Alternatively, you can specify only the outbound interface or next hop based on the outbound interface type.
  • Specify the outbound interface for P2P interfaces.

  • Specify the next hop for non broadcast multiple access (NBMA) interfaces.

  • Specify the next hop for broadcast interfaces (for example, Ethernet interfaces).

If you specify the same preference for static routes to the same destination, you can implement load balancing among these routes. If you specify different preferences for static routes, you can implement route backup among the routes.

If the destination IP address and mask are set to all 0s, an IPv4 static default route is configured. By default, no IPv4 static default route is configured.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    ip route-static ip-address { mask | mask-length } { nexthop-address | interface-type interface-number [ nexthop-address ] } [ preference preference | tag tag ] * [ description text ]

    An IPv4 static route is configured.

(Optional) Setting the Default Preference for IPv4 Static Routes

Context

The default preference of IPv4 static routes affects route selection. When an IPv4 static route is configured, the default preference is used if no preference is specified for the static route.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    ip route-static default-preference preference

    The default preference of static routes is set.

    By default, the preference of static routes is 60.

    NOTE:

    After the default preference is reconfigured, the new default preference is valid only for new IPv4 static routes.

(Optional) Configuring Static Route Selection Based on Iteration Depth

Context

Route iteration refers to the process of finding the directly-connected outbound interface based on the next hop of a route. The iteration depth indicates the number of times the system searches for routes. A smaller number of route iterations indicates a smaller iteration depth.

When there are multiple static routes with the same prefix but different iteration depths, the system selects the static route with the smallest iteration depth as the active route and delivers it to the FIB table after static route selection based on iteration depth is configured. The other static routes then become inactive. A smaller iteration depth indicates a more stable route.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    ip route-static selection-rule relay-depth

    Static route selection based on iteration depth is configured.

    By default, static routes are not selected based on iteration depth.

(Optional) Configuring Permanent Advertisement of IPv4 Static Routes

Context

Link connectivity directly affects network stability and availability. Monitoring link status is an important measure for network maintenance. If service traffic needs to be forwarded along a specified path, you can monitor the status of the path using a ping operation. In this manner, you can monitor services at a very low cost.

With permanent advertisement of static routes, you can detect link connectivity by pinging the destination addresses of static routes. After permanent advertisement of static routes is configured, static routes always take effect regardless of the outbound interface status. In this case, the system forwards ping packets along a specified path only, which helps monitor the link status of the path.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    ip route-static ip-address { mask | mask-length } { nexthop-address | interface-type interface-number [ nexthop-address ] } permanent [ description text ]

    Permanent advertisement of IPv4 static routes is configured.

    By default, permanent advertisement of IPv4 static routes is not configured.

Checking the Configuration

Procedure

  • Run the display ip routing-table command to check brief information about the IPv4 routing table.
  • Run the display ip routing-table verbose command to check detailed information about the IPv4 routing table.
Translation
Download
Updated: 2019-01-11

Document ID: EDOC1000176006

Views: 116549

Downloads: 309

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next