I have QLogic NIC card. When I am trying to configure NIC card using yast, yast will create configuration file /etc/sysconfig/network/ifcfg-eth-bus-pci-0000:03:02.0" Now if I try to execute command ifup eth0 it will give me error "No configuration found for eth0".

If I rename file /etc/sysconfig/network/ifcfg-eth-bus-pci-0000:03:02.0"
to "/etc/sysconfig/network/ifcfg-eth0" and try to run command ifup eth0 it will work fine.

I also have Broadcom NIC card on same system. If I try to configure this card it will create configuration file "/etc/sysconfig/network/ifcfg-eth-id-00:17:08:57:b3:58" where 00:17:08:57:b3:58 is MAC address of Broadcom card.

How can I force yast to create configuration file using MAC for the QLogic NIC card?

I am trying this on SLES 9 SP3 on x86

I actually have run into the same problem, running SLES 9 SP3 on an ESX 3 virtual machine. Originally when I configured the NIC through yast, everything worked fine, it created the /etc/sysconfig/network/ifcfg-eth-<MAC ADDRESS> file and it worked. Then I added in another NIC (virtually) to connect to a virtual switch which I'm using to connect to another SLES 9 SP3 box. I tried configuring that through yast, and for some reason it created the file with the BUS-id, and when I try to ifup eth1, it says there's no configuration file.

Renaming that file to ifcfg-eth1 allowed it to be found, but why does yast do this? Is there a solution to the prior poster's question, can we force yast to use the mac address?

Also, I had a second virtual SLES 9 SP3 box, and on that one, I had decided, hey, maybe if I delete both NIC configurations it will recognize them both correctly when I re-add them. Instead, it name them BOTH in the bus-id style. I figured it might be something to do with VMware, so I also tried deleting both configurations, and re-running the vmware-tools-config.pl, no difference, tried running it again while they were configured incorrectly, no such luck.

Any help would be appreciated, or if there's a link describing the behavior please post if here to help future people looking for answers

Thanks-
-Josh

I had a similar problem to this. I could create eth0 in yast but the system kept looking for eth1 when restarting the network.By removing all uncommented lines in /etc/udev/rules.d/30-net_persistent_names.rules I was able to recreate the eth0 config through yast and the network restart was successful.

Hope it helps you.

M