{"action":"created","issue":{"url":"https://api.github.com/repos/OpenBMP/openbmp/issues/39","repository_url":"https://api.github.com/repos/OpenBMP/openbmp","labels_url":"https://api.github.com/repos/OpenBMP/openbmp/issues/39/labels{/name}","comments_url":"https://api.github.com/repos/OpenBMP/openbmp/issues/39/comments","events_url":"https://api.github.com/repos/OpenBMP/openbmp/issues/39/events","html_url":"https://github.com/OpenBMP/openbmp/issues/39","id":203217508,"number":39,"title":"Path attributes timestamp","user":{"login":"vladsker","id":24914985,"avatar_url":"https://avatars0.githubusercontent.com/u/24914985?v=4","gravatar_id":"","url":"https://api.github.com/users/vladsker","html_url":"https://github.com/vladsker","followers_url":"https://api.github.com/users/vladsker/followers","following_url":"https://api.github.com/users/vladsker/following{/other_user}","gists_url":"https://api.github.com/users/vladsker/gists{/gist_id}","starred_url":"https://api.github.com/users/vladsker/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vladsker/subscriptions","organizations_url":"https://api.github.com/users/vladsker/orgs","repos_url":"https://api.github.com/users/vladsker/repos","events_url":"https://api.github.com/users/vladsker/events{/privacy}","received_events_url":"https://api.github.com/users/vladsker/received_events","type":"User","site_admin":false},"labels":[{"id":109394868,"url":"https://api.github.com/repos/OpenBMP/openbmp/labels/question","name":"question","color":"cc317c","default":true}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":8,"created_at":"2017-01-25T20:46:33Z","updated_at":"2018-02-09T10:32:07Z","closed_at":null,"author_association":"NONE","body":"Hello, team,\r\n\r\nI found strange issue - when MySQL consumer trying to install path attributes for specific NLRI , for some of them it inserts it with wrong timestamp. All my routers are synchronized with NTP and timestamp for bgp peer is correct. Because my database partitioned by date, it confuses it.\r\n\r\nI will try to catch tcpdump of real traffic to check if this is a Junos bug or not, but I see bgp_peer timestamp is ok so I assume it might be somewhere in code.\r\n\r\nHere is the example:\r\nmysql> select * from bgp_peers where hash_id = '263f9f7c5584551428eba254d9350756';\r\n+----------------------------------+----------------------------------+---------+--------+---------------+-----------------------------------------------+---------------+---------+-------+-------------+----------------------------+-------------+--------------+---------------+---------------+------------+-----------------+-----------+-------------+------------------+----------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------+------------+--------------+-----------------+------------+\r\n| hash_id                          | router_hash_id                   | peer_rd | isIPv4 | peer_addr     | name                                          | peer_bgp_id   | peer_as | state | isL3VPNpeer | timestamp                  | isPrePolicy | geo_ip_start | local_ip      | local_bgp_id  | local_port | local_hold_time | local_asn | remote_port | remote_hold_time | sent_capabilities                                                                                                                | recv_capabilities                                                                                                                | bmp_reason | bgp_err_code | bgp_err_subcode | error_text |\r\n+----------------------------------+----------------------------------+---------+--------+---------------+-----------------------------------------------+---------------+---------+-------+-------------+----------------------------+-------------+--------------+---------------+---------------+------------+-----------------+-----------+-------------+------------------+----------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------+------------+--------------+-----------------+------------+\r\n| 263f9f7c5584551428eba254d9350756 | a21266dbc666a0409183bc3e2599197d | 0:0     |      1 | 10.252.128.22 | lo0-0.ams4-bk-intmx480-01 | 10.252.128.22 |   65502 |     1 |           0 | 2017-01-25 16:51:19.000000 |           1 | NULL         | 10.252.128.21 | 10.252.128.21 |      54539 |              90 |     65502 |         179 |               90 | MPBGP (1) : afi=1 safi=1 : Unicast IPv4, Route Refresh Old (128), Route Refresh (2), Graceful Restart (64), 4 Octet ASN (65), 71 | MPBGP (1) : afi=1 safi=1 : Unicast IPv4, Route Refresh Old (128), Route Refresh (2), Graceful Restart (64), 4 Octet ASN (65), 71 |          0 |            0 |               0 |            |\r\n+----------------------------------+----------------------------------+---------+--------+---------------+-----------------------------------------------+---------------+---------+-------+-------------+----------------------------+-------------+--------------+---------------+---------------+------------+-----------------+-----------+-------------+------------------+----------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------+------------+--------------+-----------------+------------+\r\n1 row in set (0.00 sec)\r\n\r\nAnd failed try to install path attribute:\r\n\r\nadd    484363    fc00bbf629b183276f099c1bc14a7d1e    a21266dbc666a0409183bc3e2599197d    10.193.131.111    263f9f7c5584551428eba254d9350756    10.252.128.22    65502    2017-12-17 21:08:43.000000    igp     65501 3356 14492 14492 3762    5    3762    10.252.128.22    2    100                    0    1\r\n"},"comment":{"url":"https://api.github.com/repos/OpenBMP/openbmp/issues/comments/364396944","html_url":"https://github.com/OpenBMP/openbmp/issues/39#issuecomment-364396944","issue_url":"https://api.github.com/repos/OpenBMP/openbmp/issues/39","id":364396944,"user":{"login":"vladsker","id":24914985,"avatar_url":"https://avatars0.githubusercontent.com/u/24914985?v=4","gravatar_id":"","url":"https://api.github.com/users/vladsker","html_url":"https://github.com/vladsker","followers_url":"https://api.github.com/users/vladsker/followers","following_url":"https://api.github.com/users/vladsker/following{/other_user}","gists_url":"https://api.github.com/users/vladsker/gists{/gist_id}","starred_url":"https://api.github.com/users/vladsker/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vladsker/subscriptions","organizations_url":"https://api.github.com/users/vladsker/orgs","repos_url":"https://api.github.com/users/vladsker/repos","events_url":"https://api.github.com/users/vladsker/events{/privacy}","received_events_url":"https://api.github.com/users/vladsker/received_events","type":"User","site_admin":false},"created_at":"2018-02-09T10:32:06Z","updated_at":"2018-02-09T10:32:06Z","author_association":"NONE","body":"Hi, Tim,\n\nI'll have a look and check.\n\nThanks.\n\nOn Thu, Feb 8, 2018 at 7:33 PM, Tim Evens <notifications@github.com> wrote:\n\n> Hi @vladsker <https://github.com/vladsker> , Circling back on this. We\n> have confirmed that JunOS does send the older timestamps the collector and\n> DB are loading them as they are received. All timestamps are processed and\n> stored UTC. BMP protocol defines that the timestamps are UTC and we use\n> that in the DB as well since you can change the DB per session to show the\n> timestamp in anytime zone.\n>\n> If you are still seeing that issue, can you send me a PCAP (tcpdump -s0 -w\n> bmp.pcap tcp port 5000 and host ) where you see the timestamp being correct\n> but being parsed incorrectly by the collector.\n>\n> —\n> You are receiving this because you were mentioned.\n> Reply to this email directly, view it on GitHub\n> <https://github.com/OpenBMP/openbmp/issues/39#issuecomment-364206068>, or mute\n> the thread\n> <https://github.com/notifications/unsubscribe-auth/AXwsKaB76OG93bK2932VLUsViGYpIGjxks5tSz3ogaJpZM4Lt-gn>\n> .\n>\n"}}
{"actor":{"display_login":"vladsker"}}