I haven't worked with the starter system, but you can fix the layer 2/3 mismatch by
echo "QETH_LAYER2_SUPPORT=1" >> /etc/sysconfig/hardware/hwcfg-qeth-bus-ccw-0.0.0340 And rebooting. Marcy (in the middle of L3 -> L2 conversion myself :) 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 Shedlock, George Sent: Tuesday, November 18, 2008 11:06 AM To: [email protected] Subject: Re: [LINUX-390] Install problem with SLES 10 on Vswitch I am not sure if this is the same problem as the original poster indicated. When I IPL the SLES 10 SP2 starter system I get the following messages: qeth: loading qeth S/390 OSA-Express driver qeth: received an IDX TERMINATE with cause code 0xf6 qeth: sense data available on channel 0.0.0340. qeth: cstat 0x0 dstat 0xE qeth: irb: 00 c2 60 17 1f a8 70 38 0e 00 10 00 00 80 00 00 qeth: irb: 01 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 qeth: sense data: 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 qeth: sense data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 qeth: Initialization in hardsetup failed! rc=-5 This IPL was performed after I issued the command: SET VSWITCH ADCVS01 GRANT DCVML98 Command complete Previous posts seemed to indicate that there was a mis-match in layer=2 vs non layer=2. I have confirmed that we are running with layer=2. Further in the IPL process I see these messages: Setting up network interfaces: lo lo IP address: 127.0.0.1/8 Checking for network time protocol daemon (NTPD): ..unused Ý1A..doneWaiting for mandatory devices: qeth-bus-ccw-0.0.0340 __NSC__ 14 13 12 11 10 9 8 7 5 4 3 2 1 0 qeth-bus-ccw-0.0.0340 No interface found Ý1A..failedSetting up service network . . . . . . . . . . . . . . . ...failed Any suggestions on how to proceed? George Shedlock Jr AEGON Information Technology AEGON USA 502-560-3541 -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Monday, November 17, 2008 2:36 PM To: [email protected] Subject: Re: Install problem with SLES 10 on Vswitch >>> On 11/17/2008 at 1:13 PM, Mauro Souza <[EMAIL PROTECTED]> wrote: > Hi Richard! > > The most common problem with a VSWITCH is the lack of authorization to > use it. Under MAINT, try a Q VSWITCH ACCESS. If your guest isn't > listed, you can solve it using "CP SET VSWITCH VSW1 GRANT LINUX99". It's unlikely that his authorization to couple to the VSWITCH goes away between phase 1 and phase 2 of the install. Mark Post ---------------------------------------------------------------------- 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 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 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
smime.p7s
Description: S/MIME cryptographic signature
