HP Virtual Connect Domain Setup – Part 2: Network Setup

December 21, 2010 — 26 Comments

In the first post of the series I introduced to you HP Virtual Connect and showed how to use the Domain Wizard Setup to initially configure a VC domain. In the following article I will outline the use of the Network Setup Wizard and explain Virtual Connect networking concepts.

Before we begin to setup the network it would be very useful to clarify the Virtual Connect port terminology.

  • External port – The Ethernet connectors SFP+ modules (either 1GB or 10GB), 10GBASE-CX4 and RJ-45 on the faceplate of the Ethernet module.
  • Stacking port – These are Ethernet external ports used to connect within a Virtual Connect Domain the VC Ethernet modules. The Ethernet modules automatically identify the stacking modules.
  • Uplink port – An external port configured within a Domain for use as a connection to the external networking equipment. These ports are defined within Virtual Connect by the enclosure name, interconnect bay that contains the module and the port number.
  • Uplink port set – A set of uplinks ports trunked together in order to provide improved throughput and availability.
  • Shared uplink port – This is an Ethernet uplink port that carries the traffic for multiple networks. The associated networks are mapped to a specific VLAN on the external connection, the appropiate VLAN tags are removed or added as Ethernet packets enter or leave the VC Domain.
  • Shared uplink port set – This is a group of Ethernet uplinks trunked to provide improved throughput and availability to VC Shared Uplink Set.

The Virtual Connect Network Setup Wizard will help to establish external Ethernet connectivity for the enclosure. With this wizard you will be able to:

  • Identify the MAC addresses to be used by the servers within the VC Domain.
  • Configure Server VLAN tagging.
  • Set up connections from the c-Class enclosure to the external networks.

The network connections can be:

  • Dedicated uplink to a specific Ethernet network.
  • Shared uplink sets.

The first screen of the wizard is the MAC Address Settings. As every server in the market the HP Blades come with factory-default MAC addresses already assigned to their network cards. However Virtual Connect can override these values while the server remains in the enclosure.

Virtual Connect access the NICs through the Onboard Administrator and the server iLO to manage the MAC addresses. It provides 64 predefined and reserved MAC address ranges. The wizard will give you the option to use either an HP predefined range or an user defined one. HP recommends to use the predefined ranges.

Once you have chosen the address range and click next the wizard will ask for confirmation before continue.

The next screen is Server VLAN Tagging Support. Here the wizard gives you two possible options:

  • Tunnel VLAN Tags
  • Map VLAN Tags

The first one, Tunnel VLAN Tags, supports only VLAN tagging on networks with dedicated uplinks where all VLAN tags passed through the VC Domain without modification and ports connected to networks using shared uplinks can only send and receive untagged frames.

On the other hand Map VLAN Tags allow you to add more than one network to an Ethernet server port and specify the VLAN mapping between server tags and VC-Enet networks. Also, the VLAN tunneling will be disabled for VC Ethernet networks with dedicated uplinks.

There is also a checkbox in the page to , if this option is enabled the server ports connected to multiple VC Ethernet networks are forced to use the same VLAN mappings as those used for the corresponding Shared Uplink Set and the network connections can only be selected from a single Shared Uplink Set. When this option is not checked server network connections can be selected from any VC network and the external VLAN ID mappings can be manually edited. In the example of the screenshots I decided to check it.

Below are another two optional settings for link speed control when using mapped VLAN tags. These settings are:

  • Set a Custom value for Preferred Link Connection Speed. This value applies to server profiles with a Multiple Networks connection defined and the Port Speed Setting set to Preferred.
  • Set a Custom value for Maximum Link Connection Speed. This value limits the maximum port speed for multi-network connections when a Custom port speed is specified.

In our example we’re not going to check neither of them . Click next to move into the Define Network Connection screen.

Choose the network type you want to define and click next. I choose .

The Define Single Network shows up. First define the network name (prod_net_01 in my example). There are three configurable values.

  • Smart Link – With this option enabled Virtual Connect will drop the Ethernet link on every server connected to that network if the link to the external switches is lost.
  • Private Network – This option is intended to provide extra network security by isolating all server ports from each other within the VC Domain. All packets will be sent through the VC Domain and out the uplinks ports so the communication between the severs will go through an external L3 router that will redirect the traffic back to the Domain.
  • Enable VLAN Tunneling.

Click in the Advanced button to configure Advanced Network Settings. Set the network link speeds that best suites your configuration.

