Hi,
Vdom1 Link name : TO-VDOM21Ip 10.0.2.2/24 Interface ospf 10.0.2.2 Network 10.0.2.0/24 E2 192.168.3.10/32 [110/20] via 10.0.2.1, TO-VDOM21, 00:47:31192.168.5.0/24 [110/20] via 10.0.2.1 TO-VDOM21, 00:47:31 from vdom1 i cannot reach 192.168.3.10 ,but vdom 2 I can reach ——————————————————————————————— Vdom2 interface to_router3Ip 192.168.5.11 Vdom2 linkName TO-VDOM20 ip 10.0.2.1/24 interface ospf 10.0.2.2 192.168.5.10( port5 internal) Network 192.68.5.0/2410.0.2.0/24 OSPF ROUTE O E2 192.168.3.10/32 [110/20] via 192.168.5.12, to_router3 , 04:52:39 Please help Thanks
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
Hi,
Through ospf router3 must have learned about 10.0.2.2
I executed ping from FW cli , did not use any source ip address
from firewall local traffic log , I can see source is 10.0.2.2
Thanks
That's the first thing I would check for any routing issues. Because that's the most common problem: route is not there.Then if all routes are there at all hops, it's time to sniff traffic at vdom2 "diag sniffer packet any 'host 10.0.2.2' 4" to see it's actually going out and a return comes back in.
Since you never mentioned about a pair of policies at vdom2, I'm assuming they're there to pass traffic from/to the vdom-link to/from the interface toward router3.
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1732 | |
1106 | |
752 | |
447 | |
240 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.