Why does the log off operation fail for S5500T?

2

A mapped LUN is mounted on the AS and is being accessed.

If yes, stop the ongoing services of the LUN on the AS, delete the mapping between the LUN and the AS on the ISM, and then perform the log off operation again.

Other related questions:
Method used to log off the controller
You can log off the controller as follows: 1. Fault location and rectification a. You need to log off the controller when changing boards. b. You need to log off the controller when rebooting the controller. 2. Solution a. Querying the system status Check the master and slave controllers in CLI mode by logging in to the CLI mode and running the showmaster command. If primary is displayed, the controller is a master controller. Perform the following steps. If secondary is displayed, the controller is a secondary controller. Switch to its peer controller and then perform the following steps. b. Logging off the controllers If you want to log off controller B, log in to the CLI mode and run the following command: OceanStor: admin> offline -c b If you want to log off controller A, run the following command: OceanStor: admin> offline -c a c. Confirming that the controller is logged off Go to the man-machine language (MML) mode of the storage system, enter sys status to check whether only one controller is running. In the following information, double is single and normal is offline. If one controller is running and the peer controller is offline, the log-off is successful. spu ui>sys status Double Or Single : [ double ] Master Or Slave : [ master ] Local Controller Status : [ normal ] Peer Controller Status : [ normal ] System Running Status : [ normal mode ]

How can command operation logs be displayed in the log buffer of an AR
By default, only warning logs are displayed in the log buffer. Command operation logs are at the notifications level, which is lower than warning. Therefore, command operation logs will not be displayed in the log buffer. To view command line operation logs in the log buffer, perform the following operations: 1. Run the system-view command to enter the system view. 2. Run the info-center source default channel logbuffer log level notifications command to allow logs of the notifications level to be displayed in the log buffer.

After the version is upgraded, why the administrator fails to log in
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.

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