EMC® VNX™ Series

Release 7.0

Configuring Virtual Data Movers on VNX™

P/N 300-011-844
REV A01

EMC Corporation
Corporate Headquarters:
Hopkinton, MA 01748-9103
1-508-435-1000
www.EMC.com
 Copyright © 1998 - 2011 EMC Corporation. All rights reserved.
Published February 2011
EMC believes the information in this publication is accurate as of its publication date. The
information is subject to change without notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED "AS IS." EMC CORPORATION
MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO
THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Use, copying, and distribution of any EMC software described in this publication requires an
applicable software license.
For the most up-to-date regulatory document for your product line, go to the Technical
Documentation and Advisories section on EMC Powerlink.
For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on
EMC.com.
All other trademarks used herein are the property of their respective owners.
Corporate Headquarters: Hopkinton, MA 01748-9103

2 Configuring Virtual Data Movers on VNX 7.0

 Contents

Preface.....................................................................................................7

Chapter 1: Introduction.........................................................................11
System requirements.............................................................................................12
Restrictions.............................................................................................................12
Cautions and warnings.........................................................................................13
User interface choices...........................................................................................14
Related information..............................................................................................15

Chapter 2: Concepts.............................................................................17
Overview................................................................................................................18
CIFS servers in a VDM..........................................................................................22
VDM states.............................................................................................................22
Create a VDM in the loaded state.............................................................23
Create a VDM in the mounted state.........................................................23
Summary of the loaded and mounted states...........................................24
Changing the VDM state......................................................................................24
Moving a VDM......................................................................................................24
Unloading a VDM.................................................................................................26
Planning considerations.......................................................................................27
VDM names..................................................................................................28
VDM root file system size, layout, and inode density...........................28
Internationalization modes........................................................................29
Name resolution when moving VDMs....................................................29

Chapter 3: Configuring.........................................................................31
Create a VDM.........................................................................................................32

Configuring Virtual Data Movers on VNX 7.0 3

Contents

Create a VDM by using default values....................................................32

Create a slice for a VDM root file system.................................................33
Create a stripe for a VDM root file system..............................................34
Create a metavolume for a VDM root file system..................................34
Create the root file system for a VDM......................................................35
Create a VDM in the loaded state from an existing file system...........36
Verify the size of a root file system...........................................................37
Create a VDM in the loaded state that uses Automatic Volume
Management...........................................................................................38
Create a VDM in the mounted state.........................................................39
Create a user file system.......................................................................................40
Create a mount point for a user file system.......................................................41
Mount a user file system......................................................................................42
Configure an interface..........................................................................................43
Create a CIFS server in a VDM............................................................................44
Join the CIFS servers to a domain.......................................................................45
Create shares for CIFS servers in a VDM...........................................................46
Verify the CIFS shares in a VDM...............................................................46
Convert a VDM from ASCII to Unicode mode.................................................47

Chapter 4: Managing............................................................................49
Display the server table for a VDM....................................................................50
Display the attributes of a VDM.........................................................................50
Display the CIFS protocol configuration...........................................................51
Display a list of mounted or temporarily unmounted file systems...............52
Display the DNS configuration...........................................................................53
Display the time services configuration.............................................................54
Display parameters for configured interfaces...................................................54
Display the network connectivity for a Data Mover........................................55
Change the VDM state..........................................................................................56
Unload a VDM temporarily.................................................................................57
Unload a VDM permanently...............................................................................58
Rename a VDM......................................................................................................59
Move a VDM when using different IP addresses.............................................60
Configure the target Data Mover..............................................................61
Configure DNS on the target Data Mover...............................................62
Configure time services on the target Data Mover.................................63
Start the CIFS service..................................................................................63
Move the VDM to the target Data Mover................................................65

4 Configuring Virtual Data Movers on VNX 7.0

 Contents

Move a VDM when using the same IP address................................................67

Take down the interface on the source Data Mover...............................68
Delete the interface on the source Data Mover.......................................69
Delete a VDM.........................................................................................................70
Use VDMs and NDMP backup...........................................................................71

Chapter 5: Troubleshooting..................................................................73
EMC E-Lab Interoperability Navigator..............................................................74
Troubleshooting CIFS server accessibility errors..............................................74
Troubleshooting VDM unloading errors...........................................................74
Error messages.......................................................................................................74
EMC Training and Professional Services...........................................................75

Glossary..................................................................................................77

Index.......................................................................................................79

Configuring Virtual Data Movers on VNX 7.0 5

Contents

6 Configuring Virtual Data Movers on VNX 7.0

 Preface

As part of an effort to improve and enhance the performance and capabilities of its product lines,
EMC periodically releases revisions of its hardware and software. Therefore, some functions described
in this document may not be supported by all versions of the software or hardware currently in use.
For the most up-to-date information on product features, refer to your product release notes.
If a product does not function properly or does not function as described in this document, please
contact your EMC representative.

Configuring Virtual Data Movers on VNX 7.0 7

 Preface

Special notice conventions

EMC uses the following conventions for special notices:

CAUTION: A caution contains information essential to avoid data loss or damage to the system
or equipment.

Important: An important note contains information essential to operation of the software.

Note: A note presents information that is important, but not hazard-related.

Hint: A note that provides suggested advice to users, often involving follow-on activity for a
particular action.

Where to get help

EMC support, product, and licensing information can be obtained as follows:

Product information — For documentation, release notes, software updates, or for

information about EMC products, licensing, and service, go to the EMC Online Support
website (registration required) at http://Support.EMC.com.
Troubleshooting — Go to the EMC Online Support website. After logging in, locate
the applicable Support by Product page.
Technical support — For technical support and service requests, go to EMC Customer
Service on the EMC Online Support website. After logging in, locate the applicable
Support by Product page, and choose either Live Chat or Create a service request. To
open a service request through EMC Online Support, you must have a valid support
agreement. Contact your EMC sales representative for details about obtaining a valid
support agreement or with questions about your account.

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

Your comments
Your suggestions will help us continue to improve the accuracy, organization, and overall
quality of the user publications.
Please send your opinion of this document to:

8 Configuring Virtual Data Movers on VNX 7.0

 Preface

[email protected]

Configuring Virtual Data Movers on VNX 7.0 9

 Preface

10 Configuring Virtual Data Movers on VNX 7.0

 1

Introduction

A Virtual Data Mover (VDM) is an EMC VNX software feature that enables
the grouping of file systems and CIFS servers into virtual containers. Each
VDM contains all the data necessary to support one or more CIFS servers
and their file systems. The servers in a VDM store their dynamic
configuration information (such as local groups, shares, security credentials,
audit logs, and so on) in a configuration file system. A VDM can then be
loaded and unloaded, moved from Data Mover to Data Mover, or
replicated to a remote Data Mover as an autonomous unit. The servers,
their file systems, and configuration data are available in one virtual
container.
This document is part of the VNX information set and is intended primarily
for VNX for file administrators.
Topics included are:
◆ System requirements on page 12
◆ Restrictions on page 12
◆ Cautions and warnings on page 13
◆ User interface choices on page 14
◆ Related information on page 15

Configuring Virtual Data Movers on VNX 7.0 11

Introduction

System requirements
Table 1 on page 12 describes the EMC® VNX™ software, hardware, network, and storage
configurations required for using VDMs as described in this document.

Table 1. System requirements

Software VNX version 7.0

Hardware VNX
Network IP network
®
Storage EMC Symmetrix or EMC VNX for Block
Sufficient disk space for VDM root file systems

Note: If there is not enough disk space to accommodate the VDM root file system, the
command to create a VDM returns a no free disks available response.

Restrictions
The following restrictions apply to VDMs:
◆ In addition to CIFS servers that are created within a VDM, a global CIFS server is required
for antivirus functionality. A global CIFS server is a CIFS server that is created at the
physical Data Mover level.
◆ A default CIFS server and CIFS servers within a VDM cannot coexist on the same Data
Mover. A default CIFS server is a global CIFS server that is assigned to all interfaces, and
CIFS servers within a VDM require specified interfaces. If a VDM exists on a Data Mover,
a default CIFS server cannot be created.
◆ VDM supports CIFS and Security = NT mode only.
◆ The VDM feature does not support UNIX and SHARE mode, iSCSI, VNX Data Migration
Service (migration file systems mounted within VDMs), or resource allocation (CPU,
memory, and so on).
◆ A full path is required to back up VDM file systems with NDMP backup and the
server_archive command. An NDMP example is /root_vdm1/ufs1. A server archive
example is server_archive <movername> -w -f /dev/clt4l0/ -J /root_vdm1/ufs1.
◆ IP replication failover support for local groups must include VDMs.

12 Configuring Virtual Data Movers on VNX 7.0

 Introduction

MPFS restrictions with VDM

The following restrictions apply to Multi-Path File System (MPFS):

◆ From an MPFS Windows client, you can map shares from only one CIFS server per
Data Mover or VDM within the Data Mover. If you map shares from more than one
CIFS server, the MPFS Windows client might be denied access or file data corruption
might occur.
◆ MPFS does not allow duplicate NetBIOS names on the same physical Data Mover or
VDMs within the Data Mover.

NFS restrictions with VDM

VNX does not support creating NFS exports on VDMs. However, you can create NFS
exports on the Data Movers in which the VDM is configured. The NFS client can thus
access the file systems mounted on this particular VDM.
The following restrictions apply:

◆ As the NFS exports are created on the physical Data Movers, they do not constitute
a part of the VDM configuration. Hence the NFS exports are not carried over if the
VDM is moved to another physical Data Mover, or failed over to a remote VNX in
case of replication.
◆ You cannot restrict the NFS export to a specific VDM. However, in this case, you can
use the VLAN option of the server_export command. It specifies that all the hosts
belonging to the specified VLAN ID will have the access to the exported file sytem.
The EMC VNX Command Line Interface Reference for File provides more information
on this.
◆ You can perform the NFS export of a file system mounted on the VDM by using the
CLI server_export command and not by using EMC Unisphere™.
◆ You can access the data on a VDM mounted file system from an NFS client by using
celerra:/root_vdm_X/fs_name, where X is a consecutive number assigned by VNX
when you create the VDM. You can use the NFS export alias to change the view of
the NFS exports to the client. Configuring NFS on VNX provides more information on
NFS.

Cautions and warnings

If any of this information is unclear, contact your EMC Customer Support Representative
for assistance:
◆ After a VDM is converted to Unicode mode, it cannot be converted to ASCII mode.
◆ Converting a VDM by using the -ConvertI18N option does not trigger the file or directory
name conversion (from non-ASCII to Unicode) of user file systems mounted on the VDM.
You might need to convert the file or directory names separately by using the uc_config

Cautions and warnings 13

Introduction

-convert command if you have non-ASCII file or directory names in the user file systems.
Using International Character Sets on VNX for File provides more information.
◆ The root file system of a Data Mover or a VDM does not support automatic file system
extension.

User interface choices

VNX offers flexibility in managing networked storage that is based on your support
environment and interface preferences. This document describes how to configure a VDM
by using the VNX command line interface (CLI). You can also perform all of these tasks by
using the management applications, such as EMC Unisphere.
For additional information about managing VNX:
◆ EMC VNX Documentation on the EMC Online Support website
◆ EMC Unisphere online help
◆ Application’s online help system on the EMC VNX for File Documentation on the EMC
Online Support website
Installing Management Applications on VNX for File includes instructions on launching
Unisphere, and on installing the Microsoft Management Console (MMC) snap-ins and the
Active Directory Users and Computers (ADUC) extensions.

14 Configuring Virtual Data Movers on VNX 7.0

 Introduction

Related information
For specific information related to the features and functionality described in this document,
refer to:

◆ VNX Glossary
◆ EMC VNX Command Line Interface Reference for File
◆ Celerra Network Server Error Messages Guide
◆ Configuring and Managing CIFS on VNX
◆ Configuring NDMP Backups to Disk on VNX, and your specific backup software vendor's
similar documentation
◆ Managing Volumes and File Systems for VNX Manually
◆ Managing Volumes and File Systems with VNX Automatic Volume Management
◆ Problem Resolution Roadmap for VNX
◆ Using VNX Replicator
◆ Using International Character Sets on VNX for File
◆ EMC Unisphere online help
◆ VNX for File man pages

Related information 15
Introduction

16 Configuring Virtual Data Movers on VNX 7.0

 2

Concepts

Topics included are:

◆ Overview on page 18
◆ CIFS servers in a VDM on page 22
◆ VDM states on page 22
◆ Changing the VDM state on page 24
◆ Moving a VDM on page 24
◆ Unloading a VDM on page 26
◆ Planning considerations on page 27

Configuring Virtual Data Movers on VNX 7.0 17

Concepts

Overview
VDMs enable system administrators to group file systems and CIFS servers. Each VDM
contains the necessary information to support one or more CIFS servers. Each VDM has
access only to the file systems mounted to that VDM. This provides a logical isolation between
the VDM and the CIFS servers it contains. A VDM can be moved from one physical Data
Mover to another.
Each VDM stores its configuration information in a VDM root file system, which is a directory
within the root file system of the physical Data Mover. No data file systems are stored within
the VDM root file system. All user data is kept in user file systems.
Use VDMs for the following:
◆ To partition or group file systems and CIFS servers, users see only the file systems on
the VDM
◆ As part of a replication data-recovery strategy
When you create a VDM, a root file system is created for the VDM. This file system stores
the server configuration information for the CIFS servers created within the VDM. The VDM
root file system stores the majority of the CIFS servers' dynamic data, which includes:
◆ Local group and share databases for servers in the VDM
◆ CIFS server configuration (computer names, interface names, and so on)
◆ VNX home directory information for servers in the VDM
◆ Auditing and Event Log information
◆ Kerberos information for servers in the VDM

18 Configuring Virtual Data Movers on VNX 7.0

 Concepts

Figure 1 on page 19 shows the VDM container.

Figure 1. The VDM container

Having the file systems and the configuration information contained in a VDM:
◆ Allows replication of the CIFS environment
◆ Enables system administrators to move CIFS servers within a VDM from one physical
Data Mover to another
You can access the data on a VDM mounted file system from an NFS client by using
celerra:/root_vdm_X/fs_name, where X is a consecutive number assigned by VNX when
you create the VDM. When a user or system creates the root file system, the name of the
root file system is root_vdm_fs_<vdm name>. A user can delete the VDM root file system
only when the VDM is deleted and it is irretrievable. A user can export NFS through a Data
Mover rather than a VDM because the VDM functionality does not support NFS. If a VDM
is unmounted or moved to another Data Mover, NFS exports of the mounted file systems
on that VDM will be invalid. A user must reconfigure NFS exports if a VDM is moved to
another Data Mover. Configuring NFS on VNX provides details about NFS access to file
systems mounted on a VDM.
In contrast, a physical Data Mover supports NFS servers and CIFS servers, where each server
has the same view of all server resources. All configuration and control data is stored in the
root file system of a physical Data Mover. All event logs are global to all servers and are
stored in the root file system of the physical Data Mover. This reduces both the isolation
and the ease of moving servers between Data Movers. While it is beneficial for some
environments to consolidate multiple servers into one physical Data Mover, isolation between
servers is required in others. For example, for Internet Service Providers (ISPs) or where

Overview 19
Concepts

data from various departments must be hosted on the same physical Data Mover, VDMs
can play an important role.
Figure 2 on page 20 shows a typical physical Data Mover without VDM implementation.

Figure 2. Physical Data Mover without VDM implementation

In addition to passwd, group, viruschecker.conf, Group Policy Object (GPO) cache, and
Kerberos files, the physical Data Mover contains all configuration files on the VDM. The
VDM configuration file is a subset of the configuration files on the physical Data Mover.
Figure 3 on page 21 shows a physical Data Mover with the VDM implementation. A VDM
is an independent CIFS subset of a physical Data Mover. The physical Data Mover contains
the GPO information (in GPO cache) for all CIFS servers on the physical Data Mover, but
the GPO configuration that the CIFS servers follow is downloaded from the Active Directory.

20 Configuring Virtual Data Movers on VNX 7.0

 Concepts

GPO policies work the same for CIFS servers created at the physical Data Mover or the VDM
level.

Figure 3. Physical Data Mover with VDM implementation

You can configure the following at the physical Data Mover level, but not at the VDM level:
◆ Usermapper
◆ passwd/group file
◆ User mappings in Active Directory (VNX UNIX Users and Groups Property Page
Extension)

Overview 21
Concepts

◆ NIS
◆ DNS
◆ NTP
◆ Internationalization (I18N) mode: Unicode or ASCII
◆ Virus Checker
◆ CIFS stop/start/delete operation for CIFS service
◆ Routing
◆ Network interface
◆ Parameters
◆ Standby Data Mover assignment and failover policy
Operations at the Data Mover level that affect all VDMs on the physical Data Mover:
◆ Stop, Start, Delete (CIFS, MPFS, viruschk, rip)
◆ Data Mover failover
The VDM concepts explained in this section are:

CIFS servers in a VDM

Users with rights to the C$ share of a global CIFS server can see all the file systems mounted
to the physical Data Mover as well as the VDMs within it.
Users with rights to the C$ share of a specific VDM can see only the file systems mounted
on that VDM.
The local administrator group controls the rights to C$ on a CIFS server.
Access to the files and directories within the file systems is determined by access control
entries within the access control levels. Create a CIFS server in a VDM on page 44 describes
the procedure to create a CIFS server in a VDM.
Configuring and Managing CIFS on VNX provides more information.

VDM states
You can create VDMs in one of two states:
◆ Loaded
◆ Mounted

22 Configuring Virtual Data Movers on VNX 7.0

 Concepts

Create a VDM in the loaded state

In the loaded state, a VDM is fully functional and active. The CIFS servers in a loaded VDM
are running and serving data. A VDM must be in the loaded state to allow configuration
changes, such as the addition of CIFS servers or exports.
You can load a VDM on only one physical Data Mover at a time. If you need to move the
VDM, the network interfaces used by its CIFS servers must be available on the destination
Data Mover. You cannot load a VDM within a VDM.
When creating a loaded VDM, consider the following:
◆ If no state is specified, the VDM is created in the loaded (default) state.
◆ If a name is not specified for the VDM or its root file system, a default name is assigned,
as described in VDM names on page 28.
◆ The root file system is created from an existing storage pool. The selection of the storage
pool is based on whether the physical Data Mover is in a mirrored configuration. In a
mirrored configuration, a mirrored storage pool is selected. Otherwise, a nonmirrored
storage pool is selected.
◆ The default size of the root file system is 128 MB (as for a physical Data Mover).
Create a VDM by using default values on page 32 describes the procedure to create a VDM
by using only default values.

Create a VDM in the mounted state

You can create a VDM in the mounted state to use it as the destination in a replication
relationship. A mounted VDM is inactive and the associated CIFS servers are unavailable.
You cannot make data changes except those replicated from the source. After you create the
mounted VDM, a VDM root file system exists on the destination. You can replicate data
from the root file system on the source side to the root file system on the destination side.
In the event of failover, when using the EMC VNX Replicator™, the destination side might
be called on to act as the source. The VDM file systems on the destination side include the
configuration data necessary to change the VDM state to loaded.
Using VNX Replicator provides more information on using mounted VDMs and VNX
Replicator.

VDM states 23
Concepts

Summary of the loaded and mounted states

Table 2 on page 24 summarizes the loaded and mounted states for VDMs.

Table 2. Summary of the loaded and mounted states

VDM state CIFS active User file systems VDM reloaded at boot
Loaded Yes Accessible Yes

Mounted No Inaccessible No

Changing the VDM state

CIFS servers in a VDM run only while the VDM is in the loaded state. A loaded state is also
required to allow VDM configuration changes, such as adding new CIFS servers or new
shares.
You can change a VDM from the loaded state to any of the following states:
◆ Mounted
◆ Temporarily unloaded (tempunloaded)
◆ Permanently unloaded (permunloaded)
Changing the state to mounted, tempunloaded, or permunloaded shuts down the CIFS
servers in the VDM, by making the file systems inaccessible to the clients through the VDM.
Unloading a VDM on page 26 explains the tempunloaded and permunloaded states. Change
the VDM state on page 56 provides the procedure for changing the VDM state.

Moving a VDM
When moving a VDM from one physical Data Mover to another, the Control Station performs
the following operations:
◆ Unmounts all file systems on that VDM
◆ Unloads the VDM from the source Data Mover
◆ Loads the VDM and mounts all file systems on the target Data Mover
For every CIFS server in a VDM, you must have that CIFS server’s interfaces available and
identically named on the physical Data Mover to which you are moving the VDM. Configuring
and Managing CIFS on VNX describes setting up CIFS servers and their interfaces.
You must consider the update time of either of these static files: Domain Name System
(DNS) or Windows Internet Naming Service (WINS), when you try to access the VDM after

24 Configuring Virtual Data Movers on VNX 7.0

 Concepts

moving it to a physical Data Mover with a different IP address. Name resolution when
moving VDMs on page 29 provides more information.
Move a VDM when using different IP addresses on page 60 and Move a VDM when using
the same IP address on page 67 provide the procedures for moving a VDM to another
physical Data Mover.

Moving a VDM 25
Concepts

Internationalization modes
When moving a VDM, the -ConvertI18N option is needed only when the VDM is moved
from an ASCII Data Mover to a Unicode Data Mover. If you attempt to move an ASCII
Data Mover to a Unicode Data Mover without specifying this option, the operation fails
with the error message: Incompatible I18N mode.

Unloading a VDM
Unlike a state change from loaded to mounted, a state change from loaded to unloaded
requires the VDM to have no mounted file systems. The VDM root file system is not deleted
and is available to load. You might use the unloaded state when you want to stop all activity
on the VDM, but do not want to delete the VDM root file system with its configuration data.
When unloading a VDM from a physical Data Mover, you must specify whether to do so
permanently or temporarily:
◆ In the permanently unloaded (permunloaded) state, the VDM file system is not mounted
on the physical Data Mover, and is not remounted or reloaded on restart.
◆ In the temporarily unloaded (temunloaded) state, the VDM root file system is not mounted
on the physical Data Mover, but is remounted or reloaded on restart.
Unload a VDM temporarily on page 57 and Unload a VDM permanently on page 58 describe
the related procedures.
Table 3 on page 26 summarizes the unloaded states.

Table 3. Summary of the unloaded states

VDM state CIFS running User file systems VDM reloaded at boot
Permanently unloaded No Inaccessible No
Temporarily unloaded No Inaccessible Yes

26 Configuring Virtual Data Movers on VNX 7.0

 Concepts

Planning considerations
Consider the following guidelines before creating, configuring, or managing VDMs:
◆ VDM names on page 28
◆ Internationalization modes on page 29
◆ Name resolution when moving VDMs on page 29

Planning considerations 27
Concepts

VDM names
By naming a VDM, you can indicate its function and easily identify the VDM and its root
file system. For example, if you group the Marketing CIFS servers together into a VDM
named Marketing, you can easily identify the VDM.
When you create a VDM, you must specify a name that is unique to VNX. If you do not
specify the VDM name, a default name is assigned in the form vdm_<x>, where <x> is a
unique integer. The system assigns the root file system a name in the form root_fs_<vdm_x>,
where <vdm_x> is the name of the VDM.
For example, the root file system for a VDM named Marketing is named
root_fs_vdm_Marketing. If you name a VDM vdm_Marketing, the system does not duplicate
the vdm part of the name. The root file system is still named root_fs_vdm_Marketing.
If you rename a VDM, its root file system is renamed accordingly. Renaming a VDM to HR
causes its root file system name to change to root_fs_vdm_HR. You cannot manually change
a VDM root file system name.

VDM root file system size, layout, and inode density

A root file system is assigned to a VDM when it is created. The default size is 128 MB, which
is the same for a physical Data Mover. In an environment with a large number of users or
shares, you might need to increase the size of the root file system. You cannot extend the
root file system automatically. EMC E-Lab™ Interoperability Navigator on the EMC Online
Support website provides information about the size of root file systems.
There are three ways to create a VDM and allocate the appropriate space for its configuration
file systems:
◆ If you do not specify the file system or size, the Control Station makes a 128 MB file
system from available space. Create a VDM by using default values on page 32 describes
this procedure.

◆ You can specify an existing file system as the VDM root file system. This method provides
the greatest administrative control. You may choose the volume layout and the size and
inode density of the VDM root file system. The following procedures describe this method:
•
Create a slice for a VDM root file system on page 33
•
Create a stripe for a VDM root file system on page 34
•
Create a metavolume for a VDM root file system on page 34
•
Create the root file system for a VDM on page 35
•
Create a VDM in the loaded state from an existing file system on page 36
•
Verify the size of a root file system on page 37

28 Configuring Virtual Data Movers on VNX 7.0

 Concepts

◆ If you specify a storage pool when using Automatic Volume Manager (AVM), the Control
Station uses AVM to find the storage pool and create the file system. Managing Volumes
and File Systems with VNX Automatic Volume Management and EMC Unisphere online help
provide more information about AVM. Also, consult Create a VDM in the loaded state
that uses Automatic Volume Management on page 38

In addition, consider the volume layout and the physical Data Movers you will use.
Consider the inode density required for the VDM root file system. The caching of user and
group mappings requires the use of inodes from the root file system.

Internationalization modes
When a VDM is created, its internationalization mode is set to the same mode as the Data
Mover in which it resides. When the VDM is unloaded, its mode matches the last physical
Data Mover on which it was loaded.
When loading a VDM onto a Data Mover, the modes of the VDM and the target Data Mover
are compared. If the modes do not match, the system does not allow the operation. You can
convert an ASCII mode VDM to Unicode mode, as described in Convert a VDM from ASCII
to Unicode mode on page 47.

CAUTION: The convert operation is ASCII to Unicode only, and irreversible. A Unicode mode
VDM cannot be converted to ASCII mode.

Name resolution when moving VDMs

The examples in this document use DNS for name resolution. Whether the environment
uses DNS, WINS, or a static file, consider the following information when moving a VDM
to another physical Data Mover and using different IP addresses. Read the appropriate
section for the name resolution method used in the environment.

DNS
When moving VDMs and using DNS, consider the following:
◆ The VDM load operation updates the DNS servers configured on the physical Data
Mover.
◆ The update time between DNS servers depends on the configuration.
◆ The system administrator can force DNS database updates to all DNS servers to which
the clients might be pointing.
◆ When you move the VDM to the destination Data Mover, the DNS server is automatically
updated and displays the correct entry.
The DNS client considerations when moving VDMs are:

Planning considerations 29
Concepts

◆ The mapped drive is not immediately accessible.

◆ The client has the old DNS information in memory.
◆ To clear the client cache and view updated information, use one of the following methods:
•
Restart the client computer.
•
Wait until the cache clears and updates. This might take as long as 60 minutes because
of the Time to Live (TTL) default.
•
Restart DNS client service.
•
From the DOS prompt, run the command ipconfig/flushdns.

