Skip to main content

Online HPE Server Memory Configurator tool

I found some memory modules and wanted to see if I could boost my HP G6 server a bit more. Digging around the HPE site and reading the pdf I was not getting anywhere to see if I could just easily add the extra modules. I then googled and it pointed me to a HPE Server Memory Configurator tool - https://h22195.www2.hpe.com/ddr4memoryconfig/home/legal (Appears to only work with G6 and above)

This tool has two ways to help you work out your memory modules configuration if you are looking to increase/upgrade the memory in your existing server - 

  • Use HPE Insight Diagnostics tools to help detect the memory already installed in your server. This means possibly no downtime if you already have the correct versions of various HP management tools already installed on the server otherwise you would still need downtime to install/update/reboot the server. 
  • Enter HP part number/s for the memory modules you have installed already in your server but this requires you to either have the information already or shut down the server to gather the information (part number/assembly number) from the memory modules itself.
If you are using this tool to plan for a new server and want to know what combination of modules are required to achieve your capacity then you don’t need to worry about the two points above. I will show a quick example of how I used it based on my G6 DL360 with 8 x 8GB modules installed already. I have located some 2GB modules so I wanted to see if it was possible to add those modules and how to position the installation of all the memory modules.

1) Go to https://h22195.www2.hpe.com/ddr4memoryconfig/home/legal. Select which type of memory you are trying to configure. Select DDR4 if it is for Gen9 or Gen10 servers, DDR3 for G6, G7 or Gen8 then click "I agree". I selected DDR3 as it is a G6
2) Under "Step 1a" if you have a pre-configured BTO server model part number (SKU Number) then select "yes" and select "next". I didn’t have the details for “step 1a” so I followed “step 1b” which is to select which ProLiant server series you have, I selected “HPE ProLiant DL Servers” and then select your server from the drop down box below which I selected “ProLiant DL360 G6”
3) Processors - Once the model has been chosen you will need to select how many processors are installed or to be installed to the system
4) Memory - If you are configuring a brand new server then you would select "No" and click "Next" (Skip to step 7). For me I had memory installed so I selected "Yes" which will bring down another menu to choose what type of technology the memory is currently configured in the server. I selected "None" as I am not using any of those technology but if you are then select the appropriate one followed by "Next"
5) Existing Memory Information - If you have the correct HPE Diagnostics Insight tools (check the versions required as shown on the web screen) on a server then you can use "step2a" to help automatically detect the memory installed in your server. I chose to use "step 2b" clicking on "Enter your memory"
6) A pop-up windows appears and gives you some guidance on how to gather the part numbers of the memory modules you have installed in your server. Use the scroll bar to go down to the section where you start entering the module information. As you can see I have added the part numbers of where the modules are currently installed for me and click “Next”
7) You will see to the right of the web page your server memory configuration details. If “Existing memory” is shown as “0 GB” then you are using the tool to configure a new server or you have entered the incorrect part number/s hence the tool is not recognising your part number. My one is showing I have 64 GB ram which is correct
8) Use the slider or enter your desired memory you would like to increase/upgrade for your server. Select the memory options you would like and read the tips section to give you guidance. This section could determine how your existing memory/new server memory are configured. As you can see some options are based around cost and performance. Selecting the wrong memory option could equate to overspending or degrading the performance to achieve the desired configuration. So for my example I have used 8 out of 18 slots to get my 64GB (8 x 8GB) so I have 10 slots free. The modules that I have found are 2GB so assuming I can use all the remaining 10 slots I should be able to get 20GB extra so my desire memory would be 84GB. I selected “General purpose” and clicked “Next”

9) You will now get the results of what are the possible configuration you can achieve for your server based on your chosen desire memory and memory option selected. Some options may require you to remove/replace/add different modules to the ones you already have in your server. Once you decided which option you will go for click “Select”. As you can see there is an option where I can use all my 2GB ram and my current 8GB ram modules. 
10) You will get details about what HPE memory module kits to buy and a diagram of where to install/re-position the modules which is the essential part !!

So this was just a very basic run through of how I used it at home for my lab kit to see whether the memory I have located can be added to my server and also where to position each of the modules in my server so that it works. As I stated in step 8 it is important on which memory “option” you select where you can choose from Performance/Power Efficiency/Low Cost/ General Purpose as this could affect whether you need to replace existing modules in your server to achieve you memory requirement. I know I will be using this tool when I next do a upgrade or configure a new HPE server.


Comments

Popular posts from this blog

Rolling back a version of ESXi

There is an option in VMware where after you have performed an major upgrade of ESXi you can roll back to your previous version. The benefit of this is that you would not need to reinstall your ESXi and its configuration if you had issues with the new software. I had to do this on one occassion in my lab where I upgraded from 6.5 to 6.7 and my VMs would not run because the CPU was not supported in 6.7. Please remember if you are using ISO method to upgrade ESXi please ensure you select "Upgrade ESXi, preserve VMFS datastore". Selecting "Install ESXi, preserve VMFS datastore" does not mean preserving datastore means retaining ESXi as it will still do a clean install of ESXi. This method does not work for vSphere 7.0 as there are changes to the partitions on the boot device. Below are the steps to roll back to a previous version which is quite straight forward. As always perform an backup of your host configuration before you upgrade or rollback ( KB2042141 ). I have

Configuring ESXi 6 host to send logs to Syslog Server

In my previous post I talked about configuring VMware Syslog server for Windows which is installed and enabled by default on installation of vCenter 6 for Windows. I will now describe the basic configuration that is required on an ESXi 6 host to be able to send logs out to a syslog server using my vCenter as the example. 1) Navigate to your ESXi host within vCenter. Go to "Manage" tab and select "Settings" followed by "Advanced System Settings". Look for the settings "Syslog.global.loghost" and highlight this settings. Click the pencil icon to edit the configuration for this setting. 2) You can now add the host name or ip address of your syslog server/s. You can enter just hostname or IP address, use udp://hostname:514 or ssl://hostname:1514 to be more specific on the port and protocol to be used. If you have multiple hosts then you use the comma (,) to separate each server i.e. udp://192.168.0.1:514,udp://192.168.0.2:514 3)We n

Custom ESXi Image - ISO using PowerCLI

There comes a time when you have purchased a new hardware to run your ESXi software and discover that the installable base media provided by VMware does not include the drivers or the drivers are out of date. In the world of Windows (Plug and Play) it would discover the hardware and prompt you to provide the drivers so that Windows would install/update the drivers for the hardware. For ESXi if the drivers are not present during load time then the hardware will possibly not work. VMware uses VIB (vSphere Installation Bundle) as a way for vendors to distribute their drivers. To install these VIBs you can either use Update Manager or command line (esxcli). Now this is all good but it does mean you have to first install the base ESXi then use one of the steps above to install/update the drivers.   Some people might feel that it is OK to update the drivers using the above methods but what if it was the network card that was the new hardware and you needed new drivers. Without the net