netpalm VS netmiko

Netpalm (https://github.com/tbotnz/netpalm) is my goto for "if you actually need to talk to a device".

You might look at github.com/tbotnz/netpalm.

if you want something thats already been built checkout netpalm https://github.com/tbotnz/netpalm

Others have given you good answers. Another alternative is something like netpalm, which is just a service you deploy, and then you send it jobs via REST API, and it does all the direct interaction with the devices including balancing work over worker nodes and handling async, etc.

Made this, https://github.com/tbotnz/netpalm. Saves around $60k per year compared with $vendors orchestrator

Checkout https://github.com/tbotnz/netpalm

Script and netpalm for execution

Netpalm?

Curiously I've been googling this and not much out there. This post https://github.com/ktbyers/netmiko/issues/988 has the same problem but I don't think it got resolved.

If you can ssh into them, I'd try netmiko: https://github.com/ktbyers/netmiko . It's an ssh library specifically for network devices, and deals with some common issue you might encounter when using pure ssh.

You really should use something like https://github.com/ktbyers/netmiko and not be poking this stuff with SNMP.

Looks like that should already be incorporated in to Netmiko's Powerconnect class: https://github.com/ktbyers/netmiko/issues/1782

A good chunk of OpenStack is written in Python. The repositories have some very well-written code. F5 Networks has a well-maintained repository for their SDK. And, Kirk Byers wrote Netmiko, a fantastic library for working with network gear.

You could enable SSH on the esxi box and use Netmiko(https://github.com/ktbyers/netmiko) from Python to send VMware commands over the CLI. You can do most everything from the CLI and you can parse output as needed

Netmiko Source Code : Netmiko Github API reference (must check for more functionality) : Netmiko Doc

Python (open source): Reading other people's code is another way to launch your Python knowledge forward exponentially. As I was extremely interested in network automation, I used Netmiko heavily. And just as luck would have it, Kirk Byers (the author of Netmiko) was on the Network To Code Slack workspace too. I examined the Netmiko code base frequently and would then ask him the how's and why's of what I saw. His answers gave me insights that I hadn't gotten from anywhere else.