Installing and ConfiguringSPI for Terminal Server

for OVO/Unix(version 01.00)

HERMES SoftLab d.d.

v1.0September 2006

Contents

• Software Requirements• Installation on the Mgmt Server• Verifying Mgmt Server Installation• Configuring Mgmt Server

– Deploying Instrumentation– Licensing Managed Nodes– Verifying Requirements and

Configuration• Installing Reports

– Verifying Reports Installation on OVO/W / Reporter– Configuring Reports on OVO/W / Reporter

• Installing Graphs– Verifying Graphs Installation on OVO/W / OVPM

Software Requirements

• Microsoft Terminal Server:– Windows 2000 Server family– Windows Server 2003 (+R2) family– Windows Server 2003 x64 (+R2) family

NOTE: Microsoft Terminal Server component is a part of Microsoft Windows Server family of operating systems

• HP OpenView:– HP OpenView Operations/Unix 7.17/8.1x/8.2x– HP OpenView Reporter 3.50/3.60/3.70– HP OpenView Performance Manager 5.0/6.0

Installation on the Mgmt Server

1. Login to the Mgmt Server as user root

2. Copy the following files to the /tmp directory:– On HP-UX 11.x systems:

hsl_eulsa_hpux and TSSPI_01.00.eulsa– On Sun Solaris systems:

hsl_eulsa_sun and TSSPI_01.00.eulsa

Installation on the Mgmt Server

3. To obtain the product installation package, you first must agree to the end-user license agreement. From the /tmp directory, run from the command line:– For HP-UX 11.x:

hsl_eulsa_hpux -e TSSPI_01.00.eulsa

– For Sun Solaris:hsl_eulsa_sun -e TSSPI_01.00.eulsa

4. First, you have to enter your name and the name of your company.

5. The standard HERMES SoftLab Software License and Support Agreement will be displayed with your name and the name of your company at the bottom. Read it carefully, type I AGREE, and then press [ENTER] to generate the installation package file TSSPI_01.00.depot and file TSSPI_01.00.eulsa.txt

Installation on the Mgmt Server

5. Install SPI for Terminal Server by executing the platform specific commands:

swinstall -s /tmp/TSSPI_01.00.depot TSSPI

• IMPORTANT: Data Source Integration To Dynamic Data Feed (DSI2DDF) component, version A.01.30 or above, should be installed on the Mgmt Server system if you want to use the reporting functionality.

Verifying Mgmt Server Installation

• 2 node groups• Applications under group “SPI for Terminal Server”

– 47 applications in 11 subgroups• Templates under group “SPI for Terminal Server”

– 57 templates in 22 subgroups• Instrumentation

– Files copied to:DCE agent:

/var/opt/OV/share/databases/OpC/mgd_node/customer/ms/intel/nt/monitorand/var/opt/OV/share/databases/OpC/mgd_node/customer/ms/intel/nt/cmds

HTTPS agent:/var/opt/OV/share/databases/OpC/mgd_node/customer/ms/x86/winnt/cmds

Configuration: Distributing Instrumentation

• Put nodes under management. Terminal Server SPI is able to manage two node types:– Terminal Server nodes– Terminal Server License Server nodes

• Distribute instrumentation– Update Actions, Commands, and Monitors to all nodes

that you want to manage.

• Go to “SPI for Terminal Server/TSSPI-Maintenance/TSSPI-Configure” application group, and execute application “TSSPI-Register Subagent” against every node that you want to manage.

Configuration: Licensing Managed Nodes

• IMPORTANT: Instrumentation needs to be distributed to the managed nodes as specified on the previous slide!

1. Distribute the Licensing Template to the Managed Nodes1. Start the HP OpenView Operations Console and log in as an HP

OpenView Operations Administrator (opc_adm).2. From the Node Bank window, select the node(s) to which you

want to distribute the template to.3. From the menu, select Actions followed by selecting Agents

then Assign Templates. The Define Configuration window opens.

4. Click Add to open the Add Configuration window.5. Click Open Template Window… to open the Message Source

Templates window.

Configuration: Licensing Managed Nodes

6. From the Template Group list, expand SPI for Terminal Server/TSSPI-SPI Licensing group, and then in the right pane, select the TSSPI-Licensing message template.

7. In the Add Configuration window, click Get Template Selections and then [OK]. The selected template is now added to the list of templates in the Define Configuration window.

8. From the menu, select Actions followed by selecting Agents then Install/Update SW & Config…. The Install/Update Software and Configuration window opens.

9. Select the following checkboxes: Templates, Actions, Commands, Monitors and click [OK]. The template required for licensing is installed on the managed node.

Configuration: Licensing Managed Nodes

Generate the License Request File

1. From the Node Bank window, select Window followed by selecting Application Bank. The Application Bank window opens.

2. Go to SPI for Terminal Server/TSSPI-SPI Maintenance/TSSPI-SPI Licensing application group.

3. Run the TSSPI-1. Clear License Request File on Mgmt Server application to clear the tsspi_license_requests.dat license request file on the management server.

Configuration: Licensing Managed Nodes

4. Run the TSSPI-2. Generate License Request for Node application on the managed nodes for which you need licenses. In the Customized Startup-Application window, in the Additional Parameters field, replace the string “your company name” with the name of your company. Press [OK] to generate the license request.

After the tool is executed on all nodes, license requests of all nodes are located on the management server in file:

/opt/OV/tsspi/tsspi_license_requests.dat

Configuration: Licensing Managed Nodes

Obtain the tsspi_licact_new.dat license activation fileYou can obtain the license activation file:• Using the Licensing portal:

Go to http://spi.hermes-softlab.com/licensing/, register, and upload the license request file. When registering, have your PO information ready. The system will automatically process your request and send you the license activation file by e-mail.or

• Via e-mail: Send the generated license request file by e-mail to the HERMES SoftLab Licensing Department at spi-licensing@hermes.si. You will receive the license activation file usually within 24 hours. If you need immediate response, contact HERMES SoftLab by telephone and e-mail (see contact information on License Entitlement Certificate).

Configuration: Licensing Managed Nodes

Merge and Distribute the License Files1. Copy the license activation file tsspi_licact_new.dat to the

following directory: /opt/OV/tsspi

2. Run the 3. Merge License Activation Codes application to merge the tsspi_licact_new.dat file with the SPI license file.

3. From the Install/Update Software and Configuration window, distribute monitor to all managed nodes for which you have requested TSSPI licenses.

List License Activation Codes• To list activated license keys on the management server, run the

TSSPI-List License Activation Codes application.

Verifying Requirements and Configuration

• From the application group “SPI for Terminal Server/TSSPI-SPI Maintenance”, run the application “TSSPI-Check Requirements/Configuration” on all newly configured managed nodes. The tool should report OK status for several items checked.

• IMPORTANT: Do not distribute any SPI for Terminal Server monitoring templates to a the managed node until the above application reports that the node has been correctly configured!

Installing Reports

• Reports can be installed on the system with the Reporter product installed

• Login to the Reporter system as user administrator• Insert the SPI for Terminal Server installation CD• Install the SPI

– If autorun is enabled, a Web page is launched -> click on:

SPI for Terminal Server for OVO Unix-> Product packages

-> Installation package - Reporter 01.00

(The package is not signed; thus, IE may issue a warning – just ignore it and allow installation to execute)

– If autorun is disabled, start TSSPI_01.00-Reporter.exe on the CD

Verifying Reports Installationon Reporter

• The following metric lists should be installed:– TSSPI_LIC– TSSPI_SESS– TSSPI_SESSINFO– TSSPI_SRV– TSSPI_PSLD– TSSPI_PROFILE– TSSPI_PROFILES

• 40 reports should be installed under “SPI for Terminal Server” report group

Configuring Reports on Reporter 1/2

• SPI for Terminal Server reports will only be generated for those nodes that are put into the “SPI for Terminal Server” Reporter node group.

• The SPI configures a “SPI for Terminal Server” auto-group (File -> Configure -> Auto Groups) to help with that task.

• If “SPI for Terminal Server” node group is not generated automatically, you need to create it manually.

• Every node when it is first discovered by Reporter, and Reporter detects that node has SPI-related data, automatically inserts the node in this group.

• If by any chance this does not happen for some nodes, place them into the “SPI for Terminal Server” Reporter group manually.

Configuring Reports on Reporter 2/2

• Reports will be generated only for the following managed nodes:– Terminal Server 5.0 (Windows 2000) managed nodes that

have the “TSSPI-TS50 Data Collection” policy group deployed

– Terminal Server 5.2 (Windows 2003) managed nodes that have the “TSSPI-TS52 Data Collection” policy group deployed

– Terminal Server License Server 5.0 (Windows 2000) managed nodes that have the “TSSPI-TLS50 Data Collection” policy group deployed

– Terminal Server License Server 5.2 (Windows 2003) managed nodes that have the “TSSPI-TLS52 Data Collection” policy group deployed

Installing Graphs

• Graphs can be installed on the system Performance Manager product installed

• On Performance Manager, copy the file VPI_GraphsSPI for Terminal Server.txt from the installation CD to the following location:– OVPM on Windows:

– <HP OpenView Home>\newconfig\OVPM

– OVPM on HP-UX and Solaris:– /opt/OV/newconfig/OVPM/

Verifying Graphs Installation

• On Performance Manager, click the Display tab. In the right pane you will see the main SPI for Terminal Server graph family.

• In order for graphs to show data, the corresponding data collection policies need to be deployed to Terminal Server and Terminal Server License Server systems (see Reports section for details).