Aperi Storage Manager Installation Instructions

Welcome to Aperi Storage Manager (Aperi). Aperi is open-standards-based storage infrastructure software that can centralize, automate, and simplify the management of complex and heterogeneous storage environments. Aperi can help to improve storage capacity utilization, administrative efficiency, and provide users with greater flexibility in the way they manage their storage environments.

Use the following instructions to learn how to install and initially configure Aperi Storage Manager. See the Aperi Storage Manager User's Guide and online help for information about how to use the product once it is installed. You can view Aperi documentation on the following page: http://www.eclipse.org/aperi/documentation/.

1. Plan the deployment
2. Check install requirements
3. Plan for the database repository
4. Install the Aperi Storage Manager files
5. Configure Aperi Storage Manager
6. Start Aperi Storage Manager
- 6.1 Start the Aperi Storage Manager Server, Agent, Report server, and Database Repository
- 6.2 Start the Aperi Storage Manager user interface
7. Shut down Aperi Storage Manager
8. Uninstall Aperi Storage Manager
9. Perform post-installation configuration
10. Grant local administrative privileges to a domain account
Notices

1. Plan the deployment

Aperi Storage Manager is an integrated set of software components that provides end-to-end storage management, from the host and application to the target storage device in a heterogeneous platform environment. These components include the following:

User Interface

The user interface enables you to use Aperi Storage Manager to manage your storage environment.

Data Server

This component is the control point for product scheduling functions, configuration, event information, reporting, and GUI support. It coordinates communication and data collection with agents that gather storage demographics and populate the database with results.

Device Server

This component discovers and gathers information for storage subsystems and SAN fabrics. It coordinates communication and data collection from agents that probe SAN fabrics.

Agents

Agents gather host, application, and SAN fabric information and send this information to the Data server or Device server.

Database Repository

A single database instance serves as the repository for data collected by agents. The Aperi database repository can run under either of the following relational database systems:

Apache Derby
DB2 8 for Linux UNIX and Windows.

Keep in mind the following strategies when installing these components:

The most straightforward deployment of Aperi Storage Manager is to install its main components (user interface, servers, and agent) on the same host machine.
However, consider designating one machine to host the server if you have a large environment with many machines whose storage you want to monitor. This might help reduce the workload on the server machine.
A typical scenario is to install all components on the same machine and add remote agents and user interfaces to other machines later.
Install agents on any machine that you want to monitor and manage using the Aperi filesystem functions. Make sure that these machines (managed hosts) can communicate with the machine where you installed the Aperi Storage Manager server.
Install the user interface on any machine where you would like to use the product to manage your storage environment. Make sure that this machine can communicate with the machine where you installed the Aperi Storage Manager server.

The following figure shows a sample configuration of Aperi Storage Manager components:

2. Check install requirements

Platform/software requirements

You must be running Windows 2000, XP, or 2003 and have approximately 100MB of available disk space. Red Hat Enterprise Linux AS Version 3.0 IBM Eserver xSeries and Novell SUSE Linux Enterprise Server 10 are also supported.
You must have Java Runtime Environment (JRE) 1.5 or higher installed on your machine. To check for Java on a machine, start a command prompt window and type java -version from a command line. If you do not have a JRE 1.5 or higher installed, you can download it from the following Web site: http://java.sun.com/j2se/1.5.0/download.jsp

Server requirements (recommended)

Processor (minimum) - Intel(R) Pentium(R) 4 CPU 3.00GHz+ or compatible AMD processor
Processor (recommended): Intel(R) Xeon(TM) CPU 2.40GHz+ or compatible AMD processor
Memory - 2 GB RAM
Disk space - 100 MB
Operating systems: Windows XP Professional (service pack 2), Windows Server 2003 Standard Edition, Windows Server 2003 Enterprise Edition, Windows Server 2003 Datacenter Edition, Red Hat Enterprise Linux AS Version 3.0, Novell SUSE Linux Enterprise Server 10

Agent requirements (recommended)

Processor - Intel(R) Pentium(R) 4 CPU 3.00GHz+ or compatible AMD processor
Memory - 1 GB RAM
Disk space - 100 MB
Operating systems: Windows XP Professional (service pack 2), Windows Server 2003 Standard Edition, Windows Server 2003 Enterprise Edition, Windows Server 2003 Datacenter Edition, Red Hat Enterprise Linux AS Version 3.0, Novell SUSE Linux Enterprise Server 10

Administrative group

The Aperi Storage Manager environment supports role-based security. Operating system groups are associated with predefined roles. When a user ID is authenticated to Aperi through the GUI, membership in an operating system group determines the authorization level. By default, Aperi uses the following groups to determine administrative authority:

Windows: Administrators
UNIX/Linux: adm

If these default administrative groups do not match a group in your environment, or you want to use a different group for the Aperi administrator role, you can edit the adminGroup parameter in the server.config configuration file after a successful installation. Click here for more information about the adminGroup parameter and server.config configuration file.

3. Plan for the database repository

Use this section to determine what relational database to use as the database repository for Aperi. There are two relational databases available for use with Aperi:

Apache Derby is a relational database implemented entirely in Java and available under the Apache License, Version 2.0. Click here for more information. Apache Derby is included with the Aperi installation and can be installed using the Aperi Configurator. Click here for instructions on how to install it using the Aperi Configurator.

Note about Apache Derby Security: Aperi Storage Manager does not currently implement all the security features in Derby for an enterprise-wide management application. Most notably, the Aperi Configurator does not configure any user authentication for the Derby RDBMS.This means that anyone will be able to connect to and use the installation of Derby that comes with Aperi.

Skip to the next section if you plan to use Apache Derby as the database repository.
DB2 8 for Linux UNIX and Windows. Click here for more information about this relational database.
Complete the steps in this section if you plan to use DB2 as the Aperi database repository.

Perform the following steps to download and set up DB2 for use with Aperi Storage Manager:

Download DB2. You can download DB2 from here.
Install DB2 using the default settings. Note the db2admin password that you choose during the installation.
Continue to the next section Install the Aperi Storage Manager files.

4. Install Aperi Storage Manager files

Install the Aperi Storage Manager files on machines:

Whose storage you want to manage and monitor.
Where you want to run the Aperi Storage Manager's user interface
Where you want to run the server component. This machine must be able to communicate with the machines where you install the agents and user interface.

Perform the following steps to install the server, agent, or GUI on a machine:

Locate the Aperi Storage Manager .zip file.
Place the .zip file in the directory where you want to install the product.
Use an unzipping tool to unzip the file.
Download required components that are not distributed with the Aperi Storage Manager .zip file. There are two methods for downloading required third-party files:
- Use Aperi's Configurator script (described in the Configure Aperi Storage Manager section) to automatically download some of the required files.
- Manually download and install the required files.
This step describes the files that you must download manually (you cannot use the Configurator script to do so). Perform the following steps to download these required files:
- Download BIRT Runtime 2.1.2.
- Download Dojo Toolkit 0.4.2.
- Download JavaHelp 1.1.3.
Download additional third-party files. Depending on your environment, you can download these additional required files manually or use Aperi's Configurator script to perform the download automatically. To determine what works best for your environment, consider the following:
- Automatic download: Use the Aperi Configurator script (in regular or easy mode) to automatically download these additional third-party files. If you run the Configurator in easy mode, these files are downloaded automatically as part of the configuration process. If you run the Configurator in regular mode, press Enter at the Download third party software [Yes]? prompt to download the files automatically. Skip this step and go to step 6 if you plan to use the Configurator.
- Manual download: Download these additional third-party files manually if any of the following is true:
  - You are installing Aperi behind a firewall.
  - You are installing Aperi in an environment where there is no internet connection.
  - You are installing Aperi in an environment where the ability to automate the download of third-party libraries is prohibited.
  - You are planning to use the Configurator in easy mode to install Aperi.
  Download the following files if you do not plan to use the Configurator to perform the automatic downloads:
- Download Geronimo 1.1.
  1. Go to http://www.apache.org/dist/geronimo/1.1/geronimo-tomcat-j2ee-1.1.zip.
  2. Save the download (geronimo-tomcat-j2ee-1.1.zip) to a local directory (such as /geronimo-1.1).
  3. Unzip the contents of geronimo-tomcat-j2ee-1.1.zip.
  4. Copy geronimo-j2ee_1.4_spec-1.1.jar to [aperi_install_dir]\plugins\javax.j2ee_1.0.0.
  5. Copy geronimo-j2ee_1.4_spec-1.1.jar to [aperi_install_dir]\rcpgui\plugins\javax.j2ee_1.0.0.
    
    geronimo-j2ee_1.4_spec-1.1.jar is located in the following subdirectory where you unzipped geronimo-tomcat-j2ee-1.1.zip: /[location where you unzipped geronimo-tomcat-j2ee-1.1.zip]/repository/org/apache/geronimo/specs/geronimo-j2ee_1.4_spec/1.1.
- Download iText 1.3.
  1. Go to http://downloads.sourceforge.net/itext/itext-1.3.jar?modtime=1112806930&big_mirror=0.
  2. Save the download (itext-1.3.jar) to a local directory.
  3. Copy itext-1.3.jar to [aperi_install_dir]\plugins\org.eclipse.aperi.reporting_5.0.0\web\birt-viewer\WEB-INF\lib
- Download org.mortbay.jaas 5.1.10.
- Download javax.servlet.jsp_2.0.0.v200612120446.jar.
- Download org.apache.commons.el_1.0.0.v200704241052.jar.
- Download org.apache.jasper_5.5.17.v200701082340.jar.
If you plan to use DB2 as the database repository, continue to the next step. If you plan to use Apache Derby as the database repository, continue to step 8.
Copy the DB2 JDBC driver into the directory where you unzipped the Aperi Storage Manager files. To do this perform the following steps:
1. Locate the DB2 JDBC driver that was installed during the DB2 installation. On Windows, check C:\Program Files\IBM\SQLLIB\Java. The filenames are db2jcc.jar and db2jcc_license_cu.jar.
2. Copy the driver files to the following Aperi directories:
  - /plugins/org.eclipse.aperi.db_1.0.0
  - /rcpgui/plugins
3. Go to /plugins/org.eclipse.aperi.db_1.0.0/MANIFEST.
4. Delete MANIFEST.MF.
5. Rename DB2-MANIFEST.MF to MANIFEST.MF.
(optional) Complete this step if you intend to use the Aperi report viewer from behind a firewall or from a location that does not have an internet connection. Otherwise, continue to the Configure Aperi Storage Manager section for information about how to set up the components you want to run on the machine where you unzipped the Aperi files.

A web-based report viewer is available as a perspective within the RCP framework or as a standalone application viewed through a web browser. The report viewer is based on BIRT, an open source Eclipse-based reporting system that provides you with the ability to generate a number of reports based on storage data collected by Aperi.

If you intend to use the report viewer from behind a firewall or from a location with no access to the internet, you must modify the DTD (Document Type Definition) in the web.xml files of the two web applications that comprise the report server. Each web.xml file contains the following XML DOCTYPE declaration after the Aperi copyright statement:

<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd">

Perform the following steps to modify the DTDs in the web.xml files:
1. Create a copy of the original web.xml files as distributed with Aperi. The web.xml files are located in the following directories:
  - [aperi_install_dir]\plugins\org.eclipse.aperi.reporting_5.0.0\web\birt-viewer\WEB-INF\web.xml
  - [aperi_install_dir]\plugins\org.eclipse.aperi.reporting_5.0.0\web\aperi-reports\WEB-INF\web.xml
  For example, create a copy of these files under different names in the same directories such as:
  - c:\aperi\plugins\org.eclipse.aperi.reporting_5.0.0\web\birt-viewer\WEB-INF\web.xml.orig
  - c:\aperi\plugins\org.eclipse.aperi.reporting_5.0.0\web\aperi-reports\WEB-INF\web.xml.orig
  This ensures that you have a copy of the original files for backup purposes.
2. Start a web browser and go to http://java.sun.com/dtd/web-app_2_3.dtd.
3. Save the source of this page to: [aperi_install_dir]\reporting\web-app_2_3.dtd. Make sure the name of the file you save locally is web-app_2_3.dtd.
  Note: You can also right-click the link http://java.sun.com/dtd/web-app_2_3.dtd and select the "save target as" option to save the file locally.
4. Open the following web.xml files in a text editor:
  - [aperi_install_dir]\plugins\org.eclipse.aperi.reporting_5.0.0\web\birt-viewer\WEB-INF\web.xml
  - [aperi_install_dir]\plugins\org.eclipse.aperi.reporting_5.0.0\web\aperi-report\WEB-INF\web.xml
5. Edit the DTDs in each web.xml file to point to the local web-app_2_3.dtd file that you saved previously as follows:
  
  Change the text "http://java.sun.com/dtd/web-app_2_3.dtd" that appears in each file's DTD to: "file:///[aperi_install_dir]/reporting/web-app_2_3.dtd"
  
  For example, the modified DTD for the web.xml files might appear as follows:
  
  <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "file:///C:/Aperi/reporting/web-app_2_3.dtd">
6. Save both web.xml files with the updated DTD.
7. Continue to the Configure Aperi Storage Manager section for information about how to set up the components you want to run on the machine where you unzipped the Aperi files.

5. Configure Aperi Storage Manager

Use the Configurator tool to set up Aperi Storage Manager components on the machine where you unzipped the product. The package that you unzipped contains the run-time files for all of Aperi Storage Manager's main components: a host-based agent, a server, and a GUI. You do not have to configure all the components on each machine; rather, use the Configurator to set up only the components that you want to run on a particular machine.

Note: Keep in mind that you must configure the server on one machine, called the "server host". The server host normally also has the agent and GUI configured on it.

The Configurator will ask you several questions to help you configure Aperi Storage Manager for your environment. In most cases, the questions have default values, which are displayed in square brackets []. To answer a question, type your answer and press Enter. If there is a default answer and you want to accept it, just press Enter.

For example, if the Configurator displays:

Server port [9549]:

Press Enter to accept 9549 as the value for the server port. You can also type a different value, such as:

Server port [9549]: 12345

When answering Yes/No questions, any string starting with "Y" or "y" is interpreted as Yes, and any other non-blank string is interpreted as No.

The following instructions are Windows specific; however, the Configurator does run on Linux. The basic process is the same for both Windows and Linux, although the syntax for changing directories and setting your PATH will be different.

5.1 Start the Configurator

Make sure you have a Java Runtime Environment (JRE) from IBM or Sun 1.5 installed on your machine. To check for Java on a machine, start a command prompt window (Start > Programs > Accessories > Command Prompt) and type java -version from a command line.

If you see text similar to the following then continue to step 2:

java version "1.5.0_07" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03) Java HotSpot(TM) Client VM (build 1.5.0_07-b03, mixed mode)

If you see text like the following, download the JRE from the IBM or Sun (http://java.sun.com/j2se/1.5.0/download.jsp) web sites before continuing:

'java' is not recognized as an internal or external command, operable program or batch file.
Set java into your PATH by typing the following at the command prompt:

set path=%path%;C:\path_to_java_directory\jdk1.5.0_07\bin wherepath_to_java_directory represents the directory where the JRE is installed.

Setting the Java path has two purposes: 1) it is used to run the Configurator, and 2 ) it is stored in the Aperi startup scripts and used to run Aperi Storage Manager. This means that if you later uninstall the Java with this path, you won't be able to start Aperi Storage Manager until you reconfigure Aperi.

Note: You can also edit the cfgaperi.bat file or the System Path to contain the JRE pathname.
Change to the [aperi_install_directory>\configure subdirectory where you installed the Aperi Storage Manager files. For example, type cd c:\aperi\configure ] and press Enter.
Determine whether you want to run the Configurator in "easy" or "regular" mode:
- Easy mode: the Configurator will choose all the default values for your Aperi installation. This mode will automatically download third-party files that are required by Aperi.
- Regular mode: The Configurator will enable you to review and modify all the configuration options for your Aperi installation.
Start the Configurator using the following steps:
Note: when running under Linux, you must first execute the following command against the cfgaperi file: chmod +x cfgaperi
- Easy mode: Type cfgaperi easy and press Enter. Skip to Use the Configurator (easy mode).
- Regular mode: Type cfgaperi and press Enter. Continue to the next section Use the Configurator (regular mode).
  Note: run the Configurator in regular mode when using DB2 as the Aperi database repository.

5.2 Use the Configurator (regular mode)

When the Configurator starts the following message will appear:

Checking Java installation...passed: [java_version].

Aperi Storage Manager Configuration This program will ask you a series of questions, then configure Aperi Default values are displayed in [square brackets].

Note: The Configurator displays a warning message if you are not running Java 1.5.

Indicate which components you want to configure on the machine. If this is your first time, or you wish to do things "normally", accept the defaults and answer Yes (press Enter for each one) to the following questions:

The Aperi Storage Manager consists of these major components: The host-based agent, the server, the GUI, and the report server. You can configure any or all of these to run on this computer. Which components do you want to configure? Answer with Yes or No. Agent [Yes]? Server [Yes]? GUI [Yes]?
Your answers determine what questions you get asked next, as some questions are agent-, server-, or GUI-specific. You are not asked questions that pertain to components you are not configuring.
- Continue to the next step if you are configuring all components.
- Continue to the next step if you are configuring an agent.
- Skip to step 3 if you are configuring a server only.
- Skip to step 11 if you are configuring the GUI only.
(agent question) If you are configuring the agent, you are asked to supply port value for the subagent. The subagent will open a socket on this port for communication with the server. You may choose any valid port number (0..65535) although, of course, you should not choose a port that are already in use. The only reason to override the default for this two question is when you know the default value is already in use.

Enter values to configure the agent. Agent port [9570]:

(server and agent) Configure the Device server.
- If you answered Yes to the server question in step 1, the following will appear:
  
  Enter values to configure the device server.
- If you're configuring the agent but answered No to the server question in step 1, the following will appear:
  
  Enter values to configure how the agent communicates with the device server. These must match how the device server is configured.
Either way, you will be asked the same set of questions about the Device server. If you are configuring both the server and the agent, your answers will be passed both to the server (to configure itself) and to the agent (to configure how the agent talks to the server). If you are just configuring the agent (because the server is on a different machine), you must enter values that match however you configured that server.

(server and agent) Enter the hostname, port, and password for the Device server.

Hostname [aperi-srm1]: 

    Port [9000]: 

    Password:

Field Name	Description
`Hostname [aperi-srm1]`	Enter the name of the machine on which the Aperi server is (or will be) running. If you are configuring the server on the current machine, enter that machine's name. If you're configuring an agent to talk to a remote server, then enter the name of the remote server's machine. The Configurator supplies the current machine's name as a default. There are three reasons to override this default: Use "localhost" as the hostname if you install all Aperi components on a single machine and restrict access so that Aperi components on remote machines cannot connect to this installation. This will prevent the Aperi server and agent from answering the phone for remote connections. If you are configuring an agent or GUI that is remote from its server, you will have to enter the remote server's name here. Enter a name that is resolvable on this host: depending on how your local machine and network are configured, you might be able to use a short name like "server1", or you might need a fully-qualified name like "server1.internal.org". If your machine has multiple network interfaces with different hostnames for each interface and the Aperi Configurator chose the wrong name to use as a default.
`Port [9000]`	Enter the port number that the Device server will use for communication. If you are configuring the server locally, choose any free port; if you're configuring an agent to connect to a remote server, choose the port number you configured for that server.
`Password`	Enter the "host authentication" password that should be used to protect access to the Device server. Choose any non-blank value. Note that it will be displayed in this command prompt window in plain text, although the Configurator encrypts it before storing it in the configuration files it generates.

(server only) Enter the port and HTTP port for the Data server.

Enter values to configure the data server.

    

    Port [9549]: 

    HTTP Port [9001]:

Field Name	Description
`Port [9549]`	Enter the port number that the Data server will use for communication. If you are configuring the server locally, choose any free port; if you're configuring an agent to connect to a remote server, choose the port number you configured for that server.
`HTTP Port [9001]`	Enter a port that can be used by the Data server. Ensure that this port is open and not in use.

Enter the path for the report server repository.

Report server repository path [reports]

This is the subdirectory within the Aperi directory where information about reports in the report viewer is stored. If the path does not exist it will be automatically created.

[user-defined path] Does not exist. Will be created.
Indicate whether you want to use Apache Derby as the database repository.

Do you want to use Derby as the Aperi repository [Yes]?

Press Enter to select Apache Derby and continue to Complete the configuration. If you want to use DB2 as the database repository, type No, press Enter, and continue to the next step.
Indicate that you want to use DB2 as the database repository. If you plan to use DB2, make sure you complete the steps in Plan for DB2 as the database repository before continuing.

Do you want to use IBM DB2 as the Aperi repository [Yes]?

Press Enter to select IBM DB2 and continue to the next step.
Indicate that DB2 is ready for configuration.

DB2 should installed and running with database created named 'Aperi'. You also need to have installed the com.ibm.db2 plugin. Is DB2 ready [Yes]?

Press Enter if DB2 is ready. If DB2 is not ready, perform the steps described in Plan for DB2 as the database repository before continuing.

Enter values to configure DB2.

Port [50000]: DB2 

    username [db2admin]: 

    Password: 

    DB2 Command Line Processor Path

Field Name	Description
`Port [50000]`	Enter the port number that DB2 will use for communication.
`DB2 username [db2admin]`	Enter the user ID that you indicated in Plan for DB2 as the database repository. `db2admin` is the default user ID with administrative authority that DB2 creates during its installation.
`Password`	Enter the password for the user ID indicated in the `DB2 username` prompt.
`DB2 Command Line Processor Path:`	Enter the full path to the DB2 command line processor.

Continue to Complete the configuration.

Download some of the necessary third-party libraries required by Aperi. If you type Yes for this option, the Configurator will automatically download the following third-party files:
- itext-1.3.jar
- org.mortbay.jaas-5.1.10.jar
- geronimo-j2ee_1.4_spec-1.1.jar
- javax.servlet.jsp_2.0.0.v200612120446.jar
- org.apache.commons.el_1.0.0.v200704241052.jar
- org.apache.jasper_5.5.17.v200701082340.jar
If you select No for this option, make sure you follow the instructions in 4. Install Aperi Storage Manager files to download and install these third-party files manually.

Download third party software [Yes]? Please select a mirror for JSP API Bundle: 0. [United States] Columbia University (http) 1. [United States] Indiana University (http) 2. [United States] OSU Open Source Lab (http) 3. [United States] Georgia Tech. Software Library (http) 4. [Korea, Republic Of] Daum Communications Corp. (http) 5. [Taiwan] Computer Center, Shu-Te University (http) 6. [Australia] Pacific Internet (http) 7. [Czech Republic] Sillicon Hill Mirror (http) 8. [Germany] Innoopract Informationssysteme GmbH (http) 9. [Germany] University of Applied Sciences Esslingen (http) 10. [Greece] National Technical University of Athens (http) 11. [Hungary] I-Logic Ltd (http) 12. [Italy] GARR/CILEA (http) 13. [Portugal] Departamento de Cincia de Computadores, FCUP (http) 14. [Romania] Romanian Education Network (http) 15. [Switzerland] SWITCHmirror (http) 16. [Turkey] Tubitak-Ulakbim (http) 17. [United Kingdom] UK Mirror Service (http) Mirror [0]: 0 Please select a mirror for Apache Commons EL 1.0.0: 0. [United States] Columbia University (http) 1. [United States] Indiana University (http) 2. [United States] Georgia Tech. Software Library (http) 3. [United States] OSU Open Source Lab (http) 4. [Korea, Republic Of] Daum Communications Corp. (http) 5. [Taiwan] Computer Center, Shu-Te University (http) 6. [Australia] Pacific Internet (http) 7. [Czech Republic] Sillicon Hill Mirror (http) 8. [Germany] Innoopract Informationssysteme GmbH (http) 9. [Germany] University of Applied Sciences Esslingen (http) 10. [Greece] National Technical University of Athens (http) 11. [Hungary] I-Logic Ltd (http) 12. [Italy] GARR/CILEA (http) 13. [Portugal] Departamento de Cincia de Computadores, FCUP (http) 14. [Romania] Romanian Education Network (http) 15. [Switzerland] SWITCHmirror (http) 16. [Turkey] Tubitak-Ulakbim (http) 17. [United Kingdom] UK Mirror Service (http) Mirror [0]: Downloading the third party software. Downloads complete.
=======

(GUI only) Enter values to configure how the GUI communicates with the Data server. These must match how the Data server is configured.

Enter values to configure the data server.

    

    Hostname [aperi-srm1]: 

    Port [9549]:

Field Name	Description
`Hostname [tpc-d9-int]`	Enter the name of the machine on which the Aperi server is running. The GUI will use this name to connect to the server.
`Port [1527]`	Enter the port number on which the server is listening for requests..

5.3 Use the Configurator (easy mode)

When the Configurator starts the following message will appear:

Aperi Storage Manager Configuration This program will ask you a series of questions, then configure Aperi Default values are displayed in [square brackets]. Checking Java installation...passed.

If you chose to run the Configurator in easy mode, then default values are chosen for you for all the configuration questions. The Configurator will assume you are configuring all three components on the local machine. The hostname as determined by the Configurator will be used. Port number defaults are:

Fabric subagent: 9570
Filesystem subagent: 9550
Device server: 9000
Data server: 9549
Data server HTTP: 19550
Derby RDBMS: 1527

See 4.2 Use the Configurator (regular mode) for an explanation of these configuration questions.

5.4 Complete the configuration

After answering the configuration questions in regular mode or running in easy mode, the Configurator performs the actual configuration of the Aperi components. This involves setting values in properties files as well as generating startup scripts for the various components. The names of the properties files and the startup scripts are displayed for you in the command prompt window. Only information about the components you chose to configure will appear in the messages.

Ready to configure. 
   
   Configuring the agent... 
   ../agent/configuration/setup.properties 
   ../agent/configuration/agent.config 
   ../agent/agent.bat 
   
   Configuring database_name... 
   ../db/aperi-schema.bat OR
   ../derby/aperi-schema.bat 

   Configuring the device server... 
   devsvr/configuration/setup.properties 
   devsvr/configuration/tsnmdbparms.properties 
   ../devsvr/devsvr.bat 
   
   Configuring the data server... 
    datasvr/configuration/server.config 
    ../datasvr/datasvr.bat 
   
   Configuring the gui... 
   ../gui/gui.bat 
   
   Generating start script... 
   aperi.bat

The Configurator then generates a GUID (or UUID) for your host and stores it in guid.txt in the root directory of your installation. The GUID is also displayed:

Generating GUID for this host... 
GUID is 2a185e9d-07ed-40c9-a120-87b9a789143f 
Storing in c:\aperi\guid.txt

Next, the Configurator creates the Aperi schema. If you are using Derby for the database repository, the Configurator will start the Apache Derby server and run the aperi-schema script it created in the <aperi_install_directory>\derby subdirectory. This script creates the schema specified by 'Alter' files in the <aperi_install_directory>\derby\schema directory. The output from aperi-schema is displayed for you to inspect; again, you will have to look and see if it seems to have succeeded.

The following shows a successful database installation:

 Running .\aperi-schema.bat
 ---- 
   Database installation successful. 
 ---- 
   The output above should indicate that the schema was created 
   successfully on your system. If there was an error, 
   Aperi will not function correctly. Consult the installation 
   documentation for more information.

Note that Derby stores the database in a subdirectory of the derby directory. Keep this in mind if you want to back it up, copy it, or delete it. Deleting the database directory is the Derby equivalent of DROP DATABASE. Also, the Configurator generates derby\aperi-ij.bat, which you can run in a Command Prompt window to enter interactive SQL statements against the Derby server.

If the schema already exists, the Configurator will exit with an error message. If you wish, you can delete derby\Aperi and rerun the Configurator.

Upon completing the configuration of all the selected components, the following message is displayed:

   To bring up the Aperi server and agent, run aperi.bat. 
   To start the GUI, run gui/gui.bat. 
   Aperi configuration is complete.

5.5 Edit configuration files

Use a text editor to edit configuration files to further customize Aperi Storage Manager according to the standards at your site. These files reside in subdirectories under the \aperi_install_directory\ directory, where aperi_install_directory represents the directory where you installed Aperi. Use the information in the following table to learn about the parameters that you can edit in these configuration files:

Configuration file

Location and parameter descriptions

server.config

Edit this file to configure the Data server in your environment.

Location of file: \aperi_install_directory\datasvr\configuration\

[controller]

