DComTalk.com

Fischer Karsten · Guest

Hi,

i`ve got the following problem: A Bay 350-12 is configured to do radius authentication to IP X. There is a radius-server running at IP X. It sends out a radius-access-accept, but the switch displays
"No response from RADIUS server(s).", so i can't login.

I`ve captured the conversation with tcpdump: (The Bay is IP Y)

11:48:30.240086 Y.2048 > X.1812: rad-access-req 55 [id 81] Attr[ NAS_ipaddr{Y} Pass Service_type{Administrative} [|radius]
11:48:30.240684 X.1812 > Y.2048: rad-access-accept 26 [id 81] Attr[ Service_type{Administrative} ] (DF)
11:48:32.260127 Y.2048 > X.1812: rad-access-req 55 [id 81] Attr[ NAS_ipaddr{Y} Pass Service_type{Administrative} [|radius]
11:48:32.260392 X.1812 > Y.2048: rad-access-accept 26 [id 81] Attr[ Service_type{Administrative} ] (DF)
11:48:34.275526 Y.2048 > X.1812: rad-access-req 55 [id 81] Attr[ NAS_ipaddr{Y} Pass Service_type{Administrative} [|radius]
11:48:34.275781 X.1812 > Y.2048: rad-access-accept 26 [id 81] Attr[ Service_type{Administrative} ] (DF)

Any Ideas?

TIA,

Karsten

Mike Farnham · Guest

Yes - same problem here. If you run a continuous ping on your 350-12
switch (ping -t xxx.xxx.xxx.xxx) and then in a separate window trying
getting into it with Radius - I think you will see the connection stop
pinging for a short time and then come back. Using Radius on the 350
seems to make it reboot!

If this is the case - it's a code issue with the 350. I had to send
ours back into Nortel to have them fix it and update the code for me.
Most 350's are discontinued and if you can go with the 450 series you
might want to - but make sure it is up to 4.5.0 code (released around
6/8/04) because they do the same thing (not all of them but some and
again, it's a code thing)

Hope this helps - let me now your progress.
- Mike

Fischer Karsten <karstenf@nexgo.de> wrote in message news:<2obed4F8q5a6U1@uni-berlin.de>...

Paul Tichy · Guest

------------------------
From: Mike Farnham <mike.farnham@co.manatee.fl.us>
Subject: Re: radius & baystack 350-12
Date: 17 Aug 2004 11:27:59 -0700
Location: news://news.houston.sbcglobal.net/comp.dcom.sys.bay-networks/af3623de.0408170935.58a70a86@posting.google.com
To: "comp.dcom.sys.bay-networks" <@news:comp.dcom.sys.bay-networks@news.houston.sbcglobal.net>

Yes - same problem here. If you run a continuous ping on your 350-12
switch (ping -t xxx.xxx.xxx.xxx) and then in a separate window trying
getting into it with Radius - I think you will see the connection stop
pinging for a short time and then come back. Using Radius on the 350
seems to make it reboot!

If this is the case - it's a code issue with the 350. I had to send
ours back into Nortel to have them fix it and update the code for me.
Most 350's are discontinued and if you can go with the 450 series you
might want to - but make sure it is up to 4.5.0 code (released around
6/8/04) because they do the same thing (not all of them but some and
again, it's a code thing)

Hope this helps - let me now your progress.
- Mike

Fischer Karsten <karstenf@nexgo.de> wrote in message news:<2obed4F8q5a6U1@uni-berlin.de>...

	DComTalk.com Forum Index -> Bay Networks	All times are GMT
Page 1 of 1