Sometimes, after configuring a primary virus scanner, it no longer services client requests and does not appear in the list when you run vscan scanners on the system CLI. However, the previous configuration can be observed in old AutoSupport messages. To resolve this problem, perform the following steps.
- Ping the virus scanner to determine whether network connectivity exists between the storage system and the virus scanner.
If connectivity exists, proceed to Step 2.
- Determine whether the virus scanning software is properly installed and configured. If it is not functioning properly, see the virus scanner documentation or contact the manufacturer's technical support staff to identify and correct any problems. If there are no problems, proceed to Step 3.
- Ensure that the virus scanning software service is started. If it is not, restart the virus scanning application on the virus scan server.
Note: Even if the service appears to be started, it might be frozen. Restarting the service causes it to re-register with the storage system. The primary scanner is not configured on the secondary storage system side. Secondary virus scanners are configured on the secondary storage system only by using the vscan scanner secondary_scanners command.