Do window and linux suck when managing multiple subnet interfaces?

[deanwebb]

I retiterate

Do everything on CentOS, do the RHCA, read the official RH doco. 90% of what you learn is portable across distributions, especially with systemd borging everything (not trying to start THAT flamewar again...)

I agree with CentOS as a platform of choice. Two vendors I work with (Tufin and ForeScout) use CentOS as a base for their systems. And if you add your flavor to the terms in the Google search on what to do in order to take care of a particular function, the results are very well targeted.

For example, when dealing with an RSA key that needs replacing in order to reconnect via SSH, there are several methods available. I found out the hard way that trying a method for the wrong distro, or the right distro missing the packages invoked, simply falls flat. But, sticking with the page relevant for CentOS, I kept going down the page and got my answer.

I hear what you're saying, ggnfs000. You're frustrated right now and hitting dead ends. I was there, as well, and with both Windows and Linux. My experience has been that if there's an easy way to do something, it's easiest in Windows. If there's a hard way to do something, it is very much harder to do in Windows. When it comes to scripting and execution, I prefer Linux over Windows and even Cisco Prime. There is so much flexibility in Linux, I felt that it was worth my time to learn about it as I used it in work.

Back to the OP, if you want to manage multiple subnet interfaces and have a choice of OS, go with Linux. That's pretty much what Cisco, Juniper, and Arista did, among others.