The Solaris Profile component includes variables for each JET module. These variables are separated into the following categories:
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.
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]
Description: Ethernet MAC address. By default, this is set to the Ethernet MAC address of the targetable component.
Default value: :[targetableComponent:ethernet_mac_address]
Description: Version of the OS to be provisioned.
Example: Solaris9_u7_sparc
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.
Description: JET modules to provision.
Example: base_config spsra
Description: Name service to configure at initial boot.
Default value: NIS
Description: Network interface to use at initial boot.
Default value: PRIMARY
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]
Description: Netmask to use at initial boot. By default, this is set to the netmask of the targetable component.
Default value: :[targetableComponent:ethernet_netmask]
Description: Encrypted root password.
Example: boajrOmU7GFmY is the encrypted value for the password “newroot.”
Description: System locale to use at initial boot.
Example: en_US.ISO8859-1
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.
Description: System time zone to use for initial boot.
Example: US/Pacific
Description: Terminal emulator to set at initial boot.
Default value: vt100
Description: Kerberos security policy to use at initial boot.
Default value: NONE
Description: Whether to use IPv6 protocol at initial boot.
Default value: no
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.
Description: For x86 systems, prevents Solaris from trying to run Windows during the install.
Default value: yes
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.
Description: For x86 systems, any value disables ACPI. Disabling ACPI might make the installation process proceed better due to how the interrupts are handled.
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.
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.
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
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
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.
Description: Root space (free, or size in Megabytes)
Default value: free
Description: Swap space (in Megabytes).
Default value: 256
Description: Mount path to the slice 3 partition.
If you are using VxVM and you want your boot disk to look like the mirror, then leave slices 3 and 4 empty.
Description: Size of the slice 3 partition (in Megabytes).
Description: Mount path to the slice 4 partition.
Description: Size of the slice 4 partition (in Megabytes).
Description: Mount path to the slice 5 partition.
Default value: /var
Description: Size of the slice 5 partition (in Megabytes).
Description: Mount path to the slice 6 partition.
Default value: /usr
Description: Size of the slice 6 partition (in Megabytes).
Description: Mount path to the slice 7 partition.
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
Description: Size of the slice 7 partition (in Megabytes).
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.
Description: Comma-separated list of locales to add.
Example: fr_FR, ja_JP.UTF-8
Description: Comma-separated list of locales to delete.
Description: Comma-separated list of geographical regions to add.
Example: N_Europe, C_Europe
Description: Comma-separated list of geographical regions to delete.
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.
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
Description: Space-separated list of packages to add.
Description: Space-separated list of packages to remove.
Description: Space-separated list of cluster packages to add.
Description: Space-separated list of cluster packages to remove.
Example: SUNWCpm SUNWCpmx SUNWCdial SUNWCdialx
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
Description: Value to use for /etc/nodename if not the default hostname.
Description: Value to use for /etc/defaultrouter.
Description: If set to y, then disable IPv4 forwarding and create /etc/notrouter file.
Description: DNS domain entry for /etc/resolv.conf file.
Description: Space-separated list of IP addresses to use for DNS nameserver entries in /etc/resolv.conf file.
Description: List of entries to go in the DNS search line in /etc/resolv.conf file.
Description: Delay DNS configuration until later. If DNS is not available in the build environment, set this variable to yes.
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.
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
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
Description: If set, put the sysidcfg terminal type into inittab.
Default value: yes
Description: If set to any value, enable save core for Solaris 2.6 systems.
Default value: yes
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
Description: If set to any value, disable power management.
Default value: pm_disabled
Description: If set to any value, enable network root login from both telnet/rsh and ssh.
Description: If set to any value, enable root FTP access.
Description: If set, create an alias hostname to shut up sendmail.
Default value: yes
Description: If set, shut down the machine once the build completes.
Description: If set, the dumpadm utility configures the partition as a Dedicated Dump Device. See dumpadm(1M) for supported Operating Environments.
Description: If set, enable alternate break sequence.
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
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.
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.
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.
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:
le1
netname — netB
netmask — 255.255.255.0
hostname — myhost-netB
interface IP — 192.168.1.0
hme0
netname — netC
netmask — 255.255.255.0
hostname — myhost-netC
interface IP — 192.162.2.0
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
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:
active-standby failover — Set ipmp mode = s, and specify one logical hostname/ip address pair.
failover with outbound load spreading — Set ipmp mode = l, and specify one logical hostname/ip address pair.
active-active with outbound load spreading — Set ipmp mode = l, specify a second logical hostname/ip address pair for the second interface.
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:
netgroup — identifies the IPMP interface group name; for example, database-net
mode — specifies the IPMP mode; Valid values include:
s — standby mode; used for failover only. In this mode, test addresses are allocated last. The first test address is on the first virtual interface of the first physical adapter. The second test address is on the second physical adapter.
l — load spreading; used for active/active mode. In this mode, test addresses are allocated on the first virtual interfaces on both the first and second physical adapters.
To force the test addresses onto the physical adapters, add the suffix “p” to either mode parameter.
Be careful forcing the test addresses onto the physical adapter, as this might break some applications.
test1 — IPMP test address 1
This address must not be in the hosts file or otherwise used.
test2 — IPMP test address 2
This address must not be in the hosts file or otherwise used.
netmask — Netmask for IPMP pair
hostname — Unique hostname for logical IP
log-ip — Logical IP for first i/f of pair
hostname 2 — For active-active configurations only, unique hostname for logical IP
log-ip2 — For active-active configurations only, local IP for second i/f of pair
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
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.
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
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.
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.
The variables described in the following list provide Remote Agent (RA) configuration for the N1 SPS software. These variables directly equate to the JET spsra module.
Description: Whether to install the N1 SPS RA software.
Default value: y
Description: Version of RA to install.
Default value: 5.1
Description: Base directory in which RA files are installed.
Default value: /opt/SUNWn1sps
Description: Determines where to get RA files. When you install the JET server or attach the JET server, a snapshot of the RA on the JET server is taken automatically. As a result, this variable defaults to y. Set the variable to n for a cross architecture install. In this case, you need to import the product media for the JET module by using the Manage link in the JET Solaris Image Servers section of the OS Provisioning common tasks page.
Default value: y
Description: When using the RA installer, specify user name to own the RA filesystem.
Example: jdoe
Description: When using the RA installer, specify group name to own the RA filesystem.
Example: staff
Description: Determines whether to set up user and group account for username_spsra and groupname_spsra.
Default value: n
Description: Encrypted password for username_spsra.
Example: 6GR9gOi1vRVFw shows the encrypted value for the password “n1spspwd.”
Description: User account ID for username_spsra.
Example: 505
Description: Group account ID for groupname_spsra.
Example: 505
Description: Home directory for RA files.
Default value: /opt/SUNWn1sps
Description: Path to the Java runtime environment. If no value is provided, use the path suggested by the installer. If a path is given, the JRE must be installed at that path or the installation fails.
Description: Enable RA root access.
Default value: y
Description: Determines method to use for connecting to RA. By default, uses the connection method defined for the targetable component.
Default value: :[targetableComponent:sps_ra_conn]
Description: SSL authorization to use for network connection.
Default value: 1
Description: Port to use for network connection. By default, uses the port defined for the targetable component.
To use an SSH connection, set the port number to 70000.
Default value: :[targetableComponent:sps_ra_port]
Description: Advanced parameters to use for network connection. By default, uses the advanced parameters defined for the targetable component.
Default value: :[targetableComponent:sps_ra_adv_parms]
The variables in the following list are general variables that the OS provisioning plug-in requires. They are not technically part of the JET modules, but are required for the OS provisioning plug-in to interface between JET and the N1 SPS software.
Description: Jumpstart Enterprise Toolkit (JET) virtual host.
Example: myhost-jet
Description: Target host name.
Default value: :[targetableComponent:installPath]
Description: Whether to call the OSP Control Service, which automates power off, reboot, and power on functions (True, False).
Default value: :[targetableComponent:osp_control_service]
Description: Host name of the N1 SPS RA parent.
Default value: :[targetableComponent:sps_ra_parent]
Description: Host type of the N1 SPS RA parent (MS or LD).
Default value: :[targetableComponent:sps_ra_parent_type]
Description: Host name of the JET server.
Example: myserver
Description: Target host architecture (sun4u, x86).
Default value: :[targetableComponent:architecture]
Description: Minimum disk size.
Example: 5GB
Description: Profile description.
Description: OS provisioning monitor (TRUE, FALSE).
Default value: FALSE
Description: Solaris boot server name.
Default value: :[osp_jet_server]
Description: Subnet served by boot server.
Description: IP address of boot server on this subnet.
Example: 199.199.8.6
Description: IP address of Solaris image server.
Example: 199.199.8.6
Description: Path to image directory on image server.
Example: /osp_image/Solaris9_u7_sparc
Description: IP address of Solaris boot server.
Example: 199.199.8.6
Description: Solaris boot directory.
Default value: /osp_image/Solaris9_u7_sparc/Solaris_9/Tools/Boot
Description: IP address of system ID configuration.
Example: 199.199.8.6
Description: Directory of system ID configuration.
Default value: /opt/SUNWjet/Clients/:[osp_target_host]
Description: JumpStart IP address
Example: 199.199.8.6
Description: JumpStart directory
Default value: /opt/SUNWjet
Description: Solaris boot file name.
Default value: :[osp_target_host]
Description: Network boot file name.
Default value: :[osp_target_host]