Archived from groups: comp.dcom.lans.ethernet (More info?)
I have some aging Cisco routers, and a very complex network. I'm wondering
if anyone has experience with Juniper routers, and why one would pick
Juniper versus Cisco?
Archived from groups: comp.dcom.lans.ethernet,comp.dcom.sys.cisco (More info?)
Jon Johnson wrote:
> I have some aging Cisco routers, and a very complex network. I'm
> wondering if anyone has experience with Juniper routers, and why one
> would pick Juniper versus Cisco?
[probably better suited to comp.dcom.sys.cisco - added to the group]
We're doing the same thing. We also have a very large network.
Cisco pros:
1) support model is well understood. Never have to worry about
whether they can get the parts there or not.
2) IOS is well understood.
3) Has more enterprise/legacy features.
Cisco cons:
1) IOS quality has degraded with each and every version.
2) IPSec is not as robust as it should be, IMO.
3) No support for modular upgrades. It's all or nothing.
4) You can't encrypt multicast traffic w/o using GRE tunnels. So if f
you want to encrypt OSPF & data packets, you *have* to use GRE.
5) Multiple IOS images can be a pain to manage.
6) Control plane is *just* being protected with later IOSes.
Juniper pros:
1) Operational features such as "commit" and "rollback n" can really
make backing out of changes a no brainer.
2) Performance is not really in question.
3) IPSec can be encrypted since the AS/ES PICs are IP addressable.
4) High availability is pretty much built in.
5) Some accounting counters are done on the line cards. Easy to get
stats.
6) Control plane is well protected.
7) You can do modular upgrades to JunOS.
Juniper cons:
1) Support model is still not proven. Can they hit every office that
I have??? Not sure.
2) The J series routers are a new item. Granted, Juniper's mantra of
same JunOS everywhere! is a plus.
3) The J series has a button that will reset the router to a "known
good" configuration. Can be quite useful for remote locations.
4) No support for legacy protocols. May be a deal breaker for some
enterprises.
We looked at 6500/Sup720/VPN-SMs vs M10i/M20i/AS-PICs and they are
about the same price. Performance wise, VPN-SM and AS-PICs pushed
about 480Mbps in either direction. I prefer Juniper's implementation
of AS-PICs over VPN-SM but they had the luxury of starting late in the
game.
--
hsb
"Somehow I imagined this experience would be more rewarding" Calvin
**************************ROT13 MY ADDRESS*************************
Due to the volume of email that I receive, I may not not be able to
reply to emails sent to my account. Please post a followup instead.
********************************************************************
Archived from groups: comp.dcom.lans.ethernet (More info?)
Jon Johnson wrote:
> I have some aging Cisco routers, and a very complex network. I'm wondering
> if anyone has experience with Juniper routers, and why one would pick
> Juniper versus Cisco?
>
>
We completed the transition from Cisco to Juniper a while back. Juniper
produces clean code. If you are replacing 7200/7300/7500 series routers,
you probably can get away with a M7i/10i. Juniper SE's are some of the
best I have worked with. I bet you will have a good experience.
The problem is that Cisco paid for this as far as I can tell. I wonder
if Juniper SEs were on site to tweak? I didn't read it thoroughly but
I'm thinking Cisco had an army there to assist.
It's hard to take vendor-paid-for testing too seriously. For example,
would they have let Miercom publish it if it showed that Junipers won?
--
hsb
"Somehow I imagined this experience would be more rewarding" Calvin
**************************ROT13 MY ADDRESS*************************
Due to the volume of email that I receive, I may not not be able to
reply to emails sent to my account. Please post a followup instead.
********************************************************************
First paragraph after "Key findings and conclusions," 2nd Sentence:
Juniper declined to actively participate in the testing.
> The problem is that Cisco paid for this as far as I can tell. I
wonder
> if Juniper SEs were on site to tweak? I didn't read it thoroughly
but
> I'm thinking Cisco had an army there to assist.
>
> It's hard to take vendor-paid-for testing too seriously. For
example,
> would they have let Miercom publish it if it showed that Junipers
won?
>
> hsb
>
Good points! But I admire Cisco for their "lets-get-it-on"
competitiveness.
Miercom clearly states that Juniper declined to actively participate in
the testing.
Archived from groups: comp.dcom.lans.ethernet,comp.dcom.sys.cisco (More info?)
In article <1107774984.984771.318450@g14g2000cwa.googlegroups.com>,
Brad@BradReese.Com says...
> Good points! But I admire Cisco for their "lets-get-it-on"
> competitiveness.
>
Well, maybe they knew in advance that Juniper would decline to actively
participate in testing :-).
B> First paragraph after "Key findings and conclusions," 2nd Sentence:
B> Juniper declined to actively participate in the testing.
From reading test results done by different companies I got an idea that company
which is not paying for test always "declines to actively participate".
Archived from groups: comp.dcom.lans.ethernet,comp.dcom.sys.cisco (More info?)
Begin <1107774984.984771.318450@g14g2000cwa.googlegroups.com>
On 2005-02-07, BradReeseCom <Brad@BradReese.Com> wrote:
> Hansang Bae wrote:
>> BradReeseCom wrote:
>> > Hi Hansang,
>> > You may wish to view the Miercom Cisco vs. Juniper Core Router
>> > Head-to-Head Comparison:
>> >
>> > http://www.bradreese.com/cisco-jun [...] arison.htm ^^^
Minor nit: I see an url which promises me a micros~1 generated html
page, and I get a .pdf.
> First paragraph after "Key findings and conclusions," 2nd Sentence:
>
> Juniper declined to actively participate in the testing.
``actively participate'', as ObOtherPoster notes, meaning sponsoring,
tweaking by their own experts (who subsequently aren't on-site when joe
random netadmin has to configure the stuff, facing a deadline), etc. I'd
actually prefer to have the companies I'd test equipment of to maybe
lend me the equipment and provide normal support _when I ask_, so as to
give a more accurate reflection of the reality at seen those for who the
report would be useful. So Juniper here did the right thing, where cisco
apparently was eager to emerge favourably regardless of actual merits.
In fact, I'd probably count the very fact the test company wanted
incentives from the vendor beyond the hardware to test as a red flag.
In short, the critique still stands.
>> It's hard to take vendor-paid-for testing too seriously. For
> example,
>> would they have let Miercom publish it if it showed that Junipers
> won?
>
> Good points! But I admire Cisco for their "lets-get-it-on"
> competitiveness.
I'd compare that to what micros~1 calls ``getting the facts'', but
I would count that as inviting an invocation of Godwin's law.
> Miercom clearly states that Juniper declined to actively participate in
> the testing.
Which is good for clarity, but doesn't change the critique a bit.
*looks through the report until xpdf crashes*
I can't say I like the report format a bit. It starts out with key
points and conclusions, ``powerpoint style'', before even stating what
the test tried to prove or what the full equipment list was. If that
counts as ``excellence'' I'm borrowing one of their jumps, and my
conclusion is that they just made it on my blacklist of FUD sources for
the next 15 years, regardless of who ``won'' the test.
--
j p d (at) d s b (dot) t u d e l f t (dot) n l .
``powerpoint style'' is a very loud indicator what *not* to read.
Archived from groups: comp.dcom.lans.ethernet,comp.dcom.sys.cisco (More info?)
Hi,
I have not read any of the test results or specifications
referred to in this thread.
My understanding of some network equipment testing is that
company A funds a test of company A kit vs company B kit.
They specify the test EXACTLY. The independant testers follow
the script they are paid to follow EXACTLY and get the EXACT
results that company A knew they were going to get. Company B
knows that they are in for a kicking since the test has been
specified for that purpose by clever people and declines to
participate. They fund their own test that they
specify EX............
Test results can be informative however I feel that care is
needed in interpreting them and the tests used should be
examined very carefully.
I have heard rumours of code being altered to change test
results as opposed to being optimised purely for expected
production environments.
I seem to recall that some NIC and switch vendors were rumoured
to reduce the interframe gap on CS/CDMA ethernet so that they
would "win" more often in head-to-head contests where the two
nics were connected simultaneously to the same collision domain and
both were offered trafic to transmit. The less well informed purchaser
could easily be taken in by such treatment.
An (almost obsolete now) example might be that a particular vendor
could be attacked if a competitor could find a 'reasonable'
requirement that 'forced' a configuration that resulted in traffic
being process switched.
Archived from groups: comp.dcom.lans.ethernet,comp.dcom.sys.cisco (More info?)
BradReeseCom wrote:
> Good points! But I admire Cisco for their "lets-get-it-on"
> competitiveness.
>
> Miercom clearly states that Juniper declined to actively participate
> in the testing.
I used to admire Cisco for thier competitive edge. But in recent times
(like almost all big companies) they've lost the edge. The IOS quality
is beyond shameful. I'm not saying Juniper is the panacea because we
*FOUND* bugs in their code during *ROUTINE* testing. It was almost as
if we are the *ONLY* company in the world that runs OSPF with IPSec and
GRE tunnels.
As far as paid testing goes, it's often dicated by the company that
pays for the test. So they get to determine what gets tested and how.
Cisco employs some very smart people. Juniper does too. It would be
less then trivial for both companies to come up with scenarios that
would benefit only their gear. Not saying this is what happened as I
don't have any first hand knowledge. But I saw a lot of phrases that
may may be say "hmmm"
As an example, this is typical "academia" speak....
"It has long been known that..." ==> "I haven't bothered to look up
the original referece"
"Three of the samples were chosen..." ==> "Other experiments didn't
make sense or made the research look bad so it was ignored.."
"Typical results are shown..." ==> "The best results are shown..."
You get the idea.
--
hsb
"Somehow I imagined this experience would be more rewarding" Calvin
**************************ROT13 MY ADDRESS*************************
Due to the volume of email that I receive, I may not not be able to
reply to emails sent to my account. Please post a followup instead.
********************************************************************
Archived from groups: comp.dcom.lans.ethernet,comp.dcom.sys.cisco (More info?)
* Hansang Bae <uonr@alp.ee.pbz>:
>> You may wish to view the Miercom Cisco vs. Juniper Core Router
>> Head-to-Head Comparison:
>>
>> http://www.bradreese.com/cisco-jun [...] arison.htm >>
>> as well as the Miercom Cisco vs. Juniper Edge Router Head-to-Head
>> Comparison:
>>
>> http://www.bradreese.com/cisco-jun [...] arison.htm >
>
> The problem is that Cisco paid for this as far as I can tell. I wonder
> if Juniper SEs were on site to tweak? I didn't read it thoroughly but
> I'm thinking Cisco had an army there to assist.
It tells great lengths that Miercom didn't publish the configurations
used.
You can make ANY vendor's hardware look bad if you use insider knowledge
about pathological corner cases where the hardware at hand has specific
problems and how to exploit them via specially crafted,
far-from-realworld configurations.
> It's hard to take vendor-paid-for testing too seriously.
Archived from groups: comp.dcom.lans.ethernet (More info?)
Thanks, all for the feedback. I will stay out of the analyst debate.
"BradReeseCom" <Brad@BradReese.Com> wrote in message
news:1107774984.984771.318450@g14g2000cwa.googlegroups.com...
> Hansang Bae wrote:
> > BradReeseCom wrote:
> >
> > > Hi Hansang,
> > >
> > > You may wish to view the Miercom Cisco vs. Juniper Core Router
> > > Head-to-Head Comparison:
> > >
> > > http://www.bradreese.com/cisco-jun [...] arison.htm >
> First paragraph after "Key findings and conclusions," 2nd Sentence:
>
> Juniper declined to actively participate in the testing.
>
> > > as well as the Miercom Cisco vs. Juniper Edge Router Head-to-Head
> > > Comparison:
> > >
> > > http://www.bradreese.com/cisco-jun [...] arison.htm >
> First paragraph after "Key findings and conclusions," 2nd Sentence:
>
> Juniper declined to actively participate in the testing.
>
> > The problem is that Cisco paid for this as far as I can tell. I
> wonder
> > if Juniper SEs were on site to tweak? I didn't read it thoroughly
> but
> > I'm thinking Cisco had an army there to assist.
> >
> > It's hard to take vendor-paid-for testing too seriously. For
> example,
> > would they have let Miercom publish it if it showed that Junipers
> won?
> >
> > hsb
> >
>
> Good points! But I admire Cisco for their "lets-get-it-on"
> competitiveness.
>
> Miercom clearly states that Juniper declined to actively participate in
> the testing.
>
> Brad Reese
>
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.