On 04.09.2015 22:49, Martha McConaghy wrote:
I'm working on a project that requires RHEL 7 running in an LPAR. I've never
done Linux in an LPAR, always on top of z/VM, so its a new experience...ugh..
We've got it running finally and need to configure a 2nd network connection.
The OSA that is available for use is on port 1 of the OSA card. Under z/VM,
that would not be an issue as you add "p1" to the address when defining the
vswitch, etc. However, I can't tell how to tell Linux that the device is on
port 1. To make matters more complicated, the other port is already being
used by this system for its main connection. So, basically, I need to use
both port 0 and 1 on the OSA for different network connections.
I've been looking at znetconf, but it doesn't seen to see any port
distinctions and only sees the device addresses. Can someone point me in the
right direction?
Martha
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] 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/
Haven't ever run zLinux in LPAR, I think it's about as fun as running it under
z/VM but only device
dedications in its directory..
I think you need to use two separate rdev triplets of the same OSA channel for
the two network
interfaces. Something like this:
# vmcp att 203-208 '*'
# cio_ignore -r 203-208
# znetconf -u
Scanning for network devices...
Device IDs Type Card Type CHPID Drv.
------------------------------------------------------------
0.0.0203,0.0.0204,0.0.0205 1731/01 OSA (QDIO) b0 qeth
0.0.0206,0.0.0207,0.0.0208 1731/01 OSA (QDIO) b0 qeth
# znetconf -a 0.0.0203 -o layer2=1 -o portno=0
Scanning for network devices...
Successfully configured device 0.0.0203 (eth1)
# znetconf -a 0.0.0206 -o layer2=1 -o portno=1
Scanning for network devices...
Successfully configured device 0.0.0206 (eth2)
# cat /sys/bus/ccwgroup/drivers/qeth/0.0.0203/portno
0
# cat /sys/bus/ccwgroup/drivers/qeth/0.0.0206/portno
1
znetconf creates the udev rules:
# S/390 qeth device at 0.0.0203
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="qeth", KERNELS=="0.0.0203",
ATTR{type}=="1",
KERNEL=="eth*", NAME="eth1"
# S/390 qeth device at 0.0.0206
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="qeth", KERNELS=="0.0.0206",
ATTR{type}=="1",
KERNEL=="eth*", NAME="eth2"
That's dynamical setup for eth1 and eth2, statically in
/etc/sysconfig/network-scripts/ifcfg-eth1
./ifcfg-eth2, including portno definitions:
OPTIONS="layer2=1 portno=N"
Something like that, didn't test it though..
HTH,
Juha Vuori
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] 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/
