Tagged in: vSphere

Uila – A view into your data center.

I recently had the chance to get a product overview of Uila.

 

What product does Uila have?

 

“Uila’s Application-Centric Infrastructure Monitoring Monitoring helps align business and IT Operations goals in a single product by providing IT Operations with the application visibility and correlated network, compute and storage insights for Private, Public and Hybrid Cloud-based Data Centers (such as VMWare, Amazon AWS, Microsoft Azure, Google Cloud, Docker Container, etc.).  “

 

Ever need to see why your developer or application owner are indicating your virtual environment is causing performance issues to their application?? Of course, it’s not VMware, but it couple be something between the virtualization layer and the application layer causing performance issues.

 

 

 

 

Sounds Great. But what does that mean? How does it work?

 

 

 

 

How do I see into my environment ?

 

 

 

Uila Shows real time, and backwards in time so you can click and dig in.

 

 

Then you can dig into Application Analysis to see what is causing the problem.

 

 

Once you find the problem, in this case Oracle_11g-n1 looks suspect..  You can dig farther in.

 

 

 

Of course you can do a root cause view.

 

And find the problem.

 

 

 

 

For more information on Uila.

 

Videos

 

Tech Field Day Presentation by Uila – Company Overview
https://www.youtube.com/watch?v=Pgzx14PRpOs
http://vimeo.com/202704462

Tech Field Day Presentation by Uila – Application Visibility and Root Cause
https://www.youtube.com/watch?v=d1PeWccQZ5g
http://vimeo.com/202698494

Tech Field Day Presentation by Uila – Infrastructure Monitoring
https://www.youtube.com/watch?v=HjH2CPdFT0s
http://vimeo.com/202701527

Tech Field Day Presentation by Uila – End User Experience Monitoring
https://www.youtube.com/watch?v=k-1ExHbRGgI
http://vimeo.com/202702132

Tech Field Day Presentation by Uila – Virtual Network Monitoring
https://www.youtube.com/watch?v=ufqMYFVBlMA
http://vimeo.com/202702496

 

Data Sheet
http://uila.com/download/datasets/920/Uila_Datasheet_FullStack_Virtualization_Apr_2017.pdf

 

Check them out.

 

Thanks

 

Roger Lund

My vSphere 6.5 Upgrade Checklist – painful : Repost

I ran across this post when reviewing VMware vSphere 6.5 upgrade best practices via google.

I like to read about others and what they experience while upgrading prior to running through a upgrade myself.

 

by Michael White

https://notesfrommwhite.net/2017/01/29/my-vsphere-6-5-upgrade-checklist-painful/

 

“Yes, this has taken me a while to get too. And it took me a while to do as well. Now that I work at Veeam, and while I have used Veeam products for many years, now I need to work my lab like a Veeam customer. vSphere 6.5 is a big deal for me, and it has a lot of new stuff in it that I am looking forward to so I have been waiting anxiously for Update 1 for Veeam that supports 6.5. It is here now but there is still one more tool of mine that is not 6.5 capable but I am tired of waiting for it. It is the VMware Infrastructure Navigator (VIN) and I find it most useful. BTW, I do this article, and then with it as a plan I do the upgrade. After that I update the article with anything I learned and then finally I publish. I will keep in this article the problems I had in case it helps someone.”

I thought it was worth the time to read.

Roger L

 

Install VMware tools on Centos 7

I was standing up some Centos 7 boxes in VMware vSphere. And I figured I would blog on the steps to install VMware Tools.

 

The below Steps are taken from http://partnerweb.vmware.com/GOSIG/CentOS_7.html

 

 “CentOS 7 documentation covers information on how to install the operating system in a virtual machine. For additional information about the operating system, refer to the instructions included in the installation media.

CentOS 7 documentation includes the following topics:

Installation Instructions

To install CentOS 7 in a virtual machine you can use either the standard CentOS distribution CD or the boot floppy/network method. The following installation instructions are for standard distribution CD.

Prerequisites

Before you begin, verify that the following tasks are complete:

Installation Steps

  1. Insert the CentOS 7 CD-ROM in the CD-ROM drive.
  2. Power on the virtual machine to start installing CentOS 7.
  3. Follow the prompts to complete the installation.
  4. Set the storage location for installation. In the INSTALLATION SUMMARY screen, in the STORAGE session area, select INSTALLATION DESTINATION.
  5. Change the Base Environment and select Add-Ons to install. In the INSTALLATION SUMMARY screen, in the SOFTWARE session area, click SOFTWARE SELECTION.CentOS 7 includes Open VMware Tools. The default Base Environment is Minimal install, which only has basic functionality.
    • For Minimal install and Virtualization Host environments, Open VMware Tools is not available during installation.
      After CentOS 7 installation, to install Open VMware Tools, using root privileges, run the command:
      # yum install open-vm-tools
    • For other types of Base Environments, to install Open VMware Tools, select the Guest Agents Add-On.
    • If this Add-On is not listed, the Base Environment already includes Open VMware Tools and installs it by default.
  6. Click Done.
  7. Click Begin Installation to continue.
  8. Set root password and create new users, as needed, in the CONFIGURATION screen.

VMware Tools in an CentOS 7 Guest

Use the guest OS provided Open VM Tools or install VMware Tools, as needed.

Open VM Tools

Open VM Tools is the open source implementation of VMware Tools and consist of a suite of virtualization utilities that improves the functionality, administration, and management of virtual machines on VMware hypervisors. VMware recommends using the Open VM Tools redistributed by the operating system vendors. To use Open VM Tools:

  1. Add the vmhgfs Driver
    If you use the file sharing feature by using Shared Folders in VMware Workstation and Fusion, install the vmhgfs driver in the virtual machine. This driver is not included inbox in the operating system. Installing the additional vmhgfs driver does not disturb the other inbox VMware drivers or Open VMware Tools. To install this driver:

    1. Install Open VMware Tools.
    2. Install the traditional TAR Format VMware Tools that is bundled with VMware Workstation or Fusion products.
  2. Add the deployPkg Tools Plug-in
    If you are using the virtual machine as a template or if it will be protected by SRM (Site Recovery Manager), then install the deployPkg Tools plug-in. To install this plug-in:

    1. Create a file, /etc/yum.repos.d/vmware-tools.repo, with the following content:
      [fusion_builder_container hundred_percent="yes" overflow="visible"][fusion_builder_row][fusion_builder_column type="1_1" background_position="left top" background_color="" border_size="" border_color="" border_style="solid" spacing="yes" background_image="" background_repeat="no-repeat" padding="" margin_top="0px" margin_bottom="0px" class="" id="" animation_type="" animation_speed="0.3" animation_direction="left" hide_on_mobile="no" center_content="no" min_height="none"][vmware-tools]
      name = VMware Tools
      baseurl = http://packages.vmware.com/packages/rhel7/x86_64/
      enabled = 1
      gpgcheck = 1
    2. Install the package:
      $ sudo yum install open-vm-tools-deploypkg
      See knowledge base article 2075048, Installing the deployPkg plug-in in a Linux virtual machine, at http://kb.vmware.com/kb/2075048.

For additional information, see:

VMware Tools

For additional information on VMware Tools, see knowledge base article 1014294, General VMware Tools installation instructions, at http://kb.vmware.com/kb/1014294.

Knowledge Base Articles for CentOS 7

The following link refers to knowledge base articles on operating system specific issues. See VMware Knowledge Base for a list of known issues about the operating system.

VMware Compatibility Guide

The VMware Compatibility Guide Web site lists supported guest and host operating systems and provides related support information.”

 

 

Here we go.

 

  1. Login to the linux guest via putty.
  2. Login as root:
  3. [email protected]’s password. I entered the password.
  4. # yum install open-vm-tools -y

Then I wanted to update Centos as well.

 

  1. yum update -y
  2. shutdown -r -t now

 

Now lets look at the VM in the vSphere client.

 

 

 

 

centos7_vmware_tools_vm_selection centos7_vmware_tools_install

Now we have Running VMware Tools!

 

 

Roger L[/fusion_builder_column][/fusion_builder_row][/fusion_builder_container]

Countdown to VMworld 2015 San Francisco

200Days
10Hours
10Minutes
10Seconds

Repost : with a few additions: What is my SSO Domain Name & Site Name?

I had to use this today after forgetting a little used VMware Workstation Lab’s vSphere 6 sso domain.

 

I ended up finding this blog post, and i’m going to refer to it in my blog post as well.

vCenter Server 6.0 Tidbits Part 2: What is my SSO Domain Name & Site Name?

 

