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.

Knowledge Base

System monitoring client can not start the security process

Publication Date:  2012-11-27  |   Views:  512  |   Downloads:  0  |   Author:  c00222574  |   Document ID:  EKB1000020318


Issue Description

In system monitoring client side, you can not start the security process.

Alarm Information


Handling Process

Step 1 Ensure License file is not corrupt. Open License file locally, see whether if can normally open and display.
Step 2 Make sure that the License has not expired.
Confirm that there is only a License License directory file and License file officially released.
NMS prompts License expired, please do not hesitate to buy a new license.
Step 3 Make sure that "sm_agent.xml" file in security starting process exists.
Please check whether there is a file" sm_agent.xml " in the Windows operating system% IMAP_ROOT% \ etc \ conf ".
Step 4 Ensure that the client and server-side physical connection is normal, trouble-free network card, another network cable must be properly connected to the network card.
Step 5 to ensure that the network management server NIC in License Management within. License file check network management server server network port MAC address corresponding to the ESN number. (ESN server network port MAC address calculated encrypt a string of 40 numbers or letters.)
License file in the path of the Windows operating system under "% IMAP_ROOT% \ etc \ conf \ license".
License and NIC is bound, in the application License, make sure that the ESN has been inserted in the corresponding network port MAC address of the network management server NIC. If you replace the card will cause failure License, you must apply for a new license.

Root Cause

License file failure.
License file is not the only or expired.
Start the security process file is missing.
The NIC is not connected properly.
The network management server NIC replacement causing License failure.