A short (and funny) one. At my last upgrade of VCSA from 6.0 to 6.5 I got a warning that says: “User vdcs does not have the expected uid 1006”. Furthermore warning is talking about a KB article to read but without any hint what article it is talking about. This message has something with the vCenter feature Content Library. According to VMware Support when Content Library is not used, you can continue with upgrading VCSA – and using Content Library after the upgrade. When feature is use, call VMware Support.
When you connect your storage device to your ESXi hosts, a Path Selection Policy (PSP) will selected based on defined rule set. To help the host to select the right policy for your device, you have a few options. I personally prefer to create a device specific rule based on Vendor and Model. I will describe for ways to get the information about your device you need.
In a 3PAR system it is best practice that setsize defined in CPG is a divisor of the number of disks in the CPG. The setsize defines basically the size of a sub-RAID within the CPG. For example a setsize of 8 in a RAID 5 means a sub-RAID uses 7 data and one parity disk.
Removing a cage can by a simple task. But it can also be impossible without help from HPE. Before starting at point 1, you should probably check point 3 first.
Generally I would recommend to do any of these steps ONLY when your are
- very familiar to 3PAR systems!
- know what you are doing!
- know what are the consequences of your actions!
If you have doubt about any of the following steps, contact HPE! Also you should use the 3PAR Command line Reference Guide to check the used commands.
Generally it is supported to mix disks of different sizes of the same type within a 3PAR system. For example you can use 900GB and 1.2TB FC-disks – within the same cage and even within the same CPG. When a disk fails, HPE sends an replacement disk. Some time ago, stock of 900GB FC disks seem to be empty. So when a 900GB disk fails, you will probably get a 1.2TB disk instead.
So how to handle different disk sizes? Here are a few points to consider:
- How do a 3PAR system handle different sizes within the same CPG? The system tries to put he same amount of data on every disk in a CPG – no matter if there a different disk-sizes. When the smaller disk are full, larger disks continue to fill up. So replacing just a few disks within a CPG with larger disks does not matter – as long as smaller disks not running full. When this happens, just larger disks gets new data. This can lead to a serious performance problem.
- When talking about SSDs: mixing different sizes will probably be no problem. Even when you think of point 1. But: when your SSDs are near the performance maximum you can also get an performance problem after smaller SSDs are full.
- When you have different CPGs for different disk sizes (how this can be done, you can read here), you must check before replacing a failed disk by a disk of a new size. Will the replaced disk be part of the right CPG? If not, your should re-define you CPG disk filter. By the way, this cannot be done in SSMC any more! You need CLI. See point 4.
- What about filtering disks for CPGs by cage or position in cage instead of disk size? Since I know, HPE replaces 900GB disks by 1.2TB disks, this is my preferred option, when different CPGs are desired.
For example you can use this command to change the disk filter for an existing CPG:
setcpg -sdgs 32g -t r6 -ha mag -ssz 10 -p -devtype NL -cg 2 -saga „-ha -p -devtype NL -cg 2“ NL_r6_cage2
The meaning of the different parameters, you can find here (Option
-devtypeis mandatory for option
-cg, which is for cage selection. You can list more than one cage by list them separated by comma (1,2), or define as range (1-3). Another option is to define filter as positions of disks. Check 3PAR Command Line Reference for more information – command:
Here is a short PowerCLI script to copy vSwitch PortGroups from a source host to a target host. Security policies will be copied too. The switch at the target host has to be created already. The script takes inheritance into account. This means just setting, changed at PortGroup-level are copied. All other settings are inherited.
Recently I got the following error on two different vCenter appliances when trying to enable vCenter HA:
Cannot find a network adapter for the vCenter Server management network (NIC0) on the vCenter Server Appliance guest OS. Once available, the first guest OS network adapter will be selected. Use Edit VM settings to add a network adapter.
This error appears at VCHA wizard when first pressing Next-button.
- Rebooting VCSA
- KB article 2147932
- Adding a second vNic – witch is only supported for VCHA!
I also found out, that network configuration within VCSA GUIs was not consistent. Network configuration in VCSA can be found here:
- VCSA management (https-port 5480)
Networking –> Manage –> Network Interfaces
- WebClient (Flash)
Administration –> System Configuration –> Nodes –> vCenter –> Settings –> Networking
In my cases, in VCSA management information about nic0 was looking good. But in WebClient, no information about a nic0 was available. Not even a nic0 was displayed.
To resolve the problem I had to restart all services by running these commands in VCSA shell:
service-control --stop --all
service-control --start --all
As I mentioned before: rebooting VCSA did not solve the problem!