LDAP timeout errors since upgrade to 9.13.1
Randy Rue <[email protected]> Mon, 17 Jul 2023 13:55:29 -0700
| Newsgroups | gmane.comp.hardware.netapp |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
--===============7721225726692692142==
Content-Type: multipart/alternative;
boundary="------------PzVy8LgANx30QqrgPKKvahzk"
Content-Language: en-US
This is a multi-part message in MIME format.
--------------PzVy8LgANx30QqrgPKKvahzk
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Hi All,
Since upgrading to 9.13.1 our AFF/FAS on-premise cluster has an alert in
the System Manager dashboard and shows us receiving these errors every
hour or two:
secd.ldap.noServers: None of the LDAP servers configured for Vserver
(vfiler_name) are currently accessible via the network for LDAP service
type (Service: LDAP (Active Directory), Operation: SiteDiscovery).
We run a redundant pair of slapd LDAP servers presented via an F5 BigIP
at a single IP. The SVMs LDAP settings include of a list of the F5's
highly available IP and then the two back end servers.
Nothing has changed with our LDAP service. The LDAP servers don't seem
to be distressed and no other systems/services that touch our LDAP are
complaining. Our NetApp SVMs don't seem to be dropping or bouncing any
filer traffic.
Has anything changed from 9.9 to 9.13 in the way ONTAP talks to LDAP? Is
it chattier? More sensitive to lags?
Randy
--------------PzVy8LgANx30QqrgPKKvahzk
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi All,</p>
<p>Since upgrading to 9.13.1 our AFF/FAS on-premise cluster has an
alert in the System Manager dashboard and shows us receiving these
errors every hour or two:</p>
<p>
<span style="color: rgb(69, 69, 69); font-family: "Source
Sans Pro", Arial, "Helvetica Neue", Helvetica,
sans-serif; font-size: 18px; font-style: normal;
font-variant-ligatures: normal; font-variant-caps: normal;
font-weight: 400; letter-spacing: normal; orphans: 2;
text-align: left; text-indent: 0px; text-transform: none;
widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px;
white-space: normal; background-color: rgb(255, 255, 255);
text-decoration-thickness: initial; text-decoration-style:
initial; text-decoration-color: initial; display: inline
!important; float: none;">secd.ldap.noServers: None of the LDAP
servers configured for Vserver (vfiler_name) are currently
accessible via the network for LDAP service type (Service: LDAP
(Active Directory), Operation: SiteDiscovery).</span> <br>
</p>
<p>We run a redundant pair of slapd LDAP servers presented via an F5
BigIP at a single IP. The SVMs LDAP settings include of a list of
the F5's highly available IP and then the two back end servers.</p>
<p>Nothing has changed with our LDAP service. The LDAP servers don't
seem to be distressed and no other systems/services that touch our
LDAP are complaining. Our NetApp SVMs don't seem to be dropping or
bouncing any filer traffic.</p>
<p>Has anything changed from 9.9 to 9.13 in the way ONTAP talks to
LDAP? Is it chattier? More sensitive to lags?</p>
<p><br>
</p>
<p>Randy<br>
</p>
</body>
</html>
--------------PzVy8LgANx30QqrgPKKvahzk--
--===============7721225726692692142==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Toasters mailing list
[email protected]
https://www.teaparty.net/mailman/listinfo/toasters
--===============7721225726692692142==--