BSS Routine Maintenance

BSC6900 BSS routine Maintenance
Contents
INTRODUCTION TO BSS ROUTINE MAINTENANCE
I- Daily BSS Maintenance Guidelines

I-1 Monitoring BSS Alarms
a- Monitoring BSS Fault Alarms
b- Monitoring BSS Event Alarms
c- Collecting BSS Alarm Statistics
I-2 Monitoring the CELL status

I-3 Querying and Saving the BSC6900 and BTS/NodeB Operation Logs
on the M2000
I-4 Querying and Saving other Logs of the BSC6900
I- 5 Querying the Running Status of the BTSs/NodeB
II- Weekly BSS Maintenance
II-1 Checking the Running Status of OMU
II-2 Checking the BSC6900 Board Status
II-3 Checking the BTS/NodeB Board Status
II-4 Checking the BSC6900 Clock
II-5 Checking the BTS/NodeB Clock
II-6 Monitoring the Software Version of Boards
III- Monthly BSS Maintenance

III-1 Analyzing Customer Complaints
III-2 Checking the Disk Space on the Terminal System
III-3 Checking the Connectivity of Port Links
IV- Backing Up and Restoring the GBSS System Data
IV-1 Automatically Backing Up the System Data

IV-2 Manually Backing Up the System Data
IV-3 Manually Restoring the System Data (M2000)
IV-4 Manually Backing Up and Restoring the System Data on the LMT
a. Manually backing up system data
b. Manually restoring the system data

INTRODUCTION TO GBSS ROUTINE MAINTENANCE

The purpose of BSS routine maintenance is to ensure the reliability, stability, and optimum
operating status of the BSC6900 and BTS. In addition, routine maintenance can prevent potential
accidents, identify and solve problems in time, and improve equipment reliability.
BSS routine maintenance is a process in which the BSC6900 and BTS/NodeB are monitored and
maintained. Generally, routine maintenance is performed through the M2000.
The tools for BSS routine maintenance consist of the M2000 client and LMT. The M2000 client
is used to monitor multiple NEs simultaneously. The LMT is used to perform routine
maintenance on a single NE.When the M2000 client detects a fault in an NE, you can log in to
the NE through the LMT to locate, analyze, and rectify the fault.
Based on the maintenance frequency, routine maintenance is classified into daily, weekly, and
monthly maintenance.
I-Daily BSS Maintenance Guidelines

The following tasks would be performing during the daily maintenance:
I-1.Monitoring BSS Alarms
a- Monitoring BSS Fault Alarms
This section describes how to monitor the current fault alarms of the BSC6900
and BTS on the M2000 client.
Prerequisites:
 You have logged in to the M2000 client and the M2000 client communicates with the
related NEs normally.
 You have the permission to query alarms.
Procedure:
1. On the M2000 client, choose Monitor > Query Alarm Logs. The Filter dialog box is
displayed.
2. In the Filter dialog box, set the conditions for querying the alarms.
3. Click OK. The current alarms are displayed on the Query Alarm Logs tab page.
NOTE:
It is recommended that you set the daily used query conditions as a template as
follows:
a. Click Template in the lower left area.
b. Choose Save As... from the shortcut menu.
c. In the displayed dialog box, enter the template name and click OK.
4. Double-click an alarm to view the details in the displayed Details dialog box.
NOTE:
When you click an alarm, you can:

 View the details in the Details area.
 Obtain the handling suggestions about the alarm by clicking the link in the
Handling Suggestion area.
5. Contact the related personnel to acknowledge and handle the alarms not cleared, and
analyze and acknowledge the automatically cleared alarms.
NOTE:
Records of the acknowledged and cleared alarms are not displayed in the window.
6. In the Details dialog box, click Modify to record the fault symptoms, causes, and
handling procedures of the alarm in the Experience area.
7. Repeat 4 through 6 to handle the alarms in succession until there is no fault alarm on the
current fault alarms tab page.
b-Monitoring BSS Event Alarms

This section describes how to monitor the event alarms of the BSC6900 and BTS on the
M2000 client.
Prerequisites:
 You have logged in to the M2000 client and it communicates with the related NEs
normally.
 You have the permission to query alarms.
