GW Border Offline and GW Relay Online

Viewed 10

Hello,

I am currently experiencing an issue with GW Border and GW Relay gateways in ChirpStack v4, and I would like to know if anyone has already encountered this behavior.

Context

  • ChirpStack v4 running on a VM
  • Server, VM, and gateways are time-synchronized (NTP OK)
  • Architecture using one GW Border and one GW Relay

Observed issue

  • The GW Border appears as Offline in ChirpStack. However, the Last Seen timestamp looks correct and recent
    GW Border.jpg
  • The GW Relay appears as Online. But the Last Seen timestamp shows a delay of about 3 minutes compared to the current time
    GW Relay.jpg

Checks already performed

  • Time synchronization verified on server / VM / gateways
  • Network connectivity OK
  • Gateways are still transmitting data

Has anyone experienced an Offline status while Last Seen remains correct?

Is there any known behavior in ChirpStack v4 related to GW Relay / Border and Last Seen timestamps?

Are there specific parameters to check first (keepalive, stats interval, backend, MQTT, etc.)?

Thanks in advance for any feedback.

1 Answers
  • The border gateway online / offline is based on the last stats message sent by the gateway. In the default config, this is every 30 seconds. If the last sent stats message is > 30 seconds in the past (+ some margin), then the gateway is considered offline.
  • The relay gateway online / offline is based on the last heartbeat event sent by the relay. By default this is every 15 minutes. If the relay does not report within that interval (+ some margin), then the relay is considered offline.