sysman_clone(8) 					      System Manager's Manual						   sysman_clone(8)

NAME

       sysman_clone -  Saves SysMan configuration information, which can be used to clone configurations on similar systems

SYNOPSIS

       /usr/sbin/sysman  -clone /usr/sbin/sysman -clone -apply [file] /usr/sbin/sysman -clone -help /usr/sbin/sysman -clone -list /usr/sbin/sysman
       -clone -save [file] /usr/sbin/sysman -clone -validate [file]

OPTIONS

       The file argument is optional and specifies an alternate path to the configuration description file (CDF).  The default path and file  name
       is  var/adm/smlogs/config.cdf.	Applies  the  configuration information specified in the /var/adm/smlogs/config.cdf file.  If the optional
       file parameter is specified, this parameter specifies a CDF file in an alternate location.  When performing an  apply  operation,  the  CDF
       automatically  is  validated prior to the actual apply operation.  Displays command usage information for the sysman(8) command.  Lists the
       current values for all configured SysMan components/groups supported by sysman -clone.  Saves the current values for all configured  SysMan
       components/groups  supported  by sysman -clone to the /var/adm/smlogs/config.cdf file.  If the optional file parameter is specified, compo-
       nent/group information is saved to the specified file instead  of  /var/adm/smlogs/config.cdf.	Validates  the	file  /var/adm/smlogs/con-
       fig.cdf,  or the file specified by the optional file parameter.	The validation pass consists of invoking each component's built-in valida-
       tion routine and the checksum number at the top of the file.

DESCRIPTION

       The sysman -clone command provides the ability to save certain SysMan configuration information from a  previously  configured  system  and
       duplicate  that	configuration  information  to one or more systems with a similar hardware configuration. The configuration information is
       saved to a text-based Configuration Description File (CDF).  The CDF is organized as a pseudo stanza(4) file, with a  hierarchical  listing
       of components, groups, and attribute-value pairs describing the configuration of various components of a system.

       It is recommended that you use the sysman(8) command to access sysman -clone functions.

       The  following  components  can	be cloned: Network interface Domain Name Service (DNS) client setup Network File System (NFS) Network Time
       Protocol (NTP) Network Information Service (NIS) Internet services Mail client setup Printer setup

       Supported components and groups, as well as their current values, can be queried through the use of the -list  flag.  For  descriptions	of
       each component, group, and attribute, and how it affects the configured system, refer to the sysmancli(8) command.

       The config.cdf file is particularly useful during a Full Installation of the operating system to provide an automated and unattended system
       configuration. Combining this ability with an Installation Cloning provides for an efficient way to install and configure multiple  systems
       in a non-interactive fashion. The Full Installation process searches for the installation CDF (named install.cdf) and the configuration CDF
       in these locations in the order shown: Diskette drive Remote Installation Services (RIS) directory CD-ROM drive The /var/tmp directory

       The Installation Guide -- Advanced Topics provides detailed information about Installation Cloning, Configuration Cloning, the placement of
       CDFs,  and  writing user-supplied scripts to dynamically modify CDFs.  The Full Installation process always searches for CDFs at predefined
       points in the process.  If a CDF is found in any of the supported locations, it will be applied automatically  to  install,  configure,	or
       install and configure the target system.

   Generating Unique Client Configurations
       When saving the configuration of a model system with the intention of applying the configuration to multiple target systems, there are sev-
       eral host-specific attributes that you need to modify to allow each target system to be uniquely identified on  a  network.   The  specific
       host-specific  attributes  that must be modified are: The unique name of the system as it is known on a network.  This attribute is located
       in the netconfig component in the interface group, and depending upon which other components are configured, the host name may be specified
       in other attributes.  Make sure to search for and change all instances of host name.  The unique internet protocol address of the system as
       it is identified on a network.  This attribute is located in the netconfig component in the interface and host groups.  The network adapter
       attached to the system.	This value is modified only if the network adapter on the system to be cloned is different from the one defined in
       the config.cdf file.  Valid values for this attribute include tu0 for Tulip devices, ln0 for Lance devices, and fddi0 for FDDI devices.

       To facilitate configuration cloning of multiple target systems, it is suggested that you create a single  template  or  representative  CDF
       with  the  values  of  these  host-specific attributes set to dummy variables.  You can then manually enter a value for the dummy variables
       before applying them to a target system, or you can create a user-supplied script, which is invoked during a Full Installation  to  dynami-
       cally modify a config.cdf file before it is applied to the system.  This procedure is documented in the Installation Guide -- Advanced Top-
       ics.

   The Global Attribute CDFMODE
       During the application of configuration information to a client system, it is possible to specify how the values of databases with multiple
       records	(for  example,	entries  in  /etc/hosts  or /etc/printcap) should be applied to the system.  The CDFMODE attribute is a global CDF
       attribute that can be specified manually and placed outside of any component contained within the CDF file.   The  CDFMODE  attribute  only
       affects	databases with multiple records; individual component/group data always will be overwritten by the new value specified in the CDF.
       Once a CDFMODE has been specified in a CDF, that value is in effect until another CDFMODE statement is encountered, or  the  apply  process
       completes.

       There  are three values associated with the CDFMODE attribute: Merges the component/group data that exists in the CDF with the data that is
       currently configured on the system. Using the merge functionality, rows of records that are duplicated between the CDF and  the	configured
       system  are ignored.  MERGE is the default behavior and is implied for the entire CDF if CDFMODE is not specified.  Appends component/group
       data that exists in the CDF to the configured system.  Duplicate entries that exist between the CDF and the configured system will  not	be
       ignored.  Replaces component/group data that exists on the system with the data specified in the CDF.  Data existing on the configured sys-
       tem but not in the CDF will be removed.	Data that exists in the CDF, but not on the configured system, will be applied. Data  that  exists
       in the CDF, as well as the configured system, will be modified accordingly.

RESTRICTIONS

       You must be a privileged user to use this command.

       Configuration cloning is not supported in a cluster.

EXAMPLES

       The  following  example	lists  to stdout the components, groups, and attribute-value pairs for the supported SysMan clonable configuration
       data.  sysman -clone -list The following example saves SysMan configuration data to a CDF named template.cdf in the /admin directory.  sys-
       man   -clone  -save  /admin/template.cdf  The  following  example  manually  applies  the  saved  configuration	information  specified	in
       /var/adm/smlogs/config.cdf to the target system.  The config.cdf file must be located in the /var/adm/smlogs directory of the system to	be
       cloned.	 sysman  -clone  -apply The following example uses the CDFMODE global attribute to specify that all entries in the /etc/hosts file
       should be replaced by the data specified in the hostmappings group.  The CDFMODE attribute is then reset to merge for the rest of the apply
       process.  CDFMODE=REPLACE

       # # Component: networkedSystems #

       # # Group: hostEquivalencies # /networkedSystems/hostEquivalencies: # # Group: hostMappings # /networkedSystems/hostMappings:
	       cdf_record=00000001
	       networkAddress=127.0.0.1
	       systemName=localhost
	       cdf_record=00000002
	       aliases=host1
	       networkAddress=16.29.1.1
	       systemName=host1.mydomain.com
	       cdf_record=00000003
	       networkAddress=16.29.1.15
	       systemName=host2
	       cdf_record=00000004
	       aliases=host3
	       networkAddress=16.29.1.27
	       systemName=host3.mydomain.com

       CDFMODE=MERGE

SEE ALSO

       Commands:  sysman(8), sysmancli(8)

       Installation Guide -- Advanced Topics

       Installation Guide delim off

																   sysman_clone(8)