How Does This Help Aruba Networks?

I was going over my YouTube subscriptions tonight, as I do at least once a week, and came across this video from Aruba Networks:

While I do love watching things go through a shredder, I fail to see the point of this video. It begs the question: Who watches this and would this video change their mind?

In my opinion, this video is aimed at a non-technical buyer. If you make a significant investment in Aruba based on this video, I have serious concerns about your ability to make sound judgements when it comes to technology. That is not to say that the AP-225 from Aruba can’t beat a Cisco 3702 AP in testing. I honestly don’t know. I have access to both AP’s, and I suppose I could run my own independent tests, but to what aim? I certainly don’t have 20 laptops laying around to run my own version of this test, and I am struggling to locate the exact testing methodology used on the Aruba website. The video mentions that Aruba publishes the exact test they performed. I assume it is available somewhere. There was nothing in the video description, so I suppose I have to do Continue reading

40th Anniversary of the TCP Protocol

40th Anniversary of the TCP Protocol

by Brian Boyko, Technology Contributor - May 20, 2014

In May of 1974, the IEEE published a paper titled “A Protocol for Packet Network Intercommunication.” The authors were Vint Cerf and Bob Kahn. 

Forty years later, the protocol they developed, TCP, is still the undisputed king of “sending stuff.” It’s no longer alone in packet types, but we still use the conventions for routing and interconnecting networks that TCP established, and the basic operation hasn’t changed since 1974.

It’s a brilliant design; one that, at its most simple, comes down to a single idea: it doesn’t matter where the packets come from, how fast they get there, what order they get there, or even how many copies there are of that packet on the network - so long as they get there. 

The TCP receiver can simply reassemble the sequence as it was originally transmitted, and double-check with the sending computer to ensure accuracy. The TCP slow-start means that it automatically determines the safe rate at which to send packets.

The upshot of all of this has been that TCP enabled, for the first time, the building of robust Continue reading

Show 189 – Connecting VMware to the Network

I managed to get Chris Wahl to sit down for a while and talk about where VMware ESX and networking connect. In this podcast we talk through the nature of the “VMware vSwitch” and how it’s advanced patch panel capabilities can be integrated with the physical network. Chris is well known figure in the VMware scene and recently […]

Author information

Greg Ferro

Greg Ferro is a Network Engineer/Architect, mostly focussed on Data Centre, Security Infrastructure, and recently Virtualization. He has over 20 years in IT, in wide range of employers working as a freelance consultant including Finance, Service Providers and Online Companies. He is CCIE#6920 and has a few ideas about the world, but not enough to really count.

He is a host on the Packet Pushers Podcast, blogger at EtherealMind.com and on Twitter @etherealmind and Google Plus.

TwitterFacebookGoogle+

The post Show 189 – Connecting VMware to the Network appeared first on Packet Pushers Podcast and was written by Greg Ferro.

When Vision Becomes Reality

plat . form

/’patfÔrm/

noun

  1. an underlying computer system on which application programs can run

Working at a start-up that’s trying to create an entirely new way of doing something can take your emotions on a roller coaster ride. One minute you’re loving the fact that you’re working your tail off to create something new, innovative and different; and the next minute you’re frustrated because change takes time and you want to prove that the vision the team is chasing, but not everyone is there yet.

For the Embrane family, today is a moment when we’re reminded why we put in those hours and push through those challenges.

If you’ve followed the Embrane story, you know we’ve been touting our plans to be THE platform for delivering virtual network services to enterprises and service providers. The vision Dante and Marco had when they started Embrane was that the Embrane heleos platform not only would power our own agile network services, but we would deliver that value to third-parties. We’ve listened to our customers, identified trends and evolved our solution to prove our platform was indeed a system on which application programs can run. We spent countless hours building the premier platform Continue reading

DEMO: Using Ansible for Network Automation

There is so much discussion on if network engineers need to be programmers that I was almost getting pissed off last week.  It was an odd and funny feeling.  Anyway, I've written in the past here and here about the use of Ansible for networking.  In this post and video, the goal is to show why network engineers don’t need to be "hardcore programmers."
Below is a short demo of using Ansible to automate basic network configuration tasks on Cisco routers.  As more Ansible modules come out (or any other tool that does the job), we will quickly realize, the network engineer doesn’t need to be a “hardcore programmer,” but rather understand the tool and articulate the requirements such that new modules can easily be added by others.  If the tools we’ll have in the future are “platforms” that can be customized by the consumer/customer meaning the vendor isn’t required to add more functionality, then that’ll pretty awesome for both the network engineer and the business.  It’s a win win.

FYI- the modules being demo’d are leveraging Cisco’s onePK as the API to connect to and make changes to the routers.