name: the name of the Data server (host computer name).
port: Port on which the server listens for requests (9549).
maxConnections: Maximum number of concurrent sockets that the server will open (500).
routerThreads: Number of threads redirect incoming requests to the appropriate service provider (1).
serviceThreads: Number of threads to allocate for the Server internal service provider (2).
agentErrorLimit: Number of consecutive attempts to reach an agent before the agent is displayed as DOWN. When an agent is in this state, no attempts to connect are made until either the agent contacts the Server or the agent status is manually changed to UP (3).
adminGroup: Name of the group a user must be a member of in order to perform administrative functions from the Graphic User Interface. The default administrative groups are:
- Windows: Administrator
- UNIX/Linux: adm
If the default administrative group in this parameter does not match a group in your environment, or you want to use a different group, you can:
- create a group in your environment that matches the one defined in this parameter
- change the value in this parameter to match an existing group in your environment
commEncrypted: Switch that secures communication between the Server/Agent and the Server/GUI by encrypting the data stream:
- 0 = Off. Do not encrypt the data stream.
- 1 = On. Encrypt the data steam.

[logging]

logsKept: Number of server logs to keep (5).
messagesPerLog: Maximum number of messages in a log, when this number is reached the log is closed and a new log is created (100,000).

[repository]

driver: Name of the JDBC driver to use, normally:
- DB2: com.ibm.db2.jcc.DB2Driver
- Cloudscape: com.ibm.db2j.jdbc.DB2jDriver
url: URL used to connect to the database, normally: "jdbc:db2://machine_name:50000/Aperi".
user: User name that Aperi uses to connect to its database repository.
schema: Name of the Aperi schema in the database repository.
connectionPool: Number of database connections in a pool of reusable open connections (10).

scheduler.config

Edit this file to configure the Data server scheduler in your environment. The scheduler deploys all monitoring activities and controls when monitoring jobs are run by agents.

Location of file: \aperi_install_directory\datasvr\configuration\

[concurrency]

maxSubmitThreads: Number of threads to create that handle the submission of jobs (3).
maxCompleteThreads: Maximum Number of threads to create to handle job completions. Initially will create a pool of 1/2 the number that can grow to the maximum (3).

[jobs]

minutesAdvanced: Number of minutes in advance of scheduled time to begin the scheduling process. This allows for the overhead time involved in scheduling a job so that the job will actually start close to the scheduled time (1) .

Aperi.config

Edit this file to configure the user interface and how it processes requests.

Location of file: \aperi_install_directory\datasvr\configuration\

[server]

threadPoolSize: Number of initial threads to create for handling requests (3).
maxThreads: Maximum number of threads allowed for handling requests (8).
pingReceiveTimeout: Number of seconds to wait before indicating that a ping has failed (10).

[gui]

threadPoolSize: Number of initial threads to create for handling user interface requests (3).
maxThreads: Maximum number of threads allowed for handling user interface requests (10).
reportRowLimit: Maximum number of rows that will be sent at a time to the user interface. If this number is exceeded, a More button will be displayed above the table, along with a warning message (5000).
keepCachedReport: Number of minutes to retain incomplete reports in the server's tmp directory (120).

nas.config

Location of file: \aperi_install_directory\datasvr\configuration\

Edit this file to configure Aperi for use with NAS:

On each line not beginning with #, the first blank-delimited field must contain the SNMP Enterprise code of a NAS filer that the agent should discover, probe, or scan.
The second field contains identifying information about the filer..

Any remote host that cannot be reached by SNMP or whose enterprise code does not match one of these values will be ignored.

agent.config

Edit the agent.config file to configure the agents in your environment. This file appears in the agent install directory on every machine where an agent is installed.

Location of file: \aperi_agent_install_directory\agent\configuration\

messagesPerLog: Maximum number of messages in a log, when this number is reached the log is closed and a new log is created (100,000).
serverPort: Port on which the Data server listens for requests (9549).
logFilesKept: Number of agent logs to keep (5).
uptimePoll: How often (in seconds) should agent check to ensure it is up (20).
sendFailWait: How many seconds to wait before attempting to resend a message to the server (30).
agentPort: Port on which the agent listens for requests (9550).
maxBacklog: Maximum number of uncompleted jobs to allow in the agent. Any requests for additional jobs to be run will result in an error (500).
honorSentScripts: If this parameter is set to '1', 't', 'T', 'y', or 'Y', the agent can run scripts sent from server. Otherwise, only existing scripts in the agent's scripts directory can be run.
agent.port
installLocation: The directory where Aperi is installed.
maxIdleThreads: Maximum number of idle threads to retain for reuse by future jobs (10).
serverHost: Host computer on which the Data server resides.

6. Start Aperi Storage Manager

This section describes how to start Aperi Storage Manager's user interface, server, and agent components. Make sure you have run the Configurator before performing the steps in this section.

6.1 Start the Aperi Storage Manager Server, Agent, Report server, and Database Repository

Perform the following steps to start the Aperi Storage Manager server, agent, and database repository components at the same time.

Note: You can also use the steps described here to start up an agent or server on a machine where other Aperi Storage Manager are not installed. For example, you can perform these steps to start up an agent on a machine where only an agent is installed.

Start a command line session on the machine where Aperi Storage Manager components are installed.
Change to the directory where you unzipped Aperi Storage Manager by typing cd [aperi_install_directory].
Type the following in the command line and press Enter:
- Windows: aperi
- Linux: ./aperi
The aperi script was created by the configurator and saved to the top level of the Aperi Storage Manager installation directory. When you run the aperi script, the following components will be started (under Windows each component will be started in its own command line session that appears on top of the main command line session):
1. Apache Derby (this step is not run if you are using DB2 for the repository)
2. Device server
3. Data server
4. local agent
5. report server
A prompt will appear in the main command line session after each component is started. Components not installed on the machine where you run the startup will be skipped.
Press any key in the main command line session after each component starts. Note that on Windows the command line sessions for each started component will appear on top of the main command line session. You must switch focus back to main command line session after each component starts before you press a key to start the next component.

Alternatively, perform the following steps to start the server, agent, and database repository individually instead of at the same time.

Start a command line session on the machine where an Aperi Storage Manager component is installed. You must start a separate command-line session for each component you want to start.
Change to the directory where you unzipped Aperi Storage Manager. For example: c:\aperi
Perform the following from different command line sessions depending on what components you want to start:
- To start the database repository (Derby): Change to the \aperi_install_directory\derby directory, type derby.bat, and press Enter.
- To start the database repository (DB2): Use the DB2 Control Center.
- To start the Device server: Change to the \aperi_install_directory\devsvr directory, type devsvr.bat, and press Enter.
- To start the Data server: Change to the \aperi_install_directory\datasvr directory, type datasvr.bat, and press Enter.
- To start the local agent: Change to the \aperi_install_directory\agent directory, type agent.bat, and press Enter.
  where \aperi_install_directory\ represents the directory where you installed the Aperi files.
- To start the report server: Change to the \aperi_install_directory\reporting directory, type reporting.bat, and press Enter.
  where \aperi_install_directory\ represents the directory where you installed the Aperi files.

6.2 Start the Aperi Storage Manager User Interface

Perform the following steps to start the Aperi Storage Manager user interface. You must start up the other components first as described in Starting the Aperi Storage Manager Server, Agent, and Database Repository before you can use the user interface. To start the user interface:

Start a command line session on the machine where you want to start the user interface.
Change to the directory where you unzipped Aperi Storage Manager. For example: c:\aperi
Change to the \rcpgui directory.
Type AperiRcpGui in the command line and press Enter.

7. Shut Down Aperi Storage Manager

To shut down an Aperi Storage Manager component you can:

Press ctrl+c in a command prompt window for the component you want to shut down or
Close the command prompt window for the component you want to shut down
(for Derby) We recommend running the derby/derbystop command instead. This will ensure that Derby frees its ports when shutting down.
(for DB2) Use the DB2 Control Center if you want to stop DB2.

We recommend shutting down components in the following order:

user interface
report server
local agent
Device server
Data server
database repository (Apache Derby or DB2)

8. Uninstall Aperi Storage Manager

To uninstall Aperi:

Shut down any Aperi components that are running. See Shut Down Aperi Storage Manager for instructions on how to shut down Aperi components.
Delete the Aperi installation directory.

9. Perform post-installation configuration

After you have installed Aperi, you must configure your system to get the information you want. This section provides information about the agents required, the jobs that must be run, and the alerts you can set.

9.1 Overview

To enable data gathering from the devices and servers that will be managed and monitored, different configuration steps are required to enable these different functions in Aperi. Aperi uses four different types of agents to gather data about the devices and servers that will be managed and monitored. Different combinations of these agents are required to effectively enable the functions of Data Manager, Fabric Manager, Disk Manager, and Tape Manager. In addition to these manager functions, the topology viewer is greatly affected by the proper discovery of all the managed entities in the management scope of Aperi.

The agents are:

SMI-S Providers (CIM Agents): These agents are provided by the vendor of the storage device or tape library. For storage, they are needed for collecting storage asset information. For tape libraries, they are used for asset and inventory information. Each vendor of the storage or tape library supplies unique CIM agent code for their family of devices. These agents implement an SMI-S provider that conforms to the SNIA SMI-S specification to provide a communication transport between Aperi and the managed devices. Once a CIM agent is installed and configured, Aperi can be configured to communicate with it.

When setting up your CIM agents for managing devices, it is recommended that you read the CIM agent documentation first. This documentation can provide guidelines for how many devices the CIM agent can be configured to manage. If the CIM agent documentation does not include such guidelines, it is recommended to limit three subsystems per CIM agent.
Data agents: These agents are installed on all the computer systems that you want Aperi to manage. These agents collect information from the server they are installed on. Asset information, file and file system attributes, and any other information needed from the computer system is gathered. Data agents can also gather information on database managers installed on the server, Novell NDS tree information, and NAS device information. You can create pings and probes to run against the machines that have Data agents installed.
Fabric agents: These agents are installed on computer systems that have fiber connectivity (through HBAs) into the SAN fabrics you want to manage and monitor. Fabric agents use scanners to collect information. The scanners communicate through the HBA to collect fabric topology information, port state information, and zoning information. They also can identify other SAN-attached devices (if they are in the same zone). Fabric agents are discovered during the agent installation process and do not need to be discovered separately. A best practice is to have two agents connected to each switch for redundancy.
Out-of-band agents: The out-of-band agents are used to collect topology information from fabric switches through the IP network using SNMP queries to the switches. A best practice is to have Aperi communicating with the out-of-band agent (SNMP agent) on each switch in each SAN fabric you are managing.

Aperi uses data collection jobs to provide information about your environment. The types of data collection jobs are:

Discovery jobs: These jobs locate "data sources" and collects basic information about these data sources. When a discovery job is run against a storage subsystem CIM agent, the job will locate all the storage subsystems "behind" this CIM agent and will retrieve all information the CIM agent holds for these systems. When a discovery job is run against a fabric, the job will retrieve all available information for the fabric if supported by the switches.
Probe jobs: These jobs collect detailed statistics on all the assets of the managed infrastructure, such as computers, disk controllers, hard disks, clusters, fabrics, storage subsystems, LUNs, tape libraries, filesystems, and so on. Probe jobs can also discover information about new or removed disks and filesystems. Probe jobs can be directed against any element in the managed infrastructure. There are four types of probe jobs: for computers, fabrics, storage subsystems, and tape libraries.
- Computer probe jobs collect local host information such as file systems, directories, clusters, hard disks and so on.
- Storage subsystem probe jobs collect information about the storage subsystems, such as disk, volumes, LUNs and so on.
- Fabric probe jobs collect information about the fabric.
- Tape library probe jobs collect information about the tape libraries.
  
  Note: When probing storage subsystems that are registered with the same CIM agent, do not probe more than three storage subsystems within the same probe job because the increased load on the agent would increase the likelihood of time-outs. Instead, spread the storage subsystems across multiple probe jobs with different starting times.
Ping jobs: These jobs gather statistics about the availability of the managed computers. Ping jobs generate TCP/IP pings and consider the computer available if it gets an answer. Ping jobs can be directed against computers only.

You can define alerts so that Aperi notifies you when a specified event occurs. Such events are the triggering conditions for the alert. The specific triggering conditions that you can use to define an alert depend on the sort of storage resource that you are monitoring. The alerts you can define are:

Computer alerts: Use these alerts to be notified when a condition is detected on a computer during a probe job. Examples of computer alerts are when RAM is increased or decreased, virtual memory is increased or decreased, or when a new disk is detected or not found. Use Data Manager to define these alerts.
Filesystem alerts: Use these alerts to be notified when a condition is detected on a file system during a probe job. Examples of file system alerts are when the file system is not found or reconfigured or is low on free space. Use Data Manager to define these alerts.
Storage subsystem alerts: Use this alert to be notified when a condition is detected on a storage subsystem during a probe job. Examples of storage subsystem alerts are when a storage subsystem is discovered or not found, a subsystem cache is increased or decreased, a disk is detected or not found, or a subsystem goes offline or online. Use Disk Manager to define these alerts.
Fabric alerts: Use these alerta to be notified when a condition is detected on a fabric during a probe job. Examples of fabric alerts are if a fabric is missing or discovered, a fabric goes online or offline, a zone is missing or discovered, or a zone set is missing or discovered. Use Fabric Manager to define these alerts.
Switch alerts: Use these alerts to be notified when a condition is detected on a switch during a probe job. Examples of switch alerts is if a switch is missing or discovered, a switch goes online or offline, a switch blade is missing or discovered, or a switch blade goes online or offline. Use Fabric Manager to define these alerts.
Endpoint device: Use these alerts to be notified when a condition is detected on an endpoint device during a probe job. Endpoint devices are devices discovered by the Fabric Manager but cannot be identified as a specific device type, such as a computer or subsystem. Examples of endpoint device alerts are when an endpoint device is missing or discovered, a peripheral entity to node association is missing or discovered, or the version for an endpoint device changes. Use Fabric Manager to define these alerts.

Once you have defined alerts, you can choose to be notified through different methods:

SNMP trap: Generate an SNMP trap message to any console or terminal to indicate the occurrence of an alert.
Login notification: Send alerts to a specified user upon logging in to Aperi.
Windows� Event Log, UNIX� Syslog: Record alerts to the OS Event Log. If you already have an administrator monitoring OS logs, this is an easy way to have all of your priority messages centralized for quick notification and viewing.
Run script: Run a script in response to an alert.
E-mail: Send alerts through e-mail to e-mail addresses that you specify.

