[62455] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Worst design decisions?

daemon@ATHENA.MIT.EDU (Justin Shore)
Thu Sep 18 11:34:41 2003

Date: Thu, 18 Sep 2003 10:19:20 -0500 (CDT)
From: Justin Shore <listuser@numbnuts.net>
To: David Barak <thegameiam@yahoo.com>
Cc: nanog@merit.edu
In-Reply-To: <20030918144633.79146.qmail@web14904.mail.yahoo.com>
Errors-To: owner-nanog-outgoing@merit.edu


On Thu, 18 Sep 2003, David Barak wrote:

> 
> 
> --- Matt <acheron@qwest.net> wrote:
> > I've got a couple others in my head from 3Com and a
> > couple of others, 
> > but I thought I'd get the ball rolling.  So, what do
> > you think?
> > 
> 
> Personally my issues are console-cable related: is
> there a benefit to the HUGE variety of console pinouts
> used by the various hardware vendors?  Just look at
> vendor C as an example (I can think of four types
> immediately) - not only are the types of console port
> not standardized, but process for determining the
> location of the port clearly involved the reading of
> entrails...

<Applause>

I can think of 6 different console cable pinouts and connectors that 
Enterasys (Cabletron) has used over the years.  No wait, make that 7.  How 
could I forget the inherited Fore ATM architecture and subsequent blades.  
Could people just pick ONE pinout and connector and stick with it?  
Please!  Of course I also have a Cisco 675 that I've been unable to use 
for years simply because I have yet to figure out what ungodly pinout 
Cisco used in it.

Justin


home help back first fref pref prev next nref lref last post