Forum Discussion

Scott_79627's avatar
Scott_79627
Icon for Nimbostratus rankNimbostratus
Jun 09, 2010

BIG IP VE in standby

I had an interesting encounter with the VE. I was using a version on VM Server to study for the essentials test so I changed the configuration to redundant and put a bogus IP address in as the peer. My only purpose was to view the connection mirroring and other redundant related buttons and configurations for studying. Interestingly, the VE went into standby mode even though there was not actually a redundant pair. Has any one else seen this? I am wondering if this is a bug.

 

 

Scott
ve
virtualization

5 Replies

Sort By
  • hooleylist's avatar
    hooleylist
    Icon for Cirrostratus rankCirrostratus
    Jun 09, 2010
    Hi Scott,

     

     

    There might be a failure condition which would prevent the unit from going active. If you run 'b ha table' do you see any of the Active column entries set to yes?

     

     

    Aaron
  • offset_68718's avatar
    offset_68718
    Historic F5 Account
    Jun 10, 2010
    Did it stay in standby? Sometimes a system will transition through a few states before it goes active again. Large config or licensing changes will do this.

     

     

    Was this the 10.1.0 trial VE or 10.2.0?
  • qe_102628's avatar
    qe_102628
    Icon for Nimbostratus rankNimbostratus
    Jun 10, 2010
    This is a bug in the VE Trial of 10.1.0.

     

     

    Here's a work around to force the unit to Active:

     

    1) Set the redundancy state preference to "Active" on System->High Availability->Redundancy

     

     

    2) Click update, and the node will go Active.

     

     

  • qe_102628's avatar
    qe_102628
    Icon for Nimbostratus rankNimbostratus
    Jun 11, 2010
    If you want to use HA pairs with the LTM VE Trial, you'll need to do this on each unit at the command prompt:

     

    "b db failover.usetty01 disable"

     

     

    (this issue does not affect 10.2.0 or later - it's limited in scope to the LTM VE Trial of BIG-IP 10.1.0)