CCIE or Null!

My journey to CCIE!

Posts Tagged ‘Networking Field Day

Networking Field Day – Afterwards – Brocade SDN

with 4 comments


I wanted to start off stating Brocade broke one of the biggest barriers with getting involved with SDN and labbing out the technology. Brocade offers a free download of their Vyatta Controller! With this free download you can run a 5x node SDN network for one year, included with 60x days of support! This eliminates a huge obstacle of actually purchasing the software, sure you may still require the hardware but Brocade SDN Solution features support for OpenDaylight/OpenFlow so you do have many different hardware options.

Now, that I got that out of the way my two favorite pieces of the Brocade was 1. The technical overview of the Vyatta controller and it’s architecture, it was great to see how to the services overlay on each other and what makes it tick. Usually when it comes to some type of SDN solution it’s usually presented as some type of application that does magic. In this case however Brocade definitely did their due-diligence to cover how their controller actually functions. The 2nd thing I loved about this presentation was just how frank and up-front the presentation was. My favorite quote of the whole the presentation was “We know how to code, we went to school. We chose not to program we went into networking.” I can’t say how happy I was to hear someone actually say this! However like it was mentioned in the presentation it appears to be a natural evolution of the field.

As the presentation continues, you really get a sense about how far along the Vyatta controller has come along once the conversation steers towards volumetric traffic management. Having the additional and built-in monitoring of the traffic flows with sFlow and OpenFlow addressing a level of application performance management many current-day data centers frankly do not even have in place today just shows how grown up the tool is becoming. This is built upon again with the flexibility to handle elephant flows differently than other typical data flows, if you are not familiar with the term elephant flows these are just traffic flows that transfer a very high amount of traffic (IE: Something like backup traffic). I can’t tell you how many few companies I’ve worked with in the past that have actually taken into account these ‘elephant flows’.

Now, I don’t want to ruin the whole presentation for you, if you have not watched it yet I highly recommend you give it a watch. There also a great slide in there about Ivan! If you think SDN is still a mystery it’s time to get that Vyatta controller downloaded and running! No more excuses!

You can download the Vyatta Controller here.

Brocade’s Networking Field Day #9 videos can be found here:

Brocade Vyatta Controller

Brocade VDX & NOS Program-ability

Brocade SDN & NFV Update

Brocade Traffic Management Application Review

Written by Stephen J. Occhiogrosso

March 12, 2015 at 7:33 PM

Networking Field Day – Afterwards – Cisco ACI

with 3 comments

I first need to give a shout out to @_vCarly and her amazing skills at the white board, I only wish my white boarding design were half clean as that! If @_vCarly were to a host a white boarding session at CLUS this year I would most likely attend!


I suppose we should discuss the actual presentation now! Like probably many of you I have heard an awful lot about Cisco SDN and Controllers (Cisco ACI) however until now it has all been theory and hear-say. I can finally say I’ve seen the GUI and got to hear a deep dive of how this new architecture is supposed to work. Now, that I have seen it I am believer there is a lot of potential here and allow us to re-think the way we consider designing Data Center networks and here is why I think that:

  1. Building around the application, with this new design model we are almost forcing the application designer & server administrations to tell how their servers/applications work and communicate on the network. I have a spent a lot of time with AppDev’s going over what their application does and what else the App communicates in order to troubleshoot an issue. This approach removes much of the hassle without ever seeing the hassle. Future engineers might not know ‘the struggle’ of discovering an application via packet analysis and bridge calls.
  2. Deployment Orchestration – by specifically calling out the application and the service chaining from the get go, deploying a new application is much more streamlined and simplified in the long run when internal process are stream-lined. Eliminating the time-consuming need to:
    1. Login to multiple networking devices to configure SVI’s & Trunks
    2. Login to multiple firewalls creating the appropriate rules.
    3. Login to Load balancers and creating devices pools, health monitoring, virtual servers, and so forth.
  3. Troubleshooting and flow monitoring – Out of the box this box will be watching flow statistics. So tracking traffic statistics can easily pin-point packet loss and drops. Which may mean bad news some of the simpler NMS solutions out there unless they start looking beyond the typical Up/Down & Interface utilization mantra.
    1. Something that was brought up on Twitter post-event was the support for SNMP, which is a great question since SNMP was never mentioned (in any of the SDN-related presentations for that matter).

Now, with all that said and the fact Cisco ACI builds a Data Center around EPG’s (End Point Groups) I really look forward to this new design architecture. It’s probably going to be a bit more tedious up front since some applications will need to be called out specifically instead of going “O, that is a web server. Place it on this VLAN” but in the long run this will streamline many different parts of data center operations.

Links to the Networking Field Day 9 presentations below:

Understanding the Cisco ACI Policy Model

Cisco ACI Overview w/ Soni Jiandani & Joe Onisick

How Device Connect to the Fabric

Cisco ACI Demo w/ Carly Stoughton

Written by Stephen J. Occhiogrosso

February 23, 2015 at 9:00 AM

Networking Field Day – Afterwards – NetBeez & Wireless Monitoring

with one comment


