Contents

IPv6 static routing commands· 1

delete ipv6 static-routes all 1

display ipv6 route-static nib· 1

display ipv6 route-static routing-table· 6

ipv6 route-static· 9

ipv6 route-static default-preference· 13

ipv6 route-static nd-request 14

 

IPv6 static routing commands

delete ipv6 static-routes all

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

Syntax

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

Views

System view

Predefined user roles

network-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 IPv6 static routes for the public network.

Usage guidelines

CAUTION: Deleting all IPv6 static routes with caution. This operation might cause network connectivity failure and packet forwarding failure.

 

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

Examples

# Delete all IPv6 static routes.

<Sysname> system-view

[Sysname] delete ipv6 static-routes all

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

Are you sure?[Y/N]:y

Related commands

ipv6 route-static

display ipv6 route-static nib

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

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

nib-id: Specifies a NIB by its ID, a hexadecimal string in the range of 1 to ffffffff.

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

Examples

# Display brief IPv6 static route next hop information.

<Sysname> display ipv6 route-static nib

Total number of nexthop(s): 35

 

      NibID: 0x21000000        Sequence: 0

       Type: 0x41               Flushed: Yes

        Age: 00h01m50s

   UserKey0: 0x0                VrfNthp: 0

   UserKey1: 0x0                Nexthop: 2::3

    IFIndex: 0x0              LocalAddr: ::

     NewUK0: 0x0                 NewUK1: 0x0

     NewUK2: 0x0                 NewUK3: 0x0

     NewUK4: 0x0                 NewUK5: 0x0

     NewUK6: 0x0                 NewUK7: 0x0

   TopoNthp: Invalid            ExtType: 0x0

    FIRType: Normal           Threshold: 0

 

      NibID: 0x21000001        Sequence: 1

       Type: 0x41               Flushed: Yes

        Age: 00h01m50s

   UserKey0: 0x0                VrfNthp: 0

   UserKey1: 0x0                Nexthop: 3::4

    IFIndex: 0x0              LocalAddr: ::

     NewUK0: 0x0                 NewUK1: 0x0

     NewUK2: 0x0                 NewUK3: 0x0

     NewUK4: 0x0                 NewUK5: 0x0

     NewUK6: 0x0                 NewUK7: 0x0

   TopoNthp: Invalid            ExtType: 0x0

    FIRType: Normal           Threshold: 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.
Age	Elapsed time since the next hop information was last updated.
UserKey0	Reserved data 1.
UserKey1	Reserved data 2.
VrfNthp	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.
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. This field displays Invalid if the next hop is on an IPv6 network, because the router does not support non-base topologies.
ExtType	NIB extension type.
FIRType	Type of the link for the next hop in FIR ECMP mode: ·     Normal. ·     Primary. ·     Secondary.
Threshold	Bandwidth usage level of primary links in FIR ECMP mode.

 

# Display detailed IPv6 static route next hop information.

<Sysname> display ipv6 route-static nib verbose

Total number of nexthop(s): 35

 

      NibID: 0x21000000        Sequence: 0

       Type: 0x41               Flushed: Yes

        Age: 00h01m50s

   UserKey0: 0x0                VrfNthp: 0

   UserKey1: 0x0                Nexthop: 2::3

    IFIndex: 0x0              LocalAddr: ::

     NewUK0: 0x0                 NewUK1: 0x0

     NewUK2: 0x0                 NewUK3: 0x0

     NewUK4: 0x0                 NewUK5: 0x0

     NewUK6: 0x0                 NewUK7: 0x0

   TopoNthp: Invalid            ExtType: 0x0

    FIRType: Normal           Threshold: 0

     RefCnt: 1              FlushRefCnt: 0

       Flag: 0x12               Version: 1

    ExtFlag: 0x0

 1 nexthop(s):

PrefixIndex: 0              OrigNexthop: 2::3

  RelyDepth: 2              RealNexthop: ::

  Interface: NULL0            LocalAddr: ::

  TunnelCnt: 0                      Vrf: default-vrf

   TunnelID: N/A               Topology:

     Weight: 0                    Flags: 0x0

RealFIRType: Normal           RealThres: 0

 

      NibID: 0x21000001        Sequence: 1

       Type: 0x41               Flushed: Yes

        Age: 00h01m50s

   UserKey0: 0x0                VrfNthp: 0

   UserKey1: 0x0                Nexthop: 3::4

    IFIndex: 0x0              LocalAddr: ::

     NewUK0: 0x0                 NewUK1: 0x0

     NewUK2: 0x0                 NewUK3: 0x0

     NewUK4: 0x0                 NewUK5: 0x0

     NewUK6: 0x0                 NewUK7: 0x0

   TopoNthp: Invalid            ExtType: 0x0

    FIRType: Normal           Threshold: 0

     RefCnt: 1              FlushRefCnt: 0

       Flag: 0x12               Version: 1

    ExtFlag: 0x0

 1 nexthop(s):

PrefixIndex: 0              OrigNexthop: 3::4

  RelyDepth: 1              RealNexthop: ::

  Interface: Vlan11           LocalAddr: ::

  TunnelCnt: 0                      Vrf: default-vrf

   TunnelID: N/A               Topology:

     Weight: 0                    Flags: 0x0

RealFIRType: Normal           RealThres: 0

 

...

Table 2 Command output

Field	Description
Total number of nexthop(s)	Total number of NIBs.
NibID	NIB ID.
Sequence	NIB sequence number.
Type	NIB type.
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.
VrfNthp	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.
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	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. This field displays Invalid if the next hop is on an IPv6 network, because the router does not support non-base topologies.
ExtType	NIB extension type.
FIRType	Type of the link for the next hop in FIR ECMP mode: ·     Normal. ·     Primary. ·     Secondary.
Threshold	Bandwidth usage level of primary links in FIR ECMP mode.
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.
ExtFlag	Extended flag 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.
RealNexthop	Real next hop.
Interface	Output interface.
localAddr	Local interface address.
RelyDepth	Recursion depth.
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. This field is blank for IPv6, because IPv6 does not support non-base topologies.
Weight	ECMP route weight. This field displays 0 for non-ECMP routes.
Flags	Flags of the next hop.
RealFIRType	Type of the link for the real next hop in FIR ECMP mode: ·     Normal. ·     Primary. ·     Secondary. The real next hop is the direct next hop found after route recursion.
RealThres	Bandwidth usage level of the primary link to which the real next hop is attached in FIR ECMP mode.

‌

display ipv6 route-static routing-table

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

Syntax

display ipv6 route-static routing-table [ vpn-instance vpn-instance-name ] [ ipv6-address prefix-length ]

Views

Any view

Predefined user roles

network-admin

network-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 IPv6 static routing table information for the public network.

ipv6-address: Specifies the destination IPv6 address.

prefix-length: Specifies the prefix length in the range of 0 to 128.

Examples

# Display IPv6 static routing table information.

<Sysname> display ipv6 route-static routing-table

Total number of routes: 5

 

Status: * - valid

 

*Destination: 1::1/128

       NibID: 0x21000000        NextHop: 2::2

   MainNibID: N/A             BkNextHop: N/A

     BkNibID: N/A             Interface: Vlan-interface11

     TableID: 0xa           BkInterface: N/A

        Flag: 0x80d0a          BfdSrcIp: N/A

     DbIndex: 0x3            BfdIfIndex: 0x0

        Type: Normal        BfdVrfIndex: 0

  TrackIndex: 0xffffffff          Label: NULL

  Preference: 60            vrfIndexDst: 0

     BfdMode: N/A            vrfIndexNH: 0

   Permanent: 0                     Tag: 0

     FIRType: Normal          Threshold: 0

  MicroSegID: 0          RecurseMaskLen: N/A

  FIRLicense: Unrestricted

 

*Destination: 1::1234/128

       NibID: 0x21000000        NextHop: 2::2

   MainNibID: N/A             BkNextHop: N/A

     BkNibID: N/A             Interface: NULL0

     TableID: 0xa           BkInterface: N/A

        Flag: 0x80d0a          BfdSrcIp: N/A

     DbIndex: 0x1            BfdIfIndex: 0x0

        Type: Normal        BfdVrfIndex: 0

  TrackIndex: 0xffffffff          Label: NULL

  Preference: 60            vrfIndexDst: 0

     BfdMode: N/A            vrfIndexNH: 0

   Permanent: 0                     Tag: 0

     FIRType: Normal          Threshold: 0

  MicroSegID: 0          RecurseMaskLen: N/A

  FIRLicense: Unrestricted

 

...

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.
DbIndex	Index of the database to which the route belongs.
Type	Route type: ·     Normal. ·     DHCP. ·     NAT. ·     IPSGT.
BfdSrcIp	Source IPv6 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.
vrfIndexDst	Index of the VPN instance to which the destination belongs. For the public network, this field displays 0.
vrfIndexNH	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.
FIRType	Type of the link for the next hop in FIR ECMP mode: ·     Normal. ·     Primary. ·     Secondary.
Threshold	Bandwidth usage level of primary links in FIR ECMP mode.
MicroSegID	Microsegment ID in the route.
RecurseMaskLen	Exact mask length for route recursion. If the device uses the longest match principle for route recursion, this field displays N/A.
FIRLicense	License process status for the static route FIR mode: ·     Unrestricted—The static route FIR mode is not controlled by license. ·     Disconnected—The static route FIR mode is controlled by license, but the static route is not connected to the license process. Please check whether the license process is abnormal. ·     Active—The license for controlling the static route FIR mode is active. ·     Inactive—The license for controlling the static route FIR mode is inactive. For more information about licenses, see license management in Fundamentals Configuration Guide.

‌

ipv6 route-static

Use ipv6 route-static to configure an IPv6 static route.

Use undo ipv6 route-static to remove an IPv6 static route.

‌

NOTE: To use the primary and secondary parameters, you must first install a valid license. For more information about licenses, see license management in Fundamentals Configuration Guide.

‌

Syntax

ipv6 route-static ipv6-address prefix-length interface-type interface-number [ next-hop-address ] [ bfd { control-packet | echo-packet } [ bfd-source ipv6-address ] | permanent | track track-entry-number ] [ preference preference ] [ tag tag-value ] [ recursive-lookup ] [ primary threshold-level | secondary ] [ description text ]

ipv6 route-static ipv6-address prefix-length interface-type interface-number next-hop-address track-nd [ preference preference ] [ tag tag-value ] [ description text ]

ipv6 route-static ipv6-address prefix-length [ vpn-instance d-vpn-instance-name ] next-hop-address [ recursive-lookup host-route ] [ bfd control-packet bfd-source ipv6-address | permanent | track track-entry-number ] [ preference preference ] [ tag tag-value ] [ recursive-lookup ] [ description text ]

undo ipv6 route-static ipv6-address prefix-length [ interface-type interface-number [ next-hop-address ] | [ vpn-instance d-vpn-instance-name ] next-hop-address ] [ preference preference ]

ipv6 route-static ipv6-address prefix-length vpn-instance d-vpn-instance-name [ track track-entry-number ] [ preference preference ] [ tag tag-value ] [ description text ]

undo ipv6 route-static ipv6-address prefix-length [ vpn-instance d-vpn-instance-name ] [ preference preference ]

ipv6 route-static vpn-instance s-vpn-instance-name ipv6-address prefix-length interface-type interface-number [ next-hop-address ] [ bfd { control-packet | echo-packet } [ bfd-source ipv6-address ] | permanent | track track-entry-number ] } [ preference preference ] [ tag tag-value ] [ recursive-lookup ] [ primary threshold-level | secondary ] [ description text ]

ipv6 route-static vpn-instance s-vpn-instance-name ipv6-address prefix-length interface-type interface-number next-hop-address track-nd  [ preference preference ] [ tag tag-value ] [ description text ]

ipv6 route-static vpn-instance s-vpn-instance-name ipv6-address prefix-length { next-hop-address [ recursive-lookup host-route ] [ public ] [ bfd control-packet bfd-source ipv6-address | permanent | track track-entry-number ] | vpn-instance d-vpn-instance-name next-hop-address [ recursive-lookup host-route ] [ bfd control-packet bfd-source ipv6-address | permanent | track track-entry-number ] } [ preference preference ] [ tag tag-value ] [ recursive-lookup ] [ description text ]

undo ipv6 route-static vpn-instance s-vpn-instance-name ipv6-address prefix-length [ interface-type interface-number [ next-hop-address ] | next-hop-address [ public ] | vpn-instance d-vpn-instance-name next-hop-address ] [ preference preference ]

ipv6 route-static vpn-instance s-vpn-instance-name ipv6-address prefix-length { public | vpn-instance d-vpn-instance-name } [ track track-entry-number ] [ preference preference ] [ tag tag-value ] [ description text ]

undo ipv6 route-static vpn-instance s-vpn-instance-name ipv6-address prefix-length [ public | vpn-instance d-vpn-instance-name ] [ preference preference ]

Default

No IPv6 static route is configured.

Views

System view

Predefined user roles

network-admin

Parameters

ipv6-address prefix-length: Specifies the IPv6 address and prefix length.

interface-type interface-number: Specifies an output interface by its type and number. If the output interface is an NBMA interface or broadcast interface and not a point-to-point (P2P) interface, the next hop address must be specified.

next-hop-address: Specifies the next hop IPv6 address.

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

bfd: Enables BFD to detect reachability of the static route's next hop.

control-packet: Specifies the BFD control packet mode.

bfd-source ipv6-address: Specifies the source IPv6 address of BFD packets.

echo-packet: Specifies the BFD echo packet mode.

permanent: Specifies the IPv6 route as a permanent IPv6 static route. After you specify this keyword, the static route will always be active, even if the output interface is down.

track track-entry-number: Associates the IPv6 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.

public: Specifies the public network. If you specify this keyword following the next-hop-address argument, the next hop 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 IPv6 static route. If you specify the next-hop-address argument without specifying the public keyword, the device searches for the output interface in the source VPN instance based on the next hop address for packets matching the IPv6 static route. If you specify the public keyword without specifying the next-hop-address argument, the device searches for the output interface in the public network for packets matching the IPv6 static route.

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 you do not specify the next-hop-address argument following this option, the device searches for the output interface in the specified destination VPN instance for packets matching the IPv6 static route. If you specify the next-hop-address argument and this option, the device searches for the output interface in the specified destination VPN instance based on the specified next hop address for packets matching the IPv6 static route. If you specify a destination VPN instance without specifying a next hop address, the destination VPN instance cannot be the same as the source VPN instance.

track-nd: Associates the IPv6 static route with the ND entry corresponding to the next hop of the IPv6 static route. If you specify this keyword and the ND entry corresponding to the next hop of the IPv6 static route does not exist, the system will not activate the IPv6 static route. If you do not specify this keyword, the activation status of the IPv6 static route is irrelevant to the ND entry. As a best practice when you use this keyword, use the ipv6 route-static nd-request command to configure the device to periodically send ND requests to the next hop of the IPv6 static route to prevent the ND entry from aging and causing the IPv6 static route to become inactive.

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

tag tag-value: Sets a tag 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.

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

primary threshold-level: Specifies the IPv6 static route as a primary link in FIR ECMP mode and sets the bandwidth usage level of the primary link. The value for the threshold argument can be 70, 75, 80, 85, 90, 95, or 100, in percentage. The primary link bandwidth usage threshold depends on the setting of this option and the upper and lower bandwidth usage thresholds for the primary link in FIR ECMP mode, as described in the usage guidelines. For more information about FIR ECMP mode, see basic IP routing in Layer 3—IP Routing Configuration Guide.

secondary: Specifies the IPv6 static route as a secondary link in FIR ECMP mode.

description text: Configures a description for the IPv6 static route, which consists of 1 to 60 characters, including special characters such as the space, but excluding the question mark (?).

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

Usage guidelines

An IPv6 static route that has the destination address configured as ::/0 (a prefix length of 0) is the default IPv6 route. If the destination address of an IPv6 packet does not match any entry in the routing table, this default route is used to forward the packet.

Follow these guidelines to configure the output interface, next hop address, or both for a static route:

·     If the output interface is a broadcast interface or an NBMA interface, the next hop address must be specified.

