HPE OneView

Zoning best practices in HPE OneView

Go to solution
Soeren Emig
Valued Contributor

Zoning best practices in HPE OneView

I am exploring Oneview 3.0 and evaluating how far the sphere of influence can reach in a responsible way.

With regards to automatic zoning there is something I can’t get my head around.

When I zone the old-fashioned way I follow this scheme:

Host 1 HBA port 1 --> 0:0:1 1:0:1 (Fabric 1)
Host 1 HBA port 2 --> 2:0:1 3:0:1 (Fabric 2)

Host 2 HBA port 1 --> 0:0:2 1:0:2 (Fabric 1)
Host 2 HBA port 2 --> 2:0:2 3:0:2 (Fabric 2)

The hosts is zoned to all four nodes and complying with port-persistent requirements, but I do not zone to all host ports.

I cannot (as I see it) emulate this in Oneview. My only option is to include all host ports but this is not desirable… 1. I do not need the bandwidth 2. We may run into front-end/host port connection limit sooner in effect cutting the support number of hosts in half.

1. Have I got this all wrong and can I make Oneview zone the way I prefer?
2. What is the general opinion about Oneview/Autozing (from version 3.0)

Thank you




Soeren Emig
Valued Contributor

Re: Zoning best practices in one view


Sorry... typo in my zoning scheme:

All 4 node have 2 FC ports. All port 1 is connected to fabric A and all port 2 is connected to fabric B

host1 port1 -> fabric A 0:0:1 | 1:0:1
host1 port2 -> fabric B 2:0:2 | 3:0:2

Host2 port1 -> fabric A 2:0:1 | 3:0:1
Host2 port2 -> fabric B 0:0:2 | 1:0:2

This is my setup


Re: Zoning best practices in one view

You can control the Alias policy in the Managed SAN.  HOwever, to architect your requirement, you will need to look at Port Groups when you add and manage a 3PAR StoreServe storage system.  You would do the following:

  • PortGroup_1 -> 0:0:1,1:0:1,2:0:2,3:0:2
  • PortGroup_2 -> 2:0:1, 3:0:1, 0:0:2, 1:0:2

No, you would not have control which Port Group would be assigned to which server.  OneView would make that descision for you.  Please know that if you want to use Port Groups, are using OneView older than 3.0 and want to deploy Boot from SAN (BfS), you would have to create then edit your server profile in order to set the bootable WWN of the target boot device.  In 3.0, you can now mark a Private Volume that you are attaching as a Boot Device and OneView will automatically configure the BfS settings for you, reducing the double step necessary for older versions of OneView.

I am an HPE employee

Accept or Kudo

Soeren Emig
Valued Contributor

Re: Zoning best practices in one view

Thank you :)

Now I get it. It works


Re: Zoning best practices in one view

Hi Chris

We are also planning to automate zoning by HPOneview 5.0.We have DCX 8510 core switches connecting to  3Par -4Node & HP6500B Edge switches to Synergy ESXi servers. 

We are using 2ports from 2 FC slots in each controller for FC connectivity.

0:4:1,0:5:1,1:4:1,1:5:1,2:4:1,2:5:1,3:4:1,3:5:1 -Core FabricA

0:4:2,0:5:2,1:4:2,1:5:2,2:4:2,2:5:2,3:4:2,3:5:2 -Core Fabric B

Host1 - Port1,Port2,Port3,Port4

Host2 - Port1,Port2,Port3,Port4

Suppose we have Host1 & Host 2 with 4 port HBA , how One View will automate the zoning in this case.How it will select the ports from 3par connections for zoning ,how is this distribution done?