05 eNodeB O&M

eRAN
Operation & Maintenance

V100R011C00
www.huawei.com
Contents
1. 24/7
2. Daily O&M
3. Weekly O&M
4. Monthly O&M
Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page1
No. 24/7
1 Monitoring fault alarms
No. Daily O&M
1 Checking equipment status
2 Checking busy-hour performance
3 Checking the Connection Status Between the U2000 and NEs
No. Weekly O&M
1 Backing up the eNodeB configuration data
2 Preparing weekly reports on network performance
3 Counting top alarms
4 Auditing security logs
5 Checking the voltage standing wave ratio (VSWR)
6 Checking the equipment transmit power
No. Monthly O&M
1 Checking power supply
2 Analyzing faults and customer complaints
3 Preparing monthly reports on network performance
4 Checking Security Patches for the OMU Operating System
5 Checking OS and Database Hardening
6 Checking Weak Passwords and Others
24/7 - Monitoring fault alarms
1. Fault Management > Browse Alarm > > Query Alarm Logs (application
style) or Monitor > Browse Current Alarm (traditional style).
Daily O&M
Checking Equipment Status
Whether the equipment status is normal is checked on the U2000
client based on an NE health check (NHC) report. NE is short for
network element.
Checking Busy-Hour Performance
This section describes how to determine the eNodeB performance
based on the KPIs in busy hours queried on the U2000 client.
Checking the Connection Status Between the U2000 and NEs
This section describes how to check the connection status between
the U2000 and NEs.
From the main menu of the U2000 client, choose Trace and Maintenance > Monitor >
NE Health Check (application style) or Maintenance > Network Health Check > NE
Health Check (traditional style).
Checking Busy-Hour
Performance
From the main menu of the U2000 client, choose Performance >
Measurement > Measurement Management (application style) or
Performance > Measurement Management (traditional style).
Checking Busy-Hour
Performance
Checking the Connection Status
Between the U2000 and NEs
Choose Configuration > Browser > NE Monitor(application style) or System > NE
Monitor (traditional style). The NE Monitor dialog box is displayed. You can query
the connection status of NEs. The connection status includes Normal and Offline
Weekly O&M
 Backing Up the eNodeB Configuration Data
The eNodeB configuration data can be automatically or manually backed
up on the U2000 client. Automatic backup can be periodically performed
and therefore applies to periodic tasks, and manual backup applies to other
tasks. For routine maintenance tasks, automatic backup is recommended.
 Preparing Weekly Reports on Network Performance
PRS Server is used for Performance Reporting
 Counting Top Alarms

eNodeB alarms can be counted on an U2000 client. Analyzing top alarms
helps know the severity and quantity distribution of top alarms in a week,
facilitating network quality analysis, fault diagnosis, and threat prevention.
Weekly O&M
 Auditing Security Logs
Security logs record security-related operations, such as login and
password changes. You must query and audit security logs on an U2000
client every week to check whether system operations are authorized.
 Checking the Voltage Standing Wave Ratio

The antennas working with a high VSWR can be located and rectified by
checking the VSWR. Therefore, cell coverage decrease or cell
unavailability caused by a high VSWR can be prevented.
 Checking the Equipment Transmit Power

You can estimate and adjust the equipment status by checking the radio
frequency (RF) transmit (TX) power on the U2000 client.
Monthly O&M
 Checking Power Supply
Checking power supply includes checking the alarms related to
power supply and storage batteries, the status of power
monitoring unit (PMU), and the status of storage batteries.
 Analyzing Faults and Customer Complaints

Analyzing customer complaints helps identify causes and analyze
the fault trends to facilitate troubleshooting.
 Preparing Monthly Reports on Network Performance
Monthly O&M
 Checking Security Patches for the OMU Operating System
This section describes how to check security patches for the OMU
operating system and configure the system security policy in real time to
ensure stable running of the system.
 Checking OS and Database Hardening

This section describes how to check operating system (OS) hardening
and configure the system security policy in real time to ensure stable
running of the system.
 Checking Weak Passwords and Others

