UNSOLVED

LeeatMEP

updated

22 years ago

L

LeeatMEP

4 Posts

0

25784

July 28th, 2004 10:00

PowerEdge 2450 - Status lights

Two lights on the front, one is for the MB condition and the second is for HD activity/cond.  My question is where do I go to find out why the MB Led is yellow?

  • DELL-Mark A

    2 Intern

    •

    2521 Posts

    472

    0

    Posted July 28th, 2004 11:00

    Hi,

    The "System Indicator light" blinks when the System Case is open or when there is a Fan Speed, Power (voltage or amperage), Temperature, Memory or PCI bus problem. Most commonly the case is open or a power supply is unplugged.

    I would recommend installing the latest System BIOS and ESM Firmware. Then install the Dell OpenManage Server Administrator, which will tell you exactly which device is causing the System status indicator to blink.

    System BIOS, PowerEdge 2450, A09
    FileName: 2450-A09.exe [485 KB]

    ESM Firmware, A42
    Filename: a42cust.exe (397 KB)
    Note: Extract the files to a DOS bootable floppy disk. Boot the server to this floppy disk, and run smflsh.exe.

    Dell OpenManage Server Administrator and Remote Install (Agent), 2000, 2003, v.1.8, A00
    FileName: om38_win_managed_systemA00.exe [194 MB]
  • LeeatMEP

    4 Posts

    472

    0

    Posted July 28th, 2004 18:00

    Thanks Mark.. it told me what the problem was..
  • DELL-Mark A

    2 Intern

    •

    2521 Posts

    472

    0

    Posted August 5th, 2004 15:00

    Hi JT,

    The readme file will describe the exact dependencies, depending on the system type, Perc controller, peripherals installed etc.

    In general you want the System BIOS, ESM Firmware, Perc firmware and driver and the ERA Firmware (as applicable) at the latest version.

    thanks
    Mark
  • jman1764

    12 Posts

    472

    0

    Posted August 5th, 2004 15:00

    Mark,

    I installed this application and it will not install the openmanage server admin because the dependency checks failed?

    What do i do to resolve that problem

     

    Thanks,

    JT

  • jman1764

    12 Posts

    472

    0

    Posted August 5th, 2004 17:00

    Got it working and have a low voltage reading on Scsi termination see log export:

     

    Voltage Probes Information : Critical

    Status;Probe Name;Reading;Minimum Warning Threshold;Maximum Warning Threshold;Minimum Failure Threshold;Maximum Failure Threshold
    Ok;Backplane +12V;11.812 V;11.520 V;12.480 V;11.400 V;12.600 V
    Ok;Backplane +3.3V;3.277 V;3.150 V;3.450 V;2.950 V;3.650 V
    Ok;Backplane +5V;4.940 V;4.750 V;5.250 V;4.500 V;5.500 V
    Ok;Motherboard +12V;11.801 V;11.520 V;12.480 V;11.400 V;12.600 V
    Ok;Motherboard +2.5V;2.506 V;2.400 V;2.600 V;2.375 V;2.625 V
    Ok;Motherboard +3.3V;3.241 V;3.168 V;3.432 V;3.135 V;3.465 V
    Ok;Motherboard +5V;4.946 V;4.800 V;5.200 V;4.750 V;5.250 V
    Ok;Motherboard Battery;2.935 V;2.430 V;3.900 V;2.400 V;4.000 V
    Ok;Motherboard GTL Termination;1.503 V;1.380 V;1.620 V;1.365 V;1.635 V
    Ok;Processor 1 core;1.737 V;1.600 V;1.800 V;1.580 V;1.820 V
    Ok;Processor 2 core;1.759 V;1.600 V;1.800 V;1.580 V;1.820 V
    Critical;SCSI A external termination;3.402 V;4.000 V;5.250 V;3.750 V;5.500 V

     

  • DELL-Mark A

    2 Intern

    •

    2521 Posts

    472

    0

    Posted August 6th, 2004 12:00

    Hi JT,

    This is probably a false voltage error, however these are the things I would do to confirm there is not a hardware issue contributing to the problem.

    1. Remove, Inspect and Reseat all the components of the SCSI subsystem. Cables going to and from the SCSI Backplane, hard drives, SCSI daughtercard(s) (mounted above the hard drives), Perc Key, Dimm and Battery connection.

    Backplane Documentation

    Make sure all the related drivers / firmware / software are at the latest revision. These are the required files, assuming a PowerEdge 2450 running Win2000 with a Perc 2/si installed:

    System BIOS, PowerEdge 2450, A09
    FileName: 2450-A09.exe [485 KB]

    ESM Firmware, A42
    Filename: a42cust.exe (397 KB)
    Note: Extract the files to a DOS bootable floppy disk. Boot the server to this floppy disk, and run smflsh.exe.

    Adaptec Perc 2/si, 2/qc, 3/si, 3/di, Driver, Windows 2000, v.2.8.0.6085, A15
    FileName: W2K-2806085.exe [259 KB]

    Adaptec Perc 2/si, Firmware, PowerEdge 2400, v.2.8.0.6089, A12
    FileName: PE2400-280_6089.exe [1 MB]

    Dell OpenManage Server Administrator and Remote Install (Agent), 2000, 2003, v.1.8, A00
    FileName: om38_win_managed_systemA00.exe [194 MB]
  • BryanMCI

    21 Posts

    472

    0

    Posted August 26th, 2004 22:00

    I just downloaded this Server Administrator program, and attempted to Install it on my Dell Poweredge 2400.  (Service Tag 47PKD01).  Just as with any other OpenManage program that I've tried to install, this one fails as well.

    The setup screen gets to 40%....sometimes even 50%....then just sits there while I pull my hair and the owners of the company continue to pay while I sit and pull out my hair. :)

    Is there an "OpenManage" Suite in particular I should be installing?  Is there one that actually works?  Even the CD that came with our servers has problems.  It's quite tough to manage arrays, monitor temperature, etc when the software doesn't work. 

    Any help would be greatly appreciated, and my apologies for my frustration.

  • MichelleT

    2 Intern

    •

    127 Posts

    472

    0

    Posted August 27th, 2004 13:00

    OpenManage version 3.8 is fine for a 2400/2450.  If the install is hanging, please check your dcom permissions.  Go to Start->Run and type dcomcnfg.  If you are running W2k the DCOM properties window will open.  If you are running W2K3, you will need to expand component services, computers and then right click on My Computer to navigate to the properties window.  Please make sure the Authentication level is set to Connect and the Impersonation is set to Identify.  Then navigate to the Default Com Security tab and check that the user that you are logged in with is explicitly listed with Allow permissions on both the Access and Launch buttons.  If you are prompted to record any CLSIDs when DCOM first opens, please do so.

    If you are still unable to install, please check the temp directory for an ominstall.log, omprog and omstatus.log that might indicate the reason for the failures.  If you would like to install Array Manager, verify that the driver (first) and the firmware for the Perc controller are at the most recent versions.  These updates can be downloaded from http://support.dell.com.

    If you are still encountering difficulty, please reply with any additional specific error messages or information.

  • MichelleT

    2 Intern

    •

    127 Posts

    85

    0

    Posted August 27th, 2004 14:00

    Here are a few tasks that might help you.

    1) Please make sure that you have full control of c:\temp. 

    2) Check for any local or group policies that could be preventing an installation. 

    3) If you are running W2K make sure the Windows Installer service is started. 

    4) Navigate to the c:\program files\common files\installshield directory and delete the engine folder.  A new engine will be installed when you attempt to install Server Administrator.

    I hope that this information is helpful!

  • BryanMCI

    21 Posts

    472

    0

    Posted August 27th, 2004 14:00

    Added the administrators groups for both the domain and local computer to the Launch area of DCOM.  Everything else was set as explained. 

    Ran the install, and suprise.....stuck at 40%.

    Searched for log files, no such files exist.

    Any other hints?