Users Guide

• If DHCP is enabled on CMC and you want to use the DNS address obtained automatically by the DHCP server, type the
following command:
racadm config -g cfgLanNetworking -o
cfgDNSServersFromDHCP 1
• If DHCP is disabled on CMC, or if DHCP is enabled but you want to specify your DNS IP address manually, type following
commands:
racadm config -g cfgLanNetworking -o
cfgDNSServersFromDHCP 0
racadm config -g cfgLanNetworking -o
cfgDNSServer1 <primary DNS IP address>
racadm config -g cfgLanNetworking -o
cfgDNSServer2 <secondary DNS IP address>
The Extended Schema feature configuration is complete.
Configuring Generic LDAP Users
CMC provides a generic solution to support Lightweight Directory Access Protocol (LDAP)-based authentication. This feature does
not require any schema extension on your directory services.
A CMC administrator can now integrate the LDAP server user logins with CMC. This integration requires configuration on both
LDAP server and CMC. On the LDAP server, a standard group object is used as a role group. A user who has CMC access becomes
a member of the role group. Privileges are still stored on CMC for authorization similar to the working of the Standard Schema
setup with Active Directory support.
To enable the LDAP user to access a specific CMC card, the role group name and its domain name must be configured on the
specific CMC card. You can configure a maximum of five role groups in each CMC. A user has the option to be added to multiple
groups within the directory service. If a user is a member of multiple groups, then the user obtains the privileges of all their groups.
For information about the privileges level of the role groups and the default role group settings, see Types of Users.
The following figure illustrates configuration of CMC with Generic LDAP.
Figure 3. Configuration of CMC with Generic LDAP
Configuring the Generic LDAP Directory to Access CMC
The CMC's Generic LDAP implementation uses two phases in granting access to a user—user authentication and then user
authorization.
Authentication of LDAP Users
Some directory servers require a bind before any searches can be performed against a specific LDAP server.
140