Well, Networking Field Day 9 has ended, it was a very quick, fun and informative three days.

I have to start by giving NetBeez a lot of respect for the great presentation, and I that same I almost want to apologize for the suggestions and feedback that we (All the delegates) bombarded them with during their presentation. They were certainly taking notes of our suggestions and even questioned our suggestions.

Now, NetBeez’s big announcement during this event was the availability of a ‘Wireless’ NetBeez. (If you are not familiar with NetBeez in general I recommend swinging back around to my previous post about their product). Which in my own opinion is a great addition their product. Having your own client node monitoring various key points of the network recording WLAN statistics provides a whole new level of WLAN monitoring that we do not currently have from the client level (or something I have not seen next).

  1. When we start talking about monitoring WLAN’s I see a lot of untapped potential to spearhead into many different industries:
    • Manufacturing
    • Distribution
    • Warehouse / Inventory

These industries usually consider their WLAN’s and their accompanying WLAN Applications to be mission critical, and without these key elements the entire operation can shut down costing large amounts of money. So I can easily see NetBeez pushing into these industries. One thing I want to see is a more rugged-ized model since these environments don’t tend to be very inviting.

Being able to track both application & WLAN level statistics from different locations of the wireless network can identify issues before they happen either at the access point or from an upstream distribution switch. Which to me offers a great value add to anyone who must manage large distributed WLAN’s. This little device provides some much needed visibility across the entire network path incorporating but Wired and Wireless statistics.

I am looking forward to kicking the tires on this NetBeez product and I am looking forward to any new features that gets rolled into their products.


If you missed the live presentation, you can view the recordings here:

Introduction to NetBeez

The nuts and bolts of NetBeez

NetBeez Live Demo

Written by Stephen J. Occhiogrosso

February 17, 2015 at 9:54 PM

Networking Field Day 9: First look- Monitor the network with NetBeez?!

with one comment

With Networking Field Day #9 quickly approaching, I can’t help but start digging into the presenters and see what they currently offer.

In reviewing the presenters at Networking Field Day #9, one of them NetBeez offers an interesting take on network monitoring. I must admit this is one of the presenters I needed to do a little research on. Now, when I first went to the NetBeez homepage, the first thing I noticed was what they provide and bring to the table:


How many companies state they provide ‘end-user monitoring’ this to me is a unique twist on network monitoring. Think about it we have Application Performance monitoring, network device monitoring, traffic flow monitoring, & many others but end-user monitoring is not usually something you hear about too often.

Like many of us have, I have been using IP SLA across many networks to give me a perspective as to what the user what might be experiencing. While this is a good idea it is however slightly flawed in my opinion, my reasons below:

  1. It’s not really from the user’s perspective. (Usually)
    1. Usually the IP SLA is configured on a distribution or core device. NOT from the access layer.
  2. IP SLA does not scale very well.
    1. How are you going to manage all these IP SLA’s?
    2. You need to be careful when/where configuring or terminating a large number of IP SLA’s on individual routers, they require resources to run! You can very easily go overboard!
  3. Reporting and monitoring.
    1. Can you report on the IP SLA statistics? How long were response times above a certain threshold vs. within a reasonable expectation?

However, after reviewing NetBeez I see some potential. As their solution does appear to address some of those concerns & flaws:

  1. True user perspective
    1. NetBeez devices can be connected directly to the access layers, providing a network perspective AS A REAL USER. Albeit at the cost of a single switchport.
  2. Scalability
    1. The NetBeez devices are managed from one central management console, easing the management of this monitoring solution to a single console.
    2. Now your infrastructure devices simply need to pass packets in the data plane and service clients not worrying about the additional load of the IP SLA processes.

Now these are just some of my initial impressions, I am quite curious to see this product in action,  to see if they live up to my impressions, and what they have in store for the future. In my opinion this product has a lot of untapped potential.

A few things I am curious about:

  • Cost – I’ve worked with many companies were I could easily deploy 50 to a few 100 of these little devices. Many of know the budget is a big decision maker, can these useful little guys break the budget?
  • Consolidated Data views – Deploying a lot of these guys might get overwhelming quickly and I am curious how efficiently this data can be summarized.
  • Reporting – With all this useful information I am wondering if the data is kept for historical purposes and can be reported on later. I think being able to report on response times for the various applications (HTTP, DNS, etc) can easily provide trending capabilities after a 3 month time frame.
  • Support for additional applications, or advanced monitoring capabilities- Many companies will be running some type of home grown application, can NetBeez devices be configured to perform simple TCP handshakes over specific TCP ports? What about taking HTTP monitoring a step forward and navigate down a few pages instead of a single HTTP GET, maybe even reporting on individual page elements. eCommerce is a very large and metric driven business that could definitely benefit from advanced HTTP monitoring.
  • Most importantly can we run monitors between different NetBeez devices

Now, don’t think of those curiosities too harshly, network monitoring is a topic I tend to be overly critical about (Just ask anyone I have worked with)

With all that said I this should be a very interesting presentation, and one I am looking forward to.

Written by Stephen J. Occhiogrosso

February 3, 2015 at 9:45 PM

%d bloggers like this: