Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
Not applicable

IPSec VPN error in log 37130

Hi, I' m currently replacing our SonicWall VPN routers with Fortinet 50B units. At our head office I have done the switch to the new 50B. I have IPsecVPN tunnels setup to our two other locations and data is passing through without an issue. My only problem is that an error of 37130 keeps appearing in the Fortinet logs. There doesn' t seem to be a link problem as data and voice calls are working fine, but the error keeps appearing a couple of times a minute. error is: Message meets Alert condition date=2011-08-12 time=09:41:42 devname=BacchusMarsh device_id=FGT50B3G11607202 log_id=0101037130 type=event subtype=ipsec pri=error vd=" root" msg=" progress IPsec phase 2" action=" negotiate" rem_ip=***.***.***.*** loc_ip=***.***.***.*** rem_port=500 loc_port=500 out_intf=" wan1" cookies=" 17551550864f7a4e/3f0118ce04659fd0" user=" N/A" group=" N/A" xauth_user=" N/A" xauth_group=" N/A" vpn_tunnel=" BMtoSyd_Tunnel" status=failure init=remote mode=quick dir=inbound stage=1 role=responder result=ERROR Any ideas would be great.
1 REPLY 1
ede_pfau
SuperUser
SuperUser

Hi, and welcome to the forums. It looks like the remote side tries to set up a tunnel while the central FGT already has one open. Could you check that the remote firewalls do not negotiate on their own? This would explain why the traffic is not affected, it' s using the tunnel negotiated from the FGT.
Ede Kernel panic: Aiee, killing interrupt handler!
Ede Kernel panic: Aiee, killing interrupt handler!
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