Tag Archives: vSwitch

Day-2 Operations – Health Monitoring

Health monitoring of an infrastructure is a key element of day to day operations, knowing if something is healthy or unhealthy can make the difference between business impact or remediation steps to prevent any impact ot the business.

There are three ways you can monitor the health of vSAN, the native Health Service which is built into the vSphere UI, vRealize Operations (vROPS), and the API all of which have advantages and disadvantages over the other, for the first part we are going to cover the Health UI which is incorporated into the vSphere UI.

vSAN Health Service
In the current release of vSAN (6.6.1) there are two aspects to the Health Service, an Offline version and an Online version, the Offline version is embedded into the vCenter UI Code and any new features are added to this when patches/releases/updates for vSphere are released.  The Online portion of the Health UI is more dynamic, newer health variables are added as part of the Customer Experience and Improvement Program (CEIP), there is a major advantage to using the Online version in the fact that critical patch releases for vSAN can be alerted through the Health UI which is a really cool feature, it also dynamically adds new alarms to vCenter as part of the health reporting, as VMware understands and gets feedback on how customers are using vSAN, VMware can create alarms dynamically to alert/avoid situations that are a cause for concern.

In order to use the Online portion of the health service you need to opt in to the CEIP program, which is as simple as ensuring your vCenter server has internet capability and you have provided a myvmware account credentials.  A lot of customers are concerned with having their vCenter server having the ability to connect out to the internet, as a workaround I recommend a method where vCenter only has an allowed rule to connect to vmware.com addresses such as a proxy server or white list.

The health service is designed to report on all aspects of vSAN health, and trigger alarms in vCenter to alert you to anything that you should pay attention to, in the previous screenshot, you will notice that I have a warning against the cluster, this is due to the cluster disks not being evenly balanced due to me placing two hosts into maintenance mode to perform firmware updates, as you can see from the screenshot on the right, this has also triggered an alarm in vCenter.

A really cool feature of the Health Service is the “Ask VMware” button, simply highlight an issue and click the button and it will load up a VMware Knowledgebase article telling you what the issue means, why it has occurred and steps to remediate, as many of you know, I come from a support background and spent a good few years in VMware Support so the whole ability to self help and be provided with the right information straight away at the click of a button can be a huge time saver in my opinion.   There is a KB article for every section of the Health Service and as you can see from the screenshot on the left for my disk balance warning,  there is quite a lot of detail in each KB article and the resolution steps are well documented and easy to follow. If after you have followed the steps in the KB and your issue still persists, remember to include in your support request that you have followed the KB Article so you are not asked to run through it again as part of troubleshooting.

When you have deployments such as a 2-Node ROBO or a Stretched Cluster, you do not have to tell the Health Service about this, it will automatically detect and populate the appropriate health checks such as Site to Site latency and witness connectivity.

Critical Patch Updates – The Online Health Service also has the ability to make you aware of a critical patch release, as part of the “Build Recommendations” element of the Health Service, so as a critical patch is released, the online health service will dynamically slip entries into the UI to alert you of the release, in my opinion this is so much better than waiting for an email notification.  The benefit for this is that it can be tailored for your environment, so you are not receiving notifications for updates that are not applicable to your environment.

A question I get quite often is how frequent does the Health Service report, the simple answer is by default it is designed to check the health every 60 minutes, in my environment I have this set to the lowest value which is 15 minutes, however, if there is a critical issue for example, a host failure, network connectivity issue or disk failure then the health service will update with this information pretty instantly, it will not wait for the next refresh cycle and again you will see vCenter alarms triggered for the events.

vRealize Operations
Now I have to admit, I am not a vROPS specialist in any way, shape or form, but I have deployed vROPS in my demo environment and have got the vSAN dashboards operational pretty easily without any challenges.  Now to be clear I am using vROPS 6.6.1 which has the built in native vSAN dashboards which were not present in earlier versions and required you to use the vSAN Storage Management pack to enable the capturing of vSAN Metrics, below is a screenshot showing the default metrics reported in then vSAN Operations Overview dashboard

