EMC Smarts Server Manager Installation and Implementation

Welcome to EMC Smarts Server Manager Installation & Implementation.
Click the Notes tab to view text that corresponds to the audio recording.
Click the Supporting Materials tab to download a PDF version of this eLearning.
Copyright 1996, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012 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, 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, 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 2012 EMC Corporation. All rights reserved. Published in the USA.
Published DATE : August 2012
Revision Number: MR-1WN-EISMII.9.0.1.0
Copyright 2012 EMC Corporation. Do not copy - All Rights Reserved.
EMC Smarts Server Manager Installation & Implementation
Upon completion of this course, you should be able to install the Server Manager application
and integrate the Server Manager application into an EMC Smarts management solution.
This module focuses on the installation requirements of Server Manager, and provides an
overview of the full installation process.
Version 9.0.0 of EMC Smarts Server Manager is compatible with these versions of EMC
Smarts IP Management Suite and EMC Smarts Service Assurance Management Suite.
If the Server Manager domain is to be installed on a different host than the one hosting the
other EMC Smarts components, access to the broker from the EISM server will be required.
EISM may be installed on hosts running the 64 bit versions of Red Hat Enterprise Linux,
Solaris version 10, Or Windows Server 2008 Revision 2.
If Veritas clusters are to be managed, only the Solaris platform is supported.
EISM may be installed on a virtual machine hosted on a VMware ESX version 3.5 or a
VMware vSphere version 4.0 or 4.1i host. The virtual machine must meet the same
Operating System, RAM and CPU requirements of a comparable physical server.
Verify that your operating systems are patched to the levels recommended by the
manufacturer. The following patch levels have been identified as critical to the proper
functioning of the EMC Smarts software.
Please note that the Solaris patch, 120011-14, is part of a set of patches that must be
installed in a specific order. Install the Solaris 10 patch set for Sparc that includes 120011-14
or later.
Before performing the installation, please review the latest Installation Guide and Release
Notes to identify the most recent list of the supported software and operating systems, and
that currently required patches are installed on your systems.
There are several licenses they may be needed in running Server Manager.
The EMC Smarts Server Manager base license is required in all installations. The other
licenses are only needed if that type of management is to be performed by the server
manager.
EMC uses a tool called Powerlink Licensing , or PLL, to generate a License Authorization Code
for the software you have purchased. This code is required for you to obtain a permanent
license file. The code will be sent to you through e-mail, and you can then log into the EMC
customer support website (Powerlink) to obtain a valid software license. For temporary
(evaluation) licenses, contact your EMC account team.
Refer to the EMC Ionix ITOps System Administration Guide for more information on the new
process, and on how to relocate software to a new host and regenerate licenses.
There are five steps in installation of EMC Smarts Server Manager.

First, the software must be installed.
Next, license installation must be performed. This process is not covered by this course. For
information on obtaining and installing licenses, refer to the EMC Ionix ITOps System
Administration Guide available on the EMC Powerlink website.
Next, some of the required configuration must be done beforE the application services are
started.
Once these configurations are complete, the services must be started and the installation
verified.
Once the services are started, additional configurations must be implemented to integrate
Server Manager into the EMC Smarts Service Assurance Manager solution.
This module described the hardware, Operating System and EMC Smarts software
requirements for Server Manager. Licensing and installation tasks were also discussed.
EMC Smarts Server Manager Installation & Implementation 10
This module focuses on the installation of the Server Manager software. Three types of
installation are discussed. The standard installation using the wizard is covered, as well as
Installing Server Manager in unattended mode and from the Command Line.
EMC Smarts software is available in different forms. Purchasers of an EMC Smarts software
product receive their initial software as part of a physical package. This package contains the
software on DVD-ROM, as well as a set of documentation that includes the installation guide
and release notes.
Subsequent software updates, patches, and later releases are downloadable from the EMC
Powerlink website (powerlink.emc.com). Electronic forms of the software are available as an
ISO image, which can be used to create DVD-ROMs, or binary executables, available for each
supported OS platform.
Before installation of the EMC Server Manager Suite, stop all EMC Smarts services, EMC
Smarts daemon processes, EMC Smarts cron jobs, and any other process that uses programs
or libraries in any EMC Smarts installation area. Click OK in the Warning dialog box if you
have stopped all EMC Smarts services. Click Next in the Welcome screen to continue.
Next is disabled if you do not have administrative privileges for the products you are
attempting to install. A message also displays.
Next may also be disabled if your system failed the requirements check. If this occurs,
review the check results by clicking Get System Information, cancel the installation setup
program, and upgrade your system.
Click the first radio button to accept the terms of the end user license agreement. Failure to
accept causes installation to stop at this point.
Click Next to move on to the next screen and continue the installation.
Click Next to accept the default installation directory. For training purposes, the default
should be selected.
In your own environment, however, you can use your preferred directory. The default
installation directory is /opt/InCharge on UNIX or C:\InCharge on Windows. The location
directory to which you install the EMC Smarts product is referred to as the Base directory
and will be referred to as the abbreviation of BASEDIR.
If you specify a directory, be sure to use forward slashes for both UNIX and Windows
directories. Directory names cannot contain spaces. If the specified directory does not exist,
it is created. If you do not have write privileges, an error message displays.
Even though for the Server Manager Suite there is only one option to install, it is good
practice to select custom; if new features and options are added to EISM in subsequent
versions, it will ensure you only select the ones you want to install.
In the Feature Selection screen, you can select the features of the Server Manager Suite to
install. Currently there is only the one option so even though you selected Custom we are
installing All options.
EMC Smarts programs can be installed as services. On both Windows and UNIX, EMC Smarts
programs installed as services start automatically upon system reboot; those not installed as
services require that you issue commands to start and stop them as necessary.
It is recommended that in a production environment you install EMC Smarts programs as
services. When you choose to install a program as a service, the installation process
automatically sets up the program accordingly.
The Broker was installed as a service during the installation of Service Assurance Manager;
you do-not need to install it again.
EMC Smarts programs use the EMC Ionix Broker to determine where EMC Smarts
components are running. When a EMC Smarts component starts, it registers the host name
of the machine it is running on, as well as the TCP port on which it communicates, with the
broker. After that, the clients retrieve this information from the broker so that they can
communicate with the manager.
Specify the location of the existing broker. If all components are on the same machine, you
can keep the default values of local host for the host name and 426 for the port number. If it
is on a remote server, it is good practice to use a fully qualified domain name. The
information you add here is stored in the BASEDIR/smarts/local/conf/runcmd_env.sh if you
need to modify it after the installation process.
Make sure these are selected and click Next to continue.
Review the list of features that will be installed. Make sure adequate disk space is available.
To install the products, click Next and the Installation Progress screen displays.
The next screen can be monitored to ensure that installation is progressing.
Upon completion, the Installation Summary displays informational messages such as

successful confirmations, error messages, and warnings.
Click Finish to exit the installation. It is not necessary to reboot the system.
CLI mode provides a text-based method for invoking the installation program. This mode is
intended for UNIX platforms with non-graphics consoles. The CLI mode follows the same
process as the wizard mode but uses text rather than graphics.
During the installation processes, you are prompted with a series of steps and menus.
For prompts, accept the default value or select another choice. The default values are
indicated in brackets. To accept the default value, press Enter. To reply yes, type y; to
reply no, type n. Do not press Delete; this causes the process to terminate with an error
message.
For selections in menus, accept the default selections or type the number of the item and
press Enter. The default values are indicated in brackets or as pre-defined selections in
menus. An X is used to indicate the selected item. When you are finished making
selections, type zero (0) and press Enter.
If you incorrectly type an entry, press 5 to repeat the prompt and select the correct value.
Arrow keys and the Backspace key are not supported.
Unattended mode is supported for all operating systems but separate response files are
needed for UNIX and Windows systems. This method reads the selections and settings for
the installation from a user-modifiable file, which enables users to easily duplicate the
installation on many computer systems. Manual intervention is not necessary after you
execute the Setup command.
Please Note that the unattended install mode does not automatically copy repository files if
you are migrating from a previous version of the software. You must manually copy the
repository and configuration files after installation to complete the migration.
This module covered the installation of EMC Smarts Server Manager using the wizard,
unattended, and Command Line modes.
This module focuses on the configuration changes that must be made before activating the
Server Manager application service.
EMC Smarts uses SNMP traps to determine the status of topology objects. EMC Smarts
Server Manager uses traps from Veritas clusters for that purpose. All Veritas clusters should
be configured to send traps to the Server Manager at UDP port 9111.
Since other SNMP traps may be used by other Domain Managers, a common way to set up
the EMC Smarts solution is to have the infrastructure send all traps to what is referred to as a
trap exploder. After receiving a trap, the exploder is configured with information on all
systems that are interested in receiving traps, and which traps they are interested .
If a trap exploder is being used, it must be configured to forward the traps to the Server
Manager domain manager. The FORWARD command shown here is the line that must be
added to the trap exploder configuration. The word host in this line should be replaced
with the fully qualified domain name of the host on which Server Manager is installed.
Server Manager must be configured it to communicate with one or more IP domain

