Re: [j-nsp] FXP0 down log message

2013-01-15 Thread Muruganandham M
Thanks. Its the matching PR. On Tue, Jan 15, 2013 at 1:53 PM, Tima Maryin wrote: > Hi, > > > > On 15.01.2013 9:29, Muruganandham M wrote: > >> Hi, >> >>I have set the configuration to ignore the fxp0 failure alarm. The >> alarm is ignored. However, the Log messages are filled with this

Re: [j-nsp] EX4200 VC PFE crashes

2013-01-15 Thread Stacy W. Smith
On Jan 15, 2013, at 2:57 AM, Dennis Krul | Tilaa wrote: >> Can you tell the PR number you tried to avoid initially ? > > I wasn't trying to avoid it. I just thought it wouldn't be interesting, > because it's an internal PR. But here it is: PR843475 I suspect you may have answered a different qu

Re: [j-nsp] Confusion about DSCP marking and rewrite rules

2013-01-15 Thread Alex Arseniev
Correction: - on MX960, a firewall filter can set FC in ingress and then match on it either on ingress or egress. Thanks Alex - Original Message - From: "Per Granath" To: "John Neiberger" Cc: Sent: Monday, January 14, 2013 3:33 PM Subject: Re: [j-nsp] Confusion about DSCP marking a

Re: [j-nsp] Junos spanning-tree patch cost method

2013-01-15 Thread Misha Gzirishvili
Hi there, Not sure about changing path cost method on juniper, but if you are connecting with cisco switches, you can use "spanning-tree pathcost method long" on Cisco. So, cost calculations on cisco and juniper will be identical. On Fri, Jan 11, 2013 at 12:09 PM, Michael Radits < michael.rad...@n

Re: [j-nsp] EX4200 VC PFE crashes

2013-01-15 Thread Dennis Krul | Tilaa
On Jan 15, 2013, at 6:49 AM, Tima Maryin wrote: > On 14.01.2013 23:55, Dennis Krul | Tilaa wrote: > > skip > > >> JTAC analysed our core dumps and told us this was a known issue (null >> pointer exception). It would not be resolved in 10.4 but was resolved in >> 11.2R5.5, the recommended JTA

Re: [j-nsp] Multicast flow with "Wrong incoming interface notifications" counter incrementing

2013-01-15 Thread Riccardo S
As soon as I'll experience the issue again, I'll do... Tks > From: david@orange.com > To: dim0...@hotmail.com; nkham...@juniper.net > CC: juniper-nsp@puck.nether.net > Date: Tue, 15 Jan 2013 09:19:47 +0100 > Subject: RE: [j-nsp] Multicast flow with "Wrong incoming interface > notifications"

Re: [j-nsp] Multicast flow with "Wrong incoming interface notifications" counter incrementing

2013-01-15 Thread david.roy
Could you send us the traces of "show multicast stat" 2 times separated with 10 sec. Thank you David Roy IP/MPLS Support engineer - Orange France Ph. +33 2 99 87 64 72 - Mob. +33 6 85 52 22 13 david@orange.com JNCIE-M&T/SP #703 - JNCIE-ENT #305 - JNCIP-SEC -Message d'origine--

Re: [j-nsp] Multicast flow with "Wrong incoming interface notifications" counter incrementing

2013-01-15 Thread Riccardo S
Having also a look to Juniper documentation says: Wrong incoming interface notifications = Number of times that the upstream interface was not available It doesn't sound as an RPF fail counter, isn't it ? Tks > From: nkham...@juniper.net > To: dim0...@hotmail.com > CC: juniper-nsp@puck.nether