#2898 imm: syslog number of recent fevs messages when immnd down

[Vu Minh Nguyen]

We has encountered "OUT OF ORDER" error sometimes, and it is not easy to find out which message has been lost.

It would help if imm is able to syslog a number of recent fevs (e.g. 05) when detecting immnd down for any reason, showing recent sequence numbers and message ids.

[Danh Vo]

The format of the output:
1. <sequence_id>[msg_id_string -> additional_info_of_events] (in case we have additional info)
2. <sequence_id>[msg_id_string -> (none)] (in case we don't have additional info)

Below is example for 5 last FEVS events which will be printed in syslog when IMMND down:

2018-07-27 13:46:45.188 PL-4 osafimmnd[181]: NO Recent fevs: <2126>[IMMND_EVT_D2ND_IMPLSET_RSP -> impl_id:27]
2018-07-27 13:46:45.188 PL-4 osafimmnd[181]: NO Recent fevs: <2127>[IMMND_EVT_D2ND_DISCARD_IMPL -> impl_id:27]
2018-07-27 13:46:45.189 PL-4 osafimmnd[181]: NO Recent fevs: <2123>[IMMND_EVT_A2ND_OI_CL_IMPL_SET -> Set impl 26 to SaAmfSIDependency]
2018-07-27 13:46:45.189 PL-4 osafimmnd[181]: NO Recent fevs: <2124>[IMMND_EVT_A2ND_OI_CL_IMPL_SET -> Set impl 26 to SaAmfSIRankedSU]
2018-07-27 13:46:45.189 PL-4 osafimmnd[181]: NO Recent fevs: <2125>[IMMND_EVT_A2ND_OI_CL_IMPL_SET -> Set impl 26 to OpenSafAmfConfig]

[Danh Vo]

commit ab9b12e55f1c396e76583d71704e6b09167441ee (HEAD -> develop, origin/develop)
Author: Danh Vo danh.c.vo@dektech.com.au
Date: Thu Aug 2 11:08:58 2018 +0700

imm: syslog recent fevs evts when immnd down [#2898]

An enhancement for IMM to print out 5 last FEVS events into syslog
when there is any IMMND down for any reason.