Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Debug and troubleshoot your multicast groups and FUOTA tasks using network analyzer

The wireless resources that you can monitor using network analyzer include LoRaWAN devices, LoRaWAN gateways, and multicast groups. You can also use network analyzer to debug and troubleshoot any issues with your FUOTA task. You can also monitor and track messages related to setup, data transmission, and status query when the FUOTA task is in progress.

To monitor your FUOTA task, if the task contains multicast groups, you must add both the multicast group and the devices in the group to your network analyzer configuration. You must also activate frame info and multicast frame info. This allows you to track the unicast and multicast messages that are exchanged with the multicast group and the devices while the FUOTA task is in progress.

To monitor multicast groups, you can add them to your network analyzer configuration. You can use multicast frame info to troubleshoot multicast downlink messages that are sent to these groups. For troubleshooting devices that are attempting to join a group where unicast communication is used, you must also include these devices in the network analyzer configuration. To monitor only the unicast communication with the devices in the group, activate the frame info for your wireless devices. This approach ensures comprehensive monitoring and diagnostics for both multicast groups and devices that are joining the group.

The following sections describe how to debug and troubleshoot your multicast groups and FUOTA tasks using network analyzer.

Debug FUOTA tasks that only contain devices

You can use network analyzer to debug a FUOTA task that only has LoRaWAN devices added to the task. For information about adding devices to a FUOTA task, see Add devices and multicast groups to a FUOTA task and schedule a FUOTA session. To debug the FUOTA task, perform the following steps:

In the applicationCommandType column of the trace message information, you'll receive unicast downlink messages related to data transmission and fragmentation setup.

You can also see the applicationCommandType and other detailed messages in the JSON log message under WirelessMetadata > ApplicationInfo.

Debug FUOTA tasks with multicast groups

You can use network analyzer to debug a FUOTA task that has multicast groups and LoRaWAN devices added to the group. For information about adding devices to a FUOTA task, see Add devices and multicast groups to a FUOTA task and schedule a FUOTA session. To debug the FUOTA task, perform the following steps:

You can then view the trace messages and debug them using the applicationCommandType column of the trace message table. You can also use the details in the JSON log message as described in Debug FUOTA tasks that only contain devices.

Debug devices that are attempting to join a multicast group

You can use network analyzer to debug devices that are attempting to join a multicast group. For information about adding devices to a multicast group, see Create multicast groups and add devices to the group. To debug the multicast group, perform the following steps:

Debug a multicast group session

You can use network analyzer to debug a multicast group session. For more information, see Schedule a downlink message to send to devices in your multicast group. To debug a multicast group session, perform the following steps:

In the trace message table, the MulticastAddr will be displayed in the DevAddr column. In the JSON log message, you can view detailed information such as the MulticastGroupId under WirelessMetadata > ApplicationInfo.