- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Adding new VC modules to VCEM - worried about MAC/...
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
05-02-2014 10:18 AM
05-02-2014 10:18 AM
Hello,
I've been vetting this process but have no way to test it other than to do it. The VCEM 7.2 guide (we're using 7.3) has not direct scenario that I can find. I primarily don't want to lose my WWN's and have to rezone..
Config:
2 identical c7000 g2 with Flexfab modules at F/W 4.10
BL460G8's running esxi 5.5
adding Flex10-D modules to expand I/O capability.
So here are some possible scenarios's. My main concern is when I create a new domain group with a new logical range of WWN's/MAC's I'm not going to be able to move my server profiles from the old domain group over to the new DG because their range is incompatible.
I got these ideas from an HP source but he had not vetted them.
Steps (to be validated);
- Unassign the profiles from one enclosure
- Remove the enclosure from the group/VCEM
- Add the new VC modules and cable accordingly
- Upgrade/downgrade the VC firmware of the new modules to match the existing firmware – if required
- Add/change any networking to accommodate the new modules
- Add enclosure to VCEM and create a new VCEM group
- Edit the profiles to use the new networks on the new modules
- Assign the profiles in the same bays as they were before the change
Alternatively….
You may also be able to do the following;
Steps (to be validated);
- Remove the enclosure from VCEM and keep the profiles assigned
- The MAC/WWN’s will not change, you will retain those addresses and tell VCEM that you exported them, it will map them out so they won’t be reused.
- Add the VC modules and cable accordingly
- Upgrade/downgrade the VC firmware of the new modules to match the existing firmware – if required
- Add/change any networking to accommodate the new modules
- Edit the profiles to use the new networks on the new modules
- Add the enclosure to VCEM and create a new VCEM group
Any experience with this scenario?
Thanks,
Ron
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-07-2014 04:15 PM
05-07-2014 04:15 PM
SolutionSo it worked like a charm. The key is VCEM pools MAC's and WWN's at the VCEM level and not at the VC Domain group level like I was thinking.
The old issue with adding mezz cards and PCI numbering came back to bite me. Just had to add more unused NIC's to the profiles.