Merge pull request #5 from accelleran/2023.3.0

2023.3.0
accelleran · Mar 26, 2024 · e6c2692 · e6c2692
2 parents ada05f5 + 05086ed
commit e6c2692
Show file tree

Hide file tree

Showing 10 changed files with 48 additions and 48 deletions.
diff --git a/docs/cu-configuration/config_view.png b/docs/cu-configuration/config_view.png
diff --git a/docs/cu-configuration/cu_configuration.png b/docs/cu-configuration/cu_configuration.png
diff --git a/docs/cu-configuration/index.md b/docs/cu-configuration/index.md
@@ -40,3 +40,8 @@ The 5G CU-UP has a number of configuration parameters as seen below:
 </p>
 
 **IMPORTANT**  Do not attempt to modify slices and PLMNs unless you are aware of the target Scenario you want to achieve: slice configuration and multiple PLMN (MOCN) configurations are rather complex to handle and require that CU, DU and Core are configured coherently in order for such scenarios to be functional. We recommend to consult the relative sections of this document and contact your Core Network Supplier and Accelleran to tailor a solution for your specific case. 
+
+## 3. Extra Info
+
+- As explained all CU-CP or CU-UP parameters would require to set the admin state to locked before submitting.
+- But using the API calls, some of parameters would take effect immediately without a need to restart the CU-CP (e.g. modifications on the neighbor relation configuration)
diff --git a/docs/cu-configuration/topology_view.png b/docs/cu-configuration/topology_view.png
diff --git a/docs/images/accelleran_logo.png b/docs/images/accelleran_logo.png
diff --git a/docs/index.md b/docs/index.md
@@ -1,36 +1,30 @@
 
-# Operational User Guide 
+# Operational User Guide
 
 ## 1. Introduction
 
 This guide describes how to operate the Accelleran ORAN 5G  Platform and the different network components (RIC, CU, DU and L1). The scope of this document is therefore to cover only the operational aspects of the platform, including the basic configuration and examples of some test cases. 
 
-This means that the installation and initial configuration of the System has been already made by Accelleran Customer Support and there is no need to worry about how to prepare the server, install and initialise the components.
-
-2023.2.0 release includes Accelleran Cell Wrapper, which works as a layer on top of the DU and RU. This provides a common interface for configuration and control over a cell. 
-
-It monitors a DU and RU through periodic health checks and uses the control interface internally to attempt an automatic repair from failures. These health checks include checks for reachability of the servers, traffic thresholds, status of the applications and checks on a set of log messages. 
-
 
 ## 2. Releases
-This document is released together with the system release 2023.2.0. 
-This system release contains 
+This document is released together with the system release 2023.3.0. 
+The release contains:
 
 | component    | version                        |
 |--------------|--------------------------------|
-| RIC          | 6.5.2                          |
-| CU CHART     | 6.0.0                          |
-| CU APP       | R4.2.3_jupiler                 |
-| DU           | 2023-05-08-q1-patch-release-01 |
-| L1           | 8.7.4                          |
+| DRAX/RIC          | 7.0.0                          |
+| CU CHART     | 7.0.0                          |
+| CU APP       | R4.3.12_leffe                 |
+| cell wrapper config | 0.2.4                          |
+| Effnet-DU           | 2024-01-31-q3-patch-release-01-8.7.4 |
+| Phluido-UL1           | 8.7.4                          |
 | BNTL650      | 0.7.0                          |
-| BNTL550      | 0.5.2/0.6.0                    |
-| cell wrapper | 2.3.0                          |
-| DU/RU        | 5.1.0.30736                    |
+| BNTL550      | 0.7.1                    |
+| NodeH-DU/RU        | 5.2.0.32092                    |
 
 ## 3. Dashboard
 
-The dashboard can be accessed via ```https://"RIC_CU_VM_IP":31315```
+The dashboard can be accessed via ```https://"DRAX_VM_IP":31315```
 
 ### 3.1. Cell Monitoring
 From the **Home** tab the cell status can be monitored and the UEs attached to it.
@@ -51,15 +45,8 @@ The DRAX dashboard also uses grafana to view measurements and counters.
         - UE Measured SINR
         - DL Throughput on the NG-Interface per UE.
         - UL Throughput on the NG-Interface per UE.
-    - Accessibility and Mobility Counters (e.g. Number of RRC Attempts or Number of Handover Execution Successes) can be viewed in the **5G PM Counters** dashboard. The dashboard includes:
-        - RRC Connection Attempts and sub-counters for each of the connection attempt cause (MO Signalling, MO Data, ... etc)
-        - RRC Connection Successes and sub-counters for each of the connection success causes (MO Signalling, MO Data, ... etc)
-        - PDU Session Setup Requests.
-        - PDU Session Setup Failures.
-        - Intra-gNB Handover Execution Attempts.
-        - Intra-gNB Handover Execution Successes.
-        - Mean and Max Number of RRC Connections.
-        > PS: The definition of these counters are included in 3GPP TS 28.552 .
+    - Accessibility and Mobility Counters (e.g. Number of RRC Attempts or Number of Handover Execution Successes) can be viewed in the **5G CUCP PM Counters** dashboard.
+    > PS: The definition of these counters are included in 3GPP TS 28.552 .
     - A live view of the RIC/CU/CellWrapper Logs can be viewed using the **Loki Log Dashboard**.
 
 Example **5G UE Monitoring** report:
@@ -88,7 +75,6 @@ Below sections will give more information on how to change some of the RAN param
 * [RU/DU Configuraiton](modifying-ran650-or-ran550/index.md)
 * [Handover Configuration](handover-configuration/index.md)
 * [MOCN and Slicing](mocn-and-slicing/index.md)
-* [Split 2 RU/DU Configuration](nodeh-du-ru-operation/index.md)
 * [Logs Collection](logs-collection/index.md)
 
 

diff --git a/docs/logs-collection/grafana_view.png b/docs/logs-collection/grafana_view.png
diff --git a/docs/logs-collection/index.md b/docs/logs-collection/index.md
@@ -28,15 +28,17 @@ A directory in the DU machine with the DU/L1 logs and configuration files will b
 A tcpdump on the CU VM can be started before running the test case to save all the packets exchanged between the core <-> CU <-> DU.
 
 - Below command can be used from within the CU VM.
+```bash
 tcpdump -i enp1s0 'sctp' -w cu_side_trace.pcap
+```
 
-> - This is assuming the interface the CU VM is using is "enp1s0", please change it according to your setup.
-> - It is better to save only sctp data unless the test/debug case in question is related to user plane packets otherwise use "sctp or udp" in the command.
+> - This is assuming the interface the CU VM is using is ```enp1s0```, please change it according to your setup.
+> - It is better to save only sctp data unless the test/debug case in question is related to user plane packets otherwise use ```sctp or port 2152``` in the command.
 
 To save the CU logs:
 
 - Create a file named collect_logs.sh with the content below.
-- By default it will save the logs of the last 10minutes but to save the logs of the last 20mins for example, run: "``` ./collect_logs.sh 10```"
+- By default it will save the logs of the last 10minutes but to save the logs of the last 20mins for example, run: ``` ./collect_logs.sh 10```
 - The log files will be saved in below two files: ```/tmp/logs.tar.gz``` and ```/tmp/logs-previous.tar.gz```
 
 ```bash
@@ -72,13 +74,6 @@ done
 
 LOGFILE="${LOGDIR}/version.txt"
 helm list > "$LOGFILE"
-{
-kubectl get pods
-helm status acc-5g-cu-cp
-helm status acc-5g-cu-up
-helm status ric
-helm status cw
-} > "$LOGFILE"
 
 tar czf "$LOGDIR.tar.gz" "$LOGDIR"
 rm -r "$LOGDIR"
@@ -114,13 +109,6 @@ done
 
 LOGFILE="${LOGDIR}/version.txt"
 helm list > "$LOGFILE"
-{
-kubectl get pods
-helm status acc-5g-cu-cp
-helm status acc-5g-cu-up
-helm status ric
-helm status cw
-} > "$LOGFILE"
 
 tar czf "$LOGDIR.tar.gz" "$LOGDIR"
 rm -r "$LOGDIR"

diff --git a/docs/modifying-ran650-or-ran550/index.md b/docs/modifying-ran650-or-ran550/index.md
@@ -75,4 +75,26 @@ Below are some useful checks to confirm the status of the RU after the reboot.
 
 - The RAN650 or RAN550 units usually take from 4~6 mins to boot up after a power cycle. The status of the RU boot up will be printed in a file during boot up. It can be checked by: 
 
-```tail -F /tmp/logs/radio_status```
+```tail -F /tmp/logs/radio_status```
+
+
+## 3. Extra Info
+
+- When submitting the config, the `advanced settings` toggele on the configuration confirmation pop up message can be used to not restart the DU, RU or both.
+
+> PS: As explained above, for the Frequency change for example an RU and DU restart would be needed.
+
+- Below table have details on these parameters to take effect:
+
+| Parameter         | Need DU Restart       | Need RU Restart   |
+| ---               | ---                   | ---               |
+| CELL_ID           | True                  | ***False****             | 
+| TAC               | True                  | ***False***             | 
+| PCI               | True                  | ***False***             | 
+| Frequency Band    | True                  | ***False***             | 
+| DL ARFCN          | True                  | True              | 
+| DL Bandwidth      | True                  | True              | 
+| Max EIRP          | ***False***                  | ***False***              | 
+| PLMN_ID and Slice Config | True                  | ***False***             | 
+
+> Note: Except for the Max EIRP (RU TX Power) all cell parameters would require at least the DU to restart to take effect.
diff --git a/mkdocs.yml b/mkdocs.yml
@@ -1,4 +1,4 @@
-site_name: Accelleran 5G O-RAN System - 2023.2.0 release
+site_name: Accelleran 5G O-RAN System Operational Guide [2023.3.0]
 
 site_url: https://accelleran.github.io/ran-operation-guide/
 theme: 
@@ -41,5 +41,4 @@ nav:
     - 'modifying-ran650-or-ran550/index.md'
     - 'handover-configuration/index.md'
     - 'mocn-and-slicing/index.md'
-    - 'nodeh-du-ru-operation/index.md'
     - 'logs-collection/index.md'