Hello,
If an error message is displayed, locate and rectify the fault as prompted.
Check whether the server has been started properly. Ensure that the server runs properly, the disk space of the server is not used up, and not many processes are started on the server. If many processes are started on the server, the memory usage is high.
Ensure that the server has been started properly.
You can log in to the U2000 System Monitor to view server information. If the server startup fails, see Failure to Start Certain Processes of the U2000 Server to address the issue.
Ensure that the disk space of the server is not used up.
To troubleshoot the full disk space on the server on Windows, perform the following operations:
Check that disk C is fully used, delete log files, and restart the U2000.
To troubleshoot the full disk space on the server on Solaris or SUSE Linux, perform the following operations:
Check that the space usage of the /opt directory reaches 100%.
Run the following command to check the distribution of files larger than 100 MB.
# find /opt -size +200000 -print
Software runs abnormally because temporary files on the server are improperly large. Delete temporary files from the /opt directory if they occupy large space.
Ensure that not many processes are started on the server.
After the U2000 server is started, do not access the JDE desktop (switch to the CED environment for the U2000 on the live network). Start the U2000 in CLI mode.
Verify that the entered user name and password are correct.
If a message indicating that the license file is invalid when you log in to the U2000 client, rectify the license fault according to How to Resolve the Problem that the License Does Not Take Effect and log in to the U2000 client.
Choose Help > License Management > License Information from the main menu (traditional style); alternatively, double-click System Management in Application Center and choose License Management > Licenes Information from the main menu (application style).
If the number of clients to log in exceeds the maximum number of clients allowed in the license, apply for a new license and update the U2000 license file.
If the U2000 server is installed on Windows, check and restore the ODBC data source settings on the U2000. For details, see Step 3 in Failure to Log In to the Database.
Check whether the versions of the client and server are consistent. If the versions are inconsistent, a message will be displayed asking you to upgrade the client. In this case, try to upgrade or reinstall the client.
Check whether the communication protocols used by the client and the server are consistent. If the protocols are inconsistent, modify the protocols so that the protocols are consistent.
NOTE:
Run the ssl_adm -cmd query command on the U2000 server to view the communication mode of the U2000 server. For details, see How to Set the Communication Mode on the U2000 server for the Single-Server System (Windows)How to Set the Communication Mode on the U2000 server for the Single-Server System (Solaris)How to Set the Communication Mode on the U2000 server for the Single-Server System (SUSE Linux)How to Set the Communication Mode of the Server in a High Availability System (Solaris, SUSE Linux).
Check the network between the client and server.
Generally, the communication bandwidth between the client and server is at least 2 Mbit/s and the packet loss ratio is smaller than 0.1%.
To check the network between the client and server, run the following command on Windows:
> ping -t IP_address_of_the_NMS
To check the network between the client and server, run the following command on Solaris:
# ping -s IP_address_of_the_NMS
Check whether the port between the client and server is shielded by firewall or viruses. Install a virus scanner, scan the entire disk, and remove viruses. If the client installed on the computer where the server belongs can log in to the server, but other clients cannot log in, check whether the port has been added to the Windows firewall. If not, perform the following operations to add the port to the Windows firewall:
NOTE:
Windows Server 2008 is used as an example to describe the procedures for adding a port to a firewall. The procedures vary according to OSs. For specific procedures, see the Windows help.
Choose Start > Control Panel.
In the Control Panel window, click windows Firewall.
In the windows Firewall window, click Advanced Setting.
In the Windows Firewall with Advanced Security dialog box, choose Inbound Rules from the left navigation tree and from New Rule the right navigation tree.
In the New Inbound Pule Wizard dialog box, select Port and click Next.
In Specific local ports, set Ports and click Next.
Select Allow the connection and click Next.
Click Next, set Name, and click Finish.
Log in to the U2000 client as the admin user and choose Administration > NMS Security > ACL.
On the U2000, you can set the client IP addresses that can be accessed. If the IP address of a client is not in the permitted range, the client cannot access the server. For details, see "Setting the Access Control List" in Chapter "Security Management" in the U2000 Administrator Guide. If NAT is used for IP address translation for communication between the client and server, ensure that the translated IP address is permitted in the ACL.
If the number of failed login attempts by using the same user exceeds 3, the login authority of the user is locked.
You can log in to the client again in 30 minutes (default) or unlock the user as another user that has the authority, such as user admin.
Check whether the system time is the current time. If not, modify the system time.
Check whether the 360 antivirus software has deleted some U2000 files. If yes, uninstall the 360 antivirus software and re-install the U2000.
Log in to NE Software Management, check the process list, and start all the processes with Automatic startup mode.
Create a user and use it to log in. For details, see "Setting the Maximum Number of Sessions" in U2000 Administrator Guide.
