The Cisco UBR10012 has a high CPU problem during routine maintenance, and is checked for DHCPD Receive processes that are taking up too much.
Indicates that the device has received an excessive amount of DHCP packets, in order to avoid affecting normal business traffic, configure DRL (divert rate Limit) on
The UBR10012 CPU is protected.
The following official documents can be used to interpret and configure the DRL:
Http://www.cisco.com/c/en/us/td/docs/cable/cmts/config_guide/b_cisco_cmts_networkmgmt_trblshting/b_cisco_cmts_ Networkmgmt_trblshting_chapter_01010.html
In UBR10012, DRL can be used to control WAN port traffic and RF port traffic. The specific implementation script is as follows:
Wanside Flow:
Service Divert-rate-limit IP fib_rp_glean rate limit 20
Service Divert-rate-limit IP fib_rp_dest rate limit 20
Service Divert-rate-limit IP fib_rp_punt rate limit 20
Service Divert-rate-limit max-rate Wan fib_rp_dest rate limit 100
Rfside Flow: (Applies to RF Mac domain)
Interface cable5/0/0
Cable Divert-rate-limit Rate Limit 10
Interface CABLE5/0/1
Cable Divert-rate-limit Rate Limit 10
.........................
Add Trust-site: (this portion of traffic is not controlled by DRL, mainly for messages coming from DHCP server)
Service Divert-rate-limit trusted-site x.x.x.x 255.255.255.255 tos 0 Mask 0 VRF XXX
Service Divert-rate-limit trusted-site x.x.x.x 255.255.255.255 tos 0 Mask 0 VRF XXX
Service Divert-rate-limit trusted-site x.x.x.x 255.255.255.255 tos 0 Mask 0 VRF XXX
Service Divert-rate-limit trusted-site x.x.x.x 255.255.255.255 tos 0 Mask 0 VRF XXX
Specific values are modified as required.
This article is from the "Anrbin_boke" blog, make sure to keep this source http://anrbin.blog.51cto.com/12894439/1926128
Cisco UBR10012 uses DRL to protect the CPU against high CPU problems