Contents

Static routing commands· 1

delete static-routes all 1

display route-static nib· 1

display route-static routing-table· 7

ip route-static· 9

ip route-static default-preference· 13

ip route-static fast-reroute auto· 13

ip route-static primary-path-detect bfd echo· 14

ip route-static recursive-lookup tunnel 14

ip route-static vpn-instance· 15

ip route-static-group· 19

prefix· 20

 

Static routing commands

Non-default vSystems do not support some of the static routing commands. For information about vSystem support for a command, see the usage guidelines on that command. For information about vSystem, see Virtual Technologies Configuration Guide.

delete static-routes all

Use delete static-routes all to delete all static routes.

Syntax

delete [ vpn-instance vpn-instance-name ] static-routes all

Views

System view

Predefined user roles

network-admin

context-admin

vsys-admin

Parameters

 

vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify a VPN instance, the command deletes all static routes for the public network.

Usage guidelines

CAUTION: 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

display route-static nib

Use display route-static nib to display static route next hop information.

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

context-admin

context-operator

Parameters

nib-id: Specifies a NIB by its ID, a hexadecimal string of 1 to ffffffff. If you do not specify this argument, the command displays all static route next hop information.

verbose: Displays detailed static route next hop information. If you do not specify this keyword, the command displays brief static route next hop information.

Usage guidelines

Non-default vSystems do not support this command.

Examples

# Displays brief static route next hop information.

<Sysname> display route-static nib

Total number of nexthop(s): 44

 

      NibID: 0x11000000        Sequence: 0

       Type: 0x21               Flushed: Yes

   UserKey0: 0x111              VrfNthp: 0

   UserKey1: 0x0                Nexthop: 0.0.0.0

    IFIndex: 0x111            LocalAddr: 0.0.0.0

     NewUK0: 0x0                 NewUK1: 0x0

     NewUK2: 0x0                 NewUK3: 0x0

     NewUK4: 0x0                 NewUK5: 0x0

     NewUK6: 0x0                 NewUK7: 0x0

   TopoNthp: 0                  ExtType: 0x0

      Color: 0                   COFlag: 0x0

     LinkID: 0x0

   SIDIndex: 0x0                SRPName:

 OriNexthop: 0.0.0.0

 

      NibID: 0x11000001        Sequence: 1

       Type: 0x41               Flushed: Yes

   UserKey0: 0x0                VrfNthp: 5

   UserKey1: 0x0                Nexthop: 2.2.2.2

    IFIndex: 0x0              LocalAddr: 0.0.0.0

     NewUK0: 0x0                 NewUK1: 0x0

     NewUK2: 0x0                 NewUK3: 0x0

     NewUK4: 0x0                 NewUK5: 0x0

     NewUK6: 0x0                 NewUK7: 0x0

   TopoNthp: 0                  ExtType: 0x0

      Color: 0                   COFlag: 0x0

     LinkID: 0x0

   SIDIndex: 0x0                SRPName:

 OriNexthop: 0.0.0.0

 

...

Table 1 Command output

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.
UserKey0	Reserved data 1.
UserKey1	Reserved data 2.
VrfNthp	Index of the VPN instance that the next hop belongs to. This field displays 0 if the next hop is on the public network.
Nexthop	Next hop address.
IFIndex	Interface index
LocalAddr	Local interface address.
NewUK0	New reserved data 1.
NewUK1	New reserved data 2.
NewUK2	New reserved data 3.
NewUK3	New reserved data 4.
NewUK4	New reserved data 5.
NewUK5	New reserved data 6.
NewUK6	New reserved data 7.
NewUK7	New reserved data 8.
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	This field is not supported in the current software version. 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. If the route is obtained from a BGP UPDATE message, the address is the next hop IP address in the BGP UPDATE message.

 

# Displays detailed static route next hop information.

<Sysname> display route-static nib verbose

Total number of nexthop(s): 44

 

      NibID: 0x11000000        Sequence: 0

       Type: 0x21               Flushed: Yes

   UserKey0: 0x111              VrfNthp: 0

   UserKey1: 0x0                Nexthop: 0.0.0.0

    IFIndex: 0x111            LocalAddr: 0.0.0.0

     NewUK0: 0x0                 NewUK1: 0x0

     NewUK2: 0x0                 NewUK3: 0x0

     NewUK4: 0x0                 NewUK5: 0x0

     NewUK6: 0x0                 NewUK7: 0x0

   TopoNthp: 0                  ExtType: 0x0

      Color: 0                   COFlag: 0x0

     LinkID: 0x0

   SIDIndex: 0x0                SRPName:

 OriNexthop: 0.0.0.0

     RefCnt: 2              FlushRefCnt: 0

       Flag: 0x2                Version: 1

 1 nexthop(s):

PrefixIndex: 0              OrigNexthop: 0.0.0.0

  RelyDepth: 0              RealNexthop: 0.0.0.0

  Interface: NULL0            LocalAddr: 0.0.0.0

  TunnelCnt: 0                      Vrf: default-vrf

   TunnelID: N/A               Topology: base

     Weight: 1000000              Flags: 0x0

SRPolicyNID: 4294967295     SRInterface:

ColorWeight: 0                  Locator: N/A

 OrigLinkID: 0x0             RealLinkID: 0x0

 

      NibID: 0x11000001        Sequence: 1

       Type: 0x41               Flushed: Yes

   UserKey0: 0x0                VrfNthp: 5

   UserKey1: 0x0                Nexthop: 2.2.2.2

    IFIndex: 0x0              LocalAddr: 0.0.0.0

     NewUK0: 0x0                 NewUK1: 0x0

     NewUK2: 0x0                 NewUK3: 0x0

     NewUK4: 0x0                 NewUK5: 0x0

     NewUK6: 0x0                 NewUK7: 0x0

   TopoNthp: 0                  ExtType: 0x0

      Color: 0                   COFlag: 0x0

     LinkID: 0x0

   SIDIndex: 0x0                SRPName:

 OriNexthop: 0.0.0.0

     RefCnt: 1              FlushRefCnt: 0

       Flag: 0x12               Version: 1

 2 nexthop(s):

PrefixIndex: 0              OrigNexthop: 2.2.2.2

  RelyDepth: 7              RealNexthop: 8.8.8.8

  Interface: GE1/0/1          LocalAddr: 12.12.12.12

  TunnelCnt: 0                      Vrf: default-vrf

   TunnelID: N/A               Topology: base

     Weight: 1000000              Flags: 0x0

SRPolicyNID: 4294967295     SRInterface:

ColorWeight: 0                  Locator: N/A

 OrigLinkID: 0x0             RealLinkID: 0x0

PrefixIndex: 0              OrigNexthop: 2.2.2.2

  RelyDepth: 9              RealNexthop: 0.0.0.0

  Interface: NULL0            LocalAddr: 0.0.0.0

  TunnelCnt: 0                      Vrf: default-vrf

   TunnelID: N/A               Topology: base

     Weight: 1000000              Flags: 0x0

SRPolicyNID: 4294967295     SRInterface:

ColorWeight: 0                  Locator: N/A

 OrigLinkID: 0x0             RealLinkID: 0x0

 

...

Table 2 Command output

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.
UserKey0	Reserved data 1.
VrfNthp	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.
Nexthop	Next hop address.
IFIndex	Interface index
LocalAddr	Local interface address.
TopoNthp	Non-base topologies are 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.
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	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	This field is not supported in the current software version. Original link ID of the SDWAN TTE connection.
RealLinkID	This field is not supported in the current software version. 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 [ vpn-instance vpn-instance-name ] [ ip-address { mask-length | mask } ]

Views

Any view

Predefined user roles

network-admin

network-operator

context-admin

context-operator

vsys-admin

vsys-operator

Parameters

 

vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify a VPN instance, the command displays static routing table information for the public network.

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: GigabitEthernet1/0/1

     TableID: 0x2            BkInterface: GigabitEthernet1/0/2

        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: GigabitEthernet1/0/3

     TableID: 0x2            BkInterface: GigabitEthernet1/0/4

        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.
BkInterface	Backup output interface.
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. ·     IPsec.
BfdSrcIp	Source IP address of the indirect BFD session.
BfdIfIndex	Index of the interface where BFD is enabled.
BfdVrfIndex	Index of the VPN instance where BFD is enabled. This field displays 0 if BFD is enabled for the public network.
BfdMode	BFD session mode: ·     N/A—No BFD session is configured. ·     Ctrl—Control packet mode ·     Echo—Echo packet mode.
TrackIndex	NQA Track index.
Label	Label of the route.
vrfIndexDst	Index of VPN instance that the destination belongs to. For the public network, this field displays 0.
vrfIndexNH	Index of the VPN instance that the next hop belongs to. 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

In non-default vSystem view:

ip route-static { dest-address { mask-length | mask } | group group-name } interface-type interface-number [ dhcp | next-hop-address ] [ backup-interface interface-type interface-number [ backup-nexthop backup-nexthop-address ] [ permanent ] | bfd { control-packet | echo-packet | static session-name } | permanent | track track-entry-number ] [ ldp-sync ] [ preference preference ] [ tag tag-value ] [ description text ]

