[BGPCEP-597] C: update message not complete Created: 08/Nov/16  Updated: 03/Mar/19  Resolved: 21/Nov/16

Status: Resolved
Project: bgpcep
Component/s: BGP
Affects Version/s: Bugzilla Migration
Fix Version/s: Bugzilla Migration

Type: Bug
Reporter: Peter Gubka Assignee: Claudio David Gasparini
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

External issue ID: 7122

 Description   

odl: distribution-karaf-0.6.0-20161108.142535-1786.zip

a route is configured via application peer and it should be advertised to connected bgp peer

route:
/restconf/config/bgp-rib:application-rib/172.17.0.4/tables/bgp-types:ipv4-address-family/bgp-types:unicast-subsequent-address-family/bgp-inet:ipv4-routes/
<ipv4-route xmlns="urn:opendaylight:params:xml:ns:yang:bgp-inet">
<prefix>1.1.1.1/32</prefix>
<path-id>1</path-id>
<attributes>
<ipv4-next-hop>
<global>100.100.100.1</global>
</ipv4-next-hop>
<as-path/>
<multi-exit-disc>
<med>0</med>
</multi-exit-disc>
<local-pref>
<pref>100</pref>
</local-pref>
<originator-id>
<originator>41.41.41.41</originator>
</originator-id>
<origin>
<value>igp</value>
</origin>
<cluster-id>
<cluster>40.40.40.40</cluster>
</cluster-id>
</attributes>
</ipv4-route>

after connecting exabgp, an update is received:
Tue, 08 Nov 2016 15:32:39 | DE | 92 | wire | session 1 outgoing 172.17.0.5 / 172.17.0.4 RECEIVED (139) 0000 0034 4001 0100 4002 0080 0404 0000 0000 4005 0400 0001 2C80 0904 2929 2929 800A 0428 2828 2880 0E0E 0001 0104 6464 6403 0020 0101 0101
Tue, 08 Nov 2016 15:32:39 | INFO | 92 | message | Peer 172.17.0.4 ASN 64496 << UPDATE
Tue, 08 Nov 2016 15:32:39 | INFO | 92 | parser | parsing flag 40 type 01 (origin) len 01 payload (2) 00
Tue, 08 Nov 2016 15:32:39 | INFO | 92 | parser | parsing flag 40 type 02 (as-path) len 00 (0)
Tue, 08 Nov 2016 15:32:39 | INFO | 92 | parser | parsing flag 80 type 04 (med) len 04 payload (9) 0000 0000
Tue, 08 Nov 2016 15:32:39 | INFO | 92 | parser | parsing flag 40 type 05 (local-preference) len 04 payload (9) 0000 012C
Tue, 08 Nov 2016 15:32:39 | INFO | 92 | parser | parsing flag 80 type 09 (originator-id) len 04 payload (9) 2929 2929
Tue, 08 Nov 2016 15:32:39 | INFO | 92 | parser | parsing flag 80 type 0a (cluster-list) len 04 payload (9) 2828 2828
Tue, 08 Nov 2016 15:32:39 | INFO | 92 | parser | parsing flag 80 type 0e (mp-reach-nlri) len 0e payload (34) 0001 0104 6464 6403 0020 0101 0101
Tue, 08 Nov 2016 15:32:39 | INFO | 92 | parser | parsing 1/1 nlri payload (12) 2001 0101 01

