WLPC Conference Day 1 Highlights

I'm here at the WLAN Professionals Conference (#WLPC if you're following on Twitter). This is the first of what hopefully will turn into an annual conference dedicated to the Wi-Fi industry. But this conference is a bit different than what you might think a typical conference is. First and foremost, it's got a grassroots, peer-to-peer focus. It's engineers talking about Wi-Fi and gathering for discussion. It's not overly promoted by vendors or full of presentations with marketing drivel. Instead, it's just people who are passionate about this technology coming together to share their knowledge and experiences with each other to better everyone! What a great concept!

There are over 100+ attendees, many of whom are also presenters. I hear there was more demand than seats available, so next year Keith Parsons, organizer of the event, should have a solid baseline to grow the conference and allow more of you (the community) to attend and get involved. What's also great is that many of the presentations have been interactive, with great questions and quality discussion fostering the entire group to share information. The focus on the technology instead of the marketing that so often surrounds the technology and products Continue reading

CEF Secret Attributes, Part 3

In Part 1 we saw we can mark prefixes in CEF with certain attributes that might give us interesting things to play with. In Part 2 we found we could track traffic patterns with the traffic_index tag. We will now turn our attention to the qos-group parameters. Let’s say we would like four categories of […]

Author information

Dan Massameno

Dan Massameno is the president and Chief Engineer at Leaf Point, a network engineering firm in Connecticut.

The post CEF Secret Attributes, Part 3 appeared first on Packet Pushers Podcast and was written by Dan Massameno.

interoperability testing

Recently, one customer prospect asked the Contrail team to build a POC lab using only non-Juniper network gear. The team managed to find a cisco ASR 900 as a loaner device and we had to make that device work as a data-center gateway.

Typically we use the Juniper MX as a the data-center gateway in our clusters. When you use an MX, the system somehow feels dated. It does feel like a 10+ year old design, which it is. But it is incredibly solid and feature rich. So one ends up accepting that it feels a bit dated as a tradeoff to its “swiss army knife” powers.

The cisco ASR 900 belongs to the 1k family and runs IOS as a user space process on Linux. I’d not used IOS in 3 years. My first impression was: this artifact belongs to the Computer History Museum. In fact the CHM (which is a fantastic museum) has several pieces in exhibition that are more recent that 1984, the year IOS debuted.

And IOS (even the version 15 in this loaner box) is a history trip. You get to see a routing table that precedes classes internet addresses, the config still outputs “bgp Continue reading

Leveraging Python on Network Devices to Monitor Interfaces in Realtime

In a recent post, I wrote about some Python work I was testing on the Nexus 3000.  The end conclusion was that open Linux platforms will offer more flexibility --- for the consumer of the technology, ultimately the customer.  In this post, we’ll take a look at an example that integrates Python with the native Linux operating system.  
In the context of networking, the question often arises, what does having access to Linux really gain you?  For one, as you can see from my last post and you’ll see in this one, for native scripting within bash and Python is of extreme value in itself, not to mention you’d also have the ability to load any piece of software you want to that is compatible with Linux (think about tools, mgmt/monitoring platforms, etc.).

Okay, so you’d have the ability to use Python on a network switch.  So what?  What about running onboard analytics on the switch?  What about sending the exact data you need, the data you use to troubleshoot, the data part of your operational workflow, directly upstream to a head end server, or just simply to an existing syslog Continue reading

Inetzero Blog: PIM Anycast RP

Read my blog regarding the PIM Anycast RP feature on The Inetzero blog and prepare your JNCIE exam with their materials:Workbooks and Racks. PIM ANYCAST BLOG More regarding Inetzero click there : David

Inetzero Blog: PIM Anycast RP

Read my blog regarding the PIM Anycast RP feature on The Inetzero blog and prepare your JNCIE exam with their materials:Workbooks and Racks. PIM ANYCAST BLOG More regarding Inetzero click there : David

Review: OpenStack Deployment

Deploying OpenStack Ken Pepple OpenStack is a wide ranging initiative started by Rackspace and NASA in 2010 designed to provide open source software to build and manage IaaS cloud services. What’s often missing in open source projects like OpenStack is a definitive guide to the release schedule, the different pieces, how the different pieces interact, […]

Author information

Russ White

Russ White
Principle Engineer at Ericsson

Russ White is a Network Architect who's scribbled a basket of books, penned a plethora of patents, written a raft of RFCs, taught a trencher of classes, and done a lot of other stuff you either already know about, or don't really care about. You want numbers and letters? Okay: CCIE 2635, CCDE 2007:001, CCAr, BSIT, MSIT (Network Design & Architecture, Capella University), MACM (Biblical Literature, Shepherds Theological Seminary). Russ is a Principal Engineer in the IPOS Team at Ericsson, where he works on lots of different stuff, serves on the Routing Area Directorate at the IETF, and is a cochair of the Internet Society Advisory Council. Russ will be speaking in November at the Ericsson Technology Day. he recently published The Art of Network Architecture, is currently working on a new book in the area Continue reading

OpenDaylight OpenStack Integration with DevStack on Fedora

The following is a walk through of the OVSDB project within OpenDaylight for OpenStack integration. There are a couple of bugs so it is not for the faint of heart. It is intended for those looking to get their development environment up and running. We will have videos and what not walking through the installation and code reviews of the ...

...

The Role of Code In “The New Network”

I was inspired by many little things over the past few days to begin writing a post about this whole “writing code” thing that network engineers the world over have been asking about. I’ve said before I know that most network engineers already write some kind of code - even if it’s as simple as a snippet of VBA in an Excel spreadsheet to automatically convert a spreadsheet of configuration options into an actual running configuration.

The Role of Code In “The New Network”

I was inspired by many little things over the past few days to begin writing a post about this whole “writing code” thing that network engineers the world over have been asking about. I’ve said before I know that most network engineers already write some kind of code - even if it’s as simple as a snippet of VBA in an Excel spreadsheet to automatically convert a spreadsheet of configuration options into an actual running configuration.

Nexus 5K L3 Daughter Card Internal Port-Channels

I was trying to configure a FEX in Rack 27, so I called it FEX 127 and was configuring Port-Channel 127 so I could vPC to the FEX. However, as soon as I entered the following, I got an error message:

NX5K-1(config-if)# channel-group 127
command failed: internally used, configuration not allowed


When you have a Nexus 5K with an L3 daughter card, the switch internally allocates Po127 and Po128 to bind the L3 interfaces to the ASICs. So if you have a 5K running L2 only, and have already allocated Po127 and Po128, and then in the future add an L3 daughter card, the system will use other free Port-Channel IDs. But if you have an L3 daughter card, you cannot use Po127 and Po128 when setting up a new Port-Channel.
1 … 3,702 3,703 3,704 3,705 3,706 … 3,784