Red Hat ENTERPRISE LINUX 5 - VIRTUAL SERVER ADMINISTRATION, Installation Manual

Page: 200 / 388

Chapter 16. Steps to Get You Started
182
CMSDASD is the device ID of the CMS formatted DASD which contains the configuration file.
CMSDASD is often the 'A' DASD (usually disk 191) of the z/VM guest account. The name of the
configuration file must be set with CMSCONFFILE and needs to be all lowercase.
The syntax of the CMSCONFFILE is bash style with
variable="value"
pairs, one on each line.
Example
redhat.parm
file:
root=/dev/ram0 ro ip=off ramdisk_size=40000
CMSDASD=191 CMSCONFFILE=redhat.conf
vnc
Example
redhat.exec
file:
/* */
'cl rdr'
'purge rdr all'
'spool punch * rdr'
'PUNCH KERNEL IMG A (NOH'
'PUNCH REDHAT PARM A (NOH'
'PUNCH INITRD IMG A (NOH'
'ch rdr all keep nohold'
'i 00c'
Example
redhat.conf
file:
HOSTNAME="foobar.systemz.example.com"
DASD="200­203"
NETTYPE="qeth"
IPADDR="192.168.17.115"
SUBCHANNELS="0.0.0600,0.0.0601,0.0.0602"
PORTNAME="FOOBAR"
NETWORK="192.168.17.0"
NETMASK="255.255.255.0"
BROADCAST="192.168.17.255"
SEARCHDNS="example.com:systemz.example.com"
GATEWAY="192.168.17.254"
DNS="192.168.17.1"
MTU="4096"
The following parameters are required and must be included in the parameter file:
•
DASD= dasd-list
Where
dasd-list
represents the list of DASD devices to be used by Red Hat Enterprise Linux.
Although autoprobing for DASDs is done if this parameter is omitted, it is highly recommended to
include the
DASD=
parameter, as the device numbers (and therefore the device names) can vary
when a new DASD is added to the Red Hat Enterprise Linux guest. This can result in an unusable
system.
Additionally, in SAN-based environments, autoprobing in an LPAR-based install may have
unintended side effects, as the number of DASD and SCSI volumes visible may be unexpectedly
large and include volumes currently in use by other users. In particular, autoprobing during
a kickstart install (which may have enabled autopartitioning to clear all partitions) is highly
discouraged.