[c-nsp] BGP on 6400 NRP, anyone doing it?

[Brian Feeny]

Justin,

Thanks for replying.  In your situation with eBGP multihop, I can  
understand where/why that can work, because basically the 6400 between  
the customer and the mulithop router
merely has to default route to the multihop router, and the customer  
will have next hop reachability.  But Its quite possible I may have  
transit feeding on both sides of my
connection, so I can hardly go that route.

Tell me, you migrated away from the 6400 NRP2, but what did you  
eventually go to?  I suppose just leaving ATM switches to switching and  
routing to routers is probably
the best idea.  I can't imagine a 8510 + ARM or any of the other  
options out there being much better for combined ATM/Routing at that  
price level.

Brian



On Nov 2, 2004, at 11:17 AM, Justin M. Streiner wrote:

>> Specifically I have a set of NRP's that need to take 1 iBGP feed and  
>> 1 eBGP feed,  and I have been told that
>> these do not play well with BGP, the sessions drop for unknown  
>> reasons, etc and are just unreliable when
>> it comes to thinking about running BGP on them.
>
> I was getting to a point where I would have needed to do this at my  
> previous job, however we migrated off of the 6400 before turning up  
> BGP became necessary.  With 128MB on the NRP2, taking full feeds is  
> not practical.
>
> The one instance where I needed to provide BGP to a downstream  
> customer off of one of those, I ended up doing EBGP multi-hop (yes, I  
> know....) until I ripped out the 6400 and could re-do the BGP session  
> correctly.

> jms
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
------------------------------------------------------------------------ 
------
Brian Feeny, CCIE #8036, CISSP    	e: signal at shreve.net
Network Engineer           			p: 318.213.4709
ShreveNet Inc.             			f: 318.221.6612

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : https://puck.nether.net/pipermail/cisco-nsp/attachments/20041102/561f78c0/PGP.bin