This command might interrupt network communication and cause packet forwarding failure. Before executing the command, make sure you fully understand the potential impact on the network.

When you use this command, the system will prompt you to confirm the operation before deleting all the static routes.

To delete one static route, use the undo ip route-static command. To delete all static routes, including the default route, use the delete static-routes all command.

Examples

# Delete all static routes.

<Sysname> system-view

[Sysname] delete static-routes all

This will erase all IPv4 static routes and their configurations, you must reconfigure all static routes.

Are you sure?[Y/N]:y

Related commands

ip route-static

Field	Description
NibID	ID of the NIB.
Sequence	Sequence number of the NIB.
Type	Type of the NIB.
Flushed	Indicates whether the route with the NIB has been flushed to the FIB.
Age	Elapsed time since the next hop information was last updated.
UserKey0	Reserved data 1.
UserKey1	Reserved data 2.
UserKey2	Reserved data 3.
UserKey3	Reserved data 4.
VrfNthp	This field is not supported in the current software version. Index of the VPN instance to which the next hop belongs. This field displays 0 if the next hop is on the public network.
Nexthop	Next hop address.
IFIndex	Interface index
LocalAddr	Local interface address.
TopoNthp	Index of the topology that contains the next hop. This field displays 0 if the next hop is on the public network.
ExtType	NIB extension type.
Color	This field is not supported in the current software version. Color extended community attribute.
COFlag	This field is not supported in the current software version. Flag of the color extended community attribute.
LinkID	Link ID of the SDWAN TTE connection.
SIDIndex	This field is not supported in the current software version. SID index value.
SRPName	This field is not supported in the current software version. SR-MPLS TE policy name.
OriNexthop	Original next hop address of the route.

Field	Description
NibID	ID of the NIB.
Sequence	Sequence number of the NIB.
Type	Type of the NIB.
Flushed	Indicates whether the route with the NIB has been flushed to the FIB.
Age	Elapsed time since the next hop information was last updated.
UserKey0	Reserved data 1.
VrfNthp	This field is not supported in the current software version. Index of the VPN instance that the next hop belongs to. This field displays 0 if the next hop is on the public network.
UserKey1	Reserved data 2.
UserKey2	Reserved data 3.
UserKey3	Reserved data 4.
Nexthop	Next hop address.
IFIndex	Interface index
LocalAddr	Local interface address.
TopoNthp	This field is not supported in the current software version. Index of the topology that contains the next hop. This field displays 0 if the next hop is on the public network.
ExtType	NIB extension type.
Color	This field is not supported in the current software version. Color extended community attribute.
COFlag	This field is not supported in the current software version. Flag of the color extended community attribute.
LinkID	Link ID of the SDWAN TTE connection.
SIDIndex	This field is not supported in the current software version. SID index value.
SRPName	This field is not supported in the current software version. SR-MPLS TE policy name.
OriNexthop	Original next hop address of the route.
RefCnt	Reference count of the next hop.
FlushRefCnt	Reference count of the next hop that is flushed to the FIB.
Flag	Flag of the next hop.
Version	Version of the next hop.
x nexthop(s)	Number of next hops.
PrefixIndex	Prefix index of the next hop for an ECMP route.
OrigNexthop	Original next hop.
RelyDepth	Recursion depth.
RealNexthop	Real next hop.
Interface	Output interface.
localAddr	Local interface address.
TunnelCnt	Number of tunnels after route recursion.
Vrf	This field is not supported in the current software version. VPN instance name. For the public network, this field displays default-vrf.
TunnelID	ID of the tunnel after route recursion.
Topology	This field is not supported in the current software version. Topology name. The topology name for the public network is base.
Weight	ECMP route weight. This field displays 0 for non-ECMP routes.
Flags	Flags of the detailed next hop.
SRPolicyNID	This field is not supported in the current software version. NIB ID of the route obtained from an SR-MPLS TE policy through route recursion.
SRInterface	This field is not supported in the current software version. Output interface of the route obtained from the SR-MPLS TE policy through route recursion.
ColorWeight	This field is not supported in the current software version. Weight value of the color attribute in the SR-MPLS TE policy.
Locator	This field is not supported in the current software version. IPv6 prefix of the locator to which the SID belongs. If no locator is available, this field displays N/A.
OrigLinkID	Original link ID of the SDWAN TTE connection.
RealLinkID	Real link ID of the SDWAN TTE connection.

display route-static routing-table

Use display route-static routing-table to display static routing table information.

Syntax

display route-static routing-table [ ip-address { mask-length | mask } ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

ip-address: Specifies the destination IP address in dotted decimal notation. If you do not specify this argument, the command displays all static routing table information.

mask-length: Specifies the mask length, an integer in the range of 0 to 32.

mask: Specifies the subnet mask in dotted decimal notation.

Examples

# Display static routing table information.

<Sysname> display route-static routing-table

Total number of routes: 24

Status: * - valid

*Destination: 0.0.0.0/0

NibID: 0x1100000a NextHop: 2.2.2.10

MainNibID: N/A BkNextHop: N/A

BkNibID: N/A Interface: Vlan-interface11

TableID: 0x2 BkInterface: Vlan-interface12

Flag: 0x82d01 BfdSrcIp: N/A

DbIndex: 0xd BfdIfIndex: 0x0

Type: Normal BfdVrfIndex: 0

TrackIndex: 0xffffffff Label: NULL

Preference: 60 vrfIndexDst: 0

BfdMode: N/A vrfIndexNH: 0

Permanent: 0 Tag: 0

Destination: 0.0.0.0/0

NibID: 0x1100000b NextHop: 2.2.2.11

MainNibID: N/A BkNextHop: N/A

BkNibID: N/A Interface: Vlan-interface13

TableID: 0x2 BkInterface: Vlan-interface14

Flag: 0x82d01 BfdSrcIp: N/A

DbIndex: 0xd BfdIfIndex: 0x0

Type: Normal BfdVrfIndex: 0

TrackIndex: 0xffffffff Label: NULL

Preference: 60 vrfIndexDst: 0

BfdMode: N/A vrfIndexNH: 0

Permanent: 0 Tag: 0

...

Table 3 Command output

Field	Description
destination	Destination address/prefix.
NibID	ID of the NIB.
MainNibID	ID of the primary next hop for static route FRR.
BkNibID	ID of the backup next hop for static route FRR.
NextHop	Next hop address.
BkNextHop	Backup next hop address.
Interface	Output interface of the route. (If an SRv6 TE policy or SR-MPLS TE policy is obtained through route recursion for the route, this field displays the policy name.)
BkInterface	Backup output interface. (If an SRv6 TE policy or SR-MPLS TE policy is obtained through route recursion for the route, this field displays the policy name.)
TableID	ID of the table to which the route belongs.
Flag	Flag of the route.
DbIndex	Index of the database to which the route belongs.
Type	Route type: · Normal. · DHCP. · NAT.
BfdSrcIp	This field is not supported in the current software version. Source IP address of the indirect BFD session.
BfdIfIndex	This field is not supported in the current software version. Index of the interface where BFD is enabled.
BfdVrfIndex	This field is not supported in the current software version. Index of the VPN instance where BFD is enabled. This field displays 0 if BFD is enabled for the public network.
BfdMode	This field is not supported in the current software version. BFD session mode: · N/A—No BFD session is configured. · Ctrl—Control packet mode · Echo—Echo packet mode.
TrackIndex	This field is not supported in the current software version. NQA Track index.
vrfIndexDst	This field is not supported in the current software version. Index of VPN instance to which the destination belongs. For the public network, this field displays 0.
vrfIndexNH	This field is not supported in the current software version. Index of the VPN instance to which the next hop belongs. For the public network, this field displays 0.
Permanent	Permanent static route flag. 1 indicates a permanent static route.

ip route-static

Use ip route-static to configure a static route.

Use undo ip route-static to delete a static route.

Syntax

ip route-static dest-address { mask-length | mask } interface-type interface-number [ next-hop-address [ nexthop-index index-string ] | dhcp ] [ backup-interface interface-type interface-number [ backup-nexthop backup-nexthop-address ] [ permanent ] | permanent | track track-entry-number ] [ preference preference ] [ tag tag-value ] [ recursive-lookup ] [ description text ]

ip route-static dest-address { mask-length | mask } next-hop-address [ nexthop-index index-string ] [ recursive-lookup { host-route | longest-match } ] [ permanent | track track-entry-number ] [ preference preference ] [ tag tag-value ] [ recursive-lookup ] [ description text ]

ip route-static group group-name interface-type interface-number [ next-hop-address | dhcp ] [ backup-interface interface-type interface-number [ backup-nexthop backup-nexthop-address ] [ permanent ] | permanent | track track-entry-number ] [ preference preference ] [ tag tag-value ] [ recursive-lookup ] [ description text ]

ip route-static group group-name next-hop-address [ recursive-lookup { host-route | longest-match } ] | permanent | track track-entry-number ] [ preference preference ] [ tag tag-value ] [ recursive-lookup ] [ description text ]

undo ip route-static { dest-address { mask-length | mask } | group group-name } [ interface-type interface-number [ next-hop-address ] | next-hop-address | dhcp ]

Default

No static route is configured.

Views

System view

Predefined user roles

network-admin

Parameters

dest-address: Specifies the destination IP address of the static route, in dotted decimal notation.

mask-length: Specifies the mask length, an integer in the range of 0 to 32.

