<?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 Can't Access Switches With Loss To LDAP via NAC in ExtremeSwitching (Other)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-other/can-t-access-switches-with-loss-to-ldap-via-nac/m-p/9107#M135</link>
    <description>Hi,&lt;BR /&gt;
&lt;BR /&gt;
Currently have all switches in the network doing management login via Radius Via NAC and then onto LDAP to AD.&lt;BR /&gt;
&lt;BR /&gt;
The problem has arisen, although two AD (LDAP Connections) have been configured, where Full loss to both the LDAP services has occurred. (appreciate that the resiliency here is broken, but...)&lt;BR /&gt;
&lt;BR /&gt;
The issue is (I believe) that because Radius is still working between the switch and NAC that the switches still think all is good and doesn't default to use a local account.&lt;BR /&gt;
&lt;BR /&gt;
Do you know if there is anyway to correct that?&lt;BR /&gt;
&lt;BR /&gt;
Was wondering if there is a Rule or an AAA configuration that could take precedence in that situation to use local authentication - have played but not got anything to work with that line of thought.&lt;BR /&gt;
&lt;BR /&gt;
Perhaps there is an EXOS configuration that can for example, test the LDAP servers before doing Radius Management Authentication, or equally something NAC could do similiar?&lt;BR /&gt;
&lt;BR /&gt;
Anyone had the same problem and found a solution?&lt;BR /&gt;
&lt;BR /&gt;
Many thanks.&lt;BR /&gt;
&lt;BR /&gt;</description>
    <pubDate>Fri, 22 Sep 2017 14:25:00 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2017-09-22T14:25:00Z</dc:date>
    <item>
      <title>Can't Access Switches With Loss To LDAP via NAC</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-other/can-t-access-switches-with-loss-to-ldap-via-nac/m-p/9107#M135</link>
      <description>Hi,&lt;BR /&gt;
&lt;BR /&gt;
Currently have all switches in the network doing management login via Radius Via NAC and then onto LDAP to AD.&lt;BR /&gt;
&lt;BR /&gt;
The problem has arisen, although two AD (LDAP Connections) have been configured, where Full loss to both the LDAP services has occurred. (appreciate that the resiliency here is broken, but...)&lt;BR /&gt;
&lt;BR /&gt;
The issue is (I believe) that because Radius is still working between the switch and NAC that the switches still think all is good and doesn't default to use a local account.&lt;BR /&gt;
&lt;BR /&gt;
Do you know if there is anyway to correct that?&lt;BR /&gt;
&lt;BR /&gt;
Was wondering if there is a Rule or an AAA configuration that could take precedence in that situation to use local authentication - have played but not got anything to work with that line of thought.&lt;BR /&gt;
&lt;BR /&gt;
Perhaps there is an EXOS configuration that can for example, test the LDAP servers before doing Radius Management Authentication, or equally something NAC could do similiar?&lt;BR /&gt;
&lt;BR /&gt;
Anyone had the same problem and found a solution?&lt;BR /&gt;
&lt;BR /&gt;
Many thanks.&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Fri, 22 Sep 2017 14:25:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-other/can-t-access-switches-with-loss-to-ldap-via-nac/m-p/9107#M135</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2017-09-22T14:25:00Z</dc:date>
    </item>
    <item>
      <title>RE: Can't Access Switches With Loss To LDAP via NAC</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-other/can-t-access-switches-with-loss-to-ldap-via-nac/m-p/9108#M136</link>
      <description>Martin, If the failsafe account is configured, that is an option to access the switches.&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Fri, 22 Sep 2017 17:16:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-other/can-t-access-switches-with-loss-to-ldap-via-nac/m-p/9108#M136</guid>
      <dc:creator>Schmotter__Ryan</dc:creator>
      <dc:date>2017-09-22T17:16:00Z</dc:date>
    </item>
    <item>
      <title>RE: Can't Access Switches With Loss To LDAP via NAC</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-other/can-t-access-switches-with-loss-to-ldap-via-nac/m-p/9109#M137</link>
      <description>Oh right!&lt;BR /&gt;
&lt;BR /&gt;
The LDAP servers are backup now, but do you know if that would work via SSH and/or when locally connected?&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Fri, 22 Sep 2017 17:16:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-other/can-t-access-switches-with-loss-to-ldap-via-nac/m-p/9109#M137</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2017-09-22T17:16:00Z</dc:date>
    </item>
    <item>
      <title>RE: Can't Access Switches With Loss To LDAP via NAC</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-other/can-t-access-switches-with-loss-to-ldap-via-nac/m-p/9110#M138</link>
      <description>The Failsafe account needs to be configured, it is not on by default and does not show up in the config. It is meant to be a last-resort account. You can use it in the console and SSH. Check out page 31 of the 21.1 EXOS user guide.&lt;BR /&gt;</description>
      <pubDate>Fri, 22 Sep 2017 17:16:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-other/can-t-access-switches-with-loss-to-ldap-via-nac/m-p/9110#M138</guid>
      <dc:creator>Schmotter__Ryan</dc:creator>
      <dc:date>2017-09-22T17:16:00Z</dc:date>
    </item>
    <item>
      <title>RE: Can't Access Switches With Loss To LDAP via NAC</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-other/can-t-access-switches-with-loss-to-ldap-via-nac/m-p/9111#M139</link>
      <description>Thanks Ryan.&lt;BR /&gt;
&lt;BR /&gt;
Fortunately I always configure one by default, but there was just one step I missed out when I tested this:&lt;BR /&gt;
&lt;BR /&gt;
&lt;A href="https://gtacknowledge.extremenetworks.com/articles/How_To/How-To-Create-a-Failsafe-Account" target="_blank" rel="nofollow noreferrer noopener"&gt;https://gtacknowledge.extremenetworks.com/articles/How_To/How-To-Create-a-Failsafe-Account&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;
I had not permitted access to the failsafe account via SSH!&lt;BR /&gt;
&lt;BR /&gt;
Cheers for your help&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Fri, 22 Sep 2017 17:16:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-other/can-t-access-switches-with-loss-to-ldap-via-nac/m-p/9111#M139</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2017-09-22T17:16:00Z</dc:date>
    </item>
  </channel>
</rss>

