Ah, you are right! I must have looked at a sles 10 server! Glad it was useful, though!
Marcy -----Original Message----- From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Ron Foster at Baldor-IS Sent: Thursday, February 09, 2012 2:52 PM To: [email protected] Subject: Re: [LINUX-390] Anyone lose network connectivity during upgrade to SLES11 SP1 Marcy, Thanks for the info. It appears that on SLES11SP1 the name of the file changed to 70-persistent-net.rules Thanks for giving the information on where the rules files are. Ron ________________________________________ From: Linux on 390 Port [[email protected]] On Behalf Of Marcy Cortes [[email protected]] Sent: Friday, February 03, 2012 9:36 AM To: [email protected] Subject: Re: Anyone lose network connectivity during upgrade to SLES11 SP1 So you can modify /etc/udev/rules.d/30-net_persistent_names.rules For the servers we have with more than 1 interface, it contains this: SUBSYSTEM=="net", ACTION=="add", ENV{PHYSDEVPATH}=="*0.0.3000", IMPORT="/lib/udev/rename_netiface %k eth0" SUBSYSTEM=="net", ACTION=="add", ENV{PHYSDEVPATH}=="*0.0.4000", IMPORT="/lib/udev/rename_netiface %k eth1" That file refers you to /usr/share/doc/packages/sysconfig/README.Persistent_Interface_Names for more info Marcy -----Original Message----- From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Ron Foster at Baldor-IS Sent: Friday, February 03, 2012 7:13 AM To: [email protected] Subject: Re: [LINUX-390] Anyone lose network connectivity during upgrade to SLES11 SP1 Tobias, I will have to further testing, but I think you have come up with the cause of our problem. I am just going to have to figure out the best way to fix it. Here is the problem: 1. Almost all of our systems have more than one network interface. 2. So in order to avoid an error message, we have to modify our default route to include the interface. In order to keep that interface name from changing, we used the SLES10 version of persistent interface names. In other words, our default route looks like this: default 10.80.200.1 - qeth-bus-ccw-0.0.0700 3. You may ask why we used qeth-bus-ccw-0.0.0700 instead of the short interface name eth0. The reason why is that in our experience, the short interface names have this habit of changing. We would come in some Saturday night, take all the Linux systems down, apply some z/vm maintenance, and then bring up our Linux systems. At that point, some number of our Linux systems no longer communicated with the outside world. I finally got tired of that and changed all the default routes to use the long names. 4. You might say that that problem is fixed and does not happen anymore. On this system I am upgrading the interface we want to use for communication to the outside world is eth4. I start out the upgrade, and by the time I get to the second part of the upgrade, that is the part where I lose network connectivity. The interface name has changed to eth0 and it looks like SLES11 SP1 is no longer honoring the long interface name, so this Linux system cannot communicate with the outside world during the second part of the upgrade. I suppose my next step is to put the SLES10 SP4 system back, and change the default route to use eth4 and see if when the upgrade process changes the interface name, it also changes the default route. Does anyone know where some documentation that documents this behavior? Thanks, Ron ________________________________________ From: Linux on 390 Port [[email protected]] On Behalf Of Tobias Doerkes [[email protected]] Sent: Friday, February 03, 2012 2:03 AM To: [email protected] Subject: Re: Anyone lose network connectivity during upgrade to SLES11 SP1 Hi, what about routing? Is it possible that the default route does point to an inactive interface? Kind regards, Tobias. PS: Sorry i forgot the subject. ---------------------------------------------------------------------- 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/ ---------------------------------------------------------------------- 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/ ---------------------------------------------------------------------- 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/ ---------------------------------------------------------------------- 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/ ---------------------------------------------------------------------- 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/
