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

Reminder

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

upgrade

NE20E-S2 V800R010C10SPC500 Configuration Guide - IP Services 01

This is NE20E-S2 V800R010C10SPC500 Configuration Guide - IP Services
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 a User ACL

Configuring a User ACL

A User ACL defines rules to filter packets.

Usage Scenario

To process different types of traffic, users can configure a User ACL to perform traffic policing, traffic shaping, or traffic classification on traffic that matches the ACL rules.

Configuration Procedures

Figure 3-9 Flowchart for configuring a user ACL

(Optional) Creating a Validity Period for an ACL Rule

You can create a validity period for an ACL rule to control network traffic in a specified period.

Context

To control certain types of traffic in a specified period, you can configure the validity period of an ACL rule to determine the time traffic passes through. For example, to ensure reliable transmission of video traffic at prime time at night, limit the volume of traffic for common online users.

After this configuration task is performed, a time range is created. Then you can specify the time range as the validity period when creating an ACL rule.

The validity period of an ACL rule can be either of the following types:

  • Relative time range: The validity period is a periodic period, for example, each Monday.

  • Absolute time range: The validity period is fixed.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run time-range time-name { start-time to end-time days &<1-7> | from time1 date1 [ to time2 date2 ] }

    A validity period is created.

    • You can configure up to 256 time ranges.
    • Up to 32 relative time ranges (periodic time ranges) and 12 absolute time ranges can share one time range name.

  3. Run commit

    The configuration is committed.

Creating a User ACL

You can create a user ACL and configure parameters for the ACL.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run acl { name ucl-acl-name [ ucl | [ ucl ] number ucl-acl-number ] | [ number ] ucl-acl-number } [ match-order { auto | config } ]

    A user ACL is created.

    The user ACL number ranges from 6000 to 9999.

  3. (Optional) Run step step

    An ACL step is set.

    You can use an ACL step to maintain ACL rules and add new ACL rules conveniently.
    NOTE:
    Assume that a user has created four rules numbered from 1 to 4 in an ACL. The user can reconfigure the ACL step, for example, to 2 by running the step 2 command in the ACL view. The original rule numbers 1, 2, 3, and 4 are renumbered as 2, 4, 6, and 8, respectively. After that, the user can run the rule 3 command to add a rule numbered 3 between the renumbered rules 2 and 4.

  4. (Optional) Run description text

    The ACL description is configured.

    The description command configures a description for an ACL in any of the following situations:

    • A large number of ACLs are configured, and their functions are difficult to identify.
    • An ACL is used at a long interval, and its function may be left forgotten.
    • Names of named ACLs cannot fully explain the ACLs' functions.

  5. Run commit

    The configuration is committed.

Configuring a User ACL Rule

