WCDMA RAN12.0 RNC Serviceability Feature-20100130-B-1.0

Internal
RAN12.0 RNC
Serviceability Feature
www.huawei.com
ISSUE 1.0
WRAN Training Team
HUAWEI TECHNOLOGIES CO., LTD.
Huawei Confidential
This course describes the replacement of the

DPU, new features of the OMU, upgrade
optimization of the RNC, and the procedure for
remotely applying patches for the operating
system.
Huawei Confidential
Page 2
In this training course, you can learn:

The replacement of the DPU
The new features of the OMU in RAN12.0
The upgrade optimization of the RNC
The procedure for remotely applying patches for the
operating system
Huawei Confidential
Page 3
BSC6900 V900R012C00 Release Notes;

BSC6900 UMTS OMU Administration Guide
(V900R012C00);
Huawei Confidential
Page 4
Chapter 1 Replacing the DPU

Chapter 2 New Features of the OMU
Chapter 3 Upgrade Optimization
Chapter 4 Remotely Applying Patches for
Operating system
Huawei Confidential
Page 5
Background Information
Background and benefit

The IPC link is not broken after the INH DPU/DSP command is executed, and the MSs
occupying DCHs are not affected.
After this command is executed, the access of new MSs is denied and common channel
resources in a cell are re-created to reduce the impact of board replacement on services.
You can run the DSP UDSPRESOURCE command to query the remaining MSs on the board.
Do not replace the board until the number of MSs is decreased to an acceptable value.
INH DSP/INH BRD
Version
MBSC
V912
Whether the IPC link is broken Yes

Whether the original services
are released abnormally
Whether new services can be
accessed
No
Yes
No
No
Yes
Cell resource processing
Cell resources are re-created

immediately. The cell will be
unavailable if NE swap is impossible.
New MSs cannot access the network
from the DSP cell.
Cell resources are re-created

immediately. If NE swap is
impossible, do not swap the NE,
and new MSs can still access
the network from the DSP cell.
Command processing mode
Stiff
Placid
Huawei Confidential
Page 6
Function Description
Function description
The MML command INH DSP/INH BRD can be used to forbid allocating new
MS resources to the DPU or DSP of the specified subrack, slot, and
subsystem.
If the DSP has cell resources, the resources corresponding to the common
channel are deleted and the resources are re-created on another DSP. During
the re-creation process, the calls of MSs occupying FSCHs may be dropped. If
the cell is bound to the DSP, the binding relation needs to be released after the
DSP is inhibited.
MSs on the inhibited DPU/DSP are released naturally. You can run the DSP
UDSPRESOURCE command to query the remaining MSs on the inhibited
DPU/DSP. Do not replace the board until the number of MSs is decreased to
an acceptable value.
Huawei Confidential
Page 7
MML Command
MML command
Set INHT to LOGIC when running the INH BRD command for the
DPU.
INH BRD: INHT=LOGIC, SRN=1, SN=8;
Huawei Confidential
Page 8
MML Command
MML command
Before replacing the DPU, run the DSP UDSPRESOURCE

command to query the remaining MSs.
DSP UDSPRESOURCE: SRN=1, SN=8;
Huawei Confidential
Page 9

Operating system
Huawei Confidential
Page 10
Last Words About BAM
Function description
When a module is reset abnormally, a core file is saved to

\mbsc\bam\version_X\ftp\crashfile, and a logfile in
\mbsc\bam\version_X\ftp\crashfile\log\ records relevant information.
Cases that cause abnormal reset:

Access violation (ACCESS_VIOLATION)
Exception of dividing by zero (DIVIDE_BY_ZERO)
Stack overflow (STACK_OVERFLOW)
Notes:
1. Access violation occurs most frequently. At present, this is the cause
of over 90% of abnormal reset events.
2. This feature does not record the process reset logs of all cases. For
example, manual reset logs and module seal-healing logs are not
recorded.
Huawei Confidential
Page 11
File generation
Core file
Name format:
The core file is named in the following format: module name + time information + .dmp.
Timed compression:
The core file is compressed at scheduled time. The compressed file is named in the following format:
module name + time information +.zip.
The time information is the number of seconds counting from January 1, 1970.
Deletion processing:
Up to two dump files generated by each module can be saved. If the module is not reset after an
exception occurs, up to three files can be saved.
The total size of all the core files is also restricted. When the total size exceeds 1 GB, the old core
files are deleted (if a module has only one dump file, this file is not deleted).
When a core file is stored for more than one month, it is regarded as an outdated file and then
deleted.
The core files are deleted at the startup of modules and each module deletes only its own core files.
Others:
In the Windows operating system, when an exception occurs frequently in a module (less than 10
minutes from the last time when a core file is generated), core files will not be generated
continuously. Nevertheless, a logfile will record the exception information. In the Linux operating
system, frequent exceptions are not restricted.
Huawei Confidential
Page 12
Logfile
Name format:
The logfile is named in the following format: module name + _crash.log.
Size restriction:
When the size of a file exceeds 2 MB, the file is automatically backed up. The
backup file is named in the following format: module name + _crash.bak. Each
module has up to one logfile and one backup file.
Content:
The logfile records two types of information: feature running information and
exception information. The feature running information begins with --- for
differentiation.
Huawei Confidential
Page 13

Contents of the logfile
Windows:
Name and version of the operating system
Module startup description
Name of the existing core file
Type and number of CPUs
Stack call information in an exception
Register content in an exception
Type, time, address, and cause of an exception
When a core file is generated, the logfile records information about loaded
modules in the case of a process exception.
Linux:
Name and version of the operating system
Module startup description
Name of the existing core file
win_log.txt
Huawei Confidential
Page 14
Usage description
Check
whether abnormal restart has occurred .
Method 1:
Check whether a core file or a compressed .zip file exists in
\mbsc\bam\version_X\ftp\crashfile\. If so, a module has restarted
abnormally.
Method 2:
When analyzing the COL log returned by an operator, you can determine
the size and content of each module. If dump file XXXX exists is
contained in the log, you must ask the field engineer to provide the core
file in \mbsc\bam\version_X\ftp\crashfile\ as soon as possible.
In the Windows operating system, you can view the exception
information in the log and directly use the information for troubleshooting.
Huawei Confidential
Page 15

Windows:
Files:
core file, module file, map file, and source code

Tools: GDB and Windbg
Steps:
1. Use the Windbg tool to open the dump file, and run the !analyze -v
command to obtain the information about the exception type, stack, and
address of the input parameter.
2. Run the following command to open the module and the
corresponding map file:
gdb --exec=./module name --symbols=./map file name
3. Use the x address to analyze the address and obtain the exception
location and stack.
4. Use the dc address to analyze and obtain the value of the input
parameter.
analyze-v.txt
Huawei Confidential
Page 16

Linux:
Files: core file, module file, map file, and source code
Tool: GDB
Steps:
1. Run the following command to load the core file, module file, and
map file:
gdb --exec=./module name --symbols=./map file name --core=./dump file

name
2. Perform debugging to view the exception location, called stack, and
parameter value.
where is used to locate the exception, bt is used to view the called stack,
and p is used to view a parameter.
gdbdebug.txt
gdbLoad.txt
Huawei Confidential
Page 17
Setting an Office Name
Introduction
Command definition:
MML command: SET OFFICENAME
Parameter: SID
SID restriction:
The SID restriction is consistent with the restriction of the office name during
the installation.
V1: It is a string of 6-32 characters, consisting of only numerals, letters,
hyphens (-), and underscores (_). It must begin with a letter.
V9: It is a string of 5-32 characters, consisting of only numerals, letters,
hyphens (-), and underscores (_). It must begin with a letter.
Huawei Confidential
Page 18
Setting an Office Name
Precautions
V1:
After a valid office name is set successfully, the name takes effect
immediately and is displayed in the execution report of the MML command.
V2:
After a valid office name is set successfully, the name takes effect only after
manual soft reset of the active and standby OMUs. Otherwise, the following
case may occur: The command messages of some modules use the old office
name, and those of other modules use the new office name.
Huawei Confidential
Page 19
Filtering Alarms by Clearance

Time
C
Introduction
Feature description:
The following four parameters are added to LST ALMLOG and EXP ALMLOG
in V9 for querying alarms by clearance time: CLRSD, CLRED, CLRST, and
CLRET. The four parameter are respectively used to set the start clearance
date, end clearance date, start clearance time, and end clearance time.
The definition and usage of the parameters are similar to those of SD, ED, ST,
and ET.
V1 does not have this feature.
Precautions:
The four parameters can be used only in the case of querying/exporting fault
alarms, and cannot be used in the case of querying/exporting event alarms.
On the alarm query page of the WEBLMT, this function is provided by an MML
command.
Huawei Confidential
Page 20
Filtering Alarms by NodeB
Introduction:
Feature description:
A general mechanism is provided, so that alarms can be filtered according to

