GT Network BSC O&M Batch 9 Book File 2 of 2

BSC6900 GU Operation and Maintenance
Confidential Information of Huawei. No Spreading Without Permission
BSC6900 GU LMT User Guide describes the functions and relevant components of the
BSC6900 Local Maintenance Terminal (LMT). It also provides instructions for performing
basic operation and maintenance (OM) tasks of BSC6900.
Functions:
The OM subsystem provides the following types of management for the BSC6900:

Data Configuration Management

Security Management

Performance Management

Alarm Management

Loading Management

Upgrade Management
Hardware Involved:
The OM subsystem consists of the OMU board.
Step 1 Enter the external virtual IP address of the OMU in the address bar on the IE. Press
Enter on the keyboard, or click Go next to the address bar to display the login window of
the BSC6900.
Step 2 Enter the Name, Password, and Verify Code.

Select the User Type. You can select Local User or EMS.

If the verify code is illegible, click Change the verify code for a new code.
Step 3 Click Login.
NOTE:

If the login fails, click Reset. Enter the correct Name, Password, and Verify Code
again. If the login fails again, check whether the connection between the LMT and
the OMU is normal.
Component
Description
Alarm tab
You can query the active alarms, alarm logs, and alarm
configuration on this tab page.
Batch tab
You can run MML commands in batches on this tab page.
Trace tab
You can manage the message tracing tasks on this tab page.
Monitor tab
You can monitor the performance data on this tab page.
Device Maintenance
tab
You can maintain the device panel, base station controller, and base
stations on this tab page.
Navigation Tree
It displays the MML commands in the tree structure.
MML command area
You can input MML commands.
Progress tab
You can click the tab to display the progress of a task.

NOTE:
If this tab is hidden, click Progress on the toolbar to show the
Progress tab page. Then, double-click an entry to view the detailed
information. The Progress Management dialog box is displayed,
listing the detailed progress report.
Component
Description
FTP Tool
You can click it to download the executable application file

SFTPServer.exe.
Password
You can click it to change the password of the current user. After
changing the password, you need to use the new password when
logging in again.
File Manager
You can click it to upload files from the LMT to the OMU and download
files from the OMU to the LMT.
Language Setting
After you choose a language, text can be input and displayed in the
language on the LMT.
NOTE:
Setting the language does not change the display language of the LMT.
About
You can click it to display the version of the current LMT.
Lock
You can click it to lock the current operation interface for security.
NOTE:
After you click Lock on the toolbar, the LMT is locked.
You can click the web page or press the Enter key, type the password,
and then click OK or press Enter to enter the LMT workspace again.
Lockup Setting
You can click it to set the waiting time before the LMT screen is locked.
If there is no mouse or keyboard operation during the waiting time, the
LMT automatically locks its operation screen and goes to the locked
page. The setting prevents unauthorized users from using others'
accounts and performing unauthorized configuration and maintenance.
NOTE:
After you click Lockup Setting on the toolbar, the Lockup Setting
dialog box is displayed. In the Lockup Setting dialog box, you can set the
time for which the LMT waits before lockup.
You can click the web page or press the Enter key, type the password,
and then click OK or press Enter to enter the LMT workspace again.
Logout
You can click it to log out the current user without exiting the system.
Logout of one account user facilitates login of another account user.
No.
1
Field
Description
Common Maintenance Displays system responses, for example, the execution results.
tab
Operation Record tab
Displays commands that have been run.
Help Information tab
Displays the help information on a command
Manual editing area
Displays the area for manually editing the MML command script. In
this area, you can select Save Results, Auto Scroll to save or scroll
the command execution results automatically. You can also clear all
the results by clicking Clear All.
History Command box Displays the commands that you have run after logging in to the
system and the relevant parameters.
Command Input box
Displays in the drop-down list all the MML commands available on

the system. You can select an MML command from the drop-down
list or type in an MML command for execution.
Parameter area
Displays the parameters of the current command. You need to set

parameter values in the boxes before executing the command. The
parameters in red are mandatory to be set, and those in black are
optional.
Context:
The batch file (also called data script file) is a plain text file. It contains a group of
command scripts for a special task. The system automatically runs the commands in
sequence.
Procedure:
1. Click Batch on the top of the LMT main page.
2. Click New and enter the batch commands in the editing area, or click Open... to
select the pre-edited batch file.
3. Click Set... to set the parameters for running the MML commands.
4. Click Go to start running the commands automatically.
Note

Batch Processing Assistant
Use the batch processing assistant function. You can use the function to
check the format of MML commands in the assistant input area,
correctness of the parameters BTSID, CELLID, and TRXID, and relationship
between the parameters. You can also use the function to add MML
commands to a batch file or directly overwrite the original batch file.
Syntax Check
Check syntax of the MML commands before running a batch of MML

script commands. This function helps locate incorrect commands,
improving maintenance efficiency.
Through MML commands:

Run the LST CFGMODE command to check the current data configuration mode.

Run the LST CMCTRL command to check the current control status of the data
configuration rights.
When the OMU is installed for the first time, the CM right is disabled by default, and the
CM right is not checked if you run a configuration command. You can enable the CM right
through the SET CMCTRLSW command. Before you run a configuration command, you
should run this command to apply for CM right.
FTP Client

The FTP client is a component of the LMT software suite and enables the communication
between the LMT and the FTP server according to the FTP protocol. You can obtain logs
and upload data configuration files through the FTP client.
FTP Server

The FTP server is a component of the LMT software suite and provides upload and
download services according to the FTP protocol. It is used when uploading and
downloading BTS software and license file.
LMT Offline MML
LMT offline MML is a component of the LMT offline tool. It enables users to use MML
functions, view MML, make MML scripts, and view LMT Online Help of the corresponding
version offline by means of a browser.
File Manager

The file manager is a component of the LMT software suite. It enables file uploading and
downloading between the LMT and the OMU. The functions of the file manager are similar
to those of the FTP client. For example, you can obtain logs and upload data configuration
files.
Convert Management System

The Convert Management System is a component of the LMT software suite. It enables
communication between the OMU and the alarm box and is used to transfer the alarm
information, alarm box control information, and alarm box status information. The Convert
Management System must be started to connect the LMT to the alarm box. The Convert
Management System communicates with the OMU through the E1 port and to the alarm
box through the serial port.
Performance Browser Tool

The performance browser tool is a component of the LMT software suite. It is used to
parse the performance descriptive files in the OMU.
Traffic Recording Review Tool

The Traffic Recording Review Tool is a component of the LMT software suite and is used to
review the trace and monitor data.

In effective mode, the data configured takes effect immediately on the subrack.
In ineffective mode, the data configured for the subrack takes effect only in the OMU and
not on the subrack. In this case, you can run the SET CFGDATAEFFECTIVE command to
set the mode to effective mode, run the FMT DATA command to generate the data
configuration file for the subrack, and then run the RST SUBRACK command to reset the
subrack. In this way, the subrack can load the data configuration from the OMU so that
the data takes effect on the subrack.
If the OMU is newly installed, subrack 0 is in non-effective mode by default. If a subrack is
newly added, it is in ineffective mode by default.
The MBSC OM subsystem supports multi-user operation. For the system security, the
system uses the authority management which includes the following aspects:

Operator identity. An operator must enter the correct user name and password to
log in to the system.

Operation authority. Operators of different types are authorized to use different
command groups for GUI or MML operations. The MBSC categorizes operators
into different types and provides different command groups for each type as a way
to control operation authority.

Operation time limit. An operator can operate the MBSC only in an accountspecific period.

The BSC6900 provides 15 command groups (G_0 to G_14) with different functions by
default:
Through MML Command

List Command Groups of Operator Levels: LST OPCG

List Commands of Command Group: LST CCG

Adding commands to command group: ADD CCG

Removing commands from command group: RMV CCG
Function:

Use this command to add an operator account. Make sure that the operator has a
valid account before the operator operates the OMU.

The administrator account "admin" that is configured in the system is authorized to
execute all the commands and cannot be modified or removed.

The name of "emscomm" is reserved. The operator account with the user name of
"emscomm" cannot be added.

You can use this command to set the password, description, operation time limit, and
the operation authority for an operator. Operation right is determined by the operator
type. If the operator is of custom type, his right is determined by command groups
authorized to him.

The operators are classified as five levels:
Guest: Only query operation is allowed.
User: Besides the right of guests, the system maintenance is allowed.
Operator: Besides the right of users, the data configuration is allowed.
Administrator: Besides the right of operators, the user management is also

allowed.
Custom: The Administrators can define the operators with the Custom level.
They have administrator-defined operation rights.
The rights of the guest, user, operator, and administrator cannot be modified by user.
There are four types of operation time limits, date limit, week limit, time limit, and no
limit. The operator can access the OMU only during the intersection of those time
limits.
When the added operator is of the custom level, you can set the command groups in
which the commands can be executed by the operator.

Modify an operator account: MOD OP

You can use this command to set the password, description, operation time limit,
and the operation authority for an operator. Operation right is determined by the
operator type. If the operator is of custom type, his right is determined by
command groups authorized to him.
Alarm Type:

Fault alarms: Alarms caused by hardware faults, for example, board failure, or by the
abnormity of major functions. Fault alarms are of higher severity than event alarms. After
the faults occur, according to the statuses of the faults, fault alarms are divided into active
and recovery alarms.

Event alarms: An event alarm indicates a predefined event that happens during the running
of the devices. The alarm represents an instantaneous status of the system and the status
may not be a fault.

The fault alarms are classified into active and cleared alarms according to the fault status.
Cleared alarm: If a fault is rectified, the corresponding alarm becomes a cleared

alarm.
Active alarm: If the fault is not rectified, the corresponding alarm is an active alarm.
For example, when congestion occurs in a cell, the system reports a fault alarm of
cell congestion. Before the congestion is cleared, the alarm remains active. After
the congestion is cleared, the alarm is cleared.
Note

The record of a cleared alarm is stored in the OMU database and can be queried.
In scenarios where equipment is being deployed, commissioned, upgraded, swapped, cut
over, or the capacity of a base station is expanded, operations cause a great number of
alarms to be reported. There is no special mechanism to handle such alarms. Large in
number and short in existence period, these alarms make real fault alarms inconspicuous
and thus disturb normal network monitoring. To solve the problem discussed above,
Huawei puts forward the concept of "engineering alarms". With the concept, alarms in
scenarios of engineering maintenance are identified and handled as special cases. In this
way, delicacy management of alarms is implemented and fault OM efficiency of the
operator is improved.
Browsing Alarms

This section describes how to browse the fault alarms and event alarms on the
LMT. The alarm information provides the running status of the system in real time.
Querying Alarm Handling Suggestions

This describes how to query the handling suggestions of an alarm.
Querying the Alarm Configuration

This describes how to query the alarm configuration.
Filtering Fault Alarms

This describes how to filter the alarms by sites and specific filter options in the
Browse Alarm tab page. Only the alarms that meet the specified requirements are
displayed. All the alarms, however, are reported to the LMT and saved on the
OMU.
Browsing Alarm/Event

to browse fault alarms and event alarms on the LMT. Fault alarms and event
alarms are displayed in the Browse Alarm/Event tab page of the Alarm/Event
window. The alarm information provides the running status of the system in real
time.
Procedure

Click Alarm/Event on the LMT main page. The Browse Alarm/Event tab page is
displayed. The Normal Alarm, Event, and Engineering alarm tab pages are
displayed under the Browse Alarm/Event tab.

Browse alarms in the Browse Alarm/Event tab page.

To view the details of an alarm, double-click it. The Detail dialog box carrying the
detailed information about the alarm is displayed.

To save an alarm record, select the alarm record first. Then right-click it and choose
Save Select from the shortcut menu. To save all alarm records, right-click
anywhere in the alarm display area and choose Save All from the shortcut menu;
or directly click Save All.

Querying the Alarm/Event Log

to query alarm history from the OMU database. Using this function, you can review
the past performance and condition of the system.
Procedure
Through menu operations

displayed.

In the Query Alarm/Event Log tab page, click Query Setting. The Log
Condition dialog box is displayed.

To set the query conditions anew, click Reset. If you only need to set the BTS type
or NodeB type anew, click Filter By BTS or Filter By NodeB
NOTE: Click Filter to reset the query conditions.

Click Query. The query results are displayed in the Result area.

To learn more about an alarm, double-click it. The displayed Detail dialog box
shows the details of the alarm.

To save an alarm record, select the alarm record first. Then right-click it and choose
Save Select from the shortcut menu. To save all alarm records, right-click
anywhere in the alarm display area and choose Save All from the shortcut menu;
or directly click Save All.
Through MML commands:
Run the LST ALMLOG command to query the alarm logs.
Querying Alarm/Event Configuration

to query alarm/event configuration.
Procedure

Click Alarm on the LMT main page. The Alarm tab page is displayed.

Click the Query Alarm Configuration tab and click Query Setting. The Alarm
Configuration Condition dialog box is displayed for you to set the search criteria.

Set the search criteria as required.

Click Query. Query results are displayed in the Result area.
NOTE:

If you need to modify alarm configuration, choose an configuration item and click
Modify Alarm Configuration, or right-click in the Result area and choose
Modify Alarm Configuration from the shortcut menu.
Shield Flag

