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.


Configuration Guide - Security

S1720, S2700, S5700, and S6720 V200R011C10

This document describes the configurations of Security, including ACL, local attack defense, MFF, attack defense, traffic suppression and storm control, ARP security, Port security, DHCP snooping, ND snooping, PPPoE+, IPSG, SAVI, URPF, keychain, MPAC, separating the management plane from the service plane, security risks, PKI.
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 IPv4 MPAC Policy

Configuring IPv4 MPAC Policy


Malicious attack packets will make a network busy, increase CPU usage of network devices, and form a DoS attack. To protect the CPU, configure an MPAC policy that controls the packets to be sent to the CPU.


  1. Run system-view

    The system view is displayed.

  2. Run service-security policy ipv4 security-policy-name

    An IPv4 MPAC policy is created and its view is displayed.

    By default, no IPv4 MPAC policy exists on a device.

  3. Add a rule to the IPv4 MPAC policy:

    Table 16-2  IPv4 MPAC rules




    TCP, UDP

    rule [ rule-id ] { permit | deny } protocol { tcp | tcp-protocol-number | udp | udp-protocol-number } [ [ source-port source-port-number ] | [ destination-port destination-port-number ] | [ source-ip { source-ipv4-address { source-ipv4-mask | 0 } | any } ] | [ destination-ip { destination-ipv4-address { destination-ipv4-mask | 0 } | any } ] ] *


    BGP, OSPF, RIP, Dynamic Host Configuration Protocol-C (DHCP-C), Dynamic Host Configuration Protocol-R (DHCP-R), FTP, LDP, LSP-PING, NTP, RSVP, SNMP, SSH, Telnet, TFTP, IP

    rule [ rule-id ] { permit | deny } protocol { protocol-number | ftp | ssh | snmp | telnet | tftp | bgp | ldp | rsvp | ospf | rip | ntp | lsp-ping | dhcp-c | dhcp-r | ip } [ [ source-ip { source-ipv4-address { source-ipv4-mask | 0 } | any } ] | [ destination-ip { destination-ipv4-address { destination-ipv4-mask | 0 } | any } ] ] *


    IS-IS, any protocol

    rule [ rule-id ] { deny | permit } protocol { any | isis }

    Exercise caution when using the rule [ rule-id ] deny protocol any command. If this command is executed in the system view, no protocol packets can be sent to the CPU, causing the device to be out of management.

    By default, no rule exists in an IPv4 MPAC policy.

  4. (Optional) Run step step

    The step between two MPAC rule IDs is set.

    By default, the step between two MPAC rule IDs is 5.

  5. (Optional) Run description text

    The description of the MPAC policy is configured.

    By default, an MPAC policy does not have a description.

  6. Run quit

    Return to the system view.

  7. Apply the IPv4 MPAC policy.

    • Apply the IPv4 MPAC policy globally:

      Run the service-security global-binding ipv4 security-policy-name command.

      By default, no MPAC policy is globally applied.

    • Apply the IPv4 MPAC policy to an interface:

      1. Run the interface interface-type interface-number command to display an interface view or a subinterface view.

      2. (Optional) On an Ethernet interface, run undo portswitch

        The interface is switched to Layer 3 mode.

        By default, an Ethernet interface works in Layer 2 mode.


        Only the S5720HI, S5720EI, S6720EI, and S6720S-EI support switching between Layer 2 and Layer 3 modes.

      3. Run the service-security binding ipv4 security-policy-name command to apply the IPv4 MPAC policy to the interface.

        By default, no MPAC policy is applied to an interface.

    The MPAC policies on a subinterface, interface, or configured globally are in descending order of priority. That is, when different MPAC policies are applied globally, to an interface, and to a subinterface, the MPAC policy on the subinterface takes effect preferentially, and then the MPAC policy on the interface, and then the MPAC policy applied globally.

Updated: 2019-09-23

Document ID: EDOC1000178177

Views: 232969

Downloads: 750

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