alarm location information (not only NodeBID) during the query/export/statistics
of alarms.
Related commands:
LST ALMLOG, LST ALMAF, EXP ALMLOG, and STA ALMLOG

Parameter: LOCINFOKEY (of the string type, including 1-200 characters)
Huawei Confidential
Page 21
Filtering Alarms by NodeB
Usage description
The LOCINFOKEY parameter must be entered in a certain format.

The value of this parameter consists of sub-items. The format of each sub-item is: name of
the sub-item + separator + value of the sub-item.
Name of the sub-item: description about the alarm location parameter
Separator: colon
Value of the sub-item: value of the alarm location parameter
At present, up to two sub-items are supported, and the two items are connected by the symbol &, which
indicates the AND relation.
Notes:
The name and value of the sub-item are case-sensitive.

On the alarm query page of the WEBLMT, this function is provided by an MML command.
The feature is implemented only in V9.
Example:
Run the following command to query the alarm log where computer name is huawei-d5db447b and
service name is RemoteAccess in the alarm location information:
LST ALMLOG: ALMTP=all, LOCINFOKEY=compute name:huawei-d5db447b&service
name:RemoteAccess";
Result::
Huawei Confidential
Page 22
Optimization of Run Logs
Background
Some modules have a lot of logs; however, the logfile size of each module is restricted in the
same way. Therefore, during log collection, logs that contain error information are overwritten.
Some modules such as the FTP server need to record the process log of each request.
Therefore, many logs exist. Because error logs are hidden in normal logs, it is difficult to find
the error logs for troubleshooting.
Each thread writes logs in files separately. When many logs exist, the thread may be blocked.
Benefit from the feature
The amount of log information recorded by the BAM is increased and thus more effective
information is provided for troubleshooting.
The impact of log recording on the system performance is reduced.
Huawei Confidential
Page 23
Implementation of basic functions
Different mechanisms are used to record common logs and debug logs.
UDP is used to start a separate process to record debug logs.
A thread is created in this module to record all common logs of this module.
An interface is added to record flow logs. With regard to a complete

transaction flow, a cache mechanism is used to record all logs of the
transaction into a flow logfile at the end of the transaction according to the
number sequence.
MML commands are added to set and query various flags of the log functions.
Huawei Confidential
Page 24
Introduction to logfiles
All BAM logs are stored in the following directory: mbsc/bam/[workspace]/log
There are four types of logfiles: module name.log, module name.out, module
name.flow, and module name_bin.out
Logfiles include a series of log backup files: module name + time.log, module
name + time.bak, module name_bin.bak, and module name_flow.bak
.log files mainly record major/minor/message logs. Such logs include the key
information for troubleshooting.
.out files mainly record debug logs and message frames in the inter-process
communication. Such logs are helpful during troubleshooting.
.flow files record transaction flow logs. If an exception occurs in a flow, the
problem can be quickly located according to such logs.
_bin.out files are the personalized logs of a few modules. At present, only the
alarm module and maintenance module have such logfiles.
Huawei Confidential
Page 25
set logcfg
module name: It is used to select a module.

Flow log flag: It indicates whether to record flow
logs. If the flag is set to enable, all flow logs
are recorded. If the flag is set to disable, only
the flow logs in the case of an exception are
recorded. The default value is disable.
Log level: It is a parameter for filtering logs.
After a log level is selected, only the logs at this
level or higher levels are recorded. The default
value is debug.
Logfile size: It is used to set the maximum size
of a logfile. The default value is 2 MB.
The upper Limit Of Process Log Can Start: It is
used to set the maximum number of flow logs
that can be started by this module. The default
value is 100.
Frame log flag: It indicates whether to record
the message frames in the inter-process
communication. The default value is disable.
lst logcfg
module name: It is used to select a module.
Huawei Confidential
Page 26
Monitoring of Network Adapter Status
Background
Problems such as link break and FTP exception due to the inconsistent
setting of working modes of the external network adapter on the OMU
and those on other network devices occur in many offices.
Benefit from this feature
When the actual duplex mode of the external network adapter is

inconsistent with the expected duplex mode, a fault alarm is generated to
timely notify the field engineer of handling. In this way, the OMU and the
connected network device can work more stably and serious problems
such as link break can be reduced. Besides, problems can be discovered
in time and problem escalation can be avoided.
Huawei Confidential
Page 27
The duplex mode of the external network adapter is checked regularly. When the
actual duplex mode of the network adapter is inconsistent with the expected
duplex mode, a fault alarm is generated.
An MML command is added to query the status of the network adapter.
An MML command is added to set the expected duplex mode of the network
adapter.
The alarm function is added. When the actual duplex mode of the network adapter
is inconsistent with the expected duplex mode, a fault alarm is generated.
Huawei Confidential
Page 28
SET EXPDPLXMODE
Expect duplex mode:
Including the half duplex mode, full
duplex mode, and auto negotiation
mode
LST DUPLEX
No input parameter is required.
The output result includes the
subrack ID and slot ID of the OMU,
expected duplex mode of the
network adapter, and actual duplex
mode of the network adapter.
Huawei Confidential
Page 29
Method for analyzing alarms
Run LST DUPLEX to view the current duplex mode of the network adapter.
View the duplex mode of the network adapter on the upper-layer router.
If the duplex mode of the network adapter on the upper-layer router is
inconsistent with the actual duplex mode of the network adapter on the OMU,
change the actual duplex mode of the network adapter on the OMU to make it
consistent with that on the upper-layer router, and then wait for alarm clearance.
If the duplex mode of the network adapter on the upper-layer router is consistent
with the actual duplex mode of the network adapter on the OMU, the expected
duplex mode of the network adapter is set improperly. In this case, run SET
EXPDPLXMODE to reset the expected duplex mode of the network adapter to
make it consistent with the actual duplex mode of the network adapter on the
OMU, and wait for alarm clearance.
After the alarm is cleared, run LST DUPLEX again. Now, the actual duplex mode
of the network adapter on the OMU is consistent with the expected duplex mode
of the network adapter.
Huawei Confidential
Page 30
Monitoring of the FTP Server
Background
When the RNC is an FTP server, if transit files are not deleted by a third
party in time, the transit folder becomes larger and larger, and eventually,
incidents occur.
Benefit from this feature
The folders on the FTP server are monitored. The oversize of files on the
server is avoided.
A unified mechanism for monitoring files is provided. New functions can

be added easily to monitor other files.
Huawei Confidential
Page 31
Monitoring of the FTP Server
The folder space on the FTP server is monitored. When the space reaches a set
space threshold, a log is recorded and the files on the server are deleted. The
rule for deletion is as follows: The oldest files are deleted according to the file
modification time, and the files in the transit folder are also processed.
time threshold, a log is recorded and the files on the server are deleted. The rule
for deletion is as follows: The files dated before the set time are deleted
according to the file modification time, and the files in the transit folder are also
processed.
file quantity limit, a log is recorded and the files on the server are deleted. The
rule for deletion is as follows: The oldest files are deleted according to the file
modification time, until the number of files is less than 80% of the limit.
The monitoring of customized folders is supported. Monitoring rules can be
customized. The supported monitoring modes include time monitoring, space
monitoring, file quantity monitoring, and hybrid monitoring.
The files on the server are stored in the following path: \mbsc\bam\common\ems
Huawei Confidential
Page 32

Operating system
Huawei Confidential
Page 33
Optimization list
1. Differentiated Loading
2. Low-Loss Host Reset After Cold Patching
3. Decoupling of MML Commands
4. Auto Unlocking of Scheduled Tasks
5. Upgrade Procedure Optimization
6. Upgrade Automation
Huawei Confidential
Page 34
Differentiated Loading
To better satisfy the requirement for cold patching the host, differentiated
loading is implemented. That is, when the BAM maintenance module
processes the load command, the module first checks whether the version in
the Flash of the current board is consistent with that in the BIN file on the
BAM. If they are inconsistent, the module performs loading; otherwise, the
module does not perform loading.
The version description of the BIN file on the BAM is provided in the
verdes.xml file.
Huawei Confidential
Page 35
Differentiated Loading
Implementation of the upgrade tool:
Replace the BIN and verdes.xml files on the active OMU (maybe on
some boards). The verdes.xml file has the version number of each
BIN file.
Some commands for synchronization between the primary storage area and
the secondary storage area are progress messages, and at last an overall
load report is returned. If the return code of the MML command is 0, it
indicates success; otherwise, it indicates failure. Note that for a board not in
position, a non-zero value also indicates success.
Huawei Confidential
Page 36
Low-Loss Host Reset After Cold Patching
Low-loss reset occurs in the following four scenarios:

Some boards are cold patched but some are not cold patched. The low-loss reset of the whole system is
initiated to validate the cold patch.
All boards are cold patched. The low-loss reset of the whole system is initiated to validate the cold patch.
The versions of BIN files on some boards are upgraded; some boards are cold patched after the versions of
their BIN files are upgraded. The low-loss reset of the whole system is initiated to validate the new version
and cold patch.
The board is cold patched and the DB is changed. The whole system must be reset.
Implementation of the upgrade tool:
In scenarios 1, 2, and 4, the differentiated load command is used to load the BIN files of the boards that are
cold patched to the Flash in the primary storage areas of the boards. In scenario 3, the workspace
synchronization command is used to load the BIN files of all boards to the Flash in the primary storage areas
of the boards.
The low-loss reset command RST UGPLANE:UPLN=STANDBY,UMD=UPGRADE; is delivered to reset the
standby plane. (In scenarios 1, 2, and 4, other commands rather than the reset command in the upgrade of
version B can be used to implement the function.)
The implementation of other functions is the same as the implementation of low-loss upgrade. That is, before
low-loss upgrade, the upgrade tool checks whether the maintenance path is normal through CHK MNTPATH;
after confirming that the maintenance path is normal, it performs low-loss reset. In addition, if the low-loss
reset command fails, or if the low-loss reset command is executed successfully but the execution result of
DSP UGRESULT:UPLN=STANDBY shows that the Result field value is not Standby Plane Upgrade
Incomplete or Upgrade Complete, the whole system is immediately reset. After the Result fields of all
subracks show Upgrade Complete, the upgrade tool starts to deliver the primary plane reset command RST
UGPLANE:UPLN=PRIMARY,UMD=UPGRADE;.
The final effect is that after reset, all boards run by loading BIN files from the Flash in the primary storage areas.
That is, the patch version runs on the cold patched boards.
Huawei Confidential
Page 37
Decoupling of MML Commands

The maintenance module is required to implement an export command, which
exports the following status information: BRD, BRDVER, and DSP.
Scenarios where the upgrade tool uses the command:
Query whether a board is normal.
Query the value of the CPU in the BRD. When the value of the CPU in all BRDs is
normal, all boards are regarded as normal; otherwise, all boards are regarded as
abnormal. The upgrade tool can display the abnormal board to users simply through
the node information such as the subrack, slot, subsystem, and board type.
Compare the version information on the BAM and the FAM.
Query the value of the ISEQUAL in the BRDVER. When the value of the ISEQUAL
in all BRDVERs is 0, it indicates that the version information of all boards is
consistent on the BAM and the FAM; otherwise, the version information is
inconsistent. Likewise, the upgrade tool can display the inconsistent version to
users simply through the node information such as the subrack, slot, subsystem,
and board type in the BRDVER.
Health check
This item is deleted at present.
Huawei Confidential
Page 38
Auto Unlocking of Scheduled Tasks

An optional parameter is added to the MML command LCK SCHTSK, which indicates whether to automatically
unlock a scheduled task next day.
Function of this parameter:
This optional parameter has two enumerated values: auto unlock and non-auto unlock.
If this parameter is not set by default, it indicates auto unlock.
If the value is auto unlock, on the next day after the scheduled task is locked, the auto task manager
automatically unlocks the scheduled task.
If the value is non-auto unlock, after the scheduled task is locked, auto unlocking is performed only after an
unlock command is delivered.
Processing of the BAM:
If auto unlocking is required in LCK SCHTSK, the BAM generates an unlocking time by adding a day to the
current time and stores the unlocking time to the database. The time field needs to be upgraded. If the BAM
finds that the current time is later than the unlocking time, the BAM immediately performs unlocking and
clears the time. The preceding operations need to be performed in V1/V2 respectively.
Processing of the upgrade tool:
In the pre-upgrade phase, the upgrade tool runs LCK SCHTSK to lock the scheduled task in the preparation
phase (to lock the scheduled task of the old version).
In the upgrade phase, when the BAM switches to the new version, the upgrade tool runs LCK SCHTSK on
the new version to lock the scheduled task again (to lock the scheduled task of the new version).
In the rollback phase, when the BAM switches to the old version, the upgrade tool runs LCK SCHTSK on
the old version (to lock the scheduled task of the old version).
Modification of the upgrade guide:
The description about manual unlocking is previously added to post-upgrade processing. Now the
description must be moved to post-rollback processing. This is because the old version before RAN12 does
not support auto unlocking.
Huawei Confidential
Page 39
Upgrade Procedure Optimization

Active OMU
Standby OMU
Check
Check before upgrade
Check before upgrade
Install BAM
standby area
Install BAM
standby area
Data check
Pre-upgrade
Data backup
Data upgrade
Data upgrade check
FMT DATA
Load FAM
standby area
Upgrade
Swap BAM active

and standby area
Reset FAM
Services verification
Swap BAM active

and standby area
Huawei Confidential
Page 40
Upgrade Automation
The input information of the client is stored to a configuration file. After the client of the
upgrade tool is started, the client obtains the current upgrade information from the
specified configuration file to automatically complete upgrade. If an error occurs, the
upgrade tool records the error information in a log for troubleshooting.
Different configuration files are provided to meet the requirements in various upgrade
scenarios.
Huawei Confidential
Page 41

Operating system
Huawei Confidential
Page 42
Background
Operating system patch upgrade is a top problem

concerning customer satisfaction. To enhance the
customer satisfaction, scheduled upgraded needs to be
performed for the operating system patches in the
existing network.
Because the cost for near-end operating system
patching is too high for the GTS, this function is to
lower the implementation cost and difficulty of the
GTS.
The reliability and operability of operating system
patch upgrade are increased.
The remote and centralized management of
operating system patches is improved.
Huawei Confidential
Page 43
Function Implementation Plan
Procedure for releasing a patch package

Procedure for releasing a patch package
Company
security
organization
Wireless
products
Support
website
patch
packages
Publish
after tests
Release notes
Install
patch
packages
configure file
Front
engineers
patches
installation
Huawei Confidential
Page 44
Overall architecture
1.
The NMS implements flow control through the

MML interfaces, mainly including: file
download, progress reporting, patch upgrade,
OSS
and patch rollback interfaces.

2.
MML/FTP
transmit patch files and reports through the
NE
NE upgrade module
The NMS and the upgraded NE modules
SHELL
Interface
FTP interfaces.
SW patch
3.
The interface between the upgraded NE

modules and the outsourced software patch
installation package is a shell interface, which
is used for upgrading/rolling back the patch
package, reading the progress information,
and obtaining reports.
Huawei Confidential
Page 45
Procedure for
OSS
applying patches
NE
patches
Check the patch version installed

Check the patch version installed
Check the patch package stored
manual
Check the patch package stored

Upload files to OSS server
Start upgrade server (optional)
Download upgrade files to NE
Files download feed back

Upgrade execution
automatic
Upgrade execution
Upgrade execution feed back
Upgrade execution feed back

Patch upgrade feed back
NE upgrade report
Upgrade submit
Stop upgrade server (optional)
Check after upgrade
Huawei Confidential
Page 46
Methods for processing upgrade/rollback reports

The OS patch installation package generates upgrade/rollback reports at the board level. The contents of the
reports involve only the OS and do not involve NE information.
The NE collects the reports of the active/standby OMUs and submits the collected reports to the M2000.
Exception handling in the upgrade/rollback process

For the recovery flow after the M2000 is disconnected from the NE during upgrade, see section 3.3.2 in the
Interface Design Baseline for Wireless Software Upgrade.
Failure may occur when a user performs upgrade and rollback. In this case, the system should prompt the user to
retry, cancel, or skip the process. For the confirmed flow, see section 3.3.3 in the Interface Design Baseline for
Wireless Software Upgrade.
Flow customization file

As an NMS, the M2000 needs to provide the flow customization file upgradecfg.xml when upgrading the
outsourced software patches. The flow file is released with the OS patch package.
The flow customization file based on the plan is as follows:
For related node definitions, see the Interface Design Baseline for Wireless Software Upgrade.
Port number of the upgrade server

