Forum Discussion
wl310
Nimbostratus
NimbostratusBIG-IP LTM VE config sync failure
Hello, running into an issue where our secondary F5 appliance is failing to sync its config from the primary appliance due to an "invalid node address, the IP address already exists" error. We've identified an auto generated node entry with what appears to be the offending IP address, however it cannot be deleted from the web UI.
Has anyone else run into this issue and if so, how did you resolve it? We found this article that describes how to delete generated FQDN nodes from the F5 command line but are unsure if this is a viable solution. If anyone has any insight into this, it would be much appreciated.
Hi WL310,
This error can be seen when you have FQDN ephemeral nodes auto populated with this IP address as your desired new node which you wish to create. Environment BIG-IP Configuring a node FQDN node Cause This is expected behavior. Recommended Actions To configure new node which would have same IP address as auto_X.X.X.X FQDN node, you'll need to delete this FQDN first. It's not possible to configure node when same IP address node already exist.
To configure new node which would have same IP address as auto_X.X.X.X FQDN node, you'll need to delete this FQDN first. It's not possible to configure node when same IP address node already exist.
In rare circumstances, after deleting FQDN node, its ephemeral counterpart will still remain in configuration disallowing to create new node with this IP address.
Normally after deleting the template FQDN nodes, the ephemeral ones should be removed automatically.
If not, then after deleting the template nodes and if the ephemeral nodes still exists then you can try to remove them with the following command:
tmsh delete ltm node _auto_<address>
eg.
tmsh delete ltm node _auto_192.0.2.41https://my.f5.com/manage/s/article/K11093282
HTH
If this resolve your issue , kindly rate.
wl310Thank you for your help. We were able to successfully sync the config from our primary appliance to the secondary after manually deleting the auto generated node.
Take a UCS backup before and then delete, and the ephermeral _auto_<address> node on the secondary appliance, sync in case if issue happens, you can restore from your USC for quick healing.
- wl310
Hi, thank you for the quick response. The FQDN node on our primary F5 appliance needs to remain. Would it be safe to just delete the ephermeral _auto_<address> node on the secondary appliance without deleting the FQDN node on the primary and then syncing the primary appliance's config to the secondary via the web UI?
Hi WL310,
This error can be seen when you have FQDN ephemeral nodes auto populated with this IP address as your desired new node which you wish to create. Environment BIG-IP Configuring a node FQDN node Cause This is expected behavior. Recommended Actions To configure new node which would have same IP address as auto_X.X.X.X FQDN node, you'll need to delete this FQDN first. It's not possible to configure node when same IP address node already exist.
To configure new node which would have same IP address as auto_X.X.X.X FQDN node, you'll need to delete this FQDN first. It's not possible to configure node when same IP address node already exist.
In rare circumstances, after deleting FQDN node, its ephemeral counterpart will still remain in configuration disallowing to create new node with this IP address.
Normally after deleting the template FQDN nodes, the ephemeral ones should be removed automatically.
If not, then after deleting the template nodes and if the ephemeral nodes still exists then you can try to remove them with the following command:
tmsh delete ltm node _auto_<address>
eg.
tmsh delete ltm node _auto_192.0.2.41https://my.f5.com/manage/s/article/K11093282
HTH
If this resolve your issue , kindly rate.
