Troubleshooting guide for TACACS+ Authentication Fails on Omada Switch

TL-SG2008P , TL-SG3452X , SG3452XMPP , SG5452XMPP , TL-SG2218P , TL-SG2424P , TL-SG3452XP , TL-SG2016P , SG3428XPP-M2 , SG3428XMPP , TL-SG2210P( V3.20 V3.26 V4 V5 V5.6 ) , SG2210MP( V5.6 ) , TL-SX3008F , TL-SL2428P( V4 V4.20 V4.26 V5 V6 V6.6 ) , TL-SX3016F , SG2218 , SG3428 , TL-SG3452P , TL-SG3428X , SG3218XP-M2 , SL2428P( V4 V4.20 V4.26 V5 V6 V6.6 ) , TL-SG3428X-M2 , SG3210X-M2 , TL-SG3428XF , TL-SG2210MP , SG3428X-M2 , SG3452 , SG3210( V3 V3.6 ) , TL-SG3428XPP-M2 , SX3032F , SG3452X , SG3210XHP-M2 , TL-SG3210XHP-M2 , SG2008( V3 V3.6 V4 V4.6 ) , TL-SG2428P , SG3428XF , SG2005P-PD , SX3008F , SG3428MP , SG3428X , SG3452P , SX3016F , TL-SG3428X-UPS , SX6632YF , SG2218P , SG2428P , SG2008P , SG3452XP , TL-SG3428 , TL-SG2218 , SG5452X , SG2210P( V3.20 V3.26 V4 V5 V5.6 ) , SG2016P , TL-SG3428MP , TL-SG2008( V3 V3.6 V4 V4.6 ) , TL-SG3452 , TL-SG3210( V3 V3.6 ) , TL-SX3206HPP , SG3428XMP , TL-SG3428XMP , SX3206HPP
Recent updates may have expanded access to feature(s) discussed in this FAQ. Visit your product's support page, select the correct hardware version for your device, and check either the Datasheet or the firmware section for the latest improvements added to your product. Please note that product availability varies by region, and certain models may not be available in your region.
Contents
Objective
If you encounter the issue of devices being unable to authenticate successfully after configuring the TACACS+ feature on the Omada Switch, you can follow the troubleshooting steps below to resolve the problem.
Requirements
- Omada Smart, L2+ and L3 switches
- Omada Controller (Software Controller / Hardware Controller / Cloud Based Controller, V5.9 and above)
Introduction
To enhance network security, you can configure TACACS+ authentication to restrict client access to the switch through the SSH protocol or Console interface.
Troubleshooting Steps
Step 1. Check the network connectivity.
Ensure the network link between the switch and the TACACS+ Server is normal, and also ensure that the authentication port (usually 49, but there are exceptions) is enabled by the TACACS+ Server.
Step 2. Check that the username and password used for authentication are correct.
Step 3. Check the configurations of TACACS+ Server and AAA.
Go to Tools > Terminal, select Switch as the Device Type, select the switch that has TACACS+ configured, and then click Open Terminal.
Use the following command to view information about the configuration:
Switch>en
Switch#show run
Find the following configuration information related to TACACS+ Server and AAA. Make sure that the IP address, port number, and key of the TACACS+ Server are correct. "test" is a custom login method that specifies TACACS+ authentication as the first priority.
Find the following configuration information and make sure that the authentication method for SSH/Console login is specified as “test”.
Note: The switch is not accessible using telnet after being adopted by Contrller.
Step 4. Check if ACL, IMPB, MAC Filtering, or other security policies are configured.
Conclusion
We have now completed the troubleshooting of TACACS+ authentication failure.
Get to know more details of each function and configuration please go to Download Center to download the manual of your product.
Related FAQs
¿Es útil esta pregunta frecuente?
Sus comentarios nos ayudan a mejorar este sitio.
¿Cuál es tu preocupación con este artículo?
- Insatisfecho con el producto
- Muy complicado
- Titulo confuso
- Eso no aplica a mi
- Demasiado vago
- Otro
Gracias
Agradecemos sus comentarios.
Haga clic aquí para comunicarse con el soporte técnico de TP-Link.
Este sitio utiliza cookies. Si continúa navegando por el sitio, acepta el uso que hacemos de las cookies. No volver a mostrar Más información .
Your Privacy Choices
Este sitio utiliza cookies. Si continúa navegando por el sitio, acepta el uso que hacemos de las cookies. No volver a mostrar Más información .
Cookies basicas
TP-Link
SESSION, JSESSIONID, accepted_local_switcher, tp_privacy_banner, tp_privacy_base, tp_privacy_marketing, tp_top-banner, tp_popup-bottom, tp_popup-center, tp_popup-right-middle, tp_popup-right-bottom, tp_productCategoryType
Youtube
id, VISITOR_INFO1_LIVE, LOGIN_INFO, SIDCC, SAPISID, APISID, SSID, SID, YSC, __Secure-1PSID, __Secure-1PAPISID, __Secure-1PSIDCC, __Secure-3PSID, __Secure-3PAPISID, __Secure-3PSIDCC, 1P_JAR, AEC, NID, OTZ
Zendesk
OptanonConsent, __cf_bm, __cfruid, _cfuvid, _help_center_session, _pendo___sg__.<container-id>, _pendo_meta.<container-id>, _pendo_visitorId.<container-id>, _zendesk_authenticated, _zendesk_cookie, _zendesk_session, _zendesk_shared_session, ajs_anonymous_id, cf_clearance
Cookies de análisis y marketing
Las cookies de análisis nos permiten analizar sus actividades en nuestro sitio web para mejorar y adaptar la funcionalidad de nuestro sitio web.
Nuestros socios publicitarios pueden configurar las cookies de marketing a través de nuestro sitio web para crear un perfil de sus intereses y mostrarle anuncios relevantes en otros sitios web.
Google Analytics y Google Tag Manager
_gid, _ga_<container-id>, _ga, _gat_gtag_<container-id>
Google Ads y DoubleClick
test_cookie, _gcl_au