[c-nsp] Incompatibility for send-label between Cisco andJuniper?

[Jason Koh]

Hi Alex

I have tried rib inet.3 under labeled-unicast and it looks like this time, 
the juniper router advertises anything under inet.3 only.

Before rib inet.3

ts-07> show route advertising-protocol bgp 10.169.34.2

inet.0: 23 destinations, 28 routes (23 active, 0 holddown, 0 hidden)
  Prefix                  Nexthop              MED     Lclpref    AS path
* 10.1.1.0/24             Self                                    I
* 20.20.20.1/32           Self                 20                 I
* 50.50.50.0/24           Self                                    I
@ 192.168.38.27/32        Self                 20                 I

test22#sh ip bgp sum
BGP router identifier 192.168.38.22, local AS number 2
Neighbor        V    AS MsgRcvd MsgSent   TblVer  InQ OutQ Up/Down 
State/PfxRcd
10.169.34.1     4     1   35939   35729      225    0    0 00:00:10        4
192.168.38.19   4     2   20270   20383      225    0    0 1w2d            3

After rib inet.3

ts-07> show route advertising-protocol bgp 10.169.34.2

inet.3: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
  Prefix                  Nexthop              MED     Lclpref    AS path
* 192.168.38.27/32        Self                 1                  I

test22#sh ip bgp sum
BGP router identifier 192.168.38.22, local AS number 2

Neighbor        V    AS MsgRcvd MsgSent   TblVer  InQ OutQ Up/Down 
State/PfxRcd
10.169.34.1     4     1   35954   35744      230    0    0 00:03:18        1
192.168.38.19   4     2   20276   20394      230    0    0 1w2d            3

I'm not sure if there are any workarounds with respect to family inet any. I 
don't really want multicast NRLIs there.


----- Original Message ----- 
From: "Alex" <ecralar at hotmail.com>
To: "Jason Koh" <kohtohshyr at pacific.net.sg>; <cisco-nsp at puck.nether.net>
Sent: Sunday, September 24, 2006 4:59 AM
Subject: Re: [c-nsp] Incompatibility for send-label between Cisco 
andJuniper?


> Wrong again, I should have read the doc more closely...
> "family inet unicast" and "family inet labeled-unicast" are mutually 
> exclusive.
> So it should be either "family inet any" (which also enables IPv4 
> multicast which may or may not be desirable) or "rib inet.3" under "family 
> inet labeled-unicast" as link below specifies.
> Sorry for any confision.
> Regards
> Alex
>
> ----- Original Message ----- 
> From: "Alex" <ecralar at hotmail.com>
> To: "Jason Koh" <kohtohshyr at pacific.net.sg>; <cisco-nsp at puck.nether.net>
> Sent: Saturday, September 23, 2006 9:26 PM
> Subject: Re: [c-nsp] Incompatibility for send-label between Cisco 
> andJuniper?
>
>
>> Sorry, I should have been more specific.
>> You have to have "family inet" configured with BOTH "unicast" and
>> "labeled-unicast" under [edit protocols bgp]
>> AFAIK, having there only "labeled-unicast" enables AFI/SAFI (labeled
>> BGP/NLRI with MPLS labels) 1/4 but not AFI/SAFI 1/1 (IPv4 NLRI).
>> You may also need to enable "rib inet.3" under [edit protocols bgp family
>> labeled-unicast]
>> http://www.juniper.net/techpubs/software/junos/junos76/swconfig76-routing/html/bgp-config46.html#1044675
>>
>> HTH
>> Cheers
>> Alex
>>
>> ----- Original Message ----- 
>> From: "Jason Koh" <kohtohshyr at pacific.net.sg>
>> To: "Alex" <alex.arseniev at gmail.com>; <cisco-nsp at puck.nether.net>
>> Sent: Saturday, September 23, 2006 7:45 PM
>> Subject: Re: [c-nsp] Incompatibility for send-label between Cisco and
>> Juniper?
>>
>>
>>> Hi there.
>>>
>>> Yes I do.
>>>
>>> type external;
>>> local-address 10.169.34.1;
>>> family inet {
>>>    labeled-unicast;
>>> }
>>> peer-as 2;
>>> local-as 1;
>>> neighbor 10.169.34.2;
>>>
>
>