[Problem Description]
Logging in to DeviceManager fails, and the message "Maximum number of users has been reached." is displayed.
Log in to the CLI and enter the minisystem mode.
[Fault Symptom]
You cannot log in to the storage device for management and configuration, and host services are not affected.
[Cause]
The default maximum number of sessions on the storage device is 32 and the number of connections to the storage device exceeds 32.
[Location Method]
1. When you log in to DeviceManager, a message is displayed indicating that the number of users has reached the maximum.
2. Log in to the CLI and go to the minisystem. The system displays "Error Code: 0x40403288".
[Solution]
1. Emergency measures
Method 1:
Log in to the CLI and enter the minisystem mode. Run the om_show_omm_info.sh –q command (supported in V300R003C10 and later versions) to view the IP address of the client that occupies sessions on the storage device. Log out of the client that does not need to be connected to the storage device and release session resources.
Method 2:
1)Run the showsysstatus command in the minisystem to determine which controller is the main control board.
2) Log in to the main control board and run the ps -C aa command in the minisystem to check the PID of the AA process responsible for session connection. The PID is 2839 in the following figure.
3) Run the kill -9 PID command on the master minisystem to restart the aa process. This operation will log out all users connected to the storage device (it has no impact on the storage device).
2. Solution
1) After logging in to the storage device, log in to the CLI and check the maximum number of sessions (32 by default).
2) Change the maximum number of sessions to 256 (supported in V300R003 and later versions).
[Post-Recovery Check]
1. You can log in to DeviceManager and CLI.
