Apt Are

APTARE StorageConsole Data Collector
Installation Guide for Capacity Manager

7.2
Copyrights and Trademarks
Copyright © 2007-2009 APTARE, Inc., All rights reserved.
The information contained in this book is subject to change without notice.
Reproduction, adaptation or translation without prior written permission is prohibited,
except as allowed under the copyright laws.
APTARE® and StorageConsole® are registered trademarks of APTARE, Inc. and/or its
affiliates in the U.S. and certain other countries.
HP Data Protector is a trademark of HP.
Hitachi is a trademark of Hitachi Data Systems.
Acrobat and the Acrobat logo are trademarks of Adobe Systems Incorporated.
Microsoft, Microsoft Windows and Microsoft Internet Explorer are registered
trademarks of Microsoft Corporation in the United States and/or other countries.
Macintosh, Mac, Apple, Safari, and Mac OS are trademarks of Apple Computer, Inc.,
registered in the U.S. and other countries.
EMC NetWorker is a registered trademark of EMC Corporation.
NetBackup and Backup Exec are registered trademarks of Symantec Corporation.
NetApp, Data ONTAP, SnapVault, SnapMirror, and FlexVol are registered trademarks
of NetApp, Inc.
VMware is a registered trademark of VMware, Inc.
Other company and product names mentioned herein can be trademarks or registered
trademarks of their respective companies and should be treated as such.
Publication Change Record

The following table records all revisions to this publication. This first entry is always
the publication’s initial release. Each entry indicates the date of the release and the
number of the system release to which the revision corresponds.
Doc ID Date System Release
MK-97APT022-01 March 2008 APTARE StorageConsole, 6.5
May 2008 APTARE StorageConsole, 6.5.23
June 2008 APTARE StorageConsole, 6.5.24
October 2008 APTARE StorageConsole, v6.6
December 2008 APTARE StorageConsole, v6.6 Service Pack 1
April 2009 APTARE StorageConsole, v7.0
September 2009 APTARE StorageConsole, v7.1
November 2009 APTARE StorageConsole, v7.2
Copyrights and Trademarks iii

iv APTARE StorageConsole Data Collector Installation Guide for Capacity Manager
Contents
Preface 1
About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Contacting APTARE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Introduction to Data Collection 1
Data Collection Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Architecture Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Pre-Installation Setup 7
Before You Install Data Collectors . . . . . . . . . . . . . . . . . . . . . . .7
Planning Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
Planning Worksheets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Capacity Manager Supported Configurations . . . . . . . . . . . . . . . . 11
Capacity Manager Data Collector Requirements . . . . . . . . . . . . . 11
Supported Hardware, Software, Storage Arrays (Capacity Manager) . . 11
IBM Storage Arrays and Their Counterparts . . . . . . . . . . . . . . . 14
Pre-Requisites: Storage Arrays and Host Resources . . . . . . . . . . . . 15
Overview of the Installation Steps . . . . . . . . . . . . . . . . . . . . . . 18
Updating the Local Hosts File . . . . . . . . . . . . . . . . . . . . . . . . 19
Configuring Data Collector Policies in the Portal. . . . . . . . . . . . . . . 20
Capacity Manager for Hitachi . . . . . . . . . . . . . . . . . . . . . . . . 21
Capacity Manager for IBM 3000 & 4000 Series . . . . . . . . . . . . . . . 26
Capacity Manager for IBM 6000 & 8000 Series . . . . . . . . . . . . . . . 31
Capacity Manager for EMC CLARiiON. . . . . . . . . . . . . . . . . . . . 36
Capacity Manager for EMC Symmetrix . . . . . . . . . . . . . . . . . . . 40
Capacity Manager for NetApp . . . . . . . . . . . . . . . . . . . . . . . . 45
Capacity Manager for Host Resources. . . . . . . . . . . . . . . . . . . . 49
Probe Schedule Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Data Collector Installation 63
Installing the WMI Proxy Service (Windows Host Resources only) . . . . . 63
Installing the Data Collector . . . . . . . . . . . . . . . . . . . . . . . . . 67
Installing from the Data Collector CD . . . . . . . . . . . . . . . . . . . 67
Installing via the Internet . . . . . . . . . . . . . . . . . . . . . . . . . 68
GUI Deployment of the Data Collector . . . . . . . . . . . . . . . . . . 70
Console Installation Instructions . . . . . . . . . . . . . . . . . . . . . 73
Validating the Data Collector Installation 79
Validating the Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . 79
List Data Collector Configurations . . . . . . . . . . . . . . . . . . . . . . 82
Example Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Starting the Data Collector 85
Data Collector Manual Startup . . . . . . . . . . . . . . . . . . . . . . . . 85
Un-installing the Data Collector 87
Un-install the Data Collector on UNIX . . . . . . . . . . . . . . . . . . . . 87
Un-install the Data Collector on Windows . . . . . . . . . . . . . . . . . . 88
Appendix A - Troubleshooting 89
Verify the Data Collector Configuration . . . . . . . . . . . . . . . . . . . 90
Check the Configuration File . . . . . . . . . . . . . . . . . . . . . . . 90
Typical Host Resources Troubleshooting Sequence. . . . . . . . . . . . . 91
Host Resources: Check the Status of the WMI Proxy Server . . . . . . . . 92
Host Resources: Post-Installation Verification . . . . . . . . . . . . . . . . 94
Host Resources: Verify Connectivity . . . . . . . . . . . . . . . . . . . . . 95
Host Resources: Check Host Connectivity Using Standard SSH . . . . . 95
Host Resources: Check Host Connectivity . . . . . . . . . . . . . . . . 97
1
Host Resources: Check Host Connectivity for the Host Resources
Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Host Resources: Generating Host Resource Configuration Files . . . . . . 99
Host Resources: Check the Execution of a Command on a Remote Server .
100
Host Resources Data Collection . . . . . . . . . . . . . . . . . . . . . . 100
Host Resources: Collection in Stand-Alone Mode . . . . . . . . . . . . . 101
Configuring Parameters for SSH . . . . . . . . . . . . . . . . . . . . . 101
2 APTARE StorageConsole Data Collector Installation Guide for Capacity Manager

Preface
Chapter0
About This Book

This document provides detailed step-by-step instructions for the installation of the
APTARE Data Collector for Capacity Manager. This install guide is valid for Portal
version 6.5 onward.
This document assumes either:
• The Portal has already been successfully installed in your enterprise, and that the reader of
this document is aware of the password for the StorageConsole admin user (e.g.
admin@yourdomain.com). This is referred to as an IN-HOUSE installation. Or,
• The Portal, hosted by APTARE or a third-party service provider, will serve as your portal.
This option typically applies only to evaluation or hosted customers and is referred to as a
HOSTED installation.
Separate instructions are provided as necessary for Windows and UNIX.
Contacting APTARE
If at any time during the install you encounter a problem, or if you simply want to verify
a step or have a question about the installation, please contact the APTARE Customer
Care Group which will be happy to assist you:
Technical Support: Sales:

Customer Care Group • sales@aptare.com or
• support@aptare.com or • 1 866-9-APTARE, Option
#2
• 1-408-871-9848
• 1-866-9-APTARE, Option #1, 6:30am - 5:30pm
Pacific Time
About This Book 1

1
Application Administrator’s Guide
Introduction to Data Collection

Chapter0
This chapter covers the following topics:

• Data Collection Overview
• Architecture Overview
Data Collection Overview

The Data Collector is a centralized and remotely managed data collection mechanism.
This Java application is responsible for interfacing with backup servers and storage
arrays, gathering information related to storage backup and recovery, and capacity
management.
The Data Collector continuously collects data and sends this data, using an http or https
connection, to another Java application, the Data Receiver. The Data Receiver runs on
the Portal Server and stores the data that it receives in the Reporting Database. When
you use the Portal to generate a report, the Portal requests this information from the
Reporting Database, then returns the results in one of the many available reports.
The Data Collector obtains all of its monitoring rules from a Data Collector
Configuration File. This file resides in the Reporting Database in XML format. When
the Data Collector first starts, it downloads this file from the Reporting Database. The
Data Collector uses this file to determine the list of backup servers, hosts, or storage
arrays that are to be monitored and included in its data collection process. For details on
how host names are processed, see “Host Name Processing - Filters and Aliases” in
Application Administrator’s Guide.
Data Collector Terminology

Data Collector - This software component interfaces with each of the supported
backup and recovery software systems to extract meta-data about the underlying
backup and recovery environment. For example, data can include backup job details
and tape inventory information. In the case of Capacity Manager, the Data Collector
communicates with the storage arrays in your SAN (Storage Area Network).
Data Collection by Backup Product

The following collection mechanisms are used for the particular backup products:
• EMC NetWorker - The Data Collector uses the Networker administration command-line
utilities, such as mminfo, nsradmin, and nsrinfo.
• IBM Tivoli Storage Manager - The Data Collector interfaces with TSM using the TSM
utility, dsmadmc, collecting data from the underlying TSM databases, including TSM
Archives for LAN-free backups.
Data Collection Overview 1

• Symantec Backup Exec - The Data Collector uses database commands to obtain
information from each Backup Exec server.
• HP Data Protector - The Data Collector communicates with the Cell Manager—the
server that runs session managers and core software to manage the backup details in the
HP Data Protector IDB database.
• Generic Backup Data - APTARE StorageConsole Backup Manager can report on data
from backup products that are not native to StorageConsole—such as PureDisk,
BakBone, and BrightStor. Using the backup vendor’s export feature, create a comma-
separated values (CSV) file. The StorageConsole Data Collection process will import the
data into the Portal database.
Note: Veritas NetBackup is the only backup product that does not require a Data Collector
because an agent is used to obtain information from NetBackup.
Data Collection by Storage Array

• Capacity Manager - The Data Collector communicates with the storage array’s system
service processor (SSP) and hosts to gather storage capacity data.
Data Collector Server - This is the physical server on which the Data Collector is
installed. It can be any server within your network that is Java 1.5 compatible.
For Backup Manager, where you install the Data Collector depends on your backup
solution. NetBackup is the only backup solution that requires that the Data Collector
reside on each Master Server. For all other backup solutions, the Data Collector can run
on a standalone server, the Portal Server, or any Backup Server.
In the case of Capacity Manager, the Data Collector can run on a stand-alone server or
the Portal server. In some cases—such as EMC Symmetrix arrays—the Data Collector
must reside on the system that is running the SAN management software.
A single installation of the Data Collector supports any number of servers. The only real
limitation is the memory and CPU processing power of the server on which the Data
Collector resides.
Planning Data Collector Deployment

In most cases, a single instance of the Data Collector can support any number of backup
servers or storage arrays. However, each environment has its own unique deployment
configuration requirements, so it is important to understand where the Data Collector
software must be installed so that you can determine how many Data Collectors must be
installed and which servers are best suited for the deployment.
Use the following guidelines to plan the installation of Data Collectors.
Note: A single Data Collector can be installed, for multiple backup and storage products.
During the Data Collector installation/configuration, the configuration choices include:
VERITAS NetBackup, IBM Tivoli Storage Manager, or All Others (which currently includes
the backup products: Backup Exec, HP Data Protector, EMC Networker; and the capacity/
storage products: EMC, Hitachi, IBM, NetApp, Host Resources; and VMware)
Backup Manager:
• One Data Collector for each of these backup products: NetBackup and Tivoli Storage
Manager (TSM)

• One Data Collector can be used to include all of these backup products: EMC NetWorker,
Symantec Backup Exec, HP Data Protector, and Generic Backup products. And, you also can
include storage arrays in this Data Collector.
Capacity Manager:
• A single Data Collector can include all supported storage types—EMC, NetApp, IBM, or
Hitachi. In fact, this single Data Collector can be used for backup products and storage
arrays. See the notes earlier in this section.
• Host Resources do not require a dedicated Data Collector for each resource. If you have a
Storage Array Data Collector, the Host Resources collector is inherently part of that Data
Collector. However, if for some reason, you do not have a Storage Array Data Collector, you
can install a Host Resources Data Collector independently.
Virtualization Manager:
• This Data Collector policy can be incorporated with an existing Data Collector Policy. A
Data Collector can collect data from Virtual Center (vCenter) or from specific ESX servers
that are not managed by vCenter.
Replication Manager:
• This Data Collector policy is configured as part of the NetApp storage data collector.
Data Collection Overview 3

Architecture Overview
Capacity Manager provides end-to-end storage capacity reporting from the hosts to the
storage arrays. The Data Collector is a software component that is responsible for
interfacing with one or many storage arrays for information related to the capacity
management environment. In most cases, the Data Collector software module can
reside on any server within your network that is Java 1.5 compatible and, where
applicable, has a working copy of specific storage array command line utilities already
installed. The exception is EMC Symmetrix, which requires the Data Collector to reside
on the server that manages the arrays.
The following diagram illustrates how the Capacity Manager Data Collector could be
deployed in your environment:
Capacity Manager
Figure 1.1 Data Collector for Capacity Manager

The Data Collector obtains all of its monitoring rules from a configuration file
maintained in the database. This file is called the Data Collector Configuration File and
is stored in the database in XML format. When the Data Collector is first started, it
downloads the Data Collector Configuration File from the database. The Data Collector
uses this file to determine the list of storage arrays that are to be monitored and included
in its data polling.
In most cases, a single instance of the Data Collector can support any number of storage
arrays. The only real limitation is the memory and CPU processing power of the server
on which the Data Collector resides.
For each storage array, the Data Collector will establish connections to the database.
The Data Collector Configuration file contains all the connection information for each
server including such parameters as the hostname / IP address of the server.

The Data Collector communicates with the storage array’s system service processor
(SSP) to gather storage capacity data. The information is then sent via http(s) to the
Portal. Users can then access the Portal via a web browser.
Architecture Overview 5
2
Pre-Installation Setup
Chapter1
This chapter covers the following topics:

• Before You Install Data Collectors
• Planning Guidelines
• Planning Worksheets
• Capacity Manager Supported Configurations
• Supported HBAs
• HBA Pre-Requisites
• Pre-Requisites: Storage Arrays and Host Resources
• Overview of the Installation Steps
• Updating the Local Hosts File
• Configuring Data Collector Policies in the Portal
• Capacity Manager for Hitachi
• Capacity Manager for IBM 3000 & 4000 Series
• Capacity Manager for EMC CLARiiON
• Capacity Manager for EMC Symmetrix
• Capacity Manager for NetApp
• Capacity Manager for Host Resources
• Probe Schedule Examples
Before You Install Data Collectors

In preparation for Data Collector installation, you will need to take the steps described
in this chapter.
Note: These steps apply only if you are performing an IN-HOUSE installation. If a third-party
service provider is hosting your Portal—that is, a HOSTED installation (perhaps for a product
evaluation)—skip this section and contact your hosting organization’s representative to
configure the hosted portal for your Data Collector.
Before You Install Data Collectors 7

Planning Guidelines
Use the guidelines in this section, along with the accompanying worksheets to gather
the configuration information required for Data Collection deployment. This is a 2-step
process.
• First, you’ll identify where the Data Collectors will be installed.
• Then, you’ll determine what Data Collection Policies must be configured via the Portal.
Where to Install
Use the following guidelines to plan the installation of Data Collectors. Then, complete
the Planning Worksheets with the details.
• A single Data Collector can be installed for multiple backup and storage products.
• Host Resources do not require a dedicated Data Collector for each resource. If you have a
Storage Array Data Collector, the Host Resources collector is inherently part of that Data
Collector. However, if for some reason you do not have a Storage Array Data Collector, you
can explicitly install just a Host Resources Data Collector.
Which Policies Are Needed

Policies need to be configured via the Portal to establish communication with the
installed Data Collectors.
The following example illustrates a typical deployment:

In this example of 100 UNIX servers:
• 50 servers will have only capacity information collected
• Another 50 servers will have capacity information collected, plus some of those servers
will also have Host Resources data collected:
• 5 Memory
• 2 Network
• 1 Oracle Server
Planning Guidelines 9
Planning Worksheets
Use the following worksheets to gather the configuration information required for Data
Collection deployment. See Pre-Requisites: Storage Arrays and Host Resources for
additional details.
IMPORTANT: The EMC Symmetrix Data Collector needs to be installed on the
server(s) that manage the Symmetrix arrays.
Storage Array Details: [List all storage arrays for which you want to collect data.]
Device Data
# Storage Array Storage Array Storage Array Manager Collector
Type Name IP Address Server Server IP
(Hitachi) Address
Example Hitachi HD1000 203.23.10.10 203.23.10.1 203.23.10.5
Storage
Array
1
2
3
4
5
6
7
8
9
10
11
12
Host Resources Details:[List all storage arrays for which you want to collect data.]
Storage
# Host Array IP User ID OS Applications/Databases
Name Address
Example kiwi 203.23.10.10 Admin AIX Oracle
Host
1
2
3
4
5
6
7
8
9
10
11

Capacity Manager Supported Configurations
Capacity Manager Data Collector Requirements
Capacity Manager requires a user to have the following privileges:
• On UNIX, root privileges for SSH and Telnet
• On Windows, administrator privileges for WMI.
Note: The operating system and application commands that the data collector must run to determine
the underlying storage details, require root and administrator privileges. The HBA vendors required
this level of access for their APIs.
Supported Hardware, Software, Storage Arrays (Capacity Manager)

The following table lists the hardware and software supported by Capacity Manager data collector.
The Host Resources components are supported on the following operating systems. In general,
APTARE supports these operating systems up to and including the latest OS patch level.
• Red Hat Linux Enterprise Server 4.0 or 5.0
• Solaris 8, 9, 10 (SPARC ONLY)
• Windows 2000 Server and Advanced Server and Windows 2003
Operating • IBM AIX
Systems • HP-UX
• SUSE
Note: The WMI Proxy Server must be deployed on a Windows Server. You can use the same
server as the Data Collector, if it is a Windows Server. The WMI Proxy Server uses port 1248 to
communicate with the Data Collector.
A Data Collector can be configured to gather data from:
Applications
• Microsoft SQL Server 2005
(Host
• Microsoft Exchange Server 2003 (but not Exchange Server 2007, as it does not support WMI)
Resources)
• Oracle 10g
• Veritas Volume Manager 5.0 and 5.1 (Supported operating systems: RedHat Linux, Solaris,
AIX, HP-UX)
• Solaris Volume Manager
Volume • Linux Logical Volume Manager
Managers • AIX Logical Volume Manager
• HP-UX Logical Volume Manager
Note: Besides Veritas Volume Manager, each of the operating systems comes with its own
built-in logical volume manager, hence no specific version numbers are mentioned.
• SVM (Solaris Volume Manager) Metastat
• AIX 5.2, 5.3 JFS and JFS2, including correlation of the filesystem to the SAN disks
File Systems • Solaris ZFS
• SUSE SLES 9 & 10, 32 & 64 bit REISER FS and EXT3 and Logical Volume Manager (LVM
and LVM2)
Clustering technologies—both active-active and active-passive clusters—are supported by
Clustering Capacity Manager. Clusters are listed as “Related Hosts” in Portal reports. This relationship is
established when the data collector finds multiple servers accessing the same storage.
Table 2.1 Capacity Manager Supported Hardware, Software, and Storage Arrays
Capacity Manager Supported Configurations 11

• EMC PowerPath
Multi- • Hitachi Dynamic Link Manager (HDLM)
pathing • Symantec Dynamic Multi Pathing (DMP)
• Device Mapper Multipath for Linux
Hitachi Universal Storage Hitachi Device Manager (HDvM), 5.5+, 6.0+, 6.1+, 6.2+
Platform V
TagmaStore AMS
TagmaStore Network
Storage Controller
TagmaStore USP
Hitachi TagmaStore WMS
Lightning 9900 V Series
Thunder 9500 V Series
XP512/48
XP1024/128
XP12K/10K/SVS200
HP HP StorageWorks XP Hitachi Device Manager (HDvM), 5.5+, 6.0+, 6.1+, 6.2+
FAS6000 Series Data ONTAP, versions 7.2+
FAS3100 Series
NetApp
FAS3000 Series
FAS2000 Series
N Series Data ONTAP, versions 7.2+
Storage
Storage Systems: IBM Storage Manager CLI:
Arrays and
DS3300 • 3K series: 02.70.G5.15 & above
Interfaces
DS3300 Express Model 72 • 4K/5K series: 10.10.G5.05 & above
IBM DS3300 Models 80 & 88
DS3400 • 6K/8K series: DSCLI 5.2.2.272 & above
DS4700 Express Model 70
See IBM Storage Arrays and Their Counterparts.
DS5000 Series
DS6000
DS8000
LSI 1532, 1932, 3992, IBM Storage Manager CLI:
3994, 6994, 6998, 7900 • 3K series: 02.70.G5.15 & above
LSI
• 4K/5K series: 10.10.G5.05 & above
• 6K/8K series: DSCLI 5.2.2.272 & above
StorageTek 9900 Series Hitachi Device Manager (HDvM), 5.5+, 6.0+, 6.1+, 6.2+
StorEdge T3
IBM Storage Manager CLI:
Sun StorageTek 2510, 2540, • 3K series: 02.70.G5.15 & above
6140
• 4K/5K series: 10.10.G5.05 & above
• 6K/8K series: DSCLI 5.2.2.272 & above
Table 2.1 Capacity Manager Supported Hardware, Software, and Storage Arrays

Supported HBAs
HBA Pre-Requisites
• Windows: Either fcinfo, scli, or hbacmd (required for both LUN Mapping and HBA
data collection).
• Linux: scli or hbacmd (required only for HBA information)
• Solaris: scli or hbacmd (required only for HBA information)
• HP-UX: fcmsutil (used only for HBA information; should already be installed by
default)
EMULEX Supported Adapters (using either EMULEX Storport Miniport

v1.03 or later, or SCSIport Miniport v5.10a10 or later):
LP8000; LP8000DC; LP850; LP9002L; LP9002DC; LP9402DC; LP952L;
LP9802; LP9802DC; LP982; LP10000; LP10000DC; LP1050; LP1050DC;
LP10000Ex; LP101
LSI Logic Corp Supported Adapters (using Storport Miniport driver

Host Bus 1.20.01.09 or above):
Adapters LSI40919H, LSI40919LH, LSI40919O, LSI40919LO, LSI44929H,
LSI44929LH, LSI44929O, LSI44929LO, LSI7102XP-LC, LSI7202XP-LC and
(Windows) LSI7402XP-LC
QLOGIC Supported Adapters (using driver version 8.2.3.x or 9.1.x.x or

above):
QLA2300; QLA2340; QLA2342; QLA2344; QLE2360; QLE2362; HP
QLA2340; IBM HS20; HP QLA2342; HP QLA2312; Intel SBFCM-2312;
QMC2342; QUANTA-QLA2312; HP QLA2312; HP QLA2312; HP QLA2312;
HP A6826
• Capacity Manager obtains the HBA information using operating system
Host Bus commands such as luxadm.
Adapters
(Solaris) • In addition, product-specific commands (Emulex and QLogic) are used. See
models listed in Host Bus Adapters (Windows).
Host Bus • Capacity Manager obtains the HBA information using operating system
Adapters commands, looking for specific operating system files and directories.
(RedHat • In addition, product-specific commands (Emulex and QLogic) are used. See
Linux) models listed in Host Bus Adapters (Windows).
Host Bus • Capacity Manager obtains the HBA information using operating system
Adapters commands.
(AIX and • No product-specific commands are used; therefore, Capacity Manager
HP-UX) supports all HBAs supported by these operating systems.
Capacity Manager Supported Configurations 13