Procedure:
1. On the M2000 client, choose Monitor > Query Event Logs. The Filter dialog box is
displayed.
2. In the Filter dialog box, set the conditions for querying the alarms.
3. Click OK. The current alarms are displayed on the Query Event Logs tab page.
NOTE:
It is recommended that you set the daily used query conditions as a template as follows:
4. Double-click an alarm to view the details in the displayed Details dialog box.
NOTE:
When you click an alarm, you can:
 View the details in the Details area.
 Obtain the handling suggestions about the alarm by clicking the link in the
Handling Suggestion area.
5. Contact the related personnel to handle and acknowledge the event alarms.
1. In the Details dialog box, click Modify... to record the fault symptoms, causes, and
handling procedures of the alarm in the Experience area.
2. Repeat 4 through 6 to handle and acknowledge the alarms in succession.
c-Collecting BSS Alarm Statistics

This section describes how to collect statistics on the alarms of the BSC6900 and BTS on
the M2000 client based on the alarm severity and alarm type. It also describes how to save
the alarm statistics for easy querying.
Prerequisites:
normally.
 You have the permission to collect alarm statistics.
Procedure:
1. Log in to the M2000 client. Then, choose Monitor > Query Alarm Log Statistics or
Monitor > Query Event Log Statistics on the menu bar. The Statistic Filter dialog box
is displayed.
2. In the Statistic Filter dialog box, set the conditions for querying the alarms.
3. Click OK. The current alarms are displayed on the Query Alarm Log Statistics or
Query Event Log Statistics tab page.
NOTE:
It is recommended that you set the daily used query conditions as a template as follows:
The statistical results are displayed on the Table and Pie tab pages.
 On the Table tab page, the results are displayed in a table.
 On the Pie tab page, the results are displayed in pie charts.
4. Click Save As... in the lower right area and then select the file type and save path to save
the results of alarm statistics as a file.
I-2 Monitoring the CELL status

This section describes how to monitor the cell status and save the result.
Prerequisites:
normally.
 You have the permission to run MML commands.

Procedure:
1. On the M2000 client, choose Maintenance > MML Command. The MML Command
window is displayed.
2. Select the BSC6900 in the left navigation tree. The navigation tree of BSC6900 MML
commands is displayed.
3. Run the MML command DSP GCELLSTAT /DSP UCELL to query the running status of
all cells. Here, set the parameters as follows:
 Leave Index Type empty.
 Select CELLINIT(Cell Initialized) and CHLFAULT(Channel Fault) in the Cell

Attribute parameter.
The execution result is displayed. For the meaning of the result, see the Help Information
in the upper right area of the interface.
NOTE:
Expected result: The initialization status of cells should be Yes and the channel fault
status should be No. If the results are inconsistent, contact the corresponding personnel
for troubleshooting.
4. On the Common Maintenance tab page, right-click and then choose Save As... from the
shortcut menu. Specify the file name and path, and then click Save. The result is saved in
the specified file.
I-3 Querying and Saving the BSC6900 and BTS Operation Logs on the
M2000
The operation logs record the operations that the operation and maintenance personnel
perform on the BSC6900 and BTS. The operation logs are used to identify faults. It is
recommended that you browse and save the operation logs on the M2000 client every day
so that you can check whether any unauthorized operations are performed on the
equipment.
Prerequisites:
 You have logged in to the M2000 client and the M2000 client communicates with the
BSC6900 normally.
 The BSC6900 operation logs are synchronized to the M2000 server. For the method of
synchronizing the operation logs, see the M2000 Operator Guide.
Procedure:
 Operation Mode 1
1. On the M2000 client, choose System > Log Management > Query NE Operation
Logs, the Filter Condition dialog box will be displayed as shown in Figure 1.
Figure 1 Query NE Operation Logs

1. In the Filter Condition dialog box, set the query conditions for the NE operation
logs.
 Based on the operation results, select Success or Failed in the Result area.
 Set the Time Range.
 Click Choose.... The NE Name: Select dialog box is displayed. Select the
target NE in the Available NE Name area, and then click to add it

into the Selected NE Name area. Click OK. Then, the NE is displayed in
the NE Name area.
2. Click OK. The Query NE Operation Logs window displays the query results.
3. Click Save As... in the lower area. Then, enter the name of the log file and specify
the format of the file that saves the information about the operation logs.
The information about the operation logs is saved in the specified folder for easy
querying.
 Operation Mode 2
1. On the M2000 client, choose Maintenance > MML Command. The MML
Command window is displayed.
2. Run the MML command BKP LOGDB to query the running status of the BTSs.
I-4 Querying and Saving other Logs of the BSC6900

This section describes how to query and save other BSC6900 logs on the M2000 client.
Other logs refer to host logs, OMU logs, database logs, and system event logs.
Prerequisites:
 The M2000 client is properly connected to the server.
 You have the right to run the query type MML commands of the BSC6900.
Procedure:
2. Select the BSC6900 in the left navigation pane. The MML command navigation tree of
the BSC6900 is displayed.
NOTE:
If this function is used for the first time, a dialog box will be displayed, prompting you to
download the MML command configuration file of the current version of the NE when
the NE is selected. Click Yes to download the configuration file. After the downloading is
complete, click OK.
3. Run the COL LOG command to query all BAM logs and host logs. Set the parameters as
follows:
 Set Type to ALL.
 Set the Start Time to the start time of the last maintenance, and set the End Time
to the start time of the current maintenance.
Save the result in the zip format in the OMU active workspace installation directory\FTP
directory.
NOTE:
 The information collected in this operation involves BSC6900 running logs,
BSC6900 operation logs, and the corresponding alarms.
 The log files that are not compressed in the BZ2 format in the OMU active
workspace installation directory\common\fam\famlog and the OMU active
workspace installation directory\common\fam\famlogfmt directories will not be
saved.
I- 5 Querying the Running Status of the BTSs

This section describes how to query the running status of all the BTSs under the
same BSC6900 on the M2000 or LMT.
Prerequisites:
 You have logged in to the M2000 client or LMT, and the M2000 client communicates
with the related NEs normally.
Context:
The expected result of this operation is that all the BTSs are normal.
You can query multiple BTSs in one operation. This operation is a convenient and
effective means of maintenance as the LMT or M2000 can display all the faulty
BTSs or BTS boards through this operation. You can learn about the running
status of the BTSs through this operation for convenience of timely replacement
of faulty BTS boards.
Procedure:
 Querying the Running Status of the BTSs Through MML Commands on the M2000
2. Run the MML command DSP BTSSTAT to query the running status of the BTSs.
 Querying the Running Status of the BTSs Through GUI on the LMT
1. On the LMT, click Device Maintenance. The Device Maintenance tab page is
displayed.
2. On the BTS Maintenance tab page, choose BTS Maintenance, and then double-
click Query BTS Running Status. The Query BTS Running Status tab page is
displayed.
3. Select the BTS to be queried in the Query BTS Running Status tab page, and then
click Start.
NOTE:
You can also query the running status of a BTS in the following way: right-click
the corresponding BTS node on the Device Navigation Tree tab page, and then
choose Query BTS Running Status from the shortcut menu.
I-6 Checking the Automatic Backup Function of NEs

This section describes how to check the automatic backup function of NEs on the
M2000 client.
Prerequisite:
You have logged in to the M2000 client and it communicates with the related NEs
normally.
Context:
The scheduled NE backup is a process in which the NE data is saved to the specified
directory on the server as a backup file. By performing this operation, you can prevent
data loss and restore the NEs in case they are not normal.
 The scheduled NE backup is a regular task.
 The task can be performed periodically or only once. The unit of Period can be set to
days, weeks, or months.
 The M2000 supports a maximum of 50 scheduled NE backup tasks.
Procedure:
1. On the M2000 client, choose Maintenance > Task Management. The Task
Management window is displayed.
2. Click NE Backup under the Backup node in the left pane, and then check whether there
are scheduled NE backup tasks in the right pane.
If... Then...
There are scheduled NE The automatic backup function of the

backup tasks, NE is normal.
There is no scheduled NE Perform 3 through 7.

backup task,
3. Click New... in the lower area. The New Task dialog box is displayed.
4. Set the basic information about the task as follows:
a. Enter a name in the Task Name text box.
b. Set Task Type to NE Backup.
c. Set Run Type to Period.
5. Click Next. Set Start Time, Period, and Run Times.

6. Click Next. Select the backup type of By NE Type. The By NE Type dialog box is displayed.
Select the NE to be back up.
7. Click Finish.
II-Weekly GBSS Maintenance
II-1 Checking the Running Status of OMU