·     If the output interface is a P2P 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.

Follow these guidelines when you configure BFD for IPv6 static routes:

·     If you specify a source IPv6 address for BFD packets on the local device, you must specify that IPv6 address as the next hop IPv6 address on the peer device.

·     If you specify a non-P2P output interface and a direct next hop, specify the bfd-source ipv6-address option as a best practice. Make sure the source IPv6 address of BFD packets meets the following requirements:

¡     The address is the same as the IPv6 address of the output interface.

¡     The address is on the same network segment as the next hop IPv6 address of the same type.

For example, if the next hop IPv6 address is a link-local address, the source IPv6 address of BFD packets must also be a link-local address.

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

·     The next hop IPv6 address of echo packets must be a global unicast address.

To specify the recursive-lookup host-route keyword, you must use the ipv6 nd route-direct advertise command to enable ND direct route advertisement to advertise 128-bit host routes on the following interfaces:

·     The output interface corresponding to the next hop of the static route.

·     The peer interface connected to the output interface.

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

A recursion loop occurs when an IPv6 static route recurses to a related route whose destination address contains the destination address of the IPv6 static route. For example, a recursion loop occurs when the IPv6 static route destined for 4::2/64 recurses to a related route whose destination address is 4::2/48.

·     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 IPv6 static route is found through recursion loops, routing protocols on the device cannot advertise the IPv6 static route to other devices.

As a best practice, use the recursive-lookup keyword only in specific scenarios, for example, in a network with microsegment configuration. You can recurse an IPv6 static route to a larger network segment, and apply the associated traffic control policies to the traffic matching the IPv6 static route.

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

If FIR ECMP mode is enabled and multiple IPv6 static ECMP routes are available to reach the same destination, the static routes configured with the primary threshold option are primary links and the static routes configured with the secondary keyword are secondary links.

The upper threshold for the primary link bandwidth usage depends on the setting of the primary threshold-level option and lower and upper thresholds specified in the ecmp mode fir primary threshold command.

·     The IPv6 static route is a primary link if it is not configured with the primary threshold-level option or secondary keyword, but is configured with the ecmp mode fir primary threshold command. The upper threshold for the link bandwidth usage is specified by the upper-threshold argument in the ecmp mode fir primary threshold command in per ten thousand.

·     The IPv6 static route is a primary link if it is configured with the primary threshold-level option, but is not configured with the ecmp mode fir primary threshold command. The upper threshold for the link bandwidth usage is specified by the primary threshold-level option in percentage.

·     If the IPv6 static route is configured with the primary threshold-level option and the ecmp mode fir primary threshold command, the upper threshold for the primary link bandwidth usage is calculated as follows:

a.     For the value range between the bandwidth usage upper threshold specified by the upper-threshold argument (upper) and lower threshold specified by the lower-threshold argument (lower) in the ecmp mode fir primary threshold command, the device evenly divides the value range to six subranges. The span for each subrange (range) is calculated with the formula: range = (upper - lower) ÷ 6.

b.     The device supports seven threshold-level values, from level1 to level7 in ascending order. Each value represents a link bandwidth usage level.

c.     Based on the range value, you can obtain the link bandwidth usage upper threshold of each level as follows:

-     The upper threshold of level1 is lower.

-     The upper threshold of level2 is lower + 1 × range

-     …

-     The upper threshold of level7 is lower + 6 × range = upper

d.     You can obtain the upper threshold for a single primary link bandwidth usage from the previous process.

e.     The effective link bandwidth usage upper threshold on the device takes the smallest value among all primary link bandwidth usage thresholds.

When you configure IPv6 static ECMP routes to reach the same destination, follow these restrictions and guidelines:

·     If you do not specify the secondary keyword or the primary threshold-level option for an IPv6 static route, the IPv6 static route is used as a primary link. The link bandwidth usage level is the maximum value 100 for the threshold-level argument.

·     If multiple primary links are configured with different link bandwidth usage levels by using the threshold-level argument, the effective level is the minimum value among the configured levels.

·     If the IPv6 static ECMP routes are all primary links or all secondary links, the device treats all the links as common links. Packets are distributed among the links for load sharing.

