12:21 p.m.
Hi all,
while I was trying to get all different kinds of network device types of
s390x working (bug reports in bugzilla pending), I got it working nicely
with the traditional network service, which is what users would
typically use in a data center.
NetworkManager requires the activation (chkconfig) of the services
messagebus, haldaemon. Then NM works with static IP settings through
nm-system-settings, which is what we need in
linuxrc.s390/loader/anaconda, and seems to detect at least qeth and lcs
devices (it doesn't touch ctc and netiucv). Tested with
NetworkManager-0.7.1-4.git20090414.fc11.1.s390x.
Support for the s390 bus types ccw, ccwgroup, and iucv (which is
sufficient for all network types as well as dasd, zfcp, and tape) has
been in HAL since 2005
[http://lists.freedesktop.org/archives/hal/2005-June/002628.html,
http://cgit.freedesktop.org/hal/commit/?id=2ed3c042c13f741b8a2166e4551d9d...].
Only when NM changes to udev for device sensing there might need to be
new support for s390. See the attachment for an example output of lshal
of a z/VM 5.3 guest on a z10 with 12 different types of network devices
as well as dasd and zfcp.
If lo and eth0 (a real OSA NIC) are the only network devices defined by
means of ifcfg file in /etc/sysconfig/network-scripts/ and they have
been brought up by the network service on boot, I can startup NM and
eth0 keeps working. This is what I see in syslog-ng:
Jun 21 19:12:44 h4245010 NetworkManager: <info> starting...
Jun 21 19:12:44 h4245010 NetworkManager: <WARN> nm_generic_enable_loopback():
error -17 returned from rtnl_addr_add(): Sucess
Jun 21 19:12:44 h4245010 NetworkManager: <info> (eth0): new Ethernet device
(driver: 'qeth')
Jun 21 19:12:44 h4245010 NetworkManager: <info> (eth0): exported as
/org/freedesktop/Hal/devices/net_02_00_00_eb_a5_4b
Jun 21 19:12:44 h4245010 NetworkManager: <info> Trying to start the supplicant...
Jun 21 19:12:44 h4245010 NetworkManager: <info> Trying to start the system
settings daemon...
Jun 21 19:12:44 h4245010 NetworkManager: <info> (eth0): carrier now ON (device
state 1)
Jun 21 19:12:44 h4245010 nm-system-settings: Loaded plugin ifcfg-rh: (c) 2007 - 2008 Red
Hat, Inc. To report bugs please use the NetworkManager mailing list.
Jun 21 19:12:44 h4245010 nm-system-settings: ifcfg-rh: parsing
/etc/sysconfig/network-scripts/ifcfg-eth0 ...
Jun 21 19:12:44 h4245010 nm-system-settings: ifcfg-rh: read connection 'System
eth0'
Jun 21 19:12:44 h4245010 nm-system-settings: ifcfg-rh: parsing
/etc/sysconfig/network-scripts/ifcfg-lo ...
Jun 21 19:12:48 h4245010 NetworkManager: <info> (eth0): device state change: 1
-> 2
Jun 21 19:12:48 h4245010 NetworkManager: <info> (eth0): preparing device.
Jun 21 19:12:48 h4245010 NetworkManager: <info> (eth0): deactivating device
(reason: 2).
Jun 21 19:12:48 h4245010 NetworkManager: <WARN> check_one_route(): (eth0) error
-34 returned from rtnl_route_del(): Sucess
Jun 21 19:12:48 h4245010 NetworkManager: <info> (eth0): device state change: 2
-> 3
Jun 21 19:12:48 h4245010 NetworkManager: <info> Activation (eth0) starting
connection 'System eth0'
Jun 21 19:12:48 h4245010 NetworkManager: <info> (eth0): device state change: 3
-> 4
Jun 21 19:12:48 h4245010 NetworkManager: <info> Activation (eth0) Stage 1 of 5
(Device Prepare) scheduled...
Jun 21 19:12:48 h4245010 NetworkManager: <info> Activation (eth0) Stage 1 of 5
(Device Prepare) started...
Jun 21 19:12:48 h4245010 NetworkManager: <info> Activation (eth0) Stage 2 of 5
(Device Configure) scheduled...
Jun 21 19:12:48 h4245010 NetworkManager: <info> Activation (eth0) Stage 1 of 5
(Device Prepare) complete.
Jun 21 19:12:48 h4245010 NetworkManager: <info> Activation (eth0) Stage 2 of 5
(Device Configure) starting...
Jun 21 19:12:48 h4245010 NetworkManager: <info> (eth0): device state change: 4
-> 5
Jun 21 19:12:48 h4245010 NetworkManager: <info> Activation (eth0) Stage 2 of 5
(Device Configure) successful.
Jun 21 19:12:48 h4245010 NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP
Configure Start) scheduled.
Jun 21 19:12:48 h4245010 NetworkManager: <info> Activation (eth0) Stage 2 of 5
(Device Configure) complete.
Jun 21 19:12:48 h4245010 NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP
Configure Start) started...
Jun 21 19:12:48 h4245010 NetworkManager: <info> (eth0): device state change: 5
-> 7
Jun 21 19:12:48 h4245010 NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP
Configure Get) scheduled...
Jun 21 19:12:48 h4245010 NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP
Configure Start) complete.
Jun 21 19:12:48 h4245010 NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP
Configure Get) started...
Jun 21 19:12:48 h4245010 NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP
Configure Commit) scheduled...
Jun 21 19:12:48 h4245010 NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP
Configure Get) complete.
Jun 21 19:12:48 h4245010 NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP
Configure Commit) started...
Jun 21 19:12:49 h4245010 NetworkManager: <info> (eth0): device state change: 7
-> 8
Jun 21 19:12:49 h4245010 NetworkManager: <info> Policy set 'System eth0'
(eth0) as default for routing and DNS.
Jun 21 19:12:49 h4245010 NetworkManager: <info> Activation (eth0) successful,
device activated.
Jun 21 19:12:49 h4245010 NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP
Configure Commit) complete.
# nm-tool
NetworkManager Tool
State: connected
** (process:2189): WARNING **: error: failed to read connections from
org.freedesktop.NetworkManagerUserSettings:
The name org.freedesktop.NetworkManagerUserSettings was not provided by any .service
files
- Device: eth0 [System eth0] --------------------------------------------------
Type: Wired
Driver: qeth
State: connected
Default: yes
HW Address: 02:00:00:EB:A5:4B
Capabilities:
Carrier Detect: yes
Speed: 1000 Mb/s
Wired Properties
Carrier: on
IPv4 Settings:
Address: X.Y.108.140
Prefix: 22 (255.255.252.0)
Gateway: X.Y.108.1
DNS: X.Y.120.241
DNS: X.Y.64.172
Also the output of nm-tool looks promising. If I start "anaconda -t -T",
I find the following in /tmp/anacdump.txt after it bails out on sensing
DASDs:
id.network: Network instance, containing members:
id.network.netdevices: {'eth0': DEVICE=eth0
BOOTPROTO=none
DNS1=X.Y.120.241
DNS2=X.Y.64.172
HWADDR=02:00:00:EB:A5:4B
IPADDR=X.Y.108.140
NETMASK=255.255.252.0
NETTYPE=qeth
ONBOOT=yes
SUBCHANNELS=0.0.f5f0,0.0.f5f1,0.0.f5f2
USERCTL=no
}
id.network.ksdevice: None
id.network.overrideDHCPhostname: False
id.network.hostname: XYZ.boeblingen.de.ibm.com
id.network.domains: [boeblingen.de.ibm.com ibm.com]
This seems to be very good with regard to network so far.
Steffen
Linux on System z Development
IBM Deutschland Research & Development GmbH
Vorsitzender des Aufsichtsrats: Martin Jetter
Geschäftsführung: Erich Baier
Sitz der Gesellschaft: Böblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294