Solved! Go to Solution.
I would check the interface settings and remove it's role as a FortiLink:
conf sys int
edit "a"
set fortilink disable
next
end
Then, I'd check if the DHCP server is restricted to only serve certain devices identified by a VCI string:
config system dhcp server
edit 4
set default-gateway 169.254.2.1
set netmask 255.255.255.0
set interface "port18"
...
set vci-match enable
set vci-string "FortiSwitch" "FortiExtender"
next
If so, just set "set vci-match disable" to fix.
It should work no problem. FortiLink uses DHCP to provide addressing to switches and aps.
Do you have DHCP running on other interfaces OK?
Do other devices on port A suffer the same issue of not getting DHCP or is it just this one device?
What do your log messages show or packet captures show for the DHCP process?
I would check the interface settings and remove it's role as a FortiLink:
conf sys int
edit "a"
set fortilink disable
next
end
Then, I'd check if the DHCP server is restricted to only serve certain devices identified by a VCI string:
config system dhcp server
edit 4
set default-gateway 169.254.2.1
set netmask 255.255.255.0
set interface "port18"
...
set vci-match enable
set vci-string "FortiSwitch" "FortiExtender"
next
If so, just set "set vci-match disable" to fix.
Thanks for your help !
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1740 | |
1108 | |
752 | |
447 | |
240 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.