The shield flag is set to shield the alarm information not required. The shield flag
can be set to Shielded or Unshielded.
Shielded: A board does not report the alarms whose shield flags are set to
Shield to the network manager or the alarm box. The server does not save
the logs of such alarms.
Unshielded: A board reports the alarms whose shield flags are set to Shield
to the network manager or the alarm box. The server saves the logs of
such alarms.
Filtering Fault Alarm/Event

to filter alarms by sites and specific filter options in the Browse Alarm tab page.
Only the alarms that meet the specified requirements are displayed. All the alarms,
however, are reported to the LMT and saved on the OMU.
Procedure

displayed.

In the Browse Alarm/Event tab page, click Filtrate Setting. The Set Alarm
Filtering Conditions dialog box is displayed.

In the Set Alarm Filtering Conditions dialog box, specify Alarm Source or
Alarm ID. Then, click OK. The alarms that meet the specified requirements are
displayed.
NOTE:

Setting Alarm Source Type displays alarm sources of the selected type in the box
below.

You can manually type an alarm source in Selected Source.

You can manually type an alarm source in Selected Source after selecting Alarm
Source Type. Association display is supported in the input box under Selected
Source. For example, if you type 3, all alarm sources of the source type starting
with 3 are displayed in the box under Selected Source.
Add Shield of Alarm Object(ADD OBJALMSHLD)

Use this command to create the BSC6900-based shield of an alarm object.

When shield of an alarm object is created successfully, the alarm matching the
shield will be filtered, this alarm will not be reported to the LMT/EMS and alarm
box.

Up to 100 object-based shields can be added.
List Shield of Alarm Object(LST OBJALMSHLD)

Use this command to query the shield of an alarm object in the system.
Set Alarm Shield Flag(SET ALMSHLD)

Use this command to set the alarm shield flag according to the alarm ID.

If the shield flag of the alarm specified by the alarm ID is set to "shielded", the
alarm is not reported. If the alarm ID whose corresponding alarm is an active alarm
is set to shielded, this active alarm is cleared automatically.
Querying the Alarm Log

This describes how to query the history alarm information from the OMU database.
Through this operation, you can learn about the history running conditions of the
system.
Setting Storage Conditions of Alarm Logs

This section describes how to set the maximum number of alarm logs and the time
limitations of the logs that can be stored in the OMU database.
Querying Storage Conditions of Alarm Logs

This section describes how to query the maximum number of alarm logs and the
time limitations of the logs that can be stored in the OMU database.
Querying the Alarm/Event Log

to query alarm history from the OMU database. Using this function, you can review
the past performance and condition of the system.
If the alarm logs exceed the maximum storage capacity or time limit, the system will
automatically clear the earliest logs.

Maximum capacity for storing the alarm log: Value Range: 10000~150000

Maximum number of days for storing history alarms: Value Range: 7~90
Operation log:

The operation log is mainly used to analyze the relationships between device faults
and performed operations.
Security log:

The security log is used for auditing and tracing security events.
Running log:

The running log helps you in fault location, routine inspection, and device running
monitoring.
Only the admin, ADMINISTRATOR-level, and authorized CUSTOM-level operators can
manage the logs.
LST OPTLOG

Source: Source of the operator to be queried
Value Range: EMS(EMS), LMT(LMT)
Operator: Account of the operator
Domain Name: Domain name of the operator to be queried

Value Range: LOCAL(LOCAL), EMS(EMS), EMSOP(EMSOP)

IP Address: IP address of the workstation where the command is executed
Command Name: Name of the command to be queried. You can select one or
more commands.
Final: Execution result.

If you select "FALSE", only the records of failed operations are displayed. If
you select "TRUE", only the records of successful operations are displayed.
If this parameter is not specified, all the records are displayed.
LST SECLOG

Log Type: Type of the log to be queried. The result is displayed by the specified
type.
Value Range: LOGINEVENT(Login Event), MANAGEEVENT(Management
Event), AUTHEVENT(Authentication Event), OTHEREVENT(Other Event)
Log Level: Level of the log
Value Range: CRITICAL(Critical), MAJOR(Major), MINOR(Minor)
List Log Limit(LST LOGLIMIT)

Use this command to query the automatic deletion time limit and the maximum
number of records allowed in the operation log and security log.
Set Log Limit(SET LOGLIMIT)

Use this command to set the storage limit of the operation log and security log.

Only the administrator has the authority to execute this command.

The deletion time limit is the operation time of the OMU rather than an absolute
time.

If the operation time of the system exceeds the set time limit, the logs before the
time limit are deleted automatically. If the number of logs exceeds the set count
limit, the earlier logs are deleted automatically.
Export Operation Log(EXP LOG)

Use this command to export the records in the operation log and security log to a
text file.

Export Operation Log(EXP LOG)

Note

1. Only administrators have the authority to export the log.

2. When no term is defined, all of the logs are exported.

3. The file name cannot contain any path and suffix.

4. The file is saved as a text file in the ftp\oprator_log directory of the main area
directory of the OMU. The main area of OMU can be queried through the LST
OMUAREA command.

5. When the command is executed, the system reports the progress to the client.
Query the information of the current operation in the progress management
window.

6. The name of the log file is constructed as follows: Name of NE-Start Time-End
Time-XLOG.txt. Here, "X" is the flag of the log type: "O" indicates the operation
log, and "S" indicates the security log.

7. The time rules are as follows: If the start time and end time are not specified,
the records from the earliest time to the latest time are exported by default. If only
the start time is specified, the records from the start time to the latest time are
exported. If only the end time is specified, the records from the earliest time to the
end time are exported.

8.The IP address is the IP address of the workstation where the command is
executed.
If the operation time of the system exceeds the set time limit, the logs before the time
limit are deleted automatically. If the number of logs exceeds the set count limit, the
earlier logs are deleted automatically.
Collect Fix Information(COL LOG)

Use this command to collect the log information for fault analysis.

The directories of log files collected this time can be queried through the LST
LOGRSTINFO command. Please get the log files by yourself. The amount and
directory may be different lied on the log type.
We can use FTP Tool or File Manager to download the log files to local PC.
Step 1 Click Device Maintenance on the LMT main page. The Device Maintenance
window is displayed.
Step 2 The BSC Device Panel tab is displayed.
Step 1 Click Device Maintenance on the LMT main page. The Device Maintenance
window is displayed.
Step 2 Click BSC6900 under Device Navigation Tree. The BSC Device Panel is
displayed on the right pane.
Step 3 Specify the rack No. and double-click the peripheral of the displayed device
panel. The Emulation Subrack is displayed.
Procedure

Click Device Maintenance on the LMT main page. The Device Maintenance tab
page is displayed.

