Contents

Basic IP forwarding commands· 1

display fib· 1

fib consistency-check enable· 3

forwarding arp-packet destination· 3

forwarding hop-limit-exceeded destination· 4

forwarding nd-packet destination· 5

forwarding ttl-exceeded-packet destination· 6

forwarding tunnel-ttl-unvaried· 7

ip forwarding-table save· 7

Load sharing commands· 9

bandwidth-based-sharing· 9

display ip load-sharing mode· 9

display ip load-sharing path· 11

ip load-sharing local-first enable· 12

ip load-sharing mode· 13

ip load-sharing symmetric enable· 14

hardware-resource hash· 15

 

Basic IP forwarding commands

display fib

Use display fib to display FIB entries.

Syntax

display fib [ vpn-instance vpn-instance-name ] [ ip-address [ mask | mask-length ] ]

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. To display the FIB entries for the public network, do not specify any VPN instance.

ip-address: Displays the FIB entry that matches the specified destination IP address.

mask: Specifies the mask for the IP address.

mask-length: Specifies the mask length for the IP address. The value range is 0 to 32.

Usage guidelines

If you specify an IP address without a mask or mask length, this command displays the longest matching FIB entry.

If you specify an IP address and a mask or mask length, this command displays the exactly matching FIB entry.

Examples

# Display all FIB entries of the public network.

<Sysname> display fib

 

Destination count: 5 FIB entry count: 5

 

Flag:

  U:Usable   G:Gateway   H:Host   B:Blackhole   D:Dynamic   S:Static

  R:Relay     F:FRR

 

Destination/Mask   Nexthop         Flag     OutInterface/Token       Label

0.0.0.0/32         127.0.0.1       UH       InLoop0                  Null

1.1.1.0/24         192.168.126.1   USGF     M-GE0/0/0                Null

127.0.0.0/8        127.0.0.1       U        InLoop0                  Null

127.0.0.0/32       127.0.0.1       UH       InLoop0                  Null

127.0.0.1/32       127.0.0.1       UH       InLoop0                  Null

# Display the FIB entries for VPN vpn1.

<Sysname> display fib vpn-instance vpn1

Destination count: 6 FIB entry count: 6

 

Flag:

  U:Usable   G:Gateway   H:Host   B:Blackhole   D:Dynamic   S:Static

  R:Relay     F:FRR

 

Destination/Mask   Nexthop         Flag     OutInterface/Token      Label

0.0.0.0/32         127.0.0.1       UH       InLoop0                  Null

20.20.20.0/24      20.20.20.25     U        M-GE0/0/0                Null

20.20.20.0/32      20.20.20.25     UBH      M-GE0/0/0                Null

20.20.20.25/32     127.0.0.1       UH       InLoop0                  Null

20.20.20.25/32     20.20.20.25     H        M-GE0/0/0                Null

20.20.20.255/32    20.20.20.25     UBH      M-GE0/0/0                Null

# Display the FIB entries matching the destination IP address 10.2.1.1.

<Sysname> display fib 10.2.1.1

 

Destination count: 1 FIB entry count: 1

 

Flag:

  U:Usable   G:Gateway   H:Host   B:Blackhole   D:Dynamic   S:Static

  R:Relay     F:FRR

 

Destination/Mask   Nexthop         Flag     OutInterface/Token       Label

10.2.1.1/32        127.0.0.1       UH       InLoop0                  Null

Table 1 Command output

Field	Description
Destination count	Total number of destination addresses.
FIB entry count	Total number of FIB entries.
Destination/Mask	Destination address and the mask length.
Nexthop	Next hop address.
Flag	Flags of routes: ·     U—Usable route. ·     G—Gateway route. ·     H—Host route. ·     B—Blackhole route. ·     D—Dynamic route. ·     S—Static route. ·     R—Relay route. ·     F—Fast reroute.
OutInterface/Token	Output interface/LSP index number.
Label	Inner label.

 

fib consistency-check enable

Use fib consistency-check enable to enable IPv4 FIB entry consistency check.

Use undo fib consistency-check enable to disable IPv4 FIB entry consistency check.

Syntax

fib consistency-check enable

undo fib consistency-check enable

Default

IPv4 FIB entry consistency check is disabled.

Views

System view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

Packet drops or incorrect forwarding might occur when the IPv4 FIB entries in hardware are inconsitent with FIB entries configured in software. To prevent these issues, enable IPv4 FIB entry consistency check.

This feature compares all IPv4 FIB entries in software with the IPv4 FIB entries in hardware regularly. If the device detects an inconsistency, the device performs the following tasks:

·     Generates a log.

·     Updates the IPv4 FIB entry in hardware with the IPv4 FIB entry in software.

Examples

# Enable IPv4 FIB entry consistency check.

<Sysname> system-view

[Sysname] fib consistency-check enable

forwarding arp-packet destination

Use forwarding arp-packet destination to enable forwarding ARP packets with a specific destination address to the specified VXLAN tunnel.

Use undo forwarding arp-packet destination to restore the default.

Syntax

forwarding arp-packet destination [ vpn-instance vpn-instance-name ] ip-address interface tunnel number

undo forwarding arp-packet destination [ vpn-instance vpn-instance-name ] ip-address

Default

The device delivers ARP packets to the CPU.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

vpn-instance vpn-instance-name: Specifies the MPLS L3VPN instance to which the destination IP address belongs. The vpn-instance-name argument is a case-sensitive string of 1 to 31 characters. If you do not specify a VPN instance, the specified destination IP address belongs to the public network and all VPN instances.

ip-address: Specifies the destination IP address.

interface tunnel number: Specifies the tunnel interface. The number argument represents the interface number. The specified tunnel interface must already exist. The actual number of tunnel interfaces that can be created depends on the total number of supported interfaces and memory usage.

Usage guidelines

In ARP flooding suppression, if a device receives an ARP packet that uses the device's MAC as the destination MAC but another device's IP as the destination IP, the device discards the packet. You can perform this task for the device to forward such packets to a specific VXLAN tunnel.

Make sure the specified tunnel interface is a manual created VXLAN over IPv4 tunnel.

Examples

# Enable forwarding ARP packets with TTL of 1 to tunnel interface 1 if the packets are destined to IP address 192.168.1.2.

<Sysname> system-view

[Sysname] forwarding arp-packet destination vpn-instance vpn1 192.168.1.2 interface tunnel 1

forwarding hop-limit-exceeded destination

Use forwarding hop-limit-exceeded destination to enable forwarding IPv6 packets with HopLimit of 1 if the packets are destined to the specified IPv6 address. These IPv6 packets are not processed by the CPU.

Use undo forwarding hop-limit-exceeded destination to restore the default.

Syntax

forwarding hop-limit-exceeded destination [ vpn-instance vpn-instance-name ] ipv6-address

undo forwarding hop-limit-exceeded destination [ vpn-instance vpn-instance-name ] ipv6-address

Default

The device delivers IPv6 packets to the CPU.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

vpn-instance vpn-instance-name: Specifies the MPLS L3VPN instance to which the destination IPv6 address belongs. The vpn-instance-name argument is a case-sensitive string of 1 to 31 characters. If the specified destination IPv6 address belongs to the public network and all VPNs, do not specify this option.

ipv6-address: Specifies the destination IPv6 address.

Usage guidelines

This feature is typically configured on a device that acts as the gateway in the following scenario:

·     The device directly connects to an internal server.

·     The internal devices wishes to receive IPv6 packets destined to a specific IPv6 address, but they do not care about the HopLimit value in the packets.

Upon receiving an IPv6 packet destined to the specified destination IPv6 address, the device forwards the packet with HopLimit of 1 instead of sending it to the CPU.

Examples

# Enable forwarding IPv6 packets with HopLimit of 1 if the packets are destined to IPv6 address 1::1.

<Sysname> system-view

[Sysname] forwarding hop-limit-exceeded destination 1::1

forwarding nd-packet destination

Use forwarding nd-packet destination to enable forwarding ND packets with a specific destination address to the specified VXLAN tunnel.

Use undo forwarding nd-packet destination to restore the default.

Syntax

forwarding nd-packet destination [ vpn-instance vpn-instance-name ] ipv6-address interface tunnel number

undo forwarding nd-packet destination [ vpn-instance vpn-instance-name ] ipv6-address

Default

The device delivers ND packets to the CPU.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

vpn-instance vpn-instance-name: Specifies the MPLS L3VPN instance to which the destination IPv6 address belongs. The vpn-instance-name argument is a case-sensitive string of 1 to 31 characters. If the specified destination IPv6 address belongs to the public network and all VPNs, do not specify this option.

ip-address: Specifies the destination IPv6 address.

interface tunnel number: Specifies the tunnel interface. The number argument represents the interface number. The specified tunnel interface must already exist. The actual number of tunnel interfaces that can be created depends on the total number of supported interfaces and memory usage.

Usage guidelines

In ND flooding suppression, if a device receives an ND packet that uses the device's MAC as the destination MAC but another device's IP as the destination IP, the device discards the packet. You can perform this task for the device to forward such packets to a specific VXLAN tunnel.

Make sure the specified tunnel interface is a manual created VXLAN over IPv6 tunnel.

Examples

# Enable forwarding ND packets with TTL of 1 to tunnel interface 1 if the packets are destined to IPv6 address 4001::1.

<Sysname> system-view

[Sysname] forwarding nd-packet destination vpn-instance vpn1 4001::1 interface tunnel 1

forwarding ttl-exceeded-packet destination

Use forwarding ttl-exceeded-packet destination to enable forwarding IP packets with TTL of 1 if the packets are destined to the specified IP address. These IP packets are not processed by the CPU.

Use undo forwarding ttl-exceeded-packet destination to restore the default.

Syntax

forwarding ttl-exceeded-packet destination [ vpn-instance vpn-instance-name ] ip-address

undo forwarding ttl-exceeded-packet destination [ vpn-instance vpn-instance-name ] ip-address

Default

The device delivers IP packets to the CPU.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

vpn-instance vpn-instance-name: Specifies the MPLS L3VPN instance to which the destination IP address belongs. The vpn-instance-name argument is a case-sensitive string of 1 to 31 characters. If the destination IP address belongs to the public network and all VPNs, do not specify this option.

ip-address: Specifies the destination IP address.

Usage guidelines

This feature is typically configured on a device that acts as the gateway in the following scenario:

·     The device directly connects to an internal server.

·     The internal server wishes to receive IP packets destined to a specific IP address, but it does not care about the TTL value in the packets.

Upon receiving an IP packet destined to the specified destination IP address, the device forwards the packet with TTL of 1 instead of sending it to the CPU.

Examples

# Enable forwarding IP packets with TTL of 1 if the packets are destined to IP address 10.1.1.2.

<Sysname> system-view

[Sysname] forwarding ttl-exceeded-packet destination 10.1.1.2

forwarding tunnel-ttl-unvaried

Use forwarding tunnel-ttl-unvaried to keep the TTL or hop limit unchanged in the packets passing through tunnel interfaces or VSI interfaces.

Use undo forwarding tunnel-ttl-unvaried to restore the default.

Syntax

forwarding tunnel-ttl-unvaried

undo forwarding tunnel-ttl-unvaried

Default

The TTL or hop limit is decremented by one when a packet passes through a tunnel interface or VSI interface.

View

System view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

On a private network using VXLANs or tunnels, the gateway decrements the value in the TTL or Hop Limit field by 1 in packets passing through VSI interfaces or tunnel interfaces by default. If you do not want the gateway to change the TTL or hop limit in these packets, execute this command on the gateway.

Examples

# Configure the device not to decrement the TTL or hop limit in the packets passing through tunnel interfaces and VSI interfaces.

<Sysname> system-view

[Sysname] forwarding tunnel-ttl-unvaried

ip forwarding-table save

Use ip forwarding-table save to save the IP forwarding entries to a file.

Syntax

ip forwarding-table save filename filename

Views

Any view

Predefined user roles

network-admin

mdc-admin

Parameters

filename filename: Specifies the name of a file, a string of 1 to 255 characters. For information about the filename argument, see file system management in Fundamentals Configuration Guide.

Usage guidelines

The command automatically creates the file if you specify a nonexistent file. If the file already exists, this command overwrites the file content.

To automatically save the IP forwarding entries periodically, configure a schedule for the device to automatically run the ip forwarding-table save command. For information about scheduling a task, see Fundamentals Configuration Guide.

Examples

# Save the IP forwarding entries to the fib.txt file.

<Sysname> ip forwarding-table save filename fib.txt

Load sharing commands

bandwidth-based-sharing

Use bandwidth-based-sharing to enable IPv4 load sharing based on bandwidth.

Use undo bandwidth-based-sharing to disable IPv4 load sharing based on bandwidth.

Syntax

bandwidth-based-sharing

undo bandwidth-based-sharing

Default

The IPv4 load sharing based on bandwidth is disabled.

Views

System view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

This feature load shares flow traffic among multiple output interfaces based on their load percentages. The device calculates the load percentage for each output interface in terms of their expected bandwidths.

Devices that run load sharing protocols, such as Locator/ID Separation Protocol (LISP), implement load sharing based on the ratios defined by these protocols.

This feature is mutually exclusive with the enhanced ECMP mode configured by the ecmp mode enhanced command.

After you enable this feature, the expected bandwidth set by using the bandwidth command on an interface cannot exceed the actual physical bandwidth of the interface.

After you enable this feature, you must set the expected bandwidth for VLAN interfaces to ensure correct bandwidth allocation.

Examples

# Enable IPv4 load sharing based on bandwidth.

<Sysname> system-view

[Sysname] bandwidth-based-sharing

display ip load-sharing mode

Use display ip load-sharing mode to display the load sharing mode in use.

Syntax

In standalone mode:

display ip load-sharing mode slot slot-number

In IRF mode:

display ip load-sharing mode chassis chassis-number slot slot-number

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays the load sharing mode for all cards. (In standalone mode.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command displays the load sharing mode for all cards. (In IRF mode.)

Examples

# Display the load sharing mode in use.

<Sysname> display ip load-sharing mode slot 1

Load-sharing mode: per-flow

Load-sharing options: dest-ip | src-ip | ip-pro | dest-port | src-port | ingress-port

Load-sharing algorithm: 1

IP tunnel load-sharing mode: outer

Table 2 Command output

Field	Description
Load-sharing mode	The load sharing mode in use: ·     per-packet—Per-packet load sharing. ·     per-flow—Per-flow load sharing.
Load-sharing options	Options configured for load sharing: ·     dest-ip—Identifies flows by packet's destination IP address. ·     src-ip—Identifies flows by packet's source IP address. ·     ip-pro—Identifies flows by packet's IP protocol. ·     dest-port—Identifies flows by packet's destination port number. ·     src-port—Identifies flows by packet's source port number. ·     ingress-port—Identifies flows by packet's ingress port.
Load-sharing algorithm	Algorithm used by load sharing.
IP tunnel load-sharing mode	Load sharing for IP tunnel packets: ·     all—Identifies flows by inner and outer IP header information. ·     inner—Identifies flows by inner IP header information. ·     outer—Identifies flows by outer IP header information.

 

Related commands

ip load-sharing mode

display ip load-sharing path

Use display ip load-sharing path to display the load sharing path selected for a flow.

Syntax

display ip load-sharing path ingress-port interface-type interface-number packet-format { ipv4oe dest-ip ip-address [ src-ip ip-address ] | ipv6oe dest-ipv6 ipv6-address [ src-ipv6 ipv6-address ] } [ dest-port port-id | ip-pro protocol-id | src-port port-id | vpn-instance vpn-instance-name ] *

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

ingress-port interface-type interface-number: Specifies an ingress port by its type and number.

packet-format { ipv4oe dest-ip ip-address [src-ip ip-address ] | ipv6oe dest-ipv6 ipv6-address [ src-ipv6 ipv6-address ] }: Specifies the packet encapsulation format.

ipv4oe: Specifies the format of IPv4 over Ethernet.

dest-ip ip-address: Specifies the destination IPv4 address in dotted decimal notation. If you do not specify this argument, the calculation uses 0.0.0.0 for path selection.

src-ip ip-address: Specifies the source IPv4 address in dotted decimal notation. If you do not specify this argument, the calculation uses 0.0.0.0 for path selection.

ipv6oe: Specifies the format of IPv6 over Ethernet.

dest-ipv6 ipv6-address: Specifies the destination IPv6 address. If you do not specify this option, the calculation uses 0:0:0:0:0:0:0:0 for path selection.

src-ipv6 ipv6-address: Specifies the source IPv6 address. If you do not specify this option, the calculation uses 0:0:0:0:0:0:0:0 for path selection.

dest-port port-id: Specifies a destination port number in the range of 1 to 65535. If you do not specify this option, the calculation uses 0 for path selection.

ip-pro protocol-id: Specifies an IP protocol by its number in the range of 1 to 65535. If you do not specify this option, the calculation uses 0 for path selection.

source-port port-id: Specifies a source port number in the range of 1 to 65535. If you do not specify this option, the calculation uses 0 for path selection.

vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. To display the path on the public network, do not specify this option.

Usage guidelines

The option settings in this command must match both the options displayed in the display ip load-sharing mode command and the field values in load shared packets. If the option settings do not meet the requirement, the path displayed by this command might be different from the real path for load sharing.

Examples

# Display the load sharing path selected for the flow with the following attributes: ingress port FortyGigE 1/0/3, destination IP address 10.110.0.2, source IP address 10.100.0.2, IP protocol number 153, destination port number 2000, source port number 2000.

<Sysname> display ip load-sharing path ingress-port fortygige 1/0/3 packet-format ipv4oe dest-ip 10.110.0.2 src-ip 10.100.0.2 ip-pro 153 dest-port 2000 src-port 2000

 

Load-sharing algorithm: 0

Load-sharing options: dest-ip | src-ip | ip-pro | dest-port | src-port | ingress-port

Load-sharing parameters:

  Missing configured are set to 0.

  ingress-port: FortyGigE1/0/3

  packet-format: IPv4oE

  dest-ip: 10.110.0.2

  src-ip: 10.100.0.2

  ip-pro: 153

  dest-port: 2000

  src-port: 2000

Path selected: 20.0.0.2(interface FortyGigE1/0/3)

Table 3 Command output

Field	Description
Load-sharing algorithm	Load sharing algorithm ID.
Load-sharing options	Load sharing options specified by the ip load-sharing mode command.
Load-sharing parameters	Load sharing parameters that you specify for the display ip load-sharing path command.
Missing configured are set to 0.	Values of the unconfigured parameters are set to 0.
ingress-port	Ingress port of the packet.
packet-format	Packet encapsulation format.
dest-ip	Destination IP address of the packet.
src-ip	Source IP address of the packet.
ip-pro	IP protocol number.
dest-port	Destination port number.
src-port:	Source port number.
Path selected	Selected path information, including the IPv4 or IPv6 address of the next hop and the egress port.

 

Related commands

ip load-sharing mode

ip load-sharing local-first enable

Use ip load-sharing local-first enable to enable local-first load sharing.

Use undo ip load-sharing local-first enable to disable local-first load sharing.

Syntax

ip load-sharing local-first enable

undo ip load-sharing local-first enable

Default

Local-first load sharing is enabled.

Views

System view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

Local-first load sharing takes effect only on an IRF fabric.

Examples

# Enable local-first load sharing.

<Sysname> system-view

[Sysname] ip load-sharing local-first enable

ip load-sharing mode

Use ip load-sharing mode to configure the load sharing mode.

Use undo ip load-sharing mode to restore the default.

Syntax

In standalone mode:

ip load-sharing mode { per-flow [ algorithm algorithm-number [ seed seed-number ] [ shift shift-number ] | [ dest-ip | dest-port | ingress-port | ip-pro | src-ip | src-port ] * | tunnel { all | inner | outer } ] } { global | slot slot-number }

undo ip load-sharing mode { global | slot slot-number }

In IRF mode:

ip load-sharing mode { per-flow [ algorithm algorithm-number [ seed seed-number ] [ shift shift-number ] | [ dest-ip | dest-port | ingress-port | ip-pro | src-ip | src-port ] * | tunnel { all | inner | outer } ] } { chassis chassis-number slot slot-number | global }

undo ip load-sharing mode { chassis chassis-number slot slot-number | global }

Default

The device performs per-flow load sharing based on the following criteria: source IP address, destination IP address, source port number, destination port number, IP protocol number, and ingress port.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

algorithm algorithm-number: Specifies an algorithm for per-flow load sharing. The value range for the algorithm-number argument is 0 to 15. If you do not specify an algorithm, the default algorithm value is 0.

seed seed-number: Specifies the seed value for the algorithm. The value range is 0 to ffffffff and the default value is 0.

shift shift-number: Specifies the shift value for the hash algorithm result. The value range is 0 to 15 and the default value is 0.

per-flow: Implements per-flow load sharing.

dest-ip: Identifies flows by destination IP address.

dest-port: Identifies flows by destination port.

ingress-port: Identifies flows by ingress port.

ip-pro: Identifies flows by protocol number.

src-ip: Identifies flows by source IP address.

src-port: Identifies flows by source port.

tunnel { all |inner | outer }: Performs load sharing for IP tunnel packets. The all keyword identifies flows by inner and outer IP header information. The inner keyword identifies flows by inner IP header information. The outer keyword identifies flows by outer IP header information. If you do not specify this option, the device performs load sharing based on outer IP header information.

global: Configures the load sharing mode globally.

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command configures the load sharing mode for all cards. (In standalone mode.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command configures the load sharing mode for all cards. (In IRF mode.)

Usage guidelines

If you use the ip load-sharing mode and link-aggregation global load-sharing mode commands multiple times, the most recent configuration takes effect. To ensure correct packet forwarding, make sure you configure the same load-sharing mode in the ip load-sharing mode and link-aggregation global load-sharing mode commands.

Examples

# (In standalone mode.) Configure per-flow load sharing for slot 1.

<Sysname> system-view

[Sysname] ip load-sharing mode per-flow slot 1

ip load-sharing symmetric enable

Use ip load-sharing symmetric enable to enable symmetric load sharing.

Use undo ip load-sharing symmetric enable to disable symmetric load sharing.

Syntax

ip load-sharing symmetric enable

undo ip load-sharing symmetric enable

Default

Symmetric load sharing is disabled.

Views

System view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

Symmetric load sharing ensures that bidirectional traffic specific to a particular source and destination address pair flow along the same path.

Examples

# Enable symmetric load sharing.

<Sysname> system-view

[Sysname] ip load-sharing symmetric enable

hardware-resource hash

Use hardware-resource hash to specify the hash calculation mode for packet fragments received on the device.

Use undo hardware-resource hash to restore the default.

Syntax

hardware-resource hash { normal | frag-enhance }

undo hardware-resource hash

Default

After hash calculation, the device might forward the first fragment and other fragments of a packet along different paths.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

normal: Specifies the normal mode. The forwarding paths for the first fragment and other fragments of a packet might be different.

frag-enhance: Specifies the enhanced mode. The forwarding paths for the first fragment and other fragments of a packet are the same.

Usage guidelines

This command is mutually exclusive with the ip load-sharing mode or link-aggregation global load-sharing mode command.

Before using this command, make sure you have understood the potential impact:

·     TCP attack resistance will not take effect.

·     The number of applications supported by ACL will reduce.

·     All packet fragments can match ACL 3000.

Examples

# Specify the enhanced hash calculation mode for packet fragments received on the device.

<Sysname> system-view

[Sysname] hardware-resource hash frag-enhance                                       

Do you want to change the specified hardware resource working mode? [Y/N]:y