ETERNUS SF Disk Space Monitor User's Guide - Microsoft(R) Windows Server(TM) 2003/Solaris(TM) Operating System/Linux - 13.0

4.1 Simple Installation

This section explains how to set up the following functions:

• Manager
• Agent
• Operation management client

The explanations in this section assume that the system will manage resource information within the server by using the "Push" method as communication mode.

Install and set up this product in the following order:

The setup explanations in this section follow this order. Perform these operations in the same order as they are presented.

4.1.1 Tasks required for Manager installation

This section explains how to install the Manager. The installation procedure is as follows:

The explanations in this section follow this procedure. Perform these installation and setup operations in the same order as they are presented.

4.1.1.1 Installation

4.1.1.1.1 Installation conditions 

Refer to Chapter 3, "Installation Conditions and Resource Estimation" for the installation conditions.

4.1.1.1.2 Pre-installation preparations 

When the installer starts, it prompts the user to specify the following items. Therefore, before starting the installation process, check or decide which settings to use.

No.	Prompt item	Description
1	Installation directory	This is the path to the directory where fixed resources such as execution modules are installed.
2	Variable file directory	This is the path to the directory where files that change during operation are stored.

No.	Prompt item	Description
1	Installation directory	This is the path to the directory where fixed resources such as execution modules are installed.
2	Definition file directory	This is the path to the directory where definition files that are referenced during operation are stored.
3	Variable file directory	This is the path to the directory where files that change during operation are stored.

4.1.1.1.3 Installation procedure

The installation procedure is as follows:

1. Log in to the Windows machine using an account with Administrator privileges.
2. Insert the CD-ROM for this product into the CD-ROM drive.
3. The installer will start automatically.

   

   On some machines, the installer may not start automatically. In this case, start the installer manually using the following procedure:

   • Select Run from the Start menu.
   • In the Run window, click the Browse button, select the following file, and then click OK.

     CD-ROM drive:\dsmSetup.exe

     
     
   • The installer will start automatically.
4. Click the Install Manager button in the installer window.
5. The installer will start, and the prompts explained in the previous section will appear.

1. Log in to the Solaris machine as a superuser.
2. Mount the CD-ROM.
   • Insert the CD-ROM into the drive.
   • The CD-ROM drive may be mounted automatically by the volume management daemon.
     If not, perform the following operations:

     # mkdir -p /cdrom/cdrom0 (*1)

     # /usr/sbin/mount -F hsfs -o ro /dev/dsk/cntndnsn /cdrom/cdrom0 (*2)

     #

     *1: This step is required only if the /cdrom/cdrom0 directory does not exist.

     *2: Adjust "n" in "cntndnsn" to match the CD-ROM drive on the machine where the program will be installed.

     
     
3. Execute the shell script for installing the program. An execution example is shown below. In this example, the name of the CD-ROM drive is "/cdrom/cdrom0".

   # cd /cdrom/cdrom0/FJSVssqc/manager/packages

   # ./install.sh

4. The installer will start, and the prompts explained in the previous section will appear.

1. Log in to the Linux machine as a superuser.
2. Mount the CD-ROM.
   • Insert the CD-ROM into the drive.
   • The CD-ROM drive may be mounted automatically by the volume management daemon.
     If not, perform the following operations:

     # mount -r -t iso9660 /dev/cdrom /mnt/cdrom (*1)

     *1 Change "/mnt/cdrom" depending on the CD-ROM drive location in the installation environment.

     
     
3. Execute the shell script for installing the program. An execution example is shown below. In this example, the name of the CD-ROM drive is "/mnt/cdrom".

   # cd /mnt/cdrom/FJSVssqc/manager/packages

   # ./install.sh

4. The installer will start, and the prompts explained in the previous section will appear.

4.1.1.2 How to start and verify the program

Start the program by referring to Chapter 5, "How to Start and Stop Resident Processes". Also, check that resident processes are running normally.

4.1.2 Tasks required for Agent installation 

This section explains how to install Agent functions.

The installation procedure is as follows:

The explanations in this section follow this procedure. Perform these installation and setup operations in the same order as they are presented.

4.1.2.1 Installation

4.1.2.1.1 Installation conditions 

Refer to Chapter 3, "Installation Conditions and Resource Estimation" for the installation conditions.

4.1.2.1.2 Pre-installation preparations 

When the installation process starts, it prompts the user to specify the following items. Therefore,

before starting the installation process, check or decide which settings to use.

No.	Prompt item	Description
1	Installation directory	This is the path to the directory where fixed resources such as execution modules are installed.
2	Variable file directory	This is the path to the directory where files that change during operation are stored.
3	Alert action when thresholds are exceeded	Select either "syslog" (output message to the event log) or "centric" (Centric Manager event linkage) as the alert action taken when thresholds are exceeded. If "Centric Manager event linkage" is selected, alerts will be sent to Centric Manager when thresholds are exceeded. For this option, Systemwalker Centric Manager must be installed on this same machine.
4	Manager address	This is the host name or IP address of the Manager that this Agent will connect to. If the Manager has a cluster configuration, specify either a logical host name or a logical IP address.
5	Method for sending data to the Manager	Select whether the data collected by the Agent is to be "pushed" to the Manager or "pulled" from the Manager. Normally select "push".

No.	Prompt item	Description
1	Installation directory	This is the path to the directory where fixed resources such as execution modules are installed.
2	Definition file directory	This is the path to the directory where definition files that are referenced during operation are stored.
3	Variable file directory	This is the path to the directory where files that change during operation are stored.
4	Alert action when thresholds are exceeded	Select either "syslog" (output message to the event log) or "centric" (Centric Manager event linkage) as the alert action taken when thresholds are exceeded. If "Centric Manager event linkage" is selected, alerts will be sent to Centric Manager when thresholds are exceeded. For this option, Systemwalker Centric Manager must be installed on this same machine.
5	Manager address	This is the host name or IP address of the Manager that this Agent will connect to. If the Manager has a cluster configuration, specify either a logical host name or a logical IP address.
6	Method for sending data to the Manager	Select whether the data collected by the Agent is to be "pushed" to the Manager or "pulled" from the Manager. Normally select "push".

4.1.2.1.3 Installation procedure

The installation procedure is as follows:

1. Log in to the Windows machine using an account with Administrator privileges.
2. Insert the CD-ROM for this product into the CD-ROM drive.
3. The installer will start automatically.

   

   On some machines, the installer may not start automatically. In this case, start the installer manually using the following procedure:

   • Select Run from the Start menu.
   • In the Run window, click the Browse button, select the following file, and then click OK.

     CD-ROM drive:\dsmSetup.exe

     
     
   • The installer will start automatically.
4. Click the appropriate button in the installer window.
   • Install Agent
5. The installer will start, and the prompts explained in the previous section will appear.

1. Log in to the Solaris machine as a superuser.
2. Mount the CD-ROM.
   • Insert the CD-ROM into the drive.
   • The CD-ROM drive may be mounted automatically by the volume management daemon.
     If not, perform the following operations:

     # mkdir -p /cdrom/cdrom0 (*1)

     # /usr/sbin/mount -F hsfs -o ro /dev/dsk/cntndnsn /cdrom/cdrom0 (*2)

     #

     *1: This step is required only if the /cdrom/cdrom0 directory does not exist.

     *2: Adjust "n" in "cntndnsn" to match the CD-ROM drive on the machine where the program will be installed.

     
     
3. Execute the shell script for installing the program. Execution examples are shown below. In these examples, the name of the CD-ROM drive is "/cdrom/cdrom0".
   • For Agent

     # cd /cdrom/cdrom0/FJSVssqc/agent/packages

     # ./install.sh

     
     
4. The installer will start, and the prompts explained in the previous section will appear.

1. Log in to the Linux machine as a superuser.
2. Mount the CD-ROM.
   • Insert the CD-ROM into the drive.
   • The CD-ROM drive may be mounted automatically by the volume management daemon.
     If not, perform the following operations:

     # mount -r -t iso9660 /dev/cdrom /mnt/cdrom (*1)

     *1 Change "/mnt/cdrom" depending on the CD-ROM drive location in the installation environment.

     
     
3. Execute the shell script for installing the program. Execution examples are shown below. In these examples, the name of the CD-ROM drive is "/mnt/cdrom".
   • For Agent

     # cd /mnt/cdrom/FJSVssqc/agent/packages

     # ./install.sh

     
     
4. The installer will start, and the prompts explained in the previous section will appear.

4.1.2.2 Setup 

Execute the sqcRPolicy and sqcSetPolicy commands by referring to Chapter 13, "Creating and Applying Collection Policies".

To collect disk-related performance information for Windows systems, first enable information collection by executing the diskperf Windows command, as shown in the following example:

diskperf -y

Refer to the Windows Help files for details on the diskperf command. Be sure to enable information collection for both physical and logical drives.

• For the diskperf command, the system must be restarted after the settings have been made.
• The diskperf command must be executed before the ETERNUS SF Disk Space Monitor DCM service is started (that is, before performance information starts being collected).

