Configuring an IPv6 Static Route

Procedure

1. Access the system view.

   system-view

2. Configure an IPv6 static route.
   • ipv6 route-static dest-ipv6-address prefix-length interface-type interface-number [ nexthop-ipv6-address ] [ preference preference | tag tag ] ^* [ description text ]
   • ipv6 route-static dest-ipv6-address prefix-length nexthop-ipv6-address [ preference preference | tag tag ] ^* [ inherit-cost ] [ description text ]

   When configuring a static route, you need to specify either the outbound interface or the next-hop address according to the actual situation. If the outbound interface is a PPP interface, you can simply specify the outbound interface. If the outbound interface is a broadcast interface, you must also specify the next-hop address in addition to specifying the outbound interface.

   

   Static routes with an outgoing interface do not support recursive routing.

   If preference is not specified, the default preference is 60.

   By configuring different tag values, you can classify static routes to implement different routing policies. For example, other protocols can import static routes with specified tag values through routing policies. By default, the value is 0.

   By default, no IPv6 static route is configured.

   • ipv6 route-static vpn-instance vpn-instance-name dest-ipv6-address prefix-length interface-type interface-number [ nexthop-ipv6-address ] [ preference preference | tag tag ] ^* [ description text ]

   The vpn-instance vpn-instance-name value can be a common VPN name or the VPN instance automatically generated when a virtual system is created.

   When you configure an IPv6 static route for a virtual system, must be bound to the VPN instance with the same name as the virtual system.

3. Optional: Set the default preference of IPv6 static routes.

   ipv6 route-static default-preference preference

   By default, the preference of IPv6 static routes is 60.

   When an IPv6 static route is configured, the default preference is used if the preference of the static route is not explicitly specified. After the default preference is specified, the default preference is valid for subsequent rather than existing IPv6 static routes.

4. Optional: Enable the load balancing function for IPv6 reverse routes.

   firewall ipv6 reverse-route load-balance enable

   By default, the load balancing function for IPv6 reverse routes is disabled.

   After equal-cost routes are configured, sticky load balancing is enabled by default. If forward traffic is uneven, load unbalance occurs on reverse traffic. As a result, some interfaces may be overloaded. For scenarios where persistent connections exist and the traffic volume is large, or where a large number of GRE packets exist (GRE packets centralize at the inbound interface), you need to enable the load balancing function for reverse routes to allocate reverse traffic to interfaces in load balancing mode as configured by the firewall ipv6 load-balance { flow | packet } command.