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

AR500, AR510, and AR530 V200R007 Commands Reference

This document describes all the configuration commands of the device, including the command function, syntax, parameters, views, default level, usage guidelines, examples, and related commands.
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).
Static Route Configuration Commands

Static Route Configuration Commands

NOTE:

The AR510 series routes do not support IPv6 static routes.

ip route recursive-lookup bgp-vpnv4-route

Function

The ip route recursive-lookup bgp-vpnv4-route enable command enables a static route to be iterated to a cross route on the remote VPN.

The ip route recursive-lookup bgp-vpnv4-route disable command disables a static route from being iterated to a cross route on the remote VPN.

The undo ip route recursive-lookup bgp-vpnv4-route disable command enables a static route to be iterated to a cross route on the remote VPN.

By default, a static route can be iterated to a cross route on the remote VPN.

Format

ip route recursive-lookup bgp-vpnv4-route { enable | disable }

undo ip route recursive-lookup bgp-vpnv4-route disable

Parameters

Parameter Description Value
enable Enables a static route to be iterated to a cross route on the remote VPN. -
disable Disables a static route from being iterated to a cross route on the remote VPN. -

Views

System view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

A static route needs to be iterated if its next hop is not directly reachable. You can run the ip route recursive-lookup bgp-vpnv4-route enable command to enable the static route to be iterated to a cross route on the remote VPN. Then the static route can inherit the Label and Token information about the cross route. The device can forward data through the tunnel to which the static route is iterated.

Precautions

The ip route recursive-lookup bgp-vpnv4-route enable command and the undo ip route recursive-lookup bgp-vpnv4-route disable command have the same function and do not generate the configuration in the configuration file.

Example

# Enable a static route to be iterated to a cross route on the remote VPN.

<Huawei> system-view
[Huawei] ip route recursive-lookup bgp-vpnv4-route enable

# Disable a static route from being iterated to a cross route on the remote VPN.

<Huawei> system-view
[Huawei] ip route recursive-lookup bgp-vpnv4-route disable

# Enable a static route to be iterated to a cross route on the remote VPN.

<Huawei> system-view
[Huawei] undo ip route recursive-lookup bgp-vpnv4-route disable

ip route recursive-lookup blackhole protocol static

Function

The ip route recursive-lookup blackhole protocol static disable command prevents static routes from being iterated to blackhole routes.

The ip route recursive-lookup blackhole protocol static enable command allows static routes to be iterated to blackhole routes.

The undo ip route recursive-lookup blackhole protocol static disable command allows static routes to be iterated to blackhole routes.

By default, static routes can be iterated to blackhole routes.

Format

ip route recursive-lookup blackhole protocol static { disable | enable }

undo ip route recursive-lookup blackhole protocol static disable

Parameters

Parameter Description Value
disable Prevents static routes from being iterated to blackhole routes. -
enable Allows static routes to be iterated to blackhole routes. -

Views

System view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

If a link failure occurs on a network with IGP (OSPF for example), static, and blackhole routes, the static routes may be iterated to blackhole routes to remain active. The static routes will be preferentially selected over the OSPF routes because of a higher priority. Although active, the static routes are unreachable because they have been iterated to blackhole routes. As a result, services are interrupted. To address this problem, run the ip route recursive-lookup blackhole protocol static disable command to prevent the static routes from being iterated to the blackhole routes, so that the OSPF routes can be preferentially selected due to the inactivity of the static routes.

Precautions

The ip route recursive-lookup blackhole protocol static enable and undo ip route recursive-lookup blackhole protocol static disable commands have the same function, and either of them can be run.

Example

# Prevent static routes from being iterated to blackhole routes.

<Huawei> system-view
[Huawei] ip route recursive-lookup blackhole protocol static disable

# Allow static routes to be iterated to blackhole routes.

<Huawei> system-view
[Huawei] ip route recursive-lookup blackhole protocol static enable

# Allow static routes to be iterated to blackhole routes.

<Huawei> system-view
[Huawei] undo ip route recursive-lookup blackhole protocol static disable

ip route-static

Function

The ip route-static command configures a unicast static route.

The undo ip route-static command deletes a unicast static route.

By default, the system does not configure IPv4 unicast static routes.

Format

ip route-static ip-address { mask | mask-length } { nexthop-address | interface-type interface-number [ nexthop-address ] | vpn-instance vpn-instance-name nexthop-address } [ preference preference | tag tag ] * [ track { bfd-session cfg-name | efm-state interface-type interface-number | nqa admin-name test-name } | permanent ] [ description text ]

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

ip route-static ip-address { mask | mask-length } interface-type interface-number dhcp [ preference preference | tag tag ] * [ track nqa admin-name test-name ] [ description text ]

undo ip route-static ip-address { mask | mask-length } interface-type interface-number dhcp [ preference preference | tag tag ] *

undo ip route-static ip-address { mask | mask-length } [ nexthop-address | interface-type interface-number [ nexthop-address ] ] [ preference preference | tag tag ] * [ track { bfd-session | efm-state } | permanent ]

undo ip route-static ip-address { mask | mask-length } interface-type interface-number [ nexthop-address ] [ preference preference | tag tag ] * ldp-sync

undo ip route-static [ track bfd-session ] all

Parameters

Parameter Description Value
ip-address Specifies a destination IP address. The value is in dotted decimal notation.
mask Specifies the mask of the IP address. The value is in dotted decimal notation.
mask-length Specifies the mask length. As 1s in a 32-bit mask must be consecutive, the mask in dotted decimal notation can be replaced by the mask length. The value is an integer that ranges from 0 to 32.
nexthop-address Specifies the next-hop address. The value is in dotted decimal notation.
interface-type interface-number Specifies the type and number of the interface that forwards packets. -
vpn-instance vpn-instance-name Specifies the name of a VPN instance. If the VPN instance name is specified, a static route searches the routing table of the VPN instance for an outbound interface according to nexthop-address. The value is a string of 1 to 31 case-sensitive characters, spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string.
preference preference Specifies the preference of a static route. A smaller value indicates a higher preference. The value is an integer that ranges from 1 to 255. The default value is 60.
tag tag Specifies the tag value of a static route. By configuring different tag values, you can classify static routes to implement different routing policies. For example, other routing protocols can import static routes with specified tag values through routing policies. The value is an integer that ranges from 1 to 4294967295. The default value is 0.
ldp-sync

Enables synchronization between LDP and static routes.

-
track bfd-session cfg-name Binds a static BFD session to static routes to fast detect faults. cfg-name is a string of 1 to 15 characters without spaces.When double quotation marks are used around the string, spaces are allowed in the string.
track efm-state interface-type interface-number Detects the EFM OAM state of a specified interface. -
track nqa admin-name test-name Specifies the administrator name of an NQA test instance bound to a static route and the name of the test instance. The values of admin-name and test-name are both a string of 1 to 32 case-sensitive characters without spaces.
permanent

Configures permanent advertisement of static routes.

-
description text Configures the description of a static route. The value is a string of 1 to 80 characters that can contain spaces.
all Deletes all IPv4 unicast static routes. -
dhcp Associates the static route with DHCP so that the static route can obtain the next hop IP address dynamically. -

Views

System view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

On a simple network, you only need to configure static routes to ensure that the network runs properly. When the industrial switch router cannot use dynamic routing protocols or establish a route to the destination network, configure static routes.

A static route can be used for traffic forwarding only when a next hop IP address is available. If the next hop IP address manually specified for a static route changes, the device on which the static route is configured is unaware of the change. As a result, traffic fails to be forwarded along the static route. To address this problem, specify dhcp in the command to associate the static route with DHCP so that the static route can obtain the next hop IP address dynamically.
  • If the next hop IP address obtained using DHCP changes, the static route updates it.
  • If no next hop IP address can be obtained using DHCP, the static route is invalid.

Precautions

When configuring unicast static routes, note the following:

  • Only public routes can be used for tunnel iteration.

  • If no preference is configured for a static route, the static route uses the default preference 60.

  • When both the destination IP address and the mask are set to 0.0.0.0, a default route is configured. If the industrial switch router cannot find a route in the routing table to forward packets, the industrial switch router uses the default route to forward packets.

  • Setting different preferences can implement different routing management policies. For example, if multiple routes to the same destination are configured with the same preference, load balancing can be implemented. If multiple routes to the same destination are configured with different preferences, route backup can be implemented.

  • You can configure the description text parameter to add the description of static routes so that the administrator can check and maintain static routes easily. You can run the display this command in the system view or run the display current-configuration command to view the descriptions of static routes.

  • When configuring static routes, you can specify outbound interfaces or next-hop addresses based on the outbound interface type. For example, you can specify only outbound interfaces for static routes on P2P interfaces and specify only next hops for static routes on NBMA interfaces, and you must specify next hops for static routes on broadcast interfaces.

  • In some cases, for example, the link layer protocol is PPP and the peer IP address is unknown, you can also specify outbound interfaces when configuring a industrial switch router. In this manner, you do not need to modify the industrial switch router configuration when the peer IP address changes.

Example

# Set the next-hop address of the default route to 172.16.0.1.

<Huawei> system-view
[Huawei] ip route-static 0.0.0.0 0.0.0.0 172.16.0.1

ip route-static default-preference

Function

The ip route-static default-preference command sets the default preference for IPv4 static routes.

The undo ip route-static default-preference command restores the default preference value of IPv4 static routes.

By default, the default preference of IPv4 static routes is 60.

Format

ip route-static default-preference preference

undo ip route-static default-preference

Parameters

Parameter Description Value
preference Specifies the default preference for IPv4 static routes. A smaller value indicates a higher preference. The value is an integer that ranges from 1 to 255.

Views

System view

Default Level

2: Configuration level

Usage Guidelines

You can change the preference of a static route to change the status of the route. To change the default preference of a new IPv4 static route, run the ip route-static default-preference command.

Example

# Set the default preference of IPv4 static routes to 70.

<Huawei> system-view
[Huawei] ip route-static default-preference 70

ip route-static selection-rule relay-depth

Function

The ip route-static selection-rule relay-depth command enables static routes to be selected based on the iteration depth.

The undo ip route-static selection-rule relay-depth command disables static routes from being selected based on the iteration depth.

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

Format

ip route-static selection-rule relay-depth

undo ip route-static selection-rule relay-depth

Parameters

None

Views

System view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

To prevent a loop when GGSN services are forwarded between boards, use the ip route-static selection-rule relay-depth command to enable static routes to be selected based on the iteration depth.

Precautions

In the system, some static routes have the same prefix and preference but different iteration depths. After the system enables static routes to be selected based on the iteration depth, the static route module selects the static route with the smallest iteration depth as the active route and delivers it to the FIB table. Other static routes then become inactive.

Example

# Enable static routes to be selected based on the iteration depth.

<Huawei> system-view
[Huawei] ip route-static selection-rule relay-depth

ip route-static vpn-instance

Function

The ip route-static vpn-instance command configures static routes for a VPN instance.

The undo ip route-static vpn-instance command deletes static routes for a VPN instance.

By default, no static route is configured for a VPN instance.

Format

ip route-static vpn-instance vpn-source-name destination-address { mask | mask-length } { nexthop-address [ public ] | interface-type interface-number [ nexthop-address ] | vpn-instance vpn-destination-name nexthop-address } [ preference preference | tag tag ] * [ track { bfd-session cfg-name | efm-state interface-type interface-number | nqa admin-name test-name } | permanent ] [ description text ]

ip route-static vpn-instance vpn-source-name destination-address { mask | mask-length } interface-type interface-number [ nexthop-address ] [ preference preference | tag tag ] * ldp-sync [ description text ]

ip route-static vpn-instance vpn-source-name destination-address { mask | mask-length } interface-type interface-number dhcp [ preference preference | tag tag ] * [ track nqa admin-name test-name ] [ description text ]

undo ip route-static vpn-instance vpn-source-name destination-address { mask | mask-length } interface-type interface-number dhcp [ preference preference | tag tag ] *

undo ip route-static vpn-instance vpn-source-name destination-address { mask | mask-length } [ nexthop-address | interface-type interface-number [ nexthop-address ] ] [ preference preference | tag tag ] * [ track { bfd-session | efm-state } | permanent ]

undo ip route-static vpn-instance vpn-source-name destination-address { mask | mask-length } interface-type interface-number [ nexthop-address ] [ preference preference | tag tag ] * ldp-sync

undo ip route-static vpn-instance vpn-source-name all

Parameters

Parameter Description Value
vpn-instance vpn-source-name Specifies the name of the source VPN instance. Each VPN instance has its own routing table. The configured static routes are added to the routing table of the specified VPN instance. The value is a string of 1 to 31 case-sensitive characters, spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string.
destination-address Specifies the destination IP address of a static route. The value is in dotted decimal notation.
mask Specifies the subnet mask of the destination IP address. The value is in dotted decimal notation.
mask-length Specifies the mask length of the destination IP address. The value is an integer that ranges from 0 to 32.
interface-type interface-number Specifies the type and number of the outbound interface of a static route. -
nexthop-address Specifies the next-hop address of a static route. If the outbound interface of a static route is a broadcast interface, the next-hop address must be specified for the static route. The value is in dotted decimal notation.
public Specifies the next-hop address as a public network address but not an address in the source VPN instance. -
preference preference Specifies the preference of a static route. The value is an integer that ranges from 1 to 255. If this parameter is not specified, the default preference of a static route is 60.
tag tag Specifies the tag value of a static route. By configuring different tag values, you can classify static routes to implement different routing policies. For example, other routing protocols can import static routes with specified tag values through routing policies. The value is an integer that ranges from 1 to 4294967295. The default value is 0.
track bfd-session cfg-name Binds a static BFD session to static routes to fast detect faults. cfg-name is a string of 1 to 15 characters without spaces.
track efm-state interface-type interface-number Detects the EFM OAM state of a specified interface. -
track nqa admin-name test-name Specifies the administrator name of an NQA test instance bound to a static route and the name of the test instance. The values of admin-name and test-name are both a string of 1 to 32 case-sensitive characters without spaces.
ldp-sync

Enables synchronization between LDP and static routes.

-
permanent

Configures permanent advertisement of static routes.

-
description text Specifies the description of a static route. You can specify description to add the description of static routes, facilitating static route query and maintenance. The value is a string of 1 to 80 characters that can contain spaces.
vpn-instance vpn-destination-name Specifies the name of the VPN instance to which the local device belongs. The value is a string of 1 to 31 case-sensitive characters without spaces.
all Deletes all static routes of a VPN instance. -
dhcp Associates the static route with DHCP so that the static route can obtain the next hop IP address dynamically. -

Views

System view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

You need to configure static routes for a VPN instance on a PE in the following scenarios:
  • The PE connects to a CE.
  • The specified VPN connects to the Internet.
A static route can be used for traffic forwarding only when a next hop IP address is available. If the next hop IP address manually specified for a static route changes, the device on which the static route is configured is unaware of the change. As a result, traffic fails to be forwarded along the static route. To address this problem, specify dhcp in the command to associate the static route with DHCP so that the static route can obtain the next hop IP address dynamically.
  • If the next hop IP address obtained using DHCP changes, the static route updates it.
  • If no next hop IP address can be obtained using DHCP, the static route is invalid.

Follow-up Procedure

After a static route is configured, import the static route to BGP running between PEs if the static route needs to be sent to the peer PE.

Precautions

During the configuration of a static route for a VPN instance, the next-hop address can belong to the VPN instance or a public network. When the next-hop address of the static route is a public network address, specify public following nexthop-address.

