VMAX3TM Family ENAS Installation and Maintenance - SRG

Welcome to the VMAX3 Family eNAS Installation and Maintenance eLearning.
Click the Notes tab to view text that corresponds to the audio recording.
Click the Resources tab to download a PDF version of this eLearning.
Copyright 1996, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013 ,
2014, 2015 EMC Corporation. All Rights Reserved. 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.
EMC2, EMC, Data Domain, RSA, EMC Centera, EMC ControlCenter, EMC LifeLine, EMC OnCourse, EMC Proven, EMC
Snap, EMC SourceOne, EMC Storage Administrator, Acartus, Access Logix, AdvantEdge, AlphaStor,
ApplicationXtender, ArchiveXtender, Atmos, Authentica, Authentic Problems, Automated Resource Manager,
AutoStart, AutoSwap, AVALONidm, Avamar, Captiva, Catalog Solution, C-Clip, Celerra, Celerra Replicator, Centera,
CenterStage, CentraStar, ClaimPack, ClaimsEditor, CLARiiON, ClientPak, Codebook Correlation Technology,
Common Information Model, Configuration Intelligence, Configuresoft, Connectrix, CopyCross, CopyPoint, Dantz,
DatabaseXtender, Direct Matrix Architecture, DiskXtender, DiskXtender 2000, Document Sciences, Documentum,
elnput, ECS, E-Lab, EmailXaminer, EmailXtender, Enginuity, eRoom, Event Explorer, FarPoint, FirstPass, FLARE,
FormWare, Geosynchrony, Global File Virtualization, Graphic Visualization, Greenplum, HighRoad, HomeBase,
InfoMover, Infoscape, Infra, InputAccel, InputAccel Express, Invista, Ionix, ISIS, Max Retriever, MediaStor,
MirrorView, Navisphere, NetWorker, nLayers, OnAlert, OpenScale, PixTools, Powerlink, PowerPath, PowerSnap,
QuickScan, Rainfinity, RepliCare, RepliStor, ResourcePak, Retrospect, RSA, the RSA logo, SafeLine, SAN Advisor,
SAN Copy, SAN Manager, Smarts, SnapImage, SnapSure, SnapView, SRDF, StorageScope, SupportMate,
SymmAPI, SymmEnabler, Symmetrix, Symmetrix DMX, Symmetrix VMAX, TimeFinder, UltraFlex, UltraPoint,
UltraScale, Unisphere, VMAX, Vblock, Viewlets, Virtual Matrix, Virtual Matrix Architecture, ViPR, Virtual
Provisioning, VisualSAN, VisualSRM, Voyence, VPLEX, VSAM-Assist, WebXtender, xPression, xPresso, YottaYotta,
the EMC logo, and where information lives, are registered trademarks or trademarks of EMC Corporation in the
United States and other countries.
All other trademarks used herein are the property of their respective owners.
Copyright 2015EMC Corporation. All rights reserved. Published in the USA.
Copyright 2015 EMC Corporation. All rights reserved. 1

This course provides a detailed review of the installation and maintenance processes unique
to the VMAX3 with eNAS solution. Topics included in this course are upgrading eNAS
service release code, and replacing faulty hardware components while understanding the
interaction and effect on Network Storage.
Access to the eNAS control station components through the GOS Service Access feature of
the Management Module Control Station (MMCS) will be explained and demonstrated.
Additional procedures for eNAS based alerts and diagnostic gathering will be explained as
well as setup of eNAS call home through ConnectEMC.
This course is intended for those with knowledge of the VMAX 3 family storage arrays who
are responsible for installation and maintenance of VMAX 3 with eNAS systems.

This lessons topics include a discussion of Embedded NAS and EMC physical NAS hardware,
differences and compatibilities. At this time, an upgrade of currently installed VMAX3 to a
VMAX3 with eNAS is NOT available. We will discuss the installation process of a new
VMAX3 with eNAS. We will demonstrate the upgrade a VMAX3 with eNAS to the next
service release of Hypermax OS.

Lets start with a brief review of Embedded NAS and how it differs from its hardware
counterpart. On the left is an example of EMC VMAX 10K file hardware including Control
Stations to manage and monitor the NAS environment, Data Movers that perform the actual
file server functions, and VMAX storage.
On the right is an eNAS Container running on a VMAX3 storage array. The very same
capability of the physical VMAX 10K NAS Filer hardware and the VG Gateway is virtualized
in multiple containers which utilize director cores, memory, and access ports from an
Ethernet SLIC for network connectivity to hosts and clients. The next pages will outline the
different eNAS containers and the access to dedicated SLIC ports.

