Would love to a good open source TR69 interface.
On Mon, Nov 28, 2011 at 3:35 PM, Ray Soucy wrote:
> > 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.
>
> This.
>
> I would love a good REST API for everything; I would almost be wi
> 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.
This.
I would love a good REST API for everything; I would almost be willing
to give up the CLI for it (almost).
--
Ray Soucy
Epic Communications Specialist
Phone: +1 (207) 561-
- Original Message -
> From: "James Jones"
> Well said. I write scripts all day long to perform automation on networking
> equipment. A device needs to have a CLI, but if you have a GUI too make for
> darn sure that I can access all features in either one.
It is a relatively well establi
On Mon, 28 Nov 2011 13:25:21 EST, Ray Soucy said:
> 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.
Compare the number of customers that insist on a
- Original Message -
> From: "Ray Soucy"
> If someone wants a managed switch, they probably intend to manage it.
And that's all there is to be said about that. Nicely played, Ray.
Cheers,
-- jra
--
Jay R. Ashworth Baylink j...@baylink.com
Designe
Ray Soucy 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 us
On Mon, Nov 28, 2011 at 1:25 PM, Ray Soucy 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 d
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
What this really comes down to, I think, is figuring out how your "gut level"
concerns fit into the big picture, and to then put that into terms that the
people responsible for the big picture can use to make a good decision.
Finances do matter. Getting your employer to spend money it doesn't h
On Fri, Nov 25, 2011 at 12:01 AM, Robert Bonomi wrote:
> The trick to deailing with this as a propellorhead[sic] is to include a
> *monetized* estimate of the increased manpower OPEX of using the 'dog to
> work with' box. And a TCOS figure over the projected lifetime of the
> units. No need to
Jonathon Exley wrote;
>
> That's the problem - as a propellorhead I don't make the purchasing decisi
> ons. I can recommend products but low cost speaks more loudly than "this g
> ear is a dog to work with".
> I don't really believe that manufacturers make crippleware user interfaces
> for thi
e was already some sort of usability guide around that
> could be shown to the manufacturers with a "please read this" note attached.
> Is anyone aware of such a thing?
>
>
> Jonathon.
>
>
> From: Keegan Holley [mailto:keegan.hol...@sungard.com]
> Sent: Friday, 25 N
of such a thing?
Jonathon.
From: Keegan Holley [mailto:keegan.hol...@sungard.com]
Sent: Friday, 25 November 2011 4:12 p.m.
To: Jonathon Exley
Cc: nanog@nanog.org
Subject: Re: Network device command line interfaces
I may have a different opinion here, but I not sure I'd call any CLI easy to
work
I may have a different opinion here, but I not sure I'd call any CLI easy
to work with. Cisco's training machine is so efficient that some learn IOS
before leaving high school, so the fact that we all consider IOS easy to
work with is relative. Just look at the "router" command. Most of us know
Doug Barton writes:
> On 11/24/2011 11:58, Jonathon Exley wrote:
>> That's the problem - as a propellorhead I don't make the purchasing
>> decisions. I can recommend products but low cost speaks more loudly than
>> "this gear is a dog to work with".
>
> That's where you get a chance to impres
On 11/24/2011 11:58, Jonathon Exley wrote:
> That's the problem - as a propellorhead I don't make the purchasing
> decisions. I can recommend products but low cost speaks more loudly than
> "this gear is a dog to work with".
That's where you get a chance to impress the business folks by using
t
That's the problem - as a propellorhead I don't make the purchasing decisions.
I can recommend products but low cost speaks more loudly than "this gear is a
dog to work with".
I don't really believe that manufacturers make crippleware user interfaces for
thier products to encourage people to bu
> Yes, don't buy the cheap stuff :)
Until we do, the other stuff remains expensive.
mike
On Wed, Nov 23, 2011 at 8:53 PM, Phil Regnauld wrote:
> Jonathon Exley (Jonathon.Exley) writes:
>> However vendors of low cost routers/switches/muxes
>
> Hi Jonathon, have you ever tried to work with
On Thu, Nov 24, 2011 at 04:41:01AM +, Jonathon Exley wrote:
> Does anyone else despair at the CLIs produced by networking vendors?
Yes.
> Doe this p*** off anyone else? The business part of the company says
> "This device is great! It's cheap and does everything." However the
> poor sap who i
> However vendors of low cost routers/switches/muxes seem to take a stab in
> the dark and produce some really nasty stuff. I have a personal hate of
> text based menus and binary config backup files.
>
Not necessarily it has to be cheap to have text based menus and binary
config backups, it can b
If only it were that simple.
Try explaining the difference between the blinky lights on a 3750 and the
netgear switch to a CFO who has little tech background.
On Wed, Nov 23, 2011 at 8:51 PM, Dobbins, Roland wrote:
>
> On Nov 24, 2011, at 11:41 AM, Jonathon Exley wrote:
>
> > I have a personal
On Nov 24, 2011, at 11:41 AM, Jonathon Exley wrote:
> I have a personal hate of text based menus and binary config backup files.
So, the obvious solution is to buy the products of vendors whose CLIs one finds
least offensive, is it not?
;>
Jonathon Exley (Jonathon.Exley) writes:
> However vendors of low cost routers/switches/muxes
Hi Jonathon, have you ever tried to work with a Catalyst Express 500 ?
A good example of a fully functional IOS device, where the vendor went
out of their way to disable Telnet/SSH,
Does anyone else despair at the CLIs produced by networking vendors?
Real routers use a CLI that is command based, like IOS, TiMOS or Junos. These
interfaces work well over low bandwidth connections (unlike web interfaces),
can work with config backup systems like RANCID, have a (mostly) consiste
24 matches
Mail list logo
