SAN Health Utility

Reply
New Member
Posts: 1
Registered: ‎06-19-2017

SANHealth fails in Audit - Most switches have a maximum concurrent login limit of 2 sessions per user ID

ACTIVITY LOG SAVE AT 19/06/2017 11:31:09

 

.......................................

AUDIT INFORMATION

LAUNCHED: 16  COMPLETED: 0 FAILED: 0

BUILD: Version 4.0.7c DC06092016

.......................................

START OF LOG ENTIRES

INFO-11:31:05 Log Cleared

INFO-11:31:05 SAN Health Version 4.0.7c with 16 Devices In Audit, 0 Completed and 0 Failed

INFO-11:31:06 Start Audit Button Clicked

INFO-11:31:06 Starting preflight check

CLOSE-11:31:06 WARNING The IP Address xx.xx.xx.xx  exists 4 times in the audit set.

CLOSE-11:31:06 Most switches have a maximum concurrent login limit of 2 sessions per user ID

CLOSE-11:31:06 If you are targetting multiple logical switches behind the same IP address

CLOSE-11:31:06 Please ensure that you are using multiple user IDs or assign additional

CLOSE-11:31:06 IP addresses to your logical switches

 

 

Question for the support and community.

 

Is there anyway to increase the login limit of 2 sessions per user ID, even if just for the time to run 'Brocade healthcheck' before setting it back to 2.  I really don't want to create multiple user ID ? 

 

Thanks

 

JK

 

 

 

Highlighted
Moderator
Posts: 77
Registered: ‎02-23-2004

Re: SANHealth fails in Audit - Most switches have a maximum concurrent login limit of 2 sessions per user ID

Hi JK,

 

I don't believe it is possible to circumvent the FOS limit of 2 concurrent active sessions per user ID.

 

The simplest answer is to use 2 built in existing accounts.... "admin" and "user".

 

However it may not be that simple as you must be auditing logical switches and you want to make sure whatever user account you have SAN health sign in under has access to the FID you are trying to audit. 

Quite often when people set up Virtual Fabrics and Logical Switches they also set up user accounts for management of each with home FIDs set against those user IDs.

You can either tell SAN Health what FID you are trying to target when connecting to that IP, or if no FID is specified SAN Health will land the switch session in whatever the user IDs home FID is set to

So while the simple answer is to just use two existing built in accounts, you might still have to think about what other accounts have been created or any other user/management structure that has been implemented.

 

 

Join the Community

Get quick and easy access to valuable resource designed to help you manage your Brocade Network.