Forum Discussion
nickamon
Nimbostratus
NimbostratusBig IP FQDN Pool Member Resolution from /etc/hosts
Hi, I've added entries to the Big IP /etc/hosts file to map custom FQDNs to IP addresses (in an attempt to workaround the restriction of having LTM nodes with the same address). I then created a...
nickamonNimbostratus
NimbostratusI'm working on migrating our manual configuration of the Big IP virtual servers/pools to an AS3-based automation solution. Our automation takes as input the required information to create a virtual server, pool and all our custom configuration. The problem is that we don't want to first delete the manual configuration, we want to have both configurations running side-by-side so we can test. We have been able to assign a unique VIP for the new configuration but the traffic is destined for the same destination as the manual configuration. When the automation attempts to create a new Pool object with the same members, we run into the error about duplicate nodes.
Using /etc/hosts was an attempt to create a custom FQDN that resolves to the same destination IP address of an existing node to workaround this restriction.
Hope this helps. Thanks!
boneyard
MVP
MVPAh, yeah that makes sense.
Not sure how side-by-side you want it, else a different BIG-IP might be a way. A lab or trial license might be enough.
Else you could look into route domains perhaps with partitions to make something work, but that will require some designing if you actually want to test with traffic.