Operation - 3Com corebuilder 3500 Implementation Manual

LDAP 515
When an LDAP client connects to the LDAP server and polls it for

Operation

information, the server responds with an answer and downloads any
changes if necessary. LDAP directory services can save you a tremendous
amount of time by making it easy to update QoS parameters from a
single source instead of having to update each individual client. In
addition, QoS parameters stored on the server can be tailored to meet the
needs of different users by assigning group configuration names. The
ability to configure groups lets you associate a set of particular QoS
parameters with multiple CoreBuilder 3500 systems.
Group configuration names are created on the LDAP server.
When LDAP is enabled, it identifies the IP address of the LDAP server, a
poll time, and a groupConfig name. If a connection to the LDAP server
cannot be established when the CoreBuilder 3500 is powered on, the
settings stored in nvFlash are used to provide the fundamental QoS
parameters, including the default control (best effort) for the default
nonflow classifier (499). When a successful connection is made, the QoS
parameters are retrieved from the LDAP server using a search filter (a
group name or a wildcard). Once a CoreBuilder 3500 is associated with a
group configuration, it is automatically updated with the parameters
associated with that group configuration.
Each time you make a change to the QoS parameters, the change is sent
to the LDAP server immediately. In addition, the CoreBuilder 3500 clients
poll the LDAP server every poll period for new configuration information
and updates the new QoS configuration in nvFlash at that time.
You must have Administrator privileges (correct user name and password)
to access the LDAP server from the Administration Console. Otherwise,
the LDAP server denies the update request.