4.1.2.3 How to start and verify the program 

Start the program by referring to Chapter 5, "How to Start and Stop Resident Processes". Also, check that resident processes are running normally.

4.1.3 Tasks required for operation management client installation

This section explains how to install the operation management client. The installation procedure is as follows:

The explanations in this section follow this procedure. Perform these installation and setup operations in the same order as they are presented.

4.1.3.1 Installation 

4.1.3.1.1 Installation conditions 

Refer to Chapter 3, "Installation Conditions and Resource Estimation" for the installation conditions

4.1.3.1.2 Pre-installation preparations 

When the installer starts, it prompts the user to specify the following items. Therefore, before starting the installation process, check or decide which settings to use.

No.	Prompt item	Description
1	Installation directory	This is the path to the directory where fixed resources such as execution modules are installed.
2	Manager address	This is the host name or IP address of the Manager that the operation management client connects to.

4.1.3.1.3 Installation procedure

The installation procedure is as follows:

1. Log in to the Windows machine using an account with Administrator privileges.
2. Insert the CD-ROM for this product into the CD-ROM drive.
3. The installer will start automatically.

   

   On some machines, the installer may not start automatically. In this case, start the installer manually using the following procedure:

   • Select Run from the Start menu.
   • In the Run window, click the Browse button, select the following file, and then click OK.

     CD-ROM drive:\dsmSetup.exe

     
     
   • The installer will start automatically.
4. Click the Install Operation Management Client button in the installer window.
5. The installer will start, and the prompts explained in the previous section will appear.

The procedure for installing the operation management client from the Solaris/Linux edition of the CD is as follows:

1. Log in to the Windows machine using an account with Administrator privileges.
2. Insert the CD-ROM for this product into the CD-ROM drive.
3. Execute the following file:

   CD-ROM drive:\FJSVssqc\tools\DSMSETUP.exe

4. The installer will start automatically.
5. Click the Install Operation Management Client button in the installer window.
6. The installer will start, and the prompts explained in the previous section will appear.

4.1.3.2 Setup 

An HTTP virtual directory and properties for this virtual directory must be set up for the operation management client. Set up this directory by referring to Chapter 16, "Setting up an HTTP Communication Environment".

4.1.3.3 How to start and verify the program

Specify the following URL in a Web browser and check that the Console starts.

http://host name of the operation management client/SSQC/AdminConsole.html

4.1.3.4 Environment setup

Use the following procedure to set up the environment.

1. Open the Setting view. Refer to Section 9.2.1, "Window Configuration" for details.
2. Register the system groups. Refer to Section 9.2.3.1.1, "SystemGroups" for details.
3. Register the Agents. Refer to Section 9.2.3.2, "Unregistered Agent information (UnregisteredAgents)" for details.

After these environments have been set up, the Monitor, Drill Down, and Report views of the Console window can be displayed.

For redundant Manager operations, set up environments for the operation management clients connected to each Manager.

4.1.4 Uninstallation

This section describes the procedure for uninstalling this software.

1. Log in to the machine where the software will be uninstalled with Administrator privileges.
2. Double-click on the Add/Remove Applications or the Add/Remove Programs on the Control Panel.
3. Select the following programs from the application list and click either the Add/Remove button or the Change/Remove button.
   • ETERNUS SF Disk Space Monitor Manager 13.0
   • ETERNUS SF Disk Space Monitor Agent 13.0
   • ETERNUS SF Disk Space Monitor Operation Management Client 13.0
4. Follow the instructions to uninstall the programs.

While uninstalling, when the display targets other windows, the progress bar is hidden behind the window. In that case, please display the window in the progress bar forward by clicking the task of uninstallation in the taskbar and other methods.

When uninstalling the operation management client, OCMM 5.1 (which is installed at the same time) must be uninstalled manually. Select the following program from the application list and click either the Add/Remove button or the Change/Remove button.

• OCMM 5.1

Files that have been added after the installation are also deleted, so back up these files if necessary.

1. Become superuser while on the system.

   # su <RETURN>

2. Execute the pkgrm command.
   • For Agent

     # pkgrm FJSVdsmag <RETURN>

     
     
   • For Manager

     # pkgrm FJSVdsmmg <RETURN>

Files that have been added after the installation are also deleted, so back up these files if necessary.

1. Become superuser while on the system.

   # su <RETURN>

2. Execute the rpm command.
   • For Agent

     # rpm -e FJSVdsmag <RETURN>

     
     
   • For Manager

     # rpm -e FJSVdsmmg <RETURN>