Loading...
Loading...
SANnav logs below authentication failed for all the configured users with "Name does not resolve", indicating the hostname mapping is incorrect or not present in /etc/hosts/ file (configured during SANnav installation), root login works: mw-consolidated-2 - [INFO] 2025-05-21 03:29:58.607 [http-nio-13004-exec-6] com.brocade.dcm.authentication.server.shiro.DCMRealmAuthenticator - Login status for user XXX_admin after authentication and user role check: true Is locally Authenticated true mw-consolidated-2 - [INFO] 2025-05-21 03:29:58.732 [http-nio-13004-exec-6] com.brocade.dcm.authentication.server.util.AuthenticationUtil - Building User Profile. AOR List for user XXX_admin is:[] mw-consolidated-2 - [ERROR] 2025-05-21 03:29:58769 [http-nio-13004-exec-6] com.brocade.dcm.authentication.server.shiro.DCMRealmAuthenticator - Authentication failed for user XXX_admin authType Local Database. mw-consolidated-2 - [ERROR] 2025-05-21 03:29:58.771 [http-nio-13004-exec-6] com.brocade.dcm.authentication.server.controller.AuthenticationController - Login failed! Authentication exception occurred for client 172.XX.XX.XX org.apache.shiro.authc.AuthenticationException: nclsananv240: nclsananv240: Name does not resolve.
If the <SANnav IP><Space> <SANnav Hostname> mapping is incorrect or not present in the /etc/hosts file and the DNS server is not performing the hostname resolution, the SANnav user cannot log in to the SANnav server. SANnav uses the hostname that is defined in the /etc/hosts/ file for the hostname resolution during installation and validates the same hostname while logging in to SANnav from the browser. If the hostname entry in the /etc/hosts/ file is removed or modified, the hostname does not match with the hostname that is referred in SANnav. Check the entries in the /etc/hosts file: Run the command # hostnamectl to confirm the hostname and compare: Clarify if the user has done any changes on the DNS server that could trigger this issue. Since the hostname does not match it prevents login. If there is a mismatch, the user must follow the recovery steps.
User must add or revert to the old hostname entry in the /etc/hosts/ file, which was used during the SANnav installation and restart SANnav services. Maintain the same hostname in the file " /etc/hosts/ " and the command " hostnamectl " output to resolve the login failure issue. To set the system hostname, follow the below steps: Login into SANnav server console Run hostnamectl to set-hostname command: # hostnamectl set-hostname <hostname> //Command to set hostname Example: [root@MPS-sannav-portal-v231-test1 bin]# hostname set-hostname MPS-sannav-portal-v240-test1 Restart the SANnav services using ./restart-sannav.sh script under /sannav-home/portal_2.4.0_<build-number>/bin Once all the services are up, run the # hostnamectl command to confirm that the hostname is updated: If the hostname mapping is correct, the only option is to do a re-installation of SANnav
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.