21.3. Installation Network Parameters
- Where type must be one of the following:
ctc. The default is
- 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
- OSA-Express Fast Ethernet
- Gigabit Ethernet (including 1000Base-T)
- High Speed Token Ring
- ATM (running Ethernet LAN emulation)
- Where device_bus_IDs is a comma-separated list of two or three device bus IDs. The IDs must be specified in lowercase.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):
- 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
LAYER2="0"to operate an OSA or HiperSockets device in layer 3 mode (
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
- Where value can be
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.
- If you specify
VSWITCH="0", you can optionally use this parameter to specify a MAC address. Linux requires six colon-separated octets as pairs lower case hex digits - for example,
MACADDR=62:a3:18:e7:bc:5f. Note that this is different from the notation used by z/VM.If you specify
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
3.Specifies the CTC protocol for
NETTYPE="ctc". The default is
- Where string is the host name 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
- 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:
SEARCHDNS="subdomain.domain:domain"You only need to specify
SEARCHDNS=if you specify the
- Defines the DASD or range of DASDs to configure for the installation.The installation program supports a comma-separated list of device bus IDs or of ranges of device bus IDs with the optional attributes
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
nofcxare not supported by the installation program.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 installation program (see Section 22.214.171.124, “DASD Low-level Formatting”). Add any data DASDs that are not needed for the root file system or the
/bootpartition after installation as described in Section 126.96.36.199, “DASDs That Are Not Part of the Root File System”.For example:
DASD="eb1c,0.0.a000-0.0.a003,eb10-eb14(diag),0.0.ab1c(ro:diag)"For FCP-only environments, remove the
DASD=option from the CMS configuration file to indicate no DASD is present.
FCP_n="device_bus_ID WWPN FCP_LUN"
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. An example value looks similar to the following:
- n is typically an integer value (for example
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.fc00for 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
- 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
FCP_1="0.0.fc00 0x50050763050b073d 0x4020400100000000"
ImportantEach of the values used in the FCP parameters (for example
FCP_2) are site-specific and are normally supplied by the FCP storage administrator.