SHARE_4G LTE ENodeB Onsite Troubleshooting Guide_V0 2

4G LTE eNodeB onsite troubleshooting guide Confidential

2013-06-21 Huawei Proprietary - Restricted Distribution Page1, Total12

4G LTE eNodeB onsite troubleshooting guide

Version Control

Version 0.1 Initial design Radu Manea

[email protected]

Version 0.2 Adding partners training Marina Gallardo

This document is designed to aid the onsite engineer in troubleshooting Huawei eNodeB 3900. Please follow Preparing a USB Flash Drive for Local Commissioning eNodeB 4G and on Huawei Warrooms request follow the below steps.

Document map: 1. LED blinking signification 2. Connect your laptop to the eNodeB and check if the config and software has

been loaded 3. Ping Next hop 4. Check the port status 5. Check Trust certificate 6. Check Device certificate 7. Check the Device certificate is being used. 8. Ping IPSEC gateway 9. Display IKESA 10. Run a diagnose of the tunnel. 11. Trace routes.



1. LED blinking signification a. USB dongle LED indicator.

The USB dongle LED should be ON for the duration of the commissioning, also the LED will blink intermittent during the commissioning. Normal behavior: when connecting the USB dongle, the BBU will start the commissioning procedure and will trigger intermittent LED blinking on both USB and BBU cards.

Not normal behavior: If the USB dongle LED stays OFF for more than 1 minute after inserted in the USB port, this might indicate there is a problem with the Config/Software. Please check the Software/config by performing the Preparing a USB Flash Drive for Local Commissioning eNodeB 4G guide.



b. UMPTa2 Board LEDs Normal (before commissioning & after commissioning) LED behavior: RUN LED will blink every 1 second ACT LED will blink every 0.15 seconds

During upgrade LED behavior: RUN & ACT LED will blink intermittent depending on the commissioning progress. After about 20 minutes, the commissioning will be completed and will return to normal behavior.

c. When the commissioning is completed the eNodeB will restart. This will turn off all Green LEDs and will turn ON the Orange CPRI LEDs (picture below).

This means that in 5 minutes the eNodeB should be operational.



2. If after about 20 minutes from connecting the USB drive to the BBU, the eNodeB doesnt have remote management, some extra troubleshooting between the field engineer and the war room might be required. Please make sure that you follow the below steps and command with someone from War Room, checking the results.

Connect your laptop to the eNodeB and check if the config and software has been loaded.

You will need the following: USB to RJ45 adaptor (see picture below) RJ45 Network cable Connect the USB to RJ45 adaptor to the USB port on the UMPTa2 board, and connect the RJ45 network cable to the USB adaptor and your laptop. Start by configuration the following IP on you network adaptor: IP: 192.168.0.1 Subnet: 255.255.255.0

Connect to the eNodeB by opening in Internet Explorer address 192.168.0.49 Login user: admin Password: hwbs@com



Use the LST ENODEB command to check eNodeBs name: If the eNodeB name & ID is not the NULL & 0 this means the config has not been loaded.



Use the LST SOFTWARE command to check eNodeBs software version. You are looking for Main Area V100R005C00SPC375 if this is not as below, the software load failed.

If the software or config load fails please perform again the Preparing a USB Flash Drive for Local Commissioning eNodeB 4G guide.



3. Ping Next hop

This is important to check if the transmission has been provisioned. Start by listing the Vlans LST VLANMAP

Ping next hop IP on Vlan 500. ( source IP is next hop IP+1). If next hop will reply go to step 4. Else consult with warroom.



4. Check the port status

There might be possible that there is a physical conection problem, or that the tellabs is not activated, so we can check the port status. For the NSN radiolinks the port are closed by default, and we will need to ask for activation.

5. Check if Trust certificates have been downloaded from the CA

Use DSP TRUSTCERT command to check the trust certificates. If the 3 certificates (see below) are present go to step 5.

1) Caroot.pem (internal Huawei) 2) Vodafone Wireless Issuing Auyhority.cer 3) Vodafone Root CA.cer

Else consult with war room.



6. Check if Device Certificates have been downloaded from the CA Use DSP CERTMK command to check the device certificates. You should find 2 of them,

1) Appcert.pen (internal Huawei) 2) OPKIDevCert.cer, issued by Vodafone Wireless Issuing Authority.

If Vodafone certificate is present (see below) go to step 6. Else consult with war room

7. Check the Device certificate is being used. Use DSP APPCERT commands to check that the device certificate is being used



for the IKE application. If the certificate is being correctly used, go to step 7.

8. Check if the IPSEC tunnel is UP Use DSP IKESA to check if Phase1 or Phase 2 is attempted. Consult with war room.

DSP IKESA:SN=7,IKEVSN=IKE_V2,DSPMODE=BRIEF;

If all the Phases 2 are Ready Stay alive, then the tunnel should is up. If phase 1 or 2 is none or not ready, then there is a problem establishing the tunnel. In that case go to step 8.



9. Run the command DSP DIAGNOSE as IKE type, and communicate the results to the war room, to help to find out the root cause of the tunnel problem.

10. Engineers from the War room might also need ping alternative ping test and trace routes to other IPs addresses. They will indicate which ones.



11. If we need to reaload a new configuration file, we have to make sure that the eNodeB is returned to its basic configuration, for that we need to use the command. ACT CFGFILE.

We will use Minimum configuration and effect type: inmediatly

Documents

SHARE_4G LTE ENodeB Onsite Troubleshooting Guide_V0 2