When the device forwards service traffic that matches multiple IPv6 static ECMP routes to reach the same destination, it selects links as follows:

·     The device distributes all service traffic to primary links when the bandwidth usages of all primary links do not exceed the effective upper threshold.

·     The device distributes new service traffic to secondary links for load sharing when the bandwidth usage of any primary link exceeds the effective upper threshold.

·     The device switches traffic from secondary links to primary links when the bandwidth usages of all primary links drop below the effective upper threshold.

Examples

# Configure an IPv6 static route, with the destination address 1:1:2::/64 and next hop 1:1:3::1.

<Sysname> system-view

[Sysname] ipv6 route-static 1:1:2:: 64 1:1:3::1

Related commands

display ipv6 routing-table protocol

ipv6 nd route-direct advertise (Layer 3—IP Services Command Reference)

ipv6 route-static default-preference

Use ipv6 route-static default-preference to set a default preference for IPv6 static routes.

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

Syntax

ipv6 route-static default-preference default-preference

undo ipv6 route-static default-preference

Default

The default preference of IPv6 static routes is 60.

Views

System view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

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

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

Examples

# Set a default preference of 120 for IPv6 static routes.

<Sysname> system-view

[Sysname] ipv6 route-static default-preference 120

Related commands

display ipv6 routing-table protocol

ipv6 route-static nd-request

Use ipv6 route-static nd-request to enable periodic sending of ND requests to the next hops of IPv6 static routes.

Use undo ipv6 route-static nd-request to disable periodic sending of ND requests to the next hops of IPv6 static routes.

Syntax

ipv6 route-static nd-request [ interval interval ]

undo ipv6 route-static nd-request

Default

Periodic sending of ND requests to the next hops of IPv6 static routes is disabled.

Views

System view

Predefined user roles

network-admin

Parameters

interval: Specifies an ND request sending interval in the range of 1 to 300 seconds. The default value is 5.

Usage guidelines

As a best practice, use this command when the following types of IPv6 static routes exist on the device:

·     IPv6 static routes that recurse to host routes, which include the following IPv6 static routes:

¡     IPv6 static routes with the recursive-lookup host-route keywords specified to recurse only to host routes.

¡     IPv6 static routes that recurse to host routes according to routing policies (configured by using the protocol nexthop recursive-lookup command).

The device might delete the ND entry for the next hop host address of an IPv6 static route after that entry ages out because the device cannot update that entry in time. As a result, the device does not have the host route of the directly connected device in the IPv6 routing table for that IPv6 static route. In this case, route recursion fails and that IPv6 static route cannot be activated.

·     IPv6 static routes with the track-nd keyword specified to associate their next hops with the ND entries for these next hops. The device might delete the ND entry for the next hop address of an IPv6 static route after that entry ages out because the device cannot update that entry in time. As a result, that IPv6 static route cannot be activated.

For IPv6 static routes that recurse to host routes, the ipv6 route-static nd-request command enables the device to periodically send ND requests to the next hops of the IPv6 static routes that meet the following requirements:

·     The IPv6 static routes have no output interfaces specified.

·     The IPv6 static routes fail the next-hop recursion.

When the device receives an ND response from the next hop host of an IPv6 static route, it automatically performs the following operations:

1.     Adds the host route to the routing table.

2.     Activates the IPv6 static route that recurses to the host route.

3.     Stops sending ND requests to the host.

For IPv6 static routes with the track-nd keyword specified, the ipv6 route-static nd-request command enables the device to periodically send ND requests to the next hops of the IPv6 static routes associated with next hop ND entries. When the device receives an ND response from the next hop of an IPv6 static route, it automatically activates that IPv6 static route and stops sending ND requests to the next hop of that IPv6 static route.

For more information about ND, see IPv6 neighbor discovery in Layer 3—IP Services Configuration Guide.

Examples

# Enable sending of ND requests to the next hops of IPv6 static routes and set the sending interval to 10 seconds.

<Sysname> system-view

[Sysname] ipv6 route-static nd-request interval 10

Related commands

ipv6 route-static

protocol nexthop recursive-lookup