Contents

Configuring IPv6 static routing· 1

About IPv6 static routing· 1

vSystem support for features· 1

Configuring an IPv6 static route· 1

Configuring IPv6 static routes for vSystem intercommunication· 2

About IPv6 static route configuration for vSystem intercommunication· 2

Restrictions and guidelines for IPv6 static route configuration for vSystem intercommunication· 2

Configuring an IPv6 static route for a non-default vSystem to access the default vSystem·· 2

Configuring an IPv6 static route for the default vSystem to access a non-default vSystem·· 2

Configuring an IPv6 static route for one non-default vSystem to access another non-default vSystem   3

Configuring an IPv6 static route with the gateway address as the next hop· 3

Configuring an IPv6 floating static route· 4

Deleting IPv6 static routes· 4

Configuring BFD for IPv6 static routes· 4

About BFD for IPv6 static routes· 4

Restrictions and guidelines for BFD·· 5

Configuring BFD control packet mode· 5

Configuring BFD echo packet mode· 6

Configuring IPv6 static route FRR· 6

About IPv6 static route FRR· 6

Restrictions and guidelines for IPv6 static route FRR· 7

Configuring IPv6 static route FRR to automatically select a backup next hop· 7

Enabling BFD echo packet mode for IPv6 static route FRR· 7

Display and maintenance commands for IPv6 static routing· 7

Configuring an IPv6 default route· 9

 

Configuring IPv6 static routing

About IPv6 static routing

Static routes are manually configured and cannot adapt to network topology changes. If a fault or a topological change occurs in the network, the network administrator must modify the static routes manually. IPv6 static routing works well in a simple IPv6 network.

vSystem support for features

vSystem does not support the following IPv6 static routing features:

·     Configuring an IPv6 static route with the gateway address as the next hop.

·     Configuring IPv6 static route FRR.

For information about the support of non-default vSystems for the commands, see IPv6 static routing command reference. For more information about vSystem, see Virtual Technologies Configuration Guide.

Configuring an IPv6 static route

1.     Enter system view.

system-view

2.     Configure an IPv6 static route.

Public network:

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

By default, no IPv6 static route is configured.

VPN:

ipv6 route-static vpn-instance s-vpn-instance-name ipv6-address prefix-length { interface-type interface-number [ next-hop-address ] | vpn-instance d-vpn-instance-name next-hop-address } [ 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 nexthop-address [ public ] [ permanent ] [ preference preference ] [ tag tag-value ] [ description text ]

By default, no IPv6 static route is configured.

3.     (Optional.) Set the default preference for IPv6 static routes.

ipv6 route-static default-preference default-preference

The default setting is 60.

Configuring IPv6 static routes for vSystem intercommunication

About IPv6 static route configuration for vSystem intercommunication

Configure IPv6 static routes to realize intercommunication between the default vSystem and a non-default vSystem or between two non-default vSystems. For example, configure an IPv6 static route to allow a non-default vSystem to access the default vSystem. When data packets in the non-default vSystem match the IPv6 static route, they are forwarded to the default vSystem. The default vSystem continues to forward them.

For more information about vSystems, see Virtual Technologies Configuration Guide.

Restrictions and guidelines for IPv6 static route configuration for vSystem intercommunication

Do not specify the IPv6 next hop address when you configure an IPv6 static route for vSystem intercommunication.

Configuring an IPv6 static route for a non-default vSystem to access the default vSystem

Restrictions and guidelines

Perform this task on a non-default vSystem.

Procedure

1.     Enter system view.

system-view

2.     Configure an IPv6 static route for a non-default vSystem to access the default vSystem.

ipv6 route-static ipv6-address prefix-length public [ preference preference ] [ tag tag-value ] [ description text ]

By default, no IPv6 static routes are configured for a non-default vSystem to access the default vSystem.

Configuring an IPv6 static route for the default vSystem to access a non-default vSystem

Restrictions and guidelines

Perform this task on the default vSystem.

Make sure the specified destination VPN instance has the same name as the non-default vSystem.

Procedure

1.     Enter system view.

system-view

2.     Configure an IPv6 static route for the default vSystem to access a non-default vSystem.

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

By default, no IPv6 static routes are configured for the default vSystem to access a non-default vSystem.

Configuring an IPv6 static route for one non-default vSystem to access another non-default vSystem

Restrictions and guidelines

Perform this task on the default vSystem.

Make sure the specified source and destination VPN instances have the same names as the non-default vSystems.

Procedure

1.     Enter system view.

system-view

2.     Configure an IPv6 static route for one non-default vSystem to access another non-default vSystem.

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 ]

