Sjzl20091728-NetNumen M31 (RAN) (V3.10.410) OMC Alarm Code Reference

NetNumenM31 (RAN)Mobile Network Element Management System

OMC Alarm Code Reference

Version 3.10.410

ZTE CORPORATIONZTE Plaza, Keji Road South,Hi-Tech Industrial Park,Nanshan District, Shenzhen,P. R. China518057Tel: (86) 755 26771900Fax: (86) 755 26770801URL: http://ensupport.zte.com.cnE-mail: [email protected]

LEGAL INFORMATION

Copyright 2006 ZTE CORPORATION.

The contents of this document are protected by copyright laws and international treaties. Any reproduction or distribution ofthis document or any portion of this document, in any form by any means, without the prior written consent of ZTE CORPO-RATION is prohibited. Additionally, the contents of this document are protected by contractual confidentiality obligations.

All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE CORPORATIONor of their respective owners.

This document is provided as is, and all express, implied, or statutory warranties, representations or conditions are dis-claimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-in-fringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the use of or reliance on theinformation contained herein.

ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the subjectmatter of this document. Except as expressly provided in any written license between ZTE CORPORATION and its licensee,the user of this document shall not acquire any license to the subject matter herein.

ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.

Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.

The ultimate right to interpret this product resides in ZTE CORPORATION.

Revision History

Revision No. Revision Date Revision Reason

1.0 20090330 First Edition (NetNumenM31 V3.10.410a)

Serial Number: sjzl20091728

Contents

Preface............................................................... i

Overview...........................................................1Overview....................................................................... 1

Fault View ..................................................................... 1

Alarm ....................................................................... 1

Notification ................................................................ 2

Alarm ........................................................................... 2

Alarm Property........................................................... 2

Alarm Code ....................................................... 2

Description........................................................ 2

Severity............................................................ 2

Alarm Type........................................................ 3

Cause ....................................................................... 3

System Impact........................................................... 3

Handling Process ........................................................ 4

Notification .................................................................... 4

Notification Property ................................................... 4

Notification code ................................................ 4

Description........................................................ 4

Importance ....................................................... 4

Notification Type ................................................ 4

Cause ....................................................................... 5

System Impact........................................................... 5

Handling Process ........................................................ 5

Communication Alarm .......................................715010004 Link Broken Between Server and Alarmbox ......... 7

100000 Connection Establishment Error ............................ 8

QoS Alarm .........................................................933575633 QoS Alarm...................................................... 9

Equipment Alarm.............................................11400400 Clock Synchronization Problem ............................11

OMS Alarm ......................................................1315010001 Performance data delayed................................13

15010002 NAF performance data file delayed....................14

15010003 license Alarm .................................................14

200050 Database Disk Usage Overload.............................14

200220 CPU usage of application server overload ..............15

200210 Hard disk usage of application server

overload...............................................................15

200230 Ram usage of application server overload..............16

200250 Directory size exceed the threshold ......................16

200280 The time in which the designated alarm remains

active has expired .................................................16

200290 The time in which the designated alarm remains

unacknowledged has expired...................................17

200270 Frequency of warnning overload...........................17

200070 Storage Capacity Problem ...................................18

200260 User continuously input invalid password while

logining................................................................18

Preface

Purpose This manual introduces the OMC alarm and notification informationof ZTE NetNumenM31(RAN) (V3.10.410) Mobile Network ElementManagement System.

This manual is intended as a reference for O&M personnel whoperform operations on NetNumenM31(RAN).

What is in ThisManual

TABLE 1 CHAPTER SUMMARY

Chapter Summary

Chapter 1 Overview Covers the concept offault management ofNetNumenM31(RAN) MobileNetwork Element ManagementSystem, as well as the definition,type, level classification of alarmand notification.

Chapter 2 Communication Alarm Covers the OMC communicationalarm and notification informationof NetNumenM31(RAN) MobileNetwork Element ManagementSystem.

Chapter 3 QoS Alarm Covers the OMC QoS alarmand notification informationof NetNumenM31(RAN) MobileNetwork Element ManagementSystem.

Chapter 4 Equipment Alarm Covers the OMC equipmentalarm and notification informationof NetNumenM31(RAN) MobileNetwork Element ManagementSystem.

Chapter 5 OMS Alarm Covers the OMC OMS alarmand notification informationof NetNumenM31(RAN) MobileNetwork Element ManagementSystem.

Confidential and Proprietary Information of ZTE CORPORATION i

NetNumenM31 (RAN) OMC Alarm Code Reference

This page is intentionally blank.

ii Confidential and Proprietary Information of ZTE CORPORATION

C h a p t e r 1

Overview

Table of ContentsOverview........................................................................... 1Fault View ......................................................................... 1Alarm ............................................................................... 2Notification ........................................................................ 4

