Re: Ethernet/OSA strangeness

2003-01-08 Thread James Melin
In thenetconfig process it does ask me for the device number (0832) was
entered, it then asked me for the relative port, to which I answered 1, as
I knew port 0, devices 830,831 to be in use by the other LPAR.   LPAR 2
does not even see 830 and 831 as eligible LCS devices ( I so wish to God I
could cut and paste from our HMC into this e-mail)

So either it is overriding my port selection (doubtful) or something is
screwy with the OSA configuration (which does not seem likely, since the
config has lp1 set for relative devices 00,01 and port 0, while LP 2 has
relative devices 02,03 on port 1) or something else is missing and I'm not
seeing it





|-+>
| |   Alan Altmark |
| ||
| |   Sent by: Linux on|
| |   390 Port |
| |   <[EMAIL PROTECTED]|
| |   IST.EDU> |
| ||
| ||
| |   01/08/2003 02:23 |
| |   PM   |
| |   Please respond to|
| |   Linux on 390 Port|
| ||
|-+>
  
>--|
  |
  |
  |   To:   [EMAIL PROTECTED]
  |
  |   cc:  
  |
  |   Subject:  Re: Ethernet/OSA strangeness   
  |
  
>--|




On Wednesday, 01/08/2003 at 01:58 CST, James Melin
<[EMAIL PROTECTED]> wrote:
> hey gang. Me again. Resolved that very odd problem where my second Linux
> LPAR could only see device 83F. Someone had loaded an old OSA-SF
> configuration to that card at the last POR and port 1 was not defined.
We
> loaded a new config, configured the chipid offline to all systems and
> loaded a new config - voila , the port 1 address pair showed up.
>
> The first Linux partition is SuSE 7.0, (2.2.16) very old at this point.
> The new one (have been trying RH and SuSE) is the install ramdisk system
> for SuSE 7.2, (2.4.7 I think)
>
> The network card in question is an OSA Express ENTR 10 MB 2 port card.
>
> LPAR 1 sees device 0830, 0831 and 083F - and is currently configured for
> 'auto' detection of the ethernet hardware.
> LPAR 2 sees device 0832,0833 and 083F - This was attempted with auto and
> manual configuration so device and port could be specified.
>
> OSASF indicates the port 0 MAC address was 00:20:35:04:F6:4D
>   and that the port 1 MAC address was 00:20:35:04:F6:CD
>
> The two LPARS are reporting they are talking to the device with MAC
address
> 00:20:35:04:F6:4D
>
> The second LPAR, is obviously not getting to the network.  What I wanna
> figure out is HOW the Linux is seeing/retrieving the same MAC address
from
> the hardware on two diff. ports.

The default port is port 0.  If you want to use the other port, specify
port 1 in your Linux config.  Every host using the same port sees the same
MAC address.

Alan Altmark
Sr. Software Engineer
 IBM z/VM Development



Re: Ethernet/OSA strangeness

2003-01-08 Thread Alan Altmark
On Wednesday, 01/08/2003 at 01:58 CST, James Melin
<[EMAIL PROTECTED]> wrote:
> hey gang. Me again. Resolved that very odd problem where my second Linux
> LPAR could only see device 83F. Someone had loaded an old OSA-SF
> configuration to that card at the last POR and port 1 was not defined.
We
> loaded a new config, configured the chipid offline to all systems and
> loaded a new config - voila , the port 1 address pair showed up.
>
> The first Linux partition is SuSE 7.0, (2.2.16) very old at this point.
> The new one (have been trying RH and SuSE) is the install ramdisk system
> for SuSE 7.2, (2.4.7 I think)
>
> The network card in question is an OSA Express ENTR 10 MB 2 port card.
>
> LPAR 1 sees device 0830, 0831 and 083F - and is currently configured for
> 'auto' detection of the ethernet hardware.
> LPAR 2 sees device 0832,0833 and 083F - This was attempted with auto and
> manual configuration so device and port could be specified.
>
> OSASF indicates the port 0 MAC address was 00:20:35:04:F6:4D
>   and that the port 1 MAC address was 00:20:35:04:F6:CD
>
> The two LPARS are reporting they are talking to the device with MAC
address
> 00:20:35:04:F6:4D
>
> The second LPAR, is obviously not getting to the network.  What I wanna
> figure out is HOW the Linux is seeing/retrieving the same MAC address
from
> the hardware on two diff. ports.

The default port is port 0.  If you want to use the other port, specify
port 1 in your Linux config.  Every host using the same port sees the same
MAC address.

Alan Altmark
Sr. Software Engineer
 IBM z/VM Development



Ethernet/OSA strangeness

2003-01-08 Thread James Melin
hey gang. Me again. Resolved that very odd problem where my second Linux
LPAR could only see device 83F. Someone had loaded an old OSA-SF
configuration to that card at the last POR and port 1 was not defined. We
loaded a new config, configured the chipid offline to all systems and
loaded a new config - voila , the port 1 address pair showed up.

The first Linux partition is SuSE 7.0, (2.2.16) very old at this point.
The new one (have been trying RH and SuSE) is the install ramdisk system
for SuSE 7.2, (2.4.7 I think)

The network card in question is an OSA Express ENTR 10 MB 2 port card.

LPAR 1 sees device 0830, 0831 and 083F - and is currently configured for
'auto' detection of the ethernet hardware.
LPAR 2 sees device 0832,0833 and 083F - This was attempted with auto and
manual configuration so device and port could be specified.

OSASF indicates the port 0 MAC address was 00:20:35:04:F6:4D
  and that the port 1 MAC address was 00:20:35:04:F6:CD

The two LPARS are reporting they are talking to the device with MAC address
00:20:35:04:F6:4D

The second LPAR, is obviously not getting to the network.  What I wanna
figure out is HOW the Linux is seeing/retrieving the same MAC address from
the hardware on two diff. ports.