In the BSC Maintenance tab page, choose BSC Maintenance > Browse
Configuration Data. The Browse Configuration Data tab page is displayed.

In the Browse Items navigation tree, select the items to be browsed and click
Browse (or double-click the items to be browsed). The corresponding
configuration data is displayed on the right area.

Click Save As to save the corresponding configuration data.

To create a new template of browsing items, click New. In the displayed New
dialog box, set the Template Name and select the browsing items as required.
Then, click OK.

To modify or delete a template, select the template and click Modify or Delete.
Backing Up Data

to back up system data on the OMU. The system data includes configuration data,
alarm configuration data, and performance configuration data.
Context

When the database system crashes or an upgrade fails, start the tool used for
backing up and restoring system data in the
mbsc\bam\common\services\omu_backup_linker directory. With the latest
backup data, you can recover the system.

If you need to recover only OMU configuration data, run the RTR DB command
and select a corresponding data backup file for data recovery.
NOTE

The default directory for saving backup files is OMU active workspace
installation directory\data\backup. If such a directory does not exist, it will be
created automatically.

If the name of a backup file is not typed, the file is named BKPDB_#_*.bak
automatically. Here, "#" stands for the detailed version information of the working
OMU and "*" stands for the current system time when the backup is performed.
When the number of backup files in the backup directory exceeds 30, the earliest
backup file is automatically deleted.
Through an MML command

Run the LST BKPFILE command to query data backup files saved in the OMU
active workspace installation directory\data\backup directory.

Run the BKP DB command to back up system data on the OMU.

Restoring data overwrites OMU data, so restore data with caution.

Versions of data backup files must be the same as the OMU version.
Alarm information and operation logs are not restored. Their data remains unchanged.
After restoring OMU data, run the RST BSC command to reset the BSC.
Procedure
Through menu operations

Click Device Maintenance on the LMT main page. The Device Maintenance tab
page is displayed.

In the BSC Maintenance tab page, choose BSC Maintenance > Restore Data.
The Restore Data dialog box is displayed with information about data backup files
saved in the OMU active workspace installation directory\data\backup
directory.

Optional: In the displayed Restore Data dialog box, click Upload to upload a
backup file on the LMT PC to the OMU.

In the displayed Restore Data dialog box, click Restore Data to restore
configuration data on the OMU.

Run the LST BKPFILE command to query data backup files saved in the OMU
active workspace installation directory\data\backup directory.

Run the RTR DB command to restore configuration data on the OMU.
Through MML commands

Run the DSP BRD command to query the information about the BSC board.

Run the DSP CLK command to query the clock status of the BSC board.

Run the SWP BRD command to switch over the BSC boards.
CAUTION:

If the board switchover fails, the configuration data is not affected but the services
will be disrupted. Thus, perform this task with caution.

Resetting the board may affect the ongoing services. Thus, you are advised to
perform the switchover when the traffic load is light, for example, in the middle of
the night.

All boards configured in active/standby mode support switchover operations. Only
the active board can initiate the switchover, except the OMUa board. The OMUa
board also supports switchover initiated by the standby board.

Run the RST BRD command to reset a BSC board.

Run the DSP LAPDLNK command to query the status of an LAPD link.

Run the LOP LAPDLNK command to perform a loopback test of an LAPD link.

Run the RST LAPDLNK command to reset an LAPD link.

Run the DSP N7DPC command to query the status of the specified DPCs.

Run the INH N7DPC command to inhibit a specified DPC.

Run the UIN N7DPC command to uninhibit a specified DPC.

Run the DSP SSN command to query the status of the SCCP subsystem.
You can query the status of the MTP3 link by link signaling set or by destination signaling
point (DSP).

Query by link signaling set: Each MTP3 link has a unique link number. One
interface board corresponds to multiple links. You can specify a board and a link
number to query the status of an MTP3 link.

Query by DSP: One DSP code (DPC) can be used by multiple MTP3 links. You can
query the status of multiple MTP3 links by querying the corresponding DPC.
The operations related to an MTP3 link are as follows:

Activating: This operation is performed to set up a new MTP3 link.

Deactivating: This operation is performed to remove the MTP3 links and the MTP2
links.

Disabling: This operation is performed to disable the MTP3 links, but the MTP2
links are still available.

Enabling: This operation is performed to enable the MTP3 links.

Run the DSP MTP3LNK to query the status of MTP3 links.

Run the DSP MTP3RT to query the status of MTP3 route.

Run the DSP N7DPC command to query the status of the specified DPCs.

Run the ACT MTP3LNK command to activate MTP3 links.

Run the DEA MTP3LNK command to deactivate MTP3 links.

Run the INH MTP3LNK command to inhibit MTP3 links.

Run the UIN MTP3LNK command to uninhibit MTP3 links.

Run the DSP MTP2LNK command to query the status of an MTP2 link.

Run the DSP ACIC to query the status of A interface circuits.

Run the RST ACIC command to reset A interface circuits.

Run the UBL ACIC command to uninhibit A interface circuits.

Run the BLK ACIC command to inhibit A interface circuits.

Run the DSP DSPLINK command to query the status of a DSP link.

Run the INH DSP command to inhibit the DSP.

Run the UIN DSP command to uninhibit the DSP.
Assume that MS A is under the control of the local BSC where the external loopback is performed.
MS B (or a fixed-phone) is under the control of another BSC.
To MSC
After the external loopback towards the MSC is performed, the 64 kbit/s PCM stream
received from the MSC is directly sent to the MSC and the signals received from the BTS are
not sent. The processing mechanism of the received signals remains the same.
In normal cases, after the external loopback towards the MSC is performed, MS A can hear
the voice of MS B. MS B can hear its own voice, but cannot hear the voice of MS A.
After the external loopback towards the MSC is performed, MS B cannot hear its own voice.
In this case, you can infer that the voice problem is caused by the MSC side or A interface.
In this case, if MS A cannot hear the voice of MS B, the fault can be located through the
external loopback towards the BTS or through the DSP speech channel loopback.
To MS
After the external loopback towards the BTS is performed, the 64 kbit/s PCM stream
received on the DPUc is directly sent to the DPUc and the signals received from the MSC
are not sent. The processing mechanism of the received signals remains the same.
In normal cases, after the external loopback towards the BTS is performed, MS A cannot
hear the voice of MS B, but can hear its own voice. MS B can hear the voice of MS A.
After the external loopback towards the BTS is performed, MS A cannot hear its own voice.
In this case, you can infer that the voice problem is caused by the BSS side.
In this case, if MS B cannot hear the voice of MS B, the fault can be located through the
external loopback towards the MSC or through the DSP speech channel loopback.

In the system, the speech is divided into speech in the sending direction and speech in the
receiving direction. Respective channels are used. By looping back the speech sent over the
speech channel through the receiving path and comparing with the sent speech, you can
determine the scope of a speech problem.
The purpose of external speech channel loopback is to detect external speech channel
problems by using speech loopback at the A interface and Ater interface. If external
problems are ruled out, start internal speech channel detection to solve internal speech
channel problems.
Loopback directions include remote loopback (MSC direction) and local loopback (MS
direction).
NOTE:
If you query the user messages through MSISDN, you are advised to set MS ID to that of
the peer end:

(Recommended) To query the calling MS, set the MS ID to that of the called MS.
For example, if the MS calls 12345, then set the MS ID to 12345.

To query the called MS, set the MS ID to that of the calling MS, which is displayed
on the called MS. For example, if 54321 is displayed on the called MS, set the
MSISDN to 54321.
If you query the user messages through TMSI or IMSI, you must determine the
reassignment strategy on the MSC side:

If TMSI is carried, you can query the MS by the TMSI.

If TMSI is carried, you can query the MS by the IMSI.
If you query the user messages by IMEI, you must determine whether the IMEI is available
to the MSC.
DSP Loopback on the A interface

The loopback towards the MSC, BTS, and MSC is performed without voice coding
and decoding. The loopback towards the BTS is performed with voice coding and
decoding.

After the loopback on the A interface is performed on the DSP speech channel, MS
B can hear its own voice. After the loopback on the Abis interface is performed on
the DSP speech channel, MS B cannot hear its own voice. In this case, you can
infer that the voice processing of the TC is abnormal.
DSP Loopback on the Abis interface

When the loopback towards the MSC and BTS is performed at the same time, the
loopback towards the MSC is performed with voice coding and decoding. The
loopback towards the BTS is performed without voice coding and decoding.

After the loopback on the Abis interface is performed on the DSP speech channel,
MS A can hear its own voice. After the loopback on the A interface is performed
on the DSP speech channel, MS A cannot hear its own voice. In this case, you can
infer that the voice processing of the TC is abnormal.
You should use Query Single User Resources function to get DSP No. which is used for this
call, then perform the DSP Channels/Links Loopback
Local loopback

When the local loopback is performed on the port of the specified interface board,
the signals sent on the port are sent to the receive channel back to the interface
board. No signal will be sent to peer end.
Remote loopback

When the remote loopback is performed on the port of the specified interface
board, the signals received on the port are directly sent, but the signals on the
board to be sent are not sent. The processing mechanism of the received signals is
the same.
The analysis result is based on analysis of many logs reporting one-way audio. If the total
number of logs is less than 10 in a measurement period, the logs are not analyzed.
NOTE:

The analysis result form contains the log type, fault node, fault times, detailed
information about the fault node, total number of logs, and analysis period of
time. The fault node consists of the cell, TRX, Abis interface board, switching
network board, TC resources, Ater interface, and A interface.

Only the top three types of fault nodes in the descending order of number are
displayed in the analysis result. If the number of fault node types is less than three,
all the fault node types are displayed.
BSC6900 GO Operation and Maintenance

DSP LAPDLNK : Expected result: The value of UsageStatus is Normal.

DSP ABISTS : Expected result: The State of many timeslots is Idle, and there is no
timeslot with the State of Failure.
Expected result: The value of Cell Initialized is Yes and the value of Channel Fault is No.

DSP LAPDLNK : Expected result: The value of UsageStatus is Normal.

DSP ADJNODE : Expected result: The values of available bandwidth are not all 0.
DSP IPPATH : Expected result: The value of Operation state is Available.
DSP BTSSTAT : Expected result: The value of Cell Initialized is Yes and the value of
Channel Fault is No.
BSC6900 GO V900R013 Data Configuration Based

on LMT
UDP: User Datagram Protocol

The UDP is a connectionless and unreliable transmission protocol.

The UDP provides simple services for the application layer. With the UDP, the data packet is
transmitted from one end to the other end, but the data packet may not be transmitted to
the destination successfully. Any reliability required must be provided by the application
layer.

The UDP is a simple data packet-oriented protocol at the transport layer. The UDP is widely
used because it features low cost and high real-time performance during the transmission.
The UDP is applied to scenarios that do not require high reliability.
SCTP: Stream Control Transmission Protocol

The SCTP is a reliable transmission protocol applied to network layers above the
connectionless network (such as IP network).The functions of the SCTP are similar to those
of the TCP.

The SCTP is designed to transmit Public Switched Telephone Network (PSTN) signaling in
the IP network. In addition, the SCTP can be applied to other scenarios. Currently, the SCTP
is used as the reliable transmission protocol to transmit signaling in the IP network.

The SCTP is the enhancement and optimization of the TCP with regard to signaling
transmission. Compared with the SCTP, the TFP has the following disadvantages: The TCP
does not support the SCTP multi-homing function, which affects the availability; the TCP is
subject to distributed denial of service (DDoS) attack, which affects the security; The TCP
processes the packet in a strict sequence, but the delay is increased when processing
packets that are out of sequence. The SCTP supports the multi-homing function, which
improves the link availability. In addition, the SCTP provides optimal performance in security
and packet processing.

The SCTP provides a reliable transmission of messages between equivalent SCTP users. The
SCTP is an end-to-end and connection-oriented protocol, which transmits data in
independent sequenced streams through the SCTP association between two SCTP
endpoints.

DSP E1T1 : Expected result: The Port running state of the associated E1/T1 port is Port
available.
DSP MTP2LNK : Expected result: The value of Link State is IN SERVICE.
DSP MTP3LNK : Expected result: The value of Operation state is Available.
DSP SSN : Expected result: The value of SSN state is Allowed.

DSP N7DPC : Expected result: The value of SCCP DSP state is Accessible.
DSP ACIC: Expected result: The CIC State of many CICs is Idle, and there is no CIC with
the CIC State of Failure.
DSP ETHPORT: Expected result: The value of Link Availability Status is Available.

Optional: Check the connectivity of the gateway (mandatory in three-layer
networking).
Run the MML command LST IPCHK to query the configuration of the
gateway connectivity check.
Run the MML command STR IPCHK to start the gateway connectivity
check.
In the alarm tab page of the LMT, check whether the ALM-21346 IP
Connectivity Check Failure alarm is reported. If yes, clear the alarm as
suggested.
Optional: To keep the gateway connectivity check, end this task;

otherwise, run the MML command STP IPCHK to stop the gateway
connectivity check.
DSP SCTPLNK : Expected result: The value of SCTP link Operation state is Normal.
DSP M3LNK : Expected result: The value of Operation state is Activated state.


DSP SSN : Expected result: The value of SSN state is Allowed.

