Project:Infrastructure/Developer Machines/s390

s390 Admin Notes
These are various notes mainly targeted at people administrating Gentoo dev machines, although most things are probably generally useful. These are not general "how do I administrate a Gentoo box" notes.

Hostnames
These are the current systems we have available

Console Access
In order to access the s390 console, install the terminal emulator. This provides multiple UIs for connecting to a remote system. Use whichever version you prefer. We'll focus on two here:
 * x3270: Graphical X interface
 * c3270: Console ncurses interface


 * 1) Use the   command to connect to the console server (see hostnames above).
 * 2) The USERID field should be selected by default -- enter the account name for the host (see hostnames above).
 * 3) If the USERID is fully filled, the cursor moves automatically to the password, otherwise hit tab to move to the field.
 * 4) Type in the password.  Note: while the cursor will move, nothing will be displayed -- no actual characters or the common * marker.

Note: When you are done, do not use  as that kills the VM. Only use.

Common CP/CMS Commands
See the S390/z/VM tips and tricks page for details.

Kernel Management
s390 systems use the zipl tool from the package to manage booting of kernels. Things to remember:


 * Make updates to.
 * Run  whenever zipl.conf is changed or kernels referred to by the config file are updated (failure to do so will break booting).
 * The bootable linux kernel is created at (e.g. under ).
 * The  shortcut usually does not do the right thing under s390.

Storage
You cannot format the "full" device as a filesystem. e.g.  will fail. The s390 VM system requires the header of the device have some metadata so the hypervisor can process things correctly.

Make sure you run  on the device before you do anything else. This creates the proper metadata structure.

Do not use  to try and format block devices. Use  instead. You can use standard mkfs tools on the partitions after that.

/etc/zipl.conf
[defaultboot] defaultmenu = menu

[Gentoo] image = /boot/image target = /boot/zipl parameters = "no_removal_warning dasd=0150,0151,0160,0191,0200 root=/dev/dasdb1 rootfstype=ext4 panic=3 TERM=dumb init=/bin/busybox setarch linux32 /ginit"

[Gentoo_OK] image = /boot/image.ok   target = /boot/zipl parameters = "no_removal_warning dasd=0150,0151,0160,0191,0200 root=/dev/dasdb1 rootfstype=ext4 panic=3 TERM=dumb init=/ginit"

[Rescue] image = /boot/image.ok   target = /boot/zipl parameters = "no_removal_warning dasd=0150,0151,0160,0191,0200 root=/dev/dasdb1 rootfstype=ext4 panic=3 TERM=dumb init=/bin/bb rw"


 * menu

default = 1 prompt = 1 target = /boot/zipl timeout = 10 1 = Gentoo 2 = Gentoo_OK 3 = Rescue

/etc/conf.d/net
config_eth0="148.100.88.31/24 2620:91:0:688:1::31/64" routes_eth0="default via 148.100.88.1" ccwgroup_eth0="0.0.0340 0.0.0341 0.0.0342" ccwgroup_opts_eth0="layer2=1" #fake_ll=0

Manual Network Bringup
If the network device fails to come up properly, you can online it manually.


 * Load the kernels modules for ethernet.


 * Bind the hardware ports to the ethernet driver -- the x.y.zzzz numbers will depend on your system.


 * Initialize the ethernet settings.


 * Bring up the network directly -- obviously the network settings here depend on your box.