As technology continues to rapidly evolve, network virtualization is now applied to every aspect of the data center. Before you virtualize your network, it’s important to understand what makes sense for your business, and why. To give you the tools for your next step, we’ve gathered top VMware NSX® industry experts for an open panel discussion on the importance of the network in a virtualized world.
Sign up for our NSX panel webcast on 6/15 and discover valuable insight from these industry leaders. No slides, no scripts, just an open conversation.
Moderated by Joshua Soto, VMware Sr. Product Marketing Manager in Networking & Security, our NSX team will start the session with a discussion on network virtualization and how it completes the virtualization infrastructure. Then they’ll discuss the evolution of the data center, the role of fluid architectures, and how NSX is the network virtualization platform for the Software-Defined Data Center (SDDC).
Don’t miss this chance to hear from leading network virtualization experts in a relaxed, conversational environment.
Register to attend our NSX panel webcast on 6/15 today!
The post Join a Conversation on Network Virtualization with Leading NSX Industry Experts on June 15th appeared first on The Network Virtualization Continue reading
Docker controls the IP address assignment for network and endpoint interfaces via libnetwork’s IPAM driver(s). On network creation, you can specify which IPAM driver libnetwork needs to use for the network’s IP address management.
Libnetwork’s default IPAM driver assigns IP addresses based on its own database configuration. For the time being, there is no IPAM driver that would communicate with an external DHCP server, so you need to rely on Docker’s default IPAM driver for container IP address and settings configuration.
The need for external DHCP server support has been identified, however, there is currently no sign that libnetwork developers are working on it. There are community efforts to produce a DHCP IPAM driver, but are currently not production ready.
If you critically rely on your DHCP for IP address management in your production, you can use pipework for the time being.
Alternatively, you can use both DHCP and Docker’s default IPAM on the same Layer 2 segment (a segment that covers both the physical network and the Docker hosted macvlan), with DHCP server providing data for hosts outside Docker host and IPAM providing data for Docker containers. In this case you should split the IP space Continue reading
Proper design helps minimize co-channel and adjacent channel interference, which degrade WLAN performance.
Gabi Gerber is organizing a Software-Defined Security event in Zurich next week in which I’ll talk about real-life security solutions that could be called software defined for whatever reason, and my friend Christoph Jaggi sent me a few questions trying to explore this particular blob of hype.
For obvious reasons he started with “Isn’t it all just marketing?”
Read more ...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.