Forum Discussion
BIG-IP LTM VE config sync failure
- Aug 27, 2024
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.
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.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com