Re: [j-nsp] How many pppoe sessions E320 can handle?

2009-03-02 Thread Arda Balkanay
Hi, pppoe session limit is 96000 (16000 per LM4 module) L2TP session limit is 48000 (16000 per service module or 8000 per LM4 with IO) On Tue, Mar 3, 2009 at 9:35 AM, Robert Kern wrote: > Hi folks, > > do you know max number of pppoe sessions E320 can handle? > > Regards, > > Robert >

[j-nsp] How many pppoe sessions E320 can handle?

2009-03-02 Thread Robert Kern
Hi folks, do you know max number of pppoe sessions E320 can handle? Regards, Robert ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] ISIS metric of redistributed directly connected routes

2009-03-02 Thread Richard A Steenbergen
On Mon, Mar 02, 2009 at 09:29:22AM +0100, Hannes Gredler wrote: > hi richard, > > guessing the "correct" export metric of a direct route > is a bit of philosophical question ;-) - let me explain: > > since JUNOS does not know which end(point) of the subnet you are > interested in, it advertises t

Re: [j-nsp] Interfaces updown log

2009-03-02 Thread Faizal Rachman
OK Guys Your helps really appreciated :) Thanks Faizal On Mon, Mar 2, 2009 at 9:38 PM, Mustafa Golam - wrote: > >> file updown { >>any info; >>match "LINK_DOWN|LINK_UP"; >> [...] >> } > > That's the coolest feature ;) > //Mustafa > > -- > -- > *´¨) > ¸.•´¸.•*´¨) ¸.•*¨) > (¸.•´ (¸.•` *Mu

Re: [j-nsp] Interfaces updown log

2009-03-02 Thread david.roy
The SNMP_TRAP_LINK_UP has a severity to INFO and the SNMP_TRAP_LINK_DOWN to WARNING. So, to view SNMP_TRAP_LINK_UP and SNMP_TRAP_LINK_DOWN, you need to allow these severity in the syslog configuration : edit system syslog { host x.x.x.x { any info; [...] } file messages { any info; [

Re: [j-nsp] Interfaces updown log

2009-03-02 Thread Mustafa Golam -
On Mon, Mar 2, 2009 at 4:58 PM, Mustafa Golam - wrote: > On Mon, Mar 2, 2009 at 4:45 PM, Faizal Rachman wrote: > >> Anyone know how to enable interfaces updown status on syslog message? >> Iam using Junos 8.5SR and didn't find any interfaces updown log. >> >> H think the following link would be

Re: [j-nsp] Interfaces updown log

2009-03-02 Thread Mustafa Golam -
On Mon, Mar 2, 2009 at 4:45 PM, Faizal Rachman wrote: > Anyone know how to enable interfaces updown status on syslog message? > Iam using Junos 8.5SR and didn't find any interfaces updown log. > > Ref to: http://www.juniper.net/techpubs/software/junos/junos85/syslog-messages85/download/snmp.pdf

[j-nsp] Interfaces updown log

2009-03-02 Thread Faizal Rachman
Anyone know how to enable interfaces updown status on syslog message? Iam using Junos 8.5SR and didn't find any interfaces updown log. Thanks, Faizal ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juni

[j-nsp] E3 Multilink Bundle

2009-03-02 Thread Aamir Saleem
Hi All, I have configured E3 Multilink bundle for 2 E3 interface between M7i routers. Configuration seems to me ok and P2P IPs over lsq interface are working fine. Traffic is load-balnace over the two E3. But the maximum throughput of bundle interface is not exceeding more the 30Mbps bandwidth.Can

Re: [j-nsp] network engineering

2009-03-02 Thread Matthias Gelbhardt
Hi! To clarify my problem, I have found another example: www.snom.de Trace from our core: HOST: lyta.local Loss% Snt Last Avg Best Wrst StDev 1. 192.168.6.1 0.0%100.3 0.4 0.3 0.6 0.1 2. ge-00.cr1.ems.dlrz.net0.0%10

[j-nsp] no. of routing-instance on M10i

2009-03-02 Thread Amjad Ul Hasnain Qasmi
Hi, Can you guys tell me the maximum no. of routing-instances that can be configured on M10i. Regards, AHQ ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] ISIS metric of redistributed directly connected routes

2009-03-02 Thread Hannes Gredler
hi richard, guessing the "correct" export metric of a direct route is a bit of philosophical question ;-) - let me explain: since JUNOS does not know which end(point) of the subnet you are interested in, it advertises the worst case, which is the cost to reach the far-end, the cost of "crossing"