A customer requires anti-virus checking in their VNX for File implementation. They are planning to
configure CIFS servers in multiple domains, using VDMs to host the CIFS servers. They want to
know how many additional CIFS servers and VDMs should be created to accommodate CAVA in
their design.
What should you tell them?

Your customer has an existing VNX for File implementation which is entirely managed via
Unisphere using EMC’s best practice recommendations. The Windows clients are Windows 7 Pro.
There is a Replicator asynchronous DR solution in place that allows recovery of the CIFS servers
as well as the data file systems.
The customer has acquired a new business which uses NFSv3-based RHEL Linux clients. They
want to present simultaneous NFS exports of file systems that are currently shared by Windows to
the RHEL clients. They also want the Replicator solution to provide DR protection that allows the
new clients to meet the same RPO as the existing clients.
Which change to their environment is required to meet the customer’s needs?

A large, enterprise-level customer recently purchased a pair of VNX Gateways with VMAX
backend storage arrays to provide File services. Their requirements include the ability to have
near-synchronous, off-site data protection and to be able to easily load balance services across
two sites. All CIFS and NFS services will be configured within VDMs for ease of logical
administration.
Which EMC technologies should be recommended?

An enterprise-level customer recently purchased a pair of VNX Gateways with VMAX backend
storage arrays to provide File services. Their requirements include the ability to have synchronous,
off-site data protection. All CIFS and NFS services will be configured within VDMs for ease of
logical administration.
Which EMC technology should be recommended?

A customer has two IP Replicated VNX systems: VNXA is the Primary system; VNXB is the DR
system. VNXA is configured with VDMs containing CIFS servers, has secmap cache disabled, and
runs a primary Usermapper. VNXB is configured as a DR target system and runs a secondary
Usermapper.
During failover testing, VNXA is failed over and shut down to simulate a site outage. The small
number of Linux users that access the CIFS data via NFS find that they no longer have the same
permissions as when accessing from the primary site. Additionally, the UID ownership of many
files has changed.
What could be the cause of the change in permissions?

A customer has two IP Replicated VNX systems: VNXA is the Primary system; VNXB is the DR
system. VNXA is configured with VDMs containing CIFS servers, has secmap cache disabled, and
runs a primary Usermapper. VNXB is configured as a DR target system and runs a secondary
Usermapper.
During failover testing, VNXA is failed over and shut down to simulate a site outage. The small
number of Linux users that access the CIFS data via NFS find that they no longer have the same
permissions as when accessing from the primary site. Additionally, the UID ownership of many
files has changed. On investigation it is found that the secondary Usermapper Db contains far
fewer, and different, mappings compared to the primary.
Why would this be the case?

What is the purpose of the Usermapper on VNX?

What is a characteristic of secmap?

Which VNX virtual device can be deployed independently of pre-existing customer Ethernet
configurations?

You are trying to create a virtual network device in Unisphere. There are four physical network
connection devices on the Data Mover, but only two appear on the Unisphere device creation
page.
Why?