managers. By default it is configured to connect to one domain, named INCHARGE-AM-PM.
If the name of the IP domain in your EMC Smarts solution is different, the EISM.conf file
must be edited to reflect the correct name.
From a command line run the sm_edit command as it appears here.
Once the ESM.conf file is open in your editor, locate the lines specified in the second bullet.
Set the InChargeDomain & DomainName fields to your IP Availability Manager.
Set the DisplayName field to the name you want listed in the topology for the IP Availability
Manager.
Note that the Type attribute should always be set to AM
To configure additional IP Availability Manager sources, copy and paste the InChargeDomain
section, and repeat the above step.
Save & close the file.
This slide illustrates the original EISM.conf file with the domain name set to INCHARGE-AMPM.
The Federal Information Processing Standard Publication 140-2 is a U.S. government

computer security standard governing cryptographic modules. FIPS 140 Is required for any
software purchased by the U.S government and U.S military.
FIPS 140-2 is a standardized IT security accreditation program for cryptographic modules
produced by private sector vendors seeking certification for use in government departments
and regulated industries, such as financial and health-care institutions, that collect, store,
transfer, share and disseminate sensitive but unclassified information.
With the introduction of EMC Smarts version 8.1 SP2, a configuration parameter has been
introduced for FIPS 140 in the runcmd_env.sh file. The EMC Smarts administrator can enable
or disable this parameter as required. The default value of this parameter is FALSE.
When you install SAM 8.1.2, FIPS 140 is not enabled by default. You must enable FIPS 140 on
a clean installation or an upgrade, before the servers are started, using the following steps:
First, back up the imk.dat, brokerConnect.conf, serverConnect.conf and

clientConnect.conf files from the existing installation. These files are located in the
<BASEDIR>/local/conf folder. The backup is necessary in case you need to disable FIPS
140 mode and remove FIPS 140-2 encryption.
Next, run the sm_rebond command as specified here. As with the previous use of
sm_rebond, the path must be set to the default install path. Regardless of the FIPS
140 state, invoke the sm_rebond command from the BASEDIR where the software is
installed, not from any other product installation area which also has the sm_rebond
utility. When prompted, type a password to regenerate the imk.dat file. The default
password is the string Not a secret.
Please note that it is not recommended to enable and then disable FIPS. Though it is easy to
migrate data to FIPS support, the opposite is not true. Once data is migrated to FIPS-140
support, the only supported reversal is restoration of previous data which will most likely be
outdated.
The next step is to download and install the Unlimited Strength Jurisdiction Policy Files from
Oracle.
Go to the specified website and download the Java Cryptography Extension Unlimited
Strength Jurisdiction Policy Files 6 from the Additional Resources section.
Next, go to the <BASEDIR>/smarts/jre/lib/security directory, and then backup the

existing policy files in this path.
Next, extract the local_policy.jar and US_export_policy.jar files from the downloaded
zip file.
Next, overwrite the local_policy.jar and US_export_policy.jar files in the

