Appendix A. Appendix

Appendix A. Appendix¶

Contents

A.1. Network Connection Types
A.2. The parmfile—Automating the System Configuration
A.3. Using the vt220 Terminal Emulator

A.1. Network Connection Types¶

SUSE® Linux Enterprise Server for IBM System z includes network drivers for OSA devices (token ring, ethernet, and gigabit ethernet) and HiperSockets. This chapter describes the configuration within the SUSE Linux Enterprise Server installation system.

	CTC, ESCON, and IUCV Interfaces No Longer Supported
CTC, ESCON, and IUCV interfaces are no longer officially supported. For compatibility reasons, they are still usable, but with the next release of SUSE Linux Enterprise Server the support of these interfaces will be dropped completely.

A.1.1. Ethernet and Token Ring with the lcs Module¶

Select 1 from the list of network devices (for an OSA network adapter), then 2 for the LCS bus interface, then either 1 for ethernet or 2 for token ring.

Example A.1. Supported Network Connection Types¶

Please select the type of your network device.

1) OSA-2 or OSA Express
2) HiperSockets
3) Channel To Channel (CTC) [unsupported]
4) ESCON [unsupported]
5) Inter-User Communication Vehicle (IUCV) [unsupported]

> 1

Please choose the CCW bus interface.

1) QDIO
2) LCS

> 2

Please choose the physical medium.

1) Ethernet
2) Token Ring

> 1

When prompted, enter the network device read channel number (such as 0.0.fc20), the write channel number (like 0.0.fc21), and the relative port number on this device.

Example A.2. Network Device Driver Parameters¶

+ Device address for read channel> 0.0.fc20
+ 
+ Device address for write channel> 0.0.fc21
+ 
+ Enter the relative port number> 2

Next, choose manual configuration then enter the IP address, netmask, broadcast address, IP address of the gateway, and IP address of the DNS server.

Example A.3. Network Device Name¶

Automatic configuration via DHCP?

1) Yes
2) No

> 2

Enter your IP address> 192.168.0.20

Enter your netmask. For a normal class C network, this is usually
255.255.255.0 [255.255.255.0]> 255.255.255.0

If you need a gateway to reach the server, enter the IP address of the
gateway. If you do not need a gateway, enter your own IP address
[192.168.0.20]> 192.168.0.1

Enter the IP address of your name server. If you do not use a name server, 
just enter "+++" [192.168.0.20]> 192.168.0.2

A.1.2. Gigabit Ethernet with the qeth Module¶

Select 1 from the list of network devices for OSA network adapters, then 1 for the QDIO interface, then 1 for ethernet. When prompted, enter the network device's read, write, and data channel numbers (for example, 0.0.0808, 0.0.0809, and 0.0.080a) and the port name, if applicable. Choose whether to enable OSI Layer 2 support and enter the relative port number.

Example A.4. Network Device Driver Parameters¶

Please select the type of your network device.

1) OSA-2 or OSA Express
2) Hipersockets
--------------------
3) Channel To Channel (CTC)
4) ESCON
5) Inter-User Communication Vehicle (IUCV)

>
1

Please choose the CCW bus interface.

1) QDIO
2) LCS

>
1

Please choose the physical medium.

1) Ethernet
2) Token Ring

>
1

0.0.09a0 1731/01
0.0.09a1 1731/01
0.0.09a2 1731/01
0.0.0808 1731/01
0.0.0809 1731/01
0.0.080a 1731/01


Device address for read channel>
0.0.0808

Device address for write channel>
0.0.0809

Device address for data channel>
0.0.080a

Portname to use> SUSEPORT

Enable OSI Layer 2 support?

1) Yes
2) No

>
2

Enter the relative port number>
0

Next, enter the full hostname. Then choose manual configuration and enter the IP address, netmask, broadcast address, IP address of the gateway, and IP address of the DNS server.

Example A.5. Network Device Name¶

Fully qualified hostname> earth.cosmos.com

Automatic configuration via DHCP?

1) Yes
2) No

> 2

Enter your IP address> 192.168.0.20

Enter your netmask. For a normal class C network, this is usually
255.255.255.0 [255.255.255.0]> 255.255.255.0

If you need a gateway to reach the server, enter the IP address of the
gateway. If you do not need a gateway, enter your own IP address
[192.168.0.20]> 192.168.0.1

Enter the IP address of your name server. If you do not use a name server, 
just enter "+++" [192.168.0.20]> 192.168.0.2

A.2. The parmfile—Automating the System Configuration¶

The installation process can be partly automated by specifying the crucial parameters in the parmfile. The parmfile contains all the data required for network setup and DASD configuration. In addition to that, it can be used to set up the connection method to the SUSE Linux Enterprise Server installation system and the YaST instance running there. User interaction is thus limited to the actual YaST installation controlled by YaST dialogs.

The following parameters can be passed to the installation routine, which takes them as default values for installation. All IP addresses, server names, and numerical values are just examples. Replace these values with the ones needed in your installation scenario.

The number of lines in the parmfile is limited to 10. Specify more than one parameter on a line. Parameter names are not case-sensitive. Separate the parameters by spaces. You may specify the parameters in any order. Always keep the PARAMETER=value string together in one line. For example:

Hostname=s390zvm01.suse.de HostIP=10.11.134.65

	Using IPv6 during the Installation
By default you can only assign IPv4 network addresses to your machine. To enable IPv6 during installation, enter one of the following parameters at the bootprompt: `ipv6=1` (accept IPv4 and IPv6) or `ipv6only=1` (accept IPv6 only).

Some of the following parameters are required. If they are missing, the automatic process pauses and asks you to enter the value manually.

A.2.1. General Parameters¶

AutoYaST=<URL> Manual=0: The AutoYaST parameter specifies the location of the autoinst.xml control file for automatic installation. The Manual parameter controls if the other parameters are only default values that still must be acknowledged by the user. Set this parameter to 0 if all values should be accepted and no questions asked. Setting AutoYaST implies setting Manual to 0.
Info=<URL>: Specifies a location for a file from which to read additional options. This helps to overcome the limitations of 10 lines (and 80 characters per line under z/VM) for the parmfile. More documentation on the Info file can be found in Section “Creating the info File” (Chapter 5, Automated Installation, ↑Installation and Administration). Since the Info file can typically only be accessed through the network on System z, you cannot use it to specify options required to setup the network, i.e. options described in Section A.2.2, “Configuring the Network Interface”. Also other linuxrc specific options such as for debugging have to be specified in the parmfile to be effective.

Creating a File with Autoinstallation Information

	Creating a File with Autoinstallation Information
At the very end of the installation of a system you can check Clone This System for Autoyast. This creates a ready-to-use profile as `/root/autoinst.xml` that can be used to create clones of this particular installation. To create an autoinstallation file from scratch or to edit an existing one, use the YaST module Autoinstallation. For more information about AutoYaST, refer to Chapter Automated Installation (↑Installation and Administration).

At the very end of the installation of a system you can check Clone This System for Autoyast. This creates a ready-to-use profile as /root/autoinst.xml that can be used to create clones of this particular installation. To create an autoinstallation file from scratch or to edit an existing one, use the YaST module Autoinstallation. For more information about AutoYaST, refer to Chapter Automated Installation (↑Installation and Administration).

A.2.2. Configuring the Network Interface¶

	Configuring the Network Interface
The settings discussed in this section apply only to the network interface used during installation. Configure additional network interfaces in the installed system by following the instructions given in Section “Configuring a Network Connection Manually” (Chapter 30, Basic Networking, ↑Installation and Administration).

Hostname=zseries.example.com

Enter the fully qualified hostname.

Domain=example.com

Domain search path for DNS. Allows you to use short host names instead of fully qualified ones.

HostIP=192.168.1.2

Enter the IP address of the interface to configure.

Gateway=192.168.1.3

Specify the gateway to use.

Nameserver=192.168.1.4

Specify the DNS server in charge.

InstNetDev=osa

Enter the type of interface to configure. Possible values are osa, hsi. ctc, escon, and iucv. (CTC, ESCON, and IUCV are no longer officially supported).

For the interfaces of type hsi and osa, specify an appropriate netmask and an optional broadcast address:

Netmask=255.255.255.0
Broadcast=192.168.255.255

For the interfaces of type ctc, escon, and iucv (CTC, ESCON, and IUCV are no longer officially supported), enter the IP address of the peer:

Pointopoint=192.168.55.20

OsaInterface=<lcs|qdio> OsaMedium=<eth|tr>

For osa network devices, specify the host interface (qdio or lcs) and the physical medium (eth for ethernet or tr for token ring).

Layer2=<0|1>

For osa QDIO ethernet devices, specify whether to enable OSI Layer 2 support.

OSAHWAddr=02:00:65:00:01:09

For Layer 2-enabled osa QDIO ethernet devices, specify the manual MAC address. Note that this is distinct from HWAddr, which contains the default MAC address as detected by linuxrc.

PortNo=<0|1>

For osa network devices, specify the port number (provided the device supports this feature). The default value is 0.

Each of the interfaces requires certain setup options:

Interfaces ctc and escon (CTC and ESCON are no longer officially supported):
```
ReadChannel=0.0.0424
WriteChannel=0.0.0425
```
ReadChannel specifies the READ channel to use. WriteChannel specifies the WRITE channel.

For the ctc interface (no longer officially supported), specify the protocol that should be used for this interface:

CTCProtocol=<0/1/2>

Valid entries would be:

`0`	Compatibility mode, also for non-Linux peers other than OS/390 and z/OS (this is the default mode)
`1`	Extended mode
`2`	Compatibility mode with OS/390 and z/OS

