It would be extremely helpful to show the POE status of POE switch ports.
Given all my devices I'm worried about support the standard POWER-ETHERNET-MIB (Juniper, HP) here is my ideal of support:
1) NCM gathers the state of POE and stores it in its database, so that it can…
This would be great if it could maintain history on the provided power. I would love to see graphs that show "brownouts & drops" in provided power. Could be helpful in troubleshooting lockups and reboots…
Bumping from the grave. The OID 220.127.116.11.18.104.22.168.1.1.6 is confirmed working on the following models:
The OID description fails to mention that a value of '4' means you have a PoE controller failure for that port.
I see what you're saying. It sounds right--I'm accustomed to having to remote into a switch and issue a "show" command to find POE info.
However, I see these traps are available in my Cisco hardware:
snmp-server enable traps power-ethernet group 1
snmp-server enable traps power-ethernet group 2
snmp-server enable traps power-ethernet group 3
snmp-server enable traps power-ethernet group 4
snmp-server enable traps power-ethernet group 7
snmp-server enable traps power-ethernet group 8
snmp-server enable traps power-ethernet group 9
snmp-server enable traps power-ethernet group 10
snmp-server enable traps power-ethernet police
This document discusses them (these are from a Cisco 4510 with ten slots, 1-4 and 7-10 are Ethernet line card slots).
It would be nice to see SW leverage these, or for Cisco to develop traps that do as you wish.
traps only work when a device is added. I'm looking for information similar to vlan info on the interface. UDT simply lets me know int g2/0/22 is in vlan 230.
I would like to see a POE column that says the watts provided. This would mostly be 0 or null, and when there is a WAP or phone it could simply state the watts provided.
It sure seems like simply enabling traps on the switches would provide you the POE info you seek.
I wouldn't say "no" to POE graphics on NPM Nodes, either.
Sure, a person can build a job that issues a "show power inline" command, or even a "show int count err" and learn a ton of great info, but it would be convenient to see these types of things in UDT as long as a person is looking at a device they've searched for and found in UDT.
In my environment we run POE off switchports to VoIP phones, and PC's or TC's off those phones' internal mini switch ports.
How do you envision benefits that would help you do your jobs better if you saw POE info in UDT? What would it tell you, how would it reduce MTTI or troubleshooting time? (Maybe I can benefit from your thought process and get better info . . . or maybe I can help you find an alternative that may work for you until UDT does what you need.)
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK© online community. More than 180,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.