nokia full mmi command with detail

7/28/2019 Nokia Full MMI Command With Detail

1/9

MML Commands MSC/HLRAB - Blocked Alarms HandlingAC - Alarm CancellingAE - Error Ratio Counter HandlingAH - Alarm History HandlingAL - Lamp Panel HandlingAO - Alarm Operating Instruction HandlingAP - Alarm Parameters HandlingAR - Alarm System Rulebase HandlingAT - Alarm PrintingCA - Attribute-Directed RoutingCE - Circuit State HandlingCF - MSC/VLR Digit Analysis HandlingCG - HLR Digit Analysis HandlingCI - Internal Routing StatesCL - Calling Line Identity HandlingCM - Charging Modification HandlingCP - Call Control Parameters HandlingCR - External Circuit Group and Route StatesCT - Call Handling Time SupervisionCU - USSD Analysis Handling (HLR and MSC)CW - Extended Preanalysis HandlingCY - HLR General Analysis HandlingDA - Internal Communication Channels Handling

DB - Database HandlingDC - Clock HandlingDD - Remote Debugger SessionDE - File Conversion HandlingDF - Memory File HandlingDM - Interrogation of LAPD and SBUS Statistics MetersDN - Data Link Connection Data and State HandlingDO - Operating System Supervision and Statistics HandlingDP - Preprocessor Memory HandlingDR - Synchronization Unit HandlingDS - Primary Rate Access D-Channel Data HandlingDT - Primary Rate Access D-Channel State HandlingDU - Disk Update Handling

DW - PRIMARY RATE ACCESS D-CHANNEL FOR IUA DATA HANDLINGE2 - Radio Network Controller Parameter Handling in MSSE3 - NRI and Pool Area Configuration HandlingED - Cellular Network Controller HandlingEI - Network Location Area Address HandlingEJ - GPRS Network HandlingEK - Zone Code HandlingEL - Location Area HandlingEP - BTS and SA Handling in MSC and MSSGA - Dynamic Data HandlingGB - Hot Billing HandlingGC - Charging Counters Copy HandlingGD - Day Classes Handling

GE - CDR and Report Saving HandlingGG - Change Groups HandlingGJ - Network Charging HandlingGN - Charging Zones HandlingGO - Charging Counter Output HandlingGR - Charging Monitoring HandlingGS - Dynamic Counter HandlingGT - Detailed Charging HandlingI2 - SSH protocol layer handlingIA - MMI System Authority Handling


2/9

IB - I/O File BackupIC - Command Calendar HandlingID - Disk Command File ExecutionIE - Disk File OperationsIF - Virtual Data Storing Device HandlingIG - MML Command Log HandlingII - I/O Configuration HandlingIJ - Master Key HandlingIK - Data Protection Key HandlingIL - Mail HandlingIM - Magnetic Tape HandlingIO - Network User Authority Data HandlingIP - Batch Copy HandlingIQ - Disk Optimization ControlIR - Security Reporting HandlingIS - I/O Device Working StatesIT - Terminal Parameters HandlingIU - Network Element Access Control Data HandlingIV - User Authentication Policy HandlingIW - Disk File and Directory HandlingIX - Disk File Compression HandlingJD - Subscriber Profile Database Configuration Administration HandlingJF - User Plane Topology Data HandlingJG - Media Gateway Data Handling

JH - SIP Parameters Configuration HandlingJI - SIP Address Configuration HandlingJL - Context Manager SettingsJM - Megaco Measurement HandlingJN - Extra FQDN Configuration CommandsJO - Serving Profile Database Subscriber HandlingJP - Common Protocol Parameter HandlingJS - SNMP Platform Data HandlingJU - User Plane Analysis HandlingKI - Special Tools for Advanced ServicesKS - Advanced Service FacilitiesKU - Advanced Service SubscribersM6 - PIC Modification Handling

