SNMP Traps
CloudControl uses the following SNMP traps:
Protected Host
| Type | Description | Status | Status Code |
|---|---|---|---|
| Protected Host Monitoring |
Warning when the host is unreachable, Healthy when CloudControl can communicate with the host again. Note: This trap requires that protected host monitoring is enabled using the CLI command |
Healthy | 1 |
|
Warning |
2 |
Networking
| Type | Description | Status | Status Code |
|---|---|---|---|
| Router Monitoring | Warning when the router is unreachable, Healthy when CloudControl can communicate with the router again. | Healthy | 1 |
|
Warning |
2 |
||
| SMTP Server Monitoring |
Warning when the email server is unreachable, Healthy when CloudControl can communicate with the email server again. |
Healthy | 1 |
|
Warning |
2 |
||
|
NTP Monitoring |
Warning when the NTP server is unreachable, Healthy when CloudControl can communicate with the NTP server again. |
Healthy | 1 |
|
Warning |
2 |
High Availability (HA)
| Type | Description | Status | Status Code |
|---|---|---|---|
| CloudControl HA Host
|
Critical when secondary HA node is offline, Healthy when the node is back online and successfully synced. |
Healthy | 1 |
| Critical | 3 |
Authentication
| Type | Description | Status | Status Code |
|---|---|---|---|
|
RSA Server Connection Monitoring |
Warning when the RSA server is unreachable, Healthy when CloudControl can communicate with the RSA server again. |
Healthy | 1 |
|
Critical |
3 |
Appliance Health
| Type | Description | Status | Status Code |
|---|---|---|---|
|
CPU Monitoring |
Trigger points are based on the 15-minute running load-average divided by the number of the vCPUs in the appliance. Warning threshold is reached at a 1.0 to 1 ratio, Critical is reached at a 5.0 to 1 ratio, Healthy when the CPU utilization returns to a lower ratio. |
Healthy |
1 |
|
Warning |
2 |
||
|
Critical |
3 |
||
|
Memory Monitoring |
Trigger points are based on the swap usage and RAM usage. For swap, Warning threshold is reached when 20% of swap space is used, Critical when 70% swap space is used, Healthy when swap has returned to less than 20%. For RAM, Warning threshold is reached when 95% of all RAM is used, Healthy when memory use has returned to less than 95%. If RAM is at the Warning threshold, and swap is at Critical, you will receive a Critical message for both RAM and swap. |
Healthy |
1 |
|
Warning |
2 |
||
|
Critical |
3 |
||
|
Disk Monitoring |
Warning at 85% disk usage, Critical at 95%, Healthy when database disk usage has returned to less than 85%. |
Healthy |
1 |
|
Warning |
2 |
||
|
Critical |
3 |
||
|
Scheduled Jobs Monitoring |
Warning when a scheduled job has failed, Healthy when the job has recovered. |
Healthy |
1 |
|
Warning |
2 |
||
|
Backup and Restore Monitoring |
Warning when the backup is outdated and was created after the last RPV event, Healthy when the backup is now up to date. |
Healthy |
1 |
|
Warning |
2 |
||
|
License (Support and Maintenance Expiry) Monitoring |
Warning at 10 days before the license expires, Critical at 3 days before, Healthy when the license is updated. Note: This trap requires that the License Monitor SNMP Trap scheduled event is enabled. |
Healthy | 1 |
|
Warning |
2 |
||
|
Critical |
3 |
||
| License (CPU and Host Capacity) Monitoring |
Warning when 75% of the licensed sockets are in use, Critical when 90% are in use, Healthy when the license is updated. Note: This trap requires that the License Monitor SNMP Trap scheduled event is enabled. |
Healthy | 1 |
|
Warning |
2 |
||
|
Critical |
3 |
|
Follow us: |
