Incorrect uptime of BGP neighbours #31

Closed
opened 2020-03-10 23:41:27 +08:00 by stkonst · 10 comments
stkonst commented 2020-03-10 23:41:27 +08:00 (Migrated from github.com)

Hi team,

In our Alice deployment we see in the BGP sessions Established section an uptime of 292 years, both for the IPv4 version and the IPv6 version. You can observe it clearly in the following screenshot.
screenshot-alice2

Can you provide a fix for this issue? The birdwatcher is attached to a Bird v2 instance and we run the latest version both for Alice and birdwatcher.

Thanks
Stavros | AMS-IX NOC

Hi team, In our Alice deployment we see in the BGP sessions Established section an uptime of 292 years, both for the IPv4 version and the IPv6 version. You can observe it clearly in the following screenshot. ![screenshot-alice2](https://user-images.githubusercontent.com/17049385/76330133-c29c0f00-62ed-11ea-800b-ea828cf6b39a.png) Can you provide a fix for this issue? The birdwatcher is attached to a Bird v2 instance and we run the latest version both for Alice and birdwatcher. Thanks Stavros | AMS-IX NOC
bodsink commented 2020-03-28 21:57:26 +08:00 (Migrated from github.com)

same issue with bird version 2

Thanks
Indri | BatamIX

same issue with bird version 2 Thanks Indri | BatamIX
momorientes commented 2020-04-07 18:44:17 +08:00 (Migrated from github.com)

Same here with birdv2

Thanks
Moritz | Stuttgart-IX

Same here with birdv2 Thanks Moritz | Stuttgart-IX
momorientes commented 2020-04-24 23:50:32 +08:00 (Migrated from github.com)

Hi,

this can be fixed in the alice config file, simply add this:

servertime = 2006-01-02T15:04:05.999999999Z07:00
servertime_short = 2006-01-02 15:04:05
servertime_ext = 2006-01-02 15:04:05

to the respective [source.rsfoo.birdwatcher] statement.

@mhannig: I guess you can resolve this issue however I'd suggest improving the documentation for the config file. I'd submit a PR but this was more or less trial and error

Hi, this can be fixed in the alice config file, simply add this: ``` servertime = 2006-01-02T15:04:05.999999999Z07:00 servertime_short = 2006-01-02 15:04:05 servertime_ext = 2006-01-02 15:04:05 ``` to the respective [source.rsfoo.birdwatcher] statement. @mhannig: I guess you can resolve this issue however I'd suggest improving the documentation for the config file. I'd submit a PR but this was more or less trial and error
annikahannig commented 2020-05-04 16:24:32 +08:00 (Migrated from github.com)

I think we can add this to the default config

I think we can add this to the default config
annikahannig commented 2020-05-04 16:25:16 +08:00 (Migrated from github.com)

btw is this bird2 specific?

btw is this bird2 specific?
annikahannig commented 2020-05-04 16:53:17 +08:00 (Migrated from github.com)

Or maybe we can add to the documentation some guidelines like
if you are using XY in birdZ, then use
servertime = ...
....

otherwise:
servertime = ...

Or maybe we can add to the documentation some guidelines like if you are using XY in birdZ, then use servertime = ... .... otherwise: servertime = ...
momorientes commented 2020-05-04 17:07:03 +08:00 (Migrated from github.com)

Hi Annika,

I have no bird1 installation I could test this with, all the insights I can give are that I'm using bird2 and the following time format settings:

timeformat base         iso long;
timeformat log          iso long;
timeformat protocol     iso long;
timeformat route        iso long;

I think adding this to the documentation as bird2 specific sounds good to me.

Hi Annika, I have no bird1 installation I could test this with, all the insights I can give are that I'm using bird2 and the following time format settings: ``` timeformat base iso long; timeformat log iso long; timeformat protocol iso long; timeformat route iso long; ``` I think adding this to the documentation as bird2 specific sounds good to me.
stkonst commented 2020-05-07 21:45:55 +08:00 (Migrated from github.com)

Hi again and thank's for the reply. I modified my alice.conf file and now I have this

[source.rsfoo.birdwatcher]
# Optional: Examples for time format
# Please see https://golang.org/pkg/time/#pkg-constants for an
# explanation on how time parsing in go works.
servertime = 2006-01-02T15:04:05.999999999Z07:00
servertime_short = 2006-01-02 15:04:05
servertime_ext = 2006-01-02 15:04:05

I restarted the Alice process but the problem remains. Do I miss anything?

Thank's again.

Hi again and thank's for the reply. I modified my alice.conf file and now I have this ``` [source.rsfoo.birdwatcher] # Optional: Examples for time format # Please see https://golang.org/pkg/time/#pkg-constants for an # explanation on how time parsing in go works. servertime = 2006-01-02T15:04:05.999999999Z07:00 servertime_short = 2006-01-02 15:04:05 servertime_ext = 2006-01-02 15:04:05 ``` I restarted the Alice process but the problem remains. Do I miss anything? Thank's again.
stkonst commented 2020-05-08 19:05:23 +08:00 (Migrated from github.com)

Sorry, just realized my mistake and now I figured out where shall I place the workaround in the config. I did it and now I get the correct uptime being displayed.

Sorry, just realized my mistake and now I figured out where shall I place the workaround in the config. I did it and now I get the correct uptime being displayed.
SalehCoder commented 2023-08-10 19:17:38 +08:00 (Migrated from github.com)

Hi,

this can be fixed in the alice config file, simply add this:

servertime = 2006-01-02T15:04:05.999999999Z07:00
servertime_short = 2006-01-02 15:04:05
servertime_ext = 2006-01-02 15:04:05

to the respective [source.rsfoo.birdwatcher] statement.

@mhannig: I guess you can resolve this issue however I'd suggest improving the documentation for the config file. I'd submit a PR but this was more or less trial and error

That fix worked for Bird 1.6.8.

> Hi, > > this can be fixed in the alice config file, simply add this: > > ``` > servertime = 2006-01-02T15:04:05.999999999Z07:00 > servertime_short = 2006-01-02 15:04:05 > servertime_ext = 2006-01-02 15:04:05 > ``` > > to the respective [source.rsfoo.birdwatcher] statement. > > @mhannig: I guess you can resolve this issue however I'd suggest improving the documentation for the config file. I'd submit a PR but this was more or less trial and error That fix worked for Bird 1.6.8.
Sign in to join this conversation.
No description provided.