IBM Storage Arrays and Their Counterparts
The LSI-based arrays include IBM DS/ESS and Sun StorageTek series, as well as SGI
InfiniteStorage and Teradata Storage Systems.
IBM Arrays Sun Arrays LSI

Storage System DS3300 Sun StorageTek 2510 LSI 1532
Express Model 70
Express Model 72
Storage System DS4800 Model 80 Sun StorageTek 6540 LSI 6998
Storage System DS5000 Series Sun StorageTek 6780 LSI 7900

Pre-Requisites: Storage Arrays and Host Resources
Use the following table to identify the pre-requisite information and configuration for
each Data Collector that you will be installing.
The Data Collector access methods vary, depending on the storage array, as shown in
the following table.
Table 2.2 Capacity Manager Data Collector Access Methods
Storage Array/ Access Methods and Pre-Requisites

Host Resources
Hitachi Device • Data Collector makes XML API calls over HTTP to retrieve array data.
Manager • Identify the name of the Hitachi Device Manager server.
• Ensure that port 2001 is open.
• Use the Admin username and password for accessing the Hitachi Device Man-
ager.
IBM • IBM SMCLI—verify that SMCLI is installed on the Data Collector server.
Subsystem • Location of the SMCLI:
(3000 & 4000
Series) UNIX: /opt/SM8/client/
Windows: C:\Program Files\SM8\client\
IBM • IBM DSCLI—verify that DSCLI is installed on the Data Collector server.
Enterprise • Location of the DSCLI:
(6000 & 8000
Series) UNIX: /opt/ibm/dscli
Windows: C:\Program Files\IBM\dscli
• Locate the profile file, typically in the /profile sub-directory and named
dscli.profile. In this file, un-comment the Output Format property and set it to
XML, as shown in the following example.
# Output format type for ls commands, which can take one of the following
values:
# default: Default output
# xml : XML format
# delim : delimit columns using a character specified by "delim"
# stanza : Horizontal table format
# "format" is equivalent to option "-fmt default|xml|delim|stanza".
format: xml
• A User account with monitor group privileges on the array is required.
Pre-Requisites: Storage Arrays and Host Resources 15


Host Resources
EMC • NaviSecCLI communicates with NaviSphere Manager—therefore, verify that
CLARiiON NaviSecCLI is installed on the Data Collector server.
Storage Array
• Get the IP address or host name for each storage array.
• By default, port 443 is used; however, a different port number can be config-
ured, as shown in the following format.
<ip address>:portnumber
• Create a view-only user ID and password for CLARiiON NaviSuite.

EMC • SymCLI
Symmetrix • Run symcfg discover to discover all the EMC Symmetrix storage arrays on the
Storage Array
network and build a Symmetrix configuration database.
• Sample commands:
Symcfg list –v
Symcfg –sid ARRAYID list -dir all -address
IMPORTANT: The EMC Symmetrix Data Collector needs to be installed on

the server(s) that manage the Symmetrix arrays.
• Ensure that it is configured to enable management of the Symmetrix storage arrays for
which you want to collect data (no user ID or password is required).
NetApp Use an existing NetApp user or create one with the necessary privileges to access
Storage the application programming interface (API):
• login-http-admin
• api-*
Typically, the root, admin user has all the capabilities, but it is not advisable to use
root or admin passwords.
Creating a NetApp User with API Privileges

To create a new user, with the required privileges, on a NetApp system, use the
following CLI steps:
filer> useradmin role add apirole -a login-http-admin, api-*
filer> useradmin group add apigroup -r apirole
filer> useradmin user add apiuser -g apigroup


Host Resources
Host Resources Verify Connectivity to Hosts
• Use the stand-alone hostvalidate utility to verify host connectivity and to execute
probes that will be used by the Data Collector. This tool validates login credentials and
probes Windows servers with WMI and Unix servers with ssh/telnet (or an access
control command, like sudo).
The hostvalidate utility installs and then un-installs the WMI Proxy for the purpose of
validating probes. For details, see the Capacity Manager Host Resource Validation
Utility document.A WMI Proxy is required for collecting from Windows hosts, once
actual data collection is configured and initiated. See Windows Requirements below.
• See Host Resources: Check Host Connectivity Using Standard SSH in the Capacity
Manager Data Collector Installation Guide.
Windows Requirements
• To collect data from Windows hosts, choose a Windows host on which to install the
WMI proxy. If the Data Collector is on a Windows server, then the proxy will be
installed there by default. If the Data Collector is on a UNIX server, then find a
Windows machine on which to install it. Note the IP address of this server—the one on
which the WMI proxy resides—as you will use it during the Portal configuration
process.
Note: When installing the WMI proxy, if the installer detects that you do not have
Microsoft .NET already installed on the host, it will notify you of this required
dependency. When you acknowledge this prompt, the installer will install .NET for you.
Microsoft .NET contains several necessary libraries.
• WMI uses DCOM for networking and DCOM dynamically allocates the port numbers
for clients. DCOM’s service runs on port 135 (a static port) and any client
communicating with a host connects on this port. Then, the DCOM service allocates the
specific port for the WMI service. For additional information, see http://
msdn.microsoft.com/en-us/library/ms809327.aspx.
• All Windows hosts require a user ID with administrative privileges.
• Windows hosts that have a Host Bus Adapter (HBA) may need to have fcinfo installed.
Fcinfo is used to determine LUN mappings. If fcinfo is not installed, either QLogic
CLIs or Emulex CLIs are used to collecting HBA ports or LUNs. If none if these access
methods obtains data, the host-to-array relationship cannot be determined and the LUNs
will be displayed as DAS drives.
You can download fcinfo software from: http://www.microsoft.com/downloads/
details.aspx?FamilyID=73d7b879-55b2-4629-8734-b0698096d3b1&displaylang=en
• Create a list of the name or IP address for each host for which you want to collect data.
UNIX Requirements
• ssh or telnet is enabled.
• root user ID and password—Note that super-user root privileges are required.
APTARE StorageConsole also supports sudo, sesudo, and pbrun. If using any of
these, ensure that the user ID has sudo, sesudo, or pbrun privileges.
Pre-Requisites: Storage Arrays and Host Resources 17

Overview of the Installation Steps
Use the following checklist to ensure that you complete each step in the order indicated.
Note: Each item in this checklist corresponds to a section in this document that contains the
step-by-step instructions.
Update the Local Hosts File

• This enables Portal access.
Portal Configuration
Add Data Collector Policies for connecting to storage arrays, hosts, and
applications:
• Hitachi
• IBM
• EMC CLARiiON
• EMC Symmetrix
• NetApp
• Host Resource
Install the Data Collector on the Data Collector Server(s)
• You’ll need to install a data collector for each array type for which you will
be collecting data.
IMPORTANT: The EMC Symmetrix Data Collector needs to be
installed on the server that manages the Symmetrix arrays.
Install the WMI Proxy Service on one of the Windows hosts, if
you are collecting data from Windows hosts
• If you installed the Data Collector on a Windows server, the WMI Proxy was
installed along with the Data Collector installation, so you can skip to the
validation step.
• This step is only required if you are collecting data from Windows Host
Resources and the WMI Proxy needs to be installed on only one Windows
host.
Validate the Installation

Updating the Local Hosts File
1. Add the Portal IP Address to the Local Hosts file on the Data Collector Server or on any
available client with web-browsing capabilities.
Note: Only edit the local hosts file if a DNS entry hasn’t already been set up in your
enterprise to resolve both http://aptareportal.yourdomain.com and http://
aptareagent.yourdomain.com to the Portal IP address.
a. Login to the Data Collector Server.
b. On a UNIX server:
vi /etc/hosts
Add entries for aptareportal.yourdomain.com and aptareagent.yourdomain.com,
both resolving to the Portal server IP address.
On a Windows server:
edit C:\Windows\System32\drivers\etc\hosts
Add entries for aptareportal.yourdomain.com and aptareagent.yourdomain.com,
both resolving to the Portal server IP address.
Updating the Local Hosts File 19

Configuring Data Collector Policies in the Portal
Before installing the Data Collector software, you must create data collection policies
via the Portal.
For Capacity Manager, there are a number of storage array and host resources options:
• Capacity Manager for Hitachi
• Capacity Manager for EMC CLARiiON
• Capacity Manager for EMC Symmetrix
• Capacity Manager for NetApp
• Capacity Manager for Host Resources

Capacity Manager for Hitachi
The key parameters that the Data Collector uses to connect to the data source are
contained in Data Collector Policies. These policies are maintained via the Portal and
stored in the database. Prior to installing the Data Collector, you must create and
configure a new policy. Once the Data Collector is installed, you can create additional
policies.
When you configure a Data Collector Policy in the Portal, you first create a Data
Collector folder and then add policies to it. A single Data Collector can be installed for
multiple backup and storage products. During the Data Collector installation/
configuration, the configuration choices include: VERITAS NetBackup, IBM Tivoli
Storage Manager, or All Others (which currently includes the backup products: Backup
Exec, HP Data Protector, Legato NetWorker, Generic Backup products; and the
capacity/storage products: EMC, Hitachi, NetApp, IBM, Host Resources; and
VMware).
The process for creating a policy is described below:
1. Login as an Admin user.
The Admin user ID and password was specified during the Portal installation.
2. In the Portal toolbar at the top of the window, select:
Admin Æ Data Collector Policies
You can use this Data Collector Administration window either to declare a new Data
Collector or to add policies to an existing Data Collector.
Capacity Manager for Hitachi 21

3. If adding a new data collector, in the Data Collector Administration window, click Add to
display the Data Collector properties window, as shown below.
4. Create a relevant Collector Name and Passcode, to be used when accessing the Data
Collector that you are configuring.:
Field Description Sample Values
Collector Name* A unique name assigned to this Data Collector. BUEdc1
The Data Collector will use this value for LEGdc1
TSMdc1
authentication purposes. HRdc1
Passcode* A passcode assigned to this Data Collector. It can Password1
be any character sequence.
Note: Unlike other StorageConsole passwords (which
are encrypted and then saved) this Data Collector
passcode is not encrypted prior to saving in the
StorageConsole database and may appear as clear case
in certain files. It simply is intended as a “handshake”
identification between the data collector and the policy.
Short Notes Descriptive notes associated with this Data
Collector

