BTS Monitoring with Zabbix
This guide will explain how to use Zabbix for monitoring BTS in SatSites.
Note: If Zabbix and BTS are not already configured , please refer to LabKit/SatSite Monitoring with Zabbix – Basic Configurations
Monitoring BTS with Zabbix will offer:
- Critical triggers
- When the application restarted
- When the Basestation is down
- Unmet demands Showing when the network was unable to meet the demands of MSs with an indication of the cause.
- RF Measurements Shows the Noise value.
- SatSite Hardware
- the following rpms
- yate-bts-6.1.1-priv376_8737svn_1.mga5 or newer
- yate-bts-nipc-6.1.1-priv376_8737svn_1.mga5 or newer
- yate-bts-roaming-6.1.1-priv376_8737svn_1.mga5 or newer
From Zabbix frontend, navigate to Monitor -> problems to see list of the triggers.
When the Basestation stops, will show a trigger named Basestation Stopped with high severity.
when the Basestation is up again, the trigger will be auto resolved and the severity will be cleared.
When Yate-sdr service restarts it will show a trigger named Yate-sdr service restarted with average severity which will automatically clears itself after successful restart.
Monitoring Unmet Demands
Unmet demands shows some indications that MSs are failing to connect or to use the network resources. It meant to give an idea where the problem is happening and how dangerous its affecting the network. This graph is to give a clue of the problem and cannot be used for troubleshooting.
From Zabbix frontend, navigate to Monitor -> Graphs -> Select Group/ host -> Select BTS Unmet Demands graph from the drop down menu. The graph will show:
- RACH Success Rate
- Handover Success Rate
- Paging Success Rate
- SDCCH Assignment Success Rate
- TCH Assignment Success Rate
- Call FER
Shows the Noise value as an indication of the Rf environment.
From Zabbix frontend, navigate to Monitor -> Graphs -> Select Group/ host -> Select BTS Noise