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:

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

context-admin

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

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

Color: 0 COFlag: 0x0

LinkID: 0x0

SIDIndex: 0x0 SRPName:

OriNexthop: ::

NibID: 0x21000001 Sequence: 1

Type: 0x41 Flushed: Yes

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

Color: 0 COFlag: 0x0

LinkID: 0x0

SIDIndex: 0x0 SRPName:

OriNexthop: ::

...

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

# 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

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

Color: 0 COFlag: 0x0

LinkID: 0x0

SIDIndex: 0x0 SRPName:

OriNexthop: ::

RefCnt: 1 FlushRefCnt: 0

Flag: 0x12 Version: 1

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

SRPolicyNID: 4294967295 SRInterface:

ColorWeight: 0 Locator: N/A

OrigLinkID: 0x0 RealLinkID: 0x0

NibID: 0x21000001 Sequence: 1

Type: 0x41 Flushed: Yes

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

Color: 0 COFlag: 0x0

LinkID: 0x0

SIDIndex: 0x0 SRPName:

OriNexthop: ::

RefCnt: 1 FlushRefCnt: 0

Flag: 0x12 Version: 1

1 nexthop(s):

PrefixIndex: 0 OrigNexthop: 3::4

RelyDepth: 1 RealNexthop: ::

Interface: XGE1/0/5 LocalAddr: ::

TunnelCnt: 0 Vrf: default-vrf

TunnelID: N/A Topology:

Weight: 0 Flags: 0x0

SRPolicyNID: 4294967295 SRInterface:

ColorWeight: 0 Locator: N/A

OrigLinkID: 0x0 RealLinkID: 0x0

...

Table 2 Command output

Field	Description
x nexthop(s)	Number of next hops.
PrefixIndex	Prefix index of the next hop for an ECMP route.
Vrf	VPN instance name. For the public network, this field displays default-vrf.
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.
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.
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.
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 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

context-admin

context-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: Ten-GigabitEthernet2/3/1

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 RecurseMaskLen: N/A

Tag: 0

*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 RecurseMaskLen: N/A

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.
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.
Label	Label of the route.
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.
RecurseMaskLen	Exact mask length for route recursion. If the device uses the longest match principle for route recursion, this field displays N/A.
BfdStatic	Name of the static BFD session associated with the route. If no static BFD session is associated with the route, this field is not available.

ipv6 route-static

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

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

Syntax

ipv6 route-static ipv6-address prefix-length { interface-type interface-number [ next-hop-address ] [ bfd { { control-packet | echo-packet } [ bfd-source ipv6-address ] | static session-name } | permanent | track track-entry-number ] | [ vpn-instance d-vpn-instance-name ] next-hop-address [ bfd { control-packet bfd-source ipv6-address | static session-name } | permanent | track track-entry-number ] } [ preference preference ] [ tag tag-value ] [ description text ]

ipv6 route-static ipv6-address prefix-length interface-type interface-number gateway [ bfd { { control-packet | echo-packet } [ bfd-source ipv6-address ] | static session-name } | track track-entry-number ] [ preference preference ] [ tag tag-value ] [ description text ]

ipv6 route-static ipv6-address prefix-length interface-type interface-number gateway [ track track-entry-number ] [ preference preference ] [ tag tag-value ] [ description text ]

undo ipv6 route-static ipv6-address prefix-length [ interface-type interface-number [ next-hop-address | gateway ] | [ vpn-instance d-vpn-instance-name ] next-hop-address ] [ 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 ] | static session-name } | permanent | track track-entry-number ] | next-hop-address [ public ] [ bfd { control-packet bfd-source ipv6-address | static session-name } | permanent ] | vpn-instance d-vpn-instance-name next-hop-address [ bfd { control-packet bfd-source ipv6-address | static session-name } | permanent | track track-entry-number ] } [ preference preference ] [ tag tag-value ] [ description text ]

ipv6 route-static vpn-instance s-vpn-instance-name ipv6-address prefix-length interface-type interface-number gateway [ bfd { { control-packet | echo-packet } [ bfd-source ipv6-address ] | static session-name } | track track-entry-number ]

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

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

