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

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

Operational Procedures for BTS 51
For MIR testing, you must modify the following parameters in the
authorize
file (a Radius Server file):
l
ULBR: The uplink bit rate or sustained uplink rate (in kbps) at which each CPE has registered with
the BTS. The BTS is replenished with credits for transmission.
l
ULBL: The uplink bit limit or uplink burst allocation (in kbits). Indicates the maximum amount of
data that each CPE is allowed to transmit before being recharged at the sustained uplink data rate
(in kbps).
l
DLBR: The downlink bit rate or sustained downlink rate (in kbps) at which the BTS is replenished
with credits (tokens) for transmission to each of the CPEs in its sector.
l
DLBL: The downlink bit limit or downlink burst allocation (in kbits). Indicates the maximum amount
of data that the BTS is allowed to transmit to any registered CPE before it is replenished with the
transmission credits at the sustained downlink data rate (in kbps).
For more information about these MIR-specific parameters, refer to the cnWave™ 5G Fixed Configuration
Guide.
To test MIR, perform the following tasks:
l
Modifying the MIR parameters on the Radius Server
l
Running the MIR test
Modifying the MIR parameters on the Radius Server
To configure the MIR functionality, you must modify MIR -specific parameters in the
authorize
file (a
Radius Server file). This file contains all the CPE parameters passed onto the CPEs during the registration
process.
To modify the MIR-specific parameters, perform the following steps:
1. Log on to the Radius Server C4000 using a serial cable that is connected between the Console
Port and a USB port on the PC.
2. Use any Terminal program (for example, Tera Term) to select the PC port and log on to the Radius
Server C4000.
The Tera Term New Connection screen appears.
3. In the Tera Term New Connection screen, choose Serial and select the correct PC Port from the
drop-down list (for example, COM10 in this case as shown in Figure 41 ).