We collect the top expert content in the infrastructure community and fire it along the priority queue.
In our journey toward two-switch data center we covered:
It’s time for the next step: get rid of legacy technologies like six 1GE interfaces per server or two FC interface cards in every server.
Need more details? Watch the Designing Private Cloud Infrastructure webinar. How about an interactive discussion? Register for the Building Next-Generation Data Center course.
With 110 stores in North America, 46 data center locations, and $2 billion in revenue, Columbia Sportswear is constantly processing huge amounts of data—data whose security was being compromised by their inadequate hardware-defined data center.
When Columbia Sportswear virtualized their network, they not only stepped up their security; they also saved $16 million over a comparable hardware-based security approach.
Download our free ebook: Redefining Networking with Network Virtualization
How? Find out here. Follow their process step by step in the infographic below.
The post Micro-Fiber, Meet Micro-Segmentation! Columbia Sportswear Virtualizes the Network, Saves Millions appeared first on The Network Virtualization Blog.
MP-BGP (Multiprotocol BGP) is an extensions to BGP protocol. Standard BGP only supports IPv4 unicast address family, whereas MP-BGP supports more than 15 different BGP address families. RFC4760 defines the extensions for BGP protocol and states that ” in order to bring extra functionality to BGP protocol, new BGP AFI (Address Family Identifier) and BGP SAFI […]
The post What is MP-BGP – Multiprotocol BGP appeared first on Cisco Network Design and Architecture | CCDE Bootcamp | orhanergun.net.
Here's what to consider for building your own hyperconverged system.
Enterprises should maximize their cloud investment with analytics to optimize operations.
In this episode of Rockstar SE Jacob Hess and Terry Kim discuss basic network traffic concepts. They break down topics such as collision domains and broadcast domains and how those concepts relate to network traffic and the world of network engineering. Join them in this Tech Lesson to learn more and don’t forget to download your free PDF!
Tech Lesson PDF: Understanding Basic Network Traffic
In my last post I discussed the first part of the Architects job namely to create a Vision for the future state of the infrastructure based on business needs and requirements. In this blog I want to go into the second piece of work the architect has to create being the Strategy. The Architect as […]
The post Breaking down the Ivory Tower part 2 – Strategy appeared first on Packet Pushers.
If you have read my introduction to macvlans and tried the basic macvlan bridge mode network configuration you are aware that a single Docker host network interface can serve as a parent interface to one macvlan or ipvlan network only.
One macvlan, one Layer 2 domain and one subnet per physical interface, however, is a rather serious limitation in a modern virtualization solution. Fortunately, a Docker host sub-interface can serve as a parent interface for the macvlan network. This aligns perfectly with the Linux implementation of VLANs, where each VLAN on a 802.1Q trunk connection is terminated on a sub-interface of the physical interface. You can map each Docker host interface to a macvlan network, thus extending the Layer 2 domain from the VLAN into the macvlan network.
You have a Docker host with a single eth0
interface connected to a router. Connection between the router and the Docker host is configured as 802.1Q trunk on the router with VLAN 10 and VLAN 20.
Configure VLAN 10 and VLAN 20 on your router. Add the following IP addresses to the Layer 3 interface: 10.0.10.1/24
and 2001:db8:babe:10::1/64
for VLAN 10, 10. Continue reading