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

[VMware Labs] Onyx for Web Client

If you don’t know Onyx, it is a Plugin to vCenter that can show you PowerShell commands of tasks you do using the GUI. Up to now Onyx was just available to vSphere C# Client. Now it can be used for Web client too!

  • Download Onyx from here and extract it
  • Start a PowerShell console and go to extracted file directory
    • If neccesary change Execution Policy to at least RemoteSigned by running Set-ExecutionPolicy RemoteSigned in a PowerShell console as Administrator
  • Start Installation by running .\install.ps1
    • Attention: the script will stop Web Client Service!
Using Onyx

After connecting to Web Client you can see new buttons next to search field on top. The red circle starts the recording of tasks that will be converted into PowerShell commands. The PowerShell Icon gets you to the Onyx scripting window. To use Onxy do

  1. Navigate as near as possibly to the task you want to export to PowerShell commands
  2. Start recording by pressing the red cycle button
  3. Do the task(s)
  4. Click the PowerShell button to jump to scripting  window
  5. Press the Stop button on top of the window, then you see the recorded PowerShell commands.
  • Onyx for Web Client is just available for vSphere Web Client Version 6.0.0 Build 2559277
  • Onyx can also be installed in vCenter Appliance
  • The installation replaces Web Client files of your installation. This could be a problem in future releases or upgrade of Web Client. So it is highly recommended to use Onyx just in test environments.
  • Great Plugin!



[VMware Labs] Onyx for Web Client