Professional Documents
Culture Documents
DataSource UserGuide5.1
DataSource UserGuide5.1
NetApp, Inc.
495 East Java Drive
Sunnyvale, CA 94089 U.S.A.
Telephone: +1 (408) 822-6000
Fax: +1 (408) 822-4501
Support telephone: +1 (888) 4-NETAPP
Documentation comments: doccomments@netapp.com
Information Web: http://www.netapp.com
Copyright Copyright © 1994-2009 NetApp, Inc. All rights reserved. Printed in the U.S.A.
information The third-party copyright statements and licenses that apply to open source software components
distributed with the product are contained in the section “Third-Party Copyrights and Licenses.”
No part of this document covered by copyright may be reproduced in any form or by any means—
graphic, electronic, or mechanical, including photocopying, recording, taping, or storage in an
electronic retrieval system—without prior written permission of the copyright owner.
Software derived from copyrighted NetApp material is subject to the following license and
disclaimer:
THIS SOFTWARE IS PROVIDED BY NETAPP “AS IS” AND WITHOUT ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE,
WHICH ARE HEREBY DISCLAIMED. IN NO EVENT SHALL NETAPP BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
NetApp reserves the right to change any products described herein at any time, and without notice.
NetApp assumes no responsibility or liability arising from the use of products described herein,
except as expressly agreed to in writing by NetApp. The use or purchase of this product does not
convey a license under any patent rights, trademark rights, or any other intellectual property rights of
NetApp.
The product described in this manual may be protected by one or more U.S.A. patents, foreign
patents, or pending applications.
Trademark NetApp, the Network Appliance logo, the bolt design, NetApp—the Network Appliance Company,
information Cryptainer, Cryptoshred, DataFabric, DataFort, Data ONTAP, Decru, FAServer, FilerView,
FlexClone, FlexVol, Manage ONTAP, MultiStore, NearStore, NetCache, NOW NetApp on the Web,
SANscreen, SecureShare, SnapDrive, SnapLock, SnapManager, SnapMirror, SnapMover,
SnapRestore, SnapValidator, SnapVault, Spinnaker Networks, SpinCluster, SpinFS, SpinHA,
SpinMove, SpinServer, StoreVault, SyncMirror, Topio, VFM, VFM (Virtual File Manager), and
WAFL are registered trademarks of NetApp, Inc. in the U.S.A. and/or other countries. gFiler,
Network Appliance, SnapCopy, Snapshot, and The evolution of storage are trademarks of NetApp,
Inc. in the U.S.A. and/or other countries and registered trademarks in some other countries. The
NetApp arch logo; the StoreVault logo; ApplianceWatch; BareMetal; Camera-to-Viewer;
ComplianceClock; ComplianceJournal; ContentDirector; ContentFabric; EdgeFiler; FlexShare;
FPolicy; Go Further, Faster; HyperSAN; InfoFabric; Lifetime Key Management, LockVault; NOW;
ONTAPI; OpenKey, RAID-DP; ReplicatorX; RoboCache; RoboFiler; SecureAdmin; Serving Data by
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business
Machines Corporation in the United States, other countries, or both. A complete and current list of
other IBM trademarks is available on the Web at http://www.ibm.com/legal/copytrade.shtml.
Apple is a registered trademark and QuickTime is a trademark of Apple, Inc. in the U.S.A. and/or
other countries. Microsoft is a registered trademark and Windows Media is a trademark of Microsoft
Corporation in the U.S.A. and/or other countries. RealAudio, RealNetworks, RealPlayer,
RealSystem, RealText, and RealVideo are registered trademarks and RealMedia, RealProxy, and
SureStream are trademarks of RealNetworks, Inc. in the U.S.A. and/or other countries.
All other brands or products are trademarks or registered trademarks of their respective holders and
should be treated as such.
NetApp, Inc. is a licensee of the CompactFlash and CF Logo trademarks. NetApp, Inc. NetCache is
certified RealSystem compatible.
Preface ........................................................................................................................ix
NetApp Products.....................................................................................................x
Documentation Set ............................................................................................... xii
Chapter 1 SANscreen Architecture ..........................................................................1
1.1 Overview of Components ................................................................................1
1.2 SANscreen Server and Local Acquisition Unit ................................................3
1.3 Remote Acquisition Unit ..................................................................................3
1.4 SANscreen Client GUI.....................................................................................4
Chapter 2 Installing the Remote Acquisition Unit ..................................................5
2.1 Before You Install the Remote Acquisition Unit...............................................5
2.2 RAU Installation Procedure .............................................................................6
2.3 Verifying the New RAU Service.....................................................................10
2.4 Validating the Installation...............................................................................10
2.5 Uninstalling the Remote Acquisition Unit ......................................................10
Chapter 3 Viewing Acquisition Units ......................................................................11
3.1 The Acquisition Units Screen Described .......................................................11
3.1.1 The Main Acquisition Units Table ........................................................13
3.1.2 The Event Log......................................................................................13
3.2 Operations .....................................................................................................14
3.2.1 Removing an Acquisition Unit ..............................................................14
Chapter 4 Using Data Sources to Discover the SAN.............................................16
4.1 Understanding Data Source Concepts..........................................................17
4.2 Unsupported Configurations..........................................................................18
4.3 Preparation ....................................................................................................18
4.4 The Data Sources Screen Described............................................................19
4.4.1 The Main Data Sources Table .............................................................20
4.4.2 The Event Log Detail Pane ..................................................................22
4.4.2.1 Gathering More Status Information .............................................23
4.4.3 The Devices Detail Pane .....................................................................24
4.4.4 The Changes Detail Pane....................................................................25
4.5 Operations .....................................................................................................26
This user guide assumes knowledge of the basic screen- and table-
handling tools detailed in the SANscreen Service Insight User Guide,
including use of the toolbar to display detail panes.
x ♦ Preface NetApp
Product Name Description
http://now.netapp.com/NOW/knowledge/docs/docs.cgi
User Guide Description of Content
The server receives regular updates regarding SAN changes from the
Local Acquisition Unit (LAU), and from any Remote Acquisition Unit(s)
that are installed (detailed in the next section). These updates are
passed through a secured communication channel.
https://<SANscreen_hostname>:<acquisition_port>
SANscreen Data Sources User Guide Installing the Remote Acquisition Unit ♦ 5
The acquisition port defaults to 443 but may have been changed
during the server installation.
Click Next.
SANscreen Data Sources User Guide Installing the Remote Acquisition Unit ♦ 7
Attribute Used to Configure the…
9. Mark the Start Remote Acquisition Service box to start the RAU;
then, click Finish to end the installation.
SANscreen Data Sources User Guide Installing the Remote Acquisition Unit ♦ 9
2.3 Verifying the New RAU Service
Alternatively, open the command window (Start – Run) and enter the
following command to obtain a list of services:
net start
If you wish to uninstall the RAU, use the Add/Remove Programs feature
from the Control Panel. Then select the SANscreen application for
removal.
You can monitor the status of all running Acquisition Units, including
the Local Acquisition Unit that is installed by default with the
SANscreen server. This chapter describes how to so this, as follows:
• Section 3.1 The Acquisition Units Screen Described
provides an overview of the Acquisition Units screen, and
details the information displayed in that screen.
• Section 3.2 Operations describes the various operations
available from the Acquisition Units screen.
Choose Acquisition Units from the launch menu to open the main
Acquisition Units display:
Look at the main table and verify that the Local Acquisition Unit and
all RAUs are shown, and that they have an OK status. For any other
status, the LAU is not running.
The following fields display in the main table for each Acquisition Unit:
Field Description
Click the Event Log button in the toolbar to display any events and
errors that occurred during the most recent attempt(s) to run the
selected Acquisition Unit. Look at the error message to understand
the cause, or contact the NetApp support team for assistance.
Field Description
This operation removes the Acquisition Unit and all data sources
assigned to it. Use it with caution, and only after the devices
corresponding to the data sources are no longer used in the SAN.
1. Stop all data sources for the Acquisition Unit and remove or
migrate them to another LAU or RAU.
This chapter describes how to add and maintain data sources within
SANscreen. Data sources discover SAN information that is used for
analysis and validation. The chapter is organized as follows:
• Section 4.1 Understanding Data Source Concepts
introduces the concept of a data source.
• Section 4.2 Unsupported Configurations lists device
configurations that cannot be reported by SANscreen.
• Section 4.3 Preparation tells what information you need
to have at hand before proceeding.
• Section 4.4 The Data Sources Screen Described
provides an overview of the data sources screen, and
details the information displayed in that screen.
• Section 4.5 Operations describes the various operations
available from the data sources screen.
• Section 4.6 Adding a Data Source provides detailed
instructions to add a new data source.
• Section 4.7 Editing Data Source Properties tells how to
modify a data source definition.
• Section 4.8 Starting a Data Source tells how to start a
data source.
• Section 4.9 Stopping a Data Source tells how to stop a
data source.
• Section 4.10 Removing a Data Source tells how to
remove a data source after the devices corresponding to
the data source are no longer used in the SAN.
• Section 4.11 Forcing Acquisition tells how to force a
data source to start the acquisition process.
SANscreen Data Sources User Guide Using Data Sources to Discover the SAN ♦ 17
• Polling mode — Used to sample devices regularly for
their status, at some user-configured interval.
4.3 Preparation
For each data source, the specific requirements to define that data
source depend on the vendor and model of the corresponding SAN
device(s). Refer to Chapter 5 for detailed information.
In general, to complete discovery of your SAN you will need a list of
installed RAUs and their device connectivity responsibilities. You will
also need the IP address, user name, and password to access each
of the following:
• SAN switches
Choose Data Sources from the launch menu to open the Data Sources
screen:
The screen contains one main table and several detail panes that are
available through the toolbar:
• The main Data Sources table lists all the registered data
sources. By default, and before any data sources are
added, this list is empty. After you add the first data
source, the list shows the parameters and status of each
data source that is running, across all Acquisition Units.
Refer to page 20 for more information about this table.
SANscreen Data Sources User Guide Using Data Sources to Discover the SAN ♦ 19
• The Changes detail pane applies after you select a
data source in the main table. It lists the SANscreen
changes that resulted from information reported by this
data source. Refer to page 25 for more information about
this table.
The following fields display in the main table for each data source:
Field Description
SANscreen Data Sources User Guide Using Data Sources to Discover the SAN ♦ 21
4.4.2 The Event Log Detail Pane
Click the Event Log button in the toolbar to display the acquisition
history for the selected data source:
The information in the Event Log changes ONLY when a new event
has occurred. The Log does not display the results of every
consecutive session, but shows the event if the status has changed
from Success to Failed or from Failed to Success. For example, in the
following view of the Event Log Detail Pane, Application Insight
Arrays shows two event times, because each time registers a
different status, yet the number of actual polls was 56:
If the Status column in the Event Log detail pane shows a link—
Package Dependency—then there is more information you need to
diagnose the problem. Clicking on this link opens the next view:
SANscreen Data Sources User Guide Using Data Sources to Discover the SAN ♦ 23
1. Click on Knowledgebase. This takes you first to a login
screen and then into the Knowledgebase on the NOW
website, where you are given additional resources to address
the problem:
Click the Devices button in the toolbar to display details about the
devices on which the data source reports. Each row in the Devices
table represents a single SAN device.
Field Description
Field Description
SANscreen Data Sources User Guide Using Data Sources to Discover the SAN ♦ 25
4.5 Operations
See
Action Used to… page
…
Add Data Open a wizard that lets you add a new data 27
Source source.
Edit Data Open a wizard that lets you change the 31
Source parameters of the selected data source.
Remove Remove the selected data source and flag 33
Data all data acquired from this data source as
Source non-current.
Note: Only remove a data source after it is no
longer used. Do not remove a data source
if it is temporarily out of use.
Start Data Start the selected data source (applicable 32
Source only if the data source is Stopped).
Stop Data Stop the selected data source (applicable 32
Source only if the data source is Running). A
stopped data source does not communicate
with its corresponding device and does not
retrieve SAN data.
Force Force the selected data source to initiate a 34
Acquisition data acquisition, thereby ensuring that the
most recent data has been acquired.
Clear Event Clear the event log for the selected data 35
Log source.
Crawl With Solve communication problems between the —
Data selected data source and a SAN device.
Source Only use this option upon request by the
NetApp support team.
Manage Launch the management console/interface —
for the selected data source.
SANscreen Data Sources User Guide Using Data Sources to Discover the SAN ♦ 27
1. Enter a name for the data source that is unique across all
Acquisition Units. Choose a name that will make it easy for you
to identify the data source. The name is comprised of
alphanumeric characters (a-z, A-Z, 0-9). No symbols can be
used; the field will change to red if the name is not correct.
2. Choose the Acquisition Unit where the data source will run (local
specifies the Local Acquisition Unit on the SANscreen server).
4. Click Next to open the License Information view, which lets you
select which license packages you want to activate for the data
source. The following is a sample—each data source will have
different packages from which it is capable of collecting related
information:
SANscreen Data Sources User Guide Using Data Sources to Discover the SAN ♦ 29
6. Fill in the information requested by the configuration screen.
Definitions are provided in Chapter 5 in tables that
accompany each data source.
7. Click Finish when you are through, to activate the data source
in your environment. (SANscreen activates the Finish button
after all required fields are filled in, assuming there are no
invalid field values.)
NOTE: The Import button is used only upon request by the NetApp
support team.
After you complete the configuration, a new row displays in the main
table of the data sources screen. Proceed as follows to verify the
new data source:
3. Click Next.
5. Click Finish.
SANscreen Data Sources User Guide Using Data Sources to Discover the SAN ♦ 31
4.8 Starting a Data Source
This operation removes the data source and all entities it reported on
during the most recent acquisition (volumes, zones, connectivity,
etc.). For this reason, you should use this operation with caution, and
only after all devices corresponding to the data source are no longer
used in the SAN.
NOTE: If a second data source reports on one or more of the
same entities, they are not removed.
One exception exists to this rule, and that is the devices on which the
data source reported. These are not removed, but are grayed out in
the topology view and tables, marking them as inactive. Use the
Delete Inactive Device option to remove them, as necessary. This is
described in the SANscreen Service Insight User Guide.
SANscreen Data Sources User Guide Using Data Sources to Discover the SAN ♦ 33
etc.), as detailed in the SANscreen Service Insight User
Guide.
After completing this process, the event log will contain only the most
recent two entries.
If the following dialog appears when you click Finish from a wizard:
SANscreen Data Sources User Guide Using Data Sources to Discover the SAN ♦ 35
The operation failed because you are not an authorized user for the
requested operation. You must have administrative privileges in
order to work with data source configurations.
You can:
• Ignore the error and keep working with your current
privilege level.
• Log in under a user name that has administrative
privileges and try again.
If the Acquisition Unit Status field contains an error message in the main
Data Sources table (i.e., is not OK), make sure the Acquisition Unit is
running. For example, a Not Connected status indicates that the
software is not running.
To verify that the service is running, open the Services window on the
server where the Acquisition Unit was installed (on the SANscreen
server for a Local Acquisition Unit):
2. Recheck the status of the data source in the main table. The
status should change to OK.
SANscreen Data Sources User Guide Using Data Sources to Discover the SAN ♦ 37
Chapter 5: Available Data Sources
This chapter lists the various SAN devices and management stations
from which an installed management agent can communicate with a
SANscreen data source. For each such device, it tells how to
configure the corresponding data source to acquire SAN data from
the device.
The devices are listed alphabetically according to their Vendor and
Model.
The 3Par InServ is an SMI-S device. When you select this data
source, you need only identify the server itself. All the other fields are
set correctly by SANscreen.
Field Descriptions
Field Descriptions
Field Descriptions
Poll interval Interval, in minutes, at which the data source should poll
(min) the device.
Use HTTPS Check the box if HTTPS is desired.
SNMP SNMP read-only community string used to access the
Community device.
Fabric name Fabric name to be reported by this data source (blank to
report the fabric WWN).
Exclude devices Comma-separated list of Brocade devices, identified by IP
address, that will not be discovered by this data source.
Field Descriptions
Field Description
NOTE: The API, CLI, HTTP and SMI-S are fabric aware, and the two
SNMP data sources are not fabric aware.
Field Description
Field Descriptions
Field Descriptions
Field Descriptions
Field Descriptions
This is a generic database data source that can query any database
to attach host names to HBA WWNs. To change the data source
parameters, please update the XML configuration file with any
specific database information. This data source instance is
preconfigured with ECC database query information.
Field Descriptions
Field Description
ECC server Network address for the Enterprise Control Center (ECC)
server, specified as an IP (nnn.nnn.nnn.nnn format), or as
a hostname that can be resolved through DNS.
Poll interval (min) Interval, in minutes, at which the data source should poll
the device.
ECC port Number of the ECC server port through which the data
source acquires information.
User name Name used to log in to the ECC.
Password Password used to log in to the ECC.
Before configuring this data source, make sure the Server is installed
locally on the target device.
For an EMC Symmetrix device, make sure that SYMCLI with CLI
Performance (with appropriate version) is installed and has the
appropriate license to operate. SANscreen communicates with the
Symmetrix device using this CLI.
Before configuring this data source, make sure the Server is installed
locally on the target device.
Field Descriptions
Field Descriptions
Field Descriptions
Before configuring this data source, make sure the SSSU command
utility is available. The version number of the SSSU must match that
of the HiCommand server being accessed by the data source.
Field Descriptions
Field Description
Before configuring this data source, make sure the SSSU command
utility is available. The version number of the SSSU must match that
of the HiCommand server being accessed by the data source.
Before configuring this data source, make sure the SSSU command
utility is available. The version number of the SSSU must match that
of the HiCommand server being accessed by the data source.
Field Descriptions
Before configuring this data source, make sure the CV CLI is installed
on the target device.
Field Descriptions
Field Description
Field Descriptions
Field Descriptions
Before configuring this data source, make sure IBM’s ESS CLI is
installed on the target device.
Field Descriptions
The IBM SVC is an SMI-S device. When you select this data source,
you need only identify the server itself. All the other fields are set
correctly by SANscreen.
Field Descriptions
Refer to the screen(s) shown above for default values.
Field Description
Field Descriptions
Field Descriptions
Field Descriptions
Field Descriptions
Field Descriptions
Field Descriptions
The SUN StorEdge 6x20 is an SMI-S device. When you select this
data source, you need only identify the server itself. All the other
fields are set correctly by SANscreen.
Field Descriptions
Field Description
Poll interval (min) Interval, in minutes, at which the data source should poll
the device.
SMI-S port Number of the server port through which the data source
acquires information.
User name Name used to log in to the SMI-S server.
Password Password used to log in to the SMI-S server.
Protocol used HTTP (if unsecured access) or HTTPS (if secured access).
User name Name used to log in to the SMI-S server.
Password Password used to log in to the SMI-S server.
SMI-S SMI-S namespace used to query the data (always interop).
namespace
The SUN StorEdge 6x20 is an SMI-S device. When you select this
data source, you need only identify the server itself. All the other
fields are set correctly by SANscreen.
6.2.1 Prerequisites
Install SMI-S provider on each EMC Solutions Enabler host for each
Solutions Enabler on which you would like to collect Array
Performance statistics.
Before configuring this data source, make sure the Server is installed
locally on the target device.
For an EMC Symmetrix device, make sure that SYMCLI with CLI
Performance (with appropriate version) is installed and has the
appropriate license to operate. SANscreen communicates with the
Symmetrix device using this CLI.
Before configuring this data source, make sure the Server is installed
locally on the target device.
Field Descriptions
6.3.1 Prerequisites
6.3.4 Limitations
The following data source views are configured for EMC CLARiiON.
Field Descriptions