DCI Series: Overlay Transport Virtualization
This is the third article in my series on Data Center Interconnection (DCI). In the first (Why is there a “Wrong Way” to Interconnect Data Centers?) I wrote about the risks associated with DCI when the method chosen is to stretch Layer 2 domains between the data centers. In the second article (DCI: Why is Stretched Layer 2 Needed?) I wrote about why the need exists for stretching Layer 2 domains between sites and also touched on why it's such a common element in many DCI strategies.Routing iSCSI Traffic
This post was initiated by a side conversation I had about iSCSI. From time to time I’m required to implement an iSCSI-based solution, and this is not the first time I’ve heard the question: “So why can’t I route iSCSI traffic?” Most folks with any knowledge of storage protocols will have at some point picked up this informal best practice idea; some will vehemently defend this idea as the word of $deity and shun all those who contradict this truth.Routing iSCSI Traffic
This post was initiated by a side conversation I had about iSCSI. From time to time I’m required to implement an iSCSI-based solution, and this is not the first time I’ve heard the question: “So why can’t I route iSCSI traffic?” Most folks with any knowledge of storage protocols will have at some point picked up this informal best practice idea; some will vehemently defend this idea as the word of $deity and shun all those who contradict this truth.Arduino: Using my MelodyUtils library for R2-D2 style chirps
As part of a small robotics project I've been working on this weekend (affectionately called CoBe1, there will be a follow up blog on that soon) I decided to give by robot some personality in the form a a voice, and uploaded some of my code to GitHub.
While Arduino is capable of playing music and sounds from an SD Card I wanted something a little more authentic… something similar to R2-D2's chirps from Star Wars. I had a mini 8Ohm speaker lying around and following the tutorials here it was easy to get it hooked up to my Arduino Uno and start making sounds. By adjusting the default melody and timings I got part way to achieving my R2-D2 style attitude, but notes on their own just didn't cut it. What I needed was some articulations. I got coding and whipped up a library that makes it easy to use glissando and tremolo. Want to give it a try? Grab the code on GitHub Here's a simple example sketch:
#include <pitches.h>;
void setup()
{
MelodyUtils mel(8);
mel.Glis(NOTE_C3, NOTE_C4, 5);
delay(1000);
mel.Trem(NOTE_C3, Continue readingArduino: Using my MelodyUtils library for R2-D2 style chirps
As part of a small robotics project I've been working on this weekend (affectionately called CoBe1, there will be a follow up blog on that soon) I decided to give by robot some personality in the form a a voice, and uploaded some of my code to GitHub.
Arduino: Using my MelodyUtils library for R2-D2 style chirps
As part of a small robotics project I've been working on this weekend (affectionately called CoBe1, there will be a follow up blog on that soon) I decided to give by robot some personality in the form a a voice, and uploaded some of my code to GitHub.
Multi-Vendor OSPF Cost Calculations
While on my current kick with virtual routing, I stumbled across an interesting concept regarding OSPF, and the flexibility that vendors have in determining the best path through an OSPF network. The following topology is what I’ve been staring at for the last few days Pretty simple, right? There’s a single network (192.168.123.0/24) down inside each virtual host where the VMs are to sit. Each host has a router on it (one Cisco CSR 1000v and the other Vyatta Core 6.Multi-Vendor OSPF Cost Calculations
While on my current kick with virtual routing, I stumbled across an interesting concept regarding OSPF, and the flexibility that vendors have in determining the best path through an OSPF network. The following topology is what I’ve been staring at for the last few days Pretty simple, right? There’s a single network (192.168.123.0/24) down inside each virtual host where the VMs are to sit. Each host has a router on it (one Cisco CSR 1000v and the other Vyatta Core 6.HP Route Preference (Administrative Distance)
When building networks leveraging a variety of products you need to consider interoperability and configuration consistency. When leveraging HP A-Series switches in a Cisco environment considerations need to be made in regards to administrative distance (Cisco's term) or route preference (HP's term). In order to ensure that you maintain consistent behavior it is recommended that you modify one or the other and make them consistent with each other. I would recommend following Cisco's administrative preference instead of HP's route preference.HP's default route preference
Cisco's default administrative distance
Don't get caught with unexpected routing behaviors. Have fun!
What The Heck Is F5 Networks’ TMOS?
F5 Network’s Traffic Management Operating System (TMOS) is, first and foremost and for the sake of clarity, NOT an individual operating system. It is the software foundation for all of F5’s network or traffic (not data) products; physical or virtual. TMOS almost seems to be a concept rather than a concrete thing when you first try […]
Author information
The post What The Heck Is F5 Networks’ TMOS? appeared first on Packet Pushers Podcast and was written by Steven Iveson.
Show 144 – Open EIGRP with Russ White + Cisco’s Donnie Savage
EIGRP is a distance vector routing protocol that for many years was unique to Cisco networking environments. Created and championed by Cisco, it didn’t get any traction in the standards bodies in the early days, because there were already enough interior gateway routing protocols around according to some. EIGRP just didn’t interest enough of the […]
Author information
The post Show 144 – Open EIGRP with Russ White + Cisco’s Donnie Savage appeared first on Packet Pushers Podcast and was written by Ethan Banks.
IOS X-Treme!
Originally posted on The Networking Nerd:As a nerd, I’m a huge fan of science fiction. One of my favorite shows was Stargate SG-1. Inside the show, there was a joke involving an in-universe TV program called “Wormhole X-Treme” that…
[Virtual Routing] Part 2 – FHRP Issues in VMware vSphere
I was working on a topology for another post regarding interoperability between the recently released Cisco Cloud Services Router (CSR 1000v) and Vyatta when I ran into an issue regarding vSphere network security policies and First Hop Redundancy Procotols (FHRP) such as VRRP. This post will serve as a precursor to that overall post, but I want to point out a key configuration piece when performing redundant gateways with a FHRP like VRRP.[Virtual Routing] Part 2 – FHRP Issues in VMware vSphere
I was working on a topology for another post regarding interoperability between the recently released Cisco Cloud Services Router (CSR 1000v) and Vyatta when I ran into an issue regarding vSphere network security policies and First Hop Redundancy Procotols (FHRP) such as VRRP. This post will serve as a precursor to that overall post, but I want to point out a key configuration piece when performing redundant gateways with a FHRP like VRRP.[Virtual Routing] Part 2 – FHRP Issues in VMware vSphere
I was working on a topology for another post regarding interoperability between the recently released Cisco Cloud Services Router (CSR 1000v) and Vyatta when I ran into an issue regarding vSphere network security policies and First Hop Redundancy Procotols (FHRP) such as VRRP. This post will serve as a precursor to that overall post, but I want to point out a key configuration piece when performing redundant gateways with a FHRP like VRRP.Cisco Nexus – Port “Inactive” Status
Quick notes on the “inactive” port status seen on the Cisco Nexus platform, which was perplexing the first time I ran into it. This isn’t a new status, existing on a variety of Cisco platforms for a long time now. As it happens, I’ve just not seen it that often historically. In dealing with the […]
Author information
The post Cisco Nexus – Port “Inactive” Status appeared first on Packet Pushers Podcast and was written by Ethan Banks.
Packet Design Appoints Matt Sherrod as Vice President of Product Management
Company Snags Network Management Expert and Industry Veteran
SANTA CLARA, CA — April 16, 2013 — Packet Design, the leading provider of IP network route analytics software, announced today that it has hired Matt Sherrod as Vice President of Product Management. Sherrod will lead product strategy, product design and integrated partner solutions to expand the Packet Design product portfolio and deliver a best-in-class customer experience.
Sherrod has more than 25 years of networking experience. He joins Packet Design from CA Technologies where, as the Vice President of Product Management, he defined product direction and strategy for the company’s infrastructure management solutions. Over the last 10 years he has held a number of field and management positions at CA Technologies and NetQoS. Prior to joining NetQoS, Matt worked as Director of Communications for a Fortune 100 global enterprise, applying leading edge technologies to improve application delivery.
“Matt Sherrod has a deep understanding of customer needs coupled with years of experience in defining and delivering innovative network performance management products to address them,” said Scott Sherwood, CEO of Packet Design. “He is uniquely qualified to lead Packet Design’s product strategy and ensure we provide world-class management solutions for complex service provider and Continue reading