<?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 vCenter Identity Source: Redundant connection to LDAPS Servers in VMware vCenter™ Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-Identity-Source-Redundant-connection-to-LDAPS-Servers/m-p/2866711#M43984</link>
    <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;I have a question about the redundant connection of an LDAP source in vCenter Server.&lt;BR /&gt;If I don't express myself well, I'll write where I am in the menu&lt;BR /&gt;VMware vCenter Server &amp;gt; Menu &amp;gt; Administration &amp;gt; Configuration &amp;gt; Identity Sources&amp;nbsp;&lt;/P&gt;&lt;P&gt;At this point I entered 2 Windows servers, LDAPs with the certificates, which also worked&amp;nbsp;for the connection.&lt;BR /&gt;&lt;BR /&gt;Now to my "problem":&amp;nbsp;&lt;BR /&gt;If the first registered LDAP server is available, everything works fine&lt;BR /&gt;If maintenance is entered on the first server, the vCenter does not fail over. No request to the second LDAPs server&lt;/P&gt;&lt;P&gt;To me it looks like there is no failover here. When the first registered server is back, you can log on again with the Windows account&lt;/P&gt;&lt;P&gt;vCenter is version 6.7 U3&lt;/P&gt;&lt;P&gt;Does anyone know this behavior? Is that so or how can I get around it so that I always have an LDAP connection?&amp;nbsp;Does anyone have a solution with F5 or something similar and is that better?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
    <pubDate>Tue, 14 Sep 2021 05:40:32 GMT</pubDate>
    <dc:creator>erki72</dc:creator>
    <dc:date>2021-09-14T05:40:32Z</dc:date>
    <item>
      <title>vCenter Identity Source: Redundant connection to LDAPS Servers</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-Identity-Source-Redundant-connection-to-LDAPS-Servers/m-p/2866711#M43984</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;I have a question about the redundant connection of an LDAP source in vCenter Server.&lt;BR /&gt;If I don't express myself well, I'll write where I am in the menu&lt;BR /&gt;VMware vCenter Server &amp;gt; Menu &amp;gt; Administration &amp;gt; Configuration &amp;gt; Identity Sources&amp;nbsp;&lt;/P&gt;&lt;P&gt;At this point I entered 2 Windows servers, LDAPs with the certificates, which also worked&amp;nbsp;for the connection.&lt;BR /&gt;&lt;BR /&gt;Now to my "problem":&amp;nbsp;&lt;BR /&gt;If the first registered LDAP server is available, everything works fine&lt;BR /&gt;If maintenance is entered on the first server, the vCenter does not fail over. No request to the second LDAPs server&lt;/P&gt;&lt;P&gt;To me it looks like there is no failover here. When the first registered server is back, you can log on again with the Windows account&lt;/P&gt;&lt;P&gt;vCenter is version 6.7 U3&lt;/P&gt;&lt;P&gt;Does anyone know this behavior? Is that so or how can I get around it so that I always have an LDAP connection?&amp;nbsp;Does anyone have a solution with F5 or something similar and is that better?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Tue, 14 Sep 2021 05:40:32 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-Identity-Source-Redundant-connection-to-LDAPS-Servers/m-p/2866711#M43984</guid>
      <dc:creator>erki72</dc:creator>
      <dc:date>2021-09-14T05:40:32Z</dc:date>
    </item>
  </channel>
</rss>

