Build a virtual network lab with Ravello Systems and Cumulus Networks on AWS or Google Compute Engine.
Implementing IPv6 in your network does not require tearing down your aging IPv4 network and replacing it with a new IPv6-enabled network. Instead it is possible - and often wise - to run the IPv4 and IPv6 networks in parallel in what the industry calls a "dual-stack" network, thus adding IPv6 capabilities to your network's existing IPv4 capabilities. While such an endeavor is certainly not trivial, it might be easier than your think. The following article introduces a six step plan for implementing IPv6. It has served me well in past deployments and will hopefully give you some ideas and guidance.
DNS-based Authentication of Named Entities (DANE, RFC6698) allow X.509 certificates, commonly used for Transport Layer Security (TLS), to be bound to DNS names using Domain Name System Security Extensions (DNSSEC). DNSSEC assures users that the information they obtain from DNS - in this case the fingerprint of the X.509 certificate came from the correct source, was complete and its integrity was not compromised during the transfer.
ThousandEyes is a SaaS offering for monitoring SaaS application and website performance and provides deep insight into the underlying network including IPv6.
Install the VMware NSX plugin into the vSphere OpenStack Virtual Appliance (VOVA) for a setup including VMware vSphere, VMware NSX and OpenStack.
Create virtual networks and launch a VM instance for a setup including VMware vSphere, VMware NSX and OpenStack.
Import and configure the VMware vSphere OpenStack Virtual Appliance (VOVA) for a setup including VMware vSphere, VMware NSX and OpenStack.
Install and configure the Open vSwitch inside the ESXi hosts for a setup including VMware vSphere, VMware NSX and OpenStack.
Create and configure the VMware NSX cluster for a setup including VMware vSphere, VMware NSX and OpenStack.
Install and configure the VMware NSX appliances for a setup including VMware vSphere, VMware NSX and OpenStack.
Introduction to a series explaining how to use VMware vSphere with VMware NSX and OpenStack.
Example of a physical network design for VMware NSX, taking into consideration fault containment, traffic isolation. multi-tenant security and redundancy.
Using the simple to remember IPv6 link-local address fe80::1 as the default gateway.
Using Arista's underlying Linux OS to configure a 6in4 tunnel for IPv6 connectivity.
Arista EOS is based on a Linux kernel and provides full and open access to a Linux shell, allowing installation and use of Linux based management and troubleshooting tools. In this short post I want to show you two use cases where this capability comes in extremely handy in the daily network management work.
EOS is released as a single image that supports all of their hardware platforms. But that same single image can also be run in a virtual machine! While a great article on "Building a Virtual Lab with Arista vEOS and VirtualBox" already exists, I wanted to accomplish the same with vSphere 5.x.
The topic of measuring network throughput between network devices comes up quite frequently: It ranges from users claiming (and often blaming) that the 100 Mbps Internet uplink in reality is only 10 Mbps or being surprised why they can't transfer that multi-gigabyte file via FTP faster between data center locations. Let's have a look behind the scenes of network throughput measurement and understand why users are actually measuring something completely different, but also how to get more "performance" out of these connections.
Walk-through instructions for a project to automatically save the text-based configuration of network devices and make them browse-able via a web-based interface. The solution will also discover configuration changes and notify the network operations team of these changes.