mask: Specifies the subnet mask in dotted decimal notation.

group group-name: Specifies a static route group by its name, a case-sensitive string of 1 to 31 characters.

interface-type interface-number: Specifies an output interface by its type and number. For more information, see Layer 3—IP Routing Configuration Guide.

next-hop-address: Specifies the IP address of the next hop, in dotted decimal notation. For more information, see Layer 3—IP Routing Configuration Guide.

dhcp: Specifies the default router designated by the DHCP server for the output interface as the next hop of the static route.

nexthop-index index-string: Specifies the index of the next hop. The index-string argument represents the index, which is a case-insensitive string of 1 to 93 characters. If you do not specify an index for the next hop, the static route uses the output interface and the IP address of the next hop as the next hop index. Do not specify the same next hop index for routes to the same destination.

recursive-lookup host-route: Specifies only host routes for static route recursion.

recursive-lookup longest-match: Recurses the static route to the route with the longest matching mask.

backup-interface interface-type interface-number: Specifies a backup output interface by its type and number. If the backup output interface is an NBMA interface or broadcast interface and not a P2P interface, you must specify the backup next hop address.

backup-nexthop backup-nexthop-address: Specifies a backup next hop address.

permanent: Specifies the route as a permanent static route. If you specify this keyword, the static route is always active regardless of the output interface status. If the output interface is down, the permanent static route is still active.

track track-entry-number: Associates the static route with a track entry specified by its number in the range of 1 to 1024. For more information about Track, see High Availability Configuration Guide.

preference preference: Specifies a preference for the static route, in the range of 1 to 255. The default is 60.

tag tag-value: Sets a tag value for marking the static route, in the range of 1 to 4294967295. The default is 0.

recursive-lookup: Enables support for next hop recursion loops for the IPv4 static route. If you do not specify this keyword, the device does not support next hop recursion loops for the IPv4 static route.

description text: Configures a description of 1 to 60 characters for the static route. The description can include special characters, such as the space, except the question mark (?).

Usage guidelines

If the destination IP address and the mask are both 0.0.0.0 (or 0), the configured route is a default route. The default route is used for forwarding a packet matching no entry in the routing table.

Implement different routing policies to configure different route preferences. For example, to enable load sharing for multiple routes to the same destination, assign the same preference to the routes. To enable the routes to back up one another, assign different preferences to them.

Follow these guidelines when you specify the output interface or the next hop address of the static route:

· If the output interface is a Null 0 interface, no next hop address is required.

· If the output interface is a point-to-point interface, you can specify only the output interface. You do not need to change the configuration of the route even if the peer address is changed.

· NBMA or P2MP interfaces need IP address-to-link layer address mappings for successful packet delivery. As a best practice, specify the next hop address for the route at the same time if the output interface is an NBMA or P2MP interface.

· If the output interface is a broadcast interface, the device might have multiple next hops. Therefore, you must specify both the output interface and next hop IP address.

Follow these guidelines when you configure a static route:

· If a static route needs route recursion, the associated track entry must monitor the next hop of the related route instead of that of the recursive static route. Otherwise, a valid route might be mistakenly considered invalid.

· Do not specify the permanent keyword together with the track keyword.

If you specify a static route group, all prefixes in the static route group will be assigned the next hop and output interface specified by using this command.

After an interface obtains an IP address and gateway address through DHCP, the device automatically generates a static route with the interface as the output interface. The destination address of the static route is 0.0.0.0/0 and the next hop of the static route is the default router (the gateway address designated by the DHCP server). This static route cannot form ECMP routes with manually configured static routes. The device uses this static route to guide traffic forwarding only after the manually configured static routes become invalid.

Specify the dhcp keyword to use both the automatically generated static route and the manually configured static routes to guide traffic forwarding. This keyword is applicable when the device has dual egress WAN links.

The dhcp keyword enables the device to automatically generate a static route destined for the specified network with the DHCP-designated default router of the output interface as the next hop. This static route takes effect only after the output interface obtains an IP address and gateway address through DHCP, and becomes invalid upon the DHCP lease expiration. The next hop of this static route changes as the gateway address of the output interface changes. In addition, this static route can form ECMP routes with manually configured static routes.

To specify the dhcp keyword, make sure the output interface of the static route is a broadcast interface.

If you do not specify the recursive-lookup longest-match or recursive-lookup host-route keywords for a static route, the device preferentially recurses the static route to a direct route. If no matching direct route is found, the device recurses the static route to the route with the longest matching mask. This mechanism might cause packet forwarding failure. When the destination subnet of a direct route contains the next hop address of the static route, the device recurses the next hop of the static route to that direct route. In this case, the device determines that the next hop of the static route is directly connected. However, the next hop might be incorrect, which result in forwarding failure for packets that match the static route.

