- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
L3 VLAN interface up, but IP/Network missing under locally connected network
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Root cause was found to be in the FortiOS 6.2.9
After upgrading to 6.2.10, this issue was resolved.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dear Jonas
Your issue required to verify configuration and do deeper troubleshooting. I would suggest to raise a ticket with Fortinet technical support.
Visit us at https://community.fortinet.com to get answers to questions, technical documentation, and collaborate with Fortinet global community.
Pratheesh Kungatti
Technical Support Manager, Fortinet Middle East
E: pkungatti@fortinet.com
T: 00971 44239650
Block B, 6TH Floor Office Park Building,
Dubai Internet city, Dubai, UAE
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Can you post the output of the following as well as what IP address is on the interface? A configuration of the interface could be helpful as well from #Config system interface.
# get router info routing-table database
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I've created a TAC support ticket for the issue.
My findings so far is, that the networks are injected to the locally connected routing table if I create the interfaces directly onbox, either via GUI or CLI.
However since the FortiGate is managed via our
FortiManager
i'll usually create and push config from it. And it is when done via the Fortimanager that the issue occure
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Investigation so far suspects that the downgrade from 6.4.x to 6.2.x, might have resolved in this behavior.
Next step for me is to format the FortiGates, install FortiOS 6.2.x again and import config.
Hopefully this fixes the issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Root cause was found to be in the FortiOS 6.2.9
After upgrading to 6.2.10, this issue was resolved.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I wouldn't jump to the conclusion only because upgrading it to 6.2.10 solved the problem, unless you found it in the release notes. When you upgraded, it was rebooted and LACP needed to re-negotiate and sync again with remote on both FGT and Nexus side.
Toshi
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @Toshi_Esumi
Root cause and the bug was identified as part of Fortinet TAC support ticket, and verified by their engineering staff.
As per their suggestion, I upgraded to 6.2.10 as they had solved the issue with this build.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Can you share the bug ID?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sure.
The bug ID #0689317
