Ghost Policy!

[Jon_Dyke]

Has anyone ever had any issues with a 'ghost' policy?

What I mean by this is that we has a set of GW's that became redundant (powered down).  We deleted the policy that was associated with them but when we try to get rid of the GW's (and Cluster) they refuse to delete saying they are in use by objects - when you do a where used its referencing the policy that no longer exists!

Any suggestions welcome.

[PhoneBoy]

What version/patch level?

You may be able to delete the objects with the API and/or dbedit depending on the version. 

[Jon_Dyke]

R80.10 Jumbo Hotfix 112

[PhoneBoy]

See if you can delete one of the gateways with something like (from CLI of management): mgmt_cli -r true delete simple-gateway name gwname

The cluster, not being a simple-gateway object, will probably have to be deleted with dbedit.

Something like: delete network_objects clustername

[Jon_Dyke]

If I go into the cluster oand do a remove under cluster members, what is get is xxxx is used by another object and cannot be deleted.  If I then click where used?  I get a list of objects.  The Names are all rule names and the table is rule_base.  But I know for a fact that they are not associated with any of my three current policies and that these references are referring to a policy that was deleted.

I will try from the CLI and see what I get.

Jon

[Maarten_Sjouw]

I can only advise you to get TAC involved and get them to involve development, as these are just the type of problems we had and needed the involvement of R&D to get them resolved.

[Jon_Dyke]

TAC managed to solve this but it took some effort to remove orphaned entries from the database tables!

Thanks for Advice

Jon