OverviewFault management is responsible for collecting information of fail-ures and events that occur during system operation or service pro-cessing. The information, in the form of alarm or notification, isstored in database or displayed on realtime basis via a user-ori-ented fault monitoring platform. Means such as visual-interfacemonitor or history information query can be used to view currentor historical system operation and service processing status. Faultmanagement enables maintenance personnel to troubleshoot andtake preventive measures to remove potential fault and restoresystem and service as early as possible,

Fault ViewFault is displayed in the form of alarm or notification.

Alarm

The fault that persists during system operation and affects systemreliability and normal services is referred to as an alarm. Alarmusually lasts until fault removal.

Due to its possible impact on normal system operation, alarm re-quires timely troubleshooting in which alarm cause is identified,and the fault is located and handled.

Confidential and Proprietary Information of ZTE CORPORATION 1


Notification

Notification refers to the non-repeated/instantaneous fault orevent that occurs during system operation. Examples includeboard reset, signaling overload, etc.

Notification is mostly caused by sudden environment changeor other accidental factors. No special handling is required forthe notification, which can be automatically removed by thesystem. Only the notification that occurs persistently requirestroubleshooting.

Alarm

Alarm Property

Alarm Code

Alarm code is the identifier which differentiates alarms.

Alarm code is defined by a 32-bit field indicating the specific codevalue.

Description

Alarm description reflects such content as fault cause and faultphenomenon in a simple and straightforward way.

Severity

There are four alarm levels, which are indicated in descending or-der of severity as Critical, Major, Minor, and Warning.

Critical alarm causes system breakdown and service interrup-tion. It requires immediate troubleshooting.

Major alarm significantly affects system operation or weakensnetwork service capability. It requires troubleshooting as soonas possible.

Minor alarm affects system operation and network servicecapability in a nonsignificant way. It requires timely trou-bleshooting so as to avoid severity escalation.

Warning poses a potential hazard to system operation and net-work service capability. It requires troubleshooting at an ap-propriate time so as to avoid severity escalation.

2 Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1 Overview

The degree of impact as described in the definition of alarm sever-ity refers to the impact of a single index, such as reliability andsecurity. Once the impact on any of the index reaches the speci-fied threshold, the severity level of the alarm can be roughly de-termined. If an alarm has an impact on multiple indices, alarmseverity should be escalated accordingly.

Note:

Alarm severity can be modified in NetNumenM31 network man-agement system if necessary.

Generally speaking, the default alarm severity is reasonably set.Users should think twice before making any modification.

In addition, the severity of few alarms is undefined. It is up tousers to define the severity of such alarms.

Alarm Type

Alarm is classified into six types according to alarm trigger condi-tion and its system impact.

Equipment alarm: related with device hardware.

Communication alarm: related with information transmission(ITU-T Recommendation X.733).

Processing alarm: related with software or process fault (ITU-TRecommendation X.733).

Environment alarm: related with the environment where theequipment is located (ITU-T Recommendation X.733).

QoS alarm: related with degradation of service quality (ITU-TRecommendation X.733).

OMS alarm: related with the network management system.

Cause

Possible alarm causes are enumerated to help users troubleshoot,find preventive measures, and restore the system to normal statein a timely manner.

System Impact

System impact refers to the impact that the alarm incurs on sys-tem or services.



Handling Process

Troubleshooting measures and suggestions are provided.

Pay attention to the following tips when handling alarms.

After recording the fault phenomenon, O&M personnel mayhandle the fault step by step as described in the handlingprocess section of this manual. If the fault is removed(alarm restored) at any handling step, terminate the handlingprocess. If the fault is not removed, go ahead to the nexthandling step.

If the fault cannot be removed, contact the local ZTE office assoon as possible.

Notification

Notification Property

Notification code

Notification code is the identifier to differentiate notifications.

Notification code is defined by a 32-bit field indicating the specificcode value.

Description

Notification description reflects such content as fault cause andfault phenomenon in a simple and straightforward way.

Importance

There are two levels of notification importance: Important andOrdinary.

Notification Type

No notification type exists.


Chapter 1 Overview

Cause

Possible notification causes are enumerated to help users trou-bleshoot, find preventive measures, and restore the system tonormal state in a timely manner.

System Impact

System impact refers to the impact that the notification incurs onsystem or services.

Handling Process

Troubleshooting measures and suggestions are provided.

Pay attention to the following tips when handling notifications.

After recording the fault phenomenon, O&M personnel mayhandle the fault step by step as described in the handlingprocess section of this manual. If the fault is removed at anyhandling step, terminate the handling process. If the fault isnot removed, go ahead to the next handling step.

If the fault cannot be removed, or the system normal operationcannot be restored, contact the local ZTE office as soon aspossible.


