<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>VSAN6.7 on blogs.hareeshkg.com</title>
    <link>https://blogs.hareeshkg.bid/categories/vsan6.7/</link>
    <description>Recent content in VSAN6.7 on blogs.hareeshkg.com</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>Copyright © blogs.hareeshkg.com 2025 reserved</copyright>
    <lastBuildDate>Sun, 08 Dec 2019 02:37:07 +0000</lastBuildDate><atom:link href="https://blogs.hareeshkg.bid/categories/vsan6.7/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>WSFC with Native Shared Disks on vSAN</title>
      <link>https://blogs.hareeshkg.bid/post/wsfc-with-native-shared-disks-on-vsan/</link>
      <pubDate>Sun, 08 Dec 2019 02:37:07 +0000</pubDate>
      
      <guid>https://blogs.hareeshkg.bid/post/wsfc-with-native-shared-disks-on-vsan/</guid>
      <description>
        
          
            &lt;p&gt;With introduction of  vSAN 6.7 U3 / vSphere 6.7 U3  we now have native support for SCSI-3 Persistent reservation on vSAN objects. This means that we no longer need vSAN iSCSI targets for creating  &lt;strong&gt;a&lt;/strong&gt;pplication level clustering services like Windows Server Failover Clusters (WSFC) which needs to share a disk in order to determine ownership across the application cluster.&lt;/p&gt;
&lt;p&gt;This new feature allows for VMs running WSFC to use a shared VMDK on a vSAN datastore  by creating SCSI controllers in physical Mode and then create and share vmdks using independent-persistent presentation mode. This drastically reduces the time in deployment and configuration on WSFC when compared to previous vSAN releases which requires us to configure thru vSAN iSCSI targets and also comes with its overhead .&lt;/p&gt;
          
          
        
      </description>
    </item>
    
    <item>
      <title>How to Re-Config Replication with existing seed on vSAN</title>
      <link>https://blogs.hareeshkg.bid/post/how-to-re-config-replication-with-existing-seed-on-vsan/</link>
      <pubDate>Tue, 02 Oct 2018 02:56:15 +0000</pubDate>
      
      <guid>https://blogs.hareeshkg.bid/post/how-to-re-config-replication-with-existing-seed-on-vsan/</guid>
      <description>
        
          
            &lt;p&gt;I have been asked about re-configuring  replication for a VM without deleting the destination folder for a VM which is already replicated . In a traditional storage , we were simply renaming the folders on the destination datastore (Can be a local or a remote site) , we used to re-name the folder at the target site , perform a force stop replication at source and target site and simply re-configure replication to the same folder using existing seeds to avoid a full-sync between the two sites .&lt;/p&gt;
          
          
        
      </description>
    </item>
    
    <item>
      <title>What is vSAN Support Insight – CEIP?</title>
      <link>https://blogs.hareeshkg.bid/post/what-is-vsan-support-insight-ceip/</link>
      <pubDate>Sat, 15 Sep 2018 11:31:44 +0000</pubDate>
      
      <guid>https://blogs.hareeshkg.bid/post/what-is-vsan-support-insight-ceip/</guid>
      <description>
        
          
            &lt;p&gt;vSAN Support Insight was introduced last year with the release of vSAN 6.6.1 ( VC/ESXi 6.5 U1 Patch 02 and above) . It is a phone home system leveraging the existing vCenter Customer Experience Improvement Program (CEIP). Health, performance, and configuration information for VMware Support and engineering. Once enabled and verified, log information is pushed back to VMware’s Analytics Cloud on a regular cadence approximately every hour . No actual customer data is phoned home and user enter able or identifiable data (Hostnames, VM names, subnets, IP addresses, Mac addresses) are obfuscated . In this blog you will further see what data is seen by VMware support vs your Webclient View .&lt;/p&gt;
          
          
        
      </description>
    </item>
    
    <item>
      <title>How to  Configure vSAN Encryption?</title>
      <link>https://blogs.hareeshkg.bid/post/how-to-configure-vsan-encryption/</link>
      <pubDate>Fri, 24 Aug 2018 17:16:11 +0000</pubDate>
      
      <guid>https://blogs.hareeshkg.bid/post/how-to-configure-vsan-encryption/</guid>
      <description>
        
          
            &lt;p&gt;I have been asked about vSAN encryption a lot these days as the security requirement and standards are exponentially increasing in the IT industry . Data encryption is a key factor to make sure mission critical data are not stolen . Here is a quick and simple guide to configure vSAN-encryption with a Hy-Trust appliance and best practices to deploy and configure encryption cluster with High-Availability .&lt;/p&gt;
&lt;blockquote&gt;
&lt;/blockquote&gt;
&lt;h2 id=&#34;introduction-to-vsan-encryption&#34;&gt;Introduction to vSAN Encryption&lt;/h2&gt;
&lt;p&gt;Here is a pictorial representation of vSAN Encryption work flow which explains different hand shakes which are going to be executed until we finally encrypt the physical disks which are going to be used with vSAN , you may also refer to&lt;a href=&#34;https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.virtualsan.doc/GUID-F3B2714F-3406-48E7-AC2D-3677355C94D3.html&#34;&gt; VMware-official-page&lt;/a&gt; for additional information .&lt;/p&gt;
          
          
        
      </description>
    </item>
    
    <item>
      <title>Troubleshooting vSAN Encryption Deep Dive</title>
      <link>https://blogs.hareeshkg.bid/post/troubleshooting-vsan-encryption-deep-dive/</link>
      <pubDate>Fri, 01 Jun 2018 15:43:56 +0000</pubDate>
      
      <guid>https://blogs.hareeshkg.bid/post/troubleshooting-vsan-encryption-deep-dive/</guid>
      <description>
        
          
            &lt;p&gt;I highly encourage you to check out my previous blog to &lt;a href=&#34;https://blogs.hareeshkg.bid/configure-vsan-encryption&#34;&gt;understand how vSAN encryption&lt;/a&gt; works before you jump into troubleshooting problems with vSAN and a KMS server .&lt;/p&gt;
&lt;p&gt;This blog should give you a general approach towards troubleshooting problems with vSAN-encryption and also be able to look at a specific log location in order to isolate and fix a specific problem . I have also included certain test-case scenario to see how the logging looks on the host when there is an issue with vSAN-encryption .&lt;/p&gt;
          
          
        
      </description>
    </item>
    
    <item>
      <title>How to troubleshoot issues with vSAN  Storage policy compliance and VASA Providers ?</title>
      <link>https://blogs.hareeshkg.bid/post/how-to-troubleshoot-issues-with-vsan-storage-policy-compliance-and-vasa-providers/</link>
      <pubDate>Sun, 06 May 2018 15:00:31 +0000</pubDate>
      
      <guid>https://blogs.hareeshkg.bid/post/how-to-troubleshoot-issues-with-vsan-storage-policy-compliance-and-vasa-providers/</guid>
      <description>
        
          
            &lt;p&gt;At many times we wonder why we are not able to re-apply policy on a vSAN object or a virtual machine , it may be grayed out and many VMs on the vSAN datastore shows up as non-compliant .  Here is a complete guide which helps you understanding the role and importance of the VASA providers in a vSAN environment ,the difference between the latest vSAN 6.7 VP and previous versions and troubleshooting methods to fix VASA issues .&lt;/p&gt;
          
          
        
      </description>
    </item>
    
    <item>
      <title>Troubleshooting vSAN cluster partition vSAN 6.7 and vSAN 6.6</title>
      <link>https://blogs.hareeshkg.bid/post/troubleshooting-vsan-cluster-partition-vsan-67-and-vsan-66/</link>
      <pubDate>Thu, 27 Jul 2017 16:13:25 +0000</pubDate>
      
      <guid>https://blogs.hareeshkg.bid/post/troubleshooting-vsan-cluster-partition-vsan-67-and-vsan-66/</guid>
      <description>
        
          
            &lt;p&gt;Here are the troubleshooting Steps to resolve Unicastagent issues on vSAN cluster post upgrade usually from vSAN 6.1 / 6.2 / 6.5 to vSAN to 6.6  6.50d and below as we no longer use multicast from version 6.7 and unicastagent list is not updated with correct details on one or more hosts and you also vSAN network partition on one or more hosts .&lt;/p&gt;
&lt;p&gt;In these cases you will need to manually add the unicastagent address list on all hosts part of the cluster , follow thru the steps listed below .&lt;/p&gt;
          
          
        
      </description>
    </item>
    
  </channel>
</rss>