Again from the Define Single Network page we are going to assign a port to our network. Click on Add Port and select an uplink port.

Set the Connection Mode to Auto if the ports are trunked and to Failver if not.

Click Apply and move onto the next screen. From this screen you can create as many additional networks as you need.

Now we are going to create a network using VLAN tagging. Click Next an move again into the Define Network Connection page, select Connection with uplink(s) carrying multiple networks (using VLAN tagging) and click Next. The Define Shared Uplink Port Set page will be displayed.

A shared uplink is the way Virtual Connect has to identify which uplinks carry multiple networks over the same cable. On shared uplinks the VLAN tags are added when packets leave the enclosure and added when leave. The external switch and the Virtual Connect Manager must be configured with the same VLAN tag ID for each network  on the shared uplinks. The uplinks enables multiple ports to be added in order to support port aggregation and link failover, with a consistent set of VLAN tags. Virtual Connect has no restriction on which VLAN IDs can be used so the VLANs already used in the external infrastructure can be used here.

Since the VLAN tags are removed or added as soon as the packect enter or leave VC Ethernet Module shared uplink they have no relevance after the packet enter the enclosure. By identifying an associated network as the native VLAN will cause all untagged incoming packets to be placed onto this network, just one network can be designated as the native VLAN.

To finish the network creation assign a name (up to 64 characters with no spaces), add a port using the drop-down menu like in the single network process described above and add the networks you want to associate to the uplink. Finally click Apply.

In the final screen you will see now the three networks associated to a Shared Uplink Set. You can check this also from the Virtual Connect Manager page in the Ethernet Networks area.

And we are done with the Network Setup, in the next post I will show the storage part. As always any feedback would be welcome :-)

Juanma.

About these ads