Hope you enjoy. Continue reading

Winning With Ecosystems

Back in 2010, I wrote a post entitled “Competing With Cisco”. It has been a few years, and since I have been in the VAR space for almost 3 years now, I have a slightly different perspective. One thing I didn’t really touch on too much in that article was the powerful ecosystem that surrounds Cisco. I’ve seen it win many deals over the past several years and thought it was worth writing about. Perhaps you already know the power of that ecosystem.

I feel sorry for smaller technology vendors. They face an uphill climb when going against the 800lb gorillas. Interestingly enough, I have often wondered about that phrase. Perusing the Wikipedia article on “800lb gorilla”(That site really does have everything!), it gives a riddle:

Q: Where does an 800lb gorilla sit?
A: Anywhere it wants to.

For people within the greater networking space, that 800lb gorilla is Cisco. It has been that way for a number of years, and will likely continue that trend for years to come. Although there are numerous competitors, time and time again, they fail to take substantial market share from Cisco. While Cisco does make many fantastic products, there Continue reading

The RedHat controversy

Several articles, including one in the Wall Street Journal
hit the press last week regarding RedHat policy of only supporting RedHat guests in RedHat Linux, VMWare or HyperV Hosts.

While this policy had probably been around for a while, several RedHat customers i work with have recently changed their deployment plans towards having dual hypervisor sulotions (ubuntu + RHEL) in order to be able to run RHEL hosts under support.

RedHat seems to be using this tatic to stem its market share loss in the virtualization and OpenStack hypervisor space. In a blog post, RedHat seems to imply that its competitors providing Linux hosts “cavalierly compile and ship, untested OpenStack offerings”. Ironically, several people that i spoke with last week have echoed the opinion that RHEL 6.x is rather problematic for a cloud deployment, questioning whether it can be used in production.

One cloud provider that i spoke with, immediatly replied that they had to replaced the kernel and KVM versions in their CentOS 6.x version when i questioned thier choice of OS distribution. This seems to match the general consensus of what I hear through the grapevine. I understand than an anecdote is not data but in the Continue reading

The To DS and From DS Fields

Currently I’m studying for the Certified Wireless Analysis Professional (CWAP) exam and I’m rereading the study guide and I found the chapters that examined the different fields and elements present in the MAC header most interesting. I had a rough idea, but during my studies learned a great deal more about the unique fields and elements dedicated to wireless that keep the network functioning and help packets get delivered. Two fields of particular interest are the To Distribution System (To DS) and From Distribution System (From DS) and how these fields determine if the frame is leaving or entering the wireless environment.

Distribution System

Just a quick definition of the distribution system and basically the DS is the infrastructure that connects multiple access points together to form an Extended Service Set (ESS). The DS is typically an 802.3 Ethernet wired network, but it doesn’t have to be, and the DS can even be a wireless back haul.

MAC Header & Frame Control Field

Lets now look at the MAC header which can contain four address fields. The number of address fields is a major difference between Ethernet frames, which only use two address fields, and wireless frames that could Continue reading

Role inversion

At the OpenStack summit in Atlanta this week there was a very interesting phenomenon. Vendors that have been traditionally positioned in the I.T space seemed to be directing their energy around OpenStack on the carrier / telecom space; while vendors traditionally in this space where doing the best they could to get beyond it and into non-traditional I.T deployments.

As an example, canonical’s booth was primary advertising their “Carrier Class OpenStack” and RedHat seemed very interested in NFV; with several senior developers organizing a cross project NFV subteam to focus on how OpenStack can be a better fit for carrier data-centers.

The traditional telecom vendors on the other hand seemed to be rather less sanguine on the NFV market. At least when it comes to the timelines required to get to production deployments: 2018 seems to be a reasonable target.

I don’t currently have access to market research data; but i would be very curious to take a look at it and how it is being interpreted. Either the I.T. vendors are over-investing or the traditionally Service Provider focused vendors are under-investing in this space. Cisco, for instance, which is typically quite business savvy is nowhere to Continue reading

OpenContrail at the summit

There was a lot happening at the OpenStack summit in Atlanta this week. I got the opportunity to meet several of the most active OpenContrail developers; and envangilize the project with several people that are looking for an OpenStack networking solution that meets their needs.

The buzz on Neutron can be sumarized by: the default implementation of neutron doesn’t work. Many users find that running neutron service rack with l3-agent and dhcp agent isn’t working out for them: the neutron router is a choke point for traffic; there is no resiliency and some of the services (e.g. DHCP) are prone to melt down. This seemed to be the rought consensus of those who i spoke with (admitedly a rather un-scientific sample).

