Pppoe-Server Throttle Per-Mac - H3C MSR810 Command Reference Manual

Examples
# Set the service name to pppoes for the PPPoE server on GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] pppoe-server tag service-name pppoes

pppoe-server throttle per-mac

Use pppoe-server throttle per-mac to set the PPPoE access limit on an interface.
Use undo pppoe-server throttle per-mac to restore the default.
Syntax
pppoe-server throttle per-mac session-requests session-request-period blocking-period
undo pppoe-server throttle per-mac
Default
The PPPoE access rate is not limited on an interface.
Views
Layer 3 Ethernet interface/subinterface view
Layer 3 virtual Ethernet interface/subinterface view
VLAN interface view
Layer 3 aggregate interface/subinterface view
VE-L3VPN interface/subinterface view
EFM interface/subinterface view
Predefined user roles
network-admin
Parameters
session-requests: Specifies the maximum number of PPPoE session requests from a user within the
monitoring time. The value range is 1 to 100000.
session-request-period: Specifies the monitoring time in the range of 1 to 3600 seconds.
blocking-period: Specifies the blocking time in the range of 1 to 3600 seconds.
Usage guidelines
This command limits the rate at which a us er (identified by MAC address) can create PPPoE
sessions on an interface. If the number of PPPoE requests within the monitoring time exceeds the
configured threshold, the device discards the excessive requests, and outputs log messages. If the
blocking time is set to 0, the device does not block any requests, and it only outputs log messages.
The device uses a monitoring table and a blocking table to control PPP access rates.
• Monitoring table—Stores a maximum of 8000 monitoring entries. Each entry records the
number of PPPoE sessions created by a user within the monitoring time. When the monitoring
entries reach the maximum, the system stops monitoring and blocking session requests from
new users. The aging time of monitoring entries is determined by the session-request-period
argument. When the timer expires, the system starts a new round of monitoring for the user.
• Blocking table—Stores a maximum of 8000 blocking entries. The system creates a blocking
entry if the access rate of a user reaches the threshold, and blocks requests from that user.
When the blocking entries reach the maximum, the system stops blocking session requests
from new users and it only outputs log messages. The aging time of the blocking entries is
88