This section describes how to check the running status of OMU on the M2000 client.
The check items are the CPU usage, memory usage, hard disk space, operating status,
IP addresses, state of the links between the two OMU, operating status of the service
modules, and startup type.
Prerequisites:
 You have logged in to the M2000 client and it communicates with the BSC6900 normally.
Context:
Table 1 describes the expected result of checking the operating status of the OMU.
Table 1 Expected result of checking the operating status of the OMU
Check Item Expected Result
Operating In the query result, Free space(%) is greater than or equal

status of the to 20%.
OMU
Operating  Computer name, Internal network fixed IP, External network

status and data fixed IP, Internal network virtual IP, and External network
synchronization virtual IP in the query result comply with the planning.
status of the
 Operational state, Internal network virtual IP state, External
active and
standby OMU network virtual IP state, Internal network link state, External
Table 1 Expected result of checking the operating status of the OMU
subsystems network link state, and Backup network link state are
Normal.
 Data-sync state is Data synchronization is successful.
Table 2 describes the expected result of checking the operating status of the service
modules of the OMU.
Table 2 Expected result of checking the operating status of the service modules of the
OMU boards
State of the  State: Started

active OMU
 Startup Type: Automatic
State of the For sntp, ftp_server, omu_manager, and software:

standby
 State: Started
OMU
 Startup Type: Automatic
For other services rather than sntp, ftp_server,

omu_manager, and software:
 State: Stopped
 Startup Type: Disabled
Configuration For configuration of active and standby OMU servers:

of active and Consistent.
standby
OMU servers
Procedure:
2. Select the BSC6900 in the left navigation tree. The navigation tree of BSC6900 MML
3. Run the MML command DSP OMUSRV to query the operating status of the OMU.
4. Run the MML command DSP OMU to query the operating status and data
synchronization status of the active and standby OMU subsystems.
5. Run the MML command DSP OMUMODULE to query the operating status and startup
type of the modules of the active and standby OMU subsystems.
NOTE:
 In the case of active/standby OMU, you can also run the MML command CHK
PEERCFG to query the configuration information about the active and standby
OMU.
 For the reference of the query result, see Table 1. If any fault occurs, contact the
corresponding personnel for troubleshooting.
II-2 Checking the BSC6900 Board Status

This section describes how to check the running status of the BSC6900 boards on the
M2000 client or LMT. In the case of DPUc and DPUd boards, you should also check
the running status of the DSPs.
Prerequisites:
 You have logged in to the M2000 client or LMT, and it communicates with the BSC6900
normally.
Procedure:
 Checking the Board Status Through MML Commands on the M2000
2. Select the BSC6900 in the left navigation tree. The navigation tree of BSC6900
MML commands is displayed.
3. Run the MML command DSP BRD to query the status of all the boards in the
specified subrack. Here, specify Subrack No. and leave Slot No. empty.
4. Run the MML command DSP DSP to query the DSP state of the DPUc and DPUd
boards in the specified subrack. Here, specify Subrack No. and leave Slot No.
empty.
 Checking the Board Status Through GUI on the LMT
displayed.
2. On the BSC Maintenance tab page, choose BSC Maintenance > Maintain Device,
and then double click Query BSC Board Information. The Query BSC Board
Information dialog box is displayed.
3. Set the parameters on the Query BSC Board Information tab page, and then click
Query.
NOTE:
You can also query the board status in the following way: right-click a board on the
BSC device panel and then choose Query BSC Board Information from the shortcut
menu.
4. On the BSC Maintenance tab page, choose BSC Maintenance > Maintain User
Resources, and then double-click Query DSP Resources. The Query DSP
Resources dialog box is displayed.
5. Set the parameters on the DSP Resource Info tab page, and then click Query.
6. The result is displayed in the Query DSP Resources tab page.
Follow-up Procedure
 If any fault occurs on the boards, contact the corresponding personnel to rectify the fault.
Ensure that the CPUs of all the boards are normal.
 If any fault occurs on the DSPs of the DPUc and DPUd boards, contact the corresponding
personnel to rectify the fault. If the DSPs cannot be restored to normal and the services
are adversely affected, replace the board.
II-3 Checking the BTS/NodeB Board Status

This section describes how to check the running status of the BTS boards on the
M2000 client or LMT.
Prerequisites:
with the BSC6900 normally.
Procedure:
 Checking the Board Status Through MML Commands on the M2000
3. Run the MML command DSP BTSBRD/DSP BRD to query the status of all the
boards in the specified subrack.
 Checking the Board Status Through GUI on the LMT
displayed.
2. The BSC Device Panel tab is displayed.
3. Click BSC under Device Navigation Tree. Click the required BTS/NodeB, and the
corresponding BTS Device Panel tab is displayed on the right.
4. Right-click a board in position in the BTS/NodeB device panel, and then choose
Query Board Information. The Query Board Information dialog box is displayed,
showing details of the board.
Follow-up Procedure
If faults occur to the boards, contact corresponding personnel to clear the faults.
II-4 Checking the BSC6900 Clock

This section describes how to check the clock status of the GCGa/GCUa board on the
M2000 client or LMT.
Prerequisites:
 You have logged in to the M2000 client or LMT, and it communicates with the BSC6900
normally.
Context:
NOTE:
 It is recommended that you query the clock status of only the GCUa/GCGa board. For the
GCUa/GCGa board, you can query the status of the clock source used by the current
system and the clock source switching mode of the current clock phase-locked loop.
 The GCUa/GCGa boards are fixedly configured in slots 12 and 13 in the MPS.
Procedure:
 Checking the Clock Status Through MML Commands on the M2000
3. Run the MML command DSP CLK to query the status of the clock boards in the
MPS. Here, set Subrack No. to 0 and specify Slot No..
 Checking the Clock Status Through GUI on the LMT
displayed.
2. On the BSC Maintenance tab page, choose BSC Maintenance > Maintain Device,
and then double-click Query BSC Board Clock Status. The Query BSC Board
Clock Status dialog box is displayed.
3. Set the parameters on the Query BSC Board Clock Status tab page, and then
click Query.
4. The result is displayed in the Query BSC Board Clock Status tab page.
NOTE:
If the clock source state of any level is Unavailable or the Phase-locked loop state of
current clock is Unknown, you can infer that the clock source is lost. Contact the
corresponding personnel for troubleshooting. Ensure that the status of the clock source
stratum and the clock working state are Available and Fast Tracking respectively.
II-5 Checking the BTS/NodeB Clock

This section describes how to check the clock status of the BTS on the M2000 client or LMT.
Prerequisites:
Procedure:
 Checking the Clock Status Through MML Commands on the M2000

3. Run the MML command DSP BTSCLK/DSP CLKSTAT to query the status of
the BTS/NodeB Clock.
 Checking the Clock Status Through GUI on the LMT
displayed.
2. On the BTS Maintenance tab page, choose BTS Maintenance > Query BTS
Attributes. The Query BTS Attributes tab page is displayed.
3. Set the parameters on the Query BTS Attributes tab page, and then click Query
to query the status of the BTS Clock.
Follow-up Procedure:
NOTE:
If the status of the clock source stratum is Unavailable or the Management state is Unblocked
or Shutdown, you can infer that the clock source is lost. Contact the corresponding personnel for
troubleshooting. Ensure that the status of the clock source stratum and the clock working state are
Available and Free oscillation respectively.
II-6 Monitoring the Software Version of Boards

This section describes how to monitor the software version of BTS boards to avoid
version mismatch after capacity expansion or software upgrade.
Prerequisites:
 You have the rights to run MML commands.
Context:
The expected result of this operation is that all the boards are of the same correct
software version.
Procedure:
 Checking the Software Version Through MML Commands on the M2000
2. Select the BTS node in the left navigation tree. The navigation tree of MML
3. Run the MML command LST BTSSW/LST VER to check the version of the
BTS/NodeB software.
 Checking the Software Version Through GUI on the LMT
displayed.
2. On the BTS Maintenance tab page, choose BTS Maintenance, and then double-
click Query Board Running Software Version. The Query Board Running
Software Version tab page is displayed.
3. Set the parameters on the Query Board Running Software Version tab page, and
then click Start.
4. The result is displayed in the Operation Result area.

5. To stop querying, click Stop.
Follow-up Procedure:
Upgrade the software at a suitable time.
III-Monthly GBSS Maintenance
III-1 Analyzing Customer Complaints

