Hi,  you could add those IP addresses on the viruschecker.conf. That would solve the problem avoiding these error messages, but will unbalance your CAVA servers ( three requests will be sent to the same CAVA server ). If this is your option, specify the addresses alternating the servers. For example ( first IP on the first server, then first IP of the second server, then second IP for the first server, then wsecond IP for the second server, and so on ).  The most appropriate solution is to avoid the use of multihomed CAVA servers. Another solution is to ensure these interfaces that are not listed on viruschecker.conf cannot communicate with the Data Mover like you said. This would work.  Gustavo Barreto.
Celerra NS-G8 running 5.6.50-2 CAVA Servers are Windows Server 2003 running SAV For NAS 5.2  We have a number of CAVA servers, each with several NICs: One for backups, one for management, and one to interface with the Celerra.  Each of these interfaces have their own IP address on a different network.  We currently have the CAVA servers running OK and are being used successfully by the Celerra.  The issue I'm facing is that it appears that the CAVA servers often attempt to access the Celerra using these other interfaces, not just the one that's been configured for CAVA.  We can see these connection attempts in the Celerra Manager Notifications log: "Invalid access from client to CHECK$", "Client (123.45.67.89 *backup interface*) is not a VC/CEPP server".   Can this be addressed by modifying the routing tables on the CAVA servers to not route communication from the other interfaces to the Celerra?  I came accross an EMC Powerlink article saying that these extra interfaces should be disabled, but we can't do that in our environment.
CAVA servers connecting to Celerra on wrong interfaces