C h a p t e r 2

Communication Alarm

Table of Contents15010004 Link Broken Between Server and Alarmbox ............. 7100000 Connection Establishment Error ................................ 8

15010004 Link BrokenBetween Server andAlarmbox

Alarm Property Alarm Code: 15010004

Description: Link Broken Between Server and Alarmbox

Severity: Critical

Alarm Type: Communication alarm

Cause Server can not communication with Alarmbox.

System Impact The server fails to send the alarm to the alarmbox. Timely prompt-ing of the alarm via the alarmbox to the user fails.

Handling Process 1. View the alarmbox IP configured at background in fault man-agement. See whether you can ping through using this IP.

If yes, go to 3..

If no, go to 2..

2. Check whether the power-on of the alarmbox is normal.

If yes, go to 3..

If no, start the alarm box. See whether the alarm is re-stored after startup of the alarmbox.

3. Check the alarmbox screen to see whether the alarmbox IPand the IP configured at background is consistent.

If yes, go to 4..

If no, modify the alarmbox IP configured at background.See if the alarm is restored after modification.

4. Check the alarmbox screen to see whether the server IP andthe IP configured at background is consistent.

If yes, go to 5..



If no, modify the server IP configured at alarmbox. See ifthe alarm is restored after modification.

5. Check the alarmbox screen to see whether the configured portNo. is correct. If not correct, modify the configured port No.at alarmbox. See if the alarm is restored after modification.

100000 ConnectionEstablishment Error


Description: Connection Establishment Error

Severity: Critical

Alarm Type: Communication alarm

Cause Link to NE is broken

System Impact The system impacts that corresponds to the alarm causes is asfollows.

1. The link between MINOS and OMM is broken, affecting infor-mation transmission.

2. The alarm fails to be sent to the alarmbox.3. Message report of the northbound interface cannot be normally

received.4. NE Performance data and alarms fail to be reported.

Handling Process Check the link.


C h a p t e r 3

QoS Alarm

Table of Contents33575633 QoS Alarm.......................................................... 9

33575633 QoS AlarmAlarm Property Alarm Code: 33575633

Description: QoS Alarm

Severity: Un-Defined

Alarm Type: QoS alarm

Cause Alarm for the out of threshold bound

System Impact QoS alarm is correlated with KPI index. The KPI index where thealarm is generated can be located according to alarm details. Theindex where QoS alarm is generated can be user-defined. The im-pact of the alarm on service varies depending on the correspond-ing KPI index. The system impact of the alarm should be analyzedbased on the specific index.

Handling Process The handling differs depending on the specific KPI index. For thedetailed definition of KPI index, please refer to the performanceindex reference manual. In the manual, all indices are definedand their corresponding trigger causes are described.

Remark Defined by user.


C h a p t e r 4

Equipment Alarm

Table of Contents400400 Clock Synchronization Problem ................................11

400400 ClockSynchronization Problem


Description: Clock Synchronization Problem

Severity: Minor

Alarm Type: Equipment alarm

Cause Clock Synchronization Problem

System Impact Frame loss or link interruption occurs.

Handling Process Check the link with SNTP server. Synchronize manually if the linkis normal.


C h a p t e r 5

OMS Alarm

Table of Contents15010001 Performance data delayed ...................................1315010002 NAF performance data file delayed........................1415010003 license Alarm .....................................................14200050 Database Disk Usage Overload ................................14200220 CPU usage of application server overload ..................15200210 Hard disk usage of application server overload ...........15200230 Ram usage of application server overload..................16200250 Directory size exceed the threshold ..........................16200280 The time in which the designated alarm remains ac-tive has expired ................................................................16200290 The time in which the designated alarm remains un-acknowledged has expired ..................................................17200270 Frequency of warnning overload...............................17200070 Storage Capacity Problem .......................................18200260 User continuously input invalid password while login-ing ..................................................................................18

15010001 Performance datadelayed


Description: Performance data delayed

Severity: Warning

Alarm Type: OMS alarm

Cause Performance data delayed

System Impact Performance data fail to be stored in the database. The perfor-mance data generated during the delay period are unavailable.Creation of customer report form would also be affected if the dataof this period are the required data in customer report.

Handling Process 1. Check the status of measure tasks.2. Check the status of OMMs data acquisition.



15010002 NAF performancedata file delayed


Description: NAF performance data file delayed

Severity: Warning


Cause NAF performance data file delayed.

System Impact NAF performance data file fails to be created, affecting the reportof NAF performance data.

Handling Process 1. Check the measurement tasks status.2. Make sure that the data can be found in the NetNumens data

query system.3. Check the message which NetNumen send to NAF in the log.

15010003 license AlarmAlarm Property Alarm Code: 15010003

Description: license Alarm

Severity: Warning


