Netlogin unwanted MAC is authenticated locally
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎08-10-2017 11:43 AM
Hi,
I'm a little bit confused:
We are using netlogin for a year and it's working like you would expect it:
A unknown MAC address shows up on the switch, is getting blocked and reported in EMS.
But now, I have a unwanted MAC address, which is authenticated locally, but is reported as rejected in EMS - but the switch authenticates the user and assign to the granted VLAN.
Here is the netlogin config:
I'm happy for feedback
Best Regards
Chacko
I'm a little bit confused:
We are using netlogin for a year and it's working like you would expect it:
A unknown MAC address shows up on the switch, is getting blocked and reported in EMS.
But now, I have a unwanted MAC address, which is authenticated locally, but is reported as rejected in EMS - but the switch authenticates the user and assign to the granted VLAN.
Here is the netlogin config:
#Radius is working, the switch is a X450e-48p (stacked) with EXOS 15.3.2.11
# Module netLogin configuration.
#
configure netlogin vlan AUTH
enable netlogin mac
configure netlogin add mac-list ff:ff:ff:ff:ff:ff 48
configure netlogin mac timers reauth-period 7200
enable netlogin ports 1:10-48,2:10-2:48 mac
configure netlogin ports 1:10-48,2:10-2:48 mode mac-based-vlans
configure netlogin ports 1:10-48,2:10-2:48 no-restart
enable netlogin authentication service-unavailable vlan ports 1:10-48,2:10-2:48
configure netlogin authentication service-unavailable vlan office ports 1:10-48,2:10-2:48
I'm happy for feedback
Best Regards
Chacko
10 REPLIES 10
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎08-16-2017 06:04 AM
Hi Chacko,
Thanks for getting back on this, good to see that the issue is not seen.
Thanks for getting back on this, good to see that the issue is not seen.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎08-16-2017 06:04 AM
Okay, I revoke the last one.
The issue is still active, even with 15.3.5.2-patch1-14.
I will open up a GTAC case with our external partner
BR
Chacko
The issue is still active, even with 15.3.5.2-patch1-14.
I will open up a GTAC case with our external partner
BR
Chacko
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎08-15-2017 06:10 AM
Hi Chacko,
I would request you to pursue this issue with GTAC case as this needs further investigation.
15.3 version has already reached end of engineering hence it would be best to upgrade to the latest patch in 15.3 (15.3.5.2-patch1-14) and check if the issue is getting resolved before opening up the ticket.
I would request you to pursue this issue with GTAC case as this needs further investigation.
15.3 version has already reached end of engineering hence it would be best to upgrade to the latest patch in 15.3 (15.3.5.2-patch1-14) and check if the issue is getting resolved before opening up the ticket.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎08-15-2017 06:10 AM
Hi Karthik,
I updated the switch over night and so far, the problem hasn't occured again.
I hope there is no general netlogin problem in this software release - but the summit *50 will be out of contract next year anyway.
Thanks for your help
Best Regards
Chacko
I updated the switch over night and so far, the problem hasn't occured again.
I hope there is no general netlogin problem in this software release - but the summit *50 will be out of contract next year anyway.
Thanks for your help
Best Regards
Chacko
