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

FortiGate goes wild

Hello!

 

We have complete mystery situation. Two FortiGates has been connected one to each other via internal port 3. this ports have ip addresses as 2.2.2.1-2/24.

 

But they unable to ping each other!

 

When we issue show arp, we can see arp from second forti. But when we are trying to ssh we get : no route to host.

When we are using trace route, its shows trace like 127.0.0.1 ms H! (no route to host)

Policy set like permit ip any any.

 

How to ping directly connected fortigate ?

3 REPLIES 3
emnoc
Esteemed Contributor III

The diag debug flow is your friend, but I 'm guessing set allowaccess is not set up to allow ping ( show sys interface port3  from the cli )

 

PCNSE 

NSE 

StrongSwan  

ede_pfau
Esteemed Contributor III

'No route' is funny as assigning an IP address to a port automatically inserts a route to that subnet. Could you show us the routing table (Routing monitor)? Is the address mask on both FGTs correct?


Ede

"Kernel panic: Aiee, killing interrupt handler!"
Fahad
New Contributor III

on the routing monitor you should see 2.2.2.0 as connect, do you see that ?

FCSNP 5, JNCIS-FW,JNCIA-SSL ,MCSE, ITIL.