06 ElasticNet UME Alarm Management and Cases - P70

ElasticNet UME Alarm Management and
Cases
CONTENTS
 Overview
 Alarm and Notification Monitoring
 Alarm Handling
 Alarm Management
 Alarm Settings
 Typical Alarm Cases
Alarm Management Implementation Principle
 Alarms are an information source

reflecting NE or network operation and
assisting fault localization. To ensure
normal network operation, the network
administrator or maintenance
engineers should monitor and handle
alarms regularly.
The alarm management principles of the UME system
© ZTE All rights reserved

Basic Concepts
 Alarms: An alarm reports an exception during NE or UME operation, so that

maintenance engineers can take the corresponding action in a timely manner.
 Notifications: A notification is a prompt message related to an operation or error when
the managed NE or the UME system is working, so that maintenance engineers can
immediately know the operational status of each module.
Differences Between Alarms and Notifications:
 Alarms are sourced from faults or exceptions. If they are not removed, services may be affected.
Maintenance engineers can acknowledge and clear alarms as needed.
 Notifications are only messages reflecting the operation of managed NEs or the UME system,
which may not affect services. Maintenance engineers cannot acknowledge or clear notifications.

Alarm Severities
 Alarms can be divided into the following four levels of severity: critical, major, minor, and
warning.
Alarm Level Description
Critical Critical: faults severely affect services, and must be cleared immediately.
Major Major: faults that affect services, and must be cleared urgently.
Minor: faults with no affect on services, but error correction measures must
Minor
be taken to avoid severe faults.
Warnings mean that potential faults exist in the system, which may affect
Warning services. Diagnosis and corrective measures must be taken to prevent the
faults from becoming severe faults that affect services.

Alarm Status
 Alarm status can be divided

into the following types:
 Unacknowledged and uncleared.
 Acknowledged and uncleared.
 Unacknowledged and cleared.
 Acknowledged and cleared.

