It wasn't that the manuals stated that fact as much as it implied it. The manuals basically said that vswitch was a software version of hipersockets. Fair enough and I took it futher. In my book, a software version of hardware, a virtual version of something real, something that emulates something else, all should be able to be use without any changes.
So I tried it. I took an existing zLinux machine, connected to a vswitch, and swapped out the NICDEF for real hipersocket addresses. Didn't work at all. So, I fell back to vswitch and added the hipersocket addresses and configured them via yast. Worked a lot better. Yep, hipersockets is quite a bit different than OSA or Vswitch. However, OSA (real hardware) and vswitch (VM only software), seem to be very, very simular from a connection point of view. But the point on the origional post, was that installing with vswitch didn't work, but installing with OSA did (and then to swap the real OSA addresses for the NICDEF) did work. My point was that I believe that he/she selected something other that 3 (OSA) when using the vswitch. A common mistake, as I found out, was thinking hipersockets and vswitch were more simular then different. Tom Duerbusch THD Consulting >>> [EMAIL PROTECTED] 1/5/2007 12:31 PM >>> The z/VM Virtual Switch only accepts connections from virtual QDIO OSAs. If you've found manuals that state it can connect to a HiperSocket, you should file a bug report with the manual owner. Only HiperSocket Guest LANS and real hardware HiperSockets exercise the HiperSockets code. Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Tom Duerbusch Sent: Friday, January 05, 2007 11:24 AM To: [email protected] Subject: Re: HCPIPN2833E During install of SUSE SLES9x -snip- I've learned that 3 (OSA) is for OSA adapters and vswitch. 10 (Hipersockets) is only for hipersockets. Apparently, hipersockets is a different animal even though I've found sections of many manuals stating that vswitch was a software implementation of hipersockets. So I gathered I could just trade the vswitch connection for hipersocket and start running. Wrong assumption, in my experiment. ---------------------------------------------------------------------- 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
