Ldap; Important Considerations - 3Com corebuilder 3500 Implementation Manual

514 C 17: Q
HAPTER O

LDAP

Important
Considerations
S RSVP
AND
When you modify the QoS bandwidth, you specify the percentage of
bandwidth used for the high priority transmit queue on the output link.
You can specify a value in the range 0 to 100. The value you specify
determines the ratio of high priority to best effort traffic, as follows:
The value 75 (the default) specifies that three high-priority packets are
transmitted for each best effort packet (ratio of 75/25).
The value 50 sets equal priority for high priority and best effort
packets (ratio of 50/50).
The value 100 is strict prioritization; it allows best effort packets to be
sent only when no high priority packets need to be sent.
No bandwidth is ever lost. Because QoS uses ratios, any unused
bandwidth can be used by a lower priority queue.
Lightweight Directory Access Protocol (LDAP) is an Internet standard for
directory services. LDAP directory services is based on the client/server
model and runs over TCP/IP. The CoreBuilder 3500 contains the LDAP
client software necessary to communicate and exchange configuration
information for QoS parameters stored on the LDAP server.
Review the following before you enable LDAP on your system.
You must configure an LDAP server on either a workstation/PC (using
LDAP from Netscape Navigator), or on a Solaris or HP Unix
workstation (using University of Michigan LDAP). Each group of
CoreBuilder 3500s have QoS parameters stored in a particular
directory on the server.
The LDAP server must have an initial set of QoS parameters before
LDAP can be used. This is typically accomplished by installing an "ldif"
file on the server for each QoS group. The ldif file is specific to the
CoreBuilder 3500 and is necessary for the client software to run.
For the ldif file with default settings, see the Software and
Documentation CD-ROM that is shipped with your system.
Parameter changes for a specific group may affect more than one
system. If you know that a change will affect more than one system,
you should disable LDAP to test the change. After you are sure you
want the change you can reenable LDAP.