<BASEDIR>smarts/jre/lib/security directory.
Next, set the value for the environment variable, SM_FIPS140 to TRUE in the runcmd_env.sh
file. This file is located in the <BASEDIR>/smarts/local/conf directory.
FIPS will be enabled when you start up the service.
This module covered the pre-startup configuration steps for EISM. Including configuring the
SNMP trap Exploder, specifying one or more IP domains in the EISM configuration file, and
enabling FIPS support.
This module focuses on EMC Smarts services. Starting and stopping the services is
explained, as well as how to check their status and modify the services if needed. Verification
of FIPS status is also shown.
During installation, EMC Smarts software is set up to start up automatically when the host is
powered on. This is achieved by setting up the EMC Smarts domain managers as software
services.
On the Microsoft Windows platform the processes are set up as Windows Services.
Administration of these services is done through the Services control panel available in the
Administrative Tasks menu or in the Windows Control Panel.
In Unix, a script, ic-serviced, is copied to the appropriate startup directory and is used to
ensure correct startup of installed EMC Smarts services.
The sm_serviced daemon is started by the ic_service script and manages the order and
startup parameters required to start desired services at system startup. Services are
registered with sm_service and can be reconfigured in many ways.
The sm_service utility is used to add, modify, delete, start and stop the services registers
with the sm_serviced daemon. Sm_service --help provides the syntax and full list of options
for this command.
On the Linux platform, use the sm_service show command to list installed services, their
current state, and a description.
Please note that If the sm_service show command is executed in Windows, it does not
return the state of the installed Services. To check service status on windows, use the
Windows Services control panel.
Once the installed services are identified, the sm_service start command can be used to start
any service that is not running. Remember, the broker process must be started first to
ensure proper server startup.
If the EMC Smarts application components are installed as Services within the Windows
environment, they may be accessed via the Services Manager window. The Services
Manager window is launched by opening the Windows Control Panel. From here, the
Administrator has the ability to verify the operational status of each service, start or stop
any of the available EMC Smarts service applications, or modify the startup options of any of
the EMC Smarts service applications. To modify any of the Service settings, right-click the
appropriate service to access the configuration screens.
The sm_service install command has several options.

The --name option is used to give the service a label, that will be used to refer to that
service. All server names MUST be unique within the EMC Smarts environment.
.
The --description value is entered at installation so that an informative description can be

provided when using the show command. If the description contains spaces, enclose the
argument in quotes.
The startmode option determines the expected behavior for the designated server.
A value of runonce indicates that the service will be started as part of the operating
system startup.
Automatic causes the service to start automatically at startup, and restart when
necessary.
Manual mode requires the service to be manually started with sm_service start command.
Disable mode indicates that startup via sm_service command.
Next, specify the fully qualified path to executable that the service must start. If EISM is
installed on the Microsoft Windows platform, remember to Include the drive letter and
include the EXE extension.
Finally, the options for the designated executable may be provided. They should be enclosed
inside double quotes, especially strings that may contain embedded spaces.
The sm_service show cmdline command prints the values that would be used to register
and the specified EMC Smarts service. Though the output looks complex, it is actually two
commands concatenated; the sm_service install command with an embedded sm_server
command. The sm_server command is explained in subsequent slides. This output can be
useful in modifying service configuration, or adding additional services.
Changes that are commonly made to an EMC Smarts service are The Service Name, Service
Description, Domain Name and TCP port.
In this example, the EISM service is stopped, and the Command Line used to register it
shown. The Administrator has copied and pasted this command, and made the necessary
changes. Once the new Service is registered, the old one is removed and the new Service is
started
This module covered the all aspects of EMC Smarts Services including starting stopping and
reconfiguring them.
This module focuses on the completion of adding EISM to the EMC Smarts solution, namely
configuring Service Assurance Manager to connect to the EISM domain manager, and
verifying the solution configuration.
Ionix Server Manager Install and Config/Overview
Before installing EISM, both EMC Smarts IP Manager and EMC Smarts Service Assurance
Manager were installed and configured.
After the EISM software was installed, pre-startup configuration was performed. It specified
the names of one or more IP domain Managers to which the EISM Domain Manager will
connect.
In this lesson, SAM will be configured to connect to the EISM domain manager, and
connectivity between the components will be verified.
If the name of the EISM domain was not changed, and version 9.0 or greater of Service
Assurance Manager is being used, the SAM-to-EISM connection is easily configured in a few
steps.
First, in the Global Manager Administration Console, find the INCHARGE-ESM domain under
the ICS Configuration/Domains category.
Next, check the Enabled Check box and select the Apply button to save the change.
Finally, to activate the SAM-to-EISM connection, select the Configure button.
To add EISM Domain Manager with a non-default name, a Domain instance must be created.
From the Global Manager Administration Console, choose Edit > New Domain... or click the
Launch Domain Wizard toolbar Button to display the Domain Creation Wizard.
Type the name of the Domain and choose whether to create a new Domain or to copy an
existing one. If you choose to copy an existing type, the remaining configuration options will
be identical to the Domain that was copied. The name of a Domain Type is case-sensitive and
must be unique.
To continue, choose the Next button.
The Tag String parameter is described in the Tagging Topology Elements section of the EMC
Smarts Service Assurance Manager Administration course. Tagging will not be used in this
example.
To continue, choose the Next button.
Domain groups are used by EMC Smarts MPLS Manager. They are described in detail in the
EMC Smarts MPLS Manager Training Course.
Since EISM does not use Domain Groups, choose the Next button to continue.
Choose the Finish button to create the new Domain Type.

