Clients connected to VLAN 20 () are unexpectedly receiving IPv4 address leases from the pool configured for VLAN 10 (). Inspection of the central DHCP server shows healthy scope configurations. Which of the following is the most likely cause of this issue?
- The relay agent command was configured on the Switch Virtual Interface (SVI) for VLAN 10 instead of VLAN 20, causing the gateway IP address () field to be populated with VLAN 10's interface IP.Answer
- BThe DHCP relay agent converted the unicast broadcast into Layer 2 multicast frames, overriding the subnet scope selection mechanism.
- CThe relay agent modified the source UDP port from 67 to 68 before forwarding the unicast packet to the central server.
- DThe workstations failed to broadcast a packet and automatically generated an APIPA address within the VLAN 10 range.
Answer
The relay agent command was configured on the Switch Virtual Interface (SVI) for VLAN 10 instead of VLAN 20, causing the gateway IP address () field to be populated with VLAN 10's interface IP.
When a Layer 3 device acts as a DHCP relay agent, it captures client Layer 2 broadcast requests on a specific interface, populates the gateway IP address () field with that receiving interface's IP address, and unicasts the packet to the DHCP server. If the relay directive is placed on VLAN 10's interface instead of VLAN 20's, the sent to the server will belong to VLAN 10, causing the DHCP server to select and lease an IP address from the VLAN 10 scope.
Step-by-Step Solution
Key Concept
DHCP Relay Gateway IP Address (giaddr) Population