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

When using set monitor, why do I have to have errors at the secondary remote end?

I am using set monitor Primary_VPN for a backuip VPN to my DR site.

 

But I am getting IPSEC errors showing in my logs. See below. and attached JPG

 

ike 0:18c308510a545aed/0000000000000000:348998: responder: main mode get 1st message... ike 0:18c308510a545aed/0000000000000000:348998: VID DPD AFCAD71368A1F1C96B8696FC77570100 ike 0:18c308510a545aed/0000000000000000:348998: VID FRAGMENTATION 4048B7D56EBCE88525E7DE7F00D6C2D3 ike 0:18c308510a545aed/0000000000000000:348998: VID FRAGMENTATION 4048B7D56EBCE88525E7DE7F00D6C2D3C0000000 ike 0:18c308510a545aed/0000000000000000:348998: VID FORTIGATE 8299031757A36082C6A621DE0005026A ike 0:Annap_Trappe: ignoring IKE request, primary is still active. ike 0:18c308510a545aed/0000000000000000:348998: negotiation failure ike Negotiate ISAKMP SA Error: ike 0:18c308510a545aed/0000000000000000:348998: no SA proposal chosen

 

1 REPLY 1
ede_pfau
Esteemed Contributor III

I don't think these are errors, just messages that the monitored phase1 is still alive. I guess the attempt to establish the backup's phase1 is triggered periodically and then this condition is checked.


Ede

"Kernel panic: Aiee, killing interrupt handler!"
Ede"Kernel panic: Aiee, killing interrupt handler!"
Labels
Top Kudoed Authors