Documentation for telent in oai #149
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -711,21 +711,102 @@ The output is similar to: | |
| 9496.571150 [GNB_APP] I [gNB 0] Received NGAP_REGISTER_GNB_CNF: associated AMF 1 | ||
| ``` | ||
|
|
||
| ### Check Stats via telnet O1 Module | ||
| Make sure you have installed `netcat`. | ||
| ```bash | ||
| sudo apt update && sudo apt install netcat | ||
| ``` | ||
|
|
||
| ```bash | ||
| O1_IP=$(kubectl get svc oai-gnb-du-o1-telnet-lb -n oai-ran-du --context edge-admin@edge -o=jsonpath='{.status.loadBalancer.ingress[0].ip}') | ||
|
There was a problem hiding this comment. There shouldn't be any reference O1 - this is simply a telnet interface to the DU; not O1. The file is peppered with this misinformation. Minimally we should note that this is not a standard O1 interface but a proprietary telnet interface. There was a problem hiding this comment. I have removed the O1 reference |
||
| echo o1 stats | nc -N $O1_IP 9090 | ||
| ``` | ||
|
|
||
| <details> | ||
| <summary>The output is similar to:</summary> | ||
|
|
||
| ```console | ||
| { | ||
| "o1-config": { | ||
| "BWP": { | ||
| "dl": [{ | ||
| "bwp3gpp:isInitialBwp": true, | ||
| "bwp3gpp:numberOfRBs": 51, | ||
| "bwp3gpp:startRB": 0, | ||
| "bwp3gpp:subCarrierSpacing": 30 | ||
| }], | ||
| "ul": [{ | ||
| "bwp3gpp:isInitialBwp": true, | ||
| "bwp3gpp:numberOfRBs": 51, | ||
| "bwp3gpp:startRB": 0, | ||
| "bwp3gpp:subCarrierSpacing": 30 | ||
| }] | ||
| }, | ||
| "NRCELLDU": { | ||
| "nrcelldu3gpp:ssbFrequency": 630048, | ||
| "nrcelldu3gpp:arfcnDL": 629436, | ||
| "nrcelldu3gpp:bSChannelBwDL": 20, | ||
| "nrcelldu3gpp:arfcnUL": 629436, | ||
| "nrcelldu3gpp:bSChannelBwUL": 20, | ||
| "nrcelldu3gpp:nRPCI": 0, | ||
| "nrcelldu3gpp:nRTAC": 1, | ||
| "nrcelldu3gpp:mcc": "001", | ||
| "nrcelldu3gpp:mnc": "01", | ||
| "nrcelldu3gpp:sd": 16777215, | ||
| "nrcelldu3gpp:sst": 1 | ||
| }, | ||
| "device": { | ||
| "gnbId": 3584, | ||
| "gnbName": "du-rfsim", | ||
| "vendor": "OpenAirInterface" | ||
| } | ||
| }, | ||
| "O1-Operational": { | ||
| "frame-type": "tdd", | ||
| "band-number": 78, | ||
| "num-ues": 0, | ||
| "ues": [ ], | ||
| "load": 0, | ||
| "ues-thp": [ | ||
| ] | ||
| } | ||
| } | ||
| OK | ||
| ``` | ||
| </details> | ||
|
|
||
| Notice the block `O1-Operational` you will see the number of connected UEs, present load at the gNB and the DL/UL RLC `throughput` in `Kbps`. | ||
|
|
||
| ## Step 7: Deploy UE (20 Mhz) | ||
|
|
||
| If all three links are configured then you can proceed with deploying the UE `PackageVariants` | ||
|
|
||
| ```bash | ||
| kubectl apply -f - <<EOF | ||
| apiVersion: config.porch.kpt.dev/v1alpha1 | ||
| kind: PackageVariant | ||
| metadata: | ||
| name: oai-ue-20mhz | ||
| spec: | ||
| upstream: | ||
| repo: catalog-workloads-oai-ran | ||
| package: pkg-example-ue-bp-20mhz | ||
| revision: v1 # To be updated when catalog is tagged | ||
| downstream: | ||
| repo: edge | ||
| package: oai-ran-ue-20mhz | ||
| annotations: | ||
| approval.nephio.org/policy: initial | ||
| injectors: | ||
| - name: edge | ||
| EOF | ||
| ``` | ||
|
|
||
|
|
||
| The output is similar to: | ||
|
|
||
| ```console | ||
| packagevariant.config.porch.kpt.dev/oai-ue-20mhz created | ||
| ``` | ||
|
|
||
|
|
||
|
|
@@ -739,15 +820,15 @@ kubectl get pods -n oai-ue --context edge-admin@edge | |
| The output is similar to: | ||
|
|
||
| ```console | ||
| NAME READY STATUS RESTARTS AGE | ||
| oai-nr-ue-20mhz-f587d48b9-b4dx2 1/1 Running 0 21s | ||
| ``` | ||
|
|
||
|
|
||
| To verify if the UE is successfully connected you can use the below command | ||
|
|
||
| ```bash | ||
| UE_POD=$(kubectl get pods -n oai-ue --context edge-admin@edge -l app.kubernetes.io/name=oai-nr-ue-20mhz -o jsonpath='{.items[*].metadata.name}') | ||
| kubectl logs -n oai-ue $UE_POD -c nr-ue --context edge-admin@edge | grep "REGISTRATION ACCEPT" | ||
| kubectl logs -n oai-ue $UE_POD -c nr-ue --context edge-admin@edge | grep "Interface oaitun_ue1 successfully configured" | ||
| ``` | ||
|
|
@@ -756,8 +837,8 @@ kubectl logs -n oai-ue $UE_POD -c nr-ue --context edge-admin@edge | grep "Interf | |
| The output is similar to: | ||
|
|
||
| ```console | ||
| 791595.646099 [NAS] I [UE] Received REGISTRATION ACCEPT message | ||
| 791596.901105 [OIP] I Interface oaitun_ue1 successfully configured, ip address 10.1.0.2, mask 255.255.255.0 broadcast address 10.1.0.255 | ||
| ``` | ||
|
|
||
|
|
||
|
|
@@ -766,25 +847,199 @@ The output is similar to: | |
| To perform the end to end connectivity test you can ping from the UE to the UPF. | ||
|
|
||
| ```bash | ||
| UE_POD=$(kubectl get pods -n oai-ue --context edge-admin@edge -l app.kubernetes.io/name=oai-nr-ue-20mhz -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 | ||
|
There was a problem hiding this comment. @jain-ashish-sam I would say leave There was a problem hiding this comment. Sure, I have updated it! |
||
| ``` | ||
|
|
||
|
|
||
| The output is similar to: | ||
|
|
||
| ```console | ||
| PING 10.1.0.1 (10.1.0.1) 56(84) bytes of data. | ||
| 64 bytes from 10.1.0.1: icmp_seq=1 ttl=64 time=9.50 ms | ||
| 64 bytes from 10.1.0.1: icmp_seq=2 ttl=64 time=7.57 ms | ||
| 64 bytes from 10.1.0.1: icmp_seq=3 ttl=64 time=14.7 ms | ||
|
|
||
| --- 10.1.0.1 ping statistics --- | ||
| 3 packets transmitted, 3 received, 0% packet loss, time 2002ms | ||
| rtt min/avg/max/mdev = 7.572/10.584/14.680/3.001 ms | ||
| ``` | ||
|
|
||
|
|
||
| For now the extra interfaces which are created using inter-connectivity script does not perform natting to have internet access. | ||
|
|
||
| ## Step 9: Reconfiguring Bandwidth using O1-Telnet (20Mhz to 40Mhz) | ||
| 1. Get the O1-Ip: | ||
| ```bash | ||
| O1_IP=$(kubectl get svc oai-gnb-du-o1-telnet-lb -n oai-ran-du --context edge-admin@edge -o=jsonpath='{.status.loadBalancer.ingress[0].ip}') | ||
| ``` | ||
| 2. Delete the 20Mhz-Ue Package | ||
| ```bash | ||
| kubectl delete packageVariants oai-ue-20mhz | ||
| pkgList=$(kpt alpha rpkg get| grep oai-ran-ue-20mhz| grep edge| awk '{print $1;}') | ||
| for pkg in $pkgList | ||
| do | ||
| kpt alpha rpkg propose-delete $pkg -ndefault | ||
| kpt alpha rpkg delete $pkg -ndefault | ||
| done | ||
| ``` | ||
|
|
||
| 3. Stop the L1 | ||
| ```bash | ||
| echo o1 stop_modem | nc -N $O1_IP 9090 | ||
| ``` | ||
| 4. Reconfigure bandwidth | ||
| ```bash | ||
| echo o1 bwconfig 40 | nc -N $O1_IP 9090 | ||
| ``` | ||
| 5. Start L1 | ||
| ```bash | ||
| echo o1 start_modem | nc -N $O1_IP 9090 | ||
| ``` | ||
| 6. Check the reconfigured bandwidth | ||
| ```bash | ||
| echo o1 stats | nc -N $O1_IP 9090 | ||
| ``` | ||
|
|
||
| <details> | ||
| <summary>The output is similar to:</summary> | ||
|
|
||
| ```console | ||
| { | ||
| "o1-config": { | ||
| "BWP": { | ||
| "dl": [{ | ||
| "bwp3gpp:isInitialBwp": true, | ||
| "bwp3gpp:numberOfRBs": 106, | ||
| "bwp3gpp:startRB": 0, | ||
| "bwp3gpp:subCarrierSpacing": 30 | ||
| }], | ||
| "ul": [{ | ||
| "bwp3gpp:isInitialBwp": true, | ||
| "bwp3gpp:numberOfRBs": 106, | ||
| "bwp3gpp:startRB": 0, | ||
| "bwp3gpp:subCarrierSpacing": 30 | ||
| }] | ||
| }, | ||
| "NRCELLDU": { | ||
| "nrcelldu3gpp:ssbFrequency": 641280, | ||
| "nrcelldu3gpp:arfcnDL": 640008, | ||
| "nrcelldu3gpp:bSChannelBwDL": 40, | ||
| "nrcelldu3gpp:arfcnUL": 640008, | ||
| "nrcelldu3gpp:bSChannelBwUL": 40, | ||
| "nrcelldu3gpp:nRPCI": 0, | ||
| "nrcelldu3gpp:nRTAC": 1, | ||
| "nrcelldu3gpp:mcc": "001", | ||
| "nrcelldu3gpp:mnc": "01", | ||
| "nrcelldu3gpp:sd": 16777215, | ||
| "nrcelldu3gpp:sst": 1 | ||
| }, | ||
| "device": { | ||
| "gnbId": 3584, | ||
| "gnbName": "du-rfsim", | ||
| "vendor": "OpenAirInterface" | ||
| } | ||
| }, | ||
| "O1-Operational": { | ||
| "frame-type": "tdd", | ||
| "band-number": 78, | ||
| "num-ues": 0, | ||
| "ues": [ ], | ||
| "load": 0, | ||
| "ues-thp": [ | ||
| ] | ||
| } | ||
| } | ||
| ``` | ||
| </details> | ||
|
|
||
| You can see `nrcelldu3gpp:bSChannelBwUL` as 40. | ||
|
|
||
| ### Reconnect UE (40 Mhz) | ||
| ```bash | ||
| kubectl apply -f - <<EOF | ||
| apiVersion: config.porch.kpt.dev/v1alpha1 | ||
| kind: PackageVariant | ||
| metadata: | ||
| name: oai-ue-40mhz | ||
| spec: | ||
| upstream: | ||
| repo: catalog-workloads-oai-ran | ||
| package: pkg-example-ue-bp-40mhz | ||
| revision: v1 # To be updated when catalog is tagged | ||
| downstream: | ||
| repo: edge | ||
| package: oai-ran-ue-40mhz | ||
| annotations: | ||
| approval.nephio.org/policy: initial | ||
| injectors: | ||
| - name: edge | ||
| EOF | ||
| ``` | ||
|
|
||
|
|
||
| The output is similar to: | ||
|
|
||
| ```console | ||
| packagevariant.config.porch.kpt.dev/oai-ue-40mhz created | ||
| ``` | ||
|
|
||
|
|
||
| The UE will be deployed in the Edge cluster. To verify that the UE is deployed you can use the below command | ||
|
|
||
| ```bash | ||
| kubectl get pods -n oai-ue --context edge-admin@edge | ||
| ``` | ||
|
|
||
|
|
||
| The output is similar to: | ||
|
|
||
| ```console | ||
| NAME READY STATUS RESTARTS AGE | ||
| oai-nr-ue-40mhz-6b545c5c57-gwzdf 1/1 Running 0 16s | ||
| ``` | ||
|
|
||
|
|
||
| To verify if the UE is successfully connected you can use the below command | ||
|
|
||
| ```bash | ||
| UE_POD=$(kubectl get pods -n oai-ue --context edge-admin@edge -l app.kubernetes.io/name=oai-nr-ue-40mhz -o jsonpath='{.items[*].metadata.name}') | ||
| kubectl logs -n oai-ue $UE_POD -c nr-ue --context edge-admin@edge | grep "REGISTRATION ACCEPT" | ||
| kubectl logs -n oai-ue $UE_POD -c nr-ue --context edge-admin@edge | grep "Interface oaitun_ue1 successfully configured" | ||
| ``` | ||
|
|
||
|
|
||
| The output is similar to: | ||
|
|
||
| ```console | ||
| 791595.646099 [NAS] I [UE] Received REGISTRATION ACCEPT message | ||
| 791596.901105 [OIP] I Interface oaitun_ue1 successfully configured, ip address 10.1.0.2, mask 255.255.255.0 broadcast address 10.1.0.255 | ||
| ``` | ||
|
|
||
|
|
||
| ### Test the End to End Connectivity (40 Mhz) | ||
|
|
||
| To perform the end to end connectivity test you can ping from the UE to the UPF. | ||
|
|
||
| ```bash | ||
| UE_POD=$(kubectl get pods -n oai-ue --context edge-admin@edge -l app.kubernetes.io/name=oai-nr-ue-40mhz -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 | ||
| ``` | ||
|
|
||
|
|
||
| The output is similar to: | ||
|
|
||
| ```console | ||
| PING 10.1.0.1 (10.1.0.1) 56(84) bytes of data. | ||
| 64 bytes from 10.1.0.1: icmp_seq=1 ttl=64 time=9.50 ms | ||
| 64 bytes from 10.1.0.1: icmp_seq=2 ttl=64 time=7.57 ms | ||
| 64 bytes from 10.1.0.1: icmp_seq=3 ttl=64 time=14.7 ms | ||
|
|
||
| --- 10.1.0.1 ping statistics --- | ||
| 3 packets transmitted, 3 received, 0% packet loss, time 2002ms | ||
| rtt min/avg/max/mdev = 7.572/10.584/14.680/3.001 ms | ||
| ``` | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you remove the term O1?