<?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>jravnsbaek Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>jravnsbaek Tracker</description>
    <pubDate>Wed, 15 Nov 2023 10:01:54 GMT</pubDate>
    <dc:date>2023-11-15T10:01:54Z</dc:date>
    <item>
      <title>copy files from one esxi to another</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/copy-files-from-one-esxi-to-another/m-p/2948145#M285926</link>
      <description>&lt;P&gt;When I try to copy files from one esxi host to another it gives error:&lt;/P&gt;&lt;P&gt;[root@esxi01:~]scp /var/log/init.log root@esxi02.mydomain.com:/tmp&lt;/P&gt;&lt;P&gt;hostfile_replace_entries: link /.ssh/known_hosts to /.ssh/known_hosts.old: Function not implemented&lt;BR /&gt;update_known_hosts: hostfile_replace_entries failed for /.ssh/known_hosts: Function not implemented&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Even when I ssh from esxi01 to esxi02 I get the same error but the ssh connection is successfull:&lt;/P&gt;&lt;P&gt;[root@esxi01:/tmp] ssh root@esxi02.mydomain.com&lt;/P&gt;&lt;P&gt;(root@esxi02.mydomain.com) Password:&lt;BR /&gt;hostfile_replace_entries: link /.ssh/known_hosts to /.ssh/known_hosts.old: Function not implemented&lt;BR /&gt;update_known_hosts: hostfile_replace_entries failed for /.ssh/known_hosts: Function not implemented&lt;/P&gt;&lt;P&gt;[root@esxi02:~]&lt;/P&gt;&lt;P&gt;I have disabled the firewall on the hosts while testing, but are still unable to scp between the hosts.&lt;/P&gt;</description>
      <pubDate>Wed, 11 Jan 2023 17:11:00 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/copy-files-from-one-esxi-to-another/m-p/2948145#M285926</guid>
      <dc:creator>jravnsbaek</dc:creator>
      <dc:date>2023-01-11T17:11:00Z</dc:date>
    </item>
    <item>
      <title>Re: vCenter startup without network connection to verify restored vCenter is working</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-startup-without-network-connection-to-verify-restored/m-p/2931333#M46430</link>
      <description>&lt;P&gt;We were unable to to get vCenter up without network connected, so we created fenced network with vcenter and an very limitied DNS server with only the record for vCenter.&lt;/P&gt;&lt;P&gt;Then we were able to startup vCenter with all services.&lt;/P&gt;&lt;P&gt;In version 7.0.2 we were able to startup vCenter without network connected and all services started and this has changed in 7.0.3.&lt;/P&gt;&lt;P&gt;Problem fixed by a workaround &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@DCF4E2F7991292CEECF250394DB2C2BC/emoticons/1f642.png" alt=":slightly_smiling_face:" title=":slightly_smiling_face:" /&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 30 Sep 2022 08:09:59 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-startup-without-network-connection-to-verify-restored/m-p/2931333#M46430</guid>
      <dc:creator>jravnsbaek</dc:creator>
      <dc:date>2022-09-30T08:09:59Z</dc:date>
    </item>
    <item>
      <title>vCenter startup without network connection to verify restored vCenter is working</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-startup-without-network-connection-to-verify-restored/m-p/2930919#M46418</link>
      <description>&lt;P&gt;I was recover vCenter from backup without shutting down the production vCenter (with the same name), to test backup in a DR scenario.&lt;/P&gt;&lt;P&gt;It was restored with a suffix -testbackup and with network disconnected.&lt;/P&gt;&lt;P&gt;This was working in 7.0.2 but in version 7.0.3G it is unable to start all services.&lt;/P&gt;&lt;P&gt;Especially the lookupsvc in not starting and very long time in start pending.&lt;/P&gt;&lt;P&gt;Isn't is possible to startup a restored vCenter without network ?&lt;/P&gt;&lt;P&gt;If started up in a fenced network it wouldn't have access to NTP,DNS,AD etc.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 28 Sep 2022 12:07:41 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-startup-without-network-connection-to-verify-restored/m-p/2930919#M46418</guid>
      <dc:creator>jravnsbaek</dc:creator>
      <dc:date>2022-09-28T12:07:41Z</dc:date>
    </item>
    <item>
      <title>Does Lifecycle Manager currently not support upgrading vRealize Operations 8.6.4, only a new install</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Suite-Lifecycle/Does-Lifecycle-Manager-currently-not-support-upgrading-vRealize/m-p/2924132#M250</link>
      <description>&lt;P&gt;I was about to upgrade&amp;nbsp;vRealize Operations to version 8.6.4 and was planning to use vLCM for this, but I wasn't able to find any update to 8.6.4 only a new install.&lt;/P&gt;&lt;P&gt;There was upgrade available for earlier versions of vRealize Operations.&lt;/P&gt;&lt;P&gt;Haven't VMware created an 8.6.4 update available for vLCM ?&lt;/P&gt;</description>
      <pubDate>Tue, 16 Aug 2022 14:29:39 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Suite-Lifecycle/Does-Lifecycle-Manager-currently-not-support-upgrading-vRealize/m-p/2924132#M250</guid>
      <dc:creator>jravnsbaek</dc:creator>
      <dc:date>2022-08-16T14:29:39Z</dc:date>
    </item>
    <item>
      <title>When upgrading Lifecycle Manager from 8.6.2 to 8.6.4 the IP was reconfigured</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Suite-Lifecycle/When-upgrading-Lifecycle-Manager-from-8-6-2-to-8-6-4-the-IP-was/m-p/2923904#M249</link>
      <description>&lt;P&gt;When upgrading vLCM the IP was reconfigured and the web wasn't available.&lt;BR /&gt;The console was displaying the new IP which in fact was a duplicate of another running Windows Server - hmmm.&lt;BR /&gt;The upgrade was successfull due to the upgradeprogress and upgradestatus&lt;BR /&gt;tail -f /etc/upgradeprogress - SUCCESS&lt;BR /&gt;tail -f /etc/upgradestatus - Upgrade Completed Successfully from 8.6.2.0 to 8.8.2.3&lt;BR /&gt;Logging on the console and changing the IP back to origin using the command "opt/vmware/share/vami/vami_set_network eth0 STATICV4 192.168.1.150 255.255.255.0 192.168.1.1" made the vLCM available again.&amp;nbsp;&lt;BR /&gt;This was from the VMware doc: "Wrong IP Details During vRealize Suite Lifecycle Manager Deployment"&lt;/P&gt;&lt;P&gt;Not sure why the upgrade made the IP change.&lt;/P&gt;&lt;P&gt;Anyone tried the same issue ?&lt;/P&gt;</description>
      <pubDate>Mon, 15 Aug 2022 12:42:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Suite-Lifecycle/When-upgrading-Lifecycle-Manager-from-8-6-2-to-8-6-4-the-IP-was/m-p/2923904#M249</guid>
      <dc:creator>jravnsbaek</dc:creator>
      <dc:date>2022-08-15T12:42:26Z</dc:date>
    </item>
  </channel>
</rss>

