Forum Discussion
James_Thomson
Employee
Aug 24, 2015Currently, members in a pool are all in the pool object and not by themselves in a sub-collection. Because of this, you'll want to read in the current pool definition, then send the whole thing back in with the edits you want to make. What you have to realize is that you're patching the whole Pool to this new state. I believe F5 in version 12 was going to change pool members to a sub-collection which would allow you to patch a member individually. I have not found a way around this yet.
- Andrew_Le_12873Aug 27, 2015
Nimbostratus
Yes, in BIG-IP version 12.0, ltm pool members will become a sub-collection. Here's an excerpt: { "items": [ { "allowNat": "yes", "allowSnat": "yes", "fullPath": "/Common/P1", "generation": 496, "ignorePersistedWeight": "disabled", "ipTosToClient": "pass-through", "ipTosToServer": "pass-through", "kind": "tm:ltm:pool:poolstate", "linkQosToClient": "pass-through", "linkQosToServer": "pass-through", "loadBalancingMode": "round-robin", "membersReference": { "isSubcollection": true, "link": "https://localhost/mgmt/tm/ltm/pool/~Common~P1/members?ver=12.0.0" }, ....