vnx event enabler - 4.9.3.0

8/19/2019 VNX Event Enabler - 4.9.3.0

1/12

EMC ® VNX™ Event EnablerVersion 4.9.3.0

Release NotesP/N 300-011-827

Rev A03

October 25, 2011

1

This document provides information about the latest release of EMCVNX Event Enabler software and related documentation. Topicsinclude:

◆ Product description.................................................................................. 2◆ New features and changes ...................................................................... 2◆ Known problems and limitations .......................................................... 3◆ Problem prevention.................................................................................. 5◆ Technical notes.......................................................................................... 7◆ Environment and system requirements................................................ 8◆ Documentation ....................................................................................... 10◆ Troubleshooting and getting help ......................................................... 11

Check the EMC Online Support website, http://support.EMC.com, forupdates to this document. Updates are made when a new version orpatch is released, or when new information is discovered.


2/12

2 EMC ®

VNX ™

Event Enabler Release Notes

Product description

Product description

The EMC® VNX™ Event Enabler (VEE) framework contains thefollowing facilities and is used to provide a working environment forthese facilities:

◆ VEE Common AntiVirus Agent (CAVA) provides an antivirussolution to clients using a VNX server. It uses anindustry-standard CIFS protocol in a Microsoft Windows Serverenvironment. CAVA uses third-party antivirus software toidentify and eliminate known viruses before they infect files onthe storage system. The Using VNX Event Enabler technicalmodule contains information about using CAVA.

◆ VEE CEPA is a mechanism whereby applications can register to

receive event notification and context from the VNX system.CEPA delivers to the consuming application both eventnotification and associated context (file/directory metadataneeded to make a business policy decision) in one message. TheUsing VNX Event Enabler technical module contains informationabout using CEPA.

◆ VCAPS is a mechanism for delivering asynchronous "post events"in batch mode. The delivery can be triggered based on a timeperiod or a number of events.

While the VEE framework includes both CAVA, CEPA, and VCAPS,

they can run independently.

New features and changes

File scanning cache option change

A default setting for a file scanning cache option that is used byVirusScan has been changed. With this change, network files may not be scanned after being cached. This issue occurs when the same file issent multiple times to an EMC VNX device. If you are using McAfee

VirusScan version 8.8 or later, readMcAfee's KnowledgeBase articlewhich can be found at:https://kc.mcafee.com/corporate/index?page=content&id=KB53708&cat=CORP_VIRUSSCAN_ENTERPRISE&actp=LIST forinstructions on how to prevent this condition.

http://localhost/var/www/apps/conversion/tmp/CEPA/index.htmhttp://localhost/var/www/apps/conversion/tmp/CEPA/index.htm


3/12

EMC ®

VNX ™

Event Enabler Release Notes 3

Known problems and limitation

Symantec Endpoint Protection

As of this release, Symantec Endpoint Protection version 12.1 is

supported.

Known problems and limitations

CAVA is for CIFS clients

The CAVA feature of the VEE product is for CIFS clients only. If NFSor FTP protocols are used to modify files, the files will not be scannedfor viruses. No UNIX antivirus application support is provided.

CEPA support

CEPA supports clients that run either the CIFS or NFS protocol only.If the FTP protocol is used to move or modify files, no events areprocessed or published for the files.

File-Level Retention

It is strongly recommended that the antivirus (AV) administratorupdates the virus definition files on all resident AV engines in theCAVA pools, and periodically run a full file system scan of the file

system to detect infected FLR files. The Using VNX Event Enabler technical module provides additional information about virusdefinition updates.

Microsoft Access

Do not scan Microsoft Access database files in real time. Files inside adatabase are not scanned.

Restricted Group GPO

CAVA requires the antivirus domain account (AV user account) to bein the local administrators group of the VNX for File CIFS server. Ifthe CIFS server has Restricted Group GPO enforced and the AV useraccount is removed from the local administrators group, after thenext CAVA restart, the status will change from ONLINE toAV_NOT_FOUND.


