Dell PowerStore 1200T Using the Common Event Enabler 8.x on Windows Platforms - Page 65

Define AV machine IP addresses in viruschecker.conf, Send viruschecker.conf to the Data Mover

Page 65 highlights

Define AV machine IP addresses in viruschecker.conf About this task Steps 1. Open the viruschecker.conf file using an editor. 2. Locate the addr entry. 3. Add the IP addresses of all Windows Servers running the CAVA software. Use colons to separate multiple Windows Server IP addresses. Example: The first entry below identifies a single Windows Server, the second entry identifies multiple Windows Servers, while the third entry identifies a fully qualified domain name (FQDN): addr=192.16.20.29 addr=192.16.20.15:[2510:0:175:111:0:4:aab:ad2]: [2510:0:175:111:0:4:aab:a6f]:192.16.20.16:192.16.20.17 addr=wichita.nasdocs.emc.com NOTE: IPv6 addresses should be enclosed in square brackets to separate them from the colon delimiter that is used between multiple addresses. The addresses entered represent the Windows Servers that the VNX Data Mover or Unity NAS Server will send the UNC path of the files to scan. For multiple server installations, the UNCs are sent in a round-robin fashion to all Windows Servers configured with the CAVA software and the AV engine. 4. Save and close the viruschecker.conf file. Send viruschecker.conf to the Data Mover About this task This procedure is used for VNX systems. For Unity systems, upload the CAVA configuration by using either the Unity CLI or Unisphere software. Refer to the Unity Unisphere Command Line Interface User Guide for CLI commands. Instructions for retrieving the configuration file on Unity systems are described in Virus-checking continuation. You must put a copy of the viruschecker.conf file on each Data Mover in the domain. NOTE: If you customize a Data Mover's viruschecker.conf file by configuring the CIFSserver= parameter, ensure that you put the customized viruschecker.conf file on the correct Data Mover. Steps Copy the viruschecker.conf file from the Control Station to the /.etc directory on the Data Mover by using this command syntax: $ server_file -put viruschecker.conf viruschecker.conf where: = name of the Data Mover Output: server_2:done NOTE: ● Repeat this command for each Data Mover within the domain. ● If the viruschecker.conf file is missing from the /.etc directory, the VC client will not start. The following documents provide more information: ● EMC VNX Command Line Interface Reference for File provides detailed information on the server_file command. Unity and VNX CAVA Information 65

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84

Define AV machine IP addresses in viruschecker.conf
About this task
Steps
1.
Open the viruschecker.conf file using an editor.
2.
Locate the addr entry.
3.
Add the IP addresses of all Windows Servers running the CAVA software. Use colons to separate multiple Windows Server IP
addresses.
Example:
The first entry below identifies a single Windows Server, the second entry identifies multiple Windows Servers, while the
third entry identifies a fully qualified domain name (FQDN):
addr=192.16.20.29
addr=192.16.20.15:[2510:0:175:111:0:4:aab:ad2]:
[2510:0:175:111:0:4:aab:a6f]:192.16.20.16:192.16.20.17
addr=wichita.nasdocs.emc.com
NOTE:
IPv6 addresses should be enclosed in square brackets to separate them from the colon delimiter that is used
between multiple addresses.
The addresses entered represent the Windows Servers that the VNX Data Mover or Unity NAS Server will send the UNC
path of the files to scan. For multiple server installations, the UNCs are sent in a round-robin fashion to all Windows Servers
configured with the CAVA software and the AV engine.
4.
Save and close the viruschecker.conf file.
Send viruschecker.conf to the Data Mover
About this task
This procedure is used for VNX systems. For Unity systems, upload the CAVA configuration by using either the Unity CLI or
Unisphere software. Refer to the
Unity Unisphere Command Line Interface User Guide
for CLI commands. Instructions for
retrieving the configuration file on Unity systems are described in
Virus-checking continuation
.
You must put a copy of the
viruschecker.conf
file on each Data Mover in the domain.
NOTE:
If you customize a Data Mover’s
viruschecker.conf
file by configuring the
CIFSserver=
parameter, ensure
that you put the customized
viruschecker.conf
file on the correct Data Mover.
Steps
Copy the
viruschecker.conf
file from the Control Station to the
/.etc
directory on the Data Mover by using this
command syntax:
$ server_file
<movername>
-put viruschecker.conf viruschecker.conf
where:
<movername>
= name of the Data Mover
Output:
server_2:done
NOTE:
Repeat this command for each Data Mover within the domain.
If the
viruschecker.conf
file is missing from the
/.etc
directory, the VC client will not start.
The following documents provide more information:
EMC VNX Command Line Interface Reference for File
provides detailed information on the
server_file
command.
Unity and VNX CAVA Information
65