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

CloudEngine 8800, 7800, 6800, and 5800 V200R005C10

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, 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 Defense Against Bogus DHCP Server Attacks

Configuring Defense Against Bogus DHCP Server Attacks


After DHCP snooping is enabled and a trusted interface is configured, the device enables DHCP clients to obtain IP addresses from the authorized DHCP server, to prevent bogus DHCP server attacks. However, the location of the bogus DHCP server cannot be detected, which brings security risks on the network.

After DHCP server detection is enabled, the DHCP snooping-enabled device checks information about the DHCP server, such as the IP address and port number, in the DHCP Reply messages and records the information to the log. The network administrator identifies whether bogus DHCP servers exist on the network based on logs.


  1. Run system-view

    The system view is displayed.

  2. Run dhcp snooping server record

    Detection of DHCP servers is enabled.

    By default, detection of DHCP servers is disabled.

  3. Run commit

    The configuration is committed.

Updated: 2019-04-20

Document ID: EDOC1100074765

Views: 28532

Downloads: 97

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