Network Break serves up a bubbling cauldron of tech news, including a new hyperconverged platform from HPE, and big-name defectors from AWS such as Dropbox and Apple. There's also product and licensing news from Cisco, chip stories from Cavium and Broadcom, laurels for Huawei in an SDN competition, and more.
The post Network Break 79: HPE Hyperconverges; Dropbox Drops AWS appeared first on Packet Pushers.
Network Break serves up a bubbling cauldron of tech news, including a new hyperconverged platform from HPE, and big-name defectors from AWS such as Dropbox and Apple. There's also product and licensing news from Cisco, chip stories from Cavium and Broadcom, laurels for Huawei in an SDN competition, and more.
The post Network Break 79: HPE Hyperconverges; Dropbox Drops AWS appeared first on Packet Pushers.
The post Worth Reading: Improving Communication appeared first on 'net work.
Despite all the hype, disaggregation doesn’t make sense for most enterprise networks.
Mr. A. Anonymous, frequent contributor to my blog posts left this bit of wisdom comment on the VMware NSX Update blog post:
I don't understand the statement that "whole NSX domain remains a single failure domain" because the 3 NSX controllers are deployed in the site with primary NSX manager.
I admit I was a bit imprecise (wasn’t the first time), but is it really that hard to ask oneself “what happens if the DCI link fails?”
Read more ...Using multiple cloud providers can reduce cost and risk for an enterprise.
In what has been a fairly classic “yak shaving” exercise, I’ve been working on getting Ubuntu 15.10 “Wily Werewolf” running with Vagrant so that I can perform some testing with some other technologies that need a Linux kernel version of at least 4.2 (which comes with Ubuntu 15.10 by default). Along the way, I ran smack into a problem with Ubuntu 15.10’s networking configuration when used with Vagrant, and in this post I’m going to explain what’s happening here and provide a workaround.
The issue (described here on GitHub, among other places) involves a couple of changes in Ubuntu Linux (and upstream Debian GNU/Linux as well, although I haven’t personally tested it). One of the changes is in regards to how network interfaces are named; instead of the “old” eth0
or eth1
naming convention, Ubuntu 15.10 now uses persistent interface names like ens32
or ens33
. Additionally, an update to the “ifupdown” package now returns an error where an error apparently wasn’t returned before.
The end result is that when you try to create a Vagrant VM with multiple network interfaces, it fails. Using a single network interface is fine; the issue only rears its Continue reading
It's all about making VNFs easier to build, OSM members say.
One of the more interesting recent trends in the network space has been around software defined WAN (SDWAN). While I’ll admit I first didn’t give it much attention, I’ve since given it a harder look and see quite a bit of promise in the technology. The WAN is a part of the network that, until recently, hasn’t received much attention particularly as it relates to SDN. SDN in the enterprise space seems mostly focused on the data center since that’s where the network always seems to be the most complicated. The unfortunate outcome of that mindset is that while we focus on the data center network, technologies like SDWAN appear and don’t always get the attention they deserve. I think the primary reason for this is that many of us have WANs that we think are ‘working just fine’. And while that may be the case, I think SDWAN has the potential to significantly reduce costs, improve WAN performance, and increase network agility.
One of the vendors in this market that I’ve recently had the chance to hear about is Silver Peak. Silver Peak has been around for quite some time and is Continue reading
CORD was a big topic at the Open Networking Summit this week.