WINS
When moving VDMs and using WINS, consider the following:
◆ The VDM load updates WINS servers configured on the VDM.
◆ The update time between WINS servers depends on the configuration.
◆ System administrators can force WINS database updates to all WINS servers to which
the clients might be pointing.
◆ To clear and update the WINS cache for clients, use one of the following methods:
•
Restart the computer.
•
Wait until the cache is cleared (TTL 10 minutes).
•
From the DOS prompt, run the command nbtstat -R.

Static file (LMHOSTS/Host)

The static file (LMHOSTS/Host) used by clients must be updated with the IP address of each
new CIFS server.

30 Configuring Virtual Data Movers on VNX 7.0

 3

Configuring

Topics included are:

◆ Create a VDM on page 32
◆ Create a user file system on page 40
◆ Create a mount point for a user file system on page 41
◆ Mount a user file system on page 42
◆ Configure an interface on page 43
◆ Create a CIFS server in a VDM on page 44
◆ Join the CIFS servers to a domain on page 45
◆ Create shares for CIFS servers in a VDM on page 46
◆ Convert a VDM from ASCII to Unicode mode on page 47

Configuring Virtual Data Movers on VNX 7.0 31

Configuring

Create a VDM
The tasks to create a VDM are:
◆ Create a VDM by using default values on page 32
◆ Create a slice for a VDM root file system on page 33
◆ Create a stripe for a VDM root file system on page 34
◆ Create a metavolume for a VDM root file system on page 34
◆ Create the root file system for a VDM on page 35
◆ Create a VDM in the loaded state from an existing file system on page 36
◆ Verify the size of a root file system on page 37
◆ Create a VDM in the loaded state that uses Automatic Volume Management on page 38
◆ Create a VDM in the mounted state on page 39

Note: You must be nasadmin or root to create a VDM. A local user with assigned nasadmin or root
privileges cannot create a VDM.

Create a VDM by using default values

When using default values, the VDM is created in a loaded state, and assigned a default
name.

Note: The system assigns default names for the VDM and its root file system.

Action
To create a VDM by using default values, use this command syntax:
$ nas_server -type vdm -create <movername>
where:
<movername> = name of the physical Data Mover

Example:
To create a VDM on server_2, type:
$ nas_server -type vdm -create server_2

32 Configuring Virtual Data Movers on VNX 7.0

 Configuring

Output

id = 4
name = vdm_4
acl = 0
type = vdm
server = server_2
rootfs = root_fs_vdm_4
I18N mode = UNICODE
mountedfs = Admin_user
member_of =
standby =
status :
defined = enabled
actual = loaded, active
Interfaces to services mapping:

Create a slice for a VDM root file system

Perform this task as often as necessary to specify the size required for creating a slice for a
VDM root file system. Managing Volumes and File Systems for VNX Manually describes slice
volumes in detail.

Action
To create a slice, use this command syntax:
$ nas_slice -name <name> -create <volume_name> <size> [<offset>]
where:
<name> = name of the slice

<volume_name> = volume for the file system

<size> = size of the slice in megabytes

<offset> = distance in megabytes from beginning of the volume to the start of the slice, and if omitted, the system de-
termines the best fit
Example:
To create a slice volume named sl1_mkt from the volume named d374 with a size of 128 MB, type:
$ nas_slice -name sl1_mkt -create d374 128

Output

id = 118
name = sl1_mkt
acl = 0
in_use = False
slice_of = d374
offset(MB)= 0
size (MB)= 128
volume_name = sl1_mkt

Create a VDM 33
Configuring

Create a stripe for a VDM root file system

Action
To create a stripe for the VDM root file system, use this command syntax:
$ nas_volume -name <name> -create -Stripe [<stripe_size>]
where:
<name> = name for the volume

<stripe_size> = size of the stripe in multiples of 8192 bytes, and if omitted, 32768 is used

Example:
To create a stripe volume, stv1_mkt, for the VDM root file system with a stripe size of 32768, type:
$ nas_volume -name stv1_mkt -create -Stripe 32768 sl1_mkt,sl2_mkt,sl3_mkt,sl4_mkt

Output

id = 612
name = stv1_mkt
acl = 0
in_use = False
type = stripe
stripe_size = 32768
volume_set = sl1_mkt,sl2_mkt,sl3_mkt,sl4_mkt
disks = d374,d375,d376,d377

Create a metavolume for a VDM root file system

Action
To create a metavolume, use this command syntax:
$ nas_volume -name <name> -create -Meta <volume_name>
where:
<name> = name for the metavolume

<volume_name> = name for the volume

Example:
To create a metavolume named mtv_mkt, type:
$ nas_volume -name mtv_mkt -create -Meta stv1_mkt

34 Configuring Virtual Data Movers on VNX 7.0

 Configuring

Output

id = 613
name = mtv_mkt
acl = 0
in_use = False
type = meta
volume_set = stv1_mkt
disks = d374,d375,d376,d377

Create the root file system for a VDM

The option nbpi=1024 sets the inode density to one inode per 1KB.

Action
To create the root file system for a VDM, use this command syntax:
$ nas_fs -name <name> -create <volume_name> -option nbpi=1024
where:
<name> = name of the VDM, and the prefix root_fs is attached to this name

<volume_name> = name of the volume

Example:
To create the root file system for the VDM named vdm_mkt, type:
$ nas_fs -name vdm_mkt -create mtv_mkt -option nbpi=1024

Output

id = 112
name = vdm_mkt
acl = 0
in_use = False
type = uxfs
volume = mtv_mkt
pool =
rw_servers=
ro_servers=
rw_vdms =
ro_vdms =
stor_devs = 000187940268-0179,000187940268-017A,000187940268-017B,
000187940268-017C
disks = d374,d375,d376,d377

Create a VDM 35
Configuring

Create a VDM in the loaded state from an existing file system

Perform the following tasks, as appropriate, to prepare the root file system for a VDM:
◆ Create a slice for a VDM root file system on page 33
◆ Create a stripe for a VDM root file system on page 34
◆ Create a metavolume for a VDM root file system on page 34
◆ Create the root file system for a VDM on page 35

Note: The root file system is renamed in the format root_fs_<vdm_name>.

Action
To create a VDM in the loaded state and use an existing file system, use this command syntax:
$ nas_server [-name <name>] -type vdm -create <movername> -fs <fs_name>
where:
<name> = name for the VDM, and if specified, it must be unique to the entire system

<movername> = name of the physical Data Mover

<fs_name> = name of the existing file system. For a loaded state VDM, the file system type must be uxfs. For a
mounted state VDM, the type can be either uxfs or rawfs
Example:
To create a loaded VDM named Marketing on server_2, type:
$ nas_server -name Marketing -type vdm -create server_2 -fs vdm_mkt

Output

id = 1
name = Marketing
acl = 0
type = vdm
server = server_2
rootfs = root_fs_vdm_Marketing
I18N mode = UNICODE
mountedfs =
member_of =
status :
defined = enabled
actual = loaded, ready
Interfaces to services mapping:

36 Configuring Virtual Data Movers on VNX 7.0

 Configuring

Verify the size of a root file system

Note: The size of this root file system is 512 MB. The default size is 128 MB (the same as for a physical
Data Mover).

Action
To verify the size of a root file system, use this command syntax:
$ /nas/sbin/rootnas_fs -size <fs_name>
where:
<fs_name> = name of the VDM root file system

Example:
To verify the size of the file system root_fs_vdm_Marketing, type:
$ /nas/sbin/rootnas_fs -size root_fs_vdm_Marketing

Output

total = 504 avail = 503 used = 0 ( 0% ) (sizes in MB) ( blockcount = 1048576

)
volume: total = 512 (sizes in MB) ( blockcount = 1048576)

Create a VDM 37
Configuring

Create a VDM in the loaded state that uses Automatic Volume

Management

You can add only CIFS servers to loaded VDMs. You must specify the storage pool, that
determines the volume layout and size.

Action
To create a VDM in the loaded state that uses AVM, use this command syntax:
$ nas_server [-name <name>] -type vdm -create <movername> pool=<pool>
where:
<name> = name for the VDM, and if specified, it must be unique to the entire system

<movername> = name of the physical Data Mover

<pool> = name of the storage pool

Note: The storage pool assigns a rule set for the root file system of the VDM, the storage pool rule set contains automat-
ically created volumes and defines the type of disk volumes used, and how they are aggregated.

Available system-defined storage pool types are:

symm_std, clar_r1, clar_r5_performance, symm_std_rdf_src, symm_std_rdf_tgt,
symm_ata, symm_ata_rdf_src, symm_ata_rdf_tgt, symm_ssd, cm_r6, cmata_r6,
clar_r5_economy, clar_r6, clarata_r3, clarata_r6, clarata_archive,
clarssd_r5, clarsas_archive, clarsas_r6, clarsas_r10, cmsas_archive, cm-
sas_r6, cmsas_r10, cmssd_r5 .
Example:
To create a loaded VDM named Marketing, with a root file system of 128 MB on server_2, that uses the storage pool
symm_std, type:
$ nas_server -name Marketing -type vdm -create server_2 pool=symm_std

