Follow Techotopia on Twitter

On-line Guides
All Guides
eBook Store
iOS / Android
Linux for Beginners
Office Productivity
Linux Installation
Linux Security
Linux Utilities
Linux Virtualization
Linux Kernel
System/Network Admin
Scripting Languages
Development Tools
Web Development
GUI Toolkits/Desktop
Mail Systems
Eclipse Documentation

How To Guides
General System Admin
Linux Security
Linux Filesystems
Web Servers
Graphics & Desktop
PC Hardware
Problem Solutions




Red Hat Enterprise Linux 6 Essentials eBook now available in PDF and ePub formats for only $9.99
RHEL 6 Essentials contains 40 chapters and over 250 pages.

26.3. Installation network parameters

The following parameters can be used to set up the preliminary network automatically and can be defined in either the parameter file or the CMS configuration file. The parameters in this section are the only parameters that can also be used in a CMS configuration file. All other parameters in other sections must be specified in the parameter file.
Where type must be one of the following: qeth, lcs, or ctc. The default is qeth.
Choose lcs for:
  • OSA-2 Ethernet/Token Ring
  • OSA-Express Fast Ethernet in non-QDIO mode
  • OSA-Express High Speed Token Ring in non-QDIO mode
  • Gigabit Ethernet in non-QDIO mode
Choose qeth for:
  • OSA-Express Fast Ethernet
  • Gigabit Ethernet (including 1000Base-T)
  • High Speed Token Ring
  • HiperSockets
  • ATM (running Ethernet LAN emulation)
Where bus_IDs is a comma-separated list of two or three device bus IDs.
Provides required device bus IDs for the various network interfaces:
qeth: SUBCHANNELS="read_device_bus_id,write_device_bus_id,data_device_bus_id"
lcs or ctc: SUBCHANNELS="read_device_bus_id,write_device_bus_id"
For example (a sample qeth SUBCHANNEL statement):
PORTNAME=osa_portname , PORTNAME=lcs_portnumber
This variable supports OSA devices operating in qdio mode or in non-qdio mode.
When using qdio mode (NETTYPE=qeth), osa_portname is the portname specified on the OSA device when operating in qeth mode.
When using non-qdio mode (NETTYPE=lcs), lcs_portnumber is used to pass the relative port number as a decimal integer in the range of 0 through 15.
You can add either PORTNO=0 (to use port 0) or PORTNO=1 (to use port 1 of OSA features with two ports per CHPID) to the CMS configuration file to avoid being prompted for the mode.
Where value can be 0 or 1.
Use LAYER2=0 to operate an OSA or HiperSockets device in layer 3 mode (NETTYPE=qeth). Use LAYER2=1 for layer 2 mode. For virtual network devices under z/VM this setting must match the definition of the GuestLAN or VSWITCH to which the device is coupled.
To use network services that operate on layer 2 (the Data Link Layer or its MAC sublayer) such as DHCP, layer 2 mode is a good choice.
The qeth device driver default for OSA devices is now layer 2 mode. To continue using the previous default of layer 3 mode, set LAYER2=0 explicitly.
Where value can be 0 or 1.
Specify VSWITCH=1 when connecting to a z/VM VSWITCH or GuestLAN, or VSWITCH=0 (or nothing at all) when using directly attached real OSA or directly attached real HiperSockets.
When you specify LAYER2=1 and VSWITCH=0, optionally use this parameter to specify the MAC address. Linux needs six colon-separated octets and lower case hex digits. Note that this is different from the z/VM notation, so be careful if you copy and paste information from z/VM.
If you specify LAYER2=1 and VSWITCH=1, you must not specify the MACADDR, because z/VM assigns a unique MAC address to virtual network devices in layer 2 mode.
Where value can be 0, 1, or 3.
Specifies the CTC protocol for NETTYPE=ctc. The default is 0.
Where string is the hostname of the newly-installed Linux instance.
Where IP is the IP address of the new Linux instance.
Where netmask is the netmask.
The netmask supports the syntax of a prefix integer (from 1 to 32) as specified in IPv4 classless interdomain routing (CIDR). For example, you can specify 24 instead of, or 20 instead of
Where gw is the gateway IP address for this network device.
Where mtu is the Maximum Transmission Unit (MTU) for this network device.
Where server1:server2:additional_server_terms:serverN is a list of DNS servers, separated by colons. For example:
Where domain1:domain2:additional_dns_terms:domainN is a list of the search domains, separated by colons. For example:
You only need to specify SEARCHDNS= if you specify the DNS= parameter.
Defines the DASD or range of DASDs to configure for the installation. For a detailed description of the syntax, refer to the dasd_mod device driver module option described in the chapter on the DASD device driver in Linux on System z Device Drivers, Features, and Commands on Red Hat Enterprise Linux 6.
Linuxrc supports a comma-separated list of device bus IDs or of ranges of device bus IDs with the optional attributes ro, diag, erplog, and failfast. Optionally, you can abbreviate device bus IDs to device numbers with leading zeros stripped. Any optional attributes should be separated by colons and enclosed in parentheses. Optional attributes follow a device bus ID or a range of device bus IDs.
The only supported global option is autodetect. This does not support the specification of non-existent DASDs to reserve kernel device names for later addition of DASDs. Use persistent DASD device names (for example /dev/disk/by-path/...) to enable transparent addition of disks later. Other global options such as probeonly, nopav, or nofcx are not supported by linuxrc.
Only specify those DASDs that you really need to install your system. All unformatted DASDs specified here must be formatted after a confirmation later on in the installer (refer to Section, “DASD low-level formatting”). Add any data DASDs that are not needed for the root file system or the /boot partition after installation as described in Section, “DASDs that are not part of the root file system”.
For FCP-only environments, specify DASD=none. Should linuxrc show an error message and ask to correct the parameter, select continue. It is safe to disregard this error message. When installing with kickstart and RUNKS=1, linuxrc will simply continue without asking to correct the parameter.
For example:
FCP_n="device_bus_ID WWPN FCP_LUN"
  • n is typically an integer value (for example FCP_1 or FCP_2) but could be any string with alphabetic or numeric characters or underscores.
  • device_bus_ID specifies the device bus ID of the FCP device representing the host bus adapter (HBA) (for example 0.0.fc00 for device fc00).
  • WWPN is the world wide port name used for routing (often in conjunction with multipathing) and is as a 16-digit hex value (for example 0x50050763050b073d).
  • FCP_LUN refers to the storage logical unit identifier and is specified as a 16-digit hexadecimal value padded with zeroes to the right (for example 0x4020400100000000).
These variables can be used on systems with FCP devices to activate FCP LUNs such as SCSI disks. Additional FCP LUNs can be activated during the installation interactively or by means of a kickstart file. There is no interactive question for FCP in linuxrc. An example value may look similar to the following:
FCP_1="0.0.fc00 0x50050763050b073d 0x4020400100000000"

Important — values are site-specific

Each of the values used in the FCP parameters (for example FCP_1 or FCP_2) are site-specific and are normally supplied by the FCP storage administrator.
The installation program prompts you for any required parameters not specified in the parameter or configuration file except for FCP_n.

  Published under the terms of the Creative Commons License Design by Interspire