Study guide

2.4 Host IP Addressing and DHCP Relay Operations

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

2.4 Host IP Addressing and DHCP Relay Operations

Key Takeaways Explain This Topic AI

IPv4 host configuration requires a valid unicast IP address, subnet mask, default gateway, and DNS servers, with APIPA (169.254.0.0/16) indicating DHCP communication failure.

The standard dynamic addressing lifecycle executes via the four-step DHCP DORA process (Discover, Offer, Request, Acknowledge) using UDP ports 67 and 68.

Layer 3 boundary switches and routers drop Layer 2 client broadcasts by default, necessitating a DHCP Relay Agent (ip helper-address) to forward requests to centralized DHCP servers.

The DHCP Relay Agent converts local broadcast Discovers/Requests into routed unicast packets, populating the giaddr field with its own SVI IP address to tell the server which address pool to draw from.

Centralized enterprise DHCP servers distribute critical configuration options including Option 3 (Router), Option 6 (DNS), Option 15 (Domain), and Option 43 (Vendor Specific / Aruba Controller).

Last updated: October 2026

For endpoints to communicate beyond their local Layer 2 broadcast domain, they require valid Layer 3 Internet Protocol (IP) configurations. Every host operating on an enterprise campus network requires a valid IP address, a subnet mask, a default gateway address, and one or more Domain Name System (DNS) server addresses.

While critical servers and network management interfaces use statically configured addresses, configuring thousands of user laptops, smartphones, IP phones, and IoT endpoints manually is completely unscalable. Enterprise networks rely on the Dynamic Host Configuration Protocol (DHCP) to automate IP assignment. In segmented campus networks where clients reside in separate VLANs isolated from centralized enterprise DHCP servers, the DHCP Relay Agent ( ip helper-address ) plays an indispensable bridging role.

IPv4 Host Addressing Principles and Network Boundaries

An IPv4 address is a 32-bit binary number traditionally written in dotted-decimal format as four 8-bit octets separated by periods (e.g., 192.168.10.50 ).

The Anatomy of an IPv4 Address

Every IPv4 address is divided into two distinct components:

Network Portion (Prefix): Identifies the specific Layer 3 logical network or subnet. All hosts residing on the same physical or virtual broadcast domain share the identical network portion.

Host Portion: Uniquely distinguishes an individual interface within that specific subnet.

The boundary between the network portion and host portion is determined by the Subnet Mask , expressed in standard dotted-decimal notation (e.g., 255.255.255.0 ) or Classless Inter-Domain Routing ( CIDR ) prefix notation (e.g., /24 ).

Common Subnet Masks in Enterprise Campus Networks

  • CIDR Prefix Subnet Mask Total Addresses Usable Host Addresses Primary Campus Use Case
  • /24 255.255.255.0 256 254 Standard campus user access subnets, dedicated voice VLANs
  • /23 255.255.254.0 512 510 Large high-density wireless client pools, large auditorium Wi-Fi
  • /25 255.255.255.128 128 126 Departmental subnets, branch office LAN segments
  • /28 255.255.255.240 16 14 Small management networks, out-of-band switch subnets
  • /30 255.255.255.252 4 2 Point-to-point routed links between core and distribution switches
  • /31 255.255.255.254 2 2 Point-to-point routed links (RFC 3021, saves IP address space)

Important Addressing Rule: In every subnet from /0 through /30, two addresses are reserved and cannot be assigned to hosts (only /31 point-to-point links and /32 host routes are exceptions):

Network Address: All host bits set to binary 0 (e.g., 10.1.10.0 in a /24 ). Represents the subnet itself.

Directed Broadcast Address: All host bits set to binary 1 (e.g., 10.1.10.255 in a /24 ). Targets all hosts within that specific subnet simultaneously.

The Host Configuration Quartet

To communicate fully across an enterprise intranet and the global Internet, a client operating system requires four configuration values:

IP Address: A unique unicast address within the local subnet.

Subnet Mask: Defines which destination IPs are local (reached directly via Layer 2 ARP) versus remote.

