We have a problem with processing IPFX packets from Mikrotik routers because Mikrotik IPFIX dont containt
systemInitTimeMilliseconds. Mikrotik IPFIX containt only flowStartSysUpTime and flowEndSysUpTime Information Elements to
absolute times without knowing the systemInitTimeMilliseconds.
The absence of the value of systemInitTimeMilliseconds in the IPFIX packet makes it difficult for us to count
bandwidths.
Our problem is also described as one of the possible in the RFC 5153 https://tools.ietf.org/html/rfc5153
> 4.7. Devices without an Absolute Clock
>
> Exporting just relative times in a device without an absolute clock
> is often not sufficient. For instance, observed traffic could be
> retained in the device's cache for some time before being exported
> (e.g., if the Exporter runs once per minute), or stuck in an Inter
> Process Communication (IPC) queue, or stuck in the export stack, or
> delayed in the network between the Exporter and Collector.
>
> For these reasons, it can be difficult for the Collecting Process to
> convert the relative times exported using the flowStartSysUpTime and
> flowEndSysUpTime Information Elements to absolute times with any sort
> of accuracy without knowing the systemInitTimeMilliseconds.
> Therefore, the sending of the flowStartSysUpTime and flowEndSysUpTime
> Information Elements without also sending the
> systemInitTimeMilliseconds Information Element is not recommended.
We really hope for your help in adding the systemInitTimeMilliseconds to your IPFIX implementation
We opened the ticket almost a month ago, but the answer from Mikrotik did not receive.