Ten48

Comments

  • To find the correct OID, I did a MIB walk on a couple devices and just browsed through the Cisco env (environmental) MIB. I also set up a test 2811 I had laying around to send traps to Orion and opened up the case and yanked off the cooling fan power cable to verify that the fan failure OID I was the one I was the one I…
  • *bump* Has anyone figured out how to do this? This is a statistic I need to be able to report on for my Management Objectives which directly influence my bonus! ;)
  • Off topic from the original post, which I think I finally just gave up on, but to get BGP prefixes, poll for OID 1.3.6.1.4.1.9.9.187.1.2.4.1.1, name it cbgpPeerAcceptedPrefixes and set the MIB value type to Raw Value. The create an alert where the trigger condition is: "Poller Name is equal to cbgpPeerAcceptedPrefixes" and…
  • Really? Nothing? No one is doing alerts on Transform pollers? I guess I'm going to have to just configure a bunch of dumb'd down alerts for each UPS.
  • I believe that most (all?) Cisco devices can be configured to send a trap when temperature exceeds a threshold. That threshold is set by default on the device, but can be changed if you wish. So rather than trying to set up a temperature alert on pollers, it might be easier to set up an alert based on received the…
  • Update: I've created another alert based on a regular UnDP poller (as opposed to a UnDP Transform Poller as mentioned above) so I know it can be real easy. I have a poller now that is checking on BGP peers and prefixes and am alerting if the number of prefixes drops below a certain amount. We've had instances were our MPLS…
  • I agree that this feature is badly needed. I accidentally added some devices of which I don't want to monitor the ports and there's no way to remove them from UDT. They now show up on reports and they shouldn't. Also, it would be nice for the discover ports page to be able to group the list of the devices by location like…