- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Removing VC Enterprise Manager (VCEM) lock from VC...
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
03-22-2013 10:54 AM
03-22-2013 10:54 AM
Removing VC Enterprise Manager (VCEM) lock from VCM and keeping the configuration
Aleksandar was having management issues:
******************
We are having a VCEM machine that manages several enclosures. Unfortunately the HP SIM become unresponsive and none of the mx commands or the web server function and we opened a case.
If the troubleshooting takes a lot of time, we need to be able to manage the enclosures and the locks might be removed forcefully.
Configuration:
- Enclosures were configured with HP Pre-Defined ranges
- Some profiles are created after VCEM is implemented with VCEM managed WWN/MAC ranges. Sever serial number is left to factory.
According to the VC CLI documentation, we can break the lock on the VCM via the following commands:
remove external-manager [-quiet] [UserName=<username>]
[MacType=<Factory-Default| User-Defined>] [MacStart=<MAC
address>] [MacEnd=<MAC address>]
[WwnType=<Factory-Default|User-Defined>] [WwnStart=<WWN
address>] [WwnEnd=<WWN address>]
[ServerIdType=<Factory-Default| User-Defined>]
[ServerIdStart=<ServerId address>] [ServerIdEnd=<ServerId
address>]
I am not quite sure what the result will be when the MacType and WWNType switches are used/ not used. The CLI guide is not clear enough on the switches.
Will the existing WWN/MAC addresses from VCEM pool be removed? Are the WWN/MAC addresses used by the external managed going to be replaced with the range defined in the command? For what purpose I have to define Factory/User-Defined ranges?
Can someone share with me how this command should be used in order to keep all profiles and configurations on the domains intact and continue using HP-Predefined range initially configured in the enclosure? (Later the VCEM will be commanding the environment again).
*************
Input from Vincent:
The MacType and WwnType options determine how MAC addresses and WWNs will be allocated for profiles that are created *after* the VCEM lock is removed. It does not affect existing profiles in any way.
Reply from Aleksandar:
The support call resulted in very contradicting information that releasing the lock will remove the existing values from the profiles and that is not possible to roll back to the HP-Predefined ranges (only User Defined and Factory default) without removing all profiles and reconfigure the MAC/WWN/Server serial section. This will be great setback with a lot of downtime.
We want when releasing the lock to keep all profiles operational with their current values and have all future profiles provided with WWN/MAC from the already configured HP-Predefined range.
Is this possible/achievable with any of the command configurations?
From Julio:
As Vincent mentioned, releasing the lock will not change any existing server profile.
It may have some confusion on the command to release the lock as the only allow range types are User-Defined and Factory-Default:
remove external-manager [-quiet] [UserName=<username>]
[MacType=<Factory-Default| User-Defined>] [MacStart=<MAC
address>] [MacEnd=<MAC address>]
[WwnType=<Factory-Default|User-Defined>] [WwnStart=<WWN
address>] [WwnEnd=<WWN address>]
[ServerIdType=<Factory-Default| User-Defined>]
[ServerIdStart=<ServerId address>] [ServerIdEnd=<ServerId
address>]
As the customer wants to continue using HP-Predefined range for the new profiles or connections it is necessary to set the type as “User-Defined” and provide the start and end range values according to the HP-Predefined the customer wants to use.
For example, if the customer wants to use HP-Predefined 1 range for MAC and WWN:
remove external-manager [-quiet] [UserName=<username>]
MacType=User-Defined MacStart=00-17-A4-77-00-00 MacEnd=00-17-A4-77-03-FF
WwnType=User-Defined WwnStart=50:06:0B:00:00:C2:62:00 WwnEnd=50:06:0B:00:00:C2:65:FF
ServerIdType=<Factory-Default| User-Defined>]
[ServerIdStart=<ServerId address>] [ServerIdEnd=<ServerId
address>]
The server ID range is used by the Logical Serial Number allocation.
Let me know if you have any questions.
********************
Any other comments?