Failed login info: User Reached maximum session limit. UCSM 2.0(2q)

[vikas.k.srivastava]

Hi All ,

Very frequently on while trying to log in to the UCS after typing in the correct username and password we are gettign the following error message :

"Failed login info: User Reached maximum session limit."

This is temporarily resolved by the following process :

ucsm-1-A /system/services/web-session-limits # set per-user 256

ucsm-1-A /system/services/web-session-limits # commit-buffer

We are managing the system via DCNM , and in the sessions list we do see sessions coming in from the DCNM's IP Address .

What is the cause of this is and what could be the permanent fix ?

Regards

Vikas Srivastava

[padramas]

Hello Vikas,

Please check the current active user sessions on FI by

scope security

show user-sessions local

show user-sessions remote

Padma

[Robert Burns · Accepted solution]

Vikas,

This is a recently found issue (I just found this last week actually).  DCNM is query the UCSM too often and clogging up the 32 session limit.

There are two workarounds:

1) Log in via CLI and clear the sessions

2) Perform a management switchover

I'll be logging a bug on this later this week, but it appears to be a DCNM bug rather than UCSM.  UCSM clears stale sessions but DCNM is hitting it too often per hour.  See if you can configure DCNM to poll less requently - this might also help.

Once I have the bug ID I will update this thread.

Regards,

Robert

[Robert Burns]

Additionally, make sure you create a dcnm-user account, rather than using your admin account.  The DCNM account only needs to be ready only.

This way you can keep the default per-user session limit at 32, and always have sessions available for your admin/managment accounts.

Robert

[vikas.k.srivastava]

Thanks Robert , appreciate your help on this .

[dany.datacraft]

Hi Robert,

Do you happen to have the bug ID?

Best regards,

Dany

[arkadiy.d]

Very old thread but working with UCS Manager 3.1.3b still have the same issue and clearing the user-sessions doesn't help.

only after connect mgmt and "cluster lead a/b" solves the issue.

[malarivi]

Solution:

ssh admin@ucsm:

scope security

clear-user-sessions web

clear browser cache

close/open browser and login

Knowing how to adjust the user-session timeout would fix this, not increasing sessions (and memory heap usage). I've done the opposite and limited mine to 8/32