If the outbound interface of a static route is a broadcast interface, you must specify the next-hop address for the static route.

You can configure description text to add the description of static routes so that the administrator can query and maintain static routes easily. To view the description of static routes, run the display this command in the system view or run the display current-configuration command.

Example

# Configure a static route for VPN instance named vpn1, and set the destination address of the static route to 10.1.1.0/24 and next-hop address to 192.168.1.2 (IP address of VPN instance vpn2).

<Huawei> system-view
[Huawei] ip vpn-instance vpn1
[Huawei-vpn-instance-vpn1] route-distinguisher 100:200
[Huawei-vpn-instance-vpn1-af-ipv4] quit
[Huawei-vpn-instance-vpn1] quit
[Huawei] ip vpn-instance vpn2
[Huawei-vpn-instance-vpn2] route-distinguisher 300:400
[Huawei-vpn-instance-vpn2-af-ipv4] quit
[Huawei-vpn-instance-vpn2] quit
[Huawei] ip route-static vpn-instance vpn1 10.1.1.0 24 vpn-instance vpn2 192.168.1.2

ipv6 route-static

Function

The ipv6 route-static command configures IPv6 static routes.

The undo ipv6 route-static command deletes configured static routes.

By default, no IPv6 static route is configured.

Format

ipv6 route-static dest-ipv6-address prefix-length { interface-type interface-number [ nexthop-ipv6-address ] | nexthop-ipv6-address | vpn-instance vpn-destination-name nexthop-ipv6-address } [ preference preference | tag tag ] * [ description text ]

undo ipv6 route-static dest-ipv6-address prefix-length [ interface-type interface-number [ nexthop-ipv6-address ] | nexthop-ipv6-address ] [ preference preference | tag tag ] *

undo ipv6 route-static all

Parameters

Parameter Description Value
dest-ipv6-address Specifies the destination IPv6 address. The value is a 32-bit hexadecimal number, in X:X:X:X:X:X:X:X format.
prefix-length Specifies the length of an IPv6 prefix, namely, the number of consecutive 1s in the mask. The value is an integer that ranges from 0 to 128.
interface-type interface-number Specifies the type and number of an outbound interface. -
vpn-instance vpn-destination-name Specifies the name of a VPN instance. If the VPN instance name is specified, the system searches the routing table of the VPN instance for the outbound interface of a static route according to the configured next-hop address. The value is a string of 1 to 31 case-sensitive characters without spaces.
nexthop-ipv6-address Specifies the next-hop IPv6 address The value is a 32-bit hexadecimal number, in X:X:X:X:X:X:X:X format.
preference preference Specifies the preference of an IPv6 static route. The value is an integer that ranges from 1 to 255. The default value is 60.
tag tag Specifies the tag value of a static route. By configuring different tag values, you can classify static routes to implement different routing policies. For example, other routing protocols can import static routes with specified tag values through routing policies. The value is an integer that ranges from 1 to 4294967295. The default value is 0.
description text Specifies the description of a static route. The value is a string of 1 to 80 characters that can contain spaces.
all Deletes all IPv6 static routes. -

Views

System view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

On a simple network, you only need to configure static routes to ensure that the network runs properly. When the router cannot use dynamic routing protocols or establish a route to the destination network, configure static routes on the router.

You can configure description text to add the description of static routes so that the administrator can query and maintain static routes easily. To view the description of static routes, run the display this command in the system view or run the display current-configuration command.

Precautions

When configuring unicast static routes, note the following:

  • If no preference is set for a static route, the static route uses the default preference 60.

  • If the destination address and mask of a static route are all 0s, the static route is a default route.

Example

# Configure IPv6 static routes on the public network.

<Huawei> system-view
[Huawei] ipv6 route-static fc00:0:0:2001::1 128 fc00:0:0:2002::2

ipv6 route-static default-preference

Function

The ipv6 route-static default-preference command sets the default preference for IPv6 static routes.

