D JumpStart Enterprise Toolkit

JumpStart Enterprise Toolkit Configuration File Location

The JET module parameters are available for use in OS profiles. See the module.conf configuration files that are associated with JET modules for information about parameters for specific JET modules. The configuration files are located in the /opt/SUNWjet/Products directory on the Proxy Controller. For example, the configuration files for the custom module is located in the following directory on the Proxy Controller: /opt/SUNWjet/Products/custom/custom.conf. You can review the parameters for these modules by looking at the sample.template file in the /opt/SUNWjet/Templates directory on a Proxy Controller.

SUNWjet Parameters

When you specify JET parameters with an OS profile, the following parameters from the base_config JET module are automatically updated within the OS profile and must not be modified:

• base_config_ClientArch

• base_config_ClientEther

• base_config_client_allocation

• base_config_sysidcfg_network_interface

• base_config_sysidcfg_ip_address

• base_config_sysidcfg_netmask

• base_config_sysidcfg_nameservice

• base_config_sysidcfg_system_locale

• base_config_sysidcfg_terminal

• base_config_sysidcfg_timeserve

• base_config_sysidcfg_timezone

• base_config_sysidcfg_root_password

• base_config_sysidcfg_security_policy

• base_config_sysidcfg_protocol_ipv6

The following list describes the parameters that are associated with the base_config JET module. These parameters provide basic operating system configuration information. Values for many of these parameters use the term targetableComponent to represent the target system.

• base_config_client_allocation – The mechanism used to build this client. By default, the options listed in /opt/SUNWjet/etc/jumpstart.conf are used. Leave the value blank unless you need to do something different from the default for this specific client. If you are provisioning the Solaris 10 1/06 x86 release, set the value of this variable to GRUB to enable GRUB-based booting and installation.

• base_config_ClientArch – 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]

• base_config_ClientEther – Ethernet MAC address. By default, this is set to the Ethernet MAC address of the targetable component.

  • Default Value – [targetableComponent:ethernet_mac_address]

• base_config_ClientOS – Version of the OS to be provisioned.

  • Example – Solaris9_u7_sparc

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

• base_config_defaultrouter – Value to use for /etc/defaultrouter.

• base_config_disable_sysid_probe – If set, skip the sysid step on the first reboot. This can significantly increase provisioning efficiency on systems that have many unused network adapters.

  • Default Value – yes

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

• base_config_dns_domain – DNS domain entry for the /etc/resolv.conf file.

• base_config_dns_nameservers – Space-separated list of IP addresses to use for DNS name server entries in the /etc/resolv.conf file.

• base_config_dns_searchpath – List of entries to go in the DNS search line in /etc/resolv.conf file.

• base_config_dumpadm_minfree – Set a limit so that crash dumps do not fill up the dump file system. See the dumpadm(1M) -m option for possible values.

  • Example – 20000k

• base_config_enable_altbreak – If set, enable alternate break sequence.

• base_config_enable_rootftp – If set to any value, enable root FTP access.

• base_config_enable_rootlogin – If set to any value, enable network root login from telnet, rsh, and ssh.

• base_config_enable_savecore – If set to any value, enable save core for Solaris 2.6 systems.

  • Default Value – yes

• base_config_grub_append – For Solaris 10 1/06 x86 systems, specifies additional options or arguments to pass to the GRUB bootloader.

• base_config_ipmp_networkifs – 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, host name, log-ip, hostname2, and log-ip2 for the interface.

  • 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

• base_config_networkifs – Space-separated list of additional network interfaces to be defined. For logical interfaces, use underscores (_) rather than colons (:). Use the format c_ntndn. For each interface listed, define sets of variables to provide the netname, netmask, host name, and IP address for the interface.

  • Example – le1!netB 255.255.255.0 myhost-netB 192.168.1.0

• base_config_nfs_mounts – 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

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

• base_config_noautoshutdown – If set to any value, disable power management.

  • Default Value – pm_disabled

• base_config_nodename – Value to use for /etc/nodename if not the default host name.

• base_config_notrouter – If set to y, then disable IPv4 forwarding and create the /etc/notrouter file.

• base_config_ntp_servers – 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.

• base_config_patchdir – 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.

• base_config_poweroff_afterbuild – If set, shut down the system once the build completes.

• base_config_productdir – 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.

• base_config_products – JET modules to provision.

• base_config_profile – 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 based on the other base_config_profile variables. Alternatively, you can create your own custom JumpStart profile. To use the profile that you created manually, set the base_config_profile 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 base_config_profile variable.

  Note:

  If you are provisioning the Solaris OS on x86 target hosts, you must create a custom JumpStart profile that deletes any existing partitions, and point to that profile in the base_config_profile variable.

• base_config_profile_add_clusters – Space-separated list of cluster packages to add.

• base_config_profile_add_geos – Comma-separated list of geographical regions to add.

  • Example – N_Europe, C_Europe

• base_config_profile_add_locales – Comma-separated list of locales to add.

  • Example – fr_FR, ja_JP.UTF-8

• base_config_profile_add_packages – Space-separated list of packages to add.

• base_config_profile_additional_disks – 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.

• base_config_profile_cluster – Solaris software group package.

  • Default Value – SUNWCreq

  • Example – SUNWCreqSUNWCuserSUNWCprogSUNWCallSUNWCXallSUNWCrnet

• base_config_profile_del_clusters – Space-separated list of cluster packages to remove.

  • Example – SUNWCpm SUNWCpmx SUNWCdial SUNWCdialx

• base_config_profile_del_geos – Comma-separated list of geographical regions to delete.

• base_config_profile_del_locales – Comma-separated list of locales to delete.

• base_config_profile_del_packages – Space-separated list of packages to remove. To prevent interactive installations on Solaris x86 headless target hosts, set this value to SUNWxwssu SUNWxwscf.

• base_config_profile_dontuse – A comma-separated list of disks that must not be used. Use the format cntndn. This variable applies only if base_config_profile_usedisk is not set.

• base_config_profile_root – Root space (free, or size in Megabytes)

  • Default Value – free.

• base_config_profile_s3_mtpt – Mount path to slice 3.

  Note:

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

• base_config_profile_s3_size – Size of slice 3 (in Megabytes).

• base_config_profile_s4_mtpt – Mount path of slice 4.

• base_config_profile_s4_size – Size of slice 4 (in Megabytes).

• base_config_profile_s5_mtpt – Mount path of slice 5.

  • Default Value – /var

• base_config_profile_s5_size – Size of slice 5 (in Megabytes).

• base_config_profile_s6_mtpt – Mount path of slice 6.

  • Default Value – /usr

• base_config_profile_s6_size – Size of slice 6 (in Megabytes).

• base_config_profile_s7_mtpt – Mount path of slice 7.

  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

• base_config_profile_s7_size – Size of slice 7 (in Megabytes).

• base_config_profile_swap – Swap space (in Megabytes).

  • Default Value – 256

• base_config_profile_usedisk – Defines the boot disk 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

• base_config_shutup_sendmail – If set, create an alias host name to disable sendmail.

  • Default Value – yes

• base_config_sysidcfg_default_route – 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.

• base_config_sysidcfg_ip_address – 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]

• base_config_sysidcfg_nameservice – Name service to configure at initial boot.

  • Default Value – NIS

• base_config_sysidcfg_netmask – Netmask to use at initial boot. By default, this is set to the netmask of the targetable component.

  • Default Value – [targetableComponent:ethernet_netmask]

• base_config_sysidcfg_network_interface – Network interface to use at initial boot.

  • Default Value – NONE

• base_config_sysidcfg_protocol_ipv6 – Whether to use IPv6 protocol at initial boot.

  • Default Value – no

• base_config_sysidcfg_root_password – Encrypted root password.

• base_config_sysidcfg_security_policy – Kerberos security policy to use at initial boot.

  • Default Value – NONE

• base_config_sysidcfg_system_locale – System locale to use at initial boot.

  • Example – en_US.ISO8859-1

• base_config_sysidcfg_terminal – Terminal emulator to set at initial boot.

  • Default Value – vt100

• base_config_sysidcfg_timeserver – 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.

• base_config_sysidcfg_timezone – System time zone to use for initial boot.

  • Example – US/Pacific

• base_config_sysidcfg_x86_kdmfile – For Solaris x86 systems, specifies the name of a keyboard, display, and mouse configuration file to append to the sysidcfg file.

  • Default Value – /sysidcfg-addon-file

• base_config_ufs_logging_filesys – 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, add 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

• base_config_update_terminal – If set, put the sysidcfg terminal type into inittab.

  • Default Value – yes

• base_config_x86_confflags – For Solaris 9 x86 systems, specifies arguments to be used with the confflags attribute of the add_install_client command.

  • Example – -f -P /boot/solaris/dca

• base_config_x86_console – 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 through the serial port. For b1600, v20z, and v40z systems, use ttya. For lx50, v60x, and v65x systems, use ttyb.

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

• base_config_x86_disable_kdmconfig – For Solaris x86 systems, disables the kdmconfig interactive utility for configuring the keyboard, display, and mouse of the target host. If you are installing a Solaris OS with the GRUB bootloader, set this variable value to yes.

• base_config_x86_nowin – For x86 systems, prevents Solaris from trying to run Windows during the install.

  • Default Value – yes

• base_config_x86_safetoreboot – 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 must set this option to yes.