DSP N7DPC : Expected result: The value of SCCP DSP state is Accessible.
DSP ADJNODE : Expected result: The values of available bandwidth are not all 0.
DSP IPPATH : Expected result: The value of Operation state is Available.

on LMT
The Gb interface (Gb interface is the interface between the SGSN and PCU in Huawei GPRS
network) is used to implement packet data transmission, mobility management and session
management between the SGSN and the BSS/MS. The Gb interface is mandatory for the GPRS
networking.

Physical layer protocol L1
The several physical layer configurations and protocols defined in GSM 08.14
are available here. The physical resources shall be configured through the
Operation and Maintenance (O&M) process.
FR (NS layer subnet service protocol)
The Frame Relay (FR) sub-layer of the Gb interface belongs to the NS SubNetwork Service protocol. The FR module enables the interworking of subnetwork so that the PCU may connect to the SGSN through point-to-point
connection or the frame relay network. The point-to-point connection refers to
the direct connection between the PCU and SGSN. Generally the PCU acts as
the DTE and the SGSN the DCE. You may flexibly set the network features of
the PCU and SGSN. Huawei PCU supports the above two connection modes.
The link layer protocol of the Gb interface is based on the FR and defined in
the GSM 08.16. Establish a FR virtual circuit between the SGSN and BSS,
which is to be multiplexed by the LLC PDU from multiple subscribers. This
virtual circuit may be multi-hop and traverse the network consisting of FR
switching nodes. The frame relay is used for signaling and data transmission.

on LMT
Network Service (NS) layer
The NS here particularly refers to the network service control part of the NS
protocol. The NS layer protocol implements such functions as NS Service
Data Unit (SDU) data transmission, NS-VC link management, load sharing
of subscriber data and network congestion status indication and network
status report.
BSSGP layer
The BSSGP provides radio-specific data, QoS and selection information to

satisfy the requirements of data transmission between the BSS and SGSN.
In the BSS, it is used as the interface between the LLC frame and RLC/MAC
block; in the SGSN, it is used as the interface between the RLC/MAC
information and LLC frame. The BSSGP has a one-to-one relationship
between the SGSN and BSS. That is, if a SGSN handles several BSSs, the
SGSN must have a BSSGP in relation to each BSS.
Though distributed on both sides of the Gb interface, the BSSGP has
asymmetrical functions on two sides of the Gb interface. The BSSGP
implements the following functions:
Signaling message and subscriber data transmission.
Traffic control of downlink data.
Blocking and unblocking of the BVC.
Dynamic configuration and management of the BVC.
Error detection of interface messages.

DSP BC : Expected result: The value of BC Service State is available.

DSP NSVC : Expected result: The value of NSVC Service State is Active Unblock.
DSP SIGBVC : Expected result: The value of SIG BVC State is Normal.
DSP PTPBVC : Expected result: The value of Service State is Normal.

DSP NSVL : Expected result: The value of NSVL State is Normal.

DSP GBIPROUTE : Expected result: The value of State is Normal .
DSP SIGBVC : Expected result: The value of SIG BVC State is Normal.

If the value of SIG BVC State is Fault, the SGSN may be configured with an NSE
that has a different NSE ID
DSP PTPBVC : Expected result: The value of Service State is Normal.

SAAL: Signaling ATM Adaptation Layer

AAL2: ATM Adaptation Layer 2
UNI: User Network Interface
ALCAP: Access Link Control Application Protocol, also called Q.AAL2
NBAP: NodeB Application Part
NCP: NodeB Control Port
CCP: Communication Control Port

UDP: User Datagram Protocol

SCTP: Stream Control Transmission Protocol

The transport network layer of the Iu-CS interface consists of the following areas:
Transport network layer user plane (area A)
Transport network layer control plane (area B)
Transport network layer user plane (area C)
Areas A, B, and C share the physical layer and ATM layer. Therefore, all links in the three
areas can be carried on common physical links.
The transport network layer over the Iu-PS interface consists of the transport network layer
user plane (area A) and the transport network layer user plane (area C).
Areas A and C share the physical layer and ATM layer. Therefore, all links in the two areas
can be carried on common physical links.
The transport network layer of the Iu-PS interface consists of the transport network layer
user plane (area A) and the transport network layer user plane (area C).
Areas A and C share the physical layer and data link layer. Therefore, all links in the two
areas can be carried on common physical links.
Internal Procedure for Creating a Tracing Task

When you create a tracing task on the LMT, the LMT sends a binary command to
the OMU to create the task.

The OMU assigns an ID to the task and forwards the command to the debugging
module of the specified board.

After receiving the command, the debugging module records the filter parameters
of the trace data in the filter table and notifies the service module.

The service module updates the local filter table according to the message from
the debugging module.
Internal Procedure for Closing a Tracing Task

When you close a tracing task on the LMT, the LMT sends a binary command to
the OMU to delete the task.

The OMU forwards the command to the specified board according to the task ID.

The debugging module and service module delete the task from the filter table.
Internal Procedure for the Service Module to Report Traced Messages to the LMT

The service module compares the collected messages against the local filter table
and reports the qualified messages to the OMU.

The OMU forwards the traced messages to the LMT that creates the task
according to the task ID.

The LMT translates the messages and displays them on the tracing window.
The users at the following levels can perform the tracing tasks online: admin, USER,
OPERATOR, ADMINISTRATOR, and CUSTOM entitled to use command group G_10.
Report
In this mode, the trace results are reported in real time. The server sends the traced
messages to the LMT PC directly, and the output file is automatically saved to the
LMT PC in *.tmf format.

The default saving path in LMT PC is C:\Web LMT\output\MBSC\trace\tmfFile
Save to OMU

In this mode, you can set the trace interval. The output file is automatically saved
to the OMU in *.tmf format.

The default saving path in OMU is: /mbsc/bam/Version_a/ftp/trace

You can query the trace files on the OMU and upload the trace files onto the LMT
PC by Managing the Trace File
Managing Tracing Tasks

The created tracing tasks can be queried, stop, deleted, and restarted.
Managing the Trace File

The trace files on the OMU can be queried and upload onto the LMT PC as
required.
GSM Tracing Interface
The A interface is the interface between a BSC6900 and an MSC. This section describes
how to trace the BSSAP, MTP2, MTP3, SCCP, SCTP, and M3UA messages on the A
interface. You can perform this task to locate a fault in the following scenarios: timeslot
assignment failure, abnormal releases, location update failure, and handover failure.
To trace signaling messages on the A/Abis/Um interface of a specified subscriber. The user
can be specified by the IMSI, IMEI, TMSI, MSISDN, CELLID, or channel.

