VMware NSX: Physical (VLAN) TO Virtual (VXLAN) Bridging Configuration

I came across a scenario which require the connectivity between traditional workloads with legacy VLANs to virtualized networks using VXLAN, and thought of writing a quick blog post on the subject.

VMware NSX provides in-kernel software L2 Bridging capabilities that allow you to connect VLAN backed VMs to VMs connected to NSX based logical network (virtual wires).

Prior to NSX version 6.2, it was not possible to bridge a Logical Switch that was connected to a Distributed Logical Router: for that scenario it was required to connect the Logical Switch directly to an Edge Services Gateway.1

With NSX 6.2 on a given NSX Logical Switch, Distributed logical routing can co-exist with L2 bridging.

2

In my scenario, I have a database VM “AMS” which is connected to VLAN backed port group “VxRACK MGMT” with a VLAN ID 36

3.png

You can see Database VM “AMS” is connected to VxRACK MGMT port group:

4

And an Application VM “App-Windows” connected to “App-Tier” VxLAN backed logical switch (DLR).

7

8

To verify that “AMS” is isolated and cannot ping the application VM, let me try to ping the default gateway of application VM.

9

10.png

It’s been verified that the VM is isolated and the L2 Bridging is not configured yet.

Now let’s configure NSX L2 bridging:

We will enable NSX L2 Bridging between VLAN 36 and the “App-Tier” Logical Switch, so that VM “AMS” will be able to communicate with the rest of the network. With NSX-V 6.2 is now possible to have a L2 Bridge and a Distributed Logical Router connected to the same Logical Switch. This represents an important enhancement as it simplifies the integration of NSX in brownfield environments, as well as the migration from legacy to virtual networking.

11

Select the “App-Tier” logical switch and click ok:

12

Click on Distributed port group and select “VxRACK-MGMT” port group:

13To enable the L2 Bridging, click on the Publish Changes button, and wait until the page refreshes.

14

Verify the published configuration. You will notice the “Routing Enabled” message: it means that this L2 Bridge is also connected to a Distributed Logical Router, which is an enhancement in NSX-V 6.2.15.png

Let’s verify L2 connectivity between the “AMS” VM, attached on VLAN 36, and the machines connected “App-Tier” Logical Switch (App-Windows). First let me ping the default gateway of “App-Tier” logical switch:

16

Boom…….ping successful: we have verified connectivity between a VM attached on VLAN 36 and the Distributed Logical Router that is the default gateway of the network, through a L2 Bridge provided by NSX!

Now let’s ping the Application VM “App-Windows” from Database VM “AMS” which is on VLAN 36:

17

18.png

NSX L2 Bridging has been verified successfully. I hope you enjoyed the blog, if you think it’s worth sharing, please do.  Keep learning and sharing knowledge.

VMware AppVolumes 3.0 Deployment and…

VMware AppVolumes 3.0 Deployment and configuration Part 1 – Saurav Issar

VMware AppVolumes 3.0 Deployment and…

I had setup VMware App Volume 3.0 environment in my lab last week and want to share my experience. VMware App Volumes 3.0 enables you to deploy applications to users. These users may be widely separated in space, be using different operating systems, or using different versions of applications. VMware App Volumes 3.0 also enables…Read More


VMware Social Media Advocacy

VMware AppVolumes 3.0 Deployment and configuration Part 3

In this blog post , i will cover the final AppStack creation and assignment to the end users .

Now you are ready to create AppStack using AppCapture . Make sure to disable the UAC (user account control) in windows, if you have not done so already. Instructions for turning off UAC in windows 7 may be found at:

https://support.microsoft.com/en-us/help/17228/windows-protect-my-pc-from-viruses#1TC=windows-7

open the command prompt and change the directory to c:\Program Files (x86)\VMware\AppCapture.exe (64 bit machine) or c:\Program Files\VMware\AppCapture.exe (32 bit machine)

Run the AppCapture.exe command: AppCapture.exe /n appstack_name

In this example , I will create a AppStack for Google Chrome web browser.28

Do not close the command prompt and install the application that you want to add to AppStack. Once done, hit enter twice to complete the AppStack creation process. (Note: system will reboot to complete the AppStack creation process)29

Once we get the above  message , copy the content form (including VMDK and json file)“c:\ProgramData\VMware\AppCapture\appvhds”  to a file share .

The next step is to configure the Application file share in AppVolume web console . log in to AppVolume web console  , click Settings – Locations – click File Share tab – click the new button and add the file share information:

  • Name
  • Type – chose application from the menu
  • Source path in \\share IP\sharename format30Anytime you add applications or customizations to a file share you should synchronize the file share in the AppVolume 3.0 console. Login to AppVolume console, go to settings – locations, click file share. Select the file share you want to sync, click and select sync now.3132Now that AppStack is created, added to the file share and synced. It’s time to assign the app stack to active directory users and group.

    1 Bring up the Assignments page. You can do this in either of the following ways: a From the Getting Started page, click Go in the Create New App Assignment section. b Click Assign in the menu bar on the left. The Assignments page loads.

    2 Click New. The New Assignment panel appears.

    3 Click Get Started! Under Applications. The New Applications Assignment screen appears33Select the application in the AppStack and click next.

  • 34Add the active directory user or user group to which you want to assign the application , and click next.35

    Take a look at the input parameters and click on submit.

    To check wheatear the AppStack is provisioned properly, I will login as a user which is a member of “View Users” group to which I have assigned the AppStack and see whether google chrome is provisioned or not.373840

    Luckily It worked perfectly fine  🙂

    Let me know your feedback on this and share if you find it worth sharing. Tc.