9.2 Using the Configuration Utility

Use the Configuration Utility tool in the Aperi GUI as a teaching tool to help guide you through the steps and prerequisite steps required to configure Aperi for your environment:

If you are a new user of Aperi, use the Configuration Utility to learn what the common functions are and to help you with the task of deciding what agents you need and which jobs to run to get the information you want.
If you are an experienced Aperi user, you can go to the GUI directly to perform all of the configuration tasks. However, you might also want to use the Configuration Utility to provide you with a quick summary review of your system.

All of the main Aperi functions shown in the Configuration Utility exist separately within the Aperi GUI. However, the Configuration Utility provides a single point of access for new users to work with these functions. It also provides information that can help you decide what agents you need and which jobs to run to get the information you want about your storage environment. For example, it provides links into the Aperi GUI to display reports, add agents, create jobs, and create alerts.

To access and use the Configuration Utility:

Start Aperi.
Click Aperi Storage Manager > Configuration Utility. The Configuration Utility window appears in the right pane. You can access different pages within the Configuration Utility depending on what information you want to view, collect, and configure:

9.2.1 Managing Aperi agents and servers on the Services page

Click the Services tab to manage your servers and agents. Use this page to view a list of the Data server, Device server, Data agents, CIM agents, in-band Fabric agents, and out-of-band Fabric agents. You can use these lists to view detailed information about servers and agents, start agents, check agents (to make sure they are up and are the most current version), and run discovery jobs.

9.2.2 Manging storage asset (computers, filesystems, etc.) on the Data Manager page

Click the Data Manager tab to perform the following tasks:

Task	Description
Data Agents
View information about Data agents	Show detailed information about Data agents, check Data agents to make sure they are up and are the most current version, and start Data agents.
Ping
Collect availability information about storage assets	Run pings to collect information about the availability of storage assets monitored by Aperi in your environment. Click Show Ping Job Details to display information about the latest ping job. Click Run Default Ping Now to run a ping using the default settings. A pop-up window informs you that the job has been submitted. Click OK. The TPCUser.Default ping job status panel is displayed when the ping job is completed. Click Create Ping to create and run a new ping job
Collect availability information about storage assets	Run pings to collect information about the availability of storage assets monitored by Aperi in your environment. Click Show Ping Job Details to display information about the latest ping job. Click Run Default Ping Now to run a ping using the default settings. A pop-up window informs you that the job has been submitted. Click OK. The TPCUser.Default ping job status panel is displayed when the ping job is completed. Click Create Ping to create and run a ping job with settings that you define.
Display availability reports	Use Availability reports to view the information collected by pings, both from a network point of view and from a computer up-time perspective. This enables you to see what percentage of the time the storage in your enterprise (or on particular server or group of servers), is off-network due to network problems or perhaps is unavailable due to system downtime. Click Show Storage Availability System Report to generate and view the pre-defined Storage Availibility system report. Click Define Storage Availability Report customize and generate an availability report.
Computer Probes
Collect detailed information about storage assets	Run probes to collect detailed information about computers. Click Probe Default Computer Group Now to create and run a probe job against the computers in the default computer monitoring group. A pop-up window prompts you for a job name. Enter a job name and click OK. A pop-up window informs you that the job has been submitted. Click OK. The probe job status panel is displayed when the job is completed. Click Create Probe to create and run a probe job with settings that you define. Click Computers Topology to display the computers topology.
Display computer asset reports	Click Show Computer Asset Report to view the information collected by probes. While running probes, Aperi itemizes the information about your computers and builds a hardware inventory of your storage assets.
Alerting
Create and view alerts	Define alerts to notify when you when certain conditions on a computer or filesystem occur. Use logs to view information that is triggered by alerts. Click Computer Alert to create a computer alert. Click Filesystem Alert to create a filesystem alert. Click Computer Alerts to view the computer alerts that have been triggered. Click Filesystem Alerts to view the filesystem alerts that have been triggered.

9.2.3 Managing storage subsystems and CIMOMs on the Disk Manager page

Use this page to view the storage subsystems managed by Aperi. Click the Disk Manager tab to perform the following tasks:

Task	Description
Storage Subsystems
View information about storage subsystems	View information about the storage subsystems that have been discovered through a CIMOM discovery. If a storage subsystem is not shown in the table, the CIM agent for that subsystem needs to be added and a CIMOM discovery needs to be run. Click Show Storage Subsystem Details to generate and view a report about the selected storage subsystem. Click Show Storage Subsystem Asset Report to view the information collected by probes. While running probes, Aperi itemizes the information about your storage subsystems and builds a hardware inventory of your storage assets. Click Storage Topology to display the storage subsystems topology.
CIMOM Discovery
Locate CIMOMs in your envionment	View information about the CIM agents discovered by Aperi. CIM agents are required for the storage subsystems to be discovered. A CIMOM discovery finds all the devices managed by the known CIM agents and gathers basic information about these devices. A CIM agent managing the storage subsystem and CIMOM discovery are required to discover storage subsystems in the environment. Click Run CIMOM Discovery Now to create a CIMOM discovery job using all of the defined CIM agents. The job is run immediately. When you run the job, a pop-up window prompts you for the job name. Enter a job name and click OK. A pop-up window informs you that the job has been submitted. Click OK. The results are displayed when the job has completed. Click Edit CIMOM Discovery to edit the CIMOM discovery job information.
Storage Subsystem Probes
Collect detailed information about storage assets	Run probes to collect detailed information about storage subsystems. Click Probe Default Storage Subsystem Group Now to create and run a probe job against the storage subsystems in the default storage subsystem monitoring group. A pop-up window prompts you for a job name. Enter a job name and click OK. A pop-up window informs you that the job has been submitted. Click OK. The probe job status panel is displayed when the job is completed. Click Create Probe to create and run a probe job with settings that you define.
Alerting
Create and view alerts	Define alerts to notify when you when certain conditions on a computer or filesystem occur. Use logs to view information that is triggered by alerts. Click Storage Subsystem Alert to create a storage subsystem alert. Click Storage Subsystem Alerts to view the storage subsystem alerts that have been triggered.

9.2.4 Managing fabrics and CIMOMs on the Fabric Manager page

Use this page to view the fabrics and switches managed by Aperi, discover fabrics, CIMOMs, and out-or-band Fabric agents, and run probes to collect information about fabrics. Fabric zoning functions require a switch within that fabric to either have an in-band agent or an out-of-band agent. The agents for the switch must have been discovered by Aperi and a probe run for the fabric.

Click the Fabric Manager tab to perform the following tasks:

