- Table of Contents
-
- 07-Layer 3—IP Routing Command Reference
- 00-Preface
- 01-Basic IP routing commands
- 02-Static routing commands
- 03-RIP commands
- 04-OSPF commands
- 05-IS-IS commands
- 06-Basic BGP commands
- 07-Advanced 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-DCN commands
- Related Documents
-
Title | Size | Download |
---|---|---|
12-IPv6 policy-based routing commands | 140.64 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)
ipv6 policy-based-route-log enable
reset ipv6 policy-based-route statistics
IPv6 policy-based routing commands
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 }
undo apply access-vpn { public | vpn-instance [ vpn-instance-name ] }
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: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. The specified VPN 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.
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.
This command cannot be configured with other actions for the same IPv6 policy node. You can configure the command and other actions for different nodes in the same policy. After configuration, packets might not match the nodes based on ascending order of the node numbers.
Examples
# Specify the VPN 1 forwarding tables on node 10. In this example, VPN 1 already exists.
# Set VPN 1 and VPN 2 for node 10. (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
Related commands
apply remark-vpn
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 ] { ipv6-address [ direct ] [ track track-entry-number ] }&<1-2>
undo apply default-next-hop [ [ vpn-instance vpn-instance-name ] ipv6-address&<1-2> ]
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.
ipv6-address: Specifies the IPv6 address of the default next hop. If you do not specify the vpn-instance vpn-instance-name option, 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-2>: Indicates that the argument before it can be entered up to two times.
Usage guidelines
You can specify multiple default next hops for backup 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
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 ] }
undo apply default-output-interface [ interface-type interface-number ]
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.
Usage guidelines
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.
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, packet forwarding might fail. For more information about EVPN VXLAN, see EVPN Configuration Guide.
With a default output interface specified, the undo apply default-output-interface command removes the default output interface.
The default output interfaces specified in this command cannot be automatically created tunnel interfaces.
Without any default output interface specified, the undo apply default-output-interface command removes all default output interfaces.
Examples
# Specify HundredGigE 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 hundredgige 1/0/1
apply default-sr-policy
Use apply default-sr-policy to set default SR-MPLS TE policies.
Use undo apply default-sr-policy to remove default SR-MPLS TE policies.
Syntax
apply default-sr-policy { endpoint color }&<1-2>
undo apply default-sr-policy [ { endpoint color }&<1-2> ]
Default
No default SR-MPLS TE policies are set.
Views
IPv6 policy node view
Predefined user roles
network-admin
Parameters
endpoint: Specifies a default SR-MPLS TE policy by its endpoint IP address.
color: Specifies a default SR-MPLS TE policy by its color attribute value in the range of 0 to 4294967295.
&<1-2>: Indicates that you can specify up to two default SR-MPLS TE policies.
Usage guidelines
You can specify multiple default SR-MPLS TE policies for backup in one command line or by executing this command multiple times. The first available default SR-MPLS TE policy selected according to configuration order will be used to forward matching packets. In the current software version, the device supports forwarding packets to only the public network.
Without a default SR-MPLS TE policy specified, the undo form of the command removes the default SR-MPLS TE policy. Without any default SR-MPLS TE policy specified, the undo form of the command removes all default SR-MPLS TE policies.
Examples
# Specify a default SR-MPLS TE policy with destination node IPv4 address 10.0.0.1 and color attribute value 10.
[Sysname] ipv6 policy-based-route aa permit node 1
[Sysname-pbr6-aa-1] apply default-sr-policy 10.0.0.1 10
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-2>
undo apply default-srv6-policy [ { endpoint color }&<1-2> ]
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-2>: Indicates that you can specify up to two 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 on the source node 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 SRH header of the packets. The SRv6 SID is added after the SID list of the default SRv6 TE policy. Upon receiving the packets forwarded based on the default SRv6 TE policy, the destination node uses the specified 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
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 ] { ipv6-address [ direct ] [ track track-entry-number ] } &<1-2>
undo apply next-hop [ [ vpn-instance vpn-instance-name ] ipv6-address&<1-2> ]
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.
ipv6-address: Specifies the IPv6 address of the next hop. If you do not specify the vpn-instance vpn-instance-name option, 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.
&<1-2>: Indicates that you can repeat the previous group of parameters to configure up to two next hops.
Usage guidelines
You can specify multiple next hops for backup 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
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 ] }
undo apply output-interface [ interface-type interface-number ]
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.
Usage guidelines
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.
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, packet forwarding might fail. For more information about EVPN VXLAN, see EVPN Configuration Guide.
The output interfaces specified in this command cannot be automatically created tunnel 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 HundredGigE 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 hundredgige 1/0/1
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 vpn-instance
apply sr-policy
Use apply sr-policy to set SR-MPLS TE policies.
Use undo apply sr-policy to remove SR-MPLS TE policies.
Syntax
apply sr-policy { endpoint color }&<1-2>
undo apply sr-policy [ { endpoint color }&<1-2> ]
Default
No SR-MPLS TE policies are set.
Views
IPv6 policy node view
Predefined user roles
network-admin
Parameters
endpoint: Specifies an SR-MPLS TE policy by its endpoint IPv4 address.
color: Specifies an SR-MPLS TE policy by its color attribute value in the range of 0 to 4294967295.
&<1-2>: Indicates that you can specify up to two SR-MPLS TE policies.
Usage guidelines
You can specify multiple SR-MPLS TE policies for backup in one command line or by executing this command multiple times. The first available SR-MPLS TE policy selected according to configuration order will be used to forward matching packets. In the current software version, the device supports forwarding packets to only the public network.
Without an SR-MPLS TE policy specified, the undo form of the command removes the SR-MPLS TE policy. Without any SR-MPLS TE policy specified, the undo form of the command removes all SR-MPLS TE policies.
Examples
# Specify an SR-MPLS TE policy with destination node IPv4 address 10.0.0.1 and color attribute value 10.
[Sysname] ipv6 policy-based-route aa permit node 1
[Sysname-pbr6-aa-1] apply sr-policy 10.0.0.1 10
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-2>
undo apply srv6-policy [ { endpoint color }&<1-2> ]
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-2>: Indicates that you can specify up to two 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 on the source node 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 SRH header of the packets. The SRv6 SID is added after the SID list of the SRv6 TE policy. Upon receiving the packets forwarded based on the SRv6 TE policy, the destination node uses the specified 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
apply statistics
Use apply statistics to enable match counting on an IPv6 policy node.
Use undo apply statistics to restore the default.
Syntax
apply statistics
undo apply statistics
Default
Match counting is disabled on an IPv6 policy node.
Views
IPv6 policy node view
Predefined user roles
network-admin
Usage guidelines
To include the number of successful matches and matching bytes on an IPv6 policy node in the statistics displayed by a display command, execute this command. As a best practice to conserve hardware resources, disable this counting function.
This apply clause is always executed for the IPv6 policy node.
After enabling this feature, you cannot specify the share-mode keyword when applying a policy to an interface for IPv6 interface PBR.
Examples
# Enable match counting on IPv6 policy node 1.
<Sysname> system-view
[Sysname] ipv6 policy-based-route 1 permit node 1
[Sysname-pbr6-1-1] apply statistics
description
Use description to configure a description for an IPv6 policy node.
Use undo description to restore the default.
Syntax
description text
undo description
Default
No description is configured for an IPv6 policy node.
Views
IPv6 policy node view
Predefined user roles
network-admin
Parameters
text: Specifies a description, a case-sensitive string of 1 to 127 characters.
Examples
# Configure the description as Officeuse for IPv6 policy node 1.
<Sysname> system-view
[Sysname] ipv6 policy-based-route 1 permit node 1
[Sysname-pbr6-1-1] description Officeuse
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 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 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
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 a card by its slot number. If you do not specify a card, this command displays IPv6 interface PBR configuration and statistics for the active MPU.
Examples
# Display IPv6 PBR configuration and statistics on HundredGigE 1/0/1.
<Sysname> display ipv6 policy-based-route interface hundredgige 1/0/1
Policy based routing information for interface HundredGigE1/0/1:
Policy name: aaa
node 0 deny:
Matches: 0, bytes: 0
node 1 permit:
if-match acl 3999
Matches: 0, bytes: 0
node 2 permit:
if-match acl 2000
apply next-hop 1000::1
apply output-interface HundredGigE1/0/2 track 1 (down)
apply output-interface HundredGigE1/0/3 track 2 (inactive)
Matches: 0, bytes: 0
node 5 permit:
if-match acl 3101
apply next-hop 1000::1
Matches: 0, bytes: 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)
Matched: 0, bytes: 0
Total matches: 0, total bytes: 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. NOTE: 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 track 1 |
Specifies an output interface for permitted packets. The interface status includes the following: · up—The interface is up. · 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 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 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 support counting successful matches on a node, this field displays N/A. If match counting is disabled on the node, this field is not displayed. 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. |
bytes |
Number of matching bytes on the node. This field displays N/A if the device does not support counting matching bytes on a node. This field is not displayed if match counting is disabled on the node. |
Total matches |
Total number of successful matches on all nodes. This field displays N/A if the device does not support counting successful matches on a node. This field is not displayed if match counting is disabled on all nodes. |
total bytes |
Total number of matching bytes on all nodes. This field displays N/A if the device does not support counting matching bytes on a node. This field is not displayed if match counting is disabled 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
display ipv6 policy-based-route local [ slot slot-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays IPv6 local PBR configuration and statistics for the active MPU.
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, bytes: 0
node 1 permit:
if-match acl 3999
Matches: 0, bytes: 0
node 2 permit:
if-match acl 2000
apply next-hop 1::1
Matches: 0, bytes: 0
node 5 permit:
if-match acl 3101
apply next-hop 2::2
Matches: 0, bytes: 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)
Matched: 0, bytes: 0
Total matches: 0, total bytes: 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 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 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. This field displays N/A if the device does not support counting successful matches on a node. This field is not displayed if match counting is disabled on the node. |
bytes |
Number of matching bytes on the node. This field displays N/A if the device does not support counting matching bytes on a node. This field is not displayed if match counting is disabled on the node. |
Total matches |
Total number of successful matches on all nodes. This field displays N/A if the device does not support counting successful matches on a node. This field is not displayed if match counting is disabled on all nodes. |
total bytes |
Total number of matching bytes on all nodes. This field displays N/A if the device does not support counting matching bytes on a node. This field is not displayed if match counting is disabled 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 HundredGigE1/0/1
pr02 Local N/A
pr03 Global N/A
Table 5 Command output
Field |
Description |
Policy name |
Policy name. |
Type |
Type of the PBR: · Forward—Interface PBR. · Local—Local PBR. |
Interface |
Interface where the policy is applied. This field displays N/A for IPv6 local PBR and IPv6 global PBR. |
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.
When specifying an ACL for an IPv6 PBR policy, make sure the ACL rules are not configured with the vpn-instance keyword.
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
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 referenced 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 [ share-mode ]
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.
share-mode: Sets the resource sharing mode for the policy. An IPv6 policy in this mode uses the same hardware resources on different interfaces of a card. If you do not specify this keyword, the policy uses different hardware resources.
Usage guidelines
Typically, an IPv6 policy on different interfaces of a card uses different hardware resources. To avoid resource usage overhead, you can set the resource sharing mode when applying the policy to each interface. This mode allows the policy to use the same hardware resources on different interfaces of the card.
You can set only one mode for the policy on an interface. Before you change the mode of the policy, you must first remove the current policy from the interface.
You can apply only one ACL, QoS policy, or IPv6 PBR policy with the share-mode keyword specified to one direction of an interface. For information about ACL and QoS policies, see ACL commands and QoS policy commands in ACL and QoS Command Reference.
After configuring the apply statistics command, you cannot specify the share-mode keyword in this command.
Examples
# Apply policy aaa to HundredGigE 1/0/1.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/1
[Sysname-HundredGigE1/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. A smaller number has a higher priority. The value range for the node-number argument is 0 to 2047.
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
ipv6 policy-based-route-log enable
Use ipv6 policy-based-route-log enable to enable the IPv6 PBR logging feature.
Use undo ipv6 policy-based-route-log enable to disable the IPv6 PBR logging feature.
Syntax
ipv6 policy-based-route-log enable
undo ipv6 policy-based-route-log enable
Default
The IPv6 PBR logging feature is disabled.
Views
System view
Predefined user roles
network-admin
Usage guidelines
The IPv6 PBR logging feature helps the administrator locate and fix faults. The feature logs IPv6 PBR events and sends the logs to the information center. The information center processes the logs according to output rules. For more information about the information center, see System Management Configuration Guide.
Excessive IPv6 PBR log messages degrade the performance of the device. To avoid this problem, disable the IPv6 PBR logging feature.
Examples
# Enable the IPv6 PBR logging feature.
<Sysname> system-view
[Sysname] ipv6 policy-based-route-log enable
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