EMC IonixTM Storage Configuration Advisor · EMC Corporation Corporate Headquarters: Hopkinton, MA 01748-9103 1-508-435-1000 EMC® IonixTM Storage Configuration Advisor Version 2.0

EMC® IonixTM Storage Configuration AdvisorVersion 2.0

Administration GuideP/N 300-010-411

REV A01

EMC CorporationCorporate Headquarters:

Hopkinton, MA 01748-9103

1-508-435-1000www.EMC.com

Copyright © 2010 EMC Corporation. All rights reserved.

Published March 2010

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

For the most up-to-date regulatory document for your product line, go to the Technical Documentation and Advisories section on EMC Powerlink.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.

All other trademarks used herein are the property of their respective owners.

EMC Ionix Storage Configuration Advisor Version 2.0 Administration Guide2

Contents

Preface....................................................................................................................... 11

Chapter 1 Initial Setup Administration overview ...................................................................................... 16 Access and login to the console ............................................................................ 17 Create a new Security Administrator account.................................................... 19

Chapter 2 User Management Overview.................................................................................................................. 22 Manage users........................................................................................................... 23 Manage roles............................................................................................................ 24

Assign role ......................................................................................................... 24Edit users ........................................................................................................... 25

Manage Authentication ......................................................................................... 26 Change Lockbox password ................................................................................... 27

Chapter 3 System Administration System Notifications............................................................................................... 30

Chapter 4 Manage User-defined Groups User-defined groups............................................................................................... 32

System groups................................................................................................... 32Static user-defined groups............................................................................... 32Dynamic user-defined groups ........................................................................ 32Subgroups.......................................................................................................... 32User-Defined Groups view ............................................................................. 32

Chapter 5 Discovery Overview.................................................................................................................. 34 Manage access profiles........................................................................................... 35

Profile types....................................................................................................... 36 Manage initial discovery policies ......................................................................... 37

Creating initial discovery policies.................................................................. 37Discovery policy execution results ................................................................ 37Discovery view ................................................................................................. 38

Manage rediscovery policies................................................................................. 39

EMC Ionix Storage Configuration Advisor Version 2.0 Administration Guide 3

Contents

Configure host resolution ...................................................................................... 40 Configure non-discovered objects ........................................................................ 42 Manage object inventory........................................................................................ 43 Manage Discovery Managers status..................................................................... 44

Chapter 6 Database Administration Database Administration overview...................................................................... 46 Back-up repositories ............................................................................................... 47

Manually back-up discovered objects, Sybase and Lockbox repositories 47 Restore repositories................................................................................................. 49

Restore only Sybase repository ....................................................................... 49Restore all repositories ..................................................................................... 49

Retention policy....................................................................................................... 51

Chapter 7 Install Providers Overview .................................................................................................................. 54 EMC SMI-S Provider for Symmetrix and CLARiiON ....................................... 55

Windows installation........................................................................................ 55Linux installation .............................................................................................. 56

Adding CLARiiONs to the EMC SMI-S Provider for discovery...................... 58In-band CLARiiONs......................................................................................... 58Using the TestSMiProvider application to add Symmetrix and CLARiiON arrays to the EMC SMI-S Provider ................................................................. 58

Brocade SMI Agent ................................................................................................. 61Brocade SMI Agent for EOS (McDATA) ....................................................... 61

HiCommand for Hitachi arrays ............................................................................ 62

Appendix A Troubleshooting Overview .................................................................................................................. 64 General provider configuration issues................................................................. 65 Brocade and McDATA provider issues................................................................ 66

McDATA guides ............................................................................................... 66No elements detected with Brocade and McDATA CIMOMs ................... 66Brocade provider not sending events ............................................................ 66Brocade provider stops sending events......................................................... 67Brocade provider consuming memory and CPU......................................... 67Error message: Operation Not Supported..................................................... 67

SMI-S Provider for Symmetrix and CLARiiON ................................................. 68Provider versions .............................................................................................. 68Identifying SMI-S Provider version numbers............................................... 68Logging troubleshooting data......................................................................... 68Disabling statistical information gathering................................................... 68Solutions Enabler configuration error regarding RA Directors ................. 69Discovery errors related to timing out........................................................... 69VCMDB devices ................................................................................................ 71Starting the cimserver on Linux...................................................................... 71Database errors in the log ................................................................................ 71Connection failed message .............................................................................. 71Error opening gatekeeper device.................................................................... 72Array DM errors caused by EMC SMI Provider/Solutions Enabler related issues................................................................................................................... 72

HiCommand for HDS arrays................................................................................. 74HiCommand Device Manager does not support an automatic refresh of array


Contents

data ..................................................................................................................... 74 Troubleshooting Host discovery........................................................................... 75

Supported HBA, driver, and firmware versions ......................................... 75Discovering HBA path data ............................................................................ 75Failure to open WMI sessions......................................................................... 77Common reasons for discovery failure with Windows hosts.................... 77Improper credentials........................................................................................ 77Issues on UNIX hosts with sudo accounts.................................................... 78

General SMI issues ................................................................................................. 80Error message: HTTP Error (401 Unauthorized) ......................................... 80Error message: Cannot connect to <IP address>. Connection failed........ 80Error message: Unable to reach element....................................................... 81

Troubleshooting the gdpm DM ............................................................................ 82Guidelines for analyzing troubleshooting data ........................................... 82

Troubleshooting an offline array Domain Manager .......................................... 83 Using SNMP ............................................................................................................ 84

Cisco SNMP Rediscoveries not invoked on configuration changes ......... 84 Troubleshooting user interface conditions.......................................................... 85

Default value for the UDG refresh period .................................................... 85Discovery status permanently stays in running state ................................. 85Discovery status: One or more element discoveries failed ........................ 86Discovery status: No elements detected ....................................................... 86Out of memory errors: The user interface hangs, stalls, or slows down.. 86UI logs for troubleshooting ............................................................................. 87Unable to open UI Browser to the appliance................................................ 88Unable to see any data in the UI even after creating profiles and policies 88Progress bar for loading data hangs for a long time in any view ............. 88Unable to sort or filter by 'Last Successful' Time of Discovery in the Discovered Objects view ................................................................................. 89Object Details and Maps not showing the real-time environment ........... 89Paths shown in maps do not match the Path Details tab ........................... 89

Useful commands and utilities ............................................................................. 90Utilities ............................................................................................................... 90Commands ........................................................................................................ 90

Using discovery logs .............................................................................................. 92Sending logs and repository files to Customer Support............................. 93

Rediscovery scenarios for user-defined groups ................................................. 94 Re-imaging the appliance ...................................................................................... 95

Acquire network settings and log in.............................................................. 95Changing the time zone................................................................................... 98Linux-based time zones ................................................................................... 99


Contents


Title Page

Figures

1 Login screen ........................................................................................................................... 172 Administration screen .......................................................................................................... 193 System Notifications dialog box ......................................................................................... 304 Access Profiles view .............................................................................................................. 355 Back-up Repository dialog box ........................................................................................... 476 Historical data retention policy dialog box ....................................................................... 517 Interface window .................................................................................................................. 958 Network configuration window ......................................................................................... 969 Edit Interface eth0 pop-up ................................................................................................... 9710 Time zone selection ............................................................................................................... 97


Figures


Title Page

Tables

1 SCA role privileges ......................................................................................... 242 Host resolution parameters ........................................................................... 403 Useful utilities.................................................................................................. 904 Useful commands............................................................................................ 905 Domain Manager logs .................................................................................... 926 Logs and repository files for diagnosis ........................................................ 93


Tables


Preface

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

If a product does not function properly or does not function as described in this document, please contact your EMC representative.

Audience This document is part of the EMC Ionix Storage Configuration Advisor documentation set, and is intended for use by system administrators and analysts.

Relateddocumentation

Related documents include:

◆ EMC Ionix Storage Configuration Advisor 2.0 Administration Guide

◆ EMC Ionix Storage Configuration Advisor 2.0 Non-EMC Software

◆ EMC Ionix Storage Configuration Advisor 2.0 Hardware Replacement Guide

◆ EMC Ionix Storage Configuration Advisor 2.0 Product Security Defaults

◆ EMC Ionix Storage Configuration Advisor 2.0 Support Matrix

◆ EMC Ionix Storage Configuration Advisor 2.0 Online Help

◆ EMC Ionix Storage Configuration Advisor 2.0 Release Notes

◆ EMC Ionix Storage Configuration Advisor 2.0 Performance and Scalability Guidelines

◆ EMC Ionix Storage Configuration Advisor 2.0 Installation Quick Start

◆ EMC Ionix Storage Configuration Advisor 2.0 Installation Guide


Preface

Conventions used inthis document

EMC uses the following conventions for special notices.

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

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

IMPORTANT!An important notice contains information essential to operation of the software.

Typographical conventionsEMC uses the following type style conventions in this document:

Normal Used in running (nonprocedural) text for:• Names of interface elements (such as names of windows, dialog boxes, buttons,

fields, and menus)• Names of resources, attributes, pools, Boolean expressions, buttons, DQL

statements, keywords, clauses, environment variables, filenames, functions, utilities

• URLs, pathnames, filenames, directory names, computer names, links, groups, service keys, file systems, notifications

Bold Used in running (nonprocedural) text for:• Names of commands, daemons, options, programs, processes, services,

applications, utilities, kernels, notifications, system call, man pages

Used in procedures for:• Names of interface elements (such as names of windows, dialog boxes, buttons,

fields, and menus)• What user specifically selects, clicks, presses, or types

Italic Used in all text (including procedures) for:• Full titles of publications referenced in text• Emphasis (for example a new term)• Variables

Courier Used for:• System output, such as an error message or script • URLs, complete paths, filenames, prompts, and syntax when shown outside of

running text

Courier bold Used for:• Specific user input (such as commands)

Courier italic Used in procedures for:• Variables on command line• User input variables

< > Angle brackets enclose parameter or variable values supplied by the user

[ ] Square brackets enclose optional values

| Vertical bar indicates alternate selections - the bar means “or”

{ } Braces indicate content that you must specify (that is, x or y or z)

... Ellipses indicate nonessential information omitted from the example


Preface

Where to get help EMC support, product, and licensing information can be obtained as follows.

Product information — For documentation, release notes, software updates, or for information about EMC products, licensing, and service, go to the EMC Powerlink website (registration required) at:

http://Powerlink.EMC.com

Technical support — For technical support, go to EMC Customer Service on Powerlink. To open a service request through Powerlink, you must have a valid support agreement. Please contact your EMC sales representative for details about obtaining a valid support agreement or to answer any questions about your account.

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

[email protected]


http://powerlink.emc.com

Preface


1

This chapter describes the necessary steps for setting up and maintaining the Storage Configuration Advisor (SCA) environment. Topics include:

◆ Administration overview.............................................................................................. 16◆ Access and login to the console.................................................................................... 17◆ Create a new Security Administrator account ........................................................... 19

Initial Setup

Initial Setup 15

Initial Setup

Administration overviewAfter installation of SCA hardware and software initialization as described in the EMC Ionix Storage Configuration Advisor Installation Guide, you can begin to administer SCA for your environment.

IMPORTANT!The Admin user with Security Administrator privilege is the highest privilege in SCA. Only Security Administrator role allows you to manage users including user roles. An Admin user with Administrator role can manage all other tasks except for User Management.

SCA allows you, the Admin user, to set up and manage the following tasks:

◆ System notifications

◆ Discovery management including management of:

• Access Profiles

• Object inventory

• Initial discovery policies

• Rediscovery policies

• Host resolution parameters

• Non-discovered hosts

• Manager’s Status

◆ Database administration including administration of:

• Retention policies

• Back-up repository schedules

◆ User-defined group management—create static and dynamic user-defined groups

◆ User management—(Security Administrator role only), includes management of:

• User authentication

• Users—add, delete, modify users

• User roles—assign privileges

• Change Lockbox Passcode


Initial Setup

Access and login to the consoleThis section describes the necessary steps to access and log in to SCA.

SCA is provided with a default Admin with Security Administrator privileges for initial login. The Security Administrator is the only administrative role that can add and modify users, as well as perform normal administrative tasks. After logging in to the system, ensure that you create other users with administrative and nonadministrative roles as described in Chapter 2, “Manage roles” on page 24.

Initial loginTo access and log in to SCA:

1. Open Windows Internet Explorer (IE), or Firefox browser.

Note: Make sure your screen resolution is set to at least 1024 x 768.

For IE users, launch the browser from the Windows Desktop icon or Start>Programs menu each time you access an SCA console. Performance issues can occur when using either the File > New Window menu option, or the Ctrl + N shortcut key to launch a browser in which to run an SCA console.In addition, make sure you disable pop-up blockers.

2. Type the URL for the SCA appliance: https://<appliance IP address>/sca.

The EMC Ionix Storage Configuration Advisor login screen opens, as shown in Figure 1 on page 17.

Figure 1 Login screen

Access and login to the console 17

Initial Setup

3. Type the username and password of the default Security Administrator:

Username: admin

Password: 123456qw

4. Click Login to display the SCA Dashboard.

The website security certificate dialog box appears. Select Yes to continue.

Note: If you select Always trust content from this publisher, the security certificate does not appear for subsequent login.

CAUTION!After initial login, it is highly recommended that you log in to the Admin with Security Administrator role account, and change the default admin password to protect the security of your system. “Create a new Security Administrator account” on page 19 provides instructions.


Initial Setup

Create a new Security Administrator accountThe Admin user with Security Administrator role is the default user provided with SCA and cannot be edited, disabled, or deleted. However, the admin password can be changed to Admin user with a Security Administrator user role, thereby creating a Security Administrator account for that user.

To create a new Security Administrator account:

1. Log in to SCA with username: admin and password: 123456qw

2. From the SCA Dashboard, click the Administration tab to display the Administration menu functions, as shown in Figure 2 on page 19.

Figure 2 Administration screen

3. Click Manage Users.

4. Click Create Users in the Manage Users screen.

5. In the Create User dialog box, type:

• First Name: <First name of Security Administrator owner>

• Last Name: <Last name of Security Administrator owner>

• Email: <Security Administrator’s e-mail address>

• For User Role, select Security Administrator from the list box.

6. Type User Authentication information:

a. Select desired Authentication Method from the list box.

b. Type User Name.

c. Type the password and then retype the password.

Create a new Security Administrator account 19

Initial Setup

IMPORTANT!Ensure that you make a note of the username and password you provide here. After you type it, there is no other way to retrieve the information.

7. Click OK to create the user and return to the Manage Users screen.

8. Log out of SCA.

9. Ensure that you can:

a. Log in again with the new Security Administrator credentials.

If you cannot log in, use the default username admin and password 123456qw to log in.

b. Select the user in Administration > Manage Users page.

c. Click Edit and reset the password.

d. See the Administration options on the Administration screen, as shown in Figure 2 on page 19.

e. Select User Administration.

If you cannot see the Administration options or if the User Administration button is disabled, then you may not have selected the User Role and Permissions correctly. To fix the mistake:

a. Log out of the system.

b. Log in again as admin with password 123456qw.

c. Go to Manage Users.

d. Select the new administrator from the list and click Edit.

e. Select Security Administrator for User Role.

f. Select Create Policies and Security Administrator for Permissions.

g. Click OK to save the changes.

h. Repeat steps 5, 6, and 7.


2

This chapter discusses creating and managing users including assigning user roles, and managing user authentication. Topics include:

◆ Overview ......................................................................................................................... 22◆ Manage users .................................................................................................................. 23◆ Manage roles ................................................................................................................... 24◆ Manage Authentication................................................................................................. 26◆ Change Lockbox password........................................................................................... 27

User Management

User Management 21

User Management

OverviewEMC Ionix Storage Configuration Advisor allows the Security Administrator user to perform User Management functions.

User Management consists of managing Users, User Authentication, and User Roles. SCA provides a default User and User Role. Additional Users and User Roles can be created by the Security Administrator user and are managed from the SCA Console Administration tab.

This section provides an overview of the Manage User features. The SCA online help provides field descriptions and definitions for User Management features.

The default username is admin, and password is 123456qw. The admin user is assigned the Security Administrator role, and therefore has all necessary permissions for user management and administration. The admin user cannot be deleted or disabled.

CAUTION!It is highly recommended that you do not use the default secadmin account. It is best to create a new Security Administrator account and change the “secadmin” password to protect the security of your system. “Create a new Security Administrator account” on page 19 provides instructions.


User Management

Manage usersTo create additional users for the EMC Ionix Storage Configuration Advisor software:

1. Log in with Security Administrator permissions.

2. Click Administration to display the Administration tab.

3. Under User Management, click Manage Users.

4. In the Manage Users view, click Create User.

Complete the Create User dialog box to add a new user. The online help provides field information.

In addition, you can perform the following user assignments:

◆ Delete user — When you delete a user, all policies and rules the user created, which are assigned to the user, are automatically assigned to users in the Administrator role.

◆ Edit users — “Edit users” on page 25 provides more information on editing users.

◆ Enable and disable users.

◆ Manage user roles and permissions — “Manage roles” on page 24 provides more information on Managing user roles.

Manage users 23

User Management

Manage rolesAll users must be assigned to one user role. Only one role per user is supported. User roles are used to group users with similar permissions and functions. SCA provides four levels of users including:

◆ Security Administrator — A super user with administrator permissions who can manage users, user roles, user authentication, and view the audit log. (Similar to root in UNIX and Administrator in Windows.)

◆ Administrator — A super user with full administrator permissions to the entire application, with the exception of User Management.

◆ User — A regular user with full access to the entire application, but without administrator permissions or the ability to manage user-defined groups.

◆ Guest — A user with view-only permissions who cannot make modifications or perform administrator tasks.

The user role defines the possible permissions a user can have. User permissions can include all user role permissions, or a subset of the permissions, but a user cannot be granted more permissions than those available for a single user role. Table 1 on page 24 lists role privileges for each role.

To access Manage Roles view, select Manage roles from the User Management options in the Administration tab.

Assign role To assign a role to a user:

1. Log in with Security Administrator permissions.

2. Click Administration to display the Administration tab.

3. Under User Management, click Manage Users.

4. In the Manage Users view, if assigning a role to a new user, click Create User. If assigning a role to an existing user, select the user from the list and click Edit.

Table 1 SCA role privileges

Role privileges Role

Security Admin Administrator User Guest

User & Role Management

Yes No No No

Discovery Management Yes Yes No No

UDG Management Yes Yes Yes No

System Yes Yes No No

DB Administration Yes Yes No No

Policy Management Yes Yes Yes No

Configuration Changes Annotation

Yes Yes Yes No

Breach Management Yes Yes Yes No

View Only Operations Yes Yes Yes Yes


User Management

5. In the Create/Edit User dialog box, for Role, select the desired user role.

6. Click OK to assign the role to the user.

The SCA online help provides full field information and step-by-step procedures for assigning roles and permissions.

Edit users When creating a user, data is required for all fields. When editing user credentials, select Edit option from the menu.

This dialog box opens with the Password and Re-enter Password fields blank. These fields are not marked as required fields. If you type any characters in either of these fields, the system considers this action as a password change request. If a password change is not required, remove any characters previously typed in the password fields leaving the fields empty.

Proceed with editing any additional user changes, and then click OK to save the changes.

Manage roles 25

User Management

Manage AuthenticationThe Manage Authentication feature allows you, the Security Administrator to specify how users are authenticated when they log in. You can select either the Lightweight Directory Access Protocol (LDAP), or Local as options for types of authentication.

You set or edit user authentication options when either creating or editing a user.

Manage LDAP settingsTo manage LDAP settings for your application:

1. Select Manage Authentication from the User Management section of the Administrator tab to display the LDAP Authentication options.

2. Type the following information:

• Domain Name — Type the domain name of the LDAP server. For example, corp.yourcompany.com

• Server — Type the IP address, fully qualified name, or hostname of the LDAP server.

• LDAP Port — Type the port number of the LDAP server. The default is typically 389.

• Base Domain Name — Type the base domain name of the LDAP server. For example, dc=corp,dc=emc,dc=com.

• Patterns — Type the full domain controller information for parsing the formatted LDAP entries. For example, uid=jdoe; ou=it; dc=ldap; dc=corp; dc=yourcompany; dc=com.

The SCA online help provides full field information and step-by-step procedures for assigning and managing User Authentication.


User Management

Change Lockbox passwordAn additional responsibility for the SCA Admin—Security Administrator is to manage the Lockbox passcode.

The SCA Lockbox contains the passwords for all users defined as local, and used for local user. The Lockbox password can only be changed by the Security Administrator. This responsibility makes the Security Administrator responsible for company security policy with regard to server configuration. The Lockbox passcode is used for Lockbox administration such as resetting the Lockbox in case of relevant changes made to the server configuration.

The Lockbox verifies that the application trying to access it is running on the same machine. It does this by comparing various configurations of the machine on which the lockbox is running. As a result, an application running on the same machine as the lockbox does not need the passcode to manage users (Security Admin function).

Note: The lockbox is created by SCA during the first run (and verified in consecutive runs). It is not created during setup authentication.

To display the Lockbox password dialog box, select Change Lockbox Passcode from the User Management options in the Administration tab. The default lockbox password is: 1Passphrase!

IMPORTANT!It is the responsibility of the Security Administrator to change the Lockbox password to avoid security risks. Change the password the first time you access SCA after you assign the Security Administrator user role.

Change Lockbox password 27

User Management


3

This chapter discusses the following topic:

◆ System Notifications ...................................................................................................... 30

System Administration

System Administration 29

System Administration

System Notifications You can complete the System Notifications dialog box to set up user notification of policy breaches. You can notify users of breaches through email or SNMP traps or both.

To access the System Notifications dialog box, select System Notifications from the System Administration options in the Administration tab.

Figure 3 System Notifications dialog box

The SCA online help provides field descriptions and specific instructions for using this System Notification feature.


4


◆ User-defined groups ...................................................................................................... 32

Manage User-definedGroups

Manage User-defined Groups 31

Manage User-defined Groups

User-defined groups The user-defined group feature provides the ability to create groups. A group is a logical collection of managed objects such as hosts, arrays, switches, and fabrics. Logical grouping of managed objects allows you to perform operations on large sets of like or related managed objects. In addition to system groups, there are two types of user-defined groups: static and dynamic.

System groups System groups are groups automatically created by the system to contain all objects of a particular type. For example, All Hosts, All Arrays, All Switches, All Fabrics, All VMware ESX Hosts, All VMware vCenter Hosts, All VMware vClustered Hosts, and All VMware Virtual Hosts are system groups that contain all discovered objects of that type. The All Groups group is also a group created by the system as a container for all groups in the group tree. You cannot delete system groups and can only change the membership of a system group programmatically.

Static user-defined groups

A static user-defined group can contain managed objects (members) and other static and dynamic user-defined groups (subgroups). A static group changes only when you explicitly add or remove members and subgroups. An object can be a member of more than one static group. Static groups are intended for collections of managed objects that rarely change.

Dynamic user-defined groups

A dynamic group contains objects that meet user-defined criteria based on object attributes. At regular intervals (either the default interval of 60 minutes or some other user-specified interval), the system scans your Repository for discovered objects that meet the user-defined criteria and automatically adds and removes objects.

Subgroups Both static and dynamic groups can be subgroups of a static group. However, a group cannot be a subgroup of two parent groups. A subgroup can only have one parent.

User-Defined Groups view

The User-Defined Groups view provides information and options that allow you to manage static and dynamic user-defined groups. The panel on the left displays all system and user-defined groups in the system. When you select a group in the panel, all objects and subgroups in that group appear in the table on the right.

Additionally, Users can create and implement user-defined groups in policy creation. Only Admin users can access and manage user-defined groups from the Administration tab of the console.


5

This chapter discusses the following topics:

◆ Overview ......................................................................................................................... 34◆ Manage access profiles .................................................................................................. 35◆ Manage initial discovery policies ................................................................................ 37◆ Manage rediscovery policies ........................................................................................ 39◆ Configure host resolution ............................................................................................. 40◆ Configure non-discovered objects ............................................................................... 42◆ Manage object inventory............................................................................................... 43◆ Manage Discovery Managers status............................................................................ 44

Discovery

Discovery 33

Discovery

OverviewThe Discovery functions of EMC Ionix Storage Configuration Advisor include managing and creating:

◆ Access profiles

◆ Initial discovery policies

◆ Rediscovery policies

◆ Host resolution configuration

◆ Object inventory

This chapter provides an overview of SCA discovery. The SCA online help provides field descriptions and specific instructions for using these management features.


Discovery

Manage access profilesThis section provides an overview of SCA access profile management features. An access profile is a set of user-specified properties that define the way in which an application makes a connection to objects in the network through a management interface. The access profile specifies the protocol and the required credentials for connecting to the management interface. For example, an RSH access profile contains the port number, username, and password for connecting to a remote shell (RSH) server.

To open Access Profiles view, Figure 4 on page 35, select Manage Access Profiles from the Discovery options of the Administration tab.

Figure 4 Access Profiles view

One use of an access profile is to associate the profile with an initial discovery policy. When the initial discovery policy runs, the protocol and credentials in the access profile are used to initiate communication with the specified object types at the IP addresses specified in the initial discovery policy.

You can designate any access profile as a global profile. A global access profile can be used with any initial discovery policy that does not specify specific access profiles. This means that when running initial discovery policies that use global profiles, the system tries each global profile until it finds one that is appropriate for the object specified in the initial discovery policy.

The Discovered Objects tab lists all discovered objects and user-defined groups associated with the selected access profile.

Manage access profiles 35

Discovery

Access Profile view contains a list of the access profiles created in the system, and provides the following information:

◆ Profile Name

◆ Profile Type

◆ Global Profile

◆ Number of Discovered Objects

◆ Number of Initial Discovery Policies

◆ Description

The Access Profile view also has options for creating and managing access profiles. The options include:

◆ Create Access Profile

◆ Edit Profile

◆ Delete Profile

◆ Copy Profile

Profile types When you click Create Access profile, a profile type dialog box appears. Select the type of access profile you want to create. Profile types include:

◆ HiCommand

◆ SMI

◆ SNMP V1/V2

◆ SNMP V3

◆ SSH

◆ WMI

◆ VMware Infrastructure

The SCA online help provides complete information and field definitions.


Discovery

Manage initial discovery policiesInitial discovery is the process by which the objects in your environment are detected. An initial discovery policy specifies the IP addresses you want the system to scan to detect objects that are not yet in the Repository.

Creating initial discovery policies

Before you create an initial discovery policy and discover objects, you must create at least one access profile. A discovered object is associated with the access profile used to discover it. Other management services, such as provisioning, use the object's associated access profile.

You can designate any access profile as a global profile. A global access profile can be used with any initial discovery policy that does not specify specific access profiles. This means that when an initial discovery policy that uses global profiles runs, the system tries each global profile until it finds one that is appropriate for the objects specified in the initial discovery policy.

As an Admin you can perform the following tasks for discovery policies: create, delete, edit, enable/disable, manually run, view discovered objects, and view policy history details.

The Create Initial Discovery Policy wizard includes the following steps:

◆ Policy Information

◆ Enter IP Addresses

◆ Set Schedule

◆ Select Access Profiles

IMPORTANT!Do not run an initial discovery policy for the first time on the night of a time change to or from Daylight Savings Time.

Discovery policy execution results

This dialog box provides detailed information about a specific execution of a specific initial discovery policy. The table contains one row for each object discovered when the policy was run. Information includes:

◆ Run Date

◆ Result Message

◆ IP Address

◆ Access Profile

◆ Object Name

◆ Object Type

◆ Status Message

Manage initial discovery policies 37

Discovery

Discovery view Once you create initial discovery polices, Discovery view contains a list of these policies, and provides users the following information and options for creating and managing them:

Information:

◆ Policy Name

◆ Status

◆ Last Started

◆ Next Scheduled

◆ Last Modified

◆ Schedule enabled

◆ Description

Commands:

◆ Create Policy

◆ Edit

◆ Run Policy

◆ Enable

◆ Disable

◆ Delete

You access the Manage Initial Discovery Policies view, from the Discovery options on the Administration tab. The SCA online help provides field descriptions and specific instructions for using the Manage Initial Discovery Policies features.


Discovery

Manage rediscovery policiesRediscovery is the process by which the information about objects in the Repository is updated. Rediscovery policies specify what to rediscover (the policy scope) as well as the conditions under which you want the application to rediscover managed objects. Only discovered objects can be rediscovered.

The policy scope consists of user specified user-defined groups. When the rediscovery policy runs, each managed object in the specified user-defined groups is evaluated to see if rediscovery of that managed object is necessary.

The Administrator function of the SCA allows you to:

◆ Add a user-defined group to a rediscovery policy

◆ Create a rediscovery policy

◆ Delete a rediscovery policy

◆ Edit a rediscovery policy

◆ Enable and disable a rediscovery policy

◆ Manually rediscover specific objects

◆ Remove a user-defined group from a rediscovery policy

IMPORTANT!Do not run rediscovery on the day or evening that Daylight Savings Time occurs. This includes running discovery when time changes to or from Daylight Savings Time.

Select Manage Rediscovery Policies from the Discovery options of the Administration tab to display the Manage Rediscovery dialog box.

