Commit 24924193 authored by Sagar Arora's avatar Sagar Arora

Updating the xml test case

parent e3bec24e
...@@ -46,7 +46,7 @@ ...@@ -46,7 +46,7 @@
<class>DeployGenObject</class> <class>DeployGenObject</class>
<desc>Deploy OAI 5G CoreNetwork</desc> <desc>Deploy OAI 5G CoreNetwork</desc>
<yaml_path>yaml_files/5g_rfsimulator_e1</yaml_path> <yaml_path>yaml_files/5g_rfsimulator_e1</yaml_path>
<services>mysql oai-nrf oai-amf oai-smf oai-spgwu oai-ext-dn</services> <services>mysql oai-nrf oai-amf oai-smf oai-spgwu</services>
<nb_healthy>6</nb_healthy> <nb_healthy>6</nb_healthy>
</testCase> </testCase>
......
...@@ -39,6 +39,7 @@ UE3 --> 192.168.78.7 (RFSIM) ...@@ -39,6 +39,7 @@ UE3 --> 192.168.78.7 (RFSIM)
You should be able to deploy the [basic 5G RFsim deployment](../5g_rfsimulator/README.md). You should be able to deploy the [basic 5G RFsim deployment](../5g_rfsimulator/README.md).
First, start the MySQL server and 5GC: First, start the MySQL server and 5GC:
```bash ```bash
docker-compose up -d mysql oai-nrf oai-amf oai-smf oai-spgwu docker-compose up -d mysql oai-nrf oai-amf oai-smf oai-spgwu
docker-compose ps -a docker-compose ps -a
...@@ -47,6 +48,7 @@ docker-compose ps -a ...@@ -47,6 +48,7 @@ docker-compose ps -a
Wait till everything is healthy. Wait till everything is healthy.
Next, start the RAN: Next, start the RAN:
```bash ```bash
docker-compose up -d oai-cucp oai-cuup{,2,3} oai-du{,2,3} docker-compose up -d oai-cucp oai-cuup{,2,3} oai-du{,2,3}
``` ```
...@@ -54,6 +56,12 @@ docker-compose up -d oai-cucp oai-cuup{,2,3} oai-du{,2,3} ...@@ -54,6 +56,12 @@ docker-compose up -d oai-cucp oai-cuup{,2,3} oai-du{,2,3}
You can verify that the DUs and CU-UPs connected successfully: You can verify that the DUs and CU-UPs connected successfully:
```bash ```bash
docker logs rfsim5g-oai-cucp docker logs rfsim5g-oai-cucp
```
<details>
<summary>The output is similar to:</summary>
```console
[...] [...]
18535.139811 [RRC] I Accepting new CU-UP ID 3585 name gNB-OAI (assoc_id 257) 18535.139811 [RRC] I Accepting new CU-UP ID 3585 name gNB-OAI (assoc_id 257)
18535.425744 [RRC] I Accepting new CU-UP ID 3584 name gNB-OAI (assoc_id 260) 18535.425744 [RRC] I Accepting new CU-UP ID 3584 name gNB-OAI (assoc_id 260)
...@@ -65,11 +73,18 @@ docker logs rfsim5g-oai-cucp ...@@ -65,11 +73,18 @@ docker logs rfsim5g-oai-cucp
18536.135581 [NR_RRC] I Received F1 Setup Request from gNB_DU 3584 (du-rfsim) on assoc_id 267 18536.135581 [NR_RRC] I Received F1 Setup Request from gNB_DU 3584 (du-rfsim) on assoc_id 267
18536.135650 [RRC] I Accepting DU 3584 (du-rfsim), sending F1 Setup Response 18536.135650 [RRC] I Accepting DU 3584 (du-rfsim), sending F1 Setup Response
``` ```
</details>
You should see that the CU-UP initialized two GTP instances (one for NG-U, the You should see that the CU-UP initialized two GTP instances (one for NG-U, the other for F1-U):
other for F1-U):
``` ```bash
docker logs -f rfsim5g-oai-cuup docker logs -f rfsim5g-oai-cuup
```
<details>
<summary>The output is similar to:</summary>
```console
[...] [...]
122690.500374 [GTPU] I Initializing UDP for local address 192.168.73.2 with port 2153 122690.500374 [GTPU] I Initializing UDP for local address 192.168.73.2 with port 2153
122690.500406 [GTPU] I Created gtpu instance id: 96 122690.500406 [GTPU] I Created gtpu instance id: 96
...@@ -77,51 +92,107 @@ docker logs -f rfsim5g-oai-cuup ...@@ -77,51 +92,107 @@ docker logs -f rfsim5g-oai-cuup
122690.500414 [GTPU] I Initializing UDP for local address 192.168.71.161 with port 2152 122690.500414 [GTPU] I Initializing UDP for local address 192.168.71.161 with port 2152
122690.500420 [GTPU] I Created gtpu instance id: 97 122690.500420 [GTPU] I Created gtpu instance id: 97
``` ```
</details>
You should see the typical periodical output at the DUs: You should see the typical periodical output at the DUs:
```
```bash
docker logs rfsim5g-oai-du docker logs rfsim5g-oai-du
```
<details>
<summary>The output is similar to:</summary>
```console
[...] [...]
18626.446953 [NR_MAC] I Frame.Slot 128.0 18626.446953 [NR_MAC] I Frame.Slot 128.0
18629.151076 [NR_MAC] I Frame.Slot 256.0 18629.151076 [NR_MAC] I Frame.Slot 256.0
```
</details>
``` ```
Next, connect the UEs. They are configured to connect to each DU by setting the Next, connect the UEs. They are configured to connect to each DU by setting the
RFsimulator server address to the `public_net` IP address of each DU. For each, RFsimulator server address to the `public_net` IP address of each DU. For each,
you should see that they get an IP address you should see that they get an IP address
```bash ```bash
docker compose up -d oai-nr-ue{,2,3} docker compose up -d oai-nr-ue{,2,3}
docker logs oai-nr-ue ```
```bash
docker logs rfsim5g-oai-nr-ue
```
<details>
<summary>The output is similar to:</summary>
```console
[...] [...]
18758.176149 [NR_RRC] I rrcReconfigurationComplete Encoded 10 bits (2 bytes) 18758.176149 [NR_RRC] I rrcReconfigurationComplete Encoded 10 bits (2 bytes)
18758.176153 [NR_RRC] I Logical Channel UL-DCCH (SRB1), Generating RRCReconfigurationComplete (bytes 2) 18758.176153 [NR_RRC] I Logical Channel UL-DCCH (SRB1), Generating RRCReconfigurationComplete (bytes 2)
18758.176154 [NAS] I [UE 0] Received NAS_CONN_ESTABLI_CNF: errCode 1, length 87 18758.176154 [NAS] I [UE 0] Received NAS_CONN_ESTABLI_CNF: errCode 1, length 87
18758.176455 [OIP] I Interface oaitun_ue1 successfully configured, ip address 12.1.1.3, mask 255.255.255.0 broadcast address 12.1.1.255 18758.176455 [OIP] I Interface oaitun_ue1 successfully configured, ip address 12.1.1.3, mask 255.255.255.0 broadcast address 12.1.1.255
``` ```
</details>
Alternatively, check that they all received an IP address (the associated IP addresses might be different):
Alternatively, check that they all received an IP address (the associated IP
addresses might be different):
```bash ```bash
docker exec -it rfsim5g-oai-nr-ue3 ip a show oaitun_ue1 docker exec -it rfsim5g-oai-nr-ue3 ip a show oaitun_ue1
```
<details>
<summary>The output is similar to:</summary>
```console
[...] [...]
inet 12.1.1.2/24 brd 12.1.1.255 scope global oaitun_ue1 inet 12.1.1.2/24 brd 12.1.1.255 scope global oaitun_ue1
[...] [...]
```
</details>
```bash
docker exec -it rfsim5g-oai-nr-ue2 ip a show oaitun_ue1 docker exec -it rfsim5g-oai-nr-ue2 ip a show oaitun_ue1
```
<details>
<summary>The output is similar to:</summary>
```console
[...] [...]
inet 12.1.1.4/24 brd 12.1.1.255 scope global oaitun_ue1 inet 12.1.1.4/24 brd 12.1.1.255 scope global oaitun_ue1
[...] [...]
```
</details>
```bash
docker exec -it rfsim5g-oai-nr-ue ip a show oaitun_ue1 docker exec -it rfsim5g-oai-nr-ue ip a show oaitun_ue1
```
<details>
<summary>The output is similar to:</summary>
```console
[...] [...]
inet 12.1.1.3/24 brd 12.1.1.255 scope global oaitun_ue1 inet 12.1.1.3/24 brd 12.1.1.255 scope global oaitun_ue1
[...] [...]
``` ```
</details>
Also, note that each DU sees only one UE! At the CU-CP, you should see that Also, note that each DU sees only one UE! At the CU-CP, you should see that
each DU has been associated to a different CU-UP, based on the NSSAI (`exact each DU has been associated to a different CU-UP, based on the NSSAI (`exact
NSSAI match`): NSSAI match`):
```bash ```bash
docker logs rfsim5g-oai-cucp | grep CU-U docker logs rfsim5g-oai-cucp | grep CU-U
```
<details>
<summary>The output is similar to:</summary>
```console
[...] [...]
18757.531423 [RRC] I selecting CU-UP ID 3586 based on exact NSSAI match (3:0xffffff) 18757.531423 [RRC] I selecting CU-UP ID 3586 based on exact NSSAI match (3:0xffffff)
18757.531434 [RRC] I UE 1 associating to CU-UP assoc_id 261 out of 3 CU-UPs 18757.531434 [RRC] I UE 1 associating to CU-UP assoc_id 261 out of 3 CU-UPs
...@@ -130,10 +201,17 @@ docker logs rfsim5g-oai-cucp | grep CU-U ...@@ -130,10 +201,17 @@ docker logs rfsim5g-oai-cucp | grep CU-U
18758.772320 [RRC] I selecting CU-UP ID 3585 based on exact NSSAI match (2:0xffffff) 18758.772320 [RRC] I selecting CU-UP ID 3585 based on exact NSSAI match (2:0xffffff)
18758.772327 [RRC] I UE 3 associating to CU-UP assoc_id 257 out of 3 CU-UPs 18758.772327 [RRC] I UE 3 associating to CU-UP assoc_id 257 out of 3 CU-UPs
``` ```
</details>
Also, each UE should be able to ping the core network. For instance, with UE 1: Also, each UE should be able to ping the core network. For instance, with UE 1:
```bash ```bash
docker exec -it rfsim5g-oai-nr-ue ping -c1 12.1.1.1 docker exec -it rfsim5g-oai-nr-ue ping -c1 12.1.1.1
```
<details>
<summary>The output is similar to:</summary>
```console
PING 12.1.1.1 (12.1.1.1) 56(84) bytes of data. PING 12.1.1.1 (12.1.1.1) 56(84) bytes of data.
64 bytes from 12.1.1.1: icmp_seq=1 ttl=64 time=15.2 ms 64 bytes from 12.1.1.1: icmp_seq=1 ttl=64 time=15.2 ms
...@@ -141,6 +219,8 @@ PING 12.1.1.1 (12.1.1.1) 56(84) bytes of data. ...@@ -141,6 +219,8 @@ PING 12.1.1.1 (12.1.1.1) 56(84) bytes of data.
1 packets transmitted, 1 received, 0% packet loss, time 0ms 1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 15.155/15.155/15.155/0.000 ms rtt min/avg/max/mdev = 15.155/15.155/15.155/0.000 ms
``` ```
</details>
Finally, undeploy the UEs (to give them time to do deregistration), and then Finally, undeploy the UEs (to give them time to do deregistration), and then
the rest of the network: the rest of the network:
......
...@@ -482,4 +482,5 @@ networks: ...@@ -482,4 +482,5 @@ networks:
config: config:
- subnet: 192.168.78.1/28 - subnet: 192.168.78.1/28
driver_opts: driver_opts:
com.docker.network.bridge.name: "rfsim5g-ue" com.docker.network.bridge.name: "rfsim5g-ue"
\ No newline at end of file
\ No newline at end of file
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment