Only print a warning message if this is not the first message, since the first message always triggers an alert (sequence number is then compared to zero) when a trace is replayed. The impact for live flow data feeds is very limited, since this fix could only prohibit the logging of a warning if the first IPFIX message features a sequence number error.
Only print a warning message if this is not the first message, since the first message always triggers an alert (sequence number is then compared to zero) when a trace is replayed. The impact for live flow data feeds is very limited, since this fix could only prohibit the logging of a warning if the first IPFIX message features a sequence number error.