The embedded NAS guests consist of Control Station containers running the Linux operating
system and Data Mover containers running the DART (Data Access in Real Time) operating
system.
The Control Station is used to configure and manage the Data Mover(s), monitor Data
Mover operations for alerts and errors, provide an entry point for remote service access,
and provide call home and e-mail notification services.
The Data Mover consumes block storage on the VMAX 3 and provides file services to the
customers I/P storage network. The Data Mover data path is independent of the Control
Station and can function even if the Control Station is unavailable.
The eNAS solution requires four or six containers for high availability and scale. This
includes two Control Stations (CS0, CS1) with external network access through the MMCS
NAT gateway for management, and two or four Data Movers with external network access
directly through the PCI-Pass-through SLICs for network file services.
File services management are initiated from the File Dashboard in Unisphere for VMAX. The
admin can also use Unisphere for VNX and access VMAX via Link and Launch.
It should be noted that the management model for eNAS is a combination of Symmwin,
Unisphere for VMAX and Unisphere for VNX.

In a PCI-Pass Through configuration, a SLIC is directly accessible to and managed by the
Virtual Machine. Enginuity only has visibility to a PCI-Pass Through SLIC for the purpose of
failure detection and notification. Ethernet SLICs can be used by eNAS Data Movers for IP
File access and Fiber Channel SLICs can be used by eNAS Data Movers for NDMP backup to
tape in VMAX3 configurations. When used by a Virtual Machine within a container, a SLIC is
dedicated to the Virtual Machine.

Legacy File Services;
First - Control and data LUNs are provisioned on FA ports to support file access via a NAS
gateway
Second - LUNs are made visible to the NAS gateway across the SAN
Third - LUNs are discovered by the NAS gateway and capacity is configured as file systems
Fourth - File systems are exported for user access on the LAN as NFS or CIFS/SMB file
shares
Embedded NAS;
First - Boot, Control and data LUNs are provisioned on ports for eNAS containers
Second - LUNs are visible to Control Station and Data Mover containers
Third - LUNs are discovered by embedded NAS and capacity is configured as file systems
Fourth - File systems are exported for user access on the LAN as NFS or CIFS/SMB file
shares

VMAX3 eNAS dramatically changes the traditional architecture of a VMAX and NAS solution.
In previous versions the NAS component leveraged physical VNX hardware either through a
gateway implementation or, in a more recent release, a unified solution.
The traditional data mover and control station hardware is replaced with embedded VMs
running on the FA emulation. The VMs use virtual networking interfaces for connectivity
between integral members in the Embedded Cabinet. The Engine management module as
seen in traditional enclosure is replaced with the Intelligent Platform Management Interface
(IPMI) 2.0 compliant Baseboard Management Controller (BMC) service accessible using IPMI
Keyboard Controller Style (KCS) and Remote Management and Control Protocol (RMCP)
interfaces.
Access to block data for embedded NAS is hosted in a Container by software emulation
called a Cut-through device (CTD) which acts like an HBA to access the LUNs on the VMAX 3
array. Connectivity to the NAS clients is provided using either 1GbE or 10GbE SLICs
dedicated to the Data Mover VM inside the Container. There is also an option to use an 8Gb
FC SLIC for NDMP backup to tape.
Access to the eNAS management stack on the Control Station VM uses NAT services
provided by the virtual networking infrastructure of the VMAX array and is supported
through a separate black cable with an RJ-45 connector on the MMCS. This second MMCS
Ethernet connect is separate from the one used by the MMCS for ESRS and Remote
Connect.

A minor but very important item for the MMCS cabling is the location of the embedded
container Virtual Machine Ethernet connection. The black cable in the three wire Ethernet
cable bundle supplies this connection. There is no container communication through the
MMCS RJ-45 connection to the customer network.

For this eLearning session, we will assume that the equipment has been acclimated to the
site, put into place on the computer room floor, assembled, cabled and initially powered up.
Details for all of those steps can be found in the EMC VMAX3 TM Family VMAX 100K, 200K,
400K Installation Guide.
At this time, there is no upgrade path for a previously installed VMAX 3 to add the
embedded NAS solution. Only new VMAX3 systems shipped from EMC manufacturing and
preconfigured with eNAS software can be installed with the eNAS solution. Configurations
are gathered by pre-sales using the Sizer Tool and custom built in EMC manufacturing
according to the customers Sales Order.
The SolVe Enhanced Procedure Generator will help to guide you through the rest of the
customer site setup for VMAX3 with eNAS.

Once the new VMAX3 system has been cabled and powered up, the next step is to verify
the configuration is operational. From Simplified SymmWin, you must run the Verify VMAX
Setup script before turning the array over to the customer. The script verifies the
configuration and status of the system hardware and software. Please be aware that the
Verify VMAX Setup script will take the VMAX3 offline.
From MMCS-1 (Management Module Control Station), login with a credential and open
Simplified SymmWin. Verify the (eNAS) notation on the same line as the system serial
number and code release level. From the System Management view, select the Verify
VMAX setup script.
Please note that a standard installation does NOT include running the Configure and Install
New Symmetrix script. If you just completed the Configure and Install New Symmetrix
script for a non-standard installation, you do NOT have to run the Verify VMAX Setup script
as well.

