<?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>topic Unable to pair VR after upgrade from 6.5 to 8.2 in vSphere Replication Discussions</title>
    <link>https://communities.vmware.com/t5/vSphere-Replication-Discussions/Unable-to-pair-VR-after-upgrade-from-6-5-to-8-2/m-p/2882529#M3520</link>
    <description>&lt;P&gt;Good evening,&lt;/P&gt;&lt;P&gt;We've just updated our VR from 6.5 to 8.2 (on the road to fully upgrade the environment to 7) and we faced an issue.&lt;/P&gt;&lt;P&gt;After the upgrade, the First Site VR appliance notified us that "Sites would need to be re-paired manually" (that message did not appear when upgrading the Second Site VR).&lt;/P&gt;&lt;P&gt;When we logged into the Site Recovery screen first time after the upgrade we received a "failed to connect to hbr management server" header message.&lt;/P&gt;&lt;P&gt;Next, when trying to redo the pair we received issue below (SSL handshake failed).&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot from 2021-12-10 00-10-51.png" style="width: 400px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/92511iA2ED97A838158EB0/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="Screenshot from 2021-12-10 00-10-51.png" alt="Screenshot from 2021-12-10 00-10-51.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;We've already rebooted everything, re-created the VR certificates (self-signed) for the First Site appliance, checked connectivity and both vCenter host name resolution.&lt;/P&gt;&lt;P&gt;vCenter is running version 6.5.&lt;/P&gt;&lt;P&gt;Any one with any ideas on why this could be happening.&lt;/P&gt;</description>
    <pubDate>Fri, 10 Dec 2021 03:27:08 GMT</pubDate>
    <dc:creator>Henrique_Cicuto</dc:creator>
    <dc:date>2021-12-10T03:27:08Z</dc:date>
    <item>
      <title>Unable to pair VR after upgrade from 6.5 to 8.2</title>
      <link>https://communities.vmware.com/t5/vSphere-Replication-Discussions/Unable-to-pair-VR-after-upgrade-from-6-5-to-8-2/m-p/2882529#M3520</link>
      <description>&lt;P&gt;Good evening,&lt;/P&gt;&lt;P&gt;We've just updated our VR from 6.5 to 8.2 (on the road to fully upgrade the environment to 7) and we faced an issue.&lt;/P&gt;&lt;P&gt;After the upgrade, the First Site VR appliance notified us that "Sites would need to be re-paired manually" (that message did not appear when upgrading the Second Site VR).&lt;/P&gt;&lt;P&gt;When we logged into the Site Recovery screen first time after the upgrade we received a "failed to connect to hbr management server" header message.&lt;/P&gt;&lt;P&gt;Next, when trying to redo the pair we received issue below (SSL handshake failed).&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot from 2021-12-10 00-10-51.png" style="width: 400px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/92511iA2ED97A838158EB0/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="Screenshot from 2021-12-10 00-10-51.png" alt="Screenshot from 2021-12-10 00-10-51.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;We've already rebooted everything, re-created the VR certificates (self-signed) for the First Site appliance, checked connectivity and both vCenter host name resolution.&lt;/P&gt;&lt;P&gt;vCenter is running version 6.5.&lt;/P&gt;&lt;P&gt;Any one with any ideas on why this could be happening.&lt;/P&gt;</description>
      <pubDate>Fri, 10 Dec 2021 03:27:08 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Replication-Discussions/Unable-to-pair-VR-after-upgrade-from-6-5-to-8-2/m-p/2882529#M3520</guid>
      <dc:creator>Henrique_Cicuto</dc:creator>
      <dc:date>2021-12-10T03:27:08Z</dc:date>
    </item>
  </channel>
</rss>

