Has anybody else enabled the built-in alerts for Switch Stacks in NPM 12? I've noticed that we're getting false positive stack member number change and stack master change alerts on switch stacks located in remote sites with poor WAN connectivity for monitoring. My hunch is that the 'stack member number changed' and 'stack master changed' values are not staying consistent when a polling cycle is missed or incomplete. Most of the poorly connected sites (India and China) actually aren't even stacks, they're just stackable switches in a stack of '1', so I know the member number or master status isn't actually changing. I've checked the switch logs as well and don't see any interruptions or reboots occurring, merely the WAN link being lossy enough that polling failed. I did have one actual 3 member stack in a better-connected Italy site have a brief WAN interruption that caused the same alerts. The stack itself has no indication that any of the 3 members changed state, and all 3 member uptimes are the same 3 months. All 3 members have configured member number and priorities as well. All the change alerts come in pairs in the same minute, so the values in NPM are always what they were before the alerts triggered by the time I can look.
I'm suspecting the Solarwinds database might be recording a null or something when a stack member value can't be polled which triggers the false alert? It's so quick though I can't catch what value is going into the database when the alert triggers.
Here's the sequence of events as seen on one switch:
