The N2000 BMS server manages both broadband and narrowband services. After the N2000 BMS server is restarted, broadband NEs can be managed normally, but the narrowband NEs such as the UA5000 fall out of management and their icons are dimmed. These narrowband NEs cannot be pinged.
The N2000 BMS is in V200R011C03B008CP2005.
Communication with the device fails. This alarm is generated on the UA5000 NE and is queried on the N2000 BMS.
1. Perform a dialing test. The services are all normal.
2. The alarm indicating a failure to communicate with the device occurs within seconds after the server is restarted. You can infer that the N2000 BMS is not connected after it is restarted.
3. The broadband devices are not affected by the restart. Therefore, you can start with the difference in the management mode of narrowband devices. Through consultation, you know that the server is configured in the same network segment as the broadband devices, and that the narrowband devices in another network segment are managed through static routes.
4. The static routes may be lost during the restart of the N2000 BMS. Configure the static routes again. The N2000 BMS resumes its management of the narrowband NEs.
1. The network card on the server is faulty.
2. The network connection is faulty.
3. The N2000 software on the server is faulty.4. The database is faulty.
The N2000 BMS server can manage both the broadband service and the narrowband service in different network segments. In this case, the default network card on the server is configured with an IP address that is in the same network segment as the broadband service. To enable the server to manage the narrowband service, you should configure static routes from the narrowband NEs to the server. To prevent loss of routes during the restart of the system, add the static routes to the start items on the server as follows:
1. Write the following route starting script in the rc3 file in the path /etc on the SUN workstation: route add network address �netmask subnet mask gateway address.
Example: #route add 192.168.10.0 -netmask 255.255.255.0 10.11.201.254
2. On Windows, write the configured routes mentioned above in a batch processing file (*.bat) and add them to the start items of the system.