On Fri, Nov 07, 2008 at 10:50:29PM +0100, [EMAIL PROTECTED] wrote:
> > I've done L2VPN (Kompella), L2Ckt (Martini), VRF, full BGP routes,
> > LDP, RSVP-TE on an MX960, and it all seems to 'work' so far.
>
> VPLS (BGP based), Martini, VRF, full BGP routes, LDP for Martini, IPv6,
> RSVP-TE on MX24
Until the end of the year, Juniper has a promotion for MX Series.
It gives 75% off (under price list) ... for 10 Giga and Giga L3 DPCs.
Try to talk with you Juniper Sale Contact.
The will promote this promotion to wait for the new EX-8200 family.
I think MX Family would support SDH/Sonet DPCs.
> I'm not sure I follow...do you not consider Foundry's MLX and
> XMR lines to be 'routers' ? I admit, they've essentially taken a
> switch and taught it to route.similar to the way Juniper took a
> router and are teaching it to switch (MX doing STP, etc).
We haven't seriously looked
I'm not sure I follow...do you not consider Foundry's MLX and
XMR lines to be 'routers' ? I admit, they've essentially taken a
switch and taught it to route.similar to the way Juniper took a
router and are teaching it to switch (MX doing STP, etc). I think
it's still a relatively appl
On Fri, Nov 7, 2008 at 06:36, Nalkhande Tarique Abbas
<[EMAIL PROTECTED]> wrote:
>
> Try Removing as-overide from R2.
Not if you want to advertise routes both from P2 to P3 and from P3 to P2.
>
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Tom
> I've done L2VPN (Kompella), L2Ckt (Martini), VRF, full BGP routes,
> LDP, RSVP-TE on an MX960, and it all seems to 'work' so far.
VPLS (BGP based), Martini, VRF, full BGP routes, LDP for Martini, IPv6,
RSVP-TE on MX240 and MX480. It all seems to "just work" here too. Found
one netflow bug (ifI
I've done L2VPN (Kompella), L2Ckt (Martini), VRF, full BGP routes,
LDP, RSVP-TE on an MX960, and it all seems to 'work' so far. Done
some QoS testing as well, though not yet finished. It too, seems to
just 'work'. I haven't found much that I 'dislike' about it yet
(other than the -R cards not
On Fri, Nov 07, 2008 at 03:22:03PM -0200, Rubens Kuhl Jr. wrote:
> > Basically, can someone give me reasons apart from "we don't need SONET
> > or any other WAN interfaces, and it's cheaper per port", why should we
> > NOT choose an MX box? Are there any gotchas waiting in the wings for
> > someon
Price would be the big thing I'd think of. But like anything, it will
depend on your deployment model. What are you looking for in your switch?
What's important to you?
They're cool switches though!
Scott
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf O
> Basically, can someone give me reasons apart from "we don't need SONET
> or any other WAN interfaces, and it's cheaper per port", why should we
> NOT choose an MX box? Are there any gotchas waiting in the wings for
> someone who's used to the full flavored goodness that is the M/T
> series?
Bec
> We've been using Juniper M/T series in service provider scenarios for
> a couple of years now, and really like them. As part of an equipment
> life cycle refresh, we're considering replacing our core (campus
> enterprise) network with something in the MX series; a la this post:
>
> http://marc.
We've been using Juniper M/T series in service provider scenarios for
a couple of years now, and really like them. As part of an equipment
life cycle refresh, we're considering replacing our core (campus
enterprise) network with something in the MX series; a la this post:
http://marc.info/?l=juni
Try Removing as-overide from R2.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tomasz Opala
Sent: Friday, November 07, 2008 3:30 PM
To: juniper-nsp@puck.nether.net
Subject: [j-nsp] hidden route
Hi gurus,
Imagine following topology:
P2(AS11)--R2(A
Hi gurus,
Imagine following topology:
P2(AS11)--R2(AS100)---R3(AS100)---P3(AS11)
In order to advertise route 199.199.0.0/16 (static, redistriuted to BGP)
from router P2 to P3 (and some routes form P3 to P2), as-override has been
configured on both R2 and R3:
[EMAIL PROTECTED] show g
14 matches
Mail list logo