Device no longer receives multicast payloads

Viewed 30

Hello,

Currently experiencing issues with multicast downlink transmission on chirpstack v3.

I configured the Lora system with RAK products and Chipstack v3 previously, and everything worked fine. The system was built as follows.

RAK3172 (Transceiver module)
│
RAK7248C
(Backend: Semtech UDP packet-forwarder)
(Chirpstack Gateway Bridge)
│
│(MQTT)
│
Server
(Chirpstack Network Server)
(Chirpstack Application Server)

[Version]
- Chirpstack Gateway Bridge : 3.12.0
- Chirpstack Network Server : 3.16.8
- Chripstack Application server : 3.17.9

I moved the server a few days ago, and I wanted the multicast functionality to work the same as before, so I set the Multicast Group configuration to the same as before on the server moved.

multicast group configuration(before).png
multicast group configuration(before)

multicast group configuration(after).png
multicast group configuration(after)

Multicast Address, Network session key and Multicast Application session key is same.

It worked fine for some time, but over time, the device was not able to receive multicast messages.

[Tracking multicast messages]

  1. Added a downlink message to the multicast group queue in the Chipstack REST API.
    chirpstack REST API.png

  2. The Chirpstack Gateway bridge has received a downlink message.
    gateway-bridge.png

  3. The udp packet-forwarder received a message from the chirpstack gateway bridge.
    udp packet-forwarder.png

  4. The RAK3172 module registered the multicast setting and waited for reception as follows.
    rak3172 lstmulc.png

  5. If the multicast reception is successful, the following receive output is displayed.
    multicast-received2.png

The module's multicast downlink reception was working fine, but then suddenly stopped, and it no longer receives multicasts. Unicast reception works. If set again the multicast configuration on the chirpstack server and join the module again, the reception resumes, but the module will not receive multicast messages shortly afterwards. If the problem is that the configuration is wrong, I think I would have failed the first time received it.

Strangely, the module is receiving multicast transmissions normally from the gateway bridge connected to the previous chirpstack server. If Multicast Address and McAppsKey and McNwksKey are the same between two servers, why can one server multicast transmissions work nomally, and the other has problems?

Any help is appreciated.

2 Answers

Please note that the before frame-counter is higher than the frame-counter after. The device will not accept (multicast) downlink with frame-counter values that have not incremented compared to the previous (valid) downlinks.

@Orne Brocaar

Followed advice, adjusted the frame counter to its previous settings, and tested multicast again, and it works fine. Thank you!