Documentation for telent in oai #149
Conversation
✅ Deploy Preview for nephio ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
arora-sagar
requested review from
liamfallon and
arora-sagar
and removed request for
tliron and
efiacor
| 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 -I oaitun_ue1 -c 3 $UPF_tun0_IP_ADDR | ||
| 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 -I oaitun_ue1 to force ping to use that interface. I know to ping UPF it is not needed but for internet it will be needed.
There was a problem hiding this comment.
Sure, I have updated it!
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: arora-sagar The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@jain-ashish-sam You also need to update |
|
@jain-ashish-sam Can you update the title of the PR and remove O1 from there and just keep telnet? Another thing can you explicitly mention in the PR description for the NF reconfiguration we are not using Nephio capabilities. |
| @@ -711,25 +711,106 @@ 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 | |||
There was a problem hiding this comment.
Can you remove the term O1?
| ``` | ||
|
|
||
| ```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
jain-ashish-sam
changed the title
|
As far as " The current 004-ran-network.yaml is not deploying o1 enabled DU." is concerned, I will update the packageRevision in the "test-infra" once catalog repo is tagged. |
The documentation include:
Note: For Bandwidth-Reconfiguration, we are not using Nephio capabilities. We are planning it to add in the future