V200R016C10
Northbound Inventory File Interface
Developer Guide
Issue 02
Copyright © Huawei Technologies Co., Ltd. 2016. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
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.
Huawei Technologies Co., Ltd.
Address: Huawei Industrial BaseBantian, Longgang Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
About This Document
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.
Product Name Version
U2000 V200R016C10
Intended Audience
This document is intended for: Network management engineers
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:
Add BTS3202E and BTS3202E LTE.
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.
2 Interconnection Commissioning of the Northbound Inventory File Interface 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
3 Introduction to Exported Inventory Management Files This chapter describes the exported inventory management files. 4 Troubleshooting for the Northbound Inventory File Interface
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
Indicates an imminently hazardous situation which, if not avoided, will result in death or serious injury.
Indicates a potentially hazardous situation which, if not avoided, could result in death or serious injury.
Indicates a potentially hazardous situation which, if not avoided, may result in minor or moderate injury.
Symbol Description
Indicates a potentially hazardous situation which, if not avoided, could result in equipment damage, data loss, performance deterioration, or unanticipated results.
NOTICE is used to address practices not related to personal injury.
Calls attention to important information, best practices and tips.
NOTE is used to address information not related to personal injury, equipment damage, and environment deterioration.
General Conventions
The general conventions that may be found in this document are defined as follows.
Convention Description
Times New Roman Normal paragraphs are in Times New Roman.
Boldface Names of files, directories, folders, and users are in boldface. For example, log in as user root.
Italic Book titles are in italics.
Courier New Examples of information displayed on the screen are in Courier New.
Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention Description
Boldface The keywords of a command line are in boldface.
Italic Command arguments are in italics.
[ ] Items (keywords or arguments) in brackets [ ] are optional.
{ x | y | ... } Optional items are grouped in braces and separated by vertical bars. One item is selected.
[ x | y | ... ] Optional items are grouped in brackets and separated by vertical bars. One item is selected or no item is selected. { x | y | ... }* Optional items are grouped in braces and separated by
vertical bars. A minimum of one item or a maximum of all items can be selected.
Convention Description
[ x | y | ... ]* Optional items are grouped in brackets and separated by
vertical bars. Several items or no item can be selected.
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Convention Description
Boldface Buttons, menus, parameters, tabs, window, and dialog titles are in boldface. For example, click OK.
> Multi-level menus are in boldface and separated by the ">" signs. For example, choose File > Create > Folder.
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.
Double-click Press the primary mouse button twice continuously and quickly without moving the pointer.
Drag Press and hold the primary mouse button and move the
Contents
About This Document...ii
1 Introduction to Northbound Inventory File Interface... 1
1.1 Definition of Northbound Interface...2
1.2 Definition of Northbound Inventory File Interface... 2
1.3 Using the Inventory File Interface...2
1.4 Technical Specifications of Northbound File Interface... 3
2 Interconnection Commissioning of the Northbound Inventory File Interface...4
2.1 Checking License (Inventory File Interface)...6
2.2 Negotiating the Interconnection Parameters for the Inventory File Interface... 6
2.3 Modifying the Inventory Export Configuration File... 8
2.4 Setting an Inventory Export Task... 10
2.5 (Optional) Configuring the U2000 for Actively Uploading Files over the Northbound Interface...10
2.5.1 Configuring the SFTP for Actively Transferring Files over the Northbound Interface (Public and Private Keys) ... 11
2.5.2 Configuring the SFTP for Actively Transferring Files over the Northbound Interface (Password Authentication) ... 22
2.6 (Optional) Manually Exporting Inventory Management Files... 29
2.7 Verifying Interconnection... 29
3 Introduction to Exported Inventory Management Files... 32
3.1 Exporting Inventory Management Files... 33
3.1.1 NE Types for Inventory Management Export... 33
3.1.2 Types of Inventory Management Export Files... 35
3.1.3 Directory of Inventory Management Export Files...36
3.1.4 Naming Convention of Inventory Management Export Files... 36
3.1.5 Format of Inventory Management Export Files... 38
3.1.6 Policies for Deleting Exported Inventory Management Files... 42
3.2 Operations Related to Inventory Management Export... 43
3.2.1 Automatically Exporting Inventory Management Files... 43
3.2.2 Stopping Automatic Exporting of Inventory Management Files... 43
4 Troubleshooting for the Northbound Inventory File Interface... 45
4.1 Common Troubleshooting and Information Collection (Inventory File Interface)...47
4.3 Troubleshooting an Issue in Which the Exported File Is Empty...49
4.4 Troubleshooting Failure to Synchronize NE Inventory Data... 50
4.5 Troubleshooting Failure to Import NE Inventory Data... 51
4.6 How to Set Northbound Interface Compatibility... 52
1
Introduction to Northbound Inventory File
Interface
About This Chapter
This introduces the definition of the northbound interface and the northbound inventory file interface provided by the U2000.
1.1 Definition of Northbound Interface
The northbound interface links the element management system (EMS) and the NMS. 1.2 Definition of Northbound Inventory File Interface
The U2000 northbound inventory file interface is one of the northbound interfaces. The NMS can obtain the inventory data of NEs through the U2000 northbound inventory file interface. 1.3 Using the Inventory File Interface
This section describes how to use the inventory file interface when the U2000 system adopts different networking modes.
1.4 Technical Specifications of Northbound File Interface
1.1 Definition of Northbound Interface
The northbound interface links the element management system (EMS) and the NMS. 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.
Figure 1-1 Position of the northbound interface
In the communication network, the U2000 provides the alarm, configuration, performance, and inventory data of NEs to the NMS through the northbound interface.
1.2 Definition of Northbound Inventory File Interface
The U2000 northbound inventory file interface is one of the northbound interfaces. The NMS can obtain the inventory data of NEs through the U2000 northbound inventory file interface.
1.3 Using the Inventory File Interface
This section describes how to use the inventory file interface when the U2000 system adopts different networking modes.
For details about how to use the northbound inventory file interface in different networking modes, see Table 1-1.
Table 1-1 Usage of the inventory file interface U2000 System Type NMS and U2000
Interconnection Solution Method for the NMS toObtain Inventory Files Single-server system Perform interconnection on the
U2000 server.
Obtain inventory files on the U2000 server.
HA system Perform interconnection on the
active U2000 server.
Obtain inventory files on the active U2000 server.
Remote HA system
SUN SLS system Perform interconnection on the master U2000 server.
ATAE cluster system (Distributed
networking)
ATAE cluster online remote HA system
Perform interconnection on the master servers of the active and standby U2000 sites.
Obtain inventory files on the master servers of the active and standby U2000 sites.
VM Single System Perform interconnection on the U2000 VM.
Obtain inventory files on the U2000 VM.
VM Cluster System (Distributed networking)
Perform interconnection on the master U2000 service VM.
Obtain inventory files on the master U2000 service VM.
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.
1.4 Technical Specifications of Northbound File Interface
This section describes the technical specifications related to the northbound file interface.
Specification Item Value
Maximum re-upload attempts that are permitted after automatic file upload fails
3 Interval between re-upload attempts after an automatic file upload attempt fails (unit: minute)
15 Maximum FTP servers supported by automatic file upload 10 Number of objects of the same type supported by northbound performance threshold subscription (unit: number)
2
Interconnection Commissioning of the
Northbound Inventory File Interface
About This Chapter
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.
2.1 Checking License (Inventory File Interface)
Before interconnecting the U2000 to the NMS, make sure that the NMS is licensed to use the northbound inventory file interface.
2.2 Negotiating the Interconnection Parameters for the Inventory File Interface
Before interconnecting the U2000 to the NMS, you need to check the license of the inventory file interface and negotiate the interconnection parameters for the inventory file interface. The inventory file is exported according to the negotiated parameters.
2.3 Modifying the Inventory Export Configuration File
This section describes how to modify the inventory export configuration file. 2.4 Setting an Inventory Export Task
This describes how to set an automatic inventory export task on the U2000 client. 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.
2.6 (Optional) Manually Exporting Inventory Management Files
Besides automatic export, you can also manually export inventory management files. 2.7 Verifying Interconnection
This section describes how to simulate the NMS to obtain inventory files in SFTP mode using the OSMU. According to the obtained inventory file, you can check whether the northbound inventory file interface meets the conditions for interconnecting with the NMS.
2.1 Checking License (Inventory File Interface)
Before interconnecting the U2000 to the NMS, make sure that the NMS is licensed to use the northbound inventory file interface.
Do as follows to check that the NMS has the required license: 1. Log in to the U2000 client.
2. Choose License > OSS License Management > License Information (traditional style). Alternatively, double-click System Management in Application Center and choose License Management > License Information (application style). The License Information window is displayed.
3. Click the Resource Control Item tab. If Resource contains Inventory File Interface, the NMS is authorized to use the inventory file interface.
2.2 Negotiating the Interconnection Parameters for the
Inventory File Interface
Before interconnecting the U2000 to the NMS, you need to check the license of the inventory file interface and negotiate the interconnection parameters for the inventory file interface. The inventory file is exported according to the negotiated parameters.
Negotiating the Interconnection Parameters
The interconnection parameters for the inventory file interface include the user name and password for the NMS to log in to the U2000, the start time and format of the exported file, and the fields in the exported file. Table 2-1 lists an example of a group of inventory file interface parameters. The following interconnection operations take this example as a reference.
Table 2-1 Example of interconnection parameters
Parameter Type Parameter Parameter Value Description
User User Name ftpuser This parameter is
not modifiable.
Password The 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.
Parameter Type Parameter Parameter Value Description
Export Path /opt/oss/server/var/
fileint/cm/
InvtTimerExport/
This parameter is not modifiable.
Content NE For example,
BTS3900 WCDMA
This parameter is modifiable on the U2000 client.
Format Start Time 10/11/2008 19:40:00 This parameter is
modifiable on the U2000 client.
Export Period 1 The minimum unit is
day.
This parameter can be modified on the U2000 client.
File Format XML This parameter is
modifiable on the U2000 client.
Negotiating File Transfer Mode
You need to negotiate between the U2000 and NMS to determine whether PUSH or PULL be used. You also need to negotiate between the U2000 and NMS to determine whether FTP or SFTP be used. You can then prepare for the interconnection according to the negotiated results by referring to Table 2-2.
NOTICE
Using SFTP is recommended because of its higher security than FTP.
Table 2-2 Guidance for setting file transfer
Mode FTP SFTP
PUSH: the U2000 automatically uploads files
For details, see Step 7 of 2.5.1 Configuring the SFTP for Actively Transferring Files over the Northbound Interface (Public and Private Keys).
For details, see 2.5.1 Configuring the SFTP for Actively Transferring Files over the Northbound Interface (Public and Private Keys) or 2.5.2 Configuring the SFTP for Actively Transferring Files over the Northbound Interface (Password Authentication).
Mode FTP SFTP PULL: the
NMS directly obtains files
If you use FTP to transfer files, enable FTP by referring to the section "Configuring the FTP Transmission Policy" described in the corresponding U2000 Administrator Guide.
The U2000 uses SFTP to transfer files by default.
2.3 Modifying the Inventory Export Configuration File
This section describes how to modify the inventory export configuration file.
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
The configuration file contains the following contents: <?xml version="1.0" encoding="UTF-8"?>
<IMExpPara>
<DisCreditableRule Name="Synchronize DisCreditable Data" Value="false" /> <FileSaveDay Name="Export file saving days" Value="3"/>
<SyncRule Name="SyncTimeLatest" Value="false" />
<AlignRule Name="All align with MML,Unify to Cabinet No./Subrack No./Slot No." Value="true" />
</IMExpPara>
Step 2 Modify the InvtExportPara.xml file. l Customize the export file name:
Add the export file naming rule to <IMExpPara>...</IMExpPara>. For example, <FileNameRule Name="IM Export File naming rule"
Value="[IM]_[ExportTime]_[NeName]-[NeIP]-[NodeId].exp1234"/> l Set the collection time switch:
Set Value of SyncTimeLatest to true or false. If you set Value to true, the collection time switch is enabled, and the collection time will be recorded in the inventory export file. If you set Value to false, the collection time switch is disabled, and the collection time will not be recorded.
l Set the attribute display switch of the inventory file:
Set Value of All align with MML,Unify to Cabinet No./Subrack No./Slot No. to true or false.
l Set the file storage time switch:
Set Value of Export file saving days to a specific value (such as three days) as required. l Set whether to export untrusted inventory data:
Set Value of Synchronize DisCreditable Data to true or false as required to set whether untrusted data reported by NEs is saved to the database and exported over the northbound interface.
Old MOC Name
New MOC Name Switch Disabled
(Value="false") Switch Enabled(Value="true")
Rack Rack Cabinet
Frame Frame Subrack
MBTSRack MBTSRack MBTSCabinet
MBTSFrame MBTSFrame MBTSSubrack
BSCFrame BSCFrame BSCSubrack
BSCBTSFrame BSCBTSFrame BSCBTSSubrack
Old Attribute Name
New Attribute Name Switch Disabled
(Value="false") Switch Enabled(Value="true")
RackNo RackNo CabinetNo
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
2.4 Setting an Inventory Export Task
This describes how to set an automatic inventory export task on the U2000 client.
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.
Table 2-3 An example of setting parameters
Tab Page Parameter Parameter Value
Common Parameters Task Name Inventory Data Export
Start Time 10/11/2008 19:40:00
Period One day
Extended Parameters File Format XML
NE For example, BTS3900 WCDMA
Step 4 Click OK. The setting of automatic export is complete. ----End
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.
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.
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.
If You Need to... Then...
Generate encrypted public and private key files
Only perform Step 1.1 to Step 1.4.
Generate non-encrypted public and private key files
Only perform Step 1.5 to Step 1.8.
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 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/
– 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
– If the system displays id_rsa_pwd.pub: No such file or directory, perform Step 1.3 to create a public key file.
– 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 system displays the following message, enter /export/home/omc/.ssh/ id_rsa_pwd.
Generating public/private rsa key pair.
Enter file in which to save the key (/export/ossuser/.ssh/id_rsa):
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/
$ chmod 600 id_rsa_pwd.pub
5. Run the following command on the U2000 server to check whether the .ssh directory exists in the home directory.
$ 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 Step 1.7. $ mkdir -p ${HOME}/.ssh/
– If no command output is displayed, the .ssh directory is available in the home directory. Perform Step 1.6.
NOTE
The ${HOME} parameter indicates the home directory of user ossuser.
6. Run the following command to check whether the id_rsa file exists. $ ls id_rsa
– 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 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 ${HOME}/.ssh/
$ chmod 600 id_rsa.pub
Step 2 Enable public key authentication on the NMS.
1. Log in to the NMS server as user UserA. Run the cd ${HOME}/.ssh/ command to check whether the .ssh directory exists in the home directory.
– If No such file or directory is displayed, the .ssh directory is unavailable in the home directory. After running the mkdir -p ${HOME}/.ssh/ command, perform Step 2.2.
– If no command result is displayed, the .ssh directory is available in the home directory. Perform Step 2.2.
NOTE
The ${HOME} parameter indicates the home directory of user UserA.
2. Run the ls authorized_keys command to check whether the authorized_keys file exists. – If the system displays authorized_keys: No such file or directory, run the touch
authorized_keys command to create the authorized_keys file. Then, perform Step 2.3.
– If the system displays authorized_keys, proceed to Step 2.3.
3. Copy the content of the id_rsa.pub or id_rsa_pwd.pub file on the U2000 server to the authorized_keys file on the NMS server.
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.
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
Table 2-4 lists the parameters to be configured. Table 2-4 Parameters to be configured for the SFTP
Parameter Value RSAAuthentication yes PubkeyAuthentica-tion yes AuthorizedKeysFile .ssh/authorized_keys PasswordAuthentica-tion
yes/no. This parameter specifies whether the password authentication is used when the authentication of the public key and private key fails. You are advised to set this parameter to yes.
– yes: password authentication is used. – no: password authentication is not used.
Parameter Value
MaxStartups Number of concurrent connections. The calculation method is as follows:
1. Run the following command to query the number of the SFTP tasks deployed on the U2000 server:
n If the installed U2000 server software is a Chinese edition, run the following command:
# vi /opt/oss/server/etc/XFTPService/locale/zh_CN/ TaskInfoCache.xml
n If the installed U2000 server software is an English edition, run the following command:
# vi /opt/oss/server/etc/XFTPService/locale/en_US/ TaskInfoCache.xml ... <ftpset> <dest>10.10.10.10</dest> <localpath... <localpath... </ftpset> ...
The preceding command output is used as an example. 10.10.10.10 indicates the IP address of the northbound server, and each localpath value corresponds to a task. Record the number of tasks and enter :q! to exit the vi editor.
2. Run the following command to query the number of threads occupied by the SFTP tasks:
# cat /opt/oss/server/etc/XFTPService/ ModuleParam.xml |grep TaskThreadNum <param name="TaskThreadNum">10</param>
The preceding command output is used as an example. 10 indicates the number of threads occupied by the SFTP tasks. Record the number of threads.
3. The number of concurrent connections is obtained by multiplying the number of tasks by the number of occupied threads.
NOTE
If you change the number of SFTP tasks, you must change the number of concurrent connections at the same time.
If... Then... The NMS server is running Solaris The OpenS SH has been installe d Run the pkginf o OpenS SH comma nd, and the followi ng comma nd output is display ed: Securit y OpenSSH OpenSSH Portabl e for Solaris
# ps -ef | grep sshd | grep -v grep
root 27748 1 0 Dec 25 ? 2:13 /usr/local/sbin/sshd
root 21923 27748 0 11:11:31 ? 0:02 /usr/local/sbin/sshd -R
– If the command output contains /usr/local/sbin/ sshd, the SFTP service is running. Run the following command to restart the SFTP service: # /etc/init.d/opensshd restart
– If no command output is displayed, the SFTP service has not started. Run the following command to start the SFTP service: # /etc/init.d/opensshd start
If... Then... No OpenS SH has been installe d Run the pkginf o OpenS SH comma nd, and the followi ng comma nd output is display ed: ERROR: informa tion for "OpenSS H" was not found # svcs -a | grep ssh online 17:27:13 svc:/network/ ssh:defaul
– If the command output contains online, the SFTP service is running. Run the following command to restart the SFTP service:
# svcadm restart svc:/network/ssh:default – If the command output contains disabled, the
SFTP service has not started. Run the following command to start the SFTP service:
# svcadm enable svc:/network/ssh:default
The NMS server is running
SUSE Linux # service sshd statusChecking for service
sshd running
– If the command result contains running, the SFTP service is running. Run the following command to restart the SFTP service: # service sshd restart
– If the command result does not contain running, the SFTP service is disabled. In this case, contact Huawei technical support.
The NMS server is running any other OS
Contact Huawei technical support.
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.
$ 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.
The following information is displayed. d67A29C93775A68AE21DDAF1052EBBD1 is the encryption password.
Success. Encrpt passwd :d67A29C93775A68AE21DDAF1052EBBD1 $
2. Use the Vi command to change the values of IsSupportEncrpt, PrivateExKeyFile, and EncrptKey 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
Table 2-5 Parameter description
Parameter Description
IsSupportEncrpt Change the value to 1, indicating that the encryption password transfer mode is supported.
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.
EncrptKey Enter the queried encryption password, for example,
d67A29C93775A68AE21DDAF1052EBBD1.
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.
NOTE
The ${HOME} parameter indicates the home directory of user ossuser.
– 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
– 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
Search for the DefaultFTPType parameter and change the value to 1. 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 $ svc_adm -cmd status | grep XFTP
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.
$ svc_adm -cmd restartsvc XFTPService0X01
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.
Table 2-6 Parameters in the Target Server Setting window Parameter Description
Module Type/ Module Name
The module type consists of NBI FM, NBI CM, NBI PM, NBI Inventory, CME NBI, CME NCCDM, License Management, NBI Server Backup, NBI Log, EBC Counter, EBC Data, and LTE Trace 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.
Server IP IP address of the FTP server
User Name User name used to log in to the FTP server. Password Password used to log in to the FTP server. Confirm
Password
Parameter Description Server
Directory
Directory for storing a file after it is transferred to the FTP server. 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
Directory for storing the LTE Trace Data need to be uploaded.
NOTE
This parameter only can be configured when you modify or add a FTP server whose Module Name is LTE Trace Data.
File Compressio n Type
Whether to compress a file before transferring it. –NONE: Transfer a file without compressing it. –ZIP: Transfer a file after compressing it.
5. Click OK. The configuration setting is completed.
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.
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
Password: Password of user root # vi /etc/ssh/sshd_config
Table 2-7 lists the parameters to be configured. Table 2-7 Parameters to be configured for the SFTP
Parameter Value
PasswordAuthentica-tion
yes/no. Set this parameter to yes. l yes: password authentication is used. l no: password authentication is not used.
Parameter Value
MaxStartups Number of concurrent connections. The calculation method is as follows:
1. Run the following command to query the number of the SFTP tasks deployed on the U2000 server:
–If the installed U2000 server software is a Chinese edition, run the following command:
# vi /opt/oss/server/etc/XFTPService/locale/zh_CN/ TaskInfoCache.xml
–If the installed U2000 server software is an English edition, run the following command:
# vi /opt/oss/server/etc/XFTPService/locale/en_US/ TaskInfoCache.xml ... <ftpset> <dest>10.10.10.10</dest> <localpath... <localpath... </ftpset> ...
The preceding command output is used as an example. 10.10.10.10 indicates the IP address of the northbound server, and each localpath value corresponds to a task. Record the number of tasks and enter :q! to exit the vi editor. 2. Run the following command to query the number of threads
occupied by the SFTP tasks:
# cat /opt/oss/server/etc/XFTPService/ModuleParam.xml |grep TaskThreadNum
<param name="TaskThreadNum">10</param>
The preceding command output is used as an example. 10 indicates the number of threads occupied by the SFTP tasks. Record the number of threads.
3. The number of concurrent connections is obtained by multiplying the number of tasks by the number of occupied threads.
NOTE
If you change the number of SFTP tasks, you must change the number of concurrent connections at the same time.
If... Then... The NMS server is running Solaris The OpenSS H has been installed Run the pkginfo OpenSS H comman d, and the followin g comman d output is displaye d: Securit y OpenSSH OpenSSH Portabl e for Solaris
# ps -ef | grep sshd | grep -v grep
root 27748 1 0 Dec 25 ? 2:13 /usr/local/sbin/sshd
root 21923 27748 0 11:11:31 ? 0:02 /usr/local/sbin/sshd -R
l If the command output contains /usr/local/sbin/ sshd, the SFTP service is running. Run the following command to restart the SFTP service: # /etc/init.d/opensshd restart
l If no command output is displayed, the SFTP service has not started. Run the following command to start the SFTP service:
If... Then... No OpenSS H has been installed Run the pkginfo OpenSS H comman d, and the followin g comman d output is displaye d: ERROR: informa tion for "OpenSS H" was not found # svcs -a | grep ssh online 17:27:13 svc:/network/ssh:defaul
l If the command output contains online, the SFTP service is running. Run the following command to restart the SFTP service:
# svcadm restart svc:/network/ssh:default l If the command output contains disabled, the SFTP
service has not started. Run the following command to start the SFTP service:
# svcadm enable svc:/network/ssh:default
The NMS server is running
SUSE Linux # service sshd statusChecking for service sshd running
l If the command result contains running, the SFTP service is running. Run the following command to restart the SFTP service:
# service sshd restart
l If the command result does not contain running, the SFTP service is disabled. In this case, contact Huawei technical support.
The NMS server is running any other OS
Contact Huawei technical support.
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 $ svc_adm -cmd status | grep XFTP
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.
$ svc_adm -cmd restartsvc XFTPService0X01
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.
$ 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 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.
Table 2-8 Parameters in the Target Server Setting window Parameter Description Module Type/ Module Name
The module type consists of NBI FM, NBI CM, NBI PM, NBI Inventory, CME NBI, CME NCCDM, License Management, NBI Server Backup, NBI Log, EBC Counter, EBC Data, and LTE Trace 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.
Server IP IP address of the FTP server
User Name User name used to log in to the FTP server. Password Password used to log in to the FTP server. Confirm
Password
Enter the password again that is used to log in to the FTP server. Server
Directory
Directory for storing a file after it is transferred to the FTP server. 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
Directory for storing the LTE Trace Data need to be uploaded.
NOTE
This parameter only can be configured when you modify or add a FTP server whose Module Name is LTE Trace Data.
File Compressio n Type
Whether to compress a file before transferring it. –NONE: Transfer a file without compressing it. –ZIP: Transfer a file after compressing it.
5. Click OK. The configuration setting is completed.
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.
2.6 (Optional) Manually Exporting Inventory Management
Files
Besides automatic export, you can also manually export inventory management files.
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 to Be
Exported Operation
Inventory data of all MOs of an NE
Right-click the NE node, and then choose Export > Export All from the shortcut menu.
Inventory data of all the external data of an NE
Right-click the NE node, and then choose Export > 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 NE
Right-click the MO node, and then choose Export from 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
2.7 Verifying Interconnection
This section describes how to simulate the NMS to obtain inventory files in SFTP mode using the OSMU. According to the obtained inventory file, you can check whether the northbound inventory file interface meets the conditions for interconnecting with the NMS.
Context
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 3 In the main window of the OSMU, click NBI Management.
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=""
UserLabel="" BOMCode="" IssueNumber="" BOMFrameType="" CLEICode="" BOM="" /> </ROWDATA> </TABLE> <TABLE attrname="Slot"> <ROWDATA>
<ROW CabinetNo="0" SubrackNo="0" SlotNo="0" SlotPos="0" InventoryUnitId="0" InventoryUnitType="Hardware" VendorUnitFamilyType="SLOT" VendorUnitTypeNumber="0" VendorName="Huawei" SerialNumber="" HardwareVersion="" DateOfManufacture="" DateOfLastService="" UnitPosition="CabinetNo=0,SubrackNo=0,SlotNo=0,SlotPos=0" ManufacturerData="" /> </ROWDATA> </TABLE> <TABLE attrname="Board"> <ROWDATA>
<ROW CabinetNo="0" SubrackNo="0" SlotNo="29" SlotPos="0"
SubSlotNo="-1" InventoryUnitId="29" ModuleNo="-1" PortNo="-1" BoardName="PFCU" BoardType="" InventoryUnitType="Hardware" VendorUnitFamilyType="FAN" VendorUnitTypeNumber="0" VendorName="Huawei" SerialNumber="" HardwareVersion=""
DateOfManufacture="" DateOfLastService="" UnitPosition="CabinetNo=0, SubrackNo=0,SlotNo=29,SlotPos=0,SubSlotNo=-1,PortNo=-1"
ManufacturerData="" SoftVer="" LogicVer="" BiosVer="" BiosVerEx="" LANVer="" MBUSVer="" IssueNumber="" BOMCode="" UserLabel="" /> </ROWDATA>
</TABLE>
<TABLE attrname="Port"> <ROWDATA>
<ROW CabinetNo="0" SubrackNo="0" SlotNo="19" SlotPos="1" SubSlotNo="-1" VendorUnitFamilyType="FE Port" InventoryUnitId="5" HardwareVersion="" SerialNumber="" DateOfManufacture="" ManufacturerData=""
InventoryUnitType="Hardware" VendorName="Huawei" VendorUnitTypeNumber="0" DateOfLastService="" UnitPosition="CabinetNo=0,SubrackNo=0,SlotNo=19, SlotPos=1, SubSlotNo=-1,PortNo=5" /> </ROWDATA> </TABLE> <TABLE attrname="HostVer"> <ROWDATA>
<ROW HostVerType="HOSTVER" HostVer="VxxRxx" sDesc="" /> <ROW HostVerType="BACKVER" HostVer="VxxRxx" sDesc="" /> <ROW HostVerType="HOTPATCH" HostVer="" sDesc="" /> <ROW HostVerType="HOSTPATCH" HostVer="" sDesc="" /> <ROW HostVerType="BOOTROMVER" HostVer="" sDesc="" /> </ROWDATA>
</TABLE>
<TABLE attrname="GCELL"> <ROWDATA>
<ROW CellId="2028" CellName="2028" MCC="536" MNC="21" LAC="17851" CI="20" NCC="0" BCC="0" TYPE="GSM900" BCCHNO="50" />
</ROWDATA> </TABLE>
<TABLE attrname="BTS"> <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> ----End
3
Introduction to Exported Inventory
Management Files
About This Chapter
This chapter describes the exported inventory management files. 3.1 Exporting Inventory Management Files
This section describes the NE types for inventory management export, and also the types, default save path, naming convention, and format of the exported inventory management files. 3.2 Operations Related to Inventory Management Export
The operations related to inventory management export include enabling and disabling the automatic export of inventory management files.
3.1 Exporting Inventory Management Files
This section describes the NE types for inventory management export, and also the types, default save path, naming convention, and format of the exported inventory management files.
3.1.1 NE Types for Inventory Management Export
This section describes the NE types for inventory management export.
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.
Table 3-1 List of supported NE Types
NE Type Whether Supported
SAEGW yes CGPOMU yes UAG yes ICS yes BSC yes PCU yes HLR yes GGSN80 yes SGSN yes MGW yes MSC Server yes BSC6000 Site yes BSC6000 yes RNC yes eNodeB yes BSC6900GSM yes BSC6900GSM Site yes BSC6900UMTS yes
NE Type Whether Supported BSC6900GU yes NodeB yes MBTS yes CBSC yes CBSC Site yes BSC6910GSM yes BSC6910GSM Site yes BSC6910UMTS yes
BSC6910GU Site yes
BSC6910GU yes MICRO BTS3900 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
NE Type Whether Supported USU3900 yes USU3910 yes HSS9860 yes SPSV3 yes GUHLR yes USCDB yes SE2900 yes CSCF yes ATS yes PICO BTS3900 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
Supporting U2000 Inventory Files
Currently, the inventory files of the U2000 can be exported through the inventory
management feature. For the description of specific inventory attributes, see the Inventory
Types of NEs.xls delivered with this release.
