Reporting on the Resource Monitoring Function
The SBC generates statistics on the monitored resources for debugging purposes on the live systems. The SBC also generates statistics on the Resource Monitoring Function. Mechanism from which you can get this information includes ACLI commands, Alarms, Log Files and SNMP. When deployed in high availability mode, statistics are generated by this function separately on the active and standby nodes.
ACLI Commands
The SBC provides ACLI command You can execute on the runtime system to see what resources are active and what type of action the system has taken for specific thresholds. You can observe these statistics and status reports on the resource monitoring function using the commands below.
- show resourcemonitor
action-information—Shows the precautionary actions count per
resource.
TRUNK# show resourcemonitor action-information Accepted 13:22:17-173 Action Stats TASK-NAME MINOR MAJOR CRITICAL ALARM&TRAP DECREMENT_HEALTHSCORE ClearAction SRTP_D tPpmEntry 0 0 0 0 0 0 HMU tPpmEntry 0 0 0 0 0 0 2833 tPpmEntry 0 0 0 0 0 0 COMMAND_QUEUE sipd01 0 0 0 0 0 0 COMMAND_QUEUE mbcd01 0 0 0 0 0 0 SRTP_SESSIONS mbcd 0 0 0 0 0 0 SRTP_E tPpmEntry 0 0 0 0 0 0 COMMAND_QUEUE atcpd01 0 0 0 0 0 0 QOS tPpmEntry 0 0 0 0 0 0 TCP/TLS atcpd 0 0 0 0 0 0 NAT_FLOWS tPpmEntry 0 0 0 0 0 0 HEAP heap 0 0 0 0 0 0 TRUNK#
- show resourcemonitor
registration-status—Shows registration status per
resource.
TRUNK# show resourcemonitor registration-status Accepted 13:22:43-199 Registration Status TASK-NAME STATUS SRTP_E tPpmEntry INACTIVE QOS tPpmEntry INACTIVE 2833 tPpmEntry INACTIVE NAT_FLOWS tPpmEntry INACTIVE COMMAND_QUEUE sipd01 INACTIVE HMU tPpmEntry INACTIVE COMMAND_QUEUE mbcd01 INACTIVE SRTP_SESSIONS mbcd INACTIVE COMMAND_QUEUE atcpd01 INACTIVE TCP/TLS atcpd INACTIVE SRTP_D tPpmEntry INACTIVE HEAP heap INACTIVE TRUNK#
- show resourcemonitor
resource-registrations—Shows registration count of resource monitor
function
resources.
TRUNK# show resourcemonitor resource-registrations Accepted 13:23:05-120 Registration stats ---- Lifetime ---- Recent Total PerMax Register 0 12 6 Register 4xx 0 12 6 Register 200OK 0 0 0 TRUNK#
- show resourcemonitor resource-reports—Shows
the report count for resources in the resource monitor
function.
TRUNK# show resourcemonitor resource-reports Accepted 13:23:27-143 Usage-Percent stats ---- Lifetime ---- Resource TASK-NAME Recent Total PerMax SRTP_D tPpmEntry 0 0 0 HMU tPpmEntry 0 0 0 2833 tPpmEntry 0 0 0 COMMAND_QUEUE sipd01 0 0 0 COMMAND_QUEUE mbcd01 0 0 0 SRTP_SESSIONS mbcd 0 0 0 SRTP_E tPpmEntry 0 0 0 COMMAND_QUEUE atcpd01 0 0 0 QOS tPpmEntry 0 0 0 TCP/TLS atcpd 0 0 0 NAT_FLOWS tPpmEntry 0 0 0 HEAP heap 0 0 0 REPORT REJECTION 0 0 0 TRUNK#
- reset resourcemonitor—Resets all the statistics produces by the commands above.
The system also provides manual commands to clear out the actions the system has taken for the specified or all resource types.
clear-resourcemonitor < "resource-type" > | < all >
This command syntax example clears any action performed on heap memory, based on every crossed threshold.
ORACLE#clear-resourcemonitor HEAP
You can also use the following to view information the system generates within the context of this feature:
- The “log.tResourceMonitor” log file captures log messages generated by the Resource Monitoring Module.
- DEBUG and MINOR level logs in the “log.heap” logfile .
- Whenever required, the SBC
issues the applicable SNMP traps and alarms. The applicable objects include:
- apRmResourcesGroupTrap
- apRmResourcesGroupClearTrap
- RESOURCE_MONITOR_ALARM
Logs and Alarms
The SBC includes a log file named log.tPpmEntry that presents PPM resource logs generated by the resource monitor client. There are also some DEBUG and MINOR level log message related to this resource monitoring feature in the “log.sipd”, “log.mbcd” and “log.atcpd” logfile.
There are no separate alarms used only for this feature. Instead, the SBC uses the alarms and traps previously developed for resource issues. Each resource uses its own ALARM ID and processName.
The example alarm below show ID 131100 informing you that the HEAP process, configured with a threshold of 80% is breached.
HYDERABAD# display-alarms
2 alarms to show
ID Task Severity First Occurred Last Occurred
131100 3524 4 2023-12-04 06:33:59 2023-12-04 06:34:29
Count Description
2 Resource monitoring module raising alarm - Resource task id = 3524, threshold = 80%, current value = 82%,processName = heap
Note:
Whenever the system raises an alarm within the context of this feature, it simultaneously issues an equivalent trap.New alarms include:
Resource Monitoring Alarms Table:
AlarmName | Alarm-ID | Description | causes | Action | severity | TrapName |
MEM_UTIL_OVER_THRESHOLD | 131100 | Resource monitoring module raising alarm - Resource task id = TASK_ID, threshold = 80%, current value = 82%, processName = theap , resourceName = HEAP | High memory usage | Ensure calls are managed in a way that resource usage stays within the specified threshold |
minor major critical
|
apRmResourcesGroupTrap |
COMMAND_QUEUE_OVER_THRESHOLD | 131426 | Resource monitoring module raising alarm - Resource task id = TASK_ID, threshold = 80%, current value = 82%,processName = sipd1 , resourceName = COMMAND_QUEUE | High command Queue usage | Ensure calls are managed in a way that resource usage stays within the specified threshold |
minor major critical
|
apRmResourcesGroupTrap |
NAT_OVER_THRESHOLD | 131427 | Resource monitoring module raising alarm - Resource task id = TASK_ID, threshold = 80%, current value = 82%,processName = tPpmEntry, resourceName = NAT_FLOWS | High calls / media sessions | Ensure calls are managed in a way that resource usage stays within the specified threshold |
minor major critical
|
apRmResourcesGroupTrap |
DTMF_2833_OVER_THRESHOLD | 131429 | Resource monitoring module raising alarm - Resource task id = TASK_ID, threshold = 80%, current value = 82%,processName = tPpmEntry , resourceName = 2833 | High DTMF calls usage | Ensure calls are managed in a way that resource usage stays within the specified threshold |
minor major critical
|
apRmResourcesGroupTrap |
HMU_OVER_THRESHOLD | 131431 | Resource monitoring module raising alarm - Resource task id = TASK_ID, threshold = 80%, current value = 82%,processName = tPpmEntry , resourceName = HMU | High calls with HMU usage | Ensure calls are managed in a way that resource usage stays within the specified threshold |
minor major critical
|
apRmResourcesGroupTrap |
QOS_OVER_THRESHOLD | 131430 | Resource monitoring module raising alarm - Resource task id = TASK_ID, threshold = 80%, current value = 82%,processName = tPpmEntry, resourceName = QOS | High calls with QOS usage | Ensure calls are managed in a way that resource usage stays within the specified threshold |
minor major critical
|
apRmResourcesGroupTrap |
SRTPE_OVER_THRESHOLD | 131432 | Resource monitoring module raising alarm - Resource task id = TASK_ID, threshold = 80%, current value = 82%,processName = tPpmEntry , resourceName = SRTP_E |
High calls with SRTP_E usage |
Ensure calls are managed in a way that resource usage stays within the specified threshold |
minor major critical
|
apRmResourcesGroupTrap |
SRTD_OVER_THRESHOLD | 131433 | Resource monitoring module raising alarm - Resource task id = TASK_ID, threshold = 80%, current value = 82%,processName = tPpmEntry, resourceName = SRTP_D |
High calls with SRTP_D usage |
Ensure calls are managed in a way that resource usage stays within the specified threshold |
minor major critical
|
apRmResourcesGroupTrap |
SRTP_SESSIONS_OVER_THRESHOLD | 131428 | Resource monitoring module raising alarm - Resource task id = TASK_ID, threshold = 80%, current value = 82%,processName = tmbcd, resourceName = SRTP_SESSIONS | High calls of SRTP_SESSIONS | Ensure calls are managed in a way that resource usage stays within the specified threshold |
minor major critical
|
apRmResourcesGroupTrap |
TCP_OVER_THRESHOLD | 131434 | Resource monitoring module raising alarm - Resource task id = TASK_ID, threshold = 80%, current value = 82%,processName = tPpmEntry , resourceName = TCP/TLS | High TCP/TLS calls. | Ensure calls are managed in a way that resource usage stays within the specified threshold |
minor major critical
|
apRmResourcesGroupTrap |
SNMP
With respect to SNMP, the SBC uses the ap-res-monitor.mib to collate status data on each registered monitoring function, and generate SNMP traps on the configured resource monitoring object. The applicable OIDs use the prefix, 1.3.6.1.4.1.9148.3 under the table apRMResourceObjects, which is within ap-res-monitor.mib.
For traps, the SBC maintains an object named apRMNotifications, which includes the apRMNotificationObjects. This object refers to the apRmTrapType, which in conjunction with apRmTrapValue establishes a usable value pair that specifies each resource's utilization. The system can compare these values with your configured thresholds and generate the following when an active value crosses above or below your thresholds:
- apRmResourcesGroupTrap (threshold raised trap)
- apRmResourcesGroupClearTrap (threshold came down trap).
See the MIB Guide for detailed information about SNMP variables in the Resource Monitor OIDs section and SNMP traps in the apRMResourceObjectsTraps (ap-res-monitor.mib) section.