You will find it in the following two configuration files:

Windows:

C:\ProgramData\VMware\vCenterServer\cfg\install-defaults\vmdir.domain-name

VCSA:

/etc/vmware/install-defaults/vmdir.domain-name

You have to enable shell via ssh to vcenter first.

login to vcenter via ssh. I enabled this by default.

If not do the below steps or skip this section if ssh is enabled.

—————————————-

How to enable ssh on the vcenter appliance

 

by 

1. Open the console of the appliance using in this case the vsphere client.

2. Press F2 and log in as root.

3. Notice the choices and select Troubleshooting Mode Options.

4. Notice the two options. Select Enable SSH.

5.  Press Enter to enable it.

—————————————-

Command> shell.set –enabled True
Command> shell

localhost:~ # vi /etc/vmware/install-defaults/vmdir.domain-name

This returned

ssolocal.local

Thus I knew I had to login to [email protected] to vcenter.

P.S. Document your lab login and sso information… :0)

Roger L

Reset VMware vCenter Appliance 6 root password

If your like me, you often forget passwords or domains you setup in your lab environments.

Here are a blog post I found useful when playing in my lab.

 

VMware vCenter Server Appliance 5.5 root account locked out after password expiration (2069041)

KB: 2069041
KB: 2069041
Updated: Aug 21, 2015Categories:
Alerts
Troubleshooting
Languages:
English

Product(s):
VMware vCenter Server Appliance

Product Version(s):
VMware vCenter Server Appliance 5.5.x

 

 

“To reactivate the root account:

  1. Reboot the vCenter Server appliance using the vSphere Client.
  2. When the GRUB bootloader appears, press the spacebar to disable autoboot.Note: If the time between when you power on the virtual machine and when it exits the BIOS or EFI and launches the guest operating system is too short, you can adjust the delay. For more information, see Delay the Boot Sequence in the VMware vSphere 5.5 Documentation guide.
  3. Type p to access the appliance boot options.
  4. Enter the GRUB password.

:

 

Now I locked my self out trying passwords. Thus when you hit p you have to type your password. But it doesn’t lock you out at this point. Thus I found my password after a bit of work.

 

Entire write up by VMware here.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2069041

 

Roger L

Unitrends Free Edition. Protecting your assets with Asset Protection and Job Creation.

Yesterday I write on Installing and Configuring Unitrends free edition. Today I will cover protecting your assets with Asset Protection. Then we will go over Job Creation. This allows you to have a backup of your VM’s for free!

 

Requirements:

For this scenario we will be using vCenter 5.5.

 

And we are off!

 

1. Browse to the UI.

unitrends free edition UI

 

2. Close the welcome to Unitrends free.

unitrends free edition ui welcome

3. Navigate to Configure.

unitrends free edition ui configure

4. Click on the Protected Assets Tab.

unitrends free edition ui configure protected assets

5. Click Add, and select Virtual Host.

unitrends free edition ui configure protected assets add virtual host

 

6. Put in your vCenter information and click save.

unitrends free edition ui configure protected assets add virtual host details

7. Now navigate to Protect.

unitrends free edition ui protect

8. Highlight your vCenter

unitrends free edition ui protect select vcenter

9. Check the box next to the VM you would like to Backup.

unitrends free edition ui protect select vcenter select vm

10. Click Backup

unitrends free edition ui protect backup

11. A new window will popup, titled Create Backup Job.

unitrends free edition ui protect create backup jobJPG

12. Click Define Job Settings.

unitrends free edition ui protect create backup job define

For now we are going to just run this job once. This is called a on demand job.

13. Under Schedule, Select when to run this job: check Now, and save.

unitrends free edition ui protect create backup job define on demand

 

Right away a job success window pops up.

unitrends free edition ui protect job success

 

Lets take a look at the job to verify the job’s running status.

14. Click view Jobs.

unitrends free edition ui protect jobs running

 

15. Click on the job, and click View Details.

unitrends free edition ui protect jobs running view details

 

Once it completes you will see a Successful Status.

unitrends free edition ui protect job finished 1

Congrats! You have just protected your first VM!

 

 

Roger Lund

Installing and Configuring Unitrends free edition

