Part 5 – Deploying Service Mesh

Loading

A service mesh initiates the deployment of HCX interconnect virtual appliances on both sites (also called fleet appliances).

Go to Infrastructure > Interconnect > Service Mesh > Create Service Mesh

This image has an empty alt attribute; its file name is image-270.png

Our Sites linked will appear here so click Continue

This image has an empty alt attribute; its file name is image-271.png

Select the Source Site as London and Remote Site as Cambridge

This image has an empty alt attribute; its file name is image-272.png

We can skip this configuration as we already have defined our WAN configuration as part of the previous blog.

This image has an empty alt attribute; its file name is image-273.png

This option will enable us to deploy an additional network extension appliance for scalability purposes but we will skip it here.

This image has an empty alt attribute; its file name is image-274.png

Skip the section as we aren’t using traffic engineering but this basically will allow us to throttle the WAN link speed.

This image has an empty alt attribute; its file name is image-275.png

Finally, review our topology

This image has an empty alt attribute; its file name is image-276.png

In the next screen, give the service mesh a name. All our appliances will be deployed with this prefix so give a short name and Click Finish

This image has an empty alt attribute; its file name is image-277.png

Once done, our service mesh deployment has started

This image has an empty alt attribute; its file name is image-278.png

It will take some time for all these appliances to get deployed and boot up on the cloud and on-prem

This image has an empty alt attribute; its file name is image-279.png

The workflow will show us the progress of the deployment

This image has an empty alt attribute; its file name is image-280.png

As the on-prem and cloud VMs boot up and all services are initialized, we can see the tunnel status transitioning as Up.

This image has an empty alt attribute; its file name is image-284.png

There are three appliances that will be deployed as part of the Service mesh configuration in your HCX environment.

  • Cloud Gateway (CGW)
  • WAN Optimizer
  • Layer2 Concentrator (L2C)
This image has an empty alt attribute; its file name is image-281.png

We can now see three VM’s being built as part of the service mesh deployment on Site B

This image has an empty alt attribute; its file name is image-282.png

Once the VM’s are booted up, we can see our service mesh has been linked.

This image has an empty alt attribute; its file name is image-286.png

We can see a new distributed port group added to the on-prem London site

This image has an empty alt attribute; its file name is image-287.png

We can see a new distributed port group added to the on-prem Cambridge site

This image has an empty alt attribute; its file name is image-288.png

We can also see a new datastore of size 500 TB with the name ma-ds-UUID created on both the London side and Cambridge side.

This image has an empty alt attribute; its file name is image-289.png

We can also see a new ESXi host (mobility agent host) added to the on-prem London site

This image has an empty alt attribute; its file name is image-290.png

We can also see a new ESXi host (mobility agent host) added to the on-prem Cambridge site

This image has an empty alt attribute; its file name is image-291.png

In the next blog of the HCX series, we will be discussing how to migrate VM’s using HCX.

(Visited 51 times, 1 visits today)

By Ash Thomas

Ash Thomas is a seasoned IT professional with extensive experience as a technical expert, complemented by a keen interest in blockchain technology.

Leave a Reply