Hi Paolo,

Wondering if you can share some light on a issue i'm seeing with pmacct
bgp_daemon.

lab@lab:~$ /opt/pmacctd/bin/pmacct -V
pmacct, pmacct client 1.6.1 (20161001-00+c5)
 '--prefix=/opt/pmacctd' '--enable-kafka' '--enable-jansson'


I have a vpnv4 ibgp session with on jnp box. All the routes received have
the same bgp_nexthop of : 10.91.0.148.

in the logs
{"seq": 4391, "log_type": "update", "timestamp": "2017-02-17
13:57:02.149110", "peer_ip_src": "10.91.0.30", "event_type": "log",
"ip_prefix": "10.101.6.16/29", "bgp_nexthop": "10.91.0.148", "as_path": "",
"ecomms": "RT:29009:3801", "origin": 0, "local_pref": 100, "rd":
"0:29009:3801"}

{"seq": 4392, "log_type": "update", "timestamp": "2017-02-17
13:57:02.149110", "peer_ip_src": "10.91.0.30", "event_type": "log",
"ip_prefix": "10.101.6.8/29", "bgp_nexthop": "10.91.0.148", "as_path": "",
"ecomms": "RT:29009:3801", "origin": 0, "local_pref": 100, "rd":
"0:29009:3801"}

while if i do a packet capture i can see the correct next-hop in the bgp
update.

also correct on the router:

cpetrescu@rtr> show route advertising-protocol bgp 10.91.92.198
10.101.6.16/29

bgp.l3vpn.0: 1958 destinations, 2992 routes (1958 active, 0 holddown, 0
hidden)
  Prefix                  Nexthop              MED     Lclpref    AS path
  29009:3801:10.101.6.16/29
*                         10.91.0.203                  100        I

What is strange is i have infact a RD 10.91.0.148:3801 with next hop
10.91.0.148 advertised to the pmacct but i can't find any record of that in
the log.

This happens every time , even after the bgp session is cleared.

Regards,
Catalin
_______________________________________________
pmacct-discussion mailing list
http://www.pmacct.net/#mailinglists

Reply via email to