Skip to main content

1. Learning NSX-T: Introduction

VMware NSX is one of the most sensational product that VMware produced 5 years back post Niciria acquisition and over the years this product has just gone better and better. NSX revolutionized the SDDC by adding the SDN capabilities and they way how SDN was used before NSX. 

One of the major limitation of NSX-V was that it can be used only with vSphere and not with other platforms and customers were continuously demanding for a version of NSX that can be integrated with non-vSphere platforms.

To overcome this challenge, VMware came up with NSX-T which is version of NSX for non-vSphere based infrastructure. This version of NSX can be integrated with other hypervisiors such as KVM and application frameworks such as Redhat Openshift, Docker/Containers and Pivotal. In addition to these platforms, you can integrate your vSphere platform as well with NSX-T.

As we know that in NSX-V, vCenter was centralized management plane but NSX-T has its own management interface. As of now NSX-T doesn’t offer the same full feature set as NSX-V but VMware is continuously making enhancements to this product to make it more robust.

NSX-T when initially released was offering features such as logical routing, logical switching, micro-segmentation for VMs and a distributed firewall. But with the latest release of NSX-T, VMware added network virtualization and micro-segmentation for containers.

The latest version of NSX-T is 2.2.0 and to know more about the capabilities offered by this version, please see https://docs.vmware.com/en/VMware-NSX-T-Data-Center/2.2/rn/VMware-NSX-T-22-Release-Notes.html


Comments

Popular posts from this blog

Dell EMC VxRail – VMware Virtual SAN Stretched Cluster

Logical Diagram of VMware vSAN Stretched Cluster Physical Diagram of VMware vSAN Stretched Cluster Last week I deployed a test environment of VMware vSAN Stretched Cluster which is running on Dell EMC VxRail Appliance. In this post we will describe how to setup VMware vSAN Stretched Cluster on Dell EMC VxRail Appliance. Above figure is the high level of physical system diagram. In site A/B there are six VxRail Appliances and two 10GB Network Switch which are interconnected by two 10GB links, and each VxRail Appliance has one 10GB uplink connects to each Network Switch. In site C, there are one vSAN Witness host and one 10GB Network Switch. For the details of configuration of each hardware equipment in this environment, you can reference the followings. Site A (Preferred Site) 3 x VxRail E460 Appliance Each node includes 1 x SSD and 3 x SAS HDD, 2 x 10GB SFP+ ports 1 x 10GB Network switch Site B (Secondary Site) 3 x VxRail E460 Appliance Each node includes 1 x SSD and...

VxRail 4.0 – Scale Out

The above is the physical diagram of VxRail Cluster (3 nodes). In this post I will show how to add one VxRail Appliance into this VxRail Cluster (From 3 nodes to 4 nodes). NOTE: The model of each VxRail Appliance is E460. Before the node expansion, you need to verify each Appliance is running in health in dashboard of VxRail Manager. The above is the final physical diagram of VxRail Cluster after scale out. Now we start the node expansion. You have just mounted a new VxRail Appliance (E460) and cabled it up to the top of each rack switch. When you power it on you can see a notification appear in the top left corner of VxRail dashboard. Click “ Add Node “. When you initially configured your VxRail Appliance, you specified an IP pool for ESXi, vMotion and vSAN. You can see that there available IP addresses in these pools, so the only additional action is to set an ESXi password. Click the scroll bar, then click the “ ESXi Password “. Enter the  ESXi  and ...

UEFI Secure Boot with ESXi 6.5

UEFI Secure Boot: UEFI, or Unified Extensible Firmware Interface, is a replacement for the traditional BIOS firmware. In UEFI, Secure Boot is a “protocol” of the UEFI firmware. UEFI Secure boot ensures that the boot loaders are not compromised by validating their digital signature against a digital certificate in the firmware. UEFI can store whitelisted digital certificates in a signature database (DB). There is also a blacklist of forbidden certificates (DBX), a Key Exchange Keys (KEK) database and a platform key. These digital certificates are used by the UEFI firmware to validate the boot loader.  Boot loaders are typically cryptographically signed and their digital signature chains to the certificate in the firmware.The default digital certificate in almost every implementation of UEFI firmware is a x509 Microsoft UEFI Public CA cert. Most of the UEFI implementations also allows the installation of additional certificate in the UEFI firmware and UE...