Contents

Configuring IPv6 PBR· 1

About IPv6 PBR·· 1

IPv6 packet forwarding process· 1

IPv6 PBR types· 1

Policy· 1

IPv6 PBR and Track· 2

Restrictions and guidelines: IPv6 PBR configuration· 2

IPv6 PBR tasks at a glance· 2

Configuring an IPv6 policy· 3

Creating an IPv6 node· 3

Setting match criteria for an IPv6 node· 3

Configuring actions for an IPv6 node· 3

Specifying a policy for IPv6 PBR·· 5

Specifying an IPv6 policy for IPv6 local PBR·· 5

Specifying an IPv6 policy for IPv6 interface PBR·· 5

Enabling the IPv6 PBR logging feature· 5

Display and maintenance commands for IPv6 PBR·· 6

IPv6 PBR configuration examples· 6

Example: Configuring packet type-based IPv6 local PBR·· 6

Example: Configuring packet type-based IPv6 interface PBR·· 8

Configuring IPv6 PBR

About IPv6 PBR

IPv6 policy-based routing (PBR) uses user-defined policies to route IPv6 packets. A policy can specify parameters for packets that match specific criteria such as ACLs. The parameters include the next hop and output interface.

IPv6 packet forwarding process

A device forwards received IPv6 packets using the following process:

1.        The device uses PBR to forward matching packets.

2.        If one of the following events occurs, the device searches for a route (except the default route) in the routing table to forward packets:

¡  The packets do not match the PBR policy.

¡  The PBR-based forwarding fails.

3.        If the routing table-based forwarding fails, the device uses the default route to forward packets.

IPv6 PBR types

IPv6 PBR includes the following types:

·          Local PBR—Guides the forwarding of locally generated packets, such as the ICMP packets generated by using the ping command.

·          Interface PBR—Guides the forwarding of packets received on an interface only.

Policy

An IPv6 policy includes match criteria and actions to be taken on the matching packets. A policy can have one or multiple nodes as follows:

·          Each node is identified by a node number. A smaller node number has a higher priority.

·          A node contains if-match and apply clauses. An if-match clause specifies a match criterion, and an apply clause specifies an action.

·          A node has a match mode of permit or deny.

An IPv6 policy compares packets with nodes in priority order. If a packet matches the criteria on a node, it is processed by the action on the node. If the packet does not match any criteria on the node, it goes to the next node for a match. If the packet does not match the criteria on any node, the device performs a routing table lookup for the packet.

Relationship between if-match clauses

IPv6 PBR supports only the if-match acl clause to set an ACL match criterion. On a node, you can specify only one if-match clause.

Relationship between apply clauses

You can specify multiple apply clauses for a node, but some of them might not be executed. For more information about the relationship between the apply clauses, see "Configuring actions for an IPv6 node."

Relationship between the match mode and clauses on the node

Does a packet match all the if-match clauses on the node?	Match mode
	In permit mode	In deny mode
Yes	·         If the node contains apply clauses, IPv6 PBR executes the apply clauses on the node.If the IPv6 PBR-based forwarding succeeds, IPv6 PBR does not compare the packet with the next node. ·         If the node does not contain apply clauses, the device performs a routing table lookup for the packet.	The device performs a routing table lookup for the packet.
No	IPv6 PBR compares the packet with the next node.	IPv6 PBR compares the packet with the next node.

 

	NOTE: A node that has no if-match clauses matches any packet.

 

IPv6 PBR and Track

IPv6 PBR can work with the Track feature to dynamically adapt the availability status of an apply clause to the link status of a tracked object. The tracked object can be a next hop or output interface.

·          When the track entry associated with an object changes to Negative, the apply clause is invalid.

·          When the track entry changes to Positive or NotReady, the apply clause is valid.

For more information about Track and IPv6 PBR collaboration, see High Availability Configuration Guide.

Restrictions and guidelines: IPv6 PBR configuration

If a packet destined for the local device matches an IPv6 PBR policy, IPv6 PBR will execute the apply clauses in the policy, including the clause for forwarding. When you configure an IPv6 PBR policy, be careful to avoid this situation.

IPv6 PBR tasks at a glance

To configure IPv6 PBR, perform the following tasks:

1.        Configuring an IPv6 policy

a.    Creating an IPv6 node

b.    Setting match criteria for an IPv6 node

c.    Configuring actions for an IPv6 node

2.        Specifying a policy for IPv6 PBR

Choose the following tasks as needed:

¡  Specifying an IPv6 policy for IPv6 local PBR

¡  Specifying an IPv6 policy for IPv6 interface PBR

3.        (Optional.) Enabling the IPv6 PBR logging feature

Configuring an IPv6 policy

Creating an IPv6 node

1.        Enter system view.

system-view

2.        Create an IPv6 policy or policy node and enter its view.

ipv6 policy-based-route policy-name [ deny | permit ] node node-number

Setting match criteria for an IPv6 node

1.        Enter system view.

system-view

2.        Enter IPv6 policy node view.

ipv6 policy-based-route policy-name [ deny | permit ] node node-number

3.        Set an ACL match criterion.

if-match acl { ipv6-acl-number | name ipv6-acl-name }

By default, no ACL match criterion is set.

The ACL match criterion cannot match Layer 2 information.

Configuring actions for an IPv6 node

About apply clauses

IPv6 PBR supports the types of apply clauses shown in Table 1. The following apply clauses determine the packet forwarding paths in a descending order:

·          apply access-vpn vpn-instance

·          apply next-hop

·          apply output-interface

·          apply default-next-hop

Table 1 Priorities and meanings of apply clauses

Clause	Meaning	Priority
apply precedence	Sets an IP precedence.	This clause is always executed.
apply access-vpn vpn-instance	Sets VPN instances.	If a packet matches a forwarding entry of a specified VPN instance, it is forwarded in the VPN instance.
apply next-hop and apply output-interface	Sets next hops and sets output interfaces.	If both clauses are configured, only the apply next-hop clause is executed.
apply default-next-hop	Sets default next hops.	The clause takes effect only in the following cases: ·         No next hops are set or the next hops are invalid. ·         The packet does not match any route in the routing table.

 

Restrictions and guidelines for action configuration

If you specify a next hop, IPv6 PBR periodically performs a lookup in the FIB table to determine its availability. Temporary service interruption might occur if IPv6 PBR does not update the route immediately after its availability status changes.

Setting an IP preference

1.        Enter system view.

system-view

2.        Enter IPv6 policy node view.

ipv6 policy-based-route policy-name [ deny | permit ] node node-number

3.        Set an IP precedence.

apply precedence { type | value }

By default, no IP precedence is specified.

Configuring actions for a node

1.        Enter system view.

system-view

2.        Enter IPv6 policy node view.

ipv6 policy-based-route policy-name [ deny | permit ] node node-number

3.        Configure actions for a node.

¡  Set VPN instances.

apply access-vpn vpn-instance vpn-instance-name

By default, no VPN instance is specified.

¡  Set next hops for permitted IPv6 packets.

apply next-hop [ vpn-instance vpn-instance-name ] { ipv6-address [ direct ] [ track track-entry-number ] }&<1-2>

By default, no next hop is specified.

You can specify multiple next hops for backup or load sharing in one command line or by executing this command multiple times.

¡  Set output interfaces.

apply output-interface { interface-type interface-number [ track track-entry-number ] }

By default, no output interface is specified.

¡  Set default next hops.

apply default-next-hop [ vpn-instance vpn-instance-name ] { ipv6-address [ direct ] [ track track-entry-number ] }&<1-2>

By default, no default next hop is specified.

You can specify multiple default next hops for backup or load sharing in one command line or by executing this command multiple times.

Specifying a policy for IPv6 PBR

Specifying an IPv6 policy for IPv6 local PBR

About IPv6 local PBR

Perform this task to specify an IPv6 policy for IPv6 local PBR to guide the forwarding of locally generated packets.

Restrictions and guidelines

You can specify only one policy for IPv6 local PBR and must make sure the specified policy already exists. Before you apply a new policy, you must first remove the current policy.

IPv6 local PBR might affect local services, such as ping and Telnet. When you use IPv6 local PBR, make sure you fully understand its impact on local services of the device.

Procedure

1.        Enter system view.

system-view

2.        Specify an IPv6 policy for IPv6 local PBR.

ipv6 local policy-based-route policy-name

By default, IPv6 local PBR is not enabled.

Specifying an IPv6 policy for IPv6 interface PBR

About interface PBR

Perform this task to apply an IPv6 policy to an interface to guide the forwarding of packets received on the interface only.

Restrictions and guidelines

You can apply only one policy to an interface and must make sure the specified policy already exists. Before you apply a new policy, you must first remove the current policy from the interface.

You can apply a policy to multiple interfaces.

Procedure

1.        Enter system view.

system-view

2.        Enter interface view.

interface interface-type interface-number

3.        Specify an IPv6 policy for IPv6 interface PBR.

ipv6 policy-based-route policy-name [ share-mode ]

By default, no IPv6 policy is applied to the interface.

Enabling the IPv6 PBR logging feature

About the IPv6 PBR logging feature

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 Network Management and Monitoring Configuration Guide.

Procedure

1.        Enter system view.

system-view

2.        Enable the IPv6 PBR logging feature.

ipv6 policy-based-route-log enable

By default, the IPv6 PBR logging feature is disabled.

Display and maintenance commands for IPv6 PBR

Execute display commands in any view and reset commands in user view.

 

Task	Command
Display IPv6 PBR policy information.	display ipv6 policy-based-route [ policy policy-name ]
Display IPv6 PBR configuration.	display ipv6 policy-based-route setup
(In standalone mode.) Display IPv6 local PBR configuration and statistics.	display ipv6 policy-based-route local [ slot slot-number ]
(In IRF mode.) Display IPv6 local PBR configuration and statistics.	display ipv6 policy-based-route local [ chassis chassis-number slot slot-number ]
(In standalone mode.) Display IPv6 interface PBR configuration and statistics.	display ipv6 policy-based-route interface interface-type interface-number [ slot slot-number ]
(In IRF mode.) Display IPv6 interface PBR configuration and statistics.	display ipv6 policy-based-route interface interface-type interface-number [ chassis chassis-number slot slot-number ]
Clear IPv6 PBR statistics.	reset ipv6 policy-based-route statistics [ policy policy-name ]

 

IPv6 PBR configuration examples

Example: Configuring packet type-based IPv6 local PBR

Network configuration

As shown in Figure 1, Router B and Router C are connected through Router A. Router B and Router C do not have a route to reach each other.

Configure IPv6 PBR on Router A to forward all TCP packets to the next hop 1::2 (Router B).

Figure 1 Network diagram

‌

Procedure

1.        Configure Router A:

# Configure the IPv6 addresses of GigabitEthernet 3/1/1 and GigabitEthernet 3/1/2.

<RouterA> system-view

[RouterA] interface gigabitethernet 3/1/1

[RouterA-GigabitEthernet3/1/1] ipv6 address 1::1 64

[RouterA-GigabitEthernet3/1/1] quit

[RouterA] interface gigabitethernet 3/1/2

[RouterA-GigabitEthernet3/1/2] ipv6 address 2::1 64

[RouterA-GigabitEthernet3/1/2] quit

# Configure ACL 3001 to match TCP packets.

[RouterA] acl ipv6 advanced 3001

[RouterA-acl-ipv6-adv-3001] rule permit tcp

[RouterA-acl-ipv6-adv-3001] quit

# Configure Node 5 for policy aaa to forward TCP packets to next hop 1::2.

[RouterA] ipv6 policy-based-route aaa permit node 5

[RouterA-pbr6-aaa-5] if-match acl 3001

[RouterA-pbr6-aaa-5] apply next-hop 1::2

[RouterA-pbr6-aaa-5] quit

# Configure IPv6 local PBR by applying policy aaa to Router A.

[RouterA] ipv6 local policy-based-route aaa

2.        On Router B, configure the IPv6 address of GigabitEthernet 3/1/1.

<RouterB> system-view

[RouterB] interface gigabitethernet 3/1/1

[RouterB-GigabitEthernet3/1/1] ipv6 address 1::2 64

3.        On Router C, configure the IPv6 address of GigabitEthernet 3/1/2.

<RouterC> system-view

[RouterC] interface gigabitethernet 3/1/2

