Filter
Top Products
USER’S GUIDE
380 CyberSWITCH
Shortly after a DHCP Client is powered on, it will attempt to get its IP address from a DHCP Server.
If it is successful, its IP-related features (e.g., ping, telnet, etc.) will become operational. If the client
could not obtain its IP address, it will retry periodically to do so.
From the DHCP Client, attempt to ping the Relay Agent (“Ruby”) that is on the same LAN:
C:\> ping 204.157.42.168 <return>
Pinging 204.157.42.168 with 32 bytes of data:
Reply from 204.157.42.168: bytes=32 time=2ms TTL=64
Reply from 204.157.42.168: bytes=32 time=2ms TTL=64
Reply from 204.157.42.168: bytes=32 time=1ms TTL=64
Reply from 204.157.42.168: bytes=32 time=2ms TTL=64
A response of this form indicates that the IP-related features of this client are enabled. Therefore, it
has successfully obtained an IP address from the DHCP Server. If the ping attempt resulted in
something like the following, the client was not able to obtain its IP address from the DHCP Server:
C:\> ping 204.157.42.168
Pinging 204.157.42.168 with 32 bytes of data:
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
If this is the case, refer to Relay Agent Operation in the Problem Diagnosis chapter.
VERIFYING DHCP: PROXY CLIENT
The following sections provide instructions to verify that the DHCP Proxy Client is working
properly.
VERIFYING DHCP PROXY CLIENT INITIALIZATION
Regardless of whether or not the Proxy Client has been enabled via configuration, some
initialization processing is always performed. If this initialization is successful, there should not be
any warnings/errors written to the report log by the DHCP Proxy Client.
1. Examine the report log. Type:
dr
<return>
2. The
dr
command displays the system report log. Look for any messages that begin with:
[DHCP-P]
3. The following message indicate that errors occurred during DHCP Proxy Client initialization
processing:
[DHCP-P] Proxy Client initialization failed