Forum Discussion

Guillaume_Roman's avatar
Guillaume_Roman
Icon for Cirrus rankCirrus
Mar 22, 2015
Solved

BigSuds: Different status on LocalLB.Pool.get_member_monitor_status

Hello,   I have a problem when I get status of members from pools.   Environment: A vcmp instance (BIG-IP 11.4.1 Build 675.0 Hotfix HF7) 2 pools: pool_test_01 and pool_test_02, with http moni...
application delivery
devops
iControl
LTM
management
  • mhite_60883's avatar
    mhite_60883
    Mar 23, 2015

    Try this:

     

    LocalLB.Pool.get_member_monitor_status(['pool_test_01', 'pool_test_02'], [[{'address': 'node001', 'port': 80}],[{'address': 'node001', 'port': 80}]])

     

osnetworks_6668's avatar
osnetworks_6668
Icon for Nimbostratus rankNimbostratus
Mar 26, 2015

Just one more thought: When you specify 2 pools and one member, I would expect two results i.e. pool1+member1, pool2+member1. Similarly, when you specify two pools and two members (even if it's the same member repeated), I would expect 4 results i.e. pool1+member1, pool1+member2, pool2+member1, pool2+member2 so all your results appear to me to show the correct number of results.

 

I think your last example shows the correct output, however, the other results you are getting look inconsistent with what you would expect. One theory I have for this is that perhaps you left the default setting for "State Options" of "Apply new state to all pool member instances" enabled if you happened to be changing the State in-between tests? Annoyingly, this option only appears once you make select a different State radio button. Could this be the cause?