VMware AppVolumes 3.0 Deployment and configuration Part 3

In this blog post , i will cover the final AppStack creation and assignment to the end users .

Now you are ready to create AppStack using AppCapture . Make sure to disable the UAC (user account control) in windows, if you have not done so already. Instructions for turning off UAC in windows 7 may be found at:

https://support.microsoft.com/en-us/help/17228/windows-protect-my-pc-from-viruses#1TC=windows-7

open the command prompt and change the directory to c:\Program Files (x86)\VMware\AppCapture.exe (64 bit machine) or c:\Program Files\VMware\AppCapture.exe (32 bit machine)

Run the AppCapture.exe command: AppCapture.exe /n appstack_name

In this example , I will create a AppStack for Google Chrome web browser.28

Do not close the command prompt and install the application that you want to add to AppStack. Once done, hit enter twice to complete the AppStack creation process. (Note: system will reboot to complete the AppStack creation process)29.png

Once we get the above  message , copy the content form (including VMDK and json file)“c:\ProgramData\VMware\AppCapture\appvhds”  to a file share .

 

The next step is to configure the Application file share in AppVolume web console . log in to AppVolume web console  , click Settings – Locations – click File Share tab – click the new button and add the file share information:

  • Name
  • Type – chose application from the menu
  • Source path in \\share IP\sharename format30

    Anytime you add applications or customizations to a file share you should synchronize the file share in the AppVolume 3.0 console. Login to AppVolume console, go to settings – locations, click file share. Select the file share you want to sync, click and select sync now.

    31.png32.pngNow that AppStack is created, added to the file share and synced. It’s time to assign the app stack to active directory users and group.

    1 Bring up the Assignments page. You can do this in either of the following ways: a From the Getting Started page, click Go in the Create New App Assignment section. b Click Assign in the menu bar on the left. The Assignments page loads.

    2 Click New. The New Assignment panel appears.

    3 Click Get Started! Under Applications. The New Applications Assignment screen appears33.png34.png

    Select the application in the AppStack and click next.35

    Add the active directory user or user group to which you want to assign the application , and click next.36.png

    Take a look at the input parameters and click on submit.

    To check wheatear the AppStack is provisioned properly, I will login as a user which is a member of “View Users” group to which I have assigned the AppStack and see whether google chrome is provisioned or not.37.png3840.png

    Luckily It worked perfectly fine  🙂

    Let me know your feedback on this and share if you find it worth sharing.

VMware AppVolumes 3.0 Deployment and configuration Part 2

In the First part of blog , i have covered the App Volume appliance deployment , configuration , AD and vCenter Server integration.

In this part i will cover the App Volume agent installation and App Capture configuration.

App Volume agent installation on the desktop machine:

In order to deliver application to end-user machine, App Volume agent along with horizon view agent needs to be installed on the machines.

Simply run the App Volume agent exe file and follow the installation wizard.19.png20.png21.png222324.png

Managing Application for Deployment with AppCapture:

AppCapture is used to create AppStack for provisioning applications to users. Before you can assign applications to users using App Volume you must capture and package the application into AppStack using the AppCapture utility. Then we manually copy the Appstacks to a file share.

Note: Make sure you install App Capture on a machine with no App Volume and Horizon View agent installed.

The installation of AppCapture is straight forward, simply follow the wizard and complete the installation.

Note: You must capture application from the same OS into which you mount them. for e.g. if users are operating a windows 10×64 OS , you must capture the application using a similar or an identical base OS Windows 10×64 image.25.png26.png27.png

In the third part , i will cover the AppStack creation and assignment to the end users.

VMware AppVolumes 3.0 Deployment and configuration Part 1

I had setup VMware App Volume 3.0 environment in my lab last week and want to share my  experience.

VMware App Volumes 3.0 enables you to deploy applications to users. These users may be widely separated in space, be using different operating systems, or using different versions of applications. VMware App Volumes 3.0 also enables you to monitor application usage.

First thing to setup the App Volume is to deploy the App Volume virtual appliance.
System Requirements for App Voulme virtual appliance are below:
– vSphere 6.0U1 and above (previous versions of vSphere are not supported)
– 4 vCPUs
– minimum of 80 GB disk space
– minimum of 4 GB memory

Lets get started now with Deployment of App volume virtual appliance and initial configuration:

Quite straight forward process , simply deploy the App Volume OVA and follow the installation wizard.

12345678910

After the deployment is done , Login to the App Volumes console using default “username: root” and “password: 123”. Once you login you will be prompted to set new pas sword.Subsequently you will be asked to configure the active directory.1112

Once done click on domain bind.  Once the binding is complete, you will need to add a super administrator user group for App Volume appliance from your active directory domain.13

Now you can login to App Volume web interface using the user group added in the previously.14

Next step is to integrate vCenter Server to the App Volume.15161718.png

Now you should be able to add vCenter server without any error.

In the Next Blog post i will cover the App Volume Agent installation and App Capture installation and configuration.