sysidcfg(4)

NAME | DESCRIPTION | EXAMPLES | SEE ALSO

NAME

sysidcfg- system identification configuration file

DESCRIPTION

When a diskless client boots for the first time or a system installs over the network, the booting software tries to obtain configuration information about the system (such as the system's root password or name service) from a sysidcfg file first and then the name service databases. If the booting software cannot find the information, it prompts the user to provide the appropriate information. Like the name service databases, the sysidcfg file can be used to avoid all the prompts and provide a totally hands-off booting process.

The sysidcfg file preconfigures information through a set of keywords, and you can specify one or more of the keywords to preconfigure as much information as you want. Also, every system that requires different configuration information must have a different sysidcfg file. For example, you can use the same sysidcfg file to preconfigure the time zone for multiple systems if you want all the systems to have the same time zone configured. However, if you want to preconfigure a different root password for each of those systems, then each system would need its own sysidcfg file.

Where To Put the sysidcfg File

The sysidcfg file can reside on a shared NFS network directory or the root directory on a UFS or PCFS diskette in the system's diskette drive. If you put the sysidcfg file on a shared NFS network directory, you have to use the -p option of the add_install_client(1M) command (see install_scripts(1M)) to specify where the system being installed can find the sysidcfg file. If you put the sysidcfg file on a diskette, you need to make sure the diskette is in the system's diskette drive when the system boots (on IA systems, the sysidcfg file should reside on the Solaris Device Configuration Assistant diskette).

Only one sysidcfg file can reside in a directory or diskette. If you are creating more than one sysidcfg file, they must reside in different directories or diskettes.

Keyword Syntax Rules

The following rules apply to the keywords in a sysidcfg file:

• Keywords can be in any order

• Keywords are not case sensitive

• Keyword values can be optionally enclosed in single (') or double (") quotes

• Only the first instance of a keyword is valid; if you specify the same keyword more than once, the first keyword specified will be used.

Keywords - All Platforms

Name service, domain name, name server

Keywords	Example
name_service=NIS, NIS+, DNS, NONE
Options for NIS and NIS+: domain_name=domain_name; name_server=hostname(ip_address)	name_service=NIS {domain_name=west.arp.com name_server=timber(129.221.2.1)}
	name_service=NIS+ {domain_name=west.arp.com name_server=timber(129.221.2.1)}
Options for DNS: domain_name=domain_name; name_server=ip_address, ip_address, ip_address (three maximum); search=domain_name, domain_name, domain_name, domain_name, domain_name, domain_name (six maximum, total length less than or equal to 250 characters)	name_service=DNS {domain_name=west.arp.com name_server=10.0.1.10,10.0.1.20 search=arp.com,east.arp.com}

Choose only one value for name_service. Include either, both, or neither of the domain_name and name_server keywords, as needed. If no keywords are used, omit the curly braces {}.

Network interface, host name, Internet Protocol (IP) address, netmask, DHCP, IPv6

Keywords	Example
network_interface=NONE, PRIMARY, value
If DHCP is to be used, the options for PRIMARY and value are: dhcp; protocol_ipv6=yes_or_no	network_interface=primary {dhcp protocol_ipv6=yes}
If DHCP is not to be used, the options for PRIMARY and value are: hostname=host_name; ip_address=ip_address; netmask=netmask; protocol_ipv6=yes_or_no	network_interface=le0 {hostname=feron ip_address=129.222.2.1 netmask=255.255.0.0 protocol_ipv6=no}

Choose only one value for network_interface. Include any combination or none of the hostname, ip_address, and netmask keywords, as needed. If you do not use any of these keywords, omit the curly braces {}.

protocol_ipv6 is optional; you do not need to specify it.

Root password

Keywords	Values
root_password=root_password	Encrypted from /etc/shadow

Language in which to display the install program

Keywords	Values
system_locale=locale	/usr/lib/locale

Terminal type

Keywords	Values
timezone=timezone	/usr/share/lib/zoneinfo/*

Date and time

Keywords	Values
timeserver=localhost, hostname, ip_address	If you specify localhost as the time server, the system's time is assumed to be correct. If you specify the hostname or ip_address (if you are not running a name service) of a system, that system's time is used to set the time.

Keywords - IA Platform

Monitor type

Keywords	Values
monitor=monitor_type	Append kdmconfig -d filename output to sysidcfg file

Keyboard language, keyboard layout

Keywords	Values
keyboard=keyboard_language {layout=value}	Append kdmconfig -d filename output to sysidcfg file

Graphics card, color depth, display resolution, screen size

Keywords	Values
display=graphics_card {size=screen_size depth=color_depth resolution=screen_resolution}	Append kdmconfig -d filename output to sysidcfg file

Printing device, number of buttons, IRQ level

Keywords	Values
pointer=pointing_device {nbuttons=number_buttons irq=value}	Append kdmconfig -d filename output to sysidcfg file

EXAMPLES

---

Example 1 Sample sysidcfg files




The following example is a sysidcfg file for a group of SPARC systems to install over the network. (The host names, IP addresses, and netmask of these systems have been preconfigured by editing the name service.) Because all the system configuration information has been preconfigured, an automated installation can be created by using a custom JumpStart profile.

system_locale=en_US
timezone=US/Central
timeserver=localhost
terminal=sun-cmd
name_service=NIS {domain_name=marquee.central.sun.com
                  name_server=connor(129.152.112.3)}
root_password=m4QPOWNY
system_locale=C

The following example is a sysidcfg file created for a group of IA systems to install over the network that all have the same keyboard, graphics cards, and pointing devices. The device information (keyboard, display, and pointer) was captured from running kdmconfig -d (see kdmconfig(1M)). In this example, users would see only the prompt to select a language (system_locale) for displaying the rest of the Solaris installation program.

keyboard=ATKBD {layout=US-English}
display=ati {size=15-inch}
pointer=MS-S
timezone=US/Central
timeserver=connor
terminal=AT386
name_service=NIS {domain_name=marquee.central.sun.com
                  name_server=connor(129.152.112.3)}
root_password=URFUni9

---

SEE ALSO

install_scripts(1M), kdmconfig(1M), sysidtool(1M)

Solaris 8 Advanced Installation Guide

SunOS 5.8  Last Revised 22 Sep 1999

NAME | DESCRIPTION | EXAMPLES | SEE ALSO