08-Layer 3—IP Routing Configuration Guide

HomeSupportConfigure & DeployConfiguration GuidesH3C MSR810[2600][3600] Routers Configuration Guides(V7)-R0809-6W40008-Layer 3—IP Routing Configuration Guide
12-IPv6 policy-based routing configuration
Title Size Download
12-IPv6 policy-based routing configuration 168.39 KB

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 or that have specific lengths. The parameters include the next hop, output interface, default next hop, and default 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 forwarding fails, the device uses the default next hop or default output interface defined in PBR to forward packets.

4.     If the 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

On a node, you can specify multiple if-match clauses, but only one if-match clause for each type. A packet that matches all the if-match clauses of a node matches the node.

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 IPv6 PBR-based forwarding succeeds, IPv6 PBR does not compare the packet with the next node.

¡     If IPv6 PBR-based forwarding fails and the apply continue clause is not configured, IPv6 PBR does not compare the packet with the next node.

¡     If IPv6 PBR-based forwarding fails and the apply continue clause is configured, IPv6 PBR compares 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, output interface, default next hop, or default 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

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 match criteria.

¡     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.

¡     Set a packet length match criterion.

if-match packet-length min-len max-len

By default, no packet length match criterion is set.

Configuring actions for an IPv6 node

About this task

The apply clauses allow you to specify actions to take on matching packets on a node.

The following apply clauses determine the packet forwarding paths in a descending order:

·     apply access-vpn

·     apply next-hop

·     apply output-interface

·     apply default-next-hop

·     apply default-output-interface

IPv6 PBR supports the apply clauses in Table 1.

Table 1 Apply clauses supported in IPv6 PBR

Clause

Meaning

Remarks

apply precedence

Sets an IP precedence.

This clause is always executed.

apply loadshare { next-hop | output-interface | default-next-hop | default-output-interface }

Enables load sharing among multiple next hops, output interfaces, default next hops, or default output interfaces.

Multiple next hop, output interface, default next hop, or default output interface options operate in either primary/backup or load sharing mode.

·     Primary/backup mode—One option is selected from all options in configuration order for packet forwarding, with all remaining options as backups. For example, if multiple output interfaces are configured, the first configured output interface is selected. When the selected output interface fails, the next available output interface takes over.

·     Load sharing mode—Matching traffic is distributed across the available options, as follows:

¡     Multiple output interface, default next hop, or default output interface options—Load share traffic in round robin manner, starting from the first configured option. They perform per-packet load sharing for traffic that does not match any fast forwarding entry, and perform per-flow load sharing for traffic that matches a fast forwarding entry.

¡     Multiple next hops—Load share traffic in proportion to their weight. By default, all next hops have the same weight and traffic is evenly distributed among them.

By default, the primary/backup mode applies.

For the load sharing mode to take effect, make sure multiple next hops, output interfaces, default next hops, or default output interfaces are set in the policy.

apply access-vpn

Specifies the forwarding tables that can be used for the matching packets.

Use this clause 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 a packet matches the forwarding table for a specified VPN instance, it is forwarded in the VPN.

apply remark-vpn

Enables VPN remark action.

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.

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 and apply default-output-interface

Sets default next hops and sets default output interfaces.

If both clauses are configured, only the apply default-next-hop clause is executed.

The clauses take effect only in the following cases:

·     No next hops or output interfaces are set or the next hops and output interfaces are invalid.

·     The IPv6 packet does not match any route in the routing table.

apply continue

Compares packets with the next node upon failure on the current node.

The apply continue clause applies when either of the the following conditions exist:

·     None of the following clauses is configured for packet forwarding:

¡     apply access-vpn vpn-instance

¡     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.

Restrictions and guidelines for action configuration

If you specify a next hop or default 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 precedence

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 to direct packet forwarding

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.

¡     Specify the forwarding tables that can be used for the matching packets.

apply access-vpn { public | vpn-instance vpn-instance-name&<1-n> }

By default, the device forwards matching packets by using the forwarding table for the network from which the packets are received.

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.

¡     Enable VPN remark action to mark the matching packets as belonging to the VPN instance to which they are forwarded based on the apply access-vpn vpn-instance command.

apply remark-vpn

By default, VPN remark action is not configured.

¡     Set next hops for permitted IPv6 packets.

apply next-hop [ vpn-instance vpn-instance-name | inbound-vpn ] { ipv6-address [ direct ] [ track track-entry-number ] [ weight weight-value ] } &<1-n>

By default, no next hops are specified.

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

If multiple next hops on the same subnet are specified for backup, the device first uses the subnet route for the next hops to forward packets when the primary next hop fails. If the subnet route is not available, the device selects a backup next hop.

¡     Enable load sharing among multiple next hops.

apply loadshare next-hop

By default, the next hops operate in primary/backup mode.

¡     Set output interfaces.

apply output-interface { interface-type interface-number [ track track-entry-number ] }&<1-n>

By default, no output interfaces are specified.

You can specify multiple output interfaces for backup or load sharing in one command line or by executing this command multiple times. You can specify a maximum of four output interfaces for a node.

¡     Enable load sharing among multiple output interfaces.

apply loadshare output-interface

By default, the output interfaces operate in primary/backup mode.

¡     Set default next hops.

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

By default, no default next hops are specified.

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

¡     Enable load sharing among multiple default next hops.

apply loadshare default-next-hop

By default, the default next hops operate in primary/backup mode.

¡     Set default output interfaces.

apply default-output-interface { interface-type interface-number [ track track-entry-number ] }&<1-n>

By default, no default output interfaces are specified.

You can specify multiple default output interfaces for backup or load sharing in one command line or by executing this command multiple times. You can specify a maximum of n default output interfaces for a node.

¡     Enable load sharing among multiple default output interfaces.

apply loadshare default-output-interface

By default, the default output interfaces operate in primary/backup mode.

Comparing packets with the next node upon match failure on the current 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.     Compare packets with the next node upon match failure on the current node.

apply continue

By default, IPv6 PBR does not compare packets with the next node upon match failure on the current node.

This command takes effect only when the match mode of the node is permit.

Specifying a policy for IPv6 PBR

Specifying an IPv6 policy for IPv6 local PBR

About this task

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 this task

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

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

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 interface PBR configuration and statistics.

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 ]

Display IPv6 local PBR configuration and statistics.

In standalone mode:

display ipv6 policy-based-route local

In IRF mode:

display ipv6 policy-based-route local [ slot slot-number ]

Display IPv6 PBR configuration.

display ipv6 policy-based-route setup

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 1/0/1 and GigabitEthernet 1/0/2.

<RouterA> system-view

[RouterA] interface gigabitethernet 1/0/1

[RouterA-GigabitEthernet1/0/1] ipv6 address 1::1 64

[RouterA-GigabitEthernet1/0/1] quit

[RouterA] interface gigabitethernet 1/0/2

[RouterA-GigabitEthernet1/0/2] ipv6 address 2::1 64

[RouterA-GigabitEthernet1/0/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 1/0/1.

<RouterB> system-view

[RouterB] interface gigabitethernet 1/0/1

[RouterB-GigabitEthernet1/0/1] ipv6 address 1::2 64

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

<RouterC> system-view

[RouterC] interface gigabitethernet 1/0/2

[RouterC-GigabitEthernet1/0/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 1/0/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 1/0/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 1/0/2

[RouterA-GigabitEthernet1/0/2] ipv6 address 1::1 64

[RouterA-GigabitEthernet1/0/2] ripng 1 enable

[RouterA-GigabitEthernet1/0/2] quit

[RouterA] interface gigabitethernet 1/0/3

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

[RouterA-GigabitEthernet1/0/3] ripng 1 enable

[RouterA-GigabitEthernet1/0/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 1/0/1.

[RouterA] interface gigabitethernet 1/0/1

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

[RouterA-GigabitEthernet1/0/1] undo ipv6 nd ra halt

[RouterA-GigabitEthernet1/0/1] ripng 1 enable

[RouterA-GigabitEthernet1/0/1] ipv6 policy-based-route aaa

[RouterA-GigabitEthernet1/0/1] quit

2.     Configure RIPng on Router B.

<RouterB> system-view

[RouterB] ripng 1

[RouterB-ripng-1] quit

[RouterB] interface gigabitethernet 1/0/2

[RouterB-GigabitEthernet1/0/2] ipv6 address 1::2 64

[RouterB-GigabitEthernet1/0/2] ripng 1 enable

[RouterB-GigabitEthernet1/0/2] quit

3.     Configure RIPng on Router C.

<RouterC> system-view

[RouterC] ripng 1

[RouterC-ripng-1] quit

[RouterC] interface gigabitethernet 1/0/3

[RouterC-GigabitEthernet1/0/3] ipv6 address 2::2 64

[RouterC-GigabitEthernet1/0/3] ripng 1 enable

[RouterC-GigabitEthernet1/0/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 1/0/3. For example, verify that you can ping Router C from Host A. (Details not shown.)

Example: Configuring packet length-based IPv6 interface PBR

Network configuration

As shown in Figure 3, configure IPv6 interface PBR to guide the forwarding of packets received on GigabitEthernet 1/0/1 of Router A as follows:

·     Set the next hop of packets with a length of 64 to 100 bytes to 150::2/64.

·     Set the next hop of packets with a length of 101 to 1000 bytes to 151::2/64.

Figure 3 Network diagram

Procedure

1.     Configure Router A:

# Configure RIPng.

<RouterA> system-view

[RouterA] ripng 1

[RouterA-ripng-1] quit

[RouterA] interface gigabitethernet 1/0/2

[RouterA-GigabitEthernet1/0/2] ipv6 address 150::1 64

[RouterA-GigabitEthernet1/0/2] ripng 1 enable

[RouterA-GigabitEthernet1/0/2] quit

[RouterA] interface gigabitethernet 1/0/3

[RouterA-GigabitEthernet1/0/3] ipv6 address 151::1 64

[RouterA-GigabitEthernet1/0/3] ripng 1 enable

[RouterA-GigabitEthernet1/0/3] quit

# Configure Node 10 for policy lab1 to forward packets with a length of 64 to 100 bytes to the next hop 150::2/64.

[RouterA] ipv6 policy-based-route lab1 permit node 10

[RouterA-pbr6-lab1-10] if-match packet-length 64 100

[RouterA-pbr6-lab1-10] apply next-hop 150::2

[RouterA-pbr6-lab1-10] quit

# Configure Node 20 for policy lab1 to forward packets with a length of 101 to 1000 bytes to the next hop 151::2/64.

[RouterA] ipv6 policy-based-route lab1 permit node 20

[RouterA-pbr6-lab1-20] if-match packet-length 101 1000

[RouterA-pbr6-lab1-20] apply next-hop 151::2

[RouterA-pbr6-lab1-20] quit

# Configure IPv6 interface PBR by applying policy lab1 to GigabitEthernet 1/0/1.

[RouterA] interface gigabitethernet 1/0/1

[RouterA-GigabitEthernet1/0/1] ipv6 address 192::1 64

[RouterA-GigabitEthernet1/0/1] undo ipv6 nd ra halt

[RouterA-GigabitEthernet1/0/1] ripng 1 enable

[RouterA-GigabitEthernet1/0/1] ipv6 policy-based-route lab1

[RouterA-GigabitEthernet1/0/1] return

2.     Configure RIPng on Router B.

<RouterB> system-view

[RouterB] ripng 1

[RouterB-ripng-1] quit

[RouterB] interface gigabitethernet 1/0/2

[RouterB-GigabitEthernet1/0/2] ipv6 address 150::2 64

[RouterB-GigabitEthernet1/0/2] ripng 1 enable

[RouterB-GigabitEthernet1/0/2] quit

[RouterB] interface gigabitethernet 1/0/3

[RouterB-GigabitEthernet1/0/3] ipv6 address 151::2 64

[RouterB-GigabitEthernet1/0/3] ripng 1 enable

[RouterB-GigabitEthernet1/0/3] quit

[RouterB] interface loopback 0

[RouterB-LoopBack0] ipv6 address 10::1 128

[RouterB-LoopBack0] ripng 1 enable

Verifying the configuration

# Execute the debugging ipv6 policy-based-route command on Router A.

<RouterA> debugging ipv6 policy-based-route

<RouterA> terminal logging level 7

<RouterA> terminal monitor

# Install IPv6 protocol suites on Host A, and configure the IPv6 address 192::3.

C:\>ipv6 install

Installing...

Succeeded.

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

# Ping Loopback 0 of Router B from Host A, and set the data length to 64 bytes.

C:\>ping –n 1 -l 64 10::1

 

Pinging 10::1 with 64 bytes of data:

 

Reply from 10::1: time=1ms

 

Ping statistics for 10::1:

    Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 1ms, Maximum = 1ms, Average = 1ms

The debugging information about IPv6 PBR displayed on Router A is as follows:

<RouterA>

*Jun  26 13:04:33:519 2012 RouterA PBR6/7/PBR Forward Info: -MDC=1; Policy:lab1, Node:

 10,match succeeded.

*Jun  26 13:04:33:519 2012 RouterA PBR6/7/PBR Forward Info: -MDC=1; apply next-hop 150

::2.

The output shows that Router A sets the next hop for the received packets to 150::2 according to IPv6 PBR. The packets are forwarded through GigabitEthernet 1/0/2.

# Ping Loopback 0 of Router B from Host A, and set the data length to 200 bytes.

C:\>ping –n 1 -l 200 10::1

 

Pinging 10::1 with 200 bytes of data:

 

Reply from 10::1: time=1ms

 

Ping statistics for 10::1:

    Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 1ms, Maximum = 1ms, Average = 1ms

The debugging information about IPv6 PBR displayed on Router A is as follows:

<RouterA>

*Jun  26 13:20:33:619 2012 RouterA PBR6/7/PBR Forward Info: -MDC=1; Policy:lab1, Node:

 20,match succeeded.

*Jun  26 13:20:33:619 2012 RouterA PBR6/7/PBR Forward Info: -MDC=1; apply next-hop 151

::2.

The output shows that Router A sets the next hop for the received packets to 151::2 according to IPv6 PBR. The packets are forwarded through GigabitEthernet 1/0/3.

 

  • Cloud & AI
  • InterConnect
  • Intelligent Computing
  • Security
  • SMB Products
  • Intelligent Terminal Products
  • Product Support Services
  • Technical Service Solutions
All Services
  • Resource Center
  • Policy
  • Online Help
All Support
  • Become a Partner
  • Partner Resources
  • Partner Business Management
All Partners
  • Profile
  • News & Events
  • Online Exhibition Center
  • Contact Us
All About Us
新华三官网