Cisco Cisco Unified IP Interactive Voice Response (IVR) 8.0(1) Administrator's Guide
8-47
Cisco Customer Response Solutions Administration Guide, Release 6.0(1)
Chapter 8 Managing the Cisco CRS System
Cisco CRS Utilities
One of the following happens:
•
The CRS Serviceability Utility connects to the LDAP Server and displays
bootstrap and cluster information.
bootstrap and cluster information.
•
If the CRS Serviceability Utility cannot connect to the LDAP server, a dialog
box appears. See
box appears. See
for more information.
Caution
Changing the LDAP info in the bootstrap, does not automatically
update the same information in the LDAP information page in the
Cisco Serviceability Utility. You need to specifically change it in the
LDAP tab in Cisco Serviceability Utility.
update the same information in the LDAP information page in the
Cisco Serviceability Utility. You need to specifically change it in the
LDAP tab in Cisco Serviceability Utility.
Synchronizing LDAP Bootstrap Information
Use the CRS Serviceability Utility to enter information to connect the LDAP
server and synchronize the bootstrap information between the CRS node and the
LDAP server.
server and synchronize the bootstrap information between the CRS node and the
LDAP server.
Caution
Changing the LDAP info in the bootstrap, does not automatically
update the same information in the LDAP information page in the
Cisco Serviceability Utility. You need to specifically change it in the
LDAP tab in Cisco Serviceability Utility.
update the same information in the LDAP information page in the
Cisco Serviceability Utility. You need to specifically change it in the
LDAP tab in Cisco Serviceability Utility.
To synchronize bootstrap information, complete the following steps.
Procedure
Step 1
In the CRS Serviceability Utility, specify LDAP server information as described
in the
in the
Step 2
Click SYNC.
Step 3
Since the utility does not update ccndir.ini on all nodes in the CRS cluster, repeat
these steps on each CRS node (where ccndir.ini is not correct) in the cluster.
these steps on each CRS node (where ccndir.ini is not correct) in the cluster.