Issue: gnbsim2 Container Error Logs After Deployment

[hxngillani]

Hello Team,

First, thank you for the amazing work on this project! I’ve been following the documentation and have successfully set up the Aether platform. However, I’m facing an issue with the gnbsim2 container during testing, and I would appreciate your guidance to resolve it.

---

Environment Details

• Platform: VirtualBox
• Host OS: Ubuntu Server 22.04
• VM Configuration:
  • RAM: 10 GB
  • Storage: 100 GB
  • Networking: NAT with IP 10.0.2.15
• Deployment: Single VM setup running Kubernetes control plane, AMP, and gnbsim.

---

Setup Steps Followed

1. Copied main-upf.yml into main.yml and updated it with the required parameters:
   • Interface name
   • AMP IP address
   • Other deployment-specific configurations
2. Updated hosts.ini file according to my deployment setup.
3. Followed instructions to:
   • Add UPF blueprint
   • Load ROC for the UPF
4. Successfully deployed the setup:
   • All namespaces and pods are running.
   • Networking configuration is properly set up with IP addresses as expected.

---

Current Deployment Status

Namespaces

All namespaces are active:

• aether-5gc
• aether-5gc-upf-1
• aether-roc
• cattle-monitoring-system
• kube-system
• default

Pods

All pods are in the Running state:

• For aether-5gc: amf, smf, udm, nrf, etc.
• For aether-5gc-upf-1: upf-0 pod with interfaces (core and access) having valid IPs.
• For aether-roc: ONOS pods (onos-config, onos-topo), ROC GUI, and others.
• Monitoring pods (Prometheus, Grafana) are operational.

Networking

• Host IP: 10.0.2.15
• Interfaces in upf-0:
  • core: 192.168.250.x
  • access: 192.168.252.x
• Routing tables in UPFs confirm connectivity between core and access.

---

Issue Description

While testing the deployment:

1. Ran make aether-gnbsim-run to simulate traffic.
2. The gnbsim1 container runs successfully, and I can see its summary log without any issues.
3. The gnbsim2 container starts but does not display any logs or activity.

Both containers are in the Up state when checked using docker ps.

---

Expected Behavior

Both gnbsim1 and gnbsim2 containers should:

• Run without errors.
• Provide successful logs/summary output for the simulated traffic.

---

Actual Behavior

• Only gnbsim1 provides successful output in the logs.
• gnbsim2 is running with error logs in output please refer to last screenshot.

---

Screen Shorts

---

**Connectivity tests **

please check results of current deployment

---

[llpeterson]

There is nothing obviously wrong with what you've done. My guess is that you are running the blueprint on a single node, whereas we test this particular configuration on a 2-server configuration. (That is to say, there may have been a regression in this cast.) I suggest you try 2-servers and/or capture packet traces (as described in the guide) to help debug. Also, I'd recommend moving future questions to Slack, where there are more eyes on the issues.

[hxngillani]

Thank you for your answer yeah you are right i used single server for this 🙂 . I will try this with two servers and will update.

…

________________________________ From: Larry Peterson ***@***.***> Sent: Tuesday, January 7, 2025 6:40 PM To: opennetworkinglab/aether-onramp ***@***.***> Cc: Hassan Shabir ***@***.***>; Author ***@***.***> Subject: Re: [opennetworkinglab/aether-onramp] Issue: gnbsim2 Container Error Logs After Deployment (Issue #79) There is nothing obviously wrong with what you've done. My guess is that you are running the blueprint on a single node, whereas we test this particular configuration on a 2-server configuration. (That is to say, there may have been a regression in this cast.) I suggest you try 2-servers and/or capture packet traces (as described in the guide) to help debug. Also, I'd recommend moving future questions to Slack, where there are more eyes on the issues. — Reply to this email directly, view it on GitHub<#79 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ANB36HGGNNBMWIDTYSL6AU32JQGR7AVCNFSM6AAAAABUTT7OQWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZVHA3TSMZSGM>. You are receiving this because you authored the thread.Message ID: ***@***.***>