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.
Debbie_FTNT,
Thank you very much, I have tested the solution you provided, It is working. Thanks again.
Is this a typo? The second one is a different address object named "Terminal_192.0.132.1", with the same subnet (IP). They can coexist though.
In any case, no reboot is required for any address object changes. You should be able to remove the interface association by "unset associated-interface" under the original address object editting mode. You might need to take it out of policies if it's already used with other objects. After 6.2, you can't mix those objects with specific interface assiation and others without it on the same policy.
Toshi
Toshi,
Thank you very much for your reply.
Spot on, yes, it is a typo.
I have multiple "set associated-interface "xxx" commands in my config but I only need to remove one, will the "unset associated-interface" command remove all of them? As I only need to remove only one, can I use unset associated-interface "Terminal10" to remove this specify one instead? Thanks.
Hey yktee,
if you do this:
config firewall address
edit <object>
unset associated-interface
end
that will only remove the associated interface from this one object. The other objects will retain their associated interfaces.
Debbie_FTNT,
Thank you very much, I have tested the solution you provided, It is working. Thanks again.
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 |
---|---|
1640 | |
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.