Task	Description
Fabrics
Configure and view information about fabrics	Click Zoning Configuration to configure the selected fabric. Click Show SAN Assets (ALL) System Report to generate and view a pre-defined system report that shows detailed information about monitored fabrics. Click Fabrics Topology to display the fabrics topology.
Switches
View information about switches	Click Show SAN Assets (Switches) System Report to generate and view a pre-defined system report that provides information about switches in your SAN (including switch ID, type, manufacturer, WWN, location, and other details). Click Switches Topology to display the switches topology.
CIMOM Discovery
Locate CIMOMs in your envionment	View information about the CIM agents discovered by Aperi. Click Run CIMOM Discovery Now to create a CIMOM discovery job using all of the defined CIM agents. The job is run immediately. When you run the job, a pop-up window prompts you for the job name. Enter a job name and click OK. A pop-up window informs you that the job has been submitted. Click OK. The results are displayed when the job has completed. Click Edit CIMOM Discovery to edit the CIMOM discovery job information.
Out of Band Fabric Discovery
Locate CIMOMs in your envionment	View information about the CIM agents discovered by Aperi. Click Run Out of Band Discovery Now to create an out of band discovery job using all of the defined out-of-band agents The job is run immediately. When you run the job, a pop-up window prompts you for the job name. Enter a job name and click OK. A pop-up window informs you that the job has been submitted. Click OK. The results are displayed when the job has completed. Click Edit CIMOM Discovery to edit the discovery job information.
Inband Fabric Discovery
View information about Inband Fabric Agents	View information about the Inband Fabric agents that are required for zone configuration. Aperi automatically runs a discovery job when it detects that an Inband Fabric agent has come online. See the Services page for more information about the servers and agents.
Fabric Probes
Collect detailed information about fabrics	Run probes to collect detailed information about fabrics. collect fabrics topology and zoning information, as well as basic information about the devices attached to the fabric. Click Probe Default Fabric Group Now to create and run a probe job against the fabrics in the default computer monitoring group. A pop-up window prompts you for a job name. Enter a job name and click OK. A pop-up window informs you that the job has been submitted. Click OK. The probe job status panel is displayed when the job is completed. Click Create Probe to create and run a probe job with settings that you define.
Alerting
Create and view alerts	Define alerts to notify when you when certain conditions on a fabric, switch, or endpoint device occur. Use logs to view information that is triggered by alerts. Create Alert Definitions: Click Fabric Alert to create a fabric alert. Click Switch Alert to create a switch alert. Click Endpoint Device Alert to create an endpoint device alert. View Alert Logs: Click Fabric Alerts to view the fabric alerts that have been triggered. Click Switch Alerts to view the switch alerts that have been triggered. Click Endpoint Device Alerts to view the endpoint device alerts that have been triggered.

9.2.5 Managing tape librabries and CIMOMs on the Tape Manager page

Use this page to view the tape libraries managed by Aperi, discover CIMOMs, and run probes against tape libraries. A CIMOM discovery job and a tape library probe job are required before Aperi can monitor your tape libraries. If you do not see a tape library listed in the table, you need to run a CIMOM discovery job for the tape libraries.

Click the Tape Manager tab to perform the following tasks:

Task	Description
Tape Libraries
View information about tape libraries	View information about the tape libraries that have been discovered through a CIMOM discovery. If a tape library is not shown in the table, you must run a CIMOM discovery job and a tape library probe job. Click Show Tape Library Details to generate and view a report about the selected storage subsystem. Click Storage Topology to display the tape library topology.
CIMOM Discovery
Locate CIMOMs in your envionment	View information about the CIM agents discovered by Aperi. CIM agents are required for the tape libraries to be discovered. A CIMOM discovery finds all the devices managed by the known CIM agents and gathers basic information about these devices. Click Run CIMOM Discovery Now to create a CIMOM discovery job using all of the defined CIM agents. The job is run immediately. When you run the job, a pop-up window prompts you for the job name. Enter a job name and click OK. A pop-up window informs you that the job has been submitted. Click OK. The results are displayed when the job has completed. Click Edit CIMOM Discovery to edit the CIMOM discovery job information.
Tape Library Probes
Collect detailed information about storage assets	Run probes to collect detailed information about tape libraries. Click Probe Default Tape Library Group Now to create and run a probe job against the tape libraries in the default tape library monitoring group. A pop-up window prompts you for a job name. Enter a job name and click OK. A pop-up window informs you that the job has been submitted. Click OK. The probe job status panel is displayed when the job is completed. Note: A warning message is displayed notifying you that this is not recommended when there are several tape libraries known to the system and they are all listed in the default group. If you have a lot of tape libraries, this could take a long time to probe. Click Create Probe to create and run a probe job with settings that you define.

10. Grant local administrative privileges to a domain account

For Windows users, the user account which the Data server runs under requires local administrative rights. Because these rights are not necessarily guaranteed for domain users in a Windows domain environment, this topic provides information on how to grant local administrative rights for domain users. Using this procedure, you do not have to manually process each machine in the domain.

To use Group Policy to grant local administrative privileges to a domain account, complete the following steps:

On the domain controller, go to Administrative Tools > Active Directory Users and Computers (you must be running with Domain Administrator privileges).
Right-click on the Organizational Unit (OU) upon which you want to apply the Group Policy. Click Properties.
The Group Policy Properties panel is displayed. Select the Group Policy tab and click New to create a new Group Policy.
Designate a name for the new Group Policy. Select the new Group Policy and click Edit.
The Group Policy Object Editor panel is displayed. Go to New Group Policy Object > Computer Configuration > Windows Settings > Security Settings > Restricted Groups. Right-click on Restricted Groups. Click Add Group.
For example, name the new group "Administrators." Under "Properties", add the user "Administrator", and the domain accounts or groups upon which you want the Group Policy in effect for. For example, you can add "APERI apeadmin", "APERI apegroup", and "APERI\TestGroup". Click OK.
Add these user rights to the domain account:
- Act as part of the operating system
- Log on as a service
In the Group Policy Object Editor, go to New Group Policy Object > Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Assignments. In the right pane, select "Log on as a service" and double-click. Add the domain user for whom you are granting the user right for and click OK. Repeat this step for "Act as part of the operating system."
The group policy is now enforced for the Organizational Unit to include the domain accounts and groups specified under the local Administrators group on each computer in the Organizational Unit. In addition, the domain user has been granted the necessary rights. To verify this, log into a domain computer and open the Computer Management console. Select Groups, double-click on the Administrators group, and verify the membership of the domain users.

Notices

Aperi Storage Manager (C) Copyright IBM Corp. 2007. All Rights Reserved
All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html.

Eclipse

Aperi Storage Manager Installation Instructions

Contents

1. Plan the deployment

2. Check install requirements

3. Plan for the database repository

4. Install Aperi Storage Manager files

5. Configure Aperi Storage Manager

5.1 Start the Configurator

5.2 Use the Configurator (regular mode)

5.3 Use the Configurator (easy mode)

5.4 Complete the configuration

5.5 Edit configuration files

6. Start Aperi Storage Manager

6.1 Start the Aperi Storage Manager Server, Agent, Report server, and Database Repository

6.2 Start the Aperi Storage Manager User Interface

7. Shut Down Aperi Storage Manager

8. Uninstall Aperi Storage Manager

9. Perform post-installation configuration

9.1 Overview

9.2 Using the Configuration Utility

9.2.1 Managing Aperi agents and servers on the Services page

9.2.2 Manging storage asset (computers, filesystems, etc.) on the Data Manager page

9.2.3 Managing storage subsystems and CIMOMs on the Disk Manager page

9.2.4 Managing fabrics and CIMOMs on the Fabric Manager page

9.2.5 Managing tape librabries and CIMOMs on the Tape Manager page

10. Grant local administrative privileges to a domain account

Notices