I am continuously hitting the below error when i am creating volumes.
The login session of the storage system has expired.
Any idea how to fix this issue?
Which application are you using? SNM2 or HCS or SN.
Which storage array are you working with?
I am using HCS 7 version and the type of array is AMS2100.
Any specific reason why i am facing this issue. I am the only user using this system but not sure.
As per the Hitachi error messages guide,
"A forced logout might have been executed because the account was invalidated. Make sure such an operation was not executed performed on the storage system by another
user. If no such operation was executed, refresh the storage system, and then try again."
Can i get any update on this issue?
I am also experiencing this error when using SNM2. I need to relog again and again when doing configuration. Please help.
Saver Urm Arnold Decal
Ok, two things to note here:
1. On Modular arrays (HUS/AMS) you can only have 1 user with modify permission logged into the array. If a user with modify permission is already logged in and another tries to login with modify permission, the original users session is invalidated. It looks something like this:
a. User 1 logs in (with modify permission)
b. User 2 logs in (takes modify permission)
c. user 1's session is invalidated
2. When the root user logs in all users accounts are logged out
a. user 1 logs in (with modify permission)
b. root user logs in
c. user 1 session is invalidated.
(d. no user can login with modify permission until root logs out)
Now all services use login accounts, so it would be HCS, Hi-Track (unlikely on user evers) of even a script causing the session to invalidate. You can determine this by looking at the audit log to see if new logins are occurring.
Thank you Cris Danci, as always!
Saver Ur and Arnold Decal, I hope you received the information you needed.
Please let us know if things are resolved for you.
Since it is by design, it won;t solve our problem but this information is certainly useful as it tells us how to use the login sessions in case multiple users are using the application.
By design it works with multiple users. Sounds like an initial setup issue with something incorrectly using the root account.
Do you have any steps to troubleshoot this problem?
In SNM2 go to security-> audit logging-> Show internal log
Determine what is logging into the array (from which IP address) and use that to determine which service of script might be the cause of the problem.
Retrieving data ...