Running DFM 3.2.0 under LMS 3.2 for Windows 2003 Server Enterprise.
DFM has been pretty good about detecting power supply failures but recently I came across one power supply failure it didn't detect. This was on a 4506 running cat4500-ipbasek9-mz.122-53.SG.bin. Could there be a bug in detection of power supply failures with this firmware version?
Also, polling for power supply failures a configurable option in DFM?
SNMPv2-SMI::enterprises.22.214.171.124.126.96.36.199 = STRING: "Power Supply 1"
SNMPv2-SMI::enterprises.188.8.131.52.184.108.40.206 = STRING: "Power Supply 2"
SNMPv2-SMI::enterprises.220.127.116.11.18.104.22.168 = INTEGER: 1
SNMPv2-SMI::enterprises.22.214.171.124.126.96.36.199 = INTEGER: 6
SNMPv2-SMI::enterprises.188.8.131.52.184.108.40.206 = INTEGER: 2
SNMPv2-SMI::enterprises.220.127.116.11.18.104.22.168 = INTEGER: 2
It does appear DFM should have detected this. Power Supply 2 is clearly not functioning. Does the DFM Detailed Device View show PS2 as being found and managed?
Yes, the device is known in DFM (I did a re-import just in case)
Device Status = Known
Device Type = Switches and Hubs
Aliases = N/A
Containments = N/A
DFM Processing = Active
Time Last Discovered = 01-Feb-2010 12:28:43
Import Time Stamp = 01-Feb-2010 12:19:56
*** Data Collector Status Information ***
Error Code = N/A
Error Message = N/A
The power supply condition isn't reflected in the alerts.
Could it be that if the power supply is off to begin with when it does it's discovery, it doesn't register an alarm?
What does the Detailed Device View show for this switch? DFM may be ignoring it since its state is not functioning, and not "critical."
Hello, you can see my answer about this problem, i have a case open, the cisco TAC think the avaibility of the patch is September.
We have the same problem, no trap is coming into the LMS when we turn off a power supply of a 4500. What's the status on that? any solution?