Auto-upgrade Indicate if you want this configuration file
aptare.jar upgraded automatically.
This part of the data collector is responsible for
event and metadata processing threads.
bootstrap.jar upgraded automatically.
This data collector component is responsible for
the portal version, watchdog daemon, and health
of the system.
Once you have added the initial Data Collector information, you will configure the policy
by adding Product Policies, as described in the next step.
5. Step 1 – Select Product Type—in this case, Hitachi Data Systems— and then click Add.
6. Step 2 – Specify Data Collector Properties.
Note: You can add additional Collector Policy records upon completing the setup of this
record.

Add or select the parameters. Mandatory parameters are denoted by an asterisk (*):
Field Description Sample Value
Domain The domain identifies the top level of your server group yourdomain
hierarchy. The name was supplied during the installation
process. All newly discovered servers are added to the root
server group associated with this domain. Typically, only
one Domain will be available in the drop-down list.
If you are a Managed Services Provider, each of your

customers will have a unique domain with its own server
group hierarchy.
To find your Domain name, in the menu list at the left of

the Portal window, click on the Server Groups arrow to
expand the list. Then, click on the first folder in the Server
Groups list. This folder will have a Group ID of 100000.
User Id* Use the User ID and passcode for accessing the Hitachi Administrator
Device Manager. This typically would be an administrator
privilege, but must be a minimum privilege of a view-only
use
Password* Note: The password is encrypted prior to saving in the Password1
database and is never visible in any part of the application.
Hitachi device The address of the Hitachi Device Manager Server— hds_server1
manager server* either the IP address or server name
Schedule For example: */30 * * * *
*/30 * * * * means every 30 minutes

*/20 9-18 * * * means every 20 minutes between the
hours of 9am and 6pm
*/10 * * * 1-5 means every 10 minutes Mon - Fri.
See Probe Schedule Examples in the Application

Administrator’s Guide for additional details.
To test this connection: A Hitachi Device Manager XML API is used to obtain data,
connecting via:
http://serverAddress:2001/service/ServerAdmin
where:
serverAddress as configured for the Hitachi device manager server above

2001 the default port number allocated to this server
Click OK to save the Policy and return to the Data Collector Administration window where
the Policy will be listed. From here you can add an additional Policy record (for example, if
the data collector needs to communicate with other Servers), or make changes to the Policy
you just created.

7.

Capacity Manager for IBM 3000 & 4000 Series
Capacity Manager supports the following IBM storage arrays.

Express Model 70
Express Model 72
policies.
VMware).

Capacity Manager for IBM 3000 & 4000 Series 27

TSMdc1
Collector

of the system.
5. Select the Product Type—IBM Subsystem—and then click Add.
Enter or select the parameters. Mandatory parameters are denoted by an asterisk (*):
process. All newly discovered servers are added to the
root server group associated with this domain. Typically,
only one Domain will be available in the drop-down list.

group hierarchy.

Schedule* For example: */30 * * * *

See Probe Schedule Examples for additional
examples.
IBM SMCLI The location of the SMCLI executable, for example:
client software UNIX: /opt/SM8/client/
location *
Windows: C:\Program Files\SM8\client\
Server Address The IP address of the IBM Storage Array

Capacity Manager for IBM 6000 & 8000 Series
Capacity Manager supports the following IBM storage arrays.

Express Model 70
Express Model 72
policies.
VMware).


TSMdc1
Collector

of the system.
5. Select the Product Type—IBM Enterprise—and then click Add.


group hierarchy.


examples.
Profile Name Specify the profile filename, including the absolute path. C:\Program
e.g. Files\ibm\
Windows: C:\Program Files\ibm\dscli\profile\dscli.profile dscli\profile\
UNIX: /opt/ibm/dscli/profile/dscli.profile dscli.profile
UNIX: /opt/
See Pre-Requisites: Storage Arrays and Host Resources ibm/dscli/
for the requirement to set the output format property to profile/
XML. dscli.profile
IBM DSCLI The location of the DSCLI executable, for example:
client software
location * UNIX: /opt/ibm/dscli
Windows: C:\Program Files\IBM\dscli
Server Address Specifies the primary management console IP address or
the host name.
User Id* Specifies the user ID for the account that has monitor Monitor
group privileges on the storage array.
StorageConsole database and is never visible in any part
of the application.

Capacity Manager for EMC CLARiiON
policies.
VMware).

TSMdc1
Collector
Capacity Manager for EMC CLARiiON 37

of the system.
5. Select Product Type—in this case, EMC Clariion—and then click Add.
6. Specify Data Collector Properties.


group hierarchy.

Server address* Enter the CLARiiON storage array’s address. 192.1.1.1:445
Typically, only the IP address is required, which uses
port 443 by default. To change the port that the Data
Collector uses to communicate with the array, use the
format: <IP address>:<port number>
EMC Navi client For example:
software location Unix: /opt/Navisphere/bin
*
Windows: C:\Program Files\EMC\NavisphereCLI\

examples.
User Id* The view-only user ID for CLARiiON NaviSuite. Administrator

StorageConsole database and is never visible in any part
of the application.
Click OK to save the Policy and return to the Collector Configuration window where the
Policy will be listed. From here you can add an additional Policy record (for example, if the
data collector needs to communicate with other Servers), or make changes to the Policy you
just created.
Capacity Manager for EMC CLARiiON 39

Capacity Manager for EMC Symmetrix
IMPORTANT: The EMC Symmetrix Data Collector needs to be installed on the
server(s) that manage the Symmetrix arrays.
policies.
VMware).

Capacity Manager for EMC Symmetrix 41

TSMdc1
Collector

of the system.
5. Step 1 – Select Product Type—in this case, EMC Symmetrix— and then click Add.
6. Step 2 – Specify Data Collector Properties.
:
Field Description Sample

Value

group hierarchy.

Capacity Manager for EMC Symmetrix 43

Field Description Sample
Value
EMC Symmetrix This location refers to the location on the Data
client software Collector.
location * UNIX: /usr/symcli/bin
Windows: C:\Program Files\EMC\symCLI\bin
Schedule * For example: */30 * * * *

Click OK to save the Policy and return to the Collector Configuration window where the
Policy will be listed. From here you can add an additional Policy record (for example, if the
data collector needs to communicate with other Servers), or make changes to the Policy you
just created.

Capacity Manager for NetApp
policies.
VMware).
Capacity Manager for NetApp 45

TSMdc1
Collector

of the system.
5. Select Product Type—in this case, NetApp— and then click Add.
6. Specify Data Collector Properties and click OK.
Capacity Manager for NetApp 47


group hierarchy.

expand the list. Then, click on the first folder in the
Server Groups list. This folder will have a Group ID of
100000.
NetApp address* One or more IP addresses or host names to probe. 192.168.0.1-
Comma-separated addresses or IP ranges are supported. 250,
192.167.1.10,
myhost
Schedule * For example: */30 * * * *


SnapVault Active Check the box if you are collecting data from your
NetApp SnapVault environment.
SnapVault If you checked the SnapVault Active box, you will be
Schedule required to enter a schedule, in the format shown above.
SnapMirror Check the box if you are collecting data from your
Active NetApp SnapMirror environment.
SnapMirror If you checked the SnapMirror Active box, you will be
Schedule required to enter a schedule, in the format shown above.
User id* The view-only user ID for NetApp storage.
Password* The password associated with the User ID.
7.

Capacity Manager for Host Resources
IMPORTANT: Host Resources do not require a dedicated Data Collector for each
resource. If you have a Storage Array Data Collector, the Host Resources collector is
inherently part of that Data Collector. However, if for some reason you do not have a
Storage Array Data Collector, you can explicitly install just a Host Resources Data
Collector—that is, in the following procedure, choose an existing storage array policy
and skip to step 4 to add children.
policies.
VMware).
Capacity Manager for Host Resources 49


TSMdc1
Collector

of the system.
5. Step 1 – Select Product Type—in this case, Host Resource— and then click Add.
6. Step 2 – Configure the Host Resource


group hierarchy.

WMI proxy This is the server address of the WMI proxy, which CorpWin2k
server collects data on Windows hosts.
Enter either the server’s IP address or name.
Note: This address is needed only if you are collecting
data from Windows servers in your environment.
Click Add to launch the Host window where the Host Resource will be listed.
7. Step 3 – Add a Host Policy

Strategies for Adding Hosts
• Group Windows hosts (that are in the same domain) together in one host policy.
• Group UNIX hosts (that have a common user id and password) together in one host
policy.
Configuring a Policy
Policy name* Create a relevant name. Unix_srvrs
Host address* The host IP address or name. Note that hds-sun10
comma-separated addresses and IP
ranges are supported. If you have a large
list of addresses to enter, click Host
Address Editor.
Example of IP Range:
172.16.1.1-250

User id* User ID login to the host root
If the policy includes a group of
Windows hosts, use the Windows
domain user id. This user id must have
administrative privileges.
For UNIX hosts, super user root
privileges are required. You also could
use sudo or pbrun. If using either of
these, ensure that the user ID has sudo or
pbrun privileges.
Access UNIX hosts only: If user id is not root, /usr/bin/sudo
Command provide the full path to access control.
Control Check the checkbox to have the data /user/local/bin/sudo -p
collector use the access command for all Password:
commands.
Note: You can configure sudo to prompt
for a password using a custom prompt (the
default is “Password.” StorageConsole
expects the prompt to be “Password.” If the
hosts have a custom password prompt,
you’ll need to specify -p Password: after
the path to sudo. See the example to the
right.
Windows Windows domain name win2kdomain
Domain If any of the hosts specified in the Host
address field are Windows hosts, you
need to specify the Windows domain
name.
If the host is not a member of a domain,
or to specify a local user account, use a
period (.) to substitute the local host
SSID for the domain.
Password* User password for login to the host. rootpwd
Note: The password is encrypted prior to
saving in the database and is never visible in
any part of the application.
Private Key If you have configured Public Key/ /root/.ssh/id_rsa or C:\
Program Files\Aptare\mbs\
File Private Key between your Data conf\id_rsa
Collector Server and the Hosts you
intend to monitor, use this field to
specify the location of the Private Key
file on the Data Collector Server.

Known Hosts If you have configured Public Key/ /root/.ssh/known_hosts or
File Private Key between your Data C:\Program Files\Aptare\
Collector Server and the Hosts you mbs\conf\known_hosts
intend to monitor, use this field to
specify the location of the Known Hosts
file on the Data Collector Server.
Excludes Host addresses to be excluded, using 172.1.4.1
comma-separated or IP range
Path Provide the path(s) that you want UNIX:
prefixed to the PATH environment /usr/local/sbin:/usr/local/
variable. bin:/sbin:/bin:/usr/sbin:
/usr/bin:/root/bin
Windows:
C:\Program Files\Emulex\
Util\HBAnyware;C:\Program
Files\QLogic\SANSurfer
8. Step 4 – Add Resource Probes

In the Host window, click the Probes tab and select Host and/or Application Probes.

Depending on the Probe, you will supply parameters, as shown in the following table.
Note: All passwords are encrypted prior to saving in the database and they are never visible
in any part of the application.

Probe Type Parameters Description
Capacity Probe schedule* A schedule in cron format; for
example:
*/20 9-18 * * *
which translates to “every 20 minutes
between the hours of 9 a.m. and 6 p.m.”
See Probe Schedule Examples in the
Application Administrator’s Guide for
additional examples.
Oracle Probe schedule A schedule in cron format; for
example:
*/20 9-18 * * *
SID* The system identifier to identify the
database instance.
Port* Database port number; default: 1521
Username* The Oracle user must have the
following role granted:
SELECT_CATALOG_ROLE
To grant this access, use:
GRANT SELECT_CATALOG_ROLE TO ‘user’
where user is the database Username
that you’ll provide here.
Password* Database access password
SqlServer Probe schedule A schedule in cron format; for
example:
*/20 9-18 * * *
Database* The name of the database within the
SQL server.

Instance The system identifier to identify the
SQL server database instance—for
example: BKUPEXEC.
Specify either an instance name or a
port. If an instance name is not
specified, MSSQLSERVER is
substituted.
Port To identify the SQL server instance,
provide either an instance name or a
database port number; for example:
1433.
If a port number is not specified, the
port is determined automatically from
the instance name.
Username* Database access user name
Password* Database access password
Exchange Probe schedule A schedule in cron format; for
example:
*/20 9-18 * * *
Active Directory Host Host name or address
Active Directory Port For example: 389
Active Directory Base The starting point for the Active
DN* Directory. For example:
CN=Services,CN=Configuration,
DC=contoso2003,DC=com
Several tools are available to help you
identify the Base DN:
• Ldp.exe - http://support.microsoft.com/
kb/224543
• adsiedit.msc - http://
technet.microsoft.com/en-us/library/
cc773354(WS.10).aspx
Active Directory User Active Directory User Name
Name This username must have privileges to
search under the base DN within the
Active Directory. Typically, this is an
Administrator.
Password Active Directory Password

Network Probe schedule* A schedule in cron format; for
example:
*/20 9-18 * * *
Process Probe schedule* A schedule in cron format; for
example:
*/20 9-18 * * *
Memory Probe schedule* A schedule in cron format; for
example:
*/20 9-18 * * *
Processor Probe schedule* A schedule in cron format; for
example:
*/20 9-18 * * *
System Probe schedule* A schedule in cron format; for
example:
*/20 9-18 * * *

Probe Schedule Examples
The format for the schedule follows the cron standard:
* * * * *
minutes hours day of month month day of week
Probe Schedule Allowed Values:
Field Allowed Values

minutes 0-59 (0 is “on the hour”)
hours 0-23
day of month 1-31
month 1-12
day of week 0-6 (0 is Sunday)
Special Characters:
• A field may also be an asterisk (*), which means the full
range - i.e., “first” to “last”. However, a * in the minutes
position is not permitted, as this would excessively trigger
the probe—every minute.
• A forward slash (/) can be used to specify intervals.
• Use a dash (-) to specify a range.
Probe Schedule Examples Scheduled Run Time

0 14-15 * * 1 On the hour, every Monday, between 2 and 3pm
Note: A zero in the minutes position denotes the beginning of
the hour.
30 9-13 * * 1-5 9:30, 10:30, 11:30, 12:30, and 13:30, Monday through Friday.
0 */2 * * * To run the probe every 2 hours, put */2 in the hour position.
This schedules the probe at 2am, 4am, 6am, 8am, 10am, 12pm,
2pm, and so on.
*/30 * * * * Every 30 minutes
*/20 9-18 * * * Every 20 minutes between 9 am and 6 pm
*/30 * * * 1-5 Every 30 minutes, Monday through Friday
12*** 2:01 every day
30 9,11 * * * 9:30 and 11:30 every day

3
Data Collector Installation

Chapter2
This chapter includes the instructions for installing the Data Collector on the Data
Collector Server. In addition, if you are collecting data from host resources, you may
need to install the WMI Proxy Service. The WMI Proxy Service is installed by default,
as part of the storage array Data Collector installation on a Windows server.
Installing the WMI Proxy Service (Windows Host Resources only)

To collect data from Windows hosts, choose a Windows host on which to install the
WMI proxy. If the Data Collector is on a Windows server, the WMI Proxy will be
installed there as part of the storage array Data Collector installation. If the Data
Collector is on a UNIX server, you’ll need to identify a Windows server on which to
install the WMI proxy service.
1. Locate the executable on the Portal and copy it to the Data Collector server.
On Windows:
c:\opt\aptare\utils\aptarewmiproxyserver.exe
On UNIX:
/opt/aptare/utils/aptarewmiproxyserver.exe
2. Install Anywhere will prepare to install the Data Collector Software. An Introduction
Dialogue box will outline the installation process.
3. Click Next to view the License Agreement.
Installing the WMI Proxy Service (Windows Host Resources only) 63

4. Read the agreement.
5. Click on the “I accept the terms of the License Agreement” radio button.
6. Click Next to display the window where you will choose the installation folder.
7. Specify the directory where you would like to install the Data Collector software.
Default for Windows: C:\Program Files\Aptare
Default for UNIX: /opt/aptare
Note: Accepting the default path is recommended.
8. Click Next.
9. Verify the pre-installation summary.

10. Click Install to proceed with the installation.
11. If the installer detects that you do not have Microsoft .NET already installed on the server,
it will notify you of this required dependency. Microsoft .NET contains several necessary
libraries.
12. Click OK to enable the installer to proceed with the installation of Microsoft .NET.
The wizard will step you through the process and its progress.
When the WMI Proxy installation completes, the WMIServer will be listed in the Windows
Services list with a Startup Type of Automatic, however, this first time you will need to start
the service from the Services window. Each time you re-start this Windows server, the
proxy services will start automatically.
13. To access the Windows Services list to start the APTARE WMI Proxy Server:
Startup > Control Panel > Administrative Tools > Services
14. The following window will appear when the installation is complete.
Installing the WMI Proxy Service (Windows Host Resources only) 65

15. Click Done to complete the process.

Installing the Data Collector
Follow the steps in the following sections to install the Data Collector on the Data
Collector Server. The particular sequence of instructions depends on your environment.
The majority of installations are initiated from the Data Collector Installation CD,
however, if you are installing remotely or your Portal is being HOSTED by a service
provider, you may need to download the Data Collector software via the Internet.
In addition to the GUI version, the installer supports a console (command line) interface
for UNIX systems that do not have X-Windows installed. You will be directed to the
console interface instructions, if appropriate.
Note: Log in as a Local Administrator in order to have the necessary permissions for this
installation.
Installing from the Data Collector CD

1. Installation should be performed as user root, or as an Administrator user on Windows.
2. Note the Platform/OS of the Data Collector Server on which you want to install the Data
Collector.
3. Mount the APTARE StorageConsole Data Collector CD.
• On Windows:
• ActiveX controls must be allowed.
• The installer should load automatically. If not, navigate to the file CD_DRIVE/
install.htm and open it in a browser and click Start Installer.
• Proceed to GUI Deployment of the Data Collector.
• On UNIX:
If the Data Collector Server has X-Windows:
Open the file CD_DRIVE/install.htm in a browser.
If the Data Collector Server does not have X-Windows:
• Copy the file CD_DRIVE/InstData/{OS}/VM/aptareagentinstall.bin
to a temporary directory on the Data Collector Server.
• Proceed to the Console Installation Instructions.
Installing the Data Collector 67

Installing via the Internet
Follow these instructions if you do not have a CD and you are installing on a Data
Collector Server that has Internet access and a web browser.
Note: If your Data Collector Server does not have Internet access or web browser access—for
example, X-Windows not available), proceed to the next section, Internet Access Not Available
from the Data Collector Server, for the relevant installation steps.
1. Start the web browser on the Data Collector Server.
2. Use the following URL to access the Data Collector installer web page:
http://www.aptare.com/agent71/install.htm
The following web page will be displayed:
3. Click on the Start Installer for <Platform>… button.

4. Proceed to GUI Deployment of the Data Collector.
Internet Access Not Available from the Data Collector Server

Use these instructions if you are installing via the Internet where Internet access is not
available from the data collector server.
1. Note the Platform/OS of the Data Collector Server on which you want to install the Data
Collector.
2. Open a browser on a client with web access (you will download the installer to this client,
and then copy it to the Data Collector Server).
3. Use the following URL to access the Data Collector installer web page:
http://www.aptare.com/agent71/install.htm
The following web page will be displayed:

4. Click on the download link that corresponds to the platform of the Data Collector Server.
5. At the prompt, save the Data Collector Installer to a directory on the client.
6. Copy the Data Collector Installer to the Data Collector Server where the Data Collector is
to be installed.
7. Go to the Data Collector Server and run the installer.
• On Windows:
Execute aptareagentinstall.exe.
• On UNIX:
If the Data Collector Server has X-Windows:
chmod +x aptareagentinstall.bin
sh ./aptareagentinstall.bin –i swing
If the Data Collector Server does not have X-Windows:
• Proceed to the Console Installation instructions.

GUI Deployment of the Data Collector
InstallAnywhere will prepare to install the Data Collector software. After checking the
available disk space and downloading the installer, an introduction dialogue window
outlines the installation process.
1. Review the installation process and click Next.

The License Agreement displays for your acknowledgement.

2. Read the agreement and click the “I accept” radio button and then Next.
The installer will display a window, which prompts you for an Install Folder.
3. Specify the directory where you would like to install the Data Collector software.
Accepting the default paths is recommended.
Windows default directory: C:\Program Files\Aptare
UNIX default directory: /opt/aptare
4. Click Next to display the Pre-Installation Summary.

5. Review the summary and click Install.
6. The dialogue will track the installation as it progresses.
7. A Configuration Settings window will prompt you to select a Data Collection Task. The
configuration choices include: VERITAS NetBackup, IBM Tivoli Storage Manager, WMI
Proxy, All Others (includes WMI Proxy)—which currently includes the backup products:
Backup Exec, HP Data Protector, Legato Networker; and the capacity/storage products:
EMC, Hitachi, NetApp, Host Resources. Using the All Others selection, a single Data
Collector can be installed for multiple backup and storage products on a single server.
Note: When you select a backup product, if you are installing on a Windows server, the WMI
Proxy Server is automatically included with the installation. When you select a storage array,
the Host Resources setup is automatically included in the installation. The WMI Proxy Server
also can be installed individually.
8. When prompted to select a Data Collection Task, select All Others (includes WMI Proxy)
and click Next.
9. The following dialogue captures the configuration settings for your particular environment.

Complete the configuration fields, as described below:
Field Description
Data Collector A unique name assigned to this Data Collector. This is the name
Name that you used during the Pre-Installation setup. The Data Collector
will use this value for authentication purposes.
Password The password assigned to this Data Collector.
Note: The password is encrypted prior to saving in the StorageConsole
database and is never visible in any part of the application.
Data Receiver This is the URL the Data Collector uses to communicate to the
URL Portal server. The format of this URL should be:
http://aptareagent.yourdomain.com
It is similar to the URL you use to access the web-based Portal
(http://aptareportal.yourdomain.com).
IMPORTANT NOTE: Be sure to enter the URL with the prefix
aptareagent and NOT aptareportal!
10. After entering the configuration settings, click Finish.

11. In the Install Complete window, click Done.
The InstallAnywhere portion of the installation is now complete.
12. Continue using the instructions in Validating the Installation.
Console Installation Instructions

Follow these instructions when installing on a UNIX master server that does not have
X-Windows. The Installer will guide you through the sequence of steps to install and
configure the Data Collector. If at any time you need to go back a step, simply type
‘back’ at the prompt.
Note: The StorageConsole Data Collector installer does not support console-based installation
for the Windows operating system.

1. From your telnet session cd to the location where the aptareagentinstall.bin file has been
saved.
chmod +x aptareagentinstall.bin
sh ./aptareagentinstall.bin –i console
2. InstallAnywhere will prepare to install the Data Collector software.

=====================================================
(created with InstallAnywhere by Macrovision)
-----------------------------------------------------
Introduction
------------
InstallAnywhere will guide you through the installation of the APTARE

StorageConsole Data Collector.
It is strongly recommended that you quit all programs before continuing with this
installation.
Respond to each prompt to proceed to the next step in the installation. If you want
to change something on a previous step, type 'back'.
You may cancel this installation at any time by typing 'quit'.
PRESS <ENTER> TO CONTINUE:
3. The License Agreement will be displayed.
License Agreement
-----------------
Installation and use of APTARE StorageConsole requires acceptance of the following

License Agreement:
PLEASE READ THIS SOFTWARE LICENSE AGREEMENT CAREFULLY. BY DOWNLOADING, INSTALLING OR
USING THE SOFTWARE YOU INDICATE ACCEPTANCE OF AND AGREE TO THETERMS AND CONDITIONS OF
THIS AGREEMENT….<etc.>
4. Read the agreement and type Y to accept it.

5. The installer will prompt for the installation location:
Choose Install Folder
---------------------
Where would you like to install?
Default Install Folder: /opt/aptare
ENTER AN ABSOLUTE PATH, OR PRESS <ENTER> TO ACCEPT THE DEFAULT

: /opt/aptare

INSTALL FOLDER IS: /opt/aptare
IS THIS CORRECT? (Y/N): y
6. A Pre-Installation Summary will be displayed.

==================================================
Pre-Installation Summary
------------------------
Please Review the Following Before Continuing:
Product Name:
APTARE StorageConsole
Install Folder:
/opt/aptareagent
Link Folder:
/tmp/install.dir.30662/Do_Not_Install
Product Components:
APTARE StorageConsole Agent,
Help
Java VM Installation Folder:

/opt/aptareagent/jre
Disk Space Information (for Installation Target):

Required: 136,083,162 bytes
Available: 3,786,149,888 bytes
7. The installation process will track the progress:

==================================================
Installing...
-------------
[==================|==================|=============]
[------------------|------------------|-------------]
8. You will be prompted to select a Backup Product.
Enter Backup Product

(Choose the Backup Product for which you want to install the Agent/Data Collector.)

(Required Field)
->1- VERITAS NetBackup

2- IBM Tivoli Storage Manager
3- All Others
ENTER THE NUMBER FOR YOUR CHOICE, OR PRESS <ENTER> TO ACCEPT THE DEFAULT:
:
Note: Enter the number for the Data Collector you are installing. The configuration choices
include: VERITAS NetBackup, IBM Tivoli Storage Manager, and All Others (includes WMI
Proxy)—which currently includes the backup products: Backup Exec, HP Data Protector,
Legato Networker; and the capacity/storage products: EMC, Hitachi, NetApp, Host Resources.
Using the All Others selection, a single Data Collector can be installed for multiple backup and
storage products on a single server.
9. The installer will prompt for the Data Collector Name. This is the ID that will be used on
the Portal side to authenticate the Data Collector. This value should be the same value you
configured on the Portal for the field “ID” during the Pre-Installation step.
Enter Data Collector Name
(Required Field)
Data Collector Name (DEFAULT: ):
10. The installer will prompt for the Data Collector Password. This is the password that will
be used on the Portal side to authenticate the Data Collector. This value should be the same
value you configured on the Portal for the field “passcode” during the Pre-Installation step.
Configuration Settings - 2
--------------------------
Enter Data Collector Password:

(Please enter the Password, which will be used to authenticate the Data
Collector with the Data Receiver)
(Required)
Data Collector Password: password1
11. The installer will prompt for the Data Receiver URL. This is the URL the Data Collector
uses to communicate to the Portal server. This is the URL the Data Collector uses to
communicate to the Portal server. The format of this URL should be:
It is similar to the URL you use to access the web-based Portal (http://
aptareportal.yourdomain.com).
IMPORTANT NOTE: Be sure to enter the URL with the prefix aptareagent and NOT
aptareportal!
Configuration Settings - 3

--------------------------
Enter Data Receiver URL

(Required Field)
Data Receiver URL (DEFAULT: ): http://aptareagent.yourdomain.com
The installer will perform a post-install validation:

The installer will now configure and validate the installation.
This may take a few minutes.
===================================
Installation Complete
-----------------------------------
Congratulations! the APTARE StorageConsole Agent for EMC Legato NetWorker has been
successfully installed to: /opt/aptare
12. Press ENTER to exit the installer.

13. Continue with Validating the Installation.

4
Validating the Data Collector Installation

Chapter2
This chapter includes the instructions for validating the Data Collector installation on
the Data Collector Server.
Validating the Installation

The following directions assume that the Data Collector files have been installed in
their default location:
Windows (C:\Program Files\Aptare) or UNIX (/opt/aptare).
If you have installed the files in a different directory, please make the necessary path
translations as you follow these testing instructions.
Note: Running some of these commands can take up to several hours, depending on the size of
your enterprise.
1. Open a session.
Windows: Open a command prompt window.
UNIX: Open a telnet session logged in as root to the Data Collector Server.
2. Change to the directory where you’ll run the validation script.
Windows: At the command prompt, type:
cd C:\Program Files\Aptare\mbs\bin <enter>
UNIX: In the telnet session, type:
cd /opt/aptare/mbs/bin <enter>
3. Execute the validation script.
Windows: At the command prompt, type: checkinstall.bat <enter>
UNIX: In the telnet session. type: ./checkinstall.sh <enter>
Note: The checkinstall utility performs a high-level check of the installation, including a check
for the domain, server group and URL and database connectivity. For a component check,
specifically for Host Resources, run the hostresourcedetail.sh|bat utility, as described in Host
Resources: Collection in Stand-Alone Mode.
The Java version is --> 1.6.0-b105
Version information for datarcvr, aptare.jar and aptarebootstrap.jar at
http://aptareagent.laurentdroin
datarcvr Version
Version: 6.5.12.01
aptare.jar Version
Validating the Installation 79

Minimum Version: 6.5.12.01
Current Version: 6.5.12.07
Build Number: 05162008-1420
aptarebootstrap.jar Version
Version information for aptare.jar and aptarebootstrap.jar at

/opt/build65/EMC/lib/ on this server aptaredev3.corp
aptare.jar Version
aptarebootstrap.jar Version
Validating aptare.jar Version Compatibility - SUCCESS

Meta Collectors
---------------
1. Meta Collector Id: META_hostResource_10
Product Type: Host Resources
2. Meta Collector Id: META_172.16.1.22_8

Product Type: EMC Storage Arrays
Device to probe: 172.16.1.22
Software Home: /opt/Navisphere/bin
Choose the Meta Collector you want to execute [0 for All, 1 - 2 for
individual Meta Collector]: 1
Checkinstall for Meta Collector --> META_hostResource_10

Attempting to contact URL --> http://aptareagent.laurentdroin/servlet/util - SUCCESS
Validating Server Group Setup - SUCCESS
Validating Job -->
com.aptare.core.hostResource.HostResourceChildThread|172.16.1.13,172.16.1.152|Capacity
- SUCCESS_PERSISTING_HOST_RESOURCE_DETAIL
Validating Job -->
com.aptare.core.hostResource.HostResourceChildThread|172.16.1.13,172.16.1.152|System
Validating Job -->
com.aptare.core.hostResource.HostResourceChildThread|172.16.1.13,172.16.1.152|
Processor

Validating Job -->
com.aptare.core.hostResource.HostResourceChildThread|172.16.1.13,172.16.1.152|Memory
Validating Job -->
com.aptare.core.hostResource.HostResourceChildThread|172.16.1.13,172.16.1.152|Process
Validating Job -->
com.aptare.core.hostResource.HostResourceChildThread|172.16.1.13,172.16.1.152|Memory
Validating Job -->
com.aptare.core.hostResource.HostResourceChildThread|172.16.1.13,172.16.1.152|Process
Validating Job -->
com.aptare.core.hostResource.HostResourceChildThread|172.16.1.13,172.16.1.152|Network
Validating Job -->
com.aptare.core.hostResource.HostResourceChildThread|172.16.1.15|Capacity -
SUCCESS_PERSISTING_HOST_RESOURCE_DETAIL
Installation of APTARE StorageConsole Agent has been successfully validated.
4. If the output in the above steps contain the word FAILED, then refer to Appendix A -
Troubleshooting. If you exhaust the tips provided in the troubleshooting sections, then
contact the APTARE Customer Care Group and have the following files ready for review:
<install_dir>/mbs/logs/metadata.log
<install_dir>/mbs/logs/watchdog.log
Validating the Installation 81

List Data Collector Configurations
Use this utility to list the various child threads and their configurations encapsulated
within a data collector configuration. This utility can be used in conjunction with other
scripts, such as checkinstall.[sh|bat].
On Unix: ./listcollectors.sh
On Windows: listcollectors.bat
Example Output
[root@aptarelab1 bin]# ./listcollectors.sh
Below are the list of Data Collectors defined in

/opt/build65/EMC/mbs/conf/collectorconfig.xml
Collector Id: aptarelab1_emc_clariion

Collector Passcode: aptare
URL: http://aptareagent.aptaredev2
==== Meta Collectors ====

Meta Collector Id: META_hostResource_10
Domain: aptaredev2
Group Id: 100000
Active: true
Active: true
Task:
com.aptare.core.hostResource.HostResourceChildThread|172.16.1.13,172.16.1.152|Capacity
Payload Id: Windows
Schedule: */30 * * * *
Active: true
Task: com.aptare.core.hostResource.HostResourceChildThread|172.16.1.15|Capacity
Payload Id: Unix
Schedule: */30 * * * *
Meta Collector Id: META_172.16.1.22_8

Domain: aptaredev2
Group Id: 100000
Server Id: 100003
Active: true

Software Home: /opt/Navisphere/bin
Server Address: 172.16.1.22
User Id: UjZzW0CS8Ks=
Active: true
Task: com.aptare.core.emcStorage.EmcStorageArrayChildThread
Schedule: 240
List Data Collector Configurations 83

5
Starting the Data Collector

Chapter2
The installer configures the Data Collector to start automatically, however, it does not
actually start it upon completion of the installation because you must first validate the
installation.
Data Collector Manual Startup

Follow these steps, for the relevant operating system, to manually start the Data
Collector service:
On Windows
The installer configures the Data Collector process as a Service.
To view the Data Collector Status:
1. Click Start > Settings > Control Panel

2. Click Administrative Tools.
3. Click Services.
The Microsoft Services Dialogue will be displayed. It should include entries for “Aptare
Agent”. Start this service if it is not running.
On UNIX
The installer automatically copies the Data Collector “start” and “stop” scripts to the
appropriate directory, based on the vendor operating system.
To start the data collector, use the following command for the respective platforms:
OS Command
Linux/Solaris /etc/init.d/aptare_agent start
AIX /etc/aptare_agent start
HP-UX /sbin/init.d/aptare_agent start
Data Collector Manual Startup 85

6
Un-installing the Data Collector

Chapter2
Use the procedures in this chapter to un-install a Data Collector.
Un-install the Data Collector on UNIX

1. Login to the Data Collector Server as root.
2. Stop the Data Collector service, using the command appropriate for the operating system:
OS Command
Linux/Solaris /etc/init.d/aptare_agent stop
AIX /etc/aptare_agent stop
HP-UX /sbin/init.d/aptare_agent stop
3. Delete the following files, using the relevant command:
OS Command
AIX find /etc -name aptare_agent -print | xargs rm
HP-UX find /sbin -name aptare_agent -print | xargs rm
4. Delete the Data Collector directory structure (default installation path is /opt/aptare):
Caution: The rm command can be very destructive, if not used carefully. Do not copy and
paste commands, as the paste may include a return character, causing the execution of a
globally destructive command.
rm –rf /opt/aptare/installlogs /opt/aptare/jre /opt/aptare/lib /opt/aptare/mbs
/opt/aptare/UninstallerData
Un-install the Data Collector on UNIX 87

Un-install the Data Collector on Windows
1. Login to the Data Collector Server. (User should have Administrator privileges.)
2. Stop the Data Collector (agent) services.
• Click Start > Settings > Control Panel
• Click Administrative Tools.
• Click Services.
3. Click on “Un-install APTARE StorageConsole Agent” in “Start Menu/Programs/APTARE
StorageConsole Agent”
4. Follow the prompts in the un-install windows.
Note: The un-installer may not delete the entire Data Collector directory structure. Sometimes
new files, created after the installation, along with their parent directories, are not removed. You
may need to manually remove the root install folder (default C:\Program Files\Aptare) and its
sub-folders after the un-installer completes.

Appendix A - Troubleshooting
Chapter2
If the post-installation validation failed, this often is due to some simple configuration
issues that can be fairly easily resolved. This appendix lists some of the common
configuration issues. If the issue cannot be resolved by following the steps in this
section, contact the Customer Care Group. Be sure to include the log files that were
generated during the installation process.
This Appendix includes the following procedures and steps to isolate the source of
errors:
• Verify the Data Collector Configuration
• Typical Host Resources Troubleshooting Sequence
• Host Resources: Post-Installation Verification
• Host Resources: Verify Connectivity
• Host Resources: Generating Host Resource Configuration Files
• Host Resources: Check the Execution of a Command on a Remote Server
• Host Resources: Collection in Stand-Alone Mode
• Configuring Parameters for SSH
89
Verify the Data Collector Configuration
The Data Collector configuration file contains key information captured during the
installation process. If the information was entered incorrectly, this may be the cause of
the failure.
Check the Configuration File

1. Edit the configuration file.
Windows:
edit “C:\Program Files\Aptare\mbs\conf\wrapper.conf”
UNIX:
edit “/opt/aptare/mbs/bin/startup.sh” and "/opt/aptare/mbs/bin/updateconfig.sh"
2. Verify the values of the following parameters and update them, if necessary.
wrapper.app.parameter.2 Should match the Collector Name you specified in

“Updating the Local Hosts File” on page 19.
wrapper.app.parameter.3 Should match the Passcode you specified in “Updating
the Local Hosts File” on page 19.
wrapper.app.parameter.4 For IN-HOUSE installations:
where: yourdomain.com has the appropriate value.
For APTARE HOSTED installations:
http://agent.storageconsole.com
For third-party HOSTED installations:
http://aptareagent.domain.com
where: domain.com has the appropriate value.
3. If you changed any of the configuration file parameters, you’ll need to:
• Restart the Data Collector service, as described in “Data Collector Manual Startup” on
page 85.
• Re-run the installation validation utility, as described in “Validating the Installation” on
page 79.

Typical Host Resources Troubleshooting Sequence
The following sequence of steps can be used to determine the source of host resources
data collection issues. All commands—except for the SSH commands and the WMI
Proxy command—report errors to metadata.log. After executing a command, check the
metadata.log file for error messages. If there is an error noted, correct the problem and
then re-issue the command. If the command succeeds, proceed to the next command in
this sequence:
1. “Host Resources: Check the Status of the WMI Proxy Server” on page 92
2. “Host Resources: Post-Installation Verification” on page 94
3. “Host Resources: Check Host Connectivity Using Standard SSH” on page 95
4. “Host Resources: Check Host Connectivity” on page 97
5. “Host Resources: Check Host Connectivity for the Host Resources Configuration File” on
page 98
6. “Host Resources: Check the Execution of a Command on a Remote Server” on page 100
7. “Host Resources: Collection in Stand-Alone Mode” on page 101
Typical Host Resources Troubleshooting Sequence 91

Host Resources: Check the Status of the WMI Proxy Server
Use the following checkwmiproxy utility to verify that the WMI Proxy Server is up
and running.
The APTARE WMI Proxy logs are written to:
C:\Program Files\Aptare\WMIProxyServer\logs\aptarewmiserver.log
Prerequisites:
Either checkinstall or updateconfig must have been run before running
checkwmiproxy. Otherwise, checkwmiproxy will not have access to the proxy server
settings that are saved in the collector configuration file.
Usage:
checkwmiproxy.[sh|bat] [wmiProxyServer wmiProxyPort remoteWinHost DomainOfUserId
UserId Password "Command"]
Where:
wmiProxyServer is the name of the APTARE WMI Proxy Server
wmiProxyPort is the proxy’s port (default is 1248)
Simple Usage:
checkwmiproxy.[sh|bat]
By default, this utility will look for the WMI Proxy Server details in the Host Resources
Collector section of the collector configuration file. If it does not find a Host Resources
Collector section, the checkwmiproxy will terminate with an error and a
recommendation to pass explicit parameters, as shown in the usage statement above.
Example 1:
[root@aptaredev3 bin]# ./checkwmiproxy.sh
MetaDataChildThread.init(). Going to initialize.
Will try to connect to the APTARE WMI Proxy at 172.16.1.152:1248
APTARE WMI Proxy Version: APTAREWMIServer 6.5.01 06/25/07 21:00:00
Connection to APTARE WMI Proxy server successfully validated.
Example 2: Remote WMI Queries

This utility also can be used to execute remote WMI queries, as shown in the following
example.
[root@aptaredev3 bin]# ./checkwmiproxy.sh 172.16.1.152

Administrator password 172.16.1.152 "select * from Win32_OperatingSystem"
MetaDataChildThread.init(). Going to initialize.

Will try to connect to the APTARE WMI Proxy at 172.16.1.152:1248
APTARE WMI Proxy Version: APTAREWMIServer 6.5.01 06/25/07 21:00:00
Connection to APTARE WMI Proxy server successfully validated.
APTAREWMIServer Response:
instance of Win32_OperatingSystem
{
BootDevice = "\\Device\\HarddiskVolume1";
BuildNumber = "3790";
BuildType = "Multiprocessor Free";
Caption = "Microsoft(R) Windows(R) Server 2003, Standard Edition";
CodeSet = "1252";
CountryCode = "1";
CreationClassName = "Win32_OperatingSystem";
CSCreationClassName = "Win32_ComputerSystem";
CSDVersion = "Service Pack 1";
CSName = "APTARESTGRPT1";
CurrentTimeZone = -420;
DataExecutionPrevention_32BitApplications = TRUE;
DataExecutionPrevention_Available = TRUE;
DataExecutionPrevention_Drivers = TRUE;
DataExecutionPrevention_SupportPolicy = 2;
Debug = FALSE;
Description = "aptarestgrpt1";
Distributed = FALSE;
EncryptionLevel = 168;
ForegroundApplicationBoost = 2;
FreePhysicalMemory = "160264";
FreeSpaceInPagingFiles = "1967860";
FreeVirtualMemory = "2084508";
InstallDate = "20070212110938.000000-480";
LargeSystemCache = 1;
LastBootUpTime = "20080507115419.343750-420";
LocalDateTime = "20080520142117.484000-420";
Locale = "0409";
Manufacturer = "Microsoft Corporation";
MaxNumberOfProcesses = 4294967295;
MaxProcessMemorySize = "2097024";
Name = "Microsoft Windows Server 2003 R2 Standard
Edition|C:\\WINDOWS|\\Device\\Harddisk0\\Partition1";
NumberOfLicensedUsers = 10;
NumberOfProcesses = 90;
NumberOfUsers = 8;
Organization = "Aptare";
Host Resources: Check the Status of the WMI Proxy Server 93

OSLanguage = 1033;
OSProductSuite = 272;
OSType = 18;
OtherTypeDescription = "R2";
PAEEnabled = TRUE;
Primary = TRUE;
ProductType = 3;
QuantumLength = 0;
QuantumType = 0;
RegisteredUser = "Aptare";
SerialNumber = "69712-OEM-4418173-93136";
ServicePackMajorVersion = 1;
ServicePackMinorVersion = 0;
SizeStoredInPagingFiles = "2039808";
Status = "OK";
SuiteMask = 272;
SystemDevice = "\\Device\\HarddiskVolume1";
SystemDirectory = "C:\\WINDOWS\\system32";
SystemDrive = "C:";
TotalVirtualMemorySize = "3256472";
TotalVisibleMemorySize = "1363400";
Version = "5.2.3790";
WindowsDirectory = "C:\\WINDOWS";
};
Host Resources: Post-Installation Verification

Execute this utility to verify that the host resources installation was successful.
Usage:
hostresourcecheckinstall.{sh|bat}

Host Resources: Verify Connectivity
A number of utilities can be used to verify connectivity to the hosts for which you want
to collect data.
• “Host Resources: Check Host Connectivity Using Standard SSH” on page 95
• “Host Resources: Check Host Connectivity” on page 97
• “Host Resources: Check Host Connectivity for the Host Resources Configuration File” on
page 98
Host Resources: Check Host Connectivity Using Standard SSH

StorageConsole uses SSH to communicate with devices to run SSH commands.
Sometimes, a connectivity issue is simply an incorrect path to a host.
Note: Use the following SSH commands before attempting to collect data.
To check host connectivity using standard SSH:
1. Check that the connection to a Host is successful, using the credentials provided.
[user@host ~] ssh <user>@<host> ls
Similarly, if you are using Telnet, check your host access via Telnet and run sudo
commands, as shown in the following step.
2. In access-controlled environments such as sudo, a sudo user must be set up. Ensure that the
sudo user can run the commands required for the host operating system platform.
To verify sudo access:
[user@host ~] ssh <sudouser>@<host> “sudo <command>”
If this command results in errors, such as command not found, set up the paths correctly and
re-run this command. See “Checking Paths for SSH” on page 95.
3. Paths should be set correctly for the commands to run.
Checking Paths for SSH

If you find messages in the metadata.log file that indicate that some of the commands
are not found, then most likely the reason for it is the paths have not been set properly.
StorageConsole uses a non-interactive login shell to execute ssh commands on devices.
1. Check the environment setting for the shell by running the command.
[user@host ~] ssh <user>@<host> “env”
Check the PATH shown in the output and make sure that it contains the path to all the
commands required for StorageConsole for the OS platform of the host.
Sample PATH for each of the host operating system platforms:
Linux: /bin:/sbin:/usr/bin:/usr/sbin
Solaris: /usr/xpg4/bin:/usr/sbin:/usr/bin
AIX: /usr/bin:/usr/sbin
HPUX: /usr/bin:/usr/sbin:/opt/fcms/bin:/sbin
Host Resources: Verify Connectivity 95

Note: Since Veritas Volume Manager is supported, its path needs to be included in the
PATH env variable.
2. In sudo environments, make sure that the sudo path is also in the PATH shown in the output
of the above command.
Environment Setting for bash users:

1. Define all your settings in the file: ~/.bashrc
2. Make sure that the file ~/.bash_profile only contains the line: source ~/.bashrc

Host Resources: Check Host Connectivity
This APTARE-provided utility displays information on the connection status of a list of
host names, IP addresses, or a range of IP addresses.
Usage:
chkHostConnection.{sh|bat} HostAddresses userId password [domain <domain>] [exclude
<excludeHostAddresses>] [wmiserver <wmiserver>] [cto <connectTimeout>] [sto
socketTimeout>] [accessCmd=accessControlCommand>]
HostAddresses The hosts to verify. It can be hostname, IP address, or range of IP

addresses, or a comma-separated list of them.
domain The Domain for the Windows hosts
excludeHostAddresses The hosts to be excluded from the HostAddresses list. It can be
hostname, IP address, or range of IP addresses, or a comma
separated list of them.
wmiserver Name of the WMI Proxy Server
cto Connection time-out in milliseconds
sto Socket time-out in milliseconds
accessCmd An access control command such as sudo
Result:
For each host, the status of the connection is listed.
Connectivity Check Server List: [172.16.1.10, 172.16.1.12, APTAREaix1]
172.16.1.10 ............. SUCCESS
172.16.1.12 ............. SUCCESS
Host Resources: Verify Connectivity 97

Host Resources: Check Host Connectivity for the Host Resources
Configuration File
This APTARE-provided utility provides information on the connection status of a list of
Host Addresses that are provided in the Host Resource Configuration file.
Usage:
chkHostConnection.{sh|bat} file <HostResourceFile> [wmiserver <wmiserver>] [cto
<connectTimeout>] [sto <socketTimeout>]
HostResourceFile The file should be located under the home directory:

/mbs/conf/hostresourceconf
Result: For each host, the status of the connection is listed.

Connectivity Check Server List: [172.16.1.10, 172.16.1.12, aptareaix1]
172.16.1.10 ............. SUCCESS
172.16.1.12 ............. SUCCESS

Host Resources: Generating Host Resource Configuration Files
This APTARE-provided utility automatically generates the host resource configuration
files and collector configuration file for each valid line provided in the input file.
Usage:
genHostResourceConf.{sh|bat} {CollectorID} {fileName}
CollectorID Identifier name used for the configuration files

filename File containing the list of parameters—one per line—in the format:
HostAddresses:userId:password:domain:excludeHostAddress
Note: Comments are allowed by using a # at the beginning of the line.
Sample lines in an input file:

# Sample configuration file to generate Host Resource Conf files 172.16.1.11-
13,aptarelab3:root:adminpwd::172.16.1.12-13,apataredlab3
aptareaix1:root:superpwd::
apatrewin2k:samuel:adminpwd:aptarewin2kdomain:
Result:
• For each valid line, a host resource configuration is created under the home directory:
/mbs/conf/hostresourceconf. Lines that are not valid are sent to standard output.
• Creates a collector configuration xml file with Meta Data Collector child thread tags for each
successfully created host resource configuration file. The file is saved in the home directory
under /mbs/conf. The collector configuration xml is named in the following format:
collectorconfig-<date>.xml where date is in DDMMMYYYHHMM format
Host Resources: Generating Host Resource Configuration Files 99

Host Resources: Check the Execution of a Command on a
Remote Server
This utility provides the output of a command by running it on the specified remote
server.
Usage:
remoteExecCommand.{sh|bat} HostAddress [enc] userId password [domain=<domain>]
[wmiserver=<wmiserver>] [cto=<connectTimeout>] [sto=socketTimeout>]
[accessCmd=accessControlCommand>]
HostAddresses The hosts to verify. It can be hostname, IP address, or range of IP addresses,

or a comma-separated list of them.
userId password Use the [enc] option to provide encrypted user ID and password arguments.
domain The Domain for the Windows hosts (only for connecting to a Windows
server)
accessCmd An access control command such as sudo
Examples:
remoteExecCommand.sh 172.16.1.21 myuser mypasswd /usr/bin/df -k
remoteExecCommand.sh 172.16.1.21 myuser mypasswd accessCmd=sudo cto=10000 /usr/bin/df
-k
Host Resources Data Collection

StorageConsole can collect the following types of host resources:
• Capacity
• Oracle
• SQL Server
• Exchange
• Network
• Processor
• Memory
• Process
• System
Host Resources: Collection in Stand-Alone Mode
This utility executes the data collection process against the specific host resources files.
Usage (3 options):
hostresourceDetail.{sh|bat} all
hostresourceDetail.{sh|bat} <MetaCollectorID> <HostResourcePolicyName>
hostresourceDetail.{sh|bat} HostAddresses uid=userId pwd=password [<domain>]
[<excludeHostAddresses>]
all This option runs host resource policies against all Meta Collectors.
MetaCollectorID The ID used to identify the MetaCollector within the collector
configuration xml file.
HostResourcePolicyName The Policy ID within the Meta Collector ID specified.
HostAddresses The hosts to verify. It can be hostname, IP address, or range of IP
addresses, or a comma separated list of them.
domain The Domain for the Windows hosts
excludeHostAddresses The hosts to be excluded from the HostAddresses list. It can be
hostname, IP address, or range of IP addresses, or a comma
separated list of them.
Configuring Parameters for SSH

To add any configurable SSH parameters, modify the following scripts:
hostResourceDetail.{sh|bat} and aptarecron.{sh|bat}
For example, to add the channelWaitTime parameter, insert the following after java:
-DchannelWaitTime=5000
Configure channelWaitTime:
If you are experiencing slow connectivity from the Data Collector Server to the Host,
update the scripts with this Configurable Parameter. This parameter is specified in
milliseconds.
-DchannelWaitTime=5000 // This will set the wait time for data from the server.
Configure singleChannelSession:
This will run each command in a separate session.
-DsingleChannelSession=true // This will run the each command in a separate session.
Configure sudoWithPassword:
In sudo environments, this will send the password without waiting for a prompt.
-DsudoWithPassword=true // This will allow running sudo with -S option to send the
password without waiting for a prompt.
Host Resources: Collection in Stand-Alone Mode 101

Index
A startup data collector, 85
architecture, 4 storage arrays
EMC CLARiiON, 15
C EMC Symmetrix, 15
checkinstall, 79 Hitachi, 15
checkwmiproxy, 92
configuration file, 89, 90 T
connectivity, 95, 97 troubleshooting, 89
console
install, 73 U
un-install data collector, 87
D
data collector V
definition, 1 validate
GUI deployment, 67 configuration file, 89
install, 67 validation
policies, configuring, 20, 21, 26, 31, 36, 40, checkinstall, 79
45, 49 configuration file, 90
pre-requisites, 7 hostresourcecheckinstall, 94
server, 2 listcollectors, 82
G W
GUI deployment, 67 WMI proxy server, 63
check status, 92
H
host connectivity, 95
host resources
chkHostConnection, 95, 97
configuration files, 97
hostresourcecheckinstall, 94
remote servers, 100
stand-alone collection, 101
troubleshooting, 90
verify connectivity, 95
hostresourcecheckinstall, 94
I
install
CD, 67
console, 73
data collector, 67
internet, 68
installation
WMI proxy server, 63
installation steps
overview, 18
L
listcollectors, 82
S
SSH parameters, 101
Index 1

Apt Are

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Apt Are

Uploaded by

Copyright:

Available Formats

APTARE StorageConsole Data Collector

Installation Guide for Capacity Manager

Publication Change Record

Copyrights and Trademarks iii

2 APTARE StorageConsole Data Collector Installation Guide for Capacity Manager

About This Book

Technical Support: Sales:

About This Book 1

Introduction to Data Collection

This chapter covers the following topics:

Data Collection Overview

Data Collector Terminology

Data Collection by Backup Product

Data Collection Overview 1

Data Collection by Storage Array

Planning Data Collector Deployment

2 APTARE StorageConsole Data Collector Installation Guide for Capacity Manager

Data Collection Overview 3

Figure 1.1 Data Collector for Capacity Manager

4 APTARE StorageConsole Data Collector Installation Guide for Capacity Manager

This chapter covers the following topics:

Before You Install Data Collectors

Before You Install Data Collectors 7

Which Policies Are Needed

8 APTARE StorageConsole Data Collector Installation Guide for Capacity Manager

10 APTARE StorageConsole Data Collector Installation Guide for Capacity Manager

Supported Hardware, Software, Storage Arrays (Capacity Manager)

Capacity Manager Supported Configurations 11

12 APTARE StorageConsole Data Collector Installation Guide for Capacity Manager

EMULEX Supported Adapters (using either EMULEX Storport Miniport

LSI Logic Corp Supported Adapters (using Storport Miniport driver

QLOGIC Supported Adapters (using driver version 8.2.3.x or 9.1.x.x or

Capacity Manager Supported Configurations 13

IBM Arrays Sun Arrays LSI

14 APTARE StorageConsole Data Collector Installation Guide for Capacity Manager

Storage Array/ Access Methods and Pre-Requisites

• A User account with monitor group privileges on the array is required.

Pre-Requisites: Storage Arrays and Host Resources 15

Storage Array/ Access Methods and Pre-Requisites

• Create a view-only user ID and password for CLARiiON NaviSuite.

IMPORTANT: The EMC Symmetrix Data Collector needs to be installed on

Creating a NetApp User with API Privileges

16 APTARE StorageConsole Data Collector Installation Guide for Capacity Manager

Storage Array/ Access Methods and Pre-Requisites

Pre-Requisites: Storage Arrays and Host Resources 17

 Update the Local Hosts File

18 APTARE StorageConsole Data Collector Installation Guide for Capacity Manager

Updating the Local Hosts File 19

20 APTARE StorageConsole Data Collector Installation Guide for Capacity Manager

Capacity Manager for Hitachi 21

22 APTARE StorageConsole Data Collector Installation Guide for Capacity Manager

Capacity Manager for Hitachi 23

If you are a Managed Services Provider, each of your

To find your Domain name, in the menu list at the left of

*/30 * * * * means every 30 minutes

See Probe Schedule Examples in the Application

serverAddress as configured for the Hitachi device manager server above

24 APTARE StorageConsole Data Collector Installation Guide for Capacity Manager

Capacity Manager for Hitachi 25

IBM Arrays Sun Arrays LSI

26 APTARE StorageConsole Data Collector Installation Guide for Capacity Manager

Capacity Manager for IBM 3000 & 4000 Series 27

28 APTARE StorageConsole Data Collector Installation Guide for Capacity Manager

Update the Local Hosts File

/30 * * * means every 30 minutes

/30 * * * means every 30 minutes

/30 * * * means every 30 minutes

/30 * * * means every 30 minutes

/30 * * * means every 30 minutes

/30 * * * means every 30 minutes

/20 9-18 * * Every 20 minutes between 9 am and 6 pm

/30 * * 1-5 Every 30 minutes, Monday through Friday