Hi!
I am using a Fortigate 200E with software version 5.4.5
I am trying to delete a vlan-interface. The problem is:
fg200e_HZ_1_1 (interface) # delete Inet992
The entry is used by other 4 entries
Command fail. Return code -23
fg200e_HZ_1_1 (root) # diagnose sys checkused system.interface.name Inet992
--> The GUI shows 4 references, but there are NO references.
The config does not show any other occurence of the name "Inet992" except the interface definition.
Do you have any idea, how to delete the interface with the "invisible" references?
Thank you and best wishes
KPS
Solved! Go to Solution.
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.
Your probably missing a address binding, What I would do is to download the cfg and parse thru it or use
clid-cmd show | grep -f Inet992
And look for any references.
Ken
PCNSE
NSE
StrongSwan
Your probably missing a address binding, What I would do is to download the cfg and parse thru it or use
clid-cmd show | grep -f Inet992
And look for any references.
Ken
PCNSE
NSE
StrongSwan
Once in the past on a smaller unit I had a similar issue. A reboot cleared that issue up. Not sure if you can do that. It was up way too long.
Bob - self proclaimed posting junkie!
See my Fortigate related scripts at: http://fortigate.camerabob.com
show | grep -f Inet992
--> did only show the interface definition
I will try to schedule a reboot, tomorrow.
Thank you for your help!
The cmdb by design has handlers for configuration changes event. Config change shouldn't require a reboot. Event handler sends the new config to kernel, stopping/restarting affected daemons, validate settings, etc. If it is easily replicable to do a config change that takes effect only after reboot, just file a new bug or contact support. Rebooting also clear the session states and will disrupt client/server connections.
In my case, the config didn't change, it's just that the bindings couldn't be seen. After the reboot, there were still no longer any bindings (even though there weren't prior either) and the GUI then showed zero and I was able to remove the entry.
Bob - self proclaimed posting junkie!
See my Fortigate related scripts at: http://fortigate.camerabob.com
OP might need to upgrade off that version. I never seen this behavior in all of years btw
PCNSE
NSE
StrongSwan
I did have the same experience rwpatterson had in the past at least a couple of times even with the modern versions like v5.x. I think it's related to some certain operations/changes like deletion of referred objects and re-naming some objects before deletion, etc. mainly by error, and subsequent action of corrections. It's difficult to replicate unless you're a software tester.
Hello,
Check your dashboard (for all your admin user). It doesn't appear in CLI !
Perform a backup and search Inet992
Lucas
Hi!
After a reboot, everything looks good!
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 |
---|---|
1641 | |
1069 | |
751 | |
443 | |
210 |
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.