Hi, I did not yet worked with zACI,
but the setup and configuration of HiperSockets in Ubuntu is quite straight
forward:
Just check for configured devices:
znetconf -c | grep HiperSockets
or better check for unconfigured devices for this example:
znetconf -u | grep HiperSockets
And configure a new HiperSocket device (taken from the list with the
unconfigured):
sudo znetconf -a d200
Scanning for network devices...
Successfully configured device 0.0.d200 (encd200)
You should now see it as configured here:
znetconf -c | grep HiperSockets
0.0.d200,0.0.d201,0.0.d202 1731/05 HiperSockets D2 qeth encd200
online
(a udev rule was automatically created - for persistence)
The 'device' was automatically named based on the first address of the
triple: encd200
as shown above or verified here:
cat /sys/devices/qeth/0.0.d200/if_name
encd200
You can now configure the HiperSocket device like other qeth devices:
sudo ip addr add 192.0.1.2 dev encd200
and/or using: /etc/network/interfaces
Bring the link up afterwards:
sudo ip link set encd200 up
And verify if everything is fine:
ip addr show d200
lsqeth
In case you don't like the default device name (what I can fully
understand),
you can rename it (for example to hsi0) with the help of a udev rule like
this:
cat /etc/udev/rules.d/70-network-d200-to-hsi0.rules
# rename s390x qeth device 0.0.d200 to HiperSocket device hsi0
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="qeth", KERNELS=="0.0.d200",
ATTR{type}=="1", KERNEL=="hsi*", NAME="hsi0"
So from an Ubuntu point of view the HiperSockets can be handled as usual ...
Bye, Frank
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
