The security process cannot be started on the VSM System Monitor.
Step 1 Ensure that the license file is intact.Open the license file locally to check whether it can be opened and displayed normally.
Step 2 Ensure that the license does not expire.
Ensure that only one license file exists in the license directory and the license file is an officially released one.
If the VSM prompts that the license has expired, purchase a new license as soon as possible.
Step 3 Ensure that the security process start file sm_agent.xml is available.
On Windows, check whether this file exists in %IMAP_ROOT%\etc\conf.
Step 4 Ensure that the client and the server are connected properly, the network adapters work normally, and the cables are correctly connected to the network adapters.
Step 5 Ensure that the license covers all the NICs of the VSM server. Check whether the ESN corresponding to the MAC address of the network interface on the server exists in the license file. An ESN is a string consisting of 40-digit numerals or letters obtained by encrypted calculation on the MAC addresses of the VSM server network interface.
On Windows, this license file is in %IMAP_ROOT%\etc\conf\license.
The license is bundled with the NICs. Ensure that the ESN of the NICs of the VSM server is added when you apply for a license. Replacing a NIC invalidates the license. In this case, you need to apply for a new license.
l The license file is damaged.
l The license file is not unique or expires.
l The security process start file is unavailable.
l The network adapter is not correctly connected.
l The network adapter on the VSM server is replaced, which invalidates the license.
Figure 1-1 Troubleshooting flowchart of the fault that the security process cannot be started