Advanced alert for triggering on the status change of the Cisco OTV universal device poller I created, cotvOverlayVpnDownReason.UnDP
We use OTV to tie two mission critical data centers together.
But that means if OTV becomes inactive, the whole world comes down upon our shoulders. I hate to say it, but that's one heck of an "Inactive OTV" customer poller. It doesn't even need NPM to generate alerts to us.
;^)
Shoot, you'd think the data center had burned to the ground, each time OTV has an outage. Fortunately we don't do that anymore.
HAH! That's an awesome/SCARY pic!! Heaven forbid I ever see something like that in person!
In our case the OTV link provides internet access between our two datacenters. But each datacenter has its own internet access so this link is really only used in DR scenarios if one DC loses its internet.
Hi Ryan. I am looking to monitor our OTV status. We just found out is was down on one of our OTV VDCs and could have been for maybe a year or more but no way to detect that.
I found your UnDP on THWACK, and when I go to NPM Settings, Manage Pollers, THWACK Community Pollers, I can see it there, but when I try to import it, I get this error:
I also downloaded the alert you created and I have that imported into my alerts:
001Network_Cisco_OTV_Inactive.xml
But the alert seems to be dependent on the UnDP being loaded.
Any idea how I can get this working? I have never done UnDP's before.
Thanks,Rick
Ryan, actually, I think I got this working. Both the poller and the alert.
Awesome! Glad you got it to work!
