Make sure you are running the desired network setting: Settings -> Network (For our server we are using Bridged Adapter)

start the Appliance and login with appliance/ zabbix

apply the command (ifconfig) to know Zabbix IP address

From any device with reachability to the Zabbix server, open the browser and enter http://<zabbix-server-ip>/zabbix

You should be able to login with Admin / zabbix

Basestation configurations

We need to configure Zabbix (TM) PHP active agent for Yate based products.
It uses the Zabbix version 1 JSON to push requested data to a Zabbix server.
Zabbix.php is an active agent and is included in yate-common rpm package.

Option 2: Link for the group of hosts: Configuration -> Templates -> select (Template YateSDR) -> add the group of your hosts in the filed groups -> update.

Monitoring Triggers

From Zabbix frontend, navigate to Monitor -> problems to see list of the triggers.

S1AP Link Down

When the link is detected to be down a trigger called S1AP Disconnected will appear with high severity

When the link is detected to be recovered , the trigger will be marked as resolved and auto clear the severity

Basestation Stopped

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

Application Restarted

When Yate-sdr service restarts it will show a trigger named Yate-sdr service restarted with average severity.
This trigger automatically clears itself after successful restart of the service and mostly doesn't require any action from the admin.

Monitoring Unmet Demands

Unmet demands shows some indications that UEs 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.

low PHRdB: Low power headroom which indicates the UEs are using too much power.

Percentage of the difference between msg3 and prachs: The percentage of uncompleted connection due to not answering RRC Connection Request (msg3)

Loss rate for uplink and downlink: Lost packets for uplink and downlink

Note: The UL loss rate item is initially returned as percentage (UL packet loss rate in percent x100) according to 3GPP Section 4.4.4.2. In the template the item is divided by 100 for compatibility with the other items in the graph