- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Recovery of a Virtual Connect Domain
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
07-30-2012 07:48 AM
07-30-2012 07:48 AM
Recovery of a Virtual Connect Domain
Francesco was looking to recover a VC Domain:
**************
How I can ( if I can….) a virtual connect recovery from a broken VCEM ?
When I try to connect a Virtual Connect, I receive the warning …” managed from VCEM…” but my VCEM is unavailable and I haven’t any backup.
Which procedure I can use for managed virtual connect without a VCEM ? or can I “clean” (on the virtual connect) reference to VCEM ?
*******************
Reply from Fred:
****************
This is covered in Chapter 11 of the VCEM User's Guide (UG): http://bizsupport1.austin.hp.com/bc/docs/support/SupportManual/c03169041/c03169041.pdf
If the preferred method is not possible (for example, if the CMS where VCEM is installed is
inoperable or unreachable from the VC Domain), the Virtual Connect Manager supports
command line interfaces that allow the external manager account to be deleted from the Virtual
Connect Manager and also allow a Virtual Connect Manager to be removed from VCEM
control.
To remove the external manager account:
1. Telnet in to the Virtual Connect Manager using an SSH connection such as SSH
Administrator@xxx.xxx.xxx.xxx, where xxx is the VC Domain IP address.
2. To determine the user name of the external manager account, from the Virtual Connect
Manager command prompt, enter show external-manager. For this example, assume
the user name returned was xyz.
3. To disable the account, from the Virtual Connect Manager command prompt, enter
set external-manager Username=xyz Enabled=false
Perform the following:
◦ To remove the account and release the VC Domain from VCEM control, from the
Virtual Connect Manager command prompt, enter
remove external-manager Username=xyz
mactype=<Factory-Default/User-Defined> MacStart=<> MacEnd=<>
wwnType=<Factory-Default/User-Defined> WwnStart=<> WwnEnd=<>
serverIdType=<Factory-Default/User-Defined> serverIdStart=<>
serverIdEnd=<>
NOTE: The "-quiet" option is used to suppress user confirmation prompts. This option is useful
for scripting operations. This option is available for VC firmware 2.0x for the disable account,
remove the account, and release ranges commands.
For more information, see the HP Virtual Connect Manager Command Line Interface User Guide
at http://www.hp.com/go/virtualconnect.
*****************
Other suggestions or comments?