ClearCube Grid Center Admin Guide

Grid Center 4.11

Administrator’s Guide

ClearCube Technology, Inc.

Under copyright laws, this publication may not be reproduced or transmitted in any form, electronic or mechanical,

including photocopying, recording, storing in an information retrieval system, or translating, in whole or in part,

without the prior written consent of ClearCube Technology, Inc.

This information is subject to change without notice and ClearCube shall not be liable for any direct, indirect,

special, incidental or consequential damages in connection with the use of this material.

Trademarks

ClearCube™, C3 Architecture™, Blade Switching BackPack™, PC Blade™, and C/Port™

are trademarks of ClearCube Technology Inc. Product and company names mentioned herein

are trademarks or trade names of their respective companies.

Patents

The ClearCube Architecture and its components described in this user manual

are protected by numerous granted and pending U.S. and international patents.

Granted patents include: US06020839, US06012101, US05994952, US05966056, US05926172, US06167241,US06148182,

US06119146, US06038616, US06385666, and US06037884. Inquiries regarding patented technology should be directed to

Revision Date: 1-31-2005, based on ClearCube Grid Center release 4.1.8

ClearCube Corporate Headquarters.

Contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i

Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

ClearCube Grid Center 4.11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Management Capabilities in Grid Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Packaging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Migrating Grid Center Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Grid Center Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Installing Grid Center 4.11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Installing Components Individually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Migrating Discovery Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Uninstalling Grid Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Grid Center Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Launching the Administration Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Logging in for the First Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Take a Tour . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Grid Center Clients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

I/Port Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Blade Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Configuring Grid Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Configuring the Administration Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Configuring the Authentication Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Configuring Network Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Debugging Blade Discovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Modifying User Access to the Administration Console. . . . . . . . . . . . . . . . . . . . . . . 38

Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Creating Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Allocating I/Ports and Blades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Switching and Sparing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

When to Switch and When to Spare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Switching an I/Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Sparing an I/Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Updating an I/Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Inventory and Health . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Viewing I/Port Health . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Viewing Blade Health . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Appendix A: Using Grid Center with e100 and Capio I/Ports. . . . . . . . . . . . . . . . . . . . . 61

Grid Center 4.11 Administrator’s Guide Contents • i

Console Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Client Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Contacting Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Grid Center 4.11 Administrator’s Guide Contents • ii

Figures

Figure 1 Grid Center All-in-One Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Figure 2 Setup Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Figure 3 Grid Center Administration Console Login . . . . . . . . . . . . . . . . . . . . 18

Figure 4 Grid Center Administration Console Welcome Screen. . . . . . . . . . . 19

Figure 5 Icons for Blades, I/Ports, and Groups. . . . . . . . . . . . . . . . . . . . . . . . 19

Figure 6 Network Configuration View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Figure 7 Edit Groups View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Figure 8 Switching View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Figure 9 Allocation View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Figure 10 Update View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Figure 11 Inventory and Health View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Figure 12 I/Port Client Connection to Blade . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Figure 13 I/Port Client Login Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Figure 14 Dedicated I/Port to Blade Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . 27

Figure 15 Shared I/Port to Blade Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Figure 16 Authentication Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Figure 17 Replicating Authentication Database Entries . . . . . . . . . . . . . . . . . . 32

Figure 18 Blade Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Figure 19 Blade Client Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . 34

Figure 20 I/Port Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Figure 21 Setting the I/Port Refresh Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Figure 22 Getting I/Port Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Figure 23 Allocation Strategies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Figure 24 Creating an I/Port Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Figure 25 Allocation View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Figure 26 Adding a Shared Resource. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Figure 27 Choosing a Blade for Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Figure 28 Deleting a User Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Figure 29 Switching View with Default Blade Group Selected . . . . . . . . . . . . . 51

Figure 30 Selected I/Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Figure 31 Selecting a Blade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Figure 32 Confirm Dialog for Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Figure 33 Selecting an I/Port for Updating . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Figure 34 I/Port Inventory and Health View . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Figure 35 I/Port System Information Description Window . . . . . . . . . . . . . . . . 58

