#network #nsx #sddc #software-defined

NSX-T 2.0 General Availability

The 2.0 version of NSX-T was released yesterday (September, 7th 2017). \o/ NSX-T is focused on emerging application frameworks and architectures that have heterogeneous endpoints and technology stacks. In addition to vSphere hypervisors, these environments include other hypervisors such as KVM, containers, and bare metal. What’s New in NSX-T 2.0? NSX-T 2.0 introduces a new platform architecture that meets customer needs for flexible, scalable, and agile network and security infrastructure. ...

#dfw #nsx

Open VM Tools is now supported with NSX Distributed Firewall

Although a recurrent request, the use of Open VM Tools on guest or workload virtual machines has never been validated with NSX Distributed Firewall. It got quite unnoticed, but a small sentence in the NSX for vSphere 6.3.2 Release Notes changed the game: **Starting in NSX 6.3.2, Open VM Tools is supported with Distributed Firewall.** In NSX, VMware Tools are required to translate vCenter objects into IP. Indeed, the underlying NSX distributed firewall rules configured within the kernel are IP-based, despite being abstracted as objects at the configuration layer so it is a requirement to run VMware tools in all virtual machines so their addresses are reported into vCenter. ...

#api #vcenter #vsphere

New vSphere 6.5 REST API and API Explorer

vSphere 6.5 (released last week) introduces a new REST API providing a much more modern, simplified and developer-friendly API. The areas covered by the REST API are currently limited to vCenter Server Appliance (vCSA) management, Content Library and VM operations and lifecycle (check below for a more complete list). Also, to make our life easier, this new API is self-documented via an API Explorer embedded in the vCenter Server Appliance. ...

#nsx #operations #sddc

Force HA Failover on NSX Edges

When NSX 6.2.3 was released earlier this year, a sentence in the release notes about failover caught my attention. **NSX Edge — On Demand Failover**: Enables users to initiate on-demand failover when needed. Well, since that moment, NSX 6.2.3 has been replaced by NSX 6.2.4 (sort of), but this statement is still true. About NSX Edge High Availability Before jumping straight into the subject, I would like to come back on the HA feature itself. ...

#api #nsx

Configuring NSX Edge Services in Async Mode via API

I was reading through the NSX API Guide recently and a section caught my attention: Configuring Edge Services in Async Mode. When configuring edge services asynchronously, accepted commands return an Accepted status (HTTP response status code 202) and a jobId (or taskId). The advantage of the async mode is that APIs are returned very fast and actions are done behind the scene. This asynchronous mode is working with any 4. ...