CPOC Series: ACI MultiPod with Live vMotion from one Pod to another
Now that we have VMM integration completed, we’re going to take advantage of the Layer-2 connectivity between our ACI Pods, and vMotion a VM from a host in Pod1 to a host in Pod2.
Now that we have VMM integration completed, we’re going to take advantage of the Layer-2 connectivity between our ACI Pods, and vMotion a VM from a host in Pod1 to a host in Pod2.
With this video, we’ll look at how we can configure VMM integration from ACI to VMware vSphere. If you want to dive deeper and understand how to properly enable vMotion, check out our video on configuring your vMotion/vKernel networks to support vMotion! Here it is – CPOC Series: vMotion and vKernel configuration considerations between ACI … More CPOC Series: VMM integration from ACI to VMware vSphere
In order for vMotion to work properly, you have to enable a layer-2 segment between our VMware ESXi hosts to communicate (from a control-plane perspective). In this video, we’ll show you how to configure that communication.
Are you ready to explore MultiPod? With this video, we’re going to dive into MultiPod architecture, the design considerations, configuration for the IPN, and more!
Today, we’ll be talking about L3out connectivity to and from ACI. This video will not only walk through the configuration needed to establish Layer-3 connectivity, but we’ll also examine the routing tables for the ACI border leafs as well as the traditional devices on the outside of ACI.
Migration into ACI is always a hot-topic! In this video, we’ll take you through several must-see ACI migration scenarios where we do the following: Migrate a VM’s portgroup from a standard vSwitch portgroup to a an ACI DVS-managed portgroup. We’ll move the layer-3 gateway from the traditional network into ACI (and back to traditional, and … More CPOC Series: L2 and L3 Migration into ACI
In this video we explore the following: The configuration needed to establish a layer-2 connection between your traditional networking environment and the ACI Fabric Various ways to determine the location of our endpoints
Adding new bare-metal servers to ACI can be a pain. There, I said it. As an example, if we have (16) EPGs, and (4) Servers, each with (2) interfaces, it would take you around ~30 minutes to add the necessary static path bindings for all of our interfaces. That’s madness! You’ve got better things to … More Using Postman/Runner to configure static path bindings for bare-metal servers
One of the main benefits of ACI is the flexibility it offers. In particular, how easy it is to take configuration we have already completed, copy it, and re-use it for something else! For this demo, we’ll take configuration from Tenant dev, and copy the entire policy configuration to make a new Tenant called Tenant … More dev to prod: A network programmability demo with ACI
One of the most frequent topics that comes up when I am discussing ACI with customers, is, “How can we better operationalize ACI?”. In other words, how can we take what we have with ACI, and make it simpler to consume for not only ourselves, but for our Ops staff? For those new to ACI … More Operationalizing ACI: Enhanced Endpoint Tracker