Cisco UBR10012 uses DRL to protect cpu from high cpu problems

Cisco UBR10012 has high cpu problems in the process of daily maintenance, and it is checked that the DHCPD Receive process occupies too much.

It indicates that the device has received excessive DHCP messages. In order to avoid affecting normal business traffic, configure DRL (Divert Rate Limit) pair.

The CPU of UBR10012 is protected.

For the explanation and configuration of DRL, please refer to the following official documents:

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

DRL can be used to control WAN port flow and RF port flow in UBR10012. The specific implementation script is as follows:

WANside traffic:

Service divert-rate-limit ip fib_rp_glean rate 20 limit 20

Service divert-rate-limit ip fib_rp_dest rate 20 limit 20

Service divert-rate-limit ip fib_rp_punt rate 20 limit 20

Service divert-rate-limit max-rate wan fib_rp_dest rate 500 limit 100

RFside traffic: (applied to RF mac domain)

Interface Cable5/0/0

Cable divert-rate-limit rate 10 limit 10

Interface Cable5/0/1

Cable divert-rate-limit rate 10 limit 10

.

Add trust-site: (this part of the traffic is not controlled by DRL and is mainly used 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

The specific value is modified according to the demand.