After the version is upgraded, why the administrator fails to log in

1

There is difference between versions, so the administrator cannot log in after the version is upgraded.
To differentiate default authentication domains that common users and administrators belong to, V100R003 and later versions add the default domain default_admin for administrators. In V100R002, all users belong to the default domain default. In practice, users often use the default domain default. When the switch is upgrade from V100R002 to a later version, administrators use the default domain default_admin. The configuration of the default domain default_admin is different from that of the default domain default, so authentication fails and the administrator fails to log in.
You can use any of the following methods to solve the problem:
--Run the domain default admin command in the system view to change the administrator domain to default.
--Copy the configuration of the default domain default to the default domain default_admin.
--Enter the user name username@default during login. Ensure that the undo hwtacacs-server user-name domain-included or undo radius-server user-name domain-included command has been executed in the authentication template view.

Other related questions:
How to change the administrator login password on the U1900?
1. Run the onfig modify loginpassword command to change the password for entering the View mode. 2. Run the config modify enablepassword command to change the password for entering the enable view. Enter the current password as prompted and then enter the new password during command execution.

Why Google browser can not log on SMC2.0 when V100R003C10SPC200 version of SMC2.0 upgrade to V500R002C00 version
There are two ways to solve this problem: 1 Uninstall windows system patch KB2992611. 2 Complete all patches of the windows system. Please log in http://support.huawei.com/Enterprise, choose "Support>Telepresence and Videoconferencing>Videoconferencing Infrastructure>SMC2.0", select the appropriate version Release Notes to see the patch.

What Do I Do If the Organization Administrator Cannot Log In to the ServiceCenter Administrator Portal After ServiceCenter Is Upgraded to 3.0.5 or Later
【Product�? ServiceCenter 【Version�? 3.0.5 【Fault Type�? System fault 【Symptom�? After ServiceCenter is upgraded to 3.0.5 or later, the organization administrator cannot log in to the ServiceCenter administrator portal. 【Fault Locating�? According to the release notes, ServiceCenter 3.0.5 or later version does not allow the organization administrator to log in to the ServiceCenter administrator portal. 【Root Cause�? In ServiceCenter 3.0.5 or later version, the organization administrator can only log in to the ServiceCenter tenant portal. For details, see the ServiceCenter 3.0.5 release notes. 【Solution�? None ----End

The administrator cannot pass authentication if the administrator's authentication mode is changed to RADIUS authentication on an S series switch
The administrator cannot pass authentication if the administrator's authentication mode is changed to RADIUS authentication. For S series switches (except the S1700), such an authentication failure occurs because the entered user name does not contain a domain name. You need to check whether the user name on the authentication server contains a domain name. - If the user name on the authentication server contains a domain name, run the radius-server user-name domain-included command in the RADIUS server template view or run the hwtacacs-server user-name domain-included command in the HWTACACS server template view. - If the user name on the authentication server does not contain a domain name, run the undo radius-server user-name domain-included command in the RADIUS server template view or run the undo hwtacacs-server user-name domain-included command in the HWTACACS server template view.

Why SMC2.0 cluster upgrade failed
The current environment for the cluster environment, SQL SERVER cluster login verification using its own user name and password for authentication. In the installation process, the use of a trusted connection to lead to this problem. The use of the database user name and password to re upgrade in node 1 can solve this problem.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top