Re: [j-nsp] ISG dropping BGP Keepalives

2009-05-06 Thread Jason Dearborn
After a few more rounds with JTAC, it appears the problem lies with the core not properly switching BGP packets destined for it's own loopback address.Troubleshooting with Force 10 has indicated a potentially new FTOS bug. Thanks for all the replies, both on and off-list. Jason Dearborn 2009

[j-nsp] JUNOS upgrade validation sucks lately

2009-05-06 Thread Jeff S Wheeler
On Wed, 2009-05-06 at 11:33 -0400, Eric Van Tol wrote: > Understood. Since this is the case, I'd suggest that Juniper fix their JUNOS > Hardware Validation tool: > > http://tools.juniper.net/microcode/ > > They're getting into Cisco IOS Software Advisor territory by allowing invalid > hardware

Re: [j-nsp] 9.3 and M20 FPC

2009-05-06 Thread Larry Stites
Eric, We just supplied an M20 FPC-E (JUNIPER Enhanced Flexible PIC Concentrator) to a customer in Arizona for $3500. He is using it to operate a P-4CHDS3-QPP which requires the enhanced FPC. Since 9.3 requires same please consider us as supplier in your search for a spare FPC-E. We can ship withi

Re: [j-nsp] 9.3 and M20 FPC

2009-05-06 Thread Eric Van Tol
> -Original Message- > From: Stacy W. Smith [mailto:st...@acm.org] > Sent: Wednesday, May 06, 2009 10:39 AM > To: Eric Van Tol > Cc: juniper-nsp > Subject: Re: [j-nsp] 9.3 and M20 FPC > > From the 9.3 release notes: > > "On M20 routers running JUNOS Release 9.3 and later, nonenhanced FPC

Re: [j-nsp] 9.3 and M20 FPC

2009-05-06 Thread Timo Mohre
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 As stated in the reply from Pekka Savola to the threat "FPC-Offline on M20 after Upgrade JunOS 8.5 to 9.3" > > The very, very old FPC's (prior to E-FPC's) no longer work in 9.3, > as stated in release notes. This may or may not be related. > HTH. /

Re: [j-nsp] how to populate a forwarding routing-instance

2009-05-06 Thread Bit Gossip
there is no interface in PIPPO routing-instance; therefore the ping fails even if I don't specify the source address: rc2# run ping 1.1.1.2 routing-instance PIPPO PING 1.1.1.2 (1.1.1.2): 56 data bytes ping: sendto: Can't assign requested address The idea was to source the bgp session in routing

Re: [j-nsp] 9.3 and M20 FPC

2009-05-06 Thread Stacy W. Smith
From the 9.3 release notes: "On M20 routers running JUNOS Release 9.3 and later, nonenhanced FPCs do not come online because of memory limitations. These FPCs appear as FPC in the Description column of the output from the show chassis hardware command. As announced in Technical Bulletin PSN-2

Re: [j-nsp] 9.3 and M20 FPC

2009-05-06 Thread Eric Van Tol
> -Original Message- > From: Timo Mohre [mailto:t...@tiscali.net] > Sent: Wednesday, May 06, 2009 10:27 AM > To: Eric Van Tol > Cc: juniper-nsp > Subject: Re: [j-nsp] 9.3 and M20 FPC > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > As stated in the reply from Pekka Savola to the th

[j-nsp] 9.3 and M20 FPC

2009-05-06 Thread Eric Van Tol
Hi all, Is anyone out there running 9.3 with an M20 FPC (not FPC-E). I have a lab box that I've upgraded to 9.3R2.8 and the FPC won't come up. The only PIC in this FPC is a P-4CHDS3 PIC. The FPC basically goes from "Present" state to "Offline" within a few minutes of booting: May 5 15:07:06

Re: [j-nsp] how to populate a forwarding routing-instance

2009-05-06 Thread martin.mogensen
Does the ping work if you don't specify the source address? This way the ping can use a source address that is native to the routing-instance, ie a loopback interface declared in the routing-instance. run ping 1.1.1.2 routing-instance PIPPO Cheers Martin -Message d'origine- De : Bit G

Re: [j-nsp] how to populate a forwarding routing-instance

2009-05-06 Thread Bit Gossip
Hi Martin, indeed with rib-group I can import in the routing-instance PIPPO the connected and local routes, but still BGP doesn't come up because I think the process can not bind to the address of the local interface which is still part of a different routing-instance, the default one. For the

Re: [j-nsp] how to populate a forwarding routing-instance

2009-05-06 Thread martin.mogensen
Indeed, the interfaces routes from inet.0 are unknown to your new routing-instance which is as expected. You can use rib-groups (routing table groups) to import the connected interface routes into your new routing-instance. I haven't tested the exact config below, but the concept is as follow

Re: [j-nsp] how to populate a forwarding routing-instance

2009-05-06 Thread Bit Gossip
Martin, as a 'virtual-router' the protocol configuration commits correctly but still I have a little problem: to setup the BGP session, I need the connecting interface in the routing-instance PIPPO as well as in the global routing-instance for normal forwarding and this is not accepted :-( any

Re: [j-nsp] how to populate a forwarding routing-instance

2009-05-06 Thread martin.mogensen
Hello Try "instance-type virtual-router" instead of "instance-type forwarding" to be able to support routing protocols - this way the commit should work. "instance-type virtual-router" also support filter-based forwarding. Cheers Martin -Message d'origine- De : juniper-nsp-boun...@pu

[j-nsp] how to populate a forwarding routing-instance

2009-05-06 Thread Bit Gossip
Experts, I want to configure FilterBasedForwarding and so I need a routing-instance of type forwarding. I have no issue to populate the routing-instance with static routes; but in reality I would like to use bgp to populate it; and this doesn't commit. Is it possible to use bgp for that? If not,