U2000 Northbound Performance File Interface Developer Guide (NE-Based)
U2000 Northbound Performance File Interface Developer Guide (NE-Based)
V200R015C10
Issue Draft A
Date 2015-01-15
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
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: [email protected]
Scope
This document provides information about the U2000 northbound performance file interface. It
also provides guidance for connecting the network management system (NMS).
This document only describes how to use and configure general functions and does not describe
user-defined functions. If you want to know how to use and configure user-defined functions,
apply for related function documents from Huawei.
Product Versions
The following table lists the product version related to this document.
U2000 V200R015C10
Intended Audience
This document is intended for:
Change History
Draft A (2015-01-15)
This is a draft for V200R015C10. Compared with issue 01 (2014-04-15) of V200R014C00, the
change is:
Organization
1 Overview of Northbound Performance File Interface
This chapter defines the northbound interface and the northbound performance file interface
provided by the U2000.
This chapter describes the process for interconnecting the NMS with the U2000 northbound
performance file interface.
This chapter describes the performance result files that are exported by NE and the parameters
of performance result export services.
The NMS interconnects with the U2000 through the northbound performance file interface. If
a fault occurs when the NMS attempts to obtain performance data, rectify the fault by referring
to the relevant troubleshooting suggestions given in this chapter.
5 Appendix
This chapter provides reference information about the northbound performance file interface.
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Symbol Description
General Conventions
The general conventions that may be found in this document are defined as follows.
Convention Description
Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention Description
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Convention Description
Keyboard Operations
The keyboard operations that may be found in this document are defined as follows.
Format Description
Key Press the key. For example, press Enter and press Tab.
Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl+Alt
+A means the three keys should be pressed concurrently.
Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A means
the two keys should be pressed in turn.
Mouse Operations
The mouse operations that may be found in this document are defined as follows.
Action Description
Click Select and release the primary mouse button without moving
the pointer.
Drag Press and hold the primary mouse button and move the
pointer to a certain position.
Contents
5 Appendix.......................................................................................................................................64
5.1 NEs Supported by Performance File Export................................................................................................................65
5.2 Measurement Attributes of an NE................................................................................................................................69
5.3 Method of Obtaining Performance Counter Files of NEs............................................................................................70
5.4 Method of Transferring Data Using PSFTP.................................................................................................................70
5.5 Checking the Sybase Database Server Name...............................................................................................................70
This chapter defines the northbound interface and the northbound performance file interface
provided by the U2000.
The NMS obtains information about the network elements (NEs) managed by the EMS and
delivers operation commands through the northbound interface. The NE information includes
the alarm, configuration, performance, and inventory data. Figure 1-1 shows the position of the
northbound interface in the network.
In the communication network, the U2000 provides the alarm, configuration, performance, and
inventory data of NEs to the NMS through the northbound interface.
The NMS can use either of the following methods to obtain northbound performance files:
l PULL: The NMS uses SFTP to obtain files from a specified path of the U2000 server.
l PUSH: The U2000 automatically uploads files to a specified path of the NMS.
U2000 northbound file transfer supports the following protocols: SSH-based FTP.SFTP uses
public-key/private-key encryption to encrypt data in the network. Data communication between
two ends can therefore be performed in an encrypted channel.
The U2000 northbound performance file interface uses 3GPP TS 32.435 V7.2.0 specifications.
For details about how to view the specifications and version, see fileFormatVersion
descriptions in Format of Performance Result Export Files.
For details about how to use the northbound performance interface in different networking
modes, see Table 1-1.
U2000 System NMS and U2000 Method for the NMS to Obtain
Type Interconnection Solution Performance Files
Item Value
2 Interconnection Commissioning of
Northbound Performance File Interface
This chapter describes the process for interconnecting the NMS with the U2000 northbound
performance file interface.
2.5 (Optional) Configuring the U2000 for Actively Uploading Files over the Northbound
Interface
The U2000 can actively upload files to the NMS over the northbound interface. You can use
either method to configure the U2000 for actively uploading files to the NMS over the
northbound interface.
This section describes how to simulate the NMS to obtain performance files generated by the
U2000 in SFTP mode using the OSMU. You can determine whether the northbound performance
file interface can be interconnected with the NMS according to the obtained performance files.
Table 2-2 System parameters for SUSE Linux operating system and Oracle database
Table 2-3 System parameters for SUSE Linux operating system and Sybase dabatase
The U2000 serves as FTP user name Provided by the For details, see 2.5.2
an FTP client NMS Configuring the
(PUSH). SFTP for Actively
NOTICE Transferring Files
Using SFTP is over the
recommended Northbound
because of its higher Interface
security than FTP.
(Password
Authentication).
PUSH: the For details, see Step 7 of For details, see 2.5.1 Configuring the SFTP
U2000 2.5.1 Configuring the for Actively Transferring Files over the
automatically SFTP for Actively Northbound Interface (Public and Private
uploads files Transferring Files over Keys) or 2.5.2 Configuring the SFTP for
the Northbound Actively Transferring Files over the
Interface (Public and Northbound Interface (Password
Private Keys). Authentication).
PULL: the If you use FTP to transfer The U2000 uses SFTP to transfer files by
NMS directly files, enable FTP by default.
obtains files referring to the section
"Configuring the FTP
Transmission Policy"
described in the
corresponding U2000
Administrator Guide.
The U2000 does not export user-defined counters on the U2000 client.
File Examples
You can obtain the examples of performance result export files of some common NE types from
the 07.Northbound File\File Interface\Sample File\Performance File (NE-Based)
northbound interface document directory.
Contact Huawei technical support to obtain the examples of performance result export files of
specified NE types.
Context
You can use either of the following methods to modify parameters of performance export
services:
Procedure
l Modifying parameters of performance export services using commands
NOTICE
l In an SLS system, you need to perform the following steps only on the master and slave
servers and do not need to perform them on the standby server.
l In an HA or remote HA system, you need to perform the following steps only on the
active server and do not need to perform them on the standby server.
l In an ATAE cluster online remote HA system, you need to perform the following steps
only on the master and slave servers (include active site and standby site) and do not
need to perform them on the standby server.
-bash-3.00$ . /opt/oss/server/svc_profile.sh
-bash-3.00$ vi /opt/oss/server/etc/MediationService/MedExpParam.xml
4. Press Esc, and then run the :wq! command to save the modification and exit the vi
editor.
5. On the servers on which MediationService is deployed, run the following command
to query the names of the current MediationService:
The following command output is used as an example, the names of the current
MediationService are MediationService0101, MediationService0102, and
MediationService0105.
MediationService0101 [running ]
MediationService0102 [running ]
MediationService0105 [running ]
If the system displays the following information, performance export services are
running properly.
MediationService0101 [running ]
MediationService0102 [running ]
MediationService0105 [running ]
l Modifying parameters of performance export services using the OSMU of the master
server (include the master server of site).
1. Start the Internet Explorer, type http://IP address of the U2000 server:8090 or
https://IP address of the U2000 server:31123 in the Address bar, and then press
Enter.
2. Log in to the OSMU as user ossuser.
3. Click NBI Management in the main window of the OSMU.
4. Choose NBI Management > Centralized Management > Northbound
Configuration Parameters Settings from the navigation tree in the left pane. The
Northbound Configuration Parameters Settings interface is displayed.
5. Select Northbound Performance File Interface (NE-Based) from the Northbound
Interface Name drop-down list.
6. Select MedExpParam.xml - Basic from the Configuration file name drop-down
list, modify parameters of performance export services according to the negotiated
parameters.
For detailed description of the parameters, see 3.2 Configuration File of
Performance Result Export Services.
7. Click Save after the modification is complete.
8. Select MedExpParam.xml - Advanced from the Configuration file name drop-
down list, modify parameters of performance export services according to the
negotiated parameters.
For detailed description of the parameters, see 3.2 Configuration File of
Performance Result Export Services.
9. Click Save&Restart after the modification is complete.
You can view the progress of service restart in the Service Restarted Log area. The
modified parameters take effect after all relevant services are restarted.
----End
Context
l You can use either of the following methods to start performance export:
– Starting performance export using commands
– Starting performance export using the OSMU
l Performance export files can be exported over the northbound interface only after you start
performance export.
l The minimum granularity you can set for performance export is NE type. After you set an
NE type and measurement period, all measurement results of the NE type in the specified
period will be exported over the northbound interface.
l For the AP Manager, you need to start performance export services only on NEs and you
can ignore the following steps performed on the U2000. For details, see the AP Manager
VXXXRXXX Northbound Performance File Interface.
NOTICE
l In an SLS system, you need to perform the following steps only on the master server and
do not need to perform them on the slave or standby server.
l In an HA or remote HA system, you need to perform the following steps only on the active
server and do not need to perform them on the standby server.
l In an ATAE cluster online remote HA system, you need to perform the following steps
only on the master server (include active site and standby site) and do not need to perform
them on the slave or standby server.
Procedure
l Starting performance export using commands
1. Log in to the U2000 server as user ossuser.
2. Start the performance export script.
– On a Sun or ATAE(Sybase) platform, the default installation directory of the
U2000 server is /opt/oss/server, database server name is DBSVR, and user name
is database administrator. The default password is Changeme_123, run the
following commands:
-bash-3.00$ . /opt/oss/server/svc_profile.sh
-bash-3.00$ config_med_export.sh
NOTE
When the Sybase database is used, the user must be database administrator and the default
password is Changeme_123. The default database server name is DBSVR in the U2000 single-
server or HA system and the default database server name is DBSVR1 in the Sun-based SLS
system and ATAE Cluster system. For details about how to query the name of the Sybase
database, see 5.5 Checking the Sybase Database Server Name.
To improve system security, change the default database password upon first login and
periodically change the password. The password change interval can be customized as required.
The system displays the following information:
Please input Database dbServer: DBSVR
Please input Database userName: database administrator
Please input Database password:
Please wait for a second while loading the tool...
Welcome To Med Export Service Configuration Tool
======================================================
Please select an operation type
1--Current Measurement Display
2--New Measurement Set
3--Exit
======================================================
Please select one operation [default is 3] :
NOTICE
The user name of Oracle database is itfndb, and its default password is
Changeme_123.
To improve system security, change the default database password upon first login
and periodically change the password. The password change interval can be
customized as required.
where,
– 1: To view the preset types of NEs to be measured and their measurement periods.
– 2: To set a new measurement.
– 3: To exit.
3. Set operation types according to the actual requirement.
where,
– 1: To view the measurements that can be set currently.
– 2: To set a new measurement.
– 3: To cancel a measurement.
– 4: To return to the main menu.
4. Set a measurement export.
For example, if you want to set the NE type of MSCServer, type MSCServerNE.
You can set only one measurement period at a time. For example, if you want to set
the period to 60 minutes, type 60.
End the settings Type b to return to the previous step. Type 4 to return to the main
menu. Type 3 to exit the performance export script.
l Starting performance export using the OSMU of the master server (include the master
server of active site and standby site)
1. Start the Internet Explorer, type http://IP address of the U2000 server:8090 or
https://IP address of the U2000 server:31123 in the Address bar, and then press
Enter.
2. Log in to the OSMU as user ossuser.
3. Click NBI Management in the main window of the OSMU.
4. Choose NBI Management > Centralized Management > Northbound
Configuration Parameters Settings from the navigation tree in the left pane. The
Northbound Configuration Parameters Settings interface is displayed.
5. Select Northbound Performance File Interface (NE-Based) from the Northbound
Interface Name drop-down list.
6. Select tbl_MedExportMeas from the Configuration file name drop-down list, select
measurement periods for one or more NEs.
7. Click Update Measurements to start performance export.
----End
2.5.1 Configuring the SFTP for Actively Transferring Files over the
Northbound Interface (Public and Private Keys)
When the U2000 server actively uploads files to the NMS over the northbound interface, the
U2000 server functions as an FTP client and the NMS functions as an FTP server. To ensure
data security during file transmission, you can set the SFTP encryption mode. If the U2000 server
is upgraded to V200R015C00 or a Later Version, please reconfigure the SFTP for actively
transferring files over the northbound interface according to this chapter.
Prerequisites
l Use PuTTY to log in to the U2000 server in SSH mode as user ossuser.For an HA system,
you have logged in to the active and standby servers.For a remote HA system, you have
logged in to the active and standby servers.For an SLS system, you have logged in to all
servers. For an advanced telecommunications application environment (ATAE) cluster
system, you have logged in to each server in the U2000 cluster. For an HA system, you
have logged in to the active and standby servers. For an ATAE cluster system, you have
logged in to each server in the U2000. For an HA or remote HA system, you have logged
in to the active and standby servers. For an SLS system, you have logged in to each server.
l You have logged in to the NMS server as user UserA.
UserA is the NMS server user. Replace it as required.
Context
l To set up an SFTP connection using public or private key authentication, save the U2000
server's public key file in the authorized_keys file of the related NMS server user. The
system performs authentication using the U2000 server's private key and the U2000 server's
public key stored on the NMS server. After the authentication is successful, the SFTP
connection is set up successfully. The U2000 server is not required to provide the NMS
login password.
l The public and private key authentication files can be encrypted or not. For encrypted public
and private key authentication files, set the password. If you forget the password, all public
and private key authentication files must be generated again, and the new files will replace
the existing files.
l Unless otherwise specified, perform the following operations on each server:
NOTE
l XFTPService0X01 indicates the XFTP service name of the U2000 server. Replace it as required.
l For a single-server system, the XFTP service name is XFTPService0101.The service is deployed
on the active server. The service name is XFTPService0101.The service is deployed on the active
and standby servers. The service name is XFTPService0101. For an SLS system, the service is
deployed on the master and slave servers. The service name for the master server is
XFTPService0101. The service name for the first slave server is XFTPService0201. The service
name for the second slave server is XFTPService0301. This method applies to the service names
for other servers.For an HA system, the service is deployed on the active server, on which the
service name is XFTPService0101. For an SLS system, the service is deployed on the master and
slave servers. The service name for the master server is XFTPService0101. The service name for
the first slave server is XFTPService0201. The service name for the second slave server is
XFTPService0301. This method applies to the service names of other servers. For an HA system,
the service is deployed on the active server. The service name is XFTPService0101. For a remote
HA system, the service is deployed on the active and standby servers. The service name is
XFTPService0101. For an SLS system, the service is deployed on the master and slave servers.
The service name for the master server is XFTPService0101. The service name for the first slave
server is XFTPService0201. The service name for the second slave server is XFTPService0301.
This method applies to other service names of other servers.For the virtual cluster system, the
service is deployed on the master and slave servers. The service name for the master server is
XFTPService0101. The service name for the first slave server is XFTPService0201. The service
name for the second slave server is XFTPService0301. This method applies to the service names
for other servers.
l When the XFTP service uploads files in FTP mode:
– If the northbound server runs the Linux or Unix operating system, use the vsftpd
software whose version is 2.0.5 or later.
– If the northbound server runs the Windows operating system, use the ftpserver service
delivered with the system.
NOTICE
l In an SLS system, you need to perform the following steps only on the master and slave
servers and do not need to perform them on the standby server.
l In an HA or remote HA system, you need to perform the following steps only on the active
server and do not need to perform them on the standby server.
l In an ATAE cluster online remote HA system, you need to perform the following steps only
on the master and slave servers (include active site and standby site) and do not need to
perform them on the standby server.
Procedure
Step 1 Public and private key files are generated on the U2000.
1. Run the following command on the U2000 server to check whether the .ssh directory exists
in the home directory.
$ cd /export/home/omc/.ssh/
l If No such file or directory is displayed, the .ssh directory is unavailable in the home
directory. Perform Step 1.3 after running the following command:
$ mkdir -p /export/home/omc/.ssh/
$ cd /export/home/omc/.ssh/
l If no command result is displayed, the .ssh directory is available in the home directory.
Perform Step 1.2.
2. Run the following command to check whether the id_rsa_pwd.pub file exists.
$ ls id_rsa_pwd.pub
l If the system displays id_rsa_pwd.pub: No such file or directory, perform Step 1.3
to create a public key file.
l If the system displays id_rsa_pwd.pub, perform Step 2.
3. Run the following command to create encrypted public and private key files.
$ . /opt/oss/server/rancn/bin/ssh-keygen.sh
If the system displays the following message, enter 1 to create encrypted public and private
key files.
------------------------------------------------------------------
Please select an operation type:
1--Generate PubKey File with Encrypt Key.
2--Generate PubKey File without Encrypt Key.
------------------------------------------------------------------
Please make a choice : 1
If the following message is displayed, enter the password twice. When $ is displayed, the
encrypted public key file is generated.
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
NOTICE
l Keep the password for future use. If the password is lost, all public and private key files
must be generated again, and the new files will replace the existing files.
l The password can contain 8 to 30 characters, including lowercase letters a to z,
uppercase letters A to Z, digits 0 to 9, and special characters ]@%-=_.}{. To improve
password security, please use the following password policies:
l The password contains at least one uppercase letter.
l The password contains at least one lowercase letter.
l The password contains at least one digit.
l The password contains at least one special character.
4. Run the following commands to modify permission of the public key file.
$ cd /export/home/omc/.ssh/
$ cd ${HOME}/.ssh/
l If No such file or directory is displayed, the .ssh directory is unavailable in the home
directory. After running the following command, perform Step 1.7.
$ mkdir -p ${HOME}/.ssh/
l If no command output is displayed, the .ssh directory is available in the home directory.
Perform Step 1.6.
NOTE
$ ls id_rsa
l If the system displays id_rsa: No such file or directory, perform Step 1.7 to create
public and private key files.
l If the system displays id_rsa, perform Step 2.
7. Run the following command to create non-encrypted public and private key files.
$ . /opt/oss/server/rancn/bin/ssh-keygen.sh
If the system displays the following message, enter 2 to create non-encrypted public and
private key files.
------------------------------------------------------------------
Please select an operation type:
1--Generate PubKey File with Encrypt Key.
2--Generate PubKey File without Encrypt Key.
------------------------------------------------------------------
Please make a choice : 2
If the system displays information similar to the following, the non-encrypted public key
file has been created successfully:
Generating public/private rsa key pair.
Your identification has been saved in id_rsa.
Your public key has been saved in id_rsa.pub.
8. Run the following commands to modify permission of the public key file.
$ cd /export/home/omc/.ssh/
NOTICE
l For a non-encrypted public key file, copy the id_rsa.pub file's content.
If the id_rsa.pub file does not exist, copy the ${HOME}/.ssh/authorized_keys file's
content on the U2000 server.
l For an encrypted public key file, copy the id_rsa_pwd.pub file's content.
a. Run the cat id_rsa.pub or cat id_rsa_pwd.pub command on the U2000 server. The
content of the id_rsa.pub or id_rsa_pwd.pub file is displayed.
b. Run the vi command on the NMS server to write the content of the id_rsa.pub or
id_rsa_pwd.pub file into the authorized_keys file.
NOTICE
l The content to be written into the authorized_keys file cannot contain any line feed. If
any line feed exists, delete it.
l If the authorized_keys file contains any other data, perform a line feed operation. Then,
write the content.
4. Run the vi command to modify the /etc/ssh/sshd_config file and configure SFTP
parameters on the NMS server.
# su - root
# vi /etc/ssh/sshd_config
Parameter Value
RSAAuthentication yes
PubkeyAuthentica- yes
tion
AuthorizedKeysFile .ssh/authorized_keys
Parameter Value
5. Perform the following operations on the NMS server to check the SFTP service status.
If... Then...
OpenSSH
Portabl
e for
Solaris
If... Then...
Step 3 If you use encrypted public and private key authentication files, perform Step 4. If you use non-
encrypted public and private key authentication files, perform Step 4.
1. Run the following command on the U2000 server to query the password for encrypting the
private key.
$ . /opt/oss/server/svc_profile.sh
$ XFTPPasswdEncrypt
When the following information is displayed, enter the encryption password twice.
Please Enter Password :
Please Re-enter Password :
NOTICE
l The encryption password must be the same as that in Step 1.3.
l Keep the encryption password for future use. If the encryption password is lost, all
public and private key files must be generated again, and the new files will replace the
existing files.
This operation must be performed on each server where the XFTPService0X01 service is
deployed.
$ cd /opt/oss/server/etc/XFTPService
$ vi ModuleParam.xml
Parameter Description
PrivateExKeyFile Set this parameter to the absolute path where the public
key file generated in Step 1.3 is saved, for example, /
export/home/omc/.ssh/id_rsa_pwd.
3. Run the following command to check whether the config file exists:
$ cd ${HOME}/.ssh/
$ ls config
NOTE
l If config:No such file or directory is displayed, the config file does not exist. Perform
Step 3.4 after running the following command:
$ touch ${HOME}/.ssh/config
$ chmod 600 ${HOME}/.ssh/config
l If config is displayed, the config file exists. Proceed to Step 3.4.
4. Run the vi command to add the following contents to the config file:
$ cd ${HOME}/.ssh
$ vi config
IdentityFile /export/home/omc/.ssh/
id_rsa_pwd
IdentityFile ~/.ssh/id_rsa
NOTE
If the config file contains the preceding information, you do not need to modify the config file.
Step 4 Run the Vi command on the U2000 server to change the value of DefaultFTPType in the
ModuleParam.xml file.
This operation must be performed on each server where the XFTPService0X01 service is
deployed.
$ cd /opt/oss/server/etc/XFTPService
$ vi ModuleParam.xml
NOTE
If DefaultFTPType is set to 1, the SFTP encryption mode is used. If DefaultFTPType is set to 0, the
plaintext FTP mode is used.
To change the SFTP encryption mode to the plaintext FTP mode, change the value of DefaultFTPType
to 0 and restart the XFTPService0X01 service.
Using the plaintext FTP mode has security risks, It is recommended that you use the SFTP mode.
<GeneralParams>
…
<param name="DefaultFTPType">1</param>
…
</GeneralParams>
Step 5 Run the following command on the U2000 server to restart the XFTPService0X01 service to
make the modification take effect.
This operation must be performed on each server where the XFTPService0X01 service is
deployed.
$ . /opt/oss/server/svc_profile.sh
You can obtain the service name of XFTPService0X01 for the server on which the current
operation is performed from the command output. XFTPService0X01 is used as an example.
Replace it as required.
Step 6 Run the following command on the U2000 server to view the XFTPService0X01 service status.
This operation must be performed on each server where the XFTPService0X01 service is
deployed.
l If the XFTPService0X01 service is in the running state in the command output, the service
is running properly.
l If the XFTPService0X01 service is in the not running state in the command output, the
service is not started. When this occurs, contact Huawei technical support.
Step 7 Perform the following operations on the U2000 client to configure FTP server information:
1. Log in to the U2000 client.
2. Choose Software > FTP Auto Upload Management > Target Server Settings
(traditional style); alternatively, double-click System Management in Application
Center and choose Settings > FTP Auto Upload Management > Target Server
Settings (application style).
In the Target Server Setting window, the configured FTP server information is displayed.
3. Select an FTP server whose information needs to be configured and click Add.
4. Set the FTP server parameters, as described in Table 2-10.
Parameter Description
Module The module type consists of NBI FM, NBI CM, NBI PM, NBI Inventory,
Type/ CME NBI, CME NCCDM, License Management, NBI Server Backup,
Module NBI Log, EBC Counter, EBC Data, and LTE Trace Data. A module name
Name indicates that the configured FTP server is used to transfer the files
corresponding to the modules in the U2000. For example, if the module
name is northbound alarm, it indicates that the configured FTP server is
used to transfer the files of northbound alarm modules in the U2000
server.
User Name User name that is used to log in to the FTP server.
Confirm Enter the password that is used to log in to the FTP server again.
Password
Server Directory for storing a file after it is transferred to the FTP server.
Directory The directory name cannot contain the following special characters: colon
(:), asterisk (*), question mark (?), quotation mark ("), less than (<),
greater than (>), and vertical bar (|).
NOTE
When you log in to the U2000 server as user ftpuser, ensure that the server directory
starts with "/export/home/sysm", for example, "/export/home/sysm/ftproot".
Parameter Description
Source Directory for storing the LTE Trace Data need to be uploaded.
Directory NOTE
This parameter only can be configured when you modify or add a FTP server whose
Module Name is LTE Trace Data.
The added parameters are saved and displayed in the Target Server Setting window.
6. Choose Software > FTP Auto Upload Management > File Upload Browser (traditional
style); alternatively, double-click System Management in Application Center and choose
Settings > FTP Auto Upload Management > File Upload Browser (application style)
to check the status of the files to be uploaded.
The files to be uploaded and files that fail to be uploaded are displayed in the Upload File
Browser window.
----End
2.5.2 Configuring the SFTP for Actively Transferring Files over the
Northbound Interface (Password Authentication)
When the U2000 server actively uploads files to the NMS over the northbound interface, the
U2000 server functions as an FTP client and the NMS functions as an FTP server. To ensure
data security during file transmission, users can set the SFTP encryption mode.
Prerequisites
l Use PuTTY to log in to the U2000 server in SSH mode as user ossuser. For an HA system,
you have logged in to the active and standby servers.For a remote HA system, you have
logged in to the active and standby servers. For an SLS system, you have logged in to all
servers.For an advanced telecommunications application environment (ATAE) cluster
system, you have logged in to each server in the U2000 cluster.For an HA system, you have
logged in to the active and standby servers. For an ATAE cluster system, you have logged
in to each server in the U2000.For an HA or remote HA system, you have logged in to the
active and standby servers. For an SLS system, you have logged in to each server.
l You have logged in to the NMS server as user UserA.
UserA is an NMS server user. Replace it as required.
Context
l When the password authentication is used, the password for logging in to the NMS server
is required to set up an SFTP connection.
l Unless otherwise specified, perform the following operations on each U2000 server:
NOTE
XFTPService0X01 indicates the XFTP service name of the U2000 server. Replace it as required.
For a single-server system, the XFTP service name is XFTPService0101.The XFTP service is
deployed on the active server, and the service name is XFTPService0101. The XFTP service is
deployed on the active and standby servers, and the service name is XFTPService0101. For an SLS
system, the XFTP service is deployed on the master and slave servers, and the service name for the
master server is XFTPService0101. The service name for the first slave server is XFTPService0201.
The service name for the second slave server is XFTPService0301. This method applies to the service
names for other servers.For an HA system, the XFTP service is deployed on the active server, and
the service name is XFTPService0101. For an SLS system, the XFTP service is deployed on the
master and slave servers, and the service name for the master server is XFTPService0101. The service
name for the first slave server is XFTPService0201. The service name for the second slave server is
XFTPService0301. This method applies to the service names of other servers.For an HA system, the
XFTP service is deployed on the active server, and the service name is XFTPService0101. For a
remote HA system, the XFTP service is deployed on the active and standby servers, and the service
name is XFTPService0101. For an SLS system, the service is deployed on the master and slave
servers, and the service name for the master server is XFTPService0101. The service name for the
first slave server is XFTPService0201. The service name for the second slave server is
XFTPService0301. This method applies to other service names of other servers.
l When the XFTP service uploads files in FTP mode:
– If the northbound server runs the Linux or Unix operating system, use the vsftpd
software whose version is 2.0.5 or later.
– If the northbound server runs the Windows operating system, use the ftpserver service
delivered with the system.
l In an SLS system, you need to perform the following steps only on the master and slave
servers and do not need to perform them on the standby server.
l In an HA or remote HA system, you need to perform the following steps only on the active
server and do not need to perform them on the standby server.
l In an ATAE cluster online remote HA system, you need to perform the following steps
only on the master and slave servers (include active site and standby site) and do not need
to perform them on the standby server.
Procedure
Step 1 Run the vi command to modify the /etc/ssh/sshd_config file and configure SFTP parameters on
the NMS server.
su - root
# vi /etc/ssh/sshd_config
Parameter Value
Parameter Value
Step 2 Perform the following operations on the NMS server to check the SFTP service status.
If... Then...
OpenSSH
Portabl
e for
Solaris
If... Then...
Step 3 Perform the following operations on the U2000 server to change the value of the
DefaultFTPType parameter in the ModuleParam.xml file.
This operation must be performed on each server where the XFTPService0X01 service is
deployed.
$ cd /opt/oss/server/etc/XFTPService
$ vi ModuleParam.xml
NOTE
If DefaultFTPType is set to 1, the SFTP encryption mode is used. If DefaultFTPType is set to 0, the
plaintext FTP mode is used.
To change the SFTP encryption mode to the plaintext FTP mode, change the value of DefaultFTPType
to 0 and restart the XFTPService0X01 service.
<GeneralParams>
…
<param name="DefaultFTPType">1</param>
…
</GeneralParams>
Press Esc and run the :wq command to save the file and exit the vi editor.
Step 4 Run the following command on the U2000 server to restart the XFTPService0X01 service to
make the modification take effect.
This operation must be performed on each server where the XFTPService0X01 service is
deployed.
$ . /opt/oss/server/svc_profile.sh
You can obtain the service name of XFTPService0X01 for the server on which the current
operation is performed from the command output. XFTPService0X01 is used as an example.
Replace it as required.
Step 5 Run the following command on the U2000 server to view the XFTPService0X01 service status.
This operation must be performed on each server where the XFTPService0X01 service is
deployed.
l If the XFTPService0X01 service is in the running state in the command output, the service
is running properly.
l If the XFTPService0X01 service is in the not running state in the command output, the
service is not started. When this occurs, contact Huawei technical support.
Step 6 Perform the following operations on the U2000 client to configure FTP server information:
1. Log in to the U2000 client.
2. Choose Software > FTP Auto Upload Management > Target Server Settings
(traditional style); alternatively, double-click System Management in Application
Center and choose Settings > FTP Auto Upload Management > Target Server
Settings (application style).
In the Target Server Setting window, the configured FTP server information is displayed.
3. Select an FTP server whose information needs to be configured and click Add.
4. Set the FTP server parameters, as described in Table 2-12.
Parameter Description
Module The module type consists of NBI FM, NBI CM, NBI PM, NBI Inventory,
Type/ CME NBI, CME NCCDM, License Management, NBI Server Backup,
Module NBI Log, EBC Counter, EBC Data, and LTE Trace Data. A module name
Name indicates that the configured FTP server is used to transfer the files
corresponding to the modules in the U2000. For example, if the module
name is northbound alarm, it indicates that the configured FTP server is
used to transfer the files of northbound alarm modules in the U2000
server.
User Name User name that is used to log in to the FTP server.
Confirm Enter the password that is used to log in to the FTP server again.
Password
Server Directory for storing a file after it is transferred to the FTP server.
Directory The directory name cannot contain the following special characters: colon
(:), asterisk (*), question mark (?), quotation mark ("), less than (<),
greater than (>), and vertical bar (|).
NOTE
When you log in to the U2000 server as user ftpuser, ensure that the server directory
starts with "/export/home/sysm", for example, "/export/home/sysm/ftproot".
Source Directory for storing the LTE Trace Data need to be uploaded.
Directory NOTE
This parameter only can be configured when you modify or add a FTP server whose
Module Name is LTE Trace Data.
The added parameters are saved and displayed in the Target Server Setting window.
6. Choose Software > FTP Auto Upload Management > File Upload Browser (traditional
style); alternatively, double-click System Management in Application Center and choose
Settings > FTP Auto Upload Management > File Upload Browser (application style)
to check the status of the files to be uploaded.
The files to be uploaded and files that fail to be uploaded are displayed in the Upload File
Browser window.
----End
Context
You can use either of the following methods to stop performance export:
l Stopping performance export using commands
l Stopping performance export using the OSMU
NOTE
This section uses stopping the performance export task of MSCServerNE as an example.
l In an SLS system, you need to perform the following steps only on the master server and do not need
to perform them on the slave or standby server.
l In an HA or remote HA system, you need to perform the following steps only on the active server
and do not need to perform them on the standby server.
l In an ATAE cluster online remote HA system, you need to perform the following steps only on the
master server (include active site and standby site) and do not need to perform them on the slave or
standby server.
Procedure
l Stopping performance export using commands
1. Log in to the U2000 server as user ossuser.
2. Start the performance export script.
– On a Sun or ATAE(Sybase) platform, the default installation directory of the
U2000 server is /opt/oss/server, database server name is DBSVR, and user name
is database administrator. The default password is Changeme_123, run the
following commands:
-bash-3.00$ . /opt/oss/server/svc_profile.sh
-bash-3.00$ config_med_export.sh
NOTE
When the Sybase database is used, the user must be database administrator and the default
password is Changeme_123. The default database server name is DBSVR in the U2000 single-
server or HA system and the default database server name is DBSVR1 in the Sun-based SLS
system and ATAE Cluster system. For details about how to query the name of the Sybase
database, see 5.5 Checking the Sybase Database Server Name.
To improve system security, change the default database password upon first login and
periodically change the password. The password change interval can be customized as required.
The system displays the following information:
Please input Database dbServer: DBSVR
Please input Database userName: database administrator
Please input Database password:
Please wait for a second while loading the tool...
Welcome To Med Export Service Configuration Tool
======================================================
Please select an operation type
NOTICE
The user name of Oracle database is itfndb, and its default password is
Changeme_123.
To improve system security, change the default database password upon first login
and periodically change the password. The password change interval can be
customized as required.
where,
– 1: To view the preset types of NEs to be measured and their measurement periods.
– 2: To set a new measurement.
– 3: To exit.
3. Type 1 to query the current performance measurement export.
======================================================
Please select an operation type
1--Current Measurement Display
2--New Measurement Set
3--Exit
======================================================
Please select one operation [default is 3] :
When the system displays the following information, type MSCServerNE, 60, and
y to cancel the measurement export task.
Deactive Measurements
======================================================
Please input NeTypeName [default or 'b' to exit current menu] :
MSCServerNE
Please input Period (like '60' means 60 minutes period) [default or 'b' to
exit
current menu] : 60
You want deactive MSCServerNE with 60 minutes period, please input 'y' to
confirm, 'n' to ignore : y
Please input NeTypeName [default or 'b' to exit current menu] :
======================================================
Please select an operation type
1--Current Measurement Display
2--New Measurement Set
3--Exit
======================================================
Please select one operation [default is 3] :
1. Start the Internet Explorer, type http://IP address of the U2000 server:8090 or
https://IP address of the U2000 server:31123 in the Address bar, and then press
Enter.
2. Log in to the OSMU as user ossuser.
3. Click NBI Management in the main window of the OSMU.
4. Choose NBI Management > Centralized Management > Northbound
Configuration Parameters Settings from the navigation tree in the left pane. The
Northbound Configuration Parameters Settings interface is displayed.
5. Select Northbound Performance File Interface (NE-Based) from the Northbound
Interface Name drop-down list.
6. Select tbl_MedExportMeas from the Configuration file name drop-down list, clear
the measurement periods of one or more NEs.
7. After the setting is complete, click Update Measurements to stop performance
export.
----End
Context
The NMS can use either of the following methods to obtain northbound performance files:
l PULL: The NMS uses SFTP to obtain files from a specified path of the U2000 server.
l PUSH: The U2000 automatically uploads files to a specified path of the NMS.
NOTE
This section uses the PULL mode as an example. You are required to obtain performance files from a server
deployed with a MediationService service. To check whether a MediationService service is configured on
a server, run the following commands on the server as user ossuser:
$ . /opt/oss/server/svc_profile.sh
$ svc_adm -cmd status | grep MediationService
If the following information is displayed in the command output, the MediationService service has been
configured on the server:
MediationService0101 [running ] //0101 is the number of service,
only for example.
Procedure
Step 1 Start the Internet Explorer, type https://IP address of the U2000 server, and then press
Enter.
Step 4 In the navigation tree in the left pane, choose NBI Management > Category Management >
File Interface > Performance File(NE-Based) Interface to open the Performance File(NE-
Based) Interface page.
Step 5 On the Query Performance Med DataExport Files tab page showing generated performance
files, you can click a file name and open or download it.
Step 6 Check whether the contents of the performance export file have been generated according to the
negotiated parameters. If the file contents are consistent with the negotiated parameters, the file
is correct.
For example, the contents of the performance file A20101231.0145+0800-0200
+0800_LTE_74_003.xml are provided below. This file contains performance results of the NE
LTE_74_003 from 01:45 to 02:00. The file export format, export period, and NE name are
consistent with the preset parameters. The performance export file is therefore correct. For more
example information, see 3.1.1 Examples of Performance Result Export Files.
NOTE
Some messages are displayed in multiple lines due to the large size of contents. In the actual file, these
messages are displayed in one line.
----End
This chapter describes the performance result files that are exported by NE and the parameters
of performance result export services.
File Examples
You can obtain the examples of performance result export files of some common NE types from
the 07.Northbound File\File Interface\Sample File\Performance File (NE-Based)
northbound interface document directory.
Contact Huawei technical support to obtain the examples of performance result export files of
specified NE types.
File Description
When you interconnect the U2000 with the NMS, observe the following aspects:
l Performance counter names may be modified due to spelling mistakes. Therefore, it is
recommended that the NMS use a performance counter ID instead of a performance counter
name to map the value of measTypes. That is, it is recommended that the NMS keep the
default value of CounterMode.
l The counters in an exported file are sorted according to the value of CounterMode in the
configuration file MedExpParam.xml. When you add or cancel a measurement counter,
the absolute location of other counters may therefore be changed. When the NMS parses
a file, do not assume that a counter is fixed to a place. Otherwise, the expected counter may
be inconsistent with the actual one.
l The counter result can be NIL, indicating that a counter has a null or meaningless result.
The possible causes of displaying NIL are: The NE does not report the corresponding
counter result; the counter is a calculation counter and the corresponding formula has 0 as
the divisor.
l yyyymmdd: date for exporting performance result files. The files that are exported on the
same day will be saved to the same directory.
l neName: refers to the name of an NE. This variable for a NodeB is the name of the RNC
managing the NodeB. If the RNC cannot be found, the directory is named default.
NOTE
The Event-Based Counter (EBC) obtains the performance measurement results of eNodeB,
BSC6900UMTS, BSC6900GU, BSC6900UMTS, BSC6900GU, and BTS3900 by collecting statistics
about activated user-defined counters based on the original event data of eNodeB, BSC6900UMTS,
BSC6900GU, BSC6900UMTS, BSC6900GU, and BTS3900. For details about EBC, see the EBC Online
Help.
[<Enddate>] End date of a performance This field is currently not contained in the
measurement period. names of performance export files.
For the measurement of a single period, the
value of [Enddate] and that of
<Startdate> are the same.
results and preset threshold, the results of divided objects are written into the following
divided files: A20101130.0830+0800-0900+0800_bsc01_P001.xml, A20101130.0830
+0800-0900+0800_bsc01_P002.xml, and A20101130.0830+0800-0900
+0800_bsc01_P003.xml.
For details about how to modify a user-defined naming convention, see 2.3 Modifying
Parameters of Performance Export Services.
NodeId ID of an NE. -
NOTICE
NodeId is a customized parameter
and is not used in normal cases.
Before using this parameter,
contact Huawei technical support.
NOTICE
The description of the naming convention is as follows:
l <UniqueId> is mandatory. A user-defined naming convention must contain either
NeName or NeIP.
l A user-defined naming convention does not contain the file name extension. For details
about the naming convention for the file name extension of a retrieved file or divided file,
see 3.1.3 Default Naming Convention of Performance Result Export Files.
l If a file cannot be named on the basis of the previous syntax and rules, the system exports
a performance result file and names it based on the default naming convention.
The performance result export files for the NE RNC123 will be named
PM_RNC123_RNC_20100101.0000+0800-20100101.0030+0800_30.xml.
Format Description
The U2000 supports performance result export files in .xml format. Table 3-3 describes the
parameters of a performance result export file.
Parameter Description
Parameter Description
A measurement object is named in the format of NE name (the first level)/identifier of object
name (the second level):value of object name (the second level)/identifier of object name (the
third level):value of object name (the third level)/identifier of object name (the fourth
level):value of object name (the fourth level)/....
NOTE
Example
The following is an example of a performance result export file:
<?xml version="1.0" encoding="utf-8"?>
<measCollecFile xmlns="http://latest/nmc-omc/cmNrm.doc#measCollec"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://latest/nmc-omc/cmNrm.doc#measCollec schema
\pmResultSchedule.xsd">
<fileHeader fileFormatVersion="32.435 V7.2" vendorName="Huawei">
<fileSender elementType="RNC"/>
<measCollec beginTime="2008-01-12T22:05:00+08:00"/>
</fileHeader>
<measData>
<managedElement userLabel="testRNC"/>
<measInfo measInfoId="67109391">
<granPeriod duration="PT300S" endTime="2008-01-12T22:10:00+08:00"/>
<repPeriod duration="PT300S"/>
<measTypes>67190519 67180678 67180677 </measTypes>
<measValue measObjLdn="testRNC/Cell:Label=CELL100, CellID=100">
<measResults>31 31 31 </measResults>
<suspect>true</suspect>
</measValue>
</measInfo>
</measData>
<fileFooter>
<measCollec endTime="2008-01-12T22:10:00+08:00"/>
</fileFooter>
</measCollecFile>
NOTE
l <suspect>true</suspect> is displayed only when the result is unreliable. If this parameter is not
included in the export file, the result is reliable.
l Some messages are displayed in multiple rows because the file has many contents. In the actual file,
these messages are displayed in one row.
l The coding scheme of Chinese XML files is GBK and that of English XML files is UTF-8.
l In schema\pmResultSchedule.xsd, schema indicates the name of the folder where the
pmResultSchedule.xsd file is located. You need to replace it with the actual one specified by the NMS.
Northbound performance files can be saved compressed or non-compressed. They are saved
compressed by default.
Northbound performance files can be saved on the U2000 for a maximum of seven days. By
default, they are saved for seven days. The U2000 automatically deletes files that expire.
The parameters for the storage specification of northbound performance files are defined in the
configuration file of performance export services. For details, see Parameters for Setting File
Export Specifications.
NOTE
Some messages are displayed in multiple lines due to the large size of contents. In the actual file, these
messages are displayed in one line.
You can modify the parameters of the northbound configuration file either by running commands or by
using the OSMU. For details about the operations performed on the OSMU, see 4.4 How to Set Parameters
in a Northbound Configuration File.
Assume that the installation path of the U2000 server is /opt/oss/server, the example is as
following.
l If you set <NeTypeDir Name="special path for some ne type" NeTypeName="RNCNE|
NodeBNE" Path="wran"/>, performance result files of RNCNE and NodeBNE will be
exported to /opt/oss/server/var/fileint/pmneexport/wran/neexport_yyyymmdd.
l If you set <NeTypeDir Name="special path for some ne type"
NeTypeName="BSC6000NE" Path="gbss"/>, performance result files of BSC6000NE
will be exported to /opt/oss/server/var/fileint/pmneexport/gbss/neexport_yyyymmdd.
If the installation path has been changed during the installation, modify the path to the actual
installation path.
– When the value is set to 1, measurement results of counters (including internal counters
for calculating these counters) that are being measured on the U2000 client will be
exported.
– By default, the northbound interface updates measurement information of counters
every 24 hours. The measurement results of newly-measured counters can be exported
to result files only after the northbound interface updates measurement information.
MeasInfoUpdateSpanMins (optional): specifies the period (in minutes) for the
northbound interface to synchronize the measuring counter information with the U2000
client. This parameter is valid only when CounterFilterMode is set to 1. The default
value is 1440. You are advised to retain the default value.
l StrSeparator: specifies the separators between counter names and the string format in a
performance result export file.
The default value is a space. If a counter name contains a space, use a semicolon (;) instead
of a space as the separator. You can use a space to separate counter IDs.
NOTICE
For an LTE network configured with 2000 equivalent NEs, if the 15–minute measurement
period is in use, the total size of result files exported in a day may reach 3 GB. In this case,
you are advised to set FileSaveDay to 3.
l DelDelayTime: specifies the delay (in minutes) between the timer for automatic deletion
of expired result files and 00:00:00 every day. The default value is 30, which indicates that
the system automatically deletes expired result files at 00:30:00 every day.
l IsGZip: specifies whether to compress the exported result files. The default value is 1.
– When value is set to 0, the system will not compress the exported result files.
– When value is set to 1, the system will compress the exported result files using the
UNIX standard to generate files in GZ format.
The NMS interconnects with the U2000 through the northbound performance file interface. If
a fault occurs when the NMS attempts to obtain performance data, rectify the fault by referring
to the relevant troubleshooting suggestions given in this chapter.
Common Troubleshooting
For details about how to rectify common faults that may occur when the NMS attempts to obtain
performance data, see Table 4-1.
No performance file is exported. For details, see 4.2 Troubleshooting Performance File
Export Failure.
Information Collection
If an unusual fault occurs when the NMS attempts to obtain performance data, collect relevant
information to help Huawei technical support personnel locate the fault. For details about how
to collect fault information, see Table 4-2.
Operation information Record the operations performed before a fault occurs and the
troubleshooting measures taken later.
Description
No performance file exists in the export path. The NMS therefore fails to obtain performance
data of NEs.
Troubleshooting
One of the following three causes can result in performance file export failure:
l The performance export service is not started.
l NEs are disconnected.
l Free disk space on the U2000 server is insufficient.
-bash-3.00$ . ./svc_profile.sh
-bash-3.00$ svc_adm -cmd status | grep MediationService
If the system displays the following information, the service is started:
MediationService0101 [running ]
3. If the service is not started, run the following command to start it (For example,
MediationService0101). You must start all MediationService[xxxx] services on the server.
-bash-3.00$ svc_adm -cmd startsvc MediationService0101
NOTICE
Confirm the files can be deleted before clearing the disk space. Deleting a file by mistake can
result in incorrect system operation. You are advised to clear the disk space by referring to the
Administrator Guide of the corresponding U2000 networking mode.
Solution
Contact Huawei technical support.
Prerequisites
You have logged in to the master OSMU server (include the master server of active site and
standby site) as user ossuser. OSMU address: https://U2000 master server IP:31123/
Procedure
Step 1 Click NBI Management on the main page of the OSMU.
Step 2 In the navigation tree of the left pane, choose NBI Management > Centralized
Management > Northbound Interface Compatibility Settings. The Northbound Interface
Compatibility Settings tab page is displayed.
Step 3 View the current FDN format and OMC ID of each northbound interface.
Step 4 Set the FDN format and OMC ID for each northbound interface based on telecom operators'
requirements.
NOTE
You can reset the FDN format, OMC ID, and SRAN northbound interface only after you have negotiated
with telecom operators.
Step 5 Select The northbound interface change has been discussed with the customer. The
customer demands the above settings.
The system displays a message stating that some services will restart for the settings to take
effect.
Step 7 Click Yes to confirm the settings and restart the related services. Click No to cancel the settings.
----End
Follow-up Procedure
If the system displays a message stating that the related services fail to restart, these services do
not exist or there are other services being restarted. When this occurs, log in to the U2000 server
to install or manually restart the related services.
Prerequisites
You have logged in to the master OSMU server (include the master server of active site and
standby site) as user ossuser. OSMU address: https://U2000 master server IP:31123/
Context
For details about the configuration file of each northbound interface, see the related developer
guide.
Only the northbound performance file interface (NE-based) involves parameter reconfiguration
for slave servers. However, when you modify parameters through the OSMU, you need to modify
them only on the master server, and the slave server automatically synchronizes the
modifications.
Procedure
Step 1 Click NBI Management on the main page of the OSMU.
Step 2 Choose NBI Management > Centralized Management > Northbound Configuration
Parameters Settings. The Northbound Configuration Parameters Settings page is displayed.
Step 3 Select a northbound interface and its configuration file. Then set new values to parameters to be
modified in the configuration file.
NOTE
l If an interface is not installed, its configuration file cannot be modified. If you select an interface that
is not installed, a message is displayed, indicating that the interface is not installed and you can modify
its configuration file only after installation.
l You can click Reset to restore the modified parameters to their previous values.
l The modifications of parameters marked with * take effect only after you restart related services.
l Parameter validity check will check the validity of parameter values. For details about parameter value
ranges, see the parameter description in the related interface developer guide.
----End
5 Appendix
This chapter provides reference information about the northbound performance file interface.
A l AAANE
l AIMNE
l AP ManagerNE
l ATSNE
l AGCFNE
l AAAOMDNE
l AAABMPNE
l ASNGWNE
B l BSC6000NE
l BSCNE
l BSC6900GUNE
l BSC6900GSMNE
l BSC6900UMTSNE
l BSC6000GSMRNE
l BSC6000(R11+)NE
l BSC6810(R11+)NE
l BWANE
l BSC6910GUNE
l BSC6910GSMNE
l BSC6910UMTSNE
l BTS3900NE
C l CAS9910NE
l CHLR9820NE
l CGNE
l CBSCNE
l CHLR-DCNE
l CHLR-SCNE
l CMGWNE
l CMSCNE
l CSCFNE
l CT800GLMSNE
l CGPOMUNE
l CCFNE
l CX600NE
D l DNS9816NE
l DNSNE
l DOPRANE
E l eNodeBNE
l eRelayNE
l ECO6910NE
l EERNE
l EIRNE
l ENSNE
l ETASNE
l EudemonNE
l ENUMNE
F l FIXMGWNE
l FMCMGWNE
G l GGSN80NE
l GLMSNE
l GMSNE
l GT800BSCNE
l GTASNE
l GUEIRNE
l GUHLRNE
H l HANE
l HLR36NE
l HLR-DCNE
l HLRNE
l HLR-SCNE
l Horizon2GBSCNE
l Horizon3GRNCNE
l HRC-BSCNE
l HSSNE
l HSS9860NE
I l ICSNE
l iMSCNE
l IPCTRXNE
M l M800MSCNE
l MediationNE
l MediaX3600NE
l MGWNE
l MiniMGWNE
l MMENE
l MRFNE
l MRFPNE
l MRS6100NE
l MSCeNE
l MSCNE
l MSCServerNE
l MAG9811
l MICRO BTS3900
l MEDIAXNE
l MRP6600NE
l MRFCNE
l M-EIRNE
N NodeBNE
P l pBTS3701NE
l PCU33NE
l PCUNE
l PDSNNE
l PDSNR01NE
l PGMNE
l POCNE
R l RACNE
l RCCNE
l RIMNE
l rMSCNE
l rMSCSvrNE
l RNCNE
l RouterNE
l RTNNE
l RMNE
l RCS9880NE
l RCS9880BMPNE
l RADIUSProxyNE
S l SAEGWNE
l SAE-HSSNE
l SBCNE
l SDCNE
l SE2600NE
l SG7000NE
l SGSNNE
l SHLRNE
l SIGNE
l SOFTX3000NE
l SPSNE
l SVNNE
l SwitchNE
l SE2900NE
l SPSV3NE
l SIGServerNE
T l TDNodeBNE
l TD-RNCNE
l TGW1000NE
l tMSCNE
l tMSCSvrNE
l TSCNE
l ThirdPartyServerNE
U l UAGNE
l UANE
l UEIRNE
l UGCNE
l UGWNE
l UNPNE
l UPCCNE
l USCDBNE
l USNNE
l USU3900NE
l USU3910NE
l UIMNE
l UPANE
l UGW9500NE
l UPortalNE
V ViewPointNE
Not report by all counters: An NE reports only measurement results of counters that are set
to be measured on the U2000 client.
For details about the measurement attributes of an NE, see the Performance Counter
List.xls:
l Check the Measured Feature row in the About This Document sheet.
l Check the Default Measured(Yes/No) column in the Counters sheet.
NOTE
If a performance counter file does not contain the Measured Feature and Default Measured(Yes/No)
information, contact Huawei technical support.
Procedure
Step 1 Huawei technical support engineer download the PSFTP client to a local PC from Software at
http://support.huawei.com.
Step 2 Double-click psftp.exe to start the PSFTP client.
Step 3 Run the following command to connect the target server:
psftp> open IP address of the target server
Step 4 Type the FTP user name and password.
----End
Prerequisites
You have contacted Huawei technical support engineers to obtain PuTTY.zip at http://
support.huawei.com and decompressed it to your PC.Huawei technical support engineers can
quickly search for the tool package using its name as the keyword after clicking Search by
Category > Tools at http://support.huawei.com.
Procedure
Step 1 Use PuTTY to log in to the U2000 DB active node in SSH mode as user dbuser.
Step 2 Run the following command to view the name of the Sybase server:
In the following command output, the name of the database server is DBSVR1:
DBSVR1
----End