Hi,

I would first recommend ensuring the System BIOS and ESM Firmware are at the latest revision. This resolves many of these borderline voltage issues. I wouls also recommend the latest version of Dell OpenManage Server Administrator.

System BIOS, PowerEdge 1650, A10
FileName:  PE1650-BIOSA10.EXE [569 KB]
Release Date:  5/28/2003
http://support.dell.com/FileLib/Format.aspx?ReleaseID=R60452

Dell ESM Firmware, PowerEdge 1650, A27
FileName:  PE1650-ESMA27.exe [226 KB]
Release Date:  5/30/2003
http://support.dell.com/FileLib/Format.aspx?ReleaseID=R60478

Dell OpenManage Server Administrator, 2000, 2003, v.1.4, A03
FileName:  om34_win_managed_system_A03.exe [137 MB]
Release Date:  6/2/2003
http://support.dell.com/FileLib/Format.aspx?ReleaseID=R61476

Server Administrator Documentation:
http://docs.us.dell.com/docs/software/svradmin/1.4/en/index.htm

Hi,

I have the same problem over here, but I'm going to add on to this, 'cause we don't know if the recommendations fixed the problem or not (I suspect it did, but it'd be nice to know!).  Anyways so here it is:

OMSA Version: 1.5.0

BIOS: A10

BMC:1.71

PB:1.01

Running W2kServer SP3

In OMSA there's also Sensor Data Records which is at version 0.33 (part of ESM_A27 upgrade, it looks like)

I still get the 2.5 V warning & Failure on a daily basis....

Thanks in advance for any help you can provide.

SiD

Well, the CPU Voltage sensor problem is wierd and I really don't know why Dell can't fix it even with the latest BIOS/ESM/OMSA.

I've three 1650, all running BIOS A10, BMC 1.71, SDR 0.33, and OMSA 1.5A01.

Only one of them has the CPU Voltage Error on the second CPU! I think the problem source is not the voltage reading, but the threshold setting!

  
        Warning Threshold  Failure Threshold
Status  Probe Name  Reading  Minimum  Maximum  Minimum  Maximum
            
  CPU  1.483 V  1.277 V  1.612 V  1.251 V  1.651 V
  CPU 2  1.509 V  1.573 V  1.702 V  1.560 V  1.728 V 
 

Just don't know why the Min/Max Failure Threshold for the CPU and CPU2 could be so different. They are same in the other two normal 1650 servers!

Just found the solution to the incorrect CPU voltage thresholds problem.

Shutdown the system. Unplug all the powers. Restart. The voltage threshold set back to normal.

Is the problem related to ESM/SDR?

Thanks for the follow up!

I'm glad it worked for you, but it didn't solve anything on my end since it's not CPU voltage warnings I get.  But I gave it a shot anyways, a good reboot doesn't hurt.

I configured another 1650 this week and I have the same problem...well almost.  The difference is the read voltage on battery is 0.696 instead of the usual 2.528 on the former.   The way I see it now, is that the next server I'll setup, should read below 0   Kinda scary, but it'll fit with the winter weather at least !  

You should always see the good side of things my mom used to say

 Hopefully some bright mind will Illuminate me one day.

SiD