VMware vSAN 2017 Specialist Badge

vmware-vsan-2017-specialist

I recently earned the VMware vSAN 2017 Specialist Badge. Despite the name, I did in fact pass the exam in 2019 with a score of 411. This is the latest version of the exam. I do not like how VMware is naming the exams after the year the exam was released. Makes sense for Microsoft to put a year in the exam title because the version of their software obviously has the year in it. I hope VMware goes back to naming the exams after the version of the product.

The latest version of vSAN is 6.7 U2, but the exam objectives are based on vSAN 6.6. The exam was fairly easy so I guess that is why it is for a badge and not a certification. The exam didn’t really have any surprises. It closely followed the exam objectives. I recommend to review the material in the two links below and know it very well. I had plenty of time to finish the exam.

https://xiaoxiaoke.wordpress.com/2016/02/20/how-to-understand-and-calculate-space-requirements-for-raid-1-with-vsan/

https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.virtualsan.doc/GUID-3863B640-3449-46A2-84E0-AC07E5A604FD.html

As you can see from the image below, the badge path is for VCP6 holders. The drop down only has expired VCP and no VCP. My VCP is active, but on 5.5. I have kept it active with taking VCAP exams during the past few years. Then it would have become active anyway since VMware changed their rules for certification expiration.

vSANSpecialistRequirements2

Anyway, there is actually many more certification that meet the requirements for this badge. The screen shot below, from VMware’s certification manager, shows a long list that has VCAP 6, VCDX 6, and newer VCP exams. I earned the badge since I previously passed the VCAP6-DCV Design exam. I am not sure why it says vRealize Operations 2017 for 1.2. I am guessing it’s a mistake and should list the vSAN exam.

vSANSpecialistRequirements

 

 

Migrate resources to a new vCenter Server – Unregister old vCenter Servers (Part 4)

Now that all resources have been migrated, verify that nothing was forgotten at the source vCenter Server. Refer back to part 1. Make sure all permissions have been set on the destination resources in case you need to go back to the source to double check. Would not be fun to roll back once the single command to unregister a vCenter Server is ran.

KB2106736 has the steps for the appliance and Windows versions to unregister a vCenter Server from a PSC. In the addition to the KB article, I have two suggestions. Take a snapshot of all PSCs before running the command just to be safe.  I did run into a small issue at first, but nothing negative happened because of it. The vCenter name in the cmsso-util unregister command is case sensitive. “Could not find a host id which maps to NAME INPUTTED in Component Manager, Failed!!!” was the error message I received. If the vCenter Server is not found when running the command, I suggest you instead use the IP address of the vCenter Server.

CaseError1

The unregister command went well for me after I entered the vCenter Server in the correct case. It took a few minutes to run before I received the success output.

CaseError2

That completed the major steps in my migrations. I spent time afterwards to put datastores back in datastores clusters, import host profiles, etc. Documentation is important to assist in making your clusters look how they did before.

Migrate Resources to a New vCenter Server (Part 1)
Migrate resources to a new vCenter Server – Methods for Migrations (Part 2)
Migrate resources to a new vCenter Server – Cross vCenter vMotion Utility (Part 3)
Migrate resources to a new vCenter Server – Unregister old vCenter Servers (Part 4)

 

Migrate resources to a new vCenter Server – Cross vCenter vMotion Utility (Part 3)

I used a different method of migration for a cluster that was migrating to a new vCenter Server on a new SSO domain. The destination vCenter Server was using the vDS so I had the same limitation as the previous migration. Though, I had a different idea for this one. I had enough resources in one of the clusters to first bring over half of hosts to the destination vCenter Server. Having this configuration made the process of live migrating my VMs easy by using the Cross vCenter Workload Migration Utility.

vMotion is not bound by a SSO domain and vMotion does not even know the concept of an SSO domain. I heard this discussed on the Virtually Speaking Podcast with William Lam describing his work on the Cross vCenter Workload Migration Utility. vMotion appears to only be within the same SSO domain because of the limitation in the GUI. However, there are APIs to migrate a VM to a different SSO domain. The utility is a technically a fling, but I see no problem with using it in a production environment.  After all, the APIs are there and the utility is just giving an easy to use interface.

