From the blog.

Managing Digital Racket
The more I tune out, the less I miss it. But that has presented me with some complex choices for a nuanced approach to curb
Complexity – My Friend, My Enemy
Over my years of network engineering, I've learned that the fewer features you can implement while still achieving a business goal, the better. Why? Fewer

My Presentations at Interop NYC 2013

686 Words. Plan about 4 minute(s) to read this.

interop-nyc-2013-logoI am booked to present in three sessions at Interop NYC 2013. Here’s the big ideas behind them.

1. How To Set Up Network QoS for Voice, Video & Data. This is a 3 hour session targeted at enterprise engineers, designed to give an end-to-end perspective on practical QoS in a converged campus network, using Cisco gear by way of example. I haven’t formally written the presentation yet, but the rough brainstorm outline looks like this so far:

Hour 1 – Techniques & Theory – describe the tools available to implement QoS.

  • Marking – IP ToS, precedence, DSCP, PHBs, CoS, 802.1p, ToS reflection, NBAR
  • Policing
  • Shaping
  • Committed access rate
  • Low latency queuing
  • Random early detection
  • Determining queue depth
  • Clock cycles
  • Hardware ring

Hour 2 – An Enterprise Strategy

  • Know your traffic. Why is some data tolerant of loss, and some not?
  • Create classes.
  • How many classes is too many?
  • Mark at the edge.
  • Map marks from L2 to L3.
  • Preserve marks.
  • Cisco’s AutoQoS – what’s it really do?
  • Mapping traffic from LAN DSCP to  WAN carrier PREC.
  • Why can’t QoS fix having too small of a pipe? (Assume by “too small” we mean that the pipe is at 100% of capacity for extended periods of time.)
  • Preserving marks across WAN optimizers, firewalls, load-balancers
  • Wireless QoS techniques

Hour 3 – Configuration Examples

  • Applying QoS with tunneled traffic (GRE/IPSEC)
  • Throttling a bandwidth hog
  • Cisco AutoQoS
  • DSCP mutation map
  • WAN router with classes of voice, video, call signaling, and scavenger
  • Nesting a policy inside of a shaper due to a fat carrier handoff that’s throttled downstream
  • ASA firewall SOHO kit (VoIP over the Internet)

2. Cisco Switching Alternatives, Part 1 & Part 2. I believe that the enterprise switching market offers a number of worthy competitors to Cisco. The goal of this 2 hour session is to introduce the audience to the product lines from several non-Cisco vendors and explain their differentiators. In the first hour, I’ll hit the more traditional players like Juniper, IBM, Enterasys, Brocade, and HP. In the second hour, I’ll finish up with the conventional players, but then plan to get into the more radical switching approaches from vendors like Plexxi, Pica8, and Gnodal. Interop has set this up as 2 1-hour sessions, so if you want to catch the entirety of my blathering, register for both sessions.

I haven’t worked up an outline for this one as yet, but the idea is to talk briefly about the Cisco Ethernet switch lineups to set a baseline (they have the greatest market share, after all), and then start going through what competitors are offering. Time permitting, I’ll create a buyer’s guide matrix. No promises on that, but I can see such a thing being a useful resource.

3. Will SDN Make Me Homeless? This is a panel discussion with Greg Ferro, Michele Chubirka and Brent Salisbury. We’re going to mix it up probably podcast-style, and talk through the trends of SDN, automation and orchestration. The context is the impact these new technologies will have on the day-to-day life of the network engineer.

The four of us haven’t got our heads around an outline for this one quite yet, but all of us have written on this topic and fielded questions on this from listeners of the Packet Pushers podcast or readers of our blogs. So, it’s not like we don’t have opinions already, plus we’re all coming at it from different angles. I’m coming from the standpoint of the network engineer who’s digging into applying overlays and automation to enterprise networks that look more & more like service providers. Brent is out on the bleeding edge where the oxygen is thin and the territory uncharted, doing SDN & OpenFlow stuff the rest of us are just reading about. Michele is in the security realm, wondering how SDN is going to change the security paradigms most folks use today. Greg has been doing high-end consulting for a cloud company, as the resident “Cloud Plumber” at Canopy Cloud, where he’s been eschewing hardware in favor of software-instantiated everything. So, yeah. We have our take on what SDN means for network engineers. Should be a fun panel.