nanog mailing list archives
Re: Network device command line interfaces
From: Alex Harrowell <a.harrowell () gmail com>
Date: Mon, 28 Nov 2011 18:32:53 +0000
Ray Soucy <rps () maine edu> wrote:
One of the biggest benefits to a CLI is the ability to easily script tasks. In a Cisco environment I can roll out major changes to hundreds of switches in seconds, for example. A lot of network vendors have been trying to make network devices more simple and easier to use while the complexity of networking has gone up. Seems like the wrong direction to me. If someone wants a managed switch, they probably intend to manage it. I think a big key to the success of Cisco (and Juniper, etc) has been that they "get it" in this respect. Even companies like Vyatta have invested time in a Web UI rather than expanding the core functionality offered (multicast routing support, for example), which doesn't seem like the best idea. On Wed, Nov 23, 2011 at 11:41 PM, Jonathon Exley < Jonathon.Exley () kordia co nz> wrote:Does anyone else despair at the CLIs produced by networking vendors? Real routers use a CLI that is command based, like IOS, TiMOS orJunos.These interfaces work well over low bandwidth connections (unlike web interfaces), can work with config backup systems like RANCID, have a (mostly) consistent structure and good show commands. However vendors of low cost routers/switches/muxes seem to take astab inthe dark and produce some really nasty stuff. I have a personal hateoftext based menus and binary config backup files. Doe this p*** off anyone else? The business part of the company says"Thisdevice is great! It's cheap and does everything." However the poorsap whois given the task to make it work has to wrestle with a badlydesigned userinterface and illogical syntax. Maybe the vendors need some sort of best practices guide for what manageability features their kit needs to support to make themacceptableto the market. Does anyone know if there is anything along theselines?Jonathon. This email and attachments: are confidential; may be protected by privilege and copyright; if received in error may not be used,copied, orkept; are not guaranteed to be virus-free; may not express the viewsofKordia(R); do not designate an information system; and do not giverise toany liability for Kordia(R).-- Ray Soucy Epic Communications Specialist Phone: +1 (207) 561-3526 Networkmaine, a Unit of the University of Maine System http://www.networkmaine.net/
If you've done a proper CLI, you can easily do a good REST API. If you've done that a good Web GUI is possible. It doesn't work the other way round. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity.
Current thread:
- Re: Network device command line interfaces, (continued)
- Re: Network device command line interfaces Steve Gibbard (Nov 28)
- Re: Network device command line interfaces Aftab Siddiqui (Nov 23)
- Re: Network device command line interfaces Jussi Peltola (Nov 23)
- Re: Network device command line interfaces Keegan Holley (Nov 24)
- RE: Network device command line interfaces Jonathon Exley (Nov 24)
- Re: Network device command line interfaces Keegan Holley (Nov 24)
- RE: Network device command line interfaces Jonathon Exley (Nov 24)
- Re: Network device command line interfaces Ray Soucy (Nov 28)
- Re: Network device command line interfaces James Jones (Nov 28)
- Re: Network device command line interfaces Jay Ashworth (Nov 28)
- Re: Network device command line interfaces Jay Ashworth (Nov 28)
- Re: Network device command line interfaces Alex Harrowell (Nov 28)
- Re: Network device command line interfaces Ray Soucy (Nov 28)
- Re: Network device command line interfaces James Jones (Nov 28)
- Re: Network device command line interfaces James Jones (Nov 28)
- Re: Network device command line interfaces Valdis . Kletnieks (Nov 28)