[Date Prev] [Date Index] [Date Next] [Thread Prev] [Thread Index] [Thread Next]
Stout, Brandon firstname.lastname@example.org
Wed, 10 Apr 2013 17:05:30 GMT
Thanks Z and Jason, there turned out to be a switching problem that prevented the server from reaching the console device. DNS was all good though.
From: Zonker <email@example.com>
Date: Tuesday, April 9, 2013 4:38 PM
To: Brandon Stout <firstname.lastname@example.org>
Cc: "email@example.com" <firstname.lastname@example.org>
Subject: Re: conserver (22474): ERROR: [trfw01a] connect(5): No route to host: forcing down
Jason is on the right track. As a Best Practice, my Conserver hosts use an /etc/host file, with all of my console servers (and other infrastructure listed)., and my resolv.conf file prefers the local file to network resources. (I do this, because I want this box to be one of the first things I bring up, along with console servers, *before* I start bringing of infrastructure switches and servers, so that I can log their startups.)
Try nslookup for your console server names... if that fails, conserver won't be able to talk to them.
On Tue, Apr 9, 2013 at 3:36 PM, Stout, Brandon <email@example.com> wrote:
ConsoleTeam - Support and training services for Conserver users.
- - - - - - - -