TheSaffaGeek

My ramblings about all things technical


Leave a comment

PowerEdge 6950 shows 112GB of RAM even though 128GB is installed

 

For the past few days we’ve had the above problem where we upgraded one of our PowerEdge 6950 server to 128Gb of RAM but once we booted it it only showed 112GB of RAM. My colleague James Voll and I tested to try work out which RAM bank may have been causing the issue and found one where if we removed the two RAM sticks it still only showed 112GB so we contacted Dell and got an engineer out who replaced the motherboard for us but still after the replacement it wasn’t showing the full amount. in actual fact due to the motherboard coming with the basic BIOS update it only showed 12GB!! So we updated the BIOS to the latest revision and it was still showing 112GB. I logged into the BIOS and went to the memory settings for the server and noticed “Server Memory Test” was enabled so decided to disable it and reboot the server to see if possibly it would change something and remarkably it seems it did as now the server showed 128GB of RAM and booted twenty times faster through the post screen. I’m not if it’s a bug or because the 6950’s don’t normally have that amount of RAM in them but disabling the Server Memory Test feature seems to have given back our missing 16GB of RAM Smile

Hope this saves someone the time and effort it took for us to work it out

Gregg

Advertisements


Leave a comment

“Warning: The current memory configuration is not optimal.”

 

Today I had the problem where after adding new memory to one of our Dell 6950 servers even though we followed the correct steps of putting the new 8GB memory cards in as pairs after booting the server the server showed 82GB instead of the installed 96GB.

 image

We had 4GB cards in already and if I checked under Hardware Status via Virtual Centre (due this machine being an ESX host) it showed all the DIMMs correctly and added up correctly. I searched all over the web for an answer but only when I rebooted the server did it give me an error that helped me source the answer to my problem. The following error showed “ Warning: The current memory configuration is not optimal.”  and told me to see the owners manual as shown below.

image

I searched for this and came across Steve Jenkins’ posting on the exact error and the response he got from Dan Coulter, an Enterprise Expert Center Server Support Analyst at Dell. So as to direct traffic accordingly to Steve’s posting rather than posting the answer here I’ve pasted the link to his posting below

http://stevejenkins.com/blog/2009/12/dell-warning-the-current-memory-configuration-is-not-optimal/

Seeing as we have more memory arriving soon to match the newly added 8GB cards I’ll just wait for the new cards to fix the problem but a big thanks to Steve and Dan for the answer to the problem.

Gregg


Leave a comment

Dell Openmanage Installation

 

A few weeks ago I had to install OpenManage on some of my newer dell server machines and since some of the settings have changed since I last used it I thought I would write up a list of the steps required for our teams wiki site and write up a blog posting of the the steps for anyone who hasn’t done it before.So belatedly here are the steps and cool new tricks some of my friends on twitter showed me.

Firstly the standard steps:

  1. Download the tar file from the ftp site or the support site 
  2. Copy the file using winscp(this is what i use at least) to /tmp/openmanage on the server
  3. Log into the box either via winscp /via putty or onto the console directly and type in:

    cd /tmp/openmanage
    tar -zxvf OM_X.X.0_ManNode_A01.tar.gz (OM_6.2.0_ManNode_A00.tar currently)

  4. Once the files have unpacked type in:
    cd linux/supportscripts/
    ./srvadmin-install.sh -x
      (-x is for express install and installs everything but if you only want to install specific features the commands you can also use are -d -w -r –s )

    -d = Dell Agent
    -w = web interface
    -r = DRAC services
    -s = storage management

     
  5. Once the files have unpacked and installed type:
    srvadmin-services.sh start
  6. When the various component services have finished starting type in: 
    cd /tmp
    rm -rf Openmanage
  7. To allow the Openmanage agent to function the following firewall commands need to be run, these open the firewall ports required: 
    esxcfg-firewall -o 1311,tcp,in,OpenManageRequest

 

While asking a few friends on twitter if the latest Openmanage worked well in their environments Arne Fokkema @afokkema of ict-freak-nl fame pointed to the automated scripting way of doing it written up by Scott Hanson @dellservergeek . As you may know if you’ve read some of my previous blog posting I’m trying to learn how to script more and more of my daily tasks to firstly build my powershell and scripting knowledge and skills as well as making my daily job easier. The script is really simple and is one I’m planning to test in my lab environment very soon. At the bottom of the script though was a comment by one of my powershell idols in Alan Renouf @alanrenouf. He had changed a few of the snmpd commands and so I got a hold of him via twitter and classic him he mailed me the script he spoke of. Only after this did I notice he wrote up a blog post about it,which is exactly what he sent me.

Thanks to all who replied to my twitter messages and hopefully I can get Alan/Scott’s scripts into my automated server deployments in the very near future.

Gregg Robertson

VMW_09Q3_LGO_VMwareCertifiedProfessional_K

MCSES(rgb)MCTS(rgb)_1079_1080_1078image