NetworkingNexus.net

Getting Started: Writing Your First Playbook

Welcome to another post in our Getting Started series. Keep reading to learn how to draft a Playbook that can be run in Ansible or Ansible Tower. You can also use it along with the Module Index and the other docs to build your own Playbooks later.

What is a Playbook?

Playbooks are esentially sets of instructions (plays) that you send to run on a single target or groups of targets (hosts). Think about the instructions you get for assembling an appliance or furniture. The manufacturer includes instructions so you can put the parts together in the correct order. When followed in order, the furniture looks like what was purchased.

That's basically how a Playbook works.

Modules

The Playbook we're building will install a web server on a target RHEL/CentOS 7 host, then write an index.html file based on a template file that will reside with the final Playbook. You'll be able to take the example Playbook and additional files from this blog and test it out for yourself. While going over the example Playbook, we'll explain the modules that are used.

Authors

The author adds instructions for the modules to run, often with additional values (arguments, locations, etc. Continue reading

EVPN-VXLAN lab – basic L2 switching

My EVPN-VXLAN lab topology:

There is IP Fabric in DC1 (2 vMX and 2 vQFX), and 2 vMX_v14 to emulate CE devices. Each CE device connected to EVPN via LACP LAG ae0 (EVPN Active-Active ethernet segment on service side). vMX_old-1 also has sigle-homed interface ge-0/0/4 (just to show you the difference).
Each CE device split into two logical systems for more convenient testing of routing functionality (global device context for Vlan100 and logical-system second for Vlan200). You could also use virtual-router routing instances for that, if you prefer this way. The rest of CE config is pretty self-explanatory:

alex@MX1# show interfaces
ge-0/0/0 {
description vMX1;
gigether-options {
802.3ad ae0;
}
}
ge-0/0/1 {
description vMX2;
gigether-options {
802.3ad ae0;
}
}
ge-0/0/4 {
description vMX1_second;
flexible-vlan-tagging;
encapsulation flexible-ethernet-services;
mac 00:46:d3:04:fe:06;
}
ae0 {
description to_MC-LAG_vMX;
Continue reading

IDC: SD-WAN growth is exploding for at least the next 5 years

As network pros rely more and more on SD-WAN to streamline connections among enterprise sites, the market for this technology will balloon from $225 million in 2015 to $1.19 billion by the end of this year, according to IDC.Over the next five years, SD-WAN sales will grow at a 69% compound annual growth rate, hitting $8.05 billion in 2021, according to IDC’s Worldwide SD-WAN Forecast, 2017–2021.As businesses adopt what IDC calls “third-platform” technologies such as cloud, mobile, big data and analytics, they put increased strain on the network. As organizations look to better connect their remote and branch office employees and provide them better quality network services, SD-WAN will continue to grow.To read this article in full or to leave a comment, please click here

IDC: SD-WAN growth is exploding for at least the next 5 years

Worth Reading: LinkedIn passes an IPv6 milestone

Since we enabled IPv6 on our mail servers in 2013 and then on our web site in 2014, we have seen increased growth of our external IPv6 traffic. We are currently working on enabling IPv6 on our all of our internal networks and applications in order to begin removing IPv4 internally, beginning in 2018. The external network and public services will still support IPv4 (for compatibility with legacy clients) for years to come, but we anticipate the proportion of our external traffic served over IPv6 to only increase. The community has seen tangible benefits from serving content over IPv6 compared to IPv4. We, too, see some performance improvements on IPv6. —LinkedIn Engineering Blog

The post Worth Reading: LinkedIn passes an IPv6 milestone appeared first on rule 11 reader.

Data Center Physical Realities in a Software-Defined World

A company's ability to leverage software depends on efficient infrastructure.

Cisco’s Nexus 9516 review: About line rate

Much ink has been spilled on the topic of what constitutes true “line rate,” and in the past we’ve advocated offering traffic at, and only at, 100.00 percent of theoretical line rate to determine if frame loss exists. However, the distinction between 99.99 percent (which we used in these tests) and 100.00 percent load is not all that meaningful, especially at higher Ethernet speeds, for a couple of reasons. First, Ethernet is inherently an asynchronous technology, meaning each device (in this case, the device under test and the test instrument) uses one or more of its own free-running clocks, without synchronization. Thus, throughput measurements may just be artifacts of minor differences in the speeds of clock chips, not descriptions of a system’s fabric capacity.To read this article in full or to leave a comment, please click here

Cisco’s Nexus 9516 review: About line rate

Managing Deep Learning Development Complexity

For developers, deep learning systems are becoming more interactive and complex. From the building of more malleable datasets that can be iteratively augmented, to more dynamic models, to more continuous learning being built into neural networks, there is a greater need to manage the process from start to finish with lightweight tools.

“New training samples, human insights, and operation experiences can consistently emerge even after deployment. The ability of updating a model and tracking its changes thus becomes necessary,” says a team from Imperial College London that has developed a library to manage the iterations deep learning developers make across …

Managing Deep Learning Development Complexity was written by Nicole Hemsoth at The Next Platform.

Cisco’s Nexus 9516 review: About line rate

Cisco Nexus 9516 review: How we did it

The device under test for this project was the Cisco Nexus 9516 data center core switch/router, a 16-slot chassis equipped with 1,024 50-gigabit Ethernet interfaces and two supervisor modules. Cisco equipped the switch with its N9K-X9732C-EX line cards, each of which offers 32, 64, or 128 ports of 100-, 50-, and 25-gigabit Ethernet capacity.The traffic generator/analyzer was Spirent TestCenter equipped with its 10/25/40/50/100G MX3 modules. The Spirent instrument has a measurement precision of +/- 2.5 nanoseconds.To read this article in full or to leave a comment, please click here

Cisco Nexus 9516 review: How we did it

Cisco Nexus 9516 data center switch aces a grueling high-density stress test

How many ports are enough at the core of the data center? How does 1,024 sound?That’s the configuration we used to assess Cisco Systems’ Nexus 9516 data center core switch. In this exclusive Clear Choice test, we assessed the Cisco data center core switch with more than 1,000 50G Ethernet ports. That makes this by far the largest 50G test, and for that matter the highest-density switch test, Network World has ever published.As its name suggests, the Nexus 9516 accepts up to 16 N9K-X9732C-EX line cards, built around Cisco’s leaf-and-spine engine (LSE) ASICs. These multi-speed chips can run at 100G rates, for up to 512 ports per chassis; 50G rates for up to 1,024 ports; or 25G rates for up to 2,048 ports. We picked the 50G rate, and partnered with test and measurement vendor Spirent Communications to fully load the switch’s control and data planes.To read this article in full or to leave a comment, please click here

Cisco Nexus 9516 data center switch aces a grueling high-density stress test

Announcing the first DockerCon Europe 2017 Speakers

Summer is flying by and DockerCon Europe 2017 (October 16-19) will be here before we know it! The DockerCon team is heads down reviewing all of the proposals submitted and we are almost ready to release a full agenda. With that, we are thrilled to share with you the DockerCon Europe 2017 Website including the first confirmed speakers and sessions.

DockerCon Europe