topic Re: Secure-ACS: Special RADIUS-Attributes for Enterasys E7 in Network Access Control

Secure-ACS: Special RADIUS-Attributes for Enterasys E7

rolf.fischer_2 — Mon, 11 Mar 2019 00:02:22 GMT

Hi,

we were running a pretty old version of the Cisco Secure ACS for AAA our network devices.

Unfortunately the server crashed an we had to install and set it up with a new server.

Using TACACS+ for our Cisco devices works fine.

We have a couple of switches made by a vendor called Nexans, which only support RADIUS - this works fine too.

Furthermore we still have some Enterasys E7 and with those RADIUS doesn't work at all.

Sniffering the packets, everything looks good.

With the old server it worked well.

Does anybody know if there are special configurations (e.g. attributes) when configuring an ACS for Enterasys RADIUS-Clients?

Thanks,

Rolf

Re: Secure-ACS: Special RADIUS-Attributes for Enterasys E7

Yudong Wu — Wed, 31 Mar 2010 06:04:30 GMT

try this

attribute [011] Filter-ID to "Enterasys:version=1:mgmt=su:"

Re: Secure-ACS: Special RADIUS-Attributes for Enterasys E7

rolf.fischer_2 — Wed, 31 Mar 2010 07:23:30 GMT

Great, it works!

You saved my day 😉

Secure-ACS: Special RADIUS-Attributes for Enterasys E7

engahmed1975 — Fri, 22 Mar 2013 09:23:01 GMT

We have this configuration and works fine with our network and associate in a good manner also the policy which we have configured it on Enterasys in this way

Filter-Id===>

Enterasys:version=1:mgmt=su:policy=Administrator

After we make the update to ACS 5, the "ASA" consider this filter-id as access-list so it consider the field after the filter-id as the name of the acl, and diconnect the VPN connection.

Could soneone help me to resolve that.