Dell EMC Reference KB 483591
Note:MAC address replication is enabled by default on RP4VM 5.X. The following steps are specific for RP4VM 4.3 as per KB 483591.
When a VxBlock is shipped from the factory all Windows & SQL user/db accounts are setup as local accounts, due to obvious reasons (customer AD does not exist in factory!). This post details the steps to integrate a VUM VM & SQL with Active Directory and change the local WIN&SQL accounts to AD accounts, along with modifying the SQL DB permissions to an assigned AD account.
– Change DNS values on the Windows VUM VM (if different from LCS stated values).
– Join Windows VUM VM to AD.
– Reboot VUM VM.
– Snapshot VUM VM (precautionary step).
– Add domain\svc_vum to local admin group of the VUM VM.
Introduced as part of the EHC 4.1.1 release (Code named “Challenger”) – GA March ’17
Simple, Easy, Start Small, Scalable!
VxRAIL HCI Appliance now has the option of including the ‘Enterprise Hybrid Cloud 4.1.1’ platform as part of an automated greenfield installation. Thousands of hours of engineering, designing, testing and validation has gone into this release with a laser focus on delivering an automated ‘EHC on VxRail’ onsite installation. Engineered on the VxRail P470(F) Appliances, ‘EHC on VxRail’ offers a lighter weight and smaller footprint hybrid cloud solution from where you can start small and scale exponentially. Continue reading
The following provides guidance in a scenario where your ESXi host boots from SAN, for example this is the standard configuration for Cisco UCS blades included in a Vblock/VxBlock. These boot volumes will most likely have been created outside of ViPR Controller, thus it will be a requirement to perform an ingestion of these volumes prior to performing any host migration procedures, for example moving a UCS ESXi blade to another cluster in vCenter.
Note: by not performing the ingestion will result in the removal of the Boot volume from the ESXi host masking if you are initiating the migration process utilizing ViPR commands (more on this later).
Note: To avoid ViPR provisioning issues ensure the ESXi BOOT volume masking views have _NO_VIPR appended to their exclusive mask name, this will prevent ViPR from using the exclusive export mask when adding A NEW ESXi host to a cluster:
A frequent question I receive:
“What is the primary production storage system included in a VxBlock / Vblock?”
Note: Enterprise Hybrid Cloud (EHC) STaaS leverages EMC ViPR Controller as the abstraction layer to provide software-defined storage.
VMware Machine Blueprint Definition: A blueprint that contains a machine component specifies the workflow used to provision a machine and includes information such as CPU, memory, and storage. Machine blueprints specify the workflow used to provision a machine and include additional provisioning information such as the locations of required disk images or virtualization platform objects. Blueprints also specify policies such as the lease period and can include networking and security components such as security groups, policies, or tags. Blueprints can be specific to a business group or shared among groups in a tenant, depending on the entitlements that are configured for the published blueprint. More detail on Blueprints here.
To create the Blueprint Login as a user who has the ‘Infrastructure Architect’ role assigned (Machine Blueprint capabilities):
VMware Services Definition: Services are used to organize catalog items into related offerings to make it easier for service catalog users to browse for the catalog items they need. You can entitle the service, which entitles business group users to all the associated catalog items. More details on Services here.
Login as a Tenant Admin or a user that holds the Catalog Admin role: