Might it be helpful if router paths could be 'macro-ed'? Something like notifications... so only the macro definitions had to be maintained?
Granted, I like Greg's idea much better... :)
Josh Luthman wrote:
I would rather sever my you-know-what then have to go through all of that =)
That is a LOT of work to do. I'll put up with the annoying multi-message nights instead of doing that!
On Mon, Jun 16, 2008 at 2:36 PM, Hubbard, Greg L <greg.hubbard at eds.com> wrote:
I have used this method with great success, but it is a pain in the you-know-what to maintain. It would be nice if this "router" tagging could be made recursive so you only have to specify one upstream host for each host, assuming that the upstream host is also in Hobbit. As it is today you have to specify the full path to each "leaf" and this can get long.
GLH
-- Rich Smrcina VM Assist, Inc. Phone: 414-491-6001 Ans Service: 360-715-2467 rich.smrcina at vmassist.com http://www.linkedin.com/in/richsmrcina
Catch the WAVV! http://www.wavv.org WAVV 2009 - Orlando, FL - May 15-19, 2009