Forum Discussion
NimbostratusWhat is the criteria used by iHealth to determine objects are "orphaned"
We are trying to clean up our systems as we will be making a lot of big changes over the next year. I am using iHealth to find all the orphaned objects but i would like to know what criteria iHealth uses to determine something is orphaned.
An example are nodes...
Does iHealth verify they are not in a pool and how far back does it go to confirm the node wasn't just removed from a pool?
How far back in time does iHealth look to confirm no traffic?
Does it look for the same IP being re-used with another name?
Does it confirm that the node is enable or disabled?
Before I start removing nodes, pools, etc. I'd like to know exactly what criteria was used to deem the object orphaned so I know what cross checks I need to complete to confirm I can delete it.
Nathan_F__F5_Employee
Hi Dominic,
Orphaned objects are simply objects that are not being referenced or used by any other traffic objects. For example, if a node is not part of a pool and is not being referenced by an iRule or any other traffic object then it would be considered orphaned since it is not in use. Another example would be an iRule that is not applied to any virtual servers. I do not believe iHealth checks anything related to traffic, other names (you shouldn't be able to create the same node with 2 different names without getting an error anyway), or whether or not a node is enabled or disabled. I believe it simply checks to see if it is in use or being referenced by any other traffic objects. We have an article that speaks a bit about this as well.
K15335: F5 recommends removing orphaned configuration objects
https://support.f5.com/csp/article/K15335
I hope this helps to answer your question.
-Nathan F