Forum Discussion
smp_86112
Cirrostratus
Cirrostratusnode definition in v9 bigip.conf
I suddenly noticed today, for the first time, that the number of node definitions in my v9.3.1 bigip.conf file does not match the number reflected in the Configuration Utilty - I have many more nodes showing in the Configuration Utility.
While I did find something close, relating to the OTCU during a v4 -> v9 migration (https://support.f5.com/kb/en-us/pro...ml1013812), I didn't find anything addressing this specific question. I wasn't involved with F5 back in the v4 days, so maybe the node definitions are left over from that migration?
Can someone clarify if/how nodes are normally reflected in a v9 bigip.conf versus the Config Utility? It seems they are all reflected in a v10 bigip.conf.
Michael_YatesNimbostratus
I noticed the same thing a long time ago on my v9.x.x LTM's, but haven't actually migrated enough to my v10 to know if they are different.
Unless you have implemented Administrative Domains and Partitions on your LTM, then it won't make a difference if the node does not appear in the bigip.conf's node list.
The node(s) list created in the Configuration Utility is a list of specifically entered nodes (that appear in the bigip.conf) and the members of all of the pools listed in the bigip.conf.
It becomes important in Administrative Domains and Partitions because nodes not specifically placed in a partition will be "put there" during the configuation load of the F5. This becomes a problem if Pools in different partitions attempt to use the same servers (which violates the boundary limits of ADP (Partitions can only share resources within the same Partition or the Common Partition)).
In these cases you must specifically create the "shared servers" in the Common Partition for use by all Partitions. Doing this specifically causes an entry into the bigip.conf.
Naming a server in the Nodes area so that its name appears next tothe IP Address in the Pool Members view, also creates and entry into the bigip.conf.