Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document.
Note: Even the most advanced machine translation cannot match the quality of professional translators.
Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
SECE/3/RESOURCE_INSUFFIEIENT
Description
Attack source tracing, CAR, whitelist configuration, blacklist configuration, IP Source Trail, storm control, traffic-pppoe, or traffic suppression in VLANs fails due to insufficient resources.
Parameters
| Parameter Name | Parameter Meaning |
|---|---|
| STRING1 | Indicates the operation type. |
| STRING2 | Indicates the interface. |
Possible Causes
Attack source tracing, CAR, whitelist configuration, blacklist configuration, IP Source Trail, storm control, traffic-pppoe, or suppression on broadcast, unknown multicast, or unknown unicast packets in VLANs fails.
Procedure
- Run the display acl resource [ slot slot ] command to view information about ACL resources, including ACL4 and ACL6 resources.
- Run the display current-configuration command to check the current configuration on the switch.
- Check the services that occupy ACL resources based on ACL
resource information and the current configuration as follows, and
delete unnecessary services to release ACL resources.
- Check whether NAC, IPSG, MQC, and ACL-based simplified traffic policy services that occupy a large amount of ACL resources exist on the switch.
- Check the services that occupy ACL resources based on fields in the ACL resource information. For example, MQC, ACL-based simplified traffic policy, SVF, MPLS, and BFD for VPLS services occupy UDF ACL resources. If a large amount of UDF ACL resources are occupied, check these services first.
- If the fault persists, collect log information and configuration information, and then collect log information and configuration information, and then contact technical support personnel. For details, see Troubleshooting-Information Collection-Collecting Diagnostic Information.