Network device type osa with interface lcs:
```
ReadChannel=0.0.0124
Portname=1
```
ReadChannel stands for the channel number used in this setup. A second port number can be derived from this by adding one to ReadChannel. Portnumber is used to specify the relative port.
Interface iucv:
```
IUCVPeer=PARTNER
```
Enter the name of the peer machine.
Network device type osa with interface qdio for OSA-Express Gigabit Ethernet and OSA-Express High-speed Token Ring:
```
ReadChannel=0.0.0524
WriteChannel=0.0.0525
DataChannel=0.0.0526
Portname=FEF400
```
For ReadChannel, enter the number of the READ channel. For WriteChannel, enter the number of the WRITE channel. DataChannel specifies the DATA channel. For Portname, enter an appropriate port name. Make sure that the READ channel carries an even device number.
Interface hsi for HiperSockets and VM guest LANs:
```
ReadChannel=0.0.0624
WriteChannel=0.0.0625
DataChannel=0.0.0626
```
For ReadChannel, enter the appropriate number for the READ channel. For WriteChannel and DataChannel, enter the WRITE and DATA channel numbers.

A.2.3. Specifying the Installation Source and YaST Interface¶

Install=nfs://server/directory/DVD1/

Specify the location of the installation source to use. Possible protocols are nfs, smb (Samba/CIFS), ftp, and http.

If an ftp or smb URL is given, specify the username and password with the URL. These parameters are optional and anonymous or guest login is assumed if they are not given.

Install=ftp://user:password@server/directory/DVD1/

In case of a Samba or CIFS installation, you can also specify the domain that should be used:

Install=smb://workdomain;user:password@server/directory/DVD1/

UseSSH=1 UseVNC=1 Display_IP=192.168.42.42

Depending on which parameter you give, a remote X server, SSH, or VNC will be used for installation. UseSSH enables SSH installation, UseVNC starts a VNC server on the installing machine, and Display_IP causes the installing system to try to connect to an X server at the given address. Only one of these parameters should be set at any time.

	X Authentication Mechanism
The direct installation with the X Window System relies on a primitive authentication mechanism based on hostnames. This mechanism is disabled on current SUSE Linux Enterprise Server versions. Installation with SSH or VNC is preferred.

To allow a connection between YaST and the remote X server, run xhost <IP address> with the address of the installing machine on the remote machine.

For VNC, specify a password of six to eight characters to use for installation:

VNCPassword=<a password>

For SSH, specify a password of six to eight characters to use for installation:

SSHPassword=<a password>

A.2.4. Example Parmfiles¶

For an automatic installation with AutoYaST in an LPAR, it is preferable that the parmfile has just one long line. If multiple lines are desired for readability, use blank characters at the beginning and end of each line. The maximum number of lines in a parmfile is 10.

To receive potential error messages on the console, use

linuxrcstderr=/dev/console

Example A.6. Parmfile for Installation with NFS, VNC, and IUCV and AutoYaST with HTTP¶

ramdisk_size=131072 root=/dev/ram1 ro init=/linuxrc TERM=dumb 
instnetdev=iucv iucvpeer=ROUTER01 pointopoint=192.168.0.1 
hostip=192.168.0.2 
nameserver=192.168.0.3
 install=nfs://192.168.0.4/SLES/SLES-10-s390x/DVD1
autoyast=http://192.168.0.5/autoinst.xml 
 linuxrcstderr=/dev/console usevnc=1
vncpassword=testin

Example A.7. Parmfile for Installation with NFS, SSH, and HSI and AutoYaST with NFS¶

ramdisk_size=131072 root=/dev/ram1 ro init=/linuxrc TERM=dumb
AutoYast=nfs://192.168.1.1/autoinst/s390.xml
Hostname=zseries.example.com HostIP=192.168.1.2
Gateway=192.168.1.3 Nameserver=192.168.1.4
InstNetDev=hsi layer2=0
Netmask=255.255.255.128 Broadcast=192.168.1.255
readchannel=0.0.702c writechannel=0.0.702d datachannel=0.0.702e
 install=nfs://192.168.1.5/SLES-10-s390x/DVD1/
 UseSSH=1 SSHPassword=testing linuxrcstderr=/dev/console

A.3. Using the vt220 Terminal Emulator¶

Recent MicroCode Levels allow the use of an integrated vt220 terminal emulator in addition to the standard line mode terminal. The vt220 terminal is connected to /dev/ttyS1. The line mode terminal is connected to /dev/ttyS0. If the vt220 emulation is available, an icon for an integrated vt220 ASCII console appears next to the icon for the 3215 console on the HMC/SE.

To activate vt220 support on your machine, edit /etc/inittab as user root. Look for the following line and delete the leading # sign:

#2:2345:respawn:/sbin/mingetty --noclear /dev/ttyS1 xterm

Save the file and run telinit q to pass the changes in /etc/inittab to init. The vt220 terminal should then be ready to use. If not, try hitting Enter at the terminal until the login prompt appears.

Make sure that you do not apply the changes as described above to a system that does not support vt220 terminal emulators. Otherwise, login might become impossible on this system and you will be shown the following message:

INIT respawning too fast, disabled for 5 minutes.

To redirect the kernel messages at boot time from the system console to the vt220 terminal, add the following entries to the parameters line in /etc/zipl.conf:

console=ttyS0 console=ttyS1

The resulting parameters line would look like the following example:

parameters = "root=/dev/dasda2 TERM=dumb console=ttyS0 console=ttyS1"

Save the changes in /etc/zipl.conf, run zipl, and reboot the system.