One immediate advantage that vROPS has over the vSphere UI is that vROPS can display a holistic view of all your vSAN clusters, whereas the vSphere UI is only showing you the status for the cluster that is in focus, so if I had multiple vSAN clusters deployed they would all be listed here in this single dashboard which makes operational life that little bit easier.

You can see there’s a wealth of information at your fingertips from an operational perspective, you can immediately see how your cluster(s) are performing as well as any potential issues that have triggered alarms, which then leads us to the Troubleshooting Dashboard, and here you can immediately see the reason for my 8 “Red” alerts:

As you can see, just like the Operations Overview dashboard, the Troubleshooting dashboard has a lot of information, this dashboard is designed to allow you to drill down into specific areas and components within vSAN, provide you heatmaps on various areas such as disks for example which when a heatmap is red it will draw your attention, for example if I was to double click on one of the green squares in section 9 which is labelled “Is the write buffer full on diskgroups” it will take me to that specific cache disk:

Which takes me to a dashboard specific to that disk group and provides me the following metrics:

As you can see from the above screenshot I can see various important information about my disk group, and if the heatmap was red for this specific disk group I would be able to easily see why based on the metrics presented to me, in my case my disk group is healthy.

There is another dashboard in vROPS called Capacity Overview which I will cover on another Day-2 Operations post based around capacity reporting, so watch out for that one.

So as you can see there are immediately advantages and disadvantages of using the Health Service over vROPS and vice versa, in my opinion I think both tools are important in day to day operations and being able to use both tools provides you with the toolset to effectively manage your environments easier.

 

Creating a vSAN Cluster without a vCenter Server

I have been asked many times about creating a 3-node vSAN cluster without a vCenter server, the main reason for doing this is that you need to place your vCenter server onto the vSAN datastore but have no where to host the vCenter server until doing so.? The many customers I have spoken to are not aware that they can do this from the command line very easily.? In order to do this you must have installed ESXi 6.0 U2 and enabled SSH access to the host, there are a few steps in order to do this

  1. Configure the vSAN VMKernel Interface
  2. Create the vSAN Cluster
  3. Add the other nodes to the cluster
  4. Claim the disks

Step 1 – Create the VMKernel interface
In order for vSAN to function you need to create a VMKernel Interface on each host, this requires other dependencies such as a vSwitch and a Port Group, so performing this on all three hosts is a must so lets do it in this order, firstly lets create our vSwitch, since vSwitch0 exists for the management network we’ll create a vSwitch1

esxcli network vswitch standard add -v vSwitch1

Once our vSwitch1 is created we then need to add the physical uplinks to our switch, to help identify which uplinks to use we run the following command

esxcli network nic list

This should return details on all the physical network cards on the host for example:

Name??? PCI????????? Driver????? Link Speed????? Duplex MAC Address?????? MTU??? Description
vmnic0? 0000:01:00.0 ntg3??????? Up?? 1000Mbps?? Full?? 44:a8:42:29:fe:98 1500?? Broadcom Corporation NetXtreme BCM5720 Gigabit Ethernet
vmnic1? 0000:01:00.1 ntg3??????? Up?? 1000Mbps?? Full?? 44:a8:42:29:fe:99 1500?? Broadcom Corporation NetXtreme BCM5720 Gigabit Ethernet
vmnic2? 0000:02:00.0 ntg3??????? Down 0Mbps????? Half?? 44:a8:42:29:fe:9a 1500?? Broadcom Corporation NetXtreme BCM5720 Gigabit Ethernet
vmnic3? 0000:02:00.1 ntg3??????? Down 0Mbps????? Half?? 44:a8:42:29:fe:9b 1500?? Broadcom Corporation NetXtreme BCM5720 Gigabit Ethernet
vmnic4? 0000:82:00.0 ixgbe?????? Up?? 10000Mbps? Full?? a0:36:9f:78:94:cc 1500?? Intel Corporation Ethernet Controller 10 Gigabit X540-AT2
vmnic5? 0000:82:00.1 ixgbe?????? Up?? 10000Mbps? Full?? a0:36:9f:78:94:ce 1500?? Intel Corporation Ethernet Controller 10 Gigabit X540-AT2
vmnic6? 0000:04:00.0 ixgbe?????? Up?? 10000Mbps? Full?? a0:36:9f:78:94:c4 1500?? Intel Corporation Ethernet Controller 10 Gigabit X540-AT2
vmnic7? 0000:04:00.1 ixgbe?????? Up?? 10000Mbps? Full?? a0:36:9f:78:94:c6 1500?? Intel Corporation Ethernet Controller 10 Gigabit X540-AT2

For my cluster I am going to add vmnic5 to the vSwitch1 so for this I run the following command:

esxcli network vswitch standard uplink add -v vSwitch1 -u vmnic5

Now that we now have our uplink connected to vSwitch1 we need to configure a portGroup for vSAN, for this I am calling my portGroup name “vSAN”

esxcfg-vswitch -A vSAN vSwitch1

Now we need to create out VMKernel interface with an IP Address (192.168.100.1 for Host 1), Subnet Mask and assign it to the “vSAN” portGroup

esxcfg-vmknic -a -i 192.168.100.1 -n 255.255.255.0 -p vSAN

We validate our VMKernel Interface by running the following command:

[root@se-emea-vsan01:~] esxcfg-vmknic -l
Interface? Port Group/DVPort/Opaque Network??????? IP Family IP Address????????????????????????????? Netmask???????? Broadcast?????? MAC Address?????? MTU???? TSO MSS?? Enabled Type??????????????? NetStack
vmk0?????? Management Network????????????????????? IPv4????? 172.16.101.1??????????????????????????? 255.255.252.0?? 172.16.103.255? 44:a8:42:29:fe:98 1500??? 65535???? true??? STATIC????????????? defaultTcpipStack
vmk1?????? vSAN??????????????????????????????????? IPv4????? 192.168.100.1?????????????????????????? 255.255.255.0?? 192.168.100.255 00:50:56:6a:5d:06 1500??? 65535???? true??? STATIC????????????? defaultTcpipStack

In order to add the VMKernel interface to vSAN we need to run the following command:

esxcli vsan network ip add -i vmk1

Repeat the above steps on the two remaining hosts that you wish to participate in the cluster

Step 2 – Creating the cluster
Once we have all the VMKernel interfaces configured on all hosts, we now need to create a vSAN Cluster on the first host, to do this we run the following command

esxcli vsan cluster new

Once completed we can get our vSAN Cluster UUID by running the following command:

[root@se-emea-vsan01:~] esxcli vsan cluster get
Cluster Information
?? Enabled: true
?? Current Local Time: 2016-11-21T15:17:57Z
?? Local Node UUID: 582a29ea-cbfc-195e-f794-a0369f7894c4
?? Local Node Type: NORMAL
?? Local Node State: MASTER
?? Local Node Health State: HEALTHY
?? Sub-Cluster Master UUID: 582a2bba-0fd8-b45a-7460-a0369f749a0c
?? Sub-Cluster Backup UUID: 582a29ea-cbfc-195e-f794-a0369f7894c4
?? Sub-Cluster UUID: 52bca225-0520-fd68-46c4-5e7edca5dfbd
?? Sub-Cluster Membership Entry Revision: 6
?? Sub-Cluster Member Count: 1
?? Sub-Cluster Member UUIDs: 582a29ea-cbfc-195e-f794-a0369f7894c4
?? Sub-Cluster Membership UUID: d2dd2c58-da70-bbb9-9e1a-a0369f749a0c

Step 3 – Adding the other nodes to the cluster
From the remaining hosts run the following command adding them to the newly created cluster

esxcli vsan cluster join -u 52bca225-0520-fd68-46c4-5e7edca5dfbd