[RouterC-GigabitEthernet3/1/2] ipv6 address 2::2 64

Verifying the configuration

1.        Perform telnet operations to verify that IPv6 local PBR on Router A operates as configured to forward the matching TCP packets to the next hop 1::2 (Router B), as follows:

# Verify that you can telnet to Router B from Router A successfully. (Details not shown.)

# Verify that you cannot telnet to Router C from Router A. (Details not shown.)

2.        Verify that Router A forwards packets other than TCP packets through GigabitEthernet 3/1/2. For example, verify that you can ping Router C from Router A. (Details not shown.)

Example: Configuring packet type-based IPv6 interface PBR

Network configuration

As shown in Figure 2, Router B and Router C do not have a route to reach each other.

Configure IPv6 PBR on Router A to forward all TCP packets received on GigabitEthernet 3/1/1 to the next hop 1::2 (Router B).

Figure 2 Network diagram

‌

Procedure

1.        Configure Router A:

# Configure RIPng.

<RouterA> system-view

[RouterA] ripng 1

[RouterA-ripng-1] quit

[RouterA] interface gigabitethernet 3/1/2

[RouterA-GigabitEthernet3/1/2] ipv6 address 1::1 64

[RouterA-GigabitEthernet3/1/2] ripng 1 enable

[RouterA-GigabitEthernet3/1/2] quit

[RouterA] interface gigabitethernet 3/1/3

[RouterA-GigabitEthernet3/1/3] ipv6 address 2::1 64

[RouterA-GigabitEthernet3/1/3] ripng 1 enable

[RouterA-GigabitEthernet3/1/3] quit

# Configure ACL 3001 to match TCP packets.

[RouterA] acl ipv6 advanced 3001

[RouterA-acl-ipv6-adv-3001] rule permit tcp

[RouterA-acl-ipv6-adv-3001] quit

# Configure Node 5 for policy aaa to forward TCP packets to next hop 1::2.

[RouterA] ipv6 policy-based-route aaa permit node 5

[RouterA-pbr6-aaa-5] if-match acl 3001

[RouterA-pbr6-aaa-5] apply next-hop 1::2

[RouterA-pbr6-aaa-5] quit

# Configure IPv6 interface PBR by applying policy aaa to GigabitEthernet 3/1/1.

[RouterA] interface gigabitethernet 3/1/1

[RouterA-GigabitEthernet3/1/1] ipv6 address 10::2 64

[RouterA-GigabitEthernet3/1/1] undo ipv6 nd ra halt

[RouterA-GigabitEthernet3/1/1] ripng 1 enable

[RouterA-GigabitEthernet3/1/1] ipv6 policy-based-route aaa

[RouterA-GigabitEthernet3/1/1] quit

2.        Configure RIPng on Router B.

<RouterB> system-view

[RouterB] ripng 1

[RouterB-ripng-1] quit

[RouterB] interface gigabitethernet 3/1/2

[RouterB-GigabitEthernet3/1/2] ipv6 address 1::2 64

[RouterB-GigabitEthernet3/1/2] ripng 1 enable

[RouterB-GigabitEthernet3/1/2] quit

3.        Configure RIPng on Router C.

<RouterC> system-view

[RouterC] ripng 1

[RouterC-ripng-1] quit

[RouterC] interface gigabitethernet 3/1/3

[RouterC-GigabitEthernet3/1/3] ipv6 address 2::2 64

[RouterC-GigabitEthernet3/1/3] ripng 1 enable

[RouterC-GigabitEthernet3/1/3] quit

Verifying the configuration

1.        Enable IPv6 and configure the IPv6 address 10::3 for Host A.

C:\>ipv6 install

Installing...

Succeeded.

C:\>ipv6 adu 4/10::3

2.        Perform telnet operations to verify that IPv6 interface PBR on Router A operates as configured to forward the matching TCP packets to the next hop 1::2 (Router B), as follows:

# Verify that you can telnet to Router B from Host A successfully. (Details not shown.)

# Verify that you cannot telnet to Router C from Host A. (Details not shown.)

3.        Verify that Router A forwards packets other than TCP packets through GigabitEthernet 3/1/3. For example, verify that you can ping Router C from Host A. (Details not shown.)