HP Virtual Connect Domain Setup – Part 1: Domain Setup Wizard

December 20, 2010 — 10 Comments

A friend asked me last week if I could produce a document for him explaining the initial basic setup of Virtual Connect, I decided that instead of  that it would be better and more helpful to write in a series of blog posts, here it is the first of them for you to enjoy.

Virtual Connect is a technology developed by Hewlett-Packard for the HP BladeSystem c-Class enclosures. Provides server-edge and I/O virtualization in order to simplify the setup, maintenance and administration of server connections. It comprises a set of interconnect modules, both Ethernet and Fibre Channel, and a software known as Virtual Connect Manager.

Virtual Connect Manager, or VCM, is the single point administration interface for Virtual Connect. Under the hoods VCM is a software embedded into the VC Ethernet module, it can be accessed through a web-based interface or command line either with a serial connection to the Ethernet module or through a SSH connection to the module.

From the VCM only a single domain, with up to four enclosures, can be managed.

For large-scale infrastructures there is a more scalable version of VCM known as Virtual Connect Enterprise Manager, or VCEM. Unlike VCM, Virtual Connect Enterprise Manager is not embedded into the VC-Enet module, is a separate software that must be installed in another server. VCEM extends the VC management capabilities up to 250 domains and hundreds of blade servers.

Current series of articles will focus only on the Virtual Connect Manager GUI. Please take into account that I’m using Virtual Connect 3.10 version in the whole series and there some differences with the VC 2.x revisions.

When you login into the VCM for the first time a series of wizards will show up to help you with the initial setup of the domain. This article will cover the first of those wizards, the Domain Setup Wizard.

This wizard will allow you to:

  • Import enclosure configuration and communication settings
  • Name the domain
  • Set the IP address of the Virtual Connect Manager
  • Set up the local user accounts and its permissions and privileges
  • Confirm that the stacking links provide connectivity and redundancy

After the informative screen the first step will display. Here you have to provide the enclosure Onboard Administrator IP address and credentials, these credentials must have administrative level. Click next when finish.

Now VC Domain Wizard will import all the servers and VC interconnect modules within the enclosure.

In the next screen select the enclosure to import and click next.

A pop-up will show up to inform that the networking of all the blades within the enclosure will be disabled until VC Networking is properly configured. of course it will ask for confirmation.

After finishing the import the wizard will go the General Settings part. The Domain Setup Wizard automatically assigns a domain name based on the enclosure name, you can change the name when running the setup wizard or at any time later from the Domain Settings screen. The Virtual Connect domain name should be unique and can be up to 31 characters without spaces or special characters.

Next step is to configure the local user accounts.

By default the only local account is Administrator, this account cannot be deleted nor have domain privileges removed. You can also add up to 32 accounts with a combination of up to four levels of access. The available levels are:

  • Virtual Connect Domain
  • Server
  • Networking
  • Storage

There is also an Advanced area for each account where you can set Strong Passwords requirement and the minimum password length.

With this the Domain Setup Wizard is done. In the next article I will write about the network setup of the enclosure using the Network Setup Wizard.

Juanma.

About these ads

10 responses to HP Virtual Connect Domain Setup – Part 1: Domain Setup Wizard

  1. 

    I have been using VC for a while, but I got a tricky one…

    What happens when a VC module is installed in Bay 3&4 (using the latest firmware of course) and the VC Domain is configured… what would happen to the Passthu modules in bay 1 and 2… would the blades using that interconnect have I/O disruption?

    The error says, chassis networking will be disrupted, but is that all networking or just the VC networking? my understanding is that it just the VC networking, but HP’s notification seems to suggest otherwise…

    • 

      Hi Kev. Thanks for the comment.

      The configuration you described is fully supported since VCM 3.10 and as you said the blades using those interconnect modules will not be disrupted.

  2. 

    Thanks for the article, Juanma.

    Just only one comment:
    You stated: “The Virtual Connect domain name should be unique and can be up to 64 characters without spaces or special characters.”

    But, according to the document ‘HP Virtual Connect Manager Command Line
    Interface for c-Class BladeSystem’ (last version I have checked: 3.10/3.15), page 19:

    “The maximum length of the name is 31 characters.”

    I have seen problems in the GUI with domain names over the 31-char limit.

    • 

      Hi Marcos! Thanks for commenting :-)

      Yes you are completely correct, the domain name maximum lenght is 31 characters. I don’t know why I put a different number.

      It’s already corrected.

      Juanma.

  3. 
    Dave Claussen April 10, 2012 at 19:02

    I have a situation you can probably help me with; I have two c7000s – each with redundant Flex-10s. When I set them up initially, I was told there is no need to stack the enclosures, so they are each in their own VC_domain. Now that I know better, I want to stack the enclosures – as easily as I can without losing anything. What I plan on doing is keeping the vc_domain setup in enclosure 1, “reset” enclosure 2 and join enclosure 2 to the vc_domain in enclosure 1. After all of that I can spread out all of the running virtual machines around both enclosures. Sound good?

    Also, can a vc_domain name be changed without hurting anything that is running?

  4. 

    Crying can be stressful for babies, so do not let
    baby cry for a long time. The main objective is
    usually to have a very plan for creating an infant nursery theme
    that will likely be warm, welcoming as well as a cozy spot where you’ll be able to spend this special time along with your little treasure. When creating an eclectic floral vibe, try getting floral crib bedding set with flower accessories with block type furniture in same color. Once you know the sex of your baby-to-be and also have an appropriate room you can start creating the nursery.

Trackbacks and Pingbacks:

  1. MakeMusic: Finale PrintMusic 2011 | Recording - December 29, 2010

    [...] HP Virtual Connect Domain Setup – Part 1: Domain Setup Wizard « Juanma's Blog [...]

  2. Crash course HP Virtual Connect – Hyper-V blog by Hans Vredevoort - January 7, 2011

    [...] HP Virtual Connect Domain Setup – Part 1: Domain Setup Wizard [...]

  3. Crash course HP Virtual Connect | Hyper-v.nu - April 13, 2011

    [...] Virtual Connect Domain Setup – Part 1: Domain Setup Wizard HP Virtual Connect Domain Setup – Part 2: Network Setup HP Virtual Connect Domain Setup – Part [...]

  4. Virtualization Lab with an HP Enclosure and Flex-10 Networking Cookbook « - May 24, 2013

    […] http://jreypo.wordpress.com/2010/12/20/hp-virtual-connect-domain-setup-part-1-domain-setup-wizard/ […]

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s