Ok, see some reference for these in sysconfig/network/scripts/hwdesc2iface, but it looks like it is hitting /sys to get the info ...
I do see reference to /etc/sysconfig/network/ifcfg-*id-$LLADDR", but our auto deploy scripts setup the etho as ifcfg-eth0 ... Ben Duncan - Business Network Solutions, Inc. 336 Elton Road Jackson MS, 39212 "Never attribute to malice, that which can be adequately explained by stupidity" - Hanlon's Razor > -------- Original Message -------- > Subject: Re: Issues with persistence of Drivers > From: David Boyes <[email protected]> > Date: Tue, July 03, 2012 8:12 am > To: [email protected] > > > > I am having issues with a test of migration from a Z9 machine to a Z114. > > > Both machines have z/vm version 5.4. > > > We can get the image over to the Z114 with it up and running, but are > > > having to force the network up on the Z114 with the znetconf -A command. > > > > > > THese are devices 0600, 0601, 0603 1731/01 when on the Z9 as well as the > > > Z114. > > > > > > The network driver and network works fine on the Z9. > > > > > > After rebooting the Z114 zLinux, the network device goes away. > > > > > > We are experiencing the same thing with the multi-path drivers. > > > > > > Any one got any ideas ? > > > > First thing: Look for hardcoded LLADDR= and WWPNs in the configuration files > for the network adapters and FCP adapters. The link-level addresses for the > FCP and network adapters will have changed with the hardware swap. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
