Part of the problem is that during an upgrade our radius application still listens on port 1813 and 1812 and replies to the keepalves (working with development to resolve that since I think that is a problem) so in the mean time I'd like to be able to mark and upgrading server dead then decide when it should be marked alive.
Thanks for the quick reply! Brian -----Original Message----- From: freeradius-users-bounces+bcarpio=broadhop....@lists.freeradius.org [mailto:freeradius-users-bounces+bcarpio=broadhop....@lists.freeradius.org] On Behalf Of Alan DeKok Sent: Friday, February 04, 2011 11:45 AM To: FreeRadius users mailing list Subject: Re: Proxy Maintenance Process Brian Carpio wrote: > Currently we are using freeradiusd to proxy / load balance requests to > our backend radius application. However as I’m sure many of you > encounter there are times which require maintenance / upgrades of the > backend servers, what is the “best practice” in regards to putting > home_servers into maintenance so that freeradiusd doesn’t attempt to > send traffic to them? Use "radmin" radmin> set home server state IP PORT dead > I’m not sure if there is a simple command we can run? Or is the only > option to comment out the home_server from the home_server_pool and > then kill -1 to the radiusd process? Nope. Mark it dead. When it comes back up, the server will figure that out (if Status-Server is enabled) Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
