When activating a virtual machine (VM) for agentless anti-malware protection and assigning it a security profile, the VM status in the DSM console goes from managed (Online) to Anti-Malware Driver Offline.
When you check the properties of the alert, the description section says:
The Agent/Appliance has reported that the Anti-Malware driver is not responding. Please check the system events for the computer to determine the cause of the failure.
This issue occurs when the VM’s guest OS entered a standby sleep state. The EPSec may lose communication with the vShield driver, resulting to "Anti-Malware Driver Offline" status in the DSM console.
- Check the VM Status.
- Using VMware vSphere client, log in to vCenter.
- Check the affected virtual machines whether the machine is suspended or hibernated due to power management.
- Isolate the issue.
- Make sure that the vShield drivers are installed. By default, VMware tools installation do not install vShield drivers. Perform installation using the "Complete" or "Customer" option and manually select this driver.
- Check all your setup versions. Refer to the Deep Security and VMWare compatibility matrix.
- Check if the VMware vShield Endpoint Thin Agent is running on the protected VM.
- Open the run dialog box in the virtual machine.
- Type the "msinfo32" command.
- Go to the Software Environment section > System Drivers > System Information applet.
- Make sure that the VM drivers, vmci and vsepflt, are running.
- Make sure that the VM version is 7 or above.
- Check the vShield License.
- Check the ESXi networking. Go to the vSphere Client, select ESX > Configuration > Networking.
Create vSwitch and port group after preparing ESX.
- Check the appliance’s networking – vNIC. Go to the vSphere Client, select ESX > Configuration > Networking.
- Check the value of Net.DVFilterBindIpAddress.
- Go to the vSphere client and select an ESX server.
- Navigate to Configuration > Advanced Settings > Net.
- Make sure that the Net.DVFilterBindIpAddress setting has a value of 169.254.1.1. If this is empty, enter the value and reboot the ESX server.
- Update the certificates and check the connection.
- Check the Deep Security Virtual Appliance (DSVA).
- Log on to DSVA via console or SSH.
- Execute the "ifconfig –a" command. The following should appear:
- Test the DSVA and ESX communication.
- From DSVA, ping the IP of vmservice-vmknic-pg (ex. 169.254.1.1). The AM process should listen to 48651. The TCP connection is established when protected VM is boot-up.
- Check the EPSec Service configuration.
- Connect to the vCentre or to the affected host using vSphere Client.
- Go to Configuration > Software > Advanced Settings.
- Scroll to the bottom and select UserVars.
- Look for the UserVars.VshieldEndpointSolutionsConfiguration field and double-check if there are any duplicate settings. You may copy the content to a Notepad and easily find any duplicated settings.
If there are duplicated settings, correct it and save the changes. If none, proceed to Step 13.
- Restart the vShield Endpoint Service on ESX/ESXi using the following command:
~ # /etc/init.d/vShield-Endpoint-Mux restart
The following results will appear:
- Check the vShield driver on ESXi.
- Log on to ESX via SSH.
- Execute the "ps |grep vShield-Endpoint-Mux" command. The following appears:
If the issue persists, collect the following and send to Trend Micro Technical Support:
- DSVA Diagnostic Package
- DSM Diagnostic Package
- Virtual Agent Diagnostic Package
- Copy of the /var/log/messages and /var/log/syslog logs inside the DSVA appliance
- ESXi version and build
- vShield Manager version and build
- Manually exported msinfo32 output as mentioned in Step 4