If you trace the user messages through the MSISDN, you are advised to set the
MSISDN to that of the peer end:
(Recommended) To trace the calling MS, set the MSISDN to that of the
called MS. For example, if the MS calls 12345, then set the MSISDN to
12345.
To trace the called MS, set the MSISDN to that of the calling MS, which is
displayed on the called MS. For example, if 54321 is displayed on the called
MS, set the MSISDN to 54321.
If you trace the user messages by the TMSI or IMSI, you must check the
reassignment policies on the MSC side:
If TMSI is carried, you can trace the MS through the TMSI.
If IMSI is carried, you can trace the MS through the IMSI.

If you trace the user messages by the IMEI, you must check whether the IMEI is
available to the MSC.
If you trace the user messages by the CELLID, all calls in the cell are traced.
If you trace the user messages by the CHANINFO, the call carried by the specific
channel is traced.

NOTE
CDT Mode: If you select the CDT mode, you can trace interfaces between internal
modules.
Debug Mode: If you select the debug mode, you can trace stream data in Abis
over IP, Ater over IP, and A over IP scenarios. Interface boards need to be selected
in the Other tab page.
Location Flag: indicates information such as cell ID and TA.
Context
The UE tracing task is to trace signaling messages of a UE on the Iu, Iur, Iub, and Uu interfaces. The
UE can be specified by IMSI, TMSI, P-TMSI, or IMEI.
NOTE:
Each BSC6900 supports a maximum of 12 UE tracing tasks simultaneously.
Procedure
1. Click Trace on the LMT main page. The Trace window is displayed.
2. On the Trace Navigation Tree pane, expand Trace > UMTS Services. Double-click UE
Trace.
3. In the UE Trace dialog box, set the parameters as required, and click Submit. The trace
data pane displays the traced message flow.
NOTE:
If you trace a UE by specifying the IMSI and a consistent IMSI is included in the RRC CONNECTION
REQUEST message from the UE, the UE tracing task traces all the messages that are sent after the
RRC CONNECTION REQUEST message.
Assume that you trace a UE by specifying the IMSI and a consistent IMSI is included only in the
RANAP COMMON ID message but not in the RRC CONNECTION REQUEST message from the UE. If
CDT_MSG_FULL_TRACE is set to ON, the UE tracing task traces the messages that are sent after the
RANAP COMMON ID message, and the messages before the RANAP COMMON ID message are
buffered and reported to the BSC6900. If CDT_MSG_FULL_TRACE is set to OFF, the messages
before the RANAP COMMON ID message are discarded instead of being buffered.
In the tracing result displayed in the message browse window of UE Trace, the number displayed
in the User ID column has different meanings for different interfaces:

For the Iu interface, the user ID represents DPC ID at the CN side.

For the Iur interface, the user ID represents DPC ID at the BSC6900 side.

For the Iub interface, the user ID represents NODEB ID.

For the Uu interface, the user ID represents CELL ID.
Context

You can specify a cell by entering its cell ID. You can also select the message
types by selecting trace events. The cell message tracing task can be used to trace
NBAP common messages on the Iub interface of a specified cell and to report the
UE statistics as required. The cell to be traced must be activated.
NOTE:

A maximum of six cell tracing tasks can be performed simultaneously.

Each cell tracing task targets at only one cell.

Each cell tracing task targets at a maximum of two S-CCPCHs.
Procedure
1. Click Trace on the LMT main page. The Trace window is displayed.
2. On the Trace Navigation Tree pane, expand Trace > UMTS Services. Doubleclick Cell Trace.
3. In the Cell Trace dialog box, set the parameters as required, and click Submit.
The trace data pane displays the traced message flow.
NOTE:

You can query the cell ID and other cell information by running the command
LST UCELL.
Postrequisite
The message browse window displays the details of a tracing message, including the task
number, task time, RFN, subrack number, slot number, subsystem number, message
direction, message type, message source, user ID, and message content.
Procedure

Click Monitor on the LMT main page. The Monitor tab page is displayed.

On the Monitor Navigation Tree pane, choose Monitor > Common
Monitoring > CPU/DSP Usage Monitoring. The CPU/DSP Usage Monitoring
dialog box is displayed.

In the displayed CPU/DSP Usage Monitoring dialog box, set the parameters as
required, and click Submit.
NOTE
After the monitoring task is started, a monitoring window is displayed, showing
the real-time monitoring result by list and chart. The task name and related
parameters are displayed on the title bar of the window.
Context

Using this function disrupts transmission of an IMA group, UNI link, fractional ATM
link, fractional IMA link, MP group, or PPP link carried on a board. Services carried
on the corresponding port are thus affected.

Before starting BER monitoring, you need to configure local loopback at the local
end or configure remote loopback at the peer end. Or you can connect the
transmitting end to the receiving end using a loopback connector.

BER monitoring and a loopback test cannot be performed simultaneously.

Only one BER monitoring task can be started for one board at a time.

You must set E1/T1 port loopback before starting BER monitoring of an E1/T1 port
and timeslot-level testing.
Procedure

Click Monitor in the LMT home page. Accordingly, the Monitor tab page is
displayed.

Under Monitor Navigation Tree, choose Monitor > Common Monitoring >
BER Monitoring. Accordingly, the BER Monitoring dialog box is displayed.

In the displayed BER Monitoring dialog box, set the parameters as required, and
click Submit
To monitor the cell performance, such as the common measurement statistics and number
of UEs on the common channel. For the same monitoring item, you can start a maximum
of six tasks simultaneously.
Procedure

Click Monitor on the LMT main page. The Monitor tab page is displayed.

On the Monitor Navigation Tree pane, choose Monitor > UMTS Monitoring >
Board Resource Monitoring. The Board Resource Monitoring dialog box is
displayed.

In the Board Resource Monitoring dialog box, set the parameters as required, and
click Submit.
Note
Make sure the FTP Server in running and the LMT Offline Tool is installed in PC.
Use this command to query the detailed parameter information of a license file or query
the brief information of all the license files saved in the "\ftp\license" directory of the main
area directory of the OMU.
Course Name
P-136
Course Name
Steps
Loosen the screws of the board panel until the screws are detached from the
subrack, as shown in figures d and f.
Press down the lock washer of the panel, as shown in figure b, press outward the
ejector levers with two hands until the ejector levers are away from the springs,
continue to rotate the levers, as shown in figure c, until the board is detached
from the backplane.
Hold the handles with two hands and pull the board out along the guide rail, as
shown in figure c.
Hold the board with one hand and pull the panel with another hand to pull the
board out of the subrack.
Put the board into an ESD bag or ESD box.
P-137
Course Name
Steps

Obtain the board from the ESD box. Check the pins and sockets.
Press inward the lock washer, as shown in figures e and f, detach the ejector
levers from the lock washer and rotate the ejector levers outward until they can
no longer be rotated. Confirm that the ejector levers are in the position shown in
figure b.
Hold the board with one hand, grasp the panel with the other hand, insert the
board along the guide rail to the subrack, and push the panel until the ejector
levers are locked to the guide rail. At this time, the ejector levers are half-closed.
Quickly rotate the ejector levers inward, as shown in figure c, until they are firmly
attached to the lock washer. At this time, the board has been inserted to the
backplane and the ejector levers are inserted to the subrack, as shown in figure d.
Fasten the screws to fix the board, as shown in figures g and h.
P-138
Course Name
P-139

The DPUa/DPUc/DPUd/DPUf board is hot-swappable. It takes about two minutes to

replace the board.
Replacing the DPUa/DPUc/DPUd/DPUf board disrupts all the services carried on the board.
If the board version is inconsistent with the board version matching table,

Ensure that the program files of the board in the OMU active workspace
installation\bin\fam on the OMUa are correct. If the program files are incorrect,
contact Huawei engineers.

Run RST BRD to reset the board.

The XPUa board is hot-swappable. It takes about six minutes to replace and load a board.
CAUTION:

Replacing the standby main control XPUa board has no adverse impact on the
services in the system. Replacing the main control XPUa board that works
independently, however, disrupts services carried in the subrack.

Replacing the standby non main control XPUa board has no adverse impact on the
services in the system. Replacing the non main control XPUa board that works
independently, however, disrupts services carried in the board.
Course Name
In this slide, we mainly discusses the new and old boards are the same OS in Single-OMU
Mode.
P-144
Course Name
Prerequisites

The tools required for replacing an OMU board are prepared: an ESD wrist strap, a
Phillips screwdriver, a flat-head screwdriver, a wrench, and an ESD box or bag.
A new OMU board is prepared.
The version software required for installing the new OMU board is obtained. A
Dopra_Linux_U tool, Suse Linux OS installation disk, or Windows 2003 OS
installation disk is prepared for a new OMU board whose OS is Dopra Linux, Suse
Linux, and Windows 2003 respectively.
P-145
Course Name
To ensure OMU data consistency before and after a replacement, users need to check the
status of the OMU board to be replaced before a replacement. Users need to query and
record the OMU board information, active or standby state, and data synchronization
status.
It is expected that the returned results show that the data, version and licenses are
consistent.
P-146
Course Name
Query and record the external gateway IP address of the OMU board to be replaced.

If the OMU operating system is Dopra Linux or Suse Linux, Log in to the
OMU by referring to Logging In to the OMU.Enter the command route and press
Enter. Query and record the value of Gateway whose Destination is set to
default.
Example of OMU board status information table
Item
Setting information example
Computer name
OMU_21
Internal network fixed IP
80.168.3.50
External network fixed IP
10.168.172.2
Backup network IP
192.168.3.50
Operational state
Active normal
Version
XXXXXX
External network virtual IP
10.168.192.5
External network virtual IP mask
255.255.254.0
Internal network virtual IP
80.168.3.40
Internal network virtual IP mask
255.0.0.0
Data-sync state
Normal
P-147
Course Name
Five minutes later, run the DSP OMU to check that the OMU board to be replaced is in
the standby state and Data-sync state is set to Data synchronization is successful.
Then go to Scenario: Replacing the Standby OMU in Dual-System Mode.
P-148
Course Name
P-149
Course Name
When the new OMU board runs a different OS from that of the OMU board to be
replaced, it is recommended that you switch the OS of the new OMU board to that of the
old OMU board. This takes care of the user operation habit.
If the OMU board to be replaced is faulty and cannot undergo operation and
maintenance, skip procedures for backing up and saving the data and obtain the latest
backup data for restoring the data. The following procedures take a functional OMU
board as an example.
This slide do not discusses how to switch the OS. We will focus on Old and New OMU
Boards Running the Same OS.
P-150
Course Name
If the OMU board to be replaced is faulty and cannot undergo operation and maintenance,
skip procedures for backing up and saving the data and obtain the latest backup data for
restoring the data. The following procedures take a functional OMU board as an example.
BKP DB to back up system files to the specified path. In this step, set Path of Backup
File and File Name to appropriate values.
Save the performance configuration files, SSL certificate files, license files, and OMU
system data to the LMT PC.

Start the file manager on the LMT. For detailed operations, see File Manager.
Select the files to be downloaded in the corresponding directories and click
Download.
Run the MML command LST OMUAREA to query the OMU active workspace.
Assuming that the OMU active workspace is version_a:
Performance configuration files are saved in the directory
\bam\version_a\ftp\DefaultMeas. Only DefaultMeas_Active.xml and
DefaultMeas_Standby.xml need to be backed up.
SSL certificate files are saved in the directory \bam\version_a\ftp\cert.
License files are saved in the directory \bam\version_a\ftp\license.
P-151
Course Name
If the board is an OMUc board, gently press the PWRBTN button.
P-152
Course Name
Changing the debugging IP address immediately disconnects the LMT PC from the OMU
board. Use the new debugging IP address to connect the LMT PC to the OMU board again.
P-155

GT Network BSC O&amp;M Batch 9 Book File 2 of 2

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

GT Network BSC O&amp;M Batch 9 Book File 2 of 2

Încărcat de

Drepturi de autor:

Formate disponibile

BSC6900 GU Operation and Maintenance

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 GU Operation and Maintenance

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 GU Operation and Maintenance

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 GU Operation and Maintenance

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 GU Operation and Maintenance

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 GU Operation and Maintenance

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 GU Operation and Maintenance

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 GU Operation and Maintenance

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 GU Operation and Maintenance

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 GU Operation and Maintenance

You can run MML commands in batches on this tab page.

You can monitor the performance data on this tab page.

It displays the MML commands in the tree structure.

MML command area

You can input MML commands.

You can click the tab to display the progress of a task.

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 GU Operation and Maintenance

You can click it to download the executable application file

You can click it to display the version of the current LMT.

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 GU Operation and Maintenance

Operation Record tab

Displays commands that have been run.

Help Information tab

Displays the help information on a command

Manual editing area

Command Input box

Displays in the drop-down list all the MML commands available on

Displays the parameters of the current command. You need to set

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 GU Operation and Maintenance

Check syntax of the MML commands before running a batch of MML

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 GU Operation and Maintenance

Through MML commands:

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 GU Operation and Maintenance

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 GU Operation and Maintenance

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 GU Operation and Maintenance

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 GU Operation and Maintenance

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 GU Operation and Maintenance

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 GU Operation and Maintenance

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 GU Operation and Maintenance

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 GU Operation and Maintenance

Through MML Command

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 GU Operation and Maintenance

GT Network BSC O&M Batch 9 Book File 2 of 2

GT Network BSC O&M Batch 9 Book File 2 of 2