Changes will not take effect until the SAM Global Manager is reconfigured. Use the Launch
Server Reconfiguration button, or use the Reconfigure Server option on the Configure
menu.
To verify the EISM-to-IP connection, open the Domain Manager Administration Console.
Locate the IP Domain or Domains that had been specified in the ESM.conf file, under the
InChargeDomain class in the topology browser.
The State attribute of each domain should have a value of CONNECTED. If this is not the
case, check the ESM.conf file and verify the domains are set up correctly. Remember, Domain
names are case-sensitive. Additional troubleshooting information can be found in the log
files of the IP and EISM domain managers.
Once reconfiguration of the SAM global manager is complete, SAM will try to connect to the
EISM domain manager. If the connection is unsuccessful, a Session Disconnected is
generated. If this occurs, verify the EISM domain is set up correctly in the Global Manager
Administration Console. Additional troubleshooting information can be found in the log files
of the SAM and EISM managers.
To verify FIPS status, use the command dmctl s <server-name> get SM_System::SMSystem::FIPS
The value returned will be TRUE if FIPS is enabled.
In this case, when the server name is set to INCHARGE-ESM, the EISM manager, errors are
indicated. Using brcontrol show INCHARGE-ESM is in a dead state and checking the log file
for the domain manager tells us that the server was unable to register with the Broker. This
failure is caused when the Broker is FIPS enabled and the server that is attempting to register
is not FIPS enabled.
Note: Errors will occur when other non-FIPS enabled managers attempt to register with the
Broker. Inter-domain and FIPS 140 broker communication happens only when the Broker, IP
server, SAM server, and the SAM Console are all in FIPS 140 mode, else the application will
not be operational.
This module covered the completion of the EISM installation. The SAM-to-EISM was
configured, and the complete installation was verified.
This course covered the installation of EMC Smarts Server Manager, and its integration into
an EMC Smarts Service Assurance Manager solution.
This concludes the training.

EMC Smarts Server Manager Installation and Implementation

Caricato da

Informazioni sul documento

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

EMC Smarts Server Manager Installation and Implementation

Caricato da

Copyright:

Formati disponibili

Welcome to EMC Smarts Server Manager Installation & Implementation.

Copyright 2012 EMC Corporation. Do not copy - All Rights Reserved.

EMC Smarts Server Manager Installation & Implementation

Copyright 2012 EMC Corporation. Do not copy - All Rights Reserved.

