There is another error with the broadcast message. Currently, mds chooses an
adest (active adest for normal mode or any adest for redundancy mode) and gets
its sent message count to assign the sequence number of broadcast message.
That sequence number is only valid to the chosen adest and invalid to other
adests. Therefore, other adests will raise a packet loss when it receive that
broadcast message.
Log analysis:
* IMMD in SC-1 sends first message to IMMND in SC-2:
~~~
<142>1 2022-01-05T08:32:21.083532+07:00 SC-1 osafimmd 232 mds.log [meta
sequenceId="766"] MDTM: User Sending Data lenght=35 From svc_id = IMMD(24) to
svc_id = IMMND(25)
<143>1 2022-01-05T08:32:21.08354+07:00 SC-1 osafimmd 232 mds.log [meta
sequenceId="767"] MDTM:Sending message with Service Seqno=0, TO
Dest_Tipc_id=<0x01001002:783550957>
~~~
* IMMD in SC-1 sends first four messages to IMMND in SC-1:
~~~
<142>1 2022-01-05T08:32:21.060335+07:00 SC-1 osafimmd 232 mds.log [meta
sequenceId="708"] MDTM: User Sending Data lenght=392 From svc_id = IMMD(24) to
svc_id = IMMND(25)
<143>1 2022-01-05T08:32:21.060338+07:00 SC-1 osafimmd 232 mds.log [meta
sequenceId="709"] MDTM:Sending message with Service Seqno=0, TO
Dest_Tipc_id=<0x01001001:3762921757>
...
<142>1 2022-01-05T08:32:21.083985+07:00 SC-1 osafimmd 232 mds.log [meta
sequenceId="794"] MDTM: User Sending Data lenght=392 From svc_id = IMMD(24) to
svc_id = IMMND(25)
<143>1 2022-01-05T08:32:21.083997+07:00 SC-1 osafimmd 232 mds.log [meta
sequenceId="795"] MDTM:Sending message with Service Seqno=1, TO
Dest_Tipc_id=<0x01001001:3762921757>
...
<142>1 2022-01-05T08:32:21.086354+07:00 SC-1 osafimmd 232 mds.log [meta
sequenceId="880"] MDTM: User Sending Data lenght=392 From svc_id = IMMD(24) to
svc_id = IMMND(25)
<143>1 2022-01-05T08:32:21.086361+07:00 SC-1 osafimmd 232 mds.log [meta
sequenceId="881"] MDTM:Sending message with Service Seqno=2, TO
Dest_Tipc_id=<0x01001001:3762921757>
...
<142>1 2022-01-05T08:32:21.13546+07:00 SC-1 osafimmd 232 mds.log [meta
sequenceId="938"] MDTM: User Sending Data lenght=392 From svc_id = IMMD(24) to
svc_id = IMMND(25)
<143>1 2022-01-05T08:32:21.135468+07:00 SC-1 osafimmd 232 mds.log [meta
sequenceId="939"] MDTM:Sending message with Service Seqno=3, TO
Dest_Tipc_id=<0x01001001:3762921757>
~~~
* IMMD in SC-1 broadcasts a message to all IMMNDs. The sequence number of this
message is 4, because it's based on the number of sent message to IMMND in
SC-1.
~~~
<142>1 2022-01-05T08:32:24.25973+07:00 SC-1 osafimmd 232 mds.log [meta
sequenceId="992"] MDTM: User Sending Data lenght=35 From svc_id = IMMD(24) to
svc_id = IMMND(25)
<143>1 2022-01-05T08:32:24.259735+07:00 SC-1 osafimmd 232 mds.log [meta
sequenceId="993"] MDTM:Sending message with Service Seqno=4, TO
Dest_Tipc_id=<0x01001001:3762921757>
<143>1 2022-01-05T08:32:24.259738+07:00 SC-1 osafimmd 232 mds.log [meta
sequenceId="994"] MDTM: User Sending Multicast Data lenght=74 From svc_id =
IMMD(24) to svc_id = IMMND(25)
<142>1 2022-01-05T08:32:24.262517+07:00 SC-1 osafimmd 232 mds.log [meta
sequenceId="995"] MDTM: Successfully sent mcast message
<143>1 2022-01-05T08:32:24.262545+07:00 SC-1 osafimmd 232 mds.log [meta
sequenceId="996"] MDTM: Break while(1) prev_ver_sub_count: 0 svc_id =IMMD(24)
to_msg.bcast_buff_len: 35
<142>1 2022-01-05T08:32:24.262555+07:00 SC-1 osafimmd 232 mds.log [meta
sequenceId="997"] MDS_SND_RCV: Normal Bcast Message sent successfully from
svc_id = IMMD(24), to svc_id = IMMND(25)
~~~
* IMMND in SC-2 receives that broadcast message then notify a packet loss. The
reason is the IMMND in SC-2 received only one message from IMMD in SC-1 but
the sequence number of broadcast message is 4.
~~~
<139>1 2022-01-05T08:32:24.260379+07:00 SC-2 osafimmnd 236 mds.log [meta
sequenceId="350"] MDS_SND_RCV: msg loss detected, Src svc_id = IMMD(24), Src
vdest id= 13, Src Adest = 564117141757651, local svc_id = IMMND(25) msg num=4,
recvd cnt=1
~~~
Attachments:
-
[mds_sc1.txt](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/787c07605d/6077/attachment/mds_sc1.txt)
(696.4 kB; text/plain)
-
[mds_sc2.txt](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/787c07605d/6077/attachment/mds_sc2.txt)
(990.3 kB; text/plain)
---
** [tickets:#3304] mds: Packet loss without log**
**Status:** accepted
**Milestone:** 5.21.12
**Created:** Tue Jan 04, 2022 03:47 AM UTC by Hieu Hong Hoang
**Last Updated:** Tue Jan 04, 2022 04:50 AM UTC
**Owner:** Hieu Hong Hoang
In mds module, there is a packet loss feature. This feature provide a packet
loss callback which is called when packet loss is detected. Because it is turn
off by default, there are no callback or log when packet loss occurs.
In this ticket, the log of packet loss will be printed out by default . These
logs are helpful in many cases.
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list._______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
