Create CPG using Disk Filter

Recently I had to create a new 3PAR CPG using just new added 1.2TB disks. But the system uses already a cage full of 600GB disk. While it was straight forward to change the existing CPG (using 3PAR Management ConsoleStoreServe Management Console (SSMC) does not support this feature any more) to use all disk in cage 0, it was not possible to create a new CPG for all FC disks in cage 1. It was not possible to filter cage number, slot in cage, magazine or chunklet-sizes in the GUI. Also using a simple version of createcpg command does not work. All I got was an error: “Error: no available space for given (invalid?) parameters“.

To get the work done, I used this command:

createcpg -sdgs 32g -t r5 -ha mag -ssz 4 -ss 128 -ch first -p -devtype FC -tc_gt 546 -saga "-ha mag -p -devtype FC -tc_gt 546" FC_r5_1200_AO


  • -sdgs 32g
    Growth Increment. Note: use 32g instead of 32768!
  • -t
    Raid-Level (r0, r1, r5, r6)
  • -ha
    Availability (port, cag, mag)
  • -ssz
    Set-size. For example: set-size of 4 when using Raid5 means 3+1
  • -ss
    Step-size (KB)
  • -ch
    Preferred chunklets (first, last)
  • -p

    • -devtype
      Disktype (FC, NL, SSD)
    • -tc_gt
      Means: “total chunklets greater than”. -tc_gt 546 selects all disk have more than 546 chunklets (size of a chunklet = 1G –> use all disks greater than 600GB)
    • -tc_lt
      Means: “total chunklets less than”.
  • -saga
    This parameter describes the admin-space of the CPG. If you don’t enter this parameter, the characteristic of the admin-space will be different to the characteristic  of the user-space.
  • FC_r5_1200_AO
    Name of the new CPG
Create CPG using Disk Filter

Create PSP rule for HPE 3PAR

There are a few best practices when implementing a 3PAR into a vSphere environment. One of these is the creation of a custom PSP-rule. With this set, all 3PAR volumes are automatically configured according to best practices when they get mounted. In this post I will show ways to create this rule.

Continue reading “Create PSP rule for HPE 3PAR”

Create PSP rule for HPE 3PAR

Mount HP Blade enclosure DVD on VMs

Mounting a HP BladeSystem enclosre DVD drive on a VM sounds easy. And it is, but it is not that easy as I thought first. Technically it is a USB drive for the host, but it is not possible to pass through the device as a USB drive. This post describes the steps to take for windows VMs (tested for Windows 2008 and 2012), but this should also work for other OSs.

Continue reading “Mount HP Blade enclosure DVD on VMs”

Mount HP Blade enclosure DVD on VMs

Some basic stuff about HP P4000

Multisite Cluster

  • Multisite-Cluster always syncs synchronously.
  • Gateway connection handles the control traffic
    • Windows systems are connected to the node that holds the data. This because of the DSM driver.
    • For VMware this feature is available for SanIQ >= 12.5 with necessary patch installed for vSphere 5.5 and later.
    • Advantage of Multisite Cluster is that Gateway is always on local site.
  • To be able to failover after a complete site failure at least nRAID-10 is necessary.

Migrate Data

  • Cluster Swap
    • Create a new cluster using new nodes
    • Present the new VIP to existing hosts
    • Start Cluster Swap in CMC
    • P4000 replicates data from existing cluster to new cluster
    • after completing, traffic from hosts just accessing new cluster
  • Adding new nodes to existing cluster
    • Add new node to cluster, wait to complete re-striping
    • Remove old node from cluster
    • repeat until ever node is replaced

General information

  • When adding a new node, it is optimally the same as already used nodes in the cluster. Otherwise the used capacity of the new node will just be as the capacity of existing nodes.
  • Queue size
    • Acceptable queue size of disk is 2.
    • Acceptable queue size of node = (number disks) * 2
    • Acceptable queue size of cluster = (number disks) * (number of nodes) * 2
  • When there is a high write rate in cluster presenting storage to Oracle database, check archiving protocol data when there is a very high write density.
Some basic stuff about HP P4000

Public CA do not allow internal names and reserved IP address any more

With November 2015 public CAs do not issue new certificates that uses internal names or reserved IP addresses in subjectAltName or in commonName. Furthermore such certificates will be revoked on October 1st, 2016.

Internal names are hostnames that do not end with an Top Level Domain ending (.com, .de, …). For example: .local, .internal. Also NetBIOS names without any domain extension are affected.

Reserved IP addresses are defined by Internet Assigned Numbers Authority (IANA). You can look reservations for IPv4 here  (RFC 1918 range) and IPv6 here (RFC 4193 range).

If you are using an internal CA you are not affected. For more information about this change of public CAs click here. For more information about VMware products click here.

Public CA do not allow internal names and reserved IP address any more

HP Bundles are not updated using Update Manager

You probably know that you can add HP VIB Repositorys to VMware vSphere Update Manager. I normally add these links to Update Manager:

So you can define an own baseline for HP VIB packages or add them to you already existing baselines. I would recommend the first option. Continue reading “HP Bundles are not updated using Update Manager”

HP Bundles are not updated using Update Manager