Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
PaulSA
New Contributor II

Fortilink DHCP

Hi,
I have a question about the fortilink. I transformed port A of my fortinet into a classic lan port.
And I use a DHCP on this port but it does not work, I do not get any ip address (if I fix the IP address, the network works)
the DHCP does not work because it is a Fortilink port? How can I solve this problem?
1 Solution
ede_pfau
SuperUser
SuperUser

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.

 

 

Ede Kernel panic: Aiee, killing interrupt handler!

View solution in original post

Ede Kernel panic: Aiee, killing interrupt handler!
3 REPLIES 3
gfleming
Staff
Staff

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?

Cheers,
Graham
ede_pfau
SuperUser
SuperUser

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.

 

 

Ede Kernel panic: Aiee, killing interrupt handler!
Ede Kernel panic: Aiee, killing interrupt handler!
PaulSA
New Contributor II

Thanks for your help !

Announcements

Select Forum Responses to become Knowledge Articles!

Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.

Labels
Top Kudoed Authors