Archive

Category Archives for "Networking"

My MacBook Air Docking Solution

I decomissioned my CustoMac to return it to its origins as a gaming rig. This was mainly due to the fact that trying to keep my MacBook and CustoMac in sync was turing out to be very labour intensive... This means I am using my Macbook Air as my main office PC but its limited I/O was proving to be a little bit of a problem!

My MacBook Air Docking Solution

I decomissioned my CustoMac to return it to its origins as a gaming rig. This was mainly due to the fact that trying to keep my MacBook and CustoMac in sync was turing out to be very labour intensive... This means I am using my Macbook Air as my main office PC but its limited I/O was proving to be a little bit of a problem!

Nexus 2000 Model Number Cheat Sheet

A colleague of mine pointed something out the other day: the numbers and letters that make up the Nexus 2000 (FEX) model actually have meaning! No, I haven't been living under a rock. I think it's pretty clear that with a model number like “2248TP-E” the “22” indicates this is the 2200 series FEX and the “48” indicates it's got 48 ports. But what about the letters that follow the numbers?

I’m attending the International Summit for Community Wireless Networks

I will be giving a updated version of my bufferbloat talk there on Saturday, October 6.  The meeting is about community wireless networks (many of which are mesh wireless networks) on which bufferbloat is a particular issue.  It is in Barcelona, Spain, October 4-7.

We tried (and failed) to make ad-hoc mesh networking work when I was at OLPC, and I now know that one of the reasons we were failed was bufferbloat.

I’ll also be giving a talk at the UKNOF (UK Network Operator’s Forum) in London on October 9, but that is now full and there is no space for new registrants.


KIClet: NX-OS – Ethernet[X] is down (inactive)

This is a short one. I didn’t see a ton of information on this on the internet so I figured I’d put it forward. I’m using a pair of Nexus 2K FEX switches (N2K-C2248TP-1GE) for 1GbE copper connectivity off of a pair of Nexus 5548UP switches. I needed to set one of the 2K ports to access mode and place it in a VLAN. Pretty simple. After configuring one of the 2K ports through the 5K CLI though, I noticed that the port was listed as “down (inactive)”.

KIClet: NX-OS – Ethernet[X] is down (inactive)

This is a short one. I didn’t see a ton of information on this on the internet so I figured I’d put it forward. I’m using a pair of Nexus 2K FEX switches (N2K-C2248TP-1GE) for 1GbE copper connectivity off of a pair of Nexus 5548UP switches. I needed to set one of the 2K ports to access mode and place it in a VLAN. Pretty simple. After configuring one of the 2K ports through the 5K CLI though, I noticed that the port was listed as “down (inactive)”.

KIClet: NX-OS – Ethernet[X] is down (inactive)

This is a short one. I didn’t see a ton of information on this on the internet so I figured I’d put it forward. I’m using a pair of Nexus 2K FEX switches (N2K-C2248TP-1GE) for 1GbE copper connectivity off of a pair of Nexus 5548UP switches. I needed to set one of the 2K ports to access mode and place it in a VLAN. Pretty simple. After configuring one of the 2K ports through the 5K CLI though, I noticed that the port was listed as “down (inactive)”.

AirPlay, VLANs, and an Open Source Solution

As I've written about in the past (here), Apple's AirPlay technology relies on Bonjour which is Apple's implementation of “zero config” networking. One of the things that Bonjour enables is the automatic discovery of services on the network. For example, an Apple TV might advertise itself as being able to receive AirPlay streams. An iPad that is looking for AirPlay receivers would use Bonjour to discover the Apple TV and present it to the user as an AirPlay destination. Both the Apple TV and iPad do all this without any user intervention or configuration (hence the “zero config” part).

That's fine and dandy but what my earlier article focused on was how Bonjour broke down in a network where what I'll call the “server” and the “client” are not in the same Layer 2 domain/VLAN. This is because the service discovery aspect of Bonjour relies on link-local scope multicast. These packets will not cross Layer 3 boundaries in the network.

Spanning-tree Requirements for Cisco ISSU

I had a great conversation with a coworker regarding the requirements for the In-Service Software Upgrade (ISSU) feature on Cisco switches. For this post, I’m using Nexus 5548UP switches as a distribution layer to my Cisco UCS environment, and at the core is sitting a pair of Catalyst 6500s, set up in a VSS pair. For those unfamiliar with ISSU, it is a way for Cisco devices to upgrade their running firmware without the need for a disruptive reboot of the device, which is what has traditionally been used for upgrades to IOS, NX-OS, etc.

Spanning-tree Requirements for Cisco ISSU

I had a great conversation with a coworker regarding the requirements for the In-Service Software Upgrade (ISSU) feature on Cisco switches. For this post, I’m using Nexus 5548UP switches as a distribution layer to my Cisco UCS environment, and at the core is sitting a pair of Catalyst 6500s, set up in a VSS pair. For those unfamiliar with ISSU, it is a way for Cisco devices to upgrade their running firmware without the need for a disruptive reboot of the device, which is what has traditionally been used for upgrades to IOS, NX-OS, etc.

