NEC IP8800/S6600 DynamicDNS Cooperation in Dhcp Function Is Disabled, Checking layer 2 network

3.Troubleshooting Functional Failures in Operation

communication to the other party cannot be verified with the ping command, use ping to check communication toward clients starting from the system closest to this system. For an example of issuing ping and how to interpret the result, see the manual "Configuration Settings."

3.If the server and the client are directly connected, check the HUB and cable connections.

4.Depending on the extent of failure detected by the ping command, that is the neighboring system or remote system, proceed to the next step in the failure analysis flow.

(d) Checking route information

Check the route information acquired by this system if communication is not possible even when the address resolution with the neighboring system is achieved, or if communication is disabled in the midway to the other party, or if the route to the other party is abnormal. Use the following procedure:

1.Log in to the system.

2.Execute the show ip route command to check the route information acquired by this system.

(e) Checking filtering/QoS setting information

Only certain packets may have been discarded by filtering, or packets may have been discarded through bandwidth monitoring, discarding control, or shaper of the QoS control.

Check to see if the conditions of filtering and QoS control in the configuration have been set up correctly and if bandwidth monitoring, discarding control, or shaper has been set up appropriately for system operation in system configuration, on this system and on the relay equipment located between the client and server. For the procedure, see "3.23.1 Checking Filtering/QoS Setting Information."

(f)Checking layer 2 network

If no setting error or failure is found in steps (a) to (e), the layer 2 network may have problem. Check the layer 2 network, referring to "3.5 Layer 2 Network Communication Failure"

3.6.3DynamicDNS Cooperation in DHCP Function Is Disabled

(1)DHCP server communication trouble

Following are three possible causes for DHCP server communication failures.

1.Configuration error

2.Network configuration has changed

3.DHCP server failure

First, check 1 above. This section describes configurations that are easily misconfigured. For 2 above, check for the differences in the network configuration provided before and after the change. Check for any difference disabling communication. If the DNS server/DHCP server settings (network card setting, cable connection, etc.) have been confirmed to be normal, and if the configuration and network configuration are correct but IP communications are unavailable because IP addresses cannot be assigned to clients, as described in 3 above, see "(b)Checking time information" through "(f)Checking filtering/QoS setting information" for details.

To locate the failed part and cause, follow the flow below.

58