Over at Packet Pushers, there’s an interesting post asking why we don’t use actual user traffic to detect network failures, and hence to drive routing protocol convergence—or rather, asking why routing doesn’t react to the data place.
This is, indeed, an interesting question—and ones that’s highly relevant in our current software defined/drive world. So why not? Let me give you two lines of thinking that might be used to answer this question.
First, let’s consider the larger problem of fast convergence. Anyone who’s spent time in any of my books, or sat through any of my presentations, should know the four steps to convergence—but just in case, let’s cover them again, using a slide from my forthcoming LiveLesson on IS-IS:
There Continue reading
Because sometimes, leaf and spine are not enough.
Today we talk about how network analytics and telemetry differ from traditional monitoring, what new data sources & techniques are available, and how we can put this data to good use.
The post PQ Show 75: Talking Network Analytics And Telemetry appeared first on Packet Pushers.
Today we talk about how network analytics and telemetry differ from traditional monitoring, what new data sources & techniques are available, and how we can put this data to good use.
The post PQ Show 75: Talking Network Analytics And Telemetry appeared first on Packet Pushers.
This is the first in a series of posts about how Ansible and Ansible Tower enable you to manage your infrastructure simply, securely, and efficiently.
When we talk about Tower, we often talk in terms of Control, Knowledge, and Delegation. But what does that mean? In this series of blog posts, we'll describe some of the ways you can use Ansible and Ansible Tower to manage your infrastructure.
The first step of controlling your infrastructure is to define what it is actually supposed to be. For example, you may want to apply available updates - here's a basic playbook that does that.
--- - hosts: all gather_facts: true become_method: sudo become_user: root tasks: - name: Apply any available updates yum: name: "*" state: latest update_cache: yes
Or you may have more detailed configuration. Here's an example playbook for basic system configuration.This playbook:
Configures some users
Installs and configures chrony, sudo, and rsyslog remote logging
Sets some SELinux parameters
Normally, we’d organize our configuration into Ansible roles for reusability, but for the purpose of this exercise we're just going to use one long playbook.
We'd want to apply this as part of our standard system configuration.
Continue reading
If you missed a VMware vForum in a city near you, you can still join us on April 19th for vForum Online! At this free digital event, you’ll get practical guidance, and develop new strategies for building a digital success plan across the cloud, the virtualized network, and mobile. Continue reading