You can verify that the nodes have successfully joined the cluster by running the same command we ran earlier noting that the Sub-Cluster Member Count has increased to 3 and it also shows the other sub cluster UUID Members:

[root@se-emea-vsan01:~] esxcli vsan cluster get
Cluster Information
?? Enabled: true
?? Current Local Time: 2016-11-21T15:17:57Z
?? Local Node UUID: 582a29ea-cbfc-195e-f794-a0369f7894c4
?? Local Node Type: NORMAL
?? Local Node State: MASTER
?? Local Node Health State: HEALTHY
?? Sub-Cluster Master UUID: 582a2bba-0fd8-b45a-7460-a0369f749a0c
?? Sub-Cluster Backup UUID: 582a29ea-cbfc-195e-f794-a0369f7894c4
?? Sub-Cluster UUID: 52bca225-0520-fd68-46c4-5e7edca5dfbd
?? Sub-Cluster Membership Entry Revision: 6
?? Sub-Cluster Member Count: 3
?? Sub-Cluster Member UUIDs: 582a29ea-cbfc-195e-f794-a0369f7894c4, 582a2bf8-4e36-abbf-5318-a0369f7894d4, 582a2c3b-d104-b96d-d089-a0369f78946c
?? Sub-Cluster Membership UUID: d2dd2c58-da70-bbb9-9e1a-a0369f749a0c

Step 4 – Claim Disks
Our cluster is now created and we need to claim the disks in each node to be used by vSAN, in order to do this we first of all need to identify which disks are to be used by vSAN as a Cache Disk and as Capacity Disks, and obviously the number of disk groups, to show the disk information for the disks in the host run the following command:

esxcli storage core device list

This will produce an output similar to the following where we can identify the NAA ID for each device:

naa.500003965c8a48a4
?? Display Name: TOSHIBA Serial Attached SCSI Disk (naa.500003965c8a48a4)
?? Has Settable Display Name: true
?? Size: 381554
?? Device Type: Direct-Access
?? Multipath Plugin: NMP
?? Devfs Path: /vmfs/devices/disks/naa.500003965c8a48a4
?? Vendor: TOSHIBA
?? Model: PX02SMF040
?? Revision: A3AF
?? SCSI Level: 6
?? Is Pseudo: false
?? Status: on
?? Is RDM Capable: true
?? Is Local: true
?? Is Removable: false
?? Is SSD: true
?? Is VVOL PE: false
?? Is Offline: false
?? Is Perennially Reserved: false
?? Queue Full Sample Size: 0
?? Queue Full Threshold: 0
?? Thin Provisioning Status: yes
?? Attached Filters:
?? VAAI Status: unknown
?? Other UIDs: vml.0200000000500003965c8a48a450583032534d
?? Is Shared Clusterwide: false
?? Is Local SAS Device: true
?? Is SAS: true
?? Is USB: false
?? Is Boot USB Device: false
?? Is Boot Device: false
?? Device Max Queue Depth: 64
?? No of outstanding IOs with competing worlds: 32
?? Drive Type: physical
?? RAID Level: NA
?? Number of Physical Drives: 1
?? Protection Enabled: false
?? PI Activated: false
?? PI Type: 0
?? PI Protection Mask: NO PROTECTION
?? Supported Guard Types: NO GUARD SUPPORT
?? DIX Enabled: false
?? DIX Guard Type: NO GUARD SUPPORT
?? Emulated DIX/DIF Enabled: false

In my setup I want to create two disk groups per host consisting of 4 capacity devices plus my cache so to create one disk group I run the following command:

esxcli vsan storage add -s <naa for cache disk> -d <naa for capacity disk 1> -d <naa for capacity disk 2> -d <naa for capacity disk 3> -d <naa for capacity disk 4>

Once you have performed the above on each of your hosts, your vSAN cluster is deployed with storage and you can now deploy your vCenter appliance onto the vSAN datastore where then you can manage your vSAN License, Storage Policies, switch on vSAN Services such as iSCSI, health service and performance services as well as start to deploy virtual machines