Thanks Marcy, I'll see what I can get going.
Dave Dave Stuart Prin. Info. Systems Support Analyst County of Ventura, CA 805-662-6731 [EMAIL PROTECTED] >>> "Marcy Cortes" <[EMAIL PROTECTED]> 10/14/2008 11:45 AM >>> Welcome newbie :) 1) I've seen it too on SP2. You can just copy the file in /etc/sysconfig/hardware/ and the file in /etc/sysconfig/network files that correspond to the existing interace to appropriately named new files and edit with vi, changing the IP and chanids. With 2 interfaces, you'll have to figure out your routing, but you probably knew that already. 2) We too have a proxy server that can't see to get to Novell Customer Center. Mark Post worked with me for quite some time and was very close to figuring it all out (likely malformed request and their inbound is pickier than your average bear ) when I suddenly found another proxy server within the bank that worked just fine and I dumped him and moved on to my next challenges. 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 David Stuart Sent: Tuesday, October 14, 2008 8:36 AM To: [email protected] Subject: [LINUX-390] SuSE 10 SP 2 - New Install - Misc Questions Morning all, <newbie on> Yesterday I completed a new install of SLES 10 SP 2 into an LPAR. During the install, I defined one OSA-Express port, and it appears to be working fine. However, I have several networking related nuisances and questions. 1) How do you define a second OSA-Express port? I tried defining it using YAST, but the OSA-Express is running QDIO, and YAST seems to treat each individual address as a separate network card, rather than using the three required for QDIO. I chose a network type of QETH. I didn't see anything specific to QDIO, but thought QETH was probably the closest. 2) Novell Customer Center - We have a proxy between our internal network and the internet. I configured the proxy, and the 'test connection' says that it works ok, but when I try to 'register', check for patches, etc., it says that it can't connect. And that's enough for so early in the morning. </newbie on> TIA, Dave Dave Stuart Prin. Info. Systems Support Analyst County of Ventura, CA 805-662-6731 [EMAIL PROTECTED] ---------------------------------------------------------------------- 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