Here’s the process I went though for this migration.

  1. Export the vDS from the source vCenter Server
  2. Import the vDS on the destination vCenter Server
  3. Place host in maintenance mode
  4. Document and then remove VMkernel ports
    1. Of course, migrate the management VMkernel to a standard port if it is on the vDS.
    2. VMkernel ports need to be removed before a host can be removed from a vDS.
  5. Remove host from vDS
  6. Disconnect host and then remove host from source vCenter Server
  7. Add host to vCenter Server
  8. Add host to vDS
  9. Create and/or migrate  VMkernel ports that were previously deleted
  10. Exit maintenance mode
  11. Repeat steps 3-10 for additional hosts
  12. Use the Cross vCenter Workload Migration Utility to vMotion VMs

Migrate Resources to a New vCenter Server (Part 1)
Migrate resources to a new vCenter Server – Methods for Migrations (Part 2)
Migrate resources to a new vCenter Server – Cross vCenter vMotion Utility (Part 3)
Migrate resources to a new vCenter Server – Unregister old vCenter Servers (Part 4)

Migrate resources to a new vCenter Server – Methods for Migrations (Part 2)

My first walk through is for a cluster migrating to a different vCenter Server. This is the traditional vDS to standard switch to vDS. The reason for this way is to maintain up time for  my VMs and supportability. Moving a host to a new vCenter Server without first going to a standard switch is not supported. I will go over each step. In my case case, management and vMotion VMkernel ports are already on dedicated standard switches. Though, there is also a method to migrate the VMkernel ports with no downtime that is very similar. Only VM network traffic is on my vDS.

Each host needs to already have at least two physical NICs to avoid downtime for VMs and VM traffic. If you keep a continuous ping on a few VMs during this process, you will only see one ping drop during each major step. Make sure you verify the root password before removing hosts from vCenter.

Source vCenter Server

  1. Export the vDS configuration
    1. Go to the vDS -> Right click the vDS
    2. Export Configuration
    3. Select the Export the distributed switch configuration and all port groups option
  2. Create a Standard Switch and the virtual machine port groups
    1. No physical uplinks on every host at this moment
    2. A new port group that matches every port group that’s on the vDS
  3. Remove one of the physical NICs from all hosts
    1. Go to the vDS -> Manage Hosts
    2. Select all of the hosts
    3. Remove one of the two physical NICs
    4. Next -> Next -> Finish
  4. Add the physical NIC that was removed to the new standard switch on each host
  5. Migrate VMs in bulk in each port group
    1. Go to the vDS -> Migrate Virtual Machine Networking
    2. Select the source vDS port group
    3. Select the destination standard switch port group
    4. Select all VMs
    5. Finish
    6. Repeat these steps for each port group
  6. Remove the last physical NIC on the vDS
    1. Ensure no VM is connected to the vDS
    2. Go to the vDS -> Manage Hosts
    3. Select all of the hosts
    4. Remove the last physical NICs
    5. Next -> Next -> Finish
  7. Remove the hosts from the vDS
    1. Go to the vDS -> Click the host tab
    2. Right click each host and click remove
  8. Remove the hosts from the vCenter Server
    1. Right click a host -> Disconnect
    2. Right click a host -> Remove
    3. Repeat for each host

Destination vCenter Server

  1. Create a new cluster
  2. Add hosts to the new cluster
    1. Right click on the cluster
    2. Add host -> next through wizard
    3. Repeat for each host
  3. Import the vDS configuration at the destination vCenter Server
    1. Do not preserve the original vDS and port group identifiers
    2. Preserving the vDS and port group identifiers is used when restoring the vDS within the same vCenter Server
  4. Remove one physical NIC from the standard switch on each host
  5. Add the hosts to the vDS
    1. Go to the vDS -> Manage Hosts
    2. Select all of the hosts
    3. Add the physical NIC that was previously disconnected
    4. Next -> Next -> Finish
  6. Migrate VMs back to the vDS
    1. Go to the vDS -> Migrate Virtual Machine Networking
    2. Select the destination standard switch port group
    3. Select the source vDS port group
    4. Select all VMs
    5. Finish
    6. Repeat these steps for each port group
  7. Ensure no VMs are on the standard switches
  8. Remove one physical NIC from the standard switch on each host
  9. Add the last physical NICs to the vDS
    1. Go to the vDS -> Manage Hosts
    2. Select all of the hosts
    3. Add the physical NIC that was previously disconnected
    4. Next -> Next -> Finish
  10. Delete the unused standard switches

Now all VMs are running in the new vCenter Server on the vDS with no downtime. I will go over another method in my next article that I used for a different cluster.