Figure 36 Blade Health Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Figure A-1 ClearCube I/Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Grid Center 4.1 Administrator’s Guide Figures • iii

This page intentionally left blank.

iv • Figures Grid Center 4.1 Administrator’s Guide

Introduction

ClearCube Grid Center 4.11

ClearCube Grid Center™ 4.11 is a web-based application that provides a complete management interface for an I/Port environment. Grid Center can be accessed from any machine that has IP connectivity to the machine where Grid Center is installed, thus enabling world-wide remote systems management.

New Features

Grid Center 4.11 provides the following new features:

• Support for new XPe-based Eon e100 I/Ports

• Support for new Linux-based Capio One and Eon e100 I/Ports

• Redundant Consoles for higher availability

• Ability to block end user from changing assigned Blade

• Multiple spare groups

• Ability to define Blade and I/Port groups as shared or dedicated

• Improved Blade selection algorithm

• Support for dual NIC Blades

• All-in-One installer that streamlines new Console and Blade client installation

• Improved usability

• Improved manageability with trusted machines list

• Improved input error checking

• DCI service enhancements

Grid Center 4.11 Administrator’s Guide Introduction • 1

Management Capabilities in Grid Center

Grid Center provides several unique management capabilities in the following six View windows:

• Configuration View

• Edit Groups View

• Switching View

• Allocation View

• Updates View

• Inventory and Health View

Each View provides access to specialized tools for configuring and managing an I/Port environment, along with convenient links to the other Views.

Configuration View

The Configuration View provides the fundamentals for configuring a network built around an I/Port environment.

Edit Groups View

Grid Center applies the concept of groups to I/Ports and Blades. Quite simply, a group is a collection of zero or more I/Ports or Blades that has been created by an administrator. A group can be left empty, to be populated later. A group can contain a single I/Port or Blade, to allow dedicated mappings between I/Ports and Blades. A group can contain several I/Ports or Blades, to allow shared mappings between I/Ports or Blades. With Grid Center, groups can be set up without limitation on size or location. This capability gives a wide range of options to system administrators for load-balancing and resource sharing, and can be dynamically adjusted to meet changing resource demands. The Edit Groups View allows creating and configuring groups.

Switching View

With the Switching View, Grid Center delivers server-level availability to end users by allowing administrators to easily switch I/Ports to spare Blades if a problem occurs. This dramatically reduces downtime because the end user does not need to wait for deskside support. The end user resumes working on a spare Blade while an IT technician troubleshoots the problem Blade.

Allocation View

Allocation is the assigning of resources to users based on their computing needs. In any user environment, some people need only a little access or processing power, and some people are “power users” who need a dedicated processor—or several

2 • Introduction Grid Center 4.11 Administrator’s Guide

dedicated processors. Usually, these users are already divided into groups with similar computing needs.

Allocation defines the allowable connections between the I/Ports and the Blades, with connections defined by the administrator. For example, the I/Ports in the Sales Group can be configured to connect only to the Blades dedicated to the Sales Group. When a user logs in, Grid Center automatically connects the user’s I/Port to the least loaded Blade in the group, using a built-in algorithm that monitors the processor load and memory utilization on each Blade. On the other hand, the power users in the software development group could be set up to have their I/Ports connect to specific Blades, ensuring they always have ample computing resources.

Updates View

This update feature allows administrators to package and deploy driver updates, software patches, and new applications to individual or multiple I/Ports. The Grid Center 4.11 update adds support for ClearCube’s new Eon e100 and Capio One Linux-based I/Ports.

Inventory and Health View

Grid Center lets administrators monitor I/Port health status and see asset management information such as installed applications, memory capacity, and OS settings. In addition, administrators can see real-time CPU loading and memory utilization for any Blade.

Grid Center provides management for I/Ports. If your network also contains C/Ports, use ClearCube Switch Manager (sold separately) to manage C/Ports. Grid Center and Switch Manager can be installed on the same Console system.

Packaging

Grid Center 4.11 is shipped with an All-in-One installer application (see page 9) that automates the correct installation of certain components (see page 5). Additionally, all these components are provided on the Grid Center 4.11 installation CD as independently installable applications. Grid Center requires that these components be installed in a specific order prior to installing the application.

This manual is the most current version as of the initial release ship date for the Grid Center 4.11 application. For free updated manual versions, please visit the Tech Docs section at

If you are updating from Grid Center 4.0, you need to apply updates to your I/Ports to enable many of the new features in Grid Center 4.11. Please see the README on the

http://support.clearcube.com.

Grid Center 4.11 Administrator’s Guide Introduction • 3

installation CD for more information, or contact ClearCube using the resources listed in Contacting Support on page 67.

Migrating Grid Center Data

Grid Center 4.11 allows for the migration of Discovery lists from a Grid Center 4.0 installation to Grid Center 4.11. Because of the numerous new features in each new version, not all data can be migrated. Saving Discovery lists significantly speeds configuring your Grid Center 4.11 installation. For more information, see Migrating Discovery Lists on page 13.

4 • Introduction Grid Center 4.11 Administrator’s Guide

Grid Center Installation

The Grid Center Administration Console can be installed on Windows 2000/2003 Server or Windows XP Professional. The Grid Center Blade client can be installed on Windows XP Professional. The Grid Center I/Port clients can be installed on I8800, Eon e100, and Capio One I/Ports. The Grid Center Administration Console and the Grid Center Blade client should not be installed on the same system. Installation of either package requires local administrator access privileges.

For Grid Center to function properly, the following components must be installed. All these components are provided as part of the All-in-One installer.

• Java Runtime Environment (JRE) version 1.4.2—Grid Center 4.11 requires

JRE version 1.4.2_03 or later. The correct JRE version is provided on the Grid Center 4.11 CD shipped from ClearCube. The version of a previously installed Java package can be checked in Add or Remove Programs from the Control Panel, or by running the returns the installed Java version. Versions previous to 1.4.2_03 should be removed.

Version 1.4.2 or later of the Java 2 Enterprise Edition 1.4 Software Development Kit (SDK), which adds support for EJBs, JSPs, XML, and Web Services APIs, can also be used (not provided on the Grid Center 4.11 installation CD).

Version 1.5 or higher is not supported.

Java -version command at the DOS prompt, which

• ActiveState Perl 5.6.1—Grid Center 4.11 requires ActiveState Perl 5.6.1. The

correct version of ActiveState Perl is provided on the Grid Center 4.11 CD shipped from ClearCube. The version of a previously installed ActiveState Perl can be checked in Add or Remove Programs from the Control Panel, or by running the

Perl -version command at the DOS prompt, which returns the installed Perl

version. Versions previous to 5.6.1 should be removed.

Versions higher than 5.6.x are not supported.

The ActiveState Repository has a large collection of modules and extensions in binary packages that are easy to install and use. To view and install these packages, use the Perl Package Manager (PPM) which is included with ActivePerl.

• ClearCube Distributed Computing Infrastructure (DCI)—Grid Center 4.11

requires ClearCube DCI version 2.0.8. The correct version is provided on the Grid Center 4.11 CD shipped from ClearCube. Before installing Grid Center 4.11,

Grid Center 4.11 Administrator’s Guide Grid Center Installation • 5

please make sure that the current DCI is installed. The installed DCI version can be verified through Add or Remove Programs in the Control Panel. Versions previous to 2.0.8 should be removed prior to installing Grid Center 4.11.

• ClearCube Perl PlugIn—Grid Center 4.11 requires ClearCube Perl PlugIn

