Re: Linux LPAR install on MP3000 - LCS definition
On Wednesday, 06/12/2002 at 10:58ZE10, Vic Cross [EMAIL PROTECTED] wrote: On 12.06.2002 at 07:19:52, Rob van der Heij [EMAIL PROTECTED] wrote: On real OSA devices the number is ignored afaik. Yep. This is because on OSA, each port is its own LCS device which only has port '0'. So the default (0) is fine. Unless it is a dual-port Ethernet/Token Ring (ENTR) OSA. Those cards have 2 ports, addressable via the relative adapter number. Alan Altmark Sr. Software Engineer IBM z/VM Development
Re: Linux LPAR install on MP3000 - LCS definition
On 13.06.2002 at 00:45:18, Alan Altmark [EMAIL PROTECTED] wrote: On Wednesday, 06/12/2002 at 10:58ZE10, Vic Cross [EMAIL PROTECTED] wrote: Yep. This is because on OSA, each port is its own LCS device which only has port '0'. So the default (0) is fine. Unless it is a dual-port Ethernet/Token Ring (ENTR) OSA. Those cards have 2 ports, addressable via the relative adapter number. I was *sure* it didn't work like that, so I RTFM, and you're right Alan (of course!). It's confusing; because each port is defined with a separate DEVICE statement, and its own pair of device addresses, I believed it was a separate LCS device... so I am surprised that the port number for the second port must be specified. returns to lurk mode, sheepishly Cheers, Vic -- Vic Cross MACS mailto:[EMAIL PROTECTED] Networking, Linux, on zSeries and S/390
Linux LPAR install on MP3000 - LCS definition
I am currently trying to install the latest version of Suse Linux (2.4 kernel) in an LPAR and having trouble defining the ethernet card. The machine is a MP3000 H30 with 3 LPARs with 3 ethernet cards and 1 token ring card. LPAR 1: VSE had TR card dedicated to it. LPAR 2: not in use LPAR 3: LINUX has one ethernet card dedicated to it. MPTS, IOCP, EMIO configuration (devmap) and lantran.log have been reviewed for problems. I am installing Linux using the CD reader built into the MP3000. When i get to the part of the initial installation asking about the network I select option 2 to install OSA Ethernet (LCS device). I first tried to install manually using the real hardware addresses (720,721) and port 0. It could not find the real hardware. I then told it to do the autoinstall and it told me the hardware was a Token Ring card. I tried this several times with the same result. I even tried using an older version of SuSe (2.2 kernel) with the same results. I also tried the following from the Check HW Configuration/Detection. Selecting option 8 (show devices enabled for detection in proc/chandev. This shows all the ethernet cards as defined in the devmap (all 4 of them). Selecting option 6 (show detected devices in proc/chandev). This shows what i would expect since it matches what IOCP says is there (720 as 3088 and 721 as 3088). It appears to me that for some reason that it finds the first set of address pairs (00,01) which is in the devmap and is also the TR adapter and is trying to force that as the device driver for the LCS adapter. It shows that it finds device TR0 even though the addresses for the TR are dedicated to VSE (partition= PRODVSE in the IOCP) error msg i receive: eth0: error fetching interface information: device not found eth0 not available check device addresses/cards and cables. Any help you can give me resolving this issue would be appreciated Ira Hochner Mainline Information Systems (954) 575-0413 (office) (954) 294-1719 (cell) [EMAIL PROTECTED] (email)
Re: Linux LPAR install on MP3000 - LCS definition
I found the MP3000 (and P/390 too) very sensitive to proper 'relative adapter number' for the adapter. You need the number as defined in MPTS or LAPS (?) and letting the lcs.o driver sense them crashed my AWS3172 device driver. On real OSA devices the number is ignored afaik. Rob
