Boards and Subboards Are Displayed As UNKNOWN on the NE Panel of the U2000-IP

小虾米
小虾米  Junior  (1)
6 years 10 months ago  View: 3310  Reply: 0
1F

Keywords

NE adding

Case Information

U2000

OS

Database

NE

V100R009C00

Windows/Solaris/Linux

--

--

 

Symptom

Boards and subboards are displayed as UNKNOWN on the NE Panel of the U2000-IP.

This problem is usually caused by a failure to decouple the NE Panel after a master/slave switchover is implemented in an HA system.

U2000 V100R006C02, router series V600R005, ATN V200R001C02, and their later versions support NE Panel decoupling.

Cause Analysis

Possible causes are as follows:

l   The FTP service of the U2000 is not started.

l   The NE fails to connect to the U2000 through FTP.

l   NAT configurations are incorrect.

Problem Locating

                               Step 1      Choose Administration > Settings > Local xFTP Settings from the main menu.

Click Test FTP.

If the user name or password is incorrect, an error message is displayed. In this situation, enter the correct user name and password and test the FTP service again. Using the default FTP user name ftpuser is recommended.

If the test still fails, perform the following operations to restart the FTP service:

l   On Windows, run the following two files:

\oss\server\3rdTools\ftp\ Stop_ftp_win.bat

\oss\server\3rdTools\ftp\ Monitor_ftp_win.bat

l   On Solaris, perform the following operations:

a)     Run the following command to check the FTP service status:

# svcs |grep svc:/network/ftp

In the command output, "online" indicates that the FTP service has been started, whereas "offline" indicates that the service has been stopped.

b)     Stop the FTP service.

# svcadm disable svc:/network/ftp

c)     Restart the FTP service.

# svcadm enable svc:/network/ftp

d)     Test the FTP service again on the U2000 until the test succeeds.

                               Step 2      Check whether the value of the fixedServerName field in the sysconfigure.xml file of the \oss\server\etc\conf path is the IP address that can be used to communicate with the NE. If yes, skip this step. If not, go to the next operation.

Choose Administration > Settings > NAT Configuration Management from the main menu. Configure NAT information as shown in the following figure so that the NE can properly communicate with the U2000 through FTP.

 

The first two columns from left to right indicate the network segments to which the start and end NE IP addresses belong. The third column indicates the IP address, that is, the value of the fixedServerName field. The fourth column indicates the IP address used by the U2000 to communicate with the NE.

                               Step 3      Run the ftp command on the NE to connect to the U2000 server. Check whether the NE can successfully communicate with the U2000 server through FTP.

 

In the ftp U2000 server IP address command, no parameter can be entered after U2000 server IP address.

However, on the live network, some parameters may be added at the end of U2000 server IP address, for example, ftp U2000 server IP address vpn-instance __dcn_vpn__.

In this situation, the set net-manager vpn-instance instance name command must be run on the NE to configure a VPN instance.

                               Step 4      Select the NE, right-click, and choose Synchronize NE Configuration Data from the shortcut menu.

In the Synchronization Details dialog box, select the synchronized NE and view NE details. Ensure that associated configurations are successfully synchronized through FTP.

 

                               Step 5      Exit the U2000 client and log in again. Then access the NE Explorer and click Synchronize Description Files in the lower right corner of the NE Panel. Wait for about 2 minutes and check whether the problem has been solved.

----End