EMC Smarts Server Manager Installation & Implementation

Copyright 2012 EMC Corporation. Do not copy - All Rights Reserved.

EMC Smarts Server Manager Installation & Implementation

Copyright 2012 EMC Corporation. Do not copy - All Rights Reserved.

EMC Smarts Server Manager Installation & Implementation

Copyright 2012 EMC Corporation. Do not copy - All Rights Reserved.

EMC Smarts Server Manager Installation & Implementation

Copyright 2012 EMC Corporation. Do not copy - All Rights Reserved.

EMC Smarts Server Manager Installation & Implementation

Copyright 2012 EMC Corporation. Do not copy - All Rights Reserved.

EMC Smarts Server Manager Installation & Implementation

Copyright 2012 EMC Corporation. Do not copy - All Rights Reserved.

EMC Smarts Server Manager Installation & Implementation

There are five steps in installation of EMC Smarts Server Manager.

Copyright 2012 EMC Corporation. Do not copy - All Rights Reserved.

EMC Smarts Server Manager Installation & Implementation

Copyright 2012 EMC Corporation. Do not copy - All Rights Reserved.

EMC Smarts Server Manager Installation & Implementation 10

Copyright 2012 EMC Corporation. Do not copy - All Rights Reserved.

EMC Smarts Server Manager Installation & Implementation 11

Copyright 2012 EMC Corporation. Do not copy - All Rights Reserved.

EMC Smarts Server Manager Installation & Implementation 12

Copyright 2012 EMC Corporation. Do not copy - All Rights Reserved.

EMC Smarts Server Manager Installation & Implementation 13

Copyright 2012 EMC Corporation. Do not copy - All Rights Reserved.

EMC Smarts Server Manager Installation & Implementation 14

Copyright 2012 EMC Corporation. Do not copy - All Rights Reserved.

EMC Smarts Server Manager Installation & Implementation 15

Copyright 2012 EMC Corporation. Do not copy - All Rights Reserved.

EMC Smarts Server Manager Installation & Implementation 16

Copyright 2012 EMC Corporation. Do not copy - All Rights Reserved.

EMC Smarts Server Manager Installation & Implementation 17

Copyright 2012 EMC Corporation. Do not copy - All Rights Reserved.

EMC Smarts Server Manager Installation & Implementation 18

Copyright 2012 EMC Corporation. Do not copy - All Rights Reserved.

EMC Smarts Server Manager Installation & Implementation 19

Copyright 2012 EMC Corporation. Do not copy - All Rights Reserved.

EMC Smarts Server Manager Installation & Implementation 20

The next screen can be monitored to ensure that installation is progressing.

Copyright 2012 EMC Corporation. Do not copy - All Rights Reserved.

EMC Smarts Server Manager Installation & Implementation 21

Upon completion, the Installation Summary displays informational messages such as

Copyright 2012 EMC Corporation. Do not copy - All Rights Reserved.

EMC Smarts Server Manager Installation & Implementation 22

Copyright 2012 EMC Corporation. Do not copy - All Rights Reserved.

EMC Smarts Server Manager Installation & Implementation 23

Copyright 2012 EMC Corporation. Do not copy - All Rights Reserved.

EMC Smarts Server Manager Installation & Implementation 24

Copyright 2012 EMC Corporation. Do not copy - All Rights Reserved.

EMC Smarts Server Manager Installation & Implementation 25

Copyright 2012 EMC Corporation. Do not copy - All Rights Reserved.

EMC Smarts Server Manager Installation & Implementation 26

Copyright 2012 EMC Corporation. Do not copy - All Rights Reserved.

EMC Smarts Server Manager Installation & Implementation 27

Copyright 2012 EMC Corporation. Do not copy - All Rights Reserved.

EMC Smarts Server Manager Installation & Implementation 28

Server Manager must be configured it to communicate with one or more IP domain

Copyright 2012 EMC Corporation. Do not copy - All Rights Reserved.

EMC Smarts Server Manager Installation & Implementation 29

Copyright 2012 EMC Corporation. Do not copy - All Rights Reserved.