This section describes how to check all password policies used in the
system for security. The password policies involve LMT, operating system
(OS), and FTP passwords
Trouble-shooting
1.Cell Unavailability Faults
 When the eNodeB detects that a cell is unavailable due to a
cell activation failure, the eNodeB reports an ALM-29240
Cell Unavailable alarm.
 Factors that may affect the running of a cell include

transmission, hardware, configuration, and RF. If any factor
is abnormal, the cell may be unavailable. In this case, check
these factors for troubleshooting
 Cell alarms
 ALM-29240 Cell Unavailable
 Transmission alarms
 ALM-25880 Ethernet Link Fault
 ALM-25886 IP Path Fault
 ALM-25888 SCTP Link Fault
 Hardware alarms
 ALM-26101 Inter-Board CANBUS Communication Failure
 ALM-26200 Board Hardware Fault
 ALM-26205 BBU Board Maintenance Link Failure
 Optical module and CPRI alarms related to the faulty

cell
 ALM-26230 BBU CPRI Optical Module Fault
 ALM-26246 BBU CPRI Line Rate Negotiation Abnormal
 RF module alarms related to the faulty cell
 ALM-26238 RRU Network Topology Type and Configuration
Mismatch
 Configuration alarms related to the faulty cell

 ALM-26251 Board Type and Configuration Mismatch
 License alarms
 ALM-26817 License on Trial
 Other alarms
 ALM-29201 S1 Interface Fault
 ALM-26262 External Clock Reference Problem
 Possible Causes
 Cell unavailability may be caused by:
 Incorrect data configuration
 Abnormal transport resources
 Abnormal RF resources
 Limited capacity or capability
 Faulty hardware
2. IP Transmission Faults
 If an Internet Protocol (IP) transmission fault occurs,
messages and service data cannot be transmitted between
communication devices, and a peer device cannot be
pinged.
 The following alarms may be reported to indicate Internet Protocol (IP)
transmission faults:
 ALM-25880 Ethernet Link Fault
 ALM-25885 IP Address Conflict
 ALM-25886 IP Path Fault
 ALM-25888 SCTP Link Fault
 ALM-29240 Cell Unavailable
 ALM-25952 User Plane Path Fault
 ALM-29207 eNodeB Control Plane Transmission Interruption
 ALM-25891 IKE Negotiation Failure
 ALM-29201 S1 Interface Fault
THE END

05 eNodeB O&M

Uploaded by

Copyright:

Available Formats

05 eNodeB O&M

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

05 eNodeB O&M

Uploaded by

Copyright:

Available Formats

eRAN

Operation & Maintenance

 Preparing Weekly Reports on Network Performance

PRS Server is used for Performance Reporting

 Counting Top Alarms

 Checking the Voltage Standing Wave Ratio

 Checking the Equipment Transmit Power

 Analyzing Faults and Customer Complaints

 Preparing Monthly Reports on Network Performance

 Checking OS and Database Hardening

 Checking Weak Passwords and Others

 Factors that may affect the running of a cell include

 ALM-25886 IP Path Fault

 ALM-25888 SCTP Link Fault

 ALM-26200 Board Hardware Fault

 ALM-26205 BBU Board Maintenance Link Failure

 Optical module and CPRI alarms related to the faulty

 ALM-26246 BBU CPRI Line Rate Negotiation Abnormal

 Configuration alarms related to the faulty cell

 ALM-26262 External Clock Reference Problem

 Incorrect data configuration

 Abnormal transport resources

 Limited capacity or capability

 ALM-25885 IP Address Conflict

 ALM-25886 IP Path Fault

 ALM-25888 SCTP Link Fault

 ALM-29240 Cell Unavailable

 ALM-25952 User Plane Path Fault

 ALM-29207 eNodeB Control Plane Transmission Interruption

 ALM-25891 IKE Negotiation Failure

 ALM-29201 S1 Interface Fault

You might also like