test

Sun N1 Service Provisioning System User's Guide and Release Notes for the OS Provisioning Plug-In 2.0

Basic OS Configuration Variables

Component Variables for base_config Module

The variables described in the following list provide basic operating system configuration. These variables directly equate to the JET base_config module. In the list you see several variables that use the value of the targetable component. For purposes of the Solaris Profile variables, the targetable component is the target host.

ClientArch_base_config

Description: Kernel architecture, such as sun4u or x86. By default, this is set to the kernel architecture of the targetable component.

Default value: :[targetableComponent:kernel_arch]

ClientEther_base_config

Description: Ethernet MAC address. By default, this is set to the Ethernet MAC address of the targetable component.

Default value: :[targetableComponent:ethernet_mac_address]

ClientOS_base_config

Description: Version of the OS to be provisioned.

Example: Solaris9_u7_sparc

client_allocation_base_config

Description: The mechanism used to build this client. By default, the options listed in /opt/jet/etc/jumpstart.conf are used. Leave the value blank unless you need to do something different from the default for this specific client.

products_base_config

Description: JET modules to provision.

Example: base_config spsra

sysidcfg_nameservice_base_config

Description: Name service to configure at initial boot.

Default value: NIS

sysidcfg_network_interface_base_

Description: Network interface to use at initial boot.

Default value: PRIMARY

sysidcfg_ip_address_base_config

Description: IP address to use at initial boot. By default, this is set to the IP address of the targetable component.

Default value: :[targetableComponent:ethernet_ip_address]

sysidcfg_netmask_base_config

Description: Netmask to use at initial boot. By default, this is set to the netmask of the targetable component.

Default value: :[targetableComponent:ethernet_netmask]

sysidcfg_root_password_base_conf

Description: Encrypted root password.

Example: boajrOmU7GFmY is the encrypted value for the password “newroot.”

sysidcfg_system_locale_base_conf

Description: System locale to use at initial boot.

Example: en_US.ISO8859-1

sysidcfg_timeserver_base_config

Description: Where to get system time for initial boot. If blank, system time comes from the JET server. Alternatively, you can set this variable to localhost to get the system time from the hardware clock on the client.

sysidcfg_timezone_base_config

Description: System time zone to use for initial boot.

Example: US/Pacific

sysidcfg_terminal_base_config

Description: Terminal emulator to set at initial boot.

Default value: vt100

sysidcfg_security_policy_base_co

Description: Kerberos security policy to use at initial boot.

Default value: NONE

sysidcfg_protocol_ipv6_base_conf

Description: Whether to use IPv6 protocol at initial boot.

Default value: no

sysidcfg_default_route_base_conf

Description: Router IP address to use during JumpStart for Solaris 9 or later environments. If blank, will try to use value from the defaultrouter_base_config variable. If that is also blank, or for another net interface, JumpStart sysidcfg will get a router IP from the Jet server.

x86_nowin_base_config

Description: For x86 systems, prevents Solaris from trying to run Windows during the install.

Default value: yes

x86_console_base_config

Description: For x86 systems, set the console to the correct tty port if you are not going to connect a keyboard and monitor to the client. Setting this variable enables you to perform installs via the serial port. For b1600, v20z, and v40z systems, use ttya. For lx50, v60x, and v65x systems, use ttyb.

x86_disable_acpi_base_config

Description: For x86 systems, any value disables ACPI. Disabling ACPI might make the installation process proceed better due to how the interrupts are handled.

x86_safetoreboot_base_config

Description: For x86 systems, controls whether the system automatically reboots. If your PXE boot is a one time option, and the next reboot will attempt to boot from disk, you should set this option to yes.

profile_base_config

Description: Create your own custom JumpStart profile.

By default, if you leave this variable blank, the OS provisioning plug-in creates the /opt/SUNWjet/Clients/hostname/profile for you based on the following 21 profile_* variables. Alternatively, you can create your own custom JumpStart profile as explained in Solaris 10 Installation Guide: Custom JumpStart and Advanced Installations. To use the profile that you created manually, set the profile_base_config variable to the name of the created profile. By default, the OS provisioning plug-in looks for the profile in the /opt/SUNWjet/Clients/hostname directory. To direct the plug-in to a profile in another directory, provide an absolute path name in the profile_base_config variable.

profile_cluster_base_config

Description: Solaris software group package. SUNWCreq identifies the basic, required software. Other possibilities include:

  • SUNWCuser — User package

  • SUNWCprog — User and developer packages

  • SUNWCall — All packages

  • SUNWCXall — All packages, including OEM packages (mandatory for E10K environments)

  • SUNWCrnet — Minimal package for Solaris 10 only

Default value: SUNWCreq

profile_usedisk_base_config

Description: Defines the boot disks onto which the OS will be loaded. Use the format cntndn or the keyword rootdisk. If the value is rootdisk, then the current boot disk will be used.

Default value: rootdisk

profile_dontuse_base_config

Description: A comma-separated list of disks that should not be used. Use the format cntndn. This variable applies only if profile_usedisk_base_config is not set.

profile_root_base_config

Description: Root space (free, or size in Megabytes)

Default value: free

profile_swap_base_config

Description: Swap space (in Megabytes).

Default value: 256

profile_s3_mtpt_base_config

Description: Mount path to the slice 3 partition.

Note –

If you are using VxVM and you want your boot disk to look like the mirror, then leave slices 3 and 4 empty.

profile_s3_size_base_config

Description: Size of the slice 3 partition (in Megabytes).

profile_s4_mtpt_base_config

Description: Mount path to the slice 4 partition.

profile_s4_size_base_config

Description: Size of the slice 4 partition (in Megabytes).

profile_s5_mtpt_base_config

Description: Mount path to the slice 5 partition.

Default value: /var

profile_s5_size_base_config

Description: Size of the slice 5 partition (in Megabytes).

profile_s6_mtpt_base_config

Description: Mount path to the slice 6 partition.

Default value: /usr

profile_s6_size_base_config

Description: Size of the slice 6 partition (in Megabytes).

profile_s7_mtpt_base_config

Description: Mount path to the slice 7 partition.

Note –

If you are using Solaris Volume Manager (SVM), the default behavior is to use slice 7 as a location for metastate databases. If you are using the SVM default configuration, do not use slice 7 for data.

Default value: /opt

profile_s7_size_base_config

Description: Size of the slice 7 partition (in Megabytes).

profile_additional_disks_base_co

Description: A list of disks to use and configure in addition to the boot disk. Use the format cntndn. For each disk listed, define sets of variables for each slice to identify the mount point and the size. For more information, see Configuring Additional Disks.

profile_add_locales_base_config

Description: Comma-separated list of locales to add.

Example: fr_FR, ja_JP.UTF-8

profile_del_locales_base_config

Description: Comma-separated list of locales to delete.

profile_add_geos_base_config

Description: Comma-separated list of geographical regions to add.

Example: N_Europe, C_Europe

profile_del_geos_base_config

Description: Comma-separated list of geographical regions to delete.

ufs_logging_filesys_base_config

Description: For Solaris 7 and later systems, a space-separated list of mount points to use for logging. To enable logging on all UFS file systems, use the keyword all. Solaris 9 09/04 enables logging by default.

To disable logging on a specific file system, put a hyphen in front of the mount point. To disable logging on all file systems, use the keyword none.

Note –

You cannot mix keywords and mount points. You can specify the root file system (/), although the root file system is included as part of the all and none keywords.

Default value: all

profile_add_packages_base_config

Description: Space-separated list of packages to add.

profile_del_packages_base_config

Description: Space-separated list of packages to remove.

profile_add_clusters_base_config

Description: Space-separated list of cluster packages to add.

profile_del_clusters_base_config

Description: Space-separated list of cluster packages to remove.

Example: SUNWCpm SUNWCpmx SUNWCdial SUNWCdialx

nfs_mounts_base_config

Description: Space-separated list of remote NFS mount points. Use ? to separate the mount source from the mount target, as shown in the example.

Example: fs?1.1.1.1:/fs

nodename_base_config

Description: Value to use for /etc/nodename if not the default hostname.

defaultrouter_base_config

Description: Value to use for /etc/defaultrouter.

notrouter_base_config

Description: If set to y, then disable IPv4 forwarding and create /etc/notrouter file.

dns_domain_base_config

Description: DNS domain entry for /etc/resolv.conf file.

dns_nameservers_base_config

Description: Space-separated list of IP addresses to use for DNS nameserver entries in /etc/resolv.conf file.

dns_searchpath_base_config

Description: List of entries to go in the DNS search line in /etc/resolv.conf file.

dns_disableforbuild_base_config

Description: Delay DNS configuration until later. If DNS is not available in the build environment, set this variable to yes.

ntp_servers_base_config

Description: Space-separated list of names or IP addresses for the NTP servers. The first server will be given a “prefer” tag. This section places lines of the form: server [prefer] into the /etc/inet/ntp.conf file. For additional NTP control, use the custom module to deploy your own custom ntp.conf file.

networkifs_base_config

Description: Space-separated list of additional network interfaces to be defined. For logical interfaces, use underscores (_) rather than colons (:). Use the format cntndn. For each interface listed, define sets of variables to provide the netname, netmask, hostname, and IP address for the interface. For more information about this variable, see Configuring Additional Network Interfaces.

Example: le1!netB 255.255.255.0 myhost-netB 192.168.1.0

ipmp_networkifs_base_config

Description: Space-separated list of interfaces to be defined under IPMP control. For each interface listed, define sets of variables to provide the netgroup, mode, test1, test2, netmask, hostname, log-ip, hostname2, and log-ip2 for the interface. For more information about this variable, see Configuring IP Network Multipathing (IPMP).

Example: qfe0_qfe4!database-net l 10.0.0.1 10.0.0.2 24 oracle-db 10.0.0.3 apache 10.0.0.4

update_terminal_base_config

Description: If set, put the sysidcfg terminal type into inittab.

Default value: yes

enable_savecore_base_config

Description: If set to any value, enable save core for Solaris 2.6 systems.

Default value: yes

dumpadm_minfree_base_config

Description: Set a limit so that crash dumps do not fill up the dump filesystem. See dumpadm(1M) -m option for possible values.

Example: 20000k

noautoshutdown_base_config

Description: If set to any value, disable power management.

Default value: pm_disabled

enable_rootlogin_base_config

Description: If set to any value, enable network root login from both telnet/rsh and ssh.

enable_rootftp_base_config

Description: If set to any value, enable root FTP access.

shutup_sendmail_base_config

Description: If set, create an alias hostname to shut up sendmail.

Default value: yes

poweroff_afterbuild_base_config

Description: If set, shut down the machine once the build completes.

dedicated_dump_device_base_confi

Description: If set, the dumpadm utility configures the partition as a Dedicated Dump Device. See dumpadm(1M) for supported Operating Environments.

enable_altbreak_base_config

Description: If set, enable alternate break sequence.

disable_sysid_probe_base_config

Description: If set, skip the sysid stuff on the first reboot. This can significantly increase provisioning efficiency on systems that have many unused network adapters.

Default value: yes

nfsv4_domain_base_config

Description: Set up the NFSv4 domain to prevent being prompted at first reboot. If not set, look first for the entry in dns_domain_base_config, and second for the domain value in /etc/default/nfs.

productdir_base_config

Description: Path to the products. If blank, use information from the jumpstart.conf file and the IP address of the JET server. If your package files are not stored on the JET server, then provide an NFS-style path to the location of the packages.

patchdir_base_config

Description: Path to the patches. If blank, use information from the jumpstart.conf file and the IP address of the JET server. If your patch files are not stored on the JET server, then provide an NFS-style path to the location of the patches.

Configuring Additional Network Interfaces

The networkifs_base_config variable provides a way to configure additional network interfaces, in addition to the first network interface configured through the sysidcfg_network_interface_basevariable.

For each additional interface device, you provide a group of four variables that define the netname, netmask, hostname, and IP address for the interface.

The example below shows how to define the networkifs_base_config variable for two interfaces:

You would use the following syntax to define the single networkifs_base_config variable for the two additional interfaces:

le1!netB 255.255.255.0 myhost-netB 192.168.1.0|hme0!netC 255.255.255.0 myhost-netC 192.168.2.0

Configuring IP Network Multipathing (IPMP)

For general information about IPMP, see the IP Network Multipathing Administration Guide.

The default mode for IP multipathing in Solaris 8 or later environments is automatic failback. To change this mode, edit the /etc/default/mpathd file.

You can only set up an IPMP group with pairs of interfaces in one of the following configurations:

The ipmp_networkifs_base_config variable defines a list of interfaces to be defined under IPMP control. For each interface, a set of variables must be included to defined additional interface parameters. The following lists the parameters that you need to define:

The following example shows the content of the ipmp_networkifs_base_config variable to define one IPMP interface.

qfe0_qfe4!database-net l 10.0.0.1 10.0.0.2 24 oracle-db 10.0.0.3 apache 10.0.0.4

Configuring Additional Disks

The profile_additional_disks_base_co variable provides the ability to format and configure disks in addition to the root disk. Use the format cntndn to identify each additional disk.

The following example illustrates a three-disk configuration. The root disk is c0t0d0 and is defined using the variable profile_usedisk_base_config. The profile_additional_disks_base_co variable identifies two additional disks: c0t1d0 and c0t1d1 For each disk slice, a directory name is specified along with a size for that directory.

profile_usedisk_base_config = c0t0d0 
profile_additional_disks_base_co = c0t1d0s0!/export/mydisk1!5000MB|c0t1d1s0!/export/mydisk2!6000MB

Once you define these variables, you must perform two additional task to specify the slices to format and use on the named additional disks.

  1. Add a CHANGE line to the use the configuration file /opt/SUNWjet/etc/osp_jet_variables_to_replace on the JET server. For example:

    CHANGE:base_config:profile_additional_disks:profile_disk_<name>_mtpt, profile_disk_<name>_size
    Note –

    By modifying the JET server configuration file, this global edit applies until you change it in that file. Any Solaris profile that uses the profile_additional_disks_base_co variable on this JET server will use this information when you run the associated provision_start plan.

  2. Add the following line to the /opt/SUNWjet/etc/populate_client_dir file.

    base_config_profile_additional_disks="$(echo ${base_config_profile_additional_disks} | 
tr ' ' '\n' | sed 's/s[0-7]//' | sort -u)"

    Be sure that you add this line before the following code segment in the /opt/SUNWjet/etc/populate_client_dir file:

            #
        # Now check to see if any additional disks need to be defined
        #
        if [ -n "${base_config_profile_additional_disks}" ]; then

When you run the provision_start plan on the Solaris profile, appropriate files will be created to configure the two disks, with appropriate mount points and slices.