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
