A network technician is deploying a new smart HVAC controller on VLAN 55 (). The corporate DHCP server is centralized on VLAN 10 (). Upon booting up the controller, running a network diagnostics command shows the following output:
IPv4 Address. . . . . . . . . . . : 169.254.108.42
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCP Enabled. . . . . . . . . . . : Yes
Other existing hosts on VLAN 10 obtain their DHCP leases without issues. Which of the following is the MOST likely cause of the HVAC controller failing to acquire an IP address?
- AThe HVAC controller was configured with an incorrect default gateway residing outside its subnet.
- The router interface servicing VLAN 55 lacks an IP helper address configured to forward broadcast DHCP requests.Answer
- CThe DHCP relay service is misconfigured on the central DHCP server instead of the local workstation OS.
- DThe DHCP scope for VLAN 55 became exhausted because usable host calculations included the network and broadcast addresses.
Answer
The router interface servicing VLAN 55 lacks an IP helper address configured to forward broadcast DHCP requests.
The client's self-assignment of an Automatic Private IP Address () indicates that its DHCPDISCOVER broadcast was never answered. Since the host resides on VLAN 55 and the DHCP server resides on VLAN 10, the Layer 3 boundary router between these subnets drops the broadcast unless an IP helper address (DHCP Relay agent) is explicitly configured on the VLAN 55 interface to convert the broadcast to unicast.
Step-by-Step Solution
Key Concept
Troubleshooting DHCP Relay / IP Helper across Subnets and APIPA Diagnosis