This section describes how to find the causes and tendency of faults. The task helps to
handle problems at points of frequent faults.
Prerequisite:
The records of customer complaints are obtained.
Procedure:
1. Based on customer complaints, collect information of monthly faults and identify the
scope and category of the faults.
2. Determine the causes of faults by analyzing and comparing possible causes.
3. Collect statistics on the monthly faults and analyze the fault tendency.
4. Analyze the points of frequent faults, locate problems, and handle the problems.
5. Summarize the troubleshooting experience and offer suggestions.
III-2 Checking the Disk Space on the Terminal System

The disk space available on the terminal system should meet the specified
requirements.
Prerequisites:
 For the M2000 client, the available space on the hard disk should be at least 50% of the
total capacity.
 Minimum configuration requirement for the independent partitioning of the OMU: The
available space should be at least 20% of the capacity of each partition.
Procedure:
1. Check the available space on the hard disk of the M2000 client. If the available space is
lower than 50% of the total capacity, delete the temporary files, unnecessary software
programs and unnecessary backup files.
2. Check and clean up the OMU Hard Disk by referring to Regularly Checking and Cleaning
Up the OMU Hard Disk. Delete the temporary files and unnecessary backup files.
III-3 Checking the Connectivity of Port Links

This section describes how to check the connectivity of port links.
Context:
 You have logged in to the M2000 client. The communication between the M2000 client
and the BSC6900 is normal.
 You have the authorities to run MML commands.
 The port is enabled with Port Load Sharing function.
Procedure:
2. Run the commands PING IP and TRC IPADDR to check the connectivity of port links. In
this step, set the related parameters and specify Forward route address.
IV- Backing Up and Restoring the GBSS System Data

This section describes how to back up the system data on the M2000 client. The
system data consists of the configuration data, performance data, and alarm data.
IV-1 Automatically Backing Up the System Data
You can enable the automatic backup of the BSC6900 and BTS by creating the
corresponding backup tasks on the M2000 client.
Prerequisites:
normally.
 You have the permission to back up data.
Context:
The NE backup task is a process in which the NE data is saved to the specified
directory on the M2000 server as a backup file. Through this task, you can prevent
data loss and restore the NEs in case they are not normal.
Procedure
1. On the M2000 client, choose Maintenance > Task Management. The Task
2. Click New... in the lower area. The New Task dialog box is displayed.
3. Set the basic information about the task as follows:
a. Enter a name in the Task Name text box.
b. Set Task Type to NE Backup.
c. Set Run Type to Period.
4. Click Next. Set Start Time.
5. Click Next to select backup type. The following backup types are available: Backup
ALL NE, By NE Type, and By NE.
6. Click Finish.
IV-2 Manually Backing Up the System Data
The M2000 client supports not only the periodical backup of NE data but also the
manual backup of NE data as required.
Prerequisites:
normally.
 The FTP server is set up on the M2000.

 You have the permission to back up data.
Context:
The M2000 server is used as the FTP server to connect the client and the NE.
Procedure
1. On the M2000 client, choose Maintenance > Backup Management. The Backup
2. Click the NE Backup List tab, as shown in Figure 1.
Figure 1 NE Backup List
3. Expand the navigation tree and select an NE.
 You can press Ctrl to select multiple NEs at a time. To select all the NEs, click the
root node.
 If the selected NE contains sub NEs, a dialog box is displayed, prompting whether
to back up the data of all the sub NEs under the selected NE. Under this NE, you
can also select only the sub NEs whose data needs to be backed up.
4. Click Backup. The Confirm dialog box is displayed. Click Yes.

When the backup task is started, the real-time progress and detailed information about
the backup task are displayed in the Immediate Task in the Backup Management
window.
IV-3 Manually Restoring the System Data (M2000)
The M2000 client supports not only the periodical backup of NE data but also the
manual backup of NE data as required.
Prerequisites:
normally.
 The FTP server is set up on the M2000.
 You have the permission to restore data.
 The NE data has been on the server.
Context:
The M2000 server is used as the FTP server to connect the client and the NE.
Procedure:
1. On the M2000 client, choose Maintenance > Backup Management. The Backup
2. Click the NE Backup List tab, as shown in Figure 1.

Figure 1 NE Backup List
3. Expand the navigation tree and select an NE.
 You can press Ctrl to select multiple NEs at a time. To select all the NEs, click the
