Forum Discussion
Joel_Bowman_414
Nimbostratus
NimbostratusBigip.conf manual reconfiguration issue
The end game is to rename all 100 nodes from IP to server name. So I manipulated the bigip.conf changing the node name and the pool reference for node name. Verified the file and then loaded the conf...
Tarmo_Mamers_63Nimbostratus
NimbostratusLine numbers in the messages
... - ltm/validation/monitorRule.cpp,line 1324
... - ltm/validation/MonitorRule.cpp, line 1323
refer to lines in the TMOS source code (the messages show a source file name and line number which caused the message). The numbers may be different in each user's case as the software versions (builds) might differ. Source line numbers are useful only to F5 engineering, when the eventual support case might get to their attention. Unless you have the TMOS source code :P
The source code line numbers have nothing to do with the configuration file entries.
Those numbers should refer to the bigip.conf lines:
Invalid monitor rule instance identifier:6258
Invalid monitor rule instance identifier: 5076
Cheers
-tarmo-
hoffman_54262I can confirm this did fix my issue (Running tmsh load sys config twice) did fix this issue. I'm not sure why, it would be nice to know.