Re: [j-nsp] Speed

2013-04-10 Thread Saku Ytti
On (2013-04-10 00:01 +0200), Benny Amorsen wrote:

 Yes, you can in theory cause microbursting of UDP if you want. I am just
 not sure which tool I would use to do that. Typical UDP tests like iperf
 attempt to do perfect timing of packets so bursts are avoided, and they
 seem to do a fairly good job of it.

Fair point. This is iperf:

if ( isUDP( mSettings ) ) {
...
delay_target = (int) ( mSettings-mBufLen * ((kSecs_to_usecs * 
kBytes_to_Bits)
 / mSettings-mUDPRate) );


I still think UDP is the correct way to test network, making UDP burst (or not
burst) is easy, forcing TCP to behave as you desire is harder.


Quickly looking 'nuttcp 7.2.1' seems to support bursting,
http://lcp.nrl.navy.mil/nuttcp/beta/nuttcp-7.2.1.c

-- 
  ++ytti
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


Re: [j-nsp] curious optic issue

2013-04-10 Thread Alexandre Snarskii
On Tue, Jan 29, 2013 at 11:04:10AM +0200, Saku Ytti wrote:
  Fix is to remove+reinsert optic, or reload router. I've not yet tried
  'test xfp 1 power off|on', but I'm guessing it'll help too.
 
 I can confirm that 'test xfp 1 power off|on' 'fixes' the issue as well. 

Are there any way to power-off SFP+ in MPC-3D-16XGE as well ? 
Looks like we have the same issue in one more location... :(

-- 
In theory, there is no difference between theory and practice. 
But, in practice, there is. 

___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


Re: [j-nsp] curious optic issue

2013-04-10 Thread Sidney Boumendil
On Wed, Apr 10, 2013 at 11:06 AM, Alexandre Snarskii s...@snar.spb.ruwrote:

 Are there any way to power-off SFP+ in MPC-3D-16XGE as well ?
 Looks like we have the same issue in one more location... :(


Maybe you need the still uncommon low power transceiver =1.5 Watts just
like in the other camp to power on all ports on high density 10Gig line
cards. This is supposedly because of thermal dissipation limits.
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


Re: [j-nsp] M10i

2013-04-10 Thread Per Granath
Yes.

-Original Message-
From: juniper-nsp-boun...@puck.nether.net 
[mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Ahmad Alhady
Sent: Wednesday, April 10, 2013 12:38 PM
To: Michel de Nostredame
Cc: nsp-juniper
Subject: Re: [j-nsp] M10i

But does MX80 support SDH ?


On Wed, Apr 10, 2013 at 11:30 AM, Michel de Nostredame
d.nos...@gmail.comwrote:

 Ah~ M20 does not support 10GE interface, also M20 is already EOL.
 MX could be good choice, see

 http://www.juniper.net/us/en/local/pdf/datasheets/1000378-en.pdf
 for MX80 cards, and

 http://www.juniper.net/us/en/products-services/routing/mx-series/
 for all MX series.

 --
 Michel~

 On Tue, Apr 9, 2013 at 7:07 PM, Jonathan Lassoff j...@thejof.com wrote:
  I think you'll need at least an M20 for your 10 GigE requirement as 
  well
 as
  SDH.
 
  If you can somehow get a different transit circuit than your SDH 
  one, an
  MX5 would be a much closer (throughput-wise) and better
 bang-for-your-buck
  replacement for a 7206 than an M-series.
  J-series with a T1 module could also work, depending on your STM-1.
 
  If you need SDH though, you'll need M or T. J can do T1s.
 
  --j
 
  On Tue, Apr 9, 2013 at 6:28 PM, Orlando Cordova Gonzales  
  orlando.cordova.gonza...@gmail.com wrote:
 
  hello,
 
  I need to change a CISCO 7206 router that computer I recommend one 
  of
 the
  requirements is that you have two 10G interfacez two interfacez 1G 
  and
 STM1
  interface to connect with the ISP was thinking M10i Router but I do 
  not support 10g interface.
 
  thank you very much for your help.
  ___
  juniper-nsp mailing list juniper-nsp@puck.nether.net 
  https://puck.nether.net/mailman/listinfo/juniper-nsp
 
  ___
  juniper-nsp mailing list juniper-nsp@puck.nether.net 
  https://puck.nether.net/mailman/listinfo/juniper-nsp
 ___
 juniper-nsp mailing list juniper-nsp@puck.nether.net 
 https://puck.nether.net/mailman/listinfo/juniper-nsp

___
juniper-nsp mailing list juniper-nsp@puck.nether.net 
https://puck.nether.net/mailman/listinfo/juniper-nsp

___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


Re: [j-nsp] Stackable switches, looping stacking ports

2013-04-10 Thread Tom Storey
So I imagine that might help with latency, but is it going to have any
affect on bit rate throughput?


On 9 April 2013 21:05, Chuck Anderson c...@wpi.edu wrote:

 On Tue, Apr 09, 2013 at 11:48:36AM -0700, joel jaeggli wrote:
  On 4/9/13 11:15 AM, Tom Storey wrote:
  Hey all.
  
  A colleague of mine tells me that, if you have a single stackable switch
  (not in a stack obviously) and do not loop the two stacking ports on the
  back using the stacking cable that comes in the box, then you reduce the
  effective throughput of the switch.
 
  The ex4200's asic has a capacity of 136Gb/s from the front panel
  ports which is 100% of line rate across all ports. I don't imagine
  connecting the asic back to itself is that useful or usable
  topology.

 It does make a positive difference to loop back the stack cable on a
 standalone unit.  See this diagram:

 http://blog.cochard.me/2010/08/juniper-ex-4200-internal-pfe-routing-in.html

 Connecting from ports 0-23 to 24-47 has to normally cross 3 internal
 PFEs.  If you connect VCP-0 to VCP-1, then it only has to cross 2
 PFEs.

___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


Re: [j-nsp] M10i

2013-04-10 Thread Correa Adolfo
I tought MX series were purely ethernet.

-Original Message-
From: juniper-nsp-boun...@puck.nether.net 
[mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Per Granath
Sent: miércoles, 10 de abril de 2013 06:31 a.m.
To: Ahmad Alhady; Michel de Nostredame
Cc: nsp-juniper
Subject: Re: [j-nsp] M10i

Yes.

-Original Message-
From: juniper-nsp-boun...@puck.nether.net 
[mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Ahmad Alhady
Sent: Wednesday, April 10, 2013 12:38 PM
To: Michel de Nostredame
Cc: nsp-juniper
Subject: Re: [j-nsp] M10i

But does MX80 support SDH ?


On Wed, Apr 10, 2013 at 11:30 AM, Michel de Nostredame
d.nos...@gmail.comwrote:

 Ah~ M20 does not support 10GE interface, also M20 is already EOL.
 MX could be good choice, see

 http://www.juniper.net/us/en/local/pdf/datasheets/1000378-en.pdf
 for MX80 cards, and

 http://www.juniper.net/us/en/products-services/routing/mx-series/
 for all MX series.

 --
 Michel~

 On Tue, Apr 9, 2013 at 7:07 PM, Jonathan Lassoff j...@thejof.com wrote:
  I think you'll need at least an M20 for your 10 GigE requirement as 
  well
 as
  SDH.
 
  If you can somehow get a different transit circuit than your SDH 
  one, an
  MX5 would be a much closer (throughput-wise) and better
 bang-for-your-buck
  replacement for a 7206 than an M-series.
  J-series with a T1 module could also work, depending on your STM-1.
 
  If you need SDH though, you'll need M or T. J can do T1s.
 
  --j
 
  On Tue, Apr 9, 2013 at 6:28 PM, Orlando Cordova Gonzales  
  orlando.cordova.gonza...@gmail.com wrote:
 
  hello,
 
  I need to change a CISCO 7206 router that computer I recommend one 
  of
 the
  requirements is that you have two 10G interfacez two interfacez 1G 
  and
 STM1
  interface to connect with the ISP was thinking M10i Router but I do 
  not support 10g interface.
 
  thank you very much for your help.
  ___
  juniper-nsp mailing list juniper-nsp@puck.nether.net 
  https://puck.nether.net/mailman/listinfo/juniper-nsp
 
  ___
  juniper-nsp mailing list juniper-nsp@puck.nether.net 
  https://puck.nether.net/mailman/listinfo/juniper-nsp
 ___
 juniper-nsp mailing list juniper-nsp@puck.nether.net 
 https://puck.nether.net/mailman/listinfo/juniper-nsp

___
juniper-nsp mailing list juniper-nsp@puck.nether.net 
https://puck.nether.net/mailman/listinfo/juniper-nsp

___
juniper-nsp mailing list juniper-nsp@puck.nether.net 
https://puck.nether.net/mailman/listinfo/juniper-nsp



La información en este correo electrónico y sus anexos es confidencial y 
privilegiada. Está dirigida exclusivamente a sus destinatarios y por lo tanto 
nadie más está autorizado a tener acceso a élla. Si Ud. no es el destinatario, 
es ilícito imprimirla, reproducirla o distribuirla. Si lo recibió por error, 
por favor avise al remitente y borre cualquier registro en sus sistemas.

CONFIDENTIALITY NOTICE: This email message and its attachments, if any, are 
intended only for the person or entity to which it is addressed and contains 
privileged information. Any use, printing, disclosure, or distribution of such 
information without the written authorization is prohibited. If you are not the 
intended recipient, please contact the sender and destroy all copies of the 
original message.

Nuestro aviso de privacidad está publicado en la página web: 
http://www.mcmtelecom.com.mx/common/politica_privacidad.htm



___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


Re: [j-nsp] M10i

2013-04-10 Thread joel jaeggli

On 4/10/13 5:45 PM, Chris Adams wrote:

Once upon a time, Correa Adolfo acor...@mcmtelecom.com.mx said:

I tought MX series were purely ethernet.

I think that was true initially, but (for example) there are MX5-80 MICs
to handle circuits from T1 up to OC192.


http://www.juniper.net/us/en/local/pdf/datasheets/1000378-en.pdf
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp