[31741] in North American Network Operators' Group
RE: Anyone heard anything Good or Bad about Juniper equipment ?
daemon@ATHENA.MIT.EDU (Daniel L. Golding)
Sat Oct 14 22:35:58 2000
Date: Sat, 14 Oct 2000 22:30:07 -0400 (EDT)
From: "Daniel L. Golding" <dan@netrail.net>
To: James Cabe <jcabe@genuity.net>
Cc: Vijay Gill <vijay@umbc.edu>,
"Mr. James W. Laferriere" <babydr@baby-dragons.com>, nanog@merit.edu
In-Reply-To: <000001c03618$5bd75e90$fc200204@jcabe.sys.gtei.net>
Message-ID: <Pine.LNX.4.10.10010142229450.6311-100000@outage.netrail.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Errors-To: owner-nanog-outgoing@merit.edu
Yes. (although interop with Cisco's is pretty smooth.)
On Sat, 14 Oct 2000, James Cabe wrote:
> OSPF between Junipers, or between Junipers and other vendor's hardware?
>
> > -----Original Message-----
> > From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu]On Behalf Of
> > Daniel L. Golding
> > Sent: Saturday, October 14, 2000 11:53 AM
> > To: Vijay Gill
> > Cc: Mr. James W. Laferriere; nanog@merit.edu
> > Subject: Re: Anyone heard anything Good or Bad about Juniper equipment ?
> >
> >
> >
> > Stay away from the OSPF. 9 out of 10 engineers agree: If you use Juniper,
> > use ISIS. Or become very good at troubleshooting OSPF.
> >
> > - Dan Golding
> >
> > On Fri, 13 Oct 2000, Vijay Gill wrote:
> >
> > >
> > > On Fri, 13 Oct 2000, Mr. James W. Laferriere wrote:
> > >
> > > >
> > > >
> > > > Hello All , Replying off list would be best & I can summarize if
> > > > anyone has interest . Have my eye's on acquiring a couple of
> > > > their larger units . I Just need some feedback from -real- users .
> > >
> > > I have worked for two very large providers with juniper equipment. Like
> > > all equipment, they have their flaws but they are so much
> > better than the
> > > next closes vendor that its not even funny.
> > >
> > > Much better response from engineers, much better code, much
> > higher density
> > > per rack, and their line cards actually can do oc192
> > >
> > > /vijay
> > >
> > >
> > >
> >
> >
> >
>
