This is Part Two of configuring Site-to-Site IPSec connectivity between on-premises NSX-t and Azure. Here we are going to focus on the Azure side and learn what it takes to set up the connection between the two.
Many organizations have already realized that the public cloud only, or private cloud only, strategy is not always a good strategy. To benefit from the two worlds, a hybrid cloud strategy is the better option for many organizations.
In our last blog post, we got to where we connected our workload to our newly created segment. At this point, you probably require internet access to and from your workloads or North-South connection. This blog post will guide you through the steps to connect your NSX-t with the outside world easily and quickly using a BGP connection.
In the previous blog post, we learned how to deploy the NSX-t Manager and Edge serves. This gets us ready to start attaching our workloads to our logical networks, or NSX-t segments. Let’s together learn how to create and attach a workload to a segment.
Deploying VMware NSX-t is a straightforward and simple task, but things can become confusing when it comes to the configuration of the NSX-t environment. In this blog post, I will show you how to simplify the configuration to help you get started.
Veeam Datalabs is a powerful feature that can help your organization automatically validate your backup recoverability and integrity. However, setting Datalabs on your on-premises, or on the cloud environment, requires a very accurate network and routing configuration. Let’s simplify this topic.
vSAN is a great VMware technology; it has become a cornerstone of many VMware offerings, such as VMware on Amazon, and Azure. You can no longer ignore it, and if you still haven’t implemented it on your production environment, maybe it’s a good time now to familiarise yourself with it.
Veeam Enterprise Manager can be used by your VMware vCloud Director tenants to perform their own workload backup and restore. They can do this using the Veeam Self-Service Portal, and in this blog, I will show you how to give your tenants access to the Self-Service Portal without leaving the vCD portal?
How can you keep your ESXi hosts up to date with the latest hot-fixes and patches? Is there an easy way to compare your ESXi running build with the latest VMware released patches?
Did you upgrade to VMware vCloud Director and are now experiencing the “Unable to connect to the MKS: Internal error.”? Or you just deployed a new vCloud Director cell, and getting the MKS error when trying to connect to a tenant VM?
