Professional Documents
Culture Documents
Mobile Broadband
Wireless Base Station System
Operation Manual
Version 3.32
ZTE CORPORATION
ZTE Plaza, Keji Road South,
Hi-Tech Industrial Park,
Nanshan District, Shenzhen,
P. R. China
518057
Tel: (86) 755 26771900
Fax: (86) 755 26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
The contents of this document are protected by copyright laws and international treaties. Any reproduction or distribution of
this document or any portion of this document, in any form by any means, without the prior written consent of ZTE CORPO-
RATION is prohibited. Additionally, the contents of this document are protected by contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE CORPORATION
or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions are dis-
claimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-in-
fringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the use of or reliance on the
information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the subject
matter of this document. Except as expressly provided in any written license between ZTE CORPORATION and its licensee,
the user of this document shall not acquire any license to the subject matter herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
Revision History
Serial Number:20090409-014
Contents
Preface.............................................................. I
Accessing OMM..................................................1
Starting the ZXMBW BSS Server....................................... 1
Starting the ZXMBW BSS Client ........................................ 2
Logging in to ZXMBW BSS ............................................... 3
Configuration Management ...............................7
Searching for a Radio Parameter....................................... 7
Batch Configuring Segment Radio Parameters through
Copy and Paste ...................................................... 9
Applying for the Mutex Rights .........................................10
Configuring Environment Sensor Thresholds......................12
Managing the Administrative Status of an NE ....................15
Configuring a Dry Contact...............................................19
Configuring the Power Mode............................................20
Exporting the BTS IP Address Information.........................21
Synchronizing Configuration Data to NEs ..........................22
Backing Up Configuration Data ........................................24
Restoring Configuration Data...........................................26
Exporting and Importing BTS Data ...................................27
Function Overview .....................................................27
Exporting BTS Data....................................................28
Importing BTS Data ...................................................29
Performance Management............................... 31
Customizing the Performance Data Collection Task .............31
Setting the Performance Threshold ..................................34
Querying Raw Performance Data .....................................37
Diagnosis Testing ............................................ 41
Testing a Board Manually ................................................41
Customizing an Automatic Test Task .................................42
Obtaining the Actual GPS Longitude and Latitude
Information ..........................................................45
Accessing OMM
Table of Contents
Starting the ZXMBW BSS Server........................................... 1
Starting the ZXMBW BSS Client ............................................ 2
Logging in to ZXMBW BSS ................................................... 3
END OF STEPS
FIGURE 4 LOGIN
END OF STEPS
BSS. For the users with different user accounts, the operation
rights may be different.
Steps 1. In the Login dialog box as shown in Figure 5, set User Name,
Password and Server Address. Table 1 shows the descrip-
tion of the parameters.
FIGURE 5 LOGIN
END OF STEPS
Configuration
Management
Table of Contents
Searching for a Radio Parameter........................................... 7
Batch Configuring Segment Radio Parameters through Copy
and Paste .......................................................................... 9
Applying for the Mutex Rights .............................................10
Configuring Environment Sensor Thresholds..........................12
Managing the Administrative Status of an NE ........................15
Configuring a Dry Contact...................................................19
Configuring the Power Mode................................................20
Exporting the BTS IP Address Information.............................21
Synchronizing Configuration Data to NEs ..............................22
Backing Up Configuration Data ............................................24
Restoring Configuration Data...............................................26
Exporting and Importing BTS Data .......................................27
3. In the dialog box, set the parameters. Table 2 shows the de-
scription of the parameters.
Param- Description
eter
3. Choose Data Process > Copy or click the icon on the tool-
bar.
4. Select the SEGMENT[1] node, and then choose Data Process
> Paste or click the icon on the toolbar.
Note:
During the data paste process, BS ID and Preamble Index
are filtered out. That is, the original BS ID and Preamble
Index that are set during the segment creation are reserved
instead of overwritten.
secures the rights of the client. After a client obtains the mutex
rights, the other clients do not have the mutex rights. This ensures
the data consistency in the database.
Prerequisites � The OMC client must be started and must have accessed the
server.
� Multiple districts must be added.
Context You can apply for the mutex rights if a district exists in the system.
You do not need the mutex rights to add a district. After adding a
district, you will obtain the mutex rights of the district automati-
cally. In the left device tree of the Configuration Management
window, if a district is marked with a lock, the lock indicates the
mutex rights of the district. If a district is not marked with a lock,
it indicates that the user does not have the mutex rights of the dis-
trict and the user can apply for the mutex rights. Before the user
obtains the mutex rights of the district, the user does not have the
write rights for the district and the NEs under the district.
The mutex rights include the special strong rights. If a user has
the strong rights, the user has the mutex rights of all districts that
are managed by NetNumen ™ M31 (WiMAXOMM-B). The strong
rights can be released with by the user that is with strong rights,
while other users cannot take or release the rights forcefully.
Steps 1. Choose Views > Configuration Management to display the
Configuration Management window.
2. Choose Configuration > Mutex Management to display the
Mutex Management window.
3. In the Mutex Management window, select the district that
you want to obtain the mutex rights, and then click Apply.
If the green icon is displayed in the Status column, as shown
in Figure 10, it indicates that you have obtained the mutex
rights successfully.
Configuring Environment
Sensor Thresholds
Short Description Through this function, you can configure or batch configure BTS
sensor thresholds, realizing centralized configuration manage-
ment.
Prerequisites � The OMC client must be started and must have accessed the
server.
� WBTSB nodes must be added to the tree of the Configuration
Management window.
Context After you configure or batch configure BTS sensor thresholds and
perform the synchronization operation, the data is synchronized
to the NE. Then, the alarm module monitors the environment ac-
cording to the configure BTS sensor thresholds.
Table 3 lists the BTS environment sensors and the thresholds.
Se-
rial Config-
Nu- Default ured or
m- Sensor Default High Not by
ber Type Description Low Limit Limit Default
Room door -
1 Digital sensor - No
Rack door –
2 Digital sensor – No
Flooding –
4 Digital sensor – No
Infrared –
5 Digital sensor – No
Rack
temperature
6 Analog sensor -5℃ 60℃ No
Room
temperature
7 Analog sensor -5℃ 55℃ No
Room
humidity
8 Analog sensor 10% 90% No
Fan rotate
9 Analog speed 1000 rpm 6500 rpm Yes
6. You can click Default to set the sensor thresholds to the default
values. Modify the required threshold values and click OK to
save the modification.
7. In the BTS list pane, you can select more than one records,
right-click and choose Batch Modify Sensor. The Batch
Modify Sensor dialog box is displayed, as shown in Figure 13.
8. You can click Default to set the sensor thresholds to the default
values. Modify the required threshold values and click OK to
complete the batch modification.
END OF STEPS
FIGURE 14 NE STATUS
Cut- The options The default value is New site. In the case
over are New of Swapping site, the traffic volume is
status site and large during the initial stage of cutover.
Swapping Hence, the site requires special attention.
site. In the case of New site, the traffic volume
is small during the initial stage. The
maintenance personnel need to distinguish
END OF STEPS
Result After exporting the BTS IP address information, you can view the
file in the specified file path.
Synchronizing Configuration
Data to NEs
Short Description You can synchronize the correct configuration data to WBTSB. After
the synchronization is successful, the WBTSB can provide services
normally.
Prerequisites � The OMC client must be started, and the client must have ac-
cessed the server.
� The configuration data must be correct and the communication
link must be normal.
Context Synchronization of the OMC configuration data is performed based
on the internal message mechanism. The system compares the
version table information. After the information is consistent, it
Note:
If you do not select any node, the synchronization cannot pro-
ceed.
END OF STEPS
Backing Up Configuration
Data
Short Description With this function, you can save the configuration data so that the
system can restore the configuration data when required.
Prerequisites � The OMC client must be started and must have accessed the
server.
� The configuration data to be backed up must be ready.
Context This operation exports the data from the database in SQL state-
ments, which can be used to restore the database.
Steps 1. Choose Views > Configuration Management to display the
Configuration Management window.
2. On the configuration tree, right-click the OMM_WiMAX node
and choose Backup and Restore Data. Then, the Data
Backup and Restore dialog box is displayed, as shown in
Figure 23.
Restoring Configuration
Data
Prerequisites � The OMC client must be started and must have accessed the
server.
� The configuration data to be restored must be ready and the
version must be correct.
Context Restoring configuration data is the reverse process of backing up
configuration data. The version of the configuration data to be
restored must be the same as the version of the current OMC.
Otherwise, the data cannot be restored successfully.
Steps 1. Choose Views > Configuration Management to display the
Configuration Management window.
2. On the configuration tree, right-click the OMM_WiMAX node
and choose Backup and Restore Data. Then, the Data
Backup and Restore dialog box is displayed, as shown in
Figure 25.
4. Select the file that is used for restoration, and then click OK.
In the confirmation dialog box that appears, click OK.
After the configuration data restoration is completed, the
restoration success message is displayed.
5. After the data restoration is completed, click Close to close the
Data Backup and Restore dialog box.
END OF STEPS
Result After the BTS data is exported successfully, the BTS data file is
generated in the specified path.
3. Click Import.
The Open dialog box is displayed, as shown in Figure 29.
FIGURE 29 OPEN
Performance
Management
Table of Contents
Customizing the Performance Data Collection Task .................31
Setting the Performance Threshold ......................................34
Querying Raw Performance Data .........................................37
Customizing the
Performance Data Collection
Task
Short Description You can set the NEs, time range, and performance objects for the
performance module to collect performance data.
Prerequisites The OMC client must be started and must have accessed the server.
Context The performance module collects NE data to measure, calculate,
evaluate, and report the NE running status. The performance data
collection task sets the NEs, time range, and data to be collected,
and informs the NE of the user settings.
Steps 1. Choose Views > Performance Management to display the
Performance Management window.
2. Click on the toolbar or choose Performance Management
> Task Management. Then, the Task Management window
is displayed in the right pane.
3. Click on the toolbar or choose Task > New. Then, the New
dialog box is displayed, as shown in Figure 30.
Note:
When modifying the task, you can modify only Task Informa-
tion.
END OF STEPS
7. Click the Effective Time tab to set the effective time thresh-
old, as shown in Figure 39.
Diagnosis Testing
Table of Contents
Testing a Board Manually ....................................................41
Customizing an Automatic Test Task.....................................42
Obtaining the Actual GPS Longitude and Latitude Informa-
tion .................................................................................45
Viewing the Board CPU Usage .............................................47
Testing the Link between External Network Port and AGW .........50
5. Click the board with the test result to display the test result,
showing the parameter indexes of the board.
Note:
You can use different colors to show different test state of the
board so as to distinguish fault levels. By default, green indi-
cates normal, yellow indicates abnormal, red indicates faulty,
and grey indicates unknown. You can customize the colors ac-
cording to your requirement.
6. Click Save. In the dialog box that appears, specify the file
name and click OK to save the test result.
END OF STEPS
Postrequisite According to the indexes of a board, you can learn the board run-
ning status and locate the board fault.
Customizing an Automatic
Test Task
Short Description On the site, when the maintenance personnel want to learn the
running status of multiple boards, they can customize a diagnosis
task for automatic test. In this way, they can obtain the onsite
information efficiently.
Prerequisites The OMC client must be started and must have accessed the server.
Context Create a task for testing certain boards automatically through the
Task Management function in Diagnosis Test. You can specify a
period for the system to automatically start the test.
Task management provides two functions:
� Automatic: The newly created task can be automatically exe-
cuted at the specified time.
� Batch: A task can contain multiple board test tasks at a time.
Steps 1. Choose Views > Fault Management > Diagnosis Manage-
ment to display the Diagnosis Management view.
2. Choose Management > Task Management to display the
Task Management window, as shown in Figure 46.
Note:
� If Idle is displayed in the Status column, it indicates that
the task is in the idle status, and no execution object is
specified.
� If Overtime is displayed in the Status column, it indicates
that the execution time of the task is earlier than the cur-
rent time.
In the Test Object List, select the test object record, right-
click, and then select Modify. Then you can view the selected
boards for the test. Right-click and choose Delete, and then
you can delete a board that is selected for the test.
8. Select a test task in the Task List, right-click and choose Run
to start the auto test.
9. After the board test is completed, select the required object
in the Test Object List, right-click, and then choose Query
Result to display the Period Board Test Result window.
Note:
If the link break happens to the system, the test result shows
timeout.
10. In the Board Test Result list, select the required board type.
Then, the detailed test information is displayed in the Element
Test Result list. The running states of the boards are marked
with different colors.
11. In the Board Test Time drop-down list, select different test
time segments. Then, you can view the corresponding test
results.
END OF STEPS
and then import the information through the longitude and latitude
synchronization menu in configuration management.
Steps 1. Choose Views > Fault Management > Diagnosis Manage-
ment to display the Diagnosis Management view.
2. Choose Operation > Statistic Test. Then, the Statistic Test
window is displayed, as shown in Figure 50.
Note:
The file name format is Statistics Test + Time.
END OF STEPS
Result If the link break happens to the system, the test result shows
timeout.
If the system prompts the test timeout message, check whether
the TFM board is virtually configured. Check whether there is an
alarm prompting that the TFM board is not detected. If there is
not such an alarm, check whether the TFM board is normal through
the board test function.
If the antenna feeder is not connected or the TFM board is in the
preheat phase, the result returned in the diagnosis result is the
default initial value, not the actual latitude and longitude value.
FIGURE 55 OPTION
� Only the history CPU usage data of the object that is being
observed can be queried.
� Only the first 1000 records that meet the conditions can be
queried.
� History data can be saved as a text file or an Excel file.
� If no result is available, the system displays a message
saying no data to save when you click Save.
END OF STEPS
Context Through the OMC, you can select any available link between the
MPXM and AGW under the required NE. Then, set the test param-
eters (including timeout time, number of tests, size of the test
packet), and then sends the test command to the MPXM board.
The MPXM board sends the eco request message to the AGW, and
returns the response to the OMC. The OMC parses the returned
response and displays the test result.
Figure 57 shows the flow for testing the connectivity of the link
between the external network port and AGW.
FIGURE 58 SETTINGS
Parame- Description
ter
Size Size of the test packet, in the unit of byte. The value
range is 32~1464 and the default value is 32.
7. To save the test result, choose Command > Save Result (or
click on the toolbar) to save the test result to a local path.
END OF STEPS
Result Figure 59 shows the result of the test of the link between the ex-
ternal network port and AGW.
Figure 59 shows the ping test from the source IP address to the
destination IP address. The 5 ping operations are all successful,
the ping packet size is 32 bytes, the maximum delay is 10 ms and
the minimum delay is 4 ms.
RF Analysis
Table of Contents
Adjusting the BTS Transmit Power........................................55
Collecting RF Parameter Statistics ........................................57
Spectrum Scanning............................................................59
Baseband Interference Analysis ...........................................61
Auto Calibration ................................................................63
ii. Select the required path option and click Start to send the
auto calibration message. After the operation is successful,
the corresponding information is displayed.
Note:
– Calibration can be started for single path or all paths.
If you select single path, then calibration is started only
for the specified path. If you select all path, then cali-
bration is started for all the active channels of the RRU.
– If the calibration is successful, the channel power after
calibration is displayed in the window.
– If the calibration fails, the failure message and the
cause are displayed in the window.
– If NE timeout is prompted, check the communication
link between OMC and NE.
END OF STEPS
Collecting RF Parameter
Statistics
Prerequisites The OMC client must be started and must have accessed the server.
Steps 1. Choose Views > System Tools > RF Analysis to display the
RF Analysis window.
2. Choose RF Analysis > Resource Statistics. Then, the Re-
source Statistics window is displayed, as shown in Figure 62.
FIGURE 63 SETTINGS
4. On the node tree, select the required WBTSB node and click
to add the WBTSB to the right pane.
5. Click OK to return to the Resource Statistics window, as
shown in Figure 64.
Spectrum Scanning
Abstract Purpose of spectrum scanning: In the case of no user access, on
the specified antenna of the specified segment (that is, the speci-
fied carrier) in the uplink direction, the subcarriers within the con-
figured channel bandwidth are scanned. The scan result is then
reported to the OMC. The OMC then displays the spectrum (power
of each subcarrier), channel bandwidth RSSI, and peak to average
power ratio of the entire configured channel bandwidth.
Prerequisites The OMC client must be started and must have accessed the server.
Context Spectrum scanning collects the power values of sub-channels
based on the report time and report type specified by the user
and reports the values to the OMC.
Steps 1. Choose Views > System Tools > RF Analysis to display the
RF Analysis window.
2. Choose RF Analysis > CompactBS Spectrum Scan (or click
on the toolbar). Then, the CompactBS Spectrum Scan
window is displayed, as shown in Figure 65.
4. In the dialog box, select the required antenna, set scan type
to Average scanning or Peak scanning, set task time (re-
port working duration and report period), and then click OK to
complete the settings.
5. Choose Operation > Start (or click on the toolbar) to start
spectrum scanning.
The spectrum scanning result is displayed on the Result tab.
You can click the Curve tab to view the spectrum scan curve.
6. Choose Operation > Stop (or click on the toolbar) to stop
spectrum scanning.
You can click the Log tab to view the operation result.
END OF STEPS
Baseband Interference
Analysis
Short Description For broadband interference, you can make a judgment by ob-
serving RSSI. Therefore, only narrowband interference is provided
for spectrum analysis. Baseband analyses the spectrum features
of each symbol to determine whether interference exists. If in-
terference exists, the average value (sub-carrier number) at the
peak value position (interference position), variance with the peak
value, and the percentage at which the threshold is exceeded are
reported to the OMC.
Prerequisites The OMC client must be started and must have accessed the server.
Context Spectrum analysis analyzes the spectrum features of each sym-
bol within the user-specified scan cycle. When the user-specified
threshold is exceeded, the result is reported to the OMC.
Steps 1. Choose Views > System Tools > RF Analysis to display the
RF Analysis window.
2. Choose RF Analysis > Spectrum Analysis (or click on the
toolbar). Then, the Spectrum Analysis window is displayed,
as shown in Figure 67.
FIGURE 68 SETTINGS
Parameter Description
Auto Calibration
Abstract During the automatic calibration process, the output power of the
RRU antenna port is automatically adjusted to the target power
specified by the user. When the RRU output power needs to be set
according to the network planning personnel in the case of new site
provisioning or when the user is unsatisfied with the RRU output
power, you can use the automatic calibration function to adjust the
output power.
Prerequisites � The OMC client must be started and must have accessed the
server.
� The following nodes are added to the tree of the Configuration
Management window: district, WBTSB, radio parameter, cell,
carrier, and segment.
Context In the case of automatic calibration, change the RRU target power
to the power required by the user in OMC configuration manage-
ment, and then perform synchronization between NE and OMC.
For new site provisioning, you can set the target power when you
set the system parameters. Then, after the system is powered on,
automatic calibration is performed.
Steps 1. Set the target power.
i. Choose Views > Configuration Management to display
the Configuration Management window.
ii. In the left pane of the Configuration Management win-
dow, select the RRU for which you want to set the target
power. Then, the RRU rack view is displayed.
iii. Right-click the WTRX board and choose Configure TRX
Parameters.
The Configure TRX Parameters dialog box is displayed,
as shown in Figure 69.
Note:
The calibration power takes Preamble power as its refer-
ence. Currently, the calibration accuracy must be within
-0.5 dB to +0.5 dB. Data power changes along with service
data, so it cannot act as the reference for calibration.
Note:
The target power of this calibration mode is the target
power specified in physical configuration. To change the
target power, change it in configuration management.
ii. If the retry fails, the cause of the calibration failure is dis-
played. In this case, consult the technical support person-
nel.
END OF STEPS
Alarm Management
Table of Contents
Using the Alarm Indicator ...................................................67
Querying Active Alarms Quickly ...........................................69
Customizing Alarm Query Conditions....................................73
Notifying the Maintenance Personnel of Alarm Information
Through Emails .................................................................76
Exporting Cleared Alarms ...................................................79
Performing an Active/Standby Switchover of Boards ...............82
Setting an Alarm Mask Rule ................................................82
Setting an Alarm Filter Condition .........................................84
Masking Board Alarms........................................................86
Resetting the System .........................................................87
Resetting a Subsystem .......................................................88
Resetting a Board ..............................................................88
Resetting BBU or RRU Subsystems in Batches .......................89
Viewing the Reset Operation Logs ........................................90
Collecting Alarm Statistics by Alarm Code .............................91
Collecting Alarm Statistics by NE .........................................93
Collecting Alarm Statistics by Time ......................................95
Customizing Alarm Statistics ...............................................98
Enabling/Disabling PA ...................................................... 101
Monitoring Dry Contact Alarms .......................................... 102
Synchronizing BTS Alarms to OMC Server and Client ............ 105
Steps 1. In the OMC window, choose Views > Fault Management >
Alarm Management to display the Alarm Management win-
dow.
2. Choose Operation > Customization. Then, the Customiza-
tion window is displayed, as shown in Figure 74.
END OF STEPS
3. Click the Location tab and set the target query parameters.
Table 8 shows the description of the parameters.
Parame- Description
ter
4. Click the Code tab, set the Alarm code and Reason code
conditions, as shown in Figure 80.
Note:
The alarm code and reason code options are determined by the
System type option that is set in step 3.
5. Click the Other Conditions tab and set the target query con-
ditions, as shown in Figure 81. Table 9 shows the description
of the parameters.
Param- Description
eter
END OF STEPS
Postrequisite
� Click on the toolbar to save the query result into a file.
� Click on the toolbar to print the query result.
� Click on the toolbar to set the query conditions again.
Param- Description
eter
FIGURE 85 SETTINGS
4. In the Modify Rule dialog box, click the Condition tab and
set the Email rule. For the method, refer to the procedure in
Customizing Alarm Query Conditions.
5. In the Modify Rule dialog box, click the Parameter tab, set
the Email parameters, as shown in Figure 89.
Parame- Description
ter
ii. In the Mail list pane, you can click Add, Modify or Delete
to add, modify or delete a mail record.
6. Select Activate and click OK.
END OF STEPS
Performing an
Active/Standby Switchover
of Boards
Prerequisites � The OMC client must be started, and the client must have ac-
cessed the server.
� The communication link between the OMC and NE is normal.
Steps 1. In the OMC window, choose Views > Fault Management >
Alarm Management to display the Alarm Management win-
dow.
2. In the left pane, expand the configuration tree and select the
required BBU rack node. In the rack view that is displayed
in the right pane, right-click the board for which the standby
board is available (currently only the TFM board and CSIM
board support standby boards) and choose Changeover
Board Normally.
After the active/standby switchover, the original active board
becomes the standby board while the original standby board
becomes the active board.
Note:
The active/standby switchover may cause link break for a short
while.
END OF STEPS
3. Click on the toolbar. Then, the Add Rule dialog box is dis-
played, as shown in Figure 94.
4. In the Add Rule dialog box, set Rule name and Condition.
For the method of setting Condition, refer to Customizing
Alarm Query Conditions.
5. Click OK to display the new rule, as shown in Figure 95.
4. In the Add Rule dialog box, set Rule name and Condition.
For the method of setting Condition, refer to Customizing
Alarm Query Conditions.
5. Click OK to display the new rule, as shown in Figure 97.
Note:
Click Reload to reload the information of all systems.
3. In the list of the WBTSB tab, select the required system, and
click on the toolbar. In the confirmation dialog box, click
OK. Then, the result is displayed in the Result column.
END OF STEPS
Resetting a Subsystem
Prerequisites � The OMC client must be started, and the client must have ac-
cessed the server.
� The communication link between the OMC and NE is normal.
Context The OMC sends the reset command to the NE. After the NE receives
the command, it performs the reset operation. The OMC keeps a
log of the reset operation.
Steps 1. In the OMC window, choose Views > Fault Management >
Alarm Management to display the Alarm Management win-
dow.
2. In the left pane, expand the configuration tree, select the node
of the BBU rack or RRU rack to be reset. Then, the rack view
is displayed in the right pane.
3. In the rack view, select the control board. (The control board
of the BBU is CSIM, and the control board of the RRU is WPTR.)
Right-click the board and choose Reset Subsystem.
4. In the Confirm dialog box, click OK to reset the subsystem.
END OF STEPS
Resetting a Board
Prerequisites � The OMC client must be started, and the client must have ac-
cessed the server.
� The communication link between the OMC and NE is normal.
Context The OMC sends the reset command to the NE. After the NE receives
the command, it performs the reset operation. The OMC keeps a
log of the reset operation.
Steps 1. In the OMC window, choose Views > Fault Management >
Alarm Management to display the Alarm Management win-
dow.
2. In the left pane, expand the configuration tree, select the node
of the BBU rack or RRU rack to be reset. Then, the rack view
is displayed in the right pane.
3. In the rack view, select a board. Right-click and board and
choose Reset Board Forcedly or Reset Board Normally.
4. In the Confirm dialog box, click Yes.
END OF STEPS
Caution:
When the services are busy, do not reset subsystems. The opera-
tion has great influences on the system.
Steps 1. In the OMC window, choose Views > Fault Management >
Alarm Management to display the Alarm Management win-
dow.
2. In the left pane, expand the topology tree and select the
WBTSB node.
3. Choose Operation > Control NE to display the Control NE
window, as shown in Figure 100.
Note:
You can input the system number or alias in the Enter filter
text text box and press Enter to display the required BBU or
RRU subsystems.
You can click Reload to reload the information of the subsys-
tems.
Note:
� To view the 50 most frequent alarm codes, choose Analy-
sis > Alarm Analysis > By Alarm Code > Top 50.
� To view the 100 most frequent alarm codes, choose Anal-
ysis > Alarm Analysis > By Alarm Code > Top 100.
FIGURE 104
END OF STEPS
Note:
� To view the top 50 NEs that generate alarms most fre-
quently, choose Analysis > Alarm Analysis > By NE >
Top 50.
� To view the top 100 NEs that generate alarms most fre-
quently, choose Analysis > Alarm Analysis > By NE >
Top 100.
END OF STEPS
Note:
� To view the dates when alarms are generated frequently
during the recent one month, choose Analysis > Alarm
Analysis > By Time > By Date.
� To view the weeks when alarms are generated frequently,
choose Analysis > Alarm Analysis > By Time > By
Week.
END OF STEPS
Note:
� Alarm measurement and analysis is conducted based on
the option specified in the Stat. indicator pane.
� Alarm measurement and analysis measures the index spec-
ified in Stat. Object pane, obtains the index values and
then sorts them.
5. Click the Stat. Range tab, and then set Stat. range and the
related parameters, as shown in Figure 113.
Note:
After an option is selected in the Stat. range pane, Available
Items and Selected Items become available. Then, you can
select the required items.
6. You can save the customized task in this way: Click Export as
Task. In the Export as Stat. Task dialog box, set the name
and click OK.
7. After setting the conditions for the customized measurement
and analysis task, click OK to display the measurement and
analysis result, as shown in Figure 114.
END OF STEPS
Enabling/Disabling PA
Prerequisites � The OMC client must be started, and the client must have ac-
cessed the server.
� The communication link between the OMC and NE is normal.
Context The OMC, through the man-machine command, sends the en-
able/disable command to PA to control the PA running.
Steps 1. In the OMC window, choose Views > Fault Management >
Alarm Management to display the Alarm Management win-
dow.
2. In the left pane, expand the topology tree and select the re-
quired RRU rack. Then, the RRU rack view is displayed in the
right pane.
3. In the rack view, right-click the WDPA board and choose En-
able or Disable. Then, the Enable or Disable dialog box is
displayed. Figure 115 shows the Enable dialog box.
iii. Select the required alarms and modify the alarm descrip-
tion in the Edit alarm description pane. Then, click OK
to save the modification result.
2. Specify the alarms reported on each dry contact.
i. Choose Views > Configuration Management to display
the Configuration Management view.
ii. In the left pane, expand the topology tree and select the
District node. In the System Configuration window that
is displayed in the right pane, click the NE Dry Contact
tab, as shown in Figure 117.
Version Management
Table of Contents
Version Download ............................................................ 107
Version Query ................................................................. 113
Upgrading a Version Using a Software Package .................... 118
Version Download
Version Download Flow
The flow for downloading the ZXMBW BSS version is as follows:
adding a version ® delivering the version ® activating the version
® bring the version into effect.
If a newer version is required, after ZXMBW BSS is powered on,
query the running version and compare it with the latest version.
If there are differences between the two versions, update the run-
ning version.
The order of ZXMBW BSS version transfer is follows: OMC server
® CSIM board ® target board.
CSIM √ √
MPIM √ √ √ √
WBPM √ √ √ √ √
TFM √ √ √ √ √
FEMM √ √
PM483 √ √
PMA √ √
WPTR √ √ √
TRW- √ √ √
A_A
WDP- √ √
A0
WDP- √
A0W
MPXM √ √ √ √
CSIM √ √√ √
MPIM √ √ √ √ √
WBP- √ √ √ √ √ √
M
TFM √ √ √ √ √ √
FEMM √ √ √
PM48 √ √ √
3
PMA √ √ √
WPTR √ √ √ √
TRW- √ √ √ √
A_A
WDP- √ √ √
A0
WDP- √ √ √
A0W
MPX- √ √ √ √ √
M
Adding a Version
Prerequisites � The OMC client must be started, and the client must have ac-
cessed the server.
� The communication link between the OMC and NE is normal.
Steps 1. In the OMC window, choose Views > System Tools > Ver-
sion Management. Then, the Version Management win-
dow is displayed, as shown in Figure 119.
3. Choose Add Version > Add Version File (or click on the
toolbar). Then, the Select Version File dialog box is dis-
played, as shown in Figure 121.
4. Select the required version file and click OK to add the version
file to the version database.
END OF STEPS
Delivering a Version
Prerequisites � The OMC client must be started, and the client must have ac-
cessed the server.
� The communication link between the OMC and NE is normal.
� The version must have been added successfully.
Steps 1. In the OMC window, choose Views > System Tools > Ver-
sion Management to display the Version Management win-
dow.
2. Choose Version Management > Deliver Version. Then, the
Deliver Version dialog box is displayed, as shown in Figure
122.
4. In the NE pane, select the required NE. In the File name pane,
select the required version file, and then click OK.
Note:
� In the NE pane, the filter function is provided so as to find
the required NEs quickly.
Set District, Group, System, and Fuzzy query, and then
click OK to display the required NEs.
In the Fuzzy query dialog box, you can input a value for
the fuzzy search based on district number, group number,
system number, NE type, and NE alias. The NEs that con-
tain the value of Fuzzy query are displayed.
� In the File name pane, if BOOT is selected, the BOOT
version is delivered.
Activating a Version
Prerequisites � The OMC client must be started, and the client must have ac-
cessed the server.
� The communication link between the OMC and NE is normal.
� The version must have been delivered successfully.
Steps 1. In the OMC window, choose Views > System Tools > Ver-
sion Management to display the Version Management win-
dow.
2. Choose Version Management > Query Version to display
the Query Version window.
3. Choose Query Version > Query Saved Version (or click
on the toolbar). Then, the Query Saved Version dialog box
is displayed, as shown in Figure 124.
Note:
In the NE pane, the filter function is provided so as to find the
required NEs quickly.
Set District, Group, System, and Fuzzy query, and then
click OK to display the required NEs.
In the Fuzzy query dialog box, you can input a value for the
fuzzy search based on district number, group number, system
number, NE type, and NE alias. The NEs that contain the value
of Fuzzy query are displayed.
Note:
For certain boards, to reset them normally, you need to select
the CPU or unit number at the system prompt.
3. In the Confirm dialog box, click Yes. After the reset is suc-
cessful, the version takes effect.
END OF STEPS
Version Query
Querying the Running Version
Prerequisites � The OMC client must be started, and the client must have ac-
cessed the server.
� The communication link between the OMC and NE is normal.
Steps 1. In the OMC window, choose Views > System Tools > Ver-
sion Management to display the Version Management win-
dow.
Note:
In the NE pane, the filter function is provided so as to find the
required NEs quickly.
Set District, Group, System, and Fuzzy query, and then
click OK to display the required NEs.
In the Fuzzy query dialog box, you can input a value for the
fuzzy search based on district number, group number, system
number, NE type, and NE alias. The NEs that contain the value
of Fuzzy query are displayed.
END OF STEPS
Steps 1. In the OMC window, choose Views > System Tools > Ver-
sion Management to display the Version Management win-
dow.
2. Choose Version Management > Query Version to display
the Query Version window.
3. Click or choose Query Version > Query Running Ver-
sion. Then, the Query Running Version dialog box is dis-
played, as shown in Figure 126.
Note:
In the NE pane, the filter function is provided so as to find the
required NEs quickly.
Set District, Group, System, and Fuzzy query, and then
click OK to display the required NEs.
In the Fuzzy query dialog box, you can input a value for the
fuzzy search based on district number, group number, system
number, NE type, and NE alias. The NEs that contain the value
of Fuzzy query are displayed.
END OF STEPS
Result The result for comparing the running versions and the versions in
the software package are displayed in the Target Version col-
umn. If the versions are the same, _ is displayed. If the versions
are different, the version in the software package is displayed.
Note:
In the NE pane, the filter function is provided so as to find the
required NEs quickly.
Set District, Group, System, and Fuzzy query, and then
click OK to display the required NEs.
In the Fuzzy query dialog box, you can input a value for the
fuzzy search based on district number, group number, system
number, NE type, and NE alias. The NEs that contain the value
of Fuzzy query are displayed.
END OF STEPS
Note:
In the NE pane, the filter function is provided so as to find the
required NEs quickly.
Set District, Group, System, and Fuzzy query, and then
click OK to display the required NEs.
In the Fuzzy query dialog box, you can input a value for the
fuzzy search based on district number, group number, system
number, NE type, and NE alias. The NEs that contain the value
of Fuzzy query are displayed.
END OF STEPS
Result The result for comparing the active versions and the versions in the
software package are displayed in the Target Version column.
If the versions are the same, _ is displayed. If the versions are
different, the version in the software package is displayed.
Note:
� In the NE pane, the filter function is provided so as to find
the required NEs quickly.
Set District, Group, System, and Fuzzy query, and then
click OK to display the required NEs.
In the Fuzzy query dialog box, you can input a value for
the fuzzy search based on district number, group number,
system number, NE type, and NE alias. The NEs that con-
tain the value of Fuzzy query are displayed.
� In the Package name pane, if BOOT is selected, the BOOT
version is delivered.
Note:
Assuming that the saved CPU version is a, and the running
version is b in the CSIM query result, the prompt message
displayed in the different cases are as follows:
� If the CPU version number of CSIM in the software package
for activation is a, perform the activation operation.
� If the CPU version number of CSIM in the software package
for activation is b, the system prompts that the version has
already been activated.
� If the CPU version number of CSIM in the software pack-
age for activation is c, the system prompts that the target
software does not exist in the flash.
� If the CPU number of CSIM does not exist in the software
package for activation, the system prompts that the soft-
ware does not exist in the package.
Service Analysis
Table of Contents
Collecting Service Data .................................................... 121
Saving Signaling Data and Global Data ............................... 126
Using Service Reader to View History Files .......................... 128
4. In the left pane, expand the topology tree to select the required
NE, and then click . Then, the selected NE is displayed in the
NE list in the right pane, as shown in Figure 133. Click OK to
finish the NE selection.
6. Click the Filter Parameter tab and set the filter criteria, as
shown in Figure 135.
7. Click the Common Setting tab, and set the maximum dura-
tion of the task time.
8. Choose Operation > Synchronize Task (or click on the
toolbar) to start synchronization of the selected NE.
On the NE Management tab that is in the lower right part of
the Service Data Collection window, the status of the task
of the current NE is displayed, as shown in Figure 136.
Steps 1. Choose Views > System Tools > Service Analysis to dis-
play the Service Analysis window.
2. Choose Service Analysis > Service Data Reader (or click
on the toolbar). Then, the Service Data Reader window is
displayed, as shown in Figure 139.
3. Choose File > Open (or click on the toolbar). In the Open
dialog box, select the history file to open, and then click Open
to view the history file.
END OF STEPS
System Information
Table of Contents
Observing Software Systems Running in Real time ............... 131
Querying and Locating Fault with Abnormal Probe ................ 133
Filtering Unnecessary Boards with the Shielding/Unshielding
Function of the Abnormal Probe......................................... 134
Querying Route Information between OMC and NE and the
Message Queue Information.............................................. 135
Synchronizing the OMC Clock ............................................ 136
Observing Software
Systems Running in Real
time
Prerequisites � The OMC client must be started, and the client must have ac-
cessed the server.
� The communication link between the OMC and NE is normal.
Steps 1. In the OMC window, choose Views > System Tools > Sys-
tem Info to display the System Info window.
2. Choose System Info > Running Information to display the
Running Information window.
3. In the left pane, expand the topology tree and select the pro-
cesses under the required board, as shown in Figure 140.
Note:
� When there are responses from the NE, the nodes turn
blue.
� If there is no response from the NE due to such cause as
link broken, the nodes turn red.
5. You can click on the toolbar (or choose Flow Control >
Enable) to enable flow control. You can click on the toolbar
(or choose Flow Control > Disable) to disable flow control.
6. In the Running Information window, choose Operation >
Set Path. Then, in the Set Path dialog box as shown in Figure
142, modify or view the path of the automatically saved file.
END OF STEPS
3. Query data. Select the query object the time, and then choose
Operation > Query or click on the toolbar.
4. Save data. Choose Operation > Export or click on the
toolbar, and then save data.
END OF STEPS
Filtering Unnecessary
Boards with the
Shielding/Unshielding
Function of the Abnormal
Probe
Prerequisites � The OMC client must be started, and the client must have ac-
cessed the server.
� The communication link between the OMC and NE is normal.
Context The shielding function of the abnormal probe shields a board or all
the board of a subsystem, preventing the boards from reporting
abnormal probe information to the OMC. This reduces the amount
of unrelated information, facilitating fault location.
Steps 1. In the OMC window, choose Views > System Tools > Sys-
tem Info to display the System Info window.
2. Choose System Info > Shield Exception or click on the
toolbar. Then, the Shield Exception window is displayed, as
shown in Figure 144.
AGW
- ASN Gateway
BBUB
- BaseBand Unit type B
BTS
- Base Transceiver Station
CORBA
- Common Object Request Broker Architecture
CPU
- Central Processing Unit
FTP
- File Transfer Protocol
GPS
- Global Positioning System
MPXM
- Main Processor for WiMAX - type 1
OMC
- Operation & Maintenance Center
OMM
- Operation Maintenance Module
OS
- Operating System
PA
- Power Amplifier
PMA
- Physical Medium Attachment
SNMP
- Simple Network Management Protocol
TFM
- Timing Frequency Module
UMS
- Unified Messaging Service
WDPA
- WiMAX Digital Power Amplifier