The ipv6 nd miss anti-attack rate-limit source-ip command configures a rate limit for receiving ND Miss messages based on a specified source IPv6 address, that is, the number of ND Miss messages that can be processed per second based on a specified source IPv6 address.
The undo ipv6 nd miss anti-attack rate-limit source-ip command restores the default configuration.
By default, no rate limit for receiving ND Miss messages based on a specified source IPv6 address is configured.
Parameter | Description | Value |
---|---|---|
maximum max-value |
Specifies a rate limit for receiving ND Miss messages based on a specified source IPv6 address. |
The value is an integer ranging from 0 to 5000, in messages per second. |
miss |
Sets a rate limit for receiving ND Miss messages. |
- |
source-ip ipv6-address |
Specifies a source IPv6 address. |
The value is a 32-digit hexadecimal number, in the format of X:X:X:X:X:X:X:X. |
Usage Scenario
If a device is attacked, it receives a large number of ND Miss messages within a short period. As a result, the device consumes many CPU resources to learn and respond to ND entries, affecting the processing of other services. To resolve this issue, configure a rate limit for receiving ND Miss messages based on a specified source IPv6 address. After the configuration is complete, the device counts the number of ND Miss messages received per period based on the specified source IPv6 address. If the number exceeds the configured limit, the device does not process excess ND Miss messages.
Configuration Impact
After a rate limit for receiving ND Miss messages based on a specified source IPv6 address is configured, the device counts the number of ND Miss messages received per period based on the specified source IPv6 address. If the number of ND Miss messages exceeds the configured limit, the device does not process excess ND Miss messages. As a result, the device may fail to process valid ND Miss messages, causing user service interruptions.
Precautions
If a low rate limit is configured and the login through Telnet fails because the device receives a large number of attack packets, you can log in to the device through the console port to increase the rate limit.