Forum Discussion

jaikumar_f5_226's avatar
jaikumar_f5_226
Icon for Nimbostratus rankNimbostratus
Jan 27, 2018

Upgrade from 11.5.3 to 11.5.4 making unavailable object to offline

Hi all,

 

Can you share your thoughts on this. We upgraded an F5 from 11.5.3 to 11.5.4, the pre & post snapshots shows some differences. The difference is on the stats of network map. There were a couple of VS Unavailable with some Offline VS before change. But post upgrade, all of it moved from Unavailable VS Offline VS, making total same though. The available stats were same, so it was a relief. But why does the Unavailable & Offline vary post upgrade.

 

I'm yet to validate all other changes w.r.t pool member status (forced offline, offline)

 

LTM
security
TMOS

2 Replies

Sort By
  • boneyard's avatar
    boneyard
    Icon for MVP rankMVP
    Jan 27, 2018

    from my experience and the documentation the unavailable usually means connection limit reached.

    https://support.f5.com/csp/article/K14976

    https://support.f5.com/csp/article/K12213214

    yellow triangle status icon - The object is not currently available, but might become available later with no user intervention. For example, an object that has reached its configured connection limit might show a yellow status and then switch to a green status when the number of connections falls below the configured limit.

    why that would change to full down after an upgrade? kinda odd, perhaps a change in behaviour where in the past down virtual with too many requests could actually show yellow.

    release notes don't show anything.

    did you reboot before the upgrade and check status then?

  • jaikumar_f5's avatar
    jaikumar_f5
    Icon for MVP rankMVP
    Jan 29, 2018

    Before the upgrade we don't actually reboot. We always start with the Standby LTM, upgrade & reboot it. Perform failure and then do the upgrade on the other pair.

     

    But post upgrade I wasn't expecting the unavailable stats to clear on the new active LTM which was standby before. because of the connection mirroring.

     

    But why the objects moved to the unavailable state, which tells me those were supposed to be unavailable even before upgrade because the monitor would have failed and that is why its now showing as unavailable after upgrade.

     

    • Yellow triangle is about the connection limit & no user intervention is required.
    • Red Diamond is about the monitor marking the pool down, user actions are required.