ansible bigip_pool_member intermittently not adding member to pool
We have an ansible script that we are using to move nodes in and out of pools for testing that intermittently refuses to add the pool member thinking we are trying to add it to the root folder. The issue is that the failures are now happening almost every time, despite no changes to the script and no recent changes to our F5. Verbose mode shows it has the correct partition, but somehow that partition info is not being read or taken in properly. Thanks in advance for any help. ansible version 1.9.1 (and stuck on this version for a while) Here's what we see when running the playbook: TASK: [enable new nodes on external checkout pool] **************************** <127.0.0.1> REMOTE_MODULE bigip_pool_member server=10.10.10.10 user=myuser password=VALUE_HIDDEN state=present pool=EXTERNAL_CHECKOUT_POOL **partition=WEB-GENERAL-CORE** host=MYHOST14 port=2180 <127.0.0.1> EXEC ['/bin/bash', '-c', 'mkdir -p $HOME/.ansible/tmp/ansible-tmp-1457566442.5-241342532701996 && chmod a+rx $HOME/.ansible/tmp/ansible-tmp-1457566442.5-241342532701996 && echo $HOME/.ansible/tmp/ansible-tmp-1457566442.5-241342532701996'] <127.0.0.1> PUT /tmp/tmp59N5mT TO /home/myuser/.ansible/tmp/ansible-tmp-1457566442.5-241342532701996/bigip_pool_member <127.0.0.1> EXEC ['/bin/bash', '-c', u'LANG=C LC_CTYPE=C /usr/bin/python /home/myuser/.ansible/tmp/ansible-tmp-1457566442.5-241342532701996/bigip_pool_member; rm -rf /home/myuser/.ansible/tmp/ansible-tmp-1457566442.5-241342532701996/ >/dev/null 2>&1'] failed: [localhost -> 127.0.0.1] => (item=MYHOST14) => {"failed": true, "item": "MYHOST14"} msg: received exception: Server raised fault: 'Exception caught in LocalLB::urn:iControl:LocalLB/Pool::add_member_v2() Exception: Common::OperationFailed primary_error_code : 17241203 (0x01071473) secondary_error_code : 0 error_string : 01071473:3: Create, modify, and delete commands are not valid for (by class: pool_member) while in the root folder.' FATAL: all hosts have already failed -- aborting
iRule to redirect application to pool and change url
When setting up a f5 irule, I am trying to do the following: When an external url is hit, redirect to an internal pool of servers based on a url. Example: external= I want this to map to server pool of urls: server1.com:8080/application or server2.com:8080/application or server3.com:8080/application I need it to only direct if the server url is up. Does anyone have an idea? Basicly going to ww.abc.com/test redirect/proxies to server2.com:8080/application/test. and redirect/proxies to server2.com:8080/application. This is what I have so far: when HTTP_REQUEST { switch -glob [string tolower [HTTP::path]] { "/application*" { pool This_abc.com_WEB-R_8080 snatpool WEB-R_SNAT_Pool } } }
Assign an Existing Node to Pool in F5 BIG IP through F5-SDK
Is there any way to assign a node that already exists in the Common partition to a pool that also already exists? For example: Call pool and node pool = bigip.tm.ltm.pools.pool.load(name="mypool", partition='Common') node = bigip.tm.ltm.nodes.node.load(name="mynode", partition='Common') First Option pool.members_s.members.create(name=node.name, partition="Common") pool.update() Second Option pool.members_s.members[0] = node I don't know if the code is exactly correct, thanks in advanceManaging Multiple GTM & LTM Pool Members Over iControl REST
Currently, I have automation that manages pool member states in series. It will be trivial to work through a list of members that I might want to enable or disable programmatically, but I wonder if it's possible to pass a list in my request to the API. Is it possible to enable or disable more than one pool member with a single call? Thanks.
VIP is not accessible but direct servers are reachable
I have a scenario where the VIP is not reachable but the pool members are reachable. My virtual server is 10.1.130.100:5003, my pool members are 10.1.130.83:5003,10.1.130.85:5003,10.1.130.87:5003,10.1.130.89:5003. I created an iapp based on Weblogic for it,I have AUTOMAP enabled but the application owners insist,they can't access the VIP, but can access the individual pool members directly. What is the solution to this.
