No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


Creation of NE Fails

Publication Date:  2012-07-23 Views:  360 Downloads:  0

Issue Description


Alarm Information


Handling Process

1.         Check the types of added NEs and ensure the types are correct.

If you are not sure about NE types, it is recommended that you use automatic searching to add NEs. After NEs are added, you can check the properties of the NEs to check the NE types.

Check whether the NMS supports the NEs of these type. If no, you are advised to add NEs to the NMS as third-party ones.

2.         Check whether the disk space usage is 100% on the VSM server.

If there is no available disk space, clean up the disk on the VSM server.

3.         Check whether this NE already exists on the VSM. If it has been added to the VSM, you do not need to add it.

Ensure that the MAC address of the NE is unique. To check whether the NE has been added to the VSM, perform the following steps:

Press Ctrl F. In the Search dialog box that is displayed, enter the keyword and click Locate > Locate to Topo. Then, you can locate this NE.

4.         Check whether the System Log Collector runs normally.Log in to the VSM System Monitor.In the main window of the VSM System Monitor, click the Process Monitor tab and check whether the status of the System Log Collector is Running.If this process is not started, start this process and set Startup Mode to Automatic.

5.         Check the license consumption and verify whether the adding of new devices is allowed by the license.

1.         Log in to the VSM client and choose Help > License Management > License Information on the main menu.

2.         In the License Information dialog box, check the Resource Control Item tab and ensure that the License Consumption is smaller than the License Capacity.

3.         If the license consumption equals to the license capacity, remove some NEs and try again. If the License capacity is 0, buy a license.

6.         Log in to the system monitoring client and click the Process Monitor tab. Check whether the NE manager process for the NE to be added is present. Alternatively, log in to the SQL Server Enterprise Manager to check whether the NE manager database corresponding to the NE to be added exists.

NE Type

VSM System Monitor NE Manager Process

SQL Server Enterprise NE Manager Database

NMS Installation Components

Security NE

Security NE Manager


Security Network Element Management

Router NE

Router NE Manager


Router Network Element Management

Service Gateway

Service Gateway Manager


Switch NE(Box)

Switch NE Manager(Box)


Switch Network Element Management

Switch NE (Frame)

Switch NE Manager(Frame)


If the process cannot be located, use the VSM maintenance tool to added uninstalled components or reinstall the VSM with all components selected.   After new components are added or the VSM is reinstalled, restart the VSM server.

7.         On the system monitoring client, check the NE manager process of the NE to be added and the Device Access Manager process. Ensure that the processes are started.
Otherwise, start the processes and try again.
8.         If a process cannot be started, check whether the process is included in the items controlled by the license.
1.         In the main menu, choose Help > License Management > License Information.
2.         In the License Information dialog box, click the Function Control Item tab. Ensure that the NE management component for the NE to be added is present.
3.         Otherwise, buy a license.
9.         Check whether SNMP parameters are specified correctly.
1.         Check whether SNMP parameters are set correctly on the NE.
2.         Check whether the SNMP settings on the NE are the same as those on the VSM server.
10.      Check the DCN network connectivity.
1.         Ping the IP address of the NE from the VSM server to check the connectivity.
2.         Ensure that the connections between the VSM server and the NE are not blocked by applications such as ACL, port mappings, or blacklists.

Root Cause