Migrate Resources to a New vCenter Server (Part 1)
Migrate resources to a new vCenter Server – Methods for Migrations (Part 2)
Migrate resources to a new vCenter Server – Cross vCenter vMotion Utility (Part 3)
Migrate resources to a new vCenter Server – Unregister old vCenter Servers (Part 4)

Migrate Resources to a New vCenter Server (Part 1)

I recently had to move all resources under two vCenter Servers to two different vCenter Servers.  Then retire the source vCenter Servers. Both source vCenter Servers were in the same SSO domain. Fortunately, the source did not have many hosts and VMs and I wanted to bring over as much as I could.

I wanted to do my best not to leave anything behind at the destination vCenter Server. Most are obvious in my list below, but some may be easily forgotten if not used often. Below is a list of what I moved over and other settings to note in case moving to a completely new vCenter Server. A few have export/import wizards in vCenter and can of course be scripted for several others.

  • vDS – export/import
  • Host profiles – export/import
  • Customization specification – export/import
  • Custom attributes – output in RVTools
  • Folders – output in RVTools
  • Permissions
  • Roles
  • vCenter Settings – SMTP, database retention policy, etc
  • Alarms – custom/edited alarms
  • vCenter Server License
  • Cluster settings – HA, DRS, and EVC
  • Datastore clusters
  • Tags
  • Content libraries
  • Scheduled tasks

There are some third party apps to keep in mind. Make sure to reconfigure backups to point to the new vCenter Server. Third party plug-ins will need to be registered to the new vCenter Server.

Here are somethings not to worry about since they pertain to the hosts and remain with or without a vCenter Server.

  • Standard switches
  • Access to fiber channel storage
  • VM settings and notes

Events and tasks for a VM will persist when the VM is in the new vCenter Server. However, performance data for VMs is lost. Also, performance data, events, and tasks for hosts will be lost when a host is added to a new vCenter Server.

The next articles will focus on two different ways I migrated the hosts to the new vCenter Servers.

Migrate Resources to a New vCenter Server (Part 1)
Migrate resources to a new vCenter Server – Methods for Migrations (Part 2)
Migrate resources to a new vCenter Server – Cross vCenter vMotion Utility (Part 3)
Migrate resources to a new vCenter Server – Unregister old vCenter Servers (Part 4)

Error removing host from vDS

VMware has an article for this error, but I think it should also mention to check templates. I had a template that was not showing it was being used by the vDS. The template was still tied to the vDS since it was using a port group on the vDS before it was converted to a template. I converted template to a VM, changed the port group, and converted the VM back to a template.  Then I was able to remove the host from the vDS.

The resource ‘XXXX’ is in use. vDS NAME port XXXX is still on host NAME connected to NAME nic=4000 type-vmNic

vDS_port_error

vExpert 2018 and AWS Certified SysOps Administrator

I have two personal announcements that I am excited to share. I was selected as a VMware vExpert for 2018. One of my goals with this blog was it to assist in being recognized as a vExpert. I am happy I reached that my first year. There’s other contributions I made to the community that helped, such as the VMTN forums and VCAP Google+ community. Hopefully, I can be more active and achieve this status two years in a row.

vExpert-2018-badge

I passed the AWS Certified SysOps Administrator – Associate exam. One challenging aspect of AWS exams is the passing score changes without warning and the passing score to reach. I took the exam the last day the specific version was available and fortunately passed with a 91%.

Capture

Failed to retrieve pairs from SRM Server

I recently had a strange problem with SRM 6.5 when I tried to open it in the flash or HTML5 client.  Error said, “Failed to retrieve pairs from Site Recovery Manager Server at https://SRMaddress:9086/vcdr/vmoni/sdk. Cannot complete login due to an incorrect user name or password”. No service account passwords were recently changed. The error did not specify what user name failed.

SRMuser

I checked out SRM’s logs, which are located in C:\ProgramData\VMware\VMware vCenter Site Recovery Manager\Logs. I found only found one set of errors in the log. The message displayed another administrator, but nothing that SRM should be trying to use. A few messages in it were, “AuthorizeManager::AddCOnnection returned false for user…” and “Failed to login session…Insufficient privileges for user…”.

I could not find any information on any of the errors, except for a VMTM community post that saved me. The answer was so simple that I did not believe it would work until I tried it for myself. Daniel Soltau had a comment to login to vCenter at both sites in separate clients at the same time. It worked! SRM opened fine. I wanted to post this solution in hope that this reaches more people that have this strange SRM problem.