Software-Defined Storage Security: 6 Best Practices
Make security a priority in your software-defined storage by following these steps.
Make security a priority in your software-defined storage by following these steps.
5G subs will top 150 million by 2021, report predicts.

I’ve added a new question to my own network integration checklist, specifically when integrating chassis-based or integrated solutions:
Does the system use any reserved internal address ranges?
Some chassis-based systems reserve private IP address ranges for inter-card communication. This is a perfectly fine setup as long as you, the network integrator, know what ranges are in use. However, you’ll have a frustrating case of ‘disappearing packets’, if you’re not aware that these ranges are in use.
I first saw this issue on an IXIA XM12 chassis a few years back. As I later discovered, each line card received a /24 from an RFC1918 address range. The supervisor used an IP address in each range to communicate with each line card. When I used a conflicting range in my testing the chassis would swallow my packets, and I was left scratching my head until I figured this out.
I thought this was a one-off, but I hit it again recently on an Ericsson Call Control Node. Same problem, but a little easier to detect this time. Nevertheless, I’ve been stung twice now on this issue, so I’ve added to my checklist and brought it to your attention.
If an appliance uses a reserved Continue reading
I’ve added a new question to my own network integration checklist, specifically when integrating chassis-based or integrated solutions: Does the system use any reserved internal address ranges? Some chassis-based systems reserve private IP address ranges for inter-card communication. This is a … Continue reading
The post Reserved Internal Address Ranges appeared first on The Network Sherpa.
Some new capabilities to kick off MesosCon.
It’s using ideas from CORD and OSM.
Former Qualcomm exec Nagraj Kashyap will lead Microsoft Ventures.
This colloquialism for “make my vehicle better” is an appropriate perspective on our recently released Cumulus Linux 3.0, or as we like to say around the office, “3.0.” Our engineering team looked at the upcoming market changes and decided to give Cumulus Linux a pretty sweet makeover.

Starting with the “IP mindset” that prevails in modern deployments, our team worked with the Linux kernel community to add Virtual Routing and Forwarding (VRF) to the kernel and hardware support to Cumulus Linux. VRF is coupled with BGP unnumbered interfaces as an even simpler way to deploy multi-tenant dual-stack IPv4/IPv6 networks.
In parallel, we looked at the image installation and upgrade mechanisms, revamping the build, packaging, and base installer. As a result, 3.0 is based on Debian 8 (Jessie) and Linux kernel 4.1 tied together with an entire system that enables the development flexibility of Linux coupled with the testing and support required for wide-scale, enterprise production deployments.
All of this functional horsepower is applied to seven new hardware platforms continuing Cumulus Networks’ industry leading support for Open Networking systems. These platforms cover the gamut of speeds, feeds, and functions; introducing Mellanox Spectrum alongside Broadcom Tomahawk and Continue reading
The datacenter is a battleground with many fronts these days, with intense competition between compute, memory, storage, and networking components. In terms of revenues, profits, and prestige, the compute territory is the most valuable that chip makers and their system partners are fighting for, and the ARM and OpenPower collectives are doing their best to take some ground from a very powerful Intel.
As such, chip makers end up comparing themselves to Intel Xeon or Atom processors, and Intel sometimes makes comparisons back. At the high end, Intel is battling the Power8 processor championed by IBM and to a lesser …
Intel Lines Up ThunderX ARM Against Xeons was written by Timothy Prickett Morgan at The Next Platform.