- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Re: IP address restriction Onaboard Administrator
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
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
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-20-2009 01:08 AM
тАО02-20-2009 01:08 AM
I'm using firmware 2.32 and can't find anything in the documentation about the limitations.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-20-2009 03:17 AM
тАО03-20-2009 03:17 AM
Re: IP address restriction Onaboard Administrator
You don't mention whether you are using Virtual Connect, so I dont know if this is relevent. But it might give you a direction to investigate.
Dave.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-20-2009 09:59 AM
тАО03-20-2009 09:59 AM
SolutionI do agree that limiting the number of entries to 5 is a design flaw. What I think I would do in your case is to designate one (or two) of the enclosures as primary connection points. Consider this example:
enc_1
enc_2
enc_3
enc_4
admin_srv_1
admin_srv_2
enc_1 is my primary connection point to all enclosures, enc_2 is my backup connection point to all enclosures.
On enc_1, add trusted entries admin_srv_1, admin_srv_2, enc_2.
On enc_2, add trusted entries admin_srv_1, admin_srv_2, enc_1.
On enc_3, add trusted entries enc_1, enc_2.
On enc_4, add trusted entries enc_1, enc_2.
This way, you access the admin servers, go through enc_1 or enc_2, and can reach any enclosure. Since you have space you can even add admin_srv_1/2 IPs to enc_3/4 so that you can access them individually should the need arise (link cable fail for instance).
Good luck!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-23-2009 02:34 AM
тАО03-23-2009 02:34 AM
Re: IP address restriction Onaboard Administrator
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-23-2009 10:33 AM
тАО03-23-2009 10:33 AM
Re: IP address restriction Onaboard Administrator
Which is the issue you have.
I'm wondering if the new OA module with KVM will have the same 4 enclosure restriction.
I think the reason for having the ability to see more than one enclosure was as has been mentioned ... to see all the enclosures in a rack from one screen.