The SCA online help provides field descriptions and specific instructions for using these management features.

Manage rediscovery policies 39

Discovery

Configure host resolutionHost resolution is a feature that applies only to hosts that have not been discovered. It creates the instances of the hosts and their associated HBA port information based on zoning information. During host zoning, this feature maintains a naming convention in which the zone name contains the hostname.

Host resolution uses templates to parse for the hostname. Zone members are checked for host ports, and the system creates the host with the specified ports. By default, the system attempts to use the fully qualified hostname and its IP addresses when creating the host. By default, hostnames that do not resolve through DNS are not created.

Host resolution configuration parametersHost resolution can be configured using the parameters in Table 2 on page 40.

To set these parameters, log in to SCA as admin and edit the following file in this location:

/opt/DMT/local/conf/storage-path-query-service/tes.properties

After making the changes, stop and restart the discovery manager as follows:

1. Stop the Discovery Manager, type: sm_service stop SAN_server

2. Start the Discovery Manager, type: sm_service start SAN_server

This forces the appliance to refresh the topology using the new configuration.

Configuring the tes.zoneNameTemplates parameterZonename templates specify where to extract the hostname from the zonename.

The tes.properties file is delivered with the following value for the tes.zoneNameTemplates parameter:

tes.zoneNameTemplates = z_%h%|z_%h%_*|%h%_*|z_%h%_*_*|z_%h%_*_*_*

You must configure this parameter for your environment.

Table 2 Host resolution parameters

Parameter Description Default value Comments

tes.hostResolutionIsEnabled Enables and disables the feature. If set to false, no host will be created based on host resolution of hostnames based on zoning.

true

tes.validateHostWithDNS Specifies that TES should try to get the host IP address using DNS resolvers.

true If set to "false," host resolution is disabled.

tes.createHostOnlyIfDNSResolves Specifies that the host is created only if DNS resolves IP address of the host.

true

tes.zoneNameTemplates The templates for deducing the hostnames from a given zone name.

N/A The consumer must configure this value to suit their environment.

tes.allowedVendorCodes Specifies which WWN vendor codes can be considered host ports.

0000C9|000A33|000E03|00109B|0090FA|00C0DD|00E08B|001B32

The consumer is not expected to change the default, unless instructed otherwise.


Discovery

Edit the value for the tes.zoneNameTemplates parameter using the following examples as a guideline:

%h% – Specifies where to extract the hostname from the zone name.

* – This wildcard matches any string, up to a delimiter.

Example 1 tes.zoneNameTemplates = Zone_%h%_array101_port1

Zone_server1_array101_port1 matches the template and "server1" is extracted as the hostname.

Zone_server2_array101_port2 does not match the template because "port2" is part of the zone name but not part of the template. No hostname is extracted.

Example 2 tes.zoneNameTemplates = Zone_%h%_array101_*

Zone_server1_array101_port1 matches the template and "server1" is extracted as the hostname.

Zone_server2_array101_port2 matches the template and "server2" is extracted as the hostname. Note that in this example the template specifies a wildcard character as the last element of the template.

Multiple templates can be specified. Each template is separated by a pipebar (|) character. Each template is tried until the first successful match; the hostname is then extracted based on this match.

Note: Host resolution and TES configured hosts are identified in the SCA Console with separate icons to indicate non-discovered hosts.

Configure host resolution 41

Discovery

Configure non-discovered objectsYou can manage non-discovered hosts by creating a host for discovery, and defining it by name, IP address, and operating system using the Manage Non-Discovered Objects from the Discovery options of the Administrator menu on the console.

After defining the host, you can select paths that you want to associate with the host such as:

◆ WWN

◆ Fabric

◆ Connects to Switch

◆ Connects to Slot

◆ Connects to Port

The online help shows step-by-step procedures for creating a user-defined host and defining the host with the Create Host wizard.


Discovery

Manage object inventoryThe Manage Object Inventory view allows you to view and manage discovered objects. A tab in the Manage Object Inventory view appears for the following:

◆ Hosts

◆ Fabrics

◆ Switches

◆ Arrays

You can then select any object from one of the object tabs and display the object properties in the object details dialog box. In addition, you can select to rediscover the object.

You can access the Manage Object Inventory view by selecting it from the Discovery option of the Administration tab.

The SCA online help provides field descriptions and specific instructions for using these management features.

IMPORTANT!With this release of SCA, you must refresh Object Details manually.

Manage object inventory 43

Discovery

Manage Discovery Managers statusThe Discovery Managers Status dialog box allows you to check the health (status) of Discovery Managers.

Discovery Managers are responsible for discovery of:

◆ gdpm — Manages user-defined objects and services.

◆ SANs — Discovers fabrics, switches and zones

◆ Hosts — Discovers hosts and HBAs.

◆ Paths — Discovers paths.

◆ Arrays — Discovers arrays, volumes, and LUNs.

You can reach the Discovery Manager Status dialog box by clicking Discovery Managers Status in the Discovery menu of the Administration view. The status is updated manually, so you must click Check on the dialog box to get an updated view.

Note: The first time you access the dialog box, the update is performed before the dialog box is displayed.

A green status indicates that the Discovery Manager is connected. A yellow triangle indicates that the Discovery Manager is not connected.

If the Discovery Manager is not connected, Appendix A, on page 63 provides more information.


6

This chapter describes the necessary steps for maintaining the EMC Ionix Storage Configuration Advisor Sybase database. Topics include:

◆ Database Administration overview............................................................................. 46◆ Back-up repositories ...................................................................................................... 47◆ Restore repositories........................................................................................................ 49◆ Retention policy.............................................................................................................. 51

DatabaseAdministration

Database Administration 45

Database Administration

Database Administration overviewSCA uses two object repositories:

◆ Discovered Objects repository — The discovered objects in SCA are saved to a set of files.

◆ Sybase database — Compliance policies, configuration changes, breaches, and general product configuration information are stored in the Sybase database.

The Database Administration option of the SCA Administration tab allows you to manage the Sybase database, including options to:

◆ Back-up Repository — Back up the Sybase repository database, including scheduling routine backups of the database, for archiving and recovery. The database is in a Sybase file format.

◆ Manage Historical Data Retention — Purge or delete policy breaches and configuration changes.

To back up the Discovered Objects repository, you must perform a manual procedure from the API.

To restore either repository, you must perform a manual procedure from the API as shown in “Restore repositories” on page 49.

This chapter provides an overview of database administration features. The EMC Ionix Storage Configuration Advisor online help provides field descriptions and specific instructions for using these administrative features.



Back-up repositoriesSybase back-upUse the Back-up Repository dialog box as shown in Figure 5 on page 47 to back-up and schedule routine back-ups of the Sybase database that contains:

◆ Compliance and configuration change data

◆ Lockbox encrypted user passwords

You can use these back-ups for archiving or disaster recovery.

◆ Back-up now — Select to execute the back up immediately.◆ Back-up later — Select to execute the back up on a future date. Select the day of

the week and time for a single back up or to execute backups on a recurring schedule.

Figure 5 Back-up Repository dialog box

To access the Back-up Repository dialog box, select Back-up Repository from the Database Administration option of the Administration tab.

Manually back-up discovered objects, Sybase and Lockbox repositoriesYou can also manually back-up the Discovered Objects and Sybase repository. This action is necessary if, for example, you need to replace the SCA hardware appliance, or replace a hard drive or power supply. (The EMC Ionix Storage Configuration Advisor Hardware Replacement Guide provides instructions.)

To back up the Discovered Objects and Sybase repository, follow these steps:

1. Log in to the appliance through SSH using root user.

2. Stop the monitoring service for active probe, type monit stop activeprobe.

3. Stop SCA services, type /opt/DMT/local/conf/sdaStopAll.sh

4. Stop the monitoring service for tomcat, type monit stop tomcat

5. Stop monitoring service for sybase, type monit stop sybase

6. Stop the Sybase service, type service sybase stop

Back-up repositories 47


Note: Stopping all services can take from 15 to 25 minutes.

To ensure that the monitoring services are stopped, execute the monit status command that displays all the monit services that are running.

Just stopping the services does not help since they are being monitored and they come up automatically. You need to either stop the monitoring services and then stop the services or use /opt/emc/itcase/SCAApplianceDataBackup.sh, which takes care of all the processes outlined.

7. From a remote machine, SCP to the system using root user.

