Increase expiration time (NwkKey & AppKey)

Hello guys!!!
I have a private application with devices configured in otaa. In addition, the devices are configured for lower power consumption, being inactive for a long time. I have doubts regarding the key expiration time (NwkKey & AppKey). The keys are saved on the application server or network server? To increase this time, I have to configure:

aggregation_intervals=[“MINUTE”, “HOUR”, “DAY”, “MONTH”]

Aggregated statistics storage duration.
minute_aggregation_ttl=“2h0m0s”
hour_aggregation_ttl=“48h0m0s”
day_aggregation_ttl=“2160h0m0s”
month_aggregation_ttl=“17520h0m0s”

for example to configure to retain the keys for two years, do I have to configure the variable months?

aggregation_intervals=[“MINUTE”, “HOUR”, “DAY”, “MONTH”]

Aggregated statistics storage duration.
minute_aggregation_ttl=“0h0m0s”
hour_aggregation_ttl=“0h0m0s”
day_aggregation_ttl=“0h0m0s”
month_aggregation_ttl=“17520h0m0s” (two years)

Do these variables work if the gateway loses connection to the internet, losing connection to the chirpstack server for days for example?

You’re need to configure
device_session_ttl directive in chirpstack-network-server.toml

3 Likes