The next two windows are standard for most Simplified SymmWin scripts. The Identify
Task window will open. Click next to start, or cancel to exit the script.
The Confirmation window will open next. Again, click next to start, or cancel to exit
the script.

The next view is the Select MMCS Connectivity page. To access the VMAX3 remotely,
select the IP Connection radio button, fill in MMCS IP details, and then click next. This
information can also be updated at a later time.

Configure eNAS connectivity details here. We are using IPV4 network addresses in the
example. Note that the IPV6 addresses are left blank. Name the primary and secondary
control stations, supply an IP address and net mask for each NAT instance, then click next
to continue.

Configure eNAS Domain Name Services details here. Enter the primary and secondary DNS
server IP addresses, routing addresses, net masks and then click next to continue.
Note; We are using IPV4 network addresses in the example and the IPV6 addresses are left
blank.

Click next to start the back end cabling verification.

Next, power cable verification takes place. Click finish to proceed.

Verify VMAX setup has successfully completed, click Close to finish.

Before performing an ENAS code upgrade, please make sure the following Off-Site
Preparation pre-requisites are met: Run the Symmetrix Enhanced Procedure Generator
(EPG), selecting the "Online Code upgrade" option in order to generate the EPG Procedure
and ETA Warnings List. If the user selects that they would like Remote Proactive to perform
the upgrade, a link is provided in order to schedule the activity once the procedure is
generated.
If the task is scheduled with Remote Proactive, and the remote transfer of HYPERMAX OS to
the MMCS fails, then the local CE will be engaged to copy the code to the MMCS onsite
(refer to article 194656 VMAX3: HYPERMAX OS upgrades and file transfers).
If Remote Proactive has not been engaged to perform the HYPERMAX OS upgrade then all
procedures and warnings must be reviewed by the local CE prior to going to the customer's
site.
Following the Q4 2014 SR release, there will be two folders on the FTP location for
HYPERMAX OS downloads; 5977.xxx.xxx with Embedded eNAS and 5977.xxx.xxx without
Embedded eNAS. Copy the version relevant to the activity; if eNAS is not configured, copy
the OS from the without folder.

Refer to the generated EPG Procedure. Copy the HYPERMAX OS to the O:\Newcode folder
(Not Applicable if already transferred by Remote Proactive)
Warning!!: For online code upgrades, check to see that the "runenginuityinstaller.exe" is
present in the O:\EMC\Symmwin folder.
If it is present then the Online Code Load script will self extract the code in the Newcode
folder.
If is NOT present then copy the "runenginuityinstaller.exe" from the O:\EMC\OLD_SW to

the O:\EMC\Symmwin folder before proceeding to run the script.
If the "runenginuityinstaller.exe" is not present in the O:\EMC\OLD_SW folder it can be

downloaded from \\ssr\public\V3\runinstall and copied to the O:\EMC\Symmwin folder
(make sure to rename it from runenginuityinstaller.emc to runenginuityinstaller.exe).
Refer to article 195457 VMAX3: Online Code Load script fails; no errors posted for further
details.

Before performing the eNAS upgrade, please make sure the following pre-requisites are
met: NAS services need to be in a good state: ENAS upgrade can be performed on a
system where eNAS guests are in an installed and running state. All NAS services should be
in good state for the eNAS upgrade to take place. To verify this, run the PSE Health check
script from here; Simplified SymmWin (System Management Health Check)

The health check script shown here performs several system related hardware checks. It
also checks the status of guest containers and verifies the status of services running on all
guest containers. In case guest services are not running, it will report an error for that.
On successful completion of the health check script, a successful tag will appear against
the field eNAS guest services. Click Finish to end the script.

Copy the Enginuity Installer Bundle to the O:\NEWCODE location inside the MMCS. The
online code load script expects this package to be present here.
The online code load script will detect if an eNAS upgrade is needed by comparing current
EPACK version with the installed version on eNAS guests. You can check the source version
from the manifest file in O:\NEWCODE.

Start the online code load script from here: Simplified SymmWin (System Management
Online Code Load.

The script next prompts for confirmation to start the upgrade procedure. First, Enginuity
upgrade will be carried out. After that the script will again prompt for starting GOS
upgrade. Give confirmation to start the Online Code load script by clicking on YES.

Click on close to allow the script to run the Enginuity installer.

The installer will automatically put a checked box against those components which need to
be upgraded: Scroll down to the end to make sure eNAS guests are marked checked
The installer will see if the new eNAS image is a higher version than the installed image. If
the installer finds that the available version of eNAS image is lower than installed version, it
will not copy EPACK from O:\NEWCODE to O:\EMC\GuestOS\Images\NAS\Image location.
Click Next and let the installer run with default option Service Processor. Once the
installer finishes, click on Finish. The MMCS will then reboot.

After reboot, the MMCS comes up and the online code load script automatically resumes
from the next step. Click Next to continue. Directors will get loaded with new Enginuity
next.

Now the tools guest upgrade will start. Click Finish to start the tools guest upgrade. Note:
This step will not happen if tools are already upgraded.

The embedded NAS upgrade starts next. As part of the eNAS upgrade process, Data Mover
VMs get loaded with a new DART image and then have to be rebooted to get the new DART
image running.
The script prompts the CE to specify whether the data movers should be allowed to be
rebooted during upgrade procedure or if they should be manually rebooted after upgrade
completion. If the Data Movers are automatically rebooted, clients will loose access to files
served by each primary Data Mover and the Data Movers will not automatically fail over to
the secondary Data Mover.
WARNING: If you have not coordinated a Network Storage shutdown with the customer,
select the Manually Reboot option and click Finish to start upgrade. If you select Manually
reboot or failover Data Mover, the eNAS upgrade is not complete until after the reboot or
failover completes.

Once the eNAS upgrade completes, completion of Online Code load script gets marked. A
final summary page shows what uCode fixes were loaded as part of Enginuity upgrade. The
lower half of summary shows the eNAS upgrade summary, showing version changes.
Click close to exit.
Please note; eNAS ONLY patch management is also run through the EPACK process.

This lesson will describe the tools available to access an eNAS container, describe the steps
involved with a planned shutdown and controlled restart of the eNAS containers, and
describe the process to back-up the NAS Database.

The Guest OS Services Access tool is used to initiate an SSH session to either of the eNAS
control stations. From the control station, CLI commands can be issued to the data movers
or control station for a variety of purposes. To open the Guest OS Service Access tool, go
to the MMCS desktop and double click the gosserviceaccess icon. Select SSH, and click
next. Then select CS-0 and click next again.

When the CS-0 icon appears, select it and click Connect to open an SSH terminal. You will
be Logged-in to CS-0 as an authorized nasadmin level user.
Use the nas_version command to validate the eNAS code level.
The server_version command will verify the code version on the data movers.
The next slide gives additional verification commands and information.

The getreason command will verify the correct slot locations for the eNAS containers. A
Reason Code of 10 is the Primary Control Station, Reason Code 11 is the Secondary Control
Station. A Reason Code of 5 shows the Data Mover is communicating with the Control
Station. Additional Reason Codes can be found on the next slide and a full list of All Reason
Codes is downloadable from the student materials area.
The nas_server command gives additional Data Mover information. ID-1 and type-1 is
the primary data mover, state 0 shows it is running. ID-2 and type-4 is the stand-by data
mover and a state 0 shows it is running and available as a stand-by.
The t2slot command confirms we are logged into slot_0, CS-0 . A response of 1 should
be seen when logged into CS-1.
The t2cab command shows that this is in fact, an embedded NAS configuration rather
than physical NAS components.
Note; The term slot is a reference to the container that a VM is running in. When
containers are created in a configuration, a slot number is assigned to each as a unique
identifier. Control Stations, Data Movers, and Tools all have their own unique slot.

This is a sample list of the possible reason codes associated with the NAS command
Getreason. The reason codes are generated by the DART and Control Station software at
various points in their lifecycle. All of these Reason Codes apply to the VNX NAS
implementation. Not all of these Reason code will be implemented in the eNAS Solution.
A complete list of all Reason Codes will be included with the downloadable student material.

Enter the command /nas/sbin/nas_halt -f now to systematically shut down all eNAS
services including Data Movers and Control Stations.
WARNING! Only use this command when you have scheduled a shutdown with your
customer.
Caution: This command will disrupt ALL customer network storage access through the
VMAX3.

This next sequence describes the steps involved in starting up the Virtual Machine
containers from SymmWin. This procedure can also be used to restart any of the Guest OS
containers. Log in to the Management Module Control Station (MMCS) as a credentialed
user.
Start SymmWin, then boot all software Data Movers (DM-2, DM-3, etc.) by using the Guest
OS State Control script. To start the script, in SymmWin select: Procedures > Procedure
Wizard > CE/RTS/PSE Services > Guest OS Utilities > Guest OS State Control, then click
Run.
The state change warning message will display. Click Yes to proceed.
Please note; the customer cannot run this power up procedure. A properly credentialed
CE/PSE must be engaged to access the Guest OS State Control script from within
SymmWin.

Next, select the Guest OS command to be run. Select Start and click OK. Then choose
the Select Guests option and click OK.

To correctly start the eNAS containers, the Data Movers must be started and running when
the Control Station boots. DM-2 and DM-3 have been checked. Continue by clicking OK.
The Data Movers will show a status of running almost immediately. Allow 4 -5 minutes to
pass to allow the Data Movers to boot completely.
Then, choose the Select New Command option and click OK.

From the Select Guest OS Command prompt, select the Start command. Then click OK.
Choose the Select Guests option and click OK.

The Control Stations should be started individually. Start CS-0, the Primary Control Station
first. Check the box for CS-0 and then click OK.
Once CS-0 changes state to Running, wait an additional 2 to 3 minutes to let the control
station boot progress, then choose the Select New Command option and click OK.

Select the Guest OS Command to Start and click OK. Then choose Select Guests and
click OK.

Finally, choose CS-1 with the check box and click OK. The Guest State for CS-1 changes
to Running. Select the Done with the Script! option and click OK.

The display shows all Data Movers and Control Station Guests running. The Green Box
indicates the script completed successfully. Click OK to end the script.

This section will discuss a safe way to backup, save to an external location and restore the
eNAS Data Base. This process will need to be done any time either or both eNAS Control
Station containers are rebuilt. Saving a copy of the eNAS DB backup to another location
external to eNAS storage is good insurance.
Warning: Restoring eNAS data will recover all file systems and configuration for
replication/DM interfaces, but all file systems will come back in un-mounted and un-
exported form. File systems will have to be mounted on the Data Mover and exported as
respective CIFS/NFS shares again after restoration.

The eNAS system automatically backs up the entire database and saves it as
nasdb_backup.1.tar.gz in the /nas/var/backup directory. It does this 1 minute after each
hour. It also maintains the last 12 backup files.
You can manually create a database backup any time. First, log in to CS-0, using
gosserviceaccess from the MMCS, then SU to nasadmin user. Next, list the eNAS
database backup files by typing the command: ls -l /nas/var/backup/nasdb*.
Verify a current version of nasdb_backup.1.tar.gz exists. Ensure that nasadmin is the

group and owner of nasdb_backup.1.tar.gz and _nasbkup files.
Check that the amount of free space in the root file system is greater than the size of the
most recent database backup by typing the command: df -k / The system returns the
amount of free space in kilobytes (KB).
Create a backup of the eNAS database by typing the command:

/nas/sbin/nasdb_backup /nas /celerra/backup <yymmdd> where <yymmdd> is
the last two digits of the current year, the two-digit month and the two-digit day.

When the backup completes, confirm that the backup file,
nasdb_backup.<yymmdd>.tar.gz, was created by typing the command: ls -l
/celerra/backup
Use secure FTP or SCP to copy nasdb_backup.<yymmdd>.tar.gz and

nasdb_backup.b.tar.gz to a remote location.

In this lesson, we will discuss the interaction between the eNAS containers and VMAX 3
hardware and the effect that hardware failure can have on the eNAS containers, the steps
to perform an eNAS container failover and failback, the steps to replace an eNAS configured
SLIC and other common FRUs.
Before beginning this lesson, please access the SolVe Desktop, VMAX 3 Family of products.
Print a copy of and review the Service Procedure EMC Embedded NAS for the VMAX3
Family arrays, System Upgrade, Replacement, and Recovery Procedures.

When the eNAS Solution is configure as part of the VMAX 3, the hardware replacement
scripts in Simplified SymmWin are aware of the presence of eNAS containers and will
respond accordingly.
If a SLIC that is configure to a Data Mover fails, that Data Mover will need to be failed over
to the standby Data Mover. The failover action can be executed from either Unisphere for
VNX or through an ssh session to the Primary Control Station through the GOSSERVICES
Access utility on the MMCS desktop.
Nearly all hardware maintenance affecting eNAS components will have an impact on the
customers storage network. Director board and related failures will require CAREFULLY
assessing the location of eNAS containers to determine if their location is within the failing
Director board or related component. An eNAS container will need to be failed over to its
standby if it is hosted on a director affected by a hardware failure. Please follow the
precautions listed in the Service Procedure.

To see how eNAS containers are mapped to VMAX 3 directors, go to Symmwin, select the
IMPL file from System and then display the GuestOS configuration. The display shows the
director and slice location for each of the configured eNAS and Tools containers.
Notice that the Primary and Secondary Control Stations are located on different director
boards. The primary and standby Data Movers are likewise located on different directors.
Also, CS-0 and DM-2 are staggered across different director boards.

SLIC module replacement for eNAS configured SLICs will have multiple stages to the
replacement process. The FRU replacement script will be started as normal. The script will
notify the service engineer that an eNAS Data Mover container is affected and a failover to
the standby Data Mover will be required. Only then can the replacement script continue to
completion. Once the replacement script is complete, the affected Data Mover will need to
be failed back and the standby Data Mover resume its role.
In general, the Control Station should not be effected by this service procedure.

The SLIC replacement begins as any other FRU replacement service call would. The service
engineer follows the standard FRU replacement process up to the point when the
replacement script gets to step 2 confirmation. At this point the script advises of eNAS
containers that will be impacted. Using the Service Procedure document referenced, the
service engineer must follow the steps described before continuing with the replacement
script.
The script instructs the user to refer to the service procedure document, EMC Embedded
NAS for the VMAX3 Family arrays System Upgrade, Replacement and Recovery Procedure
available through the SolVe Desktop.
Once the Data Mover has been failed over to the stand by Data Mover, the script can be
resumed. The script will then continue as normal and instruct the CE of the FRU to be
changed, guide them through the process, then initialize the new part and complete the
script.
The script will the show this display again, so the Data Mover can be returned to an active
state and the stand by retuned to a ready state.

This demo will show the process of replacing a SLIC that is in use by an eNAS Data Mover.
It demonstrates the FRU replacement script, the Data Mover Impact notice, fail over of the
Data Mover, return and finish of the FRU replacement and finally fail back of the affected
Data Mover.

For replacement of any of the following components, please refer to the Director
Replacement service procedure in EMC Embedded NAS for the VMAX3 Family arrays
System Upgrade, Replacement and Recovery Procedure guide available on the SolVe
Desktop.
Dual Inline Memory Module (DIMM) card replacement
Management module replacement
Engine replacement
System interface board replacement
SFP replacement 10Gb Ethernet 2 Port Optical and 8Gb FC 4 Port
The eNAS containers to be failed-over will vary widely based on the eNAS configuration, but
the FRU replacements will all be similar to the non eNAS FRU replacements except for the
eNAS Notice of Impact.

VMAX3 with eNAS is unique in that both the MMCS and the eNAS Control Station have Call
Home functionality. Given this duality of functionality, an eNAS call home could be a result
of a VMAX hardware malfunction. Either or both MMCS and Control Station may call home
for a hardware malfunction. Service must decide on who owns the call in order to respond
and they may need support from the other calling element.
Alerts and Notifications can be set up in the eNAS environment via Unisphere for VNX in a
very similar fashion to hardware based NAS in the Unified VNX. We will cover the basics in
this lesson.
eNAS Diagnostic information is likewise very similar to hardware NAS. Call Home setup will
be described as well.

The challenge is to treat eNAS as a solution under VMAX 3 and NOT as two separate
products. Both have their own call home stream. The streams are merged at the ESRS
Service Link and a determination made as to whether the call originated with VMAX or
eNAS. SYR will make a distinction that this is an eNAS solution in a VMAX 3 vs. a physical
NAS box. The call will be routed to NAS support.
Who is responsible if a VMAX Director calls home but is affecting a Data Mover or Control
Station hosted on that Director? Support needs to avoid handing off the Service Request or
passing it back and forth. VMAX Support will get the call. To properly respond, VMAX
Support will need some basic NAS skills. This avoids the back and forth hand off. If
escalation is required, the NAS Support will get involved.
The VMAX Support skill set will be augmented with additional basic NAS skills (provided by
this training and the eNAS Primer for VMAX3 Family eNAS Implementation) and the Field
engineer taking the call on site will have the same additional basic NAS skills added to their
skill set.

The title line which displays the serial number, site location, and code level on both
SymmWin and Simplified SymmWin will also display the (eNAS) feature if it is installed.
Site Info also displays any additional solutions that are present on the machine.

Navigating from Unisphere for VMAX to the File Dashboard and then on to Unisphere for
VNX is straight forward. Starting from the Summary page after login, select the System tab
and then Dashboard from the drop down list.

From the Dashboard, select File Dashboard.

Then select Launch Unisphere for VNX. This will launch the login screen for Unisphere for
VNX. eNAS and File system management will then be displayed.

You can monitor and manage the eNAS system using alerts and notifications. The system
generates alerts as a result of system changes, some of which might be severe enough to
cause an error or disrupt user access. By using notifications, the Network Storage Manager
can specify a variety of actions such as sending an email, triggering an SNMP trap, or
updating a log file in response to these alerts.
To view eNAS alerts and notifications, launch Unisphere for VNX as described in the
previous slide. Select the correct system from the System pull down tab. Then select the
System tab as illustrated above. This will allow the selection of Alerts, Notifications, or
Event Logs.

To view an alert, start EMC Unisphere for VNX by clicking the File Dashboard in Unisphere
for VMAX and select the Launch Unisphere for VNX link. Log in as a root user. Select the
eNAS system from the All Systems drop-down list. On the System tab, click Monitoring and
Alerts and then click Alerts. Select an alert and click Details. The Alert Details window
appears and provides an alert description and a recommended action plan. Click Save or
click OK to close. To delete an alert, click on Delete rather than Details. Then click Yes to
delete the alert.

To view a notification, the process is very similar to viewing alerts. From the File
Dashboard in Unisphere for VMAX, select the Launch Unisphere for VNX link. Log in as a
root user. Select the eNAS system from the All Systems drop-down list. On the System
tab, click Monitoring and Alerts and then click Notifications.
The Event tab is displayed by default and will list all current event notifications. The
customer can use the Create tab to set up new event notifications as well as viewing other
tabs to determine Storage Usage, Storage Projections, and Data Mover load.

To view Event Logs, the process is again very similar to viewing Alerts. From the File
Dashboard in Unisphere for VMAX select the Launch Unisphere for VNX link. Log in as a
root user. Select the eNAS system from the All Systems drop-down list. On the System
tab, click Monitoring and Alerts and then click Event Logs. Select the name of the log file
to view in the Show events for list box. Optionally, select the time span that the log file is
to cover in the Time Interval list box and choose the severity level of events to include in
the display in the Severity Level list box.

To set up the automatic collection and transfer of Log Files, start EMC Unisphere for VNX
and log in as a root user. Select the eNAS system in the All Systems drop-down list. On
the System tab, click Automatic Log Transfer in the list of Service Tasks.
Do one of the following: Set Enable Automatic Transfer to enable automatic collection and
transfer of log files or Clear Enable Automatic Transfer to prevent automatic collection and
transfer of log files. Then click Apply.
Note: To transfer log files to your EMC-approved service provider automatically, ensure that
Connect EMC is active and configured correctly. For more information, reference the Call
Home using Connect EMC Service Procedure. Contact EMC Customer support to determine
your EMC-approved service provider.

To collect and transfer log files manually, log in to the eNAS Control Station (CS), using
gosserviceaccess from the MMCS desktop, as a nasadmin user. Change the current
directory to /nas/tools.
Collect the log files and add them to a .zip file in /nas/var/emcsupport by typing the
command ./automaticcollection -getlogs The name of the .zip file has the following
format: support_materials_SerialNumber.DateTime.zip Where: SerialNumber is a serial
number that eNAS generates for the archive. DateTime is the date and time when you
created the .zip file. This script takes several minutes to run.
Transfer the log files to your EMC-approved service provider using FTP by typing the
command ./automaticcollection -transferlogs. Log out of the eNAS Control Station by
typing: Exit
Note: There is a substantial amount of information collected with this procedure. The
screen capture has been greatly truncated.
To transfer log files to your service provider, ensure that Connect EMC is active and
configured correctly. For more information, reference the Call Home using Connect EMC
Service Procedure.

To configure ConnectEMC properties, start EMC Unisphere for VNX by clicking the File
Dashboard in Unisphere for VMAX and select the Launch Unisphere for VNX link. Log in as
a root user. Select the eNAS system from the All Systems drop-down list. Click the System
tab. In the column on the right of the screen click Manage Connect Home under Service
Tasks. From the pop-up screen, select the method to call home and populate the fields.
Delivery methods include, ESRS, Email, FTP, and HTTPS. Click Apply on the Manage
Connect Home window. A confirmation message shows that configuration was successful.

You may want to test ConnectEMC. Select a delivery method from the Test Type list box
and click Test. A message window appears confirming the test was successful. Repeat this
step for each delivery method configured. Confirm Call Home was successful by checking
SYR for a test dialhome:
http://omega.eng.emc.com/omega/Apps/AppsContainer.asp?DefaultAppID=1.

For additional information on NAS concepts, this list provides a number of available VNX
training courses that can be found on the Education Services web site:
\\edu.corp.emc.com\
Global Technical Training
All CS/GTS personnel should complete the VMAX3 (VMAX 100K, 200K, 400K) Series
eLearning and Remote Lab Launch Training modules within three quarters after GA.
Selected CS/ GTS personnel must also take the Instructor Led Training (ILT) sessions which
started July 28, 2015. Service Partners (and Drive Pros) must also plan to consume this
training as required. Additional information can be found on the Global Technical Training
Services web site: http://education.emc.com.
Below is the listing and registration links for the required courses for this release.
Training: http://education.emc.com
For a complete detailed list of courses, visit the VMAX Launch page:
http://edu.corp.emc.com/gs/programs/npl.aspx
VMAX3TM Family with HYPERMAX OS 5977 Q4 2015 SR Launch Overview:
This course provides an overview of VMAX3 with HYPERMAX OS 5977 Q4 2015 Service
Release.
Target Audience: This course is intended for those with knowledge of VMAX3 with
HYPERMAX OS 5977 who are responsible for implementing, configuring, monitoring and
managing VMAX3 arrays with the Q4 2015 Service Release (SA/ DA/ FSS/ TSE/ ASE/ CSE).
Delivery Type: eLearning
Duration: 30 Minutes

Registration: https://education.emc.com/index_login.htm?id=746398853
Copyright 2015 EMC Corporation. All rights reserved. #

These are the key points discussed in this training. They include installation of new VMAX 3
Family arrays with the eNAS solution from manufacturing and the upgrade of those arrays
to new code releases, the tools for working with eNAS containers, component replacement
in VMAX3 Family arrays with the eNAS solution.
This concludes the training. Proceed to the course assessment on the next slide.

Your feedback is important please take a moment to complete the feedback form.

VMAX3TM Family ENAS Installation and Maintenance - SRG

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

VMAX3TM Family ENAS Installation and Maintenance - SRG

Caricato da

Copyright:

Formati disponibili

Welcome to the VMAX3 Family eNAS Installation and Maintenance eLearning.

Click the Resources tab to download a PDF version of this eLearning.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS IS. EMC CORPORATION MAKES NO

Copyright 2015EMC Corporation. All rights reserved. Published in the USA.

Copyright 2015 EMC Corporation. All rights reserved. 1

Copyright 2015 EMC Corporation. All rights reserved. 2

Copyright 2015 EMC Corporation. All rights reserved. 3

Copyright 2015 EMC Corporation. All rights reserved. 4

Copyright 2015 EMC Corporation. All rights reserved. 5

Copyright 2015 EMC Corporation. All rights reserved. 6

Copyright 2015 EMC Corporation. All rights reserved. 7

Copyright 2015 EMC Corporation. All rights reserved. 8

Copyright 2015 EMC Corporation. All rights reserved. 9

Copyright 2015 EMC Corporation. All rights reserved. 10

Copyright 2015 EMC Corporation. All rights reserved. 11

Copyright 2015 EMC Corporation. All rights reserved. 12

Copyright 2015 EMC Corporation. All rights reserved. 13

Copyright 2015 EMC Corporation. All rights reserved. 14

Copyright 2015 EMC Corporation. All rights reserved. 15

Copyright 2015 EMC Corporation. All rights reserved. 16

Copyright 2015 EMC Corporation. All rights reserved. 17

Copyright 2015 EMC Corporation. All rights reserved. 18

Copyright 2015 EMC Corporation. All rights reserved. 19

If is NOT present then copy the "runenginuityinstaller.exe" from the O:\EMC\OLD_SW to

If the "runenginuityinstaller.exe" is not present in the O:\EMC\OLD_SW folder it can be

Copyright 2015 EMC Corporation. All rights reserved. 20

Copyright 2015 EMC Corporation. All rights reserved. 21

Copyright 2015 EMC Corporation. All rights reserved. 22

Copyright 2015 EMC Corporation. All rights reserved. 23

Copyright 2015 EMC Corporation. All rights reserved. 24

Copyright 2015 EMC Corporation. All rights reserved. 25

Copyright 2015 EMC Corporation. All rights reserved. 26

Copyright 2015 EMC Corporation. All rights reserved. 27

Copyright 2015 EMC Corporation. All rights reserved. 28

Copyright 2015 EMC Corporation. All rights reserved. 29

Copyright 2015 EMC Corporation. All rights reserved. 30

Click close to exit.

Copyright 2015 EMC Corporation. All rights reserved. 31

Copyright 2015 EMC Corporation. All rights reserved. 32

Copyright 2015 EMC Corporation. All rights reserved. 33

Use the nas_version command to validate the eNAS code level.

The next slide gives additional verification commands and information.

Copyright 2015 EMC Corporation. All rights reserved. 34

Copyright 2015 EMC Corporation. All rights reserved. 35

Copyright 2015 EMC Corporation. All rights reserved. 36

Copyright 2015 EMC Corporation. All rights reserved. 37

Copyright 2015 EMC Corporation. All rights reserved. 38

Copyright 2015 EMC Corporation. All rights reserved. 39

Copyright 2015 EMC Corporation. All rights reserved. 40

Choose the Select Guests option and click OK.

Copyright 2015 EMC Corporation. All rights reserved. 41

Copyright 2015 EMC Corporation. All rights reserved. 42

Copyright 2015 EMC Corporation. All rights reserved. 43

Copyright 2015 EMC Corporation. All rights reserved. 44

Copyright 2015 EMC Corporation. All rights reserved. 45

Copyright 2015 EMC Corporation. All rights reserved. 46

Verify a current version of nasdb_backup.1.tar.gz exists. Ensure that nasadmin is the

Create a backup of the eNAS database by typing the command:

Copyright 2015 EMC Corporation. All rights reserved. 47

Use secure FTP or SCP to copy nasdb_backup.<yymmdd>.tar.gz and

Copyright 2015 EMC Corporation. All rights reserved. 48

Copyright 2015 EMC Corporation. All rights reserved. 49

Copyright 2015 EMC Corporation. All rights reserved. 50