Skip to main content

HP ProLiant DL360p Gen8

I got 3 new toys in my server build room for a virtualization project. They are HP DL360p Gen8 (G8 became Gen8) servers. It is a 1U with elegant view. This server powered up with 2xIntel Xeon process and can be supported up to 768GB RAM (DDR3 with Load Reduced DIMM). HP introduced iLO ver4.0 in this servers and FlexibleLOM (4x 1Gb ports and optional 10 Gb port).  It has new slide-out SID (System Insight Display), the most useful stuff to find out the faulty components immediately. I watch this display screen often to see warning/critical errors of a server.
HP DL360p Gen8 introduced “Intelligent Provisioning” where you can configure and install the OS and perform maintenance activities such as Array Configuration utility, Firmware Update, iLO configuration and other tasks.
This feature really eliminates the SmartCD requirement.


Tasks listed under Perform Maintenance:

The internal storage with Hot Plug SFF SAS/SATA can be extended upto 8TB and 12TB with LFF SAS/SATA
No front Video interface, it requires Front Video adapter kit.. Only Rear video.
1 internal SD Slot
1 internal USB port and 6 external (4 Rear, 2 Front)
New version iLO4.0 and introduces iLO 4 management processor. ”Active Health System” is essential component of the HP iLO management engine and continuously monitoring over 1600 parameters. This log can be downloaded and forward to HP Support team for further investigations.


DL360p Specs:

Memory Configuration Tool:

128 GB
Qty 8 x HP Option Part# 672631-B21 HP 16GB 2Rx4 PC3-12800R-11 Kit (HP Module Part# 672612-081) STD


ddr4memory said…
First thing - since you mention the 768GB - you have to be aware of the difference between the LRDIMMs and the HyperCloud.

HyperCloud underpins the LRDIMMs as well as the future DDR4. It is HyperCloud IP being used in the LRDIMMs (Inphi the maker of the buffer chipset just lost their patent challenge of HyperCloud) - and HyperCloud is being copied for DDR4.

IBM and HP both are offering HyperCloud - which means they have a competitive advantage over others - as they can deliver 1333MHz at 3 DPC with HyperCloud (LRDIMMs cannot).

Further the 16GB LRDIMMs are non-viable vs. RDIMMs even (as similar performance at 3 DPC).

32GB LRDIMMs may appear at same time as 32GB HyperCloud - at which time you would want to use the HyperCloud for the above speed reasons (if not the legal issues with LRDIMMs).

For a more complete examination of the memory choices for IBM and HP (and some of the intellectual property issues driving change in DDR4), check out the main blog and the links below (which are for IBM and HP - memory choices):
May 24, 2012
Installing memory on 2-socket servers – memory mathematics

For HP:
May 24, 2012
Memory options for the HP DL360p and DL380p servers – 16GB memory modules
May 24, 2012
Memory options for the HP DL360p and DL380p servers – 32GB memory modules

For IBM:
May 25, 2012
Memory options for the IBM System x3630 M4 server – 16GB memory modules
May 25, 2012
Memory options for the IBM System x3630 M4 server – 32GB memory modules

Popular posts from this blog

vCenter Reinstallation after 60-Days trial expires without losing Database Contents

Many of us still evaluating the vSphere and vCenter in our test environments. Sometimes, it takes more than 60 days to evaluate where trial edition expires.
We can't extend the trial edition in ESX host, either we have to reinstall it or license it. vCenter also have to follow the same way as ESX does. But, here we can keep old database contents as it is when you reinstall the vCenter software.

This document using vCenter 4.0 and SQLEXPRESS 2005 (built in) database. At the time of installation of vCenter 4.0, it installs SQLEXPRESS 2005 by default unless any other Database specified. Mostly, we are using built-in database is SQLEXPRESS 2005 for testing environment.
When you install vCenter 4.0, it installs SQLEXPRESS 2005 and creates a database called "SQLEXP_VIM". You can view this thru SQL Server Configuration Manager console.
Start à All Programs à Microsoft SQL Server 2005 à Configuration Tools à SQL Server Configuration Manager

Creating DSN

Create a System DSN for this d…

Set VLAN ID to IPMI Address in Nutanix

The IPMI is remote management interface like as HP iLO, DELL DRAC. During the Nutanix cluster deployment, it is not possible to mention the VLAN ID of the IPMI's IP Address. This need to be entered thru command line via ESXi host or Windows Hyper-V. This article talks about ESXi host only.

Login to ESXi thru SSH client. Run the following command to enter the VLAN ID (we assume that you already configured IP Address)

~ # /ipmitool lan set 1 vlan id 333

~ # /ipmitool lan print1
Set in Progress         : Set Complete Auth Type Support       : NONE MD2 MD5 PASSWORD  Auth Type Enable        : Callback : MD2 MD5 PASSWORD                          : User     : MD2 MD5 PASSWORD                          : Operator : MD2 MD5 PASSWORD                          : Admin    : MD2 MD5 PASSWORD                          : OEM      : MD2 MD5 PASSWORD  IP Address Source       : Static Address IP Address              : xx.xx.xx.xx Subnet Mask             : MAC Address             : xx:xx:xx…

Changing Thin to Thick disk and vice-versa

You can change the existing Virtual Hard disks (VMware based) from Thick to thin and vice-versa. This can be achieved by either using VMotion/SVMotion or command line tool called "vmkfstools". Using VMotion/SVMotion is required a valid license. Select “Migrate” and choose “Change Datastore” and select the Disk format.

If you don’t have a VMotion/SVMotion license, use the following command to achieve the same.

From Thick to Thin:

vmkfstools –i "Thickdisk.vmdk" -d thin "Thindisk.vmdk"

It will start to clone to virtual hard disk in Thin Provision method. After completed, you can attach this disk with VM and power it on. If all looks good, you can delete the original thick disk from the data store.

Use the following command to see real-time usage of thin disk:

du –h "Thindisk.vmdk"

You can notice the big difference of disk usage between of Thin and Thick format disks.

From Thin to Thick:

vmkfstools –i "Thindisk.vmdk" -d zeroedthick "Thindisk…