It is easy to explain the advantages of the OpenContrail implementation in this context. By implementing a fully distributed router implementation as well as distributing the DHCP, metadata proxy and floatingip functionality, OpenContrail solves most of the current pain points of Neutron.

On the other side, some of the users I spoke to where often concerned with the relativly small size of the community. Hopefully this weeks annoucement of the OpenContrail Advisory Board will help aliviate this concern. Continue reading

Cisco Live US 2014 is upon us!

  Just wanted to put out a quick post and wish all the attendees, exhibitors, and staff safe travels! I know we all have a busy and exciting week ahead of us!  Make sure you stop by the Social Media lounge and say hello and meet some new friends. The social media lounge is in Moscone […]

My pinboard bookmarks for 17 May 2014

Things of note that were discovered on the web this week.

CriticMarkup

Can't do editing in Markdown eh? Obviously you haven't seen CriticMarkup. Looks very cool indeed!

markdown

java - Excluding tests from being run in IntellIJ - Stack Overflow

This is how to exclude integration tests being run in IntelliJ I've been using this for unit testing the OpenDaylight OVSDB library with the regex ^(?!(^.*(IT).*?$)).*$ and it works well!

intellij, java, testing, junit

Maven Troubleshooting FAQs

A presentation with troubleshooting Maven issues which is a necessary skill if you plan to do any development in Java.

java, maven

Elephant Detection in the vSwitch With Performance Handling in the Underlay

As we’ve discussed previously, the vSwitch is a great position to detect elephant, or heavy-hitter flows because it has proximity to the guest OS and can use that position to gather additional context. This context may include the TSO send buffer, or even the guest TCP send buffer. Once an elephant is detected, it can be signaled to the underlay using standard interfaces such as DSCP. The following slide deck provides and overview of a working version of this, showing how such a setup can be used to both dynamically detect elephants and isolate mice from queuing delays they cause. We’ll write about this in more detail in a later post, but for now check out the slides (and in particular the graphs showing the latency of mice with and without detection and handling).


Lying Headline From Business Insider: Cisco Is Going To Crush VMware

Received an email about this article Chambers: Cisco Is Going To Crush VMware – Business Insider. The title  strongly suggests that John Chambers said “Cisco is going to crush VMware” but it’s a lie. The closest that the article content gets is: A cheerful John Chambers told Wall Street analysts on Wednesday that his plan to crush […]

The post Lying Headline From Business Insider: Cisco Is Going To Crush VMware appeared first on EtherealMind.

Could Cisco ACI Kill APM?

APM TargetNote – This is ALL 100% speculation on my part. I may be WAY off base with what you are about to read, and if you know something I don’t, feel free to correct me in the comments below.

I attended the Cisco Live Local Edition event here in Nashville,TN last month. It was an all day event that gave a variety of presentations in different focus areas. While I spent the bulk of my time in the routing/switching/wireless/security presentations, I made a point to sit in on one in the data center track. It was entitled Data Center Fabric Futures. This session spent a lot of time talking about Cisco’s Application Centric Infrastructure(ACI) technology, so I was curious to learn a bit more about it since the company I work for sells a fair amount of Cisco Nexus switching.

If you want a little more information about Cisco’s ACI technology, here’s some really good writing on that subject:

Insieme and Cisco ACI [Part 1] – by Matt Oswalt

Insieme and Cisco ACI [Part 2] – by Matt Oswalt

Cisco’s ACI (Insieme) Launch – by John Herbert

While the presentation was moving along, one particular aspect of ACI caught my Continue reading

Pseudowire FAT Interoperability

I usually don’t think much about Pseudowires Sub-TLV until I encountered two IOS-XR boxes that didn’t use the same value and didn’t forward any packets. There is a special corner case of pseudowires using Flow Labels Transport (FAT) that can cause unexpected behavior and if you don’t watch out you might drop traffic. In this post I’ll go over the details of using FAT with different IOS-XR versions and what can go wrong.

Flow Aware Transport  pseudowire (RFC6391) is a type of L2VPN that operates over MPLS. The main benefit of it is that it implements a mechanism which allows you to load-balance one pseudowire over multiple equal cost paths (i.e. ECMP). ECMP of a pseudowire becomes an advantage when transporting large amount of traffic such as 10Gbps or more. FAT is a special interface sub-TLV that’s negotiated between two PE.

The problem relates to Flow Aware Transport (FAT) pseudowires where one side terminating router operates the IOS-XR version 4.3.2 and the other any version up to 4.3.1. The symptom is lack to forwarding of tunneled packets. Both sides show PW as up and operational but no traffic is being forwarded over it. Continue reading

1 … 3,688 3,689 3,690 3,691 3,692 … 3,791