NSX Data Center for vSphere to NSX-T Data Center Migration – Part 3

Planning and preparation are complete and the Healthcare organization is now ready to proceed with Part 3 of the NSX Data Center for vSphere to NSX-T Data Center migration.

Researching the process for migration from NSX Data Center for vSphere to NSX-T Data Center involves the following processes.  These efforts will be covered over a series of blog posts related to each step in the processes:

  • Understanding the NSX Data Center for vSphere Migration Process – Part 1
    • Checking Supported Features
    • Checking Supported Topologies
    • Checking Supported Limits
    • Reviewing the Migration Process and the prerequisites
  • Preparing to Migrate the NSX Data Center for vSphere Environment – Part 2
    • Prepare a new NSX-T Data Center Environment and necessary components
    • Prepare NSX Data Center for vSphere for Migration
  • Migration of NSX Data Center for vSphere to NSX-T Data Center – Part 3

As they started the process in part 1, consulting the official documentation on the processes and what steps to perform are recommended.

https://docs.vmware.com/en/VMware-NSX-T-Data-Center/2.4/migration/GUID-78947686-CC6C-460B-A185-7E2EE7D3BCED.html

MIGRATION OF NSX DATA CENTER FOR VSPHERE TO NSX-T DATA CENTER

The migration to NSX-T Data Center is a multi-step process.  The steps are outlined below:

  • Import the NSX Data Center for vSphere Configuration
  • Resolve Issues with the NSX Data Center for vSphere Configuration
  • Migrate the NSX Data Center for vSphere Configuration
  • Migrate NSX Data Center for vSphere Edges
  • Migrate NSX Data Center for vSphere Hosts
  • Finish the NSX Data Center for vSphere Migration

Upon further review of each step, the organization deployed two NSX-T Data Center Edge Nodes which will be used as replacements for the NSX Data Center for vSphere Edge Services Gateways.  These Edge Nodes were deployed using the official documentation and added to the NSX-T Manager.

migration_coordinator_process_pic8

migration_coordinator_process_pic9

IMPORT THE NSX DATA CENTER FOR VSPHERE CONFIGURATION

To begin the process, the organization needs to enable the Migration Coordinator on the NSX-T Manager that they deployed.  A quick SSH session into the NSX-T Manager using the admin account, will provide the means to run the command necessary to start the Migration Coordinator service and enable the user interface that will be used for the migration in the NSX-T Manager:

migration_coordinator_start

Now that the Migration Coordinator service is running, the user interface in the NSX-T Manager will be enabled.

migration_coordinator_process_pic1

The next step in the process is to authenticate to the NSX Manager and the vCenter Server.

migration_coordinator_process_pic2

migration_coordinator_process_pic3

With the NSX Data Center for vSphere Manager and vCenter Server added in, the organization can start the import configuration step.

migration_coordinator_process_pic4

The organization sees ‘Successful’ on importing the existing configuration into NSX-T Data Center.  There is an option to ‘View Imported Topology’ which will give them a nice visual diagram of the configuration details that were imported.

migration_coordinator_process_pic5

A successful import allows the organization to proceed with the next step in the migration process

RESOLVE ISSUES WITH THE NSX DATA CENTER FOR VSPHERE CONFIGURATION

Moving to the next step, the organization is presented with all of the ‘issues’ that need to be resolved to move forward with the migration process. The total number of inputs that need to be resolved are listed and once resolved, will also be listed.

migration_coordinator_process_pic6

Several of the issues appear to be items that the organization does have already have configured.  Each issue has a recommendation by the Migration Coordinator for the organization to consider and move forward with the migration process.  The more important issues listed, are the ones that deal with the ‘EDGE’ as those issues will result in new NSX-T Data Center Edge Nodes being deployed to replace the existing Edge Services Gateways.

migration_coordinator_process_pic7

After selecting the EDGE category of issues to resolve, the organization was met with the following items to remediate before it was able to proceed to the next step.

migration_coordinator_process_pic10

  • IP addresses for TEPs on all Edge transport nodes will be allocated from the selected IP Pool. You must ensure connectivity between Edge TEPs and NSX for vSphere VTEPs.

This issue requires putting in the TEP_POOL that was created for the Edge Nodes already.

  • An NSX-T Edge node will provide the connectivity to replace NSX-v edge. Enter an IP address for the uplink.

This issue requires putting in a valid uplink IP address for the NSX-T Edge Node.  The organization will want to use the same IP address that the NSX Data Center for vSphere Edge Services Gateway is currently using since the TOR is statically routed to that IP address.

  • An NSX-T Edge node will provide HA redundancy for NSX-v edge. Enter an IP address for the uplink on this Edge node. This IP address must be in the same subnet as the uplink of the other NSX-T Edge used to replace this edge.

This issue requires putting in a valid IP address for the HA redundancy that the Edge Node will provide

  • An NSX-T Edge node will provide HA redundancy for edge replacing NSX-v edge. Enter an unused fabric ID for Edge node. See System > Fabric > Nodes > Edge Transport Nodes.

This issue requires selecting the UUID that was imported from the NSX-T Edge Nodes and selecting which one will be the replacing the NSX Data Center for vSphere Edge Services Gateway

  • An NSX-T Edge node will provide the connectivity to replace NSX-v edge. Enter an unused fabric ID for this Edge node. See System > Fabric > Nodes > Edge Transport Nodes.

This issue is similar to the one above but requires selecting the second NSX-T Edge Node UUID instead.

  • An NSX-T Edge node will provide the connectivity to replace NSX-v Edge. Enter a VLAN ID for the uplink on this Edge node.

This issue requires putting in the VLAN ID of the uplink adapter that will be used.

With all of the items resolved, the organization is ready to proceed with the actual migration process. Given that there will be some data plane outages that will need to occur during this process, the Edge Services Gateways will need to migrate to NSX-T Gateways, the organization has decided to perform the actual migration process during a scheduled maintenance window.

MIGRATE THE NSX DATA CENTER FOR VSPHERE CONFIGURATION

Pressing start, the Migration Coordinate begins migrating the configuration over to the NSX-T Data Center Manager.  This part of the process does not incur an outage as it’s a copy of the configuration.

migration_coordinator_process_pic11

Once the configuration has been copied over, the organization can now see all of the components that have been created in NSX-T Data Center from the configuration imported.

NETWORKING

The organization can see that a new Tier-0 Gateway has been created and has the routing configuration that the Edge Services Gateways had.

networking

networking2networking3

GROUPS

The organization checks the new Group objects and can see that those new Inventory objects have been created

groups1

SECURITY

Lastly, the organization checks the security objects, specifically that their Distributed Firewall and Service Composer rulesets are migrated over properly.

security1

MIGRATE NSX DATA CENTER FOR VSPHERE EDGES

The next part will incur an outage as this is the process of migrating the NSX Data Center for vSphere Edge Services Gateways over to the NSX-T Data Center Edge Nodes.  This will involve moving the IP addressing over.

migration_coordinator_process_pic12

migration_coordinator_process_pic13

Once the Edges have been migrated over, the organization can see that a new Transport Zone is created, Edge Node Cluster created, and N-VDS switch is created.

MIGRATE NSX DATA CENTER FOR VSPHERE HOSTS

The next step involves swapping the ESXi host software components for NSX Data Center for vSphere out with NSX-T Data Center.

hosts1

With the ESXi hosts now migrated the organization has now been successfully migrated from NSX Data Center for vSphere over to NSX-T Data Center.

finished1.png

Now that the Healthcare organization has migrated over to NSX-T Data Center, they can start the decommissioning of the NSX Data Center for vSphere components that are no longer needed.  The topology of their data center environment with NSX-T Data Center now looks like this.

finish_topology

Advertisements

NSX Data Center for vSphere to NSX-T Data Center Migration – Part 2

Part 2 of the NSX Data Center for vSphere to NSX-T Data Center migration for the Healthcare organization is around preparing the new NSX-T Data Center environment by deploying, installing, and configuring the necessary components.

Researching the process for migration from NSX Data Center for vSphere to NSX-T Data Center involves the following processes.  These efforts will be covered over a series of blog posts related to each step in the processes:

  • Understanding the NSX Data Center for vSphere Migration Process – Part 1
    • Checking Supported Features
    • Checking Supported Topologies
    • Checking Supported Limits
    • Reviewing the Migration Process and the prerequisites
  • Preparing to Migrate the NSX Data Center for vSphere Environment – Part 2
    • Prepare a new NSX-T Data Center Environment and necessary components
    • Prepare NSX Data Center for vSphere for Migration
  • Migration of NSX Data Center for vSphere to NSX-T Data Center – Part 3

As they started the process in part 1, consulting the official documentation on the processes and what steps to perform are recommended.

https://docs.vmware.com/en/VMware-NSX-T-Data-Center/2.4/migration/GUID-78947686-CC6C-460B-A185-7E2EE7D3BCED.html

PREPARE A NEW NSX-T DATA CENTER ENVIRONMENT AND NECESSARY COMPONENTS

Preparing a new NSX-T Data Center environment involves deploying the NSX-T Manager.  Installation of the NSX-T Manager is beyond the scope of this blog post as the official documentation has the necessary steps involved.  The key piece of information for this part of the migration process is to deploy the NSX-T Manager appliance(s) on ESXi hosts that are NOT part of the NSX Data Center for vSphere environment that’s being migrated.  The Healthcare organization deployed the new NSX-T Manager on the same hosts that the NSX Data Center for vSphere Manager is currently deployed on.

before_topology.with.nsxt

The next step is to add the vCenter Server that is associated with the NSX Data Center for vSphere environment.  NSX-T Data Center has a completely separate user-interface to manage the NSX-T installation, that will not conflict with the NSX Data Center for vSphere user-interface that’s added as a plug-in to the vSphere Client.  The steps to add the vCenter Server, Compute Manager, into NSX-T are documented in the same official documentation as part 2 of the migration process.  Once added into NSX-T, this is what the organization sees:

nsxt_compute_manager_added

There is a recommendation to add more NSX-T Managers to form a cluster for a proper production deployment, but since the Migration Coordinator is only run on one of the NSX-T Manager appliances, they can be added later.

The last step to prepare the NSX-T side of the migration process for the organization is to create an IP Pool for the Edge Tunnel Endpoints (TEP).  The organization already has a VLAN network for the VXLAN Tunnel Endpoints on the ESXi hosts for NSX Data Center for vSphere.  The VLAN is constrained using an IP range and part of the VLAN network will be assigned for the Edge TEPs as well as the host TEPs that will need to be created as well.

tep_pool_pic1

A TEP pool is created that the organization will reference during the migration

tep_pool_pic2

An IP range of addresses in the VLAN network is allocated and ensured not stepped on by any other devices in the range.

PREPARE NSX DATA CENTER FOR VSPHERE FOR MIGRATION

With the NSX-T Data Center environment setup and the steps followed, the next part of the migration process involves preparing the NSX Data Center for vSphere environment.

The first step involves configuring any hosts that might not already be added to a vSphere Distributed Switch.  The Healthcare organization has moved all of the data center hosts over to a vSphere Distributed Switch so this part of the process is not applicable to them.

The second step of this part of the migration process involves checking the Distributed Firewall Filter Export Version of the virtual machines.  This involves checking the ESXi hosts where these workloads reside and running a few simple commands.  Checking the vSphere Client, the workloads and the hosts they reside on can be seen so the organization knows which hosts to check filter export versions.

vcenter_vm_inventory

Now that the information on the virtual workload is confirmed, a simple SSH session into the ESXi host will determine if the export version is correct or needs to be modified to support the migration process.

export_filter_check

The check of the workload shows that the Distributed Firewall Filter Export Version is the correct version for this workload.  The organization can now check all of the other workloads to ensure this is the case with those as well.  This is the last step in part 2 of the process and once fully completed the Healthcare organization can moved to Part 3 and begin the actual migration process.

 

 

NSX Data Center for vSphere to NSX-T Data Center Migration – Part 1

It’s been well over a year since the last post discussing the usage of VMware NSX with the Healthcare organization.  In that time, they’ve deployed NSX controllers, and a small amount of VXLAN networks with a few workloads attached as well as continued their micro-segmentation journey, building security around their important workloads.  The release of NSX-T Data Center and the added benefits and support, have led the organization to look into migrating from NSX Data Center for vSphere to NSX-T Data Center.  NSX-T Data Center 2.4 now includes an NSX Data Center for vSphere to NSX-T Data Center Migration Coordinator that can help transition NSX Data Center for vSphere deployments over to new or existing NSX-T Data Center deployments.  The Healthcare organization has decided to pursue making use of the tool and moving their organization from NSX Data Center for vSphere to NSX-T Data Center.

Researching the process for migration from NSX Data Center for vSphere to NSX-T Data Center involves the following processes.  These efforts will be covered over a series of blog posts related to each step in the processes:

  • Understanding the NSX Data Center for vSphere Migration Process – Part 1
    • Checking Supported Features
    • Checking Supported Topologies
    • Checking Supported Limits
    • Reviewing the Migration Process and the prerequisites
  • Preparing to Migrate the NSX Data Center for vSphere Environment – Part 2
    • Prepare a new NSX-T Data Center Environment and necessary components
    • Prepare NSX Data Center for vSphere for Migration
  • Migration of NSX Data Center for vSphere to NSX-T Data Center – Part 3

With these processes in mind, it makes sense to start with by first taking a look at the official documentation on how to migrate from NSX for vSphere to NSX-T Data Center, the organization begins to document the functionality it’s currently using to compare it to the list of supported functions that the migration tool supports.

https://docs.vmware.com/en/VMware-NSX-T-Data-Center/2.4/migration/GUID-78947686-CC6C-460B-A185-7E2EE7D3BCED.html

CHECKING SUPPORTED FEATURES BY THE MIGRATION COORDINATOR

The organization has reviewed the supported features and listed them in a chart as they reviewed them to document the items, they will need to pay attention to and are relevant to their NSX Data Center for vSphere deployment:

table1

Going through the supported features, a few things were found that the organization was using that it had to make slight changes to facilitate the migration.

table2

CHECKING SUPPORTED TOPOLOGIES BY THE MIGRATION COORDINATOR

The Healthcare organization built out the following diagram to show and document the infrastructure they had built as they continued to add new features of NSX Data Center for vSphere in their environment.  This diagram is very beneficial for checking against the supported topology that the Migration Coordinator supports.

before_topology

The Healthcare organization’s network topology contains the following configurations which we can use to compare against the supported topology for the Migration Coordinator to find one that matches.

table3

The network topology leans toward following the Migration Coordinator supported topology that’s represented in this diagram from the official documentation. 

before_topology_supported

The supported topology from the official documentation supports the configurations that match the organizations current NSX Data Center for vSphere topology.

CHECKING SUPPORTED LIMITS BY THE MIGRATION COORDINATOR

The next step in the process is to review the supported limits of the Migration Coordinator against the currently configurations in the existing NSX Data Center for vSphere environment.  The Healthcare organization is a rather small deployment so their current configurations should fall into the supported limits of the Migration Coordinator.  The organization documented the following configuration information for the migration process to ensure they were within the limits:

table4

REVIEWING THE MIGRATION PROCESS AND THE PREREQUISITES

The last step in part 1 of the Migration process is to review the prerequisites that are necessary to facilitate the migration to NSX-T Data Center.  Reviewing the official documentation, the following items are required to migrate properly:

  • Deploy a new NSX-T Data Center environment
  • Import the configuration from the NSX Data Center for vSphere environment
  • Resolve issues with the configuration and deploy NSX-T Edge Nodes
  • Migrate Configuration
  • Migrate Edges
  • Migrate Hosts

After taking a look at the first part of the process, the Healthcare organization is ready to proceed to step 2 which will involve modifying their infrastructure to support the NSX-T Data Center environment they will be migrating to.

VMworld 2019 Sessions and looking forward

It’s been well over a year since I last posted anything on my blog, but since moving into the Networking and Security Business Unit at VMware and my girls getting older, I’ve been focusing on other commitments.  That being said, I have been compiling a list of things that I plan to start working on and blogging over the next several months to bring new content back to the blog.  Stay tuned, I have a massive list that I want to get posted.

Now for a bit of shameless self-promotion of my own sessions as well as ones from my peers. 🙂

We’re now just a few short weeks away from VMworld US 2019.  There are well over 200 different sessions for security including Breakout Sessions, Deep Dives, Self-Paced and Expert-led Hands-on labs, Meet the Expert, and many more.  Discussing with my peers, their sessions are filling up so if you haven’t signed up for all of your sessions take a look at the ones below and get them scheduled.

Below are the sessions that I will be presenting with one of my customers, CHRISTUS Health, my partner in EUC crime, Graeme Gordon, and last but not least my deep dive on NSX-T Guest Introspection (Endpoint Protection) that came out recently with the NSX-T 2.4 release.

SPEAKERS – Geoff Wilmington, Senior Technical Product Manager, VMware

Thursday, August 29, 09:00 AM – 10:00 AM

SPEAKERS – Graeme Gordon, Senior Staff EUC Architect, VMware and Geoff Wilmington, Senior Technical Product Manager, VMware

Tuesday, August 27, 05:00 PM – 06:00 PM

SPEAKERS – Brandon Rivera, Enterprise Infrastructure Architect, CHRISTUS Health and Geoff Wilmington, Senior Technical Product Manager, VMware

Monday, August 26, 02:30 PM – 03:30 PM

If you’re looking for other VMware security product related deep dive sessions, take a look at these from some of my peers that I highly recommend you attend.  These folks are all amazing presenters and their content is top-notch.

SPEAKERS – Stijn Vanveerdeghem, Senior Technical Product Manager, VMware

Wednesday, August 28, 03:30 PM – 04:30 PM

SPEAKERS – Ganapathi Bhat, Sr Technical Product Manager, VMware

Wednesday, August 28, 09:30 AM – 10:30 AM

SPEAKERS – Anthony Burke, Solutions Architect, VMware and Dale Coghlan, Staff Solution Architect, VMware

Wednesday, August 28, 08:00 AM – 09:00 AM

SPEAKERS – Kevin Berger, Director, Security Engineering, VMware and Chris Corde, Senior Director of Product Management, VMware

Wednesday, August 28, 01:00 PM – 02:00 PM

Last but not least, you’re definitely going to want to check out this session.  I won’t go into too many details, but Ray has some seriously cool stuff to show off.

SPEAKERS – Ray Budavari, Senior Staff Technical Product Manager, VMware

Wednesday, August 28, 02:00 PM – 03:00 PM

If we’ve never met, please don’t hesitate to come up and say ‘Hi’.