Medium Overview: We configure app-peer and odl set to listen. Add two routes to app-peer, start exabgp to see if we get two routes on it. I think what we should look at mostly are the configurations of the routes in add_routes_1.py and add_routes_2.py, as basically all the arguments are the same except the ips.
Reproduction:
- start fluorine karaf with restconf and bgp and bgp-config
- add app pear with "conf_app_peer.py"
- configure odl to accept connection on 127.0.0.2 "reconfigure_odl.py"
- add routes into app peer with "add_routes_1.py"
- now we can check ./get_ipv4_topology or write out full rib to see there is only one routes
- add second route with "add_routes_2.py" and again there is only one route the second one.
There were no errors or warnings in karaf.log
route configurations
add_routes_1.py
<ipv4-route xmlns="urn:opendaylight:params:xml:ns:yang:bgp-inet">
<prefix>1.1.1.1/32</prefix>
<path-id>0</path-id>
<attributes>
<ipv4-next-hop>
<global>199.20.160.41</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>
add_routes_2.py
<ipv4-route xmlns="urn:opendaylight:params:xml:ns:yang:bgp-inet">
<prefix>2.2.2.2/32</prefix>
<path-id>0</path-id>
<attributes>
<ipv4-next-hop>
<global>199.20.160.41</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>