but in boron a different message is sent from odl:
Sun, 06 Nov 2016 22:00:19 | DE | 24318 | wire | session 1 outgoing 10.29.12.233 / 10.29.13.61 RECEIVED (149) 0000 0038 4001 0100 4002 0080 0404 0000 0000 4005 0400 0001 2C80 0904 2929 2929 800A 0428 2828 2880 0E12 0001 0104 6464 6403 0000 0000 0320 0101 0101
Sun, 06 Nov 2016 22:00:19 | INFO | 24318 | message | Peer 10.29.13.61 ASN 64496 << UPDATE
Sun, 06 Nov 2016 22:00:19 | INFO | 24318 | parser | parsing flag 40 type 01 (origin) len 01 payload (2) 00
Sun, 06 Nov 2016 22:00:19 | INFO | 24318 | parser | parsing flag 40 type 02 (as-path) len 00 (0)
Sun, 06 Nov 2016 22:00:19 | INFO | 24318 | parser | parsing flag 80 type 04 (med) len 04 payload (9) 0000 0000
Sun, 06 Nov 2016 22:00:19 | INFO | 24318 | parser | parsing flag 40 type 05 (local-preference) len 04 payload (9) 0000 012C
Sun, 06 Nov 2016 22:00:19 | INFO | 24318 | parser | parsing flag 80 type 09 (originator-id) len 04 payload (9) 2929 2929
Sun, 06 Nov 2016 22:00:19 | INFO | 24318 | parser | parsing flag 80 type 0a (cluster-list) len 04 payload (9) 2828 2828
Sun, 06 Nov 2016 22:00:19 | INFO | 24318 | parser | parsing flag 80 type 0e (mp-reach-nlri) len 12 payload (44) 0001 0104 6464 6403 0000 0000 0320 0101 0101
Sun, 06 Nov 2016 22:00:19 | INFO | 24318 | parser | parsing 1/1 nlri payload (22) 0000 0003 2001 0101 01

 Comments   
Comment by Peter Gubka [ 08/Nov/16 ]

