Best practices & naming conventions between VC Enterprise Manager and HP OneView

[chuckk281]

Bart was looking for an HP Oneview and VC Enterprise Manager (VCEM) glossary of terms:

***********

In HP OneView we use some different terminilogy than we had in VCEM, like networks, network sets, uplink sets, Logical interconnect groups etc.

Do we have a document with best practices about a naming convention that customers can use to keep everything quite clear and logical in the configuration of one view? When you just start, it becomes quickly a mess with all these different names.

*************

Reply from Matt:

**************

I would highly advocate pouring a cup of coffee and reading through the Users Guide. It isn’t the most exciting read but there is a lot of good information in there.

Secondly on nearly every screen and popup within Oneview there’s a giant ? (question mark) so that you can be linked to the embedded documentation to that specific topic.

There’s some great diagrams that will help explain your question.  We don’t have a best practices guide but there’s a few white papers available for your next cup of coffee.

www.hp.com/go/oneview/docs

**********

Info from BJ:

**************

Included in the OneView concepts guide. Enclosed for convenience. Available here:

http://h20195.www2.hp.com/v2/GetPDF.aspx%2F4AA5-1386ENW.pdf

Swear I saw it in a slide set somewhere in the past two weeks but couldn’t seem to find it again.

Table1. Terminology at a   glance
HP VirtualConnect	HP OneView	Details
Module	Module	Hardware   description or model name such   as “HP Virtual Connect   Flex-10/10D Module for c-Class BladeSystem.”
MAC address	MAC address	Virtual Connect   supports 64 ranges of 1,024 MAC   addresses. HP Virtual Connect   Enterprise Manager (VCEM) software supports an additional 128,000   MAC addresses. HP OneView supports millions of MAC addresses.
WWN address	WWN address	Virtual Connect   supports 64 ranges of 1,024   WWN addresses. VCEM supports an additional 128,000   WWN addresses. HP OneView   supports millions of WWN addresses.
Domain	Domain	Virtual Connect   domains contain one to   four c7000 enclosures or a   single c3000 enclosure. HP OneView domains designate the collection   of resources managed   by a single HP   OneView appliance. An HP OneView   domain consists of one or   more HP OneView   logical interconnect groups, uplink sets, and networks and defines how server profiles consume these   resources.
Domain group	Logical interconnect group   and enclosure group	Virtual Connect   domain groups are collections   of Virtual Connect domains with a common network   and storage configuration. The HP   OneView analog of domain groups is the combination of HP OneView logical interconnect groups and   HP OneView enclosure groups. HP   OneView administrators designate   groups of enclosures (enclosure   groups) sharing a common network and   storage configuration as described   in a logical interconnect group.
Uplink	Uplink	Visible port on the Virtual Connect module   faceplate that provides external   connectivity for the Virtual Connect   domain or HP OneView logical interconnect. More generally the   faceplate ports may be used   in multiple roles: stacking link, network analyzer port, or network uplink.
Shared uplink   set	Uplink set	Uplink   sets are the   HP OneView analog of shared   uplink sets in Virtual Connect. Uplink sets define the   uplink connectivity for   selected networks. An uplink set   can either be an Ethernet or Fibre   Channel (FC) type, but   not both. Any defined networks not associated with   an uplink set become internal Ethernet   networks to the logical interconnect,   and are reported within the logical interconnect.
Server profile	Server profile	Virtual Connect   profiles define server   serial number,   connectivity (network and   storage), and boot information.   HP OneView server profiles cover all aspects of a   server including firmware versioning, BIOS settings, options, connectivity (network and storage), boot configuration, and serial   number.
Network	Network	Networks   (vNets)   are logical objects within a Virtual Connect domain defining Ethernet connectivity for the   servers to the data   center infrastructure.
Fabric	Fabric	Fabrics   define   FC connectivity for the   servers in a Virtual Connect domain or HP OneView logical interconnect group to the data center   infrastructure. Uplink ports that are part   of the fabric present themselves as N_Ports to the data   center switches.
Private network	Private network	Server   ports connected   to   a private network cannot communicate   directly with each other   within the domain. All traffic   must exit through   an uplink port and be routed   through an external layer   3 router.
Server	Server	Virtual Connect manages   HP   BladeSystem servers. HP OneView   manages both BladeSystem as well as   selected rackmount servers.
Multiple networks	Network set	Virtual Connect administrators can   assign multiple VLANs to a single profile connection. HP   OneView expands on this and allows administrators to configure network sets containing multiple vNets. The network   set is then   assigned to server profile connections.   Changes made to the   network set take effect for   all profile connections   referencing the network   set. Administrators can   make changes in one place   rather than editing each profile connection   individually.

************

Questions?