[honeycomb-dev] issues with honeycomb connection in odl+bgp configuration


Giles Heron
 

So yes, it looks like the RIB is configured for IPv4 unicast and IPv4 labelled unicast only but the user has attempted to configure a linkstate peer.

I guess if the HC RIB only supports IPV4 unicast and IPv4 labelled unicast then we ought to prevent configuration of other AFI/SAFIs.   Maybe HC should have a deviation against the BGP YANG model to enforce that?

Giles


De : <honeycomb-dev-bounces@...> au nom de "Jan Srnicek -X (jsrnicek - PANTHEON TECHNOLOGIES at Cisco)" <jsrnicek@...>
Date : lundi 18 septembre 2017 à 09:54
À : cbouette <cecile.bouette@...>, "Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco)" <mgradzki@...>, "honeycomb-dev@..." <honeycomb-dev@...>
Cc : "hc2vpp@..." <hc2vpp@...>
Objet : [honeycomb-dev] FW: [hc2vpp] issues with honeycomb connection in odl+bgp configuration
 
Hi cecile
 
Our bgp expect is currently Out of office(will be back 25.09), i will try to streer you from general hc perspective(im not very familiar with bgp),
 
Something that caught my eye :
 
The very first log says
 
2017-09-14 14:19:08.632 UTC [qtp1871196571-133] INFO  o.o.p.bgp.rib.impl.config.BgpPeer - RIB instance does not list BgpTableTypeImpl [getAfi()=class org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.bgp.linkstate.rev150210.LinkstateAddressFamily, getSafi()=class org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.bgp.linkstate.rev150210.LinkstateSubsequentAddressFamily] in its local tables. Incoming data will be dropped.
 
I’ve briefly looked at code that produces this warning, and it seems to be related to your configuration of table types.
 
Our global rib instance is configured just for ipv4-unicast and ipv4-labeledunicast , so im not shure if you configuration will work or is valid in our case, but again, Marek should be able to answer your questions once he’s back.
 
If you have any other questions, i will do my best J
 
anner11
 
Jan Srnicek
Engineer - Software
Tel:
Cisco Systems, Inc.



Slovakia
cisco.com
 
Think before you print.
This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.
Please click here for Company Registration Information.
 
_______________________________________________
honeycomb-dev mailing list
honeycomb-dev@...
https://lists.fd.io/mailman/listinfo/honeycomb-dev


Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES@Cisco) <mgradzki@...>
 

Hi,

 

sorry for joining late. I don’t know any reason why HC should not support linkstate.

This is just oversight, partially caused by unfinished https://jira.fd.io/browse/HONEYCOMB-363.

Currently to properly configure BGP extensions in HC one needs to add code in several places.

Linkstate is not properly configured at least in one of them (e.g. BgpRIBProvider.java@83).

 

The HONEYCOMB-363 was planned for 17.10 and is in review,

But to be implemented properly, also requires HONEYCOMB-359.

After quick look I think they require a bit more work,

so I will workaround them to make your usecase work.

 

Regards,

Marek

 

From: Giles Heron [mailto:giles.heron@...]
Sent: 18 września 2017 16:24
To: Jan Srnicek -X (jsrnicek - PANTHEON TECHNOLOGIES at Cisco) <jsrnicek@...>; cecile.bouette@...; Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco) <mgradzki@...>; honeycomb-dev <honeycomb-dev@...>
Cc: hc2vpp@...
Subject: Fwd: [honeycomb-dev] [hc2vpp] issues with honeycomb connection in odl+bgp configuration

 

So yes, it looks like the RIB is configured for IPv4 unicast and IPv4 labelled unicast only but the user has attempted to configure a linkstate peer.

 

I guess if the HC RIB only supports IPV4 unicast and IPv4 labelled unicast then we ought to prevent configuration of other AFI/SAFIs.   Maybe HC should have a deviation against the BGP YANG model to enforce that?

 

Giles

 



De : <honeycomb-dev-bounces@...> au nom de "Jan Srnicek -X (jsrnicek - PANTHEON TECHNOLOGIES at Cisco)" <jsrnicek@...>
Date : lundi 18 septembre 2017 à 09:54
À : cbouette <cecile.bouette@...>, "Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco)" <mgradzki@...>, "honeycomb-dev@..." <honeycomb-dev@...>
Cc : "hc2vpp@..." <hc2vpp@...>
Objet : [honeycomb-dev] FW: [hc2vpp] issues with honeycomb connection in odl+bgp configuration

 

Hi cecile

 

Our bgp expect is currently Out of office(will be back 25.09), i will try to streer you from general hc perspective(im not very familiar with bgp),

 

Something that caught my eye :

 

The very first log says

 

2017-09-14 14:19:08.632 UTC [qtp1871196571-133] INFO  o.o.p.bgp.rib.impl.config.BgpPeer - RIB instance does not list BgpTableTypeImpl [getAfi()=class org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.bgp.linkstate.rev150210.LinkstateAddressFamily, getSafi()=class org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.bgp.linkstate.rev150210.LinkstateSubsequentAddressFamily] in its local tables. Incoming data will be dropped.

 