Packets can be matched based on the source/destination IP address, source/destination service group, source/destination user group, source/destination port number, and protocol type.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run acl { name ucl-acl-name [ ucl | [ ucl ] number ucl-acl-number ] | [ number ] ucl-acl-number } [ match-order { auto | config } ]

    The user ACL view is displayed.

  3. Run any of the following commands to create an ACL rule:

    • Create a user ACL rule when protocol is UDP.

      rule [ rule-id ] [ name rule-name ] { deny | permit } { protocol | udp } [ [ dscp dscp | [ precedence precedence | tos tos ] * ] | source { ip-address { source-ip-address { source-ip-address-mask | 0 } | any } | any | [ service-group { service-group-name | any } | user-group { user-group-name | any } ] } | destination { ip-address { destination-ip-address { destination-ip-address-mask | 0 } | any } | any | [ service-group { service-group-name | any } | user-group { user-group-name | any } ] } | source-port operator port-number | destination-port operator port-number | fragment-type { fragment | non-fragment | non-subseq | fragment-subseq | fragment-spe-first } | time-range time-name | logging | vlan vlan-id | inner-vlan cvlan-id ] *

    • Create a user ACL rule when protocol is TCP.

      rule [ rule-id ] [ name rule-name ] { deny | permit } { protocol | tcp } [ [ dscp dscp | [ precedence precedence | tos tos ] * ] | source { ip-address { source-ip-address { source-ip-address-mask | 0 } | any } | any | [ service-group { service-group-name | any } | user-group { user-group-name | any } ] } | destination { ip-address { destination-ip-address { destination-ip-address-mask | 0 } | any } | any | [ service-group { service-group-name | any } | user-group { user-group-name | any } ] } | source-port operator port-number | destination-port operator port-number | syn-flag { syn-flag [ mask mask-value ] | { bit-match { established | fin | syn | rst | psh | ack | urg | ece | crw | ns } } } | fragment-type { fragment | non-fragment | non-subseq | fragment-subseq | fragment-spe-first } | time-range time-name | logging | vlan vlan-id | inner-vlan cvlan-id ] *

    • Create a user ACL rule when protocol is ICMP.

      rule [ rule-id ] [ name rule-name ] { deny | permit } { protocol | icmp } [ [ dscp dscp | [ precedence precedence | tos tos ] * ] | source { ip-address { source-ip-address { source-ip-address-mask | 0 } | any } | any | [ service-group { service-group-name | any } | user-group { user-group-name | any } ] } | destination { ip-address { destination-ip-address { destination-ip-address-mask | 0 } | any } | any | [ service-group { service-group-name | any } | user-group { user-group-name | any } ] } | icmp-type { icmp-name | icmp-type icmp-code } | fragment-type { fragment | non-fragment | non-subseq | fragment-subseq | fragment-spe-first } | time-range time-name | logging | vlan vlan-id | inner-vlan cvlan-id ] *

    • Create a user ACL rule when protocol is any protocol except TCP, UDP, and ICMP.

      rule [ rule-id ] [ name rule-name ] { deny | permit } { protocol | gre | ip | ipinip | igmp | ospf } [ [ dscp dscp | [ precedence precedence | tos tos ] * ] | source { ip-address { source-ip-address { source-ip-address-mask | 0 } | any } | any | [ service-group { service-group-name | any } | user-group { user-group-name | any } ] } | destination { ip-address { destination-ip-address { destination-ip-address-mask | 0 } | any } | any | [ service-group { service-group-name | any } | user-group { user-group-name | any } ] } | fragment-type { fragment | non-fragment | non-subseq | fragment-subseq | fragment-spe-first } | time-range time-name | logging | vlan vlan-id | inner-vlan cvlan-id ] *

    Adding new rules to an ACL will not affect the existing rules.

    When an existing rule is edited and the edited contents conflict with the original contents, the edited contents take effect.

  4. (Optional) Run rule description text

    The description for an ACL rule is configured.

    The description of an ACL rule can contain the functions of the ACL rule. Configuring a description for an ACL rule is recommended to prevent misuse of the rule in the following situations:
    • A large number of ACLs are configured, and their functions are difficult to identify.
    • An ACL is used at a long interval, and its function may be left forgotten.

  5. Run commit

    The configuration is committed.

Applying a User ACL

User ACLs can be used in QoS services.

Context

Table 3-6 describes the typical applications of User ACLs.

Table 3-6 Typical applications of User ACLs

Typical Application

Usage Scenario

Operation

QoS

To process different types of traffic, users can configure a User ACL to perform traffic policing, traffic shaping, or traffic classification on traffic that matches the ACL rules.

To find out more about the procedures for processing different types of traffic, see how to configure traffic policing, traffic shaping, and traffic behavior.

Verifying the Configuration of a User ACL

After configuring a user ACL, verify the configuration.

Prerequisites

All configurations of the user ACL are configured.

Procedure

  • Run the display acl { acl-number | name acl-name | all } command to view user ACL configurations.
  • Run the display time-range { time-name | all } command view the configuration and status within a specified time range or all time ranges.

Example

Run the display acl command view the ACL number, rule quantity, step, and rule information.

<HUAWEI> display acl 7000
UCL ACL 7000, 3 rules
ACL's step is 5
 rule 1 permit icmp 
 rule 5 permit ip source ip-address 1.1.1.1 0 destination ip-address 2.2.2.2 0 
 rule 10 permit tcp source user-group 1 

Run the display time-range command to view the configuration and status in the current time range.

<HUAWEI> display time-range all
Current time is 2015-03-15 10:01:45 Wednesday

Time-range : time1 ( Inactive )
 10:00 to 12:00 daily
Time-range : time2 ( Inactive )
 from 13:00 2006/4/1 to 23:59 2099/12/31  
Time-range : active1 ( Active )
 14:00 to 00:00 daily  
Translation
Download
Updated: 2019-01-02

Document ID: EDOC1100055376

Views: 15214

Downloads: 33

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