David Spark published 16 tips for moving your workloads to the clouds. Contrary to the usual useless nonsense coming down from hybrid cloud evangelists (you know, the people who moved from “VMs following the sun” to “seamless hybrid cloud workload mobility”) some of the tips actually make sense, starting with “Have a real reason for the migration”. Enjoy!
When deploying PIM ASM, the Designated Router (DR) role plays a significant part in how PIM ASM works. The DR on a segment is responsible for registering mulicast sources with the Rendezvous Point (RP) and/or sending PIM Joins for the segment. Routers with PIM enabled interfaces send out PIM Hello messages every 30 seconds by default.
After missing three Hellos the secondary router will take over as the DR. With the standard timer value, this can take between 60 to 90 seconds depending on when the last Hello came in. Not really acceptable in a modern network.
The first thought is to lower the PIM query interval, this can be done and it supports sending PIM Hellos at msec level. In my particular case I needed convergence within two seconds. I tuned the PIM query interval to 500 msec meaning that the PIM DR role should converge within 1.5 seconds. The problem though is that these Hellos are sent at process level. Even though my routers were barely breaking a sweat CPU wise I would see PIM adjacencies flapping.
The answer to my problems would be to have Bidirectional Forwarding Dectection (BFD) for PIM but it’s only supported on Continue reading
Arista switches have an API known as eAPI. In this article, I will discuss some of the basics of how eAPI operates, how to connect to it, and how to gather network information using it. Basic eAPI operation eAPI uses JSON-RPC over HTTPS. What this means in simpler terms is that the communication to and […]
The post APIs, APIs…a look at Arista’s eAPI appeared first on Packet Pushers Podcast and was written by Kirk Byers.
Cisco Loves and Hates Net Neutrality, SDN WAN continues to grow and Analysts as AWS puppy dogs - drooling, licking themselves and barking at the AWS reinvent conference.
The post Network Break 22 appeared first on Packet Pushers Podcast and was written by Greg Ferro.
As many of you know, it’s been a busy month here at Plexxi. It’s hard to believe that November is coming to a close and that Thanksgiving is next week. We have a lot to be thankful for this year, particularly our new CEO Rich Napolitano and for the support of our skilled and dynamic team members – both new and old. Wishing everyone a safe and happy Thanksgiving holiday!
In this week’s PlexxiTube of the week, our own Dan Backman explains how Plexxi’s datacenter transport fabric can be used in a datacenter or on campus.
Check out what we’ve been up to over the past few weeks on social media!
The post PlexxiPulse— Plenty To Be Thankful For At Plexxi appeared first on Plexxi.
Out of sheer frustration this week, I tweeted this and got a big response: The Back Story I’ve wasted about 60 hours of customers time working with resellers & vendors to get a quote for a relatively simple network upgrade. Neither the vendor staffers or the reseller employees knew how the product was licensed or […]
The post Less Sales, Simpler Products, Easier Buying appeared first on EtherealMind.
I’ve written quite a bit about Open vSwitch (OVS), but I realized recently that despite all the articles I’ve written I still haven’t talked about how to remove a configuration setting to OVS. I’m fixing that now with this article.
As part of my ongoing mission to give back to the open source community, I recently started making contributions and improvements to the OVS web site; specifically, I’ve been reformatting the configuration cookbooks to make them more readable (and to clean up the HTML source). Along the way, I’ve been adding small bits of content here and there. Most recently, I just updated the QoS rate-limiting entry, and I wanted to add information on how to remove the QoS settings.
Normally, you can remove an OVS configuration setting using the ovs-vsctl remove command. For example, if you set a VLAN tag on an port with this command:
ovs-vsctl set port vnet0 tag=100
Then you could remove that VLAN tag with this command:
ovs-vsctl remove port vnet0 tag 100
Note the slight syntactical difference in the two commands; the remove command expects four parameters.
It turns out, however, that this command won’t work for all configuration parameters. In some Continue reading
We’d like to thank Jon Woloshyn for his testimonial! Jon recently passed the CCIE Collaboration lab! Here’s what Jon had to say:
“I attended iPexpert’s CCIE Collaboration 10-Day Bootcamp in August 2014 and I’m happy to say that on November 11th I passed the CCIE Collaboration exam on my first attempt.
I owe a lot of my success to Andy Vassar and iPexpert. The volume 1 workbook coupled with week 1 of the 10—Day CCIE Collaboration Lab Bootcamp helped solidify my understanding and comfort level with all of the technologies on the blueprint. Having my own un-shared, dedicated pod with the exact lab hardware that’s on the lab during that week to practice on day and night was huge. Being able to ask Andy every question that came to mind and get a detailed response was awesome. The fact the he would break from the lesson and lab up the questions being asked to prove the technology made the class very flexible and almost tailored to each student who required additional knowledge.
Week 2 of the 10-day course was the 1-Week Lab Experience (OWLE). I would not have passed without this week. Andy shared his lab strategy and at first Continue reading
Please Join us in congratulating the following iPexpert clients who have passed their CCIE lab!
Have you passed your CCIE lab exam and used any of iPexpert’s or Proctor Labs self-study products, or attended a CCIE Bootcamp? If so, we’d like to add you to our CCIE Wall of Fame!
I’ve written quite a bit about Open vSwitch (OVS), but I realized recently that despite all the articles I’ve written I still haven’t talked about how to remove a configuration setting to OVS. I’m fixing that now with this article.
As part of my ongoing mission to give back to the open source community, I recently started making contributions and improvements to the OVS web site; specifically, I’ve been reformatting the configuration cookbooks to make them more readable (and to clean up the HTML source). Along the way, I’ve been adding small bits of content here and there. Most recently, I just updated the QoS rate-limiting entry, and I wanted to add information on how to remove the QoS settings.
Normally, you can remove an OVS configuration setting using the ovs-vsctl remove command. For example, if you set a VLAN tag on an port with this command:
ovs-vsctl set port vnet0 tag=100
Then you could remove that VLAN tag with this command:
ovs-vsctl remove port vnet0 tag 100
Note the slight syntactical difference in the two commands; the remove command expects four parameters.
It turns out, however, that this command won’t work for all configuration parameters. In some Continue reading
A while ago I wrote about performance bottlenecks of Open vSwitch. In the meantime, the OVS team drastically improved OVS performance resulting in something that Andy Hill called Ludicrous Speed at the latest OpenStack summit (slide deck, video).
Let’s look at how impressive the performance improvements are.
Read more ...Working for a data center-focused reseller/integrator like H.A. Storage Systems, I spend my fair share of time in various data center environments. I have, for years, elected to use some sort of hearing protection when in these facilities. I have constantly been amazed, though, at how few other workers in data centers do the same.
Honestly, I’m not sure why most people I see in data center facilities don’t use hearing protection. Perhaps they think they’ll only be on the data center floor for a few minutes. We all know it never goes like that! Perhaps they think it makes it too hard to hear co-workers. Personally, I find it easier to communicate with someone when I have ear protection on. Maybe workers think it’s not loud enough for ear protection to be necessary. Unfortunately, this isn’t true in most cases.
As an example, I was recently down at the Sungard Availability Services colo facility in Philadelphia. It’s one of the largest colos in the immediate area with 230,000 square feet of raised floor. I was in there all day long with one of my customers, for two days while we traced out Continue reading
A few weeks ago I read this article from Craig Matsumoto on SDN Central.
At first I read it with a bit of a smile, but for some reason it has actually started to bother me a little. In this article, Craig summarizes a talk by Scott Shenker about SDN and a proposal for an SDNv2 that would fix the things that are wrong with SDNv1. In a way this represents what is wrong with our industry. We create a new version or create a new name for a concept that is not particularly well defined to begin with, and in many interpretations is far broader than is assumed in the pre-fixed version.
Many folks still believe that OpenFlow defines SDN. And that all the limitations of a basic protocol invalidate or limit the capabilities of an evolving concept like SDN. Why do we feel such a need to increment a version of an undefined term to make it sound like we are creating something new and different?
In SDNv2, we would still have separation of control and date (at least all that work is not wasted), but there are three major differences between it and the “old” SDN concepts. Continue reading
After describing the current state of affairs in his Network Programmability 101 webinar, Matt Oswald moved to the low-hanging fruits: automating repetitive tasks in baby steps, from VLAN provisioning to consistent device configurations.