> On Jun 25, 2015, at 3:08 AM, Sabyasachi Sengupta > <sabyasachi.sengu...@alcatel-lucent.com> wrote: > > [root@rtr-29-225-196-232 ~]# ovs-appctl bfd/show > ---- port3.4094 ---- > Forwarding: true > Detect Multiplier: 3 > Concatenated Path Down: false > TX Interval: Approx 500ms > RX Interval: Approx 500ms > Detect Time: now -1116ms > Next TX Time: now -436ms > Last TX Time: now +19ms > Last Flap Time: 2015-06-25 00:36:22.372 > ... > I understand that this will be based on what ovs-vswitchd 'thinks' as to when > the last flap occurred. Its still not the accurate information as > ovs-vswitchd might itself have restarted in between the last flap and when > the user actually reads it. This probably means that we save this info in > ovsdb and read it through a separate CLI, but probably we can keep it simple > for now?
I tend to prefer the number of seconds or milliseconds. However, if we do go with wall clock, we should at least put in the offset to GMT. Otherwise, when you get an off-line bug report, it can be difficult to know when the issue happened when trying to correlate it to other logs. --Justin _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
