Hi,
Has anyone eve ran into the issue of the date reporting for an established BGP
peer being reset to 00:00:00 when it rolls over to a new day using peer status?
It appears that when the session rolls into the next day, the established time
gets set to only a date and it drops the HH:MM:SS
/route-mon/peer_status | grep last_change
"last_change": "2019-08-27T00:00:00",
"last_change": "2019-08-27T00:00:00",
"last_change": "2019-08-20T00:00:00",
"last_change": "2019-08-20T00:00:00",
"last_change": "2019-08-27T00:00:00",
"last_change": "2019-08-27T00:00:00",
Also, the time being reported for the route duration is just a date.
tbird.ctl show route
BIRD 1.6.3 ready.
172.16.1.0/24 dev bbforward [static_bgp 2019-08-20] * (200)
172.16.2.0/24 dev bbforward [static_bgp 2019-08-20] * (200)
172.16.3.0/24 dev bbforward [static_bgp 2019-08-20] * (200)
172.16.4.0/24 dev bbforward [static_bgp 2019-08-20] * (200)
172.16.5.0/24 dev bbforward [static_bgp 2019-08-20] * (200)
172.16.6.0/24 dev bbforward [static_bgp 2019-08-20] * (200)
172.16.7.0/24 dev bbforward [static_bgp 2019-08-20] * (200)
172.16.8.0/24 dev bbforward [static_bgp 2019-08-20] * (200)
It would be nice if I could get more granularity out of the commands.
Any ideas?
Thanks
--
Platform Operations Engineer
Fort Lauderdale, FL USA
[id:9A68E9F7-1C69-4FEA-A38A-3B3754E954E2]
The information contained in this electronic mail transmission and its
attachments may be privileged and confidential and protected from disclosure.
If the reader of this message is not the intended recipient (or an individual
responsible for delivery of the message to such person), you are strictly
prohibited from copying, disseminating or distributing this communication. If
you have received this communication in error, please notify the sender
immediately and destroy all electronic, paper or other versions.