root node.
 If the selected NE contains sub NEs, a dialog box is displayed, prompting whether
to back up the data of all the sub NEs under the selected NE. Under this NE, you
can also select only the sub NEs whose data needs to be backed up.
4. Select a backup file in the list.
5. Click Restore in the dialog box, and click Yes in the displayed Confirm dialog box.
CAUTION:
The NE restarts after you perform the restore operations.
IV-4 Manually Backing Up and Restoring the System Data on the

LMT
a- Manually backing Up the System Data
This section describes how to back up the BSC6900 configuration data, performance
data, and alarm data through MML commands or the omu_backup_restore_tool.
Prerequisites:
 If you perform this task by running the MML command:
You have logged in to the LMT by referring to LMT Login and Exit.
 If you perform this task by using the omu_backup_linker tool:
You have logged in to the OMU by referring to Logging In to the OMU.
Context:
CAUTION:
 When the OMU works in active/standby mode, the system data must be backed up on the
active OMU.
 You must back up the OMU data manually before expansion, upgrade or loading to avoid
the failure of system data backup.
Procedure:
 Backing up the system data through an MML command
1. Run the BKP DB command to set Path of Backup File and Backup File Name to
back up the data in the specified directory on the OMU hard disk.
2. Obtain the backup data file from the specified directory by referring to
Transferring and Backing Up Files.
 Backing up the data by using the omu_backup_linker tool
1. Use the USB installation disk to install the OMU operating system by referring to
Starting the omu_backup_linker Tool.
2. Type backup and press Enter after the message "Please input a valid
bkp_res_type:" is displayed.
3. Type the save path and names of the backup files, and then press Enter. The
system data starts to be backed up. After the backup is complete, a message is
displayed, indicating whether the backup is successful. If the message "Backup
OMU database succeed!" is displayed, it indicates that the system data is
successfully backed up on the OMU hard disk.
Example:
Back up the OMU data to /mbsc/bam through the omu_backup_restore_tool and the
name the file as omu.bak. An example is given, as shown in the following figure.
omd_test_name /mbsc/bam/common/services # ./omu_backup_linker
# The backup/restore option
# backup : Backup OMU database
# restore : Restore OMU database
# Please select one option to backup or restore OMU database, if you don't know it,
please consult the administrator.
Please input a valid bkp_res_type : backup
# The backup file pathname.
# eg: d:/mbsc/bam/omu.bak, in windows;
# eg: /mbsc/bam/omu.bak, in linux.
Please input a valid backup file pathname : /mbsc/bam/omu.bak
Backup omu database [100%]
Backup OMU database succeed!
omd_test_name /mbsc/bam/common/services #
b- Manually restoring the System Data
This section describes how to restore the system data through the data backup file.
The system data consists of configuration data, performance data, and alarm data.
Prerequisites
 You have logged in to the OMU by referring to Logging In to the OMU.
 You have logged in to the LMT by referring to LMT Login and Exit.
Context
Restoring the BSC6900 system data will disrupt the services on the BSC6900
operation and maintenance system. The data on the host may be inconsistent with the
data on the BAM after the system data is restored. Thus, the services will be greatly
impacted. Therefore, you are advised to restore the system data when the traffic
volume is low.
Procedure
1. Stop the omud on the active and standby OMUs by referring to Stopping the omud.
2. Restore the system data through the omu_backup_linker.
a. Use the USB installation disk to install the OMU operating system by referring to
Starting the omu_backup_linker Tool.
b. Type restore and press Enter after the message "Please input a valid
bkp_res_type:" is displayed.
c. Type the directory and names of the backup files and press Enter after the message
"Please input backup file pathname:" is displayed. The system data starts to be
restored. A message is displayed to indicate whether the data restoration is
successful. If the message "Restore OMU database succeed!" is displayed, it
indicates that the data restoration is successful.
3. Start the omud on the active and standby OMUs by referring to Starting the omud.
4. Run the REQ CMCTRL command to obtain the data configuration rights.
5. Check the consistency between the BSC6900 host data and the OMU data.
NOTE:
After data restoration, check whether the BSC6900 host data is consistent with the
OMU data. If not, load the restored data to the BSC6900 host.
a. Run the ACT CRC command to check whether the host data is consistent with the
OMU data.
 If the data is consistent, end this task.

 If the data is inconsistent, go to 5.b.