Default Gateway: The IP address of the local Layer 3 router interface or Switched Virtual Interface (SVI). When a host needs to communicate with an IP address outside its local subnet, it encapsulates the IP packet into a Layer 2 frame addressed to the default gateway's MAC address.

DNS Servers: The IP addresses of recursive name servers that resolve human-readable domain names (e.g., portal.company.com ) into routable IP addresses.

Automatic Private IP Addressing (APIPA)

When a client device configured for dynamic addressing boots up, it issues DHCP Discover requests. If no DHCP server responds within a timeout window (typically 30 to 60 seconds), the client operating system falls back to Automatic Private IP Addressing (APIPA) , formalized in RFC 3927 :

Address Block: 169.254.0.0/16 (specifically 169.254.1.0 through 169.254.254.255 , reserving the first and last 256 addresses for future use).

Link-Local Scope: APIPA addresses are strictly link-local. Routers and Layer 3 switches must never forward packets containing 169.254.x.x addresses across network boundaries.

Collision Detection: The host generates a pseudo-random host address within 169.254.0.0/16 and transmits gratuitous Address Resolution Protocol (ARP) probes onto the local wire. If another device replies, the host generates a different address until uniqueness is verified.

Troubleshooting Significance: Seeing a 169.254.x.x address on an endpoint is an unmistakable diagnostic indicator: it proves that the physical Ethernet link and local network adapter driver are working properly, but Layer 2 or Layer 3 communication to a reachable DHCP server has completely failed.

DHCP Protocol Architecture and the DORA Flow

DHCP operates on a client-server architecture utilizing the User Datagram Protocol (UDP) :

  • DHCP Servers listen on: UDP Port 67
  • DHCP Clients listen on: UDP Port 68
  • The Four-Step DORA Handshake

When a client requests an IP configuration, it executes the four-step DORA exchange: +-------------+ +-------------+

  • | DHCP Client | | DHCP Server |
  • +------+------+ +------+------+
  • | |
  • | 1. DHCP Discover (Broadcast) |
  • | Source: 0.0.0.0:68 Dest: 255.255.255.255:67 |
  • |------------------------------------------------------>|
  • | |
  • | 2. DHCP Offer (Unicast or Broadcast) |
  • | Source: Server IP:67 Dest: Client IP/Broadcast:68 |
  • |<------------------------------------------------------|
  • | |
  • | 3. DHCP Request (Broadcast) |
  • | Source: 0.0.0.0:68 Dest: 255.255.255.255:67 |
  • |------------------------------------------------------>|
  • | |
  • | 4. DHCP Acknowledge / ACK (Unicast or Broadcast) |
  • | Source: Server IP:67 Dest: Client IP/Broadcast:68 |
  • |<------------------------------------------------------|
  • v v

DHCP Discover:

Because the client has no assigned IP address and does not know where the DHCP server resides, it emits a broadcast packet.

  • Source IP: 0.0.0.0
  • Destination IP: 255.255.255.255 (Limited Broadcast)
  • Source Port: UDP 68 | Destination Port: UDP 67

Payload: The client places its physical Layer 2 MAC address inside the CHADDR (Client Hardware Address) field so the server knows who originated the request.

DHCP Offer:

Any reachable DHCP server that receives the Discover inspects its address pools. It reserves an unassigned IP address and replies with an Offer.

Payload: Proposes an available IP address (the YIADDR / Your IP Address field), subnet mask, lease duration, default gateway (Option 3), and DNS servers (Option 6).

DHCP Request:

In multi-server environments, a client may receive multiple Offers. The client selects one (typically the first received) and broadcasts a DHCP Request.

Why Broadcast? Broadcasting the Request serves two critical purposes: it confirms acceptance to the chosen server (identifying it via Option 54, Server Identifier), and it notifies all other servers that their Offers were rejected, allowing them to release their reserved IP addresses back into their pools.

DHCP Acknowledge (ACK):

The chosen server commits the IP lease to its local binding database and transmits a final DHCP ACK.

Once the client receives the ACK, it initiates an ARP probe for the assigned IP to ensure no duplicate IP address exists on the local link, and then binds the IP address to its interface.