Book list

It is time I’ll place the list online, so with no farther delays and in the order of importance: 1 Routing TCP/IP, Volume 1 (2nd Edition) - By far, the most important book you must read. ...And remember, if you are using Private VLANs or plan to, make sure you visit my Private VLAN appliance site.

When NTP access-control needs ACL for 127.127.7.1?

The very simple answer is when the local NTP master controller is synching to the IP address 127.127.7.1 instead of 127.127.1.1. Ok, I think I need to clarify few things.  In a number of CCIE workbooks, you’ll get a task to configure NTP access-control on the master NTP router to only peer with R1.  After trying for a long time, you lookup the solution guide and realize that you were missing an ACL entry for the local address 127.127.7.1. Or you finished the task, everything works, you check the solution guide and ask yourself “why did they have an ACL for the IP address 127.127.7.1? I did it without it and it worked.”

This is something that I found to be very frustrating and without any information on the web. After doing some of my own research, it appears Cisco made few changes that are not very clearly documented.

To give you an example, R4 is the NTP master and R6 (150.1.6.6) is the NTP peer.

R4#sh run | i ntp | access-list
ntp master 4
ntp access-group peer 1


access-list 1 permit 150.1. Continue reading

The Pros/Cons of Public DNS

I strongly believe that every route/switch engineer, even highly experienced ones, should have at least a fundamental understanding of DNS architectures and best practices. More importantly, it should be understood how DNS is being used in today’s service providers and enterprises. DNS is one of those services that has been applied to many different use cases, such as a form of load balancing, or even an additional layer of security.

The Pros/Cons of Public DNS

I strongly believe that every route/switch engineer, even highly experienced ones, should have at least a fundamental understanding of DNS architectures and best practices. More importantly, it should be understood how DNS is being used in today’s service providers and enterprises. DNS is one of those services that has been applied to many different use cases, such as a form of load balancing, or even an additional layer of security.

ESXi 5 on Cisco UCS – No Local Disks Showing Up

I am installing ESXi 5 on a Cisco UCS B440 M1 blade, and ran into some local disk issues. I used both the stock ESXi 5 image from VMware, as well as the recently released image from Cisco that contains the latest UCS drivers. Same issue on both. The issue was that when I got to the disk selection screen on the ESXi installation, I did not see any disks:

ESXi 5 on Cisco UCS – No Local Disks Showing Up

I am installing ESXi 5 on a Cisco UCS B440 M1 blade, and ran into some local disk issues. I used both the stock ESXi 5 image from VMware, as well as the recently released image from Cisco that contains the latest UCS drivers. Same issue on both. The issue was that when I got to the disk selection screen on the ESXi installation, I did not see any disks:

ESXi 5 on Cisco UCS – No Local Disks Showing Up

I am installing ESXi 5 on a Cisco UCS B440 M1 blade, and ran into some local disk issues. I used both the stock ESXi 5 image from VMware, as well as the recently released image from Cisco that contains the latest UCS drivers. Same issue on both. The issue was that when I got to the disk selection screen on the ESXi installation, I did not see any disks:

My CCIE Journey Begins

I am happy to say that I have officially started putting things together for my CCIE R/S studies. I have been and will continue to be pulled in many different directions, but since my CCNP was completed a few months ago, and I recently passed my VCP exam, I decided that the time was now to begin the long journey ahead. I have a few other certifications in mind, and I will have to carefully weigh how they impact (or preferably do not impact) my CCIE studies, but this journey is important to me personally and professionally, so I’m pulling the trigger.

My CCIE Journey Begins

I am happy to say that I have officially started putting things together for my CCIE R/S studies. I have been and will continue to be pulled in many different directions, but since my CCNP was completed a few months ago, and I recently passed my VCP exam, I decided that the time was now to begin the long journey ahead. I have a few other certifications in mind, and I will have to carefully weigh how they impact (or preferably do not impact) my CCIE studies, but this journey is important to me personally and professionally, so I’m pulling the trigger.

IPv6 and flows (using nfsen)

This will be about already having nfsen/nfdump configured, and are looking to just make a flow profile to graph IPv6 traffic from your routers. If you are looking to get nfsen iniitially configured, definitely follow their instructions on their site.

Say you have an sFlow capable router like…picking one totally not at random…..a Brocade XMR or MLX(e), and you want some basic flow data, especially IPv6. Depending on how many routers you are going to collect flow data from, will determine how beefy of a machine you will need. I know that at $lastjob, it was a hefty CPU (and definitely more than 1), tons of RAM, and hardware RAID. Right now, I’m using dual quad-core Xeon, tons of RAM and a small hardware RAID, but this machine serves many purposes. Right now I’m also only polling 4 MLX routers.

Go ahead and access your nfsen website, and on the Profiles pulldown, select “New Profile …”. In the creation dialog, give the profile whatever title you like; I went with the generic title of “IPv6″. If you want to add it to a group or make one for it, do as you please. I left that alone so I’d Continue reading