What tool, if any, did you use to create the interface definitions? YaST, or did you do it by hand? If by hand, try using YaST and see if that helps.
After having to deal with many, many, Intel Linux systems that all have _at least_ four interfaces, I would suggest that not worrying about which interface is called eth0, versus eth9 or some other name, would be the simplest course. Configure each interface with the correct IP and netmask, set up your default gateway and other routes, and just don't sweat it. Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Spann, Elizebeth (Betsie) Sent: Thursday, February 16, 2006 4:41 PM To: [email protected] Subject: Linux network question Linux experts: I am trying to force one network connection to be eth0 and another eth1 but after an IPL, the lower OSA triplet address is eth0 and the other eth1. Is DEVICE= being ignored in the network files? zVM 4.4, SuSE SLES 9, kernel 2.6.5-7.191-s390x OSA C00-C02 attached * OSA E00-E02 attached * /etc/sysconfig/network/ifcfg-qeth-bus-ccw-0.0.0E00 contains DEVICE=eth0 and IPADDR=10.203.221.15 /etc/sysconfig/network/ifcfg-qeth-bus-ccw-0.0.0C00 contains DEVICE=eth1 and IPADDR=10.203.221.45 /etc/sysconfig/hardware files have the correct CCW_CHAN_IDS. Cat /proc/qeth shows eth0 on C00 and eth1 on E00 Ifconfig has eth0 with IP of 10.203.221.45 and eth1 with IP of 10.203.221.15 Any suggestions? Betsie Spann ---------------------------------------------------------------------- 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
