These are chat archives for Exa-Networks/exabgp

24th
Aug 2018
steiler
@steiler
Aug 24 2018 15:55
hi
stumbled across this exabgp output
{ "exabgp": "4.0.1", "time": 1535125123.0646856, "host" : "SRC", "pid" : 1, "ppid" : 0, "counter": 30, "type": "update", "neighbor": { "address": { "local": "172.24.100.80", "peer": "10.9.9.1" }, "asn": { "local": 65000, "peer": 65000 } , "direction": "receive", "message": { "update": { "attribute": { "origin": "igp", "local-preference": 100, "bgp-ls": { "node-flags": {"O": 0, "T": 0, "E": 0, "B": 0}, "node-name": "Core3", "area-id": "490004", "local-te-router-id": "10.9.9.3", "local-te-router-id": "10.0.0.10", "local-te-router-id": "10.0.0.13", "local-te-router-id": "10.1.1.17", "local-te-router-id": "10.1.1.21", "sr-capability-flags": {"I": 1, "V": 0, "RSV": 0}, "sids": [[65536, 900000]] } }, "announce": { "bgp-ls bgp-ls": { "10.9.9.1": [ { "ls-nlri-type": 1, "l3-routing-topology": 0, "protocol-id": 2, "node-descriptors": { "autonomous-system": 65000, "router-id": "100000000003" }, "nexthop": "10.9.9.1" } ] } } } } } }
as you can see, when looking closely is that the "local-te-router-id" is carried in that json message multiple times on the same hirarchy level ... overwrites all but the last entry when parsing ...
prior to opening an issue I wanted to make sure that this is even allowed ... carrying multiple (local-te-)router-ids
steiler
@steiler
Aug 24 2018 16:01
no clue which rfc to look at ... since this is BGP-LS exported ISIS-Segement Routing