Forum Discussion
Bigip.conf manual reconfiguration issue
I'm sure I'm way too late to help you out, but this may help out another. I just ran into this exact issue editing the bigip.conf the same as you, in order to rename all of my nodes and pool members to a name rather than IP. I used a python script (2.4.3) and using fileinput() to rewrite the file inplace on a mac osX (not sure if these params have anything to do with the issue). The fileinput method re-writes every line of the file in place, and I changed what I need with a regex. The new file loaded just fine, but one could not disable/enable any pool members.
The fix for me was to delete the trailing space on line 1323 (which was also present in the original migrated bigip.conf), save the file, and reload it. Upon reloading, it also reformatted bigip.conf to still contain the space, yet my cli/UI error was gone. My error was at a node object on a line containing text "monitor /Common/icmp" and "monitor none" on two distinctly different F5s and on the exact same line of 1323. These two LTMs had completely different config. Odd to me that your problem was on 1324, and both of mine were on 1323. Seems odd this happening on two exact same lines for me, and the very next line for you. They have to be connected.
My error: modify ltm pool testpool-80 members modify {testnode:80 {session user-enabled state user-up }} 01070712:3: Caught configuration exception (0), Invalid monitor rule instance identifier: 5076 - ltm/validation/MonitorRule.cpp, line 1323.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com