This preview shows page 715 - 719 out of 860 pages.
If you use a name service, configuring identification services involvesediting the source files that the name service uses and running commandsto update the name service.If the JumpStart client cannot obtain a response from a server for anyidentification item, the client interrupts the automatic identificationprocess and asks for the information.
Introducing the JumpStart Procedure17-6Advanced System Administration for the Solaris™ 9 Operating EnvironmentCopyright 2002 Sun Microsystems, Inc. All Rights Reserved. Enterprise Services, Revision AListing Identification Items and Their SourcesTable 17-1 lists the identification items that JumpStart clients usingSPARC®technology require, and also lists the sources in the Solaris 9 OEthat can provide the information. In earlier releases of the Solaris OE, thelist of items and usable sources sometimes differed. In systems with IntelArchitecture, you might need to specify additional items in thesysidcfgfile.Table 17-1JumpStart Client Identification ItemsIdentification ItemConfigurable WiththesysidcfgFile?Configurable With a NameService?Name serviceYesYesDomain nameYesNoName serverYesNoNetwork interfaceYesNoHost nameYesYesIP addressYesYesNetmaskYesYes, for the primary interfaceDynamic Host ConfigurationProtocol (DHCP)YesNoInternet Protocol Version 6 (IPv6)YesNoDefault routerYesNoRoot passwordYesNoSecurity policyYesNoLocaleYesYes if NIS or NIS+,No if DNS or LightweightDirectory Access Protocol (LDAP)Terminal TypeYesNoTime zoneYesYesDate and timeYesYesPower management (autoshutdown)NoNo
Introducing the JumpStart ProcedureConfiguring the Custom JumpStart™ Procedure17-7Copyright 2002 Sun Microsystems, Inc. All Rights Reserved. Enterprise Services, Revision AFor more information, refer to theAdvanced Installation Guideonline at.Configuration ServicesJumpStart clients require support from a server to automatically obtainanswers for system configuration questions that they issue. A system thatprovides this service is called a configuration server.A configuration server provides information that specifies how theSolaris OE installation will proceed on the JumpStart client. Configurationinformation can include:●Installation type●System type●Disk partitioning and file system specifications●Configuration cluster selection●Software package additions or deletionsOn the configuration server, files known as profile files store theconfiguration information. A file calledruleson the configuration serverallows JumpStart clients to select an appropriate profile file.
Introducing the JumpStart Procedure17-8Advanced System Administration for the Solaris™ 9 Operating EnvironmentCopyright 2002 Sun Microsystems, Inc. All Rights Reserved. Enterprise Services, Revision AAssociating a Configuration With a ClientA configuration server shares a directory (typically the/export/configdirectory) that minimally contains the files shown in Table 17-2.