Lease Lifecycles and Timers

DHCP assignments are not permanent; they are leases:

Lease Time: Total duration for which the client is permitted to use the IP address.

T1 Renewal Timer (50% of lease): When half the lease expires, the client sends a unicast DHCP Request directly to the original leasing server. If the server is online, it replies with a unicast ACK extending the lease.

T2 Rebinding Timer (87.5% of lease): If the original server fails to respond at T1, the client continues using the IP until 87.5% of the lease expires. At T2, the client broadcasts a DHCP Request across the local network, seeking a lease extension from any authorized DHCP server.

Expiration (100% of lease): If no server replies before the lease reaches 100%, the client must immediately stop using the IP address and restart the Discover cycle from scratch.

Essential Enterprise DHCP Options

DHCP options carry supplemental configuration parameters inside the DHCP packet payload:

Option 3 (Router): Specifies the IPv4 address of the default gateway for the client subnet.

Option 6 (Domain Name Server): Lists primary and secondary DNS server IP addresses.

Option 15 (Domain Name): Supplies the default DNS search domain suffix (e.g., corp.example.com ).

Option 43 (Vendor-Specific Information): Used extensively in enterprise campus networks to pass operational parameters to specialized hardware. For example, controller-based (AOS 8) Aruba campus APs can use Option 43 to learn the IP address of their Mobility Controller, and AOS-CX switches read Option 43 sub-options during ZTP.

Option 60 (Vendor Class Identifier / VCI): Transmitted by the client to identify its device category (e.g., ArubaAP or ArubaInstantAP ), allowing the DHCP server to return tailored Option 43 payloads.

AOS-CX ZTP options (AOS-CX 10.14 Fundamentals Guide): Option 43 sub-option 144 names the configuration file, 145 names the firmware image, 146 gives the FQDN or IPv4 address of an on-premises Central server, and 148 gives an HTTP proxy; Option 66 supplies the TFTP server IPv4 address and Option 67 the configuration file name.

DHCP Relay Operations ( ip helper-address )

In modern enterprise networks, campus access switches create separate Layer 2 broadcast domains for every department or floor (e.g., VLAN 10 for Engineering, VLAN 20 for Sales, VLAN 30 for VoIP). Dedicated enterprise DHCP servers reside centrally in a secure data center or server farm VLAN (e.g., VLAN 100).

The Layer 2 Broadcast Problem

By fundamental design, routers and Layer 3 switches drop Layer 2 broadcast frames ( 255.255.255.255 ). Therefore, when a client in VLAN 10 broadcasts a DHCP Discover, the broadcast is bounded by VLAN 10 and cannot cross the Layer 3 boundary to reach the centralized DHCP server in VLAN 100.

Deploying a dedicated physical DHCP server inside every individual access VLAN would be unmanageable and cost-prohibitive. The standard architectural solution is configuring a DHCP Relay Agent .

How the DHCP Relay Agent Works

The DHCP Relay Agent is configured on the Layer 3 interface that serves as the default gateway for the client subnet (typically a Switched Virtual Interface, or SVI , on an AOS-CX aggregation or core switch): [ Client Workstation ]

  • | (VLAN 10)
  • | 1. Broadcast Discover (255.255.255.255:67)
  • v
  • [ AOS-CX Aggregation Switch ]
  • SVI Interface vlan 10 (IP: 10.1.10.1)
  • ip helper-address 10.1.100.50
  • |

| 2. Relay Agent Actions:

  • | - Intercepts broadcast Discover on UDP 67
  • | - Populates giaddr = 10.1.10.1
  • | - Converts broadcast into unicast packet
  • | - Source IP: 10.1.10.1, Destination IP: 10.1.100.50:67
  • v (Routed Campus Backbone)
  • [ Central Enterprise DHCP Server ] (IP: 10.1.100.50)
  • |
  • | 3. Inspects giaddr (10.1.10.1)
  • | - Matches giaddr to local pool: 10.1.10.0/24
  • | - Selects available IP: 10.1.10.55
  • | - Sends unicast DHCP Offer back to giaddr (10.1.10.1:67)
  • v
  • [ AOS-CX Aggregation Switch ]
  • SVI Interface vlan 10
  • |
  • | 4. Relays the reply onto VLAN 10
  • | - Delivers the Offer to the client MAC
  • v
  • [ Client Workstation ] (Binds 10.1.10.55)
  • The Role of the giaddr Field

