Forum Discussion
ringoseagull_77
Aug 10, 2010Nimbostratus
Thanks Aaron.
The monitors were configured to use * and the nodes were set to take their monitoring method from the pool, so i guess that's what caused this.
I'm at a bit of a loss as to why those monitors were working for one or two years, I didn't think they'd load at all. I'll have to configure new monitors with specific ports.
We've had some serious issues from this. All our sites suffered intermittent loss of service, which we narrowed down to servers at one data centre. Although I'd forced the upgraded F5 offline and disabled its interfaces the active F5 was still trying to contact it every second. It wasn't until I shut down the upgraded F5 that the active box knew it was alone and started doing all of the work.
I imagine I'll now have to isolate the upgraded F5 from the network, create the new monitors, then shut down the active box to test it out when I can get some more downtime.