Output

id = 1
name = Marketing
acl = 0
type = vdm
server = server_2
rootfs = root_fs_vdm_Marketing
I18N mode = UNICODE
mountedfs = Mkt_user
member_of =
standby =
status :
defined = enabled
actual = loaded, active
Interfaces to services mapping:

38 Configuring Virtual Data Movers on VNX 7.0

 Configuring

Create a VDM in the mounted state

Before you begin
If you use the VNX Replicator , the file system must be a Universal Extended File System
(UxFS), which is the default, and therefore you can omit the fstype option.
When creating a VDM that uses AVM, you must specify the storage pool.

Procedure

Note:
The internationalization is set in the same way as the physical Data Mover on which the VDM resides.
Refer to Convert a VDM from ASCII to Unicode mode on page 47.
The default size for a VDM root file system (128 MB) is the same as that of a physical Data Mover.

Action
To create a VDM in the mounted state that uses AVM, use this command syntax:
$ nas_server[-name <name>]-type vdm -create <movername> -setstate mounted
pool=<pool> [-option fstype=rawfs]
where:
<name> = name for the VDM, and if specified, it must be unique to the entire system

<movername> = name of the physical Data Mover in which the VDM resides

<pool> = name of the storage pool

Note: the storage pool assigns a rule set for the root file system of the VDM, the storage pool rule set contains automati-
cally created volumes and defines the type of disk volumes used, and how they are aggregated.

Available system-defined storage pool types are: symm_std, clar_r1, clar_r5_performance,

symm_std_rdf_src, symm_std_rdf_tgt, symm_ata, symm_ata_rdf_src,
symm_ata_rdf_tgt, symm_ssd, cm_r6, cmata_r6, clar_r5_economy, clar_r6,
clarata_r3, clarata_r6, clarata_archive, clarssd_r5, clarsas_archive,
clarsas_r6, clarsas_r10,cmsas_archive, cmsas_r6, cmsas_r10, cmssd_r5.
Example:
To create a VDM named HR in the mounted state as a raw file system that uses the symm_std pool, type:
$ nas_server -name HR -type vdm -create server_2 -setstate mounted pool=symm_std
-option fstype=rawfs

Create a VDM 39
Configuring

Output

id = 2
name = HR
acl = 0
type = vdm
server = server_2
rootfs = root_fs_vdm_HR
I18N mode = ASCII
mountedfs = HR_user
member_of =
status :
defined = enabled
actual = mounted, inactive
Interfaces to services mapping:

Create a user file system

Managing Volumes and File Systems with VNX Automatic Volume Management provides more
information about file systems.

Action
To create a user file system in a VDM, use this command syntax:
$ nas_fs -name <name> -create size= <integer>[T|G|M] pool=<pool>
where:
<name> = name for the file system

<size> = required size of the file system in terabytes (T), gigabytes (G), or megabytes (M)

<pool> = name of the AVM storage pool

Example:
To create a user file system named Mkt_user, type:
$ nas_fs -name Mkt_user -create size=100M pool=symm_std

40 Configuring Virtual Data Movers on VNX 7.0

 Configuring

Output

id = 261
name = Mkt_user
acl = 0
in_use = False
type = uxfs
volume = v1116
pool = symm_std
member_of = root_avm_fs_group_1
rw_servers=
ro_servers=
rw_vdms =
ro_vdms =
stor_devs = 000187940268-0074,000187940268-0075,000187940268-0076,
000187940268-0077,000187940268-0078,000187940268-0079,000187940268-007A,
000187940268-007B
disks = d113,d114,d115,d116,d117,d118,d119,d120

Create a mount point for a user file system

Action
To create a mount point for a user file system in the VDM, use this command syntax:
$ server_mountpoint <vdm_name> -create <pathname>
where:
<vdm_name> = name of the VDM

<pathname> = path to the mount point

Example:
To create a mount point named MKt_user, type:
$ server_mountpoint Marketing -create /Mkt_user

Output
Marketing : done

Create a mount point for a user file system 41

Configuring

Mount a user file system

Before you begin
If the mount point does not exist, perform the task Create a mount point for a user file system
on page 41.

Procedure

Perform this procedure for each user file system in the VDM.

Action
To mount a user file system in the VDM, use this command syntax:
$ server_mount <movername> <fs_name> <mount_point>
where:
<movername> = name of the VDM

<fs_name> = name of the file system

<mount_point> = path to the mount point

Example:
To mount the user file system named Mkt_user in the VDM named Marketing, type:
$ server_mount Marketing Mkt_user /Mkt_user

Output
Marketing : done

After you finish

To verify that the file system is mounted, perform the task Display a list of mounted or
temporarily unmounted file systems on page 52.

42 Configuring Virtual Data Movers on VNX 7.0

 Configuring

Configure an interface
Action
To configure an interface, use this command syntax:
$ server_ifconfig <movername> -create -Device <device_name> -name <if_name>
-protocol IP <ipaddr> <ipmask> <ipbroadcast>
where:
<movername> = name of the physical Data Mover

<device_name> = device name

<if_name> = name of the interface

<ipaddr> = IP address

<ipmask> = IP mask

<ipbroadcast> = IP broadcast address

Example:
To configure an interface named Mkt for the existing virtual device s2_trk1, type:
$ server_ifconfig server_2 -create -Device s2_trk1 -name Mkt -protocol IP
172.24.100.125 255.255.255.0 172.24.100.255

Output
server_2 : done

Configure an interface 43
Configuring

Create a CIFS server in a VDM

The default CIFS server is incompatible with VDM because it uses all interfaces and does
not leave a free interface for the VDM. Each CIFS server in the VDM and physical Data
Mover must have its own interface explicitly specified. If a VDM exists on a Data Mover, a
default CIFS server cannot be created.

Action
To create a CIFS server, use this command syntax:
$ server_cifs <movername> -add compname=<comp_name>, domain=<full_domain_name>,
interface=<if_name>
where:
<movername> = name of the VDM

<comp_name> = name of the computer

<full_domain_name> = full name of the domain; for Windows NT 4.0, use uppercase

<if_name> = name of the interface

Example:
To create the CIFS server named Marketing, type:
$ server_cifs Marketing -add compname=Mkt_NE,
domain=c1t1.pt1.c3lab.nsgprod.emc.com,interface=Mkt

Output
Marketing : done

44 Configuring Virtual Data Movers on VNX 7.0

 Configuring

Join the CIFS servers to a domain

A VDM does not inherit the physical Data Mover WINS configuration. Add the WINS
configuration at the VDM level when WINS is used.

Action
To join the CIFS servers to the domain, use this command syntax:
$ server_cifs <movername> -Join compname=<comp_name>,domain=<full_do
main_name>,interface=<interface_name>, admin=<admin_name>

where:
<movername> = name of the VDM

<comp_name> = name of the computer

<full_domain_name>= full name of the domain

<interface_name>= name of the interface

<admin_name> = name of the system administrator

Example:
To join the Marketing CIFS server to the domain nsgprod.emc.com, type:
$ server_cifs Marketing -Join compname=Mkt_NE,domain= c1t1.pt1.c3lab.nsgprod.emc.com,
interface=Mkt,admin=admin

Output

Marketing: Enter Password: ********

Done

To display the status of the VDM and the CIFS servers in the VDM, perform these tasks:
◆ Display the attributes of a VDM on page 50
◆ Display the CIFS protocol configuration on page 51

Join the CIFS servers to a domain 45

Configuring

Create shares for CIFS servers in a VDM

The CIFS service stop or start operations can be done only at the physical Data Mover level.
You cannot stop or start the CIFS service at each VDM level.

Action
To create the shares for CIFS servers in a VDM, use this command syntax:
$ server_export <movername> -Protocol cifs -name <sharename> /<mountpoint>
where:
<movername> = name of the VDM

<sharename> = name for the share name

<mountpoint> = path to the mountpoint

Example:
To create shares named Shared_Files for the CIFS servers, type:
$ server_export Marketing -Protocol cifs -name Shared_Files /Mkt_user

Output
Marketing: done

Verify the CIFS shares in a VDM

Action
To verify that CIFS shares are created in a VDM, use this command syntax:
$ server_export <movername>
where:
<movername> = name of the VDM

Example:
To verify the CIFS shares in the VDM named Marketing, type:
$ server_export Marketing

Output

Marketing :
share "Shared_Files" "/Mkt_user" maxusr=4294967295 umask=22

46 Configuring Virtual Data Movers on VNX 7.0

 Configuring

Convert a VDM from ASCII to Unicode mode

When converting the internationalization mode of a VDM, you must convert the file or
directory names separately through the uc_config -convert command. Using International
Character Sets on VNX for File provides more information to perform this task if the user file
system contains non-ASCII files or directory names.

CAUTION: This procedure does not trigger conversion (from non-ASCII to Unicode) of file or
directory names within user file systems mounted on the VDM.

Action
To convert a VDM from ASCII to Unicode mode, use this command syntax:
$ nas_server -vdm <vdm_name> -setstate <state> <movername> -ConvertI18N
where:
<vdm_name> = name assigned to the VDM

<state> = VDM state (mounted, loaded, tempunloaded, or permunloaded)

<movername> = name of the Data Mover in which the VDM resides

Example:
To convert vdm_1 from ASCII to Unicode mode, type:
$ nas_server -vdm vdm_1 -setstate mounted server_2 -ConvertI18N

Output

id = 1
name = vdm_1
acl = 0
type = vdm
server = server_2
rootfs = root_fs_vdm_vdm_1
I18N mode = UNICODE
mountedfs =
member_of =
status :
defined = enabled
actual = mounted
Interfaces to services mapping:

Note
The output shows internationalization (I18N) mode as UNICODE.

Convert a VDM from ASCII to Unicode mode 47

Configuring

48 Configuring Virtual Data Movers on VNX 7.0

 4

Managing

Topics included are:

◆ Display the server table for a VDM on page 50
◆ Display the attributes of a VDM on page 50
◆ Display the CIFS protocol configuration on page 51
◆ Display a list of mounted or temporarily unmounted file systems on
page 52
◆ Display the DNS configuration on page 53
◆ Display the time services configuration on page 54
◆ Display parameters for configured interfaces on page 54
◆ Display the network connectivity for a Data Mover on page 55
◆ Change the VDM state on page 56
◆ Unload a VDM temporarily on page 57
◆ Unload a VDM permanently on page 58
◆ Rename a VDM on page 59
◆ Move a VDM when using different IP addresses on page 60
◆ Move a VDM when using the same IP address on page 67
◆ Delete a VDM on page 70
◆ Use VDMs and NDMP backup on page 71

Configuring Virtual Data Movers on VNX 7.0 49

Managing

Display the server table for a VDM

Action
To display a list of all VDMs in the Data Mover server table, type:
$ nas_server -list -vdm

Output

id acl server mountedfs rootfs name

1 0 2 32 Marketing
2 0 2 34 HR
3 0 1 86 Operations
4 0 2 87 vdm_4

Display the attributes of a VDM

Action
To display the attributes of a specific VDM, use this command syntax:
$ nas_server -info -vdm <vdm_name>
where:
<vdm_name> = name of the VDM

Example:
To display the attributes of the VDM named Marketing, type:
$ nas_server -info -vdm Marketing

Note:
The following output shows important information about the VDM:

◆ name = name of the VDM

◆ server = name of the physical Data Mover
◆ rootfs = name of the VDM root file system
◆ mountedfs = file systems mounted on the VDM
◆ status= VDM state
◆ Interface = name of the interface and mapped service

50 Configuring Virtual Data Movers on VNX 7.0

 Managing

Output

id = 1
name = Marketing
acl = 0
type = vdm
server = server_2
rootfs = root_fs_vdm_Marketing
I18N mode = UNICODE
mountedfs = Mkt_user
member_of =
standby =
status :
defined = enabled
actual = loaded, active
Interfaces to services mapping:
Interface = Mkt:cifs

Display the CIFS protocol configuration

Action
To display the CIFS protocol configuration, use this command syntax:
$ server_cifs<movername>
where:
<movername> = name of the VDM

Example:
To display the CIFS protocol configuration of the VDM named Marketing, type:
$ server_cifs Marketing

Display the CIFS protocol configuration 51

Managing

Output

Marketing :
96 Cifs threads started
Security mode = NT
Max protocol = NT1
I18N mode = UNICODE
CIFS service of VDM Marketing (state=loaded)
Home Directory Shares ENABLED, map=/.etc/homedir

Enabled interfaces: (All interfaces are enabled)

Disabled interfaces: (No interface disabled)

Unused Interface(s):
if=HR l=172.24.100.203 b=172.24.100.255 mac=0:4:23:7:f7:10
if=172_24_100_200 l=172.24.100.200 b=172.24.100.255 mac=0:4:23:7:f7:10

if=ace0 l=172.24.106.21 b=172.24.106.127 mac=0:60:cf:21:7e:e0

DOMAIN C1T1 FQDN=c1t1.pt1.c3lab.nsgprod.emc.com RC=4

SID=S-1-5-15-64ae4905-6fc45226-40d54d1d-ffffffff
>DC=LNSGA183(172.24.100.183) ref=3 time=0 ms
DC=LNSGC222(172.24.101.222) ref=2 time=0 ms

CIFS Server MKT_NE[C1T1] RC=2

Full computer name=mkt_ne.c1t1.pt1.c3lab.nsgprod.emc.com
realm=C1T1.PT1.C3LAB.N
SGPROD.EMC.COM
Comment='EMC-SNAS:T5.3.8.2016'
if=Mkt l=172.24.100.247 b=172.24.100.255 mac=0:4:23:7:f7:10
FQDN=mkt_ne.c1t1.pt1.c3lab.nsgprod.emc.com (Updated to DNS)

Display a list of mounted or temporarily unmounted file systems

Action
To display a list of mounted or temporarily unmounted file systems, use this command syntax:
$ server_mount <movername>
where:
<movername> = name of the Data Mover

Example:
To display a list of mounted or temporarily unmounted file systems on server_2, type:
$ server_mount server_2

Output

server_2 :
root_fs_vdm_Marketing on /root_vdm_1/.etc uxfs,perm,rw
Mkt_Shared on /root_vdm_1/Mkt_Shared uxfs,perm,rw
Mkt_User on /root_vdm_1/Mkt_User uxfs,perm,rw

52 Configuring Virtual Data Movers on VNX 7.0

 Managing

Note
The user file systems are accessible and have read/write permission.

Display the DNS configuration

Action
To display the DNS configuration, use this command syntax:
$ server_dns<movername>
where:
<movername> = name of the Data Mover

Example:
To display the DNS configuration on server_2, type:
$ server_dns server_2

Output

server_2 :
DNS is running.
c1t1.pt1.c3lab.nsgprod.emc.com
proto:udp server(s):172.24.100.183

Display the DNS configuration 53

Managing

Display the time services configuration

Action
To display the time services configuration, use this command syntax:
$ server_date <movername> timesvc
where:
<movername> = name of the Data Mover

Example:
To display the status of time services on server_2, type:
$ server_date server_2 timesvc

Output

server_2 :

Timeservice State

time: Mon Oct 15 05:52:34 EDT 2007

type: ntp
sync delay: on
interval: 60
hosts: 172.24.100.183

Display parameters for configured interfaces

Action
To display parameters for configured interfaces on the target Data Mover, use this command syntax:
$ server_ifconfig <movername> -all
where:
<movername> = name of the Data Mover

Example:
To display parameters for configured interfaces on the target Data Mover, server_3, type:
$ server_ifconfig server_3 -all

54 Configuring Virtual Data Movers on VNX 7.0

 Managing

Output

server_3 :
loop protocol=IP device=loop
inet=127.0.0.1 netmask=255.0.0.0 broadcast=127.255.255.255
UP, loopback, mtu=32768, vlan=0, macaddr=0:0:0:0:0:0
netname=localhost
el31 protocol=IP device=mge1
inet=128.221.253.3 netmask=255.255.255.0
broadcast=128.221.253.255
UP, ethernet, mtu=1500, vlan=0, macaddr=0:60:16:b:b7:17
netname=localhost
el30 protocol=IP device=mge0
inet=128.221.252.3 netmask=255.255.255.0
broadcast=128.221.252.255
UP, ethernet, mtu=1500, vlan=0, macaddr=0:60:16:b:b7:18
netname=localhost

Display the network connectivity for a Data Mover

Action
To display the network connectivity to the target Data Mover, use this command syntax:
$ server_ping <movername> -interface <interface> <ip_addr>
where:
<movername> = name of the Data Mover

<interface> = name of the interface

<ip_addr> = IP address

Example:
To display the network connectivity to the target Data Mover, server_2, type:
$ server_ping server_2 -interface Mkt 172.24.100.124

Output
server_2 : 172.24.100.124 is alive, time= 0 ms

Display the network connectivity for a Data Mover 55

Managing

Change the VDM state

Before you begin
To get the current VDM information, perform these tasks:
◆ Display the attributes of a VDM on page 50
◆ Display the CIFS protocol configuration on page 51

Procedure

Note: The user file systems appear in the output but are inaccessible through the VDM in the mounted
state.

Action
To change the state of a VDM, use this command syntax:
$ nas_server -vdm <vdm_name> -setstate <state>
where:
<vdm_name> = name assigned to the VDM

<state> = state of the VDM (mounted, loaded, tempunloaded, or permunloaded)

Example:
To change the state of the Marketing VDM from loaded to mounted, type:
$ nas_server -vdm Marketing -setstate mounted

Output

id = 1
name = Marketing
acl = 0
type = vdm
server = server_2
rootfs = root_fs_vdm_Marketing
I18N mode = UNICODE
mountedfs = Mkt_user, Mkt_shared
member_of =
status :
defined = enabled
actual = mounted
Interfaces to services mapping:

After you finish

To check the status of the mounted VDM, perform these tasks:

◆ Display the CIFS protocol configuration on page 51
◆ Display a list of mounted or temporarily unmounted file systems on page 52

56 Configuring Virtual Data Movers on VNX 7.0

 Managing

Unload a VDM temporarily

To get current information about the VDM, perform the task Display the attributes of a VDM
on page 50.

Action
To unload a VDM temporarily, use this command syntax:
$ nas_server -vdm <vdm_name> -setstate tempunloaded
where:
<vdm_name> = name of the VDM

Example:
To temporarily unload the VDM named Marketing, type:
$ nas_server -vdm Marketing -setstate tempunloaded

Output

id = 1
name = Marketing
acl = 0
type = vdm
server = server_2
rootfs = root_fs_vdm_Marketing
I18N mode = UNICODE
mountedfs =
member_of =
status :
defined = enabled
actual = temporarily unloaded
Interfaces to services mapping:

Unload a VDM temporarily 57

Managing

Unload a VDM permanently

To get current information about the VDM, perform the task Display the attributes of a VDM
on page 50.

Action
To unload a VDM permanently, use this command syntax:
$ nas_server -vdm <vdm_name> -setstate permunloaded
where:
<vdm_name> = name of the VDM

Example:
To unload the Marketing VDM permanently, type:
$ nas_server -vdm Marketing -setstate permunloaded

Output

id = 1
name = Marketing
acl = 0
type = vdm
server = server_2
rootfs = root_fs_vdm_Marketing
I18N mode = UNICODE
mountedfs =
member_of =
status :
defined = enabled
actual = permanently unloaded
Interfaces to services mapping:

58 Configuring Virtual Data Movers on VNX 7.0

 Managing

Rename a VDM
When you rename a VDM, the Control Station sends a command to the Data Mover to
modify the VDM name in the Data Mover (server) table.

Note:
Do not try to rename a VDM during a replication failover or suspend operation. Although there are
protections to avoid conflicts, it is recommended to wait until the operation is completed.
The name of the root file system for the VDM is also changed.

Action
To rename a VDM, use this command syntax:
$ nas_server -rename <old_movername> <new_movername>
where:
<old_movername> = name currently assigned to the VDM

<new_movername> = new name for the VDM

Example:
To change the name of a VDM from HR to Finance, type:
$ nas_server -rename HR Finance

Output

id = 2
name = Finance
acl = 0
type = vdm
server = server_2
rootfs = root_fs_Finance
I18N mode = UNICODE
mountedfs = Fin_user
member_of =
standby =
status :
defined = enabled
actual = loaded, active
Interfaces to services mapping:

Rename a VDM 59
Managing

Move a VDM when using different IP addresses

Before you begin
To move an existing VDM to another Data Mover, perform these tasks:
◆ Interfaces with the same name on both Data Movers
◆ IP addresses for both interfaces
◆ Name resolution configurations on both Data Movers
To verify the VDM, perform these tasks:
◆ Display the attributes of a VDM on page 50
◆ Display the CIFS protocol configuration on page 51
◆ Display the DNS configuration on page 53
◆ Display the time services configuration on page 54

Procedure

A VDM can be moved when using different IP addresses on the source and target Data
Movers. Use the same or different IP addresses on the source and target physical Data
Movers.
To move an existing VDM to another Data Mover, perform these tasks:
1. Configure the target Data Mover on page 61
2. Configure an interface on page 43
3. Configure DNS on the target Data Mover on page 62
4. Configure time services on the target Data Mover on page 63
5. Start the CIFS service on page 63
6. Move the VDM to the target Data Mover on page 65

60 Configuring Virtual Data Movers on VNX 7.0

 Managing

Configure the target Data Mover

Note: Enclose the option in quotation marks, as in the example mentioned in the table. If you do not
use the quotation marks, the command appears to have executed correctly and the link appears as
Link Up. However, the link will not work correctly.

Action
To configure the Data Mover, use this command syntax:
$ server_sysconfig <movername> -virtual -name <device> -create <device_class>
-option <option,..>
where:
<movername> = name of the Data Mover

<device> = device name

<device_class> = device class

Example:
To configure server_3 as the target Data Mover, type:
$ server_sysconfig server_3 -virtual -name s3_trk1 -create trk -option
device="cge0,cge1,cge2,cge3 protocol=lacp"

Output
server_3 : done

Move a VDM when using different IP addresses 61

Managing

Configure DNS on the target Data Mover

Before you begin
To get information about the network connectivity of the target Data Mover, perform these
tasks:
◆ Display the network connectivity for a Data Mover on page 55
◆ Display the DNS configuration on page 53

Procedure

Action
To configure DNS on the target Data Mover, use this command syntax:
$ server_dns <movername> -protocol {tcp|udp} <domainname> <ip_addr>
where:
<movername> = name of the Data Mover

<domainname> = domain name

<ip_addr> = IP address

Example:
To configure DNS on server_3, type:
$ server_dns server_3 -protocol udp c1t1.pt1.c3lab.nsgprod.emc.com 172.24.100.183

Output
server_3 : done

After you finish

To verify the DNS configuration on the target Data Mover, perform these tasks:
◆ Display the DNS configuration on page 53
◆ Display the network connectivity for a Data Mover on page 55

62 Configuring Virtual Data Movers on VNX 7.0

 Managing

Configure time services on the target Data Mover

Before you begin
To view the current time services configuration, perform the task Display the time services
configuration on page 54.

Procedure

Action
To configure time services on the target Data Mover, use this command syntax:
$ server_date <movername> timesvc start ntp <host>
where:
<movername> = name of the Data Mover

<host> = IP address of the time server host

Example:
To configure time services on server_3 and use the time server host 172.24.100.183, type:
$ server_date server_3 timesvc start ntp 172.24.100.183

Output
server_3 : done

After you finish

To verify the time services configuration, perform the task Display the time services
configuration on page 54.

Start the CIFS service

Action
To start the CIFS service, use this command syntax:
$ server_setup <movername> -Protocol cifs -option start
where:
<movername> = name of the Data Mover

Example:
To start the CIFS service on server_3, type:
$ server_setup server_3 -Protocol cifs -option start

Move a VDM when using different IP addresses 63

Managing

Output
server_3 : done

Figure 4 on page 64 shows the DNS server before the VDM is moved to the target Data
Mover.

Figure 4. DNS server before VDM move

Figure 5 on page 64 shows the shares to which the CIFS servers have access.

Figure 5. Accessible shares

64 Configuring Virtual Data Movers on VNX 7.0

 Managing

Move the VDM to the target Data Mover

Action
To move the VDM to another Data Mover, use this command syntax:
$ nas_server -vdm <vdm_name> -move <movername>
where:
<vdm_name> = name of the VDM

<movername> = name of the target Data Mover

Example:
To move the VDM named Marketing to server_3, type:
$ nas_server -vdm Marketing -move server_3

Output

id = 1
name = Marketing
acl = 0
type = vdm
server = server_3
rootfs = root_fs_vdm_Marketing
I18N mode = UNICODE
mountedfs = Mkt_user, Mkt_shared
member_of =
status :
defined = enabled
actual = loaded, active
Interfaces to services mapping:
interface=Mkt :cifs

After you finish

To verify the CIFS configuration, perform the task Display the CIFS protocol configuration
on page 51.

Move a VDM when using different IP addresses 65

Managing

Figure 6 on page 66 shows the DNS server after the VDM is moved.

Figure 6. DNS server after VDM move

The target interface must be operating before you move the VDM to the target Data Mover.
You can use a different IP address for the target Data Mover, as in the last procedure, or
keep the same IP address for the VDM interface on the target Data Mover.

66 Configuring Virtual Data Movers on VNX 7.0

 Managing

Move a VDM when using the same IP address

Before you begin
To move an existing VDM to another Data Mover, perform these tasks:
◆ Create interfaces with the same name on both Data Movers
◆ Assign IP addresses for both interfaces
◆ Check the name resolution configurations on both Data Movers
To get current information about the VDM, perform these tasks:
◆ Display the attributes of a VDM on page 50
◆ Display the CIFS protocol configuration on page 51
◆ Display the DNS configuration on page 53
◆ Display the time services configuration on page 54

Procedure

To keep the same IP address and move a VDM to another Data Mover, perform these tasks:
1. Take down the interface on the source Data Mover on page 68
2. Configure an interface on page 43
3. Move the VDM to the target Data Mover on page 65
4. Delete the interface on the source Data Mover on page 69

Move a VDM when using the same IP address 67

Managing

Take down the interface on the source Data Mover

You must take down the interface on the source Data Mover to keep the same IP address
for the interface on the target Data Mover.

Before you begin

To verify the status of the CIFS environment, perform the task Display parameters for
configured interfaces on page 54.

Procedure

Action
To take down an interface on the source Data Mover, use this command syntax:
$ server_ifconfig <movername> <if_name> down
where:
<movername> = name of the Data Mover

<if_name> = name of the interface

