New credentials, new job, now what?

New credentials, new job, now what?

2014 was a great year for me. I had the privilege to be part of the “VMware NSX Ninja” program, aiming at preparing the first group of VCDX-NV. This led me to earn my second VCDX in July. I’ve also passed an early version of the VCIX-NV in the
Integrating vSphere and NSX API’s with Python (2/2)

Integrating vSphere and NSX API’s with Python (2/2)

This post will focus on the last tasks mentioned in my Disaster Recovery scenario: Recover VMs at the simulated DR site. Connect VMs to the appropriate Logical Switch. Boot VMs and test connectivity. Check route updates on the physical network. Before going further you may want to check how to
Integrating vSphere and NSX API's with Python (1/2)

Integrating vSphere and NSX API's with Python (1/2)

It is common knowledge that NSX has great orchestration capabilities when leveraging API's. Everything you can do via the GUI can be achieved through API calls, and further integrated into some scripts. If you plan to move down this road (and you should, really!!), there are two questions you may

VMware NSX Use Case – Simplifying Disaster Recovery (Part 2)

Deploying the environment Now let's take a closer look at how to create this environment. The following picture represents the vSphere logical architecture and the associated IP scheme… … and the networks mapping: First of all you have to create three vSphere clusters: one Management Cluster and two Compute Clusters, as
VMware NSX Use Case - Simplifying Disaster Recovery (Part 1)

VMware NSX Use Case - Simplifying Disaster Recovery (Part 1)

This series of posts describes a specific use case for VMware NSX in the context of Disaster Recovery. The goal is to demonstrate the routing and programmability capabilities through a lab scenario. This first part presents the NSX components and details the use case. The second part will show how
Design considerations for vSphere and OTV in stretched clusters environments (Part 2)

Design considerations for vSphere and OTV in stretched clusters environments (Part 2)

This article is the second part of a series dealing with OTV and vSphere network design impacts. I will first cover the scenario where vSphere hosts are attached to the network at the access layer, to a pair of Nexus 5000. Then we will look at multi-nic vMotion impact on

Design considerations for vSphere and OTV in stretched clusters environments (Part 1)

In this series of posts, I’m going to focus on different scenarios involving Cisco OTV in a VMware vSphere environment, and try to demonstrate the potential impacts of design decisions for both technologies. These scenarios include common configurations at network physical and virtual access layer, often used in reference