Omo000201 Imanager m2000v2 Client o&m for Gbss Issue1.0

No Slide TitleiManager M2000V2
References
Objectives
Upon completion of this course, you will be able to:
Know the system structure of M2000 system
Understand the meaning of some important parameter
Conduct operations on M2000 client
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
Contents
Contents
M2000 software structure
Server Software
Client Software
Before the client software installed, make sure the M2000 server run normally, and the IP connection between server and client is OK.
Preparing M2000 Client software
Uploading Installation Package to M2000 Client from PC or Laptop
Upload the installation package from the PC or laptop to the M2000 client. For example, to the directory c:\ on the M2000 client.
Unzip Installation Package
Double click the installation package iManagerM2000V200R002C03_cli.exe uploaded to the client.
Select the target folder from the popup menu. The setup.bat file is extracted to the target folder.
Contents
Installing M2000 Client Software
Select English from the popup menu, and then click OK.
Click Browse to select the target directory, and then click Next. The default target directory is “C:\iManagerM2000Client”. The target directory must be empty. The system will create the target directory if it does not exist.
Select the installation mode of the localized configuration, and then click Next.
Confirm the displayed parameters to make sure that they meet requirements. If so, click Next. If not, click Previous to modify them.
The installation progress pop up. This process lasts about a few minutes
Enter the IP address of the server connected with the client, and then click Next. You can also set the IP address after you start the client application.
Contents
Checking Installation
Running Client Application
Choose Start -> Programs -> iManager M2000 Client -> M2000 Client to run the M2000 client application.
Logging On M2000 Server
The initial setting of the system is:
User name: admin
This is the super user authorized with all operation authorities.
Checking Installation
Enter the IP address of the server.
Change the password of admin.
Note:
The user password is stored on the M2000 server.
The password is null when the M2000 server is installed for the first time. It has nothing to do with whether the M2000 client is installed for the first time.
Viewing Client Status
After you log in, the client is connected to the specified server, and the topology tree is displayed in the window.
If the connection fails, check M2000 installation and network connections and the communications between client and server.
Contents
Contents
2.2 Topology Management
2.3 Security Management
2.4 Fault Management
2.5 Performance Management
Logging in to the M2000 Client
Prerequisites
The M2000 client and server match in software version.
The M2000 client communicates smoothly with the corresponding M2000 server.
You have the required username and password.
Logging in to the M2000 Client
Select Start > Programs > iManager M2000 Client > M2000 Client to start the M2000 client software.
In the displayed User Login dialog box, enter the M2000 user name, password and the server IP.
Click Login in User Login to log in to the M2000.
Setting Properties of the M2000 Client
To set the following properties of the M2000 client:
Mode for displaying characters
Items displayed in the toolbar
Whether the NE Local Maintenance Terminal (LMT) prompts on user login or logout
Mode for displaying characters
Auto locking period
Items displayed in the toolbar
LMT Prompt setting
Select System > LMT Prompt Setting.
The LMT Prompt Setting dialog box is displayed. You can set whether the NE LMT prompts on user login or logout.
Contents
Monitoring Connection Status of NEs
Introduction to Connection Status
Connected: The O&M path between the NE and the M2000 works smoothly. You can operate on or maintain the NE through the M2000. The NE icon is displayed in the topology view.
Connection down: The O&M path between the NE and the M2000 does not work smoothly, or error occurs to some TCP or UDP ports. In this case, the NE icon in the topology view is attached with at the top left corner.
Introduction to Connection Status
NE not match: The O&M path between the NE and the M2000 works well. However, you cannot operate on or maintain the NE through the M2000 because the adaptation package of the right version is not installed on the NE. In this case, the NE icon in the topology view is attached with at the top left corner.
Synchronization processing: The M2000 is extracting configuration data from the NE. The data synchronization is carried out when the NE is newly accessed to the M2000 O&M due to disconnection. In this case, the NE icon in the topology view is attached with at the top left corner.
Monitoring NE Status in the Topology view
Note: all the icon of the NE type and connection status are list in the topology tree—Legend.
Monitoring NE Status Through the System Monitor Browser
Navigation tree displays the inter-NE connection relations in tree list with the guide of regions. The system reads the region information from MapInfo, and can automatically update according to the change (deleting/adding) of NE.
The map is based on MapInfo vector map technology, and can display the topology information such as NE, virtual NE, BTS, link, office direction, etc.
The navigation tree and the map are interactive. When selecting NE/region in navigation tree, the map will change accordingly; when selecting NE in the map, the node in the navigation tree will also change.
Topology View
The M2000 topology view consists of two parts: the tree and the view:
The navigation tree on the left shows all involved topology objects, such as NEs and subnets, and the hierarchical architecture between these objects.
The topology view on the right shows all the topology objects on the current network and the location relationship among these objects.
The topology supports the display of each NE; the user can directly add/modify/delete the NE and can directly drag the NE in the map.
The topology supports the display of BTS and ODU, and can display the connection between CBSC and BTS, between BTSs, between BTS and ODU.
The topology can display the information of office direction and link, which is automatically acquired from the configuration information by the system and is able to automatically update according to the change of NE information.
The user can create/modify/delete the virtual NE in the system topology interface.
Topology View
The system can display the NE alarm status with the method of alarm lamp, and the number of lamps is corresponding to the different alarm level. If one NE has the alarm with different levels, the system just displays the highest level alarm.
The system can drive audio card and alarm box to sound to prompt the alarm information for the maintenance engineer.
The user can filter the NE to select his concerned NE to perform alarm monitoring.
The system can display link/office direction alarm via flashing line.
Creating NE
To create physical NEs in the physical topology. After you create an NE successfully, the M2000 synchronizes with the NE to obtain the NE configuration.
Click Physical Root in the left of Physical Topology.
Select the subnet for the NE to be created.
Right-click the subnet and select Create NE on the displayed menu.
The system provides electronic map function and support NE precision location.
Support various types of map scales such as country, province, and city street. When the map scale is large, the system can combine the several NEs and process them.
The electronic map support the operations such as zoom, moving, query, etc.
Support the dragging of the NE in topology.
Creating NE
In the displayed window Create NE, select Access Network Series or Core Network Series behind Select Category, and select the type of the NE to be created behind Select NE Type. Click Next.
Creating NE
Enter the name and IP address of the NE, and then click Finish.
The icon for this NE is displayed in the topology view, and meanwhile the system displays the synchronization progression.
Creating NEs in Batches
The M2000 client provides standard templates for creating NEs in batches. The templates are in the INI and CSV formats.
The templates in the INI format apply to all NEs except virtual NEs.
The templates in the CSV template apply only to NEs on the WCDMA network.
Exporting NE Attributes Template
The NE batch creating file is used for creating NEs in batches. You can save the file in two formats: INI and CSV.
Before creating the NE batch creating file in the INI format, ensure that you have obtained the relevant NE data, such as:
NE name
IP address
NE type
Vendor name
Location description
NE description
Select Configuration > Exports NE Attributes Templates > INI file format, and the Exports NE Info template dialog box is displayed.
Select NE types in the left navigation tree for exporting a template.
In the right entry box, enter a name for the template file, and select the path for saving this file. Fill in the information as required.
Save the template in the INI format.
To save a NE batch creating file in the CSV format.
Select Configuration > Exports NE Attributes Templates > CSV file format, and the Exports NE Info template dialog box is displayed.
Creating NE in batches
Right-click the subnet, and select Create Physical NEs in batches on the displayed menu.
The Bulk create NE dialog box is displayed
Select the script file to be created, and then click OK.
Creating Subnets
Right-click and select Create Physical Subnet on the displayed menu.
In the displayed Create Physical Subnet, enter the subnet name, select the background, and select NEs and subnets to be displayed under this subnet. Click OK.
Filtering NEs in the Topology View
To set the physical topology view, so that it shows only objects such as the background, NE, subnet, link and link name.
In Physical Topology, select the tab Filter in the left navigation tree
Modifying the Electronic Map
Right-click in Physical Topology, and select Set BackGround. The Set BackGround dialog box is displayed.
Click Select… to select a new electronic map file
Contents
Security Management
The M2000 security management refers to the management on the users and user privileges. It is an important function of the M2000.
The user management is the key part of the security management. It manages the users, user groups, and NE users.
Both the users and user groups are the M2000 system users. A user group is a group of the M2000 users. A user can belong to one or more user groups.
Creating user
Click System > Security Management to enter the Security Management window.
You can create a user in three ways:
Right-click the User node on the security navigation tree, and select Add from the shortcut menu.
Select the User node on the security navigation tree, and click Add in the right window.
Select the User node on the security navigation tree, select any user from the right window and right-click. From the shortcut menu, select Add.
Creating user
Creating user
In the Create new user dialog box, input the correct parameters
Click the General Info tab, and input the correct parameters
Click the User Groups tab, and select the user group to be bound
Click the NE Users tab, and select the NE user to be bound.
Click Apply or OK to add the user
Creating user
Adding NE user
An M2000 user can log in to the NE through the NE LMT to carry out operations and management on the NE after the mapping relation is set up between NE users and M2000 users.
Select System > Security Management to view the Security Management dialog box.
Unfold the Security Management navigation tree. Select the nodes NE user> NE Type, and select an NE
Adding NE user
Right-click the NE, and select Add NE User or click Add NE User.
In the displayed Add NE User dialog box, enter the information about the NE user
Binding User to NE User
You can bind a user to an NE user in three ways:
Select the User node in the security navigation tree, right-click the user to be bound to the NE user, and select Bind NE User from the shortcut menu.
Unfold the User node in the security navigation tree, select the user to be bound to the NE user. Click the NE Users tab, and click Bind NE User.
In the Bind User to NE User dialog box, bind the user to the corresponding NE user.
Binding User to NE User
Banding User Rights
You can enter the Bind User Group to Access dialog box in two ways:
Unfold the User node on the security navigation tree, right-click the user access to be bound, and select Bind User Rights from the shortcut menu.
Select the User node on the security navigation tree, select the user access to be bound in the right window, and click Bind Rights .
Banding User Rights
Banding User Rights
In the Bind User Group to Access dialog box, all the devices are displayed in the left navigation tree. Select a device, and all the accesses will be displayed on the tree in the middle.
Check/Uncheck the access to select/deselect the access in the tree.
Security Setting
Select System > Security Setting to enter the Security Setting dialog box.
Set the corresponding information.
Security Setting
If you select Single user mode, after click OK,The Message dialog box pops up. Enter the delay time for mode switching, and click OK. Then, mode switching counts down, and the system notifies all other online clients about it.
Changing Password
Click System > Change Password to enter the Change Password dialog box.
Input the current password in Old Password, and a new password in both New Password and Verify Password to ensure the new one is correct.
Unlocking User
If all the attempts failed because of incorrect password, the user will be locked for some time. (refer to Security Setting for details)
Login to M2000 as the user who has the right to unlock users.
Select System > Security Management.
Click User in Security Management and select the locked user.
Select Unlock User from the shortcut menu.
Unlocking User
Monitoring User Operation
Select System > User Monitor to display the User Monitor dialog box.
Select the User Monitor tab.
Forcing User to Exit
You can force a user to exit if you find that the user session is dangerous for the M2000.
Select System > User Monitor to open the User Monitor dialog box.
Select the User Monitor tab.
Right-click a record in the User Session Monitor pane. On the shortcut menu, select Force User to Exit. Or select the record and then click Force User to Exit.
In the Confirm dialog box, click Yes.
Forcing User to Exit
Querying User Log
Select System > Log Management > Log Query And Statistic to open the Log Management dialog box.
Click the Log Query node under the Log Management navigation tree, and you can query the user log.
Querying User Log
Click the User Log, and you can query M2000 logs by the time range, result, user, terminal type, operation and target object.
After setting conditions, click Query.
Log Statistics
Select System > Log Management > Log Query And Statistic.
From the Log Management navigation tree, select the User Log node under Log Statistics.
Click Select to enter the Select Statistic Items dialog box.
Log Statistics
Note:
There are two restrictions for selecting a statistical item: Category and Operation cannot be both selected; a maximum of four statistical items can be selected.
All the filter conditions depend on the existing data in the database. If the data does not exist or has been dumped, the corresponding information will not be displayed in the dialog box. For example, if no users are created, Create user will not appear in Security under Operations.
Log Statistics
User Log Displacement
The system provides user log displace to set displacement conditions. The user log displace include two ways:
User Log Manual Displacement
User Log Auto Displacement
Log Manual Displacement
User Log Auto Displacement
Contents
Alarm Categories (Cont.)
Fault alarms: refer to those generated when faults occur to devices or exception occurs to key functions, such as a board fault alarm. Fault alarms can be cleared. Fault alarms are more severe than event alarms.
Event alarms: refer to the event alarms occasionally generated during the equipment running. They indicate only the status of the running equipment at a certain time point. The system generates some event alarms periodically to notifying you of the equipment status. They do not need manual handling. For example, the congestion alarm.
Alarm Categories
History fault alarms: refer to those cleared and acknowledged fault alarms.
Shielded alarms: can only be fault or event alarms. They are generated during a short period of time, they match the correlation conditions set on the M2000, and they are stored in the M2000 shielding base.
Alarm Status (Cont.)
Acknowledged Alarms
The alarm acknowledgement function helps identify alarms. Once you acknowledge an alarm manually, the M2000 displays the alarm as acknowledged. In this way, you know which alarms are manually processed and which are not.
However, this status shows only that the alarm is currently acknowledged. It does not mean that the alarm is cleared.
Alarm Status
Cleared Alarms
The alarm clearance applies only to fault alarms. When a fault is cleared, the NE returns to normal and reports the alarm clearance information to the M2000, and the M2000 displays this alarm as cleared.
Fault Alarms Changing to History Alarms
Storing Alarms (Cont.)
On receiving an alarm, the M2000 processes it and decides whether to save it into the relevant alarm base or discard it, as follows:
The M2000 checks if this alarm belongs to the shielded alarms defined on the M2000. If yes, the M2000 discards this alarm.
The M2000 checks if this alarm is defined with another severity on the M2000. If yes, the M2000 redefines the severity of this alarm.
Storing Alarms
The M2000 checks if this alarm matches the correlation rule set on the M2000. If yes, the M2000 drops it into the shielded alarm base.
The M2000 saves alarms that are not shielded or discarded into the fault alarm base or event alarm base based on the alarm contents.
Displaying Alarms
After the M2000 saves alarms into the databases, you can query or browse the information about the alarms reported from both the NE and the M2000 itself on the M2000 client. These alarms include:
Current fault alarms
Alarm Processing Procedure
Querying Current Fault Alarms
The Alarm Browse, Query and Statistics dialog box is displayed.
Click the Current Fault Alarm Query tab.
Set query conditions.
Querying Current Fault Alarms
Querying Event Alarms
Click the Event Alarm Query 1 tab.
Querying Event Alarms
Querying History Alarms
Select Fault > Query > History Fault Alarm.
The Alarm Browse, Query and Statistics dialog box is displayed. Click the History Fault Alarm Query 1 tab.
Querying Shielded Alarms
Click the Shielded Alarm Query 1 tab.
Browsing Real-Time Event Alarms
Click the Event Alarm Browse 1 tab.
Alarm Filter
This task introduces how to set the alarm filter condition to filter fault alarms and event alarms.
The alarms that match the filter condition will be discarded and will not be saved in the alarm database.
The alarm can be filtered by two ways:
Alarm level or type
Alarm Filter
Querying Alarm Explanation
In Alarm Browse, Query and Statistics, select an alarm to query the alarm details.
Double-click an alarm. The Alarm Details dialog box is displayed
Click each tab to obtain all the alarm details.
Click More information in the Alarm Details tab to obtain the help for alarm processing.
Querying Alarm Explanation
Setting the Alarm List
In Alarm Browse, Query and Statistics, right-click the alarm list and select Configure Columns.
The Configure Columns dialog box is displayed.
In Configure Columns, select the columns to be displayed, and click OK.
Collecting Alarm Statistics
Select Fault > Statistics > Alarm Statistics.
The Alarm Browse, Query and Statistics dialog box is displayed. Click the Statistics 1 tab.
Select statistic items in Statistic Item.
For example, select Alarm Level and Alarm Type. Click Statistic, and the alarm data is displayed in a statistic table.
Collecting Alarm Statistics
Click the Pie tab. The alarm pie chart is displayed.
Acknowledging Alarms Manually
In Alarm Browse, Query and Statistics, select an unacknowledged alarm.
Right-click and select Acknowledge.
Acknowledging Alarms Automatically
The Fault Service Settings dialog box is displayed.
Set the conditions for auto acknowledgement of event and fault alarms.
Displacing Alarms into a File
Select Fault > Alarm Displace. The Alarm Displace dialog box is displayed.
Two displace ways are available:
auto displacement
manual displacement.
Auto displacement
Select Auto Displace. Set Alarm category to and file type, set the displace conditions, and then click Start.
There are two displace conditions.
auto displacement
manual displacement.
Manual displacement.
Redefining the Alarm Level
Select Level Redefine, and click Add.
Alarms of all NEs are displayed in the left part of the dialog box
Redefining the Alarm Level
Select an alarm or press Shift to select multiple alarms in the left pane. Select an alarm level from the drop-down list behind Set Whole Type Redefine Level in the right part of the dialog box.
Click OK. The left part of the dialog box displays the alarms with the redefined alarm level.
To modify the alarm level of the redefined alarms, click Modify.
Setting Alarm Correlation Rules
The M2000 performs correlation analysis on all received alarms. It displays the root alarm only and shields all the other redundant information, and thus helping locating the fault rapidly.
The M2000 supports the following correlation analyses:
Intermittent fault correlation
Repeat event correlation
Setting Alarm Correlation Rules for Fault Alarms
Select Fault > Fault Service Settings. The Fault Service Settings dialog box is displayed.
Select the Correlation tab.
Setting Alarm Correlation Rules for Fault Alarms (Cont.)
Select Activate under Activate or deactivate alarm correlation. Click Set, and Specified Alarm Properties at the lower part becomes available.
Select an option from the drop-down list behind Shield under Common Property and click Set.
Setting Alarm Correlation Rules for Fault Alarms
If you select Shield, the repeated alarms will be dropped into the shielded alarm base. However, you can still browse them later.
If you select Abandon, the repeated alarms will be abandoned directly and you cannot browse them in the M2000 alarm base.
Select the NE type and the alarm name, set Interval (seconds) and Times of intermittence, and Click Add.
Setting Alarm Correlation Rules for Event Alarms
Custom correlation
Modifying Alarm Knowledge (Cont.)
To add or modify alarm knowledge records and to record relevant experiences.
See the knowledge base for the knowledge on an alarm when this alarm occurs later.
Select Fault > Fault Service Settings.
Modifying Alarm Knowledge (Cont.)
Select the Knowledge and Explanation tab.
Select the alarm to add or modify in the left part of the dialog box, and enter or modify the knowledge of this alarm in the right Knowledge dialog box.
Click Modify Knowledge. The knowledge on this alarm is modified.
Modifying Alarm Knowledge
Setting the Display of the Alarm Board
Select Fault > Local Terminal Settings.
Select the Alarm Board tab.
Select Alarm board windows setting, and set is to display the number of the alarms.
Setting an Alarm Sound/Color
Select the Sound and Color tab.
Select the alarm sound file for alarms of various levels.
Starting/Stopping the Alarm Sound/Flash
Select the Sound and Color tab .
Click the speaker icon behind each alarm level to start or stop the alarm sound.
Starting/Stopping the Alarm Sound/Flash
Select Fault > Alarm Board.
Click Sound to start or stop the alarm sound for all alarm levels.
Close Alarm Board.
Setting the Alarm Box Filter
To select alarms to be delivered to the alarm box.
The alarms not selected are not delivered to the alarm box, and the alarm box does not give any audio/visual alarm for them.
All alarms are delivered to the alarm box by default.
Select Fault > Local Terminal Settings.
Select the Alarm Box tab.
Select Enable alarm box on the current client.
Select the NE and the alarm level.
Alarms of the selected NE and alarm level are delivered to the alarm box.
Click Apply and then OK.
Stopping/Resetting the Alarm Box
Select Fault > Alarm Box > Stop/Reset Alarm Box, and the alarm box is stopped/reset.
If you select Stop Alarm Box again, the alarm box starts running again.
Setting the Alarm Notification
To set the the alarm notification, we have three ways:
over PhoneNo
by E-mail
by SMS
You have logged in to the M2000 client.
Some other equipment is needed, and communicate with M2000 server normally.
Setting the Alarm Notification
Contents
Measurement Counters
The measurement counter defines what to measure. Based on the source, counters fall into the following two categories:
Default counters defined for the NE. The NE reports to the M2000 periodically measurement results of all the default performance counters. The default performance counters include Key Performance Indexes (KPIs) and extended counters.
Counters defined on the M2000 client, namely, user defined counters.
Querying Performance Results
Select Performance > Query Result.
The Query Result dialog box is displayed. Query the results in two ways:
setting new query conditions
Querying Performance Results
In the left navigation tree, select the NE, measurement set and then measurement unit.
The right part of the dialog box contains three tabs. Select objects in Object Selection and counters in Counter Selection, and set Time and Query Period in Other Setting. Click Query. The system displays results and the task is complete.
If the system prompts “not available”, it shows that these counters are extended counters. Select them manually. Select Counter Setting in the system prompt window, or select Performance > Counter Setting. Select the extended counters and click OK.
Example
to set new query conditions to measure for LAPD link.
Select Performance > Query Result.
Example
Select the NE BSC from the left navigation tree, and then the measurement set LAPD Link Measurement Function and the measurement unit LAPD Link Measurement Function.
Example
Example
If the system prompts No result for the specified condition found, click Measurement in the prompt dialog box to view the cause.
If the measurement state is displayed Measuring, it shows that the measured counter is an extended counter. Results for the extended counters are displayed at the next measurement period. No operation is necessary in this case.
Example
Applying a Template
Click New Query.
In the left navigation tree, select the NE, measurement set and then measurement unit.
The right part of the dialog box contains three tabs. Select objects in Object Selection and counters in Counter Selection, and set Time and Query Period in Other Setting. Click Save Template.
Applying a Template
Enter a name for the template, and click OK to save it.
To use the template to query measurement results, right-click a template from the left navigation tree in Query Result.
Select New Query and the time.
Setting Measurement Objects
Select Performance > Object Setting.
Select the NE, measurement set and then measurement unit in the left navigation tree.
Setting Extended Performance Counters
select Performance > Counter Setting. and save the extended counters for measurements with the period longer than 30 minutes.
Select Performance > Real-Time Counter Setting and save the extended counters for measurements with the period as 5 minutes or 15 minutes.
Setting Extended Performance Counters
Managing Performance Measurement
Select Performance > Measure Management.
Click Subscribe at the bottom of the dialog box.
The Subscribe Result – 30 Minutes dialog box is displayed. When the specified period is up, the dialog box displays measurement results.
Select Performance > Real-Time Measure Management.
Click Subscribe at the bottom of the dialog box.
The Real-Time Subscribe Result – 5 minutes dialog box is displayed.
Contents
Creating Periodic Backup Tasks
Select Tools > System Backup > Periodic Backup.
Select the NE tab. Select Enable NE Periodic Backup, and set Execution Time and Backup Period.
Backup Management
Summary
Operation and maintenance on M2000 client
Backup and restoration

Date post:	24-Nov-2015
Category:	Documents
Upload:	hsrobby
View:	20 times
Download:	0 times

Omo000201 Imanager m2000v2 Client o&m for Gbss Issue1.0

Documents