b. Run the FMT DATA command to format the data in the OMU database so that the
data can be loaded into the host.
c. If data inconsistency occurs in only one subrack, run the RST SUBRACK
command to reset this subrack. Before running the command, set Subrack No.. If
data inconsistency occurs in multiple subracks, run the RST BSC command to
reset the BSC.
Example
Restore the OMU data through the omu.bak file under /mbsc/bam. An example is
given, as shown in the following figure:
omd_test_name ~ # /etc/rc.d/omud stop
Shutting down mbsc daemon..........
omd_test_name ~ # cd /mbsc/bam/common/services
omd_test_name /mbsc/bam/common/services # ./omu_backup_linker
# The backup/restore option
# backup : Backup OMU database
# restore : Restore OMU database
# Please select one option to backup or restore OMU database, if you don't know it,
please consult the administrator.
Please input a valid bkp_res_type : restore
# The backup file pathname.
# eg: d:/mbsc/bam/omu.bak, in windows;
# eg: /mbsc/bam/omu.bak, in linux.
Please input a valid backup file pathname : /mbsc/bam/omu.bak
Restore omu database [100%]
Restore OMU database succeed!

omd_test_name /mbsc/bam/common/services # /etc/rc.d/omud start
Starting mbsc daemon

BSS Routine Maintenance

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

BSS Routine Maintenance

Hochgeladen von

Copyright:

Verfügbare Formate

BSC6900 BSS routine Maintenance

INTRODUCTION TO BSS ROUTINE MAINTENANCE

I- Daily BSS Maintenance Guidelines

I-2 Monitoring the CELL status

II- Weekly BSS Maintenance

II-1 Checking the Running Status of OMU

II-2 Checking the BSC6900 Board Status

II-3 Checking the BTS/NodeB Board Status

II-4 Checking the BSC6900 Clock

II-5 Checking the BTS/NodeB Clock

II-6 Monitoring the Software Version of Boards

III- Monthly BSS Maintenance

III-1 Analyzing Customer Complaints

III-2 Checking the Disk Space on the Terminal System

III-3 Checking the Connectivity of Port Links

IV- Backing Up and Restoring the GBSS System Data

IV-1 Automatically Backing Up the System Data

b. Manually restoring the system data

INTRODUCTION TO GBSS ROUTINE MAINTENANCE

I-Daily BSS Maintenance Guidelines

When you click an alarm, you can:

b-Monitoring BSS Event Alarms

c-Collecting BSS Alarm Statistics

I-2 Monitoring the CELL status

 You have the permission to run MML commands.

 Leave Index Type empty.

 Select CELLINIT(Cell Initialized) and CHLFAULT(Channel Fault) in the Cell

target NE in the Available NE Name area, and then click to add it

I-4 Querying and Saving other Logs of the BSC6900

I- 5 Querying the Running Status of the BTSs

I-6 Checking the Automatic Backup Function of NEs

There are scheduled NE The automatic backup function of the

There is no scheduled NE Perform 3 through 7.

5. Click Next. Set Start Time, Period, and Run Times.

II-Weekly GBSS Maintenance

II-1 Checking the Running Status of OMU

 You have the permission to run MML commands.

Table 1 Expected result of checking the operating status of the OMU

Check Item Expected Result

Operating In the query result, Free space(%) is greater than or equal

Operating  Computer name, Internal network fixed IP, External network

Table 1 Expected result of checking the operating status of the OMU

Check Item Expected Result

 Data-sync state is Data synchronization is successful.

modules of the OMU.

Check Item Expected Result

State of the  State: Started

State of the For sntp, ftp_server, omu_manager, and software:

For other services rather than sntp, ftp_server,

 Startup Type: Disabled

Configuration For configuration of active and standby OMU servers:

II-2 Checking the BSC6900 Board Status

 You have the permission to run MML commands.

 Checking the Board Status Through MML Commands on the M2000

 Checking the Board Status Through GUI on the LMT

6. The result is displayed in the Query DSP Resources tab page.

II-3 Checking the BTS/NodeB Board Status

 You have the permission to run MML commands.

 Checking the Board Status Through MML Commands on the M2000

 Checking the Board Status Through GUI on the LMT

2. The BSC Device Panel tab is displayed.

II-4 Checking the BSC6900 Clock