The naming convention in version 4.1 of VMware Validated Design provides uniqueness of objects across the SDDC. You can identify managed objects directly if you use many components that are linked together, for example, multiple vCenter Server systems working in Enhanced Linking Mode or management dashboards in vRealize Operations Manager or vRealize Business monitoring multiple instances of the same component.

This naming convention also enables you to scale out across infrastructure blocks, for example, in the following cases:

  • Scale a Consolidated SDDC out to a Standard SDDC.

  • Extend a Standard SDDC with a ROBO SDDC.

  • Add blocks of infrastructure to support more availability zones.

The new naming convention covers the following components:

  • Virtual machines and ESXi hosts

  • Objects in the vCenter Server and NSX inventories

Elements of the Component Names in VMware Validated Design 4.1

The name of each component or object in this validated design consists of units that represent the location, purpose and numerical identifier of the component in the SDDC.

Table 1. Elements of the Component and Object Names in the SDDC

Element

Description

Used In

location

Defines the physical location of the component, for example, sfo and lax.

  • Host names

  • VM names

  • Virtual switch names

  • Names of placeholder objects in the vCenter Server inventory

az_id

Defines the ID of the availability zone of the component in the physical location. It is a two-character numerical value starting at 01.

  • Host names

  • VM names

  • Virtual switch names

  • Names of vCenter Server container and managed objects

pod

Indicates the purpose of the pod the component is linked to. Possible values are as follows:

  • m for management

  • w for workload

  • Host names

  • VM names

  • Virtual switch names

  • Names of vCenter Server container and managed objects

pod_id

Defines the pod ID. It is a two-character numerical value starting at 01.

  • Host names

  • VM names

  • Virtual switch names

  • Names of vCenter Server container and managed objects

mgmt_component

Defines the function of the management applications using up to six characters, for example, vc, psc and nsx.

  • Host names

  • VM names

mgmt_component_id

Defines the instance of the cluster. Two character numerical value starting at 01.

  • Host names

  • VM names

cluster_type

Indicates the purpose of the cluster. Possible values are as follows:

  • m for management

  • w for workload

Cluster names

cluster_id

Defines the ID of the cluster. It is a two-character numerical value starting at 01.

Cluster names

virtual_switch_type

Indicates the switch type. Possible values are as follows:

  • vss for standard switch

  • vds for distributed switch

  • Virtual switch names

virtual_switch_id

Defines the ID of the switch. It is a two-character numerical value starting at 01.

  • Virtual switch names

port_group_type

Defines the name of the port group.

  • Port group names in virtual switches

datastore_type

Indicates the datastore type. Possible values are as follows:

  • vsan for vSAN

  • nfs for NFS

  • Datastore names

datastore_id

Defines the ID of the datastore. It is a two-character numerical value starting at 01.

  • Datastore names

object_type

Defines what the object type in the vCenter Server inventory. Possible values are:

  • rp for resource pool

  • fd for VM folder

  • hp for host profile

  • cl for content library

Names of vCenter Server container and managed objects

object_name

Defines the name of the object.

Names of vCenter Server container and managed objects

object_id

Defines the ID of the object. It is a two character numerical value starting at 01.

Names of vCenter Server container and managed objects

Syntax of Component Names

Each component in this validated design is assigned a name according to its type.

Table 2. Name Syntax for the Management Objects in the SDDC

Name Attribute

Value

Component type

Virtual machine or host

Syntax

<location><az_id><pod><pod_id><mgmt_component><mgmt_component_id>

Example

sfo01m01vc01

Component type

Cluster

Syntax

<location><az_id>-<pod><pod_id>-<cluster_name><cluster_id>

Example

sfo01-m01-mgmt01

Component type

Virtual switch

Syntax

<location><az_id>-<pod><pod_id>-<switch_name><switch_id>

Example

sfo01-m01-vds01

Component type

Port group on a virtual switch

Syntax

<location><az_id>-<pod_type><pod_id>-<switch_type><switch_id>-<port_group_type>

Example

sfo01-m01-vds01-management

Component type

Datastore

Syntax

<location><az_id>-<pod_type><pod_id>-<datastore_type><datastore_id>

Example

  • sfo01-m01-vsan01

  • sfo01-m01-nfs01

Component type

vCenter Server container and managed object, such as data center, resource pool, folder, host profile and content library

Syntax

<location><az_id>-<pod_type><pod_id><object_type>-<object_name><object_id>

<object_id> is optional.

Example

  • Data center - sfo01-m01dc

  • Resource pool - lax01-w01rp-sddc-edge

  • Folder - sfo01-m01fd-mgmt

  • Host profile - sfo01-m01hp-mgmt01

  • Content library - lax01-w01cl-lib01