ecCLOUD Terminology Follow
Term
|
Context
|
Definition |
Blocked
|
Device status
|
You can block a device from the device's main menu if you no longer wish for it to communicate with the ecCLOUD.
Once blocked, a device will no longer be allowed to connect to the XMPP server, which means it will no longer send in wireless stats, client data, etc. You will also no longer be able to change its configuration.
Note: Disabling a device automatically blocks it at the same time.
|
Configuration inheritance policy
|
Device configuration
|
A device's configuration inheritance policy determines whether or not it should inherit any common settings from the site-level configuration.
|
Critical
|
Device health
|
A device's health is considered to be critical if it has an unresolved critical-level alert.
An example of a critical-level alert is the "unreachable" alert. It may occur if a device loses power, a network cable becomes unplugged, or if firewall rules block the device from accessing the Cloud.
Critical health usually indicates that a user will have to take some sort of action in order to get the device operating normally again.
|
Device configuration status
|
Device configuration
|
A device's configuration status will tell you if the device's running configuration matches the configuration stored on the Cloud.
If the device's configuration state is anything other than Synchronized, then there is an outstanding issue with your device's configuration.
The available values for this indicator are: Suspended, Out of sync/unsynced, Running, Waiting, Synchronized, and Disabled. You can read more about these options on this page or on the Registration and Configuration article. |
Device health
|
Device health
|
The device's health can give you a general idea about the overall operational status of the device, and whether or not you are needed in order to resolve an issue.
The available values for this indicator are: Critical, Normal, Warning, and Unknown.
|
Device registration status
|
Device registration
|
The device's registration status indicates if the device has been able to successfully make an initial connection to the ecCLOUD after you've added it to a site.
Read more about the complete registration process here.
The available values for this state are: Pending, Registered, and Requires Action.
Note: If a device is blocked or disabled, it will not be allowed to complete the registration process.
|
Device status
|
Device status
|
A device's general status indicates if it's currently online (connected), or offline (disconnected from) the ecCLOUD.
Offline devices are usually accompanied by unresolved critical-level alerts.
The available values for this indicator are: Online and Offline.
Other important flags include: Blocked and Disabled.
|
Disabled |
Device configuration
|
When a device's configuration state is disabled, no received configurations from the device are processed by the Cloud, nor are new configs pushed to the device. You will not be able to view any configuration pages for the device from the Cloud. A device's configuration will only be disabled when configuration is disabled site-wide (this setting can be found from the site properties page). |
Disabled
|
Device status |
A device can be disabled from the device's main menu in the event that it's being uninstalled and permanently decommissioned. This action will block the device from contacting the cloud, however historical stats and the device's last config will still be available.
Disabled devices will not show up in the global search results, and by default, they will not show up in your site or cloud-level device lists.
Deleting a device is similar to disabling a device, but in the former case, all historical stats, system events, and configuration are removed at the time the device is deleted.
Disabled devices do not count towards any license counts.
|
Normal
|
Device health |
A device's health is considered to be normal if it has no outstanding warning or critical-level alerts.
|
Out of Sync
|
Device configuration
|
See Unsynchronized.
|
Pending Registration
|
Device registration
|
A registration state of pending registration means that you've added a device to your site, and the Cloud is waiting for the device to call in for the first time in order to fetch the credentials it will use for future communication with the Cloud.
The device should not stay in this state for more than a couple of minutes. If it does, check that it has power, network connectivity, and that a firewall isn't blocking any of the Cloud's IP addresses or ports.
|
Registered
|
Device registration
|
A registration state of registered means that your device has made initial contact with the Cloud, completed the registration process, and received the credentials that it will use in any further communication with the Cloud.
The registered state is the normal registration state of a device on the cloud.
|
Requires Action,
Re-registration |
Device registration
|
A registration state of requires action (or re-registration) means that your device was previously registered, but is attempting to register again.
The system creates a warning-level alert for this situation as it requires a user to login to their Cloud account and choose which actions they want to take – such as to allow the device to connect again, and what to do with the device’s new configuration.
|
Running
|
Device configuration
|
When a device's configuration state is running, it means the Cloud is currently running a task to push a new configuration down to the device.
You can view the status of all tasks from the maintenance tab of the device's Activity page.
|
Suspended
|
Device configuration
|
A device's configuration state can be suspended in two cases:
1) A system error occurred when the Cloud received a config from your device that it did not know how to process. When this happens, configuration is suspended for that device until the error is resolved. Sometimes you can resolve this issue by resetting your device to defaults, and choose the option to reset the Cloud config. More rarely, the support and development team will need to provide a fix for the bug.
2) If you downgrade your device, and choose to keep the previous configuration, the Cloud will automatically suspend configuration. This happens because the device's configuration may not be compatible with the older firmware. To resolve this issue, you'll need to reset to defaults.
|
Synchronized
|
Device configuration
|
A device's configuration state is considered to be synchronized if the device's running config matches the config settings stored on the Cloud.
|
Unsynchronized
|
Device configuration
|
A device's configuration state is considered to be unsynchronized if the device's running config does not match the config settings stored on the Cloud.
This error state occurs when the device reverts a configuration pushed down from the Cloud because it can’t connect to the Cloud again after the change. You can resolve this error by fixing the settings which break the device's network connectivity.
|
Unknown
|
Device status
|
If a device hasn't called into the Cloud for the first time (such as before registration is completed), its online/offline status is considered to be unknown.
|
Waiting
|
Device configuration
|
A device's configuration state is set to waiting in the event that a user has made changes to the device's configuration, but that the device is currently offline or unavailable.
It effectively means "waiting on the device to become available".
|
Warning
|
Device health
|
A device's health is considered to be in a warning state if it has an unresolved warning-level alert.
An example of a resolvable warning-level alert is the re-registration alert, which requires that a user login and take action in order to allow the device to re-register.
An example of informational (non-resolvable) warning-level alert is the reboot alert.
|
Comments
0 comments
Article is closed for comments.