05-Layer 3-IP Routing Command Reference

HomeSupportReference GuidesCommand ReferencesH3C S6805 & S6825 & S6850 & S9850 Command References-Release 66xx-6W10305-Layer 3-IP Routing Command Reference
11-IPv6 policy-based routing commands
Title Size Download
11-IPv6 policy-based routing commands 115.72 KB

IPv6 policy-based routing commands

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 hop is 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 or load sharing in one command line or by executing this command multiple times.

·     In Release 6607, you can specify a maximum of two default next hops.

·     In Release 6616 and later, you can repeat this command to specify a maximum of 16 default next hops.

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.

If you have specified the apply service-chain clause for the IPv6 policy node, you cannot specify multiple default ECMP next hops for recursive lookup in this command.

Examples

# Set 1:1::1:1 to be a directly connected default next hop.

<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 fail-action-drop next-hop

Use apply fail-action-drop next-hop to set the action that drops matching packets when all next hops on an IPv6 policy node are invalid.

Use undo apply fail-action-drop next-hop to restore the default.

Syntax

apply fail-action-drop next-hop

undo apply fail-action-drop next-hop

Default

The drop action is not configured. The matching packets are forwarded based on the typical packet forwarding process if all next hops on the IPv6 policy node are invalid.

Views

IPv6 policy node view

Predefined user roles

network-admin

Usage guidelines

By default, the device uses the typical packet forwarding process to route matching packets when all next hops on the IPv6 policy node are unavailable. To drop all matching packets when all next hops on the IPv6 policy node are unavailable, use this command. This command is typically used in scenarios that require strict routing paths.

If no next hops are specified on the IPv6 policy node, this command drops all packets that match the node.

This command does not apply to software-forwarded packets.

Examples

# Set next hop 1::1 on IPv6 policy node 10 and configure the IPv6 policy node to drop matching packets when the next hop is invalid.

<Sysname> system-view

[Sysname] ipv6 policy-based-route policy1 permit node 10

[Sysname-pbr6-policy1-1] apply next-hop 1::1

[Sysname-pbr6-policy1-1] apply fail-action-drop next-hop

apply loadshare

Use apply loadshare to enable load sharing among multiple next hops or default next hops.

Use undo apply loadshare to restore the default.

 

 

NOTE:

This command is supported only in Release 6616 and later.

 

Syntax

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

undo apply loadshare { default-next-hop | next-hop }

Default

Multiple next hops or default next hops 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.

next-hop: Enables load sharing among multiple next hops.

Usage guidelines

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

·     Primary/backup mode—One option is selected from among all options in configuration order for packet forwarding, with all remaining options as backups. If multiple next hops are configured, the first configured next hop is selected. When the selected next hop fails, the next available next hop takes over.

·     Load sharing mode—Multiple options load share traffic. By default, traffic is evenly distributed among all next hops or default next hops.

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

Related commands

apply default-next-hop

apply next-hop

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-n>

undo apply next-hop [ [ vpn-instance vpn-instance-name ] ipv6-address&<1-n> ]

Default

No next hop is 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-n>: Indicates that the argument before it can be entered up to n times. In Release 6607, you can specify a maximum of two next hops. In Release 6616 and later, you can specify a maximum of 16 next hops.

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.

If you have specified the apply service-chain clause for the IPv6 policy node, you cannot specify multiple ECMP next hops for recursive lookup in this command.

Examples

# Set 1::1 to be a directly connected next hop.

<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 interface Null 0.

Use undo apply output-interface to remove the output interface.

 

 

NOTE:

This command is supported only in Release 6616 and later.

 

Syntax

apply output-interface null 0 [ track track-entry-number ]

undo apply output-interface null 0

Default

No output interfaces are set.

Views

IPv6 policy node view

Predefined user roles

network-admin

Parameters

null 0: Specifies Null 0 as the output interface.

track track-entry-number: Specifies a track entry by its number in the range of 1 to 1024.

Examples

# Specify Null 0 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 null 0

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 service-chain

Use apply service-chain to set service chain information.

Use undo apply service-chain to restore the default.

 

 

NOTE:

This command is supported only in Release 6616 and later.

 

Syntax

apply service-chain path-id service-path-id [ path-index service-path-index ]

undo apply service-chain

Default

No service chain information is set.

Views

IPv6 policy node view

Predefined user roles

network-admin

Parameters

path-id service-path-id: Specifies a service chain by its path ID in the range of 1 to 16777215. The path ID uniquely identifies a service chain.

path-index service-path-index: Specifies the path index of the node to which you are sending the matching packets. The value range for path indexes is 1 to 255. Specify this option if the destination node might receive packets from different nodes in the service chain. If the destination node receives packets only from the device, you do not need to specify this option.

Examples

# Set service chain path ID 1 and node index 10.

<Sysname> system-view

[Sysname] ipv6 policy-based-route aa permit node 5

[Sysname-pbr6-aa-5] apply service-chain path-id 1 path-index 10

Related commands

if-match service-chain

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

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.

 

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

Examples

# Display IPv6 PBR configuration and statistics on VLAN-interface 2.

<Sysname> display ipv6 policy-based-route interface vlan-interface 2

Policy based routing information for interface Vlan-inerface2(failed):

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

  Matches: 0, bytes: 0

  node 5 permit:

    if-match acl 3101

    apply next-hop 1000::1

  Matches: 0, bytes: 0

Total matches: 0, total bytes: 0

<Sysname> display ipv6 policy-based-route interface Vlan-inerface2

Policy based routing information for interface Vlan-inerface2:

Policy name: aaa

  node 0 deny(not support):

  Matches: 0, bytes: 0

  node 1 permit:

    if-match acl 3999

  Matches: 0, bytes: 0

  node 2 permit(no resource):

    if-match acl 2000

    apply next-hop 1000::1

  Matches: 0, bytes: 0

  node 5 permit:

    if-match acl 3101

    apply next-hop 1000::1

  Matches: 0, bytes: 0

Total matched: 0, total bytes: 0

Table 3 Command output

Field

Description

Policy based routing information for interface XXXX (failed)

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. The failed status will persist even after the policy is successfully issued. To clear the failed status, you must remove the policy from the interface and then apply it on the interface again.

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(not support)

node 2 permit(no resource)

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.

Matches: (no statistics resource)

This field is not supported in the current software version.

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.

bytes:

This field is not supported in the current software version.

Number of matching bytes on the node.

Total matches:

This field is not supported in the current software version.

Total number of successful matches on all nodes.

total bytes:

This field is not supported in the current software version.

Total number of matching bytes on all nodes.

 

Related commands

reset ipv6 policy-based-route statistics

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

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

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.

Matches:

This field is not supported in the current software version.

Number of successful matches on the node.

bytes:

This field is not supported in the current software version.

Number of matching bytes on the node.

Total matches:

This field is not supported in the current software version.

Total number of successful matches on all nodes.

total bytes:

This field is not supported in the current software version.

Total number of matching bytes on all nodes.

 

Related commands

reset ipv6 policy-based-route statistics

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            Vlan-interface 2

pr02                     Local              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.

 

Related commands

ipv6 policy-based-route (interface view)

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.

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> system-view

[Sysname] ipv6 policy-based-route aa permit node 10

[Sysname-pbr6-aa-10] if-match acl name aaa

if-match qos-local-id

Use if-match qos-local-id to set a local QoS ID match criterion.

Use undo if-match qos-local-id to restore the default.

Syntax

if-match qos-local-id local-id-value

undo if-match qos-local-id

Default

No local QoS ID match criterion is set.

Views

IPv6 policy node view

Predefined user roles

network-admin

Parameters

local-id-value: Specifies a local QoS ID in the range of 1 to 4095.

Examples

# Match packets with local QoS ID 200.

<Sysname> system-view

[Sysname] ipv6 policy-based-route aa permit node 11

[Sysname-pbr6-aa-11] if-match qos-local-id 200

if-match service-chain

Use if-match service-chain to set a service chain match criterion.

Use undo if-match service-chain to restore the default.

 

 

NOTE:

This command is supported only in Release 6616 and later.

 

Syntax

if-match service-chain path-id service-path-id [ path-index service-path-index ]

undo if-match service-chain [ path-id service-path-id ]

Default

No service chain match criteria are set.

Views

IPv6 policy node view

Predefined user roles

network-admin

Parameters

path-id service-path-id: Specifies a service chain by its path ID in the range of 1 to 16777215. The path ID uniquely identifies a service chain.

path-index service-path-index: Specifies a node in the service chain by its index to match packets sent from that node. The value range for path indexes is 1 to 255. Specify this option if the device might receive packets from different nodes in the service chain. If only one node in the service chain sends packets to the device, you do not need to specify this option.

Examples

# Set a service chain match criterion to match packets with service chain path ID 1 and node index 10.

<Sysname> system-view

[Sysname] ipv6 policy-based-route aa permit node 5

[Sysname-pbr6-aa-5] if-match service-chain path-id 1 path-index 10

Related commands

apply service-chain

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 setup

ipv6 policy-based-route (system view)

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 policy 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 VLAN-interface 2.

<Sysname> system-view

[Sysname] interface vlan-interface 2

[Sysname-Vlan-interface2] ipv6 policy-based-route aaa

Related commands

display ipv6 policy-based-route setup

ipv6 policy-based-route (system view)

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

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 local policy-based-route

ipv6 policy-based-route (interface view)

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

Related commands

display ipv6 policy-based-route interface

display ipv6 policy-based-route local

 

  • 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
新华三官网