[28811] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: IGPs and services?

daemon@ATHENA.MIT.EDU (Valdis.Kletnieks@vt.edu)
Wed May 17 02:41:56 2000

Message-Id: <200005170639.e4H6dkn24380@black-ice.cc.vt.edu>
To: rmeyer@mhsc.com
Cc: nanog@merit.edu
In-reply-to: Your message of "Tue, 16 May 2000 23:22:09 PDT."
             <00e201bfbfc8$3b7597f0$eaaf6cc7@PEREGRIN> 
From: Valdis.Kletnieks@vt.edu
Date: Wed, 17 May 2000 02:39:45 -0400
Errors-To: owner-nanog-outgoing@merit.edu


On Tue, 16 May 2000 23:22:09 PDT, "Roeland M.J. Meyer" said:
> > What  is  the  general  feeling  about running  routing  protocols  on
> > web/dns/mail servers?
> 
> Technically, not a problem. However, there is a school of thought that
> thinks that to be a bad policy. That routing functions should be on
> appliance-level systems, like routers. There is also some merit in that
> appliances are more reliable, mainly because nothing *else* can cause an
> operational interrupt. Unix systems are *real* good about process
> control. but, there are still some things that makes it advisable to
> reboot a system, at times. If that system is ALSO a critical router then
> the entire net is down until the reboot is complete. It is generally not

How about the case of a system with several network interfaces on
different subnets, and using a routing protocol to better pick which
interface to send a connection out on?

This is probably more applicable to mail servers - web and dns servers
don't have as much latitude as they sort of have to answer on the
interface they were contacted on...

				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech


home help back first fref pref prev next nref lref last post