For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Angelo_Turetta1's avatar
Angelo_Turetta1
Icon for Nimbostratus rankNimbostratus
Sep 04, 2014

Annoying bug on LTM nodes/pools list (11.5.1 HF4)

Hi all,   I just replaced our 11.2.1 8900 pair with a brand new pair of 11.5.1 7250v   I noticed a very repeatable bug on the web interface. I go to "Local traffic/Nodes" and click on the 'Addr...
application delivery
LTM
management
Jerry_Lees_4280's avatar
Jerry_Lees_4280
Historic F5 Account
Jan 21, 2015

Workaround (11.5.1 HF7, and probably others):

 

bigstart restart httpd tomcat

 

  • Misty_Spillers's avatar
    Misty_Spillers
    Icon for Nimbostratus rankNimbostratus
    Jan 26, 2015
    Can you fairly safely run this command during production hours? I'm having this problem on 11.5.1 HF7
  • Jerry_Lees_4280's avatar
    Jerry_Lees_4280
    Historic F5 Account
    Jan 26, 2015
    Yes, I believe so. It will cause the configuration manager to restart. So on a high traffic box it may be best to wait. However, it's as safe as most services you could restart.
  • Jerry_Lees_4280's avatar
    Jerry_Lees_4280
    Historic F5 Account
    Jan 26, 2015
    Also, Open a case please as shaggy says below.
  • Angelo_Turetta1's avatar
    Angelo_Turetta1
    Icon for Nimbostratus rankNimbostratus
    Feb 18, 2015
    Of course, this is no workaround at all. BTW, it solves the error because it resets node ordering. Much easier to restore the node ordering 'by name' yourself, with no need to potentially disrupt service.