By default, no IPv6 static routes are configured for one non-default vSystem to access another non-default vSystem.

Configuring an IPv6 static route with the gateway address as the next hop

About this task

An interface can obtain the gateway address during IPv6 address autoconfiguration. You can configure this feature for an IPv6 static route to use the gateway address as the next hop. 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 Layer 3—IP Services Configuration Guide.

Restrictions and guidelines

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.

Procedure

Public network:

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 ]

VPN:

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 ]

Configuring an IPv6 floating static route

Perform this task to implement route backup and improve network reliability.

When an IPv6 static or dynamic route to a destination address already exists on the device, you configure another IPv6 static route with a lower priority as the backup route to improve the network reliability. This backup IPv6 static route is called an IPv6 floating static route, and it is activated only when the primary route fails. After the primary route recovers from failure, the IPv6 floating static route becomes inactive, and data forwarding switches back to the primary route.

You can configure an IPv6 floating static route in either of the following ways

·     Configure different priorities for multiple IPv6 static routes to the same destination address. The route with lower priority automatically becomes the IPv6 floating static route.

·     When an IPv6 route to a destination address already exists on the device, configure an IPv6 static route with a lower priority to the same destination address.

When you configure an IPv6 floating static route, the priority value of the route must be larger than then priority value of the primary route. For more information, see "Configuring an IPv6 static route."

Deleting IPv6 static routes

About this task

To delete an IPv6 static route, use the undo ipv6 route-static command. To delete all IPv6 static routes including the default route, use the delete ipv6 static-routes all command.

Procedure

1.     Enter system view.

system-view

2.     Delete all IPv6 static routes, including the default route.

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

‌

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.

‌

Configuring BFD for IPv6 static routes

About BFD for IPv6 static routes

BFD provides a general purpose, standard, and medium- and protocol-independent fast failure detection mechanism. It can uniformly and quickly detect the failures of the bidirectional forwarding paths between two routers for protocols, such as routing protocols. BFD for IPv6 static routes tests the reachability of the next hop for each IPv6 static route. If a next hop is unreachable, BFD deletes the associated IPv6 static route.

For more information about BFD, see Network Management and Monitoring Configuration Guide.

Restrictions and guidelines for BFD

When you configure BFD for IPv6 static routes, follow these restrictions and guidelines:

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

Configuring BFD control packet mode

About this task

This mode uses BFD control packets to detect the status of a link bidirectionally at a millisecond level.

BFD control packet mode can be applied to IPv6 static routes with a direct next hop or with an indirect next hop.

Restrictions and guidelines for BFD control packet mode

If you configure BFD control packet mode at the local end, you must also configure this mode at the peer end.

Configuring BFD control packet mode for an IPv6 static route (direct next hop)

1.     Enter system view.

system-view

2.     Configure BFD control packet mode for an IPv6 static route.

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

By default, BFD control packet mode for an IPv6 static route is not configured.

Configuring BFD control packet mode for an IPv6 static route (indirect next hop)

1.     Enter system view.

system-view

2.     Configure BFD control packet mode for an IPv6 static route.

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 } [ preference preference ] [ tag tag-value ] [ description text ]

By default, BFD control packet mode for an IPv6 static route is not configured.

Configuring BFD echo packet mode

About this task

With BFD echo packet mode enabled for a static route, the output interface sends BFD echo packets to the destination device, which loops the packets back to test the link reachability.

Restrictions and guidelines

You do not need to configure BFD echo packet mode at the peer end.

Do not use BFD for a static route with the output interface in spoofing state.

Procedure

1.     Enter system view.

system-view

2.     (Optional.) Configure the source address of echo packets.

bfd echo-source-ipv6 ipv6-address

By default, the source address of echo packets is not configured.

As a best practice to avoid network congestion caused by excessive ICMPv6 redirect packets from the peer, use this command. Make sure the source IPv6 address is not on the subnet of any interfaces on the device.

For more information about this command, see Network Management and Monitoring Command Reference.

3.     Configure BFD echo packet mode for an IPv6 static route.

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

By default, BFD echo packet mode for an IPv6 static route is not configured.

The next hop IPv6 address must be a global unicast address.

Configuring IPv6 static route FRR

About IPv6 static route FRR

A link or router failure on a path can cause packet loss. IPv6 static route fast reroute (FRR) enables fast rerouting to minimize the impact of link or node failures.

Figure 1 Network diagram

 

As shown in Figure 1, upon a link failure, packets are directed to the backup next hop to avoid traffic interruption. You can enable FRR to automatically select a backup next hop (which must be configured in advance).

Restrictions and guidelines for IPv6 static route FRR

Do not use IPv6 static route FRR and BFD (for an IPv6 static route) at the same time.

Equal-cost routes do not support IPv6 static route FRR.

Besides the configured IPv6 static route for FRR, the device must have another route to reach the destination. When the state of the primary link (with Layer 3 interfaces staying up) changes from bidirectional to unidirectional or down, IPv6 static route FRR quickly redirects traffic to the backup next hop. When the Layer 3 interfaces of the primary link are down, IPv6 static route FRR temporarily redirects traffic to the backup next hop. In addition, the device searches for another route to reach the destination and redirects traffic to the new path if a route is found. If no route is found, traffic interruption occurs.

Configuring IPv6 static route FRR to automatically select a backup next hop

1.     Enter system view.

system-view

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

ipv6 route-static fast-reroute auto

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

Enabling BFD echo packet mode for IPv6 static route FRR

About this task

By default, IPv6 static route FRR uses IPv6 ND to detect primary link failures. For quicker IPv6 static route FRR, use BFD echo packet mode on the primary link of redundant links to detect link failure.

Procedure

1.     Enter system view.

system-view

2.     (Optional.) Configure the source IP address of BFD echo packets.

bfd echo-source-ipv6 ipv6-address

By default, the source IPv6 address of BFD echo packets is not configured.

As a best practice to avoid network congestion caused by excessive ICMPv6 redirect packets from the peer, use this command. Make sure the source IPv6 address is not on the subnet of any interfaces on the device.

You must specify a global unicast address as the source IPv6 address of BFD echo packets.

For more information about this command, see BFD commands in Network Management and Monitoring Command Reference.

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

ipv6 route-static primary-path-detect bfd echo

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

Display and maintenance commands for IPv6 static routing

‌

IMPORTANT: Non-default vSystems do not support some of the display and maintenance commands. For information about vSystem support for these commands, see IPv6 static routing command reference.

‌

Execute display commands in any view.

 

Task	Command
Display IPv6 static route next hop information.	display ipv6 route-static nib [ nib-id ] [ verbose ]
Display IPv6 static routing table information.	display ipv6 route-static routing-table [ vpn-instance vpn-instance-name ] [ ipv6-address prefix-length ]
Display IPv6 static route information.	display ipv6 routing-table protocol static [ inactive | verbose ]

 

For more information about the display ipv6 routing-table protocol static [ inactive | verbose ] command, see basic IP routing in Layer 3—IP Routing Command Reference.

Configuring an IPv6 default route

A default IPv6 route is used to forward packets that match no entry in the routing table.

A default IPv6 route can be configured in either of the following ways:

·     The network administrator can configure a default route with a destination prefix of ::/0. For more information, see "Configuring IPv6 static routing."

·     Some dynamic routing protocols (such as OSPFv3, IPv6 IS-IS, and RIPng) can generate a default IPv6 route. For example, an upstream router running OSPFv3 can generate a default IPv6 route and advertise it to other routers. These routers install the default IPv6 route with the next hop being the upstream router. For more information, see the respective chapters on those routing protocols in this configuration guide.

As shown in Figure 2, Device B is the next hop for packets from Device A to Device C, Device D, and Device E. You can configure a default route on Device A to replace the three IPv6 static routes from Device A to Device C, Device D, and Device E.

Configure the IPv6 default route as follows:

·     Configure the next hop address as 1::2.

·     Configure the destination address as ::.

·     Configure the prefix length as 0.

Figure 2 Configuring an IPv6 default route

‌