Why does the CPCAR rate limit configuration not take effect


The CPU committed access rate (CPCAR) is configured in the attack defense policy view. The CPCAR takes effect only when the attack defense policy is applied on the main control board or interface board on the local area network (LAN) side.

Other related questions:
Rate limiting based on IP addresses does not take effect on an AR
Verify that the interface to which rate limiting is applied is the router's interface connecting to intranet users or the interface does not have NAT configured. If the interface has NAT configured, ensure that it can match source and destination IP addresses correctly. For the intranet, inbound and outbound in the command indicate the source and destination IP addresses respectively.

Why doesn't the configured CPCAR value take effect
The CPCAR value is configured in the anti-attack policy view. When this policy is applied to the SRU or LAN interface card, the value takes effect.

Why the MAC-VLAN does not take effect
MAC address-based VLANs take effect only to untagged packets. If an MAC address-based VLAN does not take effect, check whether the incoming packets contain VLAN tags.

Why does IPSG fail to take effect
The possible causes are as follows: --Invalid binding entries A static binding table is created using the user-bind static command. A dynamic binding table is generated only after the DHCP snooping function is enabled. --IPSG not enabled on the specified interface or VLAN After a binding table is generated, the IPSG function must be enabled in the interface or VLAN view using the ip source check user-bind enable command. IPSG takes effect only on the interface or VLAN where it is enabled, and IPSG check is not performed on the interfaces or VALNs without IPSG enabled. Therefore, if IPSG does not take effect on an interface or in a VLAN, the IPSG function may not be enabled on this interface or in this VLAN. --Insufficient hardware ACL resources The hardware ACL resources are shared by IPSG and other services. If the ACL resources are insufficient, IPSG cannot take effect. For example, you can run the display dhcp static user-bind all verbose command to view the IPSG status corresponding to static binding entries. If the value of IPSG Status is ineffective, IPSG of this entry does not take effect. The possible reason is that hardware ACL resources are insufficient. --Conflict between IPSG and QoS traffic policy This situation may only occur in V1R6C05. When a QoS traffic policy conflicts with IPSG, the traffic behavior in the QoS traffic policy takes effect.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top