The log information of the U2000 XML interface is saved in the %IMAPROOT%\server\log
\nbi directory. Back up the log files regularly in case they occupy too much of the system disk space. The log files records the running information of the U2000 XML interface and the operation performed by the NMS/OSS through the U2000 XML interface. If an error occurs when the U2000 XML interface is running, you can refer to the log files to do the troubleshooting.
If you want to back up the log information of the U2000 XML interface, manually copy the log information to a specified directory.
NOTE
In the case of the Solaris OS and Linux OS, the environment variable is represented by $Variable (Variable indicates the name of the variable).
In the case of the Windows OS, the environment variable is represented by %Variable% (Variable indicates the name of the variable).
The environment variable $IMAP corresponds to the installation directory of the U2000 server.
l In the case of the Solaris OS and Linux OS, the U2000 server is installed in the /opt/U2000/server directory by default. Hence, $IMAP corresponds to /U2000/server/conf.
l In the case of the Windows OS, the U2000 server is installed in the C:\U2000\server directory by default, Hence, %IMAP% corresponds to C:\U2000\server\conf and %IMAPROOT% corresponds to C:\U2000.
4.3 Logging In to the System Monitor Client
The U2000 System Monitor Client uses the client/server model. To perform an operation, you need to log in to the server through the U2000 client.
Prerequisite
Before login, ensure that the U2000 client and server are connected normally, and the server works correctly.
Context
l The default port number of the server is 31030. Do not change it in normal conditions.
Otherwise, you cannot log in to the U2000 server.
l The login mode is classified into the SSL mode and the common mode. In SSL mode, the data is encrypted when being transmitted between the client and the server. In common mode, the data is not encrypted during transmission.
l The port used for login in common mode is different from that in SSL mode. The port is 31030 in common mode, and 31080 in security (SSL) mode.
l If you do not log in during the preset period after the previous login, the U2000 disables or delete the user account.
l If you never use a new user account for login, the account is not restricted to these rules, that is, the U2000 does not set it to be invalid or delete it.
Procedure
1 Double-click the related shortcut icon on the desktop to start the system monitor client.
2 In the Login dialog box, select a server from the Server drop box.
NOTE
If there is no server to select, do as the followings:
1. Click on the right of Server drop box.
2. In the Server List dialog box, click Add.
3. In the Add Server Information dialog box, specify Name and Server Name(or IP Address), and then select a login mode. Click OK.
4. In the Server List dialog box, click OK.
3 In the Login dialog box, enter the user name and password.
The user name and password are the same as those for the U2000 client.
4 Click Login.
NOTE
l If the user name and the password are correct, the Loading dialog box is displayed, indicating the loading progress.
l If the user name or password is wrong, the Information dialog box prompts cannot login.
l If the password is to expire in the specified days, the system prompts you to change the password before the expiration date.
l If the license is to expire in the specified days, the system notifies you of the expiration date.
l If you use a temporary license, you are prompted to apply for an official license.
----End
4.4 Stopping the XML NBI
If you need not use the XML NBI, you can stop the XML process by using the System Monitor client.
Prerequisite
l On Solaris or SUSE Linux, you must have the nmsuser user rights.
l On Windows, you must have the administrator user rights.
l In an HA system, the XML interface is configured on the active server.
l The U2000 must be started.
l The XML Service and JMS Service processes are in the running state.
Context
NOTE
After you add an instance of the XML interface by using the NMS Maintain Tool, the startup mode is Automatic by default. The XML interface process is started together with the U2000.
Procedure
1 Log in to the System Monitor.
2 On the System Monitor, click the Process Monitor tab.
3 Select the XML Service process, right-click, and then choose Stop the Process from the shortcut menu.
4 The dialog box displayed, click Yes.
5 Follow step 3 to step 4, stop JMS Service processes.
6 In the System Monitor client, when Status of the relevant XML processes is Stopped, the operation is successful.
----End
4.5 Disabling the XML NBI
If you need not use the XML NBI, you can disable the related XML processes so that the processes are not started together with the nmsuser.
Prerequisite
l On Solaris or SUSE Linux, you must have the nmsuser user rights.
l On Windows, you must have the administrator user rights.
l In an HA system, the XML interface is configured on the active server.
l The U2000 must be started.
l The XML Service and JMS Service processes are in the running state.
Procedure
1 Log in to the System Monitor.
2 On the System Monitor, click the Process Monitor tab.
3 Select the XML Service process, right-click, and then choose Startup Mode > Disabled from the shortcut menu.
4 Select the JMS Service process, right-click, and then choose Startup Mode > Disabled from the shortcut menu.
5 In the System Monitor client, when Startup Mode of the relevant XML processes is Disabled, the operation is successful.
----End
4.6 Restarting the XML NBI
This topic describes how to restart the XML NBI.
Prerequisite
l On Solaris or SUSE Linux, you must have the nmsuser user rights.
l On Windows, you must have the administrator user rights.
l In an HA system, the XML interface is configured on the active server.
l The U2000 must be started.
l The XML Service and JMS Service processes are in the Stopped state.
Procedure
1 Log in to the System Monitor.
2 On the System Monitor, click the Process Monitor tab.
3 In the System Monitor client, select the JMS Service process, right-click, and then choose Start the Process from the shortcut menu.
4 In the System Monitor client, select the XML Service process, right-click, and then choose Start the Process from the shortcut menu.
5 In the System Monitor client, when Status of the relevant XML processes, namely JMS Service and XML Service are Running, the operation is successful.
----End
4.7 Deleting the XML Interface Instance
You can delete an instance for the XML interface if it is not in use, which enhances the running efficiency of the U2000.
Prerequisite
l Log in to the Solaris or SUSE Linux OS as user root.
l Log in to the Windows OS as user Administrator.
l In a HA system, configure the XML interface on the active server.
l The NMS Maintenance Suite server installed on the master and slave servers must be started.
l The U2000 must be operating.
l The NMS Maintenance Suite client communicates with the NMS Maintenance Suite server in the normal state.
l It is recommended that you stop the XML interface before delete the instance.
Context
l In a distributed system, you only need to log in to the NMS maintenance tool server of the master server to perform this operation.
l In a high availability system, you only need to log in to the NMS maintenance tool server of the primary site to perform this operation.
Procedure
1 Log in to the client of the NMS Maintenance Suite. For details, see 3.3 Logging in to the Client of the NMS Maintenance Suite.
2 On the NMS Maintenance Suite client, click the Instance tab. Select the AgentXML instance from the instance list, right-click, and choose Delete Instance
3 Click OK. After the confirmation, the NMS Maintenance Suite begins deleting the AgentXML instance.
4 Click the Deployment Package tab, if the Instance Count of the XML NBI deployment package is zero, that means the deletion success.
NOTE
After the AgentXML instance is deleted, the Sysmonitor does not display the information about the XML Service process, JMS Service process. If you need to re-enable the XML interface, refer to 3 Deploying and Configuring the XML NBI.
----End
4.8 Deleting the XML NBI Component
You can delete the component for the XML NBI if it is not in use, which enhances the running efficiency of the U2000.
Prerequisite
l Log in to the Solaris or SUSE Linux OS as user root.
l Log in to the Windows OS as user Administrator.
l In a HA system, configure the XML interface on the active server.
l The NMS Maintenance Suite server installed on the master and slave servers must be started.
l The U2000 must be operating.
l The NMS Maintenance Suite client communicates with the NMS Maintenance Suite server in the normal state.
l Ensure you have deleted the XML NBI instance.
Context
l In a distributed system, you only need to log in to the NMS maintenance tool server of the master server to perform this operation.
l In a high availability system, you only need to log in to the NMS maintenance tool server of the primary site to perform this operation.
Procedure
1 Log in to the client of the NMS Maintenance Suite. For details, see 3.3 Logging in to the Client of the NMS Maintenance Suite.
2 On the NMS Maintenance Suite client, click Deployment Package tab, check whether the instance count of XML NBI deployment package is zero.
l If Instance Count is not zero, you need to deleted the XML NBI instance first.
l If Instance Count is zero, choose Deploy > Remove Component from the Main Menu.
The dialog box is displayed.
3 Select Northbound XML Interface component, click OK. The deleting of the component is started.
NOTE
You can not delete the components which are basic or have not installed. You can not select them in the left window.
4 Wait until the message the component is successfully removed is displayed. Click OK.
5 View the Deployment Package list, the Northbound XML Interface deployment package not exist indicate that the operation is successful.
----End
4.9 FAQ
This section describes the identifying and handling methods for common failures in the system.
NOTE
For the irremovable faults, please dial 800-830-2118 (available at any time) for technical support from Huawei, and work together with engineers from Huawei to clear the faults.
4.9.1 Failure in Starting the U2000 XML Interface
4.9.2 Whether the U2000 Successfully Enables the XML Interface 4.9.3 Whether the U2000 XML Interface is Licensed