A network technician is troubleshooting an issue where a newly connected workstation on VLAN 30 fails to receive an IP address from a central DHCP server located on VLAN 10. Place the troubleshooting steps in the correct logical sequence according to standard network troubleshooting methodology to isolate and resolve the issue.
- 1Check physical layer connectivity and verify that the workstation switch port LED indicates an active link.
- 2Run an IP configuration command on the client workstation to verify whether it has assigned itself an APIPA address (169.254.x.x).
- 3Inspect the default gateway router interface configuration for VLAN 30 to confirm that the 'ip helper-address' points to the DHCP server on VLAN 10.
- 4Review the DHCP server administration console to verify that the address pool for VLAN 30 is not exhausted of available IP leases.
Answer
The correct logical order begins with Layer 1 physical link verification, followed by local client IP configuration inspection, then router DHCP relay (ip helper-address) verification, and lastly central DHCP server scope pool check.
The correct sequence follows standard structured troubleshooting: starting at the physical layer (verifying link LED), checking local operating system network configuration (confirming APIPA), inspecting intermediate network infrastructure (verifying IP helper/DHCP relay placement across VLAN boundaries), and finally validating end-service resource capacity (DHCP scope pool status).
Step-by-Step Solution
Key Concept
Inter-VLAN DHCP Troubleshooting Methodology