undo ipv6 route-static vpn-instance s-vpn-instance-name ipv6-address prefix-length [ interface-type interface-number [ next-hop-address | gateway ] | 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 srv6-policy { color color-value end-point ipv6 ipv6-address | name policy-name } [ sid sid ] [ preference preference ] [ tag tag-value ] [ description text ]

undo ipv6 route-static vpn-instance s-vpn-instance-name ipv6-address prefix-length [ srv6-policy { color color-value end-point ipv6 ipv6-address | name policy-name } ]

Default

No IPv6 static route is configured.

Views

System view

Predefined user roles

network-admin

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

gateway: Specifies the next hop IPv6 address of the IPv6 static route as the gateway address obtained by the interface in IPv6 address autoconfiguration. When the gateway address changes, the device automatically updates the next hop IPv6 address of the IPv6 static route accordingly. For more information about IPv6 address autoconfiguration, see IPv6 basics and DHCPv6 in Network Connectivity Configuration Guide.For more information about IPv6 address autoconfiguration, see IPv6 basics and DHCPv6 in Network Connectivity Configuration Guide.For more information about IPv6 address autoconfiguration, see IPv6 basics and DHCPv6 in Network Connectivity Configuration Guide.

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.

static session-name: Associates a static BFD session with the IPv6 static route. The session-name argument specifies a static BFD session by its name, a case-sensitive string of 1 to 64 characters. If you specify a nonexistent static BFD session, the configuration takes effect after you create the static BFD session.

permanent: Specifies the IPv6 route as a permanent IPv6 static route. After you specify this keyword, the IPv6 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 Network Management and Monitoring Configuration Guide.

public: Indicates the next hop is on the public network.

· With this keyword specified, the system searches for an output interface for the IPv6 static route from the public network IPv6 routing table based on the specified next hop.

· Without this keyword and the destination VPN instance specified, the next hop of the IPv6 static route belongs to the source VPN instance. In this case, the system searches for an output interface for the IPv6 static route from the routing table of the source VPN instance based on the specified next hop.

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 is specified, packets will search for the output interface based on the specified next hop (IPv6 address) for the static route.

preference preference: Specifies a preference for IPv6 static routes, in the range of 1 to 255. The default is 60. The smaller the value, the higher the preference. 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.

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.

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

Application scenarios

If a network's topology is simple, you only need to configure static routes for the network to work correctly. You can also configure static routes when the device cannot use dynamic routing protocols or cannot establish routes to the destination network.

Restrictions and guidelines

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 the source IPv6 address of BFD packets, you must specify the 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.

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.

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

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.

If the specified interface has not obtained the gateway address, the IPv6 static route with the gateway address as the next hop address does not take effect.

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

context-admin

Parameters

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

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 fast-reroute auto

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

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

Syntax

ipv6 route-static fast-reroute auto

undo ipv6 route-static fast-reroute auto

Default

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

Views

System view

Predefined user roles

network-admin

context-admin

Examples

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

<Sysname> system-view

[Sysname] ipv6 route-static fast-reroute auto

ipv6 route-static primary-path-detect bfd echo

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

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

Syntax

ipv6 route-static primary-path-detect bfd echo

undo ipv6 route-static primary-path-detect bfd

Default

BFD echo packet mode is disabled for IPv6 static route FRR.

Views

System view

Predefined user roles

network-admin

context-admin

Usage guidelines

Application scenarios

After you configure static route FRR on the device, you can use this command to enable the device to fast detect FRR primary link failures to minimize traffic loss.

Operating mechanism

If static route FRR forms primary and backup next hops, executing this command will enable the device to automatically create an echo-packet-mode BFD session to detect the primary route next hop. The source address of the BFD session is the IP address of the local device, and the destination address is the next hop address of the primary route. To view the BFD session information, execute the display bfd session command.

Restrictions and guidelines

If you do not configure static route FRR, or no reachable backup next hops are available for FRR, the device cannot establish a BFD session to detect the primary route next hop.

Examples

# Enable BFD echo packet mode for IPv6 static route FRR.

<Sysname> system-view

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

ipv6 route-static vpn-instance

Use ipv6 route-static vpn-instance to configure an IPv6 static route in a VPN instance.

Use undo ipv6 route-static vpn-instance to delete an IPv6 static route from a VPN instance.

Syntax

· Specify an output interface and a next hop

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 ] | static session-name } | permanent | 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 interface-type interface-number next-hop-address [ preference preference ]

· Specify an output interface without specifying a next hop

