Description
This article discusses an issue when DHCP service is not starting after the appliance has powered up after a power failure in the closet or building.
Scope
FortiNAC.
Solution
Verify eth1 interface of the Server or Application Server has link and is administratively up. In the CLI of the Server or Application Server, run the command:
ip addr show dev eth1
> ip addr show dev eth1
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
...
If eth1 has no link, but the interface is administratively up:
- Verify the switch to which eth1 connects is powered and the switch port is working
- Check the cabling connecting eth1 and switch port
Related article:
Technical Note: DHCP service running but isolated hosts do not get IP
Technical Note: Troubleshooting DHCP for isolation VLANs
