Description
This article discusses how to troubleshoot issues with Hosts in isolation which are not receiving an IP address.
Scope
FortiNAC.
Solution
Log in to the CLI of the Server/Application server and do the following:
- Ensure appliance is fully booted.
- Control processes are running (Yams). Type:
jps
- DHCP service is running:
service dhcpd status
Example of running service:
> service dhcpd status
Redirecting to /bin/systemctl status dhcpd.service
● dhcpd.service - DHCPv4 Server Daemon
Loaded: loaded (/usr/lib/systemd/system/dhcpd.service; enabled; vendor preset: disabled)
Active: active (running) since Thu 2019-12-26 15:44:53 EST; 4 days ago
...
- If the DHCP is not running:
Verify eth1 interface is up. In the CLI of the Server or Application Server, run the command:
ip addr show dev eth1
Example:
> ip addr show dev eth1
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
...
- If eth1 is up, attempt restarting the service:
service dhcpd restart
- If the service fails to start and output reports Read-only file system, refer to related KB article:
- If eth1 is administratively up but has no link, troubleshoot network connection. See related KB article:
- Ensure there is ample disk space on file system.
df -h
- If dhcpd is running, refer to the related KB articles below for additional troubleshooting steps:
- If additional information is needed to determine the problem, collect logs. Refer to the following KB article:
- Review the following logs for errors:
/bsc/logs/messages
/bsc/logs/dhcpd.log
