CLI Still Sucks for Automation
Using network CLI for automation has always been fragile. But it keeps surprising me with the way it breaks. This time, it was a combination of Ansible, Arista, replace: config and terminal length used as a config command.
The Problem
I often hang out in the NTC Slack channel. A user reported they were having a problem with Ansible and EOS. Basic changes worked, but when they used eos_config with the replace: config option, it just timed out. We knew basic authentication & connectivity was fine, it had to be something else.
But it made no sense, because these modules are widely used. What’s going on?
Background #1: Pagination
Some commands produce more than one screen’s worth of output - for example, show run can be hundreds of lines long. Most screens don’t have hundreds of lines, so pagination is used. The network Continue reading

This platform, TrueConnect Hybrid, provides customers with a full-stack of networking and internet...

It also announced a product that integrates secondary storage with the Nutanix platform providing a...
According to IDC Research Director Rajesh Ghai, Altiostar has "obviously come to the market to...
“We are dancing again. You have seen our young management in development. I hope in the next six...
Sprint continued to play the victim and struck a defeated tone during its fiscal year 2018 fourth...