SNMP Traps: System Monitoring¶
Administrators at sysadmin level
can configure additional SNMP traps for alerts
from the System Monitoring > Configuration menu on the GUI
(menu model: data/SystemMonitoringConfig). Note: some traps
are not configurable.
Refer to the topic on System Monitoring Configuration in the Advanced Configuration Guide.
The following alerts are configured:
| Notification | Interval | Level | Configurable |
|---|---|---|---|
| Txn Queue Size | Hourly | warn | Yes |
| Failed Txn | Immediate | warn | Yes |
| data/Alert (CNF atm) | Immediate | Alert defined | No |
| Session Exceeded | Immediate | warn | Yes (via platform CLI command) |
| API Request Throttled | Immediate | warn | Yes (via platform CLI command) |
| Total DB Index Size | Daily | warn | Yes |
| Total DB Size | Daily | warn | Yes |
| Device Comms. Concurrency Limit | Immediate | warn | No |
For platform CLI commands for session limits and throttle rates, see: Performance Commands.
Transaction Queue Size¶
In accordance with the configurable threshold (default 500)
Identifying strings and example context:
DISMAN-EVENT-MIB::mteHotTrigger.0 = STRING: Transaction Queue Size Exceeded Threshold
DISMAN-EVENT-MIB::mteHotContextName.0 = STRING: Current Size: 520 Threshold: 500
Transactions: Model Operations Alerts¶
- Alerts on transactions failure
- per model (wild cards allowed, default is
data/*) - model operations (default is Import)
- per model (wild cards allowed, default is
Identifying string:
DISMAN-EVENT-MIB::mteHotTrigger.0 = STRING: Transaction Completed with Fail
Transaction trap context information (200 chars):
ID: transaction ID (same as on GUI - further transaction details available on GUI)Action: transaction message (same as on GUI)Detail: source of resource (source host for import)Hierarchy: friendly path of the resource, else the execution hierarchy of transaction
Example: Import Fail
2019-03-28 10:54:46 <UNKNOWN>
[UDP: [192.168.100.3]:31384->[192.168.100.25]:162]:
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (170158257) 19 days, 16:39:42.57
SNMPv2-MIB::snmpTrapOID.0 = OID: DISMAN-EVENT-MIB::mteTriggerFired
DISMAN-EVENT-MIB::mteHotTrigger.0 = STRING:
Transaction Completed with Fail
DISMAN-EVENT-MIB::mteHotContextName.0 = STRING:
ID: 44967,
Action: Import Call Manager,
Detail: 192.168.100.15,
Hierarchy: sys
DISMAN-EVENT-MIB::mteHotValue.0 = INTEGER: 1
SNMPv2-MIB::sysName.0 = STRING: VOSS
Change Notification Feature (CNF)¶
CNF traps are triggered when Change Notification Sync transactions
add or update instances
on the data/Alerts model.
The identifying alert string is:
DISMAN-EVENT-MIB::mteHotTrigger.0 = STRING: Device Change Notification
The data/Alerts attribute values of the model
are provided in the traps details:
alert_severity
alert_category
alert_timestamp
alert_count
alert_id
alert_message
alert_code
For example , the trap Context information (200 chars) is:
ID: Device Host business key (alert_id)Code: CNF Alert code (alert_code)Occurrences: number of occurrencesLatest Occurrence:: time stamp (alert_timestamp)
Warning and Error Alert Codes¶
The following table shows alert codes and details
| Code | Details | Resolution |
|---|---|---|
| 72051 | ERROR. Device connectivity failure | For connectivity checks, see UC Apps Reachability in the Advanced Configuration Guide and also the Platform Guide and Health Checks for Cluster Installations Guide. |
| 72052 | WARNING. Slow device connection: the roundtrip time (RTT) is greater than 400ms. | For latency checks, see UC Apps Reachability in the Advanced Configuration Guide and the Health Checks for Cluster Installations Guide. |
| 72053 | ERROR. Utilization approaching limit: if the maximum number of sessions during the interval exceeds 80% of the configured limit. | The threshold can be reached if many users are using the system at the same time, or by not logging out. For Utilization %, see Login Sessions in the Advanced Configuration Guide. |
Example: CNF alert
2019-03-28 10:54:46 <UNKNOWN>
[UDP: [192.168.100.3]:31384->[192.168.100.25]:162]:
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (170158257) 19 days, 16:39:42.57
SNMPv2-MIB::snmpTrapOID.0 = OID: DISMAN-EVENT-MIB::mteTriggerFired
DISMAN-EVENT-MIB::mteHotTrigger.0 = STRING: Device Change Notification
DISMAN-EVENT-MIB::mteHotContextName.0 = STRING:
ID: 44967,
Code: 100034,
Occurrences: 1,
Latest Occurrence: 2019-03-28 10:54:44Z
DISMAN-EVENT-MIB::mteHotValue.0 = INTEGER: 1
SNMPv2-MIB::sysName.0 = STRING: VOSS
Session Limits¶
SNMP traps are triggered when session limits are reached.
Example:
For example, the customer administrator session limit default is 10 and a trap is triggered if it is exceeded. (The default can be configured with the voss session-limits command).
Note
Global session limits do not show a Hierarchy value in the message string.
2019-03-28 10:54:46 <UNKNOWN>
[UDP: [192.168.100.3]:31384->[192.168.100.25]:162]:
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (170158257) 19 days, 16:39:42.57
SNMPv2-MIB::snmpTrapOID.0 = OID: DISMAN-EVENT-MIB::mteTriggerFired
DISMAN-EVENT-MIB::mteHotTrigger.0 = STRING: Customer Administration Session Limit Exceeded
DISMAN-EVENT-MIB::mteHotContextName.0 = STRING:
Limit: 10,
Hierarchy: sys.hcs.Varidion.GSCorp
DISMAN-EVENT-MIB::mteHotValue.0 = INTEGER: 1
SNMPv2-MIB::sysName.0 = STRING: VOSS
API Request Throttle¶
SNMP traps are triggered when throttle rates are reached.
Throttle rates are configured with:
voss throttle-rates type <administration|selfservice|user> requests <number of requests> unit <min|sec>
In other words, the SNMP trap would be triggered for request limits for any of:
- Administration
- Self-service
- User-specific
Identifying strings and Self-service as example:
DISMAN-EVENT-MIB::mteHotTrigger.0 = STRING: Selfservice Api Request Limit Exceeded
DISMAN-EVENT-MIB::mteHotContextName.0 = STRING: Rate 20/min
Total DB Index Size¶
In accordance with the configurable threshold (default 50)
Identifying strings and example:
DISMAN-EVENT-MIB::mteHotTrigger.0 = STRING: DB Index Size Exceeded Threshold
DISMAN-EVENT-MIB::mteHotContextName.0 = STRING: DB Index Size (60.00GB) exceeded threshold (50GB)
Total DB Size¶
In accordance with the configurable threshold (default 200)
Identifying strings and example:
DISMAN-EVENT-MIB::mteHotTrigger.0 = STRING: DB Size Exceeded Threshold
DISMAN-EVENT-MIB::mteHotContextName.0 = STRING: DB Size (210.30GB) exceeded threshold (200GB)
Device Communications Concurrency Limit¶
SNMP traps are sent if there is a timeout failure while connecting to a device and waiting for the concurrency limit.
Current concurrency support:
- 8 concurrent requests to Unified CM
- 8 concurrent requests to Unifity Connection
- 1 concurrent requests to HCM-F
