Note
This feature requires NetCloud OS version 7.25.100 or later.
The Heartbeat feature on Ericsson Cradlepoint devices is designed to allow NetCloud Manager (NCM) to poll devices for their online status. This feature provides a device's connection status in NCM and is helpful when troubleshooting connectivity issues.
The Heartbeat feature is applied and modified at the group level in NCM on a group's dashboard under the Settings tab using the Connection Pulse slider. The intervals for when NCM checks a device's online status can be adjusted from 10 seconds to 15 minutes using the slider.
An individual device's online status can be viewed on the Devices > Routers page in the Online Status (
) column.
Use the following table for reference on estimated maximum detection times and data usage based on heartbeat intervals.
Note
These numbers assume stable devices where a heartbeat isn't missed. Most of the time, even for a device going offline, these estimates will be close. But, as noted at the 10 second interval, the usage is double if you somehow always had a device recover after the second heartbeat was sent.
These data-usage values are the maximum contributed data usage from heartbeat monitoring on a device that has nothing else traversing the connection. Heartbeats are only sent if no other form of traffic was observed during the heartbeat window. Under typical conditions, data usage for heartbeat monitoring will often be much lower than shown in the table.
Heartbeat Interval | Max Detection Time | Data Usage per 24 Hours |
|---|---|---|
10 seconds | 10s+5s+5s = 20s | 3MB (up to 6MB if every miss) |
20 seconds | 20s+10s+10s = 40s | 1.5MB |
30 seconds | 30s+15s+15s = 60s | 1MB |
40 seconds | 40s+20s+20s = 80s | 752KB |
50 seconds | 50s+25s+25s = 100s | 601KB |
1 minute | 60s+30s+30s = 2m | 501KB |
2 minutes | 2m+1m+1m = 4m | 250KB |
3 minutes | 3m+1m+1m = 5m | 167KB |
4 minutes | 4m+1m+1m = 6m | 125KB |
5 minutes | 5m+1m+1m = 7m | 100KB |
10 minutes | 10m+1m+1m = 12m | 50KB |
15 minutes | 15m+1m+1m = 17m | 33KB |