Hello,
I might be the one not searching good enough, but I couldn't really find anywhere to put a feature request on Launchpad. As I've seen quite a few suggestions on stuff on this list, I might as well give it a shot here. One of many NAV features we've found handy, is the Module State warning feature. What I really don't understand, is why NAV haven't built in a PSU State warning system. There are numerous of MIBs under the CISCO-ENVMON-MIB http://tools.cisco.com/Support/SNMP/do/BrowseMIB.do?local=en&step=2&mibName=CISCO-ENVMON-MIB tree for this task. A Cisco specific MIB for the general PSU status would be "1.3.6.1.4.1.9.9.13.1.5.1", and would give you the following result on:
Cisco 65XX series:
SNMPv2-SMI::enterprises.9.9.13.1.5.1.2.1 = STRING: "Power Supply 1, WS-CAC-2500W" SNMPv2-SMI::enterprises.9.9.13.1.5.1.2.2 = STRING: "Power Supply 2, WS-CAC-2500W" SNMPv2-SMI::enterprises.9.9.13.1.5.1.3.1 = INTEGER: 1 SNMPv2-SMI::enterprises.9.9.13.1.5.1.3.2 = INTEGER: 1 SNMPv2-SMI::enterprises.9.9.13.1.5.1.4.1 = INTEGER: 2 SNMPv2-SMI::enterprises.9.9.13.1.5.1.4.2 = INTEGER: 2
Cisco 35XX series:
SNMPv2-SMI::enterprises.9.9.13.1.5.1.2.1003 = STRING: "Sw1, PS1 Normal, RPS NotExist" SNMPv2-SMI::enterprises.9.9.13.1.5.1.3.1003 = INTEGER: 1 SNMPv2-SMI::enterprises.9.9.13.1.5.1.4.1003 = INTEGER: 2
Cisco 45XX series:
SNMPv2-SMI::enterprises.9.9.13.1.5.1.2.1 = STRING: "Power Supply 1" SNMPv2-SMI::enterprises.9.9.13.1.5.1.2.2 = STRING: "Power Supply 2" SNMPv2-SMI::enterprises.9.9.13.1.5.1.3.1 = INTEGER: 1 SNMPv2-SMI::enterprises.9.9.13.1.5.1.3.2 = INTEGER: 1 SNMPv2-SMI::enterprises.9.9.13.1.5.1.4.1 = INTEGER: 2 SNMPv2-SMI::enterprises.9.9.13.1.5.1.4.2 = INTEGER: 2
The status integers for the power supply MIB are pretty much alike the Module State warning integers, so implementing such a feature wouldn't be a big problem. And the graphical interface/warning would look pretty much the same as the Module State thing when browsing a device, or as a Power Supply failure on the Status page.. I don't know about others, but I like to get a warning when my power equipment fails, or we're having a power failure :)
Any thoughts?
------------------------------------------------------ Vidar Stokkenes Konsulent Nettverk Seksjon for nettverk og telekom HN IKT - Tromsø
Tlf: 76 16 61 87 / 77 66 99 55 Mobil: 95 87 99 42 e-post: vidar.stokkenes@hn-ikt.nomailto:vidar.stokkenes@hn-ikt.no [cid:image001.png@01C90F3D.BA283A30]
Hello,
Hi!
I might be the one not searching good enough, but I couldn't really find anywhere to put a feature request on Launchpad.
Feature request in Launchpad are made out of blueprints, so thats what you'd want to register. We can then track the feature request, and maybe later promote it and register it against a milestone.
Have a fantastic day!
- Kristian
On Fri, 5 Sep 2008 11:09:10 +0200 Kristian Klette kristian.klette@uninett.no wrote:
I might be the one not searching good enough, but I couldn't really find anywhere to put a feature request on Launchpad.
Feature request in Launchpad are made out of blueprints, so thats what you'd want to register. We can then track the feature request, and maybe later promote it and register it against a milestone.
If you are unable to post a meaningful blueprint, I guess you could also post it as a bug. We would set wishlist priority on it, and if we decide to to anything about it, we'll make our own blueprint.
But then again, Kristian knows his way around Launchpad better than me so far :)
On Fri, 5 Sep 2008 10:04:49 +0200 Stokkenes Vidar Vidar.Stokkenes@hn-ikt.no wrote:
One of many NAV features we've found handy, is the Module State warning feature. What I really don't understand, is why NAV haven't built in a PSU State warning system. There are numerous of MIBs under the CISCO-ENVMON-MIB http://tools.cisco.com/Support/SNMP/do/BrowseMIB.do?local=en&step=2&mibName=CISCO-ENVMON-MIB tree for this task. A Cisco specific MIB for the general PSU status would be "1.3.6.1.4.1.9.9.13.1.5.1", and would give you the following result on:
Hi Vidar,
For the sake of clarity, the CISCO-ENVMON-MIB is _one_ MIB. "1.3.6.1.4.1.9.9.13.1.5.1" is an object identifier (OID) defined in that MIB, and holds one entry in the ciscoEnvMonSupplyStatusTable.
While your suggestion is a good one, you're not the first to suggest PSU monitoring. NTNU have actually implemented their own quick-and-dirty way of doing this. By quick-and-dirty, I mean it bypasses NAV's event- and alert system.
It only uses NAV to find the list of devices to poll, but it's a proof-of-concept which we are considering for proper implementation in NAV when the new polling engine is finished.
I read it again now, and it's a result of copy/pasting some test I wrote in a .doc file earlier. I was intending to refer to the CISCO-ENVMON-MIB and the Cisco specific OID.
I've considered attempting to the same, only using snmptrapd.py, but I have no idea how I would proceed to make it show in NAV.. That's why I'd appreciate if someone more qualified and with more insight could take a look at it, and implement this long sought-after feature. Posted on LP Blueprints for NAV btw.
-Vidar
-----Opprinnelig melding----- Fra: Morten Brekkevold [mailto:morten.brekkevold@uninett.no] Sendt: 5. september 2008 11:34 Til: nav-users@uninett.no Kopi: Stokkenes Vidar Emne: Re: Feature request hidden in Launchpad?
On Fri, 5 Sep 2008 10:04:49 +0200 Stokkenes Vidar Vidar.Stokkenes@hn-ikt.no wrote:
One of many NAV features we've found handy, is the Module State warning feature. What I really don't understand, is why NAV haven't built in a PSU State warning system. There are numerous of MIBs under the CISCO-ENVMON-MIB http://tools.cisco.com/Support/SNMP/do/BrowseMIB.do?local=en&step=2&mibName=CISCO-ENVMON-MIB tree for this task. A Cisco specific MIB for the general PSU status would be "1.3.6.1.4.1.9.9.13.1.5.1", and would give you the following result on:
Hi Vidar,
For the sake of clarity, the CISCO-ENVMON-MIB is _one_ MIB. "1.3.6.1.4.1.9.9.13.1.5.1" is an object identifier (OID) defined in that MIB, and holds one entry in the ciscoEnvMonSupplyStatusTable.
While your suggestion is a good one, you're not the first to suggest PSU monitoring. NTNU have actually implemented their own quick-and-dirty way of doing this. By quick-and-dirty, I mean it bypasses NAV's event- and alert system.
It only uses NAV to find the list of devices to poll, but it's a proof-of-concept which we are considering for proper implementation in NAV when the new polling engine is finished.
-- mvh Morten Brekkevold UNINETT
-
Kristian Klette -
Morten Brekkevold -
Stokkenes Vidar