Cause The number of currently systems trx is beyond limit.

System Impact The configuration object whose license quantity exceeds thethreshold fails to be created. For example, if the number oflicenses used by Node B reaches the upper limit, Node B fails tobe created.

Handling Process Update License.

200050 Database DiskUsage Overload


Description: Database Disk Usage Overload

Severity: Warning


Cause Hard disk usage of database server overload.


Chapter 5 OMS Alarm

System Impact Related with the user-configured threshold and the hard-disk ca-pacity of the database server, the alarm indicates that the availablespace of the hard disk of database server is insufficient. As a re-sult, the information required to be saved in the database mightbe lost or fail to be saved.

Handling Process Clean up database regularly, and export history data.

200220 CPU usage ofapplication server overload


Description: CPU usage of application server overload

Severity: Major


Cause CPU usage overload.

System Impact CPU usage overload might affect the performance efficiency ofother operations.

Handling Process Please have the system checked by system manager.

200210 Hard disk usage ofapplication server overload


Description: Hard disk usage of application server overload

Severity: Major


Cause Hard disk usage overload.

System Impact The available space of the alarm hard disk reduces.

Handling Process Please have the system checked by system manager, or increasehard disk capacity.



200230 Ram usage ofapplication server overload


Description: Ram usage of application server overload

Severity: Major


Cause Ram usage overload.

System Impact The over-utilization of RAM affects the performance of the systemor other operations.

Handling Process Please have the system checked by system manager, or increaseRAM.

200250 Directory sizeexceed the threshold


Description: Directory size exceed the threshold

Severity: Major


Cause Directory size exceed the threshold.

System Impact The directory files take too much hard disk space, so the availablespace left diminishes. As a result, the information required to besaved in the database might be lost or fail to be saved.

Handling Process Please have the directory cleaned by the system manager.

200280 The time in which thedesignated alarm remainsactive has expired


Description: The time in which the designated alarm remainsactive has expired

Severity: Un-Defined



Chapter 5 OMS Alarm

Cause The time in which the alarms under specified conditions remainunrestored or uncleared has expired.

System Impact The designated alarm remains active for too long, which mightresult in abnormity in system operation.

Handling Process Please handle and restore the original alarm timely according toits causes.


200290 The time in whichthe designated alarmremains unacknowledgedhas expired


Description: The time in which the designated alarm remainsunacknowledged has expired

Severity: Undefined


Cause The time in which the alarms under specified conditions remainunacknowledged has expired.

System Impact The designated alarm remains unacknowledged for too long, whichmight result in abnormity in system operation.

Handling Process Please acknowledge the original alarm, or handle and restore ittimely according to its causes.


200270 Frequency ofwarnning overload


Description: Frequency of warnning overload

Severity: Undefined


Cause Frequency of the warning of specified alarm code and specifiedposition overload.

System Impact The specified alarm occurs too often, which might result in abnor-mity in system operation.



Handling Process Please find the reason of warning, depress the frequency of warn-ing.


200070 Storage CapacityProblem


Description: Storage Capacity Problem

Severity: Undefined


Cause Storage Capacity Problem.

System Impact The available storage space of the database is insufficient. As aresult, information saving in the database might fail, and data lossmight occur.

Handling Process Clean up database regularly, and export history data. Or increasedatabase size.


200260 User continuouslyinput invalid password whilelogining


Description: User continuously input invalid password whilelogining

Severity: Critical


Cause User continuously inputs invalid password while logining.

System Impact The account is locked.

Handling Process User has been locked. Please contact your Administrator.


Preface1 OverviewOverviewFault ViewAlarmNotification

AlarmAlarm PropertyAlarm CodeDescriptionSeverityAlarm Type

CauseSystem ImpactHandling Process

NotificationNotification PropertyNotification codeDescriptionImportanceNotification Type

CauseSystem ImpactHandling Process

2 Communication Alarm15010004 Link Broken Between Server and Alarmbox100000 Connection Establishment Error

3 QoS Alarm33575633 QoS Alarm

4 Equipment Alarm400400 Clock Synchronization Problem

5 OMS Alarm15010001 Performance data delayed15010002 NAF performance data file delayed15010003 license Alarm200050 Database Disk Usage Overload200220 CPU usage of application server overload200210 Hard disk usage of application server overload200230 Ram usage of application server overload200250 Directory size exceed the threshold200280 The time in which the designated alarm remains active has200290 The time in which the designated alarm remains unacknowle200270 Frequency of warnning overload200070 Storage Capacity Problem200260 User continuously input invalid password while logining

Sjzl20091728-NetNumen M31 (RAN) (V3.10.410) OMC Alarm Code Reference

Documents

Transcript of Sjzl20091728-NetNumen M31 (RAN) (V3.10.410) OMC Alarm Code Reference