A network engineer is configuring a newly provisioned Layer 3 switch interface to relay DHCP traffic from a client subnet () to a centralized DHCP server located at . Although the command `ip helper-address 10.200.10.5` has been applied to the client-facing VLAN interface, workstations on the subnet fail to obtain IP addresses. Packet captures on the centralized DHCP server indicate that relayed unicast packets arrive, but the server discards them because the Gateway IP Address () field in the DHCP header is set to . Which of the following configuration issues is the primary cause of this behavior?
- The client-facing VLAN interface on the Layer 3 switch lacks an assigned IPv4 address, preventing the relay agent from identifying the client subnet scope.Answer
- BThe IP helper address was configured on the egress interface connecting toward the centralized DHCP server rather than the client gateway interface.
- CThe switch modified the destination UDP port from port 67 to port 68 when converting the broadcast frame into a unicast packet.
- DThe Layer 3 switch failed to flood the broadcast frame across all ports member to the management VLAN prior to encapsulation.
Answer
The client-facing VLAN interface on the Layer 3 switch lacks an assigned IPv4 address, preventing the relay agent from identifying the client subnet scope.
DHCP Relay agents require a valid Layer 3 IPv4 address on the client-facing interface where the broadcast is received. This interface IP address is written into the field of the DHCP header before forwarding the packet via unicast to the DHCP server. If the interface lacks an IP address, the relay agent sets to , causing the DHCP server to discard the request because it cannot determine which address pool/scope to allocate from.
Step-by-Step Solution
Key Concept
DHCP Relay Agent Subnet Selection via GIADDR Field
Estimated Time:2m 0s