Avatar of leadtheway
leadtheway
Flag for United States of America asked on

3650 Radius Configuration

Have a new 3650 configured from scratch, I'm trying to get ssh/radius authentication setup.  I went through a guide to setup on switch, I have several others that are working so i know the server is setup correctly, but when i try to use it on the switch, SSh works, and i can log in with local creds, but AD creds don't work. Thinking I'm missing something.  was hoping someone could take a look over my config and see if anything stands out.. Thanks
3650_scrub.txt
Switches / HubsSSH / Telnet Software

Avatar of undefined
Last Comment
arnold

8/22/2022 - Mon
arnold

Your issue is likely the encoding of the ad credentials you are using user@addomain
addomain\user?

Check what radius sees as far as a request.
Check your check items to see whether they pass.

If you have a test radius server to which you can have this switch send its radius packets without impacting the environment and without being inundated with other radius packets........... drop it into debug mode so you can see what comes in, what you sent and where the breakdown is.

Did you on the switch perform a test radius query?


potentially realm, or user from realm separation is where the issue is. DO you have other switches  in the environment to which you can compare this one?
leadtheway

ASKER
i have 15 other switches setup the same way that work.  attached is code of one that works see if anything jumps out

usually we just enter ad username/pass.  Don't need upn
3650_scrub.txt
arnold

What happens on the switch when you test radius auth. Double check whether the sw new switch is setup as a client on radius?
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
rwheeler23
arnold

Which port is your radius server on, the one that works does not specify auth/acct ports while the instigator does not points to the newer 1812/1813 ports. Suggesting perhaps that the default might be running on 1645/1646 ....
Remove on the new the added auth-port 1812 acct-port 1813 and see
Radius-server.....

Your http authentication on the new is set to local only ....

Still double check that this switch is configured as a client on the radius box.
leadtheway

ASKER
the switch is set as client, see attached, also see attached for the port config
Capture.PNG
Capture3.PNG
ASKER CERTIFIED SOLUTION
arnold

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
leadtheway

ASKER
how do i remove it, i tried to do a no statement to that line but it didn't work
⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
arnold

Try switching them to 1645/1646 respectively and see if that gets it to work.
leadtheway

ASKER
2nd_Floor_IDF_3650(config-radius-server)#address ipv4 192.168.9.9 auth
2nd_Floor_IDF_3650(config-radius-server)#$4 192.168.9.9 auth-port 1645 ac
2nd_Floor_IDF_3650(config-radius-server)#$9.9 auth-port 1645 acct-port 1646
%Server already exists with same address port combination.
leadtheway

ASKER
ok i got it fixed...not sure what was wrong, basically i just backed all the radius config out and mimic'd a working switch config.  Thanks for the help
Experts Exchange has (a) saved my job multiple times, (b) saved me hours, days, and even weeks of work, and often (c) makes me look like a superhero! This place is MAGIC!
Walt Forbes
arnold

Great to hear. You might want to take the time and make sure that your radius paths include both 1645/1812 and 1646/1813 including the local server firewall if any.

...