The undo ipv6 route-static default-preference command restores the default preference of IPv6 static routes.

By default, the default preference of IPv6 static routes is 60.

Format

ipv6 route-static default-preference preference

undo ipv6 route-static default-preference

Parameters

Parameter Description Value
preference Specifies the default preference of IPv6 static routes. A smaller value indicates a higher preference. The value is an integer that ranges from 1 to 255.

Views

System view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

You can change the preference of a static route to change the status of the route. To change the default preference of a new IPv6 static route, run the ipv6 route-static default-preference command.

Configuration Impact

After the ipv6 route-static default-preference command is used, the default preference of all the new IPv6 static routes is changed.

After a new default preference is specified, the new default preference is valid only for new IPv6 static routes but not for existing IPv6 static routes.

Example

# Set the default preference of IPv6 static routes to 70.

<Huawei> system-view
[Huawei] ipv6 route-static default-preference 70

ip route-static track bfd-session admindown invalid

Function

The ip route-static track bfd-session admindown invalid command prevents a static route from being selected if its bound BFD session is in AdminDown state.

The undo ip route-static track bfd-session admindown invalid command restores the default configuration.

By default, a static route can still be selected even if its bound BFD session is in AdminDown state.

Format

ip route-static track bfd-session session-name bfd-name admindown invalid

undo ip route-static track bfd-session session-name bfd-name admindown invalid

undo ip route-static track bfd-session admindown invalid

Parameters

Parameter Description Value
session-name bfd-name

Specifies a BFD session bound to a static route.

