CTS 079: GUI or CLI

Clear To Send: Wireless Network Engineering - A podcast by Rowell Dionicio and François Vergès - Mondays

Categories:

How do you like to configure and maintain your Wi-Fi infrastructure? Do you use GUI or CLI? If both, when do you use CLI? When do you use GUI? How we are trained might affect the way we approach management. In this episode we discuss the pros and cons of using both GUI (graphical user interface) and CLI (command line interface). What are the pros of using the GUI? * Dashboards * Easier to configure multiple APs at the same time * Easier to perform multiple changes at the same time * Do you need a separate GUI system What are the cons of using the GUI? * Debugging * Not all commands are available * Can be slower * Has a connotation of being for a noob What are the pros of using CLI? * It’s kool 😉 * Can be faster * More command available * Debugging and troubleshooting is easier and more thorough * Needed for initial setup * Getting the exact output What are the cons of using CLI? * Need to know the commands * Can take more time to display some information (vs the ease of a dashboard) * Some operations are more complicated (file transfers) * Different versions for CLI Usually, when provisioning a network device you must go through an initial set up which is done using the command line interface. Examples are setting up a wireless LAN controller or initial provisioning of an AP. Do you use configuration templates using command line or graphical user interface? Was it custom made or defined as part of your Network Management System? How do you adapt it to a new device you want to configure?

Visit the podcast's native language site