Professional Documents
Culture Documents
Northbound Inventory File Interface Developer Guide: U2000 V200R016C10
Northbound Inventory File Interface Developer Guide: U2000 V200R016C10
Northbound Inventory File Interface Developer Guide: U2000 V200R016C10
V200R016C10
Issue 02
Date 2016-03-20
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: support@huawei.com
Scope
This document provides the information about U2000 Northbound inventory file interface.
The document also provides the operation guide for connecting the 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 V200R016C10
Intended Audience
This document is intended for:
Change History
02 (2016-03-20)
This is 02 version for V200R016C10. Compared with issue 01 (2016-02-25) of
V200R016C10, no change.
01 (2016-02-25)
This is 01 version for V200R016C10. Compared with issue Draft A (2015-12-30) of
V200R016C10, no change.
Draft A (2015-12-30)
This is a draft for V200R016C10. Compared with issue 01 (2015-09-20) of V200R016C00,
the change is:
Organization
1 Introduction to Northbound Inventory File Interface
This introduces the definition of the northbound interface and the northbound inventory file
interface provided by the U2000.
Before interconnecting the NMS and the U2000, you need to conduct an interconnection
commissioning. Based on the commissioning result, determine whether the northbound
inventory file interface meets the conditions for interconnecting with the NMS
The NMS interconnects with the U2000 through the northbound inventory file interface. If a
fault occurs when the NMS is obtaining inventory data, rectify the fault by referring to this
part.
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
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
Drag Press and hold the primary mouse button and move the
pointer to a certain position.
Contents
This introduces the definition of the northbound interface and the northbound inventory file
interface provided by the U2000.
In the communication network, the U2000 provides the alarm, configuration, performance,
and inventory data of NEs to the NMS through the northbound interface.
ATAE cluster online Perform interconnection on the Obtain inventory files on the
remote HA system master servers of the active and master servers of the active and
standby U2000 sites. standby U2000 sites.
If the Site Power Management component has been deployed, interconnect the component
with the northbound energy saving service in U2000 Site Power Management Northbound
Inventory File Interface Developer Guide.
Before interconnecting the NMS and the U2000, you need to conduct an interconnection
commissioning. Based on the commissioning result, determine whether the northbound
inventory file interface meets the conditions for interconnecting with the NMS
Context
NOTICE
The interconnection commissioning of the northbound inventory file interface does not rely
on the MOC or attribute order in the exported inventory file.
NOTICE
Using SFTP is recommended because of its higher security than FTP.
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 The U2000 uses SFTP to transfer files by
NMS directly transfer files, enable FTP default.
obtains files by referring to the
section "Configuring the
FTP Transmission
Policy" described in the
corresponding U2000
Administrator Guide.
Prerequisites
You have logged in to the U2000 server as user ossuser.
Context
The inventory export configuration file is saved in the /opt/oss/server/etc/CMServer/
Inventory/InvtExportPara.xml folder. To customize the naming convention of exported
inventory management files or set whether to record the collection time of inventory files, you
have to modify the configuration file. Currently, only NE-based inventory management file
export supports collection time recording. MOC-based export does not support this function.
Perform the following steps on the server where CMServer is deployed, run the following
command to query CMServer:
> . /opt/oss/server/svc_profile.sh
> svc_adm -cmd status | grep CMServer
The following information means CMServer is deployed on the server:
CMServer [running ]
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.7 How to Set Parameters in a Northbound Configuration File.
Procedure
Step 1 Run the following command to open the configuration file InvtExportPara.xml:
$ vi /opt/oss/server/etc/CMServer/Inventory/InvtExportPara.xml
NOTE
By default, the switch is enabled for a newly installed V200R013 and later versions, and is disabled for
V200R013 and later versions after an upgrade.
Step 3 Press Esc and run the :wq! command to save the modification and exit the vi editor.
Step 4 Run the following command to restart the CMServer service:
$ . /opt/oss/server/svc_profile.sh
$ svc_adm -cmd restartsvc CMServer
----End
Procedure
Step 1 Choose Maintenance > Task Management (traditional style); alternatively, double-click
System Management in Application Center and choose Task Schedule > Task
Management (application style). The Task Management window is displayed.
Step 2 Choose File Interface > Inventory Data Export from the navigation tree in the left pane.
The task records are displayed.
Step 3 Double-click the task record to open the Attribute dialog box. Set relevant parameters by
referring to Table 2-3.
----End
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.
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. 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.
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.
l In an HA or remote HA system, you need to perform the following steps only on the active
server.
l In an ATAE cluster online remote HA system, you need to perform the following steps on
the master server at both active site and standby sites. In a VM cluster system, you need to
perform the following steps on the master server at the active site.
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/
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
– 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.
– 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:
n The password contains at least one uppercase letter.
n The password contains at least one lowercase letter.
n The password contains at least one digit.
n 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/
– If the system displays id_rsa: No such file or directory, perform Step 1.7 to create
public and private key files.
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 ${HOME}/.ssh/
NOTICE
– 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.
– 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
– The content to be written into the authorized_keys file cannot contain any line feed.
If any line feed exists, delete it.
– 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
Password: Password of user root
# vi /etc/ssh/sshd_config
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
– The encryption password must be the same as that in Step 1.3.
– 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.
$ vi ModuleParam.xml
3. Run the following command to check whether the config file exists:
$ cd ${HOME}/.ssh/
– If No such file or directory is displayed, the .ssh directory is unavailable in the
home directory. After running the following command. Perform the following steps.
$ mkdir -p ${HOME}/.ssh/
– If no command output is displayed, the .ssh directory is available in the home
directory. Perform the following steps.
$ ls config
NOTE
$ 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.
$ svc_adm -cmd status | grep XFTP
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-6.
Module The module type consists of NBI FM, NBI CM, NBI PM, NBI
Type/ Inventory, CME NBI, CME NCCDM, License Management, NBI
Module Server Backup, NBI Log, EBC Counter, EBC Data, and LTE Trace
Name Data. A module 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.
Confirm Enter the password again that is used to log in to the FTP server.
Password
Parameter Description
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.
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.
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. 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.
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.
l In an HA or remote HA system, you need to perform the following steps only on the active
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).
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-8.
Module The module type consists of NBI FM, NBI CM, NBI PM, NBI
Type/ Inventory, CME NBI, CME NCCDM, License Management, NBI
Module Server Backup, NBI Log, EBC Counter, EBC Data, and LTE Trace
Name Data. A module 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.
Confirm Enter the password again that is used to log in to the FTP server.
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.
----End
Prerequisites
l You have logged in to the U2000 client.
l You are authorized to perform inventory management.
Procedure
Step 1 Choose Configuration > Inventory Management (traditional style); alternatively, double-
click Trace and Maintenance in Application Center and choose Monitor > Inventory
Management (application style) . The Inventory Management window is displayed.
Step 2 Perform relevant operations according to the data to be exported.
Inventory data of all MOs of an Right-click the NE node, and then choose Export >
NE Export All from the shortcut menu.
Inventory data of all the Right-click the NE node, and then choose Export >
external data of an NE Export External Data from the shortcut menu.
NOTE
External data refers to the inventory data of special components
that is unable to be reported.
Inventory data of an MO of an Right-click the MO node, and then choose Export from
NE the shortcut menu.
Step 3 Set the file name, save path, and save type of the file in the Save dialog box.
Step 4 Click Save to finish the automatic export configuration.
Step 5 Click Close to close the Message dialog box.
----End
Context
The NMS can use either of the following methods to obtain inventory files:
l The NMS uses the SFTP to obtain inventory files from the specified path on the U2000
server.
l The U2000 uploads inventory files to the NMS.
NOTE
This part takes the first method as an example.
l In an SLS system, you need to perform the following steps only on the master server.
l In an HA or remote HA system, you need to perform the following steps only on the
active server.
l In an ATAE cluster online remote HA system, you need to perform the following steps
on the master server at both active site and standby sites. In a VM cluster system, you
need to perform the following steps on the master server at the active site.
Procedure
Step 1 Start the Internet Explorer, type https://IP address of the U2000 server:31123, and then
press Enter.
Step 2 Log in to the OSMU as user ossuser.
Step 4 In the navigation tree in the left pane, choose NBI Management > Category Management >
File Interface > Inventory File Interface to open the Inventory File Interface page.
Step 5 On the Query Inventory Auto DataExport Files tab page showing generated inventory files,
you can click a file name and open or download it.
Step 6 Check the downloaded inventory file, if the inventory file is generated according to the
negotiated parameters, you can infer that the northbound inventory file interface meets the
interconnection conditions.
The example of inventory file as following:
<?xml version="1.0" encoding="UTF-8"?>
<DATAPACKET>
<NE NEFdn="NE=256" NEName="10.145.18.23" NEType="BSC6900GSM" />
<TABLES>
<TABLE attrname="Cabinet">
<ROWDATA>
<ROW CabinetNo="2" InventoryUnitId="2" RackType="LOCAL"
InventoryUnitType="Hardware" VendorUnitFamilyType="Rack"
VendorUnitTypeNumber="0" VendorName="Huawei" SerialNumber=""
HardwareVersion="" DateOfManufacture="" DateOfLastService=""
UnitPosition="CabinetNo=2" ManufacturerData="" UserLabel=""
BOMCode="" IssueNumber="" BOMRackType="" CLEICode="" BOM="" />
<ROW CabinetNo="0" InventoryUnitId="0" RackType="LOCAL"
InventoryUnitType="Hardware" VendorUnitFamilyType="Rack"
VendorUnitTypeNumber="0" VendorName="Huawei" SerialNumber=""
HardwareVersion="" DateOfManufacture="" DateOfLastService=""
UnitPosition="CabinetNo=0" ManufacturerData="" UserLabel=""
BOMCode="" IssueNumber="" BOMRackType="" CLEICode="" BOM="" />
</ROWDATA>
</TABLE>
<TABLE attrname="Subrack">
<ROWDATA>
<ROW CabinetNo="0" SubrackNo="0" InventoryUnitId="0" FrameType="MPS"
RackFrameNo="0" ModuleNo="-1" InventoryUnitType="Hardware"
VendorUnitFamilyType="Frame" VendorUnitTypeNumber="0"
VendorName="Huawei" SerialNumber="" HardwareVersion=""
DateOfManufacture="" DateOfLastService=""
UnitPosition="CabinetNo=0,SubrackNo=0" ManufacturerData=""
----End
Supported NE Types
The inventory management feature allows users to export inventory data of NE types
described in Table 1. For the description of specific inventory attributes, see the Inventory
Types of NEs.xls delivered with this release.
SAEGW yes
CGPOMU yes
UAG yes
ICS yes
BSC yes
PCU yes
HLR yes
GGSN80 yes
SGSN yes
MGW yes
BSC6000 yes
RNC yes
eNodeB yes
BSC6900GSM yes
BSC6900UMTS yes
BSC6900GU yes
NodeB yes
MBTS yes
CBSC yes
BSC6910GSM yes
BSC6910UMTS yes
BSC6910GU yes
BTS3900 yes
ECO6910 yes
DBS3900IBS yes
MiniMGW yes
MSCe yes
SAE-HSS yes
SBC yes
SE2600 yes
SG7000 yes
SOFTX3000 yes
UPCC yes
ViewPoint yes
HA yes
SPS yes
CHLR9820 yes
FIXMGW yes
FMCMGW yes
CAS9910 yes
eRelay yes
USU3900 yes
USU3910 yes
HSS9860 yes
SPSV3 yes
GUHLR yes
USCDB yes
SE2900 yes
CSCF yes
ATS yes
SVA-AC yes
SVA-AG yes
SVA-AE yes
MSP yes
SVA3100 yes
SVA3200 yes
WSE3100 yes
VCMC yes
vUSN yes
vUGW yes
vEPSN yes
vUIC yes
vePDG yes
vCG yes
The inventory management files are exported by NE or MOC on a scheduled basis. When the
files are exported by NE, they can be saved in XML, CSV, or TXT format; when the files are
exported by MOC, they can be saved in XML or CSV format.
The inventory management files to be exported at the scheduled time are saved in
the /opt/oss/server/var/fileint/cm/InvtTimerExport directory on the U2000 server.
1. Predefined rule
Modify the parameter configuration file /opt/oss/server/etc/CMServer/Inventory/
InvtExportPara.xml by referring to the operations to in and add the following rule:
<FileNameRule Name="IM Export File naming rule"
Value="[IM]_[ExportTime]_[NeName]-[NeIP]-[NodeId].exp1234"/>
After the modification is complete, restart the CMServer service to make the
configuration file take effect.
2. Conventions and remarks
a. Variables in the brackets ([ ]) are system built-in variables and cannot be changed at
will. However, you can set them to an empty value.
b. NeName and NeIP indicate the NE name and the NE IP address. The file name
contains at least one UniqueId field to differentiate file names of different NEs.
NeIP is inapplicable to separate-MPT base station or BSC6000 site.
c. Letters and digits can be placed anywhere in the file name according to the naming
convention. However, when letters and digits are placed next to a variable in the
brackets ([ ]), an underscore (_), hyphen (-), or dot (.) must be used between them.
In addition, the underscore (_), hyphen (-), or dot (.) cannot at the beginning or end
of the file name.
d. ExportTime indicates the time for exporting an inventory management file.
The time format is YYYYMMDDHH. For example, 2009121814.
e. NeType indicates the NE type such as BTS3900 WCDMA and BTS3900 LTE. The
exported value of this field for BSC6000 site is BTS.
f. NodeId indicates the ID of an NE. You type the ID when creating the NE. This
field is inapplicable to separate-MPT base station or BSC6000 site.
NOTICE
NodeId is a customized parameter and is not used in normal cases. Before using this
parameter, contact Huawei technical support.
g. If you configure the attribute PRNCN/ PRNCId for a NodeB, PRNCN indicates
the name of the RNC that controls the NodeB and PRNCId indicates the ID of the
RNC. This field is inapplicable to other NEs.
h. The naming convention does not include the file name extension. For details about
how to configure the file name extension, see the default naming convention.
i. You can modify the custom naming convention in a configuration file stored on the
server and restart CMServer for the modification to take effect. Generally, you are
not advised to modify the custom naming convention.
j. If the rules are not defined according to the syntax and conventions, the exported
file is named based on the default naming convention.
3. Example
If the custom naming convention is abc123_[IM]_336-[ExportTime]_[NeName]-[NeIP]-
[NodeId].exp1234.
The exported file of the NE RNC123 is named
abc123_IM_336-2011101208_RNC123-10.145.22.103-.exp1234.xml.
NOTE
The naming convention of the inventory association relationship file of an separate-MPT base
station is restricted by the custom naming convention. The custom naming convention of the
inventory association relationship file of an separate-MPT base station is CIM_NE
type_[controller name_]NE name.file format. [controller name_] is available only when the NE
type is TDNodeBNE.
The name of the file exported by MOC cannot be customized, and therefore the predefined rule do
not take effect.
l Example
If the NE type is eNodeB, NE name is 211, and file format is csv, the name of the
exported file is as follows:
AIM_eNodeB_211.csv. If the NE is part of a separate-MPT base station, the
CIM_eNodeB_211.csv file is also exported.
NOTE
When the FDN format is set to FDN dotted format on the Northbound Interface Compatibility
Settings tab page, the inventory management export files are named in the following format:
W_OMC_NE type_NE FDN_NE name.file format. For a single sub-NE of a separate-MPT base
station, you can also export the association relationship file, which is named in the following format:
W_OMC_NE_type_RELETION_NE name.file format.
The NE FDN uniquely identifies an NE in the U2000 system.
<NE> Records the basic information about an NE, including NEFdn, NEName,
and NEType.
If SyncTimeLatest, switch for recording collection time, in the
configuration file InvtExportPara.xml is set to true (collection time will
be recorded), the SyncTimeLatest attribute (used for recording the
collection time of NE inventory data) is available.
<TABLES> Contains one or more TABLE flags and does not have any attribute.
<TABLE> Contains information about inventory types and has an attrname attribute
that specifies the current inventory type.
The inventory types may be changed based on the U2000 or NE versions.
Therefore, you are advised to make the NMS ignore unnecessary
inventory types on the U2000, which has no impact on system operations.
The location of a specified inventory type in the file may also be changed
based on the version changes. Therefore, you need to make the NMS
identify an inventory type based on the properties of the inventory type
when the NMS parses the file.
<ROWDATA Contains one or more records of the current inventory type. The records
> are separated by the ROW flags.
<ROW> Contains one record. The attribute of this flag is the attribute name and
value of each record. For details about the attribute names, see the
Inventory Types of NEs.xls.
The inventory types may be changed based on the U2000 or NE versions.
Therefore, you are advised to make the NMS ignore unnecessary
inventory types on the U2000, which has no impact on system operations.
The location of a specified inventory type in the file may also be changed
based on the version changes. Therefore, you need to make the NMS
identify an inventory type based on the properties of the inventory type
when the NMS parses the file.
The following uses the inventory management export file for BSC6900GSM as an example:
<?xml version="1.0" encoding="UTF-8"?>
<DATAPACKET>
<NE NEFdn="NE=256" NEName="10.145.18.23" NEType="BSC6900GSM" />
<TABLES>
<TABLE attrname="Cabinet">
<ROWDATA>
<ROW CabinetNo="2" InventoryUnitId="2" RackType="LOCAL"
InventoryUnitType="Hardware" VendorUnitFamilyType="Rack"
VendorUnitTypeNumber="0" VendorName="Huawei" SerialNumber=""
HardwareVersion="" DateOfManufacture="" DateOfLastService=""
UnitPosition="CabinetNo=2" ManufacturerData="" UserLabel=""
BOMCode="" IssueNumber="" BOMRackType="" CLEICode="" BOM="" />
<ROW CabinetNo="0" InventoryUnitId="0" RackType="LOCAL"
InventoryUnitType="Hardware" VendorUnitFamilyType="Rack"
<ROWDATA>
<ROW SiteIndex="1" SiteName="BTS_hbz" SiteType="BTS3900AL_GSM" />
<ROW SiteIndex="2" SiteName="BTS3900_TDM_XUEWEIWEI"
SiteType="BTS3900_GSM" />
<ROW SiteIndex="108" SiteName="BTS3900_108_TDM_ZhouZhenguo"
SiteType="BTS3900_GSM" />
</ROWDATA>
</TABLE>
</TABLES>
</DATAPACKET>
NOTE
l For details about the inventory files for MBTS, see the Inventory Types of NEs.xls.
l To export single-mode GBTS, NodeB, eNodeB or single-mode BTS3900 data from MBTSs to
generate the inventory file and correlation file, perform the following steps:
1. Choose Maintenance > Task Management (traditional style); alternatively, double-click
System Management in Application Center and choose Task Schedule > Task Management
(application style).
2. In the displayed Task Management window, select Inventory Data Export from the navigation
tree in the left pane of the window.
3. Double-click a task in the task list. In the displayed Attribute dialog box, click the Extended
Parameters tab and check whether All NEs and Export data of child NEs from MBTSs are
selected.
l The naming convention of correlation files is as follows:
CIM_NE type_[controller name_]NE name.file format
l NE type: type of the current NE, such as BTS3900 WCDMA and BTS3900 LTE.
l Controller name: name of the controller that manages the current NE.
l NE name: name of the current NE that is displayed in the topology view on the client.
l File format: file format, which can be set to xml, csv, or txt.
l When an NE has no inventory data to be reported, the U2000 exports inventory files based on the
attributes defined by the inventory model. When an NE has inventory data to be reported, the U2000
exports inventory files based on the actual attributes reported by the NE, excluding the attributes that
have not been defined in the inventory model.
l To export single-mode eNodeB data from an MBTS (WL), the correlation file for eNodeB will not
be generated.
NOTE
If a northbound interface compatibility ID has been set, the U2000 will adjust the EMS ID and FDN
format based on the setting. For example, the EMS ID is changed from OSS to OMC and the FDN is
changed from name-value format to dotted format. For details, see 4.6 How to Set Northbound
Interface Compatibility.
Table 3-3 describes the flags in the inventory management files that are exported based on the
MOC and saved in XML format.
<NE> Records the basic information about an NE, including NEFdn, NEName,
and NEType.
Currently, MOC-based export does not support collection time recording.
<ROW> Contains one record. The attribute of this flag is the attribute name and
value of each record. For details about the attribute names, see the
Inventory Types of NEs.xls.
The inventory types may be changed based on the U2000 or NE versions.
Therefore, you are advised to make the NMS ignore unnecessary
inventory types on the U2000, which has no impact on system operations.
The location of a specified inventory type in the file may also be changed
based on the version changes. Therefore, you need to make the NMS
identify an inventory type based on the properties of the inventory type
when the NMS parses the file.
In the following example, the inventory management export file for BSC6900 GSM is
exported based on the MOC Rack.
<?xml version="1.0" encoding="UTF-8"?>
<DATAPACKET>
<NE NEFdn="NE=256" NEName="10.145.18.23" NEType="BSC6900GSM">
<ROW BOM="" BOMCode="" BOMFrameType="" CLEICode="" CabinetNo="0"
DateOfLastService="" DateOfManufacture="" FrameType="MPS"
HardwareVersion="" InventoryUnitId="0" InventoryUnitType="Hardware"
IssueNumber="" ManufacturerData="" ModuleNo="-1" RackFrameNo="0"
SerialNumber="" SubrackNo="0" UnitPosition="CabinetNo=0,SubrackNo=0"
UserLabel="" VendorName="Huawei" VendorUnitFamilyType="Frame"
VendorUnitTypeNumber="0" />
</NE>
</DATAPACKET>
Prerequisites
l You have logged in to the U2000 client.
l You are authorized to perform inventory management.
l The progress is displayed as Idle.
Procedure
Step 1 Choose Maintenance > Task Management (traditional style); alternatively, double-click
System Management in Application Center and choose Task Schedule > Task
Management (application style). The Task Management window is displayed.
Step 2 Click Inventory Data Export in the navigation tree to view a task record.
Step 3 Double-click the task record to view the Attribute dialog box. Set Common Parameters and
Extended Parameters.
----End
Prerequisites
l The conditions for the automatic inventory management data export are met.
l You have logged in to the U2000 client.
l You are authorized to perform inventory management.
Context
After the automatic export of inventory management files is enabled, you can stop it manually
at any time.
For details about how to enable the automatic export of inventory management files, see 3.2.1
Automatically Exporting Inventory Management Files.
Procedure
Step 1 Choose Maintenance > Task Management (traditional style); alternatively, double-click
System Management in Application Center and choose Task Schedule > Task
Management (application style). The Task Management window is displayed.
Step 2 Click Inventory Data Export in the navigation tree to view a task record.
Step 3 Right-click a task record and then choose Suspend from the shortcut menu to stop the
automatic exporting of inventory management files.
----End
The NMS interconnects with the U2000 through the northbound inventory file interface. If a
fault occurs when the NMS is obtaining inventory data, rectify the fault by referring to this
part.
This section describes how to set parameters in the configuration file of a northbound
interface.
Troubleshooting
For the methods of rectify common faults that may occur during the process of obtaining
inventory data for the NMS, see Table 4-1.
How to set northbound interface See 4.6 How to Set Northbound Interface
compatibility Compatibility.
Information Collection
If an unusual fault occurs when the NMS is obtaining inventory data, you need to collect the
fault information to help to locate the fault. For details about how to collect fault information,
see Table 4-2.
Symptom
No exported inventory file is available in the export file. Thus, the NMS fails to obtain the
inventory data of NEs.
Problem Localization
The following causes may lead to the problem that no inventory file is exported:
l An NE is disconnected.
l The disk space on the U2000 server is insufficient.
Main Topology (application style). In the Main Topology window, right-click the
disconnected NE and then choose Reconnect NE.
2. Verify the network and rectify the network fault.
3. Rectify the fault on the NE mediation. To reinstall the NE mediation, see the
Commissioning Guide of the corresponding U2000 networking mode.
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.
Symptom
You can view and export the correct inventory information on the NE side. After the U2000
client synchronizes the data, however, you fail to query the corresponding inventory
information about an NE and the file does not contain the information.
Problem Localization
When the inventory data is synchronized, if the NE does not report the correct device file, the
U2000 may fail to obtain the corresponding inventory information. Accordingly, you fail to
query the NE inventory data or export the file. Perform the following operations for
confirmation.
1. In the corresponding path on the U2000 server, check whether the original device files
reported by NEs are available.
– The path for the original device files is /export/home/sysm/ftproot/devdoc/NE
type/temp.
– The format of original device files is W_NE FDN.xml or W_NE FDN.zip.
NOTE
Some NEs such as BSC32s do not report the original device files, thus, you need to check the
U2000 device files.
2. In the U2000 device file, check whether the data under ROWDATA in the description
area of the inventory type is correct.
– The path for the U2000 device files is /export/home/sysm/ftproot/devdoc/NE
type/.
– The format of the U2000 device files is W_IP address of the U2000_NE type_NE
Device ID-NE FDN_NE name.xml.
Troubleshooting
Contact Huawei engineers for assistance.
Symptom
The failure to synchronize the NE inventory data may cause the following problems:
l When you select a faulty NE on the U2000 Ne Information Collection Tool to collect the
device file of the NE again after the inventory data fails to be synchronized, Status is
displayed as Collecting when the progress ranges from 0% to 33%. A timeout error is
displayed. Double-click the progress bar. The message The data export times
out is displayed.
l When you select a faulty NE on the U2000 Ne Information Collection Tool to collect the
device file of the NE again after the inventory data fails to be synchronized, Status is
displayed as Collecting when the progress reaches 33%. A timeout error is displayed or
the collection is in progress for a long period without a response.
l When you select a faulty NE on the U2000 Ne Information Collection Tool to collect the
device file of the NE again after the inventory data fails to be synchronized, the progress
of synchronization is displayed 33%, and Status is displayed as Uploading files. Finally,
the message Upload failed is displayed.
l After the inventory data fails to be synchronized, the synchronization progress is equal to
or greater than 66% when you use the U2000 client.
Troubleshooting
The U2000 Ne Information Collection Tool fails to collect NE device files, which leads to the
failure to synchronize NE inventory data. Perform the following operations to find the cause
for the failure.
1. Before collecting device files, enable the function of the follow-up reports browser on
the Ne Information Collection Tool, right-click the NEs whose inventory data fails to be
synchronized, set Follow-up Report Hint, and then collect device files or synchronize
inventory data.
– If the collection progress displayed after the EXP DEVFILE command is run stays
at 0%, or no progress message is displayed, you can infer that the NE does not
respond to the EXP DEVFILE command and leads to timeout.
– If the progress displayed after the EXP DEVFILE command is run stays at 99%
for more than five minutes, you can infer that the NE is faulty. This method is
especially applicable to RNCs.
– View the progress displayed after the ULD DEVFILE command is run. Check
whether the NE reports error messages.
2. Run the following command to check whether the trace information in the mediation
reports the error information about message parsing. If the parsing is erroneous, you can
infer that the collection fails.
$ cd /opt/oss/server/var/logs/
$ more iMAP.med[xxxx]_agent.trace
Solution
Contact Huawei engineers for assistance.
Symptom
After exporting the NE inventory data from the U2000, and adding or modifying partial data,
you fail to import the data to the U2000.
The messages displayed during the failure to import inventory data are as follows:
l Importing inventory data
Cabinet No.= 0; asset unit identity = 0: the key properties of the cabinet
and the node are duplicate.
Troubleshooting
One of the following causes may lead to the previous failure:
1. The key properties of a certain record (for example, a cabinet) in the imported inventory
data conflict with those of an existing inventory record in the U2000.
2. The key properties of an inventory record (for example, a cabinet) in the imported
inventory data are null.
Solution
In the imported file, delete the inventory record whose key properties conflict with those of an
existing inventory record in the U2000, including the contents of ROWDATA that contain
this inventory record. Delete the inventory record whose key properties are null, including the
contents of ROWDATA that contain this inventory record.
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
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