You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Im deploying a CU-DU split in different machines, but when i try to setup the DU's F1U i'm having some assertion errors when binding an IP address. This happens when i configure both a localhost IP or a network IP.
Error on the DU:
--== srsRAN DU (commit a041e3162) ==--
Lower PHY in quad executor mode.
/home/nap/srsRAN_Project/lib/f1u/du/split_connector/f1u_split_connector.cpp:50: srsran::srs_du::f1u_split_connector::f1u_split_connector(const srsran::gtpu_gateway_maps&, srsran::gtpu_demux*, srsran::dlt_pcap&, uint16_t, std::string):
Assertion `not udp_gw_maps.default_gws.empty()' failed - Cannot create CU F1-U split connector, no default GW presentAborted
Currently the CU is connecting to the core, if no configuration for the F1U is provided the DU can connect to the CU, and the UE receives an IP address (although it does not have connection).
CU config:
gnb_id: 411# Optional UINT (411). Sets the numerical ID associated with the gNB.gnb_id_bit_length: 22# Optional UNIT. Sets the bit length of the gnb_id above. Format: integer between [22 - 32]cu_cp:
f1ap:
bind_addr:
10.0.23.73 # Configure the F1AP bind address, this will enable the CU-cp to connect to the DU# tem que ser igual cu-cup address da config da DUamf:
addr: 10.0.23.62 # The address or hostname of the AMF.bind_addr: 10.0.23.73 # A local IP that the gNB binds to for traffic from the AMF.supported_tracking_areas: # Configure the TA associated with the CU-CP
- tac: 1plmn_list:
- plmn: "00101"tai_slice_support_list:
- sst: 1mobility:
trigger_handover_from_measurements: true # Optional BOOLEAN (false). Sets whether or not to start HO if neighbor cells become stronger. Supported: [false, true]cells: # Optional TEXT. Sets the list of cells known to the CU-CP, their configs (if not provided over F1) and their respective neighbor cells.
- # Define Cell 1nr_cell_id: 0x19B0# Required UINT. The ID of this serving cell.periodic_report_cfg_id: 1# Optional UINT. The periodical report configuration to use for this serving cell.ncells: # Required TEXT. List of neighbor cells.
- nr_cell_id: 0x19B1# Required UINT. The ID of this neighbor cell.report_configs: [2] # Required TEXT. List of report configurations to use for measurements of this neighbor cell.gnb_id_bit_length: 22# Optional UINT. The ID of this gNB. Supported: [22 - 32]pci: 1# Optional UINT. The PCI of this serving cell. Supported: [0-1007]ssb_arfcn: 632628band: 78# Optional UINT. The NR band of this serving cell cell. Must be present if not provided over F1.ssb_scs: 30# Optional UINT. The SSB subcarrier spacing of this serving cell in KHz. Must be present if not provided over F1.ssb_period: 20# Optional UINT. The SSB period of this serving cell in ms. Must be present if not provided over F1.ssb_offset: 0# Optional UINT. The SSB offset of this serving cell. Must be present if not provided over F1.ssb_duration: 5# Optional UINT. The SSB duration of this serving cell in subframes. Must be present if not provided over F1.
- nr_cell_id: 0x19B1# periodic_report_cfg_id: 2ncells:
- nr_cell_id: 0x19B0report_configs: [2]gnb_id_bit_length: 22# Optional UINT. The ID of this gNB. Supported: [22 - 32]pci: 2# Optional UINT. The PCI of this serving cell. Supported: [0-1007]ssb_arfcn: 632628band: 78# Optional UINT. The NR band of this serving cell cell. Must be present if not provided over F1.ssb_scs: 30# Optional UINT. The SSB subcarrier spacing of this serving cell in KHz. Must be present if not provided over F1.ssb_period: 20# Optional UINT. The SSB period of this serving cell in ms. Must be present if not provided over F1.ssb_offset: 0# Optional UINT. The SSB offset of this serving cell. Must be present if not provided over F1.ssb_duration: 5# Optional UINT. The SSB duration of this serving cell in subframes. Must be present if not provided over F1.report_configs: # Sets the report configuration for triggering handover
- report_cfg_id: 1# Report config ID 1report_type: periodical # Sets the report type as periodicalreport_interval_ms: 480# Sets to report every 480ms
- report_cfg_id: 2report_type: event_triggeredevent_triggered_report_type: a3meas_trigger_quantity: rsrpmeas_trigger_quantity_offset_db: 6hysteresis_db: 0time_to_trigger_ms: 100report_interval_ms: 1024cu_up:
f1u:
socket: # Define UDP/IP socket(s) for F1-U interface.
- # Socket 1bind_addr: 127.0.10.1 # Required TEXT. Sets the address that the F1-U socket will bind to.ext_addr: 10.0.23.73udp:
max_rx_msgs: 256# maximum packets read from the socket in a single syscall.pool_threshold: 0.9# Pool occupancy threshold, after which packets are dropped.ngu:
socket:
- bind_addr: 10.0.23.73
DU config:
gnb_id: 411# Optional UINT (411). Sets the numerical ID associated with the gNB.gnb_id_bit_length: 22# Optional UNIT. Sets the bit length of the gnb_id above. Format: integer between [22 - 32]gnb_du_id: 0cells:
- pci: 1dl_arfcn: 632628# Optional TEXT. Set the ARFCN for the above PCI. Note, this must match the value used in the cell_cfg section.f1ap:
cu_cp_addr: 10.0.23.73bind_addr: 10.0.22.176f1u:
socket:
- bind_addr: 127.0.0.1ext_addr: 10.0.22.176five_qi: 9udp:
max_rx_msgs: 256# maximum packets read from the socket in a single syscall.pool_threshold: 0.9# Pool occupancy threshold, after which packets are dropped.ru_sdr:
srate: 23.04# Required FLOAT (61.44). Sets the sampling rate of the RF-frontend in MHz.device_driver: uhd # Required TEXT (uhd). RF device driver name. Supported: [uhd, zmq].device_args: type=b200,num_recv_frames=64,num_send_frames=64 # Optional TEXT. An argument that gets passed to the selected RF driver.otw_format: sc12tx_gain: 80rx_gain: 40cell_cfg:
dl_arfcn: 632628sector_id: 1band: 78channel_bandwidth_MHz: 20common_scs: 30plmn: "00101"tac: 1pci: 1
I noticed that the NRU field was removed and that this F1U field is quite recent, i've update the code yesterday (19/02). Are you aware of this problem? I dont know if there is any configuration error, but doesnt seem like it as i've tried various combinations.
I have the CU in a Virtual Machine and the DU in an host computer with an USRP B210.
Best regards,
And thanks for the project!
The text was updated successfully, but these errors were encountered:
Hello,
Im deploying a CU-DU split in different machines, but when i try to setup the DU's F1U i'm having some assertion errors when binding an IP address. This happens when i configure both a localhost IP or a network IP.
Error on the DU:
Currently the CU is connecting to the core, if no configuration for the F1U is provided the DU can connect to the CU, and the UE receives an IP address (although it does not have connection).
CU config:
DU config:
I noticed that the NRU field was removed and that this F1U field is quite recent, i've update the code yesterday (19/02). Are you aware of this problem? I dont know if there is any configuration error, but doesnt seem like it as i've tried various combinations.
I have the CU in a Virtual Machine and the DU in an host computer with an USRP B210.
Best regards,
And thanks for the project!
The text was updated successfully, but these errors were encountered: