I ran into an unexpected issue the other day that kept me scratching my head for a few minutes when a new ASA refused to take a code upgrade. Read on for the details.
Over the last couple of years, two major philosophies for SDN have evolved which I will call the overlay model, and the flow programmability model. Overlay networks are the notion of building multiple virtual networks in parallel on top of a physical network fabric, using some means of separating the virtual networks — typically an encapsulation method like VXLAN or NVGRE. Then we have the “flow programmability” model, based on the idea of programming SDN behaviors on a flow-by-flow basis into your existing (or new) physical and virtual network switches using a protocol like OpenFlow.
Virtualization, Storage, and other techy stuff
I ask those questions you're too clever to.
Pluribus Networks Founder's Blog on OS, Networking, Virtualization, Cloud Computing, Solaris Architecture, etc
Just another WordPress.com weblog
Data networking, stray thoughts, nerdy fun...
Tales of the network reformation
Jottings on the intersection of tech and humanness
Ramblings about my thoughts, experiences, and ideas.
Looking for the next big thing.
A Network Blog by a Network Engineer
Attaining my CCIE with the help of Warhammer 40k
just another networking blog
Network Architect . CCIE 17846 . CCDE 2012::1
Making Packets Do Silly Things
Jonathan Davis (@subnetwork) keeps layers 1-7 working so that Layer 8 can be productive.