Professional Documents
Culture Documents
GBSS Weekly Maintenance Guidelines
GBSS Weekly Maintenance Guidelines
b. In the NE Health Check window, click on the upper left. The Create Task dialog
box is displayed.
c. In the displayed dialog box, choose Maintenance from the Scenario Management
drop-down list. The Task Name text box will be automatically filled by the system
based on the application scenario and the task creating time (accurate to seconds).
d. Select target NEs for health check in the Select NE area.
e. In the Time Setting area, select Scheduled.
f. Click Next. In the displayed dialog box, specify Start Time and Run Times, and set
Period to Week. Then, Click Finish.
NOTE:
The executed health check task is listed under the Finished Tasks node in the navigation tree
on the left side.
If... Then...
The HTML format is selected Select the report from the report list and view the report in one
of the following ways:
Click Open to directly open the report in HTML format.
Click Save As and select the path for saving the report in
the displayed Save dialog box to save the report in HTML
format.
The DOC format is selected Select the report from the report list and view the report in one
of the following ways:
Click Open to directly open the report in DOC format.
Click Save As and select the path for saving the report in
the displayed Save dialog box to save the report in DOC
format.
NOTE:
The health check report is compressed as a .zip file. To view the report, double-click
the .zip file, and double-click the report file "index.html" in the zip file browser.
2. Checking the Running Status of the OMU
1. On the M2000 client, choose Trace and Maintenance > Maintenance > MML Command
(application style) or Maintenance > MML Command (traditional style). The MML
Command window is displayed.
2. Select the BSC6900/BSC6910 in the left navigation tree. The navigation tree of
BSC6900/BSC6910 MML commands is displayed.
NOTE:
If this method is used for the first time, you will be prompted with a message The MML
command file of the current version does not exist. Are you sure you want to download
this file from the server?. Click Yes to start downloading the file. Click OK when the
download is complete.
3. Run the DSP OMUSRV command to query the OMU running status.
Expected result: Free space of each partition on the OMU hard disk is at least 20%.
4. Run the DSP OMU command to query the basic configuration information, operational state,
and data synchronization status of active and standby OMU subsystems.
Expected result:
a. Computer name, Internal network fixed IP, External network fixed IP, Internal
network virtual IP, and External network virtual IP in query results are the same
as planned.
b. The values of Operational state for active and standby OMUs are Active normal
and Standby normal, respectively. For an independent OMU, the value of
Operational state is Normal. The values of Internal network virtual IP state,
External network virtual IP state, Internal network link state, External network
link state, and Backup network link state are all Normal.
c. The value of Data-sync state is Data synchronization is successful.
5. Run the DSP OMUMODULE command to query the running status and startup types of the
modules of active and standby OMUs.
Table 1 provides the expected results.
Table 1 Expected results of checking running status of service modules of the OMUs
Status of the active The value of State of all service modules is Started.
OMU The value of Startup Type is Automatic.
State of the standby For debug_log, ftp_server, omu_manager, sntp, and software:
OMU The value of State is Started.
The value of Startup Type is Automatic.
For other services rather than debug_log, ftp_server, omu_manager, sntp, and
software:
The value of State is Stopped.
The value of Startup Type is Disabled.
6. Optional: When the OMU works in active/standby mode, run the CHK PEERCFG command
to query the configuration information about the active and standby OMUs.
Expected result: Values of the configure items of active and standby OMUs are Consistent.
NOTE:
If this method is used for the first time, you will be prompted with a message The MML
command file of the current version does not exist. Are you sure you want to
download this file from the server?. Click Yes to start downloading the file. Click OK
when the download is complete.
c. Run the DSP BRD command with Status set to FAULT(FAULT) to query all the
faulty boards.
Expected result: No board Status is FAULT(FAULT).
d. For a BSC6900, run the DSP DSP command with Subrack No. specified to query
the DSP status of the DPUa/DPUc/DPUd/DPUf/DPUg board in a specific subrack.
Expected result: DSP operational state is Normal.
e. For a BSC6910, run the DSP SUBSYS command to query the DSP status of the
faulty board in a specific subrack. In this step, set Operator Type to BYPOS(By
Position) and Status to FAULT(FAULT), and specify Subrack No..
Expected result: No DSP State is FAULT(FAULT).
2. Checking the board status using the LMT GUI
a. On the LMT, click Device Maintenance. The Device Maintenance tab page is
displayed.
b. On the BSC Maintenance tab page, choose BSC Maintenance > Maintain Device
> Query BSC Board Information. The Query BSC Board Information dialog box is
displayed.
c. Set parameters in the Query BSC Board Information dialog box and click Query to
query the board information.
NOTE:
You can also query the board status in the following way: right-click a board on the BSC
device panel and choose Query BSC Board Information from the shortcut menu.
Expected result:
i. For a BSC6900, if the board works in independent mode, CPU status is
Normal; if the board works in active/standby mode, CPU status of the active
board is Active normal and CPU status of the standby board is Standby
normal.
ii. For a BSC6910, if the board works in independent mode, Board status is
Normal; if the board works in active/standby mode, Board status of the
active board is Active normal and Board status of the standby board is
Standby normal.
NOTE:
If this method is used for the first time, you will be prompted with a message The MML
command file of the current version does not exist. Are you sure you want to
download this file from the server?. Click Yes to start downloading the file. Click OK
when the download is complete.
c. Run the DSP CLK command to query the status of clock boards in the MPS. In this
step, set Subrack No. to MPS Subrack No. and specify Slot No..
2. Checking the source clock status using the LMT GUI
a. Click Device Maintenance. The Device Maintenance window is displayed.
b. Right-click a board on the BSC device panel and choose Query BSC Board Clock
Status from the shortcut menu to query the BSC board clock status.
NOTE:
2.1. You can press and hold Ctrl and click the root node to select multiple NEs at a time. To
select all the NEs, click the root node.
2.2. If the selected NEs contain sub-NEs, a dialog box will be displayed, informing you
whether to back up the data of all the sub-NEs under the selected NE. You can also
select some of the sub-NEs whose data need to be backed up.
Expected result: After the backup is completed, you can obtain the specific system backup file in
the specified directory.
2. Restoring the system data by running MML commands
2.1. Run the RTR DB command with File Name specified to restore the system data on the
OMU server.
2.2. Run the RST BSC command so that the restored configuration data takes effect.
Expected result: After the system data is restored, the NE is working correctly and services are
running.
Expected result: After the automatic backup is completed, you can obtain the backup file of the
target NE in a specified directory.
2. Manually backing up BSC6900/BSC6910 license information on the LMT
a. Log in to the BSC6900/BSC6910 LMT and click FTP Tool at the upper right corner to
start the local FTP server.
b. Run the BSC6900/BSC6910 command ULD LICENSE to upload the
BSC6900/BSC6910 license file to the PC through FTP. In this step, enter the IP
address of the local PC in IP Address, a directory for saving the backup file in
Directory, and a file name in File Name.
NOTE:
The file name must contain .dat, for example, BSC01LIC.dat.
3. Expected result: You can obtain the backup file of the target NE in the specified directory.
4. Backing up eGBTS license allocation information
a. On the M2000 client, choose Software Management > NE License > eGBTS
(application style) or License > NE License Management > eGBTS (traditional
style). The eGBTS License Management window is displayed.
b. In the left navigation tree in the eGBTS License Management window, click an
eGBTS. The operator and license information about the eGBTS is displayed in the
right pane. Set a local path and file name for saving the backup file. Then, click OK.
NOTE:
After the file export starts, you can check the progress on the FTP Task tab page in the
eGBTS License Management window. After the export is completed, you can check the
exported information locally.
The eGBTS license allocation information is exported as in the .csv format.
5. Expected result: You can obtain the backup file of the target NE in the specified directory.
NOTE:
The query result can be displayed in three forms: table, line chart, and bar chart.
4. Compare the performance counter values with those required for the office. If the values are
inconsistent, contact the related engineers for handling.
NOTE:
The statistical results are displayed on the Table and Pie tab pages.
i. On the Table tab page, the results are displayed in a table.
ii. On the Pie tab page, the results are displayed in pie charts.