Beruflich Dokumente
Kultur Dokumente
V100R001C00
User Guide
Issue 04
Date 2014-09-30
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
Overview
This document describes how to use the SAU on a GSM or UMTS network. It covers
hardware installation, software installation (including the EBC and EMS service
components), IP address configuration, operation and maintenance (OM), common
operations, and troubleshooting methods of common faults. After all service components are
installed on each SAU board, you can deliver counters for each theme to the SAU through
upper-layer analysis systems, requesting the SAU to collect and preprocess data.
Intended Audience
This document is intended for:
Field engineers
Network optimization engineers
Change History
Issue 04 (2014-09-30)
This is the fourth commercial release.
Compared with Issue 03 (2014-07-30), Issue 04 (2014-09-30) includes the following changes:
Issue 03 (2014-07-30)
This is the third commercial release.
Compared with Issue 02 (2014-07-15), Issue 03 (2014-07-30) includes the following changes:
Issue 02 (2014-07-15)
This is the second commercial release.
Compared with Issue 01 (2014-05-20), Issue 02 (2014-07-15) includes the following changes:
Issue 01 (2014-05-20)
The guide is divided into two guides for installing and maintaining the Nastar and EBC&EMS
service components, respectively.
This guide is used for installing and maintaining the EBC&EMS service component. This
issue is the first release.
Contents
4 FAQs...............................................................................................................................................99
4.1 Hardware Problems Related to the SAU......................................................................................................................99
4.1.1 How Can I Set Hard Disks to the RAID 1 Mode......................................................................................................99
4.1.2 How Can I Query the Hardware Mapping Relations of Network Adapters............................................................105
4.1.3 How Can I Query the Network Configuration of Ethernet Adapters......................................................................106
4.1.4 How Can I Boot the SAU from the USB................................................................................................................106
4.1.5 How Do I Ensure Normal Communication Between the SAU and OMU When the OMU's Internal Network
Segment Changes.............................................................................................................................................................108
4.1.6 How Can I Set the Link Mode of the External Ethernet Adapter of the SAU.........................................................110
4.2 Software Problems Related to the SAU.....................................................................................................................112
4.2.1 How Do I Use FileZilla to Transfer Files?..............................................................................................................112
4.2.2 How Can I Log In To the SAU in SSH Mode.........................................................................................................114
4.2.3 How Can I Start the omutool...................................................................................................................................116
4.2.4 How Can I Set the IP Address of a PC....................................................................................................................117
4.2.5 How Do I Uninstall SAU Applications?..................................................................................................................118
4.2.6 How Can I Install the Integrity Check Tool for Installation Packages....................................................................121
4.2.7 How Do I Open and Close the Non-Encrypted Json Port of the SAU?..................................................................122
4.2.8 How Do I Manually Update SAU Digital Certificates?..........................................................................................124
4.2.9 How Do I Query the Occupied Ports on the SAU?.................................................................................................130
4.2.10 How Do I Manually Change the Authentication Key on the SAU?......................................................................131
4.2.11 How Do I Enable or Disable the SSL Renegotiation Function on the SAU?........................................................132
4.2.12 How Do I Set SSL Configuration Parameters on the SAU by Running Commands on the Server?....................134
4.2.13 How Do I Set FTP Client Parameters on the SAU by Running Commands on the Server?.................................137
1 Mapping Versions
This section describes the mapping upper-layer products and NE versions for the SAU.
Context
The Nastar service component supporting Nastar applications, the EBC service
component supporting EBC applications, and the EMS service component supporting
Trace Server applications can be deployed on the SAU board.
The services for the Nastar, EBC, and EMS service components do not affect each other.
EBC is the feature of the U2000/M2000 product. Trace Server is the component of the
U2000/M2000 product.
This document describes how to deploy and maintain the EBC and EMS service
components on the SAU board.
If the NE version used with the SAU is earlier than BSC6900 V900R015C00SPH516/BSC6910
V100R015C00SPH516, only one SAU board where the Nastar service component is deployed can
be configured on the NE. The EBC and EMS service components cannot be deployed on the SAU
board.
If the NE version used with SAU is BSC6900 V900R015C00SPH516/BSC6910
V100R015C00SPH516 or later, a maximum of two SAU boards can be configured on the NE. One
board is used for deploying the Nastar service component. The other board is used for deploying the
EBC or EMS service component or both.
If both SAU boards are configured on the NE side, the software version of the SAU board for
deploying the Nastar service component must be GENEX Nastar V600R011C00SPC201 or later. If
the software version does not meet the requirement, you need to upgrade it. Otherwise, it cannot
support two SAU boards. The software version of the SAU board for deploying the EBC/EMS
service component supports two SAU boards by default.
Version mapping
Service Upper- Upper- RAT NE Version
Compone Layer Layer
nt Product Product
Installed Version
on the
SAU
Figure 1.1 Networking of the SAUc board (with a single LAN switch)
Figure 1.2 Networking of the SAUc board (with two LAN switches)
Figure 1.3 Networking of the ESAUa board (with a single LAN switch)
Figure 1.4 Networking of the ESAUa board (with two LAN switches)
Functions
The SAU board provides the following functions:
For the Trace Server:
− Filters and aggregates raw data reported by NEs according to data subscription
requests from the Trace Server.
− Sends data preprocessing results to the Trace Server. The Trace Server then provides
the data for the SONMaster and PRS.
For the EBC (Event-based Counter) feature:
− Filters and aggregates raw data reported by NEs according to activated EBC counters
on the U2000/M2000.
− Sends data preprocessing results to the U2000/M2000 for the U2000/M2000 to
generate EBC counters.
SAUc Panel
Figure 2-6 shows the SAUc panel.
To power off the SAUc, you need to simultaneously pivot the top and bottom ejector levers away from
the front panel of the SAUc. After the OFL (OFFLINE) indicator is on steady, remove the SAUc.
ESAUa Panel
Figure 2-7 shows the ESAUa panel.
To power off the ESAUa, you need to simultaneously pivot the top and bottom ejector levers away
from the front panel of the ESAUa. After the OFFLINE indicator is on steady, remove the ESAUa.
The SHUTDOWN button is used only for powering off the board in emergency.
The RESET button is used to reset the system. It works in the same way as the reset button on the
PC.
Pressing the SHUTDOWN or RESET button may scratch the face of hard disks in the ESAUa
board. Therefore, you are advised not to perform this operation frequently.
USB0-1 and USB2-3 Operators can use the USB ports USB
only after logging in to the
operating system (OS) running on
the board. The ports does not
require a signal cable or
connection to other devices when
the system runs properly.
Therefore, equipment security is
not affected.
ETH0 to ETH1 The hardware ports are used for RJ45
the communication between the
SAU and EBC, and Trace Server.
ETH2 The port does not require a signal RJ45
cable or connection to other
devices when the system runs
properly. Therefore, equipment
security is not affected.
COM The port does not require a signal DB9
cable or connection to other
devices when the system runs
properly. Therefore, equipment
security is not affected.
VGA Monitor port DB15
USB0-1 and USB2-3 Operators can use the USB ports USB
only after logging in to the
operating system (OS) running on
the board. The ports does not
require a signal cable or
connection to other devices when
the system runs properly.
Therefore, equipment security is
not affected.
ETH0 to ETH1 The hardware ports are used for RJ45
the communication between the
SAU and EBC, and Trace Server.
ETH2 The port does not require a signal RJ45
cable or connection to other
devices when the system runs
properly. Therefore, equipment
security is not affected.
VGA Monitor port DB15
RUN Green ON for 1s and OFF for The board is running properly.
1s
ON for 0.125s and OFF The board is being started.
for 0.125s
ON There is power supply, but the
board is faulty.
RUN Green ON for 1s and OFF for The board is running properly.
1s
ON for 0.125s and OFF The board is being started.
for 0.125s
ON There is power supply, but the
board is faulty.
OFF There is no power supply, or the
board is faulty.
ALM Red OFF No alarm is generated.
ON or blinking An alarm is reported, indicating
that a fault occurs during the board
operation.
ACT Green ON The board is in active mode.
Figure 1.1 Mapping between the ETHxxx and the bondxxx on the SAUc
F_ETH0, F_ETH1, and F_DBG are connected to the external network through the Ethernet ports on the
SAUc panel. B_ETH0, B_ETH1, B_UPDATE0, and B_UPDATE1 are connected to the backplane of the
subrack, and they are not displayed on the SAUc panel.
F_DBG: Used as a debugging Ethernet adapter (bond 2), which is used to connect the
SAU to a PC for SAU commissioning as required. The name of this debugging Ethernet
adapter on the ESAUa panel is ETH2.
B_UPDATE: It is the Ethernet adapter for backup channels (bond3), which is not used
by the SAU currently.
B_ETH0 and B_ETH1: The two Ethernet adapters are teamed as the internal Ethernet
adapter team, that is, bond 0 (vlan 1), which is used for communication between the
SAU and the OMU board in the BSC/RNC (defined as the internal network).
Figure 2-9 shows the mapping between the ETHxxx and the bondxxx on the ESAUa.
Figure 1.1 Mapping between the ETHxxx and the bondxxx on the ESAUa
F_ETH0, F_ETH1, and F_DBG are connected to the external network through the Ethernet ports on the
ESAUa panel. B_ETH0, B_ETH1, and B_UPDATE are connected to the backplane of the subrack, and
they are not displayed on the ESAUa panel.
BSC6900 V900R015 and later The SAUc board can be installed in the vacant
versions slots in MPS or EPS, except the following slots :
MPS
The SAUc board must be installed in the lowest subrack of the cabinet for good heat dissipation.
The SAUc is preferentially installed in the MPS and then the EPS.
When the SAUc is installed in the MPS, if the MPS is reset, all the boards except the OMU and
SAUc will be reset. The services of the SAUc are not affected.
When the SAUc is installed in the EPS, if the EPS is reset, all the boards except the SAUc will be
reset. The services of the SAUc are not affected.
BSC6910 V100R015 and later The ESAUa board can only be installed in any slot
versions except those for the SCUb and GCUa/GCGa. You
are advised to insall the ESAUa in slots 0 and 1 in
the front of the subrack.
The ESAUa must be installed in two adjacent even-odd slots that serve as active and standby slots.
The ESAUa is preferentially installed in the MPS and then the EPS.
When the ESAUa board is installed in the MPS, if the MPS is reset, the services of the ESAUa are
not affected.
When the ESAUa board is installed in the EPS, if the EPS is reset, the services of the ESAUa are not
affected.
The service or process name may contain N, an integer greater than or equal to 0, which indicates that
multiple services or processes can be running concurrently. The number of concurrent services or
processes may vary according to server configurations to maximize system resource usage.
2.6 Precautions
This section describes the precautions. Relevant precautions must be followed to ensure the
proper operation of the SAU.
The SAU can be installed with only the operating system software (including all
necessary driver programs and components) and the SAU applications.
The following operations are prohibited: deleting any directory, modifying the contents
and attributes of any system file, disabling the Ethernet adapter, and modifying the
configuration files of the Ethernet adapter.
The information about both data pre-processing and fault generation is recorded in the
logs of the SAU. To timely and accurately locate and rectify faults, do not delete any log
file on the SAU.
The unauthorized use of patches or upgrade versions may lead to unstable SAU
performance due to version incompatibility.
If the NE version used with the SAU is earlier than BSC6900
V900R015C00SPH516/BSC6910 V100R015C00SPH516, only one SAU board where
the Nastar service component is deployed can be configured on the NE. The EBC and
EMS service components cannot be deployed on the SAU board.
If the NE version used with SAU is BSC6900 V900R015C00SPH516/BSC6910
V100R015C00SPH516 or later, a maximum of two SAU boards can be configured on
the NE. One board is used for deploying the Nastar service component. The other board
is used for deploying the EBC or EMS service component or both.
The SAUc must be used if the SAU is required for the BSC6900.The ESAUa must be
used if the SAU is required for the BSC6910.
If... Then...
The new SAU board is used for Initially install and commission the SAU. For detailed
deploying the EBC service operations, see 3.1 Installing and Commissioning the
component SAU.
An SAU board running the EMS Perform operations by referring to 3.1.6.2 Installing
service component is available SAU Applications (for the EBC and EMS Service
onsite and the EBC service Components). In this case, installing the EBC service
component needs to be deployed component does not affect existing services.
on the SAU board
The operating system of the SAU Reinstall the operating system and SAU applications
breaks down on the SAU. For detailed operations, see 3.2
Reinstalling and Commissioning the SAU.
The EBC service component Uninstall the EBC service component by referring
cannot work properly and the 4.2.5 How Do I Uninstall SAU Applications?, and then
operating system settings of the manually reinstall the EBC service component by
SAU remain unchanged referring to 3.1.6.2 Installing SAU Applications (for
the EBC and EMS Service Components).
If... Then...
The new SAU board is used for Install and commission the SAU. For detailed
deploying the EMS service operations, see 3.1 Installing and Commissioning the
component SAU.
An SAU board running the EBC Perform operations by referring to 3.1.6.2 Installing
service component is available SAU Applications (for the EBC and EMS Service
onsite and the EMS service Components). In this case, installing the EMS service
component needs to be deployed component does not affect existing services.
on the SAU board
The operating system of the SAU Reinstall the operating system and SAU applications
breaks down on the SAU. For detailed operations, see 3.2
Reinstalling and Commissioning the SAU.
The EMS service component Uninstall the EMS service component by referring
cannot work properly and the 4.2.5 How Do I Uninstall SAU Applications?, and then
operating system settings of the manually reinstall the EMS service component by
SAU remain unchanged referring to 3.1.6.2 Installing SAU Applications (for
the EBC and EMS Service Components).
Figure 1.1 Procedure for installing the SAU during initial commissioning
1 Preparing for the Check the settings of the SAU board before delivery,
Installation the availability of the application installation package,
the slot where the SAU board is to be installed, the IP
address, and the computer name.
2 Installing the SAU Install the SAU board to the specific slot. The operating
Board system is installed before delivery.
After the SAU board is installed, you need to connect
the SAU board to the switches by using network cables.
This ensures that the SAU board can communicate with
other components properly.
3 Logging In To the Log in to the SAU by using the debugging IP address of
SAU the SAU. The debugging IP address is set before
delivery.
4 Uploading the SAU Use the FileZilla software to upload the SAU
Applications applications to the SAU board.
5 Installing the SAU Install the SAU applications on the SAU board. Ensure
Applications that the Dopra Linux operating system is installed on
the SAU board.
6 Checking the Check the installation of the SAU applications by
Installation of the checking the SAU processes and installation directory.
SAU Applications
(for the EBC Service
Component)
Checking the
Installation of the
SAU Applications
(for the EMS Service
Component)
7 3.1.7.2 Changing the Change the external IP addresses according to actual
IP Address of the situations. In normal cases, do not change the
SAU (for the EBC or debugging IP and internal IP address.
EMS Service
Component)
8 Adding the SAU Run the ADD BRD command on the LMT to add the
Board data of the SAU board so that the BSC can identify the
SAU board.
9 Setting a Central Specify the SAU board where the EBC or EMS service
FTP Server component is installed as the FTP center.
After the preceding operations, you need to check that the SAU is installed and commissioned through
certain check items. For details, see 3.1.8 Checking the Installation and Commissioning of the SAU.
Related operations on the SAU do no have impact on other services. However, considering
the security, you are advised to perform related operations on the SAU at night.
SAU board Perform the following operations before installing the SAUc or
ESAUa board.
If the SAUc or ESAUa needs to be installed or replaced,
keep a new board ready. For details about how to replace
the SAUc or ESAUa, see 3.3 Replace an SAU Board.
If the operating system of the SAUc or ESAUa needs to be
reinstalled, ensure that the original SAUc or ESAUa
functions properly.
PC The PC helps users operate the SAU.
Ethernet cable Keep the Ethernet cable ready before connecting the near end
to the SAU through the debugging port.
Keep the Ethernet cable ready for connecting the SAU to the
switch.
Before downloading the software, ensure that you have a user account at
http://support.huawei.com and you are authorized to download software packages. If you are
not authorized to download the packages, contact the website administrator to apply for the
rights.
SAU SAU application Software > Carrier Software & Site initial
application software package Core Network > Core Network > commissioning
NMS Value-Added Services & and reinstallation
Tools > OSS > iManager M2000-
TOOL > iManager TOOL(OSS-
SAU)V100R001CXXSPCXXX
The software package name is
xSAUV100R001CXXSPCXXXS
AU_PARC_X86_32_pkg.tar
Integrity Used to check the Huawei technical support is Site initial
check tool SAU software advised to log in to commissioning
for package integrity http://support.huawei.com and and reinstallation
software choose Search by Category >
packages Tools to obtain the software
package by typing the software
package name or keywords in
Keyword.
The software package name is
ipsi_signcli_suse10_X86_32_pkg
_2_0.tar
If multiple search results meet the
criteria, you are advised to obtain
the latest version.
PuTTY Used to log in to Tools > Mini-tool Software > Site initial
the SAU remotely Core Network Product Line > commissioning
Wireless-OSS > iManger M2000- and reinstallation
II > Public Tools
The software package name is
PuTTY.zip
FileZilla Used to transfer Tools > Mini-tool Software > Site initial
files Core Network Product Line > commissioning
Wireless-OSS > iManger M2000- and reinstallation
II > Public Tools
The software package name is
FileZilla.zip
Dopra_Lin Operating system Huawei technical support is Site reinstallation
ux_USB advised to log in to
Check whether the onsite link mode of the LAN switch is auto-negotiation. If the link mode of the LAN
switch is not auto-negotiation, set the link mode by referring to 4.1.6 How Can I Set the Link Mode of
the External Ethernet Adapter of the SAU.
Planning Routes
Plan SAU route information in advance by referring to the OMU route planning on the live
network and ensure that the SAU can communicate properly with the Trace Server, SAU, and
U2000/M2000.
%%DSP SAU:;%%
RETCODE = 0 Execution succeeded.
--- END
Context
The SAUc must be used if the SAU is required for the BSC6900.
The ESAUa must be used if the SAU is required for the BSC6910.
When you configure two SAU boards, you need to run the SET SAUCENTER command
to cancel the central FTP server setting of the first SAU board before installing the second
SAU board. This avoids the conflict between the default internal network IP address of the
second SAU board and the internal network IP address of the central FTP server. After you
install hardware and application software of the second SAU board, reconfigure the central
FTP server by referring to 3.1.7.4 Setting a Central FTP Server.
If you cancel and reset the central FTP server, the SAU boards will fail to receive data
temporarily, affecting existing services. Therefore, you are advised to make preparations
and cancel and reset the the central FTP server at night.
Prerequisites
The tools used for installation are ready. The tools are as follows: ESD wrist strap,
Phillips screwdriver, and ESD box/bag.
The SAUc board to be installed is ready.
The power-on check is performed on the cabinet.
The slot where the SAUc is to be installed is confirmed. For details, see 2.3 Slot
Planning.
Context
Before performing the following operations, wear the ESD wrist strap and connect the
ground core of the wrist strap to the ESD jack on the cabinet. If no ESD wrist strap is
available or no proper location for grounding the wrist strap, wear the ESD gloves.
When you configure two SAU boards, you need to run the SET SAUCENTER command
to cancel the central FTP server setting of the first SAU board before installing the second
SAU board. This avoids the conflict between the default internal network IP address of the
second SAU board and the internal network IP address of the central FTP server. After you
install hardware and application software of the second SAU board, reconfigure the central
FTP server by referring to 3.1.7.4 Setting a Central FTP Server.
Procedure
Step 1 Take out the SAUc board from the ESD box, and check the pins and socket of the board.
If any pin or socket is in an improper condition, contact Huawei technical support engineers.
Step 2 As shown in (1) of Figure 3-2, press the retaining springs on the front panel inwards and, at
the same time, raise the ejector levers of the front panel outwards to free the front panel from
the self-locking springs, and then continue to raise the ejector levers until they cannot be
raised, as shown in (2) of Figure 3-2.
Step 3 Hold the front panel with one hand and hold the lower edge of the board with the other hand,
and then insert the SAUc board into the subrack along the guide rail till the board fully fits
into the subrack and the ejector levers are partially closed.
Insert the board slowly and with balanced force to avoid damage to the pins on the back of the
board and the metal sheets in the slot touching the backplane in the slot.
Step 4 As shown in (3) of Figure 3-2, lower the ejector levers by an angle of about 60° so that the
ejector levers fix the self-locking springs tightly. At this time, the board is securely fixed to
the backplane, and the ejector levers are locked with the subrack tightly, as shown in (4) of
Figure 3-2.
Step 5 Press the captive screws inwards and fasten them clockwise to fix the SAUc board, as shown
in (4) of Figure 3-2.
The springs of the captive screws on the ejector levers ensure that the captive screws can be tightened
with the screws on the subrack through the corresponding holes.
Step 6 Check whether the SAUc board can be powered on normally according to the LEDs on the
SAUc board.
Step 7 Use the Ethernet cable to connect the switch to the ETH0 port and the ETH1 port of the SAUc
board.
Connect the switch connected to the OMU to the ETH0 port and the ETH1 port of the SAUc
and ensure that the SAUc and switch are in the same external VLAN.
Ensure the ETH0 port and the ETH1 port are connected by the Ethernet cable to the external
VLAN. If not, the SAU will generate the alarm named the SAU hardware fault. For details,
see section 6.1 Alarm List.
----End
Prerequisites
The tools used for installation are ready. The tools are as follows: ESD wrist strap,
Phillips screwdriver, and ESD box/bag.
The ESAUa board to be installed is ready.
The power-on check is performed on the cabinet.
The slots for housing the board have been determined. For details, see 2.3 Slot Planning.
Context
Before performing the following operations, wear the ESD wrist strap and connect the
ground core of the wrist strap to the ESD jack on the cabinet. If no ESD wrist strap is
available or no proper location for grounding the wrist strap, wear the ESD gloves.
When installing ESAUa board, use a 5 x 200 screwdriver with a long handle. The
screwdriver uses type No.1 bit, it is 200 mm (7.87 in.) long in total, and the diameter of
the bit is 5 mm (0.17 in.).
When you configure two SAU boards, you need to run the SET SAUCENTER command
to cancel the central FTP server setting of the first SAU board before installing the second
SAU board. This avoids the conflict between the default internal network IP address of the
second SAU board and the internal network IP address of the central FTP server. After you
install hardware and application software of the second SAU board, reconfigure the central
FTP server by referring to 3.1.7.4 Setting a Central FTP Server.
Procedure
Step 1 Take out the ESAUa board from the ESD box, and check the pins and socket of the board.
If any pin or socket is in an improper condition, contact Huawei technical support engineers.
Step 2 As shown in a of Figure 3-3, press and hold the two locking buttons on the ejector levers, flip
outward the ejector levers, and rotate them to the extreme until they are in the position shown
in (2) of Figure 3-3.
Step 3 Hold the front panel with one hand and hold the lower edge of the board with the other hand,
and then insert the board into the subrack along the guide rail till the board fully fits into the
subrack and the ejector levers are partially closed, as shown in (3) of Figure 3-3.
Insert the board slowly and with balanced force to avoid damage to the pins on the back of the
board and the metal sheets in the slot touching the backplane in the slot.
Step 4 Turn the two ejector levers on the board inward until they are in full contact with the panel, as
shown in (4) of Figure 3-3.
Step 5 Ensure that the two ejector levers hook on to the self-locking latches on the front panel, and
use a screwdriver to tighten captive screws clockwise, as shown in b of Figure 3-3.
The springs of the screws on the ejector levers ensure that the screws can be tightened on the subrack
through the corresponding holes.
Step 6 Check whether the ESAUa board is powered on normally by referring to LEDs on the ESAUa
board.
Step 7 Use Ethernet cables to connect ETH0 and ETH1 on the ESAUa to the switch.
Connect ETH0 and ETH1 on the ESAUa to the switch that is connected to the OMU and
ensure that the ESAUa and switch are in the same external VLAN.
Do connect ETH0 and ETH1 to the external network; otherwise, an SAU hardware fault
alarm will arise. For details, see 6 Appendix B: SAU Fault Alarm Reference.
----End
Prerequisites
You have obtained the external IP address or debugging IP address of the SAU.
For details about the default IP address plan during SAU board delivery, see List for the
SAU Software Configurations Before Delivery.
(Required when the IP address is changed) You have obtained the new IP address from
the field administrator.
Context
OS hardening has been performed for SAU boards before delivery.
After OS hardening is performed, do not remotely log in to the SAU as user root.
Instead, you have to log in to the SAU as user lgnusr and then run the su - root
command to switch to user root.
You need to run all the commands and perform all operations described in this document as user root.
User lgnusr is only used to log in to the SAU.
Procedure
Commissioning During Initial Installation and Reinstallation
1. Use a cable to connect the PC to the port for commissioning (ETH2) of the SAU.
2. Set the IP address of the PC to be on the same network segment as the debugging IP
address of the SAU. The default debugging IP address of the SAU is 192.168.6.50 and
the subnet mask is 255.255.255.0.
3. On the PC, open the SSH client (for example, PuTTY) and type the debugging IP
address of the SAU.
4. Log in to the SAU as the operating system user lgnusr.
For details about the user name and password plan, see 7.3 User Names and Initial User
Passwords.
5. Run the su - root command and press Enter. Then, type the password of user root to
switch to user root.
Routine Operation and Maintenance
1. Use a network device to connect the PC and he ETH0 or ETH1 port of the SAU board.
2. On the PC, open the SSH client (for example, PuTTY) and type the external IP address
of the SAU.
3. Log in to the SAU as the operating system user lgnusr.
For details about the user name and password plan, see 7.3 User Names and Initial User
Passwords.
4. Type the su - root command and press Enter. Then, type the password of user root to
switch to user root.
----End
Follow-up Procedure
Exit the SAU after you have completed the operation and maintenance on the SAU using
PuTTY on your PC.
1. Type exit and press Enter to exit PuTTY.
Procedure
Step 1 Log in to the SAU based on 3.1.4 Logging In to the SAU.
If you can only log in to the SAU board as a user other than user root, such as user lgnusr, and then run
the su - root command to switch to user root, OS hardening has been performed on the SAU board.
Otherwise, OS hardening has not been performed. If this occurs, contact Huawei technical support.
----End
Prerequisites
You have obtained the SAU application package, see 3.1.2 Preparing for the Installation.
Context
This section assumes that the SAU application package is stored in the local directory
D:\xSAUV100R001CXXSPCXXX.
The name of the SAU application package:
xSAUV100R001CXXSPCXXXSAU_PARC_X86_32_pkg.tar
Procedure
Step 1 Create the folder xSAUV100R001CXXSPCXXX in the root directory of disk D on the local
PC, and store the installation package
xSAUV100R001CXXSPCXXXSAU_PARC_X86_32_pkg.tar in the folder.
Step 2 Log in to the SAU. For details, see 3.1.4 Logging In to the SAU.
Step 3 Run the following command as user root to check whether the /mbsc/upgrade directory
exists.
# ls /mbsc/upgrade/
If a message is displayed stating that the file or directory does not exist, proceed to Step 4 to
create the directory. If the directory exists, the system automatically goes to Step 5.
Step 4 Run the following command as user root to create the /mbsc/upgrade directory.
# mkdir -p /mbsc/upgrade
Step 5 Use FileZilla to upload the xSAUV100R001CXXSPCXXX folder containing the SAU
application package to the SAU board.
For details about how to use FileZilla, see 4.2.1 How Do I Use FileZilla to Transfer Files?.
If... Then...
You can directly log in to the SAU board as OS hardening has not performed on the
user root SAU board.
The configuration information required for
uploading the files is as follows:
User and password: root and its password
Folder to be uploaded:
xSAUV100R001CXXSPCXXX
Directory of files on the SAU board:
/mbsc/upgrade
You can only log in to the SAU board as a OS hardening generally has been performed
user other than user root, such as user on the SAU board.
lgnusr, and then run the su - root command You need to set the following information
to switch to user root when uploading files and continue to
perform Step 6 after the upload is complete.
User and password: lgnusr and its
password
Folder to be uploaded:
xSAUV100R001CXXSPCXXX
Directory of files on the SAU board:
/home/lgnusr
Step 6 If you upload files to the /home/lgnusr directory as user lgnusr, run the following commands
as user root to move the folder containing the SAU application program to the
/mbsc/upgrade directory:
# cd /home/lgnusr/
# mv xSAUV100R001CXXSPCXXX /mbsc/upgrade/
----End
3.1.6.2 Installing SAU Applications (for the EBC and EMS Service
Components)
You can install different service components on the SAU board by selecting related
parameters during the SAU application installation. This section describes how to install EBC
and EMS service components.
Prerequisites
You have checked the version of the operating system of the SAU. For details, see 3.4.1
Checking the Version of the Operating System.
You have uploaded the SAU application package to the SAU board. For details, see
3.1.6.1 Uploading the SAU Application Package.
You have obtained the language information about the U2000/M2000.
Context
The default installation directory of the EBC service component is /opt/ebcsau after the
SAU applications are installed. You are not allowed to change this directory.
The default installation directory of the EMS service component is /opt/emssau after the
SAU applications are installed . You are not allowed to change this directory.
Only one SAU board can be used for deploying the EBC and EMS service components
or either of them.
Procedure
Step 1 Install the integrity check tool for the SAU application package. For details, see 4.2.6 How
Can I Install the Integrity Check Tool for Installation Packages.
Step 2 Log in to the SAU. For details, see 3.1.4 Logging In to the SAU.
Step 3 Run the following command to query information about the service components that have
been installed on the SAU board. Record the information.
# ls /opt
If the system output contains ebcsau or emssau, the EBC service component or EMS
service component has been installed on the SAU board.
Step 4 Switch to the directory where the SAU application package is stored.
Assume that the SAU application package is stored in the
/mbsc/upgrade/xSAUV100R001CXXSPCXXX directory. Type the following command and
press Enter:
# cd /mbsc/upgrade/xSAUV100R001CXXSPCXXX
Step 5 Run the following command to check the SAU application package integrity:
# /opt/signtool/verifyPkgSign
xSAUV100R001CXXSPCXXXSAU_PARC_X86_32_pkg.tar
If the command output contains SignCLI Info: Successfully verified, the package is
intact.
If the command output contains fail or error, the SAU application package integrity fails to be
verified. If this occurs, contact Huawei technical support.
If the command output contains /opt/signtool/verifyPkgSign: No such file or directory, the
integrity check tool has not been installed. You must install the integrity check tool before checking
the SAU application package integrity. For details, see 4.2.6 How Can I Install the Integrity Check
Tool for Installation Packages.
Step 6 Run the following command to decompress the SAU application package:
# tar xzf xSAUV100R001CXXSPCXXXSAU_PARC_X86_32.tar.gz
Step 7 Run the following commands to modify the owner of the files and the folders.
# chown -R root:root xSAUV100R001CXXSPCXXXSAU*
Step 8 Run the following commands to execute the install_oss.sh script, and press Enter.
# cd xSAUV100R001CXXSPCXXXSAU
# ./install_oss.sh
Step 9 When the following information is displayed, select the required upper-layer applications
based on the information queried in Step 3 and site requirements:
Please input the application which you want to access:
1. ebc
2. ems
The SAU application package contains service components and board management software.
When installing the first service component, the system prompts you to enter the required NE
information and install the board management software (as described in Step 10 through Step 15).
When installing the second service component on the same SAU board, the system only installs the
service component and does not install the board management software. In addition, the system does
not prompts for the required NE information.
If... Then...
The EMS service component has 1. Type 1 to select ebc. The system starts
been installed on the SAU board installing the EBC service component.
and the EBC service component
also needs to be installed onsite
Step 10 When the following information is displayed, selected a required NE and press Enter.
For example, to select a BSC6910, type 1.
The command output is as follows:
Please Choose Supported Product Type:
Index Product Type
0 BSC6900
1 BSC6910
Please Input Index:
Step 11 When the following information is displayed, type a RAT index and press Enter.
For example, to select UMTS, type 1.
Step 12 When the following information is displayed, type an OMU version index and press Enter.
For example, to select V100R015, type 0.
The command output is as follows:
Please Choose Supported OMU Version:
Index OMU Version
0 V100R015
1 V100R016
2 V100R017
Step 13 When the following information is displayed, type a patch version range index and press
Enter.
The command output is as follows:
Please Choose V100R015 Supported Patch:
Index Patch No.
0 between C00(include) and C00SPH516(exclude)
1 C00SPH516 and Later
2 C01 and Later
Step 14 When the following information is displayed, type the language information and press Enter:
The command output is as follows:
# The SAU language version. eg: eng/chs
Please input a valid version :
The language of the SAU must be the same as that of the U2000/M2000. Otherwise, MML
commands will fail to be parsed.
Step 15 When the following information is displayed, type Y (case insensitive). The system starts
installing SAU applications.
The command output is as follows:
Please affirm input information. input Y to continue; input E to exit. ->
When the following information is displayed, the SAU applications are installed successfully.
Or
Install SAU for ems successfully.
If you have reinstalled the SAU after uninstalling the SAU application software and BAM
platform and you have changed the internal network segment of the SAU board, the
network segment for the changed internal IP address of the SAU is automatically restored
to the default internal network segment.
In this case, you need to change the internal network segment of the SAU board by
referring to 4.1.5 How Do I Ensure Normal Communication Between the SAU and OMU
When the OMU's Internal Network Segment Changes to ensure that the network segment
is consistent with the internal network segment of the OMU.
----End
3.1.6.3 Checking the Installation of the SAU Applications (for the EBC
Service Component)
This section describes how to check the installation of the SAU applications. The default
installation directory of the EBC service component in the SAU application software package
is /opt/ebcsau. The following items are stored in the installation directory of the SAU
applications: the SAU application components and data used or generated during operations.
In addition, you can check the installation of the SAU applications through the progress bar.
Prerequisites
The SAU applications are installed on the SAU server (for details, see 3.1.6.2 Installing
SAU Applications (for the EBC and EMS Service Components)).
You have logged in to the SAU server (for details, see 3.1.4 Logging In to the SAU).
Procedure
Step 1 Start SAU processes, including the SAU service processing processes and board management
processes.
Run the following commands and then press Enter.
# cd /opt/ebcsau
# . ./svc_profile.sh
# sau4ebc_start
Step 2 Check the status of the SAU processes.
1. Run the following commands to check the status of the SAU service processing
processes and then press Enter.
# cd /opt/ebcsau
# . ./svc_profile.sh
# sau4ebc_ps
The last line in the command result is [Not Running : n].
2. Run the following command to check the status of the board management processes and
then press Enter.
# /etc/rc.d/saud status
The status of the processes in the displayed The board management processes run
information are running properly and the SAU applications are
installed successfully.
The status of the processes in the displayed The board management processes run
information are unused or another status abnormally and the SAU applications fail to
be installed. You need to uninstall the SAU
and then install it again.
# ll
Table 3-5 lists the main subfolders of the SAU applications.
Directory Description
----End
3.1.6.4 Checking the Installation of the SAU Applications (for the EMS
Service Component)
This section describes how to check the installation of the SAU applications. The default
installation directory of the EMS service component in the SAU application software package
is /opt/emssau. The following items are stored in the installation directory of the SAU
applications: the SAU application components and data used or generated during operations.
In addition, you can check the installation of the SAU applications through the progress bar.
Prerequisites
The SAU applications are installed on the SAU server (for details, see 3.1.6.2 Installing
SAU Applications (for the EBC and EMS Service Components)).
You have logged in to the SAU server (for details, see 3.1.4 Logging In to the SAU).
Procedure
Step 1 Start SAU processes, including the SAU service processing processes and board management
processes.
Run the following commands and then press Enter.
# cd /opt/emssau
# . ./svc_profile.sh
# sau4ems_start
2. Run the following command to check the status of the board management processes and
then press Enter.
# /etc/rc.d/saud status
The status of the processes in the displayed The board management processes run
information are running properly and the SAU applications are
installed successfully.
The status of the processes in the displayed The board management processes run
information are unused or another status abnormally and the SAU applications fail to
be installed. You need to uninstall the SAU
and then install it again.
# ll
Table 3-6 lists the main subfolders of the SAU applications.
Directory Description
----End
Fixe One The default internal IP address of All the IP addresses for the
d the SAU is 80.168.3.250 before internal network are centrally
inter delivery. During the startup of planned, and therefore the
nal the SAU, the system calculates a fixed internal IP address is
IP new internal IP address based on not allowed to be changed.
addr the existing internal network Otherwise, the IP address for
ess segment and then changes the the SAU will conflict with
internal IP address of the SAU to the IP address for the OMU,
the new one. and therefore the
If the NE version used with the communication between the
SAU is earlier than BSC6900 SAU and the OMU fails.
V900R017C00SPC500/BSC691
0V100R017C00SPC500, or SAU
version is earlier than
V100R001C00SPC330, when
the system automatically
calculates the IP address, the
existing internal network
segment is not changed, for
example, xxx.yyy of the
xxx.yyy.3.250.
If the NE version used with the
SAU is BSC6900
V900R017C00SPC500/BSC691
0V100R017C00SPC500 or later,
and the SAU version is
V100R001C00SPC330 or later,
when the SAU software is
started, the system automatically
calculates and changes the last
two digits of the internal IP
address. The system also
automatically synchronizes the
3.1.7.2 Changing the IP Address of the SAU (for the EBC or EMS Service
Component)
This section describes how to change the IP address, masks, and gateway IP addresses of the
SAU Ethernet adapter by using the omutool. All the information about the IP address can only
be changed with the permission of field engineers.
Prerequisites
The SAU applications are installed on the SAU server (for details, see 3.1.6.2 Installing
SAU Applications (for the EBC and EMS Service Components)).
You have logged in to the SAU (for details, see 3.1.4 Logging In to the SAU).
The planned IP address is obtained.
Procedure
Step 1 Stop SAU processes.
If both EBC and EMS service components are deployed on the SAU board, their processes must be
stopped.
1. Switch the current directory to the directory where the omutool is saved.
Assume that the active workspace of the SAU is in /mbsc/bam/version_a. Run the
following command, and then press Enter:
# cd /mbsc/bam/version_a/bin/bam
You can query the active workspace of the SAU by one of the following methods:
Run the command in the SAU: cat /mbsc/bam/common/reg.ini|grep bamarea|sed -e
"s/bamarea//"|sed -e "s/=//".
Log in to the LMT, run the MML command DSP SAUAREA to query the active workspace of the
SAU.
2. Run the following command to start the omutool and display parameter information
about the omutool:
# ./omutool
Step 3 Run the following command to change the fixed external IP addresses, masks, and gateway IP
addresses, and then press Enter.
# ./omutool extercard IP address mask gateway IP address
For example,
# ./omutool extercard 10.161.10.100 255.255.255.0 10.161.10.1
You are advised to set the external IP address for the SAU and that for the OMU on the same
network segment.
To change the IP addresses of the SAU, you must follow the principle of IP address planning by
referring to 3.1.7.1 SAU IP Addresses and Planning Principles. When entering the command, ensure
that there is a space between the IP address and the mask.
If a dialog box stating change gateway failed,because File exists is displayed, the changed IP
address is identical with that before the change.
The changed IP addresses are recorded in 7.1 Data Sheet of SAU Software Installation Information.
You can also run the ./omutool gateway gateway IP address command to change the gateway IP
address.
----End
Follow-up Procedure
Ensure that the IP address of the SAU has been set properly on U2000/M2000.
1. Log in to the U2000/M2000 client and open the topology view.
2. Right-click the base station controller and choose properties from the shortcut menu. In
the displayed dialog box, check that the IP address of the SAU has been set properly.
− If a single SAU board is configured, the IP address of the SAU is set to the external
IP address of the SAU.
− If two SAU boards are configured, the IP address of the SAU is set to the external IP
address of the SAU board that has been set to the central FTP server.
For details about how to check and configure NE attributes on the U2000/M2000, see the U2000/M2000
online help.
You do not need to change the internal network segment and debugging IP address of the
SAU except in the following conditions.
− If the internal network segment of the OMU has been changed, then the internal
network segment of the SAU need to be changed. For detailed operations, see 4.1.5
How Do I Ensure Normal Communication Between the SAU and OMU When the
OMU's Internal Network Segment Changes.
− In consideration of security, if the default debugging IP address conflicts with the IP
address on the existing network, you need to change the debugging IP address.
Before changing the debugging IP address, you need to check whether the default debugging IP address
of the SAU conflicts with the IP address on the existing network by querying the debugging IP address
of the OMU. For details, consult the operators or read relevant OMU materials.
Type the following command and then press Enter.
# cd /mbsc/bam/version_a/bin/bam
# ./omutool debugcard IP address
For example,
# ./omutool debugcard 192.168.6.60
Prerequisites
You have logged in to the LMT.
Procedure
Step 1 Run the ADD BRD command to add an SAU board.
Step 2 Run the DSP SAU command to check the result of adding the SAU board.
If you can query the information of the SAU, the adding operation is successful.
If you can not query the information of the SAU, the adding operation is unsuccessful.
----End
Prerequisites
You have logged in to the LMT.
Context
If two SAU boards are deployed onsite, set the SAU board where the EBC/EMS service component is
installed as the central FTP server. This is because the EBC/EMS service component has higher time
requirements.
Procedure
Step 1 Run the DSP SAU command to know the Subrack No. and Slot No. of SAU board.
Run the DSP SAU command directly, and do not set the parameters.
Step 2 Optional: Log in to the SAU by referring to 3.1.4 Logging In to the SAU, and run the ls /opt
command to query information about the service component that has been installed on the
SAU board.
Step 3 Perform the following operations as required.
If... Then...
There is only one SAU board at the Run the SET SAUCENTER command to set
site the SAU board as the central FTP server.
There are two SAU boards at the Run the following operations to set the SAU
site board where the EBC/EMS service component
is installed as the central FTP serve:
1. If the another SAU board other than SAU
board where the EBC/EMS service
component is installed has been set to the
central FTP server, run the SET
SAUCENTER command to cancel the
setting.
2. Run the SET SAUCENTER command to
set the SAU board where the EBC/EMS
service component is installed to the central
FTP server.
NOTICE
During the change of the central FTP server for the
SAU, the SAU board will fail to receive data for a
short period of time.
----End
Prerequisites
You have installed and commissioned the SAU.
Procedure
Check SAU installation and commissioning.
Check SAU 1. Log in to the SAU using the external IP address. For details, see the
processes operations in the routine operation and maintenance scenario
specified in 3.1.4 Logging In to the SAU.
2. Check the status of SAU processes by referring to 3.4.9.1 Checking
the Status of SAU Processes (for the EBC Service Component) or
3.4.10.1 Checking the Status of SAU Processes (for the EMS
Service Component).
Verify that 1. Log in to the SAU using the external IP address.
communication 2. Run the ping command to check that communication is proper
is proper between the SAU and EBC, and Trace Server (EMS service
between the component).
SAU and the # ping EBC/Trace Server external IP address
EBC, and Trace
Server (EMS
service
component)
Check whether Run the LST SAUCENTER command to check that the SAU board
the SAU board where the EBC/EMS service component is deployed has been set as a
is set as the central FTP server.
central FTP NOTE
server You can run the DSP SAUINSTANCE command to query information about the
service component installed on an SAU board.
Check whether 1. Log in to the U2000/M2000 client and open the topology view.
the IP address 2. Right-click the base station controller and choose properties from
of the SAU has the shortcut menu. In the displayed dialog box, check that the IP
been address of the SAU has been set properly.
configured on If a single SAU board is configured, the IP address of the SAU
the is set to the external IP address of the SAU.
U2000/M2000 If two SAU boards are configured, the IP address of the SAU is
set to the external IP address of the SAU board that has been set
to the central FTP server.
NOTE
For details about how to check and configure NE attributes on the
U2000/M2000, see the U2000/M2000 online help.
----End
1 3.1.2 Preparing for Check the configuration of the SAU board and the
the Installation availability of the SAU application installation package.
2 3.2.2.1 Preparing the Use the USB installation CD-ROM to quickly install the
USB Installation Dopra Linux operating system during the reinstallation.
CD-ROM
3 3.2.2.2 Installing the
Operating System
4 3.1.4 Logging In to Log in to the SAU through the external fixed IP address
the SAU of the SAU. The external fixed IP address is recorded in
7.1 Data Sheet of SAU Software Installation
Information.
5 3.1.6.1 Uploading Use the FileZilla software to upload the SAU
the SAU Application applications to the SAU board.
Package
6 3.1.6.2 Installing Install the SAU applications on the SAU board.
SAU Applications
(for the EBC and
EMS Service
Components)
7 3.1.6.3 Checking the Check the operating status of the SAU applications by
Installation of the checking the SAU installation directory.
SAU Applications
(for the EBC Service
Component)
3.1.6.4 Checking the
Installation of the
SAU Applications
(for the EMS Service
Component)
8 3.1.7.2 Changing the Change the external IP addresses according to actual
IP Address of the situations. In normal cases, do not change the
SAU (for the EBC or debugging IP and IP address segment.
EMS Service
Component)
9 Setting a Central Specify the SAU board where the EBC or EMS service
FTP Server component is installed as the FTP center.
After the preceding operations, you need to check that the SAU is installed and commissioned through
certain check items. For details, see 3.1.8 Checking the Installation and Commissioning of the SAU.
Prerequisites
The SAU board is SAUc or ESAUa.
The capacity of the USB disk is greater than 1 GB.You are advised to prepare the USB
installation CD-ROM with a blank USB disk. If you use a USB disk containing data, the
data may be lost.
The PC must meet one of the following requirements:
The Windows 7 Professional operating system has been installed. The version of
Dopra_Linux_U tool package must be DOPRA Linux USB Disk Creator v1.1.1 or later.
The USB disk is inserted into the USB port on the PC.
The Dopra_Linux_U tool package is obtained. For details, see 3.1.2 Preparing for the
Installation.
The IP addresses and SAU name planned by the customer are obtained.
Context
The USB installation CD-ROM is used in the following scenarios:
Initial installation of the SAU operating system
Restoration of the collapsed SAU operating system
When the USB installation CD-ROM is used to perform operations on the SAU, the data on
the SAU may be lost or reserved:
If the operation mode of the USB installation CD-ROM is install, the SAU hard disk is
formatted, and the SAU data is lost. Ensure that you have backed up the SAU data before
installing the SAU operating system through the USB installation CD-ROM.
If the operation mode of the USB installation CD-ROM is recover, the SAU operating
system is restored, and the SAU application data is reserved.
If the operation mode of the USB installation CD-ROM is upgrade, the SAU data is
removed to the new operating system smoothly, and the SAU application data is
reserved.
Procedure
Step 1 Preparing the configuring files
1. Double-click the Dopra Linux\default_config\configuration_files folder in the Dopra
Linux tool package.
2. Set each configuration file according to Table 3-10.
You can open each configuration file by using a tool such as the UltraEdit-32 to set
various configuration items of each file.
ifcfg-bond1 Paths for Used for You can set the following configuration
saving configuring the items:
configurati external Ethernet IPADDR, indicating the fixed IP
on files are adapter team of the address for the Ethernet adapter
as follows SAU team
according
ifcfg-bond2 to the SAU Used for NETMASK, indicating the subnet
board type: configuring the mask for the Ethernet adapter team
commissioning NETWORK, indicating the network
Path for Ethernet adapter of
the address for the Ethernet adapter
the SAU team
SAUc
ifcfg-vlan1 board: Used for BROADCAST, indicating the
Dopra configuring the broadcast address for the Ethernet
Linux\d internal Ethernet adapter team
efault_c adapter team of the The preceding configuration items
onfig\o SAU must meet the requirements as follows:
muc\co
nfigatio
IPADDR&NETMASK =
n_files\ NETWORK
networ IPADDR|(~NETMASK) =
k BROADCAST
Path for & indicates the AND logical operation,
the | indicates the OR logical operation,
ESAUa and ~ indicates the CPL logical
board: operation. For example,
Dopra 10.121.139.201 & 255.255.255.0 =
Linux\d 10.121.139.0; 10.121.139.201 |
efault_c (~255.255.255.0) = 10.121.139.255
onfig\eo NOTICE
mua\co IPADDR=80.168.3.50 in the ifcfg-vlan1
nfigatio file must be changed to
n_files\ IPADDR=80.168.3.250.
networ Do not change other configuration items.
k Otherwise, the network fails.
If two SAU boards are installed, leave
the fixed internal IP address of the
second board empty when you reinstall
the operating system on this board. This
avoids conflicts between the default fixed
internal IP addresses of the two SAU
boards.
After the configuration items are changed, you must convert the format of the configuration items as
follows in accordance with the Dopra Linux operating system. Choose File > Conversions > DOS
to UNIX, and save the file.
The configuration files contain the Ethernet adapters teaming relationship. You cannot change the
teaming relationship manually. Use the default values.
Step 2 Double-click DLUSBCreator-CLI.exe in Dopra Linux\tools to use the tool for creating
USB installation CD-ROM, as shown in Figure 3-5.
Step 3 Select a USB drive for the PC from the USB Drive (Use With Care) drop-down list box.
If the drive of the USB is not displayed, check that the USB installation CD-ROM is inserted properly.
Then, click Refresh to refresh the drive of the USB installation CD-ROM.
Step 4 Click Add dist to add information about the USB installation CD-ROM to be prepared, as
shown in Figure 3-6.
Step 5 Set Dist file path, and click to select the operating system installation file.
By default, the operating system installation file of the SAUc board is saved in Dopra
Linux\default_config\omuc\dopraLinux_target_file\dl-e.target.
By default, the operating system installation file of the ESAUa board is saved in Dopra
Linux\default_config\eomua\dopraLinux_target_file\dl-e.target.
Step 6 If the ESAUa board is used, Set Install Scripts Dir to Dopra
Linux\default_config\eomua\install_scripts. If the SAUc board is used, Install Scripts Dir
is not configured by default.
Step 7 Set Config Scripts Dir, and click to select configuration folders in Step 1.
Paths for saving configuration files are as follows according to the SAU board type:
Path for the SAUc board: Dopra Linux\default_config\omuc\configation_files
Path for the ESAUa board: Dopra Linux\default_config\eomua\configation_files
The system displays a message, prompting you to check whether to format the USB disk. If
the USB disk is to be formatted, the USB installation CD-ROM starts to be created. After the
creation is complete, a message is displayed indicating whether the creation is successful.
----End
Prerequisites
Obtain a VGA cable for connecting the SAU board and the monitor.
Obtain a keyboard that provides USB ports.
Obtain a power cable for connecting the monitor.
The USB installation CD-ROM is prepared. For details, see 3.2.2.1 Preparing the USB
Installation CD-ROM.
The hard disk on the SAU is set to RAID 1. For details, see 4.1.1 How Can I Set Hard
Disks to the RAID 1 Mode.
The SAU is set to be preferentially restarted through the USB port. For details, see 4.1.4
How Can I Boot the SAU from the USB .
There are two USB ports available on the SAU board panel.
The USB disk with LED is inserted into the USB port of the SAU board. If the LED is on, then the USB
port is available.
Procedure
Step 1 Insert the USB installation CD-ROM into any of the USB ports on the SAU board panel.
Step 2 Press the RESET or PWRBTN button on the panel of the SAU board to reset the SAU board.
The installation of the operating system starts.
Step 3 Check whether the SAU operating system is successfully installed through either of the
following methods.
Method 1: Wait for 5 to 10 minutes to view the status of the LEDs on the SAU board
panel.
The state of the LEDs on the SAU board panel can be: RUN LED flashes, ALM LED flashes, ACT LED
flashes, and OFFLINE LED is off.
Table 1.1 Status of the LEDs on the SAUc/ESAUa board panel when the SAU operating system is
installed
Board Successful Installation Failed Installation
Method 2: Connect the display to the VGA port on the SAU board panel. The SAU
operating system is successfully installed if the following message is displayed:
Please login from TTY2(Press ALT-F2).
----End
Follow-up Procedure
If the SAU operating system fails to be installed, perform the following operations:
1. Check that the SAU is preferentially started up through the USB port
by referring to 4.1.4 How Can I Boot the SAU from the USB .
2. Check whether the configuration files and operating system installation scripts are
correct.
− If the configuration files and operating system installation scripts are incorrect,
perform the operations in 3.2.2.1 Preparing the USB Installation CD-ROM.
− If the configuration files and operating system installation scripts are correct, contact
Huawei technical support engineers.
If the SAU operating system is installed successfully, log in to the SAU by referring to
3.1.4 Logging In to the SAU.
Prerequisites
The tools used for replacing the SAU board are ready. The required tools are as follows:
ESD wrist strap, Phillips screwdriver, and ESD box/bag.
You have prepared a new SAU board.
You have powered off the SAU board to be replaced.
Context
The following items of the new SAU board must be consistent with those of the SAU board to
be replaced:
Password of the administrator of the operating system
Internal and external fixed IP addresses
SAU name
When two SAU boards are deployed, specify the SAU board where the Nastar service
component is installed as the FTP center if the SAU board where the EBC or EMS service
component is installed needs to be replaced due to certain faults. After a new SAU board is
deployed for installing the EBC or EMS service component, specify this SAU board as the
FTP center.
Replacing the SAU board that works independently will disrupt the communication
between the host boards and the SAU, which results in system data loss.
When installing and removing ESAUa board, use a 5 x 200 screwdriver with a long
handle. The screwdriver uses type No.1 bit, it is 200 mm (7.87 in.) long in total, and the
diameter of the bit is 5 mm (0.17 in.).
Procedure
Step 1 Wear the ESD wrist strap and connect the ground core of the wrist strap to the ESD jack on
the cabinet.
If no ESD wrist strap is available or no proper location for grounding the wrist strap, wear the
ESD gloves.
Step 2 Remove the SAU board to be replaced.
1. Loosen the captive screw on the SAU board counterclockwise with a screwdriver, as
shown in A of Figure 3-7.
The preceding figure takes an ESAUa board as an example. The procedure for an SAUc board is similar.
2. Optional: If the board is an SAUc board, gently press the PWRBTN button.
3. Press and hold the two locking buttons, flip outward the ejector levers on the SAU board
panel to unlock them, and rotate them outward. The SAU board is separated from the
backplane, as shown in part B of Figure 3-7.
Turning outwards the ejector levers on the SAU board gives a power-off sign to the SAU board. The
SAU board automatically shuts down the operating system and stops the read/write operations on the
hard disk. Then, the OFFLINE/OFL LED on the SAU board is on steady. In indicates that the SAU
board is powered off.
4. Remove the Ethernet cable, mouse cable, keyboard cable, and monitor cable (if
configured) from the SAU board after the OFFLINE/OFL LED flashes fast and then is
steady blue.
5. Remove the SAU board to be replaced along the guide rail of the subrack, as shown in C
of Figure 3-7.
The preceding figure takes an ESAUa board as an example. The procedure for an SAUc or is similar.
The SAU is preferentially inserted into slots that meet the requirements. For details, see 2.3 Slot
Planning.
3. Turn the ejector levers on the SAU board inwards until they are in position, as shown in
C of Figure 3-8.
4. Tighten the captive screw clockwise with a screwdriver, as shown in D of Figure 3-8.
The new SAU board loads automatically and the RUN LED blinks (0.125s on and 0.125s
off).
5. Install the cables by referring to the labels.
Step 4 Install the SAU Software.
For details, see 3.1.6 Installing the SAU Software.
Step 5 Configure the IP addresses, name and password of the administrator of the operating system
of the new SAU board to ensure that they are the same as those of the replaced SAU board.
For details, see 3.4.2 Changing the IP Address of the SAU Ethernet Adapter Team (for the
EBC or EMS Service Component), 3.4.3 Changing the SAU Name (for the EBC or EMS
Service Component) and 3.4.11.1 Changing the Password of Operating System User root.
Step 6 Confirm that the SAU board works properly.
1. Run the DSP SAU command to query the status of the new SAU board when the RUN
indicator is blinking (1s on and 1s off).
If ... Then ...
2. Check whether the alarms related board faults are displayed on the LMT.
If ... Then ...
Alarms related to board faults are 1. Analyze the alarms according to the alarm
reported information, and then clear the alarms.
2. Go to Step 6.1.
Alarms related to board faults are Go to Step 6.3.
not displayed
3. Run the DSP SAUMODULE command to query the status of the SAU services.
If ... Then ...
----End
Follow-up Procedure
1. Record the name of the site, slot, and board where the faulty board is located and the
version of the board.
2. Check whether there is obvious physical damage to the board. For example, check
whether there are any deformed mechanical parts, burned components, distorted
connectors, and bent or broken-off pins.
3. Record the fault cause, fault symptom, alarm name, status of indicators on the panel of
the board, and details of the procedures for locating and processing the faults on site.
4. Put the board into the ESD bag and then put the bag together with the onsite fault record
into the board box. Keep the box properly.
5. Contact the local Huawei office to handle the faulty board.
Prerequisites
You have logged in to the SAU. For details, see 3.1.4 Logging In to the SAU.
Procedure
Step 1 Run the following command to check the OS version:
# cat /etc/DL-Release
Information similar to the following is displayed, where VXXXRXXXCXX is the OS version. The
information next to the version is the suffix ID of an OS. For example, 2013020218321359847962 or
Jasper-OMU-V100R001C02.
VXXXRXXXCXXSPCXXX.2013020218321359847962
Or
VXXXRXXXCXX.Jasper-OMU-V100R001C02
Or
DopraLinuxVXXXRXXXCXX.1
You only need to check that the OS version is correct and do not need to focus on the suffix
ID. Different SAU boards support different OS versions:
SAUc: Dopra Linux V200R003C02 or later
ESAUa: RTOS V100R001C00 or later
RTOS is an upgraded Dopra Linux system.
----End
Prerequisites
You have logged in to the SAU (for details, see 3.1.4 Logging In to the SAU).
Context
Improperly changing the IP address of the Ethernet adapter team leads to network failure.
Therefore, you must follow the instructions.
Procedure
Change the external fixed IP address when the SAU applications are operating normally.
1. Change the external fixed IP address by referring to 3.1.7.2 Changing the IP Address of
the SAU (for the EBC or EMS Service Component), and then record the new IP address
in 7.1 Data Sheet of SAU Software Installation Information.
Replace the SAU board, and reconfigure the IP addresses of the internal and external
Ethernet adapter teams.
1. Replace the SAU board by referring to 3.3 Replace an SAU Board.
Replace the SAU board, and reconfigure the IP addresses of the internal and external Ethernet adapter
teams, to avoid the conflicts between the IP addresses of the internal and external Ethernet adapter
teams.
2. Configure the external Ethernet adapter team and its IP address by referring to 3.1.7.2
Changing the IP Address of the SAU (for the EBC or EMS Service Component), and
then record the IP address in 7.1 Data Sheet of SAU Software Installation Information.
----End
3.4.3 Changing the SAU Name (for the EBC or EMS Service
Component)
This section describes how to change the name of the SAU board on the Linux operating
system.
Prerequisites
You have logged in to the SAU (for details, see 3.1.4 Logging In to the SAU).
Context
The SAU name have been planned. You need to change the SAU name and IP addresses
through the omutool after you have installed the SAU applications. For details about how to
change the IP addresses, see 3.4.2 Changing the IP Address of the SAU Ethernet Adapter
Team (for the EBC or EMS Service Component).
Procedure
Step 1 Stop SAU processes.
If both EBC and EMS service components are deployed on the SAU board, their processes must be
stopped.
Step 2 Switch the current directory to the directory where the omutool is saved.
Assume that the active workspace of the SAU is in /mbsc/bam/version_a. Run the following
command, and then press Enter:
# cd /mbsc/bam/version_a/bin/bam
You can query the active workspace of the SAU by one of the following methods:
Step 3 Run the following command to change the name of the SAU, and then press Enter.
# ./omutool hostname SAU name
For example, to change the SAU name to sau_123, run the ./omutool hostname sau_123
command.
Step 4 Start the SAU processes to make the parameters take effect.
If you have logged in to the SAU (for example, by using PuTTY), you need to log in to the SAU again
using PuTTY so that the host name in the login window changes to the new one.
----End
Prerequisites
You have logged in to the SAU. For details, see 3.1.4 Logging In to the SAU.
Context
The SAU routing and forwarding function is enabled by default. You can disable this function to
improve SAU security.
The SAU routing and forwarding function cannot be disabled if the related scenarios are required
onsite.
This section applies only to the Dopra Linux V2 operating system.
Procedure
Step 1 Run the following command to switch from the current directory to the directory that stores
the ip_forward.sh script.
Assume that the active workspace of the SAU is installed in the /mbsc/bam/version_a
directory. Run the following command:
# cd /mbsc/bam/version_a/bin/bam
Step 2 Run the following command to set the execute permission on the ip_forward.sh script:
# chmod +x ip_forward.sh
----End
Prerequisites
The operating system of the peer end for the SAU is Linux or Unix.
You have logged in to the SAU. For details, see 3.1.4 Logging In to the SAU.
Context
This function can be enabled on multiple SAU boards, and the access information can be
reported to the peer ends simultaneously.
Procedure
Step 1 Run the following command to switch from the current directory to the directory that stores
the syslog_config.sh script:
Assume that the active workspace of the SAU is installed in the /mbsc/bam/version_a
directory. Run the following command:
# cd /mbsc/bam/version_a/bin/bam
Step 2 Run the following command to set the execute permission on the syslog_config.sh script:
# chmod +x syslog_config.sh
----End
Prerequisites
The SAU works with BSC6900 V900R016C00, BSC6910 V100R016C00, or a later version.
Context
When the SAU works with a version earlier than BSC6900 V900R016C00 or BSC6910
V100R016C00, set SSL configuration parameters of the SAU by referring to 4.2.12 How Do I
Set SSL Configuration Parameters on the SAU by Running Commands on the Server?.
Procedure
Step 1 Install and activate digital certificates, and set SSL configuration parameters of the OMU. For
detailed operations, see Setting the Connection Mode Between the U2000/M2000 and the
BSC6900 to SSL or Setting the Connection Mode Between the U2000/M2000 and the
BSC6910 to SSL in the commissioning guide of the NE working with the SAU.
The security policies on the OMU are automatically synchronized to the SAU on a scheduled
basis. After the synchronization, the SSL configuration parameter settings on the OMU are
automatically synchronized to the SAU.
Step 2 Set SSL parameters of the upper-layer applications for the SAU.
For detailed operations, see the sections of setting SSL connections in the product
documentation of the U2000/M2000 (EBC and Trace Server).
----End
Prerequisites
The version of NEs that work with the SAU is BSC6910 V100R016, BSC6900
V900R016, or later.
This function does not support Dopra Linux V100R001C03.
You are not allowed to add a user-defined user omuser that does not belong to the non-
root user group to the Linux operating system.
You have logged in to the SAU. For details, see Logging In to the SAU.
Context
After this function is enabled, the operating system user omuser will be automatically
added. User omuser, which belongs to the root user group, can be used to run SAU
processes but not to log in to the SAU. This user has no password and does not support
password setting.
After the function is enabled, the omud, monitor, sau_manager, and sntp processes can
only be executed by user root. Other processes can be executed by user omuser.
If non-root users run SAU processes, they do not have file operation rights that are only
granted to user root, thereby improving system security.
In upgrade scenarios, this function remains the status before the upgrade. By default, this
function is disabled for new networks.
Procedure
Step 1 Stop SAU processes.
If both EBC and EMS service components are deployed on the SAU board, their processes must be
stopped.
You can query the active workspace of the SAU by using one of the following methods:
Enable the function of running Run the following command and press Enter:
SAU processes as a non-root # ./omutool privilege_restrict on
user
When the following information is displayed, the
command is successfully executed:
Successfully set the privilege restrict flag on!
Disable the function of running Run the following command and press Enter:
SAU processes as a non-root # ./omutool privilege_restrict off
user
When the following information is displayed, the
command is successfully executed:
Successfully set the privilege restrict flag off!
Query the status of the Run the following command and press Enter:
function of running SAU # ./omutool privilege_restrict
processes as a non-root user
Information similar to the following is displayed,
showing the status query result:
Current privilege restrict flag is OFF.
----End
Prerequisites
You have logged in to the LMT.
Procedure
Check the information about the SAU.
Run the DSP SAU command to query the operating status of the SAU, IP address
configuration information, and version information.
Check the operating status of the SAU.
Run the DSP SAUSRV command to query the CPU usage, memory usage, total capacity of
every logical disk, available space, and percentage of the available space of the SAU board.
Check the work area information of the SAU.
Run the DSP SAUAREA command to query the versions of the SAU software installed on
the active and standby work areas of the SAU.
Check status of processes on the SAU.
Run the DSP SAUMODULE command to query the status and startup type of each SAU
process.
----End
Prerequisites
You have logged in to the LMT.
Context
When you add data to an SAU board, you need to reset the SAU board.
If you reset an SAU board by performing a hard reset, the operating system on the SAU
board will be restarted. Faults caused by the SAU operating system and applications will
be rectified after the reset is successful.
If you reset an SAU board by performing a soft reset, the management processes on the
SAU board will be interrupted. Faults caused by the SAU applications will be rectified
after the reset is successful.
Procedure
Run the RST SAU command to reset the SAU board specified by the subrack number
and slot number and SAU applications.
− If Reset Type is set to SOFT (soft reset), only the SAU applications are restarted.
This type is recommended.
− If Reset Type is set to HARD (hard reset), only the SAU operating system is
restarted.
----End
3.4.9.1 Checking the Status of SAU Processes (for the EBC Service
Component)
This section describes how to check the status of SAU processes, including the SAU service
processing processes and board management processes.
Prerequisites
You have logged in to the SAU (for details, see 3.1.4 Logging In to the SAU).
Procedure
Step 1 Run the following commands to check the SAU service processing processes:
# cd /opt/ebcsau
# . ./svc_profile.sh
# sau4ebc_ps
The last line of the command output is as follows:
[All Services: xx ] [Running: yy] [Not Running: zz ]
# /etc/rc.d/saud status
The board management processes runs in either of the following states:
running state, indicating that the board management processes are running
unused state, indicating that the board management processes are not running
----End
Prerequisites
You have logged in to the SAU (for details, see 3.1.4 Logging In to the SAU).
The SAU applications are already installed.
Procedure
Step 1 Run the following commands to start the SAU processes, including the SAU service
processing processes and board management processes:
# cd /opt/ebcsau
# . ./svc_profile.sh
# sau4ebc_start
Step 2 Check whether all the SAU processes are started by referring to 3.4.9.1 Checking the Status
of SAU Processes (for the EBC Service Component).
----End
Prerequisites
You have logged in to the SAU (for details, see 3.1.4 Logging In to the SAU).
The SAU applications are already installed.
Context
Stop SAU processes with caution because when the SAU processes are stopped, services
provided for the EBC are interrupted.
When both EBC and EMS service components are deployed on the SAU board, the board
management processes is shared by the two service components. So if the board management
processes is stopped, the two service components can not wok properly.
Procedure
Step 1 Run the following command to stop the SAU service processing processes:
# cd /opt/ebcsau
# . ./svc_profile.sh
# sau4ebc_stop
Step 3 Check whether all the SAU processes are stopped by referring to 3.4.9.1 Checking the Status
of SAU Processes (for the EBC Service Component).
----End
3.4.10.1 Checking the Status of SAU Processes (for the EMS Service
Component)
This section describes how to check the status of SAU processes, including the SAU service
processing processes and board management processes.
Prerequisites
You have logged in to the SAU (for details, see 3.1.4 Logging In to the SAU).
Procedure
Step 1 Run the following commands to check the SAU service processing processes:
# cd /opt/emssau
# . ./svc_profile.sh
# sau4ems_ps
The last line of the command output is as follows:
[All Services: xx ] [Running: yy] [Not Running: zz ]
----End
Prerequisites
You have logged in to the SAU (for details, see 3.1.4 Logging In to the SAU).
The SAU applications are already installed.
Procedure
Step 1 Run the following commands to start the SAU processes, including the SAU service
processing processes and board management processes:
# cd /opt/emssau
# . ./svc_profile.sh
# sau4ems_start
Step 2 Check whether all the SAU processes are started by referring to 3.4.10.1 Checking the Status
of SAU Processes (for the EMS Service Component).
----End
Prerequisites
You have logged in to the SAU (for details, see 3.1.4 Logging In to the SAU).
The SAU applications are already installed.
Context
Stop SAU processes with caution because when the SAU processes are stopped, services
provided for the EMS are interrupted.
When both EBC and EMS service components are deployed on the SAU board, the board
management processes is shared by the two service components. So if the board management
processes is stopped, the two service components can not wok properly.
Procedure
Step 1 Run the following command to stop the SAU service processing processes:
# cd /opt/emssau
# . ./svc_profile.sh
# sau4ems_stop
Step 3 Check whether all the SAU processes are stopped by referring to 3.4.10.1 Checking the Status
of SAU Processes (for the EMS Service Component).
----End
Context
For details about SAU users, see 7.3 User Names and Initial User Passwords.
Prerequisites
The SAU board functions normally.
You have logged in to the SAU. For details, see 3.1.4 Logging In to the SAU.
You have prepared the new password of user root.
Context
It is recommended that you change the password at your first login and change the
password every three months.
The password contains digits 0 to 9, lowercase letters a to z, uppercase letters A to Z, and
special characters. To improve password security, you are advised to use the following
password policies:
− At least one upper-case letter
− At least one lower-case letter
− At least one digit
− At least one special character `~!@#$%^&*()-_=+\|[{}];:'",<.>/? and space
− The user password must have a minimum length of 8 characters and maximum length
of 32 characters.
Procedure
Step 1 Run the following command to change the password of user root:
# passwd root
Step 2 Enter the new password according to the system prompt, and then press Enter.
Step 3 Enter the new password again according to the system prompt, and then press Enter.
If the system does not display any information, the password of user root has been changed.
Otherwise, contact Huawei technical support.
Step 4 Record the new password to 7.1 Data Sheet of SAU Software Installation Information.
----End
Prerequisites
The SAU board functions normally.
You have prepared the new password.
Context
It is recommended that you change the password at your first login and change the
password every three months.
The password contains digits 0 to 9, lowercase letters a to z, uppercase letters A to Z, and
special characters. To improve password security, you are advised to use the following
password policies:
Procedure
Step 1 Log in to the SAU. For details, see 3.1.4 Logging In to the SAU.
Step 2 Run the following command as user root to change the password of user lgnusr:
# passwd lgnusr
Step 3 According to the system prompt, enter the new password, and then enter the new password
again.
If the system does not display any information, the password has been changed. Otherwise,
contact Huawei technical support.
----End
Prerequisites
You have installed the SAU applications.
You have logged in to the SAU. For details, see 3.1.4 Logging In to the SAU.
You have prepared the new password of mysql database user.
Context
The password contains digits 0 to 9, lowercase letters a to z, uppercase letters A to Z, and
special characters. To improve password security, you are advised to use the following
password policies:
The password can contain 8 to 32 characters.
At least one digit.
At least one lowercase letter.
At least one uppercase letter.
At least one special character `~!@#$%^&*()-_=+\|[{}];:'",<.>/? and space
Procedure
Step 1 Stop SAU processes.
If both EBC and EMS service components are deployed on the SAU board, their processes must be
stopped.
You can query the active workspace of the SAU by one of the following methods:
EBC # cd /opt/ebcsau
# . ./svc_profile.sh
# sau4ebc_start
EMS # cd /opt/emssau
# . ./svc_profile.sh
# sau4ems_start
----End
Prerequisites
You have logged in to the SAU (for details, see 3.1.4 Logging In to the SAU).
You have logged in to the LMT.
Context
The files that can be deleted on the SAU are as follows:
EBC service component:
− Files under /opt/ebcsau/etc/cbb_running_dir/subject/output/log generated one
week ago or earlier
− All the files under /opt/ebcsau/var/logs/backup
EMS service component:
− Files under /opt/emssau/etc/cbb_running_dir/subject/output/log generated one
week ago or earlier
− All the files under /opt/emssau/var/logs/backup
Procedure
Step 1 Check the available space on the SAU disk.
The available space is less than 20% You must clean up the disk.
You can check the available space on the SAU disk by one of the following methods:
Run the command in the SAU:
# df -k
In normal cases, the hard disk usage is lower than 80%, and the value of Use% is smaller than 80%.
Log in to the LMT, run the MML command DSP SAUSRV to check the available space on the SAU
disk.
Step 2 Run the rm command to delete the files that are not required.
Before cleaning up the disk, you need to ensure that the files to be deleted are not required for
future operations. Deleting useful files by mistake may lead to improper system running.
----End
Prerequisites
The firewall on the PC is disabled.
The user password for FTP is obtained (for details, see 7.1 Data Sheet of SAU Software
Installation Information).
The SAU applications are running normally.
Context
In normal cases, the flies that are required to be backed up on the SAU are as follows:
This task takes how to download the /opt/ransau/data/common/datasource folder from the SAU to
local disk D as an example.
Procedure
Step 1 Use FileZilla to download the /opt/ransau/data/common/datasource folder from the SAU to
local disk D.
For details about how to use FileZilla, see 4.2.1 How Do I Use FileZilla to Transfer Files?.
The configuration information required for uploading the files is as follows:
User and password: user root or lgnusr and its password
After operating system (OS) hardening is performed, you cannot use FileZilla to connect
to the SAU board using SFTP as user root. To connect to the SAU board using SFTP,
you must use a user name other than root, for example, lgnusr.
Folder to be downloaded: all the files under /opt/ransau/data/common/datasource
Directory to save the files on the PC: D:\
----End
Prerequisites
The target slots for the SAU are idle and can hold the SAU. Such slots refer to Slot Planning.
Procedure
Step 1 Log in to the SAU (for details, see Logging In To the SAU).
Step 2 Run the LST SAUCENTER command to check whether the SAU board servers as the
central FTP server.
If yes, go to Step 12 after the board adjustment. If no, you do not need to perform other
operations after the board adjustment.
Step 3 Run the /etc/rc.d/saud stop command to stop the board management processes.
Step 4 Run the poweroff command to shut down the SAU.
Step 5 When the OFFLINE LED on the SAU board panel is on, pull the SAU and insert it into the
target slots.
Step 6 Wait about 5 minutes, and then log in to the LMT to run the LST BRD command to query the
subrack number and slot numbers of the SAU before the switchover.
Step 7 Run the RMV BRD command to remove the original SAU.
Step 8 Run the ADD BRD command to add a new SAU. In this step, set slot numbers of the SAU to
the target SAU slot numbers.
For example, if the target slots of the SAU are 20 and 21, run the following command:
ADD BRD: SRN=0, BRDCLASS=SAU, BRDTYPE=SAUc, SN=21;
Step 9 Log in to the LMT and check whether the SAU is properly displayed on the device panel and
whether it is in normal state, and then run the DSP SAU command to check whether the SAU
operate properly.
Step 10 In the LMT main window, click Alarm and select Browse Alarm to check the active alarms
on NEs.
Step 11 Optional: If there is an alarm related to the original SAU in the list of active alarms, select
the alarm, right-click it, and choose Clear Alarm from the shortcut menu to manually clear
the alarm.
Step 12 If you have detected that the SAU board servers as the central FTP server before the board
adjustment in Step 2, run the SET SAUCENTER command to specify the SAU board as the
central FTP server.
----End
4 FAQs
Prerequisites
The ESAUa board is installed with two hard disks.
The source disk and target disk are defined as follows: The source disk is the disk whose
data is to be backed up. The target disk is the disk that stores the backup data.
Context
Figure 4-1 shows positions of the hard disks on the ESAUa board.
Procedure
Run the following steps to set hard disks to the RAID 1 Mode on the ESAUa board.
1. Insert the ESAUa board into the corresponding slot and power it on. The board starts
automatically.
2. When the system displays Press Ctrl-C to start LSI Logic
Configuration Utility..., press Ctrl+C. The LSI BIOS interface is displayed,
as shown in Figure 4-2.
3. Select Eval Board, and then press Enter. The adapter property interface is displayed, as
shown in Figure 4-3.
4. Select RAID Properties, and then press Enter. The interface for selecting an array type
is displayed.
− If the interface shown in Figure 4-4 is displayed, it indicates that the two hard disks
on the ESAUa board are set to the RAID 1 mode.
Figure 1.3 Selecting an array type (The hard disks are set to the RAID 1 mode.)
− If the interface shown in Figure 4-5 is displayed, it indicates that the two hard disks
on the ESAUa board are not set to the RAID 1 mode. Then, process with Step 5.
Figure 1.4 Selecting an array type (The hard disks are not set to the RAID 1 mode.)
5. Select Create RAID 1 Volume, and then press Enter. The interface for selecting the
source disk and target disk is displayed, as shown in Figure 4-6.
Figure 1.5 Selecting the source disk and target disk (1)
6. Set a disk at the source disk, and then press SPACEBAR. The following information is
displayed:
M - Keep existing data, migrate to an IM array.
Synchronization of disk will occur.
D - Overwrite existing data, create a new IM array
ALL DATA on ALL disks in the array will be DELETED!!
NO Synchronization performed.
7. Press M to define the source disk. The interface shown in Figure 4-7 is displayed. At this
time, RAID Disk of the source disk is Yes and Drive Status of the source disk is
Primary.
Figure 1.6 Selecting the source disk and target disk (2)
8. Select another hard disk, and then press SPACEBAR. The warning interface shown in
Figure 4-8 is displayed.
9. Press C. The interface for selecting the source disk and target disk is displayed, as shown
in Figure 4-9.
Figure 1.8 Selecting the source disk and target disk (3)
10. Press C. The interface for saving the configuration is displayed, as shown in Figure 4-10.
11. Select Save changes then exit this menu, and then press Enter. The hard disks are set
to the RAID 1mode and data synchronization automatically starts. The value of Status
indicates the synchronization progress, as shown in Figure 4-11.
It takes no less than 15 minutes to finish the data synchronization of the RAID 1. If the
ESAUa board is restarted during the synchronization, the synchronization restarts.
12. When the data synchronization of the RAID 1 is complete, press Esc, and then select
Exit the Configuration Utility and Reboot, as shown in Figure 4-12. Then, press
Enter. The ESAUa board is restarted.
Figure 1.11 Saving the configuration and exiting the configuration interface
----End
Question
How to query the hardware mapping relations of the network adapter on the SAU board?
Answer
The installation of the SAU applications is the perquisite for querying the network
configuration of the Ethernet adapters.
Step 1 Log in to the SAU.
Step 2 Query the configuration information about the Ethernet adapters before delivery.
If you want to query the configuration information about the Ethernet adapters on the
SAUc board, enter the /root/eth_alias_names.sh command, and then press Enter.
The following information is displayed:
eth0 02,0,0 F_ETH0
eth1 01,0,0 F_ETH1
eth2 07,0,0 F_DBG
eth3 05,0,0 B_UPDATE0
eth4 06,0,0 B_UPDATE1
eth5 03,0,0 B_ETH0
eth6 03,0,1 B_ETH1
If you want to query the configuration information about the Ethernet adapters on the
ESAUa board, enter the /root/eth_alias_names.sh command, and then press Enter.
The following information is displayed:
eth0 05,0,0 F_ETH0
eth1 05,0,1 F_ETH1
eth2 06,0,0 F_DBG
eth3 06,0,1 B_UPDATE
eth4 01,0,0 B_ETH0
eth5 01,0,1 B_ETH1
The three columns of the configuration of SAU Ethernet adapters are detailed as follows:
The first column lists the logical names of the Ethernet adapters for software identification.
The second column lists the Peripheral Component Identity (PCI) of Ethernet adapters for hardware
identification.
The third column lists the names of Ethernet adapters for users to identify the Ehternet adapters.
The mapping between the second and third columns cannot be changed. The mapping between the first
and second columns, and the mapping between the first and third columns depend on the configuration
scenarios.
----End
Question
How Can I query the network configuration of the Ethernet adapters on the SAU board?
Answer
The installation of the SAU applications is the perquisite for querying the network
configuration of the Ethernet adapters.
Step 1 Log in to the SAU.
Step 2 Run the following command to query the external fixed IP address, broadcast IP address, and
subnet mask, and then press Enter.
# ifconfig bond1
The following information is displayed:
Run the following commands to query other IP addresses and subnet masks.
Run the ifconfig bond1 command to query the fixed external IP address, broadcast IP address, and
subnet mask.
Run the ifconfig vlan1 command to query the fixed internal IP address, broadcast IP address, and
subnet mask.
Run the ifconfig bond2 command to query the debugging IP address, broadcast IP address, and
subnet mask.
----End
Prerequisites
The local keyboard and monitor are configured and connected to the SAU board.
The USB disk is inserted into the USB port of the SAU board.
Procedure
Step 1 Press the RESET or PWRBTN button on the SAU board panel to reset the SAU board. The
BIOS Setup dialog box is displayed.
Step 4 Use arrow keys to select Boot Device Priority, and then press Enter.
Step 5 Use arrow keys to select 1st Boot Device, and then press Enter.
Step 6 In the displayed dialog box, set the first boot device of the SAU to USB, and then press
Enter.
The previous interface returns. If the value of 1st Boot Device is [USB:******], it indicates
that the configuration is complete.
Step 7 After the setting is complete, press F10 to save the settings and exit.
----End
Context
When the NE version is BSC6900 V900R017C00SPC500/BSC6910
V100R017C00SPC500 or later and the SAU version is V100R001C00SPC330 or later, if
the internal network segment of the OMU changes, you do not need to perform any
operations on the SAU. In this scenario, if the system detects that the internal network
communication between the SAU and OMU is disconnected after the SAU software is
started, the internal network segment of the SAU is automatically synchronized to that of
the OMU.
When the NE version is earlier than BSC6900 V900R017C00SPC500/BSC6910
V100R017C00SPC500 or SAU version is earlier than V100R001C00SPC330, change
the internal network segment of the SAU by following the instructions provided in this
section.
All IP addresses in the internal network are centrally planned, and therefore you are not
allowed to change the internal fixed IP address of the SAU. If you change the internal
fixed IP address of the SAU forcibly, the IP address of the SAU will conflict with that of
the OMU, and consequently the communication between the SAU and the OMU fails.
Procedure
Step 1 Log in to the SAU. For detailed operations, see 3.1.4 Logging In to the SAU.
Step 2 Stop SAU processes.
If both EBC and EMS service components are deployed on the SAU board, their processes must be
stopped.
Step 3 Start the omutool. For detailed operations, see 4.2.3 How Can I Start the omutool.
Step 4 Run the following command to change the network segment of the SAU's internal IP address:
# ./omutool innersubnet internal network segment
For example, when the internal IP address of OMU is changed from 10.168.3.40 to
172.16.3.40, you need to run the following command to change the network segment of the
SAU's internal IP address:
# ./omutool innersubnet 172.16
The internal network segment of SAU must be same as that of the OMU.
You can change only the network segment of the SAU's internal IP address and cannot change other
parts of the IP address.
Step 5 Run the following commands to start the SAU processes for the modifications to take effect.
EBC # cd /opt/ebcsau
# . ./svc_profile.sh
# sau4ebc_start
EMS # cd /opt/emssau
# . ./svc_profile.sh
# sau4ems_start
----End
4.1.6 How Can I Set the Link Mode of the External Ethernet
Adapter of the SAU
This section describes how to set the link mode of the external Ethernet adapter on the SAU
board so that it is consistent with that of the LAN switch.
Prerequisites
You have obtained the link mode of the LAN switch. You can contact the operator for the
specific mode of the link.
You have logged in to the SAU (for details, see 3.1.4 Logging In to the SAU).
Context
If the link mode of the external Ethernet adapter on the SAU board panel is inconsistent with
that of the LAN switch, the network may be interrupted. If the link mode of the LAN switch
is specified, the link mode of the external Ethernet adapter on the SAU board panel should
also be specified.
There are two link modes of the LAN switch: force full-duplex mode and auto-negotiation
mode.
In this section, the following case is taken as an example.
For the SAUc and ESAUa boards, Ethernet adapters F_ETH0 and F_ETH1 correspond
to the external Ethernet adapters eth0 and eth1 identified by the operating system.
The force link mode is force full-duplex with a rate of 10 Mbit/s.
This section uses the SAUc and ESAUa boards as an example.
Procedure
Step 1 Run the following command to query the names of the external Ethernet adapters that are
identified by the operating system and correspond to F_ETH0 and F_ETH1:
Commands for querying the names of the external Ethernet adapters are as follows according
to the SAU board type:
Command for the SAUc and ESAUa boards:
# /root/eth_alias_names.sh
For details about the query result, see 4.1.2 How Can I Query the Hardware Mapping Relations of
Network Adapters.
Step 2 Run the following command to query the link mode of F_ETH0:
# ethtool eth0
Step 3 Check whether the fields Speed, Duplex, and Auto-negotiation are consistent with the link
mode parameters for the LAN switch.
Option Description
Step 4 Set the link mode of the SAU external Ethernet adapter according to the link mode of the
LAN switch.
1. Run the following command and press Enter to switch the current directory to the
directory where the speedduplex.sh file is saved:
# cd /mbsc/bam/version_a/bin/bam
Option Description
If the link mode of the Run the ./speedduplex.sh F_ETH0 10 full off command.
LAN switch is force full-
duplex mode
If the link mode of the Run the ./speedduplex.sh F_ETH0 10 full on command.
LAN switch is auto-
negotiation mode
If the link mode of the LAN switch is not anto-negotiation mode, the link mode of both the
LAN switch and the SAU external Ethernet adapter must be set to full duplex mode.
The command for setting the link mode of the SAU external Ethernet adapter is saved to
etc/rc.d/rc.local after it is executed.
Step 5 Repeat Step 2 and Step 4 to set the link mode of Ethernet adapter eth1. The setting is
complete.
The link mode of Ethernet adapter eth0 must be the same as the link mode of Ethernet adapter eth1.
----End
Prerequisites
You have obtained the IP address of the SAU board.
Communication is proper between the PC and the SAU board.
You have obtained the file to be uploaded to the SAU board and have saved the file to
the PC.
You have contacted Huawei technical support to obtain FileZilla.zip at
http://support.huawei.com and decompress it to the PC.
You have obtained the user password of the SAU board.
Procedure
Step 1 Double-click filezilla.exe to start the tool.
Step 3 In the lower left area of the Site Manager dialog box, click New Site.
Step 4 On the General tab page, set site parameters according to Table 4-1.
You can ignore the dialog box displayed during the connection. Click OK in the dialog box.
After the connection is successful, the Remote Site area displays directory information on the SAU
board.
Step 6 In the Remote site area, set the destination directory on the SAU board. For example,
/mbsc/upgrade.
After you set the directory, the Remote site area displays all files stored in this directory.
If you need to upload files as a user other than user root (for example, user lgnusr) to a target
directory to which you are not authorized to upload files (for example, the target directory is
/mbsc/upgrade), you can upload the files to the home directory of the user (for example,
/home/lgnusr), and then log in to the SAU and run the mv command as user root to move the files
to the target directory.
If you need to download files as a user other than user root (for example, user lgnusr) from a target
directory from which you are not authorized to download files (for example, the target directory is
/mbsc/upgrade), you can log in to the SAU and run the mv command as user root to move the files
to the home directory of the user (for example, the /home/lgnusr directory), and then download the
files from the home directory as user lgnusr.
Step 7 In the Local site area, set the source directory on the PC. For example, D:\.
After you set the directory, the Local site area displays all files stored in this directory.
Step 8 Perform the following operations as required.
Purpose Operation
Upload files In the Local site area, right-click the file to be uploaded and choose
Upload from the shortcut menu.
Download In the Remote site area, right-click the file to be downloaded and choose
files Download from the shortcut menu.
If the upload or download fails, click the Failed transfers tab in the lower left area of the FileZilla
window. Then right-click the file that fails to be transferred and choose Reset and requeue selected
files from the shortcut menu to resume the file transfer.
----End
Prerequisites
The PC is connected to the Internet.
The SAU board is installed with the operating system.
You have obtained the PuTTY software. For details, see 3.1.2 Preparing for the
Installation.
Context
PuTTY can be used for remotely logging in to the Dopra Linux operating system.
Procedure
Step 1 Double-click PuTTY.exe. The PuTTY Configuration dialog box is displayed, as shown in
Figure 4-14.
Step 2 Enter the IP address of the SAU board in the Host Name(or IP address) box of the Specify
the destination you want to connect to area. Then, set Connection type to SSH.
The PC is connected to ETH0 or ETH1 on the The IP address is the external fixed
SAU board through a network device IP address of the SAU board.
Step 4 Log in to the SAU board as the root user or lgnusr user.
----End
Prerequisites
You have logged in to the SAU server (for details, see 3.1.4 Logging In to the SAU).
The SAU applications are installed.
Context
You can perform related tasks by running the commands attached with parameters through the
omutool.
Procedure
Step 1 Run the following command as user root to switch the current directory to the directory
where the omutool is saved.
Assume that the active workspace of the SAU is in /mbsc/bam/version_a. Run the following
command, and then press Enter:
# cd /mbsc/bam/version_a/bin/bam
You can query the active workspace of the SAU by using one of the following methods:
Run the following command on the SAU: cat /mbsc/bam/common/reg.ini|grep bamarea|sed -e
"s/bamarea//"|sed -e "s/=//".
Log in to the LMT, and run the MML command DSP SAUAREA to query the active workspace of
the SAU.
Step 2 Run the following command to start the omutool and display parameter information about the
omutool:
# ./omutool
----End
Prerequisites
You have logged in to the Windows operating system as a user of the Administrators
user group.
The connection between the PC and the debugging port of the SAU is proper.
Context
This section uses the classic view of the Windows 7 operating system as an example.
Procedure
Step 1 Choose Start > Control Panel.
Step 2 In the Control Panel window, click Network and Sharing Center.
Step 3 Click the connection to the SAU, and then choose Properties.
Step 4 In the displayed Local Area Connection Properties dialog box, select the Internet Protocol
Version 4 (TCP/IPv4) check box, and click Properties.
Step 5 In the displayed Internet Protocol Version 4 (TCP/IPv4) Properties dialog box, set the IP
address for the PC.
Set the IP address, which must be on the same network segment as the debugging IP
address of the SAU.
Set the subnet mask, which must be the same as that of the debugging port of the SAU.
Set the default gateway, which must be the same as that of the debugging port of the
SAU.
Step 6 Click OK.
----End
Prerequisites
You have logged in to the SAU server. For detailed operations, see 3.1.4 Logging In to
the SAU.
You have installed SAU applications.
Context
Uninstalling SAU applications consists of uninstalling the service components installed
on the SAU and uninstalling the BAM platform.
If the EBC and EMS service components are installed on the SAU board and only the
EBC service component is uninstalled but the BAM platform is not installed, the EMS
service component can run properly.
Procedure
Step 1 Stop SAU processes.
If both the EBC and EMS service components have been deployed on the SAU board and you only need
to uninstall one of them, you only need to stop the process of the service component you want to
uninstall.
Step 3 Uninstall the board management software, which is the BAM program.
If both the EBC and EMS service components are deployed on the SAU board and you only need to
uninstall one of them, do not uninstall the board management software. If you uninstall the board
management software, another service component will fail to work properly.
1. Run the uninstall_bam script and press Enter:
# cd /opt
# uninstall_bam
2. Type Y (case insensitive) to uninstall BAM programs.
3. Run the following command to check whether the BAM programs have been uninstalled
successfully:
# ls /mbsc/ | grep "bam"
If no command output is displayed, the BAM programs have been uninstalled
successfully.
If "bam" is displayed, not all the BAM programs have been uninstalled completely.
Repeat Step 3.1 and Step 3.2 to uninstall the BAM programs from another workspace.
----End
4.2.6 How Can I Install the Integrity Check Tool for Installation
Packages
This section describes how to install the integrity check tool for installation packages.
Prerequisites
You have obtained the installation package of the integrity check tool
ipsi_signcli_suse10_X86_32_pkg_2_0.tar.
Procedure
Step 1 Log in to the SAU (for details, see 3.1.4 Logging In to the SAU).
Step 2 Upload the installation package of the integrity check tool to the SAU by using Filezilla tool.
For details about how to use the Filezilla tool, see 4.2.1 How Do I Use FileZilla to Transfer
Files?.
If... Then...
You can directly log in to the SAU board as OS hardening has not performed on the
user root SAU board.
The configuration information required for
uploading the files is as follows:
User and password: root and its password
Folder to be uploaded:
ipsi_signcli_suse10_X86_32_pkg_2_0.t
ar
Directory of files on the SAU board:
/mbsc/upgrade
You can only log in to the SAU board as a OS hardening generally has been performed
user other than user root, such as user on the SAU board.
lgnusr, and then run the su - root command You need to set the following information
to switch to user root when uploading files and continue to
perform Step 3 after the upload is complete.
User and password: lgnusr and its
password
Folder to be uploaded:
ipsi_signcli_suse10_X86_32_pkg_2_0.t
ar
Directory of files on the SAU board:
/home/lgnusr
Step 3 If you upload files to the /home/lgnusr directory as user lgnusr, run the following commands
as user root to move the installation package of the integrity check tool
ipsi_signcli_suse10_X86_32_pkg_2_0.tar to the /mbsc/upgrade directory:
# cd /home/lgnusr/
# mv ipsi_signcli_suse10_X86_32_pkg_2_0.tar /mbsc/upgrade/
Step 4 Perform the following operations to decompress the installation package.
1. Run the following commands to decompress the installation package:
# cd /mbsc/upgrade
# tar xvf ipsi_signcli_suse10_X86_32_pkg_2_0.tar
2. Run the following commands to install the integrity check tool:
# cd IPSISignCliPkg
# ./install.sh
When the system displays the following information, the integrity check tool has been
installed on the SAU.
/opt/signtool dose exsits,please check!
When the system displays the following information, the integrity check tool is
successfully installed.
IPSI tool software installed successfully.
----End
Procedure
Step 1 3.1.4 Logging In to the SAU.
Step 2 Stop SAU processes.
If both the EBC and EMS service components have been deployed on the SAU board, you only need to
stop the process of the service component you want to set or modify.
# . ./svc_profile.sh
# sau4ems_stop
If the command output contains All processes have been
stopped successfully!, it indicates that all service processes
are stopped. Otherwise, run the sau4ems_kill command to forcibly
stop the service processes.
If... Then...
Step 4 Run the following command to navigate to the config_non_ssl_port.sh script path.
If... Then...
Step 6 Open and close the non-encrypted Json port for the SAU.
You can type A to check the status of the non-encrypted Json ports.
If the system displays Non-SSL
port .......................................................
Disabled, the non-encrypted Json ports have been closed.
If the system displays Non-SSL
port
.......................................................Enabled, the
non-encrypted Json ports have been opened.
If... Then...
----End
Prerequisites
You have logged in to the SAU (for details, see 3.1.4 Logging In to the SAU).
You have obtained the newly digital certificates.
Context
For details about the default digital certificates of SAUs, see Table 4-2.
Procedure
Step 1 Use the FileZilla to upload the obtained CA certificate, device certificate, and CRL certificate
to the save path shown in Table 4-2. For details, see 4.2.1 How Do I Use FileZilla to Transfer
Files?.
Step 2 Stop SAU processes.
If both the EBC and EMS service components have been deployed on the SAU board, you only need to
stop the process of the service component you want to set or modify.
Step 3 Run the following command to modify the cerConfig.xml configuration file.
Update the digital certificate of the EBC service Run the following command:
component # cd
/opt/ebcsau/etc/Certificate
Update the digital certificate of the EMS service Run the following command:
component # cd
/opt/emssau/etc/Certificate
# vi cerConfig.xml
Type i to enter the insert mode. Configure the following parameters as required:
Configure transmission mode-related parameters
The parameters formats of transmission mode are similar as follows:
<AREADESC areaname="option">
<PARAS>
<PARA name="enableSSL" value="true" />
<PARA name="version" value="1" />
<PARA name="enableAuthType" value="2" />
<PARA name="alarmPeriod" value="30" />
<PARA name="clientID" value="0" />
<PARA name="privatekeyDH" value="OMU"/>
<PARA name="crlpolicy" value="0"/>
</PARAS>
</AREADESC>
Multiple CA certificates can be installed on an SAU. Configure relevant parameters for each CA
certificate by referring to Table 4-4.
You are advised to delete the CA certificates and parameter configurations that are not used.
Configure device configuration-related parameters
The parameter formats of device certificate are similar as follows:
<AREADESC areaname="dev">
<PARAS>
<PARA name="file" value="usercert.pem" />
file This parameter determines the Set to the device certificate name.
device certificate file name.
format This parameter determines the The device certificate format can
device certificate format. be set to:
PEM
DER
PFX
certStorePwd This parameter determines the Set to the device certificate
password for a certificate that encryption password.
has been encrypted and stored. You do not need to set this
parameter if the device certificate
is not encrypted.
keyFileName This parameter determines the Set to the key file name.
name of the certificate key file.
keyStorePwd This parameter determines the Set to the password for encrypting
password for encrypting and the key file.
storing a key file. You do not need to set this
parameter if the key file is not
encrypted.
isTest This parameter determines This parameter is reserved and has
whether a test certificate is to be not been used.
installed.
isActive This parameter determines the Set this parameter to true.
certificate activation.
Only one device certificate can be installed on an SAU. Delete the device certificate that is not used.
Configure CRL certificate-related parameters
By default, the CRL certificate is not installed on the SAU. To install one or more CRL
certificates and configure relevant parameters, see Configure CA certificate-related
parameters.
Step 4 After the configuration, press Esc to switch to the command mode. Run the :wq! command to
save the file and exit the vi editor.
Step 5 Start the SAU processes for the modifications to take effect.
If... Then...
The EBC service 1. Run the following commands to start SAU processes, including
component is the SAU service processing processes and board management
installed processes (for the EBC service component):
# cd /opt/ebcsau
# . ./svc_profile.sh
# sau4ebc_start
2. Check whether all the SAU processes have been started by
referring to 3.4.9.1 Checking the Status of SAU Processes (for
the EBC Service Component).
The EMS service 1. Run the following commands to start SAU processes, including
component is the SAU service processing processes and board management
installed processes (for the EMS service component):
# cd /opt/emssau
# . ./svc_profile.sh
# sau4ems_start
2. Check whether all the SAU processes have been started by
referring to 3.4.10.1 Checking the Status of SAU Processes (for
the EMS Service Component).
----End
Procedure
Step 1 Log in to an SAU. For detailed operations, see Logging In to the SAU.
Step 2 Run the following command to check the occupied ports on the SAU:
# netstat -tuan
Information similar to the following is displayed, where the information next to : in the Local
Address column indicates the numbers of occupied ports:
omu_136 ~ # netstat -tuan
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 10.0.0.1:8000 0.0.0.0:* LISTEN
tcp 0 0 10.0.0.1:8001 0.0.0.0:* LISTEN
tcp 0 0 10.0.0.1:16002 0.0.0.0:* LISTEN
tcp 0 0 10.0.0.1:16002 0.0.0.0:* LISTEN
tcp 0 0 10.0.0.1:8099 0.0.0.0:* LISTEN
tcp 0 0 10.0.0.1:8100 0.0.0.0:* LISTEN
----End
Procedure
Step 1 Log in to the SAU. For details, see 3.1.4 Logging In to the SAU.
Step 2 Run the script for setting the environment variable based on the external systems.
Trace Server Run the following commands on the SAU board where
the EMS service component is installed:
# cd /opt/emssau
# . ./svc_profile.sh
1. Perform the following operation to stop SAU processes based on service component
deployed on the blade.
If the service Then...
component is...
Trace Server see 3.4.10.3 Stopping SAU Processes (for the EMS Service
Component)
EBC see 3.4.9.3 Stopping SAU Processes (for the EBC Service
Component)
2. Perform the following operation to start SAU processes based on service component
deployed on the blade.
If the service Then...
component is...
Trace Server see 3.4.10.2 Starting SAU Processes (for the EMS Service
Component)
EBC see 3.4.9.2 Starting SAU Processes (for the EBC Service
Component)
----End
Context
The SSL renegotiation function on the SAU is enabled by default.
When the SSL renegotiation function on the SAU is enabled, you need to set the SSL
renegotiation period. This prevents malicious clients from frequently performing SSL
renegotiation with the SAU, making valid clients fail to set up SSL connections with the
SAU due to a high CPU usage of the SAU.
For the SAU working with BSC6900 V900R016C00, BSC6910 V100R016C00, or a
later version, the SSL renegotiation function is consistent with that on the OMU, and the
information is automatically synchronized to the SAU. In this case, you can enable or
disable the SSL renegotiation function on the SAU by enabling or disabling the function
on the OMU. No manual operations are required on SAU.
Procedure
Step 1 Log in to the SAU. For details, see 3.1.4 Logging In to the SAU.
NOTE
The SSL renegotiation period indicates how long a new renegotiation
request can be handled following the previous renegotiation. The
value range is 0-60 minutes. The default value is 60 minutes.
When the system displays The SSL renegotiation is
enabled and the interval is set to 30., the SSL
renegotiation function is enabled and the renegotiation period is set to
30 minutes.
Prerequisites
You have logged in to the SAU. For details, see 3.1.4 Logging In to the SAU.
Context
For the SAU working with BSC6900 V900R016C00 or BSC6910 V100R016C00, or a
later version, the OMU automatically synchronizes SSL parameter configurations to the
SAU. No manual operations are required.
SSL parameters include connection type, authentication mode, and renegotiation
parameters.
Procedure
Step 1 Perform related operations based on SSL parameters.
If both the EBC and EMS service components have been deployed on the SAU board, you only need to
stop the process of the service component you want to set or modify.
2. Run the following command to navigate to the directory that stores the cerConfig.xml
configuration file.
If the service Then...
component is...
Default value: 1
4. After parameters are configured, press Esc to switch to the command mode. Run the
:wq! command to save the file and exit the vi editor.
5. Run the following commands to start the SAU processes for the modifications on
configuration file to take effect.
If the service Then...
component is...
----End
Prerequisites
You have logged in to the SAU. For details, see 3.1.4 Logging In to the SAU.
Context
You can run the SET SAUFTPSCLT and LST SAUFTPSCLT commands to set and query
FTP client parameters, respectively, for the SAU working with BSC6900 V900R016C00,
BSC6910 V100R016C00, and later versions.
Procedure
Step 1 Stop SAU processes.
If both the EBC and EMS service components have been deployed on the SAU board, you only need to
stop the process of the service component you want to set or modify.
Step 2 Run the following command to navigate to the directory that stores the ftpsclient.xml
configuration file.
Step 3 Perform the following steps to modify the ftpsclient.xml configuration file:
1. Run the following command to modify the ftpsclient.xml configuration file:
# vi ftpsclient.xml
Press i to enter the editing mode. Find the related FTP client parameters as shown in the
command output. Then, change the parameter values. For details about FTP client
parameters, see Table 4-7.
<policy encrypted_mode="0" support_statefwl="0" command_port="21"
data_port="20" transfer_mode="1" transfer_size="4096"
progress_interval="5" min_port="25001" max_port="30000" ccc_suport="1"
client_num="500" time_out="30" enable_authtype="2" ssl_version="1">
</policy>
value.
time_out Timeout for None Default value: 30
receiving data Retain the default
Unit: second value.
enable_authtype Whether SSL-based SSLCERTAUTH 1: not
digital certificate authenticated
authentication is 2: peer-end
supported authenticated
Default value: 1
ssl_version SSL protocol None 1: Negotiated
version< version during
handshaking
2: SSL 2.0
3: SSL 3.0
4: TLS 1.0
5: TLS 1.1
6: TLS 1.2
Default value: 1
2. After parameters are configured, press Esc to switch to the command mode. Run the
:wq! command to save the file and exit the vi editor.
Step 4 Run the following commands to start the SAU processes for the modifications on
configuration file to take effect.
----End
Function
The routing table relays IP addresses between network segments. The route command is used
to modify and maintain the routing table.
Format
route -CFvnee
route -v -A family add -net|-host target netmask gw
route -v -A family del -net|-host target netmask gw
Authorized User
This command is executed by user root.
Parameter Description
Options of the route command can be combined. Table 5-1 lists the common options.
Option Description
Application Example
Check the information about the routing table.
root@osssvr # route -ne
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window
irtt Iface
10.71.15.0 0.0.0.0 255.255.255.0 U 0 0
0 eth2
10.254.0.0 0.0.0.0 255.255.0.0 U 0 0
0 eth2
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0
0 lo
0.0.0.0 10.71.15.1 0.0.0.0 UG 0 0
0 eth2
Add a route.
root@osssvr # route add -net 10.71.15.0 netmask 255.255.255.0 gw 10.71.15.1
root@osssvr # route -ne
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
10.71.15.0 10.71.15.1 255.255.255.0 UG 0 0 0 eth2
10.71.15.0 0.0.0.0 255.255.255.0 U 0 0 0 eth2
10.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth2
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 10.71.15.1 0.0.0.0 UG 0 0 0 eth2
Function
The ifconfig command is used for viewing the IP address of the host.
Syntax
ifconfig option
Authorized User
This command is executed by user root.
Options
-a: views the information about all the addresses.
-a: views the information about all the addresses.
bond1: views the fixed external IP address, broadcast IP address, and subnet mask.
vlan1: views the fixed internal IP address, broadcast IP address, and subnet mask.
bond2: views the debugging IP address, broadcast IP address, and subnet mask.
Example
To view the IP address of the host, run the following command:
# ifconfig -a
bond0 Link encap:Ethernet HWaddr 00:25:9E:96:BB:C6
inet6 addr: fe80::225:9eff:fe96:bbc6/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:5979810 errors:0 dropped:0 overruns:0 frame:0
TX packets:551223 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:375631320 (358.2 Mb) TX bytes:23272066 (22.1 Mb)
In the preceding example, the displayed IP addresses of the host are as follows: The external IP address
is 10.141.146.201, the debugging IP address is 192.168.6.50, and the internal IP address is 172.16.3.250.
Function
The ping command is used to check the physical connection of the network when the
communication between a PC and the hosts in the network is interrupted.
Format
ping IP address of a host
Example
Check the physical connection between the current host and the host whose IP address is
10.71.15.1.
# ping 10.71.15.1
PING 10.71.15.1 (10.71.15.1) 56(84) bytes of data.
64 bytes from 10.71.15.1: icmp_seq=1 ttl=255 time=11.5 ms
64 bytes from 10.71.15.1: icmp_seq=2 ttl=255 time=7.11 ms
64 bytes from 10.71.15.1: icmp_seq=3 ttl=255 time=7.77 ms
You can press Ctrl+Z (case insensitive) to stop running the ping command.
The Internet Control Message Protocol (ICMP) is used through the ping command to check
the network connection. An ICMP echo request message is sent to a specific host to request an
ICMP echo response message. If the response message is not received within a specified time,
the Host unreachable message is displayed on the screen.
To analyze the causes, run the ping command to connect to other hosts in the same network
segment. If the ping command is successful, you can infer that the connection is functional. In
this case, check the physical connection and the operational status of the specified host. If the
ping command fails, check whether the physical network connection of the current host is
secure or whether the TCP/IP protocol is set correctly.
Function
Use this command to query the information about the SAU. The information includes the
running state of the SAU, fixed IP addresses, and version.
Note
None
Parameters
Parameter ID Parameter Name Parameter Description
Example
To query the information about the SAU, run the following command:
DSP SAU:;
%%DSP SAU:;%%
RETCODE = 0 Execution succeeded.
--- END
Output Description
Domain Name Description
Function
Use this command to query the version information of the SAU area.
Note
None
Parameters
Parameter ID Parameter Name Parameter Description
Performance: N/A
SN Slot No. Meaning: Indicates the slot
number for running this
command.
GUI Value Range: 0~27
Unit: None
Actual Value Range: 0~27
MML Default Value: None
Recommended Value: None
Parameter Relationship:
None
Service Interrupted After
Modification: N/A
Impact on Network
Performance: None
Example
To switch over the working area of the SAU, run the following command:
DSP SAUAREA:;
%%DSP SAUAREA:;%%
RETCODE = 0 Execution succeeded.
--- END
Output Description
Domain Name Description
Function
Use this command to query the running state of modules on the SAU.
Note
None
Parameters
Parameter ID Parameter Name Parameter Description
Impact on Network
Performance: None
Example
To query the state of the SAU, run the following command:
DSP SAUMODULE:;
%%DSP SAUMODULE:;%%
RETCODE = 0 Execution succeeded.
--- END
Output Description
Domain Name Description
Function
Use this command to query the state of the SAU Server.
Note
None
Parameters
Parameter ID Parameter Name Parameter Description
Example
To query the state of the SAU server, run the following command:
DSP SAUSRV:;
%%DSP SAUSRV:;%%
RETCODE = 0 Execution succeeded.
(Number of results = 1)
--- END
Output Description
Domain Name Description
Function
This command is used to query the SAU business instance at SAU board.
Note
None
Parameters
Parameter ID Parameter Name Parameter Description
Example
To query the SAU business instance at SAU board, run the following command:
DSP SAUINSTANCE:;
--- END
Output Description
Domain Name Description
Function
Use this command to query the certificate synchronization status of the SAU.
Note
Only the system administrator can run this command.
Parameters
Parameter ID Parameter Name Parameter Description
Example
Use this command to query the certificate synchronization status of the SAU:
DSP SAUCERTFILE: SRN=0, SN=23;
--- END
Output Description
Domain Name Description
Function
Use this command to reset the software or hardware of the SAU.
Note
1. If the reset type is SOFT, the SAU software is reset. If the reset type is HARD, the SAU
hardware is reset.
2. When multiple SAUs are configured, all the SAUs will be reset if the subrack number and
slot number are not specified.
Parameters
Parameter ID Parameter Name Parameter Description
mode)
Impact on Network
Performance: None
SRN Subrack No. Meaning: Number of the
subrack.
GUI Value Range: 0~11
Unit: None
Actual Value Range: 0~11
MML Default Value: None
Recommended Value: None
Parameter Relationship:
None
Service Interrupted After
Modification: N/A
Impact on Network
Performance: N/A
SN Slot No. Meaning: Indicates the slot
number for running this
command.
GUI Value Range: 0~27
Unit: None
Actual Value Range: 0~27
MML Default Value: None
Recommended Value: None
Parameter Relationship:
None
Service Interrupted After
Modification: N/A
Impact on Network
Performance: None
Example
1. To reset the hardware of the SAU( (Subrack No. = 0, Slot No. = 23)), run the
following command:
RST SAU: TP=HARD, SRN=0, SN=23;
Running result
--------------
Subrack No. = 0
Slot No. = 23
State = Success
(Number of results = 1)
--- END
2. To reset the software of the SAU( (Subrack No. = 0, Slot No. = 23)), run the
following command:
RST SAU: TP=SOFT, SRN=0, SN=23;
Running result
--------------
Subrack No. = 0
Slot No. = 23
State = Success
(Number of results = 1)
--- END
Function
Use this command to switch over the working area of the SAU.
Note
1. Switching the working area of the SAU changes the version and data of the SAU and
disrupts the services on the SAU.
2. To keep normal SAU switchover, you should ensure that the standby working area of the
SAU is normally installed.
3. Before running this command, you should ensure that no other operations are performed on
the SAU.
4. When multiple SAUs are configured, the work areas of all the SAUs will be switched over
if the subrack number and slot number are not specified.
Parameters
Parameter ID Parameter Name Parameter Description
Example
1. To switch over the working area of the SAU (Subrack No. = 0, Slot No. = 23),
run the following command:
SWP SAUAREA: SRN=0, SN=23;
Running result
--------------
Subrack No. = 0
Slot No. = 23
State = Success
(Number of results = 1)
--- END
Function
This command is used to specify whether to set the SAU board in a specified slot to the FTP
center.
Note
1. When setting an SAU as the FTP center, the state of the SAU must be normal. Otherwise,
command execution on the SAU will fail.
2. Data reception on the SAU may temporarily fail during a switch of the SAU FTP center.
Parameters
Parameter ID Parameter Name Parameter Description
Example
To set an SAU as the FTP center (Subrack N0. = 1, Slot No. = 23), run the
following command:
SET SAUCENTER: FTPCENTER=ON, SRN=0, SN=23;
Function
Use this command to query the subrack and slot information about the SAU that functions as
the FTP center.
Note
None
Parameters
None
Example
To query the subrack and slot information about the SAU that functions as the FTP
center, run the following command:
LST SAUCENTER:;
%%LST SAUCENTER:;%%
RETCODE = 0 Execution succeeded.
Center of SAU
-------------
Subrack No. = 0
Slot No. = 23
(Number of results = 1)
--- END
Output Description
Domain Name Description
Function
Use this command to query the SSL configuration of the SAU.
Note
Only the system administrator can run this command.
Parameters
Parameter ID Parameter Name Parameter Description
Impact on Network
Performance: None
SN Slot No. Meaning:
GUI Value Range: 0~27
Unit: None
Actual Value Range: 0~27
MML Default Value: None
Recommended Value: None
Parameter Relationship:
None
Service Interrupted After
Modification: N/A
Impact on Network
Performance: None
Example
To query the SAU SSL configuration, run the following command:
LST SAUSSLCONF:SRN=0, SN=23;
--- END
Output Description
Domain Name Description
SSLAUTHMODE command.
Renegotiation Switch See the parameter description of the SET
SSLCONF command.
Renegotiation Interval See the parameter description of the SET
SSLCONF command.
Function
Use this command to add a board. This command can be used by all types of boards except
the SCUa, SCUb, GCUa, GCUb, GCGa and GCGb.
Note
1. Configure the boards in the following sequence: XPU, TNU, INT/DPU/NIU, OMU/SAU.
2. After a subrack is added, the SCUa/SCUb boards are configured in slots 6 and 7 by default
and cannot be removed. The GCUa boards are automatically configured in slots 12 and 13 in
the MPS and cannot be removed.
3. When adding the boards that are in active/standby mode, set SN to an even number. The
active and standby boards can be added at the same time by running this command once.
4. If the subrack is in effective mode and the board added by this command has been installed,
the board immediately starts and performs internal configuration after this command is
executed. When a board is during internal configuration, other commands cannot be executed.
To check whether any board is during internal configuration, run the DSP BRD command.
5. The precautions for adding an XPU board are as follows:
1) The XPU board with the logical function of RGCP or RUCP manages resources and must
be configured preferentially. It is recommended that you configure one XPUa/SPUa board out
of every six pairs of XPUa/SPUa boards to be of the RGCP/RUCP type, and configure one
XPUb/SPUb/XPUc/SPUc board out of every three pairs of XPUb/SPUb/XPUc/SPUc boards
to be of the RGCP/RUCP type.
2) When adding an XPU board with the logical function of GCP or UCP to the MPS or EPS,
bind the added board with the board where the MPU subsystem is located.
3) An XPU board cannot be configured in slot 24 or 25 of the MPS.
6. The precautions for adding a TNU board are as follows:
1) A TNU board is needed in TDM networking mode to maintain the inter-subrack TDM
service switching capability.
2) TNUa or TNUb boards must be configured in active/standby mode in slot 4.
3) When adding TNU boards to the MPS or EPS, bind the added boards with the board where
the MPU subsystem is located.
4) When adding a TNUa or TNUb board, set Add inter-subrack path automatically based
on the actual conditions. You can query the inter-subrack path by running the LST
SRCONPATH command.
7. The precautions for adding an INT board are as follows:
1) When adding an INT board to the MPS or EPS, bind the added board with the board where
the MPU subsystem is located.
2) Before adding an EIUa/EIUb (Abis_TDM/Ater_TDM/Pb_TDM/A_TDM), OIUa/OIUb
(Abis_TDM/Ater_TDM/Pb_TDM/A_TDM), or POUc (TDM) board, ensure that the TNUa or
TNUb board has been configured.
3) When adding an EIUa/EIUb (Abis_TDM/Ater_TDM/Pb_TDM/A_TDM), OIUa/OIUb
(Abis_TDM/Ater_TDM/Pb_TDM/A_TDM), or POUc (TDM) board, it is recommended that
you set RED to YES. This avoids that reliability of the interface board to be added does not
decrease.
4) During site deployment or capacity expansion, it is recommended that you configure the
FG2c, GOUc, GOUe, FG2d, GOUd, and UOIc boards in slots 16 to 23.
8. The precautions for adding a DPU board are as follows:
1) When adding a DPU board to the MPS or EPS, bind the added board with the board where
the MPU subsystem is located.
2) Before adding the DPUa (GTC), DPUb (GTC/GPCU), DPUc (GTC), DPUd (GPCU),
DPUe/DPUh (GPCU), DPUf (GTC), or DPUg/DPUj (GPCU) board, ensure that an XPU
board with the logical function of RGCP or GCP has been configured. Otherwise, software
loading fails in the DSP.
3) Before adding the DPUb (UUP) or DPUe/DPUh (UUP) board, ensure that an XPU board
with the logical function of RUCP or UCP has been configured. Otherwise, software loading
fails in the DSP.
9. The precautions for adding an NIU board are as follows:
1) An NIU board can only be configured in the MPS or EPS. When adding an NIU board,
bind the added board with the board where the MPU subsystem is located.
10. The precautions for adding an OMU board are as follows:
1) An OMU board can only be configured in the MPS.
2) An OMUa or OMUb board occupies two slots and an OMUc board occupies one slot.
3) If the BSC6900 works in single-OMU mode and an OMUa/OMUb board is configured, the
OMUa/OMUb board can be installed in slot 0, 2, 21, 23, 25, or 27. If the BSC6900 works in
single-OMU mode and an OMUc board is configured, the OMUc board can be installed in
slots 0-3 or slots 20-27.
4) If the BSC works in dual-OMU mode and two OMUa/OMUb boards are configured, the
OMUa/OMUb boards can be installed in slots 0 and 2, 21 and 23, or 25 and 27. If the
BSC6900 works in dual-OMU mode and two OMUc boards are configured, the OMUc
boards can be installed in slots 0 and 1, 2 and 3, 20 and 21, 22 and 23, 24 and 25, or 26 and
27.
5) If the BSC6900 works in dual-OMU mode and one OMUa/OMUb board and one OMUc
board are configured, the OMUa/OMUb board can be installed in slot 0, 2, 21, 23, 25, or 27,
and the OMUc board must be installed adjacent to the OMUa/OMUb board. That is, the
OMUa/OMUb board and the OMUc board must be in slots 0 and 2, slots 21 and 23, or slots
25 and 27.
11. The precautions for adding an SAU board are as follows:
1) The SAU boards must be installed in the lowest subrack of the cabinet for good heat
dissipation.
2) An SAUa board occupies two slots and an SAUc board occupies one slot.
3) If an SAUa/SAUc board is added by running this command, a soft reset of this
SAUa/SAUc board must be implemented by running the RST SAU command.
12. A pair of active and standby MPU subsystems can simultaneously manage a maximum of:
1) 32 EIUa, EIUb, OIUa, and OIUb boards as well as POUc boards whose logical function
type is TDM.
2) 14 AEUa, PEUa, PEUc, AOUa, AOUc, UOIa, UOIc, FG2a, FG2c, FG2d, GOUa, GOUc,
GOUe, GOUd, and POUa boards as well as POUc boards whose logical function type is IP.
Note that one pair of active and standby boards are still considered as one board here. For
example, a pair of active and standby MPU subsystems can manage 14 OIUa boards and 14
pairs of active and standby OIUb boards.
13. After a board is started, the counter value for the board is unreliable in the first
measurement period.
14. When an AOUa/AOUc/UOIa/UOIc/FG2a/FG2c/GOUa/GOUc/GOUe/FG2d/GOUd board
is added to a BSC, the physical ports for the boards are automatically configured. The total
number of ATM logical ports, IP logical ports, resource groups, and physical ports configured
for a BSC must not exceed 8192.
15. An MPU can simultaneously manage 14 pairs of interface boards using IP, ATM, and
HDLC transmission modes.
16. A maximum number of five NIUa boards can be configured for an MPS. A maximum of
six NIUa boards can be configured for an EPS. The total number of
DPUa/DPUb/DPUc/DPUd/DPUe/DPUf/DPUg and NIUa boards configured for a subrack
cannot exceed 15.
17. A maximum number of 5 POUc boards can be configured for one TC subrack. If
EIUa/EIUb/OIUa/OIUb boards are configured in the same TC subrack as the POUc boards, 4
EIUa/EIUb/OIUa/OIUb boards are considered as one POUc board. One pair of active and
standby boards is considered as one board here.
Parameters
Parameter ID Parameter Name Parameter Description
Parameter Relationship:
None
Service Interrupted After
Modification: No (And no
impact on the UE in idle
mode)
Impact on Network
Performance: None
BRDCLASS Board Class Meaning: Classes of boards
classified according to
function modules
GUI Value Range: INT,
DPU, XPU, TNU, OMU,
SAU, NIU
Unit: None
Actual Value Range: INT,
DPU, XPU, TNU, OMU,
SAU, NIU
MML Default Value: None
Recommended Value: None
Parameter Relationship:
None
Service Interrupted After
Modification: No (And no
impact on the UE in idle
mode)
Impact on Network
Performance: None
BRDTYPE Board Type Meaning: Type of the board
GUI Value Range: AEUa,
AOUa, AOUc, DPUa,
DPUb, DPUc, DPUd, DPUe,
DPUf, DPUg, DPUh, DPUj,
EIUa, EIUb, FG2a, FG2c,
FG2d, GOUa, GOUc,
GOUd, GOUe, NIUa, NIUc,
OIUa, OIUb, OMUa,
OMUb, OMUc, PEUa,
PEUc, POUa, POUc, SAUa,
SAUc, SPUa, SPUb, SPUc,
TNUa, TNUb, UOIa, UOIc,
XPUa, XPUb, XPUc
Unit: None
Actual Value Range: AEUa,
AOUa, AOUc, DPUa,
DPUb, DPUc, DPUd, DPUe,
DPUf, DPUg, DPUh, DPUj,
OIUb/A_TDM channelized
Optical STM-1 Interface for
A
Abis_IP: PEUa/Abis_IP IP
interface for Abis
SAU: Service Aware Unit.
The SAUa/SAUc board
filters and takes statistics of
the data reported by NEs and
reports the result to the
upper-level product.
NIU: Network Intelligence
Unit
NASP: Network Assistant
Service Processor
GUI Value Range: A_TDM,
Abis_IP, Abis_TDM,
Ater_TDM, ATM, FR, GbIP,
GCP, GPCU, GTC, HDLC,
IP, MCP, NASP, NIU, OAM,
Pb_TDM, RGCP, RUCP,
SAU, TDM_Switching,
TDM, UCP, UUP
Unit: None
Actual Value Range:
A_TDM, Abis_IP,
Abis_TDM, Ater_TDM,
ATM, FR, GbIP, GCP,
GPCU, GTC, HDLC, IP,
MCP, NASP, NIU, OAM,
Pb_TDM, RGCP, RUCP,
SAU, TDM_Switching,
TDM, UCP, UUP
MML Default Value: None
Recommended Value: None
Parameter Relationship:
This parameter is valid if
one of the following
conditions is met:
1.BRDCLASS is set to
TNU,SAU,OMU.
2.BRDTYPE is set to
SPUb,NIUa,NIUc,DPUf,PO
Ua,POUc,DPUg,AEUa,DPU
e,DPUd,DPUc,DPUb,DPUa,
XPUb,DPUj,DPUh,GOUe,G
OUd,XPUa,EIUb,GOUa,GO
Uc,XPUc,AOUc,FG2c,FG2
a,AOUa,FG2d,OIUb,OIUa,
UOIc,SPUc,UOIa,SPUa,EI
Ua,PEUc,PEUa. This
parameter must be set when
BRDTYPE is set to
EIUa,DPUe,DPUb,SPUc,SP
Ub,FG2a,OIUa,SPUa,XPUc,
XPUb,XPUa,EIUb,UOIa,PE
Uc,OIUb,PEUa,POUc.The
default value of
"LGCAPPTYPE" is OAM
when "BRDCLASS" in MO
BRD is set to OMU, SAU
when "BRDCLASS" in MO
BRD is set to SAU and
TDM_Switching when
"BRDCLASS" in MO BRD
is set to TNU.
Service Interrupted After
Modification: N/A
Impact on Network
Performance: None
SN Slot No. Meaning: Number of the slot
GUI Value Range: 0~27
Unit: None
Actual Value Range: 0~27
MML Default Value: None
Recommended Value: None
Parameter Relationship: The
default value of "SN" is 4
when "BRDCLASS" in MO
BRD is set to TNU.
Service Interrupted After
Modification: No (And no
impact on the UE in idle
mode)
Impact on Network
Performance: None
RED Backup Meaning: Working mode of
a board. If this parameter is
set to YES, the board works
in active/standby mode. If
this parameter is set to NO,
the board works in
independent mode.
GUI Value Range:
YES(YES), NO(NO)
Unit: None
Example
1.To add a board (Subrack No. = 0; Board Class = XPU; Board Type = XPUa; Logic
function type = RGCP; Slot No. = 0), run the following command:
ADD BRD: SRN=0, BRDCLASS=XPU, BRDTYPE=XPUa, LGCAPPTYPE=RGCP, SN=0;
2.To add a board (Subrack No. = 0; Board Class = XPU; Board Type = SPUa; Logic
function type = RUCP; Slot No. = 2), run the following command:
ADD BRD: SRN=0, BRDCLASS=XPU, BRDTYPE=SPUa, LGCAPPTYPE=RUCP, SN=2;
3.To add a board (Subrack No. = 0; Board Class = DPU; Board Type = DPUb; Logic
function type = UUP; Slot No. = 10;
Is TC board = NO(NO); MPU Subrack No. = 0; MPU Slot No. = 2), run the following
command:
ADD BRD: SRN=0, BRDCLASS=DPU, BRDTYPE=DPUb, LGCAPPTYPE=UUP, SN=10, ISTCBRD=NO,
MPUSUBRACK=0, MPUSLOT=2;
Function
Use this command to remove a board. This command is used on all types of boards except
the SCUa, SCUb, GCUa, GCUb, GCGa and GCGb.
Note
1. The board is unavailable after the removal. You must use this command with caution.
2. The board where the MPU subsystem is configured can be removed only when the MPU
subsystem is not bound with other boards.
3. The MML command cannot be run to remove the SCUa, SCUb, GCGa, GCGb, GCUa and
GCUb boards that are configured in the system by default.
4. After a board is removed, the counter values for the board are unreliable in the last
measurement period.
5. Before deleting an SAU board, check whether the board to be deleted functions as the SAU
center. If yes, this board cannot be deleted. If you want to delete the board that functions as
the SAU center, run the SET SAUCENTER command to change the board to non-SAU
center, and then delete this board.
Parameters
Parameter ID Parameter Name Parameter Description
Example
To remove the board in slot 10 of subrack 0 (Subrack No. = 0; Slot No. = 10), run
the following command:
RMV BRD: SRN=0, SN=10;
Function
Use this command to query the information about the OMU.
Note
1. In dual-server mode, the OMU consists of the active and standby nodes. You can use this
command to query the configurations and states of each node, data synchronization
information, and link states.
2. The virtual IP address is the one configured on the active OMU during the installation.
3. When the OMU is installed in single-server mode, the data synchronization status, the
status of the network ,and backup channel are unavailable.
4. The data synchronization status can only be queried only when the standby OMU server
works in stable state.
5. The process of the data synchronization between the active and standby OMUs consists of
two steps:
(1) The standby OMU server synchronizes the initial data of the active OMU server.
(2) The standby OMU server synchronizes the modification of the active OMU server in real
time.
Parameters
None
Example
To query the information about the OMU, run the following command:
DSP OMU:;
%%DSP OMU:;%%
RETCODE = 0 Execution succeeded.
Subrack No. = 0
Slot No. = 27
Computer name = OMU_27
Internal network fixed IP = 172.16.3.60
External network fixed IP = 10.168.172.8
Backup network IP = 192.168.3.60
Debugging IP = 192.168.6.60
Operational state = Standby normal
Version = XXXXXX
(Number of results = 2)
Other state
-----------
Internal network virtual IP = 172.16.3.40
Internal network virtual IP mask = 255.0.0.0
External network virtual IP = 10.168.172.5
External network virtual IP mask = 255.255.254.0
Internal network virtual IP state = Normal
External network virtual IP state = Normal
Data-sync state = Data synchronization is successful
Internal network link state = Normal
External network link state = Normal
Backup network link state = Normal
(Number of results = 1)
--- END
Output Description
Domain Name Description
If network connections break down, ALM-20702 Active and Standby OMU Communication
Link Failure is generated. Then, you must clear the alarm by referring to the related alarm
handling suggestions.
Function
Use this command to set the security policy of the SAU FTP client.
Note
1. When the encryption mode for transmission is set to AUTO, the FTP client first tries to
connect the FTP server with the encrypted mode. If the connection fails, the plain text mode is
selected.
2. If the state firewall is selected, the FTP client sends the CCC command to the firewall to
switch the transmission mode to the plain text.
3. If the SSL certificate authentication is selected, certificates for the NE should be configured
on the U2000 at first.
Parameters
Parameter ID Parameter Name Parameter Description
encryption mode.
PLAINTEXT(Plain Text):
indicates that the plaintext
mode must be used.
ENCRYPTED(SSL
Encrypted): indicates that
the encrypted mode must be
used.
GUI Value Range:
AUTO(Auto),
PLAINTEXT(Plain Text),
ENCRYPTED(SSL
Encrypted)
Unit: None
Actual Value Range: AUTO,
PLAINTEXT,
ENCRYPTED
MML Default Value: None
Recommended Value:
AUTO(Auto)
Parameter Relationship:
None
Service Interrupted After
Modification: N/A
Impact on Network
Performance: None
SPTSTATEFWL Support State Firewall Meaning: Whether the FTP
client supports the state
firewall.
GUI Value Range: NO(Not
Support), YES(Support)
Unit: None
Actual Value Range: NO,
YES
MML Default Value: None
Recommended Value:
YES(Support)
Parameter Relationship:
None
Service Interrupted After
Modification: No (And no
impact on the UE in idle
mode)
Impact on Network
Performance: None
Example
1. To set the security policy of the FTP client (The Encrypted Mode = PLAINTEXT;
Support State Firewall = YES), run the following command:
SET SAUFTPSCLT: ENCRYMODE=PLAINTEXT, SPTSTATEFWL=YES;
2. To set the security policy of the FTP client (The Encrypted Mode = ENCRYPTED;
Function
Use this command to query the security policy of the SAU FTP client.
Note
None
Parameters
Parameter ID Parameter Name Parameter Description
Example
%%LST SAUFTPSCLT:SRN=0,SN=23;%%
RETCODE = 0 Execution succeeded.
(Number of results = 1)
--- END
Output Description
Domain Name Description
Function
Use this command to query the setting of the event CHR(Call History Record) process switch
on an application for an RNC.
Note
None
Parameters
Parameter ID Parameter Name Parameter Description
VERTICAL
MML Default Value:
VERTICAL
Recommended Value: None
Parameter Relationship:
None
Service Interrupted After
Modification: N/A
Impact on Network
Performance: None
Example
To query the setting of the event CHR process switch on the EBC for an RNC, run
the following command:
LST UMMEVENTCHRCTRL: AppType=EBC;
%%LST UMMEVENTCHRCTRL: AppType=EBC;%%
RETCODE = 0 Execution succeeded.
--- END
Function
Use this command to query the information about the SAU. The information includes the
running state of the SAU, fixed IP addresses, and version.
Note
None
Parameters
Parameter ID Parameter Name Parameter Description
Example
To query the information about the SAU, run the following command:
DSP SAU:;
%%DSP SAU:;%%
RETCODE = 0 Execution succeeded.
--- END
Output Description
Domain Name Description
Function
Use this command to query the version information of the SAU area.
Note
None
Parameters
Parameter ID Parameter Name Parameter Description
Example
To switch over the working area of the SAU, run the following command:
DSP SAUAREA:;
%%DSP SAUAREA:;%%
RETCODE = 0 Execution succeeded.
--- END
Output Description
Domain Name Description
is installed.
Mainarea version Version of the software installed on the
active SAU workspace.
Standbyarea version Version of the software installed on the
standby SAU workspace.
Function
Use this command to query the running state of modules on the SAU.
Note
None
Parameters
Parameter ID Parameter Name Parameter Description
Example
To query the state of the SAU, run the following command:
DSP SAUMODULE:;
%%DSP SAUMODULE:;%%
RETCODE = 0 Execution succeeded.
--- END
Output Description
Domain Name Description
Function
Use this command to query the state of the SAU Server.
Note
None
Parameters
Parameter ID Parameter Name Parameter Description
Example
To query the state of the SAU server, run the following command:
DSP SAUSRV:;
%%DSP SAUSRV:;%%
RETCODE = 0 Execution succeeded.
(Number of results = 1)
--- END
Output Description
Domain Name Description
Function
This command is used to query the SAU business instance at SAU board.
Note
None
Parameters
Parameter ID Parameter Name Parameter Description
Example
To query the SAU business instance at SAU board, run the following command:
DSP SAUINSTANCE:;
--- END
Output Description
Domain Name Description
Function
Use this command to query the certificate synchronization status of the SAU.
Note
Only the system administrator can run this command.
Parameters
Parameter ID Parameter Name Parameter Description
Example
Use this command to query the certificate synchronization status of the SAU:
DSP SAUCERTFILE: SRN=0, SN=23;
--- END
Output Description
Domain Name Description
Function
Use this command to reset the software or hardware of the SAU.
Note
1. If the reset type is SOFT, the SAU software is reset. If the reset type is HARD, the SAU
hardware is reset.
2. When multiple SAUs are configured, all the SAUs will be reset if the subrack number and
slot number are not specified.
Parameters
Parameter ID Parameter Name Parameter Description
mode)
Impact on Network
Performance: None
SRN Subrack No. Meaning: Number of the
subrack.
GUI Value Range: 0~11
Unit: None
Actual Value Range: 0~11
MML Default Value: None
Recommended Value: None
Parameter Relationship:
None
Service Interrupted After
Modification: N/A
Impact on Network
Performance: N/A
SN Slot No. Meaning: Indicates the slot
number for running this
command.
GUI Value Range: 0~27
Unit: None
Actual Value Range: 0~27
MML Default Value: None
Recommended Value: None
Parameter Relationship:
None
Service Interrupted After
Modification: N/A
Impact on Network
Performance: None
Example
1. To reset the hardware of the SAU( (Subrack No. = 0, Slot No. = 23)), run the
following command:
RST SAU: TP=HARD, SRN=0, SN=23;
Running result
--------------
Subrack No. = 0
Slot No. = 23
State = Success
(Number of results = 1)
--- END
2. To reset the software of the SAU( (Subrack No. = 0, Slot No. = 23)), run the
following command:
RST SAU: TP=SOFT, SRN=0, SN=23;
Running result
--------------
Subrack No. = 0
Slot No. = 23
State = Success
(Number of results = 1)
--- END
Function
Use this command to switch over the working area of the SAU.
Note
1. Switching the working area of the SAU changes the version and data of the SAU and
disrupts the services on the SAU.
2. To keep normal SAU switchover, you should ensure that the standby working area of the
SAU is normally installed.
3. Before running this command, you should ensure that no other operations are performed on
the SAU.
4. When multiple SAUs are configured, the work areas of all the SAUs will be switched over
if the subrack number and slot number are not specified.
Parameters
Parameter ID Parameter Name Parameter Description
Example
1. To switch over the working area of the SAU (Subrack No. = 0, Slot No. = 23),
run the following command:
SWP SAUAREA: SRN=0, SN=23;
Running result
--------------
Subrack No. = 0
Slot No. = 23
State = Success
(Number of results = 1)
--- END
Function
This command is used to specify whether to set the SAU board in a specified slot to the FTP
center.
Note
1. When setting an SAU as the FTP center, the state of the SAU must be normal. Otherwise,
command execution on the SAU will fail.
2. Data reception on the SAU may temporarily fail during a switch of the SAU FTP center.
Parameters
Parameter ID Parameter Name Parameter Description
Example
To set an SAU as the FTP center (Subrack N0. = 1, Slot No. = 23), run the
following command:
SET SAUCENTER: FTPCENTER=ON, SRN=0, SN=23;
Function
Use this command to query the subrack and slot information about the SAU that functions as
the FTP center.
Note
None
Parameters
None
Example
To query the subrack and slot information about the SAU that functions as the FTP
center, run the following command:
LST SAUCENTER:;
%%LST SAUCENTER:;%%
RETCODE = 0 Execution succeeded.
Center of SAU
-------------
Subrack No. = 0
Slot No. = 23
(Number of results = 1)
--- END
Output Description
Domain Name Description
Function
Use this command to query the SSL configuration of the SAU.
Note
Only the system administrator can run this command.
Parameters
Parameter ID Parameter Name Parameter Description
Impact on Network
Performance: None
SN Slot No. Meaning:
GUI Value Range: 0~27
Unit: None
Actual Value Range: 0~27
MML Default Value: None
Recommended Value: None
Parameter Relationship:
None
Service Interrupted After
Modification: N/A
Impact on Network
Performance: None
Example
To query the SAU SSL configuration, run the following command:
LST SAUSSLCONF:SRN=0, SN=23;
--- END
Output Description
Domain Name Description
SSLAUTHMODE command.
Renegotiation Switch See the parameter description of the SET
SSLCONF command.
Renegotiation Interval See the parameter description of the SET
SSLCONF command.
Function
Use this command to add a board. This command can be used by all types of boards except
the SCUb, GCUa, GCGa, GCUb, GCGb, EGPUa(RMP) and EXPUa(RMP).
Note
1. You are advised to configure the boards in the following sequence: GPU, INT, NIU, DPU,
OMU, SAU.
2. After a subrack is added, the SCUb boards are automatically configured in slots 20 and 21.
In the MPS, the EGPUa boards are automatically configured in slots 8 and 9 and the GCUa
boards are automatically configured in slots 14 and 15. These automatically configured boards
cannot be removed.
3. When adding the boards that are in active/standby mode, set SN to an even number. The
active and standby boards can be added at the same time by running this command once.
4. For GPU boards:
1) A maximum of 128 GPU boards can be configured in a base station controller. A maximum
of 64 GPU boards whose logical function type is GCUP, GMCP, NASP or UMSP can be
configured.
2) If the subrack is a Main Processing Subrack (MPS), the GPU board can be configured only
in slots 0-7, 10-13, 16-19, and 22-27. If the subrack is not an MPS, the GPU board can be
configured only in slots 0-19 and 22-27.
5. For INT boards:
1) If the subrack is a Main Processing Subrack (MPS), the INT board can be configured only
in slots 16-19 and 22-27. If the subrack is not an MPS, the INT board can be configured only
in slots 14-19 and 22-27.
2) EXOUa boards can only be configured in slots 16-19 and 22-25.
3) A maximum of 12 INT boards can be configured in a subrack.
6. For OMU boards:
1) OMU boards can only be configured in the MPS.
2) An EOMUa occupies two slots.
3) If the BSC6910 works in single-OMU mode and an EOMUa board is configured, the
EOMUa board can be configured in slot 0, 2, 4, 6, 10, 12, 25, or 27.
4) If the BSC6910 works in dual-OMU mode and two EOMUa boards are configured, the
EOMUa boards can be configured in slots 0 and 2, 4 and 6, 10 and 12, or 25 and 27.
7. For SAU boards:
1) An ESAUa board occupies two slots.
2) If an ESAUa board is added by running this command, a soft reset of this ESAUa board
must be implemented by running the RST SAU command.
3) If the subrack is a Main Processing Subrack (MPS), the ESAUa board can be configured
only in slots 0-7, 10-13, 16-19, and 22-27. If the subrack is not an MPS, the ESAUa board can
be configured only in slots 0-19 and 22-27.
8. For NIU boards:
1) If the subrack is a Main Processing Subrack (MPS), the NIU board can be configured only
in slots 0-7, 10-13, 16-19, and 22-27. If the subrack is not an MPS, the NIU board can be
configured only in slots 0-19 and 22-27.
9. For DPU boards:
1) If the subrack is a Main Processing Subrack (MPS), the NIU board can be configured only
in slots 0-7, 10-13, 16-19, and 22-27. If the subrack is not an MPS, the NIU board can be
configured only in slots 0-19 and 22-27.
2) Before adding the DPU board, ensure that a GPU board with the logical function of GCUP
has been configured.
10. After a board is started, the counter value for the board is unreliable in the first
measurement period.
11. When an AOUc/FG2c/GOUc/GOUe/EXOUa/FG2d/GOUd board is added to a BSC, the
physical ports for the boards are automatically configured. The total number of ATM logical
ports, IP logical ports, and physical ports configured for a BSC must not exceed 15000.
Parameters
Parameter ID Parameter Name Parameter Description
Impact on Network
Performance: None
BRDCLASS Board Class Meaning: Classes of boards
classified according to
function modules
GUI Value Range: INT,
DPU, GPU, OMU, SAU,
NIU
Unit: None
Actual Value Range: INT,
DPU, GPU, OMU, SAU,
NIU
MML Default Value: None
Recommended Value: None
Parameter Relationship:
None
Service Interrupted After
Modification: No (And no
impact on the UE in idle
mode)
Impact on Network
Performance: None
BRDTYPE Board Type Meaning: Type of the board
GUI Value Range: AOUc,
DPUf, EGPUa, ENIUa,
EOMUa, ESAUa, EXOUa,
EXPUa, FG2c, FG2d,
GOUc, GOUd, GOUe,
POUc, UOIc
Unit: None
Actual Value Range: AOUc,
DPUf, EGPUa, ENIUa,
EOMUa, ESAUa, EXOUa,
EXPUa, FG2c, FG2d,
GOUc, GOUd, GOUe,
POUc, UOIc
MML Default Value: None
Recommended Value: None
Parameter Relationship:
None
Service Interrupted After
Modification: Yes
Impact on Network
Performance: None
LGCAPPTYPE Logical function type Meaning: Logical function
Example
To add a GPU board with the board type of EGPUa and logical type of UCUP in slot 0
of subrack 0, run the following command:
ADD BRD: SRN=0, BRDCLASS=GPU, BRDTYPE=EGPUa, LGCAPPTYPE=UCUP, SN=0;
Function
Use this command to remove a board. This command is used on all types of boards except
the SCUb, GCUa, GCGa, GCUb, GCGb, EGPUa(RMP) and EXPUa(RMP).
Note
1. The board is unavailable after the removal. You must use this command with caution.
2. After a GPU board is removed by running this command, the BSC6910 automatically
adjusts backup resources and enters the internal configuration state. In this case, follow-up
executions of this command can succeed only after the BSC6910 leaves the internal
configuration state.
3. After a board is removed, the counter values for the board are unreliable in the last
measurement period.
4. Before deleting an SAU board, check whether the board to be deleted functions as the SAU
center. If yes, this board cannot be deleted. If you want to delete the board that functions as
the SAU center, run the SET SAUCENTER command to change the board to non-SAU
center, and then delete this board.
5. Disable the BTS local switch before removing a GPU board. Replan the region for the BTS
local switch after the BTS whose GPU board is removed is relocated.
Parameters
Parameter ID Parameter Name Parameter Description
Example
To remove the board in slot 10 of subrack 0 (Subrack No. = 0; Slot No. = 10), run
the following command:
RMV BRD: SRN=0, SN=10;
Function
Use this command to query the information about the OMU.
Note
1. In dual-server mode, the OMU consists of the active and standby nodes. You can use this
command to query the configurations and states of each node, data synchronization
information, and link states.
2. The virtual IP address is the one configured on the active OMU during the installation.
3. When the OMU is installed in single-server mode, the data synchronization status, the
status of the network ,and backup channel are unavailable.
4. The data synchronization status can only be queried only when the standby OMU server
works in stable state.
5. The process of the data synchronization between the active and standby OMUs consists of
two steps:
(1) The standby OMU server synchronizes the initial data of the active OMU server.
(2) The standby OMU server synchronizes the modification of the active OMU server in real
time.
Parameters
None
Example
To query the information about the OMU, run the following command:
DSP OMU:;
%%DSP OMU:;%%
RETCODE = 0 Execution succeeded.
Subrack No. = 0
Slot No. = 27
Computer name = OMU_27
Internal network fixed IP = 172.16.3.60
Other state
-----------
Internal network virtual IP = 172.16.3.40
Internal network virtual IP mask = 255.0.0.0
External network virtual IP = 10.168.172.5
External network virtual IP mask = 255.255.254.0
Internal network virtual IP state = Normal
External network virtual IP state = Normal
Data-sync state = Data synchronization is successful
Internal network link state = Normal
External network link state = Normal
Backup network link state = Normal
(Number of results = 1)
--- END
Output Description
Domain Name Description
If network connections break down, ALM-20702 Active and Standby OMU Communication
Link Failure is generated. Then, you must clear the alarm by referring to the related alarm
handling suggestions.
Function
Use this command to set the security policy of the SAU FTP client.
Note
1. When the encryption mode for transmission is set to AUTO, the FTP client first tries to
connect the FTP server with the encrypted mode. If the connection fails, the plain text mode is
selected.
2. If the state firewall is selected, the FTP client sends the CCC command to the firewall to
switch the transmission mode to the plain text.
3. If the SSL certificate authentication is selected, certificates for the NE should be configured
on the U2000 at first.
Parameters
Parameter ID Parameter Name Parameter Description
Performance: None
ENCRYMODE The Encrypted Mode Meaning: Transport
encryption mode supported
when the NE serves as the
FTP client.
AUTO(Auto): indicates that
the FTP server selects the
encryption mode.
PLAINTEXT(Plain Text):
indicates that the plaintext
mode must be used.
ENCRYPTED(SSL
Encrypted): indicates that
the encrypted mode must be
used.
GUI Value Range:
AUTO(Auto),
PLAINTEXT(Plain Text),
ENCRYPTED(SSL
Encrypted)
Unit: None
Actual Value Range: AUTO,
PLAINTEXT,
ENCRYPTED
MML Default Value: None
Recommended Value:
AUTO(Auto)
Parameter Relationship:
None
Service Interrupted After
Modification: N/A
Impact on Network
Performance: None
SPTSTATEFWL Support State Firewall Meaning: Whether the FTP
client supports the state
firewall.
GUI Value Range: NO(Not
Support), YES(Support)
Unit: None
Actual Value Range: NO,
YES
MML Default Value: None
Recommended Value:
YES(Support)
Parameter Relationship:
None
Service Interrupted After
Modification: No (And no
impact on the UE in idle
mode)
Impact on Network
Performance: None
SSLCERTAUTH Support SSL Certificate Meaning: Whether the FTP
Authentication client supports
authenticating the FTP
server.
GUI Value Range: NO(No),
YES(Yes)
Unit: None
Actual Value Range: YES,
NO
MML Default Value: None
Recommended Value:
NO(No)
Parameter Relationship:
This parameter is valid only
when ENCRYMODE is set
to AUTO,ENCRYPTED.
Service Interrupted After
Modification: No (And no
impact on the UE in idle
mode)
Impact on Network
Performance: None
TRANSMODE FTP Mode Meaning: Choose which
transfer mode for ftp client.
GUI Value Range:
Auto(Auto Mode),
Passive(Passive Mode),
Port(Port Mode)
Unit: None
Actual Value Range: Auto,
Passive, , Port,
MML Default Value: None
Recommended Value:
Auto(Auto Mode)
Parameter Relationship:
None
Service Interrupted After
Modification: No
Impact on Network
Performance: None
STARTPORT Start Data Port Meaning: Start data port
number on the FTP client.
GUI Value Range:
1024~65535
Unit: None
Actual Value Range:
1024~65535
MML Default Value: None
Recommended Value: None
Parameter Relationship: 1.
The start data port must be
smaller than the end data
port. 2. The range between
the start data port and the
end data port must not be
less than 5000.
Service Interrupted After
Modification: No (And no
impact on the UE in idle
mode)
Impact on Network
Performance: N/A
ENDPORT End Data Port Meaning: End data port
number on the FTP client.
GUI Value Range:
1024~65535
Unit: None
Actual Value Range:
1024~65535
MML Default Value: None
Recommended Value: None
Parameter Relationship: 1.
The end data port must be
bigger than the start data
port. 2. The range between
the start data port and the
end data port must not be
less than 5000.
Service Interrupted After
Modification: No (And no
impact on the UE in idle
mode)
Impact on Network
Performance: N/A
Example
1. To set the security policy of the FTP client (The Encrypted Mode = PLAINTEXT;
Support State Firewall = YES), run the following command:
SET SAUFTPSCLT: ENCRYMODE=PLAINTEXT, SPTSTATEFWL=YES;
2. To set the security policy of the FTP client (The Encrypted Mode = ENCRYPTED;
SSLCERTAUTH = YES), run the following command:
SET SAUFTPSCLT: ENCRYMODE=ENCRYPTED, SSLCERTAUTH=YES;
Function
Use this command to query the security policy of the SAU FTP client.
Note
None
Parameters
Parameter ID Parameter Name Parameter Description
Modification: N/A
Impact on Network
Performance: None
Example
%%LST SAUFTPSCLT:SRN=0,SN=23;%%
RETCODE = 0 Execution succeeded.
(Number of results = 1)
--- END
Output Description
Domain Name Description
Function
Use this command to query the setting of the event CHR(Call History Record) process switch
on an application for an RNC.
Note
None
Parameters
Parameter ID Parameter Name Parameter Description
Modification: N/A
Impact on Network
Performance: None
AppType Application Type Meaning: Type of an
application that uses CHRs.
GUI Value Range:
EBC(Event Based Counter),
ECO(eCoordinator),
NASTAR(Nastar),
EMS(EMS)
Unit: None
Actual Value Range: EBC,
ECO, NASTAR, EMS
MML Default Value: None
Recommended Value: None
Parameter Relationship:
NONE
Service Interrupted After
Modification: N/A
Impact on Network
Performance: NONE
LstFormat LstFormat Meaning: When this switch
is set to on, the RNC
performs user data
consistency check after each
procedure. When this switch
is set to off, the RNC does
not perform user data
consistency check after each
procedure.
GUI Value Range:
HORIZONTAL,
VERTICAL
Unit: None
Actual Value Range:
HORIZONTAL,
VERTICAL
MML Default Value:
VERTICAL
Recommended Value: None
Parameter Relationship:
None
Service Interrupted After
Modification: N/A
Impact on Network
Performance: None
Example
To query the setting of the event CHR process switch on the EBC for an RNC, run
the following command:
LST UMMEVENTCHRCTRL: AppType=EBC;
%%LST UMMEVENTCHRCTRL: LogicRncId=3333, AppType=EBC;%%
RETCODE = 0 Execution succeeded.
--- END
5.3.1.1 svc_profile.sh
This section describes the function, directory, and running method of the svc_profile.sh script
of EBC service. Before running commands on the SAU, you must run the svc_profile.sh
script to set the user operating environment.
Script Format
. ./svc_profile.sh
Function
Before running commands on the SAU, you can run the svc_profile.sh script to set the user
operating environment such as the command search path.
Saving Path
This script is saved in the /opt/ebcsau directory.
Authorized Users
User root is authorized to run this script.
Example
Log in to the SAU as an authorized user and run the environment variable script.
# cd /opt/ebcsau
# . ./svc_profile.sh
5.3.1.2 sau4ebc_start
This section describes the command for starting SAU processes.
Command Syntax
sau4ebc_start
Function
1. Application scenario
This command is used for routine maintenance and troubleshooting.
2. Example
This command is used to start SAU processes, including the SAU service processing
processes and board management processes.
Authorized User
This command is executed by user root.
Prerequisites
Before you run this command, ensure that:
The operating system is running properly.
You have set environment variables by running the svc_profile.sh script on the Dopra
Linux operating system.
Application Example
# cd /opt/ebcsau
# . ./svc_profile.sh
# sau4ebc_start
Start SAU processes.
5.3.1.3 sau4ebc_stop
This section describes the command for stopping SAU service processes.
Command Syntax
sau4ebc_stop
Function
1. Application scenario
This command is used for routine maintenance and troubleshooting.
2. Example
This command is used to stop all SAU service processes.
Authorized User
This command is executed by user root.
Prerequisites
Before you run this command, ensure that:
The operating system is running properly.
You have set environment variables by running the svc_profile.sh script on the Dopra
Linux operating system.
Application Example
# cd /opt/ebcsau
# . ./svc_profile.sh
# sau4ebc_stop
Stop all SAU service processes.
If the command output contains All processes have been stopped
successfully!, it indicates that all service processes are stopped. Otherwise, run the
sau4ebc_kill command to forcibly stop the service processes.
5.3.1.4 sau4ebc_kill
This section describes the command for forcibly stopping all SAU service processes.
Command Syntax
sau4ebc_kill
Function
1. Application scenario
You are advised not to forcibly stop SAU service processes. If a process is suspended or
abnormal, you can perform this operation.
2. Example
Forcibly stop all SAU service processes.
Authorized User
This command is executed by user root.
Prerequisites
You have set environment variables by running the svc_profile.sh script on the Dopra Linux
operating system.
Precautions
Normally, you can run the sau4ebc_stop command to stop SAU services.
If you run the sau4ebc_kill command, service data loss or service exceptions may occur.
Therefore, this command is the last resort to forcibly stopping SAU services.
Application Example
# cd /opt/ebcsau
# . ./svc_profile.sh
# sau4ebc_kill
5.3.1.5 sau4ebc_ps
This section describes the command for viewing SAU service process status on the SAU
board.
Command Syntax
sau4ebc_ps
Function
This command is used to check the operating status of all SAU services on the SAU board.
Authorized User
This command is executed by user root.
Prerequisites
You have set environment variables by running the svc_profile.sh script on the Dopra Linux
operating system.
Application Example
# cd /opt/ebcsau
# . ./svc_profile.sh
# sau4ebc_ps
The operating status of all SAU services is displayed as running or not running.
5.3.1.6 sau4ebc_version
This describes the command for viewing the version of the running SAU software.
Command Syntax
sau4ebc_version
Function
This command is used to view the version of the SAU software running on the SAU board.
Authorized User
This command is executed by user root.
Prerequisites
You have set environment variables by running the svc_profile.sh script on the Dopra Linux
operating system.
Application Example
# cd /opt/ebcsau
# . ./svc_profile.sh
# sau4ebc_version
------------------------SAU Server --------------------------
Component Name : EBC SAU Server
Version : xSAUV100R001C00SPC330
InstalledPath : /opt/ebcsau
ReleaseVer : SAU_PARC_X86_32
InternalVersion : Sun Sep 28 14:42:18 CST 2014, revision: 24929
5.3.2.1 svc_profile.sh
This section describes the function, directory, and running method of the svc_profile.sh script
of EMS service. Before running commands on the SAU, you must run the svc_profile.sh
script to set the user operating environment.
Script Format
. ./svc_profile.sh
Function
Before running commands on the SAU, you can run the svc_profile.sh script to set the user
operating environment such as the command search path.
Saving Path
This script is saved in the /opt/emssau directory.
Authorized Users
User root is authorized to run this script.
Example
Log in to the SAU as an authorized user and run the environment variable script.
# cd /opt/emssau
# . ./svc_profile.sh
5.3.2.2 sau4ems_start
This section describes the command for starting SAU processes.
Command Syntax
sau4ems_start
Function
1. Application scenario
This command is used for routine maintenance and troubleshooting.
2. Example
This command is used to start SAU processes, including the SAU service processing
processes and board management processes.
Authorized User
This command is executed by user root.
Prerequisites
Before you run this command, ensure that:
The operating system is running properly.
You have set environment variables by running the svc_profile.sh script on the Dopra
Linux operating system.
Application Example
# cd /opt/emssau
# . ./svc_profile.sh
# sau4ems_start
Start SAU processes.
5.3.2.3 sau4ems_stop
This section describes the command for stopping SAU service processes.
Command Syntax
sau4ems_stop
Function
1. Application scenario
This command is used for routine maintenance and troubleshooting.
2. Example
This command is used to stop all SAU service processes.
Authorized User
This command is executed by user root.
Prerequisites
Before you run this command, ensure that:
The operating system is running properly.
You have set environment variables by running the svc_profile.sh script on the Dopra
Linux operating system.
Application Example
# cd /opt/emssau
# . ./svc_profile.sh
# sau4ems_stop
Stop all SAU service processes.
5.3.2.4 sau4ems_kill
This section describes the command for forcibly stopping all SAU service processes.
Command Syntax
sau4ems_kill
Function
1. Application scenario
You are advised not to forcibly stop SAU service processes. If a process is suspended or
abnormal, you can perform this operation.
2. Example
Forcibly stop all SAU service processes.
Authorized User
This command is executed by user root.
Prerequisites
You have set environment variables by running the svc_profile.sh script on the Dopra Linux
operating system.
Precautions
Normally, you can run the sau4ems_stop command to stop SAU services.
If you run the sau4ems_kill command, service data loss or service exceptions may
occur. Therefore, this command is the last resort to forcibly stopping SAU services.
Application Example
# cd /opt/emssau
# . ./svc_profile.sh
# sau4ems_kill
Forcibly stop all SAU service processes.
5.3.2.5 sau4ems_ps
This section describes the command for viewing SAU service process status on the SAU
board.
Command Syntax
sau4ems_ps
Function
This command is used to check the operating status of all SAU services on the SAU board.
Authorized User
This command is executed by user root.
Prerequisites
You have set environment variables by running the svc_profile.sh script on the Dopra Linux
operating system.
Application Example
# cd /opt/emssau
# . ./svc_profile.sh
# sau4ems_ps
The operating status of all SAU services is displayed as running or not running.
5.3.2.6 sau4ems_version
This section describes the command for viewing the version of the running SAU software.
Command Syntax
sau4ems_version
Function
This command is used to view the version of the SAU software running on the SAU board.
Authorized User
This command is executed by user root.
Prerequisites
You have set environment variables by running the svc_profile.sh script on the Dopra Linux
operating system.
Application Example
# cd /opt/emssau
# . ./svc_profile.sh
# sau4ems_version
------------------------SAU Server --------------------------
Component Name : EMS SAU Server
Version : xSAUV100R001C00SPC330
InstalledPath : /opt/emssau
ReleaseVer : SAU_PARC_X86_32
InternalVersion : Sun Sep 28 14:42:18 CST 2014, Revision: 24929
Attribute
Alarm ID Alarm Severity Alarm Type
Parameters
Name Meaning
Impact on System
When the free space of the logical disk is insufficient, the SAU works abnormally.
System Actions
None
Possible Causes
The free space of the logical disk of the SAU is less than 10%.
Handling Procedure
1. Log in to the SAU, navigate to the installation directory of the SAU, and then run the "du
-m | sort -n | tail" command to list the ten largest directories. Check whether the
following directories are listed.
− /mbsc/bam/common/sau/datafile/bak
− /mbsc/bam/common/fam/famlogfmt
− /mbsc/bam/common/fam/mr
YES=>Delete the files in the following sequence. Ensure that the related data files are
deleted.
a. Delete the files in the /mbsc/bam/common/sau/datafile/bak directory.
b. Delete the files that are modified a long time ago in the
/mbsc/bam/common/fam/famlogfmt directory.
c. Delete the files that are modified one day ago in the /mbsc/bam/common/fam/mr
directory. Go to step 2.
NO=>The ten largest directories do not include the directories that can be deleted. Go to
step 2.
2. Check whether directories that are created by users or files that are backed up by users
exist on the SAU.
YES=>Directories that are created by users or files that are backed up by users exist on
the SAU. Delete these directories or files. Go to step 3.
NO=>Directories that are created by users or files that are backed up by users do not
exist. Contact Huawei customer services center.
3. Wait about 10 minutes and then check whether the alarm is cleared.
YES=>The alarm is cleared. The alarm handling is complete.
Attribute
Alarm ID Alarm Severity Alarm Type
Parameters
Name Meaning
Impact on System
Certain SAU functions are abnormal when the SAU process exits abnormally.
System Actions
The monitoring process automatically starts the process that exits abnormally.
Possible Causes
Errors may occur on the SAU.
Handling Procedure
1. Run the RST SAU command to restart the SAU.After the SAU server is restarted, check
whether the alarm is cleared.
YES=>The alarm is cleared. The alarm handling is complete.
NO=>The alarm persists. Contact Huawei Customer Service Center.
Attribute
Alarm ID Alarm Severity Alarm Type
Parameters
Name Meaning
Impact on System
The SAU can not work normally, the Net Optimize Tool can not get data from SAU.
System Actions
None
Possible Causes
The hard disk of the SAU is faulty.
The array card of the SAU is faulty.
The Ethernet adapter of the SAU is faulty or the Ethernet cable is disconnected.
The operation environment of the SAU is abnormal.
The actual duplex mode of the SAU Ethernet adapter is inconsistent with the expected
duplex mode of the SAU Ethernet adapter.
Get slot No. of SAU failed.
The CPLD self check of SAU error.
The clock self check of SAU error.
Handling Procedure
1. Check the alarm location information.
a. The Ethernet adapter or the Ethernet adapter group is faulty. Go to step 2.
b. The hard disk is faulty. Go to step 3.
c. The Redundant Array of Independent Disks (RAID card) is faulty. Go to step 3.
d. The temperature or voltage is abnormal. Go to step 4.
e. The actual duplex mode of the SAU Ethernet adapter is inconsistent with the
expected duplex mode of the SAU Ethernet adapter. Go to step 5.
f. The slot get failed. Go to step 6.
g. The CPLD self check error. Go to step 3.
h. The clock self check error. Go to step 3.
2. Check the Ethernet adapters of the SAU.
a. Find the fault reasion form "Fault Cause".
b. If the ETH0 netcard or the ETH1 netcard is disconnected, replace or securely insert
the Ethernet cables for the ETH0 netcard or the ETH1 netcard.
c. If the Inner0 netcard or the Inner1 netcard is disconnected, the active and standby
SCU boards in the switching subrack may be faulty. Rectify the fault on the SCU
boards.
d. Wait about 3 minutes, and then check whether the alarm is cleared.
YES=>The alarm is cleared. The alarm handling is complete.
NO=>The alarm persists. Contact Huawei Customer Service Center.
3. Replace the SAU.
a. Replace the faulty SAU. Please refer to 3.3 Replace an SAU Board.
b. Wait about 3 minutes, and then check whether the alarm is cleared.
YES=>The alarm is cleared. The alarm handling is complete.
NO=>The alarm persists. Contact Huawei Customer Service Center.
4. Check the subrack environment.
a. Find the fault reasion form "Fault Cause", whether The value of temperature or
voltage of the SAU equals to zero.
YES=>Remove the SAU board ,then push the SAU board into the subrack.
NO=>The fans in the subrack where the SAU is located may be faulty or the power
supply to the subrack may be faulty. Rectify the fault.
b. Wait about 3 minutes, and then check whether the alarm is cleared.
YES=>The alarm is cleared. The alarm handling is complete.
NO=>The alarm persists. Contact Huawei Customer Service Center.
5. Check the actual duplex mode of the Ethernet adapters.
a. Set both of the duplex mode of the Ethernet adapters of the SAU and of the upper-
layer Router to Mode Full. For details, please refer to 4.1.6 How Can I Set the Link
Mode of the External Ethernet Adapter of the SAU.
b. Wait about 3 minutes, and then check whether the alarm is cleared.
YES=>The alarm is cleared. The alarm handling is complete.
NO=>The alarm persists. Contact Huawei Customer Service Center.
6. Remove the SAU board, then push the SAU board into the subrack.Make sure it is fixed.
Attribute
Alarm ID Alarm Severity Alarm Type
Parameters
Name Meaning
Impact on System
The communication between the OMU and host board is disconnected, and the host board
cannot be managed through the OMU.
System Actions
The host board initiates a reconnection to the OMU automatically.
Possible Causes
The board is faulty or out of position.
The network communication between the OMU and host board is disconnected.
Handling Procedure
1. Check whether the SCU in the switching subrack works normally.
a. Run the DSP BRD command to check whether the SCU in subrack 0 works
normally.
YES=>Normal. Go to step 2.
NO=>Abnormal. Go to step b.
b. Rectify the SCU fault, and then check whether the alarm is cleared.
YES=>The alarm is cleared. The alarm handling is complete.
NO=>The alarm persists. Go to step 2.
2. Check whether the board disconnected from the OMU works normally.
a. Run the DSP BRD command to check whether the board works normally.
YES=>Normal. Contact Huawei Customer Service Center.
NO=>Abnormal. Go to step b.
b. Rectify the board fault, and then check whether the alarm is cleared.
YES=>The alarm is cleared. The alarm handling is complete.
NO=>The alarm persists. Contact Huawei Customer Service Center.
Attribute
Alarm ID Alarm Severity Alarm Type
Parameters
Name Meaning
Name Meaning
Impact on System
This alarm does not affect the connection between the OMU or SAU and the peer end using
an invalid security certificate.
System Actions
The peer-end authentication failure on the OMU or SAU does not affect the connection
between the OMU or SAU and the peer end using an invalid security certificate. If you do not
need to check the certificate revocation list (CRL) for the peer certificate or if you want to
disconnect from the peer end when the peer certificate is invalid, run the SET CRLPOLICY
command to set the CRL policies on the OMU. You do not need to set CRL policies on the
SAU, because the SAU automatically synchronizes CRL policies with the OMU on a daily
basis.
Possible Causes
Cause Possible Causes
Category
Causes Of None
Configuration
Causes Of None
Software
Causes Of None
hardware
Causes Of The security certificate used by the peer end has been revoked, but the
Others existing users still use the certificate.
Remote Handling
Step 1 Check the validity of the peer end.
Check the validity of the peer end If the IP address passes the 1 -
based on the IP address contained validity check, go to Step 2.
in the alarm information. If the IP address fails the validity
check, go to Step 4.
Step 2 Request the operator at the peer end to upgrade the certificate and connect to the OMU again.
Contact the local technical support Collect the fault information and 1 -
center or the local office. send the information to Huawei
technical support.
----End
Attribute
Event ID Event Severity Event Type
Parameters
Name Meaning
Impact on System
The user is notified that the SAU software starts up.
System Actions
None
Possible Causes
Cause Possible Causes
Category
Causes Of None
Configuration
Causes Of The SAU software starts up.
Software
Causes Of None
hardware
Causes Of None
Others
Remote Handling
Step 1 This event is reported as a notification and does not need to be handled.
----End
Attribute
Event ID Event Severity Event Type
Parameters
Name Meaning
Impact on System
The data cannot be uploaded to the server and the upper layer cannot obtain the required data.
System Actions
The current task continuously attempts to connect to the server. If the connection cannot
be recovered before 24:00 on that day, the uploading task is discarded.
After a task is complete on the SAU, the SAU attempts to upload the data of the new
task.
Possible Causes
Cause Possible Causes
Category
Causes Of The IP address and port number of the server are configured incorrectly.
Configuration
Causes Of None
Software
Causes Of None
hardware
Causes Of The network connection of the server is abnormal.
Others The network connection of the SAU is abnormal.
The FTP service on the server is faulty.
Remote Handling
Step 1 Log in to the server, and then run the "ftp localhost" command, check whether the connection
is successful.If yes, go to step 2. If no, start the FTP service on the server, go to step 5.
Step 2 Log in to the SAU, and then run the ping server IP address command, check whether the ping
operation is normal. If yes, go to step 3. If no, check whether the network connection is
normal, go to step 5.
Step 3 Log in to the SAU, and then run the ftp Server IP address Port number command, check
whether the connection is successful. If yes, go to step 4. If no, Contact Huawei Customer
Service Center.
Step 4 Check whether the server IP address and port number configured on the SAU are the same as
the actual server IP address and port number. If yes, Contact Huawei Customer Service
Center. If no, change the configurations to the actual server IP address and port number, go to
step 5.
Step 5 Wait about 10 minutes and then check whether the event alarm is cleared. If yes, the event
handling is complete. If no, Contact Huawei Customer Service Center.
----End
PC name (SAU)
Password of the
administrator (SAU)
Data Sheet of the IP Addresses of the Network Adapter Team of the SAU
Item Configuration Operating Personnel
Information
Configuring the SAUc BIOS Set the first boot device of the SAUc from the USB.
Installing the operating system The default password for user root of the operating
system is 11111111, mbsc@com, or osadmin@123.
The default password for user lgnusr of the
operating system is osnormal@123.
Installing the IPMI driver -
Creating the internal Ethernet The default internal IP address of the SAU is
adapter team 80.168.3.250 before delivery. During the startup of
the SAU, the system calculates a new internal IP
address based on the existing internal network
segment and then changes the internal IP address of
the SAU to the new one.
If the NE version used with the SAU is earlier than
BSC6900
V900R017C00SPC500/BSC6910V100R017C00SP
C500, or SAU version is earlier than
Item Remarks
Configuring the ESAUa BIOS Set the first boot device of the ESAUa from the USB.
Installing the operating system The default password for user root of the operating
system is 11111111, mbsc@com, or osadmin@123.
The default password for user lgnusr of the
operating system is osnormal@123.
Installing the IPMI driver -
Creating the internal Ethernet The default internal IP address of the SAU is
adapter team 80.168.3.250 before delivery. During the startup of
the SAU, the system calculates a new internal IP
address based on the existing internal network
segment and then changes the internal IP address of
the SAU to the new one.
If the NE version used with the SAU is earlier than
BSC6900
V900R017C00SPC500/BSC6910V100R017C00SP
C500, or SAU version is earlier than
V100R001C00SPC330, when the system
automatically calculates the IP address, the existing
internal network segment is not changed, for
example, xxx.yyy of the xxx.yyy.3.250.
Item Remarks
Initial SAU user passwords must be changed and kept with caution to improve system
security.
If you deploy the latest version by upgrading the SAU, the SAU user passwords do not
change after the upgrade.