Case23: M4370 Hardware Installation and troubleshooting

M4370 Hardware Installation:

Connect the following Hardware:

1. Fiber optic cable from the Firewall switch to OP3 of DU (BBU)
2. Fiber optic cable from OP2 of BBU to RU
3. GPS Antenna cable to connect to the GPS port on BBU
4. Power Cable from BBU to power outlet
5. Power Cable from the RU to power outlet
6. 4 Antennas from the Duplex RF Ports 1, 2, 3, 4 respectively.

M4370 Software & Configurations:

Perform the following steps:

Step 1:

Access the LMT using the IP Address: 192.168.5.216

Username: admin

Password: admin

Step 2:

Specify G-Node B name:

Example: SW-Dallas-Lab-GNB

Step 3:

Assign Integrated G-Node B IP Address:

Step 4:

Verify LMT (Maintenance IP Address for the M4370):

Step 5:

Add/Modify Cell Config Parameters (as per the client requirements):

Step 6:

Add/Modify Cell Sub-Frame Assignments (as per the client requirements):

Step 7:

Adjust the Transmit Power Levels based on the requirements (between 24 dBm to 37 dBm):

Step 8:

Modify & Verify Cell TAC ID, and CID:

Step 9:

Add/Modify Cell PLMN ID as per the Client’s Network needs after verifying MCC and MNC:

Step 10:

Add/Modify the Default 5QI Values:

Step 11:

Modify the QOS Parameters for Cell Index 1:

Step 12:

Add/Modify 5GC Configurations (AMF IP) while making sure the GNB IP and PLMN ID are also corresponding to the respective values:

Connectivity:

Step1:

Verify Connectivity from the GNB to the AMF using MobaXTerm & SSh Tools:

Also, verify AMF Connectivity through the Web GUI of GNodeB:

Step 2:
Verify if the CPE is connected with the G-Nodeb using the MobaXterm prompt of GNB:

Step 3:
Verify if CPE is connected through Web Portal:

Step 4:
Verify VPN Access in order to Access the Network without LMT.

Troubleshooting & Debugging:

Issue # 1:

Go through the history of Alarms & Verify Active Alarms:

Issue # 2:

Verify and confirm the APN Settings including the APN Name (specific to customer; examples are: “internet” ):

The APN was incorrect; changed from “xxxx” to “internet” after below Wireshark Log observation:

The CPE was visible with the correct CRNTI from GNodeB after the APN was corrected:

Issue # 3:

If CPE keeps getting disconnected after being idle, verify CPE Inactivity Timer under UE Capabilities.

It can be modified from 30 seconds to 60 seconds:

Issue # 4:

Incorrect PLMN was programmed. Updated PLMN from 315010 to 00101f after below 2 observations:

Issue # 5:

If AMF is Not accessible, verify the below:

Issue # 6:

.....

.....

Please find the atteched for more information: Download