Last week I wrote on Unitrends offers free backup’s with Unitrends Free. Unitrends is a leader in the backup space. And they recently announced a free edition.  Today I am going to cover deploying the software via a appliance, and the post deployment configuration. This is our first Step to backing up our virtual environment, for free!

Once we finish this, we will be ready to login to the UI, setup asset protection, and create a new backup job.

 

Before we start:

This requires a windows machine to launch the setup with .net framework 4.0. Note this does not install on the device you run it from, but deploy’s a appliance.

 

 

Ready, get set, and GO!

 

1. Run the unitrends Installer.

unitrends free edition exe

2. Fill out the vCenter information, and click Next.

unitrends free edition vcenter

3. Next name the appliance and select the VMware host and Datastore and click Next.

unitrends free edition vcenter host and datacenter

 

4. Now select your network, and give the appliance the correct network information for your environment, and click next.

unitrends free edition applaince network config

5. Now Configure the disk size, select the datastore, and disk provision method, and click install.

unitrends free edition disk config

6. Now browse to the IP Address, and proceed by ignoring any SSL warning, and agree to the agreement.

unitrends accept

7. Next we will setup the Date and time on the appliance. Once you have made any adjustments click next.

unitrends free edition date and time

8. Now we set the hostname, domain name, and password. Click Next.

unitrends free edition hostname and password

9. Next we set the mail server information and click Finish.

unitrends free edition email

On the next write up. I will cover protecting assets and creating jobs.

Roger Lund

Getting Opvizor Working by Michael White worth a read.

Michael White another vExpert did a great write up on Opvizor www.opvizor.com

Opvizor has engaged the VMware vExpert program to allow us to dive into the program. Michael’s write up shows how to install the product.

 

Getting Opvizor Working – and is it interesting or what!

 

“If you watch the video on their home page you will see what I did and perhaps be as interested as I was.  Essentially their product compares your environment against best practices from VMware and or NetApp and then will let you know how your environment differs and provide you with the info to fix it.”

 

He then walks you through the installation.

I will dive into the inside of Opvizor in my a follow up post.

Roger Lund

VMware Virtual SAN 6.0

The following Blog post is about VMware VSAN or Virtual San. http://www.vmware.com/products/virtual-san

 

The following post was made with pre GA , Beta content.

All performance numbers are subject to final benchmarking results. Please refer to guidance published at GA

All Content and media is from VMWare, as part of the blogger program.

Please also read vSphere 6 – Clarifying the misinformation http://blogs.vmware.com/vsphere/2015/02/vsphere-6-clarifying-misinformation.html

 

Here is the published What’s New: VMware Virtual SAN 6.0 http://www.vmware.com/files/pdf/products/vsan/VMware_Virtual_SAN_Whats_New.pdf

Here is the published VMware Virtual SAN 6.0 http://www.vmware.com/files/pdf/products/vsan/VMware_Virtual_SAN_Datasheet.pdf

 

Whats New?

 

vsan01

 

Disk Format

  • New On-Disk Format
  • New delta-disk type vsanSparse
  • Performance Based snapshots and clones

VSAN 5.5 to 6.0

  • In-Place modular rolling upgrade
  • Seamless In-place Upgrade
  • Seamless Upgrade Rollback Supported
  • Upgrade performed from RVC CLI
  • PowerCLI integration for automation and management

 

Disk Serviceability Functions

  • Ability to manage flash-based and magnetic devices.
  • Storage consumption models for policy definition
  • Default Storage Policies
  • Resync Status dashboard in UI
  • VM capacity consumption per VMDK
  • Disk/Disk group evacuation

VSAN Platform

  • New Caching Architecture for all-flash VSAN
  • Virtual SAN Health Services
  • Proactive Rebalance
  • Fault domains support
  • High Density Storage Systems with Direct Attached Storage
  • File Services via 3rd party
  • Limited support hardware encryption and checksum

 

Virtual SAN Performance and Scale Improvements

 

 

2x VMs per host

  • Larger Consolidation Ratios
  • Due to increase of supported components per hosts
  • 9000 Components per Host

 

62TB Virtual Disks

  • Greater capacity allocations per VMDK
  • VMDK >2TB are supported

Snapshots and Clone

  • Larger supported capacity of snapshots and clones per VMs
  • 32 per Virtual Machine

Host Scalability

  • Cluster support raised to match vSphere
  • Up to 64 nodes per cluster in vSphere

VSAN can scale up to 64 nodes

 

