DHCP relay is not working

[#1]

We have two FGt 3000 in a cluster. We have a DHCP server connected on our management VLAN which serves a lot of the customers connected on individual VLANs. The DHCP requests are relayed to the DHCP server. Shortly after update to MR5 the DHCP relay function stopped working. I can see the DHCP request on the interface where the requesting device is connected, but nothing on the interface where the DHCP server is connected. Is ther anyone who ca give me a hint on what may be wrong? Thanks Magne

[Carl_Wallmark]

i was having problems when i configured DHCP relay, but then i played around with STP and RSTP on the switches, then it worked perfect. in my solution i have 2 FG 200A in a cluster A-P with 2 VDOMS (1 NAT, 1 TP) and with 120 VLANS, and every VLAN have its own IP network, and every VLAN is using the same DHCP server. So my problem was the Spanning Tree protocol in the switches (HP Procurve).

[#3]

That solved my problem. Thank you very much.

[Carl_Wallmark]

Ohhh, i have helped my first " customer" , im not a virgin anymore =) Wheres the beer ???????

[rwpatterson]

I thought it was a cigarette??

[Carl_Wallmark]

thats just in the movies =)

[Yngve0]

Unfortunately; My issue is not solved and Fortinet have now idee neither. My issue is -DHCP -server (windows 2k3) is located on HQ, connected to FG200A - All sub-office running DHCP-relay against central DHCP-server. Suboffice have FG50A, FG60 or FG50B with VPN-connection in interface-mode to HQ. Mainly there are a VLAN-switch(D-link 3010) connected to internal interface and multiple VLAN on each site. This was working problemless until upgrading to MR5. Y

[#8]

Have similar configuration here: - DHCP server (linux based) in main location with a cluster of 2 300A - secondary office with DHCP relay through interface mode VPN with a cluster of 2 100A We had some trouble after the upgrade to MR5 patch 1 (build 564) with both normal traffic and DHCP requests disapparing crossing the VPN tunnel. It seems that a bring down - up on the virtual interface and a disable - enable on the DHCP relay solved the problems, it' s running problemless since 1 day ago. Hope this can help Marco