Login
- Table of Contents
-
- 08-Layer 3—IP Routing Command References
- 00-Preface
- 01-Basic IP routing commands
- 02-Static routing commands
- 03-RIP commands
- 04-OSPF commands
- 05-IS-IS commands
- 06-EIGRP commands
- 07-BGP commands
- 08-Policy-based routing commands
- 09-IPv6 static routing commands
- 10-RIPng commands
- 11-OSPFv3 commands
- 12-IPv6 policy-based routing commands
- 13-Routing policy commands
- 14-MTR commands
- 15-RIR commands
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 12-IPv6 policy-based routing commands | 176.02 KB |
Contents
IPv6 policy-based routing commands
apply default-output-interface
display ipv6 policy-based-route
display ipv6 policy-based-route interface
display ipv6 policy-based-route local
display ipv6 policy-based-route setup
ipv6 policy-based-route (interface view)
ipv6 policy-based-route (system view)
reset ipv6 policy-based-route statistics
IPv6 policy-based routing commands
Certain routers do not support SRv6 TE policies because they do not support segment routing. For more information about SRv6 TE policies, see Segment Routing Command Reference.
The following compatibility matrixes show the support of hardware platforms for IPv6 policy-based routing:
|
Hardware |
IPv6 policy-based routing compatibility |
|
MSR610 |
No |
|
MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LM-CNDE-SJK, MSR810-CNDE-SJK, MSR810-EI, MSR810-LM-EA, MSR810-LM-EI |
Yes |
|
MSR810-LMS, MSR810-LUS |
Yes |
|
MSR810-SI, MSR810-LM-SI |
Yes |
|
MSR810-LMS-EA, MSR810-LME |
Yes |
|
MSR1004S-5G, MSR1004S-5G-CN |
Yes |
|
MSR1104S-W, MSR1104S-W-CAT6, MSR1104S-5G-CN, MSR1104S-W-5G-CN |
Yes |
|
MSR2600-6-X1, MSR2600-15-X1, MSR2600-15-X1-T |
Yes |
|
MSR2600-10-X1 |
Yes |
|
MSR 2630 |
Yes |
|
MSR3600-28, MSR3600-51 |
Yes |
|
MSR3600-28-SI, MSR3600-51-SI |
Yes |
|
MSR3600-28-X1, MSR3600-28-X1-DP, MSR3600-51-X1, MSR3600-51-X1-DP |
Yes |
|
MSR3600-28-G-DP, MSR3600-51-G-DP |
Yes |
|
MSR3610-I-DP, MSR3610-IE-DP, MSR3610-IE-ES, MSR3610-IE-EAD, MSR-EAD-AK770, MSR3610-I-IG, MSR3610-IE-IG |
Yes |
|
MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC, MSR3620-X1, MSR3640-X1 |
Yes |
|
MSR3610, MSR3620, MSR3620-DP, MSR3640, MSR3660 |
Yes |
|
MSR3610-G, MSR3620-G |
Yes |
|
MSR3640-G |
Yes |
|
MSR3640-X1-HI |
Yes |
|
Hardware |
IPv6 policy-based routing compatibility |
|
MSR810-W-WiNet, MSR810-LM-WiNet |
Yes |
|
MSR830-4LM-WiNet |
Yes |
|
MSR830-5BEI-WiNet, MSR830-6EI-WiNet, MSR830-10BEI-WiNet |
Yes |
|
MSR830-6BHI-WiNet, MSR830-10BHI-WiNet |
Yes |
|
MSR2600-6-WiNet |
Yes |
|
MSR2600-10-X1-WiNet |
Yes |
|
MSR2630-WiNet |
Yes |
|
MSR3600-28-WiNet |
Yes |
|
MSR3610-X1-WiNet |
Yes |
|
MSR3610-WiNet, MSR3620-10-WiNet, MSR3620-DP-WiNet, MSR3620-WiNet, MSR3660-WiNet |
Yes |
|
Hardware |
IPv6 policy-based routing compatibility |
|
MSR860-6EI-XS |
Yes |
|
MSR860-6HI-XS |
Yes |
|
MSR2630-XS |
Yes |
|
MSR3600-28-XS |
Yes |
|
MSR3610-XS |
Yes |
|
MSR3620-XS |
Yes |
|
MSR3610-I-XS |
Yes |
|
MSR3610-IE-XS |
Yes |
|
MSR3620-X1-XS |
Yes |
|
MSR3640-XS |
Yes |
|
MSR3660-XS |
Yes |
|
Hardware |
IPv6 policy-based routing compatibility |
|
MSR810-LM-GL |
Yes |
|
MSR810-W-LM-GL |
Yes |
|
MSR830-6EI-GL |
Yes |
|
MSR830-10EI-GL |
Yes |
|
MSR830-6HI-GL |
Yes |
|
MSR830-10HI-GL |
Yes |
|
MSR1004S-5G-GL |
Yes |
|
MSR2600-6-X1-GL |
Yes |
|
MSR3600-28-SI-GL |
Yes |
apply access-vpn
Use apply access-vpn to specify the forwarding tables that can be used for the matching packets.
Use undo apply access-vpn to remove the specified forwarding tables.
Syntax
apply access-vpn { public | vpn-instance vpn-instance-name&<1-4> }
undo apply access-vpn { public | vpn-instance [ vpn-instance-name&<1-
4> ] }
Default
Views
IPv6 policy node view
Predefined user roles
network-admin
Parameters
public: Specifies the forwarding table for the public network.
vpn-instance: Specifies the forwarding table for the specified MPLS L3VPN instances.
vpn-instance-name&<1-4>: Specifies a space-separated list of up to four VPN instance names. A VPN instance name is a case-sensitive string of 1 to 31 characters. The specified VPN instance must already exist.
Usage guidelines
Use this command only in special scenarios that require sending packets received from one network to another network, for example, from a VPN to the public network, or from one VPN to another VPN.
You can repeat this command to specify the forwarding tables for the public network and VPN instances. The device forwards the matching packets by using the first available forwarding table selected in the order in which they are specified.
If you specify the vpn-instance keyword without specifying any VPN instances when you execute the undo form of this command, all the VPN instances are removed from the IPv6 policy node.
After all the forwarding tables on the IPv6 policy node are removed, the default forwarding behavior restores.
Examples
# Specify the VPN 1 and VPN 2 forwarding tables on node 10. In this example, VPN 1 and VPN 2 already exist.
<Sysname> system-view
[Sysname] ipv6 policy-based-route policy1 permit node 10
[Sysname-pbr6-policy1-10] apply access-vpn vpn-instance vpn1 vpn2
# Specify the public network forwarding table on node 10.
<Sysname> system-view
[Sysname] ipv6 policy-based-route policy1 permit node 10
[Sysname-pbr6-policy1-10] apply access-vpn public
Related commands
apply remark-vpn
apply continue
Use apply continue to compare packets with the next policy node upon failure on the current node.
Use undo apply continue to restore the default.
Syntax
apply continue
undo apply continue
Default
IPv6 PBR does not compare packets with the next policy node upon failure on the current node.
Views
IPv6 policy node view
Predefined user roles
network-admin
Usage guidelines
This command takes effect only when the mode of the node is permit.
This command applies when either of the following conditions exist:
¡ apply access-vpn
¡ apply next-hop
¡ apply output-interface
¡ apply default-next-hop
¡ apply default-output-interface
· A clause listed above is configured, but it has become invalid. Then, a routing table lookup also fails for the matching packet.
|
|
NOTE: A clause might become invalid because the specified next hop is unreachable, packets cannot be forwarded in the specified VPN instance, or the specified output interface is down. |
Examples
# Compare with the next policy node upon failure on the current node.
<Sysname> system-view
[Sysname] ipv6 policy-based-route aa permit node 11
[Sysname-pbr6-aa-11] apply continue
apply default-gateway
Use apply default-gateway to specify the default next hop addresses as the gateway addresses.
Use undo apply default-gateway to remove the configuration.
Syntax
apply default-gateway { interface-type interface-number [ track track-entry-number ] }&<1-n>
undo apply default-gateway [ { interface-type interface-number }&<1-n> ]
Default
The gateway addresses are not specified as the default next hop addresses.
Views
IPv6 policy node view
Predefined user roles
network-admin
Parameters
interface-type interface-number: Specifies an interface that obtains the gateway address by its type and number.
track track-entry-number: Specifies a track entry by its number in the range of 1 to 1024.
&<1-n>: Indicates that the argument before it can be entered up to n times.
Usage guidelines
After you configure this command, IPv6 PBR uses the gateway addresses obtained by the specified interfaces as the default next hop addresses for forwarding matching packets. When the default gateway addresses change, the device automatically updates the default next hop addresses. If the interfaces fail to obtain any gateway addresses or the gateway addresses are invalid, the command does not take effect.
You can configure multiple interfaces in one command line or by executing this command multiple times. The gateway addresses obtained by the interfaces back up one another. The first reachable gateway next hop address selected according to configuration order will be used to forward matching packets.
If you specify an interface, the undo form of this command removes the gateway address obtained by the interface. If you do not specify any interfaces, the undo form of this command removes all gateway addresses used as default next hop addresses.
Examples
# Specify the default next hop address as the gateway address obtained by interface GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] ipv6 policy-based-route aa permit node 11
[Sysname-pbr6-aa-11] apply default-gateway gigabitethernet 1/0/1
apply default-next-hop
Use apply default-next-hop to set default next hops.
Use undo apply default-next-hop to remove default next hops.
Syntax
apply default-next-hop [ vpn-instance vpn-instance-name | inbound-vpn ] { ipv6-address [ direct ] [ track track-entry-number ] }&<1-4>
undo apply default-next-hop [ [ vpn-instance vpn-instance-name | inbound-vpn ] ipv6-address&<1-4> ]
Default
No default next hops are set.
Views
IPv6 policy node 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. The specified VPN instance must already exist.
inbound-vpn: Specifies the VPN instance where the inbound interface belongs.
ipv6-address: Specifies the IPv6 address of a default next hop. If you do not specify the vpn-instance vpn-instance-name option or the inbound-vpn keyword, the default next hop belongs to the public network.
direct: Specifies a directly connected default next hop.
track track-entry-number: Specifies a track entry by its number in the range of 1 to 1024.
&<1-4>: Indicates that you can specify up to four default next hops, each of which can be associated with a track entry.
Usage guidelines
You can specify multiple default next hops for backup or load sharing in one command line or by executing this command multiple times.
With a default next hop specified, the undo apply default-next-hop command removes the default next hop.
Without any default next hop specified, the undo apply default-next-hop command removes all default next hops.
Examples
# Set a directly-connected default next hop of 1:1::1:1.
<Sysname> system-view
[Sysname] ipv6 policy-based-route aa permit node 11
[Sysname-pbr6-aa-11] apply default-next-hop 1:1::1:1 direct
Related commands
apply loadshare
apply default-output-interface
Use apply default-output-interface to set default output interfaces.
Use undo apply default-output-interface to remove default output interfaces.
Syntax
apply default-output-interface { interface-type interface-number [ track track-entry-number ] }&<1-4>
undo apply default-output-interface [ { interface-type interface-number }&<1-4> ]
Default
No default output interfaces are set.
Views
IPv6 policy node view
Predefined user roles
network-admin
Parameters
interface-type interface-number: Specifies an interface by its type and number.
track track-entry-number: Specifies a track entry by its number in the range of 1 to 1024.
&<1-4>: Indicates that you can specify up to four interfaces, each of which can be associated with a track entry.
Usage guidelines
You can specify multiple default output interfaces for backup or load sharing in one command line or by executing this command multiple times.
The default output interface must be P2P type. Using a non-P2P default output interface can result in forwarding failures when the interface has multiple next hops. Non-P2P interfaces include broadcast and non-broadcast multi-access (NBMA) interfaces such as Ethernet and virtual-template interfaces. In NBMA networks, packets are sent in unicast.
With a default output interface specified, the undo apply default-output-interface command removes the default output interface.
Without any default output interface specified, the undo apply default-output-interface command removes all default output interfaces.
Examples
# Specify GigabitEthernet 1/0/1 as the default output interface for IPv6 packets.
<Sysname> system-view
[Sysname] ipv6 policy-based-route aa permit node 11
[Sysname-pbr6-aa-11] apply default-output-interface gigabitethernet 1/0/1
Related commands
apply loadshare
apply default-srv6-policy
Use apply default-srv6-policy to set default SRv6 TE policies.
Use undo apply default-srv6-policy to remove default SRv6 TE policies.
Syntax
apply default-srv6-policy { endpoint color [ { sid | vpnsid } sid ] }&<1-n>
undo apply default-srv6-policy [ { endpoint color }&<1-n> ]
Default
No default SRv6 TE policies are set.
Views
IPv6 policy node view
Predefined user roles
network-admin
Parameters
endpoint: Specifies a default SRv6 TE policy by its endpoint IPv6 address.
color: Specifies a default SRv6 TE policy by its color attribute value in the range of 0 to 4294967295.
sid: Indicates that the SRv6 SID of the destination node is a public network SID.
vpnsid: Indicates that the SRv6 SID of the destination node is a VPN SID.
sid: Specifies the SRv6 SID of the destination node in IPv6 address format.
&<1-n>: Indicates that you can specify up to n default SRv6 TE policies.
Usage guidelines
You can specify multiple default SRv6 TE policies for backup in one command line or by executing this command multiple times. The first available default SRv6 TE policy selected according to configuration order will be used to forward matching packets.
Without any default SRv6 TE policy specified, the undo apply default-srv6-policy command removes all default SRv6 TE policies.
Use the { sid | vpnsid } sid option to specify the SRv6 SID of the destination node and its attribute information (public network SID or VPN SID). The attribute information is not encapsulated in packets and does not affect packet forwarding.
When encapsulating packets matching the default SRv6 TE policy, the source node adds the SRv6 SID of the destination node to the SID list in the SRH header of the packets. Upon receiving the packets, the destination node uses the SRv6 SID to perform an SRv6 local SID forwarding table lookup to forward the packets.
Examples
# Specify a default SRv6 TE policy with destination node IPv6 address 1000::1, color attribute value 10, and destination node SRv6 SID 2000::2.
<Sysname> system-view
[Sysname] ipv6 policy-based-route aa permit node 1
[Sysname-pbr6-aa-1] apply default-srv6-policy 1000::1 10 sid 2000::2
Related commands
apply loadshare
apply gateway
Use apply gateway to specify the next hop addresses as the gateway addresses.
Use undo apply gateway to remove the configuration.
Syntax
apply gateway { interface-type interface-number [ track track-entry-number ] }&<1-n>
undo apply gateway [ { interface-type interface-number }&<1-n> ]
Default
The gateway addresses are not specified as the next hop addresses.
Views
IPv6 policy node view
Predefined user roles
network-admin
Parameters
interface-type interface-number: Specifies an interface that obtains the gateway address by its type and number.
track track-entry-number: Specifies a track entry by its number in the range of 1 to 1024.
&<1-n>: Indicates that the argument before it can be entered up to n times.
Usage guidelines
After you configure this command, IPv6 PBR uses the gateway addresses obtained by the specified interfaces as the next hop addresses for forwarding matching packets. When the gateway addresses change, the device automatically updates the next hop addresses. If the interfaces fail to obtain any gateway addresses or the gateway addresses are invalid, the command does not take effect.
You can configure multiple interfaces in one command line or by executing this command multiple times. The gateway addresses obtained by the interfaces back up one another. The first reachable gateway next hop address selected according to configuration order will be used to forward matching packets.
If you specify an interface, the undo form of this command removes the gateway address obtained by the interface. If you do not specify any interfaces, the undo form of this command removes all gateway addresses used as next hop addresses.
Examples
# Specify the next hop address as the gateway address obtained by interface GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] ipv6 policy-based-route aa permit node 11
[Sysname-pbr6-aa-11] apply gateway gigabitethernet 1/0/1
apply loadshare
Use apply loadshare to enable load sharing among multiple next hops, output interfaces, SRv6 TE policies, default next hops, default output interfaces, or default SRv6 TE policies.
Use undo apply loadshare to restore the default.
Syntax
apply loadshare { default-next-hop | default-output-interface | default-srv6-policy | next-hop | output-interface | srv6-policy }
undo apply loadshare { default-next-hop | default-output-interface | default-srv6-policy | next-hop | output-interface | srv6-policy }
Default
Multiple next hops, output interfaces, SRv6 TE policies, default next hops, default output interfaces, or default SRv6 TE policies operate in primary/backup mode.
Views
IPv6 policy node view
Predefined user roles
network-admin
Parameters
default-next-hop: Enables load sharing among multiple default next hops.
default-output-interface: Enables load sharing among multiple default output interfaces.
default-srv6-policy: Enables load sharing among multiple default SRv6 TE policies.
next-hop: Enables load sharing among multiple next hops.
output-interface: Enables load sharing among multiple output interfaces.
srv6-policy: Enables load sharing among multiple SRv6 TE policies.
Usage guidelines
Multiple next hop, output interface, SRv6 TE policy, default next hop, default output interface, or default SRv6 TE policy options operate in either primary/backup or load sharing mode. The following description uses multiple next hops as an example:
· Primary/backup mode—A next hop is selected from all next hops in configuration order for packet forwarding, with all remaining next hops as backups. When the selected next hop fails, the next available next hop takes over.
· Load sharing mode—Matching traffic is distributed across the available next hops. If the traffic does not match any fast forwarding entries, per-packet load sharing is performed. If the traffic matches a fast forwarding entry, per-flow load sharing is performed.
Examples
# Enable load sharing among multiple next hops.
<Sysname> system-view
[Sysname] ipv6 policy-based-route aa permit node 11
[Sysname-pbr6-aa-11] apply next-hop 1::1 2::2
[Sysname-pbr6-aa-11] apply loadshare next-hop
# Enable load sharing among multiple output interfaces.
<Sysname> system-view
[Sysname] ipv6 policy-based-route aa permit node 11
[Sysname-pbr6-aa-11] apply output-interface gigabitethernet 1/0/1 gigabitethernet 1/0/2
[Sysname-pbr6-aa-11] apply loadshare output-interface
# Enable load sharing among multiple SRv6 TE policies.
<Sysname> system-view
[Sysname] ipv6 policy-based-route aa permit node 11
[Sysname-pbr6-aa-11] apply srv6-policy 1000::1 10 sid 2000::2 3000::1 12 sid 4000::2
[Sysname-pbr6-aa-11] apply loadshare srv6-policy
# Enable load sharing among multiple default next hops.
<Sysname> system-view
[Sysname] ipv6 policy-based-route aa permit node 11
[Sysname-pbr6-aa-11] apply default-next-hop 1::1 2::2
[Sysname-pbr6-aa-11] apply loadshare default-next-hop
# Enable load sharing among multiple default output interfaces. )
<Sysname> system-view
[Sysname] ipv6 policy-based-route aa permit node 11
[Sysname-pbr6-aa-11] apply default-output-interface gigabitethernet 1/0/1 gigabitethernet 1/0/2
[Sysname-pbr6-aa-11] apply loadshare default-output-interface
# Enable load sharing among multiple default SRv6 TE policies.
<Sysname> system-view
[Sysname] ipv6 policy-based-route aa permit node 11
[Sysname-pbr6-aa-11] apply default-srv6-policy 1000::1 10 sid 2000::2 3000::1 12 sid 4000::2
[Sysname-pbr6-aa-11] apply loadshare default-srv6-policy
Related commands
apply default-next-hop
apply default-output-interface
apply default-srv6-policy
apply next-hop
apply output-interface
apply srv6-policy
apply next-hop
Use apply next-hop to set next hops.
Use undo apply next-hop to remove next hops.
Syntax
apply next-hop [ vpn-instance vpn-instance-name | inbound-vpn ] { ipv6-address [ direct ] [ track track-entry-number ] [ weight weight-value ] } &<1-4>
undo apply next-hop [ [ vpn-instance vpn-instance-name | inbound-vpn ] ipv6-address&<1-4> ]
Default
No next hops are set.
Views
IPv6 policy node 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. The specified VPN instance must already exist.
inbound-vpn: Specifies the VPN instance where the inbound interface belongs.
ipv6-address: Specifies the IPv6 address of a next hop. If you do not specify the vpn-instance vpn-instance-name option or the inbound-vpn keyword, the next hop belongs to the public network.
direct: Specifies that the next hop must be directly connected to take effect.
track track-entry-number: Specifies a track entry by its number in the range of 1 to 1024.
weight weight-value: Specifies a load sharing weight for the next hop, in the range of 1 to 100. The default is 10. If you specify weights 1, 1, and 2 for three next hops, they share 1/4, 1/4, and 1/2 of the whole traffic, respectively.
&<1-4>: Indicates that you can specify up to four next hops, each of which can be associated with a track entry.
Usage guidelines
You can specify multiple next hops for backup or load sharing in one command line or by executing this command multiple times.
With a next hop specified, the undo apply next-hop command removes the next hop.
Without any next hop specified, the undo apply next-hop command removes all next hops.
Examples
# Set a directly-connected next hop of 1::1.
<Sysname> system-view
[Sysname] ipv6 policy-based-route aa permit node 11
[Sysname-pbr6-aa-11] apply next-hop 1::1
Related commands
apply loadshare
apply output-interface
Use apply output-interface to set output interfaces.
Use undo apply output-interface to remove output interfaces.
Syntax
apply output-interface { interface-type interface-number [ track track-entry-number ] }&<1-4>
undo apply output-interface [ { interface-type interface-number }&<1-4> ]
Default
No output interfaces are set.
Views
IPv6 policy node view
Predefined user roles
network-admin
Parameters
interface-type interface-number: Specifies an interface by its type and number.
track track-entry-number: Specifies a track entry by its number in the range of 1 to 1024.
&<1-4>: Indicates that you can specify up to four interfaces, each of which can be associated with a track entry.
Usage guidelines
You can specify multiple output interfaces for backup or load sharing in one command line or by executing this command multiple times.
The output interface must be P2P type. Using a non-P2P output interface can result in forwarding failures when the interface has multiple next hops. Non-P2P interfaces include broadcast and NBMA interfaces such as Ethernet and virtual-template interfaces.
With an output interface specified, the undo apply output-interface command removes the output interface.
Without any output interface specified, the undo apply output-interface command removes all output interfaces.
Examples
# Specify GigabitEthernet 1/0/1 as the output interface for IPv6 packets.
<Sysname> system-view
[Sysname] ipv6 policy-based-route aa permit node 11
[Sysname-pbr6-aa-11] apply output-interface gigabitethernet 1/0/1
Related commands
apply loadshare
apply precedence
Use apply precedence to set a precedence for IPv6 packets.
Use undo apply precedence to restore the default.
Syntax
apply precedence { type | value }
undo apply precedence
Default
No precedence is set for IPv6 packets.
Views
IPv6 policy node view
Predefined user roles
network-admin
Parameters
type: Specifies the precedence type for IPv6 packets.
value: Specifies the precedence for IPv6 packets. Eight precedence values (0 to 7) are available. Each precedence value corresponds to a precedence type, as shown in Table 1. You can set either a precedence value or a precedence type for IPv6 packets.
Table 1 IP precedences and the corresponding types
|
Precedence value |
Precedence type |
|
0 |
routine |
|
1 |
priority |
|
2 |
immediate |
|
3 |
flash |
|
4 |
flash-override |
|
5 |
critical |
|
6 |
internet |
|
7 |
network |
Examples
# Set the precedence to 5 (critical) for IPv6 packets.
<Sysname> system-view
[Sysname]ipv6 policy-based-route aa permit node 11
[Sysname-pbr6-aa-11] apply precedence critical
apply remark-vpn
Use apply remark-vpn to enable VPN remark action.
Use undo apply remark-vpn to restore the default.
Syntax
apply remark-vpn
undo apply remark-vpn
Default
VPN remark action is not configured.
Views
IPv6 policy node view
Predefined user roles
network-admin
Usage guidelines
VPN remark action marks the matching packets as belonging to the VPN instance to which they are forwarded based on the apply access-vpn vpn-instance command. All subsequent service modules of IPv6 PBR handle the packets as belonging to the re-marked VPN instance.
If the VPN remark action is not enabled, the forwarded matching packets are marked as belonging to the VPN instance or the public network from which they were received.
VPN remark action applies only to packets that have been successfully forwarded based on the apply access-vpn vpn-instance command.
Examples
# Forward packets that match ACL 3000 based on the forwarding table of VPN instance vpn1 and perform VPN remark action on the successfully forwarded packets.
<Sysname> system-view
[Sysname] ipv6 policy-based-route aaa permit node 10
[Sysname-pbr6-aaa-10] if-match acl 3000
[Sysname-pbr6-aaa-10] apply access-vpn vpn-instance vpn1
[Sysname-pbr6-aaa-10] apply remark-vpn
Related commands
apply access-vpn
apply srv6-policy
Use apply srv6-policy to set SRv6 TE policies.
Use undo apply srv6-policy to remove SRv6 TE policies.
Syntax
apply srv6-policy { endpoint color [ { sid | vpnsid } sid ] }&<1-n>
undo apply srv6-policy [ { endpoint color }&<1-n> ]
Default
No SRv6 TE policies are set.
Views
IPv6 policy node view
Predefined user roles
network-admin
Parameters
endpoint: Specifies an SRv6 TE policy by its endpoint IPv6 address.
color: Specifies an SRv6 TE policy by its color attribute value in the range of 0 to 4294967295.
sid: Indicates that the SRv6 SID of the destination node is a public network SID.
vpnsid: Indicates that the SRv6 SID of the destination node is a VPN SID.
sid: Specifies the SRv6 SID of the destination node in IPv6 address format.
&<1-n>: Indicates that you can specify up to n SRv6 TE policies.
Usage guidelines
You can specify multiple SRv6 TE policies for backup in one command line or by executing this command multiple times. The first available SRv6 TE policy selected according to configuration order will be used to forward matching packets.
Without any SRv6 TE policy specified, the undo apply srv6-policy command removes all SRv6 TE policies.
Use the { sid | vpnsid } sid option to specify the SRv6 SID of the destination node and its attribute information (public network SID or VPN SID). The attribute information is not encapsulated in packets and does not affect packet forwarding.
When encapsulating packets matching the SRv6 TE policy, the source node adds the SRv6 SID of the destination node to the SID list in the SRH header of the packets. Upon receiving the packets, the destination node uses the SRv6 SID to perform an SRv6 local SID forwarding table lookup to forward the packets.
Examples
# Specify an SRv6 TE policy with destination node IPv6 address 1000::1, color attribute value 10, and destination node SRv6 SID 2000::2.
<Sysname> system-view
[Sysname] ipv6 policy-based-route aa permit node 1
[Sysname-pbr6-aa-1] apply srv6-policy 1000::1 10 sid 2000::2
Related commands
apply loadshare
display ipv6 policy-based-route
Use display ipv6 policy-based-route to display IPv6 PBR policy information.
Syntax
display ipv6 policy-based-route [ policy policy-name ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
policy policy-name: Specifies a policy by its name, a case-sensitive string of 1 to 19 characters. If you do not specify a policy, this command displays information for all IPv6 PBR policies.
Examples
# Display all IPv6 policy information.
<Sysname> display ipv6 policy-based-route
Policy name: aaa
node 1 permit:
if-match acl 2000
apply next-hop 1000::1
node 5 permit:
if-match acl 3500
apply srv6-policy 1000::1 10 sid 2000::2(NID: 2150629377)
apply default-srv6-policy 3000::3 20 vpnsid 4000::4(NID: 2149580801)
Table 2 Command output
|
Field |
Description |
|
node 1 permit |
The match mode of Node 1 is permit. |
|
if-match acl |
Compares IPv6 packets with IPv6 ACL. |
|
apply next-hop |
Specifies a next hop for permitted IPv6 packets. |
|
apply srv6-policy 1000::1 10 sid 2000::2(NID: 2150629377) |
Specifies an SRv6 TE policy for permitted IPv6 packets. Associated information about the SRv6 TE policy include: · Destination node IPv6 address 1000::1. · Color attribute value 10. · Destination node SRv6 SID 2000::2. · Next Hop Label Forwarding Entry (NHLFE) index 2150629377. |
|
apply default-srv6-policy 3000::3 20 vpnsid 4000::4(NID: 2149580801) |
Specifies a default SRv6 TE policy for permitted IPv6 packets. Associated information about the SRv6 TE policy include: · Destination node IPv6 address 3000::3. · Color attribute value 20. · Destination node SRv6 SID 4000::4. · NHLFE index 2149580801. |
Related commands
ipv6 policy-based-route (system view)
display ipv6 policy-based-route interface
Use display ipv6 policy-based-route interface to display IPv6 interface PBR configuration and statistics.
Syntax
In standalone mode:
display ipv6 policy-based-route interface interface-type interface-number
In IRF mode:
display ipv6 policy-based-route interface interface-type interface-number [ slot slot-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface-type interface-number: Specifies an interface by its type and number.
slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command displays IPv6 interface PBR configuration and statistics for the master device. (In IRF mode.)
Examples
# Display IPv6 PBR configuration and statistics on GigabitEthernet 1/0/1
<Sysname> display ipv6 policy-based-route interface gigabitethernet 1/0/1
Policy based routing information for interface GigabitEthernet1/0/1(failed):
Policy name: aaa
node 0 deny:
Matches: 0
node 1 permit:
if-match acl 3999
Matches: 0
node 2 permit:
if-match acl 2000
apply next-hop 1000::1
apply output-interface GigabitEthernet1/0/2 track 1 (down)
apply output-interface GigabitEthernet1/0/3 track 2 (inactive)
Matches: 0
node 5 permit:
if-match acl 3101
apply next-hop 1000::1
Matches: 0
node 8 permit:
if-match acl 3200
apply srv6-policy 1000::1 10 sid 2000::2(NID: 2150629377)
apply default-srv6-policy 3000::3 20 vpnsid 4000::4(NID: 2149580801)
Matches: 0
Total matches: 0
Table 3 Command output
|
Field |
Description |
|
Policy based routing information for interface XXXX |
IPv6 PBR configuration and statistics on the interface. This field displays failed in brackets if none of the nodes in the policy has been successfully issued to the driver. To issue the policy, you must remove the policy from the interface and then apply it on the interface again. The failed status is available on a per-slot basis. To obtain this information, you must specify a slot number when you execute the command. · For a global interface (for example, a VLAN interface), which might have member physical interfaces on multiple slots, specify a slot that contains its member interfaces. · For a physical interface, specify its slot number. |
|
node 0 deny node 2 permit |
Match mode of the node, permit or deny. If a node fails to be issued to the driver, the command displays the cause in brackets, which include: · not support—The device does not support the match criteria configured on the node. · no resource—No sufficient resources (for example, ACLs) are available for the node. NOTE: The cause is available only on a per-slot basis. To obtain this information, you must specify a slot number when you execute the command. · For a global interface (for example, a VLAN interface), which might have member physical interfaces on multiple slots, specify a slot that contains its member interfaces. · For a physical interface, specify its slot number. |
|
if-match acl |
Compares IPv6 packets with the IPv6 ACL. |
|
apply next-hop |
Specifies a next hop for permitted IPv6 packets. |
|
apply output-interface |
Specifies an output interface for permitted packets. The interface status includes the following: · down—The interface is down at network layer. · inactive—The interface is not in position. |
|
apply srv6-policy 1000::1 10 sid 2000::2(NID: 2150629377) |
Specifies an SRv6 TE policy for permitted IPv6 packets. Associated information about the SRv6 TE policy include: · Destination node IPv6 address 1000::1. · Color attribute value 10. · Destination node SRv6 SID 2000::2. · NHLFE index 2150629377. |
|
apply default-srv6-policy 3000::3 20 vpnsid 4000::4(NID: 2149580801) |
Specifies a default SRv6 TE policy for permitted IPv6 packets. Associated information about the SRv6 TE policy include: · Destination node IPv6 address 3000::3. · Color attribute value 20. · Destination node SRv6 SID 4000::4. · NHLFE index 2149580801. |
|
Matches |
Number of successful matches on the node. If the device does not have sufficient resources to count matches, this field displays no statistics resource in brackets. NOTE: The statistics collection failure cause is available only on a per-slot basis. To obtain this information, you must specify a slot number when you execute the command. · For a global interface (for example, a VLAN interface), which might have member physical interfaces on multiple slots, specify a slot that contains its member interfaces. · For a physical interface, specify its slot number. |
|
Total matches |
Total number of successful matches on all nodes. |
Related commands
ipv6 policy-based-route (interface view)
display ipv6 policy-based-route local
Use display ipv6 policy-based-route local to display IPv6 local PBR configuration and statistics.
Syntax
In standalone mode:
display ipv6 policy-based-route local
In IRF mode:
display ipv6 policy-based-route local [ slot slot-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command displays IPv6 local PBR configuration and statistics for the master device. (In IRF mode.)
Examples
# Display IPv6 local PBR configuration and statistics.
<Sysname> display ipv6 policy-based-route local
Policy based routing information for local:
Policy name: aaa
node 0 deny:
Matches: 0
node 1 permit:
if-match acl 3999
Matches: 0
node 2 permit:
if-match acl 2000
apply next-hop 1::1
Matches: 0
node 5 permit:
if-match acl 3101
apply next-hop 2::2
Matches: 0
node 8 permit:
if-match acl 3200
apply srv6-policy 1000::1 10 sid 2000::2(NID: 2150629377)
apply default-srv6-policy 3000::3 20 vpnsid 4000::4(NID: 2149580801)
Matches: 0
Total matches: 0
Table 4 Command output
|
Field |
Description |
|
Policy based routing information for local |
IPv6 local PBR configuration and statistics. |
|
node 0 deny/node 2 permit |
Match mode of the node, permit or deny. |
|
if-match acl |
Compares packets with the ACL. |
|
apply next-hop |
Specifies a next hop for permitted packets. |
|
apply srv6-policy 1000::1 10 sid 2000::2(NID: 2150629377) |
Specifies an SRv6 TE policy for permitted IPv6 packets. Associated information about the SRv6 TE policy include: · Destination node IPv6 address 1000::1. · Color attribute value 10. · Destination node SRv6 SID 2000::2. · Next Hop Label Forwarding Entry (NHLFE) index 2150629377. |
|
apply default-srv6-policy 3000::3 20 vpnsid 4000::4(NID: 2149580801) |
Specifies a default SRv6 TE policy for permitted IPv6 packets. Associated information about the SRv6 TE policy include: · Destination node IPv6 address 3000::3. · Color attribute value 20. · Destination node SRv6 SID 4000::4. · NHLFE index 2149580801. |
|
Matches |
Number of successful matches on the node. |
|
Total matches |
Total number of successful matches on all nodes. |
Related commands
ipv6 local policy-based-route
display ipv6 policy-based-route setup
Use display ipv6 policy-based-route setup to display IPv6 PBR configuration.
Syntax
display ipv6 policy-based-route setup
Views
Any view
Predefined user roles
network-admin
network-operator
Examples
# Display IPv6 PBR configuration.
<Sysname> display ipv6 policy-based-route setup
Policy name Type Interface
pr01 Forward GigabitEthernet 1/0/1
pr02 Local N/A
Table 5 Command output
|
Field |
Description |
|
Policy name |
IPv6 PBR policy name. |
|
Type |
Type of the IPv6 PBR: · Forward—IPv6 interface PBR. · Local—IPv6 local PBR. |
|
Interface |
Interface where the policy is applied. This field displays N/A for an IPv6 local PBR policy. |
if-match acl
Use if-match acl to set an ACL match criterion.
Use undo if-match acl to restore the default.
Syntax
if-match acl { ipv6-acl-number | name ipv6-acl-name }
undo if-match acl
Default
No ACL match criterion is set.
Views
IPv6 policy node view
Predefined user roles
network-admin
Parameters
ipv6-acl-number: Specifies an IPv6 ACL by its number in the range of 2000 to 3999. The value range of a basic ACL is 2000 to 2999 and that of an advanced ACL is 3000 to 3999.
name ipv6-acl-name: Specifies an IPv6 ACL by its name, a case-insensitive string of 1 to 63 characters starting with a letter. The ACL name cannot be all. For the command to take effect, make sure the specified IPv6 ACL is a basic or advanced ACL.
Usage guidelines
If the specified ACL does not exist or has no rules configured, no packets will match the ACL.
If the vpn-instance keyword is specified for an ACL rule, the rule applies to only VPN packets. If the vpn-instance keyword is not specified, the rule applies to only public network packets.
Examples
# Configure Node 10 of policy aa to permit the packets matching ACL 2000.
<Sysname> system-view
[Sysname] ipv6 policy-based-route aa permit node 10
[Sysname-pbr6-aa-10] if-match acl 2000
# Configure Node 10 of policy aa to permit the packets matching ACL aaa.
[Sysname] ipv6 policy-based-route aa permit node 10
[Sysname-pbr6-aa-10] if-match acl name aaa
if-match app-group
Use if-match app-group to set application group match criteria.
Use undo if-match app-group to delete application group match criteria.
Syntax
if-match app-group app-group-name&<1-6>
undo if-match app-group [ app-group-name&<1-6> ]
Default
No application group match criteria are set.
Views
Policy node view
Predefined user roles
network-admin
Parameters
app-group-name&<1-6>: Specifies up to six application groups by their names. An application group name is a case-insensitive string of 1 to 63 characters, which can contain letters, digits, underscores (_), and hyphens (-). The application group name cannot be Invalid, other, or any application group name predefined by the system.
Usage guidelines
The application match criteria apply only to interface PBR.
If you specify an application group, the undo if-match app-group command deletes the application group match criterion.
If you do not specify an application group, the undo if-match app-group command deletes all application group match criteria.
Examples
# Specify the application group test as a match criterion.
[Sysname] ipv6 policy-based-route aa permit node 11
[Sysname-pbr6-aa-11] if-match app-group test
if-match object-group
Use if-match object-group to set service object group match criteria.
Use undo if-match object-group to delete service object group match criteria.
Syntax
if-match object-group service object-group-name&<1-6>
undo if-match object-group service [ object-group-name&<1-6> ]
Default
No service object group match criteria are set.
Views
Policy node view
Predefined user roles
network-admin
Parameters
object-group-name&<1-6>: Specifies up to six service object groups by their names. The value for n varies by device model. A service object group name is a case-insensitive string of 1 to 63 characters, which can contain letters, digits, underscores (_), and hyphens (-).
Usage guidelines
If you specify a service object group, the undo if-match object-group command deletes the service object group match criterion.
If you do not specify a service object group, the undo if-match object-group command deletes all service object group match criteria.
Examples
# Specify the service object group test as a match criterion.
<Sysname> system-view
[Sysname] ipv6 policy-based-route aa permit node 11
[Sysname-pbr6-aa-11] if-match object-group service test
if-match packet-length
Use if-match packet-length to set an IPv6 packet length match criterion.
Use undo if-match packet-length to restore the default.
Syntax
if-match packet-length min-len max-len
undo if-match packet-length
Default
No packet length match criterion is set.
Views
IPv6 policy node view
Predefined user roles
network-admin
Parameters
min-len: Specifies the minimum IPv6 packet length in the range of 1 to 65535 bytes.
max-len: Specifies the maximum IP packet length in the range of 1 to 65535 bytes. The maximum length must be no less than the minimum length.
Usage guidelines
The packet length range includes boundary values. For example, if you set the min-len and max-len arguments to 100 and 200, respectively, packets with lengths of 100 bytes and 200 bytes are also matched.
Examples
# Match packets with a length from 100 to 200 bytes.
[Sysname] ipv6 policy-based-route aa permit node 11
[Sysname-pbr6-aa-11] if-match packet-length 100 200
if-match source-ipv6
Use if-match source-ipv6 to set a source IPv6 address match criterion.
Use undo if-match source-ipv6 to delete the source IPv6 address match criterion.
Syntax
if-match source-ipv6 { interface interface-type interface-number | [ vpn-instance vpn-instance-name ] ipv6-address }
undo if-match source-ipv6
Default
No source IPv6 address match criterion is set.
Views
IPv6 policy node view
Predefined user roles
network-admin
Parameters
interface interface-type interface-number: Specifies an interface by its type and number. The IPv6 global unicast address of the interface will be used to match packets. If the interface has multiple IPv6 global unicast addresses, the lowest IPv6 address will be used.
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 this option, the specified IPv6 address belongs to the public network.
ipv6-address: Specifies an IPv6 address, which must be an IPv6 global unicast address.
Usage guidelines
As a best practice to specify an interface for the command to match locally generated packets, specify the output interface of the packets.
As a best practice, do not specify the interface of a VXLAN tunnel automatically created by EVPN for this command. If the tunnel interface number changes upon VXLAN tunnel reestablishment, the match criterion no longer takes effect. For more information about EVPN, see EVPN overview in EVPN Configuration Guide.
If you execute this command multiple times on an IPv6 policy node, the most recent configuration takes effect.
Examples
# Match packets with source IPv6 address 1::1.
<Sysname> system-view
[Sysname] ipv6 policy-based-route aa permit node 11
[Sysname-pbr6-aa-11] if-match source-ipv6 1::1
ipv6 local policy-based-route
Use ipv6 local policy-based-route to configure IPv6 local PBR based on a specified policy.
Use undo ipv6 local policy-based-route to restore the default.
Syntax
ipv6 local policy-based-route policy-name
undo ipv6 local policy-based-route
Default
No policy is specified for IPv6 local PBR.
Views
System view
Predefined user roles
network-admin
Parameters
policy-name: Specifies a policy by its name, a case-sensitive string of 1 to 19 characters. The specified IPv6 policy must already exist.
Usage guidelines
You can apply only one policy locally. Before you apply a new policy, you must first remove the current policy.
IPv6 local PBR is used to route locally generated packets except the packets destined for the sender. This feature might affect local services. Do not configure IPv6 local PBR unless doing so is required.
Examples
# Configure IPv6 local PBR based on policy aaa.
<Sysname> system-view
[Sysname] ipv6 local policy-based-route aaa
Related commands
display ipv6 policy-based-route local
ipv6 policy-based-route (interface view)
Use ipv6 policy-based-route to configure IPv6 interface PBR by applying an IPv6 policy to an interface.
Use undo ipv6 policy-based-route to restore the default.
Syntax
ipv6 policy-based-route policy-name
undo ipv6 policy-based-route
Default
No IPv6 is applied to an interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
policy-name: Specifies a policy by its name, a case-sensitive string of 1 to 19 characters. The specified policy must already exist.
Examples
# Apply policy aaa to GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ipv6 policy-based-route aaa
Related commands
display ipv6 policy-based-route interface
ipv6 policy-based-route (system view)
Use ipv6 policy-based-route to create an IPv6 policy node and enter its view, or enter the view of an existing IPv6 policy node.
Use undo ipv6 policy-based-route to delete an IPv6 policy or IPv6 policy node.
Syntax
ipv6 policy-based-route policy-name [ deny | permit ] node node-number
undo ipv6 policy-based-route policy-name [ deny | node node-number | permit ]
Default
No IPv6 policy nodes exist.
Views
System view
Predefined user roles
network-admin
Parameters
policy-name: Specifies a policy name, a case-sensitive string of 1 to 19 characters.
deny: Specifies the match mode for the policy node as deny.
permit: Specifies the match mode for the policy node as permit (default mode).
node node-number: Specifies the number of the IPv6 policy node, in the range of 0 to 65535. A smaller number has a higher priority.
Usage guidelines
To delete an IPv6 policy that has already applied to an interface, you must delete the policy from the interface first.
If a policy node is specified, the undo ipv6 policy-based-route command deletes the specified policy node. If a match mode is specified, the command deletes all nodes configured with the match mode. If no node is specified, the command deletes the whole policy.
Examples
# Create permit-mode Node 10 for IPv6 policy aaa and enter its view.
<Sysname> system-view
[Sysname] ipv6 policy-based-route aaa permit node 10
[Sysname-pbr6-aaa-10]
Related commands
display ipv6 policy-based-route
reset ipv6 policy-based-route statistics
Use reset ipv6 policy-based-route statistics to clear IPv6 PBR statistics.
Syntax
reset ipv6 policy-based-route statistics [ policy policy-name ]
Views
User view
Predefined user roles
network-admin
Parameters
policy policy-name: Specifies a policy by its name, a case-sensitive string of 1 to 19 characters. If you do not specify a policy, this command clears IPv6 PBR statistics for all policies.
Examples
# Clear all IPv6 PBR statistics.
<Sysname> reset ipv6 policy-based-route statistics
