Trouble with vty when console works fine

sfmta-cisco — Mon, 11 Mar 2019 03:27:16 GMT

I've done a lot of digging around and can't seem to find any references to my specific problem:

I have 3750Xs (12.2) that authenticate against Radius for both console and vty access, that all works fine.

So I took that same working config and pasted it into a new ME3400 (12.2), and for console access the authentication is working as expected, but for vty access I'm getting "authentication failed." I don't know what I'd expect to find on the server side of things as the successful console authentication kinda tells me that's all set up correctly. Doesn't seem to be many options I can add to the vty piece of config either, so I'm really stumped. What might I be missing that would make vty authentication behave differently from console authentication on an ME3400, while not being the case on a 3750X?

username admin password password

aaa new-model

aaa group server radius Auth-Radius

server 1.2.3.4 auth-port 1645 acct-port 1646

aaa authentication login default group Auth-Radius local

aaa authorization exec default group Auth-Radius local

aaa session-id common

ip radius source-interface Vlan24

radius-server host 1.2.3.4 auth-port 1645 acct-port 1646 key Key-Radius

line vty 5 15

Trouble with vty when console works fine

Jatin Katyal — Tue, 21 May 2013 19:32:51 GMT

Few questions:

1.] What do you see on radius server logging section when you try a connection from vty?

2.] Can we have debugs from the device

debug aaa authentication

debug radius

3.] show run | beg line vty

Jatin Katyal

- Do rate helpful posts -

topic Trouble with vty when console works fine in Network Access Control

Trouble with vty when console works fine

Trouble with vty when console works fine