version 1.1. The correct version is provided on the Grid Center 4.11 CD. The installed Perl PlugIn version can be verified through Add or Remove Programs in the Control Panel. Version 1.0 should be removed.

Installing Grid Center 4.11

The Grid Center 4.11 Administration Console provides the capability of installing a secondary, or redundant Console. The main benefit of this feature is that it allows maintaining control of the managed systems if the Primary Console system fails or is disconnected. When this happens, information about I/Ports and Blades is stored on the redundant (Secondary) Console system, and replicated to the Primary Console system when it is reconnected. Installation of a Secondary Console is not required.

Grid Center 4.11 provides two types of installation:

• Grid Center Administration Console—The Grid Center Administration Console

should be installed on a Primary Console and a Secondary Console system. Only one Secondary Console can be installed.

• Grid Center Clients—The Grid Center clients are installed on the targeted

Blades and I/Ports once the Grid Center Administration Console is installed.

Note: If you are installing the Grid Center Administration Console on a Blade that

has Blade Manager 4.0 or higher installed, you should already have the correct versions of Java, ActiveState Perl, and ClearCube DCI installed.

The Grid Center 4.11 All-in-One installer application checks for the necessary components, and installs all components not detected. In addition, separate installers for each application are provided on the Grid Center installation CD.

Note: If you already have Grid Center Console 4.1 or Grid Center Blade client 4.1

installed, do not remove or reinstall the Grid Center Console or Blade client.

Before You Install

Before you begin your installation, you need to gather the following information:

• The version number of your Grid Center installation (if installed).

• The name of the system to be designated as the Primary Grid Center

Administration Console, and the name of the system to be designated as the

6 • Grid Center Installation Grid Center 4.11 Administrator’s Guide

Secondary Console, if desired.

• Administrator logins and passwords for the Consoles, Blades, and I/Ports.

• IP subnet ranges for the Blades and I/Ports.

You should plan your I/Port and Blade groups before installing Grid Center. You can always create, edit, and delete groups after you configure your network.

On the Blade and Console systems, you need to stop the CC DCI service before installing or uninstalling Grid Center or its components.

Back up existing Discovery lists if desired. See Migrating Discovery Lists on page 13.

On the Blade and Console systems, check the versions of the JRE, ActiveState Perl, ClearCube DCI, and Perl PlugIn (if these products are installed), and remove any previous versions. Installations of Grid Center 4.0 or earlier should also be removed (see Migrating Grid Center Data on page 13 before uninstalling Grid Center). The Grid Center installer contains a dialog box reminding you to remove previous versions. Installations of Grid Center 4.1 should not be removed.

Using Grid Center’s All-in-One Installer

The Grid Center 4.11 installation CD provides an All-in-One installer for the Administration Console that simplifies the task of installation. See Figure 1.

Figure 1 Grid Center All-in-One Installer

The installer displays all the required components for the Grid Center installation. If a component needs to be installed, a check box is placed by its name. If it has already been installed, the box next to its name is empty. The installer then installs each component selected in the correct order. It is strongly recommended to use the All-in-One installer to determine the necessary components and their installation order, and to accept the settings of the installer.

Grid Center 4.11 Administrator’s Guide Grid Center Installation • 7

Note: Verify the versions of your installed components, and uninstall outdated

versions before beginning to install Grid Center.

In all cases, allow the installer adequate time to complete its operation. The ClearCube All-in-One installer appears to pause at several times during its execution, while showing no obvious activity. The installation resumes within several seconds, and displays a dialog box with information or more instructions.

Installing the Grid Center Administration Console

If you have a Grid Center 4.0 installation, remove it before installing Grid Center 4.11. If you have a Grid Center 4.1 installation, do not remove or re-install Grid Center. Instead, go to the Installing the Linux Console Update procedure on page 9.

Install the Grid Center Administration Console using the All-in-One installer on the Grid Center CD. Installation requires local administrator access privileges.

