Control Host Statistics
MaaS monitors the health and performance of your TMedia host servers and individual application processes. For 1+1 redundant deployments, each host is monitored separately with role identification.
Host Status
Host State
Text
Operational state (Up/Down)
Host Name
Text
Configured hostname
Role
Text
Primary or Secondary (for 1+1)
Serial Number
Text
Hardware serial number
OAM State
Text
Host OAM operational state
Firewall Status
Text
Whether TBRouter firewall is enabled
Reboot Required
Text
Whether a reboot is pending
Scheduling Problem
Count
Number of scheduling issues detected
License Expired
Text
License expiration status
License Expiring Soon
Text
License approaching expiration
Firmware Version
Text
Current software version
Dump Files
Count
Core / crash dump files present on the host
Host Performance
CPU Usage
%
Overall CPU utilization
RAM Usage
%
Memory utilization
File System Used
%
Disk space utilization
File System Free
%
Available disk space (calculated)
Ethernet Port Statistics
Ethernet port monitoring is currently available for ProSBC deployments. TMG support is coming soon.
MaaS monitors the physical Ethernet ports on each host:
Ethernet Port Up
Binary
Port operational status (Up/Down)
Received Bytes
Bytes
Total bytes received on the port
Received Errors
Count
Receive errors on the port
Sent Bytes
Bytes
Total bytes sent on the port
Sent Errors
Count
Transmit errors on the port
IP Interface Statistics
IP interface monitoring is currently available for ProSBC deployments. TMG support is coming soon.
MaaS monitors IP interfaces configured on each host:
Availability
Text
Interface availability status
Link Status
Text
Physical link state
Received Bytes/s
Bps
Incoming data rate
Received Packets/s
pps
Incoming packet rate
Transmitted Bytes/s
Bps
Outgoing data rate
Transmitted Packets/s
pps
Outgoing packet rate
Application Statistics
MaaS monitors individual application processes running on each host, including per-application HA state for 1+1 deployments.
Application Metrics
App State
Text
Application operational state
HA State
Text
Per-application high availability state
Core App HA
Text
HA state of core applications (gateway, tbsip, tbrouter). Drives switchover alerts.
App CPU
%
Per-application CPU usage
Common Applications Monitored
Toolpack System Manager
toolpack_sys_mgr
Core system management
TBOAM App
tboam_app
OAM application
SNMP Agent
tbsnmpagent
SNMP interface
Stream Server
stream_server
Media streaming
TB Router
tbrouter
Firewall/routing (if enabled)
MySQL
mysqld
Database server
Ruby
ruby
Web interface
SNMP Daemon
snmpd
SNMP service
Sig Trace
tbsigtrace
Signaling trace
CLI Tools
tbx_cli_tools_remote
Remote CLI
IP Watchdog
ipwatchd
IP monitoring
KNI Single
kni_single
Kernel network interface
Alerts
High Severity
Host Down
State ≠ "Up"
Host is not operational
File System 95%
Disk > 95%
Critical disk space
App CPU 95%
5-min avg > 94%
Critical application CPU usage
RAM Usage 95%
RAM > 95%
Critical memory usage
Ethernet Port Down
Port status = Down
Physical Ethernet port is offline
Average Severity
File System 80%
Disk > 80%
Elevated disk usage
App CPU 80%
15-min avg > 79%
Elevated application CPU usage
Scheduling Problem
Scheduling issues > 0
Host has scheduling problems
Firewall Scheduling Problem
Firewall issues > 0
Firewall has scheduling problems
Dump File Detected
Dump files > 0
A core or crash dump is present on disk
Information Severity
RAM Usage 80%
RAM > 80%
Elevated memory usage
Reboot Required
Reboot pending = True
Host requires a reboot
Core Application Switchover
Core App HA state changed
A core application switched Active/Standby role
Understanding HA States
For 1+1 redundant deployments, application HA states indicate:
Active
Application is handling traffic
Standby
Application is ready for failover
Initialized
Application has started and is coming online
Ready
Application is operational but not yet carrying traffic
Not Present
Application is not installed or not expected on this host
Not Ready
Application is not in a ready state
Core Application HA Tracking
MaaS tracks Core Application HA — the HA state of the applications that actually carry your traffic (gateway, tbsip, tbrouter, and others). When any of these flips between Active and Standby, a Core Application Switchover notification fires so your team knows traffic has moved units.
This is distinct from generic App State — a process can be running (App State = Up) while still being Standby. Core App HA tells you which unit is actually handling calls.
HA Failover Behavior
In a 1+1 deployment, MaaS monitors both hosts independently. During a failover:
The previously Active host transitions applications to Standby or Not Ready
The previously Standby host transitions applications to Active
MaaS continues monitoring both hosts throughout the transition
A Core Application Switchover notification is sent
Monitor the standby host — issues there will become problems during failover.
Troubleshooting
Last updated
Was this helpful?
