- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- HP Pre-defined Address question
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
08-19-2011 06:32 AM
08-19-2011 06:32 AM
HP Pre-defined Address question
Wim had a customer question:
******************
A large customer is afraid to run out of the number of 64 pre-defined MAC and WWN address ranges. He is not using VCEM at the moment.
Are there any plans to increase that number in the near future or is the only possibility to use VCEM or user defined ranges?
********************
Jon replied:
********************
I cannot answer futures questions, but you can further stretch the pre-defined ranges by using enclosure stacking, upto 4 enclosures per domain. So we are then talking about 256 enclosures instead of 64 single domain enclosures. (Some design limitations apply.)
Using double density blades would maximize the number of physical blades per enclosure; alternatively, heavily built full height blades with multiple, multiport mezzanine adapters could be used in conjunction with many virtual machines accessing many LANs and SANs. (This requires capacity planning.) VLANs and NPIV may be used to further stretch the use of each physical MAC and WWN used through Virtualization.
Beyond that, we are talking about the efficiencies using a global VCEM address pool with little or no waste of address space. Given the human labour involved with managing hundreds of enclosures separately and the design limitations associated with using stacking (some interconnect population consistency is required within the domain), the cost to benefit using VCEM becomes increasingly appearent, as does other technologies such as CloudSystem Matrix, which leverages VCEM.
******************
Any other comments or suggestions?