Cambium Networks cnWave 5G Fixed, Руководство по эксплуатации и устранению неисправностей

Страница: 59 / 85

Operational Procedures for BTS 59
a. Stop the Radius Server by running the following command:
$ sudo systemctl stop freeradius
b. Restart the Radius Server by running the following command:
$ sudo systemctl start freeradius
c. Reboot the CPE for which the MIR parameters are modified in the
authorize
file.
Either repower the CPE manually or go to the C100 UI and press the Reboot button (located
at the top right corner of the UI). Wait for the CPE(s) to get re-connected and re-registered
before doing the throughput tests.
Running the CIR test
On modifying the CIR-specific parameters in the
authorize
file for the required CPE, you must run the
test.
To complete the CIR testing, perform the following steps:
1. Ensure that all the other CPEs are powered off, except for the one under test.
Only one CPE is enough to demonstrate the CIR functionality. Ensure that the Radius Server is
restarted, and the CPE (under test) is rebooted after modifying the CIR-specific parameters. For
more information, refer to the
Modifying the CIR parameters on the Radius Server section.
2. Check the B1000 UI dashboard (BTS) to confirm that only one CPE is connected and registered.
3. Run the link capacity test using the Tools > Link Capacity Test page of B1000 UI.
You must run this test using a single shot 30s bidirectional traffic setting. Check the throughput,
which must show that the maximum downlink throughput doesn’t exceed 50 Mbps and that the
uplink throughput doesn’t exceed 20 Mbps (as shown in
Figure 47 ).
4. Edit the authorize file of the Radius to add four (4) VLANs, with each VLAN corresponding to a
priority.
5. Set up the p-bit priority bits on the machines that you are using to send traffic.
Example: If you are using a Linux PC, use the following scripts to set up Ultra High priority (VLAN
ID = 241) on both sides:
sudo ip link set enp1s0.241 type vlan id 241 egress-qos-map 0:7 1:7 2:7 3:7 4:7
5:7 6:7 7:7 ingress-qos-map 0:7 1:7 2:7 3:7 4:7 5:7 6:7 7:7
You can experiment the four priorities, but you must run four (4) concurrent iperf client sessions
from the BTS side and ensure that the CPE side is running an iperf server. Otherwise, you can use
one priority to test the CIR. An example of four priorities is shown in
Figure 50 .