After three consecutive months attending 75 customer meetings throughout the U.S., Europe and Asia, I came away with plenty of frequent flyer miles and, more importantly, tons of insight to share with you.
What I learned from customers is that VMware NSX is truly a game-changer. And as we exit the second quarter, the list of customers excited about NSX is only getting bigger. We recently announced that we have grown from more than 150 VMware NSX customers a year ago, to more than 700 customers today. These customers are setting the stage for others to follow. They are providing best practices that we are feeding back to others, and giving us valuable insight into challenges they encounter along the way.
So as I promised, I’ve pulled together highlights from these meetings and condensed them into three key themes that emerged. For you IT pros out there reading this, let me know if any of this sounds familiar.
1. The story remains the same
For years, IT has been complaining that it takes minutes to spin up applications, and weeks or months to provision the network and its associated services to support the application. As one Continue reading
How does Internet work - We know what is networking
This is really cool feature on Cisco router not usually mentioned until you dig a little deeper inside Cisco IOS. But first a bit of theory… What is TCP SYN flood attack TCP 3-way handshake SYN flood DoS attack happens when many sources start to send a flood of TCP SYN packets usually with fake source IP. This attack uses TCP 3-way handshake to reserve all server available resources with fake SYN requests thus not allowing legitimate users to establish connection to the server. SYN packet is the first step in TCP 3-way handshake where client sends connection synchronization request
Matt Oswalt wrote a great blog post complaining about vendors launching ocean-boiling solutions instead of focused reusable components, and one of the comments his opinion generated was along the lines of “I thought one of the reasons people wanted SDN, is because they wanted to deal with The Network – think about The Network's Performance, Robustness and Services instead of dealing with 100s or 1000s of individual boxes.”
The comment is obviously totally valid, so let me try to reiterate what Matt wrote using Lego bricks ;)
Read more ...After some great feedback and some additional learning/fixes on my end, I wanted to make an updated version of this post.
This go around, I’ve added some plugins I found helpful as well as made a couple of tweaks that I think (not sure yet) will be helpful to me going forward. So here is the brand new build script I came up with…
#Install dependancies and neccessary packages yum -y install golang git vim wget python-devel cmake yum -y groupinstall "Development Tools" #Modify your bash_profile... vim ~/.bash_profile #Add this config... export GOPATH=$HOME/go #Source the file source .bash_profile #Make the golang workspace mkdir ~/go mkdir ~/go/bin mkdir ~/go/pkg mkdir ~/go/src #Install and configure Vundle... #Pull down Vundle git clone https://github.com/gmarik/Vundle.vim.git ~/.vim/bundle/Vundle.vim #Edit your .vimrc file... vim ~/.vimrc #Add this config... set nocompatible filetype off colorscheme molokai set rtp+=~/.vim/bundle/Vundle.vim call vundle#rc() Plugin 'gmarik/Vundle.vim' Plugin 'nsf/gocode', {'rtp': 'vim/'} Plugin 'fatih/vim-go' Plugin 'Valloric/YouCompleteMe' Plugin 'scrooloose/nerdtree.git' filetype plugin indent on "Prevent autocomplete help from staying visisble autocmd CursorMovedI * if pumvisible() == 0|pclose|endif autocmd InsertLeave * if pumvisible() == 0|pclose|endif "Quit VIM if NERDTree is last open Window autocmd bufenter * Continue reading
As I've written about previously (The Importance of BGP NEXT_HOP in L3VPNs), the BGP NEXT_HOP attribute is key to ensuring end to end connectivity in an MPLS L3VPN. In the other article, I examine the different forwarding behavior of the network based on which of the egress PE's IP addresses is used as the NEXT_HOP. In this article I'll look at the subnet mask that's associated with the NEXT_HOP and the differences in forwarding behavior when the mask is configured to different values.
There is a lot of (mis-)information on the web stating that the PE's loopback address — which, as I explain in the previous article, should always be used as the NEXT_HOP — must have a /32 mask. This is not exactly true. I think this is an example of some information that has been passed around incorrectly, and without proper context, and is now taken as a rule. I'll explain more about this further on in the article.
Templeton is out, Elliott is in.
The OpenDaylight Summit kicks off with an open source battle cry.
Don't worry if you missed out on Sonus' DemoFriday on business continuity. Sonus answered audience's questions following the demo.
Startup taps Mirantis as first partner.