4/12

4 EMC ®

VNX ™


Known problems and limitations

To ensure the CAVA status remains ONLINE, you must either includethe corresponding AV user account in the Restricted Group, orremove the Restricted Group.

Using Microsoft SMB2

When using Microsoft SMB2 as the protocol between AV engines andthe VNX for File, the Microsoft Redirector uses a local cache fordirectory metadata on the machine where the AV engine resides. Bydefault, this cache is invalidated every 10 seconds.

As a consequence, the updates that are made to the server shareduring this period might not be seen in the cache. When this occurs,the AV engines cannot scan the files requested by CAVA because thecontents of the Redirector’s cache and the actual directory structure

on the server share do not match. The Data Mover’s server_logcontain the following SMB2 error message: file not found.

WorkaroundTo prevent this condition, disable the directory cache on the machineson which CAVA and AV engines are running by using the followingprocedure:

1. Open the Windows Registry Editor and navigate toHKLM\SystemCurrentControlSet\Services\LanmanWorkstation\Parameters.

2. Right-click Parameters and select New > DWORD Value.3. For the new REG_DWORD entry, type a name of

DirectoryCacheLifetime.

4. Set the value to 0 to disable DirectoryCacheLifetime.

5. Click OK.

6. Restart the machine.

Windows 64-bit operating systems

64-bit CAVA agent cannot work with 32-bit AntiVirus enginesThe 64-bit CAVA agent cannot work with a 32-bit AV engine. If youare using a 32-bit AV engine, you must use 32-bit CAVA. Similarly, ifyou are using a 64-bit AV engine, you must use the 64-bit CAVA.


5/12

EMC ®

VNX ™


Fixed bug

Loading a 32-bit driver on a 64-bit Windows operating system isdisallowed by Windows. When using CAVA with a 32-bitdriver-based AV engine, you must load the AV engine and

CAVA/VEE on a 32-bit Windows OS. This does not apply to anAPI-based AV engine.

A 32-bit API-based AV engine and 32-bit CAVA can be loaded on a64-bit OS. At this time, the only API-based AV engine supported withCAVA is Symantec SAV for NAS.

MS-RPC

In order to run VEE on Windows 64-bit operating systems, the VNXfor File -to-CEE communications must be over Microsoft RPC(MS-RPC). The version of VEE that runs on Windows 64-bit operatingsystems is supported with Celerra version 5.6.45 or later and VEE

version 4.5.0.4 or later.

Windows Server 2008

If you are using Windows Server 2008, you must manually compilethe cava.mof file while using the EMC cavamon sizing tool.

Fixed bugs

There were no bugs fixed in this release.

Problem prevention

The EMC Customer Service center has reported a number of callsconcerning the following issues. Take a moment to familiarizeyourself with these potential issues.

VNX Common AntiVirus Agent

Number of CAVA engines

It is possible to configure your EMC VNX installation with only oneCAVA engine. However, this non high-availability configuration canmake your installation susceptible to data unavailability in the eventthat the CAVA engine goes offline for any reason. The best methodfor preventing this type of outage is to increase the number ofavailable CAVA engines.


6/12

6 EMC ®

VNX ™


Problem prevention

Additional information for configuring the Common AntiVirusAgent can be found in the Using VNX Event Enabler technical module.This document describes the parameter settings that specify

shutdown actions to take when no servers are available.

Performance

If a large number of files need to be checked at the same time, theCAVA file checking process may be slow depending on the number ofthreads configured, the number of CAVA servers, and the speed ofthe CAVA servers.

If the CAVA servers cannot process file checks quickly enough, thenall antivirus (AV) threads become busy and the AV “collector queue”increases, indicating that file check requests are queueing up.Increasing the number of AV threads (10 by default) allows more files

to be checked in parallel and may improve performance.

However, the number of CAVA engines may need to be increased tosatisfy a heavy load.

Removing AV user from Data Mover password file

If you remove an AV user from the Data Mover password file, CAVAwill not work. Depending on the setting you have on CIFS, you coulduse up all the CIFS threads because they are used for virus checkingor CAVA will shut down CIFS altogether.


7/12

EMC ®

VNX ™


Technical note

Technical notes

VNX for File virus checking solution

Third-party antivirus engines

Table 1 lists the requirements for using CAVA with third-partyantivirus engines.

Table 1 Virus checking solution requirements

AV vendorVNX for File or CelerraOperating System version AntiVirus version

Computer Associates

eTrust r8.1 All currently-supportedversions1

Celerra AntiVirus Agent (CAVA) 3.4.0 andlater

eTrust r8

TrendMicro

ServerProtect for EMC NAS 5.3.1 All currently-supportedversions1


ServerProtect for EMC NAS 5.8

Sophos

AntiVirus 3.x

All currently-supportedversions1


AntiVirus 5.x

AntiVirus 6.x

AntiVirus 7.x

AntiVirus 9.x

Kaspersky

Kaspersky Anti-Virus for WindowsServers Enterprise Edition

5.6.46.4 and later Celerra Event Enabler (CEE) 4.5.1 andlater

McAfee

VirusScan 8.0i All currently-supportedversions1


VirusScan 8.7i

Symantec


8/12

8 EMC ®

VNX ™


Environment and system requirements

Configurationguidelines

Table 2 lists the configuration guidelines for the Common AntiVirusAgent. The values listed in this section represent the highest or lowestvalues tested by EMC. In some cases, actual capacities may exceedthe capacities tested by EMC.

Table 2 Virus checking guidelines

Environment and system requirementsFor the latest system requirements, consult the website or

documentation of the particular third-party AV engine manufacturer.The AV engine version may differ depending on the operatingsystem.

Table 3 details the minimum system requirements recommended byEMC for each AV server.

Symantec Endpoint Protection 12.1 All currently-supportedversions1

VNX Event Enabler (VEE) 4.9.3.0 and later

Symantec Endpoint Protection 11.06 5.6.48.x and later Celerra Event Enabler (CEE) 4.5.2.2 andlater

SAV for NAS 5.2.x All currently-supportedversions1


SAV for NAS 4.3.x

1.Currently supported NAS versions include the entire 5.6.x, 6.0.x , and 7.0.x families. Refer to the EMC E-LabTM Interoperability Navigator for the latest supported version information.

Table 1 Virus checking solution requirements (continued)

AV vendorVNX for File or CelerraOperating System version AntiVirus version

Guideline/specification Maximum tested value Comment

Virus checker filepending

90% of availableVNODES in system

