AudioCodes Mediant 4000 SBC, Руководство пользователя

Страница: 261 / 1037

CHAPTER 16 Services
Mediant 4000 SBC | User's Manual
Parameter Description
level
[MgmntLDAPGroups_
Level]
■ [0] Monitor (Default)
■ [1] Admin
■ [2] Security Admin
'Groups'
groups
[MgmntLDAPGroups_
Group]
Defines the attribute names of the groups in the LDAP server.
The valid value is a string of up to 256 characters. To define multiple
groups, separate each group name with a semicolon (;).
Configuring the Device's LDAP Cache
The device can optionally store LDAP queries of LDAP Attributes for a searched key with an LDAP
server and the responses (results) in its local cache. The cache is used for subsequent queries
and/or in case of LDAP server failure. The benefits of this feature include the following:
■ Improves routing decision performance by using local cache for subsequent LDAP queries
■ Reduces number of queries performed on an LDAP server and corresponding bandwidth
consumption
■ Provides partial survivability in case of intermittent LDAP server failure (or network isolation)
The handling of LDAP queries using the device's LDAP cache is shown in the flowchart below:
If an LDAP query is required for an Attribute of a key that is already cached with that same
Attribute, instead of sending a query to the LDAP server, the device uses the cache. However, if an
LDAP query is required for an Attribute that does not appear for the cached key, the device queries
the LDAP server, and then saves the new Attribute (and response) in the cache for that key.
If the device queries the LDAP server for different Attributes for a cached key, the device also
includes already cached Attributes of the key, while adhering to the maximum number of allowed
saved Attributes (see note below), with preference to the different Attributes. In other words, if the
cached key already contains the maximum Attributes and an LDAP query is required for a different
Attribute, the device sends an LDAP query to the server for the different Attribute and for the five
most recent Attributes already cached with the key. Upon the LDAP response, the new Attribute
replaces the oldest cached Attribute while the values of the other Attributes are refreshed with the
new response.
- 228 -