1. Double-click the setup.exe icon on the Grid Center 4.11 installation CD.

2. Choose the components to be installed from the Select Features window (see

Figure 1). Press Next.

3. When prompted, choose the users who see the Grid Center installation by selecting “Anyone who uses this computer (all users)” or “Only for me (username).” This can be changed later. See Administration Console on page 38.

4. Select Grid Center Administration Console from the Setup Type screen

Figure 2). Press Next.

(see

Modifying User Access to the

Figure 2 Setup Type

5. Accept the default settings as the InstallShield Wizard runs. Press Next when necessary.

6. Follow the prompts as appropriate.

8 • Grid Center Installation Grid Center 4.11 Administrator’s Guide

7. Enter the Grid Center Server names when you are prompted for them. The

Primary Server is the first system on which you are installing the Administration Console now. The Secondary Server is the system that you plan to designate as the Secondary Console. If you have not yet chosen the Secondary Server, enter a non-null text string. This can be easily changed later. Enter the name of the Primary Server as the name of the Secondary Server if you do not plan to use a Secondary Server. Press Next.

8. When the installation has completed, restart your system.

9. Repeat the installation on the Secondary Console, if one is being configured.

Note: If the installer prompts you to restart your system, do so, and restart the

setup.exe application after restarting.

Installing the Linux Console Update

Install the Linux Console update from the update installer in the Console Updates directory of the Grid Center 4.11 CD. Installation requires local administrator access privileges.

1. Double-click the updater icon on the Grid Center 4.11 installation CD.

2. Accept the defaults.

3. Reboot your system after completing the installation.

Installing Grid Center Clients

Once the Grid Center Administration Console is installed on the Primary and Secondary systems, Grid Center clients need to be installed on each Blade and each I/Port that Grid Center manages.

Installing the Grid Center Blade Client

Install the Grid Center Blade client from the installation program on the Grid Center CD. Installation requires administrator access privileges.

1. From the Grid Center 4.11 Blade Client folder on the ClearCube Grid Center

CD, launch the

2. Choose the components to be installed from the Select Features window (see

Figure 1). Press Next.

3. Select Grid Center Blade Client from the Setup Type screen (see Figure 2).

4. Click Next to begin installing the Grid Center Blade client.

5. Follow the prompts as appropriate.

6. Enter the Grid Center Server names when you are prompted for them. Both

fields are auto-populated with the name of the Primary Server. Enter the name of the Secondary Server in the specified field. To configure for only one Grid Center server, click Next.

7. When the installation has completed, restart your system.

setup.exe file.

Grid Center 4.11 Administrator’s Guide Grid Center Installation • 9

Installing the I8800 I/Port Client

The Grid Center I8800 I/Port client is installed after the Blade clients are installed. This client can be installed in one of two ways:

• Locally at the I/Port

• Remotely from the Console, using the Grid Center Update function (see Updates

on page 55)

To install the Grid Center client, do the following (for both methods):

1. Change the following configuration files in the IPORT-CLIENT file before sending it as an update:

a. Edit the iportinfo.xml file to specify valid Primary and Secondary

Administration Console(s).

<dcreason>2</dcreason> <adminblade>PrimaryServer</adminblade> <secondaryserver>SecondaryServer</secondaryserver> <refreshtime>150</refreshtime>

Change to the name of the Primary Admin Console.

Change to the name of the Secondary Admin Console.

b. Edit the trustusers.xml file to include the name of the Secondary Admin

Console as a trusted Console.

<?xml version="1.0" encoding="UTF-8"?> <trustusers></trustusers>

Insert the name of the Secondary Administration Console

This establishes the Console systems as trusted machines for the I/Ports. A trusted machine is a system that is assumed to be safe to send data, snapins, and operating system updates to the I/Ports without requiring authentication or a challenge/ response exchange. By default, the Consoles are the trusted machines for the I/Ports. More systems can be added as trusted machines in this fashion. Trusted machines can also be configured through Grid Center after the I/Ports have been discovered.

For a local installation:

1. Copy the update files to a USB mass storage device such as a key drive and go to the I/Port.

2. Log into the I/Port as an administrator. Press and hold the Shift key and select Logoff from the Start menu. Keep the Shift key depressed until the Administrator Login dialog box is displayed. The factory default Administrator account is

administrator and the default password is clearcube. These

can be changed in the User Accounts control panel.

10 • Grid Center Installation Grid Center 4.11 Administrator’s Guide

3. Turn off the Write Filter by double-clicking the Write Filter Disable icon on the

desktop. The Write Filter is a special mechanism that prevents unauthorized writes to the I/Port’s flash memory. The Write Filter status is always displayed in the toolbar by a green circle for Write Filter Enabled (flash memory cannot be written), or by a red circle for Write Filter Disabled (flash memory can be written).

4. Insert the USB storage device into an available USB port.

5. Copy the update files to C:\. (This is faster than installing through the USB

port.)

6. Launch the update installer. Accept the defaults and click through the installer.

7. Reboot your computer when prompted to do so. This reboots the I/Port.

8. When the I/Port finishes rebooting, log in as Administrator again.

9. Delete the update files from C:\ and double-click the Enable Write Filter icon

to re-enable the Write Filter.

10. When the Write Filter has been re-enabled (a green circle is displayed in the

tool bar), log out from the Administrator account and continue to the next I/Port.

Note: If you have a number of I/Ports to update, you may want to set up several

terminals (keyboard, monitor and mouse) in the same place, and update several I/Ports at one time. A KVM switch can also be used to provide this same capability.

For a remote installation:

1. Compress the IPORT-CLIENT folder to IPORT-CLIENT.zip.

2. Push out the batch file and the IPORT-CLIENT.zip file via the Administration

Console. See

Updates on page 55 for more information.

By default, the installer places the I/Port User account in the Administrators group of the I/Port. This is required for the client to function correctly. If the User account is moved from the Administrator group, or is installed in another group, the I/Port client cannot communicate with Grid Center.

Note: Grid Center I/Port clients are pre-installed on Eon e100 and Capio One

I/Ports. For more information, see

Appendix A: Using Grid Center with e100

and Capio I/Ports on page 61.

Grid Center 4.11 Administrator’s Guide Grid Center Installation • 11

Installing Components Individually

Components on the Console and Blade client systems can be installed individually, if desired. Use the following procedures.

Install JRE

Installation of the JRE requires local administrator access privileges.

1. To begin installation, launch the j2re-1_4_2_06-windows-i586-p .exe file on the ClearCube Grid Center CD.

2. The Java License Agreement Screen is displayed. Click the I accept the terms of the license agreement radio button to accept the license agreement. Click the Next button.

3. Click the Next button to accept the Custom Setup choices.

4. Accept the default selection for Browser Registration. Click the Next button.

5. Click the Finish button to complete the installation of JRE.

Note: The Java SDK 1.4.2 or higher can also be installed. The 1.5 version is not

supported.

Install ActivePerl

Installation of ActivePerl requires local administrator access privileges.

1. To begin installation, launch the ActivePerl installer file

ActivePerl-5.6.1.638-MSWin32-x86.msi on the ClearCube Grid Center

CD. Click the Next button to continue.

2. The Active State End User License Agreement is displayed. Click the I accept the terms in the License Agreement button to accept the license agreement. Click the Next button. If you decline the agreement, installation is halted.

3. Click the Next button to accept the Custom Setup choices.

4. Click the Next button to skip the Programmer’s Package Manager and continue with installation.

5. Select all the options in the Choose Setup Options screen. Click the Next button.

6. Click the Finish button to complete the installation.

Install Distributed Computing Infrastructure (DCI)

Installation of ClearCube Distributed Computing Infrastructure (DCI) requires local administrator access privileges.

1. To begin installation, launch the dci-setup.exe file on the ClearCube Grid Center CD. Click the Next button to continue.

12 • Grid Center Installation Grid Center 4.11 Administrator’s Guide

2. The ClearCube Distributed Computing Infrastructure License Agreement is

displayed. Click Yes to accept the license agreement.

3. Click the Next button to accept the default Destination Location.

4. Click the Finish button to complete the installation.

5. Once the installation is complete, you must restart the computer to finalize the

setup process. Select the Yes radio button and click the Finish button to restart your computer.

6. Once DCI is installed on the system, the service must be started. Check the

CC DCI service from Start–>Control Panel–>Administrative Tools–>Services.

7. Double-click the CC DCI service to view the properties. Click the Log On tab.

8. Set up logon parameters as appropriate.

9. Click the OK button to save changes to the logon name. Click through the

following dialog boxes.

10. Stop and then restart the DCI service for all changes to take effect.

Install Grid Center Administration Console and Blade Client

Installation of the Grid Center Administration Console and Blade clients requires local administrator access privileges.

1. To begin installation, launch the gcAdmin-setup.exe file to launch the

installer for the Administration Console, or the launch the installer for the Grid Center client.

gcClient-setup.exe file to

Note: Install the Grid Center Consoles before installing Blade clients.

2. The installer verifies whether the necessary components have been installed.

3. If all the necessary components have been installed in the correct order, the

installer proceeds in the same fashion as if it were running as the All-in-One installer. Accept the default options during installation.

4. When the installation is complete, click the Finish button.

5. If installing on a Console system, run the Grid Center Linux client updater.

Migrating Discovery Lists

If you have a previous Grid Center 4.0 installation, you can migrate your existing discovery lists to your new Grid Center 4.11 installation. This greatly speeds network configuration. Your Grid Center 4.1 data is not changed by the Grid Center 4.11 update.

Use these procedures to migrate Discovery lists. Local administrator access is generally required.

Grid Center 4.11 Administrator’s Guide Grid Center Installation • 13

Note: You must begin this process before beginning to uninstall a previous version

of Grid Center.

Backing up the Discovery List Files

To back up the Discovery list files for Grid Center 4.0, do the following before you begin your Grid Center 4.11 installation process:

1. Go to C:\Program Files\ClearCube Management Suite\DCI\CGI-BIN\IPORT\ .

2. Copy these two files:

• shosts

• bladehosts

3. Save these files to a directory outside the ClearCube Management Suite directory.

4. Proceed with your Grid Center 4.11 installation, beginning with un-installing your previous version of Grid Center.

Removing Grid Center erases these files from the ClearCube Management Suite directory.

Restoring the Discovery List Files

To restore the Discovery list files, do the following after you complete your Grid Center 4.11 installation process:

1. Go to C:\Program Files\ClearCube Management Suite\DCI\CGI-BIN\IPORT\ .

2. Copy the backed-up shosts and bladehosts files into the IPORT directory. This overwrites the newly installed files with the data from your previous Grid Center installation.

3. Start Grid Center 4.11.

Uninstalling Grid Center

Use these procedures to uninstall Grid Center. Local administrator access is required for all uninstallations.

Note: On the Blade and Console systems, you need to stop the CC DCI service

before installing or un-installing Grid Center or its components.

14 • Grid Center Installation Grid Center 4.11 Administrator’s Guide

Uninstalling the Administration Console

To uninstall the Grid Center Administration Console, do the following:

1. Go to Add/Remove Programs in the Control Panel.

2. Select ClearCube Grid Center from the list of programs. Click the

Change/Remove button.

3. Select the radio button for Remove. Click the Next button.

4. Once the removal is complete, click the Finish button.

Uninstalling the Clients

To uninstall Grid Center Blade clients, do the following:

1. Go to Add/Remove Programs in the Control Panel.

2. Select ClearCube Grid Center from the list of programs. Click the

Change/Remove button.

3. Select the radio button for Remove. Click the Next button.

4. Once the removal is complete, click the Finish button.

Uninstalling Other Components

The other components necessary for Grid Center (such as Java) can be uninstalled from Add/Remove Programs in the Control Panel.

Note: Components must be un-installed in the following order, or system errors will

occur.

Administration Console Blade Client Side

1. Grid Center Administration Console 1. Grid Center Blade Client

2. DCI 2. DCI

3. Perl Plugin for ClearCube Technology 3. Perl Plugin for ClearCube Technology

4. ActivePerl 4. ActivePerl

5. Java 5. Java

Grid Center 4.11 Administrator’s Guide Grid Center Installation • 15

This page intentionally left blank.

16 • Grid Center Installation Grid Center 4.11 Administrator’s Guide

Grid Center Console

ClearCube Grid Center 4.11 is a web-based application that provides a complete management interface for an I/Port environment consisting of I8800, Eon e100, and Capio One I/Ports. I8010 I/Ports are not supported. Grid Center can be accessed from any machine that has IP connectivity to the machine where Grid Center is installed.

The Administration Console is the first of three Grid Center components. It can be installed on any Windows 2000 or 2003 server, or Windows XP Pro system. The Administration Console acts as a traffic director between I/Ports and Blades. When an I/Port client is launched, the Administration Console directs it to a specific Blade or to a group of Blades.

When an I/Port is in Dedicated mode, the Administration Console always directs it to a specific Blade. In this case, the user logs in to the same Blade every time. When an I/Port is in Shared mode, the Console directs it to a group of Blades. The Console tracks utilization on the Blades, and always directs the I/Port to the least utilized Blade in the specified group.

Grid Center uses TCP ports 6500, 9000, and 3389; and UDP ports 6500 and 9000. These ports must remain open between network nodes that use Grid Center. The first time the Grid Center Administration Console is run, it does not have any Blades or I/Ports populated in its database. To populate Blades and I/Ports, you need to specify the IP address subnet range that contains the Blades and I/Ports to be managed by this Grid Center installation. See Configuring the Administration Console on page 29 for more information. After specifying the subnet range, you need to do a process called Discovery, which searches for Blades and I/Ports in the subnet range. See Configuring the Authentication Database on page 30 for more information.

When Discovery finds a Blade or an I/Port, it stores the identifying information for each component in the database. When new components are added to the network, Discovery can be run again to locate them.

Once a Blade or I/Port has been discovered, Grid Center maintains a record of it and graphically displays whether it is active on the network. Grid Center maintains these records indefinitely, and periodically re-discovers Blades and I/Ports. When this happens, the database is updated. Blades and I/Ports can be manually deleted from the database if they are physically removed from the network, but if they are reconnected, they will be saved in the database again when Discovery is run.

Grid Center 4.11 Administrator’s Guide Grid Center Console • 17

Launching the Administration Console

Launch the primary Grid Center Administration Console by selecting Start Menu–>All Programs–>ClearCube Management Suite–>Grid Center–>Grid Center Admin.

Grid Center can also be launched by pointing a browser to:

http://hostname:6500/iport/index.htm

where Console is installed. Once the Primary Console is installed, its settings are replicated automatically on the Secondary Console.

hostname is the system on which the Primary Grid Center Administration

Logging in for the First Time

The first screen in Grid Center is the Login screen. The first time you log in, you must use the administrator username and password for the local machine. The local system’s host name is automatically populated in the Domain Name field. Click the Login button.

Figure 3 Grid Center Administration Console Login

Once you have logged in, use the procedures found in Configuring Grid Center on page 29 to configure the Console. This process needs to be done only once, and only on the Primary Console. These settings and subsequent updates are automatically replicated on the Secondary Console.

18 • Grid Center Console Grid Center 4.11 Administrator’s Guide

+ 54 hidden pages