How can I add another CTC

[Bernie VK2KAD]

I am trying to work out how to define another CTC to Fedora.   I added a
second CTCA in my Herc config file at address 610/611,

I was hoping Fedora would autodetect the new CTC - not so.   So then I added
a definition in /etc/sysconfig/network-scripts for CTC2 - this I did by
copying CTC1 and making the changes I wanted.   I saw this in dmesg - not
sure what is happening here.

ctcm: CTCM driver initialized
ctc0 (ctcm): not using net_device_ops yet
net ctc0: setup OK : r/w = ch-0.0.0600/ch-0.0.0601, protocol : 0
udev: starting version 139
udev: renamed network interface ctc0 to ctc1

My aim is to have one CTC pointing to my loopback device for local IP access
and the other CTC configured to talk to my NIC so I can get to the out-side
world.

Rgds   Bern

[Steffen Maier]

On 08/04/2009 05:55 AM, Bernie VK2KAD wrote:
> I am trying to work out how to define another CTC to Fedora.   I added a
> second CTCA in my Herc config file at address 610/611,
>
> I was hoping Fedora would autodetect the new CTC - not so.   So then I added
> a definition in /etc/sysconfig/network-scripts for CTC2 - this I did by
> copying CTC1 and making the changes I wanted.   I saw this in dmesg - not
> sure what is happening here.
>
> ctcm: CTCM driver initialized
> ctc0 (ctcm): not using net_device_ops yet
> net ctc0: setup OK : r/w = ch-0.0.0600/ch-0.0.0601, protocol : 0

This is due to the manual hack in /etc/rc.d/rc.sysinit for configuring
the network hardware. In fact ignoring SUBCHANNELS and other
s390-specific lines in ifcfg-ctc1.
> udev: starting version 139
> udev: renamed network interface ctc0 to ctc1

This is because of /etc/udev/rules.d/70-persistent-net.rules which is
fine and you don't have to do anything there.
> My aim is to have one CTC pointing to my loopback device for local IP access
> and the other CTC configured to talk to my NIC so I can get to the out-side
> world.

Phil did a great job in assembling a F11 tar-ball (or disk image) with
the goal to make it automatically work self-contained under the emulator
and thus used a few little hacks to get around some open issues.

For using the default distro mechanisms to configure devices, there are
still some open issues, the fixes of which are not yet upstream.

Please apply the fixes described in the following bugzillas:
https://bugzilla.redhat.com/show_bug.cgi?id=507211
https://bugzilla.redhat.com/show_bug.cgi?id=507214

Please remove the following lines from /etc/rc.d/rc.sysinit:
modprobe ctcm
echo "0.0.0600,0.0.0601" > /sys/bus/ccwgroup/drivers/ctcm/group
echo 1 > /sys/bus/ccwgroup/drivers/ctcm/0.0.0600/online
((Should my suggestions not work for you, you may continue with the
hacks and instead add the following two lines here:
echo "0.0.0610,0.0.0611" > /sys/bus/ccwgroup/drivers/ctcm/group
echo 1 > /sys/bus/ccwgroup/drivers/ctcm/0.0.0610/online
))

There is one more hack in /etc/rc.local:
route add default ctc1
This would usually be in /etc/sysconfig/network as:
GATEWAYDEV=ctc1
GATEWAY=192.168.200.4

Just to be sure, use the traditional network service instead of
NetworkManager, which cannot manage multiple network devices at the same
time (think this is already the case; the udev trigger is for
configuring the hardware of your ctc2 without reIPLing):
/sbin/chkconfig NetworkManager off
/sbin/chkconfig network on
/sbin/service NetworkManager stop
/sbin/udevadm trigger
/sbin/service network start

Now the default ifcfg files should work including your new ifcfg-ctc2.

HTH
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