1. technology and computing

How to install and verify EMC
Solutions Enabler in a Symantec
i3 context
Technical Note
How to install and verify EMC Solutions Enabler in a
Symantec i3 context
Copyright © 2007 Symantec Corporation. All rights reserved.
Symantec, the Symantec Logo, Symantec i3, Symantec Indepth, Symantec Inform, and
Symantec Insight are trademarks or registered trademarks of Symantec Corporation or its
affiliates in the U.S. and other countries. Microsoft, Microsoft Windows, and Microsoft
Excel are registered trademarks of Microsoft Corporation. Other names may be
trademarks of their respective owners.
The product described in this document is distributed under licenses restricting its use,
copying, distribution, and decompilation/reverse engineering. No part of this document
may be reproduced in any form by any means without prior written authorization of
Symantec Corporation and its licensors, if any.
THIS DOCUMENTATION IS PROVIDED “AS IS” AND ALL EXPRESS OR IMPLIED
CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED
WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH
DISCLAIMERS ARE HELD TO BE LEGALLY INVALID, SYMANTEC CORPORATION SHALL
NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION
WITH THE FURNISHING PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE
INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE
WITHOUT NOTICE.
The Licensed Software and Documentation are deemed to be “commercial computer
software” and “commercial computer software documentation” as defined in FAR
Sections 12.212 and DFARS Section 227.7202.
Symantec Corporation
20330 Stevens Creek Blvd.
Cupertino, CA 95014
www.symantec.com
Technical support
For technical assistance, http://www.symantec.com/enterprise/support/
index.jsp and select phone or email support. Use the Knowledge Base search
feature to access resources such as TechNotes, product alerts, software
downloads, hardware compatibility lists, and our customer email notification
service.
Contents
Chapter 1
Solutions Enabler
About this technical note ...................................................................................... 5
About obtaining the Solutions Enabler .............................................................. 5
Installing the Solutions Enabler .......................................................................... 6
Installation of the Solutions Enabler 5.3 ........................................................... 9
Verifying the Solutions Enabler ........................................................................11
Chapter 2
EMC on Symantec i3
Gatekeeper devices ..............................................................................................15
Checking if Statistics Logging is enabled for CLARiiON ...............................16
Chapter 3
Troubleshooting
Common troubleshooting tips ...........................................................................19
4 Contents
Chapter
1
Solutions Enabler
This chapter includes the following topics:
■
About this technical note
■
About obtaining the Solutions Enabler
■
Installing the Solutions Enabler
■
Installation of the Solutions Enabler 5.3
■
Verifying the Solutions Enabler
About this technical note
This technical note describes how to install and verify the installation of the
EMC Solutions Enabler. It also contains a section describing Gatekeeper devices
and enabling Statistics Logging for CLARiiON. These topics are sources for
frequent support questions.
About obtaining the Solutions Enabler
The EMC Solutions Enabler can be obtained from either EMC or from Symantec,
as Symantec is licensed to ship EMC Solutions Enabler with Indepth for Oracle
(bundled with Storage Extension for EMC) and Indepth for SQL Server (bundled
with Storage Extension for EMC). The version Symantec currently ships is v6.0.
The EMC source for the Solutions Enabler is the EMC extranet site - PowerLink.
https://powerlink.emc.com/nsepn/webapps/btg548664833igtcuup4826/km/
appmanager/km/
secureDesktop?_nfpb=true&_pageLabel=servicesDownloadsTemplatePg&inter
nalId=0b01406680020355&_irrt=true
6 Solutions Enabler
Installing the Solutions Enabler
Note: You will need an account (login and password) to access this site, which is
provided by EMC.
Installing the Solutions Enabler
Note: Storage Extension for EMC requires the 32-bit version of the Solutions
Enabler, regardless of whether the Oracle instance(s) being monitored are 32- or
64-bit. On Windows, whether the database is Oracle or SQL Server, you need to
use the 32- bit version as well.
To install the Solutions Enabler on a UNIX server
Note: Use user root for the whole procedure.
1
Install the 32-bit version from the Solutions Enabler CD. On UNIX servers
the install package consists of 2 files:
emc_install.csh
symclinm.tar.Z (nm denotes the revision level, for example 54).
2
To install, make the emc_install.csh file executable and run it. It will
use the tar.Z file, installs the product, and prompts you appropriately
when needed.
The components that need to be installed for versions 5.x and 6.x during a
UNIX installation are shown in the following list.
Note: For version 5.x, default values apply for the entire installation, but for
version 6.x, you must specify 'y' for 'Install Single-threaded Symapi Shared
Libraries'.
Solutions Enabler 5.x
■
Install All EMC Solutions Enabler Shared Libraries and Run Time
Environment ? [Y]
■
Install EMC Solutions Enabler 64-bit Shared Libraries ? [N]
■
Install Shared Libraries That Will ONLY Allow Monitoring Capability?
[N]
■
Install Symmetrix Command Line Interface (SYMCLI) ? [Y]
■
Install EMC Solutions Enabler SRM Database Run Time Components ?
[N]
Solutions Enabler
Installing the Solutions Enabler
■
Install SMI Provider and cimserver? [N]
Install Option to Enable JNI Interface for EMC Solutions Enabler APIs ?
[N]
Solutions Enabler 6.x.
■
■
Install All EMC Solutions Enabler Shared Libraries and Run Time
Environment ? [Y]
■
Install EMC Solutions Enabler 64-bit Shared Libraries ? [N]
■
Install Single-threaded Symapi Shared Libraries ? [N]: y
■
Install Shared Libraries That Will ONLY Allow Monitoring Capability?
[N]
■
Install Symmetrix Command Line Interface (SYMCLI) ? [Y]
■
Install EMC Solutions Enabler SRM Database Run Time Components ?
[N]
■
Install SMI Provider and cimserver? [N]
■
Install Option to Enable JNI Interface for EMC Solutions Enabler APIs ?
[N]
3
Run the following command to apply the BASE and SOLUTIONS_4 keys:
/usr/symcli/bin/symlmf
The key values are:
License Key: 7FBE-9150-E0BC-9CCD SYMAPI Feature: BASE
License Key: C0C9-80AF-366B-A846 SYMAPI Feature:
SOLUTION_4
4
If CLARiiON works with the Solutions Enabler version 5.4 or later on UNIX
platforms after Indepth for Oracle is installed, run the following command
to build the /var/symapi/db/symapi_db.bin file:
/usr/symcli/bin/symcfg discover -clariion.
See “Installation of the Solutions Enabler 5.3” on page 9.
5
If you are using Symmetrix, run the following command to build the /var/
symapi/db/symapi_db.bin file:
/usr/symcli/bin/symcfg discover
6
To validate that the file mapping to the EMC array/device is working, run the
following command:
/usr/symcli/bin/symrslv file <full path name of any file
residing on Symmetrix>
Make sure the file size is greater than 0 bytes.
7
8 Solutions Enabler
Installing the Solutions Enabler
If it is, you will see values for Array and Dev fields (Solutions Enabler 5.x
and later) - for example: 00993 and 00A - in the output of the symrslv
command. If the mapping fails, you will see 'N/A' displayed for these field.
Table 1-1 is a sample snippet of the symrslv output for version 5.x or later:
Table 1-1
symrslv output for version 5.x or later
Size
Array
Dev
Offset
PPdevName
Offset
184k
00217
00D0
1460m
/dev/rdsk/c24t2d4
5839m
1m
00217
00CD
1460m
/dev/rdsk/c24t2d4
5839m
1m
00217
00CE
1460m
/dev/rdsk/c24t2d4
5840m
1m
00217
00CF
1460m
/dev/rdsk/c24t2d4
5841m
1m
00217
00D0
1460m
/dev/rdsk/c24t2d4
5842m
7
As UNIX user ‘i3’, check permissions of Solutions Enabler directories and
files, as detailed at the end of Verifying the Solutions Enabler section in this
document.
To install the Solutions Enabler on a Windows server
1
Install the 32-bit software from the Solutions Enabler CD.
2
In the Select EMC Solutions Enabler Library options dialog box, select the
following check boxes:
3
■
Base Storage Libraries
■
Control Storage Libraries
■
Base SRM Libraries
In the Select EMC Solutions Enabler Runtime installation options dialog
box, select the following check box:
■
4
In the Install Shared Libraries That Will ONLY Allow Monitoring Capability
dialog box, select:
■
5
Install Symmetrix Command Line Interface (SYMCLI)
No
To apply the BASE and SOLUTIONS_4 keys, run the following command via
the DOS command prompt:
c:\program files\emc\symcli\bin\symlmf
Note: For version 5.1 or later enter the key values as prompted.
Solutions Enabler
Installation of the Solutions Enabler 5.3
The key values are:
License Key: 7FBE-9150-E0BC-9CCD SYMAPI Feature: BASE
License Key: C0C9-80AF-366B-A846 SYMAPI Feature:
SOLUTION_4
6
If CLARiiON works with Solutions Enabler version 5.4 or later on Windows
platforms, run the following command via the DOS command prompt to
build the c:\program files\emc\symapi\db\symapi_db.bin file:
\program files\emc\symcli\bin\symcfg discover -clariion
7
If you are using Symmetrix, run the following command via the DOS
command prompt to build the c:\program
files\emc\symapi\db\symapi_db.bin file:
\program files\emc\symcli\bin\symcfg discover
8
To verify that the mapping is successfully working, run the following
command via the DOS command prompt:
c:\emc\symcli\bin\symrslv file <full path name of a file
residing on Symmetrix or CLARiiON>
Make sure that the file size is greater than 0 bytes.
If it is, you will see values for the ARRAY and DEVICE fields - for example:
00993 and 00A - in the output of the symrslv command. For a sample
output, see Table 1-1 in the UNIX section above.
Installation of the Solutions Enabler 5.3
If CLARiiON works with Solutions Enabler 5.3.x on UNIX platforms after
Indepth for Oracle is installed
Note: Use user root for the whole procedure.
1
Set the appropriate Library Path environment variable to point to where
Solutions Enabler shared libraries are installed - typically /usr/symcli/
shlib for your specific UNIX platform per the following table:
Table 1-2
Environment variable name per UNIX platform
UNIX platform
Environmental variable name
Sun-Solaris, Alpha-OSF1, Sequent-Dynix
LD_LIBRARY_PATH
AIX
LIBPATH
HP
SHLIB_PATH
9
10 Solutions Enabler
Installation of the Solutions Enabler 5.3
2
Run the following command:
<i3_root>/products/oracle/bin/pss_discover_clarions
<symapi.db name>
The following is an example of the output:
Using SYMAPI database file: /var/symapi/db/symapi_db.bin
Compiled with Symapi version 0x50301E7(V5.3-487); Library
Version:0x5040214(V5.4-532)
Build date: Mar 14 2004 13:48:41
VENDOR_ID=Veritas VENDOR_APPLICATION_ID=StorageExtension
VENDOR_APPLICATION_KEY=
2FCB-379D-C93E-3C56
Calling SymInit()
Calling SymPrefsSet()
Calling SymDiscover()
Listing Clariion Units:
Found Clariion Unit APM00042500384
Listing Symmetrix Units:
Exiting
If CLARiiON works with Solutions Enabler version 5.3.x on Windows
platforms after Indepth for Oracle or Indepth for SQL Server is installed
1
Use the DOS command prompt and:
a
Change directory to the root directory of Indepth for SQL Server or
Indepth for Oracle on the Windows server.
b
Run to following command:
■
For Oracle
products\oracle\bin\pss_discover_clariions.exe
<symapi.db name>
■
For SQL Server
products\sql-server\bin\pss_discover_clariions.exe
<symapi.db name>
Note: You must specify the full path name of the symapi_db.bin file
on the Windows server. Typically the full path name is c:\program
files\emc\symapi\db\symapi_db.bin. This file name will need
to be enclosed in "" since there is white space in 'program files'.
Note: This file may not yet exist.
Solutions Enabler
Verifying the Solutions Enabler
See also the sample output of this command shown in the previous
UNIX section.
c
The symapi_db.bin file is now updated with the CLARiiON device
information.
d
Verify that the symapi_db.bin file has been modified.
Note: The above procedure needs to be applied to each server that is connected
to the CLARiiON array and runs an Indepth for SQL Server or Indepth for Oracle
Collector agent.
Verifying the Solutions Enabler
To determine if Solutions Enabler is already installed and what version it is,
perform the following step:
■
UNIX
run /usr/symcli/bin/symcli
■
Windows
run c:\program files\emc\symcli\bin\symcli
This command will return output like:
Symmetrix Command Line Interface (SYMCLI) Version V5.4.2.0
(Edit Level: 541)
built with SYMAPI Version V5.4.2.0 (Edit Level: 541)
In this particular case we see that we are running v5.4.2.0.
The BASE and SOLUTIONS_4 keys must be applied so that the basic
functionality and SymAPI mapping calls of Solutions Enabler will work.
To check to see if these keys have already been applied
1
Examine the contents of the symapi_licenses.dat file:
■
UNIX
cat /var/symapi/config/symapi_licenses.dat
Windows
type c:\program
files\emc\symapi\config\symapi_licenses.dat
It should contain, at the minimum, the following 2 lines:
License Key: 7FBE-9150-E0BC-9CCD SYMAPI Feature: BASE
License Key: C0C9-80AF-366B-A846 SYMAPI Feature:
SOLUTION_4
■
11
12 Solutions Enabler
Verifying the Solutions Enabler
If either of these keys are missing, they must be applied with user root, via the
symlmf command as documented in the previous section.
For UNIX we need to check that permissions are such that the UNIX user i3 can
access certain directories/files of the Solutions Enabler.
To check the access permissions for UNIX
1
Log in with user i3.
2
Make sure that you can perform the following:
$ cd /usr/symcli/shlib
$ ls -l libsymapi.so libsymlvm.so
-r-xr-xr-x
1 root
other
775084 Jul
libsymapi.so
-r-xr-xr-x
1 root
other
72728 Jul
libsymlvm.so
6 05:18
6 05:18
Note: These two files must be readable by the 'world'.
Note: The above is an example taken from a Sun Solaris server. If the server
is HP-UX, then the library file suffix will be '.sl', and if IBM AIX, the library
file suffix will be '.a'.
$ cd /var/symapi/db
$ ls -l
total 416
-rw-r--r-1 root
symapi_db.bin
other
200000 Jul
6 05:20
Note: This file must be readable by the 'world'.
$ cd /var/symapi/config
$ ls -l symapi_licenses.dat
-rw-r--r-1 root
other
symapi_licenses.dat
140 Jul
6 05:19
Note: This file must be readable by the 'world'.
If you cannot access any of these directories and/or any of these files are
not readable by the 'world', then permissions on these directories/files will
have to be changed by user root. The change is to make them accessible to
user i3.
Solutions Enabler
Verifying the Solutions Enabler
If any of the these files are missing, then you will need to contact the
Storage administrator to 'finish' or 'redo' the installation of the EMC
Solutions Enabler.
If the Solutions Enabler is installed, proceed to validate this document as
described in the previous section. If the Solutions Installer is not installed,
proceed to install the Solutions Installer as described in the previous
section.
13
14 Solutions Enabler
Verifying the Solutions Enabler
Chapter
2
EMC on Symantec i3
This chapter includes the following topics:
■
Gatekeeper devices
■
Checking if Statistics Logging is enabled for CLARiiON
Gatekeeper devices
When you have the EMC Solutions Enabler version 5.3 or later, you need to have
a special device, known as a Gatekeeper, visible to the server to communicate
with the EMC Symmetrix storage array. This device is not needed to provide the
basic mapping functionality as described before, but is needed for the Indepth
for Oracle or Indepth for SQL Server Storage agent to be able to run and gather
storage array metrics from the Symmetrix on a periodic basis.
To determine if one or more Gatekeeper devices exists on the server
1
Run the following command:
■
UNIX (as user root)
/usr/symcli/bin/syminq
■
Windows
C:\program files\emc\symcli\bin\syminq
16 EMC on Symantec i3
Checking if Statistics Logging is enabled for CLARiiON
Table 2-1 shows a sample output after running the syminq command.
Table 2-1
syminq output example
Device
Name
Product
Type
Device
Vendor
ID
Rev
Ser Num
Cap (KB)
/dev/rdsk/c0t4d0
SEAGATE
ST118273WC
HP05
LP547430
17783240
/dev/rdsk/c0t5d0
SEAGATE
ST15150W
HP09
01625770
4194157
/dev/rdsk/c0t6d0
SEAGATE
ST15150W
HP12
02994239
4194157
/dev/rdsk/c1t0d0
EMC
SYMMETRIX
5265
93052361
4224000
/dev/rdsk/c1t1d0
EMC
SYMMETRIX
5265
93052461
4224000
/dev/rdsk/c1t2d0
EMC
SYMMETRIX
5265
93052561
4224000
/dev/rdsk/c1t3d0
EMC
SYMMETRIX
5265
93052661
4224000
/dev/rdsk/c1t4d0
EMC
SYMMETRIX
5265
93052761
4224000
/dev/rdsk/c1t5d0
EMC
SYMMETRIX
5265
93052861
4224000
/dev/rdsk/c1t8d0
EMC
SYMMETRIX
5265
93052961
4224000
/dev/rdsk/c1t9d0
GK
EMC
SYMMETRIX
5265
93050161
2880
/dev/rdsk/c1t10d0
GK
EMC
SYMMETRIX
5265
93051161
2880
/dev/rdsk/c1t11d0
GK
EMC
SYMMETRIX
5265
93052161
2880
/dev/rdsk/c1t12d0
GK
EMC
SYMMETRIX
5265
93053161
2880
Note: Under the Type column several devices are named 'GK'. This indicates
that we have GK devices on this server. If there are no GK devices listed, you will
not be able to start the Storage agent. You must have at least one GK device
added to the server. This is typically taken care of by the 'Storage
Administrator'.
Checking if Statistics Logging is enabled for
CLARiiON
If CLARiiON is the attached storage media, the storage agent of Indepth for
Oracle or Indepth for SQL Server needs to be able to run and gather storage
array metrics from the Clariion on a periodic basis, and therefore Statistics
Logging must be enabled via the Clariion software Navisphere.
EMC on Symantec i3
Checking if Statistics Logging is enabled for CLARiiON
To enable Statistics Logging in Clariion
1
Open Navisphere.
Note: Typically this will require a user with Storage Administrator rights and
the URL of the Navisphere software.
2
Right-click on the APM storage System and select Properties.
3
On the General tab, select Statistics Logging.
4
Click Apply.
5
Click OK.
6
Click File>Save and Exit.
17
18 EMC on Symantec i3
Checking if Statistics Logging is enabled for CLARiiON
Chapter
3
Troubleshooting
This chapter includes the following topics:
■
Common troubleshooting tips
Common troubleshooting tips
If the mapping step fails (running of symrslv), then the most probable cause is
that the symapi_db.bin file is not up-to-date or has old data in it. Building a
brand new symapi_db.bin will, in most cases, fix the problem.
To safely build a new symapi_db.bin for UNIX
Note: Log in with user root.
Note: All commands referenced below reside in /usr/symcli/bin.
1
$ cd /usr/symcli/bin
2
Determine if any device groups have been defined by running:
$ symdg list
3
If there are no device groups defined, perform steps 5 and 6.
4
If there are device groups define, then run for each device group:
$ symdg export <dgname> -f <filename>
Note: In step 2 the command symdg list shows the dgname value.
5
Make a backup of the file by running:
$ cd /var/symapi/db; mv symapi_db.bin symapi_db.bin.old
20 Troubleshooting
Common troubleshooting tips
6
Run:
$ cd /usr/symcli/bin; symcfg discover
7
For each device group, run:
$ symdg import <dgname> -f <filename>
To safely build a new symapi_db.bin for Windows
Note: All commands referenced below reside in C:\program
files\emc\symcli\bin
1
cd C:\program files\emc\symcli\bin
2
Determine if any device groups have been defined by running:
symdg list
3
If there are no device groups defined, perform steps 5 until 9.
4
If there are device groups, then run for each device group:
symdg export <dgname> -f <filename>
Note: In step 2 the command symdg list shows the dgname.
5
cd C:\program files\emc\symapi\db
6
Make a backup of the bin file:
copy symapi_db.bin symapi_db.bin.old
7
Ensure that a brand new bin file is built:
erase symapi_db.bin
8
cd C:\program files\emc\symcli\bin
9
Run:
symcfg discover
10 For each device group, run:
symdg import <dgname> -f <filename>