The percentage of total cached open files available in the system that canbe pending on Virus Checking. An event is sent to the Control Stationwhen the maximum is reached. To change the default value, modify param viruschk.vnodeMax(default=2000) and/or paramviruschk.vnodeHWM(default=0x5a(90%). Parameter information canbe found in the Parameters Guide for VNX for File.


9/12

EMC ®

VNX ™


Environment and system requirement

Table 3 Minimum requirements for AV servers

Table 4 describes the VNX for File software, hardware, network, andstorage configurations.

Software Microsoft Windows Server or any Windows operating system compatible with the vendor’sconsumer application software.

Two kits are available:

• EMC_VEE_Pack_Win32_xxxx for installation on Windows 32-bit operating systems

• EMC_VEE_Pack_x64_xxxx for installation on Windows 64-bit operating systems

where xxxx = software version number

You cannot install both a 32-bit and a 64-bit version of the software on the same machine.

Note: Running VEE in the Windows on Windows (WOW) environment on a 64-bit platform isnot supported.

Search the EMC E-Lab Interoperability Navigator for consumer applications supported whenusing VNX Event Enabler.

Hardware A workstation with:

• 600-megahertz Pentium III-compatible or faster.

• 512 megabytes of RAM.

• 80 megabytes of free disk space.

Network The Windows network must contain a domain controller with Active Directory and DNSenabled.

Data Movers on VNX must be configured with the CIFS protocol. You cannot use a Virtual DataMover for the CIFS protocol. Configuring and Managing CIFS on VNX provides moreinformation on configuring the CIFS protocol.

Storage No specific storage requirements.

Hardware

A workstation with:

Intel Pentium III 700 MHz (or faster)• 512 MB RAM minimum

• 50 MB free disk space

SoftwareWindows Server or any Windows operating system compatible with the vendor’s consumerapplication software.

Network

CAVA must be running on a machine that is part of a valid Windows environment.

Note: Share-level authentication or stand-alone Windows servers are not supported when usingCAVA.


Table 4 System requirements


10/12

10 EMC ®

VNX ™


Documentation

Table 5 details the minimum system requirements for the CAVACalculator.

Table 5 Minimum requirements for the CAVA calculator

Documentation

VNX for File version 7.0This section lists the user documentation for VEE version 4.8.5.0software. These components can be downloaded from the EMCOnline Support website at http://Support.EMC.com .

Antivirus

Table 6 lists information for antivirus protection described in

technical modules and online help.

Software

• Microsoft Windows Server.

• Microsoft .NET Framework 1.1.

• CAVA Tools.

Hardware No specific hardware requirements.

Network No specific network requirements.


Table 6 Antivirus

Part number Name Description

Online help CAVA Calculator Describes using the CAVA Calculator sizing tool to estimate the number ofCAVAs required to provide a user-defined level of performance in a CAVApool, based upon user information.

Online help Common AntiVirus Management Explains how to modify CAVA virus-checking configuration parameters ona Data Mover from a Microsoft Windows server.

300-011-824 Using VNX Event Enabler Describes how to install and configure the VNX Event Enabler Frameworksoftware that provides a working environment for the CAVA and CEPAfacilities.

300-011-825 Getting Started with EMC VNXEvent Enabler

Helps you to verify the product shipment and set up an EMC Supportwebsite account.

http://powerlink.emc.com/


11/12

EMC ®

VNX ™


Troubleshooting and getting help

Troubleshooting and getting help

Where to get help

EMC support, product, and licensing information can be obtained asfollows:

Product information — For documentation, release notes, softwareupdates, or for information about EMC products, licensing, andservice, go to the EMC Online Support website (registration required)at: http://Support.EMC.com

Troubleshooting — Go to the EMC Online Support website. Afterlogging in, locate the appropriate Support by Product page.

Technical support — For technical support and service requests , goto EMC Customer Service on the EMC Online Support website. Afterlogging in, locate the appropriate Support by Product page and

choose either Live Chat or Create a service request. To open a servicerequest through EMC Online Support, you must have a valid supportagreement. Contact your EMC Sales Representative for details aboutobtaining a valid support agreement or to answer any questionsabout your account.

Note: Do not request a specific support representative unless one has beenassigned to your particular system problem.

EMC E-Lab

InteroperabilityNavigator

The EMC E-Lab Interoperability Navigator is a searchable,

web-based application that provides access to EMC interoperabilitysupport matrices. It is available at http://Support.EMC.com . Afterlogging in to the EMC Online Support website, locate the applicableSupport by Product page, find Tools, and click E-LabInteroperability Navigator.

300-011-817 VNX Event Enabler PublishingAgent API Guide

Describes how to create a CEPA configuration file, issue CEPA commandsusing the CLI and assign the EMC Event Notification Bypass privilege tosuppress third-party application events.

Table 6 Antivirus (continued)

Part number Name Description


12/12

Copyright © 2011 EMC Corporation. All rights reserved.

EMC believes the information in this publication is accurate as of its publication date. Theinformation is subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATIONMAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THEINFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIEDWARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires anapplicable software license.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks onEMC.com.

All other trademarks used herein are the property of their respective owners.

12 EMC ®

VNX ™


vnx event enabler - 4.9.3.0

Documents