If you specify the recursive-lookup longest-match keywords for a static route, the device will recurse the static route to the route with the longest matching mask to ensure that the next hop is correct after recursion. If you specify the recursive-lookup host-route keywords, the device can recurse the static route only to a host route with a prefix of 32 bits. The static route is active only when the host route is reachable.

A recursion loop occurs when an IPv4 static route recurses to a related route whose destination address contains the destination address of the IPv4 static route. For example, a recursion loop occurs when the IPv4 static route destined for 10.1.0.0/24 recurses to a related route whose destination address is 10.1.0.0/16.

· If the recursive-lookup keyword is not specified, the recursion loop results in route recursion failure. The device further looks up for a related route.

· If the recursive-lookup keyword is specified, the device determines that the recursion succeeds if the output interface of the related route is an interface directly connected to the device.

If the output interface of an IPv4 static route is found through recursion loops, routing protocols on the device cannot advertise the IPv4 static route to other devices.

The recursive-lookup host-route and recursive-lookup keywords are mutually exclusive. You cannot specify both of the keywords.

Examples

# Configure a static route, whose destination address is 1.1.1.1/24, next hop address is 2.2.2.2, tag value is 45, and description information is for internet.

<Sysname> system-view

[Sysname] ip route-static 1.1.1.1 24 2.2.2.2 tag 45 description for internet

Related commands

display ip routing-table protocol

ip route-static-group

prefix

ip route-static default-preference

Use ip route-static default-preference to configure a default preference for static routes.

Use undo ip route-static default-preference to restore the default.

Syntax

ip route-static default-preference default-preference

undo ip route-static default-preference

Default

The default preference of static routes is 60.

Views

System view

Predefined user roles

network-admin

Parameters

default-preference: Specifies a default preference for static routes, in the range of 1 to 255.

Usage guidelines

If no preference is specified for a static route, the default preference applies.

When the default preference is reconfigured, it applies only to newly added static routes.

Examples

# Set a default preference of 120 for static routes.

<Sysname> system-view

[Sysname] ip route-static default-preference 120

Related commands

display ip routing-table protocol

ip route-static fast-reroute auto

Use ip route-static fast-reroute auto to configure static route FRR to automatically select a backup next hop.

Use undo ip route-static fast-reroute auto to disable static route FRR from automatically selecting a backup next hop.

Syntax

ip route-static fast-reroute auto

undo ip route-static fast-reroute auto

Default

Static route FRR is disabled from automatically selecting a backup next hop.

Views

System view

Predefined user roles

network-admin

Examples

# Configure static route FRR to automatically select a backup next hop.

<Sysname> system-view

[Sysname] ip route-static fast-reroute auto

ip route-static-group

Use ip route-static-group to create a static route group and enter its view, or enter the view of an existing static route group.

Use undo ip route-static-group to delete a static route group.

Syntax

ip route-static-group group-name

undo ip route-static-group group-name

Default

No static route groups exist.

Views

System view

Predefined user roles

network-admin

Parameters

group-name: Specifies the static route group name, a case-sensitive string of 1 to 31 characters.

Examples

# Create static route group test and enter its view.

<Sysname> system-view

[Sysname] ip route-static-group test

[Sysname-route-static-group-test]

Related commands

ip route-static

prefix

Use prefix to add a static route prefix to a static route group.

Use undo prefix to delete a static route prefix from a static route group.

Syntax

prefix dest-address { mask-length | mask }

undo prefix dest-address { mask-length | mask }

Default

No static route prefix is added to a static route group.

Views

Static route group view

Predefined user roles

network-admin

Parameters

dest-address: Specifies the destination IP address of the static route, in dotted decimal notation.

mask-length: Specifies the mask length, an integer in the range of 0 to 32.

mask: Specifies the subnet mask in dotted decimal notation.

Usage guidelines

Execute this command repeatedly to add multiple static route prefixes to a static route group.

After you add static route prefixes to a static route group, you can specify that group in the ip route-static group command to configure static routes with the prefixes. To configure more static routes, you only need to add new static route prefixes to the group.

Examples

# Add static route prefix 1.1.1.1/32 to static route group test.

<Sysname> system-view

[Sysname] ip route-static-group test

[Sysname-route-static-group-test] prefix 1.1.1.1 32

Related commands

ip route-static

ip route-static-group

05-Network Connectivity

Static routing commands

delete static-routes all

display route-static nib

display route-static routing-table

ip route-static

ip route-static default-preference

ip route-static fast-reroute auto

ip route-static-group

prefix

Cloud & AI

Intelligent Connection

Intelligent Computing

Intelligent Storage

Security

SMB Products

Intelligent Terminal Products

Industry Solutions

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Technical Blogs

Training & Certification

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Partner Business Management

Service Business

Profile

News & Events

Online Exhibition Center

Contact Us