When the M2000 is used for upgrade, the NE needs to release the port number of the upgrade server of the
outsourced software patches at the adaptation layer. The M2000 sends an MML package to the upgrade server
according to the port number released by the NE.
Method for implementing check after upgrade/rollback

At present, the check after upgrade/rollback is implemented by the STP UPSRV command. After the M2000
delivers STP UPSRV, if the NE responds to the command, it indicates that the NE and the M2000 are connected
normally.
Huawei Confidential
Page 47
Operation Introduction
Step 1: On the
M2000
operation page,
choose
Software > NE
Upgrade Task
Management >
NE Upgrade
Task. A dialog
box is
displayed.
Huawei Confidential
Page 48
Step 2: On the
previous tab
page, click
Create. A dialog
box is displayed.
Huawei Confidential
Page 49
Step 3: In the displayed dialog box, enter a task name, select an upgrade
type, a target version, and an NE, add the selected NE to the right box, and
then click Next. A dialog box is displayed.
Step 4: Complete the task configuration according to the prompt, and then
click Finish.
Step 5: After the task is created, the NE Upgrade Task Management tab
page is displayed automatically. The task is executed automatically according
to the task configuration.
Huawei Confidential
Page 50
Step 6: After the task is executed, the patch implementation report similar to the
preceding report is automatically generated.
Package-upgrade-report_modified.HTML
Huawei Confidential
Page 51
Thank you
www.huawei.com

WCDMA RAN12.0 RNC Serviceability Feature-20100130-B-1.0

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

WCDMA RAN12.0 RNC Serviceability Feature-20100130-B-1.0

Uploaded by

Copyright:

Available Formats

Internal

HUAWEI TECHNOLOGIES CO., LTD.

This course describes the replacement of the

HUAWEI TECHNOLOGIES CO., LTD.

In this training course, you can learn:

HUAWEI TECHNOLOGIES CO., LTD.

BSC6900 V900R012C00 Release Notes;

HUAWEI TECHNOLOGIES CO., LTD.

Chapter 1 Replacing the DPU

HUAWEI TECHNOLOGIES CO., LTD.

Background and benefit

Whether the IPC link is broken Yes

Cell resource processing

Cell resources are re-created

Cell resources are re-created

Command processing mode

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.

Before replacing the DPU, run the DSP UDSPRESOURCE

HUAWEI TECHNOLOGIES CO., LTD.

Chapter 1 Replacing the DPU

HUAWEI TECHNOLOGIES CO., LTD.

Last Words About BAM

When a module is reset abnormally, a core file is saved to

Cases that cause abnormal reset:

HUAWEI TECHNOLOGIES CO., LTD.

Last Words About BAM

HUAWEI TECHNOLOGIES CO., LTD.

Last Words About BAM

HUAWEI TECHNOLOGIES CO., LTD.

Last Words About BAM

HUAWEI TECHNOLOGIES CO., LTD.

Last Words About BAM

whether abnormal restart has occurred .

HUAWEI TECHNOLOGIES CO., LTD.

Last Words About BAM

core file, module file, map file, and source code

HUAWEI TECHNOLOGIES CO., LTD.

Last Words About BAM

gdb --exec=./module name --symbols=./map file name --core=./dump file

HUAWEI TECHNOLOGIES CO., LTD.

Setting an Office Name

HUAWEI TECHNOLOGIES CO., LTD.

Setting an Office Name

HUAWEI TECHNOLOGIES CO., LTD.

Filtering Alarms by Clearance

V1 does not have this feature.

HUAWEI TECHNOLOGIES CO., LTD.

Filtering Alarms by NodeB

A general mechanism is provided, so that alarms can be filtered according to

LST ALMLOG, LST ALMAF, EXP ALMLOG, and STA ALMLOG

HUAWEI TECHNOLOGIES CO., LTD.

Filtering Alarms by NodeB

The LOCINFOKEY parameter must be entered in a certain format.

The name and value of the sub-item are case-sensitive.

HUAWEI TECHNOLOGIES CO., LTD.

Optimization of Run Logs

Benefit from the feature

The impact of log recording on the system performance is reduced.

HUAWEI TECHNOLOGIES CO., LTD.

Optimization of Run Logs

Implementation of basic functions

UDP is used to start a separate process to record debug logs.