Hi,

Thanks for theses response but I'm always blocked...I need again
help...sorry about that.

> > The logging to the MySQL db is working correctly but a lot of
> > information are missing :
> > DEBUG ( default/mysql ): INSERT INTO `acct_bgp` (stamp_updated,
> > stamp_inserted, as_src, as_dst, as_path, local_pref, med, peer_as_src,
> > peer_as_dst, peer_ip_src, peer_ip_dst, agent_id, comms, packets, bytes)
> > VALUES (FROM_UNIXTIME(1256724001), FROM_UNIXTIME(1256723400), 34383, 0,
> > '', 100, 0, 0, 0, '192.168.5.1', 'WAN_IP', 0, '', 2, 509)
> > 
> > As you can see, in my configuration below, i've set the bgp
> > update-source IP the same than sflow agent-ip. Is it enough to able to
> > match informations between sflow & bgp ? How can I see than the match is
> > working ? 
> 
> The correlation between sFlow and BGP is working as, as it can be seen
> from the query above src_as, local_pref and peer_ip_dst (BGP next-hop)
> are resolved fine. All of that comes from BGP. As what is missing above
> is roughly as_dst, peer_as_dst, as_path (and there are no communities
> attached): is it not possible this is something redistributed in BGP
> (ie. a static or a connected route or a route injected from some other
> protocol)?


The 2 transit peers are connected with BGP4.
The BGP backbone routers are connected to  "level 2" routers in OSPF but
I don't see the point ?
(peer_ip_dst is correctly set to primary OSPF)
 
> 
> Two troubleshooting steps that helped recently (thanks to Zenon from
> GRNET for his cooperation at this propo) are:
> 
> * temporarily set to true 'bgp_daemon_msglog' to have a debug of all
>   the BGP routes (and their attributes) being exported from the peer(s)

The information seems perfect, sample :
INFO ( default/core/BGP ): [Id: ROUTER-ID] u Prefix: '208.74.16.0/21'
Path: '174 3549 32952' Comms: '174:21000 174:22013' EComms: '' LP: '100'
MED: '82011' Nexthop: 'WAN_IP_ROUTER_TRANSIT_AS_174'

> 
> * temporarily increase resolution of the aggregation, ie. add src_host
>   and/or dst_host, so that specific issues can be pin-pointed.

When I add src_host :
AG|TAG2|CLASS|SRC_MAC|DST_MAC|VLAN|SRC_AS|DST_AS|BGP_COMMS|AS_PATH|PREF|
MED|PEER_SRC_AS|PEER_DST_AS PEER_SRC_IP|PEER_DST_IP|SRC_IP|DST_IP|
SRC_PORT|DST_PORT|TCP_FLAGS|PROTOCOL|TOS|PACKETS|FLOWS|BYTES
0           0           unknown           00:00:00:00:00:00
00:00:00:00:00:00  0      0           0
^$                       100    0      0           0
192.168.5.1      PEER_DST_IP     X.Y.Z.N                      0
0         0          ip          0      1           0           40

and dst_host : 
0           0           unknown           00:00:00:00:00:00
00:00:00:00:00:00  0      3215        0
^$                       100    0      0           0
192.168.5.1      PEER_DST_IP     SRC_IP    DST_IP   0         0
0          ip          0      1           0           200


So, do you have more information about the link (the key) between the
BGP information and the sflow ?

Thanks a lot,

-- 
Maxence Rousseau
mrouss...@ate.info
ATE - Avenir Télématique
http://www.ate.info
+33(0)3.28.800.300


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

Reply via email to