<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>sureshsiwach Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>sureshsiwach Tracker</description>
    <pubDate>Thu, 23 Nov 2023 12:39:45 GMT</pubDate>
    <dc:date>2023-11-23T12:39:45Z</dc:date>
    <item>
      <title>How to Achive One device One HBA to one Path</title>
      <link>https://communities.vmware.com/t5/vSphere-Storage-Discussions/How-to-Achive-One-device-One-HBA-to-one-Path/m-p/1844275#M16426</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is scenario where storage Admin messed up the configuration. They have presented 1500-1600 path which is more then our limit 1024. Now I can see few devices from 4,3,2,1 HBA's instead of all 4HBA's. It's very risky to change it from storage end.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there any way we can restrict one HBA to all devcie to via one path?(for example if I have 4 HBA and 100 devices then i want every devices should be coming on all 4 HBA's via means 400 path and 100 path per HBA no more).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;BR /&gt;Suresh Siwach&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 02 Nov 2019 09:30:12 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Storage-Discussions/How-to-Achive-One-device-One-HBA-to-one-Path/m-p/1844275#M16426</guid>
      <dc:creator>sureshsiwach</dc:creator>
      <dc:date>2019-11-02T09:30:12Z</dc:date>
    </item>
    <item>
      <title>Live Migration via HCX with in DC (vSphere upgrade)</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Live-Migration-via-HCX-with-in-DC-vSphere-upgrade/m-p/1390147#M14527</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope you are doing good. I need your advice. I have to Upgrade vSphere 5.5 to 6.5 with in data center. In current infra approx 70% of hardware is out of life/support. New infra which i am supposed to receive will have different CPU class so I will be requiring the downtime for approx every VM in ordinary vSphere upgrade process. To avoid downtime i want to use VMware HCX. My concern is "can i use VMware HCX as on premises to on permisis or on prem to cloud and then on prem? Would it be recommended method? Please share if you have any another thought/ idea about same. I am looking forward for your reply.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Suresh Siwach&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 06 May 2018 19:35:58 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Live-Migration-via-HCX-with-in-DC-vSphere-upgrade/m-p/1390147#M14527</guid>
      <dc:creator>sureshsiwach</dc:creator>
      <dc:date>2018-05-06T19:35:58Z</dc:date>
    </item>
    <item>
      <title>Re: Running a PowerCLI script against multiple vCenters at the same time</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Running-a-PowerCLI-script-against-multiple-vCenters-at-the-same/m-p/1299713#M38593</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi LucD,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was also facing the same problem and use the method provided by you. But when I have tested it it was not working then I have open new session of power CLI then its stared working.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note:- Please open a new session after changing your configuration so you get desired output.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Suresh Siwach&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 30 May 2016 05:39:23 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Running-a-PowerCLI-script-against-multiple-vCenters-at-the-same/m-p/1299713#M38593</guid>
      <dc:creator>sureshsiwach</dc:creator>
      <dc:date>2016-05-30T05:39:23Z</dc:date>
    </item>
    <item>
      <title>Re: Error "Host cannot communicate with all other nodes in the VSAN enabeld cluster"</title>
      <link>https://communities.vmware.com/t5/VMware-vSAN-Discussions/Error-quot-Host-cannot-communicate-with-all-other-nodes-in-the/m-p/933360#M2591</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have seen the same issue in my environment while I was configuring VSAN at new site. I have worked for two days to resolving this issue.&amp;nbsp; Now i can advise you how to troubleshoot it.&lt;/P&gt;&lt;P&gt;You can follow the below point. Its up to you if you want to follow step by step or any individual which suits to your infrastructure.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Restart management services. &lt;/P&gt;&lt;P&gt;2. Restart ESXI host.&lt;/P&gt;&lt;P&gt;3. Login on ESXI and try to ping the IPs which you are using for handle VSAN traffic.&lt;/P&gt;&lt;P&gt;4. &lt;SPAN style="font-size: 13.3333330154419px;"&gt;Recreation of virtual adapter, use for VSAN traffic. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;5. &lt;SPAN style="font-size: 13.3333330154419px;"&gt;Recreation of Vlans(Port Group)use for VSAN. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;6. &lt;SPAN style="font-size: 13.3333330154419px;"&gt;Recreation of &lt;/SPAN&gt;&lt;SPAN style="font-size: 13.3333330154419px;"&gt;DVswitch &lt;SPAN style="font-size: 13.3333330154419px;"&gt;use for VSAN.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333330154419px;"&gt;7. E&lt;/SPAN&gt;&lt;SPAN style="font-size: 13.3333330154419px;"&gt;nable\disable VSAN,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333330154419px;"&gt;8. Recreation and deletion of disk group.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333330154419px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333330154419px;"&gt;If you are following step 3 and you will be successful to ping&amp;nbsp; it. Then approach to your network Team\person to make changes on &lt;SPAN style="font-family: sans-serif; font-size: 10pt;"&gt;physical switch. The ports used for Virtual SAN have multicast enabled. Enabling multicast can be done in one of two way on your physical switches:&lt;/SPAN&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333330154419px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; font-family: sans-serif;"&gt;• Disabling IGMP snooping.&lt;BR /&gt;• Configure IGMP snooping for selective traffic.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; font-family: sans-serif;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; font-family: sans-serif;"&gt;I am pasting a link which can help you more in resolving above issue or other related to VSAN.&amp;nbsp; &lt;A href="https://www.vmware.com/files/pdf/products/vsan/VMware_Virtual_SAN_Quick_Monitoring_Reference_Guide.pdf" title="https://www.vmware.com/files/pdf/products/vsan/VMware_Virtual_SAN_Quick_Monitoring_Reference_Guide.pdf"&gt;https://www.vmware.com/files/pdf/products/vsan/VMware_Virtual_SAN_Quick_Monitoring_Reference_Guide.pdf&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; font-family: sans-serif;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; font-family: sans-serif;"&gt;I was able to perform all step because my infrastructure was in implementation phase. &lt;STRONG&gt;Please consider you infrastructure and then follow the step carefully and at your own risk.&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; font-family: sans-serif;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; font-family: sans-serif;"&gt;Thanks&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; font-family: sans-serif;"&gt;Suresh Siwach&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333330154419px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333330154419px;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 04 Jul 2015 10:53:21 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSAN-Discussions/Error-quot-Host-cannot-communicate-with-all-other-nodes-in-the/m-p/933360#M2591</guid>
      <dc:creator>sureshsiwach</dc:creator>
      <dc:date>2015-07-04T10:53:21Z</dc:date>
    </item>
    <item>
      <title>Re: OVF export fails with timeout error</title>
      <link>https://communities.vmware.com/t5/VI-VMware-ESX-3-5-Discussions/OVF-export-fails-with-timeout-error/m-p/1157073#M59086</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;SPAN style="font-size: 10pt;"&gt;sienna_pb,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have you tried mentioned above. " convert vm disk into thin provision then migrate"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Suresh Siwach&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 Jan 2014 16:44:48 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VI-VMware-ESX-3-5-Discussions/OVF-export-fails-with-timeout-error/m-p/1157073#M59086</guid>
      <dc:creator>sureshsiwach</dc:creator>
      <dc:date>2014-01-27T16:44:48Z</dc:date>
    </item>
    <item>
      <title>Re: OVF export fails with timeout error</title>
      <link>https://communities.vmware.com/t5/VI-VMware-ESX-3-5-Discussions/OVF-export-fails-with-timeout-error/m-p/1157071#M59084</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;STRONG style=": ; color: #0000ff; font-size: 12pt;"&gt;failed to export ovf package&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-size: 12pt;"&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style=": ; font-size: 10pt;"&gt;I got above error while i was exporting a VM to OVF. After troubleshooting found i was migrating a VM which was using 250 GB disk over 100GB partition. The VM was having thick disk. Then i have converted thick disk to thin by migrating VM on different datastore. Then exported the VM on that time it was completed successfully.&lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 26 Jan 2014 17:57:08 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VI-VMware-ESX-3-5-Discussions/OVF-export-fails-with-timeout-error/m-p/1157071#M59084</guid>
      <dc:creator>sureshsiwach</dc:creator>
      <dc:date>2014-01-26T17:57:08Z</dc:date>
    </item>
    <item>
      <title>Re: How to find HBA WWN number on ESX server</title>
      <link>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/How-to-find-HBA-WWN-number-on-ESX-server/m-p/162619#M1793</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you want find WWN number of all data store in your infrastructure then please use RVtools. It is best and very quick option.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Or you can use below script from power CLI.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="color: #222222; font-family: arial, sans-serif;"&gt;&lt;SPAN style="font-family: 'Courier New';"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;add-pssnapin&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; vmware.vimautomation.core&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;connect-viserver&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Vcenter server name -User "domain\username" -Password xxxxxxxxxxxxx&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;#param (&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;#[Parameter(Mandatory=$true)][string]$Cluster,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;#[Parameter(Mandatory=$true)][string]$CSVName&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;#)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;$cluster&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; = "cluster name"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;$csvName&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; = "c:\boot\test.csv"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;#Get cluster and all host HBA information and change format from Binary to hex&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;$list&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; = Get-cluster $cluster | Get-VMhost | Get-VMHostHBA -Type FibreChannel | Select VMHost,Device,@{N="WWN";E={"{0:X}"-f$_.PortWorldWideName}} | Sort VMhost,Device&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;#Go through each row and put : between every 2 digits&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;foreach&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;($item in $list){&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;$item.wwn = (&amp;amp;{for ($i=0;$i-lt$item.wwn.length;$i+=2)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;{&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;$item.wwn.substring($i,2)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;}})&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-join':'&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;}&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;#Output CSV to current directory.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;$list&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;| export-csv -NoTypeInformation $CSVName&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Jan 2014 10:39:50 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/How-to-find-HBA-WWN-number-on-ESX-server/m-p/162619#M1793</guid>
      <dc:creator>sureshsiwach</dc:creator>
      <dc:date>2014-01-14T10:39:50Z</dc:date>
    </item>
    <item>
      <title>Re: Restart management agents</title>
      <link>https://communities.vmware.com/t5/Virtual-Machine-Guest-OS-and-VM/Restart-management-agents/m-p/2635917#M48231</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It's worked for me..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Suresh Siwach&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Dec 2013 10:26:52 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Virtual-Machine-Guest-OS-and-VM/Restart-management-agents/m-p/2635917#M48231</guid>
      <dc:creator>sureshsiwach</dc:creator>
      <dc:date>2013-12-11T10:26:52Z</dc:date>
    </item>
  </channel>
</rss>