Alarm Management Page
 Log in to the UME page.

 Enter the IP address (for example,
https://IP:PortNumber/uportal)
of the UME system in the address
bar of a browser, and press the
Enter key.
 Select Alarm Management.

Alarm Management Page 1. Shortcut menu bar
2. Alarm Monitor bar
 The Alarm Monitor page is displayed: 3. Navigation bar
1
3
Alarm Management Module
 Monitoring Alarms: Maintenance engineers query alarms.

 Handling Alarms: After resolving faults in accordance with alarm information,
maintenance engineers acknowledge, clear, and forward alarms as needed.
 Managing Alarms: Maintenance engineers export alarms, and set scheduled statistics
tasks and scheduled export tasks.
 Setting Alarms: Maintenance engineers redefine alarm levels, colors, and prompt tones,
and set remote notifications and the handling rules of alarms and notifications.

Alarm Types
 Equipment Alarm: such as 198100250 RRU link interrupted, 1 Container Startup Failed.
 QoS Alarm: such as 200201001 DU cell out-of-service.
 Communication Alarm: such as 200201007 Ng link is broken.
 Processing Error Alarm:198092029 The hardware type does not match the
configuration.
 Environment Alarm: such as 198097061 Abnormal temperature.
 UME Alarm: such as 198098261 User password has expired.
 Notification: such as 198098316 Abnormal receiving optical power.

CONTENTS
 Overview
 Alarm Handling
 Alarm Settings
Querying Active Alarms
 On the alarm monitoring page of the UME system, the alarms to be monitored can be
located in any of the following ways:
 Customize query conditions.
 Query alarms by level.
 Query alarms in accordance with the existing conditions.

Customizing Query Conditions
1. On the navigation bar of the Alarm Management page, select Active Alarm > Alarm
Monitor.
2. Click Condition Query:
3. Set one or more query conditions.

4.Click Query.

Querying Alarms by Level
 Perform the following operations to query alarms by level (Critical, Major, Minor, and
Warning).

Querying Alarms by Using the Current Condition
 On the navigation bar of the Alarm Management page, select Active Alarm > Alarm
Monitor. Click Condition Template.
 By default, the system provides three query conditions: Alarm Monitor, Last One Day,
and Last Two Days.
 After the user-defined query conditions are saved,

they are also available in the Conditions list.

Querying Historical Alarms
 Historical alarms refer to the ones that are stored in the historical alarm
database after active alarms are cleared.
 The query historical alarms is in the following ways:
 Customize query conditions.
 Query alarms in accordance with the existing conditions.

 Querying Historical Alarms by

Using Customized Conditions
 1. On the navigation bar of the
Alarm Management page, select
History Alarm > Alarm Query.
 2. Click Advanced and set query
parameters.
 3. Click Query.

 Querying Historical Alarms by Using the Current Condition

 Click Conditions in the upper right corner of the History Alarm > Alarm Query page.

Querying Alarm Details
 This procedure describes how to query the basic information and handling suggestions
of active and historical alarms, alarm Trace Active period, and Relative rules.
 Both active alarms and historical alarms could check the detail information.
Type of the Alarms to be Operation

Queried
Active alarms On the navigation bar of the Alarm page, select Active Alarm > Alarm
Monitor. The Alarm Monitor page is displayed.
Historical alarms On the navigation bar of the Alarm page, select History Alarm >
Alarm Query. The Alarm Query page is displayed.

Querying Alarm Details
 Click the corresponding Detail button;
 On the displayed page, query the alarm

details and handling suggestions.

Querying the Statistics of Active Alarms
 The UME system supports collecting statistics on alarms at different levels by NE and NE
type. This assists maintenance engineers in monitoring the network and current devices.
 On the Alarm Management page, select Active Alarm > Statistics on the navigation bar.

Querying the Statistics of Sites
 On the Alarm Management page, select Active Alarm > Site Statistics on the
navigation bar.

Querying the Statistics of Historical Alarms
 The statistics of historical alarms refer to the summarization of the average duration of
historical alarms or the number of alarm occurrences in accordance with a specific
attribute.
 The UME system supports four types of statistical types:
 basic statistics,
 busy-time statistics,
 important alarm code statistics ,
 fault/fault rates statistics.
 On the Alarm Management page, select History Alarm > Statistics on the navigation bar.
The Statistics page is displayed:

1. Querying Basic Statistics.

 Click Table, Donut, or Bar to change the display form of statistical results.

2. Querying Busy-Time Statistics.

3. Querying Statistics on Important Alarm Codes.
 On the Important Alarm-Code Statistics tab ： Resource, Alarm Code, Time Condition, and More Condition.
 Resource: Select the type of one or more NEs to query.
 Alarm Code: Select an alarm code from the left panel and click the right arrow. An alarm code is selected if
it is displayed in the right panel.
 Time Condition: Select the check box, and specify a time period.

4. Querying Statistics on
Fault/Fault Rates.
 On the Fault/Fault
Rates Statistics tab,
click the Condition
button, to set the query
condition parameters.

Notification Monitor
 The notification monitoring is real-time and the UME notification information can be
viewed immediately. You can refresh and export notifications.
 On the navigation bar of the Alarm Management page, select Notification > Monitor.

Notification Query
 A notification is a prompt message related to an operation or error when the managed

NE or the UME system is working.
 There are two methodes to query the notifications of the UME system:
 Customize query conditions
 Specify an existing condition

Notification Query
 Customizing Query Conditions

 On the navigation bar of the Alarm
Management page, select
Notification > Query
 Click Advanced. The page for setting
advanced query conditions is
displayed.
 Set query conditions .
 Click Query.

CONTENTS
 Overview
 Alarm Handling
 Alarm Settings
Alarm Handling
 After discovering alarms, engineers need to handle them and resolve faults in
accordance with the specified procedure.
 Acknowledging an Alarm.
 Clearing an Alarm.
 Forwarding an Alarm.
 Stop Refreshing Alarms in Real Time.

Acknowledging an Alarm
 When an alarm is acknowledged, it means that this alarm is being handled by the current user, and
other users do not need to pay much attention to it. After an alarm is acknowledged, its status
changes to Ack.
 To cancel an acknowledged alarm, just unacknowledge it. After an alarm is unacknowledged, its
status changes to Unack.
 Select one or more alarms on the current page, Click , change the status of acknowledged alarms to Ack.

Clearing an Alarm
 If an alarm is not cleared after the fault is resolved, it can be manually cleared.
 Verify that the following prerequisites are met before clearing an alarm.
 The alarm cannot be automatically cleared.
 The alarm does not exist on the NE.
 The alarm does not exist in the UME system.
 Clear an alarm: Click the corresponding Clear button.
 Clear multiple alarms: Select these alarms, and click button.

Forwarding an Alarm
 After alarm forwarding rules are defined, the matched alarms can be automatically
forwarded to the specified persons.
 An alarm that is being handled can also be forwarded to the specified persons through
mails and SMS messages manually.
 At the Alarm Monitor page, Click the corresponding ...
button, and then select Forwarding.
 You can select E-mail or Phone or both as the forwarding
type.

Stop Refreshing Alarms in Real Time
 This procedure describes how to stop refreshing alarms in real time. In the menu panel
on the left of the Alarm Management page, select Active Alarm > Alarm Monitor.
 Stop refreshing alarms in real time by setting the Real-time Refresh slider button to On.

CONTENTS
 Overview
 Alarm Handling
 Alarm Settings
Synchronizing Active Alarms
 When the network is interrupted, the alarm data of the UME system may not be consistent with
the one of the NE. The current alarm data of the selected NE can be synchronized to the UME
system through manual synchronization as needed.
 On the navigation bar of the Alarm Management page, select Active Alarm > Synchronization.
 Select one or more NEs to be synchronized. Synchronization of the alarms is for some selected NEs or all the NEs.To
synchronize selected NEs, click the Synchronization button.To synchronize all the NEs, click the All Me Synchronization
button.

Exporting Active Alarms
1. Manually Exporting Alarms

 On the Alarm Management page, select Active Alarm > Alarm Monitor from the function navigation tree.
 Click Export and select Export Selected or Export All.
 Set a file name and a file type (xlsx, CSV, XML, TXT, or HTML).
 Click OK. The file is downloaded to the default folder of the Web browser in the form of a ZIP package.

Exporting Active Alarms
2. Exporting Alarms Periodically-Scheduled Export Tasks

 After scheduled export tasks are executed, the UME system periodically exports matched alarms to files
and uploads these files to the default FTP server.
 Maintenance engineers can create, activate, suspend, or delete scheduled export tasks as needed.

Exporting History Alarms-Scheduled Statistics
 After scheduled statistics tasks are executed, statistics templates are executed at fixed
time intervals, and statistics results are output to the specified directories.
 Scheduled statistics tasks can be executed by day, by week, or by month.
 A scheduled statistics task can be executed only once a day.
 On the navigation bar of the Alarm Management page, select History Alarm >
Scheduled Statistics.

Create New Tasks
 Create a new task:

 Click New.
 Specify Name, Task Time,
Template Name, Status, and
Execution Plan.
 Click OK.

Exporting Notifications
 All notifications on the Monitor and Query pages can be exported to a file of the
specified type.
 The notification monitoring function is real-time and it can show the UME notification
immediately.
 Notifications can be exported on the following two tabs.
 On the navigation bar of the Alarm Management page,
select Notification > Query.
 On the navigation bar of the Alarm Management page,
select Notification > Monitor. The Monitor page is displayed.
 Click Export and select Export Selected or Export All.
Selecting an Export Type.
 Set a file name and a file type (CSV, XML, TXT, or HTML).
 Click OK. The file is downloaded to the default folder of the Web browser in the form of a ZIP package.

CONTENTS
 Overview
 Alarm Handling
 Alarm Settings
Alarm Settings
 Redefine alarm attributes:

 Alarm severity redefine
 Alarm sound-color settings
 Alarm-color settings
 Alarm prompt settings
 Alarm forwarding template settings
 Alarm Auto-Ack task settings
 Alarm Synchronization settings
 Alarm Lock-Alarm settings

Alarm Settings- Redefine Alarm Attributes
 On the navigation bar of the Alarm Management page, select Alarm Settings > Others.
 When the redefine alarm attribute is selected just click it.

Redefine Alarm Attributes-Alarm Severity Redefine
 1. Select a type of alarm to be modified from the drop-down list.

 2. Select a severity (for example, Minor) from the drop-down list in the Modified Severity
column:
 3.Click Save.

Redefine Alarm Attributes- Alarm Sound-color Settings
 The UME system provides default sound and color for different levels of alarms. It can be
default sound or customize sound and color.
2. Sound on/Sound off
1. Sound Reset
3. Color Reset
4. Color Redefine
Redefine Alarm Attributes- Alarm-color settings
1. On the Others page, click the Alarm-Code Settings tab.

2. Select a type of alarm code to be modified from the drop-down list.
3. Select an alarm code to be modified and click Modify in the Operation column.
4. Select an alarm severity from the User-defined Severity drop-down list.
5. Enter a name in the User-defined Alarm Code Name text box. Click OK.

Redefine Alarm Attributes- Alarm prompt settings
1. On the Others page , click the Prompt

Settings tab.
2. New: Create an alarm prompt task.
3. Activate: Activate an alarm prompt task.
4. Suspend: Suspend an alarm prompt task.
5. Delete: Delete an alarm prompt task.
6. Modify: Modify an alarm prompt task.

Checking Alarm Prompts
1. Set alarm prompt rules on the Prompt Settings tab as required.

2. On the Alarm Management page, select Active Alarm > Alarm Prompt. The list of the
alarms that meet the alarm prompt rules is displayed.

Redefine Alarm Attributes- Alarm Forwarding Template Settings
1. On the Others page, click the

Forwarding Template tab.
2. In the E-mail area, set Title and
Content. In the SMS area, set Content. To
use the default template, click the Default
button.
3. Click Check. If an item is successfully
checked, a mark is displayed behind
the corresponding text box. If an item
fails the check, modify it until a mark is
displayed. Click OK.

Redefine Alarm Attributes- Alarm Auto-Ack Task Settings
1. On the Others page, click the Auto-Ack Task Settings tab.

2. Click Settings to set the number of days for automatic acknowledgment of historical
alarms.

Redefine Alarm Attributes- Alarm Synchronization Settings
 Synchronization settings include periodical

synchronization settings and automatic
synchronization settings.
 Period Synchronization Settings: Click the
Activate button.Click OK to enable periodical
synchronization.
 Auto Synchronization settings: Click the Activate
button.Click OK to enable Auto synchronization.

Redefine Alarm Attributes- Alarm Lock-Alarm Settings
 On the Others page , click the Lock-Alarm Settings tab.

 After Cleared unacknowledged alarm as active alam is selected, the alarms in this status
are called locked alarms.
 Click Save.

Setting Alarm Handling Rules
 Automatic alarm handling means that the UME system automatically triggers an alarm
handling operation when a specified alarm or notification meets particular conditions.
 Alarm visible filtering
 Alarm acknowledging • Alarm raised filtering
• Alarm delaying
 Alarm clearing • Alarm persisting
 Alarm masking • North filtering
• Repeated history alarm
 Intermittent alarm filtering
 Notification filtering • Repeated-notification
filtering
 Alarm forwarding • Alarm merging
 On the navigation bar of the Alarm Management page, select Alarm Settings > Rule
Settings.

Setting an Alarm Suppression Plan Task
 A suppression plan task is to manage the alarms

generated during engineering cutover and switchover.
During the execution of a suppression plan task, if an
alarm that meets the task conditions is reported, the
system generates an alarm as a root alarm and uses the
reported alarm as a derived alarm of the root alarm.
 On the Alarm Monitor page, select Alarm Settings >
Suppress Plan.

CONTENTS
 Overview
 Alarm Handling
 Alarm Settings
Transmission Faults
 The link between the server and the ME is broken.
 [Alarm Cause Analysis]

1. The physical optical interface or optical fiber is abnormal.
2. The board is not started properly, the board version is not operating properly, or the data
configuration is incorrect.
3. Transmission network problems.

Transmission Faults
 Ng Link is Broken.

1. The physical optical interface or optical fiber is abnormal.
2. The board is not started properly, the board version is not operating properly, or the data
configuration is incorrect.
3. Transmission network problems.
Transmission Faults
【 Troubleshooting 】
1. Check whether the VSW board is powered on
and is operating properly through the board
indicators.
2. Judge whether the physical optical interface

and optical path are normal through the ETH1\
ETH2 port indicator.
3. Check SCTP and Servicemap 5G Parameters.
4. Ping Test destination IP ( UME IP, AMF IP,

UPF IP ).

Transmission Faults
 AAU Link Disconnection

 In most cases, AAU link disconnection is caused by AAU power-off or optical path fault. If
there is an AAU link disconnection alarm, confirm that the VBP board is running normally,
and then go to the site for handling.
1. Check whether the AAU is powered on, and then observe the status of the optical
interface indicator of the VBP board.

Transmission Faults

2. Verify that the optical module model is correct.
The optical module model includes single-mode and multi-mode, whether the transmission distance, central
wavelength and transmission rate meet the requirements, and whether the optical modules at the VBP side and
AAU side are of the same model.

Transmission Faults

3. Check Configuration Parameters.

Cell Faults
 DU cell out-of-service.

1. Cell is blocked or shutdown caused by system policies.

Cell Faults
2. GNSS Fault, if less than 4 satellite locked,the cell out of service fault may occur.
 GPS signals work in the 1575.42 MHz ± 1.023 MHz frequency band. If this frequency band is
interfered with, the receiver cannot work normally.

Cell Faults
3. Check configuration parameters.(template format and network slice).

Network Slice Parameters Checking
 Network slice information on the wireless side, so it must be the same as that configured on the core network.
 The sd parameter of the network slice is carried in the sD field in the Initial Context Setup Request sent by the core
network to the siteThe hexadecimal 010101 is converted into the decimal 65793. After the sd value is modified
correctly, the cell status is normal.
Other Faults
 Board fault:
 Board faults are mainly caused by power supply faults, equipment room environment faults,
improper operations, aging hardware faults, or board port faults.
 Power supply problems and equipment room environment problems can be avoided through
power supply troubleshooting and routine maintenance of the equipment room.
 Improper operations can be avoided by standardizing operations and reducing errors.
 Hardware aging can be prevented in advance through periodic maintenance.
 A board port fault refers to a board fault caused by the damage of one or more ports. After
troubleshooting the external device connected to the port, you can replace the port to
determine whether the original port is damaged. If the port is damaged, replace the port or
interface board.

Thank you!

06 ElasticNet UME Alarm Management and Cases - P70

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

06 ElasticNet UME Alarm Management and Cases - P70

Uploaded by

Copyright:

Available Formats

ElasticNet UME Alarm Management and

 Alarms are an information source

The alarm management principles of the UME system

© ZTE All rights reserved

 Alarms: An alarm reports an exception during NE or UME operation, so that

Differences Between Alarms and Notifications:

© ZTE All rights reserved

Alarm Level Description

© ZTE All rights reserved

 Alarm status can be divided

© ZTE All rights reserved

 Log in to the UME page.

© ZTE All rights reserved

 Monitoring Alarms: Maintenance engineers query alarms.

© ZTE All rights reserved

© ZTE All rights reserved

© ZTE All rights reserved

3. Set one or more query conditions.

© ZTE All rights reserved

© ZTE All rights reserved

 After the user-defined query conditions are saved,

© ZTE All rights reserved

© ZTE All rights reserved

 Querying Historical Alarms by

© ZTE All rights reserved

 Querying Historical Alarms by Using the Current Condition

© ZTE All rights reserved

Type of the Alarms to be Operation

© ZTE All rights reserved

 Click the corresponding Detail button;

 On the displayed page, query the alarm

© ZTE All rights reserved

© ZTE All rights reserved

© ZTE All rights reserved

© ZTE All rights reserved

1. Querying Basic Statistics.

© ZTE All rights reserved

2. Querying Busy-Time Statistics.

© ZTE All rights reserved

© ZTE All rights reserved

© ZTE All rights reserved

© ZTE All rights reserved

 A notification is a prompt message related to an operation or error when the managed

© ZTE All rights reserved

 Customizing Query Conditions

© ZTE All rights reserved

© ZTE All rights reserved

© ZTE All rights reserved

© ZTE All rights reserved

© ZTE All rights reserved

© ZTE All rights reserved

© ZTE All rights reserved

1. Manually Exporting Alarms

© ZTE All rights reserved

2. Exporting Alarms Periodically-Scheduled Export Tasks

© ZTE All rights reserved

© ZTE All rights reserved

 Create a new task:

© ZTE All rights reserved

© ZTE All rights reserved

 Redefine alarm attributes:

© ZTE All rights reserved

© ZTE All rights reserved