HP OneView – Part 1: Enclosures and Uplinks (logical or otherwise)

The initial configuration of HP OneView is a pretty simple and intuitive process, it just isn’t documented as well as it could be. I’ve decided to put together a few posts detailing some of the areas of configuration that could possibly do with a bit more detailed procedures. I’d expect that someone who wishes to use any thing that is documented here is already acquainted with Virtual Connect, Onboard Administrator, VMware vSphere and iLO’s etc.

Design

Before any implementation work is carried out there has to be a design in place, otherwise what and how are you going to configure anything.. The design for these posts will be a simple VMware environment consisting of a number of networks to handle the standard traffic one would expect (Production, Vmotion etc.) at this point we have defined our networks and these have been trunked by our network admin on the switches out to the C7000’s we will be connecting too.

c7000 VMware

 

From this diagram, you can see the coloured VLANs represent the traffic designated management/service traffic and the grey VLANs represent production traffic. All of these VLANs are trunked from the Access switches down to the virtual connect modules located in the back of the C7000 enclosures.

 

Note: I’ve omitted SAN switches from this and just presented what would appear as zoned storage direct to the Virtual Connect. I may cover storage and flat san at a later date, if there is any request to do so.

 

 

This represents the external connectivity being presented to our Enclosure, it’s now time for the logical configuration with HP OneView…

 

To begin with, it makes sense to be aware of some of the HP OneView terminology:

Interconnect Group, A collection of logical interconnects that have the same configuration, this can be used as a master template and any changes made here can be then applied to all interconnects in the group.

Logical Interconnect, This is a logical appearance of available networks, uplinks, and stacking links that can be physically applied.

Enclosure Group, This is a logical group containing similarly configured C7000 enclosures, and a server profile has to exist in an enclosure group to be created.

Server Hardware, This is list of hardware choices that is populated by detected servers. This ultimately means that a server profile can’t be created until a server has been detected by HP OneView.

Network Set, This is a logical grouping of a number of defined networks. This allows automation of network provisioning at the click of a button.

Create Networks

It is recommended that networks are created first, this is mainly due to a bizarre omission in the wizard for adding an enclosure that only created networks can be added during enclosure import. Note: Network Sets will be covered afterwards as these apply to server profiles. These tagged networks can be simply created from the HP OneView menu -> Networks -> [+] Create network and adding in the simple details such as VLAN name and VLAN ID..

Networks

 

From here we can also configure FC (Fibre Channel) Connectivity, from this example we will assume that zoning is a manual task (i.e. no FlatSan automation). So the Fabric Type is regarded as Direct attach. Create Two Fabric networks of type Direct attach for Fabric A/B.

Adding an Enclosure

A few details are required to add in a C7000 to a HP OneView:

  • Add_EnclosureIP address of the OA (Onboard Administrator)
  • Username and Password of OA
  • The name of a new Enclosure group or an existing one. (This can’t be changed afterward so ensure you’ve confirmed details before submitting)
  • Optional: Firmware and/or Licensing

Select the HP OneView menu and select Enclosures -> [+] Add Enclosure

Add in the correct details as shown in the screenshot… and select Add

 

If this is the first Enclosure to be added or is added to a new Enclosure Group then you will be presented with another screen to create your first Interconnect Group with configured uplink sets, which can then be applied to additional enclosures as they are added. This screen can be a little bit overwhelming on first glance but is actually simple depending on the type of virtual connect module that is being used in the C7000.

Q Ports: These are related to the 40GB QSFP+ ports and a 40GB QSFP will only allow use of Q1.1, where as a breakout cable (4x10GB) will allow the use of Q1.1 to Q1.4 on each 40GB port.

X Ports: These ports can accommodate either 1/10 GB Ethernet or 2/4/8 GB FC.

So Ensure that the cabling aligns up before you define you Uplinks, for the purposes of this example the cabling is straight forward:

We have redundant 40GB Ethernet going to ports 1/2 on both virtual connects so (Q1.1 and Q2.1), and the same with 8Gb fibre going into the first X port (X1), ensure that the networks are added as tagged on both network uplinks as well.

If correct it should look something like this:

uplinks

This covers all of the external connectivity, next is logical (server profiles etc..)

 

2 thoughts on “HP OneView – Part 1: Enclosures and Uplinks (logical or otherwise)”

  1. PLease do write more about virtual connect and different ways to set it up. Best way for NFS storage?

  2. Hello,

    Can you elaborate on what exactly you would like to see added to the Virtual connect configuration? Also with regards to NFS? I’d assign another pair of interfaces to the ESXi host that were dedicated for NFS traffic..

    Let me know and I will add accordingly.

Leave a Reply

Your email address will not be published. Required fields are marked *