The value is a string of 1 to 15 case-insensitive characters without spaces. If the string is enclosed within double quotation marks ("), the string can contain spaces.

Views

System view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

By default, a static route can still be selected even if its bound BFD session is in AdminDown state. However, the static route cannot be selected by some non-Huawei devices. As a result, communication with these non-Huawei devices may fail.

To address this problem, run the ip route-static track bfd-session admindown invalid command to avoid selecting the static route if its bound BFD session is in AdminDown state.

Prerequisites

The BFD session specified by bfd-name has been created.

Precautions

The undo ip route-static track bfd-session admindown invalid command enables all static routes to be selected even if their bound BFD sessions are in AdminDown state.

Example

# Prevent a static route from being selected if its bound BFD session is in AdminDown state.

<Huawei> system-view
[Huawei] bfd
[Huawei-bfd] quit
[Huawei] bfd bfda bind peer-ip 1.1.1.1
[Huawei-bfd-session-bfda] discriminator local 20
[Huawei-bfd-session-bfda] discriminator remote 10
[Huawei-bfd-session-bfda] commit
[Huawei-bfd-session-bfda] quit
[Huawei] ip route-static track bfd-session session-name bfda admindown invalid

ipv6 route-static vpn-instance

Function

The ipv6 route-static vpn-instance command configures IPv6 static routes in a VPN instance.

The undo ipv6 route-static vpn-instance command withdraws IPv6 static routes in a VPN instance.

By default, the system does not configure IPv6 static routes for VPN instances.

Format

ipv6 route-static vpn-instance vpn-instance-name dest-ipv6-address prefix-length { [ interface-type interface-number [ nexthop-ipv6-address ] ] | nexthop-ipv6-address [ public ] | vpn-instance vpn-destination-name nexthop-ipv6-address } [ preference preference | tag tag ] * [ description text ]

undo ipv6 route-static vpn-instance vpn-instance-name dest-ipv6-address prefix-length [ interface-type interface-number ] [ nexthop-ipv6-address ] [ preference preference | tag tag ] *

undo ipv6 route-static vpn-instance vpn-instance-name all

Parameters

Parameter Description Value
vpn-instance vpn-instance-name Specifies the name of a VPN instance. Each VPN instance has its own unicast routing table. The configured static routes are installed into the routing table of the specified VPN instance. The value is a string of 1 to 31 case-sensitive characters, spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string.
dest-ipv6-address Specifies the destination IPv6 address. The value is a 32-bit hexadecimal number, in X:X:X:X:X:X:X:X format.
prefix-length Specifies the length of an IPv6 prefix, namely, the number of consecutive 1s in the mask. The value is an integer that ranges from 0 to 128.
interface-type Specifies the type of an interface. -
interface-number Specifies the number of an interface. -
nexthop-ipv6-address Specifies the next-hop IPv6 address. The value is a 32-bit hexadecimal number, in X:X:X:X:X:X:X:X format.
vpn-instance vpn-destination-name Specifies the name of the destination VPN instance. If the name of the destination VPN instance is specified, a static route searches the destination VPN instance for an outbound interface based on the configured next hop address. The value is a string of 1 to 31 case-sensitive characters, spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string.
public Specifies the next-hop address as a public network address. -
preference preference Specifies the preference of a static route. The value is an integer that ranges from 1 to 255.
tag tag Specifies the tag value of a static route. By configuring different tag values, you can classify static routes to implement different routing policies. For example, other routing protocols can import static routes with specified tag values through routing policies. The value is an integer that ranges from 1 to 4294967295. The default value is 0.
description text Specifies the description of static routes.80 The value is a string of 1 to 80 characters that can contain spaces.
all Deletes all the IPv6 static routes configured for the specified VPN instance. -

Views

System view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

When an IPv6 VPN network is simple, you can run the ipv6 route-static vpn-instance command to configure static routes for this VPN.
  • To configure VPN users to access a public network, you can perform network address translation (NAT) or run the ipv6 route-static vpn-instance command with the keyword public to configure the VPN route with the next-hop address as the public network address.

  • You can configure description text to add the description of static routes so that the administrator can query and maintain static routes easily. To view the description of static routes, run the display this command in the system view or run the display current-configuration command.

Precautions

If the destination address and the prefix length are set to all 0s, a default route is configured.

After a network fault occurs or the network topology changes, static routes cannot automatically change. Therefore, configure static routes with caution.

Example

# Configure a default route with next-hop address FC00:0:0:2001::1.

<Huawei> system-view
[Huawei] ipv6 route-static vpn-instance vpn1 :: 0 fc00:0:0:2001::1
Related Topics

routing-table download filter

Function

The routing-table download filter command configures the static route filtering function.

The undo routing-table download filter command cancels the static route filtering configuration.

By default, the static route filtering function is not configured.

NOTE:

Only V200R007C00 supports this command.

Format

routing-table download filter acl acl-number

undo routing-table download filter acl acl-number

Parameters

Parameter Description Value
acl acl-number

Specifies the number of an ACL.

The value is an integer that ranges from 3000 to 3999.

Views

System view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

If routes advertised through routing protocols by the device into a network must be different from the routes used by the device to forward packets, run the routing-table download filter command on the device to configure the static route filtering function. This configuration ensures that the device does not use the filtered static routes to forward packets, but it can still advertise static routes through routing protocols into the network.

Precautions

  • You can specify an empty ACL (ACL number) in this command, and configure this ACL later.
  • To ensure that the static route filtering function takes effect, run the routing-table download filter command and then configure static routes to be filtered.
  • If the undo ip soft-forward enhance enable command has been configured, running the routing-table download filter command only ensures that the device does not use the filtered static routes to forward service packets. The device can still use static routes to forward the protocol packets sent by itself and advertise static routes through routing protocols into the network.

Example

# Configure ACL 3100 to filter 24-bit mask routes with the destination network segment 10.215.10.0.

<Huawei> system-view
[Huawei] acl 3100
[Huawei-acl-adv-3100] rule 5 deny ip source 10.215.10.0 0.0.0.255
[Huawei-acl-adv-3100] quit
[Huawei] routing-table download filter acl 3100
[Huawei] ip route-static 10.215.10.0 255.255.255.0 null 0
Translation
Download
Updated: 2019-05-29

Document ID: EDOC1000097293

Views: 92520

Downloads: 126

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