Study guide

9.1 DHCP Snooping and Dynamic ARP Inspection

HPE Aruba Networking Certified Associate - Campus Access HPE6-A85

Track your progress as you read

Finished sections get a check mark.

1 Introduction: HPE6-A85 Exam Overview

HPE6-A85 Exam Facts and Current Blueprint

2 Chapter 1: Network Stack Fundamentals

1.1 OSI Reference Model and Encapsulation 1.2 TCP/IP Protocol Suite and IP Headers 1.3 Layer 2 Operation, ARP, and 802.1Q Tagging

3 Chapter 2: Physical Connectivity and Host Addressing

2.1 Ethernet Media and Transceiver Standards 2.2 Power over Ethernet (PoE, PoE+, PoE++) Standards and Budgeting 2.3 LLDP, LLDP-MED, and Voice VLAN Configuration 2.4 Host IP Addressing and DHCP Relay Operations

4 Chapter 3: Network Resiliency and Virtualization

3.1 Virtual Switching Framework (VSF) Architecture and Topologies 3.2 VSF Split Detection, Failover, and Auto-Stacking 3.3 Virtual Switching Extension (VSX) Architecture and Operations 3.4 High-Availability Gateways: VRRP and VSX Active-Gateway

5 Chapter 4: AOS-CX Architecture and Switch Operation

4.1 AOS-CX Hardware Portfolio and State Database Architecture 4.2 Network Analytics Engine (NAE) and Automated Telemetry 4.3 AOS-CX Interface Configuration and Port Control 4.4 Link Aggregation (LAG) and LACP Configuration

6 Chapter 5: Layer 2 Protocols and Spanning Tree

5.1 AOS-CX VLAN Configuration and Native VLAN Handling 5.2 Spanning Tree Protocols: STP, RSTP, and MSTP 5.3 Spanning Tree Protections and Loop Prevention 5.4 MAC Address Table Learning, Aging, and Forwarding

7 Chapter 6: Wireless Fundamentals, Standards, and RF

6.1 IEEE 802.11 Standards and Wi-Fi Generations 6.2 RF Fundamentals, Signal Propagation, and Channel Design 6.3 Aruba Access Point Hardware Portfolio and Suffix Conventions 6.4 WLAN Topologies, BSSID/ESSID, and Roaming Standards

8 Chapter 7: Aruba Wireless Architecture and Management

7.1 AOS 10 Architecture and Aruba Central Integration 7.2 Wireless Forwarding Modes: Bridge vs Tunnel Mode 7.3 Automated RF and Client Optimization: AirMatch and ClientMatch 7.4 Secure Wireless Access: WPA3, SAE, and MPSK Implementation

9 Chapter 8: IP Routing Fundamentals and OSPF

8.1 IP Routing Principles and Packet Forwarding 8.2 OSPFv2 Protocol Mechanics and Adjacency Formation 8.3 OSPF Designated Routers and Multi-Area Deployments 8.4 ECMP, Static Routing, and VRF Isolation

10 Chapter 9: Campus Network Security and Segmentation

9.1 DHCP Snooping and Dynamic ARP Inspection 9.2 Port Security and MAC Address Limiting 9.3 ClearPass Policy Management and RADIUS Change of Authorization 9.4 Dynamic Segmentation, User-Based Tunneling, and Policy Enforcement

11 Chapter 10: Authentication, Authorization, and Accounting

10.1 The AAA Framework and Architecture 10.2 802.1X Authentication and EAP Methods 10.3 MAC Authentication and Captive Portal Onboarding 10.4 Administrative Access Control: RADIUS vs TACACS+

12 Chapter 11: Network Management and Telemetry

11.1 Aruba Central Cloud Architecture and Group Configuration 11.2 Zero-Touch Provisioning (ZTP) and Aruba Activate 11.3 AI Insights and Aruba User Experience Insight (UXI) 11.4 Network Telemetry, Streaming APIs, and SNMP/Syslog

13 Chapter 12: Troubleshooting the Solution

12.1 Structured Troubleshooting Methodologies and Scope Isolation 12.2 AOS-CX Layer 2 and Interface Diagnostic Commands 12.3 Layer 3, IP Services, and End-to-End Diagnostics 12.4 Physical-Layer Troubleshooting 12.5 Troubleshooting Wireless Clients and Network Access

14 Chapter 13: Optimizing Performance: QoS, Baselines, and Comparisons

13.1 Quality of Service (QoS) Classification and Marking 13.2 Queuing Algorithms and Congestion Management 13.3 Traffic Policing, Shaping, and Broadcast Rate Limiting 13.4 Establishing a Performance Baseline 13.5 Comparing Results to the Baseline