Enterprise-Class Scale and Performance

vsan02

VMware Virtual SAN : All-Flash

Flash-based devices used for caching as well as persistence

Cost-effective all-flash 2-tier model:oCache is 100% write: using write-intensive, higher grade flash-based devices
Persistent storage: can leverage lower cost read-intensive flash-based devices

Very high IOPS: up to 100K(1)IOPS/Host
Consistent performance with sub-millisecond latencies

 

vsan05

 

 

30K IOPS/Host100K IOPS/Hostpredictable sub-millisecond latency

 

Virtual SAN FlashCaching Architectures

 

vsan06

 

 

All-FlashCache Tier Sizing

Cache tier should have 10% of the anticipated consumed storage capacity

 Measurement Requirements Values
Projected VM space usage 20GB
Projected number of VMs 1000
Total projected space consumption per VM 20GB x 1000 = 20,000 GB = 20 TB
Target flash cache capacity percentage 10%
Total flash cache capacity required 20TB x .10 = 2 TB

 

  • Cache is entirely write-buffer in all-flash architecture
  • Cache devices should be high write endurance models: Choose 2+ TBW/day or 3650+/5 year
  • Total cache capacity percentage should be based on use case requirements.

–For general recommendation visit the VMware Compatibility Guide.

–For write-intensive workloads a higher amount should be configured.

–Increase cache size if expecting heavy use of snapshots

 

New On-Disk Format

 

  • Virtual SAN 6.0 introduces a new on-disk format.
  • The new on-disk format enables:

–Higher performance characteristics

–Efficient and scalable high performance snapshots and clones

–Online migration to new (RVC only)

  • The object store will continue to mount the volumes from all hosts in a cluster and presents them as a single shared datastore.
  • The upgrade to the new on-disk format is optional; the on-disk format for Virtual SAN 5.5 will continue to be supported

 

Performance Snapshots and Clones

 

  • Virtual SAN 6.0 new on-disk format introduces a new VMDK type

–Virtual SAN 5.5 snapshots were based on vmfsSparse (redo logs)

  • vsanSparse based snapshots are expected to deliver performance comparable to native SAN snapshots.

–vsanSparse takes advantage of the new on-disk format writing and extended caching capabilities to deliver efficient performance.

  • All disks in a vsanSparse disk-chain need to be vsanSparse (except base disk).

–Cannot create linked clones of a VM with vsanSparse snapshots on a non-vsan datastore.

–If a VM has existing redo log based snapshots, it will continue to get redo log based snapshots until the user consolidates and deletes all current snapshots.

 

 

 

 

Hardware Requirements

 

vsan03

 

Flash Based Devices In Virtual SAN hybrid ALL read and write operations always go directly to the Flash tier.
Flash based devices serve two purposes in Virtual SAN hybrid architecture

1.Non-volatile Write Buffer (30%)
–Writes are acknowledged when they enter prepare stage on the flash-based devices.
–Reduces latency for writes2.

2. Read Cache (70%)
– Cache hits reduces read latency
– Cache miss – retrieve data from the magnetic devices

 

Flash Based Devices In Virtual SAN all-flash read and write operations always go directly to the Flash devices.

Flash based devices serve two purposes in Virtual SAN All Flash:

1 .Cache Tier
–High endurance flash devices.
–Listed on VCG2.
2. Capacity Tier
–Low endurance flash devices
–Listed on VCG
Network

•1Gb / 10Gb supported
–10Gb shared with NIOC for QoS will support most environments
–If 1GB then recommend dedicated links for Virtual SAN
–Layer 3network configuration supported in 6.0

•Jumbo Frames will provide nominal performance increase
–Enable for greenfield deployments
–Enable in large deployments to reduce CPU overhead

•Virtual SAN supports both VSS & VDS–NetIOC requires VDS
•Network bandwidth performance has more impact on host evacuation, rebuild times than on workload performance

 

High Density Direct Attached Storage

 

vsan04

 

 

–Manage disks in enclosures – helps enable blade environment
–Flash acceleration provided on the server or in thesubsystem
–Data services delivered via the VSAN Data Services and platform capabilities
–Direct attached and disks (flash devices, and magnetic devices) are Supports combination of direct attached disks and high density attached disks (SSDs and HDDs) per disk group.

 

Users are expected to configure the HDDAS switch such that each disk is only seen by one host.

