If you use a name service configuring identification services involves editing

If you use a name service configuring identification

This preview shows page 715 - 719 out of 860 pages.

If you use a name service, configuring identification services involves editing the source files that the name service uses and running commands to update the name service. If the JumpStart client cannot obtain a response from a server for any identification item, the client interrupts the automatic identification process and asks for the information.
Introducing the JumpStart Procedure 17-6 Advanced System Administration for the Solaris™ 9 Operating Environment Copyright 2002 Sun Microsystems, Inc. All Rights Reserved. Enterprise Services, Revision A Listing Identification Items and Their Sources Table 17-1 lists the identification items that JumpStart clients using SPARC ® technology require, and also lists the sources in the Solaris 9 OE that can provide the information. In earlier releases of the Solaris OE, the list of items and usable sources sometimes differed. In systems with Intel Architecture, you might need to specify additional items in the sysidcfg file. Table 17-1 JumpStart Client Identification Items Identification Item Configurable With the sysidcfg File? Configurable With a Name Service? Name service Yes Yes Domain name Yes No Name server Yes No Network interface Yes No Host name Yes Yes IP address Yes Yes Netmask Yes Yes, for the primary interface Dynamic Host Configuration Protocol (DHCP) Yes No Internet Protocol Version 6 (IPv6) Yes No Default router Yes No Root password Yes No Security policy Yes No Locale Yes Yes if NIS or NIS+, No if DNS or Lightweight Directory Access Protocol (LDAP) Terminal Type Yes No Time zone Yes Yes Date and time Yes Yes Power management (auto shutdown) No No
Introducing the JumpStart Procedure Configuring the Custom JumpStart™ Procedure 17-7 Copyright 2002 Sun Microsystems, Inc. All Rights Reserved. Enterprise Services, Revision A For more information, refer to the Advanced Installation Guide online at . Configuration Services JumpStart clients require support from a server to automatically obtain answers for system configuration questions that they issue. A system that provides this service is called a configuration server. A configuration server provides information that specifies how the Solaris OE installation will proceed on the JumpStart client. Configuration information can include: Installation type System type Disk partitioning and file system specifications Configuration cluster selection Software package additions or deletions On the configuration server, files known as profile files store the configuration information. A file called rules on the configuration server allows JumpStart clients to select an appropriate profile file.
Introducing the JumpStart Procedure 17-8 Advanced System Administration for the Solaris™ 9 Operating Environment Copyright 2002 Sun Microsystems, Inc. All Rights Reserved. Enterprise Services, Revision A Associating a Configuration With a Client A configuration server shares a directory (typically the /export/config directory) that minimally contains the files shown in Table 17-2.

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture