Forum Discussion
- BinaryCanary_19Historic F5 Account
it generally suggests that a configuration file is corrupt/unparseable. If you have a backup of your configuration, restore it and start again. Otherwise, you may have to fiddle with the bigip.conf file until you find where the problem is and correct it.
- What_Lies_Bene1Cirrostratus
Seems to be a known issue with this version of TMOS, see here: https://devcentral.f5.com/questions/annoying-bug-on-ltm-nodes-pools-list-1151-hf4. I'd suggest a call to support.
- omar05_132659Nimbostratus
Hello friends,
Thanks a lot for answering.
I have had lot of issues with this version. This issue has had the less impact due to I just open the GUI after a period of time and from another browser. The issue has not appeared since such date. But, I supposed I have to be ready when it appears again. Thanks a lot for the information.
Thanks
- Nick_T_68319Nimbostratus
I have the same issue
- Jerry_Lees_4280Historic F5 Account
Workaround (11.5.1 HF7, and probably others):
bigstart restart httpd tomcat
(But definitely still call and report a case.)
- Bob_Lyons_14865Nimbostratus
Please be aware this is also happening in 11.5.2 Hotfix 1. I have opened a case as well, but re-sorting the Nodes does correct this issue.
- JGCumulonimbusWhere and how did you resort the nodes?
- JGCumulonimbusOK I know now from the other thread you posted in.
- LeighLl_176246NimbostratusHow do you re-sort the nodes? I can't find your other post.
- elvis_chavez_18Nimbostratus
thanks, it working