Skip to content

Latest commit

 

History

History
75 lines (66 loc) · 3.39 KB

ReadMe.md

File metadata and controls

75 lines (66 loc) · 3.39 KB
Raw

Local Testing Environment for OAI with Telnet

Follow the Installation Guide to install Nephio

Now, we need to follow the following exercise which we term as Master Excerises.

Step-1: Setting up infrastructure

Follow the steps 1 and 2 of Master Excercise

Step-2: Creating a Local operator-image and pushing it to Edge and Regional Cluster:

# Clone the Repo
cd oai/
docker build . -t local-ran-operator:v0.1
kind load docker-image local-ran-operator:v0.1  -n edge
kind load docker-image local-ran-operator:v0.1  -n regional

Step-3. Setting up Local Blueprint Repo:

  1. Create a new Repo at the Gitea-Cluster (172.18.0.200:3000) (Repo-name: 'oai-ran-bp' is recommended)
  2. Register the Repo to KPT
kpt alpha repo register \
--namespace default \
--repo-basic-username=<username_for_gitea> \
--repo-basic-password=<passowrd_for_gitea> \
<repo-url>
  1. Create and push blueprints to local as per the PR
cd test-infra/local-bp/
./create-bp-package.sh

The above script will create the following blueprint packages with updated values: 'oai-ran-operator', 'pkg-example-cucp-bp', 'pkg-example-cuup-bp', 'pkg-example-du-bp'. Make sure to check your repo, before moving forward.

Step-4: Making sure your PackageVariant point to your local Bp-Repo

 cd test-infra/local-bp/packageVariants/
 cp -r . $HOME/test-infra/e2e/tests/oai/

Note: If your repo-name is not 'oai-ran-bp', then update the upstream-repo of packageVariant accordingly.

Step-5: Deploy Core and Ran

Follow the steps 3-6 of Master Excercise

Step-6: Validate the deployment by ascessing telnet

 sudo apt update && sudo apt install netcat
 TELNET_IP=$(kubectl get svc oai-gnb-du-telnet-lb -n oai-ran-du --context edge-admin@edge -o=jsonpath='{.status.loadBalancer.ingress[0].ip}')
 echo o1 stats | nc -N  $TELNET_IP 9090

Step-7: Deploy UE (20 MHz):

cd test-infra/oai-ue/
kubectl apply -f namespace.yaml --context edge-admin@edge
kubectl apply -f 20Mhz/. --context edge-admin@edge

Run the Ping Test

UE_POD=$(kubectl get pods -n oai-ue --context edge-admin@edge  -l app.kubernetes.io/name=oai-nr-ue -o jsonpath='{.items[*].metadata.name}')
UPF_POD=$(kubectl get pods -n oai-core --context=edge-admin@edge -l workload.nephio.org/oai=upf -o jsonpath='{.items[*].metadata.name}')
UPF_tun0_IP_ADDR=$(kubectl exec -it $UPF_POD -n oai-core -c upf-edge --context edge-admin@edge -- ip -f inet addr show tun0 | sed -En -e 's/.*inet ([0-9.]+).*/\1/p')
kubectl exec -it $UE_POD -n oai-ue --context edge-admin@edge -- ping -c 3 $UPF_tun0_IP_ADDR

Step-8: Bandwidth Reconfigure Procedure (20 Mhz to 40 Mhz) using telnet

TELNET_IP=$(kubectl get svc oai-gnb-du-telnet-lb -n oai-ran-du --context edge-admin@edge -o=jsonpath='{.status.loadBalancer.ingress[0].ip}')
echo o1 stop_modem | nc -N $TELNET_IP 9090
echo o1 bwconfig 40 | nc -N $TELNET_IP 9090
echo o1 start_modem | nc -N $TELNET_IP 9090
echo o1 stats | nc -N $TELNET_IP 9090

After Reconfiguration, Connect the 40 Mhz ue using Step-7 and validate the Bandwidth-reconfiguration using Ping-Test