BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Pacific Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02000
Folks,
Our 18.07 release F0 (API freeze) date has arrived... We won't merge risky
patches, or patches which involve API changes until the master branch reopens
in a week: on or about Monday July 16th.
Committers, please take notice.
Thanks... Dave
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive al
Hi Shwetha,
I found that dump message has something strange.
I configured my system at "trace-tsp 2 (microseconds)". But dump was followings.
[0] ttl 0xfc node id 0x4 ts 0x4c5470ee
[1] ttl 0xfd node id 0x3 ts 0x4c4cd843
[2] ttl 0xfe node id 0x1 ts 0x4c562e52
0x4c5470ee (hex) = 128060
IOAM trace timestamp is 4 bytes. So it always returns the least significant 4
bytes of milli, micro or nanoseconds specified by trace-tsp.
We have not yet implemented the long format timestamps yet.
For performance, the IOAM trace timestamp is populated using cpu time stamp
counter and initia
Hi Neha,
You should provide the PID of the process that wants to receive the callbacks
for the want apis not the PID of the vpp.
Look at the API documentation /src/vpp /stats/stats.api. Something like
pid=os.getpid() instead of the VPP PID in the code snippet below will fix it.
Also the callbac
Hi Saurabh,
Glad to see you’re interested in LISP!
As the error lower suggests, you first need to enable the lisp code. You can
achieve this by doing: “one enable". Note that although “lisp enable” would
also have the same result, going forward we plan to deprecate the “lisp” apis
in favor of