MA - Authentication Data HandlingMB - Basic Service HandlingMC - Connection Path InterrogationMD - CCBS Data HandlingME - Equipment Identity Register HandlingMG - Operator Determined Barring HandlingMH - Multiple Subscribers HandlingMI - Home Subscriber Identification HandlingMJ - HLR and PLMN Parameter HandlingMK - Closed User Group HandlingML - IMEI Database Interface ControlMN - GPRS Subscriber Data HandlingMO - Virtual Subscriber and Attached IMSI Handling

MP - Private Numbering Plan HandlingMQ - Subscriber-related Intelligent Network ServicesMS - Supplementary Services HandlingMT - Subscriber Trace HandlingMV - Visiting Subscriber Identification HandlingMW - VLR Subscriber and Equipment Trace HandlingMX - VLR and PLMN Parameter HandlingMY - Profile HandlingNA - Global Title Result HandlingNB - Global Title Analysis Handling


3/9

NC - Signalling Link Data HandlingNE - Signalling Network State InterrogationNF - SCCP Data HandlingNG - SCCP State HandlingNH - SCCP Subsystem State HandlingNI - SCCP Calling GT Analysis and Result HandlingNL - Signalling Link State HandlingNM - CCS7 Level 3 Parameters HandlingNN - Signalling Route Set Parameter HandlingNO - Signalling Link Parameter HandlingNP - Service Information Data HandlingNR - Signalling Route Set Data HandlingNS - Signalling Link Set Data HandlingNV - Signalling Route State HandlingOA - IN Protocol Statistics HandlingOB - SCCP Broadcast Status HandlingOC - SCCP Parameter Set HandlingOD - SCCP Screening HandlingOE - IN Protocol Parameter HandlingOF - ISUP Screening Mask HandlingOH - Diameter ConfigurationOI - Management of Traffic Matrix Measurement for MTPOL - Interrogation of Signalling Link Statistics MetersOM - Interrogation of Auxiliary MTP Statistics Meters

ON - Interrogation of Signalling Network Statistics MetersOO - OSI Statistics HandlingOP - MAP Parameter HandlingOS - States of SS7 StatisticsOT - Interrogation of SCCP and TCAP Statistics MetersOV - SS7 Routing Verification Test HandlingOX - MAP and SSAP Measurements HandlingOY - SCTP Configuration HandlingQ2 - IPSec Configuration HandlingQ4 - Key Database HandlingQ6 - IPv6 TCP/IP Stack Configuration HandlingQ8 - IP QoS Configuration HandlingQB - OSI Network Address and NSAP Data Handling

QC - Physical Channel Data HandlingQD - OSI Environment Application Data HandlingQE - OSI Environment Connectionless Network Service HandlingQF - OSI File ServicesQG - Physical Channel Group Data HandlingQH - Ethernet Interface HandlingQK - IP Routing Data HandlingQL - OSI Environment Linkage HandlingQN - O&M Network HandlingQQ - OSI Access Control Data HandlingQR - TCP/IP Stack Data HandlingQS - Physical Channel State HandlingQT - Analog Terminal Data Handling

QV - Virtual Terminal CommunicationQX - X.25 Interface Configuration Parameters HandlingRA - Announcement HandlingRC - Circuit Group HandlingRD - Digit Analysis HandlingRG - Trigger and Service Set HandlingRI - Digit Analysis InterrogationRK - Outgoing Call Barring Analysis HandlingRM - Digit Analysis ModificationRN - Number Modification


4/9

RP - GSM Special Route HandlingRQ - Attribute Analysis HandlingRR - Route HandlingRS - Semipermanent CircuitsRT - Time Controlled RoutingRU - Area Service Number HandlingRV - Origin Analysis HandlingRW - Dialling Preanalysis HandlingRX - End-of-Selection and Function Analysis HandlingSA - Digital Branch Exchange Supplementary ServicesSD - Digital Branch Exchange ChargingSG - PBX Closed User Group HandlingSV - User Equipment Specific Behavior Information Database Management HandlingT2 - Measurement HandlingT6 - Handover Measurement Object List HandlingT8 - CAMEL and SIP Protocol Measurement HandlingTB - Supervision of Circuit Group AvailabilityTC - Supervision of Disturbances (MSC and HLR)TD - Destination Object ListsTE - Supervision of Circuit SeizureTF - Announcement Object ListTG - Circuit Group Object ListsTK - Cell Object ListsTL - Load Observation (MSC)

