“Hey,” said my friend, “are you interested in buying an Ethernet switch? 48 1Gbps copper ports and two 10Gbps fiber uplinks. Very cheap. Layer 2 only, though.” A few minutes later, we were doing business out of the trunk of … Continue reading
If you liked this post, please do click through to the source at The Quanta LB4M – Cheap White Box Switching? and give me a share/like. Thank you!
In the world of Anything-as-a-Service (I will leave the acronym to your imagination), Network-as-a-Service is not a new term. In fact, it even has its own wikipedia page which will tell you it has been used for many years now, well before the current set of service related terms in IT have become popular.
Like most high tech industries, we get somewhat carried away when we have some new terminology and quickly overuse and overload them, watering them down to be meaningless or at least highly confusing. But when you cut through the clutter a bit, the as-a-Service terminology most certainly articulates a shift in thought process and behaviors on how we provide and consume IT resources.
The IT organization has always been a service organization, there is nothing much new there. From the days of mainframes and supercomputers, their job was to provide access to these expensive resources and maintain them. They provided environments that allowed the users to conveniently consume these abilities, and the business applications that ran on top of them, whether those were financial systems, email, uucp news (remember those days) or the basic ability to run user created jobs.
With the distribution of compute and Continue reading
For non-programmers, making a meaningful contribution to an open source project can be difficult; this is as true for OpenStack as for other open source projects. Documentation is a way to contribute, but in the case of OpenStack there is a non-trivial setup required in order to be able to contribute to the OpenStack documentation. In this post, I’m going to share how to set up the tools to contribute to OpenStack documentation in the hopes that it will help others get past the “barrier to entry” that currently exists.
I’ve long wanted to be more involved in supporting the OpenStack community, beyond my unofficial support via advocacy and blogging about OpenStack. I felt that documentation might be a way to achieve that goal. After all, I’ve written books and have been blogging for 9 years, so I should be able to add some value via documentation contributions. However, the toolchain that the OpenStack documentation uses requires a certain level of familiarity with development-focused tools, and the “how to” guides were less than ideal because of assumptions made regarding the knowledge level of new contributors. For these reasons, I felt that sharing how I (a non-programmer) set up the tools Continue reading
I carried out an interesting quiz during one of my Interop workshop:
Is there a rational explanation for this seemingly nonsensical result?
Read more ...So, sure, you COULD run NSX and ACI in the same network. No, you WOULD NOT run NSX and ACI in the same network.
The post Musing: On Using Cisco ACI and VMware NSX in the same network appeared first on EtherealMind.
In today's sponsored podcast, HP Networking looks to educate network engineers about HP’s data center portfolio and technologies that make it a formidable choice for architecting today’s data center networks. Tune in to learn how HP is helping customers develop Data Center solutions that deal with today and tomorrow’s challenges.
The post Show 212 – HP Networking in the Data Centre – Sponsored appeared first on Packet Pushers Podcast and was written by Greg Ferro.
In Episode 167 of The Cloudcast – “Bringing Advanced Analytics to DevOps”, Dave Hayes brings up an interesting point about Mean Time to Resolution (MTTR). At about 8:30 in, he states:
“In a counter-intuitive sense, you actually want this to be going up…If you’re removing false alerts, and you’re getting better about the quantity of alerts, you’re going to be solving far fewer, more difficult problems, so you should see a slight trend upwards in Mean Time to Resolution”
This is a really interesting way of looking at things. Obviously you don’t want to set your goal as “Increase our MTTR,” but this could be a positive side-effect of improved processes.
I recommend listening to the whole episode. PagerDuty is a very cool product in itself, but this is a broader discussion about operations, analytics, and best practices.
Subscribe to the podcast while you’re there too. Lots of interesting technology discussed there.
Who needs the Wireshark GUI right; let’s do this at the command line and be grown up about things. This is a straight copy of my popular Using Wireshark to Decode/Decrypt SSL/TLS Packets post, only using ssldump to decode/decrypt SSL/TLS packets at the CLI instead of Wireshark. Aside from the obvious advantages, immediacy and efficiency of a CLI tool, ssldump also […]
The post Using ssldump to Decode/Decrypt SSL/TLS Packets appeared first on Packet Pushers Podcast and was written by Steven Iveson.
Ever been asked to list the serial numbers on an f5 Viprion? No? Well stay with me anyway – this is a quick one, and you never know when it will be helpful! Once upon a time, much of the … Continue reading
If you liked this post, please do click through to the source at The Quick Way to get f5 Viprion Serials and give me a share/like. Thank you!
This blog post is a follow-up to our previous introduction to DNSSEC. Read that first if you are not familiar with DNSSEC.
DNSSEC is an extension to DNS: it provides a system of trust for DNS records. It’s a major change to one of the core components of the Internet. In this post we examine some of the complications of DNSSEC, and what CloudFlare plans to do to reduce any negative impact they might have. The main issues are zone content exposure, key management, and the impact on DNS reflection/amplification attacks.
DNS is split into smaller pieces called zones. A zone typically starts at a domain name, and contains all records pertaining to the subdomains. Each zone is managed by a single manager. For example, cloudflare.com is a zone containing all DNS records for cloudflare.com and its subdomains (e.g. www.cloudflare.com, api.cloudflare.com).
There is no directory service for subdomains in DNS so if you want to know if api.cloudflare.com exists, you have to ask a DNS server and that DNS server will end up asking cloudflare.com whether api.cloudflare.com exists. This is not true with DNSSEC. In Continue reading
How many SDN jobs are out there so far? If you missed the previous post, well, I’ve been counting them for about five months. Today’s post looks at the numbers for 3QCY14. Check out the previous post for all the picky details about how we gathered the data. This post focuses on the numbers!
I’m theorizing that for a term to be in the title of the job posting, that term must be a pretty important part of the job. So, we searched for “SDN” in the title, at Dice.com and Monster.com, did some averaging to keep a week or two spike or drop from skewing the perception, and we’ve created some graphs.
Figure 1 shows the first graph:
When we find “SDN” Continue reading
I’ve mentioned in past articles about my belief that networking – both as a discipline and a technology – needs to be more consumable to other disciplines. But what does this mean? I was reminded of a few great examples today that I think are relevant to this idea, and might help explain my point a little more clearly.
The assembly line revolutionized the auto industry. Prior to this, vehicle production was very slow, and extremely costly. The introduction of the assembly line for creating automobiles allowed cars to be created in a predictable, repeatable way. However, Ford famously required all Model T’s to be painted black. Even before the introduction of the assembly line, the Model T was available in other colors, but with the move to mass production, this option was taken away.
The term “mass customization” is essentially the idea that mass production can co-habitate with customization, resulting in a customer experience that is personal and custom-built, but that also gets to experience the low unit cost that comes with mass production.
A great example of mass customization is the Moto X phone, whose commercials famously offer all kinds of customization options Continue reading
Kaspersky published a research note on Black Energy malware that uses backdoors and exploits on Cisco routers to install a TCL file, perform surveillance or destruction of the device configuration. And, they revealed that their Cisco routers with different IOS versions were hacked. They weren’t able to connect to the routers any more by […]
The post Response: Black Energy 2 Malware Router Abuse – Kaspersky appeared first on EtherealMind.
In their Q3-2014 VMware results, the revenue from "services" is 30% larger than licensing revenue. What does this mean for customers ?
The post Musing: VMware Sells More Services Than Licenses appeared first on EtherealMind.
I’ve finally had time to do some proper studying for JNCIE, and I noticed something that I may have been getting wrong for a looong time. It is minor, but could have bad consequences in a route-reflection environment.
I have a lab topology set up that looks like this:
Route-reflection in JNCIE study lab
R1 is advertising a direct network of 10.0.5.0 to the route reflectors R3 and R4. When I looked at R5 I was expecting to see R1 as the “protocol next-hop” but instead I was seeing R3 and R4. That didn’t look right to me.
Some explanation first: When you look at a route using “extensive” you get quite a lot of information but in there are two types of next hop. The “forwarding next hop” is (literally) the next IP hop to get to the “protocol next-hop” which is the BGP speaker that is advertising the route. The forwarding next hop is derived from the IGP, but the protocol next hop comes from iBGP. I was expecting to see the forwarding next hop to be the other end of one of the circuits to R3 or R4 Continue reading
Last year, we published two shows of horror stories about network outages and these shows generated a HUGE response from the audience. People emailed us about laughing, head nodding and “that happened to me”. Because you loved it, we are going to do it again. Because of time constraints the format will be a little […]
The post Show News: Network Down Stories and The Nightmare Before Christmas appeared first on Packet Pushers Podcast and was written by Greg Ferro.
This was a new one on me – in the past I have always advertised an aggregate route and then written policy to match the contributing routes so that they can be suppressed. It turns out there’s an easier way to do this:
root@R3# show policy-options policy-statement AGG
term T1 {
from protocol aggregate;
then accept;
}
term T2 {
from aggregate-contributor;
then reject;
}
Plexxi along with Piston Cloud, Colovore, and King Star Computing published a white paper a few months back looking at the cost of a private cloud running OpenStack in a hosted environment versus renting compute instances from Amazon. The details are here. The short story is that in this analysis, at about 129 Cores, the costs for a private cloud start to become better than public cloud. Certainly the efficiency of colocation, commodity computing/storage, and an application oriented network fabric integrated tightly with a cloud orchestration management platform (OpenStack) has a lot of built in efficiencies so its not surprising to see the result of this analysis.
Similarly, years ago in software development circles, the debates about outsourcing were fierce and emotional. Back then, much centered on the cost leverage available to companies to move development to low-cost areas such as India, China, and Eastern Europe. However, over time, companies found that while cost gave them flexibility and resourcing mite, the more important benefit ended up being owning development resources and presences close to emerging markets while leveraging outsourcing partners for on-demand resource expansion. Wow, sounds a lot like Colocation + Hybrid Cloud Continue reading
Want to know how HP IRF works? What its limitations are? Which data center protocols HP 5900 supports? How Dell Force10 switches handle MLAG? How well are HP and Dell supporting OpenFlow?
You’ll get answers to all these questions in the videos recently published in the Data Center Fabric Architecture webinar (also available as part of yearly subscription).