The most critical mechanism in DHCP relay operations is the Gateway IP Address ( giaddr ) field inside the DHCP header:

When the client broadcasts its Discover, giaddr is set to 0.0.0.0 .

When the AOS-CX SVI intercepts the frame, it writes its own IP address ( 10.1.10.1 ) into the giaddr field.

The switch converts the broadcast into a routable unicast IP packet (Source IP: 10.1.10.1 , Destination IP: 10.1.100.50 ) and forwards it across the routed campus core.

When the central DHCP server receives the packet, it does not look at the source IP in the IP header; it examines the giaddr field inside the DHCP payload.

The giaddr value ( 10.1.10.1 ) tells the DHCP server exactly which subnet pool to draw from ( 10.1.10.0/24 ). Without giaddr , the central server would have no way of knowing which subnet the client belongs to.

The server generates a DHCP Offer and unicasts it directly back to the IP address specified in giaddr ( 10.1.10.1 ).

The AOS-CX switch receives the unicast Offer on UDP port 67, recognizes that it is a relayed response, and relays it onto the local VLAN 10 segment to the client's hardware address (as a broadcast or unicast, depending on the client's broadcast flag).

  • AOS-CX DHCP Relay Configuration and Diagnostics
  • Configuring DHCP Relay on an SVI

In AOS-CX, the DHCP Relay Agent is enabled by applying the ip helper-address command directly to the routed SVI ( interface vlan ) or routed physical interface. Multiple helper addresses can be specified to support redundant DHCP servers: switch# configure terminal

  • ! Configure the Layer 3 SVI for VLAN 10
  • switch(config)# interface vlan 10
  • switch(config-if-vlan)# description "Engineering Department Gateway"
  • switch(config-if-vlan)# ip address 10.1.10.1/24
  • ! Configure primary and secondary centralized DHCP servers
  • switch(config-if-vlan)# ip helper-address 10.1.100.50
  • switch(config-if-vlan)# ip helper-address 10.1.100.51
  • switch(config-if-vlan)# exit
  • Verifying DHCP Relay Status and Counters

To list the helper addresses configured on each interface, execute show ip helper-address (AOS-CX 10.14 CLI Guide). The output below is abbreviated: switch# show ip helper-address

IP Helper Addresses

  • Interface: vlan10
  • IP Helper Address VRF
  • ---------------- -----------------
  • 10.1.100.50 default
  • 10.1.100.51 default

To confirm that the relay agent is enabled and to read its request and response counters, execute show dhcp-relay : switch# show dhcp-relay

  • DHCP Relay Agent : enabled
  • DHCP Request Hop Count Increment : enabled
  • Option 82 : disabled

DHCP Relay Statistics:

  • Valid Requests Dropped Requests Valid Responses Dropped Responses
  • ------------- ---------------- --------------- -----------------
  • 1420 0 1418 0
  • Common DHCP Relay Troubleshooting Checkpoints

When clients in a VLAN fail to receive IP addresses and self-assign APIPA addresses, verify the following root causes:

Missing ip helper-address : The helper address must be configured on the specific SVI acting as the client's Layer 3 gateway. If configured on the wrong VLAN interface, broadcasts will be dropped.

Routing Reachability: The switch SVI must have a valid routing path to reach the DHCP server, and the DHCP server must have a return route back to the SVI's giaddr subnet.

Access Control Lists (ACLs) / Firewalls: Security policies traversing intermediate firewalls or applied to switch interfaces must permit UDP port 67 and 68 traffic between the SVI IP and the DHCP server.

DHCP Scope Exhaustion: If show dhcp-relay shows valid requests climbing but almost no valid responses, the central DHCP server scope matching giaddr may be deactivated or 100% exhausted.

Loading diagram... DHCP Relay Architecture and Packet Routing Flow