Skip to content

known_issues.md

Latest commit

 

History

History
86 lines (63 loc) · 2.79 KB

known_issues.md

File metadata and controls

86 lines (63 loc) · 2.79 KB

Known Issues and Solutions: Juju-Based RAN (CU/DU) Deployment

This document captures the recurring problems and their resolutions during the deployment of a Juju-based RAN environment, particularly focusing on the Central Unit (CU) and Distributed Unit (DU) components.

Issue 1: Invalid Configuration Keys

Error Message:

The following configurations are not valid: ['bandwidth', 'center-frequency', 'frequency-band', 'sub-carrier-spacing']

Cause: This error typically occurs when applying configuration options to the DU that are not recognized due to either incorrect syntax or timing (e.g., applying too early before the charm is ready).

Solution: Use the following valid Juju configuration commands:

juju config du bandwidth=40
juju config du frequency-band=77
juju config du sub-carrier-spacing=30
juju config du center-frequency=4060

Issue 2: DPDK Initialization Failure Due to IOVA Mode

Error Message (Excerpt):

EAL: FATAL: Cannot use IOVA as 'PA' since physical addresses are not available
PANIC in xran_ethdi_init_dpdk_io():
Cannot init EAL: Invalid argument

Cause: This is a known DPDK initialization issue related to IOVA mode (PA) incompatibility in certain environments, particularly when using incompatible microk8s versions.

Solution: Downgrade or switch to a compatible MicroK8s version and verify Juju version:

# Use MicroK8s v1.31.6 (revision 7746)
# Confirm Juju version
juju version
# Expected output:
3.6.4-genericlinux-amd64

Issue 3: Internet Connectivity Issues with LXD and Docker

Problem: When using charmcraft pack or other LXD-based operations, you might face internet connectivity issues inside the LXD container due to Docker bridge firewall rules.

Solution:

  1. Enable IPv4 forwarding:
echo "net.ipv4.conf.all.forwarding=1" > /etc/sysctl.d/99-forwarding.conf
systemctl restart systemd-sysctl
  1. Update Docker iptables rules to allow traffic from LXD bridge:
sudo su

iptables  -I DOCKER-USER -i lxdbr0 -j ACCEPT
ip6tables -I DOCKER-USER -i lxdbr0 -j ACCEPT
iptables  -I DOCKER-USER -o lxdbr0 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
ip6tables -I DOCKER-USER -o lxdbr0 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT

Reference Links:

Notes

  • Ensure the DU/CU charms are fully deployed and in a stable state before applying custom configurations.
  • Monitor DPDK-related logs carefully when troubleshooting hardware-related deployment failures.