This recommended read goes over the steps to localize an object within SFOS.
If you’re trying to delete an object within SFOS and it’s already in use, you have to localize the rules first and delete/edit those rules.In the case of complex setups, it can be complicated to localize all rules. The following UI error will occur:
"Host could not be deleted. Firewall rule exists for this host."
Doing a full export of the entire configuration under "Backup & firmware - Import export" gives you a XML File, which helps localize all config settings.
If you know the location of the config, you can export only firewall rules for example. If the usage is unknown to you, you can do a full export. Within the file is the "Entities.xml" file.With a standard text editor, you can localize all objects, using your object. The object itself:
A TLS Inspection rule using this object:
SMTP General Settings are using this as a Required TLS Host object:
One Firewall Rule is using this object as Source called "FirewallRule".
There is one NAT Rule using this object as Source Network.
This option is an easy way to do a "where is used" option if needed to delete it.
If everything‘s include in one single xml-file, adding this to WebAdmin shouldn‘t be such a challenging task? Like SG…
Generating a XML takes performance effort. This takes some time to get the XML in the first place. SFOS Webadmin does not have the XML present at any time.
Figuring out usage of multiple objects within an migration process or daily usage takes at least time effort (by manually searching xml files and webadmin once again after that). That‘s much more effort than performance impact on current hardware… in 2022…
We were able to have these information ready at any time in SG Firewall for years…