For details of vRSLCM Patch 1 and associated fixes please refer to VMware KB59658
Note: It is best practice to snapshot vRSLCM before proceeding with the update.
From the top right corner of vRSLCM notification alerts are visible, clicking on the icon presents ‘Patch 1’ as being available for download:
One quick method to discover your ESXi build number and version is to connect via ssh and run the following command from the ESXi console:
vmware -vl
The output displays a build number 8294256 and also returns the Update level U2.
You may also lookup your ESXi build number and version from the following KB:
vRealize Suite Lifecycle Manager (vRSLCM) v2.0 is a centralized way to manage the vRealize suite of products from a single pane of glass, allowing users to perform tasks such as installation, configuration, content management, integrated market place, upgrades, patching, certificate management, support matrix lookup among other admin tasks.. more details can be found here on the What’s New video for vRSLCM 2.0.
This post details how to import an existing brownfield installation of the vRealize Suite into vRSLCM 2.0, these products were originally deployed as per the VVD 4.3 architecture, namely:
The following steps detail how to onboard these vRealize products into LCM, allowing the user to leverage all these management capabilities that come with vRSLCM 2.0.
This example is based on logging into a newly deployed vRSLCM 2.0, begin by logging in with default username ‘admin@localhost’ and default password ‘vmware’:
The following post provides a basic UI overview of how the VxRail Appliance disk groups are configured and viewed from both the VxRail Manager and the vSphere Client.
The VxRail Appliance vSAN disk groups are configured in one of two ways:
Hybrid – single SSD disk for caching and one or more HDD disks for capacity.
All-flash – single SSD disk for caching and one or more SSD disks for capacity.
The amount of storage available to the vSAN datastore is based on the capacity drives.
A VxRail node allows for multiple disk groups (please refer to official VxRail docs for specifics, as the quantity of disk groups differ per VxRail model) which in turn provides multiple cache drives per node thus potentially improving performance. In this example each VxRail Appliance node has two All-flash disk groups, each node in the cluster is required to have the same storage configuration.
From the vSphere client click on the cluster and navigate to the ‘configure – vSAN – General’ from here we can see that the vSAN cluster for this VxRail appliance comprises of 24 disks in total (4x 13G servers).
‘vSAN – Disk Management’ displays both the Disk Groups and the disks associated with each Disk Group. Taking the example below of the first ESXi host in the cluster, we can see the VxRail node has a total of 6 disks contributing storage to the vSAN cluster, comprising of two disk groups with three disks in each disk group. Continue reading
VxRail manager utilizes the PTAgent running on the ESXi hosts as part of a VxRail cluster in order to pull hardware related information from the host. If you are experiencing host visibility issues in VxRail manager, then a good starting point is to check the PTAgent status,
PTAgent is bundled with VxRail code releases as part of the Dell PowerEdge components. ESXCLI can be used to determine the PTAgent version running on the host.
esxcli software vib list | grep dellptagent
For a detailed overview of the VxRail Management Pack for vROps please refer to the excellent post by Steve Hegarty:
VxRail Management Pack for vROps
This post provides an example use case of working with this mgmt pack. You can see from the image below capturing the Mgmt. pack dashboard ‘Dell EMC VxRail Clusters‘, is throwing an alert in relation to a VM that has exceeded the threshold for snapshot duration (by the way this is a lab and yes it has well exceeded said threshold!):
Clicking on the alert provides detailed info (‘Symptoms’) of the alert. Click on the ‘RUN ACTION’ button in order to be presented with the options for remediation: Continue reading
Quick ‘How to’ on looking up the current running version of VxRail Manager.
Login to VxRail Manager UI:
Navigate to ‘Config’, click on the ‘General’ tab:
From CLI, ssh to the VxRail Manager:
mystic@vvdrailmgr01:~> rpm -qa | grep vxrail
vxrail-mystic-4.5.210-8392085.noarch
