Grid Center 4.11 Administrator’s Guide ClearCube Technology, Inc.
Copyright © 2005, ClearCube Technology, Inc. All rights reserved. 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.
Contents Contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 ClearCube Grid Center 4.11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Console Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Client Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Contacting Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Grid Center 4.
Figures Figure 1 Figure 2 Figure 3 Figure 4 Figure 5 Figure 6 Figure 7 Figure 8 Figure 9 Figure 10 Figure 11 Figure 12 Figure 13 Figure 14 Figure 15 Figure 16 Figure 17 Figure 18 Figure 19 Figure 20 Figure 21 Figure 22 Figure 23 Figure 24 Figure 25 Figure 26 Figure 27 Figure 28 Figure 29 Figure 30 Figure 31 Figure 32 Figure 33 Figure 34 Figure 35 Figure 36 Figure A-1 Grid Center All-in-One Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Setup Type . . . . . . . . . . . . . . . . . .
This page intentionally left blank. iv • Figures Grid Center 4.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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:\.
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.
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.
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.
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.
This page intentionally left blank. 16 • Grid Center Installation Grid Center 4.
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.
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 hostname is the system on which the Primary Grid Center Administration Console is installed. Once the Primary Console is installed, its settings are replicated automatically on the Secondary Console.
Take a Tour The following figures show the six Views in the Administration Console. The next chapter, Configuring Grid Center, describes how to use the tools in these Views. When you log in to the Administration Console, the Welcome screen (shown in Figure 4) is displayed. The main menu on the left side of the screen lists the Views with their associated sub-menu items. Select any of the main menu or sub-menu items to navigate to that View.
The Network Configuration View, shown in Figure 6, allows configuring Grid Center’s network database and the Blades and I/Ports (also called nodes) in the database. Figure 6 Network Configuration View Select I/Ports or Blades under the Configuration menu to configure I/Ports or Blades, respectively. The Auth. DB menu choice allows configuring and editing the Authentication database, which allows assigning user names and passwords for specific Blades and I/Ports.
The Edit Groups View (shown in Figure 7) allows the administrator to create, modify, and delete I/Port and Blade groups. This View also allows designating Blade groups as Dedicated, Shared, or Spare. Figure 7 Edit Groups View The Switching View, shown in Figure 8, allows the administrator to switch I/Ports and I/Port groups from one Blade or Blade group to another, depending on how the I/Ports and Blades have been allocated. Grid Center 4.
Figure 8 Switching View The Allocation View in Figure 9 allows creating and managing allocations between Blades and I/Ports. Allocation reflects the mappings between I/Ports and Blades. The sections Grid Center Clients on page 25 and Allocation on page 41 provide detailed information on allocation and how to configure allocations. Figure 9 Allocation View 22 • Grid Center Console Grid Center 4.
The Update View (Figure 10) allows sending updates to I/Ports, either individually or by group. The I8800 I/Port and some Eon e100s use the Windows XP Embedded (XPe) operating system. The Capio One and some Eon e100s use the NeoLinux operating system. From time to time, the operating systems and the applications running on it require updates to enhance functionality or new add features. For more information, see Appendix A: Using Grid Center with e100 and Capio I/Ports on page 61.
Figure 11 Inventory and Health View 24 • Grid Center Console Grid Center 4.
Grid Center Clients Grid Center 4.11 provides two types of clients: • • I/Port client Blade client This chapter briefly discusses their interaction. Allocation on page 41 details how to configure this interaction. I/Port Client The I/Port client is an application that resides on each I/Port being managed by the Administration Console. When an I/Port client is launched, it polls the Administration Console that controls the appropriate Blade to which the I/Port should connect.
Click to refresh Blade list Click to select last-connected Blade Figure 13 I/Port Client Login Screen Connections are accomplished via Microsoft Remote Desktop Protocol (RDP). When a user clicks Connect, an RDP session is initiated, and the desktop of the remote Blade is displayed after the client passes through the login credentials. Blade Client The Blade client is an application that resides on each Blade being managed by the Grid Center Administration Console.
Grid Center Admin Console End User Blade (Data Center) Using dedicated mappings, as many as four I/Ports can connect to a specified Blade. The I/Ports connect to the same Blade each time the I/Port client is launched. Figure 14 Dedicated I/Port to Blade Mapping Grid Center Admin Console End User Blade (Data Center) Using shared mappings, a group of I/Ports is mapped to a group of Blades. In this scenario, an I/Port always connects to the least utilized Blade in the Blade group.
This page intentionally left blank. 28 • Grid Center Clients Grid Center 4.
Configuring Grid Center Once you have logged into Grid Center for the first time, you need to configure the Administration Console, the Blades, and the I/Ports on the network before you can actually begin managing your network. Configuring the Administration Console Figure 6 on page 20 shows the Network Configuration View, which opens by default to the User Database.
Table 1: Configuration Database Fields (Continued) Field Name Description Blade Refresh Time (Min.) If a Blade does not poll the Console within this interval, it is considered idle. Server Type Primary, Secondary, or Stand-Alone. Click Configure to toggle between types. Primary Server Name Name of the Primary Server. Secondary Server Name Name of the Secondary Server. Click the Save button to save the configuration. Grid Center connects to the specified database and stores the changes.
Discover Network Nodes Click Use Last Discovery to pick up the machines in the lists of previously discovered I/Ports and Blades. This option is useful when a pre-populated discovery list is available, because it avoids a potentially lengthy discovery process. If you migrated your Discovery lists, click Use Last Discovery to restore these network nodes to the Authentication database. Click Add New Blades to discover new Blades on the network and populate the Authentication database with them.
Figure 17 Replicating Authentication Database Entries Figure 17 shows a populated Authentication database. To add user/password entries, enter a user name and a password in the top row of the database. Press Save Record(s) to save the entries. To replicate entries, as has been done in Figure 17, click the top check box. All the entries on the page are marked. Enter a user name and a password in the top row of the database.
Blades The Blade Configuration screen, shown in Figure 18, allows connecting to individual Blades to configure them. The left-hand tree shows all the discovered Blades. If Blades are part of a group, then they are displayed in their respective groups. If they have not yet been assigned to a group, they are displayed in the Last Discovered list.
2. Enter the Username, Password, and (if required) the Domain Name for this Blade. Click Login. 3. Enter the Primary Server, Secondary Server, and Refresh Time in the Configuration window. Figure 19 Blade Client Configuration Window The parameters in the Client Configuration window are: • • Primary Server – the machine running the Administration Console. Secondary Server – the machine running the Secondary Console, if one is configured.
Figure 20 I/Port Configuration Screen 4. Only trusted machines can push software updates to I/Ports. To add a trusted machine to an I/Port’s list of trusted machines, click the here link on the screen. A login screen is displayed. Enter the I/Port’s local system user credentials or domain user credentials to add new trusted machines or delete previous ones. 5. Click the Configure I/Port link to see the I/Port Client Manager configuration and make changes. 6.
To see details regarding the I/Port client, click the Get I/Port Client Information link. The I/Port Client Manager window is displayed (Figure 22) is displayed. Figure 22 Getting I/Port Information Debugging Blade Discovery Occasionally, Blade discovery may not seem to work properly. Use this checklist and set of debugging procedures to isolate and resolve the most common problems.
“clean” copy of the ServiceDirectory.xml file is available on the ClearCube Support website. Debugging Take these steps to diagnose Blade client problems: • • Open the %cc_install_dir%\cgi-bin\iport\projects\bladehosts file and check its contents. Are any discovered hosts present? Open a command prompt and run the following command: cd %cc_install_dir%\iport set classpath=%classpath%;.
• Check these if the discovery appears to work: Check to see whether all the Blades that have Grid Center Blade client installed also have following service directory tag in their serviceDirectory.xml file: chkgcclient.bat If the tag does not exist, then the installation has been corrupted somehow. Reinstallation should resolve the issue.
Grid Center 4.
40 • Configuring Grid Center Grid Center 4.
Allocation Grid Center utilizes the concepts of I/Port groups and Blade groups for the purpose of mapping, or allocating, I/Ports to Blades. A group can contain a single I/Port or Blade, or many. Allocation defines the allowable connections (mappings) between the I/Port groups and Blade groups. Allocation allows administrators to allocate dynamic or static mappings between groups of Blades and I/Ports.
When a Blade group is designated as a Spare group, I/Ports can be re-mapped, or spared, to any available Blade in that group, regardless of their allocation to a Dedicated or Shared Blade group. For example, the I/Ports in an I/Port group named “Sales I/Ports” could be configured to connect only to the Blades in a Blade group named “Sales Blades.” When an end user logs in, the Grid Center Console directs that user to a specific Blade, or to any Blade in a particular group, as allocated.
Creating a Blade Group 1. From the main menu, click Blade Groups under Edit Groups. or In the Group Edit View, click Blade Groups in the menu bar. 2. Enter the Group Name, Description, and Location. Select a Users Class parameter from the Users Class pull-down menu.
3. You are prompted for confirmation before the Blade is removed from the group. 4. Click the Save button. Multiple Blades in a group can be selected for deletion. If you do not click Save, the changes are discarded and the group remains unchanged. Note: This process removes the Blade from the group in the Grid Center database. The Blade itself remains untouched, and is available to be added to a different group.
choice is None. However, you can add or modify a Blade group and designate it as a Spare group, and change the I/Port group spare mapping later. 3. Press Save or Add Group and confirm this action. The new I/Port group is saved in the database and the group name is added to the I/Port Group pull-down menu at the right end of the menu bar. An I/Port group can be modified at any time by selecting its name from the I/Port Group pull-down menu in the Group Edit View — I/Port Groups screen.
Figure 24 Creating an I/Port Group Note: I/Ports cannot be added to more that one group. Each I/Port can belong to only one group. To delete an I/Port from an I/Port group, do the following: 1. Click on the check box next to the I/Port to be deleted in the right pane. 2. Click Delete I/Ports in the center pane. 3. You are prompted for confirmation before the I/Port is removed from the group. 4. Click the Save button. Multiple I/Ports in a group can be selected for deletion.
You can create an essentially unlimited number of I/Port groups and leave them unpopulated if you wish. This is useful for planning future network expansions. Remember that each I/Port can be a member of only one group. Allocating I/Ports and Blades Allocation allows administrators to allocate dynamic connections between groups of Blades and I/Ports. After they are created, allocations can be easily modified to allow for changing network needs and use.
Figure 25 Allocation View The Resource Users lists show the existing allocations between I/Port groups and Blade groups. To delete an allocation from one of these lists, click the check box to the left of the record, and click Delete. You are asked for confirmation. To allow or disallow the user from being able to change his assigned Blade, click the link under Blade Selection that corresponds to the group or the I/Port.
Figure 26 Adding a Shared Resource Creating a Shared User Mapping Before creating a shared user mapping, each Blade client must be configured as a Shared resource type (see Creating a Blade Group on page 43). The Blade group and I/Port groups must also be configured as Shared resource types (see Creating a Blade Group on page 43 and Creating an I/Port Group on page 44). 1. From the Allocation View, click the Add link. 2. Select Shared Resource Users from the drop-down menu in the upper gray bar. 3.
1. From the Allocation View, click the Add link. 2. Select Dedicated Resource Users from the drop-down menu in the upper gray bar. 3. Click on the I/Port Group name in the left pane. 4. Select an individual I/Port. 5. Select the Blade Group to be used from the drop-down menu in the upper gray bar. 6. Click on any of the Blades shown in the right pane. Figure 27 Choosing a Blade for Mapping 7. Click the Save button to save the shared user mapping. 8.
Switching and Sparing The Switching View lets administrators view and switch any I/Port to any Blade on the network. To access the Switching View, click the Switching link in the left-hand frame in the Grid Center Console. The tree in the left pane shows the available I/Port groups. The drop-down list in the top gray bar shows the Blade group currently selected. By default, information for the first Blade group is shown, as in Figure 29.
When an I/Port or a Blade is selected, its information is shown at the bottom of the screen, as shown in Figure 30. Figure 30 Selected I/Port When to Switch and When to Spare When an administrator needs to move a user from one Blade to another, the decision should be made with both the administrator’s and the user’s needs in mind.
Switching an I/Port Switching an I/Port is possible only when the I/Port user has already connected to a Blade using the Grid Center I/Port client. Switching an I/Port to Another Blade 1. Select the I/Port to be switched from the left pane. The I/Port description at the bottom shows the user name and the Blade to which it is currently connected. 2. Using the Blade Group menu, select the Blade group containing the Blade you want connected to the selected I/Port. Click on the target Blade in the right pane.
Sparing an I/Port The Administration Console also allows switching an I/Port to a spare Blade. 1. Select the I/Port to be spared from the left pane. 2. Using the Blade Group menu, select the Spare Blade group. 3. Click the Spare button to switch the I/Port to the spare Blade. Grid Center then connects the selected I/Port to an available spare Blade from the Spare group not currently connected to an I/Port. 54 • Switching and Sparing Grid Center 4.
Updates Updating an I/Port Grid Center lets the administrator update software on I/Ports without having to physically be at the I/Port location. To update an I/Port or I/Port group, two files are required – the update file (a .zip or .tar archive file) that contains the new or updated files for installation, and the answer file (a .bat or .2do file) file that installs the files contained in the update file to the specified locations. Updates don’t necessarily have to always deploy files.
2. 3. 4. Note: Click the first Browse button to locate the update file. Click the second Browse button to locate the answer file. Click the Update button. The Browse function checks only that a file is specified, and not a directory. File extensions are checked when the Update button is clicked, and the extensions for the update and answer files are verified. Use .zip and .bat files for the I8800 and XPe Eon e100 I/Ports, and .tar and .2do files for the Capio One and Linux Eon e100 I/Ports.
Inventory and Health Viewing I/Port Health Health of individual I/Ports can be seen from the Inventory and Health View. 1. Click the Inventory and Health link in the left menu. 2. Click on an individual I/Port from left tree to see the health categories. 3. Click a category link in the right pane to see the details of the I/Port. If the I/Port is offline, its health statistics are not shown. Figure 34 I/Port Inventory and Health View 4.
Figure 35 I/Port System Information Description Window This page intentionally left blank. 58 • Inventory and Health Grid Center 4.
Viewing Blade Health Health of individual Blades can be seen from the Inventory and Health View. To see a Blade’s status, do the following: 1. From the Health and Inventory View, select Blade Health Stats. 2. Click on a Blade in the left pane to see its health stats. Figure 36 Blade Health Window 3. Click the Expand button next to the Blade name to see additional details. 4. Click a user name link to see currently running tasks for that user. Grid Center 4.
60 • Inventory and Health Grid Center 4.
Appendix A: Using Grid Center with e100 and Capio I/Ports Grid Center 4.11 adds support for ClearCube’s new I/Ports, the Eon e100 and Capio One. These two new architectures differ from ClearCube’s previous I/Ports, although Grid Center’s management capabilities are essentially unchanged. The most significant changes are: • Updates and snapins for the new I/Ports do not work with the I8800 I/Port, and vice versa.
Console Software The new I/Ports use the following console applications: • • Grid Center 4.11 Neoware ezRemote Manager Grid Center is used in its traditional fashion to monitor and manage I/Ports. The ezRemote Manager application is used to push system updates and snapins for the new I/Ports.
With the Grid Center clients installed on the I/Ports and the new Grid Center Linux Update installed on the Grid Center Console, Grid Center ‘s management functionality between the old and the new I/Ports is essentially the same. The two most notable differences are that the Eon e100 I/Ports with XPe report a larger set of parameters in the Inventory and Health View; and ezRemote Manager must be used to push operating system updates to the new I/Ports.
Client Software Grid Center 4.11 maintains full compatibility with the I8800 I/Port, and adds client support for the Eon e100 XPe I/Ports, and Eon e100 and Capio One NeoLinux I/Ports. The Eon e100 is available with either XPe or NeoLinux. The Capio One is available only with NeoLinux. The NeoLinux operating system and client can be installed on an Eon e100, although this is not recommended. Eon e100 and Capio One I/Ports from ClearCube are shipped with Grid Center Client software pre-installed.
The default administrator ID/ password on the NeoLinux I/Ports is root / clearcube. A default user ID/ password is not provided on the on the NeoLinux I/Ports. For security reasons, these passwords should be changed. User accounts can be set up individually via RDP or at the local desktop by the administrator. In addition, Grid Center and ezRemote Manager can execute scripts on multiple I/Ports, offering an effective tool for updating authentication credentials.
Notes When re-imaging an Eon e100 XPe I/Port, the initial system messages report that NeoLinux is loading. This is correct. NeoLinux is used to begin the XPe installation. When the installation is complete, the I/Port will restart in XPe. Do not turn off power to the I/Port during a software update. After updating or re-imaging an Eon e100 XPe I/Port, system response will be slower until after the system saves its user settings the first time.
Contacting Support ClearCube In the event you have any problems with your ClearCube software, please refer to our Web site or contact ClearCube Technical Support for guidance. support@clearcube.com Email address to ClearCube Technical Support support.clearcube.com ClearCube Support Website (866) 652-3400 +1 (512) 652-3400 Direct line in the US Direct line from outside the US Active Perl ClearCube Grid Center 4.11 utilizes ActiveState Perl technology.
This page intentionally left blank. 68 • Contacting Support Grid Center 4.
Index A E ActiveState Perl installing 5, 12 adding Blade group 43 I/Port group 44 I/Ports to a group 45 Administration Console 18 configuring 29 installing 13 All-in-One Installer 7 allocating Blades 47 I/Ports 47 allocation 41 dedicated 41 deleting 50 shared 41 spare 41 Allocation View 2, 22, 47 Edit Groups View 21 B I Blade allocating 47 Blade group adding Blades 43 creating 43 Blade health viewing 59 I/Port allocating 47 sparing 54 switching 53 I/Port group adding I/Ports 45 creating 44 I/Port hea
S shared allocation 41 spare allocation 41 sparing I/Port 54 support ActivePerl 67 ClearCube 67 switching I/Port 53 Switching View 2, 21, 51 U uninstalling Administrator Console 13, 14, 15 Update View 3, 23, 55 updating I/Port software 55 V viewing Blade health 59 I/Port health 57 70 • Index Grid Center 4.
ClearCube Technology, Inc. 8834 Capital of Texas Highway North Austin, Texas 78759 voice 512.652.3500 www.clearcube.com P/N 020031-B Rev.
