8/9/2019 07 Appendix Dx200 Basics o&m on Flexi Ns Mme

1/31

8/9/2019 07 Appendix Dx200 Basics o&m on Flexi Ns Mme

2/31

8/9/2019 07 Appendix Dx200 Basics o&m on Flexi Ns Mme

3/31

8/9/2019 07 Appendix Dx200 Basics o&m on Flexi Ns Mme

4/31

8/9/2019 07 Appendix Dx200 Basics o&m on Flexi Ns Mme

5/31

8/9/2019 07 Appendix Dx200 Basics o&m on Flexi Ns Mme

6/31

8/9/2019 07 Appendix Dx200 Basics o&m on Flexi Ns Mme

7/31

8/9/2019 07 Appendix Dx200 Basics o&m on Flexi Ns Mme

8/31

Four types of alarms:

notices (0-999)

disturbances (1000-1999) alarms (2000-2999)

error ratio counters

8/9/2019 07 Appendix Dx200 Basics o&m on Flexi Ns Mme

9/31

8/9/2019 07 Appendix Dx200 Basics o&m on Flexi Ns Mme

10/31

8/9/2019 07 Appendix Dx200 Basics o&m on Flexi Ns Mme

11/31

8/9/2019 07 Appendix Dx200 Basics o&m on Flexi Ns Mme

12/31

8/9/2019 07 Appendix Dx200 Basics o&m on Flexi Ns Mme

13/31

Recovery system

-recovery of units and the whole network element

-operating states

Recovery of the whole element

-only in total power lost or in commissioning

- first OMU then 2N units come up (more on the file administration)

8/9/2019 07 Appendix Dx200 Basics o&m on Flexi Ns Mme

14/31

8/9/2019 07 Appendix Dx200 Basics o&m on Flexi Ns Mme

15/31

REDUNDANCY

2N: SAME CODE AND FILE

N+1: SAME CODE, DIFF. FILE->WARM-UP

SE-OU-> Unit is faulty

SE-NH-> When user is changing a PIU

8/9/2019 07 Appendix Dx200 Basics o&m on Flexi Ns Mme

16/31

8/9/2019 07 Appendix Dx200 Basics o&m on Flexi Ns Mme

17/31

8/9/2019 07 Appendix Dx200 Basics o&m on Flexi Ns Mme

18/31

8/9/2019 07 Appendix Dx200 Basics o&m on Flexi Ns Mme

19/31

8/9/2019 07 Appendix Dx200 Basics o&m on Flexi Ns Mme

20/31

8/9/2019 07 Appendix Dx200 Basics o&m on Flexi Ns Mme

21/31

BLCODE: The Boot Loadable Code subdirectory contains the programcode files and parameter files that are loaded first into thecomputer unit's memory when the computer unit starts up

MMDIRE: The MMI system subdirectory contains MML programs andtheir text files

LFILES: The Loadable Files subdirectory contains disk copies ofmemory files, e.g. net elements database

ASWDIR: The Application Specific Work subdirectory is for saving' , . . .

CONVPR: The Conversion Program subdirectory contains the file

conversion programs that are needed to perform softwareupdates

WEBFIL: The files of the WEBFIL subdirectory and its six additionalsubdirectories are needed for the Web Based management ofthe network element and graphical user interface GUI

8/9/2019 07 Appendix Dx200 Basics o&m on Flexi Ns Mme

22/31

There are two essential software configuration management files that are controlledby the software configuration management:

Software configuration management file (SOMAFI) contains managementinformation of all builds created in the system. SOMAFI is common for all builds.

Software build master list (MAFILE) is a description list of the build's load modulesand files and their versions. Each build has its own MAFILE.

The Software configuration Management File (SOMAFI) contains information onsoftware builds created in the exchange.

The SOMAFI is found in the SCMANA directory.

SOMAFI includes eight records of the same size. Each record can contain theadministration data of one created software build.

A build is always accompanied by a Master File (MAFILE), which contains a list ofall load modules of the build together with their version data.

The MAFILE is found in the BLCODE directory.

By using the MAFILE, the user can create a software build. Created software buildscan eventually be loaded into the functional units of the exchange.

Software builds stored into the management system are identified and thusdistinguished from one another by means of the following build specific data:

Application identifier of the build and the version of the build Application identifierof the environment specification and the version of the environment specification

Name of the delivery and the version of the delivery.

In addition to the above, the SW-build can be identified in the network element by aname given to it in the creation.

8/9/2019 07 Appendix Dx200 Basics o&m on Flexi Ns Mme

23/31

8/9/2019 07 Appendix Dx200 Basics o&m on Flexi Ns Mme

24/31

The main procedures for handling SW build statuses are:

Safecopy

Roll-back Status change

Safecopy

A safecopy is a copy of a software package that is kept for reference in case the originalfile or data set is destroyed. During the safecopy procedure, the complete software of thepackage that currently has the status BU is physically copied. This implies that also a newpackage directory tree is created on the disk. The package created during a safecopygets the status FB.

Note that the copying process always gets the files of the package with the status BU.This is not necessaril the current default acka e.

Command to perform a safecopy: ZWKS:....

RollbackThe rollback procedure supports the user to obey the recommendations for softwarepackages. In case of a fault in a BU package, the FB package should be taken into use. Itbecomes a default package and permanently running in the system. However, arecommended running package should be BU. So, status changes have to be performed.With the rollback command:

Status of the FB package is changed to BU Status of the package that functioned as BUis changed to NW. If there is a package with the NW status, it is changed to UT status.During a rollback no software is copied, only statuses are changed.

Command to perform a rollback: ZWSR:

Status change

The user can change the status of software packages with 2 possibilities:

Swap the statuses BU and NW

Name one of the UT packages to attach the status NW to it.

Command to perform a status change: ZWSC:

8/9/2019 07 Appendix Dx200 Basics o&m on Flexi Ns Mme

25/31

8/9/2019 07 Appendix Dx200 Basics o&m on Flexi Ns Mme

26/31

8/9/2019 07 Appendix Dx200 Basics o&m on Flexi Ns Mme

27/31

8/9/2019 07 Appendix Dx200 Basics o&m on Flexi Ns Mme

28/31

8/9/2019 07 Appendix Dx200 Basics o&m on Flexi Ns Mme

29/31

8/9/2019 07 Appendix Dx200 Basics o&m on Flexi Ns Mme

30/31

8/9/2019 07 Appendix Dx200 Basics o&m on Flexi Ns Mme

31/31

MME measurements (TP - Measurement Configuration Handling productdocument)

- Mobility Management Measurement

The Mobility Management Measurement provides information on, for example,successful and failed EPS attaches and detaches, tracking are updates, servicerequests, handovers and paging procedures. The mobility management functions areused to keep track of the current location of a User Equipment (UE) within the PublicLand Mobile Network (PLMN) or within another PLMN. The counters are collected onTracking Area level.

M50C004 / EPS PERIODIC TAU FAIL

M50C006 / EPS TAU FAIL

M50C010 / EPS PATH SWITCH X2 FAIL

- Session Management Measurement

The Session Management Measurement provides information on, for example,successful and failed default bearer activation procedures. The counters arecollected on Tracking Area level.

- MMDU User Level Measurement

The MULM (MMDU User Level Measurement) provides information on users in ECMconnected, ECM idle, EMM registered and EMM deregistered states on MMDU level.Minimum, maximum and average number of users in each state is reported perMMDU. The reported average value is a result of two counters, denominator andsum. The counters are collected on MMDU level.

- User MME Level Measurement

The User MME Level Measurement provides information on users in ECMconnected, ECM idle, EMM registered and EMM deregistered states on MME level.

Maximum and minimum number or users in each state is reported. The counters arecollected on MME level.