Issues with gNB Configuration on Band n3 and Metrics Server Integration (BladeRF2)

[MamdouhEgy]

I am currently working with the following hardware setup:

1-Dell OptiPlex Tower Plus 7010 (Intel Core i7-13700K, 32GB RAM) – Hosting the Open5GS core and the installed srsRAN.
2-BladeRF 2.0 micro XA4 – Serving as the base station (BS).
3-5 Xiaomi 11 Lite 5G NE – Used as the user equipment (UE).
4- Sysmocom SIM Cards

I successfully have a full connection between UEs and the internet and capturing data working fine.

I am encountering two issues and would appreciate any guidance:

1. gNB Configuration Issue on Band n3
   I am unable to configure the gNB to operate on Band n3 (dl_arfcn=375500). However, it functions correctly on Band n78 (dl_arfcn=632628). I have reviewed the configuration file, but I have not been able to identify the cause of the issue.

2. Metrics Server Integration Issue
   I have adjusted the docker-compose.yml file to include Grafana, Metrics Server, and InfluxDB. Additionally, I have added the Metrics Server into the gNB configuration YAML file using the following parameters (not shown in the above screenshot but it was added in the same YML file):

metrics:
    enable_json_metrics: true
    addr: 172.19.1.4  # Metrics Server IP
    port: 55555       # Metrics Server Port

Despite verifying the indentation and attempting to enclose the IP address in quotes (""), I continue to encounter the following error:

"ini was not able to parse metrics.addr"

Any insights or recommendations for resolving these issues would be greatly appreciated.

[improperaffo]

@MamdouhEgy could you show the output of the console from when you launch the gNB until you get the ini error?