The redirect ipv6-nexthop command assigns the IPv6 address and configures the outbound interface of the next hop for redirection. In addition, you can also apply the action to a specific interface according to a traffic behavior and redirect the traffic with a matching class.
The undo redirect ipv6-nexthop command cancels the configuration.
By default, the redirection of the IPv6 address and the outbound interface of the next hop are not configured in traffic behavior view.
redirect ipv6-nexthop ipv6-address vpn vpn-name [ nqa nqa-test-administer-name name-of-nqa-test-instance ] [ routing-filter { default-routing | blackhole-routing } * ] [ deny ] [ pri-type common ]
redirect ipv6-nexthop ipv6-address nqa nqa-test-administer-name name-of-nqa-test-instance [ routing-filter { default-routing | blackhole-routing } * ] [ deny ] [ pri-type common ]
redirect ipv6-nexthop ipv6-address [ routing-filter { default-routing | blackhole-routing } * ] [ deny ] [ pri-type common ]
redirect ipv6-nexthop ipv6-address interface { interface-name | interface-type interface-number } [ route-forward ] [ pri-type common ]
undo redirect ipv6-nexthop
| Parameter | Description | Value |
|---|---|---|
| ipv6-address |
Specifies the IPv6 address of the next hop for redirection. |
The value is in the format of X:X::X:X with each X representing four hexadecimal digits. |
| vpn vpn-name |
Specifies the name of a VPN instance. |
The value is a string of 1 to 31 case-sensitive characters, spaces not supported. In addition, the VPN instance name must not be _public_. When double quotation marks are used around the string, spaces are allowed in the string. |
| nqa nqa-test-administer-name |
Specifies the name of a manager of an NQA test instance. |
The name is a string of 1 to 32 case-insensitive characters, spaces not supported. The string can contain spaces if it is enclosed with double quotation marks ("). |
| name-of-nqa-test-instance |
Specifies the name of an NQA test instance. |
The name is a string of 1 to 32 case-insensitive characters, spaces not supported. The string can contain spaces if it is enclosed with double quotation marks ("). |
| default-routing |
When this parameter is configured, if the IP address of the next hop matches the default route, the packets are forwarded based on their destination IP address. |
- |
| blackhole-routing |
When this parameter is configured, if the IP address of the next hop matches a black-hole route, the packets are forwarded based on their destination IP address. |
- |
| deny |
If the next hop does not exist, the packet is discarded. |
- |
| pri-type |
Specifies the route priorities so that common routes take precedence. To be specific, when the destination IP address of a packet is reachable, the packet is forwarded preferentially based on the destination IP address. When the destination IP address of a packet is unreachable, the packet is forwarded based on policy-based routing. |
- |
| interface |
Interface. |
- |
| interface-name |
Specifies the name of the outbound interface. |
- |
| interface-type |
Specifies the type of the outbound interface. |
- |
| interface-number |
Specifies the number of the outbound interface. |
- |
| route-forward |
If a discard PBR policy is enabled in this command, and all the specified outbound interfaces were shut down, the parameter route-forward can be configured to return packets to the original forwarding process. |
- |
Usage Scenario
For the IPv6 packets involved in the complex traffic classification, you can run the redirect ipv6-nexthop command to assign the IPv6 address and configure the outbound interface of the next hop for redirection.
Precautions
If you have specified the outbound interface, strong policy routing is enabled. The device forwards packets based on the specified next hop and the outbound interface but does not search the FIB table. The outbound interface can be a GE interface, GE sub-interface, Eth-Trunk interface and Eth-Trunk sub-interface.
One traffic behavior has only one redirect configuration. To create another redirect configuration, you must delete the existing one. A traffic policy containing redirecting actions can be applied to only the inbound direction of an interface. To switch the forward policy and discard policy, delete the original configuration and reconfigure one. Policy-based routing supports redirection only for incoming traffic. MF classification configured for outgoing traffic does not take effect.