This section describes how to set parameters in the configuration file of a northbound interface.
4.1 Common Troubleshooting and Information Collection (Inventory File Interface)
If a fault occurs when the NMS attempts to obtain inventory data through the northbound inventory file interface, rectify the fault by referring to common troubleshooting methods. If it is not possible to rectify a fault by using common troubleshooting methods, collect the fault information and contact a Huawei engineer for assistance.
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.
Table 4-1 Troubleshooting
Common Fault Troubleshooting Method
No inventory file is exported. See 4.2 Troubleshooting the Inventory File Export Failure.
The exported file is empty. See 4.3 Troubleshooting an Issue in Which the Exported File Is Empty.
The NE inventory data fails to be synchronized.
See 4.4 Troubleshooting Failure to Synchronize NE Inventory Data.
Exporting the NE inventory data fails. See 4.5 Troubleshooting Failure to Import NE Inventory Data.
How to set northbound interface compatibility
See 4.6 How to Set Northbound Interface Compatibility.
How to set parameters in a northbound configuration file
See 4.7 How to Set Parameters in a Northbound Configuration File.
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.
Table 4-2 Description of information collection
Related Information Description
Operation information Record the operations performed before a fault occurs and the troubleshooting measures taken later.
Related Information Description
Version information You can obtain version information about the U2000, NE mediations, and NEs from each office.
IP information You can obtain IP information about U2000
servers from each office.
Log information NOTE
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 ]
l You can obtain log information in the /opt/oss/server/var/logs path. In this path, the trace file name of cmserver is iMAP.cmserver_agent.trace.
l You can obtain the exported inventory file in the /opt/oss/server/var/
fileint/cm/InvtTimerExport/ path.
l You can obtain the backup trace file from the following path: /opt/oss/
server/var/logs/tracebak.
4.2 Troubleshooting the Inventory File Export Failure
This describes how to troubleshoot the inventory file export failure that occurs due to the following causes: NE disruption and disk space insufficiency of the U2000 server.
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.
Handling NE Disconnection Faults
1. On the U2000 client, choose Topology > Main Topology (traditional style);
alternatively, double-click Topo View in Application Center and choose Topology >
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.
Handling Insufficient Disk Space Faults on the U2000 Server
Clear the disk space on the U2000 server.
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.
4.3 Troubleshooting an Issue in Which the Exported File Is Empty
This section describes how to analyze and solve the problem when you fail to query the inventory data on the U2000 client and the file does not contain the relevant information because the NE does not report the inventory data.
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.
4.4 Troubleshooting Failure to Synchronize NE Inventory Data
This section describes how to analyze and solve the problem that the U2000 fails to collect the device files, which leads to the failure to synchronize the NE inventory data.
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.
4.5 Troubleshooting Failure to Import NE Inventory Data
This section describes how to analyze and solve the problem that the key attributes of an imported inventory file are null or conflict with each other, which leads to the failure to import NE inventory data.
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.
l Importing inventory data
Cabinet No.; asset unit identity: the key properties of the cabinet cannot be null.
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.
4.6 How to Set Northbound Interface Compatibility
This section describes how to set the FDN format and OMC ID of northbound interfaces so that the northbound interfaces are compatible with earlier versions.
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.
Step 6 Click OK.
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
4.7 How to Set Parameters in a Northbound Configuration File
This section describes how to set parameters in the configuration file of a northbound interface.
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.
Step 4 Click Save for the modification to take effect.
You can view service restart logs in Service Restarted Log.
----End