–VSAN protects against misconfigured HDDASs (a disk is seen by more than 1 host).
–The owner of a disk group can be explicitly changedby unmounting and restamping the disk group from the new owner.

•If a host who own a disk group crashes, manual re-stamping can be done on another host

.–Supported HDDASs will be tightly controlled by the HCL (exact list TBD).•Applies to HDDASs and controllers

 

FOLLOW the VMware HCL. www.vmware.com/go/virtualsan-hcl

 

Upgrade

 

  • Virtual SAN 6.0 has a new on disk format for disk groups and exposes a new delta-disk type, so upgrading from 1.0 to 2.0 involves more than upgrading the ESX/VC software.

Upgrades are performed in multiple phases

Phase 1: Fresh deployment or upgrade of to vSphere 6.0

vCenter Server

ESXi Hypervisor

Phase 2: Disk format conversion (DFC)

Reformat disk groups

Object upgrade

Disk/Disk Group Evacuation

  • In Virtual SAN 5.5 in order to remove a disk/disk group without data lost, hosts were placed in maintenance mode with the full data evacuation mode from all disk/disk groups.
  • Virtual SAN 6.0 Introduces the support and ability to evacuate data from individual disk/disk groups before removing a disk/disk group from the Virtual SAN.
  • Supported in the UI, esxcli and RVC.

Check box in the “Remove disk/disk group” UI screen

vsanexample

 

Disks Serviceability

 

Virtual SAN 6.0 introduces a new disk serviceability feature to easily map the location of magnetic disks and flash based devices from the vSphere Web Client.

vsanexample2

  • Light LED on failures
  • When a disk hits a permanent error, it can be challenging to find where that disk sits in the chassis to find and replace it.
  • When SSD or MD encounters a permanent error, VSAN automatically turns the disk LED on.
  • Turn disk LED on/off
  • User might need to locate a disk so VSAN supports manually turning a SSD or MD LED on/off.
  • Marking a disk as SSD
  • Some SSDs might not be recognized as SSDs by ESX.
  • Disks can be tagged/untagged as SSDs
  • Marking a disk as local
  • Some SSDs/MDs might not be recognized by ESX as local disks.
  • Disks can be tagged/untagged as local disks.

 

Virtual SAN Usability Improvements

  • What-if-APIs (Scenarios)
  • Adding functionality to visualize Virtual SAN datastore resource utilization when a VM Storage Policy is created or edited.

–Creating Policies

–Reapplying a Policy

vsanexample3

 

Default Storage Policies

 

  • A Virtual SAN Default Profile is automatically created in SPBM when VSAN is enabled on a cluster.

–Default Profiles are utilized by any VM created without an explicit SPBM profile assigned.

vSphere admins to designate a preferred VM Storage Policy as the preferred default policy for the Virtual SAN cluster

 

vsanexample4

  • vCenter can manage multiple vsanDatastores with different sets of requirements.
  • Each vsanDatastore can have a different default profile assigned.

Virtual Machine Usability Improvements

  • Virtual SAN 6.0 adds functionality to visualize Virtual SAN datastore resource utilization when a VM Storage Policy is created or edited.
  • Virtual SAN’s free disk space is raw capacity.

–With replication, actual usable space is lesser.

  • New UI shows real usage on

–Flash Devices

–Magnetic Disks

Displayed in the vSphere Web Client and RVC

vsanexample5

 

Virtual Machine >2TB VMDKs

 

  • In VSAN 5.5, the max size of a VMDK was limited to 2TB.

–Max size of a VSAN component is 255GB.

–Max number of stripes per object was 12.

  • In VSAN 6.0 the limit has been increased to allow VMDK up to 62TB.

–Objects are still striped at 255GB.

  • 62TB limit is the same as VMFS and NFS so VMDK can be

 

vsanexample6

 

There it is. I tried to lay it out as best I could.

Want to try it? Try the Virtual SAN Hosted Evaluation https://my.vmware.com/web/vmware/evalcenter?p=vsan6-hol

 

What’s New in Virtual SAN 6

Learn how to deploy, configure, and manage VMware’s latest hypervisor-converged storage solution.

– See more at: https://my.vmware.com/web/vmware/evalcenter?p=vsan6-hol#sthash.OcuO1gXQ.dpuf

 

Roger Lund