Re: Multiple Network Interface Routing Problem
"Sollenberger, Justin W Mr CIV US DISA CDB24" wrote: We are currently running a SLES 10 SP2 guest (hostx) with access to three networks (eth0, eth1, eth2). The issue we are having is that the default route is not correct after an ipl. If I delete the incorrect route (using: route del) and add the correct route (using: route add) everything works as it should. On a network with three interfaces I would like do dynamic routing, and run routed or gated. If you don't yet, soon you will want redundant routes and that means that hosts should be able to choose the best route dynamically. -- glen -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Multiple Network Interface Routing Problem
Thanks to all who replied. I was able to get it working properly by removing all of the default routes except for one. I also replaced those default routes (in the ifroute files) with the other more specific routes. Now my route table look like this: Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface x.y.z.128 * 255.255.255.224 U 0 0 0 eth0 link-local * 255.255.0.0 U 0 0 0 eth0 1.0.0.0 1.a.1.1 255.0.0.0 UG0 00 eth2 2.0.0.0 2.b.1.1 255.0.0.0 UG0 00 eth1 loopback* 255.0.0.0 U 0 0 0 lo default x.y.z.129 0.0.0.0 UG0 00 eth0 VR, Justin Sollenberger Linux on System z Administrator Operating Systems, CDB24 DECC Mechanicsburg DSN: 430-8386 Comm: 717-605-8386 justin.sollenber...@csd.disa.mil -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of David Boyes Sent: Tuesday, January 06, 2009 12:14 To: LINUX-390@VM.MARIST.EDU Subject: Re: Multiple Network Interface Routing Problem There's no guarantee in what order a network interface will initialize, so I think the confusion is with multiple default route specifications, and you're getting lucky with the other machine getting the right one. There should be only one default route specified. The route add/del flushes the extra entries and causes it to work. I think I would try removing the default entry from the ifroute files for all but one interface (the one that should actually be the default network if there is not a more specific route) and add a init script to establish any other needed routes later in the boot process. That way you can control when the additonal connectivity becomes available and ensure that the routes are correctly inserted. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Multiple Network Interface Routing Problem
>>> On 1/6/2009 at 12:32 PM, Ron Foster at Baldor-IS >>> wrote: -snip- > Notice I had to use the persistent name for the interface. The eth0, > eth1 type of name > can change from IPL to IPL. If you're running SLES10, that shouldn't be true. The udev rules in /etc/udev/rules.d/30-net_persistent_names.rules should provide consistency across IPLs. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Multiple Network Interface Routing Problem
Mark, Come to think of it, the last time I remember having device names change on me was a few of the systems that I upgraded to SLES10 SP2. I don't remember what level of code I was coming from-SLES10 or SLES10SP1. I still think I will stick with the long names for the time being. On most of our systems we have two hipersocket interfaces defined-5100 and 5200. hsi0 is not always 5100. Now that I know that the rules file is there, I can go fix it. But I have other things to do right now. Thanks for the info, Ron Mark Post wrote: On 1/6/2009 at 12:32 PM, Ron Foster at Baldor-IS wrote: -snip- Notice I had to use the persistent name for the interface. The eth0, eth1 type of name can change from IPL to IPL. If you're running SLES10, that shouldn't be true. The udev rules in /etc/udev/rules.d/30-net_persistent_names.rules should provide consistency across IPLs. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Multiple Network Interface Routing Problem
Justin, We have systems with multiple network interfaces. I finally had to modify the default route in /etc/sysconfig/network/routes to look like this. default 32.71.175.1 - qeth-bus-ccw-0.0.0600 Notice I had to use the persistent name for the interface. The eth0, eth1 type of name can change from IPL to IPL. Ron Sollenberger, Justin W Mr CIV US DISA CDB24 wrote: We are currently running a SLES 10 SP2 guest (hostx) with access to three networks (eth0, eth1, eth2). The issue we are having is that the default route is not correct after an ipl. If I delete the incorrect route (using: route del) and add the correct route (using: route add) everything works as it should. We have another system (host z) running with the same three interfaces and are having no problems there. I'm just not sure how Linux is creating its routing table with the info provided in the ifroute files. hostz comes up with the correct default ip (x.y.z.129) and hostx does not. The ips/gateways/masks are what was given to me from our networking office. I've included the output from route and the /etc/sysconfig/network/ifroute* files from hostx and from hostz: hostx:/etc/sysconfig/network # route Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface x.y.z.128 0.0.0.0 255.255.255.224 U 0 00 eth0 1.0.0.0 0.0.0.0 255.0.0.0 U 0 00 eth2 2.0.0.0 0.0.0.0 255.0.0.0 U 0 00 eth1 127.0.0.0 0.0.0.0 255.0.0.0 U 0 00 lo default 1.a.1.1 0.0.0.0 UG0 00 eth0 hostx:/etc/sysconfig/network # cat ifroute-qeth-bus-ccw-0.0.0* defaultx.y.z.1290.0.0.0eth0 default1.a.1.1 0.0.0.0eth2 default2.b.1.1 0.0.0.0eth1 hostz:/etc/sysconfig/network # route Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface x.y.z.128 0.0.0.0 255.255.255.224 U 0 00 eth0 1.0.0.0 0.0.0.0 255.0.0.0 U 0 00 eth2 2.0.0.0 0.0.0.0 255.0.0.0 U 0 00 eth1 127.0.0.0 0.0.0.0 255.0.0.0 U 0 00 lo default x.y.z.129 0.0.0.0 UG0 00 eth0 hostz:/etc/sysconfig/network # cat ifroute-qeth-bus-ccw-0.0.0* defaultx.y.z.1290.0.0.0eth0 default1.a.1.1 0.0.0.0eth2 default2.b.1.1 0.0.0.0eth1 Any ideas on why hostx and hostz come up with different default gateways when the configuration files are the same? What am I missing? How can I correct it? Thanks in advance for your help. VR, Justin Sollenberger -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 . -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Multiple Network Interface Routing Problem
There's no guarantee in what order a network interface will initialize, so I think the confusion is with multiple default route specifications, and you're getting lucky with the other machine getting the right one. There should be only one default route specified. The route add/del flushes the extra entries and causes it to work. I think I would try removing the default entry from the ifroute files for all but one interface (the one that should actually be the default network if there is not a more specific route) and add a init script to establish any other needed routes later in the boot process. That way you can control when the additonal connectivity becomes available and ensure that the routes are correctly inserted. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Multiple Network Interface Routing Problem
>>> On 1/6/2009 at 11:59 AM, "Sollenberger, Justin W Mr CIV US DISA CDB24" wrote: -snip- > Any ideas on why hostx and hostz come up with different default gateways > when the configuration files are the same? What am I missing? How can > I correct it? Thanks in advance for your help. What are the contents of /etc/sysconfig/network/routes on the two systems? Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