ip route-static { dest-address { mask-length | mask } | group group-name } next-hop-address [ bfd control-packet bfd-source ip-address | permanent | track track-entry-number ] [ preference preference ] [ tag tag-value ] [ description text ]

ip route-static { dest-address { mask-length | mask } | group group-name } vpn-instance d-vpn-instance-name next-hop-address [ bfd control-packet bfd-source ip-address | permanent | track track-entry-number ] [ preference preference ] [ tag tag-value ] [ description text ]

ip route-static dest-address { mask-length | mask } vpn-instance d-vpn-instance-name [ track track-entry-number ] [ preference preference ] [ tag tag-value ] [ description text ]

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

In non-default vSystem view:

ip route-static dest-address { mask-length | mask } interface-type interface-number [ dhcp | next-hop-address ] [ backup-interface interface-type interface-number [ backup-nexthop backup-nexthop-address ] [ permanent ] | bfd { control-packet | echo-packet | static session-name } | permanent | track track-entry-number ] [ ldp-sync ] [ preference preference ] [ tag tag-value ] [ description text ]

ip route-static dest-address { mask-length | mask } public [ track track-entry-number ] [ preference preference ] [ tag tag-value ] [ description text ]

undo ip route-static dest-address { mask-length | mask } [ interface-type interface-number [ next-hop-address ] | next-hop-address | public ] [ preference preference ]

Default

No static route is configured.

Views

System view

Predefined user roles

network-admin

context-admin

vsys-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.

vpn-instance d-vpn-instance-name: Specifies a destination MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If a destination VPN instance is specified, packets will search for the output interface in the destination VPN instance based on the configured next hop address.

public: Specifies the default vSystem where the destination address of the static route resides. If you specify this keyword, you do not need to specify a next hop address.

interface-type interface-number: Specifies an output interface by its type and number. 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.

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.

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.

bfd: Enables BFD to detect reachability of the static route's next hop. When the next hop is unreachable, the system immediately switches to the backup route.

control-packet: Specifies the BFD control mode.

bfd-source ip-address: Specifies the source IP address of BFD packets. As a best practice, specify the loopback interface address.

echo-packet: Specifies the BFD echo mode.

static session-name: Specifies a static BFD session by its name, a case-sensitive string of 1 to 64 characters. You can specify a nonexistent static BFD session. For the configuration to take effect, you must create the static BFD session.

permanent: Specifies the route as a permanent static route. 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 Network Management and Monitoring Configuration Guide.

ldp-sync: Enables LDP and static route synchronization.

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. Tags of routes are used for route control in routing policies. For more information about routing policies, see Layer 3—IP Routing Configuration Guide.

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.

To realize intercommunication between the default vSystem and a non-default vSystem, use the following commands:

·     In the system view of the default vSystem, execute the ip route-static dest-address { mask-length | mask } vpn-instance d-vpn-instance-name [ track track-entry-number ] [ preference preference ] [ tag tag-value ] [ description text ] command. This command allows the default vSystem to access a non-default vSystem. The d-vpn-instance-name argument specifies the name of the VPN instance that has the same name as the non-default vSystem.

·     In the system view of a non-default vSystem, execute the ip route-static dest-address { mask-length | mask } public [ track track-entry-number ] [ preference preference ] [ tag tag-value ] [ description text ] command. This command allows the non-default vSystem to access the default vSystem.

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.

·     Multiple next hops might exist if the output interface is a broadcast interface (for example, an Ethernet interface or VLAN interface). You must specify both the output interface and next hop IP address for the static route.

Follow these guidelines when you configure a static route:

·     Enabling BFD for a flapping route could worsen the route flapping situation. Therefore, use it with caution. For more information about BFD, see Network Management and Monitoring Configuration Guide.

·     For static routing-Track-NQA collaboration, you must configure the same VPN instance ID for the next hop to be detected and the NQA operation.

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

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.

When LDP establishes LSPs based on static routes, if LDP and the static routes are not synchronized, MPLS traffic forwarding might be interrupted. To resolve this issue, specify the ldp-sync keyword to enable LDP and static route synchronization.

After LDP and static route synchronization is enabled, a static route becomes Active only when LDP is converged on the link used by the static route. Before LDP convergence is completed, the static route is in Inactive state. In this way, the device can avoid discarding MPLS packets when no LDP LSP is established on the static route.

On a network where primary and backup LDP LSPs are established based on static routes, LDP and static route synchronization helps minimize traffic interruption when the primary LSP fails:

1.     When the primary LSP fails, LDP and static route synchronization places the static route of the primary LSP to Inactive state. MPLS traffic is switched to the backup LSP.

2.     LDP and static route synchronization keeps the Inactive route state during the recovery of the primary LSP.

3.     After the primary LSP completely recovers, LDP and static route synchronization places the static route to Active state, and then MPLS traffic is switched back to the primary LSP.

LDP and static route synchronization allows the primary LSP and the static route to become available synchronously. This ensures that when MPLS traffic arrives, the LSP has been established, so as to avoid MPLS traffic loss.

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.

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

context-admin

Parameters

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

Usage guidelines

Non-default vSystems do not support this command.

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

context-admin

Usage guidelines

Non-default vSystems do not support this command.

If you execute this command on the default vSystem, this command takes effect on all vSystems.

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 primary-path-detect bfd echo

Use ip route-static primary-path-detect bfd echo to enable BFD echo packet mode for static route FRR.

Use undo ip route-static primary-path-detect bfd to disable BFD echo packet mode for static route FRR.

Syntax

ip route-static primary-path-detect bfd echo

undo ip route-static primary-path-detect bfd

Default

BFD echo packet mode for static route FRR is disabled.

Views

System view

Predefined user roles

network-admin

context-admin

Usage guidelines

Non-default vSystems do not support this command.

This command enables static route FRR to use BFD echo packet mode for fast failure detection on the primary link.

Examples

# Enable BFD echo packet mode for static route FRR.

<Sysname> system-view

[Sysname] ip route-static 1.1.1.1 32 gigabitethernet 1/0/1 2.2.2.2 backup-interface gigabitethernet 1/0/2 backup-nexthop 3.3.3.3

[Sysname] ip route-static primary-path-detect bfd echo

ip route-static recursive-lookup tunnel

Use ip route-static recursive-lookup tunnel to allow static routes to recurse to LSP tunnels.

Use undo ip route-static recursive-lookup tunnel to restore the default.

Syntax

ip route-static recursive-lookup tunnel [ prefix-list ipv4-prefix-list-name ] [ tunnel-policy tunnel-policy-name ]

undo ip route-static recursive-lookup tunnel

Default

Static routes cannot recurse to LSP tunnels.

Views

System view

Predefined user roles

network-admin

context-admin

Parameters

prefix-list ipv4-prefix-list-name: Specifies an IPv4 prefix list by its name, a case-sensitive string of 1 to 63 characters. Only static routes filtered by the specified IPv4 prefix list can recurse to LSP tunnels. If you do not specify an IPv4 prefix list, this command allows all static routes to recurse to LSP tunnels.

tunnel-policy tunnel-policy-name: Specifies a tunnel policy by its name, a case-sensitive string of 1 to 19 characters. Static routes can recurse only to LSP tunnels that match the specified tunnel policy. If you do not specify a tunnel policy, this command allows static routes to recurse to any LSP tunnels.

Usage guidelines

Non-default vSystems do not support this command.

By default, a static route can recurse only to output interfaces and next hops based on IP forwarding. This command allows the device to preferentially recurse static routes to LSP tunnels. If a static route cannot recurse to an LSP tunnel, the device recurses the static route to an output interface and next hop based on IP forwarding.

If you execute this command multiple times, the most recent configuration takes effect.

Examples

# Enable the device to recurse static routes to LSP tunnels.

<Sysname> system-view

[Sysname] ip route-static recursive-lookup tunnel

ip route-static vpn-instance

Use ip route-static vpn-instance to configure a static route in a VPN instance.

Use undo ip route-static vpn-instance to delete a static route from a VPN instance.

Syntax

ip route-static vpn-instance s-vpn-instance-name dest-address { mask-length | mask } interface-type interface-number [ dhcp | next-hop-address ] [ backup-interface interface-type interface-number [ backup-nexthop backup-nexthop-address ] [ permanent ] | bfd { control-packet | echo-packet | static session-name } | permanent | track track-entry-number ] [ ldp-sync ] [ preference preference ] [ tag tag-value ] [ description text ]

ip route-static vpn-instance s-vpn-instance-name dest-address { mask-length | mask } vpn-instance d-vpn-instance-name next-hop-address [ bfd control-packet bfd-source ip-address | permanent | track track-entry-number ] [ preference preference ] [ tag tag-value ] [ description text ]

ip route-static vpn-instance s-vpn-instance-name dest-address { mask-length | mask } next-hop-address [ public ] [ bfd control-packet bfd-source ip-address | permanent | track track-entry-number ] [ preference preference ] [ tag tag-value ] [ description text ]

