Introduction to BSS Operations and Maintenance NokiaEDU Introduction to BSS Operations and Maintenance Base Station Subsystem Essentials for GSM18 (Flexi and mcBSC) RN28120-V-18 RN28120-V-18 © Nokia 2018 RN28120-V-18 1 Introduction to BSS Operations and Maintenance Copyright and confidentiality The contents of this document are proprietary and confidential property of Nokia. This document is provided subject to confidentiality obligations of the applicable agreement(s). This document is intended for use of Nokia’s customers and collaborators only for the purpose for which this document is submitted by Nokia. No part of this document may be reproduced or made available to the public or to any third party in any form or means without the prior written permission of Nokia. This document is to be used by properly trained professional personnel. Any use of the contents in this document is limited strictly to the use(s) specifically created in the applicable agreement(s) under which the document is submitted. The user of this document may voluntarily provide suggestions, comments or other feedback to Nokia in respect of the 2 contents of this document ("Feedback"). Such Feedback may be used in Nokia products and related specifications or other documentation. Accordingly, if the user of this document gives Nokia Feedback on the contents of this document, Nokia may freely use, disclose, reproduce, license, distribute and otherwise commercialize the feedback in any Nokia product, technology, service, specification or other documentation. Nokia operates a policy of ongoing development. Nokia reserves the right to make changes and improvements to any of the products and/or services described in this document or withdraw this document at any time without prior notice. The contents of this document are provided "as is". Except as required by applicable law, no warranties of any kind, either express or implied, including, but not limited to, the RN28120-V-18 implied warranties of merchantability and fitness for a particular purpose, are made in relation to the accuracy, reliability or contents of this document. NOKIA SHALL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS DOCUMENT or for any loss of data or income or any special, incidental, consequential, indirect or direct damages howsoever caused, that might arise from the use of this document or any contents of this document. This document and the product(s) it describes are protected by copyright according to the applicable laws. Nokia is a registered trademark of Nokia Corporation. Other product and company names mentioned herein may be trademarks or trade names of their respective owners. © Nokia 2018 RN28120-V-18 2 Introduction to BSS Operations and Maintenance Objectives After this module the students must be able to: Explain the principles and control of the BSS software Employ the principles of the BSS MML Apply the principle of BSS equipment state handling Apply the operational principal of handling BSS alarms Describe the functionality of NetAct when applied to the BSS Describe the functionality of the BTS Manager 3 RN28120-V-18 © Nokia 2018 RN28120-V-18 3 Introduction to BSS Operations and Maintenance Content Introduction BSS Software BSS MML BSS Equipment State Handling BSS Alarms NetAct BTS Manager 4 RN28120-V-18 © Nokia 2018 RN28120-V-18 4 Introduction to BSS Operations and Maintenance Introduction • Configuration and integration of NE & Interfaces • Control of Network Element Software • Alarm monitoring • Fault rectification • Gathering of statistics • Report generation OSS (NetAct) BSS MML BTS TCSM BSC BTS MS BTS BTS Manager RN28120-V-18 5 © Nokia 2018 The operation and maintenance of the network in general and the BSS in particular, is usually dependent upon a number of tools, which are used to perform the actions like: • Configuration and integration of Network Elements and Interfaces, • Control of Network Element Software, • Alarm monitoring, • Fault rectification, • Gathering of statistics, and • Report generation. The main tools available for Operations and Maintenance are: • OSS (NetAct), • BSS MML, and • BTS Manager Also, there are other tools available such as Service Terminal, Wireshark etc but these are outside the scope of this presentation. RN28120-V-18 5 Introduction to BSS Operations and Maintenance Content Introduction BSS Software BSS MML BSS Equipment State Handling BSS Alarms NetAct BTS Manager 6 RN28120-V-18 © Nokia 2018 RN28120-V-18 6 Introduction to BSS Operations and Maintenance BSS Software Build/ Software Package • A collection of programs and data files (that is, load modules) operating in a required system: • SW with certain characteristics for certain HW • If one load module change software update • Stored in WDU • MML Command Options: • Create Software Package • Delete Software Package • Backup / copy Software Package • Restore Software Package • Changing Software Package status 7 RN28120-V-18 © Nokia 2018 The rapid development in telecommunications demands equipment that can be easily upgraded to the latest standards and features. Taking the satisfaction of subscribers into account, these upgrades must be possible without major service interruptions. One of the advantages of a computer-controlled exchange is that new telecommunication technologies can be easily introduced into an active exchange. To make this possible, little or no replacement of existing hardware is needed. Most of the upgrades are realized by merely modifying or replacing the software. A software Build/Software Package is a combination of programs and data files that provide a defined hardware with defined software versions. Every software package consists of so called load modules. A file that contains code or standard data of one program block or one file block is called a “load module”. The load modules are the smallest objects in the software configuration management and the smallest entities of a package. Software packages are physically stored on hard disks. On these disks, a tree of directories is implemented like on a PC. However, disks of the network elements can have a maximum of three subdirectory levels. The highly developed operation and maintenance system of the DX 200, as well as its RAM-based computer units, lay the foundation for successful software updates. Initiated by MML programs, the software configuration management part of the DX 200 system provides the user with sophisticated means for software updates. RN28120-V-18 7 Introduction to BSS Operations and Maintenance DISK DIRECTORY STRUCTURE ROOT/ Max of 3 subdirectory levels SCMANA Package A Max of 8 created packages Package B Package X SOMAFI Name Status Default flag 1 2 3 4 5 6 7 8 SCMANA: S/W Conf Mgt Dir SOMAFI: S/W Conf Mgt File 8 SOMAFI tells information about every SW package created in the system: - Name - Status - Package-id - Directory - Delivery - Default package RN28120-V-18 © Nokia 2018 DISK DIRECTORY STRUCTURE Disk structure consist of the root and under that software package (package) directories. Usually, each directory contains the data of one SW package. During the change delivery deployment, the files of two SW packages are stored in the same directory. SCMANA (Software Configuration Management Directory) subdirectory contains SOMAFI parameter file. In SOMAFI there is information about created SW-packages. The SCMANA also occurs in the FB package when you take a fallback copy of the backup package. There are two essential software configuration management files that are controlled by the software configuration management: Software configuration management file (SOMAFI) contains management information of all packages created in the system. SOMAFI is common for all packages. It includes eight records of the same size. Each record can contain the administration data of one created software package such as name, directory, status, package-id, etc Software package master list (MAFILE) is a description list of the package’s load modules and files and their versions. Each package has its own MAFILE in BLCODE directory. By using the MAFILE, the user can create a software package RN28120-V-18 8 Introduction to BSS Operations and Maintenance DISK DIRECTORY STRUCTURE Max of 3 subdirectory levels SCMANA Package A ROOT/ Max of 8 created packages BCF_PACK Package X Package B SCMANA TMPDIR BLCODE LFILES MMDIRE CONVPR ASWDIR CDTEMP WEBFIL Only in FB Package MAFILE abcd efgh ijkl mnop ASWDIR contains Work files LIST TMPDIR Auxiliary Directory for SW Package Updating procedure 9 abcd efgh etc. ijkl mnop etc. BLCODE Contains files which load to memories during start up LFILES contains loadable delivery -specific files and databases RN28120-V-18 MMDIRE contains MML program files CONVPR converts programs need for a major SW update (optional) WEBFIL For Web Based Management Of NE (IPA2800) CDTEMP Stores temporary file for Change Delivery © Nokia 2018 DISK DIRECTORY STRUCTURE TMPDIR: The Temporary Directory (TMPDIR) is an auxiliary directory for SW updating procedure. The result of conversions are stored in the TMPDIR. When the update is completed, the directory is deleted. BLCODE: The Boot Loadable Code Directory contains the program code and the MAFILE of a SW package. MMDIRE: The Man Machine Interface System Directory contains MML programs. LFILES: The Loadable Files Directory contains the loadable delivery-specific files and databases of SW package. CONVPR: The Conversion Program Directory contains the conversion programs which are needed for the conversion runs performed during SW updates. ASWDIR: The Application Specific Workfile Directory contains the work files of the applications. Files created by the user or by the software are stored in this directory. CDTEMP: The Change Delivery Temporary File Store is used during the change delivery installation. WEBFIL: This HTTP Server Root Directory and its subdirectories are used for Web Based Management of the network element. RN28120-V-18 9 Introduction to BSS Operations and Maintenance ZWQO:CR; Execution Printout To check if one package is active version or not. This is the Default package. 10 RN28120-V-18 © Nokia 2018 RN28120-V-18 10 Introduction to BSS Operations and Maintenance Status of a Created SW Package Note : the WKS command creates a new package, the status of BU package does not change Fallback copy (WKS) Switch active package (WSS) BU FB Rollback statuses (WSR) Change of status (WSC) Rollback statuses (WSR) Change of status (WSC) Fallback copy (WKS) with parameter FULL NW UT Switch active package (WSS) Rollback statuses (WSR) 11 RN28120-V-18 © Nokia 2018 RN28120-V-18 11 Introduction to BSS Operations and Maintenance BS (BCF) Software in the BSC (OMU) HD ROOT DEFAULT SCMANA PACKAGE A PACKAGE B PACKAGE C BCF_PACK PACK_0 PACK_1 BLCODE MMDIRE LFILES CONVPR ASWDIR PACK_2 PACK_18 Each “PACK_n” subdirectory contains one BS software package. PACK_39 HWDATA 12 RN28120-V-18 © Nokia 2018 RN28120-V-18 12 Introduction to BSS Operations and Maintenance BS (BCF) Software Packages Created in the BSC < ZEWL; MF: MASTER FILE Describes the contents of every BTS SW package LOADING PROGRAM VERSION 15.6-0 BSC3i DX220-LAB 2011-04-01 09:34:47 BUILD-ID TYPE REL VER INITIAL MF NAME SUBDIR CONN ------------------------------------------------------------------------------------------------------------------------------CXM53 C 5.3-0 C BTS_C800.666 /PACK_0 0 EP111 E 1.17-0 E BTS_1110.011 /PACK_1 0 CX511 P 5.1-1 P BTS_C800.468 /PACK_2 0 DF603 DF 6.0-3 D BTS_S602.270 /PACK_3 1 DF70 DF 7.0-91 BTS_S700.159 /PACK_7 0 COMMAND EXECUTED 13 RN28120-V-18 © Nokia 2018 RN28120-V-18 13 Introduction to BSS Operations and Maintenance Answer the question What does SCMANA stands for? 1. Software configuration management files 2. Software configuration management directory 3. Temporary Directory 4. Default Package RN28120-V-18 14 © Nokia 2018 Answer: 2 RN28120-V-18 14 Introduction to BSS Operations and Maintenance Content Introduction BSS Software BSS MML BSS Equipment State Handling BSS Alarms NetAct BTS Manager 15 RN28120-V-18 © Nokia 2018 RN28120-V-18 15 Introduction to BSS Operations and Maintenance Man-to-Machine Interface (MMI) Main Level… ALARM SYSTEM ADMINISTRATION H A .. Command Class Level ALARM HISTORY HANDLING AH. Command Group Level O AHO Command DISPLAY MAIN LEVEL ? ….. DISPLAY MENU A ….. ALARM SYSTEM ADMINISTRATION C ….. ROUTING STATE ADMINISTRATION D ….. SYSTEM SUPPORT AND COMMUNICATION I ….. I/O SYSTEM ADMINISTRATION L ….. BROADBAND ADMINISTRATION N ….. SS7 NETWORK ADMINISTRATION O ….. SUPPLEMENTARY SS7 NETWORK ADMINISTRATION Q ….. O&M NETWORK ADMINISTRATION R ….. ROUTING ADMINISTRATION T ….. TRAFFIC ADMINISTRATION U ….. UNIT ADMINISTRATION W ….. SYSTEM CONFIGURATION ADMINISTRATION Y ….. SYSTEM SUPERVISION Z; …. END DIALOGUE/DESTINATION SELECTION (:) ALARMS CURRENTLY ON 16 RN28120-V-18 © Nokia 2018 Before you can enter MMI commands, you have to open an MML session. You can Before you can enter MMI commands, you have to open an MML session. You can open an MML session only if you have a user identity. Open an MML session a) Enter your user ID when the system asks you to (ENTER USERNAME <). b) Enter your password when the system asks you to (ENTER PASSWORD <). Close an MML session a) Enter Z and a semi-colon (Z;) at the main level To move to the main level, enter Z and a semi-colon (Z;). Terminate an MML session It is not recommended to use this procedure in normal circumstances. It is better to close the MML session instead of terminating it. To terminate the MML session press BREAK. You can also press CTRL-Y: this key combination terminates the session when you are entering your user identity or password or typing a command at the main level; or when you have entered the command class letter or displayed the command class menu. RN28120-V-18 16 Introduction to BSS Operations and Maintenance MML Menu Hierarchy Main Level … Z ; ALARM SYSTEM ADMINISTRATION A .. H ALARM HISTORY HANDLING U .. ZUS U AH . US . O ZUSI AHO USI ZUSI INTERROGATE UNIT STATE AND INFO ALARMS CURRENTLY ON RN28120-V-18 Working state and restart handling I DISPLAY 17 UNIT ADMINISTRATION © Nokia 2018 Repeat an MML command a) Press the 'up' arrow to search for a command Search the command you wish to repeat by pressing the 'up' arrow. b) Execute the command Execute the command by pressing ENTER when the command is displayed after the prompt. Cancel an MML command Select one of the following alternatives: • Interrupt MML command execution When the semicolon has not been given, but all the command parameters have been typed, type the letter 'N'. Thus the command will not be executed, and the command entering procedure returns to the beginning of the command group in question. • Terminate command execution To terminate command execution, press CTRL-Y. RN28120-V-18 17 Introduction to BSS Operations and Maintenance MML Command Syntax Command ZABC : Parameter Block : Parameter Block :; :Parameter, Parameter, ..... , : Parameter Type • Name Defined .. : UNIT = OMU, DEV = LPT : ... or .. : DEV = LPT, UNIT = OMU : ... • Position Defined .. : P1, P2, P3, , P5 : ... Omitted Parameter = DEFAULT RN28120-V-18 18 © Nokia 2018 Enter default values to position-defined parameters Select one of the following alternatives: Separate the parameter from other parameters (,) If other parameters must be entered before the parameter block ends, enter a comma (,) to separate the parameter from the other parameters. Separate the parameter from the following parameter block (:) If the parameter block ends after the parameter, enter a colon (:) to separate the parameter from the following parameter block. Example: Entering default value by giving comma Omit the value of the first parameter in the first parameter block by giving comma: ZIID:,OMU:COMCAL; Example: Entering default value by omitting the values Omit the values of both parameters in the first parameter block and leave the separator (the colon): ZIID::COMCAL; RN28120-V-18 18 Introduction to BSS Operations and Maintenance MML Frequently Used Command Groups ZWS/Q - BSS software handling ZWT – Equipment configuration and management ZWU – Equipment / function unit handling ZUS – Equipment working states ZDT – Information regarding LAPD ZQR/K – BSS IP Information ZAH - Alarms ZEW – BCF software and neighbor information ZDD – Remote login to units and the transcoder RN28120-V-18 19 © Nokia 2018 There are a number of MML commands groups that may be used on a day to day basis. These are as follows: ZWS/Q - BSS software handling ZWT – Equipment configuration and management ZWU – Equipment / function unit handling ZUS – Equipment working states ZDT – Information regarding LAPD ZQR/K – BSS IP Information ZAH - Alarms ZEW – BCF software and neighbor information ZDD – Remote login to units and the transcoder RN28120-V-18 19 Introduction to BSS Operations and Maintenance MML Command Groups - Interfaces SGSN ZOY ZNE ZNF MSS ZFX Gb ZFU BSC MGW ZWG A 20 Ater RN28120-V-18 BS ZER ZDW ZD2 ZOY Abis MS ZEE ZEF Um © Nokia 2018 There are a number of MML commands groups that may be used on a day to day basis for information regarding Interfaces and health Checks. These are as follows: A interface – ZNF, ZNE, ZWG, ZOY Ater interface - ZWG, ZRC Abis Interface – ZER, ZDW, ZD2, ZOY Base Station – ZEE, ZEF Gb Interface – ZFX, ZFU RN28120-V-18 20 Introduction to BSS Operations and Maintenance Modifying a Radio Network Parameter Start Lock Network Object (BTS, TRX) Modify Parameter Influence on involved Network Elements Yes Modify involved NE (eg. MSS,BTS) No Unlock Network Object (BTS, TRX) End 21 RN28120-V-18 © Nokia 2018 Modification of a Radio Network parameter or indeed any parameter will usually require the locking of the object by the operator. In some cases extra steps may also be involved such as modification, locking, denying activation of Network Elements / Interface etc. When the modification is complete the Network Element, Interface or object may be unlocked allowing the modified parameter to take effect. RN28120-V-18 21 Introduction to BSS Operations and Maintenance MML User Interface Exercise 1. Execute the command ZUSI:COMP; 2. How many BCSU’s are there in the system? 3. Execute the command ZUSI:ET#,::; 4. What is the displayed state of the ET? 5. Execute the command ZEEI; 6. How many Base Stations are configured? 7. Execute the command ZNET; 8. What is the Link Set name and how many Links are in the Set? 9. Execute the command ZDTI; and then ZDSB; 10. Which of the two executed commands displays the TEI of the TRX? 22 RN28120-V-18 © Nokia 2018 RN28120-V-18 22 Introduction to BSS Operations and Maintenance Answer the question What are the MML commands for Ater interface? (select all that apply) 1. ZNF 2. ZWG 3. ZNE 4. ZRC RN28120-V-18 23 © Nokia 2018 Answer: 2 and 4 RN28120-V-18 23 Introduction to BSS Operations and Maintenance Content Introduction BSS Software BSS MML BSS Equipment State Handling BSS Alarms NetAct BTS Manager 24 RN28120-V-18 © Nokia 2018 RN28120-V-18 24 Introduction to BSS Operations and Maintenance Unit States Model: Main State Unit State Working (WO) Spare (SP) Blocked (BL) Description “Normal" state of units doing some assigned task in the system Running in hot-standby with its active counterpart (in 2N) idle, waiting for a possible switchover (in N+1) Unit with configured resources needs to be taken off-line Test (TE) Fault is detected : unit does not participate in the operation of the system Diagnostics may be run Separated (SE) Initial state a newly added unit will get Unit needs to be physically removed or replaced 25 RN28120-V-18 © Nokia 2018 RN28120-V-18 25 Introduction to BSS Operations and Maintenance Unit States Model: Sub State Possible Main state Sub State Description Executing (EX) WO, SP, BL, TE Unit has achieved full functionality Restarting (RE) WO, SP, BL Unit start up sequence is in progress Updating (UP) SP Processes are updating data from active unit to achieve hot-standby Idle (ID) BL Unit has finished all operations Out of use (OU) SE Unit is separated but still part of a set of redundant units No hardware (NH) SE Unit is configured but not used, or not even physically present RN28120-V-18 26 © Nokia 2018 All the components that are critical concerning the whole system are backed up. Redundancy is implemented at the functional unit level identified by the recovery system. Some functional units do not have all the states listed above. The working states of the functional units are determined as follows: • The SP state can only exist with replaceable 2N or N+1 redundancy. • The BL state can only exist with complementary N+1 redundancy, and without redundancy. • The SP-RE, BL-RE, and WO-RE states can only exist if the unit can be restarted by using a command. • The SP-UP state can only exist if the unit has a spare unit warm-up (computer units only). RN28120-V-18 26 Introduction to BSS Operations and Maintenance Flexi BSC Unit Redundancy Type Flexi BSC Functional Unit Redundancy principle 27 OMU None MCMU 2N BCSU N+1 GSW 2N ET None EET 2N – or MSP1+1 ETPE / ETPT 2N – or MSP1+1 ETPA 2N (MSP1+1) CLS 2N CLAB 2N SET 2N (MSP1+1) WDU 2N RN28120-V-18 © Nokia 2018 Duplication (2N) If the spare unit is designated for only one active unit, the software in the spare unit is kept synchronized so that taking it in use in fault situations (switchover) is very fast. The spare unit can be said to be in hot stand-by. This redundancy principle is called duplication, abbreviated "2N". Replacement (N+1) For less strict reliability requirements, one or more spare units may also be designated to a group of functional units. One spare unit can replace any unit in the group. In this case, the execution of the switchover is a bit slower, because of the spare unit synchronization (warming) is performed as a part of the switchover procedure. The spare unit is in cold stand-by. This redundancy principle is called replacement, abbreviated "N+1". Load sharing (SN+) A unit group may be allocated no spare unit at all, if the group acts as a resource pool. The number of units in the pool is selected so that there is a certain amount of extra capacity. If a few units of the pool are disabled because of faults, the whole group can still perform its designated functions. This redundancy principle is called load sharing, abbreviated "SN+". None Some functional units have no redundancy at all. This is because a failure in them does not prevent the function or cause any drop in the capacity. RN28120-V-18 27 Introduction to BSS Operations and Maintenance TCSM3i Unit Redundancy Type TCSM3i Functional Unit Redundancy principle TCSM None CLS 2N CLAB 2N ET None EET 2N (MSP1+1) ETPA 2N (MSP1+1) RN28120-V-18 28 © Nokia 2018 Duplication (2N) If the spare unit is designated for only one active unit, the software in the spare unit is kept synchronized so that taking it in use in fault situations (switchover) is very fast. The spare unit can be said to be in hot stand-by. This redundancy principle is called duplication, abbreviated "2N". Replacement (N+1) For less strict reliability requirements, one or more spare units may also be designated to a group of functional units. One spare unit can replace any unit in the group. In this case, the execution of the switchover is a bit slower, because of the spare unit synchronization (warming) is performed as a part of the switchover procedure. The spare unit is in cold stand-by. This redundancy principle is called replacement, abbreviated "N+1". Load sharing (SN+) A unit group may be allocated no spare unit at all, if the group acts as a resource pool. The number of units in the pool is selected so that there is a certain amount of extra capacity. If a few units of the pool are disabled because of faults, the whole group can still perform its designated functions. This redundancy principle is called load sharing, abbreviated "SN+". None Some functional units have no redundancy at all. This is because a failure in them does not prevent the function or cause any drop in the capacity. RN28120-V-18 28 Introduction to BSS Operations and Maintenance mcBSC Unit Redundancy Type mcBSC Functional Unit Redundancy principle OMU None MCMU 2N BCXU N+1 PCUM N+M ETPE N+M ETPA SN+ PTUM 1+1 HDD 2N RN28120-V-18 29 © Nokia 2018 Duplication (2N) If the spare unit is designated for only one active unit, the software in the spare unit is kept synchronized so that taking it in use in fault situations (switchover) is very fast. The spare unit can be said to be in hot stand-by. This redundancy principle is called duplication, abbreviated "2N". Replacement (N+1) For less strict reliability requirements, one or more spare units may also be designated to a group of functional units. One spare unit can replace any unit in the group. In this case, the execution of the switchover is a bit slower, because of the spare unit synchronization (warming) is performed as a part of the switchover procedure. The spare unit is in cold stand-by. This redundancy principle is called replacement, abbreviated "N+1". Load sharing (SN+) A unit group may be allocated no spare unit at all, if the group acts as a resource pool. The number of units in the pool is selected so that there is a certain amount of extra capacity. If a few units of the pool are disabled because of faults, the whole group can still perform its designated functions. This redundancy principle is called load sharing, abbreviated "SN+". None Some functional units have no redundancy at all. This is because a failure in them does not prevent the function or cause any drop in the capacity. RN28120-V-18 29 Introduction to BSS Operations and Maintenance Unit State Transition: ZUSC 2N Redundancy: WO-EX SP-EX TE-EX SE-OU SE-NH N+1 (N+M) Redundancy: WO-EX SP-EX No Redundancy: WO-EX TE-EX SE-NH FCD BL-ID BL-EX RN28120-V-18 30 SE-OU TE-EX SE-OU SE-NH © Nokia 2018 2N 2N Redundancy (duplication) is used when two units are dedicated to a task for which one is enough at any given time. One of the units is always active, that is in the working state. The other unit is kept in the hot stand–by state, the spare state. For example: 2N in Flexi BSC: OMU, GSW, MCMU When a unit is detected faulty, it is taken into the testing state, and the fault location and testing programs are activated. On the basis of the diagnosis, the unit is taken to the separated state, if a fault is detected, or into use automatically, if no fault is detected. If the spare unit is designated for only one active unit, the software in the spare unit is kept synchronized so that taking it in use in fault situations (switchover) is very fast. The spare unit can be said to be in hot standby. This redundancy principle is called duplication, abbreviated "2N". N+1 Replaceable N+1 / N+M Redundancy are used when there is just one or a few spare units for a set of N units of a given type. The spare unit is not used by the applications and is not permanently bound to one of the N active units, but can take over the load of any one of them. When a command–initiated changeover for a replaceable N+1 unit is performed, a pair is made up, the spare unit is warmed up to the hot stand–by state, and changeover takes place without major interruptions. When a unit is detected faulty, it is automatically replaced without interruptions to other parts of the system. For example: N+1 in Flexi BSC: BCSU No Redundancy No Redundancy is needed in cases where the redundancy of a unit would not noticeably increase the overall availability performance of the unit type. RN28120-V-18 30 Introduction to BSS Operations and Maintenance Exercise 1. Display all computer units that are in WO-EX state ________________________________________________________ 2. Select a non used ET PCM and change the state to SE-NH and then back to its original status ________________________________________________________ 3. Select an ET PCM, change the state to TE and perform a diagnostic __________________________________________________ __________________________________________________ __________________________________________________ 4. Output the diagnostic result __________________________________________________ __________________________________________________ 31 RN28120-V-18 © Nokia 2018 RN28120-V-18 31 Introduction to BSS Operations and Maintenance Answer the question Which is the redundancy of SP state? 1. Complementary N+1 2. Nil 3. 2N or N+1 4. 2N RN28120-V-18 32 © Nokia 2018 Answer: 3 RN28120-V-18 32 Introduction to BSS Operations and Maintenance Content Introduction BSS Software BSS MML BSS Equipment State Handling BSS Alarms NetAct BTS Manager 33 RN28120-V-18 © Nokia 2018 RN28120-V-18 33 Introduction to BSS Operations and Maintenance BSC Alarm Handling - Handle in various ways: • MML system - Alarm Cancelling command group <AC_> - Alarm History Handling command group <AH_> • NetAct - Alarm monitor - Alarm Operation • Display active alarm • Display historical alarm • Cancel alarm • Block Alarm 34 RN28120-V-18 © Nokia 2018 Each alarm event, alarm and its cancellation, not filtered by the alarm system, is saved in a log file. This log data is called alarm history. Using the AH command group commands, you can display the history data concerning the system's alarm situation. You can either display the alarm history, or merely the active alarms, on the selected output device. The alarm history can be useful in troubleshooting situations. By analyzing the alarm history data you may be able to find trends or patterns on how and when the alarms occur. RN28120-V-18 34 Introduction to BSS Operations and Maintenance Alarm Urgency Level Alarm Class Notice Disturbance Disturbance is used for informing about temporary disturbance situations, which means informing about a short failure event that does not have any permanent effect on service An alarm or transient disturbance marked with one asterisk does not usually require user actions * ** An alarm marked with two asterisks does not threaten the operation of the system. However, if the fault occurs during working hours, it must be corrected at once. If the fault occurs outside working hours, it can be corrected the next day Alarms marked with three asterisks require immediate action from the user. An alarm like this is set when the system has become faulty to the extent that some essential functionality of the system has stopped, or is in danger of stopping. The maintenance personnel must take immediate action *** 35 Description Alarm which is not cancelled and which only informs about a fault event without printing out the urgency class RN28120-V-18 © Nokia 2018 RN28120-V-18 35 Introduction to BSS Operations and Maintenance Example of Active Alarms Handling : ZAHO AHO:BCSU:CLS=AL2:; 36 RN28120-V-18 © Nokia 2018 RN28120-V-18 36 Introduction to BSS Operations and Maintenance Exercise : Alarm system 1. Display the Alarm System Administration menu. ____________________________________________________ 2. Display the Alarm Parameters Handling menu. ____________________________________________________ 3. Display the menu for Alarm History Handling. _____________________________________________________ 4. Display all alarms currently in the ON state (= active alarms). _____________________________________________________ 5. Display all ** alarms and *** alarms for the OMU’s (active and history) _____________________________________________________ 37 RN28120-V-18 © Nokia 2018 RN28120-V-18 37 Introduction to BSS Operations and Maintenance Exercise: Active alarms and Alarm History Handling 1. By referring to the Alarm Reference Manual, find out which fault causes the alarm with the alarm number 2692? _____________________________________________________ 2. Display all alarms currently in the ON state (= active alarms). _____________________________________________________ 3. Display all ** alarms and *** alarms for the OMU’s (active and history) _____________________________________________________ _____________________________________________________ 38 RN28120-V-18 © Nokia 2018 RN28120-V-18 38 Introduction to BSS Operations and Maintenance Content Introduction BSS Software BSS MML BSS Equipment State Handling BSS Alarms NetAct BTS Manager 39 RN28120-V-18 © Nokia 2018 RN28120-V-18 39 Introduction to BSS Operations and Maintenance NetAct Applications - Functional Areas Administration Configuration Monitoring Reporting Optimization User Assistance Security 40 RN28120-V-18 © Nokia 2018 RN28120-V-18 40 Introduction to BSS Operations and Maintenance Accessing NetAct NetAct Start Page Access the Login Page with address provided by your system administrator. 41 RN28120-V-18 © Nokia 2018 RN28120-V-18 41 Introduction to BSS Operations and Maintenance Accessing NetAct NetAct Start Page NetAct applications are grouped into following categories: Administration Optimization Configuration Reporting Monitoring Security User Assistance Online Help NetAct applications can be launched from NetAct start page. 42 RN28120-V-18 © Nokia 2018 RN28120-V-18 42 Introduction to BSS Operations and Maintenance Accessing NetAct Administration Administration category contains the applications for management of Adaptation, Mediations and NE integrations. 43 RN28120-V-18 © Nokia 2018 RN28120-V-18 43 Introduction to BSS Operations and Maintenance NetAct Applications Categories Security The security management defines the actions, tools and functionalities designed to protect the system and the network against security threads. 44 RN28120-V-18 © Nokia 2018 RN28120-V-18 44 Introduction to BSS Operations and Maintenance NetAct Applications Categories Configuration Configuration management defines the tool for giving access to real-time network configuration, data, and tools to manage network configuration. 45 RN28120-V-18 © Nokia 2018 RN28120-V-18 45 Introduction to BSS Operations and Maintenance NetAct Applications Categories Optimization NetAct Optimizer is designed for automated, measurement based optimization of operational GSM, WCDMA and LTE networks. It provides the functionality for viewing, analyzing and optimizing the actual network performance and capacity. 46 RN28120-V-18 © Nokia 2018 RN28120-V-18 46 Introduction to BSS Operations and Maintenance NetAct Applications Categories Monitoring NetAct Monitor provides tools to manage alarms from different Network Elements, perform root cause analysis, troubleshoot faults in the network services and to improve the quality of the network services for subscribers. 47 RN28120-V-18 © Nokia 2018 RN28120-V-18 47 Introduction to BSS Operations and Maintenance NetAct Applications Categories Monitoring: TraceViewer NetAct Trace Viewer supports the system-level trace functionality that is implemented in various NSN elements throughout the whole network. 48 RN28120-V-18 © Nokia 2018 RN28120-V-18 48 Introduction to BSS Operations and Maintenance NetAct Applications Categories Reporting Centralized Management of NEs Measurements: • Administration of Measurements Network Elements features usage reporting: • Software Asset Monitoring PM Reporting and Monitoring Tools in Performance Manager: • • • • 49 Reporting Suite Saved Reports Report Creator Report Publisher • • • • KPI Creator Scheduler Admin Toolkit Threshold and Profiler RN28120-V-18 Performance Manager is a centralized, multi-vendor, multitechnology data reporting solution. © Nokia 2018 RN28120-V-18 49 Introduction to BSS Operations and Maintenance NetAct Applications Categories User Assistance User assistance provides the user with all the support information required to operate NetAct and the information about counters, traffic measurements, configuration parameters, managed objects and alarms information via the Object Information Browser. 50 RN28120-V-18 © Nokia 2018 RN28120-V-18 50 Introduction to BSS Operations and Maintenance Answer the question Which of the following is NOT the functional area of NetAct Applications? 1. Administration 2. Optimization 3. Deployment 4. Monitoring RN28120-V-18 51 © Nokia 2018 Answer: 3 RN28120-V-18 51 Introduction to BSS Operations and Maintenance Content Introduction BSS Software BSS MML BSS Equipment State Handling BSS Alarms NetAct BTS Manager 52 RN28120-V-18 © Nokia 2018 RN28120-V-18 52 Introduction to BSS Operations and Maintenance BTS Manager Main Window To launch.the 2G Flexi BTS Manager, user can click shortcuts in the Start Menu, and following window will come up : For commissioning/ supervision if PC connect directly to BTS For re-commissioning/ supervision if PC connect BTS via NetAct (remotely) For Snapshot For help List of release package and 2G Flexi BTS Site Manager versions For creating the SCF or EasyWizard templet, if PC connect BTS offline (PC not connected to BTS) List of release package and 2G Flexi BTS Site Manager versions RN28120-V-18 53 © Nokia 2018 The BTS manager is available for control of all variants of the Flexi BTS product range. It should be noted that there are different variants available depending upon SW release and technology, but in essence they are all similar. The main functions of Flexi BTS manager are: • BTS commissioning • BTS supervision • BTS maintenance • BTS testing RN28120-V-18 53 Introduction to BSS Operations and Maintenance BTS Manager Main Window – Local Connection By clicking the Local Connection option, following window opens: IP Address of ESMB/C/FSMF As default, password is not required, just left this box blank. 54 RN28120-V-18 © Nokia 2018 RN28120-V-18 54 Introduction to BSS Operations and Maintenance BTS Manager Main Window – Remote Connection By clicking the Remote Connection option, following window opens: Mandatory to fill 55 RN28120-V-18 © Nokia 2018 RN28120-V-18 55 Introduction to BSS Operations and Maintenance BTS Manager Main Window Create File By clicking the Create File option, following window opens: Release packages and 2G Flexi BTS Site Manager versions 56 RN28120-V-18 © Nokia 2018 RN28120-V-18 56 Introduction to BSS Operations and Maintenance BTS Manager Main Window – Tools By clicking the Tools option, following window opens: Available tools (help for BTS Site Manager) 57 RN28120-V-18 © Nokia 2018 RN28120-V-18 57 Introduction to BSS Operations and Maintenance BTS Manager Main Window – About By clicking the Tool option, the following window appears: List of installed Release packages and 2G Flexi BTS Site manager version 58 RN28120-V-18 © Nokia 2018 RN28120-V-18 58 Introduction to BSS Operations and Maintenance BTS Site Manager Window RN28120-V-18 59 © Nokia 2018 The main functions of Flexi BTS manager are: BTS commissioning, BTS supervision, BTS maintenance, and BTS testing In main menu, the view are: Alarms, Base Station, Commissioning, Supervision, Transmission, and Tests RN28120-V-18 59 Introduction to BSS Operations and Maintenance Answer the question Which of the following is NOT a mandatory field in BTS Manager Main Window – Remote Connection? 1. BSC Username 2. BSC Password 3. BTS Password 4. BTS BCF ID RN28120-V-18 60 © Nokia 2018 Answer: 3 RN28120-V-18 60 Introduction to BSS Operations and Maintenance RN28120-V-18 © Nokia 2018 RN28120-V-18 61