What does "lsqeth" say?
Probably need to update (or let yast do it)
/etc/udev/rules.d/51-qeth-0.0.xxxx.rules
Mine looks like this:
# Configure qeth device at 0.0.3000/0.0.3001/0.0.3002
ACTION=="add", SUBSYSTEM=="drivers", KERNEL=="qeth", IMPORT{program}="collect
0.0.3000 %k 0.0.3000 0.0.3001 0.0.3002 qeth"
ACTION=="add", SUBSYSTEM=="ccw", KERNEL=="0.0.3000", IMPORT{program}="collect
0.0.3000 %k 0.0.3000 0.0.3001 0.0.3002 qeth"
ACTION=="add", SUBSYSTEM=="ccw", KERNEL=="0.0.3001", IMPORT{program}="collect
0.0.3000 %k 0.0.3000 0.0.3001 0.0.3002 qeth"
ACTION=="add", SUBSYSTEM=="ccw", KERNEL=="0.0.3002", IMPORT{program}="collect
0.0.3000 %k 0.0.3000 0.0.3001 0.0.3002 qeth"
TEST=="[ccwgroup/0.0.3000]", GOTO="qeth-0.0.3000-end"
ACTION=="add", SUBSYSTEM=="ccw", ENV{COLLECT_0.0.3000}=="0",
ATTR{[drivers/ccwgroup:qeth]group}="0.0.3000,0.0.3001,0.0.3002"
ACTION=="add", SUBSYSTEM=="drivers", KERNEL=="qeth",
ENV{COLLECT_0.0.3000}=="0",
ATTR{[drivers/ccwgroup:qeth]group}="0.0.3000,0.0.3001,0.0.3002"
LABEL="qeth-0.0.3000-end"
ACTION=="add", SUBSYSTEM=="ccwgroup", KERNEL=="0.0.3000",
ATTR{portname}="LACPVSW"
ACTION=="add", SUBSYSTEM=="ccwgroup", KERNEL=="0.0.3000", ATTR{portno}="0"
ACTION=="add", SUBSYSTEM=="ccwgroup", KERNEL=="0.0.3000", ATTR{layer2}="1"
ACTION=="add", SUBSYSTEM=="ccwgroup", KERNEL=="0.0.3000", ATTR{online}="1"
Marcy
This message may contain confidential and/or privileged information. If you are
not the addressee or authorized to receive this for the addressee, you must not
use, copy, disclose, or take any action based on this message or any
information herein. If you have received this message in error, please advise
the sender immediately by reply e-mail and delete this message. Thank you for
your cooperation.
-----Original Message-----
From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Lee
Stewart
Sent: Tuesday, February 28, 2012 4:13 PM
To: [email protected]
Subject: [LINUX-390] OSI Layer 2/3 mismatch?
Hi all....
I must be missing something...
Customer has a VM 6.1 system (RSU 1101 + z114 PTFs) and SLES11 SP1
guests. Initially the guest was on a Layer3 Vswitch - no problem. They
needed to change to go to Layer2 so they could have guests on different
VLANs - but still have the Linuxes be Layer3. We:
- Updated the IP info on the Llnuxes and shut them down and logged off.
- Deleted (DETach) the old Layer3 Vswitch.
- Networking changed the real switch port to trunk mode
- We changed the TCPIP stack to Layer2 and it's VLAN - all ok..
- We redefined the Vswitch as:
DEFINE VSWITCH VSWITCH2 RDEV E203 ETH VLAN 999 NAT 999
(Default PORTTYPE ACCESS)
- Regranted the user as:
SET VSWITCH VSWITCH2 GRANT LXTECH VLAN 301
All looks good in the queries....
But when we boot the Linux, we can see qeth try to register layer3, but
we get:
The qeth device is not configured for the OSI layer required by z/VM
We've double checked our definitions and even bounced the system.
Have I missed something? Am I having a brain cloud?
Thanks,
Lee
--
Lee Stewart, Senior SE
Sirius Computer Solutions
Phone: (303) 996-7122
Email: [email protected]
Web: www.siriuscom.com
----------------------------------------------------------------------
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/
----------------------------------------------------------------------
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/