26 responses to HP Virtual Connect Domain Setup – Part 2: Network Setup

  1. 

    poglejte si tole [url=http://www.vsezasport.si/sporti-na-prostem/drsalke]Drsalke[/url]

  2. 

    Hi Juan Manuel.

    Thank you very much for your posts on HP VC: they are really good!

    Recently we have adquired 10 HP 1/10Gb-F VC-Enet Module to provide connectivity to our 5 C7000 enclosures.

    When we try to configure them and we reach the Network Wizard we found a weird issue: the Add ports drop-down is missing, so we cannot see the uplink ports neither add them to any network.

    We have tried both single networks and multiple networks. We have tried to do it without using the wizard. We have even tried to do it through the CLI!! And the result is the same. The CLI returns:

    “ERROR: Port not found”

    when we try any of these commands:

    add uplinkport enc0:1:1 network=network04
    add uplinkport 1:1 network=network04
    add uplinkport 1:S1 network=network04
    add uplinkport 1:X1 network=network04

    Other sympthoms we see are:

    – On the modules, the leds for the port are light up before we begin the configuration. Afterwards they go out.
    – On the CLI, if we run “show interconnect” we get:

    ID Enclosure Bay Type Product Name Status
    ===============================================================================
    enc0:1 ERA-ENCLOSURE04 1 VC-ENET HP 1/10Gb-F VC-Enet Module No Comm

    – On the VCM web interface, under the Hardware Overview, the enclosure is marked as Critical. If we click the enclosure on the left menu and then the Enclosure Status tab, we see Overall status: failed and VC Status Failed.

    – On the VCM web interface, under the Hardware Overview, under the Interconnect Bays, the HP VC is marked as Major, showing Overall status: No Communication and OA Communication Status: Failed.

    Maybe you can give us a hint on this.

    Thank you!!

    • 

      Hi Otura. Thanks for commenting.

      At first sight you seem to have a hardware problem however my experience tells me that first thing you should check is firmware, which VCM version are you running?

      You commented that you have 10 VC-Enet modules, does the problem happen with every module in any enclosure? With every module in a certain enclosure?

      The first test I would do is trying other modules in the same bay and the failed module in other bays and enclosures.

      Tell what you found it and contact me in Twitter if you need more help :-)

      • 

        Thank you Juan Manuel.

        Your guess was right and a FW upgrade did the trick.

        The behavior was common to all the 10 VC’s.

        Current FW of VCM is 3.18 and works like a charm, even when I miss then server profile wizard.

  3. 

    Hi,

    We have hp blade c3000 with a vc module in bay 1, but we have no way to manage it so we can make it work.
    There ip address shows as unknown or 0.0.0.0 – it seems the web interface is not working on it -.

    can any one help.

    • 

      George,

      To assign management IP address to the VC you should install it in the enclosure and then setup the EBIPA addresses by using the OA interface, exactly in the same way that you assign IP addresses to the ILO for each blade.

      Hope this helps.

  4. 

    Good article. Can you give more detail into VLAN Mapping vs VLAN Tunneling? I set up VLAN Mapping but now every time I want to add a new VLAN to my network, I not only have to add it to my switch I have to add it to the Flex too. I’d like the Flex to trunk everything through and not care, and I’ll then manage them from the switch and the server. I reset my config and tried VLAN Tunneling but it doesn’t support tagged frames, so it’s only one network port physical port. This also isn’t suitable as I want to run lots of VLANs.
    Is there a way to get Flex to trunk everything without having to configure each and every network?

  5. 

    Is there any limit to create VLAN if then what is the maximum number of vlan we can create with one port

    • 

      Thanks fot the comment Anog. Yes, there is a limit. The maximum number of VLANs for VC are:
      For VC up to 3.1x

      – 128 VLANs per Shared Uplink Set (64 for pre-2.30 firmwares)
      – 28 per server downlink

      For VC 3.30 an later:

      – 1000 VLANs per Shared Uplink Set
      – 162 VLANs per server downlink

      Hope this help :-)

  6. 

    Hi Bilbo thanks for commenting, glad you liked the article. I’m planing to write more about Virtual Connect, specially an article related to VLAN configuration since it looks there’s a bit of confusion around that. But for now it will have to wait, I’m currently studying for my VCP5 and I’m preparing a series of articles about it.

  7. 
    Charles Chill January 6, 2012 at 12:33

    Excellence, thanks a lot.

    -charles

  8. 

    How to create a home community over completely from scratch — organizing – what is required and the way to carry out. Simply by robert Holloranhome networks

  9. 

    Hi,

    After we have completed the Network setup on Virtual Connect Manager, how do we configure the server blade so that it will be accessible remotely? We tried to configure the IP on our blade server but we cannot access it remotely. Pinging the server produces “request timed out errors” Where do we look to troubleshoot is it on the VCM or the server blade itself or both?
    Sorry for the newbie questions as i’m new to HP-UX, been working mostly on Solaris and Linux.

    Thanks a lot in advance.

  10. 

    thank you for a well written howto. i have just acquired c7000 blade and in the process of setting it up. i have managed to logon to the onboard administrator but i am missing the virtual connect manager link. blade details: rack firmware version is 3.32, administrator firmware version 1.7 and vc flexfabric firmware version 3.18

    thanks.

    • 

      Make sure you assigned an IP to the VC modules from the OA enclosure IP addressing section.

  11. 

    Good article!

    Can I change the name of a shared uplink set online?
    Can I chante the name of a VNet online?
    Could be make any problem o error?

  12. 

    Attractive component to content. I just stumbled upon your web site and in accession capital to
    claim that I get in fact enjoyed account your
    blog posts. Any way I will be subscribing in your feeds
    and even I achievement you access consistently quickly.

  13. 

    Magnificent website. Plenty of helpful info here.
    I am sending it to a few buddies ans also sharing in delicious.
    And obviously, thank you in your sweat!

  14. 

    What’s up colleagues, its enormous paragraph on the topic oof teachingand completely explained, keep
    itt up all the time.

  15. 

    Hello Juan
    how do we use / activate the LOMS 1a , 1b, 1c,1d ? I now see only 1a that i can use while defining server profiles.

  16. 

    whoah this blog is fantastic i really like studying your posts.
    Keep up the good work! You recognize, a lot of people are looking around for this
    information, you could help them greatly.

  17. 

    Hi everyone, it’s my first visit at this web site, and paragraph
    is really fruitful in favor of me, keep up posting these types of content.

Trackbacks and Pingbacks:

  1. Crash course HP Virtual Connect – Hyper-V blog by Hans Vredevoort - January 7, 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 3: Storage setup HP Virtual Connect Domain Setup – Part […]

  2. Crash course HP Virtual Connect | Hyper-v.nu - April 9, 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 3: Storage setup HP Virtual Connect Domain Setup – Part […]

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

    […] http://jreypo.wordpress.com/2010/12/21/hp-virtual-connect-domain-setup-part-2-network-setup/ […]

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