<?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>SomeClown Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>SomeClown Tracker</description>
    <pubDate>Wed, 15 Nov 2023 11:29:33 GMT</pubDate>
    <dc:date>2023-11-15T11:29:33Z</dc:date>
    <item>
      <title>Re: Error creating VMFS Datastore on redundant FAS3240</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Error-creating-VMFS-Datastore-on-redundant-FAS3240/m-p/1266729#M108764</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;??&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Nov 2011 17:31:22 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Error-creating-VMFS-Datastore-on-redundant-FAS3240/m-p/1266729#M108764</guid>
      <dc:creator>SomeClown</dc:creator>
      <dc:date>2011-11-21T17:31:22Z</dc:date>
    </item>
    <item>
      <title>Error creating VMFS Datastore on redundant FAS3240</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Error-creating-VMFS-Datastore-on-redundant-FAS3240/m-p/1266727#M108762</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Greetings,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am trying to create a VMFS datastore of approximately 1TB in size on one controller in an active/active FAS3240 pair.&amp;nbsp; If I create the iSCSI LUN on one controller, it works fine.&amp;nbsp; On the other it does not and errors out with the error seen in the screenshot below.&amp;nbsp; The odd thing is, I have plenty of direct iSCSI connections to this other controller and everything is fine (from Windows and Linux boxes using software initiators).&amp;nbsp; I actually had this problem with two LUNs that I created today, but one of them inexplicably worked the last time I tried it.&amp;nbsp; I've checked paths, Jumbo Frames end-to-end, VIF configs, QLogic initator configs, etc. and nothing seems to make a difference.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="1866087.png"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/40498i95F28A67EC9AB948/image-size/large?v=v2&amp;amp;px=999" role="button" title="1866087.png" alt="1866087.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;VMKernel logs from the event are below:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2011-11-18T20:02:41.326Z cpu4:3273)&amp;lt;3&amp;gt;ata1.00: bad CDB len=16, scsi_op=0x9e, max=12&lt;BR /&gt;2011-11-18T20:02:41.335Z cpu2:447519)NMP: nmp_ThrottleLogForDevice:2318: Cmd 0x1a (0x41240079d7c0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.Act:NONE&lt;BR /&gt;2011-11-18T20:02:41.335Z cpu2:447519)ScsiDeviceIO: 2316: Cmd(0x41240079d7c0) 0x1a, CmdSN 0x81a74 to dev "mpx.vmhba0:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.&lt;BR /&gt;2011-11-18T20:02:41.477Z cpu1:3273)&amp;lt;3&amp;gt;ata1.00: bad CDB len=16, scsi_op=0x9e, max=12&lt;BR /&gt;2011-11-18T20:02:42.821Z cpu6:3273)&amp;lt;3&amp;gt;ata1.00: bad CDB len=16, scsi_op=0x9e, max=12&lt;BR /&gt;2011-11-18T20:02:42.824Z cpu6:3273)&amp;lt;3&amp;gt;ata1.00: bad CDB len=16, scsi_op=0x9e, max=12&lt;BR /&gt;2011-11-18T20:02:42.827Z cpu6:3273)&amp;lt;3&amp;gt;ata1.00: bad CDB len=16, scsi_op=0x9e, max=12&lt;BR /&gt;2011-11-18T20:02:42.830Z cpu6:3273)&amp;lt;3&amp;gt;ata1.00: bad CDB len=16, scsi_op=0x9e, max=12&lt;BR /&gt;2011-11-18T20:02:42.836Z cpu6:3273)FSS: 4333: No FS driver claimed device 'mpx.vmhba0:C0:T0:L0': Not supported&lt;BR /&gt;2011-11-18T20:02:42.836Z cpu6:3273)Vol3: 647: Couldn't read volume header from control: Invalid handle&lt;BR /&gt;2011-11-18T20:02:42.836Z cpu6:3273)FSS: 4333: No FS driver claimed device 'control': Not supported&lt;BR /&gt;2011-11-18T20:02:42.851Z cpu6:3273)FSS: 4333: No FS driver claimed device 'mpx.vmhba32:C0:T0:L0': Not supported&lt;BR /&gt;2011-11-18T20:02:43.557Z cpu6:3273)VC: 394: Number of PEs for volume 470ca539-5df8e7f0-d25f-0019b9eac0a7 changed from 3 to 1. A VMFS volume rescan may be needed to use this volume&lt;BR /&gt;2011-11-18T20:02:43.590Z cpu6:3273)VC: 1449: Device rescan time 1241 msec (total number of devices 49)&lt;BR /&gt;2011-11-18T20:02:43.590Z cpu6:3273)VC: 1452: Filesystem probe time 1448 msec (devices probed 41 of 49)&lt;BR /&gt;2011-11-18T20:03:02.814Z cpu4:51414)&amp;lt;6&amp;gt;qla4xxx 0000:0f:01.1: qla4xxx_mark_device_missing: ddb[65] os[1] marked MISSING&lt;BR /&gt;2011-11-18T20:03:02.814Z cpu4:51414)iscsi_linux: [vmhba3: H:7 C:0 T:1] session blocked&lt;BR /&gt;2011-11-18T20:03:02.814Z cpu1:2049)NMP: nmp_ThrottleLogForDevice:2318: Cmd 0x2a (0x412400722b40) to dev "naa.60a98000646f6452534a675651324d37" on path "vmhba3:C0:T1:L13" Failed: H:0x2 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.Act:EVAL&lt;BR /&gt;2011-11-18T20:03:02.814Z cpu1:2049)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237:NMP device "naa.60a98000646f6452534a675651324d37" state in doubt; requested fast path state update...&lt;BR /&gt;2011-11-18T20:03:02.814Z cpu1:2049)ScsiDeviceIO: 2305: Cmd(0x412400722b40) 0x2a, CmdSN 0x15d to dev "naa.60a98000646f6452534a675651324d37" failed H:0x2 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.&lt;BR /&gt;2011-11-18T20:03:13.041Z cpu5:2655)&amp;lt;6&amp;gt;qla4xxx 0000:0f:01.1: scsi7: qla4xxx_process_ddb_changed: ddb[65] os[1] marked ONLINE&lt;BR /&gt;2011-11-18T20:03:13.042Z cpu5:2655)iscsi_linux: [vmhba3: H:7 C:0 T:1] session unblocked&lt;BR /&gt;2011-11-18T20:03:13.575Z cpu7:2177)&amp;lt;6&amp;gt;qla4xxx 0000:0f:01.1: scsi7:0:1:13: ABORT ISSUED cmd=0x4124014a1800, pid=127589081, ref=1&lt;BR /&gt;2011-11-18T20:03:22.813Z cpu7:2177)&amp;lt;6&amp;gt;qla4xxx 0000:0f:01.1: scsi7:0:1:13: ABORT TASK - FAILED.&lt;BR /&gt;2011-11-18T20:03:22.813Z cpu4:2052)&amp;lt;6&amp;gt;qla4xxx 0000:0f:01.1: qla4xxx_mark_device_missing: ddb[65] os[1] marked MISSING&lt;BR /&gt;2011-11-18T20:03:22.813Z cpu4:2052)iscsi_linux: [vmhba3: H:7 C:0 T:1] session blocked&lt;BR /&gt;2011-11-18T20:03:22.813Z cpu0:2056)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237:NMP device "naa.60a98000646f6452534a675651324d37" state in doubt; requested fast path state update...&lt;BR /&gt;2011-11-18T20:03:22.924Z cpu7:2177)&amp;lt;6&amp;gt;qla4xxx 0000:0f:01.1: scsi7:0:1:13: ABORT SUCCEEDED - cmd returned back to OS.&lt;BR /&gt;2011-11-18T20:03:22.975Z cpu0:617973)ScsiPath: 3478: CmdSN 0x0 to path vmhba3:C0:T1:L13 timed out: expiry time occurs 9399ms in the past&lt;BR /&gt;2011-11-18T20:03:23.779Z cpu3:627125)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237:NMP device "naa.60a98000646f6452534a675651324d37" state in doubt; requested fast path state update...&lt;BR /&gt;2011-11-18T20:03:23.779Z cpu3:627125)ScsiDeviceIO: 2316: Cmd(0x412400722b40) 0x2a, CmdSN 0x15d to dev "naa.60a98000646f6452534a675651324d37" failed H:0x5 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.&lt;BR /&gt;2011-11-18T20:03:23.779Z cpu6:662475)BC: 1858: Failed to write (uncached) object 'naa.60a98000646f6452534a675651324d37': Timeout&lt;BR /&gt;2011-11-18T20:03:31.056Z cpu7:2655)&amp;lt;6&amp;gt;qla4xxx 0000:0f:01.1: scsi7: qla4xxx_process_ddb_changed: ddb[65] os[1] marked ONLINE&lt;BR /&gt;2011-11-18T20:03:31.056Z cpu7:2655)iscsi_linux: [vmhba3: H:7 C:0 T:1] session unblocked&lt;BR /&gt;2011-11-18T20:03:31.436Z cpu1:257738)ScsiCore: 1455: Power-on Reset occurred on vmhba3:C0:T1:L13&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 Nov 2011 21:13:55 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Error-creating-VMFS-Datastore-on-redundant-FAS3240/m-p/1266727#M108762</guid>
      <dc:creator>SomeClown</dc:creator>
      <dc:date>2011-11-18T21:13:55Z</dc:date>
    </item>
    <item>
      <title>Trying to upgrade to newest vCenter Server...</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Trying-to-upgrade-to-newest-vCenter-Server/m-p/840488#M25616</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Greetings,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've used the data migration tool to backup my vcenter server, and am trying to now restore onto a new server in order to facilitate the conversion from 32-bit to 64-bit, go to ESXi on VSphere 5, etc.&amp;nbsp; Current database is sitting on a SQL 2008 Enterprise server and works great.&amp;nbsp; I backed it up too.&amp;nbsp; &lt;img id="smileyhappy" class="emoticon emoticon-smileyhappy" src="https://communities.vmware.com/i/smilies/16x16_smiley-happy.png" alt="Smiley Happy" title="Smiley Happy" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I go through the process of running the restore on the new server, and get to the part where it tries to connect to the database whereby I get the ever-popular error:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="1841889.png"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/40440i6045C3E7064CA718/image-size/large?v=v2&amp;amp;px=999" role="button" title="1841889.png" alt="1841889.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The problem is, I've tried with 3 different usernames, including a new one just to make certain I haven't missed anything.&amp;nbsp; In all cases, the users are domain users and in the database have DBO, sysadmin, etc. to both the Virtual Center database and the MSDB database.&amp;nbsp; In fact, one user has wide-open permissions to every damned database (this is a named instance server with a lot of databases, so he was just a test).&amp;nbsp; I still get this error.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DSN is 64-bit, using the SQL native drivers and tests just fine.&amp;nbsp; Every other database from BES to SharePoint is working great, and even our DBA can't find any problems.&amp;nbsp; I'm completely stuck here and am looking for options. If need be, I'll even create a new database and migrate this one over if that's easy enough... I just want to get through this @#$@! so I can move on with my life.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Considering the lack of errors on the SQL side, we're wondering if there might be some sort of problem with named instances on the new vcenter?&amp;nbsp; Or a bug?&amp;nbsp; We've been running the same configuration for years now and have upgraded with no problems in each case.&amp;nbsp; This is the first time we're seeing this error and are more than a little bewildered.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Oct 2011 23:19:29 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Trying-to-upgrade-to-newest-vCenter-Server/m-p/840488#M25616</guid>
      <dc:creator>SomeClown</dc:creator>
      <dc:date>2011-10-06T23:19:29Z</dc:date>
    </item>
    <item>
      <title>Re: cannot upgrade ESX4 to ESX 4 Update1</title>
      <link>https://communities.vmware.com/t5/Update-Manager-Discussions/cannot-upgrade-ESX4-to-ESX-4-Update1/m-p/2551470#M4858</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yup... same behaviour on all hosts.  I'm wondering if it has something to do with the VEM patch level, though that's all been remediated by VUM with everything else (a process which has worked amazingly well up until Update 1.)  I'll probably file a ticket with support as soon as it bothers me enough...  &lt;img id="smileyhappy" class="emoticon emoticon-smileyhappy" src="https://communities.vmware.com/i/smilies/16x16_smiley-happy.png" alt="Smiley Happy" title="Smiley Happy" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Dec 2009 22:42:39 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Update-Manager-Discussions/cannot-upgrade-ESX4-to-ESX-4-Update1/m-p/2551470#M4858</guid>
      <dc:creator>SomeClown</dc:creator>
      <dc:date>2009-12-08T22:42:39Z</dc:date>
    </item>
    <item>
      <title>Re: cannot upgrade ESX4 to ESX 4 Update1</title>
      <link>https://communities.vmware.com/t5/Update-Manager-Discussions/cannot-upgrade-ESX4-to-ESX-4-Update1/m-p/2551468#M4856</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yeah, I've gone around and around with this.  We updated our VUM, Client, and VC to U1 (though the VC upgrade was a bit dodgy and we had to MacGyver our way through that... upgrade script didn't like our service user running as sysadmin in SQL, but wouldn't let us pass when we took it off, so we flipped the permissions half-way through the script and that did the trick.)  As for ESX, however, the ESX update 1 reports as incompatible in VUM, and when we try to do the manual process we get: "Requested VIB rpm_vmware-esx-vmkernel64_4.0.0-1.9.208167@i386 conflicts with the host."  Bottom line at this point is that we have all ESX servers sitting at 175625 with no apparent way forward to U1.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Dec 2009 22:10:01 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Update-Manager-Discussions/cannot-upgrade-ESX4-to-ESX-4-Update1/m-p/2551468#M4856</guid>
      <dc:creator>SomeClown</dc:creator>
      <dc:date>2009-12-08T22:10:01Z</dc:date>
    </item>
    <item>
      <title>Update 1 pulled from patch repository?</title>
      <link>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Update-1-pulled-from-patch-repository/m-p/2073115#M22628</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Greetings--My systems are all compliant and patched to version 4.0.0, 175625 and I have no more patches available.  I have pulled both the ISO and the .ZIP locally, just in case I want to manually update, but shouldn't the Update 1 be available and listed in my Update Manager view?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Dec 2009 22:38:05 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Update-1-pulled-from-patch-repository/m-p/2073115#M22628</guid>
      <dc:creator>SomeClown</dc:creator>
      <dc:date>2009-12-02T22:38:05Z</dc:date>
    </item>
    <item>
      <title>Re: vlans with one network card</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/vlans-with-one-network-card/m-p/2563642#M237959</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I don't know how only one NIC will play in the grand scheme of things, but yes, we use VLANs all of the time here.  In fact, all of our ESX hosts have a minimum of 10 dedicated NICs split into two switches, and all of those links are 802.1q trunks.  Then we assign port-groups to the 10 pNICs, and assign VLANs there.  That all said, we're a Cisco shop here and I'm not intimately familiar with how you would need to set up the Procurves.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Dec 2009 22:29:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/vlans-with-one-network-card/m-p/2563642#M237959</guid>
      <dc:creator>SomeClown</dc:creator>
      <dc:date>2009-12-02T22:29:26Z</dc:date>
    </item>
    <item>
      <title>Re: Update Manager - Error connecting to VMware vCenter Update Manager - Database temporarily unavailable or has network problems.</title>
      <link>https://communities.vmware.com/t5/Update-Manager-Discussions/Update-Manager-Error-connecting-to-VMware-vCenter-Update-Manager/m-p/2497995#M4481</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Wow... that was the fix for me too!  Thanks!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Still not sure why I can't use the same user to run the Update Manager as I do to run the main database, but at this point I'm not complaining.  Incidentally, this is against a SQL 2008 Enterprise server, running on Server 2008 Enterprise 64-bit.  Virtual Center is on a dedicated hardware box, SQL is its own set of boxes, ESX servers are their own set of boxes.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Dec 2009 17:04:47 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Update-Manager-Discussions/Update-Manager-Error-connecting-to-VMware-vCenter-Update-Manager/m-p/2497995#M4481</guid>
      <dc:creator>SomeClown</dc:creator>
      <dc:date>2009-12-02T17:04:47Z</dc:date>
    </item>
    <item>
      <title>Re: ESX 3.5 VC 2.5 Host Disconnected (happens repeatedly)</title>
      <link>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/ESX-3-5-VC-2-5-Host-Disconnected-happens-repeatedly/m-p/687218#M8971</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hmmm...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any word on what to do if you have already done the upgrade?  Or a timeframe for a fix?  Or can you point me to where you found that documented somewhere?  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Jan 2008 21:55:07 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/ESX-3-5-VC-2-5-Host-Disconnected-happens-repeatedly/m-p/687218#M8971</guid>
      <dc:creator>SomeClown</dc:creator>
      <dc:date>2008-01-22T21:55:07Z</dc:date>
    </item>
    <item>
      <title>Re: ESX 3.5 VC 2.5 Host Disconnected (happens repeatedly)</title>
      <link>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/ESX-3-5-VC-2-5-Host-Disconnected-happens-repeatedly/m-p/687216#M8969</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Correct--this is only on hosts upgraded to 3.5 from 3.02 (or whatever the last version was... don't have it in front of me this second.)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Jan 2008 16:12:39 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/ESX-3-5-VC-2-5-Host-Disconnected-happens-repeatedly/m-p/687216#M8969</guid>
      <dc:creator>SomeClown</dc:creator>
      <dc:date>2008-01-22T16:12:39Z</dc:date>
    </item>
    <item>
      <title>Re: ESX 3.5 VC 2.5 Host Disconnected (happens repeatedly)</title>
      <link>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/ESX-3-5-VC-2-5-Host-Disconnected-happens-repeatedly/m-p/687214#M8967</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is the third high-profile crash of this server array since we upgraded.  I've already had to completely reinstall one host to fix the first crash, move filestores from one SAN to another to fix a communications lockup on our QLogic HBAs (again, VMware issue), and now we're back to issue number 1 where I either reboot and maybe it works for a couple of days, follow the procedure outlined above, or reinstall (again).  I'm really beginning to wonder if VMware actually tests anything they release or if they follow the Microsoft beta-test cycle.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Jan 2008 00:21:37 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/ESX-3-5-VC-2-5-Host-Disconnected-happens-repeatedly/m-p/687214#M8967</guid>
      <dc:creator>SomeClown</dc:creator>
      <dc:date>2008-01-22T00:21:37Z</dc:date>
    </item>
    <item>
      <title>Re: ESX 3.5 VC 2.5 Host Disconnected (happens repeatedly)</title>
      <link>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/ESX-3-5-VC-2-5-Host-Disconnected-happens-repeatedly/m-p/687212#M8965</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As a follow-up... I do notice that when I run the "service mgmt-vmware restart" command I get the following error message:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"touch: creating '/var/lock/subsys/mgmt-vmare': Read-only file system"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Jan 2008 18:26:17 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/ESX-3-5-VC-2-5-Host-Disconnected-happens-repeatedly/m-p/687212#M8965</guid>
      <dc:creator>SomeClown</dc:creator>
      <dc:date>2008-01-21T18:26:17Z</dc:date>
    </item>
    <item>
      <title>ESX 3.5 VC 2.5 Host Disconnected (happens repeatedly)</title>
      <link>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/ESX-3-5-VC-2-5-Host-Disconnected-happens-repeatedly/m-p/687211#M8964</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Greetings,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; After upgrading to the aforementioned versions (newest of each) I am having an issue where each host in the farm seems to randomly lose connection to the VirtualCenter.  This impacts all manageability of virtual machines, since they show as disconnected and can't be migrated or touched, but they're still up and running just fine.  If I ssh into the affected box and do a mgmt-vmware restart (or stop and start) everything comes back up except for "VMware ESX Server Host Agent Watchdog" which shows "FAILED."  On a status query I see that hostd is not running.  Nothing I do seems to get anything back up again.  The last time this happened I rebooted the server and everything came back up, but that's getting a little old.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thoughts?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Jan 2008 18:02:02 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/ESX-3-5-VC-2-5-Host-Disconnected-happens-repeatedly/m-p/687211#M8964</guid>
      <dc:creator>SomeClown</dc:creator>
      <dc:date>2008-01-21T18:02:02Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot access image after upgrading VC</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-access-image-after-upgrading-VC/m-p/667319#M16806</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, yes I know... as evidenced by my comments to that effect earlier in the thread.  My irritation at this point is with the lack of documentation on the change, and with the fact that I have to do the renaming in the first place because of some (apparently) arbitrarily imposed file-name-size limit in the new version of VirtualCenter.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Jan 2008 22:42:44 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-access-image-after-upgrading-VC/m-p/667319#M16806</guid>
      <dc:creator>SomeClown</dc:creator>
      <dc:date>2008-01-08T22:42:44Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot access image after upgrading VC</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-access-image-after-upgrading-VC/m-p/667317#M16804</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just the standard Microsoft .iso names that you get when you download licensed software from their licensing portal... something like so:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SW_DVD5_Office_SharePoint_Server_2007_W32_English_-2_1_PA_BP_ISO_Onl_X13-38800.ISO&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It's not even so much that their may now be a limitation, it's just that I didn't find anything in the documentation referring to this, and since all of the Microsoft .iso files come down this way, now I have to come up with my own renaming scheme... just another bit of work I have to do to make VirtualCenter happy all of a sudden.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Jan 2008 22:33:42 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-access-image-after-upgrading-VC/m-p/667317#M16804</guid>
      <dc:creator>SomeClown</dc:creator>
      <dc:date>2008-01-08T22:33:42Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot access image after upgrading VC</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-access-image-after-upgrading-VC/m-p/667315#M16802</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Nevermind... figured it out.  For some reason the new version of VirtualCenter doesn't like long .iso names (like the ones Microsoft uses if you have an EA or Technet account).  I just renamed my .iso images to shorter names and everything is great.  Though I still think this is a @#$@# thing to just "toss in" on an upgrade like this... especially since I now won't know what I've downloaded as matched against the official .iso names from Microsoft.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Jan 2008 22:07:57 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-access-image-after-upgrading-VC/m-p/667315#M16802</guid>
      <dc:creator>SomeClown</dc:creator>
      <dc:date>2008-01-08T22:07:57Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot access image after upgrading VC</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-access-image-after-upgrading-VC/m-p/667314#M16801</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Bump&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Same thing is happening to me.  I keep my .ISO install images out on a network share, and while I can still see them, I get this error any time I try to connect the CD/DVD device.  Worked repeatedly and often in 2.0.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Jan 2008 21:57:52 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-access-image-after-upgrading-VC/m-p/667314#M16801</guid>
      <dc:creator>SomeClown</dc:creator>
      <dc:date>2008-01-08T21:57:52Z</dc:date>
    </item>
    <item>
      <title>Re: Host xxx currently has no management network redundancy</title>
      <link>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/Host-xxx-currently-has-no-management-network-redundancy/m-p/1552420#M21722</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dunno... worked before the VC upgrade to 2.5.  Works now after the 3.02 upgrade of all hosts to 3.5.  Basically upgraded the ESX Hosts, then unconfigured and reconfigured HA/DRS and now life is good again.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Jan 2008 21:33:06 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/Host-xxx-currently-has-no-management-network-redundancy/m-p/1552420#M21722</guid>
      <dc:creator>SomeClown</dc:creator>
      <dc:date>2008-01-04T21:33:06Z</dc:date>
    </item>
    <item>
      <title>Re: Host xxx currently has no management network redundancy</title>
      <link>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/Host-xxx-currently-has-no-management-network-redundancy/m-p/1552418#M21720</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I should clarify--I can migrate hosts if I &lt;EM&gt;unconfigure&lt;/EM&gt; HA.  Once I reconfigure HA, I have the network redundancy error and no ability to even manually migrate.  So, for this second I'm running with no HA and we'll see what happens after I get the hosts upgraded to 3.5 (I'm on 3.02) later today.  If I still have the problem after looking through the logs I'll open a case.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Jan 2008 15:53:22 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/Host-xxx-currently-has-no-management-network-redundancy/m-p/1552418#M21720</guid>
      <dc:creator>SomeClown</dc:creator>
      <dc:date>2008-01-04T15:53:22Z</dc:date>
    </item>
    <item>
      <title>Re: host esx01.domain.com currently has no management network redundancy</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/host-esx01-domain-com-currently-has-no-management-network/m-p/1536476#M48180</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I did reconfigure HA and it got rid of one set of errors (relating to HA not being configured on one host) but left the network redundancy alert in place.  I actually got some answers in a different thread (&lt;A href="https://communities.vmware.com/m-832170"&gt;http://communities.vmware.com/message/832170&lt;/A&gt;) that seemed to point to having to have a redundant physical NIC for management.  Interesting thing, however, and you can see it in that thread, is that when I &lt;EM&gt;unconfigure&lt;/EM&gt; HA the alert goes away and I get back my ability to manually migrate my vms from host to host.  Once I reconfigure HA again, back to the same problem--alert and no ability to migrate any VMs.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Jan 2008 15:26:07 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/host-esx01-domain-com-currently-has-no-management-network/m-p/1536476#M48180</guid>
      <dc:creator>SomeClown</dc:creator>
      <dc:date>2008-01-04T15:26:07Z</dc:date>
    </item>
  </channel>
</rss>

