[j-nsp] routing engine communication

[Greg.Griffis at cox.com]

As far as I know there is not a fix (we have seen this since 6.4).  It
involves using Radius or Tacacs without having FXP0 enabled.  The backup
RE cannot reach the authentication server so it can't authenticate you.
The only way it works is with a local login so that the backup RE can
authenticate you itself.  Otherwise, the backup RE has to be able to
reach the Tacacs or Radius server through FXP0 by a static route.

Previously, there was no authentication when switching between RE's.

Thanks,

Greg Griffis
Data Network Engineer - Backbone & Peering
Cox Communications

-----Original Message-----
From: juniper-nsp-bounces at puck.nether.net
[mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Jeroen Valcke
Sent: Wednesday, January 26, 2005 12:05 PM
To: juniper-nsp at puck.nether.net
Subject: Re: [j-nsp] routing engine communication

On Tue, Jan 25, 2005 at 04:48:16AM +0100, Daniel Roesen wrote:
> On Mon, Jan 24, 2005 at 07:38:42PM -0700, Wayne E. Bouchard wrote:
> > Did I miss something? In 6.0, this immediately gives me a cli prompt
> > on the other RE but in 6.3, I get asked to authenticate. (And how
it's
> > trying to authenticate is beyond me because the settings are
> > "[ radius password ]" which clearly aren't being checked here..)
> 
> As far as I know it's a bug, already being fixed (at least in the
> current issued 6.4 daily build).

Would you happen to know when that fix was introduced?

Seems that it isn't solved yet in the lastest 7.0 release.

	jeroen at a-router> request routing-engine login
other-routing-engine
	EURPassword:
	Login incorrect
	login: xxxxx
	Password:

	--- JUNOS 7.0R2.7 built 2005-01-06 06:58:15 UTC

	{backup}
	xxxxx at a-router-BACKUP>

br,
-Jeroen-

-- 
Jeroen Valcke
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
http://puck.nether.net/mailman/listinfo/juniper-nsp