Agreed.
On Tuesday 19 November 2002 10:55 am, you wrote:
> In a message dated 11/19/2002 9:47:04 AM Mountain Standard Time,
>
> [EMAIL PROTECTED] writes:
> > If you're playing the game by somebody else's rules, on occasion you have
> > to give in... :(
> >
> > On Tuesday 19 November 2002 10:25 am
In a message dated 11/19/2002 9:47:04 AM Mountain Standard Time,
[EMAIL PROTECTED] writes:
> If you're playing the game by somebody else's rules, on occasion you have to
> give in... :(
>
> On Tuesday 19 November 2002 10:25 am, you wrote:
> >We have OSA/SF set up, but another 'faction' of the s/3
|
|cc:
|
| From:
|
| Subject: Re: g3 and O
If you're playing the game by somebody else's rules, on occasion you have to
give in... :(
On Tuesday 19 November 2002 10:25 am, you wrote:
> We have OSA/SF set up, but another 'faction' of the s/390 group controls
> that. Therein lies the problem. I'd rather not string another cable but I
> will
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| Subject
I might suggest that he verify that the CHPID is online and to examine the
Linux startup messages.
On Tuesday 19 November 2002 09:36 am, you wrote:
> No LPARs at all. My colleague shutdowned OS/390 and load linux.
>
>
> WBR, Sergey
>
--
Rich Smrcina
Sytek Services, Inc.
Milwaukee, WI
[EMAIL PROTE
The port can be shared, but OSA/SF is the way that the sharing is set up on
the card and in the I/O subsystem. Linux will just see an LCS device.
Do you have OSA/SF set up or are you using the defaults?
On Tuesday 19 November 2002 09:10 am, you wrote:
> That helps if you understand OSA/SF - whic
On Tuesday, 11/19/2002 at 09:10 CST, James Melin
<[EMAIL PROTECTED]> wrote:
> That helps if you understand OSA/SF - which I don't. What I want to be
> able to prove to the people who control the network is that YES indeed,
I
> can have an LPAR share a port on an OSA card. The biggest thing
prevent
No LPARs at all. My colleague shutdowned OS/390 and load linux.
WBR, Sergey
Rich Smrcina
<[EMAIL PROTECTED]> To:
PROTECTED]
Subject: Re: g3 and OSA-2 Ethernet problem
The devices are shared at the I/O definition level. If the environment is
mixed, it would have been created on the OS/390 side.
The I/O definition can be viewed from the Hardware Management Console if you
have the proper authority or it can be view
|
| cc:
|
| Subject: Re: g3 and OSA-2 Ethernet problem
|
>---
The devices are shared at the I/O definition level. If the environment is mixed, it
would have been created on the OS/390 side.
The I/O definition can be viewed from the Hardware Management Console if you have the
proper authority or it can be view via HCD on the OS/390 side.
I am not exactly s
;--|
> >
> | To: [EMAIL PROTECTED]
> |
To: [EMAIL PROTECTED]
|
| cc:
|
| Subject: Re: g3
I'll start with the silly questions... was the OSA configured for port
sharing between LPARS?
On Tuesday 19 November 2002 07:48 am, you wrote:
> Hi.
>
> My colleague has a problem with G3 machine with OSA-2 card. SLES7 doesn't
> see path to OSA (that path doesn't present in /proc/subchannels).
>
Hi.
My colleague has a problem with G3 machine with OSA-2 card. SLES7 doesn't
see path to OSA (that path doesn't present in /proc/subchannels).
OS/390 on that machine works fine.
Any suggestions?
WBR, Sergey
16 matches
Mail list logo