TM - Traffic MeasurementTN - Control Unit Object ListsTO - Traffic ObservationTP - GSM Measurement Handling (HLR and MSC)TR - Traffic Category Object ListsTT - Supervision of Circuit Seizure TimesTU - Field ReportingTW - Field Reporting of Routing ComponentsUD - Diagnostics HandlingUE - ECU and DSU Routine Test HandlingUF - Echo Canceller HandlingUS - Working State and Restart HandlingW1 - RAB Parameter Handling

W6 - LAN Device Topology Management

Installing an Element ManagementApplicationRBSUSER GUIDECopyright Copyright Ericsson AB 2009. All rights reserved.DisclaimerNo part of this document may be reproduced in any form without the writtenpermission of the copyright owner.The contents of this document are subject to revision without notice due to

continued progress in methodology, design and manufacturing. Ericsson shallhave no liability for any error or damage of any kind resulting from the useof this document.4/1553-LZA 701 6003 Uen A 2009-04-16ContentsContents1 Introduction 11.1 Target Groups 11.2 Prerequisites 12 Overview 3


5/9

2.1 Version Handling 32.2 Start Methods for the EM Applications 33 Installing EM Application 53.1 Supported Client Environment 53.2 Installation Order 53.3 Downloading the EM Installation Package 53.4 Installing the Installation Package 63.5 Using Silent Installation 84 Starting an EM Application 114.1 Handling Addresses in the Connect Window 125 Uninstalling EM Applications 134/1553-LZA 701 6003 Uen A 2009-04-16Installing an Element Management Application4/1553-LZA 701 6003 Uen A 2009-04-16Introduction1 IntroductionThis user guide describes how to install and start an Element Management(EM) Application on a Windows client and how to remove, or uninstall, the EMapplication.An EM application is a tool for managing a node. For each node, one or moreEM applications are available. The EM applications are downloaded from thenode and installed on the client.1.1 Target GroupsThe document is intended mainly for users who want to install and run one or

more EM applications on a standalone client in order to manage a node:InstallationEngineerAn installation engineer uses the Element Manager toinstall a node and bring it into service.Field Engineer A field engineer uses the Element Manager during visitsto a node to perform maintenance, fault-tracing, orrepair activities.1.2 PrerequisitesThe Element Management Applications and the installer require thata Java version 1.5 is installed as the Java Runtime Environment(JRE). It can be obtained by downloading JRE 1.5 from Sun at:http://java.sun.com/products/archive. JRE 1.5 is also called JRE 5.0 and is

included in the JDK 5.0 and J2SE 5.0 packages.Regarding the setup of the EM environment and the O&M infrastructure, seeSecurity for O&M Node Access.4/1553-LZA 701 6003 Uen A 2009-04-16 1Installing an Element Management Application2 4/1553-LZA 701 6003 Uen A 2009-04-16Overview2 OverviewThe following EM applications are available for the RBS: RBS Element Manager RBS Configuration Tools consisting of:?? Integrate RBS?? Modify RBS Equipment Configuration

An EM application must first be installed on the client. This is done bydownloading an EM installation package from the node. The EM installationpackage installs a framework that handles the version handling (see Section2.1 on page 3) and start alternatives for all the EM applications.The process of installing and starting an EM application is divided in thefollowing steps: Downloading and Installing the Element Manager ApplicationsThe EM installation package is downloaded from a web server on the node,to the client, see Section 3 on page 5. The framework for running the EMapplications is then installed on the client.


6/9

Starting an EM ApplicationEach EM application is started by using an icon or start link, see Section2.2 on page 3. Section 4 on page 11 describes what happens when an EMapplication is started.2.1 Version HandlingAn EM installation of a certain software version can be used to connectto nodes with the same or earlier software versions. Version handling isperformed automatically, so that the correct EM version executes for eachnode. The EM installation package only needs to be installed once for eachRBS software release.2.2 Start Methods for the EM ApplicationsDuring installation, select where to create the start icons or start links for theEM applications. Follow the instructions during the installation. The followingoptions are available:4/1553-LZA 701 6003 Uen A 2009-04-16 3Installing an Element Management ApplicationThe start icons for the EM applications can, for example, be installed asspecified below. In the Start menu. On the desktop. In the quick launch bar.All the start icons and start links are connected to the start script for the EMapplication.

4 4/1553-LZA 701 6003 Uen A 2009-04-16Installing EM Application3 Installing EM ApplicationThis section describes how to download the EM installation package andhow to install it.3.1 Supported Client EnvironmentTable 1 on page 5 describes the supported operating system versions.Table 1 Supported Operating System VersionsOperating System VersionWindows Vista, (American) English VersionWindows 2000, Service Pack 2, (American) English VersionWindows XP, (American) English Version3.2 Installation Order

If a new version of the EM installation package needs to be installed onthe client computer, it is important to comply with the following prescribedinstallation order: The EM for an older system version must be installed before an EM for anewer system version. If there is a need to re-install the EM of an earlier node version due to, forexample, an error correction delivery, the EM for a newer system versionmust also be re-installed, afterwards, in order to be able to launch towardsboth old and new nodes.3.3 Downloading the EM Installation PackageThe EM installation package resides on the node and can be downloadedfrom a web page located on the node.The web page can, for example, be found in the following location:

A link for downloading the Element Management installation package isavailable on the web page, see Figure 1 on page 6.4/1553-LZA 701 6003 Uen A 2009-04-16 5Installing an Element Management ApplicationFigure 1 Link for Downloading of the EM Installation PackageTo download the EM installation package, perform the following steps:1. Click the link. A new window is opened and you are asked to save theinstallation package.2. Select a directory and save the installation package.


7/9

3.4 Installing the Installation PackageThe next step is to install the EM Applications on the client by double-clickingthe downloaded file. Information about how to perform the installation isavailable on the web page, by clicking on the View link in the Instructionscolumn next to the download links, see Figure 1 on page 6 .You are guided through the installation by the installation wizard, ElementManagement Applications, see Figure 2 on page 7. The installation is dividedinto steps. Instructions for each step can be found to the right in the window ofthe installation program.6 4/1553-LZA 701 6003 Uen A 2009-04-16Installing EM ApplicationFigure 2 The Start Page in the Installation ProgramTo go to the next step in the installation, click Next. To go back to the previousstep, click Previous.When asked to choose Java Virtual Machine (Figure 3 on page 8), make sureto select a Java Runtime Environment version 1.5. If a correct Java version isinstalled on the client, but not displayed here, click Search for Others to scanthe client for other versions. See Section 1.2 on page 1 for information onhow to obtain the correct Java version.4/1553-LZA 701 6003 Uen A 2009-04-16 7Installing an Element Management ApplicationFigure 3 Choose Java Virtual Machine page

As the last step before the installation starts a Pre-Installation Summary isdisplayed. Click Install to start the installation.3.5 Using Silent InstallationA silent installation can be used to install the EM Applications. This enablesan installer program to execute automatically in the background, not visible tothe user. You must first set the variables to be used by the installer program inthe properties file. The installer program automatically looks in the directoryin which it resides for a file called installer.properties. You can alsospecify a properties file for the installer to use by specifying the followingcommand line option:-f /path/to/properties fileThe following variables must be set when running in silent mode:

INSTALLER_UI set the variable to silent, to invoke the silentinstallation. USER_INSTALL_DIR set the variable to the directory where the EMApplications are to be installed. An Ericsson folder will be appended toyour input during installation. APP_JAVA_EXEC points to the JRE to be used by the installedapplications.8 4/1553-LZA 701 6003 Uen A 2009-04-16Installing EM ApplicationOnly a complete install can be performed during silent mode. This means thateverything in the installation package will be installed on the client.Application shortcuts will be placed in the Start menu under the Program GroupEM Applications.

