No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


CLI-based Configuration Guide - Security

AR500, AR510, and AR530 V200R007

This document describes the configurations of Security, including AAA, DAA,NAC, BRAS Access, ACL, Firewall, Deep Security Defense, Local Attack Defense;Attack Defense, Traffic Suppression, ARP Security, Port Security, DHCP Snooping, IPSG, URPF, PKI, SSL, HTTPS, Keychain, separating the management plane from the service plane, security risks.
Rate and give feedback :
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).
Configuring Traffic Identification Rules

Configuring Traffic Identification Rules


To implement destination-based accounting, the device must be able to identify the traffic destined for different networks according to the access control list (ACL).


  1. Run:


    The system view is displayed.

  2. Run:

    acl [ number ] acl-number [ match-order { auto | config } ]

    A numbered advanced ACL is created by using an ACL number and the advanced ACL view is displayed.

    Or, run:

    acl name acl-name { advance | acl-number } [ match-order { auto | config } ]

    A named advanced ACL is created by using an ACL name and the advanced ACL view is displayed.

    acl-number specifies the number of an advanced ACL. The value ranges from 3000 to 3999.

    By default, no ACL exists on the device.

  3. Run:

    rule [ rule-id ] permit ip { source { source-ip-address { source-wildcard | src-netmask } | any } | destination { destination-ip-address { destination-wildcard | des-netmask } | any } } *

    An advanced ACL rule is created.

    By default, no ACL rule is created on the device.


    The destination address is mandatory and source address is optional. Configuring both the source and destination addresses can precisely specify the traffic on which accounting will be performed.

    If the any parameter is specified, the device does not check the source and destination addresses of packets, and considers that all packets match the ACL rule. In this situation, the traffic classification rule is invalid.

Updated: 2019-05-25

Document ID: EDOC1000097287

Views: 13480

Downloads: 40

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Previous Next