Recently we had to troubleshoot rather high storage latency at a customer site. The environment consists of Hyper-V hosts connecting to 3PAR arrays via iSCSI. 3PAR arrays are all-flash arrays (AFA). I know such problems in vSphere environments too. There higher storage latency can be caused by delayed acknowledgement (DelAck). Read more about this issue and how to configure DelAck on vSphere ESXi hosts here. […]
A new – and badly documented – feature in StoreServ Management Console 3.6 is Topology Insights. Sounds first like the probably known Maps. But Topology View shows an end-to-end view: VM <–> VMDK <–> Datastore <–> Host <–> Virtual Volume <–> System. Enriched with performance-information! This short post is about this feature and how to get it.
First, what does active/standby mean. For this blog post, it means the array hast at least 2 controllers, one presents ALL LUNs to the hosts, the second controller presents NO active LUNs path to the hosts. Just in case of a manual or automatic failover, the second controller takes-over ALL LUN-presentations – and active paths. Examples of such arrays are: [very old one] HP MSA 1000 HPE Nimble […]
Normally when using a self-signed certificate you get a warning. It is also normal to accept the certificate to continue your task. These days I wanted to register a 3PAR system as storage provider in vCenter. Because of a certification error, this could not be accomplished. In this post I describe how to solve – at least my – problem.
Recently I had problems to connect a 3PAR system to a quorum appliance. Quorum is needed in a Peer Persistence configuration. The system had a connection to the quorum. After HPE support did replace a node, connection could not be established any more. Command showcropy -qw shows error “below min safe num QAs” and other errors talking about QAs. In SSMC quorum was stated as […]
The code snippet in this blog post is an example of how to add iSCSI targets to an ESXi iSCSI initiator. But there is also a loop within processing a host, that sets iSCSI target parameter. For example this can be used when a storage vendor recommends to disable delayed acknowledgment per iSCSI target, like HPE does for 3PAR and LeftHand. Here you can see […]
When implementing new storages or configure existing ones it is a good idea to check paths (state and amount) to volumes. When operating a few hosts using a few datastores this can be a very time-consuming task when using the GUI. Therefore I wrote the following function.
Recently I upgraded a new 3PAR from 3.2.2 MU6 to 3.3.1 MU3. Even during the upgrade I could use me putty to run commands in 3PAR console. After the upgrade process activated 3.3.1 MU3, no putty session could be established any more. When trying to connect, the error appears: Network error: Software caused connection abort It turned out this is because no older TLS version […]
To deploy new HPE SimpliVity nodes, you need to run Deployment Manager. Current version at writing: 220.127.116.11. Requirements to run Deployment Manager are: .NET 4.7.1 and Java 1.8. When .NET is not installed during installation, wizard links to Microsoft and starts the download. When Java is not installed or too old, an message is shown at first start. Sounds very simple. Anyway I had some […]
When initialize a new 3PAR, depending on your protection level, at least the size of one disk per disk-type will be reserved as spare. Also when you add disks to a running system, spare-chunklets are created. This is done by admithw. For example when you initialize a system containing 2 SSDs for adaptive flash cache (AFC) the size of one SSD is reserved for spare. […]