[j-nsp] NSR, multicast, and VRFs?

[Dave Diller]

>
On May 5, 2008, at 1:14 PM, Pekka Savola wrote:

>> Now, 9.1 says:
>>
>> Border Gateway Protocol (BGP), for unicast IPv4 and IPv6 address
>> families only. If you configure any other address family, the BGP
>> session will not come up on the backup router.
>
> This text is probably inaccurate.  At least previously if you have  
> MP-BGP w/ multicast enabled, when doing NSR manually (mastership  
> switch) the BGP sessions would reset similarly as if NSR wasn't  
> enabled at all (which is something different from "will not come up").

Yes, that's precisely the behavior I ran into with 9.0R2.10 when  
testing in the lab, sessions were just resetting on me when I flipped  
REs.

Tracing the BGP/NSR interactions, the backup RE shows this in the logs:

May  5 10:57:29.661446 bgp_standby_check_nsr_support: xxx.xxx.xxx.xx  
(Internal AS xxxxx) NSR not supported for all negotiated adress  
families (bgp_nlri 0x0007)

but I wasn't clear on WHICH famil(y was|ies were) the problem since I  
have both on that peer:

    NLRI for this session: inet-unicast inet-multicast inet-vpn-unicast

and the docs didn't help clarify what was and was not supported ;-)    
Thanks for the clarification that multicast will definitely cause this  
behavior.

----

On May 5, 2008, at 1:48 PM, Stefan Fouant wrote:


> IMHO, I would read that to say that L3 VPN VRFs are still not
> supported as you wouldn't be able to configure the inet-vpn address
> family.

Hmm, now THAT's an interesting point I'd not considered.  Even inet- 
vpn is unicast, so that's what I was keying in on, but I can certainly  
"unicast IPv4 and IPv6 address families" meaning "family inet" and  
"family inet6" only.

PROBABLY the case since 9.1 only claims L2 and VPLS support for NSR...  
but disappointing.


So, in other words, I've got TWO reasons I can't use NSR... and  
thereby ISSU.  Boo.

-dd