Page 1 of 1

RADIUS service monitoring wizard

Posted: Thu Jul 23, 2015 1:58 pm
by ManojNamdev
Dear Team,

How we can monitor RADIUS server, when we are using Monitoring Wizard its asking for following things:

Server Options

Secret: ???????????

The shared secret to use when logging into the RADIUS server.


Username: ??????????

The username used to login to the RADIUS server.


Password: ??????????
The password used to login to the RADIUS server.

Port: ?????????

The port number the RADIUS server runs on.
After giving this input which mentioned above
[pap] login attempt with password "¿³?òd?~?¢??>titý"

[pap] Using clear text password "nagios"

[pap] Passwords don't match

Please how we can monitor RADIUS Server ........?

Also I want to give some more input on this query:
From RADIUS server side we have checked following things please look into it also

[root@radius2 tmp]# ./check_radius_adv -r localhost -u nagios -p nagios -s testing123 -c 1812 -v

Using the following information
-------------------------------
username: nagios
password: nagios
shared secret: testing123
server: localhost
path of attributes file :

CRITICAL: Access REJECT. (code = 3) | rtt=1.0035 rttms=1003.5219


But when we are running radtest command, passwords are matching without any error.

Re: RADIUS service monitoring wizard

Posted: Fri Jul 24, 2015 9:53 am
by ssax
This error (if you're running it from your radius server) CRITICAL: Access REJECT. (code = 3) leads me to believe the nagios user you are trying to authenticate to your radius server with is not allowed for radius authentication.

Re: RADIUS service monitoring wizard

Posted: Thu Jan 28, 2016 8:57 pm
by andarnold
I think that this thread https://support.nagios.com/forum/viewto ... us#p157549 provides a good workaround for checking RADIUS servers.

HTH,
Derek

Re: RADIUS service monitoring wizard

Posted: Fri Jan 29, 2016 10:42 am
by rkennedy
andarnold wrote:I think that this thread https://support.nagios.com/forum/viewto ... us#p157549 provides a good workaround for checking RADIUS servers.

HTH,
Derek
Thanks @andarnold! Yes, this looks to be the same issue. I had done a lot of testing and concluded it was how the password is sent. Try the work around in that thread mentioned by Scott.