8. Copy existing /opt/DMT/local/repos/icf/*.rps files to external location.

9. Copy /opt/sqlanywhere10/itcase.db and /opt/sqlanywhere10/itcase.log files to external location.

10. Copy the following files from the /opt/CST/xml/ directory:

• csp.clb• csp.clb.bak• LocalDirectoryData.xml

11. To start all the monitoring services, type:

• monit start activeprobe

• monit start tomcat

• monit start sybase

Note: To ensure that the monitoring services are started, execute the monit status command that displays all the monit services that are running.



Restore repositoriesYou cannot restore repositories with the user interface, you must use the API.

Restore only Sybase repository

To restore just the Sybase repository, follow these steps:

1. Log in to appliance though SSH as Admin user.

2. Stop Tomcat service, type: monit stop tomcat.

3. Stop Sybase service, type: monit stop sybase.

4. Back up existing /opt/sqlanywhere10/itcase.db and /opt/sqlanywhere10/itcase.log

5. Copy new SCA database, and itcase.log files to /opt/sqlanywhere10. Overwriting existing files is necessary.

6. Start Sybase service, type: monit start sybase.

7. Start Tomcat service, type: monit start tomcat.

It might take a couple of minutes to start the services.

Restore all repositories

To restore the Sybase, Discovered Objects and Lockbox repositories follow these steps:

1. Log in to the appliance through SSH using root user.

2. Stop the monitoring service for active probe, type monit stop activeprobe.

3. Stop SCA services, type /opt/DMT/local/conf/sdaStopAll.sh.

4. Stop the monitoring service for tomcat, type monit stop tomcat.

5. Stop monitoring service for sybase, type monit stop sybase.

6. Stop Sybase service, type service sybase stop.

Note: To ensure that the monitoring services are stopped, execute the monit status command that displays all the monit services that are running.

7. Back up existing /opt/DMT/local/repos/icf/*.rps files.

8. Delete all *.rps file under /opt/DMT/local/repos/icf directory.

9. Copy previously backed-up SCA discovered object repository files (*.rps files) to /opt/DMT/local/repos/icf.

10. Copy the following files to /opt/CST/xml/ directory:

• csp.clb

• csp.clb.bak

• LocalDirectoryData.xml

11. Run the following commands from the location /opt/CST/cst_1.0.1/builds/linux_gcc34_ia32_d/lib:

export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:./

./cstadmin sign-file csp.clb -passphrase=<passphrase> -cstdir=<cst config dir>./cstadmin sign-file csp.clb.bak -passphrase=<passphrase>

Restore repositories 49


-cstdir=<cst config dir>./cstadmin sign-file "*.xml" -passphrase=<passphrase> -cstdir=<cst config dir>

Note: The default passphrase is 1Passphrase!

12. Back up /opt/sqlanywhere10/itcase.db and /opt/sqlanywhere10/itcase.log files.

13. Copy previously backed-up SCA database, and itcase.log files to /opt/sqlanywhere10. Overwriting existing files is necessary.

14. To start Sybase service, type service sybase start.

15. To start SCA services, type /opt/DMT/local/conf/sdaStartAll.sh.

16. To start all the monitoring services, type

• monit start activeprobe

• monit start tomcat

• monit start sybase

Note: To ensure that the monitoring services are started, execute the monit status command that displays all the monit services that are running.

Rebooting the appliance after replacing a defective appliance restarts all services



Retention policyManaging data retention allows you to purge or resolve policy breaches and configuration changes after a period of time.

To manage data retention:

1. Select Retention policy from the Database Administration option of the Administration tab to display the dialog box as shown in Figure 6 on page 51.

2. Select the checkbox next to each retention setting you want to enable.

3. Type the number of days/weeks/months/years to retain the policy breaches or configuration changes before they are purged.

4. Specify the day and time to run the retention policy.

5. Click Purge now to run the retention policy.

Note: Ensure that atleast one of the options is selected before selecting Purge now.

The time selected for purging the breaches or configuration changes allows you to purge or resolve policy breaches and configuration changes after the period of time specified. For example, if the time specified is 2 days, then the policy breaches and configuration changes 48 hours before the specified time are purged.

Figure 6 Historical data retention policy dialog box

Retention policy 51



7


◆ Overview ......................................................................................................................... 54◆ EMC SMI-S Provider for Symmetrix and CLARiiON .............................................. 55◆ Adding CLARiiONs to the EMC SMI-S Provider for discovery............................. 58◆ Brocade SMI Agent ........................................................................................................ 61◆ HiCommand for Hitachi arrays ................................................................................... 62

Install Providers

Install Providers 53

Install Providers

Overview The SCA discovery uses the following agents and providers to discover the SAN:

• Brocade/McDATA SMI Provider

• EMC SMI-S Provider for Symmetrix® and CLARiiON® (Solutions Enabler)

• EMC Host Proxy

• HiCommand for HDS arrays

It is very important to ensure that these data providers are properly installed and configured for discovery to function correctly.

Ensure that the provider versions match the versions qualified by SCA. The providers are separate products and they change rapidly. It is very essential to install the correct version for discovery to work.

Note: The EMC Ionix Storage Configuration Advisor Support Matrix provides information on supported devices and provider versions.

This chapter provides installation information for the following:

◆ “EMC SMI-S Provider for Symmetrix and CLARiiON” on page 55

◆ “Brocade SMI Agent” on page 61

◆ “Brocade SMI Agent for EOS (McDATA)” on page 61

◆ “Adding CLARiiONs to the EMC SMI-S Provider for discovery” on page 58

Note: The EMC Ionix Storage Configuration Advisor Support Matrix provides information on the latest supported versions.

Also, you should obtain installation documentation from the provider manufacturer as needed.


Install Providers

EMC SMI-S Provider for Symmetrix and CLARiiONTo discover Symmetrix, you must install the SMI-S Provider for Symmetrix and CLARiiON (with Solutions Enabler kit) on a host connected to the Symmetrix.

Note: Solutions Enabler 7.0.1 is an ECOM-based provider rather than a Pegasus-based provider. As a result several things have been deleted or moved around. Several things in the symcli/storbin directory (for example, TestSmiProvider) have been moved to the ecim/ecom/bin directory. There is no cimserver daemon any more.Default Provider Username: LocalDir/adminDefault Provider Password: #1Password

The following procedures for Windows and Linux installation are examples; the provider version depends on the particular site installation.

Windows installationThe Windows installer with the correct build of Solutions Enabler is available on Powerlink®.

To install EMC SMI-SProvider with the Solutions Enabler kit:

1. Uninstall previous versions of Solutions Enabler by navigating:

Start > Control Panel > Add/Remove Programs

2. Select EMC Solutions Enabler and remove it.

3. Delete following directories:

C:\Program Files\EMC\SYMAPIC:\Program Files\EMC\SYMCLI

4. Download the Windows installer from Powerlink.

5. Double-click the <filename_WINDOWS-x86-SMI>.msi file.

Example: Double-click the se65132-WINDOWS-x86-SMI.msi file.

6. After the installation is complete, create the following file:

<SE directory>\symcli\storbin\emcprovider_user.conf

7. Add the following line to the file in step 6 and save it:

OslProv/com.emc.se.osls.osl.StatisticsService.enable = false

8. Restart the cimserver:

a. Stop the CIM Server using following commands:

For 6.5 SMI provider:

From the SYMCLI/storbin directory:

cimserver -stop EMC_SMI_Provider


From the ECIM/ECOM/bin directory:

sm service stop ecom.exe

EMC SMI-S Provider for Symmetrix and CLARiiON 55

Install Providers

From the ECIM/Slp/lib directory:

slpd -stop

b. Restart the CIM Server using the following commands:


From the SYMCLI/storbin directory:

cimserver -start EMC_SMI_Provider



sm service start ecom.exe

From the ECIM/Slp/lib directory:

slpd -start

Linux installationThe Linux version of the Symmetrix SMI-S Provider with Solutions Enabler is available on Powerlink.

Follow these steps for installation:

1. Download the Linux installer with the correct build of Solutions Enabler from Powerlink.

Example: Download the se65132-Linux-i686-SMI.tar.Z file from Powerlink.

2. Untar the installer by typing the following command:

gunzip <filename>.tar.z

3. Extract the installer by typing the following command:

tar -xvf <filename>.tar

4. Execute the installation script by typing the following command:

./<filename_install>.sh -install

Example:

./se650294_install.sh -install

5. After the installation is complete, create the emcprovider_user.conf file. For example:

/opt/symcli/storbin/emcprovider_user.conf for SE 6.5.3

or

/opt/emc/SYMCLI/V7.0.0/storbin/emcprovider_user.conf for SE 7.0

6. Add the following line to the file in step 5 and save it:

OslProv/com.emc.se.osls.osl.StatisticsService.enable = false


Install Providers

7. Restart the cimserver:

a. Stop the CIM Server using the following commands:

For 6.5 SMI provider

From the SYMCLI directory:

./storbin/cimserver -s

For 7.0 SMI provider


1. Find the PID of the running ECOM daemon:ps -ef | grep “ECOM -d”

2. Kill the ECOM daemon:kill -s TERM <ecom-pid>

3. Find the PID of the running SLP daemon:ps -ef | grep slpd

4. Kill the SLP daemon:kill -s TERM <slpd-pid>

b. Restart the CIM Server using the following commands from the SYMCLI directory:


From the SYMCLI directory:

./storbin/cimserver



./ECOM -d

From the ECIM/slp/lib directory:

slpd

.

EMC SMI-S Provider for Symmetrix and CLARiiON 57

Install Providers

Adding CLARiiONs to the EMC SMI-S Provider for discovery

In-band CLARiiONsIn-band arrays have a direct connection with the provider’s host system through a Fibre Channel or a SCSI port. Out-of-band arrays are not connected to the host system using Fibre Channel or SCSI port. Generally, the out-of-band systems have a network connection to the host system.

In-band CLARiiON arrays are discovered automatically by the EMC SMI Provider if all of the Service Processor credentials have been supplied using the "symcfg auth" command:.

Windows: cd C:\Program Files\EMC\SYMCLI\bin UNIX: cd /usr/symcli/bin– symcfg auth add -host <SPA Address> -username <username> -password <password>symcfg auth add -host <SPB Address> -username <username> -password <password>

To verify what you added, type:

symcfg auth list

Using the TestSMiProvider application to add Symmetrix and CLARiiON arrays to the EMC SMI-S Provider

In-band and out-of-band Symmetrix and CLARiiON arrays may also be added to the EMC SMI-S Provider using the TestSmiProvider application using the "addsys" command. The TestSmiProvider application is a command-line based CIM Client that can be used to invoke generic CIM operations as well as some special operations supported only by the EMC SMI-S Provider. For example, the TestSmiProvider provides convenient methods for invoking EMC_SystemRegistrationService operations used to add, remove, discover, and refresh EMC arrays contained in the EMC SMI Provider database.

Example: Starting theTestSMiProvider

application and supplyingconnection details

Start the TestSmiProvider application by going to the SYMCLI\storbin directory and entering "TestSmiProvider".

For example:

The TestSmiProvider for SE 6.5.3 is located at symcli/storbin/ and the TestSmiProvider for SE 7.0.1 is located at ecim/ecom/bin/TestSmiProvider.

Connect to a running EMC SMI-S Provider by typing the requested information when prompted (defaults are listed in brackets and may be accepted by pressing Enter).

The following is an example of how to start the TestSMiProvider application.

C:\Program Files\EMC\SYMCLI\storbin>TestSmiProvider.exeHost [localhost]:Connection Type (ssl,no_ssl) [no_ssl]:Logfile path [Testsmiprovider.log]:Port [5988]:Username []:Password []:Connecting to localhost:1234


Install Providers

########################################################################## #### EMC SMI Provider Tester #### This program is unsupported and intended for use by EMC Support #### personnel only. At any time and without warning this program may #### be revised without regard to backwards compatibility or be #### removed entirely from the Solutions Enabler kit. ##########################################################################

slp - slp urls slpv - slp attributes cn - Connect dc - Disconnect rc - RepeatCount st - Set timeout value ns - NameSpace ens - EnumerateNamespaces ec - EnumerateClasses ecn - EnumerateClassNames ei - EnumerateInstances ein - EnumerateInstanceNames a - Associators an - AssociatorNames r - References rn - ReferenceNames gi - GetInstance gc - GetClass lc - Log control dv - Display version info addsys - EMC AddSystem refsys - EMC RefreshSystem disco - EMC Discover remsys - EMC RemoveSystem im - InvokeMethod tms - TotalManagedSpace q - Quit h - Help#####################################################################

Example: disco command To force the EMC SMI Provider to discover all in-band arrays known to it, use the TestSmiProvider "disco" command:

(EMCProvider:5988) ? disco++++ EMCDiscoverSystem ++++Output : 0Legend:0=Success, 1=Not Supported, 2=Unknown, 3=Timeout, 4=Failed5=Invalid Parameter4096=Job Queued, 4097=Size Not Supported

Example: addsyscommand

To add in-band or out-of-band arrays to the EMC SMI Provider, use the "addsys" command and supply information as requested by the prompts. In-band arrays may be specified by array name. Out-of-band arrays may be specified by hostname or IP address.

IMPORTANT!All CLARiiON Service Processors must be listed in order—for example, SP_A followed by SP_B—in the input file. Failure to specify all service processors may create array discovery problems.

(EMCProvider:1234) ? addsysAdd System {y|n} [n]: yArrayType (1=Clar, 2=Symm) [1]:One or more IP address or Hostname or Array IDElements for AddressesIP address or hostname or array id 0 (blank to quit): 1.2.3.4IP address or hostname or array id 1 (blank to quit): 1.2.3.3IP address or hostname or array id 2 (blank to quit):Address types corresponding to addresses specified above.(1=URL, 2=IP/Nodename, 3=Array ID)

Adding CLARiiONs to the EMC SMI-S Provider for discovery 59

Install Providers

Address Type (0) [default=2]:Address Type (1) [default=2]:User [null]: xyzPassword [null]: **********++++ EMCAddSystem ++++Output : 0Legend:0=Success, 1=Not Supported, 2=Unknown, 3=Timeout, 4=Failed5=Invalid Parameter4096=Job Queued, 4097=Size Not SupportedSystem :Clar_StorageSystem.CreationClassName="Clar_StorageSystem",Name="CLARiiON+APM00012345678"

Example: ein and remsyscommands

To remove an array, you must first get the array's instance name using the ein (enumerate instances) command and specify the "EMC_StorageSystem". Then use the "remsys" command and provide the array's instance name:

(localhost:5988) ? einClass: EMC_StorageSystem++Testing EnumerationInstanceNames: EMC_StorageSystem++Instance 0:Symm_StorageSystem.CreationClassName="Symm_StorageSystem",Name="SYMMETRIX+000000000123"

Enumerate 1 instance names; repeat count 1;return data in 0.046872 seconds

Retrieve and Display data - 1 Iteration(s) In 0.062496 Seconds

Please press enter key to continue...

repeat count: 1(localhost:5988) ? remsysRemove System {y|n} [n]: y

System's ObjectPath[null]: Symm_StorageSystem.CreationClassName="Symm_StorageSystem",Name="SYMMETRIX+000000000123"About to delete system Symm_StorageSystem.CreationClassName="Symm_StorageSystem",Name=="SYMMETRIX+000000000123"

Are you sure {y/n} [n]:

Example: refsys command To refresh the EMC SMI Provider's view of an array with the actual array hardware, use the TestSmiProvider "refsys" command:

(EMCProvider:1234) ? refsysRefresh Systems {y|n} [n]: yRefresh all systems {y|n} [n]:One or more System's ObjectPath.System 0 (blank to quit):Clar_StorageSystem.CreationClassName="Clar_StorageSystem",Name="CLARiiON+ APM00012345678"System 1 (blank to quit):++++ EMCRefreshSystem ++++Output : 0Legend:0=Success, 1=Not Supported, 2=Unknown, 3=Timeout, 4=Failed5=Invalid Parameter4096=Job Queued, 4097=Size Not Supported


Install Providers

Brocade SMI Agent To discover Brocade switches, you must install and run SMI providers on the host that manage those switches.

The Brocade website provides installation documentation and provider information.

Brocade SMI Agent for EOS (McDATA)To discover McData switches, you must install and run SMI providers on a host that manages those switches.

The Brocade website provides installation documentation and provider information.

Brocade SMI Agent 61

Install Providers

HiCommand for Hitachi arraysSCA supports Hitachi arrays that are supported by the HiCommand Device Manager. To discover Hitachi arrays you must install and configure the HiCommand Device Manager.

The Hitachi HiCommand Device Manager Server XML API provides discovery of Hitachi arrays; however, it does not support array health and operational status updates or alerts.

The Hitachi website provides HiCommand installation and configuration documentation.


A

This appendix explains several methods of troubleshooting issues with EMC Ionix Storage Configuration Advisor. Topics include:

◆ Overview ......................................................................................................................... 64◆ Brocade and McDATA provider issues....................................................................... 66◆ SMI-S Provider for Symmetrix and CLARiiON ........................................................ 68◆ HiCommand for HDS arrays........................................................................................ 74◆ Troubleshooting Host discovery .................................................................................. 75◆ General SMI issues......................................................................................................... 80◆ Troubleshooting the gdpm DM.................................................................................... 82◆ Troubleshooting an offline array Domain Manager.................................................. 83◆ Using SNMP.................................................................................................................... 84◆ Useful commands and utilities..................................................................................... 90◆ Using discovery logs...................................................................................................... 92◆ Rediscovery scenarios for user-defined groups......................................................... 94◆ Re-imaging the appliance ............................................................................................. 95

Troubleshooting

Troubleshooting 63

Troubleshooting

OverviewThis appendix provides additional information for best practices and troubleshooting an SCA implementation.

The EMC Ionix Storage Configuration Advisor Release Notes provides information on known issues and limitations, and the EMC Ionix Storage Configuration Advisor Support Matrix provides complete support data for this release.

The EMC Ionix Storage Configuration Advisor User Guide, available from the SCA online help or from the EMC Powerlink website, provides more information.

IMPORTANT!If you review this document and still need assistance troubleshooting your application, contact your EMC Support Representative to check relevant log files.


Troubleshooting

General provider configuration issuesFollow these guidelines when configuring providers and troubleshooting provider configuration issues:

◆ The SCA discovery services use the following agents and providers to discover the SAN:

• Brocade/McDATA SMI Provider

• EMC SMI-S Provider for Symmetrix and CLARiiON (Solutions Enabler)

• EMC Host Proxy

It is very important that these data providers are properly installed and configured for discovery to function properly.

◆ Ensure that the provider versions match the versions qualified by SCA. The providers are separate products and they change rapidly. It is very essential that the correct version is installed for discovery to work.

Note: The EMC Ionix Storage Configuration Advisor Support Matrix provides information on supported devices and provider versions.

◆ Learn how to enable logging on providers. (The manufacturer’s documentation provides information.)

◆ Have knowledge of starting and stopping provider services. (“Useful commands and utilities” on page 90.)

◆ Keep a list of provider known issues at hand. (This Troubleshooting section and manufacturer’s provider documentation provide information.)

◆ Brocade providers only need a single proxy switch to manage a large fabric. Since SCA discovery management is lost if the proxy becomes unavailable, select a high availability director class switch.

◆ To receive events from Cisco, add the IP address of the SCA appliance to trap recipient table on Cisco. For all other providers, the appliance automatically subscribes to events following a discovery.

◆ The EMC Ionix Storage Configuration Advisor Performance and Scalability Guidelines provides information on allocating managed elements per providers. There are no restrictions for host or Cisco.

◆ Host discovery requires Host-HBA, drivers, and firmware listed in the EMC Support Matrix. Use the E-LabTM Interoperability Navigator tool, available through this URL:

http://Powerlink.EMC.com/

◆ Discovery issues typically arise when new models, software, and firmware are introduced to the discovery environment. Identifying where the issue lies, with SCA or provider and managed element is key to troubleshooting.

General provider configuration issuesOverview 65

http://powerlink.emc.com/km/appmanager/km/secureDesktop

Troubleshooting

Brocade and McDATA provider issuesThis section describes issues that may arise with SAN discovery when Brocade and McDATA providers are used.

McDATA guidesA McDATA provider troubleshooting guide is available on their corporate website.

No elements detected with Brocade and McDATA CIMOMsFollow these steps:

1. Verify that instances of root/brocade1:Brocade_Switch or root/mcdata:McDATA_Switch exist in the CIMOM using a CIM/XML client such as cimcli.

If there are no errors but no instances are returned for one of these, then it is possible that the CIMOM was not configured correctly or it cannot connect to its proxy or proxies. Both CIMOMs have configuration GUIs that you can use to verify this.

The Brocade configuration GUI lists all proxy switches used and whether or not it is currently connected to each.

The McDATA GUI tests the credentials used for EFCM as listed under Test Connection under Management Platform > Update Login ID Password.

2. Verify that the correct CIMOM is installed on the expected IP. If the detection probe can connect to the CIMOM but it is managing arrays instead of switches, it returns “No Elements Detected” without failures or errors in the probe log.

3. If the SMI Access Profile does not have SSL enabled, make sure that the provider is configured with HTTP access enabled. The default setting for the McDATA provider is to have HTTP disabled and only HTTPS (SSL) enabled. Alternatively, modify the SMI Access Profile to enable SSL and set the port number accordingly (default port for HTTPS is 5989).

4. Verify that SSL certificate authentication is disabled. In the Brocade SMI Agent, disable the "Mutual Authentication (Clients)" and "Mutual Authentication (Indications)" features.

Brocade provider not sending eventsThe Brocade provider may not send events if either the "Mutual Authentication (Client)" or "Mutual Authentication (Indications)" are enabled.

A workaround for this issue is to verify that the "Mutual Authentication (Client)" and "Mutual Authentication (Indications)" features are disabled. If either of them is enabled, disable it using Brocade's configuration tool.

After restarting the provider, run Brocade's SubscriptionCleanup tool (<install>\agent\server\jserver\bin\SubscriptionCleanup.bat on Windows) to remove any failed subscription instances. Finally, run a Discovery Policy or Rediscovery Policy using that provider.


Troubleshooting

Note: The SubscriptionCleanup tool is not included with Brocade SMI Agent for EOS (McDATA) version 2.5; if needed you can use SubscriptionCleanup tool included with Brocade SMI Agent for FOS (Brocade) version 120.7.2a

Brocade provider stops sending eventsThe Brocade provider may stop sending events due to a large number of event subscriptions.

A workaround for this issue is to schedule rediscoveries periodically and disable indication subscriptions.

To disable indication subscriptions:

1. Open the following file:

/opt/DMT/local/conf/cmp-fabric/fabric-smi.import

2. Change TRUE to FALSE in the following line:

parameters += {"INDICATIONS_SUBSCRIBE", "TRUE"}

3. Restart the SCA.

Brocade provider consuming memory and CPUSometimes the Brocade provider consumes large amounts of memory and CPU. To determine CPU and memory consumption:

1. Start Windows Task Manager

2. Look for the following provider process with several hundred threads active and large amounts of memory allocated to it:

jserverd.exe

3. If this is occurring, restart the provider to recover from this state.

A workaround for this issue is to avoid indication subscriptions. If indication subscriptions are enabled, disable them by following the procedure in “Brocade provider not sending events” on page 66.

Error message: Operation Not SupportedWhile adding a proxy switch to the Brocade SMI Agent on a host that has multiple IP addresses, you may notice an error "Operation Not Supported."

A workaround for this issue is to modify the file <SMIAgent>/agent/server/jserver/bin/SMIAgentConfig.xml as described in the SMI Agent User Guide under "Brocade SMI Agent", "Enable multi-homed support".

General provider configuration issuesBrocade and McDATA provider issues 67

Troubleshooting

SMI-S Provider for Symmetrix and CLARiiON Provider documentation contains information about installation, starting, stopping, and configuring the SMI provider.

“EMC SMI-S Provider for Symmetrix and CLARiiON” on page 55 provides information on the installation for SMI-S Provider for Symmetrix and CLARiiON.

Provider versionsArray discovery can fail or there may be partial discovery if the provider version is not qualified.

Identifying SMI-S Provider version numbersTo verify the versions of the SE kit and the SMI-S provider do the following:

1. Start symcli/storbin/TestSMIProvider(.exe)

2. At the command prompt, type the following:

dv

This command displays version information for the Pegasus CIMOM, SMI-S Provider, Solutions Enabler, and all the attached Symmetrix and CLARiiON systems.

Logging troubleshooting dataTo log additional troubleshooting information for the array discovery, enable debug mode:

1. Open the following file:

/opt/DMT/local/conf/cmp-storage-arrays/array.import

2. Set the DEBUG parameter to TRUE as in the following example:

CMP_ConfigurationParameters::Array-ConfigurationParameters {parameters += {"DEBUG", "TRUE"}

}

3. Restart the DM after updating the parameter.

Disabling statistical information gatheringThe EMC SMI-S Provider collects statistical information from the arrays every 5 minutes. This information is not used by SCA at this time. Disable this collection if there are no other applications that utilize the statistical information.


Troubleshooting

Solutions Enabler configuration error regarding RA DirectorsA Solutions Enabler configuration error as in Example 1 may appear in the Array DM log file regarding RA Directors. Sometimes this can be addressed by cleaning up the Solutions Enabler database and restarting it.

Example 1 Error for RA Director from array1.log file

===========================================WBEM-EUNKNOWNERROR-Unknown error occurred: C:ERROR_CLASS_SOFTWAREF:ERROR_FAMILY_FAILED R:1 R:1100015 L:2 1100015 : "The load of a remote storage array configuration failed" : "Unable to initialize Mask Session for specified handle" : 2 : 152 : "Could not find any valid (online and connected) RA Director to use for remote call"===========================================

If this occurs, try cleaning the Solutions Enabler repository.

To clean Solutions Enabler on a Windows host:

1. Stop the cimserver by typing the following commands:

cd C:\Program Files\EMC\SYMCLI\storbin

cimserver –stop EMC_SMI_Provider

2. Delete the following file by typing the command:

del C:\Program Files\EMC\SYMAPI\db\symapi_db.bin

3. Restart the cimserver by typing the following commands:

cd C:\Program Files\EMC\SYMCLI\storbin

cimserver –start EMC_SMI_Provider

To clean Solutions Enabler on a UNIX host:

1. Stop the cimserver by typing the following commands:

cd /usr/SYMCLI

./storbin/cimserver –s

2. Delete the following file by typing the command:

rm /var/symapi/db/symapi_db.bin

3. Restart the cimserver by typing the following commands:

cd /usr/SYMCLI

./storbin/cimserver

Discovery errors related to timing outThe provider does not discover the arrays until it receives the first client request. When a large number of arrays are managed by a single SMI-S provider instance, the initial discovery may take several minutes and may sometimes result in time-outs during detection. You may see the following errors in the logs:

WBEM-EUNKNOWNERROR-Unknown error occured: C:ERROR_CLASS_SOFTWARE

General provider configuration issuesSMI-S Provider for Symmetrix and CLARiiON 69

Troubleshooting

F:ERROR_FAMILY_FAILED R:1 connection timed out

In order to avoid this, do the following after starting the provider for the first time:

1. Start symcli/storbin/TestSMIProvider(.exe)

2. At the command prompt, type the following:

ein

3. When prompted for the Classname, force the provider to discover the arrays by typing the following:

EMC_StorageSystem

Some array discovery time-out issues may be related to network latency (such as discovering over a WAN). If this is the case, then the array DM has a configuration parameter that can be adjusted to work around the latency.

An example of an array discovery time-out during the discovery of storage volumes over a WAN:

[25-Jun-2008 06:42:47 AM+659ms UTC] t@-1419818064 Discovery #2ASL-W-ERROR_RULE_SOURCE-While executing rule set '/opt/DMT//local/rules/cmp-storage-rules/array/volumes_discovery_smi.asl' ASL-ERROR_ACTION-While executing action at: ASL-CALL_STACK_RULE- RuleName: DISCOVER, Line: 1766 ASL-CALL_STACK_RULE- RuleName: INITIATE_DISCOVERY, Line: 1616 ASL-CALL_STACK_RULE- RuleName: START, Line: 1734 ASL-ERROR_INVOKE-While attempting to invoke operation 'createAssociators' of object 'CIMXML_Session::CIMXML_Session-172.23.144.146-access-profile-3-root/emc' WBEM-ECREATE_ASSOCIATED_FAILED-Create associated instance failed with remote instance root/emc:Symm_DeviceStoragePool%InstanceID=SYMMETRIX+000187700037+C+0000 and association CIM_AllocatedFromStoragePool WBEM-EUNKNOWNERROR-Unknown error occured: C:ERROR_CLASS_SOFTWARE F:ERROR_FAMILY_FAILED R:1 connection timed out

To increase the default time-out period while discovering CIMOMs across a WAN where latency may be an issue, follow this procedure:

1. Edit /opt/DMT/local/conf/cmp-storage-array/array.import.

2. Find the following section:

CMP_ConfigurationParameters::SMI-ConfigurationParameters { … # Timeout values are in seconds parameters += {"DETECTION_TIMEOUT", "900"} parameters += {"DISCOVERY_TIMEOUT", "240"} …}

3. Change the value of "DISCOVERY_TIMEOUT" to a larger value.

4. Save the array.import file.

5. Restart the Array DM (or entire SCA).

6. Initiate discovery again.


Troubleshooting

There may be time-outs because of dropped packets too. In that case, the time-out errors in the log file happen randomly at different places. If the time-outs are consistently in the same place (especially while discovering volumes), as in this case, it may be an indication of network latency related problems. In such cases, increasing the time-out alleviates the problem. However, if you have network issues where packets are dropped randomly, a large time-out value keeps discovery going for a long time because each time there is a problem, the probe waits much longer before moving on.

VCMDB devicesA VCMDB device should also be visible to the host where the provider is running.

Starting the cimserver on LinuxUse the full path of the cimserver when starting the provider, such as the following:

/usr/symcli/storbin/cimserver

Otherwise, a default cimserver that ships with Linux may be started.

Database errors in the logAn error message such as the following indicates that some changes have been made to the array outside of the CIMOM, and the provider is unable to synchronize its cache with the new state of the array:

WBEM-EUNKNOWNERROR-Unknown error occured: C:ERROR_CLASS_SOFTWARE F:ERROR_FAMILY_FAILED R:1 R:1200019 1200019 : "The internal database is in an inconsistent state, and must be fully synchronized before performing this operation."

To rectify this situation:

1. Shut down the cimserver.

2. Shut down all the stordaemons.

3. Delete the following files:

/var/symapi/db/*.bin/var/symapi/db/*.xml

4. Restart all services.

Connection failed messageThe following error in the array logs indicate that the CIMOM IP address is bad or the host is down, or the CIMOM is not running:

ASL-W-ERROR_RULE_SOURCE-While executing rule set '/opt/DMT//local/rules/cmp-storage-rules/array/array_detection_smi.asl' ASL-ERROR_ACTION-While executing action at: ASL-CALL_STACK_RULE- RuleName: DETECT_CIMOM, Line: 1515 ASL-CALL_STACK_RULE- RuleName: ATTEMPT_ARRAY_DETECT, Line: 2192 ASL-CALL_STACK_RULE- RuleName: START, Line: 1756


Troubleshooting

ASL-ERROR_INVOKE-While attempting to invoke operation 'enumerateInstanceNames' of object 'CIMXML_Session::OSLS-Session-losay1971210153329927-172.23.157.197-access- profile-1' WBEM-EUNKNOWNERROR-Unknown error occured: C:ERROR_CLASS_SOFTWARE F:ERROR_FAMILY_FAILED R:1 Cannot connect to 172.23.157.197:5988. Connection failed.

Error opening gatekeeper deviceThe provider host should be FC connected to the Symmetrix array with a minimum of four gatekeeper devices available for each Symmetrix system connected to the host. If you see the following errors in the logs, it means there are no gatekeeper devices available or that there is a problem with the host connectivity to the gatekeepers:

ASL-W-ERROR_RULE_SOURCE-While executing rule set ASL-ERROR_ACTION-While executing action at: ASL-ERROR_INVOKE-While attempting to invoke operation 'createAssociators' of WBEM-EUNKNOWNERROR-Unknown error occured: C:ERROR_CLASS_SOFTWARE F:ERROR_FAMILY_FAILED R:1 R:1100012 L:2 1100012 : "A gatekeeper open : 2 : 34 : "Error opening the gatekeeper device for communication to the Symmetrix"

Array DM errors caused by EMC SMI Provider/Solutions Enabler related issuesEntries, in the SYMAPI device masking database, point to a device that has been deleted. The following error is displayed in the logs:

WBEM-ECREATE_REFERENCED_FAILED-Create referenced instance failed with remote instanceroot/emc:Symm_LunMaskingSCSIProtocolController%CreationClassName=Symm_LunMaskingSCSIProtocolController%DeviceID=W+200000E08B0B5C31210000E08B0B5C31+SYMMETRIX+000190100315+FA-3C+1%SystemCreationClassName=Symm_StorageProcesso rSystem%SystemName=SYMMETRIX+000190100315+FA-3C and association CIM_ProtocolControllerForUnitWBEM-EUNKNOWNERROR-Unknown error occurred: C:ERROR_CLASS_SOFTWARE F:ERROR_FAMILY_FAILED R:1 R:1100007 L:2 1100007 : "A device attribute makes its use invalid for the requested operation" : 2 : 4659 : "The operation cannot be completed because one or more devices are unconfigured"

In order to view the complete list of bad devices, log on to the provider (symapi\logs) and browse for a file EMCProvider<date> and find Device name = “01F11” as shown next.

Thu Feb 05 10:34:45 Eastern Standard Time 2009 losak111 cimserver.exe 3800 4900 global WARNING Device.cpp 231 : Received STORAPI return code STOR_C_ARRAY_INV_DEVICE for StorDevShow of array id: '<Array type="SYMMETRIX" encoding="String" value="000190100315" />' using device id: '<Device name="01F11" />'.


Troubleshooting

It is possible that the storage array masking database may have devices assigned and configured that are no longer available for use.

To overcome this issue:

1. Use "symmaskdb list database" to find the entries that use the device in question

symmaskdb list database -wwn 10000000C94186F3Symmetrix ID : 000190300172Database Type : Type6Last updated at : 02:03:18 PM on Thu Sep 27,2007Director Identification : FA-2ADirector Port : 1 User-generatedIdentifier Type Node Name Port Name Devices---------------- ----- --------------------------------- 10000000c94186f3 Fibre losak131 10000000c12345f3 0039

003C:003F0103172F:1732

2. Use the symmask delete command to remove those devices from the database:

symmask delete -wwn 10000000c12345f3 -dir 2a -p 1

Masking and Mapping discovery should complete normally after all bad masking entries have been removed.


Troubleshooting

HiCommand for HDS arraysThis section describes issues that may arise with discovering HDS arrays.

HiCommand Device Manager does not support an automatic refresh of array dataThe Hitachi Device Manager or HP Command View XP Device Manager must be configured to automatically refresh the array data contained in the Device Manager database. Else, a manual refresh needs to be performed from the Device Manager user interface before each array discovery:

◆ To automatically refresh the array data in the Device Manager, execute the "RefreshStorageArrays" CLI command and specify a refresh interval.

For example:

HiCommandCLI RefreshStorageArrays -o"D:\logs\RefreshStorageArrays.log" "interval=1440"

• The Interval time option is specified in minutes from storage subsystem re-discovery completion to start of next storage subsystem re-discovery. You can specify a value from 0 to 2147483647. If it is not set, the default interval time is 0.

• The user must be a member of the "All Resources Resource Group" and have Modify permissions to execute this command. A user to whom a user-defined resource group is assigned, and who has only the View permission, cannot execute this command.

• The Hitachi Storage Command Suite Hitachi Device Manager Software Command Line Interface (CLI) user’s guide or similar document for HP Command View XP provides more information.

◆ To manually refresh using the Device Manager UI:

1. Log in to the Device Manager web-based UI.

2. Select Subsystems in the explorer pane.

3. Select the array you wish to refresh in the Subsystems pane .

4. Click the Refresh button.


Troubleshooting

Troubleshooting Host discoveryThis section describes issues that may arise during host discovery.

Know the difference between discovered host instances and host instances that are created by resolving their names based on zoning information.

Supported HBA, driver, and firmware versionsHost discovery fails if the target host does not have E-Lab supported HBAs, drivers, and firmware versions.

To verify that hosts use supported versions, obtain the version numbers from hosts and verify them against the eLab supported versions:

1. Log in to the target host.

2. Go to:

/usr/symcli/bin

3. Type the following command:

./syminq –fibre hba

This command returns the versions on the host.

Note: Use Step 2 and Step 3 only if symcli is in target machine. If not, use vendor CLIs and UIs (in case of Windows) to find out about the versions.

4. Compare these versions to the supported versions.

The Qlogic website provides supported Qlogic HBAs, and the Emulex website provides supported Emulex HBAs.

For additional supported versions, use the E-Lab Interoperability Navigator tool, available through this URL:

http://Powerlink.EMC.com/

Discovering HBA path dataIf HBA path information is not discovered for a target host, the easiest way to diagnose issues is to go to the target machine and run the inq command. Host discovery uses this command to discover the host.

For UNIX hosts, inq is located in:

/tmp/nl_dwd

Type the following to run inq:

inq –mapinfo

Note: If logged in as a sudo user, type the following to run the INQ:sudo /tmp/nl_dwd/inq -mapinfo

If everything is fine, the output should look like the output in “Example 2: Sample inq output”.

General provider configuration issuesTroubleshooting Host discovery 75

http://powerlink.emc.com/km/appmanager/km/secureDesktop

Troubleshooting

Example 2: Sample inq output# ./inq -mapinfoInquiry utility, Version T7.3-863 (Rev 0.267) (SIL Version T6.5.0.267 (Edit Level 863)Copyright (C) by EMC Corporation, all rights reserved.For help type inq -h.---------------------------------------------------HBA name: Emulex-LP9002-1host WWN: 20000000C928CA4Cvendor name: Emulex Corporationmodel: LP9002firmware version: 3.81A3 (C2D3.81A3)driver version: 6.11c; HBAAPI(I) v2.0.f, 01-23-06serial number: 0000c928ca4cvendor code: 0xc9HBA type: Fibre Channelport count: 1port number: 1port WWN: 10000000C928CA4CPort OS name: /devices/pci@17,4000/fibre-channel@2port type: NPORTport speed: 1GBITsupported speed: 2GBITport state: ONLINEport FCID: 0x621013----------------------------------------------------RAW ARRAYDEVICE NAME :VENDOR :PROD :REV :SERIAL # :CAP :BUS :TGT :LUN :HBA PORT WWN :TARGET PORT WWN :PARENT DEVICE--------------------------------------------------------------------------------------------------------------------------------------------------------/dev/rdsk/c0t0d0s2 :FUJITSU :MAN3184MC :3703 :UFR4P220 :17847430 :0 :0 :0 :N/A :N/A :N/A/dev/rdsk/c0t4d0s2 :TEAC :CD-ROM CD :1.0A : :17847430 :0 :4 :0 :N/A :N/A :N/A/dev/rdsk/c2t0d0s2 :HITACHI :OPEN-3 :2113 :33038 : 2403360 :2 :0 :0 :10000000C928CA4C :50060e8003513500 :/dev/rdsk/emcpower40c/dev/rdsk/c2t1d0s2 :HITACHI :OPEN-3 :2113 :33038 : 2403360 :2 :1 :0 :10000000C928CA4C :50060e8003810e17 :/dev/rdsk/emcpower40c/dev/rdsk/emcpower40c:HITACHI :OPEN-3 :2113 :33038 : 2403360 :0 :0 :0 :N/A :N/A :N/A

The top portion contains HBA information. The bottom tabular portion contains host device/path information.

If the bottom portion is empty or WWNs are missing for host devices coming from storage arrays, then it could be a SNIA library issue. In this case you must install the latest HBA drivers as per the EMC Support Matrix.

There is a SNIA library issue if you see garbage in HBA names.

If inq simply crashed with “segmentation fault”, then there are no HBAs in this host.

If the PARENT DEVICE column displays N/A, then the PowerPath® is not managing the paths. For Windows hosts, the PARENT DEVICE column always displays N/A because Windows hides child devices when PowerPath is managing the paths.

The above example is of the scenario where inq is in target host. In case the “ActiveProbe” fails to push the inq, follow these steps:

1. Check whether inq is present.

2. If the inq is missing check whether HBAs are present.


Troubleshooting

3. If inq is not pushed even though the HBAs are present, check:

• If scp is installed in the host

• The host is a UNIX

4. If the host is a Windows host, check the ActiveProbeService.log to see why inq push failed.

5. If inq is present, try to push it and observe the output.

6. If the host is accessing host devices from arrays through HBA and paths are missing in inq output, then check the HBA driver and firmware versions.

Failure to open WMI sessionsThe following prerequisites are required for successful Windows host discovery.

Windows prerequisites:◆ The user (defined in the access profile) through which the discovery is done must

be an administrator, or should be part of an administrator group.

◆ Windows Management Instrumentation and Remote Registry services must be running on the target host.

◆ DCOM communication must be enabled between the target host and the SCA. On the target host make sure that the following registry key is set to Y:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole ->EnableDCOM

UNIX prerequisites:There are no prerequisites other than file access permissions that are available through the root user.

Common reasons for discovery failure with Windows hostsThe following are the common reasons for discovery failure.

Improper credentialsVerify that all credentials in the WMI profile are correct. If they are not, the host1.log file displays the following error message:

Credentials/Authentication Failure

If the wrong credentials were passed for discovery from the access profiles, the host1.log file displays the following message for the IP with the credentials of the target host:

03-02-08 11:03:23 AM==> HostDetection.DiscoveryTaskToTomcatSubmitter.createTasksForIPsAndAddToTomcat: 172.23.147.219-Got an unsuccessful result from ActiveProbe03-02-08 11:03:23 AM==> HostDetection.DiscoveryTaskToTomcatSubmitter.createTasksForIPsAndAddToTomcat: 172.23.147.219-The message is Authentication failed03-02-08 11:03:23 AM==> HostDetection.DiscoveryTaskToTomcatSubmitter.createTasksForIPsAndAddToTomcat: 172.23.147.219-The resolution is CHANGE_USER_OR_CREDENTIALS03-02-08 11:03:23 AM==> HostDetection.setDetectionResults: detection result added is [, Host, SSH, 0, , , , , , 219 discovery1209740538880, , , ]


Troubleshooting

If an unreachable IP was tried for detection or discovery or if there were network issues, the following message appears in the host1.log for the targeted IP address that was tried and unsuccessful:

19-02-08 11:19:34 AM==> HostDetection.DiscoveryTaskToTomcatSubmitter.createTasksForIPsAndAddToTomcat: 192.168.101.101-The resolution is CHECK_NETWORK19-02-08 11:19:34 AM==> HostDetection.setDetectionResults: detection result added is [, Host, SSH, 0, , , , , , invalid discovery1209741352567, , , ]

Logging Active Probe dataTo capture data from Active Probe (APE) discovery attempts, set the debug flag to true in the following file:

/opt/DMT/local/conf/host/RuntimeSettings.properties

The default setting is false. Setting it to true enables debugging invalid data originating with APE that may result in failure when updating data to the DM.

Using sudo

Error symptoms for a host with partial sudo prerequisites

If the target host does not have the sudo account, but the sudo feature is installed, then the policy fails because the account to log in to the host is not available.

If the target host has a valid sudo account (without the sudo feature installed), then there is a partial discovery because of limited credentials.

If the target host has a valid account with the sudo feature installed, but the credentials provided for sudo account are invalid then the discovery fails because of authentication failure.

Verifying sudo feature prerequisites

Log in to the respective host using sudo credentials. If login credentials do not work, resolve this with your local IT.

Move to the /tmp/nl_dwd folder if it is present and execute sudo /tmp/nl_dwd/inq –mapinfo. If sudo is installed, all HBAs and the respective host devices are visible. Otherwise, the following message is populated: Sudo is not available.

If the /tmp/nl_dwd folder is not present, type “sudo”. If you see the message sudo: not found or Sudo is not available, have your local IT install it.

Using the administrative (root) account, check the settings for the host to be discovered in the sudoers file. The UNIX sudoers file is typically located at /etc/sudoers or /usr/local/etc/sudoers. On some UNIX hosts, the sudoers file can be edited using visudo, otherwise use locally available editors (vi, and so on).

Issues on UNIX hosts with sudo accounts

Sudo Messages repeatedly seen on UNIX hosts with improperly configured sudo accountsOn all the UNIX hosts with Sudo accounts, the sudo messages get repeatedly populated.

This issue is observed only when the discovery command fails, and a line is added to the console. As the application is designed to retry the same command at an interval of x seconds for 2 hours, this message gets added repeatedly. It is the absence of the sudoers file that causes the problem.


Troubleshooting

Improperly configured sudo accounts could be either of the scenarios explained next:

◆ The credentials given to SCA do not include the /etc/sudoers file.

Message displayed on the UNIX console:

user NOT in sudoers ; TTY=pts/4 ; PWD=/ ; USER=root ; COMMAND=/tmp/nl_dwd/inq -mapinfo

◆ /etc/sudoers file was never setup. Sudo accounts are not used.

Message displayed on the UNIX console:

can't stat /etc/sudoers: No such file or directory; s/2 ; PWD=/ ; USER=root ; COMMAND=/tmp/nl_dwd/inq


Troubleshooting

General SMI issuesThere are some connection-related errors that apply to fabric and array-based SMI discovery. During detection, some of these errors may not be a real issue. If several SMI access profiles and IP addresses are given, then the discovery attempts all combinations, and some are bound to fail.

Error message: HTTP Error (401 Unauthorized) The following messages are a result of invalid credentials:

Error message: Invalid Credentials (Detection)

[25-apr-2009 04:25:23 PM+961ms UTC] t@-123456789 Discovery #8CMPP-W-EDIC-Invalid credentials specified for IP 123.45.678.123 using access profile SMIProfile. Check provider configuration.

Error message: Invalid Credentials (Discovery)

[25-apr-2009 04:27:20 PM+210ms UTC] t@-123456789 Discovery #9ASL-W-ERROR_RULE_SOURCE-While executing rule set '/opt/DMT//local/rules/cmp-storage-rules/fabric-smi/switch_discovery_smi.asl' ASL-ERROR_ACTION-While executing action at: ASL-CALL_STACK_RULE- RuleName: ELEMENT_REACHABLE, Line: 1489 ASL-CALL_STACK_RULE- RuleName: INITIATE_DISCOVERY, Line: 2442 ASL-CALL_STACK_RULE- RuleName: START, Line: 2604 ASL-ERROR_INVOKE-While attempting to invoke operation 'findInstance' of object'CIMXML_Session::CIMXML_Session-123.45.678.123-access-profile-1-root/mcdat a' WBEM-ENONEXISTENTINSTANCE-Instanceroot/mcdata:McDATA_Switch%CreationClassName=McDATA_Switch%Name=11111102222 407CD does not exist WBEM-EUNKNOWNERROR-Unknown error occurred: C:ERROR_CLASS_SOFTWARE F:ERROR_FAMILY_FAILED R:1 HTTP Error (401 Unauthorized).[25-apr-2009 04:27:20 PM+210ms UTC] t@-1234568 Discovery #9CMPP-E-EIC-Invalid credentials specified for IP 123.45.678.123 while discovering Switch test111. Check Access Profile and provider configuration.

Error message: Cannot connect to <IP address>. Connection failedUnreachable IP, SSL Certificates enabled on the CIMOM, wrong port number issues appear with the same Connection Failed message similar to the message in Example 2 and Example 3

To determine what the problem is, ensure that the IP can be pinged and check the configuration on the CIMOM.

The default port numbers are 5988 for HTTP and 5989 for HTTPS (SSL), but they can be changed on the CIMOM.

Note: For SCA and RME 1.0 SSL Certificates (Mutual Authentication) are not supported.


Troubleshooting

Example 2 Sample Connection Failed message (Detection)

[25-Feb-2009 04:29:46 PM+815ms UTC] t@-123456789 Discovery #1CMPP-W-EDUTCTI-Unable to connect to IP 123.45.678.123 using access profile SMIProfile. Make sure provider is running.

Example 3 Sample Connection Failed message (Discovery)

[25-Feb-2009 04:28:56 PM+445ms UTC] t@-123456789 Discovery #10CMPP-N-NDISCO_SHORT-Probing Switch information about Switch test111 from IP 123.45.678.123 using Access Profile SMIProfile[25-Feb-2009 04:28:58 PM+466ms UTC] t@-123456789 Discovery #10ASL-W-ERROR_RULE_SOURCE-While executing rule set'/opt/DMT//local/rules/cmp-storage-rules/fabric-smi/switch_discovery_smi.a sl' ASL-ERROR_ACTION-While executing action at: ASL-CALL_STACK_RULE- RuleName: ELEMENT_REACHABLE, Line: 1489 ASL-CALL_STACK_RULE- RuleName: INITIATE_DISCOVERY, Line: 2442 ASL-CALL_STACK_RULE- RuleName: START, Line: 2604 ASL-ERROR_INVOKE-While attempting to invoke operation 'findInstance' of object'CIMXML_Session::CIMXML_Session-172.23.145.234-access-profile-1-root/mcdat a' WBEM-ENONEXISTENTINSTANCE-Instanceroot/mcdata:McDATA_Switch%CreationClassName=McDATA_Switch%Name=11111800880 407CD does not exist WBEM-EUNKNOWNERROR-Unknown error occurred: C:ERROR_CLASS_SOFTWARE F:ERROR_FAMILY_FAILED R:1 Cannot connect to 123.45.678.123:5980. Connection failed.[25-Feb-2009 04:28:58 PM+466ms UTC] t@-1774249040 Discovery #10CMPP-E-EUTCTI-Unable to connect to IP 123.45.678.123 while discovering Switch test111. Make sure provider is running.

Error message: Unable to reach element. There are two reasons for this error message:

◆ The CIMOM is no longer managing the device. For example, a switch may have disappeared after a fabric split.

◆ There is a connection error.

If it is a connection error, then there should be another error message nearby in the element DM logs, similar to the following messages:

CMPP-E-EENR-Unable to reach Switch element angels80

or

CMPP-E-EENR-Unable to reach Array element angels80

In the UI, the error code “CMPP-E-EENR-“ is stripped off and does not appear.

General provider configuration issuesGeneral SMI issues 81

Troubleshooting

Troubleshooting the gdpm DMData path related issues may result from problems in the Synchronizer or with the discovered data. If you encounter path issues, use the following procedure to collect information necessary to investigate the problem:

1. Log in to the appliance and collect Translator.log and gdpm.log files in /opt/DMT/local/logs.

2. Run these commands to dump GDP-related data from all DMs:

a. Change current directory to /opt/DMT/local/conf.

b. Run dm_dum.sh.

c. Collect all generated files in the newly created dm_dump directory.

3. Include gdpm.log under Guidelines for analyzing troubleshooting data.

Guidelines for analyzing troubleshooting dataThese are some guidelines for analyzing the data collected in the following files:

◆ Translator.log

◆ path.log

◆ path.txt

◆ array1.txt

◆ host1.txt

◆ san1.txt

If you find problems in the paths between a host and an array:

a. Open host1.txt and locate the host, or port, if you know which host or port to look for.

b. Open path.txt and locate the same host using the instance name.

c. Check the attributes for paths under this host/port.

If there is no path:

a. Open the array1.txt file and look for the host port WWN.

b. See if it is masked.

If it is, then probably there was an issue during synchronization, and you should look at the Translator.log file. If not, then this indicates the discovery was not complete or there was an issue during discovery or an issue with the provider.

If there are paths but the attributes are not as expected, for example, IsConnected and IsZoned are wrong, open the san1.txt file and search for the host port WWN or array port WWN. Check if they are in the same fabric and in the same zone. If yes, then probably it is a synchronization issue. If not, then check the discovery-side issues.


Troubleshooting

Troubleshooting an offline array Domain ManagerIf an array DM crashes or stops, objects managed by it will not be populated or managed in the other array DM unless the offline DM is restarted.

To diagnose whether a DM is offline:

1. If all rediscovery policies managed by a particular DM fail and the following error message is displayed in the UI, then that DM has gone offline. The error message is as follows:

Discovery service related data for this element not found. Unable to proceed with discovery of the element <element Name>.

2. Log in to the appliance using SSH and type sm_service show.

To restart the offline DM:

1. Type sm_service start <ServiceName>

Example: sm_service start Array_Server_1

General provider configuration issuesTroubleshooting an offline array Domain Manager 83

Troubleshooting

Using SNMPTo use SMMPv3 or SNMPv2, it must be enabled on the switch. Using an incorrect version often causes problems.

Cisco SNMP Rediscoveries not invoked on configuration changesMake sure that the appliance IP is set as the trap destination on each Cisco switch managed by the SCA.

To set up traps destination on the Cisco switch refer to http://www.cisco.com/


http://www.cisco.com/en/US/docs/storage/san_switches/mds9000/sw/rel_3_x/configuration/guides/cli_3_3_1/snmp.html#wp1352294

Troubleshooting

Troubleshooting user interface conditionsThis section describes the following user interface (UI) conditions and actions that you need to take to diagnose them:

◆ “Default value for the UDG refresh period” on page 85

◆ “Default value for the UDG refresh period” on page 85

◆ “Discovery status: One or more element discoveries failed” on page 86

◆ “Discovery status: No elements detected” on page 86

◆ “Out of memory errors: The user interface hangs, stalls, or slows down” on page 86

◆ “UI logs for troubleshooting” on page 87

◆ “Unable to open UI Browser to the appliance” on page 88

◆ “Unable to see any data in the UI even after creating profiles and policies” on page 88

◆ “Progress bar for loading data hangs for a long time in any view” on page 88

◆ “Unable to sort or filter by 'Last Successful' Time of Discovery in the Discovered Objects view” on page 89

◆ “Object Details and Maps not showing the real-time environment” on page 89

◆ “Paths shown in maps do not match the Path Details tab” on page 89

Default value for the UDG refresh periodThe default value for the UDG refresh period to refresh dynamic groups' membership is 15 minutes. Every refresh consumes significant CPU and memory resources. Because of the minor memory leak issue in the UDG refresh process, lowering this value will cause GDPM DM memory usage to increase. This will therefore degrade system performance, scalability, and availability. For small to medium-scale systems, the 15-minute default value is fine, and will not impact performance. For large scale systems, however, the recommendation for optimal performance is to set the refresh period to 30 minutes. Based on current memory leak analysis, increasing the refresh period to 30 minutes will double the lifetime of the GDPM DM.

Discovery status permanently stays in running stateFollow the procedure given below:

1. SSH to SCA and log in.

2. Verify that all services are running as expected by typing the following command:

sm_service show

Note: The sm_service show command shows all services that are running. All other services except Path_Starter must be running.

3. Use the dmctl geti command to determine if you can get instances from the DM by typing the following commands. In this example, the commands attach you to the Path DM:

dmctlattach path

Troubleshooting user interface conditionsUsing SNMP 85

Troubleshooting

getiThe geti command retrieves discovery instances known to the Path DM. This command may hang with the Path DM.

If the command hangs on Path DM, it is an indication of deadlock on DM processes that needs to be reported. If not, then it indicates a different error and the logs for UI and DMs need to be handed over to developers for troubleshooting.

Discovery status: One or more element discoveries failedThe status may not reflect an accurate count of discovered elements, which could be related to failure of event subscriptions. Determine if the point of failure lies with the SCA application or the provider.

1. Verify that all SCA services are running by entering the following command:

sm_service show

2. Check the Path DM log as well as the logs for the Host, SAN, and Array DMs. Look for the following strings to see if something has failed:

errorexceptionfailasl

3. The sm_service show command shows all services run status. Except 'Path_Starter', all other services must be running.

Discovery status: No elements detectedFollow the procedure given below:

1. Check the Path DM log as well as the logs for the Host, SAN, and Array DMs. Look for the following strings to see if something has failed:

errorexceptionfailasl

Table 5 on page 92 provides a list of log files to check.

2. Verify that the provider is up and running.

3. Ping the Cisco or provider switch from the SCA Telnet utility.

Out of memory errors: The user interface hangs, stalls, or slows downIf you are actively using the same web browser session for 3 hours or longer, you may notice that the UI starts to run slower, and buttons may disappear or hang. This may be due to the browser sessions's Out Of Memory condition, and such delays depend on the level of activity or scale of data managed by the application.

When there is an Out Of Memory condition, the following exceptions can be found in the Java Console:

java.lang.OutOfMemoryError: Java heap space with pollingjava.lang.OutOfMemoryError: Java heap space


Troubleshooting

In order to view the Java Console, click on the Java icon located on your system's taskbar.

To overcome this issue:

◆ Regularly close browser and reopen the application in a new browser at your convenience.

◆ Using your operating system's Java Control Panel, increase the browser memory for the Java process to a minimum of 256 MB, and maximum of 1 GB.

Example To increase the browser memory on Windows XP:

1. Open the Windows Control Panel (Start > Settings > Control Panel).

2. Double-click on the Java icon within the list. This will open the Java Control Panel.

3. Click the Java tab.

4. In the Java Applet Runtime Settings field, click the View button. (This will open the Java Runtime Settings dialog box.)

5. Type -Xmx1024m -Xms256m in the Java Runtime Parameters field.

Note: These instructions may vary for different operating systems.

UI logs for troubleshootingIt is helpful to collect logs of UI activity when troubleshooting UI behavior. There are two sources that log UI activity:

◆ Java console in the browser for the client side

◆ Tomcat logs for the server side

To obtain client logs from the Java console:

1. Start the browser.

2. From the Internet Explorer Tools menu, select Sun Java Console to start the Java console.

3. For Firefox, select Java Console from the Tools menu.

4. Browse to the appliance and use the SCA as you would under normal operations, navigating to the trouble spot. The console records all activity from the browser client as you work.

5. When you reach the trouble source, examine the console log for errors and exceptions. Click Copy to copy the log contents from the Java console.

To check the server logs from the Tomcat server, go to the following locations and check the UI logs for errors and exceptions:

/opt/apache-tomcat-5.5.25/logs


Troubleshooting

Unable to open UI Browser to the applianceIf you have problems browsing to the appliance:

1. Ensure that the URL is correct.

2. Verify that you are using a supported browser with a supported version of JRE.

EMC Ionix Storage Configuration Advisor Support Matrix provides a list of supported browsers.

EMC Ionix Storage Configuration Advisor Installation Quick Reference Guide provides the supported JRE versions.

Unable to see any data in the UI even after creating profiles and policiesIf unable to see any data:

1. Verify that all DMs are running and alive by typing all of the following commands. Each command returns a DM-specific instance:

dmctl --broker=<brokerhost> --server=path geti CMP_AccessProfile

dmctl --broker=<brokerhost> --server=array1 geti EMC_SDMStorageArray

dmctl --broker=<brokerhost> --server=san1 geti EMC_SDMPhysicalConnectivityDevice

dmctl --broker=<brokerhost> --server=host1 geti EMC_SDMHost

If the DMs are functioning properly, then each command returns data.

2. Verify the UI logs for domain disconnect or lost phrases to look for any DM connections failure.

3. If the network connection is up and running, click Refresh the view to force the UI to retrieve data again. If possible, restart the Tomcat server.

4. If data does not appear in the UI, check the logs located in the /opt/DMT/local/logs directory in the appliance for any errors in restoring data.

“Using discovery logs” on page 92 provides more information on checking log files.

Progress bar for loading data hangs for a long time in any viewIf queries for getting data are run for a long time or if the DMs are not responsive, the progress bar in the UI tends to hang. If this happens, you can try any of the following:

◆ Ensure that all DMs are running and alive (Step 1 on page 88).

◆ Check for 'DM disconnect' statements in UI logs. ““UI logs for troubleshooting” on page 87 provides instructions on how to do this. Consider restarting the Tomcat Server.

◆ If the DMs are responsive, wait for the queries to finish. This may take a long time but they should finish eventually. If the queries are running, you will observe 100 percent CPU utilization. This indicates that the queries are getting data.


Troubleshooting

Unable to sort or filter by 'Last Successful' Time of Discovery in the Discovered Objects viewThis is a known issue for which there is no workaround.

Object Details and Maps not showing the real-time environmentThis may be due to a lag in discovery or rediscovery policy schedules. Rerun the policies to show the live data.

Paths shown in maps do not match the Path Details tabSometimes, the paths displayed in maps do not match the paths in the Path Details tab. This behavior could be due to the following reasons:

1. If this behavior pertains to a Windows host with PowerPath, the pseudo devices will not show the links through all the initiators; it just shows through a single initiator. To overcome this issue, use the Host Path Details tab to see all the paths by selecting the device.

2. For hosts with multipathing, if all of the paths from an array to devices are up and running, then they will be displayed correctly. If a path from an array to a device goes down, and then the host is rebooted, the path should no longer be displayed. However, the path is still displayed in this scenario and therefore the user cannot know for sure whether the path is really down or not.


Troubleshooting

Useful commands and utilitiesThe following sections describe utilities and commands that may be useful when troubleshooting problems and issues with the SCA.

UtilitiesTable 3 on page 90 provides two useful utilities.

CommandsTable 4 on page 90 provides a list of useful commands. You must be logged in to the appliance and use them from a command line in the appliance.

Table 3 Useful utilities

To Use More information about the utility

SSH to the SCA Putty PuTTY is a shareware Telnet/SSH client.

Transfer files between a Windows machine and the appliance

WinSCP WinSCP is a Windows freeware SFTP and FTP client.

Table 4 Useful commands

To Use

Show status of all required SCA services sm_service show

Stop service sm_service stop <service name>

Start service sm_service start <service name>

Start tomcat (UI and compliance engine) service service tomcat start

Stop tomcat (UI and compliance engine) service service tomcat stop

Start sybase database service service sybase start

Stop sybase database service service sybase stop

Start discovery service service ic-serviced start

Stop discovery service service ic-serviced stop

Reboot SCA Reboot.sh

List details of all processes ps -ef | more

Save list of running processes ps -ef > scaProcesses.txt

Collect memory and thread usages in all Domain Managers

ps -eo thcount,rss,vsz,pid,cmd | grep sm_server > dm_info.txt

List files with timestamp ls -lt | more


Troubleshooting

Collect TCP connections between all processes. Redirect output to a file for easy analysis.

netstat -p

List CPU/memory usage top

Collect the version of the installed RME build conary q | grep rme > rme_installed.txt

Table 4 Useful commands (continued)

To Use

Troubleshooting user interface conditionsUseful commands and utilities 91

Troubleshooting

Using discovery logsKey logs related to discovery issues are stored in /opt/DMT/local/logs. These logs show discovery progress and any issues. In general, look for the following strings:

◆ ERROR

◆ EXCEPTION

◆ FAIL

◆ ASL-ERROR

Table 5 on page 92 lists and describes the logs that you can use in troubleshooting discovery issues.

All log files are named as follows:

<DM name>.log

where <DM name> is the name of the Domain Manager. If you have renamed the DMs, the logs will always bear the name of the DM.

Table 5 Domain Manager logs

Log Description

Translator.log Translate end-to-end path.

san1.log Switch discovery log.

path.log Task execution.

indications.log Provider event indications.

gdpm.log This log file collects the information related to gdpm domain manager. This will show when the last time the gdp/udg data was saved to the gdpm RPS file.

host1.log Lists Host discovery log.

array1.log / array2.log a Lists Array discovery log.

sm_trapd.log Cisco traps.

discovery-service.log Discovery Services log.

AMSDataManager Lists all logs from AMS Data expiration service.

Path_Java Lists Java logs from all the services (discovery service, task manager, task scheduler, scheduler, AMSDataManager, and so on).

Scheduler Lists logs from the scheduler service.

TaskManager Lists logs from the task manager.

TaskScheduler Lists logs from the task scheduler.

a. Load balancing that has been introduced that evenly divides the number of arrays discovered in a discovery policy, across both the DMs. This is reflected in the data contained within array1.log and array2.log.


Troubleshooting

Sending logs and repository files to Customer SupportZip the directories in Table 6 on page 93.

Table 6 Logs and repository files for diagnosis

Directory Description

/opt/DMT/local/logs Discovery logs; core file is indication of a service component crash.

/opt/DMT/local/repos Repository files that contain details of discovered data

/opt/apache-tomcat-5.5.25/logs GUI internals

/opt/DMT/local/logs/logs Task manager and task scheduler logs

Troubleshooting user interface conditionsUsing discovery logs 93

Troubleshooting

Rediscovery scenarios for user-defined groupsAn object such as an array or switch may belong to more than one user-defined group. Similarly, a user-defined group may belong to more than one rediscovery policy. Thus there are scenarios where the same object—an array or switch, for example—is part of multiple rediscovery policies. The system handles this scenario as follows:

◆ Assume user-defined group A (UDG A) contains several children UDGs, and a storage array belongs to each of these children UDGs. When the rediscovery policy executes for UDG A, it will create discovery tasks for all the unique members. Duplicate rediscoveries are therefore avoided.

◆ Assume there are two separate UDGs: UDG A and UDG B. A storage array belongs to each of them. When the rediscovery policy executes for each UDG, duplicate discovery tasks are created for the array. However, one discovery task will run, and the other will fail, stating that the object is already being discovered.


Troubleshooting

Re-imaging the applianceTo re-image your appliance, you need the installation DVD or ISO image of the DVD. Contact your EMC Customer Service Representative.

Acquire network settings and log inBefore switching on the appliance, obtain the following required network information for your site:

◆ IP Address of the appliance

◆ Network mask

◆ Default Gateway

◆ Primary DNS

◆ Hostname

If you are required to replace the SCA hardware appliance, follow the steps in the “Removing and replacing the appliance” section of the EMC Ionix Storage Configuration Advisor Hardware Replacement Guide.

Follow these steps to re-image the SCA software:

1. Insert the software DVD (or ISO image burned to a DVD), into the DVD driver and turn on the appliance.

2. When the Interface window appears, as shown in Figure 7 on page 95, select the To install or upgrade in Graphical mode, and then press Enter.

Figure 7 Interface window

Troubleshooting user interface conditionsRe-imaging the appliance 95

Troubleshooting

The Network configuration window appears as shown in Figure 8 on page 96.

Figure 8 Network configuration window

3. Make sure the following default values appear in Miscellaneous Settings:

Gateway - 1.0.0.2

Primary DNS - 1.0.0.3

4. In the Network Devices box, in the Network Configuration window, clear eth1, eth2, and eth 3, and make sure that eth0 is selected.

5. Select manually and type the fully qualified hostname.

Note: The network configuration can also be done at a later stage after installing the appliance; so you can skip the steps below for network configuration and directly proceed to step 10 on page 97 .The network configuration can be done, after installation, by executing the script itcaseConfig.sh located at opt/emc/itcase

6. Click Edit.The Edit Interface eth0 pop-up dialog box appears as shown in Figure 9 on page 97.


Troubleshooting

Figure 9 Edit Interface eth0 pop-up

7. Select Activate on boot and provide the IP Address and Netmask information

8. Click OK. The dialog box disappears and displays the Network Configuration window as shown in Figure 8 on page 96

9. Update the hostname, Gateway, and Primary DNS values

10. Click Next to display the Time Zone Selection window as shown in Figure 10 on page 97.

Figure 10 Time zone selection


Troubleshooting

11. Follow the directions in the left panel of the Time Zone selection window to restore time zone information for your site, and then click Next to begin the software installation. “Linux-based time zones” on page 99 gives information on selecting your relevant Linux-specific time zone.

12. An Installing Packages progress window appears. When the software installation is complete, reboot, and then log in to the appliance home page, http:// <appliance_IP>/sca and change default password to your previously used admin password. Initial login password is ChangeMe.

13. Proceed to restore your data to the new appliance. “Restore repositories” on page 49 provides information.

Changing the time zoneIf a time zone is typed incorrectly, you can change the existing time zone.

To change time zone settings:

a. Type nlclockcfg --getzone <timezone> to view a list of time zones.

Note: To view active time zone, type nlclockcfg --listzones.

Note: You can also view list of supported time zones as shown in “Linux-based time zones” on page 99.

b. Reboot the appliance after changing the time zone.


Troubleshooting

Linux-based time zones The following two tables list standard Linux time zones. Select the correct time zone for your site.

Africa America America America/US/Chile/Mexico Australia/Brazil/Canada

Africa/BrazzavilleAfrica/AsmaraAfrica/AlgiersAfrica/MaputoAfrica/El_AaiunAfrica/AsmeraAfrica/BanjulAfrica/NdjamenaAfrica/BujumburaAfrica/MbabaneAfrica/LuandaAfrica/TunisAfrica/KinshasaAfrica/OuagadougouAfrica/BlantyreAfrica/NouakchottAfrica/BissauAfrica/Addis_AbabaAfrica/MonroviaAfrica/KhartoumAfrica/CasablancaAfrica/JohannesburgAfrica/DakarAfrica/AccraAfrica/DoualaAfrica/DjiboutiAfrica/LubumbashiAfrica/Sao_TomeAfrica/CeutaAfrica/MogadishuAfrica/NairobiAfrica/NiameyAfrica/FreetownAfrica/WindhoekAfrica/LagosAfrica/ConakryAfrica/TimbuktuAfrica/LibrevilleAfrica/BamakoAfrica/HarareAfrica/CairoAfrica/GaboroneAfrica/BanguiAfrica/MaseruAfrica/AbidjanAfrica/LomeAfrica/KampalaAfrica/KigaliAfrica/TripoliAfrica/Dar_es_SalaamAfrica/LusakaAfrica/Malabo

America/St_LuciaAmerica/MendozaAmerica/Rio_BrancoAmerica/CuiabaAmerica/ScoresbysundAmerica/Thunder_BayAmerica/ParamariboAmerica/Rainy_RiverAmerica/TegucigalpaAmerica/Rankin_InletAmerica/MartiniqueAmerica/TorontoAmerica/LimaAmerica/CuracaoAmerica/Glace_BayAmerica/GrenadaAmerica/HalifaxAmerica/El_SalvadorAmerica/BelizeAmerica/ShiprockAmerica/GuadeloupeAmerica/MenomineeAmerica/Coral_HarbourAmerica/JujuyAmerica/GuyanaAmerica/RecifeAmerica/Porto_AcreAmerica/Porto_VelhoAmerica/Campo_GrandeAmerica/Fort_WayneAmerica/JamaicaAmerica/St_JohnsAmerica/New_YorkAmerica/MontserratAmerica/RosarioAmerica/BarbadosAmerica/MaceioAmerica/MontevideoAmerica/EdmontonAmerica/Mexico_CityAmerica/DetroitAmerica/ThuleAmerica/GodthabAmerica/CaracasAmerica/St_VincentAmerica/ArubaAmerica/GuatemalaAmerica/VirginAmerica/TortolaAmerica/NassauAmerica/BoiseAmerica/Boa_Vista

America/FortalezaAmerica/PangnirtungAmerica/IndianapolisAmerica/DanmarkshavnAmerica/CaymanAmerica/Swift_CurrentAmerica/St_ThomasAmerica/CayenneAmerica/Buenos_AiresAmerica/CordobaAmerica/ChicagoAmerica/La_PazAmerica/WhitehorseAmerica/ReginaAmerica/Knox_INAmerica/IqaluitAmerica/MazatlanAmerica/PanamaAmerica/HermosilloAmerica/HavanaAmerica/LouisvilleAmerica/MiquelonAmerica/InuvikAmerica/ChihuahuaAmerica/PhoenixAmerica/ManausAmerica/AsuncionAmerica/CatamarcaAmerica/YellowknifeAmerica/CancunAmerica/AtikokanAmerica/EirunepeAmerica/AnchorageAmerica/AdakAmerica/Costa_RicaAmerica/AtkaAmerica/Dawson_CreekAmerica/NoronhaAmerica/JuneauAmerica/Cambridge_BayAmerica/NipigonAmerica/TijuanaAmerica/MonctonAmerica/MonterreyAmerica/AraguainaAmerica/BogotaAmerica/Goose_BayAmerica/Port_of_SpainAmerica/MontrealAmerica/WinnipegAmerica/Los_AngelesAmerica/Resolute

America/Grand_TurkAmerica/Puerto_RicoAmerica/AnguillaAmerica/AntiguaAmerica/ManaguaAmerica/St_KittsAmerica/GuayaquilAmerica/MeridaAmerica/BahiaAmerica/NomeAmerica/DenverAmerica/EnsenadaAmerica/Santo_DomingoAmerica/SantiagoAmerica/YakutatAmerica/BelemAmerica/VancouverAmerica/DawsonAmerica/DominicaAmerica/Sao_PauloAntarctica/SyowaAntarctica/RotheraAntarctica/South_PoleAntarctica/VostokAntarctica/DavisAntarctica/DumontDUrvilleAntarctica/PalmerAntarctica/McMurdoAntarctica/CaseyAntarctica/MawsonArctic/LongyearbyenUS/MichiganUS/HawaiiUS/PacificUS/SamoaUS/AleutianUS/CentralUS/AlaskaUS/EasternUS/ArizonaUS/MountainChile/ContinentalChile/EasterIslandMexico/BajaNorteMexico/BajaSurMexico/General

Atlantic/FaroeAtlantic/St_HelenaAtlantic/CanaryAtlantic/StanleyAtlantic/Jan_MayenAtlantic/South_GeorgiaAtlantic/Cape_VerdeAtlantic/ReykjavikAtlantic/AzoresAtlantic/BermudaAtlantic/MadeiraAtlantic/Faeroe

Australia/ACTAustralia/CurrieAustralia/SouthAustralia/NorthAustralia/DarwinAustralia/NSWAustralia/WestAustralia/VictoriaAustralia/YancowinnaAustralia/Broken_HillAustralia/EuclaAustralia/MelbourneAustralia/LHIAustralia/QueenslandAustralia/AdelaideAustralia/LindemanAustralia/HobartAustralia/PerthAustralia/CanberraAustralia/Lord_HoweAustralia/SydneyAustralia/BrisbaneAustralia/Tasmania

Brazil/DeNoronhaBrazil/WestBrazil/AcreBrazil/East

Canada/NewfoundlandCanada/PacificCanada/SaskatchewanCanada/CentralCanada/YukonCanada/EasternCanada/MountainCanada/Atlantic


Troubleshooting

Europe India/Misc areas Asia Asia Pacific

Europe/VolgogradEurope/MoscowEurope/KievEurope/ParisEurope/ChisinauEurope/CopenhagenEurope/MonacoEurope/BudapestEurope/GibraltarEurope/AthensEurope/SimferopolEurope/DublinEurope/LjubljanaEurope/BelgradeEurope/ViennaEurope/San_MarinoEurope/LondonEurope/OsloEurope/IstanbulEurope/RigaEurope/PodgoricaEurope/TiraspolEurope/BrusselsEurope/HelsinkiEurope/TiraneEurope/VilniusEurope/ZurichEurope/JerseyEurope/BratislavaEurope/TallinnEurope/BucharestEurope/GuernseyEurope/NicosiaEurope/SkopjeEurope/WarsawEurope/ZagrebEurope/MariehamnEurope/LuxembourgEurope/Zaporozhye Europe/BerlinEurope/UzhgorodEurope/Isle_of_ManEurope/LisbonEurope/MinskEurope/VaduzEurope/AndorraEurope/SofiaEurope/RomeEurope/KaliningradEurope/MaltaEurope/StockholmEurope/MadridEurope/SarajevoEurope/AmsterdamEurope/SamaraEurope/BelfastEurope/VaticanEurope/Prague

Etc/GMT0Etc/UCTEtc/UTCEtc/ZuluEtc/GreenwichEtc/UniversalEtc/GMT

Indian/ChagosIndian/ChristmasIndian/AntananarivoIndian/ReunionIndian/MayotteIndian/MaheIndian/KerguelenIndian/MauritiusIndian/ComoroIndian/MaldivesIndian/Cocos

Asia/AshkhabadAsia/SeoulAsia/VientianeAsia/ChungkingAsia/MagadanAsia/KamchatkaAsia/QatarAsia/BangkokAsia/ThimbuAsia/Phnom_PenhAsia/MuscatAsia/AlmatyAsia/TashkentAsia/ManilaAsia/AmmanAsia/AdenAsia/HovdAsia/KatmanduAsia/HarbinAsia/IrkutskAsia/VladivostokAsia/AnadyrAsia/BeirutAsia/ThimphuAsia/IstanbulAsia/UrumqiAsia/SingaporeAsia/Riyadh88AAsia/DushanbeAsia/QyzylordaAsia/ChoibalsanAsia/DiliAsia/JakartaAsia/TokyoAsia/DamascusAsia/Ulan_BatorAsia/OralAsia/Riyadh89Asia/DubaiAsia/ChongqingAsia/CalcuttaAsia/DhakaAsia/Kuala_LumpurAsia/KarachiAsia/BahrainAsia/MacauAsia/Kuwait

Asia/KuchingAsia/SaigonAsia/OmskAsia/BruneiAsia/Riyadh87Asia/MacaoAsia/NovosibirskAsia/TehranAsia/JayapuraAsia/KrasnoyarskAsia/BakuAsia/KabulAsia/YerevanAsia/YekaterinburgAsia/RiyadhAsia/Nicosiasia/PyongyangAsia/BishkekAsia/GazaAsia/ShanghaiAsia/TaipeiAsia/AshgabatAsia/JerusalemAsia/YakutskAsia/MakassarAsia/AqtobeAsia/PontianakAsia/SamarkandAsia/KashgarAsia/DaccaAsia/SakhalinAsia/RangoonAsia/BaghdadAsia/Tel_AvivAsia/Ujung_PandangAsia/UlaanbaatarAsia/TbilisiAsia/Hong_Kong

Pacific/PitcairnPacific/WakePacific/KosraePacific/GuamPacific/Port_MoresbyPacific/HonoluluPacific/TongatapuPacific/GuadalcanalPacific/KiritimatiPacific/TarawaPacific/Pago_PagoPacific/TahitiPacific/GambierPacific/EasterPacific/SaipanPacific/ChathamPacific/ApiaPacific/EfatePacific/RarotongaPacific/SamoaPacific/MajuroPacific/NorfolkPacific/FijiPacific/JohnstonPacific/NiuePacific/KwajaleinPacific/GalapagosPacific/MidwayPacific/TrukPacific/MarquesasPacific/NoumeaPacific/FunafutiPacific/YapPacific/FakaofoPacific/AucklandPacific/EnderburyPacific/WallisPacific/NauruPacific/PalauPacific/Ponape


Documents

EMC IonixTM Storage Configuration Advisor · EMC Corporation Corporate Headquarters: Hopkinton, MA 01748-9103 1-508-435-1000 EMC® IonixTM Storage Configuration Advisor Version 2.0