ip route-static vpn-instance s-vpn-instance-name dest-address { mask-length | mask } vpn-instance d-vpn-instance-name [ track track-entry-number ] [ preference preference ] [ tag tag-value ] [ description text ]

ip route-static vpn-instance s-vpn-instance-name group group-name interface-type interface-number [ dhcp | next-hop-address ] [ bfd { control-packet | echo-packet | static session-name } | backup-interface interface-type interface-number [ backup-nexthop backup-nexthop-address ] [ permanent ] ] [ ldp-sync ] [ preference preference ] [ tag tag-value ] [ description text ]

ip route-static vpn-instance s-vpn-instance-name group group-name next-hop-address [ public ] [ bfd control-packet bfd-source ip-address | permanent | track track-entry-number ] [ preference preference ] [ tag tag-value ] [ description text ]

undo ip route-static vpn-instance s-vpn-instance-name { dest-address { mask-length | mask } | group group-name } [ interface-type interface-number [ dhcp | next-hop-address ] | next-hop-address [ public ] | vpn-instance d-vpn-instance-name next-hop-address ] [ preference preference ]

Default

No static route is configured in a VPN instance.

Views

System view

Predefined user roles

network-admin

context-admin

Parameters

s-vpn-instance-name: Specifies a source MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. Each VPN instance has its own routing table, and the configured static route is installed in the routing tables of the specified VPN instances.

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.

vpn-instance d-vpn-instance-name: Specifies a destination MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If a destination VPN instance is specified, packets will search for the output interface in the destination VPN instance based on the configured next hop address.

interface-type interface-number: Specifies an output interface by its type and number. 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.

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.

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

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

bfd: Enables BFD to detect reachability of the static route's next hop. When the next hop is unreachable, the system immediately switches to the backup route.

control-packet: Specifies the BFD control mode.

bfd-source ip-address: Specifies the source IP address of BFD packets. As a best practice, specify the loopback interface address.

echo-packet: Specifies the BFD echo mode.

static session-name: Specifies a static BFD session by its name, a case-sensitive string of 1 to 64 characters. You can specify a nonexistent static BFD session. For the configuration to take effect, you must create the static BFD session.

permanent: Specifies the route as a permanent static route. 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 Network Management and Monitoring Configuration Guide.

ldp-sync: Enables LDP and static route synchronization.

public: Specifies the public network, which indicates that the specified next hop address is on the public network. The device searches for the output interface in the public network based on the next hop address for packets matching the static route. If you do not specify this keyword or the destination VPN instance, the specified next hop address is in the source VPN instance. The device searches for the output interface in the source VPN instance based on the next hop address for packets matching the static route.

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. Tags of routes are used for route control in routing policies. For more information about routing policies, see Layer 3—IP Routing Configuration Guide.

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

Non-default vSystems do not support this command.

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.

To realize intercommunication between two non-default vSystems, use the ip route-static vpn-instance s-vpn-instance-name dest-address { mask-length | mask } vpn-instance d-vpn-instance-name [ track track-entry-number ] [ preference preference ] [ tag tag-value ] [ description text ] command in the system view of the default vSystem. The s-vpn-instance-name and d-vpn-instance-name arguments specify the names of the VPN instances that have the same names as the non-default vSystems.

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 (for example, an Ethernet interface or VLAN interface), the device uses the next hop IP address to obtain the MAC address of the next hop. Therefore, you must specify both the output interface and next hop IP address.

Follow these guidelines when you configure a static route:

·     Enabling BFD for a flapping route could worsen the route flapping situation. Therefore, use it with caution. For more information about BFD, see Network Management and Monitoring Configuration Guide.

·     For static routing-Track-NQA collaboration, you must configure the same VPN instance ID for the next hop to be detected and the NQA operation.

·     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.

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.

When LDP establishes LSPs based on static routes, if LDP and the static routes are not synchronized, MPLS traffic forwarding might be interrupted. To resolve this issue, specify the ldp-sync keyword to enable LDP and static route synchronization.

After LDP and static route synchronization is enabled, a static route becomes Active only when LDP is converged on the link used by the static route. Before LDP convergence is completed, the static route is in Inactive state. In this way, the device can avoid discarding MPLS packets when no LDP LSP is established on the static route.

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.

Examples

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

<Sysname> system-view

[Sysname] ip route-static vpn-instance vpn1 1.1.1.1 24 vpn-instance vpn2 2.2.2.2 tag 45 description for internet

Related commands

display ip routing-table protocol

ip route-static-group

prefix

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

context-admin

Parameters

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

Usage guidelines

Non-default vSystems do not support this command.

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

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

context-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

Non-default vSystems do not support this command.

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