Re: [j-nsp] Recommended Releases now posted for MX, M, T, QFX - Update!

2012-02-01 Thread Bjørn Tore
Den 01.02.2012 08:26, skrev sth...@nethelp.no: Yup.. our hindsight would have been to continue deploying E/ERX ;) While we don't use those, I certainly agree that they sound like a much better option from Juniper than the MX. The Juniper ERX/E-series has its own series of challenges. They have

Re: [j-nsp] Recommended Releases now posted for MX, M, T, QFX - Update!

2012-02-01 Thread Paul Stewart
; juniper-nsp@puck.nether.net Subject: Re: [j-nsp] Recommended Releases now posted for MX, M, T, QFX - Update! > > Yup.. our hindsight would have been to continue deploying E/ERX ;) > > While we don't use those, I certainly agree that they sound like a > much better option from

Re: [j-nsp] Recommended Releases now posted for MX, M, T, QFX - Update!

2012-01-31 Thread sthaug
> > Yup.. our hindsight would have been to continue deploying > > E/ERX ;) > > While we don't use those, I certainly agree that they sound > like a much better option from Juniper than the MX. The Juniper ERX/E-series has its own series of challenges. They have a *lot* of BRAS functionality whic

Re: [j-nsp] Recommended Releases now posted for MX, M, T, QFX - Update!

2012-01-31 Thread Mark Tinka
On Tuesday, January 31, 2012 06:52:19 PM Paul Stewart wrote: > Yup.. our hindsight would have been to continue deploying > E/ERX ;) While we don't use those, I certainly agree that they sound like a much better option from Juniper than the MX. Mark. signature.asc Description: This is a digita

Re: [j-nsp] Recommended Releases now posted for MX, M, T, QFX - Update!

2012-01-31 Thread Paul Stewart
d Releases now posted for MX, M, T, QFX - Update! On Tuesday, January 31, 2012 06:26:44 PM Mark Tinka wrote: > The MX is nowhere near ready to run as BRAS. But like you, we decided > to migrate to it, so we have no choice but to run bleeding edge Junos > 11.4R1 as well, just to g

Re: [j-nsp] Recommended Releases now posted for MX, M, T, QFX - Update!

2012-01-31 Thread Mark Tinka
On Tuesday, January 31, 2012 06:26:44 PM Mark Tinka wrote: > The MX is nowhere near ready to run as BRAS. But like > you, we decided to migrate to it, so we have no choice > but to run bleeding edge Junos 11.4R1 as well, just to > get basic things the outgoing Redback is able to do, as > well as s

Re: [j-nsp] Recommended Releases now posted for MX, M, T, QFX

2012-01-31 Thread Mark Tinka
On Tuesday, January 31, 2012 06:12:02 PM Paul Stewart wrote: > One incredible frustration we're going through lately on > the MX boxes is the BRAS function as Mark mentioned > briefly . we're up to "bleeding edge" code now > (11.4R1.14) just to get what we consider typical > features of a BRAS

Re: [j-nsp] Recommended Releases now posted for MX, M, T, QFX

2012-01-31 Thread Paul Stewart
-Original Message- From: juniper-nsp-boun...@puck.nether.net [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Mark Tinka Sent: Tuesday, January 31, 2012 3:05 AM To: James Jones Cc: juniper-nsp@puck.nether.net Subject: Re: [j-nsp] Recommended Releases now posted for MX, M, T, QFX On Tues

Re: [j-nsp] Recommended Releases now posted for MX, M, T, QFX

2012-01-31 Thread Mark Tinka
On Tuesday, January 31, 2012 12:32:26 AM James Jones wrote: > I am just curious what issues you guys are having with > the junos releases? Run through the archives to get a feel for what issues folk are facing. And these are just the issues that folk have decided to share. There are others tha

Re: [j-nsp] Recommended Releases now posted for MX, M, T, QFX

2012-01-30 Thread Chris Cappuccio
that only took...about 5 years ? sweet, juniperdude. Chris Kawchuk [juniperd...@gmail.com] wrote: > Just noticed this today - Seems JNPR has filled out the recommended release > JunOS matrix for all the products now (incl M, T, MX, QFX) > > http://kb.juniper.net/InfoCenter/index?page=content&id=

Re: [j-nsp] Recommended Releases now posted for MX, M, T, QFX

2012-01-30 Thread James Jones
I am just curious what issues you guys are having with the junos releases? I am currently not having issues with any of my Juniper kit. It would be interesting to understand the use cases in which you are seeing issues. Sent from my iPhone On Jan 30, 2012, at 6:39 AM, Mark Tinka wrote: > On M

Re: [j-nsp] Recommended Releases now posted for MX, M, T, QFX

2012-01-30 Thread Mark Tinka
On Monday, January 30, 2012 07:31:39 PM Derick Winkworth wrote: > R9 will be good... we hope. That's what we always say starting from R4, and yet here we are... again :-). Mark. signature.asc Description: This is a digitally signed message part. __

Re: [j-nsp] Recommended Releases now posted for MX, M, T, QFX

2012-01-30 Thread Derick Winkworth
/ From: Paul Stewart To: juniper-nsp@puck.nether.net Sent: Monday, January 30, 2012 5:12 AM Subject: Re: [j-nsp] Recommended Releases now posted for MX, M, T, QFX Hey Chris yeah, that just showed up about 2 weeks ago (at least that's when I notic

Re: [j-nsp] Recommended Releases now posted for MX, M, T, QFX

2012-01-30 Thread Paul Stewart
--Original Message- From: juniper-nsp-boun...@puck.nether.net [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Chris Kawchuk Sent: Monday, January 30, 2012 3:54 AM To: juniper-nsp@puck.nether.net Subject: [j-nsp] Recommended Releases now posted for MX, M, T, QFX Just noticed this today -

[j-nsp] Recommended Releases now posted for MX, M, T, QFX

2012-01-30 Thread Chris Kawchuk
Just noticed this today - Seems JNPR has filled out the recommended release JunOS matrix for all the products now (incl M, T, MX, QFX) http://kb.juniper.net/InfoCenter/index?page=content&id=KB21476 - Chris. ... Riding the 10.4 MX Release Train. Next Stop, R9.