Anne, Vic - I might have missed previous responses but what Anne shows in
the messages, 3088/60, I think is consider an OSA in LCS mode. This could
be that you need to put an ipldelay on the boot parameter. I haven't used
the Marist distro in a long time and I never experienced problems when
coming up with an LCS card on an LPAR but I think there were some people
that did. Carlos :-)
Saying goes: Great minds think alike - I say: Great minds think for
themselves!
Carlos A. Ordonez
IBM Corporation
Server Consolidation
|---------+--------------------------->
| | Vic Cross |
| | <vic.cross@veejo|
| | e.com.au> |
| | Sent by: Linux |
| | on 390 Port |
| | <[EMAIL PROTECTED]|
| | RIST.EDU> |
| | |
| | |
| | 10/17/2002 12:11|
| | AM |
| | Please respond |
| | to Linux on 390 |
| | Port |
| | |
|---------+--------------------------->
>-------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| From:
|
| Subject: Re: Marist Linux and OSA-Express
|
|
|
>-------------------------------------------------------------------------------------------------------------------------------|
Anne,
It would appear that OSA-E is not (at this time) supported by the Marist
system.
The problem you see is happening because your OSA-Express is not an OSA --
OSA
refers to the pre-Express OSA cards, or an OSA defined in LCS mode. If
there\'s
not an option that says \"QDIO\" or \"OSA-Express\", you\'re out of luck.
If you want to play with Marist on your OSA-Express, redefine it to use LCS
rather than QDIO. This will require IOCDS work, and a port cannot be in
LCS and
QDIO mode simultaneously so you would not be able to do this if your port
is
used by another LPAR/guest. This is also not possible if you have the
Gigabit
Ethernet OSA-Express, as it *only* supports QDIO.
Rather than changing your IOCDS, you could use CTC to link to another
system and
use that as your router to the outside world. (Of course if you don\'t
already
have CTC defined to that LPAR and would have to update the IOCDS to do so,
you
might as well change your OSA...) There\'s network voodoo involved, but
nothing
that this list couldn\'t get you through! ;)
Best of luck,
Vic Cross
On 17.10.2002 at 05:36:53, \"Peticolas, Anne\" <[EMAIL PROTECTED]>
wrote:
> Hi,
> I\'m trying to get my feet wet by bringing up Marist distribution
from
> tape in an LPAR environment. Cannot get network connectivity. (This
seems
> to be a common problem as I\'ve looked through the archives of this list,
but
> do not see an exact match to my problem, so . . . ) I\'m wondering now
> whether I should be doing something different or whether OSA-Express is
> supported by Marist. Any help/advice would be appreciated.
> I\'ve tried several variations. Right now the device is configured
in
> the IOCDS as type OSE. When it comes up I see
>
> Detected device 0090 on subchannel 01C5 - PIM = 80 PAM = 80 POM = FF
> Detected device 0091 on subchannel 01C6 - PIM = 80 PAM = 80 POM = FF
> Detected device 009E on subchannel 01C7 - PIM = 80 PAM = 80 POM = FF
>
> and
>
> SenseID: device 0090 reports: Dev Type/Mod = 3088/60
> SenseID: device 0091 reports: Dev Type/Mod = 3088/60
> SenseID: device 009E reports: Dev Type/Mod = 3088/62
>
> I answer 2) for osa ethernet to \"Select the type of your network
device:\"
> and
> noauto=1 devno_portno_pairs=0x0090,0 to \"Please type in the options for
the
> lcs module:\"
>
> After answering network questions, I get
> Bringing up interface lo
> [OK]
> Bringing up interface eth0
>
> and it just hangs there forever.
>
>
> Regards,
> Anne Peticolas
> Dept. of Veterans\'
> Affairs
> Austin, Texas
> (512) 326-6105
>