Example:
To take down the interface named Mkt on server_2, type:
$ server_ifconfig server_2 Mkt down

Output
server_2 : done

After you finish

To verify that the source interface is down, perform the task Display parameters for
configured interfaces on page 54.

68 Configuring Virtual Data Movers on VNX 7.0

 Managing

Delete the interface on the source Data Mover

This procedure is required after moving a VDM when using the same IP address.

Action
To delete an interface on the source Data Mover, use this command syntax:
$ server_ifconfig <movername> -delete <if_name>
where:
<movername> = name of the Data Mover

<if_name> = name of the interface

Example:
To delete the interface named Mkt on server_2, type:
$ server_ifconfig server_2 -delete Mkt

Output
server_2 : done

Move a VDM when using the same IP address 69

Managing

Delete a VDM
The delete operation is used only when a system administrator decides to irreversibly remove
a VDM. You cannot delete the VDM root file system independently of the VDM. When you
delete a VDM, its root file system is also deleted. The deletion includes the entire CIFS
configuration (local group and share databases) of the VDM.

Before you begin

To delete a VDM, unmount all nonroot file systems that are mounted on it.

Procedure

Action
To delete a VDM, use this command syntax:
$ nas_server -delete <movername>
where:
<movername> = name of the VDM

Example:
To delete the VDM named Operations, type:
$ nas_server -delete Operations

Output

id = 3
name = Operations
acl = 0
type = vdm
server =
rootfs = root_fs_Operations
I18N mode = UNICODE
mountedfs =
member_of =
standby =
status :
defined = enabled
actual = permanently unloaded
Interfaces to services mapping:

70 Configuring Virtual Data Movers on VNX 7.0

 Managing

Use VDMs and NDMP backup

In a CIFS environment that uses VDMs and NDMP backup, you must specify the full path
of the file system in the backup application. This path is listed in the output for the
server_mount command on the physical Data Mover. Configuring NDMP Backups to Disk on
VNX provides information about specific backup software vendors.

Action
To display the full path of a file system, use this command syntax:
$ server_mount <movername> | grep <fs_name>
where:
<movername> = name of the Data Mover

<fs_name> = name of the file system

Example:
To display the full path for the file system Mkt_user, type:
$ server_mount server_2 | grep Mkt_user

Output
Mkt_user on /root_fs_vdm_Marketing/Mkt_user uxfs,perm,rw

Use VDMs and NDMP backup 71

Managing

72 Configuring Virtual Data Movers on VNX 7.0

 5

Troubleshooting

As part of an effort to continuously improve and enhance the performance

and capabilities of its product lines, EMC periodically releases new versions
of its hardware and software. Therefore, some functions described in this
document may not be supported by all versions of the software or
hardware currently in use. For the most up-to-date information on product
features, refer to your product release notes.
If a product does not function properly or does not function as described
in this document, please contact your EMC Customer Support
Representative.
Topics included are:
◆ EMC E-Lab Interoperability Navigator on page 74
◆ Troubleshooting CIFS server accessibility errors on page 74
◆ Troubleshooting VDM unloading errors on page 74
◆ Error messages on page 74
◆ EMC Training and Professional Services on page 75

Configuring Virtual Data Movers on VNX 7.0 73

Troubleshooting

EMC E-Lab Interoperability Navigator

The EMC E-Lab™ Interoperability Navigator is a searchable, web-based application that
provides access to EMC interoperability support matrices. It is available at
http://Support.EMC.com. After logging in to the EMC Online Support website, locate the
applicable Support by Product page, find Tools, and click E-Lab Interoperability Navigator.

Troubleshooting CIFS server accessibility errors

When no accessible CIFS servers are found, verify the state of the VDM. If the VDM is in
the mounted state, try changing the VDM to the loaded state before verifying the CIFS
servers again.
Troubleshoot this error by performing these tasks:
1. Display the CIFS protocol configuration on page 51
2. Display the attributes of a VDM on page 50
3. Change the VDM state on page 56
4. Display the attributes of a VDM on page 50

Troubleshooting VDM unloading errors

When temporarily unloading a VDM, there are file systems mounted on the VDM. You
cannot unload a VDM with mounted file systems.
Troubleshoot this error by performing these tasks:
1. Display a list of mounted or temporarily unmounted file systems on page 52
2. Display the attributes of a VDM on page 50
3. Unload a VDM temporarily on page 57

Error messages
All event, alert, and status messages provide detailed information and recommended actions
to help you troubleshoot the situation.
To view message details, use any of these methods:

◆ Unisphere software:

• Right-click an event, alert, or status message and select to view Event Details, Alert
Details, or Status Details.

74 Configuring Virtual Data Movers on VNX 7.0

 Troubleshooting

◆ CLI:

• Type nas_message -info <MessageID>, where <MessageID> is the message

identification number.

◆ Celerra Error Messages Guide:

• Use this guide to locate information about messages that are in the earlier-release
message format.

◆ EMC Online Support:

• Use the text from the error message's brief description or the message's ID to search
the Knowledgebase on the EMC Online Support website. After logging in to EMC
Online Support, locate the applicable Support by Product page, and search for the
error message.

EMC Training and Professional Services

EMC Customer Education courses help you learn how EMC storage products work together
within your environment to maximize your entire infrastructure investment. EMC Customer
Education features online and hands-on training in state-of-the-art labs conveniently located
throughout the world. EMC customer training courses are developed and delivered by EMC
experts. Go to the EMC Online Support website at http://Support.EMC.com for course and
registration information.
EMC Professional Services can help you implement your VNX series efficiently. Consultants
evaluate your business, IT processes, and technology, and recommend ways that you can
leverage your information for the most benefit. From business plan to implementation, you
get the experience and expertise that you need without straining your IT staff or hiring and
training new personnel. Contact your EMC Customer Support Representative for more
information.

EMC Training and Professional Services 75

Troubleshooting

76 Configuring Virtual Data Movers on VNX 7.0

 Glossary

CIFS server
Logical server that uses the CIFS protocol to transfer files. A Data Mover can host many instances
of a CIFS server. Each instance is referred to as a CIFS server.

CIFS service
CIFS server process that is running on the Data Mover and presents shares on a network as
well as on Microsoft Windows-based computers.

Control Station
Hardware and software component of VNX for file that manages the system and provides the
user interface to all VNX for file components.

Multi-Path File System (MPFS)

VNX for file feature that allows heterogeneous servers with MPFS software to concurrently
access, directly over Fibre Channel or iSCSI channels, shared data stored on a EMC Symmetrix
or VNX for block storage system. MPFS adds a lightweight protocol called File Mapping Protocol
(FMP) that controls metadata operations.

multibyte support
Generic term for encoding schemes for characters that may require more than one byte.

Virtual Data Mover (VDM)

VNX for file software feature that enables users to administratively separate CIFS servers,
replicate CIFS environments, and move CIFS servers from one Data Mover to another.

Configuring Virtual Data Movers on VNX 7.0 77

Glossary

78 Configuring Virtual Data Movers on VNX 7.0

 Index

A domain, join CIFS servers 45

attributes of VDM, displaying 50

E
C EMC E-Lab Navigator 74
error messages 74
cautions 13
changing VDM state 56
CIFS servers F
creating in VDMs 44 file systems
creating shares in VDMs 46 displaying mounted or temporarily unmounted
displaying configuration 51 52
joining to domain 45 mounting 41, 42
troubleshooting 74
concepts 18
configuring H
interface on Data Mover 43
converting VDM from ASCII to Unicode 47 hardware requirements 12
creating
CIFS servers in VDMs 44 I
mount point for user file system 41
shares for CIFS servers in VDM 46 I18N 47
slice for VDM root file system 33 interfaces
VDMs 32 configuring 43
VDMs by using default values 32 displaying parameters 54
interfaces, user 14
internationalization mode 47
D
displaying J
CIFS protocol configuration 51
mounted or temporarily unmounted file joining CIFS servers to domain 45
systems 52
network connectivity for Data Mover 55
parameters for interfaces 54 M
server table for VDM 50 messages, error 74
VDM attributes 50 mounted file systems, displaying 52
mounting user file systems 42

Configuring Virtual Data Movers on VNX 7.0 79

Index

MPFS restrictions 13 unloading VDM

permanently 58
temporarily 57
N user interface choices 14
network connectivity, displaying 55
network requirements 12 V
VDMs
R changing states 56
renaming VDMs 59 concepts 18
requirements, system 12 creating 32
restrictions 12 creating CIFS servers 44
displaying information 50
internationalization mode 47
S querying 50
renaming 59
server table, displaying 50 unloading permanently 58
shares, creating for VDM CIFS servers 46 unloading temporarily 57
software requirements 12 verifying
state of VDM, changing 56 CIFS shares in VDM 46
storage requirements 12 size of root file system 37
system requirements 12 VNX 11
VNX Data Migration Service 12
T VNX Replicator 23

temporarily unmounted file systems, displaying 52

troubleshooting W
CIFS server accessibility errors 74 warnings 13
unloading VDMs 74

U
Unicode mode 47

80 Configuring Virtual Data Movers on VNX 7.0