When our primary DNS server went down today, and our log-in server began
to perform the DNS(as it is the secondary DNS server), radius
authenticating stopped logging in users after 30 minutes.
When we rebooted this server(the Radius server now doing DNS as well) it
started logging in users again, as well as DNS, but after 30 minutes just
stopped logging in users again. The dial-in users got the message " You
have been disconnected from your ..." , and if I do a show sessions, I do
not see the User login name or password, and it does not connect, it just
goes from username to disconnected. Its like radiusd isn't there anymore!
When we finally got our primary DNS server back up then the Login server
kept working as well.
If you can help us solve this mystery you will be a hero!
We had the pm2e30's set for alternate radius server (the one that went
down for primary DNS), but when it went down we took the alternate DNS and
accounting IP addresses out. Is it possible that even though we took them
out, the PM's still think they are there, and when the load got too heavy
for the main server, it went to the alternate radius server that was down?
Do you need to reboot the PM's to really get the alternate addresses out?
Do you have to actually power the PM down to really get them out?
Thank you in advance for you help!
BoB Kerman, JVLNET by Electrolarm