Once you have configured the XSCF network, it requires no
The Domain Name Service (DNS) allows computers on a network to communicate with each other by using centrally maintained DNS names instead of locally stored IP addresses. If you configure the Service Processor to use the DNS service, it “joins” the DNS community and can communicate with any other computer on the network through its DNS server.
There are no defaults for this service. To configure the Service Processor to use DNS, you must specify the Service Processor host name, and the DNS server name and IP address.
You can configure the Service Processor DNS service with these commands:
■sethostname
■setnameserver
On a server with dual Service Processors, the domain name is common for both Service Processors. A host name can be specified for each Service Processor. Setting a different host name for each Service Processor does not disable failover.
Once you have configured the Service Processor to use the DNS service, it does not require
The LDAP service stores user authentication and privilege settings on a server so that individual computers on the network do not have to store the settings.
By default, the Service Processor stores user passwords and privileges locally. Account information for users who have access to the Service Processor are stored on the Service Processor itself. (Authentication and privilege lookups for the server’s domains are provided by the Solaris OS.)
However, if you want to have authentication and privilege lookups performed by an LDAP server, you can set up the Service Processor to be an LDAP client.
The general process for setting up the Service Processor as an LDAP client is:
1.Enable the LDAP service.
2.Provide the LDAP server configuration information:
■ The IP address or hostname, and port, of the primary LDAP directory
Chapter 3 System Configuration | 21 |