Novell LINUX ENTERPRISE SERVER 11 - DEPLOYMENT Deployment Manual page 72

common "layer 3" mode. The card mode affects all systems that share the device includ-
ing systems on other LPARs. If in doubt, please specify 2 for compatibility with the
default mode used by other operating systems such as z/VM and z/OS. Consult with
your hardware administrator for further information on these options.
z/VM Installation
After the kernel has completed its start-up routines, answer a few questions regarding
the network setup. First, select the type of network connection to use: OSA Express or
HiperSockets. In this example installation, OSA Express is used.
The system now displays a possible OSA configuration. Choose first whether to use
QDIO or LCS OSA. Next, choose the physical medium to use and enter the device ad-
dresses. If you prefer another setup, enter the device address of the OSA read channel
(0.0.0700 in this example) then the one of the OSA write channel (0.0.0701) and the
OSA control channel (0.0.0702). After entering the channels, insert the name of the
port to which the OSA card is connected.
SUSE Linux Enterprise Server now tries to load the network module by building a pa-
rameter line with the information provided then displays all loaded modules. Loading
was successful if you get an output like:
Example 4.9 Network Device Driver Parameters
qeth: Device 0.0.0700/0.0.0701/0.0.0702 is a Guest LAN QDIO card (level: V448)
with link type GuestLAN QDIO (portname: VSW1)
qeth: Hardware IP fragmentation not supported on eth0
qeth: VLAN enabled
qeth: Multicast enabled
qeth: IPV6 enabled
qeth: Broadcast enabled
qeth: Could not set up broadcast echo filtering on eth0: 0x2
qeth: Using SW checksumming on eth0.
qeth: Outbound TSO not supported on eth0
Next, enter your IP address, netmask, and default gateway. To install over iucv or ctc,
enter additional information, like the the peer address (for a point-to-point adapter) or
the port name.
Finally, the IP address of the DNS server and the MTU size are requested. The MTU
size should always match the one used by the network to which to connect.
60 Deployment Guide