<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>NetworkStatic</title><link>https://networkstatic.net/</link><description>Recent content on NetworkStatic</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 10 Apr 2023 22:52:16 +0000</lastBuildDate><atom:link href="https://networkstatic.net/index.xml" rel="self" type="application/rss+xml"/><item><title>AI and Networking</title><link>https://networkstatic.net/ai-and-networking/</link><pubDate>Mon, 10 Apr 2023 22:36:31 +0000</pubDate><guid>https://networkstatic.net/ai-and-networking/</guid><description>&lt;h3&gt;AI and Networking&lt;/h3&gt;&#10;&lt;p&gt;Bill Gates recently called the development of AI as fundamental of a creation as the microprocessor, the personal computer, the Internet, and the mobile phone. He is most likely right. OpenAI found that around 80% of the U.S. workforce could have at least 10% of their work tasks affected by the introduction of large language models (LLMs). If you are in technology that will be more like 100%.&lt;/p&gt;</description></item><item><title>Getting Started with the Rust Programming Language</title><link>https://networkstatic.net/getting-started-with-the-rust-programming-language/</link><pubDate>Thu, 02 Jan 2020 15:58:54 +0000</pubDate><guid>https://networkstatic.net/getting-started-with-the-rust-programming-language/</guid><description>&lt;h3&gt;Getting Started with the Rust Programming Language&lt;/h3&gt;&#10;&lt;p&gt;A programming language that has begun picking up momentum in the community lately is Rust. This is a guide aimed at helping folks get started with the Rust Programming Language. Rust has been around for a while with a stable v1.0 shipping in 2015. Rust initially came from Mozilla who maintain the multi-million line C++ codebase in Firefox that has bugs that Mozilla devs speak openly about being unfixable due to the unintended consequences up and down stream as a result. Rust does an amazing job via memory ownership and strict compilation rules, that address the massive problem of memory safety bugs and CVEs. In short, Rust is the overbearing parent you need in your life.&lt;/p&gt;</description></item><item><title>Open Source Flow Monitoring and Visualization</title><link>https://networkstatic.net/open-source-flow-monitoring-and-visualization/</link><pubDate>Wed, 11 Dec 2019 00:46:48 +0000</pubDate><guid>https://networkstatic.net/open-source-flow-monitoring-and-visualization/</guid><description>&lt;h3&gt;Open Source Flow Monitoring and Visualization&lt;/h3&gt;&#10;At the heart of any reasonably sized network, should be a solid strategy around flow collection, querying and visualization. Proper use of flow logs are crucial to SecOps/NetOps from triaging attacks to capacity planning and traffic trending. I remember some 20 years ago, the first time I saw flow logs being visualized in rrdtools it was pretty close to magic. I wanted to recreate that &lt;a href="https://github.com/nerdalert/nfsen-dockerized" target="_blank" rel="noopener noreferrer"&gt;environment&lt;/a&gt; a few years back and it felt pretty dated.&#10;&lt;p&gt;Recently, I decided to poke around and see what’s new in the open source monitoring space of sFlow/NetFlow/IPFIX and ran across a couple of interesting projects, &lt;a href="https://github.com/cloudflare/goflow" target="_blank" rel="noopener noreferrer"&gt;cloudflare/goflow&lt;/a&gt; (CloudFlare OSS), &lt;a href="https://github.com/VerizonDigital/vflow" target="_blank" rel="noopener noreferrer"&gt;VerizonDigital/vflow&lt;/a&gt; (Verizon OSS) and &lt;a href="https://github.com/robcowart/elastiflow" target="_blank" rel="noopener noreferrer"&gt;robcowart/elastiflow&lt;/a&gt; (also deserving of a mention here is &lt;a href="https://github.com/pmacct/pmacct" target="_blank" rel="noopener noreferrer"&gt;pmacct&lt;/a&gt;). GoFlow and vFlow are both written in Go which I like and both appear to be highly scalable collectors. What they don’t have are built-in front ends so will require a bit more work to extract interesting data.&lt;/p&gt;</description></item><item><title>Measuring Network Bandwidth using Iperf and Docker</title><link>https://networkstatic.net/measuring-network-bandwidth-using-iperf-and-docker/</link><pubDate>Tue, 02 Jan 2018 23:38:59 +0000</pubDate><guid>https://networkstatic.net/measuring-network-bandwidth-using-iperf-and-docker/</guid><description>&lt;h3&gt;Measuring Network Bandwidth using Iperf and Docker&lt;/h3&gt;&#10;&lt;p&gt;At the heart of any network engineer&amp;rsquo;s toolkit, are applications that let you peer into the network for performance, congestion and capacity planning. One of the thoroughbreds in the open source network tools collection is iperf. Iperf has been around for a long time. The good folks at &lt;a href="https://www.es.net" target="_blank"&gt;ESnet&lt;/a&gt; updated the original iperf with new features and what not and released it as iperf3.&lt;/p&gt;</description></item><item><title>GoBGP - A Control Plane Evolving Software Networking</title><link>https://networkstatic.net/gobgp-control-plane-evolving-software-networking/</link><pubDate>Tue, 29 Mar 2016 05:15:17 +0000</pubDate><guid>https://networkstatic.net/gobgp-control-plane-evolving-software-networking/</guid><description>&lt;h3&gt;GoBGP - A Control Plane Evolving Software Networking&lt;/h3&gt;&#10;If I have talked to you over the past year or two about networking, odds are I have mentioned a project to you called &lt;a href="http://osrg.github.io/gobgp/" target="_blank"&gt;GoBGP&lt;/a&gt;. If we have spoken a lot, you are probably sick of me talking to you about GoBGP :) There is a reason, it's because GoBGP is a missing link in networking that has been for a long time. GoBGP is a project from some really smart and just as importantly friendly, community minded folks at NTT Communications (largest telco in Japan). The software group that does the software is &lt;a href="https://github.com/osrg/gobgp" target="_blank"&gt;OSRG&lt;/a&gt; and the same organization that did RYU the SDN controller that was popular in OpenStack deployments. &lt;a href="http://osrg.github.io/gobgp/" target="_blank"&gt;GoBGP&lt;/a&gt; is a BGP focused routing daemon that is incredibly flexible, written in Go and perfect for those both looking for practical control plane SDN solutions or network engineers looking to figure out what the hell their future will look like and where to start evolving in a software driven age. The tutorial will also instruct you how to install the Go programming language and environment in order to pull down and build the GoBGP binaries.&#10;&lt;p&gt;There are a few software router implementations, all useful in their own right. The first reason I prefer GoBGP is its written in Go, which gives you many of the benefits of C with a lower barrier to entry then C along with great concurrency support along with great native tooling. More on reasons to use Go &lt;a href="https://www.youtube.com/watch?v=FTl0tl9BGdc" target="_blank"&gt;here&lt;/a&gt;. GoBGP is also completely cross platform and does not have any hardware specific dependencies. Secondly, its architecture is outstanding and very modular unlike the monolithic alternatives. As an example, they implemented a draft I am huge fan of from &lt;a href="https://twitter.com/petrlapu" target="_blank"&gt;Petr Lapukhov&lt;/a&gt; of Facebook named &lt;a href="https://tools.ietf.org/html/draft-lapukhov-bgp-opaque-signaling-00" target="_blank"&gt;BGP for opaque signaling&lt;/a&gt; in a couple of days without needing to change anything internally. I see this level of modularity at work and recognize the level of experience required to design such nice architectures like the OSRG team have put together to seamlessly support EVPN, Opaque Flowspec, RRs, RPKI, BMP to name a few.&lt;/p&gt;</description></item><item><title>Configuring Macvlan and Ipvlan Linux Networking</title><link>https://networkstatic.net/configuring-macvlan-ipvlan-linux-networking/</link><pubDate>Mon, 28 Mar 2016 22:26:23 +0000</pubDate><guid>https://networkstatic.net/configuring-macvlan-ipvlan-linux-networking/</guid><description>&lt;h3&gt;Configuring Macvlan and Ipvlan Linux Networking&lt;/h3&gt;&#10;&lt;p&gt;Macvlan and Ipvlan are both Linux type networking interfaces that are both supported by the Linux kernel. They are unique for a few different reasons. One thing that makes them both very attractive is they do not use bridges in their implementation and natively namespace aware. It solves some painful problems such as getting access to a gateway from a bridge that can alleviate a need for PAT/NAT and increased performance as a result of less overhead.&lt;/p&gt;</description></item><item><title>Time to Ditch the Definition of SDN</title><link>https://networkstatic.net/time-to-ditch-the-definition-of-sdn/</link><pubDate>Sun, 16 Aug 2015 21:44:35 +0000</pubDate><guid>https://networkstatic.net/time-to-ditch-the-definition-of-sdn/</guid><description>&lt;h2&gt;Time to Ditch the Definition of SDN&lt;/h2&gt;&#10;While at a stoplight looking at the random news feeds on Linkedin I ran across a post of a recent &lt;a href="https://www.opennetworking.org/?p=1830&amp;option=com_wordpress&amp;Itemid=316" target="_blank"&gt;blog post&lt;/a&gt; by the ONF and the subsequent conversation where my friend &lt;a href="http://blog.ipspace.net" target="_blank"&gt;Ivan Pepenlnjak&lt;/a&gt; commented. So I threw in my two cents and quickly regretted it because Linkedin has an amazing ability to frustrate me as it updated the comment counter but ate my post and then disappeared. Awesome. So I'm going to post what I remember of it here. Let me also disclaim this isn't a response to a response and so on, the blog post simply mustered up enough energy in me to write a disappearing comment on LinkedIn. I really like Dan Pitt, few have made such a difference in networking by promoting new ways to think about networking like Dan has. He is merely pointing out the accepted definition of SDN, not defining it. My disagreement of the opinionated definition of SDN is simply where my thinking has landed after being involved in both ops/dev on both sides of the approach. We have centralized with one or two protocols vs whatever makes sense to the use case.&#10;&lt;p&gt;Quick review, OpenFlow is not a framework, architecture or philosophy, but a wire protocol that can be used to program a local or remote forwarding tables of an IP endpoint (presumably dwdm lambdas now too last I read the draft). SDN is where things get squirrely. There is this long running assumption that SDN is only SDN if it uses a centralized controller and programs remote endpoints/datapaths. I&amp;rsquo;m as guilty as the rest, before trying to guess the state of remote endpoints from a controller to deal with the nearly infinite number of states an endpoint can be in. I have also used that definition where it was convenient being one controller with lots of remote endpoints. If that works for you go nuts. Im not saying its bad in some cases, the traffic alignment of wireless controllers often make a lot of sense to have a central cluster to insert into the datapath since it needs to traverse that path anyways etc. Of course even here good opposing arguments can be made.&lt;/p&gt;</description></item><item><title>Docker on Google Compute Engine Using Docker Machine</title><link>https://networkstatic.net/docker-on-google-compute-engine-using-docker-machine/</link><pubDate>Sat, 13 Jun 2015 01:26:59 +0000</pubDate><guid>https://networkstatic.net/docker-on-google-compute-engine-using-docker-machine/</guid><description>&lt;h3&gt; Docker on Google Compute Engine Using Docker Machine&lt;/h3&gt;&#10;Next up in Using Docker Machine across &lt;a href="https://networkstatic.net/normalizing-the-cloud-with-docker-machine/" target="_blank"&gt;private and public clouds&lt;/a&gt;, is Google Compute Engine (GCE).&#10;&lt;hr /&gt;&#10;&lt;p&gt;As with the other posts, a diagram of how I view the importance of a Docker Machine abstraction.&lt;/p&gt;</description></item><item><title>Building Network Tools using Docker</title><link>https://networkstatic.net/building-network-tools-using-docker/</link><pubDate>Mon, 01 Jun 2015 10:22:09 +0000</pubDate><guid>https://networkstatic.net/building-network-tools-using-docker/</guid><description>&lt;h3&gt;Building Network Tools using Docker&lt;/h3&gt;&#10;&lt;p&gt;I am going to start pushing out an app every month that fixes some problem in networking. In this case I hacked it up over the past couple of weekends, but other times it will just be me using someones open source awesomeness and demoing it.&lt;/p&gt;</description></item><item><title>Running Docker Machine on Digital Ocean</title><link>https://networkstatic.net/running-docker-machine-on-digital-ocean/</link><pubDate>Mon, 11 May 2015 00:23:42 +0000</pubDate><guid>https://networkstatic.net/running-docker-machine-on-digital-ocean/</guid><description>&lt;h3&gt; Running Docker Machine on Digital Ocean &lt;/h3&gt;&#10;&lt;p&gt;Continuing the series on &lt;a href="https://networkstatic.net/normalizing-the-cloud-with-docker-machine/" target="_blank"&gt;cloud provider examples using Docker machine&lt;/a&gt;, up next is Digital Ocean.&lt;/p&gt;&#10;&lt;hr&gt;&#10;As with the other posts here is a diagram of how I view Docker Machine usage.&#10;&lt;p&gt;&lt;a href="https://cloud.githubusercontent.com/assets/1711674/7408653/ffad6dbe-eeec-11e4-85b2-9fef61d02818.gif"&gt;&lt;img src="https://cloud.githubusercontent.com/assets/1711674/7408653/ffad6dbe-eeec-11e4-85b2-9fef61d02818.gif" alt="Docker Machine" width="645" height="675" class="aligncenter size-full wp-image-7574" /&gt;&lt;/a&gt;&lt;/p&gt;</description></item><item><title>10 Examples of how to get Docker Container IP Address</title><link>https://networkstatic.net/10-examples-of-how-to-get-docker-container-ip-address/</link><pubDate>Sun, 10 May 2015 09:04:05 +0000</pubDate><guid>https://networkstatic.net/10-examples-of-how-to-get-docker-container-ip-address/</guid><description>&lt;h3&gt;10 Examples of how to get Docker Container IP Address&lt;/h3&gt;&#10;&lt;p&gt;One thing that is so much fun about the need virtualization paradigm we are heading towards is that in the age of &amp;ldquo;software defined&amp;rdquo;, the flexibility of how to do things with infra are much more like programming then working with highly opinionated traditional infrastructure. Along that thread, here are 10 different ways to get a container or docker-machine address using the Docker/Docker-Machine CLI. This doesn&amp;rsquo;t even go into the remote http API which is slick because the client commands below are actually making calls to the verioned API described &lt;a href="https://docs.docker.com/reference/api/docker_remote_api/" target="_blank"&gt;here&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Running Docker Machine on Rackspace Public Cloud</title><link>https://networkstatic.net/running-docker-machine-on-rackspace-public-cloud/</link><pubDate>Fri, 01 May 2015 04:43:45 +0000</pubDate><guid>https://networkstatic.net/running-docker-machine-on-rackspace-public-cloud/</guid><description>&lt;h3&gt; Running Docker Machine on Rackspace Public Cloud&lt;/h3&gt;&#10;&lt;p&gt;Next up I am giving Docker Machine on Rackspace public cloud a whirl. If you don&amp;rsquo;t have an account and want to check it out take a look at their &lt;a href="https://developer.rackspace.com/signup/"&gt;developer+&lt;/a&gt; credit.&lt;/p&gt;&#10;&lt;p&gt;Here is a gif diagram (I&amp;rsquo;m addicted to making gifs atm, sometimes not even cats doing cute fluffy cat stuff like here) overviewing Docker Machine. To get installed and much more on docker and docker machine check out the excellent docs at &lt;a href="https://docs.docker.com/machine/" target="_blank"&gt;docs.docker.com&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Docker Machine Provisioning on AWS</title><link>https://networkstatic.net/docker-machine-provisioning-on-aws/</link><pubDate>Thu, 30 Apr 2015 07:46:02 +0000</pubDate><guid>https://networkstatic.net/docker-machine-provisioning-on-aws/</guid><description>&lt;h3&gt; Docker Machine Provisioning on AWS&lt;/h3&gt;&#10;Next up in the docker machine &lt;a href="http://normalizing-the-cloud-with-docker-machine" target="_blank"&gt;series&lt;/a&gt; of integration posts is spinning up some cloud resources on Amazon EC2. The model is the same as previous docker machine posts, boot a VM running as a Docker host, add your cloud credentials for the provider and use your regular docker client commands on the remote Docker host in Amazon.&#10;&lt;p&gt;The docker machine docs are excellent at &lt;a href="https://docs.docker.com/machine/" target="_blank"&gt;docs.docker.com&lt;/a&gt;. These posts are just my notes as I am getting to know the docker machine provisioning harness.&lt;/p&gt;</description></item><item><title>Normalizing the Cloud with Docker Machine</title><link>https://networkstatic.net/normalizing-the-cloud-with-docker-machine/</link><pubDate>Thu, 30 Apr 2015 07:43:32 +0000</pubDate><guid>https://networkstatic.net/normalizing-the-cloud-with-docker-machine/</guid><description>&lt;h3&gt; Normalizing the Cloud with Docker Machine &lt;/h3&gt;&#10;&lt;p&gt;Docker machine creates a virtual machine running Docker located in an array of locations that I can then create containers and ship workloads to. The locations and types you can provision to range from the who is who of cloud computing, workstation resources and traditional on prem local resources sitting in the average enterprise DC.&lt;/p&gt;</description></item><item><title>Using Docker Machine to Provision on Microsoft Azure</title><link>https://networkstatic.net/using-docker-machine-to-provision-on-microsoft-azure/</link><pubDate>Thu, 30 Apr 2015 07:40:25 +0000</pubDate><guid>https://networkstatic.net/using-docker-machine-to-provision-on-microsoft-azure/</guid><description>&lt;H3&gt; Using Docker Machine to Provision on Microsoft Azure &lt;/H3&gt;&#10;&lt;p&gt;Microsoft has done a pretty amazing job with Azure over the years. It has been really cool seeing Microsoft &lt;a href="http://azure.microsoft.com/blog/?s=docker" target="_blank"&gt;embrace&lt;/a&gt; Docker and open source in general like they recently have. This post is a continuation of the &lt;a href="http://normalizing-the-cloud-with-docker-machine" target="_blank"&gt;series&lt;/a&gt; on docker machine provisioning to dev hypervisors, DC infra and cloud providers. If you are new to Azure or don&amp;rsquo;t have an account, you can grab a free trial from &lt;a href="http://azure.microsoft.com/en-us/pricing/free-trial/" target="_blank"&gt;Azure&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Starting OVSDB and vSwitchd in OpenvSwitch with Debugging Enabled</title><link>https://networkstatic.net/starting-ovsdb-and-vswitchd-in-openvswitch-with-debugging-enabled/</link><pubDate>Tue, 07 Apr 2015 22:24:04 +0000</pubDate><guid>https://networkstatic.net/starting-ovsdb-and-vswitchd-in-openvswitch-with-debugging-enabled/</guid><description>&lt;/h2&gt;&lt;h2 class="legacy-heading"&gt;Starting OVSDB and vSwitchd in OpenvSwitch with Debugging Enabled &lt;/h2&gt;&lt;/h2&gt;&#10;&lt;p&gt;Here are some quick notes on how I went about debugging OVSDB (ovsdb-server) and OVS vSwitchd (ovs-vsctl). There are lots of ways to debug OVS these are what I used to get debug logs generated. Those logs are helpful troubleshooting for OVSDB transactions and OpenFlow commands when using the ovs-vctl or OVSDB and OpenFlow APIs.&lt;/p&gt;</description></item><item><title>Docker Command One Liners</title><link>https://networkstatic.net/docker-one-liners/</link><pubDate>Tue, 24 Feb 2015 04:35:54 +0000</pubDate><guid>https://networkstatic.net/docker-one-liners/</guid><description>&lt;H3&gt;Docker Command One Liners&lt;/H3&gt;&#10;&lt;p&gt;I love the code snippets, it&amp;rsquo;s how I learn any syntax by rolling up the sleeves, hacking and breaking while taking notes along the way. It&amp;rsquo;s probably not the most efficient but the muscle memory is how I learn. Here is a list of one liners from my notes in no particular order (even though I tried to in a couple of places :).&lt;/p&gt;</description></item><item><title>Installing Golang IDE Support in Intellij</title><link>https://networkstatic.net/installing-golang-ide-support-intellij/</link><pubDate>Sun, 08 Feb 2015 23:03:39 +0000</pubDate><guid>https://networkstatic.net/installing-golang-ide-support-intellij/</guid><description>&lt;h2&gt; Installing Golang IDE Support in Intellij &lt;/h2&gt;&#10;&lt;p&gt;I have always preferred Intellij Community Edition IDE for Java, Bash, Python, Node and anything else I have needed, including recently &lt;a href="https://www.jetbrains.com/clion/" target="_blank"&gt;C/C++&lt;/a&gt; which is pretty slick. The plus is I can hang on to key-mappings, syntax color and general workflow all in a ubiquitous dev environment. There are some good IDE &lt;a href="https://github.com/golang/go/wiki/IDEsAndTextEditorPlugins" target="_blank"&gt;options&lt;/a&gt; for Go and of course support for the staunch EMACS/VIM purist. I like the background support an IDE offers but to each their own. There is a nice community driven project for an Intellij &lt;a href="https://github.com/go-lang-plugin-org/go-lang-idea-plugin" target="_blank"&gt;Golang plugin&lt;/a&gt; hosted on github. It is a Java project that is very active. At any time you can go to Intellij Prefrences -&amp;gt; Plugins -&amp;gt; search for &amp;lsquo;golang&amp;rsquo;.&lt;/p&gt;</description></item><item><title>Golang for Network Ops</title><link>https://networkstatic.net/golang-network-ops/</link><pubDate>Fri, 16 Jan 2015 06:03:49 +0000</pubDate><guid>https://networkstatic.net/golang-network-ops/</guid><description>&lt;h2&gt;Golang for Network Ops&lt;/h2&gt;&#10;&lt;p&gt;I get asked quite often where the traditional network engineer / network ops should start if they want to broaden their horizons with better code hacking skills or they have spent the last 20 years using Perl scripts or more recently Python and need a change. The answer is easy, Golang. At &lt;a href="https://github.com/socketplane" target="_blank"&gt;Socketplane&lt;/a&gt;, we all ditched the past couple of years of Java or C and now all code almost exclusively in Go. Go allows us to rapidly develop network solutions around &lt;a href="https://www.docker.com/tryit/" target="_blank"&gt;Docker&lt;/a&gt; which is written in Go, not to mention incredibly fun to develop in. We have a technology preview up and some really cool new things in development. Now there are many that could care less about the language they use and argue that is merely an implementation detail, the difference to me is if it takes you 3x the time in another language, or there is a performance penalty it is very relevant. That coupled with natively integrated tools, (go fmt, go run -race, go get, go test; etc) puts the productivity through the roof.&lt;/p&gt;</description></item><item><title>The Network Iceberg</title><link>https://networkstatic.net/network-iceberg/</link><pubDate>Fri, 31 Oct 2014 18:19:47 +0000</pubDate><guid>https://networkstatic.net/network-iceberg/</guid><description>&lt;h2&gt;The Network Iceberg&lt;/h2&gt;&#10;The impact of compute virtualization on the data center network has been profound. There are more virtual ports then physical ports. That simple measurement overshadows any other disruption in networking. We arrived at this transformation as a result of significant adoption of OS virtualization.&#10;&lt;p&gt;The next revision of compute virtualization is the application. The last significant bastion of efficiency is to remove the OS from the equation and virtualize that application itself. At the helm of the compute disruption is &lt;a href="https://www.docker.com/tryit/" target="_blank"&gt;Docker&lt;/a&gt;. Depending on a providers oversubscription, a typical ratio of VM/CPU is in the range of 20-50 VMs per physical core. The consolidation and eventual removal of the guest OS will significantly affect the subscription ratio. The condensation of the application to CPU ratio and the demand that will be imposed on the network is pretty damn exciting. There is of course some debate around security, shared kernel etc, but we had the same conversations in the infancy of OS virtualization. Atomic and CoreOS are both cool projects if you haven&amp;rsquo;t seen them before, take a look. The lightweight, purpose build OS are pretty awesome.&lt;/p&gt;</description></item><item><title>Brent's Technology Bookmarks from June</title><link>https://networkstatic.net/brents-technology-bookmarks-from-june/</link><pubDate>Sat, 21 Jun 2014 04:55:41 +0000</pubDate><guid>https://networkstatic.net/brents-technology-bookmarks-from-june/</guid><description>&lt;h1&gt;Brent's Technology Bookmarks from June&lt;/h1&gt;&#10;Lots going on in the past couple of months. While current projects have me pretty busy I wanted to share some good reads and interesting developments in the industry. In no particular order:&#10;&lt;hr /&gt;&#10;&lt;ul&gt;&#10;&#9;&lt;li&gt;&lt;a href="http://www.coverfire.com/articles/queueing-in-the-linux-network-stack/" target="_blank"&gt;Queueing in the Linux Network Stack&lt;/a&gt; - This is a fantastic breakdown of buffer management in the Linux networking stack.&lt;/li&gt;&#10;&#9;&lt;li&gt;&lt;a href="http://www.sdncentral.com/news/google-open-source-help-policy-based-sdn/2014/06/%20f" target="_blank"&gt;Google Wants Open-Source Help for Policy-Based SDN&lt;/a&gt; from the guys over at SDN Central. I'm glad to see Google recognizes it needs to participate in a broader open source networking community to drive their architectural agendas. Hope to see them jump into OpenDaylight with us and get some oxygen on their models. How tightly coupled models and platforms are is still something that needs debate in my opinion. The article also makes me want to revisit &lt;span style="color: #000000;"&gt;protobufs to see if any of the RPC code has been open sourced. &lt;/span&gt;&lt;/li&gt;&#10;&#9;&lt;li&gt;Facebook has been a huge supporter of the &lt;a href="http://www.opencompute.org" target="_blank"&gt;Open Compute Project&lt;/a&gt; and this week announced further adoption of the whitebox evolution. Since networking is roughly in the mid-1980s when it comes to embracing the inevitability of a commoditized network hardware world. That said, incumbent vendors are quite adept at &lt;a href="http://www.networkworld.com/article/2169117/lan-wan/facebook-open-compute-project-has--weaknesses---cisco-ceo-says.html" target="_blank"&gt;slowing&lt;/a&gt; down and managing disruption to avoid going the way of Sun. I have been pretty steadfast on believing that those who run whitebox/ODM manufactured compute today will be the aggressive adopters on the networking front. This will drive down the disproportionate (compared to compute) margins of networking kit. OEMs can surely add enough value to makeup for the single digit/teen margins to stay status quo.&lt;/li&gt;&#10;&#9;&lt;li&gt;A fun read to remind us to keep our pessimism in check or ending up having some amusing quotes someday. &lt;a href="http://thenextweb.com/shareables/2010/02/27/newsweek-1995-buy-books-newspapers-straight-intenet-uh/#!qmSFr" target="_blank"&gt;Newsweek in 1995: Why the Internet will Fail.&lt;/a&gt;&lt;/li&gt;&#10;&#9;&lt;li&gt;Next are a dozen things this fella learned from the VC king Marc Andreessen (lesser known, cut his teeth as the author of the Mosaic browser from his time at NCSA). &lt;a href="http://25iq.com/2014/06/14/a-dozen-things-ive-learned-from-marc-andreessen/" target="_blank"&gt;A Dozen Things I’ve Learned From Marc Andreessen&lt;/a&gt;&lt;/li&gt;&#10;&#9;&lt;li&gt;A classic and tragic story on why your backups should probably not reside in the same cloud platform as your production systems. &lt;a href="http://www.theregister.co.uk/2014/06/18/code_spaces_destroyed/" target="_blank"&gt;Code Spaces goes titsup forever after attacker nukes its Amazon-hosted data&lt;/a&gt;&lt;/li&gt;&#10;&#9;&lt;li&gt; Google also made the headlines with their growing support of the hottest topic since Chuck Norris's beard Docker. For Google, their GCE cloud strategy appears the same, don't compete with Amazon on their field (IaaS) but change the rules of the game and compete at the application layer. There is so much margin left and Google will continue to drive the &lt;a href="https://networkstatic.net/does-the-cost-of-cloud-iaas-intersect-the-local-vm/" target="_blank"&gt;race to zero&lt;/a&gt;. Read more from their blog about the update: An update on container support on &lt;a href="http://googlecloudplatform.blogspot.com/2014/06/an-update-on-container-support-on-google-cloud-platform.html" target="_blank"&gt;Google Cloud Platform&lt;/a&gt;.&lt;/li&gt;&#10;&#9;&lt;li&gt;I may have another hero to add to my collection. Former FCC Commissioner Michael Copps speaking at the Library of Congress spoke the truth about the tragic state of broadband in the US. &lt;a href="http://consumerist.com/2014/06/18/former-fcc-commissioner-we-should-be-ashamed-of-ourselves-for-state-of-broadband-in-the-u-s/" target="_blank"&gt;Former FCC Commissioner: “We Should Be Ashamed Of Ourselves” For State of Broadband In The U.S.&lt;/a&gt;&lt;/li&gt;&#10;&#9;&lt;li&gt;The only worthwhile thing I have seen the FCC do since &lt;a href="http://www.lightreading.com/regulation/meet-tom-wheeler-net-neutrality-procrastinator-in-chief/a/d-id/709264" target="_blank"&gt;Wheeler&lt;/a&gt; (a former Cable lobbyist) took over as chairman was covered in this article &lt;a href="http://www.thewire.com/technology/2014/06/fcc-redefines-internet-speed/371961/" target="_blank"&gt;FCC May Redefine What It Means to Have 'Broadband' Internet&lt;/a&gt;. Bringing the broadband benchmarks out of the 90's is important in many different ways that are too long to list so take a peek and tell these dummies why a strong National (and Global for that matter) broadband infrastructure isn't just important for watching NetFlix movies to future generations. They are fracturing and it may well be worth throwing some support towards the &lt;a href="http://www.lightreading.com/regulation/fcc-split-on-net-neutrality-plans-/d/d-id/709100" target="_blank"&gt;dissenters&lt;/a&gt; with enough backbone to push back on the lobbyist culture in US politics.&lt;/li&gt;&#10;&#9;&lt;li&gt;One more from Google that presents empirical data on the impact of build time breakage in software development &lt;a href="http://static.googleusercontent.com/media/research.google.com/de//pubs/archive/42184.pdf"&gt;Programmers’ Build Errors: A Case Study (at Google)&lt;/a&gt;. Something we all love :)&lt;/li&gt;&#10;&#9;&lt;li&gt;A post from one of my favorite blogs Network Heresy where Martin Casado frequently has folks from his staff guest blog. Here &lt;a href="http://blog.scottlowe.org" target="_blank"&gt;Scott Lowe&lt;/a&gt; and Tim Hinrichs discuss the hot topic of policy in &lt;a href="http://networkheresy.com/2014/06/19/on-policy-in-the-data-center-the-solution-space/" target="_blank"&gt;On Policy in the Data Center: The solution space&lt;/a&gt;. Another pal, &lt;a href="https://twitter.com/dvorkinista" target="_blank"&gt;Mike Dvorkin&lt;/a&gt; is also working on the policy problem from many years of obsessing and numerous implementations, namely UCS Manager. I don't have any links but will dig some up in a future post to share both sides. I avoid looking at company names, ideas are either bullshit mouse traps or not. Both of these select camps understand the importance open source plays in adoption. No migration path, no adoption.&lt;/li&gt;&#10;&#9;&lt;li&gt;There was also a nice writeup on Martin's &lt;a href="http://www.informationweek.com/cloud/infrastructure-as-a-service/why-goldilocks-zone-of-data-center-security-makes-sense/a/d-id/1269304" target="_blank"&gt;Goldilocks Zone&lt;/a&gt; security concepts. Someday I will be out of the low levels in ODL when we stabilize with feature parity and really start grinding security and policy implementations, rather then the rudimentary OS services I'm working on currently. Take a look at it. I fundamentally believe that SDN solving the disaster of security application today is a core business and technological deliverable. If I'm not mistaken, his original SDN/OF work was to better segment/secure research networks and some .gov work, he understands the space as well as anyone out there.&lt;/li&gt;&#10;&#9;&lt;li&gt;Netflix is probably the biggest broadband consumer advocate in existence (arguably 100x more productive then the FCC). Here is a nice&lt;a href="http://ispspeedindex.netflix.com/usa" target="_blank"&gt; speed index&lt;/a&gt; they recently started publishing to the &lt;a href="http://www.fierceonlinevideo.com/story/verizon-fios-speed-drops-netflix-isp-index-despite-peering-deal/2014-06-09" target="_blank"&gt;chagrin of a few carriers&lt;/a&gt;.&lt;/li&gt;&#10;&#9;&lt;li&gt;Lastly, my favorite is an &lt;a href="https://secure.mysociety.org/admin/lists/pipermail/developers-public/2011-October/007647.html" target="_blank"&gt;informational packet&lt;/a&gt; from the legend of the free software world, Richard Stallman. It outlines his speaker visits and what he requires if he is visiting as a guest speaker. Stallman on cats in the house where he will be staying, and this quote makes him even more awesome &lt;em&gt;"I like cats if they are friendly, but they are not good for me; I am somewhat allergic to them. This allergy makes my face itch and my eyes water. So the bed, and the room I will usually be staying in, need to be clean of cat hair. However, it is no problem if there is a cat elsewhere in the house--I might even enjoy it if the cat is friendly."&lt;/em&gt;&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;hr /&gt;&#10;&lt;p&gt;Thats all for now. Have a great weekend.&lt;/p&gt;</description></item><item><title>Updated DevStack OpenDaylight VM Image for OpenStack IceHouse</title><link>https://networkstatic.net/updated-devstack-opendaylight-vm-image-for-openstack-icehouse/</link><pubDate>Mon, 05 May 2014 19:46:05 +0000</pubDate><guid>https://networkstatic.net/updated-devstack-opendaylight-vm-image-for-openstack-icehouse/</guid><description>&lt;h2&gt;Updated DevStack OpenDaylight VM Image for OpenStack&lt;/h2&gt;&#10;&lt;p&gt;Here is an updated Fedora 20 image for building OpenStack Icehouse and OpenDaylight. ODL is now merged into the upcoming OpenStack Icehouse release so now you can install ODL directly from OpenStack trunk. The updated image comes from Kyle Mestery who was primarily responsible for getting the OpenStack/OpenDaylight merge and navigating the process. Thanks also to Andrew Grimberg from the Linux Foundation with assisting with getting testing setup and all the code contributors from the community.&lt;/p&gt;</description></item><item><title>Setting Up Overlays on Open vSwitch</title><link>https://networkstatic.net/setting-overlays-open-vswitch/</link><pubDate>Thu, 06 Mar 2014 07:58:22 +0000</pubDate><guid>https://networkstatic.net/setting-overlays-open-vswitch/</guid><description>&lt;h2&gt; Setting Up Overlays on Open vSwitch &lt;/h2&gt;&#10;&lt;p&gt;Most &amp;ldquo;SDN&amp;rdquo; solutions involve overlays or at the least HW overlay gateways/ToR of some type. Some sell overlays terminating in hardware, others sell overlays terminating in the server. The encaps include standards like GRE, VXLAN and soon to be &lt;a href="http://tools.ietf.org/html/draft-gross-geneve-00" target="_blank"&gt;Geneve &lt;/a&gt;(Generic Network Virtualization Encapsulation: basically the good parts of the other encaps evolved). While none of these overlay networks should ever be setup by hand like we provision networks currently today, if you are trying to get a good understanding of OVS and overlays for proofing something before you code it this may be helpful. Before we do any coding to automate provisioning, it helps to work out any potential blocking ahead of time. OVS is the reference SDN datapath from developers who I regard as the best in the business. If you invest time into evolving your network, OVS is the place to start.&lt;/p&gt;</description></item><item><title>OpenDaylight OpenStack Integration with DevStack on Fedora</title><link>https://networkstatic.net/opendaylight-openstack-integration-devstack-fedora-20/</link><pubDate>Fri, 07 Feb 2014 06:32:25 +0000</pubDate><guid>https://networkstatic.net/opendaylight-openstack-integration-devstack-fedora-20/</guid><description>&lt;h2 class="legacy-heading"&gt; OpenDaylight OpenStack Integration with DevStack on Fedora &lt;/h2&gt;&#10;&lt;p&gt;The following is a walk through of the OVSDB project within OpenDaylight for OpenStack integration. There are a couple of bugs so it is not for the faint of heart. It is intended for those looking to get their development environment up and running. We will have videos and what not walking through the installation and code reviews of the implementation. It was developed by folks from various vendors and users in the community. Some are in companies that aren&amp;rsquo;t dedicating resources to the project but are doing it in their personal time. Both &lt;a href="https://twitter.com/MadhuVenugopal" target="_blank"&gt;Madhu&lt;/a&gt; and I are maintaining this post to keep it as accurate as possible and up to date with our own individual notes as we move into the next phase of development for Helium. Madhu is going to do a separate Fedora 19 post on a new blog he is setting up which I am pumped about! Until then, keep an eye out for Fedora19 and Fedora20 specific instructions below.&lt;/p&gt;</description></item><item><title>Install Open vSwitch Networking on Red Hat Fedora 20</title><link>https://networkstatic.net/install-open-vswitch-networking-red-hat-fedora-20/</link><pubDate>Thu, 23 Jan 2014 02:28:08 +0000</pubDate><guid>https://networkstatic.net/install-open-vswitch-networking-red-hat-fedora-20/</guid><description>&lt;h2&gt; Install Open vSwitch Networking on Red Hat Fedora 20 &lt;/h2&gt;&#10;&lt;p&gt;The following tutorial will bootstrap you in installing and configuring Open vSwitch on Red Hat Fedora 20. It also has some extras that are just general Fedora configuration tasks such as setting up networking along with Wireshark over an X11 ssh session. This is the first of lots of integration posts over the next year as we develop network virtualization in Open Daylight and continue to integrate further into OpenStack. The &amp;ldquo;we&amp;rdquo; is a royal &amp;ldquo;we&amp;rdquo;. It is the awesome team I am on at Red Hat, but much broader, the OpenDaylight and OpenStack communities and the thousands of contributors around the world that truly mak the difference. The OVSDB ODL team is hyper-focused on simplifying and automating the deployment and integration of cloud infrastructures. Complexity is in my opinion, typically a hurdle for consumers of open source projects and cloud/scale in general.&lt;/p&gt;</description></item><item><title>New Opportunity at Red Hat</title><link>https://networkstatic.net/new-opportunity-red-hat/</link><pubDate>Thu, 09 Jan 2014 19:49:19 +0000</pubDate><guid>https://networkstatic.net/new-opportunity-red-hat/</guid><description>&lt;p&gt;Exciting times are upon us. I have humbly accepted a job at Red Hat on the Open Daylight dev team working with some incredible people at Red Hat and just as special folks in the community. I just wanted to pop up a brief post letting my friends in the community know where I am heading. I will miss my friends and co-workers in EDU like Dave Hucaby, JimO and Doyle Friskney to name a couple, that have believed in me even when sometimes I did not.&lt;/p&gt;</description></item><item><title>Install Open vSwitch v2.0 from RPM on RedHat Fedora</title><link>https://networkstatic.net/install-open-vswitch-v2-0-rpm-redhat-fedora/</link><pubDate>Thu, 05 Dec 2013 04:00:02 +0000</pubDate><guid>https://networkstatic.net/install-open-vswitch-v2-0-rpm-redhat-fedora/</guid><description>&lt;h2&gt;Install Open vSwitch v2.0 from RPM on RedHat Fedora&lt;/h2&gt;&#10;This post is for installing OVS from RedHat RPM binaries. If you want to build Open vSwitch from source please see &lt;a href="https://networkstatic.net/install-open-vswitch-v2-redhat-fedora-19/" target="_blank"&gt;this post&lt;/a&gt;. Open vSwitch v2.0 introduces some really important features, at the top of the list is multi-threaded support in vswitchd. This will increase flow instantiation rates significantly into the upstream kernel module. A rough guess would be from less then 10k per/sec to 10x that w/ multithreaded support. I would imagine there will be a single threaded implementation for a single trace, serial hardware switch needs. This release also includes experimental support for OpenFlow v1.1, v1.2 and v1.3 along with some new OVSDB tables that have some cool potential such as &lt;a href="http://networkheresy.com/2013/11/01/of-mice-and-elephants/" target="_blank"&gt;IPFIX&lt;/a&gt;.&#10;&lt;p&gt;Lastly, is the important support for &amp;ldquo;remote_ip=flow&amp;rdquo; and &amp;ldquo;local_ip=flow&amp;rdquo; options that are enabling us to push multiple keys/VNIs over a single overlay tunnel in the &lt;a href="https://wiki.opendaylight.org/view/Project_Proposals:OVSDB-Integration" target="_blank"&gt;OVSDB OpenDaylight&lt;/a&gt; project. This was supported in previous versions but different matching options have been added. An example of a VXLAN tunnel carrying multiple tenants or network IDs or whatever your segmentation strategy is:&lt;/p&gt;</description></item><item><title>Installing OpenStack ML2 Neutron Plugin with DevStack on Fedora</title><link>https://networkstatic.net/installing-openstack-ml2-neutron-plugin-devstack-fedora/</link><pubDate>Tue, 26 Nov 2013 09:27:02 +0000</pubDate><guid>https://networkstatic.net/installing-openstack-ml2-neutron-plugin-devstack-fedora/</guid><description>&lt;h2&gt;Installing OpenStack ML2 Neutron Plugin with DevStack on Fedora &lt;/h2&gt;&#10;OpenStack networking is tricky. This is primarily because programmable distributed systems are relatively new beyond the rigid L2/L3 control protocols we have used for the past 20 years. What I am consistently impressed with about OpenStack networking is the innovative network services that systems programmers are developing using APIs and virtual switching. Of course most vendors have a plugin for their hardware but service instantiation in the hypervisor endpoint is relatively easy since these are open systems with compute scale.&#10;&lt;p&gt;My comrades and I that are working on the OVSDB implementation in the OpenDaylight project have needed to get up to speed on the OpenStack Neutron ML2 (Modular Layer 2) plugin to begin integration. OVSDB in OpenDaylight enables us to implement an agent-less/driver-less OpenStack/OpenDaylight integration using OVSDB for topology provisioning and OpenFlow for forwarding control and service insertion. We are fortunate to have our friend and OVSDB committer &lt;a href="http://www.siliconloons.com" target="_blank"&gt;Kyle Mestery&lt;/a&gt; who is also on the core Neutron team to assist on the ML2 integration front.&lt;/p&gt;</description></item><item><title>Install Open vSwitch v2 from Source on Red Hat Fedora 19</title><link>https://networkstatic.net/install-open-vswitch-v2-redhat-fedora-19/</link><pubDate>Sun, 10 Nov 2013 06:07:00 +0000</pubDate><guid>https://networkstatic.net/install-open-vswitch-v2-redhat-fedora-19/</guid><description>&lt;h2&gt;Install Open vSwitch v2 on Red Hat Fedora 19&lt;/h2&gt;&#10;&lt;p&gt;This is a walk through for installing Open vSwitch v2.0+ on RedHat Fedora 19 from source. If you want to build Open vSwitch from RPM binaries please see &lt;a href="https://networkstatic.net/install-open-vswitch-v2-0-rpm-redhat-fedora/" target="_blank"&gt;this post&lt;/a&gt; There are some new OVS tables included in the latest builds that include some &lt;a href="http://networkheresy.com/2013/11/01/of-mice-and-elephants/" target="_blank"&gt;neat concepts&lt;/a&gt;. OVS is often regarded as the SDN reference data plane implementation in the early SDN space. That is good for the industry and innovation as it reduces R&amp;amp;D risk and thus cost, which leads to less fragmentation and faster adoption of innovative ideas and architectures. Not to mention resides in easily over half of the vendors SDN DP kit in some form, fashion or library. I tend to make a case OVSDB is looking like the reference SDN management protocol based on real world adoption, not slide deckery. For more information on the Open vSwitch database schema, please see the &lt;a href="http://openvswitch.org/ovs-vswitchd.conf.db.5.pdf" target="_blank"&gt;ovsdb.conf spec&lt;/a&gt;. Fedora is a perennial favorite Linux platform for many and one of the many sponsored community projects by &lt;a href="https://twitter.com/RedHatNews" target="_blank"&gt;RedHat&lt;/a&gt;. Fedora is often perceived as more bleeding edge with regard to software software packaging then its counterparts, CentOS and the most conservative of the three, RHEL.&lt;/p&gt;</description></item><item><title>Installing Mininet, OpenDaylight and Open vSwitch</title><link>https://networkstatic.net/installing-mininet-opendaylight-open-vswitch/</link><pubDate>Mon, 21 Oct 2013 18:36:07 +0000</pubDate><guid>https://networkstatic.net/installing-mininet-opendaylight-open-vswitch/</guid><description>&lt;h2&gt;Installing Mininet, OpenDaylight and Open vSwitch&lt;/h2&gt;&#10;The easiest way to get started with a quick SDN lab image is using the Mininet image that is now managed by the &lt;a href="http://onlab.us" target="_blank"&gt;ONLAB&lt;/a&gt; which is part of the &lt;a href="http://onrc.stanford.edu" target="_blank"&gt;ONRC&lt;/a&gt;. They do a nice job keeping the images maintained. Ideally the will incorporate ODL into the image soon since the ODL GUI is great for folks to get started with SDN.&#10;&lt;h2&gt;Download and Bring up Mininet&lt;/h2&gt;&#10;You can use your prefered hypervisor of choice to run the image. The Mininet guide has instructions for each. &lt;em&gt;Download Mininet and get the image up and running with the following guide:&lt;/em&gt;&#10;&lt;p&gt;&lt;a href="http://mininet.org/download/" target="_blank" rel="noopener noreferrer"&gt;Download and Get Started With Mininet&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Eliminating VLANs and Fragility in the Underlay with Network Virtualization</title><link>https://networkstatic.net/eliminating-vlans-and-fragility-in-the-underlay-with-network-virtualization/</link><pubDate>Wed, 16 Oct 2013 19:41:30 +0000</pubDate><guid>https://networkstatic.net/eliminating-vlans-and-fragility-in-the-underlay-with-network-virtualization/</guid><description>&lt;h2 class="legacy-heading"&gt;Eliminating VLANs and Fragility in the Underlay with Network Virtualization&lt;/h2&gt;&#10;This post is not intended to participate in the vendor Overlay vs. Underlay vs. Open OS vs. closed NOS but rather a network centric look at some things I am considering. The simple answer is routing scales and bridging doesn't in my experience. As I look back at the first decade in my career I spent operating and designing Ethernet networks, the one thing that no amount of effort could solve was the inherent fragility of the broadcast domain. When I started in networking, it was the early days of the VLAN. VLANs were the magical answer to the instabilities of a single bridge in a large network and it worked fine in the linear topologies of the day. As VoIP and other data center applications critical to the business began to require redundancy. It was at that point when we should have been coming up with more effective means of dealing with L2 learning then flooding broadcast domains.&#10;&lt;figure class="legacy-figure"&gt;&lt;img src="https://networkstatic.net/wp-content/uploads/2013/10/VLAN-Fail1.jpeg" alt="VLAN Fail"&gt;&lt;/figure&gt;&#10;&lt;p&gt;Instead, we came up with mechanisms of tricking the logical network into thinking the physical network was loop free and adjusting L2 topology timers to the edge of math to reduce convergence as much as possible. The next iteration of patching was segmenting the L2 network into smaller chunks. This was where the wheels came off. If (big if) an organization could re-address their infrastructure they were handicapping the ability to use tools in the server virtualization realm such as vMotion. And yes, while L3 failover is always the more scalable solution, most systems administrators tune you out when you are explaining why they need to gut their infrastructure to implement it.&lt;/p&gt;</description></item><item><title>Getting Started With OVSDB</title><link>https://networkstatic.net/getting-started-ovsdb/</link><pubDate>Tue, 01 Oct 2013 01:57:09 +0000</pubDate><guid>https://networkstatic.net/getting-started-ovsdb/</guid><description>&lt;h2&gt;Getting Started With OVSDB&lt;/h2&gt;&#10;&lt;p&gt;OVSDB (Open vSwtich Database) is a management protocol used to manipulate the configuration of &lt;a href="http://openvswitch.org" target="_blank"&gt;Open vSwitches&lt;/a&gt; and more recently vendors have begun implementing OVSDB in their Ethernet switches firmware. Some of those vendor data plane implementations are already running OVS under the hood so the implementation should be relatively painless. A project I am involved in developing is the OVSDB implementation in the OpenDaylight SDN platform. I will disclaim this post is relatively self-serving to act as a reference for anyone interested in being part of the Daylight implementation and a little bit about how we are going about coding it. But it is also for anyone interested in getting started with OVSDB. I see OVSDB as a keystone protocol for enabling programmatic networks in the future. Adoption is high underway from &lt;em&gt;almost&lt;/em&gt; all networking software and hardware vendors.&lt;/p&gt;</description></item><item><title>SDN Product Rundown from September</title><link>https://networkstatic.net/sdn-product-rundown-september/</link><pubDate>Sun, 22 Sep 2013 19:57:20 +0000</pubDate><guid>https://networkstatic.net/sdn-product-rundown-september/</guid><description>&lt;h2&gt;SDN Product Rundown from September &lt;/h2&gt;&#10;What an exciting time to be in networking. This past month of September has been a blur of SDN product announcements and emerging strategies. At the top of the heap was the &lt;a href="http://www.networkcomputing.com/next-generation-data-center/commentary/networking/inside-vmware-nsx/240161109" target="_blank"&gt;NSX&lt;/a&gt; announcement from a software company in Vmware that encapsulated Nicira's SDN push. I am an unabashed Casado fan boy so whatevers. Humility and genius is lightning striking twice. The blinders are off and now there is a steady pipeline of fantastic ideas (both new and old) that are starting to gain traction from software and hardware startups and even incumbent hardware vendors. I had the honor of spending the week with friends from Network Field Day and SDNCentral to debate product, architectures and the futures of networking.&#10;&lt;h2&gt;Harnessing Data with Plexxi&lt;/h2&gt;&#10;&lt;p&gt;First up is &lt;a href="https://networkstatic.net/plexxi-capacity-planning-done-right/" target="_blank"&gt;Plexxi networks&lt;/a&gt;. The exciting aspect of Plexxi has always been data driven analytics. There is an unbelievable amount of data from networking, storage and compute that goes to waste in our data centers. Ultimately we can have all of the mechanisms to provision and control the network, but if we cannot extract, relate and present the data in a functional manner it is still an operation hand crank. Mutating the network based on predictive or realtime data analysis will not get the glares and eye rolls in the room that it used to.&lt;/p&gt;</description></item><item><title>The OpenFlow Overlay</title><link>https://networkstatic.net/the-openflow-overlay/</link><pubDate>Sun, 30 Jun 2013 06:06:02 +0000</pubDate><guid>https://networkstatic.net/the-openflow-overlay/</guid><description>&lt;h2&gt;The OpenFlow Overlay&lt;/h2&gt;&#10;Integrating SDN beyond the data center is still the wild west. The needs are very similar, traffic classification and policy instantiation at the edge. Data center solutions then abstract the underlying network with tunneling/encapsulation mechanisms to achieve IP mobility among other things. Outside the data center, some may care about choosing a forwarding path beyond the SPF calculation accounting for other constraints and some may not. What everyone does care about is the edge. SDN in DC is being defined today, flow based forwarding on the edge (wildcarding available), exact match forwarding in the core (CAM/LPM). Whether enterprise security services or provider service insertion to generate new revenue it is all about the edge. How do we begin to integrate SDN without replacing our networks and without vendor applications to do it? Using a similar approach to data center solutions that Martin Casado and team pioneered using DC tunnels, we can use VID, VPLS and in one case I'm pinning specific flows for tapping over GREs (just as a &lt;a href="http://etherealmind.com/integrating-overlay-networking-and-the-physical-network/" target="_blank"&gt;DC overlay&lt;/a&gt; would but in edge HW) to avoid having to deal with the native core.&#10;&lt;hr /&gt;&#10;&lt;p&gt;Since IP mobility is less of a concern rather then pathing I can replace L2 tunnels with application specific OpenFlow overlay flows. That doesn&amp;rsquo;t mean it needs to be OpenFlow. &lt;a href="http://blog.ioshints.info/2013/06/scott-shenker-on-openflow-and-sdn.html" target="_blank"&gt;Scott Shenker&lt;/a&gt; (a co-founder at Nicira along with Casado and McKeown) recently made a powerful point that &lt;em&gt;(paraphrasing) &amp;ldquo;the OpenFlow edge can solve any problem that someone would be willing to pay for&amp;rdquo;&lt;/em&gt;.&lt;/p&gt;</description></item><item><title>OpenDaylight Maven and OSGI Dev Notes</title><link>https://networkstatic.net/opendaylight-maven-and-osgi-dev-notes/</link><pubDate>Tue, 04 Jun 2013 05:09:35 +0000</pubDate><guid>https://networkstatic.net/opendaylight-maven-and-osgi-dev-notes/</guid><description>&lt;h2&gt;OPENDAYLIGHT MAVEN AND OSGI DEV NOTES&lt;/h2&gt;&#10;Prior to OpenDaylight I had only used the ODGI framework with David Ericson's Beacon contorller. I wanted to dump some of my notes from code hacking over the past couple of weeks. Most of the time has been spent getting used to OSGI and Maven. After the Maven and OSGI overviews, I list my dev notes for setting OSGI log levels, building an individual specific OpenDaylight bundle with Maven and making a creating a new module to hack on.&#10;&lt;h2&gt;WHAT IS OSGI?&lt;/h2&gt;&#10;OSGI is adds a modular framework that allows for dynamic loading of Java modules. This means you can load and unload , start and stop applications without taking down the running JVM platform. This seems to fits the theme of OpenDaylight to allow applications and protocols to plug into the framework to fit different use cases and vendor strategies. The platform is merely a series of Java interfaces. The projects that plug into the framework are referred to as bundles. The bundles need a few things to get started.&#10;&lt;h2&gt;WHAT IS MAVEN?&lt;/h2&gt;&#10;Here are some high points of the value Maven brings. Maven is awesome becuase it pulls dependencies automagically and lets you change version by merely changing the release number.&#10;&lt;ul&gt;&#10;&#9;&lt;li&gt;Making the build process easy&lt;/li&gt;&#10;&#9;&lt;li&gt;Providing a uniform build system&lt;/li&gt;&#10;&#9;&lt;li&gt;Providing quality project information&lt;/li&gt;&#10;&#9;&lt;li&gt;Providing guidelines for best practices development&lt;/li&gt;&#10;&#9;&lt;li&gt;Allowing transparent migration to new features&lt;/li&gt;&#10;&#9;&lt;li&gt;Change log document created directly from source control&lt;/li&gt;&#10;&#9;&lt;li&gt;Cross referenced sources&lt;/li&gt;&#10;&#9;&lt;li&gt;Mailing lists&lt;/li&gt;&#10;&#9;&lt;li&gt;Dependency list&lt;/li&gt;&#10;&#9;&lt;li&gt;Unit test reports including coverage&lt;/li&gt;&#10;&#9;&lt;li&gt;Keeping your test source code in a separate, but parallel source tree&lt;/li&gt;&#10;&#9;&lt;li&gt;Using test case naming conventions to locate and execute tests&lt;/li&gt;&#10;&#9;&lt;li&gt;Have test cases setup their environment and don’t rely on customizing the build for test preparation.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;hr /&gt;&#10;&lt;h2&gt;ENABLING LOGGING LEVELS AND TRACES IN THE OSGI CONSOLE&lt;/h2&gt;&#10;Lets say you want to see all log messages from the bundle. Change the logging level to arphandler to trace from the OSGI console.&#10;&lt;pre class="code-sample"&gt;&lt;code&gt;&#10;osgi setLogLevel org.opendaylight.controller.arphandler trace&#10;&lt;/code&gt;&lt;/pre&gt;&#10;Next verify your logging level.&#10;&lt;pre class="code-sample"&gt;&lt;code&gt;&#10;osgi getloglevel | grep arp&#10;Logger org.opendaylight.controller.arphandler at level INFO&#10;Logger org.opendaylight.controller.arphandler.internal at unknown level&#10;Logger org.opendaylight.controller.arphandler.internal.Activator at unknown level&#10;Logger org.opendaylight.controller.arphandler.internal.ArpHandler at unknown level&#10;Logger org.opendaylight.controller.arphandler_0 at unknown level&#10;Logger org.opendaylight.controller.arphandler_0.4 at unknown level&#10;Logger org.opendaylight.controller.arphandler_0.4.0 at unknown level&#10;Logger org.opendaylight.controller.arphandler_0.4.0.SNAPSHOT at level TRACE&#10;&lt;/code&gt;&lt;/pre&gt;&#10;&lt;p&gt;Logs will appear in the OSGI console and also in your opendaylight.log file.&lt;/p&gt;</description></item><item><title>Compiling Wireshark to Install the OpenFlow Dissector on a MAC</title><link>https://networkstatic.net/compiling-wireshark-to-install-the-openflow-dissector-on-a-mac/</link><pubDate>Mon, 20 May 2013 02:25:36 +0000</pubDate><guid>https://networkstatic.net/compiling-wireshark-to-install-the-openflow-dissector-on-a-mac/</guid><description>&lt;h2&gt;Compiling Wireshark to Install the OpenFlow Dissector on a MAC&lt;/h2&gt;&#10;&lt;figure class="legacy-figure"&gt;&lt;img src="https://networkstatic.net/wp-content/uploads/2013/10/Wireshark-OpenFlow.jpeg" alt="OpenFlow from Package PPA"&gt;&lt;/figure&gt;&#10;&lt;aside class="legacy-callout"&gt;&#10;&lt;ul&gt;&#10;&#9;&lt;li&gt;&lt;strong&gt;Update:&lt;/strong&gt; the OpenFlow dissector appears natively included in the nightly Ubuntu dev builds and even better, native in &lt;a href="http://fedoraproject.org/get-fedora" target="_blank"&gt;Fedora 19&lt;/a&gt;:&lt;/li&gt;&#10;&lt;li&gt;### Fedora 19 Wireshark Installation ###&#10;1) sudo yum install wireshark&#10;2) Nothing! Its that easy w/ native OpenFlow support +1&#10;For an X session on Fedora over SSH perform the following.&#10;1) Install the following:&#10;sudo yum install xorg-x11-xauth&#10;sudo yum install xorg-x11-fonts-*&#10;sudo yum install xorg-x11-utils&#10;======================&#10;2) Enable the following in the sshd_config file:&#10;=============================&#10;Change X11Forwarding to yes and uncomment:&#10;X11Forwarding yes&#10;====== sshd_config ==========&#10;#AllowAgentForwarding yes&#10;#AllowTcpForwarding yes&#10;#GatewayPorts no&#10;#X11Forwarding no&#10;X11Forwarding yes &lt;=== change this&#10;#X11DisplayOffset 10&#10;#X11UseLocalhost yes&#10;#PrintMotd yes&#10;===============&#10;$ export (should contain)&#10;declare -x DISPLAY="localhost:10.0"&#10;=========================&#10;Now you can "ssh -X 192.168.1.100" to your host and run an X Wireshark session using "sudo wireshark".&lt;/li&gt;&#10;&lt;/ul&gt;&#10;### Mac Installation ###&#10;Wireshark 1.11.0-SVN-52202&#10;&lt;a href="http://www.wireshark.org/download/automated/" target="_blank"&gt;http://www.wireshark.org/download/automated/&lt;/a&gt;&#10;&lt;ul&gt;&#10;&#9;&lt;li&gt;For a Mac just install quartz and this build and run as su.&lt;/li&gt;&#10;&#9;&lt;li&gt;sudo /Applications/Wireshark.app/Contents/MacOS/Wireshark&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;em&gt;### Installing on Ubuntu using the PPA repo try the following ###&lt;/em&gt;&#10;&lt;ul&gt;&#10;&#9;&lt;li&gt; sudo apt-get install python-software-properties&lt;/li&gt;&#10;&#9;&lt;li&gt;sudo add-apt-repository ppa:mighost/ppa&lt;/li&gt;&#10;&lt;li&gt;sudo apt-get update&lt;/li&gt;&#10;&lt;li&gt;### The following was pulled from 1.12.0~201309171613-1ppa1~precise in a dpkg --list. You likely don't need to mess with repo preferences.###&lt;/li&gt;&#10;&lt;li&gt;sudo apt-get install wireshark-common libwireshark3 libwireshark-data libwireshark3 libwiretap3 &lt;/li&gt;&#10;&lt;li&gt;sudo wireshark&lt;/li&gt;&#10;&lt;li&gt;### To run remotely you can connect using X over ssh with 'ssh -XY &lt;ip-address&gt;&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;a href="http://ppa.launchpad.net/mighost/ppa/ubuntu/" target="_blank"&gt;Link to the PPA Repo&lt;/a&gt;&#10;&lt;/aside&gt;&#10;&lt;p&gt;For those looking to learn or begin some development work with OpenFlow your trusty friend is the OpenFlow Wireshark dissector. Unfortunately it is still not available as a built in plugin packaged with the Wireshark binary yet. So in the meantime it requires compiling wireshark to get the C header files to generate the shared object file to drop into the Wireshark plugin directory. First install MacPorts, then compile Wireshark with MacPorts and lastly compiling the OpenFlow Dissector.&lt;/p&gt;</description></item><item><title>Pre-Built OpenDaylight VM Images</title><link>https://networkstatic.net/pre-built-opendaylight-vm-images/</link><pubDate>Mon, 06 May 2013 03:00:59 +0000</pubDate><guid>https://networkstatic.net/pre-built-opendaylight-vm-images/</guid><description>&lt;h2&gt;Pre-Built OpenDaylight VM Images&lt;/h2&gt;&#10;&lt;aside class="legacy-callout"&gt;&lt;strong&gt;Update&lt;/strong&gt;: We have new images for download now. Please see this post:&#10;&lt;a href="https://networkstatic.net/opendaylight-openstack-integration-devstack-fedora-20/" target="_blank" rel="noopener noreferrer"&gt;OpenDaylight OpenStack Integration with DevStack on Fedora&lt;/a&gt;&#10;There are more images on the OpenDaylight web site:&#10;&lt;a href="http://www.opendaylight.org/software" target="_blank" rel="noopener noreferrer"&gt; OpenDaylight Downloads Page&lt;/a&gt;&#10;&lt;/aside&gt;&#10;&lt;hr&gt;&#10;While there is still some uncertainty on the platform details of OpenDaylight, there isn't uncertainty in my mind, where I will be devoting my time for the rest of the year. I put up a couple of Pre-Built OpenDaylight VM Image, made up of the two proposed bootstrap controllers and OpenFlow tools, on a couple of VM images. I split it into dev and ops images so anyone curious or having trouble getting things installed can pull these down. Very little if any Linux knowledge is required. Once the project consolidates, I will do the same with the VMs. This is not anything official from ODP. This is merely a VM that has two controller proposals. I think it is important for those interested in OpenDaylight and ideally, what direction the community collectively decides is necessary and flexible enough to fit as broad a community as possible, rather then niche hyper-scale networks.&#10;&lt;hr /&gt;&#10;&lt;p&gt;&lt;a href="http://www.opendaylight.org" target="_blank"&gt;OpenDaylight&lt;/a&gt; is run by the Linux foundation based off meritocracy rather then a handful of people. For what it is worth, this is a real life open source project, very much like OpenStack. Someone like myself, who doesn&amp;rsquo;t work for Google, MS, FBook etc, that hasn&amp;rsquo;t paid to join this, or other consortiums, yet still was able to push a &lt;a href="https://networkstatic.net/wp-content/uploads/2013/05/ODP-Pen-Test.png" target="_blank"&gt;commit&lt;/a&gt; to the project. Thus, my optimism and excitement. Take a look at both of the projects, wether ops or dev oriented, both are have had a lot of work put into them and hopefully will blend into a good base for everyone to begin contributing to. I am sure the TSC (Technical Steering Committee) would appreciate feedback from the community over the next few months from actual networking pros who get paid to design, build and operate networks.&lt;/p&gt;</description></item><item><title>SDN, OpenFlow and OpenDaylight Updates and Recordings</title><link>https://networkstatic.net/sdn-openflow-and-opendaylight-updates-and-recordings/</link><pubDate>Mon, 29 Apr 2013 02:27:34 +0000</pubDate><guid>https://networkstatic.net/sdn-openflow-and-opendaylight-updates-and-recordings/</guid><description>&lt;h2&gt;SDN, OpenFlow and OpenDaylight Updates and Recordings&lt;/h2&gt;&#10;It's been a busy few weeks in the SDN debate. I am posting some SDN updates from April along with some recordings from various events. The Open Networking Summit held its event. Only a few of the videos have posted so far. The keynotes and presentations that stuck out to me were, Rose Schooler from Intel, Bruce Davie from Nicira/Vmware, Nick Mckeown, Rob Sherwood from BigSwitch and most importantly the OpenDaylight technical steering committee (TSC) Q&amp;amp;A.&#10;&lt;hr /&gt;&#10;&lt;h2&gt;OpenDaylight Q&amp;amp;A Audio Recording&lt;/h2&gt;&#10;The highlight of ONS and hands down the entire year is the OpenDaylight consortium. The project is open source (OSS) where each vendor has one vote. Value is measured by quality and quantity of code. Measuring a vendors contribution to the OpenDaylight project is quite easy by looking at the &lt;a href="https://git.opendaylight.org/gerrit/gitweb?p=controller.git;a=log" target="_blank"&gt;ODP project commits&lt;/a&gt;. The days of SDN message control and closed circles has served its purpose but will fade in relevance. Hard to compete with OSS without a large tent and community support. OpenStack set the course for networking and incumbents seem to be learning from OpenStack misses. Point in case, Cisco starting OSS consortiums rather then Vmware avoiding OpenStack until post Nicira acquisition.&#10;&lt;hr /&gt;&#10;&lt;p&gt;The audio is from my handheld recorder so quality is what it is. I think its fairly listenable though.&lt;/p&gt;</description></item><item><title>Open Networking Summit 2013 Is Streaming</title><link>https://networkstatic.net/open-networking-summit-2013-is-streaming/</link><pubDate>Mon, 15 Apr 2013 04:08:36 +0000</pubDate><guid>https://networkstatic.net/open-networking-summit-2013-is-streaming/</guid><description>&lt;h2&gt;Open Networking Summit 2013 Is Streaming&lt;/h2&gt;&#10;&lt;p&gt;The Open Networking Summit 2013 is going to be live streaming a good chunk of the content. Thats outstanding since most people don&amp;rsquo;t get a chance to travel. The ONS is ground zero for SDN and specifically OpenFlow. It is a great mix of vendors, researchers and &lt;a href="http://packetpushers.net/ons-2013-brings-together-the-entire-sdn-ecosystem-on-april-15-17/" target="_blank"&gt;community&lt;/a&gt; working out potential future paths of networkings. Head over to see the streams starting Monday April 15th for three days of outstanding presentations including Vincent Cerf from Google.&lt;/p&gt;</description></item><item><title>Importing OpenDaylight Into Eclipse</title><link>https://networkstatic.net/importing-opendaylight-into-eclipse/</link><pubDate>Sun, 14 Apr 2013 16:49:16 +0000</pubDate><guid>https://networkstatic.net/importing-opendaylight-into-eclipse/</guid><description>&lt;h2&gt;Importing OpenDaylight Into Eclipse&lt;/h2&gt;&#10;This is a quick video for importing OpenDaylight into Eclipse for development. You need to build OpenDaylight with Maven prior to importing it into Eclipse. Once you build ODL from the CLI, you can either run it from there for learning OpenFlow or getting to know the OpenDaylight controller or go on to importing the controller into Eclipse. For those new to Eclipse, it is a free and open source (FOSS) integrated development environment (IDE) that supports Windows, Mac and Linux. Once imported and built in Eclipse, you can run the project from within the IDE for test/dev.&#10;&lt;hr&gt;&#10;Here is a recording from ONS 2013. This was a Q&amp;A session with the technical steering committee (TSC). The recording is pretty grainy since it was just a pocket recorder. You can't hear David Meyer very well in the audio but you can hear the panel well enough. The ONS does a nice job of getting a lot of the content on their &lt;a href="http://www.youtube.com/user/OpenNetSummit" target="_blank"&gt;YouTube&lt;/a&gt; channel. I will replace this with a link to that once it posts.&lt;a href="https://networkstatic.net/wp-content/uploads/2013/04/OpenDaylight-ONS-ODP.mp3" target="_blank" rel="noopener noreferrer"&gt;OpenDaylight TSC Q&amp;A from ONS 2013&lt;/a&gt;&#10;&lt;hr /&gt;&#10;&lt;h2&gt;Video: Importing OpenDaylight Into Eclipse &lt;/h2&gt;&#10;&lt;hr /&gt;&#10;&lt;p&gt;I will keep this page or some pointer to a page updated as the project matures. Make sure you use JDK7 and not JDK6. See this thread on the ODL &lt;a href="https://lists.opendaylight.org/pipermail/controller-dev/2013-April/000171.html" target="_blank"&gt;Listserv&lt;/a&gt;. The audio is very low, I will remix it in the next day or two and upload it.&#10;[youtube url=&amp;ldquo;http://youtu.be/vjRJ8d_0Jwo&amp;amp;vq=hd720&amp;rdquo; width=&amp;ldquo;630&amp;rdquo; height=&amp;ldquo;360&amp;rdquo; hd=&amp;ldquo;1&amp;rdquo;]&lt;/p&gt;</description></item><item><title>OpenDaylight OpenFlow Tutorial</title><link>https://networkstatic.net/opendaylight-openflow-tutorial/</link><pubDate>Fri, 12 Apr 2013 20:12:37 +0000</pubDate><guid>https://networkstatic.net/opendaylight-openflow-tutorial/</guid><description>&lt;h2&gt;OpenDaylight OpenFlow Tutorial&lt;/h2&gt;&#10;The OpenDaylight project was announced this week and they already have working controller code up on a repositry. Under the controller hood, looks to be the OSGI framework originally forked from &lt;a href="https://openflow.stanford.edu/forums/topic/243-looking-for-beta-testers/" target="_blank"&gt;David Erickson's&lt;/a&gt; Beacon controller. It's a simple tutorial to help kickstart the dependencies and getting a chance to learn how instantiating OpenFlow flow rules work. This was the first time I have looked at OpenDaylight, so I was learning as I did the screencast.&#10;&lt;h2&gt;OpenDaylight Installation and Setup&lt;/h2&gt;&#10;&lt;p&gt;If you do not want to mess with the code and just run the controller it is super simple. Download the &lt;a href="http://mininet.org" target="_blank"&gt;Mininet&lt;/a&gt; image now managed by the &lt;a href="http://onlab.us" target="_blank"&gt;On.lab&lt;/a&gt;. I personally prefer Mininet for dev/test.&lt;/p&gt;</description></item><item><title>The Cisco ONE SDN Controller</title><link>https://networkstatic.net/the-cisco-one-sdn-controller/</link><pubDate>Fri, 12 Apr 2013 05:11:13 +0000</pubDate><guid>https://networkstatic.net/the-cisco-one-sdn-controller/</guid><description>&lt;h2&gt;The Cisco ONE SDN Controller GUI&lt;/h2&gt;&#10;Cisco announced the ONE controller at Cisco Live last summer. The ONE has been in Beta for a few months now. There is still plenty of fragmentation around what SDN is and what it should solve. One generally accepted concept is the way we operate networks today, is showing signs of age. The announcement of OpenDaylight this week, pretty much sealed the SDN deal. Right, wrong or stupid, the old way of doing things will change. One generally agreed upon outcome is the way we operate networks, hand coding APIs calls into VTY sessions may be subject to change. So what is it going to look like, a GUI or an API using web services calls to operate the network? Yes.&#10;&lt;h2&gt;Cisco ONE SDN/OpenFlow Controller GUI&lt;/h2&gt;&#10;It's good to see a functional GUI on a controller, that will be available soon. While some of us love to roll up our sleeves and hack away on code, many engineers aren't nerds like you and me. Even more often, network professionals would like to, but don't have the time. When people start learning OpenFlow, the rawness can be a bit daunting for those not used to OSS, which is many engineers/operators today. The key will be to see if OpenDaylight is a stall tactic for Insieme. OSS will ideally prevent this from being a misdirection.&#10;&lt;p&gt;The idea that you will have to write code to operate networks of the future, is not what I am seeing in my neck of the woods (as much as I would like to). Most of those I know need commercial products because of lack of time, lack of resources and risk avoidance. For those who are indifferent or just don&amp;rsquo;t have the time to learn scripting, Python, JS, Java, Linux, etc there will be functional GUIs to operate, just like wireless and VoIP controllers today.&lt;/p&gt;</description></item><item><title>Installing OpenStack Grizzly with DevStack</title><link>https://networkstatic.net/installing-openstack-grizzly-with-devstack/</link><pubDate>Mon, 08 Apr 2013 06:53:22 +0000</pubDate><guid>https://networkstatic.net/installing-openstack-grizzly-with-devstack/</guid><description>&lt;h2&gt;OpenStack Multi-Node DevStack Nova Network Tutorial&lt;/h2&gt;&#10;&lt;p&gt;DevStack is a scripted OpenStack installer  maintained for developers to prototype and debug. It is also handy for operators to proof concepts and test new services and configurations. This is a good starter for folks new to OpenStack to help understand how to install and operate OpenStack. Some folks have been asking about multi-node DevStack deployment using nova network, so I thought this tutorial might help.&lt;/p&gt;</description></item><item><title>SDN Dominates NFD#5</title><link>https://networkstatic.net/sdn-dominates-nfd5/</link><pubDate>Sat, 30 Mar 2013 06:09:43 +0000</pubDate><guid>https://networkstatic.net/sdn-dominates-nfd5/</guid><description>&lt;h2&gt;SDN Dominates NFD#5&lt;/h2&gt;&#10;SDN was the soup dajoure at &lt;a href="http://techfieldday.com/event/nfd5/" target="_blank"&gt;Networking Field Day #5&lt;/a&gt; and rightfully so. My friends are not only talented bloggers, but also some of the best architects, engineers and operators in the networking field. The networking industry has gone without significant innovation since at least MPLS and arguably Ethernet. Our network architectures are snapshots of the cold war. Every device must maintain a full consistent state in case Reagan or Gorbachev hit the red button.&#10;&lt;p&gt;Every vendor out there is hedging their bets on a combination of the following. There are a few more arguable points but to keep things manageable I am sticking to the following:&lt;/p&gt;</description></item><item><title>Big Switch Introduces Switch Light</title><link>https://networkstatic.net/big-switch-introduces-switch-light/</link><pubDate>Tue, 26 Mar 2013 12:18:50 +0000</pubDate><guid>https://networkstatic.net/big-switch-introduces-switch-light/</guid><description>&lt;h2&gt;Big Switch Introduces Switch Light&lt;/h2&gt;&#10;Big Switch took a step towards rounding out their portfolio with introducing plans to release a software switching software to integrate into &lt;a href="https://nerdtwilight.wordpress.com/category/odms/" target="_blank"&gt;ODM&lt;/a&gt; (Original Design Manufacturer) and vendor hardware switches. The “thin switching” software is made up using the FOSS (Free and Open Source Software) Indigo project from Stanford University and Project &lt;a href="http://www.projectfloodlight.org" target="_blank"&gt;Floodlight&lt;/a&gt;. Just as various vendors have used &lt;a href="http://openvswitch.org" target="_blank"&gt;Open vSwitch&lt;/a&gt; as their early OpenFlow agent, so have other vendors used Indigo.&#10;&lt;h2 class="legacy-heading"&gt;OpenFlow Enablement for More Switching Platforms&lt;/h2&gt;&#10;&lt;figure class="legacy-figure"&gt;&lt;img src="https://networkstatic.net/wp-content/uploads/2013/03/Big-Light-Architecture1.png" alt="Big Light SDN OpenFlow"&gt;&lt;/figure&gt;&#10;&lt;p&gt;Big Switch will provide a forwarding driver to the ODM to place above the Broadcom ASIC firmware that will provide hooks into the ODM hardware. There is also support for Open vSwitch that will be open sourced. That would be to presumably get more specific features from OVS then would be available from the project.&lt;/p&gt;</description></item><item><title>Be The Steamroller Not The Road</title><link>https://networkstatic.net/be-the-steamroller-not-the-road/</link><pubDate>Tue, 19 Mar 2013 04:41:52 +0000</pubDate><guid>https://networkstatic.net/be-the-steamroller-not-the-road/</guid><description>&lt;h2&gt;Be The Steamroller Not The Road&lt;/h2&gt;&#10;&lt;blockquote class="pullquote"&gt;“Once a new technology rolls over you, if you're not part of the steamroller, you're part of the road.”&lt;footer&gt;-Stewart Brand&lt;/footer&gt;&lt;/blockquote&gt;&#10;I always chuckle when I hear SDN or OpenFlow "bigots". I find that it is normally vendors being flippant towards SDN in general are from a handful of camps:&#10;&lt;hr&gt;&#10;&lt;ul&gt;&#10;&#9;&lt;li&gt;Incumbent vendors, realizing the days of high profit margins, through vertical integration on commodity silicon are coming to an end.&lt;/li&gt;&#10;&#9;&lt;li&gt;Companies who think proprietary southbound protocols is a good place to try and differentiate. The irony is, most of those are doing flow based forwarding with proprietary messaging protocols. Net is, the same flexibility and maybe even better than OF, but using closed wire protocols. So it makes sense, of course they trash OF because they want to separate themselves using the same concepts and be the "innovator". I personally think the application layer is the place to focus to be effective. I am expecting Intel to own the &lt;strong&gt;edge &lt;/strong&gt;hardware market someday, but thats for another day.&lt;/li&gt;&#10;&#9;&lt;li&gt;Then there is the a-typical IT guy, that hates change. Hey, thats understandable. I like stability as much as the next fear of failure driven person. Server guys freaked out over server virtualization, mainframe guys hugged their water cooled monoliths all the way to the dumpster, but at the end of the day, IT abstraction doesn't shrink jobs. Horizontalization creates jobs and enables innovation.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;hr&gt;&#10;When people spend time to understand that OpenFlow is merely an open messaging protocol to instantiate flow based forwarding. &lt;a href="http://etherealmind.com/sdn-use-case-firewall-migration-in-the-enterprise/" target="_blank"&gt;Flow based forwarding&lt;/a&gt; integrates L4 into forwarding decisions. L4 adds rudimentary application awareness. OpenFlow is merely a means of forwarding L1-L4 in a single protocol. Thats not to say you don't need other protocols. OpenFlow has no awareness of port provisioning etc. That leaves plenty of room for differentiation in the management plane and actually building &lt;a href="http://blog.ioshints.info/2013/03/nec-programmableflow-scalability.html" target="_blank"&gt;applications&lt;/a&gt; to control the network. Odds are, one vendors SDN solution isn't much different from the next when you look under the hood. Outside of performance, look for application differentiation, not who has the best flow-based forwarding protocol.&#10;&lt;figure class="legacy-figure"&gt;&lt;img src="https://networkstatic.net/wp-content/uploads/2013/03/DC-SP-SDN.png" alt="SDN in the Data Center and Service Provider"&gt;&lt;/figure&gt;&#10;&lt;p&gt;A vendor agnostic southbound forwarding abstraction is all OpenFlow is. Creating network operating systems and extracting state to run programs against is much more interesting but we don&amp;rsquo;t get there without a few key protocols.&lt;/p&gt;</description></item><item><title>Configure an HP OpenFlow Switch for Floodlight</title><link>https://networkstatic.net/configure-an-hp-openflow-switch-for-floodlight/</link><pubDate>Sat, 16 Mar 2013 05:20:31 +0000</pubDate><guid>https://networkstatic.net/configure-an-hp-openflow-switch-for-floodlight/</guid><description>&lt;h2&gt;Configure an HP OpenFlow Switch for Floodlight &lt;/h2&gt;&#10;This is a revised tutorial to configure an HP OpenFlow switch for Floodlight or any other OpenFlow controller. HP revised its firmware a few months back which is great. HP has been supporting OpenFlow on its switches with generally available code longer then any other networking vendor. Other vendors with GA OpenFlow firmware are &lt;a href="http://community.brocade.com/thread/8445?start=0&amp;tstart=0" target="_blank"&gt;Brocade&lt;/a&gt; and Pica8. Maturity of OpenFlow agents should be taken into account when purchasing hardware. Most agents are Open vSwitch based but vendor allocations to software development of porting OVS has been slow while waiting on large volume customer demand.&#10;&lt;h2&gt;Hybrid OpenFlow Ships in the Night&lt;/h2&gt;&#10;Hybrid OpenFlow support is a must for any vendor. We have reviewed different &lt;a href="https://networkstatic.net/openflow-sdn-hybrid-deployment-strategies/" target="_blank"&gt;hybrid architectures&lt;/a&gt; such as &lt;a href="https://networkstatic.net/hybrid-openflow-using-the-normal-action/" target="_blank"&gt;normal&lt;/a&gt; and "ships in the night". For this tutorial we will use the simple ships in the night, meaning there is one Vlan enabled with OpenFlow (VID 3) and one on the native network (VID 1). The native network on Vlan 1 is also the control channel for the FloodLight OpenFlow controller and the host on the native network. The control Vlan could just as easily be a dedicated management network.&#10;&lt;figure class="legacy-figure"&gt;&lt;img src="https://networkstatic.net/wp-content/uploads/2013/03/OpenFlow-Hybrid-HP.png" alt="HP OpenFlow Hybrid Ships in the Night"&gt;&lt;/figure&gt;&#10;&lt;h2&gt;Hybrid OpenFlow Gateways&lt;/h2&gt;&#10;The OpenFlow Vlan L3 gateway can be as simple as a native switch or router tapped into the Vlan with an L3 interface. OpenFlow hosts can use that interface as the default gateway to leave the SDN island. The SDN edge can also use OFPP_Normal to push flows to the normal forwarding pipeline. With one OpenFlow rule you can have all traffic processed as it normally would by the switch. HP supports the "normal" OpenFlow action. All vendors need strong hybrid OpenFlow support if they expect to be taken seriously for early SDN non-vSwitch networks.&#10;&lt;h2&gt;Download and Configure The &lt;a href="http://floodlight.openflowhub.org" target="_blank"&gt;Floodlight&lt;/a&gt; OpenFlow Controller&lt;/h2&gt;&#10;Floodlight and &lt;a href="http://www.noxrepo.org/pox/about-pox/" target="_blank"&gt;POX OpenFlow&lt;/a&gt; controllers are both super easy to get up and running. Both can load as flood and learn &lt;a href="https://networkstatic.net/openflow-proactive-vs-reactive-flows/" target="_blank"&gt;reactive switches or proactive&lt;/a&gt; only configurations. For building the controller on CentOS check out a colleague &lt;a href="https://twitter.com/buraglio" target="_blank"&gt;Nick Buraglio's&lt;/a&gt; blog &lt;a href="http://www.forwardingplane.net/2013/02/building-a-floodlight-openflow-controller-on-centos-6/" target="_blank"&gt;post.&lt;/a&gt; &#10;&lt;pre class="brush: bash; gutter: true; first-line: 1; highlight: []; html-script: false"&gt;&#10;sudo apt-get install openjdk-7-jre git&#10;git clone git://github.com/floodlight/floodlight.git&#10;cd floodlight&#10;ant&#10;java -jar target/floodlight.jar&lt;/pre&gt;&#10;&lt;hr&gt;&#10;&lt;h2&gt;Configure the HP switch for OpenFlow&lt;/h2&gt;&#10;&lt;p&gt;The follwoing HP configuration refelcts the latest firmware. Use &amp;ldquo;show open flow ?&amp;rdquo; to view related OpenFlow operational commands. This will also tell you what flows are in hardware and software. My colleague &lt;a href="https://twitter.com/owens_bill" target="_blank"&gt;Bill Owens&lt;/a&gt; wrote a nice article at &lt;a href="http://packetpushers.net/openflow-switching-performance-not-all-tcam-is-created-equal/" target="_blank"&gt;Packet Pushers&lt;/a&gt; recently on this topic that I highly recommend.&lt;/p&gt;</description></item><item><title>Open vSwitch on VirtualBox</title><link>https://networkstatic.net/open-vswitch-on-virtualbox/</link><pubDate>Wed, 13 Mar 2013 00:03:06 +0000</pubDate><guid>https://networkstatic.net/open-vswitch-on-virtualbox/</guid><description>&lt;h2&gt;Open vSwitch on VirtualBox&lt;/h2&gt;&#10;Here is a quick tutorial for installing Open vSwitch on VirtualBox. &lt;a href="https://www.virtualbox.org" target="_blank"&gt;VirtualBox&lt;/a&gt; is an open source virtualization project from Oracle. It is supported on Windows, Mac, BSD and Linux to name a few. It has a nice GUI for VM management out of the box. Open vSwitch is an open source vSwitch from &lt;a href="http://networkheresy.com" target="_blank"&gt;Martin Casado&lt;/a&gt;, &lt;a href="http://benpfaff.org/papers/index.html" target="_blank"&gt;Ben Pfaff&lt;/a&gt; and a whole &lt;a href="http://www.ohloh.net/p/openvswitch/factoids" target="_blank"&gt;crew of awesome&lt;/a&gt;. If you are here, OVS probably doesn't require anymore explanation, &lt;a href="https://networkstatic.net/tag/openvswitch/" target="_blank"&gt;learn it&lt;/a&gt;, love it.&#10;&lt;h2&gt;Install VirtualBox&lt;/h2&gt;&#10;Install VirtualBox from the VirtualBox repository.&#10;&lt;pre class="brush: bash; gutter: true"&gt;Add the following repo to /etc/apt/sources.list &#10;deb http://download.virtualbox.org/virtualbox/debian precise contrib&#10;wget -q http://download.virtualbox.org/virtualbox/debian/oracle_vbox.asc -O- | sudo apt-key add -&#10;sudo apt-get update&#10;sudo apt-get install dkms&#10;sudo apt-get install virtualbox-4.2&lt;/pre&gt;&#10;&lt;h2&gt;Install Open vSwitch from repo&lt;/h2&gt;&#10;Install Open vSwitch from Package. This is easiest for those not familiar with compiling from source or just need basic functionality rather than the latest features.&#10;&lt;pre class="brush: bash; gutter: true"&gt;sudo apt-get install openvswitch-datapath-source bridge-utils&#10;sudo module-assistant auto-install openvswitch-datapath&#10;sudo apt-get install openvswitch-brcompat openvswitch-common openvswitch-controller&lt;/pre&gt;&#10;&lt;h2&gt;Open vSwitch Install from Source &lt;/h2&gt;&#10;Install dependencies and install from source on Ubuntu Linux.&#10;&lt;pre class="brush: bash; gutter: true"&gt;apt-get install -y git python-simplejson python-qt4 python-twisted-conch automake autoconf gcc&#10;uml-utilities libtool build-essential git pkg-config linux-headers-`uname -r`&#10;git clone git://openvswitch.org/openvswitch&#10;cd openvswitch&#10;./boot.sh&#10;./configure --with-linux=/lib/modules/`uname -r`/build&#10;make &amp;amp;&amp;amp; make install&#10;./boot.sh&#10;./configure --with-linux=/lib/modules/`uname -r`/build&#10;make &amp;amp;&amp;amp; make install&#10;insmod datapath/linux/openvswitch.ko&#10;touch /usr/local/etc/ovs-vswitchd.conf&#10;mkdir -p /usr/local/etc/openvswitch&#10;ovsdb-tool create /usr/local/etc/openvswitch/conf.db vswitchd/vswitch.ovsschema&#10;ovsdb-server /usr/local/etc/openvswitch/conf.db \&#10;--remote=punix:/usr/local/var/run/openvswitch/db.sock \&#10;--remote=db:Open_vSwitch,manager_options \&#10;--private-key=db:SSL,private_key \&#10;--certificate=db:SSL,certificate \&#10;--bootstrap-ca-cert=db:SSL,ca_cert --pidfile --detach --log-file&#10;ovs-vsctl --no-wait init&#10;ovs-vswitchd --pidfile --detach&lt;/pre&gt;&#10;&lt;h2&gt;Create Open vSwitch bridge and interfaces&lt;/h2&gt;&#10;To setup the virtual interfaces use Tuntap. Tuntap sets up a emulates an L2 interface. That interface will show up in the interface as a physical interface.&#10;&lt;pre class="brush: bash; gutter: true"&gt;ovs-vsctl add-br br0&#10;ip tuntap add mode tap vnet0&#10;ip link set vnet0 up&#10;ovs-vsctl add-port br0 vnet0&#10;ip link (View the created interface)&lt;/pre&gt;&#10;&lt;hr&gt;&#10;&lt;figure class="legacy-figure"&gt;&lt;img src="https://networkstatic.net/wp-content/uploads/2013/03/openvswitch-virtualbox.png" alt="Open vSwitch VirtualBox"&gt;&lt;/figure&gt;&#10;&lt;h2&gt;Spin up VirtualBox instances with Open vSwitch Interfaces &lt;/h2&gt;&#10;For testing Open vSwitch or any other hypervisor testing, I highly recommend this Linux image &lt;a href="http://wiki.qemu.org/Testing" target="_blank"&gt;linux-0.2.img&lt;/a&gt;. It only takes a couple of MB of memory. It is perfect for &lt;a href="https://networkstatic.net/nested-kvm-hypervisor-support/" target="_blank"&gt;nested hypervisor&lt;/a&gt; testing.&#10;&lt;figure class="legacy-figure"&gt;&lt;img src="https://networkstatic.net/wp-content/uploads/2013/03/openvswitch-VM.png" alt="Open vSwitch VM"&gt;&lt;/figure&gt;&#10;&lt;h2&gt;Connect the Open vSwitch bridge to the physical network&lt;/h2&gt;&#10;&lt;p&gt;You can put the following into a text file and give it execute permissions with “chmod +x filename” and then run it “./filename”. If your network settings are right it should flip the IP to the bridge and not cut you off. Keyword “should” so have a way to get to the box if you cut yourself off. What is happening here is you are placing both the virtual interface &amp;ldquo;vnet0&amp;rdquo; and the physical Nic &amp;ldquo;eth0&amp;rdquo; into the same bridge &amp;ldquo;br0&amp;rdquo;. You can think of a bridge as a logical grouping of virtual and physical interface much like a locally significant VLAN without the 0x8100 Ethertype framing and tag.&lt;/p&gt;</description></item><item><title>The Good and Bad of Wireless</title><link>https://networkstatic.net/the-good-and-bad-of-wireless/</link><pubDate>Sun, 10 Mar 2013 17:52:07 +0000</pubDate><guid>https://networkstatic.net/the-good-and-bad-of-wireless/</guid><description>&lt;h2&gt;The Good and Bad of Wireless&lt;/h2&gt;&#10;The Good and Bad of Wireless :A while back, I posted some numbers on campus 802.11 growth. Wether cellular or 802.11, the numbers are big. The numbers show &lt;a href="https://networkstatic.net/enterprise-802-11-wireless-growth-part-3/" target="_blank" rel="noopener noreferrer"&gt;%1000 annual growth&lt;/a&gt;in the 802.11 campus which reflects smart phones, tablets, laptops and soon to be glasses and watches painted all over people. In networking, customer growth typically linearly correlates into the need for more engineers, architects and operators to absorb the growth. When it comes to managing wireless networks, that trend is consistently disproved. That said, all is not rosey in wireless space, there is a major lack of interoperability that needs to be dealt with at some point. Before we dig into the good and bad of wireless, let's level set the framework.&#10;&lt;h2&gt;How is wireless so different?&lt;/h2&gt;&#10;&lt;ul&gt;&#10;&#9;&lt;li&gt;Management - Centralized management for provisioning, orchestration and troubleshooting. The driver was RF orchestration.&lt;/li&gt;&#10;&#9;&lt;li&gt;Oversubscription and Zero Touch Provisioning - The ability to oversubscribe clients on RF since it is a shared medium can readily absorb growth without the need for new physical elements. New clients do not require slow provisioning cycles, cabling, VIDs etc.&lt;/li&gt;&#10;&#9;&lt;li&gt;Policy Application - Bring Your Own Disaster (BYOD) is less then awful in wireless then the wired side. This is enabled because almost all solutions have various centralization techniques that wedge a bump in the forwarding pipeline to apply policy. Reasonable tight control loops in networking only exist in wireless orchestration today.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h2&gt;The Good: Wireless Management&lt;/h2&gt;&#10;Early wireless was a monolithic device. All functionality was self contained. Some early startups (particularly Aruba) saw the lack of functionality a completely distributed system presented. The inability to orchestrate RF, made for poor performance on the client side. Centralized controllers often leverage centralized forwarding or centralized forwarding institutions. What this enabled was a rich set of policy application in the security and QoS realm. This does not necessarily mean, tunnel all traffic through a controller or a collection of federated controllers. A TCO including bandwidth availability and component cost, should dictate the levels of centralized forwarding. There are also some emerging technologies that are presumably using a proprietary wire protocol to instantiate forwarding policy while maintaining centralized management and orchestration.&#10;&lt;h2&gt;The Bad: Wireless Management&lt;/h2&gt;&#10;While the wireless industry can pat itself on the back for delivering products that are manageable, it represents one of the biggest vendor lock-ins in networking. Since wireless is so proprietary, there are hardly any mechanisms to have rich interoperability between vendor controllers and AP. Proprietary&#10;How would a large campus, hospital or any other enterprise with thousands of contiguous APs that require L3 roaming, RF orchestration, feature parity and all of the other tricks required to have a stable RF environment and an acceptable user experience. I expect those questions are being asked by the wireless community leaders in the industry. If they aren't they should be. I'm willing to bet some of the &lt;a href="http://techfieldday.com/event/wfd4/" target="_blank"&gt;Wireless Field Day&lt;/a&gt; delegates are all over it. &#10;&lt;h2&gt;Wireless at Network Field Day #5&lt;/h2&gt;&#10;&lt;ul&gt;&#10;&#9;&lt;li&gt;At network field day we had two vendors talk to us about their wireless solutions, Cisco and Ruckus.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h2 class="legacy-heading"&gt;The Future is Software&lt;/h2&gt;&#10;The 1Q12 market share looked as follows:&#10;&lt;figure class="legacy-figure"&gt;&lt;img src="https://networkstatic.net/wp-content/uploads/2013/03/Wireless-Marketshare.png" alt="Wireless Market Share"&gt;&lt;/figure&gt;&#10;&lt;p&gt;In my opinion this is much less pure RF differentiation. Who has a better widget than the next guy is rarely ferreted out in RFPs. At the end of the day, the pieces and parts are commodity. Other then Cisco&amp;rsquo;s dominance in the enterprise the first reason for such disproportionate market share is the vendor lock mentioned earlier, rip and replace at scale is typically a touch TCO. The second reason being, Cisco&amp;rsquo;s tight integration into its NAC product line. Centralized operating systems (even if only the management plane) enable policy. The following silly quadrants, reflect the efforts at vertical integration Cisco does a phenomenal job at selling:&lt;/p&gt;</description></item><item><title>Networking Field Day #5 - A Community Event</title><link>https://networkstatic.net/networking-field-day-5-a-community-event/</link><pubDate>Mon, 04 Mar 2013 02:14:20 +0000</pubDate><guid>https://networkstatic.net/networking-field-day-5-a-community-event/</guid><description>&lt;h2&gt;Networking Field Day #5 - A Community Event&lt;/h2&gt;&#10;&lt;blockquote class="pullquote"&gt;I'm not the smartest fellow in the world, but I can sure pick smart colleagues.&lt;footer&gt;Franklin D. Roosevelt&lt;/footer&gt;&lt;/blockquote&gt;&#10;Networking Field Day is upon us again. The days of March 6-8 some of the best in the business are going to be together again to have participating vendors pitch their product strategies to the NFD delegates and more importantly, to everyone else watching the live stream. I was invited to attend Network Field #5 and I humbly accepted. &lt;a href="http://techfieldday.com/event/nfd4/" target="_blank"&gt;Network Field Day #4&lt;/a&gt; was a wonderful experience where I made lifelong colleagues and friends. &#10;&lt;h2&gt;IT Community Leaders&lt;/h2&gt;&#10;&lt;blockquote class="pullquote"&gt;We make a living by what we get. We make a life by what we give.&lt;footer&gt;Winston Churchill&lt;/footer&gt;&lt;/blockquote&gt;&#10;NFD delegates are industry thought leaders and more importantly community developers and mentors to future leaders in IT. To name just a few guys, involved in Network Field Day, that have gone out of their way in my professional development, that I look to as role models are &lt;a href="http://blog.fosketts.net" target="_blank"&gt;Stephen Foskett&lt;/a&gt;, &lt;a href="http://etherealmind.com" target="_blank"&gt;Greg Ferro&lt;/a&gt;, &lt;a href="http://ethancbanks.com" target="_blank"&gt;Ethan Banks&lt;/a&gt; and &lt;a href="http://blog.ioshints.info" target="_blank"&gt;Ivan Pepelnjak&lt;/a&gt; define community and leadership in IT. They go out of their way to see others to be successful and encourage fellowship amongst our developing community. The network is changing mankind, I have the utmost respect for those who sacrifice time with family and friends because they are dedicated to making a difference.&#10;&lt;blockquote class="pullquote"&gt;Many people are good at talking about what they are doing, but in fact do little. Others do a lot but don't talk about it; they are the ones who make a community live.&lt;footer&gt;Jean Vanier, Community Growth&lt;/footer&gt;&lt;/blockquote&gt;&#10;&lt;h2&gt;NFD#5 Thoughts From other Delegates and Past Videos&lt;/h2&gt;&#10;&lt;p&gt;&lt;a href="http://vimeo.com/51116387"&gt;Watch video on Vimeo&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Putting Together Provider Bridging, Provider Backbone Bridging, S-Tags and C-Tags</title><link>https://networkstatic.net/putting-together-provider-bridging-provider-backbone-bridging-s-tags-and-c-tags/</link><pubDate>Sun, 03 Mar 2013 04:38:13 +0000</pubDate><guid>https://networkstatic.net/putting-together-provider-bridging-provider-backbone-bridging-s-tags-and-c-tags/</guid><description>&lt;h2&gt;Putting Together Provider Bridging, Provider Backbone Bridging, S-Tags and C-Tags&lt;/h2&gt;&#10;Putting Together Provider Bridging, Provider Backbone Bridging, S-Tags and C-Tags: Understanding carrier bridging techniques is important, not just for provider operators, but also for engineers on the customer edge. When turning up or troubleshooting a circuit, carrier operators will ramble off C-tag and S-tag when many in the enterprise, are used to hearing Vlan ID in single tenancy deployments. More customers are transitioning to L2 circuits from carriers, to cut out carrier L3 routing that is often a complete nightmare to troubleshoot between carrier and customer. Provider bridging (QinQ) and provider backbone bridging (MAC-in-MAC) can be conceptually viewed as the layer 2 equivalent of virtual route forwarding (VRF-lite). These technologies can be signaled via MPLS. L3/VPNs have some advantages, when it comes to draining spoke sites to the Internet by reducing hub to spoke traffic. That said, most organizations drain traffic to the hub sites for policy application. This is a review of one of many ways providers carry L2 customer bridges, as less customers are willing to deal with the headache of having carriers route their traffic. Provider bridging can give the customer a dark fiber experience, which in turn, reduces OpEx to carrier and customer.&#10;&lt;figure class="legacy-figure"&gt;&lt;img src="https://networkstatic.net/wp-content/uploads/2013/03/PBB.png" alt="Provider Bridging 802.1ad"&gt;&lt;/figure&gt;&#10;&lt;h2&gt;Provider Bridging 802.1ad&lt;/h2&gt;&#10;Provider bridging is conceptually pretty simple, vlan stacking or QinQ (802.1Q in 802.1Q). The customer traffic is identified by a Vlan ID (VID) referred to as the C-tag (customer VID) in the 802.1Q framing format. When the C-tagged frame goes upstream to the service provider, it is encapsulated again by the carriers provider bridging edge network. Using 802.1ad encapsulation, the C-tag is then wrapped up with an S-tag (Service VID). Encapsulation in the carrier network allows for overlapping customer VIDs.&#10;&lt;h2&gt;Provider Backbone Bridging 802.1ah &lt;/h2&gt;&#10;Just as customer VIDs need to be masked off from one another to avoid overlap, so does the carrier. Provider Backbone Bridging is also reffered to as MAC in MAC since depending on the scenario, there can be up to 5 Ethertypes doing encapsulation. Some carriers require well over 4094 Vlan IDs to support circuits. Provider Backbone Bridging or MAC-in-MAC (802.1ah) allows for overlapping of S-Tag VIDs, while provider bridging or QinQ (802.1ad) allows for overlapping C-tags. MAC-in-MAC is backwards compatible with QinQ, as they are both tightly coupled to one another. The process is very similar to L3 VPN/VRFs and RFC1918 IPv4 addresses and path isolation for the customer and virtualization of the carrier network to oversubscribe for slicing. Both QinQ and provider backbone bridging are addressed in &lt;a href="https://www.opennetworking.org/images/stories/downloads/specification/openflow-spec-v1.3.0.pdf" target="_blank"&gt;OpenFlow v1.3&lt;/a&gt; spec.&#10;&lt;figure class="legacy-figure"&gt;&lt;img src="https://networkstatic.net/wp-content/uploads/2013/03/PBB-Topology.png" alt="Provider Backbone Bridging"&gt;&lt;/figure&gt;&#10;&lt;p&gt;Provider bridging can be designed in a hierarchal fashion to add scale and reduce complexity.&lt;/p&gt;</description></item><item><title>Hybrid OpenFlow Using The Normal Action</title><link>https://networkstatic.net/hybrid-openflow-using-the-normal-action/</link><pubDate>Thu, 21 Feb 2013 02:22:56 +0000</pubDate><guid>https://networkstatic.net/hybrid-openflow-using-the-normal-action/</guid><description>&lt;h2&gt;Hybrid OpenFlow Using The Normal Action&lt;/h2&gt;&#10;Hybrid OpenFlow Using The Normal Action: When a new technology is introduced in networking, it is not uncommon for most to transition that new technology into their network for test/dev or production by starting with small chunks at a time. &lt;a href="https://networkstatic.net/openflow-sdn-hybrid-deployment-strategies/" target="_blank"&gt;Hybrid OpenFlow &lt;/a&gt;deployments will used by many of us as a place to start with SDN with fairly low risk and flxible enough to integrate into existing architectures. Just a minimal edge deployment of OpenFlow provides the flexibility to apply new policy techniques never before possible outside of software switching. If you compare a hybrid OpenFlow edge to the overlay data center architectures, not much is different. Using the OpenFlow Normal action, represents the default route of hybrid flow based forwarding at the edge. The disruption and CapEx is fairly low since the hybrid model is still using traditional networks as you aggregate upstream into the native network. &lt;a href="https://networkstatic.net/openflow-coarse-vs-fine-flows/" target="_blank"&gt;Classify&lt;/a&gt; and then forward.&#10;&lt;p&gt;Overlay tunneling in the data center gets the attention because it can solve layer 2 adjacency requirements for live workload migrations (vMotion). Tunneling is where much focus has been, when the true innovation, is the classification at the edge before the flows get stuffed into tubes. There are very few, if any, good reasons to extend layer2 networks in that same manor in enterprise and provider networks, other than more broken L2 applications. That said, take aways the tunnels, s/vSwitch/HW Switch/g and you are left with an SDN edge attached to a native forwarding core. The main difference is, one edge device is virtual in a &lt;a href="http://openvswitch.org" target="_blank"&gt;vSwtich&lt;/a&gt; and the other is a physical switch (more on that in a future post). The commonality between virtual and physical is they can both be reduced to a forwarding target with similar primitives between the two for object instantiation. A key method for enabling a seemless transition is the OpenFlow normal forwarding action (OFPP_NORMAL). Proper processing at the edge to push into an LSP or any other data path at aggregation, is interesting in and of itself.&lt;/p&gt;</description></item><item><title>More Vendors Define Their SDN Strategy</title><link>https://networkstatic.net/more-vendors-define-their-sdn-strategy/</link><pubDate>Sat, 09 Feb 2013 05:03:16 +0000</pubDate><guid>https://networkstatic.net/more-vendors-define-their-sdn-strategy/</guid><description>&lt;h2&gt;More Vendors Define Their SDN Strategy&lt;/h2&gt;&#10;It was a busy week in SDN. Some pretty significant revelations gave us good directional indications for SDN in 2013. Most significantly is SDN is getting enough traction to drive significant investment and tough decisions to be made by the networking incumbents. As more vendors define their SDN strategy, we will see an increasing amount of commercial products, rather than slideware.&#10;&lt;h2&gt;Cisco ONE Webcast Series: An Introduction to OpenFlow&lt;/h2&gt;&#10;Cisco is giving an introductory WebEx lead by Dave Ward of Cisco and Matt Davy who recently left R&amp;amp;E for an SDN startup. Not much to say here, the webinar title speaks for itself. The most amusing thing I heard in reaction to this from a colleague was, "Cisco wants to teach us OpenFlow? @!#$! we teach them OpenFlow." After reassuring him hell didn't freeze over, we both agreed this is a positive sign. I am not expecting the presentation is to explain why OpenFlow is only suitable for Google or academics doing research projects, so certainly looking forward to it. I am personally looking forward to the presentation to help encourage more people to begin thinking about the SDN potential to their business, not the mechanism.&#10;&lt;ul&gt;&#10;&#9;&lt;li&gt;An introduction to OpenFlow: protocol, features, and future evolution&lt;/li&gt;&#10;&#9;&lt;li&gt;Introducing OpenFlow into existing networks&lt;/li&gt;&#10;&#9;&lt;li&gt;Cisco innovations across Enterprise and Service Provider portfolios&lt;/li&gt;&#10;&#9;&lt;li&gt;Best practices and recommendations for customers evaluating OpenFlow enabled networks&lt;/li&gt;&#10;&#9;&lt;li&gt;Live Q&amp;amp;A&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;Registration for February 14th (WebEx): &lt;a href="http://tools.cisco.com/gems/cust/customerSite.do?METHOD=L&amp;LANGUAGE_ID=E&amp;SEMINAR_CODE=S17515&amp;PRIORITY_CODE=000105112" target="_blank" rel="noopener noreferrer"&gt;Cisco ONE Webcast Series: An Introduction to OpenFlow&lt;/a&gt;&lt;/p&gt;</description></item><item><title>More Details About The Cisco ONE Controller Announced</title><link>https://networkstatic.net/more-details-about-the-cisco-one-controller-announced/</link><pubDate>Tue, 05 Feb 2013 00:29:30 +0000</pubDate><guid>https://networkstatic.net/more-details-about-the-cisco-one-controller-announced/</guid><description>&lt;h2&gt;More Details About The Cisco ONE Controller Announced&lt;/h2&gt;&#10;Cisco has begun further unveiling more details about the Cisco ONE controller, currently in early beta. The announcement, specifies new SDN applications and hardware support for a select few existing products and new ones like the Catalyst 3850. Also recently announced, is the new &lt;a href="http://www.networkcomputing.com/data-networking-management/cisco-nexus-6000-first-impressions/240147690" target="_blank"&gt;Nexus 6000&lt;/a&gt; switching product, along with a NAM module for the Nexus 7000. The Nexus 6000 is 96-ports of 40Gb low latency data center switch. Lastly, the Nexus 1000v support for Hyper-V integration into Microsoft System Center VM Manager and VXLan gateway support, both calculated moves in high stakes, data center virtualization chess. The big announcement is the software and will be for some time to come. With the Open Networking Summit coming up in April, it isn't far fetched to expect the Java open source controller from the "&lt;a href="https://networkstatic.net/more-vendors-define-their-sdn-strategy/" target="_blank"&gt;Daylight&lt;/a&gt;" multi-vendor consortium to be announced relatively soon.&#10;&lt;h2 class="legacy-heading"&gt;Key Cisco ONE Controller Announcements&lt;/h2&gt;&#10;&lt;ul&gt;&#10;&#9;&lt;li&gt;A new Cisco ONE Software Controller supports a highly available, scalable and extensible architecture; the industry’s first multiprotocol interfaces with One Platform Kit (onePK) and OpenFlow; consistent management, troubleshooting and security features; and built-in applications that include network slicing functionality for enabling logical partitioning of network resources. In addition, the ONE Controller will interact with Cisco networking applications such as Custom Forwarding and Network Tapping.&lt;/li&gt;&#10;&#9;&lt;li&gt;Expanded platform support for Cisco onePK developer environment with Nexus 3000, Nexus 7000 and ASR 9000.&lt;/li&gt;&#10;&#9;&lt;li&gt;Solutions for overlay networks including Nexus 1000V support for VXLAN Gateway; Nexus 1000V support for Microsoft Hyper-V and integration with Microsoft System Center VM Manager; virtual Network Analysis Module (vNAM) for network analysis and monitoring of virtualized and oud geoud workloads&lt;/li&gt;&#10;&#9;&lt;li&gt;Expanded platform support for OpenFlow with Nexus 3000, Nexus 7000, ASR 9000 and Catalyst 6500.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h2&gt;The Cisco ONE and OpenFlow&lt;/h2&gt;&#10;&lt;p&gt;Cisco has publicly committed to supporting OpenFlow since its announcement of the onePK last year. In order to do flow based forwarding, it only makes sense for consumers to expect a common mechanism to interact with hardware. The value should be well up the stack, but to get a proper stack, software developers need a common set of primitives.&lt;/p&gt;</description></item><item><title>Installing Wireshark On Linux for OpenFlow Packet Captures</title><link>https://networkstatic.net/installing-wireshark-on-linux-for-openflow-packet-captures/</link><pubDate>Sun, 03 Feb 2013 03:35:05 +0000</pubDate><guid>https://networkstatic.net/installing-wireshark-on-linux-for-openflow-packet-captures/</guid><description>&lt;h2&gt;Installing Wireshark On Linux for OpenFlow Packet Captures&lt;/h2&gt;&#10;&lt;aside class="legacy-callout"&gt;Update March 16, 2014:&#10;Fedora 20 has native Wireshark OpenFlow support.&#10;e.g:&#10;yum install wireshark&#10; &lt;/aside&gt;&#10;&lt;aside class="legacy-callout"&gt;&#10;&lt;ul&gt;&#10;&#9;&lt;li&gt;&lt;strong&gt;Update:&lt;/strong&gt; the OpenFlow dissector appears natively included in the nightly Ubuntu dev builds and even better, native in &lt;a href="http://fedoraproject.org/get-fedora" target="_blank"&gt;Fedora 19&lt;/a&gt;:&lt;/li&gt;&#10;&lt;li&gt;### Fedora 19 Wireshark Installation ###&#10;1) sudo yum install wireshark&#10;2) Nothing! Its that easy w/ native OpenFlow support +1&#10;For an X session on Fedora over SSH perform the following.&#10;1) Install the following:&#10;sudo yum install xorg-x11-xauth&#10;sudo yum install xorg-x11-fonts-*&#10;sudo yum install xorg-x11-utils&#10;======================&#10;2) Enable the following in the sshd_config file:&#10;=============================&#10;Change X11Forwarding to yes and uncomment:&#10;X11Forwarding yes&#10;====== sshd_config ==========&#10;#AllowAgentForwarding yes&#10;#AllowTcpForwarding yes&#10;#GatewayPorts no&#10;#X11Forwarding no&#10;X11Forwarding yes &lt;=== change this&#10;#X11DisplayOffset 10&#10;#X11UseLocalhost yes&#10;#PrintMotd yes&#10;===============&#10;$ export (should contain)&#10;declare -x DISPLAY="localhost:10.0"&#10;=========================&#10;Now you can "ssh -X 192.168.1.100" to your host and run an X Wireshark session using "sudo wireshark".&lt;/li&gt;&#10;&lt;/ul&gt;&#10;### Mac Installation ###&#10;Wireshark 1.11.0-SVN-52202&#10;&lt;a href="http://www.wireshark.org/download/automated/" target="_blank"&gt;http://www.wireshark.org/download/automated/&lt;/a&gt;&#10;&lt;ul&gt;&#10;&#9;&lt;li&gt;For a Mac just install quartz and this build and run as su.&lt;/li&gt;&#10;&#9;&lt;li&gt;sudo /Applications/Wireshark.app/Contents/MacOS/Wireshark&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;em&gt;### Installing on Ubuntu using the PPA repo try the following ###&lt;/em&gt;&#10;&lt;ul&gt;&#10;&#9;&lt;li&gt; sudo apt-get install python-software-properties&lt;/li&gt;&#10;&#9;&lt;li&gt;sudo add-apt-repository ppa:mighost/ppa&lt;/li&gt;&#10;&lt;li&gt;sudo apt-get update&lt;/li&gt;&#10;&lt;li&gt;### The following was pulled from 1.12.0~201309171613-1ppa1~precise in a dpkg --list. You likely don't need to mess with repo preferences.###&lt;/li&gt;&#10;&lt;li&gt;sudo apt-get install wireshark-common libwireshark3 libwireshark-data libwireshark3 libwiretap3 &lt;/li&gt;&#10;&lt;li&gt;sudo wireshark&lt;/li&gt;&#10;&lt;li&gt;### To run remotely you can connect using X over ssh with 'ssh -XY &lt;ip-address&gt;&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;a href="http://ppa.launchpad.net/mighost/ppa/ubuntu/" target="_blank"&gt;Link to the PPA Repo&lt;/a&gt;&#10;&lt;/aside&gt;&#10;&lt;figure class="legacy-figure"&gt;&lt;img src="https://networkstatic.net/wp-content/uploads/2013/10/Wireshark-OpenFlow.jpeg" alt="OpenFlow from Package PPA"&gt;&lt;/figure&gt;&#10;&lt;p&gt;This tutorial is for those who are learning, troubleshooting and developing using the OpenFlow wire protocol. Packet captures are vital to troubleshooting issues that occur between the switch and OpenFlow controller. The instructions are for installing Wireshark from package or compiling and installing from source. It also walks through installing the OpenFlow v1.0 dissector plugin for Wireshark. Once the plugin is installed you will be able to view OpenFlow messaging in the Wireshark packet captures.&lt;/p&gt;</description></item><item><title>The SDN Impact on Net Neutrality</title><link>https://networkstatic.net/the-sdn-impact-on-net-neutrality/</link><pubDate>Mon, 28 Jan 2013 04:01:21 +0000</pubDate><guid>https://networkstatic.net/the-sdn-impact-on-net-neutrality/</guid><description>&lt;h2&gt;The SDN Impact on Net Neutrality&lt;/h2&gt;&#10;&lt;blockquote class="pullquote"&gt;The neutral communications medium is essential to our society. It is the basis of a fair competitive market economy. It is the basis of democracy, by which a community should decide what to do. It is the basis of science, by which humankind should decide what is true. Let us protect the neutrality of the net.&lt;footer&gt;Tim Berners-Lee&lt;/footer&gt;&lt;/blockquote&gt;&#10;Over the next 10 years the networking industry is going to transform much more than it has in the previous ten year. The catalyst as we know it today is called SDN. What SDN really means is, the time has come to bring networking into the same decade conceptually, as the rest of the computing world. Networking will move away from being a collection of loosely coupled monolithic devices, into a more layered and programmatic construct that will resemble the virtualization of the x86 market. With this new found flexibility will bring new ways of controlling the traffic that today essentially drops in the mailbox and is never seen again. I propose that &lt;a href="https://networkstatic.net/sdn-use-cases-for-service-providers/" target="_blank"&gt;network service providers (NSPs)&lt;/a&gt; and mobile network operators (MNOs) will be able to skirt around any net neutrality regulations by exploiting emerging technologies. With great power, comes great responsibility.The SDN impact on net neutrality may very well programmatically dismantle what is left of a unified Internet.&#10;&lt;h2&gt;What is Net Neutrality?&lt;/h2&gt;&#10;&lt;blockquote class="pullquote"&gt;Network neutrality is the principle that Internet users should be able to access any web content they choose and use any applications they choose, without restrictions or limitations imposed by their Internet service provider.&#10;For example, if you are shopping for a new appliance online you should be able to shop on any and all websites, not just the ones with whom your provider has a preferred business relationship. Or If you want to use your high-speed Internet connection to make phone calls, your provider should not be able to impede your ability to do so.&lt;/blockquote&gt;&#10;&lt;h2&gt;Pro Net-Neutrality Position&lt;/h2&gt;&#10;&lt;blockquote class="pullquote"&gt;&#10;&lt;strong&gt;Discrimination:&lt;/strong&gt; The Internet was designed as an open medium. The fundamental idea since the Internet's inception has been that every Web site, every feature and every service should be treated without discrimination. That's how bloggers can compete with CNN or USA Today for readers. That's how up-and-coming musicians can build underground audiences before they get their first top-40 single. That's why when you use a search engine, you see a list of the sites that are the closest match to your request -- not those that paid the most to reach you. Discrimination endangers our basic Internet freedoms.&#10;&lt;strong&gt;Double-dipping:&lt;/strong&gt; Traditionally, network owners have built a business model by charging consumers for Internet access. Now they want to charge you for access to the network, and then charge you again for the things you do while you're online. They may not charge you directly via pay-per-view Web sites. But they will charge all the service providers you use. These providers will then pass those costs along to you in the form of price hikes or new charges to view content.&#10;&lt;strong&gt;Stifling innovation:&lt;/strong&gt; Net Neutrality ensures that innovators can start small and dream big about being the next EBay or Google without facing insurmountable hurdles. Unless we preserve Net Neutrality, startups and entrepreneurs will be muscled out of the marketplace by big corporations that pay for a top spot on the Web. On a tiered Internet controlled by the phone and cable companies, only their own content and services -- or those offered by corporate partners that pony up enough "protection money" -- will enjoy life in the fast lane.&#10;&lt;footer&gt;&lt;a href="http://savetheinternet.com"&gt;-Net Neutrality 101&lt;/a&gt;&lt;/footer&gt;&lt;/blockquote&gt;&#10;&lt;h2&gt;Anti Net Neutrality Position&lt;/h2&gt;&#10;&lt;blockquote class="pullquote"&gt;&#10;-Those who oppose net neutrality argue that it is an absolutely futile exercise as none of the Internet service providers would go about sabotaging their rivals by blocking their content or degrading network performance. They also cite the example of other networks, which are functioning properly even with the major contributors being in charge of them.&#10;-Speaking against net neutrality, the Internet service providers justify the norm of charging more for heavy Internet usage, as this money helps them create better infrastructure, and indirectly contributes to the quality of service. They further add that the high fees are only meant for large companies who have a heavy usage, and these companies, they say, can definitely afford the fees.&#10;-Then again, the legislation has to be defined clearly. Loose ends will be used by people with vested interests for their own benefits. As for the government control of the Internet, those against this type of Internet regulation say that it will depend on the government's attitude. When in wrong hands, net neutrality can be used as a tool of Internet censorship or invasion of privacy.&#10;&lt;footer&gt;&lt;a href="http://www.buzzle.com/articles/net-neutrality-pros-and-cons.html"&gt;Net Neutrality Pros and Cons&lt;/a&gt;&lt;/footer&gt;&lt;/blockquote&gt;&#10;&lt;h2&gt;How does Application Aware SDN Networks&lt;/h2&gt;&#10;The two-lane model is in full effect today. Carriers run managed services for enterprise customers, mobile back hauls for other carriers or their own triple play service and application offerings. There are also expensive traffic management, application aware black boxes that classify and shape or limit consumer traffic such as peer to peer rate-limiting and blocking.&#10;&lt;p&gt;Emerging traffic engineering techniques such path computation element (PCE) takes a set of resources like price, QOS and strategic business goals and strategies and applies to to MPLS and Generalized Multi-Protocol Label Switching (GMPLS) networks. This is the beginning of programmatic interfaces to create application aware Label Switch Paths(LSP) in provider networks. A core change to the packet switched networks of today, is decoupling route computation from the forwarding planes of monolithic networking elements we have today.&lt;/p&gt;</description></item><item><title>OpenStack Multi-Node DevStack Nova Network Tutorial</title><link>https://networkstatic.net/openstack-multi-node-devstack-nova-network-tutorial/</link><pubDate>Tue, 22 Jan 2013 00:41:19 +0000</pubDate><guid>https://networkstatic.net/openstack-multi-node-devstack-nova-network-tutorial/</guid><description>&lt;h2&gt;OpenStack Multi-Node DevStack Nova Network Tutorial&lt;/h2&gt;&#10;&lt;aside class="legacy-callout"&gt;&#10;&lt;ul&gt;&#10;&#9;&lt;li&gt;&lt;a href="https://networkstatic.net/installing-openstack-grizzly-with-devstack/" target="_blank"&gt;Installing OpenStack Grizzly with DevStack&lt;/a&gt; : Here is an updated Grizzly DevStack tutorial since Folsom is coming to an end.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;/aside&gt;&#10;DevStack is a scripted OpenStack installer  maintained for developers to prototype and debug. It is also handy for operators to proof concepts and test new services and configurations. This is a good starter for folks new to OpenStack to help understand how to install and operate OpenStack. Some folks have been asking about multi-node DevStack deployment using nova network, so I thought this tutorial might help.&#10;&lt;p&gt;Another difference in this tutorial. is using nova-network instead of the Quantum network plugin. The Quantum plugin is very flexible and offers much richer networking feature, by implementing vSwitches, rather then Linux bridging. With flexibility, comes complexity.The reality if most people looking to do test deployments, proof of concepts or richer KVM/XEN hypervisor management do not really need the added complexity. Nova-network is slated for depreciation at some point, but I am not sure that is the best plan of action for typical until the installation becomes easier for folks in my humble opinion. Most enterprises don&amp;rsquo;t have &amp;ldquo;DevOps&amp;rdquo; programmers, and I think OpenStack brings some good value and expenditure savings to the enterprise. The complexity of the advanced networking may turn some folks off to the project in smaller organizations. Then again smaller organizations aren&amp;rsquo;t the ones running OpenStack and that may be attractive to vendors looking to find revenue from service offerings. Anywho, thats my two cents, let&amp;rsquo;s get on to the tutorial.&lt;/p&gt;</description></item><item><title>OpenFlow: SDN Hybrid Deployment Strategies</title><link>https://networkstatic.net/openflow-sdn-hybrid-deployment-strategies/</link><pubDate>Mon, 21 Jan 2013 07:22:27 +0000</pubDate><guid>https://networkstatic.net/openflow-sdn-hybrid-deployment-strategies/</guid><description>&lt;h2&gt;OpenFlow: SDN Hybrid Deployment Strategies&lt;/h2&gt;&#10;This series of posts, has been focused on reviewing some practical OpenFlow SDN deployment strategies. Early SDN, will be hybrid networks and early niche applications to begin understanding how to integrate pockets of SDN, mitigate risks and most importantly understand the technology to properly scale solutions. If you try and put 5,000,000 access-lists into a kit that can only do 2,000 rules, does that mean access-lists do not scale? Or does that mean bad designs do not scale? Risk of network instability and pressure of constant availability, has networking trapped in a less than ideal situation. Absorption of the oncoming onslaught of &lt;a href="http://www.cisco.com/en/US/solutions/collateral/ns341/ns525/ns537/ns705/ns827/white_paper_c11-481360_ns827_Networking_Solutions_White_Paper.html" target="_blank"&gt;growth on the horizon&lt;/a&gt; along with uptake in cloud adoption will be hit and miss at best.&#10;&lt;h2&gt;3 Key OpenFlow Hurdles&lt;/h2&gt;&#10;&lt;ol class="legacy-numbers"&gt;&#10;&lt;ol&gt;&#10;&#9;&lt;li&gt;&lt;strong&gt;Performance - Pre-Populating Flows:&lt;/strong&gt;Pre-populating the flow tables at boot or at policy creation in a proactive manner instead of reacting with packet-in events. The only thing centralized at that point is your management engine, in order to define and push policy and topology awareness to the holistic network.  More on that topic in &lt;a href="https://networkstatic.net/openflow-proactive-vs-reactive-flows/" target="_blank"&gt;OpenFlow: Proactive vs. Reactive&lt;/a&gt;.&lt;/li&gt;&#10;&#9;&lt;li&gt;&lt;strong&gt;Scale - Flow Rule Allocations:&lt;/strong&gt;Early OpenFlow enabled hardware is limited in the amount of wildcard flow rules to 750-3,000 depending on vendor. Some vendors such as NEC, have external TCAM that supports tens of thousands of rules. Early designs need to take that into account and be judicious if the amount of coarse vs fine flows chosen to pre-populate into flow tables. Peel niche applications or selective traffic with granular flows and drain the rest of the traffic with broad flows. This will make more room for interesting traffic. More on this topic in &lt;a href="https://networkstatic.net/openflow-coarse-vs-fine-flows/" target="_blank"&gt;OpenFlow: Course vs. Fine Flows&lt;/a&gt;.&lt;/li&gt;&#10;&#9;&lt;li&gt;&lt;strong&gt;Risk - Hybrid Architectures:&lt;/strong&gt; A ships in the night strategy is a pretty straightforward approach to new networking architectures.  Hybrid features from the OpenFlow agent on the switch are critical to maintain logical path and process isolation between legacy networks and OpenFlow enabled Vlans, bridges and interfaces. Hybrid path isolation is well understood and documented. That should may be enough risk reduction for many to introduce early use cases of SDN applications or pockets of exploratory test/dev. The rest of this article is focused on the hybrid component.&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;/ol&gt;&#10;&lt;h2&gt;Mitigate Risk and Innovate&lt;/h2&gt;&#10;Hybrid deployments are intrinsic to reducing risk. Hybrid networks are not a new concept. Hybrid techniques should be well understood after consolidating many traditionally parallel network services, into a converged architecture. We slowly introduced services like VOIP and wireless along with deploying virtualization overlays with MPLS. New SDN deployments wether tunneled overlays or logical isolations, will be the important first steps  of innovative progress.&#10;&lt;h2&gt;Hybrid SDN Networks: Keys to Unlocking Progress&lt;/h2&gt;&#10;The most important thing to begin thinking about SDN enabled networks, is helping colleagues, leadership and community understand that almost all risk can be mitigated by using engineering hybrid native forwarding and SDN enabled forwarding networks. The risk lies in vendor firmware on the SDN enabled switch. Since most of the agents are ported Open vSwitch that should offer some stability. All early OpenFlow enabled gear is sharing forwarding hardware between native and SDN pipelines so any planning needs to incorporate existing configurations, particularly QOS and ACLs.&#10;&lt;h2&gt;8 Hybrid Strategy Considerations&lt;/h2&gt;&#10;&lt;figure class="legacy-figure"&gt;&lt;img src="https://networkstatic.net/wp-content/uploads/2013/01/Hybrid-OpenFlow-SDN.png" alt="Openflow SDN Hybrid"&gt;&lt;/figure&gt;&#10;&lt;p&gt;Figure 1. An example of a simple topology from a post last year on &lt;a href="https://networkstatic.net/hybrid-sdn-deployments/#!prettyPhoto" target="_blank"&gt;hybrid SDN&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>OpenFlow: Coarse vs. Fine Flows</title><link>https://networkstatic.net/openflow-coarse-vs-fine-flows/</link><pubDate>Sun, 20 Jan 2013 06:09:03 +0000</pubDate><guid>https://networkstatic.net/openflow-coarse-vs-fine-flows/</guid><description>&lt;h2&gt;OpenFlow: Coarse vs. Fine Flows&lt;/h2&gt;&#10;OpenFlow: Coarse vs. Fine Flows - This series of posts, is to shed light on some illogicalities surrounding the SDN discussion. I will highlight what I propose, will achieve performance and scale when implementing flow based forwarding designs. Soon these debates, will no longer be conceptual or limited deployments in only the &lt;a href="http://www.extremetech.com/internet/140459-networking-is-getting-better-and-thats-partly-thanks-to-google" target="_blank"&gt;hyper-scale&lt;/a&gt; networks, as more of us begin real-life implementations. The last post &lt;a href="https://networkstatic.net/openflow-proactive-vs-reactive-flows/" target="_blank"&gt;OpenFlow: Proactive vs Reactive Flows&lt;/a&gt;, was an attempt to point out some fallacies that OpenFlow performance is weak compared to today's flood, learn, route and filtering methods. After reviewing some  facts that pre-populating flows proactively via OpenFlow into a switches flow table, eliminates the need to punt the first packet of each new flow into a controller. Packet forwarding now takes place at wire speed with L2-L4 policy implemented. The second misnomer, is flow based forwarding does not scale. Bad designs are what do not scale.  In this article, we will examine the second factor in finding performance and scale in initial OpenFlow SDN: coarse vs. fine flow scaling.&#10;&lt;h2&gt;OpenFlow Matching&lt;/h2&gt;&#10;OpenFlow allows a off-board x86 server create a TCP socket with the switch in order to exploit TCAM memory, creating flow tables rules for line rate forwarding. Just as today's routers and switches have limited numbers of access-list and QOS policies, the same applies to the number of flow table lines are available. This is especially true with the current OpenFlow enabled hardware since it is being retro fitted to exploit the TCAM that is traditionally used for QOS and access-lists.&#10;&lt;p&gt;The matching of fields in in OpenFlow can either be an explicit match or a wildcard match. A wildcard match means the  switch does not care what the value is in the specified field. An explicit match is a binary match, it matches or doesn&amp;rsquo;t.&lt;/p&gt;</description></item><item><title>OpenFlow: Proactive vs Reactive Flows</title><link>https://networkstatic.net/openflow-proactive-vs-reactive-flows/</link><pubDate>Tue, 15 Jan 2013 06:50:19 +0000</pubDate><guid>https://networkstatic.net/openflow-proactive-vs-reactive-flows/</guid><description>&lt;h2&gt;OpenFlow: Proactive vs Reactive&lt;/h2&gt;&#10;As more people begin entering the Software Defined Networking conversation, there is still only one wire protocol that has a reasonably good chance at becoming the de-facto open SDN southbound messaging standard, OpenFlow. There is quite a bit of debate around whether or not OpenFlow can scale. Most claims that OpenFlow does not scale are probably grounded in misconception. That is not to say we do not have a long way to go, but spending the next 5-10 years debating a hardware abstraction layer would be counterproductive in the face of unmanageable networks, with exponential growth occurring annually. As forwarding abstractions in hardware continue to become more flexible, the scale debate should not be whether OpenFlow can scale as a messaging protocol, but be focused on when and if to use reactive flow based rules as opposed to proactive instantiation.&#10;&lt;h2&gt;Recap of Why OpenFlow is Important&lt;/h2&gt;&#10;Today we have switches that operate at L2, routers that operate at L3 and firewalls that operate at L4. Some of those functions are blended together in purpose-built hardware such L3 switches. An access-list is a common function that uses &lt;a href="http://etherealmind.com/tcam-detail-review/" target="_blank"&gt;TCAM&lt;/a&gt; (ternary content addressable memory) to have the flexibility to match on various layers of a packets L2-L4 headers. That TCAM memory has the ability to match (0), not match(1) (the binary is counterintuitive there) or not care (wildcard). Each field or tuple is searched in parallel all in one clock cycle. So, very quickly and at "line rate" in hardware.&#10;&lt;figure class="legacy-figure"&gt;&lt;img src="https://networkstatic.net/wp-content/uploads/2013/01/tcam.png" alt="OpenFlow TCAM"&gt;&lt;/figure&gt;&#10;&lt;strong&gt;&lt;em&gt;Figure 1&lt;/em&gt;&lt;/strong&gt;. TCAM matching&#10;&lt;p&gt;The simplicity of OpenFlow is it was merely a mechanism to exploit TCAM tables in existing vendor switches in order instantiate whatever flows a programmer wants to push. Now with OpenFlow, one can tell a switch to match on any field and apply an action. For network operators and engineers this is policy based routing, on steroids. We can decouple logic and push a set of flow policy from off board the switch, through a TCP socket, using a structured messaging protocol to describe the policy and flow rules to put in TCAM.&lt;/p&gt;</description></item><item><title>SDN OpenFlow Policy Abstractions</title><link>https://networkstatic.net/sdn-openflow-policy-abstractions/</link><pubDate>Wed, 09 Jan 2013 07:21:38 +0000</pubDate><guid>https://networkstatic.net/sdn-openflow-policy-abstractions/</guid><description>&lt;h2&gt;SDN OpenFlow Policy Abstractions : Frenetic Netcore Procera&lt;/h2&gt;&#10;SDN OpenFlow Policy Abstractions : Abstraction layers are a fundamental principle in computer science. It is a core pillar in creating efficiencies through layered, modular scale. Proper abstraction layers are also where the networking train came off the tracks. Network operators program network devices using proprietary APIs one device at a time. In today's networks, when we push policy to network elements, the control loop is anything but tight. Basic worthwhile operational tools never made it to market, in large part due to a lack of layered abstractions.&#10;&lt;p&gt;Networking is made up of vertically integrated components today that resemble the monolithic mainframes of the 80&amp;rsquo;s. As we continue the debate around SDN solutions and agnostic forwarding abstractions such as OpenFlow, are merely building blocks that are not magic bullets. What OpenFlow does offer, is a low level network instruction set agnostic to the vendor and likely flexible enough to serve as a base abstraction as it evolves. With a consistent set of primitives we can write controllers and applications that can control forwarding and/or extract valuable information about the state of your network. Operators nailing up static flows for traffic forwarding would be as unmanageable as throwing out your &lt;a href="http://mellowd.co.uk/ccie/?p=1929" target="_blank"&gt;IGPs&lt;/a&gt; and hand crafting not just L3 forwarding but L1-L4 forwarding. State distribution will stay decentralized depending on scale, just likely not fully distributed because it just doesn&amp;rsquo;t make much sense any longer inside an administrative domain, we made it through the cold war.&lt;/p&gt;</description></item><item><title>Plexxi Capacity Planning Done Right</title><link>https://networkstatic.net/plexxi-capacity-planning-done-right/</link><pubDate>Sun, 06 Jan 2013 02:28:25 +0000</pubDate><guid>https://networkstatic.net/plexxi-capacity-planning-done-right/</guid><description>&lt;h2&gt;Plexxi Capacity Planning Done Right&lt;/h2&gt;&#10;I try and get a daily dose of at least a few minutes of a PacketPushers podcast to keep up with latest networking products and trends. In &lt;a href="http://packetpushers.net/show-126-plexxi-affinity-networking-with-marten-terpstra-sponsored/" target="_blank"&gt;Show 126 Plexxi &amp;amp; Affinity Networking With Marten Terpstra&lt;/a&gt; Greg and Ethan meet with Marten Terpstra of Plexxi and dug into the new GA product offering from Plexxi.&#10;&lt;h2&gt;Plexxi Affinity Networking&lt;/h2&gt;&#10;Plexxi defines "affinitized traffic" as traffic that matches a proactively installed rule. That rule forwards the data plane traffic based on a &lt;a href="http://www.sdncentral.com/products-technologies/sdn-openflow-tcam-need-to-know/2012/07/" target="_blank"&gt;TCAM&lt;/a&gt; rule rather than a destination mac address in a MAC address to port Key-&amp;gt;Value mapping. This is different from OpenFlow in how a controller interacts with the switch. In OpenFlow, the first packet of the flow comes into the switch and a packet-in event is created. That event involves the switch encapsulating the first packet of the flows fields/tuples and punts it to the controller. Plexxi focuses on configuration management by pre-populating forwarding/flow tables.&#10;&lt;h2&gt;Broadcom ASICs in the Switch x86 in the controller&lt;/h2&gt;&#10;Plexxi uses Broadcom ASICs, presumably the Trident+ or 2 chipset. Flow table scale is still a problem in today's &lt;a href="http://etherealmind.com/merchant-silicon-vendor-software-rise-lost-opportunity/" target="_blank"&gt;merchant silicon&lt;/a&gt;. Off the shelf top of rack geared silicon only supports around ~3,000-6,000 wildcard flows. Typical BCAM (binary content addressable memory) is used for example in mac address tables. An example of BCAM logic is a key with a value such as a mac address in a key-&amp;gt;value pair. That key would either match or not match a value (binary). If a frame comes in destined for a mac address it is either in the tables or not. If it is not the switch floods all ports for that destination until it is learned. Ternary CAM can return either a match, a doesn't match or something often referred to as a "don't care bit". The don't care bit is denoted with a wildcard.&#10;&lt;h2&gt;Example of TCAM Flow table Wildcard Matching in SDN &lt;/h2&gt;&#10;If I have a simple 4 tuple rule consisting of src_mac, dest_mac, src_ip and dest_ip a flow table could match:&#10;&lt;ol class="legacy-numbers"&gt;&#10;&lt;ol&gt;&#10;&#9;&lt;li&gt;src_mac: *&lt;/li&gt;&#10;&#9;&lt;li&gt;dest_mac: 00:00:C0:FF:FF:EE&lt;/li&gt;&#10;&#9;&lt;li&gt;src_ip: *&lt;/li&gt;&#10;&#9;&lt;li&gt;dest_ip: 172.16.1.20&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;/ol&gt;&#10;In that example src_mac and src_ip are wild carded meaning ignore those values and the two source addresses have explicit values. That rule would take up one flow entry in a flow tables. 5,000 flow tables begin draining very quickly considering a single host can have thousands of flows at any given time. presumably, just as in OpenFlow programming and design for scale, coarse flow rules are being installed to large swaths of traffic rather than large amounts of individual flows. This is very similar to access lists in traditional networks.&#10;&lt;h2&gt;Lambda Driven Fabric&lt;/h2&gt;&#10;The new twist that Plexxi offers is built in &lt;a href="http://en.wikipedia.org/wiki/Wavelength-division_multiplexing" target="_blank"&gt;Wave Division Multiplexing&lt;/a&gt; (WDM) Coarse WDM specifically. A simple way of thinking of WDM is passing light through a prism, each color that breaks out is a color or wave with an associated frequency that is measure in nanometers (NM) in space between waves. In traditional chassis along with stackable (virtual and physical) switches control channels are setup for management and FIB or flow table downloads. That is almost always a proprietary encapsulating or messaging. I am assuming Plexxi sets up a lambda or two (if not in a physical ring topology) for controller to switch communications.&#10;&lt;figure class="legacy-figure"&gt;&lt;img src="https://networkstatic.net/wp-content/uploads/2013/01/plexxi-sdn.jpg" alt="Pexxi Network Controller"&gt;&lt;/figure&gt;&#10;&lt;p&gt;&lt;em&gt;Figure 1. &lt;/em&gt;Plexxi Controller Architecture.&lt;/p&gt;</description></item><item><title>Best Cat Videos of 2012</title><link>https://networkstatic.net/best-cat-videos-of-2012/</link><pubDate>Mon, 31 Dec 2012 06:07:23 +0000</pubDate><guid>https://networkstatic.net/best-cat-videos-of-2012/</guid><description>&lt;h2 class="legacy-heading"&gt;Best Cat Videos of 2012&lt;/h2&gt;&#10;&lt;p&gt;&lt;span class="drop-cap"&gt;I&lt;/span&gt;&#10;took a rare, but important intermission from technology related posts to write about the one and only thing cooler than computing, programming and networking, that is videos of cute cats and kittens! These are the best cat videos of 2012 that I remember watching this year. Pets love us unconditionally that can only come from pure innocence. As they depend on us we often depend on them to take a little time out of life to appreciate life.&lt;/p&gt;</description></item><item><title>Google Data Center Pictures: Year in Review</title><link>https://networkstatic.net/google-data-center-pictures-year-in-review/</link><pubDate>Mon, 24 Dec 2012 04:30:35 +0000</pubDate><guid>https://networkstatic.net/google-data-center-pictures-year-in-review/</guid><description>&lt;h2&gt;Google Data Center Pictures: Year in Review&lt;/h2&gt;&#10;Google Data Center Pictures: Year in Review :In 2012 Google opened the doors up to some of it's data centers in the typical colorful fashion we expect from Google. Hyper-scale content and cloud providers are ultra secretive about their trade secrets. Facebook's &lt;a href="http://opencompute.org" target="_blank"&gt;Opencompute&lt;/a&gt; project is probably the most notable transparent architectures with regard to how they build their compute and storage nodes. &#10;&lt;h2&gt;There is scale and Google scale&lt;/h2&gt;&#10;&lt;blockquote class="pullquote"&gt;“You benefit from the efficiency of Google data centers and our decade of running them”..."We’ve worked very hard to get the cost of computing down for a decade, and we’re passing the savings on to you."&lt;footer&gt;Urs Hoezle Google Senior VP&lt;/footer&gt;&lt;/blockquote&gt;The sheer scale of nearly 1 million servers distributed globally is pretty awe inspiring. It helps to remember that any good architecture scales if done in a modular fashion. The distributed systems at Google are one of, if not the best in the business. When people leave Google, a year or two later the reverse-engineered product emerges. Google has been one of the handful of consumers that through purchasing volume and R&amp;D have turned the industry into a consumer driven market rather than the past two decades of manufacturers dictating the architectures and products.&#10;&lt;h2&gt;Why is Google Opening the Data Center Doors?&lt;/h2&gt;&#10;The likely reason for 2012 being the Google data center PR blitz is to make personal connections with potential Google Compute Engine (GCE). GCE is Google's cloud platform that is striving to be the one to start chipping at Amazon's coveted &lt;a href="https://networkstatic.net/does-the-cost-of-cloud-iaas-intersect-the-local-vm/" target="_blank"&gt;AWS&lt;/a&gt; market share. The cloud computing market share is ripe disruption with AWS operating with next to no competition since its entrance into the public cloud. Amazon's agility to reduce CapEx and squeeze efficiencies will be important in remaining the incumbent.&#10;&lt;p&gt;The final lesson from Google is, put loud colors on everything in your data center to make it look technically advanced. It even works with dirty old backup tapes.&lt;/p&gt;</description></item><item><title>Floodlight OpenFlow Controller: Using the Static Flow Entry Pusher</title><link>https://networkstatic.net/floodlight-openflow-controller-using-the-static-flow-entry-pusher/</link><pubDate>Mon, 10 Dec 2012 04:22:04 +0000</pubDate><guid>https://networkstatic.net/floodlight-openflow-controller-using-the-static-flow-entry-pusher/</guid><description>&lt;h2&gt;Floodlight OpenFlow Controller: Using the Static Flow Entry Pusher&lt;/h2&gt;&#10;Floodlight OpenFlow Controller: Using the Static Flow Entry Pusher: The first post in this tutorial can be found at &lt;a href="https://networkstatic.net/tutorial-to-build-a-floodlight-sdn-openflow-controller-module/" target="_blank"&gt;Tutorial to Build a FloodLight SDN OpenFlow Controller &lt;/a&gt;.&#10;&lt;hr /&gt;&#10;&lt;p&gt;For those looking to do things with early SDN / OpenFlow controllers this post may be of some use to kickstart your efforts. I am posting a Java class below that Cory Fowler and I put together. There are lots of good guides out there but what exactly I was looking for was unavaialble at the time.&lt;/p&gt;</description></item><item><title>Cacti Network Management Installation Tutorial</title><link>https://networkstatic.net/cacti-network-management-installation-tutorial/</link><pubDate>Mon, 03 Dec 2012 05:29:07 +0000</pubDate><guid>https://networkstatic.net/cacti-network-management-installation-tutorial/</guid><description>&lt;h2&gt;Cacti Network Management Installation Tutorial&lt;/h2&gt;&#10;Network management has to be, one of the most neglected pieces of networking. I am sure we all have our hypotheses as to why but that is for another day. This tutorial is for installing the latest stable release 0.8.8a, released on 04/29/12. I needed to proof Cacti and get a scripted installation together. Cacti has been around a long time and has a nice ecosystem of plugins. Like any open source there is much more code then documentation. That said, the &lt;a href="http://forums.cacti.net/viewforum.php?f=25" target="_blank"&gt;Cacti community forum&lt;/a&gt; is fantastic and full of community contributions. I tested the installation on both current CentOS and RHEL. It could be easily ported to Ubuntu s/yum/apt-get/g.&#10;&lt;h2 class="legacy-heading"&gt;Cacti Network Management Plugins&lt;/h2&gt;&#10;&lt;p&gt;Here are some supported and user built &lt;a href="http://docs.cacti.net/plugins" target="_blank"&gt;plugins&lt;/a&gt; part of this install.&lt;/p&gt;</description></item><item><title>Programming the NSP: Vendors on SDN for SP Operators</title><link>https://networkstatic.net/programming-the-nsp-vendors-on-sdn-for-sp-operators/</link><pubDate>Sun, 02 Dec 2012 19:00:26 +0000</pubDate><guid>https://networkstatic.net/programming-the-nsp-vendors-on-sdn-for-sp-operators/</guid><description>&lt;h2&gt;Programming the NSP: Vendors on SDN for SP Operators&lt;/h2&gt;&#10;&lt;span class="drop-cap"&gt;L&lt;/span&gt;&#10;ast week we looked at what the Network Service Provider Customers are looking for from vendors in the  &lt;a href="https://networkstatic.net/sdn-use-cases-for-service-providers/" target="_blank"&gt;&lt;em&gt;Network Virtualization Function (NFV)&lt;/em&gt;&lt;/a&gt;. This week, let's take a look at what the vendors were proposing in October at the SDN &amp;amp; OpenFlow World Congress. Some of the vendor and ONF white papers were posted recently which is nice to see. The keynote was streamed but everything else was members only. These new groups need to generate revenue to maintain bodies and hold conferences and their businesses. That said, it generates more  long tail interest about the events when the lecture recordings are posted for viewing after the fact, like the &lt;a href="http://www.youtube.com/user/OpenNetSummit" target="_blank"&gt;Open Networking Summit&lt;/a&gt; and &lt;a href="http://nerdtwilight.wordpress.com/2012/11/17/for-your-sdn-reading-pleasure/" target="_blank"&gt;SIGCOMM&lt;/a&gt; conferences.&#10;&lt;h2&gt;NSP Optical and Ethernet Market Share&lt;/h2&gt;&#10;Below is the NSP global market share for optical transport along with the core and edge router market as od 3Q2012.&#10;&lt;p style="text-align: center;"&gt;&lt;a href="https://networkstatic.net/wp-content/uploads/2012/12/NSP-Network-Marketshare1.jpg"&gt;&lt;img class="aligncenter wp-image-4933" title="NSP-Network-Marketshare-2012Q3" src="https://networkstatic.net/wp-content/uploads/2012/12/NSP-Network-Marketshare1.jpg" alt="NSP-Network-Marketshare-2012Q3" width="542" height="246" /&gt;&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Open vSwitch Red Hat Installation</title><link>https://networkstatic.net/open-vswitch-red-hat-installation/</link><pubDate>Sat, 01 Dec 2012 06:57:57 +0000</pubDate><guid>https://networkstatic.net/open-vswitch-red-hat-installation/</guid><description>&lt;h2&gt;Open vSwitch Red Hat Installation&lt;/h2&gt;&#10;This is an updated tutorial for an Open vSwitch Red Hat Installation. It is a little tricky at the moment from a kernel-devel bug that has a broken symbolic link. I did a screencast also in case anyone gets stuck. Just let me know if I mistyped anything and I will update it.&#10;&lt;h2&gt;Install Open vSwitch Pre-Reqs for Red Hat&lt;/h2&gt;&#10;&lt;hr /&gt;&#10;&lt;p&gt;The OS details are here.&lt;/p&gt;</description></item><item><title>Cisco acquisition of Cariden</title><link>https://networkstatic.net/cisco-acquisition-of-cariden/</link><pubDate>Fri, 30 Nov 2012 03:42:34 +0000</pubDate><guid>https://networkstatic.net/cisco-acquisition-of-cariden/</guid><description>&lt;h2&gt;Cisco acquisition of Cariden&lt;/h2&gt;&#10;&lt;span class="drop-cap"&gt;C&lt;/span&gt;&#10;isco announced today the intended acquisition of Cariden, a network management software company. Cisco will purchase the self-funded Cariden for $141 million. This deal is on the heels of two other Cisco acquisitions. The purchase of the WiFi company Meraki for $1.2 billion and the cloud software company Cloupia for $125 million. Cariden has built it's business from developing network management software targeting service providers. Cariden listed it's business partners as Alcatel-Lucent, Big Switch Networks, Cisco and Juniper.&#10;&lt;p&gt;Cariden marketing focuses on capacity planning and business intelligence. The Cariden website claims to deliver the &amp;ldquo;global view&amp;rdquo; of networks. In August Cariden announced its &lt;a href="http://www.cariden.com/about/news/details/?id=170" target="_blank"&gt;blueprint&lt;/a&gt; for Software Defined Networking (SDN). It targeted the keywords for the service provider SDN market like, computational path elements (CPE), controller interfaces and big data components like predictive analytics.&lt;/p&gt;</description></item><item><title>Bad Idea List: ITU UN Plan To Regulate The Internet</title><link>https://networkstatic.net/bad-idea-list-itu-un-plan-to-regulate-the-internet/</link><pubDate>Wed, 28 Nov 2012 04:34:05 +0000</pubDate><guid>https://networkstatic.net/bad-idea-list-itu-un-plan-to-regulate-the-internet/</guid><description>&lt;h2&gt;Bad Idea List: ITU UN Plan To Regulate The Internet&lt;/h2&gt;&#10; The International Telecommunication Union Standardization (ITU-T) is no longer only interested in telecommunications standards, now they what to regulate the whole Internet. ITU-T is a part of the United Nation that had a leaked document over the summer that outlines their plans of regulating, content filtering and even taxing companies for the use of the Internet. The ITU is a closed body attempting to regulate an open Internet (in some parts of the world), with open communities developing it. Closed regulatory and standards bodies have no place in technology, much less Internet regulations.&#10;&lt;p&gt;The UN, with histories of &lt;a href="http://www.thetrumpet.com/article/73.0.70.0/world/united-nations/sex-scandal-uncovered" target="_blank"&gt;sex-scandals&lt;/a&gt;, &lt;a href="http://www.economist.com/node/10853611" target="_blank"&gt;oil-for-food scandal&lt;/a&gt; and an all around &lt;a href="http://en.wikipedia.org/wiki/Criticism_of_the_United_Nations" target="_blank"&gt;inability&lt;/a&gt; to prevent war and &lt;a href="http://www.nytimes.com/2009/03/29/books/review/LeBor-t.html" target="_blank"&gt;genocide&lt;/a&gt; now wants to regulate the Internet? The list of failures is long and revealing. &lt;a href="http://en.wikipedia.org/wiki/Criticism_of_the_United_Nations" target="_blank"&gt;Wikipedia: Criticism of the United Nations&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Software Defined Network (SDN) -Looking Toward 2013 - Part 2</title><link>https://networkstatic.net/software-defined-network-sdn-looking-toward-2013-part-2/</link><pubDate>Tue, 27 Nov 2012 03:19:50 +0000</pubDate><guid>https://networkstatic.net/software-defined-network-sdn-looking-toward-2013-part-2/</guid><description>&lt;h2&gt;Software Defined Network (SDN) -Looking Toward 2013 - Part 2&lt;/h2&gt;&#10;In the second part of the two parter I am looking at some of the softer sides of the networking futures and what I expect to see in the coming year. Click &lt;a href="https://networkstatic.net/software-defined-network-sdn-looking-toward-2013-part-1/" target="_blank"&gt;here&lt;/a&gt; for Part I.&#10;&lt;h2&gt;SDN for HyperScale and Everyone Else&lt;/h2&gt;&#10;Today Google back-hauls their inter-data center traffic using its implementation of OpenFlow called G-Scale. While a fairly fixed set of flow patterns they have so far been the largest example of  an SDN extracted control plane deployment to date.&#10;&lt;blockquote class="pullquote"&gt;OpenFlow is the most significant change to the networking game since he first came to Google more than a decade ago. -Urs Hölzle Senior VP of technical infrastructure and Google Fellow &lt;a href="http://www.wired.com/wiredenterprise/2012/11/big-switch/" target="_blank"&gt;Wired&lt;/a&gt; 13 Nov 2012.&lt;/blockquote&gt;&#10;&lt;p&gt;Others, such as large carriers are very focused on CapEx reduction. Read how the Service Providers have approached SDN in a white paper from IETF85 summarized &lt;a href="https://networkstatic.net/sdn-use-cases-for-service-providers/" target="_blank"&gt;here&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Software Defined Network (SDN) -Looking Toward 2013 - Part 1</title><link>https://networkstatic.net/software-defined-network-sdn-looking-toward-2013-part-1/</link><pubDate>Tue, 27 Nov 2012 03:10:37 +0000</pubDate><guid>https://networkstatic.net/software-defined-network-sdn-looking-toward-2013-part-1/</guid><description>&lt;h2&gt;Software Defined Network (SDN) -Looking Toward 2013 - Part 1&lt;/h2&gt;&#10;As we near the end of 2012 I wanted to reflect on some things I expect to pick up speed and solidify in 2013. Q1 of 2013 will bring beta SDN software products and with the tail end of the year bringing hardware and GA products. We will begin to see just what sort of R&amp;amp;D each vendor has been up to. Starting off let's look at some hardware.&#10;&lt;h2&gt;Forwarding Abstraction&lt;/h2&gt;&#10;The pieces and parts of hardware required to make SDN work are still rather salient. At this point it is pretty clear to expect a couple of fairly well vetted alternatives in hardware to the status-quo by the end of 2013. Question of where and how much state remains in protocols, controllers, centrally and de-centrally will continued to be proofed by researchers and industry. The biggest challenge with regard hardware is memory allocation and width and allocation to multiple tables in hardware with OpenFlow v1.1 and greater.&#10;&lt;p&gt;There have been comments coming out of Broadcom that allude to a shift in their SDN position. Here are two quotes three months apart. Both comments are presumably with regards to the &lt;a href="http://www.broadcom.com/press/release.php?id=s702418" target="_blank"&gt;StrataXGS&lt;/a&gt; Trident II chipset:&lt;/p&gt;</description></item><item><title>Programming</title><link>https://networkstatic.net/programming/</link><pubDate>Wed, 21 Nov 2012 06:20:54 +0000</pubDate><guid>https://networkstatic.net/programming/</guid><description>&lt;p&gt;[blog_grid column=&amp;ldquo;1&amp;rdquo; showposts=&amp;ldquo;15&amp;rdquo; category_in=&amp;ldquo;215&amp;rdquo; pagination=&amp;ldquo;true&amp;rdquo;]&lt;/p&gt;</description></item><item><title>Fundamentals</title><link>https://networkstatic.net/study-time/</link><pubDate>Wed, 21 Nov 2012 06:19:53 +0000</pubDate><guid>https://networkstatic.net/study-time/</guid><description>&lt;p&gt;[blog_grid column=&amp;ldquo;1&amp;rdquo; showposts=&amp;ldquo;15&amp;rdquo; post_content=&amp;ldquo;excerpt&amp;rdquo; category_in=&amp;ldquo;138&amp;rdquo; pagination=&amp;ldquo;true&amp;rdquo;]&lt;/p&gt;</description></item><item><title>Speculation</title><link>https://networkstatic.net/speculation/</link><pubDate>Wed, 21 Nov 2012 06:18:40 +0000</pubDate><guid>https://networkstatic.net/speculation/</guid><description>&lt;p&gt;[blog_grid column=&amp;ldquo;1&amp;rdquo; showposts=&amp;ldquo;15&amp;rdquo; post_content=&amp;ldquo;excerpt&amp;rdquo; category_in=&amp;ldquo;125&amp;rdquo; pagination=&amp;ldquo;true&amp;rdquo;]&lt;/p&gt;</description></item><item><title>In The Lab</title><link>https://networkstatic.net/networkstatic-in-the-lab/</link><pubDate>Wed, 21 Nov 2012 06:13:34 +0000</pubDate><guid>https://networkstatic.net/networkstatic-in-the-lab/</guid><description>&lt;p&gt;[blog_grid column=&amp;ldquo;1&amp;rdquo; showposts=&amp;ldquo;15&amp;rdquo; post_content=&amp;ldquo;excerpt&amp;rdquo; category_in=&amp;ldquo;132&amp;rdquo; pagination=&amp;ldquo;true&amp;rdquo;]&lt;/p&gt;</description></item><item><title>Why Consumers of U.S. Wireless Carriers Need a Google</title><link>https://networkstatic.net/why-consumers-of-u-s-wireless-carriers-need-a-google/</link><pubDate>Tue, 20 Nov 2012 03:51:41 +0000</pubDate><guid>https://networkstatic.net/why-consumers-of-u-s-wireless-carriers-need-a-google/</guid><description>&lt;h2&gt;Why Consumers of U.S. Wireless Carriers Need a Google&lt;/h2&gt;&#10;With talk recently of Google exploring the wireless market it is a good time to start thinking about why consumers of U.S. wireless carriers need a Google. In August of 2012 AT&amp;amp;T &lt;a href="https://prodnet.www.neca.org/publicationsdocs/wwpdf/83112att.pdf" target="_blank"&gt;filed&lt;/a&gt; to be classified not as Telecommunications provider but as an "Information Service" in the U.S. This is basically means they are not beholden to provide telephony services to the rural U.S. as the "carrier of last resort". This would permit traditional  incumbent local exchange carrier (&lt;em&gt;ILEC&lt;/em&gt;) to follow the profit rather than servicing the communities they collect federal subsidies to service.&#10;&lt;h2&gt;Wireless Service Carriers Positioning&lt;/h2&gt;&#10;&lt;p&gt;Recently, AT&amp;amp;T announced plans to invest $14 Billion into their U.S. wired and wireless infrastructure. In an article written by Bruce Kushnick the Executive Director, New Networks Institute wrote a piece titled &lt;a href="http://www.huffingtonpost.com/bruce-kushnick/atts-14-billion-dollar-br_b_2104100.html" target="_blank"&gt;AT&amp;amp;T&amp;rsquo;s $14 Billion Dollar &amp;lsquo;Bribe&amp;rsquo; to Get Rid of Telecom Regulations Is a Multi-Layered Hoax&lt;/a&gt; in the Huffington Post, in which he laid out scathing analysis. He also points out, this is not the first time AT&amp;amp;T and other wireless carriers like Verizon, have made this commitment without delivering.&lt;/p&gt;</description></item><item><title>SDN Use Cases for Service Providers</title><link>https://networkstatic.net/sdn-use-cases-for-service-providers/</link><pubDate>Sun, 18 Nov 2012 18:34:15 +0000</pubDate><guid>https://networkstatic.net/sdn-use-cases-for-service-providers/</guid><description>&lt;h2&gt;NFV Defines SDN Use Cases for Service Providers&lt;/h2&gt;&#10;&lt;span class="drop-cap"&gt;T&lt;/span&gt;&#10;he service provider community has been active with the research community since the early incubation of software define networking (SDN). Recently, there has been quite a bit of collaborative efforts amongst carrier operators to define SDN use cases for service providers. Currently, there are three Service Provider's on the Open Networking Foundation (ONF) Board today; Deutsche Telekom, Verizon, NTT. Obviously missing there is AT&amp;amp;T, who until recently, had been rather quiet about their plans. They have not been part of the ONF as a member, but appear to be taking a leadership role moving forward. Showing the most public leadership has been Deutsche Telekom (DT) and Verizon. Operators are looking to SDN concepts to increase provisioning agility in revenue generating service and reduce service time to market, capital and operational expenditure spelled out in the NFV vision. The onslaught of exponential growth in connected devices in the order of tens of billions by 2020 leaves them no choice to evolve. The sleeping giants are also eager to take profit from cloud computing and above the net services and why not, the own the last mile which is the lifeline to the cloud. &#10;&lt;ul&gt;&#10;&#9;&lt;li&gt;&lt;em&gt;Deutsche Telekom&lt;/em&gt; was an original partner with the Stanford researchers on &lt;a href="https://networkstatic.net/the-birth-unicorn-early-openflow-meeting-notes/" target="_blank"&gt;OpenFlow&lt;/a&gt;.&lt;/li&gt;&#10;&#9;&lt;li&gt;&lt;em&gt;Verizon&lt;/em&gt;, with Stuart Elby out front, has been crystal clear at the Open Networking Summits as to what Verizon's &lt;a href="http://www.youtube.com/watch?v=WVczl03edi4" target="_blank"&gt;motivations&lt;/a&gt; behind SDN involvement is, reduction of CapEx hardware spending. This is a theme amongst carriers, since a large portion of their hardware spend is networking equipment, as opposed to Hyper-Scale data center that seems to land around &lt;a href="http://perspectives.mvdirona.com/2010/09/18/OverallDataCenterCosts.aspx" target="_blank"&gt;10%-20%&lt;/a&gt; of overall cost.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;blockquote class="pullquote"&gt;“You don’t have to have an MBA to realize there is a problem. We are still ok, but not for very long.” &lt;footer&gt;Stuart Selby,Verizon Open Networking Summit Oct, 2011&lt;/footer&gt;&lt;/blockquote&gt;&#10;&lt;p&gt;Carriers provide services, take profit and pay stakeholders, just like networking vendors. All networking hardware venders use commodity silicon to some degrees to reduce manufacturing cost and increase margin. If carriers can extract more profit, from better architectural constructs and operating models, they will. No one owes anyone anything in business from the shareholders perspective.&lt;/p&gt;</description></item><item><title>BigSwitch Announces SDN GA Products and Pure Disruption</title><link>https://networkstatic.net/bigswitch-announces-sdn-ga-products-and-pure-disruption/</link><pubDate>Tue, 13 Nov 2012 06:15:45 +0000</pubDate><guid>https://networkstatic.net/bigswitch-announces-sdn-ga-products-and-pure-disruption/</guid><description>&lt;p&gt;BigSwitch Announces SDN GA Products and Pure Disruption: Today BigSwitch announced it&amp;rsquo;s first product line that is generally available. For those unaware, &lt;a href="http://www.bigswitch.com" target="_blank"&gt;BigSwitch Networks&lt;/a&gt; is a VC whose heritage was deeply seeded by researchers and PHD&amp;rsquo;s from Stanford, UC-Berkeley along with, product managers and executives from traditional networking companies. BigSwitch recently received round B venture cap funding from &lt;a href="http://www.networkworld.com/news/2012/103112-big-switch-funding-263846.html" target="_blank"&gt;Goldman Sachs&lt;/a&gt;, who was recently accepted as a member of the &lt;a href="https://www.opennetworking.org" target="_blank"&gt;Open Networking Foundation&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Tutorial to Build a FloodLight SDN OpenFlow Controller Module</title><link>https://networkstatic.net/tutorial-to-build-a-floodlight-sdn-openflow-controller-module/</link><pubDate>Sun, 11 Nov 2012 06:35:55 +0000</pubDate><guid>https://networkstatic.net/tutorial-to-build-a-floodlight-sdn-openflow-controller-module/</guid><description>&lt;h2&gt;Tutorial to Build a FloodLight SDN OpenFlow Controller Module&lt;/h2&gt;&#10;This how-to is a tutorial to build a FloodLight SDN OpenFlow controller module in Java using the open source OpenFlow controller FloodLight that BigSwitch open sourced to the community. The installation and class creation is documented on the FloodLight &lt;a href="http://www.openflowhub.org/display/floodlightcontroller/Installation+Guide" target="_blank"&gt;Wiki&lt;/a&gt;. I am adding a screencast of the installation for those who get stuck on any steps. This is just how to extract PacketIn fields, the next step is to create custom actions that can be programmatically executed. If comfortable with getting Floodlight up and running in a development environment you could skip to the 2nd post the not only extracts the packet-in but also a FlowMod is performed: F&lt;a href="https://networkstatic.net/floodlight-openflow-controller-using-the-static-flow-entry-pusher/" target="_blank"&gt;loodlight OpenFlow Controller: Using the Static Flow Entry Pusher&lt;/a&gt;&#10;&lt;h2&gt;Preparing the System for Eclipse and FloodLight&lt;/h2&gt;&#10;&lt;ul&gt;&#10;&#9;&lt;li&gt;The screencast is on a Mac running &lt;a href="http://www.vmware.com/products/fusion/overview.html" target="_blank"&gt;VMWare Fusion&lt;/a&gt; but VirtualBox works just the same for this tutorial and is free. VirtualBox can be downloaded &lt;a href="https://www.virtualbox.org/wiki/Downloads" target="_blank"&gt;here&lt;/a&gt;.&lt;/li&gt;&#10;&#9;&lt;li&gt;The OS is Ubuntu 12.04 installed on a VM. A tutorial for preparing the Ubuntu image is &lt;a href="https://networkstatic.net/openvswitch-and-openflow-lab-preparation/" target="_blank"&gt;here&lt;/a&gt;. Just any vanilla Ubuntu or any other Linux distro will cover it so use whatever you like.&lt;/li&gt;&#10;&#9;&lt;li&gt;Mac installation is about the exact same.&lt;/li&gt;&#10;&#9;&lt;li&gt;Windows will need some trickery to get &lt;a href="http://ant.apache.org/manual/install.html" target="_blank"&gt;Apache Ant&lt;/a&gt; built.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h2&gt;Install the FloodLight OpenFlow SDN Controller&lt;/h2&gt;&#10;&lt;p&gt;The following is from the &lt;a href="http://www.openflowhub.org/display/floodlightcontroller/Installation+Guide" target="_blank"&gt;FloodLight Wiki Installation Guide&lt;/a&gt;. It&amp;rsquo;s perfect so no need to rewrite it.&lt;/p&gt;</description></item><item><title>Juniper Networks at Network Field Day #4</title><link>https://networkstatic.net/juniper-networks-at-network-field-day-4/</link><pubDate>Sat, 10 Nov 2012 07:22:22 +0000</pubDate><guid>https://networkstatic.net/juniper-networks-at-network-field-day-4/</guid><description>&lt;h2&gt;Juniper Networks at Network Field Day #4&lt;/h2&gt;&#10;Juniper Networks at Network Field Day #4 Anchored the final day of &lt;a href="http://techfieldday.com/event/nfd4/" target="_blank"&gt;NFD#4&lt;/a&gt; organized by &lt;a href="http://blog.fosketts.net" target="_blank"&gt;Stephen Foskett&lt;/a&gt;, Claire Chaplais and the Gestalt IT team. We had presentations on QFabric, Mykonos, Virtual Chassis and network management automation. Below are some of my reactions to the &lt;a href="http://www.juniper.net/us/en/" target="_blank"&gt;Juniper Networks&lt;/a&gt; presentations and technology. I definitely recommend checking out my friends posts on their blogs with their thoughts on this and other presentations in the links at the end of the post.&#10;&lt;h2&gt;Mykonos Acquisition&lt;/h2&gt;&#10;Is a recent acquisition by Juniper that delivers a web security product. This was a fun presentation. I looked to the right of me and &lt;a href="http://evilrouters.net" target="_blank"&gt;Jeremy Gladdis&lt;/a&gt; was fuzzing the web server of the demo and digging into the "Super Cookie" being placed by the Mykonos appliance onto his machine by visiting Juniper homepage. Eventually our tin foil hats came off and we all enjoyed the demo.&#10;&lt;p&gt;Juniper has been quite focused on filling out their security portfolio as of late. Strong security products are a good entry point into the enterprise. The page redirect features of Mykonos based on threat level escalation were classic. I believe one page was a redirection to the nearest lawyers office. Interestingly just this week the FTC asked for a no&lt;a href="http://www.pcmag.com/article2/0,2817,2411916,00.asp" target="_blank"&gt; tracking option&lt;/a&gt; to be placed in browsers. How this affects the product I am not sure but it sounds as if the non-track is just a request in the browser which doesn&amp;rsquo;t mean a whole lot anyways. Before anyone goes all tin foil hat, this is all standard practice, Junipers website was much cleaner then some of its competitors. I would conehead over Google before anyone for tricks like &lt;a href="http://crave.cnet.co.uk/software/google-hit-by-record-fine-over-tricksy-tracking-cookies-50008863/" target="_blank"&gt;this&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>OpenStack Quantum DevStack on a Laptop with VMware Fusion</title><link>https://networkstatic.net/openstack-quantum-devstack-on-a-laptop-with-vmware-fusion/</link><pubDate>Wed, 07 Nov 2012 06:52:53 +0000</pubDate><guid>https://networkstatic.net/openstack-quantum-devstack-on-a-laptop-with-vmware-fusion/</guid><description>&lt;h2&gt;OpenStack Quantum DevStack on a Laptop with VMware Fusion&lt;/h2&gt;&#10;&lt;aside class="legacy-callout"&gt;&#10;&lt;ul&gt;&#10;&#9;&lt;li&gt;&lt;a href="https://networkstatic.net/installing-openstack-grizzly-with-devstack/" target="_blank"&gt;Installing OpenStack Grizzly with DevStack&lt;/a&gt; : Here is an updated Grizzly DevStack tutorial since Folsom is coming to an end.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;/aside&gt;&#10;&lt;p&gt;VMware Fusion and VMware Workstation both support nested virtualization. This is great news for folks looking to either learn OpenStack, proof new concepts or do development work without needing physical hardware. The reason nested virtualization is important is to support KVM, Xen or other hypervisors you need hardware virtualization to get hooks into &lt;a href="http://wiki.openstack.org/Quantum" target="_blank"&gt;Quantum&lt;/a&gt; and Open vSwitch that Qemu will not support like it did in previous OpenStack releases.&lt;/p&gt;</description></item><item><title>Brocade Acquisition of Vyatta</title><link>https://networkstatic.net/brocade-acquisition-of-vyatta/</link><pubDate>Tue, 06 Nov 2012 06:14:16 +0000</pubDate><guid>https://networkstatic.net/brocade-acquisition-of-vyatta/</guid><description>&lt;p&gt;The Brocade acquisition of Vyatta was announced today. On the surface Vyatta is functionality we have in today&amp;rsquo;s routers to load in VMs or on physical gear as a software router. It is complete with IGPs, EGPs, QOS, PBR, Crypto (no MPLS) and about everything else you find in a traditional router. Vyatta is not a vSwitch, it is routing functionality in x86. While being delivered in software ,almost everything I see is leveraging our existing bag of networking protocols and encapsulations to integrate into the network along with service provisioning in an on demand fashion. They do mention the ability to accommodate OpenFlow. I would imagine as aggressive as &lt;a href="http://www.brocade.com/index.page" target="_blank"&gt;Brocade&lt;/a&gt; is on SDN that will be in the works day one, if it is not already in the pipeline.&lt;/p&gt;</description></item><item><title>The Potential Impact of Software Defined Networking SDN on Security</title><link>https://networkstatic.net/the-potential-impact-of-software-defined-networking-sdn-on-security/</link><pubDate>Mon, 05 Nov 2012 07:26:34 +0000</pubDate><guid>https://networkstatic.net/the-potential-impact-of-software-defined-networking-sdn-on-security/</guid><description>&lt;h2&gt;The Potential Impact of Software Defined Networking SDN on Security&lt;/h2&gt;&#10;The Potential Impact of Software Defined Networking SDN on Security is something that is quite exciting as we explore the new opportunities that are enabled by SDN. Security is a perfect spot to begin contemplating the impact of SDN use cases to the infrastructure ecosystem. The disruptive implications of software defined networking on the legacy network security industry is significant. Current security solutions are left chasing the business in areas like BYOD, identity management, affordability and scale to name a few. The flexibilities presented from flow instantiation that we are seeing today in software switching, creates a blank canvas of opportunity to do things that were never possible prior with rigid proprietary hardware, software and APIs.&#10;&lt;h2&gt;Programmatic Security Policy Application with SDN&lt;/h2&gt;&#10;&lt;p&gt;This is a rare opportunity to begin truly integrating security policy at scale all the way into the network substrate. There is no way to continue absorbing exponential growth and complexity, with the incessant need to squeeze profit and find cost savings that has clearly become the new norm since the 2007 economic downturn. Technology is here to do more with less, not more with more. Linear scale does not fit in todays business leaders culture with their obsession to find savings and convince themselves that everyone is a widget that can be replaced by process. Programmatic abstractions will not fix that silliness for the record but will bring efficiencies and new opportunities to the business.&lt;/p&gt;</description></item><item><title>5 Useful Mac Apps - Snagit EverNote ScreenFlow Reeder and DaisyDisk</title><link>https://networkstatic.net/5-useful-mac-apps-snagit-evernote-screenflow-reeder-and-daisydisk/</link><pubDate>Sun, 04 Nov 2012 02:09:11 +0000</pubDate><guid>https://networkstatic.net/5-useful-mac-apps-snagit-evernote-screenflow-reeder-and-daisydisk/</guid><description>&lt;p&gt;Here is a quick rundown of 5 useful Mac Apps - Snagit EverNote ScreenFlow Reeder and DaisyDisk. All of these Apps are pretty useful to me in one way or another so take a quick peek. All are available for a Mac and a few are available on both Mac and Windows.&lt;/p&gt;</description></item><item><title>NetworkStatic's Reading For Technologists</title><link>https://networkstatic.net/articles/</link><pubDate>Thu, 01 Nov 2012 02:46:30 +0000</pubDate><guid>https://networkstatic.net/articles/</guid><description>&lt;p&gt;Feedburner is broken and I haven&amp;rsquo;t gotten around to organizing a decent feed. Check back :)&lt;/p&gt;</description></item><item><title>WireShark Install on Mac OS X</title><link>https://networkstatic.net/wireshark-install-on-mac-os-x/</link><pubDate>Sun, 28 Oct 2012 07:27:53 +0000</pubDate><guid>https://networkstatic.net/wireshark-install-on-mac-os-x/</guid><description>&lt;h2&gt;WireShark Install on Mac OS X&lt;/h2&gt;&#10;Seems like the WireShark install on Mac OS X has always been a total disaster for me. Packet capture utility are vital for developers, network and systems engineers alike. For troubleshooting or supporting SLAs it is often the only tool the defines fact vs. misconception. The WireShark installation process prior to XQuartz was long and convoluted and more often than not would end miserably. For whatever reason the WireShark download site does not list XQuartz the key to end the pain that I saw anywhere.&#10;&lt;h2&gt;WireShark Installation on Mac OSX&lt;/h2&gt;&#10;Thanks to XQuartz the Mac install is as easy as installing two applications.&#10;&lt;ol class="legacy-numbers"&gt;&#10;&lt;ol&gt;&#10;&#9;&lt;li&gt;Download and install XQuartz from &lt;a href="http://xquartz.macosforge.org/landing/" target="_blank"&gt;xquartz.macosforge.org&lt;/a&gt;.&lt;/li&gt;&#10;&#9;&lt;li&gt;Log out and log back in to restart your X session.&lt;/li&gt;&#10;&#9;&lt;li&gt;Download and install WireShark from &lt;a href="http://www.wireshark.org/download.html" target="_blank"&gt;wireshark.org&lt;/a&gt;.&lt;/li&gt;&#10;&#9;&lt;li&gt;Run WireShark.&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;/ol&gt;&#10;&lt;h2&gt;Additional Wireshark Resources&lt;/h2&gt;&#10;&lt;p&gt;Gerald touched on the interoperability problems with Mac OS X and it sounded as if there was some issues with libpcap, Mac and Wireshark. Who knows, but that recipe led to plenty of frustration in the community as more of us migrate to Mac&amp;rsquo;s for Unix capability under the hood while still maintaining the corporate application support from business suite applications.&lt;/p&gt;</description></item><item><title>Install WordPress on Ubuntu</title><link>https://networkstatic.net/install-wordpress-on-ubuntu/</link><pubDate>Wed, 24 Oct 2012 05:45:02 +0000</pubDate><guid>https://networkstatic.net/install-wordpress-on-ubuntu/</guid><description>&lt;h2&gt;Install WordPress on Ubuntu and Migrate an Existing Site&lt;/h2&gt;&#10;&lt;p&gt;Install WordPress on Ubuntu and Migrate an Existing Site: This is a guide on how to install &lt;a href="http://wordpress.org"&gt;WordPress&lt;/a&gt; on Ubuntu and migrate and existing site to  new host or a test/dev environment. Wordpress is an Open Source free package that started out as a platform for blogging and has since morphed into other more CMS like uses. Their are thousands of plugins that have been written for WordPress for styling and functionality. I like it for  blogging but have done installs for business centric usage for other folks. The simplicity is appealing along with the many tools that lower the barrier to entry into getting content to the customer or reader with little to no development work if setup properly. This post is for folks to get their feet wet or to install a &amp;ldquo;sandbox&amp;rdquo; development environment to test new themes, plugins or functionality using Ubuntu as the OS platform.&lt;/p&gt;</description></item><item><title>Revisiting the vCider SDN Solution Prior to Cisco Acquisition</title><link>https://networkstatic.net/revisiting-the-vcider-sdn-solution-prior-to-cisco-acquisition/</link><pubDate>Tue, 23 Oct 2012 03:46:26 +0000</pubDate><guid>https://networkstatic.net/revisiting-the-vcider-sdn-solution-prior-to-cisco-acquisition/</guid><description>&lt;p&gt;Revisiting the vCider SDN Solution Prior to Cisco Acquisition : I never really got a chance to know what &lt;a href="http://vcider.com"&gt;vCider&lt;/a&gt; brought to the menu of network industry disruption  prior to their recent acquisition by Cisco. Matt Nabors &lt;a href="https://twitter.com/itsjustrouting"&gt;@itsjustrouting&lt;/a&gt; and I were talking about vCider the other day and I realized I never knew much about them other than some general concepts and went to check out there site and blog and saw the content had been removed. Matt has been bearish and ahead on thought leadership on the topic of SDN, when one would be scoffed at or jumped on from the tech bullies. I think the idea of revisiting some long in the tooth practices is beginning to catch on which is great for those of us held &lt;a href="https://networkstatic.net/why-we-expect-more-from-technology-providers-we-dont-have-a-choice/"&gt;accountable&lt;/a&gt; for their performance and availability. So I wanted to revisit what little I remember and post the web mirrors that I didn&amp;rsquo;t read enough of. Chris Marino one the co-founders wrote quite a bit on his thoughts around the emerging SDN opportunities and some interesting insights from a VC.&lt;/p&gt;</description></item><item><title>Why We Expect More From Technology Providers? We Don't Have a Choice</title><link>https://networkstatic.net/why-we-expect-more-from-technology-providers-we-dont-have-a-choice/</link><pubDate>Mon, 22 Oct 2012 07:19:04 +0000</pubDate><guid>https://networkstatic.net/why-we-expect-more-from-technology-providers-we-dont-have-a-choice/</guid><description>&lt;img class="alignright" style="border: 0px;" title="future.jpg" src="https://networkstatic.net/wp-content/uploads/2012/10/future1.jpg" alt="Future" width="298" height="232" border="0" /&gt;&#10;&lt;p&gt;Why We Expect More From Technology Providers? We Don&amp;rsquo;t Have a Choice: Network Architects, engineers and operators is often where the buck stops in the infrastructure world. Our jobs implicitly depend on robust and reliable networks while trying to absorb exponential growth, coupled with flat or even shrinking budgets. We are real world people in Healthcare, Banking, Finance, Government and every other large enterprise whose revenue and even life and death SLAs. We have zero tolerance for anything other than 100% in every metric across the board while growing efficiency in the process.&lt;/p&gt;</description></item><item><title>Brocade on SDN at Network Field Day</title><link>https://networkstatic.net/brocade-on-sdn-at-network-field-day/</link><pubDate>Fri, 19 Oct 2012 03:24:22 +0000</pubDate><guid>https://networkstatic.net/brocade-on-sdn-at-network-field-day/</guid><description>&lt;p&gt;Brocade on SDN at Network Field Day: I was honored with participating in &lt;a href="http://techfieldday.com/event/nfd4/" target="_blank"&gt;Network Field Day #4&lt;/a&gt; which had loads of top notch presenters from the biggest names in Networking and IT in the industry today. Each of those organizations have people who believe in the value in open public dialogue with the consumers. This is becoming ever more important as we transition into a truly consumer driven market thanks to hyper scale providers that can bend vendors to their will on sheer volume. I was doing the reviews sequentially but Brocade had some news around &lt;a href="http://www.brocade.com/launch/sdn/index.html" target="_blank"&gt;SDN&lt;/a&gt; so I bumped them up a couple days.&lt;/p&gt;</description></item><item><title>Hybrid SDN Deployments</title><link>https://networkstatic.net/hybrid-sdn-deployments/</link><pubDate>Fri, 19 Oct 2012 02:01:09 +0000</pubDate><guid>https://networkstatic.net/hybrid-sdn-deployments/</guid><description>&lt;h2&gt;Hybrid SDN Deployments&lt;/h2&gt;&#10;The concept of a hybrid SDN deployments using and interacting with legacy networks has come up quite a bit recently in the industry. This idea that a rip and replace or physical overlay network in order to evolve networks in some cases is not often grounded in fact. When we replaced Token ring, ATM and before my time Decnet/Thinnet those were absolutely hardware forklifts because we were gutting everything from framing/cells/tokens down. When we joyously ripped protocols like IPX and AppleTalk we did not need to replace hardware since those were encapsulations on top of ethernet. Look at standalone wireless to wired deployments, all achievable.&#10;&lt;p&gt;The point is, existing investments are protected to some degree. There is risk involved with anything, so measure it. When someone takes on an MPLS  migration on their network that can be done with a new batch of seed gear to slowly migrate to or it can be done in a hybrid fashion and isolate traffic logically. Both are equally relevant the difference is tolerance for risk based on the software a vendor provides for it&amp;rsquo;s network elements. I will go through a couple of options and logical topologies.&lt;/p&gt;</description></item><item><title>Spirent Communications Looks Toward the Enterprise</title><link>https://networkstatic.net/spirent-communications-looks-toward-the-enterprise/</link><pubDate>Tue, 16 Oct 2012 21:54:02 +0000</pubDate><guid>https://networkstatic.net/spirent-communications-looks-toward-the-enterprise/</guid><description>&lt;p&gt;Spirent Communications Looks toward the Enterprise with new products and new angles to existing products. Spirent has traditionally gone after service provider markets with their product offerings. They are branching out and I liked a couple of their ideas quite a bit. It is nice to write a post in my &amp;ldquo;Tools&amp;rdquo; category, we do not exactly have a lot of those in the current networking industry today. Second blog post in one &lt;a href="https://networkstatic.net/network-management-system-nms-statseeker/" target="_blank"&gt;week&lt;/a&gt; around tools! Certainly reflects the &lt;a href="http://www.zdnet.com/juniper-networks-forrester-networks-are-at-a-breaking-point-7000005705/" target="_blank"&gt;desperate&lt;/a&gt; (forgive me for a link including Forrester, but its amusing and true that times are bad) times we are in as we try and absorb exponential &lt;a href="https://networkstatic.net/enterprise-802-11-wireless-growth-part-3/" target="_blank"&gt;growth&lt;/a&gt; on stalled frameworks. As a sponsor of Network Field Day #4 Spirent did a two hour presentation on three different products which I will run through and give my reaction in an &lt;a href="http://www.blogwithintegrity.com" target="_blank"&gt;independent&lt;/a&gt; manner.&lt;/p&gt;</description></item><item><title>SDN Using DNS Naming for Classification</title><link>https://networkstatic.net/sdn-using-dns-naming-for-classification/</link><pubDate>Tue, 16 Oct 2012 06:51:21 +0000</pubDate><guid>https://networkstatic.net/sdn-using-dns-naming-for-classification/</guid><description>&lt;p&gt;SDN Using DNS Naming for Classification Update: First, a Refresher. The initial project was outlined &lt;a href="https://networkstatic.net/sdn-using-names/" target="_blank"&gt;here&lt;/a&gt;&lt;/p&gt;&#10;&lt;h4&gt;Abstract&lt;/h4&gt;&#10;Current generation networks are under scrutiny for not presenting the proper amount of flexibility at scale to accomplish technical and business objectives. At the core of the problem are the constraints imposed by the network revolving around the inflexible nature of IP addressing being so tightly coupled to geography. Traffic classification and policy application has been far too entwined with IP prefixes rather than providing any abstractions to extract flexibility while still maintaining the scalability that is required in networks that require constant availability with ability to absorb exponential growth. This project proposes using canonical naming structures and mapping them to policy classification and policy application.&#10;&lt;p&gt;In order to apply this concept the underpinning network is assumed to support basic flow based forwarding leveraging a wire protocol such as OpenFlow. Basic forwarding primitives are required in order to instantiate proper forwarding with applied policy instructions. Using naming conventions for IP mapping and compute classification has been used by applications for decades. The same naming construct in the network as objects and leveraging network elements that are, name to policy mappings aware will insert a layer of abstraction. This framework could reduce operational complexity while increasing provisioning overhead and begin to create networks that are taxonomically application aware.&lt;/p&gt;</description></item><item><title>Network Management System NMS - Statseeker</title><link>https://networkstatic.net/network-management-system-nms-statseeker/</link><pubDate>Sun, 14 Oct 2012 18:51:03 +0000</pubDate><guid>https://networkstatic.net/network-management-system-nms-statseeker/</guid><description>&lt;p&gt;Network Management NMS - Statseeker&lt;em&gt; Not a Swiss Army Knife, but a Sharp Blade:&#10;&lt;/em&gt;&lt;/p&gt;&#10;&lt;p&gt;At &lt;a href="http://techfieldday.com/event/nfd4/" target="_blank"&gt;Network Field Day #4&lt;/a&gt; we had a a company named Statseeker who is in the Network Management business. Stewart Reed from &lt;a href="http://www.statseeker.com" target="_blank"&gt;Statseeker&lt;/a&gt;, an Australian presented and demoed the product.  We were almost outnumbered something friends, &lt;a href="http://thenetworksherpa.com" target="_blank"&gt;John Harrington&lt;/a&gt; an Irishman, &lt;a href="http://blog.ciscoinferno.net" target="_blank"&gt;Anythony Burke&lt;/a&gt; an Australian and me a native Kentuckian with a funny accent had some fun with (&lt;em&gt;cough 3xC&lt;/em&gt;). Network Management (NMS) has been a fairly major pain point in the networking industry. The history of NMS is paved with failed products and product deployments.&lt;/p&gt;</description></item><item><title>SDN Using Names</title><link>https://networkstatic.net/sdn-using-names/</link><pubDate>Tue, 09 Oct 2012 10:05:41 +0000</pubDate><guid>https://networkstatic.net/sdn-using-names/</guid><description>&lt;h3&gt; SDN Using Names&lt;/h3&gt;&#10;SDN Using Names as an approach to simplifying policy application and ease operations barrier: For anyone who is visiting for the first time, first thank you for visiting. By day I design networks with completely traditional means, the handful of scalable architectures with a slight amount of flexibility, BGP/VPNs thats it. I am a one trick pony as the saying goes, because nothing else is the right combination of stability, scalability and lowest possible operational TCO (obviously generalized). Needless to say, it isn't working in an R&amp;amp;D lab solving next-gen network problems during the day. I say that because there are obvious performance limitations in what I am proposing but I feel silicon innovation will solve much of those problems just as merchant silicon has opened a new world up to the x86 industry almost two decades ago with the microprocessor and much more recently starting to bring the hope of horizontalization to the networking industry. By night, I think of ways to fix the ever growing frustrating list of problems we in the networking industry face. Our answers are to create more problems with more protocols/encapsulation/shims/duck tape rather than as Scott Shanker puts it "The ability to master complexity is not the same as the ability to extract simplicity".&#10;&lt;h3&gt;SDN Abstraction Refresher&lt;/h3&gt;&#10;&lt;p style="text-align: center;"&gt;&lt;a href="https://networkstatic.net/wp-content/uploads/2012/10/SDN-Abstraction-Layers.jpg"&gt;&lt;img class="size-full wp-image-2993 aligncenter" title="SDN-Abstraction-Layers" src="https://networkstatic.net/wp-content/uploads/2012/10/SDN-Abstraction-Layers.jpg" alt="SDN-Abstraction-Layers" width="537" height="424" /&gt;&lt;/a&gt;&lt;em&gt;&lt;strong&gt;Figure 1.&lt;/strong&gt; &lt;/em&gt;Some quick concepts on abstraction layers as compared to x86 concepts.&lt;/p&gt;</description></item><item><title>Network Field Day 4</title><link>https://networkstatic.net/network-field-day-4/</link><pubDate>Tue, 09 Oct 2012 04:07:46 +0000</pubDate><guid>https://networkstatic.net/network-field-day-4/</guid><description>&lt;h2&gt;Network Field Day 4&lt;/h2&gt;&#10;&lt;a href="https://networkstatic.net/wp-content/uploads/2012/10/NFD-Logo.jpg"&gt;&lt;img class="alignright size-full wp-image-2966" title="NFD-Logo" src="https://networkstatic.net/wp-content/uploads/2012/10/NFD-Logo.jpg" alt="network field day" width="150" height="150" /&gt;&lt;/a&gt;Network Field Day 4 is upon us again! I was honored by the Network Field Day delegates and asked to participate as a delegate in Network Field Day 4 in Silicon Valley starting at 1:30PM PST. Not only do the Field Day event staff record the events but they also live stream the vendor presentations! Even more interesting the incredibly insightful dialogue from the delegates and even some heralded "Snark" from the infamous &lt;a href="http://networkingnerd.net" target="_blank"&gt;Tom Hollingsworth&lt;/a&gt;. The halls of the past, current and future Field Day delegates are some of the best in the industries of wireless, storage and networking. I am incredibly excited to get to me so many of the folks I look to help shape my hone my knowledge and perspectives on technology.&#10;&lt;p&gt;What separates the men and women that not only I personally hold on a pedestal, but vendors, pundits analyst and investors are far from just the hard skills of IT. First and foremost, they are all friendly humble people that believe in community. In their day jobs, they are most likely the most informed and up to date on industry trends and technologies in the room but they are still humbly considerate of others opinions and treat colleagues with respect. The soft skills of relationship building, humility and teamwork is often lost in such an emerging industry like IT where intellect is perceived as the capital.&lt;/p&gt;</description></item><item><title>OpenStack Folsom Quantum Devstack Installation Tutorial</title><link>https://networkstatic.net/openstack-folsom-quantum-devstack-installation-tutorial/</link><pubDate>Sat, 06 Oct 2012 06:45:35 +0000</pubDate><guid>https://networkstatic.net/openstack-folsom-quantum-devstack-installation-tutorial/</guid><description>&lt;h2&gt;OpenStack Folsom Quantum Devstack Installation Tutorial and Screencast&lt;/h2&gt;&#10;&lt;aside class="legacy-callout"&gt;&#10;&lt;ul&gt;&#10;&#9;&lt;li&gt;&lt;a href="https://networkstatic.net/installing-openstack-grizzly-with-devstack/" target="_blank"&gt;Installing OpenStack Grizzly with DevStack&lt;/a&gt; : Here is an updated Grizzly DevStack tutorial since Folsom is coming to an end.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;/aside&gt;&#10;&lt;p&gt;This is a quick guide that includes a diagram of a working reference architecture for installation of the OpenStack Folsom release using which includes the Quantum networking component using the &lt;a href="http://devstack.org" target="_blank"&gt;DevStack&lt;/a&gt; installation bash script.&lt;/p&gt;</description></item><item><title>HP Announces Their SDN Controller</title><link>https://networkstatic.net/hp-announces-their-sdn-controller/</link><pubDate>Wed, 03 Oct 2012 02:05:49 +0000</pubDate><guid>https://networkstatic.net/hp-announces-their-sdn-controller/</guid><description>&lt;h3&gt;HP Announces Their SDN Controller&lt;/h3&gt;&#10;Hp announces their SDN controller at Interop: HP is not new to the OpenFlow conversation. HP was one of the first, if not the first networking companies to make their OpenFlow enabled switch firmware agent GA (generally available) in 16 products in 2011 and now up to 24 products in 2012. HP has also long supported the &lt;a href="http://groups.geni.net/geni/wiki/GENIRacksHome" target="_blank"&gt;GENI&lt;/a&gt; project which is an &lt;a href="http://www.nsf.gov" target="_blank"&gt;NSF&lt;/a&gt; project to leverage prototyped networks fir research. Likely the most recognized project that from GENI was Flowvisor, which is the concept of slicing and arbitrating networks to create virtualization. Yes, &lt;a href="https://networkstatic.net/ietf-draft-bgp-signaled-end-system-ip-vpns/" target="_blank"&gt;MPLS/BGP/VPNs&lt;/a&gt; do that also, but the difference is an exposed northbound API that allows for self provisioning.&#10;&lt;p style="text-align: center;"&gt;&lt;a href="https://networkstatic.net/wp-content/uploads/2012/10/sdn-agility-hp.jpg"&gt;&lt;img class="size-full wp-image-2911 aligncenter" title="sdn-agility-hp" src="https://networkstatic.net/wp-content/uploads/2012/10/sdn-agility-hp.jpg" alt="sdn-agility-hp" width="531" height="321" /&gt;&lt;/a&gt;&lt;/p&gt;</description></item><item><title>The Control Plane, Data Plane and Forwarding Plane in Networks</title><link>https://networkstatic.net/the-control-plane-data-plane-and-forwarding-plane-in-networks/</link><pubDate>Thu, 27 Sep 2012 03:52:40 +0000</pubDate><guid>https://networkstatic.net/the-control-plane-data-plane-and-forwarding-plane-in-networks/</guid><description>&lt;h2&gt;The Control Plane, Data Plane and Forwarding Plane in Networks&lt;/h2&gt;&#10;The Control Plane, Data Plane and Forwarding Plane in Networks is the heart core DNA in today's networking hardware to move IP packets from A to Z. The Management plane is another vital component but also widely excepted as user to hardware interaction. These planes of operation are the building blocks of the layered architecture that networks have evolved to today. By abstracting data to conform to these constructs is how the Internet works today. If I could rewind a dozen years I would probably have made myself write the concepts of Control, Data and Forwarding planes on the chalkboard a few thousands times rather than spending the first couple of years of my career trying to understand the incredible complexities of networks backwards with a weak foundation.&#10;&lt;p&gt;Working with some interns this week I was walking through these &amp;ldquo;planes&amp;rdquo; with them and as I have in the past got to &amp;ldquo;Data Plane&amp;rdquo; and &amp;ldquo;Forwarding Plane&amp;rdquo;. It seems a bit nascent from time to time what the difference, if any is between the forwarding and data plane. I thought it might be helpful to cobble together some definitions from some of my favorite books, a couple of RFCs and some drawings, so I don&amp;rsquo;t have to fumble around every semester with poor explanations. Kicking off with fast path, slow path, BCAM and Trie lookups doesn&amp;rsquo;t do anyone any good. So lets look at some pictures instead. &lt;em&gt;Disclaimer much of this can be semantics which tend to get tedious and boring so, well sorry.&lt;/em&gt;&lt;/p&gt;</description></item><item><title>OpenFlow, OpenvSwitch and KVM SDN Lab Installation App</title><link>https://networkstatic.net/openflow-openvswitch-and-kvm-sdn-lab-installation-app/</link><pubDate>Mon, 24 Sep 2012 23:15:47 +0000</pubDate><guid>https://networkstatic.net/openflow-openvswitch-and-kvm-sdn-lab-installation-app/</guid><description>&lt;h2&gt;OpenFlow, OpenvSwitch and KVM SDN Lab Installation App&lt;/h2&gt;&#10;This OpenFlow, Open vSwitch and KVM SDN Lab Installation App is a python app that will install a few different options at an SDN lab. There are some really nice SDN applications that are coming along that have been open sourced from vendors or the community. Lots of people are really getting interested in understanding what SDN and getting to know new technologies but can quickly hit a wall wether its time to figure out the often tricky installs, lack of experience in Unix and for all of us just time to dedicate to getting a lab framework built.I tried to keep the Python program very linear to make it as readable and reusable as I could. I think I wrote about five pages worth of comments in it.&#10;&lt;hr&gt;&#10;&lt;a href="https://networkstatic.net/wp-content/uploads/2012/09/term21.jpg"&gt;&lt;img class="alignright size-full wp-image-2873" title="term2" alt="terminal sdn" src="https://networkstatic.net/wp-content/uploads/2012/09/term21.jpg" width="200" height="200" /&gt;&lt;/a&gt;&#10;It can be difficult either remembering how to install some of this stuff after a while so I have gotten to the point just to automate everything if possible. The nice thing is you can easily fire up QEMU/KVM within VM Fusion and VirtualBox  without having to have a server. I will refer to QEMU/KVM interchangeably, it just depends on hardware virtualization. The app will script install for OpenFlow controllers like FloodLight and POX along with OpenvSwitch v1.8.9 with and without VXLan (Cisco contribution) support all on top of the KVM hypervisor. That installation can be used as an SDN lab or just in general to start understanding hypervisor switching with Open vSwitch and forget about the control plan OpenFlow part.&#10;&lt;hr&gt;&#10;There is a screencast below in case anyone gets stuck and needs a reference. I did a post for the pre-requisite Ubuntu &lt;a href="https://networkstatic.net/openvswitch-and-openflow-lab-preparation/" target="_blank"&gt;install&lt;/a&gt; in case anyone is unfamiliar with that. VM Fusion networking seemed to work the best for me with OpenvSwitch when it came to being able to talk all the way from the nested VM out, I touch on that later before the installation.&#10;&lt;h2&gt;Open vSwitch KVM and OpenFlow Build Options&lt;/h2&gt;&#10;&lt;p&gt;There are four installation builds to choose from. I didn&amp;rsquo;t want to muck up the code too much with too many nested options so I kept it simple. If you were to want for example FloodLight with the OpenvSwitch VXlan build you would just stop the openvswitch-controller service and install Floodlight as explained in these &lt;a href="https://networkstatic.net/floodlight-openflow-controller-screencast-with-hp-switches/" target="_blank"&gt;directions&lt;/a&gt;. I also compile everything from source to have the latest development releases with latest features and also to avoid too much package break. I install generic things from package for simplicity, for example, Git, JRE and linux-headers.&lt;/p&gt;</description></item><item><title>OpenvSwitch and OpenFlow Lab Preparation</title><link>https://networkstatic.net/openvswitch-and-openflow-lab-preparation/</link><pubDate>Fri, 21 Sep 2012 04:51:46 +0000</pubDate><guid>https://networkstatic.net/openvswitch-and-openflow-lab-preparation/</guid><description>&lt;h2&gt;OpenvSwitch and OpenFlow Lab Preparation&lt;/h2&gt;&#10;This post OpenvSwitch and OpenFlow Lab Preparation will serve as a base Linux install using virtual machines in VirtualBox a free hypervisor that you can run on your laptop or desktop. Many do not have access to lab gear but would still like to be able to gets hands on experience in learning new technologies. Another important reason to have access and understanding to how to build virtual machines is for proof of concepts and modeling architectures for validity.&#10;&lt;p&gt;If you have want to get into really digging into KVM and Open vSwitch I highly recommend getting VMFusion since it supports nested hypervisor. Here is a &lt;a href="https://networkstatic.net/openstack-quantum-devstack-on-a-laptop-with-vmware-fusion/" target="_blank"&gt;link&lt;/a&gt; touching on a use case.&lt;/p&gt;</description></item><item><title>Does the Cost of Cloud IaaS Intersect the Local VM?</title><link>https://networkstatic.net/does-the-cost-of-cloud-iaas-intersect-the-local-vm/</link><pubDate>Wed, 19 Sep 2012 04:02:36 +0000</pubDate><guid>https://networkstatic.net/does-the-cost-of-cloud-iaas-intersect-the-local-vm/</guid><description>&lt;h2&gt;Does the Cost of Cloud IaaS Intersect the Local VM?&lt;/h2&gt;&#10;Does the Cost of Cloud IaaS Intersect the Local VM? In the 90's if you were to recommend hosting your corporate email from a provider for cost savings you would probably get laughed out of a job. Today depending on the sensitivity of your data and levels of FUD in your organization suggesting keeping email long term on your premise you may get just as bizarre of looks from your colleagues. Hard to beat free. The ability to monetize things like 3Gb of storage from DropBox or free email to an Enterprise from Google is fascinating. Last I saw %97 of Googles income was from advertising.&#10;&lt;ul&gt;&#10;&#9;&lt;li&gt;SaaS - Well, we all have a Gmail account.&lt;/li&gt;&#10;&#9;&lt;li&gt;PaaS - Some examples-Wordpress &lt;a href="http://wordpress.com" target="_blank"&gt;Wordpress.org&lt;/a&gt;, Drupal &lt;a href="http://www.drupalgardens.com" target="_blank"&gt;Drupalgardens&lt;/a&gt;, (insert_prefix_names)Cloud(insert_suffix_names) doing pretty cool stuff, Ruby on Rails &lt;a href="http://www.heroku.com" target="_blank"&gt;Heroku&lt;/a&gt;.&lt;/li&gt;&#10;&#9;&lt;li&gt;IaaS - Can it be monetized? Why not. Mine it? Add value like amazon does with extra services, features, availability etc. First hit is free. More PaaS integration? Wtf do I care about an OS again? Is it the wrong place to abstract? Probably&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;hr /&gt;&#10;If&lt;strong&gt; Google &lt;/strong&gt;can be&lt;strong&gt; worth $200 Billion&lt;/strong&gt; US and derive &lt;strong&gt;%97&lt;/strong&gt; of it's revenue from &lt;strong&gt;advertising&lt;/strong&gt;, anything is doable and leads me to never rule anything out.&#10;&lt;p style="text-align: center;"&gt;&lt;a href="https://networkstatic.net/wp-content/uploads/2012/09/Q1-2012.jpg"&gt;&lt;img class="aligncenter wp-image-2800" title="Q1 Q2 2012 Google Microsoft Apple" src="https://networkstatic.net/wp-content/uploads/2012/09/Q1-2012.jpg" alt="Q1 Q2 2012 Google Microsoft Apple" width="580" height="420" /&gt;&lt;/a&gt;&lt;/p&gt;</description></item><item><title>IETF Draft - BGP-signaled end-system IP/VPNs Contrail</title><link>https://networkstatic.net/ietf-draft-bgp-signaled-end-system-ip-vpns/</link><pubDate>Mon, 17 Sep 2012 03:28:29 +0000</pubDate><guid>https://networkstatic.net/ietf-draft-bgp-signaled-end-system-ip-vpns/</guid><description>&lt;h2&gt;IETF Draft - BGP-signaled end-system IP/VPNs Contrail&lt;/h2&gt;&#10;There is a new IETF Draft - BGP-signaled end-system IP/VPNs draft-marques-l3vpn-end-system submitted for review. It is quite the whose who on the working group of traditional networking vanguard companies like Cisco, Juniper, Infinera, AT&amp;amp;T labs, Verizon and a new comer to the race Contrail. Contrail is an SDN startup with series A funding at $10Mil. There are some of the best out there heading that way such as Kireeti Kompella from Juniper, Ankur Singla from Aruba (I had Arista typed edited (Oct 10- Thanks Ankur!), Pedro Marques from Google and Harshad Nakil from Cisco. Rumor is this is a spin-in for Juniper. If you want to go straight to the draft and skip any of this post here is the &lt;a href="http://tools.ietf.org/html/draft-marques-l3vpn-end-system-07" target="_blank"&gt;link&lt;/a&gt;.&#10;&lt;p&gt;What jumps out on the surface the most is this draft is actually talking to a coherent control plane. I have changed my mind on what it is going on in the draft proposal about 10 times over the past 3 days that I have looked at it so it will probably change again and I am sure I missing about a dozen nuances. It is truly amazing to see how BGP has evolved through extensions to be as relevant today and in the future as ever.&lt;/p&gt;</description></item><item><title>The Death of the Wired Enterprise Network</title><link>https://networkstatic.net/the-death-of-the-wired-enterprise-network/</link><pubDate>Sat, 15 Sep 2012 22:55:30 +0000</pubDate><guid>https://networkstatic.net/the-death-of-the-wired-enterprise-network/</guid><description>&lt;p&gt;&lt;a href="https://networkstatic.net/wp-content/uploads/2012/09/bad.cabling.networks.jpg"&gt;&lt;img class="alignright wp-image-2723" title="bad.cabling.networks" src="https://networkstatic.net/wp-content/uploads/2012/09/bad.cabling.networks-310x350.jpg" alt="bad cabling communications networks" width="248" height="280" /&gt;&lt;/a&gt;&lt;/p&gt;&#10;&lt;p&gt;I remember about two years ago having a conversation with my boss and we were speculating on the lifespan of a wired network in an Enterprise campus. We both agreed it would all be driven by the App. Well, thanks to carrier networks being what they are, content, cloud and application providers typically develop to the lowest common denominator bandwidth, the cellular mobile networks. Those are networks that struggle to pull off double digit Mbps performance yet we (not necessarily the user, well except for my residential service, another story) are demanding 1Gbps to the desktop. The days of fat client server apps being the bandwidth driver are trending down as SaaS and cloudy like application delivery rapidly grows. Is this the death of the wired Enterprise network?&lt;/p&gt;</description></item><item><title>Django Installation and First App Tutorial</title><link>https://networkstatic.net/django-installation-and-first-app-tutorial/</link><pubDate>Sat, 15 Sep 2012 08:03:29 +0000</pubDate><guid>https://networkstatic.net/django-installation-and-first-app-tutorial/</guid><description>&lt;h2&gt;Django Installation and First App Tutorial &lt;/h2&gt;&#10;&lt;p&gt;&lt;strong&gt;Django Installation and First App Tutorial:&lt;/strong&gt; Django is a powerful web framework written in Python used to create pluggable database driven websites that are complex, but simplified by the abstraction of the Django framework. I am using Ubuntu for this install but beyond it will work for most OS&amp;rsquo;s. I will configure Django to use sqlite as a database. It can easily be swapped to use &lt;a href="http://postgresql.org" target="_blank"&gt;PostgreSQL&lt;/a&gt;, &lt;a href="http://www.mysql.com/" target="_blank"&gt;MySql&lt;/a&gt;, &lt;a href="http://www.sqlite.org/" target="_blank"&gt;Sqlite&lt;/a&gt; or an &lt;a href="http://www.oracle.com/technetwork/indexes/downloads/index.html" target="_blank"&gt;Oracle&lt;/a&gt; database. The installation is pretty simple, getting to know the configuration files and framework is quite a bit more complicated depending on how much experience with Python and web development you have. For that reason, this is a super simple tutorial to break someone in to how Django operates.&lt;/p&gt;</description></item><item><title>Enterprise 802.11 Wireless Growth (Part 3)</title><link>https://networkstatic.net/enterprise-802-11-wireless-growth-part-3/</link><pubDate>Fri, 07 Sep 2012 05:51:33 +0000</pubDate><guid>https://networkstatic.net/enterprise-802-11-wireless-growth-part-3/</guid><description>&lt;h2&gt;Enterprise 802.11 Wireless Growth (Part 3)&lt;/h2&gt;&#10;In &lt;a href="https://networkstatic.net/2012/08/why-enterprise-wireless-networks-got-it-right/" target="_blank"&gt;part 1&lt;/a&gt; of the three parter we looked at the ability to manage 802.11 wireless networks and the benefits of analytics that is provided out of the box. In &lt;a href="https://networkstatic.net/2012/09/enterprise-wireless-and-wired-traffic-part2" target="_blank"&gt;part 2&lt;/a&gt; we compared traffic rates (unscientifically) between an average wireless controller distribution and wired distribution. In the conclusion we will look at the growth of three points over two years. We have those numbers because out of the box central controllers retain this information. While we capture similar information from wired networks, it is a totally separate process, cost and operational task requiring significant engineering people hours to operate the management plane independently in the enterprise. This is very close to what many are explaining software defined networking as today. Missing key ingredients are open standards and integration into the rest of the computing ecosystem but it is certainly a much more coherent architecture than thousands of distributed devices individually maintaining state within a single administrative boundary.&#10;&lt;h2&gt;Exponential Enterprise 802.11 Wireless Growth&lt;/h2&gt;&#10;The numbers are doubling annually with no signs of letting up. The &lt;a href="http://www.cisco.com/en/US/solutions/collateral/ns341/ns525/ns537/ns705/ns827/white_paper_c11-520862.html" target="_blank"&gt;Cisco Networking Index&lt;/a&gt; is always fun to read, if you have not before I recommend admiring the data. I whole heartedly believe the reason we can deliver really good wireless (enterprise, certainly not giving kudos to my cell service) networks is because of the of the centralized nature of the current predominate frameworks. &#10;&lt;h2&gt;Centralized Wireless Today is SDN&lt;/h2&gt;&#10;The need to manage edge RF, was enough of a technical reason to drive centralization. Interesting product stories on who was first and who followed when wireless controller architectures emerged a few years back if anyone has never poked around on that. These numbers are from September of 2012, while &lt;a href="https://networkstatic.net/2012/08/why-enterprise-wireless-networks-got-it-right/" target="_blank"&gt;part 1&lt;/a&gt; were from August of 2012. The delta is students returning for Fall semester and it is a 14-day aggregate. These are 802.11 vendor OUI are burned into wireless NICs and captured centrally from the controller. I wrote a hacked up Perl script years ago to crawl neighbor discoveries for that years ago, then Cisco Works fixed that 0_O, thats right Cisco works. &#10;&lt;p&gt;The difference in today&amp;rsquo;s centralized wireless solutions to the current SDN debate is only different in adding the ability to distribute forwarding to the edge. In most centralized wireless controllers, the data plane is an overlay tunnel back to a headend control plane for policy and forwarding. Sound familiar? It should, that is the same logic as most of the emerging SDN data center overlay solutions. Companies like Aruba are beginning to sell products that address this for remote sites and more theoretical distributed scale. That is flow based forwarding. Knowing nothing about the technology, if you were to match up Aruba distributed wireless, Juniper&amp;rsquo;s Q-Fabric, Cisco&amp;rsquo;s SW firewall and OpenFlow, there would be very similar logic in the lineup. The main difference would be proprietary vs. open wire protocols.&lt;/p&gt;</description></item><item><title>Enterprise Wireless and Wired: A Byte is a Byte (Part 2)</title><link>https://networkstatic.net/enterprise-wireless-and-wired-traffic-part2/</link><pubDate>Fri, 07 Sep 2012 05:43:48 +0000</pubDate><guid>https://networkstatic.net/enterprise-wireless-and-wired-traffic-part2/</guid><description>&lt;p&gt;Enterprise Wireless and Wired: A Byte is a Byte (Part 2): This is a second post regarding enterprise wireless and why those networks are much more &lt;strong&gt;manageable,&lt;/strong&gt; (out of the box) then it&amp;rsquo;s wired network brethren. I have simplified my explanation of why the current path needs adjusting and the &lt;a href="https://networkstatic.net/2012/05/sdn-business-cases/" target="_blank"&gt;reasons&lt;/a&gt; why. Enterprise, Data Center and Service Provider networks all have very different challenges, but we are fairly limited architecturally in how we tackle those unique problems. That said, all have one thing in common, the management &lt;a href="http://etherealmind.com/openflow-software-defined-networking-routing-or-switching/" target="_blank"&gt;plane&lt;/a&gt;. Traffic rates going through wireless controllers are pretty close and in many cases higher, than wired devices as mobile devices continue to fill our pockets. We are at a crossroads that we are calling software defined networking that can bring networks back into alignment with the rest of the computing world, well, at least the same galaxy.&lt;/p&gt;</description></item><item><title>Python Tutorial: Classes, Objects, Methods, init and Simple Examples</title><link>https://networkstatic.net/python-tutorial-classes-objects-methods-init-and-simple-examples/</link><pubDate>Thu, 06 Sep 2012 23:09:40 +0000</pubDate><guid>https://networkstatic.net/python-tutorial-classes-objects-methods-init-and-simple-examples/</guid><description>&lt;h2&gt;Python Tutorial: Classes, Objects, Methods, init and Simple Examples&lt;/h2&gt;&#10;Python Tutorial on Classes, Objects, Methods: In this post we will dive into Python classes, methods, objects and using the init constructer to initialize classes. Object oriented programming has gone well past being a fad (sorry punchcards) like it or not encapsulation and inheritance is winning out. The idea is to make modules and procedures abstracted, modifiable and reusable without needing to worry about reinventing the wheel. All interesting stuff, but this is just to give some examples as I am knocking off years of rust and having some fun with Python. These are just simple examples that might help folks out as they start learning programming. Most attempts Python tutorials on classes object methods etc, are more advanced than are appropriate for beginners.&#10;&lt;hr&gt;&#10;If you want a quick review on basic functions check this tutorial.&#10;&lt;ul&gt;&#10;&#9;&lt;li&gt;More Python tutorials: &lt;a href="https://networkstatic.net/python-tutorial-functions-and-passing-lists-and-dictionaries-with-simple-examples/" target="_blank"&gt;Functions and Passing Lists and Dictionaries with Simple Examples&lt;/a&gt;&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;hr /&gt;&#10;&lt;h2&gt;Python Classes and Object Oriented Programming OOB&lt;/h2&gt;&#10;&lt;a href="https://networkstatic.net/wp-content/uploads/2012/09/Kitty-Coder.jpg"&gt;&lt;img class="alignright size-full wp-image-2478" title="Kitty-Coder" alt="Kitty writing code" src="https://networkstatic.net/wp-content/uploads/2012/09/Kitty-Coder.jpg" width="247" height="247" /&gt;&lt;/a&gt;&#10;If you look at python.org &lt;a href="http://docs.python.org/py3k/tutorial/classes.html"&gt;docs&lt;/a&gt; the definition is about as clear as mud. No offense intended, programming concepts in general can fairly nacient and wide open to interpretation regardless of language since it is as much style and theory. I tend to explain classes and methods (think function in a class) as a blueprint for what to pass and object data with attributes being applied through a framework. I can pass an object (examples to follow) into a class and it modifies the object based on the &lt;strong&gt;blueprint&lt;/strong&gt;.&#10;&lt;h2&gt;Python Methods&lt;/h2&gt;&#10;In the simplest term a &lt;a href="http://docs.python.org/py3k/tutorial/classes.html#method-objects" target="_blank"&gt;method&lt;/a&gt; is a function inside of an object. You can pass attributes (variable inside a method) to the class and method that will get processed inside of the method and independently for each object. Variables or attributes defined or initialized at the beginning of the class are inherited to the methods inside that class. We will see in the examples.&#10;&lt;h2&gt;Python Self for OOB&lt;/h2&gt;&#10;This can be rather confusing starting out. In a method which is a function inside of a class the first parameter is always &lt;strong&gt;self&lt;/strong&gt;. &lt;a href="http://www.tutorialspoint.com/python/python_classes_objects.htm" target="_blank"&gt;Self&lt;/a&gt; is just referring to the object you passed into the method. Clear as mud? One other thing is a class object can be called or instantiated using __init__ (self). Using init will save you a couple lines of code. I learn through example so enough chit chat.&#10;&lt;h4&gt;Practical Application (ever so loosely o_O)&lt;/h4&gt;&#10;A practical application of this could be calling a process that would spawn a VM to spin up. Here we will just print the name but you could execute a shell command that would spawn a widget.&#10;&lt;pre class="brush: python; gutter: false; first-line: 1; highlight: []; html-script: false"&gt;subprocess.Popen(&amp;quot;&amp;quot;&amp;quot; nova boot --flavor 1 --image &amp;lt;insert image ID here&amp;gt; --key_name \&#10; ssh_key&amp;quot;&amp;quot;&amp;quot; VMnameFromPython &amp;quot;&amp;quot;&amp;quot;, shell=True, stdin=None, executable=&amp;quot;/bin/bash&amp;quot;&amp;quot;&amp;quot;)&lt;/pre&gt;&#10;&lt;h2&gt;Class and Method Examples&lt;/h2&gt;&#10;So here are a couple of easy peasy examples that should help you get a kickstart, think of code reusability and as why you would add this extra complexity. Also you notice what happens when we try and print from the method, it returns 'none', in the next example we will change that to return which can be useful to break out of methods and also return parameters back from the method while pass would be indicate and empty block statement:&#10;&lt;pre class="brush: python; gutter: false; first-line: 1; highlight: []; html-script: false"&gt;#!/usr/bin/python&#10;class VMname:&#10; def createVM(self, name):&#10; #Remember Self just refers to the object you are passing firstHot or secondHost&#10; self.name=name&#10; #Initialize the argument we passed with the object&#10; def stateVM(self):&#10; print(self.name)&#10;&lt;p&gt;#Create your first object&#10;firstHost = VMname()&#10;firstHost.createVM('email.foo.org')&#10;Hname1 = firstHost.stateVM()&#10;print('You named your VM ' + str(Hname1))&lt;/p&gt;&#10;&lt;p&gt;#Create your second object&#10;secondHost = VMname()&#10;secondHost.createVM('ldap.bar.org')&#10;Hname2 = secondHost.stateVM()&#10;print('You named your VM ' + str(Hname2))&lt;/p&gt;&#10;&lt;p&gt;#Notice what gets printed when we call the method stateVM, it prints 'None&amp;quot;&#10;#If we replace print(self.name) with return(self.name)&#10;#it will pass the attribute back outside of the class.&#10;#Next we call a method directly using the variable assigned to the object and class &amp;quot;firstHost&amp;quot; with a &amp;quot;.statVM() calling the method.&#10;#It will not pass back data from the class without us using return.&#10;#Notice it says none.&lt;/p&gt;&#10;&lt;p&gt;print(firstHost.stateVM())&#10;print(Hname2)&lt;/pre&gt;</description></item><item><title>Python Tutorial: Functions and Passing Lists and Dictionaries with Simple Examples</title><link>https://networkstatic.net/python-tutorial-functions-and-passing-lists-and-dictionaries-with-simple-examples/</link><pubDate>Tue, 04 Sep 2012 06:54:38 +0000</pubDate><guid>https://networkstatic.net/python-tutorial-functions-and-passing-lists-and-dictionaries-with-simple-examples/</guid><description>&lt;h2&gt;Python Tutorial: Functions, Passing Lists, Dictionaries with Simple Examples&lt;/h2&gt;&#10;&lt;p&gt;In Python the differences between functions, classes and methods is often best explained with examples of code. It is also the best way to learn syntax and languages for some of us. We will start off with Functions and work into Classes which is the Object Oriented Programming (OOP) in Python over the next few posts. These are merely blueprints to run data through often times in an iterated fashion. Python is much like C in syntax minus declarations, in fact it, is written in C and interpreted in a C binary. This will be the first of a series of post that are a primer to the programming language Python. This Python tutorial will focus on functions with a refresher or start learning Python for beginners to look at lists, dictionaries / associative arrays.&lt;/p&gt;</description></item><item><title>Software Defined Data Center Slidedeck</title><link>https://networkstatic.net/software-defined-data-center-slidedeck/</link><pubDate>Thu, 30 Aug 2012 01:27:26 +0000</pubDate><guid>https://networkstatic.net/software-defined-data-center-slidedeck/</guid><description>&lt;p&gt;Software Defined Data Center SlideDeck: Posting a SlideDeck from a presentation while back titled Software Defined Data Centers, if the graphics help anyone with their own presentations have at em! The only different concepts are some public cloud thoughts and scenarios and some analogies to wireless controllers and SDN deployments.&lt;/p&gt;</description></item><item><title>Nested KVM Hypervisor Support</title><link>https://networkstatic.net/nested-kvm-hypervisor-support/</link><pubDate>Sat, 25 Aug 2012 05:50:01 +0000</pubDate><guid>https://networkstatic.net/nested-kvm-hypervisor-support/</guid><description>&lt;h2&gt;Nested KVM Hypervisor Support&lt;/h2&gt;&#10;&lt;p&gt;Adding Hardware Virtualization Support to a VM in KVM with Nested Hypervisor support is pretty important for folks wanting to do proofs for VMs, IaaS, OpenStack etc. It is fairly well supported now under both KVM and Xen. Not to mention, who wants to lab up bare metal when they can use their laptop for modeling. The major driver for nested virtualization is the ability to run nested Hypervisors in IaaS and/or Public Cloud services. It will be attractive for some to run VM farm as a service instances. This provides added flexibility to the customer to maximize their subscription of leased cloud instances.&lt;/p&gt;</description></item><item><title>Public Cloud and Network as a Service</title><link>https://networkstatic.net/public-cloud-network-as-a-service/</link><pubDate>Tue, 21 Aug 2012 04:59:44 +0000</pubDate><guid>https://networkstatic.net/public-cloud-network-as-a-service/</guid><description>&lt;h2&gt;Public Cloud and Network as a Service&lt;/h2&gt;&#10;The first part of the post was building the &lt;a href="https://networkstatic.net/2012/08/the-hp-public-cloud-and-openstack/"&gt;Public Cloud&lt;/a&gt; node. The second part of this post is going to be a primitive blue print for how to build a hybrid private/public network and what network as a service could mean. Without reliable national broadband and backbone networks both provider and customer will be taking serious risks. I will ask one question and move on, what incentive does a carrier have to improve their infrastructure if they are the incumbent with no competition? Puzzling we get so enthralled in the minute details of technology yet something as broken as the very backbone substrate right before our eyes. It isn't waiting on any technological breakthroughs, only vision and leadership.&#10;&lt;aside class="legacy-callout"&gt;&lt;strong&gt;So WtF is Hybrid Cloud Networking? &lt;/strong&gt;It is a fancy name for GRE and VXLAN tunnels getting pinned from a local cloud stack to a public cloud stack. Voila!&lt;/aside&gt;&#10;&lt;h2&gt;Grandpas Network, What has Changed?&lt;/h2&gt;&#10;&lt;figure class="legacy-figure"&gt;&lt;img src="https://networkstatic.net/wp-content/uploads/2012/12/fail-cabling.jpg" alt="Cloud Internet Fail"&gt;&lt;/figure&gt;&#10;There has been a growing swell in the networking industry coined Software Defined Networking (SDN) that has culminated into a full fledged evolution. One primary drivers of change in the networking industry has come from commodity hardware. Researchers at Stanford began working to decouple the network operating system and control plane. As soon as &lt;a href="http://blog.ioshints.info/2012/05/openflow-google-brilliant-but-not.html" target="_blank"&gt;Google&lt;/a&gt; bought in things got serious. As a result, &lt;a href="http://etherealmind.com/merchant-silicon-vendor-software-rise-lost-opportunity/" target="_blank"&gt;merchant silicon&lt;/a&gt; manufacturers have supposedly begun to alter their "off the shelf silicon" to facilitate this exploration. Still today, the topic of decoupling the control and management plane into some form of centralization is enough to start a nerd rage brawl. &#10;&lt;p&gt;The second driver, is the need for much more abstraction and scale in the hyper-scale data centers. Public cloud providers need to better align the network with automation and orchestration eco&amp;rsquo;s in the data center. Folks like Amazon, have made it clear they expect vendors to pursue this support or risk some fairly large accounts. Data center orchestration is merely a subset of &lt;a href="https://networkstatic.net/2012/08/why-enterprise-wireless-networks-got-it-right/" target="_blank"&gt;network management&lt;/a&gt; and operational efficiency which has but nothing but a total joke in the networking industry to date. So here is a rough cut at what one option and some research someone could use if their CEO walked in tomorrow and said he was all in for the public cloud and you had to deliver something other than laughter or even sarcasm, well maybe both.&lt;/p&gt;</description></item><item><title>The HP Public Cloud and OpenStack</title><link>https://networkstatic.net/the-hp-public-cloud-and-openstack/</link><pubDate>Tue, 21 Aug 2012 04:48:34 +0000</pubDate><guid>https://networkstatic.net/the-hp-public-cloud-and-openstack/</guid><description>&lt;h2&gt;The HP Public Cloud and OpenStack&lt;/h2&gt;&#10;We have listened to people ramble on about the promise of the cloud and the impact on infrastructure for a few years now, but very rarely has anyone articulated a reasonable blueprint on ramp into this public cloud. SaaS is everywhere, the application was and will continue to be the low hanging fruit, the rest is a bit more difficult. Even the United States Government has a cloud first policy, too bad its not a broadband first policy. To say the public cloud is remotely close to the end game is irresponsible if you gloss over a weak National Internet infrastructure that is strangle-held by the incumbent local exchanges carriers (ILEC) and cable companies only interested in serving what serves themselves. You can't blame them, they answer to stockholders not tax payers. This isn't a rant on the FCC or the horrendous &lt;a href="http://www.broadband.gov/plan/" target="_blank"&gt;lack&lt;/a&gt; of an actionable national broadband roadmap but if we are serious about public cloud we had better get serious about the public (not stakeholder but tax payer owned) infrastructures. Later in the post we will provision an HP OpenStack public cloud instance and in the next post setup what today may qualify as network as a service alpha v0.9 and actually build a hybrid private/public cloud. Sorry about the unicorn addiction, I cant get enough, that one does my taxes, cute little fella.&#10;&lt;h2&gt;Transport to the "public cloud" today&lt;/h2&gt;&#10;&lt;ol class="legacy-numbers"&gt;&#10;&lt;ol&gt;&#10;&#9;&lt;li&gt;Leased lines from your local premise to a cloud provider. At the point you are picking up this sort of cost you are much closer to a colocation arrangement or on a scale that can absorb the cost that would wreck most business cases.&lt;/li&gt;&#10;&#9;&lt;li&gt;Through the Internets. Also lots of problems, but one of those is not necessarily economic. The cost of commodity Internet services in the US has gone from $60-$100 per/1mb to well under $1 per/1mb from some of the more aggressive providers (obviously not AT&amp;amp;T). By leveraging existing infrastructure and  tunneling encapsulations we begin to roadmap what it might mean to deliver networking as a service (NaaS).&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;/ol&gt;&#10;Let's choose path #2 since the cost prohibitive nature of leased lines is less likely and hey I don't need a leased line to Google to check my email.&#10;&lt;h2&gt;Public Cloud Brokerage&lt;/h2&gt;&#10;&lt;p&gt;We have gone from Amazon Web Services and a couple other fledging to a whole hell of a lot more cloud providers in the past year. Part of the allure to the public cloud should be the commoditized nature of the services. Instead of the IT guy worrying about types of storage, compute and network he needs to purchase, negotiating the best rate with the manufacturer and putting together an even remotely accurate TCO, he instead throws a number at the business unit and they cut the check. So we all know that is mostly fairy tale today but at some point it will be more reasonable a scenario. The cost of IaaS in the public cloud is going to most of the time be significantly more than local. If you can manage to pull of an elastic environment to offload peak compute to the cloud it becomes very attractive in todays standards. The classic example is doing payroll at the end of the month, why buy 200% hardware that sits at 50% usage except for one day of the month. Buy half the hardware and burst the peak to a (partner, public, private) cloud rather than buy capacity that is not maximized.&lt;/p&gt;</description></item><item><title>Rackspace OpenStack Installation on a KVM VM</title><link>https://networkstatic.net/rackspace-openstack-installation-on-a-kvm-vm/</link><pubDate>Thu, 16 Aug 2012 04:09:33 +0000</pubDate><guid>https://networkstatic.net/rackspace-openstack-installation-on-a-kvm-vm/</guid><description>&lt;p&gt;&lt;a href="https://networkstatic.net/wp-content/uploads/2012/08/Cloud-Uni3.jpg"&gt;&lt;img class="alignright wp-image-2289" title="Cloud Unicorn" src="https://networkstatic.net/wp-content/uploads/2012/08/Cloud-Uni3-350x304.jpg" alt="" width="270" height="234" /&gt;&lt;/a&gt;&lt;/p&gt;&#10;&lt;p&gt;Rackspace OpenStack Installation on a KVM VM: Big day in the OpenStack world, Rackspace announced it was releasing its Openstack installer image named Alamo v1.0. running on top of KVM, along with Opscode Chef and Rackspace OpenStack cookbooks. This may be the Open Source renaissance we have been needing and forced into by exorbitant profit taking, M&amp;amp;A, takeovers, buyouts, spin-ins, spin-offs, spin-outs, IPOs and greedy margins during times of economic uncertainty. Never fear my young republican, there is profits to be made here on by monetizing open source software, but they will be earned with value, partnerships with customers and risk.&lt;/p&gt;</description></item><item><title>Quantum OpenStack Scripted Python Install</title><link>https://networkstatic.net/quantum-openstack-python-installer/</link><pubDate>Tue, 14 Aug 2012 05:18:48 +0000</pubDate><guid>https://networkstatic.net/quantum-openstack-python-installer/</guid><description>&lt;p&gt;&lt;em&gt;&lt;strong&gt;Update:&lt;/strong&gt;&lt;/em&gt; My latest installation document for Folsom can be found &lt;a href="https://networkstatic.net/openstack-folsom-quantum-devstack-installation-tutorial/"&gt;here&lt;/a&gt;. It&amp;rsquo;s too tough to try and keep up with debugging installers myself so I am just using DevStack in that tutorial. This will not work with OpenStack apt-get repos anymore since the packages have changed to Folsom. Thanks!&lt;/p&gt;</description></item><item><title>Why Enterprise Wireless Networks Got it Right</title><link>https://networkstatic.net/why-enterprise-wireless-networks-got-it-right/</link><pubDate>Sun, 12 Aug 2012 22:33:06 +0000</pubDate><guid>https://networkstatic.net/why-enterprise-wireless-networks-got-it-right/</guid><description>&lt;h2&gt;Why Enterprise Wireless Networks Got it Right&lt;/h2&gt;&#10;&lt;p&gt;I wanted to post some 802.11 wireless usage numbers and device breakdowns. These are two week University usage numbers in August of 2012. This period is right before students return so I wanted a baseline to capture the diff when students 25,000+ students come back with the ever growing amount of 802.11 wireless enabled BYOD hidden in pockets and purses. Apple is 50%+ in all categories other than total traffic by vendor where is is slightly less ~%45, which I would speculate is due to so many of those devices being mobile devices that would likely consume less traffic or more mobile optimized traffic loads. Most of these numbers will likely come close to doubling in the next few weeks has been pretty typical over the past few years.&lt;/p&gt;</description></item><item><title>Building a Windows Image for OpenStack</title><link>https://networkstatic.net/building-a-windows-image-for-openstack/</link><pubDate>Fri, 10 Aug 2012 03:36:20 +0000</pubDate><guid>https://networkstatic.net/building-a-windows-image-for-openstack/</guid><description>&lt;h2&gt;Building a Windows Image for OpenStack&lt;/h2&gt;&#10;Building a Windows Image for OpenStack :  Here is a how-to for building a Windows image to import into OpenStack or a KVM Hypervisor. We need to sysprep the image before we can import it into Glance.&#10;&lt;aside class="legacy-callout"&gt;For a tutorial on getting OpenStack Folsom up and running have a look at &lt;a href="https://networkstatic.net/openstack-folsom-quantum-devstack-installation-tutorial/" target="_blank"&gt;OpenStack Folsom Installation with Devstack Guide&lt;/a&gt; &lt;/aside&gt;&#10;&lt;!--?xml version="1.0" encoding="UTF-8" standalone="no"?--&gt;&#10;&lt;div&gt;Download the Virtio-win binary driver&#10;&lt;a href="http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/" target="_blank"&gt;http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/&lt;/a&gt;&lt;/div&gt;&#10;&lt;h4&gt;System Prep&lt;/h4&gt;&#10;&lt;div&gt;Have the windows install ISO and the VirtIO iso in the same directory that you execute the commands below.&lt;/div&gt;&#10;&lt;div&gt;&lt;/div&gt;&#10;&lt;pre class="brush: bash; gutter: true; first-line: 1; highlight: []; html-script: false"&gt;apt-get install vncviewer kvm qemu-kvm&#10;kvm-img create -f raw windowsr2.img 20G (Create the image file)&#10;kvm -m 2048 -no-reboot -boot order=d -drive file=windowsr2.img,if=virtio,boot=off -drive file=windows-2008r2.iso,media=cdrom,boot=on -drive file=virtio-win-0.1-30.iso,media=cdrom,boot=off -net nic,model=virtio -nographic -vnc :1&#10;vncviewer&lt;/pre&gt;&#10;&lt;div&gt;&lt;/div&gt;&#10;&lt;div&gt;***Note if you add index=x in the command as listed in the OpenStack admin &lt;a href="http://docs.openstack.org/trunk/openstack-compute/admin/content/creating-a-windows-image.html" target="_blank"&gt;guide&lt;/a&gt; it may throw an error like this:&lt;/div&gt;&#10;&lt;div&gt;&lt;!--?xml version="1.0" encoding="UTF-8" standalone="no"?--&gt;root@openstack1:/home/brent# kvm -m 2048 -cdrom windows-2008r2.iso -drive file=windowsr2.img ,if=virtio,boot=on -boot d drive file=virtio-win-0.1-30.iso,index=3,media=cdrom -net nic,model=virtio -net user -nographic -vnc :0&lt;/div&gt;&#10;&lt;div&gt;kvm: -drive file=windowsr2.img: drive with bus=0, unit=0 (index=0) exists***&lt;/div&gt;&#10;&lt;hr /&gt;&#10;&lt;h2&gt;Build the Windows Image for OpenStack&lt;/h2&gt;&#10;Enter 127.0.0.1:1 into the window. :1 = is the screen number after you put in the KVM command. This will spawn a VNC window in which you will install windows.&#10;&lt;div&gt;&lt;a href="https://networkstatic.net/wp-content/uploads/2012/08/Windows-VM2.jpg"&gt;&lt;img class="wp-image-2012 aligncenter" title="Windows Openstack VM" alt="" src="https://networkstatic.net/wp-content/uploads/2012/08/Windows-VM2.jpg" width="513" height="383" /&gt;&lt;/a&gt;&lt;/div&gt;&#10;&lt;div&gt;&lt;strong&gt;Figure 1. &lt;/strong&gt;Next.&lt;/div&gt;&#10;&amp;nbsp;&#10;&lt;div&gt;&lt;/div&gt;&#10;&lt;div&gt;&lt;a href="https://networkstatic.net/wp-content/uploads/2012/08/select-driver1.jpg"&gt;&lt;img class="aligncenter wp-image-2020" title="select-driver" alt="" src="https://networkstatic.net/wp-content/uploads/2012/08/select-driver1.jpg" width="542" height="399" /&gt;&lt;/a&gt;&lt;/div&gt;&#10;&lt;div&gt;&lt;strong&gt;Figure 2. &lt;/strong&gt;I used the WLH-&amp;gt;AMD folder to locate the driver.&lt;/div&gt;&#10;&amp;nbsp;&#10;&lt;div&gt;&lt;/div&gt;&#10;&lt;div&gt;&lt;a href="https://networkstatic.net/wp-content/uploads/2012/08/SCSI4.jpg"&gt;&lt;img class="aligncenter wp-image-2024" title="SCSI" alt="" src="https://networkstatic.net/wp-content/uploads/2012/08/SCSI4.jpg" width="561" height="440" /&gt;&lt;/a&gt;&lt;/div&gt;&#10;&lt;div&gt;&lt;strong&gt;Figure 3. &lt;/strong&gt;Choose the VirtIO SCSI driver which will be the only one listed.&lt;/div&gt;&#10;&amp;nbsp;&#10;&lt;div&gt;&lt;/div&gt;&#10;&lt;div&gt;&lt;a href="https://networkstatic.net/wp-content/uploads/2012/08/20G-img2.jpg"&gt;&lt;img class="aligncenter wp-image-2025" title="20G-img" alt="" src="https://networkstatic.net/wp-content/uploads/2012/08/20G-img2.jpg" width="557" height="443" /&gt;&lt;/a&gt;&lt;/div&gt;&#10;&lt;div&gt;&lt;strong&gt;Figure 4. &lt;/strong&gt;Choose the 20GB image you created with the kvm-img command from the CLI earlier.&lt;/div&gt;&#10;&amp;nbsp;&#10;&lt;div&gt;&lt;a href="https://networkstatic.net/wp-content/uploads/2012/08/Installing.jpg"&gt;&lt;img class="aligncenter wp-image-2017" title="windows openstack image" alt="" src="https://networkstatic.net/wp-content/uploads/2012/08/Installing.jpg" width="570" height="446" /&gt;&lt;/a&gt;&lt;/div&gt;&#10;&lt;div&gt;&lt;strong&gt;Figure 5. &lt;/strong&gt;Windows will install.&lt;/div&gt;&#10;&amp;nbsp;&#10;&lt;div&gt;&lt;/div&gt;&#10;&lt;div&gt;&lt;a href="https://networkstatic.net/wp-content/uploads/2012/08/nic-driver.jpg"&gt;&lt;img class="aligncenter wp-image-2018" title="windows openstack image" alt="" src="https://networkstatic.net/wp-content/uploads/2012/08/nic-driver.jpg" width="574" height="401" /&gt;&lt;/a&gt;&lt;/div&gt;&#10;&lt;div&gt;&lt;strong&gt;Figure 6. &lt;/strong&gt;Under Computer Management -&amp;gt; Device Manager update the drivers to the RedHat Ethernet Adaptor on the virtio ISO mounted.&lt;/div&gt;&#10;&amp;nbsp;&#10;&lt;div&gt;&lt;/div&gt;&#10;&lt;div&gt;&lt;a href="https://networkstatic.net/wp-content/uploads/2012/08/windows-FW.jpg"&gt;&lt;img class="aligncenter wp-image-2019" title="windows openstack image" alt="" src="https://networkstatic.net/wp-content/uploads/2012/08/windows-FW.jpg" width="593" height="512" /&gt;&lt;/a&gt;&lt;/div&gt;&#10;&lt;div&gt;&lt;strong&gt;Figure 7.&lt;/strong&gt; Either disable the firewalls or open TCP 3389 and allow ICMP to test your image. RDC is the only way to reach the host for initial setup.&lt;/div&gt;&#10;&lt;h2&gt;Import the Image into Glance&lt;/h2&gt;&#10;&lt;div&gt;Shutdown the windows machine and import it into Glance.&lt;/div&gt;&#10;&lt;pre class="brush: bash; gutter: true; first-line: 1; highlight: []; html-script: false"&gt;glance add name=Ubuntu-12.04 is_public=true container_format=ovf disk_format=qcow2 &amp;lt; windowsr2.img&#10;#Open TCP 3389 and ICMP in Nova Security&#10;nova secgroup-add-rule default tcp 3389 3389 0.0.0.0/0&#10;nova secgroup-add-rule default icmp -1 -1 0.0.0.0/0&lt;/pre&gt;&#10;&lt;div&gt;&lt;/div&gt;&#10;&lt;div&gt;After the Windows host boots you should be able to ping it. Depending on your build you may need to add a floating IP to the instance and the RDC into the host.&lt;/div&gt;&#10;&lt;div&gt;&lt;/div&gt;&#10;&lt;div&gt;Finis!&lt;/div&gt;</description></item><item><title>XRDP Installation: An Easy Remote Desktop Setup for Linux</title><link>https://networkstatic.net/xrdp-an-easy-remote-desktop-setup-for-your-ubuntu-servers/</link><pubDate>Thu, 09 Aug 2012 03:19:39 +0000</pubDate><guid>https://networkstatic.net/xrdp-an-easy-remote-desktop-setup-for-your-ubuntu-servers/</guid><description>&lt;h2&gt;XRDP Installation: An Easy Remote Desktop Setup for Linux&lt;/h2&gt;&#10;&lt;figure class="legacy-figure"&gt;&lt;img src="https://networkstatic.net/wp-content/uploads/2012/08/xrdp-logo.jpg" alt="XRDP for Linux Remote Access"&gt;&lt;/figure&gt;&#10;&lt;p&gt;XRDP Installation: An Easy Remote Desktop Setup for Linux - Quick tutorial for an installation on Linux (Ubuntu specifically but easily ported) for an easy remote desktop (RDP) setup for Linux. Setting up remote GUI access has always been quite a pain. XRDP is lightweight and really easy to install for a remote administrative GUI desktop. This is a 2 minute setup for a minimal lightdm desktop manager install and setup from a server installed with Ubuntu 12.04 server.&lt;/p&gt;</description></item><item><title>OpenStack Essex Installer Script</title><link>https://networkstatic.net/openstack-essex-installer-script/</link><pubDate>Mon, 06 Aug 2012 02:37:24 +0000</pubDate><guid>https://networkstatic.net/openstack-essex-installer-script/</guid><description>&lt;p&gt;&lt;em&gt;&lt;strong&gt;Update:&lt;/strong&gt;&lt;/em&gt; My latest installation document for Folsom can be found &lt;a href="https://networkstatic.net/openstack-folsom-quantum-devstack-installation-tutorial/"&gt;here&lt;/a&gt;. It&amp;rsquo;s too tough to try and keep up with debugging installers myself so I am just using DevStack in that tutorial. Thanks!&lt;/p&gt;&#10;&lt;p&gt;Here is a Python Script I put together for installing OpenStack Essex on either your laptop in a Virtualbox VM running Qemu or on a standalone server/box for more of a production like environment using KVM. I recommend using a script install to get your feet wet and then do manual installs to understand the components. Then come back to scripts. Openstack has so many pieces and parts right now the only way to get the same install every time is by scripting it. Devstack has some really impressive scripts but this is a much more simple one as I needed something nice and linear to give to some friends. The installer will take care of it itself if it has two Nics (1 can be fake in a VM), Internet access and the right environmentals. Using QEMU in a nested hypervisor performance is beyond terrible so be prepared to be frustrated unless you want anything other than understanding how to install OpenStack. I just use this to quickly get a box up, it is not something I support, recommend etc other than getting to learn OpenStack.&lt;/p&gt;</description></item><item><title>Thoughts from the PacketPusher Show 112 SDN's SDN’s Potential as a Displacement Technology</title><link>https://networkstatic.net/thoughts-from-the-packetpusher-show-112-sdns-sdns-potential-as-a-displacement-technology/</link><pubDate>Wed, 01 Aug 2012 22:20:42 +0000</pubDate><guid>https://networkstatic.net/thoughts-from-the-packetpusher-show-112-sdns-sdns-potential-as-a-displacement-technology/</guid><description>&lt;p&gt;If anyone has not listened to the PackPusher &lt;a href="http://packetpushers.net/show-112-sdns-potential-as-a-displacement-technology-with-jeff-doyle-bill-koss/" target="_blank"&gt;Show 112 – SDN’s Potential as a Displacement Technology With Jeff Doyle &amp;amp; Bill&lt;/a&gt; it is a must listen. A comment made by Greg who has rationalized and articulated the SDN conversation as well or better than anyone so far got me thinking. It was something I had never heard anyone else say except for vendors.&lt;/p&gt;</description></item><item><title>Floodlight OpenFlow Controller GUI Applet</title><link>https://networkstatic.net/floodlight-openflow-controller-gui-applet/</link><pubDate>Sat, 28 Jul 2012 19:56:47 +0000</pubDate><guid>https://networkstatic.net/floodlight-openflow-controller-gui-applet/</guid><description>&lt;h2&gt;Floodlight OpenFlow Controller GUI Applet&lt;/h2&gt;&#10;&lt;p&gt;&lt;/a&gt;There is a new FloodLight OpenFlow SDN controller GUI out from a Marist College and IBM research group/internship. I am guessing it is the same IBM researcher that developed the &lt;a href="https://networkstatic.net/2012/07/floodlight-gui-topology-addition/" target="_blank"&gt;FloodLight web UI&lt;/a&gt;. This applet allows one to instantiate a flow from the GUI along with a couple of other bells and whistles. It is great to see the public/private partnership. Kudos to both Marist and IBM for the contribution to the community.&lt;/p&gt;</description></item><item><title>Why Community Counts</title><link>https://networkstatic.net/why-community-counts/</link><pubDate>Wed, 25 Jul 2012 06:19:17 +0000</pubDate><guid>https://networkstatic.net/why-community-counts/</guid><description>&lt;p&gt;&lt;a href="https://networkstatic.net/wp-content/uploads/2012/07/nervous.jpeg" rel="attachment wp-att-1864"&gt;&lt;img class="alignright size-full wp-image-1864" title="nervous" src="https://networkstatic.net/wp-content/uploads/2012/07/nervous.jpeg" alt="" width="161" height="152" /&gt;&lt;/a&gt;&lt;/p&gt;&#10;&lt;p&gt; &lt;/p&gt;&#10;&lt;p&gt;I was graciously invited to join some of the best in the business which each of the folks rounding out my top 5 technologist hero list. The panel included &lt;a href="http://blog.fosketts.net/" target="_blank"&gt;Stephen Foskett&lt;/a&gt;, &lt;a href="http://nerdtwilight.wordpress.com/" target="_blank"&gt;Brad Casemore&lt;/a&gt;, &lt;a href="http://blog.ioshints.info/" target="_blank"&gt;Ivan Pepelnjak&lt;/a&gt; and &lt;a href="http://etherealmind.com/" target="_blank"&gt;Greg Ferro&lt;/a&gt; to join &lt;a href="http://blogs.cisco.com/tag/omar-sultan/" target="_blank"&gt;Omar Sultan&lt;/a&gt; from Cisco to discuss the Cisco SDN strategies and what problems it may&lt;a href="https://networkstatic.net/2012/05/sdn-business-cases/" target="_blank"&gt; solve&lt;/a&gt; someday if the community makes it so. I managed to spill a drink in my lap right as I was introduced and I am pretty sure I forgot my name for a second.&lt;/p&gt;</description></item><item><title>Nicira Acquisition by VMWare Winners and Losers</title><link>https://networkstatic.net/nicira-acquisition-by-vmware-winners-and-losers/</link><pubDate>Tue, 24 Jul 2012 03:10:29 +0000</pubDate><guid>https://networkstatic.net/nicira-acquisition-by-vmware-winners-and-losers/</guid><description>&lt;p&gt;&lt;a href="https://networkstatic.net/wp-content/uploads/2012/07/Ghetto-Lisa.jpg" rel="attachment wp-att-1862"&gt;&lt;img class="alignright size-full wp-image-1862" title="Ghetto-Lisa" src="https://networkstatic.net/wp-content/uploads/2012/07/Ghetto-Lisa.jpg" alt="" width="190" height="190" /&gt;&lt;/a&gt; VMware acquired Nacira today. They were one of the two (not including Embrane) venture cap groups that came out of the of Stanford group that developed among other things the OpenFlow and much larger the concepts around making Software Defined Networks (SDN) a potential reality. They open sourced and upstreamed Open vSwitch, two big contributions. I hope this frees up some millionaires now to focus all of their time on OVS and community :)&lt;/p&gt;</description></item><item><title>How to Build an SDN Lab without Needing OpenFlow Hardware</title><link>https://networkstatic.net/how-to-build-an-sdn-lab-without-needing-openflow-hardware/</link><pubDate>Wed, 18 Jul 2012 05:43:04 +0000</pubDate><guid>https://networkstatic.net/how-to-build-an-sdn-lab-without-needing-openflow-hardware/</guid><description>&lt;h2&gt;How to Build an SDN Lab without Needing OpenFlow Hardware&lt;/h2&gt;&#10;&lt;aside class="legacy-callout"&gt;I no longer use much in this post. For a current lab setup please see &lt;a href="https://networkstatic.net/opendaylight-openstack-integration-devstack-fedora-20/"&gt;OpenDaylight OpenStack Integration with DevStack on Fedora&lt;/a&gt; &lt;/aside&gt;&#10;&lt;p&gt;How do you build a networking lab without networking equipment? Yet another plus in the column of open software driven networks. Proofing and prototyping networks today are often done with things like NETFPGA or expensive vendor manufactured hardware. Since we are beginning to build primitives, APIs and abstraction layers the value of what the software development community has had for two decades is becoming obvious to networking.&lt;/p&gt;</description></item><item><title>Configuring an OpenFlow POX SDN Controller and HP Switches</title><link>https://networkstatic.net/configuring-an-openflow-pox-sdn-controller-and-hp-switches/</link><pubDate>Wed, 18 Jul 2012 04:46:10 +0000</pubDate><guid>https://networkstatic.net/configuring-an-openflow-pox-sdn-controller-and-hp-switches/</guid><description>&lt;h2&gt;Configuring an OpenFlow POX SDN Controller and HP Switches&lt;/h2&gt;&#10;&lt;hr&gt;&#10;There is an updated post with the newest HP OpenFlow firmware that can be found at: &lt;a href="https://networkstatic.net/configure-an-hp-openflow-switch-for-floodlight/"&gt;Configure an HP OpenFlow Switch for Floodlight&lt;/a&gt;&#10;&lt;hr&gt;&#10;Configuring an OpenFlow POX SDN Controller and HP Switches: HP has been supporting OpenFlow v1.0 with general availability longer than anyone in the industry. While there are limitations, just as most vendors will have as we start exploring exposing and/or decoupling control planes. Installing the SDN / OpenFlow controller to attach to the HP switch is very simple using open source controllers like POX and &lt;a href="http://floodlight.openflowhub.org/" target="_blank"&gt;FloodLight&lt;/a&gt;. Specific limitations revolve around attempting to modify multiple headers in the OFAction function. This is likely a TCAM width limitation.&#10;&lt;p&gt;POX is a Python based OpenFlow Controller developed by Murphy McCauley at UC Berkeley. POX is great for fast development proofing, along with being platform independent by virtue of being Python based. Mre information can be found &lt;a href="http://www.noxrepo.org/pox/about-pox/" target="_blank"&gt;here&lt;/a&gt;. I highly recommend it over NOX for learning and prototyping since Python is a more abstracted language unless you need to manage hardware resources for performance. Also the development seems to be more focused on POX. Murphy has a nice set of modules to load different features. He has some new ones in the pipe that will help with experimentation for people to get more comfortable with SDN. I really like it for terrible programmers like myself to have an interpreted option to tweak or add modules to.&lt;/p&gt;</description></item><item><title>SDN APIs- I Think I Have Seen This Movie Before</title><link>https://networkstatic.net/sdn-apis-this-all-feels-pretty-familair/</link><pubDate>Mon, 09 Jul 2012 04:08:42 +0000</pubDate><guid>https://networkstatic.net/sdn-apis-this-all-feels-pretty-familair/</guid><description>&lt;h2&gt;SDN APIs- I Think I Have Seen This Movie Before:&lt;/h2&gt;&#10;&lt;a href="https://networkstatic.net/wp-content/uploads/2012/07/old-movie1.jpg"&gt;&lt;img class="alignright size-full wp-image-1869" title="SDN old movie" alt="" src="https://networkstatic.net/wp-content/uploads/2012/07/old-movie1.jpg" width="331" height="293" /&gt;&lt;/a&gt; To see the future of SDN and arguably the future of networks, the roadmap is in our rear-view mirror. Like with most things the past holds the clues to the future and computing cycles fit that mold well. The Northbound API is starting to get some attention as there has been recent milestones in announcements regarding SDN support.&#10;&lt;p&gt;There have been some new SDN products and support being disclosed, the biggest coming last month from Cisco with it&amp;rsquo;s onePK announcement which implies there will be SDN support in all future product lines under onePK(OpenFlow v1.0). Roy Chua over at SDN Central had a great post summarization some of the infant APIs in existence today and made the point, &amp;ldquo;In the ensuing competition between the different APIs, we will see true evolution towards really useful NBAPIs. The alternative, if we sit around and debate in committees, is stagnation and irrelevancy&amp;rdquo; &lt;a href="http://www.sdncentral.com/sdn-blog/openflow-northbound-api-olympics/2012/07/" target="_blank"&gt;OpenFlow Northbound API – A New Olympic Sport&lt;/a&gt;. When we (the networking community) are trailing the rest of the computing world after a decade of proprietary hardware, software and APIs you don&amp;rsquo;t need to be a psychic to take a good guess at what the future holds because I think we have seen this movie before, it&amp;rsquo;s just a little bit different this time around.&lt;/p&gt;</description></item><item><title>My Top 10 Essential Wordpress Plugins</title><link>https://networkstatic.net/my-top-10-essential-wordpress-plugins/</link><pubDate>Mon, 09 Jul 2012 03:05:59 +0000</pubDate><guid>https://networkstatic.net/my-top-10-essential-wordpress-plugins/</guid><description>&lt;p&gt;My Top 10 Essential Wordpress Plugins: I jotted down my Top 10 plugins that I think are essential or aesthetically nice. It can be a bit confusing when you first start your own Wordpress blog to figure out what is needed. Click on the screenshots for a link to the plugin site on Wordpress.org. Hope these help someone starting out to navigate the essentials. Thanks to the creators for taking the time especially the ones just giving to the community, in no particular order here they are.&lt;/p&gt;</description></item><item><title>SDN Floodlight Controller GUI Topology Video and Install</title><link>https://networkstatic.net/floodlight-gui-topology-addition/</link><pubDate>Sun, 08 Jul 2012 17:55:53 +0000</pubDate><guid>https://networkstatic.net/floodlight-gui-topology-addition/</guid><description>&lt;p&gt;SDN Floodlight Controller GUI Topology Video and Install: There is a new topology component to the OpenFlow Controller FloodLight. The page is located in the GUI Web UI under the &amp;ldquo;Topology&amp;rdquo; menu and the balls on the screen represent hosts. I haven&amp;rsquo;t checked the listserv to see where they are going with it but it&amp;rsquo;s all in the right direction and actually reminds me of the OpenStack dev history video made with Gource the visualization software. The OpenStack video is the future of computing and network SDN resource visualization if done in realtime and made useful. Replace developer with Tenant and you have some sparkle. Pretty &amp;ldquo;Minority Report&amp;quot;esque but it wouldn&amp;rsquo;t be the first time Science Fiction predicted the future.&lt;/p&gt;</description></item><item><title>Artboard Vector Drawing App Review</title><link>https://networkstatic.net/artboard-vector-drawing-app-review/</link><pubDate>Sun, 08 Jul 2012 04:29:31 +0000</pubDate><guid>https://networkstatic.net/artboard-vector-drawing-app-review/</guid><description>&lt;p&gt;I tried a new vector drawing app called &lt;a href="http://itunes.apple.com/us/app/artboard/id414551588?mt=12" target="_blank"&gt;Artboard&lt;/a&gt;. So far I am pretty pleased with it. Clean UI and pretty intuitive. What I like the most is it has a nice amount of clip art to go with it. As a guy with zero artistic skills I rely on software to fix that for me. I have been using PowerPoint quite a bit for drawings but it can only go so far. I will be testing some other apps and will post reviews as I go.&lt;/p&gt;</description></item><item><title>New IETF SDN Drafts</title><link>https://networkstatic.net/new-ietf-sdn-drafts/</link><pubDate>Fri, 06 Jul 2012 06:34:44 +0000</pubDate><guid>https://networkstatic.net/new-ietf-sdn-drafts/</guid><description>&lt;h2&gt;New IETF SDN Drafts&lt;/h2&gt;&#10;New IETF SDN Drafts: A Service Provider SDN IETF Draft: There are four new drafts submitted to the IETF in the past few days. These are all informational drafts and a "work in progress" for the 6 month period after submission. It would be reasonable to expect vendors to seek some disruption to be triggered by having multiple standards bodies get involved to have favorable standards fall in their direction. The most recent split is  TRILL and SPB, between the IEEE and IETF slowed that process to a snails pace. IETF, the ONF and the RETF are all either doing or beginning the process of weighing in on standards. Each have unique properties, for example the ONF (Open Networking Foundation) does not have any networking device vendors on it's voting board. Regardless of where these standards and definitions come from the results need to remain open in as many sense of the word possible for the industry to take a run at some efficient and smart abstraction.&#10;&lt;ol class="legacy-numbers"&gt;&#10;&lt;h2&gt;Cisco, MPLS and OpenFlow: Defense or Offense?&lt;/h2&gt;&#10;&lt;ol&gt;&#10;&#9;&lt;li&gt;This was submitted by Jan Medved of Cisco who is the chair of the ONF Hybrid Working Group.&lt;/li&gt;&#10;&#9;&lt;li&gt;The management (northbound) application is the UI from which the operator will provision the pseudowire circuit.&lt;/li&gt;&#10;&#9;&lt;li&gt;The draft does not include how the other than a traditional push and pop of the transport label on ingress and egress from the LSP.&lt;/li&gt;&#10;&#9;&lt;li&gt;There is an OAM engine on the head and tail of the circuit. The tail engine detects the failure while the headend provisions the failover over LSP.&lt;/li&gt;&#10;&#9;&lt;li&gt;The OpenFlow switch has one dedicated flow table and one dedicated table-group table. The table-group table is typically thought to be used for OAM, BFD, bcast and mcast.&lt;/li&gt;&#10;&#9;&lt;li&gt;The OF switch has to support matching on input port and the label stack mpls label and bottom of stack label.&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;/ol&gt;&#10;&lt;h2&gt;Use Cases for ALTO with SDN (Huawei and Telefonica)&lt;/h2&gt;&#10;Application-Layer Traffic Optimization (ALTO) is the marrying application awareness and the underlying substrate which is one of the primary use cases of SDN in NSPs and CDNs. This reads like a nortbound application that will orchestrate controller domains with coarse aggregate data through extensions. A signaling protocol is not identified in the draft. That signalling would be the Northbound controller interaction to the ALTO server. Some use cases and dependencies for path selection identified are QOS metrics, Bandwidth on Demand, bandwidth availability, delay, CDN ranking and cost maps. I love the idea of working in a brokerage of transport costs in maybe even creating a bandwidth commodities market.&#10;&lt;h2&gt;SDNi: A Message Exchange Protocol for SDN (Huawei and Telefonica)&lt;/h2&gt;&#10;SDNi is a protocol proposed for the interface between Software Defined Networking (SDN) domains. An SDN domain has been shaping up to be an SDN subset of the overall network that is made up of a collection of SDN domains. It is probably similar to the reasons we carve failure domains today along with an natural migration path potentially from existing to SDN. OpenFlow or is a north-south transaction from OF enabled hardware making up the data plane(encompassing forwarding) to the controller containing the decoupled control plane. SDNi is an east-west protocol that interconnects controller and the exchange reach ability information.&#10;&lt;p&gt;A single flow can be extended across SDN domains with one controller lookup. This would de-duplicate multiple policy (firewall, PBR, load balancing etc) classification as a flow traverses multiple SDN domains. Sounds an awful lot like an label switch path (LSP) forwarding equivalency class (FEC) on ingress into an label edge router (LER) MPLS domain and choose a path if multiple paths exist. Ok that was too many acronyms. It references that reachability (hosts maybe even presumably even mac) could be exchanged with BGP or SIP over SCTP extensions. It explicitly states that it is to exchange information under the same operator implying it is out of scope to be AS-to-AS peering. This was submitted by Huawei and Telefonica.&lt;/p&gt;</description></item><item><title>TCAMs, SDN/OpenFlow and Why We Care</title><link>https://networkstatic.net/tcams-sdnopenflow-and-why-we-care/</link><pubDate>Mon, 02 Jul 2012 23:56:46 +0000</pubDate><guid>https://networkstatic.net/tcams-sdnopenflow-and-why-we-care/</guid><description>&lt;p&gt;I recently meet Roy Chua and Matt Palmer over at &lt;a href="http://www.sdncentral.com" target="_blank"&gt;SDN Central&lt;/a&gt; a few weeks ago. They have put together a really nice site dedicated to Software Defined Networks (SDN) and contributing to the community. They are really seasoned IT pros that have great vision.&lt;/p&gt;</description></item><item><title>Configuring VXLAN and GRE Tunnels on OpenvSwitch</title><link>https://networkstatic.net/configuring-vxlan-and-gre-tunnels-on-openvswitch/</link><pubDate>Mon, 02 Jul 2012 06:52:13 +0000</pubDate><guid>https://networkstatic.net/configuring-vxlan-and-gre-tunnels-on-openvswitch/</guid><description>&lt;h2&gt;Configuring VXLan and GRE tunnels on OpenvSwitch&lt;/h2&gt;&#10;&lt;aside class="legacy-callout"&gt;&lt;strong&gt;Update: VXLan Encapsulation &lt;/strong&gt;VXLan is now upstreamed into the Master build. It is worth mentioning that is the VXLAN framing only, not the Multicast control plane functionality. So basically no need to pull from the fork anymore but pull directly from the Open vSwitch Master or 1.10+ tarball (approximately). &lt;/aside&gt;&#10;I have done a couple of GRE tunnel how-tos using OpenvSwitch (OVS). I had been itching to give VXLan a spin in OVS so why not ferret out someones tree on GitHub. I believe VXLan is still scheduled to officially release soon in OpenvSwitch. So here are the steps for installing, configuring tunnels on OpenvSwitch with VXLan and GRE encapsulations. At the end we will compare some of the protocols with difference MTU sizes. The results were interesting I think (for a nerd). We will be installing and then configure both GRE and VXLan encapsulated tunnels using Open vSwitch.&#10;&lt;p&gt;I like seeing some collaboration of really smart people from different companies as displayed in the GPL below.&lt;/p&gt;</description></item><item><title>The Birth of an SDN Unicorn - Early OpenFlow Meeting Notes</title><link>https://networkstatic.net/the-birth-unicorn-early-openflow-meeting-notes/</link><pubDate>Thu, 21 Jun 2012 20:06:08 +0000</pubDate><guid>https://networkstatic.net/the-birth-unicorn-early-openflow-meeting-notes/</guid><description>&lt;h2&gt;The Birth of an SDN Unicorn - Early OpenFlow Meeting Notes&lt;/h2&gt;&#10;&lt;p&gt;The Birth of an SDN Unicorn - Early OpenFlow Meeting Notes: I wanted to share something I found very fun to read. These are the OpenFlow notes from the working group meetings at Stanford from 2010. The conversations are fascinating and the notes read like a book.&lt;/p&gt;</description></item><item><title>It's OK to Like OpenFlow</title><link>https://networkstatic.net/its-ok-to-like-openflow/</link><pubDate>Tue, 19 Jun 2012 04:59:25 +0000</pubDate><guid>https://networkstatic.net/its-ok-to-like-openflow/</guid><description>&lt;p&gt; &lt;/p&gt;&#10;&lt;p&gt;A trend is happening, seems like a recurring theme from vendors or pundits the past year has been to point out SDN is much larger than just OpenFlow. My question is, who thinks that SDN is exclusively OpenFlow? I am looking for the person who thinks this so I can understand the fuss. What is SDN? We already have SDN management for automation from HP with HP Network Node Manager (NNM), from via Dell Advanced Infrastructure Manager (AIM) and Cisco&amp;rsquo;s slew of Cloud Automation packs and so on. We now have proprietary extensibility from Juniper, Cisco, Arista etc. So whats all the fuss? Clearly we already have everything we need.&lt;/p&gt;</description></item><item><title>Comparing Vmware vs. OpenStack</title><link>https://networkstatic.net/comparing-vmware-vs-openstack/</link><pubDate>Tue, 19 Jun 2012 01:50:19 +0000</pubDate><guid>https://networkstatic.net/comparing-vmware-vs-openstack/</guid><description>&lt;h2&gt;Comparing Vmware vs. OpenStack&lt;/h2&gt;&#10;Comparing Vmware vs. OpenStack: I ran into a great slide deck Mirantis comparing VMware and OpenStack (Essex) and wanted to share it. I am not affiliated with Mirantis. I started to research a side by side comparison between OpenStack and VMware. The slide deck is really good and deserves more than a Tweet. VMware is a good tool for many enterprises, but with that comes at a financial premium. I tend to get worried if systems folks need too many tools in order to keep the lights on.&#10;&lt;hr&gt;&#10;&lt;ul&gt;&#10;&#9;&lt;li&gt;VMware solves for the enterprise.&lt;/li&gt;&#10;&#9;&lt;li&gt;OpenStack solves for the cloud ￼￼￼￼￼￼￼￼￼￼￼Both technology and philosophy differ .&lt;/li&gt;&#10;&#9;&lt;li&gt;Not an apples-to-apples comparison Select features can be compared side by side/&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h2&gt;VMware and OpenStack Compared&lt;/h2&gt;&#10;&lt;figure class="legacy-figure"&gt;&lt;img src="https://networkstatic.net/wp-content/uploads/2012/06/VMware-v-ostack.jpg" alt=""&gt;&lt;/figure&gt;&#10;&lt;p&gt;&lt;strong&gt;Figure 1.&lt;/strong&gt; Summary slide&lt;/p&gt;</description></item><item><title>Cisco onePK Announcement, big Surprise or About Time?</title><link>https://networkstatic.net/cisco-onepk-about-time/</link><pubDate>Fri, 15 Jun 2012 22:52:59 +0000</pubDate><guid>https://networkstatic.net/cisco-onepk-about-time/</guid><description>&lt;p&gt;This week Cisco announced their new strategy for engaging software defined networks (SDN) with the announcement of the the onePK (Cisco One Platform Kit). I think we saw what I think most of us &lt;a href="https://networkstatic.net/2012/06/cisco-networkers-live-clus-or-whatever-we-call-it-now-sdn-predictions/" target="_blank"&gt;expected&lt;/a&gt;. I didn&amp;rsquo;t expect an DK, so that was a pleasant surprise. I know many folks especially from R&amp;amp;E have wanted that visibility into the planes of operation of their purchased networking gear for many years now so that is a direct result of years of consumer demand that got too big to ignore. For most of us the Cisco DK is as much of a game changer as the JunOS SDK was couple years back, not much except for the corner cases. This is a major step into opening the network for integration at some level into the rest of the world of computing as opposed to the black box we have become in IT.&lt;/p&gt;</description></item><item><title>Getting Started OpenFlow OpenvSwitch Tutorial Lab : Setup</title><link>https://networkstatic.net/openflow-openvswitch-lab/</link><pubDate>Fri, 15 Jun 2012 05:50:49 +0000</pubDate><guid>https://networkstatic.net/openflow-openvswitch-lab/</guid><description>&lt;h2&gt;Getting Started OpenFlow OpenvSwitch Tutorial Lab : Setup&lt;/h2&gt;&#10;&lt;aside class="legacy-callout"&gt;For a more up to date tutorial as anything more then 6 months old is outdated in the world of SDN Please see:&#10;&lt;a href="https://networkstatic.net/opendaylight-openstack-integration-devstack-fedora-20/"&gt;OpenDaylight OpenStack Integration with DevStack on Fedora 20&lt;/a&gt;&lt;/aside&gt;&#10;&lt;p&gt;I wrote a Python OpenFlow installation app to automate an OpenFlow KVM and Open vSwitch setup found at:&#10;&lt;a href="https://networkstatic.net/openflow-openvswitch-and-kvm-sdn-lab-installation-app/" target="_blank" rel="noopener noreferrer"&gt;OpenFlow, OpenvSwitch and KVM SDN Lab Installation App&lt;/a&gt;&lt;/p&gt;</description></item><item><title>OpenFlow Starter Tutorial Lab #3</title><link>https://networkstatic.net/openflow-tutorial-lab-3/</link><pubDate>Fri, 15 Jun 2012 05:47:44 +0000</pubDate><guid>https://networkstatic.net/openflow-tutorial-lab-3/</guid><description>&lt;h2&gt;OpenFlow Starter Tutorial Lab #3&lt;/h2&gt;&#10;&lt;aside class="legacy-callout"&gt;For a more up to date tutorial as anything more then 6 months old is outdated in the world of SDN Please see:&#10;&lt;a href="https://networkstatic.net/opendaylight-openstack-integration-devstack-fedora-20/"&gt;OpenDaylight OpenStack Integration with DevStack on Fedora 20&lt;/a&gt;&lt;/aside&gt;&#10;&lt;p&gt;OpenFlow Starter Tutorial Lab #3 : Move individual flows&lt;/p&gt;</description></item><item><title>OpenFlow Starter Tutorial Lab #2</title><link>https://networkstatic.net/openflow-tutorial-lab-2/</link><pubDate>Fri, 15 Jun 2012 05:47:04 +0000</pubDate><guid>https://networkstatic.net/openflow-tutorial-lab-2/</guid><description>&lt;h2&gt;OpenFlow Starter Tutorial Lab #2&lt;/h2&gt;&#10;&lt;aside class="legacy-callout"&gt;For a more up to date tutorial as anything more then 6 months old is outdated in the world of SDN Please see:&#10;&lt;a href="https://networkstatic.net/opendaylight-openstack-integration-devstack-fedora-20/"&gt;OpenDaylight OpenStack Integration with DevStack on Fedora 20&lt;/a&gt;&lt;/aside&gt;&#10;&lt;p&gt;OpenFlow Starter Tutorial Lab #2 :This lab is to restrict two hosts to only talk to each other with source based forwarding using the static flow pusher RESTful API. You can add any field you want to make the forwarding decisions on. Remember to name the flows with unique names or else you will overwrite previously instantiated flows. Previous posts in the series have setup included. Links to those at the bottom of this post.&lt;/p&gt;</description></item><item><title>OpenFlow Starter Tutorial Lab #1</title><link>https://networkstatic.net/openflow-starter-tutorial-lab-1/</link><pubDate>Fri, 15 Jun 2012 05:44:57 +0000</pubDate><guid>https://networkstatic.net/openflow-starter-tutorial-lab-1/</guid><description>&lt;h2&gt;OpenFlow Starter Tutorial Lab #1&lt;/h2&gt;&#10;&lt;ol class="legacy-numbers"&gt;&#10;&lt;aside class="legacy-callout"&gt;For a more up to date tutorial as anything more then 6 months old is outdated in the world of SDN Please see:&#10;&lt;a href="https://networkstatic.net/opendaylight-openstack-integration-devstack-fedora-20/"&gt;OpenDaylight OpenStack Integration with DevStack on Fedora 20&lt;/a&gt;&lt;/aside&gt;&#10;&lt;ol&gt;&#10;&#9;&lt;li&gt;Lab 1: Add static destination MAC addresses to each node. Match: DstMac: , Action:DstPortX&lt;/li&gt;&#10;&#9;&lt;li&gt;Lab 2: Add static flow with src mac address match with the associated action to an output port e.g. Match:SrcMac Action:DstPortY.&lt;/li&gt;&#10;&#9;&lt;li&gt;Lab 3: Add a bad static flow for one of the hosts and watch ICMP replies from the gateway on the board port come back through tcpdump. Match:DstMac, Action:PortZ&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;/ol&gt;&#10;&lt;hr&gt;&#10;&lt;a href="https://networkstatic.net/wp-content/uploads/2012/06/Topology-overview.jpg"&gt;&lt;img class="wp-image-1087 aligncenter" title="Openflow lab tutorial openvswitch" alt="" src="https://networkstatic.net/wp-content/uploads/2012/06/Topology-overview.jpg" width="482" height="265" /&gt;&lt;/a&gt;&#10;&lt;strong&gt;Figure 1.&lt;/strong&gt; The topology for the lab simulates in software the same capabilities you can get in hardware thanks to OpenvSwitch.&#10;This setup allows you to add and remove as many matches into the API calls and tinker with them to get a feel once you nail down the basics. Then you can write the next "killer app" get rich and make it rain, but first lets figure out what is going on here.&#10;&lt;h2&gt;RESTful/JSON API&lt;/h2&gt;&#10;The API is documented very well (that is huge and differentiating IMO) @&#10;&lt;pre class="code-sample"&gt;&lt;code&gt;&lt;a href="http://www.openflowhub.org/display/floodlightcontroller/Proposed+New+API"&gt;http://www.openflowhub.org/display/floodlightcontroller/Proposed+New+API&lt;/a&gt;&lt;/code&gt;&lt;/pre&gt;&#10;RESTful APIs are very important in my opinion if there is to be a transition of any kind to make it human readable for at the least troubleshooting or easy field parsing programmaticlaly for those of us who are only willing to muck our way through interpreted languages. Huge fan of what they have done here with their API and I expect the industry to follow this.&#10;&lt;h2&gt;Forwarding Table in OpenvSwitch&lt;/h2&gt;&#10;Based on 'ovs-appctl fdb/show br-int' build your cheat sheet so see what port your host VMs are on inside of OpenvSwitch. If you do not see your entry it has like timed out ~300 seconds or so, refresh the entry by simply pinging the host VM from the vSwitch. These tables are the same as your CAM tables doing key/value exact matches for L2 mac address lookups and LPM (Longest Prefix Match) in todays network systems only in software.&#10;&lt;pre class="code-sample"&gt;&lt;code&gt;$ovs-appctl fdb/show br-int&#10;port  VLAN  MAC                Age&#10;1     0  00:23:69:62:26:09   58&#10;6     0  00:11:22:cc:cc:10    7&#10;5     0  00:00:00:00:cc:10    4&#10;0     0  5c:26:0a:5a:c8:b2    3&#10;7     0  22:22:22:00:cc:10    3&lt;/code&gt;&lt;/pre&gt;&#10;MAC tables for this lab are as follows. Yours will likely be different based on the assignment by the vSwitch. The mac addresses are specifed by the KVM boot but anything can be used as long they are unique.&#10;&lt;p&gt;The DPID datapath ID is required to send the API calls. You need to find the one on your vSwitch. Lots of ways to find it either through the Floodlight console or APIs or from the ovs-ofctl show &amp;lt;bridge name&amp;gt; listed below. It is basically a few bytes prepended on your Nics MAC address).&lt;/p&gt;</description></item><item><title>Cisco Networkers Live CLUS or whatever we call it now SDN Predictions</title><link>https://networkstatic.net/cisco-networkers-live-clus-or-whatever-we-call-it-now-sdn-predictions/</link><pubDate>Mon, 11 Jun 2012 01:23:21 +0000</pubDate><guid>https://networkstatic.net/cisco-networkers-live-clus-or-whatever-we-call-it-now-sdn-predictions/</guid><description>&lt;p&gt;I was emailing with my buddy Roy at SDN Central &lt;a title="http://www.sdncentral.com/" href="http://www.sdncentral.com/" target="_blank"&gt;&lt;a href="http://www.sdncentral.com"&gt;http://www.sdncentral.com&lt;/a&gt;&lt;/a&gt;/ about it would be fun to see a poll for people to guess what Cisco will do with their big SDN announcement. I jotted down four options that are all in the realm of possibility, or at least the same realm of if SDN makes sense and will adopt. Let&amp;rsquo;s say solar-system or galaxy.&lt;/p&gt;</description></item><item><title>The Northbound API- A Big Little Problem</title><link>https://networkstatic.net/the-northbound-api-2/</link><pubDate>Sun, 10 Jun 2012 03:27:11 +0000</pubDate><guid>https://networkstatic.net/the-northbound-api-2/</guid><description>&lt;p&gt;The Northbound API- A Big Little Problem : What is a Northbound API (Application Programming Interface) in SDN? The Northbound API is available on a SDN controller that allows for applications to interact with the controller. The controller in turn, interacts with the network hardware through the OpenFlow protocol to manipulate the flow tables and send instructions to the underlying network substrate. I am going to call that the Southbound API. The controller appears to be the glue at the center of the SDN paradigm. While crucial in the incubation period we are in, I think in the long run it will be just another resource pool we scale up and out, similar to what we have in the x86 compute construct. The following are three fundamentals if I were to rank what I need from an OpenFlow controller.&lt;/p&gt;</description></item><item><title>The Best MPLS Lecture on the Net</title><link>https://networkstatic.net/the-best-mpls-lecture-on-the-net/</link><pubDate>Sat, 02 Jun 2012 08:13:34 +0000</pubDate><guid>https://networkstatic.net/the-best-mpls-lecture-on-the-net/</guid><description>&lt;h2&gt;The Best MPLS Lecture on the Net&lt;/h2&gt;&#10;&lt;p&gt;The Best MPLS Lecture on the Net: The title says it all. Professor Karandikar gives two amazing lectures on MPLS and MPLS-TE that most engineers should hope to know cold. I watch it probably once every few months. Not saying much for my memory these days. It is an amazing amount of material delivered very precisely. Great stuff!&lt;/p&gt;</description></item><item><title>Ethernet Switch Fabric Cards</title><link>https://networkstatic.net/ethernet-switch-fabric-cards/</link><pubDate>Fri, 01 Jun 2012 06:23:34 +0000</pubDate><guid>https://networkstatic.net/ethernet-switch-fabric-cards/</guid><description>&lt;p&gt;I was working with a buddy today about ethernet switch fabric cards in the nexus 7000 and not doing a very good job at explaining it, so I figured I would draw some pictures. The conversation was around how adding more fabric cards increases the bandwidth. I think some, myself included growing up on Catalyst 6500&amp;rsquo;s got accustomed to a single stage architecture which in the case of the ASR 9000 and similarly the  Sup 7200 and newer, have the switch fabric living on the route processor (RP), routing engine (RE juniper) or supervisor (sup Cat 6500). Chip, ASIC, fabric hardware developers are tackling the same problems in silicon design that we as network engineers/architects tackle  in macro engineering network design. Its all modularity the building blocks of scale and abstraction.&lt;/p&gt;</description></item><item><title>NOX OpenFlow Controller Install on Ubuntu 12.04</title><link>https://networkstatic.net/nox-openflow-controller-install-on-ubuntu-12-04-precise-lts/</link><pubDate>Thu, 31 May 2012 06:09:09 +0000</pubDate><guid>https://networkstatic.net/nox-openflow-controller-install-on-ubuntu-12-04-precise-lts/</guid><description>&lt;p&gt;&lt;a href="http://www.youtube.com/watch?v=RQzFgFjPlD8"&gt;http://www.youtube.com/watch?v=RQzFgFjPlD8&lt;/a&gt;&lt;/p&gt;&#10;&lt;p&gt;Screencast w/o audio. I think it&amp;rsquo;s quick and self explanatory.&lt;/p&gt;&#10;&lt;p&gt;This is an install for the newer NOX release on Ubuntu 12.04. I believe the branch name is &amp;lsquo;verity&amp;rsquo;. It was just upped a couple weeks ago to Github with the new repo linked from noxrepo.org. It isn&amp;rsquo;t fully released but the site said Q1 2012, at the least, it will be a base to work from on 12.04. Classic doesn&amp;rsquo;t seem to build without downgrading everything on Precise. The Nox &amp;ldquo;classic&amp;rdquo; build seems to have been dormant or not maintained for a while from what I can tell. It is important to have readily available Nox controllers since most of the projects are built on that controller. That said I like Floodlight a lot and the community is active with BidSwitch behind it. Nox has an amazing backing from Nicira so that is critical also.&lt;/p&gt;</description></item><item><title>OpenvSwitch Configure from Packages and Attaching to a Floodlight OpenFlow Controller</title><link>https://networkstatic.net/openvswitch-configure-from-packages-and-attaching-to-a-floodlight-openflow-controller/</link><pubDate>Mon, 28 May 2012 05:32:54 +0000</pubDate><guid>https://networkstatic.net/openvswitch-configure-from-packages-and-attaching-to-a-floodlight-openflow-controller/</guid><description>&lt;h2&gt;OpenvSwitch Configure from Packages and Attaching to a Floodlight OpenFlow Controller&lt;/h2&gt;&#10;&lt;a href="https://networkstatic.net/wp-content/uploads/2012/05/Openvswitch1.jpg"&gt;&lt;img class="alignright" title="Openvswitch framework" alt="" src="https://networkstatic.net/wp-content/uploads/2012/05/Openvswitch1-300x254.jpg" width="300" height="254" /&gt;&lt;/a&gt;OpenvSwitch Configure from Packages and Attaching to a Floodlight OpenFlow Controller: Couple folks have asked about installing OpenvSwitch from packages on Ubuntu 12.04 as opposed to from source. The default repos have v1.4 up so almost at the latest v1.4.1. OVS will be the de facto vSwitch in the hyper-scale providers in the future in my opinion. As Vmware's Nicira acquisition merges it will percolate into the enterprise. So its a good time to learn software switching and OVS is the best platform to start with.&#10;&lt;h2&gt;OpenvSwitch Configure from Packages&lt;/h2&gt;&#10;&lt;p&gt;This is currently not building on Ubuntu 13.04 w/ 3.8.0-29-generic. Give installing from the tarball a run. Detailed instructions are located in the INSTALL file in the root of the release. A post covering the build and overlay tunnels can be found at the following link:&lt;/p&gt;</description></item><item><title>Help Wanted: Cultural Change</title><link>https://networkstatic.net/help-wanted-cultural-change/</link><pubDate>Sun, 27 May 2012 20:33:10 +0000</pubDate><guid>https://networkstatic.net/help-wanted-cultural-change/</guid><description>&lt;p&gt;Help Wanted: Cultural Change: This post is low on the nerdalert meter and more of the arts, rather than the science. Earlier this year, Level3 blogged about their new initiative of training ~%20 of their 11,000 person staff to be “change agents” in order to cross-pollinate their peers, the notion that change is healthy for the company (speculating).&lt;/p&gt;</description></item><item><title>SDN and OpenFlow Quotes from some of the Best</title><link>https://networkstatic.net/sdn-and-openflow-quotes-from-some-of-the-best/</link><pubDate>Sun, 27 May 2012 00:04:43 +0000</pubDate><guid>https://networkstatic.net/sdn-and-openflow-quotes-from-some-of-the-best/</guid><description>&lt;p&gt;Like anyone reading this, we are avid consumers (in my case leech) of information. I put together some quote from people regarding SDN and OpenFlow. Most of the people in the list are intrinsic in helping me shape my own views regarding technology with the outstanding content, ideas and research they generate.&lt;/p&gt;</description></item><item><title>MPLS VPLS configuration with Juniper JunOS</title><link>https://networkstatic.net/mpls-vpls-configuration-with-juniper-junos/</link><pubDate>Sat, 26 May 2012 09:17:52 +0000</pubDate><guid>https://networkstatic.net/mpls-vpls-configuration-with-juniper-junos/</guid><description>&lt;h2&gt;MPLS VPLS configuration with Juniper JunOS&lt;/h2&gt;&#10;Posting a Juniper VPLS how-to on a couple of J-series routers. Have been pretty SDN focused lately so wanted to get some real stuff in for a post. Docs on JunOS VPLS can be shaky so nothing like a couple real configs to plugin your address in the lab if having problems with L2 VPNs. This includes MPLS VPLS configuration with Juniper JunOS.&#10;&lt;p&gt;The two PE routers build MPLS/BGP adjacencies to one another to exchange label information and build the LSPs for the two VRFs. VRF Blue is the VPLS virtual circuit and VRF red is a simple L3 VPN you can use to test MP-BGP to test MP-BGP populating it with loopbacks (or phy ints). VPLS can be multipoint while draft-Martini/Kompella are p2p one being LDP (Martini) to signal the label and the other being BGP (Kompella) signalled.&lt;/p&gt;</description></item><item><title>SDN Use Cases</title><link>https://networkstatic.net/sdn-business-cases/</link><pubDate>Wed, 23 May 2012 10:35:29 +0000</pubDate><guid>https://networkstatic.net/sdn-business-cases/</guid><description>&lt;h2&gt;SDN Use Cases&lt;/h2&gt;&#10;We have a few problems in networking. The following document are some SDN use cases that have come up over the past recent months/years. New abstractions in networking should enable solutions we never thought possible due to the monolithic nature of networking gear today (Mainframe 1980). This is all coming from a person who thinks MPLS can squeeze orange juice out of a lemon and am not a change for change sake guy.&#10;&lt;p&gt;&lt;a href="http://184.173.232.53/~bbsali0/wp-content/uploads/2012/05/change-is-bad1.jpg"&gt;&lt;img class="alignleft size-full wp-image-697" title="Change-is-bad" alt="" src="http://184.173.232.53/~bbsali0/wp-content/uploads/2012/05/change-is-bad1.jpg" width="330" height="260" /&gt;&lt;/a&gt;&lt;/p&gt;</description></item><item><title>SDN for Internet Providers Use Case</title><link>https://networkstatic.net/sdn-for-internet-providers-use-case/</link><pubDate>Sat, 19 May 2012 20:35:25 +0000</pubDate><guid>https://networkstatic.net/sdn-for-internet-providers-use-case/</guid><description>&lt;p&gt;This post has been updated &lt;a href="https://networkstatic.net/sdn-use-cases-for-service-providers/"&gt;here&lt;/a&gt;&lt;/p&gt;&#10;&lt;p&gt;Thanks!&#10;-Brent&lt;/p&gt;</description></item><item><title>OpenStack Essex and Quantum Installation using OpenvSwitch from Scratch</title><link>https://networkstatic.net/openstack-essex-and-quantum-installation-using-openvswitch-from-scratch/</link><pubDate>Wed, 16 May 2012 07:38:41 +0000</pubDate><guid>https://networkstatic.net/openstack-essex-and-quantum-installation-using-openvswitch-from-scratch/</guid><description>&lt;h2&gt;OpenStack Essex and Quantum Installation using OpenvSwitch from Scratch&lt;/h2&gt;&#10;&lt;aside class="legacy-callout"&gt;&lt;strong&gt;&amp;lt;em&amp;gt;&amp;lt;strong&amp;gt;Update: This is a very dated post, check out the Grizzly installation&amp;lt;/strong&amp;gt;&amp;lt;/em&amp;gt;&lt;/strong&gt; My latest installation document for Folsom can be found at the post &lt;a href="https://networkstatic.net/installing-openstack-grizzly-with-devstack/"&gt;OpenStack Folsom Quantum Devstack Installation Tutorial and Screencast&lt;/a&gt;. It's too tough to try and keep up with debugging installers myself so I am just using DevStack in that tutorial. Thanks!&lt;/aside&gt;&#10;&lt;hr&gt;&#10;Here is a walkthrough for the Quantum Network Manager Plugin for OpenStack Essex with a Quantum Installation with OpenvSwitch. It is still in dev so expect weird things and stability issues. For a guy with a networking bread and butter this is the extremely exciting piece of OpenStack for me. I will do a followup and try and breakdown the OpenvSwitch components but the data path is using the same call into the kernel as of 3.2 as Linux bridging is so the performance is in the kernel. It has a control plane component in the way of an OpenFlow controller which executes in user land which has incredible potential. Keystone is clunky still here in that you still have to run random scripts people open source, right your own or what would probably be best is figure out what its doing under the hood, but I don't have time for it and its still arcane for a next gen UI. Here is a nice guide from Stackops I got some of the Quantum configs from &lt;a href="https://github.com/EmilienM/doc-openstack" target="_blank"&gt;here.&lt;/a&gt;&#10;&lt;ul&gt;&#10;&#9;&lt;li&gt;I recommend getting a working install OpenStack Essex core components as a precursor to this, only because of the added module complexity of mixing in Quantum and OVS @&lt;/li&gt;&#10;&#9;&lt;li&gt;OpenStack Essex Installation and Configuration Screencast from Scratch (Part 1)&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;Get to know that conf file. It is the heart of the architecture for today.&#10;To find and replace the address in the file with yours you can get lazy with&lt;/p&gt;</description></item><item><title>Troubleshooting Common OpenStack Errors</title><link>https://networkstatic.net/troubleshooting-common-openstack-errors/</link><pubDate>Sat, 12 May 2012 22:56:15 +0000</pubDate><guid>https://networkstatic.net/troubleshooting-common-openstack-errors/</guid><description>&lt;h2&gt;Troubleshooting Common OpenStack Errors&lt;/h2&gt;&#10;These are some notes from troubleshooting common OpenStack Errors that I have run into in the past year. These were mostly from Diablo and Essex but some are applicable to future releases especially surrounding Nova.&#10;&lt;p&gt;/*Check all services&#10;$nova-manage service list (check for XXX or smiley face)&#10;Binary Host Zone Status State Updated_At&#10;nova-scheduler openstack1 nova enabled : - ) 2012-05-12 22:42:14&#10;nova-compute openstack1 nova enabled : - ) 2012-05-12 22:42:12&#10;nova-network openstack1 nova enabled : - ) 2012-05-12 22:42:14&lt;/p&gt;</description></item><item><title>OpenStack Essex Installation Walkthrough from Scratch (Part3)</title><link>https://networkstatic.net/openstack-essex-installation-walkthrough-from-scratch-part3/</link><pubDate>Sat, 12 May 2012 06:21:55 +0000</pubDate><guid>https://networkstatic.net/openstack-essex-installation-walkthrough-from-scratch-part3/</guid><description>&lt;p&gt;&lt;a href="http://www.youtube.com/watch?v=zdswg5Lj-Hc&amp;amp;amp;hd=1"&gt;http://www.youtube.com/watch?v=zdswg5Lj-Hc&amp;amp;amp;hd=1&lt;/a&gt;&lt;/p&gt;&#10;&lt;h2&gt;Dashboard Installation&lt;/h2&gt;&#10;/*Install packages&#10;&lt;strong&gt;$apt-get install libapache2-mod-wsgi openstack-dashboard&lt;/strong&gt;&#10;&lt;p&gt;/*Restart Apache&#10;&lt;strong&gt;$restart apache&lt;/strong&gt;&#10;&lt;strong&gt; $service apache2 restart&lt;/strong&gt;&lt;/p&gt;&#10;&lt;p&gt;/*Connect to the Dashboard web page.&#10;&lt;strong&gt;http://localhost or &lt;a href="http://x.x.x.x"&gt;http://x.x.x.x&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;&#10;&lt;p&gt;So easy a caveman (me) can do it. Not really it is a pain to get it working smoothly but mainly for me was lack of good directions and learning the pieces and parts to something a vast as this project.&lt;/p&gt;</description></item><item><title>OpenStack Essex Installation Walkthrough from Scratch (Part2)</title><link>https://networkstatic.net/openstack-essex-installation-walkthrough-from-scratch-part2/</link><pubDate>Sat, 12 May 2012 06:18:10 +0000</pubDate><guid>https://networkstatic.net/openstack-essex-installation-walkthrough-from-scratch-part2/</guid><description>&lt;p&gt;&lt;em&gt;&lt;strong&gt;Update:&lt;/strong&gt;&lt;/em&gt; My latest installation document for Folsom can be found &lt;a href="https://networkstatic.net/openstack-folsom-quantum-devstack-installation-tutorial/"&gt;here&lt;/a&gt;. It&amp;rsquo;s too tough to try and keep up with debugging installers myself so I am just using DevStack in that tutorial. Thanks!&lt;/p&gt;&#10;&lt;p&gt;&lt;a href="http://www.youtube.com/watch?v=fnxWSTuV4FU&amp;amp;amp;hd=1"&gt;http://www.youtube.com/watch?v=fnxWSTuV4FU&amp;amp;amp;hd=1&lt;/a&gt;&lt;/p&gt;&#10;&lt;h3&gt;Populate Glance Host VM OS Images&lt;/h3&gt;&#10;&lt;p class="textbox"&gt;/*Upload Images&#10;/* 11.10 image&#10;wget http://uec-images.ubuntu.com/releases/11.10/release/ubuntu-11.10-server-cloudimg-amd64-disk1.img&#10;/* 12.04 image&#10;wget https://cloud-images.ubuntu.com/precise/current/precise-server-cloudimg-amd64-disk1.img&lt;/p&gt;</description></item><item><title>OpenStack Essex Installation and Configuration Screencast from Scratch (Part 1)</title><link>https://networkstatic.net/openstack-essex-installation-and-configuration-screencast-from-scratch/</link><pubDate>Sat, 12 May 2012 06:13:51 +0000</pubDate><guid>https://networkstatic.net/openstack-essex-installation-and-configuration-screencast-from-scratch/</guid><description>&lt;h2&gt;OpenStack Essex Install on 12.04&lt;/h2&gt;&#10;&lt;aside class="legacy-callout"&gt;&lt;strong&gt;Dated Content, Please see the Following&lt;/strong&gt;&lt;p style="text-align: left;" align="center"&gt;&lt;em&gt;&lt;strong&gt;Update:&lt;/strong&gt;&lt;/em&gt; My latest installation Tutorial for OpenStack Folsom. It's too tough to try and keep up with debugging installers myself so I am just using DevStack in that tutorial. Thanks!&#10;&lt;a href="https://networkstatic.net/openstack-folsom-quantum-devstack-installation-tutorial/" target="_blank"&gt;OpenStack Folsom Quantum DevStack Installation Tutorial&lt;/a&gt; &#10;&lt;/p&gt;&lt;/aside&gt;</description></item><item><title>OpenStack Essex Operational Demo</title><link>https://networkstatic.net/openstack-essex-operational-demo/</link><pubDate>Wed, 09 May 2012 06:44:05 +0000</pubDate><guid>https://networkstatic.net/openstack-essex-operational-demo/</guid><description>&lt;p&gt;This is the first in some configuration and deployment guides for OpenStack Essex. This clearly has potential well beyond hyper-scale cloud and content providers. If VMware execs are not concerned about enterprise market share today, I expect they will be sooner, rather than later. It represents consumerism driving the market. &amp;lsquo;Ecosystem&amp;rsquo;, is the new, fun buzzword in the cloudy, smokey industry today. That is nothing new. We have always looked for more comprehensive forms of orchestration and typically that equates to yet another layer of abstraction. That is not a bad thing. That rise up the stack typically reduces operational cost and boosts productivity.&lt;/p&gt;</description></item><item><title>Floodlight OpenFlow Controller Screencast with HP Switches</title><link>https://networkstatic.net/floodlight-openflow-controller-screencast-with-hp-switches/</link><pubDate>Tue, 01 May 2012 04:50:33 +0000</pubDate><guid>https://networkstatic.net/floodlight-openflow-controller-screencast-with-hp-switches/</guid><description>&lt;h2&gt;Floodlight OpenFlow Controller Screencast with HP Switches&lt;/h2&gt;&#10;&lt;hr&gt;&#10;There is an updated post with the newest HP OpenFlow firmware that can be found at: &lt;a href="https://networkstatic.net/configure-an-hp-openflow-switch-for-floodlight/"&gt;Configure an HP OpenFlow Switch for Floodlight&lt;/a&gt;&#10;&lt;hr&gt;&#10;&lt;p&gt;Quick how-to on installing the Floodlight OpenFlow controller and a slick http UI fronted someone put up on GutHub. Floodlight is probably the easiest of all controllers to setup. It is built in Java and based on the Beacon controller project. It is a great way to get your feet wet in SDN. I will work on a post showing some of the capabilities in the next few days.&lt;/p&gt;</description></item><item><title>Configuring the NOX GUI</title><link>https://networkstatic.net/configuring-the-nox-gui/</link><pubDate>Tue, 24 Apr 2012 04:07:11 +0000</pubDate><guid>https://networkstatic.net/configuring-the-nox-gui/</guid><description>&lt;h2 class="legacy-heading"&gt;Configuring the NOX GUI&lt;/h2&gt;&#10;&lt;aside class="legacy-callout"&gt;&lt;strong&gt;Configuring the NOX GUI Update: &lt;/strong&gt;The NOX libraries are not maintained for most distros at the moment. Everything has been stripped out of NOX except for the core implementation as a C++ base for development.  I &lt;strong&gt;recommend&lt;/strong&gt; trying either &lt;a href="https://networkstatic.net/floodlight-openflow-controller-screencast-with-hp-switches/"&gt;FloodLight&lt;/a&gt; or &lt;a href="https://networkstatic.net/pox-openflow-controller-installation-screencast/"&gt;POX&lt;/a&gt;.&lt;/aside&gt;&#10;&lt;h2&gt;Configuring the NOX GUI&lt;/h2&gt;&#10;To install NOX Destiny branch refer to this &lt;a href="https://networkstatic.net/2012/04/22/nox-openflow-controller-installation-screencast/" target="_blank"&gt;post&lt;/a&gt;.&#10;&lt;p&gt;To get the little test web page going run the following on startup.&lt;/p&gt;</description></item><item><title/><link>https://networkstatic.net/google0d5477471e9d4160-html/</link><pubDate>Mon, 23 Apr 2012 23:42:43 +0000</pubDate><guid>https://networkstatic.net/google0d5477471e9d4160-html/</guid><description>&lt;p&gt;google-site-verification: google0d5477471e9d4160.html&lt;/p&gt;</description></item><item><title>OpenStack Essex Scripted Installation on Ubuntu 12.04 (Part 2)</title><link>https://networkstatic.net/openstack-essex-scripted-installation-on-ubuntu-12-04-part-2/</link><pubDate>Mon, 23 Apr 2012 03:42:43 +0000</pubDate><guid>https://networkstatic.net/openstack-essex-scripted-installation-on-ubuntu-12-04-part-2/</guid><description>&lt;p&gt;&lt;em&gt;&lt;strong&gt;Update:&lt;/strong&gt;&lt;/em&gt; My latest installation document for Folsom can be found &lt;a href="https://networkstatic.net/openstack-folsom-quantum-devstack-installation-tutorial/"&gt;here&lt;/a&gt;. It&amp;rsquo;s too tough to try and keep up with debugging installers myself so I am just using DevStack in that tutorial. Thanks!&lt;/p&gt;&#10;&lt;p&gt;Well, we have OpenStack running on a couple of nodes now what? Let’s install Wordpress on two nodes with web server running Apache on one node and MySql on another compute node.&lt;/p&gt;</description></item><item><title>OpenStack Essex Scripted Installation on Ubuntu 12.04 (Part 1)</title><link>https://networkstatic.net/openstack-essex-scripted-installation-on-ubuntu-12-04-part-1/</link><pubDate>Mon, 23 Apr 2012 03:09:36 +0000</pubDate><guid>https://networkstatic.net/openstack-essex-scripted-installation-on-ubuntu-12-04-part-1/</guid><description>&lt;aside class="legacy-callout"&gt;&#10;&lt;ul&gt;&#10;&#9;&lt;li&gt;&lt;a href="https://networkstatic.net/installing-openstack-grizzly-with-devstack/" target="_blank"&gt;Installing OpenStack Grizzly with DevStack&lt;/a&gt; : Here is an updated Grizzly DevStack tutorial since Folsom is coming to an end.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;/aside&gt;&#10;&lt;p&gt;&lt;em&gt;&lt;strong&gt;Update:&lt;/strong&gt;&lt;/em&gt; My latest installation document for Folsom can be found &lt;a href="https://networkstatic.net/openstack-folsom-quantum-devstack-installation-tutorial/"&gt;here&lt;/a&gt;. It&amp;rsquo;s too tough to try and keep up with debugging installers myself so I am just using DevStack in that tutorial. Thanks!&lt;/p&gt;</description></item><item><title>NOX OpenFlow Controller Installation Screencast Ubuntu 11.10</title><link>https://networkstatic.net/nox-openflow-controller-installation-screencast/</link><pubDate>Sun, 22 Apr 2012 07:36:55 +0000</pubDate><guid>https://networkstatic.net/nox-openflow-controller-installation-screencast/</guid><description>&lt;h2&gt; NOX OpenFlow Controller Installation Screencast Ubuntu 11.10 &lt;/h2&gt;&#10;&lt;p&gt;This post is on the NOX OpenFlow Controller Installation Screencast Ubuntu 11.10. When compiling NOX If you get the error &amp;ldquo;configure: error: openssl/md5.h not found. NOX requires OpenSSL&amp;rdquo;&lt;/p&gt;&#10;&lt;p&gt;You just need to switch to the &amp;lsquo;destiny&amp;rsquo; branch from the default &amp;lsquo;zaku&amp;rsquo; branch.&lt;/p&gt;</description></item><item><title>POX Openflow Controller Installation Screencast</title><link>https://networkstatic.net/pox-openflow-controller-installation-screencast/</link><pubDate>Sun, 22 Apr 2012 07:30:54 +0000</pubDate><guid>https://networkstatic.net/pox-openflow-controller-installation-screencast/</guid><description>&lt;h2&gt;POX Openflow Controller Installation Screencast&lt;/h2&gt;&#10;POX Openflow Controller Installation: POX is a lightweight OpenFlow controller that is written completely in Python that is targeted for developers to spin up their own controllers. The nice thing about POX is if you want an OF controller spun up in as fast as you can type git clone etc, you got it.&#10;&lt;p&gt;It supports the same tools that NOX does but you dont have the C++ compilation dependencies that without maintenance get stale quickly as libraries evolve.&lt;/p&gt;</description></item><item><title>Open vSwitch GRE Tunnel Configuration</title><link>https://networkstatic.net/open-vswitch-gre-tunnel-configuration/</link><pubDate>Thu, 19 Apr 2012 06:45:57 +0000</pubDate><guid>https://networkstatic.net/open-vswitch-gre-tunnel-configuration/</guid><description>&lt;h2&gt;Open vSwitch GRE Tunnel Configuration&lt;/h2&gt;&#10;&lt;aside class="legacy-callout"&gt;&lt;strong&gt;Open vSwitch Updated Tutorial&lt;/strong&gt;-I updated this September 20, 2012. Also adding this PDF from a instruction I did over the summer at an Internet2 conference. Download the lab here &lt;a href="https://networkstatic.net/wp-content/uploads/2012/04/openvswitch.openflow.gre_.tutorial1.pdf"&gt;OpenFlow and Open vSwitch GRE Tunnel Configuration Tutorial&lt;/a&gt;.&#10;-Another lab building from source with video and pretty vetted is &lt;a href="https://networkstatic.net/configuring-vxlan-and-gre-tunnels-on-openvswitch/"&gt; Configuring VXLan and GRE Tunnels on OpenvSwitch&lt;/a&gt;&lt;/aside&gt;&#10;&lt;h2&gt;Open vSwitch GRE Tunnel Screencast&lt;/h2&gt;&#10;&lt;p&gt;&lt;a href="http://www.youtube.com/watch?v=VMP4Q2XtFjw"&gt;Watch video on YouTube&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Installing and Configuring OpenvSwitch on Ubuntu 12.04 (Precise Pangolin)</title><link>https://networkstatic.net/installing-and-configuring-openvswitch-on-ubuntu-12-04-precise-pangolin/</link><pubDate>Mon, 16 Apr 2012 06:00:44 +0000</pubDate><guid>https://networkstatic.net/installing-and-configuring-openvswitch-on-ubuntu-12-04-precise-pangolin/</guid><description>&lt;h2&gt;Installing and Configuring OpenvSwitch on Ubuntu 12.04 (Precise Pangolin)&lt;/h2&gt;&#10;&lt;aside class="legacy-callout"&gt;&lt;strong&gt;Updates&lt;/strong&gt;&#10;&lt;ul&gt;&#10;&#9;&lt;li&gt;For installing OpenvSwitch on Ubuntu from package head to &lt;a href="https://networkstatic.net/openvswitch-configure-from-packages-and-attaching-to-a-floodlight-openflow-controller/" target="_blank"&gt;OpenvSwitch Configure from Packages and Attaching to a Floodlight OpenFlow Controller&lt;/a&gt;&lt;/li&gt;&#10;&#9;&lt;li&gt;To install Open vSwitch from source head to &lt;a href="https://networkstatic.net/configuring-vxlan-and-gre-tunnels-on-openvswitch/" target="_blank"&gt;Configuring VXLan and GRE tunnels on OpenvSwitch&lt;/a&gt;&lt;/li&gt;&#10;&#9;&lt;li&gt;Or use this Python App I wrote to install some different combinations of tools. Last verified working June 2013. &lt;a href="https://networkstatic.net/openflow-openvswitch-and-kvm-sdn-lab-installation-app/" target="_blank"&gt;OpenFlow, OpenvSwitch and KVM SDN Lab Installation App&lt;/a&gt;&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;/aside&gt;&#10;&lt;h2 class="legacy-heading"&gt;Installing and Configuring OpenvSwitch on Ubuntu 12.04 (Precise Pangolin)&lt;/h2&gt;&#10;Quick install how to for Installing and Configuring OpenvSwitch on Ubuntu 12.04 (Precise Pangolin) with the nightly OVS build. Before I start, I must point out the great progress the dev team has done in such a short time. All of the old gotchas in earlier releases on implementation are long gone. I am going to revisit the KVM integration in a few days as some of the inconsistencies for bringing up TAPs into hypervisors should be getting some consensus for provisioning.&#10;&lt;hr&gt;&#10;The announcement of the inclusion of OpenvSwitch into the mainline Linux kernel, coupled with some KVM enhancements to provide VLAN tagging, LACP, QoS, sFlow etc, is making some of us excited ,and others very nervous.&#10;&lt;pre class="code-sample"&gt;&lt;code&gt;&#10;@ubuntu-12:openvswitch-HEAD-f1936eb# uname -a&#10;Linux ubuntu-12 3.2.0-23-generic-pae #36-Ubuntu SMP Tue Apr 10 22:19:09 UTC 2012 i686 i686 i386 GNU/Linux&#10;&lt;em&gt;#Ubuntu release&lt;/em&gt;&#10;@ubuntu-12:openvswitch-HEAD-f1936eb# lsb_release -a&#10;No LSB modules are available.&#10;Distributor ID: Ubuntu&#10;Description: Ubuntu precise (development branch)&#10;Release: 12.04&#10;Codename: precise&#10;&lt;/code&gt;&lt;/pre&gt;&#10;For those familiar with the build you can just paste the following in your bash shell as root. To walk through the install skip the following snippet. The installation is extensively documented in the INSTALL file in the root of the tarball.&#10;&lt;pre class="code-sample"&gt;&lt;code&gt;apt-get update&#10;apt-get install -y git automake autoconf gcc uml-utilities libtool build-essential git pkg-config linux-headers-`uname -r`&#10;wget http://openvswitch.org/releases/openvswitch-1.10.0.tar.gz&#10;tar zxvf openvswitch-1.10.0.tar.gz&#10;cd openvswitch-1.10.0&#10;./boot.sh&#10;./configure --with-linux=/lib/modules/`uname -r`/build&#10;make &amp;&amp; make install&#10;insmod datapath/linux/openvswitch.ko&#10;mkdir -p /usr/local/etc/openvswitch&#10;ovsdb-tool create /usr/local/etc/openvswitch/conf.db vswitchd/vswitch.ovsschema&#10;ovsdb-server -v --remote=punix:/usr/local/var/run/openvswitch/db.sock \&#10; --remote=db:Open_vSwitch,manager_options \&#10; --private-key=db:SSL,private_key \&#10; --certificate=db:SSL,certificate \&#10; --pidfile --detach --log-file&#10;ovs-vsctl --no-wait init&#10;ovs-vswitchd --pidfile --detach&#10;ovs-vsctl show&lt;/code&gt;&lt;/pre&gt;&#10;&lt;h4&gt;System Preperation&lt;/h4&gt;&#10;Install dependencies:&#10;&lt;pre class="code-sample"&gt;&lt;code&gt;apt-get update&#10;apt-get install python-simplejson automake autoconf gcc uml-utilities libtool build-essential git pkg-config&lt;/code&gt;&lt;/pre&gt;&#10;Download the OVS tarball &lt;em&gt;Note: you can also pull from the git repository but that is bleeding edge and depending on kernel releases it may need some massaging.&lt;/em&gt;&#10;&lt;pre class="code-sample"&gt;&lt;code&gt;wget http://openvswitch.org/releases/openvswitch-1.10.0.tar.gz&#10;tar zxvf openvswitch-1.10.0.tar.gz&#10;cd openvswitch-1.10.0&lt;/code&gt;&lt;/pre&gt;&#10;&lt;h2&gt;Compiling Open vSwitch From Source&lt;/h2&gt;&#10;&lt;pre class="code-sample"&gt;&lt;code&gt;./boot.sh&#10;./configure --with-linux=/lib/modules/`uname -r`/build&#10;make&#10;make install&#10;#Load the OVS Kernel Module&#10;insmod datapath/linux/openvswitch.ko&lt;/code&gt;&lt;/pre&gt;&#10;&lt;pre class="code-sample"&gt;&lt;code&gt;#If you are running a stripped version of Nix like an EC2 cloud image and get an error along the lines of this:&#10;configure: error: source dir /lib/modules/3.2.0-23-virtual/build doesn&amp;#039;t exist&#10;#Pull down the headers for your kernel. &#10;sudo apt-get install linux-headers-`uname -r`&lt;/code&gt;&lt;/pre&gt;&#10;&lt;h2&gt;Open vSwitch Configuration&lt;/h2&gt;&#10;&lt;pre class="code-sample"&gt;&lt;code&gt;touch /usr/local/etc/ovs-vswitchd.conf&#10;mkdir -p /usr/local/etc/openvswitch&#10;ovsdb-tool create /usr/local/etc/openvswitch/conf.db vswitchd/vswitch.ovsschema&lt;/code&gt;&lt;/pre&gt;&#10;Run the following commands, note some dashes are two '- -' e.g. - -remote=db &amp;amp; - -private-key&#10;&lt;p&gt;Start ovsdb-server, this stores the config into a file that is persistent even after restarts.&lt;/p&gt;</description></item><item><title>Juniper Default Routing Tables</title><link>https://networkstatic.net/juniper-default-routing-tables/</link><pubDate>Sun, 15 Apr 2012 19:38:53 +0000</pubDate><guid>https://networkstatic.net/juniper-default-routing-tables/</guid><description>&lt;h2&gt; Juniper Default Routing Tables &lt;/h2&gt;&#10;&lt;p&gt;The first time I saw these I remember thinking what is going on here. It can be pretty foreign the first time someone sees it especially coming from Cisco IOS. The two CLIs wrap and abstract the underlying standardized frameworks pretty differently. I think it helps to decouple what the function of the table is before ever operating the gear. I tended to start banging away on the gear and wind up with holes since I didn’t breakdown the architectural pieces first. It would have saved many days of back tracking if I had started with a clear breakdown of the tables and still does to this day :)&lt;/p&gt;</description></item><item><title>Juniper and Cisco Comparisons of RIB, LIB, FIB and LFIB Tables</title><link>https://networkstatic.net/juniper-and-cisco-comparisons-of-rib-lib-fib-and-lfib-tables/</link><pubDate>Sun, 15 Apr 2012 10:06:46 +0000</pubDate><guid>https://networkstatic.net/juniper-and-cisco-comparisons-of-rib-lib-fib-and-lfib-tables/</guid><description>&lt;h2&gt;Juniper and Cisco Comparisons of RIB, LIB, FIB and LFIB Tables&lt;/h2&gt;&#10;A quick overview before we start:&#10;&lt;ul&gt;&#10;&#9;&lt;li&gt;RIBs maintain the network topologies and routing tables for each protocol. This would include many routes going to the same destination prefix.&lt;/li&gt;&#10;&#9;&lt;li&gt;FIBs are the best route from the possibly many protocols in the RIBs pushed down to fast forwarding lookup memory for the best path(s).&lt;/li&gt;&#10;&#9;&lt;li&gt;I wanted to get on paper some of the differences between Junos and IOS commands with regards to MPLS related forwarding tables.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;It starts off with the ingress packet. As a packet comes into the Label Edge Router (LER) the Layer2 frame header will be examined and forwarded to the appropriate table, based on the Ethertype field to determine what protocol in payload of the Ethernet frame.&lt;/p&gt;</description></item><item><title>Use case for MPLS in the Enterprise for PCI Compliance</title><link>https://networkstatic.net/an-no-brainer-use-case-for-mpls-in-the-enterprise-pci-compliance/</link><pubDate>Fri, 13 Apr 2012 04:07:15 +0000</pubDate><guid>https://networkstatic.net/an-no-brainer-use-case-for-mpls-in-the-enterprise-pci-compliance/</guid><description>&lt;h2&gt; Use case for MPLS in the Enterprise for PCI Compliance&lt;/h2&gt;&#10;MPLS is today's only form of scalable network virtualization we have for now. I personally think the promise of something called SDN will move into that space soon but until then, we need network virtualization. PCI is a joke. It is a racket by Visa and banks to spread fear without any brains behind the architecture. PCI DSS v2.0 soon to be v3.0 is on of the few technological security documents that clearly states the requirements. Path Isolation is very clear for the network architect to build a design around.&#10;&lt;p&gt;That happens to be the bread and butter of MPLS as it has been used for well over a decade by service providers to provide multi tenant virtualized networks. Virtual logical and scalable networks overlaid on top of a single physical network.&lt;/p&gt;</description></item><item><title>Basic MPLS/VPN with Cisco IOS</title><link>https://networkstatic.net/basic-mplsvpn-using-cisco-ios/</link><pubDate>Wed, 11 Apr 2012 03:59:03 +0000</pubDate><guid>https://networkstatic.net/basic-mplsvpn-using-cisco-ios/</guid><description>&lt;h2&gt;Basic MPLS/VPN with Cisco IOS&lt;/h2&gt;&#10;This is a quick tutorial for basic MPLS/VPN with Cisco IOS configuration. The tutorial exemplifies basic PE to P to PE configuration on three Cisco 7200s running in GNS3 with IOS. R2 is configured as a route reflector P node and R4, R6 and R3 are PE node route reflector clients. The IGP is OSPF with R2 as the ABR. Loopback1 (Lo1) on R3  &amp;amp; R4 represent a customer VPN (CE) ethernet segment. The loopback 1 interfaces are pushed into the MPLS/VRF named "data" to simulate an Ethernet segment advertised into the VRF.&#10;&lt;h2&gt;Basic MPLS/VPN and Multi-Protocol BGP Topology&lt;/h2&gt;&#10;&lt;p style="text-align: center;"&gt;&lt;a href="https://networkstatic.net/wp-content/uploads/2012/04/4-node.jpg"&gt;&lt;img class="size-full wp-image-322 aligncenter" title="4-node" alt="" src="https://networkstatic.net/wp-content/uploads/2012/04/4-node.jpg" width="500" height="383" /&gt;&lt;/a&gt;&lt;/p&gt;</description></item><item><title>How Headers Encapsulate in the OSI stack</title><link>https://networkstatic.net/how-headers-encapsulate-in-the-osi-stack/</link><pubDate>Tue, 10 Apr 2012 05:51:06 +0000</pubDate><guid>https://networkstatic.net/how-headers-encapsulate-in-the-osi-stack/</guid><description>&lt;h2&gt;How Headers Encapsulate in the OSI stack&lt;/h2&gt;&#10;How Headers Encapsulate in the OSI stack: Part 2 of some refreshers. We send application data or payload by encapsulating or framing each layer within the previous layer. We looked at each one individually and now here is how they look when each layer is wrapped inside the previous layer.&#10;&lt;figure class="legacy-figure"&gt;&lt;img src="https://networkstatic.net/wp-content/uploads/2012/12/youtube-kitty-osi.jpg" alt="OSI Model Encapsulation"&gt;&lt;/figure&gt;&#10;&lt;strong&gt; Figure 1&lt;/strong&gt;. Here is how application data gets passed to each protocol in the stack to see a cute cat playing piano.&#10;&lt;p&gt;Each device along the path from source to destination (user to Youtube in this case) strips the header it is concerned with and imposes the new information in another header wrapping the packet back up for its next hop. The payload remains the same along the way outside of fragmentation but these days Path MTU Discovery (PMTUD) has alleviated the need to fragment packets thus reducing overhead on devices in the path. I left out the footer in the Layer 2 Ethernet layer so keep in mind there is one there along with &amp;ldquo;TCP data&amp;rdquo; on the tail of the TCP header and payload.&lt;/p&gt;</description></item><item><title>How I Learned to Hate the DCI</title><link>https://networkstatic.net/how-i-learned-to-hate-the-dci/</link><pubDate>Mon, 09 Apr 2012 00:57:46 +0000</pubDate><guid>https://networkstatic.net/how-i-learned-to-hate-the-dci/</guid><description>&lt;p&gt;How I Learned to Hate the DCI: Layer 2 data center interconnects (DCI) is still alive and well. I blame VMware with vMotion and now every other Hypervisor vendor on the planet. Live workload migration is certainly vital to most operations. The further up the stack that happens the more flexibility you have with choosing more layers beneath you to reach for in the toolkit.&lt;/p&gt;</description></item><item><title>What are Ethernet, IP and TCP Headers in Wireshark Captures</title><link>https://networkstatic.net/what-are-ethernet-ip-and-tcp-headers-in-wireshark-captures/</link><pubDate>Sun, 08 Apr 2012 04:58:49 +0000</pubDate><guid>https://networkstatic.net/what-are-ethernet-ip-and-tcp-headers-in-wireshark-captures/</guid><description>&lt;h2&gt;What are Ethernet, IP and TCP Headers in Wireshark Captures&lt;/h2&gt;&#10;If I could go back in time when I was a n00b kid wanting to go from zero to a million in networking, the one thing I would change would be spending about 6 months on the fundamentals of networking headers and framing before ever touching a single peice of vendor gear. Ethernet, IP and Transport headers (L2-L4) are the past present and future of networking. Protocols will come and go, Ethernet and IP will undoubtedly be with us for the rest of our careers. I know a lot of good engineers, Ops and architects that have learned and forgotten fundamental details five times over, me included as we fill our heads with timers of IGPs and framing encapsulations of data center interconnects.&#10;&lt;p&gt;I tend to try and go back and refresh the basics on the wikis as much as possible. Example, 802.1Q encapsulation is not actually encapsulating the original frame but inserting a 32-bit field with the TPID, VID etc.&lt;/p&gt;</description></item><item><title>Why the NOS will decouple</title><link>https://networkstatic.net/why-the-nos-will-decouple/</link><pubDate>Mon, 02 Apr 2012 03:43:30 +0000</pubDate><guid>https://networkstatic.net/why-the-nos-will-decouple/</guid><description>&lt;p&gt;Over the next couple of years some of us expect the networking industry to have some fairly significant changes.&lt;/p&gt;&#10;&lt;p&gt;There are really two options:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&#9;&lt;li&gt;A distributed approach we have today or a controller based centralized model. We  have today just that, autonomous devices building adjacencies to one another, exchanging what it hopes are the best healthy paths to send next hop traffic to. I am not holding my breath that Netconf is suddenly going to revolutionize operational scale of distributed networks under a single organization.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;div&gt;&lt;/div&gt;&#10;&lt;ul&gt;&#10;&#9;&lt;li&gt;There are three components in our networking switches/routers today, management, data (Layer2 forwarding) and control (Layer3 routing) planes. Centralizing or at least abstracting distributed networks into a single management and possibly control plane to our network. We have some examples of that today that show significant ROI of decoupling the network operating system from the network edge device. Wireless controllers have allowed wireless to scale operationally without having to double the networking staff to support 2x 3x growth in most enterprises annually. QFabric is another example of an exploding chassis across a data center. Software defined networks (SDN) means just that, abstracting operations, administration and management one layer up the stack.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;I expect us to see a start from vendors to explore decoupling the network operating system from the hardware beyond just data center software switches like a Nexus 1000v. Decoupling the NOS and at least the management plane to start with will allow for innovation beyond just what a handful of networking vendors deem as good software solutions. Decoupling the NOS will allow for our researchers and new startups to develop software above the net.&#10;&lt;p&gt;If we can do this with everything else in the data center why not on the network also? I get a little aggravated when we come up with as many reasons possible to at the end of the day avoid change and innovation when the x86 market has set the roadmap of what I believe we will see over the next decade in the networking industry. The road to innovation is paved with the likes of those unwilling to take risk, Sun, Kodak, Nortel etc. Doing the right thing for the consumer and customer tends to work in my experience.&lt;/p&gt;</description></item><item><title>Network Processor Units (NPU) FTW</title><link>https://networkstatic.net/network-processing-units-npu-for-the-win/</link><pubDate>Sun, 25 Mar 2012 23:50:17 +0000</pubDate><guid>https://networkstatic.net/network-processing-units-npu-for-the-win/</guid><description>&lt;h2 class="legacy-heading"&gt;Network processing Units (NPU) for the Win&lt;/h2&gt;&#10;&lt;p&gt;&lt;a href="https://networkstatic.net/wp-content/uploads/2013/03/Cisco-Catalyst-3850-Cavium.png"&gt;&lt;img src="https://networkstatic.net/wp-content/uploads/2013/03/Cisco-Catalyst-3850-Cavium.png" alt="Cisco-Catalyst-3850-Cavium" width="635" height="590" class="aligncenter size-full wp-image-6084" /&gt;&lt;/a&gt;&lt;/p&gt;</description></item><item><title>OTV configuration notes</title><link>https://networkstatic.net/otv-configuration-notes/</link><pubDate>Mon, 27 Feb 2012 07:22:23 +0000</pubDate><guid>https://networkstatic.net/otv-configuration-notes/</guid><description>&lt;p&gt;Quick notes on OTV. I have not put this on lab gear yet so there may be typos. It does require licensing so make sure you have that budgeted, if not its a 20kish surprise which sucks.&lt;/p&gt;&#10;&lt;p&gt;&lt;a href="http://184.173.232.53/~bbsali0/wp-content/uploads/2012/05/dci1.jpg"&gt;&lt;img src="http://184.173.232.53/~bbsali0/wp-content/uploads/2012/05/dci1.jpg" alt="" title="DCI" width="432" height="279" class="aligncenter size-full wp-image-590" /&gt;&lt;/a&gt;&lt;/p&gt;</description></item><item><title>February 2012 SDN Thoughts</title><link>https://networkstatic.net/february-2012-sdn-thoughts-2/</link><pubDate>Tue, 21 Feb 2012 01:10:59 +0000</pubDate><guid>https://networkstatic.net/february-2012-sdn-thoughts-2/</guid><description>&lt;p&gt;I commented on a blog post earlier and I am recording my updated thoughts to review over the next few years to see how wrong I was. My initial business cases still have not changed much from 4 months ago.&lt;/p&gt;</description></item><item><title>OpenVswitch and GRE tunnel notes</title><link>https://networkstatic.net/openvswitch-and-gre-tunnel-notes/</link><pubDate>Tue, 14 Feb 2012 04:18:03 +0000</pubDate><guid>https://networkstatic.net/openvswitch-and-gre-tunnel-notes/</guid><description>&lt;p&gt;Here is a quick post for setting up GRE tunnels on OpenVswitch. Both Vswitch boxes are attached to an OpenFlow Beacon controller.&lt;/p&gt;&#10;&lt;p&gt;More up to date how-to can be found here:&lt;/p&gt;&#10;&lt;p&gt;&lt;a href="https://networkstatic.net/configuring-vxlan-and-gre-tunnels-on-openvswitch/" target="_blank"&gt;&lt;em&gt;Configuring VXLan and GRE tunnels on OpenvSwitch&lt;/em&gt;&lt;/a&gt;&lt;/p&gt;&#10;&lt;p&gt;KVM live storage migration makes an interesting story and run at VMware tools. The dreaded layer2 data center link conversation may never go away unfortunately. It would be nice to push this to the Hypervisors rather than mucking up our pretty networks.&lt;/p&gt;</description></item><item><title>Installing Open vSwitch with KVM</title><link>https://networkstatic.net/installing-open-vswitch-with-kvm/</link><pubDate>Fri, 03 Feb 2012 02:50:10 +0000</pubDate><guid>https://networkstatic.net/installing-open-vswitch-with-kvm/</guid><description>&lt;h2&gt;Installing Open vSwitch with KVM&lt;/h2&gt;&#10;This tutorial is for installing Open vSwitch with KVM in order to replace traditional hypervisor Ethernet switching using Linux bridging with Open vSwitch.&#10;&lt;aside class="legacy-callout"&gt;&lt;strong&gt;Updates&lt;/strong&gt;&lt;ul&gt;&#10;&#9;&lt;li&gt;&#10;For installing Open vSwitch on Ubuntu from package head to &lt;a href="https://networkstatic.net/openvswitch-configure-from-packages-and-attaching-to-a-floodlight-openflow-controller/" target="_blank"&gt;Open vSwitch Configure from Packages and Attaching to a Floodlight OpenFlow Controller&lt;/a&gt;&lt;/li&gt;&#10;&#9;&lt;li&gt;To install Open vSwitch from source head to &lt;a href="https://networkstatic.net/configuring-vxlan-and-gre-tunnels-on-openvswitch/" target="_blank"&gt;Configuring VXLan and GRE tunnels on OpenvSwitch&lt;/a&gt;&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;/aside&gt;&#10;&lt;h2&gt;Installing Open vSwitch on Ubuntu with KVM&lt;/h2&gt;&#10;I rebuilt this box becuase as fun as it was to setup OpenStack (I think) there are a million modules that would take more time to clip out rather than just rebuilding. Anyone gotten Nova integrated into Open vSwitch yet? That will be a great marriage for nailing up cloud nodes through tunnels dynamically. I expect Open vSwitch to be an important not just to Vmware moving forward with software defined networking but more importantly setting a trend for open source software (OSS) project in networking.&#10;&lt;p&gt;Pulled some deps for some other things but here is history.&lt;/p&gt;</description></item><item><title>OpenStack on Ubuntu 11.10 Installation</title><link>https://networkstatic.net/my-notes-from-2/</link><pubDate>Wed, 01 Feb 2012 16:43:46 +0000</pubDate><guid>https://networkstatic.net/my-notes-from-2/</guid><description>&lt;aside class="legacy-callout"&gt;&lt;strong&gt;&amp;lt;em&amp;gt;&amp;lt;strong&amp;gt;Update:&amp;lt;/strong&amp;gt;&amp;lt;/em&amp;gt;&lt;/strong&gt; My latest installation document for Folsom can be found at the post &lt;a href="https://networkstatic.net/openstack-folsom-quantum-devstack-installation-tutorial/"&gt;OpenStack Folsom Quantum Devstack Installation Tutorial and Screencast&lt;/a&gt;. It's too tough to try and keep up with debugging installers myself so I am just using DevStack in that tutorial. Thanks!&lt;/aside&gt;&#10;&lt;p&gt;My notes from an OpenStack &amp;amp; Ubuntu 11.10. These are only my notes. Lots of errors. It was a fairly painless install. I didnt have the lab gear setup with two Nics so I got a bit kludgy at the end. I think the interesting component will be to replace the Openstack bridging with OpenVswitch.&lt;/p&gt;</description></item><item><title>Installing NOX OpenFlow Controller on Ubuntu 11.10</title><link>https://networkstatic.net/installing-nox-openflow-controller-on-ubuntu-11-10/</link><pubDate>Wed, 01 Feb 2012 05:30:03 +0000</pubDate><guid>https://networkstatic.net/installing-nox-openflow-controller-on-ubuntu-11-10/</guid><description>&lt;p&gt;&lt;strong&gt;Updated UB 11.10 post &lt;a title="here" href="https://networkstatic.net/2012/04/22/nox-openflow-controller-installation-screencast/"&gt;here&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;&#10;&lt;p&gt;It is all pretty straight forward except for the default branch is zaku(stable) which has compilation issues. This switches the branch to destiny(unstable).&#10;&lt;strong&gt;$wget &lt;a href="http://openflowswitch.org/downloads/debian/binary/nox-dependencies.deb"&gt;http://openflowswitch.org/downloads/debian/binary/nox-dependencies.deb&lt;/a&gt;   &lt;/strong&gt;&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;$dpkg &amp;ndash;info nox-dependencies.deb $cd /etc/apt/sources.list.d &lt;/strong&gt;&#10;&lt;strong&gt;$sudo wget &lt;a href="http://openflowswitch.org/downloads/debian/nox.list"&gt;http://openflowswitch.org/downloads/debian/nox.list&lt;/a&gt; &lt;/strong&gt;&#10;&lt;strong&gt;$sudo apt-get update $sudo apt-get install nox-dependencies &lt;/strong&gt;&#10;&lt;strong&gt;$git clone git://noxrepo.org/nox &lt;/strong&gt;&#10;&lt;strong&gt;$cd nox&lt;/strong&gt;&lt;/p&gt;</description></item><item><title>Installing Openvswitch and KVM on CentOS 6.2</title><link>https://networkstatic.net/installing-openvswitch-and-kvm-on-centos-6-2/</link><pubDate>Thu, 26 Jan 2012 09:22:02 +0000</pubDate><guid>https://networkstatic.net/installing-openvswitch-and-kvm-on-centos-6-2/</guid><description>&lt;h2&gt; Installing Openvswitch and KVM on CentOS 6.2 &lt;/h2&gt;&#10;&lt;aside class="legacy-callout"&gt;Please see the updated how-to on &lt;a href="https://networkstatic.net/open-vswitch-red-hat-installation/" target="_blank"&gt;Installing OpenvSwitch on CentOS&lt;/a&gt;.&lt;/aside&gt;&#10;&lt;p&gt;This is all (mostly) covered in the INSTALL.Linux inside the tar. This might help folks with some of the&lt;/p&gt;&#10;&lt;p&gt;graph&lt;/p&gt;&#10;&lt;h2&gt; Download and Install Open vSwitch&lt;/h2&gt;&#10;&lt;pre class="code-sample"&gt;&lt;code&gt;&#10;$ wget http://openvswitch.org/releases/openvswitch-1.3.0.tar.gz&#10;wget http://download.fedoraproject.org/pub/fedora/linux/releases/16/Everything/source/SRPMS/autoconf-2.68-2.fc15.src.rpm&#10;$rpm -ivh webdot-2.26-1.el6.noarch.rpm&#10;$yum -y install graphviz-tcl&#10;$yum -y install python-zope-filesystem&#10;$yum -y install python-zope-interface&#10;$yum -y install automake&#10;$yum -y install autoconf&#10;&lt;/code&gt;&lt;/pre&gt;&#10;&lt;p&gt;add yum -y install openssl-devel this package is necessary if you use SSL with OpenVSWitch. (Thanks for input Marcos)&lt;/p&gt;</description></item><item><title>Top 10 Reasons I think SDN Openflow will gain momentum</title><link>https://networkstatic.net/top-10-reasons-i-think-sdn-openflow-will-gain-momentum/</link><pubDate>Fri, 04 Nov 2011 03:24:38 +0000</pubDate><guid>https://networkstatic.net/top-10-reasons-i-think-sdn-openflow-will-gain-momentum/</guid><description>&lt;h2&gt; Top 10 Reasons I think SDN Openflow will gain momentum &lt;/h2&gt;&#10;&lt;ol class="legacy-numbers"&gt;&#10;&lt;ol&gt;&#10;&#9;&lt;li&gt;Ridiculously high profit margins in the networking hardware market.&lt;/li&gt;&#10;&#9;&lt;li&gt;Content deliverers needing the flexibility that SDN’s claim to deliver in their data centers. To do anything they want with their network traffic, as opposed to trying to orchestrate the ever growing list of protocols and encapsulation methods in closed proprietary network operating systems.&lt;/li&gt;&#10;&#9;&lt;li&gt;Merchant Silicon- The typical lead time of developing custom ASICs is measured in numerous years. Off the shelf silicon can bring products in a fraction of the time. Custom silicon will still be used in many cases but chips and TCAM will need to be standardized to some degree. Hardware commoditization is likely inevitable just as it was in the x86 market. The Nexus 3064 is a classic example of reacting to Arista’s takeover of the low latency switching fabrics on financial trading floors where data availability advantages are measured in microseconds. Net is, this will bring the profit margins much closer to the x86 market.&lt;/li&gt;&#10;&#9;&lt;li&gt;Cisco and Juniper both signaling there will be at least some synergy with their product and SDN. We are likely to hear both of those companies repeat quite often that they have always been “software companies”. JunOS and IOS are the staples of both of those companies. They will stay ahead of it rather than sticking their heads in the sand in order to stay relevant. Fun trivia, the pilot switch used over two years ago by the Stanford research team was a Cisco Cat6500.&lt;/li&gt;&#10;&#9;&lt;li&gt;SDN can be deployed in a similar module horizontal fashion in the same way we bolt on growth today. MPLS compliments SDN incredibly well since it is another method of virtualization that can manipulate traffic in granular and dynamic ways. Proper abstraction layers are absent from networking. Monolithic devices with proprietary hardware, software and APIs will die the way IBM PCs did in the early 80s. Very few companies have been able to sustain high margins for commodity parts, except for Apple. That is differentiation in software, not silicon. That is what networking vendors will have to evolve to or lose market share.&lt;/li&gt;&#10;&#9;&lt;li&gt;I think SDN will be able to deliver the latest and greatest features significantly faster. It will also deliver or integrate protocols like TRILL, MPLS etc. I have a dream that I never hear “that is not supported in hardware” again.&lt;/li&gt;&#10;&#9;&lt;li&gt;A potential open standard OpenFlow as a base. However, I fully expect for vendors to have proprietary bells and whistles and pre-standards in their controller software. Standards bodies are slow and imbalanced, begin moving towards open source development models.&lt;/li&gt;&#10;&#9;&lt;li&gt;Simplified management and operations which will drive down OpEx much like we see with DevOps in hyper-scale business models today. Capture the entire infrastructure architecture by looking at significantly less devices to get a quicker holistic view of the network instead of crawling through thousands of devices loosely coupled by a bag of protocols. It would be nice to hit the print button of a controller to give a dynamic view of the network rather than digging up a 5 year old map and figuring out what is still there.&lt;/li&gt;&#10;&#9;&lt;li&gt;Security- Instead of punting your east-west data center traffic north for an expensive security policy application it could be done in the flow lookup routine along with every other black box we put in the data center i.e. load balancer, NAT etc.&lt;/li&gt;&#10;&#9;&lt;li&gt;Blah blah cloud.&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;/ol&gt;&#10;&lt;hr&gt;&#10;Predicting the future is often as easy as looking at the past, no crystal ball required.&#10;&lt;hr&gt;</description></item><item><title>The MPLS and transport roles merge</title><link>https://networkstatic.net/the-new-mpls-and-transport-roles-merge/</link><pubDate>Mon, 10 Oct 2011 02:17:03 +0000</pubDate><guid>https://networkstatic.net/the-new-mpls-and-transport-roles-merge/</guid><description>&lt;p&gt;The Juniper PTX in 2011 was a pretty bold merge of the OTN and MPLS functionality into one box.  They are marketing it as the &amp;ldquo;Converged Supercore&amp;rdquo; &lt;a href="http://www.juniper.net/as/en/dm/supercore/"&gt;&lt;a href="http://www.juniper.net/as/en/dm/supercore/"&gt;http://www.juniper.net/as/en/dm/supercore/&lt;/a&gt;&lt;/a&gt;. As the debate of packet vs. circuit switched networks has clearly been won by the packet side of the house. Arguably the the increasing demands of service provider bandwidth for triple play and cloud services and need for rapid provisioning of customer and provider needs that packet switched networks provide. We can now virtually provision circuit services via MPLS-TP/PBB-TE and reduce cost.&lt;/p&gt;</description></item><item><title>MVPN Multicast with Multi-Protocol BGP MPLS VPN on Cisco IOS</title><link>https://networkstatic.net/mvpn-multicast-with-multi-protocol-bgp-mpls-vpn-on-cisco-ios/</link><pubDate>Tue, 14 Jun 2011 02:14:26 +0000</pubDate><guid>https://networkstatic.net/mvpn-multicast-with-multi-protocol-bgp-mpls-vpn-on-cisco-ios/</guid><description>&lt;h2&gt;MVPN Multicast with Multi-Protocol BGP MPLS VPN on Cisco IOS&lt;/h2&gt;&#10;Below assumes you have the basic MPLS transport setup. MVPN or multicast vpn is deployed on Cisco gear using Multicast Distribution Trees (MDT). This information is encapsulated in the MPBGP MPLS sessions to be distributed into label switch paths (LSPs) for forwarding. The following code will produce a basic functioning Cisco IOS MDT multicast environment. A tutorial for that can be found in this post &lt;a href="https://networkstatic.net/basic-mplsvpn-using-cisco-ios/" target="_blank"&gt;Basic MPLS/VPN with Cisco&lt;/a&gt;.&#10;&lt;h2 class="legacy-heading"&gt;Configuring MVPN Multicast with MBGP MPLS VPN&lt;/h2&gt;&#10;&lt;p&gt;Global multicast configuration:&lt;/p&gt;</description></item><item><title>Death to the Firewall</title><link>https://networkstatic.net/death-to-the-firewall/</link><pubDate>Mon, 06 Jun 2011 20:00:11 +0000</pubDate><guid>https://networkstatic.net/death-to-the-firewall/</guid><description>&lt;h2&gt;Death to the Firewall&lt;/h2&gt;&#10;The Firewall will die soon. Blackbox hardware just doesn't make sense anymore. CPU is king when it comes to processing payload and that is commodity. SDN will put a nail in the custom hardware closed system soon enough. Until then, some musings on a project to collapse some functions into a router. Ironically, I can only collapse application processing into a router because the Quantum Flow RE is merely a bunch of Intel cores.&#10;&lt;hr&gt;&#10;&lt;ol class="legacy-numbers"&gt;&#10;&lt;ol&gt;&#10;&#9;&lt;li&gt;10gbps throughput with MPLS/VPN support to act as a PE node with MVPN support.&lt;/li&gt;&#10;&#9;&lt;li&gt;Traffic shaping and reduction of traffic.&lt;/li&gt;&#10;&#9;&lt;li&gt;Blacklisting of offenders who violate policy, DMCA/RIAA etc.&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;/ol&gt;&#10;Traditionally that would be a huge traffic shaping box that is through the roof if available at 10G speeds.&#10;&lt;p&gt;For route/switch, either a chassis based lan switch with MPLS support (overkill possibly). Other than the ME3600 (which we have some of but thats another long story) it is big chassis or ISR/ASR routers from each vendor. Juniper 4500 is sketchy on the documentation of whether it is just MPLS on the northbound uplinks.&lt;/p&gt;</description></item><item><title>Nexus 3000</title><link>https://networkstatic.net/nexus-3000/</link><pubDate>Wed, 01 Jun 2011 17:03:58 +0000</pubDate><guid>https://networkstatic.net/nexus-3000/</guid><description>&lt;p&gt;I think Cisco re-branded an Arista switch with Nexus 3000. Low latency financial market oriented with merchant silicon. lolz&lt;/p&gt;</description></item><item><title>How to deploy MPLS VPN's on Cisco gear</title><link>https://networkstatic.net/how-to-deploy-mpls-vpns-on-cisco-gear/</link><pubDate>Sun, 29 May 2011 17:27:43 +0000</pubDate><guid>https://networkstatic.net/how-to-deploy-mpls-vpns-on-cisco-gear/</guid><description>&lt;p&gt;There is no easier way to simplify your enterprise routing and path isolation than implementing MPLS/VPNs RFC 4364. Label Distribution Protocol (LDP) is the transport method to insert a label into the header to be forwarded down the Label Switch Path (LSP) by the Label Switch Router (LSR)&lt;/p&gt;</description></item><item><title>Brent Salisbury's Bio</title><link>https://networkstatic.net/bio/</link><pubDate>Sat, 28 May 2011 02:58:48 +0000</pubDate><guid>https://networkstatic.net/bio/</guid><description>&lt;h3&gt;Brent Salisbury's Bio&lt;/h3&gt;&#10;&lt;hr&gt;&#10;I have over 20 years of networking and compute experience wearing various hats from, network engineer, architect, ops and software engineer. &#10;&lt;p&gt;Complete bio can be found on &lt;a href="https://www.linkedin.com/in/brentsalisbury/"&gt;LinkedIn&lt;/a&gt;&lt;/p&gt;&#10;&lt;hr&gt;</description></item><item><title>Search</title><link>https://networkstatic.net/search/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://networkstatic.net/search/</guid><description/></item></channel></rss>