I’ve briefly looked at code that produces this warning, and it seems to be related to your configuration of table types.

 

Our global rib instance is configured just for ipv4-unicast and ipv4-labeledunicast , so im not shure if you configuration will work or is valid in our case, but again, Marek should be able to answer your questions once he’s back.

 

If you have any other questions, i will do my best J

 

anner11

 

Jan Srnicek

Engineer - Software

Tel:

Cisco Systems, Inc.




Slovakia
cisco.com

 

Think before you print.

This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.

Please click here for Company Registration Information.

 

_______________________________________________
honeycomb-dev mailing list
honeycomb-dev@...
https://lists.fd.io/mailman/listinfo/honeycomb-dev

 


Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES@Cisco) <mgradzki@...>
 

Cécile,

 

please try:

 

https://gerrit.fd.io/r/#/c/8536/

 

In case you need program routes with linkstate extension via HC application-peer,

also ApplicationRibWriterFactory needs to be updated.

 

Regards,

Marek

 

From: Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco)
Sent: 26 września 2017 08:19
To: 'Giles Heron' <giles.heron@...>; Jan Srnicek -X (jsrnicek - PANTHEON TECHNOLOGIES at Cisco) <jsrnicek@...>; cecile.bouette@...; honeycomb-dev <honeycomb-dev@...>
Cc: hc2vpp@...
Subject: RE: [honeycomb-dev] [hc2vpp] issues with honeycomb connection in odl+bgp configuration

 

Hi,

 

sorry for joining late. I don’t know any reason why HC should not support linkstate.

This is just oversight, partially caused by unfinished https://jira.fd.io/browse/HONEYCOMB-363.

Currently to properly configure BGP extensions in HC one needs to add code in several places.

Linkstate is not properly configured at least in one of them (e.g. BgpRIBProvider.java@83).

 

The HONEYCOMB-363 was planned for 17.10 and is in review,

But to be implemented properly, also requires HONEYCOMB-359.

After quick look I think they require a bit more work,

so I will workaround them to make your usecase work.

 

Regards,

Marek

 

From: Giles Heron [mailto:giles.heron@...]
Sent: 18 września 2017 16:24
To: Jan Srnicek -X (jsrnicek - PANTHEON TECHNOLOGIES at Cisco) <jsrnicek@...>; cecile.bouette@...; Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco) <mgradzki@...>; honeycomb-dev <honeycomb-dev@...>
Cc: hc2vpp@...
Subject: Fwd: [honeycomb-dev] [hc2vpp] issues with honeycomb connection in odl+bgp configuration

 

So yes, it looks like the RIB is configured for IPv4 unicast and IPv4 labelled unicast only but the user has attempted to configure a linkstate peer.

 

I guess if the HC RIB only supports IPV4 unicast and IPv4 labelled unicast then we ought to prevent configuration of other AFI/SAFIs.   Maybe HC should have a deviation against the BGP YANG model to enforce that?

 

Giles

 

 

De : <honeycomb-dev-bounces@...> au nom de "Jan Srnicek -X (jsrnicek - PANTHEON TECHNOLOGIES at Cisco)" <jsrnicek@...>
Date : lundi 18 septembre 2017 à 09:54
À : cbouette <cecile.bouette@...>, "Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco)" <mgradzki@...>, "honeycomb-dev@..." <honeycomb-dev@...>
Cc : "hc2vpp@..." <hc2vpp@...>
Objet : [honeycomb-dev] FW: [hc2vpp] issues with honeycomb connection in odl+bgp configuration

 

Hi cecile

 

Our bgp expect is currently Out of office(will be back 25.09), i will try to streer you from general hc perspective(im not very familiar with bgp),

 

Something that caught my eye :

 

The very first log says

 

2017-09-14 14:19:08.632 UTC [qtp1871196571-133] INFO  o.o.p.bgp.rib.impl.config.BgpPeer - RIB instance does not list BgpTableTypeImpl [getAfi()=class org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.bgp.linkstate.rev150210.LinkstateAddressFamily, getSafi()=class org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.bgp.linkstate.rev150210.LinkstateSubsequentAddressFamily] in its local tables. Incoming data will be dropped.

 

I’ve briefly looked at code that produces this warning, and it seems to be related to your configuration of table types.

 

Our global rib instance is configured just for ipv4-unicast and ipv4-labeledunicast , so im not shure if you configuration will work or is valid in our case, but again, Marek should be able to answer your questions once he’s back.

 

If you have any other questions, i will do my best J

 

anner11

 

Jan Srnicek

Engineer - Software

Tel:

Cisco Systems, Inc.




Slovakia
cisco.com

 

Think before you print.

This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.

Please click here for Company Registration Information.

 

_______________________________________________
honeycomb-dev mailing list
honeycomb-dev@...
https://lists.fd.io/mailman/listinfo/honeycomb-dev