changing memeber priorty - gtm

GTM pools are quite different to LTM pools and as such there is no direct "priority" attribute associated with each pool member. There is an "order" attribute however that you can assign to each pool member which will affect the weighting based on which LB method you are using.

If you want to send traffic to "pool1" in preference to "pool2" but have traffic go to pool2 in the case where all members of pool1 fail or at capacity then you could define two seperate GTM pools and set the LB method to "global availablity" for the wideIP. Then define pool1 with "order 0" and pool2 with "order 1". This will then give pool1 the more preferred priority.

You can do the same thing at the GTM pool level as well (e.g. if you just want to define a single GTM pool for your wideIP). In this case set the GTM pool preferred LB method to "global availability" and define the poolmember1 with "order 0" and poolmember2 with "order 1".

Now to answer your question. Assuming you did this at the pool level and you had a GTM pool called "gtmpool" using "global availability" with two pool members "gtmpoolmember1" (order 0) preferred over "gtmpoolmember2" (order 1), then the tmsh command to change the preference order would be:

modify gtm pool gtmpool members modify { /Common/bigip.domain.com:/Common/gtmpoolmember1 { order 1 } }

After running this gtmpoolmember1 will have order 1 and gtmpoolmember2 will have order 0. As a result gtmpoolmember2 will now be preferred.