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

Connected route not in table

In a multi-VDOM setup (91G @7.4.8) I have connected routes in several VDOMs, iBGP between VDOMs, one VDOM as RR. For root VDOM I have the route 192.168.0.0/24 (VLAN on a LAG), and the physical port is up. I can even ping it. But it does not show up in the routing table - and thus is not advertised to it's peers nor the RR.

 

Any pointers here? It's not in the routing-table database. I see the connected routes of the other VDOMs via BGP.

 

FG1 (root) # execute ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1): 56 data bytes
64 bytes from 192.168.0.1: icmp_seq=0 ttl=255 time=0.0 ms

--- 192.168.0.1 ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max = 0.0/0.0/0.0 ms

FG1 (root) # get router info routing-table connected | grep 192

DS1 (root) # get router info routing-table details 192.168.0.0/24
% Network not in table

 

 

3 REPLIES 3
BillH_FTNT
Staff
Staff

You can check the routing table in database and all.

 

get router info routing-table database

get router info routing-table all

 

Regards

Bill

paulism

Yes - I did that. However downgrading to 7.4.7 and then back to 7.4.8 seems to have worked. Feels like a bug to me.

BillH_FTNT

Hi @paulism 

Thanks for the information. I would like to reproduce this issue in the lab. Could you please share the full configuration, or at least the relevant routing configuration, with me via email at bhoang@fortinet.com? I will use it to replicate the issue and investigate the root cause.
Thanks again!

Regards

Bill

Announcements
Check out our Community Chatter Blog! Click here to get involved
Labels
Top Kudoed Authors