INSTALLER_UI=silentUSER_INSTALL_DIR=C:\\Documents and Settings\\useridAPP_JAVA_EXEC=C:\\Java\\j2re1.5.0_12\\bin\\java.exeExample 1 Contents of the properties file4/1553-LZA 701 6003 Uen A 2009-04-16 9Installing an Element Management Application10 4/1553-LZA 701 6003 Uen A 2009-04-16Starting an EM Application4 Starting an EM ApplicationStart an EM application by using a start icon or link, see Section 2.2 on page 3


8/9

.The location of the start icon or start link is selected during the installation. Tostart an EM Application, perform the following steps:1. Use the start link or start icon created on your client to start the EMapplication.2. The Connect to Network Element window is displayed, see Figure 4 onpage 11. Enter the address to the node in the Address field or select abookmarked address in the list. This is further described in Section 4.1on page 12.3. Click Connect.4. The software for the EM applications may need to be updated. If an updateis necessary, the new version of the software is automatically downloadedfrom the node.Note: Regarding the setup of the EM environment and the O&Minfrastructure, see Security for O&M Node Access.The EM application is now started and ready to be used.Figure 4 The Connect to Network Element Window4/1553-LZA 701 6003 Uen A 2009-04-16 11Installing an Element Management Application4.1 Handling Addresses in the Connect WindowThe Connect to Network Element window, see Figure 4 on page 11, is usedwhen connecting to a node. The window is displayed after a start link or starticon has been selected to start an EM application. The window contains

two address lists: All Nodes and Favorites, that can be selected from thecorresponding tab control.When selecting a node, the address can be given in the following ways: By searching and selecting the address from one of the lists of addresses.The address then appears in the Address field. Click Connect to connectto the node. By typing the address in the first text field, the Address field, and thenclicking Connect.To save an address in any of the lists, click Add. The address is added to thelist that is currently displayed. It is possible to add a name and a comment tothe address. To remove an address from the currently displayed list, select theaddress and click Remove.To help find an address in the displayed list, a number of sort and search

functions are available. By clicking on each column heading, the contents aresorted in alphanumerical order. Search criteria can be entered in any of the textfields below the table, although the search works in slightly different ways. Characters entered in the Address field are compared character-by-character to the first column of the list, showing only the addresses beginningwith the entered characters. The search function in the Name and Comment fields filters the list contentto the occurrences of those lines containing the entered substring anywherein the respective column. The search is case-insensitive.4.1.1 Preparing an Address ListAn address list can be prepared in advance by scripting. The address list isstored in the file, /Ericsson/visited.dat. The favorites list

is stored in visited_favorites.dat in the same directory.The format is: , seeExample 2 on page 12. The name and comment fields are restricted toprintable characters except semicolon (;). The address must not contain spaceor semicolon. Each line is delimited by carriage return, CR, and line feed, LF.125.126.127.128 test RBS; 3 Main Street, Ns125.124.125.126 RXI 126; NorrtljeExample 2 Example of the Address List Format in visited.dat12 4/1553-LZA 701 6003 Uen A 2009-04-16Uninstalling EM Applications


9/9

5 Uninstalling EM ApplicationsThis section describes how to uninstall all or selected Element Managementapplications from the client. The uninstallation removes the application andother files that were created during the installation.To uninstall EM applications, perform the following steps:1. Open Add/Remove Programs from the Control Panel by double-clickingon the icon.2. Select EM applications from the list and click Change/Remove.3. The uninstallation wizard, Uninstall Element_Management_Applications,is started, see Figure 5 on page 13.Figure 5 The Start Page in the Uninstallation ProgramYou are guided through the uninstallation by the uninstallation wizard,Uninstall_Element_Management_Applications, see Figure 5 on page 13.The uninstallation is divided into steps. Instructions for each step can be foundto the right in the window of the uninstallation program.To go to the next step in the uninstallation, click Next. To go back to theprevious step, click Previous.As a last step before the uninstallation starts, click Uninstall.4/1553-LZA 701 6003 Uen A 2009-04-16 13