15 Chapter 14: Plan the Solution

14.1 Analyzing the Current Environment 14.2 Interpreting an Architect's High-Level Design 14.3 Creating a Low-Level Design 14.4 Preparing for Implementation

16 Chapter 15: Validate and Operate the Solution

15.1 Validating the Solution 15.2 Performing Firmware Updates 15.3 Making Basic Ongoing Configuration Changes 15.4 Maintaining Network Documentation

9.1 DHCP Snooping and Dynamic ARP Inspection

Key Takeaways Explain This Topic AI

DHCP Snooping acts as a Layer 2 perimeter firewall, classifying switch ports into trusted (uplinks to authorized DHCP servers) and untrusted (access ports where server responses are discarded).

The DHCP Snooping Binding Table dynamically tracks authenticated client MAC-to-IP bindings, lease times, VLANs, and switch ports, providing the foundational telemetry for downstream security features.

Dynamic ARP Inspection (DAI) uses the DHCP snooping database to validate Address Resolution Protocol packets on untrusted ports, thwarting ARP cache poisoning and Man-in-the-Middle (MitM) attacks.

Uplinks connecting access switches to default gateways or core infrastructure must be explicitly designated as trusted for both DHCP Snooping and DAI to prevent legitimate network traffic from being dropped.

In AOS-CX 10.14, enable DHCP snooping globally with dhcp-snooping and per VLAN with dhcp-snooping in VLAN context, enable ARP inspection with arp inspection in VLAN context, and trust uplinks with dhcp-snooping trust and arp inspection trust (older releases used dhcpv4-snooping ).

Last updated: October 2026

DHCP Snooping and Dynamic ARP Inspection

Quick Summary: Standard Ethernet networks operate on an implicit trust model where any connected endpoint can broadcast network control messages. Attackers exploit this design by introducing rogue DHCP servers or broadcasting fraudulent Address Resolution Protocol (ARP) responses to execute Man-in-the-Middle (MitM) and Denial-of-Service (DoS) attacks. DHCP Snooping mitigates rogue DHCP servers by categorizing switch ports into trusted and untrusted interfaces and dynamically building a secure binding database. Dynamic ARP Inspection (DAI) leverages this binding table to intercept and validate ARP packets on untrusted ports, ensuring that Layer 2 MAC addresses match authorized Layer 3 IP assignments.

The Layer 2 Threat Landscape: Rogue DHCP and ARP Spoofing

Within a standard broadcast domain, client devices broadcast requests to discover network infrastructure services. Because Layer 2 switches forward broadcast frames out all active ports within a VLAN by default, any host can listen to or respond to these discovery broadcasts.

The Threat of Rogue DHCP Servers

When an endpoint joins an Ethernet network, it broadcasts a DHCP Discover message. Any DHCP server residing in that broadcast domain can respond with a DHCP Offer . A rogue DHCP server —whether placed intentionally by an attacker or accidentally by an employee connecting an unmanaged wireless router—introduces severe security vulnerabilities:

Man-in-the-Middle (MitM) Traffic Redirection: The rogue server responds faster than the legitimate enterprise DHCP server, supplying client devices with a fraudulent default gateway address (pointing to the attacker's workstation). All outbound client traffic is intercepted, analyzed, or altered before being forwarded upstream.

DNS Hijacking: The rogue server assigns the IP address of an attacker-controlled DNS server, redirecting users to phishing portals or credential-harvesting clones of corporate services.

Denial of Service (DoS): The rogue server leases invalid IP configurations (such as an incorrect subnet mask or unroutable gateway), completely severing client connectivity.

DHCP Starvation Attacks: An attacker uses automated tools (such as Yersinia) to flood the legitimate DHCP server with thousands of DHCP Discover messages containing randomized MAC addresses. This exhausts the available IP scope, preventing legitimate enterprise devices from acquiring network access.

ARP Protocol Vulnerabilities and Cache Poisoning

The Address Resolution Protocol (ARP, RFC 826) maps known Layer 3 IPv4 addresses to dynamic Layer 2 Ethernet MAC addresses. However, ARP possesses no built-in authentication mechanisms:

Stateless and Unverified: Devices process and cache ARP replies even if they never transmitted a corresponding ARP request.

Gratuitous ARP Poisoning: An attacker can transmit an unsolicited Gratuitous ARP (GARP) frame asserting that the default gateway's IP address is now associated with the attacker's own MAC address. The victim workstation and the default gateway both update their local ARP caches with this forged binding.

Traffic Interception: Outbound packets from the victim to external networks are delivered directly to the attacker's switch port at Layer 2. The attacker enables IP forwarding to relay packets to the real gateway, eavesdropping on unencrypted traffic without the victim detecting connection disruption.

DHCP Snooping Operational Mechanics

DHCP Snooping acts as a Layer 2 perimeter firewall on the access switch, inspecting DHCP control messages exchanged between clients and servers. It operates by enforcing a strict classification of physical switch ports: +---------------------------------------------------------------------------------------------------------+

  • | DHCP SNOOPING PORT ARCHITECTURE |
  • | |
  • | [ Untrusted Port 1/1/1 ] --------> Client Workstation (Permits DHCP Discover / Request) |
  • | (DISCARDS Rogue DHCP Offer / ACK / NAK Frames!) |
  • | |
  • | [ AOS-CX Access Switch ] --------> Maintains DHCP Snooping Binding Table in Hardware |
  • | [ MAC | IP | Lease | Type | VLAN | Port ] |
  • | |
  • | [ Trusted Port 1/1/48 ] ---------> Uplink to Enterprise DHCP Server / Core Router |
  • | (Permits all DHCP messages: Discover, Offer, Request, ACK) |
  • +---------------------------------------------------------------------------------------------------------+
  • Trusted vs. Untrusted Ports

Untrusted Ports:

By default, once DHCP Snooping is enabled on a VLAN, all switch ports in that VLAN operate in untrusted mode .

Untrusted ports connect to edge endpoints: user laptops, desktop workstations, printers, and standard IoT devices.

Allowed Ingress Traffic: Client-originated DHCP messages, including DHCPDISCOVER , DHCPREQUEST , DHCPDECLINE , and DHCPRELEASE .

Blocked Ingress Traffic: Server-originated DHCP messages, including DHCPOFFER , DHCPACK , and DHCPNAK . If an untrusted port receives a server-generated frame, the switch immediately discards the frame, increments a security violation counter, and generates an administrative log.

Trusted Ports:

Network engineers must explicitly configure uplinks connecting to legitimate enterprise DHCP servers, DHCP relay agents, or upstream aggregation/core switches as trusted .

Allowed Ingress Traffic: All DHCP messages (both client requests and server responses) flow unimpeded without filtering.

The DHCP Snooping Binding Database

As legitimate endpoints complete the four-step DHCP transaction ( DORA : Discover, Offer, Request, ACK) across untrusted ports and trusted uplinks, the access switch snoops the passing frames. Upon observing a valid DHCPACK returning from a trusted port, the switch dynamically records an entry in the DHCP Snooping Binding Table :

  • Attribute Description Example Entry
  • MAC Address Hardware Layer 2 address of the client NIC 00:50:56:fd:aa:12
  • IP Address Leased Layer 3 IPv4 address assigned by server 10.10.20.105
  • Lease Time Duration of the lease in seconds 86400 seconds (24 hours)
  • Binding Type Origin of the binding ( dynamic or static ) dynamic
  • VLAN ID Layer 2 broadcast domain of the access port VLAN 20
  • Interface Physical switch port where the client resides 1/1/1

The switch maintains this table dynamically: when a client gracefully disconnects via DHCPRELEASE or the lease timer expires, the corresponding binding is removed. If a device uses a static IP address, an administrator can manually configure a static binding entry.

DHCP Option 82 Support

DHCP Snooping also supports DHCP Option 82 (Relay Agent Information Option). When an access switch intercepts a DHCP Discover on an untrusted port, it can append sub-options identifying the client's physical switch chassis, module, and port ( Circuit ID ) and switch identifier ( Remote ID ). The upstream DHCP server uses this metadata to allocate specific IP subnets or lease policies based on physical switch port locations.

Dynamic ARP Inspection (DAI) Mechanics

While DHCP Snooping protects the initial address acquisition process, Dynamic ARP Inspection (DAI) —referred to as ARP Protection in some AOS-S documentation and ARP Inspection in AOS-CX—secures ongoing Layer 2 to Layer 3 address resolution.

Validation Process on Untrusted Ports

DAI intercepts all ARP Request and ARP Reply frames arriving on untrusted switch ports. Before forwarding an ARP packet, the switch hardware compares the sender information stored inside the ARP packet payload against the verified DHCP Snooping Binding Table :

Payload Inspection: The switch extracts the Sender Hardware Address (SHA) and Sender Protocol Address (SPA) from the ARP payload.

Binding Table Lookup: The switch queries its internal database to verify if an active entry exists linking that exact MAC address (SHA) to that exact IP address (SPA) on that specific ingress interface and VLAN.

Forwarding Decision:

Valid Match: The ARP frame is forwarded out normal switch ports.

Invalid or Missing Entry: If the IP-MAC pairing does not match an active lease, or if no entry exists for that host, the frame is dropped immediately, and a security violation is logged.

Trusted Ports in DAI

Just as with DHCP Snooping, interfaces connecting to upstream default gateways, core switches, and trusted servers are configured as ARP Inspection Trusted . ARP packets received on trusted ports bypass inspection entirely, minimizing latency and eliminating switch CPU overhead on high-throughput uplinks.

Protecting the CPU

Because ARP inspection sends ARP packets to the switch CPU for validation, a flood of ARP traffic is also a CPU-protection concern. AOS-CX protects its control plane with control-plane policing (CoPP) and lets you cap broadcast traffic per port with rate-limit broadcast <rate> pps ; there is no separate ARP-inspection rate-limit command to memorize for this exam.

Technical Comparison: DHCP Snooping vs. Dynamic ARP Inspection

  • Technical Dimension DHCP Snooping Dynamic ARP Inspection (DAI)
  • Primary Threat Mitigated Rogue DHCP servers, DHCP starvation ARP poisoning, Man-in-the-Middle (MitM) snooping

Layer of Operation Layer 7 payload inside UDP datagrams (Ports 67/68) Layer 2/Layer 3 ARP protocol packets (EtherType 0x0806 )

Inspection Mechanism Filters server responses on untrusted ports Validates Sender MAC/IP against binding table

Database Dependency Creates and maintains the binding database Dependent on the DHCP Snooping database (or static bindings)

Untrusted Port Behavior Drops DHCPOFFER , DHCPACK , DHCPNAK Drops invalid ARP frames missing from binding table

Trusted Port Behavior Permits all DHCP requests and server responses Permits all ARP frames without database validation

AOS-CX Configuration Commands and Verification

The following AOS-CX 10.14 configuration enables DHCP snooping and Dynamic ARP Inspection on VLANs 10 and 20 and trusts the aggregation uplink. (Releases before 10.14 used the keyword dhcpv4-snooping .) switch# configure terminal

  • ! Step 1: Globally enable DHCP Snooping, then enable it per VLAN (VLAN context)
  • switch(config)# dhcp-snooping
  • switch(config)# vlan 10
  • switch(config-vlan-10)# dhcp-snooping
  • switch(config-vlan-10)# arp inspection
  • switch(config-vlan-10)# exit
  • switch(config)# vlan 20
  • switch(config-vlan-20)# dhcp-snooping
  • switch(config-vlan-20)# arp inspection
  • switch(config-vlan-20)# exit
  • ! Step 2: Configure the Uplink Port to Aggregation/Core Switch as Trusted
  • switch(config)# interface 1/1/48
  • switch(config-if)# description Uplink-to-Campus-Core
  • switch(config-if)# no routing
  • switch(config-if)# vlan trunk allowed 10,20
  • switch(config-if)# dhcp-snooping trust
  • switch(config-if)# arp inspection trust
  • switch(config-if)# exit
  • ! Step 3: Edge access ports stay untrusted (the default)
  • switch(config)# interface 1/1/1-1/1/24
  • switch(config-if-<1/1/1-1/1/24>)# no routing
  • switch(config-if-<1/1/1-1/1/24>)# vlan access 10
  • switch(config-if-<1/1/1-1/1/24>)# exit
  • Essential Verification Commands

Verification Command Operational Diagnostic Output

show dhcp-snooping Displays global DHCP snooping status, enabled VLANs, and settings such as Option 82.

show dhcp-snooping binding Lists active client bindings: MAC address, IP address, lease duration, VLAN, and interface.

show arp inspection interface Shows which interfaces are trusted or untrusted for ARP inspection.

show arp inspection statistics Displays packet counters for forwarded, dropped, and rate-limited ARP frames.

show arp inspection vlan Details per-VLAN ARP inspection status.

Common Exam Traps

DAI Dependency on DHCP Snooping: A classic exam question asks why legitimate dynamic clients lose network connectivity immediately after enabling DAI. If an administrator enables DAI before DHCP Snooping has populated the binding database, the switch drops all client ARP requests because no bindings exist! DHCP Snooping must be active and populated first.

Omitting Uplink Trust: Forgetting to configure dhcp-snooping trust on switch uplinks prevents all downstream clients from receiving IP addresses because legitimate DHCPOFFER and DHCPACK packets from the core DHCP server are dropped at the access switch uplink.

Untrusted Port Misconceptions: Untrusted ports do not block all DHCP traffic; they specifically permit client-originated requests ( DHCPDISCOVER , DHCPREQUEST ) and block server-originated responses.

Loading diagram... DHCP Snooping and Dynamic ARP Inspection Workflow