ipv6 route-static vpn-instance s-vpn-instance-name ipv6-address prefix-length interface-type interface-number [ permanent | 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 interface-type interface-number [ preference preference ]

· Specify a next hop without specifying an output interface

ipv6 route-static vpn-instance s-vpn-instance-name ipv6-address prefix-length next-hop-address [ public ] [ bfd { control-packet bfd-source ipv6-address | static session-name } | permanent ] [ preference preference ] [ tag tag-value ] [ description text ]

undo ipv6 route-static vpn-instance s-vpn-instance-name ipv6-address prefix-length next-hop-address [ preference preference ]

· Specify the next hop address as the gateway address obtained during IPv6 address autoconfiguration of the interface

undo ipv6 route-static vpn-instance s-vpn-instance-name ipv6-address prefix-length interface-type interface-number gateway [ preference preference ]

· Specify a destination VPN instance and a next hop

ipv6 route-static vpn-instance s-vpn-instance-name ipv6-address prefix-length vpn-instance d-vpn-instance-name next-hop-address [ bfd { control-packet bfd-source ipv6-address | static session-name } | permanent | 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 vpn-instance d-vpn-instance-name next-hop-address [ preference preference ]

· Specify a destination VPN instance without specifying a next hop

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

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

Default

No IPv6 static route is configured in a VPN instance.

Views

System view

Predefined user roles

network-admin

context-admin

Parameters

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 instance has its own routing table, and the configured IPv6 static route is installed in the routing tables of the specified VPN instances.

ipv6-address prefix-length: Specifies the IPv6 address and prefix length. 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.

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

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

gateway: Uses the gateway address obtained during IPv6 address autoconfiguration of the interface as the next hop address of the IPv6 static route. If the gateway address changes, the device automatically changes the next hop address of the IPv6 static route to the changed gateway address. For more information about IPv6 address autoconfiguration, see IPv6 basics configuration and DHCPv6 configuration in Layer 3—IP Services Configuration Guide.

bfd: Enables BFD to detect reachability of the static route's next hop. For more information about BFD, see High Availability Configuration Guide.

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.

static session-name: Associates the IPv6 static route with a static BFD session. The session-name argument represents the static BFD session name, a case-sensitive string of 1 to 64 characters. If you specify a nonexistent static BFD session, you must create the static BFD session to have the configuration take effect.

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, the device searches for the output interface in the IPv6 routing table of the public network based on the next hop address for packets matching the IPv6 static route. If you do not specify this keyword and do not specify the destination VPN instance, the next hop belongs to the source VPN instance. The device searches for the output interface in the IPv6 routing table of the source VPN instance based on the next hop address 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 the destination VPN instance without specifying the next-hop-address argument, make sure the destination VPN instance is different from the source VPN instance.

tag tag-value: Sets a tag for marking the IPv6 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 for the IPv6 static route, a string of 1 to 150 characters, including special characters such as the space, but excluding the question mark (?).

srv6-policy name policy-name: Specifies an SRv6 TE policy by its name for IPv6 static route recursion. The policy-name argument represents the SRv6 TE policy name, a case-sensitive string of 1 to 59 characters.

srv6-policy color color-value end-point ipv6 ipv6-address: Specifies an SRv6 TE policy by its color and endpoint attributes for IPv6 static route recursion. The color-value argument represents the color attribute value of the SRv6 TE policy, in the range of 0 to 4294967295. The ipv6-address argument represents the endpoint IPv6 address of the SRv6 TE policy.

sid sid: Specifies the SRv6 SID of the tail node. Packets forwarded by the specified SRv6 TE policy will continue to be forwarded based on the specified SRv6 SID.

Usage guidelines

Application scenarios

If a network's topology is simple, you only need to configure IPv6 static routes for the network to work correctly. You can also configure IPv6 static routes when the device cannot use dynamic routing protocols or cannot establish routes to the destination network.

In the system view of the default vSystem, execute the ipv6 route-static vpn-instance s-vpn-instance-name ipv6-address prefix-length vpn-instance d-vpn-instance-name [ preference preference ] [ tag tag-value ] [ description text ] command. This command allows intercommunication between two non-default vSystems. 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.

Restrictions and guidelines

Follow these guidelines to configure the output interface, next hop address, or both for an IPv6 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:

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

· If you specify the source IPv6 address of BFD packets, you must specify the IPv6 address as the next hop IPv6 address on the peer device.

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

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.

If the specified interface has not obtained the gateway address, the IPv6 static route with the gateway address as the next hop address does not take effect.

Examples

# Configure an IPv6 static route in VPN instance vpn1, whose destination address is 1:1:2::/64 and next hop address is 1:1:3::1 in VPN instance vpn2.

<Sysname> system-view

[Sysname] ipv6 route-static vpn-instance vpn1 1:1:2:: 64 vpn-instance vpn2 1:1:3::1

Related commands

display ipv6 routing-table protocol

07-Layer 3—IP Routing Command Reference

Application scenarios

Restrictions and guidelines

ipv6 route-static fast-reroute auto

Application scenarios

Operating mechanism

Restrictions and guidelines

ipv6 route-static vpn-instance

Application scenarios

Restrictions and guidelines

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business

News & Events

Contact Us