(In reply to Peter Gubka from comment #0)
> odl: distribution-karaf-0.6.0-20161108.142535-1786.zip
>
> a route is configured via application peer and it should be advertised to
> connected bgp peer
>
> route:
> /restconf/config/bgp-rib:application-rib/172.17.0.4/tables/bgp-types:ipv4-
> address-family/bgp-types:unicast-subsequent-address-family/bgp-inet:ipv4-
> routes/
> <ipv4-route xmlns="urn:opendaylight:params:xml:ns:yang:bgp-inet">
> <prefix>1.1.1.1/32</prefix>
> <path-id>1</path-id>
> <attributes>
> <ipv4-next-hop>
> <global>100.100.100.1</global>
> </ipv4-next-hop>
> <as-path/>
> <multi-exit-disc>
> <med>0</med>
> </multi-exit-disc>
> <local-pref>
> <pref>100</pref>
> </local-pref>
> <originator-id>
> <originator>41.41.41.41</originator>
> </originator-id>
> <origin>
> <value>igp</value>
> </origin>
> <cluster-id>
> <cluster>40.40.40.40</cluster>
> </cluster-id>
> </attributes>
> </ipv4-route>
>
>
> after connecting exabgp, an update is received:
> Tue, 08 Nov 2016 15:32:39 | DE | 92 | wire | session 1
> outgoing 172.17.0.5 / 172.17.0.4 RECEIVED (139) 0000 0034 4001
> 0100 4002 0080 0404 0000 0000 4005 0400 0001 2C80 0904 2929 2929 800A 0428
> 2828 2880 0E0E 0001 0104 6464 6403 0020 0101 0101
> Tue, 08 Nov 2016 15:32:39 | INFO | 92 | message | Peer
> 172.17.0.4 ASN 64496 << UPDATE
> Tue, 08 Nov 2016 15:32:39 | INFO | 92 | parser | parsing flag
> 40 type 01 (origin) len 01 payload (2) 00
> Tue, 08 Nov 2016 15:32:39 | INFO | 92 | parser | parsing flag
> 40 type 02 (as-path) len 00 (0)
> Tue, 08 Nov 2016 15:32:39 | INFO | 92 | parser | parsing flag
> 80 type 04 (med) len 04 payload (9) 0000 0000
> Tue, 08 Nov 2016 15:32:39 | INFO | 92 | parser | parsing flag
> 40 type 05 (local-preference) len 04 payload (9) 0000 012C
> Tue, 08 Nov 2016 15:32:39 | INFO | 92 | parser | parsing flag
> 80 type 09 (originator-id) len 04 payload (9) 2929 2929
> Tue, 08 Nov 2016 15:32:39 | INFO | 92 | parser | parsing flag
> 80 type 0a (cluster-list) len 04 payload (9) 2828 2828
> Tue, 08 Nov 2016 15:32:39 | INFO | 92 | parser | parsing flag
> 80 type 0e (mp-reach-nlri) len 0e payload (34) 0001 0104 6464 6403 0020
> 0101 0101
> Tue, 08 Nov 2016 15:32:39 | INFO | 92 | parser | parsing 1/1
> nlri payload (12) 2001 0101 01
>
>
> but in boron a different message is sent from odl:
> Sun, 06 Nov 2016 22:00:19 | DE | 24318 | wire | session 1
> outgoing 10.29.12.233 / 10.29.13.61 RECEIVED (149) 0000 0038 4001
> 0100 4002 0080 0404 0000 0000 4005 0400 0001 2C80 0904 2929 2929 800A 0428
> 2828 2880 0E12 0001 0104 6464 6403 0000 0000 0320 0101 0101
> Sun, 06 Nov 2016 22:00:19 | INFO | 24318 | message | Peer
> 10.29.13.61 ASN 64496 << UPDATE
> Sun, 06 Nov 2016 22:00:19 | INFO | 24318 | parser | parsing flag
> 40 type 01 (origin) len 01 payload (2) 00
> Sun, 06 Nov 2016 22:00:19 | INFO | 24318 | parser | parsing flag
> 40 type 02 (as-path) len 00 (0)
> Sun, 06 Nov 2016 22:00:19 | INFO | 24318 | parser | parsing flag
> 80 type 04 (med) len 04 payload (9) 0000 0000
> Sun, 06 Nov 2016 22:00:19 | INFO | 24318 | parser | parsing flag
> 40 type 05 (local-preference) len 04 payload (9) 0000 012C
> Sun, 06 Nov 2016 22:00:19 | INFO | 24318 | parser | parsing flag
> 80 type 09 (originator-id) len 04 payload (9) 2929 2929
> Sun, 06 Nov 2016 22:00:19 | INFO | 24318 | parser | parsing flag
> 80 type 0a (cluster-list) len 04 payload (9) 2828 2828
> Sun, 06 Nov 2016 22:00:19 | INFO | 24318 | parser | parsing flag
> 80 type 0e (mp-reach-nlri) len 12 payload (44) 0001 0104 6464 6403 0000
> 0000 0320 0101 0101
> Sun, 06 Nov 2016 22:00:19 | INFO | 24318 | parser | parsing 1/1
> nlri payload (22) 0000 0003 2001 0101 01

Adding app peer and bgp peer configs
app peer:
<neighbor xmlns="urn:opendaylight:params:xml:ns:yang:bgp:openconfig-extensions">
<neighbor-address>172.17.0.4</neighbor-address>
<config>
<peer-group>application-peers</peer-group>
</config>
</neighbor>

bgp peer:
<neighbor xmlns="urn:opendaylight:params:xml:ns:yang:bgp:openconfig-extensions">
<neighbor-address>172.17.0.5</neighbor-address>
<route-reflector>
<config>
<route-reflector-client>false</route-reflector-client>
</config>
</route-reflector>
<timers>
<config>
<hold-time>180</hold-time>
</config>
</timers>
<transport>
<config>
<remote-port>17900</remote-port>
<passive-mode>true</passive-mode>
</config>
</transport>
<config>
<peer-type>INTERNAL</peer-type>
</config>
<afi-safis>
<afi-safi>
<afi-safi-name xmlns:x="http://openconfig.net/yang/bgp-types">x:IPV4-UNICAST</afi-safi-name>
<receive>true</receive>
<send-max>0</send-max>
</afi-safi>
<afi-safi>
<afi-safi-name xmlns:x="http://openconfig.net/yang/bgp-types">x:L3VPN-IPV4-UNICAST</afi-safi-name>
</afi-safi>
<afi-safi>
<afi-safi-name xmlns:x="http://openconfig.net/yang/bgp-types">x:L2VPN-EVPN</afi-safi-name>
</afi-safi>
</afi-safis>
</neighbor>

Comment by Claudio David Gasparini [ 09/Nov/16 ]

Could you attach the add path configuration used for global(rib) please,
thank you.

Comment by Peter Gubka [ 21/Nov/16 ]

problem on the test side

Generated at Wed Feb 07 19:13:33 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.