- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Onboard Administrator / LDAP logon limit - workaro...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-08-2011 01:04 PM
02-08-2011 01:04 PM
Onboard Administrator / LDAP logon limit - workaround??
Ed had a customer question:
******************
I have a customer asking the following..
"LDAP allows one user logon to the OnBoard Administrator; local user logons are not limited
· customer has a 2-node cluster that they are in the process of implementing
· cutomer is experiencing what they believe to be contention with LDAP user attempting to logon to the OnBoard Administrator simultaneously via their orchestration scripts
· One node appear to have a successful logon; the other node fails
· customer is wondering if there is a configuration change to the blade environment that will enable more than one concurrently LDAP logon
· If not, they will need to modify a substantial number of scripts (some of which are currently operational in the field) and change the LDAP user to a local user
Any thoughts please..?
Thanks,
********************
Monty responded:
***********************
Yes, the OA limits each LDAP user account to only one login – if they are logged into the GUI, that session is closed if they also open a CLI session and vice-versa. This behavior is not configurable.
Workarounds which will not disturb current LDAP user sessions include:
- Use an OA local user account for the scripting commands
- Use a different LDAP user account for the scripting commands.
*********************
Any other comments or suggestions?? Seemed to be a lot of confusion around this one.